CiTRANS 660

High-capacity MPLS-TP Platform

Troubleshooting Guide
Version: A

Code: MN000001394

FiberHome Telecommunication Technologies Co., Ltd.

December 2012
Thank you for choosing our products.

We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +6 03 7960 0860/0884 (for Malaysia)
+91 98 9985 5448 (for South Asia)
+593 4 501 4529 (for South America)
Fax: +86 27 8717 8521
Website: http://www.fiberhomegroup.com
Legal Notice

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.

All rights reserved

No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface

Related Documentation
Document Description

CiTRANS 660 High-capacity Introduces functions and features, protection mechanisms,

MPLS-TP Platform Product networking applications and technical specifications of the
Description product.

Describes the equipment’s structures, functions, signal

CiTRANS 660 High-capacity
flows, specifications, and technical parameters in terms of
MPLS-TP Platform Hardware
its hardware components (i.e. the cabinet, the subrack,
Description
cards, and cables).

Details the equipment’s appearance and structure, how to

CiTRANS 660 High-capacity
install the equipment, connect and lay out its wires and
MPLS-TP Platform Installation
cables, as well as the requirements on the installation
Guide
environment.
Introduces the rules and methods for the configuration of
CiTRANS 660 High-capacity
various functions and performance parameters in the
MPLS-TP Platform Configuration
subnet-level mode through the OTNM2000; gives some
Guide
typical configuration examples and operation procedures.

Details the routine maintenance items and operation

procedures, including the daily maintenance, the weekly
CiTRANS 660 High-capacity
maintenance, the monthly maintenance, and the quarterly
MPLS-TP Platform Routine
maintenance. Also includes the daily operation procedures
Maintenance
of the equipment, instructing users on the implementation
of the basic operations such as hardware replacement.

CiTRANS 660 High-capacity Gives a detailed introduction to notices of fault

MPLS-TP Platform management, fault isolating methods as well as
Troubleshooting Guide procedures and methods of fault management.

I
 Document Description

Describes classification and category of alarm and

CiTRANS 660 High-capacity
performance indicators and their suppressing
MPLS-TP Platform Alarm and
relationships, and lists definitions, causes and
Performance Reference
management of each alarm and performance.

Includes four manuals, i.e., product description, operation

guide, routine maintenance and installation guide, all of
e-Fim OTNM2000 Element
which are aimed at introducing common and fundamental
Management System Manual Set
contents of the OTNM2000 for a better understanding and
proficient use of the network management system.

II
Version
Version Description

A Initial version.

Intended Readers

This manual is intended for the following readers:

u Commissioning engineers

u Operation and maintenance engineers

To utilize this manual, these prerequisite skills are necessary:

u MPLS-TP technology

u Data communication technology

u TDM communication theory

u Ethernet technology

III
 Conventions

Terminology Conventions

Terminology Convention
FiberHome CiTRANS 660 High-capacity MPLS-TP
CiTRANS 660
Platform
FiberHome e-Fim OTNM2000 Element Management
OTNM2000
System

NMUJ1 EMU Management Card

XCUJ2 Cross-connect & Clock Card (320G)

XCUJ4 Cross-connect & Clock Card (160G)

XSJ2 10G LAN/WAN Optical Interface Card (2 channels)

XSJ3 10G LAN/WAN Optical Interface Card (4 channels)

XGJ1 XGE & GE Interface Board

GSJ2 GE Interface Card with Switch Function (MPLS)

GSJ3 GE Interface Card

ESJ1 Ethernet Interface Card with Switch Function
ESJ2 FE Interface Card with Switch Function
S1J1 STM-1 Optical Interface Card

S1J2 STM-1 Optical Interface Card (2 channels)

S1O1 cSTM-1 Emulated Interface Unit

S1J4 8×STM-1 Optical Interface Card

E1J1 E1 Interface Card

E1J2 E1 Processing Card

AIFJ1 Power and Auxiliary Terminal Board 1

AIFJ2 Power and Auxiliary Terminal Board 2

IEJ1 E1 Terminal Board (75Ω)

IEJ2 E1 Terminal Board (120Ω)

IFJ1 Ethernet Terminal Board

IV
Symbol Conventions

Symbol Convention Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.

Warning May cause severe bodily injuries.

➔ Jump Jumps to another step.

Cascading
→ Connects multi-level menu options.
menu
Bidirectional
↔ The service signal is bidirectional.
service
Unidirectional
→ The service signal is unidirectional.
service

V
Contents

Preface...................................................................................................................I

Related Documentation ...................................................................................I

Version ..........................................................................................................III

Intended Readers ..........................................................................................III

Conventions ................................................................................................. IV

1 Overview of Troubleshooting...........................................................................1

1.1 Operation Safety Precautions............................................................2

1.1.1 Safety and Warning Signs ...................................................2

1.1.2 ESD Protection ...................................................................3
1.1.3 Plugging and Unplugging Cards..........................................4
1.1.4 Operation Safety Rule of a Fiber and an Optical Interface ....5
1.1.5 Electrical Safety..................................................................8
1.1.6 Operation Safety Rules for the OTNM2000..........................9

1.2 Requirement for Maintenance Staff .................................................14

1.2.1 Theoretical Knowledge .....................................................14

1.2.2 Network Information of the Project.....................................15
1.2.3 Basic Operations on the Equipment ..................................15
1.2.4 Application of Tools and Meters.........................................15
1.2.5 Collecting and Saving Field Data.......................................16

1.3 List of Tools and Meters ..................................................................16

2 Troubleshooting Flow....................................................................................17

2.1 Troubleshooting Flow......................................................................18

2.2 Flow Description .............................................................................20

3 Basic Principles and Methods for Fault Isolation ............................................22

3.1 Basic Principles of Fault Isolation ....................................................23

3.2 Common Methods for Fault Isolation ...............................................24

3.2.1 Layer-by-layer Method ......................................................24

3.2.2 Block-by-block Method......................................................26
3.2.3 Section-by-section Method................................................29
 3.2.4 Alarm and Performance Event Analysis.............................32
3.2.5 Loopback Method .............................................................35
3.2.6 Substitution ......................................................................40
3.2.7 Meter Test Method ............................................................42

4 Common Operations of Troubleshooting .......................................................44

4.1 Resetting a Card.............................................................................45

4.1.1 Hardware Reset................................................................45

4.1.2 Software Reset .................................................................46

4.2 Plugging and Unplugging a Card.....................................................47

4.3 Replacing a Component..................................................................49

4.3.1 Replacing a Card ..............................................................50

4.3.2 Replacing an Optical Module.............................................53
4.3.3 Replacing a Pigtail ............................................................56
4.3.4 Replacing a Fan ...............................................................57
4.3.5 Replacing the Anti-Dust Screen ........................................59

4.4 Performing Loopback......................................................................61

4.4.1 Performing Hardware Loopback........................................61

4.4.2 Performing Software Loopback .........................................63

4.5 Cleaning an Optical Fiber Connector ...............................................65

4.6 Measuring Optical Power ................................................................66

4.6.1 Measuring Transmitting Optical Power ..............................67

4.6.2 Measuring Receiving Optical Power ..................................70

4.7 Viewing Alarms and Performance ...................................................72

4.7.1 Viewing Alarms.................................................................72

4.7.2 Viewing Performance........................................................74

5 Handling Network Management Communication Faults .................................79

5.1 A Single NE Out of Management.....................................................80

5.1.1 Background Information ....................................................80

5.1.2 Cause of Fault ..................................................................80
5.1.3 Troubleshooting Procedures .............................................80

5.2 All NEs in a Certain Network Block or the Entire Network Out of
Management ..................................................................................81

5.2.1 Background Information ....................................................81

 5.2.2 Cause of Fault ..................................................................82
5.2.3 Troubleshooting Procedure ...............................................82

6 Handling Errors and Packet Loss ..................................................................84

6.1 Background Information ..................................................................85

6.2 Cause of Fault ................................................................................85

6.3 Troubleshooting Procedure .............................................................86

7 Handling Abnormal Optical Power Faults.......................................................87

7.1 Background Information ..................................................................88

7.2 Cause of Fault ................................................................................88

7.3 Troubleshooting Procedure .............................................................89

8 Handling L2VPN Service Interruption ............................................................90

8.1 Handling CES Interruption...............................................................91

8.1.1 Background Information ....................................................91

8.1.2 Cause of Fault ..................................................................91
8.1.3 Troubleshooting Flow........................................................91
8.1.4 Troubleshooting Procedure ...............................................93

8.2 Handling Ethernet Service Interruption ............................................94

8.2.1 Background Information ....................................................94

8.2.2 Cause of Fault ..................................................................94
8.2.3 Troubleshooting Flow........................................................94
8.2.4 Troubleshooting Procedure ...............................................95

9 Handling QoS Failure....................................................................................98

9.1 Background Information ..................................................................99

9.2 Cause of Fault ................................................................................99

9.3 Troubleshooting Flow......................................................................99

9.4 Troubleshooting Procedure ...........................................................100

10 Handling Network Level Protection Switching Faults....................................102

10.1 Background Information ................................................................103

10.2 Cause of Fault ..............................................................................103

10.3 Troubleshooting Flow....................................................................103

10.4 Troubleshooting Procedure ...........................................................105

11 Fault Case ..................................................................................................107

11.1 Some Services Interrupted due to Tributary Card Failure ...............108

11.2 All Services Interrupted due to Line Card Failure ........................... 114

11.3 Service Interrupted due to Optical Line Failure............................... 117

Appendix A Indicator LEDs ........................................................................120

A.1 Cabinet Indicator LEDs .................................................................120

A.2 FAN Indicator LEDs ......................................................................120

A.3 Card Indicator LEDs......................................................................121

Appendix B Optical Interface Specifications................................................124

Appendix C Abbreviations..........................................................................126
Figures

Figure 1-1 Positions of the ESD protection earth ground fastener, subrack earth
ground pole ......................................................................................3
Figure 1-2 Slide rails..........................................................................................5
Figure 1-3 Dedicated fiber puller ........................................................................6
Figure 1-4 No access to Internet ........................................................................9
Figure 1-5 Do not modify IP addresses ............................................................10
Figure 1-6 Do not modify protocol settings ....................................................... 11
Figure 1-7 Do not modify computer name.........................................................12
Figure 1-8 Do not modify LAN settings .............................................................13
Figure 2-1 Troubleshooting flow.......................................................................19
Figure 3-1 Network diagram - layer-by-layer method ........................................26
Figure 3-2 Network diagram - block-by-block method .......................................28
Figure 3-3 Diagram of section-by-section method.............................................29
Figure 3-4 Network diagram - section-by-section method .................................31
Figure 3-5 Alarm and performance analysis .....................................................34
Figure 3-6 Hardware loopback (optical interface)..............................................36
Figure 3-7 Signal flow of line loopback .............................................................37
Figure 3-8 Signal flow of equipment loopback ..................................................38
Figure 3-9 Card connection under loopback method ........................................39
Figure 3-10 Network diagram - substitution method............................................41
Figure 3-11 Meter test method ...........................................................................43
Figure 4-1 Installing a card...............................................................................48
Figure 4-2 Unplugging a card...........................................................................49
Figure 4-3 Unplugging the SFP / XFP optical module .......................................55
Figure 4-4 Installing the SFP / XFP optical module ...........................................55
Figure 4-5 The snap-in latch of the fan unit.......................................................57
Figure 4-6 Removing the fan unit .....................................................................58
Figure 4-7 Installing the fan unit .......................................................................59
Figure 4-8 Removing the subrack's anti-dust screen ........................................60
Figure 4-9 Installing the subrack's anti-dust screen ..........................................60
Figure 4-10 Hardware loopback (optical interface)..............................................62
Figure 4-11 Hardware loopback (Ethernet interface) ..........................................62
Figure 4-12 Hardware loopback (E1 interface) ...................................................63
Figure 4-13 Connection of optical Tx power test .................................................68
Figure 4-14 Connection of optical Rx power test.................................................70
Figure 4-15 Querying current alarms..................................................................73
Figure 4-16 Querying alarm history ....................................................................74
Figure 4-17 Querying current performance.........................................................76
Figure 4-18 Querying performance history .........................................................77
Figure 8-1 Troubleshooting flow of CES interruption .........................................92
Figure 8-2 Troubleshooting flow of Ethernet service interruption .......................95
Figure 9-1 Troubleshooting flow of QoS abnormality ......................................100
Figure 10-1 Troubleshooting flow of the network level protection switching
failure ...........................................................................................104
Figure 11-1 Network topology of tributary card failure .......................................108
Figure 11-2 Example of tributary card failure - VP layer loopback frame
configuration................................................................................. 110
Figure 11-3 Example of tributary card failure - VP layer CV frame configuration of
NE1.............................................................................................. 111
Figure 11-4 Example of tributary card failure - VC layer loopback frame
configuration................................................................................. 112
Figure 11-5 Example of tributary card failure - VC layer CV frame configuration 113
Figure 11-6 Network topology of line card failure .............................................. 115
Figure 11-7 Example of line card failure - VS loopback frame configuration ...... 116
Figure 11-8 Network topology of line failure...................................................... 117
Tables

Table 1-1 Security and warning signs ...............................................................2

Table 1-2 List of tools and meters ...................................................................16
Table 3-1 Comparison between the two ways of obtaining information (by the
OTNM2000 and by the equipment indicator LEDs) ..........................33
Table 3-2 Loopback related information ..........................................................35
Table 4-1 Comparisons between card reset methods......................................45
Table 4-2 Recommended Value......................................................................77
Table 4-3 Performance codes of card error, packet loss and error packet
count ..............................................................................................78
Table 7-1 Common causes of abnormal optical power faults ...........................88
Table 8-1 Common causes of CES interruption...............................................91
Table 8-2 Common causes of Ethernet faults..................................................94
Table 9-1 Common causes of QoS faults ........................................................99
Table 10-1 Common causes of the network level protection switching fault......103
Table A-1 Descriptions of cabinet indicator LEDs ..........................................120
Table A-2 Descriptions of the indicator LEDs on the fan unit ..........................120
Table A-3 LED indicators on the interface card's panel ..................................121
Table A-4 LED indicators on the NMUJ1 card's panel ....................................122
Table A-5 LED indicators on the XCUJ2 / XCUJ4 card's panel.......................123
Table B-1 10GE optical interface specifications .............................................124
Table B-2 GE optical interface specifications.................................................124
Table B-3 FE optical interface specifications .................................................125
Table B-4 STM-1 optical interface specifications ...........................................125
1 Overview of Troubleshooting

During troubleshooting of the equipment, the maintenance staff should follow the
operation safety rules, so as to avoid bodily injury and equipment damage. In
addition, the maintenance staff should master certain technical knowledge and
operation skills.

The following discusses the troubleshooting rules.

Operation Safety Precautions

Requirement for Maintenance Staff

List of Tools and Meters

Version: A 1
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

1.1 Operation Safety Precautions

The following discusses precautions of equipment operations. During operations of

the equipment, the maintenance staff should obey the operation safety rules, so as
to avoid bodily injury and equipment damage.

1.1.1 Safety and Warning Signs

The maintenance staff should be familiar with the safety and warning signs, whose
meanings are shown in Table 1-1 and Figure 1-1.

Table 1-1 Security and warning signs

Sign Meaning Location

The ESD protection sign. This sign
reminds the operators to wear an
ESD protection wrist strap, so as to
avoid damage to the equipment
See Figure 1-1.
caused by electrostatic discharge.

The subrack earth ground sign. This

