Cisco ONS 15454 Troubleshooting Manual page 337

Chapter 2 Alarm Troubleshooting
Step 2 If the alarm is against the control channel AID, this is caused by mismatched control channel parameters
between the near-end ONS 15454 and the far-end node (which may be another vendor's equipment).
Complete the following steps:
a.
b.
c.
d.
Step 3 If instead the alarm is raised against the TE link AID, complete the following steps:
a.
b.
c.
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport
Step 4
for more information or call Cisco TAC 1 800 553-2447.
2.7.195 LMP-SD
The LMP Data Link Signal Degrade condition occurs for when the TCC2/TCC2P receives an LMP link
summary or channel status message that the control channel is not available from the far end, so the data
link level of service is not guaranteed. The degrade range is provisionable.
LMP-SD clears when the TCC2/TCC2P receives a link summary or channel status message reporting
that the data link is in the Signal Okay (OK) state.
November 2009
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 Channel tabs and view the
•
Admin State column content for the channel.
• If the status does not say IS, change it and click Apply.
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.
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.
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.
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 link tab.
• If the status does not say IS, change it and click Apply.
Determine whether the near-end node's remote TE link ID matches the far-end node's local TE link
ID. If the near-end node's remote value is incorrect, enter it correctly.
Determine whether the far-end node's remote TE link ID corresponds to the near-end node's local
TE link ID. If the far-end node's remote value is incorrect, enter it correctly.
Default Severity:Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
DWDM Logical Object: GE
Cisco ONS 15454 Troubleshooting Guide, R8.5
2.7.195 LMP-SD
2-143