Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Understanding Chassis Cluster Formation

To form a chassis cluster, a pair of the same kind of supported SRX Series devices are combined to act as a single system that enforces the same overall security. SRX1400 has dedicated slots for each kind of cards which cannot be interchanged. For SRX5400, SRX5600 and SRX5800 chassis clusters, the placement and type of Services Processing Cards (SPCs) must match in the two clusters. For SRX3400 and SRX3600 chassis clusters, the placement and type of SPCs, I/O cards (IOCs), and Network Processing Cards (NPCs) must match in the two devices.

For SRX Series branch devices (SRX100, SRX210, SRX220, SRX240, SRX550, and SRX650), although the devices must be the same kind, they can contain different Physical Interface Modules (PIMs).

Note: For SRX210 Services Gateways, the base and enhanced versions of a model can be used to form a cluster. For example: SRX210B and SRX210BE SRX210H and SRX210HE However, the following combinations cannot be used to form a cluster: SRX210B and SRX210H SRX210B and SRX210HE SRX210BE and SRX210H SRX210BE and SRX210HE

When a device joins a cluster, it becomes a node of that cluster. With the exception of unique node settings and management IP addresses, nodes in a cluster share the same configuration.

You can deploy up to 255 chassis clusters in a Layer 2 domain. Clusters and nodes are identified in the following way:

• A cluster is identified by a cluster ID (cluster-id) specified as a number from 1 through 255. Setting a cluster ID to 0 is equivalent to disabling a cluster. Cluster ID greater than 15 can only be set when the fabric and control link interfaces are connected back-to-back.

  Note: If you create a cluster with cluster IDs greater than 16, and then decide to roll back to a previous release image that does not support extended cluster IDs, the system comes up as standalone.

  Note: If you have a cluster set up and running with an earlier release of Junos OS, you can upgrade to Junos OS Release 12.1X45-D10 and re-create a cluster with cluster IDs greater than 16. However, if for any reason you decide to revert to the previous version of Junos OS that did not support extended cluster IDs, the system comes up with standalone devices after you reboot. However, if the cluster ID set is less than 16 and you roll back to a previous release, the system will come back with the previous setup.

• A cluster node is identified by a node ID (node) specified as a number from 0 to 1.