A7670 Alarm Dictionary

150 —Setting up alarm handling

150.1 Alarms and queues 150-2

150.2 Alarm queue overflow handling 150-3

150.3 Alarm remote logging using CPSS 150-3

150.4 Alarm remote logging using SNMP 150-3

150.5 Remote logging overflow 150-5

Alcatel 7670 Edge Services Extender, Release 2.2 150-1June 2004 90-9150-02

150 — Setting up alarm handling

150.1 Alarms and queues

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

A LED on the Alarm card indicates an outstanding alarm.

An alarm severity indicator also displays in the header line of the CLI screen, and indicates the highest-priority alarm queue with unacknowledged outstanding alarms, if any are present on the node. The alarm severity indicator updates as the system raises and clears alarms.

Table 150-1 lists the maximum number of alarm records that the system stores in each queue.

Table 150-1 Alarm queue size

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.

Table 150-2 Options for alarm handling

Alarm queue Maximum number of alarms

Critical 100

Major 500

Minor 2000

Diagnostic 2000

Option CPSS SNMP Section

Alarm queue overflow ✓ 150.2

Remote logging ✓ 150.3

✓ 150.4

Remote logging overflow ✓ 150.5

150-2 Alcatel 7670 Edge Services Extender, Release 2.290-9150-02 June 2004


150.2 Alarm queue overflow 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.

To configure the alarm queue overflow method

Description Use this command to configure the alarm queue overflow method.

Syntax alarms config queue {critical | diagn | major | minor}{circular | fixed} ↵

150.3 Alarm remote logging using CPSS

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.

To enable or disable alarm logging using CPSS

Description Use this command to enable or disable alarm logging using CPSS.

Syntax alarms logging {critical | diagnostic | major | minor}{remote-off | remote-on} ↵

150.4 Alarm remote logging using SNMP

Alarm remote logging allows the network management system to record alarm queues using SNMP.

Note — The default is circular.

Note — The default is remote-off.



SNMP trapsThe 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.

Table 150-3 Format for SNMP traps

The SNMP agent generates alarm traps based on an enterprise-specific extension. This extension, nncExtAlarm, provides the SNMP agent with the following four SNMP alarm traps:

• criticalQAlarm• majorQAlarm• minorQAlarm• diagnosticQAlarm

Field Start Length in bytes

Description

## 0 4 The position in the queue; this field is updated as alarms are deleted.

blk1 4 1 Padding

Date 5 9 The date of the alarm in the format DDMMMYYYY

blk2 14 1 Padding

Time 15 8 The time of the alarm in the format HH:MM:SS.

blk3 23 2 Padding

Ack 24 1 An acknowledgment (A=ack, U=unack)

blk4 25 1 Padding

Id 26 5 The sequence number in the range 1 to 99 999

blk5 31 1 Padding

Code 32 26 A description of the event

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.



To enable or disable alarm logging over SNMP

Description Use this command to enable or disable alarm logging over SNMP.

Syntax alarms logging {critical | diag | major | minor}{snmp-off | snmp-on} ↵

150.5 Remote logging overflow

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.

To configure the remote logging overflow method

Description Use this command to configure the remote logging overflow method.

Syntax alarms config log-queue {circular | fixed} ↵

Note — The default is snmp-off.

Note — The default is circular.




151 —Managing alarms

151.1 Viewing alarms 151-2

151.2 Configuring alarm priority 151-3

151.3 Acknowledging alarms 151-4

151.4 Clearing alarms 151-5

151.5 Deleting alarms 151-5

151.6 Alarm queue redundancy 151-6


151 — Managing alarms

151.1 Viewing alarms

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 information does not refresh automatically.

The status of an alarm can be outstanding or cleared. An outstanding alarm indicates a problem that has not been resolved. A cleared alarm indicates a problem that has been resolved. For more information about clearing alarms, see section 151.4.

When you view alarms, you can display:

• a summary of the alarms• the alarms in a specific queue• all alarms• outstanding or cleared alarms only

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.

Table 151-1 Information for alarm queues

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)



To view alarms in a specific queue

Description Use this command to view alarms in a specific queue.

Syntax alarms outstanding {all-alarms | critical | diagn | major | minor} ↵goto {alarm_number | goto_bottom} ↵

Parameters Table 151-2 lists the parameters required for this command.

Table 151-2 Parameters for viewing alarms in a specific queue

To filter the alarm information

Description Use this command to filter the alarm information.

Syntax alarms outstanding {all-alarms | critical | major | minor} ↵subset {all | cleared | outstanding} ↵

151.2 Configuring alarm priority

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.

Code The alarm condition.

Location The card type and the shelf, slot, port, and VPI/VCI of the affected device, if applicable.

Parameter Description Value Default

alarm_number This parameter is the number of the alarm. — —

value This parameter is the value of the alarm. 1 to 2000 —

Field Description

(2 of 2)



To change alarm priority

Description Use this command to change the alarm priority.

Syntax alarms config priority alarm_code {critical | diagn | major | minor} ↵


Table 151-3 Parameters for changing alarm priority

To view alarm priorities

Description Use this command to view alarm priorities.

Syntax alarms config priority {show-all | show-chg} ↵

151.3 Acknowledging alarms

Acknowledge alarms to indicate to other operators that an alarm condition is being examined. When you acknowledge an alarm, its status changes from U (unacknowledged) to A (acknowledged).

You can acknowledge:

• one alarm• all alarms in a specific queue• all alarms

When you acknowledge all alarms in a specific queue, you acknowledge them whether they are outstanding or cleared.

To acknowledge alarms

Description Use this command to acknowledge alarms.

Syntax alarms outstanding {critical | major | minor | all-alarms} ↵ {ack {alarm_value | alarm_value-alarm_value} | ack_all} ↵

Parameters Table lists the parameters required for this command.


alarm_code This parameter is the code number of the alarm you are configuring.

— —



Table 151-4 Parameters for acknowledging outstanding alarms

151.4 Clearing 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.

Syntax alarms outstanding {all-alarms | critical | major | minor} ↵ {clear {alarm_value | alarm_value-alarm_value} | clear-all} ↵


Table 151-5 Parameters for clearing alarms

151.5 Deleting alarms

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.


alarm_value-alarm_value This parameter is the first and last number of the range of alarms displayed in the # column.

— —

alarm_value This parameter is the number of the specific alarm displayed in the # column.

— —



— —


— —



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.

Syntax alarms outstanding {all-alarms | critical | major | minor} ↵ {delete {alarm_value | alarm_value-alarm_value} | delete-all} ↵


Table 151-6 Parameters for deleting alarms

151.6 Alarm queue redundancy

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.



— —


— —


152 —Critical alarm descriptions

Table 152-2 Critical alarms 152-3


152 — Critical alarm descriptions

Table 152-1 New critical alarms

Alarm text Location Description

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 Card slot A card has been physically removed.

Card Removed/Auto HReset

Card slot A card has been physically removed or has autonomously reset, and the system cannot distinguish between the two events. The Card Ready alarm displays the reset cause code.



Table 152-2 Critical alarms

Alarm text Location Description Clearing alarm

Self-clearing

# of Accnting Records Lost

Card slot The spooling agent queue is overflowing and accounting records are lost with the number displayed.

No No

ATMizer Failure System The ECC card ATMizer control communication sub-processor has failed.

No No

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.

Yes No

Card Removed Card slot A card has been physically removed. Yes No

Card Removed/Auto HReset

Card slot A card has been physically removed or has autonomously reset, and the system cannot distinguish between the two events. The Card Ready alarm displays the reset cause code.

Yes No

Control Mode Mismatch Card slot The DB attribute that defines the control mode does not match the default control mode as expected by the application.

No No

Critical Backg DIAG Failure

Card, subcard or module slot

A background diagnostic test has failed. (1) Yes No

Critical Directed DIAG Failure


A directed diagnostic test has failed. (1) Yes No

Critical Startup DIAG Failure


A startup diagnostic test has failed. (1) Yes No

Database Reset Subcard The configuration database on the Control subcard has been reset to default values.

No No

DB Corruption Detected System The NVM auditor raises this alarm if the file “/nvm/db” is corrupted and appears unsalvageable.

Yes No

ePM Module Required System An ePM module is required. No No

Fan Removed Shelf-fan 1 The cooling unit is not installed. The fan number is always 1.

Yes No

Losing Accnting Records Card slot The ECC card is discarding accounting records because the NVM storage capacity has been exceeded.

Yes No

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 system audit fails.

Yes No

NVM File Audit Problem System The NVM auditor raises this alarm if the file system audit fails.

No No

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 than once.

No No

(1 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.

Power Zone Failed Shelf-zone Both feeds to a power zone have failed. The zone is either 1 or 2. Check the Status LEDs. Inspect the feed source and input connections.

Yes No

Shelf Out of Service Shelf The shelf is not receiving power or the ECC card cannot communicate with the shelf.

Yes No

SRAM card missing Card slot An SRAM card has not been detected on an ECC card that supports data spooling.

No No

Too Many AIS Detected Card slot or endpoint

The number of AIS alarms exceeds the configured AIS threshold.

Yes No

Too Many Alarms (2) Card slot The number of alarm records logged to the queue exceeds the queue size.

No No

Too Many LOC Port The number of LOC alarms exceeds the configured LOC threshold.

Yes No

Too Many RDI Detected Endpoint The number of RDI alarms exceeds the configured RDI threshold.

Yes No

Too Many Starvation Card slot The number of starvation alarms exceeds the configured threshold.

Yes No


Self-clearing

(2 of 2)


153 —Major alarm descriptions

Table 153-1 New major alarms 153-2

Table 153-2 Major alarms 153-3

Table 153-3 System restart alarm subcodes 153-13


153 — Major alarm descriptions

Table 153-1 New major alarms


MFR Feature Not Supported

Card The installed frame relay card does not support the MFR feature.

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, or port

A condition is present that prevents the protection 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.

Sparing Bus Fault Card slot of protection card

A fault is detected by the sparing bus integrity 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

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.



Table 153-2 Major alarms


Self-clearing alarm

Activity Chg to Active Card The card has become the active ECC card. No Yes

Activity Chg to Inactive

Card The card has become the inactive ECC card. No Yes

Add Bus DCHK Error Card A cell payload (DCHK) error is detected on ingressing traffic from an interface card or ECC block.

Yes No

Add Bus Error Slot Subcard A CRC error is detected on ingressing traffic to the fabric block.

Yes No

Add Bus HEC Error Card An HEC error is detected on ingressing traffic from an interface card or ECC block.

Yes No

AIS Port, circuit, or IMA group

An AIS is on the incoming line. The remote device 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.

Yes No

All Synch References Lost

Card slot The SSU on the active ECC card has lost synchronization with all external timing sources, and has entered holdover or free-run synchronization mode.

Yes No

Applic Mismatch Port The DS3 application on the incoming signal does not match the DS3 application configured on the port.

Yes No

APS-Chan Mismatch Card, module, or port

The K2 code is different from the transmitted K1 code.

Yes No

APS-PSB Failure Card, module, or port

An invalid or inconsistent APS K1 code has been received.

Yes No

APS-Switch Failure Card, module, or port

A protection switch could not be executed. No Yes

Bad NVM Battery Battery This alarm is raised when the NVM battery fails. Yes No

Starvation Port The playout buffer for a connection on an AAL-1 multiplexer has been starved for an amount of time equal to the alarm declaration time.

Yes No

Bus Parity Error Subcard A Bus Parity error in the Switching Fabric subcard of the ECC card is detected.

Yes No

Card Dead Card slot The card has been inserted, but is not communicating with the system.

Yes No

Card in Boot Card slot The card cannot run the application software stored 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.

Yes No

Card Overheated Card slot The temperature of the card has risen to a level that can affect service.

Yes No

Card Unreachable Card slot The card is present in the slot but cannot be accessed. For example, the card may not be able to communicate with the ECC card.

Yes No

(1 of 10)



Cell Data Error (E) Port A cell data (DCHK) error is detected in the egress direction by the Switching Fabric subcard of the ECC card.

Yes No

Cell Data Error (I) Port A cell data (DCHK) error is detected in the ingress direction by the Switching Fabric subcard of the ECC card.

Yes No

Cell DCHK Error Subcard A cell data (DCHK) error is detected by the Switching Fabric subcard of the ECC card.

Yes No

Cell HEC Error Subcard A cell HEC error is detected by the Switching Fabric subcard of the ECC card.

Yes No

Cell Mapping Heterogeneous

Port The mapping modes between the ports on a DS3-2 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.

Yes No

Connection Download Failed

Node The Control subcard could not download the database for the interface card after the system restarted.

Yes No

Congested CPU Card Buffer utilization on the CPU has exceeded the MCT.

Yes No

CTL EDC Error Detected

Card A database checksum mismatch has been detected on the active ECC card. The mismatch indicates a single bit error that is correctable.

Yes No

CTL Uncorrectable EDC Err

Card A database checksum mismatch has been detected on the active ECC card. The mismatch indicates two or more bit errors that are not correctable.

Yes No

Data Collector Link Down

Card The data spooling ECC card cannot communicate with the data collectors or the connection has failed.

Yes No

Drop Bus X Failure Port The Switching Fabric subcard of the ECC card detects a drop bus failure that is signaled by two or more faults detected by the UCS cards on the X fabric.

Yes No

Drop Bus Y Failure Port The Switching Fabric subcard of the ECC card detects a drop bus failure that is signaled by two or more faults detected by the UCS cards on the Y fabric.

Yes No

Equipment Failure Card The DS3 or E3 CCE-2 card, or the E1 or T1 card has detected an equipment failure.

Yes No

Fab Cfg: Connects Deleted

Card Connections are deleted from the switch database because of a change in the fabric configuration.

Yes No

Fan Failed Shelf-fan 1 A fan in the cooling unit is not operating. The fan number is always 1.

Yes No

FlashDisk Capacity Too Low

Subcard The installed FlashDisk is a smaller capacity than required by this platform.

No No

Gender Mismatch Port The gender of the attached MAU does not match the configured port gender.

Yes No

HDWR Device Fault Subcard slot A hardware device of the Switching Fabric subcard has failed its periodic sanity check.

Yes No


Self-clearing alarm

(2 of 10)



Hierarchy Not Supported

Card PNNI hierarchy has been configured on the switch, but the present ECC card does not support PNNI hierarchy.

Yes No

ICTL EDC Error Detected

Card A database checksum mismatch has been detected on the inactive ECC card. The mismatch indicates a single bit error that is correctable.

Yes No

ICTL Uncorrectable EDC Err

Card A database checksum mismatch has been detected on the inactive ECC card. The mismatch indicates two or more bit errors that are not correctable.

Yes No

Idle Signal Port An idle signal has been detected on the incoming line.

Yes No

ILMI Link Down Port The ILMI link has failed. Yes No

IMA: Fault declared at NE

IMA link The near-end IMA group declared an implementation-specific fault.

Yes No

IMA: FE Indicates Start-Up

IMA group The far end indicates a Start Up status, but the near end does not indicate a Start Up (Akn) or a Config Abort status.

Yes No

IMA: FE Insuff. Links IMA group The far-end IMA group has fewer than the required P value Tx and Rx links active.

Yes No

IMA: FE Link Unusable

IMA link Link forced to Unusable because of a link Unusable state detected at the far end.

Yes No

IMA: FE reports Blocked

IMA group The far end reports that it is blocked. Yes No

IMA: FE rpts unaccept.Conf

IMA group The far end reports unacceptable configuration parameters.

Yes No

IMA: Insufficient–Links

IMA group The near-end IMA group has fewer than the required P value Tx and Rx links active.

Yes No

IMA: Link Mis-connected

IMA link The Tx link is detected as misconnected. Yes No

IMA: Loss of Delay Sync

IMA link There is a persistent near-end LODS defect. Yes No

IMA: Loss of IMA Frame

IMA link There is a persistent near-end LIF defect. Yes No

IMA: Remote Failure Ind.

IMA link There is a persistent RDI-IMA defect at the near-end.

Yes No

IMA Version, Rev. Mismatch

Card The configured IMA version is not supported by the installed PRI line card.

Yes No

Inactive Database Not Sync

Card slot The database on the inactive ECC card is not synchronized with the database on the active ECC card.

Yes No

Incompatible Software

Card The inactive ECC card is running a version that 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.

No No

Incorrect Memory Module

Card The installed memory module is incompatible with the combination of hardware and software on the card.

No No


Self-clearing alarm

(3 of 10)



Insufficient CPU Resources

Card slot The packet processor has insufficient resources to support the connections configured through the card. The card temporarily disables all connections.

Yes No

Invalid PPC Module Present

Card An invalid PPC module has been detected. No No

LGN Rx Lower Level PTSE

Node A PTSE has been received by a logical node from 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.

No No

Line AIS Port A line-layer AIS condition has been detected on the incoming signal.

Yes No

Line Loopback Activated

Port A remote loopback is requested and is active. Yes No

Line RDI Port A line-layer RDI condition has been detected on the incoming signal.

Yes No

Link Integrity Lost Port The system does not detect receive data input or link integrity pulses.

Yes No

LOF Interface circuit

The DS1 circuit has detected an LOF condition on the incoming signal. LOF is caused by the DS1 or DS3 port experiencing an LOS or LOF.

Yes No

Regenerated circuit

The DS1 circuit has detected an LOF condition on the incoming signal. LOF is caused by the DS1 or DS3 port experiencing an LOS or LOF.

Yes No

Port An LOF condition has been detected on the incoming signal. LOF is caused by a faulty connection or cable, a faulty remote card, or a high bit error rate on the line.

Yes No

LOR Port The Far End Ready signal is de-asserted while the clock signal is present.

Yes No

LOS Port or circuit An LOS condition has been detected on the 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.

Yes No

Loss of Cell Del Port A failure to detect the ATM cell boundary has occurred on the incoming signal.

Yes No

Loss of Pointer Port An LOP condition has been detected on the incoming signal.

Yes No

LOSW Port An LOSW condition has been detected on the incoming signal.

Yes No

Low Number PNNI PTSE Bufs

Node The PNNI application is running low of PNNI PTSE buffers.

No No

LowSNR Port A low signal-to-noise ratio has been detected on an SHDSL port.

Yes No


Self-clearing alarm

(4 of 10)



LPR Port A loss of power has been reported by the dying 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.

Yes No

Major Backg DIAG Failure

Card slot, subcard or module

A background diagnostic test failed. (1) Yes No

Major Directed DIAG Failure


A directed diagnostic test failed. (1) Yes No

Major Startup DIAG Failure


A startup diagnostic test failed. (1) Yes No

Many PVC Alarms Stream The rate for the PVC alarm filter has been exceeded.

Yes No

Many Stream Alarms Stream The rate for the stream alarm filter has been exceeded.

Yes No

MAU Missing Card No MAU is installed for the ISC card. Yes No

MFR Feature Not Supported

Card The installed frame relay card does not support the MFR feature.

No No

MFR Out of Service MFR bundle An MFR bundle is out of service because the ISR of a MFR bundle is zero.

Yes No

Negotiation Failed Port The autonegotiation process failed. Yes No

NNI Signaling Link Down

Port The alarm text reflects the operational status of NNI links.

Yes No

No Support for ILMI 4.0

Card This alarm is raised when a line card does not support ILMI 4.0.

No No

Not Talking to Mate Ctl

Card slot The active and inactive ECC cards cannot communicate with each other.

Yes No

NTP Not Synchronized

Card slot The active and inactive ECC cards have lost NTP synchronization.

Yes No

NVM Maintenance Required

System The NVM auditor raises this alarm if the file system audit fails.

Yes No

Optical Failure Port A problem has been detected on the laser monitoring function. The alarm indicates that the lifetime of the laser is nearly over and should be replaced.

Yes No


Self-clearing alarm

(5 of 10)



Out of PNNI Resources

System The PNNI protocol has no more operational resources. The location field of the alarm indicates the logical node instance that is out of resources and the type of resource identifier. The type of resource identifier is an integer that describes an internal switch resource and is defined as follows:

• Res-5 - out of topology database peer group resource

• Res-6 - out of topology database node resource• Res-7 - out of topology database horizontal link

resource• Res-8 - out of topology database up-link

resource• Res-9 - out of topology database TLV resource• Res-10 - out of topology database PTSE buffer

resource• Res-11 - out of horizontal link FSMs resource• Res-12 - out of NRM link info items resource• Res-13 - out of NRM PTSE Identifier item

resource• Res-14 - out of NBR link Id items resource• Res-15 - out of NBR peer re-transmission list

items resource• Res-16 - out of PTSE Utils PTSE key items

resource• Res-17 - out of SVCC Hello FSMs resource• Res-18 - out of PDU PTSE offset items

resource• Res-19 - out of topology db ancestor neighbor

table entry items resource• Res-22 - out of topology summary adjacency

free list resource• Res-23 - out of NRM address info table entry

items resource• Res-24 - out of address routing table entries

resource

No No

P2MP Failed on Inactive

Card slot If the P2MP set fails on the inactive card, this alarm is raised on the active card to notify the user that the connection has been removed on the inactive card.

No No

P2P Failed on Inactive

Card slot If the P2P set fails on the inactive card, this alarm is raised on the active card to notify the user that the connection has been removed on the inactive card.

No No

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 the incoming signal.

Yes No

Path RDI Port A path-layer RDI condition has been detected on the incoming signal.

Yes No


Self-clearing alarm

(6 of 10)



Path Trace Mismatch Port A path trace mismatch has been detected. Yes No

Payload Loopback Activated

Port A local payload loopback has been initiated from the far end.

Yes No

PCMCIA Recovered Error

Subcard There has been an internal PCMCIA module failure. No No

Peer Group Mismatch

PNNI link The nodes at each end of the PNNI link are not in the same peer group.

Yes No

PLCP-LOF Port An LOF condition has been detected at the PLCP layer of the incoming signal.

Yes No

PLCP-RDI Port or circuit An RDI condition has been detected at the PLCP layer of the incoming signal.

Yes No

PNNI Addr Advert Thresh

Port or circuit The number of advertised addresses across all 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.

Yes No

PNNI_Not Enough Memory

System Downloading PNNI node configuration has failed because of insufficient memory on the ECC card.

Yes No

PNNI Link Down PNNI link The PNNI link has an operational status of down. Yes No

PNNI Loop Back Detected

PNNI link A loopback is running on the PNNI link. Yes No

PNNI SVCC Link Down

Link The PNNI SVCC RCC to an adjacent LGN is down. Yes No

PNNI TimeToFlush Reach Max

Node A PTSE is having trouble being flushed by a PGL. No No

Port Diagnostic Fault Port The port is not responding to the system or has failed startup diagnostics.

No No

Port in Reset Port or circuit The port is has been reset. Yes No

Port OOS Port or circuit The port is out of service. Yes No

Power Supply Failed Shelf-BRKR -module-zone

A power failure has been detected. 1 or 2 indicates the power module. A or B indicates the power zone. Check the input connections and the circuit breaker.

Yes No

PPC Module Mismatch (2)

Card A configured module is not installed or the wrong type of module is installed.

No No

Processor Failure Card slot Card diagnostics have detected a processor failure on the card.

Yes No

Protection Lost Card, module, or port

A condition is present that prevents the protection 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.

Yes No

PTSE Rxd Not From PG

System A PTSE that is not from this peer group is received. No No

PTSE Too Big For Database

System A PTSE that is too big for the PNNI node database is received.

No No


Self-clearing alarm

(7 of 10)



QoS Guarantees Lost

Card QoS guarantees are lost. No No

QoS Routing Not Supported

Card This alarm indicates that the ECC card does not support the QoS Routing feature.

Yes No

RAM Parity Error Subcard RAM Parity errors in the datapath RAM on the Switching Fabric subcard of the ECC card have been detected.

Yes No

RDI Port, circuit, or IMA group

An RDI condition has been detected on the 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.

Yes No

Revision/Feature Mismatch

Card The card has an incompatible version of hardware or software.

No No

Section LOF Port An LOF condition has been detected at the section-layer of the incoming signal.

Yes No

Section LOS Port An LOS condition has been detected at the section-layer of the incoming signal.

Yes No

Signal Degrade Port The card or module has passed the BER threshold for signal degrade.

Yes No

Signal Failure Port The card or module has passed the BER threshold for signal fail.

Yes No

Signaling Link Down Port The system has failed to correct a signaling link. Yes No

Sig Profile Not Supported

Card slot The active ECC card that provides the call processing application does not support the signaling protocol. The subcode provides the signaling profile number.

No No

Slave 1 Processor Failure

Card slot The Slave 1 processor has failed. Yes No







Sonet/SDH Mismatch

Port The protocol received on a port does not match the protocol configured on the port.

Yes No

Sparing Bus Fault Card slot of protection card

A fault is detected by the sparing bus integrity 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

Yes No

Spare Sectors Exhausted

Subcard The Control subcard has exhausted all available sectors.

No No

SPVC Config Limit Exceeded

Card There are more SPVCs configured in the database than are supported by the PM hardware.

No No


Self-clearing alarm

(8 of 10)



Starvation Circuit The playout buffer on the circuit has underrun. Yes No

Channel group The playout buffer on the channel group has underrun.

Port The playout buffer on the port has underrun.

AAL-1 multiplexer

The playout buffer for an AAL-1 multiplexer starved for an amount of time equal to the configured alarm declaration time.

Stream Out of Service

Stream The frame stream has been put into an inactive state because of a failure of the link management protocol.

Yes No

SVC Routing Tbl Thresh

System A SVC routing table is overloaded. The number of 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).

Yes No

SW Generic Not Supported

Subcard The software generic load is not supported on the Control subcard or Switching Fabric subcard of the ECC card.

No No

System Restart (2) Card slot The active ECC card has reset. No No

TAC Failed on Inactive

Port This alarm is raised on the active port to notify the user that the connection is removed and inactive.

No No

TCA (DXI Card Cong): 1 Hr

Card slot The congestion statistics on a circuit emulation card have exceeded the defined threshold during a 1-h interval.

No Yes

TCA (DXI Strm Cong): 1 Hr

Stream The congestion statistics on the stream have exceeded the defined threshold during a 1-h interval.

No Yes

TCA (FR Card Cong): 1 Hour

Card slot The congestion statistics on the frame relay card have exceeded the defined threshold during a 1-h interval.

No Yes

TCA (Stream Cong): 1 Hour

Stream The congestion statistics on the frame stream have exceeded the defined threshold during a 1-h interval.

No Yes

Too Many Alarms (3) Card The number of alarm records logged to the queue exceeds the queue size.

No No

Too Many Connections

Card The number of connections exceeds capacity. Yes No

Too Many Neighbors PNNI link The maximum number of PNNI neighbors has been exceeded.

Yes No

Too Many Parallel Links

PNNI link The maximum number of PNNI links between the same two PNNI nodes has been exceeded.

Yes No

Too Many VCC-SW mode VPIs

Card There are more than 16 VPIs in VCC switch mode. Yes No

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 of an E1 port.

Yes No

TS16 LOF Port An LOF condition has been detected on timeslot 16 of an E1 port.

Yes No


Self-clearing alarm

(9 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.

TS16 RDI Port An RDI condition has been detected on timeslot 16 of an E1 port.

Yes No

Wrong CE HW Rev for EC

Card Echo cancellation functionality is not available because a CE-EC-128 module has been installed onto an old revision of a CE card. A hardware modification is required for the CE-EC module to be usable with the card.

Yes No

Wrong CE SW Rev for EC

Card Echo cancellation functionality is not available because the CE card is running an earlier version of software that does not support echo cancellation. The CE card software must be upgraded.

Yes No

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.

Yes No

Wrong SW Rev for CR/IMA Module

Card A CR/IMA module is configured for a slot that contains a supported card, and the software on that card does not support the CR/IMA functionality.

Yes No

X Egress Cell Data Error

Card The fabric application raises this alarm when a UCS 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.

Yes No

X Egress HEC Error Card The fabric application raises this alarm when a UCS 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.

Yes No

X UCS Unreachable Error

Card The ECC card installed in slot X cannot communicate with the UCS listed in the alarm field.

Yes No

Y Egress Cell Data Error

Card The fabric application raises this alarm when a UCS 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.

Yes No

Y Egress HEC Error Card The fabric application raises this alarm when a UCS 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.

Yes No

Y UCS Unreachable Error

Card The ECC card installed in slot Y cannot communicate with the UCS listed in the alarm field.

Yes No


Self-clearing alarm

(10 of 10)



Table 153-3 System restart alarm subcodes

Subcode Description

Db The database is restored.

Dmt A ECC card activity switch has occurred as a result of the active card having more demerits than the inactive card.

Net The 5620 NM has reset the ECC card.

Pwr The system is powered up.

Rls A ECC card activity switch initiated by the user has occurred.

Sys01 A watch dog timer has timed out.

Sys02 The RDS has reset.

Sys03 The processor executed a RESET instruction.

Sys04 Activity is lost.

Sys05 An unknown alarm has caused the system to restart.

Sys06 An OS Call caused the system to reboot.

Sys07 There is a diagnostic fatal error.

Sys08 An exception is raised.

Sys09 An exception is raised on the interrupt level.

Sys10 An exception occurred before the kernel initialized.

Sys11 A block corruption occurred in the memory header.

Sys12 A block corruption in the memory trailer has occurred.

Sys13 A memory free tracked block mismatch occurred.

Sys14 A memory partition mismatch occurred.

Sys15 A memory free fails occurred.

Sys16 A semaphore create failure occurred.

Sys17 A TCBE Task create error occurred.

Sys18 An invalid TCBE core pointer caused the system to reset.

Sys19 A TCBE hook error occurred.

Sys20 Both fabrics are unhealthy.

Sys21 The event monitor has reset the database.

Sys22 The event monitor has forced a reconciliation.

Sys23 The event monitor initializes the nonpersistent database.

Sys24 A task stack overflowed.

Sys25 A push-button restart occurred.

Sys26 An external signal is driving the RESET line.

Sys27 A double bus fault monitor caused the system to restart.

Sys28 A loss of clock occurred.

Sys29 The system became active while the database was not synchronized.

Sys30 An ATMizer failure occurred.

(1 of 2)



Sys31 A Switching Fabric Mate Link Timer 2 Timeout occurred.

Sys33 Out of memory buffers caused the system to restart.

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.

Sys38 There is no idle activity.

Sys39 The inactive ECC card received a Null object ID from the active ECC card.

Sys40 An error in the code space protection occurred.

Sys41 The card is in an errored state and has been unleashed.

Sys42 The card is unreachable by the ECC card.

Sys43 The card was not unleashed in 15 minutes.

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.

Sys48 An ISC instance was deleted/removed from a card.

Sys49 Out of system buffers.

Sys50 The system has detected an ECC error.

Sys51 The system does not detect the Distribution Panel.

Usr The node management session reset the ECC card.

Subcode Description

(2 of 2)


154 —Minor alarm descriptions

Table 154-1 New minor alarms 154-2

Table 154-2 Minor alarms 154-3

Table 154-3 Subcodes for fabric switch alarms 154-8


154 — Minor alarm descriptions

Table 154-1 New minor alarms


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 Support

Card A DBA-capable card is installed in a slot configured on the DBA fabric port, but it is running a software load that does not support DBA.



Table 154-2 Minor alarms


Self-clearing alarm

AIS Interface Circuit

The circuit has detected an AIS on the incoming line. 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.

Yes No

Regenerated Circuit

The circuit has detected an AIS on the incoming line. 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.

Port The port has detected an AIS on the incoming line. 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. Faulty local hardware can also cause AIS.

Alarm Card Removed

Shelf The Alarm card is not installed. Yes No

APS-FEPL Failure Card, module, or port

The far end protection line is in a Signal Fault condition.

Yes No

APS-Mode Mismatch

Card, module or port

The far end is provisioned for a different operational mode.

Yes No

Card Missing Card slot or subcard slot

There is only one ECC card installed in a fabric redundant system.

Yes No

Module The subslot is configured for a module but the subslot is empty at system startup.

Yes No

Card/Module Not Supported

Card slot This alarm is raised when an older version line card that is not supported is inserted.

No No

Card Variant Mismatch

Card or module

A slot is configured for a laser-reach variant other than the one installed in the slot.

Yes No

Card Version Mismatch

Card slot There is a difference between the configured variant and the installed variant types.

No No

CLI In Limit System There is an excessive number of incoming characters and the CLI cannot process all of them.

Yes No

Congestion Detected

Card slot A buffer on the card is experiencing prolonged severe congestion.

Yes No

CPSS Class A Mismatch

CPSS Link The far-end node of the CPSS link does not have the same class A address as the local node.

Yes No

Ctl Connect Module Removed

Shelf The ECCI is not installed. Yes No

Domain Mismatch CPSS Link The CPSS link is not set up because the near-end and far-end nodes are in different CPSS domains.

Yes No

Ethernet Port Down Card slot The Ethernet management port on the ECC card has lost connectivity to the Ethernet LAN.

Yes No

External Alarm Inputs ON

System The external alarm contacts are closed, indicating a fault condition on an external device.

Yes No

(1 of 5)



Fabric Switch to X (2) 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.

Yes No

Fabric Switch to Y (2) 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.

Yes No

Far End Critical Failure

System The Far End Critical Failure is generated when the far-end equipment indicates that it has a failure that requires attention.

Yes No

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 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.

Yes No

Far End LOF Port The system has received a DS3 LOF FEAC 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.

Yes No

Far End LOS Port The system has received a DS3 LOS FEAC codeword from the far end. A local hardware fault, a faulty connection or cable, or a faulty or missing remote card causes an LOF.

Yes No

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 status of the link is still down.

Yes No

IbIP Loopback Detected

IbIP link The far-end IP address is the same as the local In-band IP address.

Yes No

IbIP Link Arp Timeout

IbIP link The node timed out while waiting for a reply to an Inverse ATM ARP request.

Yes No

Idle Signal Port The port has received a DS3 payload that contains the idle signal.

Yes No

Label Mismatch Port A signal label mismatch is detected on the incoming signal.

Yes No

LAN overrun Card slot One or more LAN frames have been lost due to an overrun condition.

Yes No

Link Down Port A physical port has failed, or the CPSS has timed out for other reasons.

Yes No

Link Time-out Port The far-end device has stopped responding, or there is no CPSS link configured on the far-end device.

Yes No

Link Up - Parallel Link

Port The CPSS link is inactive because another CPSS link already has an active connection with the far-end device. The inactive link acts as a backup.

No Yes


Self-clearing alarm

(2 of 5)



Loopback Detected Port The CPSS nodes at the two ends of the link have the same node number, or there is a physical connection error and both ends of the CPSS link are physically connected to the same node.

Yes No

Loss of Synch Card slot The SSU is receiving an impaired signal because of LOS, AIS, or an out-of-range frequency.

Yes No

Many UNI ILMI Links Down

Port This alarm is raised when more than 16 UNI ILMI links have gone down. This alarm is not cleared until all UNI links are up.

Yes No

MFR B/W Insufficient

MFR bundle The MFR bundle has insufficient bandwidth because the ISR is less than CSR.

Yes No

Minor Backgr DIAG Failure

Card, subcard or module


Minor Directed DIAG Failure



Minor Startup DIAG Failure



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.

Yes No

Non-Routable Port The CPSS link to the stub node cannot route to the active network management system.

Yes No

Not Using Pref Fabric

Card slot 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.

Yes No

OAM Ingress Overflow

Card slot The card is receiving OAM cells on too many endpoints.

Yes No

OAM LNK E2E VC-LOC

Endpoint A VC end-to-end endpoint with link OAM CC enabled has declared a LOC defect state condition.

Yes No

OAM LNK E2E VP-LOC

Endpoint A VP end-to-end endpoint with link OAM CC enabled has declared a LOC defect state condition.

Yes No

OAM LNK SEG VC-LOC

Endpoint A VC segment endpoint with link OAM CC enabled has declared a LOC defect state condition.

Yes No

OAM LNK SEG VP-LOC

Endpoint A VP segment endpoint with link OAM CC enabled has declared a LOC defect state condition.

Yes No

OAM MATX E2E VC-LOC

Endpoint A VC end-to-end endpoint with matrix OAM CC enabled has declared a LOC defect state condition.

Yes No

OAM MATX E2E VP-LOC

Endpoint A VP end-to-end endpoint with matrix OAM CC enabled has declared a LOC defect state condition.

Yes No

OAM MATX SEG VC-LOC

Endpoint A VC segment endpoint with matrix OAM CC enabled has declared a LOC defect state condition.

Yes No

OAM MATX SEG VP-LOC

Endpoint A VP segment endpoint with matrix OAM CC enabled has declared a LOC defect state condition.

Yes No


Self-clearing alarm

(3 of 5)



OAM VC-AIS Endpoint A VC endpoint with OAM-AIS enabled on a UNI or B-ICI boundary has entered the AIS state. The alarm includes a timestamp of the date and time of the connection failure, or N/A if the alarm was raised after the AIS threshold was crossed.

Yes No

OAM VC-RDI Endpoint A VC endpoint with OAM-AIS enabled on a UNI or B-ICI boundary has entered the RDI 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 RDI threshold is crossed.

Yes No

OAM VP-AIS Endpoint A VP endpoint with OAM-AIS enabled has entered 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.

Yes No

OAM VP-RDI Endpoint A VP endpoint with OAM-RDI enabled has entered 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.

Yes No

Overrun Port The playout buffer on the port has overrun. Yes No

Channel group

The playout buffer on the channel group has overrun.

Circuit The playout buffer on the circuit has overrun.

RAI Interface Circuit

The DS1 circuit has received an RAI from the far end; this indicates that the far end has detected an error on the incoming signal.

Yes No

Regenerated Circuit

The DS1 circuit has received an RAI from the far 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 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.

Yes No

Slot Sync Loss Card slot This alarm indicates that the line card in the UCS slot 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.

Yes No

SPVC Priority Rpting Off

Card slot The ECC card does not support prioritized SPVC status reporting. Configured values for report priority and hold-down time will not be used.

Yes No


Self-clearing alarm

(4 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.

SVCC RCC Diag Failure

Link Indicates that a diagnostic test has failed for a 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.

Yes No

Synch Source Failure

Port or circuit The SSU cannot derive timing from the specified synchronization source, and has switched to the next available source.

Yes No

Starvation (AAL2) AAL2 channel

The playout buffer for an AAL2 channel starved for an amount of time equal to the configured alarm declaration time.

Yes No

Synch Unit Range Exceeded

Port The specified synchronization source has become impaired because its frequency is out of range and the SSU cannot derive timing from the signal frequency.

Yes No

TCA (DXI Card Cong): 1 Hr

Card slot The congestion statistics on a circuit emulation card have exceeded the defined threshold during a 1-h interval.

No Yes

TCA (DXI Strm Cong): 1 Hr

Stream The congestion statistics on the stream have exceeded the defined threshold during a 1-h interval.

No Yes

TCA (FR Card Cong): 1 Hour

Card slot The congestion statistics on the frame relay card have exceeded the defined threshold during a 1-h interval.

No Yes

TCA (Stream Cong): 1 Hour

Stream The congestion statistics on the frame stream have exceeded the defined threshold during a 1-h interval.

No Yes

Too Many Alarms (3) Card slot The number of alarm records logged to the queue exceeds the queue size.

No No

TS16 AIS Port There is an incoming AIS on timeslot 16 of an E1 port which is one of the tributaries of an E3 CCE-2.

Yes No

UNI ILMI Link Down Port An ILMI link failure has occurred. Yes No

UNI Signaling Link Down

Port The operational status of the UNI signaling link is down.

Yes No

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 Not Support

Card slot A DBA-capable card is installed in a slot configured on the DBA fabric port, but it is running a software load that does not support DBA.

Yes No

Wrong Card in Slot Card, subcard, or module

A slot is configured for a card, subcard or module type other than the one installed in the slot, or the slot has been configured as EMPTY.

No No


Self-clearing alarm

(5 of 5)



Table 154-3 Subcodes for fabric switch 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.


155 —Diagnostic alarm descriptions

Table 155-1 New diagnostic alarms 155-2

Table 155-2 Diagnostic alarms 155-3

Table 155-3 Alarm subcodes for diagnostic faults 155-9

Table 155-4 TCA alarm subcodes 155-10


155 — Diagnostic alarm descriptions

Table 155-1 New diagnostic alarms


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 link

An MFR bundle link is out of service as the LIP procedures determine that the link is in a state other than up.

Port Activity Gained Port A port involved in a protection group is inactive.



Table 155-2 Diagnostic alarms


Self-clearing alarm

Activity Change Due to Demerits

Card This alarm indicates that a ECC card has become active because it has fewer demerits than its mate ECC card.

No Yes

Adapter Card Absent Card slot The card in a protection group is installed, but it has detected that the adapter card is absent.

No Yes

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.

No Yes

APS-Maint Oper Card, module, or port

A maintenance operation is being performed on a card or module 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

No Yes

APS-Remote Maint Oper Card, module, or port

A maintenance operation initiated from the remote side is being performed on a card or module 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

No Yes

Background DIAG Failure



Card Activity Gained Card slot or module

A card or module involved in a protection group is in service.

No Yes

(1 of 7)



Card Activity Lost Card slot or module

A card or module involved in a protection group is 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

No Yes

Card Diagnostic Fault (2) Subcard The Control subcard or/and the Switching Fabric subcard of the ECC card is not responding to the system, or has failed one or more diagnostic tests during power-up.

No No

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 that has experienced a hard reset.

No No

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 failed due to the restrictions imposed by the software on the ECC card.

No Yes

Card Revs Too Old Card slot The card failed the minimum revision check. No Yes

Congested Frame Stream

Port Buffer utilization for the frame stream has exceeded the MCT configured for the stream.

Yes No

Congested Slot Card slot The switching processor on the card has entered the severely congested state and is out of memory.

Yes No

Connect Diagnostic Card slot A connection message from the ECC to the line card may not have been successfully downloaded three consecutive times; therefore, the connection may not be able to pass traffic.

No Yes

Data Collector Switch Over

Card slot The data spooling ECC card has switched its connection from the active to the inactive collector.

No Yes

Database Transfer Failed

Card slot The database transfer between the active and inactive ECC card has failed.

No Yes


Self-clearing alarm

(2 of 7)



DBC Source Build Type System The source system is running an unofficial version of software and the destination system is running a hardened software load.

No Yes

DBC Target Build Type System The destination system is running an unofficial version of software and the source system is running a hardened software load.

No Yes

DBC Version Incompatible

System The version of the database installed is incompatible with the system.

No Yes

Directed DIAG Failure Card, subcard or module


Directed HReset Card slot An operator has performed a hard reset of a card for a maintenance activity.

No No

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.

No No

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.

No No

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 is a stub node and the far end is a network management system or stub node.

No Yes

FDB Overflow Port The Ethernet port filtering database overflowed 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.

Yes No

Interface Rate Change Port The Ethernet port rate configuration has changed due to autonegotiation.

No Yes

Invalid Dest IP Port A CPSS link detects an invalid source IP address: 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.

Yes No

Invalid Src IP Port The CPSS link detects an invalid source IP 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.

Yes Nos

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.

No Yes

Max num NetMgrs Configured

Port The system tried to configure more than the allowed number of network management systems.

No Yes


Self-clearing alarm

(3 of 7)



Max num Routers Configured

Port The system tried to configure more than the allowed number of CPSS routing nodes.

No Yes

Max num Stubs Configured

Port The system tried to configure more than the allowed number of CPSS stub nodes.

No Yes

MFR BL Out of Service MFR bundle link

An MFR bundle link is out of service as the LIP procedures determine that the link is in a state other than up.

Yes No

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 because its child node has been elected PGL

No No

PNNI LGN Oper Down Card slot A logical node has become operational DOWN because its child node has abdicated PGL election responsibilities.

No No

Port Activity Gained Port A port involved in a protection group is inactive. No Yes

Power Module Removed Shelf- module

A power module is not installed and is indicated by A or B.

Yes No

PVC Active Endpoint The link management protocol configured on the stream has changed the DLC status from inactive to active.

No Yes

PVC Added Endpoint The link management protocol configured on the port has confirmed the addition of a PVC.

No Yes

PVC Deleted Endpoint The link management protocol configured on the port has confirmed the deletion of a PVC.

No Yes

PVC Inactive Endpoint The link management protocol configured on the port has changed the DLC status from active to inactive.

No Yes

PVC Unconfigured Endpoint The link management protocol configured on the 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.

No Yes

Rate Limit, Rev Mismatch

Port The installed line card does not have the version of software needed to support the rate limit feature.

No No

Rate Limit, ABR-UBR CAC

Port The virtual bandwidth used by all the ABR and UBR connections together exceeds the available bandwidth qualified by the configured rate limit for the port.

No No

Rate Limit, NRT-VBR CAC

Port The virtual bandwidth used by all nrt-VBR connections together exceeds the bandwidth qualified by the configured rate limit for the port.

No No

Reconcile Restarted Card slot The card restarted after a database download, but the active and the inactive database did not reconcile.

No Yes

SNMP Authentication Failure

System An SNMP manager did not use any of the configured access community names or IP addresses when it tried to access the SNMP agent.

No Yes


Self-clearing alarm

(4 of 7)



Startup DIAG Failure Card, subcard or module


Stream Config. Correct Stream The frame stream is in service and the DLC 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.

No Yes

Stream Config. Mismatch Stream The frame stream is in service and the DLC 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.

No Yes

TCA (AAL1Perf): 15 Min Endpoint The 15-min AAL-1 statistics parameter has been exceeded on a connection of a circuit emulation card.

No Yes

TCA (AAL1Perf): 24 Hour

Endpoint The 24-h AAL-1 statistics parameter has been exceeded on a connection of a circuit emulation card.

No Yes

TCA (DS1-Line): 15 Min Port The 15-min TCA line statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DS1-Line): 24 Hour Port The 24-h TCA line statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DS1-Line-FE): 15 Min

Port The 15-min TCA far end statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DS1-Line-FE): 24 Hour

Port The 24-h TCA far end Line statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DS1-Path): 15 Min Port The 15-min TCA path statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DS1-Path): 24 Hour

Port The 24-h TCA path statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DS1-Path-FE): 15 Min

Port The 15-min TCA far end path statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DS1-Path-FE): 24 Hour

Port The 24-h TCA far end path statistics threshold has been exceeded on the DS1 port.

No Yes

TCA (DXI Stream): 1 Hour

Card slot The threshold of a given DXI Layer 2 gauge is exceeded on a DXI stream.

No Yes

TCA (E1-G 821): 15 Min Port The 15-min TCA G.821 statistics threshold has been exceeded on the E1 port.

No Yes

TCA (E1-G 821): 24 Hour Port The 24-h TCA G.821 statistics threshold has been exceeded on the E1 port.

No Yes

TCA (E1-G 821-FE): 15 Min

Port The 15-min TCA far end G.821 statistics threshold has been exceeded on the E1 port.

No Yes

TCA (E1-G 821-FE): 24 Hour

Port The 24-h TCA G.821 statistics threshold has been exceeded on the E1 port.

No Yes


Self-clearing alarm

(5 of 7)



TCA (E1-LineEr): 15 Min Port The 15-min line error statistics threshold has been exceeded on the E1 port.

No Yes

TCA (E1-LineEr): 24 Hour

Port The 24-h line error statistics threshold has been exceeded on the E1 port.

No Yes

TCA (E1-LineEr-FE): 15 Min

Port The 15-min far end line error statistics threshold has been exceeded on the E1 port.

No Yes

TCA (E1-LineEr-FE): 24 Hour

Port The 24-h far end line error statistics threshold has been exceeded on the E1 port.

No Yes

TCA (Egress Cell Data Err)

Card slot A line card has detected egress cell data errors. No Yes

TCA (Fabric Path) Port Fabric errors on the Switching Fabric subcards have generated a threshold crossing alert once during a 15-min interval.

No Yes

TCA (Line): 15 Minute (3) Port A statistic at the line layer has exceeded the defined threshold during a 15-min interval.

No Yes

TCA (Line): 24 Hour (3) Port A statistic at the line layer has exceeded the defined threshold during a 24-h interval.

No Yes

TCA (G.SHDSL): 15 Minute

Port The configured 15-min threshold has been exceeded for one of the following statistics (identified in the alarm subcode for an SHDSL card):

• LOSS• LOSWS• LowSNRS• LPRS• ES• SES• UAS

No Yes

TCA (G.SHDSL): 24 Hour

Port The configured 24-h threshold has been exceeded for one of the following statistics (identified in the alarm subcode for an SHDSL card):

