To start a software vEdge Cloud router, you must create a virtual machine (VM) instance for it. This article describes how to create a VM instance on a server running the vSphere ESXi Hypervisor software. You can also create the VM on Amazon AWS or on a server running the Kernel-based Virtual Machine (KVM) Hypervisor software.
For server requirements, see Server Hardware Recommendations.
To create a vEdge Cloud VM instance on the ESXi hypervisor:
- Launch the vSphere Client and create a vEdge Cloud VM instance.
- Add a vNIC for the tunnel interface.
- Start the vEdge Cloud VM instance and connect to the console.
The details of each step are provided below.
If you are using the VMware vCenter Server to create the vEdge Cloud VM instance, follow the same procedure. Note, however, that the vCenter Server screens look different than the vSphere Client screens shown in the procedure.
Launch vSphere Client and Create a vEdge Cloud VM Instance
- Launch the VMware vSphere Client application, and enter the IP address or name of the EXSi server, your username, and your password. Click Login to log in to the ESXi server.
The system displays the ESXi screen.
- Click File ► Deploy OVF Template to deploy the virtual machine.
- In the Deploy OVF Template screen, enter the location to install and download the OVF package. This package is the vedge.ova file that you downloaded from the Viptela Support webpage. Then click Next.
- Click Next to verify OVF template details.
- Enter a name for the deployed template and click Next. The figure below specifies a name for the vEdge instance.
- Click Next to accept the default format for the virtual disks.
- Click Next to accept your destination network name as the destination network for the deployed OVF template. In the figure below, CorpNet is the destination network.
- In the Ready to Complete screen, click Finish. The figure below shows the name for the vEdge instance.
The system has successfully created the VM instance with the parameters you just defined and displays the vSphere Client screen with the Getting Started tab selected. By default, this includes four vNICs which can be used for the management, tunnel, or service interface.
Add a New vNIC
- In the left navigation bar of the vSphere Client, select the vEdge Cloud VM instance you just created, and click Edit virtual machine settings.
- In the vEdge Cloud – Virtual Machine Properties screen, click Add to add a new vNIC. Then click OK.
- Click Ethernet Adapter for the type of device you wish to add. Then click Next.
- In the Adapter Type drop-down, select E1000 for the vNIC to add. Then click Next.
- In the Ready to Complete screen, click Finish.
- The vEdge Cloud – Virtual Machine Properties screen opens showing that the new vNIC is being added. Click OK to return to the vSphere Client screen.
Modify the MTU for a vSwitch
To allow the interface to carry jumbo frames (packets with an MTU of 2000 bytes), configure the MTU for each virtual switch (vSwitch):
- Launch the ESXi Hypervisor and select the Configuration tab.
- In the Hardware box, click Networking. The network adapters you added are displayed in the right pane.
- Click Properties for the vSwitch whose MTU you wish to modify.
- In the vSwitch Properties screen, click Edit.
- In the Advanced Properties MTU drop-down, change the vSwitch MTU to the desired value. The range is 2000 to 9000. Then click OK.
Start the vEdge Cloud VM Instance and Connect To the Console
- In the left navigation bar of the vSphere Client, select the vEdge Cloud VM instance you just created, and click Power on the virtual machine. The vEdge Cloud virtual machine is powered on.
- Select the Console tab to connect to the vEdge Cloud console.
- At the login prompt, log in with the default username, which is admin, and the default password, which is admin. To view the vEdge Cloud router default configuration, enter the following command:
vEdge# show running-config
Mapping vNICs to Interfaces
When you create a vEdge Cloud router VM instance on ESXi in the procedure in the previous section, you create two vNICs: vNIC 1, which is used for the management interface, and vNIC 2, which is used as a tunnel interface. From the perspective of the VM itself, these two vNICs map to the eth0 and eth1 interfaces, respectively. From the perspective of the Viptela software for the vEdge Cloud router, these two vNICs map to the mgmt0 interface in VPN 512 and the ge0/0 interface in VPN 0, respectively. You cannot change these mappings.
You can configure up to five additional vNICs, numbered 3 through 7, on the VM host. You can map these vNICs to interfaces eth2 through eth7 as desired, and to Viptela interfaces ge0/1 through ge0/7, as desired.
The table below summarizes the mapping between vNICs, VM host interfaces, and vEdge Cloud interfaces.
|vNIC||Interface on VM Host||Interface in vEdge Cloud Configuration|
|vNIC 1||eth0||mgmt0 in VPN 512|
|vNIC 3 through 7||eth2 through eth7||ge0/1 through ge0/7|