Documente Academic
Documente Profesional
Documente Cultură
Version 1.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE
CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality
obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are
disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-
infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on
the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the
subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its
licensee, the user of this document shall not acquire any license to the subject matter herein.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support
or training are subject to change without notice.
Revision History
Please fax to: (86) 755-26772236; or mail to Publications R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Your
evaluation of Accessibility:
this (Contents, Index, Headings, Numbering, Glossary)
documentation Good Fair Average Poor Bad N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good Fair Average Poor Bad N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Your Add more examples Add more/better quick reference aids
suggestions for Add more detail Improve the index
improvement
of this Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
Chapter 1................................................................................... 19
Safety Instructions.................................................................................. 19
Chapter 2................................................................................... 21
Maintenance Overview............................................................................ 21
Maintenance Classification ..................................................................................... 21
Routine Maintenance .............................................................................................................21
Performance Message Handling..............................................................................................21
Alarm Message Handling........................................................................................................21
Emergency Maintenance........................................................................................................22
Maintenance Precautions....................................................................................... 36
Card Maintenance Precautions ...............................................................................................36
Precautions in Optical Card Maintenance.................................................................................37
Precautions in Equipment Maintenance...................................................................................37
EMS Maintenance Precautions................................................................................................38
Chapter 3................................................................................... 39
Routine Maintenance .............................................................................. 39
List of Routine Maintenance Items.......................................................................... 39
Environment Maintenance ..................................................................................... 40
Equipment Room Temperature ..............................................................................................40
Equipment Room Humidity ....................................................................................................40
Dustproof Requirements of the Equipment Room....................................................................40
Clear Height..........................................................................................................................41
Wall Treatment in the Equipment Room .................................................................................41
Lighting in the Equipment Room ............................................................................................41
Chutes and Apertures in the Equipment Room........................................................................41
Equipment Power Supply.......................................................................................................41
AC Power Supply...................................................................................................................42
Air Conditioning System.........................................................................................................42
Fire Protection Facilities..........................................................................................................42
Maintenance Space ...............................................................................................................42
Chapter 4................................................................................... 59
Performance Message and Handling...................................................... 59
Performance Message Categories........................................................................... 59
SDH Interface Performance Messages ....................................................................................59
Analog Performance Messages...............................................................................................61
Ethernet Interface Performance Messages ..............................................................................61
Chapter 5................................................................................... 73
Alarm Message and Handling ................................................................. 73
Overview of Alarm Message................................................................................... 73
Alarm Categories...................................................................................................................73
Alarm Levels .........................................................................................................................73
Alarm Priorities......................................................................................................................73
Alarm Summary....................................................................................................................74
Figures........................................................................................ 227
Chapter 5 Alarm and Handling, gives the classification, severity levels, and
priorities of alarms; summarizes the alarms; describes the alarm causes
and handlings.
Typographical Conventions
ZTE documents employ with the following typographical conventions.
Typeface Meaning
Italics References to other guides and documents.
Quotes Links on screens.
Bold Menus, menu options, function names, input fields, radio
button names, check boxes, drop-down lists, dialog box
names, window names.
CAPS Keys on the keycard and buttons on screens and company
name.
Constant width Text that you type, program code, files and directory names,
and function names.
[] Optional parameters
{} Mandatory parameters
| Select one of the parameters that are delimited by it
Typeface Meaning
Click Refers to clicking the primary mouse button (usually the left
mouse button) once.
Double-click Refers to quickly clicking the primary mouse button (usually
the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button (usually the
right mouse button) once.
Drag Refers to pressing and holding a mouse button and moving the
mouse.
Safety Signs
TABLE 3 S AFETY SIGNS
Customer Support
If you have problems, questions, comments, or suggestions regarding
your product, contact us by e-mail at support@zte.com.cn. You can also
call our customer support center at (86) 755 26771900 and (86) 800-
9830-9830.
Documentation Support
ZTE welcomes your comments and suggestions on the quality and
usefulness of this document. For further questions, comments, or
suggestions on the documentation, you can contact us by e-mail at
doc@zte.com.cn; or you can fax your comments and suggestions to (86)
755 26772236. You can also explore our website at
http://support.zte.com.cn, which contains various interesting subjects like
documentation, knowledge base, forum and service request.
Safety Instructions
High temperature and high voltages exist in this equipment. Only qualified
professionals are entitled to install, operate and maintain the equipment.
Abide the local safety rules and related operation regulations during the
equipment installation, operation and maintenance, to avoid personal
injuries or equipment damages. The safety precautions in this manual are
only a supplement to the local safety rules.
Refer to Safety Signs for the signs of the safety precautions during the
equipment installation, operation and maintenance.
Maintenance Overview
Maintenance Classification
Equipment maintenance is divided into routine maintenance, performance
message handling, alarm message handling and emergency maintenance.
Routine Maintenance
Routine maintenance involves checking the equipment operation status
periodically, and handling the problems promptly; so as to find hidden
trouble, prevent accident, find fault and handle them as early as possible.
Emergency Maintenance
Emergency maintenance is also called troubleshooting. It involves
maintenance tasks brought by transmission equipment faults or network
adjustments, such as the maintenance tasks to handle equipment damage,
line faults, and emergency events found and recorded in routine
maintenance.
Maintenance Tools
Table 4 lists the maintenance tools in the equipment room.
Name Name
Tape Crimper
Screwdrivers (one each for straight/cross screwdriver
40 W Electric iron
respectively in large, medium and small sizes)
Long straight screwdriver (equipment accessory) Clamping pincers
Tweezers Chip puller
Adjustable wrench Antistatic wrist strap
Diagonal pliers Insulating tape
Sharp nose pliers Strap
Wire stripper Pliers
Scissors Fiber puller
Straight-through cable (the length depends on the actual
requirement)
Instruments/Meters
Meters for Environment Monitoring
Include thermometers and hygrometers. They should be always prepared
in the equipment room for detecting the equipment operating environment.
Other Instruments
Chip burner: For equipment upgrading, if no chips of new version are
burned, a chip burner should be prepared.
Caution: All the instruments/meters should be checked and calibrated before using,
to ensure their accuracies and good conditions.
Work Rules
1. Keep the equipment room tidy and clean. Change shoes at the door,
keep the floor clean, keep the equipment dust-free, arrange the
equipment properly; Ensure that the instruments are precise, the tools
are ready and the materials are complete.
2. Do not smoke, eat, play games, or talk loudly in the equipment room.
3. Do not put personal articles around in the equipment room, and do not
do anything irrelevant to the job.
4. Do not bring inflammable or explosive articles into the equipment room.
Unauthorized entry into the equipment room is not allowed.
5. Put on antistatic wrist strap before operating the equipment.
6. Take care of the public properties in the equipment room.
7. Do not disclose any confidential information.
8. Keep proper records and statistics of the original data. Make sure that
the technical documents and original records are authentic and
complete.
9. The person on duty must be dutiful. Handle and report any major fault
and accident promptly.
10. There should be leaders who conduct regular checks for the equipment
room, and make continuous improvement.
Caution: Once the test and diagnosis finish, the maintenance operations conducted
should be canceled in time, so that the equipment operation will not be affected.
Square bayonet
Square bayonet fiber connector
MT-RJ LC/PC
fiber connector /polished slightly
convex sphere
Note: The fiber pigtail connector type of the ZXMP S385 is LC/PC.
1. Hold the fiber pigtail plug with your thumb and forefinger; align the
spring piece on the plug with the grove of the optical interface flange;
push the pigtail inward with a moderate force. Avoid damaging the
ceramic inner pipe of the optical adaptor or the connector end surface.
1. Hold the pigtail connector with your thumb and index finger or with an
extractor, and press down the spring piece on the connector.
3. Protect the fiber pigtail plug with a dustproof cap to avoid end surface
contamination caused by the dust.
Laser: During optical fiber operation, do not look staight at the laser beam of the
optical interface or inside the optical fiber to avoid eye hurt.
Loopback
Loopback is the operation of sending information from the transmitting
interface of an NE, and receiving the information from the receiving
interface of that NE. It is a usual measure for detecting the fault of
transmission channel.
The loopback can locate the faulty point of the NE level by level in case of
separate communication links, and detect the working status of nodes and
transmission lines. It helps locate the faulty NE and even the faulty card
quickly and accurately. It also facilitates the equipment commissioning and
debugging.
Caution: The loopback may cause service interruption. Be cautious to use it.
Hardware Loopback
The hardware loopback connects the receiving/transmitting interfaces of
one signal via physical method. In terms of the signal flow direction, the
hardware loopback orients towards the equipment inside, so it is also
called hardware self-loop. The self-loops of the electrical signal and optical
signal are similar. The following content takes the optical interface
hardware self-loop as an example.
Software Loopback
The software loopback employs the EMS software to implement loopback.
It can configure not only the optical/electrical signal self-loop equivalent to
the hardware loopback, but also the line loopback or single channel
loopback.
The loopback from a line card to a line interface is called line side
loopback; The loopback in the reverse direction is called terminal
side loopback.
The loopback from a tributary card to a tributary interface is called
terminal side loopback; The loopback in the reverse direction is
called line side loopback.
Software loopback in different directions are shown in Figure 1.
Line card
Tributary card
For the ZXMP S385, the channels that can implement software loopback
include: administrative unit AU4, cascade administrative unit AU4-nc, and
tributary unit VC12.
The correspondence between loopback points and cards are listed in Table
6.
Note: The loopback principle is to minimize the effect on services. Avoid using the
AU loopback if the fault can be located via tributary unit loopback.
Fiber
pigtail
R
Optical interface of
optical line card
Optical power meter
1. Set the receiving optical wavelength of the optical power meter to the
same as the transmitting optical wavelength of the tested optical line
card.
1. Set the receiving optical wavelength of the optical power meter to the
same as the tested optical wavelength.
2. Select at the local site the fiber pigtail that connects to the
transmitting optical interface of the adjacent site. Normally, this fiber
pigtail is connected to the receiving optical interface of the optical line
card at the local site. Connect the fiber pigtail to the test input
interface of the optical power meter. Read the stable optical power
value of the optical power meter, i.e. the receiving optical power value
of this optical line card.
On-line test
Select a service channel in use, directly connect the bit error tester to
the monitoring connector of the DDF or ODF that connects with the
corresponding interface of the channel, and perform online monitoring.
Off-line test
Select a service channel, and find the PDH/SDH interface of this
channel at both the local site and the remote site.
Perform a line side loopback at the remote PDH/SDH interface via
the EMS software, or a hardware loopback on the DDF.
Perform bit error test at the corresponding PDH/SDH interface via
the bit error tester.
In normal case, the tester should show no bit error.
Caution: Make sure that the meter is well grounded. Do not turn on/off any other
electrical appliances during the test.
The correspondences between the bit error insertion points, bit error types
and cards are listed in Table 7.
TABLE 7 THE CORRESPONDENCES BETWEEN THE BIT ERROR INSERTION POINTS, BIT
ERROR TYPES AND CARDS
Insertion
Bit Error Type Card Type
Point
VC12 V5 2 M electrical tributary card and Ethernet card
VC3 B3 Ethernet card
VC4 B3 Optical line card and STM-1 electrical processor
MS B2 Optical line card and STM-1 electrical processor
RS B1 Optical line card and STM-1 electrical processor
VC3-nc B3 Optical line card
VC4-nc B3 Optical line card above STM-4
The correspondences between the alarm insertion points and cards are
listed in Table 8.
Once the alarm insertion succeeds, the AIS alarm should be reported in
the corresponding channel at the receiving end. If the insertion point is
TU3/TU12 and is configured as bidirectional service, the insertion point
should also report the Remote Defect Indication (RDI) alarm. When the
alarm insertion succeeds, if the service is not interrupted in a protected
network, it indicates that the switching is normal; if the service is
interrupted, it indicates that the switching is abnormal. Check the line and
related cards.
Switching Configuration
The ZXMP S385 can implement the multiplex section (MS) protection and
sub-network connection protection. The MS protection includes two-fiber
bidirectional MS shared protection, and 1+1/1:1 MS dedicated protection.
The sub-network connection protection includes the AU4, TU3 and TU12
levels protections. When the working sub-network connection fails or the
performance is lower than a necessary level, it will be replaced by the
protection sub-network connection.
APS start
It means that the equipment APS protocol is in normal working status, and
the MS protection ring is in the automatic protection switching status.
When the MS protection ring is configured, the APS should be started.
APS stop
It stops the equipment APS protocol, and keeps the data before the stop.
For example, if the MS protection switching has happened at a site before
the APS stop, this MS protection switching operation will be maintained
after the APS stop configuration, and the new data will not be processed.
APS reset
When the equipment receives the APS reset command, it will clear all
current APS data, save the equipment initialization data, and then return
to the normal working status, waiting for the new data and automatic
protection switching. In addition, when the equipment receives the APS
reset command, it directly enters the APS started status.
The Obliged state of the CS card command in the EMS software can be
used to set the CSA card bus used by card.
Note: All cards except for the NCP and CSA cards support operations of CS card
obliged state.
The laser of the ZXMP S385 supports two modes: open and shutdown.
When a laser is open, the optical line card is in light emitting state; when
the laser is shut down, the optical power is zero and the optical line card is
in no light state. Laser shutdown is often used to shut down an
unconnected optical interface and protects operating personnel engaged in
optical line maintenance.
Card Switching
The ZXMP S385 can implement the 1:N protection. For the NE configured
with card protection, the standby card works in standby mode when the
master card works normally. When the master card is abnormal, the
standby card switches to the active mode and works instead of the master
card, to ensure the normal services.
Card switching switches the services of the master card to the standby
card, to protect the services. Tributary cards support the card switching
operation.
Protect switching: The EMS sends this command and forces the master
card to work, no matter whether the master card works normally.
Forced switching: The EMS sends this command and forcibly switches
services to the configured card, no matter whether the card works
normally.
Manual switching: The EMS sends this command. If the configured card
works normally, the system forcibly switches services to it; otherwise,
the active card before the command is sent still works.
Clear switching: The active card will stop working once it detects
abnormality, and will notify the standby card about its status. The
standby card that works normal will switch to active status at once and
work instead of the faulty card. This command is the default EMS
configuration.
1. Short-circuit the signal core and shielded layer with a short conducting
wire or tweezers at one end of the cable, and then measure the
resistance between the signal core and shielded layer at the other end.
The resistance value got should be zero.
If the results of the above two tests are normal, the tested ends are of the
same cable, and the cable is normal. Otherwise, the cable has short-circuit
or break somewhere; the cable plug has false soldering, open solder point
or short circuit; or the tested ends are not of the same cable.
A V ie w
1
A
8
R J 4 5 p lu g R J 4 5 p lu g
A network cable has an RJ45 plug at either end. Figure 3 shows how the
pins are numbered in an RJ45 plug.
Card Reset
Card reset operations include the hardware reset and software reset.
Warning: Only reset the card to recover its normal work. Do not reset the card
unless the card function is confirmed to be affected by the processor fault.
Hardware reset
There is a reset hole with reset switch in it on the card front panel.
Press down the reset switch to reset the CPU and other chips of the
card.
Software reset
The software reset resets the card via the EMS software. The software
reset itself includes hard-reset and soft-reset.
ii. IC level: Resets application programs of the CPU and ICs on the
card
Caution: Resetting the NCP card will interrupt the EMS monitoring of the NEs.
Maintenance Precautions
Before the maintenance operations on the ZXMP S385, the operator
should learn not only the basic precautions for maintaining general
communication equipment, but also the special precautions for
maintaining transmission equipment, to ensure safety of both human and
equipment.
1. Make sure the hardware installation and cable layout are correct, the
input power of the equipment satisfies the requirement, there is no
short circuit inside the equipment, and the fan installation is correct.
2. Turn on the power supply switch for the equipment in the equipment
room.
3. Set the air switch of the power distribution box to "ON" to power on
the equipment. The green indicator light at the cabinet top should on,
the fan should run normally.
1. Set the air switch on the power distributor box to OFF to shut down
the equipment.
2. Turn off the power supply switch for the equipment in the equipment
room. Disconnect the input power supply of the equipment.
Warning: Powering off the equipment will make the equipment exit running state,
resulting in the interruption of all services of the NE. Since the transmission
equipment is very important in the network, power-off operation should be avoided
once the equipment is in service.
Never install or disconnect any power cables without turning off the
power switch. Otherwise, electric sparks or electric arc may occur,
causing a fire or eye hurt. Be sure to turn off the power switch before
installing or disconnecting a power cable.
Once the equipment is in service, pulling out the fan without reason is
forbidden. Clean the dust filter mesh of the fan regularly according to
the equipment room environment conditions to ensure good heat
dissipation of the equipment.
After the maintenance operations on the equipment, close the cabinet
door to ensure the equipment always has an excellent anti
electromagnetic-interference performance.
Routine Maintenance
Environment Maintenance
The ZXMP S385 is precise electronic equipment that requires good
equipment room environment to ensure stable and reliable operation. This
section gives the equipment room environment requirements for the ZXMP
S385. The maintenance personnel should conduct regular checks on these
items, and make immediate remedies and improvements in case of non-
conformity, so as to guarantee the normal running of the equipment.
Clear Height
The clear height of the equipment room should be no less than 3 m.
Note: Clear height of the equipment room refers to the vertical distance from the
bottom of the beam or air duct to the upper surface of the antistatic floor.
All the chutes should have damp-proof measures and well trimmed at the
edges and corners. Lay the lighting/ power cables in a hidden manner.
The routing, quantity and the layout of DC power cables installed in the
equipment room should meet the general specifications of
telecommunications projects. The conductor type (aluminum/copper bar or
rubber-skinned wire), the equipment insulation strength and the fuse
capacities should meet the design requirements.
Use complete segment cable for the power cable. No joints in the middle
of the power cable.
AC Power Supply
Prepare 220 V/2000 W AC power socket outlet in the equipment room,
since some electric tools and instruments are needed for equipment
installation, debugging and maintenance. The AC power socket outlet
should have both two-pin and three-pin multifunctional power sockets. The
socket quantities and positions should satisfy the debugging requirements
for all the equipment.
Select the air condition according to the equipment heat quantity. The
formula below is generally used for heat quantity calculation.
Q = 0 . 8 2 V A ( K W / h o u r ) , where
Maintenance Space
The front maintenance space of the ZXMP S385 should be greater than
800 mm.
The front maintenance space for two ZXMP S385 cabinets installed face to
face should be greater than 1000 mm.
Equipment Maintenance
Operations
Common equipment maintenance operations include audio alarm check,
cabinet indicator light observation, card indicator light observation, fan
plug-in box check, regular dustproof unit cleaning, and service check.
Operation Method
Generate alarms manually. For example, use EMS software to perform the
Alarm Inversion operation to check the alarm sound.
Inspection Criteria
When alarm occurs, the ZXMP S385 and the column head cabinet should
be able to make alarm sound.
Troubleshooting
Check if the ring interception switch is in the Normal state.
Check the cable connections between the alarm door panel,
ALARM_SHOW interface in the SCI card and the ring trip switch.
If the alarm of the ZXMP S385 is connected externally to the column
head cabinet, check the external alarm cable connection.
Operation Method
Observe the status of the indicator lights on the top of the cabinet.
Inspection Criteria
When the equipment works normally, only the green cabinet indicator light
on the cabinet is on. The relationships between the cabinet indicator lights
and the equipment operating status are described below:
The indicator lights of the ZXMP S385 are located in the top middle of the
cabinet front door, including red, yellow and green lights. Table 12
describes the meanings of the indicators.
Indicator Status
Name
Light On Off
Critical/major A critical or major alarm occurs No critical or major
Red light alarm indicator in the equipment, usually with alarm in the
light an audio alarm. equipment
Yellow Minor alarm A minor alarm occurs in the No minor alarm in
light indicator light equipment the equipment
Green Power indicator Equipment power supply is Equipment power
light light normal supply is cut off
Troubleshooting
When the red and yellow indicator lights of the cabinet are on, further
check the card indicator lights, and notify the EMS operators at the central
site in time to check the alarm and performance message of the
equipment.
Operation Method
Observe the status of the indicator lights of the card.
Inspection Criteria
Indicator light status of the cards
When the card works normally, only the green indicator light flashes.
The indicator light status of the ZXMP S385 common cards are
described below.
Note: The NCP card transmits running and monitor information between the NE
and EMS. Its indicator light status also indicates the running status of the current
NE. The NCP card alarms are mainly caused by the alarms of other cards.
Correspondences between the working status and the indicator light status
of the SEC card are listed in Table 20.
For the electrical interface switching cards, the green indicator light is
constantly on and the yellow light is off after the cards are powered on.
The yellow light lights up when the switching occurs, and it turns off
when the switching is cancelled.
Troubleshooting
When the red/yellow indicator light of the card is on, notify the EMS
operators at the central site in time to check the alarm/performance
message of the equipment and card.
Fan Check
Operation Purpose
Good heat dissipation function is critical for long-term normal running of
the equipment. Make sure the fan is working normally when the
equipment is running.
Operation Method
Observe the working status of the fan, and execute the Fan Config
command in the EMS software to query the configuration information of
the fan.
Inspection Criteria
The fan runs stably at regular rotation speed, and buzzes continuously
without abnormal sound.
Troubleshooting
If the fan rotates at irregular speed or has abnormal sound, check
immediately whether foreign substance exists in the fan box, and
whether the fan is damaged.
If the fan does not run, check immediately if the fan in the plug-in box
is damaged.
Operation Method
Take out the air filter from the lower part of the dustproof unit and check
it.
Inspection Criteria
The air filter of the dustproof unit is free from accrued dust.
Trouble Shooting
Clear away the accrued dust of the air filter by using clean water to scrub
the air filter and air-dry it before inserting it back to the lower part of
dustproof unit.
Operation Method
If the local site is not a central site, make order wire calls periodically
from the local site to the central site, and request the central site to
dial back, so as to test the order wire telephone.
The central site should also make order wire calls periodically to other
sites in turn to check the order wire telephones.
Inspection Criteria
The order wire calls get through among every site and can be clearly
heard without noise.
Troubleshooting
Use other method to check if the called site has ringed off.
If the called site has ringed off, check the configured data and
performance/alarm message through the EMS software, to find out the
problem and solve it.
Operation Method
In respect of idle traffic channels between two sites, the test can be
performed on the idle channels to test the traffic channel quality
between two sites.
If there is no idle traffic channel between two sites, a traffic channel
originally used for protection can be temporarily disconnected, when
the traffic is small, for accepting an error test and checking the quality
of traffic channels between the two sites.
If both of the above two circumstances are not applicable, use the EMS
software to query the service performance and alarms, and make sure
of the quality of traffic channels between the two sites.
Note: Refer to Bit Error Test for the detailed operations of bit error test.
Inspection Criteria
No bit error exists on any traffic channel.
Troubleshooting
When there is bit error in the traffic channel, refer to Bit Error Fault for
troubleshooting.
User Management
Operation Purpose
In order to prevent illegal access to the EMS software and ensure normal
running of equipment and service security, it is necessary to change the
login password of the EMS users periodically, and assign proper authorities
to the EMS operators.
Operation Method
The EMS software provides four levels of users: system administrator,
system maintainer, system operator and system monitor. Each level of
user has specific operation authorities. Assign unique username,
password and management objects for each EMS operator, and assign
different user levels according to the specific operation authorities of
each user.
Change the login password of the EMS operators periodically.
Note: Since the system administrators possess all the operation authorities, if they
login to the EMS and perform any improper operation, it may cause severe
consequences. Therefore, in routine maintenance, it is not recommended for the
user to log into the EMS as a system administrator. Instead, a system monitor
user should be created, and used to log into the EMS for routine maintenance.
Inspection Criteria
The EMS operators should be able to log in to the EMS with an
assigned username, and have the assigned operation authorities.
The EMS operators should be able to change the login password
periodically.
Troubleshooting
If the EMS operators have wrong operation authorities or cannot
change the password, they should request the system administrator to
check the user configuration data or reset the user authorities and
password.
To troubleshoot faults of EMS connections, refer to EMS Connection
Fault.
Operation Method
Log in to the EMS and check the NE ID.
Inspection Criteria
The EMS can be logged in normally, and the screen of the computer
marked in the EMS is blue.
The NE icon is not grey. It should be green representing for normal
running, or other colors representing for certain alarm levels. The
default relationships between icon colors and alarms are listed in Table
21.
Troubleshooting
To troubleshoot faults of EMS connections, refer to EMS Connection Fault.
Operation Method
In the client-side operation window of the EMS software, check the NE icon
in the navigation tree and the topology map.
Inspection Criteria
The NE icon is not grey. It should be green representing for normal
running, or other colors representing for certain alarm levels. The
default relationships between icon colors and alarms are listed in Table
21.
The grey NE icon indicates that the NE is offline or loses connection
with the EMS.
The green NE icon indicates that the communication between the
NE and EMS is normal and there is no alarm.
If the NE icon is in some color of certain alarm level, it indicates
that the communication between the NE and EMS is normal, but
alarm exists. The NE icon color indicates the highest level of alarms.
The solid line between two NEs indicates that the optical connection is
normal. And the dotted line indicates that the optical connection
between NEs is broken.
Troubleshooting
To troubleshoot faults of EMS connections, please refer to EMS
Connection Fault.
When alarm indicator exists on the NE icon, query the alarm details via
the current alarm monitoring dialog box or monitoring window. For the
handling of alarm message, refer to Common Alarm Messages and
Solutions.
If the line indicative of the optical connection is a dotted line, check the
corresponding optical cable and pigtail.
Note: The EMS software can perform monitoring and management only on the NEs
that are in a status of normal communication with the EMS host.
Alarm Monitoring
Operation Purpose
In the ZXONM E300 EMS software, the user can monitor the alarm
message of the NE; thus keep aware of the current working status of the
NE, and detect/handle the alarm message of the NE in time.
Operation Method
In the client-side operation window of the EMS software, open the
monitoring window to monitor the alarm message of all NEs in real
time.
Inspection Criteria
The NE has no current alarm message.
The NE has no unconfirmed history alarm message.
Troubleshooting
To troubleshoot faults of EMS connections, refer to EMS Connection Fault.
Performance Monitoring
Operation Purpose
In the ZXONM E300 EMS software, the user can monitor the performance
message of the NE; thus keep aware of the current service performance of
the NE, and detect/handle the performance message of the NE in time.
Operation Method
In the client-side operation window of the EMS software, query the latest
15 minutes and 24 hours performance data of the NE.
Inspection Criteria
The NE has no performance over-threshold event.
Troubleshooting
For the handling of performance message, refer to Chapter 4.
Operation Method
In the client-side operation window of the EMS software, query the
current network configuration information.
Inspection Criteria
The current network/NE configurations agree with the actual
networking.
There is no switching event.
Troubleshooting
If the current network/NE configurations conflict with the actual
networking:
If the current service meets the user requirements, the network
configuration data should be corrected to comply with the actual
networking.
If the current service does not meet the user requirements, the
network configuration data should be corrected to comply with the
user requirements.
For the handling of switching events, refer to Chapter 4.
Operation Method
In the client-side operation window of the EMS software, query the user
operation log.
Inspection Criteria
No illegal login.
No user operations affecting system operation or service functions.
Troubleshooting
When any illegal user or operation is found, use the user management
function of the EMS software to check the user identity and the authority
settings, and change the user password in time.
Report Printing
Operation Purpose
With the printing function of the EMS software, the user can print out the
network configuration, user operation log, equipment performance and
alarm message. The printed reports are a basis for operation/maintenance
records and network analysis.
Operation Method
Print the reports in the client-side operation window of the EMS software.
Inspection Criteria
None
Troubleshooting
If the ZXONM E300 on Windows platform cannot print reports, check
whether the Report Server is started up. The Report Server can be started
up through the Windows menu of Startup-> Programs-> ZXONM E300
-> Report Server.
Data Backup
Operation Purpose
In the ZXONM E300 EMS software, database backup is primarily used to
copy and save the data of the Manager database. In the network operation
& maintenance, it is necessary to backup the system data often so that
the network data is quickly recoverable in case of network fault and EMS
data loss.
Operation Method
In the client-side operation window of the EMS software, perform the
operation of data backup.
Note: It is recommended to save the backup data in a mobile storage device lest
backup loss in case of hard disk fault of the EMS host.
Inspection Criteria
None
Troubleshooting
None
Data Recovery
Operation Purpose
In case of network fault or EMS data loss, use the ZXONM E300 EMS
software to recover the data that is backed up at the EMS database side.
The recovery implemented by the ZXONM E300 covers all the current data.
Operation Method
In the client-side operation window of the EMS software, perform the
operation of data recovery.
Inspection Criteria
None
Troubleshooting
None
Performance Message
Categories
Performance messages of the ZXMP S385 include SDH interface
performance messages, equipment analog performance messages, and
Ethernet port performance messages.
Performance
Detection Point Description
Message
2 Mbit/s PDH physical
CV Coding Violation
interface
BBE Background Block Error
ES Errored Second
Regenerator section SES Severely Errored Second
UAS Unavailable Second
OFS Out-of-Frame Second
Performance
Detection Point Description
Message
BBE Background Block Error
ES Errored Second
SES Severely Errored Second
UAS Unavailable Second
Multiplex section
FEBBE Far End Background Block Error
FEES Far End Errored Second
FESES Far End Severely Errored Second
FEUAS Far End Unavailable Second
BBE Background Block Error
ES Errored Second
SES Severely Errored Second
TABLE 24 LIST OF SDH PERFORM ANCE MESSAGES DETECTABLE BY THE ETHERNET CARD
Detection Performance
Description
Point Message
Table 26 lists the data performance messages of the ZXMP S385 Ethernet
card.
TABLE 26 DATA PERFORM ANCE MESSAGES OF THE ZXMP S385 ETHERNET CARD
Detection
Performance Message Description
Point
Detection
Performance Message Description
Point
VCG Send GFP Data Frames Number of sent GFP Data Frames
(EOS) port Send GFP Idle Frames Number of sent GFP Idle Frames
Send GFP Client Management Frames Number of sent GFP Client Management Frames
Send GFP Frame Bytes Number of sent GFP Frame Bytes
Receive GFP Dropped Frames Number of received GFP Dropped Frames
Receive PPP/HDLC Frames Number of received PPP/HDLC Frames
Receive PPP/HDLC Frame Bytes Number of received PPP/HDLC Frame Bytes
Receive PPP/HDLC Dropped Frames Number of received PPP/HDLC Dropped Frames
Receive PPP/HDLC FCS Error Frames Receive PPP/HDLC FCS Error Frames
Receive PPP/HDLC Aborted Frames Number of received PPP/HDLC Aborted Frames
Send PPP/HDLC Frames Number of sent PPP/HDLC Frames
Send PPP/HDLC Frame Bytes Number of sent PPP/HDLC Frame Bytes
The 2 Mbit/s signal of the ZXMP S385 employs HDB3 code. When the
equipment detects signal code error, it will report CV to the EMS.
Event Causes
The causes of CV are similar for electrical signals of different rates. Taking
the commonly used 2 M signal as an example, the possible causes include:
Influence on Equipment
If CV values are small, only a few or no CVs occur in 15 minutes, or
just a few are reported in 24 hours, it will impose no influence on the
service.
If CV values are large in 15 minutes and they keep increasing, the
service may be affected, and voice noise or illegible characters of data
may occur, even with the possibility of service interruption.
If significant CV values burst out, the service will be interrupted
instantly.
Solutions
Isolate the switch equipment from the transmission equipment. Use a
bit error tester to test the corresponding clear transmission channel of
the two equipment respectively, and check whether the CV is reported
from the switch equipment or transmission equipment.
If the CV is reported from the transmission equipment, cut off the
service connection of this channel, find out the NE reporting this CV
through the EMS, and locate the fault. There are different solutions to
different causes:
If the CV is caused by the interface performance of the 2 M
tributary card, it can be judged through hardware loopback.
Replacing the tributary card will probably solve the problem.
If the CV is caused by poor cable connection, weld or splice the
cable again.
If the CV is caused by inferior cable, replace the cable.
If the CV is caused by poor grounding, it is usually because the
service interface ground cables of the equipment are designed
differently by different manufacturers. To solve this problem,
remake the ground cable, or connect a capacitor in series at the
originating core. The capacitor can be 0.1u to 1u Tantalum.
Warning: In the ZXMP S385 equipment room, the case of the cable distribution
frame should connect with the protection ground. The grounding resistances of the
protection ground and the DC working ground should be less than 1 , and the
ground cables should be highly interference-resistant.
Regenerator Section
Performance Events and
Solutions
Overview
The regenerator section performance events are detected via the B1 byte,
which is the regenerator section overhead byte. B1 byte uses 8 bits for
parity check. It is detected and terminated at the receiving NE, and will
not be transferred to the next NE.
Event Causes
External causes: The fiber connectors are dirty or connected
improperly. The fiber has deteriorated performance and incurs a high
loss.
Equipment causes: Inferior quality of the receiving and transmitting
optical modules of the optical line card, the CSA card, or the clock.
Man-made causes: Somebody inserted bit errors at the regenerator
section using EMS software, and did not delete them.
Influence on Equipment
In case of sporadic and minor bit errors, which occur regularly, several
times in 24 hours, or once in a few days, or occur continuously,
averaging one BBE per errored second, they generate no low-level bit
errors, and impose little influence on the service.
In case of major bit errors, which occur regularly, several times in 24
hours, or once in a few days, averaging at least 5 BBEs per errored
second, occasionally with transient out-of-frame alarms (lasting for 5
to 6 seconds) and OFS count, they will result in B2 and B3 bit errors,
and impose influence on all services. Especially, they will cause
transitory mosaic or frame suspension of the video service, but they
are scarcely perceptible in the telephone or data services.
In case of burst of continuous major bit errors, the system will report
performance over-threshold alarm along with out-of-frame alarm, the
unavailable time will begin, and transient interruption of services will
occur frequently.
Solutions
Perform the line-side self loopback of the optical interface at the local
equipment, and adjust the insertion depth of the fiber properly. If the
alarm disappears, the alarm cause lies in too strong or too weak
optical power.
In case of too strong optical power, add an attenuator into the line
to adjust it.
In case of too weak optical power, cleanse the fiber pigtail and
connect it again, or replace the optical modules which have strong
transmitting optical power.
If it is caused by inferior optical line card or CSA card, replace the card.
If it is caused by bit errors inserted in the EMS software, delete the bit
errors in the EMS, and issue the command.
The MS bit errors detection use three B2 bytes, i.e., 24 bits, for parity
check. MS bit errors will not be transferred to the next NE. The receiving
NE which deals with the MS overhead will terminate MS bit errors, and
send the remote alarm message back to the transmitting NE at the same
time. Since REG equipment does not deal with MS overhead, B2 byte will
not be changed by REG and will be sent to the next NE. However, since
the ADM and TM equipment deal with the MS overhead, they will terminate
B2 byte, restart parity check counting, and send the remote alarm
message to the transmitting NE.
Note: Remote alarm message is a message returned by the receiving end to the
transmitting end as an acknowledgement, so that the transmitting end can know
about the bit error status of the receiving end.
For B2, its remote alarm message byte is the M1 byte in the MS overhead,
i.e., the MS remote block error indication byte. After the receiving NE
detects the B2, it will store the performance value of B2 into the M1 byte,
and send it back to the transmitting NE. After the transmitting NE detects
the M1, it will report the M1 value (B2 FEES/FEBBE/FESES/FEUAS).
Therefore, the B2 FEBBE/FEES/FESES/FEUAS of the transmitting NE
always occur with the B2 BBE/ES/SES/UAS of the receiving NE.
Event Causes
Possible causes of the MS performance events include:
B1 bit error can result in B2 bit error. The causes are the same as B1
bit error. Refer to Regenerator Section Performance Events and
Solutions.
Influence on Equipment
If B2 bit errors are few, they impose little influence on the system. When
the performance keeps deteriorating and the bit errors cross the
performance threshold, the performance over-threshold alarm will be
reported.
If the EMS reports the out-of-frame alarm and the B2 performance over-
threshold alarm concurrently, the MS switching will occur for the network
configured with the MS protection, and MS-PSD and MS-PSC start to count.
In case of normal switching, MS-PSC count is an even number; in case of
switching back, the MS-PSD count is cleared to zero, waiting for recount at
the next switching.
Solutions
If B2 bit error occurs along with B1 bit error, solve B1 bit error first.
For how to handle B1 bit error, refer to Regenerator Section
Performance Events and Solutions.
If B2 bit error is caused by bit errors inserted in the EMS software,
delete the bit errors in the EMS, and issue the command.
When MS switching events occur in the network, if the MS-PSC count is
an odd number, follow the steps below:
Check whether these problems occur in the network: unplugged or
faulty NCP card, self loopback of optical interface, protection
configuration error, suspended APS, inconsistent APS-ID,
inconsistent switching control command, and abnormal transmitting
of the K byte between the protection optical line card pairs.
If such problems exist, solve them first. If they do not exist, issue
the Reset APS command to all the points in the MS ring to solve
the problem.
path, and transparently transmitted through the ZXMP S385 in the path,
without being processed. It is terminated at the termination NE of the
whole path.
The remote alarm byte of B3 bit error is the higher-order path overhead
G1. G1 sends the status and performance message of the terminal in the
path back to the VC4 path source equipment, so as to enable monitoring
on the status and performance of the whole bidirectional path at any end
or any point of the path. The B3 BBE/ES/SES/UAS of the NE occurs along
with the B3 FEBBE/FEES/FESES/FEUAS of the opposite NE.
Event Causes
B3 bit errors usually occur along with B1 and B2 bit errors. Its possible
causes are:
Influence on Equipment
If B3 bit errors are few, they will impose little influence on the equipment.
If the performance keeps deteriorating, and the B3 bit errors cross the
threshold, the B3 bit error performance over-threshold alarm will be
reported, and the transmission quality of the path will deteriorate.
Solutions
First, check whether the B1 or B2 bit errors exist. If they exist, handle
as described in Regenerator Section Performance Events and Solutions,
and Multiplex Section Performance Events and Solutions.
If no B1 or B2 bit error exists, find the starting point of the B3 bit error
in the path where the B3 bit error is reported. After resolving the B3
bit error at the starting point, find the next starting point of B3 bit
error along the path. Carry on until all the bit errors are solved.
If it is caused by bit errors inserted in the EMS software, delete the bit
errors in the EMS, and issue the command.
Event Causes
The possible causes of V5 bit errors are:
Influence on Equipment
If V5 bit errors are few, they will impose little influence on the equipment.
If the performance keeps deteriorating, and the V5 bit errors cross the
threshold, the performance over-threshold alarm will be reported, and the
transmission quality will deteriorate.
Solutions
If V5 bit error is caused by bit errors of regenerator or multiplex
section, and the B1/B2/B3 bit errors exist, handle B1/B2/B3 bit errors
first. Refer to the solutions described in Regenerator Section
Performance Events and Solutions, Multiplex Section Performance
Events and Solutions, and Higher-Order Path Performance Event.
If it is caused by tributary card faults, replace the tributary card.
If it is caused by bit errors inserted in the EMS software, delete the bit
errors in the EMS, and issue the command.
When the network is in synchronous working status, pointers are used for
phase alignment between synchronous signals. When the network is out of
synchronization, the frequency and phase can be aligned through pointer
justification. Depending on the running speed of the NE clocks carried by
various signals, pointer justification can be divided into positive pointer
justification and negative pointer justification. The pointer justification
byte is detected and terminated at the receiving NE, and will not be
transferred to the next NE.
During the multiplexing and mapping of SDH, three types of pointers are
involved: AU-4, TU-12, and TU-3.
The AU-4 pointer locates at the first nine bytes of the fourth line in the
SDH frame structure, and is used for determining the starting position
of VC-4 in the AU.
The TU-3 pointer locates in the TUG-3. It has a total of nine bytes to
determine the starting position of VC-3 in the TU-3.
The TU-12 pointer has three bytes in total to determine the starting
position of VC-12 in the TU-12.
Event Causes
External causes: The clock is unlocked, or the clock source is of poor
quality; or the CSA card, and the optical line card are worn away after
long-term running.
Equipment causes: The CSA card, and the optical card are faulty. For
TU-3/TU-12, tributary card fault can also cause pointer justification.
EMS causes: Manually forced switching command is not cancelled; or
there are configuration errors of clock source.
Note: The AU4 pointer justification may result in TU3/TU12 pointer justification
events.
Influence on Equipment
A pointer justification event indicates that there is problem of network
synchronization. Slight point justification events impose little influence
on the equipment. Major pointer justification events indicate symptoms
such as unlocked clock, which mean that the service quality is at risk.
Major pointer justifications should be handled immediately.
If the network is out of synchronization and keeps deteriorating, when
the pointer justification value crosses the threshold, the EMS will report
the corresponding performance over-threshold alarm.
Solutions
Handling AU4 Pointer Justification Event
If the clock is unlocked, check whether the clock switches. If the clock
does not switch, the event may be caused by fault/wear-down of
optical line card or CSA card. Replace the corresponding cards.
If the clock switches, check the configuration of the clock source,
especially the data configuration, clock source level configuration, clock
source extraction configuration and the setting of clock switching rules.
If the clock source configuration is correct, check the hardware fault of
the switched clock source. If hardware fault exists, replace the
corresponding card.
If the external clock is unlocked, follow the above three steps to locate
the fault and solve it.
If poor clock lock quality results in the pointer justification event, it
may be caused by fault/wear-down of optical card or CSA card.
Replace the corresponding cards.
Alarm Categories
Communication alarm: The alarm which directly affects the service
layer, and indicates that the communication signals are interrupted or
deteriorated at a certain layer.
Synchronization alarm: The alarm for clock-related faults.
Equipment alarm: The alarm directly caused by internal fault of the
equipment, including power failure, card fault, card out-of-position,
and inconsistency between the EMS configuration and the hardware
installed on the equipment.
Alarm Levels
Alarms can be classified into four severity levels: critical, major, minor,
and warning alarms, which are in order from higher severity to lower
severity. Every alarm message has a default severity. The user can modify
the alarm level in the EMS as required.
Alarm Priorities
Alarm priorities of the transmission equipment are as the follows:
Alarm Summary
Table 27 lists the possible alarm messages of the ZXMP S385.
Alarm Detection
Alarm Category Alarm Name Alarm Level
Point
Alarm Detection
Alarm Category Alarm Name Alarm Level
Point
Alarm Detection
Alarm Category Alarm Name Alarm Level
Point
The alarm messages of the ZXMP S385 Ethernet card are listed in Table 28.
Detection Alarm
Alarm Name
Point Level
Ethernet
electrical Ethernet interface unconnected Critical
interface
Ethernet interface unconnected Critical
Ethernet optical Loss of Signal (LOS) Critical
interface Missing Laser Module Critical
Laser Module Fault Critical
Loss of Pointer (LOP) Critical
AU4/TU3/TU12
Alarm Indication Signal (AIS) Major
Trace ID MismatchTIM Major
Remote Defect IndicationRDI Minor
Enhanced Remote Defect Indication of Payload
Minor
Defect ( E-RDI Payload Defect)
Enhanced Remote Defect Indication of Connectivity
Minor
Defect (E-RDI Connectivity Defect)
Enhanced Remote Defect Indication of Server
VC4/VC3 Minor
Defect (E-RDI Server Defect)
Payload Mismatch (PLM) Critical
Signal Deterioration ( SD) Minor
Path Unequipped ( UNEQ) Major
Loss of Multi-frameLOM Critical
BER Cross-threshold (EXC) Major
Unavailable Second (UAS) Major
Trace ID Mismatch (TIM) Major
Remote Defect Indication (RDI) Minor
Enhanced Remote Defect Indication of Payload
Minor
Defect ( E-RDI Payload Defect)
Enhanced Remote Defect Indication of Connectivity
Minor
Defect (E-RDI Connectivity Defect)
VC12 Enhanced Remote Defect Indication of Server
Minor
Defect (E-RDI Server Defect)
Payload Mismatch (PLM) Critical
Signal Deterioration ( SD) Major
BER Cross-threshold (EXC) Major
Extended Signal Label Mismatch ( ExSLM) Major
Unavailable Second (UAS) Major
Interface card type mismatch Critical
Interface card out of position Critical
Card
Interface card running abnormality Critical
Detection point temperature over-threshold Minor
Detection Alarm
Alarm Name
Point Level
Item Description
Item Description
Logical functional block of the fault: Basic functional block of the SDH physical
Remarks
interface (SPI)
Item Description
Logical functional block of the fault: Basic functional block of the SDH physical
Remarks
interface (SPI)
Item Description
Logical functional block of the fault: Basic functional block of the SDH physical
Remarks
interface (SPI)
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
T A B L E 3 8 B 1 U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Item Description
Related
A1, A2, B1
overhead
Alarm Card: The red alarm indicator light is constantly on.
indication EMS: Open the card management dialog box, there is orange alarm identifier.
Fault of external optical line
Fault of fiber pigtails and coupling components
Inferior coupling or wrong transmitting-receiving relationship
Fault of local optical line card
Alarm cause
Fault of opposite optical line card
Local optical line card receives light of different rate levels.
Fault of CSA card
Fault of backplane
Take care of the optical line
Replace the fiber pigtails or coupling components
Ensure good coupling, and correct the transmitting-receiving relationship
Replace the local optical line card.
Solutions Replace the opposite optical line card
Check the rate level of the optical connection line, and connect a correct optical
line
Replace the CSA card
Replace the backplane
Logical functional block of the fault: Basic functional block of regenerator section
Remarks terminal (RST)
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Logical functional block of the fault: Basic functional block of multiplex section
Remarks terminal (MST)
Item Description
T A B L E 4 8 B 2 U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
T A B L E 4 9 B 2 F E U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Item Description
Related
B2, M1
overhead
Alarm Card: The red alarm indicator light is constantly on.
indication EMS: Open the card management dialog box, there is orange alarm identifier.
This alarm message occurs in pair with the alarm message of B2 UAS
Performance Over-Threshold. The causes are the same that can be:
Fault of external optical line
Fault of fiber pigtails and coupling components
Inferior coupling or wrong transmitting-receiving relationship
Alarm cause
Fault of local optical line card
Fault of opposite optical line card
Local optical line card receives light of different rate levels.
Fault of CSA card
Fault of backplane
Take care of the optical line
Replace the fiber pigtails or coupling components
Ensure good coupling, and correct the transmitting-receiving relationship
Replace the local optical line card.
Solutions Replace the opposite optical line card
Check the rate level of the optical connection line, and connect a correct optical
line
Replace the CSA card
Change the slot or replace the backplane
Logical functional block of the fault: Basic functional block of multiplex section
Remarks terminal (MST)
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
This alarm message occurs in pair with the alarm message of B2 SES
Performance Over-Threshold. The causes are the same that can be:
Fault of external optical line
Fault of fiber pigtails and coupling components
Inferior coupling or wrong transmitting-receiving relationship
Alarm cause
Fault of local optical line card
Fault of opposite optical line card
Local optical line card receives light of different rate levels.
Fault of CSA card
Improper plugging of cards and backplane pins
Take care of the optical line
Replace the fiber pigtails or coupling components
Ensure good coupling, and correct the transmitting-receiving relationship
Replace the local optical line card.
Solutions Replace the opposite optical line card
Check the rate level of the optical connection line, and connect a correct optical
line
Replace the CSA card
Change the slot or replace the backplane
Logical functional block of the fault: Basic functional block of multiplex section
Remarks terminal (MST)
Item Description
Item Description
Item Description
Item Description
This alarm message occurs in pair with the alarm message of B2 ES Performance
Over-Threshold. The causes are the same that can be:
Fault of external optical line
Fault of fiber pigtails and coupling components
Inferior coupling or wrong transmitting-receiving relationship
Alarm cause
Fault of local optical line card
Fault of opposite optical line card
Local optical line card receives light of different rate levels.
Fault of CSA card
Improper plugging of cards and backplane pins
Take care of the optical line
Replace the fiber pigtails or coupling components
Ensure good coupling, and correct the transmitting-receiving relationship
Replace the local optical line card.
Solutions Replace the opposite optical line card
Check the rate level of the optical connection line, and connect a correct optical
line
Replace the CSA card
Change the slot or replace the backplane
Logical functional block of the fault: Basic functional block of multiplex section
Remarks terminal (MST)
Item Description
Item Description
Item Description
Item Description
This alarm message occurs in pair with the alarm message of B2 BBE
Performance Over-Threshold. The causes are the same that can be:
Fault of external optical line
Fault of fiber pigtails and coupling components
Inferior coupling or wrong transmitting-receiving relationship
Alarm cause
Fault of local optical line card
Fault of opposite optical line card
Local optical line card receives light of different rate levels.
Fault of CSA card
Improper plugging of cards and backplane pins
Take care of the optical line
Replace the fiber pigtails or coupling components
Ensure good coupling, and correct the transmitting-receiving relationship
Replace the local optical line card.
Solutions Replace the opposite optical line card
Check the rate level of the optical connection line, and connect a correct optical
line
Replace the CSA card
Change the slot or replace the backplane
Logical functional block of the fault: Basic functional block of multiplex section
Remarks terminal (MST)
Item Description
Item Description
When an optical line card detects "loss of receiving signal", "loss of frame", or
"RS/MS AIS" alarms, or when the BER of the RS/MS reaches 10-3, the MS
protection switching will occur. And the EMS will report the "MS protection
Alarm cause switching event" alarm.
Fault of APS configuration on the local/opposite optical line card.
Physical fault of APS protocol processing module on the local/opposite optical line
card
Handle higher level alarms. After handling the higher level faults, the Multiplex
section protection switching event alarm will automatically disappear at the end
Solutions of APS automatic recovery.
Reset APS startup/stop status and issue the command.
Replace the local/opposite optical line card.
Logical functional block of the fault: Basic functional block of multiplex section
Remarks
protection (MSP)
Item Description
Item Description
Logical functional block of the fault: multiplexing functional block of higher-order
interface (HOI)
Remarks If one NE is configured with timeslot straight-through at AU4-level, since the AU4
path alarm indication signal will not be terminated, the EMS will report this alarm
which is a normal indication.
Item Description
Item Description
Item Description
Alarm
Communication alarm
category
Alarm This alarm indicates that opposite end receives no signal on the higher-order path
explanation from the local end.
Alarm card OL1, OL4, OL16, LP1, EPE1
Related
G1
overhead
Alarm Card: The red alarm indicator light is constantly on.
indication EMS: Open the card management dialog box, there is yellow alarm identifier.
This alarm occurs in pair with the AU4 path alarm indication signal, unavailable
time. The causes are the same that can be:
Wrong cross-connect configuration
Wrong clock configuration
Alarm cause Fault of optical line card
Fault of CSA card or clock
Fault of tributary card
Fault of backplane pins
Damage of backplane
Correct the timeslot configuration
Correct the clock configuration
Replace the optical line card
Solutions
Replace the CSA card
Replace the tributary card
Change the slot or replace the backplane
Logical functional block of the fault: multiplexing functional block of higher-order
Remarks interface (HOI)
T A B L E 6 2 B 3 U AS P E R F O R M A N C E O V E R - T H R E S H O L D ( H I G H E R - O R D E R V C 4 P A T H
VIRTUAL CONTAINER)
Item Description
Item Description
T A B L E 6 3 B 3 F E U AS P E R F O R M A N C E O V E R - T H R E S H O L D ( H I G H E R - O R D E R V C 4 P A T H
VIRTUAL CONTAINER)
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Related
G1
overhead
Alarm Card: The red alarm indicator light is constantly on.
indication EMS: Open the card management dialog box, there is orange alarm identifier.
Wrong cross-connect configuration
Wrong clock configuration
Fault of optical line card
Alarm cause
Fault of CSA card or clock
Fault of tributary card
Fault of backplane pins
Correct the timeslot configuration
Correct the clock configuration
Replace the optical line card
Solutions
Replace the CSA card
Replace the tributary card
Change the slot
Logical functional block of the fault: multiplexing functional block of higher-order
Remarks interface (HOI)
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Related
G1
overhead
Alarm Card: The red alarm indicator light is constantly on.
indication EMS: Open the card management dialog box, there is orange alarm identifier.
Wrong cross-connect configuration
Wrong clock configuration
Fault of optical line card
Alarm cause
Fault of CSA card or clock
Fault of tributary card
Fault of backplane pins
Correct the timeslot configuration
Correct the clock configuration
Replace the optical line card
Solutions
Replace the CSA card
Replace the tributary card
Change the slot
Logical functional block of the fault: multiplexing functional block of higher-order
Remarks interface (HOI)
Item Description
Item Description
Rewrite C2 byte
Correct the timeslot configuration
Replace the optical line card
Solutions
Replace the CSA card
Replace the tributary card
Change the slot
Logical functional block of the fault: multiplexing functional block of higher-order
Remarks interface (HOI)
Item Description
Item Description
Item Description
Item Description
Item Description
TABLE 76 TU12 P ATH AL ARM INDICATION SIGNAL, UNAV AIL ABLE TIME
Item Description
Item Description
Item Description
Item Description
T A B L E 7 9 V 5 U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Item Description
T A B L E 8 0 V 5 F E U AS P E R F O R M A N C E O V E R - T H R E S H O L D
Item Description
Item Description
Item Description
Item Description
Logical functional block of the fault: multiplexing functional block of lower-order
Remarks interface (LOI).
Alarms of higher level automatically mask the alarms of lower level.
Item Description
Item Description
Item Description
Item Description
Item Description
Item Description
Related
V5
overhead
Alarm Card: The red alarm indicator light is constantly on.
indication EMS: Open the card management dialog box, there is orange alarm identifier.
Fault of some tributaries of 2M tributary card at the local/opposite end
Alarm cause
Fault of CSA card
Replace the EPE1 card
Solutions Switch between the active/standby CSA card; reset the CSA card; or replace the
CSA card
Logical functional block of the fault: multiplexing functional block of lower-order
Remarks interface (LOI)
Item Description
Item Description
Item Description
Alarm This alarm message occurs in the network protected by path switching. It
explanation indicates occurrence of lower-order path protection switching.
Alarm card CSA card
Related
None
overhead
Alarm Card: The red alarm indicator light is constantly on.
indication EMS: Open the card management dialog box, there is yellow alarm identifier.
When the CSA card detects higher-order path alarm on the optical line card, the
path protection switching will occur. And the EMS will report the "TU12 protection
Alarm cause
switching event" alarm.
Wrong timeslot configuration.
Handle higher level alarms.
Solutions
Correct the wrong timeslot configuration.
Logical functional block of the fault: the multiplexing functional block of lower-
Remarks
order interface (LOI)
Item Description
Item Description
Item Description
Item Description
Item Description
Remarks None
Item Description
Item Description
Alarm
Equipment alarm
category
Alarm
This alarm indicates that the NCP card lost the ability to manage other cards.
explanation
Alarm card All the cards except the NCP card
Related
None
overhead
Alarm EMS: The red alarm indicator light is off, and the green indicator light does not
indication flash.
The EMS configuration disagrees with the hardware version
Fault of card self test
Alarm cause
Fault of card hardware
Failure of communication between the NCP card and the card
Modify the EMS configuration to comply with the hardware version.
Reset the card
Solutions
Replace the card
Reset or replace the NCP card
Remarks None
Item Description
Remarks None
Item Description
Alarm name Loss of the receiving signal at the Ethernet physical optical interface (LOS)
Alarm level Critical
Alarm
Communication alarm
category
This alarm indicates interruption at the physical layer of the Ethernet optical
Alarm
interface and the external equipment, the local end receives no optical signal from
explanation the external equipment.
Remarks None
Troubleshooting
Troubleshooting Procedures
The troubleshooting flow chart is shown in Figure 4.
No
Troubleshooting
successful?
On-call troubleshooting by
local ZTE office
Local ZTE office/ equipment
room maintenance personnel
Yes Troubleshooting No
successful?
Basic Principles of
Troubleshooting
In handling the equipment faults, the maintenance staff should follow
these basic principles: observe first, then query, think, and take action
finally.
Observing
After arriving at the site, the maintenance personnel should first observe
the fault phenomena carefully including the faulty point, alarm reason,
severity level and damage level. Only by fully considering fault reasons of
the equipment, can one feel the essence of problem.
Query
Put questions to onsite operators after observing fault phenomena. Check
whether there is any direct cause of the fault, such as data modification,
file deletion, circuit board replacement, power supply fault or lightening.
Thinking
After observing the symptoms and querying the operators, the
maintenance person can analyze by using his own knowledge. Locate the
fault, find the faulty point, and work out the fault cause.
Action
After locating the faulty point through above given three steps, the
maintenance staff or technician can remove the fault by performing proper
fault eradication procedures, e.g., by modifying the configuration data or
by replacing the card.
Causes
The common fault causes include: engineering problems, external causes,
improper operations, equipment interconnection problems, and equipment
problems.
Engineering Problems
Project problem refers to substandard or inferior construction of project,
which may results in equipment fault. Such problems can be revealed
during the construction of project and there are some problems, which
cannot be revealed, until the equipment has operated for a certain time.
These are latent risks for the equipment.
External Causes
External causes refer to the environment and equipment factors, which
results in equipment fault. Such factors do not include transmission
equipment, but they do include:
1. Power failure, e.g., equipment power failure, too low supply voltage.
2. Switch fault.
3. Fiber fault: Performance deterioration of fiber due to its wear and tear,
fiber cut, ill contact of fiber connector.
4. Cable fault, e.g., relay dropped or broken due to ill contact of cable
connector.
5. The equipment is improperly grounded.
6. The equipment placed in unsuitable environment.
Improper Operations
Improper operations refer to inappropriate operations performed by
maintenance staff due to lack of in-depth understanding of equipment,
which results in equipment fault.
Equipment Problems
Equipment problems refer to the faults caused by the transmission
equipment itself, including equipment damage and inferior cooperation of
PCBs. After running for a long time, the PCBs are damaged due to aging
factor, which ultimately result in damaged equipment. The characteristics
of equipment damage are: the equipment has been in use for a long time
and has been running normally before the fault occurs; and the fault only
occurs at some certain point/PCB, or the fault occurs because of external
causes.
1. Check the external factors first, which can be fiber cut, switching fault,
or power failure, and after that consider the transmission equipment
faults.
2. Try to find out the faulty site first, and then locate the fault to the card.
3. The fault of optical line card causes alarms of tributary cards.
Therefore, consider the line first and then consider the tributaries.
While analyzing alarms, consider the higher priority alarms first, and
then analyze the lower priority alarms.
When a fault arises, EMS will record abundant alarm events and
performance data. Analyze the information, combine it with the overhead
byte in SDH frame structure and the SDH alarm principle, to determinate
fault type and fault location primarily.
Test Method
When the networking, service and fault information are complicated or
when equipment faces unidentifiable faults without reporting any clear
alarm or performance information, use the maintenance functions
provided by EMS to test the faulty point and fault type. The following
content takes loop-back operation as an example.
The loop-back operation does not require any in-depth analysis of alarms
and performance. It is a common and effective method for locating the
fault point. However, it may affect the services.
Unplugging/Plugging
After locating fault to specific card, unplug the card and external interface
connector. Plug them back to check ill contacts or abnormal card status.
Replacement Method
Replacement method means replacing suspected faulty piece of equipment
with a new one such as a segment of cable, a card or a equipment, to
troubleshoot the fault. The replacement method is applicable to the
following circumstances:
In this case, after locating the fault of distant NE site, query the current
configuration data and user operation log of equipment to analyze the
fault.
Reconfiguration Method
This method is used to locate fault by modifying the equipment
configuration. It is applicable to checking configuration error after locating
fault to a specific site. The modifiable configurations include timeslot, slot
and card parameters.
Processing by Experiences
At some special occasions, the equipment card gets into abnormal working
status resulting in service interruption, ECC communication interruption,
but the equipment configuration data stays completely normal due to
instant abnormal power supply and strong external electromagnetic
interference. Practice tells us that in such cases, we can troubleshoot and
recover effectively in time by resetting card, restarting the equipment, and
by delivering the configuration data again..
Typical Troubleshooting
The ZXMP S385 may come across some typical faults which are:
communication fault, service interruption, BER fault, synchronization fault,
order wire fault, equipment interconnection fault and EMS interconnection
fault.
Note: Communication faults generally refer to faults like path interruption or bit
error, and fault at both the switching side and transmission side. The faults
described hereunder other than communication faults usually occur in transmission
equipment.
Communication Fault
Causes
The faults at the transmission equipment or switching equipment result in
interruption of communication services or in large number of bit errors.
Troubleshooting Procedure
The troubleshooting flow is shown in Figure 5.
A fault occurs
On switch side
Fault analysis and
location
Perform transmission
troubleshooting
1. After the fault occurs, activate the standby path to ensure normal
running of existing communication services.
2. Check whether the fault is at transmission side or switching side.
To locate the fault point, recommend to use the test method and
perform the loop-back operation. To perform loop-back, either perform
hardware loop-back at the DDF, or perform software loop-back for
transmission equipment and connect a BER tester to test the signal in
path loop. In case of software loop-back, you must tell tributary loop-
back from AU loop-back, and terminal side loop-back from line side
loop-back type.
3. If the fault is located to the switch side, coordinate with the switch
staff to handle it. If the fault is located to the transmission side,
determine the category of transmission fault according to Figure 6.
A transmission
fault occurs
Perform error
troubleshooting
Troubleshooting Procedure
1. Connect the BER tester to the tributary receiving/transmitting port of
the faulty path at the local NE, and use test method to perform loop-
back of the path segment by segment to locate the faulty NE, as
shown in Figure 7.
Remote Remote
Local Local Local
If the fault is located to the higher order path, perform the following
operations consecutively:
Perform terminal-side loop-back for the faulty AU from the faulty
optical direction at the local NE.
Perform line-side loop-back for the faulty AU of the local optical
path at the adjacent NE.
Perform terminal-side loop-back for faulty AU of remote optical
path at the adjacent NE.
Perform line-side loop-back for faulty AU of the local optical path at
next adjacent NE.
Perform terminal-side loop-back for faulty AU of the remote optical
path at next adjacent NE, and so on.
Perform line-side loop-back for faulty AU of the local optical path at
the terminating NE.
Perform line-side loop-back for the corresponding tributary at the
terminating NE.
If the fault is located to the lower order path, perform the following
operations consecutively:
At the adjacent NE, next adjacent NE, ..., terminating NE, modify
the tributary timeslot configuration at the local end from Optical
path cut-through to Lower tributary segment by segment; and
perform line-side loop-back for the reconfigured tributaries in turn.
2. Observe status of the equipment indicator lights and analyze the fault.
If both the red and green indicator lights of a card are off and other
cards are normal, this card may be invalid or faulty. Replace this card.
3. Analyze the alarms and performance events of EMS. According to
alarms and performance events caused by faults, locate the faulty card
and replace it.
Step 2 and step 3 can be performed concurrently, and can be combined
with the unplugging/plugging method and replacement method.
Waring: If the received optical power is too strong, it will result in signal
deterioration or service blockage. Therefore, when the sites are closely located, an
optical attenuator must be installed in between them on the optical path.
will not raise alarm and the opposite optical line card cannot
receive any remote alarm either.
3. Symptom: The transmitted optical power of the optical line card is
normal, but the service is interrupted. The Multiplexing section AIS
alarm is reported at the receiving NE and Multiplexing section RDI
alarm is reported at the transmitting NE. Loss of multiplexing section
occurs even if performing self loop-back using fiber pigtail.
Analyzing and handling:
The symptoms show that the optical line card gives light normally but
does not scramble. In this case, use the empirical method, reset
software or re-plug the card to solve the problem. However, it is
preferable to replace the optical line card.
4. Symptom: 2 M service is blocked
Analyzing and handling:
Check the quantity of blocked 2 M services. If the quantity is
considerable, consider the optical path problem first.
If only one or several 2 M services are blocked, check whether the
timeslot is configured correctly or not. Execute the download command
in EMS to apply the correct timeslot configuration data to the tributary
card. If the tributary is still out of signal, reset the tributary card and
the alarm will disappear if there is no other hardware problem.
If the service is still blocked after the above step, follow the
troubleshooting procedure to perform terminal-side loop-back for the
2M tributary and connect a BER tester.
If the Loss of 2 M signal alarm persists on BER tester, the causes
may be improper interface of 2 M interface, 2 M line broken or the
improper welding of the coaxial connector of cable distribution
frame. Replace the interface to fix the problem.
If the BER tester alarm disappears, the problem lies in 2 M
interface card, CSA card or backplane. Replace 2 M interface
card/CSA card/backplane to fix the problem.
If the fault locates at 2 M interface card interconnected with third-party
equipment, the fault cause may lie in different ground voltage between
the interconnected equipment and the transmission equipment. In
order to eliminate the influence of voltage difference, following
methods are applicable:
Check the ground grid and make consistent ground voltage
between transmission equipment and the interconnected
equipment.
Ground the transmitting end of 2 M signal of the transmission
equipment and interconnected equipment, and do not ground the
receiving end.
Connect a 0.1 u~0.5 u capacitor in series with interconnected 2 M
signal cable.
5. Symptom: After the ZXMP S385 gets into service, the 2 M service is
blocked, no alarm or performance event is detected at the EMS, and no
bit errors are detected via the BER tester in the offline test.
Note: When the tributary service is blocked, check the connections of ground
cables.
Warning: Before testing the optical cable by means of OTDR, unplug the
connection fiber pigtail from the corresponding optical interface lest the strong
light emitted by OTDR damages the optical interface.
Caution: While using a fiber pigtail to perform optical interface self-loop, add an
optical attenuator between the receiving and transmitting optical interfaces to
ensure that the received optical power at optical interface falls within the allowed
range of optical interface (between received sensitivity and the overload optical
power).
Troubleshooting Procedure
1. Use the test method to locate the source of bit error as instructed in
Troubleshooting Procedure.
2. If the bit error is derived from the optical line card, analyze the bit
error performance event of the optical line card to remove the line bit
errors. The procedures are:
First check the external factors, e.g., improper grounding, too high
working temperature, too low/high received optical power of optical
line card.
Then observe the bit errors of optical line card. If all the optical line
cards at one site have bit errors, the CSA card of this site might
have failed. Replace the CSA card. If only the optical line card
reports bit errors, the fault may lie in this optical line card, the
opposite line card or fiber.
3. If the bit errors derive from the tributary card, analyze the
performance event of the tributary card to remove the tributary bit
errors. If only the tributary has bit errors, the tributary card or the CSA
card may be faulty, so replace the tributary card or the CSA card.
B1 bit errors on the optical line card at site A at this time. Handle it
immediately by replacing the optical line card.
Confirm that the EMS software works normally and the existent bit
errors are not reported mistakenly.
Clear the performance count of this site and query its performance
value.
If the bit error performance of corresponding tributary is constantly
zero then use the software loop-back test method. Visit the site to
check whether 2 M card interface of both sites and 2 M cables are
connected normally.
If only the bit errors of local site are reported without remote bit error,
it indicates that the bit errors are derived from the local site. Check the
tributary performance of the opposite site, which should report remote
bit error indication. In this case, check whether the connections of the
cards at local site are correct. If they are correct, change the timeslot
configuration of tributary, the tributary interface or change the
tributary card to fix the problem.
If the local site bit errors and occasional remote bit errors are reported
together but only the local site bit errors are reported at the opposite
site, it indicates that fault lies in opposite site. Handle it as instructed
in the preceding paragraph.
If both the local and opposite sites have local and remote bit errors,
handle local site and opposite site separately. Check the card
performance of both sites that the services have passed through, and
handle them as described in previous lines.
3. Symptom: Almost all 2 M tributaries have bit errors
Analyzing and handling:
Confirm that the EMS software works normally and the existing bit
errors are not reported mistakenly.
Collect the current alarm information, and check if any other higher
priority or severer alarms occur.
Query the timeslot configuration of tributary reporting the bit errors
and locate the faulty site.
Query whether the optical line card reports bit errors and locate the
faulty point. While querying, discriminate the local bit errors from
remote bit errors.
Troubleshooting Procedure
1. Check the clock configuration of EMS; avoid mutual extraction of clock
caused by human factors. Deliver correct clock configuration to the
NCP card to keep EMS data consistent with the NCP data.
2. Check through the EMS whether the optical path and tributaries have
AU PJE/TU PJE performance values. If only TU PJE exists in EMS, it
indicates that the tributary card is faulty. Just replace it.
3. If AU PJE/TU PJE exists concurrently, handle the AU PJE first and then
go on handling TU PJE if any.
Optical line cards and clock cards are the possible cards, which
generate AU PJE, and they are handled in the following procedure:
The EMS detects loss of timing input, which indicates that the local CSA
card is normal. The causes include:
Fault of the external equipment. The opposite site CSA card connected
to this site is unplugged.
Fault of optical line card. Check the clock source configuration,
download the clock configuration, and reset the CSA card.
Loss of the local clock source. Check the clock source.
3. Symptom: The clock source of the NE is configured as line extraction
clock but the clock card cannot extract the line clock normally.
Analyzing and handling:
Query whether the loss of timing input alarm is reported at EMS. If
this alarm exists, it will be impossible to extract the line clock. After
resolving the alarm problem, the function of extracting line clock will
recover.
Query the utilization of SSM byte and the clock quality level via EMS.
When the clock quality level of ZXMP S385 was unknown and this
function was not enabled, the CSA card will deem this clock source
unavailable by default. In this case, modify the configuration via EMS.
Query via EMS whether locked clock source is set or not.
4. Symptom: In EMS, the NE originally set as external clock source is
reported as extraction line clock.
Analyzing and handling:
The clock may be looped. In this case, troubleshooting varies with the
types of networking mode:
Chain network
Check via EMS whether the mutual extraction of NE clock is performed
on two fiber pairs. If the mutual extraction of clock is performed on
two fiber pairs and the clock source fails, the chain network clock will
be abnormal. Configure the clock source as mutual extraction of the
same fiber pair.
Ring network
Check via EMS whether the mutual extraction of NE clock is
performed on same fiber pair. If not, see preceding paragraphs to
modify the setting of extraction clock.
Check the extraction clock direction of all NEs that are set as
extraction line clock. If the extraction clock forms a closed loop in
same direction, it may result in clock looping. Change the clock
source configuration, e.g., set an NE in the ring network as an
internal clock to damage the clock looping. If the network is a
single ring and only one external clock source exists, set the NE
clock source type as external clock source and the only clock
source, and set all other NEs as bidirectional mutual extraction.
Troubleshooting Procedure
1. Check external causes, e.g., power failure or fiber performance
degradation.
2. Check whether the EMS configuration is correct or otherwise.
3. Use the test method to perform self-loop in each segment and locate
the faulty NE.
4. Use the alarm analysis method to check the optical card and CSA card.
Note: Refer to Appendix A for the definitions of NE IP address and the principles of
routing.
Troubleshooting Procedure
1. Check whether the optical path raises any alarm. Blocked optical path
will result in blocked order wire.
2. Check whether the order wire telephone is faulty. Use another
telephone for testing if necessary.
3. Check the OW card; observe the indicator lights and the EMS alarms.
Check whether the order wire card gets faulty by using the
unplugging/plugging method and replacement method.
4. Check the configuration of the OW card and optical line card.
Fan Fault
Causes
1. External causes: Fan cable failure, or ill contact between the fan box
and backplane.
2. Equipment causes: Fault of NCP card or fan control card (FAN).
Troubleshooting Procedure
1. Observe the running status of the fan and check the connection of
cables and interfaces. Check if there is any fault caused by external
factors.
2. Check the FAN card, and observe the indicator lights on the fan plug-in
box panel, observe the EMS alarms. Use the unplugging/plugging
method and replacement method to check if there is any fault in the
FAN card or NCP card.
i. Check whether the indicator lights on fan plug-in box panel are
normal. In normal case, the green indicator light is constantly on,
and the red indicator light is constantly off.
ii. Check whether the fan box is completely inserted into the fan plug-
in box.
2. Symptom: The EMS reports the alarm of FAN card running blocked.
Analyzing and handling:
i. Check whether the indicator lights on fan plug-in box panel are
normal. In normal case, the green indicator light is constantly on,
and the red indicator light is constantly off. If the red indicator light
is constantly on, it indicates that the fan running is blocked.
ii. Check whether the fan box is completely inserted into the fan plug-
in box.
Troubleshooting Procedure
1. Check whether the physical connections between the equipment are
correct. Avoid open solder point/cold joint of cable and ill cable contact.
2. Check the alarms and performance at both sides of interconnected
equipment, which help locating the fault.
3. Check grounding and the ground-sharing status of the equipment at
both sides.
Grounding problem is usually caused by two interconnected equipment
not sharing the ground properly. The grounding resistance fails to
reach the required index. The DDF is not grounded properly.
The equipment room usually adopts joint grounding. For the sites that
do not adopt joint grounding, conduct the test carefully during
hardware installation to ensure that the equipment at both sides share
common ground. Check the grounding status of shielding layer of the
coaxial port.
4. Check clock synchronization of whole network.
The switches and GSM equipment of some manufacturers impose high
requirements of clock synchronization throughout the network.
Through the SDH transmission network, if the clock of module office is
not synchronized with the clock of mother office, it may result in trunk
slip, dial-up access service interruption or even frequent call
interruption. Firstly, check if the clock of transmission equipment is
faulty. If it is normal, check whether the clock planning throughout the
network is rational. If not rational, adjust the clock synchronization
scheme, to synchronize clocks in the whole network.
The order wire overhead bytes and order wire protection bytes are defined
differently in different type of SDH equipment. When the equipment are
interconnected, transfer of order wire protection bytes will affect the order
wire of whole network. Table 96 lists the order wire protection bytes of the
ZTE SDH equipment.
This appendix describes how to set the NE IP address and EMS host IP
address.
EMS
2
Area 193
3 4 5
6 8
Area 192 7 10
9 11
Area 194
12
Of course, all the NEs can be simply allocated into one area, in which the
backbone area is not needed. For example, they may all be defined in area
193, and their NE addresses are listed in Table 98.
NE NE IP Address NE NE IP Address
Although defining all NEs into the same area is simple, but the efficiency of
ECC route algorithm will be affected if the number of NEs is larger..
Therefore, this method only applies to applications with a small number of
NEs. Normally, the maximum number of NEs in one area should not
exceed 120.
Address/Route Configuration of
the EMS Host
In order to enable EMS to manage all the NEs properly, it is necessary to
set on the EMS host the IP routes that can reach the whole network.
1. Run the OSPF dynamic routing protocol at the EMS host side. In this
method, no route needs the setting. However, be cautious when using
a dynamic route and do not advertise those invalid or possibly
repeated routes to the network, to avoid some unreachable NEs or too
large routing table. In addition, the application of dynamic routes
increases the operating load of EMS host. Therefore, it is
This default route means that all IP packets, without showing route
locally, have to pass NE 1.
Set static routes
route add 193.1.0.0 mask 255.255.0.0 193.1.1.18
route add 194.1.0.0 mask 255.255.0.0 193.1.1.18
route add 192.1.0.0 mask 255.255.0.0 193.1.1.18
The three static routes mean that all IP packets shall pass NE 1 to
access the networks 193.1, 194.1, and 192.1. In this method, the
network adapter of the EMS host must be bound to corresponding IP
address, e.g., 193.1.1.1, 194.1.1.1, 192.1.1.1 of each different
network.
In Windows 2000, the r o u t e command may be used to add, delete,
and view the relevant routes. Besides, the Ping and Tracer commands
may be used to check, whether the destination NE is reachable, and
which NEs are passed by the route.
For example:
Add default route: r o u t e a d d 0 . 0 . 0 . 0 m a s k 0 . 0 . 0 . 0 1 9 3 . 1 . 1 . 1 8
Add route: route add 193.1.0.0 mask 255.255.255.0
193.1.1.18
View route: r o u t e p r i n t
Check whether the destination NE is reachable: p i n g 1 9 2 . 1 . 7 . 1 8
Check which NEs are passed by the route: t r a c e r t 1 9 2 . 1 . 7 . 1 8
NCP Application/Logic
Upgrade
Note: The initial ZXMP S385 equipment cannot connect to the EMS terminal
computer for network data configuration or network management until the
application has been downloaded to the NCP card and the initial parameters have
been configured.
Note: The EMS of ZXONM E300 3.16R2 version or later support the 1+1 protection
for NCP cards.
7 6 5 4 3 2 1
S1
Backplane side
3. If two NCP cards are installed simultaneously, only one NCP card is the
master card and the other is the standby card at any moment during
normal running. Only the Qx, S, and ECC interfaces of the master NCP
card can communicate normally; while those interfaces of the standby
NCP card are closed. The Ethernet port of QxI card only communicates
with the master card, i.e. it can only connect one NCP card (the master
NCP card) at any moment.
Description of BOOTROM
Module on NCP Card
This section describes the functions and state switching of BOOTROM
module on NCP card.
1. Set the DIP switch to full ON state, start or reset the NCP card, it will
enter the Download state. In this state, the default value of NCP card
IP address is 192.192.192.11. Communication between the EMS and
the NCP card can only be established by connecting the EMS with the
Ethernet interface of this NCP card.
2. Set the DIP switch is set to non-full ON and non-full OFF state, start or
reset the NCP card, it will enter the Running state. In this state,
connect the EMS with the Qx interface of QxI card to establish
communication between the EMS and the master NCP card.
Upgrade Instruction
The ZXMP S385 NCP card supports local upgrade and remote upgrade of
application/logic.
Local Upgrade
Local upgrade refers to the procedure of upgrading application/logic in the
Download state. The local upgrade flowchart is shown in Figure 10.
Begin
Upgrade the
application/logic
Use telnet
method
Verify the
application/logic
Upgrade the
application/logic of the
standby NCP card
Performed in
the EMS
Verify the
application/logic version
in the EMS
End
Upgrade Preparations
The flowchart of local upgrade preparations is shown in Figure 11.
Begin
Connected
No
Is it the first time to use the CF
card?
Yes
No
Is it necessary to reconfigure the
Format the CF card NE information?
Yes
Configure the NE
information
End
1. Make sure the correct BOOTROM chip is plugged on NCP card, as each
type of NCP card can only use its own BOOTROM chip.
2. Make sure the CF card is correctly plugged on NCP.
3. Set the DIP switch on NCP card to full ON state (Download state).
4. Connect the EMS with the Ethernet interface of the NCP card, and
confirm the Ethernet cable connection between the EMS computer and
NCP card is correct.
5. Set the IP address and subnet mask of the EMS computer according to
the following rules:
IP address: 192.192.192.X (0 < X < 255 and X 11)
Subnet mask: 255.255.255.0
6. Execute the p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command on the EMS computer
to confirm that the EMS computer can connect to NCP.
7. If the CF card is not used for the first time, and it is unnecessary to
completely clear the NE data or reconfigure the NE, the upgrade
preparations finish.
8. If the CF card is not used for the first time, and it is necessary to
completely clear the NE data and reconfigure the NE, follow the steps
below:
Execute the command t e l n e t 192.192.192.11 on the EMS
computer.
The system prompts to enter user name and password which are
both empty, press ENTER directly.
Input the command f o r m a t under the prompt Z T E + > to format
the CF card, as shown in Figure 12.
FIGURE 14 ERASING THE CHIP ARE A WHICH S AVES THE APPLICATION PROGRAM
FIGURE 15 ERASING THE CHIP ARE A WHICH S AVES THE LOGIC PROGRAM
Caution: The application/logic of NCP card must be transferred to the NCP card in
the binary mode
Upgrading Application/Logic
It is to upgrade the application/logic on CF card into the application/logic
area.
<Command Format>
<Parameter Description>
Subrack-NO. 1 or 2, generally 1.
The slot number of the card. It is an integer ranging from 1 to
Slot-NO. 19; It is 18 or 19 for the NCP card.
<Command Format>
<Parameter Description>
Subrack-NO. 1 or 2, generally 1.
The slot number of the card. It is an integer ranging from 1 to
Slot-NO. 19; It is 18 or 19 for the NCP card.
3. The IP address, subnet mask and MAC address of the standby NCP
card must be the same as those of the master NCP card. Refer to step
8, point 7 of section Upgrade Preparations for how to configure the IP
address, subnet mask and MAC address.
Note:
It is unnecessary to download the database when upgrading the logic.
It is unnecessary to download the database for the standby NCP card. The data
will be automatically synchronized to the standby NCP card.
2. Right click the NCP card to be queried with the version, and the
shortcut menu pops up. Select the Card Special Version, as shown
in Figure 21.
3. The Card Special Version dialog box pops up and displays the
application/logic version of the queried NCP card, as shown in Figure
22. If the information displayed is consistent with the downloaded
application/logic version, it indicates that the newly downloaded
application/logic is running normally.
Remote Upgrade
The remote upgrade is the procedure that upgrades the application/logic
of NCP card in its Running state. The flowchart is shown in Figure 23.
Begin
Upgrade the
application/logic
Activate the
application/logic
Download the
database
Performed in the
EMS
End
Upgrade Preparations
Execute the p i n g N E - I P command at the EMS terminal. Confirm that
the EMS terminal communicates normally with the NE, and that the
ECC of the NE that is to be upgraded is smooth.
Confirm that the NCP program version comply with the current EMS
version. Ensure the validity and consistency of the versions.
3. Click the Update button, the text box of Current Working Card will
display the address information of the master NCP card (1 1 8 1 or 1
1 9 1 ).
<Command Format>
d-try Subrack-NO. Slot-NO. Card-CPU-NO. {-p\-f}
<Parameter Description>
Subrack-NO. 1 or 2, generally 1.
The slot number of the card. It is an integer ranging from 1 to
Slot-NO. 19; It is 18 or 19 for the NCP card.
For example, to try running the program file in section Upgrading the
Application/Logic, the result is shown in Figure 28.
3. When the d - t r y command completes, the NCP card is reset, and the
communication with the computer is interrupted. The ECC will be
interrupted for about one to two minutes, and during this time the
EMS cannot manage this NE. If there are two NCP cards, after the
reset, the system will switch to another NCP card first. And after the
NCP card to be upgraded starts running again, it will automatically
switch back to the upgraded NCP card, and continue the upgrade
process.
For example, to verify the program file in section Try Run of the
Application/Logic, the result is shown in Figure 29. The parameters in the
original standby area (the standby area is labeled as p r o g r a m n u m b e r :
0 x 0 2 ) that need to be verified are described in Table 105.
<Command Format>
<Parameter Description>
Subrack-NO. 1 or 2, generally 1.
The slot number of the card. It is an integer ranging from 1 to
Slot-NO. 19; It is 18 or 19 for the NCP card.
Caution: If the application/logic is not activated within 15 minutes after the try-
run, or it is not activated before resetting the NCP board, it will go back to the
original application/logic.
For example, to verify the activated program file, the operation and result
are shown in Figure 31. The parameters in the original standby area (the
standby area is labeled as p r o g r a m n u m b e r : 0 x 0 2 in Figure 31) that
need to be verified are described in Table 107.
try-run
remained time Changes to r e s e r v e d -
2. Right click the NCP card to be queried with the version, and the
shortcut menu pops up. Select the Card Special Version, as shown
in Figure 21.
3. The Card Special Version dialog box pops up and displays the
application/logic version of the queried NCP card, as shown in Figure
22. If the information displayed is consistent with the downloaded
application/logic, it indicates that the newly downloaded
application/logic is running normally.
Maintenance
Result for Reference Check Result
Item
Maintenance
Result for Reference Check Result
Item
The yellow indicator ALM1 is on, indicating minor NE/card
alarms.
The red indicator ALM2 is on, indicating severe NE/card
alarms
When normal, the green indicator NOM flashes.
The yellow indicator ALM1 is on, indicating minor NE/card
TGE2B card alarms.
The red indicator ALM2 is on, indicating severe NE/card
alarms
Summary of the indicator status: (Sum up the indicator status in this period and record the troubleshooting
details.)
Note: As the cards configured in different sites are different so the form can be
made according to actual conditions.
Maintenance Check
Maintenance Content Result for Reference
Item Result
Maintenance Check
Maintenance Content Result for Reference
Item Result
monitoring Warning alarm, the icon is purple (Record the
Minor alarm, the icon is yellow total
number of
NE working state Major alarm, the icon is orange alarms and
confirm the
number of
Critical alarm, the icon is red alarms)
Summary of maintenance:
(Summing up the equipment and EMS status in this period and recording whether the faults have been cleared. If the faults have been
solved, the troubleshooting methods should also be recorded to provide basis for future maintenance work.)
Note: As there may be no EMS configured on some sites, the form can be made
according to actual conditions.
Maintenance
Maintenance Content Check Result Remarks
Item
Maintenance
Maintenance Content Check Result Remarks
Item
(Check whether the call is connected and
Dial site A order-wire phone
whether the voice quality is normal)
(Check whether the call is connected and
Dial-back
whether the voice quality is normal)
(Check whether the call is connected and
Checking order Dial site B order-wire phone whether the voice quality is normal)
wire telephones
(Central site) (Check whether the call is connected and
Dial-back
whether the voice quality is normal)
(Check whether the call is connected and
Dial site C order-wire phone
whether the voice quality is normal)
(Check whether the call is connected and
Dial-back
whether the voice quality is normal)
When no service is configured
to the channel, a BER tester is
Channel Check used for the test. Otherwise the (Recording the tested BER)
EMS performs the test when the
bit error is 0, it is normal
Summary of maintenance:
(Summing up the check results in this period and recording the troubleshooting details)
Note: The central site needs to dial the order wire telephones of all the subnet
sites to test the voice quality of order wire, while an ordinary site just needs to dial
the central site, for test.
Recorded into
The Last The Present the Changed Checked Check
Change Date Change Date Memorandum or by by Date
not
Note: The login password should be changed once a month. The table can be
made according to actual conditions
Note: For the irregular checks of system configuration, user operation log, report
printing, and data backup, the maintenance forms can be made according to the
above forms.
Card Replacement
Card Plugging/Unplugging
Unplugging the Card
1. Hold the upper and lower ejector levers, and press down the lever
spring plates, move the levers up/down wards with appropriate force
to free the card from the slot. Figure 33 shows how to free the OL4x2
card.
2. Pinch the card ejector lever with thumb and forefinger of one hand, at
the same time hold the card panel with the other hand, and smoothly
pull the card out of the slot. Figure 34 shows how to pull out the OL4x2
card.
2. When the card is about to get into position, clamp the bayonet of
ejector lever with front beam of the sub-rack, push the ejector lever
up/down wards with both hands exerting proper force unless the
ejector lever stands upright and produces the locking sound of "clatter".
The card connector should be fully inserted into the backplane socket.
In this case, the card panel should be in parallel position with outer
frame of the card area in the cabinet. Now, the card insertion is
complete. Figure 36 shows how to plug the OL4x2 card.
Start
Prepare a spare
card
Prepare a label
Service switching
Unplug card
Restore services
Check Abnormal
working Troubleshooting
status
Normal
End
Service Switching
For the card configured with service protection or backup, the service
function processed by it should be switched to the standby card, so that
the service is not interrupted by card unplugging.
While unplugging the card without service protection or backup, the
service function of this card would be interrupted. Explain this to the user
before unplugging, and take any possible measure to minimize drawbacks
of service interruption.
Before unplugging the card, unplug the fiber pigtail and cable connected to
the card panel. Refer to Unplugging the Card for description of unplugging
operation.
1. Prepare the spare card and label as described in General Flow of Card
Replacement. Ensure the compatibility of BOOTROM and main program
of the NCP card, and EMS software.
2. Unplug the card that needs to be replaced and label it.
3. Set DIP-switch of the spare NCP card to full ON state, which makes the
NCP card to be in DOWNLOAD state; and plug the card into the sub-
rack. Then execute the command p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS
computer to check if it is possible to ping the NE.
4. Download the application and initial parameters via FTP, that are
consistent with the original NCP card; and the NCP card can reset
automatically if the setting is successful. Refer to Appendix B for the
details of NCP program download.
5. Set the fourth digit of the DIP-switch on the NCP card to OFF, and
write the NE configuration data onto the NCP card with EMS software.
6. Replacement confirmation
In the Download state, can ping 192.192.192.11 on the computer.
After replacement, select the NE that has replaced the NCP card in
the operation window at the EMS client. If the NCP time could be
extracted, it indicates the NCP card is successfully replaced.
1. Prepare the spare card and label as described in General Flow of Card
Replacement.
2. Unplug the card to be replaced, attach the label, and plug the spare
card.
3. Replacement confirmation
After replacement, the green NOM indicator light on the card flashes
slowly and regularly, and the order wire phone and data service are
normal. These indicate that the card replacement is successful.
Note: The card replacement when the multiplexing section switchover ring is
configured is too complex to describe. Conduct this kind of card replacement under
the guidance of ZTE maintenance engineers.
1. Prepare the spare card and label as described in General Flow of Card
Replacement.
2. Unplug the card to be replaced, attach the label, and plug the spare
card.
3. Replacement confirmation
After replacement, the green NOM indicator light on the card flashes
slowly and regularly, and the service performance is normal. It
indicates that the card replacement is successful.
1. Prepare the spare card and label as described in General Flow of Card
Replacement.
2. Unplug the card to be replaced, attach the label, and plug the spare
card.
3. Replacement confirmation
After replacement, the green NOM indicator light on the card flashes
slowly and regularly, and the service performance is normal. It
indicates that the card replacement is successful.
1. Prepare the spare card and label as described in General Flow of Card
Replacement.
2. Unplug the card to be replaced, attach the label, and plug the spare
card.
3. Replacement confirmation
After replacement, the green NOM indicator light on the card flashes
slowly and regularly. It indicates that the service performance is
normal, and the card replacement is successful.
Equipment Upgrade
Version Overview
To differentiate between new and old hardware/software, all of them are
to be labeled with version numbers, including equipment version, EMS
software version, card PCB version, and software versions of the NCP card
and other cards.
Hardware Upgrade
Hardware upgrade is to replace the presently in-use equipment hardware
with the equipment hardware of higher version. For successful upgrade,
make sure to modify the corresponding hardware version information in
the EMS software to free the software and hardware from cooperation
errors.
Upgrade preparations
Before upgrading the EMS software, first back up the software to be
upgraded; and carefully check the compatibility of the card hardware, card
program and the EMS software. In case of incompatibility, consider to
upgrade the card program of replace the card.
This appendix introduces the meters (including the optical power meter,
BER tester, and chip burner) that are frequently used in routine
maintenance. It covers their functions, operations, parameter setting,
and operation precautions.
Note: Since the meters with similar functions have various models, the
introduction in this appendix serves only as reference. For details on how to use
the meters, refer to their instruction manuals.
The PMS-1A optical power meter mainly serves to measure the continuous
optical signal power, employing 4-digit liquid crystal display. It is capable
of automatic measurement range switching, automatic power-off,
automatic reset zero, multi-wavelength measurement and relative power
measurement, etc. The working wavelengths of the PMS-1A optical power
meter are 1300 nm, 1310 nm, 1480 nm, and 1550 nm, which are optional.
The measurement range is -40 dBm ~ +20 dBm (0.1 nW ~ 100 mW), with
the measurement accuracy of 5%, and the detector interface is the FC
type.
Panel Description
Figure 40 describes the Front Panel of PMS-1A optical power meter.
1 7
2
3
1. Clear button. 2. WATT unit selection button. 3. dBm unit selection button
4. Wavelength selection button 5. External power supply plug.
6. Relative measurement state switching button 7. Power switch. 8. LCD.
9. Detector interface
Operation Flow
Figure 41 shows the operation flow of measurement via the PMS-1A
optical power meter, along with the specific operation in each step.
Press ON/OFF to
power on optic power
meter
Press to select
wavelength
Press CLEAR to
clear all digits
Connect optical
source to be tested
with optical power
meter
Relative power
Select measurement
measurement
mode
Absolute power Press dBrel to
measurement enter relative
measurement state
dBm
Select unit
dBm
WATT Select unit
Press
Press dBm WATT
WATT
Press
Press dBm
WATT
Precautions
Remember to recharge the batteries in time.
Cover the detector before the clearing operation lest the light enter
inside and affect the measurements.
The ALL-11 chip burner serves to burn E/EPROM, MCU/MPU, and PLD. It is
connected with the PC through RS232C serial port or parallel port of the
PC, and it is controlled by the special program installed in the Windows
system. With the IC multi-tap or conversion socket, the ALL-11 chip
burner is compatible with most of the present IC models and packages.
Panel Description
Figure 43 shows the panel of the ALL-11 chip burner.
9 8 7
1 2 3
1
3
Operation Flow
Figure 45 shows the operation flow for burning a chip with ALL-11 chip
burner. Before burning, make sure that the chip burner is connected with
PC, the given burning software has been properly/successfully installed on
PC, and the connection between the PC and chip burner has been
established.
Select a chip
manufacturer
Read from
Select source another chip
of chip contents
Read Insert the source chip
from a file into the chip burner
Select the file and load
it
No
Verification passed?
Yes
Burning succeeds
Precautions
During the operation, observe the device indicator lights status and
check whether it complies with the current operation. If any
incompliance, pause the operation to find out the cause.
In the program, the chip manufacturer information, its type and model
should be set as per actual chip. The file format should be set
according to the format of actual file. The two common file formats are
BIN and HEX. A file with the extension of BIN is binary file, and its file
format should be selected as Binary. A file with the extension of HEX is
hexadecimal file, and its file format should be selected as Intel HEX.
To insert the chip into the chip burner socket, ensure that pins are in
the correct sequence by follow the Chip insertion guide shown in Figure
44. Usually, lower part of the chip should be aligned with the bottom of
the socket.
Pull over the socket extractor lever before inserting the chip, and press
it down after insertion. Make sure the chips pins are in reliable contact.
Figure 44 shows the extractor levers positions.
Panel Description
Figure 47 shows the panel of YGBERT-2M BER tester.
18 16
17
Power
1
2
15
4 No signal
AIS
5 No sync
Bit Error
6
Setup
7
Select
8
9 Start/Stop
10
BE/BER
11
G.821
12
Tx Bit Error
13
14
Operation Flow
Figure 48 shows the operation flow for testing bit errors with YGBERT-2M
BER tester.
Start test
Stop test
Precautions
Remember to recharge the battery in time. The fully charged battery
can last for about four consecutive hours. Use the external power
supply for 24-hour bit error test.
Select the code pattern of PRBS15 for testing the SDH equipment.
SDH Analyzer
Figure 49 shows the external view of HP37718A SDH analyzer.
Alarm
Page
Detection Alarm Name Alarm Level
No.
Point
Loss of received 2.5 G optical signal Critical 78
Loss of received 622 M optical signal Critical 79
Loss of received 155 M optical signal Critical 80
Physical layer Loss of 155 M electrical signal Critical 80
Loss of received 2 M electrical signal Critical 81
CV performance over-threshold Warning 82
Receiving optical power over-threshold Major 82
Loss of frame Critical 83
Unavailable time starts Major 84
B1 UAS performance over-threshold Major 84
Out of frame Critical 85
Regenerator
OFS performance over-threshold Major 86
section layer
Regenerator section signal degraded Minor 87
B1 SES performance over-threshold Major 88
B1 ES performance over-threshold Major 89
B1 BBE performance over-threshold Major 90
Multiplex section Multiplex section alarm indication signal Major 91
layer
Unavailable time starts Major 92
Multiplex section remote defection indication Minor 93
B2 UAS performance over-threshold Major 94
B2 FEUAS performance over-threshold Major 94
Multiplex section signal degraded Minor 95
B2 bit error cross-threshold Major 96
B2 SES performance over-threshold Major 97
B2 FESES performance over-threshold Major 98
Alarm
Page
Detection Alarm Name Alarm Level
No.
Point
B2 ES performance over-threshold Major 99
B2 FEES performance over-threshold Major 100
B2 BBE performance over-threshold Major 101
B2 FEBBE performance over-threshold Major 102
Multiplex section protection switching event Minor 103
AU4 path alarm indication signal, Unavailable
Major 104
time starts
Loss of AU4 pointer Critical 105
Remote defect indication (higher-order VC4
Minor 105
path virtual container)
B3 UAS performance over-threshold (higher-
Major 106
order VC4 path virtual container)
B3 FEUAS performance over-threshold
Major 107
(higher-order VC4 path virtual container)
VC4 higher-order path signal degraded Minor 108
B3 SES performance over-threshold (higher-
Major 109
order VC4 path virtual container)
Management
unit (AU4), B3 FESES performance over-threshold
Major 109
tributary unit (higher-order VC4 path virtual container)
(TU3), Higher-
B3 ES performance over-threshold (higher-
order path Major 110
order VC4 path virtual container)
(VC4/VC3)
B3 FEES performance over-threshold (higher-
Major 111
order VC4 path virtual container)
B3 BBE performance over-threshold (higher-
Major 112
order VC4 path virtual container)
B3 FEBBE performance over-threshold
Major 112
(higher-order VC4 path virtual container)
VC4 higher-order path unequipped Major 113
VC4 higher-order path trace ID mismatch Major 114
VC4 signal label mismatch Major 115
AU4 PJE+/PJE- performance over-threshold Critical 115
AU4 protection switching event Minor 116
TU12 path alarm indication signal, Unavailable
Major 117
time starts
Loss of TU12 pointer Critical 117
Tributary unit Remote defect indication Minor 118
(TU12) and
lower-order path V5 UAS performance over-threshold Major 118
(VC12)
V5 FEUAS performance over-threshold Major 119
V5 SES performance over-threshold Major 120
V5 FESES performance over-threshold Major 120
Alarm
Page
Detection Alarm Name Alarm Level
No.
Point
V5 ES performance over-threshold Major 121
Tributary unit
(TU12) and V5 FEES performance over-threshold Major 121
lower-order path V5 BBE performance over-threshold Major 122
(VC12)
V5 FEBBE performance over-threshold Major 122
TU12 PJE+/PJE- performance over-threshold Major 123
TU12 protection switching event Minor 123
Abbreviations
A
ADM Add/Drop Multiplexer
AGENT Agent
AI Adapted Information
AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
ANSI American National Standards Institute
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
AU-n Administrative Unit, level n
AUG Administrative Unit Group
B
BA Booster Amplifier
BBER Background Block Error Ratio
BER Bit Error Ratio
BIP-X Bit Interleaved Parity of depth X
BITS Building Integrated Timing Supply
C
CE CONFORMITE EUROPENDE
CF Compact Flash
CM Connection Matrix
CMIP Common Management Information Protocol
C-n Container-n
CP Connection Point
CRC Cyclic Redundancy Check
CS Cross Switch
CTP Connection Termination Point
CV Coding Violation
D
DC Direct Current
I
IC Integrated Circuit.
IP Internet Protocol
ITE Integrated Terminal Equipment
International Telecommunication
ITU-T
Union-Telecommunication Standardization Sector
L
L2 Layer 2
LAN Local Area Network
LAPD Link Access Procedure for D-channel
LA Line Amplifier
LMT Local Management Terminal
LO Lower Order
LOF Loss Of Frame
LOM Loss Of Multiframe
LOP Loss Of Pointer
LOS Loss Of Signal
LP Lower-order Path
LPA Lower-order Path Adaptation
LPC Lower-order Path Connection
LPP Lower-order Path Protection
LIT Loss of all Incoming Timing references
M
MAF Management Application Function
MC Matrix Connection
MCU Management Control Unit
MD Mediation Device
MF Mediation Function
MM Multi Mode (optical fiber)
MS Multiplex Section
MS-AIS Multiplex Section - Alarm Indication Signal
MSOH Multiplex Section OverHead
MSP Multiplex Section Protection
MS-PSC Multiplex Section - Protection Switching Count
MS-PSD Multiplex Section - Protection Switching Duration
MS-SPRing Multiplex Section Shared Protection Ring
MST Multiplex Section Termination
MTIE Maximum Time Interval Error
N
NC Network Connection
NE Network Element
NEF Network Element Function
T
TCM Tandem Connection Monitor
TCP Termination Connection Point
TCS Time division Cross-connect
TD Transmit Degrade
TDEV Time Deviation
TF Transmit Fail
TM Terminal Multiplexer
TMN Telecommunications Management Network
TS Time Slot
TSA Time Slot Assignment
TU-m Tributary Unit, level m
TUG-m Tributary Unit Group, level m
U
UAS Unavailable Second
UNEQ UN-Equipped
UNI User Network Interface
V
VC-n Virtual Container, level n
W
WAN Wide Area Network
WDM Wavelength Division Multiplexing
WS Work Station
WSF Work Station Function
WTR Wait to Restore Time