Guest

Cisco ONS 15300 Series

Common Alarms and Events Supported by ONS 15305 and ONS 15302

Document ID: 64208

Updated: Oct 05, 2005

   Print

Introduction

This document explains the most common alarms that ONS 15305 supports. Many of these alarms are also applicable to ONS 15302, except for some differences in default severity for some of the alarms, because the products serve different roles in a network.

For an overview of the default alarm suppression list and persistency for each type of network element (NE), refer to the respective user guides.

Note: Ensure that you enable alarm reporting for modules and ports that are in use, because these parameters are disabled by default.

Note: Most alarm IDs with higher severity than “Warning”, which is an event, are on-off alarms (which are raised and cleared).

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

  • Cisco ONS 15305 and 15302

Components Used

The information in this document is based on the Cisco ONS 15305 and 15302.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Alarms and Events

This table describes the alarms and events on Cisco ONS 15305 and 15302:

Reference Number Object Default Severity Alarm Id (ProbCause) Description (ProbCauseQ) Detailed Description Troubleshooting (or) Comments
1 aiPort Warning alarmInp Alarm condition on alarm-in port The NEs provide four auxiliary alarm inputs (dry contact alarms) for associated equipment. For example, power module failure, battery condition, and open cabinet door. The operator can set the alarm to be triggered on either open or closed contact. -
2 au4 Minor ais Alarm Indication Signal (AIS) When an NE detects a defect in the regenerator section (RS) or the multiplexer section (MS) of an incoming link, the payload of that link is invalid. The NE then replaces the payload with an AIS in the forwarding direction. All subsequent NEs detect AU-4 AIS.

Note: By default, the alarm is suppressed.

If AIS occurs for AU-4, verify alarm conditions on sections between intermediate nodes on the path.
3 au4 Critical lop Loss Of Pointer AU-4 Loss of Pointer (LOP) occurs when an NE is unable to interpret the AU-4 pointer. This alarm normally indicates that the NE receives concatenated AU-4s when the NE actually expects non-concatenated AU-4s. Ensure that connected STM-n ports maintain the same structure on both ends.
4 au4 Major epj Excessive Ptr Justification This alarm appears if the number of Pointer justification events (PJEs) over a 15-minute period is greater than a threshold that you can configure, or the PJEL (Pointer Justification Event Limit). You can configure the PJEL individually for each AU-4 from 1 to 1024 events. The default configuration is 100 events per interval. PJE, both positive and negative justifications, are counted and measured over a 24-hour interval. Both current and past 24-hour interval counters are available. This alarm indicates synchronization problems in the network. The likely cause is that the devices operate with different sync-sources. For example, interconnected devices that operate in "free running" mode cause this alarm per AU-4 object. The alarm clears when the number of received pointer events is lower than the set threshold within a full 15-minute interval.
5 au4 Warning switchWork SNCP switched to “working” This event occurs if the traffic switches from “protecting” to “working”. Switching criteria depend on SNCP type. In other words, the criteria depend on whether SNCP is SNC/i or SNC/n. The main difference between the two is that in addition to a switch on AIS/LOP alarms, SNC/n also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
6 au4 Warning switchProt SNCP switched to “protecting” This event occurs if the traffic switches from “working” to “protecting”. Switching criteria depend on SNCP type. In other words, switching depends on whether SNCP is SNC/i or SNC/n. The main difference between the two is that in addition to switch on AIS/LOP alarms, SNC/n also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
7 au4-4c Minor ais Alarm Indication Signal When an NE detects a defect in the regenerator section (RS) or the multiplexer section (MS) of an incoming link, the payload of that link is invalid. The NE then replaces the payload with an AIS in the forwarding direction. All subsequent NEs detect AU-4-4c AIS.

Note: By default, the alarm is suppressed.

If AIS occurs for AU-4-4c, verify alarm conditions on sections between intermediate nodes on the path.
8 au4-4c Critical lop Loss Of Pointer AU-4-4c Loss of Pointer (LOP) occurs when an NE is unable to interpret the AU-4-4c pointer. This normally indicates that the NE receives non-concatenated AU-4s when the NE expects concatenated AU-4-4cs. Verify whether connected STM-n ports maintain the same structure on both ends.
9 au4-4c Major epj Excessive Ptr Justification Excessive Pointer justification (EPJ) alarm appears if the number of Pointer justification events (PJEs) over a 15-minute period is greater than a threshold that you can configure, or the PJEL (Pointer Justification Event Limit). You can configure the PJEL individually for each AU-4-4c from 1 to 1024 events. 100 events per interval is the default configuration. PJE, both positive and negative justifications, are counted and measured over a 24-hour interval. Both current and past 24-hour interval counters are available. This alarm indicates synchronization problems in the network. The likely cause is that the devices operate with different sync-sources. For example, interconnected devices that operate in "free running" mode cause this alarm per AU-4-4c object. The alarm clears when the number of received pointer events is lower than the set threshold within a full 15-minute interval.

Note: You can experience this alarm after an NE restart. If the network maintains synchronization, this alarm clears in less than 30 minutes.

10 au4-4c Warning switchWork SNCP switched to working This event occurs if the traffic switches from “protecting” to “working”. Switching criteria depend on the SNCP type. In other words, switching depends on whether SNCP is SNC/i or SNC/n. The main difference between the two is that in addition to switch on AIS/LOP alarms, SNC/n also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
11 au4-4c Warning switchProt SNCP switched to protecting This event occurs if the traffic switches from “working” to “protecting”. Switching criteria depend on the SNCP type. In other words, switching depends on whether SNCP is SNC/i or SNC/n. The main difference between the two is that in addition to switch on AIS/LOP alarms, SNC/n also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
12 auxIf Major lofTx Loss Of Frame This alarm appears when an unsupported signal type arrives. -
13 auxIf Major los Loss Of Signal This alarm appears when the AUX interface has no signal. -
14 device Critical ufail Device main unit failure This alarm appears if you encounter problems when you try to load FPGA, SPI/Eeprom, Power input, DXC inlet or XBAR on Main card. Restart or reboot the device. If the alarm persists, replace the device (because the error can be on the main-board).
15 device Major temp High temperature alarm This alarm appears if the temperature exceeds 450. For ONS 15305, both pair of Fans spin. Ensure that the combination of equipped modules in the chassis maintains the limit for maximum power consumption. Verify whether the environment that surrounds the device maintains proper ventilation.
16 device Major t0HoldOver T0 in holdover mode This alarm appears if none of the T0 synchronization candidates is available. -
17 device Critical t0Defect T0 SETG defect This alarm appears for defective hardware that impacts the internal T0 clock. Replace the chassis (because this error is on the main-board).
18 device Warning t0SyncSwitch T0 sync switchover This event occurs when automatic, manual or forced switchover occurs. -
19 device Warning t0QlFailed T0 sync candidate in fail This alarm applies to T1/T2/T3 sources member of the T0 synchronization table. -
20 device Warning t0QlDnu T0 sync candidate rec. DNU This alarm appears when T0 synchronization candidate receives the "DoNotUse" message. -
21 device Critical t4Squelch T4 output squelched This alarm appears when no T4 synchronization candidate has QL equal to or above QLmin -
22 device Critical inletFail DXC inlet failure When you power cycle (turn the power on or off at different temperatures) a device, the main card can fail to recover operations after the power on or off, and can remain in an alarm state. In such a state, the device does not carry traffic, and the card reports the "DXC inlet failure alarm." Restart or reboot the device. If the alarm persists, replace the device.
23 device Critical inletBitError DXC inlet bit error The DXC inlet bit error alarm appears on the device level to indicate a failure between the two DXC devices on the main-board. The system detects no failures in nominal conditions. -
24 device Warning unknownFlashType Unknown FLASH-device detected This alarm appears when the Flash-process discovers an unknown flash type on the main-board. Restart or reboot the device. If the alarm persists, replace the device.
25 device Warning errorNewBank ERROR in newest bank This error indicates that the main-board does not start up with the latest downloaded firmware. Download the firmware again.
26 device Warning alarmStormStart Alarm storm start detected This alarm indicates number of alarm status changes is too high for the device to report all alarms as traps. -
27 device Warning alarmStormEnd Alarm storm end detected This alarm appears when the number of alarm status changes reduces to a level where all alarms show up as traps again. In a situation where alarmStormStart appears, the current alarm-list can be wrong before alarmStormEnd appears. The list can show alarms that are no longer present, and there can be active alarms that are not in the list. Also, for some alarms, the time-stamp can be wrong. In this situation, the alarm history can also be wrong. Some alarm conditions could have been present and disappeared again, and probably did not appear in the alarm-lists. Also the time-stamps can be wrong on some alarms or events. After alarmStormEnd goes out, the system updates the current-alarm-list, and every alarm from that point in time appears in the alarm-history.
28 device Warning rxOverflow HWFault RX buffer overflow This alarm indicates an overflow of the receive buffers on the LAN interface. -
29 device Warning txOverflow HWFault Interport queue overflow This alarm indicates an interport queue overflow on the LAN interface. -
30 device Warning routeTable Overflow Routing table overflow This event occurs when the routing table exceeds 2048 entries. -
31 device Warning endTftp TFTP session completed This event occurs on successful completion of a TFTP session. -
32 device Warning abortTftp TFTP session aborted This event occurs when the completion of a TFTP session is unsuccessful. Check TFTP-server settings, and retry the transfer.
33 device Warning startTftp TFTP session initiated This event occurs when a download operation starts from the manager towards the NE. For example, a software upgrade or configuration file restore operation. -
34 device Warning forwardingTab Overflow Layer II Forward Table overflow This event indicates that the Unicast Global Forwarding table has reached the maximum limit on the number of MAC addresses. No new addresses are learned until old ones are removed (which can happen through aging, or when a link goes down, or when the operator removes them). You can configure the Unicast-Global- Forwarding table in the range 20-32767. 8192 entries is the default parameter.
35 device Warning vlanDynPortAdded Dynamic VLAN port added This event shows that the GVRP protocol dynamically adds a port to a VLAN. -
36 device Warning vlanDynPort Removed Dynamic VLAN port removed This event shows that the GVRP protocol dynamically removes a port from a VLAN. -
37 device Warning rsPingCompletion Ping sequence completed This event signifies the completion of a sequence of ICMP echos (Pings) initiated from the device. -
38 device Warning rlIgmpTable Overflow IGMP table overflow This alarm indicates that the maximum allowed entries in the IGMP table has been reached. -
39 device Warning rlIpFftStnOverflow IP SFFT overflow This alarm shows that the table that holds an individual IP address to forward data is full. -
40 e1Port Major lofRx Loss Of Frame downlink This alarm appears on E1 in PRA mode, when E1 receives the signal from the network in a format that E1 does not expect. -
41 e1Port Major lofTx Loss Of Frame uplink This alarm appears on E1 in PRA mode, when E1 receives the signal on the PDH port in a format that E1 does not expect. -
42 e1Port Minor aisRx AIS received downlink This alarm appears on E1 in PRA mode, when the network sends a signal with AIS to E1. This event indicates an alarm elsewhere in the network. -
43 e1Port Critical los Loss Of Signal This alarm appears when the E1 port does not receive a PDH signal. -
44 e1Port Warning loopClosed Loop closed This event occurs when you set a test-loop on an E1-port. -
45 e1Port Warning loopOpened Loop opened This event occurs when a test-loop clears on an E1-port. -
46 e3T3Port Minor aisRx AIS received downlink Not supported. -
47 e3T3Port Critical los Loss Of Signal This alarm appears when the E3 port does not receive a PDH signal. -
48 e3T3Port Warning loopClosed Loop closed This event occurs when you set a test-loop on an E3-port. -
49 e3T3Port Warning loopOpened loop opened This event occurs when a test-loop clears on an E3-port. -
50 eth Warning rldot1dStpPort StateForwarding Bridge port learning to forwarding state transition This message means that the STP port state for the given port has moved from Learning state to Forwarding state. The port now forwards traffic. This message indicates a topology change.
51 eth Warning rldot1dStpPort StateNotForwarding Bridge port forwarding to blocking state transition This message means that the STP port state for the given port has moved from the Forwarding state to the Blocking state. The port no longer forwards traffic. This message indicates a topology change.
52 fan Major fan Fan failure This alarm appears on the main-card when temperature rises above 850C. The alarm is specific for each fan. The main-card processes and presents this alarm as “Fan Failure Alarm”. The fan becomes active for a specified time (24 hours) when only two fans run. After the fans are active for the specified time, they stop, and the other fans become active. An alarm appears if a fan fails, and the other fans run continuously. You must replace the fan module now in order to protect the remaining fans, which no longer have protection.
53 fan Critical diagFail Diagnostic failure This alarm implies incorrect module identification. Replace the module.
54 fan Major inventoryFail Inventory failure This alarm indicates that inventory retrieved from the fan module does not match with expected inventory. Replace the module, even though the module can still be operational.
55 gfp Minor plm GFP payload mismatch This alarm appears due to a mismatch between expected and received PTI value in the GFP PTI field. Refer to ITU-T G.7041 for details. Check the configuration at both ends of the path.
56 gfp Minor upm GFP user payl. type mismatch This alarm appears when the received User Payload Identifier (UPI) is different from the expected UPI. This release supports the Frame-Mapped Ethernet UPI. Refer to alarm based on detection of UPI field value in ITU-T G.7041. Check the configuration at both ends of the path.
57 gfp Minor lfd GFP loss of frame delin. This alarm appears when the delineation process is not in SYNC state. -
58 gfp Minor exm GFP ex-header ident. mismatch This alarm appears when the received Extension Header Identifier (EXI) is different from the expected EXI. This release supports the Null Extension Header EXI. Refer to alarm based on detection of EXI field value in ITU-T G.7041. The opposite side port sends unsupported EXI.
59 gfp Minor pfm GFP payload FCS ident. mismatch This alarm appears when the received Payload FCS Indication (PFI) is different from the expected PFI. Refer to alarm based on detection of PFI field value in ITU-T G.7041. -
60 lanx Warning lanOn Link Up This event occurs as you try to connect the Ethernet LAN-port. -
61 lanx Warning lanOff Link Down This event occurs as you try to disconnect the Ethernet LAN-port. -
62 lcas Warning acMstTimeout Ack Mst Timeout This event indicates a Member Status Signal (MST) timeout. When you add a VC-n to the upstream capacity, MST=OK for this VC-n is expected to be received from the opposite end. If the source does not receive an MST=OK within a reasonable amount of time, the source declares a timeout. Check the configuration and cross-connects.
63 lcas Warning rsAckTimeout RS ACK Timeout This event indicates that an RS-sequence Acknowledge has timed out. When an LCAS source re-sequences the VC-n channels, the LCAS source expects the opposite end to acknowledge this operation through an RS-ACK. If the source does not receive an RS-ACK within a reasonable amount of time, the source declares a timeout. Look for other alarms in both ends.
64 lcas Minor eosMultiple Two or more chan. have EoS This event occurs when two or more received channels have End of Sequence (EoS). One and only one channel must have EOS. See sqnc alarm. Look for other alarms at both ends.
65 lcas Minor eosMissing No channel has EoS None of the received channels has End of Sequence (EoS). One and only one channel must have EOS. See sqnc alarm. Look for other alarms at both ends.
66 lcas Minor sqNonCont Missing SQ detected This alarm appears when a sequence number is missing. See sqnc alarm. Check for configuration mismatch or other alarms.
67 lcas Minor sqMultiple Equal SQ for two or more chan This message appears when two or more channels have the same sequence number. See sqnc alarm. Check for configuration mismatch or other alarms.
68 lcas Major sqOor SQ outside of range This alarm occurs when the received sequence number is outside of the valid range (VC-4: 0-6, VC-3: 0-20, VC-12: 0-62). See sqnc alarm. Check for configuration mismatch or other alarms.
69 lcas Major sqnc sequence nbr not consistent This alarm appears when one or more of these alarms occur: eosMultiple, eosMissing, sqNonCont, sqOor and sqMultiple. Channels must have unique sequence numbers. Check the received sequence numbers. This alarm can indicate a signalling problem at the opposite port, or cross-connect problems.
70 lcas Major gidErr GID different for active chan This alarm appears when active channels within the same VCGroup receive different Group ID. Check the configuration.
71 lcas Major ctrlOor CTRL word undefined This alarm indicates the receipt of an illegal or undefined CTRL word value. Check the configuration at both ends.
72 lcas Major lcasCrc CRC error detected This alarm appears when the Cyclic Redundancy Check (CRC) fails. Check the configuration at the other end, and look for other alarms.
73 lcas Minor nonLcas Non-LCAS source detected This alarm implies that the NE at the other end is not in LCAS mode. Check the configuration.
74 lcas Major plcr Partial loss capacity rx This alarm appears when the received capacity is less than expected. Check the operational-capacity, VC-n alarms, and configuration parameters on the opposite port.
75 lcas Critical tlcr Total loss capacity rx This message indicates that the port receives no traffic. Check for VC-n alarms and configuration parameters on the opposite port.
76 lcas major plct Partial loss capacity tx This alarm appears when the send capacity is less than expected. Check the operational capacity. Check for configuration parameters on this side, and also check the cross-connect status, and alarm status on the opposite port.
77 lcas Critical tlct Total loss capacity tx This message indicates that no traffic is sent. Check for configuration parameters on this side, and also check the cross-connect status, and alarm status on the opposite port.
78 module Critical modFail Module failure This alarm indicates a module failure (power loss on the module). Restart the module. If the problem persists, replace the module.
79 module Critical diagFail Diagnostic failure This alarm appears when you encounter problems when you try to load FPGA, SPI/Eeprom, Power input, DXC inlet or Ethernet switch on service modules. Restart the module. If the problem persists, replace the module.
80 module Major inventoryFail Inventory failure Inventory failure occurs when module identification is not correct. Replace the module.
81 module Critical inletFail DXC inlet failure When you power cycle (power on/off at different temperatures) a service module, the card can fail to recover operation after the power on/off, and can remain in an alarm state. In sych a state the card does not carry traffic. When the card indicates the "DXC inlet failure alarm", the LED of the card is also red. The card recovers normal operation after software reset. This issue occurs in approximately one out of every 20 power cycles. Restart the module. If the problem persists, replace the module.
82 module Critical inletBitError DXC inlet bit error Cards with EoS mappers can experience packet losses. For example, LAN traffic mapped to EoS ports on 8xSTM1+map module, and "DXC inlet bit error alarm" conditions can occur when you expose 8xSTM1+map cards to extreme temperature cycles (-5 to 50�C with 2 hours dwell at each extreme temperature, and 1�C/min gradients). The packet losses and condition can occur on the 8xSTM1+map card. This only occurs under temperature stress. The frequency with which the issue occurs is an average of 10 packets lost, and less than 100 alarms recorded in a 12 hours cycle. Nominal conditions record no failures. -
83 module Critical cardIsolated Card isolated The 'card isolated' error can occur in these conditions:
  1. A card anomaly occurs while the module is in-service:
    1. Module removed (extracted from the chassis).
    2. Module failed (power loss on the module).
    3. Dxc inlet failure (interface between main-card and the module).

      Note: If a) or b) or c) occurs on pure SDH/PDH modules, an alarm appears.

      • Card_removed (A)
      • Card_anomaly (B/C)
      If a) occurs on modules with switch (8xstm1_map/8xfe/2xge/4xfe_map/8xmap) an alarm (card_removed) appears, BUT, in addition the complete device restarts, due to recovery/clean-up handling of the crossbar or switch system. When the device is up again, the card_removed alarm is still present. If b) or c) occurs on modules with switch (8xstm1/8xfe/2xge/4xfe_map/8xmap) an alarm (card_anomaly) appears BUT in addition, the complete device restarts, due to recovery/clean-up handling of the crossbar or switch system. When the device is up again, the failed module is marked "ISOLATED".
  2. On a module (with switch - 8xstm1/8xfe/2xge/4xfe_map/8xmap) the hot-removal process fails when you shut down the module. Again the system restarts, due to recovery/clean-up handling of the crossbar or switch system. When the device is up again, the failed module is marked "ISOLATED".
When a module ends up in an "ISOLATED" alarm-state, not caused by physical handling, you must replace the module.
84 module Critical cardAnomaly Card anomaly See card Isolated. -
85 module Critical hotSwapFailure Hot swap failure This alarm indicates that the module cannot be reported to the processor, and Ethernet services will not become operational for the module. Restart the module. If the problem persists, try to insert the module in another slot. If the problem still persists, replace the module. If the module does not fail in different slots, check for issues on the main board (XBAR).

Note: In addition, you can experience this condition for 1.x level of software for ONS15305. For more information, refer to the known issues in latest software release note for the respective units.

86 module Warning modOos Module Out Of Service This event occurs when the module enters the OOS state. -
87 module Warning modOosMaint Module OOS by maintenance This event occurs when the module enters the OOS by maintenance state. -
88 module Warning modIns Module IN Service This event occurs when the module enters the in-service state. -
89 module Warning unknownFlashType Unknown FLASH-device detected This alarm appears when the Flash-process discovers an unknown flash type on the module. Restart or reboot the module. If the alarm persists, replace the module.
90 module Warning errorNewBank ERROR in newest bank This error appears when the module does not start up with the latest downloaded firmware. Retry download.
91 module Warning moduleShutdown Module shutdown This event occurs when the module enters the Shutdown state. -
92 module Warning moduleRestart Module restart This event occurs when the module enters the Restart state. -
93 module Warning modUnEq Module UnEquipped This event occurs when the module or slot enters the Unequipped state. -
94 mst Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5. Investigate whether there are bit errors for RS sections on the path. For example, a radio hop.
95 mst Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than the configured threshold. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm appears when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). Investigate whether there are bit errors reported for RS sections on the path. For example, a radio hop. To clear this alarm, improve the BER level by a factor 10.
96 mst Minor csf Dcc Termination Failure This alarm can occur for a DCC-m (D4-D12) connection, which is active but does not properly terminate at the other end. Verify whether both ends of the link obtain equal DCC settings.
97 mst Minor ais Alarm Indication Signal MS-AIS is the alarm indication signal for the multiplexer section (MS). STM-n ports that are not configured often transmit MS-AIS, and a regenerator with no input signal transmits MS-AIS. If AIS appears in MS, verify alarm conditions on regenerator sections on the path, for example, a radio hop. Verify the configuration on the opposite port also.
98 mst Minor rdi Remote Defect Indication If an RS alarm (LOS, LOF, TIM, AIS) or MS-AIS appears on an STM-n port, MS-RDI goes out on that port. Verify alarm conditions on regenerator sections on the path, for example, a radio hop. Also check the configuration on the opposite port.
99 mst Critical msp MSP signalling problem This problem typically occurs if you have a mismatch in configuration. In other words, this occurs when your configuration is unidirectional on one end and bidirectional on the other end. Check the MSP configuration.
100 mst Warning switchToProt MSP switched to protecting This event occurs if the traffic switches from “working” to “protecting”. -
101 mst Warning switchToWork MSP switched to working This event occurs if the traffic switches from “protecting” to “working”. -
102 mst Warning mspComTimeOut MSP command timed out, removed This event indicates the timeout of an MSP-command that you successfully enter at this end. The timeout occurs due to a "no" from the other end. This alarm only appears when you use bidirectional MSP. This event does not indicate any malfunction, and can occur as a consequence of the MSP-protocol in different combinations of alarm-state or MSP-commands.
103 mst Warning mspComOverruled MSP command overruled, removed This event indicates that a user has entered an MSP-command with a higher priority at the other end of the connection. The result is that the MSP-command at this end is removed. This alarm only appears when you use bidirectional MSP. -
104 power Critical pwrInA Power failure input A This means power input A is absent. Check power cable or supply.
105 power Critical pwrInB Power failure input B This means power input B is absent. Check power cable or supply.
106 power Critical pwrOut Power output failure This indicates that 48VDC / 230VAC power module does not provide internal power (5V). Replace the module.
107 power Critical pwrFail Power module out This alarm appears if the power module is administratively enabled and removed. -
108 power Critical diagFail Diagnostic failure This failure occurs due to incorrect module identification. Replace the module.
109 power Major inventoryFail Inventory failure This event occurs if the correct HW-inventory cannot be retrieved from the power-module. This condition most likely requires a replacement of the module, but can still be operational. If this alarm appears for a slot, independent of module inserted, the alarm indicates problem of the chassis. In this case, replace the device.
110 power Critical pwrUIL 230VAC power input low This alarm appears when an AC module receives less than 195VAC from the 230VAC outlet. The module disconnects the output voltage and activates an alarm if the output voltage is outside the specified tolerance (Higher than 6V or less that 5V). The module also limits the maximum output current to 11A.
111 power Critical pwrUIH 230VAC power input high This alarm appears when an AC module receives more than 255VAC from the 230VAC outlet. The module disconnects the output voltage and activates an alarm if the output voltage is outside the specified tolerance (Higher than 6V or less that 5V). The module also limits the maximum output current to 11A.
112 rst Critical lof Loss Of Frame The loss of frame (LOF) alarm appears when the frame sync is not recognizable, and the out of frame (OOF) alarm persists for 3ms. Set OOF.
113 rst Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5. Investigate whether there are bit errors reported for other sections in the network between intermediate nodes.
114 rst Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than the configured threshold. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm appears when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear this alarm, improve the BER level by a factor 10.
115 rst Critical tim Trace Identifier Mismatch Trace Identifier Mismatch occurs when you have enabled path trace and the “received string” is different from the “expected string”. This alarm condition stops traffic. Verify the configured string at both ends of the physical connection. You do not need to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (such as, "BONN-3-21") you can check whether the other side of teh network receives this value. If you enter a value for the Path Trace Expected and enable Path Trace, a TIM alarm appears if the received value is different from the transmitted value.
116 rst Minor csf Dcc Termination Failure This alarm appears for a DCC-r (D1-D3) connection, which is active but does not properly terminate at the other end. Verify whether both ends of the link obtain equal DCC settings.
117 rst Critical oof Out Of Frame The out of frame (OOF) alarm appears when the frame sync in not recognizable. OOF condition results in a loss of frame (LOF) alarm, if persistent in 3ms. Check whether the framing format configured on the port matches the framing format on the line. Try the other framing format and see if the alarm clears. Open the statistics report (RS) for the port and look for evidence of a bad line. Bit errors can indicate a timing problem. If you find evidence of a bad line, isolate the problem. For this, physically loop the ports with a cable at each end of the connection.
118 sdhPort Critical los Loss Of Signal - -
119 sdhPort Minor orxo Optical Receiver Overload This alarm appears on STM-4 and STM-16 when the received signal is too strong (optical Rx-level too high). The maximum allowed level depends on module type and type of optical receiver. Reduce optical Rx-level to make sure that the traffic remains unaffected.
120 sfp Warning sfpRemoved SFP removed from module This event indicates that an SFP has been removed at a port. -
121 sfp Warning sfpInserted SFP inserted in module This event indicates that an SFP has been inserted at a port. -
122 slot Critical modMis Module mismatch This alarm appears if the module type that you configure is different from the module you insert. The alarm clears if you replace the module, or change the expected module (to create a match between expected and installed).
123 slot Critical modOut Module removed This alarm appears if the module is in the in-service state and is extracted from the slot. Issue a module shutdown process before you pull out the module.
124 tu12 Minor ais Alarm Indication Signal When an NE detects a defect on the TU-12 level or any level above TU-12, the TU-12 payload is invalid. The NE then replaces the payload with an AIS in the forwarding direction. All subsequent NEs detect TU-AIS.

