2020-09-29

uniper vMX and GNS3+QEMU Setup
N 9, 2016 • 38 Likes • 6 CommentsJade DeaneCloud & Network Architect, Engineer, DeveloperBackstoryDuring a recent design session on a new platform that will use Juniper OpenContrail for overlay networking, my team and I found ourselves revisiting design decisions from a previous and now production OpenContrail environment.While we’ll eventually complete a full lab validation of our design from bare metal to containers and our gateway of choice, the Juniper MX there are some basic conceptual ideas we need to play around with immediately.We’re rather used to Cisco’s VIRL, which works tremendously well for template based automated and collaborative workflows in reasonably scaled topologies, but sometimes one just needs to manually and methodically work through a concept from scratch. In this case, enter the Juniper vMX and GNS3.An Olive By Any Other NamePresumably you’re already familiar with the Juniper vMX, or in a previous life the good ol’ Olive. For those not fully aquatinted it’s a virtual Junos router available at https://www.juniper.net/support/downloads/?p=vmx, and alternatively https://www.juniper.net/us/en/dm/free-vmx-trial/. For a great and authoritative introduction to the vMX please take a look at http://matt.dinham.net/juniper-day-one-vmx-running/.With vMX 14.1R4 and later the VCP (Virtual Control Plane) and VFP (Virtual Forwarding Plane) run as separate VMs. This is owning to the new distributed forwarding nature of vMX. Unfortunately the old “local PFE” trick of adding “vm_local_rpio=1” to “/boot/loader.conf” no longer applies.Template and Topology SetupFor this guide I’ve used vMX 15.1F6.9 running on GNS3 1.5.2 with QEMU 2.5.0.Start by creating two new VM templates for the VFP and VCP respectively, using whatever means you prefer within the GNS3 GUI.Unpack your vMX tarball and look inside the images directory. For the VFP you’ll find a single “vFP” prefaced image filename. Be sure you use paravirtualized network I/O for your network adapters (“virtio-net-pci”).斜体样式For the VCP there are three images required. Pay note to the order in which they’re added to the VM template. If you fail to add the metadata image you’ll see the VCP VM type listed as an “Olive”, rather than “vMX”.Create a topology with a VFP, VCP, and another router to test data-plane forwarding.The VCP and VFP first interfaces, em0 and ext respectively are your typical management links. Their second interfaces, em1 and int respectively are the interfaces they use for intra logical vMX communication, and your physical MX RE interface analog.The third interface and beyond off the VFP will be your vMX’s forwarding interfaces. I believe the limit here is 10. These will be the interfaces your logical vMX uses to forward traffic on, enumerated as “ge-”.TestingFire the devices up and after a little while you’ll see the interfaces come up on your VCP.If you don’t see these interfaces first validate your template and topology setup, and then confirm the VCP and VFP can talk. By default the VFP’s int interface will use 128.0.0.16/8, while the VCP’s side will be 128.0.0.1/8.If you’re able to ping between the vMX’s nodes but don’t see interfaces come online try restarting the VCP’s FPC (“request chassis fpc restart”), and then restarting the VCP’s chassis management process (“restart chassis-control”). Carefully review the VFP’s syslogs for an indication on where things are breaking down.Finally with everything working apply a basic interface configuration and test.I sincerely hope you found this information helpful.发布者:Jade DeaneCloud & Network Architect, Engineer, DeveloperTook a few moments to write-up a quick and simple how-to for running Juniper’s vMX in GNS3+QEMU. Hope you or someone you know finds this helpful!6 commentsSign in to leave your commentTorkis Halomoan DaulayNetwork Engineer at Lintasartawhat is the minimum ram specifications?赞回复8 个月Adrian G