Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring the vMX Instance

    The parameters required to configure vMX are defined in the startup configuration file. The configuration file is in YAML format. The default file is config/vmx.conf. You can save your configuration file to a different name for different instances.

    To customize the configuration, perform these tasks:

    Configuring the Host

    To configure the host environment, you must change the identifier for each vMX instance and you must provide the correct path for the images.

    To configure the host, navigate to Host and specify the following parameters:

    • identifier—Name of the vMX instance, maximum of four alphanumeric characters.
    • host-management-interface—Name of the physical NIC on the host device that is used for management access (eth0).

      Note: The interfaces for HOST:host-management-interface, CONTROL_PLANE, and FORWARDING_PLANE must be on the same subnet.

    • routing-engine-image—Absolute path to the jinstall64-vmx.img file for launching VCP.
    • routing-engine-hdd—Absolute path to the vmxhdd.img file for VCP storage.
    • forwarding-engine-image—Absolute path to the vPFE.img file for launching VFP. The image file can be the performance image or the lite image.
    • make-local-copy-of-images—(Optional) Makes a local copy of the VCP and VFP images and uses the local copy to launch vMX. Default value is yes.
    • make-local-copy-of-vmxhdd—(Optional) Makes a local copy of the VCP storage image and uses the local copy to launch vMX. Default value is yes.

    Configuring the VCP VM

    To configure the VCP VM, you must change the IP address and you must make sure the console port is not being used by another vMX instance or another server.

    To configure the VCP VM, navigate to CONTROL_PLANE and specify the following parameters:

    • vcpus—Number of vCPUs for the VCP, default is 1.
    • memory-mb—Amount of memory for the VCP, default is 2 GB.
    • console_port—KVM TCP-based console port. It must be a unique number.
    • ipaddr—Management IP address for the VCP VM (fxp0). Navigate to interfaces > type (static) > ipaddr to modify this parameter.

      Note: The interfaces for HOST:host-management-interface, CONTROL_PLANE, and FORWARDING_PLANE must be on the same subnet.

    Configuring the VFP VM

    Before you configure the VFP VM, consider the following:

    • You must make sure the console port is not being used by another vMX instance or another server.
    • To disable network access to the VFP console, do not configure an IP address.
    • Based on your requirements, you might want to change the memory, number of vCPUs, and the device type. See Sample Configurations for Use Cases for some sample configuration requirements.

    To configure the VFP VM, navigate to FORWARDING_PLANE and specify the following parameters:

    • memory-mb—Amount of memory for the VFP, default is 6 GB.
    • vcpus—Number of vCPUs for the VFP, default is 3.
    • console_port—KVM TCP-based console port. It must be a unique number.
    • device-type—NIC interface type, either sriov or virtio.
    • ipaddr—Management IP address for the VFP VM (eth0). Navigate to interfaces > type (static) > ipaddr to modify this parameter.

      Note: The interfaces for HOST:host-management-interface, CONTROL_PLANE, and FORWARDING_PLANE must be on the same subnet.

    Configuring Interfaces

    The JUNOS_DEVICES interface names correspond to the Linux physical NIC names on the host. Bring up the Linux physical NIC ports that are defined in this section before proceeding. For example, use the ifconfig eth9 up command to bring up the NIC ports on the eth9 interface.

    To configure interfaces for virtio device types, you must specify the interface and the MAC address.

    To configure interfaces for SR-IOV device types, you must specify the interface, the NIC, and the MAC address.

    To configure the routed interfaces, navigate to JUNOS_DEVICES and specify the following parameters:

    • interface—Name of the interface on the vMX.

      Note: The interface names that are defined in the vmx.conf file must be contiguous starting from ge-0/0/0. The total number of interfaces supported is 10, up to ge-0/0/9.

    • port-speed-mbps—(SR-IOV only) Port speed for the physical NIC, default is 10000 Mbps.
    • nic—(SR-IOV only) Name of the physical NIC.

      Note: Depending on the version of udev, you can rename the classic Linux standard ethXX names. See Predictable Network Interface Names for more information.

    • mtu—(SR-IOV only) MTU value, default is 2000 and maximum is 9500.

      To change the MTU configuration for virtio device types, modify the mtu parameter in the device binding file (vmx-junosdev.conf).

    • virtual-function—(SR-IOV only) Child unit of the physical NIC, default is 0.
    • mac-address—MAC address for the physical NIC.
    • description—Description of the mapping.

    Modified: 2015-10-14