ZXMP M721: Maintenance Manual (Volume III) Troubleshooting

ZXMP M721
Multi-transmission Platform Compact WDM

Equipment
Maintenance Manual
(Volume III) Troubleshooting
Version:V1.00
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.2 2011–11–10 Version update
R1.1 2011–05–20 Version update
R1.0 2010–10–22 ZXMP M721 (V1.00) First version issued
Serial Number: SJ-20101022085432-008
Publishing Date: 2011–11–10(R1.2)

Table of Contents
Preface............................................................................................................. I
Chapter 1 Troubleshooting Flow............................................................... 1-1
1.1 General Troubleshooting Flow............................................................................. 1-1
1.2 Emergency Troubleshooting Flow........................................................................ 1-2
Chapter 2 Troubleshooting Principles...................................................... 2-1

2.1 Basic Troubleshooting Principles ......................................................................... 2-1
2.2 Basic Considerations for Fault Location ............................................................... 2-2
2.2.1 Fault Causes ........................................................................................... 2-2
2.2.2 Fault Location Principles........................................................................... 2-3
2.3 Common Methods of Fault Location .................................................................... 2-3
2.3.1 Observation and Analysis Method ............................................................. 2-3
2.3.2 Instrument Test Method ............................................................................ 2-4
2.3.3 Unplugging/Plugging Method .................................................................... 2-4
2.3.4 Replacement Method ............................................................................... 2-5
2.3.5 Configuration Data Analysis Method .......................................................... 2-5
2.3.6 Reconfiguration Method............................................................................ 2-5
2.3.7 Experience Method .................................................................................. 2-6
2.4 Basic Requirements for Maintenance Personnel................................................... 2-6
Chapter 3 Typical Troubleshooting........................................................... 3-1

3.1 Service Interruption Fault .................................................................................... 3-1
3.1.1 Symptom and Cause of Service Interruption Fault ...................................... 3-1
3.1.2 Service Interruption Fault Location Flow .................................................... 3-2
3.1.3 Analysis and Handling of Service Interruption Fault .................................... 3-2
3.2 Bit Error Fault..................................................................................................... 3-3
3.2.1 Symptom and Cause of Bit Error Fault....................................................... 3-3
3.2.2 Troubleshooting Flow of Bit Error Fault ...................................................... 3-4
3.2.3 Analysis and Handling of Bit Error Fault ..................................................... 3-5
3.3 Optical Power Fault ............................................................................................ 3-6
3.3.1 Symptom and Cause of Optical Power Fault .............................................. 3-6
3.3.2 Optical Power Fault Location Flow............................................................. 3-7
3.3.3 Analysis and Handling of Optical Power Fault ............................................ 3-7
3.4 Protection Switching Fault................................................................................. 3-10
3.4.1 Symptom and Cause of Protection Switching Fault................................... 3-10
I
3.4.2 Troubleshooting Flow of Protection Switching Fault ................................. 3-10
3.4.3 Analysis and Handling of Protection Switching Fault ..................................3-11
3.5 EMS Communication Fault ............................................................................... 3-12
3.5.1 Symptom and Cause of EMS Communication Fault.................................. 3-12
3.5.2 Troubleshooting Flow of EMS Communication Fault ................................. 3-13
3.5.3 Analysis and Handling of EMS Communication Fault ................................ 3-14
3.6 Orderwire Fault ................................................................................................ 3-14
3.6.1 Symptom and Cause of Orderwire Fault .................................................. 3-14
3.6.2 Troubleshooting Flow of Orderwire Fault.................................................. 3-15
3.6.3 Analysis and Handling of Orderwire Fault................................................. 3-16
List of Figure................................................................................................... I
List of Table................................................................................................... III
Glossary .........................................................................................................V
II
Preface
Applicable Product
This manual is applicable to Unitrans ZXMP M721 (V1.00) multi-transmission platform
compact WDM equipment (ZXMP M721 in short hereinafter).
What Is in This Manual

This manual is Unitrans ZXMP M721 (V1.00) Multi-transmission Platform Compact
WDM Equipment Maintenance Manual (Volume III) Troubleshooting. The following table
describes the chapters in this manual.
Chapter Description
Chapter 1 Troubleshooting Introduces the general troubleshooting flow and the emergency
Flow troubleshooting flow.
Chapter 2 Troubleshooting Introduces the basic principles and common methods of

Principles troubleshooting.
Chapter 3 Typical Describes the symptom, cause, troubleshooting flow and handling
Troubleshooting method of some typical faults.
I
II
Chapter 1
Troubleshooting Flow
Table of Contents
General Troubleshooting Flow....................................................................................1-1
Emergency Troubleshooting Flow ..............................................................................1-2
1.1 General Troubleshooting Flow

Figure 1-1 shows the general troubleshooting flow.
1-1
SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

ZXMP M721 Maintenance Manual (Volume III) Troubleshooting
Figure 1-1 General Troubleshooting Flow
1.2 Emergency Troubleshooting Flow

Flowchart
Figure 1-2 shows the emergency troubleshooting flow of DWDM optical transmission
systems.
1-2

Chapter 1 Troubleshooting Flow
Figure 1-2 Emergency Troubleshooting Flow of ZXWM/ZXMP Series DWDM Optical Transmission
System
Description of Emergency Troubleshooting Flow

1. Recover the service transmission as soon as possible
When some faults occur in the system, switch the service to the standby channel if
there is one, so as to recover the service transmission as soon as possible.
2. Loopback
1-3

Check whether there is any loopback (software loopback or hardware loopback)

configured on the service channel. If yes, cancel it immediately.
3. Handling of the alarms related to the main optical channel
In case of no optical power alarm, low optical power alarm or optical power overload
alarm, conduct the troubleshooting according to the optical power fault troubleshooting
procedure. In case of other alarms, such as absence of card alarm, abnormal pump
temperature, bias current threshold crossing or cooling current threshold crossing
alarm etc., conduct the troubleshooting by resetting, unplugging/plugging or replacing
the faulty board.
Table 1-1 lists main alarms of optical amplifier board, optical Mux/Demux board type
boards and introduces corresponding troubleshooting.
Table 1-1 Main Alarms and Corresponding Troubleshooting of M2SEOA/Optical Mux Board
Board Alarm Troubleshooting
No optical input power alarm
Low optical input power

These alarms are related to the received/transmitted
alarm
optical power. Focus on the optical power of the up-
No optical output power
stream optical line/site reporting the alarm and check
alarm
whether it is normal.
Low optical output power
alarm of M2SEOA board
Pump laser 1 temperature

threshold crossing alarm
Pump laser 2 temperature

M2SEOBA/ threshold crossing alarm
M2SEOPA Pump laser 1 bias current
These alarms are generally caused by the board itself.
Pump laser 2 bias current
Replace the faulty board directly.
Pump laser 1 cooling current

Pump laser 2 cooling current

Absence of card alarm
Presence of card alarm These alarms are generally caused by wrong config-
uration of the board in the EMS. Modify the configura-
Mismatch of card alarm
tion to remove the alarms.
1-4

SOGMD/SOAD board out-

put optical power out of up-
per limit alarm
SOGMD/SOAD board out-

put optical power out of
lower limit alarm
SOGMD/SOAD board input

optical power out of upper
limit alarm
SOGMD/SOAD board input

These alarms are related to the received/transmitted
optical power out of lower
optical power. Focus on the optical power of the
limit alarm
upstream optical line/site reporting the alarm and
check whether it is normal.
alarm of SOGMD/SOAD
board
SOGMD/
SOAD Low optical output power
alarm of SOGMD/SOAD
board
No optical input power alarm

of SOGMD/SOAD board

alarm of SOGMD/SOAD
board
OMU AWG temperature

These alarms are caused by the board itself, which
ODU AWG temperature does not affect services. Replace the faulty board
threshold crossing alarm when the time allows.
Absence of card alarm
Presence of card alarm These alarms are generally caused by wrong config-
uration of the board in the EMS. Modify the configura-
tion to remove the alarms.
During the handling of alarms, you can also get a preliminary judgement of the fault
cause by observing the status of indicators on the board reporting the alarm, and
conduct the troubleshooting correspondingly. Table 1-2 introduces the status of
indicators on a board, common cause and corresponding handling method.
1-5

Table 1-2 Indicator Status, Corresponding Common Cause and Handling
Indicator Status Common Cause Handling
The red and the green indicators

The power supply of the Check the power supply system or replace the
of all the boards in the equipment
equipment’s subracks fails. power supply distribution subrack directly.
dim out.
The board is damaged or

Both the red and the green Unplug the board and plug it in again; or replace
the board program fails to
indicators of a board dim out. the board directly.
run normally.
The red indicator of a board dims The board is damaged or

Unplug the board and plug it in again; or replace
out, while the green indicator the board program fails to
the board directly.
lights up. run normally.
The green indicator of a board The board is damaged or

Unplug the board and plug it in again; or replace
dims out, while the red indicator the board program fails to
the board directly.
lights up. run normally.
The board is damaged or

Both the red and the green Unplug the board and plug it in again; or replace
the board program fails to
indicators of a board light up. the board directly.
run normally.
The green indicator of a board Log in to the EMS and query the alarms of the
Alarm(s) occur in the
flashes slowly (once per second), board in it. Handle the alarms according to
board.
while the red indicator lights up. corresponding troubleshooting procedure.
The red and the green indicators The slot corresponding to

In the EMS, install and configure the board in the
flash alternately and slowly (once the board is not configured
slot.
per second). in the EMS.
The red and the green indicators The board is damaged or

Reload the board program to the board again
flash simultaneously and slowly the board program fails to
through the EMS, or replace the board directly.
(once per second). run normally.
• Flashing slowly (once per second) means that the indicator repeats lighting up for 0.5 second and then dimming out
for 0.5 second.
Caution!
l Make sure that the status of the ID DIP switch is consistent with that of the previous
board after the replacement.
l Be sure to reload the configuration data of the NE through the EMS after the
replacement.
l Be sure not to modify the important parameters of a board in the EMS, which may
directly affect the smooth transmission of services.
4. Handling of the alarms related to a single optical channel
1-6

In case of no optical power alarm, low optical power alarm or optical power overload
alarm, conduct the troubleshooting according to the optical power fault troubleshooting
procedure. In case of other alarms, such as absence of card alarm, loss of lock alarm,
high temperature, bias current threshold crossing or cooling current threshold crossing
alarm etc., conduct the troubleshooting by resetting, unplugging/plugging or replacing
the faulty board.
Table 1-3 lists main alarms of MQA/TD2C/TS2C/MJA type boards and introduces
corresponding troubleshooting.
Table 1-3 Main Alarms and Corresponding Troubleshooting of MQA/TD2C/TS2C/MJA Board
No optical input power

alarm

These alarms are related to the received/transmitted optical
alarm
power. Focus on the optical power of the upstream optical
High optical input power line/site reporting the alarm and check whether it is normal.
alarm The power-related alarms may also occur when the module
at the receive end of the board fails to detect optical signals
ES threshold crossing
or the upstream modulation module has problems
alarm
SES threshold crossing

alarm

alarm
Low optical output power

MQA/TD2C/TS2C/MJA alarm
These alarms are related to the transmit part of a board. Re-
High laser temperature
place the board immediately if the alarms affect the service
alarm
transmission.
Laser cooling current
Laser bias current thresh-

old crossing alarm
These alarms are caused by the board itself. Replace the

Loss of lock alarm
faulty board immediately if the alarms affect services. If the
alarms do not affect services, replace the faulty board when
J0 TIM alarm
the time allows.
Presence of board alarm These alarms are generally caused by wrong configuration
of the board in the EMS. Modify the configuration to remove
the alarms.
During the handling of alarms, you can also get a preliminary judgement of the fault
cause by observing the status of indicators on the board reporting the alarm, and
1-7

conduct the troubleshooting correspondingly. Refer to Table 1-3 for the status of
indicators on a board, common cause and corresponding handling method.
5. Optical power fault handling
Abnormal optical power may cause bit errors or shutdown of lasers in a system.
Either too high or too low optical power may result in a fault generally accompanying
with no optical power, low optical power or high optical power alarm etc. In case
of service interruption, regeneration section bit errors or mass of error correction
performance data, query the optical power performance of MQA/TD2C/TS2C/MJA,
optical amplification board and SOGMD/SOAD boards, or measure the optical
received and launched power by an optical power meter, so as to check whether the
optical power of each board is within the normal operating range. In this way, you
can find whether the abnormal optical power is caused by the power failure of the
opposite NE or extra attenuation on optical line.
Note:
You can also determine whether the current optical power is normal by comparing the
current value with the optical power data before the occurrence of the fault, such as
the history optical power performance data record in the EMS or periodically updated
data file.
If the fault is caused by the equipment, use the self-loop method to locate the faulty
point and then replace the faulty optical amplification board or MQA/TD2C/TS2C/MJA
board.
Be cautious to control the optical power at the receive end of the board and the use of
attenuators during the self-loop operation, so as to prevent the MQA/TD2C/TS2C/MJA
board from being damaged by too high optical input power.
6. Bit error fault handling
a. The occurrence of bit errors is related to abnormal optical power, abnormal

reflection in fibers, faults of optical amplification board/optical transparent board
and the non-linear effect of fibers. Troubleshoot bit error faults board by board
along the signal flow.
b. The existence of bit errors in a single optical channel indicate that these bit errors
are unrelated to the optical line through which the multiplexing optical signal
passes.
c. The existence of bit errors in all optical channels indicates that these bit errors are
related to the optical line through which the multiplexing optical signal passes, but
unrelated to a signal optical channel
d. Adopt replacement to locate fault when some optical channels are abnormal with
bit errors.
1-8

e. Some wavelengths may be abnormal when the optical power and the OSNR is
just at the critical point of the system.
Note:
The optical transparent type boards of Unitrans ZXWM/ZXMP series DWDM
equipment provides the RS_BBE(B1), detection function. An optical transparent
board detects RS_BBE(B1) byte in the signal with the wavelength to be converted,
and embodies it by the performance BBE/ES/SES of optical transparent type board.
1-9

This page intentionally left blank.
1-10

Chapter 2
Troubleshooting Principles
Table of Contents
Basic Troubleshooting Principles ................................................................................2-1
Basic Considerations for Fault Location......................................................................2-2
Common Methods of Fault Location ...........................................................................2-3
Basic Requirements for Maintenance Personnel ........................................................2-6
2.1 Basic Troubleshooting Principles

Maintenance personnel shall follow the basic principles of “observe first, then query, think,
and take action finally” during the troubleshooting.
Observing
First observe the fault symptom carefully, including the faulty point, alarm reason, severity
level and damage level, after arriving at the site. Only by fully considering the reasons of
a fault, can maintenance personnel get the essence of the problem.
Querying
After the observation, ask the on-site operator to find whether there is any direct cause of
the fault, such as data modification, file deletion, circuit board replacement, power supply
fault or lightening.
Thinking
According to the observation and query result, analyze the fault and locate the fault by
making use of the knowledge of the product.
Taking Action
After locating the faulty point, remove the fault by performing proper procedures, e.g., by
modifying the configuration data or by replacing a faulty board.
2-1

2.2 Basic Considerations for Fault Location

2.2.1 Fault Causes
Engineering Problems
Project engineering problem refers to substandard or inferior construction of project, which
may results in equipment fault. Such problems can be revealed during the construction
of project and there are some problems that cannot be revealed until the equipment has
operated for a certain time. These are latent risks for the equipment.
The product engineering specifications are usually summed up according to features
of the product itself and some practical experiences. Therefore, in order to prevent
such problems, you should strictly observe the engineering specifications to perform
construction and installation. You should carry out the single-site or entire- network
debugging and test.
External Causes
External causes refer to the environment and equipment factors instead of the equipment
itself, which results in equipment fault:
1. Power failure, such as equipment power failure and too low supply voltage.
2. Fiber fault, such as fiber performance deterioration, high loss, broken fiber, ill contact
of fiber connector.
3. Cable fault, such as trunk cable dropped or broken, and ill contact of cable connector.
4. The equipment is improperly grounded.
5. The equipment is placed in unsuitable environment.
Improper Operations
Improper operations refer to inappropriate operations performed by maintenance staff due
to lack of in-depth understanding of equipment, which results in equipment fault.
Improper operation is the most common phenomena while carrying out equipment
maintenance, especially in network reconstruction, upgrading, and expansion, where the
old and new devices are mixed or old and new versions are mixed. The maintenance
staff is usually unaware of the difference between old and new devices or between the
old and new versions and tends to trigger off a fault.
Equipment Interconnection Problems

A ZXMP M721 system is capable of accessing various optical signals, which are
transparently transmitted over the ZXMP M721 system. The interconnection failure may
be caused by the characteristics of optical devices.
The following lists the probable causes of equipment interconnection problems:
1. Improper fiber connection. The common cause during the maintenance is incorrect
connection of the optical interfaces.
2-2

Chapter 2 Troubleshooting Principles
2. The problems related to client equipment itself.

3. Performance deterioration of the service boards and mux/demux boards.
Equipment Problems
Equipment problems refer to the faults caused by the transmission equipment itself,
including equipment damage and inferior cooperation of PCBs. After running for a long
time, the PCBs are damaged due to aging factor, which ultimately result in damaged
equipment. The characteristics of equipment problems are: the equipment has been in
use for a long time and has been running normally before the fault occurs; and the fault
only occurs at certain points/PCBs, or the fault occurs because of external causes.
2.2.2 Fault Location Principles

Since a transmission system covers certain numbers of sites, which are located far away
from each other, it becomes critical to locate a fault to a specific site accurately. After
finding the faulty site, maintenance personnel can concentrate on eliminating the fault at
the site.
During the fault location, follow the general principles introduced below:
l Check for external causes first, such as broken fiber and power supply failure etc.
After that, consider the problems in the transmission equipment itself.
l Try to find out the faulty site as possible, and then locate the fault to a board.
l Analyze higher-level alarms first, and then lower-level alarms during the analysis of
alarms.
2.3 Common Methods of Fault Location

2.3.1 Observation and Analysis Method
When a system gets faulty, related alarms appear in the faulty equipment. At the same
time, the performances and alarms related to the fault are reported to the EMS, which
records and shows them in a graphical user interface. Observing the status of alarm
indicator lights on the equipment helps to locate the fault timely. In addition, by analyzing
the performance and alarm information on the basis of the generating principle of WDM
alarms, maintenance personnel can find the fault type and fault location primarily.
Caution!
Make sure to set the current running time of NEs synchronous to the EMS time previously
for the purpose of collecting correct alarm and performance information through the EMS.
Deviation of the time setting will result in incorrect or delayed collection of alarm and
performance information of NEs in the system.
2-3

2.3.2 Instrument Test Method

The instrument test method is generally used to handle external problems of transmission
equipment. If it is difficult to locate bit errors and find whether they are generated by SDH
equipment or WDM system, perform the remote self-loop with a fiber pigtail and then use
instruments to test the local equipment.
The following sequence of using instruments is recommended to reduce the negative
influence on services during fault location.
1. SDH analyzer
Loop the remote end of the SDH equipment and connect an SDH analyzer to its local
end to judge whether the bit error comes from the SDH or the WDM equipment.
2. Optical power meter
Use an optical power meter to accurately measure the optical power of the probable
fault points.
3. Optical spectrum analyzer
Test the optical interface of the probable faulty board with an optical spectrum analyzer,
read the optical power and OSNR from the analyzer. Then compare the data with the
original data to find whether there is considerable performance deterioration.
If all services of the main optical channel are affected, focus on the spectrum of OM/OD
and OAD type boards. If only one channel of service of the main channel is affected,
focus on the spectrum of the OTU, OM/OD and OAD type boards.
Caution!
A passive board of the ZXMP M721 has an external monitoring optical interface, which
should be used for the test to avoid influence on the transmission services of the main
optical channel.
2.3.3 Unplugging/Plugging Method

The unplugging/plugging method is used after a fault is located to a specific board. Unplug
the faulty board and its external interface connectors. Then plug them back to check
whether the fault is caused by ill contact or board fault.
Caution!
Be sure to observe the operation specifications while plugging/ unplugging the board so
as to avoid damaging the board or causing other problems caused by improper handling.
2-4

2.3.4 Replacement Method

The replacement method is used to troubleshoot a fault by replacing suspected faulty piece
of equipment with a new one, such as a segment of cable, a board or an equipment. It is
usually applied in the following circumstances:
l Check for the problem of an external transmission device, which may be a fiber,
access equipment, and a power supply device.
l Locate the faulty board in a specific site.
l Handle the problems related to power supply or grounding
The replacement method is simple for maintenance personnel and more practical than
other methods However, it demands the availability of spare parts and accessories.
2.3.5 Configuration Data Analysis Method

In some cases, the configuration data of an equipment may be damaged because of the
configuration change or improper maintenance operation, which will result in faults. The
configuration data analysis method is used to find the fault cause by querying the current
configuration data and user operation log of the equipment after locating the faulty NE
(equipment).
By the configuration data analysis method, maintenance personnel can find and analyze
probable causes of a fault after locating the fault to the exact NE (equipment). However,
this method takes relatively longer time and requires more professional skills. It is suitable
for experienced maintenance personnel who are well familiar with the equipment.
2.3.6 Reconfiguration Method

The reconfiguration method is used to locate a fault by modifying the configuration of an
equipment. When a fault is located to a specific site, maintenance personnel can check
whether there is any configuration error by modifying the configuration of timeslot, board
slots and boards.
Caution!
Before modifying the equipment configuration, keep a backup of the original configuration
and record the reconfiguration operations in detail for the convenience of fault analysis
and data recovery.
During the upgrading, capacity expansion or reconstruction of a system, deliver the

previous configuration data for checkup if you suspect that there are errors in new
configuration data.
The reconfiguration method is complicated and suitable for skilled maintenance personnel.
This method is not recommended in routine maintenance. It is only used in the following
circumstances:
2-5

l There is no enough time to solve the problem completely.

l It is required to recover the services in a system temporarily.
l A pointer justification problem occurs.
2.3.7 Experience Method

At some special occasions (such as transient power supply failure, low voltage or external
severe electro-magnetic interference), a board in an equipment gets into abnormal
working status (service interruption or ECC communication interruption), but it does
not generate corresponding alarms with completely normal configuration data. An
experienced maintenance personnel can troubleshoot the fault effectively by resetting the
board, restarting the equipment, and then delivering the configuration data again. In such
case, the experience method is used.
Generally, it is unable to find the real cause of a fault by using the experience method.
Therefore, it is not recommended to use it unless the fault is emergent.
When a maintenance personnel encounters a fault difficult to be located, he/she shall
request for technical support from the nearest service office, try to troubleshoot the fault
and eliminate the latent risks with the help of ZTE's technical support engineers.
2.4 Basic Requirements for Maintenance Personnel

