Chapter 28
Alarms and Statistics
as the meaning of the active line alarms which are reported in the 0x55 Line Alarms command and are
discussed in other documentation. The APS specific alarms consist of seven alarms in addition to APS
OK, and APS Deactivated, and Line Looped.
Some of the APS alarms reflect problems with the underlying APS channel protocol, the K1/K2 bytes.
The K1 byte carries the request for a switch action on a specific channel to the remote end of the line.
The K2 byte indicates the status of the bridge in the APS switch and also carries mode information.
•
Remote Signl FAIL
A remote signal failure indicates that there is a problem with the far end signalling information in
the K1K2 bytes. There is a problem with the protection line's physical layer. So, one has to disable
APS and try to bring up the protection line as a normal line and diagnose the physical layer (by
putting loopback etc.).
Channel Mismatch
•
Can only happen in bidirectional mode and indicates that there is a problem with the underlying
APS channel protocol. The receive K2 channel number does not equal the transmit K1 channel
number. There is a problem with the protection line's physical layer. So, one has to disable APS
and try to bring up the protection line as a normal line and diagnose the physical layer (by putting
loopback etc.).
•
Prot Sw Byt FAIL
Protection Switch Byte failure or PSB. In bidirectional mode indicates that there is an invalid K1
byte. The receive K1 request does not match the reverse request and is less than the transmit K1
request. In all modes a PSB alarm indicates that K1/K2 protocol is not stable. There is a problem
with the protection line's physical layer. So, one has to disable APS and try to bring up the
protection line as a normal line and diagnose the physical layer (by putting loopback etc.). This
alarm will be seen if the local end of an APS working line or trunk is connected directly to the
remote end's protection line or trunk.
APS Card Missing
•
This alarm is seen in APS 1+1 configurations when BXM firmware determines that any BXM front
or back card is missing. Check dspcds or look in the dsplog to see which card associated with the
APS line is missing.
•
FarEnd Prot FAIL
Far end protection failure indicates that the far end's protection line is failing. When there is Signal
Failure on the protection channel, the remote end sees Far End Protection Fail. There is a problem
with the protection line's physical layer. So, one has to disable APS and try to bring up the
protection line as a normal line and diagnose the physical layer (by putting loopback, etc).If the
other end shows the "Architect Mismtch" APS alarm then the APS standards could be different at
each end. Use cnfcdaps or cnfapsln to check for this.
Architect Mismatch
•
Architecture mismatch indicates that one end of the APS line is configured for APS 1+1 and the
other end is configured for APS 1:1 which will not work. If the line is configured for GR-253
standard operation an architecture mismatch can also mean that one end is bi-directional and the
other end is uni-directional (ITUT will not report this). Verify that the APS architecture is
configured the same on either end of the APS lines using the cnfapsln command. This alarm will
also be seen if the local end of an APS working line or trunk is connected directly to the remote
end's protection line or trunk. In this case one end of the line usually will have a "Prot Sw Byt
FAIL" alarm present. If the other end shows the "FarEnd Prot FAIL" APS alarm then the APS
standards could be different at each end. Use cnfcdaps or cnfapsln to check for this.
Standard Mismatch
•
This indicates that on the local end of an APS 1+1 configuration that one card is running the ITUT
standard and the redundant card is running the GR-253 standard. Use the cnfcdaps command to
check and change the standard.
Release 9.3.0, Part Number 78-10674-01 Rev. D0, July 2001
Cisco BPX 8600 Series Installation and Configuration
APS Alarms
28-7