Cisco ONS 15454 Troubleshooting Manual page 266

2.7.68 CPP-INCAPABLE
2.7.68 CPP-INCAPABLE
The Card Port Protection Incapable alarm indicates that the ML-MR-10 card or port is unable to provide
protection. This condition occurs when the Resilient Packet Ring (RPR) interface on the ML-MR-10
card is down, or when the CPP peer slot number is not configured from the Cisco IOS command line
interface or the protection group is disabled.
Note For information about provisioning ML-MR-10 Ethernet cards from the Cisco IOS interface, refer to the
Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration
Guide.
Clear the CPP-INCAPABLE Alarm
Ensure that the RPR interface is not in the administratively shutdown state.
Step 1
Ensure that the RPR interface is in the line protocol UP state.
Step 2
Ensure that the CPP peer slot is configured in Cisco IOS under the protection group configuration.
Step 3
Step 4 If the condition does not clear, log into the Technical Support Website at
http://www.cisco.com/techsupport for more information or call Cisco TAC 1 800 553-2447.
2.7.69 CTNEQPT-MISMATCH
The Connection Equipment Mismatch condition is raised when there is a mismatch between the
cross-connect card preprovisioned in the slot and the card actually installed in the shelf. For example,
one type of cross-connect card could be preprovisioned in Slot 10, but another could be physically
installed. It can also be caused by a card that is mismatched with the card. For example,
CTNEQPT-MISMATCH is raised when an XCVT card is replaced with a XC10G card.
Cisco does not support configurations of unmatched cross-connect cards in Slot 8 and Slot 10, although
this situation could briefly occur during the upgrade process.
The cross-connect card you are replacing should not be the active card. (It can be in SBY state or
otherwise not in use.)
Note During an upgrade, this condition occurs and is raised as its default severity, Not Alarmed (NA).
However, after the upgrade has occurred, if you wish to change the condition's severity so that it is
Not Reported (NR), you can do this by modifying the alarm profile used at the node. For more
information about modifying alarm severities, refer to the "Manage Alarms" chapter in the
Cisco ONS 15454 Procedure Guide.
Cisco ONS 15454 Troubleshooting Guide, R8.5
2-72
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: MLMR
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: EQPT
Chapter 2 Alarm Troubleshooting
November 2009