1. Maintenance personnel shall perform routine maintenance carefully to ensure that all
equipment in the equipment room run in a normal working environment.
2. Maintenance personnel shall be familiar with the conditions of the area in charge,
understanding the running status of equipment, completing and maintaining the
engineering documents.
3. Handle the faults following the troubleshooting process specified in this manual strictly.
4. Maintenance personnel shall be calm and composed in troubleshooting, to prevent
further problems.
5. While handling a fault, pay attention to the following items:
a. Before handling the fault, the maintenance person should inform the network
management center to collect, save, and back up onsite data. Because it
is unavoidable that some data of the current alarm and performance will
be influenced during the troubleshooting, the data of the current alarm and
performance details should be saved for searching the causes of the fault.
b. The maintenance person is not allowed to reset the network element control board
of equipment when a fault occurs. He/she should contact with the EMS center in
time to check and confirm the alarm information, and then handle the fault with the
guidance of the EMS center.
c. Record the detail of each operation step during the fault handling process, which
is very helpful for the handling of similar faults in the future as the reference.
6. Maintenance personnel are required to be skilled in the basic operations of
transmission equipment and the use of test instruments and meters.
2-6

7. Maintenance personnel shall also know the emergency telephone number and the
relevant person in charge of ZTE CORPORATION for help when necessary.
2-7

2-8

Chapter 3
Typical Troubleshooting
Table of Contents
Service Interruption Fault ...........................................................................................3-1
Bit Error Fault .............................................................................................................3-3
Optical Power Fault ....................................................................................................3-6
Protection Switching Fault ........................................................................................3-10
EMS Communication Fault .......................................................................................3-12
Orderwire Fault ........................................................................................................3-14
3.1 Service Interruption Fault

3.1.1 Symptom and Cause of Service Interruption Fault
Fault Symptom
l Total service interruption accompanying with alarms or performances reported in the
EMS
l Total service interruption without any alarm or performance reported in the EMS
l Main optical path or optical supervisory channel failure
l Multiple wavelength or single wavelength service interruption
Fault Cause
l External cause
à Power supply failure
à Optical fiber/cable fault
à Improper grounding
l Improper operation
à Wrong configuration of NEs and EMS
à Loopback of a single wavelength due to misoperation
à Modification or deletion of configuration data due to misoperation
à Manual insertion of alarms
l Equipment interconnection problem
Board failure or performance degradation
l Equipment cause
3-1

Board fault or gradual damage
3.1.2 Service Interruption Fault Location Flow

The fault location flow of service interruption fault is shown in Figure 3-1.
Figure 3-1 Service Interruption Fault Location Flow
3.1.3 Analysis and Handling of Service Interruption Fault

Checking for External Cause
l Check the power supply of the equipment. When the power supply of an NE fails,
the corresponding NE icon in the EMS turns gray and the EMS can not manage the
NE any longer. At the same time, the boards, having connection with the NE, in the
upstream and downstream NEs report no optical power alarms. The services on the
multiple wavelength channel and the main optical path are interrupted.
3-2

Chapter 3 Typical Troubleshooting
l Check all fiber connections to make sure that all optical connections are correct and
the transmit/receive interfaces of optical boards are in good condition. Then check
the optical power of the NE. If there is no light detected, or the difference between
the measured optical power and the normal optical power is very great, it can be
concluded that the optical line has problems. Adjust the related optical interfaces and
observe whether the alarms disappear.
l Check service cables for pseudo soldering, solder skip and loose contact. Use an
OTDR to locate the faulty point and handle the fault correspondingly, such as fiber
splicing. Then observe whether the alarms disappear.
l Check the grounding of the equipment. If the DDF/ODF is not grounded, or the
transmission equipment and the exchange equipment do not share the common
ground, the great grounding voltage difference can also result in service interruption.
In this case, no alarm and performance can be queried in the EMS.
Checking Configuration Data of NE

l Check whether the single wavelength channel is configured with a software or
hardware loopback, which interrupts all the services carried by the wavelength. If
yes, cancel the loopback.
l Check whether the NE configuration data is correct.
l Check whether there is a manually-inserted alarm, which result in the service
interruption. If yes, remove the alarm in the EMS.
3.2 Bit Error Fault

3.2.1 Symptom and Cause of Bit Error Fault
Fault Symptom
l The optical output power of ODU board varies severely during a short term.
l Bit error performances and bit error threshold crossing alarms are reported on the
EMS.
Fault Cause
l External cause
à Dirty fiber connectors

à Deteriorated fiber performance, which results in too high power loss
à Poor grounding of equipment

à Strong interference source near the equipment
à Poor heat dissipation in the equipment, which results in too high working
temperature
à Unstable voltage of power supply, which results in surge
3-3

à Too many accumulated dusts in the equipment after long-term work

à Improper clock configuration of client-side equipment, such as looped clock
à Fiber connectors are loose.
à Deteriorated transmission performance of optical transponder boards or
convergence boards.
l Equipment problem
à Some optical transponder board(s) or convergence board(s) is (are) faulty or
damaged.
à Other boards are faulty.
3.2.2 Troubleshooting Flow of Bit Error Fault

The troubleshooting flow of bit error fault is shown in Figure 3-2.
3-4

Figure 3-2 Troubleshooting Flow of Bit Error Fault
3.2.3 Analysis and Handling of Bit Error Fault

Bit errors are generally caused by high reflection of light in a system, which may be caused
by too small coiling radius of optical cables (less than the minimum allowed bend radius)
or dirty optical cables. The influence of bit errors depends on their quantity. Consecutive
big bit errors may result in service interruption; while transient small bit errors only damage
services instead of interrupting them. To handle bit error faults, the observation & analysis
method, instrument test method and the replacement method can be used.
Check for External Cause

l Check whether the optical input/output power of optical lines is within the specified
range. Too low/high optical power may make optical receiving modules unable to
normally receive optical signals, which also gives rise to bit errors at the same time.
3-5

In case of abnormal optical input power, adjust the optical attenuators or clean fiber
connectors related to the optical power.
l Check the grounding of equipment in the equipment room, especially whether the
DDFs/ODFs have been properly grounded, or whether the transmission equipment
and the switching equipment share the same common ground.
l Check the clock configuration of the equipment and make sure that the clock is not
looped.
l Check whether the equipment temperature is within the normal range. Dirty
equipment room, blocked air filters or faulty fans may result in too high/low equipment
temperature.
l Check whether any electromagnetic interference source, such as thunder and
lightning, high voltage transmission line, power supply and other electric facilities,
exists near the equipment.
Check the Interconnection of Equipment

Check the connection of related fiber pigtails according to the labels on them. The
equipment may only report large amounts of abnormal performance values but not give a
loss of signal alarm when some fiber pigtail is wrongly connected.
Check Equipment Hardware

Check the bit errors reported by the equipment.
l If the bit errors come from both optical transponder boards and convergence boards, it
can be concluded that the upstream line of the equipment, optical amplification boards
or optical Mux/DeMux boards have problems.
l If the bit errors come from only one optical transponder board, it can be concluded
that the transmission performance of the previous-stage optical transponder board or
convergence board is degraded. Locate the faulty board (at transmit end or receive
end) through loopback tests and then replace the faulty board.
3.3 Optical Power Fault

3.3.1 Symptom and Cause of Optical Power Fault
Fault Symptom
l The flatness of the main optical signal's operating wavelength is not good.
l The optical power and OSNR of different channels varies greatly.
l The gain or optical output power of OA type boards is incorrect.
l Alarms or performances related to optical power are reported in the EMS.
Fault Cause
l External cause
3-6

à The transmission performance of fiber pigtails is degraded due to the affect of

external factors.
à The loss on the optical line increases.
The data related to optical power in the EMS is modified.
l Equipment cause
à The optical transmitting modules in the equipment fails to output light normally.
à The performance of optical devices in the ZXMP M721 system deteriorates.
3.3.2 Optical Power Fault Location Flow

The fault location flow of optical power fault is shown in Figure 3-3.
Figure 3-3 Optical Power Fault Location Flow
3.3.3 Analysis and Handling of Optical Power Fault

ZXMP M721 contains large amount of optical devices. Abnormal optical power of these
devices may result in bit errors and even service interruption.
It is recommended to use the observation and analysis method, instrument test method
and the replacement method to handle optical power faults. Before the fault handling,
record the optical power of related points in each site, compare it with the original data to
3-7

find the point where the optical power differs greatly from the original one. Then use an
optical power meter to measure the optical power at the point. Note that the measurement
of optical power may affect other services in the site.

l Check whether the fiber pigtail at the fault point is damaged. If yes, replace it with a
new one.
l If the fault point is located at an optical channel of an OM type board, check the
insertion loss of the channel. If the insertion loss is too high, clean corresponding
optical input interface of the channel with absolute alcohol.
Check NE Configuration Data

l Check the optical output power and central frequency of OTU type boards.
If the deviation of an OTU board's optical output power and corresponding central
frequency is found, which may be caused by the adjustment of optical power and
wavelength on the OTU board in the EMS, query the configuration of the OTU boards'
power and wavelength in the EMS and set their offsets to zero.
l Check the gain flatness of OA type boards.
First use an instrument to test the OA type boards stage by stage, so as to find the
OA board whose gain flatness is poor. Then query its gain configuration in the EMS.
If it is found that the gain of this board has been adjusted, clear the adjustment value
(return to zero). If the abnormal optical power still exists after the operation, replace
the board.
l Check whether the APC function of M2SEOA type boards is enabled in the EMS.
If the APC function of an M2SEOA board is enabled, the input of its next-stage
M2SEOA board will be disconnected and its previous-stage M2SEOA board will
perform its APR (or APSD) function when the optical path fails. At this time, the gain
of the M2SEOA board is wrong. After the optical path recovers, the M2SEOA board
shall restore its normal gain automatically. If the gain can not restore automatically,
try to restore it manually in the EMS.
l Check whether the gain of the M2SEOA board has been adjusted in the EMS.
Access the power adjustment dialog box in the EMS and check the gain of the
M2SEOA board. If the gain has been changed, reset the adjustment value to zero.
Then check when the gain slope has been adjusted.

l Observe the indicator status of the boards at the fault point, and query the alarm and
performance messages in the EMS at the same time, so as to locate the fault.
à If all the indicators of a board are blacked out, while the indicators of the other
boards work normally, it can be concluded that the board with all indicators dim
out is faulty. Replace the board immediately.
3-8

Note:
If no spare board is available on site, just reset the faulty board to try to remove
the fault temporarily. Generally, the board can restore the service after the reset.
However, once a spare board is available, the faulty board shall be replaced
immediately.
à If the red and green indicators of a board are flashing alternately, it can
be concluded that the board is waiting for configuration. Inform the EMS
maintenance personnel to download the configuration data again.
In the ZXMP M721 system, the board status of waiting for configuration indicates
that the board has not been configured in the EMS, which does not affect the
service transmission. In this case, add the board in the EMS and issue the
configuration data to the board. After that, the green indicator of the board flashes
normally.
à If the red indicator of a board glows constantly, it can be concluded that the board
may detect an alarm. Check the alarm type in the EMS and handling the alarm.
l Measure the optical input power of OA type boards.
If the optical input power of an M2SEOA board is greater than the allowed maximum
optical input power, the M2SEOA board will output saturated optical power with the
gain different from the nominal one. In this case, add a proper attenuator before the
optical input interface so as to adjust the optical input power to a value less than the
maximum one.
Caution!
Be sure not to use an optical power meter with the maximum measurement value less
than 20 dBm in the test. Or else, the calculated gain of the M2SEOA board would be
wrong and the optical power meter may be damaged.
l After all the above operations, carry out the following measures if the M2SEOA board
does not recover its normal working yet.
Danger!
Be cautious to perform the following operations because the operation of unplugging
the M2SEOA board or fiber pigtails connected to it will result in service interruption.
3-9

