Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Chassis Cluster Control Plane Interfaces

You can use control plane interfaces to synchronize the kernel state between Routing Engines on SRX Series devices in a chassis cluster. Control plane interfaces provide the link between the two nodes in the cluster.

Control planes use this link to:

  • Communicate node discovery.

  • Maintains session state for a cluster.

  • Access the configuration file.

  • Detect liveliness signals across the nodes.

Example: Configure Chassis Cluster Control Ports for Control Link

This example shows how to configure chassis cluster control ports on these devices: SRX5400, SRX5600, and SRX5800. You need to configure the control ports that you will use on each device to set up the control link.

Requirements

Before you begin:

Overview

Control link traffic passes through the switches in the Services Processing Cards (SPCs) and reaches the other node. On SRX Series devices, chassis cluster ports are located at the SPCs in the chassis cluster. By default, all control ports on SRX5400 devices, SRX5600 devices, and SRX5800 devices are disabled. To set up the control links, you connect the control ports, configure the control ports, and set up the chassis cluster.

This example configures control ports with the following Flexible PIC Concentrators (FPCs) and ports as the control link:

  • FPC 4, port 0
  • FPC 10, port 0

Configuration

Procedure

CLI Quick Configuration

To quickly configure this section of the example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit in configuration mode.

Step-by-Step Procedure

To configure control ports as the control link for the chassis cluster:

Specify the control ports.

Results

In configuration mode, confirm your configuration by entering the show chassis cluster command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

For brevity, this show command output includes only the configuration that is relevant to this example. Any other configuration on the system has been replaced with ellipses (...).

After you configure the device, enter commit in configuration mode.

Verify the Chassis Cluster Status

Purpose

Verify the chassis cluster status.

Action

In operational mode, enter the show chassis cluster status command.

Meaning

Use the show chassis cluster status command to confirm that the devices in the chassis cluster are communicating with each other. The preceding output shows that chassis cluster is functioning properly, as one device is the primary node and the other is the secondary node.

Verify Chassis Cluster Control Plane Statistics

Purpose

Display chassis cluster control plane statistics.

Action

At the CLI, enter the show chassis cluster control-plane statistics command:

Clear Chassis Cluster Control Plane Statistics

To clear displayed chassis cluster control plane statistics, enter the clear chassis cluster control-plane statistics command at the CLI:

SCB Chassis Cluster Control Links

For SRX series devices SRX5400, SRX5600, and SRX5800, you can connect the control links in a chassis cluster using the Switch Control Board (SCB) chassis cluster control ports.

Increase the resiliency of the chassis cluster by separating chassis cluster control links from Services Processing Card (SPC).

The SCB chassis cluster control link path is independent of SPCs. The SPC failures do not affect the chassis cluster control link.

The supported 10-Gigabit (Gb) SFPP connections on the SCB external 10-Gigabit Ethernet (10GbE) ports are as follows:

  • SCB2 chassis cluster port: SFPP-10GE-LR, SFPP-10GE-SR, SFPP-10GE-LRM

  • SCB3 chassis cluster port and SCB4 chassis cluster port: SFPP-10GE-LR, SFPP-10GE-SR

Figure 1: SCB Chassis Cluster Control Link Path SCB Chassis Cluster Control Link Path

The control port connections on the chassis cluster are as follows:

  • Chassis cluster control port 0 is on SCB0.

  • Routing Engine 0 is on SCB0.

  • SCB chassis cluster port 0 is used to replace SPC chassis cluster port 0.

Change from Chassis Cluster to Standalone Mode

Change from cluster mode to standalone mode when using single primary control link.
  1. Disable the chassis cluster and reboot the devices to enter the standalone mode.
  2. Enable the chassis cluster and reboot the devices to enter the chassis cluster mode.

Example: Configure Control Ports Using the SCB Control Link

This example shows how to configure a chassis cluster with two standalone nodes using a single SCB control link.

Requirements

Before you begin:

Overview

Configure the control ports that you will use on each device to set up the control link.

You must not configure the following control links at the same time:

  • SPC and SCB primary control links

  • SPC and SCB secondary control links

Configuration

Procedure

To configure a chassis cluster using a single SCB control link:

  1. Connect an SCB control link cable between the SCB0 chassis cluster control ports on node 0 and node 1.

  2. Configure an SCB control port (primary control link) on node 0 and node 1.

  3. Reboot node 0.

  4. Reboot node 1.

Results

In configuration mode, confirm your configuration by entering the show chassis cluster command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

For brevity, this show command output includes only the configuration that is relevant to this example.

After you configure the device, enter commit from configuration mode.

Verification

Verify the Chassis Cluster Status

Purpose

You can verify the chassis cluster status and run the show chassis fpc pic-status command to ensure that the FPCs are online.

Action

In operational mode, enter the show chassis cluster status command.

In operational mode, enter the show chassis fpc pic-status command.

In operational mode, enter the show chassis cluster control-plane statistics command to view the statistics of the control link used by chassis cluster traffic.

Meaning

Use the show chassis cluster control-plane statistics command to view the control link statistics and fabric link statistics exchanging heartbeats.

Transition from SPC to SCB with a Single Control Link

This example provides steps for the chassis cluster control link transition from a single SPC control link to a single SCB control link concurrently.

Requirements

Before you begin:

Overview

After completing the control link transition, ensure that you disconnect the SPC control link cables that existed before the control link transition. You must disconnect the secondary SCB control cable when you configure only the primary control link.

Configuration

Procedure

To transition from SPC to SCB control links concurrently:

  1. During a single control link transition, heartbeats may be missing for a short time. The secondary node may detect the missing heartbeats and go into an ineligible state. To prevent the secondary node from entering an ineligible state, configure it to extend the control link heartbeat timeout from 3 seconds (the default) to 16 seconds.

  2. Disable the SCB 0 chassis cluster control port on the primary node using the operational command.

  3. Verify the SCB 0 chassis cluster control port status on the primary node.

  4. Enable the SCB 0 chassis cluster control port on the secondary node.

  5. Verify the SCB 0 chassis cluster control port status on the secondary node.

  6. Connect the SCB primary control link cable.

  7. Transition from the SPC control link to the SCB control link on the primary node by disabling SPC chassis cluster port 0 on the primary node and enabling SCB chassis cluster port 0 on the primary node. Here the SPC slot number is the one on which the SPC chassis cluster control port is configured.

  8. Delete the SPC primary control link configuration.

  9. Configure the SCB primary control link.

  10. Verify that the control link is up, using the show chassis cluster interfaces command.
  11. Delete the control link heartbeat timeout.

  12. Disconnect the SPC primary control link cable.

Transition from SCB to SPC with a Single Control Link

This example shows how to configure a control link transition from an SCB control link to an SPC control link.

Requirements

Before you begin:

Configuration

Procedure

To transition from an SCB control link to an SPC control link concurrently:

  1. During a single SCB control link transition, heartbeats may be missing for a short time. The secondary node may detect the missing heartbeats and enter an ineligible state. To prevent the secondary node from entering an ineligible state, configure it to extend the control link heartbeat timeout from 3 seconds (the default) to 16 seconds.

  2. Disable SPC chassis cluster control port 0 on the primary node. fpc 4 is the local slot number on which the chassis cluster control port will be configured later.

  3. Enable SPC chassis cluster control port 0 on the secondary node. fpc 4 is the local slot number on which the chassis cluster control port will be configured later.

  4. Connect the SPC primary control link cable.

  5. Transition from the SCB control link to the SPC control link by disabling SCB chassis cluster control port 0 on the primary node and enabling SPC chassis cluster port 0 on the primary node. Here the SPC slot number is the one on which the SPC chassis cluster control port will be configured.

  6. Delete the primary SCB control link configuration.

  7. Configure the primary SPC control link.

  8. Verify if the control link is up, using the show chassis cluster interfaces command.

  9. Delete the control link heartbeat timeout.

  10. Disconnect the SCB primary control link cable.

Release History Table
Release
Description
19.3R1
Starting in Junos OS Release 19.3R1, the SRX5K-RE3-128G is supported along with SRX5K-SPC3 on the SRX5000 series devices. The control interfaces ixlv0 and igb0 are used to configure SRX5K-RE3-128G.Control links control the communication between the control, and data plane and the heartbeat messages.