Sjzl20090609-Unitrans ZXONM E300 (V3.19R2) Maintenance Manual - 516854

ZXONM E300
Unified EMS/SNMS of Optical Network
Maintenance Manual
Version 3.19R2
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 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE
CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality
obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are
disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or
non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance
on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the
subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its
licensee, the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Date
Revision No.
Serial No.
Description
Jun. 18, 2007
R1.0
sjzl20071700
First edition
May. 4, 2008
R1.0
sjzl20081489
Upgrade parts of the operating

interfaces according to the new EMS
version
May. 30, 2009
R1.0
sjzl20090609
Upgrade parts of the operating

interfaces according to the new EMS
version
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
Name
Product
Version
Manual
ZXONM E300 (V3.19R2) Unified EMS/SNMS of Optical Network Maintenance

Document
Revision Number
V3.19R2
R1.0
Equipment Installation Date

Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good
Your
evaluation of
this
documentation
Fair
Average
Poor
Bad
N/A
Bad
N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Good
Fair
Average
Poor
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:
Your
suggestions for
improvement
of this
documentation
Improve the overview/introduction
Make it more concise/brief
Improve the Contents

procedures/tutorials
Add more step-by-step
Improve the organization
Add more troubleshooting information
Include more figures
Make it less technical
Add more examples
Add more/better quick reference aids
Add more detail
Improve the index
Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# 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 Manual .......................................................................................i
Purpose .................................................................................................................. i
Intended Audience...................................................................................................i
Prerequisite Skill and Knowledge...............................................................................i
What is in this Manual .............................................................................................. i
Related Documentation........................................................................................... ii
Conventions...........................................................................................................iii
How to Get in Touch ............................................................................................... v
Customer Support...................................................................................................................v
Documentation Support...........................................................................................................v
Chapter 1........................................................................................ 1
Maintenance Overview...............................................................................1
Maintenance Classification .......................................................................................1
Routine Maintenance ...............................................................................................................1
Emergency Maintenance..........................................................................................................1
Management Rules for EMS.....................................................................................1
Chapter 2........................................................................................ 3
Routine Maintenance .................................................................................3
Operation Instructions.............................................................................................3
Managing Users......................................................................................................3
Purpose ..................................................................................................................................3
Operations ..............................................................................................................................3
Inspection Criteria ...................................................................................................................4
Troubleshooting ......................................................................................................................4
Checking EMS Connection .......................................................................................4

Purpose ..................................................................................................................................4
Operations ..............................................................................................................................4
Monitoring Topology ...............................................................................................5

Purpose ..................................................................................................................................5
Operations ..............................................................................................................................5

Monitoring Alarms...................................................................................................6
Purpose ..................................................................................................................................6
Operations ..............................................................................................................................6
Monitoring Performance ..........................................................................................6

Purpose ..................................................................................................................................6
Operations ..............................................................................................................................6
Querying System Configuration ...............................................................................7

Purpose ..................................................................................................................................7
Operations ..............................................................................................................................7
Querying User Operation Log...................................................................................8

Purpose ..................................................................................................................................8
Operations ..............................................................................................................................8
Printing Report .......................................................................................................8

Purpose ..................................................................................................................................8
Operations ..............................................................................................................................8
Saving/Printing Alarm/Performance Messages...........................................................9

Purpose ..................................................................................................................................9
Operations ..............................................................................................................................9
Troubleshooting ....................................................................................................................10
Backing up Data ................................................................................................... 10

Purpose ................................................................................................................................10
Operations ............................................................................................................................10
Inspection Criteria .................................................................................................................11
Restoring Data ..................................................................................................... 11

Purpose ................................................................................................................................11
Operations ............................................................................................................................11
Inspection Criteria .................................................................................................................12
Chapter 3...................................................................................... 13
Maintenance of Operating System ......................................................... 13
Running Environment Requirements of ZXONM E300 .............................................. 13
Unix Platform ........................................................................................................................13
Windows Platform .................................................................................................................14
Installation and Configuration of Unix ..................................................................... 16

Installing Unix .......................................................................................................................16
Configuring Unix....................................................................................................................16
Installing Patch......................................................................................................................18
Configuring Database on HP-UX Platform ...............................................................................20
Installation and Configuration of Windows............................................................... 22

FAQ..................................................................................................................... 22
Chapter 4...................................................................................... 25
EMS Installation and Upgrade ................................................................ 25
Installation Flow ................................................................................................... 25
Upgrading ZXONM E400 to ZXONM E300 ............................................................... 26
Preparing for Upgrade ...........................................................................................................26
Upgrade Operations ..............................................................................................................27
Upgrading ZXONM E300........................................................................................ 28

Applicable Scope ...................................................................................................................29
Preparing for Upgrade ...........................................................................................................29
Upgrading EMS in Unix ..........................................................................................................29
Upgrading EMS in Windows ...................................................................................................36
Sharing Data between EMS in Unix and EMS in Windows ........................................................39
Setting EMS Parameters in Windows ...................................................................... 41

Configuring Communication between GUI and Manager ..........................................................41
Configuring Communication between DB and Manager ...........................................................41
Configuring Synchronization of SYBASE Database...................................................................42
Configuring SQL Server Database ..........................................................................................42
Setting EMS Parameters in Unix............................................................................. 44

Setting Dynamic Route..........................................................................................................44
Configuring Communication between GUI and Manager ..........................................................45
Configuring Communication between DB and Manager ...........................................................45
Configuring Database Synchronization....................................................................................46
FAQ..................................................................................................................... 46
FAQ for EMS Installation in HP-UX..........................................................................................46
FAQ for EMS Installation in SUN .............................................................................................49
Other Installation FAQ ...........................................................................................................52
Chapter 5...................................................................................... 57
Maintenance of EMS ................................................................................ 57
EMS Connection Fault ........................................................................................... 57

Common Faults.....................................................................................................................57
Typical Faults and Analysis.....................................................................................................58
Database Fault ..................................................................................................... 59

Manager Fault ...................................................................................................... 60
Agent Fault .......................................................................................................... 60
Other Faults ......................................................................................................... 61
Setting Environment Variables ............................................................................... 62
Overview ..............................................................................................................................62
Setting Environment Variable.................................................................................................63
Appendix A ................................................................................... 67
DBMAN Operations.................................................................................. 67
DBMAN Overview ................................................................................................. 67
Major Functions.....................................................................................................................67
Launching DBMAN.................................................................................................................67
DBMAN Main Window in Windows 2000 .................................................................................68
Database Server Management Operations .............................................................. 70

Starting Database Server.......................................................................................................71
Stopping Database Server .....................................................................................................71
Using isql Tool.......................................................................................................................72
Using isql Tool with Output File...............................................................................................72
Configuring Database Interface..............................................................................................72
Database Management Operations......................................................................... 73

Monitoring Database..............................................................................................................73
Creating Database.................................................................................................................75
Deleting Database.................................................................................................................75
Extending Database ..............................................................................................................76
Clearing Database .................................................................................................................78
Recreating Tables & Stored Procedure....................................................................................78
Backing Up and Restoring Data.............................................................................. 78

Backing up Data....................................................................................................................79
Restoring Data ......................................................................................................................80
Merging Another EMSs Data..................................................................................................81
Backing up NE Timeslot .........................................................................................................82
Restoring NE Timeslot ...........................................................................................................83
Backing up NE Information ....................................................................................................83
Restoring NE Information.......................................................................................................84
Checking Timeslot ................................................................................................ 85

Restoring ZXONM E100 data in ZXONM E300.......................................................... 85
Changing NE Software Version............................................................................... 86
Changing Software Versions of All NEs ...................................................................................86
Changing Software Version of Selected NE .............................................................................87
Changing NE ID.................................................................................................... 88
V3.16 Backup File Update to V3.17 ........................................................................ 89
Analyse and Process Network Data ........................................................................ 90
Replication System Management Operations........................................................... 90
Installing/Uninstalling Replication Server ................................................................................91
Configuring Replication System..............................................................................................92
Maintaining Replication System..............................................................................................99
Monitoring Replication System .............................................................................................105
Appendix B ................................................................................. 109

Abbreviations ........................................................................................ 109
Figures........................................................................................ 111
Tables ......................................................................................... 113
About this Manual
Purpose
This manual provides the basic information about how to maintain the
ZXONM E300 (V3.19R2).
Intended Audience
This manual is intended for engineers and technicians who perform
maintenance activities on ZXONM E300.
Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general understanding
of optical transmission technology and network management system.
Familiarity with the following is helpful:
System and various components of transmission equipment of ZTE
User interfaces of the ZXONM E300
Basic operations of the ZXONM E300
What is in this Manual

This manual is the Unitrans ZXONM E300 (V3.19R2) Unified EMS/SNMS of
Optical Network Maintenance Manual. It provides basic information about
how to maintain the ZXONM E300 (V3.19R2).
This manual includes five chapters and two appendixes:
Chapter
Description
Chapter 1 Maintenance Overview
Describes the classification of ZXONM E300 maintenance

operations, and the system management rules.
Chapter 2 Routine Maintenance
Describes the routine maintenance operations on ZXONM

E300.
Chapter
Describes the requirements for ZXONM E300 running
Maintenance
of
Confidential and Proprietary Information of ZTE CORPORATION
ZXONM E300 (V3.19R2) Maintenance Manual
Chapter
Description
Operating System
environment, the installation and configuration of Windows

and Unix operating systems, and FAQ.
Chapter 4 EMS Installation and

Upgrade
Describes the installation procedure, upgrade procedure,

and parameter settings of ZXONM E300.
Chapter 5 Maintenance of EMS
Describes how to maintain the EMS and how to set

environment variables when fault occurs to the EMS
connection, database, Manager, or Agent.
Appendix A DBMAN Operations
Takes the DBMAN tool in Windows 2000 operating system

to illustrate various functions of DBMAN.
Appendix B Abbreviations
Gives some terms and abbreviations for users reference.
Related Documentation
The Unitrans ZXONM E300 (V3.19R2) 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.19R2)
SDH equipment: ZXMP S390, ZXMP S380, ZXMP S360, ZXMP S320,
ZXMP S330, ZXMP S385, ZXMP S100, ZXMP S200, ZXMP S150,
ZXMP S325
DWDM equipment: ZXWM-32(V1), ZXWM M900, ZXMP M800, ZXMP

M720, ZXMP M820, ZXMP M920
CWDM equipment: ZXMP M600
PCM equipment: ZXMP P210, ZXMP P220, ZXMP P230, ZXMP P240
2. Manual suite
Manual Name
Function
Unitrans ZXONM E300 (V3.19R2) Unified

EMS/SNMS of Optical Network Installation Manual
It describes the basic knowledge and

installation process of ZXONM E300.

EMS/SNMS of Optical Network Interface Manual
It is an electrical manual, which

describes the operations of ZXONM
E300 client/ server interfaces.

EMS/SNMS of Optical Network Operation Manual
It includes several volumes which

describe the operations commonly used
in the ZXONM E300 in details.

EMS/SNMS of Optical Network LCT Users Manual
It describes the installation and

configuration of the ZXONM E300 LCT
(Local Craft/maintenance Terminal).
Unitrans
It
ZXONM
E300
(V3.19R2)
Unified
ii Confidential and Proprietary Information of ZTE CORPORATION
describes
the
maintenance
About this Manual
Manual Name
EMS/SNMS
Manual
of
Optical
Network
Function
Maintenance
knowledge of ZXONM E300.
Conventions
Typographical Conventions
ZTE documents employ 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.
iii
Typeface
Meaning
Drag
Refers to pressing and holding a mouse button and moving the

mouse.
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.
iv Confidential and Proprietary Information of ZTE CORPORATION
About this Manual
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.
vi Confidential and Proprietary Information of ZTE CORPORATION
Chapter
Maintenance Overview
In this chapter, you will learn about:
Classification of EMS maintenance operations
Management rules for the EMS
Maintenance Classification
The maintenance operations on EMS fall into two categories: routine
maintenance and emergency maintenance.
Routine Maintenance
Routine maintenance involves checking the EMS running status
periodically, and handling the problems promptly; so as to find hidden
trouble, prevent accident, find fault, and handle them as early as possible.
Emergency Maintenance
Emergency maintenance is also called troubleshooting. It
maintenance tasks brought by transmission equipment faults or
adjustments, such as the maintenance tasks to handle equipment
line faults, and emergency events found and recorded in
maintenance.
involves
network
damage,
routine
Management Rules for EMS

1. Do not exit the EMS when it working normally. Exiting the EMS will not
interrupt services; however, the EMS would be unable to monitor the
NEs.
2. Create a unique account for each user to log into the EMS, assign
proper authorities to each account, and change the EMS password
periodically to ensure its security.
3. Do not use the EMS to dispatch services during the traffic peak hours.
Otherwise, any wrong operation will seriously affect the services.
Choose the period when the traffic is the least to dispatch services.
4. Back up the data in time after dispatching services, so that the
services can be recovered promptly in the case of fault.
5. Do not play games on the EMS computer or copy irrelevant
files/software to the EMS computer. Use the anti-virus software to kill
virus on the EMS computer periodically to prevent the EMS computer
from getting infected by virus.
Chapter
Routine Maintenance
Operation Instructions
The EMS is a very important tool for routine maintenance. To ensure the
EMS is running reliably, the maintenance personnel at the site where the
EMS is located should check the running status of the equipment via EMS
everyday.
This chapter briefly describes the EMS maintenance operations. For
operation details, refer to the Unitrans ZXONM E300 (V3.19R2) Unified
SNMS/EMS of Optical Network Operation Manual.
Managing Users
Purpose
In order to prevent illegal user from logging into the EMS, and to
guarantee normal running and service security of equipment, it is
necessary to change the password of an EMS user and assign proper
operation authority to an EMS user.
Operations
1. Assign an EMS user with a unique username, a password,
management objects, and a user level according to his operation
authorities.
Note: The EMS provides four levels of users: administrator, maintainer,

operator, and monitoring user; each of which has certain operation authorities.
2. Change the login password for each EMS user periodically.
Tip: An administrator has all the operation authorities on the EMS, and an
improper operation taken by him may result in serious damage to the system.
Therefore, it is suggested no to log into the EMS as an administrator during routine
operations. Instead, create a monitoring user and log into the EMS as a monitoring
user.
Inspection Criteria
1. An EMS user can log into the EMS using the designated username and
password; and he has been assigned with proper operation
authorities.
2. An EMS user can change his password periodically.
Troubleshooting
1. If an EMS user has improper operation authorities or cannot change
the password, ask the administrator to check the configuration data of
the user or change the authorities and password of the user.
2. To troubleshoot fault of EMS connection, refer to the Handling EMS
Connection Fault section in Chapter 5.
Checking EMS Connection

Purpose
To ensure that the EMS can reflect the equipment running status in time
and accurately, and can monitor the equipment effectively, it is necessary
to check the connection between the equipment and the EMS.
Operations
1. On the computer installed with the EMS client software, run the
ZXONM E300 client software and log into the server.
2. In the EMS client operation window, select an online NE, and click the
Maintenance -> Time Management menu item.
Inspection Criteria
1. Based on the Operations described in step 1, the user can log into the
server normally from the client computer.
2. Based on the Operations described in step 2, the NE's NCP time can be
queried.
4Confidential and Proprietary Information of ZTE CORPORATION
Chapter 2 - Routine Maintenance
Troubleshooting
To troubleshoot fault of EMS connection, refer to the Handling EMS
Monitoring Topology
Purpose
The ZXONM E300 client operation window can give audible and visible
alarms. User can monitor the running status of the current subnet and NEs
via the navigation tree, topology, NE icons, and the board management
dialog box; and can judge the alarm level through the sound or color given
with the alarm.
Operations
1. Log into the EMS server on the client computer, and enters the EMS
client operation window.
2. Observe the NE icons in the client operation window, and the board
icons in the board management dialog box.
Note: The EMS software can only monitor or manage the NEs that are
communicating with the EMS computer normally.
Inspection Criteria
1.
The NE icon is not grey which indicates that the NE is online.
2.
The NE icon bears no alarm identifier.
3.
The optical connections are normal.
Troubleshooting
2. If the NE icon bears alarm identifier, query the detailed alarm message
in the current alarm monitoring dialog box or window. To handle alarm
messages, refer to the maintenance manual of the SDH equipment.
3. If the optical connection is a dotted line in the EMS, check the
corresponding optical fiber and fiber pigtail.
Monitoring Alarms
Purpose
In the ZXONM E300 EMS, user can monitor the alarm messages of a NE,
so as to know about the NE current running status, to discover and handle
the NE alarm messages.
Note: The EMS software can only monitor or manage the NEs that are
communicating with the EMS computer normally.
Operations
1. In the EMS client operation window, open the monitoring window to
monitor all the NEs alarms at real-time.
2. Query the NEs current or history alarm messages in the EMS client
operation window.
Inspection Criteria
1.
The NE has no alarm message at present.
2.
The NE has no unacknowledged history alarm.
Troubleshooting
2. To handle alarm messages, refer to the maintenance manual of the
SDH equipment.
Monitoring Performance
Purpose
In the ZXONM E300 EMS, the user can monitor the performance message
of the NE; thus keep aware of the current service performance of the NE,
and detect/handle the performance message of the NE in time.
Operations
In the client operation window of the EMS software, query the latest 15
minutes and 24 hours performance data of the NE.
Inspection Criteria
1.
For digital performance, the NE has no over-threshold event.
2. For analog performance, the NEs performance should comply with

corresponding index.
Troubleshooting
To handle performance messages, refer to the maintenance manual of the
SDH equipment.
Querying System Configuration

Purpose
In the ZXONM E300 EMS software, user can query the configuration
information of the network through the configuration menus. The result of
this query is the network configuration in the EMS software, not
necessarily the actual configuration of the NE. To obtain the actual
configuration and current working status of the NE, user needs to perform
the operations such as automatically uploading data, backing up NE data,
and comparing the EMS database and the NE database.
Operations
1. In the client operation window of the EMS software, select an NE, and
then click the System -> NCP Data Management -> Auto Upload
and Compare menu item. Then the EMS will automatically issue the
upload and compare command according to the period set by the
user. Or
2. In the client operation window of the EMS software, select an NE, and
then click the System -> NCP Data Management -> DB Upload
and Compare menu item. Then the EMS will issue the upload and
compare command for one time.
Inspection Criteria
The current network/NE configurations agree with the actual networking.
Troubleshooting
If the current service meets the user requirements, the network

configuration data should be corrected to comply with the actual
networking.
If the current service does not meet the user requirements, the
network configuration data should be corrected to comply with the user
requirements.
Querying User Operation Log

Purpose
The ZXONM E300 EMS software can record all the operations performed by
the user into the user operation log. It is one of the security guarantees.
Query the user operation log periodically; and check whether there is any
illegal access and any improper operation that affects the system running.
Operations
1. In the client operation window of the EMS software, click the System
-> Log Management menu item to open the Log Administration
window.
2.
Click the Operation Log tab to enter the Operation Log page.
3. Enter the query conditions and then click the Query button to query
the user operation log.
Inspection Criteria
There is no illegal login.
There is no user operation that affects system operation or service

functions.
Troubleshooting
When any illegal user or operation is found, use the user management
function of the EMS software to check the user identity and the authority
settings, and change the user password in time.
Printing Report
Purpose
With the printing function of the EMS software, user can print out the
network configuration, user operation log, equipment performance and
alarm messages. The printed reports can serve as the basis for
operation/maintenance records and network analysis.
Operations
1. In Windows operating system, if the Report Server is not started up,
click the Windows menu of Start -> Programs -> ZXONM E300 ->
Report Server to start up it.
2. In the client operation window of the EMS software, select an NE. Click
the submenu items in the Report menu item to query the
corresponding dialog box.
3. Enter the query conditions and then click the Print button to print the
report.
Inspection Criteria
None
Troubleshooting
1. Check whether the Report Server is started up on the client computer.
Saving/Printing
Alarm/Performance Messages
Purpose
Use the save and print function of the EMS to save the queried
alarm/performance data as a txt file onto the local computer, or to print
out the data as a report. Keep the file or report for future maintenance.
Operations
2. Query the alarm or performance in the Alarm Management or
Performance Management dialog box.
3. Click the
button to open the Unitrans Report window.
4. To save the queried alarm or performance messages, click the File ->
Save As menu item.
5. To print the queried alarm or performance messages, click the File ->
Print menu item
Inspection Criteria
None
Troubleshooting
1. Check whether the Report Server is started up on the client computer.
Backing up Data
Purpose
In the ZXONM E300 EMS software, database backup is primarily used to
copy and save the data of the Manager database. In the network operation
and maintenance, it is necessary to backup the system data often so that
the network data can be restored quickly in the case of network fault or
EMS data loss.
Note: It is recommended to save the backup data in a mobile storage device

lest backup loss in the case of hard disk fault of the EMS host.
Operations
There are two methods to back up the data:
Use the DBMAN tool to back up the data including the history data.
1. Run
the
dbman.exe
file
EMS_installation_directory\dbman.
in
the
directory
of
2. In the DBMAN main window, enter 4 which represents for Backup

and Restore.
3. In the Backup and Restore window, enter 1 which represents for
Backup database.
4. In the Backup database window, enter 1 which represents for
Backup directory.
5. Input the directory where the data to be backed up.
6. Enter 4 which represents for Backup to start backing up the data.
Use the EMS software to back up the current data only with no history
data.
1. In the client operation window of the EMS software, click the
System -> System Data Management -> DB Backup or
Restore menu item.
10
2. In the Database Backup/Restore dialog box, click the DB

Backup/Restore tab.
3. Select the Backup option button. Input or select the backup file
directory, and input the backup file folder name.
4. Click the Backup DB button to start backing up the data.
Inspection Criteria
A folder with the same name as the backup file name shall exist in the
backup file directory.
Troubleshooting
If the backup files do not exist, back up the data again.
Restoring Data
Purpose
In the case of network upgrade, network fault, or EMS data loss, restore
the data that had been backed up.
Warning: The restore of ZXONM E300 data would overwrite all the current
data. Therefore, back up current data before restoring the data.
Operations
There are two methods to restore the data:
Use the DBMAN tool to restore the data including the history data.
1. Run
the
dbman.exe
file
EMS_installation_directory\dbman.
in
the
directory
of
2. In the DBMAN main window, enter 4 which represents for Backup

and Restore.
3. In the Backup and Restore window, enter 2 which represents for
Restore database.
4. In the Restore database window, enter 1 which represents for
Backup directory.
5. Input the directory where the data is backed up.
11
6. Enter 4 which represents for Restore to enter the data restore

confirmation window. Then, start to restore the data according to
the system prompt information.
Use the EMS software to restore the data, which only include the data
when the backup operation was performed and no history data.
1. In the client operation window of the EMS software, click the
Restore menu item.
2. In the Database Backup/Restore dialog box, click the DB
Backup/Restore tab.
3. Select the Restore option button. Input or select the backup file
4. Click the Restore DB button to start restoring the data.
Inspection Criteria
None
Troubleshooting
If the EMS cannot work normally after the data restore operation, the data
used for data restore are of later version than the current EMS. Upgrade
the current EMS.
12
Chapter
Maintenance of Operating
System
Running environment requirements of ZXONM E300
Installation and configuration of EMS in Unix operating system
Installation and configuration of EMS in Windows operating system
Frequently asked questions and the answers
Running Environment
Requirements of ZXONM E300
Before installing the ZXONM E300, determine configuration requirements
of the EMS based on actual networking conditions, check configurations of
EMS computer based on software and hardware requirements, and
determine the software installation items.
Unix Platform
Hardware Requirements
Table 4 describes the hardware requirements based on Unix platform.
TABLE 4 HARDWARE REQUIREMENTS BASED ON UNIX PLATFORM
Hardware Item
Host
Requirement
HP B2600
Workstation
HP C8000
Workstation
HP RP3410 (maximum: 2CPU)
Mini computer
HP RP3440 (maximum: 4CPU)
Mini computer
Sun Blade 150
Workstation
Confidential and Proprietary Information of ZTE CORPORATION 13
Hardware Item
Requirement
Sun Blade 2500
Tape drive (optional)
Workstation
4 mm tape drive (DDS4) with SCSI cables and SCSI interface

card
Select host type according to the quantity of NEs to be managed in the

network.
NE quantity < 200: recommend to use HP B2600, HP C8000, Sun

Blade 150. The hard disk should be no less than 30 GB, and memory
should be no less than 1 GB.
NE quantity 200: recommend to use HP RP3410, HP RP3440, Sun

Blade 2500. The hard disk should be no less than 36 GB, and memory
should be no less than 3 GB.
Software Requirements
Table 5 describes the software requirements based on Unix platform.
TABLE 5 SOFTWARE REQUIREMENTS BASED ON UNIX PLATFORM
Software Item
Operating system
Requirement
HP-UX 11.00
HP workstation/mini-computer
Solaris 8 (SunOS 5.8)
SUN workstation
Database
SYBASE
Available space of
hard disk
No less than 9 GB
Windows Platform
Hardware Requirements
Table 6 describes the minimum hardware requirements based on
Windows.
TABLE 6 MINIMUM HARDW ARE REQUIREMENTS BASED ON WINDOWS
Hardware Item
14
Requirement
Host
P III 800 (with network card and CDROM)
Memory
512 MB
Hard disk
20 GB
Monitor
17 inches
Resolution
1024768
Color
Enhanced color (16 bits)
Chapter 3 - Maintenance of Operating System
LCT can be a portable computer with the following configurations: PIII

750/128 MB/10 GB/14.1 inch color monitor/24CDROM/56 K Modem/100
M network card/floppy disk drive, 1024768 resolution or above,
enhanced color (16 bits) or above
256.
Caution: The GUI on Windows platform does not support the color mode of
Select the host according to the quantity of NEs to be managed in the

network, as listed in Table 7.
TABLE 7 MINIMUM REQUIREMENTS FOR HOST CONFIGURATION (WINDOWS PLATFORM)
Minimum Configuration of Host
NE Quantity
CPU
Hard Disk
Memory
Less than 30
PIII 877
20 G
256 M
30 to100
P4 1 G
30 G
512 M
100 to 300
P4 2 G
60 G
1G
300 to 500
P4 2.5 G
80 G
2G
Software Requirements
Table 8 describes the software requirements based on Windows.
TABLE 8 SOFTWARE REQUIREMENTS BASED ON WINDOWS
Software Item
Requirement
Operating system
Windows 2000 or above (the GUI, Manager, and Database

should be installed on the same computer)
Database
SYBASE [Note] or SQL Server
Available space of hard disk
No less than 9 GB
Note: The ZXONM E300 which uses SYBASE as its database must be installed on Windows
2000, and Windows XP is not supported.
15
Installation and Configuration of

Unix
This section describes installation requirements of the Unix operating
system, and mandatory configurations before installing ZXONM E300.
Installing Unix
1.
Select proper host according to NE quantity. Refer to the section of

Unix Platform in Chapter 3.
2.
Install the Unix operating system according to manuals about Unix.
If the host is HP workstation or mini computer, install the HP-UX

11.0 operating system
If the host is SUN workstation, install the Solaris 8 (SUN OS 5.8)

operating system.
Configuring Unix
After installing the operating system successfully, make sure to set
parameters of the Solaris platform or HP-UX platform according to
descriptions in this section.
Configuring Solaris Platform

1. Execute the following command to set the kernel parameter in the file
named etc/system.
set shmsys:shminfo-shmmax=209715200
2. Execute the following commands to reboot the computer.

cd /
shutdown i6 g0 -y
Configuring HP-UX Platform

1. If the operating system is HP-UX 11.0, make sure the available space
of the directory / t m p is no less than 1 GB.
If the space is less than 1 GB, follow the steps below to extend it.
i.
Execute the following command to enter the single user mode.

#shutdown -y 0
ii. Log in as the ROOT user and execute the following command under
the root directory prompt to load all the file systems.
#mount -a
iii. Execute the # b d f command to check if the directory named / t m p

has been loaded successfully. If yes, record the logical volume
name of the directory.
16
Note: It is necessary to extend the logical volume which corresponds to the

file system before extending the file system. Therefore, execute the command b d f
to search the logical volume that corresponds to the directory named / t m p .
iv. Execute the following commands to extend the directory named

/tmp.
#umount /tmp
//Unmount the directory / t m p . This step is necessary before

changing its size
#lvextend -L 1024 /dev/vg00/lvol4
//Extend the logical volume / d e v / v g 0 0 / l v o l 4 that corresponds to

the / t m p file system to 1 GB (1024 MB).
#extendfs /dev/vg00/lvol4
//Extend the logical volume. For the v x f s file system, execute the
command e x t e n d f s - F v x f s / d e v / v g 0 0 / l v o l 4 .
#mount /dev/vg00/lvol4/tmp
//Mount the logical volume onto the directory / t m p .

2. Follow the steps below to adjust kernel parameters of the system and
re-create HP-UX kernel.
i.
Run the s a m program as the ROOT user.
ii. Select Kernel configuration area in the menu of s a m window.

iii. Set the kernel parameters as listed in Table 9.
TABLE 9 KERNEL P AR AMETER CONFIGURATIONS OF HP-UX OPERATING SYSTEM
Parameter
Value
maxdsiz_64bit
0XC0000000
maxssiz_64bit
0X4000000
maxtsiz_64bit
0x40000000
maxdsiz
0XC0000000
maxssiz
0X4000000
maxtsiz
0x40000000
shmmax
0x80000000
maxfiles
The recommended value is 256, indicating soft restriction on the

number of files that can be opened by a process.
The recommended value is 1210, indicating the maximum number of
nfile
files that can be opened at any time in the system. If this value is not
modified, the modification for the parameter maxfiles will fail.
17
Pay attention to the following parameters

shmseg
The default value is 120, indicating the maximum number of shared

memory sections that can be associated with a process at any time.
maxuprc
Maximum number of processes that can be run simultaneously by a

user.
nproc
Maximum number of processes that can be run simultaneously by the

system.
ninode
Maximum number of inodes that can be opened by the kernel. Each file
has an inode. The ninode value is generally greater than the nfile value.
iv. Follow the steps below to re-create HP-UX kernel in s a m .

Select sam -> Actions -> Create a New Kernel, and then select
Move kernel into place and shutdown/reboot system now or
Do not move kernel into place; do not shutdown/reboot
now.
v. Reboot the computer.
Installing Patch
Install patches after installing the operating system. For different Unix
platforms, the patches to be installed and the operations are different.
Solaris Platform
The patch is in os_patch/8_Recommended.zip of the installation CD.
To install the patch
1. Execute the following command to extract the 8_Recommended.zip file
to the directory 8_Recommended.
unzip 8_Recommended.zip
2. Enter the directory 8_Recommended and run the install_cluster

program. This process may take two hours.
3. Reboot the computer.
HP-UX Platform
For HP-UX 11.00, make sure to install QPK1100 in the HP-UX Support
Plus CD coming with the HP-UX installation CD. The installation
commands are as follows:
# mount /dev/dsk/c0t0d0/cdrom
# swinstall -s /cdrom/QPK1100
If the version of HP-UX is earlier than June 2001, install patches

XSWGR1100 and XSWHWCR1100 of year 2000 in the HP-UX Support
Plus CD. The installation commands are as follows:
# swinstall -s /cdrom/XSWGR1100 \
18
-xpatch_match_target=true \
-x autoreboot=true
# swinstall -s /cdrom/XSWHWCR1100 \
-xpatch_match_target=true \
-x autoreboot=true
Table 10 lists other patches to be installed.
TABLE 10 P ATCHES TO BE INSTALLED
Patch Name
Function
Remarks
PHNE_23876
Used for database, mandatory
PHNE_24100
GUI
PHSS_23803
GUI
PHSS_23823
GUI
PHSS_23800
Install this patch after installing the

patches of PHNE_24100, PHSS_23803,
and PHSS_23823
PHSS_22217
GUI
The patches in Table 10 can be installed in the following two methods:
Download the patches from the website of http://itrc.hp.com, and

then install them.
Install from the ZXONM E300 installation CD. The patches are in
the patch directory os_patch of the CD, with file suffix as tar.
Extract the .tar file first before installation. The operations are as
follows:
i.
Execute the following commands to extract the .tar file to

directory /tmp.
# cd /tmp
# tar xvf /cdrom/patch/hppatch.tar
ii. Taking the patch PHNE_24100 as an example, execute the

following commands to install it. Other patches are installed
according to this operation.
# cd /tmp/patch
# sh PHNE_24100
# swinstall -s /tmp/patch/PHNE_24100.depot
19
Configuring Database on HP-UX Platform

Note: For a computer installed with SYBASE on HP-UX platform, make sure
to create database storage devices and asynchronous devices to store data before
installing the ZXONM E300 software.
Creating Database Storage Devices

To create database storage devices
1. Check the free space of the hard disk and confirm that it is no less
than 1400 MB.
Log into the system as the ROOT user and execute the following
command:
# vgdisplay
The following information will be displayed:

--- Volume groups --VG Name
/dev
VG Write Access
read/write
VG Status
available
Max LV
255
Cur LV
10
Open LV
10
Max PV
16
Cur PV
Act PV
Max PE per PV
2500
VGDA
PE Size (Mbytes)
Total PE
2168
Alloc PE
2133
Free PE
35
Total PVG
Total Spare PVs
Total Spare PVs in use
V G N a m e is the volume group name, for example: / d e v / v g 0 0 . F r e e P E

is the free space of the volume group in the unit of PE. P E S i z e
( M b y t e s ) is the size of a PE in the unit of MB.
The free space of the volume group can be calculated as follows:

F r e e P E * F E S i z e (unit: MB)
20
2. Create database storage devices.

i.
Execute the following command to create a database data storage

device at the size of 600 M and with sybdat as the logical volume
name and vg00 as the volume group:
# lvcreate -L 600 -n sybdat vg00
ii. Execute the following command to create a database log storage

devices at the size of 800 M and with syblog as the logical volume
name and vg00 as the volume group:
# lvcreate -L 800 -n syblog vg00
3. The database storage devices are created completely.
Creating Asynchronous Devices

By default, the HP-UX does not have asynchronous devices. Therefore, it
is necessary to create asynchronous devices.
To create asynchronous devices
1. Run the sam program as the ROOT user.
2. Select sam -> Kernel configuration to enter the Drivers area.
3. Select asyncdsk and then perform the following operations to
re-create the HP-UX kernel.
i.
Select sam -> Actions -> Add Driver to Kernel to create a new
HP-UX kernel.
ii. Select sam -> Actions -> Process New Kernel, and then select
Move kernel into place and shutdown/reboot system now or
Do not move kernel into place; do not shutdown/reboot now
in the popup dialog box.
4. Execute the following command to reboot the system and load the
asynchronous I/O driver:
# /sbin/shutdown -r 0
5. Log into the system as the ROOT user, create the device file
/dev/async with 101 as the host device number, and execute the
following command to ensure the authority of the file is correct.
# ls -l
/dev/async
The result may be as follows:

crw-rw---/dev/async
sybase
sybase
101
0x000004
Oct
28
10:32
If /dev/async does not exist or the device number is incorrect, delete

the device, and then execute the following command to re-create it:
# /sbin/mknod
/dev/async c 101 0x4
6. Create sybase group and user for the device:

# /sbin/mknod
/dev/async c 101 0x4
# /usr/bin/chown
sybase:sybase /dev/async
# /usr/bin/chmod 660
/dev/async
21
Installation and Configuration of

Windows
For hardware requirements for the computer installed with Windows
operating system, refer to Table 6. Select host according to the quantity of
NEs to be managed in the network, as listed in Table 7.
Install the Windows operating system according to its related manuals.
Caution: The ZXONM E300 which uses SYBASE as its database must be
installed on Windows 2000 Server, and Windows XP is not supported.
After installation, it is required to log into the operating system as the

super user to install and operate the ZXONM E300 EMS.
FAQ
In the Unix operating system, various problems may come up. Sometimes,
the system administrator has to retrieve the loss caused by serious
accident.
This section introduces some emergency cases and the solutions in the
Unix operating system.
What are emergency startup floppy disks? How to

make them?
The emergency startup floppy disks are very important tools for system
administration. They include a system boot floppy disk and a root file
system floppy disk.
When the system is working normally, a qualified administrator should
make an emergency startup floppy disk for Unix system. Use the
emergency startup floppy disk to restore the system when the system
suffers disastrous damage and would not respond when being restarted.
The emergency startup floppy disk can restore the damaged root file
system, so that the operating system needs no reinstallation.
To make the emergency floppy disks
1.
Startup the operating system in the single-user maintenance mode.
2. Format the two floppy disks that are to be used for the emergency
startup floppy disks.
3. Make two emergency startup floppy disks: a system boot floppy disk
and a root file system floppy disk.
22
Warning: Each computer has its own emergency startup floppy disks which
cannot be used by another computer; since the emergency startup floppy disks
would not work on another computer, and evern worse, they may bring severer
damage to another computer.
What to do when forgetting the super user password?

First, the system administrator needs to use the emergency startup floppy
disks to start up the operating system. Then install the root file system on
the hard disk to the /mnt directory. After that, edit corresponding files to
delete the password of the root account.
The detailed steps are as follows:
1.
Insert the system boot disk into the floppy drive.
2.
Power on the computer.
3. Insert the root file system disk into the floppy drive as per the system
prompt.
4. After system has
(administrator).
started
up,
log
into
it
as
super
user
5. Execute the following command to install the root file system on the
hard disk to the /mnt directory.
# mount /dev/hd0root /mnt
Then the /etc/passwd file changes its location to /mnt/etc/passwd.

6. Follow the steps below to edit the corresponding files using the vi
editor and delete the password of the root account.
For an operating system configured with lower security level

Need to edit the /mnt/etc/passwd file in which each line has the
format Loginname:Password:UID:GID:Userinformation:Home:Shell.
Delete the password information in the second domain of root
account.
For example:
Change the line of root:Ctsf6P/L/nav6,..1k:0:1:Superuser:/: into
the following line:
root:,..1k:0:1:Superuser:/:
For an operating system configured with higher security level

Need to edit the /mnt/etc/shadow file.
information in the /mnt/etc/passwd file is:
The
root
account
root:x:0:1:Superuser:/: adm:x:4:4:System accounting:/usr/adm:

doug:x:200:50:Dougs account:/usr/doug:/bin/sh
23
The passwords of all the accounts

/mnt/etc/shadow file. For example:
are
saved
in
the
root:Ctsf6P/L/nav6:9881:0:0
adm:*:9926:0:0 doug:oTDTuBctxUBtc:9926::
Delete the password information in the second domain of root
account.
For example, the root:Ctsf6P/L/nav6:9881:0:0 is changed to
root::9881:0:0 &gt
Warning: Be careful not to delete other information by accident when

editing a file in the hard disk file system.
How to retrieve lost files?

If user deletes important files by accident, there is no command in Unix to
retrieve the files directly. Follow the steps below to retrieve the lost files:
1. Copy the corresponding files from the emergency startup floppy disk
into the hard disk file system.
2. If the deleted file is not in the emergency startup floppy disk, choose
one of the following methods:
Copy the file from another system.
Retrieve the file from the backup system.
3. If none of the above methods can retrieve the lost files, the user
would have to recreate the file.
24
Chapter
EMS Installation and Upgrade

ZXONM E300 installation flow
Upgrade of ZXONM E300
Parameter settings of ZXONM E300
Installation Flow
Figure 1 shows the installation flowchart of the ZXONM E300.
FIGURE 1 INSTALLATION FLOWCHART OF ZXONM E300
Install operating system
Prepare for
ZXONM E300
installation
Typical
installation
Install
ZXONM E300
Configure the
parameters
Customized
installation
Confirm installation
components
Install corresponding
components
Configure the
parameters
The ZXONM E300 EMS can be installed on Unix or Windows platform based
on networking requirements. For installation details, refer to the Unitrans
ZXONM E300 (V3.19R2) Unified EMS/SNMS of Optical Network Installation

Manual.
Upgrading ZXONM E400 to

ZXONM E300
Preparing for Upgrade
This section takes the network shown in Figure 2 as an example to
illustrate how to prepare for upgrading ZXONM E400 to ZXONM E300.
FIGURE 2 NETWORK EXAMPLE
NE B
NE A
NE C
EMS
NE
ECC link
IP link
In Figure 2, ZXONM E400 uses NE A as the access NE. After upgrade, it is

required that ZXONM E300 also uses NE A as the access NE.
To prepare for upgrading ZXONM E400 to ZXONM E300
1. Install the standby ZXONM E400 on the computer which is connected
with NE B.
2. Install the ZXONM E300 on the EMS computer which is connected with
NE A.
3. Make sure that the free space on the hard disk of ZXONM E300
computer is no less than 2GB.
4. Make sure that the database server of ZXONM E300 is running in the
TCP/IP mode.
26
Chapter 4 - EMS Installation and Upgrade
5. If the ZXONM E300 computer has multiple IP addresses, make sure

that the IP address of the ZXONM E300 database server is the IP
address in DCN (Data Communications Network).
6. Make sure that the ZXONM E300 configuration
$INSTALL/Sybase/ini/sql.ini has the following content:
file
named
[SQL_ZXONM]
master=TCP,*.*.*.*,4001
query=TCP,*.*.*.*,4001
//*.*.*.* is the IP address of ZXONM E300 computer.
7.
Restart the ZXONM E300.
8. Make sure that the standby ZXONM E400 can manage the network
consisting of ZXWM-32(V1) NEs with NE B as the access NE, lest that
the NEs cannot be managed for a long time once the upgrade fails.
9. Prepare the Agent program of the ZXWM-32(V1) NE which is to be
upgraded.
10. Make sure that both the ZXONM E400 and the ZXONM E300 can ping
through NE A.
Caution: For ZXWM-32(V1) NE, the performance data during the upgrade
procedure may be lost. Therefore, make sufficient preparations for the upgrade
and make the upgrade procedure as short as possible.
Upgrade Operations
Follow the steps below to upgrade ZXONM E400 to ZXONM E300:
1. Check the network of ZXWM-32(V1) NEs using the standby ZXONM
E400. Make sure that the optical powers of all main optical paths are
normal, and no OTU board reports alarm.
2. Run the data transfer tool on the ZXONM E400 computer to transfer
the data of active ZXONM E400 onto ZXONM E300.
Note:
The data transferred include the configuration data and the history data, thus
ensures that these data would not get lost.
The length of time spent on data transfer varies with the amount of history
data.
Make sure that the ZXONM E300 employs the correct ManagerID for data
transfer.
27
3. Restart ZXONM E300 upon completion of data transfer. Once ZXONM

E300 is started up normally, set the NE A to be the access NE in
ZXONM E300.
4. Now, ZXONM E300 should be able to display the data of ZXWM-32(V1)
NEs. However, it cannot manage these NEs yet.
5. Upgrade the program of NE A to V1.40 using ZXONM E400. NE A will
reset upon successful upgrade, and ZXONM E400 cannot manage NE A
any more. Instead, ZXONM E300 can manage NE A. And it can
manage the whole ZXWM-32(V1) network before long.
6. Use ZXONM E300 to upgrade the programs of all the other
ZXWM-32(V1) NEs to V1.40. After this, the standby ZXONM E400
cannot manage the ZXWM-32(V1) NEs any more. Instead, the ZXONM
E300 can manage the whole network of ZXWM-32(V1).
7. Use the ZXONM E300 to download database for each ZXWM-32(V1) NE,
so as to synchronize the NE data with ZXONM E300 data.
Caution: If a ZXWM-32(V1) NE is connected with ZXONM E300 through

DCN, it is forbidden to download database to this NE.
Because, in order to use ZXONM E300 to download database to a NE wich accesses
the DCN, it is necessary to set the gateway information on this NE via a serial port.
Otherwise, the routes on DCN will be lost and the monitoring on the NE will be
interreupted. However, current ZXONM E300 cannot set gateway on ZXWM-32(V1)
NE.
8. Observe the ZXWM-32(V1) NEs in ZXONM E300 for about four hours.
If no problem comes up, the upgrade had succeeded.
Upgrading ZXONM E300

Caution: If both the NCP program and the ZXONM E300 need to be
upgraded, upgrade the NCP program in current ZXONM E300 first. After that,
upgrade the ZXONM E300.
Note: ZXMP S380/S390/S385/S330/S325/S200 equipments all support the

remote online upgrade of NCP program, which makes the NCP program upgrade
very convenient. The upgrade operations of NCP program vary with equipment
type. For detailed operations, refer to the Unitrans ZXONM E300 (V3.19R2) Unified
EMS/SNMS of Optical Network Operation Manual (Volume IV) Agent
Configurations.
28
Applicable Scope
The upgrade operations of ZXONM E300 are applicable to:
Upgrading ZXONM E300 V3.12.001[020228] in Unix to ZXONM

V3.12.004[020628] in Windows/Unix or later version.
Upgrading ZXONM E300 V3.12.002[020522] in Windows/Unix to later

version.
Preparing for Upgrade

1. Make sure that the ZXONM E300 is working normally. Remove any
fault before upgrading.
2. Make sure that the free space on EMS computers hard disk is enough.
In Windows operating system, at least 4 GB free space is required; in
Unix operating system at least 5 GB free space is required, and the
v g d i s p l a y command can be executed to check the free space.
3. Make sure that the free space under the root directory is at least 80
MB. In Unix operating system. The d f - k command can be used to
check free space of a file system.
4. Make sure that no NE is in the switching state. Otherwise, find out the
reason for the switching. Do not perform the upgrade until the
switching disappears.
5. Make sure that the version of ZXONM E300 installation software is
correct and is compliant with the NEs NCP program.
6. Make a copy of the old version installation software of ZXONM E300;
so that once the upgrade fails, the EMS can be recovered to the old
version.
7. To upgrade ZXONM E300 in Unix, check if the patch of Unix system is
correct. For patch requirement, refer to the Installing Patch section in
Chapter 3.
Upgrading EMS in Unix

Suppose the original EMS was installed under the /opt/Unitrans directory.
Note: It is recommended to back up the /opt directory.
1. Back up the following critical configuration files:
/opt/unitrans/gui/etc/mgrcfg.ini
/opt/unitrans/db/cfg
/opt/unitrans/manager/cfg
29
For example, to back up the configuration files to the /opt/cfg_bak

directory, execute the following commands:
#cd
/opt
#mkdir
cfg_bak
#mkdir
cfg_bak/db
#mkdir
cfg_bak/manager
#cp
cfg_bak
#cp
cfg_bak/db
#cp
cfg_bak/manager
Warning: The backup files cannot be saved under the EMS installation
directory.
2. Map the CD ROM file system

i.
Log into the Unix workstation as the root user. Insert the
installation CD into the CD ROM.
ii. Execute the following commands to search for the device name of
the CD ROM, as shown in Figure 3.
#cd
#ioscan
-fnkC
disk
FIGURE 3 SEARCHING FOR DEVICE NAME OF CD ROM
The result shows

/dev/dsk/c0t0d0.
iii. Execute the # m k d i r
that
the
device
name
of
CD
ROM
/ c d r o m to create the cdrom directory.
iv. Execute the # m o u n t

-ocdcase
/dev/dsk/c0t0d0
command to mount the CD ROM to the system.
/cdrom
3. Choose one of the following three methods to back up the database:
30
is
Use the backup.sh script
Use the DBMAN tool
Use the database backup function provided by EMS
Note: To backup not only the current data but also the history data, use the
DBMAN tool.
To backup database using the backup.sh script

i.
Execute the following commands:

#cd
/opt/unitrans/db
#vi
cfg
//Check the database server name. Suppose it is h p 9 a s e . Check if

it is correct in the cfg file. Then exit v i .
#./backup.sh
hp9ase
//Back up the data to the /opt/unitrans/db/backup directory.

ii. Copy the /opt/unitrans/db/backup directory to a directory which is
not used for EMS installation, such as / o p t / d a t a _ b a k directory.
iii. Execute the following commands:
#cd
/opt
#mkdir
#cp
-R
data_bak
/opt/unitrans/db/backup
data_bak
Note: The database backed up using this method cannot be used for the
new EMS. It is only a preventive measure, so that once the EMS upgrade fails, the
old data can be restored by running the restore.sh script after the old EMS has
been restored.
To backup database using the DBMAN tool

i.
Run the DBMAN tool. Suppose DBMAN is located under the

/opt/unitrans/db directory, execute the following commands to run
DBMAN:
#cd
/opt/unitrans/db/dbman
#export
LANG=C
#./dbman
The DBMAN interface may vary with the EMS version. Taking the
ZXONM E300 V3.19R2 in Unix as example, the DBMAN main
interface is shown in Figure 4.
31
FIGURE 4 DBM AN M AIN INTERFACE IN UNIX
ii. Enter 4 which represents for Backup and Restore in Figure 4 to

enter the BACKUP AND RESTORE interface, as shown in Figure 5.
FIGURE 5 BACKUP AND RESTORE INTERFACE OF DBM AN IN UNIX
iii. Enter 1 which represents for Backup database to enter the

BACKUP DATABASE interface, as shown in Figure 6.
32
F I G U R E 6 B A C K U P D A T A B AS E I N T E R F A C E O F D B M A N I N U N I X
iv. Enter 1 which represents for Backup directory. Then input the
database backup directory, e.g. /opt/data_bak. Press ENTER.
v. In Figure 6, enter 4 which represents for Backup to back up the
database.
vi. Exit DBMAN once database backup is completed.
Note: For operation details of DBMAN, refer to Appendix A DBMAN

Operations.
Warning: The backup files should be placed under a directory other than
the EMS installation directory, since the installation directory will be deleted when
removing the EMS.
To backup database using the EMS database backup function

i.
In the EMS client operation window, click the System -> System
Data Management -> DB Backup or Restore menu item.
ii. In the Database Backup/Restore dialog box, click the DB

Backup/Restore tab.
iii. Select the Backup option button. Input or select the backup file
iv. Click the Backup DB button to start backing up the data.
33
4. Remove the old version EMS

i.
Execute the following commands:

#cd
/opt/unitrans
#./unistall
ii. Check if the /opt/unitrans directory is empty. If not, follow the

steps below to delete it manually:
#ps
-ef|grep
dataserver
//Obtain the d a t a s e r v e r process ID. Suppose it is 2 0 0 2 .

#kill
-9
2002
//Kill the d a t a s e r v e r process

#cd /opt
#rm
-rf
/opt/unitrans
//Delete the EMS installation directory.

5. Install the new version ZXONM E300 in Unix according to the Unitrans
ZXONM E300 (V3.19R2) Unified EMS/SNMS of Optical Network
Installation Manual.
6. Choose one of the following two methods to restore the data.
To restore data using the EMS data restore function
To restore data using the DBMAN tool
To restore data using the DBMAN tool

i.
Run the DBMAN tool. Suppose DBMAN is located under the

/ o p t / u n i t r a n s / d b directory, execute the following commands to
run DBMAN:
#cd
/opt/unitrans/db/dbman
#export
LANG=C
#./dbman
The DBMAN interface may vary with the EMS version. Taking the
ZXONM E300 V3.19R2 in Unix as example, the DBMAN main
interface is shown in Figure 4.
ii. Enter 4 which represents for Backup and Restore in Figure 4 to
enter the BACKUP AND RESTORE interface, as shown in Figure 5.
iii. Enter 2 which represents for Restore database to enter the
RESTORE DATABASE interface, as shown in Figure 7.
34
FIGURE 7 RESTORE DATAB ASE INTERFACE OF DBMAN IN UNIX (1)
iv. Enter 1 which represents for Backup directory. Then input the
database backup directory, e.g. /opt/0603. Press ENTER, then
the RESTORE DATABASE interface turns into Figure 8.
FIGURE 8 RESTORE DATAB ASE INTERFACE OF DBMAN IN UNIX (2)
v. In Figure 8, enter 4 which represents for Restore to start to

restore the data. After restoring the data successfully, the interface
will prompt database restore successfully.
35
To restore data using the EMS data restore function

i.
In the client operation window of the EMS software, click the

Restore menu item.

Backup/Restore tab.
iii. Select the Restore option button. Input or select the backup file
iv. Click the Restore DB button to start restoring the data.
7. Execute the following commands to restore the configuration files
#cd
#cp
#cp
#cp
/opt/cfg_bak
mgrcfg.ini
/opt/unitrans/gui/etc
cfg
/opt/unitrans/db
cfg
/opt/unitrans/manager
8. Execute
the
following
commands
to
set
the
o p t / u n i t r a n s / g u i / e t c / t e s t file to be writable.
#cd
/opt/unitrans/gui/etc
#chmod
+w
test
9. Execute the following commands to restart the workstation.

#cd
#shutdown
-ry
10. Follow the steps below to download the NE database using the new
ZXONM E300.
Note: If the NCP database has been cleared when upgrading the NCP board,
the NE database must be downloaded.
i.
Start up the ZXONM E300 of new version.
ii. Once the EMS get able to manage NEs, select an NE, then click the
System -> NCP Data Management -> DB Download menu
item.
iii. Select the Select All The Files check box.
iv. Click the Apply button to start downloading the NE database.
Upgrading EMS in Windows

In Windows operating system, suppose the original EMS was installed
under the d:\zte\zxonm e300 directory. Follow the steps below to upgrade
the EMS.
36
1. Back up the critical configuration files including d:\zte\zxonm

e300\gui\etc\mgrcfg.ini, d:\zte\zxonm e300\db\cfg, d:\zte\zxonm
e300\manager\cfg. Suppose these files are backed up under the
corresponding subdirectories of the d:\zte\e300_bak directory.
2. Choose one of the following two methods to back up the EMS data:
Use the DBMAN tool
Use the EMS data backup function
To back up the EMS data using the DBMAN tool

i.
Start up the ZXONM E300 server to start up the database server.
ii. Double-click the dbman.bat file to open the DBMAN main interface
shown in Figure 9.
FIGURE 9 DBM AN M AIN INTERFACE IN WINDOWS
iii. Refer to the corresponding steps in the Upgrading EMS in Unix

section for subsequent steps.
To back up the EMS data using the EMS data backup function
i.

