Ribbon SWe Lite step-by-step deployment on Azure

Hi All,

Ribbon has released the Azure Marketplace version of their Virtual SBC SWe Lite.
Thanks to Ribbon, I got the opportunity to try the Preview version… and it works like a charme!

The initial configuration is quite easy, and the Azure Marketplace version come with a 30 days trial license embed, so you can start to use it immediately!

Let’s see how to deploy it.

Deploy the VM on Azure

Create a new Resource Group
I’ll use Ribbon-RG in this article

Deploy a new VM
Search for Ribbon SWe Lite in the Azure Marketpalce and follow the images below.
Choose a very strong password for the sweliteadmin account

Configure the VM

I want to add new Network Interfaces with custom names, in this example ribbonswelite-01-admin for the mandatory Admin Interface (Mgt0) that we will disable at the end, and ribbonswelite-01-wan for the production NIC that will receive Public IP at the end.

Note: Ribbon do not suggest to disable the Admin Interface but to connect it to a dedicated network in Azure.

Create the ribbonswelite-01-admin Network Interface

Do the same to create the ribbonswelite-01-wan Network Interface

Stop the VM.

Attach the ribbonswelite-01-admin Network Interface

Detach the initially randomly created Network Interface

Create and assign a Public IP to the Admin Network Interface

Be carefull to select a Static assignment for the Public IP

Now you can safely delete the initially randomly created Network Interface

Start the VM

Initial Setup

Connect the https://<PublicIP&gt;

Complete the Initial Setup page.
I prefer to not autorun Easy Setup

Make sure you can see the SWe Lite login page then stop the VM again

WAN Interface

Attach the ribbonswelite-01-wan Network Interface to the VM

Now you should have this Network Interfaces configuration

Start the VM.

Login to SWe Lite

Setup the Ethernet 1 IP Logical Interface

Stop the VM

Remove the Public IP from the ribbonswelite-01-admin Network Interface

Assign the Public IP to the ribbonswelite-01-wan Network Interface

Refresh the page. Now you should see the Public IP listed in the ribbonswelite-01-wan Network Interface.

Change Primary Network Interface via PowerShell

Now we need only to change the Primary Network Interface, and this can be done via PowerShell only.
I use Cloud Shell (I love it), you can find it in the upper right menu of Azure Portal

Run these commands

# List existing NICs on the VM and find which one is primary 
$vm = Get-AzureRmVm -Name "ribbonswelite-01" -ResourceGroupName Ribbon-RG
#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 Ribbon-RG

Start the VM for the last time

Login to the SWe Lite and disalbe the Admin Logical Interface.

You should have this Logical Interfaces configuration

The SWe Lite deployment on Azure is completed.
Now you should launch the Easy Config Wizard for Teams Direct Routing and configure the SWe Lite as usual.
Remember only that SWe Lite on Azure could not use Teams Direct Routing Media Bypass due to the fact that the Public IP use NAT, so ICE Lite don’t work.

I hope this could help some of you.

7 thoughts on “Ribbon SWe Lite step-by-step deployment on Azure

Add yours

  1. Hi Luca,

    followed your steps here (very clear – thank you!) and the only question is that when I get to step ‘Setup the Ethernet 1 IP Logical Interface’ and enter the options you show, when I apply I get an error saying I must enter a value for the ‘Media Next Hop IP’ field. Can you explain what is the best thing to put in this field – would it be the vNet subnet default gateway (.1) ? Thanks – Antony


    1. Hi Antony,
      Thank you for your kind word. About your question, Media Next Hop is always the network gateway of that interface. You need to set the Media Next Hop IP for every NIC, and obviously any configured NIC will have it’s own, unique, gateway. Just to be clear, one of these gateway will be ALSO the SBC Default Gateway, but these are completely different settings. Hope this will help you. Best. Luca


  2. We have our SWe Lite setup in Azure but it keeps sending the private interface address out in the SIP header, even though the outbound NAT rule on all the signalling group is set to NAT and the public address. Something in Azure seems to be ignoring /re-writing what we’re putting in the SIP header…and putting it back to the private address. Any ideas!?


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Create a free website or blog at WordPress.com.

Up ↑

%d bloggers like this: