Praise on Juniper vMX – Getting Started Guide PerformX Testo Review on MTU settings on Junos & IOS (part 1) Bhoomi on Juniper vMX – Getting Started Guide (VMware).
According to Unetlab, Unetlab support the following version vMX: 14.1R1.10-domestic and 14.1R4.8-domestic I can get the 14.1R1.10 easily from Internet. However, I can’t find a packaged 14.1R4.8 image for Unetlab. I went to Unetlab and ask for help. Unfortunately, nobody responded me. As I need to use the newer version for my eVPN lab (eVPN HA), I had to try my own best to get one.
I downloaded the 14.1R4.8 doemestic img file from Internet: jinstall-vmx-14.1R4.8-domestic.img Interestingly, I used CLI qemu-img and found that the Juniper image file is qcow2 format! [ root@localhost tmp]# qemu-img info jinstall-vmx-14.1R4.8-domestic.img grep file.format file format: qcow2 Like adding a normal image, I created a new folder /opt/unetlab/addons/qemu/vmx-14.1R4.8.
Then uploaded the file “jinstall-vmx-14.1R4.8-domestic.img” to this newly created folder and renamed the files as “hda.qcow2”. Till now, in the Unetlabe GUI, I am able to select this new Junos version for my vMX. Although I can power on this new version vMX, I still can’t really use it for my eVPN lab. The reason is: Since 14.1R4, Juniper vMX will try to connect to a remote PFE, which means a different virtual machine as PFE. To change this default behaviour and use local PFE, I need to add a new line vm_local_rpio=”1″ to /boot/loader.conf and save the file. The change need reboot to take effect. After reboot, I am able to use this new Juniper vMX in my eVPN lab.
I’m excited to finally have the opportunity to play with Juniper’s vMX! Since it was announced last year I’ve been eagerly waiting for release – a couple of client projects already have passed by where the vMX would have been a perfect fit. vMX already won an earlier this year at Interop Tokyo 2015! In this post I’ll be giving a bit of background on the vMX architecture and licensing, and then go on to walk through a lab based configuration of vMX. The vMX is a virtual MX Series Router that is optimized to run as software on x86 servers. Alezhka izlozhenie po belaruskaj move. Like other MX routers, it runs Junos, and Trio has been compiled for x86!
Kak sdelatj dinamometr svoimi rukami iz linejki. Yes, that means the sophisticated L2, L2.5 and L3 forwarding features we are used to on the MX are present on the vMX. Architecture vMX can be installed on server hardware of your choice, so long as it is x86 based and running Linux (although I’m sure a version to run on vmware won’t be too far away). VMX itself actually consists of two separate VMs – a virtual forwarding plane (VFP) running the vTrio, and a virtual control plane (VCP) running Junos. The Linux virtualisation solution KVM is what Juniper are using to spin up the virtual instances of the control and forwarding planes, and multiple instances of vMX can be run on the same hardware. To see Juniper using Linux and KVM is no surprise as this is what we are used to on Juniper’s other products such as the QFX.
The VMs are managed by a simple orchestration script which is used to create, stop and start the vMX instances. A simple configuration file defines parameters such as memory and vCPUs to allocate to the VCP and VFP. A couple of Linux bridges are created by the orchestration script. Clearly VCP and VFP need to be able to communicate directly so an “internal” bridge is automatically created for each vMX instance to enable this communication.
An “external” bridge is also created, this is used to enable the management interface on the Linux Physical host to be used for the virtual management interfaces on the VCP and VFP. For data interfaces, there are a couple of techniques available for packet I/O depending on the required vMX throughput – • Paravirtualisation using KVMs virtio drivers • PCI passthrough using single root I/O virtualisation (SR-IOV), enabling packets to bypass the hypervisor and therefore increase I/O. Juniper recommend virtio or SR-IOV up to 3Gbps, and SR-IOV over 3Gbps (using a minimum of 2 x 10GE interfaces). Which you will choose will ultimately depend on your use case for the vMX. Licensing Now this is what I really like about vMX!