You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

 

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).  

Configure an SBC SWe Lite Virtual Machine

Prerequisites

A Virtual Machine (VM) that hosts the SBC SWe Lite, must meet the following prerequisites:

Prerequisites

RequirementsDescription/How to Obtain
Microsoft PowerShellAn option used to create an SBC SWe Lite VM. Refer to PowerShell documentation.
Azure Virtual Machine Requirements
Refer to Virtual Machine Requirements - Microsoft Azure.

Configure SBC SWe Lite VM via Azure Portal

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:

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the menu, click Create a Resource.

    Search for Ribbon SWe Lite

  3. In the search bar, enter Ribbon and click <Enter>. The Ribbon SWe Lite option is displayed.
  4. Click on Ribbon SBC SWe Lite.

  5. Review the product description and click Create.

    Product Description

  6. In the Basics tab, configure the fields as described below.

  7. 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.

  8. In Virtual machine name field, enter SWeLite.

  9. 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:

    1. B1ms

    2. F1s

    3. F2s

    4. F4s

  10. In Authentication Type, click on Password.
  11. Enter Username, Password, and Confirm Password.

    Create a virtual machine - Basics

  12. Click Next: Disks.

  13. From OS disk type drop down list, select Premium SSD.

    Create a virtual machine - Disks

     

  14. Click Next: Networking.
  15. Review and verify the default fields.

    Create a virtual machine - Networking

  16. Click Review + Create. A summary of the virtual machine is displayed.

    Review & Create

  17. Click Create. A VM status is displayed.

    Create VM


    A message is displayed to indicate the deployment is complete.

  18. From the main menu, select Virtual Machines. The newly created SBC SWe Lite instance is displayed.

    Select Virtual Machines

     

Create SWe Lite VM via Microsoft PowerShell

Perform these steps via PowerShell:

  1. Access PowerShell. Refer to PowerShell documentation.
  2. Run the following commands (per Azure CLI PowerShell module):

     

    $ResourceGroup = "SWeLite-RG"
    $VirtualNetwork = "SWeLite-Network"
    $Image = "ribboncommunications:ribbon_sbc_swe-lite:ribbon_sbc_swe-lite:8.0.0"
    
    ### Azure CLI ###
    az network nic create --resource-group $ResourceGroup --name "swelite800-1-1" --vnet-name $VirtualNetwork --subnet MySubnet1
    az network nic create --resource-group $ResourceGroup --name "swelite800-1-2" --vnet-name $VirtualNetwork --subnet MySubnet2
    az vm create -g $ResourceGroup -n "swelite800-1" --image $Image --size "Standard_B1ms" --generate-ssh-keys --nics "swelite800-1-1" "swelite800-1-2"
    
    

Assign Additional Network Interface on SBC SWe Lite

Assign Additional Network Interface via Azure Portal

Perform these steps via Azure Portal:

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the menu, select Virtual Machines
  3. From the list of VMs, click the check box next to the desired SBC SWe Lite VM.
  4. 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.

    SWe Lite VM - Stop function

  5. Click on the desired VM to view the settings.
  6. From Settings, select Networking.
  7. Click Attach network interface and select Create network interface.

    Select SWe Lite

  8. Enter the required information.

    Create Network Interface

  9. Click Create.
  10. Select the newly created Network Interface and click OK.

    Create Network Interface

  11. Confirm that your VM has two NICs.

    Confirm NICs

Assign Additional Network Interface via PowerShell

Perform these steps via PowerShell:

  1. Access PowerShell. Refer to PowerShell documentation.
  2. Run the following commands (per Azure CLI PowerShell module):

     

    $ResourceGroup = "SWeLite-RG"
    $VirtualNetwork = "SWeLite-Network"
    
    ### Azure CLI ###
    az network nic create --resource-group $ResourceGroup --name "swelite-2" --vnet-name $VirtualNetwork --subnet pkt0
    az vm nic add -g $ResourceGroup --vm-name "swelite" --nics "swelite-2"
    

Change Azure Default Route

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.

Change Primary Network Interface

  1. Access PowerShell. Refer to the PowerShell documentation.

    Follow Powershell instructions for all commands.

  2. 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
     
  3. In Azure, from the list of VMs, select the SBC SWe Lite VM.
  4. From the main menu select Start (alternatively, right-click on the desired VM and select Start).

Connect to SBC SWe Lite via Azure Portal

Perform these steps using Azure Portal:

  1. Connect to the Azure portal. Refer to portal.azure.com.
  2. From the menu, click Virtual Machines.
  3. Select the SBC SWe Lite VM.
  4. From Settings, select Networking.
  5. Select the first Network Interface.

  6. 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).


  7. Click Save.

    Inbound Port Rules

  8. 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.


    Public and Private IP Addresses

     


Complete Initial Setup

Proceed to SBC SWe Lite Initial Setup. 

 

  • No labels