This procedure maps the network interfaces in the initial setup on the
You do not need to perform this procedure if you use the cloud-init function.
To assign a virtual NIC to a physical network adaptor, refer to the respective third-party documentation:
KVM Hypervisor: http://www.linux-kvm.org/page/HOWTO
Microsoft Hyper-V: https://technet.microsoft.com/en-us/library/mt169373(v=ws.11).aspx
VMware ESXi: https://www.vmware.com/support/pubs/
Microsoft Azure: Deploying an SBC SWe Lite via Azure Marketplace
Log in as user
netconfig
with password asConfig!
. Change the password when prompted.Modify Password
Static or DHCP IP
Choose DHCP or enter a static IP address.
For
Unable to show "metadata-from": No such page "_space_variables"deployment in Azure, Microsoft does not recommend assigning static IP address on theUnable to show "metadata-from": No such page "_space_variables"'s Ethernet port; you must configure theUnable to show "metadata-from": No such page "_space_variables"'s ethernet port to use DHCP.Would you like to configure a static IP address for Initial Setup on the Admin interface? This is only required if DHCP is unavailable (y/[n]): n
Enter the interface name to map the interface as shown in the WebUI when prompted by the interface mapping shell script.
InfoThe interface mapping shell script requests that the user provide the interface name to map the interface as shown in the WebUI.
Use the MAC address (identified in the virtual machine editing portion during Installing SBC SWe Edge on your specific platform) in order to correctly map the interface. The interface name and MAC address are required to properly activate the interface and have it appear on the WebUI.
- Enter an admin interface name. Example:
mgt0
. Enter an Ethernet 1 Media interface name. Example:
pkt0
.Enter each subsequent Ethernet Media interface Name, and then apply the changes.
Saving Interface Mapping