Cisco ONS 15454 Troubleshooting Manual page 238

2.7.18 APSIMP
2.7.18 APSIMP
The APS Invalid Code alarm occurs if a 1+1 protection group is not properly configured at both nodes
to send or receive the correct APS byte. A node that is either configured for no protection or is configured
for path protection or BLSR protection does not send the right K2 APS byte anticipated by a system
configured for 1+1 protection. The 1+1 protect port monitors the incoming K2 APS byte and raises this
alarm if it does not receive the byte.
The alarm is superseded by an APSCM or APSMM alarm, but not by an AIS condition. It clears when
the port receives a valid code for 10 ms.
Clear the APSIMP Alarm
Check the configuration of the other node in the 1+1 protection group. If the far end is not configured
Step 1
for 1+1 protection, create the group. For procedures, refer to the "Turn Up Node" chapter in the
Cisco ONS 15454 Procedure Guide.
If the other end of the group is properly configured or the alarm does not clear after you have provisioned
Step 2
the group correctly, verify that the working ports and protect ports are cabled correctly.
Ensure that both protect ports are configured for SONET.
Step 3
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.19 APS-INV-PRIM
The Optimized 1+1 APS Primary Facility condition occurs on OC-N cards in an optimized 1+1
protection system if the incoming primary section header does not indicate whether it is primary or
secondary.
APS-INV-PRIM is an informational condition and does not require troubleshooting. If the APS switch
Note
is related to other alarms, troubleshoot these alarms as necessary using the procedures in this chapter.
2.7.20 APSMM
Cisco ONS 15454 Troubleshooting Guide, R8.5
2-44
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
Default Severity: Minor (MN), Non-Service Affecting (NSA)
SONET Logical Object: OCN
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
Chapter 2 Alarm Troubleshooting
November 2009