Troubleshooting Alarms

11 Troubleshooting Alarms In this chapter: Overview ....................................................................................................... 11-1 Alarm Resolution Workflow ......................................................................... 11-3 Alarm Interactions ......................................................................................... 11-4 Transmission Alarms ..................................................................................... 11-5 Service Alarms ............................................................................................ 11-43 Timing Alarms............................................................................................. 11-45 Equipment Alarms ....................................................................................... 11-48 ATS Alarms ................................................................................................. 11-66 EMS-XDM-specific Alarms ........................................................................ 11-67 Checking Optical Parameters ...................................................................... 11-69 Card Objects, Alarms, and Maintenance Operations................................... 11-70

Overview This section provides a comprehensive list of EMS-XDM alarms and maintenance operations relevant to each object in EMS-XDM. Alarms are listed alphabetically within each alarm type category. Details for each alarm are provided, including the alarm name, description, severity, and corrective action(s).

432006-2444-0H3-A00

ECI Telecom Ltd. Proprietary

11-1

Troubleshooting Alarms

EMS-XDM User Manual

Some alarms, such as the Trace Identifier Mismatch (TIM) alarm, can occur at multiple levels, like the Regenerator Section (RS), Multiplexer Section (MS), and High-order (HO) Path, and Low-order (LO) Path levels. In most cases, alarms are cleared in the same fashion at all levels. NOTE: Layers/levels in this section refer to SDH overhead fame hierarchical levels, such as RS, MS, and HO path, which delineate various segments of the transmission network interconnecting SDH network elements (NEs). These terms are used interchangeably throughout this section.

EMS-XDM alarm types include: |

Transmission: alarms reported by the XDM indicating transmission problems

|

Optical Power Control-related Transmission: transmission alarms related to optical power control reported by the XDM

|

Service: alarms generated by transmission problems at the service layer

|

Timing: timing alarms reported by the XDM

|

Equipment: alarms reported for hardware failures/malfunctions

|

EMS-XDM-specific: alarms internal to the EMS-XDM management system

For transmission alarms and optical power control-related transmission alarms, the technique used to evaluate the level of system performance is to count the number of error events and increment the respective counter each time an event occurs. A PM alarm occurs whenever the threshold value of the event counter is crossed. Thresholds and counters are maintained for 15-minute and 24-hour periods.

11-2


432006-2444-0H3-A00


EMS-XDM User Manual

Administrative Unit (AU)/Tributary Severity: Major Unit (TU) AIS The AU/TU-AIS indicates that a failure has occurred upstream of the equipment sending the AIS. It indicates that another alarm exists before the equipment sending the AIS. To clear an AU/TU-AIS alarm: 1. Check higher-level alarms on this port. 2. If there are no alarms, go back to previous connections and do the same. The problem could be in any of the NEs before this port.

Degraded (DEG) Severity: Minor The DEG alarm indicates that the Bit Error Rate (BER) on the incoming frame is higher than the configured threshold. This threshold is lower than the one specified for the EXC alarm. To clear a DEG alarm: 1. Check performance at higher levels (RS, MS). 2. Check the input power level on the physical interfaces. 3. Check the path (MS/VC) optics and PM data. 4. If the alarm appears in AU/TU objects, the problem may have appeared before this NE. In this case, check and clean the fiber optic connector (if it is an electrical connector, it should be firmly connected). 5. If instructed to do so by qualified ECI Telecom personnel, replace the faulty card.

11-6


432006-2444-0H3-A00

EMS-XDM User Manual


Loss of Alignment (LOA) Severity: Major The LOA alarm indicates a loss of alignment on the incoming concatenation signal (that is, the VC-4 has exceeded its allocated RAM for delay compensation). To clear an LOA alarm: |

Verify that the difference between the fast VC-4 and the slow VC-4 in the same VC-4 group does not exceed the allocated RAM. To do this, examine the network topology and search for a path for the concatenation signal in which the total distance between nodes is less than the maximum permissible delay compensation.

Loss of Data (LOD) Severity: Major The LOD alarm indicates that the optical LOS is not detected and no signal transitions exist. This alarm applies only to OPS objects on TRP and SIO64F cards. LOD alarms may result when: |

The received frequency does not match the expected frequency.

|

The received protocol does not match the expected protocol.

|

The received signal does not include FEC in the optical layer, but FEC was expected.

To clear an LOD alarm: |

Verify that the data flow rate is correct within the link.

432006-2444-0H3-A00


11-7


EMS-XDM User Manual

Loss of Frame (LOF) Severity: Major The LOF alarm indicates that no frame alignment was detected in the incoming signal. The far end of the link can cause this alarm. This is a major alarm condition, as the receiver cannot recognize any data from the fibers. This alarm is detected at the RS level. Both failures at the source (transmitter) and extremely high BER conditions can generate LOF alarms. High BER conditions can be caused by problems such as: |

Extremely high received optical power levels

|

Very low received optical power levels

|

A receiver malfunction or a problem with the other-side transmitter

In addition, an LOF alarm can be caused by an incorrect rate, which typically only occurs during installation. The LOF alarm is triggered when severely errored framing (SEF) persists for three or more milliseconds. When troubleshooting an LOF alarm, it is critical to have a full understanding of the root cause of the LOF defect before attempting to correct the problem. If an LOF alarm occurs during installation, it is likely that optical planning was incorrect. An LOF alarm may also occur after some maintenance operations, as it is not unusual to obtain higher power levels after maintenance has been performed. To clear an LOF alarm: 1. Check for BIT alarms on both sides of the link. 2. If instructed to do so by qualified ECI Telecom personnel, replace the faulty card.

11-8


432006-2444-0H3-A00

EMS-XDM User Manual


Loss of Multiframe (LOM) Severity: Major The LOM alarm indicates a loss of multiframe alignment on the incoming signal. This alarm is triggered when a loss of synchronization is detected on byte H4 (bit 7, 8) in a superframe sequence. This alarm can result from: |

A faulty card

|

Connected test equipment that does not support multiframe

To clear an LOM alarm: |

If instructed to do so by ECI Telecom personnel, replace the faulty card.

Loss of Multiframe - Concatenated (LOMC) Severity: Major The LOMC alarm indicates a loss of multiframe alignment related to concatenated trails. To clear an LOMC alarm: |

Verify that the cross-connected VC-4 source is a member of the concatenated group.

Loss of Pointer (LOP) Severity: Major The LOP alarm indicates that invalid pointers were received due to an equipment failure, mismatch in signal mapping, or timing problem. To clear an LOP alarm: 1. Search for system timing alarms to determine the origin of the LOP alarm. 2. If instructed to do so by ECI Telecom personnel, replace the faulty card.

432006-2444-0H3-A00


11-9


EMS-XDM User Manual

Loss of Signal (LOS) Severity: Major The LOS alarm indicates a significant drop in the received signal level. This error may be caused by a broken or disconnected fiber or by a faulty optical transmitter. To clear an LOS alarm: 1. Disable ALS and verify whether the signal drop is bidirectional or unidirectional. 2. Check the fiber physical connection. 3. Clean the fiber connector interface. 4. If instructed to do so by qualified ECI Telecom personnel, replace the faulty card.

MSPL Failure Severity: Minor In bidirectional operation mode, the MSPL Failure alarm indicates that one of the following conditions exists: |

Faulty K1/K2 bytes received

|

No answer from the far-end node

|

Failure of the Exercise command

To clear an MSPL Failure alarm: 1. Perform an MSP (exercise) check in order to verify the protection link between NEs. Be sure to perform this check when traffic is on the main path. 2. Verify that MSP 1+1 is defined as bidirectional on both sides. NOTE: There are two HLXC384 cards (XIO cards in XDM-400 shelves) on both sides. MSP 1+1 requires two HLXC/XIO matrices. The left matrix is the working link and the right matrix is the protection link.

11-10


432006-2444-0H3-A00

EMS-XDM User Manual


3. Check that the fiber is connected between the connecting ports, and that there are no LOS or LOF alarms at the RS level and no AIS alarms at the MS level. 4. Check the MS PM counters in the protection link. 5. Reboot the protecting card in both sides. 6. Replace the protecting card.

Payload Label Mismatch (PLM) Severity: Major The PLM alarm indicates a mismatch in the payload signal label. As with the UNEQ or TIM alarms, the cause for this alarm may be a wrong connection (a missing XC or a crossed fiber). To clear a PLM alarm: 1. Open the Info window for the sink object with the alarm. 2. Change the C2 Expected value to match the C2 Received value. These two values must be identical.

PJ_15M Severity: Warning The PJ_15M alarm indicates that the pointer justification count exceeds a predetermined value. To clear a PJ_15M alarm: 1. Check the quality of the primary timing clock reference. 2. Check the timing map configuration.

432006-2444-0H3-A00


11-11


EMS-XDM User Manual

Remote Alarm Indication (RAI) Severity: Warning An RAI alarm indicates a far-end signal failure condition. When this alarm is detected, a code is sent upstream in a digital signal network as a notification that a failure has occurred downstream. This alarm applies to Async physical objects. NOTE: RAI signals may also be referred to as Yellow signals. To clear an RAI alarm: 1. Check client equipment to determine the origin of the problem. 2. Check if a Force RAI maintenance operation is activated at the far end. 3. Check which additional alarm is reported and proceed accordingly.

Remote Defect Indication (RDI) Severity: Warning An RDI alarm indicates a far end signal failure condition. To clear an RDI alarm: 1. Check whether a Force RDI maintenance operation is activated at the far end. 2. Check which additional alarm is reported and proceed accordingly.

11-12


432006-2444-0H3-A00

EMS-XDM User Manual


Sequence Mismatch (SQM) Severity: Major The SQM alarm indicates a loss of sequence on the virtual concatenation signal. This error may be caused by a mismatch in connections. For example, in the XC Browser, check the XC set for each NE along the path to ensure that the concatenation group objects are connected in the same order along the entire path. Access the XC Set List window to perform this check. NOTE: DIO and EIS/EISM cards use a transparent reordering process to modify incorrect sequencing of virtual containers in the group. Therefore, the SQM alarm will be reported only when two or more members from the same virtual concatenation group have the same sequence number. To clear an SQM alarm: |

Verify that all VC-4s in the virtual concatenation group are connected in the same order along the path.

Server Signal Fail (SSF) Severity: Major The SSF alarm indicates a failure in the adaptation function due to an AU-AIS or AU-LOP.

Trace Identifier Mismatch (TIM) Severity: Major The TIM alarm indicates a trace identifier mismatch caused by the incorrect provisioning of the expected trace or a misconnection. This alarm results from comparing the expected J0/J1/J2 byte to the received one. To clear a TIM alarm: 1. If the link is between a unit and an XDM NE, open the EMS-XDM Alarm Severity window, deselect TIM Detection, and select TIM Inhibition. 2. Adapt the Trace ID label to the label actually received. 3. Check PM counters. If they show errors, check the cause, for example, timing in higher levels.

432006-2444-0H3-A00


11-13


EMS-XDM User Manual

Unavailable Time (UAT) Severity: Warning The UAT alarm indicates 10 consecutive SESs (severely errored seconds). To clear a UAT alarm: 1. Check performance logs for errors. 2. Search for lower level alarms.

Unequipped (UNEQ) Severity: Major The UNEQ alarm indicates that an unequipped signal has been detected. This error may be caused by a disconnected trail. To clear a UNEQ alarm: 1. Verify that the fiber physical connection is the same as that described in the management topology view. 2. Reconnect the trail by performing a reconnect operation in the network management application. If LightSoft is being used as the network manager, this operation is performed in the Trail List window.

3. Click the

11-14

icon to reconnect the required trail.


432006-2444-0H3-A00

EMS-XDM User Manual


TCAs PM thresholds of an object are determined by the assigned PM profile. The PM profile contains a threshold setting for each PM counter relevant to the object type. Threshold-crossing alarms (TCAs) are triggered when the PM threshold for an object is exceeded. There are two thresholds for each PM interval (15-minutes and one day): a low threshold and a high threshold. When the value of a PM counter is higher than the high threshold, an alarm is reported. PM profiles are user-defined and can be used by the operator to troubleshoot alarms. For example, if the current high threshold settings within a PM profile are relatively low, you can change these settings to determine if an alarm, such as an Errored Seconds alarm, resulted from a sudden bursty error or errors that have accumulated over time. By changing the threshold setting in the PM profile, you can detect if the error was received over a long or short period of time. The following topics describe the XDM TCAs.

Background Block Errors Far End (BBEFE) Severity: Warning The BBEFE alarm is a threshold-crossing alarm that indicates that the system crossed the one day or 15 minute background block errors threshold at the far end. Since the BBEFE alarm is often reported at multiple levels, you should begin the alarm resolution process by checking for the alarm at multiple levels and then looking for a common denominator for the problem. Frequently, one card can cause several paths to report errors. To clear a BBEFE alarm: 1. If the alarm is reported at the low-order level, check the other ports on the same card to rule out the possibility of a hardware failure. 2. If it is reported at the high-order level as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the highorder level.

432006-2444-0H3-A00


11-15


EMS-XDM User Manual

Background Block Errors Near End (BBENE) Severity: Warning The BBENE alarm is a threshold-crossing alarm that indicates that the system has exceeded the one day or 15-minute background block errors threshold at the near end. Since the BBENE alarm is often reported at multiple levels, you should begin the alarm resolution process by checking for the alarm at multiple levels and then looking for a common denominator for the problem. Frequently, one card can cause several paths to report errors. To clear a BBENE alarm: 1. If the alarm is reported at the low-order level, check the other ports on the same card to rule out the possibility of a hardware failure. 2. If it is reported at the high-order level as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the highorder level.

Errored Seconds Far End (ESFE) Severity: Warning The ESFE alarm is a threshold-crossing alarm that indicates that the system has exceeded the 1-day or 15-minute errored seconds threshold at the far end node. As the ESFE alarm is often reported at multiple levels, you should begin the alarm resolution process by checking for the alarm at multiple levels and then looking for a common denominator for the problem. Frequently, one card can cause several paths to report errors. To clear an ESFE alarm: 1. If the alarm is reported at the low-order level, check the other ports on the same card (far-end) to rule out the possibility of a hardware failure. 2. If it is reported at the high-order level (far-end) as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the high-order level.

11-16


432006-2444-0H3-A00

EMS-XDM User Manual


Errored Seconds Near End (ESNE) Severity: Warning The ESNE alarm is a threshold-crossing alarm that indicates that the system has exceeded the 1-day or 15-minute errored seconds threshold at the near end node. Since the ESNE alarm is often reported at multiple levels, you should begin the alarm resolution process by checking for the alarm at multiple levels and then looking for a common denominator for the problem. Frequently, one card can cause several paths to report errors. To clear an ESNE alarm: 1. If the alarm is reported at the low-order level, check the other ports on the same card to rule out the possibility of a hardware failure. 2. If it is reported at the high-order level as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the highorder level.

Excessive Errors (EXC) Severity: Major The EXC alarm is a threshold-crossing alarm that indicates that the Bit Error Rate (BER) on the incoming signal frame is higher than the configured threshold. As the EXC alarm is often reported at multiple levels, you should begin the alarm resolution process by checking for the alarm at multiple levels and then looking for a common denominator for the problem. Frequently, one card can cause several paths to report errors. To clear an EXC alarm: 1. If the alarm is reported at the low-order level, check the other ports on the same card to rule out the possibility of a hardware failure. 2. If it is reported at the high-order level as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the highorder level.

432006-2444-0H3-A00


11-17


EMS-XDM User Manual

Severely Errored Seconds Far End (SESFE) Severity: Warning The SESFE alarm is a threshold-crossing alarm that indicates that the system has exceeded the respective 1-day/15-minute severely errored seconds (SES) threshold at the far end node. The PM counter for this alarm is incremented whenever 30% or more of the frames in a given second are errored. This alarm may indicate possible hardware failure. To clear an SESFE alarm: 1. If the alarm is reported at the low-order level, check the other ports on the same card to rule out the possibility of a hardware failure. 2. If it is reported at the high-order level as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the highorder level.

Severely Errored Seconds Near End (SESNE) Severity: Warning NOTE: On GEoS objects, this alarm is only reported for 15minute intervals. The SESNE alarm is a threshold-crossing alarm that indicates that the system has exceeded the respective 1-day/15-minute SES threshold at the near end node. The PM counter for this alarm is incremented whenever 30% or more of the frames in a given second are errored. This alarm may indicate possible hardware failure. To clear an SESNE alarm: 1. If the alarm is reported at the low-order level, check the other ports on the same card to rule out the possibility of a hardware failure. 2. If it is reported at the high-order level as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the highorder level.

11-18


432006-2444-0H3-A00

EMS-XDM User Manual


Data (Ethernet and Layer 2) Transmission Alarms Data transmission alarms apply to Ethernet and Layer 2 transmission path problems affecting EIS/EISM and DIO cards and their objects. The following topics describe the data transmission alarms.

Auto Negotiation (AN) Ability Mismatch Severity: Warning The AN Ability Mismatch alarm indicates that the total capacity of the link is not being utilized, for example, a Fast Ethernet link is operating at 10 Mbps. To clear an AN Ability Mismatch alarm: 1. Verify that the customer configuration is set up for auto-negotiation. 2. Check the fibers and cables on the remote partner (customer) device.

Auto Negotiation (AN) Failure Severity: Major The AN Failure alarm indicates a synchronization and communication failure in the auto-negotiation process between the EIS/EISM card and a customer device. When the AN process is enabled, it is automatically activated whenever cables are connected between the EIS/EISM or DIO and a customer device. Typically, a Link Down alarm is also generated in tandem with the AN Failure alarm. Therefore, the AN Failure alarm is set by default as a non-reported alarm in the EMS-XDM. The AN Failure alarm is reported on the customer device, such as a switch or router. To clear an AN Failure alarm: 1. Verify that the remote partner (customer) configuration is set up for autonegotiation. 2. Check the fibers and cables on the customer device.

432006-2444-0H3-A00


11-19


EMS-XDM User Manual

Client Signal Fail (CSF) Severity: Warning The CSF alarm indicates a fault that exists on the far-end (upstream) client side. The alarm is generated upon detection of loss on the link from the client (OPI Snk object). By default, this alarm is not reported. Upon detection, the OPI laser is shut down. This alarm is useful in cases where the client supports some Ethernet protection scheme that may be operated in case of a far-end client failure, assuming that the underlying layer is okay. In cases where GbE connections are implemented over a transport network (such as by the DIO), the client may not sense a failure that occurred in the transport network or in the far-end GbE link. The CSF alarm provides the necessary client notification mechanism should such conditions occur. To clear a CSF alarm: 1. Check the link between the far-end DIO and the far-end client. 2. Resolve the connection failure at the far-end client. Use the LOS alarm resolution process.

Encapsulation Mismatch Severity: Major The Encapsulation Mismatch alarm indicates that the GFP/HDLC encapsulation hardware revision does not support the configured Encapsulation Type. To clear an Encapsulation Mismatch alarm: |

Verify that the Encapsulation Type attribute is configured correctly for the GEoS sink object. This attribute is set in the object Info window.

Extension Header Mismatch (EXM) Severity: Major The Extension Header Mismatch (EXM) alarm indicates a mismatch between the expected and received extension headers in the GFP layer. This alarm typically indicates an interoperability problem with other vendor equipment. To clear a Header Mismatch alarm: |

11-20

Seek out the source of the problem on the far-end GFP equipment and proceed accordingly. ECI Telecom Ltd. Proprietary

432006-2444-0H3-A00

EMS-XDM User Manual


Header Mismatch Severity: Major The Header Mismatch alarm indicates a mismatch between the expected and received extension headers in the GFP layer. This alarm typically indicates an interoperability problem with other vendor equipment. NOTE: Laser shutdown as a consequent action of the Header Mismatch alarm is not currently supported. To clear a Header Mismatch alarm: |

Seek out the source of the problem on the far-end GFP equipment and proceed accordingly.

Link Down Severity: Major The Link Down alarm indicates an Ethernet link that is down or loss of carrier (as defined in IEEE 802.3). This alarm may result from: |

A failure in the auto-negotiation process between the EIS/EISM/DIO and the customer device

|

A loss of signal on the link resulting from disconnected fibers or cables, or a hardware failure

To clear a Link Down alarm: 1. Check the physical connections on both sides of the link. 2. Check the configuration of the EIS/EISM/DIO card and the customer device to be sure they are set up properly and to ensure that the port has not been disabled.

Loss of Frame Delineation (LFD) Severity: Major The LFD alarm indicates a loss of frame delineation on the Generic Framing Procedure (GFP) layer. To clear an LFD alarm: |

Check the GFP layer for a loss of signal or other high-level alarms and clear accordingly.

432006-2444-0H3-A00


11-21


EMS-XDM User Manual

Partner AN Failure Severity: Minor The Partner AN Failure alarm indicates a failure of the remote partner during the auto-negotiation process. To clear a Partner AN Failure alarm: 1. Verify that the customer configuration is set up for auto-negotiation. 2. Check the fibers and cables on the customer device.

Partner Link Down Severity: Minor The Partner Link Down alarm indicates that the remote partner link is down or unavailable. To clear a Partner Link Down alarm: 1. Verify that fibers and cables are connected properly on the customer device. 2. Check the connection between the remote partner and the EIS/EISM card. 3. Check the optical input power to the EIS/EISM card.

Partner Offline Severity: Minor The Partner Offline alarm indicates that the remote partner is offline or out of service. To clear a Partner Offline alarm: 1. Verify that the customer configuration is set up properly. 2. Check the fibers and cables on the customer device. 3. If the configuration is correct on both sides of the link, check the EIS/EISM card and the customer device for defects. Replace components, such as the EIS/EISM card or the customer device, if required.

11-22


432006-2444-0H3-A00

EMS-XDM User Manual


Partial Loss of Capacity (PLCR/PLCT) Severity: Minor The PLCR alarm indicates a partial loss of capacity on the GEoS link in the receive direction. The PLCT alarm indicates a partial loss of capacity on the GEoS link in the transmit direction. This may occur when some of the VC members in the group experience a failure and are not used for carrying traffic. When LCAS is supported, this alarm indicates that one or more of the provisioned path terminations is not currently carrying traffic due to a failure. This alarm applies on DIO and EIS/EISM cards. Failure in one direction affects service in both directions. Thus, these alarms will be reported on both sides of the connection. To clear a PLC alarm: |

Identify the VC member(s) that has experienced a failure condition. Use the relevant alarm clearing procedure to clear the alarm detected on this VC member(s).

Payload Type Identifier Mismatch (PTIM) Severity: Minor The PTIM alarm indicates a mismatch between the payload type identifiers. This alarm typically indicates an interoperability problem with other vendor equipment. To clear a PTIM alarm: |

Seek out the source of the problem on the respective equipment and proceed accordingly.

Port Over Quota Severity: Major The Port Over Quota alarm indicates that there is a port with a quota exceeding an event on at least one of the S-VIDs. To clear a Port Over Quota alarm: |


432006-2444-0H3-A00


11-23


EMS-XDM User Manual

Rx Buffer Overflow Severity: Minor The Rx Buffer Overflow alarm indicates a First In First Out (FIFO) buffer overflow for the ingress traffic. To clear an Rx Buffer Overflow alarm: 1. Check the Pause Mode setting on both sides of the link. 2. Verify that auto-negotiation is configured properly on both sides of the link.

Total Loss of Capacity (TLCR/TLCT) Severity: Major The TLCR and TLCT alarms indicate that none of the path terminations are currently carrying traffic due to a failure. This alarm is associated with GEoS source objects on the DIO card and is generated only when the LCAS attribute is enabled. To clear a TLC alarm: |

Follow the relevant alarm clearing procedure for the specific alarm detected on the VC members.

Trail Signal Degraded (TSD) Severity: Minor The TSD alarm indicates degradation in at least one of the path terminations comprising a virtually concatenated Ethernet over SDH (EoS) trail. This alarm is inhibited by default. When this alarm is not inhibited, the OPI laser is shut down upon detection of the TSD alarm. To clear a TSD alarm: |

11-24

Identify the VC members that have experienced an SD alarm. Use the relevant alarm clearing procedure to clear the alarm on these VC members.


432006-2444-0H3-A00

EMS-XDM User Manual


Trail Signal Fail (TSF) Severity: Major The TSF alarm indicates a failure in one of the path terminations comprising a virtually concatenated EoS trail. This alarm is detected on the SDH server layer and may affect both GEoS source and sink objects. The TSF alarm is triggered when the VC-4 that is mapped to a GbE port is faulty. Upon detection, the OPI laser is shut down towards the client. If LCAS is enabled, this alarm means that all VC-4 members are not available. If LCAS is not enabled, then a fault has been detected on one or more of the VC members to which the GbE is mapped, thereby causing the GbE trail to fail. To clear a TSF alarm: |

Identify the VC member(s) that has experienced a failure condition. Use the Service Failed alarm clearing procedure to clear the alarm detected on this VC member(s).

Tx Buffer Overflow Severity: Minor The Tx Buffer Overflow alarm indicates a FIFO buffer overflow condition for egress traffic. To clear a Tx Buffer Overflow alarm: 1. Check the Pause Mode setting on both sides of the link. 2. Verify that auto-negotiation is configured properly on both sides of the link.

Tx CRC Error Frames Severity: Warning The Tx CRC Error Frames alarm indicates the number of transmitted packets with errors. To clear a Tx CRC Error Frame alarm: |

Check client equipment to determine the origin of the problem.

432006-2444-0H3-A00


11-25


EMS-XDM User Manual

User Payload Identifier Mismatch (UPM) Severity: Minor The UPM alarm indicates a mismatch between the user payload identifiers. This alarm typically indicates an interoperability problem with other vendor equipment. To clear a UPM alarm: |


VCG Fail of Protocol Received (FOPR) Severity: Major The VCG FOPR alarm is caused by CRC or SQNC defects. This alarm is generated only when the LCAS attribute is enabled. To clear a VCG FOPR alarm: |

Follow the relevant alarm clearing procedure for the specific alarm detected on the VC member.

VCG Fail of Protocol Transmitted (FOPT) Severity: Major The VCG FOPT alarm is caused by CRC or SQNC defects. This alarm is generated only when the LCAS attribute is enabled. To clear a VCG FOPT alarm: |


VCG Group ID Mismatch (GIDM) Severity: Major The VCG GIDM alarm is caused by CRC or SQNC defects. This alarm is generated only when the LCAS attribute is enabled. To clear a VCG GIDM alarm: |

11-26



432006-2444-0H3-A00

EMS-XDM User Manual


VCG PCS 15-Min Severity: Warning The VCG PCS 15-Min alarm indicates loss of partial capacity. This alarm is generated only when the LCAS attribute is enabled. This alarm is only reported for 15-minute intervals. To clear a VCG PCS 15-Min alarm: |


VCG PCS 1-Day Severity: Warning The VCG PCS 1-Day alarm indicates loss of partial capacity. This alarm is generated only when the LCAS attribute is enabled. This alarm is reported for 24-hour intervals. To clear a VCG PCS 1-Day alarm: |


VCG Tx Utilization 15-Min Severity: Warning The VCG Tx UTIL 15-Min alarm indicates the transmitted utilization (transmitted average octets rate per percentage of the dedicated network BW). This alarm is only reported for 15-minute intervals. To clear a VCG Tx UTIL 15-Min alarm: |

Examine the threshold setting for the VCG Tx Utilization attribute to ensure that it is set properly.

432006-2444-0H3-A00


11-27


EMS-XDM User Manual

VCG Unavailable Seconds (UAS) 15-Min Severity: Warning The VCG UAS 15 Min alarm indicates 10 consecutive SESs (severely errored seconds). This alarm is generated only when the LCAS attribute is enabled. This alarm is reported for only 15-minute intervals. To clear a VCG UAS 15-Min alarm: |


VCG UAS 1-Day Severity: Warning The VCG UAS 1-Day alarm indicates 10 consecutive SESs (severely errored seconds). This alarm is generated only when the LCAS attribute is enabled. This alarm is reported for only 24-hour intervals. To clear a VCG UAS 1-Day alarm: |


Data TCAs The following topics describe the data-related TCAs for Ethernet and Layer 2.

Background Block Errors Near End (BBENE) Severity: Warning The BBENE alarm is a threshold-crossing alarm that indicates that at least one of the VC members has exceeded the 15-minute background block errors near end threshold. To clear a BBENE alarm: |

11-28

Identify the VC member(s) that has experienced a failure condition. Use the relevant alarm clearing procedure to clear the alarm detected on this VC member(s).


432006-2444-0H3-A00

EMS-XDM User Manual


Broadcast Packets (Pkts) Severity: Warning The Broadcast Pkts alarm is a threshold-crossing alarm that indicates that the number of broadcast packets received on a port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Broadcast Pkts alarm: |


Broadcast Storming Control (BSC) Discard Seconds Severity: Warning The BSC Discard Seconds alarm is a threshold-crossing alarm that indicates that the number of seconds in which the BSC dropped frames exceeds the configured threshold. This alarm is only reported for 15-minute intervals. The BSC attribute must be enabled on an EIS/EISM bridge object for this alarm to be generated. This attribute is disabled by default. EIS/EISM bridge objects use BSC to limit the broadcast rate from a source. When BSC is enabled, the maximum rate at which a source can broadcast is 500 k per second. If this limit is exceeded, the alarm is triggered. BSC is typically used for closed loops in case of RSTP failure. To clear a BSC Discard Seconds alarm: |

Reduce the rate of the broadcast service to an acceptable rate. On the client side, locate the broadcast source and correct its broadcast rate.

Committed Information Rate (CIR) Utilization Severity: Warning The CIR Utilization alarm indicates that the average rate of a service is near the permitted CIR rate in an SLA. As such, the alarm serves as a notification mechanism to alert you when you are near the CIR limit. This alarm is only reported for 15-minute intervals. This alarm applies to Policer objects and is typically used as a planning tool to enable you to determine whether your current SLA is adequate. To clear a CIR Utilization alarm: 1. Review the CIR setting in your current SLA and proceed accordingly. 2. Examine the threshold setting for the CIR Utilization attribute to ensure that it is set properly.

432006-2444-0H3-A00


11-29


EMS-XDM User Manual

Dropped Packets (Pkts) Severity: Warning The Dropped Pkts alarm is a threshold-crossing alarm that indicates that the number of dropped packets received on a port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Dropped Pkts alarm: |


Duplicate Media Access Control (MAC) Alert Severity: Major The Duplicate MAC Alert alarm indicates that a duplicate MAC address has been used illegally. This alarm provides a security mechanism to guard against unauthorized port access and hacking. The default high threshold for this alarm is 1 and the default low threshold is 0. This alarm is only reported for 15minute intervals. To clear a Duplicate MAC Alert alarm: |

Search out and locate the source of the attack. To do this, retrieve the list of ports in the network that may contain the suspect MAC address in their filter database. If more than one ETY port contains this MAC address, one of the clients connected to these ports has the wrong MAC address.

EoS Tx Utilization Severity: Warning The EoS Tx Utilization alarm indicates that EoS link utilization exceeds the configured percentage threshold of the active bandwidth. This alarm is typically used as a planning tool to aid in detecting when there is insufficient bandwidth on the link. This alarm is only reported for 15-minute intervals. To clear an EoS Tx Utilization alarm: 1. Increase the bandwidth by adding another VC-4. 2. Reduce the amount of information sent over the link.

11-30


432006-2444-0H3-A00

EMS-XDM User Manual


In Discard Severity: Warning The In Discard alarm is a threshold-crossing alarm that indicates the total number of events in which the probe dropped frames, due to lack of resources. Note that this number is not necessarily the number of frames dropped, but the number of times this condition has been detected. This alarm is only reported for 15-minute intervals. To clear an In Discard alarm: |


Multicast Packets (Pkts) Severity: Warning The Multicast Pkts alarm is a threshold-crossing alarm that indicates that the number of multicast packets received on a port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Multicast Pkts alarm: |


Nonconforming Octets Ratio Severity: Warning The Nonconforming Octets Ratio alarm indicates the percentage of nonconforming octets in a 15-minute interval. This alarm is triggered when the rate you are trying to pass exceeds the permitted CIR in your SLA. For example, if your SLA authorizes a CIR of 5 Mbps, and you are trying to transmit 10 Mbps, 5 Mbps are considered as conforming to the SLA and 5 Mbps are not. In this case, the nonconforming packets are dropped. This alarm is typically used as a planning tool to alert you that the current SLA is insufficient. To clear a Nonconforming Octets Ratio alarm: |

Review the specifications in your current SLA and proceed accordingly.

432006-2444-0H3-A00


11-31


EMS-XDM User Manual

Random Early Discard (RED) Drop Octets CoS Severity: Warning The RED Drop Octets CoS is a threshold-crossing alarm indicating that the number of packets dropped per port or egress queue exceeds the configured threshold. Packets are dropped based on their CoS in the following order: |

RED Drop Octets: CoS Best Effort (BE)

|

RED Drop Octets: CoS Bronze

|

RED Drop Octets: CoS Silver

|

RED Drop Octets: CoS Gold

To clear a RED Drop Octets CoS alarm: 1. Check client equipment to determine the origin of the problem. 2. Check the configuration of the policers. 3. Check the network planning for this port.

Rx Error Octets Severity: Major The Rx Error Octets alarm is a threshold-crossing alarm that indicates that the number of received errored octets per port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. This alarm results when incorrect information is transmitted from the remote partner. To clear an Rx Error Octets alarm: |

11-32

Check the client side of the link and the connection to the client to determine the source of the alarm. This alarm occurs due to problems on the client side and is always external to the EIS/EISM.


432006-2444-0H3-A00

EMS-XDM User Manual


Rx Error Pkts Severity: Warning The Rx Error Pkts alarm is a threshold-crossing alarm that indicates that the number of received errored frames per port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. This alarm results when incorrect information is transmitted from the remote partner. To clear an Rx Error Pkts alarm: |

Check the client side of the link and the connection to the client to determine the source of the alarm. This alarm occurs due to problems on the client side and is always external to the EIS/EISM.

Severely Errored Seconds Near End (SESNE) Severity: Warning This alarm is the same as that described in the Standard Transmission Threshold-Crossing Alarms (TCAs).

Tx Packets (Pkts) Error Severity: Warning The Tx Pkts alarm indicates the number of transmitted packets with errors. To clear a Tx Pkts Error alarm: |


Tx Utilization Severity: Warning The Tx Util alarm indicates the transmitted utilization (transmitted average octets rate per percentage of the dedicated network BW). This alarm is only reported for 15-minute intervals. To clear a Tx Utilization alarm: |

Examine the threshold setting for the Tx Utilization attribute to ensure that it is set properly.

432006-2444-0H3-A00


11-33


EMS-XDM User Manual

DCC TCAs The following topics describe the DCC TCAs.

DCC Link Failure Severity: Warning The DCC Link Failure alarm is a threshold-crossing alarm indicating that at least one of the DCC links has failed. To clear a DCC Link Failure alarm: |


Crossing the 15-Min Threshold for Received Errored DCC Packets Severity: Warning The Crossing the 15-Min Threshold for Received Errored DCC Packets alarm is a threshold-crossing alarm indicating that the number of DCC packets received on a port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Crossing the 15-Min Threshold for Received Errored DCC Packets alarm: |


Crossing the 15-Min Threshold for Discarded Received DCC Packets Severity: Warning The Crossing the 15-Min Threshold for Discarded Received DCC Packets alarm is a threshold-crossing alarm indicating that the number of discarded DCC packets received on a port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Crossing the 15-Min Threshold for Discarded Received DCC Packets alarm: |

11-34



432006-2444-0H3-A00

EMS-XDM User Manual


Crossing the 15-Min Threshold for Transmitted Errored DCC Packets Severity: Warning The Crossing the 15-Min Threshold for Transmitted Errored DCC Packets alarm is a threshold-crossing alarm indicating that the number of transmitted DCC packets received on a port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Crossing the 15-Min Threshold for Transmitted Errored DCC Packets alarm: |


Crossing the 15-Min Threshold for Discarded Transmitted DCC Packets Severity: Warning The Crossing the 15-Min Threshold for Discarded Transmitted DCC Packets alarm is a threshold-crossing alarm indicating that the number of discarded DCC packets transmitted to a port exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Crossing the 15-Min Threshold for Discarded Transmitted DCC Packets alarm: |


Crossing the 1-Day Threshold for Received Errored DCC Packets Severity: Warning The Crossing the 1-Day Threshold for Received Errored DCC Packets alarm is a threshold-crossing alarm indicating that the number of errored DCC packets received on a port exceeds the configured threshold. This alarm is reported for 24-hour intervals. To clear a Crossing the 1-Day Threshold for Received Errored DCC Packets alarm: |


432006-2444-0H3-A00


11-35


EMS-XDM User Manual

Crossing the 1-Day Threshold for Discarded Received DCC Packets Severity: Warning The Crossing the 1-Day Threshold for Discarded Received DCC Packets alarm is a threshold-crossing alarm indicating that the number of discarded DCC packets received on a port exceeds the configured threshold. This alarm is reported for 24-hour intervals. To clear a Crossing the 1-Day Threshold for Discarded Received DCC Packets alarm: |


Crossing the 1-Day Threshold for Transmitted Errored DCC Packets Severity: Warning The Crossing the 1-Day Threshold for Transmitted Errored DCC Packets alarm is a threshold-crossing alarm indicating that the number of errored DCC packets transmitted to a port exceeds the configured threshold. This alarm is reported for 24-hour intervals. To clear a Crossing the 1-Day Threshold for Transmitted Errored DCC Packets alarm: |


Crossing the 1-Day Threshold for Discarded Transmitted DCC Packets Severity: Warning The Crossing the 1-Day Threshold for Discarded Transmitted DCC Packets alarm is a threshold-crossing alarm indicating that the number of discarded DCC packets transmitted to a port exceeds the configured threshold. This alarm is reported for 24-hour intervals. To clear a Crossing the 1-Day Threshold for Discarded Transmitted DCC Packets alarm: |

11-36



432006-2444-0H3-A00

EMS-XDM User Manual


Crossing the 15-Min Threshold for Packets Discarded at the Router Severity: Warning The Crossing the 15-Min Threshold for Packets Discarded at the Router alarm is a threshold-crossing alarm indicating that the number of DCC packets discarded at the router exceeds the configured threshold. This alarm is only reported for 15-minute intervals. To clear a Crossing the 15-Min Threshold for Packets Discarded at the Router alarm: |


Crossing the 1-Day Threshold for Packets Discarded at the Router Severity: Warning The Crossing the 1-Day Threshold for Packets Discarded at the Router alarm is a threshold-crossing alarm indicating that the number of DCC packets discarded at the router exceeds the configured threshold. This alarm is reported for 24-hour intervals. To clear a Crossing the 1-Day Threshold for Packets Discarded at the Router alarm: |


432006-2444-0H3-A00


11-37


EMS-XDM User Manual

Optical Power Control-related Transmission Alarms Optical power control-related transmission alarms apply to all SDH levels, unless otherwise noted. The following topics describe the XDM optical power control-related transmission alarms.

Gain Input Overloaded Severity: Major The Gain Input Overloaded alarm indicates a gain input overload condition in an OFA-2 card. This alarm occurs when the power budget in the link is poorly planned, resulting in elevated input power levels to the optical amplifier and amplifier gain that is too high. These factors cause low attenuation between the input of the card and the input of the gain block, meaning that the optical power at the input of the gain block is higher than the permitted level, causing overload. To clear a Gain Input Overloaded alarm: 1. Check the optical parameters to determine if they are within the required ranges. 2. Recalculate the link power budget parameters, adjust the system based on your revised calculations, and then recalibrate.

Illegal Alarm Severity: Major The Illegal alarm indicates that the required correction is beyond the gain capability of the card, and that the set correction is less than the required correction. To clear an Illegal alarm: |

11-38

Since the required correction is greater than the remaining capability of the card, replace the card with one that has a higher gain capability.


432006-2444-0H3-A00

EMS-XDM User Manual


Input Power Change Severity: Major The Input Power Change alarm indicates that the required correction is greater than the Low Alarm Threshold that was added. This alarm can result from conditions that are temporary and reversible or conditions that are permanent. For example: |

A fiber cut that has been spliced to repair the cut: In this case, the fiber splice produces attenuation at the site of the splice. This is usually a permanent condition that must be corrected to prevent the generation of an Input Power Change alarm.

|

Bending of fibers while performing fiber maintenance: This is typically a temporary condition. The Input Power Change alarm usually disappears when the fibers are straightened out.

To clear an Input Power Change alarm: 1. Check the line for changes or abnormal attenuation. 2. Determine if the present situation is a temporary or permanent condition. If the alarm resulted from a permanent condition (see previous explanation), make the following change: In the EMS-XDM Power Control window, access the Gain Control window. In this window, select Adopt (Changes) and then click Apply.

OCU Alarms The following topics describe the Orderwire Control Unit (OCU) alarms.

OCU-LCK Severity: Warning The OCU-LCK alarm indicates a problem on the Orderwire Control Unit optical channel interface. To clear an OCU-LCK alarm: |


432006-2444-0H3-A00


11-39


EMS-XDM User Manual

OCU-OCI Severity: Warning The OCU-OCI alarm indicates a problem on the Orderwire Control Unit optical channel interface. To clear an OCU-OCI alarm: |


PCS Alarms The following topics describe the PCS alarms.

PCS Block 15-minutes Severity: Warning The PCS Block 15-Min alarm indicates block error. This alarm is reported only for 15-Minute intervals. To clear a PCS Block alarm: |


PCS HI BER Severity: Warning The PCS HI BER alarm indicates HI BER conditions, possibly caused by: |

Extremely high received optical power levels

|

Very low received optical power levels

|

A receiver malfunction or a problem with the other-side transmitter

To clear a PCS HI BER alarm: |


PCS LF Severity: Warning The PCS LF alarm indicates a local fail. To clear a PCS LF alarm: |

11-40

Check client equipment to determine the origin of the problem. ECI Telecom Ltd. Proprietary

432006-2444-0H3-A00

EMS-XDM User Manual


PCS Loss of Synch Severity: Major The PCS LOS alarm indicates a significant loss in the received signal level. This error may be caused by a broken or disconnected fiber or by a faulty optical transmitter. To clear a PCS LOS alarm: 1. Disable ALS and verify whether the signal drop is bidirectional or unidirectional. 2. Check the fiber physical connection. 3. Clean the fiber connector interface. 4. If instructed to do so by qualified ECI Telecom personnel, replace the faulty card.

PCS RF Severity: Warning The PCS RF alarm indicates a remote fail. To clear a PCS RF alarm: |


432006-2444-0H3-A00


11-41


EMS-XDM User Manual

Set Capability Exceeded Severity: Major The Set Capability Exceeded alarm indicates that the required correction is beyond the gain capability of the card, and that the set correction is less than the required correction. NOTE: This alarm serves as a warning to the operator that the current power budget margins are insufficient and will not be able to continue to provide the compensation required. Therefore, you should consider replacing the card with one that has a higher gain capability. Even if traffic is still flowing without errors, the next time an Input Power Change alarm occurs in the same direction (up or down), the card with the Set Capability Exceeded alarm may not be able to compensate for the gain.

To clear a Set Capability Exceeded alarm: |

Replace the card with one that has a higher gain capability, since the required correction is greater than the remaining capability of the card. For example, if the current OFA card has a 23 dB gain, replace it with one that has a 29 dB gain.

Tracking Limit Exceeded Severity: Major The Tracking Limit Exceeded alarm indicates that the span attenuation changes more than the power control can correct. This alarm usually occurs as a result of some type of catastrophic event, such as an NE shutting down unexpectedly or a fiber cut, and is typically accompanied by other alarms such as LOS. To clear a Tracking Limit Exceeded alarm: 1. Investigate possible events that may have caused the abnormal attenuation, such as an NE shutdown or a fiber cut. 2. Take relevant measurements that may aid in identifying the reason for abnormal attenuation. 3. Check the span attenuation and correct it. 4. If you fail to clear the alarm, reconfigure the power control definitions. Because this alarm rarely results from actual power control-related problems, you should perform this step only when all other avenues fail to resolve the alarm.

11-42


432006-2444-0H3-A00


EMS-XDM User Manual

Protection Path Failed Severity: Major The Protection Path Failed alarm indicates that the protection path of a trail transmitting traffic (which is currently not used for the active traffic) has failed. As a result, the active path is transmitting. To clear a Protection Path Failed alarm: 1. Check information and performance for all object types that are part of the protection path. 2. Check the higher level to determine if the same phenomenon is occurring. After you have identified the highest level with the problem, resolve the alarm at that level. 3. Check the optical parameter levels to ensure they are within the correct ranges. 4. Clean the fiber connectors.

Service Degraded Severity: Major The Service Degraded alarm indicates degradation in the traffic signal. This alarm may also indicate that a XC that is part of a trail is transmitting traffic, but the traffic is recognized as degraded. If the service is on an unprotected path, this alarm indicates a degraded traffic signal somewhere along the path. If the service is on a protected path, then it indicates one of two possible problems: either the nonactive path has failed, or the service on the active path is degraded. To clear a Service Degraded alarm: 1. Check information and performance for all object types that are part of the protection path. 2. Check for a failure on the nonactive path. 3. Open masking on relevant objects to try to locate the origin of the problem. 4. If the alarm is reported at the low-order level, check the other ports on the same card to rule out the possibility of a hardware failure. 5. If it is reported at the high-order level as well, check the optical parameters, clean the fiber optic connectors, and then monitor performance at the highorder level.

11-44


432006-2444-0H3-A00


EMS-XDM User Manual

T3-1/T3-2 AIS Severity: Major The T3-1/T3-2 AIS alarm indicates that T3-1/T3-2 has an alarm indication signal. To clear a T3-1/T3-2 AIS alarm: |

Check the T3-1/T3-2 source.

TG T4 Squelch Severity: Warning The TG T4 Squelch alarm indicates that the quality of the timing source for T4 output is below the quality threshold set for this output, and is therefore considered unsuitable as a T4 timing output. The timing source is squelched so it is not used as a synchronization source for other systems. To clear a TG T4 Squelch alarm: 1. Check the quality of the T4 source signal and its connections (it may have been reduced by mistake or the network timing may have been altered). 2. Change the T4 source to another source.

Timing Generator (TG) Holdover Severity: Warning The TG Holdover alarm indicates that the TG has no available timing reference for synchronization, and is entering a holdover state (the last valid clock source). To clear a TG Holdover alarm: 1. In the Timing Configuration window, check the primary timing clock reference. 2. In the Timing Configuration window, verify the timing configuration protection (secondary clock reference).

11-46


432006-2444-0H3-A00

EMS-XDM User Manual


TS-1/TS-2/T3-1 LOF Severity: Major The TS-1/TS-2/T3-1 LOF alarm indicates that TS-1/TS-2/T3-1 has a loss of frame. To clear a TS-1/TS-2/T3-1 LOF alarm: |

Check the TS-1/TS-2/T3-1 source.

TS1/TS2/TS3/TS4 Loss of Clock (LOC) Severity: Minor The TS1/TS2/TS3/TS4 LOC alarm indicates that timing source 1/2/3/4 has a loss of clock defect, which is identified by the TMU for T3 input and PIO tributary lines (disconnection of the timing source in the TMU input). To clear a TS1/TS2/TS3/TS4 LOC alarm: 1. Check the TS1/TS2/TS3/TS4 signal source and connection. 2. Change the source the TS1/TS2/TS3/TS4 uses to another port/card.

TS1/TS2/TS3/TS4 Transmitter Failure Severity: Minor The TS1/TS2/TS3/TS4 Transmitter Failure alarm indicates that timing source 1/2/3/4 has a transmission defect (AIS, LOS, LOF). It is identified by the HLXC card. To clear a TS1/TS2/TS3/TS4 Transmitter Failure alarm: 1. Check the TS1/TS2/TS3/TS4 signal source and connection. 2. Change the source the TS1/TS2/TS3/TS4 uses to another port/card.

432006-2444-0H3-A00


11-47

EMS-XDM User Manual


Improper MSP Codes Severity: Minor The Improper MSP Codes alarm indicates the occurrence of three consecutive and identical frames containing unused codes in bits 6 through 8 of byte K2 and codes irrelevant to the specific protection switching operation requested. This alarm may result from: |

An incorrectly created ring. For example, if a ring was created using a 4fiber code, which the XDM does not support, instead of 2-fiber code, this alarm is generated.

|

A ring containing non-XDM nodes.

To clear an Improper MSP Codes alarm: |

Recreate MS-SPRing to correct any problems with the ring configuration. NOTE: The MSP protocol is used in MS-SPRing protection schemes.

Inconsistent MSP Code Severity: Minor The Inconsistent MSP Code alarm indicates the occurrence of 12 successive frames, starting with the last frame containing previously consistent MSP code, in which no 3 consecutive frames contain identical MSP bytes. This alarm may result from: |

Network problems

|

Improper configuration of matrices and I/O cards

To clear an Inconsistent MSP Code alarm: 1. Check the I/O cards and matrices in the node that received the MSP codes and in the node that sent the codes. This check must be performed on at least two adjacent nodes. 2. Recreate MS-SPRing to correct any ring configuration problems. NOTE: The MSP protocol is used in MS-SPRing protection schemes.

432006-2444-0H3-A00


11-49


EMS-XDM User Manual

MS-SPRing Equipment Alarms The following topics describe the XDM MS-SPRing equipment alarms.

Default MS-SPRing K Bytes Severity: Minor The Default MS-SPRing K Bytes alarm indicates that the node cannot properly signal MSP bytes, and therefore cannot properly execute the switch to protection. Until the node has knowledge of the ring map, squelch table, and node ID, it will transmit the default K bytes. MS-SPRing is not properly defined in the NE connected to the port that emits this alarm. To clear a Default MS-SPRing K Bytes alarm: |

Recreate MS-SPRing.

MS-SPRing Extra Traffic Severity: Minor A node that preempts Extra Traffic will send an alarm of Extra Traffic Preempted. This alarm appears as a result of a protection switch in the MSSPRing. When there is a ring switch, all nodes should drop their extra traffic connections and pass the protection channels. This alarm is cleared when the failure in the MS-SPRing recovers (for example, fiber cut, node failure, and so on).

MS-SPRing Squelching Severity: Minor If a switching NE detects segmentation in a ring or additional segmentation in a ring, it squelches traffic destined for the unreachable NEs. In the case of a switching node, this alarm identifies the line being squelched (MS TTP). To clear the MS-SPRing Squelching alarm: |

11-50

This alarm is normal if squelching is activated. Check the reason in the Physical or RS layers.


432006-2444-0H3-A00

EMS-XDM User Manual


Node ID Mismatch Severity: Minor The Node ID Mismatch alarm indicates the occurrence of three consecutive and identical frames that contain a source node (byte K2, bits 1-4) that does not match the node ID of a neighbor (based on the resident ring map of the destination node), or that does not match an entry in the ring map. To clear a Node ID Mismatch alarm: 1. If an NE with a previous MS-SPRing configuration was inserted into the ring, clear the configuration on this NE and on the ring and then reconfigure it. 2. If a node was inserted into a ring in the wrong place, insert it in the correct place or reconfigure the MS-SPRing ring.

Built-In Test (BIT) Equipment Alarms The following topics describe the XDM BIT card-level equipment alarms.

BIT Slightly Degraded Severity: Minor The BIT Slightly Degraded alarm indicates an equipment fault that does not affect functionality. This alarm results from: |

A problem in the card or the HLXC/XIO connector to the card

|

A misplaced or faulty HLXC/XIO matrix

To clear a BIT Slightly Degraded alarm: 1. Check whether there are alarms on the two HLXC/XIO cards. 2. In the card Info window, check the BIT Codes attribute to determine if it is valid. To perform this check, you must contact ECI Telecom customer support to obtain the list of valid BIT code values.

432006-2444-0H3-A00


11-51


EMS-XDM User Manual

BIT Degraded Severity: Major The BIT Degraded alarm indicates an equipment fault that may affect functionality. BIT code information identifies the module within a card reporting a problem. In addition to the alarm, if the equipment is protected, it performs a switch to protected mode. This alarm can result from: |


|


To clear a BIT Degraded alarm: 1. Check whether there are alarms on the two HLXC/XIO cards. 2. In the card Info window, check the BIT Codes attribute to determine if it is valid. To perform this check, you must contact ECI Telecom customer support to obtain the list of valid BIT code values.

BIT Failed Severity: Critical The BIT Failed alarm indicates an equipment fault that is more severe than the one indicated by the BIT Degraded alarm. This alarm results from: |


|


BIT failure with severity critical will cause card to reset. The card initialization is not complete, in order to provide time for a technician to view the critical BIT failure log. The card does not forward traffic until the log is deleted. To clear a BIT Failed alarm: 1. Check whether there are alarms on the two HLXC/XIO cards. 2. In the card Info window, check the BIT Codes attribute to determine if it is valid. To perform this check, you must contact ECI Telecom customer support to obtain the list of valid BIT code values.

11-52


432006-2444-0H3-A00

EMS-XDM User Manual


Card-level Equipment Alarms The following topics describe the XDM card-level equipment alarms.

Air Flow Severity: Warning The Air Flow alarm indicates there is an intake airflow shortage into the system (originating from the fan unit on the XDM-40 or XDM-50). To clear an Air Flow alarm: 1. Replace the dust filter. 2. Check if the inlet air holes are sucking the air into the system. If blocked, clean the inlet air holes.

Card Failure Severity: Major The Card Failure alarm indicates that the card has a general hardware failure. This alarm indicates a more serious condition than the BIT Failed alarm, as it signifies a total failure of the card. In contrast, the BIT Failed alarm suggests that some of the functioning of the card or module is missing or not working properly. To clear a Card Failure alarm: 1. Reset the card. If the card still does not work properly after resetting it, replace the card. 2. If the problem still recurs, contact ECI Telecom customer support.

432006-2444-0H3-A00


11-53


EMS-XDM User Manual

Card Out Severity: Major The Card Out alarm indicates that an assigned card is no longer in its slot. This alarm results when: |

The card is assigned, but not physically present in the slot

|

The card is not in the slot

To clear a Card Out alarm: 1. If the card is not in its slot, insert the card. 2. If the card is in the slot, unassign the card so that the system no longer looks for the card.

Door Open Severity: Warning The Door Open alarm indicates that the shelf door (on the MECP/MXC) is open. To clear a Door Open alarm: |

Close the door of the shelf.

Eqpt Ctrl Severity: Warning The Eqpt Ctrl alarm indicates a problem with the control object on the equipment. To clear an Eqpt Ctrl alarm: |


High Line Out Severity: Major The High Line Out alarm indicates that the card output power is high (over 27 dBm). To clear a High Line Out alarm: |

11-54

Check the output power level. ECI Telecom Ltd. Proprietary

432006-2444-0H3-A00

EMS-XDM User Manual


High Temperature Severity: Major The High Temperature alarm indicates that the equipment temperature is high (65°C or higher). To clear a High Temperature alarm: 1. Check the ambient temperature level. 2. Check the fans. 3. Check that the shelf door is closed.

Low Line Out Severity: Major The Low Line Out alarm indicates that the card output power is low (less than 400 mW). To clear a High Line Out alarm: |

Check the output power level.

Low Temperature Severity: Major The Low Temperature alarm indicates that the temperature is below 0°C. To clear a Low Temperature alarm: |

Check the environmental conditions at the site and verify whether they are within the operational limits of the equipment.

Power Failure Severity: Major The Power Failure alarm indicates that a power failure has been detected in the card. To clear a Power Failure alarm: 1. Reset the card. If the card still does not work properly after resetting it, replace the card. 2. If the problem still recurs, contact ECI Telecom customer support.

432006-2444-0H3-A00


11-55


EMS-XDM User Manual

Program Fail Severity: Major The Program Fail alarm indicates either that the software is not functioning properly in the card, or that the system has failed to update the card database to the nonvolatile memory (NVM). WARNING: Contact ECI Telecom before attempting to correct this problem. It is critical that this alarm be handled carefully, so as not to adversely affect system configuration. To clear a Program Fail alarm: |

Replace the NVM with the same software as in the xMCP/MXC card.

Turbo Mode On Severity: Warning The Turbo Mode alarm indicates that there is a card in the system with a high temperature. To clear a Turbo Mode alarm: |

If a major alarm occurs, replace the card. If only a warning occurs, no action is necessary.

Type Mismatch Severity: Major The Type Mismatch alarm indicates that the wrong card or module was inserted in the slot. This alarm results when the Equipment Actual Type and the Equipment Expected Type are not the same. These two values must be identical. To clear a Type Mismatch alarm: |

11-56

Assign the card and ensure that the Equipment Actual Type matches the Equipment Expected Type.


432006-2444-0H3-A00

EMS-XDM User Manual


USF Severity: Warning The USF alarm indicates a problem with the air dust filter. To clear a USF alarm: |

Clean the air dust filter.

External Equipment Alarms The following topic describes the XDM external equipment alarms.

External Input Alarm Unit 1 through 8 Severity: Major The External Input Alarm Unit 1/2/3/4/5/6/7/8 alarm indicates that an environmental alarm was detected at external alarm unit 1 through 8. External inputs can be used by the XDM to trigger an external device, or to trigger an alarm in the EMS-XDM whenever a certain condition external to the XDM occurs. Up to eight external inputs can be defined. To clear an External Input Alarm Unit 1 through 8 alarm: |

The corrective action required is based on the type of equipment connected to the XDM for the given input unit. Perform the necessary action according to the user definition of this alarm.

432006-2444-0H3-A00


11-57


EMS-XDM User Manual

Optical Equipment Alarms The following topics describe the XDM optical equipment (including optical module and transceiver) alarms.

Application Code Mismatch Severity: Major The Application Code Mismatch alarm indicates that the expected configured application code differs from the actual value supported by the optical module. To clear an Application Code Mismatch alarm: |

In the optical module Info window, change the Expected Application Code attribute value so that it matches the Actual Application Code value. These two values should be the same on both the transmitter and receiver. An A in these two fields identifies an APD receiver, which is highly sensitive. A P in these fields denotes a pin diode receiver, which is less sensitive. The V, B, A, X, and U characters in these fields designate the transmitter type.

High Current Pump Severity: Major The High Current Pump alarm indicates that the optical amplifier pump has heated above the allowed current. This alarm may result from a defective module. To clear a High Current Pump alarm: 1. Check that the shelf door is closed. 2. Replace the card containing the defective module. Since the module is not detachable from the card, the entire card (including the module) must be replaced.

11-58


432006-2444-0H3-A00

EMS-XDM User Manual


High Rx Power Severity: Major The High Rx Power alarm indicates that the received power is higher than the maximum allowed value. To clear a High Rx Power alarm: 1. Check the optical parameters to ensure that they are within the correct ranges. 2. If power control is available on the line, consider using it to lower the input power. 3. Add an attenuator to the input, if needed.

High Temperature Pump Severity: Major The High Temperature Pump alarm indicates that the optical amplifier pump has heated above the allowed temperature. This alarm may result from a defective module. To clear a High Temperature Pump alarm: 1. Check that the shelf door is closed. 2. Replace the card containing the defective module. Since the module is not detachable from the card, the entire card (including the module) must be replaced.

High Tx Power Severity: Critical The High Tx Power alarm indicates that the transmitted power is higher than the maximum allowed value. To clear a High Tx Power alarm: |

Replace the optical module.

432006-2444-0H3-A00


11-59


EMS-XDM User Manual

Invalid Carrier Severity: Major The Invalid Carrier alarm indicates an out-of-grid carrier (that is, above the noise threshold) or a double carrier (within a grid window). The alarm is generated for one or more invalid carriers. This alarm applies only to OPM cards and is detected when the OPM scans the spectrum and identifies a wavelength(s) that is not defined. The alarm usually occurs during installation or when adding another lambda with the wrong setups. This alarm can result from: |

A non-WDM transmitter connected to a WDM system

|

A misplaced transmitter

To clear an Invalid Carrier alarm: 1. Check if a non-WDM transmitter is connected to a WDM system by looking for a misplaced transmitter. 2. In the Mux, check for two channels assigned to the same wavelength.

Laser Bias Severity: Major The Laser Bias alarm indicates that the laser bias current is becoming low, signaling the end of life of the device. To clear a Laser Bias alarm: |

Replace the optical module.

Low Optical Signal to Noise Ratio (OSNR) Severity: Major The Low OSNR alarm indicates that the OSNR, as measured by the OPM card, is lower than the minimum threshold value. This alarm applies only on OPM cards. To clear a Low OSNR alarm: 1. Clean the fiber connectors for all components in the optical path. 2. Check all amplifiers and the gain block input to ensure that they are within the required ranges.

11-60


432006-2444-0H3-A00

EMS-XDM User Manual


Low Rx Power Severity: Major The Low Rx Power alarm indicates that the received power is lower than the minimum allowed value. To clear a Low Rx Power alarm: 1. Check the optical parameters, especially the Input Power level, to ensure they are within the required ranges. 2. Check the transmitter on the other-side node. 3. Check line amplifiers and OADMs. 4. Check whether there are any bent fibers or dirty connectors.

Low Tx Power Severity: Critical The Low Tx Power alarm indicates that the transmitted power is lower than the minimum allowed value. To clear a Low Tx Power alarm: 1. Check the optical parameters, especially the Input Power level, to verify that they are within the required ranges. 2. Try switching the ALS feature to Off.

Midstage Out of Range Severity: Major The Midstage Out of Range alarm indicates that OFA_M is in passive mode and its midstage attenuation is either below 5 dB or above 9 dB. When OFA_M is in passive mode, it automatically measures its midstage attenuation. This alarm applies only to the OFA_M card. To clear a Midstage Out of Range alarm: |

Check the midstage attenuation and increase or decrease it, as required.

432006-2444-0H3-A00


11-61


EMS-XDM User Manual

