sjzl20060795-Unitrans+ZXONM+E300 (V3 (1) 17) +Operation+Manual PDF

ZXONM E300
Unified EMS/SNMS of Optical Network

Operation Manual
(Volume IV) Agent Configurations
Version 3.17
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright © 2005 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE
CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality
obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are
disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-
infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on
the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the
subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its
licensee, the user of this document shall not acquire any license to the subject matter herein.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support
or training are subject to change without notice.
Revision History
Date Revision No. Serial No. Description

2006/07/21 R1.0 sjzl20060795
ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to: (86) 755-26772236; or mail to Publications R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network Operation Manual
Name (Volume IV) Agent Configurations
Product Document
V3.17 R1.0
Version Revision Number
Equipment Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Your
evaluation of Accessibility:
this (Contents, Index, Headings, Numbering, Glossary)
documentation Good Fair Average Poor Bad N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good Fair Average Poor Bad N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Your Add more examples Add more/better quick reference aids
suggestions for Add more detail Improve the index
improvement
of this Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
About this Operation Manual ...................................................................xi

About the Manual Suite ......................................................................................... xi
Purpose of this Manual ......................................................................................... xii
Typographical Conventions...................................................................................xiii
Mouse Operation Conventions...............................................................................xiii
Safety Signs....................................................................................................... xiv
How to Get in Touch ............................................................................................ xv
Customer Support................................................................................................................xv
Documentation Support........................................................................................................xv
Chapter 1.................................................................................. 17
ZXMP S320/S360 Agent Configurations ............................................... 17
Smcc GDownloader Functions...............................................................................17
Card Storage Areas Overview ...............................................................................18
Card Storage Areas Division................................................................................................. 18
Program Areas States.......................................................................................................... 18
Smcc GDownloader Operations.............................................................................20

GDownloader Page.............................................................................................................. 20
Monitor Page....................................................................................................................... 28
NCP Working Status Switching..............................................................................29

Setting DIP Switch of ZXMP S320 ........................................................................................ 29
Setting DIP Switch of ZXMP S360 ........................................................................................ 29
Downloading Database via EMS Software ..............................................................29

Common Operation Flows of Smcc GDownloader ...................................................30
Local Download Flow ........................................................................................................... 30
Remote Upgrade Flow ......................................................................................................... 32
Operation Precautions ..........................................................................................33
Chapter 2.................................................................................. 35
Relationship between ZXMP S380/S390 Software Version and EMS .........................35
Description of BOOTROM Module ..........................................................................36
Functions ............................................................................................................................ 36
State Switching of NCP Card ................................................................................................ 36
Local Data Remake..............................................................................................37

Preparations........................................................................................................................ 37
Downloading Agent Application ............................................................................................ 40
Downloading Agent Configuration File................................................................................... 40
Starting Agent Application Program...................................................................................... 41
Local/Remote Online Download.............................................................................41

Preparations........................................................................................................................ 42
Download Procedure............................................................................................................ 42
Clearing NCP Database ........................................................................................43

Clearing NCP DB via EMS..................................................................................................... 43
Clearing NCP DB via Command Line..................................................................................... 43
Upgrading NE of V3.1...........................................................................................44
Chapter 3.................................................................................. 49
ZXMP S100 Agent Configurations.......................................................... 49
Functions of BOOTROM Module.............................................................................49
Card Storage Areas..............................................................................................50
Card Storage Area Division .................................................................................................. 50
Card Storage Area States .................................................................................................... 51
Download/Configuration Command Set .................................................................52

FTP Commands................................................................................................................... 52
Telnet Commands ............................................................................................................... 53
Download Process................................................................................................57
Local Download of Agent Program........................................................................................ 57
Local Modification of NE Configuration Information................................................................ 57
Local Upgrade of Agent Program.......................................................................................... 58
Remote Upgrade of Agent Program...................................................................................... 58
Precautions ......................................................................................................................... 59
Chapter 4.................................................................................. 61
ZXMP S385 Agent Configurations.......................................................... 61
Description of NCP Card .......................................................................................61
Description of BOOTROM Module on NCP Card .......................................................62
Functions of BOOTROM Module............................................................................................ 62
NCP Card State Switching.................................................................................................... 63
Local Upgrade .....................................................................................................64

Upgrade Preparations .......................................................................................................... 65
Clearing the Database ......................................................................................................... 69
Downloading the Application/Logic ....................................................................................... 69
Upgrading Application/Logic................................................................................................. 70
Verifying the Application/Logic ............................................................................................. 71
Upgrading Application/Logic for Standby NCP ....................................................................... 73
Downloading the Database .................................................................................................. 73
Verifying the Application/Logic Version in the EMS ................................................................ 74
Remote Upgrade .................................................................................................75

Confirming the Address of the Master NCP Card.................................................................... 77
Upgrading the Application/Logic ........................................................................................... 79
Verifying the Upgraded Application/Logic.............................................................................. 80
Try Run of the Application/Logic........................................................................................... 81
Verifying the Application/Logic after Try Run......................................................................... 82
Activating the Application/Logic............................................................................................ 84
Verifying the Activated Application/Logic............................................................................... 85
Upgrading the Application/Logic for Standby NCP.................................................................. 86
Verifying the Application/Logic Version in EMS ...................................................................... 87
Chapter 5.................................................................................. 89
Description of BOOTROM Module on NCP Card .......................................................89
Functions of BOOTROM Module............................................................................................ 89
NCP Card State Switching.................................................................................................... 89
Local Upgrade .....................................................................................................91

Clearing the Database ......................................................................................................... 94
Upgrading Application/Logic................................................................................................. 95
Verifying the Application/Logic ............................................................................................. 96
Verifying the Application/Logic Version in the EMS ................................................................ 98
Remote Upgrade .................................................................................................98

Downloading the Application/Logic ......................................................................................100
Upgrading the Application/Logic ..........................................................................................100
Verifying the Upgraded Application/Logic.............................................................................101
Try Run of the Application/Logic..........................................................................................102
Verifying the Application/Logic after Try Run........................................................................103
Activating the Application/Logic...........................................................................................104
Verifying the Activated Application/Logic..............................................................................104
Downloading the Database .................................................................................................105
Verifying the Application/Logic Version in EMS .....................................................................106
Chapter 6................................................................................107
ZXMP S200 Agent Configurations........................................................ 107
Description of BOOTROM Module ........................................................................ 107
Functions of BOOTROM Module...........................................................................................107
NCP Unit State Switching....................................................................................................108
Local Upgrade ................................................................................................... 109

Upgrade Preparations .........................................................................................................110
Clearing the Database ........................................................................................................112
Upgrading Application/Logic................................................................................................113
Verifying the Application/Logic ............................................................................................115
Verifying the Application/Logic Version in the EMS ...............................................................116
Remote Upgrade ............................................................................................... 117

Upgrade Preparations .........................................................................................................119
Upgrading the Application/Logic ..........................................................................................120
Verifying the Upgraded Application/Logic.............................................................................120
Try Run of the Application/Logic..........................................................................................121
Verifying the Application/Logic after Try Run........................................................................122
Activating the Application/Logic...........................................................................................123
Verifying the Activated Application/Logic..............................................................................124
Verifying the Application/Logic Version in EMS .....................................................................125
Precautions ....................................................................................................... 125
Chapter 7................................................................................127
WDM Equipment Agent Configurations............................................... 127
DIP Switch on NCP/NCPF Card............................................................................ 127
Use of TELNET and FTP Commands..................................................................... 128
Local NCP/NCPF Reconfiguration ......................................................................... 129
Preparing for Local Reconfiguration .....................................................................................130
Downloading the Agent/FPGA Programs (FTP) .....................................................................131
Modifying the Address of NCP/NCPF Card ............................................................................132
Burning the Agent/FPGA Programs (TELNET).......................................................................133
Running the Agent Program................................................................................................134
Local Download ................................................................................................. 134

Remote Online Download ................................................................................... 135
Preparing for the Remote Online Download..........................................................................136
Remote Online Download via Command Lines .....................................................................137
Remote Online Download via the ZXONM E300....................................................................142
Running the Agent Program................................................................................................142
Running Procedures of Blank NCP/NCPF Card....................................................... 143

ZXWM M900/ZXMP M800 ...................................................................................................143
ZXMP M600 .......................................................................................................................145
Appendix A .............................................................................147
SDH NE Address Definition and Route Configuration ......................... 147
Definition of NE IP Address ................................................................................. 147
FLSM Addressing................................................................................................................147
VLSM Addressing................................................................................................................149
Example of NE Addressing.................................................................................. 151

Address/Route Configuration of the EMS Host ...................................................... 153
EMS Host Address Configuration .........................................................................................153
Route Configuration............................................................................................................154
Route Configuration Commands..........................................................................................154
Appendix B .............................................................................159
DWDM NE Address Configurations ...................................................... 159
Definition of the NE IP Address ........................................................................... 159
Definition and Configuration Principle...................................................................................159
Configuration Example of the NE IP Address ........................................................................160
ECC Optical Interface Address Configuration ........................................................ 163

2 M Supervision System .....................................................................................................163
100 M Supervision System .................................................................................................170
Address/Route Configuration of the EMS Host ...................................................... 171

EMS Host Address Configuration .........................................................................................171
Route Configuration............................................................................................................172
Route Configuration Commands..........................................................................................173
Appendix C .............................................................................175
ZXMP M600 Address Configurations ................................................... 175
ECC Function of NCP Card .................................................................................. 175
Address Definition.............................................................................................. 176
Address of the NCP Card.....................................................................................................176
IP Address of the EMS Host.................................................................................................177
Typical Cases of Address Setting ......................................................................... 177

Cases with Default Gateway Disabled..................................................................................177
Cases with Default Gateway Enabled...................................................................................179
Appendix D ............................................................................183
Abbreviations ....................................................................................... 183
Figures.......................................................................................187
Tables ........................................................................................189
About this Operation Manual
About the Manual Suite

The Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network
(ZXONM E300 in short) is a set of NE/subnet layer network management
system based on Windows 2000 and Unix platforms. On the basis of
guaranteeing hardware functions of transmission equipment, it manages
and controls system NEs and regional networks, providing such functions
as system management, configuration management, performance
management, fault management, security management, and maintenance
management.
1. Management scope of ZXONM E300 (V3.17)
¾ SDH equipment: ZXMP S390, ZXMP S380, ZXMP S360, ZXMP S320,
ZXMP S330, ZXMP S385, ZXMP S100, ZXMP S200, ZXMP S325
¾ DWDM equipment: ZXWM-32 (V1.1), ZXWM M900, ZXMP M800
¾ CWDM equipment: ZXMP M600
¾ PCM equipment: ZXMP P210, ZXMP P220, ZXMP P230, ZXMP P240
2. Manual suite
Manual Name Function

Unitrans ZXONM E300 (V3.17) Unified
It describes the basic knowledge and
EMS/SNMS of Optical Network Installation
installation process of ZXONM E300.
Manual
Unitrans ZXONM E300 (V3.17) Unified It is an electrical manual, which describes
EMS/SNMS of Optical Network Interface the operations of ZXONM E300 client/
Manual server interfaces.
Unitrans ZXONM E300 (V3.17) Unified It includes several volumes which describe
EMS/SNMS of Optical Network Operation the operations commonly used in the
Manual ZXONM E300 in details.
Unitrans ZXONM E300 (V3.17) Unified It describes the installation and
EMS/SNMS of Optical Network LCT User’s configuration of the ZXONM E300 LCT
Manual (Local Craft/maintenance Terminal).
Unitrans ZXONM E300 (V3.17) Unified
It describes the maintenance knowledge of
EMS/SNMS of Optical Network Maintenance
ZXONM E300.
Manual
Confidential and Proprietary Information of ZTE CORPORATION xi

ZXONM E300 (V3.17) Operation Manual (Volume IV)
Purpose of this Manual

This manual is the Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of
Optical Network Operation Manual (Volume IV) Agent Configurations.
Chapter 1 ZXMP S320/S360 Agent Configurations, describes the download

and configurations of ZXMP S320/S360 Agent program.
Chapter 2 ZXMP S380/S390 Agent Configurations, describes the download

and configurations of ZXMP S380/S390 Agent program.
Chapter 3 ZXMP S100 Agent Configurations, describes the equipment

configurations, Agent program download and update of ZXMP S100.
Chapter 4 ZXMP S385 Agent Configurations, describes the upgrade

operations of ZXMP S385 Agent application/logic.
Chapter 5 ZXMP S330/S325 Agent Configurations, describes the upgrade

operations of ZXMP S330/S325 Agent application/logic.
Chapter 6 WDM Equipment Agent Configurations, describes the upgrade

operations of Agent application/logic of WDM equipment except ZXWM-32
(V1.1). The WDM equipment include ZXWM M900, ZXMP M800, and ZXMP
M600.
Appendix A SDH NE Address Definitions and Route Configurations,

describes the address definitions of SDH NEs, and route configurations of
EMS host. This appendix is applicable to all the SDH NEs.
Appendix B DWDM NE Address Configurations, describes the address

definitions of DWDM NEs, and route configurations of EMS host. This
appendix is applicable to DWDM NEs, including ZXWM M900 and ZXMP
M800.
Appendix C ZXMP M600 Address Configurations, describes the NE

definitions and EMS computer route configurations of ZXMP M600 NE in
networking.
Appendix D Abbreviations, gives the abbreviations and their corresponding

terms used in this manual for user’s reference.
xii Confidential and Proprietary Information of ZTE CORPORATION

Typographical Conventions
ZTE documents employ with the following typographical conventions.
TABLE 1 TYPOGRAPHICAL CONVENTIONS
Typeface Meaning
Italics References to other guides and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input fields,
radio button names, check boxes, drop-down lists,
dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens and
company name.
Constant width Text that you type, program code, files and directory
names, and function names.
[] Optional parameters
{} Mandatory parameters
| Select one of the parameters that are delimited by it
Note: Provides additional information about a certain

topic.
Checkpoint: Indicates that a particular step needs to

be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things

easier or more productive for the reader.
Mouse Operation Conventions

TABLE 2 MOUSE OPERATION CONVENTIONS
Typeface Meaning
Click Refers to clicking the primary mouse button (usually
the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button (usually
the right mouse button) once.
Drag Refers to pressing and holding a mouse button and
moving the mouse.
Confidential and Proprietary Information of ZTE CORPORATION xiii

Safety Signs
TABLE 3 S AFETY SIGNS
Safety Signs Meaning

Danger: Indicates an imminently hazardous situation,
which if not avoided, will result in death or serious
injury. This signal word should be limited to only
extreme situations.
Warning: Indicates a potentially hazardous situation,
which if not avoided, could result in death or serious
injury.
Caution: Indicates a potentially hazardous situation,
which if not avoided, could result in minor or moderate
injury. It may also be used to alert against unsafe
practices.
Erosion: Beware of erosion.
Electric shock: There is a risk of electric shock.
Electrostatic: The device may be sensitive to static

electricity.
Microwave: Beware of strong electromagnetic field.
Laser: Beware of strong laser beam.
No flammables: No flammables can be stored.
No touching: Do not touch.
No smoking: Smoking is forbidden.
xiv Confidential and Proprietary Information of ZTE CORPORATION

How to Get in Touch

The following sections provide information on how to obtain support for
the documentation and the software.
Customer Support
If you have problems, questions, comments, or suggestions regarding
your product, contact us by e-mail at support@zte.com.cn. You can also
call our customer support center at (86) 755 26771900 and (86) 800-
9830-9830.
Documentation Support
ZTE welcomes your comments and suggestions on the quality and
usefulness of this document. For further questions, comments, or
suggestions on the documentation, you can contact us by e-mail at
doc@zte.com.cn; or you can fax your comments and suggestions to (86)
755 26772236. You can also explore our website at
http://support.zte.com.cn, which contains various interesting subjects like
documentation, knowledge base, forum and service request.
Confidential and Proprietary Information of ZTE CORPORATION xv

xvi Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
ZXMP S320/S360 Agent

Configurations
This chapter describes how to download and configure the Agent program
of ZXMP S320 and ZXMP S360 equipment.
Note: The initial ZXMP S320/S360 equipment cannot connect to the EMS terminal
computer for network data configuration or network management until the Agent
application has been downloaded to the NCP card and the initial parameters have
been configured.
This chapter also describes the operations and precautions of Smcc

GDownloader Ver2.x software, which is a piece of download tool software
specially designed for ZXMP S320 and ZXMP S360.
Warning: As the operation of Smcc GDownloader Ver2.x may directly affect the
running security of the NE equipment, only the maintenance personnel can use this
software.
Smcc GDownloader Functions

1. Query the hardware information of the NCP card, including the card
type, database and application area.
2. Monitor the running of NCP program.
3. Upload the database and NCP program files.
4. Erase the chip of the database or main program.
5. Set the initial parameters of NCP.
6. Burn the NCP application into NCP main program chip.
7. Download the data files to NCP database chip.
8. Support both the local download and remote download.
Confidential and Proprietary Information of ZTE CORPORATION 17

¾ Local download is also known as offline download. It refers to the

case where the EMS host connects to the Qx interface of the NE
equipment that is in DOWNLOAD state through the network
interface for downloading and upgrading operations.
¾ Remote download is also known as online download. It refers to the
case where the EMS host remotely connects to the NE equipment
that is in normal working state through the ECC channel for
downloading and upgrading operations.
In the remote download mode, the Smcc GDownloader provides the
trial and start functions. It restricts buttons on its operation
interface according to the working state of Agent to ensure that
download is reliable and safe.
9. Supported equipment
The GDownloader must be used together with the new BOOTROM
version of the ZXMP S360 and ZXMP S320, and the Agent version
supporting the IP stack.
¾ For ZXMP S320, the NCP BOOTROM version should be 020807 or

above.
¾ For ZXMP S360, the NCP BOOTROM version should be 030910 or
above.
Only the ZXMP S320 with the main program version later than August
2002 can use Smcc GDownloader software.
Card Storage Areas Overview

This section describes the card storage area division and states of theses
areas.
Card Storage Areas Division

The NCP card uses the FLASH ROM chip to store programs and data. The
FLASH ROM chip includes the following storage areas: program area 1,
program area 2, database area, and data backup area. Program area 1
and program area 2 work in the active/standby mode.
Program Areas States

Program area 1 and program area 2 work in the active/standby mode.
They serve to store the main program of NCP. They have the following five
states:
1. Invalid: The storage area has abnormal program(s) or has no program

at all, and thus cannot be used any more.
2. Active: The storage area used (booted) when the NCP works normally.
3. Standby: Programs in the storage area are correct but are not used
(booted) currently.
18 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 - ZXMP S320/S360 Agent Configurations
4. Trial Start: The standby storage area has been set as active, but the
equipment is not reset and thus still runs the old active program.
5. Ongoing Trial: The standby storage area has been set as active, and
the equipment is reset and begins to load the new active program.
The relations between the program areas states are as follows:
1. When there is no program, both program area 1 and program area 2

are invalid.
2. Burn program V1 to program area 1 through the local download.
Program area 1 becomes active while program area 2 remains invalid
and the equipment can boot program V1 and work normally.
3. Write program V2 into program area 2 in remote download mode for
version upgrade. Program area 1 remains active while program area 2
becomes standby and the equipment still runs program V1.
4. Try program area 2. Now, program area 2 changes to the trial start
state and program area 1 changes to the standby state. The
equipment still runs program V1 since it has not been reset yet.
5. Reboot the equipment. Now the equipment detects that program area
1 is in the standby state while program area 2 in the trial start state,
so it will boot program V2 in program area 2 and change program area
2 to the ongoing trial state.
6. When program area 2 is in the ongoing trial state, execute the
activation command. Program area 2 changes from the ongoing trial
state to the active state, while program area 1 remains in the standby
state. This indicates that remote upgrade succeeds. Later, only
program V2 in program area 2 will be booted regardless of equipment
reset or power-off.
7. When program area 2 is in the ongoing trial state, if it is not activated
after three consecutive resets of the equipment, it indicates that the
new version program V2 cannot run on the equipment, in which case
the equipment will automatically change program area 2 to invalid
while changing the program area 1 to active. The equipment still runs
program V1 in program area 1 after reset, indicating that remote
upgrade fails.
8. When program area 2 is in the ongoing trial state, if it is not activated
upon expiry of the trial time, the equipment will automatically change
program area 2 to invalid while changing program area 1 to active. The
equipment still runs program V1 in program area 1 after reset,
indicating that remote upgrade fails.
Tip: If a storage area in ongoing trial state is not activated upon expiry of the trial
time, the reason may be that the program in the storage area can run normally
but the equipment disconnects from the EMS or that the operator does not execute
the activation command within the trial time.

Smcc GDownloader Operations

Execute the GDownLoad.exe program. The Smcc GDownloader program
interface pops up, as shown in Figure 1.
The Smcc GDownloader program interface includes the GDownloader page

and Monitor page.
GDownloader Page
Click GDownloader tab in the Smcc GDownloader program interface, the
GDownloader page appears. In the GDownloader page, users may erase,
upload and download the active program area and database area of NCP;
query and configure NE parameters; reset the NCP.
Figure 1 illustrates the GDownloader page of the Smcc GDownloader.

Before a connection to the NE is set up, only Connect button is active.
After the connection is set up, other buttons will be active.
FIGURE 1 GDOWNLOADER P AGE OF SMCC GDOWNLOADER SOFTWARE
The discriptions of buttons and options in the GDownloader page are as

follows:
1. DesIP text box:

Enter the IP address of the NE to be connected.
2.

This button is used to set up a connection with the current NE. The
user must perform this operation first when using the Smcc
GDownloader program. The user cannot perform other operations
unless a connection is set up.
Click this button, and the system will indicate that the NE is being
connected, as shown in Figure 2. After the program completes the
connection operation, the working status area indicates whether the
operation is successful.
FIGURE 2 SET UP A CONNECTION
3.
This button is used to disconnect the NCP of the current NE.
4. Card and Area Type area
Select the the storage area type of the NCP being operated currently
from the Area Type drop-down list box. Four options are available: DB
area, program area 1, program area 2, and data backup area.
5. File Selection area
Select the type of program or of data file to be written into the current
area from the File Type option buttons. And enter the specific file
location and file name in the File Name text box.
6. Running state area
Below the File Selection area is the working state area, which
displays the progress, completion state, and the returned results of the
Smcc GDownloader program’s operation of NCP.

7.
This button is used to erase the storage area selected in the Card and
Area Type area. It is not active until a connection is set up.
In the local download mode, all the storage areas selected may be
erased. In the remote download mode, the program areas in standby,
invalid, initial or abnormal state can be erased; while the program
areas in active, trial start or ongoing trial state and the database area
cannot be erased.
Click this button, and a warning box will pop up. Click Yes to confirm
the erase operation. Upon the erase completion, the working status
area will display whether the erase operation is successful.
8.
This button is used to download the specified file to the selected
storage area. It is active only when a connection to the NE is set up
and a file to be downloaded is selected.
In the local download mode, files can be downloaded to any selected
storage area. In the remote download mode, files can be downloaded
to the program areas in standby, invalid, initial or abnormal state; but
not to the program areas in active, trial start or ongoing trial state, or
the database area.
Click this button, and the working status area will indicate the
download progress. Upon the download completion, the working status
area will indicate whether the download operation is successful.
9.
This button is used to upload contents of a selected storage area to a
computer. It in active only when a connected is set up. Contents in the
database area and in the program areas in standby, active, trial start
or ongoing trial state can be uploaded; while the contents in the
program areas in invalid, initial or abnormal state cannot be uploaded.
Click this button, and a file selection window appears, asking the user
to specify the file name under which contents of the storage area will
be saved. During the upload, the working status area indicates the
upload progress. Upon the upload completion, the working status area
indicates whether the upload operation is successful.
10.
This button is used to set the storage area of standby state to trial
start state. It is active only in the remote download mode, and is
screened in the local download mode.
Click this button, and a dialog box asking for confirming the database
upgrade pops up, as shown in Figure 3.

FIGURE 3 DIALOG BOX FOR CONFIRMING THE DAT AB ASE UPGRADE
¾ If it is necessary to upgrade the database, click Yes button.

The Smcc GDownloader program sets the storage area of standby
state to trial start state, automatically backs up the configuration
data in the database area into the data backup area, and sets the
database upgrade flag in the program area. After the NCP reset, it
clears the configuration data in the database area. If it fails to clear
the configuration data, it can restore the configuration data in the
data backup area to the database area.
¾ If it is unnecessary to upgrade the database, click No button.

The Smcc GDownloader program sets the storage area of standby
state to trial start state but does not operate the database area.
11.
This button is used to set the storage area of standby or ongoing trial
state to active state. It is active only in the remote download mode,
and is screened in the local download mode.
12.
This button is used to configure network parameters of the current NE.
It is active only when a connection is set up.
Click this button, and a window for network parameter configurations
pops up, as shown in Figure 4.

FIGURE 4 WINDOW FOR NETWORK P AR AM ETER CONFIGURATIONS-NET P AR A CONFIG
Set network parameters of the current NE in the Net Para Config

window, including:
¾ IP address and subnet mask of the EMS terminal
¾ Initial IP address of NE and subnet mask
¾ Subnet ID
¾ Gateway NE IP
¾ NE MAC
After completing and confirming the settings, click OK button. The
configuration information is issued to the NCP database area. The
working status area indicates whether the operation is successful.
Caution: When configuring NE parameters, ensure that the configuration

information is consistent with that in the EMS.
13.
This button is used to configure system parameters of the current NE.
It is active only when a connection is set up.
Click this button, and a window for system parameter configurations
pops up, as shown in Figure 5.

FIGURE 5 WINDOW FOR SYSTEM P AR AMETER CONFIGURATIONS-SYSTEM P AR A CONFIG
Set system parameters of the current NE in the System Para Config

window, including:
¾ TryRun Time: The time restriction on trying a program after the
remote download. It ranges 60 sec – 14400 sec (4 hours).
¾ E3 Detect Period(m): Used to detect the communication link. If
no E3 detection packet is received in the E3 Detect Period, the
Smcc GDownloader program automatically disconnects the
communication. It ranges from one minute to 240 minutes.
¾ MTU Size(Byte): A configuration item reserved for the IP protocol
stack. It is used for performance adjustment of the IP protocol
stack, but is unused now.
After completing and confirming the settings, click OK button. The
configuration information is issued to the NCP database area. The
working status area indicates whether the operation is successful.
14.
This button is used to query the current system information. It is
active only when a connection is set up.
Click this button, and the System Information window pops up, as
shown in Figure 6. The window displays the running information of the
current NE, configuration information, and relevant information of the
database area and active program area.

FIGURE 6 SYSTEM INFORMATION WINDOW
15.
Click this button, and the working status area will display the current
status of program area 1 and program area 2.
16.
Click this button, and program area 1 and program area 2 will be
erased. This button is only active in the local download mode, and is
screened in the remote download mode.
17.
When the current area type selected is the database area, this button
appears as , which is used to back up the whole database
into the data backup area.
When the current area type selected is the data backup area, this
button appears as , which is used to restore data in the
data backup area to the database.

18.
This button is used to reset the NCP of the current NE and to
disconnect the current NE. This button is active only when a connection
is set up.
Click this button, and a window pops up for the user to confirm the
reset operation, as shown in Figure 7. Click OK button, and the
program resets and disconnects the current NE. Upon the reset
completion, the working status area indicates whether the operation is
successful.
FIGURE 7 RESET CONFIRMATION
Note: If the directory where GDownLoad.exe is located has a help file named
GDownloader.chm, the user can click F1 for help information of the Smcc
GDownloader while it is running.

Monitor Page
Click Monitor tab in the Smcc GDownloader program interface, the
Monitor page appears. In the Monitor page, the NCP program running
status of the current NE can be monitored.
Figure 8 illustrates the Monitor page of the Smcc GDownloader.
FIGURE 8 MONITOR P AGE OF THE SMCC GDOWNLOADER
The monitoring operation can be performed only when a connection with

the NE is set up. The prerequisite for monitoring the NCP running status is
that the NCP of the current NE is running in monitored status. Enter the IP
address of the NE NCP to be monitored in the Des IP text box. After a
connection is set up, the program running status of the NCP of the current
NE can be monitored.
The monitoring function is only used for debugging rather than

operation/maintenance, so it is not described in details here.

NCP Working Status Switching

The NCP can work in two states: DOWNLOAD state and normal working
state.
1. The DOWNLOAD state is used to locally download NCP applications and

to set initial parameters of the NCP.
2. The Normal working state is used to start the NCP applications. Only in
this state, can the NE service functions and the EMS monitoring can be
implemented.
Setting DIP Switch of ZXMP S320

DIP switch S3 relates to the NCP software, which is set as follows:
DOWNLOAD state: Bits 1 – 4 are all set to ON.

Normal working state: Not all bits 1 – 4 are set to ON.
Setting DIP Switch of ZXMP S360

1. DIP switch S2 relates to the NCP software of the NCP whose hardware
version is B000201. S2 is set as follows:
¾ DOWNLOAD state: Bits 1 – 8 are all set to ON.
¾ Normal working state: Bit 4 of the DIP switch is set to OFF, while
all the other bits are set to ON.
2. DIP switch S1 relates to the NCP software of the NCP whose hardware
version is B990800 or B991100. S1 is set as follows:
¾ DOWNLOAD state: Bits 1 – 8 are all set to ON.
¾ Normal working state: Bit 4 of the DIP switch is set to OFF, while
all the other bits are set to ON.
Downloading Database via EMS

Software
1. Start the ZXONM E300 EMS software.
2. In the EMS client operation window, select the NE from which the data
is to be downloaded, select the System > NCP Data Management >
DB Download menu, and then implement data download in the
Download DB dialog box.
3. If the data download succeeds, the NCP card will be automatically reset.
If the automatic reset does not occur, the user may reset the NCP card
manually.

4. When the NE self-check is finished, select the NE from which the data
is to be downloaded in the client operation window and click the
Maintenance > Time Management menu. Select the NCP time of
the current NE. If the NCP time is not zero, the database is successfully
downloaded.
Common Operation Flows of

Smcc GDownloader
This section describes the operation flows of the local download and
remote download.
Local Download Flow

Figure 9 illustrates the common operation flow of the Smcc GDownloader
in the local download mode.

FIGURE 9 LOCAL DOWNLO AD FLOW CHART OF SMCC GDOWNLOADER
Begin
Power on the NE so that the

NCP card can enter the
configuration status
Check the
equipment status
and the network
connection
ping 192.192.192.11 -t
Is it pinged No
through?
Yes
Run GdownLoad.exe to
connect the NE
Determine the operation to be performed
Download the
Download the
database main program
Set the current area as
the Database Area
Set the current area as the

Erase the database Program Area
Configure initial Select the file type

parameters for the NE
Download the selected file to Select the main program file

the Database Area
Disconnect the NE and the Download the selected file to

EMS the Program Area
Disconnect the NE and the

Restart or reset the NE so EMS
that the new NE IP address
can take effect
Restart or reset the NE so

that the NCP card can enter
the normal working status
Modify the EMS IP address to
be within the same section
with the NE IP address
Check the
No Can the NE IP address
equipment status
and the network be pinged through?
connection
Yes
Enter the ZXONM E300
Download the NE basic

databases
NCP card
automatically resets
No
Can the NCP time be
extracted?
Yes
End

Remote Upgrade Flow

Figure 10 illustrates the remote upgrade flow of the Smcc GDownloader in
the remote download mode.
FIGURE 10 REMOTE UPGRADE FLOWCHART OF SMCC GDOWNLOADER
Begin
Power on NE equipment and NCP card

enters normal start state
Check the equipment state and

network connection
ping NE IP address -t
Is it pinged through? No
Yes
Run GDownLoad.exe to connect the

NE equipment
Check the program area state and

decide the main program area
(suppose it is program area 1)
Select program area 2 (standby or

invalid program area)
Select the main program file of the new

version
Download the selected file to the

program area 2
No TryRun program area 2?
Yes
Set program area 2 as active Set program area 2 as trial start state
Reset NE equipment and load the new

Reset NE equipment and load the new
version main program
version main program
Started normally? Trial run succeeded? No
No
Yes
Set program area 2 as invalid and start
using program area 1
Yes
Set program area 2 as active
Reset NE equipment, upgrade

Upgrade failed Upgrade succeeded Reset NE equipment, upgrade failed
succeeded
End

Operation Precautions
1. Before configuration , check the chip model and main program version
of the NCP card. The NCP card can only use appropriate FLASH ROM
that matches the card.
2. Make sure that NCP card is started before starting GDdownLoad.exe on
the computer. Otherwise, the program may run abnormally.
3. If the connection fails, reset NCP card correctly and re-start
GdownLoad.exe.
4. If the connection fails for several times, but 192.192.192.11 can be
pinged through, reboot the computer, reset the NCP card correctly,
and re-start GDownLoad.exe.
5. Area type needs to be selected only for erasing, downloading or
uploading commands.
6. Confirm that correct file type (BIN or HEX) is selected for download.
7. Do not erase the program area unless necessary. Erase the database
before downloading the data, but the program area should not be
erased.
8. Only perform necessary operations. Otherwise NCP card may not run
normally.
9. For remote upgrade, Smcc GDownloader allows to directly start the
new version program without trial run. But users should guarantee the
correctness of the new version program; otherwise, connections cannot
be established with NE once the upgrade fails.


Chapter 2

Configurations
This chapter describes how to download and configure the Agent program
of ZXMP S380 and ZXMP S390 equipment.
been configured.
Relationship between ZXMP

S380/S390 Software Version and
EMS
The software version of the ZXMP S380 and ZXMP S390 equipment
includes V3.1 and V3.2. The relationship between software versions and
the EMS is described in Table 4.
TABLE 4 RELATIONSHIP BETWEEN ZXMP S380/S390 SOFTWARE VERSION AND EMS
Software Corresponding
Version Description Support from EMS
Version Sub-manager
The NCP program and the EMS software
are bound together.
The ZXONM E300 earlier
V3.1 The user must upgrade the NCP program smgr10g than V3.15 only supports
after upgrading the EMS. Otherwise, the ZXMP S380/S390 of V3.1.
EMS of the new version cannot manage the
NE normally.

Software Corresponding
Version Description Support from EMS
Version Sub-manager
The NCP program and the EMS software
are separated
The upgraded EMS can still manage the The ZXONM E300 of
original NE even if the NCP card program is V3.16R1 and later versions
V3.2 smgr10g_320
not upgraded together with the EMS. support ZXMP S380/S390 of
However, some new functions can be V3.2.
available only after the NCP program is
upgraded.
Note:
After ensuring that the EMS and the NCP program have been correctly
upgraded, the user must use the EMS of the new version to clear the NE database
and re-download the NE data. If the new EMS is of V3.16R1 or above, the user
must upgrade the software version of the ZXMP S380 and ZXMP S390 equipment
from V3.1 to V3.2. Refer to the section of Upgrading NE of V3.1 for details.
For the ZXONM E300 of the version above V3.16R1, the default version of the
newly created ZXMP S380 or ZXMP S390 NE is V3.2.
Description of BOOTROM
Module
This section briefly describes functions and state switching of the
BOOTROM module.
Functions
1. Prepare for running the Agent application.
i. Download (burn) the Agent application onto the electronic disk of
the NCP.
ii. Download the configuration file onto the electronic disk of the NCP.
2. Start the Agent application on the NCP.
3. Format the electronic disk.
4. Delete database and Agent application from NCP.
5. Read and configure system parameters (mainly the MAC address).
State Switching of NCP Card

The states of NCP card include the DOWNLOAD state and the Running
state, which are determined by the DIP switch on the NCP card. Table 5
illustrates the states of ZXMP S380/S390 NCP card.

TABLE 5 STATES OF ZXMP S380/S390 NCP CARD
NCP Card State Function DIP Switch

Download the Agent application and
DOWNLOAD All ON
configuration files
Not all ON and
Running Start the application on the NCP card
not all OFF
Local Data Remake

The local data remake means that the operator remake Agent data and
downloads the Agent program at the local place where the equipment is
located, and when the IP address of NCP card is the obliged one
(192.192.192.11).
Preparations
The flowchart of preparations for local data remake is shown in Figure 11.

FIGURE 11 FLOWCHART OF PREPAR ATIONS FOR LOCAL DAT A REM AKE (ZXMP
S380/S390)
Begin
Ensure that the chip is

correct and the
electronic disk is ready
Set the DIP switch of NCP

card to all ON (Download
state)
Ensure the NE and the

EMS are properly
connected
Set IP address for the

EMS
Succeeded Check the equipment

ping 192.192.192.11 status and the network
connection
Failed
No
Is it the first time to use the
electronic disk?
Yes
Format the electronic

disk
Set MAC address for

the NCP card
End
1. Ensure that the BOOTROM chip of the NCP card is correct. Any kind of
NCP card can only use the BOOTROM chip of its own.
2. Make sure that a right electronic disk is plugged on the NCP card.
3. Set all bits of the DIP switch on the NCP card to ON (DOWNLOAD
state). And the NE IP address will be 192.192.192.11 with the subnet
mask of 255.255.255.0.
4. Ensure correct network cable connection exists between the EMS
computer and the NCP.
5. Add the IP address and subnet mask to the EMS computer according to
the following rules.
IP address: 192.192.192.X (0 < X < 255, and X ≠ 11)

Subnet mask: 255.255.255.0

6. Execute the command p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS computer
to make sure that it is successfully connected with the NCP card.
7. If it is not the first time to use the electronic disk, go to step 8.
Otherwise, format the electronic disk by executing the following
commands:
i. Execute the t e l n e t 192.192.192.11 command on the EMS
computer.
ii. The system prompts to enter username and password. Leave them
empty and press the ENTER key directly.
iii. Under the prompt of Z T E + > , type the f o r m a t command to format

the electronic disk.
ZTE+> format
ZTE+> exit
8. Set the MAC address of NCP card by executing the following commands:
i. Execute the t e l n e t 192.192.192.11 command on the EMS
computer.
ii. The system prompts to enter the username and password. Leave
them empty and press the ENTER key directly.
iii. Under the prompt of Z T E + > , type the following command to set
MAC address of NCP card:
ZTE+>Setup
iv. After inputting the MAC address of NCP card, the system will show
the command line of [ S a v e [ s ] / C a n c e l [ c ] ] .
¾ Input s to save the setting.

¾ Input c to cancel the setting and keep the original NE MAC address.
Caution:
For NE of V3.1, after the executing the s e t u p command, only the m a c
a d d r e s s and N E i p a d d r e s s make sense among all the input information
prompted by the system. The N E ip a d d r e s s must be set to
1 9 2 . 1 9 2 . 1 9 2 . 1 1 . While for NE of V3.2, only the MAC address needs to be set
after the executing the s e t u p command.
The MAC address of an NE must be unique in a network, with the format of
00:D0:D0:xx:xx:xx.
v. Type the e x i t command, and the download preparations are

completed.

Downloading Agent Application

1. Execute the f t p 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command under the directory
containing the Agent application (ram.bin) on the EMS computer.
2. The system prompts to enter the username and password. Leave them
empty and directly press ENTER until the F T P > prompt appears.
3. Type the following commands under the F T P > prompt:
FTP> bin
FTP> put ram.bin RAM.BIN
FTP> bye
4. Agent application downloading is completed.
Downloading Agent Configuration File

1. Edit the SDH.CFG text file on the computer.
¾ The content template of the SDH.CFG file of V3.1 NE is:
192.1.1.18
255.255.255.0
1
4
5
1
1
¾ The content template of the SDH.CFG file of V3.2 NE can be

simplified as:
192.1.1.18
255.255.255.0
Table 6 describes the format of the SDH.CFG file.
TABLE 6 FORM AT OF THE SDH.CFG FILE
Line No. Content V3.1 Example V3.2 Example

1 NE address when the Agent application is 192.1.1.18 192.1.1.18
executed
2 Subnet mask 255.255.255.0 255.255.255.0
3 NE ID 4 -
4 NE rate (1=STM-1, 2=STM-4, 3=STM-16, 4 -
4=STM-64)
5 NE type (1=TM, 2=ADM, 3=REG, 5=ADM&REG) 5 -
6 Single or dual system (1 = single system, 2 = 1 -
dual systems)
Start ECC or not (1 = start, 0 = not start).
Generally, ECC should be started; otherwise,
7 1 -
management between NEs via optical fiber is
unavailable.

2. Execute the f t p 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command. Leave the username

and password empty, and press ENTER directly until the F T P > prompt
appears.
3. Type the following commands under the F T P > prompt:
FTP> ascii
FTP> put SDH.CFG
FTP> bye
4. The Agent configuration file is downloaded.
Caution: Once the NCP card starts running normally, this file allows no random
modification. If it is necessary to modify the file, delete the original database in
the NCP before the modification. For how to clear the NCP database, refer to the
section of Clearing NCP Database in this chapter.
Starting Agent Application Program

1. Make sure the Agent application and Agent configuration file are
downloaded correctly.
2. Set the DIP switch on NCP card so that its bits are not all ON (Normal
working state). Once the NCP card starts running normally, this NE will
have the newly configured IP address and application.
3. Change the IP address of EMS computer to be within the same network
section as the NE IP address. Execute the command p i n g N E I P to
check if the NE can be pinged through.
4. Clear the NCP database according to the section of Clearing NCP
Database in this chapter.
5. In the ZXONM E300 client operation window, select the NE, and click
the menu item of System -> NCP Data Management -> DB
Download to download the NE database.
6. The NCP card will reset automatically after download. In the EMS client
operation window, right-click the NE, and click the Time Management
menu item to extract the NCP time. If it succeeds, the local data
remake is completed.
Local/Remote Online Download

The local online download and the remote online download have the same
procedures. They mean that when the NE IP address is known, the
operator downloads new version of NCP program to the NE through ECC
channel. When upgrading the EMS, it is recommended to apply
local/remote online download if the NE IP address does not change.
This section uses one example to illustrate the online download procedures.

Preparations
1. Execute the p i n g N E I P command on the EMS terminal, to make sure
that the EMS terminal communicates normally with the NE and the ECC
channel of the NE whose program is to be upgraded is smooth.
2. Confirm that the downloaded NCP program version matches the
current EMS version, and ensure the correctness and consistency of
them.
Download Procedure
Suppose that the IP address of the NE is 188.92.3.18. The NCP remote
online download procedure is as follows:
1. Execute the p i n g 1 8 8 . 9 2 . 3 . 1 8 command on the EMS computer to

confirm that the NE can be successfully pinged through.
2. Execute the f t p 1 8 8 . 9 2 . 3 . 1 8 command and connect the EMS to the
NCP card. Enter the username and password as prompted. The
username is “zte”, and the password is “ecc”.
Caution: The user name and password must be lowercases.
3. Input the following commands under the f t p > prompt:

ftp> bin
//Set the file sending format as binary
ftp> rm RAM.OLD
//Delete the old NCP program created by previous upgrade.
ftp> put ram.bin RAM.NEW

//ram.bin is the NCP program used for upgrade on the
computer, and the RAM.NEW is the file name of the new
NCP program downloaded to the NCP card.
Caution:
RAM.NEW cannot be input as the running NCP program name RAM.BIN.
Otherwise, once the downloading process is interrupted, the NCP program will be
damaged and cannot be started.
This process lasts about three or four minutes. Only when this operation ends,
can the next operation be conducted. If failure or error occurs, it is necessary to
repeat this operation until the downloading succeeds.
ftp> rename RAM.BIN RAM.OLD

//Change the name of the old NCP program to RAM.OLD

ftp> rename RAM.NEW RAM.BIN

//Change the name of the newly downloaded NCP program as
NCP program RAM.BIN
ftp> bye
4. In the EMS client operation window, select this NE and select the
System -> NCP Data Management -> Clear_NCP DB menu to clear
the NCP database on line. Then the NCP will reset.
Caution: If there is no special requirement, the operator must clear NCP database
in order to remake NCP data. After clearing NCP database, there is no NE data in
the NCP. Therefore the NE power-off or ECC block during NCP running may cause
service interruption.
5. For the ZXONM E300 of V3.16R1 or above, use the DBMAN tool to
upgrade the ZXMP S380 and ZXMP S390 NEs of V3.1 to those of V3.2.
And the remote online download of the NE is completed without service
interruption. Refer to the section of Upgrading NE of V3.1 in this
chapter.
6. In the EMS client operation window, select this NE and select the
System -> NCP Data Management -> DB Download menu to
download all databases of the NE.
7. The NCP card will reset automatically after download. In the EMS client
operation window, right-click the NE, and click the Time Management
menu item to extract the NCP time. If it succeeds, the local data
remake is completed.
Clearing NCP Database

For the ZXMP S380 and ZXMP S390 equipment, the NCP database can be
cleared through the EMS or command lines.
Clearing NCP DB via EMS

If the NCP is running normally, clear the NCP DB through the following
operations:
In the EMS client operation window, select the NE and click the System -
> NCP Data Management -> Clear_NCP DB menu item.
Generally this method is recommended.
Clearing NCP DB via Command Line

Suppose the NE IP address is 188.92.3.18, execute the following
commands to clear the NCP database.
1. Execute the p i n g 1 8 8 . 9 2 . 3 . 1 8 command on the EMS computer to

ensure normal communication between the EMS and NE.

2. Execute the t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command on the EMS

computer to connect with the NCP card. Enter the username and
password as prompted. The username is “zte” and the password is
“ecc”.
Caution: The user name and password must be lowercases.
3. Under the Z T E + > prompt, type the following command to delete the
NCP database.
¾ For V3.1 NE
ZTE+>deldb
//Delete the database. Once executed, the NCP card
will reset automatically and the database will be
deleted
ZTE+>exit //Exit telnet
Note: If the NCP card does not reset automatically, you can execute the r e b o o t
command to force the NCP to reset.
¾ For V3.2 NE
ZTE+>rm –rf DbSys
//Delete the database. The prompt ZTE+> will appear
once the database is deleted.
ZTE+>d-reboot //Reboot the NCP card

ZTE+>exit //Exit telnet
Upgrading NE of V3.1
Note: If the new ZXONM E300 EMS is V3.16R1 or above, the user should upgrade
the NE software version from V3.1 to V3.2 after upgrading the NCP version of the
ZXMP S380 and ZXMP S390 NE.
Upgrade the software version using the DBMAN tool in the following
procedure.
1. Enter the EMS installation directory / d b m a n to open the d b m a n . b a t

file and enter the DBMAN interface, as shown in Figure 12

FIGURE 12 DBM AN INTERFACE
2. Type 7 to enter the Change Ne Software Version interface, as

shown in Figure 13.
FIGURE 13 CHANGE NE SOFTWARE VERSION INTERFACE
Selected Ne: All Nes in E300 database: Displays the NEs whose
versions are to be converted. For the first time to enter Figure 13, all
NEs are selected by default.
1. Select the Single Ne: Selects the designated NE.
2. Select All Nes : yes: Selects all ZXMP S380/S390 NEs. yes
indicates that the system selects all NEs for version conversion.
3. From 3.1 to 3.2: Modify the version of the selected NE from V3.1
to V3.2.
4. From 3.2 to 3.1: Modify the version of the selected NE from V3.2
to V3.1.
5. Help: Shows the help information.

6. Exit: Exit the Change Ne Software Version interface and return

to the dbman main interface.
3. Modify versions of all NEs.
i. In Figure 13, type 3 or 4 .
ii. If the modification succeeds, reboot the ZXONM E300 Server as

prompted by the system.
4. Modify the version of the designated NE.

i. In Figure 13, type 2 , and then the Change Ne Software Version
interface is as shown in Figure 14. Selected NE: becomes null, and
2. Select All Nes : yes is changed to 2. Select All Nes : no.
FIGURE 14 CHANGE NE SOFTWARE VERSION INTERFACE (SELECTING ALL NES IS NOT

ALLOWED)
ii. Type 1 to enter the SELECT NE interface shown in Figure 15.

Figure 15 lists NE names and ID of all the ZXMP S380 and ZXMP
S390 equipment.
FIGURE 15 SELECT NE INTERFACE

iii. Type the serial No. in front of the NE name to return to the
Change Ne Software Version interface. Suppose that the version
of the ZXMP S380 is to be modified, type 2 , and then the name of
the selected NE is displayed after Selected NE :, as shown in
Figure 16.
FIGURE 16 CHANGE NE SOFTWARE VERSION INTERFACE (CONVERTING THE VERSION OF

THE DESIGNATED NE)
iv. Type 3 .
v. If the version conversion succeeds, reboot the ZXONM E300 Server

as prompted by the system.


Chapter 3
ZXMP S100 Agent

Configurations
This chapter describes equipment configuration, Agent program

download/upgrade of ZXMP S100, including the format, function, and
operation procedure of each command.
Note: The initial ZXMP S100 equipment cannot connect to the EMS terminal
been configured.
Functions of BOOTROM Module

1. Prepare for running the Agent application.
¾ Download (burn) the application to FLASHROM.
¾ Download the configuration file to FLASHROM.
2. Start the card application.
3. Switch the NE working state.
The ZXMP S100 can work in three states: DOWNLOAD state, Running
state, and Debugging state, which are controlled by the DIP switch
marked as S3 on the NCP card. Table 7 describes the three working
states.
TABLE 7 WORKING STATES OF ZXMP S100 NCP CARD
Working State
Function DIP Switch (S3)
of NCP Card
This state is used for local download of Agent application and
configuration file.
DOWNLOAD state First, power off the equipment. Then, set the DIP switch S3 All ON
on the NCP card to all ON. Power on the equipment. Thus
the system enters the DOWNLOAD state, and the NE IP
address is forced to be 192.192.192.11 with the subnet mask

Working State
Function DIP Switch (S3)
of NCP Card
of 255.255.255.0.
This state is used for starting the card application. In this
state, the NE can perform its service function and the EMS
can monitor the NE. In addition, the remote
download/upgrade/configuration can be performed. Not all ON and not
Running state
all OFF
First, power off the equipment. Then, set the DIP switch S3
on the NCP card to not all ON and not all OFF. Power on the
equipment. Thus the system enters the Running state.
This state is used for debugging by the development staff.
The equipment cannot run normally in this state
Debugging state First, power off the equipment. Then, set the DIP switch S3 All OFF
on the NCP card to all OFF. Power on the equipment. Thus
the system enters the Debugging state.
4. Remote download and local download.

¾ Remote download refers to the case that the EMS host remotely
connects to the NE equipment in normal state through the ECC
channel for download and upgrade operations.
¾ Local download refers to the case that the EMS host connects to
the Qx interface of the NE equipment in DOWNLOAD state through
the network interface for download and upgrade operations.
5. Other functions:
¾ Delete the configuration database and the card application.
¾ Read and set the NE parameters.
Card Storage Areas

This section describes the card storage area division as well as states of
theses areas.
Card Storage Area Division

The card of the ZXMP S100 has a FLASH chip as its storage area, including
program area and database area. Division of the storage area is listed in
Table 8
TABLE 8 DIVISION OF CARD STORAGE AREA
Card Storage Area Relations between Storage Areas

Program area Agent program area 1
In mutually active/standby mode
Agent program area 2
FPGA1 In mutually active/standby mode

Chapter 3 - ZXMP S100 Agent Configurations
Card Storage Area Relations between Storage Areas

FPGA2
Active database area
Database area In mutually active/standby mode
Standby database area
Card Storage Area States

Storage areas of the ZXMP S100 work in active/standby mode and have
five working states.
1. Invalid: The storage area has abnormal program(s) or has no program

at all, and thus cannot be used any more.
2. Active: The storage area that is used (booted) during normal running.
3. Standby: Programs in the storage area are correct but are not used
(booted) currently.
4. Trial Start: The standby storage area has been set as active, but the
equipment is not reset and thus still runs the old active program.
5. Ongoing Trial: The standby storage area has been set as active, and
the equipment is reset and begins to load the new active program.
Relations of states of the storage areas are described as follows:
1. Suppose there are two storage areas, numbered 1 and 2 respectively.

Both of them are invalid when they have no program.
2. Burn the program V1 into the storage area 1 through the local
download, and then the storage area 1 is active and the storage area 2
is invalid. The program V1 can be booted and run normally.
3. When remote download is required for version upgrade, write the
program V2 into the storage area 2. Then the storage area 1 is active
and the storage area 2 is standby. The equipment runs the V1 program.
4. Try the program in the storage area 2. Change the state of the
program V2 in the storage area 2 to trial start, and change the
program V1 in the storage area 1 to standby. The NE still runs the V1
program because the equipment is not reset.
5. Reboot the equipment. The NE finds that storage area 1 is standby
while storage area 2 is trial start, and thus it will boot the program in
storage area 2 and change its state to ongoing trial.
6. When storage area 2 is in the ongoing trial state, execute the
activation command. Program V2 in storage area 2 changes from the
ongoing trial state to the active state, while program V1 in storage
area 1 remains in the standby state. This indicates that remote
upgrade succeeds. Later, only program V2 in storage area 2 will be
booted regardless of equipment reset or power-off.
7. During the ongoing trial, if the program V2 of the new version has not
been activated when the equipment has been reset for three times, the
program V2 of the new version cannot run on the NE. The NCP
automatically changes the state of the program V2 in the storage area

2 to invalid, and changes the standby program V1 in the storage area

1 to active. The NE still runs program V1 in storage area 1 after reset,
and thus remote upgrade fails.
8. During the ongoing trial, if the equipment is reset for no more than
three times but exceeds the longest trial period before program V2 is
activated, the program may have run normally, but the NE loosed
connection with the EMS. The state of the program V2 in the storage
area 2 is automatically changed to invalid, and the standby program
V1 in the storage area 1 is changed to active. The NE still runs
program V1 in storage area 1 after reset, and thus remote upgrade
fails.
Download/Configuration
Command Set
The download/configuration commands of the ZXMP S100 comprise two
parts: FTP commands and Telnet commands.
FTP Commands
The FTP commands serve to upload and download program files.
1. Create an FTP connection

Suppose the IP address of the NE is 192.192.192.11.
ftp 192.192.192.11 <Enter>
User: <Enter>
Password: <Enter>
2. Select the file to be transfer through FTP as binary format.

bin <Enter>
3. Download the file from the EMS host to the NE’s storage area.
put path\filename <Enter>
p a t h and f i l e n a m e indicate the path and name of the file to be

downloaded on the EMS host.
4. Upload a file from the NE’s storage area to the EMS host.
get obj-filename <Enter>
o b j - f i l e n a m e is name of the file to be uploaded from the destination

NE to the default directory of Windows on the EMS host.
5. Terminate the FTP connection and exit
bye <Enter>
Or
quit <Enter>
6. Help command

help <Enter>
The user can view all the available FTP commands one by one.
Telnet Commands
Telnet commands serve for interactive operations with the NE NCP: Query,
delete and modify configurations; and upgrade programs.
1. Create a Telnet connection

¾ In the case of local operation, suppose the IP address of the NE is
192.192.192.11.
telnet 192.192.192.11 <Enter>
¾ In the case of remote operation, suppose the IP address of the NE

is 192.192.192.18. Input the username “zte” and password “ecc” to
establish a Telnet connection.
telnet 192.192.192.11 <Enter>
User: zte <Enter>
Password: ecc <Enter>
2. Read states of the current NE’s storage areas

d-get-status <Enter>
Upon execution of this command, the state information about the

Agent program areas, FPGAs and database area will be returned.
3. Upgrade NE’s storage area
d-upgrade -p pFileName -f fFileName -d dFileName
<Enter>
Each parameter is described in Table 9
TABLE 9 P ARAMETER DESCRIPTION FOR UPGRADING AN NE’S STORAGE ARE A
Parameter Description
-p Upgrade the Agent program area.
pFileName File used to upgrade the Agent program area.
-f Upgrade the FPGA area.
fFileName File used to upgrade the FPGA area.
-d Update the database area.
dFileName File used to upgrade the database area.
¾ One or more of -p, -f, and –d can be selected. Each of them, if

selected, shall be followed by a filename. To upgrade programs in
both the Agent program area and FPGA area, the command format
is: d - u p g r a d e –p prg.bin –f fpga.bin < E n t e r > ; To
upgrade programs in the Agent program area only, the command
format is: d - u p g r a d e – p p r g . b i n < E n t e r > .
¾ To upgrade the Agent program area, the program shall ask the
user whether to upgrade the database. If the user answer “YES”, all

database contents except the network configuration information

shall be erased. If both – p and – d options are selected, the user
must answer “NO”.
¾ During the remote upgrade of NE, if its two program areas are
invalid, the contents of the upgraded program will be burned into
storage area 1 after this command is executed; if one storage area
is in active or trial start or ongoing trial state, the contents of the
upgraded program will be burned to the other storage area, and
the program will be set as standby and will not turn to active until
ongoing trial and activation operations are conducted.
¾ During the local upgrade of NE, the newly-written program storage
area will be immediately set as active while the original active
program area is set as invalid after this command is executed.
¾ Upon execution of this command, information about the file
upgrade progress and the result (successful or not) will be returned.
4. Upload the file from NE’s storage area to EMS host
d-upload -p |-f| -d [-m | -s] <Enter>
Each parameter is described in Table 10.
TABLE 10 UPLOAD P AR AMETER DESCRIPTION
-p Upload programs in the Agent program area.
-f Upload programs in the FPGA area.
-d Upload programs in the database area.
-m Get programs in the active area. The command will get

programs in the active area by default.
-s Get programs in the standby area.
This command can upload only one file each time. Upon receipt of this
command, the NE uploads programs in the corresponding storage area
and reports the progress information and the operation result.
Upon execution of this command, a “temp” directory will be
automatically created under the root directory for storing the uploaded
programs. The root directory will be searched for the “temp” directory
when uploading programs, so this command must be executed under
the root directory.
5. Set a storage area as trial running
d-try -p | -f | -a [time] <Enter>

TABLE 11 P ARAMETER DESCRIPTION FOR SETTING A STORAGE ARE A AS TRIAL RUNNING
-p Try programs in the standby Agent program area.
-f Try programs in the standby FPGA.
Try programs in the standby Agent program area and
-a the standby FPGA at the same time. It shouldl be used
cautiously.
time In trial time; the system default value will be used by

default.
Upon receipt of this command, the NE sets the corresponding storage

area as trial start and reports the progress and result. Upon trial
success, execute the d - r e b o o t command to reset the NE, so that it
will switch to programs in the storage area under trial running. d-
r e b o o t command is only valid for remote download.
6. Activate storage area

d-active -p | -f | -a <Enter>
Each parameter is described in Table 12
TABLE 12 P ARAMETER DESCRIPTION FOR ACTIVATING A STORAGE AREA
-p Activate programs in the standby Agent program area.
-f Activate programs in the standby FPGA.
-a Activate programs in the standby Agent program area and the

standby FPGA at the same time. It should be used cautiously.
Upon receipt of this command, the NE directly activates the storage

area if it is in the ongoing trial state. If no area is under trial running,
the program asks the user whether to activate the standby area. After
execution of the command, the NE will report the progress and
operation result. This command is only valid for remote download.
7. Reboot NE
d-reboot <Enter>
Upon receipt of the command, the NE will be rebooted.

Use this command after modifying the state of Agent program area or
FPGA. If a storage area changes from standby to trial start, its state
will turn to ongoing trial after the reboot; if programs in the storage
area are activated, the equipment will switch to the activated storage
area after the reboot.
8. Erase storage area
d-erase -p1 | -p2 | -d1 | -d2 | -f1| -f2 <Enter>

TABLE 13 P ARAMETER DESCRIPTION FOR ERASING A STORAGE ARE A
p1 Erase Agent program area 1.
p2 Erase Agent program area 2.
d1 Erase the active database area.
d2 Erase the standby database area.
f1 Erase the FPGA1.
f2 Erase the FPGA2.
This command is used to erase the contents in the Agent program

areas, database areas or FPGAs. When erasing the Agent program
areas or FPGAs, they will be erased completely and set as invalid state;
when erasing the database areas, all of their contents including the
network configuration information will be erased. This command is only
valid for local download.
9. Modify NE configuration information
d-cfgnet [-s] <Enter>
Where - s means view but not modify the NE configuration information.

If the d - c f g n e t command is executed without - s , the NE
configuration information is modified in interactive mode. The
interactive process is as follows after the NE receives this command:
i. Show the old NE configuration information.
ii Prompt the user to input the new configuration information of the

NE, including the IP address and subnet mask of the EMS terminal;
initial IP address, subnet mask, gateway IP address, and physical
address of NE. If one item needs no modification, press ENTER to
use the original value; otherwise, input new configuration
information.
iii Ask the user whether to save the NE configuration information

upon confirmation of complete NE configuration information. If the
user answers “YES”, the information will be saved in the
corresponding area.
10. H e l p command
help [CommandName] <Enter>
C o m m a n d N a m e is the name of the command that the user want to query.
H e l p command is in the same format as standard Telnet commands.

The command without the C o m m a n d N a m e parameter displays all
commands names that Telnet supports, while that with a specific
C o m m a n d N a m e shows the format of that command and meaning of each
parameter.
11. Exit the Telnet connection
exit <Enter>

Download Process
This section respectively describes the process of local Agent program
download, local modification of NE configuration information, and
local/remote Agent program upgrade; and the upgrade precautions.
Local Download of Agent Program

1. Confirm that the NE card has been properly inserted with the
BOOTROM chip and the database configuration chip (no program exists
in the storage areas now).
2. Set all bits of the DIP switch S3 on NCP card to “ON” for the equipment
to enter the DOWNLOAD state.
3. Confirm that a proper network connection has been set up between the
EMS computer and the NE equipment.
4. Abide by the following rules to add 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
5. Execute the p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command on the EMS computer
to ensure the connection with the NCP.
6. Execute the f t p 192.192.192.11 command to set up an FTP
connection.
7. Execute the following commands at the F T P > prompt character.
FTP> bin
FTP> put path\filename
FTP> bye
8. Download completed.
Local Modification of NE Configuration

Information
BOOTROM chip and the database configuration chip.
2. Set all bits of the DIP switch S3 on the card to “ON” for the equipment
the EMS computer.
Subnet mask: 255.255.255.0


6. Execute the t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command to set up a Telnet
connection.
7. Execute the d - c f g n e t command. According to the program prompts,
input the IP address and subnet mask of the EMS terminal; initial IP
address, subnet mask, gateway IP address and physical address of the
NE one by one.
8. After the user input the above information, the program will ask
whether to save it. Select “YES” to save the modified configuration
information.
9. Execute the e x i t command to exit the telnet connection.
Local Upgrade of Agent Program

BOOTROM chip and the database configuration chip (with the Agent
program in the storage area now).
2. Set all bits of the DIP switch S3 on the card to “ON” for the equipment
the EMS computer.
Subnet mask: 255.255.255.0
6. Execute the t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 command to set up a Telnet
connection.
7. Execute the d - u p g r a d e - p p r g . b i n command. The program will ask
whether to upgrade the database. Select “NO” to write the new version
Agent program (prg.bin) into the Agent program area and set it as
active.
9. Set the bits of the DIP switch S3 on the card to not all “OFF” or not all
“ON”, so that the equipment will enter the normal state. If the
equipment starts the new version Agent program normally, it indicates
that upgrade succeeds.
Remote Upgrade of Agent Program

1. Suppose the IP address of the NE is 192.192.192.18, the old version
V1 of the Agent program is stored in Agent program area 1 and the
new version is V2 with file name as “prg.bin”.

2. Ensure the NE equipment is in the state of normal running already.

Execute the p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 8 command on the EMS computer
3. Execute the t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 8 command to establish a Telnet
connection, with the user name as “zte” and the password as “ecc”.
4. Execute the d - u p g r a d e - p p r g . b i n command and answer “NO”
when the program asks whether to upgrade the database. Write the
new version Agent program V2 (prg.bin) into Agent program area 2
and set Agent program area 2 as standby.
5. Execute the d - t r y – p command to set Agent program area 1 as
standby while Agent program area 2 as trial start.
6. Execute the d - r e b o o t command to reboot the NE. The NE boots the
Agent program V2 and sets Agent program area 2 as ongoing trial.
7. The following three cases may occur when executing the d - a c t i v e
command for activation during ongoing trial period:
¾ Agent program area 2 is set as active and the remote upgrade is
successful.
¾ When Agent program area 2 is not activated after three
consecutive reboots, it indicates that the new version program V2
cannot run on the NE, in which case the NE will automatically
change program V2 in storage area 2 to be invalid while changing
the standby program in storage area 1 to be active. The NE still
runs program V1 in storage area 1 after reboot, and thus the
remote upgrade fails.
¾ The NE reboots no more than three times, but the NE is not
activated after the maximum trial time is exceeded. It is possible
that the program is running normally, but the NE lost connection
with the EMS. The NE automatically changes the program V2 in
storage area 2 to be invalid and changes the standby program V1
in storage area 1 to be active. The NE still runs the program V1 in
storage area 1 after reboot, and thus remote upgrade fails.
Precautions
1. The user name and password must be lowercases when using Telnet
commands.
2. During upgrade, the upgraded program may be directly activated to be
active without trial run, but the user must ensure the program is
correct.


Chapter 4
ZXMP S385 Agent

Configurations
This chapter describes the Agent application/logic download operations of

ZXMP S385.
application and logic has been downloaded to the NCP card and the initial
parameters have been configured.
Description of NCP Card

1. ZXMP S385 equipment reserves two slots for NCP card (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 cards can be
installed simultaneously to implement the 1+1 protection for NCP cards.
Note: The ZXONM E300 of V3.16R2 or above support the 1+1 protection for NCP
cards.
2. NCP card has an Ethernet interface (debugging interface) as shown in

Figure 17. The Ethernet interface is used to connect the NCP card
working in the Download status. QxI card also has an Ethernet
interface (EMS Qx interface) which is used to connect the NCP card
working in the master status. Refer to the section of NCP Card State
Switching in this chapter for the work states of NCP card.

FIGURE 17 NCP PCB BOARD
7 6 5 4 3 2 1
S1
Motherboard side
1. Card running indicator NOM 2. Major/minor alarm indicator ALM1

3. Critical alarm indicator ALM2 4. Dip switch S1
5. Ethernet interface (debugging interface) 6. Master status indicator MS
7. Reset button RST
3. If two NCP cards are installed simultaneously, only one NCP card is the
master card and the other is the standby card at any moment during
normal running. Only the Qx, S, and ECC interfaces of the master NCP
card can communicate normally; while those interfaces of the standby
NCP card are closed. The Ethernet port of QxI card only communicates
with the master card, i.e. it can only connect one NCP card (the master
NCP card) at any moment.
Module on NCP Card
This section describes the functions and state switching of BOOTROM
module on NCP card.

1. Prepare for running the Agent program.
¾ Download (burn) the Agent program to the CF card on NCP.
¾ Download the configuration files to the CF card on NCP.
2. Start the Agent program on NCP card.
3. Other functions
¾ Format the CF card.
¾ Delete the NCP database and the Agent program.
¾ Read and set the system parameters (mainly the MAC address).

NCP Card State Switching

The functional states of NCP card include DOWNLOAD state and Running
state which are determined by the DIP switch marked as S1 on NCP card.
The DOWNLOAD state is used to download the NCP application and
configuration parameters, while the Running state is used to start the NCP
application program. The settings of the DIP switch digits are described as
follows:
1. Set the DIP switch to all ON, start or reset the NCP card, it will enter
the DOWNLOAD state. In this state, the default value of NCP card IP
address is 192.192.192.11. Communication between the EMS and the
NCP card can only be established by connecting the EMS with the
Ethernet interface of the NCP card.
2. Set the DIP switch set to non-all ON and non-all OFF, start or reset the
NCP card, then it will enter the Running state. In this state, connect
the EMS with the Qx interface of QxI card to establish communication
between the EMS and the master NCP card.

Local Upgrade
Local upgrade refers to the procedure of upgrading application/logic in the
DOWNLOAD state. The local upgrade flowchart is shown in Figure 18.
FIGURE 18 LOCAL UPGRADE FLOWCHART OF ZXMP S385
Begin
Prepare for upgrade
Use telnet Clear the database

method
Use ftp Download the

method application/logic
Upgrade the
application/logic
Use telnet
method
Verify the
application/logic
Upgrade the
application/logic of the
standby NCP board
Download the database
Performed in
the EMS
Verify the
application/logic version
in the EMS
End

Upgrade Preparations
The flowchart of local upgrade preparations is shown in Figure 19.
FIGURE 19 FLOWCHART OF LOCAL UPGRADE PREPAR ATIONS
Begin
Confirm the BOOTROM

chip is correct and the CF
card is ready
Set the DIP switch of NCP

board to all ON (Download
state)
Confirm the network cable

between EMS and NE NCP
board is correctly connected
Set the EMS IP address
Disconnected Check the equipment

connection status
Connected
No
Is it the first time to use the CF
card?
Yes
No
Is it necessary to reconfigure the
Format the CF card NE information?
Yes
Clear the NCP database
Configure the NE
information
Reset the NCP board
End

Each step is described below:
1. Make sure the correct BOOTROM chip is plugged on NCP card, as each
type of NCP card can only use its own BOOTROM chip.
2. Make sure the CF card is correctly plugged on NCP.
3. Set the DIP switch on NCP card to all ON state (DOWNLOAD state).
And the NE IP address is 192.192.192.11 with the subnet mask of
255.255.255.0
4. Connect the EMS with the Ethernet interface of the NCP card, and
confirm the Ethernet cable connection between the EMS computer and
NCP card is correct.
5. Set the IP address and subnet mask of the EMS computer according to
the following rules:
¾ IP address: 192.192.192.X (0 < X < 255 and X ≠ 11)
¾ Subnet mask: 255.255.255.0
to confirm that the EMS computer can connect to NCP.
7. If the CF card is not used for the first time, and it is unnecessary to
completely clear the NE data or reconfigure the NE, the upgrade
preparations are completed.
8. If the CF card is not used for the first time, and it is necessary to
completely clear the NE data and reconfigure the NE, follow the steps
below:
¾ Execute the command t e l n e t 192.192.192.11 on the EMS
computer.
¾ The system prompts to enter user name and password which are
both empty, press ENTER directly.
¾ Input the command d - e r a s e – d 1 under the prompt Z T E + > to
erase the database, as shown in Figure 20.
FIGURE 20 ERASE THE DATABASE
¾ Input the commands d - e r a s e – p 1 and d - e r a s e – p 2 under the

prompt Z T E + > to erase the chip area which saves the application
program, as shown in Figure 21.

FIGURE 21 ERASE THE CHIP ARE A WHICH S AVES THE APPLICATION PROGRAM
¾ Input the commands d - e r a s e – f 1 and d - e r a s e – f 2 under the

prompt Z T E + > to erase the chip area which saves the logic
FIGURE 22 ERASE THE CHIP ARE A WHICH S AVES THE LOGIC PROGRAM
¾ Input the command d - c f g n e t under the prompt Z T E + > to

configure the NE related information, as shown in Figure 23. The
input principles of each item are listed in Table 14.
FIGURE 23 CONFIGURE THE NE RELATED INFORM ATION

TABLE 14 INPUT PRINCIPLES OF NE RELATED P AR AMETERS
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: Must input each parameter. Press ENTER directly if there is no

modification. Cannot quit in the middle of the procedure, otherwise the NCP card
will stay in the infinite waiting state.
¾ Input the command d - r e b o o t to reboot the NCP card, and the NE

information configuration will take effect. Upgrade preparations are
completed.
9. If the CF card is used for the first time, perform the following
operations to format the CF card, clear the NCP database, and
reconfigure the NE information:
¾ Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS
computer.
¾ The system prompts to enter the user name and password which
are both empty. Press ENTER directly.
¾ Input the command f o r m a t under the prompt z t e + > to format the
CF card, as shown in Figure 24.
FIGURE 24 FORM AT THE CF CARD

erase the database, as shown in Figure 20.
¾ Input the commands d - e r a s e – p 1 and d - e r a s e – p 2 under the
prompt Z T E + > to erase the chip area which saves the application
¾ Input the commands d - e r a s e – f 1 and d - e r a s e – f 2 under the
prompt Z T E + > to erase the chip area which saves the logic
configure the NE related information, as shown in Figure 23. The
input principles of each item are listed in Table 14.

¾ Reset the NCP card to make the NE configuration take effect. Input
the command d - c f g n e t – s to query the NE related information.
Clearing the Database

Tip: If the NE data has been cleared during the upgrade preparation, this step can
be skipped.
Perform the following operations to clear the NCP database:
1. Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS computer.

2. The system prompts to enter the user name and password which are
both empty. Press ENTER directly until the prompt Z T E + > appears.
3. Input the command d - e r a s e – d 1 to erase the database.
Downloading the Application/Logic

1. Execute the command f t p 1 9 2 . 1 9 2 . 1 9 2 . 1 1 under the directory
containing the Agent application or logic on the computer. When the
system prompts to input the username and password, press ENTER
until the prompt f t p > appears.
2. Execute the following commands under the f t p > prompt, to download
card application/logic and check if the downloaded file is correct.
ftp> bin
//Set the file transfer mode to binary mode.
ftp> put file_name_of_the_application/logic
//Download the card application/logic. When the f t p > prompt appears again,
it indicates that the file transfer has completed.
ftp> ls –l
//Check if the downloaded file size is consistent with the local file. If not
consistent, re-download the file.
ftp> bye
//Exit ftp connection.
Caution: The application/logic of NCP card must be transferred to the NCP card in
the binary mode
Suppose the Agent program N C P - Z X M P S 3 8 5 - P R G - V 1 . 0 1 R 1 P 0 5 . B I N is

downloaded from the computer to the NE, the operations are shown in Figure
25.

FIGURE 25 LOCAL DOWNLOAD OF NCP APPLICATION TO NE
Upgrading Application/Logic
It is to upgrade the application/logic on CF card into the application/logic
area.
1. Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 . When the system

prompts to input the username and password, press ENTER directly
until the prompt Z T E + > appears.
2. Execute the command d - u p g r a d e under the Z T E + > prompt, to

upgrade the card application/logic into the application/logic area
respectively.
<Command Format>
d-upgrade Subrack-NO. Slot-NO. Card-CPU-NO. {-p

Application-file-name\-f Logic-file-name}
<Parameter Description>
The parameters of the command are described in Table 15.
TABLE 15 P ARAMETERS OF THE COMM AND D-UPGRADE
Parameter Name Parameter Value
Subrack-NO. 1 or 2, generally 1.
The slot number of the card. It is an integer ranging from 1 to
Slot-NO. 19. It is 18 or 19 for the NCP card.
Card-CPU-NO. Integer ranging from 1 to 3, generally 1.

The parameter for NCP application delivery, followed by the card
-p application file name.
The parameter for NCP logic delivery, followed by the card logic
-f file name.

For example, to upgrade the program in Figure 25 of section Downloading

the Application/Logic into the application/logic area, perform the operation
shown in Figure 26.
FI G U R E 2 6 LOC AL U P G R AD E O F N C P AP P L I C AT I O N T O N E
Verifying the Application/Logic

prompts to enter the username and password, press ENTER directly
2. Execute the command d - g e t - s t a t u s under the Z T E + > prompt, to

verify if the application/logic version is normal.
If the version is abnormal, it is necessary to re-perform the operations

described in the section Downloading the Application/Logic and in the
section Upgrading the Application/Logic until the version queried is
normal.
<Command Format>
d-get-status Subrack-NO. Slot-NO. Card-CPU-NO.
TABLE 16 P ARAMETERS OF THE COMM AND D-GET-STATUS
Slot-NO. 19. It is 18 or 19 for the NCP card.

For example, to verify the version of the application in Figure 25 of the

section Downloading the Application/Logic, the results are shown in Figure
27. The parameters need to be verified are described in Table 17.
FIGURE 27 VERSION INFORMATION FOR LOCAL UPGRADE OF CARD APPLICATION
TABLE 17 DESCRIPTIONS OF P AR AMETERS THAT NEED TO BE VERIFIED FOR LOCAL

UPGRADED CARD PROGRAM VERSION
Parameter Name Parameter Description Remarks

p r o g r a m indicates the application
file type -
area
Should be consistent with
download date File downloaded time the actual time when the
file is downloaded
download
version File version downloaded the actual downloaded file
version
reserved indicates that this
try-run type -
parameter is reserved
master indicates the master
status -
status
upgrade N O indicates the database is not
-
database upgraded
0 x 0 A 0 0 0 0 0 0 indicates the initial
start address -
address of the program
file length The size of the downloaded file the actual downloaded file
size
try-run r e s e r v e d indicates that this
-
elapsed time parameter is reserved
-
remained time parameter is reserved

Upgrading Application/Logic for Standby

NCP
Note: If only one NCP card is configured, skip this step.
1. Re-perform the steps described in section Upgrade Preparations and in

the section Verifying the Application/Logic, to upgrade the standby NCP
card.
2. The IP address, subnet mask, and MAC address of the standby NCP
card must be the same as those of the master NCP card.
Downloading the Database

1. Set the DIP switches of both NCP cards to non-all ON and also non-all
OFF state (Running state).
2. Reset the NCP card and it enters the Running state.
3. Set the IP address of EMS computer to be within the same network
section as the NE IP address.
4. Execute the command p i n g N E - I P to confirm if the NE can be pinged
through.
5. In the EMS client operation window, select the NE to be upgraded, and
click System -> NCP data Management -> DB Download to
download all the databases via the EMS software, as shown in Figure
28.
FIGURE 28 DOWNLOAD DB DIALOG BOX OF THE EMS

Note:
It is unnecessary to download the database when upgrading the logic.
It is unnecessary to download the database for the standby NCP card. The data
will be automatically synchronized to the standby NCP card.
Verifying the Application/Logic Version in

the EMS
1. Double-click the NE that has been upgraded in the ZXONM E300 EMS,
to open the Card Management dialog box.
2. Right-click the NCP card to be queried with the version, and the
shortcut menu pops up. Select the Card Special Version menu, as
shown in Figure 29.
FIGURE 29 CARD M AN AGEMENT DIALOG BOX
3. The Card Special Version dialog box pops up and displays the
application/logic version of the queried NCP card, as shown in Figure
30. If the information displayed is consistent with the downloaded
application/logic version, it indicates that the newly downloaded
application/logic is running normally.

FIGURE 30 CARD SPECIAL VERSION DIALOG BOX
Remote Upgrade
The remote upgrade is the procedure that upgrades the application/logic
of NCP card in its Running state. The flowchart is shown in Figure 31.

FIGURE 31 REMOTE UPGRADE FLOWCHART
Begin
Prepare for upgrade
Confirm the address of

the active NCP board
Use ftp method Download the

application/logic
Upgrade the
application/logic
Verify the upgraded

application/logic
Try run of the

Use telnet method application/logic
Verify the application/logic

that has passed the try run
Activate the
application/logic

that has been activated
Upgrade the application/logic

of the standby NCP board
Download the
database
Performed in the
EMS

version in the EMS
End

Use network cable to connect the Ethernet interface of EMS computer
with the Ethernet interface of QxI card. Confirm that the network cable
is connected correctly.
Set the DIP switch on NCP card to non-all ON and non-all OFF so that
the NCP card enters the Running state.
Execute the p i n g N E - I P command at the EMS terminal. Confirm that
the EMS terminal communicates normally with the NE, and that the
ECC of the NE to be upgraded is smooth.
Confirm that the Agent program version to be downloaded comply with
the current EMS version. Ensure the validity and consistency of the
versions.
Confirming the Address of the Master NCP

Card
There are to methods to confirm the NCP card address: via EMS software
and via command lines.
Query via EMS software

1. In the ZXONM E300 EMS client operation window, select the ZXMP
S385 NE to be upgraded, and click Maintenance -> Diagnosis ->
MasterSlaveBrd Switch menu.
2. The MasterSlaveBrd Switch dialog box pops up, as shown in Figure

32.
FIGURE 32 M ASTERSLAVEBRD SWITCH DIALOG BOX

3. Click the Update button, the text box of Current Working Card will
display the address information of the master NCP card (1 1 8 1 or 1
1 9 1 ).
Query via command lines

1. Execute the command t e l n e t N E - I P , input the user name of z t e
and password of e c c according to the system prompt, and press
ENTER, until the prompt Z T E + > appears.
Note: The user name and password must be lowercase.
2. Under the prompt Z T E + > , input the command n c p s p i n g , to check if

the communication state of the standby NCP card is normal; and then
confirm the address of the master NCP card according to the result of
this command.
For example, to check the communication state of the standby NCP

card, and confirm the address of the master NCP card, the operations
are shown in Figure 33.
FIGURE 33 CONFIRMING THE ADDRESS OF THE M ASTER NCP CARD
The result shown in the figure is N C P S p i n g i n g 1 . 1 9 . 1 w i t h 3 2

b y t e s o f d a t a , which indicates that the address of the standby NCP
card is 1 19 1. Thus it can be concluded that the address of the master
NCP card is 1 18 1, with the Slot No. of 18.

1. Execute the command f t p N E - I P under the directory containing the
Agent program or logic on the computer. Input z t e for username and
e c c for password according to the system prompts, press ENTER until
the prompt f t p > appears.
card application/logic and check if the downloaded file is correct.
ftp> bin

ftp> put file_name_of_the_application/logic

//Download the card application/logic. When the f t p > prompt appears again,
it indicates that the file transfer has completed.
ftp> ls –l
//Check if the downloaded file size is consistent with the local file. If not
consistent, re-download the file.
ftp> bye
Caution: The application/logic of NCP card must be transferred to the NCP card in
the binary mode
Upgrading the Application/Logic

1. Execute the command t e l n e t N E - I P . Input z t e for username and
e c c for password according to the system prompts, press ENTER until
the prompt z t e + > appears.

upgrade the card application/logic. Refer to the section Upgrading the
Application/Logic in Local Upgrade section for detailed procedures of
upgrading the application/logic.
Caution: When executing the d - u p g r a d e command, the S l o t - N o . parameter

should be the slot number of the master NCP card queried in the section
Confirming the Address of the Master NCP Card.
For example, to upgrade the program file N C P - Z X M P S 3 8 5 - P R G -

V 1 . 0 1 R 1 P 0 5 . B I N 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 34.
FIGURE 34 REMOTE UPGRADE OF APPLICATION

Verifying the Upgraded Application/Logic

Execute the command d - g e t - s t a t u s under the prompt of Z T E + > to verify
if the version of the upgraded application/logic in the standby area is
normal.
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.
<Command Format>
<Parameter Description> is listed in Table 16.
For example, to verify the program file in the section Upgrading the
Application/Logic, the result is shown in Figure 35.
FIGURE 35 VERIFYING THE UPGRADED PROGRAM
The parameters in the standby area (labeled as p r o g r a m n u m b e r : 0 x 0 2 )

that need to be verified are described in Table 18.

TABLE 18 P ARAMETERS IN THE STANDBY ARE A TH AT NEED TO BE VERIFIED

file type -
area
file is downloaded
download
version
try-run type -
status m a s t e r indicates the master state -
upgrade N O indicates that the database is
-
database not upgraded
0 x 0 A 4 0 0 0 0 0 0 is the initial
start address -
size
-
elapsed time parameter is reserved
-
remained time parameter is reserved
Try Run of the Application/Logic

1. Execute the d - t r y command under the prompt Z T E + > to perform the
try run of the application/logic in the standby area.
<Command Format>
d-try Subrack-NO. Slot-NO. Card-CPU-NO. {-p\-f}
TABLE 19 P ARAMETERS OF THE COMM AND D-TRY
Slot-NO. 19; It is 18 or 19 for the NCP card.
-p Try running the card application.
-f Try running the card logic.

2. During the process of executing the command d - t r y , the system will

prompt: D o y o u w a n t t o u p g r a d e t h e D B a r e a ? Y e s [ y ] / N o [ n ] .
Select y to clear the NCP database; while select n to not to clear the
NCP database.
For example, to try running the program file in the section Upgrading
the Application/Logic, the result is shown in Figure 36.
FIGURE 36 TRY RUN OF THE PROGRAM
3. When the d - t r y command completes, the NCP card is reset, and the
communication with the computer is interrupted. The ECC will be
interrupted for about one to two minutes, and during this time the
EMS cannot manage this NE. If there are two NCP cards, after the
reset, the system will switch to another NCP card first. And after the
NCP card to be upgraded starts running again, it will automatically
switch back to the upgraded NCP card, and continue the upgrade
process.
Verifying the Application/Logic after Try

Run
1. Execute the t e l n e t N E - I P command on the EMS computer, and input
the user name of z t e and password of e c c according to the system
prompts. Press ENTER until the prompt Z T E + > appears.
2. Under the prompt Z T E + > , execute the n c p s p i n g command, to test if

the communication state of the standby NCP card is normal, and
confirm the master NCP address according to the command result. The
operation example is shown in Figure 33.
3. Execute the command d - g e t - s t a t u s under the prompt of Z T E + > to

verify if the version of the upgraded application/logic in the original
standby area is normal. If the version is abnormal, it is necessary to
re-perform all the operations from the section Downloading the
Application/logic to the section Try Run of the Application/Logic again,
until the version queried is normal.
<Command Format>

For example, to verify the program file in section Try Run of the
Application/Logic, the result is shown in Figure 37.
FIGURE 37 VERIFYING THE PROGRAM THAT P ASSED THE TRY RUN
The parameters in the original standby area (labeled as p r o g r a m n u m b e r :

0 x 0 2 ) that need to be verified are described in Table 20.
TABLE 20 P ARAMETERS IN THE ORIGINAL STANDBY AREA THAT NEED TO BE VERIFIED

AFTER THE TRY RUN

file type -
area
download date File downloaded time
the result in Figure 35
download Should be consistent with
File version downloaded
version the result in Figure 35
try-run indicates that it is
try-run type performing the try-run of the -
program
try-run indicates the try-run
status -
status
upgrade Y E S ! indicates that the database
-
database is upgraded


0 x 0 A 4 0 0 0 0 0 0 is the initial
start address -
file length Size of the downloaded file
try-run 4<minutes> indicates the
-
elapsed time elapsed time of the try-run
try-run 11<minutes> indicates the
-
remained time remaining time of the try-run
Activating the Application/Logic

Execute the d - a c t i v e command under the prompt Z T E + > , to activate the
card application/logic in the standby area after the try run succeeds.
<Command Format>
d-active Subrack-NO. Slot-NO. Card-CPU-NO {-p/-f}
TABLE 21 P ARAMETERS OF THE COMM AND D-ACTIVE
Slot-NO. 19; It is 18 or 19 for the NCP card.
-p Activate the card application.
-f Activate the card 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 card, it will go back to the
original application/logic.
For example, the program activation operation is shown in Figure 38.
FIGURE 38 ACTIVATING THE PROGRAM

Verifying the Activated Application/Logic

Execute the command d - g e t - s t a t u s under the prompt Z T E + > , to verify if
the version of the activated application/logic in the original standby area is
normal.
<Command Format>

For example, to verify the activated application file, the operation and
result are shown in Figure 39.
FIGURE 39 VERIFYING THE ACTIVATED PROGRAM
The parameters in the original standby area (labeled as p r o g r a m n u m b e r :

0 x 0 2 in Figure 39) that need to be verified are described in Table 22.
TABLE 22 DESCRIPTIONS OF P AR AMETERS THAT NEED TO BE VERIFIED AFTER

ACTIVATION

file type -
area


download Should be consistent with
version the result in Figure 35
try-run type Changes to r e s e r v e d -
The s t a t u s of the area

labeled as p r o g r a m
status m a s t e r indicates the master state
number: 0x01
should change to s l a v e
upgrade N O indicates that the database
-
database upgrade is completed
0 x 0 A 4 0 0 0 0 0 0 is the initial
start address -
file length Size of the downloaded file
try-run
elapsed time Changes to r e s e r v e d -
try-run
remained time Changes to r e s e r v e d -
Upgrading the Application/Logic for

Standby NCP
Note: If only one NCP card is configured, skip this step.
1. Execute the command t e l n e t N E - I P on the EMS computer. Enter

z t e for user name and e c c for password according to the system
2. Execute the command d - s e t - n c p b a c k s t a t under the prompt Z T E + >

to switch to the standby NCP card, as shown in Figure 40.
FIGURE 40 SWITCHING TO THE STANDBY NCP CARD

3. Re-perform all the operations from section Upgrade Preparations to

section Verifying the Activated Application/Logic, to complete the
upgrade of the standby NCP card.

In the EMS client operation window, select the NE to be upgraded, and
click System -> NCP data Management -> DB Download to download
all the databases via the EMS software, as shown in Figure 28.

EMS
to open the Card Management dialog box, as shown in Figure 29.
2. Right click the NCP card to be queried with the version, and the
shortcut menu pops up. Select the Card Special Version menu, as
shown in Figure 29.
application/logic version of the queried NCP card, as shown in Figure
30. If the information displayed is consistent with the downloaded
application/logic, it indicates that the newly downloaded
application/logic is running normally.


Chapter 5

Configurations
This chapter describes how to configure the Agent program for the ZXMP
S330/S325, including DIP switch definition, Agent program download and
upgrade process.
been configured.
Module on NCP Card
1. Prepare for running the Agent program.
2. Start the Agent program on NCP card.
3. Other functions
¾ Read and set the system parameters (mainly the MAC address).
NCP Card State Switching

The states of NCP card include DOWNLOAD state and Running state, which
are controlled by the 4-digit DIP switch marked as S3 on the NCP card.

1. DOWNLOAD state: Used to download Agent application and

configuration files. To enter this state, set the DIP switch to all ON; or
restart/reset NCP card and press down the ring-trip button for long
time. Once the NCP card is reset or restarted, the NE IP address will be
192.192.192.11 with the subnet mask of 255.255.255.0 by default.
2. Running state: Used to start the application of the NCP card. The DIP
switch is set to non-all ON and non-all OFF.

Local Upgrade
FIGURE 41 LOCAL UPGRADE FLOWCHART OF ZXMP S330/S325
Begin
Prepare for upgrade

method

Upgrade the
application/logic
Use telnet
method
Verify the
application/logic
Performed in
the EMS
Verify the
in the EMS
End

Begin
Confirm the BOOTROM

card is ready
Set the DIP switch of NCP board to all ON; or

under the Running state, restart/reset NCP board
and then press down the ring-trip switch for long
time; so that the NCP board enters the
DOWNLOAD state

between EMS and the Qx
interface of NCP board is
correctly connected

connection status
Connected
No
card?
Yes No
NE information?
Format the CF card
Yes
Reset the NCP board
Configure the NE
information
Reset the NCP board
End

1. Confirm the BOOTROM chip is correct and the CF card is ready.

¾ Make sure the correct BOOTROM chip is plugged on NCP card, as
each type of NCP card can only use its own BOOTROM chip.
¾ Make sure the CF card is correctly plugged on NCP.
2. Set the DIP switch on NCP card to all ON; or under the Running state,
restart/reset the NCP card and press down the ring-trip button for long
time to enter the DOWNLOAD state. The NE IP address is
192.192.192.11 with the subnet mask as 255.255.255.0.
3. Use a network cable to connect the EMS Ethernet interface with the Qx
interface on NCP card, and confirm the network cable connection is
correct.
¾ Subnet mask: 255.255.255.0
to confirm that the EMS computer is connected with NCP.
reconfigure the NE information, the upgrade preparations finish here.
reconfigure the NE information, follow the steps below to clear the NCP
database:
computer.
both empty, press ENTER till the prompt Z T E + > appears.
¾ Input the command d - e r a s e – d 1 and then the command r m – r f
D b S y s under the prompt Z T E + > to clear the NCP database, where
d 1 represents for the NCP database area and D b S y s represents for
database information on CF card.
8. If the CF card is used for the first time, execute the following
commands to format the CF card.
computer.
¾ Input the command f o r m a t under the prompt Z T E + > to format
the CF card.
Caution: The CF card contains critical configurations including NE IP address, MAC

address, subnet mask, database information, and card configuration. Be cautious
to use the format operation since it will clear all the data on CF card.

9. Input the command d - r e b o o t to reset the NCP card. If the reset is

successful, the system will prompt “The connection with the host is
lost”.
10. Configure the NE IP address, subnet mask, and MAC address
¾ Input the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS
computer. When the system prompts to enter user name and
password which are both empty, press ENTER till the prompt Z T E + >
appears.
configure the NE IP address, subnet mask, and MAC address. The
input principles of each item are listed in Table 23. Input the
command d - c f g n e t – s to query the NE related information.
Parameter Name Input Principle Remarks

IP Address Input the IP address of the NE. It is mandatory.
Subnet Mask Input the subnet mask of the NE. It is mandatory.
It is mandatory and should be
MAC Address Input the physical address of the NE.
unique for each NE.
Warning: Each parameter must be entered. Press ENTER directly if there is no

modification. Do not quit in the middle of the procedure, otherwise the NCP card
will stay in the infinite waiting state.
¾ The configuration is completed. The system will display the newly

configured NE address.
¾ Save the configuration according to system prompt.
11. Input the command d - r e b o o t to reset the NCP card, and the new NE
IP address will immediately take effect. All the local upgrade
preparations complete here.

be skipped.

both empty. Press ENTER directly.
3. Input the command d - e r a s e – d 1 to clear the database information in
the memory of NCP card.
4. Input the command r m – r f D b S y s to clear the database information
in the CF card of NCP card.


system prompts to input the username and password which are both
empty, press ENTER until the prompt f t p > appears.
2. Execute the following commands under the f t p > prompt, to deliver the
application/logic to the NCP card.
ftp> bin
ftp> put file name of the application/logic
//Deliver the card application/logic.
ftp> ls -l
//Check if the size of the downloaded file is consistent with that of the local file.
If not, re-download the file.
ftp> bye
//Exit the ftp connection.
Caution: The application of NCP card must be named as “NCP***.BIN”, and the
logic must be named as “NCP***.FPZ” or “NCP***.RBF”. Otherwise the automatic
download cannot be implemented. The file extension name can be either lowercase
or uppercase.
area.

prompts to input the username and password which are both empty,
press ENTER directly until the prompt Z T E + > appears.

upgrade the NCP card application/logic.
<Command Format>
d-upgrade Subrack-NO. Slot-NO. Card-CPU-NO. {-p Program-

file-name\-f Logic-file-name}
TABLE 24 P ARAMETERS OF THE COMM AND D-UPGRADE (ZXMP S330/S325)
Subrack-NO. 1 or 2, generally 1. It is 2 when the extended subrack is configured.
Slot-NO. The slot number of the card. It is 17 for the NCP card.
Card-CPU-NO. Generally 1.


The parameter for card application delivery, followed by the card
The parameter for card logic delivery, followed by the card logic file
-f name.
Note: It is recommended to put the files to be delivered under the current

directory when executing the d - u p g r a d e command. Otherwise, it is necessary to
add the file directory in front of the application/logic file names in the command
line.


Note: If the version is abnormal, it is necessary to re-perform the operations

described in the sections of Downloading the Application/Logic and Upgrading the
Application/Logic until the version queried is normal.
<Command Format>
TABLE 25 P ARAMETERS OF THE COMM AND D-GET-STATUS
Slot-NO. 19. It is 17 for the NCP card.

<Field Description>
The fields that need to be verified are described in Table 26.
TABLE 26 DESCRIPTIONS OF FIELDS THAT NEED TO BE VERIFIED FOR LOCAL UPGRADE
Field Name Field Description Remarks

file type -
area, f p g a indicates the FPGA
file is downloaded
download
version
try-run type -
m a s t e r indicates the master
status state, s l a v e indicates the standby -
state
-
It is the initial address of the
start address -
program
size
try-run This parameter changes to
elapsed time reserved -

remained time reserved -

1. Set the DIP switch S3 of NCP card to non-all ON and non-all OFF, and
then reset the NCP card. The NCP card enters the Running state.
Note: During local upgrade, if the DOWNLOAD state was entered by

restarting/resetting NCP card and pressing down the ring-trip button for long time,
plugging out the NCP card and re-inserting it into the slot can enable the NCP card
to enter the Running state.

through.


click the menu System -> NCP data Management -> DB
Download to download all the databases via the EMS software.
Note: It is unnecessary to download the database when upgrading the logic.

the EMS
shortcut menu pops up. Select the Card Special Version.
application/logic version of the queried NCP card. If the information
displayed is consistent with the downloaded application/logic version,
it indicates that the newly downloaded application/logic is running
normally.
Remote Upgrade
The remote upgrade is the procedure that upgrades the Agent
application/logic of NCP card in its Running state. The flowchart is shown
in Figure 43.

FIGURE 43 REMOTE UPGRADE FLOWCHART OF ZXMP S330/S325
Begin
Prepare for upgrade

application/logic
Upgrade the
application/logic
Verify the upgraded

application/logic
Try run of the


Activate the
application/logic

Download the
database
Performed in the
EMS

version in the EMS
End
with the Qx Ethernet interface of NCP card. Confirm that the network
cable is connected correctly.

Set the IP address of EMS computer to be within the same network

Set the DIP switch of S3 on NCP card to non-all ON and non-all OFF so
that the NCP card enters the Running state.
versions.

1. Execute the command f t p N E - I P under the directory which contains
the application/logic. Input the user name of z t e and password of e c c
according to the system prompts, then press ENTER until the prompt
f t p > appears.

the application/logic and confirm if the downloaded file is correct.
ftp> bin
//Download the card application/logic. If the prompt f t p > appears again, it
indicates that the file transfer is completed.
ftp> ls -l
//Check if the size of downloaded file is consistent with the local file. If not, re-
download the file.
ftp> bye
Caution: The card application/logic must be transferred to NCP card using the
binary mode. The application must be named as “NCP***.BIN”, and the logic must
be named as “NCP***.FPZ” or “NCP***.RBF”. Otherwise, the automatic download
cannot be implemented. The extension name of the files can be either lowercase or
uppercase.

1. Execute the command t e l n e t N E - I P . Input the user name of z t e and
password of e c c according to the system prompts, then press ENTER

upgrade the NCP card application/logic to the application/logic area
respectively.

<Command Format>


normal.

<Command Format>
<Field Description>
TABLE 27 DESCRIPTIONS OF FIELDS IN THE STANDBY ARE A TH AT NEED TO BE VERIFIED

file type -
area
file is downloaded
download
version
try-run type -
state
-
start address -
program


size


<Command Format>
TABLE 28 P ARAMETERS OF THE COMM AND D-TRY
Slot-NO. 19. It is 17 for the NCP card.
-p Try running the card application.
-f Try running the card logic.

prompt: D o y o u w a n t t o u p g r a d e t h e D B a r e a ? Y e s [ y ] / N o [ n ]
¾ Input y : Clear the NCP database.

¾ Input n : Do not clear the NCP database.
3. When the d - t r y command completes, the NCP card is reset, and the
communication with the computer is interrupted. The ECC will be
interrupted for about one to two minutes, and during this time the
EMS cannot manage this NE.


Run

verify if the version of the application/logic in the original standby area
that has passed the try run is normal.

<Command Format>
<Field Description>
The fields in the original standby area that need to be verified are
described in Table 29.

AFTER THE TRY RUN

file type -
area
the result got in the
Verifying the Upgraded
Application/Logic section
download the result got in the
version Verifying the Upgraded
program
status -
status
-
start address The initial address of the program -


file length The file size
try-run Indicates the elapsed time of the
-
elapsed time try-run
try-run Indicates the remaining time of the
-
remained time try-run

card application/logic in the standby area after the try run succeeds.
<Command Format>
TABLE 30 P ARAMETERS OF THE COMM AND D-ACTIVE
Slot-NO. 19; It is 17 for the NCP card.
run, or it is not activated before resetting the NCP card, it will go back to the

normal.
<Command Format>

<Field Description>
T AB L E 3 1 D E S C R I P T I O N S OF FI E L D S T H AT N E E D T O B E V E R I F I E D AF T E R AC T I V AT I O N

file type -
area
Should be consistent
with the result got in
download date File downloaded time the Verifying the
Application/Logic after
Try Run section
download
version File version downloaded the Verifying the
Try Run section
The status of the
original master area
status m a s t e r indicates the master status
should change to
slave
-
database upgrade is finished
0 x 0 A 4 0 0 0 0 0 0 is the initial address
start address -
of the program
file length The file size the Verifying the
Try Run section
try-run
try-run

click System -> NCP data Management -> DB Download menu.
Download all the databases in the dialog box pops up.
Note: It is unnecessary to download database when upgrading the logic.


EMS
to open the Card Management dialog box of this NE.
shortcut menu pops up. Select the Card Special Version menu.
application/logic version of the queried NCP card. If the information
displayed is consistent with the downloaded application/logic, it
indicates that the newly downloaded application/logic is running
normally.

Chapter 6
ZXMP S200 Agent

Configurations
This chapter describes how to configure the Agent program for the ZXMP
S200, including DIP switch definition, Agent program download and
upgrade process.
application has been downloaded to the NCP unit on the system motherboard (SMB
in short) and the initial parameters have been configured.
Module
The system motherboard (SMB in short) of ZXMP S200 integrates various
interface units, NCP unit, clock unit, cross-connect unit, etc. The NCP unit
equals to NCP card of other SDH equipment. Its BOOTROM functional
module has the following functions:
Prepare for running the Agent program.

Start the Agent program on NCP card.
Other functions
¾ Read and set the system parameters.

NCP Unit State Switching

The states of NCP unit include DOWNLOAD state and Running state, which
are controlled by the 4-digit DIP switch marked as S3 on the SMB PCB
board.
DOWNLOAD state: Used to download Agent application and

configuration files. To enter this state, set the DIP switch to all ON.
Once the NCP is reset or restarted, the NE IP address will be
192.192.192.11 with the subnet mask of 255.255.255.0 by default.
Running state: Used to start the Agent application. The DIP switch is
set to non-all ON and non-all OFF.

Local Upgrade
FIGURE 44 LOCAL UPGRADE FLOWCHART OF ZXMP S200
Begin
Prepare for upgrade

method

Upgrade the
application/logic
Use telnet
method
Verify the
application/logic
Performed in
the EMS
Verify the
in the EMS
End

Begin
Confirm the BOOTROM

card is ready
Set the DIP switch of NCP to all ON; or under the

Running state, restart/reset NCP and then press
down the ring-trip switch for long time; so that the
NCP enters the DOWNLOAD state

between EMS and the Qx
interface of NE is correctly
connected

connection status
Connected
No
card?
Yes No
NE information?
Format the CF card
Yes
Reset the NCP
Configure the NE
information
Reset the NCP
End

1. Confirm the BOOTROM chip is correct and the CF card is ready.

¾ Make sure the correct BOOTROM chip is plugged into the slot D55
on the SMB PCB board, as each type of NCP unit can only use its
own BOOTROM chip.
¾ Make sure the CF card is correctly plugged on the SMB PCB board.
2. Set the DIP switch S3 on the SMB PCB board to all ON; or under the
Running state, restart/reset the NCP and press down the ring-trip
button for long time to enter the DOWNLOAD state. The NE IP address
is 192.192.192.11 with the subnet mask as 255.255.255.0.
3. Use a network cable to connect the EMS Ethernet interface with the Qx
interface on the front panel of SMB, and confirm the network cable
connection is correct.
¾ Subnet mask: 255.255.255.0
to confirm that the EMS computer is connected with NCP.
reconfigure the NE information, the upgrade preparations finish here.
reconfigure the NE information, follow the steps below to clear the NCP
database:
computer.
clear the NCP database, where d 1 represents for the NCP database
area.
8. If the CF card is used for the first time, execute the following
commands to format the CF card.
computer.
¾ Input the command f o r m a t under the prompt Z T E + > to format
the CF card.
Caution: The CF card contains critical configurations including NE IP address, MAC

address, subnet mask, database information, and card configuration. Be cautious
to use the format operation since it will clear all the data on CF card.

9. Input the command d - r e b o o t to reset the NCP card. If the reset is

successful, the system will prompt “The connection with the host is
lost”.
10. Configure the NE IP address, subnet mask, and MAC address
¾ Input the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 on the EMS
computer. When the system prompts to enter user name and
password which are both empty, press ENTER till the prompt Z T E + >
appears.
configure the NE IP address, subnet mask, and MAC address. The
input principles of each item are listed in Table 32. Input the
command d - c f g n e t – s to query the NE related information.
Parameter Name Input Principle Remarks

IP Address Input the IP address of the NE. It is mandatory.
Subnet Mask Input the subnet mask of the NE. It is mandatory.
It is mandatory and should be
MAC Address Input the physical address of the NE.
unique for each NE.
Warning: Each parameter must be entered. Press ENTER directly if there is no

modification. Do not quit in the middle of the procedure, otherwise the NCP will
stay in the infinite waiting state.
¾ The configuration is completed. The system will display the newly

configured NE address.
¾ Save the configuration according to system prompt.
11. Input the command d - r e b o o t to reset the NCP card, and the new NE
IP address will immediately take effect. All the local upgrade
preparations complete here.

be skipped.
both empty. Press ENTER directly until the prompt Z T E + > appears.
3. Input the command d - e r a s e – d 1 to clear the database.


system prompts to input the username and password which are both
empty, press ENTER until the prompt f t p > appears.
2. Execute the following commands under the f t p > prompt, to deliver

the application/logic to the NCP card.
ftp> bin
//Deliver the NCP application/logic.
ftp> ls
// Check if the size of the downloaded file is consistent with that of the local
file. If not, re-download the file.
ftp> bye
Caution: The application of NCP card must be named as “NCP***.BIN”, and the
logic must be named as “NCP***.FPZ” or “NCP***.RBF”. Otherwise the automatic
download cannot be implemented. The file extension name can be either lowercase
or uppercase.
area.


upgrade the NCP application/logic.
<Command Format>

TABLE 33 P ARAMETERS OF THE COMM AND D-UPGRADE (ZXMP S200)
Subrack-NO. It is generally 1.
The sequence number of the unit to be upgraded. For NCP unit of
Slot-NO. SMB, it is 1; for MCU of SMB, it is 2.

Card-CPU-NO. It is generally 1.
The parameter for application delivery, followed by the application
-p file name.
-f The parameter for logic delivery, followed by the logic file name.
Note: It is recommended to put the files to be delivered under the current

directory when executing the d - u p g r a d e command. Otherwise, it is necessary to
add the file directory in front of the application/logic file names in the command
line.
[Example]
d To upgrade the application of NCP unit of ZXMP S200:
Suppose the application file name is NCP-ZXMPS200-PRG-V1.00R1P05.BIN,

execute the following command:
ZTE+>d-upgrade 1 1 1 –p NCP-ZXMPS200-PRG-V1.00R1P05.BIN
Continue with the follow-up upgrade operations as per system prompt.

The operation interface is shown in Figure 46.
FIGURE 46 INTERFACE FOR LOCAL UPGRADE OF NCP APPLICATION OF ZXMP S200




<Command Format>
TABLE 34 P ARAMETERS OF THE COMM AND D-GET-STATUS (ZXMP S200)
The sequence number of the unit to be upgraded. For NCP unit
Slot-NO. of SMB, it is 1; for MCU of SMB, it is 2.
<Field Description>
TABLE 35 DESCRIPTIONS OF FIELDS THAT NEED TO BE VERIFIED FOR LOCAL UPGRADE

file type -
file is downloaded
download
version
try-run type -


state
-
start address -
program
size


1. Set the DIP switch S3 to non-all ON and non-all OFF, and then reset
the NCP. The NCP enters the Running state.
Note: During local upgrade, if the DOWNLOAD state was entered by

restarting/resetting NCP card and pressing down the ring-trip button for long time,
resetting the NCP can enable it to enter the Running state.


through.

click the menu System -> NCP data Management -> DB
Download to download all the databases via the EMS software.
Note: It is unnecessary to download the database when upgrading the logic.

the EMS
2. Right-click the NCP to be queried with the version, and the shortcut
menu pops up. Select the Card Special Version menu item.

application/logic version of the queried NCP unit. If the information
displayed is consistent with the downloaded application/logic version,
it indicates that the newly downloaded application/logic is running
normally.
Remote Upgrade
The remote upgrade is the procedure that upgrades the application/logic
of Agent in its Running state. The flowchart is shown in Figure 47.
Note: For NCP unit, the ZXMP S200 supports both local and remote upgrade of its
application, but supports only local upgrade of its logic. While for other application
and logic, the ZXMP supports both local and remote upgrade.

FIGURE 47 REMOTE UPGRADE FLOWCHART OF ZXMP S200
Begin
Prepare for upgrade

application/logic
Upgrade the
application/logic
Verify the upgraded

application/logic
Try run of the


Activate the
application/logic

Download the
database
Performed in the
EMS

version in the EMS
End

with the Qx interface on the front panel of SMB. Confirm that the
network cable is connected correctly.
Set the IP address of EMS computer to be within the same network
Set the DIP switch of S3 to non-all ON and non-all OFF so that the NCP
enters the Running state.
versions.
To download the application or logic of MCU, the DIP switch S4 on SMB
PCB should be set to non-all ON and non-all OFF.

1. Execute the command f t p N E - I P under the directory which contains
the Agent application/logic. Input the user name of z t e and password
of e c c according to the system prompts, then press ENTER until the
prompt f t p > appears.

the application/logic and confirm if the downloaded file is correct.
ftp> bin
//Download the Agent application/logic. If the prompt f t p > appears again, it
indicates that the file transfer is completed.
ftp> ls -l
//Check if the size of downloaded file is consistent with the local file. If not, re-
download the file.
ftp> bye
Caution: The Agent application/logic must be transferred to NCP using the binary
mode. The application must be named as “NCP***.BIN”, and the logic must be
named as “NCP***.FPZ” or “NCP***.RBF”. Otherwise, the automatic download
cannot be implemented. The extension name of the files can be either lowercase or
uppercase.


1. Execute the command t e l n e t N E - I P . Input the user name of z t e and
password of e c c according to the system prompts, then press ENTER
Caution: To upgrade the application/logic of MCU, execute the s p i n g 1 2 1

command first before executing the t e l n e t command, so as to check if the S
interface between NCP and MCU is normal. Only when the communication is
normal, can the upgrade operation be continued.

upgrade the NCP card application/logic to the application/logic area
respectively.
<Command Format>


normal.

<Command Format>
<Field Description>


file type -
file is downloaded
download
version
This parameter changes to

try-run type -
reserved.
state
-
start address -
program
size


<Command Format>
TABLE 37 P ARAMETERS OF THE COMM AND D-TRY (ZXMP S200)


The parameter for application delivery, followed by the
-f The parameter for logic delivery, followed by the logic file name.

prompt: D o y o u w a n t t o u p g r a d e t h e D B a r e a ? Y e s [ y ] / N o [ n ]
¾ Input y : Clear the NCP database.

¾ Input n : Do not clear the NCP database.
3. When the d - t r y command completes, the NCP unit will reset.

Run

verify if the version of the application/logic in the original standby area
that has passed the try run is normal.

<Command Format>
<Field Description>


AFTER THE TRY RUN

file type -
download the result got in the
version Verifying the Upgraded
program
status -
status
-
start address The initial address of the program -
file length The file size
try-run Indicates the elapsed time of the
-
elapsed time try-run
try-run Indicates the remaining time of the
-
remained time try-run

application/logic in the standby area after the try run succeeded.
<Command Format>

TABLE 39 P ARAMETERS OF THE COMM AND D-ACTIVE (ZXMP S200)
run, or it is not activated before resetting the NCP unit, it will go back to the

normal.
<Command Format>
<Field Description>
T AB L E 4 0 D E S C R I P T I O N S OF FI E L D S T H AT N E E D T O B E V E R I F I E D AF T E R AC T I V AT I O N

file type -
area, f p g a indicates FPGA.
download date File downloaded time the Verifying the
Try Run section
download
version File version downloaded the Verifying the
Try Run section


The status of the
original master area
status m a s t e r indicates the master status
should change to
slave
-
database upgrade is finished
0 x 0 A 4 0 0 0 0 0 0 is the initial address
start address -
of the program
file length The file size the Verifying the
Try Run section
try-run
try-run

click System -> NCP data Management -> DB Download menu.
Download all the databases in the dialog box pops up.
Note: It is unnecessary to download database when upgrading the logic.

EMS
to open the Card Management dialog box of this NE.
2. Right-click the NCP to be queried with the version, and the shortcut
menu pops up. Select the Card Special Version menu.
application/logic version of the queried NCP unit. If the information
displayed is consistent with the downloaded application/logic, it
indicates that the newly downloaded application/logic is running
normally.
Precautions
For NCP unit, its Agent application supports both local and remote
upgrade, and its logic only supports local upgrade. For MCU, both its
application and logic support local and remote upgrade.

Make the preparations below before downloading the application or

logic of MCU on SMB:
¾ Set the NCP unit to Running state, i.e. set the DIP switch S3 on
SMB PCB to non-all ON and non-all OFF.
¾ The DIP switch S4 controls the working state of MCU on SMB. Set
S4 to non-all ON and non-all OFF.
In the EMS, the Card Management dialog box of ZXMP S200 is shown
in Figure 48.
FIGURE 48 CARD M AN AGEMENT DIALOG BOX OF ZXMP S200
The slot #1 corresponds to the NCP unit, the cards inserted in slot #2
through slot #8 share the MCU of SMB. Therefore, upgrading
application/logic of any card in slot #2 to slot #8 will upgrade all the
units controlled by the MCU.
The parameters of S u b r a c k - N O . , S l o t - N O . , and C a r d - C P U - N O . of a
command shall be configured as the following:
¾ The S u b r a c k - N O . and C a r d - C P U - N O . are generally “1”.
¾ The S l o t - N O . is determined by the card to be upgraded. For NCP
unit, it is “1”; for MCU, it is “2”.
Take the d - g e t - s t a t u s command as an example. To query the NCP
state, the command line is d - g e t - s t a t u s 1 1 1 ; to query the MCU
state, the command line is d - g e t - s t a t u s 1 2 1 .

Chapter 7
WDM Equipment Agent

Configurations
This chapter describes the Agent program configurations of ZXWM M900,

ZXMP M800, and ZXMP M600.
Note:
For ZXWM M900 or ZXMP M800, there are two kinds of NE control processors:
NCP card which is only applicable to 2 M supervision system, and NCPF card
applicable to both 2 M and 100 M supervision system.
For ZXMP M600, the NE control processor is the NCP card.
DIP Switch on NCP/NCPF Card

The DIP switch is located on the PCB of the NCP/NCPF card with the
identifier of S2. It has eight pins which are named from DIP1 to DIP8 in
this manual. Each pin can be switched between the ON position and the
opposite position (non-ON).
The definition of various switch status are described in Table 41.
TABLE 41 DEFINITION OF DIP SWITCH ON NCP/NCPF CARD
DIP Switch Description NE Status Caution
ON DIP Application program status

(normal working status)
DIP1 ~ DIP 8: non-ON The login name and password
are admin while running the The change of DIP
1 2 3 4 5 6 7 8
FTP and TELNET. switch becomes valid
only after resetting the
ON DIP DOWNLOAD status card.
DIP1 ~ DIP7: non-ON The login name and password is
DIP 8: ON null while running the FTP and
1 2 3 4 5 6 7 8 TELNET.

DIP Switch Description NE Status Caution
Be cautious to use this

ON DIP
DIP4: ON In the normal working status, function for it will
the user can print out influence the system
DIP8: ON or non-ON
information through the serial efficiency seriously when
Others: non-ON interface (traceMsg output). there is much debugging
1 2 3 4 5 6 7 8
information output.
In the normal working status,

ON DIP force the NE IP as
The IP address of
DIP2: ON 192.192.192.11/255.255.255.0.
only one NE can be
Others: non-ON The login name and password set as
1 2 3 4 5 6 7 8 are admin while running the 192.192.192.11 in
FTP and TELNET. the whole network
at the same time.
In the DOWNLOAD status, force
ON DIP the NE IP as The change of DIP
DIP2: ON
192.192.192.11/255.255.255.0. switch becomes
DIP8: ON valid only after
The login name and password
Others: non-ON resetting the card.
1 2 3 4 5 6 7 8 are null while running the FTP
and TELNET.
ON DIP
The change of DIP
DIP1: ON switch becomes valid
Probe and debugging status
DIP8: ON only after resetting the
1 2 3 4 5 6 7 8 card.
Use of TELNET and FTP

Commands
There are two methods to run the TELNET and FTP services, depending on
whether the IP address of an NE is known:
1. IP address of an NE is known
i. Keep the DIP4 and DIP8 of the DIP switch of the NCP/NCPF card on
either position, and set all the other pins of the switch to the non-
ON position.
ii. Execute the t e l n e t or f t p command to log in to the NE. Suppose
the IP address of the NE is 192.1.1.1. For example, enter the
following command.
telnet 192.1.1.1
iii. Press the ENTER key. Then input the login name and password on
the local computer screen according to the prompt.
Note: When the DIP8 is set to the ON position, the default login name and
password are empty. When the DIP8 is set to the non-ON position, the default
login name and password are both “admin”.

Chapter 7 - WDM Equipment Agent Configurations
2. IP address of an NE is unknown
i. Set the DIP2 and DIP8 of the DIP switch to the ON position, set the
DIP4 to ON or non-ON, and the other pins to non-ON. By this way,
the IP address of the NE is set to 192.192.192.11 and the mask to
255.255.255.0 forcibly.
ii. Execute the t e l n e t or f t p command to log in to the NE directly.
For example, enter the following command line.
telnet 192.192.192.11
Caution: To ensure later supervision on the NE by the EMS, switch the DIP2 of the
DIP switch back to the ON position and reset the card after using the forced IP
address.
Local NCP/NCPF
Reconfiguration
Setting the IP address of the NCP/NCPF card to 192.192.192.11 forcibly,
the maintenance person downloads the Agent/FPGA program(s) to the
card at the location of the equipment and then resets the IP address of the
NE. This operation procedure is called local NCP/NCPF reconfiguration.
Note: The NCP card only supports the download of Agent program, while the NCPF
card supporst the download of both Agent program and FPGA program.
The NCP/NCPF local reconfiguration flow is shown in Figure 49.

FIGURE 49 LOCAL NCP/NCPF RECONFIGURATION FLOW
Prepare before the Prepare before the

reconfiguration reconfiguration
Download the Agent Download the Agent/

program FPGA programs
Modify the address of Modify the address of

the NCP board the NCPF board
Burn the Agent/FPGA

Burn the Agent program
programs
Run the Agent program Run the Agent program
a. NCP board b. NCPF board
Preparing for Local Reconfiguration

1. Check and make sure that the BOOTROM chip on the NCP/NCPF card is
correct. Each kind of NCP/NCPF card can only use the BOOTROM chip
special for itself.
2. Set the DIP2 and DIP8 of the DIP switch on the NCP/NCPF card to the
ON position. The DIP4 can be set to either position, and all the other
pins of the DIP switch are set to the non-ON position. By this way, the
IP address of the NE is set to 192.192.192.11, and the subnet mask is
set to 255.255.255.0 forcibly.
3. Check and make sure the network cable connection between the EMS
host and the NE equipment is correct according to Table 42.
TABLE 42 NETWORK CABLE CONNECTION FOR LOCAL NCP/NCPF RECONFIGURATION
Equipment Supervision NCP/ Equipment-

Network Cable Type
Type System NCPF side Interface
J9 interface of The EMS host is connected
NCP
the OA subrack to the equipment directly
2M with a crossover network
NET interface of cable.
ZXMP M800/ NCPF
the NCPF card
ZXWM M900 Or the EMS host is connected
to the equipment through a
NET interface of
100 M NCPF HUB with straight network
the NCPF card
cables.


Network Cable Type
The network cable can be of
ETH1 or ETH2
any type since the interface
ZXMP M600 - NCP interface of the
can automatically identify the
NCP card
network cable type.
4. On the EMS computer, execute the command p i n g 1 9 2 . 1 9 2 . 1 9 2 . 1 1

to check and make sure that the EMS can communicate with the
NCP/NCPF card.
Downloading the Agent/FPGA Programs

(FTP)
d To download the Agent/FPGA programs through the FTP:
1. Enter the command f t p 1 9 2 . 1 9 2 . 1 9 2 . 1 1 to connect the NE, and

then input the login name and password. After successful connection,
the prompt f t p > appears.
2. Input the command b i n to set the file transmission mode to binary
mode.
3. Input the command l c d followed by the path name to convert the
path to the directory where the Agent program is located.
4. Input the command s e n d followed by the name of Agent/FPGA
program in the host and the file name in the NCP/NCPF card, to send
the program to the NCP/NCPF card. If the file name in the NCP/NCPF
card is not input, it will use the same name as that of file in the host.
5. Input the command b y e to exit from the FTP service.
Note: The extension name of the Agent/FPGA programs must be “bin”.
For example, download the Agent program to an NE as follows:
1. Enter f t p 1 9 2 . 1 9 2 . 1 9 2 . 1 1 to enter the ftp service. The login name

and password are empty.
2. After the connection succeeds, the prompt f t p > appears. Execute the
following commands to complete file transmission and exit from the
FTP service.
ftp>bin
ftp>lcd E:\ //“E:\” indicates the path where the Agent
program is located
ftp>send flash.bin a.bin //“flash.bin” is the file name of the Agent
program in the host while “a.bin” is the

name of the Agent program stored on the

NCP/NCPF card
ftp>bye
Modifying the Address of NCP/NCPF Card

1. Enter the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 , the prompt of Z T E - >
or Z T E # appears.
2. Input the command v w c to query the basic data stored in the
database of the current NE. The content of query result depends on
the version of the NCP/NCPF card.
3. Input the command d b e to clear the original data.
Caution: The command d b e must be in lowercase.
4. Input the command v w c to query the database again and make sure
the database has been cleared up.
5. Input the command c f g to configure the basic data once as required.
Note: The items which the system prompt to be configured depend on the version
of the NCP/NCPF card. Among these items, the configuration of the NE IP address,
subnet mask and area ID should conform to the principle described in Appendix B
and Appendix C. For other items, there is no special requirement.
Take an NE with the NCPF card as example. Modify the NE IP address into
192.1.12.18 and the mask into 255.255.255.0 with the TELNET service.
The NE is configured in a 2 M supervision system. Execute the following
commands:
ZTE#vwc
……
ZTE#dbe
ZTE#vwc
……
ZTE#cfg
Please input ncp config parameter
Board IP Address 192.1.12.18
Board Subnet Mask 255.255.255.0
Board Gateway IP 0.0.0.0

……
ZTE#exit
Note:
If the contract has no special requirements for the gateway in the networking:
for ZXWM M900 and ZXMP M800, it is recommended to set the B o a r d G a t e w a y
I P to the same as the address of the OSCF card in a 100 M supervision system,
and it is recommended to set it to the same as the NE IP address or to 0.0.0.0
directly; for ZXMP M600, it is recommended to set the B o a r d G a t e w a y I P to
0.0.0.0.
If the contract has special requirement for the gateway in the networking, set
the B o a r d G a t e w a y I P as required.
Burning the Agent/FPGA Programs

(TELNET)
d To burn the Agent/FPGA programs through the TELNET service:
1. Download the Agent/FPGA programs to the NCP/NCPF card.

2. Execute the t e l n e t command to connect the NE. The prompt Z T E - >
or Z T E # appears after successful connection.
3. Use the command p r g to burn the Agent/FPGA program.
¾ To burn the Agent program, input the command p r g followed by
the file name of the Agent program in the NCP/NCPF card.
¾ To burn the FPGA program, input the command p r g followed by the
file name of the FPGA program in the NCP/NCPF card and the
command f p g a .
4. Execute the e x i t command to exit from the TELNET service.
On the basis of the example in the section of Downloading the Agent/FPGA
Programs (FTP), burn the Agent program to the NE as follows:
1. Execute the command t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1 to enter the TELNET

mode.
2. After successful connection, the prompt Z T E # appears. Execute the
following commands to complete the program burning and exit from
the TELNET service.
ZTE#prg a.bin //“a.bin” is the file name of the Agent
program in the NCP/NCPF card
ZTE#exit

Running the Agent Program

1. Switch all the pins of the DIP switch on the NCP/NCPF card to the non-
ON position and then reset the NCP/NCPF card.
2. The red indicator light and green indicator light of the card flash
alternately, indicating the card is being initialized.
3. After the initialization, check the status of indicators and determine the
follow-up operations.
ZXWM M900 and ZXMP M800
¾ The green indicator flashes slowly and the red indicator is off. It
indicates that the system is running normally.
¾ The green indicator is off while the red indicator flashes slowly. It
indicates that the system is running normally but lacks basic
database. The user should download the database through the
ZXONM E300, and only after that can the equipment run normally.
ZXMP M600
¾ The indicator light with two colors is green and flashes slowly. It
¾ The indicator light with two colors is red and flashes slowly. It
Local Download
Local download: with the IP address of the NCP/NCPF card set to
192.192.192.11 forcibly, the maintenance person downloads the
Agent/FPGA program(s) to the NE at the location of the equipment.
The operation flow of the local download is shown in Figure 50.

F I G U R E 5 0 L OC AL D O W N L O AD F L O W C H AR T O F T H E AG E N T / F P G A P R O G R AM S
Prepare for the local

download
Download the Agent/

FPGA programs
Burn the Agent/FPGA

programs
Run the Agent program
1. Prepare for the local download

i. Check and make sure that the BOOTROM chip on the NCP/NCPF
card is correct. Each kind of NCP/NCPF card can only use the
BOOTROM chip special for itself.
ii. Switch the DIP2 and DIP8 of the DIP switch on the NCP/NCPF card
to the ON position. The DIP4 can be set to either position, and all
the other pins of the DIP switch are set to the non-ON position. By
this way, the IP address of the NE is set to 192.192.192.11, and
the mask to 255.255.255.0 forcibly.
iii. Check and make sure the network cable connection between the
EMS host and the NE equipment is correct according to Table 42.
iv. On the EMS
computer, execute the command ping
192.192.192.11 to check and make sure that the EMS can
communicate with the NCP/NCPF card.
2. Download/burn the Agent/FPGA program and run the Agent program
Remote Online Download

Remote online download: In the case that the NE IP address is known, the
maintenance person download the Agent program to the NE through the
ECC channel. This mode is usually used for online upgrade of the EMS
software.

Note: All the cards of ZXWM M900, ZXMP M800, and ZXMP M600 supports the
remote online download. Therefore, the operations described in this section is
applicable to call the cards in ZXWM M900, ZXMP M800, and ZXMP M600.
The flowchart of the remote online download is shown in Figure 51.
FIGURE 51 REM OTE ONLINE DOWNLO AD FLOWCH ART OF THE AGENT PROGR AM
Prepare for the remote

online download
Commond line mode ZXONM E300

Select the download mode
Download the Download the Agent

Agent program program with the board
software upgrade command
Upgrade the
Agent program
Run the Agent

program
Preparing for the Remote Online

Download
1. Set all the pins of the DIP switch on the NCP/NCPF card to the non-NO
position.
2. Check and make sure the network cable between the equipment and
the access NE is correctly connected according to the description in
Table 43.
TABLE 43 NETWORK CONNECTION FOR REMOTE ONLINE DOWNLOAD

Network Cable Type
ZXMP M800/ J9 interface of The EMS host is connected
NCP
ZXWM M900 the OA subrack to the equipment directly
with a crossover network
cable.
2M
NET interface of Or the EMS host is
NCPF connected to the equipment
the NCPF card
through a HUB with straight
network cables.


Network Cable Type
Any electrical
100 M NCPF interface of the
can automatically identify
OSCF card
the network cable type.
ETH1 or ETH2
ZXMP M600 - NCP interface of the
can automatically identify
NCP card
the network cable type.
3. Check and make sure that the fiber connections between NEs are
correct.
4. Execute the command “p i n g NE IP address” and make sure that the
ECC channel between the EMS and the NE to be upgraded is normal.
5. Check the version of the Agent program to be downloaded and make
sure it is correct and is consistent with that in the EMS.
Remote Online Download via Command

Lines
The remote online download via command lines includes two procedures:
downloading the Agent program and upgrading the Agent program.
Downloading the Agent Program (FTP)
d To transfer the Agent program to the card through the FTP service:
1. Execute the command f t p to connect the NE. The login name and
password are both admin. After successful connection, the prompt
“f t p > ” appears.
2. Enter the command b i n to set the file transmission mode as binary
system.
3. Enter the command l c d followed by the path name of the Agent
program.
4. Input the command s e n d followed by the name of Agent/FPGA
program in the host and the file name in the NCP/NCPF card, to send
the program to the NCP/NCPF card. If the file name in the NCP/NCPF
card is not input, it will use the same name as that of file in the host.
Note: The command s e n d can also be used to download other programs to the
card.
5. Input the command b y e to exit the FTP service.

Checkpoint: The extension name of the Agent/FPGA programs stored in the

NCP/NCPF card must be “bin”.
For example, download the Agent program to the NE with the IP address
192.1.12.18 as follows:
1. Enter the command f t p 1 9 2 . 1 . 1 2 . 1 8 to enter the FTP service. The

login name and password are both admin.
2. After successful connection, the prompt “ftp>” appears. Then execute
the following commands to transfer the program file and exit the FTP
service.
ftp>bin
ftp>lcd E:\ //“E:\” is the path of the Agent program
ftp>send flash.bin a.bin

//“flash.bin” is the file name of the Agent program in the EMS host, while
“a.bin” is the file name of the Agent program stored in the NCP/NCPF card.
ftp>bye
Burning the Agent Program of ZXWM M900/ZXMP M800

(TELNET)
d To burn the Agent program of ZXWM M900/ZXMP M800 through the

TELNET service:
1. Download the new version program file to the NCP/NCPF card

according to the section of Downloading the Agent Program (FTP).
2. Use the t e l n e t command to connect the NE. The login name and
“Z X O N M - > ” appears.
3. Enter the command s w i t c h w o r k m o d e [ m c u a d d r p o r t n o w o r k m o d e ]
to switch the card from the normal running status to the DOWNLOAD
status. If the command is executed successfully, the system will
display the success information; or else, it will prompt the errors.
Th e p aramet ers m c u a d d r , p o r t n o and w o r k m o d e are all displayed
in HEX with the “0 x ” added to the head. For example, the meaning of
the command s w i t c h w o r k m o d e 0 x 2 0 3 0 x 0 0 x 1 0 is as follows:
¾ m c u a d d r : card address (0 x 2 0 3 ). The complete representation is
0 x 0 0 0 2 0 3 , where “0 0 ” is the rack No., “0 2 ” is the subrack No., and
“0 3 ” is the slot No.
¾ p o r t n o : The definition of this parameter varies with different
supervision system, as described in Table 44.

TABLE 44 DEFINITION OF THE PAR AMETER PORTNO
Supervision
Definition of “portno”
System
2M It is 0 x 0 for all cards
For NCPF card
0x0: to download the Agent program
0x1: to download the 186 program on the NCPF card
100 M For OHPF card
0x0: to download the OHPF application program
0x1: to download other programs which can be upgraded (firmware)
For other cards, it is 0x0.
¾ w o r k m o d e : This parameter varies with different card, as described

in Table 45.
TABLE 45 DEFINITION OF THE PAR AMETER WORKMODE
Card/Program Type Definition of “workmode”
0x10 Switch to the normal working mode (used for normal

download)
Run the new version Agent program after resetting the
NCP/NCPF card. (Two latest downloaded Agent
NCP/NCPF
0x00 programs can be stored in the FLASH memory of the
NCP/NCPF card. The new version Agent program refers
(not including 186 to the newer one of them.)
program)
Run the old version Agent program after resetting the
NCP/NCPF card. (Two latest downloaded Agent
0x01 programs can be stored in the FLASH memory of the
NCP/NCPF card. The old version Agent program refers
to the older one of them.)

Programs of other cards download)
and 186 program of
NCP/NCPF card 0x20 Switch the working mode forcibly (used for setting the
card to DOWNLOAD status forcibly)
Note: For the NCP/NCPF card, avoid using the parameter “0 x 0 0 ” and “0 x 0 1 ” to
force the card to run the Agent program of a certain version unless there is special
requirement. After resetting the NCP/NCPF card, run the latest Agent program
downloaded.
4. Enter the command u p d a t e s o f t w a r e m c u a d d r p o r t n o f i l e n a m e to

load the b i n file downloaded to the card through the FTP service. For
example, input u p d a t e s o f t w a r e 0 x 2 0 3 0 x 0 O A _ D 5 V 1 3 4 . b i n , where
the O A _ D 5 V 1 3 4 . b i n is the file name of the program.

After successful upgrade, the system displays the information “u p d a t e

s o f t w a r e s u c c e e d ”. If the upgrade fails, the system will prompt the
errors.
¾ m c u a d d r , p o r t n o : slot No. and port No. of the card. Their
meanings are same as the parameters in the command
“s w i t c h w o r k m o d e ” described above.
¾ f i l e n a m e : the file name of the Agent program that has been
downloaded to the card through the FTP service.
5. Enter the e x i t command to exit from the TELNET service.
On the basis of the example in the section of Downloading the Agent

Program (FTP), upgrade the Agent program of the NE as follows:
1. Enter the command t e l n e t 1 9 2 . 1 . 1 2 . 1 8 to enter the TELNET mode.

The login name and password are both admin.
2. After successful connection, the prompt “Z X O N M - > ” appears. Perform
the following commands to switch the work mode of the card and
upgrade the Agent program.
ZXONM-> switchworkmode 0x208 0x0 0x10

//Switch the work mode of the NCP to the DOWNLOAD status
ZXONM-> updatesoftware 0x208 0x0 a.bin

//Download the a . b i n file to the NCP card
ZXONM->exit
Burning the Agent Program of ZXMP M600 (TELNET)
d To burn the Agent program of ZXMP M600 through the TELNET service:
1. Download the new version program file to the NCP card according to
according to the section of Downloading the Agent Program (FTP).
2. Use the t e l n e t command to connect the NE. The login name and
“ZXONM->” appears.
3. Enter the command s w i t c h w o r k m o d e [ m c u a d d r w o r k m o d e ] to
switch the NCP card from the normal working status to the DOWNLOAD
status.
If the command is executed successfully, the system will display the
success information; or else, it will prompt the errors.
The parameters m c u a d d r and w o r k m o d e are all displayed in HEX with
the “0 x ” added to the head. For example, the meaning of the
command s w i t c h w o r k m o d e 0 x 2 0 3 0 x 1 0 is as f ollow s:
¾ m c u a d d r : board address (0 x 2 0 3 ). The complete representation is
0 x 0 0 0 2 0 3 , where “0 0 ” is the rack No., “0 2 ” is the subrack No. and
“0 3 ” is the slot No.

¾ w o r k m o d e : This parameter varies with different card, as described

in Table 46.
TABLE 46 DEFINITION OF THE PAR AMETER WORKMODE
Card/Program
Definition of “workmode”
Type

download)
Run the new version Agent program after resetting the NCP
0x00 card. (Two latest downloaded Agent programs can be stored
in the FLASH memory of the NCP card. The new version
NCP
Agent program refers to the newer one of them.)
Run the old version Agent program after resetting the NCP
0x01 card. (Two latest downloaded Agent programs can be stored
in the FLASH memory of the NCP card. The old version
Agent program refers to the older one of them.)

Programs of other download)
boards Switch the working mode forcibly (used for setting the card
0x20
to DOWNLOAD status forcibly)
Caution: For the NCP card, avoid using the parameter “0 x 0 0 ” and “0 x 0 1 ” to force
the card to run the Agent program of a certain version unless there is special
requirement. After resetting the NCP card, it is default to run the latest Agent
program downloaded.
4. Enter the command u p d a t e s o f t w a r e m c u a d d r f i l e n a m e to load the

b i n file downloaded in the card through the FTP service. For example,
input u p d a t e s o f t w a r e 0 x 2 0 3 C O P D . b i n , where the C O P D . b i n is the
file name of the program.
After successful upgrade, the system displays the information “u p d a t e
s o f t w a r e s u c c e e d ”. If the upgrade fails, the system will prompt the
errors.
¾ m c u a d d r : slot No. of the card. Its meaning is same as the
parameter in the command “s w i t c h w o r k m o d e ” described above.
¾ f i l e n a m e : the file name of the Agent program that has been
downloaded to the card through the FTP service. The ZXMP M600
will judge whether the program file matches the card type. The file
must match the card completely. The requirements for the program
file name are described in Table 47.
TABLE 47 REQUIREMENTS FOR PROGRAM FILE NAME OF CARDS IN THE ZXMP M600
Card File Name

