unitrans zxmp s385 (v3.10) maintenance manual (volume iii) troubleshootings

ZXMP S385SDH Based Multi-Service Node Equipment

Maintenance Manual(Volume III) Troubleshootings

Version 3.10

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2011 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2012-01-16 First edition

Serial Number: SJ-20120110092612-006

Publishing Date: 2012-01-16(R1.0)

ContentsAbout This Manual ......................................................................................... I

Chapter 1 Basic Ideas and Methods for Fault Locating.......................... 1-11.1 Troubleshooting Procedure ................................................................................. 1-1

1.2 Basic Principles of Troubleshooting ..................................................................... 1-1

1.3 Basic Ideas for Fault Locating ............................................................................. 1-2

1.3.1 Fault Causes ........................................................................................... 1-2

1.3.2 Principles of Fault Locating ...................................................................... 1-3

1.4 Common Methods of Fault Locating .................................................................... 1-4

1.4.1 Observation & Analysis Method................................................................. 1-4

1.4.2 EMS Test Method..................................................................................... 1-4

1.4.3 Unplugging/Plugging Method .................................................................... 1-5

1.4.4 Replacement Method ............................................................................... 1-5

1.4.5 Configuration Data Analysis Method .......................................................... 1-5

1.4.6 Reconfiguration Method............................................................................ 1-6

1.4.7 Instrument Test Method ............................................................................ 1-6

1.4.8 Processing by Experiences ....................................................................... 1-7

Chapter 2 Typical Troubleshootings......................................................... 2-12.1 Service Interruption Fault .................................................................................... 2-1

2.1.1 Symptoms and Causes of Service Interruption Fault................................... 2-1

2.1.2 Troubleshooting Flow of Service Interruption Fault...................................... 2-2

2.1.3 Analysis and Handling of Service Interruption Fault .................................... 2-4

2.2 Bit Error Fault..................................................................................................... 2-5

2.2.1 Symptoms and Causes of Bit Error Fault ................................................... 2-5

2.2.2 Troubleshooting Flow of Bit Error Fault ...................................................... 2-5

2.2.3 Analysis and Handling of Bit Error Fault .................................................... 2-7

2.3 MS Protection Switching Fault............................................................................. 2-8

2.3.1 Symptoms and Causes of MS Protection Switching Fault............................ 2-8

2.3.2 Troubleshooting Flow of MS Protection Switching Fault .............................. 2-9

2.3.3 Analysis and Handling of MS Protection Switching Fault ........................... 2-10

2.4 SNCP Protection Switching Fault ...................................................................... 2-10

2.4.1 Symptoms and Causes of SNCP Protection Switching Fault ..................... 2-10

2.4.2 Troubleshooting Flow of SNCP Protection Switching Fault .........................2-11

2.4.3 Analysis and Handling of SNCP Protection Switching Fault....................... 2-13

I

2.5 Board 1:N Protection Switching Fault................................................................. 2-14

2.5.1 Symptoms and Causes of Board 1:N Protection Switching Fault................ 2-14

2.5.2 Troubleshooting Flow of Board 1:N Protection Switching Fault .................. 2-14

2.5.3 Analysis and Handling of Board 1:N Protection Switching Fault ................. 2-15

2.6 Clock Fault ...................................................................................................... 2-16

2.6.1 Symptoms and Causes of Clock Fault ..................................................... 2-16

2.6.2 Troubleshooting Flow of Clock Fault ........................................................ 2-17

2.6.3 Analysis and Handling of Clock Fault ....................................................... 2-18

2.7 EMS Monitoring Fault ....................................................................................... 2-19

2.7.1 Symptoms and Causes of EMS Monitoring Fault ...................................... 2-19

2.7.2 Troubleshooting Flow of EMS Monitoring Fault......................................... 2-20

2.7.3 Analysis and Handling of EMS Monitoring Fault ....................................... 2-22

2.8 Equipment Interconnection Fault ....................................................................... 2-24

2.8.1 Symptoms and Causes of Equipment Interconnection Fault ...................... 2-24

2.8.2 Troubleshooting Flow of Equipment Interconnection Fault......................... 2-25

2.8.3 Analysis and Handling of Equipment Interconnection Fault........................ 2-27

2.9 Data Service Fault............................................................................................ 2-28

2.9.1 Symptoms and Causes of Data Service Fault........................................... 2-28

2.9.2 Troubleshooting Flow of Data Service Fault ............................................. 2-28

2.9.3 Analysis and Handling of Data Service Fault ........................................... 2-30

2.10 Orderwire Fault .............................................................................................. 2-30

2.10.1 Symptoms and Causes of Orderwire Fault ............................................. 2-30

2.10.2 Troubleshooting Flow of Orderwire Fault ................................................ 2-31

2.10.3 Analysis and Handling of Orderwire Fault............................................... 2-32

2.11 Fan Fault ....................................................................................................... 2-32

2.11.1 Symptoms and Causes of Fan Fault ...................................................... 2-32

2.11.2 Troubleshooting Flow of Fan Fault ......................................................... 2-32

2.11.3 Analysis and Handling of Fan Fault ....................................................... 2-33

Figures............................................................................................................. I

Glossary ........................................................................................................ III

II

About This ManualPurpose

This manual applies to the Unitrans ZXMP S385 (V3.10) SDH based multi-service nodeequipment (ZXMP S385 for short).

ZXMP S385 is a multi-service node equipment with the highest transmission rate of 10Gbit/s. It supports ASON and can apply to the transmission network (at the access layerand convergence layer).

This manual describes the analyses and solutions for some common faults.

Intended Audience

The intended audience of this manual are as follow:

l Equipment maintenance personnels

What Is in This Manual

This manual is the Unitrans ZXMP S385 (V3.10) SDH Based Multi-Service NodeEquipment Maintenance Manual (Volume III) Troubleshootings, consisting of the followingparts:

Chapter Contents

Chapter 1, Basic Ideas and Methods for Fault Locating Describes the troubleshooting flow, and

basic principles and common methods for

troubleshooting.

Chapter 2, Typical Troubleshootings Describes the symptoms, causes, locating

procedures, analyses and handlings of

typical faults.

Related Documentation

The following documentation is related to this manual:

l Unitrans ZXMP S385 (V3.10) SDH Based Multi-Service Node Equipment ProductDescription

It describes the system architecture, system features, system functions, technicalspecifications and application example.

l Unitrans ZXMP S385 (V3.10) SDH Based Multi-Service Node Equipment HardwareDescription

It describes the equipment hardware, including cabinet, power distribution box,subrack, boards, interfaces, and indicators.

I

l Unitrans ZXMP S385 (V3.10) SDH Based Multi-Service Node Equipment InstallationManual

It describes the equipment installation procedures, including installation preparation,hardware installation, cable layout, installation check, and the detailed power on/offoperations.

l Unitrans ZXMP S385 (V3.10) SDH Based Multi-Service Node EquipmentMaintenance Manual (Volume I) Routine Maintenance

It describes the major items and common operations of routine maintenance of theequipment.

l Unitrans ZXMP S385 (V3.10) SDH Based Multi-Service Node EquipmentMaintenance Manual (Volume II) Alarms and Performances

It describes the handling methods for the equipment alarms and performance events.

Conventions

This document uses the following typographical conventions.

Typeface Meaning

Italics Variables in commands. It may also refers to other related manuals and

documents.

Caution: Indicates a potential hazard that, if not avoided, could result in moderate

injuries, equipment damages or partial service interruption.

Note: Provides additional information about a certain topic.

II

Chapter 1Basic Ideas and Methods forFault LocatingTable of Contents

Troubleshooting Procedure ........................................................................................1-1Basic Principles of Troubleshooting ............................................................................1-1Basic Ideas for Fault Locating ....................................................................................1-2Common Methods of Fault Locating ...........................................................................1-4

1.1 Troubleshooting ProcedureFigure 1-1 shows the troubleshooting procedure.

Figure 1-1 Troubleshooting Procedure

1.2 Basic Principles of TroubleshootingIn handling the equipment faults, the maintenance staff should follow these basicprinciples: observe first, then query, think, and take action finally.

1-1

SJ-20120110092612-006|2012-01-16(R1.0) ZTE Proprietary and Confidential

ZXMP S385 Maintenance Manual (Volume III) Troubleshootings

ObservingAfter arriving at the site, the maintenance personnel should first observe the faultphenomena carefully, including the faulty point, alarm cause, severity level, and damagelevel. Only by fully considering fault reasons of the equipment, can one feel the essenceof problem.

QueryingPut questions to onsite operators after observing fault phenomena. Check whether thereis any direct cause of the fault, such as data modification, file deletion, circuit boardreplacement, power supply fault or lightening.

ThinkingAfter observing the symptoms and querying the operators, the maintenance person cananalyze by using his own knowledge. Locate the fault, find the faulty point, and work outthe fault cause.

Taking ActionAfter locating the faulty point through above given three steps, the maintenance staffcan remove the fault by performing proper fault eradication procedures, for example, bymodifying the configuration data or by replacing the board.

1.3 Basic Ideas for Fault Locating

1.3.1 Fault Causes

Engineering ProblemsProject problem refers to substandard or inferior construction of the project, which resultsin equipment fault. Such problems can be revealed during the construction of project andthere are some problems, which cannot be revealed, until the equipment has operated fora certain time. These are latent risks for the equipment.

The product engineering specifications are usually summed up according to featuresof the product itself and some practical experiences. Therefore, in order to preventsuch problems, you should strictly observe the engineering specifications to performconstruction and installation. You should carry out the single-site or entire-networkdebugging and test.

External CausesExternal causes refer to the environment and equipment factors, which result in equipmentfault. Such factors do not include transmission equipment, but include:

l Power failure, such as equipment power failure, and too low supply voltage.l Switch fault.

1-2


Chapter 1 Basic Ideas and Methods for Fault Locating

l Fiber fault: Performance deterioration of fiber due to its wear and tear, fiber cut, illcontact of fiber connector.

l Cable fault, such as relay dropped or broken due to ill contact of cable connector.l The equipment is improperly grounded.l The equipment is placed in unsuitable environment.

Improper Operations

Improper operations refer to inappropriate operations performed by maintenance staff dueto lack of in-depth understanding of equipment, which results in equipment fault.

Improper operation is the most common phenomena while carrying out equipmentmaintenance, especially in network reconstruction, upgrading, and expansion, where theold and new devices are mixed or old and new versions are mixed. The maintenancestaff is usually unaware of the difference between old and new devices or between theold and new versions and tends to trigger off a fault.

Equipment Interconnection Problems

Various services are transmitted over the transmission equipment, which is connectedto various devices. In addition, different services require different performance oftransmission channels. There are equipment faults, which are usually derived fromimproper equipment interconnection. The interconnection problems include:

l Cable connection error.l Equipment grounding error.l Out-of-sync of clock between the transmission and switching networksl Inconsistent definition of overhead byte in the SDH frame structure.

Equipment Problems

Equipment problems refer to the faults caused by the transmission equipment itself,including equipment damage and inferior cooperation of PCBs. After running for a longtime, the PCBs are damaged due to aging factor, which ultimately result in damagedequipment. The characteristics of equipment damage are: the equipment has been inuse for a long time and has been running normally before the fault occurs; and the faultonly occurs at some certain point/PCB, or the fault occurs because of external causes.

1.3.2 Principles of Fault LocatingSince the transmission equipment covers the sites which are located far away from eachother, it becomes critical to locate the fault to the specific site accurately. After finding thefaulty site, concentrate on its eradication/troubleshooting.

The general principles of fault locating are as follows:

1. Check the external factors first, which can be fiber cut, switching fault, or power failure,and after that consider the transmission equipment faults.

2. Try to find out the faulty site first, and then locate the fault to the board.

1-3



3. The fault of optical line board causes alarms of tributary boards. Therefore, considerthe line first and then consider the tributaries. While analyzing alarms, consider thehigher priority alarms first, and then analyze the lower priority alarms.

1.4 Common Methods of Fault Locating

1.4.1 Observation & Analysis MethodWhen the system gets faulty, alarm information will appear on the equipment and EMS.Observing the status of alarm indicator on equipment will help to find the fault in time.

When a fault arises, EMS will record abundant alarm events and performance data.Analyze the information, and combine it with the overhead byte in SDH frame structureand the SDH alarm principle, to determinate fault type and fault location primarily.

While collecting the alarm information and performance information through EMS, makesure to set the current running time of NEs synchronous to EMS time. Deviation of timesetting will result in incorrect or delayed collection of alarm and performance informationof NEs.

1.4.2 EMS Test MethodWhen the networking, service and fault information are complicated or when equipmentfaces unidentifiable faults without reporting any clear alarm or performance information,use the maintenance functions (such as bit error insertion, alarm insertion, and loopback)provided by the EMS to test the faulty point and fault type.

The following content takes loopback operation as an example.

1. Before performing loopback operation, you need to determine the NE, board, path anddirection of loopback. The paths concurrently faulty are usually correlated to someextent, so when selecting the loopback path, select one faulty NE, one faulty trafficchannel, and then perform the loopback operation in each direction of selected trafficchannel for analyzing.

2. When performing the loopback operation, break up the business process of the faultytraffic channel, draw a service route map, set out the service source/sink, NEs thatthe service passes through, paths and timeslots occupied, and then perform loopbackin each segment to locate the faulty NE. After locating the fault to the NE, performloopback at the line side and tributary side to locate the possible faulty board. Finally,confirm the faulty board with other methods, and replace it.

The loopback operation does not require any in-depth analysis of alarms and performance.It is a common and effective method for locating the fault point. However, it may affect theservices.

1-4



1.4.3 Unplugging/Plugging MethodAfter locating fault to specific board, unplug the board and external interface connector.Plug them back to check ill contacts or abnormal board status.

Caution!

Be sure to observe the specifications while unplugging/plugging the board to avoid boarddamage or other problems caused by improper operations.

1.4.4 Replacement MethodReplacement method means replacing suspected a faulty piece of object with a normalone, such as a segment of cable, a board or a device, to locate and troubleshoot the fault.The replacement method is applicable to the following circumstances.

1. Check the problems of external transmission devices, such as the fiber, trunk cable,switch, or power supply equipment.

For example, the 2 M interface of a tributary board raises the “CV performancethreshold crossing” or “Loss of 2M signal” alarm, and it may be the switch or trunkfault; try replacing it with a normal path. If the alarm transfers after replacement, itindicates that external trunk cable or switch may be faulty. If the fault persists evenafter replacement, it may be a transmission fault.

2. Check the problem on board after locating the fault to a specific site.

For instance, if an alarm occurs because of faulty optical line board, the receiving fiberand transmitting fiber may be connected inversely, and fault can be removed just bycorrecting the fiber connection.

3. Resolve the power and grounding problems.

For example, if the input power and grounding of a device are suspected to be faulty,you can use a new channel of input power and connecting terminal to locate andremove the fault.

The replacement method is simple and demands less for maintenance staff. It is morepractical but demands availability of spare parts and accessories.

1.4.5 Configuration Data Analysis MethodDue to change of equipment configuration or improper operation of maintenance staff, theequipment 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 dataof equipment and EMS security log to analyze the fault.

By configuration data analysis method we can find and analyze causes of faults afterlocating the faulty NE. However, this method takes relatively longer time and is more

1-5



demanding. This method is applicable to the experienced maintenance staff who arefamiliar with the equipment.

1.4.6 Reconfiguration MethodThis method is used to locate fault by modifying the equipment configuration. It isapplicable to checking configuration error after locating fault to a specific site. Themodifiable configurations include timeslot, slot and board parameters.

Caution!

Before modifying the equipment configuration, back up the original configuration and keepa detailed record of operations being performed for convenience of fault investigation anddata recovery.

Here is an example of applying the reconfiguration method:

1. A typical application of reconfiguration method is to resolve the pointer justificationproblem. To locate the pointer justification problem, change the clock sourceconfiguration and clock extraction direction.

2. If you suspect that a tributary board or some of its paths are faulty, configure thetimeslot to another path or another tributary board. If you suspect that a slot on themotherboard is faulty, insert the board into another slot to locate/remove the fault.

3. During upgrading, expansion and reconstruction, if you suspect error in newconfiguration 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 servicestemporarily, or to tackle the pointer justification problem. It is not recommended inordinary circumstances.

1.4.7 Instrument Test MethodThe instrument test method refers to quantitatively testing the working parameters ofequipment by means of instruments. It is mostly used for checking the external problemsof transmission devices and problems of connecting with other devices.

Here is an example of conducting the instrument test:

1. Use a multi-meter to test whether the supply voltage is too high or too low.2. If the transmission device cannot be connected with other devices, and it is suspected

that the equipment grounding is improper, use a multi-meter to measure the voltagebetween the transmitting signal ground, and the receiving signal ground. If the voltagevalue is higher than 500 mV, you can conclude improper grounding of equipment.

3. If the transmission equipment cannot be interconnected with other equipment and it issuspected that the interface signal is not compatible, use a signal analyzer to observe

1-6



whether the frame signal is normal, whether the overhead bytes are normal, whetherany abnormal alarm occurs, so as to find out the cause of the fault.

This method features high accuracy, but it requires highly accurate instruments anddemands more for maintenance personnel.

1.4.8 Processing by ExperiencesAt some special occasions, due to instant abnormal power supply and strong externalelectromagnetic interference, the equipment board gets into abnormal working statusresulting in service interruption, ECC communication interruption, but the equipmentconfiguration data stays completely normal. Practice tells us that in such cases, we cantroubleshoot and recover effectively in time by resetting board, restarting the equipment,and by delivering the configuration data again.

The method demands thorough examination of the causes, and it is not recommendedunless in emergencies. While handling complex/tricky problems, the maintenance staffshould request technical support from nearest service center and try to eliminate the latentrisks.

1-7



This page intentionally left blank.

1-8


Chapter 2Typical TroubleshootingsTable of Contents

Service Interruption Fault ...........................................................................................2-1Bit Error Fault .............................................................................................................2-5MS Protection Switching Fault....................................................................................2-8SNCP Protection Switching Fault .............................................................................2-10Board 1:N Protection Switching Fault .......................................................................2-14Clock Fault ...............................................................................................................2-16EMS Monitoring Fault ...............................................................................................2-19Equipment Interconnection Fault ..............................................................................2-24Data Service Fault....................................................................................................2-28Orderwire Fault ........................................................................................................2-30Fan Fault..................................................................................................................2-32

2.1 Service Interruption Fault

2.1.1 Symptoms and Causes of Service Interruption Fault

Symptoms

l Service cannot get through, and alarms or performances are reported on EMS.l Service cannot get through, but no alarm or performance is reported on EMS.l Most tributary services are blocked.l Individual tributary service is blocked.

Fault Causesl External causes

à Power supply failure

à Fiber or cable failure

à Grounding abnormal

l Configuration errors

Data configuration of NE and EMS is wrong.

l Improper operations

à Due to improper operation, loopback is mistakenly set for optical/tributary path.

à Due to improper operation, the configuration data is modified or deleted.

2-1



à An alarm is manually inserted.

l Equipment problems

The board fails or has poor performance.

2.1.2 Troubleshooting Flow of Service Interruption FaultFigure 2-1 shows the troubleshooting flow of service interruption fault.

2-2


Chapter 2 Typical Troubleshootings

Figure 2-1 Troubleshooting Flow of Service Interruption Fault

2-3



2.1.3 Analysis and Handling of Service Interruption Fault

Eliminate external causes

1. Check the power supply for equipment. If the equipment is power-down, theunmanageable NEwill be gray on EMS, upstream/downstreamNEs are correspondingto reported LOS alarms on optical board, and a large area of 2 M services are blocked.

2. Check if the optical fiber connection is correct. Check the received optical power ofthe optical line board, test whether the receiving/transmitting light is normal and adjustthe optical interface to see whether the alarm disappears. Eliminate faults in opticalcircuit. Otherwise, EMS reports LOS alarms, and a large area of 2 M services areblocked.

3. Check if dry joint, miss out weld or loose connection exists, which might lead to blocked2 M services. Execute terminal-end loopback for 2 M tributary signals, and connect tobit error tester. If loss of 2 M electrical signals alarm does not disappear, the causesmight be interface problems of 2 M interface board, disconnection of 2 M cables, orcoaxial connector problems of distribution frame. Replace 2 M interface or cable tosolve these problems.

4. Check the grounding of equipment, the main cause is that the DDF/ODF is notgrounded or the transmission equipment does not share ground with the switch,which results in a significant voltage difference.

If the fault locates at 2 M interface board interconnected with third-party equipment,the fault cause may lie in different ground voltage between the interconnectedequipment and the transmission equipment. In order to eliminate the influence ofvoltage difference, following methods are applicable:

a. Check the ground grid and make consistent ground voltage between transmissionequipment and the interconnected equipment.

b. Ground the transmitting end of 2 M signal of the transmission equipment andinterconnected equipment, and do not ground the receiving end.

c. Connect a 0.1 u~0.5 u capacitor in series with interconnected 2 M signal cable.

For further information about grounding requirements, refer to Unitrans ZXMP S385SDH Based Multi-Service Node Equipment Technical Manual.

Check configuration data for NE

1. Check if slot configuration is correct. Wrong configuration might lead to blockingfor one or several 2 M services. Then execute downloading commands on EMS todownload the correct slot configuration data to tributary board. If there is still no signalon tributary board, reset the tributary board. Alarms will disappear if there is not anyother hardware problem.

2. Check if loopback exists between sites with blocked services. If loopback existsbetween optical line boards, all the 2 M services passing through this board areblocked. If some irregular 2 M service is blocked, check if corresponding 2 M tributarysignals are loopback.

2-4



3. Check if alarms are manually inserted, which leads to service blocking.

Check equipment hardware

1. Observe the running status of equipment indicators, and analyze equipment faults. Ifboth red light and green light of a board go out, and other boards are normal, it can beconcluded that the board is faulty. Replace the board.

2. Select tributary transmitting/receiving interface in faulty channel to connect with biterror tester. Execute hop-by-hop loopback from near-end to opposite-end, to locatefaulty board.

2.2 Bit Error Fault

2.2.1 Symptoms and Causes of Bit Error Fault

Symptoms

l B1/B2 performance events exist on EMS.l No B1/B2 performance events exist on EMS and only B3 performance events exist

on EMS.l No B1/B2/B3 performance events exist on EMS and only V5 performance events exist

on EMS.l No B1/B2/B3/V5 performance events exist on EMS and only CV performance events

exist on EMS.

Fault Causes

l External causes

à Optical power is too high or too low.

à The equipment is grounded improperly.

à Dry joint, miss out weld or loose connection exists in service cables.

à There is a strong interference source nearby.

à The equipment works in a high temperature environment without proper heatdissipation.


à The CSA/CSE/CSF board, line board or tributary board fails, or its performancedegrades.

à The clock synchronization performance is inferior.

2.2.2 Troubleshooting Flow of Bit Error FaultFigure 2-2 shows the troubleshooting flow of bit error fault.

2-5



Figure 2-2 Troubleshooting Flow of Bit Error Fault

2-6



2.2.3 Analysis and Handling of Bit Error FaultRelated overhead bytes include B1, B2, B3, and V5 bytes. Their priorities ranking in adescending order are B1→ B2→ B3→ V5.

For the performance events reported by EMS, the higher-level performance events shouldbe handled first. Go on to handle the lower level performance events if they are stillreported after handling the higher-level performance events.In normal cases, ensure theperformance value collected at any board by EMS is zero whenever the service is running.

Adopting test method to local the source of bit error by hop-by-hop loopback from nearend to opposite end.

Eliminate external causes1. Check whether the received/transmitted optical power falls in the index range. Both

the too high or too low optical power might lead to abnormality of optical module inreceiving optical signals, and also cause B1/B2 bit error at the same time. When thetransmitting optical power of opposite-end optical line board is normal, if local-endreceived optical power is lower than the receiver sensitivity, check if the fiberperformance is degraded or fiber connector is not clean; if received optical power ishigher than the overload power, check if optical interface types do not match withtransmission distance.

2. Check the equipment grounding. Check the grounding of equipment in the equipmentroom, especially whether the DDF/ODF have been properly grounded, or whetherthe transmission equipment and the switching equipment share the same commonground. If there are interconnection devices, check whether these two devices sharethe same common ground.For the grounding requirements, refer to theUnitrans ZXMPS385 SDH Based Multi-Service Node Equipment Technical Manual..

3. Check whether dry joint, miss out weld or loose connection exists in service cables,which will lead to V5 bit error or CV performance. Solve the problem by replacing DDFand interface of equipment interface board, or replacing cables.

4. Check whether any electromagnetic interference source, such as thunder andlightning, high voltage transmission line, power supply and other electric facilities,exists near the equipment.

5. Check whether the equipment temperature is within the normal range. Dirtyequipment room, blocked air filters or faulty fans may result in too high/low equipmenttemperature. For the requirements of environment temperature, refer to the UnitransZXMP S385 SDH Based Multi-Service Node Equipment Technical Manual.

Eliminate equipment causes1. Check bit errors of line board. If bit errors occur on all the line boards at a site, it

can be concluded that cross-connection clock board at this site is faulty. Replace thecross-connection clock board. If bit errors only occur on an individual line board, theline board or the opposite line board might be faulty.

2. If no B1/B2 performance event is reported after performing self-loop of local-end opticalline board, it means the local-end optical line board is normal. Similarly, if no B1/B2

2-7



performance event is reported after performing self-loop of the opposite optical board,it means the opposite optical board is normal.

3. Cross-connection clock board faulty or E3/T3 tributary board faulty will lead to poorperformance in higher-order channel. At the same time, B3 performance events existon EMS. Locate faulty board by switching cross-connection clock board or replacingtributary board.

4. Cross-connection clock board faulty or E1/T1 tributary board faulty will lead to poorperformance in lower-order channel. At the same time, V5 performance events existon EMS. Locate whether the local-end tributary board is faulty or the opposite-endtributary board is faulty, by switching cross-connection clock board, modifying slot totributary of adjacent NE, or executing loopback for tributary channel.

5. Check current timing source, and check if clock is in the normal status of locking.The degradation of clock synchronization performance will cause that line boardsconnecting with local site and adjacent site report B1/B2 bit error. Tributary servicesat local site will cause that tributary boards at local site and tributary boards atdownstream site passing through local site report channel bit errors.

2.3 MS Protection Switching Fault

2.3.1 Symptoms and Causes of MS Protection Switching Fault

Symptomsl The system cannot normally perform the protection switching when some faults occur,

and services are interrupted.l The switching status of individual site is abnormal after switching, MSP ring switching

fails, and services are interrupted.l The switching status of each board is normal after switching, but services are

interrupted.


Optical fiber connection is faulty.


à MS parameter configuration is faulty.

à Protection switching protocol is not enabled.


à Protection switching protocol is manually stopped.

à Forced switching or lock-out status is configured.

à MS-AIS alarm is manually inserted.

l Board faults

2-8



à Line board is faulty.

à Cross-connection clock board is faulty.

2.3.2 Troubleshooting Flow of MS Protection Switching FaultFigure 2-3 shows the troubleshooting flow of MS protection switching fault.

Figure 2-3 Troubleshooting Flow of MS Protection Switching Fault

2-9



2.3.3 Analysis and Handling of MS Protection Switching Fault

Eliminate external causesCheck fiber connections in the whole network, and make sure that they are correct.

Check configuration data for NE1. Check MS parameter configuration. Check if protection type configuration for MS

protection group is correct, check if NE sequence in the protection group is correct,check if configuration for APS ID is correct, check if the connection between NE portsis correct, check if APS byte adopted in MS ring is consistent.

2. Check if APS protocol of each NE is enabled, and if the protocol status of is normal.

Check improper operations1. Check if the status of forced switching or lock-out is configured. If so, protection

switching might not be triggered.2. Check if MS-AIS alarm is inserted manually. If so, switching might not be implemented

normally.

Check equipment hardwareIf the protection switching protocol is normally enabled, but the protection switching fails,and services are interrupted, it can be concluded that cross-connection board is faultyor line board is faulty. Locate the faults by switching or replacing cross-connection clockboard.

2.4 SNCP Protection Switching Fault

2.4.1 Symptoms and Causes of SNCP Protection Switching Fault

SymptomsSNCP services cannot be implemented for normal protection switching, and services areinterrupted.


Optical fiber connection is faulty.


à Configurations for SNC (I) and SNC (N) are faulty.

à Configurations for SNCP services at source site or sink site are faulty.

à Configurations for SNCP services passing through corresponding sites are faulty.

2-10



l Board faults

à Electrical tributary board is faulty.


à Line board is faulty.

2.4.2 Troubleshooting Flow of SNCP Protection Switching FaultFigure 2-4 shows the troubleshooting flow of SNCP protection switching fault.

2-11



Figure 2-4 Troubleshooting Flow of SNCP Protection Switching Fault

2-12



2.4.3 Analysis and Handling of SNCP Protection Switching Fault

Eliminate external causesSNCP adopts the protection mechanism of "concurrent transmission and selectivereception". Normally, if services are received via working channel, the incorrect connectionof pass-through NE in the protection channel will not affect services.

When the working channel for receiving services is faulty, and SNCP protection switchingoccurs, services select protection channel. At this moment, the incorrect connection ofpass-through NE in the protection channel will affect services. Hence, ensure the correctoptical connection in the whole network.

Check configuration data for NE1. Check if the configurations for switching conditions are incorrect.

The conditions for SNCP switching include:

a. Inherent monitored subnetwork connection: SNC (I)

If SSF alarms are detected at receiving end, services will be forced to executeswitching.

SSF signals are induced by LOP and AIS.

SNC (I) is the switching condition for SNC by default.

b. Signal degrade (SD)

SD will not lead to channel switching by default. Set SD as the switchingcondition, services will be forced to execute switching when SD alarms aredetected in channel.

c. Non-intrusive monitored subnetwork connection: SNC (N)

If TSF or TSD alarm is detected at receiving end, services will be forced to executeswitching.

TSF is induced by SSF, UNEQ or TIM alarm, while TSD is induced by SD alarm.

By fault, UNEQ, TIM or SD alarm will not lead to channel switching.

2. Check the configurations for SNCP services at source site or sink site, which need tobe configured as bidirectional services from tributary to working channel and protectionchannel.

3. Check the configurations for SNCP services at relevant pass-through site. Normally,configure bidirectional pass-through services for site in the ring network, configure bi-directional pass-through services between working channel and protection channel inthe cross-connection site of ring network and chain network.

Check equipment hardwareSNCP protection is implemented by adopting tributary board, cross-connection board andline board. Analyze EMS alarm data and performance data to locate board faults.

2-13



2.5 Board 1:N Protection Switching Fault

2.5.1 Symptoms and Causes of Board 1:N Protection SwitchingFault

Symptoms

The system cannot normally perform board 1:N protection switching, and services areinterrupted.

Fault Causes


à Hardware configuration is faulty.

à EMS data configuration is faulty.

l Hardware fault

à Working board in 1:N protection group is faulty.

à Protection board in 1:N protection group is faulty.


à Bridge board is faulty.

à Interface board is faulty.

2.5.2 Troubleshooting Flow of Board 1:N Protection Switching FaultFigure 2-5 shows the troubleshooting flow of board 1:N protection switching fault.

2-14



Figure 2-5 Troubleshooting Flow of Board 1:N Protection Switching Fault

2.5.3 Analysis and Handling of Board 1:N Protection SwitchingFault

Check equipment configurations

1. Check equipment hardware configuration, and eliminate configuration errors.

a. ZXMP S385 supports 2 M/1.5 M tributary protection. The subrack provides onegroup of 1:N (N≤9) tributary protection. Make sure that the configured board type

