Sjzl20060681-Unitrans ZXMP S385 (V2 (1) .00&V2.10) Maintenance Manual

ZXMP S385
SDH Based Multi-Service Node Equipment

Maintenance Manual
Version 2.00 & Version 2.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright © 2005 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.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support
or training are subject to change without notice.
Revision History
Date Revision No. Serial No. Description

2006/06/05 R1.0 sjzl20060681 First version
ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to: (86) 755-26772236; or mail to Publications R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document ZXMP S385 (V2.00&V2.10) SDH Based Multi-Service Node Equipment

Name Maintenance Manual
Product Document
V2.00 & V2.10 R1.0
Version Revision Number
Equipment Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Your
evaluation of Accessibility:
this (Contents, Index, Headings, Numbering, Glossary)
documentation Good Fair Average Poor Bad N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good Fair Average Poor Bad N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Your Add more examples Add more/better quick reference aids
suggestions for Add more detail Improve the index
improvement
of this Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
About this Maintenance Manual .............................................................xiii

About the Manual Suit...........................................................................................xiii
Purpose of this Manual ..........................................................................................xiv
Typographical Conventions.................................................................................... xv
Mouse Operation Conventions................................................................................ xv
Safety Signs.........................................................................................................xvi
How to Get in Touch ............................................................................................xvii
Customer Support................................................................................................................xvii
Documentation Support........................................................................................................xvii
Chapter 1................................................................................... 19
Safety Instructions.................................................................................. 19
Chapter 2................................................................................... 21
Maintenance Overview............................................................................ 21
Maintenance Classification ..................................................................................... 21
Routine Maintenance .............................................................................................................21
Performance Message Handling..............................................................................................21
Alarm Message Handling........................................................................................................21
Emergency Maintenance........................................................................................................22
Requirements of Tools and Instruments.................................................................. 22

Maintenance Tools.................................................................................................................22
Instruments/Meters...............................................................................................................23
Equipment Room Maintenance Rules...................................................................... 23

Work Rules ...........................................................................................................................23
Shift Handover Rules .............................................................................................................24
Basic Maintenance Operations ............................................................................... 25

Unplugging/Plugging Fiber Pigtail ...........................................................................................25
Loopback ..............................................................................................................................26
Optical Power Test.................................................................................................................29
Bit Error Test.........................................................................................................................30
Inserting Alarm to Judge the Switching Status ........................................................................31
Switching Configuration .........................................................................................................32
APS Start/Stop/Reset Settings ...............................................................................................32
Obliged State Settings of CS Board ........................................................................................33
Laser State Settings ..............................................................................................................33
Board Switching ....................................................................................................................33
Using Multimeter to Test Service Cables .................................................................................34
Making Network Cable...........................................................................................................34
Board Reset ..........................................................................................................................36
Maintenance Precautions....................................................................................... 36
Board Maintenance Precautions..............................................................................................36
Precautions in Optical Board Maintenance...............................................................................37
Precautions in Equipment Maintenance...................................................................................37
EMS Maintenance Precautions................................................................................................38
Chapter 3................................................................................... 39
Routine Maintenance .............................................................................. 39
List of Routine Maintenance Items.......................................................................... 39
Environment Maintenance ..................................................................................... 40
Equipment Room Temperature ..............................................................................................40
Equipment Room Humidity ....................................................................................................40
Dustproof Requirements of the Equipment Room....................................................................40
Clear Height..........................................................................................................................40
Wall Treatment in the Equipment Room .................................................................................41
Lighting in the Equipment Room ............................................................................................41
Chutes and Apertures in the Equipment Room........................................................................41
Equipment Power Supply.......................................................................................................41
AC Power Supply...................................................................................................................41
Air Conditioning System.........................................................................................................42
Fire Protection Facilities..........................................................................................................42
Maintenance Space ...............................................................................................................42
Equipment Maintenance Operations ....................................................................... 43

Audio Alarm Check ................................................................................................................43
Cabinet Indicators Observation ..............................................................................................43
Board Indicators Observation.................................................................................................44
Fan Check.............................................................................................................................49
Dustproof Unit Cleansing .......................................................................................................50
Orderwire Phone Check .........................................................................................................50
Service Inspection – Bit Error Test..........................................................................................51
Routine EMS Maintenance Operations..................................................................... 52

User Management.................................................................................................................52
Connection with the EMS .......................................................................................................53
Topology Map Monitoring.......................................................................................................54
Alarm Monitoring...................................................................................................................55
Performance Monitoring.........................................................................................................55
System Configuration Query ..................................................................................................56
Querying User Operation Logs ...............................................................................................56
Report Printing ......................................................................................................................57
Data Backup .........................................................................................................................57
Data Recovery ......................................................................................................................58
Chapter 4................................................................................... 59
Performance Message and Handling...................................................... 59
Performance Message Categories........................................................................... 59
SDH Interface Performance Messages ....................................................................................59
Analog Performance Messages...............................................................................................61
Ethernet Interface Performance Messages ..............................................................................61
Physical Interface Performance Events and Solutions ............................................... 63

Overview ..............................................................................................................................63
Event Causes ........................................................................................................................64
Influence on Equipment.........................................................................................................64
Solutions...............................................................................................................................64
Regenerator Section Performance Events and Solutions........................................... 65

Overview ..............................................................................................................................65
Event Causes ........................................................................................................................65
Solutions...............................................................................................................................66
Multiplex Section Performance Events and Solutions ................................................ 66

Overview ..............................................................................................................................66
Event Causes ........................................................................................................................67
Solutions...............................................................................................................................67
Higher-Order Path Performance Event and Solutions ............................................... 68

Overview ..............................................................................................................................68
Event Causes ........................................................................................................................68
Solutions...............................................................................................................................69
Lower-Order Path Performance Event and Solutions ................................................ 69

Overview ..............................................................................................................................69
Event Causes ........................................................................................................................69
Solutions...............................................................................................................................70
Pointer Justification Performance Event and Solutions .............................................. 70
Overview ..............................................................................................................................70
Event Causes ........................................................................................................................70
Solutions...............................................................................................................................71
Chapter 5................................................................................... 73
Alarm Message and Handling ................................................................. 73
Overview of Alarm Message................................................................................... 73
Alarm Categories...................................................................................................................73
Alarm Levels .........................................................................................................................73
Alarm Priorities......................................................................................................................73
Alarm Summary....................................................................................................................74
Alarm Messages and Solutions............................................................................... 78
Chapter 6................................................................................. 169

Troubleshooting .................................................................................... 169
Troubleshooting Procedures................................................................................. 169
Basic Principles of Troubleshooting ....................................................................... 170
Observing ...........................................................................................................................170
Query .................................................................................................................................171
Thinking..............................................................................................................................171
Action .................................................................................................................................171
Basic Considerations for Fault Locating ................................................................. 171

Causes................................................................................................................................171
Common Methods of Fault Locating...................................................................... 173

Observation & Analysis Method ............................................................................................173
Test Method........................................................................................................................173
Unplugging/Plugging ...........................................................................................................174
Replacement Method...........................................................................................................174
Configuration Data Analysis Method .....................................................................................175
Reconfiguration Method .......................................................................................................175
Instrument Test Method ......................................................................................................176
Processing by Experiences ...................................................................................................176
Typical Troubleshooting....................................................................................... 176

Communication Fault...........................................................................................................177
Service Interruption Fault ....................................................................................................178
Bit Error Fault......................................................................................................................181
Clock Synchronization Fault .................................................................................................185
EMS Connection Fault..........................................................................................................188
Orderwire Fault ...................................................................................................................190
Fan Fault.............................................................................................................................191
Equipment Interconnection Fault..........................................................................................192
Ethernet Service Fault .........................................................................................................193
Chapter 7................................................................................. 197

Maintenance Examples ......................................................................... 197
Complete Blockage of Service due to Optical Cable Link Interruption....................... 197
System Overview ................................................................................................................197
Fault Description .................................................................................................................198
Fault Analysis......................................................................................................................198
Troubleshooting ..................................................................................................................198
B2 Bit Error due to High Temperature................................................................... 199

System Overview ................................................................................................................199
Fault Analysis......................................................................................................................200
B2 Bit Error due to Optical Board Fault.................................................................. 200

System Overview ................................................................................................................200
Fault Analysis......................................................................................................................201
Tips ....................................................................................................................................202
155 M Optical Interfaces Interworking Failure due to Improper Fiber Pigtail ............. 202
System Overview ................................................................................................................202
Fault Analysis......................................................................................................................203
155 M Electrical Interfaces Interworking Failure due to Improper Transmission Distance

......................................................................................................................... 204
System Overview ................................................................................................................204
Fault Analysis......................................................................................................................204
Switching Failure/Service Block due to CS Board Malfunction.................................. 205

System Overview ................................................................................................................205
Fault Analysis......................................................................................................................206
Tips ....................................................................................................................................206
LOF or LOS of Optical Board due to Clock Fault...................................................... 207

Fault Analysis......................................................................................................................207
Conclusion ..........................................................................................................................207
MS Switching Abnormality due to Invalid MS Protection Relation............................. 207

Fault Analysis......................................................................................................................208
Appendix A .............................................................................. 209

NE Address Definition and Route Configuration .................................. 209
Definition of NE IP Address .................................................................................. 209
FLSM Addressing.................................................................................................................209
VLSM Addressing.................................................................................................................211
Example of Network Address Coding of NEs .......................................................... 213

Address/Route Configuration of the EMS Host ....................................................... 215
EMS Host Address ...............................................................................................................215
Route Configuration.............................................................................................................216
Route Configuration Command ............................................................................................217
Appendix B .............................................................................. 221

NCP Application/Logic Upgrade ........................................................... 221
Description of NCP Board..................................................................................... 221
Description of BOOTROM Module on NCP Board .................................................... 222
Functions of BOOTROM Module on NCP ................................................................................222
NCP Board State Switching ..................................................................................................223
Local Upgrade Instructions .................................................................................. 224

Upgrade Preparations ..........................................................................................................225
Clearing the Database .........................................................................................................229
Downloading the Application/Logic .......................................................................................229
Upgrading Application/Logic.................................................................................................230
Verifying the Application/Logic .............................................................................................231
Upgrading Application/Logic for Standby NCP .......................................................................233
Downloading the Database ..................................................................................................233
Verifying the Application/Logic Version in the EMS ................................................................234
Remote Upgrade Instructions .............................................................................. 235

Upgrade Preparations ..........................................................................................................237
Confirming the Address of the Master NCP Board..................................................................237
Downloading the Application/Logic .......................................................................................238
Upgrading the Application/Logic ...........................................................................................239
Verifying the Upgraded Application/Logic..............................................................................240
Try Run of the Application/Logic...........................................................................................241
Verifying the Application/Logic that Passed the Try Run.........................................................242
Activating the Application/Logic............................................................................................244
Verifying the Activated Application/Logic...............................................................................245
Upgrading the Application/Logic for Standby NCP..................................................................246
Downloading the Database ..................................................................................................247
Verifying the Application/Logic Version in EMS ......................................................................247
Appendix C .............................................................................. 249

Maintenance Forms............................................................................... 249
Half-day Maintenance Record .............................................................................. 250
Daily Maintenance Record ................................................................................... 252
Weekly Maintenance Record ................................................................................ 254
Login Password Change Record............................................................................ 255
Appendix D ............................................................................. 257

Board Replacement............................................................................... 257
Board Plugging/Unplugging ................................................................................. 257
Unplugging the Board..........................................................................................................257
Plugging the Board ..............................................................................................................258
Board Operation Precautions................................................................................................259
Flowchart of Board Replacement .......................................................................... 260

Preparing a Spare Board......................................................................................................261
Preparing a Label ................................................................................................................261
Service Switching ................................................................................................................261
Unplugging the Board..........................................................................................................261
Labeling the Faulty Board ....................................................................................................262
Plugging the Board ..............................................................................................................262
Restoring the Service Function.............................................................................................262
Board Replacement Procedure ............................................................................. 262

NE Control Processor (NCP) .................................................................................................262
Cross-connect and Clock Board (CSA/CSE)...........................................................................263
Orderwire Board (OW).........................................................................................................263
Optical Line Board (OL64/OL16/OL4/OL1) ............................................................................264
Line Processor (LP1)............................................................................................................264
Electrical Processor (EPE1/EPT1/EP3) ...................................................................................265
Ethernet Board (TGE2B/MSEB/SEC).....................................................................................265
Appendix E............................................................................... 267
Equipment Upgrade .............................................................................. 267
Version Overview................................................................................................ 267
Hardware Upgrade.............................................................................................. 268
EMS Software Upgrade ....................................................................................... 269
Board Software Upgrade ..................................................................................... 270
Appendix F............................................................................... 271

Common Instruments and Meters........................................................ 271
PMS-1A Optical Power Meter................................................................................ 271
Function..............................................................................................................................271
Panel Description.................................................................................................................272
Operation Flowchart ............................................................................................................273
Precautions .........................................................................................................................273
ALL-11 Chip Burner ............................................................................................ 274

Function..............................................................................................................................274
Operation Flow....................................................................................................................276
Precautions .........................................................................................................................277
YGBERT-2M 2 M BER Tester ................................................................................ 277

Function..............................................................................................................................277
Operation Flow....................................................................................................................279
Precautions .........................................................................................................................279
SDH Analyzer..................................................................................................... 280
Appendix G.............................................................................. 281

Alarm Quick Reference Table................................................................ 281
Appendix H ............................................................................. 285

Abbreviations ........................................................................................ 285
Figures........................................................................................ 291
Tables ......................................................................................... 293

About this Maintenance
Manual
About the Manual Suit

This manual is applicable for the Unitrans ZXMP S385 (V2.00 & V2.10)
SDH based multi-service node equipment (the ZXMP S385 for short).
The ZXMP S385 is an SDH based multi-service node equipment with the
highest transmission rate of 10 Gbit/s. It can apply to the long haul
backbone transmission network, backbone area transmission network, and
metropolitan area transmission network (at access layer and convergence
layer).
The whole manual suite of ZXMP S385 is listed as follows:
Unitrans ZXMP S385 (V2.00&V2.10) SDH Based Multi-Service Node

Equipment Technical Manual
It describes the system architecture, system features, system
functions, technical specifications, and application example.
Unitrans ZXMP S385 (V2.00&V2.10) SDH Based Multi-Service Node

Equipment Hardware Manual
It describes the equipment hardware, including cabinet, power
distribution box, dustproof unit, ventilation unit, subracks, boards and
interfaces.
Unitrans ZXMP S385 (V2.00&V2.10) SDH based Multi-service Node

Equipment Installation Manual
It describes the equipment installation procedures, including
installation preparation, hardware installation, cable layout, installation
check, and the detailed power on/off operations.
Unitrans ZXMP S385 (V2.00&V2.10) SDH based Multi-service Node

Equipment Maintenance Manual
It describes the content and operations of daily maintenance,
emphasizing common alarms, reasons and handlings of typical faults.
It also gives typical cases for maintenance reference.
Confidential and Proprietary Information of ZTE CORPORATION xiii

ZXMP S385 (V2.00&V2.10) Maintenance Manual
Purpose of this Manual

This manual is the Unitrans ZXMP S385 (V2.00&V2.10) SDH Based Multi-
Service Node Equipment Maintenance Manual. The content of this manual
is as follows:
Chapter 1 Safety Instructions, gives the safety precautions for equipment

maintenance.
Chapter 2 Maintenance Overview, gives the basic knowledge of equipment

maintenance, including maintenance classification, tools and instruments
for maintenance, basic operation and precautions of equipment
maintenance.
Chapter 3 Routine Maintenance, describes the routine maintenance issues,

maintenance interval, and operation methods.
Chapter 4 Performance Message and Handling, summarizes the ZXMP

S385 performances; describes the mechanism, effect, and handlings of
various performance events.
Chapter 5 Alarm Message and Handling, gives the classification, severity

levels, and priorities of alarms; summarizes the alarms; describes the
alarm causes and handlings.
Chapter 6 Troubleshooting, describes the troubleshooting flow, locating

faults, and troubleshooting analysis method; classifies the typical faults of
ZXMP S385, and describes the fault causes and handlings in details.
Appendix A NE Address Definition and Route Configuration, describes how

to define the NE address and configure the route of the NE management
server.
Appendix B NCP Application/Logic Upgrade, describes how to download the

NCP application/logic of the ZXMP S385.
Appendix C Maintenance Forms, gives the tables for recording the routine
maintenances.
Appendix D Board Replacement, describes the board replacement issues,

including preparations, operation steps and noticeable issues.
Appendix E Upgrade, describes the version information of the ZXMP S385,

and the equipment upgrade operations.
Appendix F Common Instruments and Meters, describes the commonly

used instruments during maintenance.
Appendix G Alarm Quick Reference Table, summarizes the common alarms.

The user can quickly look up the alarm causes and handlings in this table.
Appendix H Abbreviations, gives the abbreviations and terms used in this

manual.
xiv Confidential and Proprietary Information of ZTE CORPORATION

About this Maintenance Manual
Typographical Conventions
ZTE documents employ with the following typographical conventions.
TABLE 1 TYPOGRAPHICAL CONVENTIONS
Typeface Meaning
Italics References to other guides and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input fields, radio
button names, check boxes, drop-down lists, dialog box
names, window names.
CAPS Keys on the keycard and buttons on screens and company
name.
Constant width Text that you type, program code, files and directory names,
and function names.
[] Optional parameters
{} Mandatory parameters
| Select one of the parameters that are delimited by it
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be

checked before proceeding further.
Tip: Indicates a suggestion or hint to make things easier or

more productive for the reader.
Mouse Operation Conventions

