Installing vMX for Different Use Cases

 

Installing vMX is different for specific use cases. Table 1 lists the sample configuration requirements for some vMX use cases.

Table 1: Sample Configurations for Use Cases

Use Case

Minimum vCPUs

Minimum Memory

NIC Device Type

Lab simulation

Up to 100 Mbps performance

4:

1 for VCP

3 for VFP

5 GB:

1 GB for VCP

4 GB for VFP

virtio

Low-bandwidth applications

Up to 3 Gbps performance

10:

1 for VCP

9 for VFP

20 GB:

4 GB for VCP

16 GB for VFP

virtio

High-bandwidth applications or performance testing

For 3 Gbps and beyond performance

10:

1 for VCP

9 for VFP

20 GB

4 GB for VCP

16 GB for VFP

SR-IOV

Dual virtual Routing Engines

Note: When deploying on separate hosts, you must set up a connection between the hosts for the VCPs to communicate with each other.

Double the number of VCP resources for your particular use case is consumed when deploying both VCP instances.

Double the number of VCP resources for your particular use case is consumed when deploying both VCP instances.

virtio or SR-IOV

To install vMX for a particular use case, perform one of the following tasks:

Installing vMX for Lab Simulation

The use case for lab simulation uses the virtio NIC.

To install vMX for the lab simulation (less than 100 Mbps) application use case:

  1. Download the vMX software package as root and uncompress the package.

    tar xzvf package-name

  2. Change directory to the location of the uncompressed vMX package.

    cd package-location

  3. Edit the config/vmx.conf text file with a text editor to configure a single vMX instance.

    Ensure the following parameter is set properly in the vMX configuration file:

    device-type : virtio

    See Specifying vMX Configuration File Parameters.

  4. Run the ./vmx.sh -lv --install script to deploy the vMX instance specified by the config/vmx.conf startup configuration file and provide verbose-level logging to a file. See Deploying vMX.
  5. From the VCP, enable lite mode for the VFP.
    user@vmx# set chassis fpc 0 lite-mode

Here is a sample vMX startup configuration file using the virtio device type for lab simulation:

Installing vMX for Low-Bandwidth Applications

The use case for low-bandwidth applications uses virtio or SR-IOV NICs.

To install vMX for the low-bandwidth (up to 3 Gbps) application use case:

  1. Download the vMX software package as root and uncompress the package.

    tar xzvf package-name

  2. Change directory to the location of the uncompressed vMX package.

    cd package-location

  3. Edit the config/vmx.conf text file with a text editor to configure a single vMX instance.

    Ensure the following parameter is set properly in the vMX configuration file:

    device-type: virtio or device-type: sriov

    See Specifying vMX Configuration File Parameters.

  4. Run the ./vmx.sh -lv --install script to deploy the vMX instance specified by the config/vmx.conf startup configuration file and provide verbose-level logging to a file. See Deploying vMX.
  5. From the VCP, enable performance mode for the VFP.
    user@vmx# set chassis fpc 0 performance-mode

Here is a sample vMX startup configuration file using the virtio device type for low-bandwidth applications:

Installing vMX for High-Bandwidth Applications

The use case for high-bandwidth applications uses the SR-IOV NICs.

To install vMX for the high-bandwidth (above 3 Gbps) application use case:

  1. Download the vMX software package as root and uncompress the package.

    tar xzvf package-name

  2. Change directory to the location of the uncompressed vMX package.

    cd package-location

  3. Edit the config/vmx.conf text file with a text editor to configure a single vMX instance.

    Ensure the following parameter is set properly in the vMX configuration file:

    device-type: sriov

    See Specifying vMX Configuration File Parameters.

  4. Run the ./vmx.sh -lv --install script to deploy the vMX instance specified by the config/vmx.conf startup configuration file and provide verbose-level logging to a file. See Deploying vMX.
  5. From the VCP, enable performance mode for the VFP.
    user@vmx# set chassis fpc 0 performance-mode

Here is a sample vMX startup configuration file using the SR-IOV device type:

Installing vMX with Dual Routing Engines

You can set up redundant Routing Engines on the vMX server by creating the master Routing Engine (re0) and backup Routing Engine (re1) in the CONTROL_PLANE section of the vMX startup configuration file (default file is config/vmx.conf).

Note

When deploying the Routing Engines on separate hosts, you must set up a connection between the hosts for the VCPs to communicate with each other.

To install vMX for the dual Routing Engines use case:

  1. Download the vMX software package as root and uncompress the package.

    tar xzvf package-name

  2. Change directory to the location of the uncompressed vMX package.

    cd package-location

  3. Edit the config/vmx.conf text file with a text editor to configure the vMX instance.

    The default CONTROL_PLANE section resembles the following with one interface entry:

    To set up the redundant Routing Engines:

    1. Navigate to CONTROL_PLANE and specify the proper number of vCPUs (vcpus) and amount of memory (memory-mb).
    2. Starting with Junos OS Release 18.1R1, add the deploy parameter to designate the Routing Engine instance deployed on this host. If you do not specify this parameter, all instances (0,1) are deployed on the host.

      When deploying the Routing Engines on separate hosts, you must set up a connection between the hosts for the VCPs to communicate with each other.

    3. Modify the interfaces entry to add instance : 0 after the type parameter to set up re0.

      Specify the ipaddr and macaddr parameters. This address is the management IP address for the VCP VM (fxp0).

    4. Add another entry, but specify instance : 1 to set up re1 and specify the console_port parameter for re1 after the instance : 1 parameter.

      Specify the ipaddr and macaddr parameters. This address is the management IP address for the VCP VM (fxp0).

    The revised CONTROL_PLANE section that deploys re0 on the host resembles the following example with two interface entries:

    See Specifying vMX Configuration File Parameters.

  4. Run the ./vmx.sh -lv --install script to deploy the vMX instance specified by the config/vmx.conf startup configuration file and provide verbose-level logging to a file. See Deploying vMX.
  5. From the VCP, enable performance mode for the VFP.
    user@vmx# set chassis fpc 0 performance-mode
  6. When deploying the Routing Engines on separate hosts, you must set up a connection between the hosts for the VCPs to communicate with each other.

    For example, to set up a connection (such as br-int-vmx1) between the two hosts over an interface (such as eth1), run the following command on both hosts:

    ifconfig eth1 up && brctl addif br-int-vmx1 eth1

Here is a sample vMX startup configuration file that is deploying the first Routing Engine instance on this host:

Installing vMX with Mixed WAN Interfaces

The use case for mixed WAN interfaces uses the virtio and SR-IOV interfaces. Sample configuration requirements are the same as for using SR-IOV device type.

To install vMX with mixed interfaces:

  1. Download the vMX software package as root and uncompress the package.

    tar xzvf package-name

  2. Change directory to the location of the uncompressed vMX package.

    cd package-location

  3. Edit the config/vmx.conf text file with a text editor to configure a single vMX instance.

    Ensure the following parameter is set properly in the vMX configuration file:

    device-type: mixed

    When configuring the interfaces, make sure the virtio interfaces are specified before the SR-IOV interfaces. The type parameter specifies the interface type.

    See Specifying vMX Configuration File Parameters.

  4. Run the ./vmx.sh -lv --install script to deploy the vMX instance specified by the config/vmx.conf startup configuration file and provide verbose-level logging to a file. See Deploying vMX.
  5. From the VCP, enable performance mode for the VFP.
    user@vmx# set chassis fpc 0 performance-mode

Here is a sample vMX startup configuration file using mixed interfaces: