Sjzl20051606-ZXWM M900 (V2[1].0) Maintenance Manual

ZXWM M900Dense Wavelength Division Multiplexing

Optical Transmission System Maintenance Manual

Version 2.0

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: [email protected]

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/04/29 R1.0 sjzl20051606 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 Name

ZXWM M900 (V2.0) Dense Wavelength Division Multiplexing Optical Transmission System Maintenance Manual

Product Version V2.0 Document Revision

Number R1.0

Equipment Installation Date

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)


Your evaluation of this documentation

Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Your suggestions for improvement of this documentation

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 Add more examples

Add more/better quick reference aids Add more detail Improve the index

Other suggestions

___________________________________________________________________________

___________________________________________________________________________

___________________________________________________________________________

___________________________________________________________________________

___________________________________________________________________________

# 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 ...............................................................xi About the Manual Suite.......................................................................................... xi Purpose of this Maintenance Manual........................................................................xii Typographical Conventions....................................................................................xiii Mouse Operation Conventions................................................................................xiii Safety Signs.........................................................................................................xiv How to Get in Touch ............................................................................................. xv

Customer Support................................................................................................................. xv Documentation Support......................................................................................................... xv

Chapter 1...................................................................................17

Safety Instructions.................................................................................. 17

Chapter 2...................................................................................19

Maintenance Overview............................................................................ 19 Maintenance Classification .....................................................................................19 Requirements of Tools and Instruments..................................................................20

Maintenance Tools and Materials............................................................................................20 Instruments and Meters ........................................................................................................21

Equipment Room Maintenance Rules......................................................................22 Basic Requirements for Maintenance Personnel.......................................................................22 Work Rules ...........................................................................................................................23 Shift Rules ............................................................................................................................23

Basic Maintenance Operations ...............................................................................24 Unplugging/Plugging a Fiber Pigtail.........................................................................................24 Plugging/Unplugging an Optical Attenuator.............................................................................27 Optical Power Test.................................................................................................................28 Loopback ..............................................................................................................................29 Bit Error Test.........................................................................................................................36 Making Network Cable...........................................................................................................37 Alarm Output Cable Connection .............................................................................................40

Board Reset ..........................................................................................................................42 Automatic Power Control Management...................................................................................43 Setting Registers and Important Data of Boards .....................................................................45 Communication Test..............................................................................................................45 FEC Configuration..................................................................................................................46 Protection Management.........................................................................................................48 Optical Spectrum Management ..............................................................................................49 OMS Power Management.......................................................................................................50 Wavelength Adjustment ........................................................................................................51 Integrated Wavelength Supervision Subsystem......................................................................51 Receiver Adaptive Control......................................................................................................52 Fan Rotate Speed Adjustment................................................................................................52

Maintenance Precautions.......................................................................................53 Board Maintenance Precautions..............................................................................................53 Optical Interface and Fiber Pigtail Maintenance Precautions .....................................................54 DRA Board Maintenance Precautions......................................................................................54 Equipment Maintenance Precautions ......................................................................................54 EMS Maintenance Precautions................................................................................................55

Chapter 3...................................................................................57

Routine Maintenance .............................................................................. 57 Routine Maintenance Items ...................................................................................57 Environment Maintenance .....................................................................................58

Equipment Room Temperature & Humidity.............................................................................58 Dustproof Requirement .........................................................................................................58

Equipment Maintenance Operations .......................................................................61 Power Supply Check..............................................................................................................61 Cabinet Indicator Lights Observation......................................................................................62 Fan Check and Dustproof Unit Cleansing ................................................................................73 User Management.................................................................................................................76 Connection with the EMS.......................................................................................................77 Topology Map Monitoring.......................................................................................................78 Alarm Monitoring...................................................................................................................78

Chapter 4...................................................................................83

Performance Message and Handling...................................................... 83

Definition of Performance ......................................................................................83 Analog Performance ..............................................................................................................84

Performance Message Classification........................................................................85 Classification by Performance Detection Point .........................................................................85

Classification by Performance Type.........................................................................................87 Analysis of Common Performance..........................................................................92

Chapter 5.................................................................................111

Alarm Message and Handling ............................................................... 111

Overview of Alarm Message................................................................................. 111 Alarm Message Classification................................................................................................111 Alarm Levels and Severities .................................................................................................117

Common Alarm Messages and Solutions............................................................... 118

Chapter 6.................................................................................155

Troubleshooting .................................................................................... 155

Basic Principles of Troubleshooting ....................................................................... 155 Observing ...........................................................................................................................155 Querying.............................................................................................................................155 Thinking..............................................................................................................................155 Taking Action ......................................................................................................................156

Troubleshooting Procedures................................................................................. 156 Common Methods of Fault Location...................................................................... 159

Observation & Analysis Method............................................................................................159 Unplugging/Plugging Method ...............................................................................................160 Replacement Method...........................................................................................................160 Bit Error Problem.................................................................................................................163 Optical Power Problem.........................................................................................................165 Protection Switching Fault....................................................................................................172

Typical Troubleshooting....................................................................................... 176 Bit Error Problem of Main Optical Channel.............................................................................177

Appendix A..............................................................................181

NE Address Definition and Route Configuration .................................. 181

Definition of the NE IP Address ............................................................................ 181 Definition and Configuration Principle....................................................................................181 Configuration Example of the NE IP Address.........................................................................183

ECC Optical Interface Address Configuration ......................................................... 185 2 M Supervision System ......................................................................................................185 100 M Supervision System ..................................................................................................192

Definition of the EMS Host Address and Route Configuration................................... 193 Address Definition and Route Configuration Principle.............................................................193 Route Configuration.............................................................................................................194

Common Route Configuration Commands............................................................................195

Appendix B..............................................................................199

Agent Configuration.............................................................................. 199 DIP Switch on NCP/NCPF Board ........................................................................... 199 Use of TELNET and FTP Commands...................................................................... 200 Local NCP/NCPF Reconfiguration .......................................................................... 201

Preparing Before the Reconfiguration....................................................................................202 Downloading the Agent/FPGA Programs (FTP)......................................................................202 Modifying the Address of NCP/NCPF Board............................................................................203 Burning the Agent/FPGA Programs (TELNET)........................................................................204 Running the Agent Program.................................................................................................205

Local Download of the Agent/FPGA Programs........................................................ 206 Remote Online Download of the Agent Program.................................................... 207

Preparing before the Remote Online Download .....................................................................208 Downloading the Agent Program Through Command Lines ...................................................208 Downloading the Agent Program through the ZXONM E300 ..................................................212 Running the Agent Program.................................................................................................212

Running Procedures of Blank NCP/NCPF Board...................................................... 213

Appendix C..............................................................................215

Common Maintenance Forms ............................................................... 215

Half-day Maintenance Record .............................................................................. 215 Daily Maintenance Record ................................................................................... 217 Weekly Maintenance Record................................................................................ 219 Login Password Change Record............................................................................ 220

Appendix D .............................................................................221

Board Replacement............................................................................... 221 Board Plugging/Unplugging ................................................................................. 221

Plugging a Board.................................................................................................................221 Unplugging a Board.............................................................................................................222 Precautions in Board Operation ............................................................................................222

General Flow of Board Replacement ..................................................................... 223

Appendix E...............................................................................227

Common Instruments and Meters........................................................ 227 PMS-1A Optic Power Meter.................................................................................. 227

Brief Function Description ....................................................................................................227 Panel Description.................................................................................................................228 Operation Flow....................................................................................................................229 Precautions.........................................................................................................................229

ALL-11 Chip Burner ............................................................................................ 230 Function..............................................................................................................................230 Panel Description.................................................................................................................231 Operation Flow....................................................................................................................232 Precautions.........................................................................................................................233

SDH Tester ........................................................................................................ 233 Function..............................................................................................................................233 Panel Description.................................................................................................................234 Operation Flow....................................................................................................................236 Precautions.........................................................................................................................237

Other Instruments and Meters............................................................................. 238 Optical Spectrum Analyzer...................................................................................................238 Multi-Wavelength Meter.......................................................................................................238 Variable Optical Attenuator ..................................................................................................239 Optical Return Loss Tester ...................................................................................................239

Appendix F...............................................................................241

Alarm Quick Lookup Table.................................................................... 241

Abbreviations .............................................................................243

Figures........................................................................................247

Tables .........................................................................................249


Confidential and Proprietary Information of ZTE CORPORATION xi

About this Maintenance Manual

About the Manual Suite The Unitrans ZXWM M900 Dense Wavelength Division Multiplexing Optical Transmission System (ZXWM M900 for short) is a kind of DWDM equipment developed by ZTE CORPORATION. Its operating wavelength is located at the C and L bands near the 1550 nm window, with the maximum transmission capacity of 1600 Gbit/s.

The ZXWM M900 supports access of multiple services, featuring powerful protection and network management function. Applicable to backbone networks, local switching networks and various private networks, it can meet networking requirements and network management requirements at different levels.

There are four manuals associated with the ZXWM M900 equipment:

Unitrans ZXWM M900 (V2.0) Dense Wavelength Division Multiplexing Optical Transmission System Technical Manual

Unitrans ZXWM M900 (V2.0) Dense Wavelength Division Multiplexing Optical Transmission System Hardware Manual

Unitrans ZXWM M900 (V2.0) Dense Wavelength Division Multiplexing Optical Transmission System Installation Manual

Unitrans ZXWM M900 (V2.0) Dense Wavelength Division Multiplexing Optical Transmission System Maintenance Manual

ZXWM M900 (V2.0) Maintenance Manual

xii Confidential and Proprietary Information of ZTE CORPORATION

Purpose of this Maintenance Manual This manual describes the main contents and common operations of routine maintenance, focusing on the possible causes of common alarms and typical faults and corresponding processing methods. It also summarizes some typical cases for your reference during the maintenance of the equipment.

Chapter 1 Safety Instructions describes the safety precautions that you must know before equipment maintenance.

Chapter 2 Maintenance Overview outlines the basic knowledge of equipment maintenance, which covers maintenance classification, tools, instruments, and meters used for maintenance. The basic operations and precautions for equipment maintenance are also included.

Chapter 3 Routine Maintenance describes the routine maintenance items, maintenance periods, and methods.

Chapter 4 Performance Message and Handling offers a summary of the ZXWM M900 performance, and introduces the definition of common important performance events, and their influence on the equipment.

Chapter 5 Alarm Message and Handling specifies the types, severity levels of alarm information. It summarizes the alarm information, and describes the causes and procedures for handling common alarms.

Chapter 6 Troubleshooting presents the troubleshooting process for emergent faults. It also describes the possible causes and handling methods of typical faults in ZXWM M900.

Appendix A NE Address Definition and Route Configuration introduces the definition of NE address and the route configuration of the EMS host during the networking.

Appendix B Agent Configuration describes the initialization and operation of the NCP board in the ZXWM M900.

Appendix C Common Maintenance Forms provides record forms commonly used in the maintenance for your reference.

Appendix D Board Replacement describes the replacement of boards in the ZXWM M900, including the preparation, procedure and precautions.

Appendix E Common Instruments and Meters introduces some instruments and meters commonly used in the maintenance.

Appendix F Alarm Quick Lookup Table summarizes all common alarms in the ZXWM M900 for quick lookup.


Confidential and Proprietary Information of ZTE CORPORATION xiii

Typographical Conventions ZTE documents employ the following typographical conventions.

T AB L E 1 TY P O G R AP H I C AL C O N V E N T I O N S

Typeface Meaning

Italics References to other guides and documents.

“Quotes” Links on screens.

Bold Menus, menu options, input fields, radio button names, check boxes, drop-down lists, dialog box names, window names

CAPS Keys on the keyboard 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 T AB L E 2 M O U S E OP E R AT I O N C O N V E N T I O N S

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.


xiv Confidential and Proprietary Information of ZTE CORPORATION

Safety Signs T AB L E 3 S AF E T Y S I G N S

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.


Confidential and Proprietary Information of ZTE CORPORATION xv

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 [email protected]. 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 [email protected]; 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.


xvi Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION 17

C h a p t e r 1

Safety Instructions

This equipment involves large amount of laser devices, so it should be installed, operated, and maintained by the qualified professionals.

Please observe the local safety specifications and relevant operating procedures in equipment installation, operation and maintenance; otherwise personal injury or equipment damage may be caused. The safety precautions introduced in this manual are only supplementary to the local safety specifications.

ZTE shall not bear any liabilities incurred by violation of the universal safety operation requirements, or violation of the safety standards for designing, manufacturing, and using the equipment.


18 Confidential and Proprietary Information of ZTE CORPORATION



C h a p t e r 2

Maintenance Overview

In this chapter, you will learn about: Maintenance classification

Tools and instruments required for the maintenance

Maintenance regulations in equipment room

Basic maintenance operations and precautions

Maintenance Classification The equipment maintenance is classified 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.



Requirements of Tools and Instruments Maintenance Tools and Materials Table 4 lists the standing maintenance tools in an equipment room.

T AB L E 4 M AI N T E N AN C E TO O L S R E Q U I R E D I N AN E Q U I P M E N T R O O M

Tool Tool

Tape Crimping pliers

Screw drivers (flat-head and Phillips, one piece for each type respectively in large, medium and small sizes)

Electric iron (40W)

Tweezers Clamping pincers

Diagonal pliers Antistatic wrist strap

Sharp-nose pliers Insulation tape

Cable peeler Cable tie

Scissors Pliers

Crossover or straight network cable (the cable length depends on the actual needs) Fiber extractor

Pigtails (SC/PC-FC/PC, SC/PC-SC/PC) Attenuator (SC/PC, FC/PC)

Ring flange (SC/PC, FC/PC) IC extractor

Besides the common tools listed above, the following materials need to be prepared for equipment maintenance: anhydrous alcohol, dust-free paper, solder tin, rosin, cable ties, self-loop fiber, etc.

For equipment upgrade, the maintenance personnel should also carry a certain number of BOOTROOM chips of the NCP board, and corresponding program chips of other boards.

Chapter 2 - Maintenance Overview


Instruments and Meters Table 5 lists the common instruments and meters required for the equipment maintenance.

T AB L E 5 I N S T R U M E N T S AN D M E T E R S R E Q U I R E D F O R E Q U I P M E N T M AI N T E N AN C E

Instrument/Meter Description

Thermometer/Hygrometer Both of the must be arranged in an equipment room to monitor the operating environment of equipment.

Digital multimeter It is used to measure the voltage of equipment’s power supply during the commissioning.

Optical power meter It is used to measure the power of input/output light.

Bit error tester It used to test bit errors during the system debugging.

SDH synthetic analyzer

It acts as a light source to provide single-wavelength light for ZXWM M900 equipment during the equipment debugging and system debugging. It can also be used as an optical power meter and bit error tester.

Optical spectrum analyzer It is mainly used to measure the optical signal-to-noise ratio of ZXWM M900 equipment while maintaining equipment or debugging the system.

Multi-wavelength meter This meter is needed during the single point test to test the optical wavelengths. It can also be used to measure optical power.

Optical attenuator

An optical attenuator can be added between a pigtail fiber and an optical interface to adjust the optical power and make it meeting the requirement of the optical interface. There are two kinds of optical attenuators, fixed attenuator and variable attenuator. The fixed attenuator’s attenuation amount is fixed; while the attenuation amount of a variable attenuator can be adjusted in a range.

Portable PC

A portable PC with Modem card and network card is needed when the site should be accessed to the EMS during the maintenance. In this case, straight network cables or crossover network cables are needed.

Chip burner The chip burner may be needed while upgrading equipment, which is used to burn the new version program into a chip.

Note: As the optical communication meters and computers are expensive, the instruments and meters listed in the above table can be equipped only at one or several major sites according to the network scale, which can be shared by other sites.

Checkpoint: 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.

Basic Requirements for Maintenance Personnel 1. Maintenance personnel should perform routine maintenance carefully

to ensure that all equipment in the equipment room run in a normal working environment.

2. Maintenance personnel should be familiar with the conditions of the area in charge, understanding the running status of equipment, completing and maintaining the engineering documents.

3. Handle the faults following the troubleshooting process specified in this manual strictly.

4. Maintenance personnel should be calm and composed in troubleshooting, to prevent further problems.

5. While handling a fault, pay attention to the following items:

Before handling the fault, the maintenance person should inform the network management center to collect, save, and back up onsite data. Because it is unavoidable that some data of the current alarm and performance will be influenced during the troubleshooting, the data of the current alarm and performance details should be saved for searching the causes of the fault.

The maintenance person is not allowed to reset the network element control board (NCP/NCPF) of equipment when a fault occurs. He/she should contact with the NM center in time to check and confirm the alarm information, and then handle the fault with the guidance of the NM center.

Record the detail of each operation step during the fault handling process, which is very helpful for the handling of similar faults in the future as the reference.

6. Maintenance personnel are required to be skilled in the basic operations of transmission equipment and the use of test instruments and meters.

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



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 Rules The shift rules are very important for uninterrupted communications and should be strictly followed by each maintenance person.

1. The persons on duty should perform shift handover seriously. The responsibilities and formalities should be clearly defined to ensure smooth shift.

2. The person on the previous shift should, before going off duty, provide clear information about his/her shift to the person on the next shift; the person on the next shift should conduct careful checks before taking over the duty.

3. Check and make sure during the shift that: the equipment running status, the state of the tools and instruments are clear; various drawings and records are complete.

4. The person on the previous shift should stay on duty until the person on the next shift arrives and can only leave after the shift is completed.

5. After proper shift, 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.

6. If fault occurs during shift, the persons of both shifts should be responsible for the troubleshooting.



Basic Maintenance Operations The maintenance person can locate and clear faults in the system through proper maintenance operations.

For the ZXWM M900 equipment is managed by the network element management system (EMS) ZXONM E300 developed by ZTE CORPORATION, the ZXWM M900 maintenance operations can be classified into equipment maintenance and 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 manuals of the ZXONM E300 for the detailed EMS maintenance operations.

Checkpoint: Once the test and diagnosis finishes, the maintenance operations conducted should be canceled in time, so that the equipment operation will not be affected.

Unplugging/Plugging a 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 6.

T AB L E 6 F I B E R C O N N E C T O R TY P E S

Type Description Picture

FC/PC Round fiber connector/polished slightly convex sphere

FC/APC Round fiber connector/polished convex sphere at 8º

SC/PC Square fiber connector/polished slightly convex sphere



Type Description Picture

SC/APC Square fiber connector/polished convex sphere at 8º

ST/PC Round bayonet fiber connector /polished slightly convex sphere

ST/APC Round bayonet fiber connector/ polished convex sphere at 8º

MT-RJ Bayonet square fiber connector

LC/PC Bayonet square fiber connector / polished slightly convex sphere

Note: SC/PC and LC/PC plugs are mainly used for connectors of fiber pigtails connected to the ZXWM M900 boards.

To plug a fiber pigtail with LC/PC connectors:

1. Hold the pigtail plug with your thumb and index finger, align the spring piece on the connector with concave trough of optical interface flange, and push the pigtail inward by applying moderate force.

Be careful and avoid damaging the ceramic inner pipe of the optical adaptor or the connector’s end surface.

2. Clamp it tightly once the pigtail connector is completely plugged in.

To plug a fiber pigtail with SC/PC connector

1. Hold the pigtail plug with your thumb and index finger, and align the protruding face of connector with concave trough of optical interface flange and push the pigtail inward by applying moderate force.

Be careful and avoid damaging the ceramic inner pipe of optical adaptor or the connector end surface.

2. After the pigtail connector is completely plugged in, clamp it tightly.



Figure 1 illustrates an example of inserting a fiber pigtail with SC/PC connectors to an optical interface of a board.

F I G U R E 1 IN S E R T I N G A F I B E R P I G T AI L W I T H SC/PC C O N N E C T O R S

To unplug a fiber pigtail with LC/PC connectors:

1. Hold the pigtail connector by your thumb and index finger or clamp the connector with an extractor, and then press down the spring piece on the connector.

2. Pull out the connector with moderate force along the connector’s direction.

To unplug a fiber pigtail with SC/PC connectors:

1. Clamp the plastic end face connector with an extractor.

2. Pull out the connector with moderate force along the connector’s direction.

Caution: The connector of a fiber pigtail should immediately be protected with a dust-proof cap to prevent end surface from damage after the fiber pigtail is unplugged from a board.

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.

Do not clean a fiber pigtail while there is light (especially strong light) in it; or else, the fiber connector will be damaged.



Plugging/Unplugging an Optical Attenuator Optical attenuators of high return loss with SC or LC connectors are used for the ZXWM M900 equipment.

Checkpoint:

Unplug the fiber pigtails first before unplugging the attenuator.

Install an optical attenuator before plugging fiber pigtails.

To unplug an optical attenuator with SC connectors:

1. Clip the plastic end surface of the attenuator with an extractor.

2. Pull it out with moderate force.

To unplug an optical attenuator with LC connectors:

1. Clip the connector of the attenuator with an extractor and press down the spring piece.

2. Pull it out with moderate force.

Caution: After the attenuator is unplugged, both ends of it should be protected with a dust-proof cap to prevent it from damage.

To install an optical attenuator with SC connectors:

1. Make the convex part of the connector aligned with the concave of the optical interface flange, and then push it in with a moderate force.

Be careful and avoid damaging the ceramic inner pipe of optical adaptor or the connector’s end surface.

2. Push the optical attenuator until it clicks to be in place.

To install an optical attenuator with LC connectors:

1. Hold the pigtail connector by your thumb and index finger, make the convex part of the connector aligned with the concave of the optical interface flange, and then push it in with a moderate force.

Be careful and avoid damaging the ceramic inner pipe of optical adaptor or the connector’s end surface.

2. Push the optical attenuator until it clicks to be in place.



Optical Power Test Before testing optical power, pay attention to the following precautions:

Measure the attenuation amount of the fiber pigtail and 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 amount 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.

Checkpoint:

Check and make sure that the pigtail connector is clean, and the connecting devices of the ring flange on the optical board panel and the optical power meter are well coupled.

Shut off the laser before plugging/unplugging fibers to or from the DRA or the HOBA board.

To test the optical launched power of an optical interface:

1. Set the received optical wavelength of optical power meter as closer to the transmitted optical wavelength of the tested optical board as possible.

2. Connect one end of the fiber pigtail to the optical transmit port (T) of the optical board and the other end to the input port of the optical power meter, as illustrated in Figure 2.

F I G U R E 2 TE S T I N G T H E OP T I C AL L AU N C H E D P O W E R

R

T

Optical power meterOptical interface

Fiber pigtail



3. Then read the stable optical power value displayed on the optical power meter, which is the optical launched power of the optical interface.

To test the optical received power of an optical interface:

1. Set the received optical wavelength of optical power meter as closer to the optical wavelength to be tested as possible.

2. Unplug the fiber pigtail connected to the optical receive port (R) on the board to be tested, and connect it to the input interface of the optical power meter.

3. Read the stable optical power value displayed on the optical power meter, which is the optical received power of the optical interface.

Loopback Loopback is a usual measure for detecting the fault of optical transmission channel. It can be used to locate the faulty point of a WDM 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 and also facilitates the equipment commissioning and debugging. The loopback is classified into hardware loopback and software loopback.

Hardware Loopback The purpose of hardware loopback is to loop the signal of the interface by connecting the optical receive interface and the optical transmit interface with a fiber pigtail. In terms of the signal flow direction, the hardware loopback orients towards the equipment side, so it is also called hardware self-loop.

According to the interface type and the loop direction, the line-side/aggregate-side/client-side/tributary-side near-end/far-end loopback can be implemented.

For example, connect the IN1 optical interface to the OUT2 optical interface on a single-channel bidirectional OTU board with a fiber pigtail to implement the far-end loopback at the client side.

Caution: If a fiber pigtail is used for the hardware self-loop, an optical attenuator must be added before the optical receive port in order to control the input power. The input power should be between the overload point and sensitivity of the optical interface in order to prevent optical power overload from damaging the optical port.



Software Loopback The software loopback of ZXWM M900 equipment is implemented in the network element management system ZXONM E300.

The OTU boards and the convergence boards (SRM41/SRM42/GEMF) support the software loopback.

1. Software loopback of OTU boards

The software loopback modes applicable to OTU boars are listed in

T AB L E 7 S O F T W A R E LO O P B A C K M O D E S F O R OTU B O AR D S

Loopback Mode Description Applicable Board

Client-side near-end loopback

In this mode, a signal is input to a client-side interface (OAC source) and then output from the client-side interface (OAC sink) to implement the loopback at the client side.

Line-side far-end loopback

In this mode, a signal is input to a line-side interface (OCH source) and then output from the line-side interface (OCH sink) to implement the loopback at the line side.

Single-channel bidirectional OTU/OTU10G/OTUF board, OTUP board

Client-side far-end loopback

In this mode, a signal is input to a line-side interface (OCH source), and then looped to a client-side input port inside the board after being decoded (FEC). Then it is output from the line-side interface (OCH sink) after being coded.

Line-side near-end loopback

In this mode, a signal is input to a client-side interface (OAC source), and then looped to a line-side input port inside the board after being coded (FEC). Then it is output from the client-side interface (OAC sink) after being decoded.

Single-channel bidirectional OTU10G/OTUF board

Note:

In the ZXONM E300, the code of the OTU board in ZXWM M900 is “OTUD”. The code of OTU boards with continuous-rate optical modules is “OTUC”.



Single-channel bidirectional OTU board

It supports the client-side near-end loopback and line-side far-end loopback. The flow direction of the looped signal is illustrated in Figure 3.

F I G U R E 3 LO O P B AC K O F A S I N G L E -C H AN N E L B I D I R E C T I O N AL OTU B O AR D

OTU



IN1

IN2OUT2

OUT1

Dual-channel regenerator OTU board

It supports the line-side far-end loopback. The flow direction of the looped signal is illustrated in Figure 4.

F I G U R E 4 LO O P B AC K O F A D U AL -C H AN N E L R E G E N E R AT O R OTU B O AR D

Regenerator OTU



IN1

IN2OUT2

OUT1Line 1

Line 2

Original signal flow direction

Loopback signal flow direction

OTUP board

The OTUP board implements the wavelength conversion and service protection with the operating principle of “concurrent transmitting and preferred receiving”. It supports the client-side near-end loopback and the line-side far-end loopback, of which the line-side far-end loopback is applicable to both the working path and the protection path.

The flow direction of the looped signal is illustrated in Figure 5.



F I G U R E 5 LO O P B AC K O F AN OTUP BO AR D



C INL IN

L INP

C OUT

L OUTP

L OUT

Working path

Protection path

Concurrent Transmitting

Preferred Receiving



OTUP

Single-channel bidirectional OTUF/OTU10G board

The OTUF/OTU10G board has an FEC coding unit and an FEC decoding unit. Both of them support all of the four loopback modes: client-side/line-side near-end/far-end loopback.

The client-side near-end loopback and the line-side far-end loopback modes are commonly used while the other two modes are usually used to check whether the FEC coding/decoding unit is working normally

The flow direction of the looped signal is illustrated in Figure 6.

F I G U R E 6 LO O P B AC K O F S I N G L E -C H AN N E L B I D I R E C T I O N AL OTUF/OTU10G BO AR D

FEC decoding

Client Side Line Side

IN1

OUT2

FEC codingOUT1

IN2


Client-side far-end loopback







Dual-channel regenerator OTUF board

It supports the line-side far-end loopback and the line-side near-end loopback. The line-side far-end loopback mode is commonly used while the line-side near-end loopback mode is usually used to check whether the FEC coding/decoding unit is working normally. The flow direction of the looped signal is illustrated in Figure 7.

F I G U R E 7 LO O P B AC K O F D U AL -C H AN N E L R E G E N E R AT O R OTUF BO A R D

FEC decoding

Line Side Line Side

IN1

OUT2

FEC codingOUT1

IN2



Figure 8 illustrates a loopback application example of OTU10G board. The IN1 interface and the OUT2 interface of the OTU10G (1) board are connected to the bit error tester.

F I G U R E 8 AP P L I C AT I O N E X A M P L E O F OTU B O AR D LO O P B AC K

OTU10G(1)Bit error

tester

IN1

OUT2

Client-side near-end loopback Line-side far-end loopback

NE A NE B

OUT1

IN2

OMU

ODU

OBA

OPA

OPA

OBA

ODU

OMU

IN2

OUT1

OTU10G(2)

OUT2

IN1

If the IN1 and OTU2 interfaces of the OTU10G (1) board are looped (client-side near-end loopback), the bit error tester can test the bit error performance of the OTU10G (1) board.

If the IN2 and OUT1 interfaces of the OTU10G (2) board are looped (line-side far-end loopback), the bit error tester can test the bit error performance of the wavelength channel between NE A and NE B.



2. Software loopback of convergence boards

The SRM41/SRM42/GEMF boards support the tributary near-end/far-end loopback and the aggregate near-end/far-end loopback as described in Table 8.

T AB L E 8 S O F T W A R E LO O P B A C K M O D E S F O R SRM41/SRM42/GEMF BO AR D S

Loopback Mode Description Remark

Tributary near-end loopback

In this mode, a signal is input to a tributary interface and then output from the tributary interface to implement the tributary loopback.

This kind of loopback can be configured based on tributary. Those tributaries un-looped can continue working normally.

Aggregate near-end loopback

In this mode, a signal is input to an aggregate interface and then output from the aggregate interface to implement the aggregate loopback.

-

Tributary far-end loopback

In this mode, a signal is input to an aggregate interface and then divided into n tributary signals. One or multiple tributary signals are looped to the tributary input port(s) and then combined into an aggregate signal, which is output from the aggregate interface to implement the aggregate loopback.

This kind of loopback can be configured based on tributary. And the traffic of one or several tributary traffic can be set to pass through the board in the loopback.

Aggregate far-end loopback

In this mode, a signal is input to a tributary interface and combined into an aggregate signal, which is looped to an aggregate input port in the board. Then the tributary signal is separated from the aggregate signal and then output from the tributary interface to implement the aggregate loopback.

-

Figure 9 illustrates the four loopback modes applicable to convergence boards, where the loopback modes are indicated as follows.

Loopback mode 1: Tributary near-end loopback

Loopback mode 2: Tributary far-end loopback

Loopback mode 3: Aggregate near-end loopback

Loopback mode 4: Aggregate far-end loopback



F I G U R E 9 LO O P B AC K O F A C O N V E R G E N C E B O AR D

Tributary Side Aggregate Side

ADD1

DROP1

Convergence Unit

OUT

IN



ADDn

DROPn

.

.

.

Loopback mode 1

Loopback mode 1

Loopback mode 2

Loopback mode 2

Loopback mode 3

Loopback mode 4

As illustrated in Figure 10, the loopback can be configured at different position of the communication link to test the bit error performance of nodes and transmission lines level by level.

F I G U R E 10 AP P L I C AT I O N E X AM P L E O F C O N V E R G E N C E BO AR D LO O P B A C K

Convergence Unit

Convergence Unit

Tributary near-end loopback

Bit error tester

Tributary far-end loopback

Aggregate near-end loopback

Aggregate far-end loopback

SRM41/SRM42/GEMF SRM41/SRM42/GEMF

...

...



Bit Error Test 1. Single-wavelength bit error test

Taking single-channel bidirectional OTU10G boards as example, Figure 11 illustrates the connection relationship between the bit error tester and the equipment under test in the single-wavelength test.

F I G U R E 11 C O N N E C T I O N R E L AT I O N S H I P I N S I N G L E -W AV E L E N G T H B I T E R R O R TE S T

OTU10G(1)Bit error

tester

IN1

OUT2

Fiber pigtail

NE A NE B

OUT1

IN2

OMU

ODU

OBA

OPA

OPA

OBA

ODU

OMU

IN2

OUT1

OTU10G(2)

OUT2

IN1

In the test, the interfaces (IN1/OUT2) at the client side of OTU10G (1) board in NE B are looped. The client-side interfaces of OTU10G (2) board in NE A are connected to the bit error tester with a fiber pigtail. The IN1 interface is connected to the transmit port of the tester while the OUT2 interface is connected to the receive port of the tester.

In normal status, there is no error displayed on the bit error tester.

2. Cascade bit error test

The purpose of cascade bit error test is to test all wavelengths in a WDM system. Taking a 3-channel system as example, Figure 12 illustrates the connection relationship between the bit error tester and the equipment under test.

F I G U R E 12 C O N N E C T I O N R E L A T I O N S I N CAS C AD E B I T ER R O R TE S T

OTU1T OTU1R

OTU1R OTU1T

OTU2T OTU2R

OTU2R OTU2T

OTU3T OTU3R

OTU3R OTU3T

Bit error tester

: Tunable optical attenuator

OBA OPA

OPA OBA

T

R1

2

2

3

3

OMU

OMU

ODU

ODU

1

λ

λ

λ

λ

λ

1

2

3

λ

λ

λ

1

2

3

λ

λ

λ

λ



As illustrated in Figure 12, the transmit port (T) of the bit error tester is connected to the OTU1T which transfers the first wavelength (λ1); while the receive port (R) of the tester is connected to the OTU3R which transfers the last wavelength (λ3). The other OTUT and OTUR at the bit error tester side are connected in a cross way.

On the other side, the OTUR and OTUT of the same wavelength are looped with fiber pigtails.

In normal status, there is no error displayed on the bit error tester.

Checkpoint:

In a bit error test, tunable optical attenuators should be added at the position of self-loop and between the bit error tester and equipment in order to protect the lasers.

Make sure the bit error tester is well grounded, and do not switch other electrical appliances on or off during the test.

Making Network Cable The appearance of a network cable is shown in Figure 13.

F I G U R E 13 AP P E AR AN C E O F A N E T W O R K C AB L E

RJ45 plug RJ45 plug

A

A view

1

8

There are two types of network cable depending on the connection relationship between pins: crossover network cable and straight network cable.