NCP CNCP*.bin or CNCP*.BIN
SRM CSRM*.bin or CSRM*.BIN
GEM CGEM*.bin or CGEM*.BIN

Card File Name

PCW CPCW*.bin or CPCW*.BIN
OAD/OMD COMD*.bin or COMD*.BIN
OTU COTU*.bin or COTU*.BIN
OTUV COTUV*.bin or COTUV*.BIN
OTUE COTUE*.bin or COTUE*.BIN
DSA CDSA*.bin or CDSA*.BIN
OP COPD*.bin or COPD*.BIN
Enter the e x i t command to exit the TELNET service.
Remote Online Download via the ZXONM

E300
Make sure the ZXONM E300 is normally connected to the NE. Select the
menu Maintenance -> Card Software Management -> Update Card
Software to download the Agent program online.
For detailed operations, refer to the manual suite of the ZXONM E300.
Running the Agent Program

1. Switch all the pins of the DIP switch on the NCP/NCPF card to the non-
ON position and then reset the NCP/NCPF card.
2. The red indicator light and green indicator light of the card flash
alternately, indicating the card is being initialized.
3. After the initialization, check the status of indicators and determine the
follow-up operations.
ZXWM M900 and ZXMP M800
¾ The green indicator flashes slowly and the red indicator is off. It
¾ The green indicator is off while the red indicator flashes slowly. It
ZXMP M600
¾ The indicator light with two colors is green and flashes slowly. It
¾ The indicator light with two colors is red and flashes slowly. It

