Escolar Documentos
Profissional Documentos
Cultura Documentos
Security Level:
Huawei Confidential
Contents
1 2 3 4 5 6 7 8 9 10
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes Locating Clock Faults Locating DCN Faults Locating Other Faults Handling Common Alarms Typical Cases of Fault Locating Reference Documents
Huawei Confidential Page 2
11
Record network configurations, operation procedures, fault symptoms, and time points of key events.
Collect data.
End
Huawei Confidential
Page 3
5. Check records of manual operations, operation records on the NMS, and oplog records on
NEs. Check version information, NE configuration, and board configuration. 6. Collect fault information by using specific tools.
Huawei Confidential
Page 4
Contents
1 2 3
Process of Locating Common Faults Locating Link Faults
4
5 6
7
8 9 10 11
No Is Tx power normal? No Yes Is Rx power lower than normal? No Fading causes abnormal Rx power? Yes
No 6 Are links faulty unidirectionally? 7 No Go to the next step. No Faults are rectified? Yes Yes Handle the fault.
End
Huawei Confidential
Page 6
Slow up-fading causes abnormal Rx power. There is external interference. Slow down-fading causes abnormal Rx power. Fast fading causes abnormal Rx power. Fading margin is insufficient. Multipath fading is severe.
Rx power is normal, but the microwave link There is external interference. is faulty unidirectionally.
Huawei Confidential
Page 7
Huawei Confidential
Page 8
Huawei Confidential
Page 9
5. 6. 7. 8. 9.
Huawei Confidential
Page 10
5. Handle fading.
To handle down-fading: Increase the installation heights of antennas. Reduce the transmission distance. Increase the antenna gain. Increase Tx power. To handle fast fading: Contact the network planning department for appropriate plan changes, such as: Adjust the position of the antenna to block the reflected wave or make the reflection point fall on the ground that has a small reflection coefficient, reducing multipath fading. Configure 1+1 SD for microwave links. For microwave links with 1+1 SD, adjust the height difference between two antennas to make one's Rx power higher than the other's Rx power. Increase fading margins by using larger-diameter antennas or raising antennas' Tx power. To handle up-fading: Check for co-channel interference. Use a spectrum analyzer to analyze interference sources. Contact the spectrum management department for clearing the interference spectrum, or change plans to minimize the interference.
Huawei Confidential
Page 11
1. 2. 3. 4. 5. 6.
Perform an inloop on the IF port. Replace the IF board if the fault persists. Check cable connectors and redo the substandard ones. Check IF cables and replace those that are soggy, broken, or pressed. Replace the ODU. If the fault is rectified after replacement, you can infer that the ODU is faulty.
Huawei Confidential
Page 12
The CONFIG_NOSUPPORT is an alarm indicating that the configuration is not supported. Cause 1: The model and configuration parameters of the ODU do not meet the requirements. Cause 2: On Hybrid microwave links, the configured ODU's Tx power is beyond the allowed range. (On Hybrid microwave links, which are composed of IFH2 boards, the maximum Tx power of ODUs is determined by the IF modulation mode and AM enabling status.)
Possible Causes
Handling Procedure Cause 1: The model and configuration parameters of the ODU do not match the requirements.
Check the alarm parameters to determine the configuration parameters that do not meet the requirements. If the alarm parameter is 0x01-0x03, check whether the configuration parameters of the ODU port meet the requirements of network planning. If the alarm parameter is 0x04-0x06, check whether the configuration parameters of the IF port meet the requirements of network planning. If not, change the parameter settings.
Huawei Confidential
Page 13
Possible Causes
Cause 1: Certain other alarms occur at the opposite site. Cause 2: The opposite Tx power is over low. Cause 3: Signal attenuation on the microwave link is heavy.
Huawei Confidential
Page 14
Cause 1: Certain other alarms occur at the opposite site. Check whether any of the following alarms is reported at the opposite site. If yes, clear the alarm immediately.
RADIO_MUTE
CONFIG_NOSUPPORT RADIO_TSL_LOW BD_STATUS
Cause 2: The opposite Tx power is over low. Check whether the opposite Tx power is normal. If not, replace the opposite ODU. Check whether the opposite NE is powered off.
Huawei Confidential
Page 15
Check whether the alarm is repeatedly reported among historical alarms. If the alarm is reported occasionally, contact the network planning department for improving anti-fading performance. Check whether the antennas at both ends are aligned. If not, realign the antennas. Check whether transmission is blocked by any mountains or buildings. If yes, contact the network planning department for avoiding the block. Check whether the polarization direction is set correctly for the antennas, ODUs,
Check whether the outdoor units such as antennas, combiners, ODUs, and flexible waveguides are wet, damp, or damaged. If yes, replace the faulty component. Check the antenna gain at the two ends and replace the antennas that do not provide required antenna gain.
Huawei Confidential
Page 16
Huawei Confidential
Page 17
Huawei Confidential
Page 18
Huawei Confidential
Page 19
Huawei Confidential
Page 20
Huawei Confidential
Page 21
Start
C - STM MLPPP
No
No
No
Compute the boards and physical links that services traverse. E 1 MLPPP No Any alarms on the boards? Types of NNI ports
Yes
No
MW
Huawei Confidential
Page 22
BTS 1 CES
RTN
STM-1
MPLS
MPLS
RTN
BSC
RTN
BTS 2
CES
RTN
Core network
10G/GE
STM-1
BTS 3
ETH RTN RTN
BSC
Possible Causes Possible Possible Causes Causes 1. Fiber cuts 2. Faulty optical modules 3. Excessive optical attenuation 1.Negotiation Excessive bit errors detected at the MAC layer. 2. two Lineends. signals 1. fails due are to different working modes at the 2.
degrade. 3. Fiber performance deteriorates. Optical ports are dirty. Electrical cables, fiber connections, or opposite4. units are faulty.
Huawei Confidential
Page 23
Huawei Confidential
Page 24
The ETH_LINK_DOWN is an alarm indicating that the connection on the network port is faulty.
Cause 1: Negotiation fails due to different working modes at the two ends. Cause 2: An inloop is performed on the port. Cause 3: The fiber is connected to an incorrect port.
Possible Causes
Handling Procedure Cause 1: Negotiation fails due to different working modes at the two ends. Verify that the working modes are the same at the two ends. Cause 2: An inloop is performed on the port.
Check for the LOOP_ALM alarm at the two ends and clear the alarm immediately if it is reported.
Cause 3: The fiber is connected to an incorrect port. Check whether the fiber on the alarmed port is connected to an incorrect port. If yes, connect the fiber to a correct port. Cause 4: A certain board is faulty. Check for hardware-related alarms (such as HARD_BAD) at the two ends and replace the board that reports any of these alarms.
Huawei Confidential
Page 25
The MAC_FCS_EXC is an alarm indicating that excessive bit errors are detected at the MAC layer.
Cause 1: The line signals deteriorate. Cause 2: The input optical power is abnormal. Cause 3: The fiber connector is dirty.
Possible Causes
Handling Procedure Cause 1: The line signals deteriorate. Check for the LOOP_ALM alarm on the NMS and clear the alarm immediately if it is reported. If the alarm persists then, check for DOS attacks and eradicate any sources that transmit a large amount of invalid data. If the alarm persists then, verify that the fiber and electrical cable are normal. Cause 2: The input optical power is abnormal. Check whether the alarmed port also reports IN_PWR_ABN. If yes, clear the IN_PWR_ABN alarm immediately. Cause 3: The fiber connector is dirty. Clean the fiber connector and the receive optical port.
Huawei Confidential
Page 26
STM-1
MPLS
MPLS
RTN
BSC
BTS 2
CES
Core network
STM-1
BTS 3
ETH RTN RTN
BSC
Possible Causes Possible PossibleCauses Causes 1. Failure in received signals 2. Malfunction of clock extraction modules 1. 1.Fiber Excessive cuts 2. attenuation Excessive of loss received on the signals line 3. Malfunction 2. Unframed of structure oppositeof transmit signalsunits from the opposite site 3.
Malfunction of local receive units
Huawei Confidential
Page 27
The R_LOS is an alarm indicating loss of signals on the receive side of the line.
Possible Causes
Cause 1 of lasers: The local optical port is not used but the local laser is open.
Cause 2 of lasers: The local laser is open but the opposite laser is closed, so there is no output of optical signals. Cause 1 of fibers: No pigtail is connected to the local optical port or the pigtail on the local optical port is connected incorrectly. Cause 2 of fibers: Fiber cuts occur. Cause 3 of fibers: Rx power is over low. Cause 1 of boards: The local receive board is faulty. Cause 2 of boards: The opposite transmit board is faulty.
Handling Procedure Cause 1 of lasers: The local optical port is not used but the local laser is open. Check the enabling status of the local laser on the NMS and close the laser if it is open. Cause 2 of lasers: The local laser is open but the opposite laser is closed, so there is no output of optical signals. Check the enabling status of the opposite laser on the NMS and open the laser if it is closed.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 28
Huawei Confidential
Page 29
The R_LOF is an alarm indicating loss of frames on the receive side of the line. Cause 1: Different types of optical modules are used at the two ends. Cause 2: The receive power of the ODU is abnormal. Cause 3: Fibers are misconnected. Cause 4: The signals transmitted from the opposite site do not have the frame structure.
Possible Causes
Handling Procedure Cause 1: Different types of optical modules are used at the two ends. Verify that optical modules of one type are used at the two ends. Cause 2: The receive power of the ODU is abnormal. Check whether the alarmed port also reports IN_PWR_ABN. If yes, clear the IN_PWR_ABN alarm immediately.
Huawei Confidential
Page 30
Huawei Confidential
Page 31
BTS 1 CES
RTN
STM-1
MPLS
MPLS
RTN
BSC
BTS 2
CES
Core network
STM-1
BTS 3
ETH RTN RTN
BSC
Possible Causes Possible Causes 1. E1/T1 services are not received. 2. Fibers on the DDF-side E1/T1 output ports are Some alarms are reported on the opposite site. disconnected or loosely connected. 3. Fibers on local E1/T1 output ports are disconnected or loosely connected. 4. A certain board is faulty. 5. The electrical cable is faulty.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 32
The T_ALOS is an alarm indicating loss of signals on E1 ports. Cause 1: The opposite site does not transmit any E1 services. Cause 2: E1 cables are disconnected or loosely connected. Cause 3: The opposite equipment is faulty. Cause 4: The electrical cable is faulty. Cause 5: The alarmed board is faulty.
Possible Causes
Handling Procedure Cause 1: The opposite site does not transmit any E1 services. Verify that the opposite site transmits E1 services properly. Cause 2: E1 cables are disconnected or loosely connected. Verify that E1 cables are correctly connected.
Huawei Confidential
Page 33
Huawei Confidential
Page 34
The UP_E1_AIS is an alarm indicating upstream E1 signals. This alarm is reported when the
upstream E1 signal is all 1s.
Possible Causes
Cause 1: The opposite site reports the T_ALOS alarm. Cause 2: An inloop is set for the E1 port.
Handling Procedure Cause 1: The opposite site reports the T_ALOS alarm. Check for the T_ALOS alarm on the opposite site and clear this alarm immediately if it is reported. Cause 2: An inloop is set for the E1 port.
Check whether the E1 port reports the LOOP_ALM alarm on the NMS. If yes, release the inloop on the
E1 port. Cause 3: Some boards are faulty. On the NMS, check whether the local NE and the opposite NE report any hardware-related alarms such as HARD_BAD. If yes, perform a cold reset for the boards that report hardware-related alarms. If the alarm persists then, replace the boards that may be faulty.
Huawei Confidential
Page 35
The DOWN_E1_AIS is an alarm indication for downstream 2 Mbit/s signals. This alarm is reported when the downstream E1 signal is all 1s.
Possible Causes
Cause 1: The alarmed board also reports the UP_E1_AIS or T_ALOS alarm.
Cause 2: Some boards are faulty.
Handling Procedure Cause 1: The alarmed board also reports the UP_E1_AIS or T_ALOS alarm. Check whether the alarmed board reports the UP_E1_AIS or T_ALOS alarm on the NMS. If yes, clear the UP_E1_AIS or T_ALOS alarm immediately. Cause 2: Some boards are faulty. On the NMS, check whether the alarmed board and local cross-connect board report any hardwarerelated alarms such as HARD_BAD. If yes, perform a cold reset for the boards that report hardware-related alarms. If the alarm persists, replace the boards that may be faulty.
Huawei Confidential
Page 36
The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal. Cause 1: The opposite transmit power is abnormal. Cause 2: The local receive power is higher than the upper threshold. Cause 3: The local receive power is lower than the lower threshold. Cause 4: The receive board is faulty.
Possible Causes
Handling Procedure Cause 1: The opposite transmit power is abnormal. On the NMS, check whether the opposite site reports the OUT_PWR_ABN alarm. If yes, clear this alarm immediately and check whether the IN_PWR_ABN is cleared. If the alarm persists, query the local receive power and handle the alarm according to other causes. Cause 2: The local receive power is higher than the upper threshold. Add proper optical attenuators to the receive optical port and adjust the input optical power to a normal value.
Huawei Confidential
Page 37
Cause 3: The local receive power is lower than the lower threshold.
Verify that the bending radius of the pigtail on the local site is no smaller than 6 cm. If the alarm persists, use proper optical attenuators and correctly connect the local optical module. If the alarm persists, replace the optical module and clean the fiber connectors at the two ends. Cause 4: The receive board is faulty. Check whether the processing board and cross-connect board on the local site report any hardware-related alarms such as HARD_BAD and TEMP_OVER. If yes, replace the boards that report hardware-related alarms.
Huawei Confidential
Page 38
is abnormal.
Possible Causes
Cause 1: The output optical power is over high or over low. Cause 2: The alarmed board is faulty.
Handling Procedure Cause 1: The output optical power is over high or over low. Replace the optical module of the alarmed port.
Huawei Confidential
Page 39
The LOOP_ALM is an alarm of loopbacks. Cause 1: The port is looped back. Cause 2: The service is looped back.
Possible Causes
On the NMS, check whether the alarmed port is looped back. If yes, release the loopback.
Cause 2: The service is looped back. On the NMS, check whether the service is looped back. If yes, release the loopback. For Ethernet services, enable the automatic shutdown function for looped-back ports.
Huawei Confidential
Page 40
The FLOW_OVER is an alarm indicating the traffic received by the port is higher than the threshold.
Possible Causes
Cause 1: The traffic received by the port is higher than the preset threshold of the port.
Handling Procedure Cause 1: The traffic received by the port is higher than the preset threshold of the port.
Check whether the actual received traffic indicated by the alarm parameter is higher than the port bandwidth. If yes, reduce the data transmitted by the opposite site. Configure the service on an unused port.
Huawei Confidential
Page 41
Contents
1 2 3 4 5 6 7 8 9 10
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes
11
Page 42
3
Handle RS errors on SDH optical interface boards.
Yes
No
Yes
No
Huawei Confidential
Page 43
1. 2. 3. 4. 5.
Huawei Confidential
Page 44
1.
2. 3. 4. 5.
The PDH service processing board or Ethernet service processing board is faulty. The cross-connect board is faulty. The PDH service processing board or Ethernet service processing board has over high working temperature. The working temperature on the cross-connect board is over high. Unstable power supply, incorrect grounding, or external interference exists.
Huawei Confidential
Page 45
Handling Method
Focus on: TEMP_ALARM SYN_BAD HARD_BAD MW_CFG_MISMATCH 1. Analyze and process clock alarms. 2. Ensure that the configuration is correct and fibers are correctly connected. 3. Locate the sites with clock asynchronization by changing clock configuration. 4. Replace the components with poor performance.
Huawei Confidential
Page 46
2.
3.
4.
5.
1. 2. 3.
Check for the MW_FEC_UNCOR and RPS_INDI alarms. If any of these alarms is reported, clear the alarm immediately. If none of these alarms is reported, replace the IF board.
Huawei Confidential
Page 47
2. 3.
4.
6.
1. 2. 3. 4.
Huawei Confidential
Page 1
Handling Method
1. Replace PDH service processing boards, Ethernet service processing boards, or cross-connect boards along the overlapped route of errored services. 2. If the alarm persists after board replacement, check for unstable power supply, improper grounding, and external interference.
Huawei Confidential
Page 2
Possible Causes
Cause 1: The number of E1 signals is different on both ends of a microwave link (including the number of E1 signals on the active page and the number of E1 signals on the standby page). Cause 2: The AM enabling is different on both ends of a microwave link. Cause 3: The IEEE 1588 overhead enabling is different on both ends of a microwave link. Cause 4: The modulation mode is different on both ends of a microwave link. Cause 5: The channel spacing is different on both ends of a microwave link.
Handling Procedure
Cause 1: The number of E1 signals is different on both ends of a microwave link. Cause 2: The AM enabling is different on both ends of a microwave link. Cause 3: The IEEE 1588 overhead enabling is different on both ends of a microwave link. Cause 4: The modulation mode is different on both ends of a microwave link. Cause 5: The channel spacing is different on both ends of a microwave link. the microwave link. Ensure that the configuration is the same on both ends of the microwave link.
Determine the possible cause of the alarm according to the alarm parameters. Then, check the configuration on both ends of
Huawei Confidential
Page 3
Contents
1 2 3 4 5 6 7 8 9 10 11
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes Locating Clock Faults Locating DCN Faults
Page 4
Yes
No
No
No
End
Huawei Confidential
Page 5
Alarm Reported
HARD_BAD, TEMP_OVER, or BUS_ERR
COMMUN_FAIL T_ALOS
UP_E1_AIS or DOWN_E1_AIS
Huawei Confidential
Page 6
Alarm Reported
HARD_BAD, TEMP_OVER, or BUS_ERR
Huawei Confidential
Page 7
Cause 4: On the NE, the priority of synchronization clock source is lost, or the synchronization
clock source is lost. Cause 5: On the PW carrying CES services, the number of lost packets, errored packets, or jitters within a time unit crosses the threshold.
Huawei Confidential
Page 8
Huawei Confidential
Page 9
Possible Causes
Cause 1: Clock synchronization cannot be performed. Cause 2: Link quality deteriorates, causing more jitters. Cause 3: The size of buffer area is set to a low value. Cause 4: There are too many hops of microwave link on the network side, which generates a large number of jitters.
Handling Procedure
Cause 1: Clock synchronization cannot be performed.
On the NMS, check whether the LTI or other clock alarms are reported. If yes, clear these alarms. Cause 2: Link quality deteriorates, causing more jitters. Check whether the alarmed port also reports IN_PWR_ABN or TEM_HA. If yes, clear the IN_PWR_ABN or TEM_HA alarm immediately. Cause 3: The size of buffer area is set to a low value. On the NMS, increase the size of buffer area if possible.
Cause 4: There are too many hops of microwave link on the network side, which generates a large number of jitters.
Reduce the number of hops on the network side.
Huawei Confidential
Page 10
Possible Causes
Cause 1: Clock synchronization cannot be performed. Cause 2: Parameter settings are different at the two ends of CES services. Cause 3: The tunnel or PW carrying CES services is congested. Cause 4: The link signal deteriorates or is interrupted due to a fault of cables, optical fibers, or optical modules.
Handling Procedure
Cause 1: Clock synchronization cannot be performed. On the NMS, check whether the LTI or other clock alarms are reported. If yes, clear these alarms. Cause 2: Parameter settings are different at the two ends of CES services. Modify the parameter settings to the same. Cause 3: The tunnel or PW carrying CES services is congested. On the NMS, check whether the bandwidth configured for the tunnel or PW is too low and whether the QoS parameters are set properly. If the bandwidth and QoS settings cannot meet the requirements of CES services, increase the bandwidth, replan the service trail, and change QoS settings. Cause 4: The link signal deteriorates or is interrupted due to a fault of cables, optical fibers, or optical modules. Verify that electrical cables and fibers are correctly connected to the ports. Clean the fiber connectors and optical modules. If the alarm persists, replace the cables, fibers, or optical modules that may be faulty.
Huawei Confidential
Page 11
Possible Causes
Cause 1: Parameters of CES services are set incorrectly. Cause 2: The tunnel or PW carrying CES services is congested. Cause 3: The link signal deteriorates or is interrupted due to a fault of cables, optical fibers, or optical modules.
Handling Procedure
Cause 1: Parameters of CES services are set incorrectly.
Modify the incorrect parameter settings on the NMS. Cause 2: The tunnel or PW carrying CES services is congested. On the NMS, check whether the bandwidth configured for the tunnel or PW is too low and whether the QoS parameters are set properly. If the bandwidth and QoS settings cannot meet the requirements of CES services, increase the bandwidth, replan the service trail, and change QoS settings.
Cause 3: The link signal deteriorates or is interrupted due to a fault of cables, optical fibers, or optical modules.
Verify that electrical cables and fibers are correctly connected to the ports. Clean the fiber connectors and optical modules. If the alarm persists, replace the cables, fibers, or optical modules that may be faulty.
Huawei Confidential
Page 12
Possible Causes
Cause 1: Clock synchronization cannot be performed. Cause 2: The tunnel or PW carrying CES services is congested. Cause 3: The link signal deteriorates or is interrupted due to a fault of cables, optical fibers, or optical modules.
Handling Procedure
Cause 1: Clock synchronization cannot be performed. On the NMS, check whether the LTI or other clock alarms are reported. If yes, clear these alarms. Cause 2: The tunnel or PW carrying CES services is congested.
On the NMS, check whether the bandwidth configured for the tunnel or PW is too low and whether the QoS parameters are
set properly. If the bandwidth and QoS settings cannot meet the requirements of CES services, increase the bandwidth, replan the service trail, and change QoS settings. Cause 3: The link signal deteriorates or is interrupted due to a fault of cables, optical fibers, or optical modules. Verify that electrical cables and fibers are correctly connected to the ports. Clean the fiber connectors and optical modules. If the alarm persists, replace the cables, fibers, or optical modules that may be faulty.
Huawei Confidential
Page 13
The CES_STRAYPKT_EXC is an alarm indicating errored packets of CES services. Possible Causes
Cause 1: Parameter settings are different at the two ends of CES services. Cause 2: Fibers or cables are connected incorrectly.
Handling Procedure
Cause 1: Parameter settings are different at the two ends of CES services. Modify the parameter settings to the same. Cause 2: Fibers or cables are connected incorrectly. Reconnect the fibers or cables correctly.
Huawei Confidential
Page 14
Yes
Yes
No
LOOP_AL M occurs?
Yes
Loopbacks on ports
Release loopbacks.
No Yes FLOW_OVER occurs? Service configuration faults Rectify service configuration faults.
No
End
Huawei Confidential
Page 15
Alarm Reported
HARD_BAD, TEMP_OVER, or BUS_ERR
COMMUN_FAIL ETH_LOS, ETH_LINK_DOWN, ETH_AUTO_LINK_DOWN, or LOOP_ALM LASER_SHUT or LSR_WILL_DIE Ethernet services have packet loss or errored packets. HARD_BAD, TEMP_OVER, or BUS_ERR
LSR_WILL_DIE FLOW_OVER
Huawei Confidential
Page 16
Cause 1: The board carrying ETH services cannot work properly due to hardware errors,
over-high temperature, or inter-board communication failure. Cause 2: The signal is lost in the receive direction. Cause 3: Negotiation between Ethernet ports fails due to incorrect connections on Ethernet ports. Cause 4: Loopbacks are performed for Ethernet ports. Cause 5: Traffic limit on Ethernet ports is set to a low value or parameter settings are different on source and sink ports.
Huawei Confidential
Page 17
Huawei Confidential
Page 18
Huawei Confidential
Page 19
MPLS tunnels cannot be created, and therefore services cannot be provisioned. MPLS tunnels are faulty, causing service interruption. Protection switching fails, causing service interruption, packet loss, or bit errors.
Common Causes
Huawei Confidential
Page 20
Huawei Confidential
Page 21
Possible Causes
Cause 1: The ingress node on the tunnel stops transmitting CV/FFD packets. Cause 2: The physical link carrying the tunnel is faulty. Cause 3: Some boards on the ingress node are being reset. Cause 4: The service interface is configured incorrectly. Cause 5: Severe congestion occurs on the network. Cause 6: The CPU is highly occupied and cannot process ARP protocol packets.
Handling Procedure
Cause 1: The ingress node on the tunnel stops transmitting CV/FFD packets. 1. Check whether the settings of detection mode and detection packet type are consistent on the two ends. If not, make
consistent settings.
2. Check the parameter of CV/FFD status on the ingress node. If the CV/FFD status is disabled, change it to enabled. Cause 2: The physical link carrying the tunnel is faulty. On the NMS, check whether the egress node reports the HARD_BAD, ETH_LOS, or ETH_LINK_DOWN alarm. If yes, clear this alarm.
Huawei Confidential
Page 22
Cause 6: The CPU is highly occupied and cannot process ARP protocol packets.
Check for the CPU_BUSY alarm on the NMS and clear this alarm immediately if it is reported.
Huawei Confidential
Page 23
Possible Causes
Cause: The upstream NE detects that the tunnel at the physical layer is faulty
Handling Procedure
Cause: The upstream NE detects that the tunnel at the physical layer is faulty On the physical link between the local NE and its upstream NE, check for the faults such as fiber cuts, failure in optical modules, and board failure. Rectify the fault if any.
Huawei Confidential
Page 24
2. PWs are faulty, causing service interruption, packet loss, or bit errors.
Common Causes Cause 1: The physical link carrying the PW is faulty. Cause 2: Cross-connections of PWs cannot be created. Cause 3: The tunnels carrying PWs are faulty.
Huawei Confidential
Page 25
Huawei Confidential
Page 26
The PW_DROPPKT_EXC is an alarm indicating that the number of lost packets on the PW crosses the threshold. Possible Causes
Cause: A small number of packets are lost on the PW.
Handling Procedure
Cause 1: A small number of packets are lost on the PW. Check whether any service ports on the PW are congested. If yes, replan the trail of
Huawei Confidential
Page 27
Contents
1 2 3 4 5 6 7 8 9 10
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes Locating Clock Faults Locating DCN Faults Locating Other Faults Handling Common Alarms Typical Cases of Fault Locating Reference Documents
Huawei Confidential
11
Page 28
1+1 protection switching cannot be triggered. After the working channel of a 1+1 protection group is restored, services cannot be The following hardware- and service-related alarms occur: POWER_FAIL, VOLT_LOS, RADIO_TSL_HIGH, RADIO_TSL_LOW, IF_INPWR_ABN, CONFIG_NOSUPPORT, R_LOC, R_LOF, MW_RDI
RADIO_RSL_HIGH,
The packet services transmitted on the Hybrid microwave link are unavailable. 1+1 protection switching is delayed.
Huawei Confidential
Page 29
alarms and the RDI alarm; the NE is being reset; the switching between active and standby
SCC boards is being performed. Cause 6: IF cables are connected incorrectly.
Huawei Confidential
Page 30
Huawei Confidential
Page 31
The RPS_INDI is a microwave protection switching alarm indication. Services are transmitted on the standby channel. Troubleshoot the working channel. Set the revertive mode of the 1+1 protection group to revertive.
Possible Causes
Handling Procedure
Huawei Confidential
Page 32
Possible Causes
Cause 1: SNCP switching fails because the NE software version mismatches the board
software version. Cause 2: The working and protection channels of an SNCP protection group fail. Cause 3: TU_AIS insertion upon E1_AIS is not provided (for OptiX RTN 600 V100R005 and OptiX RTN 900 V100R002C01 and later versions).
Huawei Confidential
Page 33
Huawei Confidential
Page 34
The PS is an alarm indicating protection switching. Services are transmitted on the standby channel.
Possible Causes
Handling Procedure 1. Troubleshoot the active channel. 2. Set the revertive mode of the SNCP protection group to revertive.
Huawei Confidential
Page 35
Yes
Yes
No
ETH_APS_LOST occurs?
Yes
Configurations are the same on two ends? Yes APS protocol is enabled on both ends? Yes
No
No
Yes
Troubleshoot clocks.
Yes
No
End
Huawei Confidential
Page 36
Huawei Confidential
Page 37
Cause 1: The settings of the APS protection group differ between the two ends. Cause 2: The APS protection group is deactivated. Cause 3: Fibers or cables are connected incorrectly. Cause 4: APS frames cannot be transmitted because hardware-related alarms occur
Cause 5: The system reports clock alarms. Cause 6: The working tunnel or protection tunnel is faulty.
Huawei Confidential
Page 38
Huawei Confidential
Page 39
BUS_ERR) occur on the board that carries the protection channel. If yes, clear these
alarms. Cause 5: The system reports clock alarms. Check whether the system reports clock alarms such as TR_LOC, SYNC_C_LOS, and
Huawei Confidential
Page 40
Huawei Confidential
Page 88
Possible Causes
Handling Procedure Cause 1: The settings of the APS protection group differ between the two ends.
On the NMS, check whether the settings of the APS protection group are the same at the two ends. If the settings differ
between the two ends, change them to the same. Then, deactivate and activate the APS protection group at the two ends. The ETH_APS_TYPE_MISMATCH is an alarm indicating a protection scheme mismatch.
Possible Causes
Handling Procedure Cause: The switching type, switching mode, or revertive mode of the protection group differs between the two ends. On the NMS, check whether the settings of the APS protection group are the same at the two ends. If the settings differ between the two ends, change them to the same. Then, deactivate and activate the APS protection group at the two ends.
Huawei Confidential
Page 89
Huawei Confidential
Page 90
The LAG is invalid, all the member ports cannot LAG_DOWN be used, and the services are interrupted.
The member ports in the LAG cannot be used, and the service has packet loss.
LAG_MEMBER_DOWN
Huawei Confidential
Page 91
Cause 1: The NEs at the two ends of the LAG are incorrectly configured. Cause 2: The working mode of the member ports in the LAG is set to halfduplex.
Huawei Confidential
Page 92
cleared.
Cause 2: The working mode of the member ports in the LAG is set to half-duplex. Check whether the working mode of each member port in the LAG is set to half-duplex. If the working mode is set to half-duplex, modify the working mode of each port to full-duplex. Cause 3: The loopback is configured on the member ports in the LAG. (1) Check whether the LOOP_ALM alarm exists on each member port in the LAG. If yes, release the loopback on each port to clear the LOOP_ALM alarm. (2) Check whether the ETH_EFM_LOOPBACK alarm exists on each member port in the LAG. If yes, release the remote loopback to clear the ETH_EFM_LOOPBACK alarm.
Cause 4: The connections of the member ports in the LAG are faulty or lost.
Check whether the ETH_LOS or ETH_LINK_DOWN alarm exists on each member port in the LAG. If yes, clear the ETH_LOS or ETH_LINK_DOWN alarm.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 93
Possible Causes
Cause 1: The opposite NE is not configured with any LAGs. Cause 2: All member ports in the LAG are unavailable.
Handling Procedure Cause 1: The opposite NE is not configured with any LAGs. On the NMS, check whether the opposite NE is configured with a LAG. If the opposite NE is not configured with a LAG, configure one on the opposite NE and check whether the alarm clears. Cause 2: All member ports in the LAG are unavailable. When a member port in the LAG is unavailable, the system generates an ETH_LOS,
The LAG_MEMBER_DOWN is an alarm indicating that a member port of a LAG is unavailable. Cause 1: The port link is unavailable. Cause 2: The port receives no LACP packet. Cause 3: The port works in half-duplex mode. Cause 4: The port is looped back.
Possible Causes
Handling Procedure Cause 1: The port link is unavailable. On the NMS, check whether the port in the LAG is enabled. If the port is not enabled, enable the port in the LAG and check whether the alarm clears. If the alarm persists, check whether an ETH_AUTO_LINK_DOWN alarm occurs on the
port that reports the LAG_MEMBER_DOWN alarm. If yes, clear the LAG_MEMBER_DOWN alarm.
Cause 2: The port receives no LACP packet. On the NMS, check whether the opposite port is added to the LAG. If the opposite port is not added to the LAG, add the opposite port to the LAG and check whether the alarm clears. If the alarm persists, check whether an ETH_LOS or FLOW_OVER alarm occurs on the port that reports the LAG_MEMBER_DOWN alarm. If yes, clear the LAG_MEMBER_DOWN alarm. Cause 3: The port works in half-duplex mode. Change the working mode of the port to auto-negotiation or full-duplex. Cause 4: The port is looped back. Release the loopback on the port.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 95
Contents
1 2 3 4 5 6 7 8 9 10 11
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes Locating Clock Faults Locating DCN Faults
The service has bit errors or is interrupted. The system control, cross-connect, and timing board reports an EXT_SYNC_LOS/LTI/S1_SYN_CHANGE/SYNC_C_LOS/SYNC_DISABLE alarm.
Possible Causes
Cause 1: The priority of the synchronous clock source on the service board is absent from the priority list. Cause 2: The synchronous clock source is lost and the clock of the NE works improperly. Cause 3: The clock source is switched in SSM mode and the clock source traced by the NE is also switched. Cause 4: The signals of the synchronous clock source are degraded.
Huawei Confidential
Page 98
Cause 1: The external clock source is configured in the clock source priority list, but
Handling Procedure
Cause 1: The external clock source is configured in the clock source priority list, but the external clock source cannot be detected or become invalid. Check whether the equipment that provides the external clock source is faulty, and check whether the cable that connects the external clock source is normal.
Huawei Confidential
Page 99
Cause 1: The clock configuration is incorrect. Cause 2: All the clock sources in the clock source priority list fail.
Handling Procedure
Cause 1: The clock configuration is incorrect. Query the clock synchronization status and check whether the data in the clock source priority list meets the network planning requirement. Cause 2: All the clock sources in the clock source priority list fail. Troubleshoot the synchronization sources based on the clock source priority list. If the synchronization source is an external clock, handle the EXT_SYNC_LOS alarm; if the synchronization source is a line clock, handle the alarm that occurs on the line board; if the synchronization source is an IF clock, handle the alarm that occurs on the IF board; if the synchronization source is a tributary clock, handle the alarm that occurs on the tributary board; if the synchronization source is an Ethernet clock, handle the alarm that occurs on the Ethernet board.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 100
Cause 1: The original clock source is lost when the SSM protocol or extended SSM
protocol is enabled.
Handling Procedure
Cause 1: The original clock source is lost when the SSM protocol or extended SSM protocol is enabled. Handle the SYNC_C_LOS alarm that is related to the original clock source.
Huawei Confidential
Page 101
Handling Procedure
Cause 1: The clock source is lost. Based on the clock source priority list, determine the synchronization source corresponding to the lost clock source.
Huawei Confidential
Page 102
Cause 1: The status of the automatic synchronization of SCC boards changes from
enabled to disabled.
Handling Procedure
Cause 1: The status of the automatic synchronization of SCC boards changes from enabled to disabled. Change the status of the automatic synchronization of SCC boards from disabled to enabled. Then, check whether the alarm clears. If the alarm persists, replace the board that reports the alarm.
Huawei Confidential
Page 103
Contents
1
2
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services
3
4
5 6 7
8 9 10 11
Huawei Confidential
Page 105
Cause 1: On a network, the NE IDs, NE IP addresses or subnet masks conflict. Cause 2: The inband DCN port of the faulty NE is not enabled, or parameter settings for the interconnected ports are inconsistent. Cause 3: The physical connection between the faulty NE and the NMS is interrupted. Cause 4: The received signals of the faulty NE are lost, or the received optical power is excessively low, and therefore the DCN packets cannot be extracted. Cause 5: A certain board is faulty. Cause 6: A DCN storm or DCN interruption occurs as the third-party network that the DCN packets traverse is faulty. Cause 7: The bandwidth configured for the inband DCN channel is excessively small. Cause 8: The SCC board on the faulty NE is being reset or switched, and therefore the inband DCN packets cannot be responded.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 106
Locating Inband DCN Faults - Handling Method Cause 1: On a network, the NE IDs, NE IP addresses or subnet masks conflict.
It is usually caused by the new NE on the network. According to the NE plan table, check whether the NE ID, NE IP address and subnet mask of the new NE are correctly configured. If any parameters are incorrect or conflict with the configuration of another NE, re-configure these parameters. Cause 2: The inband DCN port of the faulty NE is not enabled, or parameter settings for the interconnected ports are inconsistent. (1) Check whether the ports, which support the DCN function by default, are connected to fibers or cables. If the fibers or cables are not connected to the ports whose DCN function is enabled by default, change the present port to a port whose DCN function is enabled by default. (2) Check whether the ports at the two ends of the link are enabled. If not, enable the inband DCN for the ports. (3) Check whether the configurations of the ports at the two ends are consistent, such as the working mode of the Ethernet port. If inconsistent, modify the configurations to match each other. Cause 3: The physical connection between the faulty NE and the NMS is interrupted. Check whether the network cables or fibers of the faulty NE are disconnected from the ports. If the network cables or fibers are disconnected from the ports, insert the network cables or fibers again. Cause 4: The received signals of the faulty NE are lost, or the received optical power is excessively low, and therefore the DCN packets cannot be extracted. Check whether the R_LOS, ETH_LOS, or IN_PWR_ABN alarm exists on the board configured with the inband DCN channel. If the alarm exists, clear it. Cause 5: A certain board is faulty. Check whether the HARD_BAD or TEMP_OVER alarm exists on the board configured with the inband DCN channel. If the alarm exists, replace the board that reports the alarm.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 107
Contents
1 2 3 4 5 6 7 8 9 10 11
Process of Locating Common Faults Locating Link Faults
Possible Causes
Cause 1: A manual operation causes the reset. Cause 2: The power supply of the NE is abnormal. Cause 3: A certain board is faulty. Cause 4: Certain tasks have high CPU usage. Cause 5: Other reasons cause the reset.
Huawei Confidential
Page 110
Possible Causes
Cause 1: The NE is abnormal in the process of software loading. Cause 2: Backing up databases fails.
Huawei Confidential
Page 112
Cause 10: The NE is in the Undispensed state when an upgrade task is being created.
Cause 11: The NE is in the Unactivated state when an upgrade task is being created. Cause 12: The NE is in the Uncommitted state when an upgrade task is being created. Cause 13: No CF card is installed on the SCC board or the memory in the CF card is
insufficient.
Huawei Confidential
Page 113
Handling Procedure
Cause 1: The NE is abnormal in the process of software loading. Load software 10 minutes later because the NE is in an unstable state. Cause 2: Backing up databases fails. Upload the NE databases to the U2000 again; create another upgrade task and run the task. If the backing-up fails again, perform a warm reset on the NE. Cause 3: A rollback occurs due to a failure in package downloading. Check whether DCN communication is normal and whether bandwidth is sufficient. If no fault is found, check whether a correct software package is downloaded. If the downloaded software package is correct, check whether the remaining space on the flash memory is greater than the space required by the software package. If the remaining space on the flash memory is sufficient, change the gateway NE. Cause 4: A rollback occurs due to an error in the software activation process. Check whether any board is removed or whether the NE is manually reset during the upgrade. Then, activate the software again.
Huawei Confidential
Page 114
Handling Procedure
process. Select the task and click Ignore to commit the task. Then, check the version of each board. For boards whose version information is not updated, perform a cold reset on them. If a resetting command cannot be issued, perform a warm reset on the SCC board if the NE has only one SCC board, or perform active/standby switching between SCC boards if the NE has two SCC boards.
Cause 5: The upgrade task is not rolled back when an error occurs in the software activation
Cause 6: The SWDL_INPROCESS alarm persists after the upgrade is complete. Check whether the NE is in a normal state. If yes, perform a warm reset on the NE. Cause 7: User interfaces stop responding in the upgrade process. Restart the tool and create a new task that runs directly from the NE state, which is displayed when the task is originally created.
Huawei Confidential
Page 115
Handling Procedure
Remove the board, and then insert the board after the NE enters the normal state. If automatic matching still fails, check whether an SWDL_INPROCESS alarm occurs. If yes, clear the SWDL_INPROCESS alarm first.
Cause 9: The PCBs of the active and standby SCC boards are of different versions. Run the :mon-get-dump:bid,"SWDL.ISWDL.CSWDL","" command on the Navigator and check whether the returned values of m_byPCB for the active and standby SCC boards are the same. If the returned values of m_byPCB for the two SCC boards are different, replace any SCC board to ensure that the SCC boards use the same PCB. Cause 10: The NE is in the Undispensed state when an upgrade task is being created. Skip Load Package and create a task from the Dispense state; or enter the :swdl-dnldswmem command on the Navigator.
Huawei Confidential
Page 116
Handling Procedure
Skip Load Package and Dispense and create a task from the Active state; or enter
the :mon-init-sys:0,swdl command on the Navigator. (An activation operation will interrupt services. Therefore, check whether an activation operation is allowed.)
Cause 11: The NE is in the Unactivated state when an upgrade task is being created.
Cause 12: The NE is in the Uncommitted state when an upgrade task is being created.
Skip Load Package, Dispense, and Active, and create a task from the Commit state; or
enter the :swdl-commit-swmem command on the Navigator. Cause 13: No CF card is installed on the SCC board or the memory in the CF card is insufficient.
If no CF card is installed on the SCC board, install a CF card; if the memory in the CF card
is insufficient, delete unnecessary files in the CF card. Cause 14: Other reasons cause the failure. Collect data and send the data to Huawei engineers.
Huawei Confidential
Page 117
Common Alarms
Possible Causes
Cause 1: The CF card is faulty, resulting in an initialization failure. Cause 2: The SCC board is faulty, resulting in a failure to create a CF file.
Huawei Confidential
Page 118
Common Alarms
The CFCARD_OFFLINE is an alarm indicating that the CF card is offline. Possible Causes Cause 1: The CF card is not installed. Cause 2: The CF card is in poor contact with the SCC board. Cause 3: The SCC board is faulty. Handling Procedure Cause 1: The CF card is not installed. Check whether the CF card is installed on the SCC board. If not, install a CF card. Cause 2: The CF card is in poor contact with the SCC board. Check whether the CF card is loosened. If yes, re-install the CF card. Then, check whether the alarm is cleared. If the alarm persists, replace the CF card. Cause 3: The SCC board is faulty. Check whether the HARD_BAD alarm exists on the SCC board. If yes, perform a cold reset on the SCC board. Then, check whether the alarm is cleared. If the alarm persists, replace the SCC board.
Huawei Confidential
Page 119
Contents
1 2
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes
3
4
5
6
7
8 9 10 11
Reference Documents
Huawei Confidential Page 120
Huawei Confidential
Page 121
Cause 1 of the alarm reported by a board of the IDU: The board is installed in an incorrect slot. Cause 2 of the alarm reported by a board of the IDU: The board and the backplane are not connected properly. Cause 3 of the alarm reported by a board of the IDU: The slot is faulty. Cause 4 of the alarm reported by a board of the IDU: The alarmed board is faulty. Cause 5: The ODU is faulty; the power that the IF board supplies to the ODU is abnormal; the IF cable is damaged or is not properly connected.
Handling Procedure
Cause 1: The board is installed in an incorrect slot. Check whether the physical slot and logical slot of the alarmed board are the same. Cause 2: The board and the backplane are not connected properly. Re-install the alarmed board. Cause 3: The slot is faulty. Check whether the slot has broken or bent pins. If yes, insert the board in a vacant slot. Cause 4: The alarmed board is faulty. Replace the board. Cause 5: The ODU is faulty; the power that the IF board supplies to the ODU is abnormal; the IF cable is damaged or is not properly connected. Replace the ODU that reports the alarm; check the voltage at the RF port on the IF board; check whether the IF cable is wet or abnormal; re-connect the IF cable.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 122
The BUS_ERR is an alarm of bus errors. Cause 1: The board and the backplane are not connected properly. Cause 2: The alarmed board is faulty. Cause 3: The inter-board bus is faulty.
Possible Causes
Handling Procedure
Cause 1: The board and the backplane are not connected properly.
Re-install the alarmed board; check whether the backplane has broken or bent pins. If the backplane has broken or bent pins, insert the board in a vacant slot or replace the backplane. Cause 2: The alarmed board is faulty. Perform a cold reset on the alarmed board. If the alarm persists, perform a cold reset on the SCC board. If the alarm still persists, replace the alarmed board. Cause 3: The inter-board bus is faulty. On the NMS, check whether an alarm indicating loss/deterioration of a clock source is reported. If yes, clear clock alarms and then check whether the BUS_ERR alarm clears.
Huawei Confidential
Page 123
Possible Causes
Handling Procedure Cause 1: The alarmed board is reset. Perform a reset on the alarmed board. Then, the alarm disappears automatically. Cause 2: The board and the backplane are not connected properly. insert the board in a vacant slot or replace the backplane.
Re-install the alarmed board; check whether the backplane has broken or bent pins. If the backplane has broken or bent pins,
Huawei Confidential
Page 124
Possible Causes
Cause 1: The alarmed board and the backplane are not connected properly.
Cause 2: A fan is faulty.
Handling Procedure Cause 1: The alarmed board and the backplane are not connected properly. Re-install the alarmed board; check whether the backplane has broken or bent pins. If the backplane has broken or bent pins, insert the board in a vacant slot or replace the backplane. Cause 2: A fan is faulty. Remove the fan board and clean the fans. Then, install the fan board and check whether the alarm clears. If the alarm persists, replace the fan board.
Huawei Confidential
Page 125
Possible Causes
Handling Procedure
Cause 1: The external power supply fails. Check the external power supply. Cause 2: The alarmed board and the backplane are not connected properly. Re-install the alarmed board; check whether the backplane has broken or bent pins. If the backplane has broken or bent pins, insert the board in a vacant slot or replace the backplane. Cause 3: The alarmed board has hardware errors. Perform a cold reset on the alarmed board and check whether the alarm clears. If the alarm persists, replace the alarmed board.
Possible Causes
Handling Procedure Cause 1: The IF cable is loose or faulty. Check whether the connector of the IF cable is damaged/wet/corroded/loose or whether the connector is made properly. (The connectors to be checked include the connector between the IF pigtail and the IF board, the connector between the IF pigtail and the IF cable, and the connector between the IF cable and the ODU.)
The IF_INPWR_ABN is an alarm indicating that the power supplied by an IF board to an ODU is abnormal.
Possible Causes
Cause 1: The IF board is faulty. Cause 2: The IF cable is faulty. Cause 3: The ODU is faulty.
Handling Procedure
Cause 1: The IF board is faulty. Replace the alarmed IF board. Cause 2: The IF cable is faulty. Check whether the connector of the IF cable is damaged/wet/corroded/loose or whether the connector is made properly. (The connectors to be checked include the connector between the IF pigtail and the IF board, the connector between the IF pigtail and the IF cable, and the connector between the IF cable and the ODU.) Cause 3: The ODU is faulty. Perform a cold reset on the ODU and check whether the alarm clears. If the alarm persists, replace the ODU.
Huawei Confidential
Page 128
Possible Causes
Cause 1: The number of E1 signals is different on both ends of a microwave link (including the number of E1 signals on the active page and the number of E1 signals on the standby page). Cause 2: The AM enabling is different on both ends of a microwave link. Cause 3: The IEEE 1588 overhead enabling is different on both ends of a microwave link. Cause 4: The modulation mode is different on both ends of a microwave link. Cause 5: The channel spacing is different on both ends of a microwave link.
Handling Procedure
Cause 1: The number of E1 signals is different on both ends of a microwave link. Cause 2: The AM enabling is different on both ends of a microwave link. Cause 3: The IEEE 1588 overhead enabling is different on both ends of a microwave link. Cause 4: The modulation mode is different on both ends of a microwave link. Cause 5: The channel spacing is different on both ends of a microwave link. Determine the possible cause of the alarm according to the alarm parameters. Then, check the configuration on both ends of the microwave link. Ensure that the configuration is the same on both ends of the microwave link.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 129
Huawei Confidential
Page 130
Huawei Confidential
Page 131
Possible Causes
Cause 1: If the alarm is reported on the board on the IDU, the input power or the PIU is
abnormal. Cause 2: If the alarm is reported on the board on the IDU, the power module is abnormal. Cause 3: If the alarm is reported on the ODU, the power module of the ODU is faulty.
Handling Procedure Cause 1: If the alarm is reported on the board on the IDU, the input power or the PIU is abnormal. Check whether any alarms are reported on the PIU. If yes, clear the alarms immediately. Cause 2: If the alarm is reported on the board on the IDU, the power module is abnormal.
Huawei Confidential
Page 132
The POWER_ABNORMAL is an alarm indicating that the input power supply is abnormal.
Possible Causes
Handling Procedure Cause 1: The power cable is cut, damaged, or not connected. Check whether the power cable is cut, damaged, or not connected. If the power cable is cut or damaged, replace it with a proper power cable. If the power cable is not connected, connect it. Cause 2: The input power is abnormal.
Huawei Confidential
Page 133
The RADIO_TSL_HIGH is an alarm indicating that the microwave transmit power is too high.
Cause 1: The ODU is faulty.
Possible Causes
Handling Procedure Cause 1: The ODU is faulty. Perform a cold reset on the ODU and check whether the alarm clears. If the alarm persists, replace the ODU.
The RADIO_TSL_LOW is an alarm indicating that the microwave transmit power is too low. Cause 1: The ODU is faulty. Cause 2: The signals from the IF board to the ODU are abnormal.
Possible Causes
Handling Procedure Cause 1: The ODU is faulty. Perform a cold reset on the ODU and check whether the alarm clears. If the alarm persists, replace the ODU. Cause 2: The signals from the IF board to the ODU are abnormal. Perform a cold reset on the IF board and check whether the alarm clears. If the alarm persists, replace the
IF board.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 134
Huawei Confidential
Page 135
Contents
1 2 3 4 5 6 7 8 9 10 11
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes
Services on an IF Board Were Interrupted Because the IF Board Was Reset Due to Low Voltage
Fault Symptoms
On an NE that was not powered off or reset, an IF board reported BD_STATUS alarms but it was not reseated or reset.
The services that the IF board carried were automatically restored after an
interruption.
Cause Analysis
The software black box contained a record indicating a board reset due to low
voltage. It was found that a transient voltage dip occurred on the IF board.
Solutions
Check the power supply records of the NE.
Huawei Confidential
Page 137
Software Watchdogs of RTN NEs Were Frequently Reset Due to a Large Network Scale
Fault Symptoms
The software watchdogs of RTN NEs on a live network were frequently reset.
(1) Tasks SOCK, tNetTask, and tL2TSvR1b58 accounted for more than 60% of the CPU usage. As a result, task VIDL could not be carried out.
Cause Analysis
(2) Task SOCK is a communication task of the TCP/IP protocol stack; task
tNetTask is a communication task of the VXworks operating system; task tL2TSvR1b58 is an internal communication task of NEs. When these three tasks had high CPU usage simultaneously, the communication traffic was very heavy.
(3) Route query results showed that some NEs had 600 routes. Generally, it is recommended that an NE has a maximum of 64 routes (or 100 routes in particular cases).
Solutions
Divide the network into more subnets.
Huawei Confidential
Page 138
An NE Failed to Trace an External Clock Due to Inconsistent Settings for the NEs at the Two Ends Fault Symptoms
On a live network, an NE failed to trace an external clock and entered the free-run state, but its opposite NE properly output clock signals. The NMS displayed an LTI alarm but not an EXT_SYNC_LOS alarm. (1) Check the network topology; check whether the external clock was available; check the connection of the clock line; check which type of equipment output clock signals at the opposite end. (2) Check whether the clock output mode was set to a same value at the two ends. If the clock output mode was set to 2 Mbit/s, check whether the settings for the S1 byte and SSM protocol were consistent between the two ends. In addition, check whether the local external clock port was configured with DCC overheads. Due to inconsistent setting for the SSM protocol at the two ends, the local NE could not correctly obtain the S1 byte and as a result, reported an LTI alarm. The NE finally restored to normal after its SSM protocol was disabled.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 139
Cause Analysis
Solutions
An IF Board Reported an LPUAS Performance Event But Did Not Report a Lower Order Alarm Because LP_UNEQ Alarms Were Suppressed
Fault Symptoms
An IF board reported an LPUAS performance event but did not report a lower order alarm. The IF board and line board were configured with cross-connections but the services that the line board carried were not completely cut over. As a result, the value of the V5 byte carried in the lower order channel was 0 and accordingly the IF board reported an LPUAS event. It was found that the reporting status of LP_UNEQ alarms was set to DISABLE. Therefore, LP_UNEQ alarms could not be reported. In addition, LP_REI, LP_RDI, LP_TIM, LP_RFI, BIP_EXC, and BIP_SD alarms could not also be reported because they were suppressed by LP_UNEQ alarms. Set the reporting status of LP_UNEQ alarms to ENABLE.
Cause Analysis
Solutions
Huawei Confidential
Page 140
The network diagram is provided in the following figure. After NE2108 was powered off, the services between NE2108, NE2199, NE2299, and NE2120 were interrupted. The services, however, were not restored even after NE2108 restarted.
Note: NE2199 and NE2299 were at the same site; NE2108 and NE2120 were at different sites.
Huawei Confidential
Page 141
Normally, after NE2108 is powered off, the active and standby ODUs of NE2199
alarms.
It is suspected that the IF cables for the standby links of NE2199 and NE2299 were incorrectly connected. Based on the reported alarms, it is confirmed that IF board 7 of NE2199 was connected to ODU 17 of NE2299 and IF board 7 of
NE2299 was connected to ODU 17 of NE2199. For the connections, see the figure
provided in the next slide.
Huawei Confidential
Page 142
Huawei Confidential
Page 143
A computer has two network adapters, one connected to a public network and the other connected to an NE. The IP addresses of the two network adapters and that of the NE were in a same network segment. The subnet mask of the network adapter connected to the public network and that of the NE were set to 255.255.255.0, and that of the private network was set to 255.255.0.0. A user could not find the NE using the Web LCT but could find the NE using the Navigator. The user, however, could not log in to the NE or successfully ping the NE. (1) Ran the arp a command to query the IP addresses of the devices connected to the computer, and found that the public network and private network had same IP addresses. (2) Disconnected the network cable that connected one network adapter to the public network. Then, added the NE again. After the addition of the NE, the Web LCT properly communicated with the NE.
Cause Analysis
Solutions
Check IP addresses on a network and ensure that every IP address on the network is unique.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 144
A Newly Deployed BTS Encountered Service Interruptions Because IF Parameter Settings Were Not in Compliance with the Network Planning Document
Fault Symptoms
After being activated, a newly deployed BTS frequently encountered transient service interruptions. It took 20 ms or even 1,000 ms for a user to successfully ping a BSC from the BTS. It, however, always took less than 30 ms for a user to successfully ping the BSC from the microwave equipment that was connected to the BTS. (1) The pinging duration is normal if undersized packets are transmitted but is abnormal if oversized packets are transmitted. (2) Based on IF configurations, it is found that IF parameters were not set according to the network planning document. The bandwidth allocated to data services was very low. Modify the IF parameter settings according to the network planning document.
Cause Analysis
Solutions
Note: Bandwidth available to data services = Service bandwidth - E1-used bandwidth (for Hybrid microwave)
Huawei Confidential
Page 145
Fault Symptoms On a new OptiX RTN network, NE01, NE02, and NE03 formed a chain. A user could log in to NE03 from NE02 but could not log in to NE03 from NE01. Cause Analysis Possible cause 1: NE03 has a hardware fault, causing a DCN communication failure. Possible cause 2: The network configuration is incorrect. Handling Procedure (1) Queried NE03's adjacent routes and found that the NE IDs of NE01 and NE02 were displayed. (2) Performed a reset on NE03 and found that the fault persisted. (3) Checked NE03 on site, and found that one optical port of the EG2 board was connected to NE02 and another optical port of the EG2 board was connected to NE04. (4) Logged in to NE04 and found that the NE ID of NE04 was the same as that of NE01. (5) Changed the NE ID of NE04 to a unique value on the network. Then, logged in to NE03 from NE01. The login was successful.
Huawei Confidential
Page 146
A Service Created on a Static Tunnel Could Not Be Set Up Due to Incorrect Fiber Connections Fault Symptoms
The DCN communication between two NEs was normal but the service created on the static tunnel between the two NEs could not be set up. Cause Analysis Possible cause 1: The physical link is faulty. Possible cause 2: The IP addresses of the ports are incorrect. Possible cause 3: The ARP protocol works improperly. Handling Procedure (1) Checked the current alarms of the system and found that none of ETH_LOS, ETH_LINK_DOWN, and HARD_BAD alarms was reported. In addition, as the DCN communication was normal, link/port/board hardware malfunctions were ruled out. (2) Checked the IP addresses of the concerned ports and found that the IP addresses were correct and were in a same network segment. (3) Checked the entries of the ARP table and found that the IP address of the opposite port could not be learned. (4) The DCN communication could be normal only after the two interconnected ports successfully learned their opposite ports' MAC addresses. Based on query results, it is found that the MAC address of the port on the sink NE was not the planned one. (5) Checked the fiber connections and found that the fibers were incorrectly connected. Due to the incorrect fiber connection, the ARP protocol worked improperly and the service created on the static tunnel could not be set up. (6) Re-connected the fibers according to the NE planning table.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 147
BTS
NE04
Handling Procedure (1) Connected a BER tester to NE01 and set an inloop at one 2 Mbit/s port of NE04. The BER tester detected a large number of bit errors. (2) Configured a static ARP entry at NE03 with the MAC address being the egress port of NE03 and the IP address being NE04, and created a tunnel whose egress label was the same as its ingress label between NE03 and NE04. (3) Set an outloop at the network-side port of NE04. Then, on NE03, set an inloop at the network-side port that was connected to NE04. In both cases, the BER tester detected bit errors. (4) On NE03, set an outloop at the network-side port that was connected to NE02 and found that no bit error occurred. Therefore, it was inferred that NE03 malfunctioned. (5) On NE03, replaced the 10GE line board that was connected to NE02.
Huawei Confidential
Page 149
Fault Symptoms
All NodeBs connected to NE01 (an OptiX RTN 950 NE) reported an alarm indicating a large clock frequency deviation.
Handling Procedure
(1) Suspected that the clock configuration of NE01 was incorrect because NE01 did not report an alarm. (2) Queried the clock source priority lists of NE01 and NE02, and found that NE01 traced the line clock from optical port 1 on the EG2 board in slot 1 (of NE01) and NE02 traced the line clock from optical port 1 on the EG2 board in slot 2 (of NE02). The two optical ports were directly interconnected. As a result, the clock signals traced by NE01 and NE02 formed a loop, resulting in clock quality deterioration and large clock frequency deviations on the NodeBs connected to NE01. (3) Changed the clock source of NE01 according to the NE planning table.
Huawei Confidential
Page 151
Huawei Confidential
Page 152
Service Interruptions Due to Inconsistent Bandwidth Planning for TDM Services and Ethernet Services
Fault Symptoms
Two OptiX RTN 950 NEs of a version earlier than V100R002C02SPC100 were
interconnected. They carried TDM services and Ethernet services. The microwave link was correctly configured, but the Ethernet services could not be set up and no alarm related to microwave links was reported.
Handling Procedure
(1) Checked the configurations of the two interconnected NEs and found that the number of E1s was set to different values at the two ends. The data discrepancy caused inconsistent bandwidths at the two ends and resulted in service interruptions. (2) Changed the number of E1s at the two ends to the same value.
Notes
Hybrid microwave bandwidth is equal to the sum of the TDM service bandwidth and the Ethernet service bandwidth. For TDM services carried on a microwave link, the number of E1s must be the same at the two ends. Otherwise, the TDM services cannot be set up. Besides, if the set E1 bandwidth uses up all microwave bandwidth, Ethernet services will be interrupted due to absence of bandwidth.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 153
Contents
1
Process of Locating Common Faults Locating Link Faults Locating Faults of TDM Services Locating Faults of Packet Services Locating Faults of Protection Schemes Locating Clock Faults Locating DCN Faults
2
3 4 5 6 7 8 9 10 11
Reference Documents
http://support.huawei.com/support/pages/navigation/gotoKBNavi.do?actionFlag=intoKBNavigation&aut oFlag=autoThink&colID=ROOTENWEB|CO0000000173&itemId0=29-2&itemId1=3-400
Huawei Confidential
Page 155
For the preceding documents, please download the latest versions from support.huawei.com. For any comments or suggestions on the documents, please
Huawei Confidential
Page 156
Security Level:
www.huawei.com
Huawei Confidential