Example: Setting the Chassis Cluster Node ID and Cluster ID (CLI)

After connecting the two devices together, you configure a cluster ID and a node ID. A cluster ID identifies the cluster that the two nodes belong to. A node ID identifies a unique node within a cluster.

Before You Begin

Read:

The system uses node IDs and cluster IDs to apply the correct configuration for each node when you use the apply-group command described in Example: Configuring the Number of Redundant Ethernet Interfaces in a Chassis Cluster (CLI). The node ID and cluster ID statements are written to the EPROM, and when the system is rebooted, they take effect.

You can deploy up to 15 clusters in a Layer 2 domain. Each cluster is defined by a cluster-id value within the range of 1 through 15. A device can belong to only one cluster at any given time. Nodes in a cluster are numbered 0 and 1.

To set the node IDs and cluster IDs, connect to each device through the console port and enter the following operational commands, then reboot the system.

After you set the cluster ID and node ID for each node and the system reboots, the built-in interfaces are automatically renamed (see J Series Chassis Cluster Slot Numbering and Port/Interface Naming). Use the show chassis cluster status operational command to view node status.


{primary:node1}

user@host# show chassis cluster status
Cluster ID: 3
Node name                  Priority     Status    Preempt  Manual failover

Redundancy group: 0 , Failover count: 1
    node0                   254         secondary no       no
    node1                   2           primary   no       no

Redundancy group: 1 , Failover count: 1
    node0                   101         Secondary no       no
    node1                   99          primary   no       no

When you complete the chassis cluster basic configuration, any subsequent configuration changes you make are automatically synchronized on both nodes.

Related Topics