Chinese
English
Huawei SDH Faults
1.1 R_LOS
Alarm name or fault phenomenon:
The R_LOS alarm indicates Receive loss of signal on the receiving line side ( Receive loss of signal ) and is an emergency alarm.
Alarm causes:
1, fiber break;
2, line attenuation is too large;
Failure of receiving direction of this board;
4. Failure of the transmitting part of the opposite end station, line transmission failure;
5, the opposite end station cross clock board failure or not in position.
Alarm processing methods:
1. Use an optical power meter to detect whether the received optical power of the alarm board is normal. If the received optical power is normal, go to step 8.
2、Check whether the fiber optic cable is faulty. After eliminating the fault of the fiber optic cable, check whether the alarm is eliminated.
3、Clean the pigtail connector of this station and the receiving optical port of the circuit board to see if the alarm is excluded.
4、Check whether the flange and optical attenuator of this station are connected correctly and whether the attenuation value of the optical attenuator is too large. After using the flange and optical attenuator correctly, check whether the alarm is excluded.
5, use the optical power meter to check whether the transmitter optical power of the opposite end station is normal, if the transmitter optical power is not normal, replace the circuit board.
6. If the transmit optical power is normal, clean the pigtail connector of the end station and check whether the alarm is excluded.
7、Check whether the flange and optical attenuator of the terminal station are connected correctly and whether the attenuation value of the optical attenuator is too large. After using the flange and optical attenuator correctly, check whether the alarm is eliminated.
8、Replace the circuit board of the alarm reported on this station to see if the alarm is excluded.
9、Replace the line board of the opposite station to see if the alarm is excluded.
1.2 R_LOF, R_OOF
Alarm name or fault phenomenon:
R_LOF alarm indicates Receive loss of frame (Receive loss of frame ) on the line side, which is an emergency alarm.
Alarm causes:
1、Receive signal attenuation is too large;
2. No frame structure in the transmit signal from the opposite end station;
3. Failure in the receiving direction of this board.
Alarm processing method:
1. Check whether there are high-level R_LOS alarms on the network management, prioritize these high-level alarms, and then check whether the alarms are excluded.
2. Check whether the received optical power of the alarm board is normal. If the received optical power is normal, go to step 9. If the received optical power is not normal, let the site locate whether the attenuation point is in the server room or on the line, if on the line, go to step 8.
3. Clean the pigtail connector of this station and the receiving optical port of the circuit board to see if the alarm is excluded.
4. Check whether the flange and optical attenuator of this station are connected correctly and whether the attenuation value of the optical attenuator is too large. After using the flange and optical attenuator correctly, check whether the alarm is excluded.
5、Check whether the transmitter optical power of the opposite end station is normal, if the transmitter optical power is not normal, replace the circuit board.
6. If the transmit optical power is normal, clean the pigtail connector of the end station and check whether the alarm is excluded.
7、Check whether the flange and optical attenuator of the terminal station are connected correctly and whether the attenuation value of the optical attenuator is too large. After using the flange and optical attenuator correctly, check whether the alarm is eliminated.
8、Check whether the fiber optic cable is faulty. After eliminating the fault of the fiber optic cable, check whether the alarm is eliminated.
9、Replace the circuit board of the alarm reported on this station to see if the alarm is excluded.
10、 Replace the line board of the opposite station to see if the alarm is excluded.
1.3 MS_AIS
Alarm name or fault phenomenon:
MS_AIS alarm indicates Multiplex section alarm indication
Cause of alarm:
1. MS_AIS signal is sent from the peer station;
2. Clock board failure of the peer station;
3. Failure of the receiving section of this board.
Alarm processing method:
1. Check whether there are R_LOS and R_LOF alarms on the corresponding line board on the network management, and check whether the alarms are excluded after excluding R_LOS and R_LOF alarms.
2、Test whether the received optical power of the alarm single board is normal.
3, with the pigtail at the end and the opposite end of the optical port for the inner loopback, check whether the alarm is excluded, if not excluded, continue the following steps to locate
4, reset and replace the circuit board on this site to see if the alarm is excluded.
5、Reset and replace the line board of the opposite end station to see if the alarm is excluded.
1.4 IN_PWR_LOW, IN_PWR_ABN, IN_PWR_FAIL
Alarm name or fault phenomenon:
Optical power too low, too high, abnormal
Cause of alarm:
1、 Fiber optic connector is dirty;
2. The tail fiber is bent too much, damaged or aged;
The receiving optical port of the single board in this station is equipped with too large an optical attenuator.
4, the optical signal attenuation in the transmission process is too large, not enough compensation for optical amplification;
5, the transmitter optical port of the end station board added too large optical attenuator or transmitter optical module failure, resulting in low transmitter optical power to the end station board;
6. The single board of this station fails.
Alarm processing methods:
1, high optical power can be directly added to the attenuation to deal with
2、 For low and abnormal optical power, use OTDR to test whether the fiber optic cable has abnormal attenuation.
3、 Use the optical power meter to measure whether the input optical power of the single board in the normal range;
4, if the measurement results are within the normal range of reception, but the reported performance value is incorrect, it may be a single board failure at this site, replace the faulty single board;
5、 If the measurement result is relatively low, check the fiber optic connector, if there is dirt, clean or replace the fiber optic connector.
6、 If the alarm is not cleared, check the pigtail, if the pigtail is bent too much, damaged or aged, adjust the pigtail or replace the pigtail.
7, if the alarm is not cleared, query the performance value of the output optical power of the single board of the terminal station and the related alarm, if the queried performance value is not in line with the index value, for example, there is a TF alarm, then it is a failure of the optical module, replace the single board of the terminal station.
1.5 B1_EXC, B1_SD, B2_EXC, B2_SD
Alarm name or fault phenomenon:
BER overrun alarm. That is, the signal quality of SDH frames received by the single board is deteriorated .
Cause:
1、 Received signal attenuation is large, the fiber or connector is not clean;
2. Failure of the transmitting part of the opposite end station;
3. Failure of the receiving part of this station.
Alarm processing methods:
1, through the T2000 query optical port received optical power is within the normal range. If the received optical power of this station is too low, clear the alarm according to the processing steps of IN_PWR_LOW;
2. If the optical power is normal but there is still BER, let the field maintenance personnel use the pigtail fiber to make a self-loop on the single board, and if there is still BER, replace the single board. If the error code disappears, let the field maintenance personnel of the opposite end equipment use the pigtail fiber to make a self-loop on the single board, and if there is an error code, replace the single board;
3, if the two ends of the self-loop no error code, unloop back to the error code, check the tail fiber, if the tail fiber is too bent, damaged or aging, adjust the tail fiber or replace the tail fiber.
1.6 MS_REI
Alarm name or fault phenomenon:
MS_REI alarm indicates that the far end of the multiplexing section has an error code indication.
Cause of alarm:
B2 error code received at the opposite end station
Alarm processing method:
Check whether there is any error code at the opposite end, and handle it according to "Alarm B1_EXC, B1_SD, B2_EXC, B2_SD ".
1.7 TD, TF, LSR_WILL_DIE
Alarm name or fault phenomenon:
Laser failure
Cause of alarm:
Laser failure
Alarm processing method:
Replace the faulty single board
1.8 NESTATE_INSTALL
Alarm name or fault phenomenon:
The network element is in the installation state , and the network element is not configured with the data alarm.
Reason for alarm:
The network element is in the installation state , and the network element is not configured with data alarm.
Alarm processing method:
Dispatch to specialized room
1.9 COMMUN_FAIL
Alarm name or fault phenomenon:
Single board serial port communication failure.
Cause of alarm:
1. Single board failure.
Alarm processing methods:
Look at the parameters of the alarm, if the parameters show that the single board failure, you can check the single board running lights, unplug the single board, replace the single board to troubleshoot by the scene; if the parameters show that the other single board failure, check the running lights of the single board shown in the parameters, unplug the single board, replace the single board to troubleshoot; if it shows that it is a problem with the network cable, you need to check the network cable and replace it. Because of the parameters involved, it is recommended to contact the professional room or on-site factory supervisor to deal with.
1.10 FAN_FAIL
Alarm name or fault phenomenon:
Fan Failure.
Cause of alarm:
1. False alarm report;
2、Fan failure.
Alarm processing methods:
1、Let the site check the operation of the fan, if the fan is abnormal, replace the faulty fan
1.11 APS_FAIL
Alarm name or fault phenomenon:
APS_FAIL alarm indicates protection reversal failure indication
Cause of alarm:
1. The node's multiplexing segment protection parameters are set incorrectly;
2、The node's multiplexing segment protection parameter is lost.
Alarm processing method:
Please dispatch the order to the specialized room for processing.
Alcatel SDH fault
2.1 RUP, RUM, ICP class alarm processing
Alarm name or fault phenomenon: Replaceable Unit Problem; Replaceable Unit Missed; Internal Communication Problem The corresponding faulty unit reports fault.
Causes of Alarms:
1. Cause 1 RUM may also be the board configured by the network administrator, but the actual board is plugged in.
2. Cause 2 Hardware failure of the disk
3. Cause 3 ICP may be caused by other disks, such as the matrix and master of 1660, SYNTH16 of 1662, and the MB board of 1642.
Alarm processing methods:
1. Cause 1 for RUM first verify whether the site per plug board, such as no plug board can be configured in the network management (for the configuration of the circuit or as a clock source, you need to delete these configurations), of course, the site per plug board, by the configuration of the circuit or the clock source need to be carefully verified whether it is garbage data in the deletion.
2. Cause 2 to replace the corresponding fault disk
3. If the ICP alarm does not disappear after replacing the faulty disk, you should consider that it may be caused by other matrix, master control, SYNTH16, MB disk, etc. You can first do a test on these suspected boards. You can first plug and unplug these suspected boards (pay attention to the impact on business and monitoring, generally the main control board plug and unplug only affects the monitoring; matrix and SYNTH16 are protected, if there is no abnormal state or the second failure, plug and unplug the spare does not affect the business (to plug and unplug the current main matrix need to be switched to the spare role before plugging, switch and then wait for 15 minutes to let it synchronize and then operate)), and then locate the faulty boards and then replace the faulty boards. board and then replace the faulty board.
2.2 TD, URU, TF Alarm
Alarm name or fault phenomenon: TD ( Transmitter Degraded ) , URU ( Underlying Resource Unavailable ) , TF ( Transmitter Failure ) alarms are reported on the device's optical interface or port.
Alarm causes:
1. Cause 1 may be a failure if there is a disk for the optical module
2. Cause 2 Disk failure
How to handle the alarm:
1. Cause 1 Replace the optical module
2. Cause 2 Replace the diskette
2.3 LOS, LOF Alarm Handling
Alarm name or fault phenomenon: LOS ( Loss of signal; LOF (Loss Of Frame);MS-AIS; MS-RDI alarm
Cause of alarm:
1. Cause 1 Fiber optic cable failure
2. Cause 2 Power failure or hang-up of the opposite-end equipment (mainly access equipment)
3. Cause 3 apparent hardware failure, the corresponding fiber optic board reports RUP, RUM, ICP, URU, TD, TF and other alarms
4. Cause 4 Hidden hardware failure
5. Cause 5 Optical module hangs
Alarm handling methods:
1. cause 1 to optical and OTDR test, etc. to check the optical path failure, clear the fiber optic cable failure (see fiber optic cable failure processing)
2. Cause 2 On-site power on or ring MB board
3. Cause 3 Appears to be a hardware failure, please replace the corresponding faulty board
4. Cause 4 When the optical path is normal to the light and there is no obvious hardware failure, then it may be a hidden hardware failure. The treatment method is as follows: first, do the self loop of the corresponding ports on both sides of the pigtail, see which optical port fails to appear after the self loop, then replace the optical board. Do optical port self-loop need to pay attention to the following issues: 1: pay attention to the optical power, according to different CD-ROM to add different attenuators, to avoid overloading, optical port parameters, see \ 10.244.9.52
etwork management group Learning Materials (GPON PTN) Alcatel training materials/
5. Reason 5: For Alcatel CD-ROMs with number beginning with 8DG ( L64.2E ), the optical module may hang and not emit light after an LOS alarm occurs, so you need to plug and unplug the optical module on site.
2.4 Optical port EBER, DS alarm processing
Alarm name or fault phenomenon: EBER ( Excessive EBER performance limit); DS ( Degraded Signal ), optical port performance degradation.
Cause of alarm:
1. Cause 1 Fiber optic cable failure
2. Cause 2 Hidden hardware failure
Alarm handling methods:
1. Cause 1 Check for optical path faults such as optical-to-optical and OTDR tests, and clear optical cable faults (see Optical Cable Fault Handling for details)
2. Cause 2 When the optical path is normal to the light, it may be a hidden hardware failure. Processing methods are as follows: first of all, the corresponding ports on both sides of the tail fiber self-loop, self-loop to check the performance of the optical port, see that the CD-ROM still has error codes, then replace that piece of optical board. Do optical port self-loop need to pay attention to the following issues: 1: pay attention to the optical power, according to different CD-ROM to add different attenuators, to avoid overloading, optical port parameters, see \ 10.244.9.52
etwork management group Learning Materials (GPON PTN) Alcatel training materials/
2.5 CSF Alarm Handling
Alarm name or fault phenomenon: CSF ( Communication signal failure );
Cause of alarm:
1. Cause 1 The LAPD configurations of the corresponding optical ports at both ends do not match or one side is not configured.
2. Cause 2 There are other alarms such as LOS, LOF, MS-RDI, MS-AIS, DS, EBER, RUP, RUM, etc. on the corresponding optical boards.
3. Cause 3 Faulty SYNTH16 disk on 1660 master board, 1642 MB board, 1662 6-slot
Alarm handling methods:
1. Cause 1 Reconfigure LAPD, the configuration principle is that NETWORK must be paired with USER.
2. cause 2 Tackle other faults first to clear this alarm.
3. Cause 3 Plug or reboot the corresponding master control board (usually it is a problem with the counterpart device of the network element that reports CSF alarm) or change the master control board.
2.6 CPE Alarm Handling
Alarm name or fault phenomenon: CPE ( Communication Protocol Error )
Alarm causes:
1. Cause 1 Configuration problem
2. Cause 2 Hardware problem
Alarm handling methods:
1. Cause 1 For the optical port of the alarm belongs to MSP1+1 protection group, generally the uni-directional and bi-directional options of the network elements on both sides of the protection group are not the same, and it is enough to delete the protection group and reconfigure it. Before deleting the protection group, please verify that the primary and backup optical ports are available, otherwise the service may be affected. For MSP-SPRING ring protection optical port, it is upgraded to the transmission room for processing.
2. Cause 2 If the corresponding board has RUP, RUM, and other alarms. Otherwise, escalate to the transmission room for processing.
2.7 inside failuer alarm processing
Alarm name or failure phenomenon: inside failure Internal bus alarm
Cause of alarm:
1. Cause 1 The device clock is in a free oscillation state, and there is no valid reference clock.
2. Cause 2 Service board failure
3. Cause 3 Matrix failure
Alarm processing method:
1. Cause 1 At this time, the standby matrix to all service disks is red, you need to deal with the clock failure first.
2. Cause 2 If a service disk to the primary and backup matrices are all red, replace the service disk first. If only one business disk to one matrix has a red line, also replace the business disk first to see if the fault disappears.
3. Cause 3 If there are red lines from a particular matrix to more than one business disk, replace that matrix.
2.8 Cooling Fan Failure, HOUSE KEEPING alarm processing
Alarm name or fault phenomenon: fan alarm alarm
Cause of alarm:
1. Cause 1 Fan hardware failure
2. Cause 2 Fan power supply failure
Alarm processing method:
1. Cause 1 Replace the failed fan
2. Cause 2 Check if the fan power fuse is on to clear the power failure.
2.9 Battery Failure, Fuse Failure Alarm Handling
Alarm name or fault phenomenon: Power supply related alarm
Alarm cause:
1. Cause 1 External power supply failure
2. Cause 2 CONGI disk failure
Alarm processing method:
1. Cause 1 Handle external power failure, make sure that the header cabinet has power, the power switch on the top of the rack is on, and there is no short circuit imagery
2. Cause 2 Replace the reported faulty CONGI disk. Confirm the corresponding power switch of the CONGI board at the top of the rack before replacing it. After confirming that there is no error, first disconnect the corresponding open light and observe that there should be no power failure of the equipment, then remove the cable on the CONGI board, replace it with a new board and reconnect the cable, and then turn on the corresponding switch at the top of the rack.
2.10 Loss Of Timing Sources; Frequency Offset Alarm Processing
Alarm Name or Fault Phenomenon: Loss of Timing Sources; Frequency Offset Alarm
Cause:
1. Cause 1 No signal from external 2M reference clock
2. Cause 2 No signal from external line reference clock
3. Cause 3 Matrix failure
4. Cause 4 1642 MB board failure
Alarm handling:
1. Cause 1 Check whether the 2M clock line is faulty, if the clock line is confirmed to be correct, then the CONGI disk connected to the clock may be faulty, replace the CONGI disk.
2. Cause 2 Check the line clock source optical port for LOS, LOF and other alarms, if these alarms are handled first; if there is no alarm and the optical signal is normal, then check the opposite end of the device has not sent the clock.
3. Cause 3 If you suspect that the matrix disk problem, upgrade to the transmission room to deal with
4. Cause 4 For 1642, after eliminating cause 2, you can delete the clock configuration and reconfigure it to see if the alarm disappears, if not, you need to replace the MB board.
2.11 Resource Isolation alarm processing
Alarm name or fault phenomenon: Network element de-administration alarm
Alarm cause:
1. Cause 1 Equipment power failure
2. Cause 2 Bi-directional fiber optic cable outage
3. Cause 3 LAPD configuration problem
4. Cause 4 Main control board failure
5. Cause 5 Network management process failure
Alarm handling:
5. Cause 1 Device re-powering
6. Cause 2 Repair the fiber optic cable, see Fiber Optic Cable Troubleshooting
7. Cause 3 If there is a problem with the LAPD configuration, generally the neighboring device's optical port will report a CSF alarm, so please modify the LAPD configuration.
8. Cause 4 Plug/unplug/restart the master disk
9. Cause 5 If there are no faults in causes 1-4 and you can PING the network element, the network management process should be faulty, restart the corresponding EML process.
2.12 Optical Port Unavailable Performance Monitoring Abnormal Alarm Handling
Alarm name or fault phenomenon: new energy monitoring data alarm
Cause:
1. Cause 1 Faulty optical port leads to abnormal performance monitoring data
Alarm processing method:
1. Cause 1 This alarm is a secondary alarm, and it will not be reported again after dealing with the faults related to the optical port; if the faults of the optical port cannot be cleared for a while, you can turn off the performance monitoring first so that it will not be reported again. However, because the alarm is a historical state alarm, even after clearing the primary faults and no longer reporting the related alarms, the alarm entries that have been reported will not disappear. At this time, you can respond to the alarm, and then munual purge (manually clear ) the alarm entries, and the alarm will be permanently cleared in the network management.
2.13 Network Element Cannot Update Alarm Processing
Alarm Name or Fault Phenomenon: The alarm status bar on the device panel is all false, at this time, the alarms of the device can not be updated to the network management, resulting in the alarms seen by the network management are "false" alarms.
Cause:
2. Cause 1 The status of the network element in the network management is not normal.
How to handle the alarm:
2. Cause 1: Stop supervision and thenalign up on 1353NM. After the operation, the alarm status column on the panel diagram of the device should become solid, and the alarms of 1353NM and 1354RM can be updated. In the 1354RM search to the network element to locate the network element belongs to which 1353NM network management methods: selected network elements, click the 1354RM window icon is "magnifying glass" tool button, a pop-up window has a column neGroup = nxx (eg,210) the first digit on the labeled 1353NM network management ( 1 is the convergence 1 network management, 2 is the backbone network management, 3 is the 1678 network management, 4 is the convergence 2 network management), the whole number is the EML process number.