à Unplug the fiber pigtails connected to the optical interfaces of the OA board.
Clean these optical interfaces and then plug the fiber pigtails back. After that,
check whether the optical power recovers normal.
à Check whether the optic fiber adapters or the 1550/1510
multiplexer/demultiplexer on the OA board are normal. If no, replace the board.
3.4 Protection Switching Fault

3.4.1 Symptom and Cause of Protection Switching Fault
Fault Symptom
l The system can not normally perform the protection switching when some faults occur
or it receives a protection switching command from the EMS.
l The system performs the protection switching successfully when the optical line of a
span is faulty. However, the system can not restore the normal working state after the
WTR time when the fault is removed.
l A new fault occurs on another span when the system is recovering from the protection
switching, which makes the system unable to recover successfully.
Fault Cause
l External cause
à Power supply failure
à Optical fiber faults, such as fiber performance degradation and too high loss etc.
protection switching function is wrongly configured.
Optical fibers are wrongly connected.
l Equipment problem
à Some board(s) is (are) faulty.

à The optical supervisory channel is blocked. 28 Confidential
3.4.2 Troubleshooting Flow of Protection Switching Fault

The troubleshooting flow of protection switching fault is shown in Figure 3-4.
3-10

Figure 3-4 Troubleshooting Flow of Protection Switching Fault
3.4.3 Analysis and Handling of Protection Switching Fault

During the troubleshooting of a protection switching fault in a system, it is recommended to
locate the fault based on the unit of span with the cooperation of proper command through
the EMS to minimize the influence on services.

l Check the power supply of equipment. If the power supply of an equipment fails, the
icon of corresponding NE in the EMS turns gray and the EMS can not manage the NE
any longer. Power on the equipment again after handling the power supply fault.
l Check optical fibers to find whether there is any performance degradation. Adjust
related optical attenuators or clean related fiber connectors if some abnormal optical
input power is found.
Check NE Configuration
l Check whether the configuration of each NE in the EMS is correct. Once any wrong
configuration is found, re-configure corresponding NE.
l Check whether all fiber pigtails are correctly connected to corresponding interfaces.
3-11


l Check the optical input/output power of optical supervision boards in each related NE
in the EMS to find whether the protection switching fault is caused by communication
problems in the optical supervision system.
l Check the optical input/output power of power detection boards (that is, preamplifier
boards, such as M2SEOPA board) in each related NE in the EMS to find whether the
protection switching fault is caused by the fault of a detection board.
l Check whether the execution boards of protection switching (such as SOPCS board)
in each related NE in the EMS, which run the APS protocol, are working normally.
Then make use of the communication test function of the EMS to find whether the
EMS can normally communicate with the APS controller boards (such as NCP board)
in each NE.
l Check whether there is a new fault occurring at the moment when the system is
performing the restoration action. If yes, issue the “Clear” command to the NEs at both
ends of the span through the EMS after ensuring that the optical line has completely
recovered.
3.5 EMS Communication Fault

3.5.1 Symptom and Cause of EMS Communication Fault
Fault Symptom
l No NE in a system can be successfully pinged through the EMS.
l The NEs in a system can be successfully pinged through the EMS but they can not
be monitored by the EMS.
l Only part NEs in the system can be normally managed by the EMS.
l The boards of NE(s) can not be configured through the EMS.
Fault Cause
l External cause
à Power supply fault: power supply failure and too low voltage of power supply etc.
à Optical fiber fault: performance degradation and too high loss etc.
à Wrong assignment of the EMS computer's IP address or route, as well as the IP

addresses of NEs in the system
à Wrong configuration of ECC
à Some network cable has problems.

à The fiber pigtails used for internal supervision are wrongly connected.
3-12

l Equipment problem
à The network adapter of the EMS computer fails to work normally.
à Some board(s) is (are) faulty.
à The ECC is blocked.
3.5.2 Troubleshooting Flow of EMS Communication Fault

The troubleshooting flow of EMS communication fault is shown in Figure 3-5.
Figure 3-5 Troubleshooting Flow of EMS Communication Fault
3-13

3.5.3 Analysis and Handling of EMS Communication Fault

l Check the power supply of equipment. If the power supply of an equipment fails, the
icon of corresponding NE in the EMS turns gray and the EMS can not manage the NE
any longer. Power on the equipment again after handling the power supply fault.
l Check optical fibers to find whether there is any performance degradation. Adjust
related optical attenuators or clean related fiber connectors if some abnormal optical
input power is found.
Check Configuration
l Check the network configuration of the EMS computer. If the EMS computer itself
can be pinged successfully, it can be concluded that the network adapter in the EMS
computer is working normally and the network configuration is already in use. In this
case, the failure of pinging an NE through the EMS computer may be caused by the
network segment difference between the NE and the EMS computer.
l Check whether the IP addresses of the NE and the EMS computer are consistent with
the configuration data in the EMS after uploading the database of the NE to the EMS.
l Check whether the ECC configuration is correct.
Check Equipment Interconnection

l Check whether a correct network cable (crossover or straight-through network cable)
is used and whether it is correctly connected.
l Check whether the fiber pigtails used for internal supervision are correctly connected.

Check whether there is any board reporting fault alarms. If yes, check the board further
and replace it once it is confirmed damaged.
3.6 Orderwire Fault

3.6.1 Symptom and Cause of Orderwire Fault
Fault Symptom
l It fails to make an orderwire call with no dialing tone heard.
l It fails to make a orderwire call.
l There are lots of noises during an orderwire IP call.
l The orderwire IP telephone rings without reason.
l It is unable to make an orderwire call in a 100 M supervision system.
3-14