Backup/Restore tab.
iii. Select the Backup option button. Input or select the backup file
iv. Click the Backup DB button to start backing up the data.
3. Follow the steps below to remove the old version EMS
37
i.
On the client computer, click the Start -> Settings -> Control
Panel menu item.
ii. Double-click the Add/Remove Programs icon to open the

Add/Remove Programs window.
iii. Select ZXONM_E300 in the currently installed program list. Then
click the Change/Remove button to remove the ZXONM E300.
4. Install the new version ZXONM E300 in Windows operating system
according to the ZXONM E300 installation manual.
5. Choose one of the following two methods to restore the EMS data
Use the DBMAN tool
Use the EMS data restore function
To restore the EMS data using the DBMAN tool

i.
Start up the ZXONM E300 server to start up the database server.
ii. Double-click the dbman.bat file to open the DBMAN main interface
shown in Figure 9.
iii. Refer to the corresponding steps in the Upgrading EMS in Unix
section for subsequent steps.
To restore the EMS data using the EMS data restore function
i.

Backup/Restore tab.
iii. Select the Restore option button. Input or select the backup file
iv. Click the Restore DB button to start restoring the data.
6. Follow the steps below to restore the configuration files
i.
Copy
the
d:\zte\e300_bak\gui\etc\mgrcfg.ini
file
to
the
d:\ZTE\zxonm e300\gui\etc directory, thus overwrite the mgrcfg.ini
file.
ii. Copy the d:\zte\e300_bak\db\cfg file to the d:\ZTE\zxonm e300\db

directory, thus overwrite the cfg file.
iii. Copy the d:\zte\e300_bak\manager\cfg file to the d:\ZTE\zxonm
e300\manager directory, thus overwrite the cfg file.
7. Restart the computer.
38
ZXONM E300.
i.
item.
Sharing Data between EMS in Unix and

EMS in Windows
For the ZXONM E300 of version V3.12.005[020522] or above, the data
can be shared between the E300 installed in Windows and the E300
installed in Unix. That is, the backup data of E300 installed in Windows can
be restored in the EMS of the same version which is installed in Unix; and
vice versa.
To back up the data of E300 (V3.19R2) installed in Unix and then
restore the data in EMS (V3.19R2) installed in Windows
1. Execute the following commands to back up the critical configuration
files under the /opt/cfg_bak directory.
#cd
/opt
#mkdir
cfg_bak
#mkdir
cfg_bak/db
#mkdir
cfg_bak/manager
#cp
cfg_bak
#cp
cfg_bak/db
#cp
cfg_bak/manager
2. Use the FTP tool to copy the /opt/cfg_bak file to a directory on

Windows 2000 computer that is to be upgraded. Suppose the
d:\e300\cfg_bak directory is used.
3. Map the CD ROM file system
i.
Log into the Unix workstation as the root user. Insert the
installation CD into the CD ROM.
ii. Execute the following commands to search for the device name of
the CD ROM, as shown in Figure 3.
#cd
#ioscan
-fnkC
disk
39
The result shows

/dev/dsk/c0t0d0.
iii. Execute the # m k d i r
that
the
device
name
of
CD
ROM
is
/ c d r o m to create the cdrom directory.
iv. Execute the # m o u n t

-ocdcase
/dev/dsk/c0t0d0
command to mount the CD ROM to the system.
/cdrom
4. Refer to step 3 in the Upgrading EMS in Unix section to back up the

database of EMS in Unix.
5. Use the FTP tool to copy the data files to a directory on Windows 2000
computer that is to be upgraded. Suppose the d:\e300\data_bak
directory is used.
6. Refer to step 4 in the Upgrading EMS in Unix section to remove the old
version EMS.
7. Install the new version EMS in Windows 2000 according to the ZXONM
E300 installation manual.
8. Refer to step 5 in the Upgrading EMS in Windows section to restore the
data.
9. Follow the steps below to restore the configuration files
i.
Copy the d:\e300\cfg_bak\db\cfg file to the d:\ZTE\zxonm

e300\gui\etc directory, thus overwrite the mgrcfg.ini file.
ii. Copy the d:\e300_bak\db\cfg file to the d:\ZTE\zxonm e300\db

directory, thus overwrite the cfg file.
iii. Copy the d:\e300_bak\manager\cfg file to the d:\ZTE\zxonm
e300\manager directory, thus overwrite the cfg file.
10. Restart the computer.
ZXONM E300.
i.
item.
40
Note: For a specific version of ZXONM E300, follow its dedicated operations
to back up data, restore data, or upgrade E300.
Setting EMS Parameters in

Windows
On Windows platform, setting EMS parameters involve configurations of
communication between GUI and Manager, communication between DB
and Manager, synchronization of SYBASE database, and SQL Sever
database.
Configuring Communication between GUI

and Manager
If GUI and Manager are installed on different computers, it is necessary to
modify the installation-directory/gui/etc/mgrcfg.ini file to configure
communication between the GUI and Manager.
Open the mgrcfg.ini file, as shown in Figure 10.
In the mgrcfg.ini file, user can set the Manager name. The Manager IP
address must be the same as the IP address of the logged-in Manager. By
default, the Manager port is 2000. User can modify the port number.
FIGURE 10 MGRCFG.INI FILE

Manager name
Manager IP address
Manager port
Configuring Communication between DB

and Manager
If Manager and dbsvr are installed on different computers, configure the
communication between them by modifying files of installation
directory\db\cfg and installation directory\manager\cfg.
41
The OID in the c f g files of the dbsvr and Manager must be configured to
be the same.
For example:
Database configuration file: installation directory\db\cfg
//Database OID. Only the last digit can be changed, and the
configuration of OID must be consistent with that of Manager.
dbOid=iso:org:dod:internet:private:enterprise:zte:db:8
//Parent Manager OID. Only the last digit can be changed, and the
mgrOid=iso:org:dod:internet:private:enterprise:zte:
manager:8
......
Manager configuration file: installation directory\manager\cfg

......
//Database OID
//Parent Manager OID

parentMgrOid=iso:org:dod:internet:private:enterprise:zte:
manager:8
......
Configuring Synchronization of SYBASE

Database
If the ZXONM E300 adopts the SYBASE database and there are multiple
EMSs in the network, synchronize databases through the EMS DBMS to
ensure synchronization among these EMSs.
For details, refer to the Unitrans ZXONM E300 Unified EMS/SNMS of
Optical Network Operation Manual (Volume VI) Database Synchronization
Configuration.
Configuring SQL Server Database

For a computer installed with typical ZXONM E300 EMS and SQL Server
database, it is necessary to change the alias configuration after the
ZXONM E300 installation. This is to prevent the conflict between the
default named pipes and SQL server database, and to ensure that the EMS
can start up normally.
42
To configure SQL Server database

1. In the computer where the EMS is installed, select Start -> Programs
-> Microsoft SQL Server -> Client Network Utility to enter the
SQL Server Client Network Utility dialog box. In the dialog box,
select the Alias tab to enter the Server alias configuration page, as
shown in Figure 11.
FIGURE 11 SQL SERVER CLIENT NETWORK UTILITY DIALOG BOX
In Figure 11, the alias SQL_ZXONM is generated automatically after

the ZXONM E300 is installed. It is the server alias required by EMS
data.
2. In Figure 11, click SQL_ZXONM and it will be highlighted. Click Edit to
enter the Edit Network Library Configuration dialog box, as shown
in Figure 12.
FIGURE 12 EDIT NETWORK LIBRARY CONFIGURATION DIALOG BOX
43
3. Select TCP/IP in Network libraries, and enter the IP address of the

computer or loop address (127.0.0.1) in the Server name text box of
Connection parameters area, as shown in Figure 13.
FIGURE 13 EDIT NETWORK LIBRARY CONFIGURATION DIALOG BOX (MODIFY

NETWORK LIBRARY)
Note: It is recommended to set the IP address to 127.0.0.1. When the IP

address of the computer is changed, it unnecessary to modify the server name.
4. Click OK to save configuration and return to SQL Server Client

Network Utility dialog box, as shown in Figure 11. Update the
configuration of server alias in the dialog box.
5. Click OK in SQL Server Client Network Utility dialog box to finish
database configuration.
Setting EMS Parameters in Unix

Set the following parameters based on actual conditions to ensure normal
running of the EMS.
Setting Dynamic Route

If dynamic routes are used for communication between EMS and Agent,
the configuration of dynamic route is as follows.
1. Set the IP address of the EMS computer and the IP address of the
access NE to be in the same network section.
Note: If the computer is equipped with multiple network cards, the IP

address of the network card serving to access NE should be set. The dynamic
routes are valid for the first IP address of the network card only.
44
2. Modify G A T E D = 0 to G A T E D = 1 in the /etc/rc.config.d/netconf file.

3. Modify the /etc/gated.conf file. Check if such information as o s p f
y e s . . . exists in the file. If not, append the following content to the
file.
ospf yes {
aera 0.0.0.1 {
interface all;
};
};
4. Reboot the system to complete the configuration.

5. Execute the following command to check dynamic routes:
# netstat -rn
Configuring Communication between GUI

and Manager
If the GUI and the Manager are installed in different computers, open the
mgrcfg.ini file using the vi editor or other file edit tools, and configure
communication between the GUI and Manager.
Configure communication at the GUI side. It is recommended to execute
the following commands to access the configuration file. Suppose the EMS
installation directory is /opt/unitrans.
# cd /opt/unitrans/gui/etc
# ./config
Suppose the modified mgrcfg.ini file is as follows:

[Manager A]
IP="192.192.192.23"
PORT="2000"
[Manager B]
IP="192.192.192.25"
PORT="2000"
In the configuration file, I P represents for the IP address. The address of

Manager must be the same as the address in the Manager configuration
used for communication with GUI. The default port of Manager is 2 0 0 0 and
can be modified by user.
Configuring Communication between DB

and Manager
If the Manager and dbsvr are installed on different computers, modify the
files installation directory/db/cfg and installation directory/manager/cfg to
configure the communication between DB and Manager.
45
The OIDs in the c f g files of the dbsvr and Manager must be configured to
be the same.
For example:
1. Database configuration file /opt/unitrans/db/cfg:
......
//Database OID. Only the last digit can be changed, and the
//Parent Manager OID. Only the last digit can be changed. and the
mgrOid=iso:org:dod:internet:private:enterprise:zte:manag
er:8
......
2. Manager configuration file /opt/unitrans/manager/cfg:
......
//Database OID
//Parent Manager OID

parentMgrOid=iso:org:dod:internet:private:enterprise:zte
:manager:8
......
Configuring Database Synchronization

If multiple EMSs are used for networking, and EMS DBMS is used to
ensure data consistency of EMSs, database synchronization configuration
must be performed. For detailed operations, refer to the Unitrans ZXONM
E300 Unified EMS/SNMS of Optical Network Operation Manual (Volume VI)
Database Synchronization Configuration.
FAQ
FAQ for EMS Installation in HP-UX
1. During the process of EMS installation, the system is powered off
suddenly. After the system reboots, the disk space becomes
insufficient. Why does this happen?
Possible causes:
46
i.
Some temporary files are stored under the directory /tmp during
installation. After the system is powered off suddenly, these files
are not cleared up automatically.
ii. After the system is powered off, it saves the information which was
in the buffer into lost+found folder under the operation directory.
This information is not released after the system reboots. Execute
the command b d f to measure the used space. The contents of this
folder are stored in the file index node. Therefore, corresponding
records cannot be queried.
iii. In case of sudden power-off, the system saves the information
which was in the buffer to the /var/preserve folder. This
information is not released after the system reboots.
iv. Sudden power-off makes temporary files under the /var/tmp
directory not released.
Solution:
i.
Delete the files in the folders: /tmp, /opt/lost+found, /var/tmp, and

/var/preserve.
ii. If the above operation cannot work, delete the EMS installation
directory, and re-install the EMS.
2. When creating logical volume, the disk space is insufficient. How to
deal with it?
Check the disk and if you find that the free space is insufficient, you
should re-partition the hard disk. Because the HP platform does not
provide the command to reduce the space occupied by the file system,
you must back up the file system to another file system. Then, delete
the original file system, re-create a smaller file system, and finally
restore the data of the original file system. The detailed procedure is
as follows:
i.
Execute the command b d f to search the file system that can be

reduced.
Usually, it is recommended to use the file system which is large,
with large available space that satisfies the space requirement and
low utilization ratio, as the target to be reduced. In most cases,
you can select the /opt file system.
After the command # b d f is executed, the following information will
be displayed:
Filesystem
kbytes
used
/dev/vg00/lvol3
143360
134789
/dev/vg00/lvol1
83733
/dev/vg00/lvol9
2867200
2639553
/dev/vg00/lvol8
532480
426533
/dev/vg00/lvol7
512000
507975
/dev/vg00/lvol4
65536
/dev/vg00/lvol6
3072000
27637
2043
72000
avail
%used
Mounted on
8258
94%
47722
37%
/stand
213865
99682
3788
59652
3000000
93%
/home
81%
/var
99%
/usr
3%
3%
/tmp
/opt
47
F i l e s y s t e m indicates the file system;

k b y t e s indicates the size of the file system;
u s e d indicates the used space in unit of Kbyte;
a v a i l indicates the available space in unit of Kbyte;
% u s e d indicates the space utilization ratio;
M o u n t e d o n indicates the installation location.
According to the above result, select the /opt file system as the file
system to be reduced.
ii. Select the intermediate storage file system.
The intermediate storage file system is used to store the data of
the file system which is to be reduced. It must have sufficient free
space. If the space is insufficient, you can delete useless files in
this system or select multiple intermediate storage file systems.
For example, /opt has 72000 KB files, and /home has 213865 KB of
space. Therefore, select /home as the intermediate storage file
system.
iii. Reboot the system and log in as a single user. Copy the data of the
file system which is to be reduced into the intermediate storage file
system. The commands are:
#mount *
#cp r opt /home/
iv. Delete the logical volume where the filesystemsrc file system is
located.
To delete the /opt logical volume, the commands are:
#umount /opt
//Uninstall the logical volume to be deleted.
#lvremove /dev/vg00/lvol6
//Delete logical volume.
v. Re-create a logical volume smaller than the original logical volume,

and then create the file system and install it to the original
directory.
To add the file system volume named lvo16 whose size is 80 MB
onto vg00 using the directory /opt as the mounting point, the
commands are as follows:
#lvcreate -L 80 -n lvo16 /dev/vg00
//Create the logical volume lvo16

#newfs -F hfs /dev/vg00/lvo16
//Create a file system for the logical volume

# mount /dev/vg00/lvo16 /opt
//Mount the logical volume on /opt

#bdf
//Query whether the logical volume is successfully created.
48
vi. Execute the following command to copy files back to the re-created
file system and restore the original file system:
#cp r /home/opt/* /opt/
Note: The calculation methods for the free space of a volume group is as
follows:
Log in the system as root user, execute the command # v g d i s p l a y , and

obtain the values of Free PE and PE Size from the displayed results.
Free PE is the free space of the volume group, in the unit of PE; PE Size is the
space size of one PE, in the unit of MB.
The free space of a volume group = Free PE * PE Size (unit: MB).
3. How to deal with the failure when uninstalling the CD-ROM file system
through the u m o u n t command?
After installing the EMS on the HP-UX platform using a CD and
rebooting the computer, execute the u m o u n t command. However, the
system reports an error, and the CD cannot be taken out. In this case,
follow the procedure below to take out the CD:
i.
Execute the command m o u n t to install the CD-ROM at a mounting

point (suppose the device file name of CD-ROM is /dev/dsk/c3t2d0
and the installation location is /SD_CDROM).
# mount /dev/dsk/c3t2d0 /SD_CDROM
ii. Execute the command u m o u n t to uninstall the CDROM.

# umount /SD_CDROM
During the procedure, if the system prompts error information, ignore

it.
4. After the EMS is installed on HP-UNIX platform, the client cannot be
started. Why does this happen?
Possible cause: The color bits of the monitor are set incorrectly.
Solution: In the graphic mode, make the following modifications to set
the color bits of the monitor to 24 bits.
i.
Run the sam program.
ii. Select
Display,
X
Server
VISUALIZE-FXE in sequence.
Configuration,
and
HP
iii. Select the Actions -> Modify Default Visual menu.

iv. Set Default Visual to Image, Depth24 True Color.
FAQ for EMS Installation in SUN

1. How to modify the IP address of the host?
Modify the IP addresses with the same domain name in the files
/etc/hosts and /etc/hostname.eri0.
49
Format of hosts file is:

//Loopback address of local host
127.0.0.1 localhost
193.1.2.7 zte
//IP address and domain name of local host
Format of Hostname.eri0 file is:

Zte
//Domain name of local host
2. How to add an IP address to the host?

i.
Execute the command

information of local host.
netstate-r
to
query
the
routing
ii. Execute the command i f c o n f i g a to query current IP address of

local host.
iii. Query the network card name in the file /etc/hostname.interface.
iv. Modify the IP address of the local host in the file /etc/hosts.
You must set the domain names of IP addresses in the hosts file.
The format is as follows:
127.0.0.1 localhost
193.1.2.7 zte
v. Execute the command i n i t 6 to reboot the computer.

3. For the SUN Blade 150 installed with double video cards, the client
cannot be started after the EMS is installed. Why does this happen?
Cause: The client does not support Xvr500 video card.
Solution: Use the M64 video card.
4. On the SUN platform, after the EMS is installed, the client cannot be
started. Why does this happen?
Possible cause: The color bits of the monitor are set incorrectly.
Solution: Perform the following operations to set the color bits of
monitor to 24 bits.
i.
Execute the following command:

#fbconfig prconf
ii. Find C u r r e n t r e s o l u t i o n s e t t i n g : 1 2 8 0 x 1 0 2 4 x 7 6 from the

returned information. 1280x1024x76 is the current resolution.
iii. Check if the depth supports 24 bits. If it supports, execute the
following command:
# fbconfig -res <resolution> - depth 24
//Use the queried resolution for the above r e s o l u t i o n parameter.
5.
What are the network files of a SUN workstation?