sign marks the location of the
subrack earth ground pole.

The laser class sign. This sign

marks the optical source class of the
Is located on panels of the
optical interface on a card. The
cards with optical
maintenance staff must prevent the
interfaces.
optical source from entering eyes
directly to avoid bodily harm.

A periodical cleaning sign on the

anti-dust screen, used as a reminder
Is located on the panel of
that operation engineers should
the anti-dust screen.
clean the anti-dust screen
periodically.

The fan safety alarm sign. This sign

Is located on the panel of
reminds the maintenance staff not to
the fan unit.
touch the running fan blades.

Reminds the maintenance staff to

Is located on the panel of
disconnect power before plugging
the AIFJ1 / AIFJ2 power
and unplugging the AIFJ1 / AIFJ2
terminal board.
power terminal board.

2 Version: A
 1 Overview of Troubleshooting

(1) ESD protection sign (2) ESD protection earth ground fastener

(3) Subrack earth ground sign (4) Subrack earth ground pole

Figure 1-1 Positions of the ESD protection earth ground fastener, subrack earth ground pole

1.1.2 ESD Protection

Relevant knowledge

Electrostatic discharge can damage electrostatic sensitive components on cards

and subracks. Therefore, wear an ESD protection wrist strap before touching the
equipment, cards, IC (Integrated Circuit) chips, etc. Use the ESD protection bags to
store and transport cards

Version: A 3
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Note:

The ESD protection wrist strap is an accessory shipped with the

equipment.

Safety measures

To wear an ESD protection wrist, put one end on your wrist with the metal fastener
on it in close contact with the skin, and fasten the other end to the ESD protection
earth ground fastener on the right mounting ear of the subrack.

1.1.3 Plugging and Unplugging Cards

u Before plugging / unplugging a card, you need to wear ESD protection gloves
or the ESD protection wrist strap, and keep your hands dry and clean.

u When taking a card, do not touch the devices and wiring troughs on it.

u Before inserting a card, pay attention to the following aspects:

4 Confirm that the slot to contain this card is available.

4 Confirm that this card is not connected with wires and cables or optical
fibers.

4 Confirm the insertion direction of this card, and do not insert the card in the
opposite direction. The side with the card name should be placed
downward.

u When inserting a card, pay attention to the following aspects:

4 Operate the card gently to avoid distorting pins on the subrack backplane.

4 Slide the card gently along the slide rails to avoid distorting pins on the
backplane. The slide rails are shown in Figure 1-2.

u Before unplugging a card, ascertain whether this card carries services.

Unplugging an in-service card can cause interruption of services.

4 Version: A
 1 Overview of Troubleshooting

(1) Upper slide rail (2) Lower slide rail

Figure 1-2 Slide rails

1.1.4 Operation Safety Rule of a Fiber and an Optical

Interface

Operating on a fiber or an optical interface in an incorrect way can cause bodily

harm. The following introduces the precautions when connecting fibers and cleaning
fiber connectors.

Version: A 5
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Using the special fiber puller

Optical fibers are easily damaged if they are plugged or unplugged by hand without
using any tool.

Caution:

A dedicated fiber puller is required for plugging and unplugging fibers.

The fiber puller, as the delivery accessory, is similar to tweezers in appearance and
attached with a spring cord, as shown in Figure 1-3.

The fiber puller has been installed on the cabinet with the spring cord before delivery.
Clip the fiber connector with the fiber puller to plug and unplug fibers.

(1) Spring cord (2) Connected to the installation (3) Fiber puller
hole on the vertical mounting
flange

Figure 1-3 Dedicated fiber puller

Protecting optical modules against high optical power

Do not insert the pigtail into the card’s optical interface when the pigtail’s Tx optical
power is unknown. To avoid damage to optical modules, just put the pigtail in the
card’s optical interface without connecting them or add an attenuator.

6 Version: A
 1 Overview of Troubleshooting

Connecting optical fibers

u Check the optical power before connecting fibers. Connect the optical fibers
only when the optical power meets the power requirements of the optical
interfaces. See product description for optical power specifications of all rates
of optical modules.

u Before connecting optical fibers, check whether the optical fiber connector
matches the optical interface. If the optical fiber connector does not match the
optical interface, use a compatible connector.

Protecting eyes

High optical power can cause bodily harm, especially to eyes. Never look directly
into the end of the optical transmitter fiber jumper or the end of its active connector

Avoiding excessive bends of the fiber

Exercise care if you must bend fibers. If bends are necessary, the fiber bending
radius should never be less than 38mm.

Protecting optical interfaces and connectors

u If an unused optical interface or pigtail is found without an anti-dust cap, put an

anti-dust cap on it. Prevent dust from entering the optical interface or connector.
To protect your eyes, never look into the optical interface or connector directly.

u Cover the optical interfaces of the replaced cards with anti-dust caps to keep
the optical interfaces clean.

Cleaning

While cleaning fiber connectors or active connectors, you should use dedicated
cleaning tools and materials.

The following lists some common tools; the maintenance staff can choose to
prepare some of them.

u Dedicated cleaning solvent (the first choice is the isoamyl alcohol and the
second choice is the isopropyl alcohol )

u The non-woven lens tissue

Version: A 7
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

u Dedicated compressed air

u Cotton swab (cotton for medical purposes or other long-staple cotton)

u Dedicated reel connector cleaner

1.1.5 Electrical Safety

The following introduces the operation precautions when implementing routine

maintenance so as to avoid the electrical accident such as shorting or grounding
failure.

Shorting

u When a short circuit occurs, a quick, significant rise in the short circuit current
will easily result in damage to the equipment and unforeseen safety problems.

u During operation, avoid metal fillings, water and other conductive materials into
the in-service equipment so as to prevent damage to electrical apparatus and
components caused by a short circuit.

u Provide comprehensive rodent-proofing devices at location where rodents

(such as rats) travel.

Grounding

u Ensure that the protection earth ground bar in the equipment room is securely
connected.

u Ensure that the equipment is well-grounded.

Equipment power supply

u The operating DC voltage range of the equipment is -40 V to -57 V.

u The DC power distribution system should have the power-off protection

measures; generally storage batteries should be configured.

u Before removing the power cable, confirm that the power supply is
disconnected.

u The power cable should not be exposed. The exposed part should be
completely covered with insulating tape.

8 Version: A
 1 Overview of Troubleshooting

u If the operation condition permits, shut down the power first and then perform
other operations.

1.1.6 Operation Safety Rules for the OTNM2000

Safe operations on the OTNM2000 server

u Use UPS power supply to avoid loss of network management data caused by
accidental power failure.

u To shut down the OTNM2000 server, first exit the operation system normally
and then shut off the power supply.

u The OTNM2000 server requires a dedicated computer. Use of unidentified

memory devices should be prohibited so as to avoid computer viruses.

u Do not delete any file in the network management system randomly or copy
any irrelevant file into the OTNM2000 server.

u Do not visit Internet via the OTNM2000 server. Doing so may increase data
flow in the net card and hence affects normal network management data
transmission or results in other accidents.

Figure 1-4 No access to Internet

u Do not modify the OTNM2000 server’s protocol settings, computer name or

LAN settings. Doing so may result in abnormal operation of network
management system.

Version: A 9
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 1-5 Do not modify IP addresses

10 Version: A
 1 Overview of Troubleshooting

Figure 1-6 Do not modify protocol settings

Version: A 11
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 1-7 Do not modify computer name

12 Version: A
 1 Overview of Troubleshooting

Figure 1-8 Do not modify LAN settings

Safe operations on the OTNM2000

u Do not disclose your username and password in any occasion or to anyone

else.

u To avoid illegal operations by lower-level users, the higher-level users can use
the authorization and domain division function to divide the network into
different management domains, and assign the management authorization of
certain domains for lower-level users.

u Do not modify the completed settings or service configuration on the

OTNM2000 during commissioning so as to avoid impact on the provisioned
service.

Version: A 13
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

u If you need to modify the service configuration, keep the following rules in mind:

4 Before modifying the configuration, read the NE data from the equipment,
so as to ensure that the configuration data of the OTNM2000 and the NE
are the same; at the same time, back up the network management data,
for restoring the data when accidents occur.

4 After modifying the configurations, back up the newest network

management data.

u Do not exit the network management system when it is working normally.

Note:

Exiting the network management system does not interrupt traffic in the
network, but precludes centralized control of the networked equipment.

1.2 Requirement for Maintenance Staff

To ensure normal maintenance of the CiTRANS 660, it is required that the

maintenance staff should master the needed theoretical knowledge and operation
skills.

1.2.1 Theoretical Knowledge

The maintenance staff should master the related theoretical knowledge, so as to

analyze and isolate faults effectively.

u Be knowledgeable of basic principles of the router.

u Be knowledgeable of causes of alarms in the system and principles of

generating the alarm signal flow.

u Be knowledgeable of the operating principles of each card.

u Be knowledgeable of the implementation principles of various functions.

14 Version: A
 1 Overview of Troubleshooting

1.2.2 Network Information of the Project

Be familiar with the network information of the project to facilitate the fault analysis
and isolation.

u Be familiar with the network condition of the project, including the distance
between stations, station type and card configuration.

u Be familiar with the service configuration, the optical fiber wiring conditions at
the ODF (Optical Distribution Frame), and the arrangement of equipment sets
in the equipment room of each station.

u Be familiar with the operating status of the equipment at the local office.

u Be familiar with the project documents and maintain them regularly.

1.2.3 Basic Operations on the Equipment

Being acquainted with the basic operations on the equipment helps you to handle
faults quickly.

u For the basic operations on the equipment, refer to routine maintenance.

u For basic operations on the OTNM2000, refer to e-Fim OTNM2000 Element

Management System Manual Set or the OTNM2000 on-line help.

1.2.4 Application of Tools and Meters

When handling faults, the maintenance staff needs to use tools and meters. List of
Tools and Meters lists the common tools and meters. Being familiar with the
application of tools and meters helps you to perform the fault analysis and handling
quickly.

Version: A 15
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

1.2.5 Collecting and Saving Field Data

The maintenance staff should master the operation methods to collect and save the
field data, so as to restore the normal service communication quickly using the
backed-up data when loss of the network management data causes service
interruption; in addition, the field data can help analyze and isolate faults when the
equipment has faults.

For the operation methods to collect and save the field data, please refer to related
chapters and sections in routine maintenance.

1.3 List of Tools and Meters

Common tools and meters used in troubleshooting are listed in Table 1-2.

Table 1-2 List of tools and meters

Tools and Meter Application

Optical power meter Tests the optical interface’s Tx and Rx optical power.

TDM error analyzer Tests TDM service errors.

SmartBits analyzer Tests Ethernet service errors.
Carries out routine maintenance and backs up network
OTNM2000
management and NE data.

Variable optical attenuator Reduces optical power reduction to protect the optical interface
(VOA) against over-high optical power

Used for loopback of an optical interface and the Rx or Tx optical

Pigtail fiber for test
power test.

Ring flange Connects pigtails.

Users should use dedicated cleaning tools and materials, so as

Optical fiber cleaning tools
to avoid damaging the optical fiber connectors.

Special fiber puller Plugs and unplugs fibers.

Air blower Cleans the anti-dust screens.

Protects sensitive components on the equipment against
ESD protection wrist strap
electrostatic discharge.

Multimeter Measures the power supply voltage of the equipment.

Measures the voltage drop of the cable terminal pairs at the the
Cable tester
maximum rated current.

16 Version: A
2 Troubleshooting Flow

The following discusses the general troubleshooting process, with which the users
can apply the related knowledge in isolating and eliminating network faults quickly
and accurately, so as to solve the common faults in various network scenarios. The
following includes these contents:

Troubleshooting Flow

Flow Description

Version: A 17
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

2.1 Troubleshooting Flow

When a fault occurs in the system, the maintenance staff can isolate the fault
quickly or seek help promptly to restore the service according to Figure 2-1.

18 Version: A
 2 Troubleshooting Flow

Figure 2-1 Troubleshooting flow

Version: A 19
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

2.2 Flow Description

The following describes the troubleshooting process mentioned in Figure 2-1 in

detail.

Recording fault symptom and backing up network management data

When handling a fault, first record the symptom of the fault (such as the related
alarms, performance events, and switching data in the OTNM2000). At the same
time, back up the network management data to facilitate the data restoration when
the fault handling operations are incorrect or fail.

Eliminating external faults

Ascertain whether the fault is caused by external factors; external factors include
the power supply problem, the optical cable problem, the equipment room
environment problem (such as the temperature and humidity), and the user
equipment problem. If so, perform related troubleshooting operations accordingly.

Analyzing, isolating, and handling the fault

u To ascertain the fault of this equipment, analyze and isolate the causes of the
fault according to Basic Principles and Methods for Fault Isolation and then
handle the fault using the corresponding troubleshooting methods.

u Do not make blind attempts to troubleshoot: If the fault is hard to isolate, please
send the related records of the fault to the FiberHome local representative or
the FiberHome technical support center (see the back cover of this manual for
the contact methods). Before the FiberHome maintenance staff provides
remote or on-site guide, do not make blind attempts to troubleshoot so as to
avoid exacerbating the fault.

u Restore services at first when a fault occurs: For faults such as the service
interruption, enable the protection channels promptly. If no protection channel
exists, use other grooming schemes, so as to restore services as soon as
possible.

Making stability observation

After the fault is eliminated, observe and record the operating status of the
equipment, so as to confirm that the equipment runs normally.

20 Version: A
 2 Troubleshooting Flow

Making troubleshooting records

Make records of the troubleshooting procedure (including the card replacement, the
software upgrade, the data modification, etc.), for convenience of future
maintenance and accumulation of maintenance skills.

Version: A 21
3 Basic Principles and Methods for
Fault Isolation

The key of troubleshooting is fault isolation. To isolate the fault point quickly and
exactly, the maintenance staff should be familiar with common methods of fault
isolation and use them comprehensively in the actual applications. The following
includes these contents:

Basic Principles of Fault Isolation

Common Methods for Fault Isolation

22 Version: A
 3 Basic Principles and Methods for Fault Isolation

3.1 Basic Principles of Fault Isolation

It is significant to isolate a fault accurately since the stations are distantly apart. After
isolating the fault accurately, you can take corresponding measures to remove the
fault.

The general principles for fault isolation are: external factors first and internal factors
later, network first and NE later, higher rate first and lower rate later, higher level first
and lower level later, common first and specific later.

u External factors first and internal factors later

When isolating a fault, users should first exclude the possible external faults,
such as broken fibers, faulty trunk cables, fault in connection with the
equipment and power supply fault.

u Network first and NE later

When isolating a fault, users should first isolate the fault to a single station as
accurately as possible.

u Higher rate first and lower rate later

The alarm signal flow shows that the higher rate signal alarms usually cause
the lower rate signal alarms. Therefore, users should eliminate any fault in
higher rate signals first.

u Higher level first and lower level later

Analyze higher level alarms such as urgent alarms and major alarms first, and
lower level alarms such as minor alarms and common alarms later. Classify the
associated alarms with different priority, and handle them respectively.

u Common first and specific later

Analyze a fault according to the extent of its influence, determining whether it is

a common one or a specific one. Users need to determine whether the fault
occurs on one card or multiple cards; as for the optical interface card with
multiple optical interfaces, users need to determine whether errors occur on
one or multiple optical interfaces.

Version: A 23
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

3.2 Common Methods for Fault Isolation

In troubleshooting, it is the first step to isolate the fault accurately and quickly.

The common methods for fault isolation are as follows:

u Layer-by-layer method

u Block-by-block method

u Section-by-section method

u Alarm and performance event analysis

u Loopback

u Substitution

u Meter test

Users can select from the above isolation methods for trouble shooting according to
the field situation and condition, and also can employ the methods together.

3.2.1 Layer-by-layer Method

Overview

Data are transmitted based on the physical layer, data link layer, and network layer
in the OSI (Open System Interconnection) model. Using the layering features of the
network properly, the maintenance staff can isolate faults correctly and rapidly.

The functions, common faults, and possible causes of various layers are described
as follows:

u Physical layer: Sets up the physical transmission channels between equipment

sets, so as to provide the physical media for data transmission of the upper
level protocols. The common faults of the physical layer include

4 The connection faults of the service fibers / cables and clock cables;

4 The status of a physical port of the equipment is DOWN;

4 The faults of the equipment or the cards.

u Data link layer: Implements physical addressing and data framing. The
common faults of the data link layer include

24 Version: A
 3 Basic Principles and Methods for Fault Isolation

4 The data encapsulation modes in the same data link layer are not the
same. The possible causes include

¡ The OTNM2000 is configured incorrectly;

¡ The physical layer has faults;

4 The bandwidth is occupied too much, and the network performance is

poor;

4 The clock has faults.

u Network layer: Implements route selection between subnets. The common

faults of the network layer include

4 The routing protocol has faults. The possible causes are described as
follows:

¡ The OTNM2000 modules related to the routing protocol are

configured incorrectly;

¡ The bottom faults exist.

4 The IP address and mask are configured incorrectly.

Caution:

When using the layer-by-layer method, pay attention to the following

aspects:
u Do not always perform testing operations from the bottom layer.
Select the layers to be tested according to the fault conditions.

u It is recommended that users only test one possible fault cause in a

certain step and record all operation steps in detail. This can avoid
adding difficulties of restoring the original fault status when the
following operations are invalid.

Application

The following explains the application of the layer-by-layer method via an example
of fault.

Version: A 25
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 3-1 Network diagram - layer-by-layer method

As shown in Figure 3-1, the routing protocols such as the static routing protocol are
running in the network. The maintenance staff finds that the route between P1 and
P2 is not reachable, but other protocols all run normally. Under this condition,
according to the principles of the layer-by-layer method, we can ascertain that the
fault point is at the network protocol; later, via troubleshooting operations, we find
that the incorrect modification of the route configuration by the maintenance staff
causes the fault.

3.2.2 Block-by-block Method

Overview

The OTNM2000 provides the configuration block GUI via clearly demarcated
models. This function enables the maintenance staff to classify the faults according
to the configuration block types when handling faults. The purpose of this function is
to narrow the range of fault isolation and isolate and handle faults rapidly.

26 Version: A
 3 Basic Principles and Methods for Fault Isolation

u NE configuration: the configuration blocks such as the interfaces and protocols

of each NE. It mainly includes

4 Interface configuration: configurations of all interfaces (including physical

interfaces, logical interfaces, and management interfaces) inside a certain
NE.

4 Protocol configuration: configurations of the routing protocol and label

distribution protocol.

4 Other configurations: configurations of OAM (Operation, Administration

and Maintenance), DHCP (Dynamic Host Configuration Protocol), static
ARP (Address Resolution Protocol), etc.

u Service management configuration

4 Tunnel: configurations of tunnel.

4 VC: configurations of PW (Pseudo-Wire).

4 VPN: configurations of L2VPN services, dual-homing protection.

Application

The following explains the application of the block-by-block method via an example
of fault.

Version: A 27
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 3-2 Network diagram - block-by-block method

In the network shown in Figure 3-2, after the configuration files are delivered, the
route between R1 and R2 is not reachable. Under this condition, via performing fault
isolation using the block-by-block method, the maintenance staff can ascertain the
possible causes of the fault.

u Interface configuration: for a logical interface or management interface, its IP

address or mask is configured incorrectly.

u Protocol configuration: The route is configured incorrectly or is not delivered

correctly.

28 Version: A
 3 Basic Principles and Methods for Fault Isolation

3.2.3 Section-by-section Method

Overview

The section-by-section method is described as follows: Divides the connection

between the CiTRANS 660 and the network containing the equipment into various
sections, and ascertains the possible causes of the fault section by section. This
method can narrow the searching range of fault isolation, and improve the efficiency
of fault isolation.

Figure 3-3 Diagram of section-by-section method

Generally the system is divided into the sections as follows:

u The current equipment: When the fault is navigated to a certain set of

equipment, users can divide it into the following parts to isolate the fault section
by section:

4 Service card: The possible fault causes include interface faults, card faults,
and the fault of poor contact between the card and the backplane.

4 The XCUJ2 card: The possible fault causes include external clock faults,
card faults, and the fault of poor contact between the card and the
backplane.

Version: A 29
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4 Line card: The possible fault causes include interface faults, card faults,
and the fault of poor contact between the card and the backplane.

u Client side network: the subscriber network equipment connected with the
service card at the CiTRANS 660's client side, the cable connection between
the subscriber equipment and the service card.

u Line side network: the transmission network equipment connected with the
interface card at the CiTRANS 660's line side, the optical fiber connection
between the transmission equipment and the service card.

Note:

When using the section-by-section method, users should follow the

principle "network first and equipment second". Users should first isolate
the faulty NE, and then ascertain the fault causes.

30 Version: A
 3 Basic Principles and Methods for Fault Isolation

Application

Figure 3-4 Network diagram - section-by-section method

As shown in Figure 3-4, packet loss exists in the subscriber side services. Via
testing by the meters, we ascertain that the client side and line side network of R1
both operate normally. So we can narrow the range of equipment sets and cards
related to the fault, and ascertain that the fault point is inside NE R1. Check whether
the GSJ2 card, the XCUJ2 card, and the XSJ2 card operate normally section by
section. After the GSJ2 card is unplugged and inserted again, the packet loss
disappears. Thus we can ascertain that the cause of the fault is the poor contact
between the GSJ2 card and the backplane.

Version: A 31
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

3.2.4 Alarm and Performance Event Analysis

Overview

When the system is faulty, a large number of alarms and performance events will be
generated. By analyzing the information, you can ascertain the fault type, narrow
down the search scope and save the time for fault isolation.

You can obtain the alarms and performance information in the following two ways:

u Obtaining information via the OTNM2000

Query the current alarms, alarm history, current performance events, and
performance history of the system via the OTNM2000. See Viewing
Performance and Viewing Alarms for detailed operations.

u Obtaining information via the equipment

4 Cabinet: Three indicator LEDs in different colors (red, yellow, and green)
are provided on the cabinet top. Solid red indicates an urgent alarm of the
equipment; solid yellow indicates a non-urgent alarm; and solid green
indicates input of power supply or a service call.

4 Card: Each card has the working status LEDs on its panel with different
indications. See Indicator LEDs. By virtue of the LEDs, you can ascertain
the card operation status, the alarm levels, causes of the fault, and take
measures accordingly.

Caution:

1. When obtaining alarms or performance information through the

OTNM2000, make sure that the clock of all NEs in the network is set
correctly. Otherwise, the alarms and performance events may be
reported incorrectly or not be reported at all.

2. Equipment indicator LEDs only indicate the current operation status

of the equipment, and only reflect the detected alarms. The alarms
that have ever occurred but ended now will not be indicated.

3. The indicator LEDs will not indicate the filtered alarms set on the
OTNM2000.

32 Version: A
 3 Basic Principles and Methods for Fault Isolation

The two methods to obtain alarm information should be used together in practice.
Each station cooperates with each other and is managed by the OTNM2000.
Table 3-1 compares the two ways of obtaining information.

Table 3-1 Comparison between the two ways of obtaining information (by the OTNM2000 and
by the equipment indicator LEDs)

Comparison Item OTNM2000 Indicator LED

Network management system
Operator Equipment maintenance staff
maintenance staff
Isolation function Major Coordinative
Information about a single
Information about the entire
Alarm information station, small quantity,
network, massive and precise
obscure
Alarm history On display None

Alarm time Displayed Not displayed

Performance event Displayed Not displayed

Computer, the OTNM2000,

Completely dependent Irrelevant
communication

Application

The following explains how to apply the alarm and performance analysis in a
specific example.

The network of a project is as shown in Figure 3-5. Multiple E-Line services are
established between NE1 and NE2. Ports FE1 and FE2 are used as the service
access ports. GE1 port of NE1 and GE2 port of NE2 are used as optical line
interfaces, respectively.

Version: A 33
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 3-5 Alarm and performance analysis

Fault symptom: The service between the FE1 ports of NE1 and NE2 is interrupted.
The FE1 port of NE2 reports a LINK_LOS alarm, and the current performance data
of this port indicates no packet is received.

Fault analysis: Multiple E-Line services are established between NE1 and NE2.
Only the service accessed via the FE1 ports is interrupted whereas services
accessed via other ports are normal. The optical line must be normal. That the FE1
port of NE2 reports a LINK_LOS alarm indicates that the Rx signal is lost at the FE1
port.

Through the fault analysis, the fault causes may be as follows:

u The cable connection between the user equipment 3 at NE2 side and the FE1
port is faulty or the cable itself is faulty.

u The user equipment 3 at NE2 side is faulty.

u The F1 port at NE2 side is faulty.

Procedures for fault isolation and troubleshooting:

1. Check whether the cable between the FE1 port of NE2 and the user equipment
3 is loose. If so, secure the cable to see whether the alarm is removed. If the
alarm persists, replace the cable.

34 Version: A
 3 Basic Principles and Methods for Fault Isolation

2. If the alarm still exists, check whether the user equipment 3 at NE2 side and
the NE2 equipment are faulty using the substitution method.

If the network, service and fault information is complex, a large number of alarms
and performance events will be generated following the fault for the maintenance
personnel to analyze and determine. In this case, maintenance personnel can resort
to other methods to isolate the fault and eliminate the fault with reference to the
alarms and performance events.

Some faults may not generate visible alarms or performance events (or even
generate no alarm or performance event at all). In this case, you need to isolate the
fault with other methods.

3.2.5 Loopback Method

Overview

Loopback is the most commonly used method for fault isolation. After isolating the
fault to a certain scope by the alarm and performance analysis, users can further
isolate it to a certain station or card using the loopback.

Caution:

Loopback may influence the normal transmission of the services, it is

recommended to perform the loopback at night when the service traffic is
at a relatively low volume.

The loopback operation can be divided to hardware loopback and software

loopback.

Table 3-2 Loopback related information

Loopback Mode Supported Card

Hardware loopback All interface cards

Line XSJ2, XSJ3, XGJ1, GSJ2, GSJ3, ESJ1, ESJ2, S1J1, S1O1,
Software loopback S1J4, E1J1, E1J2
loopback Equipment XSJ3, XGJ1, GSJ2, GSJ3, ESJ1, ESJ2, S1J1, S1O1, S1J4,
loopback E1J1, E1J2

Version: A 35
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

u Hardware loopback

Perform the loopback for the physical port (optical interface and electrical
interface) using pigtail fibers and loopback cables manually.

As shown in Figure 3-6, perform the signal loopback for the optical interface or
electrical interface at the client side of NE2 using pigtails or loopback cables, so
as to connect two service flows in series to facilitate the service test.

Figure 3-6 Hardware loopback (optical interface)

Compared with the software loopback, the hardware loopback is more thorough
since it loops back the signals at a port directly. However, it is inconvenient to
operate and should be performed by on-site maintenance staff. See Performing
Hardware Loopback for the operation procedures of hardware loopback.

Note:

Users should prevent overhigh Rx optical power on the optical interface

when performing the hardware loopback.

u Software loopback

36 Version: A
 3 Basic Principles and Methods for Fault Isolation

Software loopback refers to the loopback on the card performed via the
OTNM2000. The signal received at the Rx port of the local equipment is looped
back to the Tx end, so as to perform the loopback of the remote end equipment.
Using this method, the maintenance staff can perform the loopback operations
more conveniently and isolate the fault more quickly. However, the range and
position of faults isolated by software loopback is less accurate than that
isolated by hardware loopback. For example, when you perform a single station
test, if the service is tested to be normal by the equipment loopback at the
optical interface, t cannot be ascertained that the optical interface card is
normal since the equipment loopback does not involve the optical module.
However, if the service is tested to be normal after the loopback of the optical
interface using a pigtail fiber, it can be ascertained that the optical interface card
is normal.

The software loopback operation can be divided to line loopback and

equipment loopback.

4 Line loopback

Loops back the signal received at the physical port to the corresponding Tx
port for output without changing the signal structure.

See Figure 3-7 for the line loopback signal flow of the equipment card.

Figure 3-7 Signal flow of line loopback

4 Equipment loopback

Loops back the processed signal received at the physical port to the
corresponding Tx port .

Version: A 37
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

See Figure 3-8 for the equipment loopback signal flow of the equipment
card.

Figure 3-8 Signal flow of equipment loopback

Caution:

The equipment loopback will disable the DCC of the optical interface.
Performing the equipment loopback on the tributary link will make the
equipment at the local station and the succeeding stations out of the EMS
management. In this case, users should restore the DDC by resetting
optical cards at stations manually. Always be cautious during operation.

Application

The following describes the application of the loopback method with an example.

38 Version: A
 3 Basic Principles and Methods for Fault Isolation

Figure 3-9 Card connection under loopback method

Fault symptom: The client-side E1 service of NE1 is interrupted.

Fault analysis: The service signal received by NE1 from NE2 has an error. Among
the current alarms on the OTNM2000, we can find an LOF alarm on NE1 and an
E1_RDI alarm on NE2.

According to the analysis above, we can find the possible fault causes including

u The E1 cable is faulty;

u The NE cross-connect card of the NE1 is faulty;

u The ESJ1 card of NE1 is faulty.

After listing the possible causes of the fault, eliminate the causes one by one:
Procedures of troubleshooting:

1. Check the E1 cable connection. Reconnect the cable to see whether the alarm
disappears.

2. If the alarm persists, perform loopback on the ESJ1 card of NE1. If the error
disappears after the loopback, perform loopback on other cards to narrow down
the fault scope.

The loopback method can save the time of analyzing the alarm and performance
events and isolate the fault to the specific station or card quickly. It is easy for
maintenance personnel to operate.

Version: A 39
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

However, the loopback method will interrupt all the normal services in the loopback
path. This method is recommended to use only when severe faults (such as service
interruption) occur.

3.2.6 Substitution

Overview

The substitution method means to isolate and handle the fault by replacing a
possible faulty component with a normal one. The component can be a cable, a
card, or a set of equipment.

The substitution method is applicable to excluding the external faults of the

transmission equipment, such as the fibers, the connected external equipment sets,
and the power supply devices, or to excluding the card or module faults within a
station after the fault is navigated to the station.

It requires a skilled maintenance staff to execute the substitution operations

according to related specifications. To ensure that the specification of the
component used for replacement is the same as that of the possibly faulty
component, users must discriminate the related information carefully.

Note:

You had better consult the technician of FiberHome’s local representative

in advance, lest some accidents should happen during the substitution.

Application

The following explains the application of the substitution method via an example of
isolating the card fault.

40 Version: A
 3 Basic Principles and Methods for Fault Isolation

Figure 3-10 Network diagram - substitution method

As shown in Figure 3-10, the E-Line services between R1 and R2 are interrupted.
Use the substitution method to replace the possibly faulty cards or cables related to
the interrupted services in R1 and R2 step by step, until the faulty card or cable is
found. Then eliminate the fault.

The substitution method is simple and useful, with fewer technical requirements for
the maintenance staff. It is generally used in the case when the fault is narrowed
down to a certain scope but is not yet isolated to a specific card, device or cable.

However, this method requires spare parts at hand. Moreover, the operations are
not as convenient as other methods. If users do not operate according to the
operation specifications, problems such as the card damage may occur.

Version: A 41
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

3.2.7 Meter Test Method

Overview

The meter test method is generally used to isolate the external faults of the
equipment and the faults of the connection with other equipment sets. The
commonly used test meters include the optical power meter, the TDM error detector,
the multimeter, the SmartBits analyzer and the cable detector.

u An optical power meter

The optical power meter is used to measure the Tx and Rx optical power of a
card.

u TDM error detector

The error detector is used to test the errors in a transmission channel, including
the errored second, the bit error ratio, etc.

Generally, users should operate as follows: Loop back the channel to be tested,
generate pseudo random codes with the error analyzer, and check the error
condition of the tested channel by the error analyzer.

u Multimeter

The multimeter is used to measure the voltage or resistance of the suspected

faulty point, e.g., the grounding voltage of the equipment, the voltage of the
power supply.

u SmartBits analyzer

The data analyzer is used to test and analyze the Ethernet services of layers 2
and 3 and the performance of network. It has a wide test range, and the
parameters that can be tested by it include maximum wire speed, data traffic,
frame length, throughput, packet loss rate, and network delay.

u Cable tester

The cable tester is used to measure the voltage drop of the cable terminal pair
under the maximum rated current, so as to ascertain the connectivity and the
transmission quality of the cable.

Application

The following explains the application of the meter test method via an example of
isolating the fault with the SmartBits analyzer.

42 Version: A
 3 Basic Principles and Methods for Fault Isolation

Figure 3-11 Meter test method

In the process of commissioning, a large number of packets are lost in the client
side services of a certain set of the equipment. We use the SmartBits analyzer to
connect with the GSJ2 card at the client side and observe the data receiving
conditions of the meter, and no packet is lost. So we can exclude the faults at the
transmission equipment side. Combining the troubleshooting operations with the
block-by-block method, we can ascertain that the inconsistency between settings of
the operating modes for client side service ports causes the packet loss. Then we
set the port operating modes correctly, and the fault disappears.

The meter test method is persuasive in the isolation and analysis of faults.

However, it needs meters and has a tougher requirement of the maintenance staff;
in addition, the services on the tested channel will be interrupted.

Version: A 43
4 Common Operations of
Troubleshooting

The following discusses common operations of troubleshooting.

Resetting a Card

Plugging and Unplugging a Card

Replacing a Component

Performing Loopback

Cleaning an Optical Fiber Connector

Measuring Optical Power

Viewing Alarms and Performance

44 Version: A
 4 Common Operations of Troubleshooting

4.1 Resetting a Card

The CiTRANS 660 provides multiple methods for resetting the card software and
card hardware. See Table 4-1.

Caution:

Because the card reset operations can influence services on a card and
the communication with the network management system, do not perform
the reset operations randomly.

Table 4-1 Comparisons between card reset methods

Item Operation Mode Working Mode and Feature

u All hardware parameters are restored to their initial

Plugging / values. The card is electrically restarted after power
unplugging a card failure.
Hard-
u Clears all kinds of hardware and software logical faults.
ware
u The reset operations are performed to the card software.
reset Pressing the
The parameters of the card software are restored to their
RESET key on a
initial values.
card panel
u Clears all kinds of software logical faults.

u The reset operations are performed to the card software.

Issues the control
Software The parameters of the card software are restored to their
command via the
reset initial values.
OTNM2000.
u Clears all kinds of software logical faults.

4.1.1 Hardware Reset

Operation procedures

The hardware reset operations include two types:

u Resetting a card using the RESET key.

1) Press the RESET key on the card (this key is a spring return button and it
automatically releases after being pressed).

Version: A 45
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

2) Observe the ACT indicator LED on the card. If the indicator LED blinks
again after being extinguished for several seconds, the card is restarted
and electrified normally.

u Plugging / unplugging a card: See Plugging and Unplugging a Card.

4.1.2 Software Reset

Prerequisites

u The OTNM2000 can normally manage, configure, and monitor the entire
network.

u The user has obtained the network management authority with an intermediate
level or above.

Tool and instrument

The OTNM2000

Operation procedures

1. In the OTNM2000 GUI, click the NE which the card belongs to and access the
NE window.

2. Follow either method below to access the control command window:

4 In the subrack view of the NE, right-click the card, and click "Control
Command in the shortcut menu that appears; then the control command
window of this card will appear.

4 In the subrack view of the NE, click the card, and click "Control Command
in Task Panel on the right to bring up the control command window of this
card.

3. In the control command window, click the button at the right side of the reset
option. In the dialog box that appears, click "Yes to complete the issuing of the
reset command.

46 Version: A
 4 Common Operations of Troubleshooting

Note:

After the operations are completed, the command manager window will
appear. It prompts whether the command is issued successfully (
represents the issuing failure, and represents the issuing success).

4.2 Plugging and Unplugging a Card

Precautions

Warning:
Do not plug or unplug a card with excessive force. Plugging / unplugging
an in-service card may influence normal operating of the equipment and
even cause service interruption.

u When replacing a card, users must plug / unplug the card correctly, so as to
avoid damaging the equipment.

u Hot insertion of the AIFJ1 / AIFJ2 card is strictly prohibited. When plugging /
unplugging the AIFJ1 / AIFJ2 card, users must shut off the corresponding
power supply output switch of the external power supply device.

u If a single set of equipment is configured with only one AIFJ1 / AIFJ2 card,
replacing this card can cause service interruption. Under this condition, it is
recommended that you conduct the replacement operations at night.

Prerequisites

None.

Tool and instrument

An ESD protection wrist strap

Version: A 47
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Operation procedures

1. Put on the ESD protection wrist strap (ensure that the plug is inserted in the
ESD protection earth grounding fastener correctly).

2. Inserting a card

1) Determine the slot to contain the card according to the equipment

configuration list.

2) Align the upper and bottom edges of the card with the slide rails inside the
slot (with the device face to the right side), and slowly push it in along the
slide rails, as shown in ① of Figure 4-1.

3) Push the card to its position until the card is inserted in its socket on the
subrack.

4) Close and secure the upper and bottom latches, as shown in ② of

Figure 4-1.

5) Complete the insertion of the card, as shown in ③ of Figure 4-1.

Figure 4-1 Installing a card

3. Unplugging a card

1) Remove the fibers and cables that are connected with the card.

2) Hold the card panel’s upper and bottom latches using both hands, as
indicated by ① of Figure 4-2.

48 Version: A
 4 Common Operations of Troubleshooting

3) Open and extend the latches to detach the card from the subrack, as
indicated by ② of Figure 4-2.

4) Hold the latches and draw out the card slowly along the slide rail, as
indicated by ③ of Figure 4-2.

Figure 4-2 Unplugging a card

4.3 Replacing a Component

During the troubleshooting process of the equipment, users generally use the
substitution method; that is, replace the suspected component with a known good
one. The components that are confirmed to have faults or need to be upgraded
should be replaced. The following discusses common operations of component
replacement, and includes these contents:

Version: A 49
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4.3.1 Replacing a Card

Caution:

Replacing a card may lead to the service interruption. It is recommended

that the operation is performed at night when service traffic is at a
relatively low volume.

Prerequisites

u The operator should have the intermediate or higher level network

management authority.

u The spare card of the same type as the card to be replaced is prepared.

u To replace the AIFJ1 / AIFJ2 card, first disconnect the external power supply for
the card.

Warning:
Do not plug / unplug the AIFJ1 / AIFJ2 card when the equipment is
running.

Tool and instrument

u The OTNM2000

u An ESD protection wrist strap

u An ESD protection bag

Procedures for replacing a card not configured with protection

1. Select a spare card: select a spare card that has the same card name, number
and software version as the card to be replaced. As for the NMUJ1 card, make
sure the DIP switches on the spare card are identical with DIP switches on the
card to be replaced as displayed on the OTNM2000.

2. Query and record the abnormal alarms and performance of the card to be
replaced.

50 Version: A
 4 Common Operations of Troubleshooting

3. Check and record the corresponding relationship of cables on the card to be

replaced.

4. Wear the ESD protection wrist strap (make sure that one end of the wrist strap
is connected to the ESD fastener of the cabinet correctly).

5. Remove the wires and cables connected to the panel of the card to be replaced
(put the anti-dust cap onto the removed optical fiber), and unplug the card. For
detailed operations, see Plugging and Unplugging a Card.

6. Put the replaced card into the ESD protection bag, and attach a maintenance
label to it. Then send it back to FiberHome headquarters according to the
address on the back cover of this manual.

7. Insert the new card and re-connect the fibers and cables. For detailed
operations, see Plugging and Unplugging a Card.

8. Observe the indicator LEDs on the new card. It takes three to four minutes for
the new card to enter into normal work. See Indicator LEDs for the status of
indicator LEDs of a card in normal work.

9. Issue the Download Device Config command to the NE to which the new card
belongs via the OTNM2000. As for the NMUJ1 card, first issue the
management configuration to the network block to which the new card belongs.

10. Obtain the status, performance and relevant data of the new card via the
OTNM2000.

11. Check the card via the OTNM2000 to make sure that the alarms caused by
the card fault is removed, the performance is in normal status and no abnormal
alarm or performance event occurs.

Procedures for replacing a card configured with protection

1. Select a spare card: select a spare card that has the same card name, number
and software version as the card to be replaced. As for the NMUJ1 card, make
sure the DIP switches on the spare card are identical with DIP switches on the
card to be replaced as displayed on the OTNM2000.

2. Query and record the abnormal alarms and performance of the card to be
replaced.

3. Check and record the corresponding relationship of cables on the card to be

replaced.

Version: A 51
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4. Wear an ESD protection wrist strap.

5. Check the status of the faulty card.

4 If the status of the faulty card is Activated, issue the card activation
command to the card to be replaced in the control command GUI, so as to
switch the services carried on it to the protection card.

Note:

If the NMUJ1 card is faulty, check whether the faulty card is in protection
status. If it is in working status, you should perform the active / standby
switch.

4 When the faulty card is in the Inactivated status, remove the fibers and
cables connected to the panel of the card and unplug the card. For
detailed operations, see Plugging and Unplugging a Card.

6. Put the replaced card into the ESD protection bag, and attach a maintenance
label to it. Then send it back to FiberHome headquarters according to the
address on the back cover of this manual.

7. Insert the new card and re-connect the fibers and cables. For detailed
operations, see Plugging and Unplugging a Card.

8. Observe the indicator LEDs on the new card. It takes three to four minutes for
the new card to enter into normal work. See Indicator LEDs for the status of
indicator LEDs of a card in normal work.

9. Issue the Download Device Config command to the NE to which the new card
belongs via the OTNM2000. As for the NMUJ1 card, first issue the
management configuration to the network block to which the new card belongs.

10. Issue the card activation command to the spare card in the control command
GUI to switch services carried by it to the new card.

11. Obtain the status, performance and relevant data of the new card via the
OTNM2000.

12. Check the card via the OTNM2000 to make sure that the alarms caused by
the card fault is removed, the performance is in normal status and no abnormal
alarm or performance event occurs.

52 Version: A
 4 Common Operations of Troubleshooting

4.3.2 Replacing an Optical Module

When the SFP (Small Form-factor Pluggable transceiver) / XFP (10-Gigabit small
Form-factor Pluggable transceiver) has faults or the type of the needed service
changes, users need to replace the optical module. The CiTRANS 660 optical
module supports the hot insertion. You can operate on the optical module which
needs replacement during the routine maintenance as required.

Prerequisite

A spare optical module of the same type as the optical module to be replaced is
prepared.

Tool and instrument

u The OTNM2000

u An ESD protection wrist strap

u An ESD protection bag

u Tools for unplugging optical modules

u Label paper and pens

u Cleaning tools for the optical fiber connector (choose selectively):

4 Dedicated cleaning solvent (the first choice is the isoamyl alcohol and the
second choice is the isopropyl alcohol )

4 The non-woven lens tissue

4 Dedicated compressed air

4 Cotton swab (cotton for medical purposes or other long-staple cotton)

4 Dedicated reel connector cleaner

4 Optical connector specialized magnifier

Precautions

u Before the SFP / XFP optical module is replaced, check whether the optical
interface where the optical module is to be replaced has been configured the
protection.

Version: A 53
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4 If the protection is not configured, replacing the optical module will cause
the service interruption.

4 If the protection is configured, replacing the optical module will not

influence the service in the normal switching condition.

u Never look directly into the end face of the optical fiber or connector when
operating the optical interface card or optical fiber.

Operation procedures

1. Put on the ESD protection wrist strap (ensure that the plug is inserted in the
ESD protection earth grounding fastener correctly).

2. Check whether the optical interface of the optical module to be replaced has
been configured the protection.

4 If the protection is configured, switch the service to the standby optical

interface, ➔Step 3.

4 If the protection is not configured, ➔Step 3.

3. Replace the optical module:

1) Mark the corresponding relationship between the optical fiber and the
optical interface and disconnect the optical fiber connecting with the optical
module.

2) Open the pull ring of the optical module as indicated by arrows in ① of

Figure 4-3.

3) Unplug the optical module, put it into the ESD protection bag, attach the
maintenance label and record the name and fault symptoms of the NE as
indicated by arrows in ② of Figure 4-3.

54 Version: A
 4 Common Operations of Troubleshooting

Figure 4-3 Unplugging the SFP / XFP optical module

4) Insert the standby optical module as indicated by arrows in ①of Figure 4-4.

5) Clean the optical fiber connector (See Cleaning an Optical Fiber Connector)
and plug it into the corresponding optical interface.

Figure 4-4 Installing the SFP / XFP optical module

4. In the OTNM2000, check the related alarms and performance events of the
card where the replaced optical module is located, so as to confirm that no
abnormal alarms and performance events are caused by the new optical
module.

Version: A 55
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4.3.3 Replacing a Pigtail

Prerequisites

The spare pigtail of the same type as the pigtail to be replaced is prepared.

Tool and instrument

u Dedicated cleaning solvent (the first choice is the isoamyl alcohol and the
second choice is the isopropyl alcohol )

u The non-woven lens tissue

u Adhesive tape

u Several plastic protection covers of corresponding types

u An ESD protection wrist strap

Operation procedures

1. Put on the ESD protection wrist strap (ensure that the plug is inserted in the
ESD protection earth grounding fastener correctly).

2. Hold the latch of the fiber connector, unplug the pigtail, and cover the fiber with
the plastic protection cover.

Note:

When unplugging multiple pigtails without marks, you should make

temporary marks for these pigtails with adhesive tape.

3. Select a spare pigtail fiber of the same type as the one to be replaced.

4. Remove the plastic protection cover of the new pigtail connector, and put it into
the protection cover box.

5. Clean the pigtail connector with the non-woven lens tissue with the cleaning
solvent.

6. Slowly insert the latches of the pigtail connector in the direction vertical to the
socket until a click is heard.

56 Version: A
 4 Common Operations of Troubleshooting

4.3.4 Replacing a Fan

Prerequisites

The CiTRANS 660's new fan unit is prepared.

Precautions

Please complete the replacement as soon as possible (within 5 minutes) to prevent

the cards from overheating and consequentially causing equipment failure.