Crossover network cable

Table 9 lists the color codes and the connection relationship of the crossover network cable.



T AB L E 9 C O L O R C O D E AN D C O N N E C T I O N R E L AT I O N O F T H E C R O S S O V E R C AB L E

Pins of RJ45 Plug at Equipment End

Color Code of Category-5 Network Cable

Pins of RJ45 Plug at User End

1 White-orange 3

2 Orange 6

3 White-green 1

6 Green 2

4 Blue 4

5 White-blue 5

7 White-brown 7

8 Brown 8

Straight network cable

Table 10 lists the color codes and the connection relationship of the straight network cable.

T AB L E 10 C O L O R C O D E AN D C O N N E C T I O N R E L AT I O N O F T H E ST R AI G H T C AB L E

Pins of RJ45 Plug at Equipment End

Color Code of Category-5 Network Cable

Pins of RJ45 Plug at User End

1 White-orange 1

2 Orange 2

3 White-green 3

6 Green 6

4 Blue 4

5 White-blue 5

7 White-brown 7

8 Brown 8

A network cable can be used to connect the NM computer to a NE, or connect an Ethernet electrical interface of the OSCF board to other boards in a 100 M supervision system.

Connection between the NM computer and a NE

Select the appropriate network cable according to actual situation while using a network cable to establish the communication between the NM computer and NEs, as described in Table 11.



T AB L E 11 S E L E C T I O N AN D C O N N E C T I O N RE L AT I O N S H I P O F N E T W O R K C AB L E

Network Cable Type Equipment End User End Application

Scope


Network interface of a NM computer


J9 interface of OA subrack Network interface of a

HUB

2 M supervision system with NCP board


Network interface of a NM computer


NET interface of NCPF board Network interface of a

HUB

2 M supervision system with NCPF board

Network interface of a NM computer Crossover network

cable or straight network cable

Ethernet electrical interface of OSCF board Network interface of a

HUB

100 M supervision system

Note: In a 100 M supervision system, the network cable should be connected to the NET interface of the NCPF board at the equipment end if you want to reconfigure the NCPF board on site. For the details of NCPF reconfiguration, please refer to the Appendix B in this manual.

The selection of network cable is same as that in a 2 M supervision system.

Connection of Ethernet electrical interfaces on OSCF board in a 100 M supervision system

In a 100 M supervision system, the Ethernet electrical interface 1 ~ 6 of an OSCF board can be connected to any one of the system boards in the system, such as the NCPF, OHPF, APSF and slave OSCF board, besides a standby router and the NM computer.

The Ethernet electrical interfaces of the OSCF board have the automatic identification and crossing function. Therefore, both the crossover network cable and straight network cable can be used to connect the OSCF board to other boards or equipment.



Alarm Output Cable Connection The alarm output cable is an 16-core single-strand round cable used to output equipment alarm signals to the first cabinet of each row in the equipment room, as shown in Figure 14.

F I G U R E 14 AL AR M OU T P U T C AB L E

A view

Equipment end User end

A

8

1

15

9

A DB15 connector (female) is equipped at the equipment end of the cable, which is connected to the alarm output interface (ALM_OUT) of the ZXWM M900 PWSB board. The connector at the user end of the cable is connected to the first cabinet of each row in the equipment room, which is made on site.

The color code, connection relationship, and the signal definition of alarm output cable are listed in Table 12.

T AB L E 12 C O L O R C O D E , CO N N E C T I O N RE L AT I O N S H I P A N D S I G N AL D E F I N I T I O N

Signal Name Function Description Signal Attribute Pin No. Color Code

BUZZ_OUT+ Buzzer signal + On-off signal 1 White

BUZZ_OUT- Buzzer signal - On-off signal 9 Blue

S_ALARM+ Critical alarm signal + On-off signal 2 White

S_ALARM- Critical alarm signal - On-off signal 10 Orange

G_ALARM+ Major alarm signal + On-off signal 3 White

G_ALARM- Major alarm signal - On-off signal 11 Green

ALM_SET+ Alarm setting signal + On-off signal 4 White

ALM_SET- Alarm setting signal - On-off signal 12 Brown

BGND -48 V ground -48 V ground 6 Red

BGND -48 V ground -48 V ground 13 Blue

M_-48V -48 V output -48 V 8 Red

M_-48V -48 V output -48 V 15 Orange

The ALM_SET+/ALM_SET- are the alarm setting signals. The alarm output cable provides three pairs of on-off alarm signals: BUZZ_OUT, S_ALARM, and G_ALARM.



It depends on the connection of the alarm setting signals whether the alarm signals are valid when they are connected or disconnected. Generally, the ALM_SET+ and the ALM_SET- are disconnected.

If the ALM_SET+ and the ALM_SET- are connected, the alarm signal is valid when the alarm signal is disconnected.

If the ALM_SET+ and the ALM_SET- are disconnected, the alarm signal is valid when the alarm signal is connected.

If the first cabinet of the row provides the power supply of -48 V and the corresponding ground (-48 V ground), the alarm output cable should use the power supply. If the first cabinet does not provide the -48 V power supply, the cable can use the power supply provided from the ALM_OUT socket

For example, suppose the first cabinet of a row provides the power supply required and the ALM_SET+ and ALM_SET- are not connected. Figure 15 illustrates the connection relationship of the alarm output cable.

F I G U R E 15 C O N N E C T I O N O F T H E AL A R M OU T P U T C AB L E (W I T H ALM_SET+ AN D ALM_SET- U N C O N N E C T E D )

-48V

-48VGND

Red indicator

Yellow indicator

Buzzer

First cabinet of a row

ALM_OUT

S_ALARM+

S_ALARM-

G_ALARM+

G_ALARM-

BUZZ_OUT+

BUZZ_OUT-

Alarm output cable

2

10

3

11

1

9

Equipment side

As shown in Figure 15, the pin 10 of the alarm output cable is connected to the -48 V ground of the first cabinet of the row, while the pin 2 is connected to the critical alarm terminal of the cabinet. For the ALM_SET+ and the ALM_SET- are disconnected, the switch between the S_ALARM+ and S_ALARM- is disconnected when there is no critical alarm. When a critical alarm occurs, the switch will be closed and then the critical alarm circuit of the first cabinet is continued to light on the red indicator.



Board Reset The purpose of resetting a board is to make the processor of the board recover and work normally again when any fault occurs. Boards of the ZXWM M900 can be reset in two ways: hardware reset and software reset.

Caution: A board should not be reset unless you have confirmed that the board functions are affected because of the processor fault.

Hardware reset

On the panel of the NCP/NCPF/OHPF/APSF board, there is a reset hole marked with “RST”, inside which is a reset button. Press this button to reset the NCP/NCPF/OHPF/APSF board.

To prevent misoperation, the reset buttons of other boards are located inside the boards. You can not reset these boards through the panel.

Software reset

The boards of ZXWM M900 can be reset through the EMS (ZXONM E300). The ZXONM E300 supports four kinds of reset as described in Table 13.

T AB L E 13 S O F T W AR E R E S E T

Type Description Applicable Board Remark

Soft reset

It means to reset application programs of the specified board.

Reset flow: When the network element control processing board receives the soft reset command, it forwards the command to the MCU of the board to be reset. Then the MCU interrupts the program and execute the reset program to initialize the program.

All boards It will not affect services.

Hard reset

Reset flow: When the network element control processing board receives the hard reset command, it outputs a hard reset signal to the specified board to be reset. Then the board reset its CPU through the programmable logic device.

All boards It will not affect services.

IC reset It means to reset the FEC chip in the specified board.

Boards with FEC function: OTUF/OTU10G/OTUE10G/GEMF

It will affect services. Be cautious to perform the IC reset.

186 reset

186 refers to the CPU responsible for the HDLC communication on the NCP/NCPF/APSF board. The 186 reset means to reset this CPU.

NCP/NCPF/APSF It will not affect services.



Automatic Power Control Management With the Automatic Power Control (APC) function, a board can reduce or shut down the optical power automatically when the EDFA has no input light, so as to avoid the surge.

With the cooperation of ZXONM E300, the ZXWM M900 supports two APC functions: Automatic Power ShutDown (APSD) and Automatic Power Reduction (APR).

APC function of OA board

Taking the optical path illustrated in Figure 16 as example, Table 14 describes the comparison between the APSD and APR management in the case that the optical line between the OLA1-A board and the OLA2-A board is cut off.

F I G U R E 16 APC E X AM P L E O F O A B O AR D

OBA-A

TX-A

OLA1-A OLA2-A OPA-A

RX-A

OBA-B

TX-B

OLA2-BOLA1-BOPA-B

RX-B

Direction A Direction B

OTS

OMS

T AB L E 14 P R I N C I P L E O F APR/ APSD

APC Type Principle Remark

APR

1. When the optical line is cut off, the OLA2-A board detects there is no input light.

2. The OLA2-B board in this site sends the APC information to the downstream OLA1-B board.

3. Upon receiving the APC information, the OLA1-B board informs the OLA1-A board to reduce the output optical power to a safe level (below 0 dBm), so as to ensure the optical power in the faulty OTS is within the safety range.

The APC works on the faulty OTS. The other OTS will not be affected.

The Optical Transmission Section (OTS) refers to the optical path between OTM and OLA or between OLAs.

OADM equipment is located at the same position as OTM equipment.

APSD

1. When the optical line is cut off, the OLA2-A board detects there is no input light.

2. The OLA2-B board in this site sends the APC information to all the OLA and OPA boards in the B-direction OMS.

3. The OLA/OPA boards inform all OLA/OBA boards in direction A to shut down their lasers, so as to shut down all optical power in the OMS.

The APC works on the OMS. The Optical Multiplex Section

(OMS) refers to the optical path between OTMs.

OADM equipment is located at the same position as OTM equipment.



The APC configuration of OA board in the ZXONM E300 is introduced as follows.

Create an APR/APSD group for adjacent sites in the ZXONM E300, and then select an OA board to perform the APC function according to the actual fiber connection. All OA boards support the APR and APSD function. The OA boards in the same APR/APSD group should enable the same APC type.

When the APR/APSD function is enabled, the OA boards in the faulty OTS/OMS only transfer the OSC signal.

The APR function is recommended for it is more useful to locate the fault point than the APSD function.

APC function of DRA board

When DRA boards are used in a system, the APR group must be created based on OTS, as illustrated in Figure 17.

F I G U R E 17 D I V I S I O N O F ARP GR O U P I N A S Y S T E M W I T H DR A B O AR D S

OBA/OLA-A(executor) DRA-A

(executor)OPA/OLA-A

OBA/OLA-B(executor)DRA-B

(executor) OPA/OLA-B

OTS

OPM-A (monitor)

Direction A Input port 1

Direction B

OPM-B (monitor)

Input port 1

The APR configuration of DRA board in the ZXONM E300 is introduced as follows.

An OPM board must be configured for each DRA board as the monitor to assist the DRA board to perform the APR function.

In the ZXONM E300, an APR group should be created for each OTS. In this group, the OBA/OLA board and DRA board act as executors while the OPM board acts as the monitor.

The input port of an OPM board should be connected to the MON interface of the OA board on the receiving end in the OTS.

Checkpoint: An OTS with DRA boards in it can only be recovered manually through the ZXONM E300 after the APC function is enabled.



Setting Registers and Important Data of Boards The setting of registers and important data is implemented with the cooperation of the ZXONM E300.

Setting registers of boards

You can get the information of the NE through reading the contents in the registers of the NCP/NCPF board.

Setting important data of boards

Important data covers the software/hardware version and contents related to services of the boards, which are used to control the actions of boards. The important data can be stored upon power failure.

The important data of a board can be queried and modified by some commands for important data configuration.

Caution: To avoid any fault caused by important data modification errors, only professional maintenance person can use the configuratin commands.

Communication Test In the communication test, the communication status between different modules and the network management system is tested with the cooperation of ZXONM E300. A test type should be selected before the test. Table 15 lists all communication types supported by the ZXONM E300.

T AB L E 15 C O M M U N I C AT I O N TE S T TY P E S

Communication Test Type Description

NCP service processing loopback The data is looped from the service processing module of the Agent (NCP/NCPF board).

MCU service processing loopback The data is looped from the service processing module of the board to be tested.

NCP S interface loopback The data is looped from the S interface (186) at the bottom layer of the NCP/NCPF board.

MCU S interface loopback The data is looped from the communication layer at the bottom of the board to be tested.

NCP Qx interface loopback The data is looped from the Qx interface of the Agent (NCP/NCPF board) directly.



FEC Configuration Boards in the ZXWM M900 with the FEC function, such as OTUF, OTU10G, OTUE10G, SRM41 and GEMF, should be configured with the right FEC type and correct encode/decode mode so as to ensure the smooth transmission of services. The FEC configuration of such boards is implemented with the cooperation of the ZXONM E300.

1. FEC type supported by the ZXWM M900

The ZXWM M900 supports the following three FEC types:

FEC: Forward Error Correction

EFEC: Enhanced Forward Error Correction

AFEC: Advanced Forward Error Correction

Table 16 describes these three types and corresponding applicable boards.

T AB L E 16 FEC TY P E S S U P P O R T E D B Y T H E ZXWM M900

Type Description Application Board

FEC

The signal format complies with ITU-T G.975 before encoding; while the format complies with ITU-T G.709 after encoding.

In a 10 G system, the rate after encoding is 10.709 Gbit/s, while in a 2.5 G system, the rate after encoding is 2.66 Gbit/s.

The Optical Signal-to-Noise Ratio (OSNR) is improved equivalently by 5 dB ~ 6 dB.

OTUF OTU10G SRM41/SDH SRM41/OTN GEMF

EFEC

In a 10 G system, the rate after encoding is 12.5 Gbit/s.

The OSNR is improved equivalently by 7 dB ~ 9 dB.

This type is unavailable in a 2.5 G system.

OTUE10G

AFEC

The signal format complies with ITU-T G.709. And an improved algorithm is adopted in the FEC encoding/decoding.

In a 10 G system, the rate after encoding is 10.709 Gbit/s, which is lower than that of EFEC type. Its requirement for dispersion compensation is lower than the other two types.

The OSNR is improved equivalently by 7 dB ~ 9 dB.

This type is unavailable in a 2.5 G system.

OTU10G SRM41/OTN

Note:

SRM41/SDH: SRM41 board adopting the SDH synchronous convergence mode;

SRM41/OTN: SRM41 board adopting the OTN asynchronous convergence mode.

The SRM41 board does not support these two convergence modes at the same time.



2. Configuration principle

When boards of different types are connected with fibers, their FEC types and rate must be the same. Otherwise, service would be obstructed. Select regenerator boards according to Table 17 if they are needed in the transmission.

T AB L E 17 C O N F I G U R AT I O N O F R E G E N E R A T O R B O AR D

Board Regenerator Board Configuration

OTUF Regenerator OTUF board

GEMF Regenerator OTUF board

OTUE10G Regenerator OTUE10G board

OTU10G The single-channel unidirectional OTU10G board only supports the FEC type. The single-channel bidirectional OTU10G board supports FEC and AFEC type.

SRM41/SDH It only supports the FEC type, adopting the OTU10G board supporting the FEC type as the regenerator board.

SRM41/OTN

Use a special regenerator board, or Use two SRM41/OTN boards to implement the single-channel bidirectional

regeneration. Connect all tributary interfaces of these two boards one by one correspondingly. For example, connect the tributary 1 of one SRM41 board to the tributary 1 of the other SRM41 board, connect the tributary 2 of one SRM41 board to the tributary 2 of the other SRM41 board, and so on.

Each FEC type includes the encode mode, decode mode and the codex mode. Table 18 lists the selection of FEC mode of different types of boards in the ZXONM E300.

T AB L E 18 FEC M O D E C O N F I G U R AT I O N

Board Code Mode Decode Mode Codex Mode

OTUF

OTUF board at transmit end Client-side (OAC) input port

of single-channel bidirectional OTUF board

Line-side (OCH) input port 1 of bidirectional regenerator OTUF board

OTUF board at receive end Line-side (OCH) input port

of single-channel bidirectional OTUF board

Line-side (OCH) input port 2 of bidirectional regenerator OTUF board

Single-channel unidirectional regenerator OTUF board

OTUE10G OTUE10G board at transmit end OTUE10G board at receive end OTUE10G board at the regeneration end

OTU10G

OTU10G board at transmit end

Client-side (OAC) input port of single-channel bidirectional OTU10G board

OTU10G board at receive end

Line-side (OCH) input port of single-channel bidirectional OTU10G board

OTU10G board at the regeneration end

GEMF/SRM41 - - Aggregate (OCH) input port



Protection Management 1. Hardware support

Through configuring the OMCP, SWE, OTUP and OP board, different protection modes can be set for the ZXWM M900, as described in Table 19.

T AB L E 19 P R O T E C T I O N MO D E S F O R ZXWM M900

Protection Mode

Support Board Configuration Position Remark

OTU redundancy configuration: a pair of transmit and receive OTU board iis configured for both the working and the protection path OP

Configure the protection before OTU board at the transmit end and after the OTU board at the receive end OTU share configuration: the working

and the protection path share a pair of transmit and receive OTU board

OCH 1+1 protection

OTUP Its position is same as that of OTU board

The OP board is unnecessary for the implementation.

OMCP No rate limit OCH 1:N protection SWE

Configure the protection before OTU board at the transmit end and after the OTU board at the receive end

It only protects traffic with the rate under 2.7 Gbit/s.

OMS 1+1 protection OP Configure the protection after OBA

board and before OPA board -

2. ZXONM E300 software support

The working mode of the protection can be queried and set in the ZXONM E300. For 1+1 protection, external commands can be used to check and locate problems in the protection.

The ZXONM E300 provides six external commands: Clear, LW_R, LP_A, FS_R, MS_R and EX_R. The function of each command and corresponding priority is described in Table 20.

T AB L E 20 FU N C T I O N AN D P R I O R I T Y O F P R O T E C T I O N E X T E R N AL C O M M AN D S

External Command Function Priority

Clear To clear all external switching commands and WTR (Wait-to-Restore) time of the specified node. 1

LP_A To prevent the specified node from being switched to the protection path through sending a locking protection request.

2

LW_R

To prevent the specified node from being switched to the working path through sending a locking work request. For 1+1 protection, the execution result is same as that of LP_A.

3



External Command Function Priority

FS_R

To switch the specified node to the protection path forcibly. The normal traffic of the specified node will be switched from the working path to the protection path unless there is a switching request of the same or higher priority.

4

MS_R

To switch the specified node to the protection path manually. The normal traffic of the specified node will be switched from the working path to the protection path unless there is a switching request of the same or higher priority.

5

EX_R To run the APS protocol without influence the working of board. 6

Note: After the protection has been enabled, it is recommended to execute the “EX_R” command periodically to check whether the protection function is normal.

Optical Spectrum Management The ZXONM E300 supports the optical spectrum management, including the setting of OPM board and attenuation spectrum.

Setting OPM Board OPM configuration

This function allows users to query and modify OPM channels, and to monitor the optical channel performances in real time. The user can configure whether to monitor each optical channel according to actual system configurations.

OPM insertion loss configuration

This function is to set and query the insertion loss of each port of the OPM board. The insertion loss of port is the loss of optical power at the OPM monitor port and the optical line.

OPM spectrum display

The optical spectrum performance parameters, such as optical power and wavelength, can be queried and saved by executing the OPM spectrum display command. These parameters can also be displayed in graphics.

Setting Attenuation Spectrum When the ZXWM M900 is equipped with the DGE board and the VMUX board, users can use the attenuation spectrum function provided in the ZXONM E300 to adjust the optical power of each channel according to the power detected by the OPM board.



OCH Power Management The purpose of OHC power management is to keep the power equalization of the optical channel layer. This function can be implemented with the ZXONM E300. Table 21 lists the necessary boards, EMS and their functions in the OCH power management.

T AB L E 21 B O AR D S AN D EMS N E E D E D I N T H E OCH P O W E R M AN AG E M E N T

Board/EMS Function

OPM Monitoring the OSNR

VMUX Board

DGE

Providing the function of tuning channel attenuation. When the optical power of the OCH changes, it will determine the attenuation of each channel based on the optimization algorithm.

EMS ZXONM E300

It is used to set parameters for the power management, query the current optical power and send power management commands to boards. The ZXONM E300 with the version V3.16R2 or above is required.

OMS Power Management The purpose of the OMS power management is to optimize the optical power in the OMS with the ZXONM E300.

Table 22 lists the boards and EMS needed in the OMS power management and their functions.

T AB L E 22 B O AR D S AN D EMS N E E D E D I N T H E OMS P O W E R M AN AG E M E N T

Board/EMS Function

LAC It determines the attenuation amount of the LAC according to the optimization algorithm when the line attenuation changes.

OA

HOBA

Board

DRA

Providing the function of tuning gain. It determines the gain according to the optimization algorithm

EMS ZXONM E300

It is used to set parameters for the power management, query the current optical power and send power management commands to boards. The ZXONM E300 with the version V3.16R2 or above is required.

For the detailed configuration instruction of OMS power management, please refer to Unitrans ZXWM M900 (2.0) Dense Wavelength Division Multiplexing Optical Transmission System Hardware Manual.



Wavelength Adjustment The wavelength adjustment includes two types: wavelength fine adjustment and wavelength tuning. The wavelength adjustment function and the boards supporting it are described in Table 23.

T AB L E 23 W AV E L E N G T H AD J U S T M E N T FU N C T I O N AN D AP P L I C AB L E B O AR D S

Type Description Applicable Board

Wavelength fine adjustment

Adjusting the wavelength with an offset output by the board to the standard value according to the result of the OPM board or optical spectrum analyzer. The wavelength adjustment value is the offset to the central wavelength but not the actual wavelength.

OTU/SRM/GEM

Wavelength tuning

Tuning the output wavelength of a laser from a standard wavelength to another standard wavelength according to actual situation in the network. It improves the utilization ratio of wavelengths in the case that standby light sources are used in the system.

OTU/SRM/GEM with tunable lasers

Integrated Wavelength Supervision Subsystem The integrated wavelength supervision subsystem is applicable to a WDM system with over 80 channels at the spacing of 50 GHz or 100 GHz. It is composed of OWM board, boards of multiplexing type, optical transponder boards, NCP or NCPF board and the EMS ZXONM E300, to control the wavelength stability for each channel.

The ZXONM E300 supports the configuration of the automatic wavelength adjustment and automatic calibration for the OWM board.

OWM automatic wavelength adjustment: Configuring the monitoring port of OWM board, detecting the wavelength of the board under test, enabling/disabling the adjustment command.

OWM automatic calibration: Providing a standard wavelength, and sending the automatic calibration command through the ZXONM E300. The OWM board can calculate the offset between the tested value and the expected value. It deducts the offset from the testing result while measuring the operating wavelength so as to ensure the measurement precision.

Checkpoint: Only the ZXONM E300 with the version V3.16R2 or above supports the software configuration of integrated wavelength supervision subsystems.



Receiver Adaptive Control The purpose of the Receiver Adaptive Control (RAC) function is to adjust the parameters of optical receivers dynamically through analyzing current application environment, so as to diminish or even eliminate error frames. It is suitable for systems having high requirements on Signal Noise Ratio (SNR).

Only the OTU10G and SRM41 board of the ZXWM M900 provides the RAC function now. With the cooperation of the ZXONM E300, the OTU10G/SRM42 board implements the RAC function to improve the reliability and the SNR of the system.

Checkpoint: Only the ZXONM E300 with the version V3.16R2 or above supports the configuration of the RAC function.

Board Software Management The board software management function is implemented through the ZXONM E300. It includes the upgrade of board software, the management of software fault, and the query of upgrade log and software version.

Board software upgrade

Download the board software of an NE. The download status involves two modes: switching work mode and forced switching work mode. The board will be reset after successful download.

Software fault management

This function is used to query the software faults of an NE in a specified time segment. The query result can be saved as a file.

Board software upgrade log

This function is used to query the software upgrade records of an NE in a specified time segment.

Board software version query

This function is used to query the software version information of an NE.

Fan Rotate Speed Adjustment The ZXONM E300 sends the enabling command of fan speed adjustment to the FCB board, which controls the rotate speed of fans. With this function, users can query or configure the speed adjustment mode for the equipment.

When the automatic speed adjustment function is enabled, the ZXONM E300 will adjust the fan speed automatically according to the speed and temperature reported by the FCB board.



When the automatic speed adjustment is disabled, the FCB board takes measures to cool the environment with its temperature sensor and adjust the rotate speed according to the temperature reported by the sensor.

Time Management This function is used to query and set the NE time so as to

Keep the synchronization of the NCP/NCPF of various NEs

Keep the generation time of different NE’s alarm and performance data based on the same time standard

Check whether an NE is communicating with its upper-layer network management server normally.

Maintenance Precautions Before the maintenance operations on the ZXWM M900, the operator should learn not only the basic precautions for maintaining common communication equipment, but also the special precautions for maintaining transmission equipment, to ensure the 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 backplane. 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.



Optical Interface and Fiber Pigtail Maintenance Precautions Be sure to cover the unused optical interfaces of the boards with the

dustproof caps. This not only protects the maintenance persons’ eyes during their casual direct viewing on optical interfaces, but also protects optical interfaces against dust. Once dust enters the optical interface, it may affect the output optical power of the optical transmit interface and the receiving sensitivity of the optical receive interface.

Be sure to cover fiber pigtail connectors with dust caps once the fiber pigtail is unused.

Do not look straight into the optical interface on the optical boards 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.

DRA Board Maintenance Precautions Unplug the fiber from the IN interface of the DRA board

Only after the pump of the DRA board has been shut down in the EMS, can the fiber be unplugged from the IN interface of the DRA board.

Plug the fiber to the IN interface of the DRA board

First plug the fiber to the IN interface of the DRA board, and check whether there is any alarm related to the reflect power and reflectance performance. Then turn on the pump when the reflectance of the end surface is less than -30 dB.

Checkpoint: Clean the end surface of the fiber whenever it is plugged or unplugged to or from the IN interface of the DRA board so as to ensure the end surface reflection is greater than -30db.

Equipment Maintenance Precautions

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, and there is no short circuit inside the equipment.

2. Set the air switch of power supply on the subrack to "ON". Then the green indicator on the alarm indicator panel of the power distribution



subrack glows, and the NOM indicators of the PBX plug-in boxes in the subracks being powered become to glow in green. The equipment is powered on.

3. Check the running status of each board and make sure the fans are running normally. Otherwise, locate the fault and handle it in time.

To power off the equipment:

Set the air switch to “OFF” to shut down 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 while the equipment is power on. 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.

While the equipment is in service, clean the dust filter mesh of the fan regularly according to the equipment room environment conditions to ensure good heat dissipation of the equipment.

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.



This page is intentionally blank


C h a p t e r 3

Routine Maintenance

In this chapter, you will learn about: Items and periods of routine maintenance

Routine maintenance operations

Routine Maintenance Items The routine maintenance items and periods of the ZXWM M900 are listed in Table 24.

T AB L E 24 ZXWM M900 R O U T I N E M AI N T E N AN C E I T E M S

Maintenance Item Period

Check the temperature and humidity in equipment room Daily Environment maintenance Check the cleanness of the equipment room and make

sure there is no rodents and pests Weekly

Check power supply Daily

Check audio alarm of the first cabinet of a row Daily

Observe indicator status of the first cabinet of a row Daily

Observe indicator status of boards 0.5 day

Check the fans daily and clean them regularly Daily/Regularly

Check order wire telephones 2 weeks

Equipment maintenance

Check services 2 weeks

Change the login password and record it into a memorandum Monthly

Monitor browse tree Daily

Monitor topology map Daily

Monitor alarms Daily

Monitor performances Daily

EMS maintenance

Query system configurations Irregular



Maintenance Item Period

Query user operation logs Irregular

Print reports Irregular

Back up data Irregular

Environment Maintenance The ZXWM M900 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 ZXWM M900. 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 & Humidity The requirements of ambient temperature and humidity are listed Table 25.

T AB L E 25 S P E C I F I C AT I O N S O F AM B I E N T TE M P E R AT U R E A N D H U M I D I T Y

Item Specifications

Long-term operating 5°C ~ +40°C Ambient temperature

Short-term operating 0°C ~ +45°C

Long-term operating 10% ~ 90% Relative humidity

Short-term operating 5% ~ 95%

In normal operating conditions, the equipment room temperature and humidity are measured at a place 1.5 m above the floor and 0.4 m in front of the equipment cabinet.

Dustproof Requirement 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.

Chapter 3 - Routine Maintenance


Net Height of Equipment Room The net 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. It should be no less than 3 m.

Wall Surface of 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 Equipment Room Avoid direct sunlight. Average luminance should be within the range

from 300 lx to 450 lx. The light source should be not 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 Holes in Equipment Room All the drainage pipes should bypass the equipment room.

The quantity, location and size of reserved underground pipes, ground chutes and holes 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 Power supply requirement

The ZXWM M900 uses the nominal -48 V power, with the allowed voltage fluctuation range of -57 V to -40 V.

Power cable requirement

The routing, quantity and the layout of 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 are allowed in the middle of the power cable. The protection tubes, if necessary, should be constructed according to the construction specifications.

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 ZXWM M900, 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.

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.

Fire Escape Fire escape route of the equipment room should be marked clearly, and it should be made identifiable in darkness by using laminated material on the passage doors and walls.

Maintenance Space The front and rear space of the ZXWM M900 should be greater than 800 mm for the purpose of equipment maintenance.



Equipment Maintenance Operations Common equipment maintenance operations include power supply check, audio alarm check, cabinet indicator light observation, board indicator light observation, fan check and regular dustproof unit cleaning, equipment room environment check and service check (bit error test).

Power Supply Check Operation Purpose The ZXWM M900 is powered through the power distribution subrack. Check whether the power supply of the ZXWM M900 is normal by the indicator status on the power distribution subrack and its PBX plug-in box.

Inspect ion Cr i ter ia The power indicator on distribution subrack and the NOM indicator of PBX box glow in green.

Troubleshoot ing If the indicators are black out,

1. Check the power supply loop and make sure it is normal;

2. Check the air breaker of the distribution subrack, and make sure it has been switched on

3. Check the power cable of the equipment room, and make sure they are in normal condition.

Audio Alarm Check Operat ion Purpose The audio alarms can easily attract the attention of maintenance personnel. Make sure that the cabinet sounds loud and clear when alarm occurs in the equipment. If the ZXWM M900 outputs alarms to the first cabinet of its row, the first cabinet should also generate a sound when alarm occurs.

Inspect ion Cr i ter ia The ring trip switch on the cabinet can control the generation of alarm

sound. When the switch is set to “Normal”, the equipment should generate the alarm sound when an alarm occurs. Generally, the alarm sound should always be enabled.

If the alarm is output to the first cabinet of the row, the first cabinet should also generate alarm sounds.



Troubleshooting 1. Check and make sure that the ring trip switch has been set to the

“Normal” status

2. If the alarm is output to the first cabinet of the row, check the connection of cable between the switch on the first cabinet of the row and the ALM_OUT interface on the PWSB board, and make sure it is normal.

Cabinet Indicator Lights Observation Operation Purpose Check periodically whether indicators of the power distribution subrack are normal, and make sure that their status correctly reflects the occurrence of alarm and the alarm level. If the ZXWM M900 outputs the alarm to the first cabinet of its row, the indicator status of the cabinet should also be checked.

Inspect ion Cr i ter ia When the equipment works normally, only the green indicators should glow. The meaning of indicators on the power distribution subrack and the first cabinet of the row is shown in Table 26.

T AB L E 26 M E AN I N G S O F I N D I C AT O R S O F C AB I N E T AN D F I R S T C AB I N E T O F R O W

Status Indicators Name

On Off

Red indicator Critical alarm indicator

An emergency alarm occurs in the equipment, usually with an audio alarm.

No critical alarm in the equipment

Yellow indicator Major alarm indicator

A major alarm occurs in the equipment

No major alarm occurs in the equipment

Green indicator Power indicator Equipment power supply is normal

Equipment power supply is cut off

Troubleshoot ing When the red and yellow indicator lights of the cabinet glow, 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 Indicator Lights Observation Operat ion Purpose Further check the board indicator lights to keep aware of the operating status of the equipment after observing the cabinet indicator lights.

Inspect ion Cr i ter ia When the board works normally, only the green indicator light flashes.

The indicator lights status of common boards in the ZXWM M900 is described below.

1. NCP/NCPF board

The indicator lights, NOM (green) and ALM (red), on the NCP/NCPF board represents the running status of the NE. The working status and the indicator status of the NCP/NCPF board are listed in is shown in Table 27.

T AB L E 27 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S A N D T H E I N D I C AT O R S T AT U S O F T H E NCP/NCPF BO AR D

Indicator Status Working/Debugging Status

NOM (Green) ALM (Red)

Working Status

The system is lack of basic databases. Off Flashing

The NCP/NCPF board has been equipped in the ZXWM M900; but it has not been configured in the EMS.

On Flashing

The system runs normally or it is downloading a program to a board. Flashing Off

Errors occur while the system is running. Off On

The NCP/NCPF board is started and initialized. The red indicator and green indicator flash alternately.

The Agent program is downloaded to the NCP/NCPF board.

The red indicator and green indicator flash at the same time.

Debugging Status

Mandatory IP status (the DIP2 pin of the DIP switch S2 is set to “ON”) Off On

Probe & debugging status ( the DIP1 and DIP8 of the DIP switch S2 are set to “ON”) On Off

Note:

The DIP switch S2 is located on the PCB of the board.

The J9 interface of the OA subrack is used as the network interface in the debugging of NCP board; while the NET interface on the board panel is used as the network interface in the debugging of NCPF board.



2. OSCF board

The indicator lights of the OSCF board include those indicating the running status of the board and those indicating the working status of optical/electrical interfaces on the board.