hosts file
The hosts file saves the IP address configurations of the workstation.
Changing the IP address in this file can change the IP address of the
network card. Note that the domain name of network card must be
consistent with that saved in the hostname.eri0 file.
50
The content of hosts file is shown in Figure 14.
FIGURE 14 HOSTS FILE (UNDER THE /ETC/ DIRECTORY)
hostname.eri0 file
The hostname.eri0 file saves the domain name of the network card.
The content of hostname.eri0 file is shown in Figure 15.
FIGURE 15 HOSTNAME.ERI0 FILE (UNDER THE /ETC/ DIRECTORY)
netmasks file
The netmasks file saves the network-number and its network mask.
The content of netmasks file is shown in Figure 16.
FIGURE 16 NETMASKS FILE (UNDER THE /ETC/ DIRECTORY)
51
defaultrouter file
The defaultrouter file saves the IP address of the network gate.
The content of defaultrouter file is shown in Figure 17.
FIGURE 17 DEFAULTROUTER FILE (UNDER THE /ETC/ DIRECTORY)
addroute.sh file
The addroute.sh file saves the information about routes. Upon restart,
the computer will automatically load the routes in the addroute.sh file.
The content of addroute.sh file is shown in Figure 18.
FIGURE 18 ADDROUTE.SH FILE (UNDER THE /ETC/ DIRECTORY)
Other Installation FAQ

1. Double-click the executable E300 installation file, but the installation
interface cannot be displayed normally. Why does this happen?
Cause: There is program with higher priority running in the system.
Solution: Kill the programs which have higher priorities than the E300
installation file.
2. The installation process cannot go on. Why does this happen?
52
Possible cause: The firewall of anti-virus program is enabled.

Solution: Quit the firewall program.
3. When installing the EMS in Unix, a prompt Not Enough Disk Space
occurs. Why does this happen?
Possible cause:
The installation directory does not have enough free space.
Solution:
i.
Use a directory with large enough free space as the installation

directory, or clear the original installation directory until it has
enough free space. The recommended free space for the
installation directory is above 4 GB.
ii. Run the s e t u p program again to install the EMS.

4. When installing EMS in Windows operating system, an alert box pops
up, as shown in Figure 19. Why does this happen?
FIGURE 19 SETUP ERROR ALERT BOX
Possible causes:
The installation directory does not have enough free space.
Solution:
i.
Use a directory with large enough free space as the installation

directory, or clear the original installation directory until it has
enough free space. The recommended free space for the
installation directory is above 4 GB.
ii. Run the setup program again to install the EMS.

5. After the EMS is installed, the database cannot be started. Why does
this happen?
Possible causes:
i.
The SYBASE database application is started incorrectly.
ii. dbOid configured in the database file cfg is incorrect, and

parameters are set incorrectly.
iii. If the EMS is in Unix environment, maybe the database creation
failed during installation.
53
iv. In Unix environment, observe the dataserver process to check

whether the database server is successfully started. On the HP-UX
platform, check whether the asynchronous equipment is started.
On the Sun platform, check whether the shared memory parameter
is configured under the directory /etc/system.
Solution:
i.
Start the database system application program named dbsvr.exe

correctly.
ii. Set parameters correctly according to the Configuring Unix section

in Chapter 3.
iii. Start d b m a n program to check whether the database is successfully
created. If no, use dbman to create the database.
iv. Set parameters correctly according to the Configuring Unix section
in Chapter 3
6. If the ZXONM E300 is installed by compact installation, the alert box
shown in Figure 20 appears when starting the server. Why does this
happen?
FIGURE 20 SQL_SERVER ERROR ALLERT BOX
Possible causes:
i.
The SQL Server database is not installed in the computer where the
ZXONM E300 is installed.
ii. The server alias in the SQL Server is configured incorrectly.

Solution:
i.
Install the SQL Server database in the computer where the ZXONM
E300 is installed.
ii. Configure the correct server alias of SQL Server database according
to the section of Configuring SQL Server in Chapter 4..
iii. Reboot the server of ZXONM E300.
7. On the computer where SQL Server database and typical ZXONM E300
are both installed, if the SQL Server and the EMS are started at the
same time, the GUI prompts Database connection failed when
starting the client (GUI). Why does this happen?
Possible causes:
i.
54
The server alias of SQL Server database is not configured after the
ZXONM E300 is installed, thus causing database connection failure.
ii. If the GUI still prompts that the database connection failed after
the server alias of the SQL Sever database had been configured,
the EMS database TransDB may conflict with the SQL Server
database and thus causes DBSVR exception.
Solution:
i.
Configure the correct server alias of SQL Server database according

to the section of Configuring SQL Server in Chapter 4.
ii. Reboot the server and GUI of the ZXONM E300. If the GUI still
prompts database connection failure, perform step iii.
iii. Run the file dbman.bat in the installation directory /dbman to enter
the main interface of the dbman, as shown in Figure 9.
iv. Type 3 and press ENTER to enter the DATABASE MANAGEMENT
window, as shown in Figure 21.
FIGURE 21 DAT AB ASE MAN AGEMENT WINDOW
v. Enter 2 to create a database. If the operation is successful, the

system will prompt Database already created.
vi. Reboot the GUI. Now, the database is null.
6. The system works abnormally when the ZXONM E300 supported by
SYBASE database is installed on Windows XP. How to solve it?
Reinstall the ZXONM E300 supported by SQL Server database. The
ZXONM E300 supported by SYBASE database must be installed on the
Windows 2000 Server operating system.
55
Chapter
Maintenance of EMS
How to deal with the EMS connection fault
How to deal with the database fault
How to deal with the Agent fault
How to set commonly used environmental variables
EMS Connection Fault

Common Faults
1. Causes
External causes: Power supply faults, such as equipment power failure

or too less power supply voltage; fiber faults, such as fiber
performance deterioration or too high loss.
Improper operation: There is wrong configuration.
Equipment faults: Network adapter fault, optical line board fault,

CSA/CSE board fault, or a lot of performance data is reported from NE
to the EMS resulting in ECC path block.
2. Troubleshooting Procedure
Check external causes, e.g., power failure or fiber performance

degradation.
Check whether the EMS configuration is correct or otherwise.
Use the test method to perform self-loop in each segment and locate
the faulty NE.
Use the alarm analysis method to check the optical board and CSA/CSE
board.
Typical Faults and Analysis

1. Symptom:
The EMS cannot get connected to NCP through the Qx interface. It
cannot ping through NCP but can ping through itself.
Analysis and handling:
Check whether the network cable works normally, and whether its type
is correct (straight-through cable or crossover cable).
Check whether the computer network configuration is correct. The EMS

can ping through itself, it indicates that the network adaptor is
correctly installed and the network configuration takes effect. The EMS
cannot ping through NCP; it indicates that the EMS computer, the NE
IP address and the subnet mask may be in different network section.
Set the all the bits of the DIP switch of NCP to ON, setting the NCP to
be in DOWNLOAD status. Execute the t e l n e t 1 9 2 . 1 9 2 . 1 9 2 . 1 1
command, and check whether the NE IP and server IP comply with the
EMS database configurations.
2. Symptom:
Insufficient sub-manager management networks.
Check whether all the sub-managers have been started. If the ZXONM
E300 EMS runs on the UNIX platform, execute the command p s - e f
| g r e p s m g r to check whether they have been started; if the EMS runs
on the Windows 2000 platform, use the task manager to check it.
Check whether the NE is beyond the management capability of

sub-managers. It is recommended that the maximum number under
the management of each sub-manager should not exceed 100. If the
number exceeds this value, start another sub-manager.
3. Symptom:
EMS is unable to manage the access NE, or other NEs except the
access NE.
The current EMS and NEs do not belong to the same network section.
For an NE in the IP protocol stack version, EMS and the NE belong to

same network segment. However, the user does not set IP address of
the access NE as default gateway or do not set a route.
There are redundant IP routes in the EMS. Delete the redundant IP

routes.
4. Symptom:
The EMS can only normally manage some NEs in the network.
58
Check whether the unmanageable NEs are offline, and set the offline
NEs to online NEs.
Check whether the optical connections between NEs are correct.
Chapter 5 - Maintenance of EMS
Check whether NCP versions of the unmanageable NEs are correct. If

they are incorrect, re-apply the NCP applications which support this
EMS.
When EMS runs on the UNIX platform, check whether the system
parameters of m a x f i l e s a n d n f i l e s are correct.
5. Symptom:
Confusion in IP area division leads to abnormal NE management.
In actual networking, try not to divide any area or use the backbone
area under any circumstances. Generally, when there are too many
NEs on a network (e.g., over 64), the NEs should be divided into
different areas. When the number of NEs exceeds 128, they should be
divided into different areas. In this case, since the network section
division is wrong, it becomes difficult for EMS to monitor all the NEs.
Check whether all the NEs distributed in different areas are directly
connected with the boundary NEs in backbone area.
Confirm that the total number of NEs exceed 128 either in the
backbone area or in non-backbone area, and are directly connected
with the border NEs If this value is exceeded the normal management
becomes impossible. In addition, it is recommended that each border
NE is to be directly connected with the one in non-backbone area.
Confirm whether the NEs in backbone area are connected properly.
Since the ECCs cannot directly work with each other in non-backbone
area, and can only work via backbone area, so please check for the
failure of NE in the ECC path between the backbone area and the
boundary.
Try to reduce the border NEs. Sometime, dividing NEs into many areas
may complicate inter-area relationship.
Database Fault
1. Symptom:
Time out always happens when restoring the database in EMS.
It is the GUI that reports time out.
The database implements the data restore and thus will not be affected
by the GUI time out.
Wait for about 20 minutes. Then log into the GUI again to solve the
problem.
2. Symptom:
The EMS always report that the database crosses the threshold.
59
The reason may be that the maximum number of records set for the
database is too large.
Click the System -> System Data Management -> DB History

Data Archiving menu item. In the DB Capacity Set page, change
the MAX Rows parameter to be smaller, e.g. 5000.
For data to be dumped, export them to a tap driver.
3. Symptom:
After the database has been started up, it is necessary to try several
times to log into the GUI.
This is because that the database startup process is slow.
Wait for 30 seconds after the database is started up. And then log into
the GUI.
Manager Fault
1. Symptom:
Once the Unix system time is modified, the alarm will be refreshed
automatically, and the Manager wont work normally.
Since the Unix system uses the system timer to get the system time.
Once the system time is modified, it may stop the timer or result in
some abnormal case.
Restart the EMS after modifying the system time.
It is recommended to restart the Unix operating system as well.
2. Symptom:
In Unix operating system, after the EMS has been running for some
time, the NCP time gets several hours earlier or later than the Manager
time.
In Unix, check if the timezone is set to the local time zone. If not, set it
to the local time zone.
Agent Fault
1. Symptom:
On HP-UNIX platform, the current alarms can be queried by EMS but
not be reported automatically.
60
Check if the alarm can be queried or not. If not, it indicates Agent does
not report alarm indeed. Thus, the communication with Agent should
be checked by p i n g or the method of obtaining time.
Check if the time of the working station is changed or not. Sometime,

modify the time can make the interval timer stop. Hence, all of the
processes which are relating to the timing will stop. Here, restart
computer can erase this kind of problems.
Other Faults
1. Symptom:
After install EMS which is MSSQL version on the Windows 2000 Server
operation system and start the EMSs Server, the user can not log into
the Server via GUI. Normally, this fault is caused by the disconnection of
the database.
Analyse and Handling
Open Windows Task Management to check the process list, if there

is no d b s v r . e x e process. Then go to the D B directory to check the log
file named d b s v r . l o g , finally, find that the d b s v r . e x e process had
been exited for unexpected reason.
Restart Server and log into the Server via GUI again, but the fault is
still there.
Uninstall ZXONM E300, restart the operation system, and then reinstall,
restart and re-log into the E300, but the fault is still existed.
Start DBMAN tool and select 2. Dataserver Management1. Start

Dataserver3. Use isql tool, if the i s q l tool can be started
successfully, it indicates the S Q L S E R V E R database is normally.
Find that the database port is not occupied by the tool of Fport.exe
which is used to query the port. The port list is shown in Figure 2 2 .
61
FIGURE 22 PORT LIST
Go to C:\Program Files\Common F i l e s \ S y s t e m \ a d o \ m s a d o 1 5 . d l l and

right-click on the file, select a t t r i b u t e item in the shortcut menu to
pop up msdao15.dll window, select version page to find out the
version No. which is 2.5.
Caution: If the version of msdao15.dll is lower than 2.6, the d b s v r . e x e

process will not startup normally when ZXONM E300(MSSQL) is started. The
version must be upgraded to 2.6 or above in order to meet the requirement of
starting.
Go to the directory of ZXONM E300, find \Sqlserver\mdac\zh\dasetup.exe

file, install the file and restart operation system then.
Note: There are two directory files under the \ S q l s e r v e r \ m d a c , they

are Z H and E N . Please select the corresponding file based on the language
environment of the operation system. That is, the operation system in Chinese
langue selects the ZH file, on the other side, the operation system in English
language selects the EH file.
Setting Environment Variables

Overview
Setting the environment variables of the ZXONM E300 can change the
EMS functions. Table 11 lists the commonly used environment variables,
and describes their functions.
62
TABLE 11 COMMONLY USED ENVIRONMENT V ARI ABLES OF ZXONM E300
Environment Variable
Functions
ZTEE300VERUPDATE
It does not exist by default. If it is added, the small version

number will be displayed when querying the EMS version.
ZTEDELPROMPT
If it is added, the system will give prompt when deleting

timeslot by clicking the Delete button in the Service Config
dialog box.
ZTETSHASCLEAR
If it is added, the Clear button is activated in the Service

Config dialog box. Otherwise, the button is not activated. This
button is used to clear all the timeslots.
ZTECLEARPATH
If it is 1, the end-to-end circuit can be cleared. Otherwise,

the end-to-end circuit cannot be cleared.
ZTELINK
If it is added, the system supports upload, upload and

compare, automatic upload and compare of data.
COMDETECTTIMER
It is the timer for disconnecting the GUI and Manager, in unit

of ms.
ZTEPARALLELSEND
It is the delay of sending a command in parallel. Its default

value is 100 ms.
ZTENcpAlgorithm
For ZXMP S390 equipment, if this variable is added, the

Advanced button is activated in the Card Property dialog
box of NCP board, and the algorithm can be selected in the
Advanced dialog box.
ZTEEXCEPTIONALALARM
It does not exist by default. If is added, the system will not

filter out unknown alarms.
ZTEZEROELASPE
If it is 1, the system will filter out the alarms that have been
existed for zero minute and zero second.
ZTEMAXLCTNENUM
It is the number of NEs manageable by the LCT. Its default

value is 5.
ZTEMGREXTPCM
It is zero by default, indicating that the EMS cannot manage

PCM equipment. If it does not exist or its value is not zero, the
EMS can manage PCM equipment.
Setting Environment Variable

This section takes the ZTETSHASCLEAR variable as an example to
illustrate how to set environment variables in Windows operating system.
Refer to this example to set other environment variables.
To set the ZTETSHASCLEAR variable in Windows
1. On the desktop of the computer installed with ZXONM E300 client,
right-click My Computer. Click the Properties menu item in the
shortcut menu popped up.
2. The System Properties dialog box will pop up. Click the Advanced
tab to display the Advanced page shown in Figure 23.
63
FI G U R E 2 3 AD V AN C E D P AG E O F S Y S T EM PR O P E R T I E S D IAL O G B O X
3. Click the Environment Variables button to pop up the Environment

Variables dialog box shown in Figure 24.
FIGURE 24 ENVIRONMENT VARIABLES DIALOG BOX
64
4. Click the New button in the System variables combo box. Then the
New System Variable dialog box will pop up, as shown in Figure 25.
FIGURE 25 NEW SYSTEM V ARIABLE DI ALOG BOX
5. Input ZTETSHASCLEAR in the Variable name text box. And input 1 in

the Variable value text box.
6. Click OK to return to the Environment Variables dialog box shown in
Figure 26.
FIGURE 26 ENVIRONMENT VARIABLES DIALOG BOX WITH ZTETSHAS CLE AR ADDED
7.
Click OK to save the newly added variable.
8. Log out of the ZXONM E300 GUI and log into it again. Open the
Service Config dialog box. Select the Config option button. You can
see that the Clear button is activated.
65
66
Appendix
DBMAN Operations
This appendix uses the DBMAN tool in Window 2000 as an example, briefly
introduces various functions of DBMAN.
The operations of DBMAN in Unix are the same as those in Windows2000,
and are not described in this manual.
DBMAN Overview
DBMAN is a maintenance tool for ZXONM E300 database. It can simplify
the maintenance and upgrade of database server, monitor the database
status, and execute ordinary maintenance tasks.
Major Functions
Installs/uninstalls the database server.
Manages the database server: starts/shuts down the database server;

starts the command line tool of ISQL and the directory edit tool of
DSEDIT to configure the database server.
Manages the database: creates/deletes the EMS database of TransDB,

extends database log and data equipment, clears database log,
recreates database table and storage process, backs up and restores
data.
Monitors the database: queries the database version, space occupation

status of database, database status, synchronization status, and
database table status.
Launching DBMAN
Since server and client may be installed on the same computer or
separate computer, and the server may be installed with Windows or Unix
operating system, there are several different ways to launch the DBMAN
tool.
67
Launching DBMAN on HP-UX Server

Since the HP-UX server is installed with the Unix operating system, it is
necessary to launch DBMAN in the command line interface.
1. Enter the /opt/unitrans/db/dbman directory.
2. Execute the . / d b m a n command.
Launching DBMAN on Windows Server

1.
Enter the ZXONM E300 installation directory.
2.
Run the /dbman/dbman.bat batch program directly.
Launching DBMAN on Client

1.
Execute the command of T e l n e t S e r v e r - I P to log into the server.
2. If the server is installed with the HP-UX operating system, enter the
/opt/unitrans/db/dbman directory, and then execute the . / d b m a n
command to launch DBMAN tool.
3. If the server is installed with the Windows operating system, enter the
ZXONM
E300
installation
directory,
and
then
run
the
/dbman/dbman.bat batch program directly.
DBMAN Main Window in Windows 2000

DBMAN adopts the operation method of text window. Its windows display
text information and executable commands. User can edit text or execute
command by selecting the corresponding number of the command.
The DBMAN main window is as shown in Figure 9. Options in the main
window are described in Table 12.
TABLE 12 DESCRIPTIONS OF DBM AN M AIN WINDOW
Option
Function
Remarks
[ZTE
ZXONM
E300......]
Displays the DBMAN version, which is

the same as the EMS version. The
version number is V3.19 R1P03a as
shown in Figure 9.
Sequence
No. [1]
Configure
directory.
the
database
installation
The default location

SQL_Server database
of
is
EMS
installation
directory/sqlserver.
The default location of

Sybase database is EMS
installation
directory/sybase.
68
Appendix A - DBMAN Operations
Option
Function
Remarks
Sequence
No. [2]
Manage the Sybase database server,

including start/shutdown the database
server, start the command line tool of
ISQL and the directory edit tool of
DSEDIT to configure the database
server.
Dataserver
refers
to
Sybase
database
server.
Dataserver
management is an executable
program running independently
which manages multiple databases.
It is only applicable to Sybase
database.
Sequence
No. [3]
Manage ZXONM E300 database,

including create/delete EMS database
of TransDB, delete the database used
by EMS, extend database log and data
equipment, clear database log, recreate
database table and store processes.
Database: An entity that

manages storage data. It is
managed by Dataserver.
Database refers to the EMS
database
of
TransDB
without
special
announcement.
This option is applicable to

database of SQL_Server
and Sybase.
Sequence
No. [4]
Back up and restore ZXONM E300 data.

database of SQL_Server and
Sybase.
Sequence
No. [5]
Check the timeslot occupation status of

SDH equipment.

Sybase.
Sequence
No. [6]
Restore the data backed up by ZXONM

E100 in the ZXONM E300.

Sybase.
Sequence
No. [7]
Change the NE software version.
This option is used to

upgrade ZXMP S380/ZXMP
S390 NE with the software
version of V3.1 to version
V3.2.

database of SQL_Server
and Sybase.
Sequence
No. [8]
Change the NE ID.
Sequence
No. [9]
V3.16 backup file update to V3.17
For the version before V3.17,

update the data from 9 bit to 32 bit
which is of the monitoring point.
Sequence
No. [10]
Analysis and process network data
Analysis
and
process
the
unexpected connection, avoid that
the algorithm module can not
startup because of the unexpected
connection.
Sequence
No. [11]
Manage the replication system. Refer to

the Replication System Management
Instructions section in this appendix for
details.
This option is only applicable to

Sybase database.
69
Option
Function
Remarks
Sequence
No. [12]
Timer
synchronization
system
management is used to configure the
bidirectional synchronization between
master and slave stations.
This option is only applicable to

Sybase database. Total backup of
the data on slave station is
guaranteed by configuring the
history data timer synchronization
system. The operation is used to
avoid from no history data on
slave station under the condition of
master/slave or scarcity of the
history data of all stations because
of the switching between master
and slave station.
Sequence
No. [13]
Exit DBMAN main window.
Enter the corresponding number after the prompt of [Enter the number
of your choice and press return], and then press ENTER. The child
window of the option will appear. The operations in the child window are
similar to those of the main window.
Database Server Management

Operations
The DATASERVER MANAGEMENT option is only applicable to Sybase
database.
Enter 2 and press ENTER in the DBMAN main window shown in Figure 9,
then the DATASERVER MANAGEMENT window shown in Figure 27 will
appear.
FIGURE 27 DAT ASERVER M AN AGEME NT WINDOW
70
In this window, user can start/stop Sybase database server, start up the
command line tool of ISQL, and use the directory edit tool of DSEDIT to
configure the database interface.
Table 13 describes the options in the DATASERVER MANAGEMENT
window.
TABLE 13 DESCRIPTIONS OF DAT ASERVER MAN AGEMENT WINDOW
Option
Function
1. Start dataserver
Start up the Sybase database server. If the database server is

started up, the Dataserver status will switch to running.
2. Stop dataserver
Shut down the Sybase database server. If the database server is

shut down, the Dataserver status will switch to down.
3. Use isql tool
The isql tool is a command line maintenance tool provided by

Sybase. User can execute SQL commands, and perform
complicated maintenance operations on database server and
database using the isql tool.
4. Use isql tool with

output file
This option means the output is not displayed in the window of sql
command, but displayed in curdir:QueryTxt.log.
5. Configure interface
Run the dsedit tool. User can configure Sybase directory service
using this tool. Each record in this tools main window contains
database server name, IP address, and port. Only when the
directory service has been configured correctly, can the application
program visit the local or remote database server.
6. Exit
Exit this window and return to the DBMAN main window.
Starting Database Server

1. Enter 1 and press ENTER in the DATASERVER MANAGEMENT
window shown in Figure 27.
2. Check if the database server is started up. If not, try starting up it
again.
Stopping Database Server

Enter 2 and press ENTER in the DATASERVER MANAGEMENT window
shown in Figure 27.
Note: Once the database server is restarted, the system will automatically
synchronize the changed data during the period when the database server was
stopped.
71
Using isql Tool

shown in Figure 27. Then the SQL Query Analyzer dialog box will pop
up.
In this window, user can type command lines to control the database
server. The ISQL tool is generally used for advanced functions and will not
be described in detail here.
Using isql Tool with Output File

shown in Figure 27. Then the SQL Query Analyzer dialog box will pop
up.
The option is similar to Use isql tool, except that the output is not
displayed in the window of s q l command but displayed in
curdir:QueryTxt.log.
Each time running 4.Use isqltool with output file, a new file named
Q u e r y T x t . l o g will be created. The Q u e r y T x t . l o g is used to save all of
the result after running the isql tool; once the isql tool is used again, the
original Q u e r y T x t . l o g will be cleared.
Configuring Database Interface

shown in Figure 27. Then the main window of dsedit tool will pop up, as
shown in Figure 28.
FIGURE 28 MAIN WINDOW OF DSEDIT TOOL
Note: The dsedit tool is seldom used. When the database cannot start up
normally, use this tool.
72
Database Management
Operations
then the DATABASE MANAGEMENT window shown in Figure 21 will
appear.
Table 14 describes the options in the DATABASE MANAGEMENT window.
TABLE 14 DESCRIPTIONS OF DAT AB ASE M AN AGEME NT WINDOW
Option
Function
1. Database monitor
Monitor the database, display the DATABASE MONITOR

window.
2. Create database
Create database for the EMS.
3. Drop database
Delete the EMS database. Note that all the EMS data will be
lost once the EMS database is deleted.
4. Extend database
Extend the database. It is only applicable to Sybase database.
5. Clear database log
Clear the database log. Generally, the database automatically

clears its log.
6. Recreate tables & rpc
Recreate tables and storage process. Note that all the EMS
data will be lost once this operation is performed. In case of
need to clear all the EMS data, perform this operation. Upon
successful operation, the EMS will enter the status that it was
first installed.
7. Exit
Monitoring Database
Enter 1 and press ENTER in the DATABASE MANAGEMENT window
shown in Figure 21. Then the DATABASE MONITOR window shown in
Figure 29 will appear. The information displayed in the window is
described in Table 15.
73
FIGURE 29 DAT AB ASE M ONITOR WINDOW
TABLE 15 DESCRIPTIONS OF DAT AB ASE MONITOR WINDOW
Information
Meaning
Database
version
Displays the database version which is the same as the EMS version.
Displays the database replication status, which can be one of the following
states:
Replication
status
enable: with replication configured.

disable: without replication configured.
Displays the database status, which can be:
Config
status
74
DB
normal
suspect: the database is unavailable now. It is necessary to

find out the reason and restore the database.
crashed: the database is unavailable now. It is necessary to

find out the reason and restore the database.
recover: the database is being recovered and is unavailable

now. If the status last for long, interfere it manually.
loglow: the free space for log is little. If this state lasts for
long, it is necessary to clear the log, extend the log space, or
cancel the replication.
datalow: the free space for data is little. It is necessary to

check the history data threshold and decrease it, clear part of
history data, or extend the data space.
logfull: the log is full. It is necessary to immediately clear the

log, extend the log space, or cancel the replication.
datafull: the data space is full. It is necessary to immediately

check the history data threshold and decrease it, clear part of
history data, or extend the data space.
Information
Meaning
nonsexist: the database does not exist. It is necessary to

recreate it.
Note that more than one state may appear together, e.g. datafull logfull.
Config
DB
object status
Displays the database object/table status, which can be normal, corrupt, or

unknown
Config
DB
Total size (M)
Displays the total size of database including data and log.
Config
DB
Data size (M)
Displays the size of data space in database.
Config
DB
Log size (M)
Displays the size of log space in database.
Config
DB
Free data size
(M)
Displays the free size of data space in database.
Config
DB
Free log size
(M)
Displays the free size of log space in database.
History
status
Displays the history database status
DB
History
DB
object status
Displays the history database object status
History
DB
Total size (M)
Displays the total size of history database including data and log.
History
DB
Data size (M)
Displays the size of data space in history database.
History
DB
Log size (M)
Displays the size of log space in history database.
History
DB
Free data size
(M)
Displays the size of free data space in history database.
History
DB
Free log size
(M)
Displays the size of free log space in history database.
Exit
Enter 1 and press ENTER to exit this window and return to the DATABASE
MANAGEMENT window.
Creating Database
shown in Figure 21. The system will check if the database has been
created. If not, it will create a database.
Deleting Database
shown in Figure 21. The system will automatically back up the database.
75
After that, it will prompt if to delete the database, as shown in Figure 30.
Input Y and press ENTER to delete the EMS database.
FIGURE 30 DELETING DAT ABASE
Extending Database
shown in Figure 21. Then the EXTEND DATABASE window will appear, as
shown in Figure 31. Table 16 describes the information and options in the
window.
F I G U R E 3 1 E X T E N D D A T A B AS E W I N D O W
TABLE 16 DESCRIPTIONS OF EXTEND DAT AB ASE WINDOW
Information/Option
76
Meaning/Function
Information/Option
Meaning/Function
Available data device
Displays the available data device in the format of device

name[size]. The size is in unit of MB. For example,
TransDB_DAT[10] TransDB_DAT1[100] represents for two
available data devices: TransDB_DAT and TransDB_DAT1. Their
sizes are 10 MB and 100 MB respectively.
Available log device
Displays the available database log device in the format of

device name[size]. The size is in unit of MB. For example,
TransDB_LOG[10] TransDB_LOG1[100] represents for two
available
database
log
devices:
TransDB_LOG
and
TransDB_LOG1. Their sizes are 10 MB and 100 MB respectively.
1. Data device name
Select a data device from the devices listed in Available data

device for data space extension.
2. Data device size (M)
Input the size of data device after extension. It cannot exceed

the maximum available space of the selected data device.
3. Log device name
Select a log device from the devices listed in Available log

device for log space extension.
4. Log device size (M)
Input the size of log device after extension. It cannot exceed

the maximum available space of the selected log device.
5.
Extend
database
config
Extend the data space or/and log space as per the above
configurations. The log space and data space can be extended
simultaneously or separately.
6.
Extend
database
history
Extend the history database.
7. Create new device
If there is no data device or log device available, create a new

database device first, and then extend it. The CREATE DEVICE
window shown in Figure 32 will appear once this option is
selected.
8. Exit
Exit this window and return to the DATABASE MANAGEMENT

window.
To create a new device

Enter 7 in the EXTEND DATABASE window shown in Figure 31. Then the
CREATE DEVICE window shown in Figure 32 will appear. Table 17
descries the options in the window.
FIGURE 32 CRE ATE DEVICE WINDOW
77
TABLE 17 DESCRIPTIONS OF CRE ATE DEVICE WINDOW
Option
Function
1. Device name
Input the name of the new device.

Input the physical name of the new device. The rules
are:
2. Device phyname
In Unix, it can be a file or logical volume
In Windows, it must be a complete directory.
If it is a logical volume, this logical volume

must have been existed already.
If it is a file that does not exist, the system

will automatically create the file.
3. Device size (M)
Input the size of the device, in unit of MB.
4. Create device
Create a new device as per the above configurations.
5. Exit
Exit this window and return to the CREATE DEVICE

window.
Clearing Database
shown in Figure 21.
Recreating Tables & Stored Procedure

shown in Figure 21.
Backing Up and Restoring Data

then the BACKUP AND RESTORE window will appear, as shown in Figure
33. Table 18 describes the options in the window.
FIGURE 33 BACKUP AND RESTORE WINDOW
78
TABLE 18 DESCRIPTIONS OF BACKUP AND RESTORE WINDOW
Option
Function
1. Backup database
Enter the BACKUP DATABASE window where data can

be backed up.
2. Restore database
Enter the RESTORE DATABASE window where data

can be restored.
3. Merge another EMSs data
Merge the databases of two EMSs into one database. It

is applicable when data of multiple networks need to be
merged.
4. Backup NE Time slot
Back up the timeslot (service) configuration of the

selected NE.
5. Restore NE Time slot
Restore the timeslot (service) configuration of the

selected NE.
6. Backup NE information
Back up the basic information and configuration data of

the selected NE.
7. Restore NE information
Restore the basic information and configuration data of

the selected NE.
8. Exit
Exit this window and return to the DATABASE

MANAGEMENT window
Backing up Data
Enter 1 and press ENTER in the BACKUP AND RESTORE window shown
in Figure 33. Then the BACKUP DATABASE window will appear, as shown
in Figure 34. Table 19 describes the options in the window.
FIGURE 34 BACKUP D ATAB ASE WINDOW
TABLE 19 DESCRIPTIONS OF BACKUP DAT AB ASE WINDOW
Option
Function
1.
Backup
directory
Enter the backup directory where the data will be backed up. If this
directory does not exist, DBMAN will automatically create it. Note that
the directory must be complete, e.g. /opt/0405.
2. Backup config
data
Choose whether to back up the EMS configuration data.
79
Option
Function
3. Backup history
data
Choose whether to back up the EMS history data including history

alarms, history performance, history events, and security log.
4. Backup
Perform the backup operation as per the above settings. DBMAN will
generate a series of files under the backup directory. Each file is saved
in ASCII format and corresponds to a database table. The system will
display the backup status of each table during the backup procedure.
5. Exit
Exit this window and return to the BACKUP AND RESTORE window.
Description of Backup File
Naming rule of backup file

Each backup file corresponds to a table in the database. The file name
is in the format of table-name.dat.
Content rule of backup file

The backup file is saved in ASCII format. The first line of a file is the
table name. And each of the subsequent lines represents for one
record in the table. Fields are separated by comma.
Backup information file

Each data backup has a backup information file named dbmanbk.dat.
It saves the information of this backup, including backup date, version,
whether the backup includes the configuration data and history data.
Difference between Data Backups via DBMAN and via EMS

The data backed up via DBMAN are incompatible with the data backed
up via EMS. Do not mix them up.
Data backup using DBMAN can back up both the database
configuration and history data. It can back up all the data of EMSs
which have earlier versions than current DBMAN version. However, by
doing so, the system may prompt that some table does not exist in the
database. Skip such prompts. Data backup/restore using DBMAN is
generally applied to the EMS upgrade.
Restoring Data
in Figure 33. Then the RESTORE DATABASE window will appear, as
shown in Figure 35. Table 20 describes the options in the window.
80
FIGURE 35 RESTORE DATAB ASE WINDOW
TABLE 20 DESCRIPTIONS OF RESTORE D AT AB ASE WINDOW
Information/Option
Function
Version
Display the version of the selected backup data.
Date
Display the backup date of the selected backup data.
1. Backup directory
Enter the backup directory where the backup data are located. The
data under this directory will be restored. The directory must be
complete.
2. Restore config data
Choose whether to restore the EMS configuration data.
3. Restore history data
Choose whether to restore the EMS history data including history

alarms, history performance, history events, and security log.
4. Restore
Perform the restore operation as per the above settings. DBMAN

will first clear the corresponding files of current EMS, and then
restore the data under the backup directory. The system will
display the restore status of each table during the restore
procedure.
5. Exit
Exit this window and return to the BACKUP AND RESTORE

window.
Merging Another EMSs Data

in Figure 33. Then the MERGE ANOTHER EMSS DATA window will
appear, as shown in Figure 50. Table 21 describes the options in the
window.
81
FIGURE 36 MERGE ANOTHER EMSS D AT A WINDOW
TABLE 21 DESCRIPTIONS OF MERGE ANOTHER EMSS DAT A WINDOW
Information/Option
Function
Current EMS Version
Display the version of current EMS.
1. Directory including
backup files
Enter the backup directory where the backup data are located. The
data under this directory will be restored. The directory must be
complete.
2. Start merge
Start merging another EMSs data.
3. Exit

window.
Backing up NE Timeslot
in Figure 33. Then the Backup NE TS window will appear, as shown in
Figure 37. Table 22 describes the options in the window.
FIGURE 37 BACKUP NE TS WINDOW
TABLE 22 DESCRIPTIONS OF BACKUP NE TS WINDOW
82
Information/Option
Function
Selected NE
Display the selected NE.
1. Backup File
Enter the backup directory where the backup file is located.
2. Select NE
Select the NE whose data are to be backed up.
Information/Option
Function
3. Backup
Execute the backup command.
4. Exit

window.
Restoring NE Timeslot
in Figure 33. Then the Restore NE TS window will appear, as shown in
FIGURE 38 RESTORE NE TS WINDOW
TABLE 23 DESCRIPTIONS OF RESTORE NE TS WINDOW
Information/Option
Function
Selected NE
1. Backup File
2. Select NE
Select the NE whose data are to be restored.
3. Restore
Execute the restore command.
4. Exit

window.
Backing up NE Information
in Figure 33. Then the Backup NE Style window will appear, as shown in
83
FIGURE 39 BACKUP NE STYLE WINDOW
TABLE 24 DESCRIPTIONS OF BACKUP NE STYLE WINDOW
Option
Function
1. Backup NE From EMS

Database
Back up the NEs information using the current EMS data.
2. Backup NE From
EMS-backuped Files
Back up the NEs information using the EMS backed up files.
3. Exit

