Chassis clustering provides network node redundancy by grouping a pair of the same kind of supported SRX-series devices or J-series devices into a cluster. The devices must be running JUNOS software. The control ports on the respective nodes are connected to form a control plane that synchronizes configuration and kernel state to facilitate the high availability of interfaces and services. Similarly, the data plane on the respective nodes is connected over the fabric ports to form a unified data plane. The fabric link allows for the management of cross-node flow processing and for the management of session redundancy.
The control plane software operates in active/backup mode. When configured as a chassis cluster, the two nodes back up each other, with one node acting as the primary device and the other as the secondary device, ensuring stateful failover of processes and services in the event of system or hardware failure. If the primary device fails, the secondary device takes over processing of traffic.
The data plane software operates in active/active mode. In a chassis cluster, session information is updated as traffic traverses either device and this information is transmitted between the nodes over the fabric link to guarantee that established sessions are not dropped when a failover occurs. In active/active mode, it is possible for traffic to ingress the cluster on one node and egress from the other node.
![]() |
Note: For an SRX-series chassis cluster, the fabric interfaces can also be connected over 10-Gigabit Ethernet links. |
![]() |
Note: For an SRX 5600 or SRX 5800 chassis cluster, nodes must be interconnected with a fiber optic cable. |
Chassis cluster functionality includes: