Hi all,

today I’m gonna show you how to implement MC-LAG on the vQFX (QFX10k codebase) on EVE-NG. I personally found this pretty straight forward to configure but since I recieved so many Mails asking me to show this, I will do.

Here’s the very simple Topology (click to enlarge):

And here’s the Code – as you can see it’s not that hard but you have to remember some things:

When configuring MC-LAG always remember that the following settings must match on both Members of the MC-LAG:

LACP System-ID + Key
MC-AE ID + Mode
VLAN’s (ICL and Member VLAN’s)

The following settings must be unique for each Member of the MC-LAG:

MC-AE Chassis-ID + Status Control
ICCP IP (Local) and Peer IP (who would have guessed this…)
MC-LAG Protection 

I will give you more explanation on this Topic later because as you might have heard my JNCIE-DC is booked for the 14th of February (therefore not so much time to write detailed Blogposts) and time is slowly running away… Okay just kidding – time just took a SPRINT towards my deadline… However, my beard looks fine so far…

The final Countdown for the JNCIE-DC

Just 38days of labbing until the JNCIE-DC Exam-Day has arrived.
Exam is already booked and I am so excited to do this (way more than with the first JNCIE because I already know what awaits me in terms of the trip to Amsterdam, the Exam-Room etc.) – and I feel way more confident about the Topics (EVPN really kicks ass) πŸ˜‰

I would love to share some EVE-NG Topos – however, I only work with the official inetZero Superlabs this time and therefore can’t legally share anything.

After the Exam I will try to develop some Training to share for the SEC and DC-Exams to prep you for the final day – in the meantime –> stay tuned πŸ˜‰

vQFX 17.4R1.16 on EVE-NG (Professional and Community)

Hi all,

a couple of days the new vQFX came out in Version 17.4R1.16 – and you know me – of course it had to be “eved” πŸ˜‰
Here’s how I got it flying:


1.) Create a new folderstructure for your new vQFX:

2.) Move your files (extracted from vbox) to the new folders:

To get the vmdk you need to download the “Vagrant” Virtualbox-Files and extract them twice with 7zip to uncover the vmdk’s
You start with the .tgz, extract this, get a file without an extension and extract this again (all with 7zip)

3.) Convert the vmdk (PFE and RE) to qcow2-format:

And now you can spin-up your new vQFX17.1R1.16 under EVE-NG πŸ˜‰

Enjoy – if you have questions feel free to ask in the comment section below.

JunOS Service restart via cronjob

Some days ago we had trouble on one of our QFXes where the jdhcpd deamon would consume 100% CPU and “crash” – resulting in users not getting IP’s anymore.
While TAC is still investigating, I made a quick Workaround for this – the DHCP-Sheriff πŸ˜‰


This Script restarts the Service if the load of the Service is above 1% (adjustable) – this can be easily adopted to other services and thresholds.

1.) Login as root and in shell type: vi /var/tmp/

2.) Press “i” and paste the above lines, followed by “[Esc-Button]”. Save and Quit with :wq

chmod +x /var/tmp/

crontab -e
0 */8 * * * sh /var/tmp/ (executes it every 8h)


crontab -l
0 */8 * * * sh /var/tmp/

6.) in cli check after job has finished to run via show log dhcp-sheriff.log


Feel free to use this to your advantage – hopefully this will be a workaround for you in urgent-times until a fix is released.
This is only a workaround – do not use this in production for a long time / use at your own risk.

OSPF between a vSRX-Cluster and a standalone vSRX over vQFX on EVE-NG

I promised to deliver this and here it is: OSPF over vQFX πŸ˜‰
These days I lab a lot with EVE and I love it more every day – the possibilities are endless and the Labs are very very quick configured and running. With 2 new CPU’s my EVE now runs with decent Speed so compared to VMware ESX 6.0 there is no extreme performance difference anymore. I can live with that. Since D63 on the vQFX is running very stable and smooth I thought of this small OSPF Lab – I will add more “Quick-Labs” in the Future.

The SRX in Clustermode runs very well on EVE – however there is an optical error. If you build a Cluster, the interface mappings on EVE are completely wrong. This is due to the SRX getting a new interface (em0) as second interface Card – so if you select ge-0/0/0 in EVE, you really select em0.

But why is that you will ask? The answer is simple:
EVE is not aware of Cluster-Naming or Cluster Interfaces – so you have to think twice, what you have to select – I needed Wireshark to see what happened…
From top down the first Interface in EVE is fxp0, the second Interface is em0, the third is ge-0/0/0 or 7/0/0, the fourth is ge-0/0/1 or 7/0/1 and so on (see the Table below from Juniper):

Once I figured that out I could successfully build the Cluster (this time fully working, not just partially) and here is the Lab:



vSRX-NG5+6 (the SRX-Cluster):



vSRX-NG7 (the standalone SRX):



Lab-C01 (Coreswitch 01, vQFX running 15.1X53-D63.9):



Lab-C02 (Coreswitch 02, vQFX running 15.1X53-D63.9):


Download this Lab for your EVE here: (Size 16kB, zip-Archive)