Table 28 describes the running status of the board and corresponding indicator status.

T AB L E 28 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S A N D T H E I N D I C AT O R S T AT U S O F T H E OSCF B O AR D

Indicator Status Working/Debugging Status


Working Status

The board is waiting for configuration. The red indicator and the green indicator flash alternately.

The board is running normally, and no alarm occurs.

It flashes slowly and regularly. Off

The board is running normally, and some alarm occurs.

It flashes slowly and regularly. On

The board is performing self-test upon power on.

The red indicator and the green indicator flash quickly for three times.

The board is waiting for program downloading.

The red indicator and the green indicator flash quickly at the same time.

The board is in the program downloading status.

The red indicator and the green indicator flash slowly and regularly at the same time.

Debugging Status

The board is running the Boot program in the mandatory IP status. (the DIP2 pin of the DIP switch S2 is set to “ON”)

Off On

Probe & debugging status ( the DIP1 and DIP8 of the DIP switch S2 are set to “ON”)

On Off

Note:

Both the DIP switch S2 and the Ethernet electrical interface for debugging are located on the PCB of the OSCF board.

When the board is in the debugging status, the STA indicator light and Ethernet electrical interface indicator lights of the OSCF board are all blacked out.

Table 29 describes the working status of optical/electrical interfaces of the OSCF board and the corresponding indictors’ status.



T AB L E 29 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S A N D T H E I N D I C AT O R S T AT U S O F T H E OP T I C AL /E L E C T R I C AL I N T E R F AC E S O N T H E OSCF B O AR D

Indicator Status

Working Status STA (Bi-color)

Ethernet Electrical Interface Indicator (Yellow)

Ethernet Electrical Interface Indicator (Green)

The optical interface 1 is connected while the optical interface 2 is unconnected.

Glowing in green. - -

The optical interface 1 is sending and receiving data packets; while the optical interface 2 is unconnected.

Flashing in green. - -

The optical interface 2 is connected while the optical interface 1 is unconnected.

Glowing in red. - -

The optical interface 2 is sending and receiving data packets; while the optical interface 1 is unconnected.

Flashing in red. - -

Both the optical interface 1 and 2 are connected. Glowing in orange. - -

Both the optical interface 1 and 2 are sending and receiving data packets.

Flashing in orange. - -

Both the optical interface 1 and 2 are unconnected. Off - -

The Ethernet electrical interface is connected. - On -

The Ethernet electrical interface is unconnected. - Off -

The Ethernet electrical interface is sending and receiving data.

- On Flashing

Note: For the bi-color indicator STA, when the red light and green light glows at the same time, it will be lighted in orange.



3. APSF board

There are three indicator lights on the APSF board panel: NOM, ALM and STA.

Table 30 describes the working status of the board and corresponding indicator status.

T AB L E 30 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S A N D T H E I N D I C AT O R S T AT U S O F T H E APSF B O AR D

Indicator Status Working Status NOM

(Green) ALM (Red) STA (Bi-color)


Flashing slowly and regularly

Off -


Flashing slowly and regularly

On -


The red indicator and the green indicator flashes quickly for three times.

-


The red indicator and the green indicator flashes quickly at the same time.

-


The red indicator and the green indicator flashes slowly and regularly at the same time.

-

No protection group has been configured. - - Off

No switching - - Off

A-direction switching - - Glowing in red

B-direction switching - - Glowing in

green

The protection mode of the first protection group is the channel ring shared protection or the MS ring shared protection Straight through - - Glowing in

orange

No switching - - Off

Adding switching - - Glowing in red

Dropping switching - - Glowing in

green

The protection mode of the first protection group is the 1:N channel protection Adding/Dropping

switching - - Glowing in orange




4. OTUP board

There are three indicator lights on the OTUP board panel: NOM, ALM and STA.

Table 31 describes the working status of the OTUP board and corresponding indicator status.

T AB L E 31 CO R R E S P O N D I N G R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S AN D I N D I C AT O R S T AT U S O F T H E OTUP BO AR D

Indicator Status Working Status

NOM (Green) ALM (Red) STA

The board is waiting for configuration.

The green indicator and the red indicator flash alternately. -


Flashing slowly and regularly Off -


Flashing slowly and regularly On -


The red indicator and the green indicator flashes quickly for three times. -


The red indicator and the green indicator flashes quickly at the same times. -


The red indicator and the green indicator flashes slowly at the same times.

The board is working in the working channel.

Flashing slowly and regularly - Off

The board is working in the protection channel.

Flashing slowly and regularly - On



5. SRM41/SRM42 board

The indicator lights of the SRM41/SRM42 board include those indicating the running status of the board and those indicating the working status of tributary optical interfaces on the board.

Board running indicators: NOM (green) indicator and ALM (red) indicator.

Tributary optical interface indicators: For each tributary optical interface, there is an indicator (green) indicating its working status.

The working status of the SRM41/SRM42 board and corresponding indicator status are shown in Table 32.

T AB L E 32 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S AN D I N D I C AT O R S T AT U S O F T H E SRM41/SRM42 B O AR D

Indicator Status

Working Status NOM (Green) ALM (Red)

Tributary Optical Interface Indicator (Green)

The Bootrom program is downloaded.

Off Off -


The green indicator and the red indicators flash alternately. -




Flash slowly and regularly Normally on -


The red indicator and the green indicator flashes quickly for three times. -

The board is in the downloading status

The red indicator and the green indicator flashes slowly at the same times. -

The tributary optical interface is working normally.

- - On

The tributary optical interface is working abnormally.

- - Off



6. GEMF board

The indicator lights of the GEMF board include those indicating the running status of the board and those indicating the working status of Ethernet optical interfaces on the board.


Ethernet optical interface indicators: For each Ethernet optical interface, there is an indicator (green) indicating its working status.

The corresponding relationship between the running status of the GEMF board status and indicator status is shown in Table 33.

T AB L E 33 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S AN D I N D I C AT O R S T AT U S O F T H E GEMF B O AR D

Indicators

Working Status NOM (Green) ALM (Red)

Ethernet Optical Interface Indicator (Green)

The Bootrom program is downloaded.

Off Off -

The FPGA program is downloaded.

The red indicator and the green indicator flash slowly for 30 seconds. -


The red indicator and the green indicator flash alternately. -






The red indicator and the green indicator flash quickly for three times. -

The board is waiting for download

The red indicator and the green indicator flash quickly at the same time. -

Downloading status The red indicator and the green indicator flash slowly at the same time. -

The tributary interface has no LOS alarm.

- - On

The tributary interface has LOS alarm.

- - Off



7. CA board

The indicator lights of the CA board include board running indicators, active/standby clock board indicators and clock status indicator.


Active/standby clock board indicator: M/S (green) indicator.

Clock status indicators: CKS1 (green) indicator and CKS2 (green) indicator. The current system clock running status can be indicated via the combination of these two indicator’s status.

The correspondence between CA board indicator and the board’s running status is shown in Table 34.

T AB L E 34 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S AN D I N D I C AT O R S T AT U S O F T H E C A B O AR D

Indicator Status Working Status NOM

(Green) ALM (Red)

M/S (Green)

CKS1 (Green)

CKS2 (Green)

The Bootrom program is downloaded. Off Off - - -


The red indicator and the green indicator flash alternately.

- - -


Flashing slowly and regularly Off - - -


Flashing slowly and regularly On - - -



- - -

Board in downloading status


- - -

The board is configured as the master CA board - - On - -

The board is configured as the standby CA board. - - Off - -

The CA board runs in the clock lock mode (normal tracing).

- - - On On

The CA board runs in the clock holdover mode. - - - On Off

The CA board runs in the fast pull-in mode. - - - Off On

The CA board runs in the clock free run mode. - - - Off Off



8. OMCP board

There are three indicator lights on the panel of the OMCP board: NOM, ALM and STA.

The relationship between the running status of the OMCP board and the indicator status is shown in Table 35.

T AB L E 35 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E W O R K I N G S T AT U S A N D I N D I C AT O R S T AT U S O F T H E OMCP B O AR D


NOM (Green) ALM (Red) STA (Bi-color)

The Bootrom program is downloaded. Off Off Off


The red indicator and the green indicator flash alternately. Off






The red indicator and the green indicator flash quickly for three times. Off

The board is in the downloading status.

The red indicator and the green indicator flash quickly at the same time. Off

The input of channel is switched. - - Glowing in red

The output of channel is switched. - - Glowing in green

Both the input and output of channel are switched at the same time.

- - Glowing in orange




9. SWE board

The SWE board indicator is on the front panel, involving the board’s running indicators and channel’s receiving/transmitting indicators.

Board running indicators: NOM (green) and ALM (red).

Channel receive/transmit indicators: For each channel receive/transmit interface, there is a receiving indicator (Rx), and a transmitting indicator (Tx), where x indicates the channel number.

The corresponding relation of the SWE board status and indicator status is shown in Table 36

T AB L E 36 C O R R E S P O N D E N C E R E L AT I O N S H I P B E T W E E N T H E R U N N I N G S T AT U S AN D I N D I C AT O R S T AT U S O F T H E SWE B O AR D



Rx (Red)

Tx (Green)


The red indicator and the green indicator flash alternately. Off Off


Flashing slowly and regularly Off - -


Flashing slowly and regularly On - -


The red indicator and the green indicator flash quickly for three times. Off Off

The board is waiting for download.


- -

The board is in download status.

The red indicator and the green indicator flash slowly at the same time.

- -

The transmitting of the channel is enabled.

- - - On

The transmitting of the channel is disabled.

- - - Off

The received signal has no LOS.

- - On -

The received signal has LOS. - - Off -



10. Other boards

Except the boards described above, other boards installed on the OA subrack, OTU subrack, and TMUX subrack have two indicators on their panels: NOM (green) and ALM (red) respectively.

The corresponding relation between the board status and indicator status is shown in Table 37.

T AB L E 37 C O R R E S P O N D E N C E R E L AT I O N S H I P O F T H E W O R K I N G S T A T U S A N D I N D I C AT O R S T AT U S O F O T H E R B O AR D S




The red indicator and the green indicator flash alternately.

The board is running normally, and no alarm occurs. Flashing slowly and regularly Off

The board is running normally, and some alarm occurs. Flashing slowly and regularly On



The board is waiting for download.


The board is in download status. The red indicator and the green indicator flash slowly at the same time.

Fan Check and Dustproof Unit Cleansing Operation Purpose Good heat dissipation 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 1. Observe the indicator status of the independent fan unit periodically.

2. Take out the air filter from the bottom of the subrack, clean it with water and air-dry it before putting it back.

Inspect ion Cr i ter ia 1. The NOM indicator (green) of the fan unit flashes slowly, and the fan

runs stably at regular rotation speed, without abnormal sound.

2. The air filter is not blocked, and the equipment is well ventilated.



Troubleshoot ing If the fan rotates at irregular speed, unplug the fan box and check

whether foreign substance exists in the fan unit, and whether the fan is damaged.

If the fan does not run or the indicator is blacked out, check whether the fan is damaged and whether the cable is connected to the fan normally.

Three fan units are independent of each other. When one of them fails, press the locking switch on the panel of the fan unit and then pull it out from the front of the subrack. Taking a fan unit in the OA subrack as example, Figure 18 illustrates the maintenance operation for a fan unit.

F I G U R E 18 M AI N T E N AN C E O F AN I N D E P E N D E N T F AN U N I T

1 OA Subrack 2. Independent Fan Unit

If the air filter is blocked, clean it and the equipment room to keep the environment neat and clean.



Equipment Room Environment Inspection Operat ion Purpose Keep the equipment working normally in a clean environment with proper temperature and humidity and free of rodent and pest.

Inspect ion Cr i ter ia 1. The equipment room is free from explosive, conductive, magnet-

conductive, and corrosive dust particles. The density of dust particles with a diameter of more than 5 μm should not exceed 3×104/m3. The floor is clean, and the windows and doors of the equipment room have proper airproof devices.

2. The ambient temperature of the equipment should be within the range: 5°C~45°C.

3. The relative humidity in the equipment room should be in the range: 10%~90%.

4. No rodent and pest clustering is allowed in the equipment’s ventilation pipes, ventilation channels and cabling duct.

Troubleshoot ing 1. Clean the equipment room periodically.

2. If the temperature and humidity are out of the range, check the air-conditioning system, and adjust it to a proper temperature.

3. Eliminate any rodent or pest found in equipment room timely to prevent them from damaging the equipment.

Service Inspection - Bit Error Test Operat ion 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.

Operat ion Method In respect of idle wavelength channels between two sites, the test can

be performed on the idle channels to test the traffic channel quality between two sites. For the operation of bit error test, please refer to the section “Bit Error Test” in Chapter 2.

If there is no idle wavelength division channel between two sites, the system errors can be available indirectly from the access equipment.



For instance, if the access equipment is SDH equipment, an online test with a bit error tester can be performed on the SDH equipment. If any error is found, search the error source segment according to the signal flow direction and the correspondence relationship between the wavelength division channel and the SDH equipment. Then analyze the optical power to find out the cause of the error.

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.

Inspect ion Cr i ter ia No bit error exists on any traffic channel.

Troubleshoot ing When there is bit error on the traffic channel, handle them according to the instruction in the section “Bit Error Fault” in Chapter 6.

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.

Caution: To ensure successive statistics of the equipment alarm and performance data, avoid exiting the EMS server after it has been started.

This section briefly introduces the EMS maintenance operations. Refer to the related EMS software manuals (ZXONM E300) 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.

Inspect ion Cr i ter ia 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.

Troubleshoot ing 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, please refer to the section “EMS Connection Fault” in Chapter 6.

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.

Inspection Criteria The EMS client can log in to the EMS server normally.

In the EMS client operation window, the “Time Management” command can be executed on an NE, which means the connection between the NE equipment and the EMS is normal. Please refer to the section “Time Management” for more details.

Troubleshooting To troubleshoot faults of EMS connections, refer to the section “EMS Connection Fault” 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.

Note: The EMS software can only monitro and manage the NEs who are in normal communication with the EMS host.

Inspection Criteria The state of NE icon should be online.

There shouldn’t be any alarm indicator on the NE icon.

The optical connection is normal.

Troubleshooting If there is fault of EMS connection, please refer to the section “EMS

Connection Fault” in Chapter 6 for troubleshooting.

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 the section “Common Alarm Messages and Solutions” in Chapter 5.

If the optical connection is abnormal, check the corresponding optical cables and fiber pigtails.

Alarm Monitoring Operation Purpose In the ZXONM E300 EMS software, users can monitor the alarm messages of an NE; thus keep aware of the current working status of the NE, and detect/handle the alarm message of the NE in time.

Note: The EMS software can only monitro and manage the NEs who are in normal communication with the EMS host.



Operation Method In the client operation window of EMS software, open the monitoring

window to monitor the alarm messages of all NEs in real time.

In the client operation window of the EMS software, query the current or history alarm messages of the selected NEs.

Inspect ion Cr i ter ia The NE has no current alarm information.

The NE has no unconfirmed history alarm information.

Troubleshooting To troubleshoot faults of EMS connections, refer to the section “EMS

Connection Fault” in Chapter 6.

To handle the alarm messages, refer to the section “Common Alarm Messages and Solutions” in Chapter 5.

Performance Monitoring Operat ion Purpose In the ZXONM E300 EMS software, the user can monitor the performance messages of an NE; thus keep aware of the current service performance of the NE, and detect/handle the performance messages of the NE in time.

Operat ion Method In the client operation window of the EMS software, query the following performance periodically:

1. Query the 15-minute and 24-hour performance events of the OTU/SRM/GEM board, to judge whether the board works normally.

2. Query the input and output power of the OA board so as to monitor the line loss.

3. Collect the system historical 15-minute performance events periodically, so as to judge the board and system running conditions.

Inspect ion Cr i ter ia For the digital performance of an NE, there is no performance over-

threshold event.

For the analog performance of an NE, the performance value complies with related indexes.

Troubleshoot ing For the methods of handling performance messages, please refer to the section “Performance Message and Handling” in Chapter 4.



System Configuration Query Operat ion Purpose In the ZXONM E300 EMS software, the user can query the configuration information of an NE. The result of this query is the network configuration in the EMS software, which may not be the actual configuration of the NE. To obtain the actual configuration and current working status of the NE, the user need to perform some operations periodically such as backing up the NE data, uploading the data and comparing the data in the EMS database with that in the NE database.

Operat ion Method 1. Enable the function of periodically uploading and comparing NE data,

the EMS will automatically issue an upload comparing command according to the period set by the operator.

2. Execute the upload comparing command, to upload the data of a selected NE manually.

Inspect ion Cr i ter ia The current network configuration and NE configuration are consistent with the actual networking.

Troubleshoot ing 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 according to user requirements.

User Operation Logs Query Operat ion 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.

Inspect ion Cr i ter ia No illegal login

No user operations affecting system operation or service functions



Troubleshoot ing 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 With the printing function of the EMS software, the user can print out the configuration reports of NEs, covering the contents of NEs information, performance and alarm messages. The reports can be taken as operation/maintenance records and the basis of network analysis.

Performance Messages Saving With the saving function in the current performance and historical performance dialog boxes of the EMS software, the user can save the queried performance messages to a file, which can be used for the maintenance in the future.

Backup Data 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 can be recovered quickly in case of network fault or EMS data loss.

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.





C h a p t e r 4

Performance Message and Handling

In this chapter, you will learn about: Introduction to performance messages of the ZXWM M900

Causes, influence and handling of various performance events

Definition of Performance ZXWM M900 performance involves two kinds of performance: digital performance and analog performance.

Digital Performance Digital performance

Digital performance refers to the parameters of channels and interfaces which embody the transmission and service quality.

During the running of equipment, the MCU of a board detects the digital performances and count the performance value.

Digital performance threshold

The digital performance threshold is divided into 15-minute performance threshold and 24-hour performance threshold. Each of them can be further divided into higher threshold and lower threshold.

Related influence

If the digital performance value is beyond the threshold, a performance over-threshold event (performance out-of-limit alarm) will be arisen. It may be a 15-minute performance over-threshold event and a 24-hour performance over-threshold event.

15-minute performance over-threshold event

When detecting that the 15-minute performance value exceeds the upper threshold of 15-minute performance, the MCU of the board



will report a 15-minute performance over-threshold event. If the performance value is less that the 15-minute performance lower threshold in the later 15 minutes, it can be confirmed that the 15-minute performance over-threshold event has disappeared.

24-hour performance over-threshold event

After receiving the historical 15-minute performance value reported by the MCU, the NCP board will accumulate the 24-hour performance values. If the accumulated value exceeds the 24-hour performance higher threshold, it will report the 24-hour performance over-threshold event. In the next 24 hours, if the 24-hour performance value is lower than the 24-hour performance lower threshold, it can be confirmed that the 24-hour performance over threshold event has disappeared.

Analog Performance Analog performance

Analog performance refers to the parameters that embody the working conditions of physical devices or circuits, such as the received and launched optical power of a laser.

Analog performance threshold

For the analog performance can not be accumulated, the difference (offset) between the analog performance value and the reference value is used as the judgment basis to check whether analog performance is normal. Generally, a higher threshold and a lower threshold are presented for each analog performance.

Related influence

When a transient performance value is beyond the range confined by the higher and lower thresholds, a performance over-threshold event (performance over-threshold alarm) will be reported. When the transient value is between the higher threshold and the lower threshold, the performance over-threshold event will disappear.

Chapter 4 - Performance Message and Handling


Performance Message Classification This section introduces the performance of the ZXWM M900 according to the classification by performance detection point and performance type.

Classification by Performance Detection Point The performance items classified by detection point are listed in Table 38.

T AB L E 38 P E R F O R M AN C E I T E M S O F T H E ZXWM M900 (C L A S S I F I E D B Y D E T E C T I O N P O I N T)

Detection Point Performance Remark

Input optical power -

Output optical power -

Laser bias current -

Laser TEC current -

Laser temperature offset -

B1_ERROR -

B2_ERROR Only the SRM/GEM/OTU10G board has the performance.

ES

SES

UAS

This performance is only available when the client signal is an SDH signal.

FEC correct error

Uncorrect frame

Only the boards with FEC function have the performance.

Channel optical power

Channel OSNR

OCH

Channel central optical wavelength

Only the OPM board has the performance.

ES

SES

UAS

B1_ERROR

This performance is only available when the client signal is an SDH signal.

B2_ERROR Only the SRM/GEM/OTU10G board has the performance.

OTUk BIP8 ERROR Only the boards with FEC function have the performance.

Input optical power

OAC

Output optical power

Only the OTU boards have the performance.



Detection Point Performance Remark

Total input optical power -

Total output optical power -

Pump laser bias current

Pump TEC current

OMS

Pump laser temperature offset

Only the OA board has the performance.

Input optical power -

Output optical power -


Pump TEC current

Pump laser bias current

Only the OA board has the performance.

Pump reflect power

OTS

Pump reflect ratio

Only the DRA board has the performance.

Input power

Output power

This performance is only detected for the optical interfaces of the OSC board and the 10BASE-FL optical interfaces of the OSCF board.

EB -

ES -

SES -

UAS -

LOF -

CRC ERR

MSG_LOSS

OSC

Laser bias current

Only the OSCF board has the performance.

Board OVER_BRDTMP -

Note:

OCH: Optical Channel layer

OAC: Optical Access layer

OMS: Optical Multiplexing Section layer

OTS: Optical Transmission Section layer

OSC: Optical Supervisory Channel



Classification by Performance Type In terms of type, the performance can be classified into five types: optical power performance; bit error performance, temperature performance, current performance, and synchronization performance.

Note: The performance of each type will be introduced according to the performance board. A performance board refers to a board in the EMS that displays the performance value, but is not necessarily the source of the performance message.

1. Optical power performance

T AB L E 39 P E R F O R M AN C E O F T H E ZXWM M900 (O P T I C AL P O W E R P E R F O R M AN C E )

Board Performance Unit

Output optical power of laser dBm

Input optical power of APD module dBm OTU board series

Input optical power of PIN module dBm

ODU Total input optical power dBm

OMU/VMUX Total output optical power dBm

OAD Tributary optical power dBm

Input optical power dBm OBA/OPA/OLA/HOBA

Output optical power dBm

Input optical power of working channel dBm OP

Input optical power of protection channel dBm

OPM Optical power of channel (optical interface 1 ~ optical interface 4) dBm

A-direction received optical power dBm OSC

B-direction received optical power dBm

Aggregate input optical power dBm

Aggregate output optical power dBm

Tributary input optical power dBm SRM41/SRM42/GEMF

Tributary output optical power dBm

Output optical power of MUX signal dBm OCI

Input optical power of DMUX signal dBm

Output optical power dBm

Input optical power dBm

CS input power dBm

CS output power dBm

LS input power dBm

OBM

LS output power dBm




Output optical power dBm DGE


Output optical power dBm OSC/OSCF


LAC Output optical power dBm

Output optical power dBm SDM


Output optical power of pump dBm

Output optical power (C band) dBm DRA

Reflected optical power of pump dBm

2. Bit error performance

T AB L E 40 P E R F O R M AN C E O F T H E ZXWM M900 (B I T E R R O R P E R F O R M AN C E )

Board Performance Remark

15-minute B1 error

15-minute ES

15-minute SES

15-minute UAS

15-minute BER

This performance is only available when the client traffic is SDH traffic.

15-minute received packet

15-minute received error packet

15-minute received error packet ratio

This performance is only available when the client traffic is GbE traffic.

FEC corrected BE

BER after FEC

Uncorrectable frame by FEC

15-minute OTUk BIP8 BE

OTU board series

15-minute B2 error

Only the OTUF/OTU10G/OTUE10G board has these performance items.

Background BE -

ES -

SES - OSC

UAS -

Received data message -

Sent data message -

Lost data message - OSCF

CRC error packet -



Board Performance Remark

B1 error -

ES -

SES -

UAS -

BER -

B2 error -

FEC corrected BE

BER after FEC

FEC uncorrectable frame

Aggregate receive end

OTUk BIP8 BE

Only the SRM41 board of them has these performance items.

B1 error -

B2 error -

ES -

SES -

UAS -

SRM41/SRM42

Tributary receive end

BER -

B1 error -

ES -

SES -

UAS -

BER -

B2 error -

FEC corrected BE -

BER after FEC correction -

FEC uncorrectable frame -

Aggregate receive end

OTUk BIP8 BE -

Total received data packet -

Total received byte -

Received error packet ratio -

Received error packet -

Total sent data packet -

GEMF

Tributary receive end

Total sent byte -



3. Temperature performance

T AB L E 41 P E R F O R M AN C E O F T H E ZXWM M900 (T E M P E R A T U R E P E R F O R M AN C E )

Board Perfromance Unit Remark

Laser temperature offset ℃ - OTU board series Board environment

temperature ℃ -

ODU/OMU Working temperature ℃ Only the OMU/ODU board adopting AWG devices has this performance.

VMUX Working temperature ℃ -

OWM/SWE Board environment temperature ℃ -

FCB FCB temperature ℃ -


℃ -

Pump laser temperature ℃ -

Environment temperature ℃ - OBA/OPA/OLA/HOBA

EDF temperature ℃ Among these boards, only the OA board of L band has this performance.

Environment temperature ℃ Among these boards, only the SRM41 board has this performance.

Laser temperature ℃ -

SRM41/SRM42/GEMF

Inner-module temperature

℃

For the SRM42 board, this performance is detected at the aggregate end. For these three boards, it depends on the board configuration whether to detect the performance at the tributary end.

Inner-module temperature

℃ - DRA

Laser temperature offset ℃ -



4. Current performance

T AB L E 42 P E R F O R M AN C E O F T H E ZXWM M900 (C U R R E N T P E R F O R M AN C E )


Laser bias current mA OTU series boards

Laser TEC current mA

EDFA pump bias current mA

EDFA pump TEC current mA OBA/OPA/OLA/HOBA

Pump background PD current mA

VMUX Laser temperature offset mA

Laser bias current at the aggregate transmit end mA

Laser TEC current at the aggregate transmit end mA

SRM41/SRM42/GEMF

Tributary laser bias current mA

Laser operating current mA DRA

Laser TEC current mA

5. Synchronization performance

T AB L E 43 P E R F O R M AN C E O F T H E ZXWM M900 (S Y N C H R O N I Z AT I O N P E R F O R M AN C E )

Board Performance

Number of A-direction OOF times OSC

Number of B-direction OOF times



Analysis of Common Performance Table 44 ~ Table 52 provides information about possible causes and handling methods of common performances for your reference during the maintenance of the equipment.

T AB L E 44 OTU L A S E R OU T P U T OP T I C AL P O W E R P E R F O R M AN C E OV E R TH R E S H O L D

Item Description

Performance OTU laser output optical power performance value over threshold

Explanation The OTU laser output optical power is lower than the output lower power threshold or the no output power threshold.

Category Optical power performance

Board OTU series board

Possible cause OTU board laser fault OTUR protection is enabled when there is no input optical power

Solution Replace the OTU board Turn off the OTUR protection enabling

Note



T AB L E 45 OTU ( APD/P IN R E C E I V I N G M O D U L E ) I N P U T OP T I C AL P O W E R OV E R TH R E S H O L D

Item Description

Performance OTU (APD/PIN receiving module) input optical power over threshold

Explanation The OTU (APD/PIN receiving module) input optical power is lower than the input lower power threshold or the no input power threshold, or higher than the input overload threshold.


Board OTU series board

Possible cause

In the case of input optical power lower than the lower threshold

For OTUT: The optical power from SDH is too low, the SDH transmit optical board is faulty, or the attenuation between the SDH equipment and the OTUT board in the ZXWM M900 is too high.

OTUG and OTUR: The optical power from the upstream ODU board is too low, which may be caused by a fault in optical connection between the ODU board and this board, an ODU board fault, a fault in the upstream board of the ODU board or site.

In the case of input optical power higher than the upper threshold

OTUT: The optical power from the SDH is too high, which may have been caused by the removing of the attenuator (by someone) between the SDH optical transmit board and the OTUT of the ZXWM M900.

OTUG and OTUR: The optical power from the upstream is excessively high, which may have been caused by the missing (withdrawn by someone) of the attenuator between the local site input part and the upstream site output part.

Solution

In the case of input optical power lower than the lower threshold

For OTUT: The optical power from SDH equipment is too low. Replace the faulty SDH board. Check carefully the devices such as the flange and the fiber pigtails between the SDH equipment and OTUT, and make sure that there is no extra attenuation caused by the damage and dirt on the coiled fibers and devices.

For OTUG and OTUR: The optical power from the upstream is too low. Check the relevant output optical power of the ODU board. If it is consistent with the OTU input optical power, then the ODU or its upstream is faulty. If the output relevant optical power of ODU is normal, the optical connection between ODU and OTU is faulty. Check carefully the devices such as the flange and the fiber pigtails between the ODU and the OTU, and make sure that there is no extra attenuation caused by the damage and dirt on the coiled fibers and devices.

In the case of input optical power higher than the upper threshold

For OTUT: If the optical power from SDH equipment is too high, add an attenuator between the SDH equipment and the ZXWM M900.

For OTUG and OTUR: If the optical power from the upstream is too high, add an attenuator at the input part of the local site or the output part of the upstream site.

Note



T AB L E 46 ODU B O AR D C H A N N E L OP T I C AL P O W E R P E R F O R M AN C E OV E R TH R E S H O L D

Item Description

Performance ODU board channel optical power performance value over threshold

Explanation The ODU channel optical power is lower than the low optical power threshold or the no optical power threshold.


Board ODU

Possible cause

ODU fault: The ODU is faulty if the ODU total input optical power is normal, while the output optical power performance value of all the channels or individual channel is lower than the low optical power threshold or the no optical power threshold.

Upstream fault: If the ODU’s total input optical power performance value is lower than the low optical power threshold or the no optical power threshold, the ODU upstream connection or the upstream board is faulty. In this case, check the upstream step by step.

Solution

ODU board fault: Replace the ODU board. If upstream is faulty, check the input and output optical power

of the upstream board step by step via the EMS to locate the fault point, and then check the optical connection at the fault point and check the optical power.

Note



T AB L E 47ODU TO T AL I N P U T OP T I C AL P O W E R P E R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance ODU total input optical power performance value over threshold

Explanation The ODU total input optical power is lower than the lower optical power threshold or the no optical power threshold.


Board ODU

Possible cause

The optical power from the upstream OPA is too low, which may be caused by The optical connection fault between the upstream OPA and the

local board The upstream OPA fault The optical connection fault between the upstream OPA and

ODF The optical cable line fault The upstream site fault of the OPA

Solution

Check the output optical power of OPA, If the output optical power is consistent with the total input

optical power of ODU, then the OPA or its upstream is faulty. If the output optical power of OPA is normal, then the optical

connection between OPA and ODU is faulty. In this case, carefully check the flange and fiber pigtails between the OPA and the ODU, and make sure that there is no extra attenuation caused by the damage and dirt on the coiled fibers and devices.

Note



T AB L E 48 OMU TO T AL OU T P U T OP T I C AL P O W E R P E R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OMU total output optical power performance value over threshold

Explanation The total output optical power of the OMU board is lower than the low output optical power threshold or the no optical power threshold.


Board OMU

Possible cause

If the output optical power of each channel of the OTU board is normal, while the OMU total output optical power performance value is lower than the lower optical power threshold or the no optical power threshold, the over-threshold may be caused by

OMU board fault

Optical connection fault between the OTU and the OMU

If the output optical power of each channel of the OTU board is abnormal, the fault lies in the OTU board.

Solution

Check whether the input optical power of each channel of the OMU is consistent with the output optical power of corresponding channel of the OTU.

If it is consistent, the OMU is faulty.

If it is inconsistent, check carefully the devices such as the flange and the fiber pigtails between the OTU and the OMU, and ensure that there is no extra attenuation caused by the damage and dirt on the coiled fibers and devices.

Replace the OTU board.

Note



T AB L E 49 O AD TR I B U T AR Y (1 ~ 8 ) OP T I C AL P O W E R P E R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OAD tributary (1 ~ 8) optical power performance value over threshold

Explanation The OAD tributary (1 ~ 8) optical power is lower than the low optical power threshold or the no optical power threshold.


Board OAD

Possible cause

OAD fault: If the output optical power of the upstream OPA, the laser output optical power of the upstream OTU, and the input and output optical power of other boards are all normal, the OAD tributary (1 ~ 8) optical power performance value over threshold may be caused by the OAD fault or the optical connection fault between the OPA and the OAD.

Upstream fault: If the output optical power performance value of the upstream OPA is lower than the low optical power threshold or the no optical power threshold, then the OAD tributary (1 ~ 8) performance over-threshold may be caued by the OPA fault, or the upstream connection fault of the OPA, or the upstream board fault. In this case, check up to the upstream step by step.

Solution

Check the input optical power of the OAD

If it is consistent with the output optical power of the OPA, then the OAD is faulty. Replace this OAD board.

If it is inconsistent with the output optical power of the OPA, the optical connection between OPA and OAD is faulty. Check carefully the devices such as the flange and the fiber pigtails between the OPA and the OAD, and ensure that there is no extra attenuation caused by the damage or dirt on the coiled fibers and devices.

Check the upstream connection.

Note



T AB L E 50 OBA I N P U T OP T I C AL P O W E R PE R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OBA input optical power performance value over threshold

Explanation The OBA input optical power is lower than the low optical power threshold or the no optical power threshold.


Board OBA

Possible cause

If the total output optical power of the OMU board is less than the low optical power threshold or the no optical power threshold, then the OBA input optical power performance over threshold is caused by the OMU board fault of a upstream fault of the OMU board.

If the total output optical power of the OMU board is normal, the fault lies in the optical connection between the OMU board and the OBA board.

Solution