Running Procedures of Blank

NCP/NCPF Card
ZXWM M900/ZXMP M800
A blank NCP/NCPF card refers to a NCP/NCPF card without Agent program.
This section describes the running procedures of a blank NCP/NCPF card in
different supervision systems.
2 M supervision system
TABLE 48 RUNNING PROCEDURES OF A BLANK NCP/NCPF CARD IN A 2 M SUPERVISION

SYSTEM
Step Description Instruction

Switch the DIP2 of the DIP
switch on the NCP/NCPF card to
For the network cable connection, refer to
1 the ON position to set the IP
Table 42.
address as 192.192.192.11
forcibly.
Refer to Appendix B for the configuration
Set the IP address, subnet mask description of address.
2 and gateway IP address through Refer to the section of Modifying the
the TELNET service. Address of NCP/NCPF Card in this
chapter.
Only when the number of available IP
Configure the IP address, subnet addresses is limited, configure the address and
mask and area ID (optional) for area ID for each optical interface manually.
3
four ECC channel optical Refer to the section of ECC Optical Interface
interfaces in the TELNET. Address Configuration in Appendix B for the
operation procedures.
Download the Agent program to
Refer to the section of Downloading the
4 the card through the FTP
Agent/FPGA Programs (FTP) in this Chapter.
service.
Refer to the section of Burning the
Burning the Agent program
5 Agent/FPGA Programs (TELNET) in this
through the TELNET service
chapter.
Switch the DIP2 of the DIP
switch on the NCP/NCPF card to
6 -
the non-ON position to reset the
card.
In the ZXONM E300, create an The IP address/subnet mask set in the
offline NE and install the ZXONM E300 must be same as those
7
NCP/NCPF card by click the NCP configured through the TELNET service.
installation icon. These three steps are implemented in the
Change the status of the NE ZXONM E300. Refer to related manuals of
8 from offline to online in the the ZXONM E300 for detailed operation
ZXONM E300. instructions.


