This article lists the minimum requirements for configuring SRX devices in a chassis cluster.
What are the minimum hardware and software requirements for a SRX Chassis Cluster to function properly? Two modes are supported -- Active/Passive and Active/Active. Active/Passive mode is the most commonly used HA mode in which all the traffic is processed by the "Active" or "primary" firewall, while the "Passive" or "Backup" firewall is in a warm standby mode ready to take over as the "Active" firewall in case of failure on the original "Active" firewall. In this mode, there is only two Redundancy Groups (RG). The first one is RG0 which is for "Control Plane", and RG1 is for the "Data Plane". RE is always part for RG0, and on whichever node RG0 is primary, that node is the Primary node. Active/Active mode allows both firewalls to process traffic providing a load sharing HA scenario. In this mode, there can be more than two "Redundancy Groups (RG). The first one is RG0 which is for the "Control Plane", and the other RG's are for the "Data Plane". RE is always part for RG0, and on whichever node RG0 is primary, that node is the Primary node. Only the data plane can work in Active/Active mode because the RE is part of RG0 and only one RE can be active at any given point. For additional information on chassis clustering, refer to Chassis Cluster for Security Devices
Note: Step-by-step configuration instructions are provided in KB15650 - SRX Getting Started - Configure Chassis Cluster (High Availability) [juniper.net] .
The minimum requirements for chassis clustering are:
Hardware:
The hardware on both the devices should be identical. Also, the placement of cards should be identical.
There are a couple exceptions:
Software:
The Junos software version must be the same on both devices.
Verify using this command on both devices:
root@LAB-SRX> show version Hostname: LAB-SRX Model: vsrx Junos: 19.4R2-S1.2
License Keys: There is not a separate license for chassis cluster. However, both firewalls must have the identical features and license keys enabled or installed.
Removal of existing configuration on FXP0 and FXP1:
For help on removing the existing configuration on these interfaces, refer to KB27713 - How to remove references to the interfaces that will be used as fxp0 and fxp1 [juniper.net] .
Additional requirements for the control plane, control link, data plane and data link are provided below:
2020-09-26: Added SRX345 in the exception stanza and updated latest CLIi o/p.