SJ-20140214110341-004-Unitrans ZXMP S385 (V3.30) Maintenance Manual (Volume I) Routine Maintenance

ZXMP S385
SDH Based Multi-Service Node Equipment

Maintenance Manual (Volume
I) Routine Maintenance
Version: V3.30
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.1 2015-01-25 Added the SEEU board.
R1.0 2014-03-30 Fisrt edition
Serial Number: SJ-20140214110341-004
Publishing Date: 2015-01-25(R1.1)
SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Safety Instructions.................................................................... 1-1
1.1 Safety Precautions ............................................................................................. 1-1
1.2 Safety Signs ...................................................................................................... 1-1
Chapter 2 Maintenance Overview ............................................................. 2-1

2.1 Maintenance Classification ................................................................................. 2-1
2.2 Requirements of Tools and Instruments ............................................................... 2-1
2.3 Equipment Room Maintenance Rules .................................................................. 2-5
2.3.1 Work Rules in the Equipment Room .......................................................... 2-5
2.3.2 Shift Handover Rules in the Equipment Room ............................................ 2-6
2.4 List of Routine Maintenance Items....................................................................... 2-6
2.5 Maintenance Precautions ................................................................................... 2-7
2.5.1 Precautions in Board Maintenance ............................................................ 2-7
2.5.2 Precautions in Optical Interface Maintenance............................................. 2-7
2.5.3 Precautions in Equipment Maintenance ..................................................... 2-8
2.5.4 EMS Maintenance Precautions ................................................................. 2-8
Chapter 3 Environment Maintenance ....................................................... 3-1

3.1 Cleanness Requirements.................................................................................... 3-1
3.2 Temperature and Humidity Requirements ............................................................ 3-2
3.3 Clear Height....................................................................................................... 3-2
3.4 Lightning Protection Requirements ...................................................................... 3-2
3.5 Lighting in the Equipment Room.......................................................................... 3-3
3.6 Chutes and Apertures in the Equipment Room ..................................................... 3-3
3.7 Equipment Power Supply.................................................................................... 3-4
3.8 AC Power Supply ............................................................................................... 3-4
3.9 Air Conditioning System...................................................................................... 3-4
3.10 Fire Protection Facilities.................................................................................... 3-5
3.11 Maintenance Space .......................................................................................... 3-5
Chapter 4 Equipment Maintenance Operations....................................... 4-1

4.1 Checking the Audio Alarm................................................................................... 4-1
4.2 Observing Cabinet Indicators .............................................................................. 4-2
4.3 Observing Board Indicators................................................................................. 4-3
4.4 Checking the Fan ............................................................................................... 4-4

4.5 Cleaning the Dustproof Unit ................................................................................ 4-4
4.6 Checking Groundings ......................................................................................... 4-5
4.7 Service Inspection - Bit Error Test........................................................................ 4-6
4.8 Removing/Installing the Filler Door ...................................................................... 4-6
4.8.1 Removing Filler Door................................................................................ 4-6
4.8.2 Installing Filler Door.................................................................................. 4-7
4.9 Installing Board .................................................................................................. 4-8
4.9.1 Board Operation Precautions .................................................................... 4-8
4.9.2 Board Slots in a Subrack .......................................................................... 4-9
4.9.3 Plugging a Lower-Level Board ................................................................ 4-16
4.9.4 Unplugging a Lower-Level Board............................................................. 4-17
4.9.5 Plugging an Upper-Level Board............................................................... 4-18
4.9.6 Unplugging an Upper-Level Board........................................................... 4-19
4.10 Plugging/Unplugging Fiber Pigtail .................................................................... 4-20
4.10.1 Plugging Fiber Pigtail (LC/PC)............................................................... 4-20
4.10.2 Unplugging Fiber Pigtail (LC/PC) ........................................................... 4-21
4.11 Optical Power Test.......................................................................................... 4-21
4.11.1 Cautions of Optical Power Test .............................................................. 4-21
4.11.2 Optical Launched Power Test ................................................................ 4-22
4.11.3 Optical Received Power Test ................................................................. 4-23
Chapter 5 EMS Maintenance Operations ................................................. 5-1

5.1 Managing Users ................................................................................................. 5-1
5.2 Monitoring Topology Map Status and NE Status ................................................... 5-2
5.3 Checking the Board Operating Status .................................................................. 5-4
5.4 Monitoring Alarms .............................................................................................. 5-5
5.5 Monitoring Performances .................................................................................... 5-6
5.6 Monitoring Events .............................................................................................. 5-7
5.7 Synchronizing Data ............................................................................................ 5-7
5.8 Querying EMS Logs ........................................................................................... 5-8
5.9 Printing Reports ............................................................................................... 5-10
5.10 Back Up Data..................................................................................................5-11
5.11 Restoring the Basic Data................................................................................. 5-12
5.12 Restoring Log, Alarm or Performance Data ...................................................... 5-14
5.13 Managing the NE Time ................................................................................... 5-15
Appendix A Maintenance Forms.............................................................. A-1

A.1 Half-day Maintenance Record............................................................................. A-1
A.2 Daily Maintenance Record.................................................................................. A-3
II

A.3 Weekly Maintenance Record .............................................................................. A-5
A.4 Login Password Change Record......................................................................... A-6
Appendix B NE Address Definition and Route Configuration .............. B-1

B.1 Definition of the NE IP Address........................................................................... B-1
B.1.1 FLSM Addressing .................................................................................... B-1
B.1.2 VLSM Addressing .................................................................................... B-3
B.2 Example of Network Address Coding of NEs ....................................................... B-5
B.3 Address and Route Configuration of the EMS Host .............................................. B-8
B.3.1 EMS Host Address................................................................................... B-8
B.3.2 Route Configuration ................................................................................. B-9
B.3.3 Route Configuration Commands ............................................................... B-9
Appendix C Configuration Description of NCP/ENCP Agent

Program ................................................................................................. C-1
C.1 Description of NCP Board ..................................................................................C-1
C.2 Description of BOOTROM Module on NCP Board................................................C-2
C.2.1 Functions of BOOTROM Module on NCP..................................................C-2
C.2.2 NCP Board State Switching......................................................................C-3
C.3 Local Upgrade Instructions .................................................................................C-3
C.3.1 Local Upgrade Flowchart..........................................................................C-3
C.3.2 Local Upgrade Preparations .....................................................................C-4
C.3.3 Clearing the Database Locally ..................................................................C-8
C.3.4 Downloading the Application/Logic Locally ................................................C-8
C.3.5 Upgrading the Application/Logic Locally ....................................................C-9
C.3.6 Verifying the Application/Logic After Local Upgrade.................................. C-11
C.3.7 Upgrading the Application/Logic for Standby NCP Locally ........................ C-13
C.3.8 Downloading the Database Locally ......................................................... C-13
C.4 Remote Upgrade Instructions ........................................................................... C-15
C.4.1 Remote Upgrade Flowchart.................................................................... C-15
C.4.2 Remote Upgrade Preparations ............................................................... C-17
C.4.3 Confirming the Address of the Master NCP Board.................................... C-17
C.4.4 Downloading the Application/Logic Remotely........................................... C-17
C.4.5 Upgrading the Application/Logic Remotely............................................... C-18
C.4.6 Verifying the Application/Logic After Remote Upgrade.............................. C-19
C.4.7 Try Running the Application/Logic ........................................................... C-21
C.4.8 Verifying the Application/Logic After Try Run ........................................... C-22
C.4.9 Activating the Application/Logic .............................................................. C-24
C.4.10 Verifying the Activated Application/Logic................................................ C-25
III

C.4.11 Upgrading the Application/Logic for Standby NCP Remotely ................... C-27
C.4.12 Downloading the Database Remotely.................................................... C-28
C.5 Verifying the Application/Logic Version on EMS ................................................ C-29
Appendix D Initialization and Upgrade of NE with ANCP/ANCPB

Board...................................................................................................... D-1
D.1 Overview...........................................................................................................D-1
D.2 Local Initialization ..............................................................................................D-2
D.2.1 Local Upgrade Preparations .....................................................................D-2
D.2.2 Clearing Database Locally........................................................................D-6
D.2.3 Uploading Application/Logical Programs Locally ........................................D-6
D.2.4 Loading Application/Logical Programs Locally ...........................................D-7
D.3 Remote Initialization...........................................................................................D-9
D.3.1 Remote Upgrade Preparations .................................................................D-9
D.3.2 Uploading Application/Logical Programs Remotely .................................. D-10
D.3.3 Loading Application/Logical Programs Remotely (Single ANCP Board)...... D-11
D.3.4 Loading Application/Logical Programs Remotely (Dual ANCP Boards) ...... D-15
D.4 Downloading Database .................................................................................... D-20
D.5 Verifying Application/Logical Program Version in EMS........................................ D-21
Appendix E Simple Commissioning .........................................................E-1

E.1 Overview .......................................................................................................... E-1
E.2 Performing Simple Commissioning Through Telnet .............................................. E-3
E.3 Performing Simple Commissioning Through the EMS .......................................... E-5
Appendix F Board Replacement ...............................................................F-1

F.1 Flowchart of Board Replacement......................................................................... F-1
F.2 Board Replacement Procedure............................................................................ F-4
F.2.1 Replacing NE Control Processor (NCP/ENCP/ANCP/ANCPB) .................... F-4
F.2.2 Replace the Cross-connect and Clock Board (CSA/CSE/CSF/CSC) ............ F-4
F.2.3 Replacing the Orderwire Board (OW)......................................................... F-5
F.2.4 Replacing the Optical Line Board............................................................... F-5
F.2.5 Replacing the Line Processor (LP1x8) ....................................................... F-7
F.2.6 Replacing the Electrical Processor ............................................................ F-7
F.2.7 Replacing the Optical E1 Tributary Board ................................................... F-7
F.2.8 Replacing the Optical/Electrical Processor (OEL1x16) ................................ F-8
F.2.9 Replacing the Ethernet Board.................................................................... F-8
F.2.10 Replacing the ATM Processor (AP1x8) .................................................... F-8
F.2.11 Replacing the Service Management Interface Board (SMI) ........................ F-9
Appendix G Board Indicator Status......................................................... G-1
IV

G.1 Indicator Status When Boards Are Working ........................................................ G-1
G.1.1 Indicator Status of the NCP/ENCP/ANCP Board....................................... G-1
G.1.2 Indicator Status of the CSA/CSE/CSF/CSC Board .................................... G-2
G.1.3 Indicator Status of the OW Board ............................................................ G-4
G.1.4 Indicator Status of the LP1x8 Board......................................................... G-4
G.1.5 Indicator Status of the OAD Board ........................................................... G-5
G.1.6 Indicator Status of the OA Board ............................................................. G-5
G.1.7 Indicator Status of the Electrical Tributary Board....................................... G-6
G.1.8 Indicator Status of OPE1Z Board............................................................. G-7
G.1.9 Indicator Status of the Optical Line Board................................................. G-8
G.1.10 Indicator Status of the Optical/Electrical Processor ................................. G-8
G.1.11 Indicator Status of the Ethernet Processor .............................................. G-9
G.1.12 Indicator Status of the ATM Processor (AP1x8) .....................................G-13
G.2 Board Indicator Status During Power-On Initiation .............................................G-13
G.2.1 Indicator Status of NCP/ENCP/ANCP/ANCPB Board During Power-On
Initiation ...............................................................................................G-13
G.2.2 Indicator Status of Other Boards (Except NCP/ENCP/ANCP/ANCPB)
During Power-On and Initialization .........................................................G-14
G.3 Indicator Status of Boards When Waiting for Configuration .................................G-15
G.4 Indicator Status of Boards in a 1:N Protection Group .........................................G-16
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .......................................................................................................VII

This page intentionally left blank.
VI

About This Manual
Purpose
This manual is applicable to the Unitrans ZXMP S385 Synchronous Digital Hierarchy
(SDH) based multi-service node equipment.
ZXMP S385 (V3.30) is a multi-service node equipment with the highest transmission rate
at 10 Gbit/s. It supports the Automatically Switched Optical Network (ASON) function and
can be applied to the transmission network (at the access layer and convergence layer).
Intended Audience
This manual is intended for the following engineers and technicians:
l Element Management System (EMS) supervision engineers
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters.
Chapter Contents
Chapter 1, Safety Describes the safety precautions for equipment maintenance.

Instructions
Chapter 2, Describes the basic information of equipment maintenance, including

Maintenance maintenance classification, tools and instruments for maintenance, basic
Overview operation and precautions of equipment maintenance.
Chapter 3, Describes the environment requirements in the equipment room, including

Environment the requirements for temperature/humidity, cleanness, electromagnetic
Maintenance environment, electrostatic protection, power supply, lightning protection,
protection system, air conditioning system, fire protection facilities, and
maintenance space.
Chapter 4, Describes the basic operations for equipment maintenance.

Equipment
Maintenance
Operations
Chapter 5, EMS Describes the basic operations for EMS maintenance.

Maintenance
Operations
Appendix A, Describes the forms for recording the routine maintenances.

Maintenance Forms

Chapter Contents
Appendix B, Describes how to define the NE address and configure the route of the NE
NE Address management server during networking.
Definition and Route
Configuration
Appendix C, Describes the operations for upgrading the Agent program of the NCP/ENCP
Configuration board.
Description of
NCP/ENCP Agent
Program
Appendix D, Describes the operations for initializing and upgrading the NE of the ANCP
Initialization and board.
Upgrade of NE
with ANCP/ANCPB
Board
Appendix E, Simple Describes the simple commissioning methods, including simple commissioning
Commissioning through Telnet and simple commissioning through EMS.
Appendix F, Board Describes the board replacement issues, including preparations, operational
Replacement procedure, and precautions.
Appendix G, Board Describes indicator statuses when the boards are operating, being powered
Indicator Status on and initiated, waiting for configuration, and in a 1 : N protection group.
Related Documentation
The following documents are related to this manual:
Manual Contents
Unitrans ZXMP S385 (V3.30) SDH Based Describes the system architecture, system
Multi-Service Node Equipment Product features, system functions, technical
Description specifications, and application example.
Unitrans ZXMP S385 (V3.30) SDH Based Describes the equipment hardware, including
Multi-Service Node Equipment Hardware cabinet, power distribution box, power monitoring
Description box, subrack, boards, interfaces, and indicators.
Unitrans ZXMP S385 (V3.30) SDH Based Describes the equipment installation procedures,
Multi-Service Node Equipment Installation including installation preparation, hardware
Manual installation, cable layout, installation inspection,
and power on/off operations.
Unitrans ZXMP S385 (V3.30) SDH Based Describes the handling methods for the
Multi-Service Node Equipment Maintenance equipment alarms and performance events.
Manual (Volume II) Alarms and Performances
II

Manual Contents
Unitrans ZXMP S385 (V3.30) SDH Based Describes the analyses and solutions for some
Multi-Service Node Equipment Maintenance common faults.
Manual (Volume III) Troubleshooting
Conventions
This manual may contain the following symbols. The meanings are as listed as follows:
Symbol Meaning
Indicates an imminently hazardous situation. Failure to comply can result in death

Danger
or serious injury, equipment damage, or site breakdown.
Indicates a potentially hazardous situation. Failure to comply can result in serious

Warning
injury, equipment damage, or interruption of major services.
Indicates a potentially hazardous situation. Failure to comply can result in moderate

Caution
injury, equipment damage, or interruption of minor services.
Provides additional information about a particular topic.

Note
Indicates a suggestion or hint to make things easier or more productive for the
Tip
reader.
III

IV

Chapter 1
Safety Instructions
Table of Contents
Safety Precautions .....................................................................................................1-1
Safety Signs ...............................................................................................................1-1
1.1 Safety Precautions

l Only qualified professionals are entitled to install, operate and maintain the equipment.
l Comply with the local safety rules and related operation regulations during the
equipment installation, operation and maintenance, to avoid personal injuries or
equipment damages.
l The safety precautions in this manual are only a supplement to the local safety rules.
ZTE Corporation assumes no responsibility for consequences resulted from violation of
general safety operation specifications or of safety rules for design, production and use of
equipment.
1.2 Safety Signs

Table 1-1 lists the safety signs used in this manual, which remind users of the safety
precautions to be taken when the equipment is installed, operated and maintained.
Table 1-1 Safety Signs and Descriptions
Safety Sign Meaning
Call for notice
Caution against electrostatic discharge
Warn against electric shock
Warn against laser
Three safety levels are indicated: danger, warning, and caution. Presented below are their
meanings.
1-1

ZXMP S385 Maintenance Manual (Volume I) Routine Maintenance
Danger!
Casualties or a major accident such as equipment damage may occur if you ignore this
safety warning.
Warning!
A major or severe accident or equipment damage may occur if you ignore this safety
warning.
Caution!
An accident or equipment damage may occur if you ignore this safety warning.
1-2

Chapter 2
Maintenance Overview
Table of Contents
Maintenance Classification .........................................................................................2-1
Requirements of Tools and Instruments......................................................................2-1
Equipment Room Maintenance Rules.........................................................................2-5
List of Routine Maintenance Items..............................................................................2-6
Maintenance Precautions ..........................................................................................2-7
2.1 Maintenance Classification

Equipment maintenance is divided into routine maintenance, and emergency
maintenance.
1. Routine Maintenance
Routine maintenance involves checking the equipment operation status periodically,

and handling the problems promptly; so as to locate hidden troubles, prevent
accidents, locate faults and handle them as early as possible.
2. 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.
2.2 Requirements of Tools and Instruments

Maintenance Tools and Materials
For common maintenance tools used in equipment room, refer to Table 2-1.
Table 2-1 Common Maintenance Tools
Name Remark Function
Tape It is used for measurement.
2-1

Screwdrivers It includes I size cross screwdriver, II size

cross screwdriver, I size straight screwdriver, II
size straight screwdriver for fixing screws.
Nippers It is used to nip wires, elements, and integrated

circuit pins.
Adjustable wrench It is used to fix screws.
Diagonal pliers It is used to trim cable clips.
Sharp nose pliers It is used to trim the cable with fine cable
diameter, bend single-stranded conductor
joint, strip plastic insulation layer, and nip small
accessories.
Wire stripper It is used to strip cable skins.
Wallpaper knife It is used to cut papers.
Electrical knife It is used to pare insulation layer of the wire.
Crimping Pliers It is used to crimp lugs.
Clamping pincers It is used to clamp the crystal head of network

cable.
IC extractor It is used to plug/unplug chips.
2-2

Chapter 2 Maintenance Overview
Antistatic wrist It is used to connect with ground to effectively

strap protect electrostatic sensitivity devices and
PCB.
Pliers It is used for taking or pinch-off operation.
Fiber extractor It is used to plug/unplug cables or fibers.
Marker It is used to mark on different materials, such

as paper, wood, metal, and plastics.
• In the engineering practice, select tools with appropriate specifications in accordance with actual re
quirements.
For common maintenance materials, refer to Table 2-2.
Table 2-2 Common Maintenance Materials
Name Remark
absolute alcohol -
air-laid paper -
soldering-tin cord -
rosin -
insulating tape -
nylon adhesive hook-and-loop tape -
strap
fiber-pigtail jumper
Instruments/Meters
For common instruments/meters used in equipment room, refer to Table 2-3.
2-3

Table 2-3 Common Instruments/Meters
Name Remark
Meters for It includes thermometers and hygrometers for detecting the equipment operating
Environment environment.
Monitoring
Instru- It includes a digital multimeter, an optical power meter, an optical attenuator and a
ments/Meters PDH (Plesiochronous Digital Hierarchy) bit error tester.
for Mainte- l Digital multimeter
nance
l Optical power meter
l Optical attenuator
l Flange
If possible, prepare one SDH (Synchronous Digital Hierarchy) synthetic analyzer to

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

sites, prepare a portable PC (with built-in MODEM , Ethernet adapter, and a
straight-through cable).
• In the engineering practice, select tools with appropriate specifications in accordance with actual re
quirements.
2-4

Caution!
All the instruments/meters must be checked and calibrated before using, to ensure their
accuracies and good conditions.
Note:
For further information about the usage of instrument/meter, refer to its operating
instruction.
2.3 Equipment Room Maintenance Rules

A complete set of effective maintenance rules must be developed to ensure that the
equipment room environment satisfies the equipment operating requirements, and for
better equipment maintenance. All the maintenance personnel must observe these rules.
2.3.1 Work Rules in the Equipment Room

Recommended Action
l Maintain the equipment room tidy, clean and in order.
Change shoes at the door, maintain the floor clean, maintain the equipment air-laid,
arrange the equipment properly; Ensure that the instruments are precise, the tools
are ready and the materials are complete.
l Put on antistatic wrist strap before operating the equipment.

l Take care of the public properties in the equipment room.
l Maintain proper records and statistics of the original data. Ensure that the technical
documents and original records are authentic and complete.
l The person on duty must be dutiful. Handle and report any major fault and accident
promptly.
l There must be leaders who conduct regular checks for the equipment room, and make
continuous improvement.
Forbidden Action
l Do not smoke, eat, or play games.
l Do not talk loudly in the equipment room.
l Do not put personal articles around in the equipment room.
l Do not perform any irrelevant operations to the job.
l Do not bring inflammable or explosive articles into the equipment room.
2-5

l Unauthorized entry into the equipment room is not allowed.

l Do not disclose any confidential information.
2.3.2 Shift Handover Rules in the Equipment Room

Recommended Action
l The persons on duty must perform shift handover seriously. The responsibilities and
formalities must be clearly defined to ensure smooth shift handover.
l The person on the previous shift must, before going off duty, provide clear information
about his shift to the person on the next shift; The person on the next shift must conduct
careful checks before taking over the duty.
l During the shift handover, ensure the equipment operating status, and ensure that
the state of the tools and instruments are clear, various drawings and records are
complete.
l The person on the previous shift must stay on duty until the person on the next shift
arrives and the shift handover is completed.
l After proper shift handover, the persons of both shifts must sign on the work log as a
written record, indicating that the equipment has been handed over to the next shift.
l If faults occur during shift handover, the persons of both shifts must be responsible
for the troubleshooting.
Forbidden Action
l The person on the previous shift must stay on duty until the person on the next shift
arrives.
l If faults occur during shift handover, the persons of both shifts must not pass the buck.
2.4 List of Routine Maintenance Items

For the routine maintenance items and periods of ZXMP S385, refer to Table 2-4.
Table 2-4 List of Routine Maintenance Items of ZXMP S385
Maintenance Item Period
Environment maintenance 1 day
Equipment Check audio alarms of the equipment 1 day

maintenance
Observe cabinet indicator lights 1 day
Observe board indicator lights 0.5 day
Check the fan and clean the air filter 2 weeks
Check orderwire telephones 2 weeks
Check services 2 weeks
2-6

Maintenance Item Period
EMS maintenance Manage users (change login 1 month

password)
Check the EMS connection 1 day
Monitor topology map 1 day
Monitor alarms 1 day
Monitor performances 1 day
Query system configurations Irregular
Query security logs Irregular
Print reports Irregular
Back up data Irregular
2.5 Maintenance Precautions