TABLE 2 MOUSE OPERATION CONVENTIONS
Typeface Meaning
Click Refers to clicking the primary mouse button (usually the left
mouse button) once.
Double-click Refers to quickly clicking the primary mouse button (usually
the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button (usually the
right mouse button) once.
Drag Refers to pressing and holding a mouse button and moving the
mouse.
Confidential and Proprietary Information of ZTE CORPORATION xv

Safety Signs
TABLE 3 S AFETY SIGNS
Safety Signs Meaning

Danger: Indicates an imminently hazardous situation, which if
not avoided, will result in death or serious injury. This signal
word should be limited to only extreme situations.
Warning: Indicates a potentially hazardous situation, which if

not avoided, could result in death or serious injury.
Caution: Indicates a potentially hazardous situation, which if not

avoided, could result in minor or moderate injury. It may also
be used to alert against unsafe practices.
Erosion: Beware of erosion.
Electric shock: There is a risk of electric shock.
Electrostatic: The device may be sensitive to static electricity.
Microwave: Beware of strong electromagnetic field.
Laser: Beware of strong laser beam.
No flammables: No flammables can be stored.
No touching: Do not touch.
No smoking: Smoking is forbidden.
xvi Confidential and Proprietary Information of ZTE CORPORATION

About this Maintenance Manual
How to Get in Touch

The following sections provide information on how to obtain support for
the documentation and the software.
Customer Support
If you have problems, questions, comments, or suggestions regarding
your product, contact us by e-mail at support@zte.com.cn. You can also
call our customer support center at (86) 755 26771900 and (86) 800-
9830-9830.
Documentation Support
ZTE welcomes your comments and suggestions on the quality and
usefulness of this document. For further questions, comments, or
suggestions on the documentation, you can contact us by e-mail at
doc@zte.com.cn; or you can fax your comments and suggestions to (86)
755 26772236. You can also explore our website at
http://support.zte.com.cn, which contains various interesting subjects like
documentation, knowledge base, forum and service request.
Confidential and Proprietary Information of ZTE CORPORATION xvii

xviii Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Safety Instructions
Only qualified professionals are entitled to install, operate and maintain

the equipment.
Abide the local safety rules and related operation regulations during the
equipment installation, operation and maintenance, to avoid personal
injuries or equipment damages. The safety precautions in this manual are
only a supplement to the local safety rules.
ZTE Corporation assumes no responsibility for consequences resulted from

violation of general safety operation specifications or of safety rules for
design, production and use of equipment.
Refer to Safety Signs for the signs of the safety precautions during the
equipment installation, operation and maintenance.
Confidential and Proprietary Information of ZTE CORPORATION 19

20 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 2
Maintenance Overview
In this chapter, you will learn about:

Maintenance classification
Tools and instruments required for the maintenance
Equipment room maintenance regulations
Basic operations and precautions of the equipment maintenance
Maintenance Classification
Equipment maintenance is divided into routine maintenance, performance
message handling, alarm message handling, and emergency maintenance.
Routine Maintenance
Routine maintenance involves checking the equipment operation status
periodically, and handling the problems promptly; so as to find hidden
trouble, prevent accident, find fault and handle them as early as possible.
Performance Message Handling

Performance message handling involves analyzing the performance
messages during the system operation, judging whether there is any
abnormity, and taking corresponding measures.
Alarm Message Handling

Alarm message handling involves analyzing the alarm messages during
equipment operation, judging the equipment running condition, and taking
corresponding measures.

Emergency Maintenance
Emergency maintenance is also called troubleshooting. It involves
maintenance tasks brought by transmission equipment faults or network
adjustments, such as the maintenance tasks to handle equipment damage,
line faults, and emergency events found and recorded in routine
maintenance.
Chapter 6 Troubleshooting elaborates the specific handling methods of

emergencies.
Requirements of Tools and

Instruments
This section describes the tools and instruments required during the
equipment maintenance.
Maintenance Tools
Table 4 lists the maintenance tools in the equipment room.
TABLE 4 M AINTENANCE TOOLS
Name Name
Tape Crimper
Screwdrivers (one each for straight/cross screwdriver
40 W electrical iron
respectively in large, medium, and small sizes)
Long straight screwdriver (equipment accessory) Clamping pincers
Tweezers IC extractor
Adjustable wrench Antistatic wrist strap
Diagonal pliers Insulating tape
Sharp nose pliers Strap
Wire stripper Pliers
Scissors Fiber extractor
Straight-through cable (the length depends on the actual
-
requirement)
The following items need to be prepared for the equipment maintenance:

absolute alcohol, dust-free paper, soldering-tin cord, rosin, insulating tape,
strap, 2 M self-loop cable, and fiber-pigtail jumper. For equipment upgrade,
the maintenance personnel should also prepare appropriate number of
NCP BOOTROOM chips and board application chips.

Chapter 2 - Maintenance Overview
Instruments/Meters
Meters for Environment Monitoring
Include thermometers and hygrometers. They should be always prepared
in the equipment room for detecting the equipment operating environment.
Instruments/Meters for Maintenance

Include one each for digital multimeter, optical power meter, optical
attenuator and PDH bit error tester.
If possible, prepare one SDH synthetic analyzer to replace the optical

power meter and PDH bit error tester.
If it is necessary to temporarily access the EMS for maintenance at some

sites, prepare a portable PC (with built-in modem, Ethernet adapter, and a
straight-through cable).
Other Instruments
Chip burner: For equipment upgrading, if no chips of new version are
burned, a chip burner should be prepared.
Optical communication instruments and computers: As they are expensive,

one transmission network project can be equipped with only one or several
major sites depending on the network scale. Other sites can share these
instruments.
Caution: All the instruments/meters should be checked and calibrated before using,
to ensure their accuracies and good conditions.
Equipment Room Maintenance

Rules
A complete set of effective maintenance rules should be developed to
ensure that the equipment room environment satisfies the equipment
running requirements, and for better equipment maintenance. All the
maintenance personnel should observe these rules. This section lists the
work rules and shift rules of the equipment room for users’ reference.
Work Rules
1. Keep the equipment room tidy and clean. Change shoes at the door,
keep the floor clean, keep the equipment dust-free, arrange the
equipment properly; Ensure that the instruments are precise, the tools
are ready and the materials are complete.

2. Do not smoke, eat, play games, or talk loudly in the equipment room.
3. Do not put personal articles around in the equipment room, and do not
do anything irrelevant to the job.
4. Do not bring inflammable or explosive articles into the equipment room.
Unauthorized entry into the equipment room is not allowed.
5. Put on antistatic wrist strap before operating the equipment.
6. Take care of the public properties in the equipment room.
7. Do not disclose any confidential information.
8. Keep proper records and statistics of the original data. Make sure that
the technical documents and original records are authentic and
complete.
9. The person on duty must be dutiful. Handle and report any major fault
and accident promptly.
10. There should be leaders who conduct regular checks for the equipment
room, and make continuous improvement.
Shift Handover Rules

1. The shift handover rules are very important for uninterrupted
communications and should be strictly followed by each maintenance
person.
2. The persons on duty should perform shift handover seriously. The
responsibilities and formalities should be clearly defined to ensure
smooth shift handover.
3. The person on the previous shift should, before going off duty, provide
clear information about his shift to the person on the next shift; The
person on the next shift should conduct careful checks before taking
over the duty.
4. Make sure during the shift handover that: the equipment running
status, the state of the tools and instruments are clear; various
drawings and records are complete.
5. The person on the previous shift should stay on duty until the person
on the next shift arrives and the shift handover is completed.
6. After proper shift handover, the persons of both shifts should sign on
the work log as a written record, indicating that the equipment has
been handed over to the next shift.
7. If fault occurs during shift handover, the persons of both shifts should
be responsible for the troubleshooting.

Basic Maintenance Operations

Proper maintenance operations can locate and clear the fault when
abnormities occur in the system.
The ZXMP S385 maintenance can be classified into equipment

maintenance and NE management system (EMS) maintenance.
The equipment maintenance operations refer to operations on the

equipment hardware, such as unplugging/plugging fiber pigtails and
hardware loopback.
The EMS maintenance operations refer to operations on the equipment
through the EMS, such as inserting bit errors and software loopback.
Refer to the relevant EMS manual for the detailed EMS maintenance
operations.
Caution: Once the test and diagnosis finish, the maintenance operations conducted
should be canceled in time, so that the equipment operation will not be affected.
Unplugging/Plugging Fiber Pigtail

A fiber pigtail is a segment of optical fiber connecting the external optical
interface of the equipment or the ring flange of the optical distribution
frame (ODF). It has connectors (i.e. fiber pigtail plugs) at both ends.
The common fiber pigtail connectors are listed in Table 5.
TABLE 5 COMMON FIBER PIGTAIL CONNECTORS (PLUGS)
Type Description Picture Type Description Picture
Round fiber Round fiber

connector/polished connector/polished
FC/PC FC/APC
slightly convex convex sphere at
sphere 8o
Square fiber Square fiber

connector/polished connector/polished
SC/PC SC/APC
slightly convex convex sphere at
sphere 8o
Round bayonet Round bayonet

fiber connector fiber connector/
ST/PC ST/APC
/polished slightly polished convex
convex sphere sphere at 8o
Square bayonet
Square bayonet fiber connector
MT-RJ LC/PC
fiber connector /polished slightly
convex sphere

Note: The fiber pigtail connector type of the ZXMP S385 is LC/PC.
To plug a fiber pigtail with LC/PC plug
1. Hold the fiber pigtail plug with your thumb and forefinger; align the
spring piece on the plug with the grove of the optical interface flange;
push the pigtail inward with a moderate force. Avoid damaging the
ceramic inner pipe of the optical adaptor or the connector end surface.
2. Push in the pigtail connector as far as possible until it clicks to place.
To unplug a fiber pigtail with LC/PC plug
1. Hold the pigtail connector with your thumb and index finger or with an
extractor, and press down the spring piece on the connector.
2. Pull out the connector with moderate force.
3. Protect the fiber pigtail plug with a dustproof cap to avoid end surface
contamination caused by the dust.
Laser: During optical fiber operation, do not look staight at the laser beam of the
optical interface or inside the optical fiber to avoid eye hurt.
Loopback
Loopback is the operation of sending information from the transmitting
interface of an NE, and receiving the information from the receiving
interface of that NE. It is a usual measure for detecting the fault of
transmission channel.
The loopback can locate the faulty point of the NE level by level in case of
separate communication links, and detect the working status of nodes and
transmission lines. It helps locate the faulty NE and even the faulty board
quickly and accurately. It also facilitates the equipment commissioning and
debugging.
The loopback includes the hardware/software loopback.
The loopback signal may be optical or electrical.
Caution: The loopback may cause service interruption. Be cautious to use it.
Hardware Loopback
The hardware loopback connects the receiving/transmitting interfaces of
one signal via physical method. In terms of the signal flow direction, the
hardware loopback orients towards the equipment inside, so it is also
called hardware self-loop. Self-loops of the electrical signal and optical

signal are similar. The following content takes the optical interface
hardware self-loop as an example.
The optical interface hardware self-loop connects the

receiving/transmitting optical interfaces of an optical line board via fiber
pigtail, to achieve signal loopback. The optical interface hardware self-loop
includes local self-loop and cross self-loop.
The local self-loop connects the optical receiving (R) interface with the
optical transmitting (T) interface of one optical direction in the local
equipment via fiber pigtail.
The cross self-loop connects the optical transmitting/receiving (T/R)
interfaces of an optical direction with the optical receiving/transmitting
(R/T) interfaces of another optical direction in the local equipment via
fiber pigtail.
Warning: When using fiber pigtail to do optical interface hardware self-loop, an

appropriate optical attenuator must be added to the front of the optical interface of
the receiving end, to avoid damage to the optical interface due to excessive optical
power. Resume the original optical link after the loopback test.
Software Loopback
The software loopback employs the EMS software to implement loopback.
It can configure not only the optical/electrical signal self-loop equivalent to
the hardware loopback, but also the line loopback or single channel
loopback.
Classification according to the loopback direction

According to the loopback direction, the software loopback is divided
into line side loopback and terminal side loopback.
The loopback from a line board to a line interface is called line side
loopback; the loopback in the reverse direction is called terminal
side loopback.
The loopback from a tributary board to a tributary interface is
called terminal side loopback; the loopback in the reverse direction
is called line side loopback.
Software loopback in different directions are shown in Figure 1.

FIGURE 1 THE ZXMP S385 SOFTWARE LOOPBACK IN DIFFERENT DIRECTIONS
Line side loopback Terminal side

loopback
Equipment
Line interface
inside
Line board
Terminal side loopback Line side

loopback
Tributary Equipment
interface inside
Tributary board
Loopback path types

Software loopback can control the receiving/transmitting connection of a
path via the EMS.
For the ZXMP S385, the paths that can implement software loopback
include: administrative unit AU4, concatenation administrative unit AU4-nc,
and tributary unit VC12.
The correspondence between loopback points and boards are listed in

Table 6.
TABLE 6 LOOPBACK POINTS AND CORRESPONDING BOARDS
Loopback Point Board Type

AU4 Optical line board, STM-1 electrical processor
AU4-nc Optical line board above STM-4
VC3 EP3
VC12 2 M electrical tributary board
VC11 EPT1
Note: The loopback principle is to minimize the effect on services. Avoid using the
AU loopback if the fault can be located via tributary unit loopback.

Optical Power Test

This section describes the test methods of optical launched/received power,
and cautions of the test.
Optical Launched Power Test

The test method of optical launched power is shown in Figure 2.
FIGURE 2 OPTICAL L AUNCHED POWER TEST
Fiber
pigtail
R
Optical interface of
optical line board
Optical power meter
To test the optical launched power
1. Set the optical receive wavelength of the optical power meter to be the
same as the optical transmit wavelength of the tested optical line
board.
2. Connect one end of the fiber pigtail to the optical transmit interface of
the tested optical board, and the other end to the test input interface
of the optical power meter. Read the stable optical power value of the
optical power meter, i.e. the optical launched power of this optical line
board.
Optical Received Power Test
To test the optical received power
1. Set the receiving optical wavelength of the optical power meter to the
same as the tested optical wavelength.
2. Select at the local site the fiber pigtail that connects to the
transmitting optical interface of the adjacent site. Normally, this fiber
pigtail is connected to the receiving optical interface of the optical line
board at the local site. Connect the fiber pigtail to the test input
interface of the optical power meter. Read the stable optical power

value of the optical power meter, i.e. the optical received power of this
optical line board.
Cautions of Optical Power Test

Make sure that fiber pigtail connectors are clean; Make sure that the
connecting devices of the ring flanges on the optical board panel and
the optical power meter are well coupled.
Measure the attenuation of the fiber pigtail before the test, to make
sure that this fiber pigtail has good transmission performance. For
optical boards using single-mode and multi-mode optical interfaces,
use different fiber pigtails for test accordingly.
If necessary, the attenuation values of the optical connector and the
testing fiber can be considered known, serving to amend the mean
optical launched power read from the optical power meter. For higher
test accuracy, take the average value of multiple test results, and then
amend it with the attenuation values of the optical connector and the
testing fiber.
Bit Error Test

The ZXMP S385 can implement two types of bit error test: test with a bit
error tester and test via software.
Test with Bit Error Tester

The test with bit error tester may be implemented online or offline. The
test point for bit error is the service access point that the equipment
provides for the user, such as the 2 M and 155 M physical interfaces.
Online test
Select a service channel in use, directly connect the bit error tester to
the monitoring connector of the DDF or ODF that connects with the
corresponding interface of the channel, and perform online monitoring.
In normal case, the tester should show no bit error.
Offline test
Select a service channel, and find the PDH/SDH interface of this
channel at both the local site and the remote site.
Perform a line side loopback at the remote PDH/SDH interface via
the EMS software, or a hardware loopback on the DDF.
Perform bit error test at the corresponding PDH/SDH interface via
the bit error tester.
In normal case, the tester should show no bit error.
Caution: Make sure that the meter is well grounded. Do not turn on/off any other
electrical appliances during the test.

EMS Software Test

In the EMS software, execute the Insert Error Code command to forcibly
insert bit error into the signal channel. If the insertion is successful, the
corresponding bit error performance value can be queried at the opposite
end of the channel. The bit error insertion can be used to judge the status
of channels.
The correspondences between the bit error insertion points, bit error types,
and boards of ZXMP S385 are listed in Table 7.
TABLE 7 THE CORRESPONDENCES BETWEEN THE BIT ERROR INSERTION POINTS, BIT
ERROR TYPES, AND BO ARDS
Insertion
Bit Error Type Board Type
Point
VC12 V5 bit error 2 M electrical tributary board, Ethernet board
VC3 B3 bit error Ethernet board
VC4 B3 bit error Optical line board, STM-1 electrical processor
MS B2 bit error Optical line board, STM-1 electrical processor
RS B1 bit error Optical line board, STM-1 electrical processor
VC3-nc B3 bit error Optical line board
VC4-nc B3 bit error Optical line board above STM-4
The manually-inserted B2/B3/V5 bit errors have no influence on the

services, and can not be detected by the instruments. They can only be
queried from the EMS terminal. If the insertion point is a higher-order VC3
path virtual container and it is configured as a bidirectional service, the
same amount of remote bit errors should be detected on the board where
the insertion point locates.
Inserting Alarm to Judge the Switching

Status
Alarm insertion uses a manually-generated alarm to monitor the system.
For the ZXMP S385, the AIS alarm can be inserted via the EMS software,
to judge whether the switching of the self-healing ring network is normal.
The correspondences between the alarm insertion points and boards are
listed in Table 8.
TABLE 8 AL ARM INSERTION POINTS AND CORRESPONDING BOARDS
Insertion point Board Type

TU12 2 M electrical tributary board, Ethernet board
TU3 Ethernet board
MS Optical line board, STM-1 electrical processor

Insertion point Board Type

AU4-nc Optical line board above STM-4
AU4 Optical line board, STM-1 electrical processor
Once the alarm insertion succeeds, the AIS alarm should be reported in
the corresponding channel at the receiving end. If the insertion point is
TU3/TU12 and is configured as bidirectional service, the insertion point
should also report the “Remote Defect Indication (RDI)” alarm. When the
alarm insertion succeeds, if the service is not interrupted in a protected
network, it indicates that the switching is normal; if the service is
interrupted, it indicates that the switching is abnormal. Check the line and
related boards.
Switching Configuration
The ZXMP S385 can implement the multiplex section (MS) protection and
sub-network connection protection. The MS protection includes 2-fiber/4-
fiber bidirectional MS shared protection, and 1+1/1:1 MS dedicated
protection. The sub-network connection protection includes the AU4, TU3,
and TU12 levels protections. When the working sub-network connection
fails or the performance is lower than a necessary level, it will be replaced
by the protection sub-network connection.
The Protection Switch command in the EMS software can be used to

configure the switching status of the equipment. The external switching
operations include “Lock”, “Forced Switching”, “Manual Switching” and
“Exercise”. The priorities of the operations from high to low are: Lock →
Forced Switching → Manual Switching → Exercise.
The meanings of the switching operations are:
Lock: Refuses any access to the protection section/path.

Forced Switching: Unless a switching instruction of equal or higher
priority is taking effect, the system will switch to the working
/protection sections and working/protection paths, no matter if the
switching section/path is faulty.
Manual Switching: Unless a switching instruction of equal or higher
priority is taking effect or the switching section/path is faulty, the
system will switch to the working /protection sections and
working/protection paths according to the request.
Exercise: Only processes the APS protocol, and does not implement
switching.
APS Start/Stop/Reset Settings

When the network topology is a ring and MS protection is used, a unique
ID should be configured for an NE in the ring network. This ID is the APS.
The following APS-related operations can be implemented via the EMS
software:

APS start
It means that the equipment APS protocol is in normal working status, and
the MS protection ring is in the automatic protection switching status.
When the MS protection ring is configured, the APS should be started.
APS stop
It stops the equipment APS protocol, and keeps the data before the stop.
For example, if the MS protection switching has happened at a site before
the APS stop, this MS protection switching operation will be maintained
after the APS stop configuration, and the new data will not be processed.
APS reset
When the equipment receives the APS reset command, it will clear all
current APS data, save the equipment initialization data, and then return
to the normal working status, waiting for the new data and automatic
protection switching. In addition, when the equipment receives the APS
reset command, it directly enters the APS started status.
Obliged State Settings of CS Board

The ZXMP S385 employs the dual-bus design. Each service interface board
is connected with two CS boards through two sets of buses (each set of
bus includes service bus and overhead bus). The two sets of buses are
independent of each other, so are the two CS boards. The two CS boards
select the service bus and overhead bus according to principle of
concurrently transmitting and preferred receiving.
The Obliged state of the CS board command in the EMS software can
be used to set the CSA/CSE board bus used by board.
Note: All boards except for the NCP and CSA/CSE boards support operations of CS
board obliged state.
Laser State Settings

The laser state of the equipment is the laser state of the optical line board
and the optical amplifier. The Diagnosis function of the EMS software
may be employed to set the laser state.
The laser of the ZXMP S385 supports two modes: open and shutdown.
When a laser is open, the optical line board is in light emitting state; when
the laser is shut down, the optical power is zero and the optical line board
is in no light state. Laser shutdown is often used to shut down an
unconnected optical interface and protects operating personnel engaged in
optical line maintenance.
Board Switching
The ZXMP S385 can implement the 1:N protection for tributary board. For
the NE configured with board protection, the standby board works in

standby mode when the master board works normally. When the master
board is abnormal, the standby board switches to the active mode and
works instead of the master board, to ensure the normal services.
Board switching switches the services of the master board to the standby
board, to protect the services. Tributary boards support the board
switching operation.
The board switching types include protect switching, forced switching,

manual switching, and clear switching. The types are described below:
Protect switching: The EMS sends this command and forces the master
board to work, no matter whether the master board works normally.
Forced switching: The EMS sends this command and forcibly switches
services to the configured board, no matter whether the board works
normally.
Manual switching: The EMS sends this command. If the configured
board works normally, the system forcibly switches services to it;
otherwise, the active board before the command is sent still works.
Clear switching: The active board will stop working once it detects
abnormality, and will notify the standby board about its status. The
standby board that works normal will switch to active status at once
and work instead of the faulty board. This command is the default EMS
configuration.
Using Multimeter to Test Service Cables

During the construction and maintenance, the service cables need to be
tested often, to check if there are any false soldering, open solder joint,
short circuit, and wrong cable connection on the DDF.
To test the cable using multimeter
1. Short-circuit the signal core and shielded layer with a short conducting
wire or tweezers at one end of the cable, and then measure the
resistance between the signal core and shielded layer at the other end.
The resistance value got should be zero.
2. Remove the above short-circuit. Measure the resistance at the other

end of the cable, and the value should be infinite.
If the results of the above two tests are normal, the tested ends are of the
same cable, and the cable is normal. Otherwise, the cable has short-circuit
or break somewhere; the cable plug has false soldering, open solder point
or short circuit; or the tested ends are not of the same cable.
Making Network Cable

Two types of network cables can be used for connection between the EMS
computer and the NEs: crossover network cable and straight-through
network cable.

Figure 3 illustrates network cable.
FIGURE 3 NETWORK CABLE
A V ie w
1
A
8
R J 4 5 p lu g R J 4 5 p lu g
A network cable has an RJ45 plug at either end. Figure 3 shows how the
pins are numbered in an RJ45 plug.
The crossover network cable directly connects the ZXMP S385

equipment and EMS computer.
Table 9 lists the color spectrums and connection relations of the
crossover cable.
TABLE 9 COLOR SPECTRUMS AND CONNECTION RELATIONS OF THE CROSSOVER CABLE
No. of the RJ45

Plug Pins at the 1 2 3 6 4 5 7 8
Equipment End
Color Spectrums White Orange White Green Blue White White Brown
of the Category-
5 network cable &orange &green &blue &brown
No. of the RJ45

User End
The straight-through network cable connects the ZXMP S385

equipment and EMS computer through a hub.
Table 10 lists the color spectrums and connection relations of the
straight-through network cable.
TABLE 10 COLOR SPECTRUMS AND CONNECTION RELATIONS OF THE STRAIGHT-THROUGH

NETWORK CABLE
No. of the RJ45

Equipment End
Color Spectrums White Orange White Green Blue White White Brown
of the Category-
5 Network Cable &orange &green &blue &brown
No. of the RJ45

User End

Board Reset
Board reset operations include the hardware reset and software reset.
Warning: Only reset the board to recover its normal work. Do not reset the board
unless the board function is confirmed to be affected by the processor fault.
Hardware reset
There is a reset hole with reset switch in it on the board front panel.
Press down the reset switch to reset the CPU and other chips of the
board.
Software reset
The software reset resets the board via the EMS software. The
software reset itself includes hard-reset and soft-reset.
Hard-reset resets all the chips including the CPU.

Soft-reset resets the application programs of the board. It has two
levels:
i. CPU level: Only resets the CPU application programs.
ii. IC level: Resets application programs of the CPU and of ICs on

the board
Caution: Resetting the NCP board will interrupt the EMS monitoring of the NEs.
Maintenance Precautions
Before the maintenance operations on the ZXMP S385, the operator
should learn not only the basic precautions for maintaining general
communication equipment, but also the special precautions for
maintaining transmission equipment, to ensure safety of both human and
equipment.
Board Maintenance Precautions

Take proper antistatic measures in equipment maintenance to avoid
any damage to the equipment. As human body may generate static
electromagnetic field that persists for long, one should wear antistatic
wrist straps and well ground them at the other end before touching the
equipment, in order to prevent human static electricity from damaging
sensitive components and devices. The boards not in use should be
kept in the antistatic bags.

Pay attention to the damp-proof handling of the boards. The

environment temperature and humidity effect must be taken into
consideration for standby board storage. Usually, put some desiccant
in the antistatic bags of the board, to keep the bag inside dry. When a
board is moved from a colder and drier place to a hotter and damper
place, wait for at least 30 minutes before unpacking it. Otherwise,
moisture may condense on the board surface and damage the
components.
Be careful to plug/unplug the boards. There are many pins in each
board slot on the equipment motherboard. If any pin is distorted or
falls accidentally, the normal running of the entire system will be
affected, or even worse, short circuit may be caused and make the
equipment down.
Precautions in Optical Board Maintenance

Be sure to cover the unused optical interfaces of the optical interface
board with the dustproof caps. This not only protects the maintenance
persons’ eyes during their casual direct viewing on the optical ports,
but also protects optical interfaces against dust. Once dust enters the
optical interface, it may affect the output optical power of the
transmitting optical interface and the receiving sensitivity of the
receiving optical interface.
Be sure to cover fiber pigtail connectors with dust caps once unplugged.
Do not look straight into the optical interface on the optical board to
protect your eyes from being burnt by laser.
Use dust-free paper dipped in absolute alcohol to clean fiber pigtail
connectors carefully. Do not use ordinary industrial alcohol, medical
alcohol or water.
When replacing an optical board, be sure to unplug the fiber pigtails on
it before unplugging this optical board.
Precautions in Equipment Maintenance

To power on the equipment
1. Make sure the hardware installation and cable layout are correct, the
input power of the equipment satisfies the requirement, there is no
short circuit inside the equipment, and the fan installation is correct.
2. Turn on the power supply switch for the equipment in the equipment
room.
3. Set the air switch of the power distribution box to "ON" to power on
the equipment. The green indicator light at the cabinet top should light
up, the fan should run normally.

To power off the equipment
1. Set the air switch on the power distributor box to “OFF” to shut down
the equipment.
2. Turn off the power supply switch for the equipment in the equipment
room. Disconnect the input power supply of the equipment.
Warning: Powering off the equipment will make the equipment exit running state,
resulting in the interruption of all services of the NE. Since the transmission
equipment is very important in the network, power-off operation should be avoided
once the equipment is in service.
Never install or disconnect any power cables without turning off the
power switch. Otherwise, electric sparks or electric arc may occur,
causing a fire or eye hurt. Be sure to turn off the power switch before
installing or disconnecting a power cable.
Once the equipment is in service, pulling out the fan without reason is
forbidden. Clean the dust filter mesh of the fan regularly according to
the equipment room environment conditions to ensure good heat
dissipation of the equipment.
After the maintenance operations on the equipment, close the cabinet
door to ensure the equipment always has an excellent anti
electromagnetic-interference performance.
EMS Maintenance Precautions

Do not exit the EMS when the system is running normally. Exiting the
EMS will make the EMS unable to monitor the equipment, and destroy
the continuity of equipment monitoring; although it will not interrupt
services.
Assign different EMS login accounts for different users, allocate the
related operation authority to them, and periodically change the EMS
password, to ensure its security.
Do not use the EMS to dispatch services during a service peak, as any
error will impose great influence on the equipment. Dispatch services
in case of minimum traffic.
Backup data timely after a service dispatch to ensure a quick service
recovery in case of fault.
Do not play games on the EMS computer, nor copy any irrelevant files
or software to it. Kill virus regularly on the EMS computer to protect it
from virus.

Chapter 3
Routine Maintenance

Items and periods of routine maintenance
Routine maintenance operations
List of Routine Maintenance

Items
The routine maintenance items and periods of the ZXMP S385 are listed in
Table 11.
TABLE 11 LIST OF ROUTINE M AINTEN ANCE ITEMS OF THE ZXMP S385
Maintenance item Period

Environment Maintenance Daily
Check audio alarms of the equipment Daily
Observe cabinet indicator lights Daily
Equipment Observe board indicator lights 0.5 day

maintenance Check the fan, clean the air filter 2 weeks
Check orderwire telephones 2 weeks
Check services 2 weeks
EMS maintenance Manage users (change login password) Monthly
Check the EMS connection Daily
Monitor topology map Daily
Monitor alarms Daily
Monitor performances Daily
Query system configurations Irregularly
Query user operation logs Irregularly

Maintenance item Period

Print reports Irregularly
Back up data Irregularly
Environment Maintenance
The ZXMP S385 is precise electronic equipment that requires good
equipment room environment to ensure stable and reliable operation. This
section gives the equipment room environment requirements for the ZXMP
S385. The maintenance personnel should conduct regular checks on these
items, and make immediate remedies and improvements in case of non-
conformity, so as to guarantee the normal running of the equipment.
Equipment Room Temperature

Equipment room temperature requirement: 0 °C to +40 °C
In normal operating conditions, the equipment room temperature is

measured at a place 1.5 m above the floor and 0.4 m in front of the
equipment cabinet.
Equipment Room Humidity

Relative humidity requirement for equipment room: 20% to 90%
In normal operating conditions, the equipment room humidity is measured

at a place 1.5 m above the floor and 0.4 m in front of the equipment
cabinet.
Dustproof Requirements of the Equipment

Room
No explosive, conductive, magneto-conductive and corrosive dust particles
in the equipment room. Density of dust particles with diameter of more
than 5 µm should be no greater than 3×104/m3. The floor should be clean,
and windows and doors should have airproof equipment.
Clear Height
The clear height of the equipment room should be no less than 3 m.
Note: Clear height of the equipment room refers to the vertical distance from the
bottom of the beam or air duct to the upper surface of the antistatic floor.

Chapter 3 - Routine Maintenance
Wall Treatment in the Equipment Room

The surface materials on the wall and ceiling should not easily get
powdered, and should not be dirt-susceptible or flake-susceptible. The
decorative materials should be fire-retardant.
Protect wall surfaces with wallpapers or lusterless paint.
Lighting in the Equipment Room

Avoid direct sunlight. Average luminance should be 300 lx to 450 lx. The
light source should not be dizzy. Use the fluorescent lamp embedded in
the ceiling.
Prepare accident lighting or standby lighting system according to the

specific conditions of the equipment room. Install emergency light at
proper positions.
Chutes and Apertures in the Equipment

Room
All the drainage pipes should bypass the equipment room.
The quantity, location and size of reserved underground pipes, ground

chutes and apertures in the equipment room should meet the cable laying
requirement and the craft design requirements.
All the chutes should have damp-proof measures and well trimmed at the
edges and corners. Lay the lighting/ power cables in a hidden manner.
Equipment Power Supply

The ZXMP S385 uses the nominal -48 V power, with the allowed voltage
fluctuation range of -57 V to -40 V.
The routing, quantity and the layout of DC power cables installed in the
equipment room should meet the general specifications of
telecommunications projects. The conductor type (aluminum/copper bar or
rubber-skinned wire), the equipment insulation strength and the fuse
capacities should meet the design requirements.
Use complete segment cable for the power cable. No joints in the middle
of the power cable.
AC Power Supply
Prepare 220 V/2000 W AC power socket outlet in the equipment room,
since some electric tools and instruments are needed for equipment
installation, debugging and maintenance. The AC power socket outlet
should have both two-pin and three-pin multifunctional power sockets. The
socket quantities and positions should satisfy the debugging requirements
for all the equipment.

Air Conditioning System

To ensure long-term reliable operation of the ZXMP S385, the temperature
and humidity of the equipment operating environment should meet certain
requirements. If the local weather conditions cannot satisfy the
temperature and humidity requirements all the year, install air-
conditioning system in the equipment room.
Select the air condition according to the equipment heat quantity. The
formula below is generally used for heat quantity calculation.
Q = 0 . 8 2 × V × A ( K W / h o u r ) , where
Q is the equipment heat quantity
V is the DC power supply voltage (V)
A is the average current (A)
0 . 8 2 : The coefficient to transfer 1 W electric energy to heat energy is

0.86; the coefficient to transfer 1 W electric energy to heat energy in the
equipment room is 0.95. And 0 . 8 2 is the product of these two coefficients.
Calculate the actual air condition capacity according to the equipment

room area and the equipment heat quantity. Refer to related engineering
design specification documents for calculation method.
Install the air conditioning system before powering on/debugging the

ZXMP S385 equipment. Make sure that the air conditioning system works
properly.
Fire Protection Facilities

Prepare appropriate fire protection facilities in the equipment room, such
as some portable dry powder type fire extinguishers. Make sure that the
fire protection facilities can be easily seen and reached.
Large equipment rooms should be equipped with an automatic fire

protection system.
Maintenance Space
The front maintenance space of the ZXMP S385 should be greater than
800 mm.
The front maintenance space for two ZXMP S385 cabinets installed face to
face should be greater than 1000 mm.

Equipment Maintenance
Operations
Common equipment maintenance operations include audio alarm check,
cabinet indicator light observation, board indicator light observation, fan
plug-in box check, regular dustproof unit cleaning, and service check.
Audio Alarm Check

Operation Purpose
The audio alarms can attract the maintenance personnel’s attention more
easily. Make sure that the equipment can sound normally in routine
maintenance.
Operation Method
Generate alarms manually. For example, use EMS software to perform the
Alarm Inversion operation to check the alarm sound.
Inspection Criteria
When alarm occurs, the ZXMP S385 and the column head cabinet should
be able to make alarm sound.
Troubleshooting
Check if the ring interception switch is in the “Normal” state.
Check the cable connections between the alarm door panel,
“ALARM_SHOW” interface in the SCI board, and the ring trip switch.
If the alarm of the ZXMP S385 is connected externally to the column
head cabinet, check the external alarm cable connection.
Cabinet Indicators Observation

Operation Purpose
Cabinet indicator lights are used to monitor the operating status of the
equipment, and play an important role in the routine maintenance.
Regularly check if the indicator lights on the alarm panel of the column
head cabinet and the equipment work normally. Ensure that the status of
the indicator lights can properly indicate the alarm occurrences and levels.
Operation Method
Observe the status of the indicator lights on the top of the cabinet.

Inspection Criteria
When the equipment works normally, only the green cabinet indicator light
on the cabinet is on. The relationships between the cabinet indicator lights
and the equipment operating status are described below:
The indicator lights of the ZXMP S385 are located in the top middle of the
cabinet front door, including red, yellow and green lights. Table 12
describes the meanings of the indicators.
TABLE 12 MEANINGS OF THE ZXMP S385 CABINET INDICATORS
Status
Indicator Name
On Off
A critical occurs in the
Critical alarm No critical alarm in
Red light equipment, usually with an audio
indicator the equipment
alarm.
No major or minor
Yellow Major/minor A major or minor alarm occurs in
alarm in the
light alarm indicator the equipment
equipment
Green Equipment power supply is Equipment power
Power indicator
light normal supply is cut off
Troubleshooting
When the red and yellow indicator lights of the cabinet are on, further
check the board indicator lights, and notify the EMS operators at the
central site in time to check the alarm and performance message of the
equipment.
Board Indicators Observation

Operation Purpose
The status of the indicator lights on the top of the cabinet can only
indicate the latent faults of local equipment or the existing faults of the
opposite-side equipment. Therefore, further check the board indicator
lights to keep aware of the operating status of the equipment after
observing the cabinet indicator lights.
Operation Method
Observe the status of the indicator lights of the board.
Inspection Criteria
Indicator light status of the boards

When the board works normally, only the green indicator light flashes.
The indicator light status of the ZXMP S385 common boards are
described below.
NE Control Processor (NCP)

Correspondences between the working status and the indicator
light status of the NCP board are listed in Table 13.
TABLE 13 CORRESPONDENCES BETWEEN THE WORKING STATUS AND THE INDICATOR

LIGHT STATUS OF THE NCP BOARD
NCP Working Indicator Light Status

Status Green NOM light Yellow ALM1 light Red ALM2 light Green MS light
Working normally Flashes Off Off -
NE major or
Flashes On - -
minor alarm
NE critical alarm Flashes - On -
Active Flashes - - On
Note: The NCP board transmits the running and monitor information between the
NE and EMS. Its indicator light status also indicates the running status of the
current NE. The NCP board alarms are mainly caused by the alarms reported by
other boards.
Orderwire (OW) board

light status of the OW board are listed in Table 14.

LIGHT STATUS OF THE OW BOARD
Indicator Light Status

Working Status
Green NOM Light Yellow ALM1 Light Red ALM2 Light
Working normally Flashes Off Off
Off-hook Flashes On -
Board alarm Flashes - On
Cross-connect and clock board (CSA/CSE)

light status of the CSA/CSE board are listed in Table 15.


L I G H T S T A T U S O F C S A/ C S E B O A R D

Working Status Green NOM Yellow ALM1 Red ALM2 Green CKS1 Green CKS2 Green MS Green TCS
Light Light Light Light Light Light Light
Working normally Flashed Off Off - - - -
Board major or
Flashed On - - - - -
minor alarm
Board critical
Flashed - On - - - -
alarm
Clock is in locked
mode (normal Flashes Off Off On On - -
tracing)
Clock is in hold
Flashes - - On Off - -
mode
Clock is in fast
Flashes - - Off On - -
capture mode
Clock is in free-
Flashes - - Off Off - -
oscillation mode
Active CSA/CSE Flashes - - - - On -
Standby CSA/CSE Flashes - - - - Off -
TCS in position Flashes - - - - - On
TCS in position
and working Flashes - - - - - Flashes
normally
STM-1 Line Processor (LP1)

light status of the LP1 board are listed in Table 16.

LIGHT STATUS OF THE LP1 BOARD

Working Status Green NOM Yellow ALM1 Red ALM2 Green TX Green RX
Light Light Light Light Light
Working normally Flashes Off Off - -
Board alarm Flashes - On - -
Corresponding interface
Flashes - - On On
working normally
Bit errors occur to the
Flashes - - Flashes Flashes
corresponding interface
Corresponding interfaces
Flashes - - Off Off
have no signal

Electrical Tributary Board (EPE1/EPT1/EP3)

light status of electrical tributary boards are listed in Table 17.

LIGHT STATUS OF ELECTRICAL TRIBUTARY BOARDS

Working Status
Green NOM Light Yellow ALM1 Light Red ALM2 Light
Working normally Flashes Off Off
Board alarm Flashes - On
Optical Line Boards (OL1/OL4/OL16/OL64)

light status of the optical line boards are listed in Table 18.

LIGHT STATUS OF THE OPTICAL LINE BOARDS

Corresponding optical
Flashes - - On On
interface working normally
Bit errors occur to the
corresponding optical Flashes - - - Flashes
interface
LOS occurs to the
corresponding optical Flashes - - - Off
interface
The corresponding optical
Flashes - - Off -
interface laser is off
Ethernet Boards (TGE2B/MSE/SEC)

light status of the TGE2B/MSE board are listed in Table 19.


LIGHT STATUS OF THE TGE2B/MSE BOARD

Working Status Green NOM Yellow ALM1 Red ALM2 Green LA Green SD
Corresponding GE optical
interface connects Flashes - - On
successfully
Corresponding GE optical
interface receives optical Flashes - - - On
signal

light status of the SEC board are listed in Table 20.

LIGHT STATUS OF THE SEC BOARD

Working Status Green Yellow Red ALM2 Green Green Green Green
NOM Light ALM1 Light Light LAn Light SPn Light LA Light SD Light
Corresponding FE
optical interface is Flashes - - On -
in Link status
Corresponding FE
optical interface is Flashes - - Flashes -
in Active status
The rate of the Flashes - - - On - -
corresponding FE
optical interface is
100 M
GE optical interface Flashes - - - - On -
is in Link state
GE optical interface Flashes - - - - Flashes -
is in Active state
GE optical interface Flashes - - - - - On
receives optical
signal
Optical Amplifiers (OA)

light status of the optical amplifier boards are listed in Table 21.


LIGHT STATUS OF OPTICAL AM PLIFIER BOARDS

Flashes - - On On
interface working normally
Flashes - - - Off
interface has LOS alarm
Laser at corresponding
Flashes - - Off -
optical interface is cut off
Indicator light status of boards in a 1:N protection group

For the active/standby boards in a protection group, the yellow
indicator lights light up when protection switching occurs. The yellow
indicators turn off after the protection switching is cancelled.
For interface bridge boards, the green indicator light is constantly on

after the boards are powered on.
For the electrical interface switching boards, the green indicator light is
constantly on and the yellow light is off after the boards are powered
on. The yellow light lights up when the switching occurs, and it turns
off when the switching is cancelled.
Troubleshooting
When the red/yellow indicator light of the board is on, notify the EMS
operators at the central site in time to check the alarm/performance
message of the equipment and board.
Fan Check
Operation Purpose
Good heat dissipation function is critical for long-term normal running of
the equipment. Make sure the fan is working normally when the
equipment is running.
Therefore, it is necessary to check the working status and cooling function

of the fan periodically.
Operation Method
Observe the working status of the fan, and execute the Fan Config
command in the EMS software to query the configuration information of
the fan.

Inspection Criteria
The fan runs stably at regular rotation speed, and buzzes continuously
without abnormal sound.
Troubleshooting
If the fan rotates at irregular speed or has abnormal sound, check
immediately whether foreign substance exists in the fan box, and
whether the fan is damaged.
If the fan does not run, check immediately if the fan in the plug-in box
is damaged.
Dustproof Unit Cleansing

Operation Purpose
After the equipment runs for a long time, dust may block the dustproof
unit at the lower part of the fan plug-in box, thus results in bad heat
dissipation and may even damage the equipment. Therefore, it is
necessary to clean the dustproof unit periodically.
Operation Method
Take out the air filter from the lower part of the dustproof unit and check
it.
Inspection Criteria
The air filter of the dustproof unit is free from accrued dust.
Trouble Shooting
Clear away the accrued dust of the air filter by using clean water to scrub
the air filter and air-dry it before inserting it back to the lower part of
dustproof unit.
Orderwire Phone Check

Operation Purpose
Being an important communication tool for the network maintenance
personnel in troubleshooting, orderwire telephone plays a special role in
system maintenance. Therefore, some routine checks on them are
necessary to ensure smooth orderwire calls.
Operation Method
If the local site is not a central site, make orderwire calls periodically
from the local site to the central site, and request the central site to
dial back, so as to test the orderwire telephone.

The central site should make orderwire calls periodically to other sites
in turn to check the orderwire telephones.
Inspection Criteria
The orderwire calls get through among every site and can be clearly heard
without noise.
Troubleshooting
Use other method to check if the called site has ringed off.
If the called site has ringed off, check the configured data and
performance/alarm message through the EMS software, to find out the
problem and solve it.
Service Inspection – Bit Error Test

Operation Purpose
Bit error characteristic test is a test on the long-term stable running
performance of the entire transmission network. During the routine
maintenance, make periodical sampling test on traffic channels, on
condition that no current operating service is affected, so as to check if the
performances of all the traffic channels are normal.
Operation Method
In respect of idle traffic channels between two sites, the test can be
performed on the idle channels to test the traffic channel quality
between two sites.
If there is no idle traffic channel between two sites, a traffic channel
originally used for protection can be temporarily disconnected, when
the traffic is small, for accepting an error test and checking the quality
of traffic channels between the two sites.
If both of the above two circumstances are not applicable, use the EMS
software to query the service performance and alarms, and make sure
of the quality of traffic channels between the two sites.
Note: Refer to Bit Error Test section for detailed operations of bit error test.
Inspection Criteria
No bit error exists on any traffic channel.
Troubleshooting
When there is bit error in the traffic channel, refer to Bit Error Fault
section in Chapter 6 for troubleshooting.

Routine EMS Maintenance

Operations
The NE Management System (EMS) is an important tool for routine
maintenance. To ensure that the equipment runs safely and reliably, the
maintenance personnel at the EMS site should check the running status of
the equipment through the EMS everyday.
This section briefly introduces the EMS maintenance operations. Refer to

the related EMS software manuals for more details.
User Management
Operation Purpose
In order to prevent illegal access to the EMS software and ensure normal
running of equipment and service security, it is necessary to change the
login password of the EMS users periodically, and assign proper authorities
to the EMS operators.
Operation Method
The EMS software provides four levels of users: system administrator,
system maintainer, system operator and system monitor. Each level of
user has specific operation authorities. Assign unique username,
password and management objects for each EMS operator, and assign
different user levels according to the specific operation authorities of
each user.
Change the login password of the EMS operators periodically.
Note: Since the system administrators possess all the operation authorities, if they
login to the EMS and perform any improper operation, it may cause severe
consequences. Therefore, in routine maintenance, it is not recommended for the
user to log into the EMS as a system administrator. Instead, a system monitor
user should be created, and used to log into the EMS for routine maintenance.
Inspection Criteria
The EMS operators should be able to log in to the EMS with an
assigned username, and have the assigned operation authorities.
The EMS operators should be able to change the login password
periodically.
Troubleshooting
If the EMS operators have wrong operation authorities or cannot
change the password, they should request the system administrator to
check the user configuration data or reset the user authorities and
password.

To troubleshoot faults of EMS connections, refer to EMS Connection

Fault.
Connection with the EMS

Operation Purpose
Check the connection between the equipment and the EMS in order to
make sure that the EMS software can reflect the running conditions of the
equipment timely and accurately, and to ensure that the EMS software
performs effective monitoring on the equipment.
Operation Method
Log in to the EMS and check the NE ID.
Inspection Criteria
The EMS can be logged in normally, and the screen of the computer
marked in the EMS is blue.
The NE icon is not grey. It should be green representing for normal
running, or other colors representing for certain alarm levels. The
default relationships between icon colors and alarms are listed in Table
22.
TABLE 22 THE DEFAULT RELATIONSHIPS BETWEEN ICON COLORS AND AL ARMS
Alarm Level NE Icon Color

Critical alarm Red
Major alarm Orange
Minor alarm Yellow
Warning Purple
The icon frame is purple, and the icon
Warning confirmed
inside is green
Unreliable alarm Blue
The grey NE icon indicates that the NE is offline or loses connection

with the EMS.
The green NE icon indicates that the communication between the
NE and EMS is normal and there is no alarm.
If the NE icon is in some color of certain alarm level, it indicates
that the communication between the NE and EMS is normal, but
alarm exists. The NE icon color indicates the highest level of alarms.
Troubleshooting
To troubleshoot faults of EMS connections, refer to EMS Connection Fault
section in Chapter 6.

Topology Map Monitoring

Operation Purpose
In the ZXONM E300 EMS software, audible and visual alarms are provided.
The user can monitor the running status of the current subnet and NE
through the navigation tree, topology map, NE icon and the NE installation
window; and can judge the alarm level through the sound or color given
with the alarm.
Operation Method
In the client operation window of the EMS software, check the NE icon in
the navigation tree and the topology map.
Inspection Criteria
The NE icon is not grey. It should be green representing for normal
running, or other colors representing for certain alarm levels. The
default relationships between icon colors and alarms are listed in Table
22.
The grey NE icon indicates that the NE is offline or loses connection
with the EMS.
The green NE icon indicates that the communication between the
NE and EMS is normal and there is no alarm.
If the NE icon is in some color of certain alarm level, it indicates
that the communication between the NE and EMS is normal, but
alarm exists. The NE icon color indicates the highest level of alarms.
The solid line between two NEs indicates that the optical connection is
normal. And the dotted line indicates that the optical connection is
broken.
Troubleshooting
To troubleshoot faults of EMS connections, refer to EMS Connection
Fault section in Chapter 6.
When alarm indicator exists on the NE icon, query the alarm details via
the current alarm monitoring dialog box or monitoring window. For the
handling of alarm message, refer to Common Alarm Messages and
Solutions.
If the line indicative of the optical connection is a dotted line, check the
corresponding optical cable and fiber pigtail.
Note: The EMS software can perform monitoring and management only on the NEs
that are in a status of normal communication with the EMS host.

Alarm Monitoring
Operation Purpose
In the ZXONM E300 EMS software, the user can monitor the alarm
message of the NE; thus keep aware of the current working status of the
NE, and detect/handle the alarm message of the NE in time.
Operation Method
In the client operation window of the EMS software, open the
monitoring window to monitor the alarm message of all NEs in real
time.
In the client operation window of the EMS software, query the current
or history alarm message of the NEs.
Inspection Criteria
The NE has no current alarm message.
The NE has no unconfirmed history alarm message.
Troubleshooting
To troubleshoot faults of EMS connections, refer to EMS Connection Fault
section in Chapter 6.
To handle the alarm message, refer to Chapter 5.
Performance Monitoring
Operation Purpose
In the ZXONM E300 EMS software, the user can monitor the performance
message of the NE; thus keep aware of the current service performance of
the NE, and detect/handle the performance message of the NE in time.
Operation Method
In the client operation window of the EMS software, query the latest
performance data of the NE within 15 minutes and 24 hours.
Inspection Criteria
The NE has no performance over-threshold event.
Troubleshooting
For the handling of performance message, refer to Chapter 4.

System Configuration Query

Operation Purpose
In the ZXONM E300 EMS software, the user can query the configuration
information of the network through the configuration menus. The result of
this query is the network configuration in the EMS software, not
necessarily the actual configuration of the NE. To obtain the actual
configuration and current working status of the NE, the user need to
perform the operations such as uploading data, obtaining the current
status, and querying the switching information.
Operation Method
In the client operation window of the EMS software, query the current
network configuration information.
Query the current configuration data of the NE.
Query the switching information of the NE.
Inspection Criteria
The current network/NE configurations agree with the actual
networking.
There is no switching event.
Troubleshooting
If the current network/NE configurations conflict with the actual
networking:
If the current service meets the user requirements, the network
configuration data should be corrected to comply with the actual
networking.
If the current service does not meet the user requirements, the
network configuration data should be corrected to comply with the
user requirements.
For the handling of switching events, refer to Chapter 4.
Querying User Operation Logs

Operation Purpose
The ZXONM E300 EMS software can record all the operations performed by
the user into the user operation log. It is one of the security guarantees.
Query the user operation log periodically; and check whether there is any
illegal access and any improper operation affecting the system running.
Operation Method
In the client operation window of the EMS software, query the user
operation log.

Inspection Criteria
No illegal login.
No user operations affecting system operation or service functions.
Troubleshooting
When any illegal user or operation is found, use the user management
function of the EMS software to check the user identity and the authority
settings, and change the user password in time.
Report Printing
Operation Purpose
With the printing function of the EMS software, the user can print out the
network configuration, user operation log, equipment performance and
alarm message. The printed reports are a basis for operation/maintenance
records and network analysis.
Operation Method
Print the reports in the client operation window of the EMS software.
Inspection Criteria
None
Troubleshooting
If the ZXONM E300 on Windows platform cannot print reports, check
whether the Report Server is started up. The Report Server can be started
up through the Windows menu of Startup-> Programs-> ZXONM E300
-> Report Server.
Data Backup
Operation Purpose
In the ZXONM E300 EMS software, database backup is primarily used to
copy and save the data of the Manager database. In the network operation
& maintenance, it is necessary to backup the system data often so that
the network data is quickly recoverable in case of network fault and EMS
data loss.
Operation Method
In the client operation window of the EMS software, perform the operation
of data backup.
Note: It is recommended to save the backup data in a mobile storage device lest
backup loss in case of hard disk fault of the EMS host.

Inspection Criteria
None
Troubleshooting
None
Data Recovery
Operation Purpose
In case of network fault or EMS data loss, use the ZXONM E300 EMS
software to recover the data that is backed up at the EMS database side.
The recovery implemented by the ZXONM E300 covers all the current data.
Operation Method
In the client operation window of the EMS software, perform the operation
of data recovery.
Inspection Criteria
None
Troubleshooting
None

Chapter 4
Performance Message and

Handling

List of performance messages of the ZXMP S385
Detailed causes, influence and troubleshooting methods of various
performance events
Performance Message
Categories
Performance messages of the ZXMP S385 include SDH interface
performance messages, equipment analog performance messages, and
Ethernet port performance messages.
SDH Interface Performance Messages

Detectable SDH interface performance message of the ZXMP S385 are
listed in Table 23.
TABLE 23 LIST OF SDH INTERFACE PERFORM ANCE MESSAGES
Performance
Detection Point Description
Message
2 Mbit/s PDH physical
CV Coding Violation
interface
BBE Background Block Error
ES Errored Second
Regenerator section SES Severely Errored Second
UAS Unavailable Second
OFS Out-of-Frame Second

Performance
Detection Point Description
Message
ES Errored Second
SES Severely Errored Second
Multiplex section
FEBBE Far End Background Block Error
FEES Far End Errored Second
FESES Far End Severely Errored Second
FEUAS Far End Unavailable Second
ES Errored Second
Higher-order path UAS Unavailable Second

VC3/VC4 FEBBE Far End Background Block Error
ES Errored Second
Lower-order path UAS Unavailable Second

VC12 FEBBE Far End Background Block Error
Administrative unit AU4 PJE+ AU4 Pointer Justification E+

AU AU4 PJE- AU4 Pointer Justification E-
TU3 PJE+ TU3 Pointer Justification E+
Tributary unit TU3
TU3 PJE- TU3 Pointer Justification E-
TU12 PJE+ TU12 Pointer Justification E+
Tributary unit TU12
TU12 PJE- TU12 Pointer Justification E-

Chapter 4 - Performance Message and Handling
Analog Performance Messages

Table 24 lists detectable analog performance messages of the ZXMP S385.
TABLE 24 LIST OF AN ALOGUE PERFORMANCE MESSAGES
Detection Point Performance Message Unit

Input optical power dBm
STM-1 to STM-64
Output optical power dBm
optical interfaces
Working current of laser mA
Board Detection point temperature °C
Ethernet Interface Performance Messages

Table 25 lists the SDH performance messages detectable by the
Ethernet board of the ZXMP S385.
TABLE 25 SDH PERFORM ANCE MESSAGES DETECTABLE BY ETHERNET BOARD
Detection Performance
Description
Point Message
ES Errored Second
CSES Consecutive Severely Errored Second
VC4/VC3/ UAS Unavailable Second

VC12/VC11 FEBBE Far End Background Block Error
FCSES Far-end Consecutive Severely Errored Second
PJC+ Positive Pointer Justification Count
AU4
PJC- Negative Pointer Justification Count

Table 26 lists the analogue performance messages detectable by the

Ethernet board of the ZXMP S385.
TABLE 26 ANALOGUE PERFORM ANCE MESSAGES DETECTABLE BY ETHERNET BOARD
Detection Point Performance Message Unit

o
The average temperature of the detection point C
o
Board The maximum temperature of the detection point C
o
The minimum temperature of the detection point C
Table 27 lists the data performance messages of the ZXMP S385

Ethernet board.
TABLE 27 DATA PERFORM ANCE MESSAGES OF THE ZXMP S385 ETHERNET BOARD
Detection
Performance Message Description
Point
Receive Undersize Frames Number of received undersize frames
Receive Oversize Frames Number of received oversize frames
Receive CRC Error Frames Number of received CRC errored frames
Receive Discard Frames Number of received discarded frames
Receive Frame Bytes Number of received frame bytes
Receive Flow Control Frames Number of received flow control frames
Receive Broadcast Frames Number of received broadcast frames
Receive Frames with Length of 64 Bytes Number of received frames with length of 64 bytes
Receive Frames with Length between 65 Number of received frames with length between 65
Bytes~127 Bytes bytes~127 bytes
Receive Frames with Length between 128 Number of received frames with length between
Bytes~255 Bytes 128 bytes~255 bytes
Receive Frames with Length between 256 Number of received frames with length between
Bytes~511 Bytes 256 bytes~511 bytes
VCG (EOS) Receive Frames with Length between 512 Number of received frames with length between
por Bytes~1023 Bytes 512 bytes~1023 bytes
Receive Frames with Length between Number of received frames with length between
1024 Bytes~1522 Bytes 1024 bytes~1522 bytes
Receive Unicast Frames Number of received unicast frames
Send Bytes Number of sent bytes
Send Unicast Frames Number of sent unicast frames
Send Flow Control Frames Number of sent flow control frames
Send Multicast Frames Number of sent multicast frames
Send Broadcast Frames Number of sent broadcast frames
Send Delay Exceed Frames Number of sent delay exceed frames
Send Delay Collision Frames Number of sent delay collision frames

Detection
Performance Message Description
Point
VCG (EOS) Send Frames with One Collision Number of sent frames with one collision
port
Send Frames with More Collisions Number of sent frames with more collisions
Receive GFP Control Frames Number of received GFP control frames
Receive GFP CHEC Error Frames Number of received GFP CHEC error frames
Receive GFP THEC Error Frames Number of received GFP THEC error frames
Receive GFP EHEC Error Frames Number of received GFP EHEC error frames
Receive GFP FCS Error Frames Number of received GFP FCS error frames
Receive GFP Frame Bytes Number of received GFP frame bytes
Receive GFP User Data Frames Number of received GFP user data frames
Receive GFP Idle Frames Number of received GFP idle frames
Number of received GFP client management
Receive GFP Client Management Frames
frames
Send GFP Data Frames Number of sent GFP data frames
Send GFP Idle Frames Number of sent GFP idle frames
Send GFP Client Management Frames Number of sent GFP client management frames
Send GFP Frame Bytes Number of sent GFP frame bytes
Receive GFP Dropped Frames Number of received GFP dropped frames
Receive PPP/HDLC Frames Number of received PPP/HDLC frames
Receive PPP/HDLC Frame Bytes Number of received PPP/HDLC frame bytes
Receive PPP/HDLC Dropped Frames Number of received PPP/HDLC dropped frames
Receive PPP/HDLC FCS Error Frames Receive PPP/HDLC FCS error frames
Receive PPP/HDLC Aborted Frames Number of received PPP/HDLC aborted frames
Send PPP/HDLC Frames Number of sent PPP/HDLC frames
Send PPP/HDLC Frame Bytes Number of sent PPP/HDLC frame bytes
Physical Interface Performance

Events and Solutions
Overview
The performance detections of the 1.5 M, 2 M, 34 M, and 45 M physical
interfaces are implemented via Coding Violation (CV), which detects the
electrical signal codes.
The 2 M, 34 M, and 45 M signals of the ZXMP S385 employ HDB3 code.

When the equipment detects signal code error, it will report CV to the EMS.

Event Causes
The causes of CV are similar for electrical signals of different rates. Taking
the commonly used 2 M signal as example, the possible causes include:
Poor performance of the interface of the tributary board.

At the moment of plugging/unplugging the interface cable, a slight CV
count will be generated at the tributary port.
Poor welding or splice of the cable.
Inferior cable.
If almost all the tributaries report CV, the cause may be that the
switch and transmission equipment do not have the common ground.
Influence on Equipment
If CV values are small, only a few or no CVs occur in 15 minutes, or
just a few are reported in 24 hours, it will impose no influence on the
service.
If CV values are large in 15 minutes and they keep increasing, the
service may be affected, and voice noise or illegible characters of data
may occur, even with the possibility of service interruption.
If significant CV values burst out, the service will be interrupted
instantly.
Solutions
Isolate the switch equipment from the transmission equipment. Use a
bit error tester to test the corresponding clear transmission channel of
the two equipment respectively, and check whether the CV is reported
from the switch equipment or transmission equipment.
If the CV is reported from the transmission equipment, cut off the
service connection of this channel, find out the NE reporting this CV
through the EMS, and locate the fault. There are different solutions to
different causes:
If the CV is caused by the interface performance of the 2 M
tributary board, it can be judged through hardware loopback.
Replacing the tributary board will probably solve the problem.
If the CV is caused by poor cable connection, weld or splice the
cable again.
If the CV is caused by inferior cable, replace the cable.
If the CV is caused by poor grounding, it is usually because the
service interface ground cables of the equipment are designed
differently by different manufacturers. To solve this problem,
remake the ground cable, or connect a capacitor in series at the
originating core. The capacitor can be 0.1u to 1u Tantalum.

Warning: In the ZXMP S385 equipment room, the case of the cable distribution
frame should connect with the protection ground. The grounding resistances of
both the protection ground and the DC working ground should be less than 1 Ω.
If the CV is reported from the switch equipment, refer to the user

manual of switch equipment, or refer to the solutions to the CV
reported from transmission equipment.
During normal running of the equipment, the user can connect the bit
error tester at idle transmission channels to test for 24 hours and
select those with good performance as standby transmission channels.
When a large number of CVs burst out, the services can be switched to
these standby transmission channels.
Regenerator Section
Performance Events and
Solutions
Overview
The regenerator section performance events are detected via the B1 byte,
which is the regenerator section overhead byte. B1 byte uses 8 bits for
parity check. It is detected and terminated at the receive NE, and will not
be transferred to the next NE.
Event Causes
External causes: The fiber connectors are dirty or connected
improperly. The fiber has deteriorated performance and incurs a high
loss.
Equipment causes: Inferior quality of the receiving and transmitting
optical modules of the optical line board, the CSA/CSE board, or the
clock.
Man-made causes: Somebody inserted bit errors at the regenerator
section using EMS software, and did not delete them.
In case of sporadic and minor bit errors, which occur regularly, several
times in 24 hours, or once in a few days, or occur continuously,
averaging one BBE per errored second, they generate no low-level bit
errors, and impose little influence on the service.

In case of major bit errors, which occur regularly, several times in 24

hours, or once in a few days, averaging at least 5 BBEs per errored
second, occasionally with transient out-of-frame alarms (lasting for 5
to 6 seconds) and OFS count, they will result in B2 and B3 bit errors,
and impose influence on all services. Especially, they will cause
transitory mosaic or frame suspension of the video service, but they
are scarcely perceptible in the telephone or data services.
In case of burst of continuous major bit errors, the system will report
performance over-threshold alarm along with out-of-frame alarm, the
unavailable time will begin, and transient interruption of services will
occur frequently.
Solutions
Perform the line-side self loopback of the optical interface at the local
equipment, and adjust the insertion depth of the fiber properly. If the
alarm disappears, the alarm cause lies in too strong or too weak
optical power.
In case of too strong optical power, add an attenuator into the line
to adjust it.
In case of too weak optical power, cleanse the fiber pigtail and
connect it again, or replace the optical modules which have strong
optical launched power.
If it is caused by inferior optical line board or CSA/CSE board, replace
the board.
If it is caused by bit errors inserted in the EMS software, delete the bit
errors in the EMS, and issue the command.
Multiplex Section Performance

Events and Solutions
Overview
Multiplex section performance events are detected by the multiplex section
(MS) overhead B2, K1 and K2 bytes. K1/K2 bytes are used for MS-PSD
and MS-PSC performance events, and B2 is used for monitoring MS bit
errors.
The MS bit errors detection use three B2 bytes, i.e., 24 bits, for parity
check. MS bit errors will not be transferred to the next NE. The receiving
NE which deals with the MS overhead will terminate MS bit errors, and
send the remote alarm message back to the transmitting NE at the same
time. Since REG equipment does not deal with MS overhead, B2 byte will
not be changed by REG and will be sent to the next NE. However, since
the ADM and TM equipment deal with the MS overhead, they will terminate
B2 byte, restart parity check counting, and send the remote alarm
message to the transmitting NE.

Note: Remote alarm message is a message returned by the receiving end to the
transmitting end as an acknowledgement, so that the transmitting end can know
about the bit error status of the receiving end.
For B2, its remote alarm message byte is the M1 byte in the MS overhead,
i.e., the MS remote block error indication byte. After the receiving NE
detects the B2, it will store the performance value of B2 into the M1 byte,
and send it back to the transmitting NE. After the transmitting NE detects
the M1, it will report the M1 value (B2 FEES/FEBBE/FESES/FEUAS).
Therefore, the B2 FEBBE/FEES/FESES/FEUAS of the transmitting NE
always accompanies the B2 BBE/ES/SES/UAS of the receiving NE.
Event Causes
Possible causes of the MS performance events include:
B1 bit error can result in B2 bit error. The causes are the same as B1
bit error. Refer to Regenerator Section Performance Events and
Solutions section.
Damaged optical line board.
Somebody inserted MS bit errors using the EMS software, and did not
delete them.
MS switching event occurs in the network.
If B2 bit errors are few, they impose little influence on the system.
When the performance keeps deteriorating and the bit errors cross the
performance threshold, the performance over-threshold alarm will be
reported.
If the EMS reports the out-of-frame alarm and the B2 performance
over-threshold alarm concurrently, the MS switching will occur for the
network configured with the MS protection, and MS-PSD and MS-PSC
start to count. In case of normal switching, MS-PSC count is an even
number; in case of switching back, the MS-PSD count is cleared to zero,
waiting for recount at the next switching.
Solutions
If B2 bit error occurs along with B1 bit error, solve B1 bit error first.
For how to handle B1 bit error, refer to Regenerator Section
Performance Events and Solutions section.
If B2 bit error is caused by bit errors inserted in the EMS software,
delete the bit errors in the EMS, and issue the command.
When MS switching events occur in the network, if the MS-PSC count is
an odd number, follow the steps below:
Check whether these problems occur in the network: unplugged or
faulty NCP board, self loopback of optical interface, protection
configuration error, suspended APS, inconsistent APS-ID,

inconsistent switching control command, and abnormal transmitting

of the K byte between the protection optical line board pairs.
If such problems exist, solve them first. If they do not exist, issue
the Reset APS command to all the points in the MS ring to solve
the problem.
Higher-Order Path Performance

Event and Solutions
Overview
Higher-order path performance events are detected by the higher-order
path overhead B3 byte. The B3 byte monitors the bit error performance of
VC4 transmitted in the STM-N frame. It uses 8 bits for parity check on the
higher-order path. The B3 byte is originated by the transmitting NE of the
path, and transparently transmitted through the ZXMP S385 in the path,
without being processed. It is terminated at the termination NE of the
whole path.
The remote alarm byte of B3 bit error is the higher-order path overhead
G1. G1 sends the status and performance message of the terminal in the
path back to the VC4 path source equipment, so as to enable monitoring
on the status and performance of the whole bidirectional path at any end
or any point of the path. The B3 BBE/ES/SES/UAS of the NE occurs along
with the B3 FEBBE/FEES/FESES/FEUAS of the opposite NE.
Event Causes
B3 bit errors usually occur along with B1 and B2 bit errors. Its possible
causes are:
External causes: The optical power is too strong or too weak.

Equipment causes: The optical line board or the CSA/CSE board is
faulty.
Man-made causes: Somebody inserted bit errors in the higher-order
path using EMS software, and did not delete them.
If B3 bit errors are few, they will impose little influence on the equipment.
If the performance keeps deteriorating, and the B3 bit errors cross the
threshold, the B3 bit error performance over-threshold alarm will be
reported, and the transmission quality of the path will deteriorate.

Solutions
First, check whether the B1 or B2 bit errors exist. If they exist, handle
as described in Regenerator Section Performance Events and Solutions,
and Multiplex Section Performance Events and Solutions.
If no B1 or B2 bit error exists, find the starting point of the B3 bit error
in the path where the B3 bit error is reported. After resolving the B3
bit error at the starting point, find the next starting point of B3 bit
error along the path. Carry on until all the bit errors are solved.
Lower-Order Path Performance

Event and Solutions
Overview
Lower-order path performance events are detected by the lower-order
path overhead V5 byte. The first and second bits of V5 byte employ two-
bit parity check to monitor the bit error of the lower-order path. And the
third bit of V5 byte is the indicator of the remote bit error on the lower-
order path, sending the bit error number detected by the receiving NE
back to the transmitting NE. The lower-path performance is transferred
and has the remote alarm message. Therefore, the B3 BBE/ES/SES/UAS of
the NE occurs along with the B3 FEBBE/FEES/FESES/FEUAS of the
opposite NE.
Event Causes
The possible causes of V5 bit errors are:
Bit errors of regenerator or multiplex section.

Tributary board faults.
Somebody inserted bit errors in the lower-order path using EMS
software, and did not delete them.
If V5 bit errors are few, they will impose little influence on the equipment.
If the performance keeps deteriorating, and the V5 bit errors cross the
threshold, the performance over-threshold alarm will be reported, and the
transmission quality will deteriorate.

Solutions
If V5 bit error is caused by bit errors of regenerator or multiplex
section, and the B1/B2/B3 bit errors exist, handle B1/B2/B3 bit errors
first. Refer to the solutions described in Regenerator Section
Performance Events and Solutions section, Multiplex Section
Performance Events and Solutions section, and Higher-Order Path
Performance Event section.
If it is caused by tributary board faults, replace the tributary board.
Pointer Justification Performance

Event and Solutions
Overview
In the SDH frame structure, several bytes at specific positions are used to
record the starting position of the data information in the SDH frame. Such
bytes are used to represent the phase of the data information, they are
called pointer.
When the network is in synchronous working status, pointers are used for
phase alignment between synchronous signals. When the network is out of
synchronization, the frequency and phase can be aligned through pointer
justification. Depending on the running speed of the NE clocks carried by
various signals, pointer justification can be divided into positive pointer
justification and negative pointer justification. The pointer justification
byte is detected and terminated at the receiving NE, and will not be
transferred to the next NE.
During the multiplexing and mapping of SDH, three types of pointers are
involved: AU-4, TU-12, and TU-3.
The AU-4 pointer locates at the first nine bytes of the fourth line in the
SDH frame structure, and is used for determining the starting position
of VC-4 in the AU.
The TU-3 pointer locates in the TUG-3. It has a total of nine bytes to
determine the starting position of VC-3 in the TU-3.
The TU-12 pointer has three bytes in total to determine the starting
position of VC-12 in the TU-12.
Event Causes
External causes: The clock is unlocked, or the clock source is of poor
quality; or the CSA/CSE board and the optical line board are worn
away after long-term running.

Equipment causes: The CSA/CSE board and the optical board are faulty.
For TU-3/TU-12, tributary board fault can also cause pointer
justification.
EMS causes: Manually forced switching command is not cancelled; or
there are configuration errors of clock source.
Note: The AU4 pointer justification may result in TU3/TU12 pointer justification
events.
A pointer justification event indicates that there is problem of network
synchronization. Slight point justification events impose little influence
on the equipment. Major pointer justification events indicate symptoms
such as unlocked clock, which mean that the service quality is at risk.
Major pointer justifications should be handled immediately.
If the network is out of synchronization and keeps deteriorating, when
the pointer justification value crosses the threshold, the EMS will report
the corresponding performance over-threshold alarm.
Solutions
Handling AU4 Pointer Justification Event
If the clock is unlocked, check whether the clock switches. If the clock
does not switch, the event may be caused by fault/wear-down of
optical line board or CSA/CSE board. Replace the corresponding boards.
If the clock switches, check the configuration of the clock source,
especially the data configuration, clock source level configuration, clock
source extraction configuration and the setting of clock switching rules.
If the clock source configuration is correct, check the hardware fault of
the switched clock source. If hardware fault exists, replace the
corresponding board.
If the external clock is unlocked, follow the above three steps to locate
the fault and solve it.
If poor clock lock quality results in the pointer justification event, it
may be caused by faulty optical board or CSA/CSE board. Replace the
corresponding faulty board.
Handling TU3 Pointer Justification Event

If TU-3 pointer justification event concurs with AU-4 pointer justification
event, solve the AU-4 pointer justification event first.
Handling TU12 Pointer Justification Event

If TU-12 pointer justification event concurs with AU-4 pointer
justification event, solve the AU-4 pointer justification event first.

If it is caused by fault of 2 M electrical tributary board, replace the

corresponding board.

Chapter 5
Alarm Message and Handling

Overview of alarm messages.
Detailed causes and troubleshooting methods of common alarm
messages.
Overview of Alarm Message

This section describes the categories, severity levels, and priorities of
alarm messages.
Alarm Categories
Communication alarm: The alarm which directly affects the service
layer, and indicates that the communication signals are interrupted or
deteriorated at a certain layer.
Synchronization alarm: The alarm for clock-related faults.
Equipment alarm: The alarm directly caused by internal fault of the
equipment, including power failure, board fault, board out-of-position,
and inconsistency between the EMS configuration and the hardware
installed on the equipment.
Alarm Levels
Alarms can be classified into four severity levels: critical, major, minor,
and warning alarms, which are in order from higher severity to lower
severity. Every alarm message has a default severity. The user can modify
the alarm level in the EMS as required.
Alarm Priorities
Alarm priorities of the transmission equipment are as the follows:

Communication interruption alarms have higher priorities than

communication bit error alarms.
Regenerator section alarms have higher priorities than multiplex
section alarms.
Multiplex section alarms have higher priorities than higher-order path
alarms.
Higher-order alarms have higher priorities than lower-order path
alarms.
A higher-priority alarm will result in lower-priority alarms. Therefore, when
a fault occurs, it is necessary to handle the higher-priority alarm first, and
then observe whether the lower-priority alarms disappear. If they do not
disappear, handle them accordingly; if they disappear, it means they
result from the higher-priority alarm.
Alarm Summary
Table 28 lists the possible SDH alarm messages of the ZXMP S385.
T AB L E 2 8 S DH AL AR M M E SS AG E S O F T H E Z X M P S 3 8 5
Alarm Alarm
Alarm Message Alarm Level
Category Detection Point
Loss of optical received signal Critical
SDH optical Optical launched power over-threshold Major

interface Optical received power over- threshold Major
Laser bias current over-threshold Minor
SDH electrical
Loss of Signal (LOS) Critical
interface
PDH electrical Loss of Signal (LOS) Critical

interface PDH alarm indication signal Major
Loss of frame Critical
Out of frame Critical
Communication Unavailable time Major
alarms
DCCR connection failure Major
Regenerator Regenerator section signal degraded Minor
section
Regenerator section alarm indication signal
Major
(AIS)
Trace identifier mismatch of regenerator
Major
section
Regenerator section BER over-threshold Major
Alarm indication signal (AIS) of multiplex
Multiplex section Major
section
Remote defect indication (RDI) of multiplex
Minor
section

Chapter 5 - Alarm Message and Handling
Alarm Alarm
Multiplex section signal degraded Minor
Unavailable time Major
Communication B2 bit error over-threshold Major

alarms DCCM connection failure Major
K2 byte mismatch Critical
K1/K2 byte mismatch Critical
Loss of AU pointer (LOP) Critical
AU4/AU4-nc
Alarm indication signal (AIS) of AU path Major
Loss of TU pointer (LOP) Critical
TU3/TU12/TU11
Alarm indication signal (AIS) of TU path Major
Payload mismatch (PLM) of higher-order
Critical
path
Loss of multiframe (LOM) Critical
Trace ID Mismatch (TIM) of higher-order
Major
path
VC4/VC3/VC4-nc/ Higher-order path unequipped (UNEQ) Major
VC3-nc
Remote defect indication (RDI) Minor
Signal deterioration (SD) of higher-order
Minor
path
Error rate cross-threshold (EXC) Major
Lower-order path unequipped (UNEQ) Major
Payload mismatch (PLM) of lower-order path Major
Remote defect indication (RDI) Minor
VC12/VC11 Trace ID Mismatch (TIM) of lower-order
Major
path
Error rate cross-threshold (EXC) Major
Extension signal label mismatch (ExSLM) Major
Remote Failure Indication (RFI) Minor
Loss of frame of timing input signal (LOF) Major
Alarm indication signal (AIS) of timing input
Major
signal
Synchronization Synchronous BER over-threshold of timing input signal Major
alarms timing source
Timing input loss Critical
Timing output loss Critical
Synchronous timing source mismatch Major
Equipment Board Board out of position Critical

Alarm Alarm
alarms Board type mismatch Critical
Omitted board Major
Unknown board type Major
Board ejector lever not in position Major
Interface board type mismatch Critical
Interface board not in position Critical
Interface board working abnormally Critical
Board working abnormally Critical
Module temperature over-threshold Minor
Loss of EDFA receive signal Critical
EDFA Output optical power over-threshold Major
Input optical power over-threshold Major
Optical launched power failure Critical
Laser bias current over-threshold Minor
Laser temperature over-threshold Minor
Outgoing fiber power over-threshold of
Minor
EDFA laser pumping laser
Cooling current over-threshold of pumping
Minor
laser
Fan fault Major
Excessive humidity Warning
Environment High temperature Warning
Fire alarm Warning
Temperature Temperature over-threshold of detection
Minor
detection point point
The alarm messages of the ZXMP S385 Ethernet board are listed in
Table 29.
TABLE 29 ALARM MESSAGES OF THE ZXMP S385 ETHERNET BOARD
Detection Alarm
Alarm Name
Point Level
Ethernet
electrical Ethernet interface unconnected Critical
interface
Ethernet interface unconnected Critical
Ethernet optical Loss of Signal (LOS) Critical

interface Missing Laser Module Critical
Laser Module Fault Critical

Detection Alarm
Alarm Name
Point Level
Loss of Pointer (LOP) Critical
AU4/TU3/TU12
Alarm Indication Signal (AIS) Major
Trace ID Mismatch (TIM) Major
Remote Defect Indication (RDI) Minor
Enhanced Remote Defect Indication of Payload Defect (E-RDI
Minor
Payload Defect)
Enhanced Remote Defect Indication of Connectivity Defect (E-RDI
Minor
Connectivity Defect)
Enhanced Remote Defect Indication of Server Defect (E-RDI Server
Minor
VC4/VC3 Defect)
Payload Mismatch (PLM) Critical
Signal Deterioration (SD) Minor
Path Unequipped (UNEQ) Major
Loss of Multi-frame (LOM) Critical
BER Cross-threshold (EXC) Major
Unavailable Second (UAS) Major
Trace ID Mismatch (TIM) Major
Remote Defect Indication (RDI) Minor
Enhanced Remote Defect Indication of Payload Defect (E-RDI
Minor
Payload Defect)
Enhanced Remote Defect Indication of Connectivity Defect (E-RDI
Minor
Connectivity Defect)
VC12 Enhanced Remote Defect Indication of Server Defect (E-RDI Server

Minor
Defect)
Payload Mismatch (PLM) Critical
Signal Deterioration (SD) Major
Extended Signal Label Mismatch (ExSLM) Major
Temperature Detection Point Temperature Out of Limit Minor
Interface board type mismatch Critical
Interface board out of position Critical
Board
Interface board running abnormality Critical
Detection point temperature out of limit Minor
Loss of Frame (LOF) Critical
Out of Frame (OOF) Critical
Motherboard Signal Deterioration (SD) Minor

Detection Alarm
Alarm Name
Point Level
Mismatch of User Payload ID (MUPI) Major
Customer Signal Failure (CSF) Major

VCG
Loss of Frame Delineation (LFD) Major
(EOS) port
VCG group Loss (VCG LOS) Major
Out Of Frame of Receiving PPP or HDLC Frame Major
Alarm Messages and Solutions

Table 30 through Table 121 list the causes and troubleshooting of the
common alarms for users’ reference.
TABLE 30 LOSS OF RECEIVED 10 G OPTICAL SIGN AL
Item Description
Alarm name Loss of received 10 G optical signal (LOS)
Alarm level Critical
Alarm category Communication alarm
Alarm This alarm indicates interruption at the optical physical layer, and the local end
explanation receives no optical signal from the opposite end.
Alarm board OL64
Related
None
overhead
Board: The red alarm indicator light is constantly on, and the receiving indicator light
Alarm indication is constantly off.
EMS: Open the board management dialog box, there is red alarm identifier.
Fault of external optical line
Fault of fiber pigtails and coupling components
Alarm cause Inadequate coupling or wrong transmitting-receiving relationship
Fault of optical receiving module on the local end optical line board
Fault of optical transmitting module on the opposite end optical line board
Local end optical line board receives light of different rate level
Take care of the optical line

Replace the fiber pigtails or coupling components
Ensure good coupling, and correct the transmitting-receiving relationship
Solutions
Replace the local end optical line board.
Replace the opposite end optical line board
Check the rate level of the optical connection line, and connect a correct optical line
Logical functional block of the fault: Basic functional block of the SDH physical
Remarks
interface (SPI)

TABLE 31 LOSS OF RECEIVED 2.5 G OPTICAL SIGNAL
Item Description
Alarm name Loss of received 2.5 G optical signal (LOS)
Alarm board OL16
Related
None
overhead

Solutions
Remarks
interface (SPI)

TABLE 32 LOSS OF RECEIVED 622 M OPTICAL SIGNAL
Item Description
Alarm name Loss of received 622 M optical signal (LOS)
Alarm board OL4
Related
None
overhead

Solutions
Remarks
interface (SPI)

TABLE 33 LOSS OF RECEIVED 155 M OPTICAL SIGNAL
Item Description
Alarm name Loss of received 155 M optical signal (LOS)
Alarm board OL1
Related
None
overhead

Solutions
Remarks
interface (SPI)

TABLE 34 LOSS OF 155 M ELECTRICAL SIGNAL
Item Description
Alarm name Loss of 155 M electrical signal (LOS)
Alarm This alarm indicates interruption at the electrical physical layer, and the local end
explanation receives no electrical signal from the opposite end.
Alarm board ESS1, LP1
Related
None
overhead
Board: The red alarm indicator light is constantly on.
Alarm indication
155 M cable is connected inversely.
155 M cable is cut off.
Alarm cause
155 M interface is faulty.
The external equipment connected with the 155 M interface is faulty.
Correct the connection direction of the 155 M cable.
Replace the 155 M cable.
Solutions
Replace the corresponding board.
Repair the equipment connected with the 155 M interface.
Logical functional block of the fault: Basic functional block of the PDH physical
Remarks
interface (PPI)

Item Description
Alarm board EP3
Related
None
overhead
Alarm indication EMS: Open the board management dialog box, the board is red and is marked with
“C”.
Alarm cause
Solutions
Replace the EP3 board.
Remarks
interface (PPI)

Item Description
Alarm board EP3
Related
None
overhead
Alarm indication EMS: Open the board management dialog box, , the board is red and is marked with
“C”.
Alarm cause
Solutions
Replace the EP3 board.
Remarks
interface (PPI)

Item Description
Alarm board EPE1
Related
None
overhead
Alarm indication
Alarm cause
Adjust the 2 M cable.
Solutions
Remarks
interface (PPI)

TABLE 38 LOSS OF 1.5 M ELECTRICAL SIGNAL
Item Description
Alarm name Loss of 1.5 M electrical signal (LOS)
Alarm board EPT1
Related
None
overhead
Alarm indication
1.5 M cable is connected inversely.
1.5 M cable is cut off.
Alarm cause
1.5 M interface is faulty.
The external equipment connected with the 1.5 M interface is faulty.
Correct the connection direction of the 1.5 M cable.
Adjust the 1.5 M cable.
Solutions
Replace the EPT1 board.
Repair the equipment connected with the 1.5 M interface.
Remarks
interface (PPI)

TABLE 39 CV PERFORM ANCE OVER THRESHOLD
Item Description
Alarm name CV (Coding Violation) performance over threshold
Alarm level Warning
Alarm This alarm indicates that the 1.5 M/2 M/34 M/45 M/155 M physical interface is
explanation damaged or interconnected improperly.
Alarm board EP3, EPE1, EPT1
Related
None
overhead
Board: The red alarm indicator is constantly on.
Alarm indication
EMS: Open the board management dialog box, there is purple alarm identifier.
Inferior welding of the cable connector

Improper DDF common ground
Alarm cause Poor performance of the tributary board interface
Switches or other equipment connected with the interface of transmission
equipment are faulty.
Weld the cable connector again.

Make a new ground cable.
Solutions
Take care of the peripheral equipment.
Remarks
interface (PPI).

TABLE 40 OPTICAL RECEIVED POWER OVER-THRESHOLD
Item Description
Alarm name Optical received power over-threshold
Alarm level Major
Alarm
None
explanation
Alarm board OL1, OL4, OL16, OL64
Related
None
overhead
Alarm indication
EMS: Open the board management dialog box, there is orange alarm identifier.
Improper tightness of fiber connection in the receiving direction

Alarm cause
LOS alarm reported from the optical received signal
Adjust the tightness of the fiber connector

Solutions Find out the cause of the LOS alarm. This alarm will disappear after resolving the
LOS alarm.
Remarks
interface (SPI).

TABLE 41 LOSS OF FRAME
Item Description
Alarm name Loss of Frame (LOF)
Alarm This alarm indicates interruption at the regenerator section layer, and the local end
explanation receives no optical modulation signal from the opposite end.
Related
A1, A2
overhead
Board: The red alarm indicator is constantly on, and the receiving indicator light
Alarm indication flashes.

Fault of fiber pigtails or coupling components
Inferior coupling or wrong transmitting-receiving relationship
Fault of local-end optical line board
Alarm cause
Fault of opposite-end optical line board
Local-end optical line board receives light of different rate level.
Fault of CSA/CSE board
Fault of motherboard

Replace the local-end optical line board
Solutions
Replace the opposite-end optical line board
Replace the CSA/CSE board
Replace the motherboard
Logical functional block of the fault: Basic functional block of regenerator section
Remarks
terminal (RST)

TABLE 42 UNAV AIL ABLE TIME STARTS (REGENERATOR SECTION)
Item Description
Alarm name Unavailable time starts (RS)
Alarm level Major
Related
A1, A2, B1
overhead
Alarm indication

Fault of fiber pigtails OR coupling components
Alarm cause
Local-end optical line board receives light of different rate level.
Take care of the optical line.

Replace the fiber pigtails or coupling components.
Ensure good coupling, and correct the transmitting-receiving relationship.
Solutions
Replace the opposite-end optical line board.
Check the rate level of the optical connection line, and connect a correct optical line.
Replace the CSA/CSE board.
Replace the motherboard.
Remarks
terminal (RST)

T A B L E 4 3 B 1 U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Alarm name B1 UAS performance over-threshold
Alarm level Major
Related
A1, A2, B1
overhead
Alarm indication

Alarm cause
Local-end optical line board receives light of different rate level

Solutions
Replace the motherboard
Remarks
terminal (RST)

TABLE 44 OUT OF FRAME
Item Description
Alarm name Out of frame (OOF)
This alarm indicates fault at the regenerator section layer, and the system cannot
Alarm locate frame headers of five consequent frames of optical modulation signal
explanation received by the local end from the opposite end, then the equipment enters the out-
of-frame status.

Related
A1, A2
overhead
Alarm indication

Alarm cause
Improper contact of board and motherboard pins

Solutions
Change the slot or replace the motherboard
Remarks
terminal (RST)

TABLE 45 OFS PERFORMANCE OVER-THRESHOLD
Item Description
Alarm name OFS performance over-threshold
Alarm level Major
This alarm indicates fault at the regenerator section layer, and the system cannot
Alarm locate frame headers of five consequent frames of optical modulation signal
explanation received by the local end from the opposite end, then the equipment enters the out-
of-frame status.
Related
A1, A2
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (RST)

TABLE 46 REGENERATOR SECTION SIGNAL DEGRADED
Item Description
Alarm name Regenerator section signal degraded (RS-DEG)
Alarm level Minor
This alarm indicates fault at the regenerator section layer, the optical modulation
Alarm
signal received by the local end from the opposite end degrades, resulting in the
explanation
BER of RS worse than 10-3.

Related
B1
overhead
Alarm indication
EMS: Open the board management dialog box, there is yellow alarm identifier.

Alarm cause

Solutions
Remarks
terminal (RST)

TABLE 47 B1 SES PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name B1 SES performance over-threshold
Alarm level Major
This alarm indicates fault at the regenerator section layer, there is SES (Severely
Alarm
Errored Second) in the optical modulation signal received by the local end from the
explanation
opposite end.

Related
B1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (RST)

TABLE 48 B1 ES PERFORMANCE OVER-THRESHOLD
Item Description
Alarm name B1 ES performance over-threshold
Alarm level Major
This alarm indicates fault at the regenerator section layer, there is ES (Errored
Alarm
Second) in the optical modulation signal received by the local end from the opposite
explanation
end.

Related
B1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (RST)

TABLE 49 B1 BBE PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name B1 BBE performance over-threshold
Alarm level Major
This alarm indicates fault at the regenerator section layer, there is BBE (Background
Alarm
Block Error) in the optical modulation signal received by the local end from the
explanation
opposite end.
Related
B1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (RST)

TABLE 50 MULTIPLEX SECTION AL ARM INDICATION SIGNAL (MS- AIS)
Item Description
Alarm name Multiplex section alarm indication signal
Alarm level Major
Alarm This alarm indicates interruption at the multiplex section layer, and the local end
explanation receives no multiplex signal from the opposite end.
Related
K2
overhead
Alarm indication

Alarm cause

Solutions
Logical functional block of the fault: Basic functional block of multiplex section
Remarks
terminal (MST)

TABLE 51 UNAVAILABLE TIME (MULTIPLEX SECTION)
Item Description
Alarm name Unavailable time (multiplex section)
Alarm level Major
Related
B2, M1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 52 MULTIPLEX SECTION REMOTE DEFECT INDICATION (MS-RDI)
Item Description
Alarm name Multiplex section remote defect indication (MS-RDI)
Alarm level Minor
Alarm This alarm indicates interruption at the multiplex section layer, and the opposite end
explanation receives no multiplex signal from the local end.
Related
B2, M1
overhead
Alarm indication
This alarm message occurs in pair with MS-AIS, and the causes are the same as
those of MS-AIS, which can be:
Alarm cause

Solutions
Remarks
terminal (MST)

T A B L E 5 3 B 2 U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Alarm level Major
Related
B2, M1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (MST)

T A B L E 5 4 B 2 F E U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Alarm name B2 FEUAS performance over-threshold
Alarm level Major
Alarm This alarm indicates interruption at the multiplex section layer, and the opposite end
explanation receives no multiplex signal from the local end.

Related
B2, M1
overhead
Alarm indication
This alarm message occurs in pair with the alarm message of “B2 UAS Performance
Over-Threshold”. The causes are the same which can be:
Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 55 MULTIPLEX SECTION SIGNAL DEGRADED (MS-DEG)
Item Description
Alarm name Multiplex section signal degraded (MS-DEG)
Alarm level Minor
This alarm indicates fault at the multiplex section layer, the optical modulation
Alarm
signal received by the local end from the opposite end degrades, resulting in the
explanation
BER of MS worse than 10-3.
Related
B2, M1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 56 B2 BIT ERRORS CROSS-THRESHOLD (MS-EXC)
Item Description
Alarm name B2 bit errors cross-threshold (MS-EXC)
Alarm level Major
Alarm This alarm indicates fault at the multiplex section layer, there are severely bit errors
explanation in the optical modulation signal received by the local end from the opposite end.
Related
B2, M1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 57 B2 SES PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm level Major
This alarm indicates fault at the multiplex section layer, there is SES (Severely
Alarm
Errored Second) in the optical modulation signal received by the local end from the
explanation
opposite end.
Related
B2, M1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 58 B2 FESES PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name B2 FESES performance over-threshold
Alarm level Major
This alarm indicates fault at the multiplex section layer, there is SES (Severely
Alarm
Errored Second) in the optical modulation signal received by the opposite end from
explanation
the local end.
Related
B2, M1
overhead
Alarm indication
This alarm message occurs in pair with the alarm message of “B2 SES Performance
Over-Threshold”. The causes are the same that can be:
Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 59 B2 ES PERFORMANCE OVER-THRESHOLD
Item Description
Alarm level Major
Alarm This alarm indicates fault at the multiplex section layer, there is errored second in
explanation the optical modulation signal received by the local end from the opposite end.
Related
B2, M1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 60 B2 FEES PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name B2 FEES performance over-threshold
Alarm level Major
Alarm This alarm indicates fault at the multiplex section layer, there is errored second in
explanation the optical modulation signal received by the opposite end from the local end.
Related
B2, M1
overhead
Alarm indication
This alarm message occurs in pair with the alarm message of “B2 ES Performance
Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 61 B2 BBE PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm level Major
This alarm indicates fault at the multiplex section layer, there are background block
Alarm
errors in the optical modulation signal received by the local end from the opposite
explanation
end.
Related
B2, M1
overhead
Alarm indication

Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 62 B2 FEBBE PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name B2 FEBBE performance over-threshold
Alarm level Major
This alarm indicates fault at the multiplex section layer, there are background block
Alarm
errors in the optical modulation signal received by the opposite end from the local
explanation
end.
Related
B2, M1
overhead
Alarm indication
This alarm message occurs in pair with the alarm message of “B2 BBE Performance
Alarm cause

Solutions
Remarks
terminal (MST)

TABLE 63 MULTIPLEX SECTION PROTECTION SWITCHING EVENT
Item Description
Alarm name Multiplex section protection switching event
Alarm level Minor
Alarm This alarm message occurs in the network protected by multiplex section switching.
explanation It indicates occurrence of multiplex section protection switching.
Related
K1, K2
overhead
Alarm indication
When an optical line board detects "loss of receiving signal", "loss of frame", or
"RS/MS AIS" alarms, or when the BER of the RS/MS reaches 10-3, the MS protection
switching will occur. And the EMS will report the "MS protection switching event"
Alarm cause alarm.
Fault of APS configuration on the local-end/opposite-end optical line board.
Physical fault of APS protocol processing module on the local-end/opposite-end
optical line board
Handle higher level alarms first. After handling the higher level faults, the “Multiplex
section protection switching event” alarm will automatically disappear after APS
Solutions automatic recovery.
Reset APS startup/stop status and issue the command.
Replace the local-end/opposite-end optical line board.
Remarks
protection (MSP)

TABLE 64 AU4 P ATH AL ARM INDICATION SIGNAL, UNAVAILABLE TIME
Item Description
Alarm name AU4 path alarm indication signal, unavailable time
Alarm level Major
Alarm This alarm indicates that local end receives no signal on the higher-order path from
explanation the opposite end.
Alarm board OL1, OL4, OL16, OL64, LP1, EP3, EPE1, EPT1
Related
AU pointer, B3
overhead
Alarm indication
Wrong cross-connect configuration

Wrong clock configuration
Fault of optical line board
Alarm cause Fault of CSA/CSE board
Fault of tributary board
Fault of motherboard pins
Damage of motherboard
Correct the timeslot configuration

Correct the clock configuration
Replace the optical line board
Solutions
Replace the tributary board
Logical functional block of the fault: multiplexing functional block of higher-order

interface (HOI)
Remarks
If one NE is configured with timeslot pass-through at AU4 level, since the “AU4 path
alarm indication signal” will not be terminated, the EMS will report this alarm.

TABLE 65 LOSS OF AU4 POINTER
Item Description
Alarm name Loss of AU4 pointer (LOP)
explanation the opposite end. It is caused by excessive pointer justification.
Related
AU pointer
overhead
Alarm indication


Solutions

Remarks
interface (HOI)

TABLE 66 REMOTE DEFECT INDICATION (VC4 HIGHER-ORDER P ATH VIRTUAL CONTAINER)
Item Description
Alarm name Remote defect indication (RDI)
Alarm level Minor
Alarm This alarm indicates that opposite end receives no signal on the higher-order path
explanation from the local end.
Related
G1
overhead
Alarm indication
This alarm occurs in pair with the “AU4 path alarm indication signal, unavailable
time”. The causes are the same that can be:
Alarm cause Fault of optical line board

Solutions

Remarks
interface (HOI)

T A B L E 6 7 B 3 U AS P E R F O R M A N C E O V E R - T H R E S H O L D ( V C 4 H I G H E R - O R D E R P A T H
VIRTUAL CONTAINER)
Item Description
Alarm level Major
Related
B3
overhead
Alarm indication


Solutions

Remarks
interface (HOI)

T A B L E 6 8 B 3 F E U AS P E R F O R M A N C E O V E R - T H R E S H O L D ( V C 4 H I G H E R - O R D E R P A T H
VIRTUAL CONTAINER)
Item Description
Alarm level Major
Related
G1
overhead
Alarm indication
This alarm message occurs in pair with the “B3 UAS performance over-threshold”.
The causes are the same that can be:

Solutions

Remarks
interface (HOI)

TABLE 69 LOSS OF MULTI-FRAME (VC4 HIGHER-ORDER P ATH VIRTUAL CONTAINER)
Item Description
Alarm name Loss of multi-frame (higher-order VC4 path virtual container)
Alarm This alarm indicates that H4 is lost or incorrect, which may result in abnormal lower-
explanation order service.
Related
H4
overhead
Alarm indication

Alarm cause

Solutions Replace the CSA/CSE board

Remarks
interface (HOI)

TABLE 70 VC4 HIGHER-ORDER P ATH SIGNAL DEGRADED
Item Description
Alarm name VC4 higher-order path signal degraded
Alarm level Minor
This alarm indicates fault at the higher-order path layer. The optical modulation
Alarm
signal received at the local end from the opposite end degrades, resulting in the
explanation
BER of multiplex section worse than 10-3.
Related
B3
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 71 B3 SES PERFORM ANCE OVER-THRESHOLD (VC4 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the local end from the opposite end degrades and there is SES
explanation
(Severely Errored Second).
Related
B3
overhead
Alarm indication

Alarm cause
Fault of CSA/CSE board or clock

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 72 B3 FESES PERFORM ANCE OVER-THRESHOLD (VC4 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the opposite end from the local end degrades and there is SES
explanation
Related
G1
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 73 B3 ES PERFORMANCE OVER-THRESHOLD (VC4 HIGHER-ORDER P ATH VIRTUAL

CONTAINER)
Item Description
Alarm level Major
Alarm
explanation
Related
B3
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 74 B3 FEES PERFORM ANCE OVER-THRESHOLD (VC4 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the opposite end from the local end degrades and there is ES
explanation
(Errored Second).
Related
G1
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 75 B3 BBE PERFORM ANCE OVER-THRESHOLD (VC4 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the local end from the opposite end degrades and there is BBE
explanation
(Background Block Error).
Related
B3
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 76 B3 FEBBE PERFORM ANCE OVER-THRESHOLD (VC4 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the opposite end from the local end degrades, resulting the BER
explanation
of multiplex section worse than 10-3.
Alarm board OL1, OL4, OL16, OL64, LP1, EPE1
Related
G1
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 77 VC4 HIGHER-ORDER P ATH UNEQUIPPED
Item Description
Alarm name VC4 higher-order path unequipped
Alarm level Major
Alarm
C2 byte is zero
explanation
Related
C2
overhead
Alarm indication
C2 byre is wrongly configured to 00H

Alarm cause
Rewrite C2 byte
Solutions
Change the slot

Remarks
interface (HOI)

TABLE 78 VC4 HIGHER-ORDER P ATH TRACE IDENTIFIER MISM ATCH
Item Description
Alarm name VC4 higher-order path trace identifier mismatch
Alarm level Major
Alarm The path trace identifier received at the local end disagrees with the path trace
explanation identifier sent from the opposite end.
Alarm board OL1, OL4, OL16, OL64, LP1
Related
J1
overhead
Alarm indication
Wrong J1 configuration
J1 configurations are inconsistent when different equipment or different
manufacturers’ equipment are interconnected via optical interface
CSA/CSE board fault
Tributary board fault
Motherboard pins fault
Rewrite J1
Make J1 configuration consistent.
Solutions
Change the slot

Remarks
interface (HOI)

TABLE 79 VC4 SIGNAL LABEL MISM ATCH
Item Description
Alarm name VC4 signal label mismatch
Alarm level Major
Alarm The signal identifier received at the local end disagrees with the path trace identifier
explanation sent from the opposite end.
Related
C2
overhead
Alarm indication
Wrong C2 configuration
C2 configurations are inconsistent when different equipment or different
manufacturers’ equipment are interconnected via optical interface
CSA/CSE board fault
Tributary board fault
Motherboard pins fault
Rewrite C2
Make C2 configuration consistent.
Solutions
Change the slot

Remarks
interface (HOI)

TABLE 80 AU4 PJE+/PJE- PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name AU4 PJE+/PJE- performance over-threshold
Alarm This alarm indicates synchronization fault on the higher-order path of the local end,
explanation and the clock accuracy degrades.
Related
AU-PTR
overhead
Alarm indication
Wrong clock source configuration

Fault of external clock source
Alarm cause
Fault of the CSA/CSE board internal clock or phase-lock ring clock
Fault of the clock extraction part of the optical line board
Correct the wrong clock source configuration

Replace the external clock, check and replace the cable
Solutions
Logical functional blocks of the fault: multiplexing functional block of higher-order

interface (HOI), auxiliary functional block of synchronous equipment timing source
Remarks
(SETS), auxiliary functional block of synchronous equipment timing physical
interface (SETPI)

TABLE 81 AU4 PROTECTION SWITCHING EVENT
Item Description
Alarm name AU4 protection switching event
Alarm level Minor
Alarm This alarm message occurs in the network protected by path protection. It indicates
explanation occurrence of higher-order path protection switching.
Alarm board CSA/CSE
Related
None
overhead
Alarm indication
When an optical line board detects optical line interruption, the path protection
switching will occur. And it will report the "AU4 protection switching event" alarm to
Alarm cause the EMS.
Wrong timeslot configuration.
Physical fault of CSA/CSE board.
Handle higher level alarms. After handling the higher level faults, the “AU4
protection switching event” alarm will automatically disappear.
Solutions
Correct the wrong timeslot configuration.
Logical functional block of the fault: the multiplexing functional block of higher-order
Remarks
interface (HOI)

TABLE 82 TU3 P ATH AL ARM INDICATION SIGNAL, UNAVAILABLE TIME
Item Description
Alarm name TU3 path alarm indication signal, unavailable time
Alarm level Major
Alarm board EP3
Related
TU3 pointer
overhead
Alarm indication

Fault of EP3 tributary board

Solutions

interface (HOI)
Remarks
If one NE is configured with timeslot pass-through at AU4 level, since the “AU4 path
alarm indication signal” will not be terminated, the EMS will report this alarm.

TABLE 83 LOSS OF TU3 POINTER
Item Description
Alarm name Loss of TU3 pointer (LOP)
explanation the opposite end. It is caused by excessive pointer justification.
Alarm board EP3
Related
B3 pointer
overhead
Alarm indication


Solutions

Remarks
interface (HOI)

TABLE 84 REMOTE DEFECT INDICATION (VC3 HIGHER-ORDER P ATH VIRTUAL CONTAINER)
Item Description
Alarm level Minor
Alarm board EP3
Related
G1
overhead
Alarm indication
This alarm occurs in pair with the “TU3 path alarm indication signal, unavailable
time”. The causes are the same that can be:
Fault of EP3 board

Solutions

Remarks
interface (HOI)

T A B L E 8 5 B 3 U AS P E R F O R M A N C E O V E R - T H R E S H O L D ( V C 3 H I G H E R - O R D E R P A T H
VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm board EP3
Related
B3
overhead
Alarm indication


Solutions

Remarks
interface (HOI)

T A B L E 8 6 B 3 F E U AS P E R F O R M A N C E O V E R - T H R E S H O L D ( V C 3 H I G H E R - O R D E R P A T H
VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm board EP3
Related
G1
overhead
Alarm indication
This alarm message occurs in pair with the “B3 UAS performance over-threshold”.
The causes are the same that can be:

Solutions

Remarks
interface (HOI)

TABLE 87 VC3 HIGHER-ORDER P ATH SIGNAL DEGRADED
Item Description
Alarm name VC3 higher-order path signal degraded
Alarm level Minor
Alarm
signal received at the local end from the opposite end degrades, resulting in the
explanation
BER of multiplex section worse than 10-3.
Alarm board EP3

Related
B3
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 88 B3 SES PERFORM ANCE OVER-THRESHOLD (VC3 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
explanation
Alarm board EP3
Related
B3
overhead
Alarm indication

Alarm cause
Fault of CSA/CSE board or clock

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 89 B3 FESES PERFORM ANCE OVER-THRESHOLD (VC3 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the opposite end from the local end degrades and there is SES
explanation
Alarm board EP3
Related
G1
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 90 B3 ES PERFORMANCE OVER-THRESHOLD (VC3 HIGHER-ORDER P ATH VIRTUAL

CONTAINER)
Item Description
Alarm level Major
Alarm
explanation
Alarm board EP3
Related
B3
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 91 B3 FEES PERFORM ANCE OVER-THRESHOLD (VC3 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the opposite end from the local end degrades and there is ES
explanation
(Errored Second).
Related
G1
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 92 B3 BBE PERFORM ANCE OVER-THRESHOLD (VC3 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the local end from the opposite end degrades and there is BBE
explanation
Alarm board EP3
Related
B3
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 93 B3 FEBBE PERFORM ANCE OVER-THRESHOLD (VC3 HIGHER-ORDER P ATH

VIRTUAL CONTAINER)
Item Description
Alarm level Major
Alarm
signal received at the opposite end from the local end degrades, resulting the BER
explanation
of multiplex section worse than 10-3.
Alarm board EP3
Related
G1
overhead
Alarm indication

Alarm cause

Solutions
Change the slot

Remarks
interface (HOI)

TABLE 94 VC3 HIGHER-ORDER P ATH UNEQUIPPED
Item Description
Alarm name VC3 higher-order path unequipped
Alarm level Major
Alarm
C2 byte is zero
explanation
Alarm board EP3
Related
C2
overhead
Alarm indication
C2 byre is wrongly configured to 00H

Alarm cause
Rewrite C2 byte
Solutions
Replace the EP3 tributary board

Remarks
interface (HOI)

TABLE 95 VC3 HIGHER-ORDER P ATH TRACE IDENTIFIER MISM ATCH
Item Description
Alarm name VC3 higher-order path trace identifier mismatch
Alarm level Major
Alarm The path trace identifier received at the local end disagrees with the path trace
explanation identifier sent from the opposite end.
Alarm board EP3
Related
J1
overhead
Alarm indication
Wrong J1 configuration
J1 configurations are inconsistent when different equipment or different
Alarm cause manufacturers’ equipment are interconnected via optical interface
Rewrite J1
Make J1 configuration consistent.
Solutions

Remarks
interface (HOI)

TABLE 96 VC3 SIGNAL LABEL MISM ATCH
Item Description
Alarm name VC3 signal label mismatch
Alarm level Major
Alarm The signal identifier received at the local end disagrees with the path trace identifier
explanation sent from the opposite end.
Alarm board EP3
Related
C2
overhead
Alarm indication
Wrong C2 configuration
C2 configurations are inconsistent when different equipment or different
Alarm cause manufacturers’ equipment are interconnected via optical interface
Rewrite C2
Make C2 configuration consistent.
Solutions

Remarks
interface (HOI)

TABLE 97 TU3 PJE+/PJE- PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name TU3 PJE+/PJE- performance over-threshold
Alarm This alarm indicates synchronization fault on the higher-order path of the local end,
explanation and the clock accuracy degrades.
Alarm board EP3
Related
TU-PTR
overhead
Alarm indication
There are higher-order AU pointer justification event and out-of-synchronization.

Alarm cause
Fault of EP3 board
Handle the higher-order AU pointer justification event and out-of-synchronization.

Solutions
Replace the EP3 board
Logical functional blocks of the fault: multiplexing functional block of higher-order

interface (HOI), auxiliary functional block of synchronous equipment timing source
Remarks
(SETS), auxiliary functional block of synchronous equipment timing physical
interface (SETPI)

TABLE 98 VC3 PROTECTION SWITCHING EVENT
Item Description
Alarm name VC3 protection switching event
Alarm level Minor
Alarm This alarm message occurs in the network protected by path protection. It indicates
explanation occurrence of higher-order path protection switching.
Alarm board EP3
Related
None
overhead
Alarm indication
When the EP3 board detects upper-stream path interruption, the path protection
switching will occur. And it will report the "VC3 protection switching event" alarm to
Alarm cause the EMS.
Physical fault of CSA/CSE board.
Handle upper-stream path alarms. After that, the “VC3 protection switching event”
alarm will automatically disappear.
Solutions
Logical functional block of the fault: the multiplexing functional block of higher-order
Remarks
interface (HOI)

TABLE 99 TU12 P ATH AL ARM INDICATION SIGNAL, UNAV AIL ABLE TIME
Item Description
Alarm level Major
Alarm This alarm indicates interruption on the lower-order path layer, and the local end
explanation receives no lower-order electrical signal from the opposite end.
Alarm board EPE1
Related
V5
overhead
Alarm indication
Wrong timeslot configuration

Alarm cause Fault of some tributaries of 2 M tributary board at the local/opposite end

Replace the EPE1 board
Solutions
Switch between the active/standby CSA/CSE board; reset the CSA/CSE board; or
replace the CSA/CSE board
Logical functional block of the fault: multiplexing functional block of lower-order

Remarks
interface (LOI)

Item Description
This alarm indicates interruption at the lower-order path layer, and the local end
Alarm
receives no lower-order electrical signal from the opposite end. Eight consecutive
explanation
NDF or eight multi-frames of invalid pointer are detected.
Alarm board EPE1
Related
TU12 pointer
overhead
Alarm indication

Alarm cause Fault of some tributaries of 2 M tributary board at the local/opposite end

Solutions

Remarks
interface (LOI)

TABLE 101 REMOTE DEFECT INDICATION (VC12 LOWER-ORDER P ATH VIRTUAL

CONTAINER)
Item Description
Alarm level Minor
Alarm This alarm indicates interruption at the lower-order path layer of the opposite end,
explanation the opposite end receives no electrical signal from the local end.
Alarm board EPE1
Related
V5
overhead
Alarm indication
This alarm occurs in pair with the “Lower-order path alarm indication signal”. The
causes can be:
Alarm cause Wrong timeslot configuration
Fault of some tributaries of 2 M tributary board at the local/opposite end

Solutions

Remarks
interface (LOI)

TABLE 102 TU11 P ATH ALARM INDICATION SIGNAL, UNAV AIL ABLE TIME
Item Description
Alarm level Major
Alarm This alarm indicates interruption on the lower-order path layer, and the local end
Alarm board EPT1
Related
V5
overhead
Alarm indication

Alarm cause Fault of some tributaries of EPT1 tributary board at the local/opposite end

Replace the EPT1 board
Solutions

Remarks
interface (LOI)

Item Description
This alarm indicates interruption at the lower-order path layer, and the local end
Alarm
receives no lower-order electrical signal from the opposite end. Eight consecutive
explanation
NDF or eight multi-frames of invalid pointer are detected.
Alarm board EPT1
Related
TU11 pointer
overhead
Alarm indication

Alarm cause Fault of some tributaries of EPT1 tributary board at the local/opposite end

Solutions

Remarks
interface (LOI)

TABLE 104 REMOTE DEFECT INDICATION (VC11 LOWER-ORDER P ATH VIRTUAL

CONTAINER)
Item Description
Alarm level Minor
Alarm This alarm indicates interruption at the lower-order path layer of the opposite end,
explanation the opposite end receives no electrical signal from the local end.
Alarm board EPT1
Related
V5
overhead
Alarm indication
This alarm occurs in pair with the “Lower-order path alarm indication signal,
unavailable time”. The causes can be:
Fault of some tributaries of EPT1 tributary board at the local/opposite end

Solutions Switch between the active/standby CSA/CSE board; reset the CSA/CSE board; or
Switch between the active/standby board, rise the voltage of power supply board

Remarks
interface (LOI)

T A B L E 1 0 5 V 5 U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Alarm name V5 UAS performance over-threshold
Alarm level Major
Alarm This alarm indicates interruption at the lower-order path layer, and the local end
Alarm board EPE1, EPT1
Related
V5
overhead
Alarm indication

Alarm cause Fault of some tributaries of tributary board at the local/opposite end

Replace the EPE1/EPT1 board
Solutions

Remarks
interface (LOI)

TABLE 106 V5 FEUAS PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name V5 FEUAS performance over-threshold
Alarm level Major
This alarm indicates interruption at the lower-order path layer of the opposite end,
Alarm
and the opposite end receives no electrical signal on the lower-order path from the
explanation
local end.
Related
V5
overhead
Alarm indication
This alarm occurs in pair with the “Lower-order path alarm indication signal” and
“V5 UAS performance over-threshold” alarms. The causes can be:
Fault of some tributaries of tributary board at the local/opposite end

Solutions

Remarks
interface (LOI)

TABLE 107 V5 SES PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name V5 SES performance over-threshold
Alarm level Major
This alarm indicates fault at the electrical physical layer. The electrical signal
Alarm
received at the local end from the opposite end degrades and there is SES (Severely
explanation
Errored Second).
Related
V5
overhead
Alarm indication

Alarm cause


Remarks
interface (LOI)

TABLE 108 V5 FESES PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name V5 FESES performance over-threshold
Alarm level Major
Alarm
received at the opposite end from the local end degrades and there is SES (Severely
explanation
Errored Second).
Related
V5
overhead
Alarm indication

Alarm cause


Remarks interface (LOI).
Alarms of higher level automatically mask the alarms of lower level.

TABLE 109 V5 ES PERFORMANCE OVER-THRESHOLD
Item Description
Alarm name V5 ES performance over-threshold
Alarm level Major
Alarm
received at the local end from the opposite end degrades and there is ES (Errored
explanation
Second).
Related
V5
overhead
Alarm indication

Alarm cause


Remarks
interface (LOI)

TABLE 110 V5 FEES PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name V5 FEES performance over-threshold
Alarm level Major
Alarm
received at the opposite end from the local end degrades and there is ES (Errored
explanation
Second).
Related
V5
overhead
Alarm indication

Alarm cause


Remarks
interface (LOI)

TABLE 111 V5 BBE PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name V5 BBE performance over-threshold
Alarm level Major
Alarm
received at the local end from the opposite end degrades and there is BBE
explanation
Related
V5
overhead
Alarm indication
Fault of tributary board at the local/opposite end

Alarm cause


Remarks
interface (LOI)

TABLE 112 V5 FEBBE PERFORM ANCE OVER-THRESHOLD
Item Description
Alarm name V5 FEBBE performance over-threshold
Alarm level Major
Alarm This alarm indicates fault at the electrical physical layer. The electrical signal
explanation received at the opposite end from the local end degrades, and there is BBE.
Related
V5
overhead
Alarm indication

Alarm cause


Remarks
interface (LOI)

TABLE 113 TU12 PJE+/PJE- PERFORMANCE OVER-THRESHOLD
Item Description
Alarm name TU12 PJE+/PJE- performance over-threshold
Alarm level Major
Alarm This alarm indicates fault of tributary pointer justification, tributary synchronous
explanation performance degrades.
Alarm board EPE1
Related
TU-PTR
overhead
Alarm indication
Higher-order pointer justification event (AU PJE+/AU PJE-) exists

Alarm cause
Fault of EPE1 board
Handle the higher-order pointer justification

Solutions

Remarks
interface (LOI)

TABLE 114 TU12 PROTECTION SWITCHING EVENT
Item Description
Alarm name TU12 protection switching event
Alarm level Minor
Alarm This alarm message occurs in the network protected by path switching. It indicates
explanation occurrence of lower-order path protection switching.
Alarm board CSA/CSE
Related
None
overhead
Alarm indication
When the CSA/CSE board detects higher-order path alarm on the optical line board,
the path protection switching will occur. And the "TU12 protection switching event"
Alarm cause alarm will be reported to EMS.
Handle higher level alarms.

Solutions
Logical functional block of the fault: the multiplexing functional block of lower-order
Remarks
interface (LOI)

TABLE 115 LOSS OF TIMING INPUT
Item Description
Alarm name Loss of timing input
Alarm category Synchronization alarm
Alarm occurs on the optical line board that extracts the clock. When the STM-N
signal raises alarms, the optical line board will notify the alarm status to the
CSA/CSE board, and the CSA/CSE board will report the "loss of timing input"
alarm, and select the available higher-priority timing source as indicated by the
S1 byte. The alarm statuses include: loss of signal at the optical interface
(LOS), loss of frame (LOF), and out of frame (OOF), multiplex section alarm
indication signal (MS-AIS)
Alarm
For the 2 MHz or unframed 2 Mbit/s external clock, when the corresponding
explanation
external clock inlet raises alarms, the "loss of timing input" alarm will be
reported. The alarm status includes: loss of signal (LOS) at the electrical
interface.
For the framed 2 Mbit/s external clock, when the corresponding external clock
inlet raises alarms, the "loss of timing input" alarm will be reported. The alarm
statuses include: loss of signal (LOS) at the electrical interface, LOF, OOF, and
AIS.
Alarm board CSA/CSE, SCI

Related
S1
overhead
Board: The yellow ALM1 indicator light is constantly on.
Alarm indication
Fault of the optical line board that extracts the clock

Fault of the external clock import source and the external clock import part
Alarm cause
CSA/CSE board fault
Motherboard fault
Resolve the alarm of optical line board, and the alarm of CSA/CSE board will
Solutions disappear along automatically
Check the cable of external clock; replace the external clock source
The alarm derives from the optical line board which is set to extract the clock.
Remarks
Alarm source is the external clock inlet ( the external clock inlet of the SCI board)

TABLE 116 LOSS OF TIMING OUTPUT
Item Description
Alarm name Loss of timing output
Alarm category Synchronization alarm
Invalid system clock signal is detected

The CSA/CSE board is reset
Alarm If the reports can be sent to NCP normally, it indicates that a fault in the
explanation constant-temperature crystal oscillator of the CSA/CSE board has caused output
clock signals to be invalid.
If the reports cannot be sent to NCP normally, it indicates that the CSA/CSE
board logic has become invalid.
Alarm board CSA/CSE, SCI

Related
None
overhead
Board: The yellow ALM1 indicator light is constantly on.
Alarm indication
Alarm cause System clock signal failure of the CSA/CSE board
Solutions Replace the CSA/CSE board
Remarks The alarm derives from the CSA/CSE board

TABLE 117 POWER SUPPLY FAULT
Item Description
Alarm name Power supply fault
Alarm category Equipment alarm
Alarm The secondary power supply input is faulty, and the power fault alarm is reported at
explanation the EMS.
Alarm board None
Related
None
overhead
Board: The red ALM2 indicator light is constantly on.
Alarm indication
Alarm cause Improper connection of power cable
Solutions Reconnect the cable
Remarks The alarm derives from the NCP board
TABLE 118 BOARD OUT OF POSITION
Item Description
Alarm name Board out of position
Alarm
The board is unplugged or is out of position
explanation
Alarm board All the boards except the NCP board
Related
None
overhead
Alarm indication EMS: Open the board management dialog box, there is red alarm identifier.
Alarm cause The board is unplugged.
Solutions Plug the board.
Remarks None

TABLE 119 BOARD TYPE MISM ATCH
Item Description
Alarm name Board type mismatch
Alarm
This alarm indicates that the NCP board lost the ability to manage other boards.
explanation
Alarm board All the boards except the NCP board
Related
None
overhead
Board: The red alarm indicator light is off, and the green indicator light does not
Alarm indication
flash.
The EMS configuration disagrees with the hardware version
Fault of board self-test
Alarm cause
Fault of board hardware
Communication failure between NCP board and the alarm board
Modify the EMS configuration to comply with the hardware version.
Reset the board
Solutions
Replace the board
Reset or replace the NCP board
Remarks None
TABLE 120 ETHERNET PHYSICAL ELECTRICAL INTERFACE – ETHERNET PORT

DISCONNECTED
Item Description
Alarm name Ethernet physical electrical interface – Ethernet port disconnected
Alarm This alarm indicates interruption at the Ethernet side, and the local end receives no
explanation Ethernet signal from the external equipment.
Alarm board SEC
Related
None
overhead
Board: The red alarm indicator light is constantly on, the yellow indicator light of the
Alarm indication SEC board Ethernet port is off.
The user port has been started in the EMS, but is not connected with the external
Alarm cause
equipment through cable.
Solutions Use cable to connect the user port with the external equipment.
Remarks None

TABLE 121 LOSS OF RECEIVED SIGNAL AT THE ETHERNET PHYSICAL OPTICAL INTERFACE
Item Description
Alarm name Loss of the receiving signal at the Ethernet physical optical interface (LOS)
This alarm indicates interruption at the physical layer of the Ethernet optical
Alarm
interface and the external equipment; the local end receives no optical signal from
explanation
the external equipment.
Alarm board Ethernet board
Related
None
overhead
Board: The red alarm indicator light is constantly on; the green GE indicator light of
Alarm indication the Ethernet board is off.
Fault of the external cable

Alarm cause Fault of fiber pigtail or coupling components
Fault of the optical module of the local-end Ethernet board
Take care of the cable.

Solutions Replace the fiber pigtail or coupling components.
Replace the local-end Ethernet board
Remarks None


Chapter 6
Troubleshooting

General procedures and basic principles of troubleshooting
Typical approaches and solutions of fault locating
Typical faults, their causes, and solutions
Troubleshooting Procedures
The troubleshooting flow chart is shown in Figure 4.

FIGURE 4 TROUBLESHOOTING PROCEDURES
Find a fault and an alarm

Equipment room
maintenance personnel
Request related personnel for

troubleshooting
Equipment room
Is No
troubleshooting
successful?
Inform local ZTE office of

the fault and the alarm
Equipment room
On-call troubleshooting by
local ZTE office
Local ZTE office/ equipment
room maintenance personnel
Yes Is No
troubleshooting
successful?
On-site troubleshooting by local

ZTE office
Yes Project maintenance personnel
/
equipment room maintenance
personnel
Make a fault record after

equipment recovery
Equipment room maintenance

personnel
Basic Principles of
Troubleshooting
In handling the equipment faults, the maintenance staff should follow
these basic principles: observe first, then query, think, and take action
finally.
Observing
After arriving at the site, the maintenance personnel should first observe
the fault phenomena carefully including the faulty point, alarm reason,
severity level and damage level. Only by fully considering fault reasons of
the equipment, can one feel the essence of problem.

Chapter 6 - Troubleshooting
Query
Put questions to onsite operators after observing fault phenomena. Check
whether there is any direct cause of the fault, such as data modification,
file deletion, circuit board replacement, power supply fault or lightening.
Thinking
After observing the symptoms and querying the operators, the
maintenance person can analyze by using his own knowledge. Locate the
fault, find the faulty point, and work out the fault cause.
Action
After locating the faulty point through above given three steps, the
maintenance staff or technician can remove the fault by performing proper
fault eradication procedures, e.g., by modifying the configuration data or
by replacing the board.
Basic Considerations for Fault

Locating
This section describes the common fault causes and the basic principles of
fault locating.
Causes
The common fault causes include: engineering problems, external causes,
improper operations, equipment interconnection problems, and equipment
problems.
Engineering Problems
Project 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, which
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, which
results in equipment fault. Such factors do not include transmission
equipment, but they do include:
1. Power failure, e.g., equipment power failure, too low supply voltage.
2. Switch fault.
3. Fiber fault: Performance deterioration of fiber due to its wear and tear,
fiber cut, ill contact of fiber connector.
4. Cable fault, e.g., relay dropped or broken due to ill contact of cable
connector.
5. The equipment is improperly grounded.
6. The equipment 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

Various services are transmitted over the transmission equipment, which
is connected to various devices. In addition, different services require
different performance of transmission channels. There are equipment
faults, which are usually derived from improper equipment interconnection.
The interconnection problems include:
1. The cable’s connection is faulty.

2. The equipment’s improper grounding.
3. Out-of-sync clock between the transmission and switching networks
4. Inconsistent definition of overhead byte in SDH frames structure.
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 damage 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 some certain point/PCB, or the fault occurs because of external
causes.

Principles of Fault Locating

Since the transmission equipment covers the sites which are located far
away from each other, it becomes critical to locate the fault to the specific
site accurately. After finding the faulty site, concentrate on its
eradication/troubleshooting.
General principles of locating faults:
1. Check the external factors first, which can be fiber cut, switching fault,
or power failure, and after that consider the transmission equipment
faults.
2. Try to find out the faulty site first, and then locate the fault to the
board.
3. The fault of optical line board causes alarms of tributary boards.
Therefore, consider the line first and then consider the tributaries.
While analyzing alarms, consider the higher priority alarms first, and
then analyze the lower priority alarms.
Common Methods of Fault

Locating
The common methods of fault locating include: observing & analysis
method, test method, unplugging/plugging method, replacement method,
configuration data analysis method, reconfiguration method, instrument
test method, and processing by experiences method.
Observation & Analysis Method

When the system gets faulty, alarm information will appear on the
equipment and at EMS. Observing the status of alarm indicator light on
equipment will help to find the fault timely.
When a fault arises, EMS will record abundant alarm events and
performance data. Analyze the information, combine it with the overhead
byte in SDH frame structure and the SDH alarm principle, to determinate
fault type and fault location primarily.
While collecting the alarm information and performance information

through EMS, make sure to set the current running time of NEs
synchronous to EMS time. Deviation of time setting will result in incorrect
or delayed collection of alarm and performance information of NEs.
Test Method
When the networking, service and fault information are complicated or
when equipment faces unidentifiable faults without reporting any clear
alarm or performance information, use the maintenance functions

provided by EMS to test the faulty point and fault type. The following
content takes loop-back operation as an example.
Before performing loop-back operation, you need to determine the NE,

board, path and direction of loop-back. Since the paths concurrently faulty
are usually correlated to some extent. While selecting the loop-back path,
select one faulty NE, one faulty traffic channel, and then perform the loop-
back operation in each direction of selected traffic channel for analyzing.
When performing the loop-back operation, break up the business process

of the faulty traffic channel, draw a service route map, set out the service
source/sink, NEs that the service passes through, paths and timeslots
occupied, and then perform loop-back in each segment to locate the faulty
NE. After locating the fault to the NE, perform loop-back at the line side
and tributary side to locate the possible faulty board. Further, confirm the
faulty board with other methods, and replace it.
The loop-back operation does not require any in-depth analysis of alarms
and performance. It is a common and effective method for locating the
fault point. However, it may affect the services.
Unplugging/Plugging
After locating fault to specific board, unplug the board and external
interface connector. Plug them back to check ill contacts or abnormal
board status.
Warning: Ensure to conform with the operation specifications while

plugging/unplugging the board lest board get damaged, or may cause other
problems due to improper handling.
Replacement Method
Replacement method means replacing suspected faulty piece of equipment
with a new one such as a segment of cable, a board or a equipment, to
troubleshoot the fault. The replacement method is applicable to the
following circumstances:
1. Check the problems of external transmission devices, which may be:

the fiber, trunk cable, switch, or power supply equipment.
For example, 2 M interface of a tributary board raises the “CV
performance over-threshold” or “Loss of 2M signal” alarm, and it may
be the switch or trunk fault; try troubleshooting by replacing it through
normal procedures. If the alarm transfers after replacement, it
indicates that external trunk cable or switch may be faulty. If the fault
persists even after replacement, it may be a transmission fault.
2. Check the problem on board after locating the fault to a specific site.
For instance, if an alarm occurs because of faulty optical line board,
the receiving fiber and transmitting fiber may be connected inversely,
and fault can be removed just by correcting the fiber connection.

3. Resolve the power supply and grounding problems.

The replacement method is simple and demands less for maintenance staff.
It is more practical but demands availability of spare parts and accessories.
Configuration Data Analysis Method

Due to change of equipment configuration or improper operation of
maintenance staff, the equipment configuration data may be damaged or
changed, which will result in faults.
In this case, after locating the fault of distant NE site, query the current
configuration data and user operation log of equipment to analyze the
fault.
By configuration data analysis method we can find and analyze causes of

faults after locating the faulty NE. However, this method takes relatively
longer time and is more demanding. This method is applicable to the
experienced maintenance staff that has good familiarity with the
equipment.
Reconfiguration Method
This method is used to locate fault by modifying the equipment
configuration. It is applicable to checking configuration error after locating
fault to a specific site. The modifiable configurations include timeslot, slot
and board parameters.
Caution: Before modifying the equipment configuration, back up the original

configuration and keep a detailed record of operations being performed for
convenience of fault investigation and data recovery.
Here is an example of applying the reconfiguration method:
1. A typical application of reconfiguration method is to resolve the pointer

justification problem. To locate the pointer justification problem,
change the clock source configuration and clock extraction direction.
2. If you suspect that a tributary board or some of its paths are faulty,
configure the timeslot to another path or another tributary board. If
you suspect that a slot on the motherboard is faulty, check it by
modifying the slot configuration.
3. In the upgrading, expansion and reconstruction, if you suspect error in
new configuration data, deliver the previous configuration data for
check up.
The reconfiguration method is complicated and demands more for
maintenance staff. Therefore, it is only used when the spares are short
and need to recover the services temporarily, or to tackle the pointer
justification problem. It is not recommended in ordinary circumstances.

Instrument Test Method

The instrument test method refers to quantitatively testing the working
parameters of equipment by means of instruments. It is mostly used for
checking the external problems of transmission devices and problems of
connecting with other devices.
Here is an example of conducting the instrument test:
1. Use a multi-meter to test whether the supply voltage is high or low.

2. If the transmission device cannot be connected with other devices, and
it is suspected that the equipment grounding is improper, use a multi-
meter to measure the voltage between the transmitting signal ground,
and the receiving signal ground. If the voltage value is higher than 500
mV, you can conclude improper grounding of equipment.
3. If the transmission equipment cannot be interconnected with other
equipment and it is suspected that the interface signal is not
compatible, use a signal analyzer to observe whether the frame signal
is normal, whether the overhead bytes are normal, whether any
abnormal alarm occurs, so as to find out the cause of the fault.
This method features high accuracy, but it requires highly accurate
instruments and demands more for maintenance personnel.
Processing by Experiences
At some special occasions, the equipment board gets into abnormal
working status resulting in service interruption, ECC communication
interruption, but the equipment configuration data stays completely
normal due to instant abnormal power supply and strong external
electromagnetic interference. Practice tells us that in such cases, we can
troubleshoot and recover effectively in time by resetting board, restarting
the equipment, and by delivering the configuration data again..
The method demands thorough examination of the causes, and it is not

recommended until in emergencies. While handling complex/tricky
problems, the maintenance staff should request technical support from
nearest service center and try to eliminate the latent risks.
Typical Troubleshooting
The ZXMP S385 may come across some typical faults which are:
communication fault, service interruption, BER fault, synchronization fault,
orderwire fault, equipment interconnection fault and EMS interconnection
fault.
Note: Communication faults generally refer to faults like path interruption or bit
error, and fault at both the switching side and transmission side. The faults
described hereunder other than communication faults usually occur in transmission
equipment.

Communication Fault
Causes
The faults at the transmission equipment or switching equipment result in
interruption of communication services or in large number of bit errors.
Troubleshooting Procedure
The troubleshooting flow is shown in Figure 5.
FIGURE 5 COMMUNICATION FAULT TROUBLESHOOTING FLOW CHART
A fault occurs
On switch side
Fault analysis and
location
Cooperate with switch

On transmission side team in troubleshooting
Perform transmission
troubleshooting
4. After the fault occurs, activate the standby path to ensure normal
running of existing communication services.
5. Check whether the fault is at transmission side or switching side.
To locate the fault point, recommend to use the test method and
perform the loop-back operation. To perform loop-back, either perform
hardware loop-back at the DDF, or perform software loop-back for
transmission equipment and connect a BER tester to test the signal in
path loop. In case of software loop-back, you must tell tributary loop-
back from AU loop-back, and terminal side loop-back from line side
loop-back type.
6. If the fault is located to the switch side, coordinate with the switch
staff to handle it. If the fault is located to the transmission side,
determine the category of transmission fault according to Figure 6.

FIGURE 6 FAULT CATEGORY DETERMINATION FLOW CHART
A transmission
fault occurs
Fault classificationin EMS
Error Clock synchronization

Service interruption problem
Perform troubleshooting Perform troubleshooting on

on service interruption clock synchronization problem
Perform error
troubleshooting
7. After identifying the fault type, remove the fault according to

corresponding troubleshooting procedure.
Service Interruption Fault

Causes
1. External causes: power failure; fiber or cable failure.
2. Improper operation: due to improper operation, loop back is
mistakenly set for optical/tributary path or the configuration data is
modified.
3. Equipment concerned causes: The board fails or has poor performance.
1. Connect the BER tester to the tributary receiving/transmitting port of
the faulty path at the local NE, and use test method to perform loop-
back of the path segment by segment to locate the faulty NE, as
shown in Figure 7.
FIGURE 7 LOOP-BACK SEGMENT BY SEGMENT
Remote Remote
Local Local Local
Local NE Adjacent NE Next adjacent Termniating

NE NE
If the fault is located to the higher order path, perform the following
operations consecutively:
Perform terminal-side loop-back for the faulty AU from the faulty
optical direction at the local NE.
Perform line-side loop-back for the faulty AU of the local optical
path at the adjacent NE.

Perform terminal-side loop-back for faulty AU of remote optical

path at the adjacent NE.
Perform line-side loop-back for faulty AU of the local optical path at
next adjacent NE.
Perform terminal-side loop-back for faulty AU of the remote optical
path at next adjacent NE, and so on.
Perform line-side loop-back for faulty AU of the local optical path at
the terminating NE.
Perform line-side loop-back for the corresponding tributary at the
terminating NE.
If the fault is located to the lower order path, perform the following
operations consecutively:
At the adjacent NE, next adjacent NE, ..., terminating NE, modify the
tributary timeslot configuration at the local end from “Optical path cut-
through” to “Lower tributary” segment by segment; and perform line-
side loop-back for the reconfigured tributaries in turn.
2. Observe status of the equipment indicator lights and analyze the fault.
If both the red and green indicator lights of a board are off and other
boards are normal, this board may be invalid or faulty. Replace this
board.
3. Analyze the alarms and performance events of EMS. According to
alarms and performance events caused by faults, locate the faulty
board and replace it.
Step 2 and step 3 can be performed concurrently, and can be combined
with the unplugging/plugging method and the replacement method.
Typical Faults and Analysis

1. Symptom: Service cannot get through, and the “loss of optical signal”
alarm is reported at EMS.
Analysis and handling:
Check the status of fiber to see if the fiber slot is connected
improperly.
Check the received optical power of the optical line board, test
whether the receiving/transmitting light is normal and adjust the
optical interface to see whether alarm disappears.
Check the receiving/transmitting light of optical line board at
preceding point, test whether the receiving/transmitting light is
normal and adjust the optical interface to see whether the alarm
disappears.
If the alarm persists after above given inspections, follow the
procedures described in this section, perform self-loop test on the
optical line board, so as to locate the faulty point and remove the
fault.
Waring: If the received optical power is too strong, it will result in signal
deterioration or service blockage. Therefore, when the sites are closely located, an
optical attenuator must be installed in between them on the optical path.

2. Symptom: Service is blocked and no alarm is reported.

Check whether loop back is performed between the blocked sites. If
loop back exists between optical line boards, cancel the loop back
and connect them properly.
If the not loop back exists, follow the service interruption fault
troubleshooting procedure to perform self-loop test on optical line
board, so as to locate the fault point.
Determine the faulty optical line board and conclude that this board
incurs transmitting/receiving fault, because, when an optical line
board receives no optical signal and cannot detect any fault itself, it
will not raise alarm and the opposite-end optical line board cannot
receive any remote alarm either.
3. Symptom: The transmitted optical power of the optical line board is
normal, but the service is interrupted. The “Multiplex section AIS”
alarm is reported at the receiving NE and “Multiplex section RDI” alarm
is reported at the transmitting NE. Loss of multiplex section occurs
even if performing self loop-back using fiber pigtail.
The symptoms show that the optical line board gives light normally but
does not scramble. In this case, use the empirical method, reset
software or re-plug the board to solve the problem. However, it is
preferable to replace the optical line board.
4. Symptom: 2 M service is blocked
Check the quantity of blocked 2 M services. If the quantity is
considerable, consider the optical path problem first.
If only one or several 2 M services are blocked, check whether the
timeslot is configured correctly or not. Execute the download command
in EMS to apply the correct timeslot configuration data to the tributary
board. If the tributary is still out of signal, reset the tributary board
and the alarm will disappear if there is no other hardware problem.
If the service is still blocked after the above step, follow the
troubleshooting procedure to perform terminal-side loop-back for the
2M tributary and connect a BER tester.
If the “Loss of 2 M signal” alarm persists on BER tester, the causes
may be improper interface of 2 M interface, 2 M line broken or the
improper welding of the coaxial connector of cable distribution
frame. Replace the interface to fix the problem.
If the BER tester alarm disappears, the problem lies in 2 M
interface board, CSA/CSE board or motherboard. Replace 2 M
interface board/CSA/CSE board/motherboard to fix the problem.
If the fault locates at 2 M interface board interconnected with third-
party equipment, the fault cause may lie in different ground voltage
between the interconnected equipment and the transmission
equipment. In order to eliminate the influence of voltage difference,
following methods are applicable:

Check the ground grid and make consistent ground voltage

between transmission equipment and the interconnected
equipment.
Ground the transmitting end of 2 M signal of the transmission
equipment and interconnected equipment, and do not ground the
receiving end.
Connect a 0.1 u~0.5 u capacitor in series with interconnected 2 M
signal cable.
5. Symptom: After the ZXMP S385 gets into service, the 2 M service is
blocked, no alarm or performance event is detected at the EMS, and no
bit errors are detected via the BER tester in the offline test.
The main cause for this symptom is that the ODF is not grounded or
the transmission equipment does not share ground with the switch,
which results in a significant voltage difference. To fix this problem,
check the ground grid, and connect the ground cable properly.
Note: When the tributary service is blocked, check the connections of ground
cables.
Bit Error Fault

Causes
1. External causes: The optical fiber connector is not clean or is not
correctly connected; the optical fiber incurs deteriorated performance
and an excessive loss; the equipment is grounded improperly; there is
a strong interference source nearby; the equipment works in a high
temperature environment without proper heat dissipation.
2. Equipment causes: The CSA/CSE, line board, and tributary board are
not well interoperable; the clock synchronization performance is
inferior; board failure or underperformance.
Locating the Faulty Point

Related overhead bytes include B1, B2, B3, and V5 bytes. Their priorities
ranking in a descending order are B1→ B2→ B3→ V5. For the performance
events reported by EMS, the higher-level performance events should be
handled first. Go on to handle the lower level performance events if they
are still reported after handling the higher-level performance events. In
normal cases, ensure the performance value collected at any board by
EMS is zero whenever the service is running.
1. Query the performance of faulty NE. If B1/B2 performance events exist

on EMS, it indicates that the optical path is improper. Follow the
procedure given below to locate the faulty point:

Check whether the received and transmitted optical powers falls in the
index range and the received optical power is less than the receiver
sensitivity or there is no incoming light; then check the fiber pigtail
connection and coupling conditions from the optical board inlet to the
ODF.
If the received optical power on the ODF at both transmitting and
receiving ends is too low or without incoming light, it indicates that the
optical line is faulty. Contact the optical line maintenance staff to fix
the problem in time and then check the fiber pigtail self-loop optical
board input/output to see whether the fault lies in local or opposite NE
optical interface. Self-loop must ensure that the optical received power
falls within the range allowed by this optical board (between overload
point and the received sensitivity).
Warning: Before testing the optical cable by means of OTDR, unplug the
connection fiber pigtail from the corresponding optical interface lest the strong
light emitted by OTDR damages the optical interface.
Caution: While using a fiber pigtail to perform optical interface self-loop, add an
optical attenuator between the receiving and transmitting optical interfaces to
ensure that the received optical power at optical interface falls within the allowed
range of optical interface (between received sensitivity and the overload optical
power).
If no B1/B2 performance event is reported after performing self-loop of

local-end optical line board it means the local-end optical line board is
normal. Similarly, if no B1/B2 performance event is reported after
performing self-loop of the opposite optical board, it means the
opposite optical board is normal.
2. Check the performance of faulty NE, if no B1/B2 is reported at EMS
and only B3 is reported, it indicates improper high order path and the
fault lies in CSA/CSE or tributary board. Perform the CSA/CSE control
operations in EMS to switch over to CSA/CSE and locate the faulty
board.
3. Check the performance of faulty NE. If only V5 performance event
exists on EMS, it indicates that the lower order path is improper and
the tributary board is faulty. In this case, reconfigure the timeslot to
lower tributary of adjacent NE or perform loop-back for AU to locate
whether the fault lies in local or opposite tributary board.
1. Use the test method to locate the source of bit error as instructed in
Troubleshooting Procedure.
2. If the bit error is derived from the optical line board, analyze the bit
error performance event of the optical line board to remove the line bit
errors. The procedures are:
First check the external factors, e.g., improper grounding, too high
working temperature, too low/high received optical power of optical
line board.

Then observe the bit errors of optical line board. If all the optical
line boards at one site have bit errors, the CSA/CSE board of this
site might have failed. Replace the CSA/CSE board. If only the
optical line board reports bit errors, the fault may lie in this optical
line board, the opposite line board or fiber.
3. If the bit errors derive from the tributary board, analyze the
performance event of the tributary board to remove the tributary bit
errors. If only the tributary has bit errors, the tributary board or the
CSA/CSE board may be faulty, so replace the tributary board or the
CSA/CSE board.
Caution: The transmission maintenance staff must analyze the equipment

performance carefully, and locate the faulty board by analyzing the mechanism of
basic SDH overheads such as B1/B2/B3/V5. Do not restart or replace the faulty NE
without analysis.

1. Symptom: Assume site A is connected with site B point to point.
Depending on the quantity of the B1/B2/B3 bit errors reported by EMS,
the troubleshooting methods vary and are described as under:
In case of sporadic minor bit errors on the optical line board of site A
which occurs regularly, may be several times in 24 hours, once in few
days or occur continuously averaging one BBE error per second without
B2/B3/V5 bit errors (one B2 BBE with three to five B1 BBEs, one B3
BBE with three to five B2 BBEs), or occasionally one V5 BBE at most,
these will impose little influence on the service.
First, check whether the received optical power of the optical line board
at site A is normal, whether it is too low (continuous major B1 BBE will
occur but it will be without major bit errors). If this is the case, check
whether the optical cable loss and the transmitted optical power at
point B are abnormal. If the optical received power of the optical line
board at site A is normal, it is concluded that the optical line board at
site B is faulty, which may be because of optical board performance
problem or very small dispersion tolerance of transmitting optical
module (caused by the fiber length > 100 km). If the bit errors do not
occur frequently, it is recommended not to replace the board.
In case of sporadic bit errors on the optical line board at site A, which
occur regularly, several times in 24 hours or once in few days and
averaging at least five BBEs per errored second, with occasional instant
out-of-frame (the alarm duration is 5~6 second) and OFS, they are
major bit errors and will surely result in B2/B3/V5 bit errors (B2/B3/
V5 > three BBE/ES), imposing influence on all services. e.g., will
influence video-conferencing services by transient mosaic and loss-of-
frame. For the telephone or data services, they are usually
imperceptible to the users. The base station is usually normal.

Such bit errors impose imperceptible influence on services, but they

must be handled immediately by replacing the optical line boards.
The occurrence of major bit errors burst continuously on the optical
line board at site A, the out-of-frame alarms are reported frequently
and the unavailable time begins.
In case of such bit errors, the service cannot be guaranteed. These bit
errors will not disappear automatically once they occur and need to be
handled immediately by replacing the optical line boards.
Major B2 BBEs occur continuously on the optical line board at site A,
and the “Multiplex section signal degraded” alarms are reported
occasionally.
The severity of bit errors may relate closely with the temperature.
Weather of high temperature, no air condition in the equipment room
or equipment fan damage may result in frequent bit errors. There is no
B1 bit errors on the optical line board at site A at this time. Handle it
immediately by replacing the optical line board.
Warning: High working temperature of equipment will result in abnormal running

of the equipment. High temperature environment, air conditioning failure, cooling
fan failure, and air filter choking will result in frequent bit errors.
2. Symptom: Only a few 2 M tributaries have bit errors

Confirm that the EMS software works normally and the existent bit
errors are not reported mistakenly.
Clear the performance count of this site and query its performance
value.
If the bit error performance of corresponding tributary is constantly
zero then use the software loop-back test method. Visit the site to
check whether 2 M board interface of both sites and 2 M cables are
connected normally.
If only the bit errors of local site are reported without remote bit error,
it indicates that the bit errors are derived from the local site. Check the
tributary performance of the opposite site, which should report remote
bit error indication. In this case, check whether the connections of the
boards at local site are correct. If they are correct, change the timeslot
configuration of tributary, the tributary interface or change the
tributary board to fix the problem.
If the local site bit errors and occasional remote bit errors are reported
together but only the local site bit errors are reported at the opposite
site, it indicates that fault lies in opposite site. Handle it as instructed
in the preceding paragraph.
If both the local and opposite sites have local and remote bit errors,
handle local site and opposite site separately. Check the board
performance of both sites that the services have passed through, and
handle them as described in previous lines.

3. Symptom: Almost all 2 M tributaries have bit errors

Confirm that the EMS software works normally and the existing bit
errors are not reported mistakenly.
Collect the current alarm information, and check if any other higher
priority or severer alarms occur.
Query the timeslot configuration of tributary reporting the bit errors
and locate the faulty site.
Query whether the optical line board reports bit errors and locate the
faulty point. While querying, discriminate the local bit errors from
remote bit errors.
The possible causes of large amount of bit errors on 2 M tributaries are:
first the clock problem, then the optical line board fault, finally the
CSA/CSE board or 2 M tributary board fault. Take the following actions
sequentially: switch the clock source; if bit errors persist, check the
optical launched/received power of optical line board; if they are
normal, check other boards or traversed sites.
Clock Synchronization Fault

Causes
1. External causes: The optical fiber is wrongly connected or the
external clock is of poor quality.
2. Improper operation: Wrong clock source configuration, such as two
clock sources co-exist in a subnet; wrong setting of the clock source
priority; mutual extraction of clock.
3. Equipment problem: Optical line board fault, inferior line clock; clock
board fault, inferior clock source; CSA/CSE board fault, inferior working
clock allocated to the boards.
1. Check the clock configuration of EMS; avoid mutual extraction of clock
caused by human factors. Deliver correct clock configuration to the
NCP board to keep EMS data consistent with the NCP data.
2. Check through the EMS whether the optical path and tributaries have
AU PJE/TU PJE performance values. If only TU PJE exists in EMS, it
indicates that the tributary board is faulty. Just replace it.
3. If AU PJE/TU PJE exists concurrently, handle the AU PJE first and then
go on handling TU PJE if any.
Optical line boards and clock boards are the possible boards, which
generate AU PJE, and they are handled in the following procedure:
Check the received optical power, and query B1/B2 performance

value. If the received optical power is normal, and B1/B2
performance values of the optical line board are zero, it indicates
that AU PJE derives from inside the NE.

Check the status of clock locking at the CSA/CSE board. If the clock
cannot be locked, switch the standby clock board to active through
EMS operation.
If the clock can be locked and AU PJE disappears after the
switching of CSA/CSE board, replace the original active CSA/CSE
board.
If the clock cannot be locked and AU PJE persists after switching
the CSA/CSE board, change the optical direction of the extraction
line clock. If AU PJE disappears, it indicates that the fault lies in the
optical interface of the original optical line board or that of the
opposite NE.

1. Symptom: The pointer justification over-threshold alarm is reported
at the EMS.
The pointer justification alarm may occur at either unlocked or locked
clock status. In case of pointer justification alarm, check whether the
clock locking status is normal and handle the unlocked clock first.
Unlocked clock
Check whether any external factors are in effect, e.g., fiber cut.
Check whether the network data configurations and grade settings
of clock source are correct. Also, check if the clock becomes
unlocked due to clock switching failure upon fiber disconnection or
forced clock switching on the EMS. Check whether both sides are
wrongly configured with a line clock extracted from the peer and
whether the clock switching rules are missed. If data configuration
is correct, the fault usually lies in the clock source being in use
after switchover. A typical cause is hardware fault of board. Check
the optical line board or CSA/CSE board of local site and opposite
site. In case of fault, replace the faulty board.
If no clock switchover occurs but the clock is unlocked, a typical
cause is that the optical line board or CSA/CSE board is faulty.
Consider to replacing them of the local/opposite end.
Unlocked clock of the site configured with external clock
If unlocked clock occurs at site configured with external clock,
check the data configuration according to the operations described
in the preceding paragraph to see whether multiple strata of
external clock sources are configured mistakenly.
If no data error is found, check the CSA/CSE board, external clock
line, and external clock source, and consider replacing the faulty
board or cables.
If no external clock switchover occurs but the clock is unlocked, a
typical cause is that the board or line is damaged in the process of
operation. In this case, consider replacing the clock board, external
clock cable, or external clock source at the local point.
Inferior locking of clock

If pointer justification occurs in case of normal clock locking, it

indicates inferior locking of the clock. When the network is not
synchronous, the system compensates for it in a self-cure approach of
pointer justification. Network out-of-sync is usually caused by fault of
certain boards, e.g., clock board, optical board or by ill contact of the
motherboard slot. Pointer justification is not transferred but terminated
at the local end. Adjust or replace the optical line board or CSA/CSE
board at the local end or adjacent NE, to fix the problem.
2. Symptom: The “Loss of timing input” alarm is reported at the EMS.
The EMS detects loss of timing input, which indicates that the local
CSA/CSE board is normal. The causes include:
Fault of the external equipment. The opposite site CSA/CSE board
connected to this site is unplugged.
Fault of optical line board. Check the clock source configuration,
download the clock configuration, and reset the CSA/CSE board.
Loss of the local clock source. Check the clock source.
3. Symptom: The clock source of the NE is configured as line extraction
clock but the clock board cannot extract the line clock normally.
Query whether the “loss of timing input” alarm is reported at EMS. If
this alarm exists, it will be impossible to extract the line clock. After
resolving the alarm problem, the function of extracting line clock will
recover.
Query the utilization of SSM byte and the clock quality level via EMS.
When the clock quality level of ZXMP S385 was unknown and this
function was not enabled, the CSA/CSE board will deem this clock
source unavailable by default. In this case, modify the configuration via
EMS.
Query via EMS whether locked clock source is set or not.
4. Symptom: In EMS, the NE originally set as external clock source is
reported as extraction line clock.
The clock may be looped. In this case, troubleshooting varies with the
types of networking mode:
Chain network
Check via EMS whether the mutual extraction of NE clock is performed
on two fiber pairs. If the mutual extraction of clock is performed on
two fiber pairs and the clock source fails, the chain network clock will
be abnormal. Configure the clock source as mutual extraction of the
same fiber pair.
Ring network
Check via EMS whether the mutual extraction of NE clock is
performed on same fiber pair. If not, see preceding paragraphs to
modify the setting of extraction clock.

Check the extraction clock direction of all NEs that are set as
extraction line clock. If the extraction clock forms a closed loop in
same direction, it may result in clock looping. Change the clock
source configuration, e.g., set an NE in the ring network as an
internal clock to damage the clock looping. If the network is a
single ring and only one external clock source exists, set the NE
clock source type as external clock source and the only clock
source, and set all other NEs as bidirectional mutual extraction.
EMS Connection Fault

Causes
1. External causes: Power supply faults, such as equipment power
failure or too less power supply voltage; fiber faults, such as fiber
performance deterioration or too high loss.
2. Improper operation: There is wrong configuration.
3. Equipment faults: Network adapter fault, optical line board fault,
CSA/CSE board fault, or a lot of performance data is reported from NE
to the EMS resulting in ECC path block.
1. Check external causes, e.g., power failure or fiber performance
degradation.
2. Check whether the EMS configuration is correct or otherwise.
3. Use the test method to perform self-loop in each segment and locate
the faulty NE.
4. Use the alarm analysis method to check the optical board and CSA/CSE
board.

1. Symptom: The EMS cannot get connected to NCP through the Qx
interface. It cannot ping through NCP but can ping through itself.
Check whether the network cable works normally, and whether its type
is correct (straight-through cable or crossover cable).
Check whether the computer network configuration is correct. The EMS
can ping through itself, it indicates that the network adaptor is
correctly installed and the network configuration takes effect. The EMS
cannot ping through NCP; it indicates that the EMS computer, the NE
IP address and the subnet mask may be in different network section.
Set the all the bits of the DIP switch of NCP to “ON”, setting the NCP to
be in DOWNLOAD status. Execute the t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1
command, and check whether the NE IP and server IP comply with the
EMS database configurations.
2. Symptom: Insufficient sub-manager management networks.


Check whether all the sub-managers have been started. If the ZXONM
E300 EMS runs on the UNIX platform, execute the command p s - e f
| g r e p s m g r to check whether they have been started; if the EMS runs
on the Windows 2000 platform, use the task manager to check it.
Check whether the NE is beyond the management capability of sub-
managers. It is recommended that the maximum number under the
management of each sub-manager should not exceed 100. If the
number exceeds this value, start another sub-manager.
3. Symptom: EMS is unable to manage the access NE, or other NEs
except the access NE.
The current EMS and NEs do not belong to the same network section.
For an NE in the IP protocol stack version, EMS and the NE belong to
same network segment. However, the user does not set IP address of
the access NE as default gateway or do not set a route.
There are redundant IP routes in the EMS.
4. Symptom: The EMS can only normally manage some NEs in the
network.
Check whether the unmanageable NEs are offline, and set the offline
NEs to online NEs.
Check whether the optical connections between NEs are correct.
Check whether NCP versions of the unmanageable NEs are correct. If
they are incorrect, re-apply the NCP applications which support this
EMS.
When EMS runs on the UNIX platform, check whether the system
parameters of m a x f i l e s a n d n f i l e s are correct.
5. Symptom: Confusion in IP area division leads to abnormal NE
management.
In actual networking, try not to divide any area or use the backbone
area under any circumstances. Generally, when there are too many
NEs on a network (e.g., over 64), the NEs should be divided into
different areas. When the number of NEs exceeds 128, they should be
divided into different areas. In this case, since the network section
division is wrong, it becomes difficult for EMS to monitor all the NEs.
Check whether all the NEs distributed in different areas are directly
connected with the boundary NEs in backbone area.
Confirm that the total number of NEs exceed 128 either in the
backbone area or in non-backbone area, and are directly connected
with the border NEs If this value is exceeded the normal management
becomes impossible. In addition, it is recommended that each border
NE is to be directly connected with the one in non-backbone area.
Confirm whether the NEs in backbone area are connected properly.

Since the ECCs cannot directly work with each other in non-backbone
area, and can only work via backbone area, so please check for the
failure of NE in the ECC path between the backbone area and the
boundary.
Try to reduce the border NEs. At times, dividing NEs into many areas
may complicate inter-area relationship.
Note: Refer to Appendix A for the definitions of NE IP address and the principles of
routing.
Orderwire Fault
Causes
1. External causes: The main power is off. The fiber is broken.
2. Manual causes: The OW board configuration or the optical line board
configuration is wrong.
3. Equipment concerned causes: The optical line board or the OW
board is faulty.
1. Check whether the optical path raises any alarm. Blocked optical path
will result in blocked orderwire.
2. Check whether the orderwire telephone is faulty. Use another
telephone for testing if necessary.
3. Check the OW board; observe the indicator lights and the EMS alarms.
Check whether the orderwire board gets faulty by using the
unplugging/plugging method and replacement method.
4. Check the configuration of the OW board and optical line board.

1. Symptom: The orderwire telephone cannot get through without
hearing any dial tone.
Check whether the optical line board raises any alarm. Resolve the
optical path alarm first, if any.
Reset the OW board at call originating point and the called site. Reset
the OW boards at the sites between originating and terminating points.
Check if the fibers at the sites are connected as the data configuration.
Check the phone sets.
Replace the OW board.
2. Symptom: Orderwire board group call cannot get through.
Check whether the group call is set in EMS software.

Reset the board, locate the faulty board and replace it.
3. Symptom: The orderwire call is accompanied by noise.
Check whether the orderwire is looped. If so, set the loop-back site as
control point.
Check the optical line board. Replace it if necessary.
Check the OW board. Replace it if necessary.
Check the telephone. Replace the faulty phone if necessary.
4. Symptom: The orderwire group call is accompanied by howl/echo.
More than two orderwire voice paths in the network will cause the
howl/echo in-group call, so that voice is self-excited and howl is
emitted.
Check whether the orderwire is looped. If so, set the loop-back site as
control point.
Check if the orderwire protection bytes in the interconnected optical
direction are set correctly. The orderwire protection bytes may vary in
different equipment, but the orderwire protection bytes of all the
interconnected optical interfaces must be identical.
Fan Fault
Causes
1. External causes: Fan cable failure, or ill contact between the fan box
and motherboard.
2. Equipment causes: Fault of NCP board or fan control board (FAN).
1. Observe the running status of the fan and check the connection of
cables and interfaces. Check if there is any fault caused by external
factors.
2. Check the FAN board, and observe the indicator lights on the fan plug-
in box panel, observe the EMS alarms. Use the unplugging/plugging
method and replacement method to check if there is any fault in the
FAN board or NCP board.

1. Symptom: The EMS reports FAN board out-of-position alarm.
i. Check whether the indicator lights on fan plug-in box panel are
normal. In normal case, the green indicator light is constantly on,
and the red indicator light is constantly off.

ii. Check whether the fan box is completely inserted into the fan plug-
in box.
2. Symptom: The EMS reports the alarm of FAN board running blocked.
i. Check whether the indicator lights on fan plug-in box panel are
normal. In normal case, the green indicator light is constantly on,
and the red indicator light is constantly off. If the red indicator light
is constantly on, it indicates that the fan running is blocked.
ii. Check whether the fan box is completely inserted into the fan plug-
in box.
iii. Replace the fan box.
Equipment Interconnection Fault

Causes
1. Incorrect connection of fiber or cable.
2. The equipment is interconnected with other manufacturers’ equipment,
and the equipment of one side is improperly grounded, or the
equipments of both sides do not share common ground.
3. The internal clocks of transmission network are synchronized and so
are the internal clocks of switching network, but the two networks are
not synchronized with each other.
4. Inconsistent definition of overhead bytes in the SDH frame structures
of different manufacturers.
1. Check whether the physical connections between the equipment are
correct. Avoid open solder point/cold joint of cable and ill cable contact.
2. Check the alarms and performance at both sides of interconnected
equipment, which help locating the fault.
3. Check grounding and the ground-sharing status of the equipment at
both sides.
Grounding problem is usually caused by two interconnected equipment
not sharing the ground properly. The grounding resistance fails to
reach the required index. The DDF is not grounded properly.
The equipment room usually adopts joint grounding. For the sites that
do not adopt joint grounding, conduct the test carefully during
hardware installation to ensure that the equipment at both sides share
common ground. Check the grounding status of shielding layer of the
coaxial port.
4. Check clock synchronization of whole network.
The switches and GSM equipment of some manufacturers impose high
requirements of clock synchronization throughout the network.

Through the SDH transmission network, if the clock of module office is

not synchronized with the clock of mother office, it may result in trunk
slip, dial-up access service interruption or even frequent call
interruption. Firstly, check if the clock of transmission equipment is
faulty. If it is normal, check whether the clock planning throughout the
network is rational. If not rational, adjust the clock synchronization
scheme, to synchronize clocks in the whole network.
5. Check for the consistency of overhead bytes definition in the SDH
frame structure of interconnected equipment.

Symptom: When the ZXMP S385 NE is connected with other SDH
equipment of ZTE, the orderwires between the NEs do not get through.
The orderwire overhead bytes and orderwire protection bytes are defined
differently in different type of SDH equipment. When the equipments are
interconnected, transfer of orderwire protection bytes will affect the
orderwire of whole network. Table 122 lists the orderwire protection bytes
of the ZTE SDH equipment.
TABLE 122 ORDERWIRE PROTECTION BYTES OF THE ZTE SDH EQUIPMENT
SDH Equipment Orderwire Protection Bytes

E2, F1, D12, and the byte at the
ZXMP S320, ZXMP S330, ZXMP S385,
intersection of the second row and the
ZXMP S380, ZXMP S390
ninth column.
E2, F1, and the byte at the intersection of
ZXMP S360
the second row and the ninth column.
Check whether the orderwire protection bytes in the interconnected optical

directions are set correctly. They are required to be exactly consistent.
Ethernet Service Fault

Causes
1. External causes: power supply fault, such as equipment powered off;
cable fault, such as broken fiber, wrong network cable connection,
wrong usage of crossover network cable and straight-through network
cable.
2. Improper operation: wrong Ethernet configuration, such as port
disabled, wrong VLAN configuration.
3. Equipment fault: fault of the optical line board and the Ethernet
board.

1. Get rid of the external causes, such as equipment powered off, broken
fiber, abnormal network cable connection.
2. Apply the configuration data analysis method to check if the Ethernet
board configuration is correct in the EMS.
3. Apply the replacement method to replace the faulty board with a
normal board.
Typical Fault and Analysis

When the SEC board of the equipment is applied to Internet visit or
enterprise network interconnection environment, the Ethernet service is
mainly the TCP high-level flow control service. The equipment serving as
the access point or convergence point loses lots of service. This section
uses the example shown in Figure 8 to analyze the typical fault.
FIGURE 8 CONNECTIONS OF SEC BOARDS
User Ethernet
5
System
port 1 SEC board 2
System
port 1 System
port 1
SEC board 1 SEC board 3
System
port 1
User Ethernet SEC board 4

User Ethernet
1 4
User Ethernet
2
User Ethernet
3
The SEC boards 1 to 4 are installed in different ZXMP S385 equipments.

The SEC board 1 sends Ethernet service from the system port 1 to the SEC
boards 2 to 4. During service transmission and reception, if the port rate
does not satisfy the bandwidth share principle, the later sent service will
not be able to grab matched bandwidth, and thus the service is lost.
The so called “bandwidth share" means that when multiple Ethernet

services flow to one system port, they share the bandwidth provided by
SDH. Handle the fault as follows:

1. In the EMS, enable the QoS function of the system port on the SEC
board at the access point or convergence point. For example, in Figure
8, enable the QoS function of the system port 1 on the SEC board 1.
2. Set service priorities and allocate bandwidth for the services flowing to
the system port at the convergence point. For example, in Figure 8, set
service priorities and allocate bandwidth for the system port 1 on the
SEC board 1.


Chapter 7
Maintenance Examples
This chapter describes typical equipment maintenance examples as

reference for maintenance personnel.
Complete Blockage of Service

due to Optical Cable Link
Interruption
System Overview
An office uses the ZXMP S385 equipment for its local transmission
networking. The overall network consists of six ZXMP S385 NEs, which
forms a path protection ring with chains. The transmission rate on ring 1 is
2.5 Gbit/s, the transmission rate of the link from F to C is 622 Mbit/s, and
the transmission rate on link from B to D is 155 Mbit/s. The network
architecture is shown in Figure 9. The central office contains the EMS
terminal and is located at NE E.
FIGURE 9 NETWORK ARCHITECTURE IN CASE 1
C 7# 10# B 10# A
7#
6# 7#
7#
11#
D
F
Ring 1

The optical connections on the chains are as follows:
The 11#OL4 of NE F connects to the 7#OL4 of NE A.

The 10#OL4 of NE A connects to the 7#OL4 of NE B.
The 10#OL4 of NE B connects to the 7#OL4 of NE C.
The 6#OL1 of NE B connects to the 7#OL1 of NE D.
The remaining NEs only have service configuration relation with NE E. The
service from A to E uses 1#AU on the link, service from B to E uses 2#AU
on the link, service from C to E uses 3#AU on the link, and the service
from D to E uses 4#AU on the link. The NE A is set to use the internal
clock, and the other NEs use bidirectional extracted line clocks by means
of S1 bytes.
Fault Description
The services from A, B, C and D to E are all interrupted. The 11#OL4 of NE
F reports “Loss of received 622 M signal”. The NEs A, B, C, and D are out
of management by the EMS.
Fault Analysis
The above alarm indicates that F receives no optical signal, which means
that the fault may lie in the optical board of A or F. However, there is
great possibility that the above faults are resulted from external optical
cable fault.
Troubleshooting
Use the index test method of optical power.
The troubleshooting procedure is as follows:
1. Measure the power of the input interface of the NE F 11#OL4, the

optical receive flange of ODF, and the optical cable termination flange
on ODF, level by level with a fiber optical power meter.
The fiber optical power meter displays no indication regarding
reception/transmission of optical power. Measure the optical power of
the optical transmit interface on 11#OL4 and got the reading of
-2.15 dBm. As NE F and NE A are 25 km apart and are connected with
the optical line board of L4.1, the measured value falls in the
transmission index range.
2. Carry out similar test with the fiber optic power meter in the
equipment room accommodating NE A. The result of optical received
power is the same. The optical launched power of 7#OL4 is -1.85 dBm.
3. Therefore, it could be determined that the external optical cable lines
are broken. Notify the user to handle it and assist the user to assign
the broken service to other equipment and lines.
4. Further work: Ensure that the 7#OL4 of NE A and 11#OL4 of NE F
work well. Perform self-loop at the receive interface and transmit

Chapter 7 - Maintenance Examples
interface of the optical board using fiber pigtail. Do make sure that the
optical power received from fiber pigtail by the receive interface of the
optical board falls in index range. If the “Loss of received 622 M signal”
alarm of this NE disappears, it indicates that the receive interface of
optical board is in good condition.
5. The users investigate and find out that the optical cable lines are
broken due to engineering construction negligence. The optical cables
can work normally after welding. Measure the optical power of the
receive interfaces of NEs A and F. If the results got are normal, plug
the fiber pigtails back to the optical line boards. Then the optical
channel is normal, and the alarms disappear.
Warning: The optical time domain reflector (OTDR) should be used by the users to
handle the faults of external optical cable lines. The transmit/receive fiber pigtail
on the optical board must be unplugged once the transmit/receive interfaces on
the optical boards of NEs A and F are proved in good condition; otherwise, the
strong optical power from OTDR would damage the optical devices on optical
boards.
B2 Bit Error due to High

Temperature
System Overview
A local transmission network uses the ZTE ZXMP S385 equipment for
networking. The overall network consists of two ZXMP S385 NEs, which
form a point-to-point chain with no protection at a transmission rate of
2.5 Gbit/s. The network architecture is shown in Figure 10. The central
office is located at NE B, and the EMS terminal is placed at the central
office.
A 3# 3# B
The connection relationship of the optical fiber is as follows: the

3#OL16 of NE A connects with 3#OL16 of NE B. The service between NE A
and NE B is configured to occupy sixteen AUs. The NE B is set as the
external clock, and NE A extracts the line clock.

Fault Description
The user reported bit error at the exchanging service layer and suspected
the fault lay in the transmission part. Check the EMS and find out that the
3#OL16 board of NE A reports lots of “B2, B3 BBE/ES/SES" performance
events, accompanying with the “MS signal degraded” and “B2, B3
BBE/ES/SES performance over-threshold” alarms. The 3#OL16 board of
NE B reports lots of “B2, B3 FEBBE/FEES/FESES" performance events,
accompanying with the “MS remote defect indication” and “B2, B3
FEBBE/FEES/FESES performance over-threshold” alarms.
Fault Analysis
Since there are B2/B3 and MS alarms, we can conclude that the fault lies
in the multiplex section. Check the environment and equipment condition
in the equipment room first. Then apply the higher-order fault locating and
handling method for troubleshooting.
Troubleshooting
Check the equipment, it is found that the fan of the equipment was
powered off by the user maintenance person. The board temperature is
very high which is suspected to be the cause of fault. Turn the fan on.
After ten minutes, check the EMS performance and alarm indication, the
fault disappears.
Fault cause: the board temperature is too high, resulting abnormal

running of chip, and thus causes bit errors.
B2 Bit Error due to Optical Board

Fault
System Overview
A local transmission network uses the ZTE ZXMP S385 equipment for
networking. The overall network consists of three ZXMP S385 NEs, which
form a link at a transmission rate of 622 Mbit/s with no protection. The
network architecture is shown in Figure 11, and the central office is
located at NE A.
7# 10# 7# 10#
A B C

The connection relationship of the optical fiber is as follows: The

7#OL4 of NE A connects with 10#OL4 of NE B, and the 7#OL4 of NE B
connects with 10#OL4 of NE C. 2 M services exit between these NEs.
Fault Description
The NEs alarms and performances queried in the EMS are as follows:
1. Check site A: The services between site A and site B, between site A
and site C have lots of low-order V5 BBE bit errors on the tributary,
and many B3 BBE and B2 BBE bit errors on the 7#OL4 line.
2. Check Site B: A lot of B3 FEBBE and B2 FEBBE are found on its
10#OL4 line. The service between site B and site A has lots of V5
FEBBE on the tributary, whereas the service between site B and site C
is normal.
3. Check site C: Only the service between site C and site A is found to
have lots of V5 FEBBE on the tributary.
Fault Analysis
1. Locate the faulty NE first
The fact is that bit errors occur between sites A and B, and between
sites A and C, whereas the sites B and C are trouble free. By the above
fact, it can be concluded that fault lies somewhere between sites A and
B because all the services with bit errors pass this route. It is uncertain
yet whether the problem lies in site A or site B, or in the optical
channel. This needs an analysis of the performance data.
2. Analyze performance data on the line.
There are three types of monitoring overhead bytes on the line: B1, B2,
and B3. These bytes respectively monitor the quality of route from
their originating points to their terminating points. Byte B1 monitors
the route between the regenerator sections of two sites, B2 monitors
the route between the multiplex sections of two sites, and B3 monitors
the route along a certain high-order path between two sites. Obviously,
the routes monitored by B3 include those monitored by B2 and B1, and
the routes monitored by B2 include those monitored by B1.
There is no problem on the route between the regenerator sections of
both sites since the bit errors only exist in B2 and B3, which also
indicates that the optical channel is normal.
The existence of B2 error bits indicates that the trouble is on the route
between multiplex sections of both sites. Site A has background block
error (BBE), and site B has far end background block error (FEBBE)
which clarify that bit errors are detected from site A. However, the bit
errors are monitored in downlink signal stream, which indicates that
the bit errors of site A may have resulted from the receive end of this
site, or from the transmit end of opposite site, i.e. site B. Therefore,
we can not conclude that site A is faulty.

Troubleshooting
Locate the fault by eliminating trouble free sites one by one. Conduct a
self-loop test of the westward optical channel at site A, and the bit errors
of this site disappear. So the problem does not lie in site A. When the
optical board of site B is replaced, the bit errors throughout the network
disappear, hence solves the problem.
Tips
In the process of analyzing this case, we introduce a hypothesis based on
the coverage relationship of the routes detected by B1/B2/B3 bytes, that
is: B1 bit error introduces B2 and B3 bit error, and B2 bit error introduces
B3 bit error.
In fact, this rule is not absolutely right, because no coverage relation

exists among the contents monitored by these three kinds of bit errors,
though coverage relation exists among the routes monitored by them. B1
monitors all the bytes of the STM-N frame, B2 only monitors those bytes
other than the regenerator section overhead, and B3 only monitors the
high-order path VC-3/VC-4. The association between them may disappear
when bit errors occur to the overhead byte. For example, the bit error that
is detected in B1 of the regenerator section overhead byte could not be
detected in B2 or B3.
In practical maintenance, we found that bit error rarely results from the
overhead byte. Therefore, it is a general experiential method to locate a
fault through the route coverage relation of B1/B2/B3.
155 M Optical Interfaces

Interworking Failure due to
Improper Fiber Pigtail
System Overview
networking. The overall network consists of two ZXMP S385 NEs, at a
transmission rate of 2.5 Gbit/s. The point-to-point 1+1 protection
networking is adopted, with a network architecture shown in Figure 12.
The central office is located at NE B, and the EMS terminal is placed at the
central office.

A B
7# 7#
10# 10#
The connection configuration of optical fiber is as follows: The

7#OL16 of NE A connects with 7#OL16 of NE B, and the 10#OL16 of NE A
connects with 10#OL16 of NE B. The service between NE A and NE B is
configured to occupy eight active AUs. All the services processed on NE A
are 155 M optical interface services, and all the services processed by NE
B are 155 M electrical interface services. NE B is set to be the external
clock, and NE A extracts the line clock.
Fault Description
NE A has four 155 M optical interfaces, which connect to equipment from
another manufacturer. The services fail to interwork.
Fault Analysis
The problem of optical interface interworking can be solved by checking
the interface index, overhead byte, and clock for consistency, to find out
the cause of failure and then solve it.
Troubleshooting
Test the optical power of both the transmit & receive interfaces of the four
OL1 boards interconnected with the equipment from another manufacturer.
It is found that the optical launched power of -10 dBm becomes -40 dBm
when reaching the opposite end (connected via a fiber pigtail). This
indicates that optical interfaces are faulty. Check the optical interface
index of the interconnected equipment, and found it to be a multi-mode
optical interface which must be connected through a multi-mode optical
fiber. To troubleshoot, multi-mode optical fiber must be used for
connection, and in addition, replace the jumper inside the OL1 board with
a multi-mode optical fiber. Replace the original single-mode optical fiber
with multi-mode optical fiber, the fault is cleared.

155 M Electrical Interfaces

Interworking Failure due to
Improper Transmission Distance
System Overview
networking. The overall network consists of two ZXMP S385 NEs, with a
transmission rate of 2.5 Gbit/s. The point-to-point 1+1 protection
networking is adopted, with a network architecture shown in Figure 13.
The central office is located at NE B, and EMS terminal is placed at the
central office.
A B
7# 7#
10# 10#
The connection configuration of optical fiber is as follows: The

7#OL16 of NE A connects with the 7#OL16 of NE B, and the 10#OL16 of
NE A connects with the 10#OL16 of NE B. The service between NE A and
NE B is configured to occupy eight active AUs. All the services processed
on NE A are 155 M optical interface services, and all the services
processed by NE B are 155 M electrical interface services. NE B is set to be
the external clock, and NE A extracts the line clock.
Fault Description
All electrical interfaces of NE B connect to the equipment from different
manufacturers, and the services fail to interwork.
Fault Analysis
The interconnection fault can be eradicated by checking the interface index,
protection ground, clock, and environmental electromagnetic interference.
Troubleshooting
Find out and eliminate fault at NE B:
1. Check the EMS and found that signal degraded at the 155 M electrical
interface, and B1/B2/B3 BBE/ES performance events are reported.

2. The round trip distance from the equipment rack to DDF is 50 m, which
is a long transmission distance. To make it even worse, the SYV75-2-1
coaxial cable is used as the connection cable, resulting in large return
loss.
3. The ITU recommended the level index for 155 M electrical interface
should be in-between 0 to 12.7 dBm. However, a practical test shows
that the interface level of the above cable can not satisfy the standard
interface level index recommended by ITU.
4. Replace the SYV75-2-1 cable with the SYV75-2-2 coaxial cable which
has a less return loss, the interworking becomes normal and fault is
cleared.
Switching Failure/Service Block

due to CS Board Malfunction
System Overview
A local transmission network uses the ZXMP S385 equipment for
networking. The overall network consists of nine ZXMP S385 NEs, which
form a path protection ring with chain. The transmission rate around the
ring 1 is 622 M bit/s, and the transmission rate along the chain from A to
H is 155 Mbit/s. The network architecture is shown in Figure 14. The
central office is located at NE E, and the EMS terminal is placed at the
central office.
10#
6# C
D
11#
10#
7# B
E 7#
I
10# 10# 7#
622 Mbit/s 2-fiber
unidirectional path 10#
7# protection ring
A
F
10# 7#
10#
H
7#
10#
G
The formerly configured sites have service relation with NE E only, and all
the services are configured at 2#AU4 and 3#AU4.

Cutover plan: Re-allocate path resources to make the services of NEs F,

G, A, B, and E occupy 1#AU4; make the services of NE C, D, and E occupy
2#AU4; make the services of NEs H, I, and E occupy 3#AU4.
Fault Description
After cutover, all services of F, G, A, B and E NEs fail, and 2 M tributary of
NE E reports “Loss of TU-12 pointer” alarm. When the services of these
five NEs are re-configured to 4#AU4, all the services undergo intermittent
failure, with V5 performance over-threshold very soon.
Reconfigure all the above services back to the original 2#AU4 and test
them. The services become normal.
Fault Analysis
In this case, the F, G, A, B and E NEs share one AU4, and this
phenomenon might have occurred due to malfunction of CS board, which
passes through this AU4.
Troubleshooting
Configure part of 2 M services in NE E to 1#AU4 and 4#AU4.
Conduct AU terminal-side loopback site by site in the sequence of NE B,

NE A, NE G and NE F. The results show the loopback test of 1#AU4 at NE
B blocked, and large bit errors occur during loopback of 4#AU4 at NE A.
Resetting the CS boards of both sites does not work, so replace the CS
boards of NEs B and A. As a result, 1#AU4 and 4#AU4 get back to normal.
After the services of these three sites are re-configured to 1#AU4, the test
shows that they are normal.
Caution: Fault on a 2-fiber path protection ring normally derives from CS board
fault. Cross-connect failure of some services may cause the following problems:
the protection ring cannot perform protection, 2 M services are not functional, or
large bit errors occur.
Tips
This case shows that the loopback test can locate the fault accurately for
the CS problem. Then locate fault to the specific board by means of single-
point self-loop and slot & board interchange.
Once the faulty board is located, use hot plugging or resetting the
suspected board to confirm if the board is damaged. Before doing so, if
the CS configuration data has a backup, in order to avoid or decrease
service interruption, it is recommended to use EMS to switch between the
active CS and the standby CS.

LOF or LOS of Optical Board due

to Clock Fault
Fault Description
All the optical boards of a ZXMP S385 suddenly report “LOF" (loss of frame)
and “LOS” (loss of received signal) alarms.
Fault Analysis
It is suspected that the optical board fault causes the LOF and LOS alarms.
Conduct the self-loop of optical board to determine whether the fault lies
in the local end or in the remote end. However, since the SDH signal
modulation is based on synchronization, we should consider this case: the
alarm of optical board may derive from the optical board, or from the clock
board.
Troubleshooting
Locate the faulty NE using self-loop first. Then replace the optical board.
But the alarm still exists. Therefore, it is sure that the fault does not come
from the optical board of this NE. Replace the clock board and the fault is
cleared.
Conclusion
The true cause of this fault is: the clock board is damaged, resulting in no
available framing clock inside system. And signal sent by the optical board
cannot form frame.
If all the optical board report LOF and LOS, the clock problem should be
considered first. Therefore, the first thing to do should be switching
between the active/standby clock boards or replacing the clock board.
MS Switching Abnormality due to

Invalid MS Protection Relation
Fault Description
A local transmission network uses the ZTE ZXMP S385 system for
networking. The whole network forms a 2-fiber bidirectional multiplex
section shared protection ring.
The network operates normally before upgrade, but the multiplex section
switching becomes abnormal after network-wide upgrade (including

upgrade of EMS, NEs, and boards one by one). Query of the EMS shows
the APS identifier has been started, and the protection relation is
configured correctly.
Fault Analysis
The switching failure of multiplex section may result from incorrect MS
configuration, incorrect optical fiber connection, wrong APS identifier, APS
suspension, or incorrect configuration of MS protection relation.
First, check the MS configuration in the EMS; if it is correct, check the MS

data consistency via uploading comparison; if the MS data is consistent,
query the K1 and K2 bytes of the nodes in the MS ring, and check if these
two bytes are transferred normally.
Since the network was functioning normally before upgrade, we can

exclude two causes which are incorrect optical fiber connection and wrong
APS identifier. Probably the fault is resulted from invalidation of MS
switching data after the upgrade.
Troubleshooting
The fault may be caused by incorrect MS configuration, or inconsistency
between EMS database and NE database. Perform the following operations
to solve the fault:
1. In the EMS, re-configure the MS protection, reissue the MS data, and

perform the switching test.
2. In the EMS, set the NE to be offline. Clear the EMS database, re-
configure the data and issue it. Restart the APS protocol, and the
switching recovers.

Appendix A
NE Address Definition and

Route Configuration
This appendix describes how to set the NE IP address and EMS host IP
address. The content in this appendix applies to all SDH NEs.
Caution: While configuring initial information of NE, the IP addresses of this NE

and the EMS host should be determined and written to the NE NCP board, which
allows no random modification when the equipment operates normally.
Definition of NE IP Address
The definition of the NE IP address is the same as that of the common IP
address. However, the meaning of each byte in NE IP address is redefined.
The configuration principle and byte meanings vary with different mask
format.
FLSM Addressing
FLSM represent for the Full Length Subnet Mask.
1. Definitions of NE IP address and subnet mask

The NE IP address and subnet mask are defined in Table 123.

TABLE 123 DEFINITIONS OF NE IP ADDRESS AND SUBNET M ASK (FLSM)
Item Description Remarks

The NE IP address contains three parts: area code, NE
code, and NCP board number. Byte 1 serves as the
area code, some address bits of byte 2 and byte 3
serve as the NE code, and the remaining address bits
NE IP address byte 1.byte 2.byte 3.byte 4 and byte 4 forms the NCP board number.
The area ID combined with NE ID corresponds to the
network address. The NCP board number corresponds
to the host address.
The result got from the logic AND operation of NE IP
Subnet mask 255.byte 2.byte 3.0 address and subnet mask defines the specific meaning of
each byte in NE IP address.
2. Definitions of area ID, NE ID, and board ID

The area ID, NE ID, and board ID are defined in Table 124.
TABLE 124 DEFINITIONS OF AREA ID, NE ID, AND BOARD NUMBER (FLSM)

It ranges from 1 to 223
Area 192 is defined as the backbone area that connects
to other areas. Normally, it is recommended that the
Represents for the area that area IDs ranging from 193~201 are to be used for
the NE belongs to. non-backbone areas.
Area ID
It is byte 1 of the NE IP The Non-backbone areas use backbone network to
address. communicate among themselves, and any other form
of connection shall not exist among them.
It is recommended no more than 64 NEs in one area.
The maximum number of NEs in single area is 128.
The result got from the logic AND
operation of bytes 2, 3 of the NE
NE ID In the same area, each NE must have a unique NE ID.
IP; and the corresponding bytes of
subnet mask.
The NCP board number
The NCP board number needs manual definition. The
stands for the host ID of NE,
numbers of other boards in an NE are automatically
and needs manual definition.
allocated according to the NCP board number. In
Board The NCP board number is the addition, numbers of various boards in the same NE
number result got from the logic AND must be unique, while those in different NEs can be the
operation of bytes 2, 3, 4 of same.
the NE IP; and the reverse
The NCP board number should range from 9 to 100,
code of corresponding bytes
and 18 is recommended.
in the subnet mask.

Appendix A - NE Address Definition and Route Configuration
3. Example of NE IP address allocation

The meanings of each byte in the NE IP address are listed in Table 125.
TABLE 125 MEANINGS OF BYTES IN THE NE IP ADDRESS
NE IP Address Subnet Mask Description

Byte 1 is the area ID; byte 2 and byte 3 form the NE ID; byte 4
255.255.255.0
byte 1. byte 2. byte 3. is the NCP board number.
byte 4 Byte 1 is the area ID; byte 2 is the NE ID; byte 3 and byte 4
255.255.0.0
form the NCP board number.
Taking three NEs as example, when different subnet masks are adopted,
the NE IP addresses are allocated as listed in Table 126.
T AB L E 1 2 6 N E I P AD D R E S S AL L O C AT I O N ( F L S M )
NE IP Address Allocation
Subnet Mask
NE 1 NE 2 NE 3
255.255.255.0 193.1.1.18 193.1.2.18 193.1.3.18

255.255.0.0 193.1.1.18 193.2.1.18 193.3.1.18
VLSM Addressing
At present, ZTE can employ the techniques of VLSM (Variable Length
Subnet Mask) addressing and CIDR (Classless Inter-Domain Routing) to
define NE IP address, which can greatly save the IP address space.
Note: VLSM addressing and CIDR techniques need support from the equipment
version. Consult ZTE maintenance personnel for detailed version information.
1. Definitions of NE IP address and subnet mask

The NE IP address and subnet mask are defined in Table 127.
TABLE 127 DEFINITIONS OF NE IP ADDRESS AND SUBNET M ASK (VLSM)

It consists of three parts: area ID, ECC subnet ID, NE ID.
NE IP address byte 1.byte 2.byte 3.byte 4 Each NE needs to be allocated with an IP address. In the
same ECC subnet (an interconnected ECC network), the
NE IP address must be unique.
The result got from the logic AND operation of subnet
mask and NE IP address defines the specific meaning of
Subnet mask byte 1.byte 2.byte 3.byte 4 each byte in the NE IP address.
Byte 1 is generally 255, and byte 4 can be set randomly.

2. Definitions of area ID, ECC subnet ID, and NE ID

The area ID, ECC subnet ID, and NE ID are defined in Table 128.
TABLE 128 DEFINITIONS OF AREA ID, ECC SUBNET ID, AND NE ID (VLSM)

For a complicated ECC subnet, the multi-
area configuration must be adopted due to
the limitation of NE processing capability
Represents for the area that the NE
and the requirement of dynamic route
Area ID belongs to
protocol.
It is byte 1 of NE IP address
Refer to the description of area ID in Table
124 for division principle and requirement
of the area ID.
Represents for the ECC subnet ID that
ECC subnet the NE belongs to A complicated ECC subnet can contain multiple
ID areas.
It is byte 2 of NE IP address
It is the result got from the logic AND
operation of byte 3, 4 of the NE IP
NE ID -
address; and corresponding bytes of
the subnet mask.
3. Example of NE IP address allocation

Suppose that for an address space of 193.193.193.*, the subnet mask
is 255.255.255.252, and the NE addresses are allocated as follows (63
NE addresses in total):
193.193.193.5
193.193.193.9
193.193.193.13
193.193.193.17
193.193.193.21
193.193.193.25
......
193.193.193.249
193.193.193.253
Where, byte 1 is the area ID; byte 2 represent for the ECC subnet ID; the
result got from the logic AND operation of byte 3, 4 of the NE IP address,
and corresponding bytes of the subnet mask represents for the NE ID.
4. Definition of board IP address

Suppose the number of available DCC overhead channels (count the
channels of the installed board in the NE, including optical interfaces
and electrical interfaces) in the NE is PortNum. It is necessary to define
one IP address for each optical/electrical interface.
If byte 4 of the subnet mask is zero, the board IP address is
allocated at byte 4.

Suppose the NE IP address, i.e. the NCP board IP address is “byte

1.byte 2.byte 3.byte 4”, then the IP addresses of other boards are
allocated to numbers ranging from “byte 1.byte 2.byte 3.(byte
4+1)” to “byte 1.byte 2.byte 3.(byte 4+PortNum)”.
If byte 4 of the subnet mask is not zero, the board IP address is
allocated at byte 2.
Suppose the NE IP address is “byte 1.byte 2.byte 3.byte 4”, then
the IP addresses of other boards are allocated to numbers ranging
from “byte 1.(byte 2+1).byte 3.byte 4” to “byte 1.(byte
2+PortNum).byte 3.byte 4”.
Note: Since the NCP board IP address is invisible to EMS, it will not affect the
outside network, which means it will not conflict with the outside network address.
Therefore, it is only necessary to ensure that the addresses inside the SDH internal
communication network are unique. In the same ECC network, the fourth bytes of
subnet masks being zero and being non-zero should not coexist.
Example of Network Address

Coding of NEs
This section uses the network topology shown in Figure 15 as an example
to describe the network address allocation using the FLSM technique.
FIGURE 15 NETWORK TOPOLOGY
EMS
2
Area 193
3 4 5
6 8
Area 192 7 10
9 11
Area 194
12

[Scheme 1]
Dividing areas according to Figure 15 can simplify connections between

areas, and the NEs belonging to the backbone area are relatively few.
NEs 1, 2, 3, 4, 5, 6, and 8: they are relatively centralized, among

which there are many connections, and they form a mesh topology.
Therefore, they are allocated into area 193.
NEs 9, 11, and 12: they are relatively centralized and form a ring
topology. Therefore, they are allocated into area 194.
NEs 7 and 10: there is only one single connection between areas 193
and 194 via NEs 7 and 10. Therefore, NEs 7 and 10 are taken out as
the backbone area (area 192) for connecting other areas.
Area definitions and NE IP address configurations are listed in Table 129.
TABLE 129 AREA DEFINITIONS AND NE IP ADDRESS CONFIGURATIONS
NEs in the Area

Area Number
NE NE IP Address
Access NE 1 193.1.1.18
NE 2 193.1.2.18
NE 3 193.1.3.18
Area 193 NE 4 193.1.4.18
NE 5 193.1.5.18
NE 6 193.1.6.18
NE 8 193.1.8.18
NE 9 194.1.9.18
Area 194 NE 11 194.1.11.18
NE 12 194.1.12.18
NE 7 192.1.7.18
Area 192 (backbone area)
NE 10 192.1.10.18
Note: The network mask is 255.255.255.0 and the EMS host address is 193.1.1.1.
[Scheme 2]
Since the NEs in Figure 15 are relatively few, all the NEs can be simply
allocated into one area, in which the backbone area is not needed. For
example, they may all be allocated into area 193, and their NE addresses
are listed in Table 130.

TABLE 130 NE IP ADDRESS CONFIGURATIONS OF THE NES ALLOC ATED INTO AREA 193
NE NE IP Address NE NE IP Address
Access NE 1 193.1.1.18 NE 2 193.1.2.18
NE 3 193.1.3.18 NE 4 193.1.4.18
NE 5 193.1.5.18 NE 6 193.1.6.18
NE 7 193.1.7.18 NE 8 193.1.8.18
NE 9 193.1.9.18 NE 10 193.1.10.18
NE 11 193.1.11.18 NE 12 193.1.12.18
Note: The network mask is 255.255.255.0 and the EMS host address is 193.1.1.1.
Although allocating all NEs into the same area is simple, the efficiency of
ECC route algorithm will be affected if the number of NEs is large.
Therefore, this method only applies to applications with a small number of
NEs. Normally, the maximum number of NEs in one area should not
exceed 120.
Address/Route Configuration of
the EMS Host
In order to enable EMS to manage all the NEs properly, it is necessary to
set on the EMS host the IP routes that can reach the whole network.
EMS Host Address

The EMS host address include the EMS host IP address, subnet mask, and
gateway address, as listed in Table 131.
TABLE 131 DEFINITION OF EMS HOST ADDRESS
Item Description Configuration Principle

The result got from the logic AND operation of the
EMS host IP address and the subnet mask must be
Defines the EMS host network within the same network section as the access NE, i.e.
IP address. the EMS host and the gateway NE should have the
address Employs the IP address format: same network ID.
byte 1.byte 2.byte 3.byte 4. The EMS host ID should be less than the gateway NE
host ID (i.e. the NCP board number). The EMS host ID
is suggested to range from 1 to 9, starting from 1.
Defines the subnet mask of the
EMS host.
Subnet Used to divide network section The subnet mask is suggested to be the same as the
mask by performing logic AND subnet mask of access NE.
operation with the EMS host IP
address.
Gateway Defines the gateway address of the
Set the access NE as the gateway NE.
address EMS host.

Consider the networking shown in Figure 15, for example, bind an IP

address 193.1.1.1 which is within the same network section as gateway
NE 1, with the network adapter of EMS host; thus ensuring that EMS host
can reach the access NE. Define the gateway NE address as 193.1.1.18,
thus ensuring that EMS host can reach the area 193.
Set the routes on the EMS host to reach NEs in area 192 and area 194.
Route Configuration
There are two methods to set the routes on EMS:
1. Run the OSPF dynamic routing protocol at the EMS host side.
This method requires no route setting. However, be cautious when
using dynamic route and do not advertise those invalid or possibly
repeated routes to the network, to avoid some unreachable NEs or too
large routing table. In addition, the application of dynamic route
increases the operating load of EMS host.
Therefore, it is recommended to set static route or default route for the
EMS host, so as to filter out IP packets that are irrelevant to the
network, thus increases the operating efficiency of EMS.
2. Set default route or static route directing to the NE that directly
connects with the EMS host. Delete other routes that are repeatedly
configured. As an example, consider the network shown in Figure 15,
the method of setting default route or static route for EMS host is as
follows:
Set the default route
route add default 193.1.1.18
This default route means that all IP packets, without showing route
locally, have to pass NE 1.
Set static routes
route add 193.1.0.0 mask 255.255.0.0 193.1.1.18
route add 194.1.0.0 mask 255.255.0.0 193.1.1.18
route add 192.1.0.0 mask 255.255.0.0 193.1.1.18
The three static routes mean that all IP packets accessing the networks
193.1, 194.1, and 192.1 shall pass NE 1.

Route Configuration Command

Windows operating system has different route configuration commands
from the Unix operating system.
Window Operating System

The commonly used commands in Windows 2000 to set routes are listed in
Table 132.
TABLE 132 ROUTE CONFIGURATION COMM ANDS IN WINDOWS2000
Operation Purpose Command Line

route add 0.0.0.0 mask 0.0.0.0
Add default route 193.1.1.18
route add 193.1.0.0 mask 255.255.0.0
Add route 193.1.1.18
route add –p 193.1.0.0 mask
Add permanent route 255.255.0.0 193.1.1.18
route delete 193.1.0.0 mask
Delete route 255.255.0.0 193.1.1.18
View route route print
Check if the destination NE ping 192.1.7.18

is reachable
View all the NEs along the tracert 192.1.7.18
route
Caution: Once the computer is restarted, all the routes added by the command of
r o u t e a d d will be lost. Use the command of r o u t e a d d – p to permanently
add one route to the computer.
Unix Operating System

In Unix operating system, route configuration can be completed using
command line and file.
Command line
The commonly used command lines to set route are listed in Table 133.
TABLE 133 ROUTE CONFIGURATION COMM ANDS LINES IN UNIX

Add default route route add default 193.1.1.18 1
route add 193.1.0.0 2 5 5 . 2 5 5 . 0 .0
193.1.1.18 1 (HP-UX)
Add route
route add net 193.1.0.0 193.1.1.18 1
(Solaris)


Add permanent route route delete 193.1.0.0
Delete route netstat
View route ping 192.1.7.18
Check if the destination NE tracertroute 192.1.7.18

is reachable
Caution: Once the computer is restarted, all the routes added by the command
lines will be lost. Modify the configuration file and save the changes to permanently
add one route to the computer.
Modifying the Configuration File

In different Unix systems, the configuration file location and the
modification operation are different.
HP-UX platform
Modify the /etc/rc.config.d/netconf file in the document editor. The
configuration commands in the file will automatically take effect
and be saved permanently after the system is restarted.
The route configuration commands in configuration file are listed in
Table 134.
TABLE 134 ROUTE CONFIGURATION COMM ANDS IN CONFIGURATION FILE (HP-UX)
Operation Corresponding
File Modifications
Purpose Command Line
ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]="" route add
Add default ROUTE_GATEWAY[0]= 193.1.1.18 default
route 193.1.1.18 1
ROUTE_COUNT[0]=1
ROUTE_ARGS[0]= ""
ROUTE_DESTINATION[1]=" 193.1.0.0 "
ROUTE_MASK[1]=" 255.255.0.0 " route add
193.1.0.0
Add route ROUTE_GATEWAY[1]= 193.1.1.18
255.255.0.0
ROUTE_COUNT[1]=1 193.1.1.18 1
ROUTE_ARGS[1]=""
Solaris platform
Modify the configuration files listed in Table 135 in the document
editor. The configuration commands in the files will automatically
take effect and be saved permanently after the system is restarted.

TABLE 135 ROUTE CONFIGURATION COMM ANDS IN CONFIGURATION FILES (SOLARIS)
File Location Function/Format Example

127.0.0.1 localhost
loghost
Set added IP address
192.192.1.1
/etc/hosts Format: IP_address Host_name hknttserver
Alias 192.192.66.1 hknttsdh
168.69.74.35 almftp
192.192.1.0
Set the subnet mask for the added IP 255.255.255.0
address 192.192.66.0
/etc/netmasks
Format: N e t w o r k _ I D 255.255.255.0
Subnet_mask 168.69.74.0
255.255.255.0
Set the active IP address

/etc/hostname.eri0 hknttserver
Format: H o s t _ n a m e
Set the logic IP address. One hostname.eri0:x Define the file of

file needs to be added for each added IP /etc/hostname.eri0:1 as hknttsdh
/etc/hostname.eri0:x address (x starts from one) Define the file of
Format: H o s t _ n a m e /etc/hostname.eri0:2 as almftp
route add net
Add static route. This file will be 192.192.0.0 –netmask
automatically loaded when the system 255.255.192.0
starts. The file name is S96zteRouter. The 192.192.1.6 1
name zteRouter can be defined at your will route add net
/etc/rc2.d/zteRouter except existed file name in the /etc/rc2.d 192.192.64.0 –netmask
directory 255.255.192.0
Format to add one route: r o u t e a d d 192.192.66.18 1
[ host | net ] destination route add net
gateway 168.65.0.0
168.69.74.1 5
/etc/defaultrouter Input the IP address to set the default gateway -


Appendix B
NCP Application/Logic
Upgrade
This appendix describes the operational procedures of NCP

application/logic download.
Note: The initial ZXMP S385 equipment cannot connect to the EMS terminal
computer for network data configuration or network management until the
application has been downloaded to the NCP board and the initial parameters have
been configured.
Description of NCP Board

1. ZXMP S385 equipment reserves two slots for NCP board (No. 18 and
No. 19 slots. Generally, No. 18 slot is called the master slot, and No.
19 slot is called the standby slot). Therefore two NCP boards can be
installed simultaneously to implement the 1+1 protection for NCP
boards.
Note: The EMS of ZXONM E300 3.16R2 version or later support the 1+1 protection
for NCP boards.
2. NCP board has an Ethernet interface (debugging interface) as shown in

Figure 16. The Ethernet interface is used to connect the NCP board
working in the Download status. QxI board also has an Ethernet
interface (EMS Qx interface) which is used to connect the NCP board
working in the master status. Refer to the section of BOOTROM State
Switching for the work states of NCP board.

FIGURE 16 NCP PCB BOARD
7 6 5 4 3 2 1
S1
Motherboard side
1. Board running indicator NOM 2. Major/minor alarm indicator ALM1

3. Critical alarm indicator ALM2 4. Dip switch S1
5. Ethernet interface (debugging interface) 6. Master status indicator MS
7. Reset button RST
3. If two NCP boards are installed simultaneously, only one NCP board is
the master board and the other is the standby board at any moment
during normal running. Only the Qx, S, and ECC interfaces of the
master NCP board can communicate normally; while those interfaces of
the standby NCP board are closed. The Ethernet port of QxI board only
communicates with the master board, i.e. it can only connect one NCP
board (the master NCP board) at any moment.
Description of BOOTROM
Module on NCP Board
This section describes the functions and state switching of BOOTROM
module on NCP board.
Functions of BOOTROM Module on NCP

1. Prepare for running the board application.
Download (burn) the NCP application program to the CF card on
NCP.
Download the configuration files to the CF card on NCP.
2. Start the Agent program on NCP board.
3. Other functions
Format the CF card.
Delete the database and application program of NCP board.
Read and set the system parameters (mainly the MAC address).

Appendix B - NCP Application/Logic Upgrade
NCP Board State Switching

The functional states of NCP board include Download state and Running
state which are determined by the DIP switch on NCP board. The
Download state is used to download the NCP application and configuration
parameters, while the Running state is used to start the NCP application
program. The settings of the DIP-switch digits are described as follows:
1. Set the DIP switch to full ON state, start or reset the NCP board, it will
enter the Download state. In this state, the default value of NCP board
IP address is 192.192.192.11. Communication between the EMS and
the NCP board can only be established by connecting the EMS with the
Ethernet interface of this NCP board.
2. Set the DIP switch is set to non-full ON and non-full OFF state, start or
reset the NCP board, it will enter the Running state. In this state,
connect the EMS with the Qx interface of QxI board to establish
communication between the EMS and the master NCP board.

Local Upgrade Instructions

Local upgrade refers to the procedure of upgrading application/logic in the
Download state. The local upgrade flowchart is shown in Figure 17.
FIGURE 17 LOCAL UPGRADE FLOWCHART
Begin
Prepare for upgrade
Use telnet Clear the database

method
Use ftp Download the

method application/logic
Upgrade the
application/logic
Use telnet
method
Verify the
application/logic
Upgrade the
application/logic of the
standby NCP board
Download the database
Performed in
the EMS
Verify the
application/logic version
in the EMS
End

Upgrade Preparations
The flowchart of local upgrade preparations is shown in Figure 18.
FIGURE 18 FLOWCHART OF LOCAL UPGRADE PREPAR ATIONS
Begin
Confirm the BOOTROM

chip is correct and the CF
card is ready
Set the DIP switch of NCP

board to all ON (Download
state)
Confirm the network cable

between EMS and NE NCP
board is correctly connected
Set the EMS IP address
Disconnected Check the equipment

ping 192.192.192.11 status and the network
connection status
Connected
No
Is it the first time to use the CF
card?
Yes
No
Is it necessary to reconfigure the
Format the CF card NE information?
Yes
Clear the NCP database
Configure the NE
information
Reset the NCP board
End

1. Make sure the correct BOOTROM chip is plugged on NCP board, as

each type of NCP board can only use its own BOOTROM chip.
2. Make sure the CF card is correctly plugged on NCP.
3. Set the DIP switch on NCP board to all ON state (Download state). And
the NE IP address is 192.192.192.11 with the subnet mask of
255.255.255.0
4. Connect the EMS with the Ethernet interface of the NCP board, and
confirm the Ethernet cable connection between the EMS computer and
NCP board is correct.
5. Set the IP address and subnet mask of the EMS computer according to
the following rules:
IP address: 192.192.192.X (0 < X < 255 and X ≠ 11)
Subnet mask: 255.255.255.0
6. Execute the p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command on the EMS computer
to confirm that the EMS computer can connect to NCP.
7. If the CF card is not used for the first time, and it is unnecessary to
completely clear the NE data or reconfigure the NE, the upgrade
preparations are completed.
8. If the CF card is not used for the first time, and it is necessary to
completely clear the NE data and reconfigure the NE, follow the steps
below:
Execute the command t e l n e t 192.192.192.11 on the EMS
computer.
The system prompts to enter user name and password which are
both empty, press ENTER directly.
Input the command d - e r a s e – d 1 under the prompt Z T E + > to
erase the database, as shown in Figure 19.
FIGURE 19 ERASE THE DATABASE
Input the commands d - e r a s e – p 1 and d - e r a s e – p 2 under the

prompt Z T E + > to erase the chip area which saves the application
program, as shown in Figure 20.

FIGURE 20 ERASE THE CHIP ARE A WHICH S AVES THE APPLICATION PROGRAM
Input the commands d - e r a s e – f 1 and d - e r a s e – f 2 under the

prompt Z T E + > to erase the chip area which saves the logic
FIGURE 21 ERASE THE CHIP ARE A WHICH S AVES THE LOGIC PROGRAM
Input the command d - c f g n e t under the prompt Z T E + > to

configure the NE related information, as shown in Figure 22. The
input principles of each item are listed in Table 136.
FIGURE 22 CONFIGURE THE NE RELATED INFORM ATION

TABLE 136 INPUT PRINCIPLES OF NE RELATED P AR AMETERS
Parameter Name Input Principle

IP Address Input the IP address of the NE.
Subnet Mask Input the subnet mask of the NE.
MAC Address Input the physical address of the NE. It is mandatory

and should be unique for each NE.
Warning: Must input each parameter. Press ENTER directly if there is no

modification. Cannot quit in the middle of the procedure, otherwise the NCP board
will stay in the infinite waiting state.
Input the command d - r e b o o t to reboot the NCP board, and the

NE information configuration will take effect. Upgrade preparations
are completed.
9. If the CF card is used for the first time, perform the following
operations to format the CF card, clear the NCP database, and
reconfigure the NE information:
Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS
computer.
The system prompts to enter the user name and password which
are both empty. Press ENTER directly.
Input the command f o r m a t under the prompt z t e + > to format the
CF card, as shown in Figure 23.
FIGURE 23 FORM AT THE CF CARD
Input the command d - e r a s e – d 1 under the prompt Z T E + > to

erase the database, as shown in Figure 19.
Input the commands d - e r a s e – p 1 and d - e r a s e – p 2 under the
prompt Z T E + > to erase the chip area which saves the application
Input the commands d - e r a s e – f 1 and d - e r a s e – f 2 under the
prompt Z T E + > to erase the chip area which saves the logic
Input the command d - c f g n e t under the prompt Z T E + > to
configure the NE related information, as shown in Figure 22. The
input principles of each item are listed in Table 136.

Reset the NCP board to make the NE configuration take effect.

Input the command d - c f g n e t – s to query the NE related
information.
Clearing the Database

Tip: If the NE data has been cleared during the upgrade preparation, this step can
be skipped.
Perform the following operations to clear the NCP database:
1. Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS computer.

2. The system prompts to enter the user name and password which are
both empty. Press ENTER directly until the prompt Z T E + > appears.
3. Input the command d - e r a s e – d 1 to erase the database.
Downloading the Application/Logic

1. Execute the command f t p 1 9 2 . 1 9 2 . 1 9 2 . 1 1 under the directory
containing the Agent program or logic on the computer. When the
system prompts to input the username and password, press ENTER
until the prompt f t p > appears.
2. Execute the following commands under the f t p > prompt, to download
board application/logic and check if the downloaded file is correct.
ftp> bin
//Set the file transfer mode to binary mode.
ftp> put file_name_of_the_application/logic
//Download the board application/logic. When the f t p > prompt appears
again, it indicates that the file transfer has completed.
ftp> ls –l
//Check if the downloaded file size is consistent with the local file. If not
consistent, re-download the file.
ftp> bye
//Exit ftp connection.
Caution: The application/logic of NCP board must be transferred to the NCP board
in the binary mode
Suppose the Agent program N C P - Z X M P S 3 8 5 - P R G - V 1 . 0 1 R 1 P 0 5 . B I N is

downloaded from the computer to the NE, the operations are shown in Figure
24.

FIGURE 24 LOCAL DOWNLOAD OF NCP APPLICATION TO NE
Upgrading Application/Logic
It is to upgrade the application/logic on CF card into the application/logic
area.
1. Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 . When the system

prompts to input the username and password, press ENTER directly
until the prompt Z T E + > appears.
2. Execute the command d - u p g r a d e under the Z T E + > prompt, to

upgrade the board application/logic into the application/logic area
respectively.
<Command Format>
d-upgrade Subrack-NO. Slot-NO. Board-CPU-NO. {-p

Application-file-name\-f Logic-file-name}
<Parameter Description>
The parameters of the command are described in Table 137.
TABLE 137 PAR AMETERS OF THE COMM AND D-UPRADE
Parameter Name Parameter Value
Subrack-NO. 1 or 2, generally 1.
The slot number of the board. It is an integer ranging from 1 to
Slot-NO. 19. It is 18 or 19 for the NCP board.
Board-CPU-NO. Integer ranging from 1 to 3, generally 1.

The parameter for NCP application delivery, followed by the
-p board application file name.
The parameter for NCP logic delivery, followed by the board logic
-f file name.

For example, to upgrade the program in Figure 24 of section Downloading

the Application/Logic into the application/logic area, perform the operation
shown in Figure 25.
FIGURE 25 LOCAL UPGRADE OF NCP APPLICATION TO NE
Verifying the Application/Logic

1. Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 . When the system
prompts to enter the username and password, press ENTER directly
until the prompt Z T E + > appears.
2. Execute the command d - g e t - s t a t u s under the Z T E + > prompt, to

verify if the application/logic version is normal.
If the version is abnormal, it is necessary to re-perform the operations

described in the section Downloading the Application/Logic and in the
section Upgrading the Application/Logic until the version queried is
normal.
<Command Format>
d-get-status Subrack-NO. Slot-NO. Board-CPU-NO.
TABLE 138 PARAMETERS OF THE COMMAND D-GET-STATUS
Slot-NO. 19. It is 18 or 19 for the NCP board.

For example, to verify the version of the application in Figure 24 of the

section Downloading the Application/Logic, the results are shown in Figure
26. The parameters need to be verified are described in Table 139.
FIGURE 26 VERSION INFORMATION FOR LOCAL UPGRADE OF BOARD APPLICATION
TABLE 139 DESCRIPTIONS OF P AR AMETERS THAT NEED TO BE VERIFIED FOR LOCAL

UPGRADED BOARD PROGRAM VERSION
Parameter Name Parameter Description Remarks

p r o g r a m indicates the application
file type -
area
Should be consistent with
download date File downloaded time the actual time when the
file is downloaded
download
version File version downloaded the actual downloaded file
version
reserved indicates that this
try-run type -
parameter is reserved
master indicates the master
status -
status
upgrade N O indicates the database is not
-
database upgraded
0 x 0 A 0 0 0 0 0 0 indicates the initial
start address -
address of the program
file length The size of the downloaded file the actual downloaded file
size
try-run r e s e r v e d indicates that this
-
elapsed time parameter is reserved
-
remained time parameter is reserved

Upgrading Application/Logic for Standby

NCP
Note: If only one NCP board is configured, skip this step.
1. Re-perform the steps described in section Upgrade Preparations and in

the section Verifying the Application/Logic, to upgrade the standby NCP
board.
2. The IP address, subnet mask, and MAC address of the standby NCP
board must be the same as those of the master NCP board.
Downloading the Database

1. Set the DIP switches of both NCP boards to non-all ON and also non-all
OFF state (Running state).
2. Reset the NCP board and it enters the Running state.
3. Set the IP address of EMS computer to be within the same network
section as the NE IP address.
4. Execute the command p i n g N E - I P to confirm if the NE can be pinged
through.
5. In the EMS client operation window, select the NE to be upgraded, and
click System →NCP data Management →DB Download to download
all the databases via the EMS software, as shown in Figure 27.
FIGURE 27 DOWNLOAD DB DIALOG BOX OF THE EMS

Note:
It is unnecessary to download the database when upgrading the logic.
It is unnecessary to download the database for the standby NCP board. The
data will be automatically synchronized to the standby NCP board.
Verifying the Application/Logic Version in

the EMS
1. Double-click the NE that has been upgraded in the ZXONM E300 EMS,
to open the Card Management dialog box.
2. Right-click the NCP board to be queried with the version, and the
shortcut menu pops up. Select the Card Special Version menu, as
shown in Figure 28.
FIGURE 28 CARD M AN AGEMENT DIALOG BOX
3. The Card Special Version dialog box pops up and displays the
application/logic version of the queried NCP board, as shown in Figure
29. If the information displayed is consistent with the downloaded
application/logic version, it indicates that the newly downloaded
application/logic is running normally.

FIGURE 29 CARD SPECIAL VERSION DIALOG BOX
Remote Upgrade Instructions

The remote upgrade is the procedure that upgrades the application/logic
of NCP board in its Running state. The flowchart is shown in Figure 30.

FIGURE 30 REMOTE UPGRADE FLOWCHART
Begin
Prepare for upgrade
Confirm the address of

the active NCP board
Use ftp method Download the

application/logic
Upgrade the
application/logic
Verify the upgraded

application/logic
Try run of the

Use telnet method application/logic
Verify the application/logic

that has passed the try run
Activate the
application/logic

that has been activated
Upgrade the application/logic

of the standby NCP board
Download the
database
Performed in the
EMS

version in the EMS
End

Upgrade Preparations
Use network cable to connect the Ethernet interface of EMS computer
with the Ethernet interface of QxI board. Confirm that the network
cable is connected correctly.
Execute the p i n g N E - I P command at the EMS terminal. Confirm that
the EMS terminal communicates normally with the NE, and that the
ECC of the NE to be upgraded is smooth.
Confirm that the Agent program version to be downloaded comply with
the current EMS version. Ensure the validity and consistency of the
versions.
Confirming the Address of the Master NCP

Board
There are to methods to confirm the NCP board address: via EMS software
and via command lines.
Query via EMS software

1. In the ZXONM E300 EMS client operation window, select the ZXMP
S385 NE to be upgraded, and click Maintenance →Diagnosis
→MasterSlaveBrd Switch menu.
2. The MasterSlaveBrd Switch dialog box pops up, as shown in Figure

31.
FIGURE 31 M ASTERSLAVEBRD SWITCH DIALOG BOX
3. Click the Update button, the text box of Current Working Card will
display the address information of the master NCP board (1 1 8 1 or 1
1 9 1 ).

Query via command lines

1. Execute the command t e l n e t N E - I P , input the user name of z t e
and password of e c c according to the system prompt, and press
ENTER, until the prompt Z T E + > appears.
Note: The user name and password must be lowercase.
2. Under the prompt Z T E + > , input the command n c p s p i n g , to check if

the communication state of the standby NCP board is normal; and
then confirm the address of the master NCP board according to the
result of this command.
For example, to check the communication state of the standby NCP

board, and confirm the address of the master NCP board, the
operations are shown in Figure 32.
FIGURE 32 CONFIRMING THE ADDRESS OF THE M ASTER NCP BOARD
The result shown in the figure is N C P S p i n g i n g 1 . 1 9 . 1 w i t h 3 2

b y t e s o f d a t a , which indicates that the address of the standby NCP
board is 1 19 1. Thus it can be concluded that the address of the
master NCP board is 1 18 1, with the Slot No. of 18.
Downloading the Application/Logic

1. Execute the command f t p N E - I P under the directory containing the
Agent program or logic on the computer. Input z t e for username and
e c c for password according to the system prompts, press ENTER until
the prompt f t p > appears.
2. Execute the following commands under the f t p > prompt, to download
board application/logic and check if the downloaded file is correct.
ftp> bin
//Set the file transfer mode to binary mode.
ftp> put file_name_of_the_application/logic
//Download the board application/logic. When the f t p > prompt appears
again, it indicates that the file transfer has completed.

ftp> ls –l
//Check if the downloaded file size is consistent with the local file. If not
consistent, re-download the file.
ftp> bye
//Exit ftp connection.
Caution: The application/logic of NCP board must be transferred to the NCP board
in the binary mode
Upgrading the Application/Logic

1. Execute the command t e l n e t N E - I P . Input z t e for username and
e c c for password according to the system prompts, press ENTER until
the prompt f t p > appears.
2. Execute the command d - u p g r a d e under the Z T E + > prompt, to

upgrade the board application/logic. Refer to the section Upgrading
the Application/Logic in Local Upgrade part for detailed procedures of
upgrading the application/logic.
Caution: When executing the d - u p g r a d e command, the S l o t - N o . parameter

should be the slot number of the master NCP board queried in the section
Confirming the Address of the Master NCP Board.
For example, to upgrade the program file N C P - Z X M P S 3 8 5 - P R G -

V 1 . 0 1 R 1 P 0 5 . B I N that has been downloaded to the NE (with IP address of
213.17.1.166) into the application area, the operations are shown in Figure 33.
FIGURE 33 REMOTE UPGRADE OF APPLICATION

Verifying the Upgraded Application/Logic

Execute the command d - g e t - s t a t u s under the prompt of Z T E + > to verify
if the version of the upgraded application/logic in the standby area is
normal.
If the version is abnormal, it is necessary to perform the operations in the

section Downloading the Application/logic and the section Upgrading the
Application/Logic again, until the version queried is normal.
<Command Format>
<Parameter Description> is listed in Table 138.
For example, to verify the program file in the section Upgrading the
Application/Logic, the result is shown in Figure 34.
FIGURE 34 VERIFYING THE UPGRADED PROGRAM
The parameters in the standby area (labeled as p r o g r a m n u m b e r : 0 x 0 2 )

that need to be verified are described in Table 140.

TABLE 140 PAR AMETERS IN THE STANDBY AREA TH AT NEED TO BE VERIFIED

file type -
area
download date File downloaded time the actual time when the
file is downloaded
download
version File version downloaded the actual downloaded file
version
reserved indicates that this
try-run type -
parameter is reserved
status m a s t e r indicates the master state -
upgrade N O indicates that the database is
-
database not upgraded
0 x 0 A 4 0 0 0 0 0 0 is the initial
start address -
file length The size of the downloaded file the actual downloaded file
size
-
elapsed time parameter is reserved
-
remained time parameter is reserved
Try Run of the Application/Logic

1. Execute the d - t r y command under the prompt Z T E + > to perform the
try run of the application/logic in the standby area.
<Command Format>
d-try Subrack-NO. Slot-NO. Board-CPU-NO. {-p\-f}
TABLE 141 PARAMETERS OF THE COMMAND D-TRY
Slot-NO. 19; It is 18 or 19 for the NCP board.
-p Try running the board application.
-f Try running the board logic.

2. During the process of executing the command d - t r y , the system will

prompt: D o y o u w a n t t o u p g r a d e t h e D B a r e a ? Y e s [ y ] / N o [ n ] .
Select y to clear the NCP database; while select n to not to clear the
NCP database.
For example, to try running the program file in the section Upgrading
the Application/Logic, the result is shown in Figure 35.
FIGURE 35 TRY RUN OF THE PROGRAM
3. When the d - t r y command completes, the NCP board is reset, and

the communication with the computer is interrupted. The ECC will be
interrupted for about one to two minutes, and during this time the
EMS cannot manage this NE. If there are two NCP boards, after the
reset, the system will switch to another NCP board first. And after the
NCP board to be upgraded starts running again, it will automatically
switch back to the upgraded NCP board, and continue the upgrade
process.
Verifying the Application/Logic that Passed

the Try Run
1. Execute the t e l n e t N E - I P command on the EMS computer, and input
the user name of z t e and password of e c c according to the system
prompts. Press ENTER until the prompt Z T E + > appears.
2. Under the prompt Z T E + > , execute the n c p s p i n g command, to test if

the communication state of the standby NCP board is normal, and
confirm the master NCP address according to the command result. The
operation example is shown in Figure 32.
3. Execute the command d - g e t - s t a t u s under the prompt of Z T E + > to

verify if the version of the upgraded application/logic in the original
standby area is normal. If the version is abnormal, it is necessary to
re-perform all the operations from the section Downloading the
Application/logic to the section Try Run of the Application/Logic again,
until the version queried is normal.
<Command Format>

For example, to verify the program file in section Try Run of the
Application/Logic, the result is shown in Figure 36.
FIGURE 36 VERIFYING THE PROGRAM THAT P ASSED THE TRY RUN
The parameters in the original standby area (labeled as p r o g r a m n u m b e r :

0 x 0 2 ) that need to be verified are described in Table 142.
TABLE 142 PARAMETERS IN THE ORIGINAL STANDBY AREA THAT NEED TO BE VERIFIED
AFTER THE TRY RUN

file type -
area
download date File downloaded time
the result in Figure 34
download Should be consistent with
File version downloaded
version the result in Figure 34
try-run indicates that it is
try-run type performing the try-run of the -
program
try-run indicates the try-run
status -
status
upgrade Y E S ! indicates that the database
-
database is upgraded


0 x 0 A 4 0 0 0 0 0 0 is the initial
start address -
file length Size of the downloaded file
try-run 4<minutes> indicates the
-
elapsed time elapsed time of the try-run
try-run 11<minutes> indicates the
-
remained time remaining time of the try-run
Activating the Application/Logic

Execute the d - a c t i v e command under the prompt Z T E + > , to activate the
board application/logic in the standby area after the try run succeeds.
<Command Format>
d-active Subrack-NO. Slot-NO. Board-CPU-NO {-p/-f}
TABLE 143 PAR AMETERS OF THE COMM AND D-ACTIVE
Slot-NO. 19; It is 18 or 19 for the NCP board.
-p Activate the board application.
-f Activate the board logic.
Caution: If the application/logic is not activated within 15 minutes after the try-
run, or it is not activated before resetting the NCP board, it will go back to the
original application/logic.
For example, the program activation operation is shown in Figure 37.
FIGURE 37 ACTIVATING THE PROGRAM

Verifying the Activated Application/Logic

Execute the command d - g e t - s t a t u s under the prompt Z T E + > , to verify if
the version of the activated application/logic in the original standby area is
normal.
<Command Format>

For example, to verify the activated application file, the operation and
result are shown in Figure 38.
FIGURE 38 VERIFYING THE ACTIVATED PROGRAM
The parameters in the original standby area (labeled as p r o g r a m n u m b e r :

0 x 0 2 in Figure 38) that need to be verified are described in Table 144.
TABLE 144 DESCRIPTIONS OF P AR AMETERS THAT NEED TO BE VERIFIED AFTER

ACTIVATION

file type -
area
download date File downloaded time


download Should be consistent with
File version downloaded
version the result in Figure 34
try-run type Changes to r e s e r v e d -
The s t a t u s of the area

labeled as p r o g r a m
status m a s t e r indicates the master state
number: 0x01
should change to s l a v e
upgrade N O indicates that the database
-
database upgrade is completed
0 x 0 A 4 0 0 0 0 0 0 is the initial
start address -
file length Size of the downloaded file
try-run
elapsed time Changes to r e s e r v e d -
try-run
remained time Changes to r e s e r v e d -
Upgrading the Application/Logic for

Standby NCP
Note: If only one NCP board is configured, skip this step.
1. Execute the command t e l n e t N E - I P on the EMS computer. Enter

z t e for user name and e c c for password according to the system
prompts. Press ENTER until the prompt Z T E + > appears.
2. Execute the command d - s e t - n c p b a c k s t a t under the prompt Z T E + >

to switch to the standby NCP board, as shown in Figure 39.
FIGURE 39 SWITCHING TO THE STANDBY NCP BOARD

3. Re-perform all the operations from section Upgrade Preparations to

section Verifying the Activated Application/Logic, to complete the
upgrade of the standby NCP board.
Downloading the Database

In the EMS client operation window, select the NE to be upgraded, and
click System →NCP data Management →DB Download to download all
the databases via the EMS software, as shown in Figure 27.
Verifying the Application/Logic Version in

EMS
1. Double-click the NE that has been upgraded in the ZXONM E300 EMS,
to open the Card Management dialog box, as shown in Figure 28.
2. Right click the NCP board to be queried with the version, and the
shortcut menu pops up. Select the Card Special Version menu, as
shown in Figure 28.
3. The Card Special Version dialog box pops up and displays the
application/logic version of the queried NCP board, as shown in Figure
29. If the information displayed is consistent with the downloaded
application/logic, it indicates that the newly downloaded
application/logic is running normally.


Appendix C
Maintenance Forms
This appendix presents some forms used for routine maintenance as

reference for the users.

Half-day Maintenance Record

TABLE 145 HALF-DAY M AINTENANCE FORM
Maintenance Item Result for Reference Check Result
(Record “Normal” when

When normal, the green indicator NOM flashes. there is no alarm, and
record the detailed alarm
indicator status if any
NCP board The yellow indicator ALM1 is on, indicating major or alarm occurs. For service
minor NE/board alarms. boards, the slot number of
the alarm board must be
The red indicator ALM2 is on, indicating critical NE/board
recorded)
alarms
When normal, the green indicator NOM flashes.
The yellow indicator ALM1 is on, indicating major or
OW board minor NE/board alarms.
alarms
minor NE/board alarms.
CSA/CSE board
Board indicators observation
alarms
The red indicator ALM is on when a board alarm occurs
OL64 board minor NE/board alarms.
alarms
alarms
alarms
alarms
LP1 board When normal, the green indicator NOM flashes.

Appendix C - Maintenance Forms
Maintenance Item Result for Reference Check Result

alarms
EPE1/EPT1/EP3
board
alarms
TGE2B/MSE
board
alarms
Summary of the indicator status: (Sum up the indicator status in this period and record the troubleshooting
details.)
Tested by: Check time:
Note: As the boards configuration varies with different sites, the form can be made
according to actual conditions.

Daily Maintenance Record

TABLE 146 DAILY MAINTENANCE RECORD
Maintenance Check
Maintenance Content Result for Reference
Item Result
The buzzer does not sound when there is no alarm

Equipment maintenance
Audio alarm Whether the buzzer sounds
The buzzer sounds when there is an alarm
The green indicator is always on in normal status
The yellow indicator is always on when there is a major

Cabinet Status of the indicator on the
or minor alarm
indicator cabinet
The red indicator is always on when there is a critical
alarm
Whether the server communication

is normal
Normally, the NE icon bears no ”×”
Whether the NE communication is
normal
Navigation Normally, the NE icon bears no ”×”
tree
monitoring Warning alarm, the icon is purple
NE working status Minor alarm, the icon is yellow
Major alarm, the icon is orange
Critical alarm, the icon is red
NE communication is normal or not Normally, the NE icon is green
Warning alarm, the icon is purple
Minor alarm, the icon is yellow

EMS maintenance
NE working state Major alarm, the icon is orange

Topology map
monitoring
Critical alarm, the icon is red
Normally, the connection line is a green real line

Optical connection state When there is a fault with the fiber, the connection line is
a red dashed line
Alarm audio is not shielded

Check the alarm setting
Alarm is not shielded or reversed
Alarm New warning alarm occurs, the purple button flashes

monitoring New minor alarm occurs, the yellow button flashes
Query the alarm state
New major alarm occurs, the orange button flashes
New critical alarm occurs, the red button flashes
Query the performance during the

Performance current 15 minutes and 24 hours
Normally the performance value is 0
monitoring Query the performance during
historic 15 minutes and 24 hours

Maintenance Check
Maintenance Content Result for Reference
Item Result
Summary of maintenance:
(Sum up the equipment and EMS status in this period and record whether the faults have been cleared. If the faults have been
solved, the troubleshooting methods should also be recorded to provide reference for future maintenance work.)
Tested by: Check time:
Note: As there may be no EMS configured at some sites, the form can be made
according to actual conditions.

Weekly Maintenance Record

TABLE 147 WEEKLY M AINTENANCE RECORD
Maintenance
Maintenance Content Check Result Remarks
Item
The fan runs normally or not
Fan check The dust-proof net at the fan bottom is (Record the
clean or not cleansing date)
(Check whether the call is
Check Dial the central site orderwire phone connected and whether the
orderwire voice quality is normal)
telephones
(Non-central (Check whether the call is
The central site dials back the local
site) connected and whether the
orderwire phone
voice quality is normal)
Dial site A orderwire phone connected and whether the
Dial-back connected and whether the
Check Dial site B orderwire phone connected and whether the
orderwire voice quality is normal)
telephones
(Central site) Dial-back connected and whether the
Dial site C orderwire phone connected and whether the
Dial-back connected and whether the
When no service is configured to the
channel, a BER tester is used for the test.
Channel Check (Record the tested BER)
Otherwise the EMS performs the test when
the bit error is 0, it is normal
Summary of maintenance:
(Summing up the check results in this period and recording the troubleshooting details)
Tested by: Check date:
Note: The central site needs to dial the orderwire telephones of all the subnet sites
to test the voice quality of orderwire, while an ordinary site just needs to dial the
central site for test.

Login Password Change Record

TABLE 148 LOGIN P ASSWORD CHANGE RECORD
Recorded into
The Last This Change the Changed Checked Check
Change Date Date Memorandum or by by Date
not
Note: The login password should be changed once a month. The table can be
made according to actual conditions
Note: For irregular checks of system configuration, user operation log, report
printing, and data backup, the maintenance forms can be made according to the
above forms.


Appendix D
Board Replacement
In this appendix, you will learn about:

Board’s plugging/unplugging and precautions.
Board’s replacement procedure and operation steps.
Board Plugging/Unplugging
Unplugging the Board
1. Hold the upper and lower ejector levers, and press down the lever
spring plates, move the levers up/down wards with appropriate force
to free the board from the slot. Figure 40 shows how to free the OL4x2
board.
FIGURE 40 FREE THE OL4X2 BOARD
1. Move lever 1 upward 2. Move lever 2 downward

2. Pinch the board ejector lever with thumb and forefinger of one hand, at
the same time hold the board panel with the other hand, and smoothly
pull the board out of the slot. Figure 41 shows how to pull out the
OL4x2 board.
FIGURE 41 PULL OUT THE OL4X2 BOARD
Plugging the Board

1. Place the ejector lever at leveled position by pressing the spring plate
of ejector lever. Grasp the upper and lower ejector levers, and push in
the board exactly along the guide rail. The board must be kept vertical
throughout the process, and apply appropriate force. Figure 42 shows
how to push in the OL4x2 board.
FIGURE 42 PUSH IN THE OL4X2 BOARD

Appendix D - Board Replacement
2. When the board is about to get into position, clamp the bayonet of
ejector lever with front beam of the sub-rack, push the ejector lever
up/down wards with both hands exerting proper force unless the
ejector lever stands upright and produces the locking sound of "clatter".
The board connector should be fully inserted into the motherboard
socket. In this case, the board panel should be in parallel position with
outer frame of the board area in the cabinet. Now, the board insertion
is complete. Figure 43 shows how to plug the OL4x2 board.
FIGURE 43 PLUG THE OL4X2 BOARD
1. Move lever 1 downward 2. Move lever 2 upward
Board Operation Precautions

1. Since there are many CMOS components in the board, make sure to
wear the anti-static wrist strap for connecting human body with the
equipment protection ground. If the equipment has not been
connected with the protection ground, the anti-static wrist strap won’t
take effect, and some other effective anti-static approach is necessary.
2. There is normally a bag of desiccant in the static-shielding bag, which
is used to absorb the moisture of bag keeping it dry from inside. When
the board is carried from a dry place with low temperature to moist
place with higher temperature, wait for at least half an hour before
unpacking and installation. Otherwise, moisture will condense the
board surface, resulting in board damage.
3. While plugging/unplugging the board, keep it upright and use
appropriate force to avoid bending the contact pins. While
plugging/unplugging the optical line board, carefully handle it and
avoid damaging the fiber interface or coiled cable in the board.

Flowchart of Board Replacement

Make sure to consider the following issues before replacing a board:
All the boards of ZXMP S385 are hot pluggable.

The function of the board in network and in an NE, and the effect on
the service function after it is unplugged.
The version of the spare board should be compatible with the versions
of the current equipment and EMS.
Figure 44 shows the general flow of the board replacement operation.
FIGURE 44 GENERAL FLOWCHART OF BOARD REPLACEMENT
Begin
Prepare a spare
board
Prepare a label
Board under N Service

protection? interruption
Service switching
Unplug board
Attach label on the

faulty board
Plug the spare

board
Restore services
Check Abnormal
working Troubleshooting
status
Normal
End

Preparing a Spare Board

To ensure normal working of the system after replacement with the spare
board, pay attention to the following precautions while preparing the spare
board:
Determine the spare board’s type according to the board to be
replaced, and make sure its model is consistent with the board to be
replaced.
Check if the spare board has any apparent damage, and ensure that it
works normally.
Make sure that the PCB version and software version of the spare
board are compatible with the current NE and EMS.
When the board to be replaced is configured as warm backup mode
(such as the CSA/CSE board), ensure that the software and hardware
versions of both active/standby boards are completely consistent after
replacement.
Preparing a Label
The label is used to identify the board that has been unplugged during the
replacement. The label size is decided by the maintenance personnel. The
label contents include the site name, equipment name, fault cause, board
name, handling process, the handling person, and time.
Service Switching
For the board configured with service protection or backup, the service
function processed by it should be switched to the standby board, so that
the service is not interrupted by board unplugging.
While unplugging the board without service protection or backup, the
service function of this board would be interrupted. Explain this to the user
before unplugging, and take any possible measure to minimize drawbacks
of service interruption.
Unplugging the Board

Caution: Board unplugging operation may interrupt the service, or even can stop
the working of the whole NE. Ensure to make enough preparations before the
operation and take any possible measure to minimize the drawbacks of service
interruption.
Before unplugging the board, unplug the fiber pigtail and cable connected
to the board panel. Refer to Unplugging the Board for description of
unplugging operation.

Labeling the Faulty Board

Stick the prepared label onto the PCB of the unplugged faulty board.
Plugging the Board

Plug and install the spare board, and restore connections of the fiber
pigtails and cables to the board. Refer to Plugging the Board for plugging
operation.
Restoring the Service Function

Once the spare board is installed, its service function should be recovered
immediately. Check the board/equipment working status. Verify the
normal working of both the equipment and the service functions to ensure
successful board replacement. Otherwise, perform troubleshooting till the
equipment work and service functions become normal.
Board Replacement Procedure

This section describes the board replacement procedure of the NCP,
CSA/CSE, OW, OL1/OL4/OL16/OL64, LP1, EPE1/EPT1/EP3, TGE2B, SEC,
and MSEB boards.
NE Control Processor (NCP)

The NCP board is hot pluggable. Its direct replacement does not affect the
service but interrupts EMS monitoring temporarily. The NE needs resetting
while reconfiguring the NCP parameters and data, which in turn causes
service interruption.
1. Prepare the spare board and label as described in the section Flowchart
of Board Replacement. Ensure the compatibility among the BOOTROM
and main program of the NCP board, and the EMS software.
2. Unplug the board that needs to be replaced and label it.
3. Set DIP-switch of the spare NCP board to full ON state, which makes
the NCP board to be in DOWNLOAD state; and plug the board into the
sub-rack. Then execute the command p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the
EMS computer to check if it is possible to ping the NE.
4. Download the application and initial parameters via FTP, that are
consistent with the original NCP board; and the NCP board can reset
automatically if the setting is successful. Refer to Appendix B for the
details of NCP program download.
5. Set the fourth digit of the DIP-switch on the NCP board to OFF, and
write the NE configuration data onto the NCP board with EMS software.

6. Replacement confirmation
In the Download state, 192.192.192.11 can be pinged through on
the computer.
After replacement, select the NE that has replaced the NCP board in
the operation window at the EMS client. If the NCP time could be
extracted, it indicates the NCP board is successfully replaced.
Cross-connect and Clock Board

(CSA/CSE)
The CSA/CSE board supports warm backup and is hot pluggable. The
CSA/CSE board replacement does not affect services when the CSA/CSE is
in the warm backup state. However, the CSA/CSE board replacement will
affect the transmission/receiving of the NE service when it is not in the
warm backup state.
1. Prepare the spare board and label it as described in the section

Flowchart of Board Replacement. The two CSA/CSE boards of warm-
backup configuration must have consistent PCB versions.
2. If the CSA/CSE boards are configured in the warm backup mode,
switch the system clock to the other CSA/CSE board through EMS,
unplug the CSA/CSE board to be replaced, attach the label, plug the
spare board, and switch the system clock to the plugged CSA/CSE
board. If the CSA/CSE board is not configured in the warm backup
mode, directly unplug the CSA/CSE board, attach the label, and plug
the spare board.
After replacement, the green NOM indicator light on the CSA/CSE
board flashes regularly. It indicates that the service is recovered and
the board replacement is successful.
Orderwire Board (OW)

The OW board is hot pluggable and supports warm backup. The OW board
is responsible for orderwire phones, low-speed data service. Replacing the
OW board will result in the interruption of orderwire phones and low-speed
data service, and will not affect tributary services.
of Board Replacement.
2. Unplug the board to be replaced, attach the label, and plug the spare
board.
After replacement, the green NOM indicator light on the board flashes
slowly and regularly, and the orderwire phone and data service are
normal. These indicate that the board replacement is successful.

Optical Line Board (OL64/OL16/OL4/OL1)

The optical line board is hot pluggable. Its replacement will interrupt the
service in case of unprotected networking. In protected networking if
switched to protection mode, the service will not be interrupted.
Note: The board replacement when the multiplex section switchover ring is
configured is too complex to describe. Conduct this kind of board replacement
under the guidance of ZTE maintenance engineers.
Board replacement without service protection configured

Prepare the spare board and label as described in the section
Flowchart of Board Replacement.
Unplug the fiber pigtail connected to the optical interface, unplug
the board to be replaced, attach the label, plug the spare board,
and connect the fiber pigtail.
Replacement confirmation
After replacement, the green NOM indicator light on the board
flashes slowly and regularly; and the green TX and RX indicator
lights, corresponding to the optical interface for the original service,
are constantly on. These indicate that the service is normal and the
board replacement is successful.
Board replacement with path protection configured
Prepare the spare board and label as described in the section
Flowchart of Board Replacement.
Unplug the fiber pigtail connected to the optical interface, wait until
the service switches to the protection path, unplug the board to be
replaced, attach the label, plug the spare board, and connect the
fiber pigtail.
Replacement confirmation.
After replacement, the green NOM indicator light on the board
flashes slowly and regularly; and the green TX and RX indicator
lights, corresponding to the optical interface for the original service,
are constantly on. These indicate that the service is normal and the
board replacement is successful.
Line Processor (LP1)

The line processor is hot pluggable. Its replacement will interrupt the
service.
board.

slowly and regularly, and the service performance is normal. It
indicates that the board replacement is successful.
Electrical Processor (EPE1/EPT1/EP3)

The electrical processor is hot pluggable, and its replacement would
interrupt the service.
board.
slowly and regularly, and the service performance is normal. It
indicates that the board replacement is successful.
Ethernet Board (TGE2B/MSEB/SEC)

The ZXMP S385 supports three kinds of Ethernet boards: TGE2B, MSEB,
and SEC, which are all hot pluggable. The Ethernet optical interfaces
locate on the board panel. Replacing the Ethernet board would interrupt
the Ethernet service.
board.
slowly and regularly. It indicates that the service performance is
normal, and the board replacement is successful.


Appendix E
Equipment Upgrade

All the software and hardware versions involved in ZXMP S385.
Upgrade operation steps, covering hardware upgrade, EMS software
upgrade, and board software upgrade.
Version Overview
To differentiate between new and old hardware/software, all of them are
labeled with version numbers, including equipment version, EMS software
version, board PCB version, and software versions of the NCP board and
other boards.
Equipment version: It refers to the development version of ZXMP

S385, which is V2.00&V2.10 currently.
EMS software version: It refers to the development version of the
EMS software. To query this version, go to the operation window of the
EMS software client, select About option in the Help menu to pop up
the information dialogue box for EMS software version, as shown in
Figure 45.

FIGURE 45 EMS SOFTWARE VERSION
Consider Figure 45 as an example, the present EMS is ZXONM E300,

and the versions of all the components are V3.17 R2.
Board PCB version: It locates at the component side of the board
PCB. The board PCB number starts with letter “B” followed by six
Arabic digits, out of which every two, from left to right, indicates its
version setup year, month, and change mark.
NCP board software version: The chips on the NCP board are
classified into BOOTROM chip and FLASH chip depending on different
functions. The BOOTROM chip stores the board start program, while
the FLASH chip stores the NCP main program and database program.
The program version information of the chip is usually written on an
adhesive slip, which is pasted on the corresponding chip.
Software version of other boards: To monitor and manage board
running, an EEPROM chip is set on the board for storing the board-
running program. The version information of this program is usually
written on an adhesive slip, which is pasted on the corresponding chip.
Hardware Upgrade
Hardware upgrade is to replace the presently in-use equipment hardware
with the equipment hardware of higher version. For successful upgrade,
make sure to modify the corresponding hardware version information in
the EMS software to avoid the software and hardware cooperation errors.

Appendix E - Equipment Upgrade
EMS Software Upgrade

Follow the following steps to upgrade the EMS software.
Upgrade preparations
Before upgrading the EMS software, first back up the software to be
upgraded; and carefully check the compatibility of the board hardware,
board program and the EMS software. In case of incompatibility, consider
to upgrade the board program of replace the board.
Network configuration data backup/configuration

If the network configuration data format of new version EMS software is
compatible with the old version software, the user can back up the
network configuration information in the EMS computer by using the
backup function of EMS software. If the data format of the old version of
EMS software is incompatible with the new version software, first install
the new version of EMS software in another computer, configure the
network data and back it up, and then copy the backed up data to the EMS
computer. By doing so, the user can easily recover the data after installing
new version EMS software.
Uninstall the old version EMS software

Uninstall the EMS software through Add/delete program provided by the
operating system of the EMS computer.
Install the new version of EMS software

Install the new version EMS software according to the EMS installation
manual.
Restore/Reconfigure the network configuration data

Use the DB Backup or Restore function of the EMS software to recover
the previously configured or backed up data into the EMS.
Re-downloading and connecting the NE equipment

Once the new version of EMS software issues the configuration data to the
NE, check whether the monitor and management operation of the EMS
software on the NE is normal. If there is any abnormality, find the cause
and solve the problem. When all the functions are normal, the EMS
software upgrade is complete and successful.

Board Software Upgrade

NCP board software upgrade
Carefully check the NCP board software of new version for compatibility
with the EMS software before upgrade. In case of incompatibility, consider
upgrading the EMS software simultaneously.
The NCP board software upgrade covers BOOTROM upgrade and FLASH
upgrade, which could be conducted separately as long as BOOTROM and
the main program are compatible.
To upgrade the BOOTROM program, typically burn the new version of
the BOOTROM program onto the chip by using the chip burner, and
replace the chip on site.
To upgrade the main program/logic of the NCP board, it is necessary to
write the application file onto the NCP board through FTP via the
network interface. Refer to Appendix B for detailed operations of
upgrading the main program chip of NCP.
Software Upgrade of Other Boards

Before upgrading the board software, check the board software of the new
version for compatibility with the NCP software and EMS software. In case
of incompatibility, consider the necessity of simultaneous upgrading.
The upgrade of the board software covers: board BOOTROM upgrade,
board logic/program upgrade. In general, the board BOOTROM needs no
upgrade. Both of these upgrades could be conducted separately as long as
the board BOOTROM and the main program are compatible.
To upgrade the board BOOTROM program, burn the new version of the
BOOTROM program onto the chip by using the chip burner, and replace
the chip on site.
To upgrade the board application/logic program, use the remote
upgrade method. Download the upgraded program through FTP to the
NCP of the NE, and then load it onto the board. The detailed upgrade
steps are similar to the remote upgrade of the NCP main program and
logic. Refer to Appendix B.

Appendix F
Common Instruments and

Meters
This appendix introduces the meters (including the optical power meter,
BER tester, and chip burner) that are frequently used in routine
maintenance. It covers their functions, operations, parameter setting, and
operation precautions.
Note: Since the meters with similar functions have various models, the
introduction in this appendix serves only as reference. For details on how to use
the meters, refer to their instruction manuals.
PMS-1A Optical Power Meter

Function
Figure 46 shows the external view of PMS-1A optical power meter.
FIGURE 46 EXTERNAL VIEW OF THE PMS-1 A OPTICAL POWER METER

The PMS-1A optical power meter mainly serves to measure the continuous
optical signal power, employing 4-digit liquid crystal display. It is capable
of automatic measurement range switching, automatic power-off,
automatic reset zero, multi-wavelength measurement and relative power
measurement, etc. The working wavelengths of the PMS-1A optical power
meter are 1300 nm, 1310 nm, 1480 nm, and 1550 nm, which are optional.
The measurement range is -40 dBm ~ +20 dBm (0.1 nW ~ 100 mW), with
the measurement accuracy of ±5%, and the detector interface is the FC
type.
Panel Description
Figure 47 describes the Front Panel of PMS-1A optical power meter.
FIGURE 47 FRONT P ANEL OF THE PMS-1A OPTICAL POWER METER
1 7
2
3
1. Clear button 2. WATT unit selection button

3. dBm unit selection button 4. Wavelength selection button
5. External power supply plug 6. Relative measurement state switching button
7. Power switch 8. LCD 9. Detector interface

Appendix F - Common Instruments and Meters
Operation Flowchart
Figure 48 shows the operation flowchart of measurement via the PMS-1A
optical power meter, along with the specific operation in each step.
FIGURE 48 OPERATION FLOWCHART OF MEASUREMENT VIA THE PMS-1A OPTICAL POWER

METER
Press ON/OFF to
power on optical
power meter
Press λ to select
wavelength
Press CLEAR to
clear all digits
Connect optical
source to be tested
with optical power
meter
Relative power
Select measurement
measurement
mode
Absolute power Press dBrel to
measurement enter relative
measurement state
dBm
Select unit
dBm
WATT Select unit
Press
Press dBm WATT
WATT
Press
Press dBm
WATT
Read measurement results
Precautions
Remember to recharge the batteries in time.
Cover the detector before the clearing operation lest the light enter
inside and affect the measurements.

Select an appropriate wavelength for the corresponding optical

interface for measurement. To be specific, select the 1310 nm
wavelength for the I.X, S-X.1 and L-X.1 optical interfaces, and select
the 1550 nm wavelength for the S-X.2 and L-X.2 optical interfaces,
where X represents the level of SDH signal, and X = 1, 4, 16, 64.
While using the meter, protect it from moisture, shake, dust, and heat
source. Keep the detector and connector clean.
If the meter has been stored/used in low-temperature condition for a
long time, and is to be used in high-temperature condition, put it in the
high-temperature condition for some time before using lest the
condensation damage it.
ALL-11 Chip Burner

Function
Figure 49 shows the external view of ALL-11 chip burner.
FIGURE 49 EXTERNAL VIEW OF THE ALL-11 CHIP BURNER
The ALL-11 chip burner serves to burn E/EPROM, MCU/MPU, and PLD. It is
connected with the PC through RS232C serial port or parallel port of the
PC, and it is controlled by the special program installed in the Windows
system. With the IC multi-tap or conversion socket, the ALL-11 chip
burner is compatible with most of the present IC models and packages.

Panel Description
Figure 50 shows the panel of the ALL-11 chip burner.
FIGURE 50 PANEL OF THE ALL-11 CHIP BURNER
9 8 7
GOOD BUSY YES
1 2 3
1. Success indicator light 2. Working indicator light

3. Extended memory slot 4. YES shortcut key
5. 40-jack socket 6. Power indicator light
7. Communication port 8. Power supply plug 9. Power switch
Figure 51 defines the 40-pin socket.
FIGURE 51 SECTION VIEW OF 40-PIN SOCKET
1
3
Chip insertion guide
1. Extractor lever 2. Socket 3. Jack

Operation Flow
Figure 52 shows the operation flow for burning a chip with ALL-11 chip
burner. Before burning, make sure that the chip burner is connected with
PC, the given burning software has been properly/successfully installed on
PC, and the connection between the PC and chip burner has been
established.
FIGURE 52 OPERATION FLOW OF THE ALL-11 CHIP BURNER
Power on chip burner

and start the burning
software WACCESS
Select a chip
manufacturer
Select a chip type and

model
Start chip burning

program
Read from
Select source another chip
of chip contents
Read Insert the source chip
from a file into the chip burner
Select the file and load
it
Read source chip
Specify file format
Set chip reading

parameters
Insert the target chip
into the chip burner
Run chip burning

program
Set chip burning

parameters
No
Verification passed?
Yes
Burning succeeds

Precautions
During the operation, observe the device indicator lights status and
check whether it complies with the current operation. If any
incompliance, pause the operation to find out the cause.
In the program, the chip manufacturer information, its type and model
should be set as per actual chip. The file format should be set
according to the format of actual file. The two common file formats are
BIN and HEX. A file with the extension of BIN is binary file, and its file
format should be selected as Binary. A file with the extension of HEX is
hexadecimal file, and its file format should be selected as Intel HEX.
To insert the chip into the chip burner socket, ensure that pins are in
the correct sequence by follow the Chip insertion guide shown in Figure
51. Usually, lower part of the chip should be aligned with the bottom of
the socket.
Pull over the socket extractor lever before inserting the chip, and press
it down after insertion. Make sure the chip’s pins are in reliable contact.
Figure 51 shows the extractor levers positions.
YGBERT-2M 2 M BER Tester

Function
The portable pocket YGBERT-2M BER tester serves to detect the bit errors
and to monitor alarms for the PCM digital transmission system, fiber
communication system, and digital microwave communication system. Its
measuring capacity is 2 Mbit/s, and output of the code generator complies
with CCITT G.703 recommendation. It permits the line attenuation ranging
from 0 dB to 6 dB, and permits insertion of a single bit error or periodic bit
errors. It has the LEDs to indicate AIS, out of synchronization and bit
errors; and provides the function of buzzer alarm. Its external view is
shown in Figure 53.
FIGURE 53 EXTERNAL VIEW OF THE YGBERT-2M BER TESTER

Panel Description
Figure 54 shows the panel of YGBERT-2M BER tester.
FIGURE 54 PANEL OF THE YGBERT-2M BER TESTER
18 16
17
Power
1
2
15
4 No signal
AIS
5 No sync
Bit Error
6
Setup
7
Select
8
9 Start/Stop
10
BE/BER
11
G.821
12
Tx Bit Error
13
14
1. Power off. 2. Power on and system reset. 3. No signal. 4. AIS.

5. Out of synchronization. 6. Bit Error. 7. Enter/Exit BER tester
parameter setup. 8. Setup of BER tester parameters/status. 9. Cursor
movement. 10. Start/Stop BER tester. 11. BE/BER display switching.
12. Display G.821 analysis results. 13. Single bit error insertion.
14. External power supply plug. 15. LCD.
16. Transmit port. 17. Printing port. 18. Receive port.

Operation Flow
Figure 55 shows the operation flow for testing bit errors with YGBERT-2M
BER tester.
FIGURE 55 BER TEST OPERATION FLOW OF THE YGBERT-2M BER TESTER
Power on BER tester and

connect equipment to be
tested with BER tester
Set code pattern

2 15-1 PRBS15
Start test
Keep test for a predefined

period of time
Stop test
Read test results
Precautions
Remember to recharge the battery in time. The fully charged battery
can last for about four consecutive hours. Use the external power
supply for 24-hour bit error test.
Select the code pattern of PRBS15 to test the SDH equipment.

SDH Analyzer
Figure 56 shows the external view of HP37718A SDH analyzer.
FIGURE 56 EXTERNAL VIEW OF THE HP37718A SDH ANALYZER
Due to complex operation process of HP37718A SDH analyzer, its details

are not covered in this document. Refer to the relevant document for
detailed instructions.

Appendix G
Alarm Quick Reference Table
Alarm
Page
Detection Alarm Name Alarm Level
No.
Point
Loss of received 10 G optical signal Critical 78
Loss of received 2.5 G optical signal Critical 79
Loss of received 622 M optical signal Critical 80
Loss of received 155 M optical signal Critical 81
Loss of 155 M electrical signal Critical 82
Physical layer Loss of 45 M electrical signal Critical 83
Loss of 1.5 M electrical signal Critical 86
CV performance over-threshold Warning 87
Optical received power over-threshold Major 88
Loss of frame Critical 89
Unavailable time starts Major 90
B1 UAS performance over-threshold Major 91
Out of frame Critical 92
Regenerator
OFS performance over-threshold Major 93
section layer
Regenerator section signal degraded Minor 94
B1 SES performance over-threshold Major 95
B1 ES performance over-threshold Major 96
B1 BBE performance over-threshold Major 97
Multiplex section Multiplex section alarm indication signal Major 98
layer
Unavailable time starts Major 99
Multiplex section remote defect indication Minor 100
B2 UAS performance over-threshold Major 101
B2 FEUAS performance over-threshold Major 102

Alarm
Page
No.
Point
Multiplex section signal degraded Minor 103
B2 bit error cross-threshold Major 104
B2 SES performance over-threshold Major 105
B2 FESES performance over-threshold Major 106
B2 ES performance over-threshold Major 107
B2 FEES performance over-threshold Major 108
B2 BBE performance over-threshold Major 109
B2 FEBBE performance over-threshold Major 110
Multiplex section protection switching event Minor 111
AU4 path alarm indication signal, Unavailable
Major 112
time starts
Loss of AU4 pointer Critical 113
Remote defect indication (higher-order VC4
Minor 114
path virtual container)
B3 UAS performance over-threshold (higher-
Major 115
order VC4 path virtual container)
B3 FEUAS performance over-threshold
Major 116
(higher-order VC4 path virtual container)
VC4 higher-order path signal degraded Minor 118
B3 SES performance over-threshold (higher-
Major 119
Administrative
unit (AU4), B3 FESES performance over-threshold
Major 120
tributary unit (higher-order VC4 path virtual container)
(TU3), Higher-
B3 ES performance over-threshold (higher-
order path Major 121
(VC4/VC3)
B3 FEES performance over-threshold (higher-
Major 122
B3 BBE performance over-threshold (higher-
Major 123
B3 FEBBE performance over-threshold
Major 124
(higher-order VC4 path virtual container)
VC4 higher-order path unequipped Major 125
VC4 higher-order path trace ID mismatch Major 126
VC4 signal label mismatch Major 127
AU4 PJE+/PJE- performance over-threshold Critical 128
AU4 protection switching event Minor 129
Tributary unit TU12 path alarm indication signal, Unavailable
Major 147
(TU12) and time starts
lower-order path
(VC12) Loss of TU12 pointer Critical 148
Remote defect indication Minor 149

Appendix G - Alarm Quick Reference Table
Alarm
Page
No.
Point
V5 UAS performance over-threshold Major 150
Tributary unit
(TU12) and V5 FEUAS performance over-threshold Major 154
lower-order path V5 SES performance over-threshold Major 155
(VC12)
V5 FESES performance over-threshold Major 156
V5 ES performance over-threshold Major 157
V5 FEES performance over-threshold Major 158
V5 BBE performance over-threshold Major 159
V5 FEBBE performance over-threshold Major 160
TU12 PJE+/PJE- performance over-threshold Major 161
TU12 protection switching event Minor 162
Synchronous Loss of timing input Critical 163

timing source Loss of timing output Critical 164
Power supply fault Critical 165
Board Board out of position Critical 165
Board type mismatch Critical 166
Ethernet physical
electrical Ethernet port unconnected Critical 166
interface
Ethernet physical
Loss of received signal Critical 167
optical interface


Appendix H
Abbreviations
Abbreviations Full Name

A
ADM Add/Drop Multiplexer
AI Adapted Information
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
ANSI American National Standards Institute
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
AU-n Administrative Unit, level n
AUG Administrative Unit Group
B
BA Booster Amplifier
BBER Background Block Error Ratio
BER Bit Error Ratio
BIP-X Bit Interleaved Parity of depth X
BITS Building Integrated Timing Supply
C
CE CONFORMITE EUROPENDE
CF Compact Flash
CIDR Classless Inter-Domain Routing
CM Connection Matrix
CMIP Common Management Information Protocol
C-n Container-n
CP Connection Point
CRC Cyclic Redundancy Check
CS Cross-connect
CTP Connection Termination Point


CV Code Violation
D
DC Direct Current
DCC Data Communications Channel
DCE Data Circuit-terminating Equipment
DCM Dispersion Compensation Module
DCN Data Communications Network
DCS Digital Cross-connect System
DNI Dual Node Interconnection
DTE Data Terminal Equipment
DXC Digital Cross Connect
E
EOW Engineering OrderWire
ECC Embedded Control Channel
EDFA Erbium Doped Fiber Amplifier
EMF Equipment Management Function
EMC ElectroMagnetic Compatibility
EMI ElectroMagnetic Interference
EML Element Management Layer
EMS Equipment Management System
ES Errored Second
ETSI European Telecommunication Standards Institute
EUT Equipment Under Test
F
FAS Frame Alignment Signal
FDDI Fiber Distributed Data Interface
FDM Frequency Division Multiplexing
FE Fast Ethernet
FEBBE Far End Background Block Error
FEC Forward Error Correction
FLSM Full Length Subnet Mask
G
GE Gigabit Ethernet
GUI Graphical User Interface
H

Appendix H - Abbreviations

HW High Way
HDLC High Digital Link Control
HPA Higher order Path Adaptation
HPC Higher order Path Connection
HPP Higher order Path Protection
HPT Higher order Path Termination
HTCA Higher order path Tandem Connection Adaptation
HTCT Higher order path Tandem Connection Termination
HTCM Higher order path Tandem Connection Monitor
I
IC Integrated Circuit.
IP Internet Protocol
ITE Integrated Terminal Equipment
International Telecommunication
ITU-T
Union-Telecommunication Standardization Sector
L
L2 Layer 2
LAN Local Area Network
LAPD Link Access Procedure for D-channel
LA Line Amplifier
LMT Local Management Terminal
LO Lower Order
LOF Loss Of Frame
LOM Loss Of Multiframe
LOP Loss Of Pointer
LOS Loss Of Signal
LP Lower order Path
LPA Lower order Path Adaptation
LPC Lower order Path Connection
LPP Lower order Path Protection
LIT Loss of all Incoming Timing references
M
MAF Management Application Function
MC Matrix Connection
MCU Micro Control Unit
MD Mediation Device
MF Mediation Function


MM Multi Mode (optical fiber)
MS Multiplex Section
MS-AIS Multiplex Section - Alarm Indication Signal
MSOH Multiplex Section OverHead
MSP Multiplex Section Protection
MS-PSC Multiplex Section - Protection Switching Count
MS-PSD Multiplex Section - Protection Switching Duration
MS-SPRing Multiplex Section Shared Protection Ring
MST Multiplex Section Termination
MTIE Maximum Time Interval Error
N
NC Network Connection
NE Network Element
NEF Network Element Function
NEL Network Element Layer
NML Network Management Layer
NMS Network element Management System
NNI Network Node Interface
NU National Use
NRZ Non-Return to Zero
O
OA Optical Amplifier
OAM Operation, Administration and Maintenance
ODP Open Distributed Processing
OFA Optical Fiber Amplifier
OHA OverHead Access
OOF Out Of Frame
OSF Operation System Function
OSI Open System Interconnection
OW Order Wire
P
PA Pre-Amplifier
PCB Printed Circuit Board
PCM Pulse Code Modulation
PDH Plesiochronous Digital Hierarchy
PGND Protection GND
PJE+ Positive Pointer Justification Event

Appendix H - Abbreviations

PJE- Negative Pointer Justification Event
PMD Polarization Mode Dispersion
POH Path OverHead
PPI PDH Physical Interface
PRC Primary Reference Clock
PRS Primary Reference Source
PS Protection Switching
PSE Protection Switching Event
PT Path Termination
PTR Pointer
Q
QA Q Adaptor
QAF Q Adaptor Function
R
RAM Random Access Memory
RDI Remote Defect Indication
REI Remote Error Indication
RFI Remote Failure Indication
RI Remote Information
RPR Resilient Packet Ring
RS Regenerator Section
RSOH Regenerator Section OverHead
RST Regenerator Section Termination
S
SDH Synchronous Digital Hierarchy
SEC SDH Equipment Clock
SEMF Synchronous Equipment Management Function
SESR Severely Errored Second Ratio
SETPI Synchronous Equipment Timing Physical Interface
SETS Synchronous Equipment Timing Source
SFP Small Form Factor Pluggable
SM Single Mode (optical fiber)
SMCC Sub-network Management Control Center
SML Service Management Layer
SMN SDH Management Network
SMS SDH Management Sub-network


Sn Higher order VC - n layer (n=3, 4)
SNC Sub-Network Connection
SNCP Sub-Network Connection Protection
SPRING Shared Protection Ring
SPI SDH Physical Interface
SSD Server Signal Degrade
SSF Server Signal Failure
SSM Synchronization Status Message
STM-N Synchronous Transport Module, level N (N=1, 4, 16, 64)
T
TCM Tandem Connection Monitor
TCP Termination Connection Point
TCS Time division Cross-connect
TD Transmit Degrade
TDEV Time Deviation
TF Transmit Fail
TM Terminal Multiplexer
TMN Telecommunications Management Network
TS Time Slot
TSA Time Slot Assignment
TU-m Tributary Unit, level m
TUG-m Tributary Unit Group, level m
U
UNEQ UN-Equipped
UNI User Network Interface
V
VC-n Virtual Container, level n
VSLM Variable Length Subnet Mask
W
WAN Wide Area Network
WDM Wavelength Division Multiplexing
WS Work Station
WSF Work Station Function
WTR Wait to Restore Time

Figures
Figure 1 The ZXMP S385 Software Loopback in Different Directions ...................28

Figure 2 Optical Launched Power Test ...........................................................29
Figure 3 Network Cable...............................................................................35
Figure 4 Troubleshooting Procedures........................................................... 170
Figure 5 Communication Fault Troubleshooting Flow Chart ............................. 177
Figure 6 Fault Category Determination Flow Chart ........................................ 178
Figure 7 Loop-back Segment by Segment .................................................... 178
Figure 8 Connections of SEC Boards............................................................ 194
Figure 9 Network Architecture in Case 1 ...................................................... 197
Figure 10 Network Architecture in Case 2 .................................................... 199
Figure 15 Network Topology ...................................................................... 213
Figure 16 NCP PCB Board .......................................................................... 222
Figure 17 Local Upgrade Flowchart ............................................................. 224
Figure 18 Flowchart of Local Upgrade Preparations........................................ 225
Figure 19 Erase the Database .................................................................... 226
Figure 20 Erase the Chip Area Which Saves the Application Program ............... 227
Figure 21 Erase the Chip Area Which Saves the Logic Program ....................... 227
Figure 22 Configure the NE Related Information ........................................... 227
Figure 23 Format the CF Card .................................................................... 228
Figure 24 Local Download of NCP Application to NE ....................................... 230
Figure 25 Local Upgrade of NCP Application to NE ......................................... 231
Figure 26 Version Information for Local Upgrade of Board Application .............. 232
Figure 27 Download DB Dialog Box of the EMS ............................................. 233
Figure 28 Card Management Dialog Box ...................................................... 234
Figure 29 Card Special Version Dialog Box ................................................... 235
Figure 30 Remote Upgrade Flowchart.......................................................... 236
Figure 31 MasterSlaveBrd Switch Dialog Box ................................................ 237
Figure 32 Confirming the Address of the Master NCP Board ............................ 238
Figure 33 Remote Upgrade of Application .................................................... 239
Figure 34 Verifying the Upgraded Program................................................... 240
Figure 35 Try Run of the Program............................................................... 242
Figure 36 Verifying the Program that Passed the Try Run ............................... 243
Figure 37 Activating the Program ............................................................... 244
Figure 38 Verifying the Activated Program ................................................... 245
Figure 39 Switching to the Standby NCP Board ............................................. 246
Figure 40 Free the OL4x2 Board ................................................................. 257
Figure 41 Pull out the OL4x2 Board............................................................. 258
Figure 42 Push in the OL4x2 Board ............................................................. 258
Figure 43 Plug the OL4x2 Board ................................................................. 259
Figure 44 General Flowchart of Board Replacement ....................................... 260
Figure 45 EMS Software Version................................................................. 268
Figure 46 External View of the PMS-1A Optical Power Meter ........................... 271
Figure 47 Front Panel of the PMS-1A Optical Power Meter .............................. 272
Figure 48 Operation Flowchart of Measurement via the PMS-1A Optical Power
Meter .............................................................................................. 273
Figure 49 External View of the ALL-11 Chip Burner ....................................... 274

Figure 50 Panel of the ALL-11 Chip Burner................................................... 275

Figure 51 Section View of 40-pin Socket ...................................................... 275
Figure 52 Operation Flow of the ALL-11 Chip Burner...................................... 276
Figure 53 External View of the YGBERT-2M BER Tester .................................. 277
Figure 54 Panel of the YGBERT-2M BER Tester ............................................. 278
Figure 55 BER Test Operation Flow of the YGBERT-2M BER Tester ................... 279
Figure 56 External View of the HP37718A SDH Analyzer ................................ 280

Tables
Table 1 Typographical Conventions ...............................................................xv

Table 2 Mouse Operation Conventions ...........................................................xv
Table 3 Safety Signs.................................................................................. xvi
Table 4 Maintenance Tools ..........................................................................22
Table 5 Common Fiber Pigtail Connectors (Plugs)............................................25
Table 6 Loopback Points and Corresponding Boards ........................................28
Table 7 The Correspondences between the Bit Error Insertion Points, Bit Error
Types, and Boards ..............................................................................31
Table 8 Alarm Insertion Points and Corresponding Boards ................................31
Table 9 Color Spectrums and Connection Relations of the Crossover Cable .........35
Table 10 Color Spectrums and Connection Relations of the Straight-through
network cable ....................................................................................35
Table 11 List of Routine Maintenance Items of the ZXMP S385..........................39
Table 12 Meanings of the ZXMP S385 Cabinet Indicators..................................44
Table 13 Correspondences between the Working Status and the Indicator Light
Status of the NCP Board ......................................................................45
Status of the OW Board .......................................................................45
Status of CSA/CSE Board .....................................................................46
Status of the LP1 Board .......................................................................46
Status of Electrical Tributary Boards ......................................................47
Status of the Optical Line Boards ..........................................................47
Status of the TGE2B/MSE Board............................................................48
Status of the SEC Board ......................................................................48
Status of Optical Amplifier Boards .........................................................49
Table 22 The Default Relationships between Icon Colors and Alarms..................53
Table 23 List of SDH Interface Performance Messages .....................................59
Table 24 List of Analogue Performance Messages ............................................61
Table 25 SDH Performance Messages Detectable by Ethernet Board ..................61
Table 26 Analogue Performance Messages Detectable by Ethernet Board............62
Table 27 Data Performance Messages of the ZXMP S385 Ethernet Board ............62
Table 28 SDH Alarm Messages of the ZXMP S385 ...........................................74
Table 29 Alarm Messages of the ZXMP S385 Ethernet Board.............................76
Table 30 Loss of Received 10 G Optical Signal ................................................78
Table 31 Loss of Received 2.5 G Optical Signal ...............................................79
Table 32 Loss of Received 622 M Optical Signal ..............................................80
Table 33 Loss of Received 155 M Optical Signal ..............................................81
Table 34 Loss of 155 M Electrical Signal ........................................................82
Table 35 Loss of 45 M Electrical Signal ..........................................................83
Table 36 Loss of 34 M Electrical Signal ..........................................................84
Table 37 Loss of 2 M Electrical Signal ............................................................85
Table 38 Loss of 1.5 M Electrical Signal .........................................................86

Table 39 CV Performance Over threshold.......................................................87

Table 40 Optical Received Power Over-Threshold ............................................88
Table 41 Loss of Frame ...............................................................................89
Table 42 Unavailable Time Starts (Regenerator Section) ..................................90
Table 43 B1 UAS Performance Over-Threshold ...............................................91
Table 44 Out of Frame ................................................................................92
Table 45 OFS Performance Over-Threshold ....................................................93
Table 46 Regenerator Section Signal Degraded...............................................94
Table 47 B1 SES Performance Over-Threshold................................................95
Table 48 B1 ES Performance Over-Threshold..................................................96
Table 49 B1 BBE Performance Over-Threshold................................................97
Table 50 Multiplex Section Alarm Indication Signal (MS-AIS) ............................98
Table 51 Unavailable Time (Multiplex Section) ................................................99
Table 52 Multiplex Section Remote Defect Indication (MS-RDI) ....................... 100
Table 53 B2 UAS Performance Over-Threshold ............................................. 101
Table 54 B2 FEUAS Performance Over-Threshold .......................................... 102
Table 55 Multiplex Section Signal Degraded (MS-DEG) .................................. 103
Table 56 B2 Bit Errors Cross-Threshold (MS-EXC) ......................................... 104
Table 57 B2 SES Performance Over-Threshold.............................................. 105
Table 58 B2 FESES Performance Over-Threshold .......................................... 106
Table 59 B2 ES Performance Over-Threshold................................................ 107
Table 60 B2 FEES Performance Over-Threshold ............................................ 108
Table 61 B2 BBE Performance Over-Threshold.............................................. 109
Table 62 B2 FEBBE Performance Over-Threshold .......................................... 110
Table 63 Multiplex Section Protection Switching Event ................................... 111
Table 64 AU4 Path Alarm Indication Signal, Unavailable Time ......................... 112
Table 65 Loss of AU4 Pointer ..................................................................... 113
Table 66 Remote Defect Indication (VC4 Higher-Order Path Virtual Container) .. 114
Table 67 B3 UAS Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 115
Table 68 B3 FEUAS Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 116
Table 69 Loss of Multi-Frame (VC4 Higher-order Path Virtual Container) .......... 117
Table 70 VC4 Higher-Order Path Signal Degraded ......................................... 118
Table 71 B3 SES Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 119
Table 72 B3 FESES Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 120
Table 73 B3 ES Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 121
Table 74 B3 FEES Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 122
Table 75 B3 BBE Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 123
Table 76 B3 FEBBE Performance Over-Threshold (VC4 Higher-Order Path Virtual
Container) ....................................................................................... 124
Table 77 VC4 Higher-Order Path Unequipped ............................................... 125
Table 78 VC4 Higher-Order Path Trace Identifier Mismatch............................. 126
Table 79 VC4 Signal Label Mismatch ........................................................... 127
Table 80 AU4 PJE+/PJE- Performance Over-Threshold ................................... 128
Table 81 AU4 Protection Switching Event ..................................................... 129
Table 82 TU3 Path Alarm Indication Signal, Unavailable Time ......................... 130
Table 83 Loss of TU3 Pointer...................................................................... 131
Table 84 Remote Defect Indication (VC3 Higher-Order Path Virtual Container) .. 132
Table 85 B3 UAS Performance Over-Threshold (VC3 Higher-Order Path Virtual
Container) ....................................................................................... 133
Table 86 B3 FEUAS Performance Over-Threshold (VC3 Higher-Order Path Virtual
Container) ....................................................................................... 134
Table 87 VC3 Higher-Order Path Signal Degraded ......................................... 135
Table 88 B3 SES Performance Over-Threshold (VC3 Higher-Order Path Virtual
Container) ....................................................................................... 136

Tables
Table 89 B3 FESES Performance Over-Threshold (VC3 Higher-Order Path Virtual

Container) ....................................................................................... 137
Table 90 B3 ES Performance Over-Threshold (VC3 Higher-Order Path Virtual
Container) ....................................................................................... 138
Table 91 B3 FEES Performance Over-Threshold (VC3 Higher-Order Path Virtual
Container) ....................................................................................... 139
Table 92 B3 BBE Performance Over-Threshold (VC3 Higher-Order Path Virtual
Container) ....................................................................................... 140
Table 93 B3 FEBBE Performance Over-Threshold (VC3 Higher-Order Path Virtual
Container) ....................................................................................... 141
Table 94 VC3 Higher-Order Path Unequipped ............................................... 142
Table 95 VC3 Higher-Order Path Trace Identifier Mismatch............................. 143
Table 96 VC3 Signal Label Mismatch ........................................................... 144
Table 97 TU3 PJE+/PJE- Performance Over-Threshold ................................... 145
Table 98 VC3 Protection Switching Event ..................................................... 146
Table 99 TU12 Path Alarm Indication Signal, Unavailable Time........................ 147
Table 100 Loss of TU12 Pointer .................................................................. 148
Table 101 Remote Defect Indication (VC12 Lower-Order Path Virtual Container)149
Table 102 TU11 Path Alarm Indication Signal, Unavailable Time...................... 150
Table 103 Loss of TU11 Pointer .................................................................. 151
Table 104 Remote Defect Indication (VC11 Lower-Order Path Virtual Container)152
Table 105 V5 UAS Performance Over-Threshold............................................ 153
Table 106 V5 FEUAS Performance Over-Threshold ........................................ 154
Table 107 V5 SES Performance Over-Threshold ............................................ 155
Table 108 V5 FESES Performance Over-Threshold......................................... 156
Table 109 V5 ES Performance Over-Threshold .............................................. 157
Table 110 V5 FEES Performance Over-Threshold........................................... 158
Table 111 V5 BBE Performance Over-Threshold ............................................ 159
Table 112 V5 FEBBE Performance Over-Threshold......................................... 160
Table 113 TU12 PJE+/PJE- Performance Over-Threshold ................................ 161
Table 114 TU12 Protection Switching Event.................................................. 162
Table 115 Loss of Timing Input .................................................................. 163
Table 116 Loss of Timing Output ................................................................ 164
Table 117 Power Supply Fault ....................................................................165
Table 118 Board Out of Position ................................................................. 165
Table 119 Board Type Mismatch ................................................................. 166
Table 120 Ethernet Physical Electrical Interface – Ethernet Port Disconnected ... 166
Table 121 Loss of Received Signal at the Ethernet Physical Optical Interface..... 167
Table 122 Orderwire Protection Bytes of the ZTE SDH Equipment.................... 193
Table 123 Definitions of NE IP Address and Subnet Mask (FLSM)..................... 210
Table 124 Definitions of Area ID, NE ID, and Board Number (FLSM) ................ 210
Table 125 Meanings of Bytes in the NE IP Address ........................................ 211
Table 126 NE IP Address Allocation (FLSM) .................................................. 211
Table 127 Definitions of NE IP Address and Subnet Mask (VLSM) .................... 211
Table 128 Definitions of Area ID, ECC Subnet ID, and NE ID (VLSM)................ 212
Table 129 Area Definitions and NE IP Address Configurations ......................... 214
Table 130 NE IP Address Configurations of the NEs Allocated into Area 193 ...... 215
Table 131 Definition of EMS Host Address ....................................................215
Table 132 Route Configuration Commands in Windows2000 ........................... 217
Table 133 Route Configuration Commands Lines in Unix ................................ 217
Table 134 Route Configuration Commands in Configuration File (HP-UX) .......... 218
Table 135 Route Configuration Commands in Configuration Files (Solaris) ........ 219
Table 136 Input Principles of NE Related Parameters ..................................... 228
Table 137 Parameters of the Command d-uprade ......................................... 230
Table 138 Parameters of the Command d-get-status ..................................... 231
Table 139 Descriptions of Parameters that Need to be Verified for Local Upgraded
Board Program Version ...................................................................... 232
Table 140 Parameters in the Standby Area that Need to be Verified................. 241
Table 141 Parameters of the Command d-try ............................................... 241
Table 142 Parameters in the Original Standby Area that Need to be Verified after
the Try Run ..................................................................................... 243

Table 143 Parameters of the Command d-active ...........................................244

Table 144 Descriptions of Parameters that Need to be Verified after Activation.. 245
Table 145 Half-day Maintenance Form......................................................... 250
Table 146 Daily Maintenance Record ........................................................... 252
Table 147 Weekly Maintenance Record ........................................................ 254
Table 148 Login Password Change Record ...................................................255

Sjzl20060681-Unitrans ZXMP S385 (V2 (1) .00&V2.10) Maintenance Manual

Uploaded by

Copyright:

Available Formats

You might also like

Sjzl20060681-Unitrans ZXMP S385 (V2 (1) .00&V2.10) Maintenance Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sjzl20060681-Unitrans ZXMP S385 (V2 (1) .00&V2.10) Maintenance Manual

Uploaded by

Copyright:

Available Formats

ZXMP S385

SDH Based Multi-Service Node Equipment

Version 2.00 & Version 2.10

Copyright © 2005 ZTE CORPORATION.

Date Revision No. Serial No. Description

Thank you for your cooperation!

Document ZXMP S385 (V2.00&V2.10) SDH Based Multi-Service Node Equipment

About this Maintenance Manual .............................................................xiii

Requirements of Tools and Instruments.................................................................. 22

Equipment Room Maintenance Rules...................................................................... 23

Basic Maintenance Operations ............................................................................... 25

Equipment Maintenance Operations ....................................................................... 43

Routine EMS Maintenance Operations..................................................................... 52

Physical Interface Performance Events and Solutions ............................................... 63

Regenerator Section Performance Events and Solutions........................................... 65

Multiplex Section Performance Events and Solutions ................................................ 66

Higher-Order Path Performance Event and Solutions ............................................... 68

Lower-Order Path Performance Event and Solutions ................................................ 69

Alarm Messages and Solutions............................................................................... 78

Chapter 6................................................................................. 169

Basic Considerations for Fault Locating ................................................................. 171

Common Methods of Fault Locating...................................................................... 173

Typical Troubleshooting....................................................................................... 176

Chapter 7................................................................................. 197

B2 Bit Error due to High Temperature................................................................... 199

B2 Bit Error due to Optical Board Fault.................................................................. 200

155 M Electrical Interfaces Interworking Failure due to Improper Transmission Distance

Switching Failure/Service Block due to CS Board Malfunction.................................. 205

LOF or LOS of Optical Board due to Clock Fault...................................................... 207

MS Switching Abnormality due to Invalid MS Protection Relation............................. 207

Appendix A .............................................................................. 209

Example of Network Address Coding of NEs .......................................................... 213

Appendix B .............................................................................. 221

Local Upgrade Instructions .................................................................................. 224

Remote Upgrade Instructions .............................................................................. 235

Appendix C .............................................................................. 249

Appendix D ............................................................................. 257

Flowchart of Board Replacement .......................................................................... 260

Board Replacement Procedure ............................................................................. 262

Appendix F............................................................................... 271

ALL-11 Chip Burner ............................................................................................ 274

YGBERT-2M 2 M BER Tester ................................................................................ 277

SDH Analyzer..................................................................................................... 280

Appendix G.............................................................................. 281

Appendix H ............................................................................. 285

Tables ......................................................................................... 293

About the Manual Suit

The whole manual suite of ZXMP S385 is listed as follows:

Unitrans ZXMP S385 (V2.00&V2.10) SDH Based Multi-Service Node

Unitrans ZXMP S385 (V2.00&V2.10) SDH Based Multi-Service Node

Unitrans ZXMP S385 (V2.00&V2.10) SDH based Multi-service Node

Unitrans ZXMP S385 (V2.00&V2.10) SDH based Multi-service Node

Confidential and Proprietary Information of ZTE CORPORATION xiii

Purpose of this Manual

Chapter 1 Safety Instructions, gives the safety precautions for equipment

Chapter 2 Maintenance Overview, gives the basic knowledge of equipment

Chapter 3 Routine Maintenance, describes the routine maintenance issues,

Chapter 4 Performance Message and Handling, summarizes the ZXMP