Tool and instrument

u An ESD protection wrist strap

u An ESD protection bag

u Label paper and pens

Operation procedures

1. Put on the ESD protection wrist strap (ensure that the plug is inserted in the
ESD protection earth grounding fastener correctly).

2. Firmly depress the snap-in latch of the fan. For the location of the snap-in latch
of the fan unit, see Figure 4-5.

Figure 4-5 The snap-in latch of the fan unit

3. Draw the fan unit out steadily for a distance of 5mm so that the power is
removed from the fan.

4. Wait a minute, and then draw the fan unit out completely from the subrack, as
shown in Figure 4-6

Version: A 57
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 4-6 Removing the fan unit

5. Place the fan unit that has been replaced into the ESD protection bag. Attach a
maintenance label, which records the name of the NE and the fault symptom.

6. Hold the new fan unit and align its right and left slide rails with the right and left
slide rail grooves in the fan unit area in the subrack.

7. Push the fan unit to the inside of the subrack slowly, until the snap-in latch is
secured automatically, as shown in Figure 4-7.

58 Version: A
 4 Common Operations of Troubleshooting

Figure 4-7 Installing the fan unit

8. Observe the indicator LED of the fan panel. The ACT indicator LED should be
solid green.

9. View the alarms of the NMUJ1 card via the OTNM2000, and confirm that no fan
alarms exist.

4.3.5 Replacing the Anti-Dust Screen

Tool and instrument

u An ESD protection wrist strap

u A blower

Version: A 59
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Operation procedures

1. Wear an ESD protection wrist strap.

2. Pull the handle to drag the anti-dust screen out of the subrack, as shown in
Figure 4-8.

Figure 4-8 Removing the subrack's anti-dust screen

3. Clean the anti-dust screen with water.

4. Wipe the anti-dust screen with a dry cloth and dry it using a blower.

5. Hold the cleaned anti-dust screen by two hands and align its left and right slide
rails with the left and right slide rail grooves in the anti-dust screen area of the
subrack.

6. Push the anti-dust screen slowly until it is completely inserted into the socket of
the subrack back plane, as shown in Figure 4-9.

Figure 4-9 Installing the subrack's anti-dust screen

60 Version: A
 4 Common Operations of Troubleshooting

4.4 Performing Loopback

The loopback includes the hardware loopback and the software loopback.

u The hardware loopback is implemented manually to the physical interface

(optical / electrical interface) on site using the fiber jumper and loopback cable.

u The software loopback is implemented by issuing the loopback control

command to the equipment via the OTNM2000. The software loopback can be
further classified into the equipment loopback and the line loopback.

4.4.1 Performing Hardware Loopback

Prerequisites

None.

Tool and instrument

u Optical fiber jumper (optical interface)

u Ethernet loopback cables (for RJ-45 interface)

u E1 cables (for E1 interface)

Caution:

When you perform the hardware loopback, services in the looped-back

path, port or line will be interrupted. Be cautious of this operation.

Operation procedures

u Optical interface

Connect the Tx end and Rx end of the optical interfaces using a fiber jumper to
loop back optical signals.

Version: A 61
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 4-10 Hardware loopback (optical interface)

u Ethernet interface (RJ-45 interface)

Connect the Tx port and Rx port of the Ethernet signal using a dedicated
Ethernet loopback head to loop back Ethernet signals.

Figure 4-11 Hardware loopback (Ethernet interface)

u E1 interface

Connect the Tx port and Rx port of the E1 signal using a loopback cable to loop
back the E1 signals.

62 Version: A
 4 Common Operations of Troubleshooting

Figure 4-12 Hardware loopback (E1 interface)

4.4.2 Performing Software Loopback

Note:

When you perform the software loopback, services in the looped-back

path, port or line will be interrupted. Be cautious of this operation.

Prerequisites

u The OTNM2000 can normally manage, configure, and monitor all NEs.

u The user has obtained the network management authority with an intermediate
level or above.

Caution:

When you perform the software loopback, services in the looped-back

path, port or line will be interrupted. Be cautious of this operation.

Tool and instrument

The OTNM2000

Version: A 63
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Operation procedures

1. In the OTNM2000 GUI, click the NE which the card belongs to and enter the
NE view.

2. In the subrack view, right-click the NE and select "Control Command from the
shortcut menu to bring up the control command window.

3. Set the equipment loopback in the control command window:

4 Equipment loopback

a) In the control command tab, click the button.

b) Select "Enable in the Enable/Disable field.

c) In the "Loopback Objects field, select the links, slots, ports or lines to
be looped back.

d) Click the button next to the device loopback, and issue the
loopback command.

e) Click "Yes in the Command Warning dialog box that appears.

4 Line loopback

a) In the control command tab, click the button next to the line
loopback item.

b) Select "Enable in the Enable/Disable field.

c) In the "Loopback Objects field, select the links, slots, ports or lines to
be looped back.

d) Click the button next to the line loopback, and issue the loopback
command.

e) Click "Yes in the Command Warning dialog box that appears.

Note:

Clear the loopback: Select the loopback objects, and set Disable in the
Enable/Disable field to clear the loopback.

64 Version: A
 4 Common Operations of Troubleshooting

4.5 Cleaning an Optical Fiber Connector

Dust or dirt on the optical fiber connector end can influence the optical signal quality,
lower the system performance, and even bring silent failures that affect the reliable
operating of the equipment. Clean the connector, so as to prevent degraded
transmission performance of the equipment.

Prerequisites

It is recommended that you conduct the cleaning operations at night when the
service traffic is at a relatively low volume.

Tool and instrument

u The OTNM2000

u Cleaning tools for the optical fiber connector (choose selectively):

4 Dedicated cleaning solvent (the first choice is the isoamyl alcohol and the
second choice is the isopropyl alcohol )

4 Non-woven lens tissue

4 Dedicated compressed air

4 Cotton swab (cotton for medical purposes or other long-staple cotton)

4 Dedicated reel connector cleaner

4 Optical connector specialized magnifier

u An ESD protection wrist strap

u An optical power meter

u A special fiber puller

Version: A 65
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Note:

u To prevent laser radiation from injuring eyes, do not look into the end
face of the optical interface or fiber connector directly with naked
eyes.

u Unused optical modules must be covered with anti-dust caps, so as

to prevent the dust from entering them and influencing their
performance.

Operation procedures

1. Put on the ESD protection wrist strap (ensure that the plug is inserted in the
ESD protection earth grounding fastener correctly).

2. Via the card control command GUI of the OTNM2000, issue the laser shutdown
command to the corresponding optical interface. Then unplug the optical fiber
to be cleaned.

3. Cover the corresponding optical module with the anti-dust cap.

4. Use the optical fiber connector cleaner or other cleaning tools to clean the end
of the optical fiber connector.

5. Connect the cleaned optical fiber connector with the optical interface of the
card.

6. Via the card control command GUI of the OTNM2000, issue the laser switch-on
command to the corresponding optical interface. Then unplug the optical fiber
to be cleaned.

7. Use an optical power meter to test whether the Tx / Rx optical power is in the
normal range. For the detailed parameters and specifications of the optical
power, refer to CiTRANS 660 High-Capacity MPLS-TP Platform Product
Description.

4.6 Measuring Optical Power

An optical interface’s overhigh or overlow receiving / transmitting power may cause

equipment errors, or even damage optical components.

66 Version: A
 4 Common Operations of Troubleshooting

4.6.1 Measuring Transmitting Optical Power

Measure whether the Tx optical power of the optical interface card to be tested
meets relevant specifications, making sure that the Tx optical power of the optical
interface card is in the normal range.

Prerequisite

u The card to be tested has been installed in the subrack correctly.

u The equipment has been powered on normally.

Tool and instrument

u An optical power meter

u Pigtails with LC/PC, FC/PC and SC/PC connectors for test

u Optical fiber cleaning tools

Operation connection

The connection for measuring an optical interface’s transmitting optical power is

shown in Figure 4-13.

Version: A 67
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 4-13 Connection of optical Tx power test

Operation procedures

1. Unplug the optical fiber of the optical interface to be tested (the TX port) and
cover the optical fiber connector with an anti-dust cap.

2. Set the wavelength of the optical power meter in accordance with the operating
wavelength of the optical interface to be tested.

68 Version: A
 4 Common Operations of Troubleshooting

Caution:
To ensure normal operations of the optical power meter, please first set
the wavelength of the optical power meter in accordance with the
operating wavelength of the optical interface to be tested. Then continue
to perform the next operations.

3. Use the testing pigtail fiber that matches the interface to connect the optical
interface (the TX port) and the optical power meter.

4. Observe the reading on the optical power meter. When the reading is stable,
the optical power value at this moment is the actual mean launched power of
the optical interface to be tested.

5. Check the tested optical power according to the parameter label on the optical
module of the tested optical interface and the technical specifications in Optical
Interface Specifications.

4 The tested power is within the normal range, ➔Step 7.

4 The tested power is beyond the normal range, ➔Step 6.

6. If the mean launched power of the optical interface is tested beyond the normal
range, follow the steps below:

1) Check and clean fiber connectors.

2) Repeat Step 3 to Step 5 to measure the mean launched power of the

optical interface until the value is within the normal range.

7. Remove the cap from the original fiber connector and reconnect the fiber to the
tested optical interface (TX interface).

8. On the ODF side, test the input power transmitted by the tested card and
compare it with the tested power tested at the interface on the tested card.

4 The difference is smaller than 0.5dBm: Normal, ➔Step 9.

4 The difference is equal to or larger than 0.5dBm: Abnormal. Check the fiber.
If the fiber is faulty, e.g., the fiber is seriously bent, replace the fiber
between the tested card's optical interface and the ODF. Measure the
power again until the difference is smaller than 0.5dBm.

9. Follow Step 1 to Step 8 to test the mean launched power at all interfaces on the
equipment..

Version: A 69
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4.6.2 Measuring Receiving Optical Power

Measure whether the receiving optical power of the optical interface card meet
relevant specifications, making sure that the actual receiving optical power values of
all the optical interfaces on the equipment are in the normal range.

Prerequisite

Optical fibers at the neighboring station have been connected to the ODF of the
local station and provide optical signals to the local station.

Tool and instrument

u An optical power meter

u Pigtails with LC/PC, FC/PC and SC/PC connectors for test

u Optical fiber cleaning tools

u Optical attenuator

u Fiber flange

Operation connection

Figure 4-14 illustrates the connection diagram for testing the actual Rx optical power
at the optical interface at the local station.

Figure 4-14 Connection of optical Rx power test

1. Set the wavelength of the optical power meter so that it is consistent with the
operating wavelength of the optical interface to be tested.

70 Version: A
 4 Common Operations of Troubleshooting

2. Unplug the optical fiber that is connected to the optical interface to be tested
(RX port) of the local station. Then connect the optical interface to the optical
power meter.

3. Observe the reading on the optical power meter. When the reading is stable,
the optical power value at this moment is the actual received power of the
optical interface to be tested.

4. According to technical specifications of the optical interfaces in Optical

Interface Specifications, check whether the measured optical power is within
the normal range.

Note:
The normal range of the actually received optical power is sensitivity
+3dBm＜actually received power＜overload point -5dBm.

4 Sensitivity +3dBm＜actually received power＜overload point -5dBm:

Normal, ➔Step 7.

4 Actually received power＜sensitivity +3dBm: Abnormal, ➔Step 5 for

processing until normal.

4 Actually received power＞overload point -5dBm: Abnormal, Step 6 for

processing until normal.

5. Actually received power＜sensitivity +3dBm: Process following the steps

below.

1) Check whether the optical fiber connector, optical attenuator and the fiber
flange are contaminated.

¡ If the fiber connector is contaminated, check and clean it following the

related anti-dust and cleaning instructions of optical interfaces and
fibers in Operation Safety Rule of a Fiber and an Optical Interface.

¡ If the ODF side flange and the optical attenuator are contaminated,
replace the flange and the attenuator.

2) Repeat Step 2 to Step 4 to measure the actually received optical power at

the tested interface until the value becomes normal.

3) Resume the fiber connection of the tested optical interface.

6. Actually received power＞overload point -5dBm: Process following the steps

below.
Version: A 71
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

1) Check whether the optical attenuator is working normally.

¡ If normal, add an appropriate attenuator at the ODF side.

¡ If not normal, replace the attenuator.

2) Repeat Step 2 to Step 4 to measure the actually received optical power at

the tested interface until the value becomes normal.

3) Resume the fiber connection of the tested optical interface.

7. Follow Step 1 to Step 6 to test the actually received optical power at all
interfaces on the equipment.

4.7 Viewing Alarms and Performance

The following introduces how to view the alarms and performance during
troubleshooting.

4.7.1 Viewing Alarms

View the current alarms regularly to isolate and eliminate faults in a timely manner.

Maintenance cycle

Daily

Tool and instrument

The OTNM2000

Prerequisites

u The NE is synchronized with the OTNM2000.

u The user has obtained the network management authority with an intermediate
level or above.

72 Version: A
 4 Common Operations of Troubleshooting

Querying current alarms

1. Double-click the icon on the desktop and enter your username and
password to access the OTNM2000 window.

2. Click Alarm→Current Alarm View on the menu bar to bring up the operation
tree pane, as shown in Figure 4-15.

3. In the "Operation Tree pane, select the object to query, as shown in

Figure 4-15.

4. Click the button on the top of the object tree in the Operation Tree pane,
view the current alarms of the selected object, as shown in Figure 4-15.

Figure 4-15 Querying current alarms

5. Record the check result in the routine maintenance record sheet.

Querying alarm history

1. Double-click the icon on the desktop and enter the username and
password to access the OTNM2000 window.

2. Click Alarm→History Alarm View on the menu bar to bring up the operation
tree pane, as shown in Figure 4-16.

Version: A 73
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

3. In the "Operation Tree pane, select the object to query, as shown in

Figure 4-16.

4. Click the button on the top of the object tree in the Operation Tree pane,
view the alarm history of the selected object, as shown in Figure 4-16.

Figure 4-16 Querying alarm history

5. Record the check result in the routine maintenance record sheet.

Reference Standard

No abnormal current alarm exists on the equipment.

Fault handling

If any abnormal alarm exists in the system, refer to alarm and performance
reference for troubleshooting.

4.7.2 Viewing Performance

By querying the reported performance, users can check whether the equipment is in
steady operation status, so as to detect any silent faults as soon as possible and
deal with any abnormal situation in a timely manner. Normally the performance data
of the NMUJ1 card and the service interface card are queried.

74 Version: A
 4 Common Operations of Troubleshooting

u From the NMUJ1 card's performance data, the user can detect the abnormal
temperature or power voltage of the equipment in a timely manner.

u From the service interface card's performance data, the user can obtain the
error count of the system.

Maintenance cycle

Daily

Tool and instrument

The OTNM2000

Prerequisites

u The NE is synchronized with the OTNM2000.

u The performance parameter collection is enabled.

u The user has obtained the network management authority with an intermediate
level or above.

Note:

The performance collection function should be enabled before you can

query the performance history of the network block, NE or card.

Querying current performance

1. Double-click the icon on the desktop and enter the username and
password to access the OTNM2000 window.

2. Access the current performance display:

4 Query the NE's current performance data: Right-click the desired NE in the
Logical Tree on the left side of the OTNM2000 GUI, and select Current
Performance from the shortcut menu to bring up the current performance
display.

Version: A 75
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4 Query the card's current performance data: Click the desired card in the
NE view, and select Current Performance on the Task Panel on the right
to bring up the current performance display, as shown in Figure 4-17.