2-15



supports 1:N protection first, and then check if the configurations for hardwareslots are correct.

The slots for 2 M/1.5 M tributary board are slot 1 to slot 5 and slot 12 to slot16. Select any board to protect tributary board with the same rate in the sameprotection group.

b. ZXMP S385 supports 34 M/45 M/FE (electrical) service board protection, andsingle subrack provides two groups of 1:N (N≤4) board protection. Make surethat the configured board type supports 1:N protection first, and then check if theconfigurations for hardware slots are correct.

Slot 1 to slot 5 on 34 M/45 M/FE (electrical) service board are used as a protectiongroup, in which the board in slot 1 protects the board with the same rate in slot2 to slot 5. Slot 12 to slot 16 are used as another protection group, in which theboard in slot 16 protects the board with the same rate in slot 12 to slot 15.

c. ZXMP S385 supports 155 M (electrical) service board protection. The subrackprovides two groups of 1:N (N≤4) board protection. Make sure that the configuredboard type supports 1:N protection first, and then check if the configurations forhardware slots are correct.

Slot 1 to slot 5 on 155 M (electrical) service board are used as a protection group,in which the board in slot 1 protects the board with the same rate in slot 2 to slot5. Slot 12 to slot 16 are used as another protection group, in which the board inslot 16 protects the board with the same rate in slot 12 to slot 15.

2. Check if software configuration on EMS is correct

Check if the selection of working board and protection board in EMS is correct, andcheck if the configurations for protection group property are correct. If one protectionboard protects multiple working boards, further check if the settings for protectionpriority are correct.


1. Check if the working board is faulty, which can not normally report the board faults,and trigger switching conditions.

2. If the protection group normally detects switching condition, but the protectionswitching fails, check protection board, bridge board, cross-connection clock boardand interface board in order to judge if equipment board is faulty.

2.6 Clock Fault

2.6.1 Symptoms and Causes of Clock Fault

Symptoms

l EMS reports loss of timing input/output alarm.

2-16



l EMS reports pointer justification performance or justification threshold crossing alarm.l Crystal oscillator is degraded.l Phase-locked loop is out of lock.

Fault Causes

l External causes

à The optical fiber is inversely connected.

à The external clock is of poor quality, or the cable of external clock is degraded.

à Equipment temperature is too high.


à Unreasonable planning for clock tracking.

à Wrong clock source configuration, such as two clock sources co-exist in a subnet.

à Wrong setting of the clock source priority.

à Mutual extraction of clock.

à Wrong information configuration for external clock source.


à Optical line board fault, and inferior line clock.

à CSA/CSE/CSF board fault, and inferior working clock allocated to the boards.

2.6.2 Troubleshooting Flow of Clock FaultFigure 2-6 shows the troubleshooting flow of clock fault.

2-17



Figure 2-6 Troubleshooting Flow of Clock Fault

2.6.3 Analysis and Handling of Clock Fault


1. Check if the connection of optical fiber is correct. Incorrect connection will lead to AUpointer justification.

2. Check if equipment temperature is too high, which will lead to pointer justification.If the equipment temperature is too high or too low, eliminate the possible reasonscaused by equipment room environment, equipment dust-proof net blocking, and fan

2-18



fault. For the requirements of environment temperature, refer to Unitrans ZXMP S385SDH Based Multi-Service Node Equipment Technical Manual.

3. Check external clock input. The deterioration of external clock will lead to pointerjustification or loss of timing input alarm. Locate faults by replacing one channel ofinput external clock or clock input cable.

Check clock configurations

1. Check clock planning in the whole network to avoid too long clock tracking path.2. Check configuration for clock source to avoid that two clock sources are

simultaneously locked in the same sub-network.3. Check priority of clock source. If it is configured incorrectly, tracking each other after

clock protection switching will lead to pointer justification.4. Check if SSM clock protection is enabled correctly. If not, protection switching cannot

be implemented when the clock quality degrades, which will lead to pointer justification.5. Check if clock is configured as a loop, which will lead to mutual extraction of clock.6. Check the configurations for external clock source, and ensure SA byte of external

clock. Check if the configurations for external clock are mismatched with external clocktype.


Switch cross-connection clock board via EMS, check the locking status forcross-connection clock board, and judge if cross-connection clock board is faulty.

1. If clock is locked and AU PJC disappears after switching, replace the mastercross-connection clock board.

2. If clock still cannot be locked with the appearance of AU PJC after switching, changethe optical extraction direction of clock.

3. If AU PJC disappears, it means that optical line board is faulty.

2.7 EMS Monitoring Fault

2.7.1 Symptoms and Causes of EMS Monitoring Fault

Symptoms

l No NE in a system can be successfully pinged through the EMS.l The NEs in a system can be successfully pinged through the EMS but they cannot be

monitored by the EMS.l Only part of NEs in the network can be normally managed by the EMS.

Fault Causes

l External causes

2-19



à Power supply faults, such as equipment power failure or too low power supplyvoltage.

à Fiber faults, such as fiber performance deterioration or too high loss.

à Network cable faults

à DCN network faults


à Planning for EMS IP, route IP address and NE address are wrong.

à No enough sub-Manager in EMS

l Equipment faults

à Network adapter faults

à Optical line board faults, CSA/CSE/CSF board faults, or NCP board faults

à ECC path blocking

2.7.2 Troubleshooting Flow of EMS Monitoring FaultFigure 2-7 shows the troubleshooting flow of EMS monitoring fault.

2-20



Figure 2-7 Troubleshooting Flow of EMS Monitoring Fault

2-21



2.7.3 Analysis and Handling of EMS Monitoring Fault


1. Check the power supply of equipment. If the power supply fails, the icon ofcorresponding NE in the EMS turns gray and the EMS cannot manage the NE anylonger.

2. Check optical connection of the network. Make sure that optical connection betweenNEs is normal without any circuit problems. Otherwise, EMS only manages part of theNEs in the network.

3. Check if network cables are normal, and if cable type (straight-through cable orcrossover cable) is correct.

4. If EMS directly connects with DCN network, check whether DCN network is faulty bymonitoring DCN status.

Check configuration data

1. Check whether the NE data comply with EMS data, and if the version is integrated.

a. Set the all the bits of the DIP switch of NCP to “ON”, setting the NCP to be inDOWNLOAD status. Execute the telnet 192.192.192.11 command, and checkwhether the NE IP and server IP comply with the EMS database configurations.

