Similar to VMX , have tested VQFX image and I have to say, the whole setup process is a pain.  Full feature testing related to DCX is not done but here are some points


-> Any simulator which can run qcow2, I have apparently used UNETLAB

-> 8GB Ram (technically you can get away with even less) and 6 VCPU’s

-> vqfx10k-pfe-20160609-2.vmdk and vqfx10k-re-15.1X53-D60.vmdk – Two instances for the boot.


The procedure of uploading to EVE-NG is fairly easy and can be found in many websites so i wont be stressing on it, If anyone wants this to be blogged let me know, but it is straight forward.





RE settings that I have used are as follows, not changed much made CPU 4 , increased RAM to 4096 and edited ethernet ports to 6. PFE Settings are left as usual.



Note – From here, it would take nearly 40 minutes for you to just leave the system, it took a near to 40 minutes for me for FPC to become online. All through I was troubleshooting out of nothing from the instance start of 10 minutes which yielded nothing.

After all the wait, commit is not what you compare with VMX, a commit would take more than 30 seconds in some cases, while since we do not have a better option other than this, i guess we have to live with it. I tried the one in ESXI Instance, problem with that one is the scaling, its not easy as an emulator drag and drop and you have to go about editing virtual-switches to expand the topology.


All in all, its a pain till it is developed similar to VMX but should be able to help JNCIX-DC Preparation. I have run sample OSPF Between VQFX 10GIG and VMX 1Gig and didnt had any problems.


Ping is not at the greatest times as we are running in a emulator mode, I will be labbing a lot more on VQFX shortly and will also testing out the vagrant version of it to document more