Professional Documents
Culture Documents
Unitrans ZXONM E300 V3 17 Installation Manual PDF
Unitrans ZXONM E300 V3 17 Installation Manual PDF
Installation Manual
Version 3.17
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900
800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
Copyright 2005 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE
CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality
obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are
disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or
non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance
on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the
subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its
licensee, the user of this document shall not acquire any license to the subject matter herein.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support
or training are subject to change without notice.
Revision History
Date
Revision No.
Serial No.
Description
2006/06/29
R1.0
sjzl20060790
First 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
V3.17
R1.0
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
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
Contents
About this Installation Manual .................................................................ix
About the Manual Suite .......................................................................................... ix
Purpose of this Installation Manual ........................................................................... x
Typographical Conventions..................................................................................... xi
Mouse Operation Conventions................................................................................. xi
Safety Signs..........................................................................................................xii
How to Get in Touch .............................................................................................xiii
Customer Support.................................................................................................................xiii
Documentation Support.........................................................................................................xiii
Chapter
1................................................................................... 17
Chapter
2................................................................................... 31
Installation Overview.............................................................................. 31
Installation Items ................................................................................................. 31
Running Environment Requirements of ZXONM E300 .............................................. 32
Unix Platform ........................................................................................................................32
Chapter
3................................................................................... 37
Chapter
4................................................................................... 45
Chapter
5................................................................................... 57
Chapter
6................................................................................... 73
Appendix
A ................................................................................ 77
Introduction to Unix................................................................................ 77
Overview of Unix .................................................................................................. 77
Introduction ..........................................................................................................................77
Composition..........................................................................................................................78
System Initialization ..............................................................................................................78
Directory Structure................................................................................................................79
Common Terms ....................................................................................................................80
Common Operations............................................................................................. 82
Command Line Format ..........................................................................................................82
Introduction to Interface Buttons ...........................................................................................82
Special Key Command...........................................................................................................83
Appendix
B ................................................................................ 91
NCP Upgrade........................................................................................................ 94
NCP Status............................................................................................................................94
Preparations..........................................................................................................................95
Local Data Initialization..........................................................................................................95
Appendix
C ..............................................................................105
Appendix
D .............................................................................113
Figures........................................................................................115
Tables .........................................................................................117
SDH equipment: ZXMP S390, ZXMP S380, ZXMP S360, ZXMP S320,
ZXMP S330, ZXMP S385, ZXMP S100, ZXMP S200, ZXMP S325
PCM equipment: ZXMP P210, ZXMP P220, ZXMP P230, ZXMP P240
2. Manual suite
Manual Name
Function
It
describes
the
installation
and
configuration of the ZXONM E300 LCT
(Local Craft/maintenance Terminal).
ix
Typographical Conventions
ZTE documents employ the following typographical conventions.
Typeface
Meaning
Italics
Quotes
Links on screens.
Bold
CAPS
Constant width
Text that you type, program code, files and directory names,
and function names.
[]
Optional parameters
{}
Mandatory parameters
Typeface
Meaning
Click
Double-click
Right-click
Drag
xi
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.
xii
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.
xiii
xiv
Chapter
Overview of NMS
In this chapter, you will learn about:
ZXONM E100
ZXONM E100 is an NE-layer management system based on Windows.
It manages SDH equipment including ZXSM-150, ZXSM-600,
ZXSM-150S, ZXMP S310, ZXMP S360, and ZXMP S320.
ZXONM E300
ZXONM E300 is a unified NE and subnet management system
(EMS/SNMS) of optical network based on Windows 2000 and Unix. It
manages SDH equipment, DWDM equipment, and CWDM equipment.
The ZXONM E300 (V3.17) can manage the following equipment:
SDH equipment: ZXMP S390, ZXMP S380, ZXMP S360, ZXMP S320,
ZXMP S330, ZXMP S385, ZXMP S100, ZXMP S200, ZXMP S325
PCM equipment: ZXMP P210, ZXMP P220, ZXMP P230, ZXMP P240
17
ZXONM E400
Service-layer
management system
SMS
ZXONM N100
Network-layer
management syst em
NMS
NMS
ZXONM E100/
E300/E400
NE-layer
management
s ystem
EMS
EMS
ZXONM E 100
ZXONM E300
NE
NE
NE
NE
NE
18
NE
NE
Software Structure
The ZXONM E300 system adopts a four-layer structure, including the
equipment layer, NE layer, NE management layer, and subnet
management layer. It can also provide the Corba interface for the network
management layer which manages the regions of its scope.
Figure 2 shows the software structure of ZXONM E300, where the network
management layer does not belong to ZXONM E300.
19
The core of the NE layer is Agent. Each Agent can be managed by one or
more Managers. However, only one Manager has the authority to write. An
Agent has function of automatic routing and can transmit EMS information
based on ECC.
NE layer (NE/Agent)
It manages one single NE only. During initialization of a NE after
power-on, it configures each board. While in the NE normal running
status, it is responsible for monitoring alarms and performance of the
NE, as well as receiving and processing monitoring commands of the
network element management layer or Manager through the gateway
NE (GNE).
The NE control processor (NCP) implements the functions of the NE
layer. Upon powered on and initialized, an NCP can work independently
without the Manager or NE management system. It can save
configuration data but does not have the functions of the man-machine
interface layer and NE management layer.
20
System Composition
The ZXONM E300 EMS consists of GUI, Manager, Database, and Agent.
Figure 3 shows the relations among these parts.
GUI
Manager
Database
Agent
21
Manager
It is also called as Server. For the GUI, the Manager plays the role of a
Server. It sends management commands to the corresponding Agent
and receives various notifications sent from the Agent. In addition, it
stores all the network management data in the database such as the
basic data of system management, configuration management, and
alarm maintenance. However, the Manager stores network
management data of its own domain only.
GUI
It is also called Client. Basically, the GUI does not store dynamic data
of network management, and the data are obtained from the database
through the Manager.
Database
It queries information of interfaces and management modules, stores
configuration and alarm information, and synchronizes data.
NE Agent
The Agent, located in the NE layer, manages related management
objectives directly, responds to commands sent from the Manager, and
sends notifications reflecting objective behavior to the corresponding
Manager.
Component
Software Hierarchy
GUI
Manager/Database
Agent
The GUI, Manager, and Database can be installed on the same computer
or on different computers. The system supports the Unix platform and
Windows platform. The configuration requirements of computers vary with
software packages. The Database can adopt the SYBASE database or SQL
Server database. The functions of Agent are implemented through the NCP;
and the functions of the equipment layer are implemented in MCUs in
various boards.
22
Networking Modes
Single GUI and Single Manager
Figure 4 shows the networking of a single GUI and a single Manager,
which is the most common mode. The GUI and Manager may run on the
same computer or on different computers, depending on the number of
devices under management and the process capability of the computer.
GUI-1
Manager
Subnet1
Subnet2
...
Subnetn
23
GUI-1
GUI-2
...
Higher-level
NMS
Manager
Subnet1
Subnet2
GUI-m
...
Subnetn
Switching Conditions
The vice EMS takes over the work of the main EMS in the following cases:
24
Main EMS
Gateway NE
DDN/X.25
NE
Vice EMS
NE
Gateway NE
Note: Only the SYBASE database supports this database synchronization mode.
Authority Switchover
The main and vice EMSs are actually a special case of multiple EMSs. The
vice EMSs authority can be upgraded from read only to read and write.
Authority change of the vice EMS must comply with authority switchover
principles. Correct switchover can be ensured through information
transferred between the main and vice EMSs and the current EMS status
reported on the NCP, and thus avoiding wrong switching between main
and vice EMSs.
Authority switchover principles of main/vice EMSs are as follows:
The system supports one main EMS and multiple vice EMSs. Normally,
the main EMS has the authority to read and write, and the vice EMS is
authorized to read only. In the case of exception, the vice EMSs
authority can be upgraded from read only to read and write. The
authorities of the main and vice EMSs can be modified manually.
25
The authorities of main and vice EMSs are assigned for a specific NE.
Remote EMS
In the networking modes mentioned above, a case can be called as
remote network management when a router or a bridge is required
between a GUI and a Manager, between Managers (main and vice EMSs),
or between a Manager and an Agent, which locate at different places.
Therefore, remote EMS is the implementation of the above networking
modes in the case of remote access through router or bridge.
Subnet Management
Subnet management is a special case of remote NM. For its networking
mode, refer to the NMS structure shown in Figure 2. NE management
systems are distributed in different areas, whereas the subnet
management system is installed in the management center. Through
remote access, the subnet management system manages lower-level NE
management systems, and achieves the goal of subnet management in
multiple regions.
ZXONM
E300
adopts
the
structure, and has powerful
NE management ability
The ZXONM E300 EMS software does not limit the number of NEs
under management. Therefore, the management ability of EMS
depends on the processing capability of hardware. Workstation or
server in different classes can be configured based on network
scales. And multiple EMSs can be configured based on management
regions.
Select hardware environment flexibly based on network scales.
An NE group or subnet is a logic concept and can be set randomly.
26
High flexibility
The EMS adopts a distributed structure has is highly flexible. GUI,
Manager and Database can operate on the same computer or on
several different computers. In addition, a Manager may consist of
several child managers, and the child managers can be configured
flexibly based on network scale and equipment composition. Child
managers can be added or deleted dynamically.
i.
The GUI layer controls users operation authority and NEs managed
or monitored by user.
Trans-platform solution
The EMS supports Windows 2000 and Unix operating systems, thus
satisfying demands of various users at different levels.
27
Compliant Standards
Standards and ITU-T recommendations followed by the ZXONM E300 are
listed in Table 5.
28
Standard/
Recommendation
Description
ITU-T M.3100
ITU-T M.3020
ITU-T M.3200
ITU-T M.3400
ITU-T X.200
ITU-T X.710
ITU-T X.711
ITU-T X.208
ITU-T X.209
ITU-T X.720
ITU-T X.721
ITU-T X.722
ITU-T M.3100
ITU-T Q.821
ITU-T Q.822
ITU-T X.730
ITU-T X.731
ITU-T X.733
ITU-T X.734
ITU-T X.735
ITU-T G.774
ITU-T G.774.01
Standard/
Recommendation
Description
ITU-T G.774.02
ITU-T G.774.03
ITU-T G.774.04
NMF 040
ASN.1/C++ Application
November 1997
Programming
Interface,
Issue
1.0,
NMF 041
CMIS/C++ Application
November 1997
Programming
Interface,
Issue
1.0,
NMF 042-1
NMF 042-2
NMF 042-3
NMF 043
Interface,
Part
1:
29
30
Chapter
Installation Overview
In this chapter, you will learn about:
Installation procedures
Installation Items
The ZXONM E300 installation software consists of two service programs
and three application programs.
31
Application Program
Service Program
GUI
ILOG
Manager
DBSVR
Note: The SQL Server database is only applicable to the ZXONM E300 based on Windows. If
the SQL Server database is used, Manager and DBSVR must be installed in a same computer.
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 7 describes the hardware requirements based on Unix platform.
Hardware Item
Host
Requirement
HP B2600
Workstation
HP C8000
Workstation
Mini computer
Mini computer
Workstation
Workstation
32
Software Requirements
Table 8 describes the software environment based on Unix.
Software Item
Operating system
Requirement
HP-UX 11.00
HP workstation/mini-computer
SUN workstation
Database
SYBASE
Available space of
hard disk
No less than 9 G
Windows Platform
Hardware Requirements
Table 9 describes the minimum hardware requirements based on
Windows.
Hardware Item
Requirement
Host
Memory
512 MB
Hard disk
20 GB
Monitor
17 inches
Resolution
1024768
Color
Caution: The GUI on Windows platform does not support the color mode of 256.
33
NE Quantity
CPU
Hard Disk
Memory
Less than 30
PIII 877
20 G
256 M
30 to100
P4 1G
30 G
512 M
100 to 300
P4 2G
60 G
1G
300 to 500
P4 2.5G
80 G
2G
Software Requirements
Table 11 describes the software requirements based on Windows.
Software Item
Requirement
Operating system
Database
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.
Installation Flow
Figure 7 shows the installation procedure of the ZXONM E300.
Prepare for
ZXONM E300
installat ion
Complet e
installation
Inst all
ZXONM E300
Configure the
parameters
Separate
installation
Confirm
installation
components
Install
corresponding
c omponents
Configure the
parameters
34
The ZXONM E300 EMS can be installed on Unix or Windows platform based
on networking requirements. Refer to Chapter 3 for installation and
configuration of the operating systems.
Refer to Chapter 4 for ZXONM E300 installation based on Unix, and refer
to Chapter 5 for ZXONM E300 installation based on Windows.
35
36
Chapter
Installation
1.
2.
Configuration
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.
37
ii. Log in to the single user as the user ROOT and execute the
following command under the root directory prompt to load all file
systems.
#mount -a
Note: It is necessary to expand the logical volume which corresponds to the file
system before expanding the file system. Therefore, execute the command b d f to
search the logical volume that corresponds to the directory / t m p .
//Expand 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 .
38
#mount /dev/vg00/lvol4/tmp
Parameter
Value
maxdsiz_64bit
3 Gbit
maxssiz_64bit
maxtsiz_64bit
1 Gbit
maxdsiz
3 Gbit
maxssiz
maxtsiz
1 Gbit
shmmax
2 Gbit
maxfiles
nfile
shmseg
maxuprc
nproc
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.
39
Patch Installation
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 o s _ p a t c h / 8 _ R e c o m m e n d e d . z i p of the installation CD.
HP-UX Platform
For HP-UX 11.00, make sure to install QPK1100 in the HP-UX Support
Plus CD attached with the HP-UX. The installation commands are as
follows:
# mount /dev/dsk/c0t0d0/cdrom
# swinstall -s /cdrom/QPK1100
40
Patch Name
Function
Remarks
PHNE_23876
PHNE_24100
GUI
PHSS_23803
GUI
PHSS_23823
GUI
Patch Name
Function
Remarks
PHSS_23800
PHSS_22217
GUI
Install from the ZXONM E300 installation CD. The patches are in
the patch directory o s _ p a t c h of the CD, with file suffix as tar.
Extract the .tar file first before installation. The operations are as
follows:
i.
ii. Execute the following commands to install the patches. Take the
patch PHNE_24100 as an example. Other patches are installed
according to this operation.
# cd /tmp/patch
# sh PHNE_24100
# swinstall -s /tmp/patch/PHNE_24100.depot
41
/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
42
Select sam -> Actions -> Add Driver to Kernel to create 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
/dev/async
sybase
sybase
101
0x000004
Oct
28
10:32
# /usr/bin/chown
sybase:sybase /dev/async
# /usr/bin/chmod 660
/dev/async
Caution: The ZXONM which uses SYBASE as its database must be installed on
Windows 2000 Server, and Windows XP is not supported.
43
44
Chapter
Installation Procedure
The ZXONM E300 can run on the HP-UNIX platform or Solaris platform.
The following content describes how to install the ZXONM E300.
Installation Preparations
1. Select the ZXONM E300 installation CD for the HP-UNIX or Solaris
platform according to the actual operating platform. Table 14 lists
directories in the installation CDs.
Operating
System
HP-UX
Solaris
45
Directory
Description
doc
tools
os_patch
install
doc
tools
os_patch
install
Typical Installation
If typical installation is selected, all the components of ZXONM E300 will
be installed.
After installation, the following sub-directories are generated automatically:
d b , d b m a n , d o c , g u i , i l o g , j a v a , m a n a g e r , r e p o r t , s e r v e r and
s y b a s e . The sub-directories are described in Table 15.
Sub-directory
Description
db
Save the executable program, log files, configuration files, and backup
data of the database server (DBSVR).
dbman
Saves the items related to the database maintenance tool (dbman), such
as dbman executable program and logs.
doc
gui
ilog
Saves the graphical interface development tools for ZXONM E300 Client.
java
manager
Saves the startup programs, logs, and configuration files of the parent
manager and various child managers.
report
server
Saves the startup programs of the ZXONM E300 Server and the Report
Server.
sybase
Solaris platform
i.
46
HP-UX platform
i.
Log in to the system as a ROOT user, and insert the ZXONM E300
installation CD into the CD-ROM drive.
ii. Execute the following command to query the CD-ROM device name.
# ioscan -fnkC disk
Class
I
H/W
Description
Path
Driver
S/W
State
H/W
Type
============================================
disk
0 10/0/14/0.0.0
CD-ROM LTN485S
sdisk
CLAIMED
/dev/dsk/c0t0d0
disk
1 10/0/15/1.6.0
MAJ3182MC
sdisk
CLAIMED
/dev/dsk/c3t6d0
DEVICE
LITEON
/dev/rdsk/c0t0d0
DEVICE
FUJITSU
/dev/rdsk/c3t6d0
iv. Execute the following command to mount the CD-ROM into the
system.
# mount /dev/dsk/c0t0d0 /cdrom
47
The left list box of the dialog box lists the EMS installation sequence. A
mark in front of each installation step shows installation progress.
When the mark becomes a blue round icon, it indicates that this step is
completed or installation is underway. When the mark becomes a black
block, it indicates that this step is not started yet.
48
6. In the dialog box shown in Figure 11, select I accept the terms of
the License Agreement. Click Next button. The Choose Install
Folder dialog box pops up, as shown in Figure 12.
Checkpoint: For initial installation, make sure that the space of the installation
directory is no less than 4 GB.
49
50
10. After data copy is completed, three prompt boxes including change
file mode, start SYBASE, and create database, will pop up in
sequence, as shown in Figure 16, Figure 17, and Figure 18.
51
11. After the above three processes are completed successfully, the
Install Complete dialog box pops up, as shown in Figure 19.
52
Solaris platform
The Solaris
operations.
platform
supports
two
types
of
CD-ROM
ejection
Note: The Install Complete dialog box shown in Figure 19 supports another
installation completion operation: click Done to reboot the system automatically.
And after the system reboots successfully, take out the installation CD.
Custom Installation
Custom installation is used when only part of the EMS components need to
be installed on the computer.
53
2. Click Custom to enter the Select Component dialog box, which lists
all the installation components of ZXONM E300.
3. Select components to be installed in the Select Component dialog
box based on actual conditions and the dependencies between
installation components listed in Table 6.
4. For subsequent operations, refer to the section of Typical Installation.
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.
54
//Parent Manager OID. Only the last digit can be changed. and the
configuration of OID must be consistent with that of Manager.
mgrOid=iso:org:dod:internet:private:enterprise:zte:manag
er:8
......
55
......
56
Chapter
Installation Procedure
Installation Preparations
1. Based on database type, select ZXONM E300 installation CD of SYBASE
or SQL Server. Table 16 lists directories and files in the installation CD.
Directory
SYBASE
SQL
Server
Description
doc
tools
os_patch
install
Sn.txt
doc
tools
os_patch
install
Sn.txt
57
Typical Installation
Typical installation, also called complete installation, integrates database
software, such as SYBASE or SQL Server, and EMS software. About 2.7 GB
will be occupied on the hard disk for this type of installation.
After installation, the following sub-directories listed in Table 17 are
generated automatically.
Sub-directory
Description
db
Saves the running program, log files, configuration files and backup data
of the database server (DBSVR).
dbman
Saves the items related to the database maintenance tool (dbman), such
as dbman program and logs.
doc
gui
Saves the items related to Client software, such as program, logs, and
configuration files.
ilog
java
Saves the realtime running environment for JAVA, to support the report
running
manager
Saves the startup programs, logs and configuration files of the parent
manager and various managers.
report
server
Saves the startup programs of ZXONM E300 server (Server) and the
report server (Report Server).
Saves files related to SYBASE.
sybase
sqlserver
The installation procedure of the ZXONM E300 based on SYBASE and that
based on SQL Server are quite similar.
58
Note: The ZXONM E300 EMS provides English and Chinese versions for Windows
operating system. This chapter takes the English version as an example to
illustrate the installation procedure.
3. Select English and click OK. The InstallShield Wizard dialog box
pops up, as shown in Figure 21.
59
60
Note: Get the serial number from the S n . t x t file in ZXONM E300 installation CD.
7. Enter the user name, company name, and the serial number; and then
click Next. The Choose Destination Location dialog box pops up, as
shown in Figure 25.
61
62
10. Click Next. The Setup Type dialog box will pop up, as shown in Figure
28.
typical,
custom,
and
client
11. Taking the ZXONM E300 installation using SYBASE as example, in the
Setup Type dialog box, select Typical, click Next to enter the Select
Device Type dialog box, as shown in Figure 29.
63
The Select Device Type dialog box lists the NE types that can be
managed by ZXONM E300. The relations between child managers and
NE types are listed in Table 18.
NE Type
Child Manager
Remarks
smgr10G (320)
ZXMP S360
smgr2500
ZXMP S320
smgr600
ZXMP S330
smgr2500C
ZXMP S100
smgrt150
ZXMP S385
smgr2510
ZXMP S200
smgrs200
ZXMP S325
smgrs325
smgrV3
2 M monitoring system
smgr100mV3
ZXWM M900
smgrV2
2 M monitoring system
smgr100mV2
ZXWM-32 (V1)
smgrV1
ZXMP M600
smgrcwdm
smgrpcm
SDH virtual NE
Note: By default, all child managers will be installed for the ZXONM E300, that is,
the ZXONM E300 can manage all NE types. User can select the child manager
based on current network requirements.
64
12. In the Select Device Type dialog box, click Next to enter the Select
Program Folder dialog box, as shown in Figure 30.
13. In the Select Program Folder dialog box, the default folder is
ZXONM_E300, and user can select another folder according to actual
need. Click Next and the Installing dialog box pops up, as shown in
Figure 31.
14. After copying the files, the InstallShield Wizard Complete dialog
box pops up.
15. Click Finish to finish the installation, and the system restart selection
dialog box pops up, as shown in Figure 32.
65
16. In Figure 32, select Yes, I want to restart my computer now. and
click Finish, to complete the ZXONM E300 installation and the
computer will be restarted right now. Or select No, I will restart my
computer later. and click Finish, to complete the ZXONM E300
installation and manually restart the computer later.
Compact Installation
Compact installation is applicable only to the ZXONM E300 that is
supported by the SQL Server database. The compact installation
integrates the installation programs of SQL Server database software and
the ZXONM EMS software. It is the minimum installation of ZXONM E300.
Custom Installation
Custom installation is used when only parts of components need to be
installed. The hard disk space required depends on components to be
installed.
66
Client Installation
The client installation only installs ZXONM E300 EMS client and report
server, and about 300 MB of hard disk space is needed.
67
68
For example:
//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
configuration of OID must be consistent with that of Manager.
mgrOid=iso:org:dod:internet:private:enterprise:zte:
manager:8
......
......
69
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 35.
70
71
72
Chapter
73
FI G U R E 3 8 AD D / R EM O V E PRO G R AM S D I AL O G B O X
74
Caution: In Unix, all the files in the ZXONM E300 installation folder u n i t r a n s will
be cleared during ZXONM E300 uninstallation. Therefore, the EMS data shouldnt
be saved in the u n i t r a n s folder. Also, for Windows, it is recommended not to
save the EMS data in the installation folder.
75
i.
Use the ZXONM of new version to clear the NCP database of the
NE.
Other NEs:
i.
76
Appendix
Introduction to Unix
This appendix briefly introduces basic concepts of Unix operating system,
common operations, and commands. For details, refer to the related
documents about Unix.
Overview of Unix
This section describes basic concepts of Unix, including system
introduction,
composition,
initialization,
directory
structure,
and
explanations of common terms.
Introduction
Unix is a multi-user, multi-task, and time-sharing operating system.
Multi-user
The Unix operating system allows multiple users to operate at the
same time. In Unix, each user runs his own or public programs, like an
independent computer. The disk operating system (DOS) is a
single-user operating system, and only allows one user to use it.
Multi-task
Unix allows multiple tasks to run at the same time. In earlier versions,
the multi-task function of Unix is implemented through time sharing
mechanism. Now, in addition to time sharing, Unix has the function of
real-time multi-task for real-time control and data collection.
Time-sharing
Time of the host CPU is divided into many slices to respond to different
users. Since these time slices are very small and the processing speed
of the CPU is very high, the users using them hardly feel the existence
of other users, and it seems that the whole system is occupied by one
user.
77
Composition
The Unix operating system consists of kernel, shell, tool, and applications.
Kernel is the core part of the Unix operating system. It instructs the
Unix machine to run and controls resources of computers directly,
protecting user programs from interferences caused by complicated
hardware.
Tools and applications are provided for users. They include applications,
utilities, and other system software except the Unix operating system.
System Initialization
Compared with DOS, Unix deals with multiple users. Therefore, it cannot
directly boot the command program during initialization.
78
Turn on DOS
terminal
Boot kernel
Boot kernel
Invoke init
Command
getty
login
login
shell
shell
Directory Structure
Figure 40 shows the directory structure of Unix operating system.
bin
lib
usr
smith
prog
dev
etc
sybase
install
The directory structure of Unix is similar to that of DOS, but the file path is
written differently. The full name of a file path consists of all nodes
between the root directory and the file, among them, the root directory is
represented by /, and names are separated by /. For example, the
path of the p r o g file in Figure 40 is / u s r / s m i t h / p r o g . The full name of a
79
file path for the DOS starts from a drive letter, and names are separated
by \, for example, c : \ t m p \ d a t a \ f o x .
Table 19 lists common directories of the root file.
Directory
Description
/bin
/dev
/etc
/lib
C program database
/usr
/tmp
Common Terms
Terminal:
A terminal is an interface that is used by users to communicate
with computers. Generally, a terminal consists of a monitor, a
keyboard, a terminal controller, and a mouse. The monitor and
keyboard are connected to the terminal controller. The controller is
connected to the host computer through a general port such as a
serial port. A terminal falls into two types: character terminal and
diagram terminal.
Terminal line:
A terminal line is the communication line connecting a user and the
Unix host. A serial port cable or network cable is often used as a
terminal line.
Terminal protocol:
Terminal protocols are used for communication between users and
the Unix host.
Emulation terminal
Run a specified program in a computer and use this computer as the
terminal of anther computer. At present, an emulation terminal
connects to the Unix host through the network or serial port.
80
Console
A console is a special terminal. It consists of a monitor, a keyboard and
a mouse, which are connected to dedicated interfaces of the host, that
is, monitor interface, keyboard interface and mouse interface.
Usually, a host can connect to one console only. A console can
implement the functions of common terminals. In addition, a console
can also implement the function that a common terminal cannot, for
example, to display severe error information and recover from errors.
User
Unix is a multi-user operating system, allowing multiple users to use it
at the same time. Each user has a user name, login password and
operation authority. Every time when a user log in to the Unix system,
he must enter the user name and password.
There are two types of users in Unix:
Super user: Root user. The system prompt for this type of user is
#. The Unix system does not restrict any operation performed by
a super user in the system. It is very important to keep password
of super user password secret.
Group
A group of users. Users in the same group can share information.
Process
A process is a program that is being executed. Unix allows multiple
processes to exist at the same time. Each process has a unique
number, called process ID, which is pid.
Foreground process
The process through which user can interact with computer directly.
The foreground process support keyboard input and displays the result
in the monitor. By default, Unix programs started by users run in the
foreground.
Background process
The process through which user cannot interact with computer directly.
Normally, users cannot feel running of background programs.
Device
Also known as device file. It represents one piece of hardware such as
disk, floppy disk, and serial port. It is used by Unix to access hardware.
Device files are located under the directory / d e v . For example,
/ d e v / h d 0 indicates the first floppy disk drive.
Raw device
Also known as naked device. It is a device file that had not been
processed. The name of a raw device file starts with r. For example,
/ d e v / r h d 0 indicates the raw device of the first floppy disk drive.
81
Common Operations
The Unix system supports three types of common operation: command
line, graphical interface and special keys. The follow introduces these
types of common operation.
Command prompt
In the command line format, the operating system displays a prompt
to instruct users to enter a line of command after the prompt.
For common users, shells have different prompts. The prompt of B
Shell and K Shell is $, and that of C Shell is %.
The prompt for the super user is # by default.
Users can modify the default Shell and prompts.
Note: The command format of Unix is similar to that of DOS except that Unix
commands are case sensitive, and commands and parameters must be separated.
Classification of commands
Common system commands are classified based on the following:
82
: Click this button, a dialog box or menu of the Unix pops up.
Double-click this button to shut down the dialogue box or window.
Keys
Description
CTRL + d
DEL
CTRL + s
CTRL + q
CTRL + u
Kill key, to delete all the characters in the line where the cursor is located.
ESC
83
Introduction to Common
Commands
This section introduces common commands in Unix.
Basic Commands
Table 21 lists basic Unix commands.
Command
Description
Parameters
- a : all files
- I : Node No.
ls
- l : Details
- a c : Parse
- F : Format
- R : Recursion
84
mkdir
To create a sub-directory.
rmdir
To delete a sub-directory.
mv file file2
rm
To delete a file
cd
pwd
man + command
name
Help
chmod
chown
tty
cat
cp
Copy files
ln
Link
find
Find a file
grep
wc
Technology
ps
- f : Overwrite existing
without a prompt.
file
Command
Description
Parameters
kill
Terminate a process
nohup
who
User
vi
Text editor
df
Disk space
mkfs
mount
dd
Back up
telnet
hostname
Telnet
shutdown g0
date
Date
exit
Log out
cal
Calendar
sleep
Delay
Command
Description
passwd
Change password
su
admintool
useradd
Add a user
userdel
Delete a user
userls
Note: Only the root user and authorized users can add, modify, or delete users.
85
ps
kill
exit
nohup
This command line indicates that after the current user exits, the
system continues to execute the command f i n d in the background to
find the file a b c in the current directory and its sub-directories.
Network Commands
Network commands reflect high-speed communication connections
between users and the Unix host. Through the network, you can transfer
86
ftp
Common f t p commands
Table 23 lists common ftp commands.
ftp Command
? [command]
or h e l p [command]
Description
Command help
Binary
Ascii
cd [directory]
Pwd
dir
[r-dir]
[l-file]
ls
[r-dir]
[l-file]
lcd [directory]
put
[file2]
file1
get
[fine2]
file1
mput files
mget files
Status
!command
open IP address
or domain name
Re-establish a connection.
Close
q u i t or b y e
To exit ftp
87
rcp
rlgoin
telnet
ping
Storage Devices
User may use the floppy disk drive, tape drive, or CD-ROM drive when
operating the ZXONM E300. This section introduces these three types of
storage devices.
88
CD-ROM Drive
For the Solaris platform, the CD-ROM is automatically loaded to the
system when it is used. The following describes how to use CD-ROM drive
in the HP-UX platform.
1. Find the name of CD-ROM drive
# ioscan -fnkC disk
Class
I
H/W
Description
Path
Driver
S/W
State
H/W
Type
============================================
disk
0 10/0/14/0.0.0
CD-ROM LTN485S
sdisk
CLAIMED
/dev/dsk/c0t0d0
disk
1 10/0/15/1.6.0
MAJ3182MC
sdisk
CLAIMED
/dev/dsk/c3t6d0
DEVICE
LITEON
/dev/rdsk/c0t0d0
DEVICE
FUJITSU
/dev/rdsk/c3t6d0
3. Execute the following command to mount the CD-ROM into the system.
# mount /dev/dsk/c0t0d0 /cdrom
89
90
Appendix
Software Versions
Relationship between Software Versions
of ZXMP S380/S390 and ZXONM E300
The software versions of ZXMP S380 and ZXMP S390 include V3.1 and
V3.2. Table 24 lists the relationship between software versions of ZXMP
S380/S390 and ZXONM E300.
Software
Version of ZXMP
S380/S390
Version Description
V3.1
V3.2
Corresponding
Sub-manager
Support from
ZXONM E300
smgr10g
The
ZXONM
E300 of versions
earlier
than
V3.15 supports
V3.1 only.
smgr10g_320
ZXONM E300 of
V3.16R1
and
later
versions
support V3.2.
91
Caution: For ZXMP S389/S390, after the ZXONM E300 and NCP program are
upgraded successfully, it is necessary to clear the database of NE through the
ZXONM E300 of new version and then re-download the NE data.
Querying Version
Query software versions of ZXMP S380/S390 equipment in the NE
Property dialog box.
92
FI G U R E 4 3 AD V AN C E D D I AL O G B O X
Note: The software version is 3.1 or 3.2 which respectively corresponds to V3.1
and V3.2. In the Advanced dialog box, software version can only be queried. To
modify the software version, refer to the section of Converting Version from V3.1
to V3.2.
Upgrade Relation
For ZXMP S380/S390 NE, if the EMS is upgraded, it is necessary to
upgrade the NCP meanwhile according to the NE software version and
future function requirements. The flowchart is shown in Figure 44.
93
V3.1
No
V3.2
No
Upgrade the NCP
Yes
Run the DBMAN program
to convert the software
version from V3.1 to V3.2
End
NCP Upgrade
NCP Status
The states of NCP include DOWNLOAD and Running, which are determined
by the DIP switch (identified as S2) on NCP board. Table 25 illustrates the
status of NCP board.
94
NCP Status
Function
DIP Switch
DOWNLOAD
All ON
Running
Preparations
1. Make sure that the EMS can ping through the NE of which the NCP
program is to be upgraded. To perform online upgrade, record the IP
address of the NE.
2. Make sure that the version of downloaded NCP program and the EMS
version are consistent.
1. Unplug the NCP board. Set the DIP switch to DOWNLOAD state
according to the description in the section of NCP Status. And the NE
IP address is then obliged to 192.192.192.11.
2. Make sure that a proper electronic disk is plugged on the NCP.
3. In the portable PC, configure an IP address within the same network
section as the NE IP address, e.g. 192.192.192.250. Use a crossover
network cable to connect the Qx interface on NCP board with the
network interface on the portable PC. Make sure that the portable PC
can ping through 192.192.192.11.
4. If it is not the first time to use the electronic disk, go to step 5.
Otherwise, follow the following steps to format the electronic disk:
i. Execute the t e l n e t
computer.
192.192.192.11
ii. The system prompts to enter the user name and password. Leave
the user name and password empty and directly press ENTER.
iii. Type the following command to format the electronic disk under the
prompt N C P > :
NCP>format
NCP>exit
192.192.192.11
ii. The system prompts to enter the user name and password. Leave
the user name and password empty and directly press ENTER.
95
Software
Version
Settings of Command
V3.2
Only the MAC address needs to be set, and its format is: 00:D0:D0:xx:xx:xx.
The MAC address of each NCP board in a network should be unique.
//Upload the NCP program to the flash disk. This procedure takes
about three to four minutes. r a m . b i n is the file name of NCP
program in the computer.
FTP> bye
96
Line No.
Content
V3.1 Example
V3.2 Example
192.1.1.18
192.1.1.18
Subnet mask
255.255.255.0
255.255.255.0
NE ID
NE
rate
(1=STM-1,
3=STM-16, 4=STM-64)
2=STM-4,
NE type (1=TM,
5=ADM®)
3=REG,
2=ADM,
Caution: When the NCP starts running normally, this file allows no random
modification. If it is necessary to modify the file, delete the original database in
the NCP before modification. For how to clear the NCP database.
97
8. Unplug the NCP board. Set the DIP switch to Running state according
to the description in the section of NCP Status. Once the NCP board is
reset and works normally, this NE has the newly configured IP address
and application.
9. Change the IP address of the portable PC to be within the same
network section as the new NE IP address. Execute the p i n g N E _ I P
command to make sure that the portable PC can ping through
192.192.192.11.
10. Clear the original NCP database
For the ZXMP S380 and ZXMP S390 equipment, the NCP database can
be cleared through the EMS or command lines.
NE of V3.1
ZTE+>deldb
//Exit telnet.
Note: If the NCP board does not reboot automatically, execute the r e b o o t
command to forcibly reboot the NCP.
NE of V3.2
ZTE+>rm rf DbSys
//Exit telnet.
98
11. In the ZXONM E300 client operation window, make sure that the NE
status is online, and download the NCP database.
Caution: Make sure that the NE data are configured before downloading the NCP
database.
12. The NCP board will automatically reset. In the EMS client operation
window, right-click the NE and select the Time Management menu
item to extract the NCP time. If time can be extracted successfully, it
indicates that the NE initialization is completed.
Online Upgrade
The online download is the procedure that the operator downloads new
version of NCP program to the NE through ECC channel. It is generally
applied when the EMS is upgraded.
Suppose the NE IP address is 188.92.3.18. The online upgrade procedure
of NCP board is as follows:
1. Execute the p i n g 1 8 8 . 9 2 . 3 . 1 8 command on the EMS to make sure
that the NE can be pinged through.
2. Execute the f t p 1 8 8 . 9 2 . 3 . 1 8 command and connect the EMS to the
NCP board. Enter z t e for the username and e c c for the password.
Caution: The username and password must be lowercases.
This process takes about three to four minutes. Only when this operation ends,
can the next operation be conducted. If failure or error occurs, it is necessary to
repeat this operation until the download succeeds.
99
4. In the EMS client operation window, select this NE and select the
System > NCP Data Management > Clear NCP DB menu to clear
the NCP database on line. Then the NCP will be reset.
Caution: If there is no special requirement, the operator must clear NCP database
in order to remake NCP data. After clearing NCP database, there is no NE data in
the NCP. Therefore the NE power-off or ECC block during NCP running may cause
service interruption. However, as long as the ECC is smooth, the NCP can be
upgraded online.
100
Selected Ne: All Nes in E300 database: Displays the NEs whose
versions are to be converted. For the first time to enter Figure 46, all
NEs are selected by default.
1. Select the Single Ne: Selects the designated NE.
2. Select All Nes : yes: Selects all ZXMP S380/S390 NEs. yes
indicates to select all NEs for version conversion.
3. From 3.1 to 3.2: Modify the version of the selected NE from V3.1
to V3.2.
4. From 3.2 to 3.1: Modify the version of the selected NE from V3.2
to V3.1.
5. Help: Shows the help information.
101
102
iii. Type the serial No. in front of the NE name to return to the
Change Ne Software Version interface. Suppose that the version
of the ZXMP S380 is to be modified, type 2 , and then the name of
the selected NE is displayed after Selected NE :, as shown in
Figure 49.
iv. Type 3 .
v. If the version conversion succeeds, reboot the ZXONM E300 Server
as prompted by the system.
103
104
Appendix
Installation FAQ
This chapter provides solutions to installation problems that may occur on
different platforms.
ii. After the system is powered off, it saves the information which was
in the buffer into l o s t + f o u n d folder under the operation directory.
This information is not released after the system reboots. Execute
the command b d f to measure 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 / v a r / p r e s e r v e . This information is not
released after the system reboots.
iv. Sudden power-off makes temporary files under the directory
/ v a r / t m p not released.
Solution:
i. Delete the files in the folders: / t m p , / o p t / l o s t + f o u n d , / v a r / t m p ,
and / v a r / p r e s e r v e .
ii. Delete the EMS installation directory, and re-install the EMS.
105
2. When creating logical volume, the disk space is insufficient. Why does
this happen?
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.
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
avail
Mounted on
8258
94%
47722
37%
/stand
213865
99682
3788
2043
72000
%used
59652
3000000
93%
/home
81%
/var
99%
/usr
3%
3%
/tmp
/opt
106
#mount *
#cp r opt /home/
#lvremove /dev/vg00/lvol6
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.
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.
107
Run s a m .
ii. Select
Display,
X
Server
VISUALIZE-FXE in sequence.
Configuration,
and
HP
127.0.0.1 localhost
193.1.2.7 zte
Zte
netstate-r
to
query
the
routing
the
network
card
name
in
the
file
/etc/hostname.interface.
108
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.
109
Possible causes:
The installation directory does not have enough free space.
Solution:
i.
110
Possible causes:
i.
The SQL Server database is not installed in the computer where the
ZXONM E300 is installed.
Install the SQL Server database in the computer where the ZXONM
E300 is installed.
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.
ii. Reboot the server and GUI of the ZXONM E300. If the GUI still
prompts database connection failure, perform step iii.
iii. Start the file d b m a n . b a t in the installation directory / d b m a n to
enter the main interface of the dbman, as shown in Figure 52.
111
112
Appendix
Abbreviations
Abbreviations
Full Name
A
AIS
ANSI
C
Corba
CWDM
D
DCC
DCN
DDN
DWDM
E
ECC
EMF
EML
EMS
ETSI
G
GNE
GUI
I
IP
Internet Protocol
ITU-T
L
LAN
LCT
113
Abbreviations
Full Name
N
NCP
NE
Network Element
NEL
NMF
NMS
O
OAM
OSF
OSI
P
PDH
S
SDH
SMCC
SML
SMN
SMS
STM-N
T
TMN
114
WAN
WDM
Figures
Figure 1 Positions and Relationship of ZXONM NMS Series................................18
Figure 2 Software Structure of ZXONM E300 EMS ...........................................19
Figure 3 Structure of NE Management Layer ..................................................21
Figure 4 Networking of Single GUI and Single Manager ....................................23
Figure 5 Networking of Multiple GUIs and Single Manager ................................24
Figure 6 Connection between Main and Vice EMSs...........................................25
Figure 7 Installation Procedure of ZXONM E300 ..............................................34
Figure 8 File Manager Window......................................................................47
Figure 9 Self-extract Interface .....................................................................48
Figure 10 Installation Introduction Dialog Box ................................................48
Figure 11 License Agreement Dialog Box .......................................................49
Figure 12 Choose Install Folder Dialog Box ....................................................49
Figure 13 Choose Install Set Dialog Box ........................................................50
Figure 14 Pre-Installation Summary Dialog Box ..............................................50
Figure 15 Installing Unitrans ZXONM E300 Window .........................................51
Figure 16 Change File Mode Prompt Box ........................................................51
Figure 17 Start SYBASE Prompt Box .............................................................52
Figure 18 Create Database Prompt Box .........................................................52
Figure 19 Install Complete Dialog Box ...........................................................53
Figure 20 Choose Setup Language Dialog Box ................................................59
Figure 21 InstallShield Wizard Dialog Box ......................................................59
Figure 22 Initial Window of Installation..........................................................60
Figure 23 License Agreement Dialog Box .......................................................60
Figure 24 Customer Information Dialog Box ...................................................61
Figure 25 Choose Destination Location Dialog Box ..........................................61
Figure 26 Choose Folder Dialog Box ..............................................................62
Figure 27 Choose Destination Location Dialog Box ..........................................62
Figure 28 Setup Type Dialog Box..................................................................63
Figure 29 Select Device Type Dialog Box .......................................................63
Figure 30 Select Program Folder Dialog Box ...................................................65
Figure 31 Installing Dialog Box.....................................................................65
Figure 32 System Restart Selection Dialog Box...............................................66
Figure 33 Select Components Dialog Box .......................................................67
Figure 34 mgrcfg.ini File Window..................................................................68
Figure 35 SQL Server Client Network Utility Dialog Box....................................70
Figure 36 Edit Network Library Configuration Dialog Box ..................................70
Figure 37 Edit Network Library Configuration Dialog Box (Modify Network Library)
........................................................................................................71
Figure 38 Add/Remove Programs Dialog Box..................................................74
Figure 39 Initialization Base on Unix and That Based on DOS ...........................79
Figure 40 Unix File Directory Structure ..........................................................79
Figure 41 Unix Graphic Interface ..................................................................83
Figure 42 NE Property Dialog Box .................................................................92
Figure 43 Advanced Dialog Box ....................................................................93
Figure 44 Relationship between ZXMP S380/S390 Upgrade and EMS upgrade .....94
Figure 45 dbman Interface ........................................................................ 101
Figure 46 Change NE Software Version Interface .......................................... 101
Figure 47 Change Ne Software Version Interface (Selecting All NEs is not Allowed)
...................................................................................................... 102
115
116
Tables
Table 1 Typographical Conventions ................................................................xi
Table 2 Mouse Operation Conventions ............................................................xi
Table 3 Safety Signs................................................................................... xii
Table 4 Relationship between ZXONM E300 Components and Software Hierarchy 22
Table 5 Compliant Standards and Recommendations .......................................28
Table 6 Dependences between Service Programs and Application Programs ........31
Table 7 Hardware Requirements Based on Unix Platform..................................32
Table 8 Software Requirements Based on Unix ...............................................33
Table 9 Minimum Hardware Requirements Based on Windows ..........................33
Table 10 Requirements for Host Configuration (Windows Platform)....................34
Table 11 Software Requirements Based on Windows .......................................34
Table 12 Kernel Parameter Configurations of HP-UX Operating System ..............39
Table 13 Patches to be Installed...................................................................40
Table 14 Directories in Installation CDs .........................................................45
Table 15 Sub-directory Description (Unix)......................................................46
Table 16 Directories and Files in the Installation CD ........................................57
Table 17 Sub-Directories Description (in Windows) .........................................58
Table 18 Relation between Child Manager and NE ...........................................64
Table 19 Common Directories of Root File......................................................80
Table 20 Special Key Commands ..................................................................83
Table 21 Basic Unix Commands....................................................................84
Table 22 User Operation Commands of Unix...................................................85
Table 23 Common ftp Commands .................................................................87
Table 24 Relationship between Software Versions of ZXMP S380/S390 and ZXONM
E300.................................................................................................91
Table 25 Status of NCP Board ......................................................................94
Table 26 Settings of setup Command ...........................................................96
Table 27 Format of the SDH.CFG File ............................................................97
117