Download the basic NE database
9 to the NCP/NCPF card in the
ZXONM E300
Observe the status of indicators The green indicator flashes slowly and the red
10 on the panel of the NCP/NCPF indicator is off. This indicates that the
card. operation is completed successfully.
100 M supervision system
TABLE 49 RUNNING PROCEDURES OF A BLANK NCPF CARD IN A 100 M SUPERVISION

SYSTEM

Switch the DIP2 of the DIP switch on
Connect the EMS with the equipment
the NCP/NCPF card to the ON position
1 (NET interface of the NCPF card) with a
to set the IP address as 192.192.192.11
network cable.
forcibly.
Refer to Appendix B for the
configuration description of
Set the IP address, subnet mask and address.
2 gateway IP address of the NCPF card
through the TELNET service. Refer to the section of Modifying
the Address of NCP/NCPF Card in
this chapter.
Refer to the section of Downloading the
Download the Agent program to the
3 Agent/FPGA programs (FTP) in this
card through the FTP service.
chapter.
Burning the Agent program through the
4 Agent/FPGA Programs (TELNET) in this
TELNET service
chapter.
Connect the EMS and the
equipment (an idle electrical
Switch the DIP2 of the DIP switch on interface of the OSCF card) with a
5 the NCP/NCPF card to the non-ON network cable.
position to reset the card. Connect an idle electrical interface
of the OSCF card with the NET
interface of the NCPF card.
In the ZXONM E300, create an offline The IP address/subnet mask set in
6 NE and install the NCPF card by click the ZXONM E300 must be same as
the NCP installation icon. those configured through the
TELNET service.
Change the status of the NE from
7 Refer to the section of ECC Optical
offline to online in the ZXONM E300.
Interface Address Configuration in
Download the basic NE database to the Appendix B for the configuration
8
NCPF card in the ZXONM E300 requirements of the optical
interface address of the OSCF card.
These four steps are implemented
Set the IP address, mask and area ID in the ZXONM E300. Refer to
9 for two optical interfaces of the OSCF related manuals of the ZXONM
card E300 for detailed operation
instructions.


10 Reset the OSCF card -
The green indicator flashes slowly and
Observe the status of indicators on the the red indicator is off. This indicates
11
panel of the NCPF card. that the operation is completed
successfully.
ZXMP M600
A blank NCP card refers to an NCP card without Agent program. The
running procedures of a blank NCP card are described in Table 50.
TABLE 50 RUNNING PROCEDURES OF A BLANK NCP CARD
Step Description Reference

Be sure to connect the EMS host to
Switch DIP2 and DIP8 of the DIP switch on
the ETH1 or ETH2 interface of the
the NCP card to the ON position to set the IP
1 NCP card with a network cable
address as 192.192.192.11 forcibly. Reset
before starting the running
the NCP card
procedures.
Refer to Appendix C for the
configuration description of
Set the IP address, subnet mask and address.
2 gateway IP address for the NCP card through
the TELNET service Refer to the section of
Modifying the Address of NCP
Card in this chapter.
Refer to the section of Downloading
Download the Agent program to the NCP
3 the Agent/FPGA Programs (FTP) in
card through the FTP service
this chapter.
Burning the Agent program through the
4 Agent/FPGA Programs (TELNET) in
TELNET service
this chapter.
Switch DIP2 and DIP8 of the DIP switch on
5 the NCP card to the non-ON position to reset -
the card
The IP address/subnet mask
In the ZXONM E300, create an offline NE and
6 set in the ZXONM E300 must
install the NCP card
be same as those configured
through the TELNET service.
Change the status of the NE from offline to These three steps are
7
online in the ZXONM E300 implemented in the ZXONM
E300. Please refer to related
manuals of the ZXONM E300
Download the basic NE database to the NCP
8 for detailed operation
card in the ZXONM E300
instructions.
The indicator with two colors
Observe the status of indicators on the panel flashes in green slowly, which
9
of the NCP card. indicates the operation is completed
successfully.


Appendix A
SDH NE Address Definition

and Route Configuration
This appendix describes how to set the NE IP address and EMS host IP
address. The content in this appendix is applicable to all SDH NEs.
Caution: While configuring initial information of NE, the IP addresses of this NE

and the EMS host should be determined and written to the NE NCP card, which
allows no random modification when the equipment operates normally.
Definition of NE IP Address
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.
FLSM Addressing
FLSM represent for the Full Length Subnet Mask.
1. Definitions of NE IP address and subnet mask

The NE IP address and subnet mask are defined in Table 51.

TABLE 51 DEFINITIONS OF NE IP ADDRESS AND SUBNET M ASK (FLSM)
Item Description Remarks

The NE IP address contains three parts: area code, NE
code, and NCP card 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
NE IP address byte 1.byte 2.byte 3.byte 4 forms the NCP card number.
The area ID combined with NE ID corresponds to the
network address. The NCP card number corresponds to
the host address.
The result got from the logic AND operation of NE IP
Subnet mask 255.byte 2.byte 3.0 address and subnet mask defines the specific meaning of
each byte in NE IP address.
2. Definitions of area ID, NE ID, and card ID

The area ID, NE ID, and card ID are defined in Table 52.
TABLE 52 DEFINITIONS OF AREA ID, NE ID, AND C ARD NUMBER (FLSM)

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

Appendix A - SDH NE Address Definition and Route Configuration
3. Example of NE IP address allocation

The meanings of each byte in the NE IP address are listed in Table 53.
TABLE 53 MEAN INGS OF BYTES IN THE NE IP ADDRESS
NE IP Address Subnet Mask Description

Byte 1 is the area ID; byte 2 and byte 3 form the NE ID; byte 4
255.255.255.0
byte 1. byte 2. byte 3. is the NCP card number.
byte 4 Byte 1 is the area ID; byte 2 is the NE ID; byte 3 and byte 4
255.255.0.0
form the NCP card number.
Taking three NEs as example, when different subnet masks are adopted,
the NE IP addresses are allocated as listed in Table 54.
TABLE 54 NE IP ADDRESS AL LOC ATION ( FLSM)
NE IP Address Allocation
Subnet Mask
NE 1 NE 2 NE 3
255.255.255.0 193.1.1.18 193.1.2.18 193.1.3.18

255.255.0.0 193.1.1.18 193.2.1.18 193.3.1.18
VLSM Addressing
At present, ZTE can employ the techniques of VLSM (Variable Length
Subnet Mask) addressing and CIDR (Classless Inter-Domain Routing) to
define NE IP address, which can greatly save the IP address resource.
Note: VLSM addressing and CIDR techniques need support from the equipment
version. Consult ZTE maintenance personnel for detailed version information.
1. Definitions of NE IP address and subnet mask

The NE IP address and subnet mask are defined in Table 55.
TABLE 55 DEFINITIONS OF NE IP ADDRESS AND SUBNET M ASK (VLSM)

It consists of three parts: area ID, ECC subnet ID, NE ID.
NE IP address byte 1.byte 2.byte 3.byte 4 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.
The result got from the logic AND operation of subnet
mask and NE IP address defines the specific meaning of
Subnet mask byte 1.byte 2.byte 3.byte 4 each byte in the NE IP address.
Byte 1 is generally 255, and byte 4 can be set randomly.

2. Definitions of area ID, ECC subnet ID, and NE ID

The area ID, ECC subnet ID, and NE ID are defined in Table 56.
TABLE 56 DEFINITIONS OF AREA ID, ECC SUBNET ID, AND NE ID (VLSM)

For a complicated ECC subnet, the multi-
area configuration must be adopted due to
the limitation of NE processing capability
Represents for the area that the NE
and the requirement of dynamic route
Area ID belongs to
protocol.
It is byte 1 of NE IP address
Refer to the description of area ID in Table
52 for division principle and requirement of
the area ID.
Represents for the ECC subnet ID that
ECC subnet the NE belongs to A complicated ECC subnet can contain multiple
ID areas.
It is byte 2 of NE IP address
It is the result got from the logic AND
operation of byte 3, 4 of the NE IP
NE ID -
address; and corresponding bytes of
the subnet mask.
3. 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.
4. Definition of card IP address

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

Suppose the NE IP address, i.e. the NCP card IP address is “byte

1.byte 2.byte 3.byte 4”, then the IP addresses of other cards 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)”.
¾ If byte 4 of the subnet mask is not zero, the card 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 cards 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: Since the NCP card 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 should not coexist.
Example of NE Addressing
This section uses the network topology shown in Figure 52 as an example
to describe the network address allocation using the FLSM technique.
FIGURE 52 NETWORK TOPOLOGY

[Scheme 1]
Dividing areas according to Figure 52 can simplify connections between

areas, and the NEs belonging to the backbone area are relatively few.
NEs 1, 2, 3, 4, 5, 6, and 8: they are relatively centralized, among

which there are many connections, and they form a mesh topology.
Therefore, they are allocated into area 193.
NEs 9, 11, and 12: they are relatively centralized and form a ring
topology. Therefore, they are allocated into area 194.
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.
Area definitions and NE IP address configurations are listed in Table 57.
TABLE 57 AR E A DEFINITIONS AND NE IP ADDRESS CONFIGUR ATION S
NEs in the Area

Area Number
NE NE IP Address
Access NE 1 193.1.1.18
NE 2 193.1.2.18
NE 3 193.1.3.18
Area 193 NE 4 193.1.4.18
NE 5 193.1.5.18
NE 6 193.1.6.18
NE 8 193.1.8.18
NE 9 194.1.9.18
Area 194 NE 11 194.1.11.18
NE 12 194.1.12.18
NE 7 192.1.7.18
Area 192 (backbone area)
NE 10 192.1.10.18
Note: The network mask is 255.255.255.0 and the EMS host address is 193.1.1.1.
[Scheme 2]
Since the NEs in Figure 52 are relatively few, all the NEs can be simply
allocated into one area, in which the backbone area is not needed. For
example, they may all be allocated into area 193, and their NE addresses
are listed in Table 58.

TABLE 58 NE IP ADDRESS CONFIGUR ATI ONS OF THE NES ALLOC ATE D INTO ARE A 193
NE NE IP Address NE NE IP Address
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 7 193.1.7.18 NE 8 193.1.8.18
NE 9 193.1.9.18 NE 10 193.1.10.18
NE 11 193.1.11.18 NE 12 193.1.12.18
Note: The network mask is 255.255.255.0 and the EMS host address is 193.1.1.1.
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 should not
exceed 120.
Address/Route Configuration of
the EMS Host
In order to enable EMS to manage all the NEs properly, it is necessary to
set on the EMS host the IP routes that can reach the whole network.
EMS Host Address Configuration

The EMS host address include the EMS host IP address, subnet mask, and
gateway address, as listed in Table 59.
TABLE 59 DEFINITION OF EMS HOST ADD RESS
Item Description Configuration Principle

The result got from the logic AND operation of the
EMS host IP address and the subnet mask must be
Defines the EMS host network within the same network section as the access NE, i.e.
IP address. the EMS host and the gateway NE should have the
address Employs the IP address format: same network ID.
byte 1.byte 2.byte 3.byte 4. The EMS host ID should be less than the gateway NE
host ID (i.e. the NCP card number). The EMS host ID
is suggested to range from 1 to 9, starting from 1.
Defines the subnet mask of the
EMS host.
Subnet Used to divide network section The subnet mask is suggested to be the same as the
mask by performing logic AND subnet mask of access NE.
operation with the EMS host IP
address.

Item Description Configuration Principle

