Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
In this section:
|
Note |
---|
Before deploying an SBC SWe Lite instance in Azure, follow the instructions in Preparing Microsoft Azure to Host SWe Lite. |
The SBC SWe Lite is a Microsoft-certified virtualized Session Border Controller (SBC) designed to provide small and mid-sized businesses interworking, security, and survivability for unified communications. The SWe Lite is available for deployment in Azure Marketplace as a BYOL (Bring Your Own License); it will be created as a virtual machine (VM) hosted in Azure.
These instructions include how to configure and deploy the SBC SWe Lite in Microsoft Azure cloud. All configuration commands are via Azure Portal; the equivalent Powershell configuration comments are referenced here: Using Powershell Commands to Add Resource Groups and Virtual Networks in Azure.
...
Caption | |
---|---|
|
...
|
...
|
...
|
...
...
| |
This section details the Microsoft Azure cloud computing requirements for hosting the SWe Lite VM and SWe Lite related resources.
A Microsoft Azure subscription (with credit) is required. Refer to Microsoft Azure.
Caption | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Warning |
---|
When creating the Azure resource, Ribbon recommends always using the same resource location. |
The Resource Group contains the necessary configuration for Azure to host the SWe Lite VM and the SWe Lite related resources. To deploy a SWe Lite in the Microsoft Azure .
cloud, the resource group is required for a Virtual Machine (VM).
Create a Resource Group via Azure portal as follows:
Click Add.
Caption | ||||
---|---|---|---|---|
| ||||
Enter the Resource Group Name and click Review and Create. The Resource Group is validated.
Caption | ||||
---|---|---|---|---|
| ||||
|
Click Create. The Resource Group is added and listed in the list of Resource Groups.
Caption | ||||
---|---|---|---|---|
| ||||
The Virtual Network interconnects SWe Lite with other equipment inside and outside Azure. The Virtual Subnet hosts the SWe Lite IP addresses and are interconnected by the previously created Virtual Network. The SBC SWe Lite requires at least two Virtual Subnets, one for management and one for signaling/media. Even though management operations can be performed through the signaling/media subnet, for security reasons, Ribbon recommends disabling HTTP/HTTPS on the signaling/media subnet via ACL.
Create a Virtual Network and a Virtual Subnet via Azure Portal
Click the Add button.
Caption | ||||
---|---|---|---|---|
| ||||
Enter the Virtual network information. See below for example entries.
Caption | ||||
---|---|---|---|---|
| ||||
|
Click Create. The Virtual network is added and listed in the list of Virtual networks.
Caption | ||||
---|---|---|---|---|
| ||||
From Settings, select Subnets.
Caption | ||||
---|---|---|---|---|
| ||||
Click +Subnet. The Add subnet window is displayed.
Enter the required information.
Caption | ||||
---|---|---|---|---|
| ||||
Click OK. The subnet is added to the list of subnets.
Caption | ||||
---|---|---|---|---|
| ||||
When the SBC SWe Lite image is deployed via Azure Marketplace, the image automatically appears in the general list of available images in Azure Portal. The single image can be used to deploy multiple SBC SWe Lite instances.
Info | ||
---|---|---|
| ||
|
Configure the SBC SWe Lite VM via Azure Portal as follows:
From the menu, click Create a Resource. Caption
0 | Figure |
---|---|
1 | Search for Ribbon SWe Lite |
Caption | ||||
---|---|---|---|---|
| ||||
|
Review the product description and click Create.
Caption | ||||
---|---|---|---|---|
| ||||
In the Basics tab, configure the fields as described below.
From the Resource group drop down list in the left side menu, select the Resource Group created previously (or to create a new Resource Group, click Create new and enter the Resource Group).i.e., SWeLite-RG)
Info |
---|
To view recommended VM sizes, refer to Virtual Machine Requirements - Microsoft Azure. |
In Virtual machine name field, enter SWeLite.
In Size, click Change size to select the applicable VM size (Azure selects Standard B1ms as the default option). To determine the required VM size, refer to Calculating Virtual Machine Requirements for an SBC SWe Lite. Supported VM sizes include:
B1ms
F1s
F2s
F4s
Enter Username, Password, and Confirm Password.
Caption | ||||
---|---|---|---|---|
| ||||
|
Click Next: Disks.
From OS disk type drop down list, select Premium SSD.
Caption | |||||
---|---|---|---|---|---|
| |||||
Review and verify the default fields.
Caption | ||||
---|---|---|---|---|
| ||||
Click Review + Create.
A summary screen indicates validation of the virtual machine is displayedVM has passed.
Caption | |||||
---|---|---|---|---|---|
| |||||
Click Create. A VM status is displayed.
Caption | ||||
---|---|---|---|---|
| ||||
From the main menu, select Virtual Machines. The newly created SBC SWe Lite instance is displayed.
Caption | ||||
---|---|---|---|---|
| ||||
|
...
Expand | ||
---|---|---|
| ||
Perform these steps via PowerShell:
|
Warning |
---|
The SBC SWe Lite requires at least two Network Interfaces to function at the minimum, one for management and one for signaling/media. |
Assign Additional Network Interface via Azure Portal as followsPerform these steps via Azure Portal:
From the main menu select Stop and wait then Yes to acknowledge stopping the VM. Wait for the VM status to be Stopped (Deallocated), which can sometimes take a few minutes. Alternatively, right-click on the desired VM and select Stop.
Caption | ||||
---|---|---|---|---|
| ||||
Click Attach network interface and select Create network interface.
Caption | ||||
---|---|---|---|---|
| ||||
In the Create network interface window, enter Enter the required information. Ensure you enter the signaling subnet address configured previously.
Caption | ||||
---|---|---|---|---|
| ||||
Select Click Attach network interface and select the newly created Network Interface and click . Click OK.
Caption | ||||
---|---|---|---|---|
| ||||
Confirm that your VM has two NICs.
Caption | ||||
---|---|---|---|---|
| ||||
Expand | ||
---|---|---|
| ||
Perform these steps via PowerShell:
|
Info |
---|
Microsoft does not recommend assigning static IP address on the SBC SWe Lite's Ethernet port; you must configure the SBC SWe Lite's ethernet port to use DHCP. Use the Azure portal to let Azure choose the IP address (dynamic) or specify an IP address (static). In both cases, the SBC SWe Lite receives this IP using DHCP protocol. Refer to https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-static-private-ip-arm-pportal. |
When using multiple NICs on the SBC SWe Lite, Azure designates the first network's Interface as the primary network interface. Only the primary network interface receives a network default gateway and routes via DHCP. To assign the network default route on another subnet, you must designate another Network's Interface as the primary networks interface. Follow these steps to nominate another network's interface as primary:
Warning |
---|
Ribbon does not recommend configuring a Default Gateway using IP Static Route in the SBC SWe Lite configuration. |
Access PowerShell. Refer to the PowerShell documentation.
Info |
---|
Follow Powershell instructions for all commands. |
Run one of the following commands (per Azure CLI PowerShell module or Azure RM PowerShell module):
Code Block |
---|
$ResourceGroup = "SWeLite-RG"
### Azure CLI ###
# List existing NICs on the VM and find which one is primary
az vm nic list -g $ResourceGroup --vm-name "swelite800-1"
az vm nic set -g $ResourceGroup --vm-name "swelite800-1" --nic mgt0 pkt0 --primary-nic pkt0
### Azure RM ###
# List existing NICs on the VM and find which one is primary
$vm = Get-AzureRmVm -Name "swelite800-1" -ResourceGroupName $ResourceGroup
$vm.NetworkProfile.NetworkInterfaces
# Set NIC 1 to be primary
$vm.NetworkProfile.NetworkInterfaces[0].Primary = $false
$vm.NetworkProfile.NetworkInterfaces[1].Primary = $true
# Update the VM state in Azure
Update-AzureRmVM -VM $vm -ResourceGroupName $ResourceGroup
|
Perform these steps using Connect to the SBC SWe Lite via Azure Portal as follows:
From Settings, select Networking.
Select the first Network Interface.
Under Inbound port rules, restrict the HTTP and HTTPS access to your personal IP Addresspubic and private address. See below.
Info |
---|
To ensure the management interface for the SBC SWe Lite can only be reached from the IP address(es) you specify, restrict the HTTP and HTTPS access to your personal IP address (per previous step). |
Caption | ||||
---|---|---|---|---|
| ||||
Caption | ||||
---|---|---|---|---|
| ||||
| ||||
Click Save.
Info |
---|
The |
Connect to the Public IP or Private IP from a supported browser to access the SBC SWe Lite initial Setup page.
Info |
---|
Note the Public IP and Private IP addresses in the example screen below; these values are required for subsequent SBC SWe Lite logins during Running Initial Setup on SBC SWe Lite. |
Caption | ||||
---|---|---|---|---|
| ||||
|
...
Proceed to SBC SWe Lite Initial Setup for initial configuration and next steps, which include how to access the WebUI and options to extend the SBC SWe Lite trial indefinitely. One initial setup is complete, return here to Step 8,
Info |
---|
By default, Azure designates the VM’s first network's Interface as the primary network interface. Only the primary network interface receives a network default gateway and routes via DHCP. The first network interface on the SWe Lite is recommended to be used only for management. Media traffic routed to this interface will not be processed. To avoid this problem, you must either:
|
The SBC Edge is configured via Easy Configuration Wizard.
Caption | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Calls can be tested via the SWe Lite's WEB UI.
In the left navigation pane, under Tools, click Test a Call.
Caption | ||||
---|---|---|---|---|
| ||||
|