Note: This alarm is suppressed by default.

If AIS appears for an TU-12, verify alarm conditions on sections between intermediate nodes on the path.
125 tu12 Critical lop Loss Of Pointer This alarm appears when an NE is unable to interpret the TU-12 pointer. This alarm normally indicates that the NE receives TU-3s when the NE actually expects TU-12s. Verify whether connected STM-n ports maintain the same structure at both ends.
126 tu12 Warning switchWork SNCP switched to working This event occurs if the traffic switches from “protecting” to “working”. Switching criteria include the SNCP type, namely, SNC/i or SNC/n. The main difference between the two is that SNC/n, in addition to a switch on AIS/LOP alarms, also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
127 tu12 Warning switchProt SNCP switched to protecting This event occurs if the traffic switches from “working” to “protecting”. Switching criteria include the SNCP type, namely, SNC/i or SNC/n. The main difference between the two is that SNC/n, in addition to a switch on AIS/LOP alarms, also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
128 tu3 Minor ais Alarm Indication Signal When an NE detects a defect on the TU-3 level or any level above TU-3, the TU-3 payload is invalid. The NE then replaces the payload with an AIS in the forwarding direction. All subsequent NEs detect TU-AIS.

Note: This alarm is suppressed by default.

If AIS appears for an TU-3, verify alarm conditions on sections between intermediate nodes on the path.
129 tu3 Critical lop Loss Of Pointer This alarm appears when an NE is unable to interpret the TU-3 pointer. This alarm normally indicates that the NE receives TU-12s when the NE actually expects TU-3s. Verify whether connected STM-n ports maintain the same structure at both ends.
130 tu3 Warning switchWork SNCP switched to working This event occurs if the traffic switches from “protecting” to “working”. Switching criteria include the SNCP type, namely, SNC/i or SNC/n. The main difference between the two is that SNC/n, in addition to a switch on AIS/LOP alarms, also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
131 tu3 Warning switchProt SNCP switched to protecting This event occurs if the traffic switches from “working” to “protecting”. Switching criteria include the SNCP type, namely, SNC/i or SNC/n. The main difference between the two is that SNC/n, in addition to a switch on AIS/LOP alarms, also switches on (non-intrusive) UNEQ/TIM/DEG/EXC alarms. -
132 vc12 Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
133 vc12 Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than configured threshold. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm appears when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear this alarm, improve the BER level by a factor 10. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
134 vc12 Critical tim Trace Identifier Mismatch This alarm appears when path trace is enabled and the “received string” is different from the “expected string”. This alarm condition stops traffic because AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received Path Trace.

Note: For an Ethernet over SDH (EoS) port mapper, Path trace is a global setting for each Group, though you can read the received string for each individual VC.

Verify the configured string at both ends of the VC-12 terminations. You do not have to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (such as, "BONN-3-21") you can easily check whether the other side of the network receives this value. If you enter a value for the Path Trace Expected value and enable Path Trace, a TIM alarm is triggered if the received value is different from the transmitted value.
135 vc12 Minor rdi Remote Defect Indication This alarm indicates the presence of an incoming alarm at the point where the VC-12 terminates at the other end. The alarm can be UNEQ, TIM, or SSF. -
136 vc12 Minor ssf Server Signal Failure This alarm indicates that an alarm in the device affects the traffic on this VC-12 termination point. For example, a LOS alarm on an STM-n port at the other end of a cross-connect. -
137 vc12 Critical uneq Unequipped This alarm means that the VC-12 has no payload. This alarm normally indicates loss of connectivity for the configured payload. For example, if you enable a 2Mbit (E1) but do not cross-connect the VC, this alarm appears. -
138 vc12 Critical plm Payload Mismatch The signal label indicates what type of payload the VC-12 carries. The payload label mismatch (PLM) occurs if there is detected a mismatch between an expected and received signal label. Check the configuration at other end and verify the cross-connects.
139 vc12Nim Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5 for a KLM-value that is structured as TU-12 and has a non-intrusive monitor active. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
140 vc12Nim Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than the configured threshold for a KLM-value that is structured as TU-12 and has a non-intrusive monitor active. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm appears when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear this alarm, improve the BER level by a factor 10. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
141 vc12Nim Critical tim Trace Identifier Mismatch This alarm appears when path trace is enabled and the “received string” is different from the “expected string” for a KLM-value that is structured as TU-12 and has a non-intrusive monitor active. This alarm condition does not affect traffic.

Note: For an EoS mapper (Ethernet over SDH port), Path trace is a global setting per Group, though you can read the received string for each individual VC.

Verify the configured string in both ends of the VC-12 terminations. You do not have to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (such as, "BONN-3-21") you can easily check whether the other side of the network receives this value. If you enter a value for the Path Trace Expected value and enable Path Trace, a TIM alarm is triggered if the received value is different from the transmitted value.
142 vc12Nim Critical uneq Unequipped This alarm indicates that an STM-n port does not contain a VC-12 for a KLM-value that is structured as TU-12 and has a non-intrusive monitor active. -
143 vc3 Major exc BER excessive error rate This alarm is reported if the Bit Error Rate is greater than 1E-5. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
144 vc3 Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than the configured threshold. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm appears when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear this alarm, improve the BER level by a factor 10. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
145 vc3 Critical tim Trace Identifier Mismatch This alarm appears when path trace is enabled and the “received string” is different from the “expected string”. This alarm condition stops traffic because AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received Path Trace.

Note: For an EoS mapper (Ethernet over SDH port), Path trace is a global setting for each Group, though you can read the received string for each individual VC.

Verify the configured string in both ends of the VC-3 terminations. You do not have to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (such as "BONN-3-21") you can easily check whether the other side of the network receives this value. If you enter a value for the Path Trace Expected value and enable Path Trace, a TIM alarm is triggered if the received value is different from the transmitted value.
146 vc3 Minor rdi Remote Defect Indication This alarm indicates the presence of an incoming alarm at the point where the VC-3 terminates at the other end. The alarm can be UNEQ, TIM, or SSF. -
147 vc3 Minor ssf Server Signal Failure This alarm indicates that an alarm in the device affects the traffic on this VC-3 termination point. For example, a LOS-alarm on an STM-n port at the other end of a cross-connect. -
148 vc3 Critical uneq Unequipped This alarm indicates loss of connectivity for the configured payload. For example, if you enable a 34Mbit (E3) but do not cross-connect the VC, this alarm occurs. -
149 vc3 Critical plm Payload Mismatch The payload label mismatch (PLM) occurs if a mismatch is detected between expected and received signal label. -
150 vc3Nim Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5 for a K-value that is structured as TU-3 and has a non-intrusive monitor active. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
151 vc3Nim Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than configured threshold for a K-value that is structured as TU-3 and has a non-intrusive monitor active. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm is raised when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear this alarm, improve the BER level by a factor 10. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
152 vc3Nim Critical tim Trace Identifier Mismatch This alarm appears when path trace is enabled and the “received string” is different from the “expected string” for a K-value that is structured as TU-3 and has a non-intrusive monitor active. This alarm condition does not affect traffic.

Note: For an EoS mapper (Ethernet over SDH port), Path trace is a global setting per Group, though you can read the received string for each individual VC.

Verify the configured string in both ends of the VC-3 terminations. You do not have to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (for example, "BONN-3-21") you can easily check whether the other side of the network receives this value. If you enter a value for the Path Trace Expected value and enable Path Trace, a TIM alarm is triggered if the received value is different from the transmitted value.
153 vc3Nim Critical uneq Unequipped This alarm indicates that an STM-n port does not contain a VC-3 for a K-value that is structured as TU-3 and has a non-intrusive monitor active. -
154 vc4 Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
155 vc4 Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than configured threshold. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm appears when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear this alarm, improve the BER level by a factor 10. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
156 vc4 Critical tim Trace Identifier Mismatch This alarm appears when path trace is enabled and the “received string” is different from the “expected string”. This alarm condition stops traffic because AIS is inserted downstream instead of the original signal when there is a mismatch between expected and received Path Trace.

Note: For an EoS mapper (Ethernet over SDH port), Path trace is a global setting for each Group, though you can read the received string for each individual VC.

Verify the configured string in both ends of the VC-4 terminations. You do not have to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (for example, "BONN-3-21") you can easily check whether the other side of the network receives this value. If you enter a value for the Path Trace Expected value and enable Path Trace, a TIM alarm is triggered if the received value is different from the transmitted value.
157 vc4 Minor rdi Remote Defect Indication This alarm indicates the presence of an incoming alarm at the point where the VC-4 terminates at the other end. The incoming alarm can be UNEQ, TIM, or SSF. -
158 vc4 Critical lom Loss Of Multiframe A VC-4 that carries TU-12s has a multiframe indication in the H4 byte. If this multiframe indication is absent, Loss Of Multiframe occurs. Check the configuration at the other end.
159 vc4 Minor ssf Server Signal Failure This alarm indicates that an alarm in the device affects the traffic on this VC-4 termination point. For example, a LOS-alarm on an STM-n port at the other end of a cross-connect. -
160 vc4 Critical uneq Unequipped This alarm means that the VC-4 has no payload. This alarm normally indicates loss of connectivity for configured payload. Check the configuration at the other end and verify the cross-connects.
161 vc4 Critical plm Payload Mismatch The signal label indicates what type of payload the VC-4 carries. The payload label mismatch (PLM) alarm appears in case of a mismatch between expected and received signal label. Check the configuration at the other end and verify the cross-connects.
162 vc44cNim Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5 for a C-value that is structured as AU-4-4C and has a non-intrusive monitor active. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
163 vc44cNim Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than configured threshold for a C-value that is structured as AU-4-4c and has a non-intrusive monitor active. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm appears when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear the alarm, improve the BER level by a factor 10. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
164 vc44cNim Critical tim Trace Identifier Mismatch This alarm appears when path trace is enabled and the “received string” is different from the “expected string” for a C-value that is structured as AU-4-4c and has a non-intrusive monitor active. This alarm condition does not affect traffic. When the TIM alarm is present on VC-4-4c level, verify the configured string on both ends of the VC-4-4c terminations. You do not have to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (for example, "BONN-3-21") you can easily check whether the other side of the network receives this value. If you enter a value for the Path Trace Expected value and enable Path Trace, a TIM alarm is triggered if the received value is different from the transmitted value.
165 vc44cNim Critical uneq Unequipped This alarm indicates that an STM-n port does not contain a VC-44c for a C-value that is structured as AU-44c and has a non-intrusive monitor active. -
166 vc4Nim Major exc BER excessive error rate This alarm appears if the Bit Error Rate is greater than 1E-5 for a CB-value that is structured as AU-4 and has a non-intrusive monitor active. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
167 vc4Nim Minor deg Signal degrade (BER low) This alarm appears when the Bit Error Rate is greater than configured threshold for a CB-value that is structured as AU-4 and has a non-intrusive monitor active. You can configure the threshold for this alarm from 1E-6 to 1E-9. For example, if set to 1E-7 (default), an alarm is raised when BER exceeds this threshold. The detection time depends on the threshold. (1E-6 has a short detection-time, 1E-9 has longer detection time). To clear this alarm, improve the BER level by a factor 10. Investigate whether bit errors occur for other sections in the network between intermediate nodes.
168 vc4Nim Critical tim Trace Identifier Mismatch This alarm appears when path trace is enabled and the “received string” is different from the “expected string” for a CB-value that is structured as AU-4 and has a non-intrusive monitor active. This alarm condition does not affect traffic.