Fault Cause
l External cause
à Power supply failure or broken optical fiber etc.
à Incorrect phone setting
à Network cable connection is loose.
à The configuration of orderwire IP calls are wrongly configured.
à The multicast group route in the 100 M supervision system is wrongly calculated.
l Equipment problem
The NCP board of NE(s) is faulty.
3.6.2 Troubleshooting Flow of Orderwire Fault

The troubleshooting flow of orderwire fault is shown in Figure 3-6.
3-15

Figure 3-6 Troubleshooting Flow of Orderwire Fault
3.6.3 Analysis and Handling of Orderwire Fault

l Check whether there are any alarms related to optical lines. If yes, handle these
alarms first because some faults in optical lines may lead to orderwire failure.
l Check whether the fibers at each site are correctly connected according to the speci-
fied configuration.
3-16

l Check whether the orderwire phone set at each site is normal. You can replace the
phone set in use with a normal one to test whether the phone set in use is fine.
l Check whether the network cable connecting with the orderwire board is loose.
Check Orderwire Configuration

l Check whether the orderwire call function has been configured in the EMS.
l Check whether the orderwire numbers of the caller site and the called site are correctly
set, which must be different.
l Check whether the networking mode configured in the EMS is consistent with the
actual one, especially whether there are any optical cables missed.

l Reset the orderwire IP calls at the caller site or the called site.
l Observe the indicators and check related alarms reported in the EMS. Use the
plugging/unplugging method and the replacement method.
l Check the boards connected with optical line fibers at each site and find whether they
are working normally. Replace the faulty board once it is found.
3-17

3-18

List of Figure
Figure 1-1 General Troubleshooting Flow ................................................................. 1-2
Figure 1-2 Emergency Troubleshooting Flow of ZXWM/ZXMP Series DWDM
Optical Transmission System ................................................................. 1-3
Figure 3-1 Service Interruption Fault Location Flow .................................................. 3-2
Figure 3-2 Troubleshooting Flow of Bit Error Fault .................................................... 3-5
Figure 3-3 Optical Power Fault Location Flow ........................................................... 3-7
Figure 3-4 Troubleshooting Flow of Protection Switching Fault ............................... 3-11
Figure 3-5 Troubleshooting Flow of EMS Communication Fault .............................. 3-13
Figure 3-6 Troubleshooting Flow of Orderwire Fault................................................ 3-16
I
List of Figure

List of Table
Table 1-1 Main Alarms and Corresponding Troubleshooting of M2SEOA/Optical
Mux Board ............................................................................................... 1-4
Table 1-2 Indicator Status, Corresponding Common Cause and Handling ................ 1-6
Table 1-3 Main Alarms and Corresponding Troubleshooting of
MQA/TD2C/TS2C/MJA Board ................................................................. 1-7
III
List of Table

Glossary
APC
- Automatic Power Control
APR
- Automatic Power Reduction
APS
- Automatic Protection Switching
APSD
- Automatic Power Shutdown
AWG
- Array Waveguide Grating
DDF
- Disk Data Format
ECC
- Eccor Check and Correction
EMS
- Network Element Management System
FEC
- Forward Error Correction
ODF
- Optical Distribution Frame
OM
- Optical Multiplexer
OSNR
- Optical Signal-Noise Ratio
OTDR
- Optical Time Domain Reflectometer
SDH
- Synchronous Digital Hierarchy
WDM
- Wavelength Division Multiplexing
WTR
- Wait to Restore Time

ZXMP M721: Maintenance Manual (Volume III) Troubleshooting

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZXMP M721: Maintenance Manual (Volume III) Troubleshooting

Загружено:

Авторское право:

Доступные форматы

ZXMP M721

Multi-transmission Platform Compact WDM

Revision No. Revision Date Revision Reason

R1.2 2011–11–10 Version update

R1.1 2011–05–20 Version update

R1.0 2010–10–22 ZXMP M721 (V1.00) First version issued

Serial Number: SJ-20101022085432-008

Publishing Date: 2011–11–10(R1.2)

Chapter 2 Troubleshooting Principles...................................................... 2-1

Chapter 3 Typical Troubleshooting........................................................... 3-1

What Is in This Manual

Chapter 2 Troubleshooting Introduces the basic principles and common methods of

1.1 General Troubleshooting Flow

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

Figure 1-1 General Troubleshooting Flow

1.2 Emergency Troubleshooting Flow

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

Description of Emergency Troubleshooting Flow

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

Check whether there is any loopback (software loopback or hardware loopback)

Board Alarm Troubleshooting

No optical input power alarm

Low optical input power

Pump laser 1 temperature

Pump laser 2 temperature

Pump laser 1 cooling current

Pump laser 2 cooling current

Absence of card alarm

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

Board Alarm Troubleshooting

SOGMD/SOAD board out-

SOGMD/SOAD board out-

SOGMD/SOAD board input

SOGMD/SOAD board input

No optical input power alarm

Low optical input power

OMU AWG temperature

Absence of card alarm

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

Table 1-2 Indicator Status, Corresponding Common Cause and Handling

Indicator Status Common Cause Handling

The red and the green indicators

The board is damaged or

The red indicator of a board dims The board is damaged or

The green indicator of a board The board is damaged or

The board is damaged or

The red and the green indicators The slot corresponding to

The red and the green indicators The board is damaged or

4. Handling of the alarms related to a single optical channel

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

Table 1-3 Main Alarms and Corresponding Troubleshooting of MQA/TD2C/TS2C/MJA Board

Board Alarm Troubleshooting

No optical input power

Low optical input power

SES threshold crossing

No optical output power

Low optical output power

Laser bias current thresh-

These alarms are caused by the board itself. Replace the

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential

6. Bit error fault handling

a. The occurrence of bit errors is related to abnormal optical power, abnormal

SJ-20101022085432-008|2011–11–10(R1.2) ZTE Proprietary and Confidential