Upstream fault: First check the input and output optical power of the board step by step up to the upstream via the EMS to locate the fault point, and then check the optical connection at the fault point and verify the optical power.

Optical connection fault between the OMU board and the OBA board: Check the flange and pigtail for the optical connection between the OMU and OBA boards, and make sure that there is no extra attenuation caused by the damage or dirt on the coiled fibers and devices.

Note



T AB L E 51 OBA OU T P U T OP T I C AL P O W E R P E R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OBA output optical power performance value over threshold

Explanation The OBA output optical power is lower than the low optical power threshold or the no optical power threshold.


Board OBA

Possible cause

OBA fault: If the OBA input optical power is normal, while the OBA output optical power performance value is lower than the low optical power threshold or the no optical power threshold, then it can be determined that the OBA board is faulty.

Upstream fault: If the OBA input optical power performance value is also lower than the low optical power threshold or the no optical power threshold, the upstream connection of OBA or the upstream board is faulty. In this case, check step by step up to the upstream.

Solution

For OBA board fault: Replace the OBA board. For upstream fault: First check the input and output optical

power of the board step by step up to the upstream via the EMS to locate the fault point, and then check the optical connection at the fault point and verify the optical power.

Note



T AB L E 52 OPA I N P U T OP T I C AL P O W E R PE R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OPA input optical power performance value over threshold

Explanation The OPA input optical power is lower than the low optical power threshold or the no optical power threshold.


Board OPA

Possible cause

If the upstream OBA or OLA board output optical power is less than the low optical power threshold or the no optical power threshold, the OPA input optical power performance value over threshold is caused by

The fault of OBA or OLA board at the upstream site

The upstream fault of the upstream site of the OPA board

If the upstream OBA or OLA board output optical power is normal, the OPA input optical power performance value over threshold may be caused by

The optical connection or the optical cable fault between the OBA (or OLA) and the ODF at the upstream site

The optical connection fault between the local ODF and the OPA board at the local site

Solution

For upstream fault: First check the input and output optical power of the board step by step up to the upstream via the EMS to locate the fault point, and then check the optical connection at the fault point and verify the optical power.

For connection fault: Check carefully the devices such as the flange and the fiber pigtails between the OBA/OLA and the ODF at the upstream site, and those between the local ODF to the OPA board. Make sure that there is no extra attenuation caused by the damage or dirt on the coiled fibers and devices. Troubleshoot the optical cable line fault with the OTDR.

Note



T AB L E 53 OPA OU T P U T OP T I C AL P O W E R P E R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OPA output optical power performance value over threshold

Explanation The OPA output optical power is lower than the low optical power threshold or the no optical power threshold.


Board OPA

Possible cause

OPA fault: If the OPA input optical power is normal, while the OPA output optical power performance value is lower than the low optical power threshold or the no optical power threshold, this OPA board is faulty.

Upstream fault: If the OPA input optical power performance value is also lower than the low optical power threshold or the no optical power threshold, the upstream connection of the OPA board or the upstream board is faulty. In this case, check step by step up to the upstream.

Solution

OPA board fault: Replace the OPA board. Upstream fault: First check the input and output optical power

of the board step by step up to the upstream via the EMS to locate the fault point, and then check the optical connection at the fault point and verify the optical power.

Note



T AB L E 54 OLA I N P U T OP T I C AL P O W E R PE R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OLA input optical power performance value over threshold

Explanation The OLA input optical power is lower than the the low optical power threshold or the no optical power threshold.


Board OLA

Possible cause

If the upstream OBA or OLA board output optical power is less than the low optical power threshold or the no optical power threshold, the OLA input optical power performance value over threshold is caused by

The fault of OBA or OLA board at the upstream site

The upstream fault of the upstream site of the OPA board

If the upstream OBA or OLA board output optical power is normal, the OLA input optical power performance value over threshold may be caused by

The optical connection or the optical cable fault between the OBA (or OLA) and the ODF at the upstream site

The optical connection fault between the local ODF and the OLA board at the local site

Solution

For upstream fault: First check the input and output optical power of the board step by step up to the upstream via the EMS to locate the fault point, and then check the optical connection at the fault point and verify the optical power.

For connection fault: Check carefully the devices such as the flange and the fiber pigtails between the OBA/OLA and the ODF at the upstream site, and those between the local ODF to the OLA board. Make sure that there is no extra attenuation caused by the damage or dirt on the coiled fibers and devices. Troubleshoot the optical cable line fault with the OTDR.

Note



T AB L E 55 OLA OU T P U T OP T I C AL P O W E R P E R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OLA output optical power performance value over threshold

Explanation The OLA output optical power is lower than the low optical power threshold or the no optical power threshold.


Board OLA

Possible cause

OLA fault: If the OLA input optical power is normal, while the OLA output optical power performance value is lower than the low optical power threshold or the no optical power threshold, this OLA board is faulty.

Upstream fault: If the OLA input optical power performance value is also lower than the low optical power threshold or the no optical power threshold, the upstream connection of the OLA board or the upstream board is faulty. In this case, check step by step up to the upstream.

Solution

OLA board fault: Replace the OLA board. Upstream fault: First check the input and output optical power

of the board step by step up to the upstream via the EMS to locate the fault point, and then check the optical connection at the fault point and verify the optical power.

Note



T AB L E 56 OSC B O AR D D I R E C T I O N A/B I N P U T OP T I C AL P O W E R P E R F O R M AN C E V AL U E OV E R TH R E S H O L D

Item Description

Performance OSC Direction A/B input optical power performance value over threshold

Explanation The direction A/B input optical power of the OSC board is lower than the low optical power threshold or higher than the high optical power threshold.


Board OSC

Possible cause

OSC fault OPA fault OBA fault, OLA fault Optical fiber connecti0on fault Optical cable line fault

Solution

1. Check the upstream main optical channel: Check whether the input/output optical power of the OPA/OLA board in the upstream direction of the local site OSC is over threshold. If it is over-threshold, the upstream main optical channel is faulty. First check the board input and output optical power step by step up to the upstream via the EMS to locate the fault point, and then check the optical connection at the fault point and verify the optical power. If the optical power is normal, the transmitting end of the upstream OSC board or the receiving end of the local OSC board is faulty.

2. Locate the site and the board: If the main optical channel is normal, check whether the optical transmitting of the upstream OSC is normal, and check the optical connection between the upstream OSC and the OBA/OLA board, the optical connection between the local OPA/OLA board and the OSC board, and the input optical power of the local OSC board. Find out the actual cause of the fault, and troubleshoot it.

Note: In the ZXWM M900 equipment, the input and output of the OSC module are connected to the SOUT interface of the OPA board and the SIN interface of the OBA board at the same site.

Note



T AB L E 57 OTU B1 E R R O R P E R F O R M AN C E

Item Description