Note: For an EoS mapper (Ethernet over SDH port), Path trace is a global setting for each Group, though you can read the received string for each individual VC.

When the TIM alarm is present on VC-4 level, verify the configured string in both ends of the VC-4 terminations. You do not have to set the Path Trace Identifier attributes, but you can use the tool to check the connectivity of complex networks. Basically, a Path Trace Identifier is inserted at the start of a path and extracted at the end of a path. When you set Path Trace Transmitted to a logical value, (for example, "BONN-3-21") you can easily check whether the other side of the network receives this value. If you enter a value for the Path Trace Expected value and enable Path Trace, a TIM alarm is triggered if the received value is different from the transmitted value.
169 vc4Nim Critical uneq Unequipped This alarm indicates that an STM-n port does not contain a VC-4 for a CB-value that is structured as AU-4 and has a non-intrusive monitor active. -
170 vcat Critical lom Vcat Loss Of Multiframe All Vcat VC-ns carry a multiframe indication to re-align all members of a Vcat group in the sink end. If the sink end is unable to interpret the multiframe indication, Vcat Loss Of Multiframe occurs. Check the configuration at the other end and verify the cross-connects.
171 vcat Major sqm Sequence indicator mismatch This alarm appears when the received sequence (SQ) number is different from the expected sequence number. This is applicable only in non-LCAS mode. Check the configuration at the other end and verify the cross-connects.
172 vcat Major loa Loss of align. traffic ch This alarm appears when excessive differential delay between channels prevents channel alignment. Ensure that the differential delay between the VCAT members is less than the maximum tolerable delay.
173 wan Critical wanDelay Delay between VC12s above limit This alarm appears when the differential delay between VC-12s exceed ca. 6.5 ms. This alarm is similar to loa, but appears only for WAN ports with proprietary mapping. -
174 wan Critical seqFail Wrong channel seq. numbering P2P This alarm appears when the order of the VCs is incorrect. This alarm is similar to sqm, but appears only for WAN ports with proprietary mapping. Verify the order of VCs that carry Ethernet traffic between two WAN-ports.
175 wan Major plc Partial loss capacity This alarm appears when the operational status for bandwidth for an EoS mapper is less than what is administratively set. This alarm appears only for ports with bidirectional capacity (proprietary mapping). -
176 wan Critical tlc Total loss capacity This alarm appears in the event of absence of traffic on a port due to SDH alarms. This alarm appears only for ports with bidirectional capacity (proprietary mapping). -
177 wan Major plcr Partial loss capacity rx This alarm appears when the traffic capacity is less than provisioned in the receive direction on this port due to SDH alarms. -
178 wan Critical tlcr Total loss capacity rx This alarm appears when there is no traffic in the receive direction on this port due to SDH alarms. -
179 wan Warning rldot1dStpPortState Forwarding Bridge port learning to forwarding state transition - This alarm indicates a move in the STP port state for the given port from the "Learning" state to the "Forwarding" state. The port now forwards traffic. This alarm indicates a topology change.
180 wan Warning rldot1dStpPortState NotForwarding Bridge port forwarding to blocking state transition - This alarm indicates a move in the STP port state for the given port from the "Forwarding" state to the "Blocking" state. The port no longer forwards traffic. This alarm indicates a topology change.

Related Information

Updated: Oct 05, 2005
Document ID: 64208