window.
Restoring NE Information
in Figure 33. Then the Restore NE Style window will appear, as shown in
FIGURE 40 RESTORE NE STYLE WINDOW
TABLE 25 DESCRIPTIONS OF RESTORE NE STYLE WINDOW
84
Option
Function
1. Restore NE From EMS

Database
Restore the NEs information using the current EMS data.
2. Restore NE From
EMS-backuped Files
Restore the NEs information using the EMS backed up files.
3. Exit

window.
Checking Timeslot
then the Check ZXSM TS window shown in Figure 41 will appear. Table
26 describes the options in the window.
FIGURE 41 CHECK ZXSM TS WINDOW
TABLE 26 DESCRIPTIONS OF CHECK ZXSM TS WINDOW
Information/Option
Function
Selected NE
1. Backup File
2. Select NE
Select the NE to be checked with the timeslot occupation status.
3.
Use
Algorithm
Enhanced
Choose whether to use the service priority algorithm. The

default value is No.
4. Check TS
Check the timeslot occupation status.
5. Exit
Restoring ZXONM E100 data in

ZXONM E300
This operation can only be performed by ZTE maintenance personnel and
thus is not described here.
85
Changing NE Software Version

Note: This option is used to upgrade ZXMP S380/ZXMP S390 NE with the
software version of V3.1 to version V3.2.
then the Chang Ne Software Version window shown in Figure 42 will
appear. Table 27 describes the options in the window.
FIGURE 42 CHANG NE SOFTWARE VERSION WINDOW
TABLE 27 DESCRIPTIONS OF CHANG NE SOFTWARE VERSION WINDOW
Information/Option
Function
Selected Ne: All Nes in

E300 database
Display the selected ZXMP S380/S390 NE(s). For the first time
to enter this window, all the ZXMP S380/S390 NEs are selected
by default.
1. Select the Single Ne
Select a ZXMP S380/S390 NE.
2. Select All Ne : yes
Select all the ZXMP S380/S390 NEs.
3. From 3.1 to 3.2
Change the software versions of selected ZXMP S380/S390 NEs

from V3.1 to V3.2.
4. From 3.2 to 3.1
Change the software versions of selected ZXMP S380/S390 NEs

from V3.2 to V3.1.
5. Help
Display the help information.
6. Exit
Changing Software Versions of All NEs

1.
Enter 3 or 4 and press ENTER in the window shown in Figure 42.
2. The system will prompt

successful conversion
86
restarting
ZXONM
E300
Server
upon
Changing Software Version of Selected

NE
1.
Enter 2 and press ENTER in the window shown in Figure 42.
2. The Change Ne Software Version window with Selected All Nes

disabled will appear, as shown in Figure 43. There is no Selected Ne,
and the option of Select All Nes becomes no.
FIGURE 43 CHANGE NE SOFTWARE VERSION WINDOW WITH SELECTED ALL NES

DISABLED
3. Enter 1 and press ENTER. The SELECT NE window shown in Figure 44

will appear. It lists the names and IDs of all ZXMP S380/S390 NEs.
FIGURE 44 SELECT NE WINDOW
4. Type the sequence number of an NE and press ENTER. The Chang Ne

Software Version window shown in Figure 42 will appear.
For example, to change the software version of the NE named S380 in
Figure 44, type 2 and press ENTER. The Chang Ne Software Version
window shown in Figure 45 will appear. The Selected Ne item
displays S380.
87
FIGURE 45 CHANG NE SOFTWARE VERSION WINDOW (CHANGE SOFTWARE OF THE

SELECTED NE)
5. To change the NEs software version from V3.1 to V3.2, type 3 and
press ENTER.
6. The system will prompt
successful conversion
restarting
ZXONM
E300
Server
upon
Changing NE ID
then the Chang old NeId to new NeId window shown in Figure 46 will
appear. Table 28 describes the options in the window.
FIGURE 46 CHANG OLD NEID TO NEW NEID WINDOW
TABLE 28 DESCRIPTIONS OF CHANG OLD NEID TO NEW NEID WINDOW
88
Information/Option
Function
Selected Ne: All Nes in

E300 database
Display the selected NE(s). For the first time to enter this
window, all the NEs are selected by default.
1. Select the Single Ne
Select a single NE.
2. Change history data

Neid
Choose whether to change the NE Ids in history data. The

default value is no.
Information/Option
Function
3. From old NeId to new

NeId
Change the old NE ID into the new NE ID.
5. Help
Display the help information.
6. Exit
V3.16 Backup File Update to

V3.17
then the V3.16 BACKUPFILE UPDATE TO V3.17 window shown in
Figure 47 will appear. Table 29 describes the options in the window.
FIGURE 47 V3.16 BACKUP FILE UPDATE TO V3.17 WINDOW
TABLE 29-DESCRIPTIONS OF V3.16 BACKUPFILE UPD ATE TO V3.17 WINDOW
Information/Option
Function
1. DumpFile
The data file of dump
2. Dbsvrs backup
The backup file of dbsvr
3. Dbmans backup
The backup file of Dbman
4. Exit
Exit this window and return to the DBMAN

main window.
89
Analyse and Process Network

Data
then the ANALYSE AND PROCESS NETWORK DATA window shown in
Figure 48 will appear. Table 30 describes the options in the window.
FIGURE 48 AN ALYSE AND PROCESS NETWORK DAT A WINDOW
TABLE 30-DESCRIPTIONS OF ANALYSE AND PROCESS NETWORK DATA
Information/Option
Function
1. Analyse and process Nelink
Analyse and process Nelink.
2. Exit
Exit this window and return to the DBMAN

main window.
Replication System Management

Operations
then the REPLICATION SYSTEM MANAGEMENT window shown in
Figure 49 will appear.
This window is the main window for configuring, maintaining, and
monitoring the replication system.
90
FIGURE 49 REPLICATION SYSTEM MANAGEMENT WINDOW
The elements of the window are described below:
1. Primary EMS IP address

It displays the IP address of the Primary EMS. The format is: IP
address (local).
When the local EMS is the Primary EMS, it will display the IP address
(local).
If the Configure Local EMS operation is not executed or the
Replication Server is not installed, it will display unknown.
2. Replication Server installation

Enter the REPLICATION SERVER INSTALLATION window and install
or uninstall the Replication Server locally.
3. Replication system configuration

Enter the REPLICATION SYSTEM CONFIGURATION window.
4. Replication system maintenance

Enter the REPLICATION SYSTEM MAINTENANCE window.
5. Replication system monitor

Enter the REPLICATION SYSTEM MONITOR window.
6. Exit
Exit this window and return to last level.
Installing/Uninstalling Replication Server

Replication Server can be installed or uninstalled on the Primary EMS only.
In the REPLICATION SYSTEM MANAGEMENT window of the Primary
EMS, select Replication Server installation to enter the REPLICATION
SERVER INSTALLATION window, as shown in Figure 50
91
FIGURE 50 REPLICATION SERVER INSTALL ATION W INDOW
1. Install Replication Server on local site

Install the replication server on the local EMS. After successful
installation, the local IP address will be displayed in Primary EMS IP
Address in the REPLICATION SYSTEM MANAGEMENT window, as
shown in Figure 49.
2. Uninstall Replication Server from local site

Uninstall the replication server from the local EMS.
Caution: Uninstallation of the replication server maintenance tool will cause

the replication system to stop automatically.
3. Exit
Configuring Replication System

The functions of the REPLICATION SYSTEM CONFIGURATION window
include:
Display configurations of the replication system and local EMS.
Add, delete or modify EMS information.
Configure replication data type.
Configure replication directions.
Back up and restore replication system configurations.
Initialize the replication system.
In the REPLICATION SYSTEM MANAGEMENT window, select

Replication system configuration to enter the REPLICATION SYSTEM
CONFIGURATION window, as shown in Figure 51.
92
FIGURE 51 REPLICATION SYSTEM CONFIGUR ATION WINDOW
Local EMS
It displays the name and IP address of the local EMS. The format is:
EMS name (IP address).
If the maintenance tool cannot identify the local EMS, the system
displays unknown. In this case, the user must configure the local
EMS.
Replicate Data
Display the configured replication data type.
If only SDH is selected, SDH is displayed.
If only WDM is selected, WDM is displayed.
If both types of data are selected, SDH WDM is displayed.
EMS Configuration
Display all current EMS information of the replication system in the
following format:
EMS
DSNAME
IPADDRESS
IPPORT
EMS: EMS name. Space is not allowed between characters.
DSNAME: Name of the database server generated by the system

automatically. It is the unique identification of EMS database in the
replication system, which cannot be modified.
93
IPADDRESS: EMS IP address.
IPPORT: It is the fixed database server port of the system. It is for

display only and cannot be modified.
Replicate Direction Configuration

Display the replication direction from an EMS to another EMS in the
following format:
FROM
Source EMS
TO
Destination EMS
Source EMS: Source EMS of the replication direction.
Destination EMS: All the destination EMSs of the source EMS.
1. Config local EMS

Enter the SELECT LOCAL EMS window and configure the local EMS.
2. Configure EMS
Enter the CONFIGURE EMS window to add, delete or modify EMS.
3. Configure direction
Enter the REPLICATION DIRECTION CONFIGURATION window and
configure the replication directions.
4. Configure replicate data

Enter the CONFIG REPLICATION DATA window and configure
replication data type.
5. Backup & Restore configuration

Enter the BACKUP AND RESTORE REPLICATION SYSTEM
CONFIGURATION window to back up and restore configuration of the
replication system.
6. Initialize replication system

Initialize the replication system.
7. Exit
Configuring Local EMS

In the REPLICATION SYSTEM CONFIGURATION window shown in
Figure 51, select Config local EMS to enter the SELECT LOCAL EMS
window as shown in Figure 52.
94
FIGURE 52 SELECT LOC AL EMS WINDOW
Sequence No. 1 to N: Display all the EMS names, e.g. 1, 2. Specify the
local EMS by entering the serial number of the EMS. After successful
operation, the name and IP address of the local EMS will be displayed
in Local EMS, as shown in Figure 51.
Exit: Exit this window and return to last level.
Note: The SELECT LOCAL EMS window displays information of all the EMSs
that have been configured. If no EMS information is displayed, it is necessary to
configure the EMSs first. Refer to the EMS Configuration section in this appendix.
Configuring EMS
Figure 51, select Configure EMS to enter the CONFIGURE EMS window,
as shown in Figure 53. Add or delete a EMS, or modify the name and IP
address of a selected EMS.
FIGURE 53 CONFIGURE EMS WINDOW
1. Add: Add an EMS. Enter the EMS INFORMATION window, as

shown in Figure 54.
95
FIGURE 54 EMS INFORMATION WINDOW
EMS Name: EMS name
IPADDRESS: EMS IP address
Save: Save EMS information
Exit: Exit this window and return to the last level.

In the window, enter the name and IP address of the EMS and
select Save to save the modifications.
2. Modify: Select the EMS to be modified and then enter the EMS
INFORMATION window. Modify the EMS information in the window.
3. Drop: Delete an EMS from the configuration. When the EMS

replication status is ACTIVE, the EMS cannot be deleted. The user
must deactivate the EMS before deleing it.
4. Exit: Exit this window, and return to last level.
Configuring Replication Direction

The user must configure replication directions for each EMS. Select the
source EMS and destination EMS in sequence.
To configure replication direction
1. In the REPLICATION SYSTEM CONFIGURATION window shown in
Figure 51, select Configure direction, the SELECT SOURCE EMS
window will appear, as shown in Figure 55.
FIGURE 55 SELECT SOURCE EMS WINDOW
96
Sequence No. 1 to N: Display names of all source EMSs, e.g.1, 2.
2. After selecting the source EMS, enter the CONFIGURE DIRECTIONS

window, as shown in Figure 56.
FIGURE 56 CONFIGURE DIRECTIONS WINDOW
Source EMS: The EMS selected in Figure 55. It is the source EMS
of the replication direction.
Sequence No. 1 to N: Destination EMS, e.g.1,2, indicating whether

there is replication direction from the source EMS to this EMS. The
value of this item is yes or no.
All: Select all EMSs. If it is selected, the replication direction would

be from the source EMS to all other EMSs.
Save: Save the above configurations.
Exit: Exit this window, and return to last level.
Checkpoint: If the replication status of EMS is not INACTIVE, it is not

allowed to change the replication direction with this EMS as the source. The user
must deactivate the EMS first.
Configuring Replication Data

Figure 51, select Config replicate data to enter the CONFIG
REPLICATION DATA window as shown in Figure 57.
97
FIGURE 57 CONFIG REPLIC ATION D AT A WINDOW
1. SDH: Displays whether to replicate SDH data.
2. WDM: Displays whether to replicate WDM data.
3. Exit: Exit this window and return to last level.
Backing up/Restoring Replication System Configuration

Figure 51, select Backup & Restore configuration to enter the BACKUP
AND RESTORE REPLICATION SYSTEM CONFIGURATION window as
shown in Figure 58.
FIGURE 58 BACKUP AND RESTORE REPLICATION SYSTEM CONFIGUR ATION

WINDOW
1. Backup File: Backup file of replication system configuration. If this

file does not exist, the system will create this file and back up the
configuration data of replication system in this file. For data restoration,
the system reads configuration data from the file and restores it to the
replication server.
2. Backup: Back up configuration. Backup data includes configuration

of replication data, EMS configuration, and configuration of replication
directions.
It is recommended to back up configuration data after the replication
system is configured.
98
3. Restore: Restore configuration. Restore the configuration data in

the Backup File without re-entering replication data type, EMS
information, and replication directions.
After data is restored, the procedure of configuring replication system

is as follows:
i.
In the Primary EMS, restore configuration of the replication system.
ii. Establish the replication data reference to make the data of

replication EMSs consistent.
iii. Configure the local EMS of the replication system.
iv. Initialize the replication system.
v. Check the status of the replication system.
The steps such as preparations, replication system design, replication
server installation, and replication system configuration are omitted.
Initializing Replication System

Initializing the replication system will activate the replication of all EMSs in
the replication system, and will configure the replication server with the
default Disk Partition.
The default disk partition is 1000 MB. If the disk has inadequate space,
modify the parameter repPartitionSize in the cfg file under the directory
EMS installation directory\dbman\etc.
Figure 51, select Initialize replication system to begin initialization.
After that, restart the replication server.
Maintaining Replication System

Maintenance of the replication system involves:
Start replication server.
Shut down replication server.
Start replication system.
Stop replication system.
Clear replication system.
Extend the Disk Partition of the replication server.
Activate/deactivate EMS replication.
Manually replicate data.
Use the interactive ISQL tool of the replication server.

Replication system maintenance to enter the REPLICATION SYSTEM
MAINTENANCE window, as shown in Figure 59.
99
FIGURE 59 REPLICATION SYSTEM M AINTEN ANCE WINDOW
Starting Replication Server

In the REPLICATION SYSTEM MAINTENANCE window, select Start
replication server to check if the replication server is started.
If the replication server is not started, the system will start the server.
Note that the replication server runs on the primary EMS only.
Shutting Down Replication Server

In the REPLICATION SYSTEM MAINTENANCE window,
Shutdown replication server to stop the replication system.
select
After the replication server restarts, the system will automatically replicate
data modified during the shutdown period.
Starting Replication System

In the REPLICATION SYSTEM MAINTENANCE window, select Start
replication system to start the replication system. Data can be
replicated only when the replication system is running.
100
Caution:
After the replication system is started, the REPLICATION SYSTEM

MONITOR
window (refer to Monitoring Replication System section in this
appendix) appears. Check if the replication system works normally and test the
replication system. If replication fails, the user needs to deactivate the
corresponding EMS replication and then activate it (Refer to Activating EMS
Replication section and Deactivating EMS Replication section in this appendix).
The data modified during shutdown period of the replication system cannot be
restored. Therefore, the user must ensure that data references of all EMSs before
starting are the same.
Stopping Replication System

In the REPLICATION SYSTEM MAINTENANCE window, select Stop
replication system to stop the replication system.
After the replication system restarts, replication of some EMSs may fail.
The user needs to deactivate and activate the invalid EMS replications.
Caution: Data modified during shutdown period cannot be replicated even if

the replication system is restarted. The user must be careful with this function.
Clearing Replication System

In the REPLICATION SYSTEM MAINTENANCE window, select Clear
replication system to clear all configurations of the replication system,
including replication data type, EMS and replication directions.
After clearing, the whole replication system stops running. The user needs
to reconfigure the replication system or restore configuration data of the
replication system from the backed up data.
Extending Disk Partition of Replication Server

If the disk partition space of the replication server is inadequate (refer to
the Monitoring Replication System section in this appendix), it is necessary
to extend the space of the hard disk partition. In the REPLICATION
SYSTEM MAINTENANCE window, select Extend disk partition to enter
EXTEND REPLICATION SERVER DISK window, as shown in Figure 60.
101
FIGURE 60 EXTEND REPLIC ATION SERVER DISK WINDOW
Current Size (M): Display the current disk space of the replication
server.
1. Growth Size (M): Space to be added with the unit of MB. After the
space is successfully extended, the value displayed in Current Size is
Original Size + Growth Size.
2. Execute: Execute the extension task.
Activating EMS Replication

Activate EMS replication to make specified ZXONM E300 EMS enter the
replication state. Only after EMS replication is activated, can the EMS
participate in data replication of the replication system.
In the REPLICATION SYSTEM MAINTENANCE window, select Activate
EMS replication to enter the SELECT EMS window, as shown in Figure
61.
FIGURE 61 SELECT EMS WINDOW (ACTIVATE EMS REPLICATION)
102
Sequence No. 1 to N: List all the EMSs, e.g.1,2. After an EMS is

selected, the replication of the EMS will be activated.
After EMS replication is activated successfully, enter the REPLICATION

SYSTEM MONITOR window to check the status of activated EMS and test
the replication system. Refer to Monitoring Replication System section in
this appendix.
Deactivating EMS Replication

Deactivate EMS replication to cancel the replication state of specified
ZXONM E300 EMS. After being deactivated, the EMS will not participate in
data replication of the replication system.
In the REPLICATION SYSTEM MAINTENANCE window, select
Deactivate EMS replication to enter the SELECT EMS window, as
shown in Figure 62
FIGURE 62 SELECT EMS WINDOW (DEACTIVATE EMS)
Sequence No. 1 to N: List all the EMSs, e.g.1,2. After an EMS is