b. Check whether the NCP version of NEs comply with EMS version. If not, uploadthe application program of NCP board supporting EMS.

2. Check EMS configuration data

a. Check whether the computer network configuration is correct. The EMS can pingthrough itself, it indicates that the network adaptor is correctly installed and thenetwork configuration takes effect. The EMS cannot ping through NCP; it indicatesthat the EMS computer, the NE IP address and the subnet maskmay be in differentnetwork section.

b. For an NE in the IP protocol stack version, EMS and the NE belong to samenetwork segment. However, the user does not set IP address of the access NE asdefault gateway or do not set a route. It will cause that EMS is not able to manageaccessing NE, or other NEs except for the accessing NE.

c. Check if there are redundant IP routes in the EMS, which cause EMS is not ableto manage accessing NE, or other NEs except for the accessing NE.

d. Check whether all the sub-managers have been started.

e. Check whether the NEs is beyond the management capability of thesub-Managers. For ZXMP S385, it is recommended that the maximum numberof NEs under the management of each sub-manager should not exceed 50. Ifthe number exceeds this value, start another sub-manager.

f. Check whether a gateway NE is set to isolate the internal network from the DCNnetwork. If so, check whether the gateway NE is properly set.

2-22



g. When EMS runs on the UNIX platform, check whether the system parameters ofmaxfiles and nfiles are correct.

Note:

These two parameters are core parameters in the HP-UX operating system. Wheninstalling EMS on the UNIX platform, adjust the core parameters of system, andrebuild HP-UX kernel.

maxfiles refers to the restriction of file quantity to be opened by one process.

nfiles refers to the maximum file quantity to be opened anytime. If this value is notmodified, maxfiles cannot be modified successfully.

3. Check configuration data for NE

a. Check whether all the NEs are online. The offline NEs cannot be managed by theEMS.

b. Check whether the same NE ID exists. If yes, redistribute the IDs for NEs.

c. In actual networking, try not to divide any area or use the backbone area under anycircumstances. When there are too many NEs on a network (for example, over64), the NEs are generally divided into different areas. When the number of NEsexceeds 128, they must be divided into different areas. In this case, if the networksegment division is wrong, the EMS may be unable to monitor all the NEs.

d. Check whether all the NEs distributed in different areas are directly connected withthe boundary NEs in backbone area.

e. Confirm whether the total number of NEs directly connected with the boundaryNEs, either in the backbone area or in non-backbone area, exceeds 128. If thisvalue is exceeded, the normal management becomes impossible. In addition, itis recommended that each border NE is to be directly connected with the one innon-backbone area.

f. Since the ECCs cannot directly work with each other in non-backbone area, andcan only work via backbone area, so check for the failure of NE in the ECC pathbetween the backbone area and the boundary.

g. Try to reduce border NEs. Sometimes, dividing NEs into too many areas maycomplicate inter-area relationships.

2-23



Note:

For the definition of NE address and the principle of route division, refer to UnitransZXMPS385 SDHBasedMulti-Service Node Equipment MaintenanceManual (VolumeI) Routine Maintenance

Check equipment faults

1. Check whether network adapter is faulty. If yes, EMS is unable to connect with NCPboard.

2. Check whether optical line board or cross-connection clock board is faulty. If yes, ECCchannel between NEs fails.

3. Check whether the NCP board is faulty. If yes, EMS is unable to manage the accessingNEs.

4. Check whether ECC channel is blocking.

2.8 Equipment Interconnection Fault

2.8.1 Symptoms and Causes of Equipment Interconnection Fault

Symptoms

l ZXMP S385 interconnects with other manufacturers’ SDH equipment, and servicesare interrupted.

l ZXMP S385 interconnects with other manufacturers’ SDH equipment, and the clocksare not synchronized.

Fault Causes

l External causes

à Incorrect connection of fiber or cable.

à Abnormal receiving/transmitting optical power

à Faulty cables

à The equipment is interconnected with other manufacturers’ equipment, and theequipment of one side is improperly grounded, or the devices of both sides donot share common ground.


à Inconsistent of sequence in the multiplexing process of signal mapping.

à The clocks are not synchronized.

2-24



à Inconsistent definition of overhead bytes in the SDH frame structures of differentmanufacturers.

à Wrong configuration or improper operation.

2.8.2 Troubleshooting Flow of Equipment Interconnection FaultFigure 2-8 shows the troubleshooting flow of equipment interconnection fault.

2-25



Figure 2-8 Troubleshooting Flow of Equipment Interconnection Fault

2-26



2.8.3 Analysis and Handling of Equipment Interconnection Fault


1. Check whether the physical connections between the equipment are correct.2. Check the receiving/transmitting optical power of interconnection equipment. Check

if receiving optical power is lower than receiver sensitivity caused by too high fiberloss or unclean connector, and check if receiving optical power is higher than overloadthreshold because of mismatched optical interface types.

3. Avoid open solder point/cold joint of cable and ill cable contact.4. Check the grounding and ground-sharing status of the devices at both sides.

Grounding problem is usually caused by two interconnected devices not sharingground properly, and the grounding resistance fails to reach the required index, or theDDF/ODF is not grounded properly.

The equipment room usually adopts joint grounding. For the sites that do not adoptjoint grounding, conduct the test carefully during hardware installation to ensure thatthe equipment at both sides share common ground. Check the grounding status ofthe shielding layer of the coaxial port.

Check configuration data for NE

1. Check timeslot arrangement sequence corresponding to tributary channels in themapping structure of VC-4. The numbering sequences of 3-7-3 structure fromdifferent manufacturers might be different, which will lead to service interruption.

2. Check clock synchronization of the whole network

The switches and GSM equipment of some manufacturers impose high requirementson the network-wide clock synchronization performance. Through the SDHtransmission network, if the clock of module office is not synchronized with the clockof mother office, it may result in trunk slip, dial-up access service interruption or evenfrequent call interruption. First, check whether the transmission devices are faulty. Ifthe transmission devices are normal, check whether the network-wide clock planningis rational. If not rational, adjust the network-wide clock synchronization scheme tosynchronize all clocks in the whole network.

3. Check the consistency of definition of overhead bytes in the SDH frame structuresof the interconnected devices. J1 and C2 bye mismatch alarms in ZTE transmissionequipment will not lead to service interruption, while those in othermanufacturersmightlead to service interruption. Hence, make sure that the overhead byte definitions ininterconnection equipment are inconsistent.

4. Check if configurations for service slots are wrong.5. Check if loopback is set manually.

2-27



