This document describes step by step how to install Unified Network Lab (UNetLab ) and how to run Juniper vMX in the UNetLab.Keywords: Unified Network Lab, UNetLab, Junos, Juniper, vMX.Author:​ Daniel Zvolenský1. RequirementsWe need to install following softwares:UNetLab: Download the latest version of UNetLab @. It is an.ova file.Ware Player: Download and install the VM Ware Player version 6 or later.

The official source is available at I'm using VMware Workstation 12.0.1 Player for Windows 64-bit operating systems.WinSCP: Download and install WinSCP @Junos vMX v14.1R1: Download Junos vMX.vdi version 14.1R1. The official source is listed below: or there is a 60days testing vMX atPuTTy: Download and install PuTTy @Note:. Virtualbox does not work.2016-November-Virtualbox works too.2016-December: This guide works for Windows 10 64bit, Linux Mint 64 bit.It also works, or allows to run (tested), Cisco 7200 15.4, Junos vMX 12.1, Junos vSRX 15.12. Install the UNetLab via VM Ware Player2.1 Now we will import the unetlab.ova machine, so click on Player = File = Open = Unified Network Lab.ova2.2 Name for the new virtual machine: UNetLabStorage path for a new virtual machine: 2.3 Hit Import and then Accept the license to complete the import of the UNetLab.importing will startafter sucesfull import we may see2.4 Right click = Settings2.5 Adjust processors, memory, network adapters and number of disks.

VMX jinstall vmx 14 1R1 10 domestic from Torrentreactor Software database. VMX/vMX setup guide for Network Engineer.docx: 1.63 Mb; vMX/vMX.ova: 508.98 Mb. Title: vMX jinstall-vmx-14.1R1.10-domestic Download page has been generated for the title above. MX jinstall- vmx- 1. This file is ready for download. Free download Vmx Jinstall-Vmx-14.1R1.10-Domestic programs. VMX jinstall vmx 14 1R1 10 domestic from Torrentreactor Software database.

By default the UNetLab is configured with 1 vCPU, 1GB of and 1 NIC. Finally enable under Processors the Virtualize Intel VT-x/EPT or AMD-V/RVI feature.2.6 Once you are completed with settings hit OK and then Play virtual machine3. 4.1 Hit Enter and type login root and password unl (the password you set at the step 3.2).4.2 after sucesfull login we will update and upgrade system and UNetLab to the latest version, so type:apt-get updateand thenapt-get –y upgrade4.3 If asked for configuration file ‘/etc/issue’. Press Y Yand heit Enter to continue4.4 GRUB install devices. Use SpaceBar and arrow down to mark each package and press Tab and hit Ok to install all three packages.4.5 Writing GRUB to boot device failed – continue? Press Yes Yes.once finished the prompt will apear, then.

The offspring 24 flac. Make sure the openstackrc file is sourced before you run any OpenStack commands.To prepare the OpenStack environment to install vMX, performthese tasks:.Creating the neutron NetworksYou must create the neutron networks used by vMX before youstart the vMX instance. The public network is the neutron networkused for the management (fxp0) network. The WAN network is the neutronnetwork on which the WAN interface forvMX is added.To display the neutron network names, use the neutron net-list command. NoteYou must identify and create the type of networks youneed in your OpenStack configuration.You can use these commands as one way to create the public network:. ExecStart=/usr/bin/neutron-server -config-file /usr/share/neutron/neutron-dist.conf -config-dir /usr/share/neutron/server -config-file /etc/neutron/neutron.conf -config-file /etc/neutron/plugin.ini -config-dir /etc/neutron/conf.d/common -config-dir /etc/neutron/conf.d/neutron-server -config-file /etc/neutron/plugins/ml2/ml2confsriov.ini -log-file /var/log/neutron/server.logUse the systemctl restart neutron-server commandto restart the service.For Ubuntu (starting with Junos OS Release 17.2R1):Edit the /etc/init/neutron-server.conf file as highlighted. Script -x '/usr/bin/neutron-server' exit 0 -r /etc/default/openstack &&.

/etc/default/openstack -r /etc/default/neutron-server &&. /etc/default/neutron-server -r '$NEUTRONPLUGINCONFIG' && DAEMONARGS='$DAEMONARGS -configfile=$NEUTRONPLUGINCONFIG -config-file=/etc/neutron/plugins/ml2/ml2confsriov.ini'Use the service neutron-server restart command torestart the service.

To allow proper scheduling of SR-IOV devices, the computescheduler must use the FilterScheduler with the PciPassthroughFilterfilter.Make sure the PciPassthroughFilter filter is configured in the /etc/nova/nova.conf file on the controller node. Reboot NoteStarting in Junos OS Release 15.1F6 and in later releases,performance mode is the default operating mode. For details, see. NoteEnsure that you have enough physical memory on the computenode. It must be greater than the amount of memory allocated to HugePages because any other applications that do not use Huge Pages arelimited by the amount of memory remaining after allocation for HugePages. For example, if you allocate 24576 Huge Pages and 2M Huge Pagessize, you need 24576.2M or 48G of memory for Huge Pages.You can use the vmstat -s command and look at thetotal memory and used memory values to verify how much memory is leftfor other applications that do not use Huge Pages.

Enable IOMMU in the /etc/default/grub file. Append the inteliommu=on string to any existingtext for the GRUBCMDLINELINUX parameter. To set up the configuration file:. Download the vMX KVM software package from the and uncompress the package.tar xvf package-name. Change directory to the location of the files.cd package-location/openstack/scripts. Edit the vmx.conf textfile with a text editor to create the flavors for a single vMX instance.Based on your requirements, ensure the following parametersare set properly in the vMX configuration file:.re-flavor-name.pfe-flavor-name.vcpus.memory-mbSee for informationabout the parameters.

The parameters required to configure vMX aredefined in the startup configuration file ( scripts/vmx.conf). The startup configuration file generates a file that is used tocreate flavors.

To create new flavors with different vcpus or memory-mb parameters, you must change the corresponding re-flavor-name or pfe-flavor-name parameter beforecreating the new flavors.To customize the configuration, perform these tasks:.Configuring the HostTo configure the host, navigate to HOST and specifythe following parameters:.virtualization-type—Mode of operation;must be openstack.compute—(Optional) Names of the computenode on which to run vMX instances in a comma-separated list. If thisparameter is specified, it must be a valid compute node. If this parameteris specified, vMX instance launched with flavors are only run on thespecified compute nodes.If this parameter is not specified, the output of the nova hypervisor-listcommand provides the list of compute nodes on which to run vMX instances.Configuring the VCP VMTo configure the VCP VM, you must provide the flavor name. NoteWe recommend unique values for the re-flavor-name parameter because OpenStack can create multiple entries with thesame name.To configure the VCP VM, navigate to CONTROLPLANE and specify the following parameters:.re-flavor-name—Name of the nova flavor.vcpus—Number of vCPUs for the VCP; minimumis 1. NoteIf you change this value, you must change the re-flavor-name value before running the script to create flavors.memory-mb—Amount of memory for the VCP;minimum is 4 GB. NoteIf you change this value, you must change the re-flavor-name value before running the script to create flavors.Configuring the VFP VMTo configure the VFP VM, you must provide the flavor name. Basedon your requirements, you might want to change the memory and numberof vCPUs.

See for minimum hardware requirements.To configure the VFP VM, navigate to FORWARDINGPLANE and specify the following parameters:.pfe-flavor-name—Name of the nova flavor.memory-mb—Amount of memory for the VFP;minimum is 12 GB (performance mode) and 4 GB (lite mode). NoteIf you change this value, you must change the pfe-flavor-name value before running the script to create flavors.vcpus—Number of vCPUs for the VFP; minimumis 7 (performance mode) and 3 (lite mode). NoteIf you specify less than 7 vCPUs, the VFP automaticallyswitches to lite mode.

NoteIf you change this value, you must change the pfe-flavor-name value before running the script to create flavors.Creating OpenStack FlavorsTo create flavors for the VCP and VFP, you must execute thescript on the vMX startup configuration file ( vmx.conf). To create OpenStack flavors:. Run the vmxospcreateflavor.py with the startupconfiguration file to generate the vmxospflavors.sh filethat creates flavors./vmxospcreateflavor.py vmx.conf. Execute the vmxospflavors.sh to create flavors.sh vmxospflavors.shInstalling vMX Images for the VCP and VFPTo install the vMX OpenStack glance images for the VCP and VFP,you can execute the vmxospimages.sh script. The scriptadds the VCP image in qcow2 format and the VFP file in vmdk format.

To install the VCP and VFP images:. Download the vMX KVM software package from the and uncompress the package.tar xvf package-name. Verify the location of the software images from the uncompressedvMX package. To start a vMX instance, perform these tasks:.Modifying Initial Junos OS ConfigurationWhen you start the vMX instance, the Junos OS configurationfile found in package-location/openstack/vmx-components/vms/vmxbaseline.conf isloaded. If you need to change this configuration, make any changesin this file before starting the vMX.

NoteIf you create your own vmxbaseline.conf file or move the file, make sure that the package-location/openstack/vmx-components/vms/re.yaml references the correct path. Launching the vMX Instance. To create and start the vMX instance:. Modify these parameters in the package-location/openstack/1vmx.env environmentfile for your configuration. The environment file is in YAML formatstarting in Junos OS Release 17.4R1.netid1—Network ID of the existing neutronnetwork used for the WAN port. Use the neutron net-list command to display the network ID.publicnetwork—Network ID of the existingneutron network used for the management (fxp0) port.

Use the neutron net-list grep public command to display the networkID.fpcimg—Change this parameter to linux-img. Name of the glance image for the VFP; same as the vfp-image-name parameter specified when running the scriptto install the vMX images.vfpimage—Name of the glance image forthe VFP; same as the vfp-image-name parameter specifiedwhen running the script to install the vMX images (applicable forFor Junos OS Releases 17.3R1 and earlier).fpcflav—Change this parameter to linux-flav.