Figure 4-17 Querying current performance

3. Record the check result in the routine maintenance record sheet.

Querying performance history

1. Double-click the icon on the desktop and enter the username and
password to access the OTNM2000 window.

2. Click Performance→Performance History View on the menu bar and select

History 15-Minute Performance or History 24-Hour Performance in the
shortcut menu, as shown in Figure 4-18.

3. In the Operation Tree pane, select the object to query, as shown in

Figure 4-18.

4. Click the button on the top of the object tree in the Operation Tree pane
and select History 15-Minute Performance or History 24-Hour Performance
of the selected object, as shown in Figure 4-18.

76 Version: A
 4 Common Operations of Troubleshooting

Figure 4-18 Querying performance history

5. Record the check result in the routine maintenance record sheet.

Reference Standard

u The performance parameters such as temperature, voltage and power of the

equipment are within the normal ranges. Table 4-2 lists the recommended
values.

u The equipment has no errors, packet loss or error packets. See the relevant
performance codes and names in Table 4-3.

Table 4-2 Recommended Value

Performance
Card Type Performance Name Recommended Value
Code
TEMP EMU temperature 10℃ to 50℃
Network
Power supply voltage of
management POWER -41V to -57V
cabinet
signaling control
The highest temperature in
card FAN_HTEMP 10℃ to 50℃
the cooling area of the fan

Working temperature of
LASER_TEMP 0℃ to 40℃
Optical interface laser
card See Optical Interface
IOP, OOP Input / output optical power
Specifications.

Version: A 77
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Table 4-3 Performance codes of card error, packet loss and error packet count

Performance Code Performance Name

E1_HDB3_ERR HDB3 error count
BBE_HP Higher order path block error

BBE_LP Lower order path block error

BBE_MS Multiplex section background block error

BBE_RS Regenerator section background block error

CRC_ERR The number of CRC check error packets

REI_HP Higher order path remote error indication

REI_LP Lower order path remote error indication

REI_MS Multiplex section remote error indication

JABBER Jabbers packet statistics

FRAGMENT Fragment packet statistics

STAT_OSZ Statistics of long packets

STAT_USZ Statistics of short packets

RX_DROP Number of Rx lost packets

Fault handling

For further information about abnormal performance parameters, refer to Alarm and
Performance Reference.

78 Version: A
5 Handling Network Management
Communication Faults

Network management communication faults do not influence services, but they can
preclude centralized control of the networked NEs from the OTNM2000. So users
must handle these faults promptly. The following introduces the NE communication
faults and how to handle them.

A Single NE Out of Management

All NEs in a Certain Network Block or the Entire Network Out of Management

Version: A 79
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

5.1 A Single NE Out of Management

The following introduces the common troubleshooting methods and procedures of a

single NE out of management.

5.1.1 Background Information

At present, the network management system generally communicates with NEs

using the TCP / IP protocol. The proper planning of IP addresses and correct setting
of IP protocol stack parameters for each NE are prerequisites for monitoring the
equipment via the network management system. For the methods of IP address
planning and IP protocol stack parameter setting of each NE, refer to e-Fim
OTNM2000 Element Management System Operation Guide.

5.1.2 Cause of Fault

The possible causes for the fault of a single NE out of management are described
as follows:

u The NE’s IP setting is incorrect or is modified by mistake.

u The NE’s IP address conflict exists.

u The channel faults exist on the line cards of the NE.

u The clock and cross-connect card or the OTNM2000 signaling control card is
faulty.

u The line fiber has faults.

u The power supply of the NE is faulty.

5.1.3 Troubleshooting Procedures

1. Eliminate external faults.

1) Check whether the NE’s power supply is faulty: If so, troubleshoot the
power supply faults.

80 Version: A
 5 Handling Network Management Communication Faults

2) Check whether the NE’s line fiber is interrupted: If so, troubleshoot the line
faults.

2. Eliminate faults of the ONTM2000 signaling control card and the IP settings.

1) Ping the NE via the OTNM2000 to read the NE status. If ping fails or the
NE status cannot be retrieved, unplug and replug the NMUJ1 card. If the
problem persists, replace the NMUJ1 card.

2) Check the NE’s IP setting: If it is incorrect, set the NE’s IP correctly

according to the IP address assignment table (one of the project design
documents).

3. Eliminate faults of the clock and cross-connect card: View whether the clock
and cross-connect card generates abnormal alarms. If so, first handle the
alarms of the clock and cross-connect card.

4. Eliminate faults of the line card: View whether the line card (it is used to
transport the MCC information) generates abnormal alarms. If so, first handle
the alarms of the line card.

5. Contact the after-sales engineer of FiberHome to perform the troubleshooting.

5.2 All NEs in a Certain Network Block or the

Entire Network Out of Management

The following introduces the common troubleshooting methods and procedures of

all NEs in a certain network block or the entire network out of management.

5.2.1 Background Information

At present, the network management system generally communicates with NEs

using the TCP / IP protocol. The proper planning of IP addresses and correct setting
of IP protocol stack parameters for each NE are prerequisites for monitoring the
equipment via the network management system. For the methods of IP address
planning and IP protocol stack parameter setting of each NE, refer to e-Fim
OTNM2000 Element Management System Operation Guide.

Version: A 81
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

5.2.2 Cause of Fault

The common causes for the fault of all NEs in a certain network block or the entire
network out of management are described as follows:

u Faults of the directly-connected NE.

u The network cable between the directly-connected NE and the HUB is broken
or the port on the HUB is faulty.

u The directly-connected NE’s IP setting is incorrect or is modified by mistake.

u The optical cable is faulty.

u The gateway NE is connected with too many non-gateway NEs.

u The OTNM2000's IP setting is incorrect.

Note:

Directly-connected NE: the NE that communicates with the OTNM2000

directly or via the HUB.

5.2.3 Troubleshooting Procedure

1. Eliminate external faults.

1) Check whether the directly-connected / gateway NE’s power supply is

faulty: If so, troubleshoot the power supply faults.

2) Check whether the gateway NE’s line fiber in each direction is broken: If so,
troubleshoot the fiber interruption.

2. Eliminate faults of the NMUJ1 card and the IP settings of the gateway NE.

1) Ping the NE via the OTNM2000 to read the NE status. If ping fails or the
NE status cannot be retrieved, unplug and replug the NMUJ1 card. If the
problem persists, replace the NMUJ1 card.

2) Check the gateway NE’s IP setting: If it is incorrect, set the gateway NE’s
IP correctly according to the IP address assignment table (one of the
project design documents).

3. Eliminate the gateway NE’s network cable and HUB faults.

82 Version: A
 5 Handling Network Management Communication Faults

1) Check the network cable connection between the gateway NE and the
HUB: If the connection becomes loose, secure the network cable.

2) Check the network cables connected with the gateway NE.

¡ If abnormal, replace the network cables to see whether the fault

disappears.

¡ If all network cables are normal, replace the HUB and check whether
the fault disappears.

4. Eliminate faults of the clock and cross-connect card of the gateway NE: View
whether the clock and cross-connect card generates abnormal alarms. If so,
first handle the alarms of the clock and cross-connect card.

5. Eliminate the OTNM2000 computer’s IP setting faults: You should pay attention
to the TCP / IP properties of each NIC and the configuration of the OTNM2000
management program on the OTNM2000 host. For the basic configuration
rules, refer to e-Fim OTNM2000 Element Management System Operation
Guide.

6. Contact the after-sales engineer of FiberHome to perform the troubleshooting.

Version: A 83
6 Handling Errors and Packet Loss

To handle errors and packet loss, you need to know the causes of these faults, and
handle them following proper steps. The following introduces information related to
errors and packet loss, and how to handle them.

Background Information

Cause of Fault

Troubleshooting Procedure

84 Version: A
 6 Handling Errors and Packet Loss

6.1 Background Information

When only a few errors and lost packets exist in the network, the affected services
are kept in a limited range. But the maintenance staff should isolate and eliminate
the errors and packet loss promptly, so as to prevent the faults from accumulating
and leading to service interruption.

6.2 Cause of Fault

The possible causes of errors and packet loss include

u External environment factors:

4 The equipment room does not provide stable input voltage for the
equipment .

4 The equipment room temperature is too high or too low.

4 The equipment is not grounded correctly.

4 Strong interference sources exist near the equipment.

u Physical connection faults:

4 The contact between the pigtail fiber / cable and the equipment is poor.

4 The ring flange is loosened.

4 The contact between the service interface card / clock and cross-connect
card / line card and the subrack backplane is poor.

u Equipment faults:

4 The service interface card, clock and cross-connect card, or line card has
faults.

4 The fan unit has faults.

u Abnormal optical power:

4 The optical interface module has faults.

4 The fiber connector or the optical interface connector is dirty.

4 The optical fiber has faults.

u The synchronization performance of the network clock is poor.

Version: A 85
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

6.3 Troubleshooting Procedure

1. Analyze the fault phenomena: Ascertain the possible causes of the fault
according to the fault conditions.

Multiple factors can cause error and packet loss. So the maintenance staff
should use the related knowledge to perform ascertaining and find out the
regular pattern of the error and packet loss, so as to handle the fault correctly
and rapidly. For example:

4 If all channels in a certain NE generate errors and lose packets, suspect a

fault in the clock and cross-connect card.

4 If only a certain channel at the client side generates errors and loses
packet, suspect a fault in the service card / clock and cross-connect card
at the client side or the previous clock and cross-connect card.

4 If the services related to a line card inside a certain NE all has faults,
suspect a fault in this card, the optical module of this card, or the line fiber
connected with it.

2. Isolate and eliminate faults correctly: Isolate the fault points with the generally
used fault isolation methods.

4 Query alarms and performance: Ascertain the lines generating errors and
losing packets rapidly via using the alarm and performance query functions
of the OTNM2000.

4 Section-by-section method: Use the section-by-section method to exclude

faults section by section, so as to isolate the fault point to a narrow range.

4 Substitution method: The substitution method means to replace a possible

faulty card or optical module with an identical spare.

Caution:

Replacing a service card or clock and cross-connect card without

protection configuration can cause complete interruption of services, so it
is recommended that you perform related operations at night when
service traffic is at a relatively low volume.

3. Record the phenomena of this fault event and the corresponding handling
procedure.

86 Version: A
7 Handling Abnormal Optical Power
Faults

An optical interface’s overhigh or overlow receiving / transmitting power may cause

equipment errors, or even damage optical devices. To handle the faults, you need to
know the causes of these faults, and then handle them following proper steps. The
following introduces the abnormal optical power faults and how to handle them.

Background Information

Cause of Fault

Troubleshooting Procedure

Version: A 87
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

7.1 Background Information

During the start-up and daily maintenance of the CiTRANS 660, to isolate the
optical power abnormal points in the system quickly and correctly, you should be
familiar with the specifications on the input and output optical power of various types
of optical modules.

An optical interface’s overhigh or overlow receiving / transmitting power may cause

equipment errors, or even damage optical devices. The common faults that are
caused by the abnormal optical power are described as follows:

u Overlow optical power: It can cause errors and packet loss of the services, and
can even lead to complete service interruption.

u Overhigh optical power:

4 It can cause errors and packet loss of the services, and can even lead to
complete service interruption.

4 It can damage optical receiving devices.

Note:

See Optical Interface Specifications for optical power specifications.

7.2 Cause of Fault

The causes of abnormal optical power are listed in Table 7-1.

Table 7-1 Common causes of abnormal optical power faults

Category Cause
Line performance is degraded.

The pigtail fiber attenuation is overhigh (due to bending, pressing,

External causes binding, or a dirty connector).

The connection of pigtail fibers is incorrect.

The optical fiber connector is contaminated.

A card fails or has performance degradation.

Equipment causes
The optical interface is contaminated.

88 Version: A
 7 Handling Abnormal Optical Power Faults

7.3 Troubleshooting Procedure

1. Check the external faults: Check whether the Tx optical power of the client side
equipment is normal.

4 Normal: The fiber between the optical interface card and client side
equipment is faulty or the connection is incorrect. Check the pigtail, fiber
connector and line attenuation of the equipment in sequence and exclude
the faults.

4 Abnormal: Contact the client and troubleshoot the client side equipment.

2. Check the equipment: Check whether the optical module of the local
equipment.

4 Normal: The card is faulty or its performance is degraded. Replace the

card according to Replacing a Component.

4 Abnormal: Replace the SFP or the XFP optical module of the card.

3. If the problem persists, contact the after-sales engineers of FiberHome for

troubleshooting,

Version: A 89
8 Handling L2VPN Service Interruption

In terms of service type, the L2VPN service interruption can be classified into CES
interruption and Ethernet service interruption. To handle the faults, you need to
know the causes of these faults, and then handle them following proper steps. The
following introduces L2VPN service interruption and how to handle it.

Handling CES Interruption

Handling Ethernet Service Interruption

90 Version: A
 8 Handling L2VPN Service Interruption

8.1 Handling CES Interruption

The following introduces CES service interruption and how to handle it.

8.1.1 Background Information

The CiTRANS 660's CESs include transparent transmission of E1 emulation service

and STM-1 emulation service. Common CES failure types include

u Physical connection faults;

u Card failure;

u Incorrect configuration.

8.1.2 Cause of Fault

The common causes of CES interruption are listed in Table 8-1.

Table 8-1 Common causes of CES interruption

Category Cause
Card hardware failure or the inter-card communication failure.
Signal loss or degradation received at the interface card or the
CES service interruption processing card.

Service physical link failure.

Loopback set at the port.

Overlow configuration of interface traffic limit.

CES error and
Inconsistency of configuration between the source and sink
communication quality
ports.
degradation
The NE's synchronization clock source failure.

8.1.3 Troubleshooting Flow

See the troubleshooting flow of CES interruption in Figure 8-1.

Version: A 91
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 8-1 Troubleshooting flow of CES interruption

92 Version: A
 8 Handling L2VPN Service Interruption

8.1.4 Troubleshooting Procedure

1. Isolate the possible station where service failure occurs.

4 Alarm and performance analysis: As loopback affects the normal service,

normally we analyze the alarms and performance data first to isolate the
possible station where the CES failure occurs.

4 Loopback: If possible, narrow down the search scope and isolate the
specific station where the CES failure occurs using the loopback method.

2. Isolate the faulty point.

After isolating the faulty station, refer to Cause of Fault to exclude suspected
faulty points. Follow the sequence to check and analyze:

1) Check whether alarms of card hardware failure such as CARD_ABSENT,

COMFAIL, FAIL/FAIL and TEMP_OVER occur.

2) Check whether alarms of card signal receiving failure such as LINK_LOS

and SPI_LOS occur.

3) Check whether alarms of fiber failure such as IOP_HIGH/IOP_HIGH,

IOP_LOW/IOP_LOW, LASER_TF and RLOS occur.

4) Check whether alarms of optical module failure such as TF and

LASER_TCT occur.

5) Check whether alarms of clock failure such as AU_LOP and LTI occur.

6) Check whether alarms of loopback configuration failure such as LOOP or

LOOPL occur.

7) Check whether alarms of port configuration failure such as

CFG_MISMATCH / CFG_MISMATCH occur.

3. Exclude the faults.

Refer to Troubleshooting Flow and Alarm and Performance Reference to

eliminate relevant faults.

4. The fault still persists.

Contact the after-sales engineer of FiberHome to perform the troubleshooting.

Version: A 93
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

8.2 Handling Ethernet Service Interruption

