Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Example: Setting the Node ID and Cluster ID

This topic provides steps to configure and assign the cluster ID for the nodes in the chassis cluster.

When a device is added to a cluster, it becomes a node within that cluster. All nodes share a common configuration, except for:

  • Node‑specific settings

  • Management IP addresses

A cluster is identified by a cluster ID (cluster-id), which is a numeric value from 1 to 255.

  • Setting the cluster ID to 0 disables clustering.

  • Cluster IDs from 1 to 15 can be configured without special connectivity requirements.

  • Cluster IDs greater than 15 require additional network constraints:

  • The fabric and control link interfaces must be:

  • Connected back-to-back, or

  • Connected on separate VLANs

To use extended cluster IDs without back-to-back connectivity:

  • Control and fabric link traffic for each firewall cluster must be separated using unique VLAN IDs.

If you attempt to configure a cluster ID greater than 15 without meeting these requirements, the system displays a warning message.

Example: Extended Cluster ID

Each cluster node is identified by a node ID (node) which can be either 0 or 1.

This example demonstrates how to configure the chassis cluster ID and node ID, which must be set after connecting the two devices. The chassis cluster ID identifies the cluster to which the devices belong, while the chassis cluster node ID uniquely identifies each node within the cluster. After physically connecting the devices, use CLI operational mode commands to enable chassis clustering by assigning a cluster ID and node ID on each chassis. The cluster ID must be the same on both nodes.

Requirements

Before enabling chassis clustering, ensure that the following prerequisites are met:

  • You can access each device through the console port.

  • Both devices are running the same version of Junos OS.

  • All security devices participating in the cluster are of the same hardware model.

By default, a firewall ships with preconfigured interfaces. Before enabling chassis clustering, you must remove any existing interface configurations that will be repurposed as control or fabric interfaces.

For more information, see Understanding SRX Series Chassis Cluster Slot Numbering and Physical Port and Logical Interface Naming.

Overview

The system uses the chassis cluster ID and chassis cluster node ID to ensure that each node in a cluster receives the correct configuration. This mechanism is commonly used when configuring features such as the chassis cluster management interface with the apply-groups command.

Both the chassis cluster ID and the node ID are written to the system’s EPROM. These settings take effect only after the system is rebooted.

In the example configuration, the chassis cluster ID is set to 1. The first node is assigned a node ID of 0, and the second node is assigned a node ID of 1. When redundancy group priorities are the same on both nodes, assigning node ID 0 to the first node allows it to become the primary node.

Chassis cluster supports automatic synchronization of configurations. When a secondary node joins a primary node and a chassis cluster is formed, the primary node configuration is automatically copied and applied to the secondary node. See Understanding Automatic Chassis Cluster Synchronization Between Primary and Secondary Nodes.

Configuration

Procedure

Step-by-Step Procedure

To specify the chassis cluster node ID and cluster ID, you need to set two devices to cluster mode and reboot the devices. You must enter the following operational mode commands on both devices:

  1. Connect to the first device through the console port.

  2. Connect to the second device through the console port.

    For SRX5000 line of Firewalls, you must configure the control ports before forming the chassis cluster .

    To do this, connect to the console port on the primary device, assign it a node ID, and specify the cluster ID to which it will belong, and then reboot the system.

    Next, connect to the console port of the second device. Assign it a chassis cluster node ID and configure the same cluster ID that was used on the first node. After completing the configuration, reboot the system to apply the settings. In both cases, you can initiate an automatic reboot by including the reboot parameter in the CLI command. For more information, see Understanding Chassis Cluster Redundancy Groups.

Verification

Verify Chassis Cluster Status

Purpose

Verify the status of a chassis cluster.

Action

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

Meaning

The sample output shows that devices in the chassis cluster are communicating properly, with one device functioning as the primary node and the other as the secondary node.

See Also