2.5.1 Precautions in Board Maintenance
l Take proper antistatic measures in equipment maintenance to avoid any damage
to the equipment. As human body may generate electrostatic charge that persists
for long, one should wear antistatic wrist straps and well ground them at the other
end before touching the equipment, in order to prevent human static electricity from
damaging sensitive components and devices. The boards not in use should be kept
in the antistatic bags.
l Pay attention to the damp-proof handling of the boards. The environment temperature
and humidity effect must be taken into consideration for standby board storage.
Normally, put some desiccant in the antistatic bags of the board, to maintain the bag
inside dry. When a board is moved from a colder and drier place to a hotter and
damper place, wait for at least 30 minutes before unpacking it. Otherwise, moisture
may condense on the board surface and damage the components.
l Be careful to plug/unplug the boards. There are multiple pins in each board slot on the
equipment motherboard. Any pin is distorted or falls accidentally, the normal operation
of the entire system will be affected, or even worse, short circuit may be caused and
make the equipment down.
2.5.2 Precautions in Optical Interface Maintenance

l Be sure to cover the unused optical interfaces of the optical interface board with the
dustproof caps. This not only protects the maintenance persons' eyes during their
casual direct viewing on the optical ports, but also protects optical interfaces against
dust. Once dust enters the optical interface, it may affect the output optical power of
2-7

the transmitting optical interface and the receiving sensitivity of the receiving optical
interface.
l Be sure to cover fiber pigtail connectors with dust caps once unplugged.
l Do not look straight into the optical interface on the optical board to protect your eyes
from being burnt by laser.
l Use dust-free paper dipped in absolute alcohol to clean fiber pigtail connectors
carefully. Do not use ordinary industrial alcohol, medical alcohol or water.
l When replacing an optical board, be sure to unplug the fiber pigtails on it before un-
plugging this optical board.
2.5.3 Precautions in Equipment Maintenance

1. Never install or disconnect any power cables without turning off the power switch.
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.
2. Once the equipment is in service, pulling out the fan without reason is forbidden.
Clean the dust filter mesh of the fan regularly in accordance with the equipment room
environment conditions to ensure good heat dissipation of the equipment.
3. After the maintenance operations on the equipment, close the cabinet door to ensure
the equipment always has an excellent anti electromagnetic-interference performance.
2.5.4 EMS Maintenance Precautions

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

Chapter 3
Environment Maintenance
Table of Contents
Cleanness Requirements ...........................................................................................3-1
Temperature and Humidity Requirements...................................................................3-2
Clear Height ...............................................................................................................3-2
Lightning Protection Requirements.............................................................................3-2
Lighting in the Equipment Room.................................................................................3-3
Chutes and Apertures in the Equipment Room ...........................................................3-3
Equipment Power Supply ...........................................................................................3-4
AC Power Supply .......................................................................................................3-4
Air Conditioning System .............................................................................................3-4
Fire Protection Facilities .............................................................................................3-5
Maintenance Space....................................................................................................3-5
3.1 Cleanness Requirements

Cleanness requirements include requirements for dust and harmful gases in the air. The
ZXMP S385 equipment should operate in the equipment room that meets the cleanness
requirements described below.
1. The equipment room should be free of explosive, conductive, magnetic-conductive or
corrosive dust.
2. The density of dust particles with the diameter greater than 5µm cannot be more than
3×104 particles/m3.
3. There should be no corrosive metal or insulation-destructive gas in the equipment,
such as SO2, H2S, NH3, and NO2. For the detailed information, refer to Table 3-1.
4. The equipment room should be always kept clean, with doors and windows tightly
sealed.
Table 3-1 Density Limit of Hazardous Gases in the Equipment
Gas Average (mg/m3) Maximum (mg/m3)
SO2 0.2 1.5
H2S 0.006 0.030
NO2 0.04 0.15
NH3 0.05 0.15
Cl2 0.01 0.30
3-1

3.2 Temperature and Humidity Requirements

For the requirements of ZXMP S385 for temperature and relative humidity, refer to Table
3-2.
Table 3-2 Temperature and Humidity Requirements
Item Specification
Working temperature Long-term operating 0 ℃ to +45 ℃
Short-term operating -10 ℃ to +55 ℃
Relative humidity 5% to 95%
• The temperature and humidity are measured 1.5 m above the floor and 0.4 m in front of the equipm
ent.
3.3 Clear Height

The clear height of the equipment room cannot be 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.
3.4 Lightning Protection Requirements

Typical lightning protections of power supply fall into three classes. For the detailed
information, refer to Table 3-3.
Table 3-3 Typical Lightning Protection Classes of Power Supply
Lightning Protection Parameter Position of Lightning

Class Protection Circuit
Class B (Elementary class) 40 kA (8 μs /20 μs) AC power distribution

screen (box)
Class C (Lower class) 20 kA (8 μs /20 μs) DC power supply cabinet
Class D (Lowest class) 6000 V (combined wave) -48 V power supply rectifier
ZXMP S385 must meet the following lightning protection requirements:

l The power lightning protection requirements in the central equipment room are as
follows.
à AC power cables should be led underground in the equipment room.
3-2

Chapter 3 Environment Maintenance
à Because the AC power distribution board and the DC power cabinet are in the
same equipment room, the distance between Class B and Class C lightning
protection units should meet the following decoupling distance requirements.
When the protection grounding bar is laid independently, the distance between
Class B and Class C lightning protection units cannot be less than 5 m. When
the protection grounding bar and the power cords are laid in parallel, the distance
between Class B and Class C lightning protection units should not be less than
15 m.
à If the required decoupling distance cannot be satisfied due to some restrictions
in the equipment room, additional decoupling inductor should be installed before
the Class C lightning protection unit by 1.5μH/m.
à Bunched copper wires with cross section area not less than 95 mm2 which are
joined by the Main Earthing Terminal (MET) or Floor Equipotential Earthing
Terminal Board (FEB) should be used as the grounding cables of the Class
B lightning protection unit, and the grounding cables of the Class C lightning
protection unit.
Keep the length of grounding cables as short as possible.
l For the lightning protection requirements of ZXMP S385 power input port and
input/output port of E1, Ethernet, alarm, and orderwire signals, refer to Table 3-4.
Table 3-4 Lightning Protection Requirements of ZXMP S385 Ports
Lightning Protection Port Specification
DC power input port 1 kV (1.2/50 µs)
Signal input/output port 1 kV (1.2/50 µs)
3.5 Lighting in the Equipment Room

Avoid direct sunlight. Average luminance should be 300 lx to 450 lx. The light source
cannot be dizzy. Use the fluorescent lamp installed in the ceiling.
Prepare accident lighting or standby lighting system in accordance with the specific
conditions of the equipment room. Install emergency light at proper positions.
3.6 Chutes and Apertures in the Equipment Room

All the drainage pipes should bypass the equipment room.
The quantity, location and size of reserved underground pipes, ground chutes and
apertures in the equipment room should meet the cable laying requirement and the craft
design requirements.
All the chutes should have damp-proof measures and well trimmed at the edges and
corners. Lay the lighting/power cables in a hidden manner.
3-3

3.7 Equipment Power Supply

The equipment uses the nominal -48 V power, with the allowed voltage fluctuation range
of -57 V to -40 V.
The routing, quantity and the layout of DC power cables installed in the equipment room
should meet the general specifications of telecommunications projects. The conductor
type (aluminum/copper bar or rubber-skinned wire), the equipment insulation strength and
the fuse capacities should meet the design requirements.
Use complete segment cable for the power cable. No joints in the middle of the power
cable.
3.8 AC Power Supply

Prepare 220 V/2000 W AC power socket outlet in the equipment room, because 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.
3.9 Air Conditioning System

To ensure long-term reliable operation of ZXMP S385, the temperature and humidity of
the equipment operating environment should meet particular requirements. If the local
weather conditions cannot satisfy the temperature and humidity requirements all the year,
install air-conditioning system in the equipment room.
Select the air condition in accordance with the equipment heat quantity. The formula below
is used for heat quantity calculation.
Q = 0.82×U×I (KW/hour), where
l Q is the equipment heat quantity
l U is the DC power supply voltage (V)
l I is the average current (A)
l 0.82: The coefficient to transfer 1 W electric energy to heat energy is 0.86; the
coefficient to transfer 1 W electric energy to heat energy in the equipment room is
0.95. And 0.82 is the product of these two coefficients.
Calculate the actual air condition capacity in accordance with the equipment room area and
the equipment heat quantity. Refer to related engineering design specification documents
for calculation method.
Install the air conditioning system before powering on/debugging the ZXMP S385
equipment. Ensure that the air conditioning system works properly.
3-4

Chapter 3 Environment Maintenance
3.10 Fire Protection Facilities

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

The front maintenance space of 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.
3-5

3-6

Chapter 4
Equipment Maintenance
Operations
Table of Contents
Checking the Audio Alarm ..........................................................................................4-1
Observing Cabinet Indicators .....................................................................................4-2
Observing Board Indicators ........................................................................................4-3
Checking the Fan .......................................................................................................4-4
Cleaning the Dustproof Unit........................................................................................4-4
Checking Groundings.................................................................................................4-5
Service Inspection - Bit Error Test...............................................................................4-6
Removing/Installing the Filler Door .............................................................................4-6
Installing Board ..........................................................................................................4-8
Plugging/Unplugging Fiber Pigtail.............................................................................4-20
Optical Power Test ...................................................................................................4-21
4.1 Checking the Audio Alarm

Operation Purpose
Audio alarms can attract the maintenance personnel's attention more easily. Ensure that
the equipment sound properly in routine maintenance.
Steps
Generate an alarm manually through setting Reverse Preload in the Alarm Standby list:
1. Right-click an NE. Select NE Manager. The NE Manager dialog box is displayed.
2. Unfold the NE Operation tree in the bottom left pane. Select Alarm Configuration >
Alarm Standby Configuration.
3. Select the corresponding board from the Select Card list.
4. Set Alarm Standby to be Reverse Preload in the Alarm Standby list.
4-1

5. Click Apply.
Note:
If the electric tributary board port is set to be Reverse Preload, a "signal loss" alarm will
be generated.
Inspection Criteria
When an alarm occurs, the ZXMP S385 and the column head cabinet should be able to
generate the alarm sound.
Troubleshooting
1. Verify that the ring interception switch is in the "Normal" state.
2. Check the cable connections of the ring trip switch.
3. If the alarm of the ZXMP S385 is connected externally to the column head cabinet,
check the external alarm cable connection.
4.2 Observing Cabinet Indicators

Operation Purpose
Cabinet indicators serve to monitor the operating status of the equipment, and play an
important role in routine maintenance. Regularly verify that the indicators on the column
head cabinet and other cabinets work normally to ensure that the indicators can properly
indicate the alarms and their levels.
Steps
Observe the status of the indicators on the top of the cabinet.
4-2

Chapter 4 Equipment Maintenance Operations
Inspection Criteria
When the equipment operates normally, only the green cabinet indicator on the cabinet is
on. For the meanings of the indicators, refer to Table 4-1.
Table 4-1 Meanings of the ZXMP S385 Cabinet Indicators
Indicator Name Status
ON OFF
Red light Critical alarm indicator A critical alarm is No critical alarm in the
generated in the equipment
equipment, normally
with an audio alarm.
Yellow light General alarm indicator A major or minor alarm No major or minor
is generated in the alarm in the equipment
equipment
Green light Power indicator Equipment power Equipment power

supply is normal supply fails.
Note:
When the red indicator or the yellow indicator of the cabinet is on, check the board
indicators and notify the EMS operators at the central site quickly to check the alarm and
performance of the equipment.
4.3 Observing Board Indicators

Operation Purpose
The status of the indicators on the top of the cabinet can only indicate the latent faults
of local equipment or the existing faults of the opposite-side equipment. Further check
the board indicator lights to keep aware of the operating status of the equipment after
observing the cabinet indicator lights.
Steps
Observe the status of the indicator lights of the board.
Inspection Criteria
Refer to the appendix Board Indicator Status for status of board indicators.
4-3

Troubleshooting
When the red/yellow indicator light of the board is on, notify the EMS operators at the
central site quickly to check the alarm/performance message of the equipment and board.
4.4 Checking the Fan

Operation Purpose
Good heat dissipation is critical for the long-term normal operation of the equipment.
Ensure that the fan is working normally when the equipment is operating. It is necessary
to check the operational status and cooling of the fan periodically.
Operation Steps
Observe the operational status of the fan.
Inspection Criteria
The fan runs stably at a regular rotation speed, and buzzes continuously without strange
sound.
Troubleshooting
1. If the fan rotates at an irregular speed or has strange sound, check immediately
whether foreign substance exists in the fan box, and whether the fan is damaged.
2. If the fan does not run, check immediately if the fan in the plug-in box is damaged.
3. Any one of the three fan boxes is faulty, immediately eliminate the faults or replace the
fan box.
4.5 Cleaning the Dustproof Unit

Operation Purpose
After the equipment runs for a long time, dust may block the dustproof unit at the cabinet
bottom, resulting in bad heat dissipation. The equipment may even be damaged. It is
necessary to clean the front panel and the filter mesh in the dustproof unit periodically.
Steps
1. Press the clips at both sides of the dustproof unit to remove the front panel, see Figure
4-1.
4-4

Figure 4-1 Removing the Dustproof Front Panel
1. Clip 2. Front panel
2. Use a brush to scrub dust on the front panel and the filter mesh.
3. Take out the dustproof card from the unit, see Figure 4-2.
Figure 4-2 Pulling out the Dustproof Card
1. Dustproof card
4. Clean the air filter mesh with water, and air dry it.
5. Insert the dustproof card into the dust unit.
6. Ensure sure that the clips are locked well. Mount the front panel.
Inspection Criteria
The front panel and the air filter mesh of the dustproof unit are free from dust.
Note:
When the front panel and the dust filer mesh are dusty, clean them in the above-mentioned
way.
4.6 Checking Groundings

Operation Purpose
Grounding fault would affect equipment operation, even damage equipment. It is required
to verify that equipment grounding facilities are normal, especially in spring and autumn.
4-5

Steps
1. Verify that the grounding system is normal.
2. Verify that the grounding resistance satisfies related standards.
Inspection Criteria
The grounding facilities should comply with related engineering specifications.
Troubleshooting
Correct grounding facilities as per engineering specifications.
4.7 Service Inspection - Bit Error Test

Operation Purpose
Bit error characteristic test is a test on the long-term stable operating performance of the
entire transmission network. During the routine maintenance, make periodical sampling
test on traffic channels, on condition that no current operating service is affected, so as to
verify that the performances of all the traffic channels are normal.
Steps
1. 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.
2. 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.
3. If both of the above two circumstances are not applicable, use the EMS software to
query the service performance and alarms, and ensure the quality of traffic channels
between the two sites.
Inspection Criteria
No bit error exists on any traffic channel.
4.8 Removing/Installing the Filler Door

4.8.1 Removing Filler Door
You may mount the door on the upper part of the subrack to make the subarck look neat.
Before laying the cables and mounting boards, remove the filler door.
4-6

Steps
1. Hold the front door and turn the locks on the right and left sides of the subrack to the
vertical position, where is labeled.

2. Make the upper part of the door incline outward.
3. Pull the pin on the right part of the door out of the hole on the subrack. Remove the
pin on the left side of the subrack from the groove on the left side of the door.
Figure 4-3 displays how to remove the door.
Figure 4-3 Removing the Door
1. Lock 3. Pin on the subrack 5. Pin on the door

2. Door 4. Groove 6. Hole on the subrack
– End of Steps –
4.8.2 Installing Filler Door

You may mount the filler door on the upper part of the subrack to make the subarck look
neat.
Prerequisite
l The boards have been inserted.
l The cables are laid.
Steps
1. Hold the filler door and insert the pin on right side of the door into the hole on the
subrack. At the same time, insert the pin on the left side of the subrack into the groove
on the left side of the door.
2. Push the door inward and upward till it fits well with the subarck.
4-7

3. Turn the locks on the right and left sides of the subrack to the horizontal position, where
is labeled.
Figure 4-4 displays how to mount the door.
Figure 4-4 Installing the Filler Door
1. Pin on the subrack 3. Pin on the door 5. Filler Door

2. Groove 4. Hole 6. Lock
4.9 Installing Board

4.9.1 Board Operation Precautions
l Because there are multiple CMOS components in a board, be sure to wear the
anti-static wrist strap when touching the board to connect the human body with the
system working ground.
Caution!
If the ground wire of the equipment to be installed has not been connected, the
antistatic wrist strap connected to the cabinet cannot apply and another effective
antistatic approach is necessary.
l Normally, some desiccants are placed in the antistatic protection bag for the board to
absorb moisture in the air inside it and keep it dry.
4-8

l If the board is moved from a place with low temperature and humidity to another place
with higher temperature and humidity, wait at least 30 minutes before unpacking, lest
the moisture will be accumulated on the board surface to damage the board.
l While plugging a board, maintain the board upright with proper force to avoid bending
the contact pins. While plugging an optical interface board, pay special attention not
to damage the optical interface and the fibers in the board.
l Avoid plugging/unplugging boards of ZXMP S385 while power is on.
l When the user install 2 M service boards on the subrack, it is recommended to insert
them into the middle slots first, and then the slots on both sides.
4.9.2 Board Slots in a Subrack

Diagram of Boards in a Subrack
Figure 4-5 displays the board slots of the ZXMP S385 subrack.
4-9

Figure 4-5 Diagram of Boards in a Subrack
Available Slots for Functional Boards

For the available slots for functional boards, refer to Table 4-2.
Table 4-2 Available Slots for Functional Boards of ZXMP S385
Board ID Available Slots Remark
CSA, CSE, CSF, CSC, CSG 8, 9 The slot 8 and slot 9 must be configured
with the same boards, such as CSA
board.
OW 17 –
4-10

ANCP, ENCP, NCP, ANCPB 18, 19 The slot 18 and slot 19 must be
configured with the same boards, such
as ANCP board.
QxI 66 –
SCI 67 –
OBA/OPA 1 to 7, 10 to 16 l OBA is the Optical Booster Amplifier

board.
l OPA is the Optical Pre-Amplifier
board.
l OBA12/OPA32 board occupies one
slot.
l OBA14/OBA17/OBA19/OPA38
board occupies one or two slots.
OADD 1 to 7, 10 to 16 –
OADC 1 to 7, 10 to 16 –
Available Slots for Service Boards

l For the available slots for optical/electrical line boards and service boards, refer to
Table 4-3.
Table 4-3 Available Slots for Optical/Electrical Line Boards and Service Boards
of ZXMP S385
OL64 1 to 7, 10 to 16 –
OL64x2, OL16x8 6, 7, 10, 11 –
OL4x4, OL4x2, OL16, 1 to 7, 10 to 16 –

OL16x4, OL16x8, OL1x8,
OL1x4
OL64FEC (OL64FEC) 1 to 7, 10 to 16 The ASON function is not supported.
OL64FEC (OL64FECA) 1 to 5, 12 to 16 The ASON function is supported.
OL64FECx2 6, 7, 10, 11 The ASON function is supported.
OEL1x16 1 to 7, 10 to 16 When configured in slot 1, 6, 7, 10, 11, and 16,

the board only supports eight pairs of service
processing, because it does not support
configuring interface boards.
OEIS1x8 62 to 65, 68 to 71 Cooperates with OEL1x16 board.
4-11

LP1x8 1 to 5, 12 to 16 à LP1x8 board in slot 1 and slot 16 can only

serve as a protection board, and cannot be
configured with services.
à Supports two groups of 1:N(N≤4) protec-

tion.
à The board does not support ECC, over-

head cross connect, OW, OMS link protec-
tion in 1:N protection.
ESS1x8 62 to 65, 68 to 71 Should be inserted in the slot of the upper-layer

interface board (interface switching board) that
corresponds to the service board.
BIE3 61, 72 à Only serves for 1:N (N≤4) protection.
à Should be inserted in the slot of the up-

per-layer interface board (interface bridge
board) that corresponds to the protection
board.
Note:
OL64FEC (OL64FEC)/OL64FEC (OL64FECA): The code outside the bracket refers to

the panel identification, and the code inside the bracket refers to the PCB identification.
The relations between service slots and slots for upper-layer interface boards,
interface switching boards, and interface bridge boards are: slots 1 to 5 correspond
to slots 61 to 65 sequentially, slots 12 to 16 correspond to slots 68 to 72 sequentially.
For example, if a service board LP1x8 is inserted in slot 2, its corresponding interface
switching board ESS1x8 should be inserted in slot 62.
If a service board EPE1x63 (75) is inserted in slot 12 and there is no protection, its
corresponding electrical interface board EIE1x63 should be inserted in slot 68.
l For the available slots for E3/T3 service boards, refer to Table 4-4.
4-12

Table 4-4 Available Slots for E3/T3 Service Boards of ZXMP S385
Board ID Available Remark

Slots
EP3x6 1 to 5, 12 to 16 à Serving as E3/T3 processor, it can be inserted in slots 2 to

5 and slots 12 to 15.
à Serving as protection board and inserted in slot 1, it can

implement one group of 1:N (N≤4) protection for boards in
slots 2 to 5.
à Serving as protection board and inserted in slot 16, it can

implement one group of 1:N (N≤4) protection for boards in
slots 12 to 15.
BIE3 61, 72 à Only serves for the 1:N (N≤4) protection.
à If the BIE3 board is inserted in slot 61, it operates with the

protection board in slot 1. If the BIE3 board is inserted in slot
72, it works with the protection board in slot 16.
ESE3x6 62 to 65, 68 to Should be inserted in the slot of the upper-layer interface board
71 (interface switching board) that corresponds to the service
board.
l For the available slots for E1/T1 service boards, refer to Table 4-5.
Table 4-5 Available Slots for E1/T1 Service Boards of ZXMP S385
EPE1x63 (75), EPE1x63 1 to 5, 12 to 16 à Any E1/T1 electrical processor in slots 1

(120), EPE1Fx63, EPT1x63, to 5 and slots 12 to 16 can serve as the
EPE1Zx63 (75), EPE1Zx63 protection board.
(120)
à Can implement one group of 1:N (N≤9)
protection.
EIE1x63, EIT1x63, BIE1 61 to 65, 68 to à BIE1 board only serves for the 1:N (N≤9)
72 protection of E1 electrical service.
à Should be inserted in the slot of the

upper-layer interface board (interface
bridge board) that corresponds to the
protection board.
ESE1x63, EST1x63 62 to 65, 68 to à Serves for services with E1 electrical

71 protection.
à Should be inserted in the slot of the

upper-layer interface board or interface
switching board that corresponds to the
working board.
4-13

OPE1Z 1 to 7, 10 to 16 –
l For the available slots for Ethernet service boards, refer to Table 4-6.
Table 4-6 Available Slots for Ethernet Service Boards of ZXMP S385

Slots
TGE2B, TGSAx8 1 to 7, 10 to -
16
MSE, SECx24, 1 to 5, 12 to à SECx48, SECx24, MSE board in slot 1 and slot 16

SECx48 16 can only serve as a protection board, and cannot be
configured with services.
à Supports two groups of 1:N(N≤4) protection.
à Do not configure GE service on the protected

SECx48, SECx24 or MSE board, when configuring
1:N protection to avoid GE service interruption
during FE service switching.
RSEB 2 to 5, 12 to -
15
OIS1x8 62 to 65, 68 Should be inserted in the slot of the upper-layer

