Vyatta Network OS Documentation

Learn how to install, configure and operate the Vyatta NOS, which helps drive our virtual networking & physical platforms portfolio.

Create a Vyatta NOS VM

Information about creating a Vyatta NOS VM and the commands needed to do so.

After creating all the required resources, you can create a Vyatta NOS VM. When creating your Vyatta NOS VM, it is important to select the correct VM size. Ciena supports Vyatta NOS only on F-class VMs. Details of the various VM sizes are available at https://azure.microsoft.com/en-gb/documentation/articles/virtual-machines-linux-sizes/

Note:

It is important not to use A-class or D-class VMs for the router in Azure. These VMs lack some processor features that Vyatta NOS requires, and using them leads to unexpected behavior.

The Vyatta NOS VM image in Azure does not require a Vyatta NOS license to be installed. Instead, you are automatically charged an hourly usage fee for use of Vyatta NOS software.

When creating a Vyatta NOS VM, specify the NICs that are to be attached to it in a comma-separated list. The first listed NIC is known as the primary NIC. The primary NIC is the NIC over which your default route is reached, and is the only NIC that can have a public IP attached to it.

To create a Vyatta NOS VM, use the azure vm create <resource-group> <name> <location> <os-type> command as follows.

$ azure vm create --nic-names vRouter1-Frontend-NIC,vRouter1-DMZ-NIC
--image-urn att_communications:att-vrouter-5600:vrouter-5600:latest
--admin-username azureuser --ssh-publickey-file ~/.ssh/id_rsa.pub --vm-size
Standard_F4 --storage-account-name vrouterdeploy --plan-name vrouter-5600
--plan-publisher att_communications --plan-product att-vrouter-5600 vRouter vRouter1 
westus linux
info:	Executing command vm create
+ Looking up the VM "vRouter1"

info:	Verifying the public key SSH file: /home/user/.ssh/id_rsa.pub info:	Using the VM Size 
"Standard_F4"
info:	The [OS, Data] Disk or image configuration requires storage account
+ Looking up the storage account vrouterdeploy

+ Looking up the NIC "vRouter1-Frontend-NIC"

+ Looking up the NIC "vRouter1-DMZ-NIC"

info:	The storage URI 'https://vrouterdeploy.blob.core.windows.net/' will be used for boot 
diagnostics settings, and it can be overwritten by the parameter input of '--boot-diagnostics-
storage-uri'.
+ Creating VM "vRouter1"

info:	vm create command OK