System identifier on two or more chassis in the network must be unique

Products

• XOS

Issue/Introduction

Multiple different chassis mistakenly configured with an identical system identifier may lead to conflicting MAC addresses on those chassis.Modules might fail booting process with no DHCP BOOT Requests logged in logs.

Ping to circuit IP address doesn't work, but outgoing ping from the APM works fine and during that time the ping from outside to the APM also works fine.

The ARP table on neighbor device shows that MAC address for the circuit IP is the same like a MAC address associated with another X-series chassis.

Cause

Modules might attempt to boot from another chassis with the same system identifier configured.
The MAC address for the circuit IP addresses is a virtual MAC address that takes into account the system identifier.
An identical system identifier on two different chassis in the network can lead to duplicate MAC addresses on those chassis.

To display the current system identifier, use the following CLI command:

# show system-identifier

Configured System Identifier  : 32

Operational System Identifier : 32

 

 

Resolution

The system identifier on each chassis in a shared network must be unique. If two or more chassis in the network are configured with an identical system identifier by mistake then modify the system identifier on one of those two chassis to resolve the issue. If more DBHA pairs are configured in the same management network, their system identifiers should be unique as well.

The following command sets the system identifier:

# configure system-identifier <system-id>

A reload of the chassis is required for the change to take effect.

 

Workaround

N/A