Missing Carrier Severity: Major The Missing Carrier alarm indicates a mismatch between the expected carriers list and the present carriers, as measured. The alarm is generated for one or more mismatches. This alarm applies only to OPM cards. To clear a Missing Carrier alarm: 1. Check the inputs to the Mux or DeMux for the missing channel. 2. Change the OPM card configuration (if this channel is not active).

OAM Alarms The following topics describe OAM (Optical Amplifier Module) alarms that occur in MCS and DIO cards (on ETY ports only). |

OAM Discovery Failure

|

OAM Link Lost

|

OAM Remote Link Failure

|

OAM Remote Link Event

|

OAM Local Link Event

OAM Discovery Failure Severity: Major The OAM Discovery Failure alarm indicates the incompletion of the discovery process and that settings of the local and remote port are incompatible. To clear an OAM Discovery Failure alarm: 1. Check that the local port is in passive-peer-only mode and that the remote port is passive, or that the remote port is in passive-peer-only mode and that the local port is passive. 2. Change the mode.

11-62


432006-2444-0H3-A00

EMS-XDM User Manual


OAM Link Lost Severity: Major The OAM Link Lost alarm indicates there has been no OAM PDUs from the remote port for 5 seconds. To clear an OAM Link Lost alarm:: |

Check the link.

OAM Remote Link Failure Severity: Major The OAM Remote Link Failure alarm indicates that the remote port reports a link fault (Link Fault bit set within the Flags field of OAMPDU received from remote port). To clear an OAM Remote Link Failure alarm: |

Check the link.

OAM Remote Link Event Severity: Warning The OAM Remote Link Event alarm indicates the link event the OAM PDU received. To clear an OAM Remote Link Event alarm: |

Check the link.

OAM Local Link Event Severity: Warning The OAM Local Link Event alarm indicates one of link events occurred: Errored Symbol Period, Errored Frame, Errored Frame Period, or Errored Frame Seconds Summary. To clear an OAM Local Link Event alarm: |

Check the link.

432006-2444-0H3-A00


11-63


EMS-XDM User Manual

Power In LOS Severity: Major The Power In LOS alarm indicates a loss of signal in Modules Cage modules (amplifiers). This alarm condition is conveyed as an equipment alarm instead of as a transmission alarm, as the affected modules do not have transmission objects.

Optical Power High Back Reflection Severity: Major The Optical Power High Back Reflection alarm indicates that at the output of an optical amplifier, the fiber is disconnected and the transmitted power is reflected back. To clear an Optical Power High Back Reflection alarm: |

Check the fiber and connectors from the amplifier output.

Switch Fail Severity: Major The Switch Fail alarm is specific to OPM cards where the 1:4 switch may fail. The alarm usually indicates a card hardware failure. To clear a Switch Fail alarm: |

Test the switch multiple times to ensure that the alarm is not a one-time event. If this action fails, contact ECI Telecom customer support.

Temperature (Temp) Out of Range Severity: Major The Temp Out of Range alarm is specific to AWG-based WDM modules (Muxes/DeMuxes, OADMs, and so on) in which temperature stability is crucial. The alarm usually indicates a hardware failure. To clear a Temp Out of Range alarm: |

11-64

Verify that the environmental conditions are within the operational limits of the equipment.


432006-2444-0H3-A00

EMS-XDM User Manual


Unexpected Carrier Severity: Major The Unexpected Carrier alarm indicates a mismatch between the expected carrier list and the present carriers, as measured. The alarm is generated for one or more mismatches and is detected when assigning a channel. This alarm applies only to OPM cards. To clear an Unexpected Carrier alarm: 1. Check the carrier list to ensure that it is correct and that channels are correctly assigned. Correct this list if it is in error. 2. Verify that the channel should in fact be on this link. If so, assign the new channel in the OPM card. If the channel is incorrectly assigned, remove it.

Wavelength Mismatch Severity: Major The Wavelength Mismatch alarm indicates that the expected configured wavelength differs from the actual value supported by the optical module. This alarm usually occurs during installation or maintenance (if replacing a module with the wrong type). To clear a Wavelength Mismatch alarm: |

In the object Info window, change the wavelength to the actual wavelength.

XDM-100 and XDM-300 Equipment Alarms The following topic describes the XDM equipment alarms specific to the XDM-100 and XDM-300 shelves.

Lock Open Severity: Major The Lock Open alarm indicates that in the XDM-100 or XDM-300, the MXC card is not properly inserted or the lock on this card is open. To clear a Lock Open alarm: |

Check that the MXC card is inserted properly in the slot and that the lock of the card is closed.

432006-2444-0H3-A00


11-65


11-68

EMS-XDM User Manual

Alarm name

Probable cause

Operate Loopback Action Failed

Failure to activate loopback at NE level

PM All Endpoint Counter

PM all endpoint counter alarm

PM Endpoint Counter

PM endpoint counter alarm

PM Get Endpoint Counter

PM get endpoint counter alarm

Release Equipment Lockout Failed

Failure to release lockout action at NE level

Release Equipment Protection Failed

Failure to release equipment protection action at NE level

Release Loopback Action Failed

Failure to release loopback at NE level

Restart Processor Action Failed

Failure to reset NE card

Set Request Failed

Set request failed

Set Request Rejected

Set request is rejected

Switch to Protection Failed

Failure to activate switch protection action at NE level

Unassignment Failed

Failure to unassign NE card

Update Bi-directional Action Failed

NE update of bidirectional pointers (related to cross connection activities) failed


432006-2444-0H3-A00

EMS-XDM User Manual


Maintenance operations per object Object

Maintenance operations

MS Src

Force RDI

AU-4 Snk

Force TU/AU-AIS

AU-4 Src

Force TU/AU-AIS, Force RDI

VC-4

Force AIS, Force RDI, Facility (Far-End) Loopback*, Terminal (Near-End) Loopback*

*Can only be done when the object is on a bidirectional cross connection.

SIO1_8E, SIOM1_E, SIO_16E, and SIOM1_16E Objects in card SPI SRC, SPI Snk, RS Src, RS Snk, MS Src, MS Snk, AU-4 Src, AU-4 Snk, VC-4 Src, VC-4 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

SPI Snk

LOS

RS Snk

LOF, TIM, UATNE, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBENE 1 Day, ESNE 1 Day, SESNE 1 Day

MS Snk

AIS, EXC, DEG, RDI, MSPL Failure, UATNE, UATFE, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBENE 1 Day, ESNE 1 Day, SESNE 1 Day, BBEFE 15 Min, ESFE 15 Min, SESFE 15 Min, BBEFE 1 Day, ESFE1 Day, SESFE 1 Day

AU-4 Snk

CTP AIS, LOP, AIS, EXC, DEG, RDI, TIM, SSF, UNEQ, PLM, LOM, LOA



MS Src

Force RDI

AU-4 Snk

Force TU/AU-AIS

AU-4 Src


VC-4



432006-2444-0H3-A00


11-71


EMS-XDM User Manual

SIO4_4 and SIOM4_4 Objects in card OM4, OT4, SPI Src, SPI Snk, RS Src, RS Snk, MS Src, MS Snk, AU-4 Snk, AU-4 Src, VC-4 Src, VC-4 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

OM64

Card Out, Type Mismatch, Power Failure, Card Failure, Wavelength Mismatch Alarm, Application Code Mismatch

OT4

Card Out, Type Mismatch, Power Failure, Card Failure, Low Temperature, High Temperature, Low Rx Power, High Rx Power, Low Tx Power, High Tx Power, Laser Bias

SPI Snk

LOS

RS Snk


MS Snk


AU-4 Snk




MS Src

Force RDI

AU-4 Snk

Force TU/AU-AIS

AU-4 Src


VC-4



11-72


432006-2444-0H3-A00

EMS-XDM User Manual


SIO16_1, SIOM16_1, and SIO16_2 Objects in card OM16, OT16, SPI Src, SPI Snk, MS Src, MS Snk, RS Src, RS Snk, AU-4 Src, AU-4 Snk, VC-4 Src, VC-4 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

OM16


OT16




MS Src

Force RDI

AU-4 Snk

Force TU/AU-AIS

AU-4 Src

Force TU/AU-AIS, Force RDI*

VC-4


*Supported only for an AU in a concatenated group. *Can only be done when the object is on a bidirectional cross connection.

432006-2444-0H3-A00


11-73


EMS-XDM User Manual

SIO1_16O and SIOM1_16O Objects in card OM, OT, SPI Src, SPI Snk, RS Src, RS Snk, MS Src, MS Snk, AU-4 Snk, AU4 Src, VC-4 Src, VC-4 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

OM


OT


PST64

Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail

RS Snk


MS Snk


AU-4 Snk




MS Src

Force RDI

AU-4 Snk

Force TU/AU-AIS

AU-4 Src


VC-4 Snk



11-74


432006-2444-0H3-A00

EMS-XDM User Manual


PIO2_84 Objects in card 2M Src, 2M Snk, VC-12 Src, VC-12 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

2M Src

LOS, LOF, AIS, EXC, DEG, RDI

VC-12 Snk

AIS, EXC, DEG, RDI, TIM, SSF, UNEQ, PLM, UATNE, UATFE, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBENE 1 Day, ESNE 1 Day, SESNE 1 Day, BBEFE 15 Min, ESFE 15 Min, SESFE 15 Min, BBEFE 1 Day, ESFE1 Day, SESFE 1 Day



2M Src

Force AIS, Terminal (near-End) Loopback*

2M Snk

Facility (Far-End) Loopback, Force AIS

VC-12 Src

Force AIS, Force RDI

VC-12 Snk

Force AIS

*Can only be done when the object is on a bidirectional cross connection. NOTE: NewPIO2_84H card replaces the existing PIO2_84 card due to obsolete components. An EOL for PIO2_84 is to be issued during 2009.

432006-2444-0H3-A00


11-75


EMS-XDM User Manual

PIO345_16 and PIO345_8 Objects in card 45M Src, 45M Snk, VC-3 Src, VC-3 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

45M Src

LOS, LOF, AIS, EXC, DEG, RDI

VC-3 Snk

AIS, EXC, DEG, RDI, TIM, SSF, UNEQ, PLM, UATNE, UATFE, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBENE 1 Day, ESNE 1 Day, SESNE 1 Day, BBEFE 15 Min, ESFE 15 Min, SESFE 15 Min, BBEFE 1 Day, ESFE1 Day, SESFE 1 Day



45M Src

Force AIS, NE Loopback*

45M Snk