Performance OTU B1 error (B1 error count, ES count, and SES count are not 0.

Explanation The OTU board detects bit errors (B1 error count, ES count, SES count)

Category Bit error performance

Board OTU

Possible cause

Errors from the SDH equipment OTUT/OTUR fault OMU fault OA fault ODU fault Inter-board fiber connection fault Optical cable line fault

Solution

1. First check whether the bit errors are caused by over-threshold optical power. Monitor the local OTU input optical power and upstream board input/output optical power, and handle any error caused by over-threshold optical power through the operations described above in this section.

2. If there is no optical power over-threshold performance at the upstream, downstream and the local site, check the OTU board in the utmost stream that reports the error. If the board is an OTUT, and is connected with SDH equipment, and there is also B1 error reported from the transmitting port of the SDH equipment, the problem lies in the SDH equipment. Then troubleshoot the fault in the SDH equipment. If there is not B1 error in the SDH equipment, the fault lies in the OTUT. Then replace the OTUT.

3. If the error is reported by the utmost upstream OTUG board, the problem lies in the OTUG board or its upstream OTU. In this case, connect the optical spectrum analyzer to the MON interface of the local site to measure the OSNR of related wavelengths and locate the fault channel. Then replace the fault OTU.

Note



T AB L E 58 OSC D I R E C T I O N A/B E R R O R PE R F O R M AN C E

Item Description

Performance OSC Direction A/B error performance (Background bit error, ES, SES, UAS)

Explanation OSC detects the error or interruption (Background bit error, ES, SES, UAS)

Category Bit error performance

Board OSC

Possible cause

ODU fault OA fault Inter-board fiber connection fault Optical cable line fault

Solution

1. First, check whether the main optical channel is normal. If the input/output optical power performance of the OA board in the main optical channel is over-threshold, handle the fault with the method introduced above.

2. If there is no performance over-threshold alarm reported by the OA, it suggests a problem with the Optical Supervisory Channel (OSC).

Check the optical power launched by the upstream OSC and the optical power received from the OSC by the upstream OBA/OLA. The two power value must be the same. If not, the optical fiber connection between the OSC and the OBA/OLA is faulty.

Check whether the OSC output optical power of the local site OPA/OLA is consistent with that launched by the upstream OSC. If the difference between them is large, the connector of 1550/1510 optical multiplexer of the upstream OBA/OLA is dirty or the device is faulty, or the connector of 1550/1510 optical demultiplexer of the downstream OPA/OLA is dirty or the device is faulty.

Check the received optical power of the local site OSC and the optical power of the sent OSC of the local site OPA/OLA. The two power value must be the same. If not, the optical fiber connection between the OPA/OLA and the OSC is faulty.

3. If there is still bit error after solve all possible causes mentioned above, it suggests a problem with the OSC board. Replace the OSC board and check whether the local OSC board or the upstream OSC board is faulty. Then replace the faulty OSC board.

Note



T AB L E 59 OSC B O AR D D I R E C T I O N A/B O U T -O F -FR AM E C O U N T P E R F O R M AN C E

Item Description

Performance OSC direction A/B out-of-frame count performance

Explanation The signals of the OSC board are out of synchronization.

Category Synchronization performance

Board OSC

Possible cause Inter-board fiber connection fault OSC fault

Solution

Check the received and launched optical power between sites and boards related to supervisory channel (such as OA and OSC), and judge whether the inter-board fiber connection relation is normal.

If there is still out-of-frame performance when all the inter-board connections are normal, the problem lies in the OSC board. Replace the OSC board and check whether the local OSC board or the upstream OSC board is faulty. Then replace the faulty OSC board.

Note



T AB L E 60 TE M P E R AT U R E OV E R -T H R E S H O L D P E R F O R M AN C E

Item Description

Performance Temperature over-threshold performance

Explanation

It occurs when the OTU laser temperature, the pump (1/2) temperature of OBA, the pump (1/2) temperature of OPA, the pump (1/2) temperature of OLA, or the direction A/B temperature of OSC are higher than the temperature upper limit or lower than the low temperature lower limit. The normal operating temperature for all units is 25°C. If the temperature offset is no less than 5°C, both the OTU laser and the OA pump will be automatically disabled for the sake of protection.

Category Temperature performance

Board OTU series board, OBA, OPA, OLA

Possible cause The environment temperature is too high. The fans in the cabinet fail. The board reporting this temperature performance is faulty.

Solution

When the environment temperature is too high, adjust the air conditioning system to keep the temperature in the equipment room in the required range.

If the fans in the cabinet fail, check them and replace them when necessary.

Replace the board reporting the performance if it is confirmed to be faulty.

Note



T AB L E 61 C U R R E N T OV E R T H R E S H O L D PE R F O R M AN C E

Item Description

Performance Current over threshold performance

Explanation

It occurs when the OTU board laser bias current, the OTU board laser cooler current, the OA board EDFA pump bias current, the OA board pump back current value or the OA board EDFA pump cooler current value is greater than the maximum current or less than the minimum current.

Category Current performance

Board OTU series board, OBA, OPA, OLA

Possible cause Problem of settings Board fault

Solution

During the commissioning of the equipment, be sure to record and back up the primitive current data, and correctly set the upper and lower limits of bias current.

If the performance is reported when the upper and lower limits of bias current are correctly set, it suggests the board aging or fault. Replace the board then.

Note





C h a p t e r 5

Alarm Message and Handling

In this chapter, you will learn about: Overview of alarm messages of the ZXWM M900

Causes and troubleshooting of common alarm messages

Overview of Alarm Message Alarm Message Classification The alarm in the ZXWM M900 can be classified into three types: communication alarm, equipment alarm and external environment alarm.

Communication Alarm The communication alarms refer to the alarms influencing the service layer directly, which indicates that the communication signals are interrupted or deteriorated at a certain layer.

Table 62 lists all the communication alarms in the ZXWM M900.

T AB L E 62 AL AR M S I N T H E ZXWM M900 (C O M M U N I C AT I O N AL A R M S )

Board Alarm Remark

1. Service interruption alarm

No output optical power alarm -

Low output optical power alarm -

High output optical power alarm -

No input optical power alarm -

Low input optical power alarm -

High input optical power alarm -

OTU series board

LOS alarm -



Board Alarm Remark

LOF alarm

UAS alarm

Receiving signal MS_AIS alarm

These alarms are detected when the client signals are SDH signals.

OTUk LOF alarm

OTUk loss of multi-frame alarm

OTUk J0 TIM alarm

Only OTUF/OTU10G/OTUE10G board detects these alarms.

Loss of lock alarm Only OTU boards with continuous-rate modules detect the alarm.


Low input optical power alarm - OBA/OPA/OLA/ HOBA



Low output optical power alarm - OBA/OPA/OLA/ HOBA


No total output optical power alarm

Low total output optical power alarm

Only the OMU16/OMU32/OMU40 boards detect these alarms.

No channel input optical power alarm

OMU

Low channel input optical power alarm

Only the OMU8 board detects these alarms.

No total output optical power alarm - VMUX

Low total output optical power alarm -

No total input optical power alarm

Low total input optical power alarm

Only the ODU16/ODU32/ODU40 boards detect these alarms.

No channel output optical power alarm

ODU

Low channel output optical power alarm

Only the ODU8 board detects these alarms.

No add/drop optical power alarm - OAD

Low add/drop optical power alarm -







LOS alarm -

UAS alarm -

SRM41/SRM42/ GEMF

Receiving signal MS_AIS alarm -

Chapter 5 - Alarm Message and Handling


Board Alarm Remark

OTUk LOF alarm

OTUk loss of multi-frame alarm

OTUk J0 TIM alarm

Only the SRM41/GEMF boards detect these alarms.

No MUX output optical power alarm -

Low MUX output optical power alarm -

No DMUX input optical power alarm - OCI

Low DMUX input optical power alarm -



No input optical power alarm - OBM


No output optical power alarm - DGE


LAC No output optical power alarm -

No output optical power alarm - DRA


No working channel input optical power alarm -

Low working channel input optical power alarm -

No protection channel input optical power alarm -

OP

Low protection channel input optical power alarm -

No channel optical power alarm (optical interface 1 ~ optical interface 4) -

Wavelength offset alarm (optical interface 1 ~ optical interface 4) - OPM

OSNR alarm (optical interface 1 ~ optical interface 4) -

No input optical power alarm

Low input optical power alarm

Only the SDMR board detects these alarms.

No output optical power alarm SDM

Low output optical power alarm

Only the SDMT board detects these alarms.

OWM Wavelength offset alarm -

SWE No input optical power alarm -



Board Alarm Remark

2. Service bit error alarm

BE over-threshold alarm

SES over-threshold alarm

UAS over-threshold alarm

B1 error count over-threshold alarm

SD alarm

These alarms are detected when the client signals are SDH signals.

Received error packet ratio over-threshold alarm

8B/10B CV count over-threshold alarm

8B/10B CV second over-threshold alarm

8B/10B severe CV second over-threshold alarm

8B/10B CV UAS over-threshold alarm

These alarms are detected when the client signals are GbE signals.

Before-FEC BE over-threshold alarm

After-FEC BE over-threshold alarm

OTU series board

OTUk BIP8 BE over-threshold alarm

Only the OTUF/OTU10G/OTUE10G boards detect these alarms.

SD alarm -

B1 error count over-threshold alarm -

B2 error count over-threshold alarm -

ES over-threshold alarm -

SES over-threshold alarm -

UAS over-threshold alarm -

Before-FEC BE over-threshold alarm

After-FEC BE over-threshold alarm

OTUk BIP8 BE over-threshold alarm

Only the SRM41/GEMF boards detect these alarms.

SRM41/SRM42/ GEMF

Received error packet ratio over-threshold alarm

Only the GEMF board detects this alarm.

3. Optical supervision interruption alarm

LOS alarm -

UAS alarm Only the OSC board detects the alarm.




No output optical power -

OSC/OSCF

LOF alarm Only the OSC board detects the alarm.



Board Alarm Remark

4. Supervision bit error alarm

ES over-threshold alarm -

SES over-threshold alarm -

UAS over-threshold alarm -

BE count over-threshold alarm -

OSC

SD alarm -

CRC BE block over-threshold alarm - OSCF

Message loss over-threshold alarm -

5. Supervision synchronization alarm

OSC LOF alarm -

6. Others

OTU/SRM/GEM J0 TIM alarm -

CA Loss of clock alrm -

Equipment Alarm The equipment alarms refer to the alarms directly caused by internal fault of the equipment and board. Table 63 lists all the equipment alarms in the ZXWM M900.

T AB L E 63 AL AR M S I N T H E ZXWM M900 (E Q U I P M E N T AL A R M S )

Board Alarm Remark

1. Temperature

Laser temperature offset over-threshold alarm -

Board environment temperature alarm - OTU/SRM/GEM

Inner-module temperature overthreshold alarm

Only the SRM42 board detects this alarm.

OMU/ODU Working temperature over-threshold alarm

Only the OMU/ODU boards with AWG modules detect this alarm.

VMUX Working temperature over-threshold alarm -

Module temperature alarm - DRA

Pump temperature offset alarm -

OWM Board environment temperature alarm -

OBA/OPA/OLA/ HOBA

Environment temperature over-threshold alarm -



Board Alarm Remark

Pump laser working temperature alarm -

EDF temperature offset over-threshold alarm

Only the boards of L band detect this alarm.

SWE Environment temperature over-threshold alarm -

2. Current

Laser current over-threshold alarm - OTU/SRM/GEM

Cooler current over-threshold alarm -

Pump laser bias current over-threshold alarm -

OBA/OPA/OLA/ HOBA/DRA Pump laser TEC current over-threshold

alarm -

OSCF Laser bias current over-threshold alarm -

3. Others

Laser end of lifetime alarm - OTU/SRM/GEM

Laser failure alarm -

OBA/OPA/OLA/HOBA Pump life alarm -

Pump reflection power high alarm - DRA

Pump reflection rate high alarm -

OSCF Laser failure alarm Only 10BASE-FL optical interfaces detect this alarm.

Card dismount alarm - NCP/NCPF

Card mount alarm -

FCB Fan failure alarm -

Environment Alarm The environment alarms refer to the alarms related to the environment of the equipment, such as fire alarm, temperature alarm and equipment room alarm.



Alarm Levels and Severities Alarm levels of the transmission equipment are as the follows:

Communication interruption alarms have higher level than communication bit error alarms.

Communication bit error alarms have higher level than environment alarms.

Alarms can be classified into four severity types: 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 severity in the EMS as required.

Alarm Handling Principle A higher-level alarm will result in lower-level alarms. Therefore, when a fault occurs, it is necessary to handle the higher-level alarm first, and then observe whether the lower-level alarms disappear. If they do not disappear, handle them accordingly; if they disappear, it means they result from the higher-level alarm.

The alarm handling principle is illustrated in Figure 19.

F I G U R E 19 AL AR M H AN D L I N G P R I N C I P L E

Alarms occur

Handling high-levelalarms and observe low-

level alarms

Some low-level alarmsdo not disappear

All low-level alarmsdisappear

Handling low-levelalarms

Alarm handling isfinished



Common Alarm Messages and Solutions This section lists common alarms which may occur in the ZXWM M900 system, and introduces their possible causes and handling procedures in a series of tables (from Table 64 to Table 97) for your reference during the maintenance.

Note: During the maintenance, it is necessary to perform analysis on both the alarm and performance messages for troubleshooting.

T AB L E 64 OTU B O AR D L AS E R N O OU T P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm OTU board laser no output optical power alarm

Alarm severity Critical alarm

Alarm level Alarm of the service interruption category

Explanation The board is faulty and the laser has no output.

Alarm board OTU

Alarm indication

Board: The red alarm indicator glows constantly, and the green running indicator flashes normally and slowly.

EMS: There is a red alarm flag on the board in the Card Management dialog box.

Possible cause

The laser is faulty. The environment temperature is excessively high or the fans of

the equipment fail, so that the laser temperature is also excessively high. The board switches off the laser for protection.

When the APSD function of the OTU board is enabled, if the input port has no input optical power, the board will shut down the laser of the corresponding output port automatically.

Solution

Replace the board Check the heat dissipation of the cabinet. Check whether the APSD function is enabled. If it is enabled,

troubleshoot the no input power fault and then the no output optical power alarm will disappear automatically.

Note



T AB L E 65 TR A N S M I T T I N G -E N D OTU B O AR D N O I N P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm Transmitting-end OTU board (OTUT) no input optical power alarm



Explanation The OTU board at the transmitting end has not received the optical signal sent from client-end equipment, such as SDH equipment

Alarm board Transmitting-end OTU board (such as OTUT, IN1 interface of single-channel bidrectional OTU board, OTUFT)

Alarm indication



Possible cause

Fault occurs in the client-side equipment, and the WDM equipment does not receive any optical signals from the client equipment.

The optical connection between the client equipment and the OTU board in the WDM equipment is interrupted, which suggests a problem with the flange or fiber pigtails.

The optical receiver of the board is damaged.

Solution

Troubleshoot the fault in the client-side equipment. Check the optical connection to locate the faulty device and

replace it to remove the fault. Replace the board if it is confirmed that the optical receiver is

damaged.

Note



T AB L E 66 R E C E I V I N G /R E G E N E R AT I O N -E N D OTU B O AR D OTUG BO A R D N O I N P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm Receiving-end/regeneration-end OTU board (OTUR/OTUG) no input optical power alarm



Explanation The OTU board at the receiving end or regeneration end has not received the optical signal sent from the upstream site.

Alarm board Receiving-end/regeneration-end OTU board (such as OTUR, OTUG, OTUFR and OTUFG)

Alarm indication



Possible cause

The optical connection between the upstream ODU board and the local board fails.

The upstream ODU board is faulty, or the upstream board of site of the ODU board is faulty.

The optical receiver of the OTU board is damaged.

Solution

Check the output optical power of related wavelengths of the ODU board. If the output optical power is normal, the problem lies in the optical connection between the ODU board and the OTU board. Check carefully the devices such as the flange and the fiber pigtails between the ODU and the OTU, and make sure that there is no damage and dirt on the coiled fibers and devices causing service interruption.

If the output optical power is abnormal and it is consistent with the OTU board input optical power, the problem lies in the ODU board or its upstream board or site. Further check towards the upstream until remove the fault.

Replace the board if it is confirmed that the optical receiver is damaged.

Note



T AB L E 67 OTU B O AR D LO W OU T P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm OTU board low output optical power alarm

Alarm severity Major alarm


Explanation The board is faulty and the optical power output by the laser is low.

Alarm board OTU

Alarm indication


EMS: There is an orange alarm flag on the board in the Card Management dialog box.

Possible cause The laser is faulty.

Solution Replace the board

Note



T AB L E 68 TR A N S M I T T I N G -E N D OTU B O AR D LO W I N P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm Transmitting-end OTU board low input optical power alarm



Explanation The optical signal received from the client-side equipment by the transmitting-end OTU is too weak.

Alarm board Transmitting-end OTU board (such as OTUT)

Alarm indication



Possible cause

The client-side equipment is faulty, which causes low output optical power. So the optical signal received by the WDM equipment is low consequently.

The optical connection between the client-side equipment and the OTU board in the WDM equipment, which may be caused by the flange or pigtails between them.

Solution Troubleshoot the fault in the client-side equipment. Check the optical connection to locate the faulty device and

replace it to remove the fault.

Note



T AB L E 69 R E C E I V I N G /R E G E N E R AT I O N -E N D OTU B O AR D LO W I N P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm Receiving-end/regeneration-end OTU board low input optical power alarm



Explanation The optical signal received from the upstream site by the OTU board at the receiving end or regeneration end is too weak.

Alarm board Receiving-end/regeneration-end OTU board (such as OTUG, OTUR, IN2 interface of the OTU10G board and OTU10GG board)

Alarm indication



Possible cause

The optical connection between the upstream ODU board and the local board is faulty.

The upstream ODU board is faulty. The upstream board or site of the ODU board is faulty.

Solution

Check the output optical power of related wavelengths of the ODU board. If the output optical power is normal, the problem lies in the optical connection between the ODU board and the OTU board. Check carefully the devices such as the flange and the fiber pigtails between the ODU and the OTU, and make sure that there is no damage and dirt on the coiled fibers and devices causing service interruption.

If the output optical power is abnormal and it is consistent with the OTU board input optical power, the problem lies in the ODU board or its upstream board or site. Further check towards the upstream until remove the fault.

Note



T AB L E 70 OA B O AR D N O I N P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm OA board no input optical power alarm



Explanation The OA board has not received the optical signal from the upstream.

Alarm board OA

Alarm indication



Possible cause

The upstream board is faulty. The upstream optical cable line is faulty. The fiber pigtails or adaptors connected with the upstream board

are faulty. In case of OPA/OLA board, the optical power is detected after the

input line light has been demultiplexed through the 1550/1510 demultiplexer. Therefore, if the demultiplexer is faulty, the input optical power may not be detected, which results in a no input optical power alarm reported to the EMS.

Solution

Check the upstream board output optical power througth the EMS. If the output end reports no output optical power alarm, it can be judged that the problem lies in the upstream site.

If the output optical power is normal, the fault lies in the optical connection between the upstream board and the OA board. If fiber pigtails are used to connect them, check the fiber pigtails or the adaptor; if an optical cable is used for connection, use an OTDR to locate the fault.

Replace the OPA/OLA board if the 1550/1510 demultiplexer is confirmed damaged.

Note The transceiving fiber pigtail connected to the OA board must be unplugged before using the OTDR, so as to prevent the strong optical power of the OTDR from damaging the optical devices on the board.



T AB L E 71 OA B O AR D LO W I N P U T OP T I C AL P O W E R AL AR M

Item Description

Alarm OA board low input optical power alarm



Explanation The optical signal received from the upstream by the OA board is too weak.

Alarm board OA

Alarm indication



Possible cause

The optical power output by he upstream board is too low. The upstream optical cable line is faulty. The fiber pigtails or adaptors connected with the upstream board

are faulty. In the case of the OPA/OLA board, the cause may be greater

insertion loss of the 1550/1510 demultiplexer.

Solution

Check the upstream board output optical power througth the EMS. If the output end reports low output optical power alarm, it can be judged that the problem lies in the upstream site.

If the output optical power is normal, the fault lies in the optical connection between the upstream board and the OA board. If fiber pigtails are used to connect them, check the fiber pigtails or the adaptor; if an optical cable is used for connection, use an OTDR to locate the fault.

Clean the fiber connectors or replace the OPA/OLA board if the insertion loss of the demultiplexer is too great.




T AB L E 72 OA B O AR D N O OU T P U T OP T I C AL P O W E R AL AR M

Item Description

Alarm OA board no output optical power alarm



Explanation The OA board does not output optical signals to the downstream.

Alarm board OA

Alarm indication



Possible cause

The OA board is faulty. The OA board pump temperature offset is greater than ± 5°C, and

consequently it shut down the pump automatically for protection. The optical power output by the upstream board is too low. The upstream optical cable line is faulty. The fiber pigtails or adaptors connected with the upstream board

are faulty.

Solution

Check whether the input optical power of the OA board is over threshold through the EMS. If not, the OA board is faulty. Replace it. If no input optical power alarm is reported, the problem lies in the upstream board.

Check the output optical power of upstream board through EMS.

If the output optical power is normal, the fault lies in the optical connection between the upstream board and the OA board. If fiber pigtails are used for their connection, check the fiber pigtails or the adaptors; if an optical cable is used, locate the fault via the OTDR.

If the no output optical power alarm is reported, the problem lies in the upstream. Continue locating the fault in the upstream.

Check the heat dissipation and the fans of the cabinet to make sure that the pump temperature of the OA board is normal.




T AB L E 73 O A B O AR D LO W OU T P U T OP T I C AL P O W E R AL AR M

Item Description

Alarm OA board low output optical power alarm



Explanation The optical signal sent to the downstream by the OA board is too weak.

Alarm board OA

Alarm indication



Possible cause

The OA board is faulty. The optical power output by the upstream board is too low. The upstream optical cable line is faulty. The fiber pigtails or adaptors connected with the upstream board

are faulty.

Solution

Check whether the input optical power of the OA board is over threshold through the EMS. If not, the OA board is faulty. Replace it. If no input optical power alarm is reported, the problem lies in the upstream board.

Check the output optical power of upstream board through EMS.

If the output optical power is normal, the fault lies in the optical connection between the upstream board and the OA board. If fiber pigtails are used for their connection, check the fiber pigtails or the adaptors; if an optical cable is used, locate the fault via the OTDR.

If the no output optical power alarm is reported, the problem lies in the upstream. Continue locating the fault in the upstream.




T AB L E 74 OP T I C AL M U L T I P L E X B O AR D N O TO T AL OU T P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm Optical multiplex board no output optical power alarm



Explanation The optical multiplex board does not send the optical signal to the downstream.

Alarm board Optical multiplex board (such as OMU, VMUX, OCI and OBM board)

Alarm indication



Possible cause

The multiplex board is faulty. The upstream board is faulty without optical power output. The fiber pigtails or adaptors between the optical multiplex board

and the upstream board are fualty.

Solution

OMU/VMUX

i. Check the optical power of the upstream OTU board. If no optical power of related wavelength is output by the OTU board, the OTU board is faulty. Replace it then. If the output optical power is normal, the problem may lie in the OMU/VMUX board or the connection between it and the upstream OTU board.

ii. Measure the output optical power of the MON interface on the OMU/VMUX board onsite. If there is output optical power, it can be judged that the OMU/VMUX board is faulty. If there is no output optical power, carry out the step iii as follows.

iii. Check whether the input optical power of each wavelength of the OMU/VMUX board is consistent with the corresponding output optical power of the OTU board. If they are consistent, it can be judged that the OMU/VMUX board is faulty. Or else, check the flange and fiber pigtails between the OMU/VMUX board and the OTU board to locate the faulty devices.



Item Description

OCI

iv. Check the output optical power of the upstream OMU/VMUX board. If no optical power of related wavelength is output by the OMU/VMUX board, troubleshoot the OMU/VMUX fault as described above. If the output optical power is normal, the problem may lie in the OCI board or the connection between it and the upstream OMU/VMUX board.

v. Measure the output optical power of the T-MON interface on the OCI board onsite. If there is output optical power, it can be judged that the OCI board is faulty. If there is no output optical power, carry out the step iii as follows.

vi. Check whether the optical power of input interface for optical signals at the spacing of 100 GHz of the OCI board is consistent with the corresponding output optical power of the OMU/VMUX board. If they are consistent, it can be judged that the OCI board is faulty. Or else, check the flange and fiber pigtails between the OMU/VMUX board and the OCI board to locate the faulty devices.

Solution

OBM

Check the output optical power of the upstream OA board. If no optical power is output by the OA board, troubleshoot the fault following the instruction described in OA board no output optical power alarm. If the output optical power is normal, the problem may lie in the OBM board or the connection between it and the upstream board.

Measure the output optical power of the MON_T interface on the OBM board onsite. If there is output optical power, it can be judged that the OBM board is faulty. Replace it them. If there is no output optical power, carry out the step iii as follows.

vii. Check whether the input optical power of the CT/LT interface on the OBM board is consistent with the corresponding output optical power of the upstream board. If they are consistent, it can be judged that the OBM board is faulty. Replace it then. Or else, check the flange and fiber pigtails between the OBM board and the upstream board to locate the faulty devices.

Note



T AB L E 75 OP T I C AL M U L T I P L E X B O AR D L O W TO T AL OU T P U T OP T I C AL P O W E R AL AR M

Item Description

Alarm Optical multiplex board low output optical power alarm



Explanation The optical signal output by the optical multiplex board is too weak.

Alarm board Optical multiplex board (such as OMU, VMUX, OCI and OBM board)

Alarm indication



Possible cause

The multiplex board is faulty. The upstream board is faulty with low output optical power. The fiber pigtails or adaptors between the optical multiplex board

and the upstream board are fualty.

Solution

OMU/VMUX

i. Check the optical power of the upstream OTU board. If the OTU board output low optical power of related wavelengths, the OTU board is faulty. Replace it then. If the output optical power is normal, the problem may lie in the OMU/VMUX board or the connection between it and the upstream OTU board.

ii. Measure the output optical power of the MON interface on the OMU/VMUX board onsite. If there is output optical power, it can be judged that the OMU/VMUX board is faulty. Replace it then. If the output optical power is low, carry out the step iii as follows.

iii. Check whether the input optical power of each wavelength of the OMU/VMUX board is consistent with the corresponding output optical power of the OTU board.

If they are consistent, it can be judged that the OMU/VMUX board is faulty. Or else, check the flange and fiber pigtails between the OMU/VMUX board and the OTU board to locate the faulty devices.



Item Description

OCI

i. Check the output optical power of the upstream OMU/VMUX board. If the output optical power of related wavelength is low, troubleshoot the OMU/VMUX fault as described above. If the output optical power is normal, the problem may lie in the OCI board or the connection between it and the upstream OMU/VMUX board.

ii. Measure the output optical power of the T-MON interface on the OCI board onsite. If there is output optical power, it can be judged that the OCI board is faulty. If the output optical power is low, carry out the step iii as follows.

iii. Check whether the optical power of input interface for optical signals at the spacing of 100 GHz of the OCI board is consistent with the corresponding output optical power of the OMU/VMUX board. If they are consistent, it can be judged that the OCI board is faulty. Or else, check the flange and fiber pigtails between the OMU/VMUX board and the OCI board to locate the faulty devices.

Solution

OBM

i. Check the output optical power of the upstream OA board. If the output optical power is low, troubleshoot the fault following the instruction described in OA board low output optical power alarm. If the output optical power is normal, the problem may lie in the OBM board or the connection between it and the upstream board.

ii. Measure the output optical power of the MON_T interface on the OBM board onsite. If there is output optical power, it can be judged that the OBM board is faulty. Replace it them. If the output optical power is low, carry out the step iii as follows.

iii. Check whether the input optical power of the CT/LT interface on the OBM board is consistent with the corresponding output optical power of the upstream board. If they are consistent, it can be judged that the OBM board is faulty. Replace it then. Or else, check the flange and fiber pigtails between the OBM board and the upstream board to locate the faulty devices.

Note



T AB L E 76 OP T I C AL D E M U L T I P L E X B O AR D N O TO T AL I N P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm Optical demultiplex board no total input optical power alarm



Explanation The optical demultiplex board has not received the optical signal from the upstream.

Alarm board Optical demultiplex board (such as ODU, OCI and OBM board)

Alarm indication



Possible cause

The upstream board is faulty without output optical power. The fiber pigtails or adaptors in the connection between the optical

demultiplex board and the upstream board are faulty. The optical receiver of the optical demultiplex board is faulty.

Solution

Check the output optical power of the upstream OPA/DRA board.

If the OPA/DRA board reports no output optical power alarm, the problem lies in the upstream OPA/DRA board or its upstream. Continue check the upstream until locate the fault.

If the output optical power of the OPA/DRA board is normal, the problem lies in the connection between the optical demultiplex board and its upstream OPA board. Check the flange and fiber pigtails between the OPA/DRA and the optical demultiplex board to locate the faulty device.

Replace the optical demultiplex board if it is confirmed that its optical receiver is damaged.

Note



T AB L E 77 OP T I C AL D E M U L T I P L E X B O AR D LO W TO T AL I N P U T OP T I C AL P O W E R AL A R M

Item Description

Alarm Optical demultiplex board low total input optical power alarm



Explanation The optical signal received from the upstream by the optical demultiplex board is too weak.

Alarm board Optical demultiplex board (such as ODU, OCI and OBM board)

Alarm indication



Possible cause The upstream board is faulty with low output optical power. The fiber pigtails or adaptors in the connection between the optical

demultiplex board and the upstream board are faulty.

Solution

Check the output optical power of the upstream OPA/DRA board. If the OPA/DRA board reports low output optical power alarm, the

problem lies in the upstream OPA/DRA board or its upstream. Continue check the upstream until locate the fault.

If the output optical power of the OPA/DRA board is normal, the problem lies in the connection between the optical demultiplex board and its upstream OPA board. Check the flange and fiber pigtails between the OPA/DRA and the optical demultiplex board to locate the faulty device.

Note



T AB L E 78 ODU8 B O AR D N O C H AN N E L OU T P U T OP T I C AL P O W E R AL AR M

Item Description

Alarm ODU8 board no channel optical power alarm



Explanation The ODU8 board channel outputs no optical signal to its downstream.

Alarm board ODU8

Alarm indication



Possible cause

The ODU8 board is faulty. The upstream OPA board is faulty without output optical power. The fiber pigtails or adaptors in the connection between the

upstream OPA board and the ODU8 board.

Solution

Check whether the ODU8 board has total input optical power through the EMS. If the optical power is normal, the ODU8 board is faulty. Replace it with a new board. If it reports no total input optical power alarm, it can be judged that the problem lies in the upstream OPA board or the optical connection between it and the ODU8 board.

Check the output optical power of the upstream OPA board via the EMS. If the output optical power is normal, the fault lies in the optical connection between the upstream OPA board and the ODU8 board. Check the fiber pigtails or adaptors to locate the faulty device. If the no output optical power alarm is reported, the problem lies in the upstream. Continue checking the upstream to locate the fault.

Note



T AB L E 79 OTU B O AR D B I T E R R O R OV E R -TH R E S H O L D AL AR M

Item Description

Alarm

B1/B2 error over-threshold alarm: bit error count over-threshlol alarm, ES/SES/UAS overthreshold alarm

8B/10B CV over-threshold alarm: CV count over-threshold alarm, CVS/SCVS/UAS overthreshold alarm

OTUk BIP8 error over-threshold alarm


Alarm level Alarm of the bit error category

Explanation

B1/B2 error over-threshold alarm: When SDH optical signals is accessed to the client end, the OTU board detects bit errors. The OTU/OTUP board can only detect B1 error while the OTUF/OTU10G/OTUE10G can detect both the B1 and B2 error.

8B/10B CV over-threshold alarm: When GbE signals are accessed to the client end, the board detects CV errors.

OTUk BIP8 error over-threshold alarm: When OTN signals are accessed to the client end, the board detect BIP8 errors.

Alarm board OTU

Alarm indication



Possible cause

The transmitting end of the upstream equipment is faulty. The receiving of the upstream OTU board is faulty. The optical connection between the upstream OTU and the local

OTU is faulty. The fault may be caused by OMU/OA/ODU board, optical cable line, fiber connector, adaptor or optical attenuator.

The clock configuration of the client equipment is wrong. For example, the clock is configured into a loop.

Solution

1. Try to locate the faulty segment in regeneration sections one by one. Check the upstream OTU board of a regeneration section and find whether it has error over-threshold alarm too. If yes, further check its upstream; if not, proceed to step 2 as follows.

2. Collect the optical power of every board between two OTU boards in the faulty segment. If the input/output optical power of all board between two OTUs is normal (comparing with the commissioning records), it can be judged that the problem lies in the transmitting or receiving end OTU boards. Locate the faulty board by replace transmitting/receiving end boards one by one with a spare board. And then replace the faulty board when it is found.If there is obvious change in the collected input/output optical power (low optical power alarm) of a board, troubleshoot the fault according to corresponding alarm handling procedures.

3. Check the clock configuration of the client equipment. If it is wrong, reconfigure it.

Note

An electrical regeneration section is located between two adjacent OTUs which transfer the same wavelength. For example, both the OTUT and its adjacent OTUG tranmits the wavelength 1. Then there is an electrical regeneration section between them.



T AB L E 80 LOF AL AR M

Item Description

Alarm LOF alarm



Explanation No signal frame is received from the upstream.

Alarm board OTU/SRM/GEM

Alarm indication



Possible cause

The transmitting end of the upstream equipment is faulty with no frames in the output signals.

The receiving end of the local equipment is faulty. The optical connection between the upstream site and the local

site is faulty which may be caused by the fault of OMU/OA/ODU board, optical cable line, fiber pigtail connector, adaptor or optical attenuator. For example, the attenuation of fibers increases, resulting in too much bit errors, which finally causes the loss of frame alarm.

Solution

Locate the fault between the upstream equipment and the local equipment. Collect the optical power of every board between them. If the input/output optical power of all equipment is normal

(comparing with the commissioning records), it can be judged that the board itself is faulty. Replace it with a spare board.

If the input/output optical power of some boards changes obviously (reporting low optical power alarm), troubleshoot the fault according to corresponding alarm handling procedures.

Note



T AB L E 81 LOS AL A R M

Item Description

Alarm LOS alarm



Explanation No optical signal received from the upstream, that is, no transient between 0 and 1 is detected in the upstream signals.


Alarm indication



Possible cause

The transmitting end of the upstream equipment is faulty with no output signals.

The receiving end of the local equipment is faulty. The optical connection between the upstream site and the local

site is faulty which may be caused by the fault of OMU/OA/ODU board, optical cable line, fiber pigtail connector, adaptor or optical attenuator.

Solution




Note



T AB L E 82 U AS AL A R M

Item Description

Alarm UAS alarm



Explanation Severe fault occur in the received signal which makes the signal unavailable.


Alarm indication



Possible cause

The transmitting end of the upstream equipment is faulty. The receiving end of the local equipment is faulty. The optical connection between the upstream site and the local

site is faulty which may be caused by the fault of OMU/OA/ODU board, optical cable line, fiber pigtail connector, adaptor or optical attenuator.

Solution




Note



T AB L E 83 R E C E I V I N G S I G N AL MS_ AIS AL AR M

Item Description

Alarm Receiving signal MS_AIS alarm



Explanation When SDH signals are accessed to the client end, the MS_AIS alarm from the upstream equipment is received.


Alarm indication



Possible cause The upstream equipment sends the alarm.

Solution Troubleshoot the fault of the upstream equipment.

Note

When the input interface of the upstream equipment is faulty, it usually inserts an MS_AIS alarm in the corresponding downstream output interface automatically, which will be sent to the input interface of the downstream equipment.



T AB L E 84 OTU K LOF AL AR M

Item Description

Alarm OTUk LOF alarm (k = 1, 2)



Explanation The receiving end detects that the OTUk FAS (frame alignment signal) is lost.

Alarm board When k = 1, the alarm board is OTUF/GEMF When k =2, the alarm board is OTU10G/SRM41

Alarm indication



Possible cause The attenuation of the received signal is too great. The traffic output by the upstream site has problems. The receiving end of the board is faulty.

Solution

Check whether the input optical power is normal considering the attenuation.

Check whether the traffic output by the upstream site is normal. Replace the board if it is confirmed the receiving end is damaged.

Note

The OTN is a standard frame structure specified by the ITU-T for the optical transport network, consisting of multi-layer frame format with nested relationship between layers. The OTUk is one layer among them. The OTU1 refers to the frame format and rate of STM-16 added with OTN overheads. The OTU2 refers to the frame format and rate of STM-64 added with OTN overheads.

The OTUk LOF alarm is used to check whether the FAS exists in the OTUk frame. This alarm generally occurs at the receiving port at the line side (aggregate side). If the FEC function of the board is diabled, the OTUk frame will not exist and there is no the OTUk LOF alarm consequently. If OTN traffic is accessed to the client side, this alarm may occur at the receiving port at the client side (tributary side).



T AB L E 85 OTU K LO S S O F M U L T I -FR AM E AL AR M

Item Description

Alarm OTUk loss of multiframe alarm (k = 1, 2)



Explanation The receiving end has not received the expected continuously-counted MFAS byte.


Alarm indication




Solution


Check whether the traffic output by the upstream site is normal. Replace the board if it is confirmed the receiving end is damaged.

Note -



T AB L E 86 OTU K J0 T IM AL AR M

Item Description

Alarm OTUk J0 TIM alarm (k = 1, 2)



Explanation The OTUk SM TTI received at the receiving end is not consistent with the expected value.


Alarm indication



Possible cause

The TTI receiving settings is not correct. The TTI transmitted by the opposite site is wrong. The attenuation of the received signal is too great. The receiving end of the board is faulty.

Solution

Check the TTI receiving settings. Check the TTI settings received from the opposite site. Check whether the input optical power is normal considering the

attenuation. Replace the board if it is confirmed the receiving end is damaged.

Note

The SM TTI is the section overhead trail trace identifier byte at the OTUk layer. It is set and detected in the EMS. The TTI transmitting value is set at the transmit port at the line side of a transmitting board, while the TTI expected value is set at the receive port of the line side of a terminal board or regenerator board. When the received TTI is not consist with the expected value, the OTUk

Only when the equipment receives OTN frames, the alarm may occur. If the OTN function of the board is disabled (such as in the non-FEC mode), this alarm can not occur. At the same time, the TTI transmitting value set at the transmit port of the line side is invalid.



T AB L E 87 OTU K B IP8 E R R O R OV E R -TH R E S H O L D AL A R M

Item Description

Alarm 15-minute OTUk BIP8 error over-threshold alarm (k = 1, 2) 24-hour OTUk BIP8 error over-threshold alarm (k = 1, 2)


Alarm level Alarm of the bit error category

Explanation The SM (section overhead) BIP8 error received by the receiving end exceeds the set threshold.


Alarm indication




Solution


Check whether the upstream site receives BIP8 errors too. If yes, handling the errors of the upstream site first.

Replace the board if it is confirmed the receiving end is damaged. Emergent large-scale errors may be caused by burst line

interferences. Check the line and remove any possible burst interference sources.

Note The SM BIP8 refers to the section overhead BIP8 parity information in the OTUk layer. It functions the same as B1 byte in the SDH overheads.



T AB L E 88 OTU/OTUP B O AR D S I G N AL O U T -O F -LO C K AL A R M

Item Description

Alarm OTU/OTUP signal out-of-lock alarm



Explanation When continuous-rate traffic is accessed to the client side, the OTU/OTUP board fails to extract the clock signal from the received signals, which leads to the loss of clock alarm.

Alarm board OTU/OTUP with continueous-rate traffic

Alarm indication



Possible cause The transmitting of the upstream OTU/OTUP board is inferior. The receiving of local OTU/OTUP board is inferior.

Solution The transmitting end or the receiving end OTU/OTUP board is faulty. Replace it with a spare board.

Note -



T AB L E 89 OSC B O AR D B I T E R R O R AL A R M

Item Description

Alarm

OSC board ES over-threshold alarm OSC board SES over-threshold alarm OSC board UAS over-threshold alarm OSC board error count over-threshold alarm


Alarm level Alarms of the monitoring error category

Explanation The OSC board receives bit errors.

Alarm board OSC

Alarm indication



Possible cause

The OSC board is faulty. The OA board is faulty. The fiber connection is faulty. The optical cable line is faulty.

Solution

Check whether the main optical channel has problems. Compare the input/output optical power of each board in the upstream direction of the OSC board with the commissioning records. If there are related alarms, it can be judged that the alarm is caused by the upstream main optical channel. If there is no alarm, it can be judged that the problem lies in the upstream OSC transmitting end, the local OSC receiving end or the related optical connection.

Check whether the upstream OSC transmits light normally. If it is abnormal, replace the upstream OSC. If it is normal, continue to check the optical connection from the upstream OSC to OBA or OLA, and handle the connection fault if it is abnormal. If it is normal, perform the step 3 as follows.

Check the optical connection from the local site OPA or OLA to OSC towards the downstream. If it is abnormal, handle the connection fault. If the connection is normal, continue to check the input optical power of the local site OSC. If it is normal, replace the local site OSC.

Note



T AB L E 90 OSC B O AR D LOF AL AR M

Item Description

Alarm OSC board LOF alarm


Alarm level Alarms of the monitoring synchronization category

Explanation The OSC board has not received frames.

Alarm board OSC

Alarm indication



Possible cause

The OSC board is faulty. The OA board is faulty. The fiber connection is faulty. The optical cable line is faulty.

Solution

Check the transceiving optical power of boards (OA/OSC) related to the supervisory channel at each site. Judge whether the fiber connections between boards are normal.

If no connection between boards is abnormal, it can be judged that the OSC board is faulty when the LOF alarm still exists. Locate which OSC board is faulty by the method of board replacement. Replace the fautly board with a spare board when it is found.

Note



T AB L E 91 OTU B O AR D H I G H I N P U T OP T I C AL P O W E R AL AR M

Item Description

Alarm OTU board high input optical power alarm


Alarm level Other alarms of the transmission category

Explanation The optical power received by the OTU board from the upstream is too high, beyond the threshold.

Alarm board OTU

Alarm indication



Possible cause The upstream optical power is too high.

Solution

Add attenuator(s) to decrease the input optica power. For the transmitting-end OTU board (such as OTUT), add an appropriate attenuator at the optical port receiving SDH signals. For OTUG and OTUR, add an appropriate attenuator after the OPA board.

Note



T AB L E 92 OTU B O AR D J0 T IM AL A R M

Item Description

Alarm OTU board J0 TIM alarm


Alarm level Other alarms of the transmission category

Explanation

When SDH signals are accessed to the client side, the J0 TTI byte received from the upstream by the OTU board is not consistent with that set at the local end. It usually occurs in the transmitting-end OTU board.

Alarm board OTU

Alarm indication



Possible cause The J0 in the SDH signal frame does not match the J0 set in OTUT

Solution

Modify the J0 byte transmitted by the SDH equipment so that it is consistent with the J0 settings of the OTU board in the WDM equipment.

Modify the J0 settings of the OTU board in the WDM equipment so that it is consistent with the J0 byte transmitted by the SDH equipment.

Note -



T AB L E 93 TE M P E R AT U R E /TE M P E R AT U R E OF F S E T OV E R -TH R E S H O L D AL A R M

Item Description

Alarm OTU/SRM/GEM: temperature offset over-threshold alarm OMU/ODU/VMUX: AWG working temperature over-threshold alarm OA: pump laser working temperature over-threshold alarm


Alarm level Equipment alarms of the temperature category

Explanation

The temperature in the board or device is excessively high. Make sure the temperature for normal running of all devices is 25°C. If the temperature offset ≥ 5°C, the OTU/SRM/GEM laser and the OA pump will be automatically shut down.

Alarm board OTU/SRM/GEM, OMU with AWG multiplexer, ODU with AWG demultiplexer, VMUX, OA, OSC

Alarm indication



Possible cause The environment temperature is too high. The fans in the cabinet are faulty. The board reporting the alarm is faulty.

Solution

When the environment is too high, start the air conditioning system to ensure the temperature in the equipment is within the normal range.

Replace the faulty fan(s). Replace the faulty board.

Note



T AB L E 94 C U R R E N T OV E R -TH R E S H O L D AL AR M

Item Description

Alarm

OTU/SRM/GEM: laser TEC current over-threshold alarm, laser current over-threshold alarm

OA board: pump laser bias current over-threshold alarm, pump laser TEC current over-threshold alarm

OSCF board: laser bias current over-threshold alarm


Alarm level Equipment alarms of the current category

Explanation The bias current and TEC current of the device is too high.

Alarm board OTU/SRM/GEM, OA, OSCF

Alarm indication



Possible cause

The setting of current threshold is unreasonable. The board is faulty. The external power supply has problems.

Solution

Check whether the current thresholds have been correctly set. If not, set the upper/lower threshold correctly based on the original current recorded in the commissioning of the equipment.

If the current threshold has been correctly set, the current over-threshold alarm and laser end of lifetime alarm indicate the board ages or is faulty, replace it with a spare board.

Check the external power supply and make sure the equipment works within the normal power supply range.

Note



T AB L E 95 B O AR D D I S M O U N T AL A R M

Item Description

Alarm Board dismount alarm


Alarm level Other alarms of the equipment category

Explanation In the EMS, a board has been configured in a certain slot. But the EMS does not detect the board in the equipment.

Alarm board NCP/NCPF

Alarm indication EMS: There is a red alarm icon on the NE in the topology. Open the the Card Management dialog box, a black icon is displayed on corresponding slot.

Possible cause

No board is inserted in the slot. The board has been inserted in the slot, but its program does not

run normally and thus the board runs abnormally. The pins corresponding to this board on the backplane are faulty,

or the sockets on the board are faulty, which makes the NCP/NCPF board can not monitor the board.

Solution

Insert and configure a board of the same type configured in the EMS.

Replace the board or the board program. Check if some pins on the backplane are crooked or broken;

replace the backplane or the board.

Note



T AB L E 96 B O AR D M O U N T AL AR M

Item Description

Alarm Board mount alarm


Alarm level Other alarms of the equipment category

Explanation It indicates that no board is inserted in a slot of the equipment, but the EMS detects there is a board in the slot.


Alarm indication EMS: There is a red alarm icon on the NE in the topology. Open the the Card Management dialog box, a black icon is displayed on corresponding slot.

Possible cause In the EMS, a board is inserted in a slot where actually no board has been inserted in the slot of the equipment.

Solution Unplug this board in the EMS.

Note



T AB L E 97 E N V I R O N M E N T MO N I T O R I N G AL AR M

Item Description

Alarm Fire alarm, temperature alarm, equipment room alarm


Alarm level Environment monitoring alarm

Explanation

The NCP/NCPF board can collect environmental information of the equipment room through the ZTE’s environment monitoring system, such as fire and flooding, and then reprot the external alarms via the EMS.


Alarm indication Board: The red alarm indicator glows constantly.

Possible cause The equipment room environment is abnormal.

Solution Go to the equipment room and handle the alarm on site.

Note





C h a p t e r 6

Troubleshooting

In this chapter, you will learn about: Basic principles and general procedures of troubleshooting

Typical approaches and solutions of fault tracing

Causes and solutions of typical faults

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.

Querying 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.



Taking 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.

Troubleshooting Procedures The troubleshooting flow chart is as shown in Figure 20.

F I G U R E 20 TR O U B L E S H O O T I N G P R O C E S S

Request related personnel for troubleshooting

Troubleshooting successful?

No

Troubleshooting successful?

Project maintenance personnel/equipment room maintenance

personnel

Yes

Make a fault record after equipment recovery

Find a fault and an alarm

Equipment room maintenance personnel


Inform local ZTE office of the fault and the alarm

On-call troubleshooting by local ZTE office


Local ZTE office/equipment room maintenance personnel

On-site troubleshooting by local ZTE office


No

Yes

Chapter 6 - Troubleshooting


Basic Considerations for Fault Location Fault Causes The common fault causes include: engineering problems, external causes, improper operations, equipment interconnection problems, and equipment problems.

Engineer ing 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 instead of the equipment itself, which results in equipment fault.

Power failure, such as equipment power failure and too low supply voltage.

Fiber fault, such as fiber performance deterioration, high loss, fiber cut-off, ill contact of fiber connector.

Cable fault, such as relay cable dropped or broken due to ill contact of cable connector.

The equipment is improperly grounded.

The equipment is placed in unsuitable environment.

Improper Operations Improper operations refer to inappropriate operations performed by maintenance staff due to lack of in-depth understanding of equipment, which results in equipment fault.

Improper operation is the most common phenomena while carrying out equipment maintenance, especially in network reconstruction, upgrading, and expansion, where the old and new devices are mixed or old and new versions are mixed. The maintenance staff is usually unaware of the difference between old and new devices or between the old and new versions and tends to trigger off a fault.



Equipment Interconnect ion Problems The ZXWM M900 system is capable of accessing various optical signals The accessed signals are transparently transmitted in the ZXWM M900 system. The interconnection failure may be caused by the characteristics of optical device.

Possible causes for problems in equipment interconnection are as follows:

Improper fiber connection. The common cause during the maintenance is incorrect connection of the optical interfaces.

The problems related to the SDH equipment itself.

Performance deterioration of the OTU, SRM and GEM boards.

Equipment Problems Equipment problems refer to the faults caused by the transmission equipment itself, including equipment damage and inferior cooperation of PCBs. After running for a long time, the PCBs are damaged due to aging factor, which ultimately result in damaged equipment.

The characteristics of equipment problems are: the equipment has been in use for a long time and has been running normally before the fault occurs; and the fault only occurs at certain points/PCBs, or the fault occurs because of external causes.

Principles of Fault Location 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, such as the fiber connection and power supply. 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. While analyzing alarms, consider the higher level alarms first, and then analyze the lower level alarms.



Common Methods of Fault Location 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 the EMS. Observing the status of alarm indicator light on equipment will help to find the fault timely.

When a fault arises, the EMS will record abundant alarm events and performance data. Analyze the information, combine it with the principle of WDM alarms, to determinate fault type and fault location primarily.

While collecting the alarm and performance information through the EMS, make sure to set the current running time of NEs synchronous to the EMS time. Deviation of time setting will result in incorrect or delayed collection of alarm and performance information of NEs.

Instrument Test Method If it is difficult to locate the bit error and find whether it is generated by SDH equipment or WDM system, perform the remote self-loop with fiber pigtails and then use instruments to test the local equipment. The instrument test method is generally used to handle external problems of transmission equipment.

The following sequence is recommended to reduce the negative influence on services during fault location.

1. SDH analyzer

Loop the remote end of the SDH equipment and connect the local end to an SDH analyzer to judge whether the bit error comes from the SDH or the WDM.

2. Optical power meter

Use an optical power meter to accurately measure the optical power of the point.

3. Optical spectrum analyzer

Test the optical interface of the board with an optical spectrum analyzer, read the optical power and SNR from the analyzer. Then compare the data with the original data to find whether there is considerable performance deterioration.



If all services of the main optical channel are affected, focus on the spectrum of OMD and OAD. If only one channel of service of the main channel is affected, focus on the spectrum of the OTU, OMD and OAD.

Caution: A passive board of the ZXWM M900 has an external monitoring optical interface, which should be used for the test to avoid influence on the transmission services of the main optical channel.

Unplugging/Plugging Method After locating fault to a specific board, unplug the board and external interface connector. Plug them back to check ill contacts or abnormal board status.

Caution: Ensure to conform with the operation specifications while plugging/unplugging the board so as to avoid damaging the board or causing 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, access equipment, and power supply device.

2. Check the problem on board after locating the fault to a specific site.

3. Resolve the power 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.

In the upgrading, capacity expansion or 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.

Experience Method At some special occasions (such as transient power supply failure, low voltage or external severe electro-magnetic interference), the equipment board gets into abnormal working status (service interruption or ECC communication interruption). Corresponding alarms may be generated or not. The equipment configuration data is completely normal. Experience tells us that in such cases, we can troubleshoot the fault and recover effectively in time by resetting board, restarting the equipment, and then delivering the configuration data again.

The experience method is unable to find the real causes of faults. Therefore, it is not recommended to use this method unless the fault is emergent. When the maintenance person encounters a fault difficult to be located, he/she should request for technical support from the nearest service office and try to troubleshoot the fault and eliminate the latent risks with the help of ZTE’s technical support engineers.



Handling of Classified Faults The fault of the ZXWM M900 can be classified into communication fault, bit error fault, optical power fault, and equipment interconnection fault.

Note: The communication fault generally refer to the fault causing path interruption or with bit errors. It may exist at both the WDM side and SDH side. The faults described in this section are supposed to occur at the WDM equipment except communication faults.

Communication Fault Possible Cause Communication faults, such as service interruption and bit errors, may be caused by SDH equipment, WDM equipment, or switches.

Troubleshoot ing Procedure The troubleshooting flow is as shown in Figure 21

F I G U R E 21 C O M M U N I C AT I O N F AU L T H AN D L I N G P R O C E S S

A fault occurs

Coordinate with theswitch team tohandle the fault

Switch side

Transmission side

Coordinate with theSDH team to

handle the fault

Carry out the WDM faulthandling process

WDM side

Locate the fault locatingand determine its nature

Locate the fault locatingand determine its nature

SDH side



1. While locating the communication fault point, if there is switch equipment in the equipment room, separate the connection interface between the switch and the transmission equipment should be separated first, so as to judge whether the fault is caused by the switch or the transmission equipment.

2. For the transmission path passing through multiple maintenance offices, coordinate with other maintenance offices to locate the fault point.

3. If a fault is located on the switch side, coordinate with the switch maintenance team to handle the fault; or else locate the fault at the transmission side.

4. Separate the WDM equipment and the SDH equipment connection interface, so as to distinguish whether the fault is a hardware fault with the SDH equipment, the WDM equipment, or the ODF.

i. Enable the standby channel to ensure the normal implementation of current communication services

ii. Locate the fault point in the master channel.

Perform a hardware loop-back on the ODF connecting the SDH and WDM equipment to accurately locate the fault and determine its nature. Then determine whether it is a fault on the SDH side or on the WDM side.

Note: It is recommended to use the instrument test method to locate a fault point, performing the loop-back and connecting the instruments and meters.

5. For the transmission path passing through multiple maintenance offices, coordinate with other maintenance offices to locate the fault point, Repeat step 2 to locate the fault point level by level.

6. If a fault is located on the SDH side, handle the fault in collaboration with the SDH maintenance team; if the fault is located on the WDM side, implement the WDM fault handling process.

Bit Error Problem Possible Cause External causes:

The optical fiber connector is not clean or is not correctly connected.

The optical fiber performance deteriorates and the loss increase.

The equipment is grounded improperly.

There is a strong interference source nearby.

The equipment works in a high temperature environment without proper heat dissipation.

The power supply voltage is not stable and generates surges.



The equipment has been running for a long term with dirt accumulation.

The clock of the client equipment is configured wrongly, such as the clock is looped.

Equipment causes: OTU/SRM/GEM board’s transmission performance deteriorates or other board problems.

Handl ing Method 1. Instrument test method

Locate the fault through a loop-back with the instrument.

2. Observation & analysis method

Exclude the possibility of line errors through analyzing the alarm and performance data of the line.

i. Exclude external causes, such as improper grounding, excessively high working temperature, excessively low or high received optical power.

ii. Check whether the clock of the client equipment is correctly configured. Make sure that the clock is not looped.

iii. Observe bit errors. If all OTU/SRM/GEM boards at a site report bit errors, the fault may be caused by the upstream line or the OA/OMU/ODU board.

iv. If only one OTU board reports bit errors, the fault may be caused by the transmission performance deterioration of OTU/SRM/GEM board of the previous level.

3. Replacement method

If it is confirmed that the fault is caused by a board, replace it with a new one.

Analysis of Common Bit Error Problem Problem: Most channels of the system have bit errors. Large change

of the optical power in short term is found while measuring the output optical power of the ODU board with the optical power meter.

Analysis: In this case, the bit errors are generally caused by the large reflection existing in the system due to too small coiling radius of fiber cables (less than the minimum radius) or dirty optical cables.

Solution:

i. Separate the optical path according to the transmission segment. Use the bit error meter to observe bit errors segment by segment so as to locate the line or node causing the problem.

ii. Use return loss tester to test the reflectance of the faulty optical line and related devices. Generally, the reflectance of optical devices in the system should be less than -40 dB while the line reflectance should be less than -30 dB. If the measured values do not meet the specifications, clean corresponding optical interfaces and connection points between devices.



Optical Power Problem Possible Cause The ZXWM M900 is composed of large amount of optical devices. Abnormal optical power of these devices may result in bit errors in the equipment, or even service interruption.

Abnormal optical power may be caused by:

The transmission performance deterioration of fiber pigtails due to external influence

The optical transmitting module fault of the client equipment

The optical devices performance deterioration of the ZXWM M900

High fiber line attenuation

Handl ing Method The observation and analysis method, instrument test method and replacement method can be used. The operation procedures are as follows:

1. Record the related optical power value and original data. Compare them and find the point where the two values differ greatly.

2. Test the optical power of the point with an optical power meter. Note that the test may affect other services.

3. Check the fiber pigtail on the fault point. Replace it with a new one if it is damaged.

Checkpoint: The coiling radius of fiber should be greater than its minimum turning radius.

4. Observe the status of the indicators of the faulty board, and query the alarm and performance data in the EMS to locate the fault.

i. If the indicator of a board is blacked out while the indicators of other boards are normal, it can be judged that the board is faulty. Replace the board immediately.

Tip: If no spare board of the faulty board is available onsite, just reset the board to relieve the situation temporarily. Usually, the board may restore the service after the reset. However, once a new board is available, the faulty board should be replaced immediately.

ii. If the red and green indicators of the board are flashing alternately, it suggests that the board is waiting for configuration. Inform the EMS maintenance person to download the configuration data again. In the ZXWM M900 system, if a board is in configuration status, the



services will not be affected, although it is not configured at the corresponding location on the EMS. Add the board on the EMS and issue the configuration data to the board, and then the green indicator of the board will flash normally.

iii. If the red indicator of the board glows constantly, it can be judged that the board may have detected an alarm. Confirm the alarm type from the EMS and handling the alarm.

Analysis of Common Bit Error Problem Problem 1:

The gain flatness of main optical working point is not good, and their optical power and SNR varies a lot.

Analysis and Solution:

The possible caused of this problem and corresponding solutions are described as follows:

The output optical power of OTU boards deviate and the central frequencies of these optical channels also deviate. It may be caused by the adjustment of power and wavelength on the OTU boards in the EMS.

Solution: Query the configuration of the OTU boards’ power and wavelength and set their offset to 0.

The insertion loss of some channels in the OMU board is too great.

Solution: Clean the input optical interfaces of corresponding channels of the OMU board.

The gain flatness of some OA boards is bad.

Solution: First use the instrument to test and find the optical amplifier whose gain flatness is bad. Then query its gain configuration on the EMS. If it is found that the gain of this optical amplifier has been adjusted, set it to 0. After that, if the problem does not disappear, replace the board.

Problem 2:

The gain or output optical power of an OA board is wrong.


i. Check whether the APC function of the OA board has been enabled on the EMS.

If the APC function has been enabled, the input of the next-level OA board will be disconnected, and accordingly the previous-level OA board will be in the APR (or APSD) status, which results in the wrong gain of the OA board. After the optical path recovers, the OA board can recover automatically. If it does not, recover it on the EMS manually.

ii. Check whether the gain of the OA board has been adjusted on the EMS. Open the power adjustment dialog box, and check the gain. If the gain has been changed, reset the adjustment value to zero.



iii. Measure the input optical power of the OA board. If the input optical power is greater than the maximum input optical power, the output optical power of the OA board will be saturated. Therefore, the gain is different from the nominal gain. In this case, add a proper attenuator to adjust the input optical power and make it less than the maximum value.

Caution: Please do not use a optical power meter with the maximum measurement value less than 20 dBm to test the optical power. Or else, the calculated gain of the OA board will be wrong and the optical power meter may be damaged.

iv. After all the operations mentioned above, carry out the following measures if the OA board does not recover its normal working yet.

Caution: Be cautious to perform the following operations because services will be interrupted after unplugging the OA board or fibers connected to it.

Clean the optical interfaces of the OA board after unplugging the fibers connected to them. Then plug the fibers back and check whether the optical power is normal.

Check the flange interfaces of the OA board or the 1550/1510 multiplexer/demultiplexer. If they are faulty, replace the board.

Equipment Interconnection Problem Possible Cause Various optical signals can be accessed to the ZXWM M900, which are transparently transmitted in the ZXWM M900 equipment. Unsuccessful interconnection is usually caused by the performance damage of optical devices.

The possible causes of this problem include:

Improper fiber connection, such as common incorrect connection of the optical interfaces during maintenance

Problems of the client equipment itself

Performance deterioration of the OTU/SRM/GEM board

Handl ing Method The observation & analysis method, instrument test method, and replacement method can be used. The specific operations are as follows:

1. Check the fiber labels to find whether the fiber pigtails are connected incorrectly. If any fiber is connected incorrectly, there may be no alarm



of input signal loss, but a lot of abnormal performance values may be generated.

2. Analyze the quantity of the output signals with the optical spectrum analyzer. The signal quality can be improved by raising the output optical power of the opposite OTU/SRM/GEM board.

Checkpoint: During the interconnection between the SDH equipment and the WDM equipment, make sure that the received optical power at both sides be within the specified range.

ECC Fault Possible Cause The ZXWM M900 supports 2 M supervision system and 100 M supervision system.

2 M supervision system: It employs 32 bytes (64 kbit/s) to carry ECC data, orderwire voice data, APS data and transparent user channel data of the system, forwarding and exchanging them in the format of PCM32 frame. The ECC physical layer supports the OSPF protocol, which runs in the NCP/NCPF board and is transferred through the OSC board. Each NCP/NCPF board has four ECC directions.

100 M supervision system: It adopts the 10/100 M Ethernet technology to encapsulate ECC data, orderwire voice data, APS data and transparent user channel data into IP data packets. All these data are transferred and exchanged in the format of Ethernet data frame. The ECC supports the OSPF protocol which runs in the OSCF board.

In the 100 M supervision system, the IP addresses, routes, OSPF configurations (such as area number) related to NEs must be downloaded to the OSCF board through the Agent program of the NCPF board. Each OSCF board provides two ECC optical directions. Multiple ECC directions can be obtained by equipping several OSCF boards in an NE.

In a network consisting of the ZXWM M900, information is transferred between the EMS and the gateway NE with TCP/IP, while the communication between the gateway NE and non-gateway NEs is implemented through ECC, and finally communication between the EMS and non-gateway NEs is implemented.

Possible causes of ECC fault include:

Received and launched optical power is abnormal due to line fiber fault

Power supply failure, such as equipment power failure or too lower power supply voltage

Fault of fibers connected to the OSC/OSCF board, such as fiber performance deterioration, high loss or fiber damage



NCP/NCPF board fault.

OSC/OSCF board fault.

There are a lot of performance data reported by the NE to the EMS, causing the ECC to be blocked.

The configuration on the EMS is wrong.

Handl ing Method The observation & analysis method, instrument test method, and the replacement method can be used. The specific operations are as follows:


i. Analyze the performance data of the OSC board, excluding external causes such as power off, broken fiber or fiber performance deterioration.

ii. Check whether the fiber connection is correct.

iii. Check whether it is caused by board fault. If some devices fail, replace the faulty board.


i. Analyze the performance data of the OSCF board, excluding external causes.

ii. Check whether the OSCF board is normally connected to other boards, and whether the network cable of the EMS is connected correctly.

iii. Check whether the optical interfaces configuration of the OSCF board is correct in the IP address configuration interface on the EMS. If it is incorrect, modify it and reset the board.

iv. Check whether it is caused by board fault. If some devices fail, replace the faulty board.

Orderwire Problem Possible Cause The orderwire of the ZXWM M900 system is processed on the OHP/OHPF board. The E1 and E2 bytes in the supervisory channel are used for the orderwire. The NCP/NCPF board extracts these bytes from the OSC signal and sends them to the OHP/OHPF board for processing.

The possible causes of orderwire problem are as follows:

External causes: power failure, fiber cut-off, and incorrect phone settings.

Improper operation: configuration data error, and calculation error of multi-cast group routes in 100 M supervision system

Equipment causes: NCP/NCPF faults or OHP/OHPF faults



Handl ing Method The orderwire fault can be solved with the observation and analysis method, plugging/unplugging method, replacement method, configuration data analysis method, and the experience method. The specific operations are described as follows:

1. Check the optical channel. If an optical channel is blocked, the orderwire is also unavailable. Check whether there is any alarm with the optical line.

2. Replace the orderwire phone set with a new one, and check whether it is caused by the damaged orderwire phone set.

3. Check the OHP/OHPF board. Observe the indicators and the alarms in the EMS. Check whether the orderwire board gets faulty using the plugging/unplugging method and the replacement method.

4. Check the configuration of the OHP/OHPF board.

5. For a 100 M supervision system, re-calculate the route of multi-cast group in the EMS.

Analysis of Common Orderwire Faul t Symptom 1:

It is unable to make an orderwire call and there is no dial tone in a 2 M supervision system.


i. Check whether there is any alarm of the optical line.

ii. Reset the OHP boards of the caller site or the called site, and the OHP boards between these two sites.

iii. Check whether the fibers at the sites are connected according to the configuration.

iv. Check the orderwire phone sets.

v. Replace the OHP board.

Symptom 2:

The function of calling all orderwire sites can not be implemented.


i. Check whether this function has been configured on the EMS.

ii. If it has been configured, reset the OHP/OHPF board, locate the faulty board, and replace it with a new one.

iii. Check whether the orderwire numbers of the caller site and the called site are correctly set, which can not be the same.



Symptom 3:

There is serious noise in the orderwire call.


i. Check whether the line optical power is normal.

ii. Check whether the fibers connected to the board are normal. If there is any fault, replace the board.

iii. Check if the OHP/OHPF board is normal. If there is any fault, replace the board.

Symptom 4:

The orderwire telephone rings without reason.


This fault often occurs when the actual networking mode is not the same as that in the data configuration, especially in the case of missing optical cables. When all necessary optical cables are connected, this phenomenon disappears automatically.

Symptom 5:

It is unable to make an orderwire call in a 100 M supervision system.


i. Check whether there is any alarm of the optical line.

ii. Reset the OHPF boards of the caller site or the called site, and the OHPF boards between these two sites.

iii. Check whether the fibers at the sites are connected according to the configuration.

iv. Check the orderwire phone sets.

v. Replace the OHPF board.

vi. After the operations mentioned above, if the orderwire function is still not available, re-calculate the route of multi-cast group on the EMS.



Protection Switching Fault Possible Cause External causes: power supply failure, fiber fault such as performance

deterioration and high loss

Improper operations: wrong configurations and incorrect fiber connections

Equipment faults: board fault or blocked supervisory channel

Handling Method It is recommended to locate the fault segment by segment combining with corresponding commands on the EMS so as to minimize the influence on the services in the system.

1. Check and exclude external causes, such as power supply failure and fiber performance deterioration

2. Check whether the EMS configuration and fiber connections are correct

3. Check whether it is caused by board faults

Analysis of Common Protection Switching Fault Symptom 1:

The protection switching can not be performed normally after some faults occur in the system or the EMS sends some external protection command.


i. Check the input/output optical power of the OSC/OSCF board of related nodes on the EMS and judge whether it is caused by the communication problem of the supervision system.

ii. Check the input/output optical power of the OPA board of related nodes on the EMS and judge whether the OPA board is faulty.

iii. Observe the indicators of the board which performs the APS protocol, such as the OPSC board, and check whether the board is running normally. Perform the communication test function of the EMS to check whether the communication between the EMS and the board is normal.

Symptom 2:

When the line is faulty, the corresponding segment implement the protection switching. However, the segment can not recover after the WTR time when the fault has disappeared.


i. Check the input/output optical power of the OSC/OSCF board of related nodes on the EMS and judge whether it is caused by the communication problem of the supervision system.



ii. Check whether a new fault occurs when the system tries to recover. If there is a new fault, send the clear command to the nodes at the end of the segment through the EMS after confirming the optical line has completely restored.

Symptom 3:

When the system is recovering from the protection switching, other new faults occur, which make the system unable to recover.


Send the clear command to the nodes at the end of the segment through the EMS after confirming the optical line has completely restored.

EMS Connection Fault Possible Cause External causes: power supply failure or too lower power supply

voltage, fiber performance deterioration or too high loss.

Improper operation: Configuration errors

Equipment fault: Network card fault of the EMS computer, board fault, and ECC channel block

Handling Method 1. Check external causes, such as power failure and fiber performance

degradation.

2. Check whether the EMS configuration is correct.

3. Adopt the instrument test method to perform self-loop in each segment and locate the faulty NE.

4. Check the board with observation & analysis method.

Analysis of Common EMS Connection Fault Symptom 1:

The EMS computer cannot be connected to the NE via the J9 interface on the OA subrack. The EMS computer can be pinged successfully but the NE can not.


i. Check whether the correct network cable (crossover or straight network cable) is used and whether it works normally.

ii. Check whether the network setting of the EMS computer is correct.

If it is successful to ping itself, it indicates the network card has been correctly installed and the network configuration is effective.



If it is impossible to ping the NE successfully, it indicates that the IP address of the EMS computer and that of the NE are not in the same network segment.

iii. Upload the NE database and check whether the NE and server IP address are consistent with those in the data configuration.

Symptom 2:

The EMS indicates that all boards of a subrack or cabinet are out of position, which then can not be configured.


The ZXWM M900 supports the configuration of multiple cabinets or subracks. Each cabinet and each subrack in the cabinet has a unique identifier. The EMS manages the cabinets/subracks through the identifiers, which are set through the DIP switch on the common interface area of each subrack.

This fault is caused by the incorrect setting of DIP switch on the subrack, which makes the boards unable to communicate with the NCP/NCPF board normally. There subrack numbers in each cabinet are 1, 2 and 3 respectively from the top to bottom. The settings of the DIP switch are listed in Table 98.

T AB L E 98 I L L U S T R AT I O N O F D IP S W I T C H S E T T I N G S

Subrack Cabinet-Subrack No. DIP Switch Identifier DIP Switch Illustration

OTU1 subrack Cabinet 0- Subrack 1 J3

ON

1 2 3 4 5 6 7 8

DIP

Rese

rve

OA subrack Cabinet 0- Subrack 2 J10

ON

1 2 3 4 5 6 7 8

DIP

Rese

rve

OTU2 subrack Cabinet 0- Subrack 3 J3

ON

1 2 3 4 5 6 7 8

DIP

Rese

rve

Note: The pins DIP1 ~ DIP4 of the DIP switch are used to set the cabinet number, which should be the same for the subracks, plug-in boxes and PWSB boards in the same cabinet. Different cabinets should have different numbers.

The pins DIP6 ~ DIP8 of the DIP switch are used to set the subrack number.

The pin DIP5 of the DIP switch is reserved, which can be set to the ON or the opposite position.

Checkpoint: The OA subrack equipped with functional boards such as the NCP and the OSC board should be set as the subrack 2.



DRA Reflection Problem Possible Cause The DRA board of the ZXWM M900 uses line fibers as amplification fibers. The pump output optical power of the DRA board is very high. And the pigtail connection, end surface conditions and the adjacent line fiber conditions are closely related with the amplification.

The main DRA fault is abnormal reflection, which may be caused by

The fiber pigtails transmission performance deterioration due to external influence;

The pigtail end surface is stained or there is a fault with the connection;

The performance deterioration of the optical devices of the ZXWM M900;

The fiber line conditions are degraded, leading to over-threshold reflection.

Handl ing Method The observation & analysis method, instrument test method and the replacement method can be used. The specific operations are as follows:

1. Check the reflectance and the reflection power performance on the EMS, and make sure the reflectance is less than -30 dB as the normal value. If the reflectance is over -30 dB, it is seemed as abnormal. In case of any reflection over-threshold alarm, the pump should be shut off immediately. And then search the cause.

2. Clean all fiber pigtail connectors connected to the IN interfaces of the DRA board, view the pigtail end surface through an optical microscope and ensure that the reflectance is greater than -30 dB. If the end surface is damaged, the fiber pigtail should be replaced.

3. After cleaning, resume the connection, start up the pump, and query the reflection performance. The fault is removed if the reflectance is less than -30 dB.

4. If the fiber pigtails are normal but the board performance is still abnormal, replace the DRA board.

Caution: Be cautious to replace a fiber pigtail or a DRA board, which will interrupt the traffic.



Typical Troubleshooting All Service Blocked Caused by Optical Cable Line Interruption System Overview Suppose there is a backbone transmission network composed of tens of ZXWM M900 equipment (only four of them are shown in Figure 22). The network adopts the chain networking architecture with the transmission rate 2.5 Gbit/s on the ring. As shown in Figure 22, the NE A (site A) is the central office and the EMS is located at the central office.F I G U R E 22 N E T W O R K I N G AR C H I T E C T U R E O F ZXWM M900 S Y S T E M (C A S E 1 )

A B C D

104km 67km 105km

Direction A Direction A Direction A

Direction B Direction B Direction B

Fault Description The site B reports OLA input and output no optical power alarm to

along the direction A; while the direction B is normal. The OSCL reports input optical power over-threshold alarm along the direction A.

The site C has no alarm.

The A-direction OPA board of the site A reports the input and output no optical power alarm; and the ODU report the output no optical power alarm

Fault Analysis and Location 1. Check whether the output optical power of A-direction OBA board in

the site C is normal. If it is abnormal, the OBA board is faulty. If it is normal, check the optical power received from the site C on the ODF in the site B.

2. If the ODF in the site B receives light and the received optical power is normal, the line is normal. If the ODF in the site B receives no light or the difference between the received optical power and the normal power is great, it indicates that the optical line is faulty.

Fault Handling 1. Check the input/output optical power of the OLA board in the site C. If

the optical power is normal, and there is only OSC alarm, it can be judged that the OLA board is normal.



2. We can suspect the fault may be caused by fiber problems. Measure the optical power at the site B. If there is no input light in the direction A, it can be confirmed that the fiber is broken.

3. Perform a test with an OTDR to find out the fault point. Splice the broken fiber and then the alarm disappears and the system recovers with normal data.

Caution: The Optical Time Domain Reflector (OTDR) must be used to handle the fault of the external optical cable lines.

The transceiving fiber pigtail connected to the optical boards must be unplugged after the transceiving interfaces of the optical boards in site B and site C are proved in good condition, so as to prevent the strong optical power of the OTDR from damaging the optical devices on the optical boards.

Train of Thoughts on Fault Location When the service interruption fault occurs, consider the following items to locate the fault:

Separate main optical channel faults from supervision channel faults

Separate the multiple wavelength problems from single wavelength problems.

Bit Error Problem of Main Optical Channel System Overview Suppose there is a backbone transmission network composed of tens of ZXWM M900 equipment (only four of them are shown in Figure 23). The network adopts the chain networking architecture. The transmission rate of each channel is 2.5 Gbit/s. The NE A and NE D compose a multiplex section, with five wavelengths between them (wavelength 1 ~ wavelength 5). The NE A, B, C and D are all OTM sites. The site A and D add/drop services while the site B and C just regenerate service signals.

F I G U R E 23 N E T W O R K I N G AR C H I T E C T U R E O F ZXWM M900 S Y S T E M (C A S E 2 )

A B C D

Direction A Direction A Direction A

Direction B Direction B Direction B

Fault Description Each channel of the NE D reports B1 error.



Fault Analysis and Location 1. Fault Analysis

The bit error fault must be analyzed and handled systematically. First check the upstream and downstream multiplex sections of NE D through the EMS, judging whether it is a single wavelength problem or a multi-wavelength problem, a main optical channel problem or a single channel problem.In this case, all wavelengths of the NE D report B1 error, we can suspect that it is caused by the deterioration of the main optical channel preliminarily for it is rarely that all single-channel hardware becomes faulty at the same time in actual practice.

2. Fault location

i. Check the alarms of each NE one by one on the EMS to find the first NE which reports the main optical channel alarm or perfromace over-threshold alarm.

ii. In the first NE being found, check the current main optical power and compare it with the specification. Locate the fault according to the power difference and the alarm board. The main optical power change may be caused by the abrupt change of optical cable loss and the fiber loss in the subrack, or an abnormal OA board.

iii. After confirming the fault cause of the first site, check the main optical power of downstream sites and exclude other factors which may cause the bit error. If more than one segment has optical cable deterioration or fiber pigtails deterioration in the subrack, check the main optical power of each site till the site D.

Fault Handling According to the analysis and fault location, it is found that the fibers in subrack between the NE C and NE D have great loss which causes the main optical channel deterioration, and finally results in bit errors at the NE D. Replace the faulty fiber pigtails.

Experience Summary Each single-wavelength channel should be checked for bit errors in order to solve the problem thoroughly. It is recommended to use the OPM board or optical spectrum analyzer to check the single-wavelength SNR and waveform at the receiving end of NE D.

Bit Error Problem of Single Channel System Overview Taking the system illustrated in Figure 23 as example. Suppose that the NE A, B, C and D compose a multiplex section. They are all OTM sites. There are five wavelengths between the NE A and NE D (wavelength 1 ~ wavelength 5). The NE A and NE D add/drop services while the NE B and NE C just regenerate service signals.



Fault Descr ipt ion The OTUR of wavelength (channel) 5 at the site D has bit error.

Fault Analysis and Location The bit error fault must be analyzed and handled systematically. First check the upstream and downstream multiplex sections of NE D through the EMS, judging whether it is a single wavelength problem or a multi-wavelength problem, a main optical channel problem or a single channel problem.

1. Check the downstream of the NE D in direction A and the other four wavelengths. If the other four wavelengths have no bit error at the local site and their performances are normal, and the performances of downstream wavelengths are also normal, check the upstream wavelengths in direction A.

2. It is found that only the OTUG5 of the NE B and NE C reports the bit error. In addition, the bit error count is synchronized with that of the NE D. Then we can judge the bit error occurs in the A-direction segment between NE A and NE B.

3. Generally, the bit error problem occurs at the transmitting end. Then check the performance and alarm in NE A and NE B through the EMS. It is found that the optical launched power of NE A is normal and there is no input LOS alarm. The NE B has no LOF alarm. From these, we can judge that the modulation circuit of NE A is normal.

4. Check the input/output optical power of the downstream OMU of NE A. The total output optical power is low through calculation. We can suspect that the input light of the wavelength 5 is weak.

5. Check the NE A and find the input optical power of the OMU corresponding to the wavelength 5 is low.

6. Check the fiber pigtail between the OTU and the OMU, and then we can confirm that the fiber pigtail is faulty, which may be caused by the abrupt change of loss.

Fault Handl ing Replace the fiber pigtail between the OTU and the OMU in NE A.





A p p e n d i x A

NE Address Definition and Route Configuration

This appendix describes how to set the NE IP address and EMS host IP address.

Caution:

While configuring initial information of an NE, the IP address of this NE and the EMS host should be determined and written to the NE’s NCP/NCPF board. It is forbidden to modify the IP address while the equipment is running normally.

The IP address and route information of the EMS computer should be configured correctly in order to ensure the normal communication between the EMS and NEs.

Definition of the NE IP Address Definition and Configuration Principle The ZXWM M900 adopts the OSPF protocol, supporting Classless Inter-Domain Routing (CIDR). The IP address definition of NEs varies in different supervision systems. The definition of the NE IP address is described in Table 99.



T AB L E 99 D E F I N I T I O N O F T H E NE IP AD D R E S S

Item Definition

IP address

Mask

The IP address is used to define the network address of an NE in the format byte1.byte 2.byte 3.byte4 .

Perform AND operation between the IP address and mask to divide the network segment. In a same network, different NEs should be located in different network segment.

In each network segment, a 2 M supervision system should reserve five available addresses at lease while a 100 M supervision system must reserve more than eight available addresses.

Gateway IP address The gateway IP address is used to establish the route between the EMS host and the access NE. It is stored in the NCP/NCPF board.

ECC optical interface address

The ECC optical interface address is used to establish the ECC route between NEs. For detailed information about it, please refer to the section “ECC Optical Interface Address Configuration” in this Appendix.

Area ID

When there are numerous NEs, the network can be divided into several areas to manage NEs. Generally, the number of NEs in an area should not exceed 120.

The area ID format is byte 1.byte 2.byte 3.byte 4 .

T AB L E 100 C O N F I G U R AT I O N P R I N C I P L E O F T H E NE IP AD D R E S S

Configuration Principle Item

2 M Supervision System 100 M Supervision System

IP address No special restriction

Mask

It is recommended to set the mask as 255.255.255.240 to get more available IP address. Its minimum configuration is 255.255.255.248.

It is recommended to set the mask as 255.255.255.224.

When the NE is equipped with two or more OSCF boards, the mask must be greater than or equal to 255.255.255.224.

Gateway IP address

It is recommended to set it as 0.0.0.0 if there is no special requirement.

Set the gateway IP address the same as the IP address of the OSCF board in the access NE if there is no special requirement. IP address of the OSCF board = IP address of the NE + 1.

ECC optical interface address

Refer to the section “ECC Optical Interface Address Configuration” in this Appendix.

Area ID The default area ID is 0.0.0.0 . It can be set without restriction. Please refer to the section “ECC Optical Interface Address Configuration” in this Appendix for detailed configuration procedures.

Appendix A - NE Address Definition and Route Configuration


Configuration Example of the NE IP Address Suppose there is such a network topology, as shown in Figure 24. It is a 2 M supervision system.

F I G U R E 24 N E T W O R K TO P O L O G Y

EMS

1

2

3 4 5

6 7

8 9

10 11

12

Area 1

Area 0(backbone area)

Area 2

1. Area division

Area 1: The NE 1, 2, 3, 4, 5, 6, and 7 are relatively closer to each other and many of them are connected with each other. These NEs compose a topology, which are involved in the area 1.

Area 2: The NE 10, 11 and 12 are relatively closer to each other which compose a ring topology. These three NEs are involved in the area 2.

Area 0: The area 1 and area 2 are connected through the single connection between the NE 8 and NE 9. Therefore, the NE 8 and NE 9 are defined as a backbone area (area 0) connecting other areas.

2. IP address configuration

IP address configuration based on area

Based on the area division describes above, the IP address configuration of these NEs are listed in Table 101. Suppose 16 IP addresses are reserved in each network segment (i.e. set the subnet mask to 255.255.255.240)



T AB L E 101 IP AD D R E S S C O N F I G U R AT I O N O F NE S B AS E D O N AR E A

Area (ID) NE NE IP Address/Mask

NE 1 (access NE) 193.1.1.1/255.255.255.240

NE 2 193.1.2.17/255.255.255.240

NE 3 193.1.2.33/255.255.255.240

NE 4 193.1.2.49/255.255.255.240

NE 5 193.1.2.65/255.255.255.240

NE 6 193.1.2.81/255.255.255.240

Area 1 (0.0.0.1)

NE 7 193.1.2.97/255.255.255.240

NE 10 194.1.9.1/255.255.255.240

NE 11 194.1.9.17/255.255.255.240 Area 2 (0.0.0.2)

NE 12 194.1.9.33/255.255.255.240

NE 8 192.1.7.1/255.255.255.240 Area 0 (0.0.0.0)

NE 9 192.1.7.17/255.255.255.240

Caution: The available IP address number in the network segment where the access NE is located can be increased by modigying the mask of the access NE. In addition, multiple EMS hosts can be accessed to the access NE. Note that this network segment can not influence the network segment of other NEs.

In this example, if you want to reserve 255 host addresses, set the mask of NE 1 to 255.255.255.0 with the mask of other NEs unchanged.

IP address configuration without area division

If all the NEs as shown in Figure 24 are all divided into one area, the IP address configuration is listed in Table 102.

T AB L E 102 IP AD D R E S S C O N F I G U R AT I O N O F NE S I N ON E AR E A

NE NE IP Address/Mask NE NE IP Address/Mask

NE 1 193.1.1.1/255.255.255.240 NE 2 193.1.2.81/255.255.255.240

NE 3 193.1.2.1/255.255.255.240 NE 4 193.1.2.97/255.255.255.240

NE 5 193.1.2.17/255.255.255.240 NE 6 193.1.2.113/255.255.255.240

NE 7 193.1.2.33/255.255.255.240 NE 8 193.1.2.129/255.255.255.240

NE 9 193.1.2.49/255.255.255.240 NE 10 193.1.2.145/255.255.255.240

NE 11 193.1.2.65/255.255.255.240 NE 12 193.1.2.161/255.255.255.240

Caution: Although it is very simple to divide all NEs into one area, the efficiency of ECC route algorithm will be decreased when there are numerous NEs in the area. Therefore, the single-area division mode is only applciable to cases when there are not so many NEs. Generally, the number of NEs in an area should not exceed 120.



ECC Optical Interface Address Configuration In a DWDM system, the ECC optical interface address must be set for the establishment of ECC route between NEs so as to ensure the transmission of supervision information.

Table 103 describes the implementation and number of ECC channels in different supervision systems.

T AB L E 103 R E L AT I O N S H I P B E T W E E N ECC AN D S U P E R V I S I O N SY S T E M

Supervision System Implementation of ECC ECC Optical Direction

(of an NE)

2 M

The HDLC is adopted at the physical layer of ECC. The 2 M supervision system employs PCM32 frame format to forward and exchange ECC data, orderwire voice data, APS data and transparent user channel data between NEs through the optical supervisory channel. The PPP is adopted at the data link layer. Both the OSPF protocol and Agent program run in the NCP/NCPF board.

Each NCP/NCPF board provides four ECC directions (i.e. four optical interfaces).

100 M

The physical layer of ECC adopts the Ethernet technology and supports the OSPF protocol, which runs in the OSCF board. All data related to the NE, such as the IP address, route and OSPF configuration, must be downloaded to the OSCF board through the Agent program of the NCPF board.

Each OSCF board provides two ECC optical directions (i.e. two optical interfaces). Multiple ECC directions can be obtained by equipping several OSCF boards in an NE.

2 M Supervision System In a 2 M supervision system, the addresses of four ECC optical interfaces should be configured. After the IP address of the NE has been confirmed, the ECC optical interfaces addresses can be allocated automatically by the system or configured manually.

Automatic Allocation of Optical Interface Address If the byte 4 of the NE IP address is less than 128, then the IP address

of the optical interface 1 is “byte 4 + 5”, the IP addresses of the other three optical interfaces are “byte 4 + 6”, “byte4 + 7” and “byte 4 + 8” in order. The area ID is 0.0.0.0 by default.

For example, suppose the IP address of an NE is 192.1.1.1. Then the IP addresses of four optical interfaces are as follows:

Optical interface 1: 192.1.1.6






If the byte 4 of the NE IP address is equal to or more than 128, then the IP address of the optical interface 1 is “byte 4 - 5”, the IP addresses of the other three optical interfaces are “byte 4 - 6”, “byte4 - 7” and “byte 4 - 8” in order. The area ID is 0.0.0.0 by default.

For example, suppose the IP address of an NE is 192.1.1.240. Then the IP addresses of four optical interfaces are as follows:





Manual Configuration of Optical Interface Address

Note: When the number of IP address is limited by the user, it is recommended to configure the addresses of optical interfaces manually so as to save the IP address resource.

Use the command ipcfg in the TELNET interface to configure the optical interface address manually. Enter the TELNET interface first according to the instruction described in Appendix B.

Note: In the command line, the normal font represents the information displayed by the system while the Italic font represents the information input by the terminal.

To configure the optical interface address:

Enter the command ipcfg and press the key Enter.

The system returns the information “Input portno 0 or 1” to prompt the user to input the number of port to be configured. Table 104 describes the meaning of the parameter “0” and “1”.



T AB L E 104 D E S C R I P T I O N O F C O N F I G U R AT I O N C O M M AN D S

Parameter Description Remark

0

Only configure the IP address, subnet mask and area ID of optical interface 1. The addresses of other optical interfaces increase based on that of the optical interface 1.

If the NE IP address has not been configured before setting the optical interface IP address, the system will prompt you to configure the NE IP address first.

The address of optical interface 1 should be within the range of 1 ~ 251 and the mask is 255.255.255.255. The IP address of all optical interfaces should be different from the NE IP address.

The configuration of area ID should meet the requirements in Table 99.

The related data in the Agent database will be updated after the NE IP address configuration.

1

Configure the IP address, subnet mask and area ID for five ports manually. Among these ports, port 1 is for the NE itself while port 2 ~ port 4 are for four optical interfaces respectively.

The mask of the NE IP address can not be set as 0.0.0.0 and 255.255.255.255. Set the optical interface IP address as 255.255.255.255.

The IP address of each port should be different.

The configuration of area ID should meet the requirements in Table 99.

The related data in the Agent database will be updated after the NE IP address configuration.

The configuration procedures of optical interface IP address are introduced through three examples as follows.

Configure the IP address of optical interface 1 after the NE IP address has been configured.

ZXONM>ipcfg

// Enter the ipcfg command

Input portno 0 or 1:0

// Enter 0 to configure the address of optical interface 1 only. The addresses of the other optical interfaces will be generated by the system automatically.

Input start optical port IP Address:192.192.40.4

// Input the IP address of the optical interface 1

Input start optical port Subnet Mask:255.255.255.255

// Input the mask of the optical interface 1

Input start optical port AreaId:0.0.0.1

// Input the area ID of the optical interface 1



set_ip_parms succeed, the change will take effect after reset NCP.

// The system displays the successful configuration information and prompt the user to reset the NCP/NCPF board to enable the configuration.

Configure the IP address of the optical interface 1 when the NE IP address has not been configured.

ZXONM>ipcfg

Input portno 0 or 1:0

Net port not cfg, cfg net port first!

// The system prompts the user that the NE IP address has not been configured.

Input net port IP Address:192.192.40.1

// Enter the NE IP address

Input net port Subnet Mask:255.255.255.0

// Enter the NE mask

Input net port AreaId:0.0.0.1

// Enter the NE area ID

Set start optical port parms!

// The system prompts that the optical interface IP address can be configured now.

Input start optical port IP Address:192.192.40.2

Input start optical port Subnet Mask:255.255.255.255

Input start optical port AreaId:0.0.0.1


Configure the NE IP address and the IP addresses of four optical interfaces manually.

ZXONM>ipcfg

Input portno 0 or 1 :1

// Enter 1 to configure five addresses manually

=========================================

// Configure IP address, mask and area ID of Port 1 (NE)

Input Port1 IP Address:192.192.40.1

Input Port1 Subnet Mask:255.255.255.224

Input Port1 AreaId:192.0.0.0

=========================================



// Configure IP address, mask and area ID of Port 2 (optical interface 1)




=========================================





=========================================





=========================================





=========================================


To delete the IP address:

Note: After executing the ipcfg –d command, the address information of all ports will be deleted from the FLASH memory of the board. However, the NE IP address and mask will be reserved in the Agent database.

The function of deleting address of port one by one is not supported.

ZXONM>ipcfg -d

delete_ip_parms succeed, the change will take effect after reset NCP.

// The system displays the successful deletion information and prompt the user to reset the NCP/NCPF board to enable the configuration.



To query the addresses of all ports:

ZXONM>ipcfg –a

// Enter the ipcfg –a command and press the Enter key. If the query operation succeeds, the address information of five ports will be displayed on the screen one by one: Port 1 (NE), Port 2 ~ Port 5 (optical interface 1 ~ optical interface 4).

Port1:

IP Address:0.192.40.1

Subnet Mask:255.255.255.224

AreaId:192.0.0.0

================================

Port2:

IP Address:192.192.40.4

Subnet Mask:255.255.255.255

AreaId:192.0.0.0

================================

Port3:

IP Address:192.192.40.5

Subnet Mask:255.255.255.255

AreaId:192.0.0.0

================================

Port4:

IP Address:192.192.40.6

Subnet Mask:255.255.255.255

AreaId:192.0.0.0

================================

Port5:

IP Address:192.192.40.7

Subnet Mask:255.255.255.255

AreaId:192.0.0.0

================================

get_ip_parms succeed.

If the query operation fails, the following information will appear.

ZXONM>ipcfg -a

get port1 parms failed, not configure or crc error.

// The system displays the possible cause of query failure.



Manual Configuration of Area ID In the TELNET interface, the area ID can be set manually through the interface command. Please refer to Appendix B for how to enter the TELNET interface.

Note: The interface command is used to configure the area ID of each port. The area ID can also be configured with the IP address and mask through the ipconfig command.

Command format: interface port area areaid. The meaning of the parameters port, area, and areaid are explained in Table 105.

T AB L E 105 D E S C R I P T I O N O F P AR AM E T E R S O F I NT E RF AC E C O M M AN D

Parameter Description

port

As a number, it represents the port to be configured with the area ID.

0 : To configure the area ID for all ports

1 : To configure the area ID for the NE

2 ~ 5 : To configure the area ID for the optical interface 1 ~ 4

area As a string, it represents the configuration type of the port. Only the “area” can be configured now.

areaid It represents the area ID in the format of “byte 1.byte 2.byte 3.byte 4”.

For example, suppose the area ID of the NE (Port 1) is 192.192.0.0.

To configure the area ID of the NE:

ZXONM>interface 1 area 192.192.0.0


// The system displays the successful configuration information and prompt the user to reset the NCP/NCPF board to enable the configuration.

Note: The IP address, mask and area ID can only be valid after restting the NCP/NCPF board.



100 M Supervision System In a 100 M supervision system, the optical interface address of the OSCF board is configured through the ZXONM E300 as follows.

1. In the client operation window of the ZXONM E300, select the NE in the 100 M supervision system to be configured.

2. Select the menu Device Config > 100M Route Management > Card IP Configure to pop up the Card IP Address Config dialog box.

3. Configure the IP address, subnet mask and area ID of optical interfaces according to the actual networking based on the configuration principle described in Table 106.

T AB L E 106 C O N F I G U R AT I O N P R I N C I P L E O F OP T I C AL I N T E R F AC E AD D R E S S I N A 100 M S U P E R V I S I O N S Y S T E M

Item Configuration Principle

Optical interface IP address

It can not conflict with other IP addresses in the network.

If optical interfaces of two OSCF boards are connected with fibers, the IP addresses of corresponding interfaces should be set in the same network segment.

For those interfaces of two OSCF board which are not connected with fibers, their IP addresses can not be set in the same network segment. For example, two optical interfaces of the same OSCF board can not be configured in the same segment.

Optical interface mask

The optical interface mask can be configured according to the actual requirements. The default mask is 255.255.255.0. If the optical interface is disabled, the subnet mask should be set as 0.0.0.0.

Area ID Refer to the description in Table 99. The default area ID is 0.0.0.0.

4. After the configuration, reset the OSCF board to enable the IP address.

For example, Figure 25 illustrates a ring network to explain the configuration principle of optical interface IP address in the 100 M supervision system.

As shown in Figure 25, only the optical connections between OSCF boards are displayed.



F I G U R E 25 OP T I C AL I N T E R F AC E IP AD D R E S S C O N F I G U R AT I O N I N A 100 M S U P E R V I S I O N S Y S T E M

OSCFNCPF

OSCF

NCPF

OSCF

NCPF

NE 1

NE 2

NE 3

Optical interface 7:192.1.1.1/255.255.255.0

Optical interface 8:192.1.2.1/255.255.255.0 Optical interface 7:

192.1.2.2/255.255.255.0

Optical interface 8:192.1.3.2/255.255.255



Area ID: 0.0.0.0 (Default)

Definition of the EMS Host Address and Route Configuration To allow the EMS to manage all NEs correctly, the IP address of the EMS and the IP routes over the whole network must be configured properly in the EMS host.

Address Definition and Route Configuration Principle The EMS host address includes IP address, mask and gateway address, as described in Table 107. And Table 108 describes their configuration principle in different supervision systems.

T AB L E 107 D E F I N I T I O N O F EMS H O S T AD D R E S S

Item Description

EMS host IP address It represents the network address of the EMS host in the format: byte 1.byte 2.byte 3.byte 4.

EMS host mask The EMS host mask is used to divide the network segment by performing AND operation with the EMS host IP address.

Gateway address The gateway address is used to establish the route between the EMS host and the access gateway. This address is saved in the EMS host.



T AB L E 108 C O N F I G U R AT I O N P R I N C I P L E O F T H E EMS H O S T AD D R E S S

Configuration Principle Item

2 M Supervision System 100 M Supervision System

EMS host IP address

It should be configured in the same network segment of the access NE.

It can not conflict with the ECC optical interface address and NE address of the NCP/NCPF board.

It should be configured in the same network segment of the access NE.

It can not conflict with the IP addresses of the APSF/NCPF /OHPF/OSCF board.

EMS host mask It is recommended to set the EMS host mask same as that of the access NE.

Gateway address

Configure it as the IP address of the access NE.

Configure it as the IP address of the OSCF board of the access NE. The IP address of the OSCF board is “NE IP address +1”.

Take the network illustrated in Figure 24 as example. Set the addresses of the EMS host as follows.

EMS host IP address: 193.1.1.2

EMS host mask: 255.255.255.240

Gateway address: 193.1.1.1

After setting the EMS host addresses, the route between the EMS host and the access NE is available. Then configure other routes between the EMS host and other NEs.

Route Configuration Two methods are provided on the EMS to configure routes.

Run the OSPF protocol on the EMS host

Advantage: It is unnecessary to configure any route by users.

Disadvantage: There may be some invalid or repeated routes propagated to the network, which make some NEs unreachable or result in too large route tables. The dynamic routes will increase the load of the EMS host.

Note: It is recommended to implement the route configuration by setting static routes or default routes so as to filter large amount of IP packets unrelated to the current network, thus improving the efficiency of the EMS.

Configure default routes or static routes

Default routes or static routes should be pointed to the NE directly connected to the EMS host. In addition, delete other possible repeated routes.



Take the network illustrated in Figure 24 as example. Suppose the EMS software is installed in a Windows operating system. Configure the default route and static routes as follows.

Default route configuration

route add 0.0.0.0 mask 193.1.1.1

The meaning of this route is that all IP packets having no routes on the local must pass through NE 1.

Static route configuration

route add 193.1.0.0 mask 255.255.0.0 193.1.1.1

route add 194.1.0.0 mask 255.255.0.0 193.1.1.1

route add 192.1.0.0 mask 255.255.0.0 193.1.1.1

The meaning of these routes is that all IP packets to be sent to the network 193.1, 194.1 and 192.1 must pass through NE 1.

Common Route Configuration Commands Common route configuration commands are slightly different in a Windows operation system and a UNIX operating system.

In Windows operating system

Table 109 lists common commands in Windows 2000, which are implemented in the cmd interface.

T AB L E 109 C O M M O N N E T W O R K C O N F I G U R AT I O N C O M M AN D S I N W I N D O W S

Network Configuration Command Line

Add the default route route add 0.0.0.0 mask 0.0.0.0 193.1.1.18

Add a route route add 193.1.0.0 mask 255.255.0.0 193.1.1.18

Add a permanent route route add –p 193.1.0.0 mask 255.255.0.0 193.1.1.18

Delete a route route delete 193.1.0.0 mask 255.255.0.0 193.1.1.18

Query the routes route print

Check whether the destination NE can be reached ping 192.1.7.18

Check NEs on the route tracert 192.1.7.18

Note: After restarting the computer, the route added through the “route add” command will be lost. If you want to save a route for a long term, use the “route add –p” command to add it.



In UNIX operating system

In a UNIX operating system, the user can configure routes with command lines or modify the configuration file.

Table 110 lists all common command lines for route configuration.

T AB L E 110 C O M M O N N E T W O R K C O N F I G U R AT I O N C O M M AN D S I N UNIX

Network Configuration Command

Add the default route route add default 193.1.1.18 1

Add a route route add 193.1.0.0 255.255.0.0 193.1.1.18 1（HP-UX）

route add net 193.1.0.0 193.1.1.18 1（Solaris）

Delete a route route delete 193.1.0.0

Query the routes netstat

Check whether the destination NE can be reached ping 192.1.7.18

Check NEs on the route tracertroute 192.1.7.18

Note: After restarting the computer, the route added through command lines will be lost. If you want to save a route for a long term, configure it in the route configuration file.

For different UNIX systems, the position and modification of the rout configuration file are different.

HP-UX platform

In the file editor, modify the netconf file under the directory /etc/rc.config.d. Restart the system after the modification, the configuration in the file will become valid automatically and be saved permanently.

Table 111 lists route configuration commands in the file.

T AB L E 111 N E T W O R K C O N F I G U R AT I O N C O M M AN D I N T H E C O N F I G U R AT I O N F I L E (HP-UX)

Network Configuration Commands in Conguration File

Add the default route

ROUTE_DESTINATION[0]="default" ROUTE_MASK[0]="" ROUTE_GATEWAY[0]= 193.1.1.18 ROUTE_COUNT[0]=1 ROUTE_ARGS[0]= ""

Add a route

ROUTE_DESTINATION[1]=" 193.1.0.0 " ROUTE_MASK[1]=" 255.255.0.0 " ROUTE_GATEWAY[1]= 193.1.1.18 ROUTE_COUNT[1]=1 ROUTE_ARGS[1]=""



Solaris platform

In the file editor, modify the files as listed in Table 112. Restart the system after the modification, the configuration in the files will become valid automatically and be saved permanently.

T AB L E 112 N E T W O R K C O N F I G U R AT I O N C O M M AN D I N T H E C O N F I G U R AT I O N F I L E (S O L A R I S )

Configuration File Function/Format Example

/etc/hosts Configure the IP to be added Format: IP address host name alias

127.0.0.1 localhost loghost 192.192.1.1 hknttserver 192.192.66.1 hknttsdh 168.69.74.35 almftp

/etc/netmasks Set the mask of the added IP address Format: network number subnet mask

192.192.1.0 255.255.255.0 192.192.66.0 255.255.255.0 168.69.74.0 255.255.255.0

/etc/hostname.eri0 Set the main IP Format: host name

hknttserver

/etc/hostname.eri0:x

Set a logic IP. Once add a IP, should a hostname.eri0:x be added (x increases from 0)

Format: host name

Such as define the file /etc/hostname.eri0:1 as hknttsd while define the file /etc/hostname.eri0:2 as almftp

/etc/rc2.d/S96zteRouter

Add a static route. This file will be uploaded while the system starts. S96zteRouter is the file name in which the zteRouter can be defined by users. Avoid using a existing file name under the directory /etc/rc2.d .

Format: route add [host|net] destination gateway

route add net 192.192.0.0 –netmask 255.255.192.0 192.192.1.6 1 route add net 192.192.64.0 –netmask 255.255.192.0 192.192.66.18 1 route add net 168.65.0.0 168.69.74.1 5

/etc/defaultrouter Set the default gateway. Input the IP address directly. -





A p p e n d i x B

Agent Configuration

The appendix introduces the Agent (NCP/NCPF board) configuration of the ZXWM M900, including the definition of DIP switch on NCP/NCPF board, and the local and remote program download procedures.

DIP Switch on NCP/NCPF Board The DIP switch is located on the PCB of the NCP/NCPF board with the identifier S2. It has eight pins which are named DIP1 ~ DIP8 in this manual. Each pin can be switched between the ON position and the opposite position (non-ON).

The definition of various switch status are described in Table 113.

T AB L E 113 D E F I N I T I O N O F D IP SW I T C H O N NCP/NCPF B O AR D

DIP Switch Description NE Status Caution

ON

1 2 3 4 5 6 7 8

DIP

DIP1 ~ DIP 8: non-ON

Application program status (normal working status) The login name and password are admin while running the FTP and TELNET.

ON

1 2 3 4 5 6 7 8

DIP

DIP1 ~ DIP7: non-ON DIP 8: ON

Configuration status The login name and password is null while running the FTP and TELNET.

The change of DIP switch becomes valid only after resetting the board.

ON

1 2 3 4 5 6 7 8

DIP

DIP4: ON DIP8: ON or non-ON Others: non-ON

In the normal working status, the user can print out information through the serial interface (traceMsg output).

Be cautious to use this function for it will influence the system efficiency seriously when there is much debugging information output.



DIP Switch Description NE Status Caution

ON

1 2 3 4 5 6 7 8

DIP

DIP2: ON Others: non-ON

In the normal working status, force the NE IP as 192.192.192.11/255.255.255.0. The login name and password are admin while running the FTP and TELNET.

ON

1 2 3 4 5 6 7 8

DIP

DIP2: ON DIP8: ON Others: non-ON

In the configuration status, force the NE IP as 192.192.192.11/255.255.255.0. The login name and password are null while running the FTP and TELNET.

The IP address of only one NE can be set as 192.192.192.11 in the whole network at the same time.


ON

1 2 3 4 5 6 7 8

DIP

DIP1: ON DIP8: ON

Probe and debugging status


Use of TELNET and FTP Commands There are two methods to run the TELNET and FTP services, depending on whether the IP address of an NE is known:

1. IP address of an NE is known

i. Keep the DIP4 and DIP8 of the DIP switch of the NCP/NCPF board on either position, and set all the other pins of the switch to the non-ON position.

ii. Execute the telnet or ftp command to log in to the NE. Suppose the IP address of the NE is 192.1.1.1. For example, enter the following command.

telnet 129.9.98.98

iii. Press the Enter key. Then input the login name and password on the local computer screen according to the prompt.

Note: When the DIP8 is set to the ON position, the default login name and password is null. When the DIP8 is set to the non-ON position, the default login name and password is admin.

2. IP address of an NE is unknown

i. Set the DIP2 and DIP8 of the DIP switch to the ON position, set the DIP4 to ON or non-ON, and the other pins to non-ON. By this way, the IP address of the NE is set to 192.192.192.11 and the mask to 255.255.255.0 forcibly.

Appendix B - Agent Configuration


ii. Execute the telnet or ftp command to log in to the NE directly. For example, enter the following command line.

telnet 192.192.192.11

Caution: To ensure later supervision on the NE by the EMS, switch the DIP2 of the DIP switch back to the ON position and reset the board after using the forced IP address.

Local NCP/NCPF Reconfiguration Setting the IP address of the NCP/NCPF board to 192.192.192.11 forcibly, the maintenance person downloads the Agent/FPGA program(s) to the board at the location of the equipment and then resets the IP address of the NE. This operation procedure is called local NCP/NCPF reconfiguration.

Note: The NCP board only supports the download of Agent program, while the NCPF board supporst the download of both Agent program and FPGA program.

The NCP/NCPF reconfiguration flow is shown in Figure 26.

FI G U R E 26 LO C A L NCP/NCPF RE C O N F I G U R AT I O N FL O W

Modify the address ofthe NCP board

Download the Agentprogram

Burn the Agent program

Run the Agent program

Prepare before thereconfiguration

Modify the address ofthe NCPF board

Download the Agent/FPGA programs

Burn the Agent/FPGAprograms


Prepare before thereconfiguration

a. NCP board b. NCPF board



Preparing Before the Reconfiguration 1. Check and make sure that the BOOTROM chip on the NCP/NCPF board

is correct. Each kind of NCP/NCPF board can only use the BOOTROM chip special for itself.

2. Switch the DIP2 and DIP8 of the DIP switch on the NCP/NCPF board to the ON position. The DIP4 can be set to either position, and all the other pins of the DIP switch are set to the non-ON position. By this way, the IP address of the NE is set to 192.192.192.11, and the mask to 255.255.255.0 forcibly.

3. Check and make sure the network cable connection between the EMS host and the NE equipment is correct according to Table 114.

T AB L E 114 NE T W O R K C AB L E CO N N E C T I O N F O R LO C AL NCP/NCPF RE C O N F I G U R AT I O N

Supervision System NCP/NCPF Equipment-Side

Interface Network Cable Type

NCP J9 interface of the OA subrack

2 M

NCPF NET interface of the NCPF board

100 M NCPF NET interface of the NCPF board

The EMS host is connected to the equipment directly with a crossover network cable. Or the EMS host is connected to the equipment through a HUB with straight network cables.

4. On the EMS computer, execute the command ping 192.192.192.11 to check and make sure that the EMS can communicate with the NCP/NCPF board.

Downloading the Agent/FPGA Programs (FTP)

To download the Agent/FPGA programs through the FTP:

1. Enter the command ftp 192.192.192.11 to connect the NE, and then input the login name and password. After successful connection, the prompt “ftp>” appears.

2. Input the command bin to set the file transmission mode as binary system.

3. Input the command lcd followed with the path name to convert the path to the directory where the Agent program is located.

4. Input the command send followed with the name of Agent/FPGA program in the host and the file name in the NCP/NCPF board, to send the program to the NCP/NCPF board. If the file name in the NCP/NCPF board is not input, it will use the same name as that of file in the host.

5. Input the command bye to exit from the FTP service.



Note: The extension name of the Agent/FPGA programs must be “bin”.

For example, download the Agent program to an NE as follows:

1. Enter ftp 192.192.192.11 to enter the ftp service. The login name and password is null.

2. After the connection succeeds, the prompt ftp> appears. Execute the following commands to complete file transmission and exit from the FTP service.

ftp>bin

ftp>lcd E:\ //“E:\” indicates the path where the Agent program is located

ftp>send flash.bin a.bin //“flash.bin” is the file name of the Agent program in the host while “a.bin” is the name of the Agent program stored on the NCP/NCPF board

ftp>bye

Modifying the Address of NCP/NCPF Board 1. Enter the command telnet 192.192.192.11, the prompt “ZTE->”

or “ZTE#” appears.

2. Input the command vwc to query the basic data stored in the database of the current NE. The content of query result depends on the version of the NCP/NCPF board.

3. Input the command dbe to clear the original data.

Caution: The command dbe must be in the lower case.

4. Input the command vwc to query the database again and make sure the database has been cleared up.

5. Input the command cfg to configure the basic data once as required.

Note: The items which the system prompt to be configured depend on the version of the NCP/NCPF board. Among these items, the configuration of the NE IP address, subnet mask and area ID should conform the principle described in Appendix A. For other items, there is no special requirement.

Take an NE with the NCPF board as example. Modify the NE IP address into 192.1.12.18 and the mask into 255.255.255.0 with the TELNET



service. The NE is configured in a 2 M supervision system. Execute the following commands:

ZTE#vwc

……

ZTE#dbe

ZTE#vwc

……

ZTE#cfg

Please input ncp config parameter

Board IP Address:192.1.12.18

Board Subnet Mask:255.255.255.0

Board Gateway IP:0.0.0.0

……

ZTE#exit

Note: If there is no special requirements for the gateway in the networking, it is recommended to set the Board Gateway IP same as the address of the OSCF board in a 100 M supervision system. It is recommended to set it same as the NE IP address or to 0.0.0.0 directly.

Burning the Agent/FPGA Programs (TELNET)

To burn the Agent/FPGA programs through the TELNET service:

1. Download the Agent/FPGA programs to the NCP/NCPF board.

2. Execute the telnet command to connect the NE. The prompt “ZTE->” or “ZTE#” appears after successful connection.

3. Use the command prg to burn the Agent/FPGA program.

To burn the Agent program, input the command prg followed by the file name of the Agent program in the NCP/NCPF board.

To burn the FPGA program, input the command prg followed by the file name of the FPGA program in the NCP/NCPF board and the command fpga.

4. Execute the exit command to exit from the TELNET service.



On the basis of the example in the section “Downloading the Agent/FPGA Programs (FTP)”, burn the Agent program to the NE as follows:

1. Execute the command telnet 192.192.192.11 to enter the TELNET mode.

2. After successful connection, the prompt “ZTE#” appears. Execute the following commands to complete the program burning and exit from the TELNET service.

ZTE#prg a.bin //“a.bin” is the file name of the Agent program in the NCP/NCPF board

ZTE#exit

Running the Agent Program 1. Switch all the pins of the DIP switch on the NCP/NCPF board to the

non-ON position and the reset the NCP/NCPF board.

2. The red indicator light and green indicator light of the board flash alternately, indicating the board is initialized.

3. After the initialization, check the status of indicators and perform corresponding operations as follows:

The green indicator flashes slowly and the red indicator is blacked off. It means that the system is running normally.

The green indicator is blacked out while the red indicator flashes slowly. It means that the system is running normally but lack of basic database. The user should download the database through the ZXONM E300, and only after that can the equipment run normally.



Local Download of the Agent/FPGA Programs Local download: setting the IP address of the NCP/NCPF board to 192.192.192.11 forcibly, the maintenance person downloads the Agent/FPGA program(s) to the NE at the location of the equipment.


The operation flow of the local download is shown in Figure 27.

FI G U R E 27 OP E R AT I O N FL O W O F LO C AL DO W N L O AD O F T H E AG E N T /FPGA PR O G R AM S

Download the Agent/FPGA programs

Burn the Agent/FPGAprograms


Prepare before the localdownload

1. Prepare before the local download

i. Check and make sure that the BOOTROM chip on the NCP/NCPF board is correct. Each kind of NCP/NCPF board can only use the BOOTROM chip special for itself.

ii. Switch the DIP2 and DIP8 of the DIP switch on the NCP/NCPF board to the ON position. The DIP4 can be set to either position, and all the other pins of the DIP switch are set to the non-ON position. By this way, the IP address of the NE is set to 192.192.192.11, and the mask to 255.255.255.0 forcibly.

iii. Check and make sure the network cable connection between the EMS host and the NE equipment is correct according to Table 110.

iv. On the EMS computer, execute the command ping 192.192.192.11 to check and make sure that the EMS can communicate with the NCP/NCPF board.

2. Download/burn the Agent/FPGA program and run the Agent program



Remote Online Download of the Agent Program Remote online download: In the case that the NE IP address is known, the maintenance person download the Agent program to the NE through the ECC channel. This mode is usually used in the online upgrade of the EMS software.


The operation flow of the remote online download is shown in

FI G U R E 28 OP E R AT I O N FL O W O F T H E RE M O T E ON L I N E DO W N L O AD O F T H E AG E N T PR O G R AM

Prepare before theremote online download

Download theAgent program

Upgrade theAgent program

Run the Agentprogram

Select the download mode

Download the Agentprogram with the board

software upgrade command

Commond line mode ZXONM E300



Preparing before the Remote Online Download 1. Switch all the pins of the DIP switch on the NCP/NCPF board to the

non-NO position.

2. Check and make sure the network cable between the equipment and the access NE is correctly connected according to the description in Table 115.

T AB L E 115 NE T W O R K CO N N E C T I O N F O R RE M O T E ON L I N E DO W N L O AD

Supervision System NCP/NCPF Equipment-Side

Interface Network Cable

NCP J9 interface of the OA subrack

2 M

NCPF NET interface of the NCPF board

The EMS host is connected to the equipment directly with a crossover network cable. Or the EMS host is connected to the equipment through a HUB with straight network cables.

100 M NCPF Any electrical interface of the OSCF board

The electrical interface can identify the type of network cable automatically.

3. Check and make sure that the fiber connections between NEs are correct.

4. Execute the command “ping NE IP address” and make sure that the ECC channel between the EMS and the NE to be upgraded is normal.

5. Check the version of the Agent program to be downloaded and make sure it is consistent with that in the EMS.

Downloading the Agent Program Through Command Lines The remote online download through command lines includes two procedures: downloading the Agent program and upgrading the Agent program.

Downloading the Agent Program (FTP)

To transfer the Agent program to the board through the FTP service:

1. Use the command ftp to connect the NE. The login name and password is admin. After successful connection, the prompt “ftp>” appears.



2. Enter the command bin to set the file transmission mode as binary system.

3. Enter the command lcd followed by the path name of the Agent program.

4. Input the command send followed with the name of Agent/FPGA program in the host and the file name in the NCP/NCPF board, to send the program to the NCP/NCPF board. If the file name in the NCP/NCPF board is not input, it will use the same name as that of file in the host.

Note: The command send can also be used to download other programs to the board.

5. Input the command bye to exit from the FTP service.

Checkpoint: The extension name of the Agent/FPGA programs stored in the NCP/NCPF board must be “bin”.

For example, download the Agent program to the NE with the IP address 192.1.12.18 as follows:

1. Enter the command ftp 192.1.12.18 to enter the FTP service. The login name and password is admin.

2. After successful connection, the prompt “ftp>” appears. Then execute the following commands to transfer the program file and exit the FTP service.

ftp>bin

ftp>lcd E:\ //“E:\” is the path of the Agent program

ftp>send flash.bin a.bin //“flash.bin” is the file name of the Agent program in the EMS host, while “a.bin” is the file name of the Agent program stored in the NCP/NCPF board.

ftp>bye

Upgrading the Agent Program (TELNET)

To upgrade the Agent program through the TELNET service:

1. Download the new version program file to the NCP/NCPF board according to the instructions described above.

2. Use the telnet command to connect the NE. The login name and password is admin. After successful connection, the prompt “ZXONM->” appears.



3. Enter the command switchworkmode [mcuaddr portno workmode] to switch the board from the working status to the download status. If the command is executed successfully, the system will display the success information; or else, it will prompt the errors.

The parameters mcuaddr, portno and workmode are all displayed in hex system with the “0x” at the head. For example, the meaning of the command switchworkmode 0x203 0x0 0x10 is as follows:

mcuaddr: board address (0x203). The complete representation is 0x000203, where “00” is the rack No., “02” is the subrack No. and “03” is the slot No.

portno: The definition of this parameter varies with different supervision system, as described in Table 116.

T AB L E 116 DE F I N I T I O N O F T H E CO M M AN D P O R T N O

Supervision System Definition of portno

2 M It is 0x0 for all boards

For NCPF board 0x0: to download the Agent program 0x1: to download the 186 program on the NCPF board

For OHPF board 0x0: to download the OHPF application program 0x1: to download other programs which can be upgraded (firmware)

100 M

For other boards, it is 0x0.

workmode: This parameter is different depending on different boards, as described in Table 117.

T AB L E 117 DE F I N I T I O N O F T H E CO M M AN D W O R K M O D E

Board/ProgramType Definition of workmode

0x10 Switch to the working mode (used in normal download)

0x00

Run the new version Agent program after resetting the NCP/NCPF board. (Two latest downloaded Agent programs can be stored in the FLASH memory of the NCP/NCPF board. The new version Agent program refers to the newer one of them.)

NCP/NCPF (not including 186 program)

0x01

Run the old version Agent program after resetting the NCP/NCPF board. (Two latest downloaded Agent programs can be stored in the FLASH memory of the NCP/NCPF board. The old version Agent program refers to the older one of them.)

0x10 Switch to the working mode (used in normal download)Programs of other boards and 186 program of NCP/NCPF board 0x20 Switch to the working mode forcibly (used while set

the board to download status forcibly)



Note: For the NCP/NCPF board, avoid using the parameter “0x00” and “0x01” to force the board to run the Agent program of a certain version unless there is special requirements. After resetting the NCP/NCPF board, run the latest Agent program downloaded.

4. Enter the command updatesoftware mcuaddr portno filename to transfer the *.bin file downloaded in the board through the FTP service. For example, input updatesoftware 0x203 0x0 OA_D5V134.bin, where the OA_D5V134.bin is the file name of the program.

After successful upgrade, the system displays the information “update software succeed”. If the upgrade fails, the system will prompt the errors.

mcuaddr, portno: slot No. and port No. of the board. Their meanings are same as the parameters in the command “switchworkmode” described above.

filename: the file name of the Agent program having been downloaded to the board through the FTP service.

5. Enter the exit command to exit from the TELNET service.

On the basis of the example in the section “Downloading the Agent Program (FTP)”, suppose to upgrade the Agent program of the NE as follows:

1. Enter the command telnet 192.1.12.18 to enter the TELNET mode. The login name and password is admin.

2. After successful connection, the prompt “ZXONM->” appears. Perform the following commands to switch the work mode of the board and upgrade the Agent program.

ZXONM-> switchworkmode 0x208 0x0 0x10

//Switch the work mode of the NCP to the download status

ZXONM-> updatesoftware 0x208 0x0 a.bin

//Download the a.bin file to the NCP board

ZXONM->exit



Downloading the Agent Program through the ZXONM E300 Make sure the ZXONM E300 is normally connected to the NE. Select the menu Maintenance > Card Software Management > Update Card Software to download the Agent program online.

For the detailed operation procedures, please refer to the manual suite of the ZXONM E300.

Running the Agent Program 1. Switch all the pins of the DIP switch on the NCP/NCPF board to the

non-ON position and the reset the NCP/NCPF board.

2. The red indicator light and green indicator light of the board flash alternately, indicating the board is initialized.

3. After the initialization, check the status of indicators and perform corresponding operations as follows:

The green indicator flashes slowly and the red indicator is blacked off. It means that the system is running normally.

The green indicator is blacked out while the red indicator flashes slowly. It means that the system is running normally but lack of basic database. The user should download the database through the ZXONM E300, and only after that can the equipment run normally.



Running Procedures of Blank NCP/NCPF Board A blank NCP/NCPF board refers to a NCP/NCPF board without Agent program. This section introduces the running procedures of a blanck NCP/NCPF board in different supervision systems.


T AB L E 118 RU N N I N G PR O C E D U R E S O F A BL AN K NCP/NCPF BO AR D I N A 2 M SU P E R V I S I O N SY S T E M

Step Description Instruction

1 Switch the DIP2 of the DIP switch on the NCP/NCPF board to the ON position to set the IP address as 192.192.192.11 forcibly.

For the network cable connection, refer to Table 114.

2 Set the IP address, subnet mask and gateway IP address through the TELNET service.

Refer to Appendix A for the configuration description of address.

Refer to the section “Modifying the Address of NCP/NCPF board” in this Appendix.

3 Configure the IP address, subnet mask and area ID (optional) for four ECC channel optical interfaces in the TELNET.

Only when the number of available IP addresses is limited, configure the address and area ID for each optical interface manually. Refer to the section “ECC Optical Interface Address Configuration” in Appendix A for the operation procedures.

4 Download the Agent program to the board through the FTP service.

Refer to the section “Downloading the Agent/FPGA programs (FTP)” in this Appendix.

5 Burning the Agent program through the TELNET service

Refer to the section “Burning the Agent/FPGA programs (TELNET)” in this Appendix.

6 Switch the DIP2 of the DIP switch on the NCP/NCPF board to the non-ON position to reset the board.

-

7 In the ZXONM E300, create an offline NE and install the NCP/NCPF board by click the NCP installation icon.

8 Change the status of the NE from offline to online in the ZXONM E300.

9 Download the basic NE database to the NCP/NCPF board in the ZXONM E300

The IP address/subnet mask set in the ZXONM E300 must be same as those configured through the TELNET service.

These three steps are implemented in the ZXONM E300. Please refer to related manuals of the ZXONM E300 for detailed operation instructions.

10 Observe the status of indicators on the panel of the NCP/NCPF board.

The green indicator flashes slowly and the red indicator is blacked out, which means the operation finishes successfully.




T AB L E 119 RU N N I N G PR O C E D U R E S O F A BL AN K NCPF BO AR D I N A 100 M SU P E R V I S I O N SY S T E M

Step Description Instruction

1

Switch the DIP2 of the DIP switch on the NCP/NCPF board to the ON position to set the IP address as 192.192.192.11 forcibly.

Connect the EMS with the equipment (NET interface of the NCPF board) with a network cable.

2 Set the IP address, subnet mask and gateway IP address of the NCPF board through the TELNET service.

Refer to Appendix A for the configuration description of address.

Refer to the section “Modifying the Address of NCP/NCPF board” in this Appendix.

3 Download the Agent program to the board through the FTP service.

Refer to the section “Downloading the Agent/FPGA programs (FTP)” in this Appendix.

4 Burning the Agent program through the TELNET service

Refer to the section “Burning the Agent/FPGA programs (TELNET)” in this Appendix.

5 Switch the DIP2 of the DIP switch on the NCP/NCPF board to the non-ON position to reset the board.

Connect the EMS and the equipment (an idle electrical interface of the OSCF board) with a network cable.

Connect an idle electrical interface of the OSCF board with the NET interface of the NCPF board.

6 In the ZXONM E300, create an offline NE and install the NCPF board by click the NCP installation icon.

7 Change the status of the NE from offline to online in the ZXONM E300.

8 Download the basic NE database to the NCPF board in the ZXONM E300

9 Set the IP address, mask and area ID for two optical interfaces of the OSCF board

The IP address/subnet mask set in the ZXONM E300 must be same as those configured through the TELNET service.

Refer to the section “ECC Optical Interface Address Configuration” in Appendix A for the configuration requirements of the optical interface address of the OSCF board.

These four steps are implemented in the ZXONM E300. Please refer to related manuals of the ZXONM E300 for detailed operation instructions.

10 Reset the OSCF board -

11 Observe the status of indicators on the panel of the NCPF board.

The green indicator flashes slowly and the red indicator is blacked out, which means the operation finishes successfully.


A p p e n d i x C

Common Maintenance Forms

This appendix presents some forms used for routine maintenance as reference, for the users.

Half-day Maintenance Record T AB L E 120 HAL F -D AY M AI N T E N AN C E RE C O R D FO R M

Maintenance Item Result for Reference Check Result

In normal running, the green board indicator flashes slowly and regularly

(Record “Normal” when there is no alarm, and record the detailed alarm indicator status if any alarm occurs. For service boards, the slot number of the alarm board must be recorded)

OTU board

The red indicator is on when a board alarm occurs.


ODU board The red indicator is on when a board alarm occurs.


OMU board The red indicator is on when a board alarm occurs.


OPA board The red indicator is on when a board alarm occurs.


Board indicators observation

OBA board The red indicator is on when a board alarm occurs.



Maintenance Item Result for Reference Check Result


OAD board The red indicator is on when a board alarm occurs.


OPM board The red indicator is on when a board alarm occurs.


OSC board The red indicator is on when a board alarm occurs.


OHP board The red indicator is on when a board alarm occurs.


NCP board The red indicator is on when a board alarm occurs.


SDM board The red indicator is on when a board alarm occurs.

Summary of the board indicator status (Summing up the indicator status in this period) and recording the troubleshooting details.

Tested by: Check time:

Note: As the boards configured in different sites are different, the table should be made depending on the actual conditions.

Appendix C - Common Maintenance Forms


Daily Maintenance Record T AB L E 121 DAI L Y M AI N T E N AN C E RE C O R D FO R M

Maintenance Item Maintenance Content Result for Reference Check Result

The green indicator is always on in normal status

Cabinet indicator

Status of indicator on the cabinet or alarm indicator board With an alarm, the red indicator is

always on

Ring trip switch location In “NORMAL” for normal status

The buzzer does not sound when there is no alarm Alarm sound Whether the buzzer

sounds in “NORMAL” status The buzzer sounds when there is an

alarm

Power test Cabinet indicator status

If no NM system is accessed, the indicator will flash with red and green in turn; if an NM system is accessed, the indicator slowly flashes in green

Fan check The fan runs normally or not

In case of normal running, there is a light “buzz” sound

Equipment room temperature: 5°C ~ +45°C

Equipment room humidity: 10% ~ 90%

The air-conditioning system operates normally

Equipment test item

Equipment room environment inspection

Whether suitable for the equipment to work

There is no rodent or pest

Whether logon is normal Clients may normally logon the servers

NM connection Whether the NE is online, and whether the communication is normal

NCP time can be queried via a “Time management” command

Warning alarm, and NE icon in purple

(The meaning of an NE icon status will depend on the NM version that is being run)

Minor alarm, and NE icon in yellow

Major alarm, and NE icon in orange

NE working state

Critical alarm, and NE icon in red

Normally, the connection line is a real line

NM

test item

Topology map monitoring

Optical connection stateWhen there is a fault with the fiber, the connection line is dashed line



Maintenance Item Maintenance Content Result for Reference Check Result

Check the alarm setting Alarms cannot be shielded in a normal case

A warning alarm is a purple icon

The minor alarm is a yellow icon

A major alarm is a orange icon

Alarm monitoring

Query the alarm state

A critical alarm is shown in a red icon

Query the performance during the current 15 minutes and 24 hours

Normally the performance value is 0

Performance monitoring Query the performance

during historic 15 minutes and 24 hours

Summary of maintenance (Summing up the equipment and NM status in this period and recording whether the faults have been cleared. If the faults have been solved, the troubleshooting methods should also be recorded to provide basis for future maintenance work.) Tested by Check time

Note: As there may be no NM configured on some sites, the table should be made depending on the actual conditions.

Appendix C - Common Maintenance Forms


Weekly Maintenance Record T AB L E 122 WE E K L Y M AI N T E N AN C E RE C O R D FO R M

Maintenance Item Maintenance Content Check Result Note

Checking the services

It is recommended that the test should be performed via the NM system, with 0 error as normal

(Recording the tested BER)

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 order-wire telephones of all the sites in the subnet to test the order-wire voice quality, while an ordinary site only needs to dial the central site for test



Login Password Change Record T AB L E 123 LO G I N P AS S W O R D CH AN G E R E C O R D

The Last Change date

The Present Change Date

Recorded Into the Memorandum or Not

Changed By

Checked By

Check Date

Note: The login password should be changed once a month. The table can be changed depending on the actual conditions.

Note: For irregular check of the system configuration, user operation log, report printing, and data backup, the maintenance table could be made based on the above tables.


A p p e n d i x 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 Plugging a Board 1. First, make sure the slot is right to which the board is inserted. If there

is a dummy panel blocking the sight, dismount it. Mount it back after the board is plugged.

2. Press down the spring piece of the lever, and place the lever to a horizontal place.

3. Hold the upper and lower levers with both your hands to push the board along the rail until it is in a floating status. Be careful to keep the board vertical while pushing it inward with moderate force.

Note: The board floating state means the board is already in the slot and is sliding toward the slot bottom along the guide rail, but the board connectors has not been connected with the motherboard sockets. Actually, the board has not been plugged completely.

4. When the board is completely pushed into the subrack, make the bayonet on the lever clip the front beam of the subrack, and push the board levers downward and upward respectively till the levers stand and the board clicks to place.

5. When finished, the board panel should be aligned with the outward frame of the subrack board area, as shown in Figure 29.



FI G U R E 29 SC H E M AT I C D I AG R AM O F BO AR D IN S E R T I O N OP E R A T I O N

1. Subrack 2. Board 3. Guide rail 4. Lever

Unplugging a Board 1. If there are fibers or cables connected to the board on the panel,

unplug them first.

2. Hold the upper and lower levers with both hands, press the spring pieces and move the levers upward and downward with appropriate force to free the board from the slot.

3. Pinch the board lever with one hand’s thumb and forefinger and hold the board panel with the other hand to pull the board smoothly out of the slot.

Precautions in Board Operation Since there are many CMOS devices in boards, be sure to put on the

anti-static wrist strap to connect the human body with the equipment protection ground before touching the board. If the equipment to be installed or maintained has not been connected with the protection ground, the anti-static wrist strap cannot take effect and another effective anti-static approach is necessary.

There is normally a bag of desiccant in the static-shielding bag, which is used to absorb the moisture in the bag and keep the bag inside dry. When the board is carried from a dry place with low temperature to another moist place with higher temperature, do not open the bag and begin the installation until 30 minutes later. Otherwise, moisture will condense on the board surface, resulting in board damage.

While plugging the board, keep the board upright with proper force to avoid bending the contact pins. While plugging the optical interface board, pay special attention not to damage the optical interface and the fibers in the board.

Appendix D - Board Replacement


General Flow of Board Replacement Make sure to consider the following issues before replacing a board:

The function of the board in a network and an NE

The effect on the service after the board is unplugged

The compatibility between the spare board version and the current equipment and EMS

Figure 30 shows the general flow of the board replacement operation.

FI G U R E 30 GE N E R AL FL O W O F BO AR D RE P L AC E M E N T

Start

Unplug the faulty board

Service interruption

Service switching

Plug the spare board

Attach a label on the faulty board

N

Y

Prepare a spare board

Prepare a label

End

TroubleshootingAbnormal

Normal

Restore service

Is the faulty boardunder protection?

Check working status



1. Preparing the spare board

To ensure normal working of the system after the board replacement, pay attention to the following precautions when 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 can work normally.

Make sure that the PCB version and software version of the spare board are compatible with the current NE and EMS.

2. Preparing the label

The label is used to identify the board that has been unplugged in replacement. The label size is decided by the maintenance person. The label contents include the site name, equipment name, fault cause, board name, handling process, the handling person, and time.

3. Switching the service

For the board configured with service protection or backup, the service function processed by it should be switched to the standby board for processing, so that the service will not be interrupted by board unplugging.

While unplugging the board without service protection or backup, the service function of this board will be disabled, which should be explained to the user before unplugging, and any possible measure should be taken to minimize the bad effect resulting from service interruption.

4. Unplugging the board

Warning: Board unplugging operation may interrupt the service, or even stop working of the whole NE. Be sure to make enough preparations before the operation and take any possible measure to minimize the bad effect resulting from service interruption.

Before unplugging the board, unplug the fiber pigtail connected on the board panel. Refer to Unplugging the Board for description of the board unplugging operation.

5. Sticking the label

Stick the prepared label on the PCB of the board after the board is unplugged.

6. Plugging the spare board

Plug and install the standby board in the equipment, and resume connection of the fiber pigtail on the board panel. Refer to the section “Plugging a Board” in this Appendix for description of the board plugging operation.

Appendix D - Board Replacement


7. Recovering the service function

After the spare board is installed in the equipment, the service function of this board should be recovered immediately. Check the working status of the board and the equipment, make sure the equipment works normally and the service function is normal. Otherwise, do troubleshooting till the equipment work and service functions become normal.





A p p e n d i x E

Common Instruments and Meters

This appendix introduces the meters (including the optical power meter, 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 Optic Power Meter Brief Function Description Figure 31 shows the outside view of the PMS-1A optic power meter.

FI G U R E 31 OU T S I D E V I E W O F T H E PMS-1A OP T I C PO W E R ME T E R



The PMS-1A optic power meter mainly serves to measure the continuous optical signal power, employing 4-digit LCD. It is capable of automatic measurement range switching, automatic power-off, automatic reset zero, multi-wavelength measurement and relative power measurement, etc. The specification of the PMS-1A is listed in Table 124.

T AB L E 124 SP E C I F I C AT I O N O F T H E PMS-1A OP T I C PO W E R ME T E R

Item Specification

Working wavelength 1300 nm, 1310 nm, 1480 nm or 1550 nm

Measurement range -40 dBm ~ +20 dBm (0.1 nW ~ 100 mW)

Measurement accuracy ±5%

Detector interface type FC

Panel Description Figure 32 shows the panel of the PMS-1A fiber optic power meter.

FI G U R E 32 P AN E L O F T H E PMS-1A OP T I C PO W E R ME T E R

WATT unit selectionbutton

Wavelength selectionbutton

CLEAR button Power switch

LCD

Relative measurementstatus switchover key

Detector interface

Socket for externalpower supply

dBm unit selectionbutton

Appendix E - Common Instruments and Meters


Operation Flow Figure 33 shows the operation flow of measurement via the PMS-1A optic power meter, together with the specific operation in each step.

FI G U R E 33 OP E R AT I O N FL O W O F ME AS U R E M E N T V I A T H E PMS-1A OP T I C PO W E R ME T E R

Press λ to select wavelength

Relative power measurement

Absolute power measurement

Press WATT

Select unit

Select unit

Press dBrel to enter relative

measurement state

WATT

dBm

Press dBm

Press WATT

WATT

dBm

Press dBm

Read measurement results

Press CLEAR to clear all digits

Connect optical source to be tested with

optical power meter

Select measurement

mode

Press ON/OFF to power on optic power

meter

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 1510 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 34 shows the appearance of the ALL-11 chip burner.

FI G U R E 34 AP P E AR AN C E O F AN ALL-11 CH I P BU R N E R

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 35 shows the panel of the ALL-11 chip burner.

FI G U R E 35 P AN E L O F AN ALL-11 CH I P BU R N E R

Power switch

BUSYGOOD YES

Power socket

Communication port

Power indicator

40-pin socket

YES shortcut key

Success indicator

Working indicator

Memory extension slot

The 40-pin socket definition is shown in Figure 36.

FI G U R E 36 SE C T I O N AL V I E W O F 40-P I N SO C K E T

Extractor leverSocket

Jack

Chip insertion guide



Operation Flow Figure 37 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.

FI G U R E 37 OP E R AT I O N FL O W O F ALL-11 CH I P BU R N E R

Select a chip manufacturer

Select source of chip contents

Power on chip burner and start the burning software WACCESS

Start chip burning program

Read from another chip

Read from a file

Read source chip

Select a chip type and model

Select the file and load it

Specify file format

Set chip reading parameters

Run chip burning program

Set chip burning parameters

Burning succeeds

Verification passed?

Yes

No

Insert the source chip into the chip burner

Insert the target chip into the chip burner



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 36. 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 36 shows the extractor levers positions.

The corresponding IC adaptor shall be used in burning the FLASH ROM chip of PLCC encapsulation used in the ZXWM M900.

SDH Tester Function Figure 38 shows the outside view of the HP37718A SDH tester.

FI G U R E 38 AP P E AR AN C E O F T H E HP37718A SDH TE S T E R

External interface area

Alarm monitoring area

Key selection area

Test display window

HP37718A serves to measure SDH optical interface parameters, PDH electric interface parameters, jitter parameters, and bit errors.



Panel Description Alarm monitoring area

The alarm monitoring area is shown in Figure 39

FI G U R E 39 HP37718A AL A R M MO N I T O R AR E A

Common alarmindication

PDH/DSNalarm indication

Jitter alarmindication

SDH/SONETalarm indication

Alarm related key

History alarm indicator

Key selection area

The key selection area is shown in Figure 40.

FI G U R E 40 HP37718A KE Y SE L E C T I O N AR E A

Hard key area

Print/outputarea

Direction selection keysPop-up menuselection keys

Soft key area

Test display window



Hard key area: Providing functions marked on the keys.

Print/output area: In sequence from the left to the right and from up to down are printing button, paper feeding button, external display interface and built-in printing interface.

Direction selection keys: Changing selected items in the test display window

Pop-up menu selection keys: Selecting a pop-up menu

Soft key area: Providing functions the corresponding functions indicated in the test display window.

Test display window

The window area where the test is displayed is shown in Figure 41.

FI G U R E 41 HP37718A TE S T D I S P L AY WI N D O W AR E A

Transmitting settingwindow

Receiving settingwindow

Test resultssetting window OTHER and GRAPH

setting window

Soft keys and the related function selection

External interface area

The external interface area is located at the side of HP37718A. There are various optical and electrical interfaces distributed on the test area, each of which is marked with the interface name.



Operation Flow

Note: Since the operation of the HP37718A SDH tester is complicated, this section only introduces an error test process related with the WDM system. For details of other index tests, please refer to the related documents of tester.

24-Hour Bit Error Test Process Suppose there is a 3-channel system consisting of ZXWM M900. The test process of 24-hour bit error test is described as follows.

1. Establish connection between the boards and the tester according to the networking diagram as shown in Figure 42.

FI G U R E 42 CO N N E C T I O N O F SDH TE S T E R

OTU1T OTU1R

OTU1R OTU1T

OTU2T OTU2R

OTU2R OTU2T

OTU3T OTU3R

OTU3R OTU3T

SDHtester

: Variable optical attenuator

OBA OPA

OPA OBA

T

R

λ1 λ1

λ1 λ1

λ2 λ2

λ2 λ2

λ3

λ3 λ3

λ3

ODUOMU

ODU OMU

2. In the transmitting setting window, set the rate level and mapping structure of optical launched signals. For the ZXWM M900, only set SDH signals at the rate lower than STM-16 without special requirements for the mapping structure.

3. In the receiving setting window, set the rate level and mapping structure of optical received signals. In the bit error test of a WDM system, the setting should be the same as that of the transmitting end.

4. Set a test time.

5. Return to the transmitting setting window, and click the soft key LASER ON in the test window to enable the laser of the SDH tester.

6. Press the key Run/Stop to start the error test.

7. 24-hours later, click Result to view the test results in the TROUBLE SCAN and SDH/PDH ERROR ANALYSIS of the result window.

8. If any error is displayed, check the optical line and troubleshoot any fault. Then test the bit error again till there is no error.



Print Setting and Operation HP37718A can output the test results to the internal printer, an external printer or a floppy disk.

1. Press OTHER to turn the current operation window to the OTHER window in the test display window.

2. Via the direction keys, select the FUNCTION in the OTHER window.

3. Click the soft button corresponding to LOGGING in the test window; a LOGGING setting status window will be displayed.

4. Via the direction keys, modify the parameter after the SET UP as “DEVICE”.

5. Via the direction keys, modify the parameter in column LOGGING PORT, where DISK is a disk and GPIB is a built-in printer.

6. Press the print button on the panel of the tester to implement a printing task.

Precautions Before connecting an optical interface of the equipment or an

instrument, make sure to shut down the laser.

In the test of the interconnection between the equipment and an instrument, make sure to connect the optical receive interface before connecting the corresponding optical transmit interface, or enable the laser after the connection is completed.

When the test is finished, make sure to disconnect the optical transmit interface of the equipment and the tester before disconnecting the corresponding optical receive interface, or switch off the laser before unplugging the pigtail.

Avoid looking into the pigtail end surface of the optical transmit interface of the connection device or the laser.

When the pigtail connector for the optical transmit interface of the equipment and the tester is unplugged, make sure to cover the optical interface with a dust-proof cap to avoid any injury to human bodies.

HP37718A is suitable for testing signals with a rate less than 2.5 G.

The measurable input optical power range of the HP37718A is -10 dBm ~ -30 dBm. The input overload optical power is -8 dBm.

Before a test, make sure the head of fiber pigtail should be clean, and optical interfaces and fiber pigtails of equipment or the tester in connection should be well coupled.

Press the 1st and 5th keys at the left side of the soft key area simultaneously to reset and initialize the testing instrument system.

To test SDH/PDH signals, different interfaces in the test interface area should be used for the access of different rate levels.



Other Instruments and Meters The instruments and meters may be used in the test of WDM system include the optical spectrum analyzer, multi-wavelength meter, variable optical attenuator and the optical return loss tester. The section only briefly introduces these instruments and meters. Please refer to relevant documentation for detailed information about them.

Optical Spectrum Analyzer The optical spectrum analyzer serves to measure the relationship between the optical power and the wavelength. Its operation flow is introduced as follows.

1. With the automatic testing function provided by the optical spectrum analyzer, find the wavelength range and the optical power range of the tested optical spectrum.

If the meter is incapable of the automatic testing function, the probable wavelength range of the tested optical spectrum can be estimated. For example, the wavelength range of a 32-channel DWDM system is 1,530 nm ~ 1,561 nm.

2. Based on the wavelength range, set the start wavelength (START WAVELENGTH), the stop wavelength (STOP WAVELENGTH) or the center wavelength (CENTER WAVELENGTH), and the bandwidth span (SPAN) to be displayed on the optical spetrum analyzer.

3. Set the reference level (REFERENCE LEVEL) to display the optical wave longitudinally in the center of the screen.

4. Set the longitudinal amplitude unit dB/DIV to display the optical wave with appropriate size in the center of the screen.

5. Set the sensitivity (SENS) to clearly display the optical wave noise (bottom) on the screen.

6. Set the resolution bandwidth (RES) to clearly display the optical wave signal (top) on the screen. It is usually required to be 0.1 nm in the test.

7. So far, the optical wave should be clearly displayed on the screen.

Multi-Wavelength Meter The multi-wavelength meter mainly serves to test the optical wavelength. It can also be used to test the optical power.

Pay attention to the maximum input optical power of the meter in the test, and the measurable optical wavelength range.



Variable Optical Attenuator The variable optical attenuator serves to adjust the attenuation amount of the optical power. Note that adjust the attenuation in one direction in the test.

Optical Return Loss Tester The optical return loss tester serves to measure the optical reflectance. Calibrate it before the test.





A p p e n d i x F

Alarm Quick Lookup Table

Alarm Detection Board Severity

Laser No Output Power Alarm OTU series board Critical

No Input Power Alarm Transmit-end OTU board Critical

No Input Power Alarm Receive/regeneration-end OTU board Critical

Low Output Power Alarm OTU series board Major

Low Input Power Alarm Transmit-end OTU board Major

Low Input Power Alarm Receive/regeneration-end OTU board Major

No Input Power Alarm Critical

Low Input Power Alarm Major

No Output Power Alarm Critical

Low Output Power Alarm

OA

Major

No Total Output Power Alarm Critical

Low Total Output Power AlarmOMU/VMUX/OCI/OBM

Major

No Total Input Power Alarm Critical

Low Total Input Power Alarm ODU/OCI/OBM

Major

No Channel Output Power Alarm ODU8 Critical

Bit Error Over-Threshold Alarm OTU series board Critical

LOF Critical

LOS Critical

UAS Critical

Receiving Signal MS_AIS Alarm

OTU/SRM/GEM

Critical

OTUk LOF Alarm Critical

OTUk Loss of Multi-Frame Alarm Major

OTUk J0 TIM Alarm Major

OTUk BIP8 BE Over-Threshold Alarm

OTUF/OTU10G/GEMF/SRM41

Major



Alarm Detection Board Severity

Signal Out of Lock Alarm OTU/OTUP (accessing continuous-rate traffic) Major

Bit Error Alarm Major

LOF Alarm OSC

Critical

High Input Power Alarm OTU series board Major

J0 TIM Alarm OTU series board Major

Temperature Offset Over-Threshold and Temperature Over-Threshold Alarm

OTU/SRM/GEM OMU with AWG multiplexer ODU/VMUX/OA/OSC with AWG demultiplexer

Critical

High Current Alarm OTU/SRM/GEM /OA/OSCF Major

Card Dismount Alarm Critical

Card Mount Alarm Major

Environment Monitoring Alarm

NCP/NCPF

Major


Abbreviations

Abbreviation Full Name

AFR Absolute Frequency Reference

AFEC Advanced FEC

AGENT Agent

AIS Alarm Indication Signal

APO Auto Performance Optimization

APC Automatic Power Control

APR Automatic Power Reduction

APS Automatic Protection Switching

APSD Automatic Power Shutdown

APSF Automatic Protection Switching for FastEthernet

AWG Array Waveguide Grating

BER Bit Error Ratio

CDR Clock and Data Recovery

CIDR Classless Inter-Domain Routing

CMI Code Mark Inversion

CODEC Code and Decode

CPU Central Processing Unit

CRC Cyclic Redundancy Check

DBMS Database Management System

DCC Data Communications Channel

DCF Dispersion Compensation Fiber

DCN Data Communications Network

DCM Dispersion Compensation Module

DDI Double Defect Indication

DSF Dispersion Shifted Fiber

DTMF Dual Tone Multi Frequence

DWDM Dense Wavelength Division Multiplexing

DVB Digital Video Broadcasting

DXC Digital Cross-connect

ECC Embedded Control Channel




EDFA Erbium Doped Fiber Amplifier

EFEC Enhanced FEC

ESCON Enterprise System Connection

EX Extinction Ratio

FAS Frame Alignment Signal

FC Fiber Channel

FDI Forward Defection Indication

FEC Forward Error Correction

FICON Fiber Connection

FWM Four Wave Mixing

GbE Gigabits Ethernet

GEMF Gigabit Ethernet Mux Board with FEC

GUI Graphical User Interfaces

IP Internet Protocol

Interleaver -

LOF Loss of Frame

LOS Loss of Signal

IWF Integrated Wavelength Feedback

MANAGER Manager

MFAS MultiFrame Alignment Signal

MSP Multiplex Section Protection

MST Multiplex Section Termination

NCP Net Control Processor

NCPF Net Control Processor for Fast Ethernet

NE Network Element

NNI Network Node Interface

NRZ Non Return to Zero

NT Network Termination

OA Optical Amplifier

OADM Optical Add/Drop Multiplexer

OBA Optical Booster Amplifier

OAC Optical Access

OCH Optical Channel

ODF Optical fiber Distribution Frame

ODU Optical Demultiplexer Unit

OHP OverHead Processing Board

OHPF Overhead Processing Board for Fast Ethernet

Abbreviations



OLA Optical Line Amplifier

OLT Optical Line Termination

OMS Optical Multiplex Section

OMU Optical Multiplexer Unit

OP Optical Protection Unit

OPA Optical PreAmplifier

OPM Optical Performance Monitor

OSC Optical Supervision Channel

OSCF Optical Supervision Channel for Fast Ethernet

OSNR Optical Signal-Noise Ratio

OTM Optical Terminal

OTN Optical Transport Network

OTS Optical Transmission Section

OTU Optical Transponder Unit

OTUk Optical Channel Transport Unit-k

OXC Optical Cross-connect

RAC Receiver Adaptive Control

RZ Return to Zero

SDH Synchronous Digital Hierarchy

SDM Supervisory Division Multiplexing Board

SEF Severely Errored Frame

SES Severely Errored Block Second

SFP Small Form Factor Pluggable

SM Section Monitoring

SMCC Sub-network Management Control Center

SMT Surface Mount

SNMP Simple Network Management Protocol

STM Synchronous Transfer Mode

SWE Electrical Switching Board

TCP Transmission Control Protocal

TTI Trail Trace Identifier

TMN Telecommunications Management Network

VOA Variable Optical Attenuator

WDM Wavelength Division Multiplexing





Figures

Figure 1 Inserting a Fiber Pigtail with SC/PC Connectors ..................................26 Figure 2 Testing the Optical Launched Power..................................................28 Figure 3 Loopback of a Single-Channel Bidirectional OTU Board ........................31 Figure 4 Loopback of a Dual-Channel Regenerator OTU Board...........................31 Figure 5 Loopback of an OTUP Board ............................................................32 Figure 6 Loopback of Single-Channel Bidirectional OTUF/OTU10G Board.............32 Figure 7 Loopback of Dual-Channel Regenerator OTUF Board............................33 Figure 8 Application Example of OTU Board Loopback......................................33 Figure 9 Loopback of a Convergence Board ....................................................35 Figure 10 Application Example of Convergence Board Loopback ........................35 Figure 11 Connection Relationship in Single-Wavelength Bit Error Test...............36 Figure 12 Connection Relations in Cascade Bit Error Test .................................36 Figure 13 Appearance of a Network Cable......................................................37 Figure 14 Alarm Output Cable ......................................................................40 Figure 15 Connection of the Alarm Output Cable (with ALM_SET+ and ALM_SET-

Unconnected).....................................................................................41 Figure 16 APC Example of OA Board .............................................................43 Figure 17 Division of ARP Group in a System with DRA Boards..........................44 Figure 18 Maintenance of an Independent Fan Unit .........................................74 Figure 19 Alarm Handling Principle .............................................................117 Figure 20 Troubleshooting Process..............................................................156 Figure 21 Communication Fault Handling Process..........................................162 Figure 22 Networking Architecture of ZXWM M900 System (Case 1) ................176 Figure 23 Networking Architecture of ZXWM M900 System (Case 2) ................177 Figure 24 Network Topology ......................................................................183 Figure 25 Optical Interface IP Address Configuration in a 100 M Supervision

System ...........................................................................................193 Figure 26 Local NCP/NCPF Reconfiguration Flow ...........................................201 Figure 27 Operation Flow of Local Download of the Agent/FPGA Programs ........206 Figure 28 Operation Flow of the Remote Online Download of the Agent Program207 Figure 29 Schematic Diagram of Board Insertion Operation ............................222 Figure 30 General Flow of Board Replacement ..............................................223 Figure 31 Outside View of the PMS-1A Optic Power Meter ..............................227 Figure 32 Panel of the PMS-1A Optic Power Meter .........................................228 Figure 33 Operation Flow of Measurement Via the PMS-1A Optic Power Meter ...229 Figure 34 Appearance of an ALL-11 Chip Burner ...........................................230 Figure 35 Panel of an ALL-11 Chip Burner....................................................231 Figure 36 Sectional View of 40-Pin Socket ...................................................231 Figure 37 Operation Flow of ALL-11 Chip Burner ...........................................232 Figure 38 Appearance of the HP37718A SDH Tester ......................................233 Figure 39 HP37718A Alarm Monitor Area .....................................................234 Figure 40 HP37718A Key Selection Area ......................................................234 Figure 41 HP37718A Test Display Window Area ............................................235 Figure 42 Connection of SDH Tester............................................................236





Tables

Table 1 Typographical Conventions.............................................................. xiii Table 2 Mouse Operation Conventions.......................................................... xiii Table 3 Safety Signs.................................................................................. xiv Table 4 Maintenance Tools Required in an Equipment Room .............................20 Table 5 Instruments and Meters Required for Equipment Maintenance ...............21 Table 6 Fiber Connector Types .....................................................................24 Table 7 Software Loopback Modes for OTU Boards ..........................................30 Table 8 Software Loopback Modes for SRM41/SRM42/GEMF Boards...................34 Table 9 Color Code and Connection Relation of the Crossover Cable ..................38 Table 10 Color Code and Connection Relation of the Straight Cable ...................38 Table 11 Selection and Connection Relationship of Network Cable .....................39 Table 12 Color Code, Connection Relationship and Signal Definition...................40 Table 13 Software Reset .............................................................................42 Table 14 Principle of APR/APSD....................................................................43 Table 15 Communication Test Types .............................................................45 Table 16 FEC Types Supported by the ZXWM M900 .........................................46 Table 17 Configuration of Regenerator Board .................................................47 Table 18 FEC Mode Configuration .................................................................47 Table 19 Protection Modes for ZXWM M900....................................................48 Table 20 Function and Priority of Protection External Commands.......................48 Table 21 Boards and EMS Needed in the OCH Power Management.....................50 Table 22 Boards and EMS Needed in the OMS Power Management ....................50 Table 23 Wavelength Adjustment Function and Applicable Boards .....................51 Table 24 ZXWM M900 Routine Maintenance Items ..........................................57 Table 25 Specifications of Ambient Temperature and Humidity..........................58 Table 26 Meanings of Indicators of Cabinet and First Cabinet of Row .................62 Table 27 Correspondence Relationship between the Working Status and the

Indicator Status of the NCP/NCPF Board.................................................63 Table 28 Correspondence Relationship between the Working Status and the

Indicator Status of the OSCF Board .......................................................64 Table 29 Correspondence Relationship between the Working Status and the

Indicator Status of the Optical/Electrical Interfaces on the OSCF Board.......65 Table 30 Correspondence Relationship between the Working Status and the

Indicator Status of the APSF Board........................................................66 Table 31 Corresponding Relationship between the Working Status and Indicator

Status of the OTUP Board ....................................................................67 Table 32 Correspondence Relationship between the Working Status and Indicator

Status of the SRM41/SRM42 Board........................................................68 Table 33 Correspondence Relationship between the Working Status and Indicator

Status of the GEMF Board ....................................................................69 Table 34 Correspondence Relationship between the Working Status and Indicator

Status of the CA Board ........................................................................70 Table 35 Correspondence Relationship between the Working Status and Indicator

Status of the OMCP Board ....................................................................71 Table 36 Correspondence Relationship between the Running Status and Indicator

Status of the SWE Board......................................................................72 Table 37 The Correspondence Relationship of the Working Status and Indicator

Status of Other Boards ........................................................................73 Table 38 Performance Items of the ZXWM M900 (Classified by Detection Point) ..85 Table 39 Performance of the ZXWM M900 (Optical Power Performance) .............87



Table 40 Performance of the ZXWM M900 (Bit Error Performance).....................88 Table 41 Performance of the ZXWM M900 (Temperature Performance) ..............90 Table 42 Performance of the ZXWM M900 (Current Performance)......................91 Table 43 Performance of the ZXWM M900 (Synchronization Performance) ..........91 Table 44 OTU Laser Output Optical Power Performance Over Threshold..............92 Table 45 OTU (APD/PIN receiving module) Input Optical Power Over Threshold...93 Table 46 ODU Board Channel Optical Power Performance Over Threshold ...........94 Table 47ODU Total Input Optical Power Performance Value Over Threshold ........95 Table 48 OMU Total Output Optical Power Performance Value Over Threshold .....96 Table 49 OAD Tributary (1 ~ 8) Optical Power Performance Value Over Threshold

........................................................................................................97 Table 50 OBA Input Optical Power Performance Value Over Threshold ...............98 Table 51 OBA Output Optical Power Performance Value Over Threshold .............99 Table 52 OPA Input Optical Power Performance Value Over Threshold..............100 Table 53 OPA Output Optical Power Performance Value Over Threshold............101 Table 54 OLA Input Optical Power Performance Value Over Threshold..............102 Table 55 OLA Output Optical Power Performance Value Over Threshold............103 Table 56 OSC Board Direction A/B Input Optical Power Performance Value Over

Threshold ........................................................................................104 Table 57 OTU B1 Error Performance............................................................105 Table 58 OSC Direction A/B Error Performance .............................................106 Table 59 OSC Board Direction A/B Out-of-Frame Count Performance ...............107 Table 60 Temperature Over-threshold Performance.......................................108 Table 61 Current Over threshold Performance ..............................................109 Table 62 Alarms in the ZXWM M900 (Communication Alarms) ........................111 Table 63 Alarms in the ZXWM M900 (Equipment Alarms) ...............................115 Table 64 OTU Board Laser No Output Optical Power Alarm .............................118 Table 65 Transmitting-End OTU Board No Input Optical Power Alarm...............119 Table 66 Receiving/Regeneration-End OTU Board OTUG Board No Input Optical

Power Alarm ....................................................................................120 Table 67 OTU Board Low Output Optical Power Alarm....................................121 Table 68 Transmitting-End OTU Board Low Input Optical Power Alarm .............122 Table 69 Receiving/Regeneration-End OTU Board Low Input Optical Power Alarm

......................................................................................................123 Table 70 OA Board No Input Optical Power Alarm .........................................124 Table 71 OA Board Low Input Optical Power Alarm........................................125 Table 72 OA Board No Output Optical Power Alarm .......................................126 Table 73 OA Board Low Output Optical Power Alarm......................................127 Table 74 Optical Multiplex Board No Total Output Optical Power Alarm.............128 Table 75 Optical Multiplex Board Low Total Output Optical Power Alarm ...........130 Table 76 Optical Demultiplex Board No Total Input Optical Power Alarm...........132 Table 77 Optical Demultiplex Board Low Total Input Optical Power Alarm .........133 Table 78 ODU8 Board No Channel Output Optical Power Alarm .......................134 Table 79 OTU Board Bit Error Over-Threshold Alarm......................................135 Table 80 LOF Alarm..................................................................................136 Table 81 LOS Alarm..................................................................................137 Table 82 UAS Alarm .................................................................................138 Table 83 Receiving Signal MS_AIS Alarm.....................................................139 Table 84 OTUk LOF Alarm .........................................................................140 Table 85 OTUk Loss of Multi-Frame Alarm....................................................141 Table 86 OTUk J0 TIM Alarm......................................................................142 Table 87 OTUk BIP8 Error Over-Threshold Alarm ..........................................143 Table 88 OTU/OTUP Board Signal Out-of-Lock Alarm.....................................144 Table 89 OSC Board Bit Error Alarm............................................................145 Table 90 OSC Board LOF Alarm ..................................................................146 Table 91 OTU Board High Input Optical Power Alarm .....................................147 Table 92 OTU Board J0 TIM Alarm ..............................................................148 Table 93 Temperature/Temperature Offset Over-Threshold Alarm ...................149 Table 94 Current Over-Threshold Alarm ......................................................150 Table 95 Board Dismount Alarm.................................................................151 Table 96 Board Mount Alarm......................................................................152

Tables


Table 97 Environment Monitoring Alarm ......................................................153 Table 98 Illustration of DIP Switch Settings..................................................174 Table 99 Definition of the NE IP Address......................................................182 Table 100 Configuration Principle of the NE IP Address ..................................182 Table 101 IP Address Configuration of NEs Based on Area..............................184 Table 102 IP Address Configuration of NEs in One Area..................................184 Table 103 Relationship between ECC and Supervision System ........................185 Table 104 Description of Configuration Commands........................................187 Table 105 Description of Parameters of interface Command.........................191 Table 106 Configuration Principle of Optical Interface Address in a 100 M

Supervision System ..........................................................................192 Table 107 Definition of EMS Host Address....................................................193 Table 108 Configuration Principle of the EMS Host Address.............................194 Table 109 Common Network Configuration Commands in Windows .................195 Table 110 Common Network Configuration Commands in UNIX.......................196 Table 111 Network Configuration Command in the Configuration File (HP-UX)...196 Table 112 Network Configuration Command in the Configuration File (Solaris) ..197 Table 113 Definition of DIP Switch on NCP/NCPF Board..................................199 Table 114 Network Cable Connection for Local NCP/NCPF Reconfiguration ........202 Table 115 Network Connection for Remote Online Download ..........................208 Table 116 Definition of the Command portno ...............................................210 Table 117 Definition of the Command workmode ..........................................210 Table 118 Running Procedures of a Blank NCP/NCPF Board in a 2 M Supervision

System ...........................................................................................213 Table 119 Running Procedures of a Blank NCPF Board in a 100 M Supervision

System ...........................................................................................214 Table 120 Half-day Maintenance Record Form ..............................................215 Table 121 Daily Maintenance Record Form...................................................217 Table 122 Weekly Maintenance Record Form................................................219 Table 123 Login Password Change Record ...................................................220 Table 124 Specification of the PMS-1A Optic Power Meter ..............................228

Documents

Sjzl20051606-ZXWM M900 (V2[1].0) Maintenance Manual