2.9 Data Service Fault

2.9.1 Symptoms and Causes of Data Service Fault

Symptoms

l Data services are blocked in ZTE transmission equipment networking.l Data services are blocked when interconnecting with equipment from other

manufacturers.l Data service packets lose.l Data service bandwidth is inconsistent with the setting value.

Fault Causes

l External causes

à Faults at transmitting side, such as transmission services are blocked.

à Cable faults, such as wrong network cable connection, wrong usage of crossovernetwork cable and straight-through network cable.

à Interface alarms exist in data board.

l Data service configuration errors

à Wrong configuration for user end property.

à Wrong configuration for board operation mode.

à Wrong VLAN configuration.

à Wrong configuration for VCG port property.

à Mismatched configuration for port interconnecting with equipment from othermanufactures.

l Equipment faults

Faults of the data board

2.9.2 Troubleshooting Flow of Data Service FaultFigure 2-9 shows the troubleshooting flow of data service fault.

2-28



Figure 2-9 Troubleshooting Flow of Data Service Fault

2-29



2.9.3 Analysis and Handling of Data Service Fault

Eliminate external causes1. Check if transmission services are faulty. If so, handle the transmission service alarms

first.2. Check if the construction and usage of crossover network cable and straight-through

network cable are correct.3. Check if interface alarms occur in data board. If so, check if interface or fiber is faulty.

For data board with optical interface, check if receiving optical power at port is normal.

Check data service configurations1. Check property configurations for user port. Correctly configure the rate and duplex

mode of the port, which should be consistent in both sides of the port. And correctlyconfigure restriction for output rate of user port.

2. Check the property configuration for VCG port, such as port capacity, packing mode,and LCAS settings.

3. Check if configuration for VLAN is correct.4. Check if configuration for VLAN process mode at port is correct.

Check equipment hardwareJudge if data board is faulty by checking alarm and performance data on EMS, solve boardfaults by resetting board and replacing board.

2.10 Orderwire Fault

2.10.1 Symptoms and Causes of Orderwire Fault

Symptomsl Orderwire telephone fails to make an orderwire call with no dialing tone heard.l Orderwire telephone fails to make a group orderwire call.l There are lots of noises during an orderwire call.l There are lots of howls during a group orderwire call.


à The main power is off, or the optical line is interrupted.

à The orderwire telephone is faulty.


The configuration of OW board or optical line board is wrong.


2-30



The OW board or the optical line board is faulty.

2.10.2 Troubleshooting Flow of Orderwire FaultFigure 2-10 shows the troubleshooting flow of orderwire fault.

Figure 2-10 Troubleshooting Flow of Orderwire Fault

2-31



2.10.3 Analysis and Handling of Orderwire Fault


1. Check whether the optical line raises any alarm. Resolve the optical line alarm first, ifany. Because the optical line fault will lead to orderwire fault.

2. Check if the fibers at the sites are connected as the data configuration.3. Check whether the orderwire phone sets are faulty. If so, replace the phone sets.

Check orderwire configurations

1. Check whether the group call is set in the EMS software.2. Check whether the orderwire is looped, which will cause the howl/echo in-group call.

If so, set the loopback site as control point.3. Check if the orderwire protection bytes in the interconnected optical direction are set

correctly. The orderwire protection bytes of all the interconnected optical interfacesmust be identical.


Check the OW board, optical line board, and observe indicators and EMS alarms. Checkif board is faulty by unplugging/plugging or replacing the board.

2.11 Fan Fault

2.11.1 Symptoms and Causes of Fan Fault

Symptoms

l Indicator on the front panel of fan box is abnormal. The red indicator is solid on.l EMS reports alarms of fan faults.

Fault Causes

l External causes

Fan cable failure, or ill contact between the fan box and motherboard.


Fault of NCP board or fan control board (FAN)

2.11.2 Troubleshooting Flow of Fan FaultFigure 2-11 shows the troubleshooting flow of fan fault.

2-32



Figure 2-11 Troubleshooting Flow of Fan Fault

2.11.3 Analysis and Handling of Fan Fault


1. Check whether the fan is running normally.2. Check the cable and the connection between interfaces.3. Check whether the fan box is completely inserted into the fan plug-in box.


1. Check if there are fan alarms on the EMS. If so, replace the fan box.2. Check whether the indicators on the panel of fan plug-in box are normal. In normal

case, the green indicator is constantly on, and the red indicator is constantly off. If thered indicator is constantly on, it indicates that the fan running is blocked. Replace thefan.

3. If the fan is running properly but fan alarms are reported on the EMS, check whetherthe alarms are wrongly reported by resetting or replacing the NCP board.

2-33




2-34


FiguresFigure 1-1 Troubleshooting Procedure ...................................................................... 1-1

Figure 2-1 Troubleshooting Flow of Service Interruption Fault................................... 2-3

Figure 2-2 Troubleshooting Flow of Bit Error Fault .................................................... 2-6

Figure 2-3 Troubleshooting Flow of MS Protection Switching Fault ........................... 2-9

Figure 2-4 Troubleshooting Flow of SNCP Protection Switching Fault..................... 2-12

Figure 2-5 Troubleshooting Flow of Board 1:N Protection Switching Fault............... 2-15

Figure 2-6 Troubleshooting Flow of Clock Fault ...................................................... 2-18

Figure 2-7 Troubleshooting Flow of EMS Monitoring Fault ...................................... 2-21

Figure 2-8 Troubleshooting Flow of Equipment Interconnection Fault ..................... 2-26

Figure 2-9 Troubleshooting Flow of Data Service Fault ........................................... 2-29

Figure 2-10 Troubleshooting Flow of Orderwire Fault.............................................. 2-31

Figure 2-11 Troubleshooting Flow of Fan Fault ....................................................... 2-33

I

Figures


GlossaryAIS- Alarm Indication Signal

APS- Automatic Protection Switching

ASON- Automatically Switched Optical Network

DCN- Data Communications Network

DDF- Digital Distribution Frame

ECC- Embedded Control Channel

FE- Fast Ethernet

LOP- Loss Of Pointer

MSP- Multiplex Section Protection

ODF- Optical Distribution Frame

SD- Signal Degrade

SNC- Sub-Network Connection

SNCP- Sub-Network Connection Protection

SSF- Server Signal Failure

TIM- Trace Identifier Mismatch

TSF- Trail Signal Fail

UNEQ- UN-Equipped

III

unitrans zxmp s385 (v3.10) maintenance manual (volume iii) troubleshootings

Documents