to 71 interface board (interface switching board) that
corresponds to the SECx48, SECx24, MSE, and RSEB
board.
ESFEx8 62 to 65, 68 Should be inserted in the slot of the upper-layer

corresponds to the SECx48, SECx24, MSE, RSEB,
SEE/SEEU, and SEG4 board.
BIE3 61, 72 à Only serves for the 1:N (N≤4) protection of FE ser-
vice
à Should be inserted in the slot of the upper-layer

interface board (interface bridge board) that corre-
sponds to the protection board
4-14


Slots
SEE/SEEU 1 to 7, 10 to à The SEE/SEEU board supports optical/electrical in-

16 terface board OEIFEx8, electrical interface board
ESFEx8 or no interface board.
à When OEIFEx8 board is configured, FE interface

supports the coexistence of SFP optical module
and optical/electrical interface, but SEE/SEEU
board does not support 1:N protection.
à When an FE optical interface (1320 or 1321 soft-

ware/hardware version is selected on the EMS) is
needed, the SEE/SEEU board can only be inserted
in slots 1 to 5 and slots 11 to 15, and the cooperat-
ing optical interface board OEIFEx8 can be inserted
in slots 62 to 65 and slots 68 to 71.
à When an FE optical interface (2320 or 2321 soft-

ware/hardware version is selected on the EMS) is
needed, if the board 1:N protection is required, the
SEE/SEEU board can only be inserted in slots 2 to
5 and slots 12 to 15, and the cooperating electrical
interface switching board ESFEx8 can only be in-
serted in slots 62 to 65 and slots 68 to 71.
If the board 1:N protection is required, the
SEE/SEEU board should also be inserted in slot
1 or 16 (2320 or 2321 software/hardware version
is selected on the EMS), and the bridge board
BIE3 should be inserted in slot 61 or 72 in the
corresponding interface area.
à The SEE/SEEU board only supports 1:N protec-
tion for eight FE electrical interfaces on the service
board, and it does not support 1:N protection for the
service at GE optical interface, FE optical interface,
and FE optical/electrical interface coexistence.
Slots 1 to 5 and slots 12 to 16 can provide two
independent groups of 1:4 tributary protection
as required: the SEE/SEEU board in slot 1 can
protect the service at FE electrical interface on
any SEE/SEEU board in slots 2 to 5, and the
SEE/SEEU board in slot 16 can protect the service
at FE electrical interface on any SEE/SEEU board
in slots 12 to 15.
4-15


Slots
SE10G2 1 to 7, 10 to Only three SE10G2 boards can be inserted into each

16 subrack at most, and the SE10G2 boards cannot be
inserted into connected slots.
SEG4 1 to 7, 10 to à Processes four channels of GE and eight channels

16 of FE services.
à If an FE optical interface is supported, an OEIFEx8

board is used. If an FE electrical interface is sup-
ported, an ESFEx8 board is used.
OEIFEx8 62 to 65, 68 The board is inserted in the slot of the upper-layer

corresponds to the SEE/SEEU or SEG4 board.
Table 4-7 Description of SEE/SEEU/SEG4 Board Software/Hardware Configuration
Interface Board Software/hardware Version Remark
No interface board is à SEE/SEEU: 1310 or 1311 When the software/hardware

configured. version is 1310, 1320, and
à SEG4: 1311
2320, the SEE/SEEU board
OEIFEx8 à SEE/SEEU: 1320 or 1321 does not provide port-level
à SEG4: 1321 Ethernet Protection Switch.
When the software/hardware
ESFEx8 à SEE/SEEU: 2320 or 2321
version is 1311, 1321, 2321,
à SEG4: 2321 the SEE/SEEU board supports
EPS.
l The available slots in master and expansion subracks for ATM service board AP1x8
are: 1 to 7 and 10 to 16.
4.9.3 Plugging a Lower-Level Board

Introduce how to plug a Lower-Level Board.
Steps
1. Take out the board from the antistatic bag and verify that there is no mechanical
damage. Since there are multiple CMOS components on the board, proper and
reliable antistatic measure such as wearing antistatic wrist is necessary before
touching the board.
2. In accordance with the slot layout and available slots for boards specified in the design
document, insert the board into the corresponding slot of the equipment subrack.
4-16

3. To plug a board, place the ejector lever at horizontal position by pressing the spring
plate of ejector lever. Grasp the upper and lower ejector levers, and push in the board
exactly along the guide rail. The board must be kept vertical throughout the process,
and apply appropriate force. Figure 4-6 shows how to plug a lower-level board.
Figure 4-6 Plugging a Lower-Level Board
4. When the board is about to get into position, clamp the bayonet of ejector lever with
front beam of the subrack, push the ejector lever up/down wards with both hands
exerting proper force unless the ejector lever stands upright and produces the locking
sound of "clatter". The board connector should be fully inserted into the motherboard
socket. In this case, the board panel should be parallel with the outer frame of the
board area in the cabinet. Now, the board insertion is complete.
Caution!
Do not insert the board forcibly, and avoid bending the motherboard pins. Insert the
board along the slot, do not touch the adjacent boards to avoid short-circuit.
4.9.4 Unplugging a Lower-Level Board

Introduce how to unplug a Lower-Level Board.
Steps
1. Hold the upper and lower ejector levers, and press down the lever spring plates, move
the levers up/down wards with appropriate force to free the board from the slot. Figure
4-7 shows how to unplug a lower-level board.
4-17

Figure 4-7 Unplugging a Lower-Level Board
2. Pinch the board ejector lever with thumb and forefinger of one hand, at the same time
hold the board panel with the other hand, and smoothly pull the board out of the slot.
4.9.5 Plugging an Upper-Level Board

Introduce how to plug an Upper-Level Board
Prerequisite
The filer door is removed.
Steps
1. Take out the board from the antistatic bag and verify that there is no mechanical
damage. Since there are multiple CMOS components on the board, proper and
reliable antistatic measure such as wearing antistatic wrist is necessary before
touching the board.
2. In accordance with the slot layout and available slots for boards specified in the design
document, insert the board into the corresponding slot of the equipment subrack.
3. To plug a board, place the ejector lever at horizontal position by pressing the spring
plate of ejector lever. Grasp the upper and lower ejector levers, and push in the board
exactly along the guide rail. The board must be kept vertical throughout the process,
and apply appropriate force. Figure 4-8 shows how to plug an upper-level board.
4-18

Figure 4-8 Plugging an Upper-Level Board
4. When the board is about to get into position, clamp the bayonet of ejector lever with
front beam of the subrack, push the ejector lever up/down wards with both hands
exerting proper force unless the ejector lever stands upright and produces the locking
sound of "clatter". The board connector should be fully inserted into the motherboard
socket.
5. Clockwise screw the captive fasteners. In this case, the board panel should be parallel
with the outer frame of the board area in the cabinet. Now, the board insertion is
complete.
Caution!
Do not insert the board forcibly, and avoid bending the motherboard pins. Insert the
board along the slot, do not touch the adjacent boards to avoid short-circuit.
4.9.6 Unplugging an Upper-Level Board

Introduce how to unplug an Upper-Level Board.
Prerequisite
The filer door is removed.
Steps
1. Anti-clockwise the captive fasteners.
4-19

2. Hold the upper and lower ejector levers, and press down the lever spring plates, move
the levers up/down wards with appropriate force to free the board from the slot. Figure
4-9 shows how to unplug aboard.
Figure 4-9 Unplugging an Upper-Level Board
3. Pinch the board ejector lever with thumb and forefinger of one hand, at the same time
hold the board panel with the other hand, and smoothly pull the board out of the slot.
4.10 Plugging/Unplugging Fiber Pigtail

4.10.1 Plugging Fiber Pigtail (LC/PC)
Introduce how to plug Fiber Pigtail (LC/PC).
Steps
1. Before plugging the pigtail, clean the pigtail connector using dust-free paper with
absolute alcohol. Be careful to wipe it in one direction.
2. When plugging the pigtail, nip the pigtail connector with your thumb and index finger,
make the locating piece of the connector rightward, make the connector and the optical
line board (or optical interface board) become the angle of 45°, align the connector with
the optical interface of the optical line board or the optical interface board.
3. Insert the pigtail with proper force to the optical interface, see Figure 4-10.
4-20

Figure 4-10 Plugging Fiber Pigtail
4.10.2 Unplugging Fiber Pigtail (LC/PC)

Introduce how to unplug Fiber Pigtail (LC/PC).
Steps
1. Hold the pigtail connector with your thumb and index finger, and press down the spring
piece on the connector.
2. Pull out the connector with moderate force.
3. Cover the connector with a dustproof cap as soon as it is unplugged, to avoid dust
pollution.
4.11 Optical Power Test

4.11.1 Cautions of Optical Power Test
1. Ensure that fiber pigtail connectors are clean (if not, clean them with special cleaning
solution and paper); Ensure that the connecting devices of the ring flanges on the
optical board panel and the optical power meter are well coupled.
4-21

2. Measure the attenuation of the fiber pigtail before the test, to ensure that this fiber
pigtail has good transmission performance. For optical boards using single-mode and
multi-mode optical interfaces, use different fiber pigtails for test accordingly.
3. If necessary, the attenuation values of the optical connector and the testing fiber can
be considered known, serving to amend the mean optical launched power read from
the optical power meter. For higher test accuracy, take the average value of multiple
test results, and then amend it with the attenuation values of the optical connector and
the testing fiber.
4.11.2 Optical Launched Power Test

Introduce how to execute optical launched power test.
Steps
1. Connect one end of the fiber pigtail to the optical transmit interface of the tested optical
board, and the other end to the test input interface of the optical power meter, see
Figure 4-11.
Figure 4-11 Optical Launched Power Test
Caution!
The optical launched power of the optical board may exceed the maximum input optical
power of the optical power meter. To avoid damage to the optical power meter, add
optical attenuation between the optical transmit interface of the optical board and the
test input interface of the optical power meter.
2. Set the optical receive wavelength of the optical power meter to be the same as the
optical transmit wavelength of the tested optical line board.
3. Read the stable optical power value (dBm) of the optical power meter. If no optical
attenuator is added, this value is the optical launched power of this optical line board.
4-22

If an optical attenuator is added, this value plus the optical attenuation value is the
optical launched power of this optical line board.
4.11.3 Optical Received Power Test

Introduce how to execute optical received power test.
Steps
1. Set the receiving optical wavelength of the optical power meter to the same as the
tested optical wavelength.
2. Select at the local site the fiber pigtail that connects to the transmitting optical interface
of the adjacent site. Normally, this fiber pigtail is connected to the receiving optical
interface of the optical line board at the local site. Connect the fiber pigtail to the test
input interface of the optical power meter. Read the stable optical power value of the
optical power meter, meaning, the optical received power of this optical line board.
4-23

4-24

Chapter 5
EMS Maintenance Operations
Table of Contents
Managing Users .........................................................................................................5-1
Monitoring Topology Map Status and NE Status .........................................................5-2
Checking the Board Operating Status.........................................................................5-4
Monitoring Alarms ......................................................................................................5-5
Monitoring Performances ...........................................................................................5-6
Monitoring Events ......................................................................................................5-7
Synchronizing Data ....................................................................................................5-7
Querying EMS Logs ...................................................................................................5-8
Printing Reports .......................................................................................................5-10
Back Up Data ...........................................................................................................5-11
Restoring the Basic Data..........................................................................................5-12
Restoring Log, Alarm or Performance Data ..............................................................5-14
Managing the NE Time.............................................................................................5-15
5.1 Managing Users

Operation Purpose
In order to prevent illegal access to the EMS and ensure normal operation of equipment
and service security, change the login password of the EMS users on schedule, and assign
proper authorities to the EMS operators.
Steps
1. Create a user to control user management authority.
In the NetNumen U31 R22 EMS client, select Security > User Management.
Right-click the user tree on the right pane, select Create User from the shortcut menu.
Assign unique username, user ID and password for each EMS operator, and assign
different user levels according to the specific operation authorities of each user
(read-only, read and write, or without management).
2. Change the login password of the EMS operators periodically.
5-1

Note:
Because system administrators possess all the operation authorities, any improper
operation made by them may cause severe consequences. In routine maintenance, you
must not log into the EMS as a system administrator. Instead, you may log into the EMS
as a system monitor for routine maintenance.
Inspection Criteria
1. The EMS operators can log into the EMS with an assigned username, and have the
assigned operation authorities.
2. The EMS operators can change the login password periodically.
Troubleshooting
1. If the EMS operators have wrong operation authorities or cannot change the password,
they must request the system administrator to check the user configuration data or
reset the user authorities and password.
2. If EMS connection is faulty, check the lists as follows:
l Verify that network cables are normal, and Verify that the cable type (straight cable
or crossover cable) is correct.
l Verify that the network adapter of EMS computer is normal.
l Check the optical connection of the network. Make sure that optical connection
between NEs is normal without any circuit problems.
l Verify that EMS configuration data is normal.
l Verify that NE configuration data is normal.
5.2 Monitoring Topology Map Status and NE Status

Operation Purpose
The NetNumen U31 R22 EMS can provide audible and visual alarms. The user can
monitor the operation status of the current subnets and NEs through navigation tree,
topology map, NEs, and board management dialog box. The user can also determine the
alarm level through the sound or color given with the alarm.
Steps
After the user logs in to the NetNumen U31 R22 EMS client, the Topology Management
window is displayed. Check the status of all NEs and links.
After the user log in to the NetNumen U31 R22 EMS client, the Topology Management
window is displayed automatically. Otherwise, open the Topology Management window
in one of the following ways:
5-2

Chapter 5 EMS Maintenance Operations
l In the menu bar, select Topology > View Topology.

l Click in the menu bar.
l Select Topology Management from the drop-down list in the upper-right pane of the
window.
Figure 5-1 Topology Management
Inspection Criteria
l The NE icon must be green indicating that the NE is online.
l There is no alarm icon on NE icons.
l Links are normal. The connection lines between NEs are full lines.
Troubleshooting
l The NE is off-line.
à If there is an off-line sign in the upper-left corner of the NE icon, EMS has
issued an off-line command on the NE. Set it to be on-line.
à If there is a link-broken sign in the upper-left corner of the NE icon, the EMS
and NE communicate improperly.
If the EMS is faulty, check the following items.
1. Verify that network cables are normal, and Verify that the cable type (straight
cable or crossover cable) is correct.
2. Verify that the network card of the computer where EMS works properly.
3. Check the optical fiber connection to ensure that the optical fiber connection
between two NEs is normal.
4. Verify that EMS configuration data is normal.
5. Verify that NE configuration data is normal.
l If there are alarm signs on NE icons, query the detailed alarm messages and handle
the alarms through the Current Alarm dialog box or the Fault Management window.
à If the NE icon is in red , the highest level of current alarms of the NE is
critical.
à If the NE icon is in orange , the highest level of current alarms of the NE is
major.
à If the NE icon is in yellow , the highest level of current alarms of the NE is
minor.
5-3

à If the NE icon is in blue , the highest level of current alarms of the NE is

warning.
l If the line indicative of the optical connection is a dotted line, check the corresponding
optical cables and fiber pigtails.
5.3 Checking the Board Operating Status

Operation Purpose
In daily maintenance, you must check the operating status of boards periodically to
discover and handle faults quickly.
Steps
1. Perform one of the following operations. The Rack Chart window is displayed.
l In the topology, double-click the NE to be checked.
l In NE Tree or topology, right-click the NE to be checked. Select Open Rack Chart
from the shortcut menu.
2. Click in the upper-left pane of the Rack Chart window. The Board Selection tab
and Legend tab are unfolded.
3. Query the board operating status in accordance with Legend.
Inspection Criteria
The board is in white and has no status sign.
Troubleshooting
l The board is in one of the alarm colors, indicating that there is an alarm on the board.
Query detailed alarm information and handle the alarm through the Current Alarm
dialog box or Fault Management window.
à If the board is in red , the highest level of current alarms of the board is
critical.
à If the board is in orange , the highest level of current alarms of the board
is major.
à If the board is in yellow , the highest level of current alarms of the board is
minor.
à If the board is in blue , the highest level of current alarms of the board is
warning.
l The icon indicates that the board status is unknown. Check the communication
between the NE and the EMS to ensure that the NE is online and the communication
is normal.
l The icon indicates that the board status is out of position. Verify that the board is
installed correctly and whether it is in good contact with the backplane.
5-4

l The icon indicates that loopback is set on the board. Verify that the loopback must
be removed as required.
l The icon indicates that the board is the master board, but it is not in operational
status. Check the board and handle the fault.
5.4 Monitoring Alarms

Operation Purpose
In the NetNumen U31 R22 EMS, the user can monitor alarms; thus keep aware of the
current operational status, and detect/handle the alarm messages quickly.
Steps
l Querying the current alarms, historical alarms and lock alarms of all NEs.
1. In the menu bar of the EMS client, select Fault > Active Alarm Monitoring. The
Fault Management window is displayed.
2. In the Management tree in the left pane, double-click Alarm Query > Active
Alarms > All Active Alarms to query the alarms of all NEs.
3. In the Management tree in the left pane, double-click Alarm Query > History
Alarms > History Alarm Within One Day, Alarm Query > History Alarms >
History Alarm Within Three Days, or Alarm Query > History Alarms > Lock
Alarm Search to query the historical alarms or lock alarms of all NEs.
l Querying the current alarms, historical alarms and lock alarms of an NE.
5-5

In NE Tree in the Fault Management window, right-click the NE. Select Active
Alarms, Unacknowledged Active Alarms, Active Alarms Within One Hour,
Active Alarms Within One Day, Locked Alarm Search, History Alarm Within
One Day, History Alarm Within Three Days, or All the History Alarms from the
shortcut menu.
Inspection Criteria
l The NE has no current alarm message.
l The NE has no unconfirmed historical alarm message.
5.5 Monitoring Performances

Operation Purpose
In the NetNumen U31 R22 EMS, the user can monitor the performance messages; thus
keep aware of the current service performance, and detect/handle the faults quickly.
Note:
Before monitoring performances, create a performance measurement task to collect the

performance data of NEs.
5-6

Steps
1. You can open the Performance Data Query dialog box in one of the following ways:
l In the menu bar of the EMS client, select Performance > Performance Data
Query.
l Click the icon.
l Right-click NE Tree or any NE in the topology. Select Performance Management
> Performance Data Query from the shortcut menu.
l In the menu bar of the EMS client, select Statistics > Performance Statistics >
Performance Data Query.
2. In the Performance Data Query dialog box, set the Indices Selection, Object
Selection , and Time Selection.
3. Click OK.
Inspection Criteria
The EMS client window displays the queried performance data.
The NE has no performance over-threshold event.
5.6 Monitoring Events

Operation Purpose
The EMS supports to monitor the current switches and history switches. In the NetNumen
U31 R22 EMS, the user can monitor the switch events; thus keep aware of the OMS
switches, subnet protection, board switches, and detect/handle the faults quickly.
Steps
1. In the menu bar of the EMS client, select Fault > Active Alarm Monitoring. The Fault
Management window is displayed.
2. In the Management tree in the left pane, double-click Alarm Query > Active Alarms
> Current Switch Event to query the current switches.
3. In the Management tree in the left pane of the window, double-click Alarm Query >
History Alarms > >History Switch Event to query the history switch events.
5.7 Synchronizing Data

Operation Purpose
In the NetNumen U31 R22 EMS, you can upload and compare the data, and verify that
the data stored in NE database is consistent with the data in EMS database. If not, the
user can perform the database management to ensure that they are consistent.
5-7

Steps
1. Right-click an NE in the NE Tree or topology in the Topology Management window.
2. Click Data Synchronization from the shortcut menu. The Data Synchronization
dialogue box is displayed.
3. Select the Compare tab.
4. Select data items to be uploaded in the Compare Data Item area box.
5. Click Compare.
Inspection Criteria
If the NE database is consistent with the data in EMS database, the Result area box
indicates that the comparison is successful.
Troubleshooting
The NE database is not consistent with the data in EMS database.
l If the current NE database is in compliance with the user requirements, take the data
in NE database as the basis.
In the Data Synchronization dialog box, select the Upload tab. Select the data items
to be uploaded. Click Upload.
l If the data of EMS is in compliance with the user requirements, take the data of EMS
as the basis.
In the Data Synchronization dialog box, select the Download tab. Select the data
items to be downloaded. Click Download.
Caution!
It is risky to upload or download data, be cautious.
5.8 Querying EMS Logs

Operation Purpose
There are three types of EMS logs: security logs, operation logs and system logs.
l Security logs record the information on the user login, including user name, host
address, log name, operation time, access mode, and log details.
l Operation logs record the information on the user operation, including user name,
level, operation, performed functions, operation time, operation object, operation
result, host address, and access mode.
l System logs record the operation of database, manager or NEs, including source,
level, log name, host address, operation time, and related logs.
The purpose for querying logs periodically includes:
5-8

l Checking whether illegal users log in.

l Checking whether user operations affect system operation or service functions.
l Monitoring the operation of EMS system.
Steps
1. On the menu bar of the EMS client window, select Security > Log Management.
2. Select the corresponding operations from the Log Management tree as required.
If Then
Querying the operation logs Select Operation Log > Operation Log Today or Operation
Log > >All Operation Log.
Querying the security logs Select Security Log > Security Log Today or Security Log >
>All Security Log.
Querying the system logs Select System Log > System Log Today or System Log >
All System Log.
Inspection Criteria
l No illegal login.
l No user operations affecting system operation or service functions.
l No high-level errors in the system logs.
Troubleshooting
l 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 quickly.
l When a high-level error appears in the system log, process the error in accordance
with the "Details" of EMS record.
5-9

5.9 Printing Reports

Operation Purpose
The EMS supports the printing function. The user can print out the network configurations,
user operation logs, equipment performances, and alarm messages. The printed reports
are a basis for operation, maintenance records, and network analysis.
Steps
1. On the menu bar of the EMS client window, select Statistics > BN > xTN
Configuration Report > NE Configuration Report.
Note:
You can select the NE configuration, connection information, board configuration, and
board statistics report as required. Becuase all reports are printed in the same way,
the section takes the method for printing NE configuration report as an example.
2. Select an NE in the Device Report tree.

3. Click Refresh. The configuration report of selected NEs is displayed.
4. Click Print to print the displayed report.
Inspection Criteria
Reports are printed properly.
5-10

5.10 Back Up Data

Operation Purpose
In the NetNumen U31 R22 EMS, database backup serves to copy and save the data of
the Manager database.
In network operation & maintenance, it is necessary to back up the system data on
schedule so that the data is quickly recoverable in case of network fault and EMS data
loss.
Steps
1. On the menu bar of the EMS client window, select Maintenance > System Backup
and Restore. The System Backup and Restore dialog box is displayed.
Note:
You can back up the entire database, basic data, or files. This section takes the file
backup as an example.
2. In the Backup and Restore tree, click Backup > Backup File. The Config
Parameters of Backup dialog box is displayed.
3. Select Backup File Download Path at Client. Enter the directory for saving the
backup file on the client.
4. Click Execute to start the backup.
5-11

Caution!
Do not save the backup data in the hard disk of the EMS host. Save the backup data in a
mobile storage device instead. Failure to comply can result in data loss if a fault occurs to
the hard disk.
Inspection Criteria
When the backup is completed, the Executed Result area box indicates that the client
has downloaded the backup file successfully. The backup files are saved in the specified
directory.
Note:
If the file does not exist, backup again.
5.11 Restoring the Basic Data

