Professional Documents
Culture Documents
The system tracks and reports faults such as hardware failures, software failures,
communication failures, and loss of synchronization. When a fault occurs or is
cleared, the system generates an alarm record and stores it in one of the following
alarm queues, according to the severity of the alarm:
• critical
• major
• minor
• diagnostic
Major 500
Minor 2000
Diagnostic 2000
You can use CPSS or SNMP to log alarms remotely on a network management
system.
Table 150-2 lists the options available for alarm handling.
The method for alarm queue overflow determines how the system treats new alarms
after the alarm queue reaches its maximum capacity.
When configuring the alarm queue overflow method as fixed, the alarm
Too Many Alarms is added to the end of the queue when the queue reaches
maximum capacity. Each new outstanding alarm overwrites the newest alarm that
the system has cleared.
When you configure the alarm queue overflow method as circular, a new alarm
overwrites the oldest nonoutstanding or cleared alarm in the queue after the queue
reaches maximum capacity.
Alarm remote logging allows the network management system to record alarm
queues using CPSS.
You must establish a CPSS link between the system and the network management
system to log alarms remotely using CPSS; see section 71.3.
Alarm remote logging allows the network management system to record alarm
queues using SNMP.
SNMP traps
The SNMP agent detects major events on the node and generates reports in the form
of traps. See section 20.1 for information about the SNMP agent and traps.
When you enable remote logging for a queue using SNMP, the SNMP agent sends
an enterprise-specific trap when the system logs an alarm in that queue. The SNMP
agent sends the trap only when you have configured at least one trap destination. See
section 20.3 for more information about configuring trap destinations.
Table 150-3 lists the format for all SNMP traps.
blk2 14 1 Padding
blk4 25 1 Padding
Id 26 5 The sequence number in the range 1 to 99 999
blk5 31 1 Padding
blk6 58 1 Padding
Location 59 19 The location of the card that raised the alarm; the field
may include the card type if applicable.
When you enable remote logging for the queue using CPSS, the system places each
alarm in the alarm logging queue and sends it to the 5620 NM.
When the 5620 NM reports that it has received the alarm successfully, the system
deletes the alarm from the logging queue on the node; otherwise, the alarm remains
in the logging queue until transmission is successful. The system transmits the alarm
until the alarm is successfully logged. The interval between retries is longer every
time an attempt fails.
The logging queue can store up to 2000 alarms.
When you configure the logging queue as fixed, the system does not queue new
alarms for transmission when the queue is full.
When you configure the logging queue as circular, an alarm overwrites the oldest
alarm when the queue reaches maximum capacity.
The alarm queue summary for the node management session shows the number of
outstanding alarms in each queue, and the total number of alarms logged in each
queue. The number of outstanding alarms also displays in the header line. Alarms
that the system has not cleared are listed as outstanding.
You can view the alarms in a specific alarm queue. Each numbered alarm on the
screen shows:
• when the alarm was logged
• whether the alarm is acknowledged
• the alarm ID
• the card that triggered the alarm
• a description of the alarm condition
The alarm summary displays and lists the number of alarms in each alarm queue. For
each queue, the display shows the number of outstanding alarms and total alarms; the
total includes cleared alarms and outstanding alarms.
Table 151-1 lists the alarm information that the CLI screen displays.
Field Description
#### The top number in this column indicates the number of the last alarm placed in the
queue. Use the number under the #### column when you acknowledge or delete
an alarm; the numbers update each time you delete an alarm from the queue.
Date The date that the alarm occurred. If No Date appears in the Date column, the
system has been reset and the date has not yet been configured; see section 19.2.
Time The time that the alarm occurred, in 24-h format. If R appears after the time, the
system has been reset and the time is presented in relative hours since the reset;
see section 19.2.
Ack The status of the alarm. If an alarm has not been acknowledged, its status is U
(unacknowledged). After the alarm is acknowledged, its status changes to A
(acknowledged).
Id Each alarm is assigned a unique ID number when it is raised. The ID does not
change when you delete or acknowledge the alarms.
(1 of 2)
Field Description
Location The card type and the shelf, slot, port, and VPI/VCI of the affected device, if
applicable.
(2 of 2)
Parameters Table 151-2 lists the parameters required for this command.
You can change the priority of major, minor, and diagnostic alarms according to your
needs. For example, you can set an alarm to give it less visibility while performing
equipment maintenance.
You can configure the priority of each alarm as critical, major, minor, or diagnostic.
When you change the priority of an alarm, any new instance of the alarm has that
priority.
You cannot change the priority of an alarm if an instance of that alarm is outstanding.
You cannot configure the priority of an alarm that is critical by default. However,
you can configure the priority of an alarm that has been changed to critical.
When you change the priority of a diagnostic alarm, it is not moved to the
outstanding alarms queue.
Parameters Table 151-3 lists the parameters required for this command.
alarm_code This parameter is the code number of the alarm you are — —
configuring.
To acknowledge alarms
Description Use this command to acknowledge alarms.
An alarm condition may cause the system to generate two types of alarms: an alarm
to indicate that a fault has occurred, and an alarm to indicate that the alarm has
cleared. The alarm condition is outstanding until the alarm is cleared.
Diagnostic alarms are not categorized as outstanding.
Cleared alarms are included in the Total column on the CLI screen, but they are not
included in the Outstanding column.
You can clear alarms manually to indicate that you have resolved the condition that
raised the alarm. You can clear individual alarms, or all alarms in a specific queue.
To clear alarms
Description Use this command to clear alarms.
Parameters Table 151-5 lists the parameters required for this command.
All alarms remain in the alarm queue until you delete them. The system updates the
alarm numbers in the queue each time you delete an alarm. The system does not
update the ID numbers to indicate the history of the alarm queue.
Delete alarms to indicate to other operators that the condition that caused the alarm
is no longer present.
When you delete all alarms in a specific queue, all the alarms are deleted whether
they are outstanding or cleared.
To delete alarms
Description Use this command to delete alarms.
Parameters Table 151-6 lists the parameters required for this command.
The alarm queue synchronization feature guarantees that the content, temporal order,
and time-stamp of all alarms are consistent between the active and inactive
ECC card. Alarm queue redundancy helps you isolate and analyze faults after a
system restart or an activity switch. See section 23.2 for more information about
ECC card redundancy.
Autonomous HReset Card slot A card has reset autonomously because of an unrecoverable error. The
Card Ready alarm displays the reset cause code.
The clearing alarm occurs once the card has been removed and
re-inserted, and has synchronized its configuration and connection with the
Control sub-card.
Card Removed/Auto Card slot A card has been physically removed or has autonomously reset, and the
HReset system cannot distinguish between the two events. The Card Ready alarm
displays the reset cause code.
# of Accnting Records Card slot The spooling agent queue is overflowing and No No
Lost accounting records are lost with the number
displayed.
Autonomous HReset Card slot A card has reset autonomously because of an Yes No
unrecoverable error. The Card Ready alarm
displays the reset cause code.
The clearing alarm occurs once the card has
been removed and re-inserted, and has
synchronized its configuration and connection
with the Control sub-card.
Card Removed Card slot A card has been physically removed. Yes No
Card Removed/Auto Card slot A card has been physically removed or has Yes No
HReset autonomously reset, and the system cannot
distinguish between the two events. The Card
Ready alarm displays the reset cause code.
Control Mode Mismatch Card slot The DB attribute that defines the control mode No No
does not match the default control mode as
expected by the application.
Critical Backg DIAG Card, subcard A background diagnostic test has failed. (1) Yes No
Failure or module slot
Critical Directed DIAG Card, subcard A directed diagnostic test has failed. (1) Yes No
Failure or module slot
Critical Startup DIAG Card, subcard A startup diagnostic test has failed. (1) Yes No
Failure or module slot
DB Corruption Detected System The NVM auditor raises this alarm if the file Yes No
“/nvm/db” is corrupted and appears
unsalvageable.
Losing Accnting Records Card slot The ECC card is discarding accounting records Yes No
because the NVM storage capacity has been
exceeded.
No Data Collectors Card slot The node has lost contact with both collectors. Yes No
NVM Corruption Detected System The NVM auditor raises this alarm if the file Yes No
system audit fails.
NVM File Audit Problem System The NVM auditor raises this alarm if the file No No
system audit fails.
NVM File Corrupt Card slot There is a problem with the NVM. No No
Port download problem Port A request for download has been rejected more No No
than once.
(1 of 2)
Power Zone Failed Shelf-zone Both feeds to a power zone have failed. The Yes No
zone is either 1 or 2. Check the Status LEDs.
Inspect the feed source and input connections.
Shelf Out of Service Shelf The shelf is not receiving power or the ECC card Yes No
cannot communicate with the shelf.
SRAM card missing Card slot An SRAM card has not been detected on an No No
ECC card that supports data spooling.
Too Many AIS Detected Card slot or The number of AIS alarms exceeds the Yes No
endpoint configured AIS threshold.
Too Many Alarms (2) Card slot The number of alarm records logged to the No No
queue exceeds the queue size.
Too Many LOC Port The number of LOC alarms exceeds the Yes No
configured LOC threshold.
Too Many RDI Detected Endpoint The number of RDI alarms exceeds the Yes No
configured RDI threshold.
Too Many Starvation Card slot The number of starvation alarms exceeds the Yes No
configured threshold.
(2 of 2)
Notes
(1) See section 141.3 for more information about viewing diagnostic information.
(2) You cannot change the priority of the Too Many Alarms alarm.
MFR Feature Not Card The installed frame relay card does not support the MFR feature.
Supported
MFR Out of Service MFR bundle An MFR bundle is out of service because the ISR of a MFR bundle is zero.
Protection Lost Card, module, A condition is present that prevents the protection card, module, or port from
or port protecting a working card, module, or port in a protection group. The status of
a protection group changes from up to down. The alarm clears when the
status changes from down to up.
Sparing Bus Fault Card slot of A fault is detected by the sparing bus integrity checking mechanism. The fault
protection card can be in the backplane or in one of the adapter cards in a protection group.
Removing an adapter can cause the checking mechanism to fail. This alarm
only applies to a T1/E1 MS card
Wrong Fabric Port Card The configured fabric port for a card is different than the reported fabric port.
The alarm is only generated after the card becomes active.
X Egress LOC Error Card The fabric application raises this alarm when it receives a report from a UCS
card that has detected LOC errors on its fabric drop bus. The alarm occurs
only if there are no Drop Bus Failure alarms on the drop bus of the UCS card.
The alarm overrides HEC or DCHK error alarms raised for the UCS card.
Y Egress LOC Error Card The fabric application raises this alarm when it receives a report from a UCS
card that has detected LOC errors on its fabric drop bus. The alarm occurs
only if there are no Drop Bus Failure alarms on the drop bus of the UCS card.
The alarm overrides HEC or DCHK error alarms raised for the UCS card.
Activity Chg to Active Card The card has become the active ECC card. No Yes
Activity Chg to Card The card has become the inactive ECC card. No Yes
Inactive
Add Bus DCHK Error Card A cell payload (DCHK) error is detected on Yes No
ingressing traffic from an interface card or ECC
block.
Add Bus Error Slot Subcard A CRC error is detected on ingressing traffic to the Yes No
fabric block.
Add Bus HEC Error Card An HEC error is detected on ingressing traffic from Yes No
an interface card or ECC block.
AIS Port, circuit, or An AIS is on the incoming line. The remote device Yes No
IMA group sends the AIS after it detects a fault condition at the
remote end of the incoming signal, such as an LOS
or a faulty connection. AIS can also result from
faulty local hardware.
All Synch Card slot The SSU on the active ECC card has lost Yes No
References Lost synchronization with all external timing sources,
and has entered holdover or free-run
synchronization mode.
Applic Mismatch Port The DS3 application on the incoming signal does Yes No
not match the DS3 application configured on the
port.
APS-Chan Mismatch Card, module, The K2 code is different from the transmitted K1 Yes No
or port code.
APS-PSB Failure Card, module, An invalid or inconsistent APS K1 code has been Yes No
or port received.
APS-Switch Failure Card, module, A protection switch could not be executed. No Yes
or port
Bad NVM Battery Battery This alarm is raised when the NVM battery fails. Yes No
Bus Parity Error Subcard A Bus Parity error in the Switching Fabric subcard Yes No
of the ECC card is detected.
Card Dead Card slot The card has been inserted, but is not Yes No
communicating with the system.
Card in Boot Card slot The card cannot run the application software stored Yes No
in Flash memory, there is no application software
on the card, the boot jumper is on, or the card has
been activated in the boot PROM.
Card Overheated Card slot The temperature of the card has risen to a level that Yes No
can affect service.
Card Unreachable Card slot The card is present in the slot but cannot be Yes No
accessed. For example, the card may not be able to
communicate with the ECC card.
(1 of 10)
Cell Data Error (E) Port A cell data (DCHK) error is detected in the egress Yes No
direction by the Switching Fabric subcard of the
ECC card.
Cell Data Error (I) Port A cell data (DCHK) error is detected in the ingress Yes No
direction by the Switching Fabric subcard of the
ECC card.
Cell DCHK Error Subcard A cell data (DCHK) error is detected by the Yes No
Switching Fabric subcard of the ECC card.
Cell HEC Error Subcard A cell HEC error is detected by the Switching Fabric Yes No
subcard of the ECC card.
Cell Mapping Port The mapping modes between the ports on a DS3-2 Yes No
Heterogeneous card or E3-2 card are heterogeneous. At least one
of the ports has an inconsistent cell mapping
parameter setting compared to the rest of the ports.
For example, port 1 is set for direct cell mapping
and port 2 and 3 are set for PLCP. For DS3-2 and
E3-2 cards the cell mapping setting must be
consistent or data loss occurs.
Connection Node The Control subcard could not download the Yes No
Download Failed database for the interface card after the system
restarted.
Congested CPU Card Buffer utilization on the CPU has exceeded the Yes No
MCT.
CTL EDC Error Card A database checksum mismatch has been detected Yes No
Detected on the active ECC card. The mismatch indicates a
single bit error that is correctable.
CTL Uncorrectable Card A database checksum mismatch has been detected Yes No
EDC Err on the active ECC card. The mismatch indicates
two or more bit errors that are not correctable.
Data Collector Link Card The data spooling ECC card cannot communicate Yes No
Down with the data collectors or the connection has failed.
Drop Bus X Failure Port The Switching Fabric subcard of the ECC card Yes No
detects a drop bus failure that is signaled by two or
more faults detected by the UCS cards on the
X fabric.
Drop Bus Y Failure Port The Switching Fabric subcard of the ECC card Yes No
detects a drop bus failure that is signaled by two or
more faults detected by the UCS cards on the
Y fabric.
Equipment Failure Card The DS3 or E3 CCE-2 card, or the E1 or T1 card Yes No
has detected an equipment failure.
Fab Cfg: Connects Card Connections are deleted from the switch database Yes No
Deleted because of a change in the fabric configuration.
Fan Failed Shelf-fan 1 A fan in the cooling unit is not operating. The fan Yes No
number is always 1.
Gender Mismatch Port The gender of the attached MAU does not match Yes No
the configured port gender.
HDWR Device Fault Subcard slot A hardware device of the Switching Fabric subcard Yes No
has failed its periodic sanity check.
(2 of 10)
Hierarchy Not Card PNNI hierarchy has been configured on the switch, Yes No
Supported but the present ECC card does not support PNNI
hierarchy.
ICTL EDC Error Card A database checksum mismatch has been detected Yes No
Detected on the inactive ECC card. The mismatch indicates
a single bit error that is correctable.
ICTL Uncorrectable Card A database checksum mismatch has been detected Yes No
EDC Err on the inactive ECC card. The mismatch indicates
two or more bit errors that are not correctable.
Idle Signal Port An idle signal has been detected on the incoming Yes No
line.
ILMI Link Down Port The ILMI link has failed. Yes No
IMA: Fault declared IMA link The near-end IMA group declared an Yes No
at NE implementation-specific fault.
IMA: FE Indicates IMA group The far end indicates a Start Up status, but the near Yes No
Start-Up end does not indicate a Start Up (Akn) or a Config
Abort status.
IMA: FE Insuff. Links IMA group The far-end IMA group has fewer than the required Yes No
P value Tx and Rx links active.
IMA: FE Link IMA link Link forced to Unusable because of a link Unusable Yes No
Unusable state detected at the far end.
IMA: FE reports IMA group The far end reports that it is blocked. Yes No
Blocked
IMA: FE rpts IMA group The far end reports unacceptable configuration Yes No
unaccept.Conf parameters.
IMA: IMA group The near-end IMA group has fewer than the Yes No
Insufficient–Links required P value Tx and Rx links active.
IMA: Link IMA link The Tx link is detected as misconnected. Yes No
Mis-connected
IMA: Loss of Delay IMA link There is a persistent near-end LODS defect. Yes No
Sync
IMA: Loss of IMA IMA link There is a persistent near-end LIF defect. Yes No
Frame
IMA: Remote Failure IMA link There is a persistent RDI-IMA defect at the Yes No
Ind. near-end.
IMA Version, Rev. Card The configured IMA version is not supported by the Yes No
Mismatch installed PRI line card.
Inactive Database Card slot The database on the inactive ECC card is not Yes No
Not Sync synchronized with the database on the active ECC
card.
Incompatible Card The inactive ECC card is running a version that No No
Software cannot reconcile with the generic on the active ECC
card. This incompatibility indicates that the inactive
ECC card is running an older version than the active
ECC card, or is running a version that is more than
one major release later.
(3 of 10)
Insufficient CPU Card slot The packet processor has insufficient resources to Yes No
Resources support the connections configured through the
card. The card temporarily disables all connections.
Invalid PPC Module Card An invalid PPC module has been detected. No No
Present
LGN Rx Lower Level Node A PTSE has been received by a logical node from No No
PTSE its peer and the PTSE describes information about
a lower level node. In a properly functioning
hierarchy, it is not possible for a logical node to
receive lower level PTSEs. This alarm indicates that
another logical group node in the peer group is
misbehaving and transmitting PTSEs about nodes
it should not be.
Line AIS Port A line-layer AIS condition has been detected on the Yes No
incoming signal.
Link Integrity Lost Port The system does not detect receive data input or Yes No
link integrity pulses.
LOF Interface The DS1 circuit has detected an LOF condition on Yes No
circuit the incoming signal. LOF is caused by the DS1 or
DS3 port experiencing an LOS or LOF.
LOR Port The Far End Ready signal is de-asserted while the Yes No
clock signal is present.
LOS Port or circuit An LOS condition has been detected on the Yes No
incoming signal. LOS is caused by a local hardware
fault, a faulty connection or cable, a faulty or
missing remote card, or a high BER on the line. The
port or circuit is disabled.
Loss of Cell Del Port A failure to detect the ATM cell boundary has Yes No
occurred on the incoming signal.
Loss of Pointer Port An LOP condition has been detected on the Yes No
incoming signal.
Low Number PNNI Node The PNNI application is running low of PNNI PTSE No No
PTSE Bufs buffers.
(4 of 10)
LPR Port A loss of power has been reported by the dying Yes No
gasp indicator, which is a message from a remote
device, before it shuts down, to notify a line card it
has detected a power failure.
Major Backg DIAG Card slot, A background diagnostic test failed. (1) Yes No
Failure subcard or
module
Major Directed DIAG Card slot, A directed diagnostic test failed. (1) Yes No
Failure subcard or
module
Major Startup DIAG Card slot, A startup diagnostic test failed. (1) Yes No
Failure subcard or
module
Many PVC Alarms Stream The rate for the PVC alarm filter has been Yes No
exceeded.
Many Stream Alarms Stream The rate for the stream alarm filter has been Yes No
exceeded.
MAU Missing Card No MAU is installed for the ISC card. Yes No
MFR Feature Not Card The installed frame relay card does not support the No No
Supported MFR feature.
MFR Out of Service MFR bundle An MFR bundle is out of service because the ISR of Yes No
a MFR bundle is zero.
NNI Signaling Link Port The alarm text reflects the operational status of NNI Yes No
Down links.
No Support for ILMI Card This alarm is raised when a line card does not No No
4.0 support ILMI 4.0.
Not Talking to Mate Card slot The active and inactive ECC cards cannot Yes No
Ctl communicate with each other.
NTP Not Card slot The active and inactive ECC cards have lost NTP Yes No
Synchronized synchronization.
NVM Maintenance System The NVM auditor raises this alarm if the file system Yes No
Required audit fails.
Optical Failure Port A problem has been detected on the laser Yes No
monitoring function. The alarm indicates that the
lifetime of the laser is nearly over and should be
replaced.
(5 of 10)
P2MP Failed on Card slot If the P2MP set fails on the inactive card, this alarm No No
Inactive is raised on the active card to notify the user that the
connection has been removed on the inactive card.
P2P Failed on Card slot If the P2P set fails on the inactive card, this alarm is No No
Inactive raised on the active card to notify the user that the
connection has been removed on the inactive card.
Panel/MAU Failure Card The DS3 or E3 CCE-2 card has detected a problem
with the MAU. The alarm subcode indicates the
problem as:
• MAU: the protecting card detects that a MAU
has been connected, or a protected card
cannot detect that a MAU has been connected
• SP-Mm: the protecting card has detected that it
is connected to a port that is already in use
Path AIS Port A path-layer AIS condition has been detected on Yes No
the incoming signal.
Path RDI Port A path-layer RDI condition has been detected on Yes No
the incoming signal.
(6 of 10)
Path Trace Mismatch Port A path trace mismatch has been detected. Yes No
Payload Loopback Port A local payload loopback has been initiated from Yes No
Activated the far end.
PCMCIA Recovered Subcard There has been an internal PCMCIA module failure. No No
Error
Peer Group PNNI link The nodes at each end of the PNNI link are not in Yes No
Mismatch the same peer group.
PLCP-LOF Port An LOF condition has been detected at the PLCP Yes No
layer of the incoming signal.
PLCP-RDI Port or circuit An RDI condition has been detected at the PLCP Yes No
layer of the incoming signal.
PNNI Addr Advert Port or circuit The number of advertised addresses across all Yes No
Thresh logical group nodes has passed a high water mark
indicating a potential address propagation
overload. The high water mark is 90% of the
maximum number of advertised addresses across
all logical group nodes.
PNNI_Not Enough System Downloading PNNI node configuration has failed Yes No
Memory because of insufficient memory on the ECC card.
PNNI Link Down PNNI link The PNNI link has an operational status of down. Yes No
PNNI Loop Back PNNI link A loopback is running on the PNNI link. Yes No
Detected
PNNI SVCC Link Link The PNNI SVCC RCC to an adjacent LGN is down. Yes No
Down
Port in Reset Port or circuit The port is has been reset. Yes No
Processor Failure Card slot Card diagnostics have detected a processor failure Yes No
on the card.
Protection Lost Card, module, A condition is present that prevents the protection Yes No
or port card, module, or port from protecting a working
card, module, or port in a protection group. The
status of a protection group changes from up to
down. The alarm clears when the status changes
from down to up.
PTSE Rxd Not From System A PTSE that is not from this peer group is received. No No
PG
PTSE Too Big For System A PTSE that is too big for the PNNI node database No No
Database is received.
(7 of 10)
QoS Routing Not Card This alarm indicates that the ECC card does not Yes No
Supported support the QoS Routing feature.
RAM Parity Error Subcard RAM Parity errors in the datapath RAM on the Yes No
Switching Fabric subcard of the ECC card have
been detected.
RDI Port, circuit, or An RDI condition has been detected on the Yes No
IMA group incoming signal. The device at the remote end of
the transmit signal sends an RDI after it detects a
receive signal error on the remote device. RDI is
caused by faulty local hardware, a faulty transmit
connection or cable, or a faulty remote receiver.
Section LOF Port An LOF condition has been detected at the Yes No
section-layer of the incoming signal.
Section LOS Port An LOS condition has been detected at the Yes No
section-layer of the incoming signal.
Signal Degrade Port The card or module has passed the BER threshold Yes No
for signal degrade.
Signal Failure Port The card or module has passed the BER threshold Yes No
for signal fail.
Signaling Link Down Port The system has failed to correct a signaling link. Yes No
Sig Profile Not Card slot The active ECC card that provides the call No No
Supported processing application does not support the
signaling protocol. The subcode provides the
signaling profile number.
Slave 1 Processor Card slot The Slave 1 processor has failed. Yes No
Failure
Slave 2 Processor Card slot The Slave 2 processor has failed. Yes No
Failure
Slave 3 Processor Card slot The Slave 3 processor has failed. Yes No
Failure
Slave 4 Processor Card slot The Slave 4 processor has failed. Yes No
Failure
Sonet/SDH Port The protocol received on a port does not match the Yes No
Mismatch protocol configured on the port.
Sparing Bus Fault Card slot of A fault is detected by the sparing bus integrity Yes No
protection card checking mechanism. The fault can be in the
backplane or in one of the adapter cards in a
protection group. Removing an adapter can cause
the checking mechanism to fail. This alarm only
applies to a T1/E1 MS card
Spare Sectors Subcard The Control subcard has exhausted all available No No
Exhausted sectors.
SPVC Config Limit Card There are more SPVCs configured in the database No No
Exceeded than are supported by the PM hardware.
(8 of 10)
Starvation Circuit The playout buffer on the circuit has underrun. Yes No
Stream Out of Stream The frame stream has been put into an inactive Yes No
Service state because of a failure of the link management
protocol.
SVC Routing Tbl System A SVC routing table is overloaded. The number of Yes No
Thresh address table entries in the routing table is above
the high water mark (90% of the maximum number
of address entries in the SVC routing table).
SW Generic Not Subcard The software generic load is not supported on the No No
Supported Control subcard or Switching Fabric subcard of the
ECC card.
System Restart (2) Card slot The active ECC card has reset. No No
TAC Failed on Port This alarm is raised on the active port to notify the No No
Inactive user that the connection is removed and inactive.
TCA (DXI Card Card slot The congestion statistics on a circuit emulation card No Yes
Cong): 1 Hr have exceeded the defined threshold during a 1-h
interval.
TCA (DXI Strm Stream The congestion statistics on the stream have No Yes
Cong): 1 Hr exceeded the defined threshold during a 1-h
interval.
TCA (FR Card Card slot The congestion statistics on the frame relay card No Yes
Cong): 1 Hour have exceeded the defined threshold during a 1-h
interval.
TCA (Stream Cong): Stream The congestion statistics on the frame stream have No Yes
1 Hour exceeded the defined threshold during a 1-h
interval.
Too Many Alarms (3) Card The number of alarm records logged to the queue No No
exceeds the queue size.
Too Many Neighbors PNNI link The maximum number of PNNI neighbors has been Yes No
exceeded.
Too Many Parallel PNNI link The maximum number of PNNI links between the Yes No
Links same two PNNI nodes has been exceeded.
Too Many VCC-SW Card There are more than 16 VPIs in VCC switch mode. Yes No
mode VPIs
Trail Trace Mismatch Port A trail trace mismatch has been detected. Yes No
TS16 AIS Port An AIS condition has been detected on timeslot 16 Yes No
of an E1 port.
TS16 LOF Port An LOF condition has been detected on timeslot 16 Yes No
of an E1 port.
(9 of 10)
TS16 RDI Port An RDI condition has been detected on timeslot 16 Yes No
of an E1 port.
Wrong Fabric Port Card The configured fabric port for a card is different than Yes No
the reported fabric port. The alarm is only generated
after the card becomes active.
Wrong SW Rev for Card A CR/IMA module is configured for a slot that Yes No
CR/IMA Module contains a supported card, and the software on that
card does not support the CR/IMA functionality.
X Egress Cell Data Card The fabric application raises this alarm when a UCS Yes No
Error card detects errors on egress cells on its drop
bus.The alarm occurs only if there are no Drop Bus
Failure alarms on the drop bus of the UCS card.
X Egress HEC Error Card The fabric application raises this alarm when a UCS Yes No
card detects errors on egress cells on its drop bus.
This alarm is recorded against the UCS card that
reported the problem. The alarm occurs only if there
are no Drop Bus Failure alarms on the drop bus of
the UCS card.
X UCS Unreachable Card The ECC card installed in slot X cannot Yes No
Error communicate with the UCS listed in the alarm field.
Y Egress Cell Data Card The fabric application raises this alarm when a UCS Yes No
Error card detects errors on egress cells on its drop
bus.The alarm occurs only if there are no Drop Bus
Failure alarms on the drop bus of the UCS card.
Y Egress HEC Error Card The fabric application raises this alarm when a UCS Yes No
card detects errors on egress cells on its drop bus.
This alarm is recorded against the UCS card that
reported the problem. The alarm occurs only if there
are no Drop Bus Failure alarms on the drop bus of
the UCS card.
Y UCS Unreachable Card The ECC card installed in slot Y cannot Yes No
Error communicate with the UCS listed in the alarm field.
(10 of 10)
Notes
(1) See section 141.3 for more information about viewing diagnostic information.
(2) A subcode supplements this alarm; see Table 153-3.
(3) You cannot change the priority of the Too Many Alarms alarm.
Table 153-3 lists the subcodes that may display with the system restart alarm.
Subcode Description
Dmt A ECC card activity switch has occurred as a result of the active card having more
demerits than the inactive card.
Rls A ECC card activity switch initiated by the user has occurred.
Sys29 The system became active while the database was not synchronized.
(1 of 2)
Subcode Description
Sys34 The inactive ECC card is out of synchronization with the active ECC card.
Sys37 The active ECC card has reset the inactive ECC card.
Sys39 The inactive ECC card received a Null object ID from the active ECC card.
Sys44 The ISC card has experienced a startup problem; invalid configuration was
downloaded to the card on startup, indicating STM failure.
Sys45 The ISC card has experienced a startup problem; invalid configuration was
downloaded to the card on startup, indicating VCC failure.
Sys46 The ISC card has experienced a startup problem; invalid configuration was
downloaded to the card on startup, indicating ADP failure.
Sys47 The ISC card has experienced a startup problem; invalid configuration was
downloaded to the card on startup, indicating STP failure.
(2 of 2)
Fabric Switch to X System Switching fabric X has become the active switching fabric in a
fabric-redundant system. The system raises this alarm when switching
fabric Y experiences a failure or when a Y-to-X fabric switch occurs using a
node management session. Connections experience less than 100 ms of
interruption.
Fabric Switch to Y System Switching fabric Y has become the active switching fabric in a
fabric-redundant system. The system raises this alarm when switching
fabric X experiences a failure or when a Y-to-X fabric switch occurs using a
node management session.
MFR B/W Insufficient MFR bundle The MFR bundle has insufficient bandwidth because the ISR is less than
CSR.
Module Mismatch Module This alarm is raised when the configured module parameter is set as
CR/IMA and the installed module parameter is either none or unsupported
module.
Not Using Pref Fabric Card The active fabric of a UCS card shown in the subcode is different from the
preferred fabric broadcast by the active control application. This alarm may
result from a faulty hardware device on the drop bus interface of a UCS card
or a faulty drop bus connection leading to that UCS card.
WrongApp FabPrt Not Card A DBA-capable card is installed in a slot configured on the DBA fabric port,
Support but it is running a software load that does not support DBA.
AIS Interface The circuit has detected an AIS on the incoming line. Yes No
Circuit The remote device sends the AIS after it detects fault
conditions at the remote end of the incoming DS1
signal, such as an LOS or a faulty connection. Faulty
local hardware can also cause AIS.
APS-FEPL Failure Card, The far end protection line is in a Signal Fault Yes No
module, or condition.
port
APS-Mode Card, module The far end is provisioned for a different operational Yes No
Mismatch or port mode.
Card Missing Card slot or There is only one ECC card installed in a fabric Yes No
subcard slot redundant system.
Card/Module Not Card slot This alarm is raised when an older version line card No No
Supported that is not supported is inserted.
Card Variant Card or A slot is configured for a laser-reach variant other Yes No
Mismatch module than the one installed in the slot.
Card Version Card slot There is a difference between the configured variant No No
Mismatch and the installed variant types.
CPSS Class A CPSS Link The far-end node of the CPSS link does not have the Yes No
Mismatch same class A address as the local node.
Domain Mismatch CPSS Link The CPSS link is not set up because the near-end Yes No
and far-end nodes are in different CPSS domains.
Ethernet Port Down Card slot The Ethernet management port on the ECC card has Yes No
lost connectivity to the Ethernet LAN.
External Alarm System The external alarm contacts are closed, indicating a Yes No
Inputs ON fault condition on an external device.
(1 of 5)
Fabric Switch to X (2) System Switching fabric X has become the active switching Yes No
fabric in a fabric-redundant system. The system
raises this alarm when switching fabric Y
experiences a failure or when a Y-to-X fabric switch
occurs using a node management session.
Connections experience less than 100 ms of
interruption.
Fabric Switch to Y (2) System Switching fabric Y has become the active switching Yes No
fabric in a fabric-redundant system. The system
raises this alarm when switching fabric X
experiences a failure or when a Y-to-X fabric switch
occurs using a node management session.
Far End Critical System The Far End Critical Failure is generated when the Yes No
Failure far-end equipment indicates that it has a failure that
requires attention.
Far End LOCD Port There is a loss of cell delineation at the far end. Yes No
Far End AIS Port A DS3 AIS FEAC codeword is received from the far Yes No
end. The remote device sends the AIS after it
detects fault conditions at the remote end of the
incoming signal, such as an LOS or a faulty
connection.
Far End LOF Port The system has received a DS3 LOF FEAC Yes No
codeword from the far end. A faulty connection or
cable, a faulty remote card, or a high bit error rate on
the line causes an LOF.
Far End LOS Port The system has received a DS3 LOS FEAC Yes No
codeword from the far end. A local hardware fault, a
faulty connection or cable, or a faulty or missing
remote card causes an LOF.
FELPR Port The system has received an LPR from the far end. No No
IbIP Link Down IbIP link The configured in-band IP link is not functional; the Yes No
status of the link is still down.
IbIP Loopback IbIP link The far-end IP address is the same as the local Yes No
Detected In-band IP address.
IbIP Link Arp IbIP link The node timed out while waiting for a reply to an Yes No
Timeout Inverse ATM ARP request.
Idle Signal Port The port has received a DS3 payload that contains Yes No
the idle signal.
Label Mismatch Port A signal label mismatch is detected on the incoming Yes No
signal.
LAN overrun Card slot One or more LAN frames have been lost due to an Yes No
overrun condition.
Link Down Port A physical port has failed, or the CPSS has timed out Yes No
for other reasons.
Link Time-out Port The far-end device has stopped responding, or there Yes No
is no CPSS link configured on the far-end device.
Link Up - Parallel Port The CPSS link is inactive because another CPSS No Yes
Link link already has an active connection with the
far-end device. The inactive link acts as a backup.
(2 of 5)
Loopback Detected Port The CPSS nodes at the two ends of the link have the Yes No
same node number, or there is a physical connection
error and both ends of the CPSS link are physically
connected to the same node.
Loss of Synch Card slot The SSU is receiving an impaired signal because of Yes No
LOS, AIS, or an out-of-range frequency.
Many UNI ILMI Links Port This alarm is raised when more than 16 UNI ILMI Yes No
Down links have gone down. This alarm is not cleared until
all UNI links are up.
MFR B/W MFR bundle The MFR bundle has insufficient bandwidth because Yes No
Insufficient the ISR is less than CSR.
Minor Backgr DIAG Card, A background diagnostic test failed. (1) Yes No
Failure subcard or
module
Minor Directed DIAG Card, A directed diagnostic test failed. (1) Yes No
Failure subcard or
module
Minor Startup DIAG Card, A startup diagnostic test failed. (1) Yes No
Failure subcard or
module
Module Mismatch Module This alarm is raised when the configured module Yes No
parameter is set as CR/IMA and the installed module
parameter is either none or unsupported module.
Non-Routable Port The CPSS link to the stub node cannot route to the Yes No
active network management system.
Not Using Pref Card slot The active fabric of a UCS card shown in the Yes No
Fabric subcode is different from the preferred fabric
broadcast by the active control application. This
alarm may result from a faulty hardware device on
the drop bus interface of a UCS card or a faulty drop
bus connection leading to that UCS card.
OAM Ingress Card slot The card is receiving OAM cells on too many Yes No
Overflow endpoints.
OAM LNK E2E Endpoint A VC end-to-end endpoint with link OAM CC Yes No
VC-LOC enabled has declared a LOC defect state condition.
OAM LNK E2E Endpoint A VP end-to-end endpoint with link OAM CC enabled Yes No
VP-LOC has declared a LOC defect state condition.
OAM LNK SEG Endpoint A VC segment endpoint with link OAM CC enabled Yes No
VC-LOC has declared a LOC defect state condition.
OAM LNK SEG Endpoint A VP segment endpoint with link OAM CC enabled Yes No
VP-LOC has declared a LOC defect state condition.
OAM MATX E2E Endpoint A VC end-to-end endpoint with matrix OAM CC Yes No
VC-LOC enabled has declared a LOC defect state condition.
OAM MATX E2E Endpoint A VP end-to-end endpoint with matrix OAM CC Yes No
VP-LOC enabled has declared a LOC defect state condition.
OAM MATX SEG Endpoint A VC segment endpoint with matrix OAM CC Yes No
VC-LOC enabled has declared a LOC defect state condition.
OAM MATX SEG Endpoint A VP segment endpoint with matrix OAM CC Yes No
VP-LOC enabled has declared a LOC defect state condition.
(3 of 5)
OAM VP-AIS Endpoint A VP endpoint with OAM-AIS enabled has entered Yes No
the AIS state. The alarm includes a timestamp of the
date and time of the connection failure, or N/A if the
alarm is raised after the AIS threshold is crossed.
OAM VP-RDI Endpoint A VP endpoint with OAM-RDI enabled has entered Yes No
the RDI state. The alarm includes a time stamp of
the date and time of the connection failure, or N/A if
the alarm is raised after the RDI threshold is
crossed.
Overrun Port The playout buffer on the port has overrun. Yes No
RAI Interface The DS1 circuit has received an RAI from the far Yes No
Circuit end; this indicates that the far end has detected an
error on the incoming signal.
Regenerated The DS1 circuit has received an RAI from the far
Circuit end; this indicates that the far end has detected an
error on the incoming signal.
Port The port has received a RAI from the far end; this
indicates that the far end has detected an error on
the incoming signal.
RDI Port The port is receiving RDI from the far end. Yes No
Shelf Sync Loss System This alarm is raised if two or more UCS slots within Yes No
a shelf cannot lock onto the synchronization clock
signal coming from the ECC card (SSU module). It
indicates an interruption in the source of that signal
or in its transmission. For example, it may be raised
as a result of a failure on the ECC card (SSU
module) or a failure within the active fabric.
Slot Sync Loss Card slot This alarm indicates that the line card in the UCS slot Yes No
is not locking onto the synchronization clock coming
from the ECC card (SSU module). As a result, bit
errors in the data may occur. The root cause of the
alarm may be; a) a failure within the line card; b) an
interruption in the clock signal coming from the line
card.
SPVC Priority Card slot The ECC card does not support prioritized SPVC Yes No
Rpting Off status reporting. Configured values for report priority
and hold-down time will not be used.
(4 of 5)
SVCC RCC Diag Link Indicates that a diagnostic test has failed for a Yes No
Failure particular SVCC-based RCC on a logical group
node. This alarm is raised only after a test
SVCC-based RCC has failed to connect to the far
end.
Synch Source Port or circuit The SSU cannot derive timing from the specified Yes No
Failure synchronization source, and has switched to the
next available source.
Starvation (AAL2) AAL2 The playout buffer for an AAL2 channel starved for Yes No
channel an amount of time equal to the configured alarm
declaration time.
Synch Unit Range Port The specified synchronization source has become Yes No
Exceeded impaired because its frequency is out of range and
the SSU cannot derive timing from the signal
frequency.
TCA (DXI Card Card slot The congestion statistics on a circuit emulation card No Yes
Cong): 1 Hr have exceeded the defined threshold during a 1-h
interval.
TCA (DXI Strm Stream The congestion statistics on the stream have No Yes
Cong): 1 Hr exceeded the defined threshold during a 1-h interval.
TCA (FR Card Card slot The congestion statistics on the frame relay card No Yes
Cong): 1 Hour have exceeded the defined threshold during a 1-h
interval.
TCA (Stream Cong): Stream The congestion statistics on the frame stream have No Yes
1 Hour exceeded the defined threshold during a 1-h interval.
Too Many Alarms (3) Card slot The number of alarm records logged to the queue No No
exceeds the queue size.
TS16 AIS Port There is an incoming AIS on timeslot 16 of an E1 port Yes No
which is one of the tributaries of an E3 CCE-2.
UNI ILMI Link Down Port An ILMI link failure has occurred. Yes No
UNI Signaling Link Port The operational status of the UNI signaling link is Yes No
Down down.
VC-AIS Card slot F5 end-to-end VC-AIS cells have been received. Yes No
VC-RDI Card slot F5 end-to-end VC-RDI cells have been received. Yes No
WrongApp FabPrt Card slot A DBA-capable card is installed in a slot configured Yes No
Not Support on the DBA fabric port, but it is running a software
load that does not support DBA.
Wrong Card in Slot Card, A slot is configured for a card, subcard or module No No
subcard, or type other than the one installed in the slot, or the
module slot has been configured as EMPTY.
(5 of 5)
Notes
(1) See section 141.3 for more information about viewing diagnostic information.
(2) A subcode supplements this alarm; see Table 154-3.
(3) You cannot change the priority of the Too Many Alarms alarm.
Table 154-3 lists the subcodes that may display with the Fabric Switch to X and
Fabric Switch to Y alarms.
Subcode Description
Fault A fabric fault caused the system to switch automatically to the redundant fabric.
Usr The operator used the node management terminal to switch the system to the
redundant fabric.
Adapter Card Absent Card slot The card in a protection group is installed, but it has detected that the
adapter card is absent.
Adapter Card Mismatch Card slot The card in a protection group is installed, but it has detected that the
wrong type of adapter card is installed.
Card Ready Card slot This alarm displays the reset cause code for a card that has experienced
a hard reset.
Directed HReset Card slot An operator has performed a hard reset of a card for a maintenance
activity.
Directed HReset Complete Card slot The targeted card of an operator-initiated hard reset has completed the
process for resetting and is back in service.
Directed HReset Failed Card slot The targeted card of an operator-initiated hard reset has not completed
the process for resetting and is not back in service.
Fabric Port Switched Card The fabric port on a slot has changed.
Line Fault Detected Port This alarm is only raised on cards configured for 1:N LCR with port
protection enabled. The system has determined that the port failure is due
to a problem with a line fault and does not initiate an activity switch to a
protection card. The number of the failed port appears in the subcode
field.
MFR BL Out of Service MFR bundle An MFR bundle link is out of service as the LIP procedures determine that
link the link is in a state other than up.
Activity Change Due to Card This alarm indicates that a ECC card has become No Yes
Demerits active because it has fewer demerits than its mate
ECC card.
Adapter Card Absent Card slot The card in a protection group is installed, but it has No Yes
detected that the adapter card is absent.
Adapter Card Mismatch Card slot The card in a protection group is installed, but it has No Yes
detected that the wrong type of adapter card is
installed.
APS-Remote Maint Oper Card, A maintenance operation initiated from the remote No Yes
module, or side is being performed on a card or module
port involved in APS. The alarm subcode indicates the
reason for the alarm as follows:
• Lock: a lockout command has been issued
against the card or module
• FrdSw: a forced switch command has been
issued against the card or module
• ManSw: a manual switch command has been
issued against the card or module
Card Activity Gained Card slot A card or module involved in a protection group is No Yes
or module in service.
(1 of 7)
Card Activity Lost Card slot A card or module involved in a protection group is No Yes
or module inactive. The alarm subcode indicates the reason
for the alarm as follows:
• AIS: a line alarm indication signal has been
detected on the DS3 or E3 CCE-2 card
• AIS-L: a line alarm indication signal has been
detected on the line
• CrdFl: a card failure has been detected
• FrdSw: a force switch command has been
issued against the card
• LCD: a loss of cell delineation has been
detected
• Lock: a lockout command has been issued
against the card
• LOF: a loss of frame has been detected
• LOP: a loss of pointer has been detected
• LOR: a loss of remote has been detected
• LOS: a loss of synch has been detected
• ManSw: a manual switch command has been
raised against the card
• SD-L: a signal degrade condition has been
detected
• SD-R: a signal degrade condition has been
reported by the far end
• SF-L: a signal fail condition has been detected
• SF-R: a signal fail condition has been reported
by the far end
Card Diagnostic Fault (2) Subcard The Control subcard or/and the Switching Fabric No No
subcard of the ECC card is not responding to the
system, or has failed one or more diagnostic tests
during power-up.
Card Inserted Card slot The card has been inserted into the shelf. Yes No
Card Ready Card slot This alarm displays the reset cause code for a card No No
that has experienced a hard reset.
Card Removed Card slot The card has been removed from the shelf. Yes No
Card Reset Failed Alarm Card slot This alarm indicates that a card reset request has No Yes
failed due to the restrictions imposed by the
software on the ECC card.
Card Revs Too Old Card slot The card failed the minimum revision check. No Yes
Congested Frame Port Buffer utilization for the frame stream has Yes No
Stream exceeded the MCT configured for the stream.
Congested Slot Card slot The switching processor on the card has entered Yes No
the severely congested state and is out of memory.
Connect Diagnostic Card slot A connection message from the ECC to the line No Yes
card may not have been successfully downloaded
three consecutive times; therefore, the connection
may not be able to pass traffic.
Data Collector Switch Card slot The data spooling ECC card has switched its No Yes
Over connection from the active to the inactive collector.
Database Transfer Card slot The database transfer between the active and No Yes
Failed inactive ECC card has failed.
(2 of 7)
DBC Source Build Type System The source system is running an unofficial version No Yes
of software and the destination system is running a
hardened software load.
DBC Target Build Type System The destination system is running an unofficial No Yes
version of software and the source system is
running a hardened software load.
DBC Version System The version of the database installed is No Yes
Incompatible incompatible with the system.
Directed DIAG Failure Card, A directed diagnostic test failed. (1) Yes No
subcard or
module
Directed HReset Card slot An operator has performed a hard reset of a card No No
for a maintenance activity.
Directed HReset Failed Card slot The targeted card of an operator-initiated hard No No
reset has not completed the process for resetting
and is not back in service.
Fabric Port Switched Card The fabric port on a slot has changed. No No
Far End Not Router Port The CPSS link is not set up because the near end No Yes
is a stub node and the far end is a network
management system or stub node.
FDB Overflow Port The Ethernet port filtering database overflowed Yes No
when it attempted to learn another address. The
bridge was unable to learn the MAC address of one
or more frames. This may occur when the physical
LAN has too many stations. Reducing the filtering
database aging time may compensate.
Interface Rate Change Port The Ethernet port rate configuration has changed No Yes
due to autonegotiation.
Invalid Dest IP Port A CPSS link detects an invalid source IP address: Yes No
the nodes are not configured to be in the same
domain, there is a physical connection error or a
configuration error, or the destination address field
in the received packet is corrupt. CPSS traffic to the
far end is disrupted.
Invalid Src IP Port The CPSS link detects an invalid source IP Yes Nos
address: the domain of another node differs from
the source domain, the CPSS link to leaf node is an
invalid node, the node number of the source node
is incorrect for the type of link configured, or there
is a physical connection error or a configuration
error. CPSS traffic to the far end is disrupted.
Line Fault Detected Port This alarm is only raised on cards configured for No Yes
1:N LCR with port protection enabled. The system
has determined that the port failure is due to a
problem with a line fault and does not initiate an
activity switch to a protection card. The number of
the failed port appears in the subcode field.
Max num NetMgrs Port The system tried to configure more than the No Yes
Configured allowed number of network management systems.
(3 of 7)
Max num Routers Port The system tried to configure more than the No Yes
Configured allowed number of CPSS routing nodes.
Max num Stubs Port The system tried to configure more than the No Yes
Configured allowed number of CPSS stub nodes.
MFR BL Out of Service MFR An MFR bundle link is out of service as the LIP Yes No
bundle link procedures determine that the link is in a state other
than up.
NCCI AESA not set System NCCI AESA is not configured; no billing will occur. Yes No
No support for OAM ALS Card slot The card does not support OAM alarm surveillance. No No
PNNI LGN Oper Up Card slot A logical node has become operational UP No No
because its child node has been elected PGL
PNNI LGN Oper Down Card slot A logical node has become operational DOWN No No
because its child node has abdicated PGL election
responsibilities.
Port Activity Gained Port A port involved in a protection group is inactive. No Yes
Power Module Removed Shelf- A power module is not installed and is indicated by Yes No
module A or B.
PVC Active Endpoint The link management protocol configured on the No Yes
stream has changed the DLC status from inactive
to active.
PVC Added Endpoint The link management protocol configured on the No Yes
port has confirmed the addition of a PVC.
PVC Deleted Endpoint The link management protocol configured on the No Yes
port has confirmed the deletion of a PVC.
PVC Inactive Endpoint The link management protocol configured on the No Yes
port has changed the DLC status from active to
inactive.
PVC Unconfigured Endpoint The link management protocol configured on the No Yes
port has reported the addition of a DLC not
configured on the card. The DLC does not carry
frame relay traffic until the DLC is configured on the
port.
Rate Limit, Rev Port The installed line card does not have the version of No No
Mismatch software needed to support the rate limit feature.
Rate Limit, ABR-UBR Port The virtual bandwidth used by all the ABR and UBR No No
CAC connections together exceeds the available
bandwidth qualified by the configured rate limit for
the port.
Rate Limit, NRT-VBR Port The virtual bandwidth used by all nrt-VBR No No
CAC connections together exceeds the bandwidth
qualified by the configured rate limit for the port.
Reconcile Restarted Card slot The card restarted after a database download, but No Yes
the active and the inactive database did not
reconcile.
SNMP Authentication System An SNMP manager did not use any of the No Yes
Failure configured access community names or IP
addresses when it tried to access the SNMP agent.
(4 of 7)
Startup DIAG Failure Card, A startup diagnostic test failed. (1) Yes No
subcard or
module
Stream Config. Correct Stream The frame stream is in service and the DLC No Yes
information received from the network is consistent
with the information stored in the ECC card
database. The system generates this alarm when
the card starts up or after a change in LMI
configuration.
Stream Config. Mismatch Stream The frame stream is in service and the DLC No Yes
information received from the network is
inconsistent with the information stored in the ECC
card database. This system generates this alarm
when the card starts up or after a change in LMI
configuration.
TCA (AAL1Perf): 15 Min Endpoint The 15-min AAL-1 statistics parameter has been No Yes
exceeded on a connection of a circuit emulation
card.
TCA (AAL1Perf): 24 Endpoint The 24-h AAL-1 statistics parameter has been No Yes
Hour exceeded on a connection of a circuit emulation
card.
TCA (DS1-Line): 15 Min Port The 15-min TCA line statistics threshold has been No Yes
exceeded on the DS1 port.
TCA (DS1-Line): 24 Hour Port The 24-h TCA line statistics threshold has been No Yes
exceeded on the DS1 port.
TCA (DS1-Line-FE): 15 Port The 15-min TCA far end statistics threshold has No Yes
Min been exceeded on the
DS1 port.
TCA (DS1-Line-FE): 24 Port The 24-h TCA far end Line statistics threshold has No Yes
Hour been exceeded on the
DS1 port.
TCA (DS1-Path): 15 Min Port The 15-min TCA path statistics threshold has been No Yes
exceeded on the DS1 port.
TCA (DS1-Path): 24 Port The 24-h TCA path statistics threshold has been No Yes
Hour exceeded on the DS1 port.
TCA (DS1-Path-FE): 15 Port The 15-min TCA far end path statistics threshold No Yes
Min has been exceeded on the DS1 port.
TCA (DS1-Path-FE): 24 Port The 24-h TCA far end path statistics threshold has No Yes
Hour been exceeded on the
DS1 port.
TCA (DXI Stream): 1 Card slot The threshold of a given DXI Layer 2 gauge is No Yes
Hour exceeded on a DXI stream.
TCA (E1-G 821): 15 Min Port The 15-min TCA G.821 statistics threshold has No Yes
been exceeded on the E1 port.
TCA (E1-G 821): 24 Hour Port The 24-h TCA G.821 statistics threshold has been No Yes
exceeded on the E1 port.
TCA (E1-G 821-FE): 15 Port The 15-min TCA far end G.821 statistics threshold No Yes
Min has been exceeded on the E1 port.
TCA (E1-G 821-FE): 24 Port The 24-h TCA G.821 statistics threshold has been No Yes
Hour exceeded on the E1 port.
(5 of 7)
TCA (E1-LineEr): 15 Min Port The 15-min line error statistics threshold has been No Yes
exceeded on the E1 port.
TCA (E1-LineEr): 24 Port The 24-h line error statistics threshold has been No Yes
Hour exceeded on the E1 port.
TCA (E1-LineEr-FE): 15 Port The 15-min far end line error statistics threshold No Yes
Min has been exceeded on the
E1 port.
TCA (E1-LineEr-FE): 24 Port The 24-h far end line error statistics threshold has No Yes
Hour been exceeded on the
E1 port.
TCA (Egress Cell Data Card slot A line card has detected egress cell data errors. No Yes
Err)
TCA (Fabric Path) Port Fabric errors on the Switching Fabric subcards No Yes
have generated a threshold crossing alert once
during a 15-min interval.
TCA (Line): 15 Minute (3) Port A statistic at the line layer has exceeded the No Yes
defined threshold during a 15-min interval.
TCA (Line): 24 Hour (3) Port A statistic at the line layer has exceeded the No Yes
defined threshold during a 24-h interval.
TCA (G.SHDSL): 15 Port The configured 15-min threshold has been No Yes
Minute exceeded for one of the following statistics
(identified in the alarm subcode for an SHDSL
card):
• LOSS
• LOSWS
• LowSNRS
• LPRS
• ES
• SES
• UAS
TCA (G.SHDSL): 24 Port The configured 24-h threshold has been exceeded No Yes
Hour for one of the following statistics (identified in the
alarm subcode for an SHDSL card):
• LOSS
• LOSWS
• LowSNRS
• LPRS
• ES
• SES
• UAS
TCA (Line-FE): 15 Port A statistics counter at the far-end line layer has No Yes
Minute (3) exceeded the defined threshold during a 15-min
interval.
TCA (Line-FE): 24 Hour Port A statistic at the far-end line layer has exceeded the No Yes
(3) defined threshold during a 24-h interval.
TCA (Path): 15 Minute (3) Port A statistic at the path layer has exceeded the No Yes
defined threshold during a 15-min interval.
TCA (Path): 24 Hour (3) Port A statistic at the path layer has exceeded the No Yes
defined threshold during a 24-h interval.
(6 of 7)
TCA (Path-FE): 15 Port A statistic at the far-end path layer has exceeded No Yes
Minute (3) the defined threshold during a 15-min interval.
TCA (Path-FE): 24 Hour Port A statistic at the far-end path layer has exceeded No Yes
(2)(3) the defined threshold during a 24-h interval.
TCA (PLCP): 15 Port A statistic at the PLCP layer has exceeded the No Yes
Minute (3) defined threshold during a 15-min interval.
TCA (PLCP): 24 Hour (3) Port A statistic at the PLCP layer has exceeded the No Yes
defined threshold during a 24-h interval.
TCA (PLCP-FE): 15 Port A statistic at the far-end PLCP layer has exceeded No Yes
Minute (3) the defined threshold during a 15-min interval.
TCA (PLCP-FE): 24 Hour Port A statistic at the far-end PLCP layer has exceeded No Yes
(3) the defined threshold during a 24-h interval.
TCA Profile CLI Affected Port The TCA profile has been changed through the No Yes
command line interface and may not be the same
as the rest of the network.
TCA (Section): 15 Port A statistic at the section-layer has exceeded the No Yes
Minute (3) defined threshold during a 15-min interval.
TCA (Section): 24 Port A statistic at the section-layer has exceeded the No Yes
Hour (3) defined threshold during a 24-h interval.
Too Many Alarms (4) Card slot The number of alarm records logged to the queue No No
has exceeded the queue size.
(7 of 7)
Notes
(1) See section 141.3 for more information about viewing diagnostic information.
(2) A subcode supplements this alarm; see Table 155-3.
(3) A subcode supplements this alarm; see Table 155-4.
(4) You cannot change the priority of the Too Many Alarms alarm.
Table 155-3 lists the subcodes that may display with the Card Diagnostic Fault
alarm.
Subcode Description
20 SAR Diagnostic
40 CAM Diagnostic
(1 of 2)
Subcode Description
80 Datapath Diagnostic
100 —
(2 of 2)
Table 155-4 lists the subcodes that can appear with the TCA alarms.
Subcode Description
CV Code violation
ES Errored seconds
FC Failure count