The following introduces Ethernet service interruption and how to handle it.

8.2.1 Background Information

The CiTRANS 660 cards with FE, GE or XGE interfaces all support Ethernet
services. The common Ethernet service failures include

u Ethernet service interruption

u Ethernet service quality degradation

8.2.2 Cause of Fault

The common causes of Ethernet faults are listed in Table 8-2.

Table 8-2 Common causes of Ethernet faults

Category Cause
Card failure or the inter-card communication failure.
Communication loss or degradation.

Ethernet service interruption Service physical link failure.

Loopback set at the port.

Service configuration failure.

Overlow configuration of interface traffic limit.

Card failure.
An abnormal optical power failure.
A rise in packet loss rate and a
Unclean fiber connector or incorrect connector.
decrease of communication
Optical cable or pigtail failure.
quality of the Ethernet service.
Abnormal card temperature.

Inconsistency of configuration between the source and sink

ports.

8.2.3 Troubleshooting Flow

See the troubleshooting flow of Ethernet service interruption in Figure 8-2.

94 Version: A
 8 Handling L2VPN Service Interruption

Figure 8-2 Troubleshooting flow of Ethernet service interruption

8.2.4 Troubleshooting Procedure

1. Isolate the possible station where service failure occurs.

Version: A 95
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

4 Alarm and performance analysis: As loopback affects the normal service,

normally we analyze the alarms and performance data first to isolate the
possible station where the Ethernet service failure occurs.

4 Loopback: If possible, narrow down the search scope and isolate the
specific station where the Ethernet service failure occurs using the
loopback method.

2. Isolate the faulty point.

After isolating the faulty station, refer to Cause of Fault to exclude suspected
faulty points. Follow the sequence to check and analyze:

1) Check whether alarms of card hardware or inter-card communication

occur.

¡ Check whether alarms of card hardware failure such as CARD_TCT/

CARD_TCT, COMFAIL, FAIL/FAIL and TEMP_OVER occur.

¡ Check whether alarms of card signal receiving failure such as

ETH_LOC and LINK_LOS occur.

2) Check whether Rx signal loss or degradation occurs.

¡ Check whether alarms of fiber failure such as IOP_HIGH/IOP_HIGH,

IOP_LOW/IOP_LOW, LASER_CCT and RLOS occur.

¡ Check whether alarms of optical module failure such as TF and

LASER_TCT occur.

3) Check whether the statuses of the Ethernet interface and the interface at
the opposite equipment are consistent.

¡ Check whether alarms of incorrect Ethernet connection such as

ETH_LOC occur.

¡ Check the flow control and MTU values set at both ends of the line.

4) Check whether loopback is set at the ports.

5) Check whether alarms of loopback configuration failure such as LOOP or

LOOPL occur. Check the service configuration at both ends of the link.

6) Check whether alarms of port configuration failure such as

CFG_MISMATCH / CFG_MISMATCH occur.

7) Check the link service VLAN, VPWS, VPLS and flow configuration.

96 Version: A
 8 Handling L2VPN Service Interruption

¡ Check whether Ethernet service failure caused by update or deletion

of configuration exists.

¡ Check the line service VLAN, VPWS, VPLS and flow configuration
and redeliver the cross-connect configuration.

3. Exclude the faults.

Refer to Troubleshooting Flow and Alarm and Performance Reference to

eliminate relevant faults.

4. The fault still persists.

Contact the after-sales engineer of FiberHome to perform the troubleshooting.

Version: A 97
9 Handling QoS Failure

QoS (Quality of Service) provides a network security mechanism to solve network

delay and congestion. The following introduces QoS faults and how to handle them.

Background Information

Cause of Fault

Troubleshooting Flow

Troubleshooting Procedure

98 Version: A
 9 Handling QoS Failure

9.1 Background Information

QoS (Quality of Service) provides a network security mechanism to solve network

delay and congestion. When the network is overloaded or congested, the QoS can
guarantee the important service free of being delayed or discarded, and ensure an
efficient network operation. Common QoS failure types include

u Committed bandwidth insufficiency.

u Service bandwidth of higher quality level preempted.

u Unavailable diffserv (Differentiated Services) for users.

9.2 Cause of Fault

Common causes of QoS faults are listed in Table 9-1.

Table 9-1 Common causes of QoS faults

Category Cause

Card failure. Card failure and service capability restricted.

Committed bandwidth insufficiency.

Service bandwidth of higher quality level

Service QoS configuration invalidity and flow
preempted.
out of control.
Unavailable diffserv (Differentiated Services)
for users.

9.3 Troubleshooting Flow

See the QoS abnormality troubleshooting flow in Figure 9-1.

Version: A 99
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 9-1 Troubleshooting flow of QoS abnormality

9.4 Troubleshooting Procedure

1. Isolate the faulty station.

Alarm and performance analysis: Analyze the network alarms and performance
data according to failed service information to isolate the possible station where
the QoS abnormality occurs.

2. Isolate the faulty point.

After isolating the faulty station, refer to Cause of Fault to exclude suspected
faulty points. Follow the sequence to check and analyze:

1) Check whether card hardware failure exists.

Check whether alarms of card hardware failure such as CARD_TCT/

CARD_TCT, COMFAIL, FAIL/FAIL and TEMP_OVER occur.

2) Check whether the service's QoS configuration has expired.

100 Version: A
 9 Handling QoS Failure

¡ Check the NE's QoS configuration, including traffic bandwidth, priority,

queue buffering management and queue scheduling policy. Check
whether the QoS configuration is correct and applicable to the current
requirements.

¡ Check whether the Tunnel, PW and traffic bandwidth configuration

meets the service traffic requirements.

¡ Check whether alarms of configuration failure such as

CFG_MISMATCH / CFG_MISMATCH occur.

¡ Check whether alarms of optical module and optical fiber connection

failure such as TF and LASER_TF occur.

3. Exclude the faults.

Refer to Troubleshooting Flow and Alarm and Performance Reference to

eliminate relevant faults.

4. The fault still persists.

Contact the after-sales engineer of FiberHome to perform the troubleshooting.

Version: A 101
10 Handling Network Level Protection
Switching Faults

Users should handle network level protection switching faults promptly. If these
faults are not handled in a real-time manner, the protection switching of key services
may fail, and even lead to service interruption. The following introduces the network
level protection switching faults and how to handle them.

Background Information

Cause of Fault

Troubleshooting Flow

Troubleshooting Procedure

102 Version: A
 10 Handling Network Level Protection Switching Faults

10.1 Background Information

The common network level protection switching failure types include

u The entire network does not enter the protection switching status or the
protection switching status is incorrect when the protection switching is needed.

u Switching is conducted without any reason when the entire network is working
normally.

u In the protection switching status, the services of the entire or partial network
are interrupted.

10.2 Cause of Fault

The common causes of the network level protection switching fault are listed in
Table 10-1.

Table 10-1 Common causes of the network level protection switching fault

Category Cause
The optical fibers are not correctly connected.

The switching protocol is abnormal.

External causes
The command of locking to the main or locking the working
channel is delivered manually.

The entire network services are not correctly configured.

Data configuration
The protection parameters are not correctly set.

The protection path of the line interface card has faults.

Equipment causes
The clock and cross-connect card has faults.

10.3 Troubleshooting Flow

The troubleshooting process for a network level protection switching fault is shown
in Figure 10-1.

Version: A 103
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 10-1 Troubleshooting flow of the network level protection switching failure

104 Version: A
 10 Handling Network Level Protection Switching Faults

10.4 Troubleshooting Procedure

1. Isolate the line and the station where the network level protection switching
occurs.

Alarm and performance analysis: Analyze the network alarms and performance
data according to failed service information to isolate the possible station where
the network level protection switching failure occurs.

2. Isolate the faulty point.

After isolating the faulty station, refer to Cause of Fault to exclude suspected
faulty points. Follow the sequence to check and analyze:

1) Check whether the protection switching protocol is normally enabled and

whether the protection switching succeeds when network abnormality
occurs.

¡ Query the current status of each NE via the OTNM2000: If the SWR
alarm occurs at multiple adjacent NEs in the network, the switching
protocol processing is normal. Follow the ordinary service interruption
handling procedure to check whether the card is faulty.

¡ Check the fiber connection: According to the network topology, check

the fiber connection of the entire network. Reconnect the fibers if they
are incorrectly connected.

¡ Check the switching parameters of each NE to see whether any NE

loses its parameters. If normal, check the optical interface card and
the clock and cross-connect card.

¡ Check whether forced commands such as locking to the main are

delivered manually: Query whether the LOCK_MAIN alarm of the
corresponding protection occurs at both ends of the clock and cross-
connect cards. If so, clear the corresponding switching command at
the clock and cross-connect card's control command GUI.

2) Check whether the protection switching protocol is normally enabled and

whether abnormal protection switching occurs when the network is normal.

Version: A 105
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Check whether forced switching or manual switching commands are

delivered manually: Query whether the FORCE_SWITCH or
MANUAL_SWITCH alarm at both ends of the clock and cross-connect
cards occur. If so, clear the corresponding switching command at the clock
and cross-connect card's control command GUI.

3) Check whether the service is interrupted after the protection switching

occurs.

¡ Exclude the protection channel fault: Query whether the abnormal

alarms and performance such as VC_LOC, VP_LOC, ETH_LOC,
VP_AIS and VC_AIS exist at the protection related NE interface cards.
Eliminate such faults to see whether the problem is solved.

¡ Exclude the protection line fault: Query whether the fiber line alarms
such as IOP_HIGH/IOP_HIGH, IOP_LOW/IOP_LOW, LASER_CCT
and RLOS exist at the protection related NE interface cards.

3. Exclude the faults.

Refer to Troubleshooting Flow and Alarm and Performance Reference to

eliminate relevant faults.

4. The fault still persists.

Contact the after-sales engineer of FiberHome to perform the troubleshooting.

106 Version: A
11 Fault Case

The following introduces how to troubleshoot faults using examples and

summarizes troubleshooting experiences.

Some Services Interrupted due to Tributary Card Failure

All Services Interrupted due to Line Card Failure

Service Interrupted due to Optical Line Failure

Version: A 107
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

11.1 Some Services Interrupted due to Tributary

Card Failure
Fault symptom

See Figure 11-1 for the network topology of this example. NE1, NE2 and NE3 form a
ring using the GSJ2 cards in Slot 06 and Slot 0D. NE1 and NE3 are connected to
the client equipment respectively. Several FE services exist between NE1 and NE3
and the service route is NE1→NE2→NE3. Some of the FE services from NE1 to
NE3 are interrupted.

Figure 11-1 Network topology of tributary card failure

Fault analysis

From the fault symptom, analyze whether the optical line (VS layer) is faulty. If so,
the services carried by the optical line are affected. In this example, the fault
symptom is described as some FE services are interrupted. The fault point is
probably not at the optical layer (VS layer). The fault causes may include

u The client side equipment is faulty.

u The line between the client side equipment and the transmission equipment is
faulty.

u The VP layer transmission channel is faulty.

u The VC layer service channel is faulty.

u The CiTRANS 660's clock and cross-connect card of the equipment is faulty.

108 Version: A
 11 Fault Case

u The CiTRANS 660's equipment's tributary card is faulty.

u The CiTRANS 660's subrack of the equipment is faulty.

Troubleshooting procedure

1. Exclude the client side equipment and line faults: Perform tests with meters on
the corresponding port of the faulty service. The result shows the Rx and Tx
data are abnormal. The client side equipment and line faults are excluded.

2. Check the VP layer transmission channel.

1) Access the OTNM2000 and open the clock and cross-connect

configuration panes of NE1 and NE3. In the In-TUNNEL-Table and Out-
TUNNEL-Table fields, check the corresponding VP layer configuration of
the faulty service. The NE3's related information is consistent with the
NE1's.

2) Set the VP layer loopback frame or CV frame.

¡ Loopback frame: In the VP-OAM-Config tab of the clock and cross-

connect card configuration pane, enable the VP layer loopback frame
for each LSP of the faulty service. See Figure 11-2 for NE1. The NE3's
related information is consistent with the NE1's.

Version: A 109
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Figure 11-2 Example of tributary card failure - VP layer loopback frame configuration

¡ CV frame: In the In-TUNNEL-Table field of the clock and cross-

connect card configuration pane, find the corresponding LSP entry of
the faulty service and enable the CV frame. See Figure 11-3 for NE1
and NE3. Enable CV frames of the faulty service channels between
NE1 and NE3 one by one.

110 Version: A
 11 Fault Case

Figure 11-3 Example of tributary card failure - VP layer CV frame configuration of NE1

3) Check the VP layer connection by querying the Rx and Tx conditions of

loopback frames and relevant alarms of CV frames.

¡ Loopback frame: Right-click the clock and cross-connect cards of NE1

and NE3, select Status Monitor from the shortcut menu to query the
VP layer OAM frame performance. If the Rx LBR frame quantity = Tx
LBM frame quantity, the corresponding VP layer connection is normal;
otherwise, the connection is faulty.

¡ CV frame: Query alarms on the clock and cross-connect cards of NE1

and NE3. If the VP_LOC (loss of MPLS-TP virtual path connection
confirmation signal) does not exist, the corresponding VP layer
connection is normal; otherwise, the connection is faulty.

3. Check the VC layer transmission channel.

1) Access the clock and cross-connect configuration panes of NE1 and NE3.
In the PW tab, check corresponding VC layer configuration of the faulty
LSP. The NE3's related information is consistent with the NE1's.

2) Set the VP layer loopback frame or CV frame.

Version: A 111
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

¡ Loopback frame: In the VP-OAM-Config tab of the clock and cross-

connect card configuration pane, enable the VP layer loopback frame
for each LSP of the faulty service. See Figure 11-4 for NE1. The NE3's
related information is consistent with the NE1's.

Figure 11-4 Example of tributary card failure - VC layer loopback frame configuration

¡ CV frame: Configure the VC layer CV frame in the PW tab of the clock

and cross-connect card configuration pane.

112 Version: A
 11 Fault Case

Figure 11-5 Example of tributary card failure - VC layer CV frame configuration

3) Check the VC layer connection by querying the Rx and Tx conditions of

loopback frames and relevant alarms of CV frames.

¡ Loopback frame: Right-click the clock and cross-connect cards of NE1

and NE3, select Status Monitor from the shortcut menu to query the
VC layer OAM frame performance. If the Rx LBR frame quantity = Tx
LBM frame quantity, the corresponding VC layer connection is normal;
otherwise, the connection is faulty.

¡ CV frame: Query alarms on the clock and cross-connect cards of NE1

and NE3. If the VC_LOC (loss of MPLS-TP virtual channel connection
confirmation signal) does not exist, the corresponding VC layer
connection is normal; otherwise, the connection is faulty.

4) Repeat the previous steps to test the VC services on the faulty LSP. Isolate
the fault to the specific card.

4. Now the fault scope can be narrowed down to an FE line card or a clock and
cross-connect card.

1) Replace the faulty card of the CiTRANS 660 using the substitution method.

Version: A 113
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

2) Re-deliver the OTNM2000 configuration to NEs and find that the FE

services between equipment sets have recovered.

Note:

1. The OAM configuration items in this example are described in

Configuration Guide.

2. After completing the parameter configuration, click Configuration→

Download Equipment Config on the main menu bar of the
OTNM2000 to deliver the configuration to the equipment.

Summary

The CiTRANS 660 has a comprehensive OAM mechanism to detect service faults
at all layers and narrow down the fault scope to a specific card.