Operation Purpose
The EMS supports the recovery of the basic data and NE topology. For details of the
recoverable basic data, refer to Table 5-1.
Table 5-1 Basic Data Description
Database Description
Transport Network Configuration Database -
Configuration Database of Transport -

Network NEs
End to end database -
Common platform database Includes the basic data on the common application
platform database, such as resource data, safety data,
and topology data.
Common alarm database Includes the basic data on the common application
alarm database, such as alarm codes, alarm rules,
setting suggestions on alarm processing, setting
level redefinition, querying customized alarms, and
customized alarm statistics.
5-12

Database Description
Common performance database Includes the basic data on the common application
performance database, such as measurement tasks,
threshold tasks, querying templates, template tasks,
and definitions of performances models.
During network maintenance, restore the EMS data by using the backup data in case of
network fault or data loss.
Steps
1. 1 On the menu bar of the EMS client window, select Maintenance > System Backup
2. In the Backup and Restore tree, select Restore > Restore Basic Data. The Restore
Basic Data dialog box is displayed.
3. Click Start. The Basic Data Restoration dialog box is displayed.
4. Select the backup files in the Basic Data Restoration dialog box.
Note:
You can select the backup files stored on the computer where the EMS client runs or
on an FTP server.
5. (Optional) Select the Back up the current data before the restoration? If you
choose to back up the current data first, the system will automatically... check
box as required.
6. Click Execute.
Note:
When the basic data is being recovered, the EMS server stops operating and the EMS
client does not operate.
Inspection Criteria
The basic data is recovered.
After the basic data is recovered, NMS server automatically restarts. A dialog box is
displayed. Click OK. The system will close the EMS client window and a Login dialog
box is displayed automatically.
5-13

Note:
If the basic data cannot be recovered because the version of backup data is earlier than
the current EMS version, upgrade the EMS version.
5.12 Restoring Log, Alarm or Performance Data

Operation Purpose
The EMS supports the recovery of log data, alarm data and performance data. The data
to be recovered will replace the current data.
During network maintenance, you can restore the EMS data by using the backup data in
case of network fault or data loss
Steps
1. On the menu bar of the EMS client window, select Maintenance > System Backup
Note:
You can restore the log data, alarm data and performance data in the same way. This
section takes the log data recovery as an example.
2. In the Backup and Restore tree, select Restore > >Restore Log Data. The Config
Parameters of Restore dialog box is displayed.
3. Click Choose. Select the directory for saving the data to be recovered.
4. Select Execute.
Inspection Criteria
The current data of network is recovered.
Note:
If the data cannot be recovered because the version of backup data is earlier than the
current EMS version, upgrade the EMS version.
5-14

5.13 Managing the NE Time

Operation Purpose
l You can set the synchronization time of NEs, or query the current times of NEs and
the EMS by managing the NE time.
l Only when NEs and the EMS are synchronized, the EMS can record the correct alarm
generation times and log times.
l If a Network Time Protocol (NTP) server is configured in the network, NEs can be
synchronized with the NTP server.
l To query the NE time and verify the EMS time, verify that the connection between NEs
and the EMS operates properly.
Steps
You can open the NE Time Management window in one of the following ways:
l In the Topology Management window, right-click an NE. Select NE Time
Management from the shortcut menu.
l Right-click an NE from the NE Tree in the left pane of Topology Management window.
Select NE Time Management from the shortcut menu.
l Open the NE Manager dialog box.
1. Right-click an NE in the NE Tree or the topology in the Topology Management
window. Select NE Manager from the shortcut menu, the NE Manager dialog box is
displayed.
2. Unfold the NE Operation tree in the bottom left pane of the dialog box, select Clock
Time Configuration > NE Time Management.
Inspection Criteria
The NE time and EMS are synchronized.
Note:
If the times of NE and EMS are not synchronized, click Verify Time to synchronize NEs
and EMS.
5-15

5-16

Appendix A
Maintenance Forms
Table of Contents
Ÿ Half-day Maintenance Record ................................................................................ A-1
Ÿ Daily Maintenance Record...................................................................................... A-3
Ÿ Weekly Maintenance Record .................................................................................. A-5
Ÿ Login Password Change Record ............................................................................ A-6
A.1 Half-day Maintenance Record

Table A-1 Half-day Maintenance Form
Maintenance Item Result for Reference Check Result
Board NCP/ENCP/A- When normal, the green indicator NOM If no alarm is generated,
indicators NCP/ANCPB flashes (once per second). record "normal".
observation board If any alarm is generated,
When the yellow indicator ALM1 is lit, the
record the detailed alarm
NE/board generates an major or minor alarm.
indicator status.
When the red indicator ALM2 is lit, critical
If a service board generates
(severe) NE/board alarms are generated.
an alarm, the slot number
of the alarm board must be
recorded.
CS board When normal, the green indicator NOM

flashes (once per second).
When the red indicator ALM2 is lit, the board

generates an alarm.
OW board When normal, the green indicator NOM

When the yellow indicator ALM1 is lit, a call

is made.

generates an alarm.
OL64x2/OL64/O- When normal, the green indicator NOM

L64FEC/OL64F- flashes (once per second).
ECx2 board
generates an alarm.
A-1

OL16/OL16x4/O- When normal, the green indicator NOM

L16x8 baord flashes (once per second).

generates an alarm.
OL4x2/OL4x4 When normal, the green indicator NOM

board flashes (once per second).

generates an alarm.
OL1x4/OL1x8/O- When normal, the green indicator NOM

EL1x16 board flashes (once per second).

generates an alarm.
LP1x8 board When normal, the green indicator NOM


board is switching.

generates an alarm.
EPE1/EPE1F/E- When normal, the green indicator NOM

PE1Z/EPT1EP3 flashes (once per second).
board/
board is switching.

generates an alarm.
OPE1Z board When normal, the green indicator NOM


generates an alarm.
TGE2B/TGSAx8/ When normal, the green indicator NOM

RSEB board flashes (once per second).

generates an alarm.
SEC/SEE/SEEU- When normal, the green indicator NOM

/SEG4/SE10G2 flashes (once per second).
board When the yellow indicator ALM1 is lit, the
board is switching.
A-2

Appendix A Maintenance Forms

generates an alarm.
Summary of the indicator status: (Sum up the indicator status in this period and record the troubleshooting details.)
Tested by: Check time:
A.2 Daily Maintenance Record

Table A-2 Daily Maintenance Record
Maintenance Item Maintenance Content Result for Reference Check

Result
Equip- Audio Buzzer sound When no alarm is generated, the buzzer

ment alarm does not sound.
mainte-
When the equipment generates an alarm,
nance
the buzzer sounds.
Cabinet Status of cabinet indicators When power is supplied to the equipment

indicator normally, the green indicator is lit.
When the equipment generates a minor or

a warning alarm, the yellow indicator is lit.
When the equipment generates a major

alarm, the orange indicator is lit.
When the equipment generates a critical

alarm, the red indicator is lit.
EMS Navigation Server communication When the communication is normal, the

mainte- tree NE icon bears no "×".
NE communication
nance monitoring
NE operational status When an NE operates properly, the NE
icon bears no "×".
When a warning alarm is generated, the

icon is purple.
When a minor alarm is generated, the

icon is yellow.
When a major alarm is generated, the

icon is orange.
When a critical (severe) alarm is

generated, the icon is red.
A-3

Maintenance Item Maintenance Content Result for Reference Check

Result
Topology NE communication When the communication is normal, the

map icon is green.
monitoring
NE operational status When a warning alarm is generated, the
icon is purple.

icon is yellow.

icon is orange.

generated, the icon is red.
Optical connection status When the connection is normal, the line

is a green real line.
When any optical fiber is faulty, the

connection is a red dashed line.
Alarm Alarm setting Alarm audio is not shielded.

monitoring
Alarm is not shielded or reversed.
Querying alarm status through When a warning alarm is generated, the

the board status bar on EMS purple button flashes.

yellow button flashes.

orange button flashes.

generated, the red button flashes.
Perfor- Querying the current 15 min/24 When performances are normal, the
mance hour performance performance value is 0.
monitoring
Querying the history 15 min/24
hour performance
Summary of maintenance: (Sum up the equipment and EMS status in this period and record whether the faults
have been cleared. If the faults have been solved, the troubleshooting methods should also be recorded to provide
reference for future maintenance work.)
Tested by: Check time:
• Alarm colors vary with EMS types. This table takes NetNumen T31 as an example to describe the alarms.
A-4

Appendix A Maintenance Forms
A.3 Weekly Maintenance Record