• LOSS• LOSWS• LowSNRS• LPRS• ES• SES• UAS

No Yes

TCA (Line-FE): 15 Minute (3)

Port A statistics counter at the far-end line layer has exceeded the defined threshold during a 15-min interval.

No Yes

TCA (Line-FE): 24 Hour (3)

Port A statistic at the far-end line layer has exceeded the defined threshold during a 24-h interval.

No Yes

TCA (Path): 15 Minute (3) Port A statistic at the path layer has exceeded the defined threshold during a 15-min interval.

No Yes

TCA (Path): 24 Hour (3) Port A statistic at the path layer has exceeded the defined threshold during a 24-h interval.

No Yes


Self-clearing alarm

(6 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.

Table 155-3 Alarm subcodes for diagnostic faults

TCA (Path-FE): 15 Minute (3)

Port A statistic at the far-end path layer has exceeded the defined threshold during a 15-min interval.

No Yes

TCA (Path-FE): 24 Hour (2)(3)

Port A statistic at the far-end path layer has exceeded the defined threshold during a 24-h interval.

No Yes

TCA (PLCP): 15 Minute (3)

Port A statistic at the PLCP layer has exceeded the defined threshold during a 15-min interval.

No Yes

TCA (PLCP): 24 Hour (3) Port A statistic at the PLCP layer has exceeded the defined threshold during a 24-h interval.

No Yes

TCA (PLCP-FE): 15 Minute (3)

Port A statistic at the far-end PLCP layer has exceeded the defined threshold during a 15-min interval.

No Yes

TCA (PLCP-FE): 24 Hour (3)

Port A statistic at the far-end PLCP layer has exceeded the defined threshold during a 24-h interval.

No Yes

TCA Profile CLI Affected Port The TCA profile has been changed through the command line interface and may not be the same as the rest of the network.

No Yes

TCA (Section): 15 Minute (3)

Port A statistic at the section-layer has exceeded the defined threshold during a 15-min interval.

No Yes

TCA (Section): 24 Hour (3)

Port A statistic at the section-layer has exceeded the defined threshold during a 24-h interval.

No Yes

Too Many Alarms (4) Card slot The number of alarm records logged to the queue has exceeded the queue size.

No No


Self-clearing alarm

(7 of 7)

Subcode Description

DS3 UFR and E3 UFR

01 HP IPC Interrupt Test

02 FPGA Download Test

04 Common DRAM Test

08 FP SRAM Test

10 SAR SRAM Test

20 SAR Diagnostic

40 CAM Diagnostic

(1 of 2)



Table 155-4 lists the subcodes that can appear with the TCA alarms.

Table 155-4 TCA alarm subcodes

80 Datapath Diagnostic

100 —

Subcode Description

CV Code violation

ES Errored seconds

SES Severely errored seconds

SEFS Severely errored framing seconds

UAS Unavailable seconds

ESA Errored seconds, type A

BES Bursty errored seconds

SEF Severely errored frames

MCT Mild congestion threshold

SCT Severe congestion threshold

FC Failure count

Subcode Description

DS3 UFR and E3 UFR

(2 of 2)


Date post:	17-Nov-2014
Category:	Documents
Upload:	nghiatt
View:	668 times
Download:	4 times

A7670 Alarm Dictionary

Documents