selected, the EMS replication will be deactivated.
Exit: Exit this window, and return to last level.
After EMS replication is deactivated successfully, enter the REPLICATION

SYSTEM MONITOR window to check the status of deactivated EMS and
test the replication system. Refer to Monitoring Replication System section
in this appendix.
Manually Replicating Data

Manual data replication replicates the data of an EMS to other EMSs
forcibly.
This operation is applicable to the replication system whose data are partly
inconsistent. The user can replicate all EMS database data or one NEs
data.
In the REPLICATION SYSTEM MAINTENANCE window, select
Replicate data to enter the REPLICATE DATA window, as shown in
Figure 63.
103
FIGURE 63 REPLICATE DAT A WINDOW
Source: Display the source EMS. It indicates that data is to be

replicated from this EMS to other EMSs. The user can select Select
Source EMS to choose the source EMS.
1. Select source EMS: Select this item to enter the EMS SELECTION
window and select source EMS.
2. Replicate whole database

Replication modes include no transaction mode and transaction mode.
no transaction mode: The replication process is not handled as a

transaction. If replication fails during the process, it may cause
data errors of other EMSs while the process can continue until
replication succeeds.
transaction mode: The replication process is handled as a

transaction. In this mode, the operation result will be returned as
succeeded or failed. If replication fails during the process, data of
other EMSs are not affected. However, replication in this mode is
very slow and needs large buffer. If the buffer is full, the replication
system cannot work normally. The buffer space can be checked in
the REPLICATION SYSTEM MONITOR window.
Caution: Be careful with this function. After replication, the user must wait
for a while and then restart all EMSs.
104
3. Replicate NE: Replicate data of one NE. After selecting this item,
enter the SELECT NE window, as shown in Figure 64. All the names
and IDs of NEs are listed in this window. Select the serial number of
the NE to replicate its data.
FIGURE 64 REPLICATE NE D AT A WINDOW
Using isql Tool

In the REPLICATION SYSTEM MAINTENANCE window, select Use isql
Tool. If the connection is successful, the window appears as shown in
Figure 65.
FIGURE 65 SUCCESSFUL ISQL TOOL CONNECTION WINDOW
After the ISQL tool is connected to the replication server, the user can
control the replication server through command lines. It is usually used for
advanced functions and is not described here.
Monitoring Replication System

The REPLICATION SYSTEM MONITOR window displays the statuses of
replication system. The user can control replication directions, and test the
replication system in this window. The statuses of replication system
include:
Replication server status: Whether the server is started and whether

the server is normal.
Status of disk partition of the replication server: Display the total space,
current used space, and current free space.
EMS replication status: Displays each EMS name, status of database

server, replication status, IN and OUT replication directions, and invalid
replication directions.
105

Replication system monitor to enter the REPLICATION SYSTEM
MONITOR window, as shown in Figure 66.
FIGURE 66 REPLICATION SYSTEM MONITOR WINDOW
Window Description
RepServer Status: Status of

SUSPECT, HEALTHY, and DOWN.
the
server,
including
SUSPECT: The replication system cannot work normally, which is

generally caused by abnormal IN or OUT replication directions of
some EMSs.
DOWN: Replication server is not started. If the replication server is

installed on remote host, check if the IP address of Primary EMS is
correct and if the replication server communicates host of Primary
EMS normally.
HEALTHY: The replication system is normal.
RepServer Partition: Buffer usage status of the replication server

(unit is M). Size indicates the total size, Used indicates the used space,
and Free indicates the free space. If Free is zero, the replication
system is faulty. In this case, the user needs to extend the buffer
space.
Database Status: Statuses of all replication databases.
EMS: Name of EMS and database server.
DStatus: Display the running status of EMS database server,

including DOWN (stopped) and UP (started). If the status is DOWN,
check whether the EMS is started and whether the communication
from the local to EMS is normal.
RStatus: It is the replication status of EMS, including ACTIVE,

ACTIVATE, DEACTIVATE, and INACTIVE.
ACTIVE: Replication is activated.
106
replication
ACTIVATE: The system fails to activate EMS replication or the

activation is interrupted during activation process. In this case, the
user needs to activate EMS replication again.
DEACTIVATE: The system fails to deactivate EMS replication or
the deactivation is interrupted during deactivation process. In this
case, the user needs to deactivate EMS replication again.
INACTIVE: EMS replication is not activated, and the EMS cannot
participate in the replication.
OUT: Status of OUT replication direction of database, including

DOWN (stopped), UP (started), and -.
If the status is DOWN, the database data cannot be replicated to
other EMS databases. Select Resume or suspend replicate
direction to control the status of OUT replication direction.
If the status is UP, the database is running normally.
If the status is -, the EMS is INACTIVE.
IN: Status of IN replication direction of database, including DOWN

(stopped), UP (started), and -.
If the status is DOWN, the database data of other EMSs cannot be
replicated to this EMS databases. Select Resume or suspend
replicate direction to control the status of IN replication direction.
If the status is UP, the database is running normally.
If the status is -, the EMS is INACTIVE.
FailingReplicationFrom: Display replication test result.

If the test is normal or there is no data replication from other EMSs,
the system displays None.
If the test result is abnormal, the system displays the source EMS
names of invalid replication directions, indicating that it is
impossible to replicate data from these EMSs to this EMS. In Figure
66, the replications from HP12 to PC71, from HP12/PC71 to SUN16,
and from SUN16 to HP12 are all invalid.
If the IN and OUT directions are normal and invalid directions still
exist after several tests, deactivate the source EMS and then
activate it.
1. Resume or suspend replicate direction: Restore or suspend the

IN and OUT replication directions of the EMS.
2. Test replication system: Test the replication system and display

the result in the FailingReplicationFrom column.
Suspending/Restoring Replication Direction

This operation is used to suspend or restore the IN and OUT replication
directions of specified EMS.
107
In the REPLICATION SYSTEM MONITOR window, select Resume or

suspend replicate direction to enter the RESUME OR SUSPEND
REPLICATION DIRECTION window, as shown in Figure 67.
FIGURE 67 RESUME OR SUSPEND REPLIC ATION DIRECTION WINDOW
Selected: Display the name of target EMS. The subsequent five

operations are used to control replication of the selected EMS.
1. Select EMS: Select this item to enter the EMS SELECTION window
and select the EMS.
2. Resume OUT Direction: Resume the OUT replication direction of

EMS.
3. Suspend OUT Direction: Suspend the OUT replication direction of

EMS.
4. Resume IN Direction: Resume the IN replication direction of EMS.
5. Suspend IN Direction: Suspend the IN replication direction of

EMS.
Testing Replication System

In the REPLICATION SYSTEM MONITOR window, select Test
replication system to modify certain internal data of each EMS database
without affecting EMS data, and then check whether the modification is
replicated to other EMSs. If failure occurs, the FailingReplicationFrom
column of the window will display the failure information.
The replication system test generally lasts for a few minutes. If any failure
occurs, test the replication system again to prevent slow replication in
some special cases.
108
Appendix
Abbreviations
Abbreviations
Full Name
A
AIS
Alarm Indication Signal
ANSI
American National Standards Institute
C
Corba
Common object request broker architecture
CWDM
Coarse Wavelength Division Multiplexing
D
DCC
Data Communications Channel
DCN
Data Communication Network
DDN
Digital Data Network
DWDM
Dense Wavelength Division Multiplexing
E
ECC
Embedded Control Channel
EMF
Equipment Management Function
EML
Network Element Management Layer
EMS
Network Element Management System
ETSI
European Telecommunication Standards Institute
G
GNE
Gateway Network Element
GUI
Graphical User Interface
I
IP
Internet Protocol
ITU-T
International Telecommunication UnionTelecommunication Standardization Sector
L
LAN
Local Area Network
LCT
Local Craft Terminal
109
Abbreviations
Full Name
NCP
Net Control Processor
NE
Network Element
NEL
Network Element Layer
NMF
Network Management Forum
NMS
Network Management System
O
OAM
Operation, Administration, and Maintenance
OSF
Operating System Function
OSI
Open System Interconnect
P
PDH
Plesiochronous Digital Hierarchy
S
SDH
Synchronous Digital Hierarchy
SMCC
Sub-network Management Control Center
SML
Service Management Layer
SMN
SDH Management Network
SMS
SDH Management Sub-network
STM-N
Synchronous Transport Module, level N (N=1, 4, 16, 64)
T
TMN
Telecommunications Management Network
110
WAN
Wide Area Network
WDM
Wavelength Division Multiplexing
Figures
Figure 1 Installation Flowchart of ZXONM E300...............................................25
Figure 2 Network Example...........................................................................26
Figure 3 Searching for Device Name of CD ROM .............................................30
Figure 4 DBMAN Main Interface in Unix .........................................................32
Figure 5 BACKUP AND RESTORE Interface of DBMAN in Unix ............................32
Figure 6 BACKUP DATABASE Interface of DBMAN in Unix .................................33
Figure 7 RESTORE DATABASE Interface of DBMAN in Unix (1) ..........................35
Figure 8 RESTORE DATABASE Interface of DBMAN in Unix (2) ..........................35
Figure 9 DBMAN Main Interface in Windows ...................................................37
Figure 10 mgrcfg.ini File .............................................................................41
Figure 11 SQL Server Client Network Utility Dialog Box....................................43
Figure 12 Edit Network Library Configuration Dialog Box ..................................43
Figure 13 Edit Network Library Configuration Dialog Box (Modify Network Library)
........................................................................................................44
Figure 14 hosts File (under the /etc/ directory)...............................................51
Figure 15 hostname.eri0 File (under the /etc/ directory) ..................................51
Figure 16 netmasks File (under the /etc/ directory).........................................51
Figure 17 defaultrouter File (under the /etc/ directory) ....................................52
Figure 18 addroute.sh File (under the /etc/ directory) .....................................52
Figure 19 Setup Error Alert Box....................................................................53
Figure 20 SQL_Server Error Allert Box...........................................................54
Figure 21 DATABASE MANAGEMENT Window ..................................................55
Figure 22 port list ......................................................................................62
Figure 23 Advanced Page of System Properties Dialog Box ...............................64
Figure 24 Environment Variables Dialog Box ..................................................64
Figure 25 New System Variable Dialog Box ....................................................65
Figure 26 Environment Variables Dialog Box with ZTETSHASCLEAR Added..........65
Figure 27 DATASERVER MANAGEMENT Window ..............................................70
Figure 28 Main Window of dsedit Tool ...........................................................72
Figure 29 DATABASE MONITOR Window ........................................................74
Figure 30 Deleting Database ........................................................................76
Figure 31 EXTEND DATABASE Window ..........................................................76
Figure 32 CREATE DEVICE Window ...............................................................77
Figure 33 BACKUP AND RESTORE Window .....................................................78
Figure 34 BACKUP DATABASE Window ..........................................................79
Figure 35 RESTORE DATABASE Window ........................................................81
Figure 36 MERGE ANOTHER EMSS DATA Window ...........................................82
Figure 37 Backup NE TS Window ..................................................................82
Figure 38 Restore NE TS Window..................................................................83
Figure 39 Backup NE Style Window...............................................................84
Figure 40 Restore NE Style Window ..............................................................84
Figure 41 Check ZXSM TS Window................................................................85
Figure 42 Chang Ne Software Version Window................................................86
Figure 43 Change Ne Software Version Window with Selected All Nes Disabled....87
Figure 44 SELECT NE Window ......................................................................87
Figure 45 Chang Ne Software Version window (Change Software of the Selected NE)
........................................................................................................88
Figure 46 Chang old NeId to New NeId Window ..............................................88
Figure 47 V3.16 BACKUP FILE UPDATE TO V3.17 Window ................................89
111
Figure 48 ANALYSE AND PROCESS NETWORK DATA Window ............................90

Figure 49 REPLICATION SYSTEM MANAGEMENT Window ..................................91
Figure 50 REPLICATION SERVER INSTALLATION Window .................................92
Figure 51 REPLICATION SYSTEM CONFIGURATION Window ..............................93
Figure 52 SELECT LOCAL EMS Window ..........................................................95
Figure 53 CONFIGURE EMS Window ..............................................................95
Figure 54 EMS INFORMATION Window ..........................................................96
Figure 55 SELECT SOURCE EMS Window .......................................................96
Figure 56 CONFIGURE DIRECTIONS Window ..................................................97
Figure 57 CONFIG REPLICATION DATA Window ..............................................98
Figure 58 BACKUP AND RESTORE REPLICATION SYSTEM CONFIGURATION Window
........................................................................................................98
Figure 59 REPLICATION SYSTEM MAINTENANCE Window ............................... 100
Figure 60 EXTEND REPLICATION SERVER DISK Window................................. 102
Figure 61 SELECT EMS Window (Activate EMS Replication)............................. 102
Figure 62 SELECT EMS Window (Deactivate EMS) ......................................... 103
Figure 63 REPLICATE DATA Window............................................................ 104
Figure 64 REPLICATE NE DATA Window ....................................................... 105
Figure 65 Successful isql Tool Connection Window ........................................ 105
Figure 66 REPLICATION SYSTEM MONITOR Window ...................................... 106
Figure 67 RESUME OR SUSPEND REPLICATION DIRECTION Window ................ 108
112
Tables
T A B L E 1 T Y P O G R A P H I C A L C O N V E N T I O N S ........................................................iii
Table 2 Mouse Operation Conventions ............................................................iii
Table 3 Safety Signs....................................................................................iv
Table 4 Hardware Requirements Based on Unix Platform..................................13
Table 5 Software Requirements Based on Unix Platform...................................14
Table 6 Minimum Hardware Requirements Based on Windows ..........................14
Table 7 Minimum Requirements for Host Configuration (Windows Platform) ........15
Table 8 Software Requirements Based on Windows .........................................15
Table 9 Kernel Parameter Configurations of HP-UX Operating System ................17
Table 10 Patches to be Installed...................................................................19
Table 11 Commonly Used Environment Variables of ZXONM E300 .....................63
Table 12 Descriptions of DBMAN Main Window ...............................................68
Table 13 Descriptions of DATASERVER MANAGEMENT Window ..........................71
Table 14 Descriptions of DATABASE MANAGEMENT Window..............................73
Table 15 Descriptions of DATABASE MONITOR Window ....................................74
Table 16 Descriptions of EXTEND DATABASE Window ......................................76
Table 17 Descriptions of CREATE DEVICE window ...........................................78
Table 18 Descriptions of BACKUP AND RESTORE Window .................................79
Table 19 Descriptions of BACKUP DATABASE Window ......................................79
Table 20 Descriptions of RESTORE DATABASE Window ....................................81
Table 21 Descriptions of MERGE ANOTHER EMSS DATA Window .......................82
Table 22 Descriptions of Backup NE TS Window ..............................................82
Table 23 Descriptions of Restore NE TS Window .............................................83
Table 24 Descriptions of Backup NE Style Window ..........................................84
Table 25 Descriptions of Restore NE Style Window ..........................................84
Table 26 Descriptions of Check ZXSM TS Window ...........................................85
Table 27 Descriptions of Chang Ne Software Version Window ...........................86
Table 28 Descriptions of Chang old NeId to new NeId Window ..........................88
Table 29-Descriptions of V3.16 BACKUPFILE UPDATE TO V3.17 window .............89
Table 30-Descriptions of ANALYSE AND PROCESS Network Data .......................90
113

Sjzl20090609-Unitrans ZXONM E300 (V3.19R2) Maintenance Manual - 516854

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Sjzl20090609-Unitrans ZXONM E300 (V3.19R2) Maintenance Manual - 516854

Diunggah oleh

Hak Cipta:

Format Tersedia

ZXONM E300

Unified EMS/SNMS of Optical Network

Jun. 18, 2007

Upgrade parts of the operating

May. 30, 2009

Upgrade parts of the operating

ZXONM E300 (V3.19R2) Unified EMS/SNMS of Optical Network Maintenance

Equipment Installation Date

Improve the overview/introduction

Make it more concise/brief

Improve the Contents

Add more step-by-step

Improve the organization

Add more troubleshooting information

Include more figures

Make it less technical

Add more examples

Add more/better quick reference aids

Add more detail

Improve the index

This page is intentionally blank.

Management Rules for EMS.....................................................................................1

Checking EMS Connection .......................................................................................4

Monitoring Topology ...............................................................................................5

Inspection Criteria ...................................................................................................................5

Monitoring Performance ..........................................................................................6

Querying System Configuration ...............................................................................7

Querying User Operation Log...................................................................................8

Printing Report .......................................................................................................8

Saving/Printing Alarm/Performance Messages...........................................................9

Backing up Data ................................................................................................... 10

Restoring Data ..................................................................................................... 11

Installation and Configuration of Unix ..................................................................... 16

Installation and Configuration of Windows............................................................... 22

Upgrading ZXONM E300........................................................................................ 28

Setting EMS Parameters in Windows ...................................................................... 41

Setting EMS Parameters in Unix............................................................................. 44

EMS Connection Fault ........................................................................................... 57

Database Fault ..................................................................................................... 59

Database Server Management Operations .............................................................. 70

Database Management Operations......................................................................... 73

Backing Up and Restoring Data.............................................................................. 78

Checking Timeslot ................................................................................................ 85

Changing Software Version of Selected NE .............................................................................87

Appendix B ................................................................................. 109

About this Manual

Prerequisite Skill and Knowledge

System and various components of transmission equipment of ZTE

User interfaces of the ZXONM E300

Basic operations of the ZXONM E300

What is in this Manual

Chapter 1 Maintenance Overview

Describes the classification of ZXONM E300 maintenance

Chapter 2 Routine Maintenance

Describes the routine maintenance operations on ZXONM

Describes the requirements for ZXONM E300 running

Confidential and Proprietary Information of ZTE CORPORATION

ZXONM E300 (V3.19R2) Maintenance Manual

environment, the installation and configuration of Windows

Chapter 4 EMS Installation and

Describes the installation procedure, upgrade procedure,

Chapter 5 Maintenance of EMS

Describes how to maintain the EMS and how to set