Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Preparing Your Equipment for Chassis Cluster Formation

 

To form a chassis cluster, a pair of the same kind of supported SRX Series devices is combined to act as a single system that enforces the same overall security. SRX Series devices must meet the following requirements to be included in a chassis clusters.

To form a chassis cluster, a pair of the same kind of supported SRX Series devices is combined to act as a single system that enforces the same overall security.

  • The network node redundancy is achieved by grouping a pair of the same kind of supported SRX Series devices into a cluster.

  • SRX Series devices must be the same model.

  • Junos OS requirements: Both the devices must be running the same Junos OS version

  • Licensing requirements: Licenses are unique to each device and cannot be shared between the devices. Both devices (which are going to form chassis cluster) must have the identical features and license keys enabled or installed them. If both devices do not have an identical set of licenses, then after a failover, that particular licensed feature might not work or the configuration might not synchronize in chassis cluster formation.

  • All services processing cards (SPCs), network processing cards (NPCs), and input/output cards (IOCs) on applicable SRX Series devices must have the same slot placement and must be of same type. Example:

    • For SRX5400, SRX5600 and SRX5800 chassis clusters, the placement and the type of services processing cards (SPC, SPC2, SRX5K-SPC3), and input/output cards (IOC1, IOC2, IOC3, IOC4) must match in two devices. Only SCB4 is not supported on SRX5400. All other components are supported on SRX5400.

    • For SRX3400 and SRX3600 chassis clusters, the placement and the type of SPCs, input/output cards (IOCs, NPIOCs), and network processing cards (NPCs) must match in two devices.

    You can use the show chassis hardware command to identify the type of the card.

    Following example shows the placement and the type of cards used in a chassis cluster setup:

  • SRX1500—Has dedicated slots for each kind of card that cannot be interchanged.

  • SRX4600—Has dedicated slots for each kind of card that cannot be interchanged.

  • SRX300, SRX320, SRX340, SRX345, SRX380, and SRX550M—Although the devices must be of the same type, they can contain different Physical Interface Modules (PIMs).

  • The control ports on the respective nodes are connected to form a control plane that synchronizes the configuration and kernel state to facilitate the high availability of interfaces and services.

  • 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.

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