FE Loopback, Force AIS

VC-3 Src


VC-3 Snk

Force AIS


11-76


432006-2444-0H3-A00

EMS-XDM User Manual


TRP10_2 Objects in card OM10_1xx, OM10_1, OT10, OPS Src, OPS Snk, OCH Src, OCH Snk, RS Src, RS Snk, OPG Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object Object

Alarms

OM10_1xx

Card Out, Type Mismatch, Power Failure, Card Failure, Wavelength Mismatch, Application Code Mismatch

OM10_1

Card Out, Type Mismatch, Power Failure, Card Failure, Application Code Mismatch

OT10

Card Out, Type Mismatch, Power Failure, Card Failure, Laser Temperature Low, Laser Temperature High, Low Rx Power, High Rx Power, Low Tx Power, High Tx Power, Laser Bias High

OCH Snk

LOF, EXC, DEG, TIM, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBEFE 1 Day, ESNE 1 Day, SESNE 1 Day

OPS Snk

LOS, LOD

OPG

Card Out, Type Mismatch, Power Failure, Card Failure

RS Snk


432006-2444-0H3-A00


11-77


EMS-XDM User Manual

TRP25_2 Objects in card OMT25xx, OMT25, OTx, OMR25C, ORx, OPS Src, OPS Snk, OCH Src, OCH Snk, RS Src, RS Snk, OPG Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object

11-78

Object

Alarms

OMT25xx


OMT25


Otx

Card Out, Type Mismatch, Power Failure, Card Failure, Laser Temperature Low, Laser Temperature High, Low Tx Power, High Tx Power, Laser Bias High

OMR25C


Orx

Card Out, Type Mismatch, Power Failure, Card Failure, Low Rx Power, High Rx Power

OCH Snk


OPS Snk

LOS, LOD

OPG


RS Snk



432006-2444-0H3-A00

EMS-XDM User Manual


TRP25_2C Objects in card OMT25xx, OMT25, OTx, OMR25C, ORx, OPS Src, OPS Src, OPS Snk, OCH Src, OCH Snk, DSR Src, DSR Snk, OPG Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object Object

Alarms

OMT25xx


OMT25


Otx


OMR25C


Orx


OCH Snk


OPS Snk

LOS, LOD

OPG


432006-2444-0H3-A00


11-79


EMS-XDM User Manual

TRP25_2G Objects in card OMT25xx, OMT25, OTx, OMR25C, ORx, OPS Src, OPS Snk, OCH Src, OCH Snk, GbE Src, GbE Snk, OPG Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object

11-80

Object

Alarms

OMT25xx


OMT25


Otx


OMR25C


Orx


GbE Snk

LOF, EXC, DEG, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBEFE 1 Day, ESNE 1 Day, SESNE 1 Day

OCH Snk


OPS Snk

LOS, LOD

OPG



432006-2444-0H3-A00

EMS-XDM User Manual


TRP25_2V Objects in card T6XX, OTx, MBR6, ORx, OPS Src, OCH Src, OPI Snk, OPS Snk, OCH Snk, OPG Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object Object

Alarms

OMT25xx


OMT25


Otx


OMR25C


Orx


OPS Snk

LOS, LOD

OPG


432006-2444-0H3-A00


11-81


EMS-XDM User Manual

OFA Objects in card OM_BAC, OM_PAC, OM_ILC, OTRx, OTS Src, OTS Snk, OMS Src, OMS Snk, Power Ctrl Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object Object

Alarms

OM_BAC; OM_PAC; OM_ILC


OTRx

Card Out, Type Mismatch, Power Failure, Card Failure, Low Temperature, High Temperature, Low Rx Power, High Rx Power, Low Tx Power, High Tx Power, Pump Bias High

OTS Snk

LOS

Power Control

Tracking Limit Exceeded, Input Power Change, Set Capability Exceeded, Gain Input Overload

OFA_M Objects in card OM, OTRx, OTS Src, OTS Snk, OMS Src, OMS Snk, Power Ctrl Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object

11-82

Object

Alarms

OM_OFA_M

Card Out, Type Mismatch, Power Failure, Card Failure, Application Code Mismatch, Midstage Out of Range

OT_OFA_M

Card Out, Type Mismatch, Power Failure, Card Failure, Power Reflect, High Rx Power, Low Tx Power

OTS Snk

LOS

Power Control



432006-2444-0H3-A00

EMS-XDM User Manual


OFA_R Objects in card OM, OTS Snk, OMS Snk, OCH CTP SNC Alarms at card level Card Out, Type Mismatch Alarms per object Object

Alarms

OM_OFA_R

Card Out, Type Mismatch

OT_OFA_R

Card Out, Type Mismatch, Power Failure, Card Failure, Power Reflect, High Rx Power, Low Tx Power

OTS Snk

LOS

OMSP and OMSPA Objects in card OMSP, OTRX, OTS Src, OTS Snk, Optical PG Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object Object

Alarms

OMSP


OTRx


Optical PG

Service Failure, Service Degraded, Protection Path Failure, Protection Path Degraded



Optical PG

Optical PG Lockout, Optical PG Force Switch, Optical PG Section Switch

432006-2444-0H3-A00


11-83


EMS-XDM User Manual

OPM Objects in card OM_PM, OPS_M Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, Switch Failure Alarms per object Object

Alarms

OM_PM

Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail

OPS_M

Low OSNR, Missing Carrier, Unexpected Carrier, Invalid Carrier



OPS_M

Get OPM PM Data

AUX_2I and AUX_2X Objects in card OM-1, OM-2 Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded, Program Fail Alarms per object

11-84

Object

Alarms

OM_1; OM_2



432006-2444-0H3-A00

EMS-XDM User Manual


DIO1_20 and DIO1_40F Objects in card OM, OT, OPI Src, OPI Snk, GEoS Src, GEoS Snk, VC-4 Src, VC-4 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure Alarms per object Object

Alarms

OPI Snk

LOS, LOD

GEoS Snk

Auto Negotiation Fail, Auto Negotiation Ability Mismatch, Partner Offline, Partner Link Fail, Partner Auto Negotiation Fail, Link Down, Rx Buffer Overflow, Tx Buffer Overflow, Tx Good Packets Count 15 Min, Tx Bytes Count 15 Min, Rx Good Packets Count 15 Min, Rx Bytes Count 15 Min, Tx Error Packets 15 Min, Packet Drop Event 15 Min, Tx Good Packets Count 1 Day, Tx Bytes Count 1 Day, Rx Good Packets Count 1 Day, Rx Bytes Count 1 Day, Tx Error Packets 1 Day, Packet Drop Event 1 Day



VC-4 Src


432006-2444-0H3-A00


11-85


EMS-XDM User Manual

DIO1_61 Objects in card OM, OT, OPI, Src, OPI Snk, GEoS Src, GEoS Snk, SPI Src, SPI Snk, MS Src, MS Snk, RS Src, RS Snk, VC-4 Src, VC-4 Snk, AU-4 Src, AU-4 Snk Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure Alarms per object Object

Alarms

OMDIO

Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Slightly Degraded

OT


OPI Snk

LOS, LOD

GEoS Snk

Auto Negotiation Fail, Auto Negotiation Ability Mismatch, Partner Offline, Partner Link Fail, Partner Auto Negotiation Fail, Link Fail, Rx Buffer Overflow, Tx Buffer Overflow, Tx Good packets Count 15 Min, Tx Bytes Count 15 Min, Rx Good Packets Count 15 Min, Tx Bytes Count 15 Min, Tx Error Packets Count 15 Min

SPI Snk

LOS

RS Snk

LOF, TIM, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBENE 1 Day, ESNE 1 Day, SESNE 1 Day

MS Snk


AU-4 Snk

AU/TU-AIS, LOP

VC-4 Snk

AIS, EXC, DEG, EDI, TIM, SSF, UNEQ, PLM, LOA, LOMC, PJ 15 Min, UAT, BBENE 15 Min, ESNE 15 Min, SESNE 15 Min, BBENE 1 Day, ESNE 1 Day, SESNE 1 Day, BBEFE 15 Min, ESFE 15 Min, SESFE 15 Min, BBEFE 1 Day, ESFE 1 Day, SESFE 1 Day

Maintenance operations per object

11-86

Object


RS Src

Terminal (Near-End) Loopback

MS Src

Force RDI

MS Snk

Facility (Far-End) Loopback

VC-4 Src



432006-2444-0H3-A00

EMS-XDM User Manual


OADM4REW, OADM4GEW, and OADM1EW Objects in card OM_EW_ALS_SW or OM_EW_ALS or OM_EW_SW or OM_EW and OM_AD1QEWxx or OM_AD4RQEWxx or OM_AD4GQEWxx and OTRxx, OTRx, OTS Src, OTS Snk, OMS Src, OMS Snk, OPS Src, OPS Snk, Power Control Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

OM_EW_ALS_SW; Card Out, Type Mismatch, Power Failure, Card Failure OM_EW_ALS; OM_EW_SW;OM_ EW OM_AD1QEWxx; Card Out, Type Mismatch, Power Failure, Card Failure OM_AD4RQEWxx; OM_AD4GQEWxx OTRx

Card Out, Type Mismatch, Power Failure, Card Failure, Low Rx Power, High Rx Power, Low Tx Power, High Tx Power

OTRxx


OPS Snk

LOS

OTS Snk

LOS

Power Control


432006-2444-0H3-A00


11-87


EMS-XDM User Manual

OADM4RAB, OADM4GAB, and OADM1AB Objects in card OM_AB_ALS_SW or OM_AB_ALS or OM_AB_SW or OM_AB and OM_AD1QABxx or OM_AD4RQABxx or OM_AD4GQABxx and OTRxx, OTRx, OTS Src, OTS Snk, OMS Src, OMS Snk, OPS Src, OPS Snk, Power Control Alarms at card level Card Out, Type Mismatch, Power Failure, Card Failure, BIT Failed, BIT Degraded, BIT Not OK, Program Fail Alarms per object Object

Alarms

OM_EW_ALS_SW; Card Out, Type Mismatch, Power Failure, Card Failure OM_EW_ALS; OM_EW_SW;OM_EW

11-88

OM_AD1QEWxx; OM_AD4RQEWxx; OM_AD4GQEWxx


OTRx

Card Out, Type Mismatch, Power Failure, Card Failure, Low Rx Power, High Rx Power, Low Tx Power, High Tx Power

OTRxx


OPS Snk

LOS

OTS Snk

LOS

Power Control



432006-2444-0H3-A00

Troubleshooting Alarms

Recommend Documents