Supported Platforms
Related Documentation
- J Series
- Node Interfaces on Active J Series Chassis Clusters
- J, SRX Series
- Management Interface on an Active Chassis Cluster
- Fabric Interface on an Active Chassis Cluster
- Control Interface on an Active Chassis Cluster
- Disabling Chassis Cluster
- SRX Series
- Node Interfaces on Active SRX Series Chassis Clusters
- Additional Information
- Chassis Cluster Feature Guide for Security Devices
Results of Enabling Chassis Cluster
After wiring the two devices together as described in Connecting SRX Series Devices to Create a Chassis Cluster or Connecting J Series Devices to Create a Chassis Cluster, you use CLI operational modecommands to enable chassis clustering by assigning a cluster ID and node ID on each chassis in the cluster. The cluster ID is the same on both nodes.
 | Note: For SRX5400, SRX5600 and SRX5800 devices, you must configure the control ports before the cluster is formed. |
To do this, you connect to the console port on the primary device, give it a node ID, and identify the cluster it will belong to, and then reboot the system. You then connect the console port to the other device, give it a node ID, and assign it the same cluster ID you gave to the first node, and then reboot the system. In both instances, you can cause the system to boot automatically by including the reboot parameter in the CLI command line. (For further explanation of primary and secondary nodes, see Understanding Chassis Cluster Redundancy Groups.)
| Note: On SRX210, SRX220, SRX240, SRX550, and SRX650 devices, Layer 2 Ethernet switching is supported in chassis cluster mode. |
 | Caution: After fabric interfaces have been configured on a chassis cluster, removing the fabric configuration on either node will cause the redundancy group 0 (RG0) secondary node to move to a disabled state. (Resetting a device to the factory default configuration removes the fabric configuration and thereby causes the RG0 secondary node to move to a disabled state.) After the fabric configuration is committed, do not reset either device to the factory default configuration. |
FPC Slot Numbering in an SRX Series Chassis Cluster (SRX5800 Devices) shows how the FPC slots are numbered on two nodes in an SRX5000 line chassis cluster. Other figures show slot numbering on both nodes in other SRX Series chassis clusters. PIM Slot Numbering in a J Series Chassis Cluster (J6350 Devices) shows how the PIM slots are numbered on two nodes in a J Series chassis cluster.
Related Documentation
- J Series
- Node Interfaces on Active J Series Chassis Clusters
- J, SRX Series
- Management Interface on an Active Chassis Cluster
- Fabric Interface on an Active Chassis Cluster
- Control Interface on an Active Chassis Cluster
- Disabling Chassis Cluster
- SRX Series
- Node Interfaces on Active SRX Series Chassis Clusters
- Additional Information
- Chassis Cluster Feature Guide for Security Devices
Published: 2014-07-18
Supported Platforms
Related Documentation
- J Series
- Node Interfaces on Active J Series Chassis Clusters
- J, SRX Series
- Management Interface on an Active Chassis Cluster
- Fabric Interface on an Active Chassis Cluster
- Control Interface on an Active Chassis Cluster
- Disabling Chassis Cluster
- SRX Series
- Node Interfaces on Active SRX Series Chassis Clusters
- Additional Information
- Chassis Cluster Feature Guide for Security Devices
