Yeah, I can grab 16.2R2 sometime tonight, and upload it to your server. I need to stay up all night finishing something urgent anyway.
vQFX is an awful lot like vMX, in that we have two VMs that we need to connect together. The vRE runs Junos (I'm curious if I can run 2 Junos instances at once, since that's standard on the physical switches), and then we;ve also got a vPFE that run Wind River Yocto Linux.
Here's what the software setup looks like, on the real QFX-10K switches:
Remember how I said in that setup guide for GNS3, to leave the interfaces set to Eth0, Eth1,Eth2, etc..., since GNS3's interface naming schema gets weird, when you have edge cases like vMX and vQFX?
You still need to connect Eth0 of both VMs to a dumb switch, since that's the mgmt interface. Then, you also cross-connect Eth1 of both VMs to each other, since that's the internal em1 interface that the routing engine and packet forwarding engine still use to communicate with each other. This time, though, we also need to leave Eth2 alone, since it's the internal em2 interface, which the active and standby Junos instances use to talk to each other. You connect the topology devices to the vRE starting with Eth3, which is xe-0/0/0, Eth4 is xe-0/0/1, and so on. I only assign the vPFE 2 interfaces, and give the vRE at least 13. We don't have to use virtio-net-pci this time, though.
Here's the setup I used (with KVM):
vPFE - 2 adapters, 2GB RAM, x86_64 qemu, only 1 vCPU. That pfe vmdk file from June 9th of 2016 still works.
vRE - 15 adapters, 1GB RAM, x86_64 qemu, and 2 vCPUs. You can either stick to the original 15.1X53-D60 KVM release, or get the Vagrant file of 15-1X53-D63, and double-extract it with 7zip, to get a usable vmdk file. The KVM file version of 15-1X53-D63 is/was busted, and used to crash constantly. You can always use the two original KVM files, if you feel like. I already have the three files, so I can upload those to your server, too.
I'd honestly increase the RAM and vCPU allocations for both VMs though, and definitely set the pfe to lite-mode. This thing takes a LOT longer than vMX to load up, and it always has. We're talking "start it up, and either walk the dogs, or go eat a sandwich".
You'll also likely need to delete dhcp from the xe-0/0/x interfaces, since I think it's set by default.
EDIT: One of these days, I'm going to see if I can get Master and Standby Junos instances running in both vMX and vQFX. I helped someone get two logical systems to connect and talk to each other, in the same VM a couple of weeks ago. I might need to make an Ubuntu server VM, and compile and install vMX in it, instead of running it in GNS3 via Qemu, since the images folder has a TON of files in there.
Edited by HermanToothrot, 27 July 2017 - 09:41 PM.