Table A-3 Weekly Maintenance Record (Bi-weekly)
Maintenance Item Maintenance Content Check Result Remarks
Fan check The fan runs normally or not
The dust-proof net at the fan (Record the

bottom is clean or not cleansing date)
Check orderwire Dial the central site orderwire (Verify that the call is connected and
telephones phone whether the voice quality is normal)
(Non-central site)
The central site dials back the (Verify that the call is connected and
local orderwire phone whether the voice quality is normal)
Check orderwire Dial site A orderwire phone (Verify that the call is connected and
telephones (Central whether the voice quality is normal)
site)
Dial-back (Verify that the call is connected and
whether the voice quality is normal)
Dial site B orderwire phone (Verify that the call is connected and

Dial site C orderwire phone (Verify that the call is connected and

Channel Check When no service is configured (Recording the tested BER)

to the channel, a BER tester
is used for the test, otherwise
the NM is to perform 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)
Check by: Check date:
• The central site needs to dial the orderwire telephones of all the sites in the subnet to test the orderwire voice quality,
while an ordinary site only needs to dial the central site for test.
A-5

A.4 Login Password Change Record

Table A-4 Login Password Change Record
The Last Change This Change Recorded into the Changed Checked Check Date
Date Date Memorandum or not By By
• The login password should be changed once a month.

• The table can be changed depending on the actual conditions.
Note:
For irregular checks of system configuration, security log, report printing, and data backup,
the maintenance forms can be made in accordance with the above forms.
A-6

Appendix B
NE Address Definition and
Route Configuration
Table of Contents
Ÿ Definition of the NE IP Address............................................................................... B-1
Ÿ Example of Network Address Coding of NEs .......................................................... B-5
Ÿ Address and Route Configuration of the EMS Host................................................. B-8
B.1 Definition of the NE IP Address
Note:
When configuring NE initial information, the IP addresses of this NE and the EMS host must
be determined and written into the NE NCP board, which allow no random modification
when the equipment operates normally.
The definition of the NE IP address is the same as that of the common IP address.
However, the meaning of each byte in NE IP address is redefined. The configuration
principle and byte meanings vary with different mask format.
B.1.1 FLSM Addressing

Definitions of NE IP Address and Subnet Mask
For the definitions of NE IP address and subnet mask in FLSM addressing, refer to Table
B-1.
Table B-1 Definitions of NE IP Address and Subnet Mask (FLSM)
Item Description Remarks
NE IP byte 1.byte 2.byte 3.byte 4 1. The NE IP address contains three parts: area code, NE code, and
address NCP board number. Byte 1 serves as the area code, some address
bits of byte 2 and byte 3 serve as the NE code, and the remaining
address bits and byte 4 form the NCP board number.
2. The area ID combined with NE ID corresponds to the network
address. The NCP board number corresponds to the host address.
B-1

Subnet 255.byte 2.byte 3.0 The result got from the logic AND operation of NE IP address and subnet
mask mask defines the specific meaning of each byte in NE IP address.
Definitions of Area ID, NE ID, and Board ID

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

For the meanings of each byte in the NE IP address, refer to Table B-3.
Table B-3 Meanings of Bytes in the NE IP Address (FLSM)
NE IP Address Subnet Mask Description
byte 1.byte 2.byte 3.byte 4 255.255.255.0 Byte 1 is the area ID, byte 2 and byte 3 form the NE ID, and
byte 4 is the NCP board number.
255.255.0.0 Byte 1 is the area ID, byte 2 is the NE ID, and byte 3 and byte
4 form the NCP board number.
B-2

Appendix B NE Address Definition and Route Configuration
Taking three NEs as example, when different subnet masks are used, the NE IP addresses
are allocated as listed in Table B-4.
Table B-4 NE IP Address Allocation (FLSM)
Subnet Mask NE 1 NE 2
255.255.255.0 193.1.1.18 193.1.2.18
255.255.0.0 193.1.1.18 193.2.1.18
B.1.2 VLSM Addressing

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

For the definitions of NE IP address and subnet mask, refer to Table B-5.
Table B-5 Definitions of NE IP Address and Subnet Mask (VLSM)
NE IP byte 1.byte 2.byte 3.byte 4 1. It consists of three parts: area ID, ECC subnet ID, and NE ID.
address 2. Each NE needs to be allocated with an IP address. In the
same ECC subnet (an interconnected ECC network), the NE
IP address must be unique.
Subnet byte 1.byte 2.byte 3.byte 4 1. The result got from the logic AND operation of NE IP address
mask and subnet mask defines the specific meaning of each byte
in NE IP address.
2. Byte 1, byte 2 and byte 3 are generally 255s, and byte 4 can
be set between 0 to 255 randomly.
Definitions of Area ID, ECC Subnet ID, and NE ID

For the definitions of area ID, ECC subnet ID, and NE ID, refer to Table B-6.
B-3

Table B-6 Definitions of Area ID, ECC Subnet ID, and NE ID (VLSM)
Area ID 1. Represents for the area that the NE 1. For a complicated ECC subnet, the multi-area
belongs to. configuration must be used due to the limitation of
2. It is byte 1 of NE IP address NE processing capability and the requirement of
dynamic route protocol.
2. Refer to the description of area ID in the "FLSM
Addressing" section for division principle and
requirement of the area ID.
ECC subnet ID 1. Represents for the ECC subnet ID A complicated ECC subnet can contain multiple areas.
that the NE belongs to
2. It is byte 2 of NE IP address
NE ID It is the result got from the logic AND -

operation of byte 3, 4 of the NE IP
address, and corresponding bytes of
the subnet mask.
Example of NE IP Address Allocation

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

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

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

This section uses the network topology shown in Figure B-1 as an example to describe
the network address allocation using the FLSM technique.
B-5

Figure B-1 Network Topology
Example
Scheme 1: Dividing areas in accordance with Figure B-1 can simplify connections between
areas, and the NEs belonging to the backbone area are relatively few.
l NEs 1, 2, 3, 4, 5, 6, and 8: they are relatively centralized, among which there are
multiple connections, and they form a mesh topology. Therefore, they are allocated
into area 193.
l NEs 9, 11, and 12: they are relatively centralized and form a ring topology. Therefore,
they are allocated into area 194.
l NEs 7 and 10: there is only one single connection between areas 193 and 194 via
NEs 7 and 10. Therefore, NEs 7 and 10 are taken out as the backbone area (area
192) for connecting other areas.
For area definitions and NE IP address configurations, refer to Table B-7.
B-6

Table B-7 Area Definitions and NE IP Address Configurations
Area ID NEs in the Area
NE NE IP Address
Area 193 Access NE 1 193.1.1.18
NE 2 193.1.2.18
NE 3 193.1.3.18
NE 4 193.1.4.18
NE 5 193.1.5.18
NE 6 193.1.6.18
NE 8 193.1.8.18
Area 194 NE 9 194.1.9.18
NE 11 194.1.11.18
NE 12 194.1.12.18
Area 192 (backbone area) NE 7 192.1.7.18
NE 10 192.1.10.18
• The network mask is 255.255.255.0 and the EMS host address is 193.1.1.1.
Example
Scheme 2: Because the NEs in Figure B-1 are relatively few, all the NEs can be simply
allocated into one area (for example, they may all be allocated into area 193), in which the
backbone area is not needed.
Their NE addresses are listed in Table B-8.
Table B-8 NE IP Address Configurations of the NEs Allocated into Area 193
NE NE IP Address NE
Access NE 1 193.1.1.18 NE 2
NE 3 193.1.3.18 NE 4
NE 5 193.1.5.18 NE 6
NE 7 193.1.7.18 NE 8
NE 9 193.1.9.18 NE 10
NE 11 193.1.11.18 NE 12
• The network mask is 255.255.255.0 and the EMS host address is 193.1.1.1.
B-7

Note:
Although allocating all NEs into the same area is simple, the efficiency of ECC route
algorithm will be affected if the number of NEs is large. Therefore, this method only applies
to applications with a small number of NEs. Normally, the maximum number of NEs in one
area must not exceed 120.
B.3 Address and 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 entire network.
B.3.1 EMS Host Address

The EMS host address include the EMS host IP address, subnet mask, and gateway
address, refer to Table B-9.
Table B-9 Definition of the EMS Host Address
Item Description Configuration Principle
IP address Defines the EMS host 1. The result got from the logic AND operation of the EMS host IP
network address. Employs address and the subnet mask must be within the same network
the IP address format: byte section as the access NE, i.e. the EMS host and the gateway
1.byte 2.byte 3.byte 4. NE must have the same network ID.
2. The EMS host ID must be less than the gateway NE host ID
(i.e. the NCP board number). The EMS host ID is suggested
to range from 1 to 9, starting from 1. The IP address of the
EMS host must not conflict with the IP address of any NE in
the network.
Subnet mask Defines the subnet mask The subnet mask is suggested to be the same as the subnet mask
of the EMS host. Used of access NE.
to divide network section
by performing logic AND
operation with the EMS host
IP address.
Gateway Defines the gateway address Set the access NE as the gateway NE.
address of the EMS host.
Consider the networking shown in "Example of Network Address Coding of NEs", for
example, bind an IP address 193.1.1.1 which is within the same network section as
gateway NE 1, with the network adapter of EMS host; thus ensuring that EMS host can
reach the access NE. Define the gateway NE address as 193.1.1.18, thus ensuring that
EMS host can reach area 193.
B-8

Set the routes on the EMS host to reach NEs in area 192 and area 194.
B.3.2 Route Configuration

There are two methods to set the routes on EMS:
1. 1.Run the OSPF dynamic routing protocol at the EMS host side.
This method requires no route setting. However, be cautious when using dynamic
route and do not advertise those invalid or possibly repeated routes to the network, to
avoid some unreachable NEs or too large routing table. In addition, the application of
dynamic route increases the operating load of EMS host.
Tip:
Therefore, it is recommended to set static route or default route for the EMS host, so as
to filter out IP packets that are irrelevant to the network, thus increases the operating
efficiency of EMS.
2. Set default route or static route directing to the NE that directly connects with the EMS
host. Delete other routes that are repeatedly configured. As an example, consider the
network shown in "Example of Network Address Coding of NEs", the method of setting
default route or static route for EMS host is as follows:
a. Set the default route
route add default 193.1.1.18

This default route means that all IP packets, without showing route locally, have
to pass NE 1 whose IP address is 193.1.1.18.
b. Set static routes

route add 193.1.0.0 mask 255.255.0.0 193.1.1.18
route add 194.1.0.0 mask 255.255.0.0 193.1.1.18
route add 192.1.0.0 mask 255.255.0.0 193.1.1.18
The three static routes mean that all IP packets accessing the networks 193.1,
194.1, and 192.1 shall pass NE 1 whose IP address is 193.1.1.18.
B.3.3 Route Configuration Commands

Windows operating system has different route configuration commands from the Unix
operating system. Suppose the gateway address is 193.1.1.18, and the subnet mask is
255.255.0.0.
B-9

Windows Operating System

For the commonly used commands in Windows 2000 to set routes (implemented in the
cmd interface), refer to Table B-10.
Table B-10 Route Configuration Commands in Windows 2000
Operation Purpose Command Line
Add a default route route add 0.0.0.0 mask 0.0.0.0 193.1.1.18
Add a route route add 193.1.0.0 mask 255.255.0.0 193.1.1.18

//add a route from the gateway NE to network 193.1
Add a permanent route route add 193.1.0.0 mask 255.255.0.0 193.1.1.18 -p

//add a permanent route from the gateway NE to network 193.1
Delete a route route delete 193.1.0.0 mask 255.255.0.0 193.1.1.18

//delete a route from the gateway NE to network 193.1
View a route route print
Verify that the destination ping 192.1.7.18

NE is reachable //verify that the gateway NE can reach the destination NE whose IP address is
192.1.7.18
View all the NEs along the tracert 192.1.7.18

route //view the NEs along the route that passes the IP address 192.1.7.18
Note:
Once the computer is restarted, all the routes added by the command of route add will be
lost. Use the command of route add Cp to permanently add one route to the computer.
Unix Operating System

In Unix operating system, route configuration can be completed using command line and
file.
l Command line
For the commonly used command lines to set route, refer to Table B-11.
Table B-11 Route Configuration Command Lines in Unix
Add a default route route add default 193.1.1.18 1

//add a default route to the gateway NE
B-10

Add a route route add 193.1.0.0 255.255.0.0 193.1.1.18 1 (HP-UX)

//add a route from the gateway NE to network 193.1 (HP-UX)
route add net 193.1.0.0 193.1.1.18 1 (Solaris)

//add a route from the gateway NE to network 193.1 (Solaris)
Delete a route route delete 193.1.0.0

//delete a route from the gateway NE to network 193.1
View a route netstat

//View the route that the gateway NE can reach
Verify that the destination ping 192.1.7.18

NE is reachable //verify that the gateway NE can reach the NE whose IP address is 192.1.7.18
View all the NEs along the tracertroute 192.1.7.18

route //view the NEs along the route that passes the IP address 192.1.7.18
Note:
Once the computer is restarted, all the routes added by the command lines will be
lost. Modify the configuration file and save the changes to permanently add one route
to the computer.
l Modify the configuration file

In different Unix systems, the configuration file location and the modification operation
are different.
à HP-UX platform
Modify the /etc/rc.config.d/netconf file in the document editor. The
configuration commands in the file will automatically apply and be saved
permanently after the system is restarted.
For the route configuration commands in configuration file, refer to Table B-12.
Table B-12 Route Configuration Commands in Configuration File (HP-UX)
Operation File Modifications Corresponding Command Line

Purpose
Add a default ROUTE_DESTINATION[0]=default route add default 193.1.1.18 1

route //add a default route to the gateway NE
ROUTE_MASK[0]=
ROUTE_GATEWAY[0]=193.1.1.18
ROUTE_COUNT[0]=1
ROUTE_ARGS[0]=
B-11

Operation File Modifications Corresponding Command Line

Purpose
Add a route ROUTE_DESTINATION[1]=193.1.0.0 route add 193.1.0.0 255.255.0.0

193.1.1.18 1
ROUTE_MASK[1]=255.255.0.0
//add a route from the gateway NE to network
ROUTE_GATEWAY[1]=193.1.1.18
193.1
ROUTE_COUNT[1]=1
ROUTE_ARGS[1]=
à Solaris platform
Modify the configuration files listed in Table B-13 in the document editor.
The configuration commands in the file will automatically apply and be saved
permanently after the system is restarted.
Table B-13 Route Configuration Commands in Configuration File (Solaris)
File Location Function/Format Example
/etc/hosts 1. Set added IP address 127.0.0.1 localhost loghost

2. Format: IP_address Host_name 192.192.1.1 hknttserver
Alias 192.192.66.1 hknttsdh
168.69.74.35 almftp
/etc/netmasks 1. Set the subnet mask for the added IP 192.192.1.0 255.255.255.0
address 192.192.66.0 255.255.255.0
2. Format: Network_ID Subnet_mask 168.69.74.0 255.255.255.0
/etc/hostname.eri0 1. Set the active IP address hknttserver

2. Format: Host_name
/etc/hostname.eri 1. Set the logic IP address. One Define the file of /etc/hostname.er
0:x hostname.eri0:x file needs to be i0:1 as hknttsdh. Define the file of
added for each added IP address (x /etc/hostname.eri0:2 as almftp
starts from one)
2. Format: Host_name
/etc/rc2.d/zteRout 1. Add static route.This file will be route add net 192.192.0.0
er automatically loaded when the system Cnetmask 255.255.192.0
starts. The file name is S96zteRouter. 192.192.1.6 1
The name zteRouter can be defined at route add net 192.192.64.0
your will except existed file name in the Cnetmask 255.255.192.0
/etc/rc2.d directory 192.192.66.18 1
2. Format to add one route: route add[ route add net 168.65.0.0
host | net ] destination 168.69.74.1 5
gateway
/etc/defaultrouter Input the IP address to set the default -

gateway
B-12

Appendix C
Configuration Description of
NCP/ENCP Agent Program
Table of Contents
Ÿ Description of NCP Board....................................................................................... C-1
Ÿ Description of BOOTROM Module on NCP Board .................................................. C-2
Ÿ Local Upgrade Instructions ..................................................................................... C-3
Ÿ Remote Upgrade Instructions ............................................................................... C-15
Ÿ Verifying the Application/Logic Version on EMS ................................................... C-29
C.1 Description of NCP Board
Tip:
The initial ZXMP S385 equipment cannot connect to the EMS terminal computer for
network configuration or network management until the Agent application has been
downloaded to the NCP board and the initial parameters have been configured.
1. The ZXMP S385 equipment reserves two slots for NCP board (No. 18 and No. 19
slots. Generally, No. 18 slot is called the master slot, and No. 19 slot is called
the standby slot). Therefore two NCP boards or ENCP boards can be installed
simultaneously to implement the 1+1 protection for NCP/ENCP boards.
2. The NCP board has an Ethernet interface (debugging interface), see Figure C-1.
C-1

Figure C-1 NCP PCB Board
1. Board running 3. Critical alarm indicator 6. Master status indicator

indicator NOM ALM2 MS
2. Major/minor alarm 4. Dip switch S1 7. Reset button RST
indicator ALM1 5. Ethernet interface
(debugging interface)
The Ethernet interface is used to connect the NCP board working in the Download
status. QxI board also has an Ethernet interface (EMS Qx interface) which is used
to connect the NCP board working in the master status. Refer to the sections of
"Functions of BOOTROOM Module on NCP" and "NCP Board State Switching" for
the work states of NCP board.
3. If two NCP boards are installed simultaneously, one NCP board is the master board
and the other is the standby board at any moment during normal operating. The
Ethernet port of QxI board only communicates with the master board, i.e. it can only
connect one NCP board (the master NCP board) at any moment.
C.2 Description of BOOTROM Module on NCP Board

C.2.1 Functions of BOOTROM Module on NCP
1. Prepare for operating the Agent application.
a. Download (burn) the NCP application program to the CF card on NCP.
b. Download the configuration files to the CF card on NCP.

2. Start the Agent program on NCP board.
3. Other functions
a. Format the CF card.

b. Delete the database and Agent program of NCP board.
c. Read and set the system parameters (especially the MAC address).
C-2

Appendix C Configuration Description of NCP/ENCP Agent Program
C.2.2 NCP Board State Switching

The functional states of NCP board include download state and operating state which are
determined by the DIP switch on NCP board. For the functions and DIP modes of the two
states, refer to Table C-1.
Table C-1 Description of NCP Board States
NCP Board State Function DIP Switch
Download state 1. Download the Agent application program and Full ON

configuration files.
2. After the NCP board is started or reset, its default
IP address is 192.192.192.11. In this state,
communication between the EMS and the NCP
board can only be established by connecting the
EMS with the Ethernet interface of this NCP board.
Operating State 1. Start the application program on NCP. Non-full ON and

2. After the NCP board is started or reset, it enters non-full OFF
the operating state. In this state, connect the EMS
with the Qx interface of QxI board to establish
communication between the EMS and the master
NCP board.
C.3 Local Upgrade Instructions

C.3.1 Local Upgrade Flowchart
Local upgrade refers to the procedure of upgrading application/logic in the download state.
For the local upgrade flowchart, see Figure C-2.
C-3

Figure C-2 Local Upgrade Flowchart
C.3.2 Local Upgrade Preparations

This procedure describes the preparations before executing local upgrade.
Context
Figure C-3 shows the flowchart of local upgrade preparations.
C-4

Figure C-3 Flowchart of Local Upgrade Preparations
The steps of local upgrade preparations are described as follows.
Steps
1. Ensure that the correct BOOTROM chip is plugged on NCP board.
2. Ensure that the CF card is correctly plugged on NCP.
3. Set the DIP switch on NCP board to all ON state (Download state). And the NE IP
address is 192.192.192.11 with the subnet mask of 255.255.255.0.
C-5

4. Connect the Ethernet interface of the EMS computer and the Qx interface of the NCP
board with a network cable, and ensure that the connection is correct.
5. Set the IP address and subnet mask of the EMS computer.
IP address: 192.192.192.X (0 < X < 255 and X ≠ 11)
Subnet mask: 255.255.255.0
6. Execute the ping 192.192.192.11 command on the EMS computer to confirm that
the EMS computer can connect to NCP.
l If it is unnecessary to completely clear the NE data or reconfigure the NE, the
upgrade preparations are completed.
l If it is necessary to completely clear the NE data and reconfigure the NE, follow
the steps below:
7. Perform the following operation to clear the NE data, and configure the NE again.
a. Execute the command telnet 192.192.192.11 on the EMS computer.
b. The system prompts to enter user name and password which are both empty, and
then press the Enter key directly. The DOS prompt ZTE+> is displayed.
c. Input the command d-erase -d1 to erase the database, see Figure C-4.
Figure C-4 Erase the Database
d. Input the commands d-erase -p1 and d-erase -p2 to erase the chip area which
saves the application program, see Figure C-5.
Figure C-5 Erase the Chip Area which Saves the Application Program
e. Input the commands d-erase -f1 and d-erase -f2 to erase the chip area which
saves the logic program, see Figure C-6.
C-6

Figure C-6 Erase the Chip Area Which Saves the Logic Program
f. Input the command d-cfgnet to configure the NE related information, see Figure
C-7. For the input principles of each item, refer to Table C-2.
Figure C-7 Configure the NE Related Information
Table C-2 Inputs Principles of NE Related Parameters
Parameter Name Input Principle
IP Address Input the IP address of the NE
Subnet Mask Input the subnet mask of the NE
MAC Address Input the physical address of the NE. It is mandatory and should
be unique for each NE.
Warning!
Press the Enter key directly if there is no modification. Do not quit in the middle
of the procedure, otherwise the NCP board will stay in the infinite waiting state.
g. Input the command d-reboot to reboot the NCP board, and the NE information
configuration will apply. Upgrade preparations are completed.
C-7

C.3.3 Clearing the Database Locally

This procedure describes how to clear the database locally.
Context
Tip:
If the NE data has been cleared during the upgrade preparation, this step can be skipped.
Steps
1. Execute the command telnet 192.192.192.11 on the EMS computer.
2. The system prompts to enter user name and password which are both empty, and then
press the Enter key. The DOS prompt ZTE+> is displayed.
3. Input the command d-erase -d1 to erase the database.
C.3.4 Downloading the Application/Logic Locally

This procedure describes how to download the application/logic Locally
Steps
1. Execute the command ftp 192.192.192.11 under the directory containing the
Agent program or logic on the computer, and then input the user name and password,
which are both empty.
2. Press the Enter key until the prompt ftp> is displayed. All the following operations
are completed under this prompt.
3. Execute the following commands in turn to download the board application/logic and
verify that the downloaded file is correct.
a. ftp> bin
//Set the file transfer mode to binary mode.
b. ftp> put file_name_of_the_application/logic

//Download the board application/logic. When the ftp> prompt appears again, it
indicates that the file transfer has completed.
C-8

Note:
After the put command is executed, the size of the downloaded file will return
(bytes sent). Verify that the downloaded file size is consistent with the local file. If
not consistent, re-download the file.
c. ftp> bye
//Exit the ftp connection.
Note:
The application/logic of NCP board must be transferred to the NCP board in the binary
mode.
Example
Suppose the Agent program NCP-ZXMP S385-PRG-V1.01R1P05.BIN is downloaded
from the computer to the NE, the operations are shown in Figure C-8.
Figure C-8 Local Download of NCP Application to NE
C.3.5 Upgrading the Application/Logic Locally

This procedure describes how to upgrade the application/logic Locally.
C-9

Context
This operation is to upgrade the application/logic on CF card into the application/logic area.
Steps
1. Execute the command telnet 192.192.192.11. Input the username and password
as prompted.
2. Press the Enter key until the prompt ZTE+> is displayed. All the following operations
are completed under this prompt.
3. Execute the command d-upgrade to upgrade the board application/logic into the
application/logic area respectively.
Command Format:d-upgrade Subrack-NO. Slot-NO. Board-CPU-NO. {-p

Application-file-name\-f Logic-file-name}
For Parameter Description, refer to Table C-3
Table C-3 Parameters of the d-upgrade Command
Parameter Parameter Value

Name
Subrack-NO. 1 or 2, generally 1.
Slot-NO. The slot number of the board. It is an integer ranging from 1 to 19. It is
18 or 19 for the NCP board.
Board-CPU-NO. Integer ranging from 1 to 3, generally 1.
-p The parameter for NCP application delivery, followed by the board application
file name.
-f The parameter for NCP logic delivery, followed by the board logic file name.
Example
To upgrade the program in the Figure of "Local Downloading of NCP Application to NE" in
the section of "Downloading the Application/Logic" into the application/logic area, perform
the operation, see Figure C-9.
C-10

Figure C-9 Local Upgrade of NCP Application to NE
C.3.6 Verifying the Application/Logic After Local Upgrade

This procedure describes how to verify the application/logic after local upgrade.
Steps
1. Execute the command telnet 192.192.192.11. Input the username and password
as prompted, which are both empty.
2. Press Enter until the prompt ZTE+> is displayed.

3. Execute the command d-get-status under the prompt, to verify that the application/logic
version is normal.
Command Format: d-get-status Subrack-NO. Slot-NO. Board-CPU-NO.

Table C-4 Parameters of the Command d-get-status
Slot-No. The slot number of the board. It is an integer ranging from 1 to 19. It is 18 or
19 for the NCP board.
C-11

Tip:
If the version is abnormal, it is necessary to re-perform the operations described in the
sections "Downloading the Application/Logic" and "Upgrading the Application/Logic"
until the version queried is normal.
Example
Verify the version of the application in section "Downloading the Application/Logic", see
Figure C-10.
Figure C-10 Version Information for Local Upgrade of Board Application
For Descriptions of Parameters, refer to Table C-5
Table C-5 Descriptions of Parameters that Need to be Verified for Local Upgraded
Board Program Version
Parameter Name Parameter Description Remarks
file type program indicates the application -

area
download date File downloaded time Should be consistent with the actual
time when the file is downloaded
download version File version downloaded Should be consistent with the actual
downloaded file version
try-run type reserved indicates that this -

parameter is reserved
status master indicates the master status -
C-12

upgrade database NO indicates the database is not -

upgraded
start address 0x0A000000 indicates the initial -

address of the program
file length The size of the downloaded file Should be consistent with the actual
downloaded file size
try-run elapsed time reserved indicates that this -

try-run remained time reserved indicates that this -

C.3.7 Upgrading the Application/Logic for Standby NCP Locally

This procedure describes how to upgrading the application/logic for standby NCP locally.
Context
Tip:
If only one NCP board is configured on ZXMP S385, skip this step.
Caution!
The IP address, subnet mask, and MAC address of the standby NCP board must be the
same as those of the master NCP board.
Steps
1. Re-perform the steps described in the sections from"C.3.2 Local Upgrade
Preparations" to "C.3.6 Verifying the Application/Logic After Local Upgrade", to
upgrade the standby NCP board.
C.3.8 Downloading the Database Locally

This procedure describes how to download the database Locally.
C-13

Steps
1. Set the DIP switches of both NCP boards to non-all ON and also non-all OFF state
(Running state). Reset the NCP board and it enters the Running state.
Note:
During local upgrade, the user can restart or reset the NCP board and press the bell-off
button continuously to enter the Download state. Then, unplug the NCP board and
re-insert it into the slot, and it enters the Running state.
2. Set the IP address of EMS computer to be within the same network segment as the
NE IP address.
3. Execute the command ping NE IP to confirm if the NE can be pinged through.
4. In the Topology Management view of the NetNumen T31 EMS, select the NE to be
upgraded.
5. Select Device Config > Data Synchronization. The Data Synchronization dialog
box is displayed.
a. Click the Download tab.
b. Select the items to be downloaded, and then click Download. The Confirm dialog
box is displayed.
C-14

Note:
After the above procedures, the database has been cleared without any services
available, so there is no such a problem as service interruption.
c. In the Confirm dialog box, click Yes to confirm downloading. The Confirm dialog
box of downloading NE properties is displayed.
d. Click Yes to download the NE property information. After the NE property
information has been downloaded successfully, the Message dialog box is
displayed.
Note:
l After the NE information has been downloaded successfully, the node will
automatically restart.
l It is unnecessary to download the database when upgrading the logic.
l To upgrade the EMS, click the Upload tab.
C.4 Remote Upgrade Instructions

C.4.1 Remote Upgrade Flowchart
The remote upgrade is the procedure that upgrades the application/logic of NCP board in
its Running state. For the flowchart, see Figure C-11.
C-15

Figure C-11 Remote Upgrade Flowchart
C-16

C.4.2 Remote Upgrade Preparations

This procedure describes the remote upgrade preparations.
Steps
1. Use network cable to connect the Ethernet interface of EMS computer with the
Ethernet interface of QxI board.
2. Execute the ping NE-IP command at the EMS terminal. Confirm that the EMS
terminal communicates normally with the NE, and that the ECC of the NE to be
upgraded is smooth.
3. Confirm that the Agent program version to be downloaded complies with the current
EMS version. Ensure the validity and consistency of the versions.
C.4.3 Confirming the Address of the Master NCP Board

You can confirm the address of the master NCP board through the command lines.
Steps
l On the EMS computer, execute the command telnetNE IP.
l Input the user name of zte and password of ecc in accordance with the system prompt.
l Press Enter until the prompt ZTE+> is displayed. The system indicates User zte
logged in if login succeeds, otherwise, the system indicates Sorry! Password
Incorrect!.
l Execute the command a-get-sysinfo state to view the information of the current master
NCP board, see Figure C-12
Example
Figure C-12 Viewing NCP Board Information
In Figure C-12, address: 11201: 11201 is a hexadecimal code, where the third and fourth
bits (12) are equal to 18 in decimal code after conversion, indicating that the current master
NCP board is in slot 18.
C.4.4 Downloading the Application/Logic Remotely

Before remote upgrade, you need to download the corresponding application/logic.
C-17

Steps
1. Execute the command ftp NE-IP under the directory containing the Agent program
or logic on the computer. Input zte for username and ecc for password in accordance
with the system prompts.
2. Press the Enter key until the prompt ftp> appears. All the following operations are
completed under this prompt.
3. Execute the following commands to download the board application/logic.
a. ftp> bin
//Set the file transfer mode to binary mode.
b. ftp> put file_name_of_the_application/logic
//Download the board application/logic.
c. ftp> ls -l
Check if the downloaded file size is consistent with the local file. If not consistent,
re-download the file.
d. ftp> bye
//Exit ftp connection.
C.4.5 Upgrading the Application/Logic Remotely

This procedure describes how to upgrading the application/logic remotely.
Steps
1. Execute the command telnet NE-IP. Input zte for username and ecc for password
according to the system prompts.
3. Execute the command d-upgrade to upgrade the board application/logic. Refer to
the section "Upgrading the Application/Logic" in Local Upgrade part for detailed
procedures of upgrading the application/logic.
Checkpoint:
When executing the d-upgrade command, the Slot-No. parameter should be the slot
number of the master NCP board queried in the section "Confirming the Address of
the Master NCP Board".
C-18

Example
To upgrade the program file NCP-ZXMP S385-PRG-V1.01R1P05.BIN that has been
downloaded to the NE (with IP address of 213.17.1.166) into the application area, the
operations are shown in Figure C-13.
Figure C-13 Remote Upgrade of Application
C.4.6 Verifying the Application/Logic After Remote Upgrade

This procedure describes how to verify the application/logic after remote upgrade.
Steps
1. Execute the command d-get-status under the prompt of ZTE+>.
Parameter Description: as listed in "Verifying the Application/Logic After Local

Upgrade".
2. Verify if the version of the upgraded application/logic in the standby area is normal
based on the executed command result.
C-19

Note:
If the version is abnormal, it is necessary to perform the operations in the section
"Downloading the Application/logic" and the section "Upgrading the Application/Logic"
again, until the version queried is normal.
Example
To verify the program file in the section "Upgrading the Application/Logic", the result is
shown in Figure C-14.
Figure C-14 Verifying the Upgraded Program
Descriptions of Parameters: Table C-6
C-20

Table C-6 Parameters in the Standby Area that Need to be Verified
file type program indicates the application -

area
download date File downloaded time Should be consistent with the actual
time when the file is downloaded
download version File version downloaded Should be consistent with the actual
downloaded file version
try-run type reserved indicates that this -

status master indicates the master status -
upgrade database NO indicates the database is not -

upgraded

file length The size of the downloaded file Should be consistent with the actual
downloaded file size
try-run elapsed time reserved indicates that this -

try-run remained time reserved indicates that this -

C.4.7 Try Running the Application/Logic

This procedure describes how to try running the application/logic.
Steps
1. Execute the command d-try under the prompt of ZTE+> to perform the try run of the
application/logic.
Command Format: d-try Subrack-NO. Slot-NO. Board-CPU-NO. {-p|-f}
For Parameter Description, refer to Table C-7.
Table C-7 Parameters of the d-try Command
Slot-No. The slot number of the board. It is an integer ranging from 1 to 19. It is
18 or 19 for the NCP board.
C-21

-p Try running the board application.
-f Try running the board logic.
2. When executing the command, the system will prompt: Do you want to upgrade
the DB area?Yes[y]/No[n].
l Select y to clear the NCP database;
l Select n to not to clear the NCP database.
When the d-try command completes, the NCP board is reset, and the communication
with the computer is interrupted. The ECC will be interrupted for about one to two
minutes, and during this time the EMS cannot manage this NE. If there are two NCP
boards, after the reset, the system will switch to another NCP board first.
Example
To try run the program file in the section "Upgrading the Application/Logic", see Figure
C-15.
Figure C-15 Try Run of the Program
C.4.8 Verifying the Application/Logic After Try Run

This procedure describes how to verify the application/logic after try run.
Steps
1. Execute the telnet NE-IP command on the EMS computer, and input the user name
of zte and password of ecc in accordance with the system prompts.
3. Execute the a-get-sysinfo state command, to verify that the communication state of
the standby NCP board is normal, and confirm the master NCP address according to
the command result. For the operation example, refer to the section "Confirming the
Address of the Master NCP Board".
4. Execute the command d-get-status under the prompt of ZTE+> to verify if the version
of the upgraded application/logic in the original standby area is normal.
C-22


Upgrade".
Tip:
If the version is abnormal, it is necessary to perform the operations in the section
"Downloading the Application/logic" and the section "Upgrading the Application/Logic"
again, until the version queried is normal.
Example
To verify the program file in section "Try Run of the Application/Logic", see Figure C-16.
Figure C-16 Verifying the Program that Passed the Try Run
For the parameters in the original standby area (labeled as program number: 0x02)
that need to be verified, refer to Table C-8.
C-23

Table C-8 Parameters in the Original Standby Area that Need to be Verified after the
Try Run
file type program indicates the application area -
download date File downloaded time Should be consistent with the result
in Figure C-16.
download version File version downloaded Should be consistent with the result
in Figure C-16.
try-run type try-run indicates that it is performing -

the try-run of the program
status try-run indicates the try-run status -
upgrade database YES! indicates that the database is -

upgraded

file length Size of the downloaded file Should be consistent with the result
in Figure C-16.
try-run elapsed time 4<minutes> indicates the elapsed time -

of the try-run
try-run remained time 11<minutes> indicates the remaining -

time of the try-run
C.4.9 Activating the Application/Logic

This procedure describes how to activate the application/logic.
Context
After the application/logic is downloaded and upgraded, you need to activate it within 15
minutes after the try run.
Execute the command d-active under the prompt of ZTE+> to activate the application/logic.
Command Format: d-active Subrack-NO. Slot-NO. Board-CPU-NO. {-p|-f}
Table C-9 Parameters of the Command d-active
Slot-No. The slot number of the board. It is an integer ranging from 1 to 19. It is 18 or
19 for the NCP board.
C-24

-p Activate the board application.
-f Activate the board logic.
Caution!
If the application/logic is not activated within 15 minutes after the try-run, or it is not
activated before resetting the NCP board, it will go back to the original application/logic.
Steps
1. For the program activation operation, see Figure C-17.
Figure C-17 Activating the Program
C.4.10 Verifying the Activated Application/Logic

This procedure describes how to verify the activated application/logic.
Steps
1. Execute the command d-get-status under the prompt of ZTE+>.

Upgrade".
2. Verify the activated application/logic in the original standby area according to the
command result.
Example
To verify the activated application/logic in the original standby area, the operation and result
are shown in Figure C-18.
C-25

Figure C-18 Verifying the Activated Program
For the parameters in the original standby area (labeled as program number: 0x02)
that need to be verified, refer to Table C-10.
Table C-10 Descriptions of Parameters that Need to be Verified after Activation
file type program indicates the -

application area
download date File downloaded time Should be consistent with the result in
"Verifying the Application/Logic After
Remote Upgrade"
download version File version downloaded Should be consistent with the result in
Remote Upgrade"
try-run type Changes to reserved -
status master indicates the master The status of the area labeled as program
status number: 0x01 should change to slave
C-26

upgrade database NO indicates that the database -

upgrade is completed

file length Size of the downloaded file Should be consistent with the result in
Remote Upgrade"
try-run elapsed time Changes to reserved -
try-run remained Changes to reserved -

time
C.4.11 Upgrading the Application/Logic for Standby NCP Remotely
Note:
If only one NCP board is configured on ZXMP S385, skip this step.
Steps
1. Execute the telnet NE-IP command on the EMS computer, and input the user name
of zte and password of ecc according to the system prompts.
3. Execute the command d-set-ncpbackstat under the prompt ZTE+> to switch to the
standby NCP board, see Figure C-19.
C-27

Figure C-19 Switching to the Standby NCP Board
4. Re-perform all the operations from section "Upgrade Preparations" to section

"Verifying the Activated Application/Logic", to complete the upgrade of the standby
NCP board.
C.4.12 Downloading the Database Remotely

The remote database downloading is the procedure that downloads the database to the
NCP board in its Running state.
Steps
1. In the T31 Topology Management view, select the NE to be upgraded.
2. Select Common Config > Data Synchronization from the main menu. The Data
Synchronization dialog box is displayed.
3. Click the Download tab. The Download dialog box is displayed.

4. Select the items to be downloaded, and then click Download. A message dialog box
is displayed.
5. Click Yes.
C-28

Note:
After the NE information has been downloaded successfully, the node will
automatically restart.
For the detailed procedure of downloading database, refer to the section "Downloading
the Database Locally".
C.5 Verifying the Application/Logic Version on EMS

This procedure describes how to verify the application/logic version on EMS.
Steps
1. In the Topology Management view of the NetNumen T31 EMS, double-click the
upgraded NE. The Card Management dialog box is displayed.
2. Right-click the NCP board, and select Card Current Version to be queried with the
version.
3. Check the version information of the NCP board. If the information displayed
is consistent with the downloaded application/logic, it indicates that the newly
downloaded application/logic is operating normally.
C-29

C-30

Appendix D
Initialization and Upgrade of
NE with ANCP/ANCPB Board
Table of Contents
Ÿ Overview ................................................................................................................ D-1
Ÿ Local Initialization ................................................................................................... D-2
Ÿ Remote Initialization ............................................................................................... D-9
Ÿ Downloading Database......................................................................................... D-20
Ÿ Verifying Application/Logical Program Version in EMS .......................................... D-21
D.1 Overview
An ASON equipment (NE) needs to be initialized before providing ASON functions. The
initialization procedure, which also includes the load of application and logical programs,
is implemented when the NE is set to download state.
Note:
The initialization procedures of ANCP board and ANCPB board are same. This section
uses the ANCP board as an example to describe the initialization procedure.
Figure D-1 shows the initialization flow of an ASON NE.
D-1

Figure D-1 Initialization Flow
D.2 Local Initialization

D.2.1 Local Upgrade Preparations
This procedure describes the preparation flow to local upgrade preparations.
Context
Figure D-2 shows the preparation flow before local initialization.
D-2

Appendix D Initialization and Upgrade of NE with ANCP/ANCPB Board
Figure D-2 Preparation Flow before Local Initialization
Steps
1. Check BootROM chip and CF card on the ANCP board of the NE to be initialized, and
application/logical programs and ASON configuration files to be used as well.
a. Make sure that the BootROM chip on the ANCP board is correct. Each kind of
ANCP board has its special BootROM chip.
D-3

b. Make sure that the CF card is correctly inserted on the ANCP board.
c. Make sure that right application/logical programs and ASON configuration files are
available.
Caution!
Two ASON configuration files, ason.ini and nbase.ini, are necessary for ZXMP
385 V3.XX or ZXONE 5800 V1.XX, no matter whether the equipment needs ASON
function or not. They are released corresponding to ANCP board version and can not
be modified. These two files are uploaded by means of an FTP utility. Make sure
that they are available during the initialization because the ANCP board can not work
normally without them.
Note:
ANCP board has the following two statuses:
l Download status: Switch all pins of the DIP switch S1 on the ANCP board to
"ON" position to set the ANCP board to download status. The default IP address
of corresponding NE is 192.192.192.11 in download status. And in this status,
the available network interface is Qx interface on the ANCP board, which can be
connected to the EMS computer for local initialization.
l Running status: Switch the pins of the DIP switch S1 on the ANCP board and
make sure that some of them are at "ON" position and the other at the opposite
position, to set the ANCP board to running status. And in this status, the available
interface for remote initialization is the network interface on QxI board.
2. Switch all pins of the DIP switch S1 on the ANCP board to "ON" position to set
the ANCP board to download status. In the download status, the IP address of
corresponding NE is 192.192.192.11, and the subnet mask is 255.255.255.0.
3. Connect the network interface of the EMS computer to Qx interface on the front panel
of ANCP board with a network cable and make sure that the connection is correct and
firm.
4. Add an IP address and subnet mask on the EMS computer following the principles
listed below:
l IP address: 192.192.192.X (0<X<255 and X≠11)
l Subnet mask: 255.255.255.0
5. Ping the ANCP board (192.192.192.11) on the EMS computer and check whether the
connection between the computer and the board is normal.
6. Check whether the reconfiguration of NE information is required.
D-4

l Yes→Step 7
l No→End
7. Input the command d-reboot after the prompt ZTE+> to reboot the ANCP board.
A prompt message Connection to host lost appears after successful reboot.
8. Configure the IP address, subnet mask and MAC address of the NE as follow.
a. Input the command telnet 192.192.192.11.
You are required to input the user name and password.
b. Input the user name zte and password ecc, and then press Enter key.
A prompt ZTE+ appears.
c. Input the command d-cfgnet after the prompt ZTE+ and then input the IP address,
subnet mask and MAC address one by one when prompted.
The following table describes related parameters of an NE that should be
configured, including the IP address, subnet mask and MAC address of the NE.
Parameter Requirement
IP Address It must be configured.
Subnet Mask It must be configured.
MAC Address It must be configured. Make sure that the MAC address of
each NE is unique in the network.
Caution!
Each of the three parameters must be configured. If you want to keep the
previous configuration, just press Enter key without input other information. Do
not drop out the configuration, which will result that the ANCP board always waits
for configuration .
After configuration, the address information of the NE is shown in the window, as

shown in the following figure. And you are required to confirm whether to save the
new configuration.
D-5

d. Input y to save the new configuration.

9. Input the command d-reboot to reset the ANCP board to enable the new configuration.
D.2.2 Clearing Database Locally

To clear the database of an ANCP board, perform the following steps.
Steps
1. Switch all the pins of the DIP switch S1 on the ANCP board to "ON" position to set the
ANCP board to download status.
2. Input the command telnet 192.192.192.11 on the EMS computer.
You are required to input the user name and password.
3. Input the user name zte and password ecc, and then press Enter key.
A prompt ZTE+ is displayed.
4. Input the command d-erase -d1 after the prompt ZTE+ to clear the database in the CF
card of the ANCP board.
D.2.3 Uploading Application/Logical Programs Locally

To upload the application/logical programs and ASON configuration files from the EMS
computer to the CF card of an ANCP board, perform the following steps.
D-6

Steps
1. Input the command ftp 192.192.192.11 in the DOS command line window on the
EMS computer.
2. Input the user name zte and the password ecc when prompted to log in to the ANCP
board.
A prompt ftp> appears after successful login.
3. Input the command bin after the prompt ftp> to set the file transfer format.
4. Input the command put application/logical program or configuration
file path (including file name) to transfer the application/logical program
or configuration file to the CF card.
5. Input the command ls –l to verify that the size of file transferred to the CF card is
consistent with the one on the EMS computer.
6. Input the command bye to exit the FTP utility.
D.2.4 Loading Application/Logical Programs Locally

To load (write) the application/logical program in the CF card to the application/logical
program region of the ANCP board, perform the following steps:
Steps
1. Input the command telnet 192.192.192.11 in DOS command line window on the
EMS computer
2. Input the user name zte and password ecc, and then press Enter key.
A prompt ZTE+ appears.
3. Input a command following the format below to load the application/logical program to
the ANCP board.
ZTE+>d-upgrade Subrack No. Slot No. Board CPU No. -p application file name or -f
logical program file name
The following table describes the parameters in the d-upgrade command.
Parameter Description
Subrack No. The number of subrack where the ANCP board is installed. It
is generally 1.
Slot No. The number of slot in which the board is installed. The slot No.
of ANCP board is 18.
Board CPU No. The number of board CPU. It is generally 1.
-p It indicates that the application program file following it will be

written to the board.
D-7

-f It indicates that the logical program file following it will be written

to the board.
The following figure shows an example of loading an application program.
The following figure shows an example of loading a logical program.
Note:
The application/logical program loaded by the command d-upgrade becomes the

active program by default. It is unnecessary to run and activate them for trial.
D-8

D.3 Remote Initialization

D.3.1 Remote Upgrade Preparations
This procedure describes the preparation flow to remote upgrade preparations.
Context
Figure D-3 shows the preparation flow before remote initialization.
Figure D-3 Preparation Flow Before Remote Initialization
Steps
1. Check and make sure that the connection between the EMS computer and the access
NE is normal.
D-9

2. Set the IP address of the EMS computer, which should be in the same network
segment as the access NE, and set the subnet mask of the EMS computer as
255.255.255.0.
3. Ping the access NE on the EMS computer to check whether the connection between
them is normal.
If it is unsuccessful to ping the access NE, check the running status of the access NE
and the network cable connecting it to the EMS computer.
4. Ping the NE to be initialized on the EMS computer to make sure that the route to the
NE is normal.
If it is unsuccessful to ping the NE, perform the following checkups.
a. Log in to the access NE via the telnet utility on the EMS computer, and check the
route table of the access NE to find whether the table contains the route information
of the NE to be initialized. If no, check for ECC fault.
b. Check the route information on the EMS computer. If there is no route information
of the NE, add it.
D.3.2 Uploading Application/Logical Programs Remotely

To upload the application/logical programs and ASON configuration files from the EMS
computer to a remote NE (suppose its IP address is 192.192.20.18), perform the following
steps:
Steps
1. Check and make sure that the NE to be initialized is in running status, which means
that the pins of the DIP switch on its ANCP board are not switched to the same position.
2. Input the command ftp 192.192.20.18 in the DOS command line window on the
EMS computer.
3. Input the user name zte and the password ecc when prompted, to log in the remote
NE.
A prompt ftp> appears.
4. Input the command bin after the prompt ftp> to set the file transfer format.
5. Input the command put application/logical program or configuration
file path (including file name) to transfer the application/logical program
or configuration file to the CF card in the NE's ANCP board.
6. Input the command ls –l to verify that the size of file transferred to the CF card is
consistent with the one on the EMS computer.
7. Input the command bye to exit the FTP utility.
D-10

D.3.3 Loading Application/Logical Programs Remotely (Single

ANCP Board)
The loading procedure introduced in this topic is applicable to a remote NE configured with
only one ANCP board in slot 18.
Context
Suppose the IP address of the ANCP board is 192.192.20.18 and the program file name
is "ANCP-ZXMPS385–PRG-V3.00R1P07.bin".
Steps
1. Input the command telnet 192.192.20.18 in the DOS command line window on the
EMS computer.
2. Input the user name zte and then the password ecc when prompted.
A message User zte logged in appears after successful login. You can input the
command help to check available commands related to upgrade operations, see
Figure D-4.
Figure D-4 Successful Telnet Login
3. Input the command d-upgrade 1 18 1 –p

ANCP-ZXMPS385–PRG-V3.00R1P07.bin.
D-11

Note:
l You can check the help information of this command by inputting d-upgrade in the
command line.
l Change –p to –f if the program is a logical program.
4. Input y when prompted to begin the loading of the application program to

corresponding program region in the ANCP board, see Figure D-5.
Figure D-5 Upgrading Application Program (Remote)
A message Upgrade the program area successfully! appears after successful

upgrading.
5. Input the command d-try 1 18 1 –p and input y when prompted to confirm the trial
run operation.
Note:
Change –p to –f if the program is a logical program.
6. Input n if it is unnecessary to clear the database, see Figure D-6, and then the trial run
of the program starts.
D-12

Figure D-6 Trial Run
Caution!
If it is necessary to clear the database, input y instead. Then all NE information in the
ANCP board will be erased.
7. Repeat Step 1 and 2 to log in the NE again.

8. Input the command d-get-status 1 18 1 to check the trial run result.
Caution!
Observe the running status of the board during the trial run of the program. Perform
the next step in time after making sure that the board is working normally. Or else, the
board will run the original program before loading the new program after 15 minutes.
After the command is successfully executed, both the try-run type and status are
shown as try-run, see Figure D-7. If the command fails, status are shown as slave
instead, which means that the older version program is running.
D-13

Figure D-7 Checking Trial Run Result
9. Input the command d-active 1 18 1 -p, and input y when prompted to active the
loaded program, see Figure D-8.
Figure D-8 Activating Loaded Program
Note:
D-14

10. Input the command d-get-status to check whether the status of the board turns into
master, which makes it unnecessary to reset the ANCP board.
D.3.4 Loading Application/Logical Programs Remotely (Dual ANCP

Boards)
The loading procedure introduced in this topic is applicable to a remote NE configured with
two ANCP board: one is the active one and the other is the standby one. And the exact
slot number (18 or 19) corresponding to either board is unknown.
Prerequisite
Before the loading procedure, make sure that the application/logical program files are
available in the CF card of the active ANCP board.
Context
Suppose the IP address of the active ANCP board is 192.192.20.18. For dual ANCP
boards, we load the application/logical programs to the standby one first. After the loading
procedure completes, the standby ANCP board becomes the active one. Then switch the
active one into the standby status. Repeat the loading procedure to load the programs to
the original active ANCP board.
Steps
1. Input the command telnet 192.192.20.18 in the DOS command line window on the
EMS computer.
2. Input the user name zte and then the password ecc when prompted.
A message User zte logged in appears after successful login.
3. Input the command a-set-debugon on.
4. Input the password ecc
5. Input the command a-get-sysinfo state to check the information of the active ANCP
board so as to get the slot No. of the standby ANCP board, see Figure D-9.
Figure D-9 Checking ANCP Board Information
address: 11201 in the above figure contains the slot number information "12" of the
active ANCP board, which is a hexadecimal number. It indicates that the active ANCP
D-15

board is installed in slot 18. Then we can conclude that the standby ANCP board is
installed in slot 19.
6. Input a command following the format below to load the application/logical program to
corresponding program region of the standby ANCP board.
ZTE+> d-upgrade Subrack No. Slot No. Board CPU No. -p application file name or -f
logical program file name
The following table describes the parameters in the d-upgrade command.
Subrack No. The number of subrack where the ANCP board is installed. It is
generally 1.
Slot No. The number of slot in which the board is installed. The slot No. of
ANCP board is 18 or 19.
Board CPU No. The number of board CPU. It is generally 1.
-p It indicates that the application program file following it will be written

to the board.
-f It indicates that the logical program file following it will be written to the
board.
From the result of Step 3, we know the slot No. of the standby ANCP board is 19.
Figure D-10 shows corresponding command to load the application program for
example.
Figure D-10 Remote Loading Example of Application Program (Standby ANCP

Board)
Figure D-11 shows corresponding command to load the logical program for example.
D-16

Figure D-11 Remote Loading Example of Logical Program (Standby ANCP Board)
7. Input the command d-get-status 1 19 1 to check the load information of the

application/logical program, see Figure D-12.
Figure D-12 Checking Load Information (Remote)
Verify the following information shown on the window: download date, download
version, status, upgrade database, start address and file length.
8. Input the command d-try 1 19 1 –p to try running the loaded application program.
When prompted with Do you want to upgrade the DB area?Yes[y]/No[n]: y, input y.
D-17

The standby ANCP board restarts and runs the loaded program, which results in the
communication interruption with the active ANCP board for 1 to 2 minutes. During this
period, you can not perform any operation on the standby ANCP board via the active
one.
Note:
9. After the standby ANCP board restarts successfully, input the command d-get-status
1 19 1 to check the trail run result, seeFigure D-13.
Figure D-13 Trial Run Result (Remote)
The following gives an example of the trial run result:

l file type: application program region
l download date: same as the load information got in Step 5
l download version: consistent with the loaded file
l try-run type: "try-run", which means that the board is running the program for
test
l status: "slave", which means that the ANCP board is a standby one
l upgrade database: "Yes", which means the database is upgraded
l start address: start address of the program region
l file length: same as the load information got in Step 5
l try-run elapsed time: 2 (minutes)
l remained time: 13 (minutes)
10. Input the command d-active 1 19 1 –p to activate the loaded application program,
see Figure D-14.
D-18

Figure D-14 Activating Loaded Program
Caution!
Observe the running status of the board during the trial run of the program. Perform
the next step in time after making sure that the board is working normally. Or else, the
board will run the original program before loading the new program after 15 minutes.
Note:
11. Input the command d-get-status 1 19 1 to verify the activation of program, see Figure
D-15.
Figure D-15 Verifying Activation of Loaded Program
The following gives an example of the activation result:

l file type: application program region
l download date: same as the trial run result
l download version: consistent with the loaded file
l try-run type: reserved
l status: turns into "master", which means that the standby ANCP board turns into
the active one
D-19

l upgrade database: turns into "NO", which means the loading procedure
completes
l start address: start address of the program region
l file length: same as the trial run result
l try-run elapsed time: reserved
l try-run remained time: reserved
12. Input the command d-set-ncpstate back to switch the active ANCP board into the
standby status, see Figure D-16.
Figure D-16 Active/Standby ANCP Board Switching
13. Repeat Step 4 to Step 9 to load the programs to the original active ANCP board, which
has been switched into a standby one in Step 10.
Caution!
Be cautious that the slot No. of the board is 18 and therefore the slot No. in
corresponding commands should be 18 but not 19 during the loading procedure.
D.4 Downloading Database

To download the NE information and configuration information of an NE via the EMS
NetNumen T31, perform the following steps:
Steps
1. Switch the pins of the DIP switch S1 on the ANCP board and make sure that some
of them are on "ON" position while the others are not, so as to reset the ANCP board
and set it to the running status.
Note:
If an ANCP board has been set into the download status by means of restart or ring
trip button during the local initialization, it can be set into the running status by being
pulled out from corresponding slot and inserted into the slot again.
2. Set the IP address of the EMS computer, which should be in the same network
segment as the IP address of the NE where the ANCP board is installed.
D-20

3. Ping the NE on the EMS computer to check whether the communication between the
EMS and the NE is normal.
4. In the operation window of the EMS NetNumen T31, select the NE in the Topology
Management view and select Common Config > Data Sync.. The Data Sync. dialog
box is displayed.
5. Click Download tab in the Data Sync. dialog box.
6. Tick the check box(es) corresponding to the items to be downloaded and then click
Download button.
An alert box pops up to prompt you to confirm the download operation.
7. Click Yes to start the download of database.
After successful download, a message box pops up to prompt the success information.
Note:
It is unnecessary to download database when there is only logical program with new
version is loaded to the ANCP board during upgrade.
D.5 Verifying Application/Logical Program Version in

EMS
To check and verify the version of application/logical programs running in an ANCP board
on the EMS NetNumen T31, perform the following steps:
Steps
1. Double-click the NE to be checked in the Topology Management view. The Card
Management dialog box is displayed.
2. Right-click the ANCP board to be queried in the Card Management dialog box,
and then select the shortcut menu. The Card Run-time Version message box is
displayed.
The Card Run-time Version message box shows the version information of the
selected ANCP board, including PCB version, FPGA (logical program) version
and software (application program) version. The consistency between the version
information and the that of the actually-loaded programs indicates that the loaded
programs are normally running in the ANCP board.
D-21

D-22

Appendix E
Simple Commissioning
Table of Contents
Ÿ Overview ............................................................................................................... E-1
Ÿ Performing Simple Commissioning Through Telnet ................................................ E-3
Ÿ Performing Simple Commissioning Through the EMS ............................................ E-5
E.1 Overview
Simple commissioning is a remote initial configuration method for the equipment without
the necessity for getting to the site where the equipment is located.
Application Scenario
For the application scenario of simple commissioning, see Figure E-1.
Figure E-1 Application Scenario
NE1, NE2, NE3, and NE4 are existing equipment in the network. NE5 and NE6 are
equipment to be enabled. NE1 is connected with the EMS, so that NE5 and NE6 can
be enabled remotely from NE1.
Operating Principle
When a new device is added in the network, data can be transmitted in the underlayer
channel of the Data Communications Channel (DCC), as long as the new equipment and
existing equipment are connected by fibers, and share the same rate. In that case, users
E-1

can execute the underlayer DCC commands on the existing equipment to perform the
initial configuration for the new equipment, and manage the new equipment on the EMS.
Requirements
The following requirements should be satisfied during the simple commissioning:
l Both the access NEs and the NEs to be enabled support simple commissioning.
l EMS version: NetNumen U31 R22 V12.11.40 -B06 or later
l Equipment version: ENCP-ZXMPS385-PRG-V2.50R3P05.bin or later
l All NEs are powered on, and operating normally. The fiber connections are correct.
l The NEs to be enabled have already been created on the EMS. The NE addresses
have been planed.
Note:
In the ZXMP S385, only the ENCP board supports the simple commissioning function.
Operation Flow
For the operation flow of the simple commissioning, see Figure E-2.
E-2

Appendix E Simple Commissioning
Figure E-2 Simple Commissioning Flow
Simple Commissioning Modes

There are two operation modes for the simple commissioning:
l Telnet mode
l EMS mode
E.2 Performing Simple Commissioning Through Telnet

Through Telnet, users can enable the equipment remotely, and configure the IP address
and subnetwork mask of the equipment.
Prerequisite
l All NEs are powered on, and operating properly. The fiber connections are correct.
l The NEs to be commissioned have already been created on the EMS. The NE
information have been planed.
E-3

Context
For the network planning, see Figure E-3.
Figure E-3 Network Planning
Steps
1. Verify that the DCC on NE5 which is to be enabled is proper.
a. On the EMS computer, execute the telnet 192.168.2.18 command to log in to NE2.
b. Enter the user name (zte) and password (ecc). Press Enter. The prompt ZTE+>
is displayed.
c. Execute the ecc-cmd ckchan 5 1 command to check the DCC status of port 1 of
the board in slot 5.
l If the connection is properly, go to Step 2.
l If the connection is overtime, check the fiber connection or DCC configuration
and eliminate DCC faults.
2. Disable the OSPF protocol of NE2.
a. ZTE+>ecc-cmd enable-ospf 5 1 1 // Disable the OSPF protocol of port 1 of the
board in slot 5.
Note:
The last "1" in this command indicates that OSFP protocol will be disabled. If it is
a "0", it indicates that the OSPF protocol will be enabled.
b. ZTE+>ecc-cmd show-enable-osfp // query OSPF protocol status

After the configuration, execute this command to query OSPF status. If the flag
value of port 1 of the board in slot 5 is "1", the OSPF protocol is disabled. If the
flag value is "0", the OSPF protocol is enabled.
3. Reset NE2.
Enter the ZTE+>d-reboot command.
E-4

4. Configure IP address and subnetwork mask for NE5.

is displayed.
c. ZTE+>ecc-cmd set-ip 5 1 // Configure the IP address of the NE at peer end.
d. Set Peer NCP IP Address: 194.168.5.18 // Enter the IP address of NE5.
e. Set Peer NCP Net Mask: 255.255.255.0 // Enter the subnetwork mask of NE5.
f. Save[s]/Cannel[c]: s // Save the configuration.
g. ZTE+>ecc-cmd reboot 5 1 // Reset NE5 at peer end.
5. Enable the OSPF protocol of NE2.
The operations are the same as those in Step 2. The command is ZTE+>ecc-cmd
enable-ospf 5 1 0.
6. Reset NE2.
Execute the ZTE+>d-reboot command.
After NE2 is reset, users can manage NE5 on the EMS.
E.3 Performing Simple Commissioning Through the

EMS
Through the Data Communications Network (DCN) management function of the EMS, you
can enable the equipment remotely, and configure the IP address and subnetwork mask
of the equipment, and the domain where the equipment is located.
Prerequisite
l All NEs are powered on, and operating normally. The fiber connections are correct.
l The NEs to be commissioned have already been created on the EMS. The NE
information have been planed.
Context
For the network planning, see Figure E-4.
E-5

Figure E-4 Network Planning
Steps
1. Verify that the DCC on NE5 which is to be enabled is normal.
is displayed.
c. Execute the ecc-cmd ckchan 5 1 command to check the DCC status of port 1 of
the board in slot 5.
l If the connection is normal, jump to Step 2.
l If the connection is overtime, check the fiber connection or DCC configuration
to eliminate DCC faults.
2. Disable the OSPF protocol of NE2.
a. In the Topology Management view, right-click NE2, and select NE Manager from
the shortcut. The NE Manager dialog box is displayed.
b. In the NE Operation navigation tree, select System Config > DCN Management
> OSPF Enable Set. The OSPF Enable Set screen is displayed.
c. Select the corresponding board and port of NE2, and set OSPF Use State to
Disable.
For the OSPF configurations of NE2, refer to Table E-1.
Table E-1 OSPF Configuration of NE2
Parameter Configuration
Select Card OL16[0–1–5]
Please select port to set OL16[0–1–5]-STM16:1
E-6

OSPF Use State Disabled
d. Click Apply.
3. Reset NE2.
a. In the Topology Management view, double-click NE2. The Card Management
dialog box is displayed.
b. Right-click the ENCP board, and select Reset Board from the shortcut. The Reset
Board dialog box is displayed.
c. Set the reset mode to Soft Reset or Hard Reset. Click Apply.
4. Configure the IP address and subnetwork mask of NE5, and the domain where NE5
is located.
a. In the Topology Management view, right-click NE2, and select NE Manager from
the shortcut. The NE Manager dialog box is displayed.
b. In the NE Operation navigation tree, select System Config > DCN Management
> Device Easy Open. The Device Easy Open screen is displayed.
c. Select the corresponding board and port of NE2, and configure the IP address and
subnetwork mask of NE5, and the domain where NE5 is located.
For the simple commissioning configuration of NE2, refer to Table E-2.
Table E-2 Simple Commissioning Configuration of NE2
Neighbor IP Address Set 194.168.5.18
Mask Address 255.255.255.0
Neighbor Domain Set 194.0.0.0
d. Click Apply.
NE5 will be reset automatically.
5. Enable the OSPF protocol of NE2.
E-7

The operations are the same as those in Step 2. For the OSPF configuration of NE2,
refer to Table E-3.
Table E-3 OSPF Configuration of NE2
OSPF Use State Enabled
6. Reset NE2.
a. In the Topology view, double-click NE2. Board View is displayed.
b. Right-click the ENCP board, and select Board Reset from the shortcut. The
Board Reset dialog box is displayed.
c. Set reset mode to be Hard Rest or Soft Rest as required. Click Apply.
After NE2 is reset, users can manage NE5 on the EMS.
E-8

Appendix F
Board Replacement
Table of Contents
Ÿ Flowchart of Board Replacement............................................................................ F-1
Ÿ Board Replacement Procedure............................................................................... F-4
F.1 Flowchart of Board Replacement

Make sure to consider the following issues before replacing a board:
1. All the boards of ZXMP S385 are hot pluggable.
2. The function of the board in network and in an NE, and the effect on the service function
after it is unplugged.
3. The version of the spare board should be compatible with the versions of the current
equipment and EMS.
Figure F-1 shows the general flow of the board replacement operation. For the specific
replacement procedures of different boards, refer to the replacement steps of the
corresponding boards.
F-1

Figure F-1 General Flowchart of Board Replacement
The board replacement steps in the flowchart are described in detail as below:
1. Preparing a spare board
To ensure normal working of the system after replacement with the spare board, pay
attention to the following precautions:
a. Determine the spare board type according to the board to be replaced, and make
sure its model is consistent with the board to be replaced.
F-2

Appendix F Board Replacement
b. Check if the spare board has any apparent damage, and ensure that it works
normally.
c. Make sure that the PCB version and software version of the spare board are
compatible with the current NE and EMS.
d. When the board to be replaced is configured as warm backup mode (such
as the CSA board), ensure that the software and hardware versions of both
active/standby boards are completely consistent after replacement.
2. Preparing a label
The label is used to identify the board that has been unplugged during the replacement.
The label size is decided by the maintenance personnel. The label contents include the
site name, equipment name, fault cause, board name, handling process, the handling
person, and time.
3. Switching the service
For the board configured with service protection or backup, the service function
processed by it should be switched to the standby board, so that the service is not
interrupted by board unplugging.
While unplugging the board without service protection or backup, the service function
of this board would be interrupted.
4. Unplugging the board
Caution!
Board unplugging operation may interrupt the service, or even can stop the working of
the whole NE. Ensure to make enough preparations before the operation.
Before unplugging the board, unplug the fiber pigtail and cable connected to the board
panel.
5. Labeling the faulty board
Stick the prepared label onto the PCB of the faulty board unplugged.
6. Plugging the board
Plug and install the spare board, and restore connections of the fiber pigtails and
cables to the board.
7. Recovering the service function
Once the spare board is installed, its service function should be recovered
immediately. Check the board/equipment working status. Verify the normal working of
both the equipment and the service functions to ensure successful board replacement.
Otherwise, perform troubleshooting till the equipment work and service functions
become normal.
F-3

F.2 Board Replacement Procedure

F.2.1 Replacing NE Control Processor (NCP/ENCP/ANCP/ANCPB)
The NE control processor (NCP/ENCP/ANCP/ANCPB) supports 1+1 hot backup and is hot
pluggable. Its direct replacement does not affect the service but interrupts EMS monitoring
temporarily. After replacing the NCP/ENCP/ANCP/ANCPB board, you need to reconfigure
the data to make it consistent with the EMS data.
Context
Taking NCP board as an example, the board replacement procedure is described as
follows:
Steps
1. Prepare the spare board and label as described in the section "Flowchart of Board
Replacement". Ensure the compatibility among the BOOTROM and main program of
the NCP board, and the EMS software.
2. Unplug the board that needs to be replaced and paste the label.
3. Set DIP-switch of the spare NCP board to full ON state, and plug the board into the
sub-rack. Then execute the command ping 192.192.192.11 on the EMS computer
to check if it can ping the NE successfully.
4. Download the application and initial parameters via FTP, which are consistent with
the original NCP board. Refer to the Unitrans ZXMP S385 (V3.10) SDH Based
Multi-Service Node Equipment Maintenance Manual (Volume III) Troubleshootings
for the details of NCP program download.
5. Set the fourth digit of the DIP switch on the NCP board to OFF, and write the NE
configuration data into the NCP board with EMS software. Refer to the Unitrans
ZXMP S385 (V3.10) SDH Based Multi-Service Node Equipment Maintenance Manual
(Volume III) Troubleshootings for the details of configuration data download.
6. After replacement, select the NE that has replaced the NCP board in the operation
window at the EMS client. If the NCP time can be extracted, it indicates that the NCP
board is successfully replaced.
F.2.2 Replace the Cross-connect and Clock Board

(CSA/CSE/CSF/CSC)
The CSA/CSE/CSF/CSC board supports warm backup and is hot pluggable.
The CSA/CSE/CSF/CSC board replacement does not affect services when the
CSA/CSE/CSF/CSC is in the warm backup state. However, the CSA/CSE/CSF/CSC
board replacement will affect the transmission/receiving of the NE service when it
is not in the warm backup state. If the system configures an expansion subrack,
F-4

CSA/CSE/CSF/CSC board replacement in master subrack will affect the services of

expansion subrack.
Steps
1. Prepare the spare board and label it as described in the section "Flowchart of Board
Replacement". The two CSA/CSE/CSF/CSC boards of warm-backup configuration
must have consistent PCB versions.
2. If the CSA/CSE/CSF/CSC boards are configured in the warm backup mode,
switch the system clock to the other CSA/CSE/CSF/CSC board through EMS,
unplug the CSA/CSE/CSF/CSC board to be replaced, attach the label, plug the
spare board, and switch the system clock to the plugged CSA/CSE board. If the
CSA/CSE/CSF/CSC board is not configured in the warm backup mode, directly
unplug the CSA/CSE/CSF/CSC board, attach the label, and plug the spare board.
3. Confirm that the replacement is successful.

After replacement, the green NOM indicator on the CSA/CSE/CSF/CSC board flashes
regularly, and CKS1 (green) and CKS2 (green) are ON. It indicates that the service is
recovered and the board replacement is successful.
F.2.3 Replacing the Orderwire Board (OW)

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

To replace the optical line board, perform the following steps:
F-5

Context
The optical line board (OL1x4,OL1x8, OL4x2, OL4x4, OL16, OL16x4, OL16x8, OL64,
OL64x2, or OL64FEC/OL64FECx2) is hot pluggable.
l Its replacement will interrupt the service in case of unprotected networking.
l In protected networking if switched to protection mode, the service will not be inter-
rupted.
Note:
The board replacement when the multiplex section switching ring is configured is too
complex to describe. Conduct this kind of board replacement under the guidance of ZTE
maintenance engineers.
Steps
1. Board replacement without service protection configured
a. Prepare the spare board and label as described in the section "Flowchart of Board
Replacement".
b. Unplug the fiber pigtail connected to the optical interface, unplug the board to be
replaced, attach the label, plug the spare board, and connect the fiber pigtail.
c. Confirm that the replacement is successful.
After replacement, the green NOM indicator light on the board flashes slowly and
regularly; and the green TX and RX indicator lights, corresponding to the optical
interface for the original service, are constantly on. These indicate that the service
is normal and the board replacement is successful.
2. Board replacement with path protection configured
a. Prepare the spare board and label as described in the section "Flowchart of Board
Replacement".
b. Unplug the fiber pigtail connected to the optical interface, unplug the board to be
replaced, attach the label, plug the spare board, and connect the fiber pigtail.
c. Confirm that the replacement is successful.
regularly; and the green TX and RX indicator lights, corresponding to the optical
interface for the original service, are constantly on. These indicate that the service
is normal and the board replacement is successful.
F-6

F.2.5 Replacing the Line Processor (LP1x8)

The line processor (LP1x8) is hot pluggable. Its replacement will interrupt the service.
Steps
Replacement".
If the green indicator NOM on the board blinks slowly and regularly after replacement,
and the service performance is normal, it indicates the board is successfully replaced.
F.2.6 Replacing the Electrical Processor

The electrical processor (EPE1x63/EPE1Fx63/EPE1Zx63/EPT1x63/EP3x6) is hot
pluggable, and its replacement would interrupt the service.
Steps
Replacement".
F.2.7 Replacing the Optical E1 Tributary Board

The optical E1 tributary board (OPE1Z) is hot pluggable, and its replacement would
interrupt the service.
Steps
Replacement".
F-7

F.2.8 Replacing the Optical/Electrical Processor (OEL1x16)

The optical/electrical processor (OEL1x16) is hot pluggable, and its replacement would
interrupt the service.
Steps
Replacement".The OEL1x16 board provides optical interface and electrical interface,
so make sure to select the corresponding interface module according to the interface
type.
2. Unplug the fiber pigtail or cables connected on the front panel of board. Unplug the
board to be replaced, attach the label, plug the spare board, and connect the fiber
pigtail.

F.2.9 Replacing the Ethernet Board

The Ethernet board (TGE2B/SEC/SEE/SEEU/RSEB/TGSAx8/SEG4/SE10G2) is hot
pluggable. Replacing the Ethernet board would interrupt the Ethernet service.
Steps
Replacement".
pigtail.
regularly. It indicates that the board performance is normal, and the board replacement
is successful.
F.2.10 Replacing the ATM Processor (AP1x8)

The ATM processor (AP1x8) is hot pluggable, and its replacement would interrupt the
service.
F-8

Steps
Replacement".
pigtail.
regularly. It indicates that the board performance is normal, and the board replacement
is successful.
F.2.11 Replacing the Service Management Interface Board (SMI)

As a connection board, SMI board is installed in the expansion subrack to implement
the service access function and management access function for expansion subrack and
active subrack. The SMI board supports warm backup and is hot-pluggable. When the
SMI board is configured in the warm backup mode, its replacement would not affect the
service function. When the SMI board is not configured in the warm backup mode, its
replacement would affect transmission and reception of the NE service.
Steps
1. Prepare the spare board and label it as described in the section "Flowchart of
Board Replacement". The two SMI boards of warm-backup configuration must have
consistent PCB versions. Be aware about the compatibility of BOOTROM, major
program and EMS software.
2. If SMI board is configured as hot backup, switch the system clock to another SMI board
via EMS. Unplug the SMI board to be replaced, attach the label, plug the spare board,
and switch the system clock to the new SMI board. If SMI board is not configured as
hot backup, directly unplug the SMI board to be replaced, attach the label, and plug
the spare board.
3. Unplug the board that needs to be replaced and paste the label.

Result
regularly. It indicates that the service performance is normal, and the board replacement
is successful.
F-9

F-10

Appendix G
Board Indicator Status
Table of Contents
Ÿ Indicator Status When Boards Are Working ............................................................G-1
Ÿ Board Indicator Status During Power-On Initiation ................................................G-13
Ÿ Indicator Status of Boards When Waiting for Configuration ...................................G-15
Ÿ Indicator Status of Boards in a 1:N Protection Group ............................................G-16
G.1 Indicator Status When Boards Are Working

G.1.1 Indicator Status of the NCP/ENCP/ANCP Board
Table G-1 describes the relations between the NCP/ENCP/ANCP running status and the
indicator status.
Table G-1 Relations Between NCP/ENCP/ANCP Running Status and Indicator Status
Running Status NOM (green) ALM1 (yellow) ALM2 (red) MS (green)
Runs normally Flashes (once per Off Off -

second)
Major or minor alarm Flashes (once per On - -

occurs second)
Critical alarm occurs Flashes (once per - On -

second)
Active status Flashes (once per - - On

second)
• Flashing once a second means that an indicator is on for half second and then off for half second
periodically.
• The symbol "-" indicates an uncertain status.
Note:
The NCP/ENCP/ANCP board transfers running and monitoring information between NE

and EMS. The states of NCP/ENCP/ANCP board indicators indicate the running status of
the current NE. Alarms of the NCP/ENCP/ANCP board are generally caused by alarms
reported by other boards.
G-1

G.1.2 Indicator Status of the CSA/CSE/CSF/CSC Board

Table G-2 describes the relations between the CSA/CSE running status and the indicator
status.
Table G-2 Relations Between CSA/CSE Running Status and Indicator Status
Running Status Indicator
NOM ALM1 ALM2 CKS1 CKS2 MS TCS
Runs normally Flashes (once every Off Off - - - -

two seconds)
Major or minor alarm Flashes (once every On - - - - -

occurs two seconds)
Critical alarm occurs Flashes (once every - On - - - -

two seconds)
Clock in locked Flashes (once every - - On On - -

(normal tracing) two seconds)
mode
Clock in hold mode Flashes (once every - - On Off - -

two seconds)
Clock in fast-capture Flashes (once every - - Off On - -

mode two seconds)
Clock in free- Flashes (once every - - Off Off - -

oscillation mode two seconds)
Active CSA/CSE Flashes (once every - - - - On -

board two seconds)
Standby CSA/CSE Flashes (once every - - - - Off -

board two seconds)
TCS in-position Flashes (once every - - - - - On

two seconds)
TCS in-position and Flashes (once every - - - - - Flashes

working normally two seconds) (once
per
second)
• Flashing once every two seconds means that an indicator is on for one second and then off for one second periodic
ally. Flashing once a second means that an indicator is on for half second and then off for half second periodically.
• The ALM1 yellow indicator flashes only during board self-check and program download.
Table G-3 describes the relations between the CSF/CSC running status and the indicator
status.
G-2

Appendix G Board Indicator Status
Table G-3 Relations Between CSF/CSC Running Status and Indicator Status
NOM ALM1 ALM2 CKS1 CKS2 MS TCS RX TX
Runs normally Flashes (once Off Off - - - - - -

every two seconds)
Major or minor Flashes (once On - - - - - - -

alarm occurs every two seconds)
Critical alarm Flashes (once - On - - - - - -

occurs every two seconds)
Clock in locked Flashes (once - - On On - - - -

(normal tracing) every two seconds)
mode
Clock in hold Flashes (once - - On Off - - - -

mode every two seconds)
Clock in Flashes (once - - Off On - - - -

fast-capture every two seconds)
mode
Clock in Flashes (once - - Off Off - - - -

free-oscillation every two seconds)
mode
Active CSF/CSC Flashes (once - - - - On - - -

board every two seconds)
Standby Flashes (once - - - - Off - - -

CSF/CSC board every two seconds)
TCS in-position Flashes (once - - - - - On - -

every two seconds)
TCS in-position Flashes (once - - - - - Flashes - -

and working every two seconds) (once per
normally second)
Optical interface Flashes (once - - - - - - On On

works normally every two seconds)
Bit errors occur Flashes (once - - - - - - Flashes -

to corresponding every two seconds) (once per
optical interfaces second)
G-3

NOM ALM1 ALM2 CKS1 CKS2 MS TCS RX TX
The Flashes (once - - - - - - Off -

corresponding every two seconds)
optical interface
receives no
optical signal
(LOS)
Laser of the Flashes (once - - - - - - - Off

optical interface every two seconds)
laser is shut
down
G.1.3 Indicator Status of the OW Board

Table G-4 describes the relations between the OW board running status and the indicator
status.
Table G-4 Relations Between OW Board Running Status and Indicator Status
Running Status Indicator Status
NOM (green) ALM1 (yellow) ALM2 (red)
Runs normally Flashes (once per second) Off Off
Hooked off Flashes (once per second) On -
Alarm occurs Flashes (once per second) - On
periodically.
G.1.4 Indicator Status of the LP1x8 Board

Table G-5 describes the indicator status of the LP1x8 board.
Table G-5 Indicator Status of the LP1x8 Board
Operating Status NOM (green) ALM1 ALM2 RX (green) TX (green)

(yellow) (red)
Waits for configuration On Off Off Off Off
G-4

Operating Status NOM (green) ALM1 ALM2 RX (green) TX (green)

(yellow) (red)
Operates normally Flashes (once every two Off Off - -

seconds)
Board is in switching Flashes (once every two On - - -

status seconds)
Alarm occurs Flashes (once every two Off On - -

seconds)
Electrical interface Flashes (once every two - - On On

operates normally seconds)
Electrical interface has Flashes (once every two - - Flashes Flashes

bit error seconds) (once per (once per
second) second)
Electrical interface has Flashes (once every two - - Off Off

no signal seconds)
• Flashing once every two seconds means that an indicator is on for one second and then off for one
second periodically. Flashing once a second means that an indicator is on for half second and then
off for half second periodically.
• The symbol "-" indicates a particular status.
G.1.5 Indicator Status of the OAD Board

Table G-6 describes the indicator status of the OAD board.
Table G-6 Relations Between Indicators and the OAD Board Running Status
Running Status NOM (green) ALM1 (yellow) ALM2 (red)
Runs normally Flashes (once every two Off Off

seconds)
Alarm occurs Flashes (once every two - On

seconds)
• Flashing once every two seconds means that an indicator is on for 1 second and then off for 1 second
periodically.
G.1.6 Indicator Status of the OA Board

Table G-7 describes the relations between the OA board running status and the indicator
status.
G-5

Table G-7 Relations Between OA Running Status and Indicator Status
NOM (green) ALM1 ALM2 (red) TX (green) RX (green)

(yellow)
Runs normally Flashes (once every Off Off - -

two seconds)
Alarm occurs Flashes (once every - On - -

two seconds)
Optical interface works Flashes (once every - - On On

normally two seconds)
The corresponding Flashes (once every - - - Off

optical interface two seconds)
receives no optical
signal (LOS)
Laser of the optical Flashes (once every - - Off -

interface laser is shut two seconds)
down
• Flashing once every two seconds means that an indicator is on for 1 second and then off for 1 second periodically.
G.1.7 Indicator Status of the Electrical Tributary Board

Table G-8 describes the relations between the electrical tributary board
(EPE1x63/EPE1Fx63/EPE1Zx63/EPT1x63/EP3x6) running status and the indicator
status.
Table G-8 Relations Between Electrical Tributary Board Running Status and Indicator
Status
NOM (green) ALM1 (yellow) ALM2 (red)
Runs normally Flashes (once per Off Off

second)
Alarm occurs Flashes (once per - On

second)
periodically.
G-6

G.1.8 Indicator Status of OPE1Z Board

The relation between the indicator status and OPE1Z board working status is described in
Table G-9.
Table G-9 Relations between OPE1Z Board Running Status and Indicators' Status
Board NOM (Green) ALM1 ALM2 (Red) RX TX

Running (Yellow)
Status
Waiting for key ON OFF ON - -

configuration
Running Flashing (0.5 OFF OFF - -

normally Hz)
Alarms on Flashing (0.5 ON - - -

board Hz)
Optical Flashing (0.5 - ON - ON

interface Hz)
works
normally
Error code Flashing (0.5 - - Flashing (1 -

in optical Hz) Hz)
interface
LOS on optical Flashing (0.5 - - OFF -

interface Hz)
Optical Flashing (0.5 - - - OFF

interface Hz)
shutdown
Note:
l Flashing (0.5 Hz) means the indicator is ON for 1 second and is OFF for the other 1
second.
l Flashing (1 Hz) means the indicator is ON for 0.5 second and is OFF for the other 0.5
second.
l The ALM1 yellow indicator flashes only during board self-check and program
download.
l "-" indicates uncertain status.
l When the optical interface is not configured with services, the indicator status is
uncertain.
G-7

G.1.9 Indicator Status of the Optical Line Board

Table G-10 describes the relations between the optical line board (OL1x4, OL1x8, OL4x2,
OL4x4, OL16, OL16x4, OL16x8, OL64, OL64x2 and OL64FEC/OL64FECx2) running
status and the indicator status.
Table G-10 Relations Between Optical Line Board Running Status and Indicator Status
NOM (green) ALM1 ALM2 (red) TX (green) RX (green)

(yellow)
Waits for key Constantly on Off Off - -

configuration
Runs normally Flashes (once Off Off - -

every two
seconds)
Alarm occurs Flashes (once Off Constantly on - -

every two
seconds)
Optical interface Flashes (once - - Constantly on Constantly

works normally every two on
seconds)
Bit errors occur to Flashes (once - - Flashes (once per -

corresponding optical every two second)
interfaces seconds)
The corresponding Flashes (once - - Off -

optical interface every two
receives no optical seconds)
signal (LOS)
Laser of the optical Flashes (once - - - Off

interface laser is shut every two
down seconds)
G.1.10 Indicator Status of the Optical/Electrical Processor

Table G-11 describes the relations between the optical/electrical processor (OEL1x16)
running status and the indicator status.
G-8

Table G-11 Relations Between OEL1x16 Running Status and Indicator Status
Running Status NOM (green) ALM1 (yellow) ALM2 (red)
Waits for key configuration On Off Off
Runs normally Flashes (once every Off Off

two seconds)
Alarm occurs Flashes (once every Off On

two seconds)
Optical/electrical interface works Flashes (once every - -

normally two seconds)
Bit errors occur to corresponding Flashes (once every - -

optical/electrical interfaces two seconds)
Optical/electrical interface Flashes (once every - -

receives no optical/electrical two seconds)
signal (LOS)
Laser of the optical interface Flashes (once every - -

laser is shut down two seconds)
• Flashing once every two seconds means that an indicator is on for 1 second and then off for 1 second
periodically.
G.1.11 Indicator Status of the Ethernet Processor

Table G-12 describes the relations between the Ethernet processor (TGE2B/TGSAx8)
running status and the indicator status.
Table G-12 Relations Between TGE2B/TGSAx8 Running Status and Indicator Status
NOM (green) ALM1 ALM2 (red) LA (green) SD (green)

(yellow)
Runs normally Flashing (once per Not lit Not lit - -

second)
Alarm occurs Flashing (once per - Lit - -

second)
Optical interface is Flashing (once per - - Lit -

connected successfully second)
Optical interface receives Flashing (once per - - - Lit

optical signal second)
• Flashing once a second means that an indicator is on for half second and then Not lit for half second periodically.
G-9

Table G-13 describes the relations between the SEC/SEE/SEEU/RSEB board running
status and the indicator status.
Table G-13 Relations Between SEC/SEE/SEEU/RSEB Running Status and Indicator Status
NOM (green) ALM1 ALM2 LAn SPn LA SD

(yellow) (red) (green) (green) (green) (green)
Runs normally Flashing (once per Not lit Not lit - - - -

second)
Alarm occurs Flashing (once per - Lit - - - -

second)
FE interface is in Flashing (once per - - Lit - - -

Link status second)
FE interface is in Flashing (once per - - Flashing - - -

Active status second) (once per
second)
FE interface Flashing (once per - - - Lit - -

works at the rate second)
of 100 M
GE interface is Flashing (once per - - - - Lit Lit

in Link status second)
GE interface is Flashing (once per - - - - Flashing Lit

in Active status second) (once
per
second)
GE interface Flashing (once per - - - - - Lit

receives optical second)
signal
• Flashing once a second means that an indicator is on for half second and then Not lit for half second periodically.
Table G-14 describes the relations between the SE10G2 board running status and the
indicator status.
Table G-14 Relations Between the SE10G2 Board Operation Status and Indicator Status
Board NOM ALM1 ALM2 LA Indicator SD Indicator

Operation Indicator Indicator Indicator Status Status
Status Status Status Status
The board Flashing (once Not lit Not lit - -

is operating every two
properly seconds)
G-10

Board NOM ALM1 ALM2 LA Indicator SD Indicator

Operation Indicator Indicator Indicator Status Status
Status Status Status Status
The board has Flashing (once Lit Not lit - -

a minor alarm every two
seconds)
The board has Flashing (once Not lit Lit - -

a critical alarm every two
seconds)
The board is Flashing (once Flashing (once Flashing (once - -

powered on every two every two every two
seconds) seconds) seconds)
Waits for key Lit Not lit Not lit - -

configuration
The interface Flashing (once - - Lit Lit

is in link status every two
seconds)
The interface Flashing (once - - Flashing Lit

is in active every two (three times
status seconds) every two
seconds)
The optical Flashing (once - - - Lit

interface every two
receives seconds)
optical signals
• Flashing once every two seconds means that an indicator is lit for one second and then no lit for one
second periodically. Flashing 1.5 times per second means that an indicator is lit for 1/3 second and
then not lit for 1/3 second periodically.
Table G-15 describes the relations between the SEG4 board running status and the
indicator status.
Table G-15 Relations Between the SEG4 Board Operation Status and Indicator Status
Board NOM ALM1 ALM2 LA SP GLA GSD

Opera- Indicator Indicator Indicator Indicator Indicator Indicator Indicator
tion Sta- Status Status Status Status Status Status Status
tus
The Flashing Not lit Not lit - - - -

board is (once
operating every two
properly seconds)
G-11

Board NOM ALM1 ALM2 LA SP GLA GSD

Opera- Indicator Indicator Indicator Indicator Indicator Indicator Indicator
tion Sta- Status Status Status Status Status Status Status
tus
The board Flashing Lit Not lit - - - -

has a (once
minor every two
alarm seconds)
The board Flashing Not lit Lit - - - -

has a (once
critical every two
alarm seconds)
The FE Flashing - - Lit - - -

interface (once
is in link every two
status seconds)
The FE Flashing - - Flashing - - -

interface (once (three
is in active every two times
seconds)
Rate of Flashing - - - Lit - -

the FE (once
interface every two
is 100 M seconds)
The GE Flashing - - - - Lit -

interface (once
is in link every two
status seconds)
The GE Flashing - - - - Flashing -

interface (once (three
is in active every two times
seconds)
The GE Flashing - - - - - Lit

optical (once
interface every two
receives seconds)
optical
signals
• Flashing once every two seconds means that an indicator is lit for one second and then no lit for one
second periodically. Flashing 1.5 times per second means that an indicator is lit for 1/3 second and
then not lit for 1/3 second periodically.
G-12

G.1.12 Indicator Status of the ATM Processor (AP1x8)

Table G-16 describes the relations between the ATM processor (AP1x8) operating status
and the indicator status.
Table G-16 Relations Between AP1x8 Operating Status and Indicator Status
Operating Status Indicator Status
NOM (green) ALM1 (yellow) ALM2 (red) TX (green) RX (green)
Operates normally Flashes (once every two Off Off - -

seconds)
Alarm occurs Flashes (once every two - On - -

seconds)
Optical interface Flashes (once every two - - On On

operates normally seconds)
Optical interface has Flashes (once every two - - - Off

no optical signal seconds)
(LOS)
Laser of the optical Flashes (once every two - - Off -

interface laser is shut seconds)
down
• Flashing once every two seconds means that an indicator is on for 1 second and then off for 1 second periodically.
• The symbol "-" indicates a particular status.
G.2 Board Indicator Status During Power-On Initiation

G.2.1 Indicator Status of NCP/ENCP/ANCP/ANCPB Board During
Power-On Initiation
After power-on, the NCP/ENCP/ANCP/ANCPB board executes self-test. For
the relations between indicators (Green-NOM, Yellow-ALM1, Red-ALM2) and the
NCP/ENCP/ANCP/ANCPB board DOWNLOAD/RUN status, refer to Table G-17.
G-13

Table G-17 Indicator Status of NCP/ENCP/ANCP/ANCPB Board During Power-On

Initiation
Board Status DIP Status Indicator Status
DOWNLOAD All ON After power-on, three indicators flash quickly for 14 times,
and BOOT can normally execute self-test for memory.
If the self-test fails, the red indicator is reset after flashing
10 times. Otherwise, the yellow indicator and red indicator
will be ON.
RUN Not all ON not all 1. After power-on, three lights flash once, and test if the
OFF NCP/ENCP/ANCP/ANCPB board can be powered on
normally.
2. Three lights quickly flash, and self-test for memory
is executed.
3. NCP program will be decompressed and uploaded
to memory after the green indicator lights up for 4
seconds. After uploading, the green indicator goes
out.
4. The NOM indicator flashes twice per second after
three lights go out for about 60 seconds. If an alarm
occurs, the alarm indicator lights up.
• Flashing twice per second means that the indicator is ON for one second and is OFF for another one
second.
G.2.2 Indicator Status of Other Boards (Except NCP/ENCP/ANCP/A

NCPB) During Power-On and Initialization
For the relations between indicators and other board running status, refer to Table G-18.
Table G-18 Indicator Status of Other Boards During Power-On and Initialization
No. Board Status Indicator Status
1 Board power-on The red, yellow and green indicators light up for one second, and
then go out for another one second.
2 RAM self-test l The green, yellow and red lights flash (1.5 times/second), and
other lights are all OFF.
l If memory self-test fails, the red light flashes (1.5 times/second),
and other lights are all OFF.
G-14

No. Board Status Indicator Status
3 Loading l Green light flashes (5 times/second), and other lights are all OFF
application (if boards have application programs, load from local memory;
program if the programs need to be upgraded, download from the NCP
board).
l If program or FPGA file for uploading cannot be found, yellow
light flashes (5 times/second), and other lights are all OFF.
l If problems occur when writing Flash, red light flashes (5
times/second), and other lights are all OFF.
4 Downloading l The red and green lights flash (1.5 times/second), and other
FPGA program lights are all OFF.
and chip self-test l If FPGA downloading fails, the yellow light flashes (1.5
times/second), and other lights are all OFF.
l If self-test for chips fails, the red light flashes (1.5 times/second),
and other lights are all OFF.
l If detection for board address fails, the red and yellow lights flash
(1.5 times/second), and other lights are all OFF.
5 Critical l The red and yellow lights are OFF, while the green light is ON.
configuration l If no configuration information are received within 10 seconds,
report again.
l After receiving the commands for property configuration, the
yellow indicator lights up. If all the information are not completely
received within 30 seconds, repeat the process described above.
After completely receiving commands for critical configuration,
the yellow light goes out.
6 Preheat l The green light flashes (1.5 times/second), the red and yellow
lights are OFF, and no alarm status display on the other indicators
(such as the interface status indicator of optical line board).
l The process of preheat is 2 minutes. At the same time, process
the commands from EMS, and detect the alarms without
reporting, lighting up and switching. Wait for other boards to be
in the status of normal running.
7 Running normally The green light flashes twice per second. At the same time, detect
alarms, which are indicated by default.
G.3 Indicator Status of Boards When Waiting for

Configuration
When waiting for configuration, the NOM indicator light is ON, ALM1 and ALM2 indicator
lights are OFF. Board reports board type to EMS and waits for configuration information.
G-15

After configuration, the NOM indicator light flashes quickly for two minutes, and then it
periodically flashes once every two seconds, and the ALM2 indictor light indicates the
alarm status of board.
G.4 Indicator Status of Boards in a 1:N Protection

Group
l For the active/standby boards in a protection group, the yellow indicators light up
when protection switching occurs. The yellow indicators turn off after the protection
switching is cancelled.
l For interface bridge boards, the green indicator light is on after the boards are powered
on.
l For the electrical interface switching boards, the green indicator is on and the yellow
indicator is not lit after the boards are powered on. The yellow indicator lights up when
the switching occurs, and it turns off when the switching is cancelled.
G-16

Figures
Figure 4-1 Removing the Dustproof Front Panel ....................................................... 4-5
Figure 4-2 Pulling out the Dustproof Card ................................................................. 4-5
Figure 4-3 Removing the Door .................................................................................. 4-7
Figure 4-4 Installing the Filler Door ........................................................................... 4-8
Figure 4-5 Diagram of Boards in a Subrack ............................................................ 4-10
Figure 4-6 Plugging a Lower-Level Board ............................................................... 4-17
Figure 4-7 Unplugging a Lower-Level Board ........................................................... 4-18
Figure 4-8 Plugging an Upper-Level Board ............................................................. 4-19
Figure 4-9 Unplugging an Upper-Level Board ......................................................... 4-20
Figure 4-10 Plugging Fiber Pigtail ........................................................................... 4-21
Figure 4-11 Optical Launched Power Test............................................................... 4-22
Figure 5-1 Topology Management............................................................................. 5-3
Figure B-1 Network Topology....................................................................................B-6
Figure C-1 NCP PCB Board..................................................................................... C-2
Figure C-2 Local Upgrade Flowchart........................................................................ C-4
Figure C-3 Flowchart of Local Upgrade Preparations ............................................... C-5
Figure C-4 Erase the Database................................................................................ C-6
Figure C-5 Erase the Chip Area which Saves the Application Program .................... C-6
Figure C-6 Erase the Chip Area Which Saves the Logic Program ............................ C-7
Figure C-7 Configure the NE Related Information .................................................... C-7
Figure C-8 Local Download of NCP Application to NE ............................................. C-9
Figure C-9 Local Upgrade of NCP Application to NE...............................................C-11
Figure C-10 Version Information for Local Upgrade of Board Application ............... C-12
Figure C-11 Remote Upgrade Flowchart ................................................................ C-16
Figure C-12 Viewing NCP Board Information ......................................................... C-17
Figure C-13 Remote Upgrade of Application .......................................................... C-19
Figure C-14 Verifying the Upgraded Program......................................................... C-20
Figure C-15 Try Run of the Program ...................................................................... C-22
Figure C-16 Verifying the Program that Passed the Try Run .................................. C-23
Figure C-17 Activating the Program ....................................................................... C-25
Figure C-18 Verifying the Activated Program ......................................................... C-26
Figure C-19 Switching to the Standby NCP Board ................................................. C-28

Figure D-1 Initialization Flow.................................................................................... D-2

Figure D-2 Preparation Flow before Local Initialization............................................. D-3
Figure D-3 Preparation Flow Before Remote Initialization ........................................ D-9
Figure D-4 Successful Telnet Login.........................................................................D-11
Figure D-5 Upgrading Application Program (Remote) ............................................ D-12
Figure D-6 Trial Run .............................................................................................. D-13
Figure D-7 Checking Trial Run Result .................................................................... D-14
Figure D-8 Activating Loaded Program .................................................................. D-14
Figure D-9 Checking ANCP Board Information ...................................................... D-15
Figure D-10 Remote Loading Example of Application Program (Standby ANCP
Board).................................................................................................. D-16
Figure D-11 Remote Loading Example of Logical Program (Standby ANCP
Board).................................................................................................. D-17
Figure D-12 Checking Load Information (Remote) ................................................. D-17
Figure D-13 Trial Run Result (Remote) .................................................................. D-18
Figure D-14 Activating Loaded Program ................................................................ D-19
Figure D-15 Verifying Activation of Loaded Program .............................................. D-19
Figure D-16 Active/Standby ANCP Board Switching .............................................. D-20
Figure E-1 Application Scenario ...............................................................................E-1
Figure E-2 Simple Commissioning Flow ...................................................................E-3
Figure E-3 Network Planning ...................................................................................E-4
Figure E-4 Network Planning ....................................................................................E-6
Figure F-1 General Flowchart of Board Replacement ...............................................F-2
II

Tables
Table 1-1 Safety Signs and Descriptions ................................................................... 1-1
Table 2-1 Common Maintenance Tools ..................................................................... 2-1
Table 2-2 Common Maintenance Materials ............................................................... 2-3
Table 2-3 Common Instruments/Meters .................................................................... 2-4
Table 2-4 List of Routine Maintenance Items of ZXMP S385 ..................................... 2-6
Table 3-1 Density Limit of Hazardous Gases in the Equipment ................................. 3-1
Table 3-2 Temperature and Humidity Requirements.................................................. 3-2
Table 3-3 Typical Lightning Protection Classes of Power Supply ............................... 3-2
Table 3-4 Lightning Protection Requirements of ZXMP S385 Ports .......................... 3-3
Table 4-1 Meanings of the ZXMP S385 Cabinet Indicators........................................ 4-3
Table 4-2 Available Slots for Functional Boards of ZXMP S385............................... 4-10
Table 4-3 Available Slots for Optical/Electrical Line Boards and Service Boards of
ZXMP S385 ........................................................................................... 4-11
Table 4-4 Available Slots for E3/T3 Service Boards of ZXMP S385 ......................... 4-13
Table 4-5 Available Slots for E1/T1 Service Boards of ZXMP S385 ........................ 4-13
Table 4-6 Available Slots for Ethernet Service Boards of ZXMP S385 ..................... 4-14
Table 4-7 Description of SEE/SEEU/SEG4 Board Software/Hardware
Configuration ........................................................................................ 4-16
Table 5-1 Basic Data Description ............................................................................ 5-12
Table A-1 Half-day Maintenance Form ......................................................................A-1
Table A-2 Daily Maintenance Record ........................................................................A-3
Table A-3 Weekly Maintenance Record (Bi-weekly) ..................................................A-5
Table A-4 Login Password Change Record...............................................................A-6
Table B-1 Definitions of NE IP Address and Subnet Mask (FLSM) ............................B-1
Table B-2 Definitions of Area ID, NE ID, and Board ID (FLSM)..................................B-2
Table B-3 Meanings of Bytes in the NE IP Address (FLSM) ......................................B-2
Table B-4 NE IP Address Allocation (FLSM) .............................................................B-3
Table B-5 Definitions of NE IP Address and Subnet Mask (VLSM) ............................B-3
Table B-6 Definitions of Area ID, ECC Subnet ID, and NE ID (VLSM) .......................B-4
Table B-7 Area Definitions and NE IP Address Configurations ..................................B-7
Table B-8 NE IP Address Configurations of the NEs Allocated into Area 193 ............B-7
Table B-9 Definition of the EMS Host Address ..........................................................B-8
III

Table B-10 Route Configuration Commands in Windows 2000................................B-10

Table B-11 Route Configuration Command Lines in Unix ........................................B-10
Table B-12 Route Configuration Commands in Configuration File (HP-UX) ............. B-11
Table B-13 Route Configuration Commands in Configuration File (Solaris) .............B-12
Table C-1 Description of NCP Board States ............................................................. C-3
Table C-2 Inputs Principles of NE Related Parameters............................................. C-7
Table C-3 Parameters of the d-upgrade Command................................................. C-10
Table C-4 Parameters of the Command d-get-status................................................C-11
Table C-5 Descriptions of Parameters that Need to be Verified for Local Upgraded
Board Program Version......................................................................... C-12
Table C-6 Parameters in the Standby Area that Need to be Verified ...................... C-21
Table C-7 Parameters of the d-try Command......................................................... C-21
Table C-8 Parameters in the Original Standby Area that Need to be Verified after
the Try Run ........................................................................................... C-24
Table C-9 Parameters of the Command d-active .................................................... C-24
Table C-10 Descriptions of Parameters that Need to be Verified after
Activation .............................................................................................. C-26
Table E-1 OSPF Configuration of NE2 ....................................................................E-6
Table E-2 Simple Commissioning Configuration of NE2 ...........................................E-7
Table E-3 OSPF Configuration of NE2 ......................................................................E-8
Table G-1 Relations Between NCP/ENCP/ANCP Running Status and Indicator
Status ..................................................................................................... G-1
Table G-2 Relations Between CSA/CSE Running Status and Indicator Status........... G-2
Table G-3 Relations Between CSF/CSC Running Status and Indicator Status........... G-3
Table G-4 Relations Between OW Board Running Status and Indicator Status
............................................................................................................... G-4
Table G-5 Indicator Status of the LP1x8 Board......................................................... G-4
Table G-6 Relations Between Indicators and the OAD Board Running Status........... G-5
Table G-7 Relations Between OA Running Status and Indicator Status.................... G-6
Table G-8 Relations Between Electrical Tributary Board Running Status and
Indicator Status ....................................................................................... G-6
Table G-9 Relations between OPE1Z Board Running Status and Indicators'
Status ..................................................................................................... G-7
Table G-10 Relations Between Optical Line Board Running Status and Indicator
Status ..................................................................................................... G-8
Table G-11 Relations Between OEL1x16 Running Status and Indicator
Status ..................................................................................................... G-9
IV

Tables
Table G-12 Relations Between TGE2B/TGSAx8 Running Status and Indicator

Status ..................................................................................................... G-9
Table G-13 Relations Between SEC/SEE/SEEU/RSEB Running Status and
Indicator Status ..................................................................................... G-10
Table G-14 Relations Between the SE10G2 Board Operation Status and Indicator
Status .................................................................................................. G-10
Table G-15 Relations Between the SEG4 Board Operation Status and Indicator
Status ...................................................................................................G-11
Table G-16 Relations Between AP1x8 Operating Status and Indicator
Status ................................................................................................... G-13
Table G-17 Indicator Status of NCP/ENCP/ANCP/ANCPB Board During Power-On
Initiation ................................................................................................ G-14
Table G-18 Indicator Status of Other Boards During Power-On and
Initialization ........................................................................................... G-14

Tables
VI

Glossary
ASON
- Automatically Switched Optical Network
ATM
- Asynchronous Transfer Mode
CF
- Compact Flash
CIDR
- Classless Inter-Domain Routing
DCC
- Data Communications Channel
DIP
- Dependency-Inversion Principle
ECC
- Embedded Control Channel
EMS
- Element Management System
FLSM
- Full Length Subnetwork Mask
FTP
- File Transfer Protocol
IP
- Internet Protocol
LOS
- Loss of Signal
MAC
- Media Access Control
MODEM
- Modulator-Demodulator
NTP
- Network Time Protocol
OA
- Optical Amplifier
OSPF
- Open Shortest Path First
VII

PCB
- Printed Circuit Board
PDH
- Plesiochronous Digital Hierarchy
SDH
- Synchronous Digital Hierarchy
VLSM
- Variable Length Subnet Mask
VIII

SJ-20140214110341-004-Unitrans ZXMP S385 (V3.30) Maintenance Manual (Volume I) Routine Maintenance

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20140214110341-004-Unitrans ZXMP S385 (V3.30) Maintenance Manual (Volume I) Routine Maintenance

Uploaded by

Copyright:

Available Formats

ZXMP S385

SDH Based Multi-Service Node Equipment

Revision No. Revision Date Revision Reason

R1.1 2015-01-25 Added the SEEU board.

R1.0 2014-03-30 Fisrt edition

Serial Number: SJ-20140214110341-004

Publishing Date: 2015-01-25(R1.1)

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

Chapter 2 Maintenance Overview ............................................................. 2-1

Chapter 3 Environment Maintenance ....................................................... 3-1

Chapter 4 Equipment Maintenance Operations....................................... 4-1

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

Chapter 5 EMS Maintenance Operations ................................................. 5-1

Appendix A Maintenance Forms.............................................................. A-1

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

Appendix B NE Address Definition and Route Configuration .............. B-1

Appendix C Configuration Description of NCP/ENCP Agent

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

Appendix D Initialization and Upgrade of NE with ANCP/ANCPB

Appendix E Simple Commissioning .........................................................E-1

Appendix F Board Replacement ...............................................................F-1

Appendix G Board Indicator Status......................................................... G-1

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Safety Describes the safety precautions for equipment maintenance.

Chapter 2, Describes the basic information of equipment maintenance, including

Chapter 3, Describes the environment requirements in the equipment room, including

Chapter 4, Describes the basic operations for equipment maintenance.

Chapter 5, EMS Describes the basic operations for EMS maintenance.

Appendix A, Describes the forms for recording the routine maintenances.

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

Indicates an imminently hazardous situation. Failure to comply can result in death

Indicates a potentially hazardous situation. Failure to comply can result in serious

Indicates a potentially hazardous situation. Failure to comply can result in moderate

Provides additional information about a particular topic.

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

1.1 Safety Precautions

1.2 Safety Signs

Table 1-1 Safety Signs and Descriptions

Safety Sign Meaning

Call for notice

Caution against electrostatic discharge

Warn against electric shock

Warn against laser

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

2.1 Maintenance Classification

Routine maintenance involves checking the equipment operation status periodically,

2.2 Requirements of Tools and Instruments

Table 2-1 Common Maintenance Tools

Name Remark Function

Tape It is used for measurement.

SJ-20140214110341-004|2015-01-25(R1.1) ZTE Proprietary and Confidential

Name Remark Function

Screwdrivers It includes I size cross screwdriver, II size

Nippers It is used to nip wires, elements, and integrated

Adjustable wrench It is used to fix screws.

Diagonal pliers It is used to trim cable clips.

Wire stripper It is used to strip cable skins.

Wallpaper knife It is used to cut papers.