In this section:
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).
A Virtual Machine (VM) that hosts the SBC SWe Lite, must meet the following prerequisites:
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.
For configuration, Ribbon recommends using a Premium SSD Disk Drive and Non-accelerated networking.
Configure the SBC SWe Lite VM via Azure Portal as follows:
From the menu, click Create a Resource.
Click on Ribbon SBC SWe Lite.
Review the product description and click Create.
In the Basics tab, configure the fields as described below.
From the Resource group drop down list, select the Resource Group created previously (or to create a new Resource Group, click Create new and enter the Resource Group).
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.
Click Next: Disks.
From OS disk type drop down list, select Premium SSD.
Review and verify the default fields.
Click Review + Create. A summary of the virtual machine is displayed.
Click Create. A VM status is displayed.
From the main menu, select Virtual Machines. The newly created SBC SWe Lite instance is displayed.
Perform these steps via Azure Portal:
From the main menu select Stop and wait for the VM status to be Stopped (Deallocated). Alternatively, right-click on the desired VM and select Stop.
Click Attach network interface and select Create network interface.
Enter the required information.
Select the newly created Network Interface and click OK.
Confirm that your VM has two NICs.
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:
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.
Follow Powershell instructions for all commands.
Run one of the following commands (per Azure CLI PowerShell module or Azure RM PowerShell module):
$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 Azure Portal:
Select the first Network Interface.
Under Inbound port rules, restrict the HTTP and HTTPS access to your personal IP Address.
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).
Click Save.
Connect to the Public IP or Private IP from a supported browser to access the SBC SWe Lite initial Setup page.
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.
Proceed to SBC SWe Lite Initial Setup.