11.2 All Services Interrupted due to Line Card

Failure
Fault symptom

The example in Some Services Interrupted due to Tributary Card Failure is applied
here and the network topology is shown in Figure 11-6. NE1, NE2 and NE3 form a
ring using the GSJ2 cards in Slot 06 and Slot 0D. NE1 and NE3 are connected to
the client equipment respectively. Several FE services exist between NE1 and NE3
and the service route is NE1→NE2→NE3. The FE services from NE1 to NE3 are all
interrupted.

114 Version: A
 11 Fault Case

Figure 11-6 Network topology of line card failure

Fault analysis

In this example, the fault symptom is described as FE services are all interrupted.
The fault point is probably at the optical layer (VS layer). The fault causes may
include

u The client side equipment is faulty.

u The line between the client side equipment and the transmission equipment is
faulty.

u The VC layer optical line is faulty.

u The CiTRANS 660 clock and cross-connect card of the equipment is faulty.

u The CiTRANS 660 line card of the equipment is faulty.

u The CiTRANS 660 subrack of the equipment is faulty.

Troubleshooting procedure

1. Exclude the client side equipment and line faults: Perform tests with meters on
the corresponding port of the faulty service. The result shows the Rx and Tx
data are abnormal. The client side equipment and line faults are excluded.

2. Exclude the optical line (VS layer) faults.

Version: A 115
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

1) Exclude the alarm information of all NE line cards that the faulty service
passes: Check whether the optical line alarms such as IOP_HIGH,
IOP_LOW, LASER_TF and LINK_LOS occur.

¡ If any, refer to Alarm and Performance Reference for troubleshooting.

¡ If none, ➔Step 2).

2) Test the line cables to see whether any cable has overhigh attenuation.
Exclude the line faults.

3) Exclude optical line faults using VC layer OAM frame. In the Demanded-
OAM-Config tab of the GSJ2 card configuration pane of NE1 and NE4,
add an OAM item, as shown in Figure 11-7.

Figure 11-7 Example of line card failure - VS loopback frame configuration

4) Right-click the clock and cross-connect cards of NE1 and NE3, select
Status Monitor from the shortcut menu to query the VS layer OAM frame
performance. If the Rx LBR frame quantity = Tx LBM frame quantity, the
VS link channel is normal; otherwise, the link channel is faulty.

5) From the above analysis, isolate the faulty optical section. Find the faulty
line card using the substitution method. After replacing the line card, all FE
services have recovered.

116 Version: A
 11 Fault Case

11.3 Service Interrupted due to Optical Line

Failure
Fault symptom

See Figure 11-8 for the network topology of this example. NE1 and NE2, NE3 and
NE4 are connected using the GSK1 cards in Slot 11 and Slot 10. NE1 and NE3
(using the GSK1 cards in Slot 11) are connected with NE5 (using the GSJ2 cards in
Slot 05 and Slot 06). NE5 (using the GSJ2 cards in Slot 08 and Slot 0D) is
connected with the client RNC equipment. The fiber in Slot 08 is used to carry
service of NE1 and NE2, and the fiber in Slot 0D is used to carry service of NE3 and
NE4.

The service of NE1 and NE2 is normal, whereas the service of NE3 and NE4 is
interrupted. No alarms are reported to the OTNM2000.

Figure 11-8 Network topology of line failure

Fault analysis

From external to internal analysis, the fault may be caused by the following factors:

u The user equipment is faulty.

u The fiber in Slot 05 or Slot 06 of NE5 is faulty.

u The fiber in Slot 11 of NE3 is faulty.

u The VP layer transmission channel between NE5 and NE3 is faulty.

u The clock and cross-connect card of NE3 or NE5 is faulty.

Version: A 117
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

u The GSK1 card in Slot 11 of NE3 is faulty.

u The GSJ2 card in Slot 0D or Slot 06 is faulty.

u The subrack of NE3 or NE5 is faulty.

Troubleshooting procedure

1. Exclude external faults of the equipment.

Check the RNC and exclude the client equipment faults.

2. Check the optical fiber links.

1) Ping the base station equipment connected to the NEs from the RNC
equipment to check the network connectivity. The base station equipment
connected to NE1 and NE2 can be pinged, whereas the base station
equipment connected to NE3 and NE4 cannot.

2) Ping each sub-NE from NE5 and find that the sub-NEs can be pinged.

3. From above operations, suspect a problem in the NE3 and NE5 equipment, or
in the connection between NE5 and the RNC equipment.

1) Check the OTNM2000 configuration of NE3 and NE5 and find that no
abnormal alarms or performance appears, but the Rx power performance
is slightly low.

2) Test the optical fiber between NE5 and the RNC equipment using an
optical power meter. The result shows the fiber Rx power in Slot 08 is
within the card's normal range, whereas the Rx power in Slot 0D is beyond
the normal range.

4. Now we can ascertain the fiber line signal is faulty.

Check the line and find that a 10GB optical attenuator is installed on the fiber in
Slot 0D connecting with the RNC equipment. Remove the attenuator and
reconnect the fiber to eliminate the fault.

Summary

Based on experience in laying out fibers for the TDM equipment in the central office,
an optical attenuator was added to the fiber in Slot 0D to avoid overhigh optical
power. However, this operation led to overlow Rx power of the card and further
caused service interruption.

118 Version: A
 11 Fault Case

Attenuators should be added only when the actually tested Rx power is beyond the
normal range of the optical receiver of the equipment (refer to Optical Interface
Specifications). Do not make subjective assumptions during installation and
construction.

Version: A 119
 Appendix A Indicator LEDs

The following introduces the indicator LEDs of the CiTRANS 660.

A.1 Cabinet Indicator LEDs

On the door lintel of the cabinet are three indicator LEDs in different colors. See
Table A-1 for the descriptions of the three indicator LEDs.

Table A-1 Descriptions of cabinet indicator LEDs

Indicator LED Status Description

Power working status indicator LED ON The equipment is working normally.

(green) OFF The equipment is not electrified.

A critical or a major alarm occurs on the

ON
Urgent alarm / major alarm indicator equipment.
LED (red) The alarm cable is connected incorrectly,
OFF
or no urgent / major alarm occurs.

ON A minor alarm occurs on the equipment.

Minor alarm indicator LED (yellow) The alarm cable is connected incorrectly,
OFF
or no minor alarm occurs.

A.2 FAN Indicator LEDs

The indicator LEDs on the fan unit are used to indicate the operating status of the
fan unit. See Table A-2 for descriptions of the indicator LEDs on the fan unit.

Table A-2 Descriptions of the indicator LEDs on the fan unit

Indicator LED Meaning Description

Operating status ON: the fan unit is electrified normally.

ACT (green)
indicator LED OFF: the fan unit is not electrified.
Solid red: an urgent alarm occurs in the fan unit.
Alarm indicator Solid yellow: a non-urgent alarm occurs in the fan
ALM (red -/ yellow)
LED unit.
OFF: no alarm occurs in the fan unit.

120 Version: A
 Appendix A Indicator LEDs

A.3 Card Indicator LEDs

The indicator LEDs on the card panels are used to indicate the operation, alarms
and other statuses of the cards.

Table A-3 LED indicators on the interface card's panel

Indicator LED Meaning Description

Blinking green: the card is working normally.

Operating status OFF: the card is working abnormally.
ACT
indicator LED Solid green: the card is working abnormally, or the
communication with the OTNM2000 is blocked.
OFF: no alarm occurs or the alarm is filtered in the
card.
Solid red: an urgent alarm (critical alarm or major
Alarm indicator alarm) occurs in the card.
ALM
LED Solid yellow: a non-urgent alarm (minor alarm)
occurs in the card.
Solid orange: both urgent and non-urgent alarms
occur in the card.
OFF: no alarm occurs or the alarm is filtered in the
NE.
Urgent / Non-
Solid red: an urgent alarm (critical alarm or major
UA / NUA urgent alarm
alarm) occurs in the NE.
indicator LED
Solid yellow: a non-urgent alarm (minor alarm)
occurs in the NE.

Version: A 121
CiTRANS 660 High-capacity MPLS-TP Platform Troubleshooting Guide

Table A-4 LED indicators on the NMUJ1 card's panel

Indicator LED Meaning Description

Blinking green (once per second): the card is

working normally.
Blinking green: the card is establishing
Operating status communication with the OTNM2000, or the
ACT
indicator LED communication with the OTNM2000 is blocked.
OFF: the card is working abnormally.
Solid green: the card is working abnormally or the
card is not configured.

OFF: no alarm occurs or the alarm is filtered in the

NE.
Urgent / Non-
Solid red: an urgent alarm (critical alarm or major
UA / NUA urgent alarm
alarm) occurs in the NE.
indicator LED
Solid yellow: a non-urgent alarm (minor alarm)
occurs in the NE.
Indicator LED for
Blinking green: the F interface is receiving data
NET the Ethernet
from the Ethernet.
communication
Blinking green: the BCT is communicating with the
NE management unit normally, or the BCT software
is upgrading.
BCT response
SBUS ON or OFF: the NE management unit cannot
indicator LED
receive response from the BCT.
Blinking randomly: some BCT is communicating
with the NE management abnormally.

MCC
Blinking green: the management plane data exists
MCC communication
on the optical line.
indicator LED
SCC
Blinking green: the control plane data exists on the
SCC communication
optical line.
indicator LED

122 Version: A
 Appendix A Indicator LEDs

Table A-5 LED indicators on the XCUJ2 / XCUJ4 card's panel

Indicator LED Meaning Description

Blinking green (quickly): the card is working

normally.
Operating status Blinking green (slowly): the card is standby.
ACT
indicator LED OFF: the card is working abnormally.
Solid green: the card is working abnormally, or the
communication with the OTNM2000 is blocked.
OFF: no alarm occurs or the alarm is filtered in the
card.
Solid red: an urgent alarm (critical alarm or major
Alarm indicator alarm) occurs in the card.
ALM
LED Solid yellow: a non-urgent alarm (minor alarm)
occurs in the card.
Solid orange: both urgent and non-urgent alarms
occur in the card.
OFF: no alarm occurs or the alarm is filtered in the
card.
Clock indicator
CKALM Solid red: an urgent clock alarm occurs in the card.
LED
Solid yellow: a non-urgent clock alarm occurs in the
card.
The LED blinks once after a card control command
Control command is issued to the card.
CTRL
indicator LED The LED is solid ON until a forced control is
cleared.
Clock locked- Solid green: the clock module is locked and the
LCKD status indicator output clock shares the same frequency with the
LED locked source.
Solid green: the clock module is in the holdover
Clock holdover-
state. The clock locked source is interrupted or
HOLD status indicator
unavailable. The output clock retains the frequency
LED
used during its locked state.

Solid green: the clock module is in the free-running

Clock free
state. The clocked source is interrupted or
FREE running-status
unavailable, and the maximum holdover time has
indicator LED
expired.

Version: A 123
 Appendix B Optical Interface
Specifications

10GE optical interface specifications

In the CiTRANS 660, the XSJ2, XSJ3 and XGJ1 cards use 10GE optical interface
modules. See Table B-1 for the parameter specifications.

Table B-1 10GE optical interface specifications

Item Specification

Optical interface type 10GBASE-LR 10GBASE-ER 10GBASE-ZR

Target distance (km) 10 40 80
Mean launched power (dBm) -6 to -1 -1 to 2 0 to 4
Central wavelength (nm) 1290 to 1330 1530 to 1565 1530 to 1565
Overload optical power (dBm) -1 -1 -7
Receiving sensitivity (dBm) -14 -17 -24
Minimum extinction ratio (dB) 6.5 8.2 9

GE optical interface specifications

In the CiTRANS 660, the GSJ2, GSJ3 and XGJ1 cards use GE optical interface
modules. See Table B-2 for the parameter specifications.

Table B-2 GE optical interface specifications

Item Specification

1000BASE-
Optical interface type 1000BASE-SX 1000BASE-LX 1000BASE-VX
ZX1
Source type MLM MLM SLM SLM
Target distance (km) 0.55 10 40 80
Mean launched power
-9.5 to 0 -8 to -3 -2 to 3 -2 to 5
(dBm)

Central wavelength
770 to 860 1270 to 1355 1275 to 1350 1500 to 1580
(nm)

Overload optical
0 -3 -3 -3
power (dBm)

124 Version: A
 Appendix B Optical Interface Specifications

Table B-2 GE optical interface specifications (Continued)

Item Specification

Receiving sensitivity
-17 -20 -23 -23
(dBm)

Minimum extinction
9 9 9 9
ratio (dB)

FE optical interface specifications

In the CiTRANS 660, the ESJ2 card use the FE optical interface module. See
Table B-3 for the parameter specifications.

Table B-3 FE optical interface specifications

Item Specification

Optical interface type 100BASE-FX 100BASE-FX 100BASE-FX

Source type SLM SLM SLM
Target distance (km) 15 40 80
Mean launched power (dBm) -14 to -8 -4 to 0 -4 to 0
Central wavelength (nm) 1265 to 1360 1265 to 1360 1480 to 1580
Overload optical power (dBm) -8 -10 -10
Receiving sensitivity (dBm) -31 -37 -37
Minimum extinction ratio (dB) 8.5 10.5 10.5

STM-1 optical interface specifications

In the CiTRANS 660, the S1J1, S1J2, S1O1 and S1J4 cards use the STM-1 optical
interface modules. See Table B-4 for parameter specifications.

Table B-4 STM-1 optical interface specifications

Item Specification

Optical interface type S-1.1 L-1.1 L-1.2

Tx optical power (dBm) -14 to -8 -4 to 0 -4 to 0
Central wavelength (nm) 1265 to 1360 1265 to 1360 1480 to 1580
Overload optical power
-8 -10 -10
(dBm)

Receiving sensitivity (dBm) -31 -37 -37

Version: A 125
 Appendix C Abbreviations

CES Circuit Emulation Service

GE Gigabit Ethernet

IP Internet Protocol
IC Integrated Circuit

LSP Label Switched Path

MPLS Multi-Protocol Label Switching

MPLS-TP MPLS-Transport Profile

PDP Power Distribution Panel

QoS Quality of Service

SFP Small Form-Factor Pluggable

XFP 10 Gigabit Small Form-Factor Pluggable

STM Synchronous Transport Module

126 Version: A
 Product Documentation Customer Satisfaction Survey
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.

Name
Phone Number
Email Address
Company

To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.

Documentation Name
Code and Version

Usage of the product documentation:

1. How often do you use the documentation?
□ Frequently □ Rarely □ Never □ Other (please specify)
2. When do you use the documentation?
□ in starting up a project □ in installing the product □ in daily maintenance □ in trouble
shooting □ Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
□ 100% □ 80% □ 50% □ 0% □ Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
□ Satisfied □ Unsatisfied (your advice)
5. Which documentation form do you prefer?
□ Print edition □ Electronic edition □ Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
□ Very □ Somewhat □ Not at all (your advice)
2. How do you like the language style of the documentation?
□ Good □ Normal □ Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
□ Yes
□ No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
□ Yes
□ No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
□ Yes (Please give an example)
□ No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?

8. Which parts of the documentation are you unsatisfied with?Why?

9. What is your opinion on the Figures in the documentation?

□ Beautiful □ Unbeautiful (your advice)

□ Practical □ Unpractical (your advice)

10. What is your opinion on the layout of the documentation?

□ Beautiful □ Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:

Satisfied (please specify)

Unsatisfied (please specify)

12. Additional comments about our documentation or suggestions on how we can improve:

Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
[email protected]