The Node ID Mismatch alarm is generated at nodes in a BLSR when:
The received Source Node ID does not match an entry in the node's BLSR ring map.
The Destination Node ID is equal to the node's own Node ID and the Source Node ID is not an adjacent node according to the node's BLSR ring map.
The received Destination Node ID in a short path message is not equal to the node's own Node ID or the Source Node ID is not an adjacent node according to the node's BLSR ring map.
The Destination Node ID is equal to the node's own Node ID and the Source Node ID is not an adjacent node according to the node's BLSR ring map.
Alarm Data |
Value/Meaning |
---|---|
Severity Levels |
Critical (CR), Major (MJ), Minor (MN), Not Alarmed (NA), Not Reported (NR) Default: Major (MJ) |
ASAP Type |
BLSR Protection Group |
AID Type |
OC-48 line OC-192 line |
Date |
Month/day/year that the condition was detected |
Time |
Hour:minute:second that the condition was detected |
Probable Cause |
NID-CONFL (Node ID conflict) |
Effect on Service |
NSA |
Alarm Entity Type |
OC48 OC192 |
Description |
Node ID Mismatch |
Likely Cause |
The BLSR manual ring map was not provisioned correctly. |
Visible Indication |
Lighted CR, MJ, or MN LED on the SYSCTL faceplate (when the severity level is provisioned to Critical, Major, or Minor, respectively) |
Action |
Proceed to Procedure 5-101: Clear "Node ID Mismatch" alarm. |
November 2011 | Copyright © 2011 Alcatel-Lucent. All rights reserved. |