Cisco ONS 15454 - Clear the PEER-NORESPONSE Alarm; 2.7.318 PLM-P

2-195
Cisco ONS 15454 Troubleshooting Guide, R8.5
November 2009
Chapter 2 Alarm Troubleshooting
2.7.318 PLM-P
The switch agent raises a Peer Card Not Responding alarm if either traffic card in a protection group
does not receive a response to the peer status request message. PEER-NORESPONSE is a software
failure and occurs at the task level, as opposed to a communication failure, which is a hardware failure
between peer cards.
However, for ML-MR-10 cards, a peer card not responding alarm is raised if a CPP card that is active
does not receive any heartbeat response from its peer card. This happens under the following conditions:
• Peer card is not present in the ONS 15454 chassis
• Peer card is not configured for protection
• Protection is disabled on the peer card
• Peer card has reset.
Clear the PEER-NORESPONSE Alarm
Step 1 Complete the “Reset a Traffic Card in CTC” procedure on page 2-270 for the reporting card. For the LED
behavior, see the “2.8.2 Typical Traffic Card LED Activity During Reset” section on page 2-260.
Step 2 Verify that the reset is complete and error-free and that no new related alarms appear in CTC. Verify the
LED appearance: A green ACT/SBY LED indicates an active card. An amber ACT/SBY LED indicates
a standby card.
Step 3 For ML-MR-10 card, ensure that the CPP peer card has not failed, the correct protection configuration
is present on both CPP cards, and protection is not disabled on the CPP peer card.
Step 4 If the alarm does not clear, log into the Cisco Technical Support Website at
http://www.cisco.com/techsupport for more information or log into
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml to obtain a directory of toll-free
Technical Support numbers for your country.
2.7.318 PLM-P
Default Severity: Critical (CR), Service-Affecting (SA)
SONET Logical Objects: STSMON, STSTRM
A Payload Label Mismatch Path alarm indicates that signal does not match its label. The condition is
indicated by a problematic C2 byte value in the SONET path overhead. The alarm is raised if all of the
following conditions are met:
• The received C2 byte is not 0x00 (unequipped).
• The received C2 byte is not a PDI value.
• The received C2 does not match the expected C2.
• The expected C2 byte is not 0x01 (equipped, unspecified).
• The received C2 byte is not 0x01 (equipped, unspecified).
For example, on nodes equipped with CTC Software R4.1 and earlier, this alarm could occur when you
have a DS3XM-6 card connected to a DS-3 card instead of a DS-1 card. The DS3XM-6 card expects a
C2 label byte value of 01. A DS-1 card transmits this value, but a DS-3 card transmits a value of 04. The
mismatch between the sent and expected values causes the PLM-P alarm.