Clear The Lmp-Fail Alarm - Cisco NCS 2000 series Troubleshooting Manual

Alarm Troubleshooting
Note When the LMP-FAIL alarm is reported against a control channel (CTRLx) AID, it only refers to control
channel failure. It does not directly indicate data link or traffic engineering link status.
Note When the LMP-FAIL alarm is reported against a TE link AID (TLINKx), it refers only to TE link status, not
to control channel or data link status.

Clear the LMP-FAIL Alarm

SUMMARY STEPS
1. Verify the AID (CTRLx or TLINKx) of the alarm.
2. If the alarm is against the control channel AID, this is caused by mismatched control channel parameters
between the near-end NCS and the far-end node (which may be another vendor's equipment). Complete
the following steps:
3. If instead the alarm is raised against the TE link AID, complete the following steps:
DETAILED STEPS
Step 1
Verify the AID (CTRLx or TLINKx) of the alarm.
Step 2 If the alarm is against the control channel AID, this is caused by mismatched control channel parameters between the
near-end NCS and the far-end node (which may be another vendor's equipment). Complete the following steps:
a) Determine whether both near-end and far-end sides of the control channel are in the IS administrative state:
• Click the Provisioning > Comm Channels > LMP > Control Channels tabs and view the Admin State column
content for the channel.
• If the status does not say IS, change it and click Apply.
b) Determine whether the near-end node LMP configuration contains the far-end node's IP address as its remote node
IP. Also verify that the near-end node's LMP configuration uses the LMP node ID as its own remote node ID. If one
or more of these values is incorrect, enter it correctly.
c) Determine whether the far-end node LMP configuration contains the near-end node's IP address as its remote node
IP. Also verify that the far-end node's LMP configuration uses the LMP node ID as its own remote node ID. If one
or more of these values is incorrect, enter it correctly.
d) Verify that the far-end node is using the near-end node's IP address as its remote node IP address, and that the far
end is also using the LMP node ID as its remote node ID. Update the far end's values if they are incorrect.
Step 3
If instead the alarm is raised against the TE link AID, complete the following steps:
a) Determine whether both near-end and far-end sides of the TE link are in the IS administrative state. If either end is
currently down, update its administrative state to IS:
• Click the Provisioning > Comm Channels > LMP > TE links tab.
• If the status does not say IS, change it and click Apply.
Cisco NCS 2000 series Troubleshooting Guide, Release 11.0
Clear the LMP-FAIL Alarm
255