Gateway Defines the gateway address of the
Set the access NE as the gateway NE.
address EMS host.
Consider the network shown in Figure 52, 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 the area 193.
Set the routes on the EMS host to reach NEs in area 192 and area 194.
Route Configuration
There are two methods to configure the routes on EMS:
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.
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 Figure 52,
the method of setting default route or static route for EMS host is as
follows:
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.
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.
Route Configuration Commands

Windows operating system has different route configuration commands
from the Unix operating system.

Windows Operating System

The commonly used commands in Windows 2000 to set routes are listed in
Table 60.
TABLE 60 ROUTE CONFIGURATION COMMANDS IN WINDOWS2000
Operation Purpose Command Line

route add 0.0.0.0 mask 0.0.0.0
Add default route 193.1.1.18
route add 193.1.0.0 mask 255.255.0.0
Add route 193.1.1.18
route add –p 193.1.0.0 mask
Add permanent route 255.255.0.0 193.1.1.18
route delete 193.1.0.0 mask
Delete route 255.255.0.0 193.1.1.18
View route route print
Check if the destination NE ping 192.1.7.18

is reachable
View all the NEs along the tracert 192.1.7.18
route
Caution: Once the computer is restarted, all the routes added by the command of
r o u t e a d d will be lost. Use the command of r o u t e a d d – p 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.
Command line
The commonly used command lines to set route are listed in Table 61.
TABLE 61 ROUTE CONFIGURATION COMMANDS LINES IN UNIX
Operation Purpose Command Line

Add default route route add default 193.1.1.18 1
route add 193.1.0.0 2 5 5 . 2 5 5 . 0 .0
193.1.1.18 1 (HP-UX)
Add route
route add net 193.1.0.0 193.1.1.18 1
(Solaris)
Add permanent route route delete 193.1.0.0
Delete route netstat
View route ping 192.1.7.18
Check if the destination NE tracertroute 192.1.7.18

is reachable

Caution: 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.
Modifying 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 take effect
and be saved permanently after the system is restarted.
The route configuration commands in configuration file are listed in
Table 62.
TABLE 62 ROUTE CONFIGURATION COMMANDS IN CONFIGURATION FILE (HP-UX)
Operation Corresponding
File Modifications
Purpose Command Line
ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]="" route add
Add default ROUTE_GATEWAY[0]= 193.1.1.18 default
route 193.1.1.18 1
ROUTE_COUNT[0]=1
ROUTE_ARGS[0]= ""
ROUTE_DESTINATION[1]=" 193.1.0.0 "
ROUTE_MASK[1]=" 255.255.0.0 " route add
193.1.0.0
Add route ROUTE_GATEWAY[1]= 193.1.1.18
255.255.0.0
ROUTE_COUNT[1]=1 193.1.1.18 1
ROUTE_ARGS[1]=""
¾ Solaris platform
Modify the configuration files listed in Table 63 in the document
editor. The configuration commands in the files will automatically
take effect and be saved permanently after the system is restarted.
TABLE 63 ROUTE CONFIGURATION COMMANDS IN CONFIGURATION FILES (SOLARIS)
File Location Function/Format Example

127.0.0.1 localhost
loghost
Set added IP address
192.192.1.1
/etc/hosts Format: IP_address Host_name hknttserver
Alias 192.192.66.1 hknttsdh
168.69.74.35 almftp

File Location Function/Format Example

192.192.1.0
Set the subnet mask for the added IP 255.255.255.0
address 192.192.66.0
/etc/netmasks
Format: N e t w o r k _ I D 255.255.255.0
Subnet_mask 168.69.74.0
255.255.255.0
Set the active IP address

/etc/hostname.eri0 hknttserver
Format: H o s t _ n a m e
Set the logic IP address. One hostname.eri0:x Define the file of

file needs to be added for each added IP /etc/hostname.eri0:1 as hknttsdh
/etc/hostname.eri0:x address (x starts from one) Define the file of
Format: H o s t _ n a m e /etc/hostname.eri0:2 as almftp
route add net
Add static route. This file will be 192.192.0.0 –netmask
automatically loaded when the system 255.255.192.0
starts. The file name is S96zteRouter. The 192.192.1.6 1
name zteRouter can be defined at your will route add net
/etc/rc2.d/zteRouter except existed file name in the /etc/rc2.d 192.192.64.0 –netmask
directory 255.255.192.0
Format to add one route: r o u t e a d d 192.192.66.18 1
[ host | net ] destination route add net
gateway 168.65.0.0
168.69.74.1 5
/etc/defaultrouter Input the IP address to set the default gateway -


Appendix B
DWDM NE Address
Configurations
This appendix describes the configurations of DWDM NE IP address and of

EMS host IP address. It is applicable to ZXMP M800 and ZXWM M900.
Caution: While configuring initial information of an NE, the IP address of this NE

and the EMS host should be determined and written to the NE’s NCP/NCPF card. It
is forbidden to modify the IP address while the equipment is running normally.
Definition of the NE IP Address

Definition and Configuration Principle
The ZXWM M900 and ZXMP M800 adopt the OSPF protocol, supporting
Classless Inter-Domain Routing (CIDR). The IP address definition of NE
varies in different supervision systems. The definition of the NE IP address
is described in Table 64.
TABLE 64 DEFINITION OF THE NE IP ADDR ESS
Item Definition
IP address The IP address is used to define the network address of an NE in

the format b y t e 1 . b y t e 2 . b y t e 3 . b y t e 4 .
Perform the logical AND operation between the IP address and
mask to divide the network segment. In a same network,
different NEs should be located in different network segment.
Mask
In each network segment, a 2 M supervision system should
reserve five available addresses at lease while a 100 M
supervision system must reserve more than eight available
addresses.

Item Definition
Gateway IP The gateway IP address is used to establish the route between the
address EMS host and the access NE. It is stored in the NCP/NCPF card.
The ECC optical interface address is used to establish the ECC route
ECC optical between NEs. For detailed information about it, please refer to the
interface address section “ECC Optical Interface Address Configuration” in this
Appendix.
When there are numerous NEs, the network can be divided into
several areas to manage NEs. Generally, the number of NEs in an
Area ID area should not exceed 120.
The area ID format is b y t e 1 . b y t e 2 . b y t e 3 . b y t e 4 .
The configuration principle of NE IP address is described in Table 76.
TABLE 65 CONFIGUR ATION PRINCIPLE OF THE NE IP AD DRESS
Configuration Principle
Item
2 M Supervision System 100 M Supervision System
IP address No restriction
It is recommended to set the It is recommended to set the
mask as 255.255.255.240 mask as 255.255.255.224.
so as to get more available IP When the NE is equipped with two
Mask address. Its maximum value is or more OSCF cards, the mask
255.255.255.248. must be no less than
255.255.255.224.
Set the gateway IP address the
same as the IP address of the
It is recommended to set it as OSCF card in the access NE if
Gateway IP
0 . 0 . 0 . 0 if there is no special there is no special requirement.
address
requirement.
IP address of the OSCF card = IP
address of the NE + 1.
ECC optical Refer to the section of ECC Optical Interface Address Configuration in
interface address this Appendix.
The default area ID is 0 . 0 . 0 . 0 . It can be set without restriction.
Area ID Refer to the section of ECC Optical Interface Address Configuration in
this Appendix for detailed configuration procedures.
Configuration Example of the NE IP

Address
Suppose there is such a network topology, as shown in Figure 53. It is a
2 M supervision system.

Appendix B - DWDM NE Address Configurations
FIGURE 53 NETWORK TOPOLOGY
EMS
Area 1
1
3 4 5
6 7
Area 0
(backbone area) 8 9
10 11
12
Area 2
1. Area division
Area 1: The NE 1, 2, 3, 4, 5, 6, and 7 are relatively closer to each
other and many of them are connected with each other. These NEs
compose a topology, which are involved in the area 1.
Area 2: The NE 10, 11 and 12 are relatively closer to each other which
compose a ring topology. These three NEs are involved in the area 2.
Area 0: The area 1 and area 2 are connected through the single
connection between the NE 8 and NE 9. Therefore, the NE 8 and NE 9
are defined as a backbone area (area 0) connecting other areas.
2. IP address configuration
¾ IP address configuration based on area
Based on the area division describes above, the IP address
configuration of these NEs are listed in Table 66. Suppose 16 IP
addresses are reserved in each network segment (i.e. set the
subnet mask to 2 5 5 . 2 5 5 . 2 5 5 . 2 4 0 )
T AB L E 6 6 I P AD D R E S S C O N F I G U R AT I O N O F N E S B AS E D O N AR E A
Area (ID) NE NE IP Address/Mask

Area 1 (0 . 0 . 0 . 1 ) NE 1 (access NE) 193.1.1.1/255.255.255.240
NE 2 193.1.2.17/255.255.255.240
NE 3 193.1.2.33/255.255.255.240

Area (ID) NE NE IP Address/Mask

NE 4 193.1.2.49/255.255.255.240
NE 5 193.1.2.65/255.255.255.240
NE 6 193.1.2.81/255.255.255.240
NE 7 193.1.2.97/255.255.255.240
NE 10 194.1.9.1/255.255.255.240
Area 2 (0 . 0 . 0 . 2 ) NE 11 194.1.9.17/255.255.255.240
NE 12 194.1.9.33/255.255.255.240
NE 8 192.1.7.1/255.255.255.240
Area 0 (0 . 0 . 0 . 0 )
NE 9 192.1.7.17/255.255.255.240
Caution: The available IP address number in the network segment where the
access NE is located can be increased by modigying the mask of the access NE. In
addition, multiple EMS hosts can be accessed to the access NE. Note that this
network segment can not influence the network segment of other NEs.
In this example, if you want to reserve 255 host addresses, set the mask of NE 1
to 2 5 5 . 2 5 5 . 2 5 5 . 0 with the mask of other NEs unchanged.
¾ IP address configuration without area division

If all the NEs as shown in Figure 53 are divided into one area, the
IP address configuration is listed in Table 67.
TABLE 67 IP ADDRESS CONFIGURATION OF NES IN ONE ARE A
NE NE IP Address/Mask NE NE IP Address/Mask
NE 1 193.1.1.1/255.255.255.240 NE 2 193.1.2.81/255.255.255.240
NE 3 193.1.2.1/255.255.255.240 NE 4 193.1.2.97/255.255.255.240
NE 5 193.1.2.17/255.255.255.240 NE 6 193.1.2.113/255.255.255.240
NE 7 193.1.2.33/255.255.255.240 NE 8 193.1.2.129/255.255.255.240
NE 9 193.1.2.49/255.255.255.240 NE 10 193.1.2.145/255.255.255.240
NE 11 193.1.2.65/255.255.255.240 NE 12 193.1.2.161/255.255.255.240
Caution: Although it is very simple to divide all NEs into one area, the efficiency of
ECC route algorithm will be decreased when there are numerous NEs in the area.
Therefore, the single-area division mode is only applciable to cases when there are
not so many NEs. Generally, the number of NEs in an area should not exceed 120.

ECC Optical Interface Address

Configuration
In a DWDM system, the ECC optical interface address must be set for the
establishment of ECC route between NEs so as to ensure the transmission
of supervision information.
Table 68 describes the implementation and number of ECC channels in

different supervision systems.
TABLE 68 RELATIONSHIP BETWEEN ECC AND SUPERVISION SYSTEM
Supervision ECC Optical Direction

Implementation of ECC
System (of an NE)
The HDLC is adopted at the physical layer of
ECC. The 2 M supervision system employs
PCM32 frame format to forward and exchange
ECC data, orderwire voice data, APS data and Each NCP/NCPF card
transparent user channel data between NEs provides four ECC
2M
through the optical supervisory channel. The directions (i.e. four optical
PPP is adopted at the data link layer. interfaces).
Both the OSPF protocol and Agent program run
in the NCP/NCPF card.
Each OSCF card provides
The physical layer of ECC adopts the Ethernet
two ECC optical directions
technology and supports the OSPF protocol,
(i.e. two optical
which runs in the OSCF card.
interfaces).
100 M All data related to the NE, such as the IP
Multiple ECC directions
address, route and OSPF configuration, must
can be obtained by
be downloaded to the OSCF card through the
equipping several OSCF
Agent program of the NCPF card.
cards in an NE.
2 M Supervision System
In a 2 M supervision system, the addresses of four ECC optical interfaces
should be configured. After the IP address of the NE has been confirmed,
the ECC optical interfaces addresses can be allocated automatically by the
system or configured manually.
Automatic Allocation of Optical Interface Address

If the byte 4 of the NE IP address is less than 128, then the IP address
of the optical interface 1 is “(byte 4) + 5”, the IP addresses of the
other three optical interfaces are “(byte 4) + 6”, “(byte 4) + 7” and
“(byte 4) + 8” in order. The area ID is 0 . 0 . 0 . 0 by default.
For example, suppose the IP address of an NE is 1 9 2 . 1 . 1 . 1 . Then the
IP addresses of four optical interfaces are as follows:
Optical interface 1: 1 9 2 . 1 . 1 . 6

If the byte 4 of the NE IP address is equal to or more than 128, then
the IP address of the optical interface 1 is “(byte 4) - 5”, the IP
addresses of the other three optical interfaces are “(byte 4) - 6”,
“(byte 4) - 7” and “(byte 4) - 8” in order. The area ID is 0 . 0 . 0 . 0 by
default.
For example, suppose the IP address of an NE is 1 9 2 . 1 . 1 . 2 4 0 . Then
the IP addresses of four optical interfaces are as follows:
Optical interface 1: 1 9 2 . 1 . 1 . 2 3 5
Manual Configuration of Optical Interface Address
Note: When the number of IP address is limited by the user, it is recommended to

configure the addresses of optical interfaces manually so as to save the IP address
resource.
Use the command i p c f g in the TELNET interface to configure the optical

interface address manually. Enter the TELNET interface first according to
the instruction described in Appendix B.
Note: In the command line, the normal font represents the information displayed
by the system while the Italic font represents the information input by the terminal.
d To configure the optical interface address:
Enter the command i p c f g and press the key Enter.

The system returns the information “I n p u t p o r t n o 0 o r 1 ” to
prompt the user to input the number of port to be configured. Table 69
describes the meaning of the parameter “0” and “1”.

TABLE 69 DESCRIPTION OF CONFIGURATION COMM ANDS
Parameter Description Remark

If the NE IP address has not been
configured before setting the optical
interface IP address, the system will
prompt you to configure the NE IP
address first.
Only configure the IP address, The address of optical interface 1
subnet mask and area ID of should be within the range of 1 ~ 251
optical interface 1. The and the mask is 255.255.255.255. The
0 IP address of all optical interfaces
addresses of other optical
interfaces increase based on should be different from the NE IP
that of the optical interface 1. address.
The configuration of area ID should
meet the requirements in Table 64.
The related data in the Agent database
will be updated after the NE IP
address configuration.
The mask of the NE IP address can not
be set as 0.0.0.0 and
255.255.255.255. Set the optical
Configure the IP address, interface IP address as
subnet mask and area ID for 255.255.255.255.
five ports manually. Among The IP address of each port should be
1 these ports, port 1 is for the different.
NE itself while port 2 ~ port 4
are for four optical interfaces The configuration of area ID should
respectively. meet the requirements in Table 64.
The related data in the Agent database
will be updated after the NE IP
address configuration.
The configuration procedures of optical interface IP address are

introduced through three examples as follows.
¾ Configure the IP address of optical interface 1 after the NE IP
address has been configured.
ZXONM>ipcfg
// Enter the i p c f g command
Input portno 0 or 1:0

// Enter 0 to configure the address of optical interface 1 only. The
addresses of the other optical interfaces will be generated by the
system automatically.
Input start optical port IP Address:192.192.40.4

// Input the IP address of the optical interface 1
Input start optical port Subnet Mask:255.255.255.255

// Input the mask of the optical interface 1
Input start optical port AreaId:0.0.0.1

// Input the area ID of the optical interface 1

set_ip_parms succeed, the change will take effect

after reset NCP.
// The system displays the successful configuration information and prompt
the user to reset the NCP/NCPF card to enable the configuration.
¾ Configure the IP address of the optical interface 1 when the NE IP

address has not been configured.
ZXONM>ipcfg
Input portno 0 or 1:0
Net port not cfg, cfg net port first!

// The system prompts the user that the NE IP address has not been
configured.
Input net port IP Address:192.192.40.1

// Enter the NE IP address
Input net port Subnet Mask:255.255.255.0

// Enter the NE mask
Input net port AreaId:0.0.0.1

// Enter the NE area ID
Set start optical port parms!

// The system prompts that the optical interface IP address can be
configured now.
Input start optical port IP Address:192.192.40.2
Input start optical port Subnet Mask:255.255.255.255
Input start optical port AreaId:0.0.0.1

after reset NCP.
¾ Configure the NE IP address and the IP addresses of four optical

interfaces manually.
ZXONM>ipcfg
Input portno 0 or 1 :1
// Enter 1 to configure five addresses manually
=========================================
// Configure IP address, mask and area ID of Port 1 (NE)
Input Port1 IP Address:192.192.40.1
Input Port1 Subnet Mask:255.255.255.224
Input Port1 AreaId:192.0.0.0
=========================================

// Configure IP address, mask and area ID of Port 2 (optical interface 1)

=========================================
=========================================
=========================================
=========================================
after reset NCP.
d To delete the IP address:
Note: After executing the i p c f g – d command, the address information of all

ports will be deleted from the FLASH memory of the card. However, the NE IP
address and mask will be reserved in the Agent database.
The function of deleting address of port one by one is not supported.
ZXONM>ipcfg -d
delete_ip_parms succeed, the change will take effect
after reset NCP.
// The system displays the successful deletion information and prompt the user
to reset the NCP/NCPF card to enable the configuration.

d To query the addresses of all ports:

ZXONM>ipcfg –a
// Enter the i p c f g – a command and press the Enter key. If the query operation
succeeds, the address information of five ports will be displayed on the screen one
by one: Port 1 (NE), Port 2 ~ Port 5 (optical interface 1 ~ optical interface 4).
Port1:
IP Address:0.192.40.1
Subnet Mask:255.255.255.224
AreaId:192.0.0.0
================================
Port2:
IP Address:192.192.40.4
Subnet Mask:255.255.255.255
AreaId:192.0.0.0
================================
Port3:
IP Address:192.192.40.5
Subnet Mask:255.255.255.255
AreaId:192.0.0.0
================================
Port4:
IP Address:192.192.40.6
Subnet Mask:255.255.255.255
AreaId:192.0.0.0
================================
Port5:
IP Address:192.192.40.7
Subnet Mask:255.255.255.255
AreaId:192.0.0.0
================================
get_ip_parms succeed.
If the query operation fails, the following information will appear.
ZXONM>ipcfg -a
get port1 parms failed, not configure or crc error.
// The system displays the possible cause of query failure.

Manual Configuration of Area ID

In the TELNET interface, the area ID can be set manually through the
i n t e r f a c e command. Please refer to Appendix B for how to enter the
TELNET interface.
Note: The i n t e r f a c e command is used to configure the area ID of each port.

The area ID can also be configured with the IP address and mask through the
i p c o n f i g command.
Command format: i n t e r f a c e p o r t a r e a a r e a i d . The meaning of the

parameters p o r t , a r e a , and a r e a i d are explained in Table 70.
TABLE 70 DESCRIPTION OF PAR AMETERS OF INTERFACE COMMAND
As a number, it represents the port to be configured with the area ID.
0 : To configure the area ID for all ports
port
1 : To configure the area ID for the NE
2 ~ 5 : To configure the area ID for the optical interface 1 ~ 4
As a string, it represents the configuration type of the port. Only the

area
“a r e a ” can be configured now.
It represents the area ID in the format of “b y t e 1 . b y t e 2 . b y t e

areaid
3 . b y t e 4 ”.
For example, suppose the area ID of the NE (Port 1) is 192.192.0.0.
d To configure the area ID of the NE:

ZXONM>interface 1 area 192.192.0.0
set_ip_parms succeed, the change will take effect after

reset NCP.
// The system displays the successful configuration information and prompt the
user to reset the NCP/NCPF card to enable the configuration.
Note: The IP address, mask and area ID can only be valid after restting the
NCP/NCPF card.

100 M Supervision System

In a 100 M supervision system, the optical interface address of the OSCF
card is configured through the ZXONM E300 as follows.
1. In the client operation window of the ZXONM E300, select the NE in the
100 M supervision system to be configured.
2. Select the menu Device Config -> 100M Route Management ->
Card IP Configure to pop up the Card IP Address Config dialog box.
3. Configure the IP address, subnet mask and area ID of optical
interfaces according to the actual networking based on the
configuration principle described in Table 71.
TABLE 71 CONFIGUR ATION PRINCIPLE OF OPTIC AL INTERF ACE ADDRE SS IN A 100 M

SUPERVISION SYSTEM
Item Configuration Principle
It can not conflict with other IP addresses in the network.

If optical interfaces of two OSCF cards are connected with fiber,
the IP addresses of corresponding interfaces should be set in
Optical interface IP the same network segment.
address For those interfaces of two OSCF card which are not connected
with fiber, their IP addresses can not be set in the same
network segment. For example, two optical interfaces of the
same OSCF card can not be configured in the same segment.
The optical interface mask can be configured according to the actual

Optical interface
requirements. The default mask is 255.255.255.0. If the optical
mask
interface is disabled, the subnet mask should be set as 0.0.0.0.
Area ID Refer to the description in Table 64. The default area ID is 0.0.0.0.
4. After the configuration, reset the OSCF card to enable the IP address.
For example, Figure 54 illustrates a ring network to explain the

configuration principle of optical interface IP address in the 100 M
supervision system.
As shown in Figure 54, only the optical connections between OSCF cards
are displayed.

FIGURE 54 OPTIC AL INTERFAC E IP ADDRE SS CONFIGURATION IN A 10 0 M SUPERVISION

SYSTEM
NE 2
NCPF
Optical interface 8:
192.1.1.2/255.255.255.0
OSCF Optical interface 7:
192.1.3.1/255.255.255.0
Optical interface 7:
192.1.1.1/255.255.255.0
NE 1 Optical interface 8:
192.1.3.2/255.255.255
NCPF OSCF
NE 3
Optical interface 8: OSCF

192.1.2.1/255.255.255.0 Optical interface 7:
192.1.2.2/255.255.255.0
NCPF
Area ID: 0.0.0.0 (Default)
Address/Route Configuration of
the EMS Host
To allow the EMS to manage all NEs correctly, the IP address of the EMS
and the IP routes over the whole network must be configured properly in
the EMS host.
EMS Host Address Configuration

The EMS host address includes IP address, mask and gateway address, as
described in Table 72. And Table 73 describes their configuration principle
in different supervision systems.
TABLE 72 DEFINITION OF EMS HOST ADD RESS
Item Description
It represents the network address of the EMS host in the format:

EMS host IP address
byte 1.byte 2.byte 3.byte 4.
The EMS host mask is used to divide the network segment by
EMS host mask
performing AND operation with the EMS host IP address.
The gateway address is used to establish the route between the
Gateway address EMS host and the access gateway. This address is saved in the
EMS host.

T AB L E 7 3 C O N F I G U R AT I O N P R I N C I P LE O F T H E E MS H O ST AD D R E S S
Configuration Principle
Item
2 M Supervision System 100 M Supervision System
It should be configured in the It should be configured in the
same network segment of the same network segment of the
EMS host IP access NE. access NE.
address It can not conflict with the ECC It can not conflict with the IP
optical interface address and NE addresses of the APSF/NCPF
address of the NCP/NCPF card. /OHPF/OSCF card.
EMS host
It is recommended to set the EMS host mask same as that of the access NE.
mask
Configure it as the IP address of the
Gateway Configure it as the IP address of the OSCF card of the access NE.
address access NE. The IP address of the OSCF card is
“NE IP address +1”.
Take the network illustrated in Figure 53 as an example. Set the addresses

of the EMS host as follows.
EMS host IP address: 193.1.1.2

EMS host mask: 255.255.255.240
Gateway address: 193.1.1.1
After setting the EMS host addresses, the route between the EMS host and
the access NE is available. Then configure other routes between the EMS
host and other NEs.
Route Configuration
Two methods are provided on the EMS to configure routes.
Run the OSPF protocol on the EMS host

Advantage: It is unnecessary to configure any route by users.
Disadvantage: There may be some invalid or repeated routes
propagated to the network, which make some NEs unreachable or
result in too large route tables. The dynamic routes will increase the
load of the EMS host.
Note: It is recommended to implement the route configuration by setting static

routes or default routes so as to filter large amount of IP packets unrelated to the
current network, thus improving the efficiency of the EMS.
Configure default routes or static routes

Default routes or static routes should be pointed to the NE directly
connected to the EMS host. In addition, delete other possible repeated
routes.

Take the network illustrated in Figure 53 as example. Suppose the EMS

software is installed in a Windows operating system. Configure the
default route and static routes as follows.
¾ Default route configuration
route add 0.0.0.0 mask 193.1.1.1
The meaning of this route is that all IP packets having no routes on

the local must pass through NE 1.
¾ Static route configuration
route add 193.1.0.0 mask 255.255.0.0 193.1.1.1
route add 194.1.0.0 mask 255.255.0.0 193.1.1.1
route add 192.1.0.0 mask 255.255.0.0 193.1.1.1
The meaning of these routes is that all IP packets to be sent to the

