Caveat: Clustering on Juniper SRX with EVE

Caveat: Clustering on Juniper SRX with EVE

For SRX to support clustering, here are few things to keep in mind 

The SRX in Cluster mode runs fairly well on EVE , however the interface mappings on EVE is different than regular. 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.

EVE is platform and is Clustering unaware. So you will have to tweak a few things 

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)



Note: Credits to jncie.eu for finding and documenting this Caveat



    • Related Articles

    • Do you provide IOU/IOL for EVE-NG Hosted Service?

      No. However, if you have the image, you can upload it yourself after you sign Liability Waiver form
    • Setting up Nexus 9000v with Username and Password

      Premise: This article Focuses on setting up the username and password on Cisco Nexus 9000v This Article Applies to All the Subscribers using GNS3,VIRL, EVE/ESXI 1. Once the device is booted up ) It can take up to 5 mins for the device to completely ...
    • How to make the Cisco Access Points work with Hosted EVE-NG on Cloudmylab platform

          Purpose The purpose of this document is to help cloudmylab Customers and partners to set up a base Cisco Wireless Lab   Pre-Requisites 1.       WLC version 8.5.X 2.       AP version 15.3.3 JF 1 or higher 3.       AP 3502i   Refer to the WLC ...
    • EVE-NG Community VS EVE-NG Pro

      FEATURE EVE-NG COMMUNITY EVE-NG PRO Wireshark Capture Local Wireshark Capture Integrated Wireshark Capture Lab Timer Not supported Timer for lab training Running Labs Not supported User can run multiple labs together Node limit per lab 63 1024 ...
    • Devices are not booting up. What should I do?

      Sometimes the device image can get corrupted. In that case, simply wipe your node/device and refresh your topology. This brings back the device to its base configuration.