In this section:
Overview
The
These instructions include how to configure and deploy the
Step 1: Review Prerequisites
This section details the Microsoft Azure cloud computing requirements for hosting the
Microsoft Azure Subscription
A Microsoft Azure subscription (with credit) is required. Refer to Microsoft Azure.
Azure Requirements for Unable to show "metadata-from": No such page "_space_variables" Virtual Machine
Step 2: Create Resource Group
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
Create a Resource Group via Azure portal as follows:
- Connect to the Azure portal. Refer to portal.azure.com.
- From the menu, click Resource groups. For configuration of a Resource Group via Powershell refer to: Using Powershell Commands to Add Resource Groups and Virtual Networks in Azure.
Click Add.
Enter the Resource Group Name and click Review and Create. The Resource Group is validated.
Click Create. The Resource Group is added and listed in the list of Resource Groups.
Step 3: Create a Virtual Network and a Virtual Subnet
The Virtual Network interconnects the
Create a Virtual Network and a Virtual Subnet via Azure Portal
- Connect to the Azure portal. Refer to portal.azure.com.
- From the main menu, select Virtual Networks. For configuration of a Virtual Network and Virtual Subnet via Powershell refer to: Using Powershell Commands to Add Resource Groups and Virtual Networks in Azure.
Click the Add button.
Enter the Virtual network information. See below for example entries.
Click Create. The Virtual network is added and listed in the list of Virtual networks.
- From the list of virtual networks, click on the newly created Virtual network (i.e., SWeLite-Network).
From Settings, select Subnets.
Click +Subnet. The Add subnet window is displayed.
Enter the required information.
Click OK. The subnet is added to the list of subnets.
Step 4: Deploy Unable to show "metadata-from": No such page "_space_variables" From Azure Marketplace
When the
- For configuration, Ribbon recommends using a Premium SSD Disk Drive and Non-accelerated networking.
- Configuration examples for fields are displayed (i.e., IP address, subnet, etc); configure these fields to match your specific deployment.
Configure the
- Connect to the Azure portal. Refer to portal.azure.com.
From the menu, click Create a Resource.
- In the search bar, enter Ribbon and click <Enter>. From the selections, click on Unable to show "metadata-from": No such page "_space_variables".
Review the product description and click Create.
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 (i.e., SWeLite-RG)
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. To determine the required VM size, refer to Calculating Virtual Machine Requirements for an SBC SWe Lite. Supported VM sizes include:
B1ms
B2s
DS1_v2
DS3_v2
- In Authentication Type, click on Password.
Enter Username, Password, and Confirm Password.
Click Next: Disks.
From OS disk type drop down list, select Premium SSD.
- Click Next: Networking.
Review and verify the default fields.
Click Review + Create.
A screen indicates validation of the VM has passed.
Click Create. A VM status is displayed.
When finished, this message is displayed: Your deployment is complete.From the main menu, select Virtual Machines. The newly created
Unable to show "metadata-from": No such page "_space_variables"instance is displayed.
For detailed information on reserving a VM resource, refer to Reserving a VM Resource in Azure.
Step 5: Create/Assign Signaling Network Interface on Unable to show "metadata-from": No such page "_space_variables"
The
Assign Additional Network Interface via Azure Portal as follows:
- Connect to the Azure portal. Refer to portal.azure.com.
- From the menu, select Virtual Machines
- From the list of VMs, click the check box next to the desired Unable to show "metadata-from": No such page "_space_variables"VM.
From the main menu select Stop and 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.
- Click on the desired VM to view the settings.
- From Settings > Networking, click Attach network interface.
Click Create network interface.
In the Create network interface window, enter the required information. Ensure you enter the signaling subnet address configured previously.
- Click Create.
Click Attach network interface and select the newly created Network Interface. Click OK.
Confirm that your VM has two NICs.
- From the list of VMs, select the Unable to show "metadata-from": No such page "_space_variables"VM.
- From the main menu select Start (alternatively, right-click on the desired VM and select Start).
Step 6: Connect to Unable to show "metadata-from": No such page "_space_variables" via Azure Portal
Connect to the
- Connect to the Azure portal. Refer to portal.azure.com.
- From the menu, click Virtual Machines.
- Click on the newly created Unable to show "metadata-from": No such page "_space_variables".
From Settings, select Networking.
Under Inbound port rules, restrict the HTTP and HTTPS access to pubic and private address. See below.
To ensure the management interface for the
Unable to show "metadata-from": No such page "_space_variables"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.
The Public IP and Private IP addresses in the example screen below; these values are required for subsequent
Unable to show "metadata-from": No such page "_space_variables"logins during Running Initial Setup on SBC SWe Lite.
Step 7: Run Initial Setup
Proceed to Running Initial Setup on SBC SWe Edge for initial configuration and next steps, which include how to access the WebUI and options to extend the
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
- Create a Static Route(s) on the Unable to show "metadata-from": No such page "_space_variables"to route signaling/media traffic to the Media (non admin) interface(s).
- Create a Static Route(s) on the Unable to show "metadata-from": No such page "_space_variables"to route all traffic to the Media (non admin) interface(s). When you do this, you must configure all Logical Interfaces with the DHCP Options to Use field set to IP Address (refer to Configuring and Modifying Logical Interfaces).
Change the primary network interface assignment from the Management interface to the Media interface. Refer to Change Azure Default Route.
Step 8: License Installation
Trial License Installation
If you are installing an
Production License Installation
If you are installing an