network 193.1, 194.1 and 192.1 must pass through NE 1.
Route Configuration Commands

Windows operating system has different route configuration commands
from the Unix operating system.
Refer to the section of Route Configuration Commands in Appendix A for

the route configuration commands commonly used.


Appendix C
ZXMP M600 Address

Configurations
This appendix describes how to set the IP address for the NCP card of the
ZXMP M600 NE and that of the EMS host computer.
Caution: While configuring initial information of an NE, the IP address of this NE

and the EMS host should be determined and written to the NE’s NCP card. It is
forbidden to modify the IP address while the equipment is running normally.
ECC Function of NCP Card

The NCP card of the ZXMP M600 provides the Embedded Control Channel
(ECC) for the NE, in addition to the NE control function.
Functions
While performing the ECC function, the NCP card is equivalent to a 5-
port Ethernet switch. Table 74 lists the types and functions of Ethernet
interfaces on the NCP card.
TABLE 74 TYPES AND FUNCTIONS OF ETHERNET INTERFACES ON THE NCP CARD
Interface Type Position ID Function

ETH1
Ethernet 10M/100 On the card panel Connected to the local EMS host
ETH2
electrical M
interface adaptive Connected to other Ethernet
Inside the card -
electrical interfaces of the NCP card
Ethernet AOSC Connected to other NEs, thus
100M full
optical On the card panel establishing the supervisory channel
duplex BOSC
interface between NEs

The ECC connection of between ZXMP M600 equipment is equivalent to

a switching network composed of multiple 5-port Ethernet switches.
The NCP (Agent program) of each NE is connected with one Ethernet
electrical port of the switch.
The ECC of the ZXMP M600 uses L2 switching. The IP address of the
NCP card (that is, the IP address of the NE) only needs to meet the
TCP/IP between the NCP card and the EMS.
Connection of Ethernet interfaces
When the ETH1 and ETH2 interfaces on the NCP card are used at the
same time, they should not form a loop, and should not be connected
directly. Figure 55 illustrates an incorrect connection through which
that the two interfaces of the NCP form a loop via the HUB.
FIGURE 55 INCORRECT CONNECTION OF ETHERNET INTERFACES
Usually, only one Ethernet electrical interface is used, with the other
one not connected. When you need to connect the equipment to a
Local Craft Terminal (LCT), the idle interface can be used for this
connection.
The Ethernet electrical interfaces of the NCP card can automatically
identify network cables and has the cross-connection function.
Therefore, both crossover and straight-through network cables can be
used for the direct connection between the EMS computer (or HUB)
and the NCP card.
Address Definition
The address definition includes the definition of the address of the NE NCP
card and that of the EMS host IP address.
Address of the NCP Card

The address of the NCP card of the ZXMP M600 includes the IP address of
the NCP card, subnet mask, and default gateway IP address.
The definitions of these addresses are shown in Table 75.

Appendix C - ZXMP M600 Address Configurations
TABLE 75 AD DRESS DEFINITION OF THE NCP CARD
Address Format Requirements

Complying with the IP address definition in
IP address byte1.byte2.byte3.byte4
the TCP/IP
Complying with the subnet mask definition in
Subnet mask byte1.byte2.byte3.byte4
the TCP/IP
If the EMS and the NE are connected
directly or via the HUB, the IP address
of the gateway should be set to 0.0.0.0.
That means the NCP card will discard IP
packets received from another network
Default segment.
gateway IP byte1.byte2.byte3.byte4 If the EMS and the NE are connected via
address a DCN or another network, the gateway
IP address should be set to the IP
address of the router port on the edge.
That means the NCP card will forward IP
packets received from other network
segments to the gateway.
It is generated automatically according to
the IP address and other related information
MAC address -
of the NCP card, so there is no conflict in
MAC addresses.
IP Address of the EMS Host

The network card of the EMS host must be configured with a correct IP
address for the EMS to manage all NEs correctly. This IP address should
contains the IP address of the EMS server and subnet mask.
The format is Byte1.Byte2.Byte3.Byte4, which complies with the IP

address definition in the TCP/IP.
Typical Cases of Address Setting

This section describes how to set the EMS IP address and NE address in
cases with default gateway disabled and cases with default gateway
enabled.
Cases with Default Gateway Disabled

When the EMS computer and the NE are connected directly or via the HUB,
the default gateway is disabled.
The address setting should meet the following requirements:
There is no access NE, and all the NEs are peers. The IP address of the
EMS host and that of the connected NE must be on the same network
segment and comply with the TCP/IP.

The IP addresses of the NEs must be on the same network segment.

Continuous IP addresses can be located to the NEs, which must comply
with the TCP/IP.
The gateway IP address must be set to 0.0.0.0.
The typical networking when the default gateway is disabled is shown in

Figure 56, where the ZXMP M600 and the EMS host are directly connected
with a straight-through or crossover network cable.
FIGURE 56 NETWORKING WHEN DEFAULT GATEW AY DISABLED
ETH1 or ETH2
ZXMP M600
EMS
ZXMP M600 network
Case 1 Suppose the ZXMP M600 network in the Figure 56 consists of 20 NEs (NE
1-NE 20). You can set the IP addresses of the EMS host and the NEs as
shown in Table 76.
TABLE 76 CASE 1: IP ADD RESSES OF THE EMS HOST AN D 20 NES
EMS/NE IP Address Subnet Mask Gateway IP Address

EMS host 192.168.1.1 255.255.255.224 -
NE 1 192.168.1.2 255.255.255.224 0.0.0.0
NE 2 192.168.1.3 255.255.255.224 0.0.0.0
… … … …
NE 20 192.168.1.21 255.255.255.224 0.0.0.0
Case 2 Suppose the ZXMP M600 network in the Figure 56 consists of 200 NEs (NE
1-NE 200). You can set the IP addresses of the EMS host and the NEs as
shown in Table 77.

EMS host 192.168.1.1 255.255.255.0 -
NE 1 192.168.1.2 255.255.255.0 0.0.0.0
NE 2 192.168.1.3 255.255.255.0 0.0.0.0
… … … …
NE 200 192.168.1.201 255.255.255.0 0.0.0.0

Case 3 Suppose the ZXMP M600 network in the Figure 56 consists of 2000 NEs
(NE 1-NE 2000). You can set the IP addresses of the EMS host and the
NEs as shown in Table 78.

EMS host 10.78.1.1 255.255.0.0 -
NE 1 10.78.1.2 255.255.0.0 0.0.0.0
NE 2 10.78.1.3 255.255.0.0 0.0.0.0
… … … …
NE 253 10.78.1.254 255.255.0.0 0.0.0.0
NE 254 10.78.2.1 255.255.0.0 0.0.0.0
… … … …
NE 2000 10.78.7.223 255.255.0.0 0.0.0.0
Cases with Default Gateway Enabled

The default gateway is used for complicated networking cases. For
example, the ZXMP M600 and the ZXMP M800 with 100 M supervisory
channel are used in mixed networking, or the ZXMP M600 is managed
remotely through a DCN network. In such cases, the address of NE
contains IP address, subnet mask and gateway IP address.
The address setting should meet the following requirements:
NE IP address, subnet mask: They can be set in the same way as that
when the default gateway is disabled. For details, see the section
“Cases with Default Gateway Disabled”.
Gateway IP address: Since the ZXMP M600 has no access NE, every NE
must be configured with the gateway. The specific setting depends on
the actual networking condition.
Case 1 Mixed networking of the ZXMP M600 and ZXMP M800 (100 M supervisory
channel)
At the connection point between the ZXMP M600 and the ZXMP M800, the
Ethernet electrical interface on the NCP card of the ZXMP M600 is
connected to that on the OSCF card of the ZXMP M800 via a straight-
through or crossover network cable, as shown in Figure 57.
The default gateway IP address is the IP address of the Ethernet electrical

interface on the OSCF card of the ZXMP M800 on the edge.

FIGURE 57 NETWORKING WHEN DEFAULT GATEW AY ENABLED (MIXED NETWORKING)
EMS
Ethernet optical
interface on OSCF ZXMP M800
board
ZXMP M600 network ZXMP M800 (100M) network
Network cable
ZXMP M600 ZXMP M800
ETH1 or ETH2
Case 2 The EMS manages the ZXMP M600 NEs through the DCN remotely
At the edge between the ZXMP M600 network and the DCN, the Ethernet
electrical interface on the NCP card of the ZXMP M600 is connected to the
LAN port on the DCN router via a straight-through or crossover network
cable, as shown in Figure 58.
The default gateway IP address is the IP address of the LAN port on the
edge router.
FIGURE 58 NETWORKING WHEN DEFAULT GATEW AY ENABLED (VIA DCN)
LAN port EMS
ZXMP M600 network Router n
Network cable
ZXMP M600 DCN
Router 1
ETH1 or ETH2
As shown in Figure 58, suppose the ZXMP M600 network consists of 200
NEs (NE 1-NE 200), the EMS host is located in another city, and it is
connected to the ZXMP M600 through the DCN. The IP address of the EMS
host is 10.78.100.254, and its subnet mask is 255.255.255.0. The IP
address of the LAN port on Router1 (that is, the router port connected to
the ZXMP M600) is 192.168.1.254, and its subnet mask is 255.255.255.0.
Set the IP addresses of the EMS host and NEs according to Table 79.

TABLE 79 IP ADDRESSES OF THE EMS HOST AND 200 NES WITH DEFAULT GATEWAY
ENABLED

EMS host 10.78.100.254 255.255.255.0 -
NE 1 192.168.1.2 255.255.255.0 192.168.1.254
NE 2 192.168.1.3 255.255.255.0 192.168.1.254
… … … …
NE 200 192.168.1.201 255.255.255.0 192.168.1.254


Appendix D
Abbreviations
Abbreviation Full Name

ADM Add/Drop Multiplexer
Agent
AU-n Administrative Unit, level n
AUG Administrative Unit Group
BA Booster Amplifier
C-n Container-n
CP Connection Point
ECC Embedded Control Channel
EDFA Erbium Doped Fiber Amplifier
EMC ElectroMagnetic Compatibility
EMI ElectroMagnetic Interference
EML Network Element Management Layer
EMS Equipment Management System
ES Errored Second
GUI Graphical User Interface
IP Internet Protocol
International Telecommunication Union-Telecommunication
ITU-T
Standardization Sector
LAN Local Area Network
LA Line Amplifier
LCT Local Craft Terminal
MC Matrix Connection
MCU Management Control Unit
MM Multi Mode
MS Multiplex Section
NC Network Connection
NE Network Element


OA Optical Amplifier
OAM Operation, Administration and Maintenance
OFA Optical Fiber Amplifier
OHA OverHead Access
PA Pre-Amplifier
PCB Printed Circuit Card
PCM Pulse Code Modulation
PDH Plesiochronous Digital Hierarchy
PGND Protection GND
PJE+ Positive Pointer Justification Event
PJE- Negative Pointer Justification Event
RS Regenerator Section
RSOH Regenerator Section OverHead
RST Regenerator Section Termination
SDH Synchronous Digital Hierarchy
SEC SDH Equipment Clock
SES Severely Errored Second
SM Single Mode
SMCC Subnet Management Control Center
SML Service Management Layer
SMN SDH Management Network
SMS SDH Management Subnet
Sn Higher order VC- layer n (n=3, 4)
SNC Sub-Network Connection
SNCP Sub-Network Connection Protection
SPRING Shared Protection Ring
SPI SDH Physical Interface
SSM Synchronization Status Message
STM-N Synchronous Transport Module, level N (N=1, 4, 16, 64)
TMN Telecommunications Management Network
TS Time Slot
TSA Time Slot Assignment
TU-m Tributary Unit, level m
TUG-m Tributary Unit Group, level m
UAS Unavailable Second
UNI User Network Interface
VC Virtual Channel

Appendix D - Abbreviations

VC Virtual Container
VC-n Virtual Container, level n
VLAN Virtual Local Area Network
VP Virtual Path
WDM Wavelength Division Multiplexing


Figures
Figure 1 GDownloader Page of Smcc GDownloader Software ............................20

Figure 2 Set up a Connection .......................................................................21
Figure 3 Dialog Box for Confirming the Database Upgrade................................23
Figure 4 Window for Network Parameter Configurations-Net Para Config ............24
Figure 5 Window for System Parameter Configurations-System Para Config ........25
Figure 6 System Information Window............................................................26
Figure 7 Reset Confirmation ........................................................................27
Figure 8 Monitor Page of the Smcc GDownloader ............................................28
Figure 9 Local Download Flow Chart of Smcc GDownloader ..............................31
Figure 10 Remote Upgrade Flowchart of Smcc GDownloader.............................32
Figure 11 Flowchart of Preparations for Local Data Remake (ZXMP S380/S390) ..38
Figure 12 dbman Interface ..........................................................................45
Figure 13 Change NE Software Version Interface ............................................45
Figure 14 Change Ne Software Version Interface (Selecting All NEs is not Allowed)
........................................................................................................46
Figure 15 SELECT NE Interface ....................................................................46
Figure 16 Change Ne Software Version Interface (Converting the Version of the
Designated NE) ..................................................................................47
Figure 17 NCP PCB Board ............................................................................62
Figure 18 Local Upgrade Flowchart of ZXMP S385 ...........................................64
Figure 19 Flowchart of Local Upgrade Preparations..........................................65
Figure 20 Erase the Database ......................................................................66
Figure 21 Erase the Chip Area Which Saves the Application Program .................67
Figure 22 Erase the Chip Area Which Saves the Logic Program .........................67
Figure 23 Configure the NE Related Information .............................................67
Figure 24 Format the CF Card ......................................................................68
Figure 25 Local Download of NCP Application to NE .........................................70
Figure 26 Local Upgrade of NCP Application to NE ...........................................71
Figure 27 Version Information for Local Upgrade of Card Application..................72
Figure 28 Download DB Dialog Box of the EMS ...............................................73
Figure 29 Card Management Dialog Box ........................................................74
Figure 30 Card Special Version Dialog Box .....................................................75
Figure 31 Remote Upgrade Flowchart............................................................76
Figure 32 MasterSlaveBrd Switch Dialog Box ..................................................77
Figure 33 Confirming the Address of the Master NCP Card................................78
Figure 34 Remote Upgrade of Application ......................................................79
Figure 35 Verifying the Upgraded Program.....................................................80
Figure 36 Try Run of the Program.................................................................82
Figure 37 Verifying the Program that Passed the Try Run .................................83
Figure 38 Activating the Program .................................................................84
Figure 39 Verifying the Activated Program .....................................................85
Figure 40 Switching to the Standby NCP Card ................................................86
Figure 41 Local Upgrade Flowchart of ZXMP S330/S325...................................91
Figure 42 Flowchart of Local Upgrade Preparations..........................................92
Figure 43 Remote Upgrade Flowchart of ZXMP S330/S325 ...............................99
Figure 44 Local Upgrade Flowchart of ZXMP S200 ......................................... 109
Figure 45 Flowchart of Local Upgrade Preparations........................................ 110
Figure 46 Interface for Local Upgrade of NCP Application of ZXMP S200 ........... 114
Figure 47 Remote Upgrade Flowchart of ZXMP S200...................................... 118

Figure 48 Card Management Dialog Box of ZXMP S200 .................................. 126

Figure 49 Local NCP/NCPF Reconfiguration Flow ........................................... 130
Figure 50 Local Download Flowchart of the Agent/FPGA Programs ................... 135
Figure 51 Remote Online Download Flowchart of the Agent Program................ 136
Figure 52 Network Topology ...................................................................... 151
Figure 53 Network Topology ...................................................................... 161
Figure 54 Optical Interface IP Address Configuration in a 100 M Supervision
System ........................................................................................... 171
Figure 55 Incorrect Connection of Ethernet Interfaces ................................... 176
Figure 56 Networking When Default Gateway Disabled .................................. 178
Figure 57 Networking When Default Gateway Enabled (Mixed Networking) ....... 180
Figure 58 Networking When Default Gateway Enabled (Via DCN) .................... 180

Tables
Table 1 Typographical Conventions ............................................................. xiii

Table 2 Mouse Operation Conventions ......................................................... xiii
Table 3 Safety Signs................................................................................. xiv
Table 4 Relationship between ZXMP S380/S390 Software Version and EMS ....... 35
Table 5 States of ZXMP S380/S390 NCP Card................................................ 37
Table 6 Format of the SDH.CFG File ............................................................. 40
Table 7 Working States of ZXMP S100 NCP Card............................................ 49
Table 8 Division of Card Storage Area .......................................................... 50
Table 9 Parameter Description for Upgrading an NE’s Storage Area .................. 53
Table 10 Upload Parameter Description ........................................................ 54
Table 11 Parameter Description for Setting a Storage Area as Trial Running ...... 55
Table 12 Parameter Description for Activating a Storage Area.......................... 55
Table 13 Parameter Description for Erasing a Storage Area ............................. 56
Table 14 Input Principles of NE Related Parameters........................................ 68
Table 15 Parameters of the Command d-upgrade .......................................... 70
Table 16 Parameters of the Command d-get-status........................................ 71
Table 17 Descriptions of Parameters that Need to be Verified for Local Upgraded
Card Program Version ........................................................................ 72
Table 18 Parameters in the Standby Area that Need to be Verified ................... 81
Table 19 Parameters of the Command d-try .................................................. 81
Table 20 Parameters in the Original Standby Area that Need to be Verified after the
Try Run ............................................................................................ 83
Table 21 Parameters of the Command d-active.............................................. 84
Table 22 Descriptions of Parameters that Need to be Verified after Activation .... 85
Table 23 Input Principles of NE Related Parameters........................................ 94
Table 24 Parameters of the Command d-upgrade (ZXMP S330/S325) ............... 95
Table 25 Parameters of the Command d-get-status........................................ 96
Table 26 Descriptions of Fields that Need to be Verified for Local Upgrade ......... 97
Table 27 Descriptions of Fields in the Standby Area that Need to be Verified .... 101
Table 28 Parameters of the Command d-try ................................................ 102
Table 29 Descriptions of Fields in the Standby Area that Need to be Verified after
the Try Run .................................................................................... 103
Table 30 Parameters of the Command d-active............................................ 104
Table 31 Descriptions of Fields that Need to be Verified after Activation .......... 105
Table 32 Input Principles of NE Related Parameters...................................... 112
Table 33 Parameters of the Command d-upgrade (ZXMP S200) ..................... 113
Table 34 Parameters of the Command d-get-status (ZXMP S200)................... 115
Table 35 Descriptions of Fields that Need to be Verified for Local Upgrade ....... 115
Table 36 Descriptions of Fields in the Standby Area that Need to be Verified .... 121
Table 37 Parameters of the Command d-try (ZXMP S200)............................. 121
Table 38 Descriptions of Fields in the Standby Area that Need to be Verified after
the Try Run .................................................................................... 123
Table 39 Parameters of the Command d-active (ZXMP S200) ........................ 124
Table 40 Descriptions of Fields that Need to be Verified after Activation .......... 124
Table 41 Definition of DIP Switch on NCP/NCPF Card .................................... 127
Table 42 Network Cable Connection for Local NCP/NCPF Reconfiguration ......... 130
Table 43 Network Connection for Remote Online Download ........................... 136
Table 44 Definition of the Parameter portno ................................................ 139
Table 45 Definition of the Parameter workmode........................................... 139
Table 46 Definition of the Parameter workmode........................................... 141

Table 47 Requirements for Program File Name of Cards in the ZXMP M600 ...... 141
Table 48 Running Procedures of a Blank NCP/NCPF Card in a 2 M Supervision
System .......................................................................................... 143
Table 49 Running Procedures of a Blank NCPF Card in a 100 M Supervision System
..................................................................................................... 144
Table 50 Running Procedures of a Blank NCP Card ....................................... 145
Table 51 Definitions of NE IP Address and Subnet Mask (FLSM) ..................... 148
Table 52 Definitions of Area ID, NE ID, and Card Number (FLSM)................... 148
Table 53 Meanings of Bytes in the NE IP Address ......................................... 149
Table 54 NE IP Address Allocation (FLSM) ................................................... 149
Table 55 Definitions of NE IP Address and Subnet Mask (VLSM) ..................... 149
Table 56 Definitions of Area ID, ECC Subnet ID, and NE ID (VLSM) ................ 150
Table 57 Area Definitions and NE IP Address Configurations .......................... 152
Table 58 NE IP Address Configurations of the NEs Allocated into Area 193 ....... 153
Table 59 Definition of EMS Host Address..................................................... 153
Table 60 Route Configuration Commands in Windows2000 ............................ 155
Table 61 Route Configuration Commands Lines in Unix ................................. 155
Table 62 Route Configuration Commands in Configuration File (HP-UX)........... 156
Table 63 Route Configuration Commands in Configuration Files (Solaris) ......... 156
Table 64 Definition of the NE IP Address..................................................... 159
Table 65 Configuration Principle of the NE IP Address ................................... 160
Table 66 IP Address Configuration of NEs Based on Area............................... 161
Table 67 IP Address Configuration of NEs in One Area .................................. 162
Table 68 Relationship between ECC and Supervision System ......................... 163
Table 69 Description of Configuration Commands ........................................ 165
Table 70 Description of Parameters of interface Command ......................... 169
Table 71 Configuration Principle of Optical Interface Address in a 100 M
Supervision System ..........................................................................170
Table 72 Definition of EMS Host Address......................................................171
Table 73 Configuration Principle of the EMS Host Address ..............................172
Table 74 Types and Functions of Ethernet Interfaces on the NCP Card .............175
Table 75 Address Definition of the NCP Card ................................................177
Table 76 Case 1: IP Addresses of the EMS Host and 20 NEs ...........................178
Table 77 Case 2: IP Addresses of the EMS Host and 200 NEs..........................178
Table 78 Case 3: IP Addresses of the EMS Host and 2000 NEs ........................179
Table 79 IP Addresses of the EMS Host and 200 NEs with Default Gateway Enabled
......................................................................................................181

sjzl20060795-Unitrans+ZXONM+E300 (V3 (1) 17) +Operation+Manual PDF

Uploaded by

Document Information

Original Title

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

sjzl20060795-Unitrans+ZXONM+E300 (V3 (1) 17) +Operation+Manual PDF

Uploaded by

Copyright:

Available Formats

ZXONM E300

Unified EMS/SNMS of Optical Network

Copyright © 2005 ZTE CORPORATION.

Date Revision No. Serial No. Description

Thank you for your cooperation!

About this Operation Manual ...................................................................xi

Smcc GDownloader Operations.............................................................................20

NCP Working Status Switching..............................................................................29

Downloading Database via EMS Software ..............................................................29

Operation Precautions ..........................................................................................33

Local Data Remake..............................................................................................37

Local/Remote Online Download.............................................................................41

Clearing NCP Database ........................................................................................43

Download/Configuration Command Set .................................................................52

Local Upgrade .....................................................................................................64

Remote Upgrade .................................................................................................75

Local Upgrade .....................................................................................................91

Remote Upgrade .................................................................................................98

Local Upgrade ................................................................................................... 109

Remote Upgrade ............................................................................................... 117

Precautions ....................................................................................................... 125

Local Download ................................................................................................. 134

Running Procedures of Blank NCP/NCPF Card....................................................... 143

Example of NE Addressing.................................................................................. 151

ECC Optical Interface Address Configuration ........................................................ 163

Address/Route Configuration of the EMS Host ...................................................... 171

Typical Cases of Address Setting ......................................................................... 177

About the Manual Suite

1. Management scope of ZXONM E300 (V3.17)

Manual Name Function

Confidential and Proprietary Information of ZTE CORPORATION xi

Purpose of this Manual

Chapter 1 ZXMP S320/S360 Agent Configurations, describes the download

Chapter 2 ZXMP S380/S390 Agent Configurations, describes the download

Chapter 3 ZXMP S100 Agent Configurations, describes the equipment

Chapter 4 ZXMP S385 Agent Configurations, describes the upgrade

Chapter 5 ZXMP S330/S325 Agent Configurations, describes the upgrade

Chapter 6 WDM Equipment Agent Configurations, describes the upgrade

Appendix A SDH NE Address Definitions and Route Configurations,

Appendix B DWDM NE Address Configurations, describes the address

Appendix C ZXMP M600 Address Configurations, describes the NE

Appendix D Abbreviations, gives the abbreviations and their corresponding

xii Confidential and Proprietary Information of ZTE CORPORATION

TABLE 1 TYPOGRAPHICAL CONVENTIONS

Note: Provides additional information about a certain

Checkpoint: Indicates that a particular step needs to

Tip: Indicates a suggestion or hint to make things

Mouse Operation Conventions

Confidential and Proprietary Information of ZTE CORPORATION xiii

Safety Signs Meaning

Erosion: Beware of erosion.

Electric shock: There is a risk of electric shock.

Electrostatic: The device may be sensitive to static

Microwave: Beware of strong electromagnetic field.

Laser: Beware of strong laser beam.

No flammables: No flammables can be stored.

No touching: Do not touch.

No smoking: Smoking is forbidden.

xiv Confidential and Proprietary Information of ZTE CORPORATION

How to Get in Touch

Confidential and Proprietary Information of ZTE CORPORATION xv

This page is intentionally blank.

xvi Confidential and Proprietary Information of ZTE CORPORATION

DOWNLOAD state: Bits 1 – 4 are all set to ON.