Cisco ONS 15454 Troubleshooting Manual page 234

2.7.14 APSC-IMP
protection or 1+1 configuration does not send the two valid K1/K2 APS bytes anticipated by a system
configured for BLSR. One of the bytes sent is considered invalid by the BLSR configuration. The K1/K2
byte is monitored by receiving equipment for link-recovery information.
Troubleshooting for APSCDFLTK is often similar to troubleshooting for the
page
Clear the APSCDFLTK Alarm
Complete the
Step 1
each node has a unique node ID number.
Step 2 Repeat
Step 3 If two nodes have the same node ID number, complete the
on page 2-261
If the alarm does not clear, verify correct configuration of east port and west port optical fibers. (See the
Step 4
"E-W-MISMATCH" alarm on page
fibers must connect to west port fibers. The "Install Cards and Fiber-Optic Cable" chapter in the
Cisco ONS 15454 Procedure Guide provides procedures for fibering BLSRs.
If the alarm does not clear and the network is a four-fiber BLSR, ensure that each protect fiber is
Step 5
connected to another protect fiber and each working fiber is connected to another working fiber. The
software does not report any alarm if a working fiber is incorrectly attached to a protect fiber.
If the alarm does not clear, complete the
Step 6
page
If nodes are not visible, complete the
Step 7
page 2-275
If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport
Step 8
for more information or call Cisco TAC 1 800 553-2447.
2.7.14 APSC-IMP
An Improper SONET APS Code alarm indicates three consecutive, identical frames containing:
•
•
•
•
This alarm can occur on a VT tunnel when it does not have VT circuits provisioned on it. It can also
Note
occur when the exercise command or a lockout is applied to a span. An externally switched span does
not raise this alarm because traffic is preempted.
Cisco ONS 15454 Troubleshooting Guide, R8.5
2-40
2-57.
"Identify a BLSR Ring Name or Node ID Number" procedure on page 2-261
Step 1 for all nodes in the ring.
to change one node ID number so that each node ID is unique.
2-261.
to ensure that section data communications channel (SDCC) terminations exist on each node.
Default Severity: Minor (MN), Non-Service-Affecting (NSA)
SONET Logical Object: OCN
Unused code in bits 6 through 8 of byte K2.
Codes that are irrelevant to the specific protection switching operation being requested.
Requests that are irrelevant to the ring state of the ring (such as a span protection switch request in
a two-fiber ring NE).
ET code in K2 bits 6 through 8 received on the incoming span, but not sourced from the outgoing
span.
"Change a BLSR Node ID Number" procedure
2-90.) West port fibers must connect to east port fibers and east port
"Verify Node Visibility for Other Nodes" procedure on
"Verify or Create Node Section DCC Terminations" procedure on
Chapter 2 Alarm Troubleshooting
"BLSROSYNC" alarm on
to verify that
November 2009