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:

  • Create a Static Route(s) on the SWe Lite to route signaling/media traffic to the Media (non admin) interface(s). 

  • Change the primary network interface assignment from the Management interface to the Media interface. Follow the steps below to designate another network's interface as primary.

 

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.

 

Before changing the default route, Ribbon highly recommends adding a static route for the management subnet. Otherwise, you will have to connect the SBC Edge via primary network interface. Refer to: Creating Entries in a Static IP Route Table.

Ribbon does not recommend configuring a Default Gateway using IP Static Route in the SBC SWe Lite configuration.

Prerequisites

 PowerShell is an option used to create a resource in Azure. Use Azure CLI PowerShell module or Azure RM PowerShell module to login into PowerShell as follows:

  1. Install Azure CLI PowerShell module or Azure RM PowerShell module on your laptop.

  2. Login to Azure with PowerShell:

    ### Azure CLI ###
az login

### Azure RM ###
Connect-AzureRmAccount

Change Primary Network Interface

  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. Access PowerShell. Refer to the PowerShell documentation.

    Follow Powershell instructions for all commands.

  6. 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 "SWeLite"
az vm nic set -g $ResourceGroup --vm-name "SWeLite" --nics swelite856,SWeLite-2 --primary-nic SWeLite-2

### Azure RM ###
# List existing NICs on the VM and find which one is primary
$vm = Get-AzureRmVm -Name "SWeLite" -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
  7. From the list of VMs, click the check box next to the SBC SWe Lite VM.
  8. From the main menu select Start (alternatively, right-click on the desired VM and select Start).

 

  • No labels