Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Understanding Chassis Cluster Dual Control Links

Dual control links, where two pairs of control link interfaces are connected between each device in a cluster, are supported for the SRX5000 and SRX3000 lines. Having two control links helps to avoid a possible single point of failure.

For the SRX5000 line, this functionality requires a second Routing Engine, as well as a second Switch Control Board (SCB) to house the Routing Engine, to be installed on each device in the cluster. The purpose of the second Routing Engine is only to initialize the switch on the SCB.

For the SRX3000 line, this functionality requires an SRX Clustering Module (SCM) to be installed on each device in the cluster. Although the SCM fits in the Routing Engine slot, it is not a Routing Engine. SRX3000 line devices do not support a second Routing Engine. The purpose of the SCM is to initialize the second control link.

For SRX1400 devices, ports 10 and 11 on the SYSIO can be configured as dual control links. When the devices are not in cluster mode, these ports can be used as revenue ports.

Note: For the SRX5000 line, the second Routing Engine must be running Junos OS Release 10.0 or later. For the SRX3000 line, the cluster must be running Junos OS Release 10.2 or later (the SCM is not supported in earlier releases and might be incorrectly recognized). For SRX1400 Services Gateways, the cluster must be running Junos OS Release 11.1 or later.

The second Routing Engine, to be installed on SRX5000 line devices only, does not provide backup functionality. It does not need to be upgraded, even when there is a software upgrade of the master Routing Engine on the same node. Note the following conditions:

  • You cannot run the CLI or enter configuration mode on the second Routing Engine.
  • You do not need to set the chassis ID and cluster ID on the second Routing Engine.
  • You need only a console connection to the second Routing Engine. (A console connection is not needed unless you want to check that the second Routing Engine booted up or to upgrade a software image.)
  • You cannot log in to the second Routing Engine from the master Routing Engine.

Note: As long as the first Routing Engine is installed (even if it is rebooting or failing), the second Routing Engine cannot take over the chassis mastership; that is, it cannot control all the hardware on the chassis. The second Routing Engine can only become the master when the master Routing Engine is not present.

 

Related Documentation

 

Published: 2013-11-11

Previous Page Next Page