unitrans zxonm e300(v3.17) installation manual

ZXONM E300Unified EMS/SNMS of Optical Network

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: [email protected]

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

ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network Installation Manual

Product Version V3.17 Document

Revision Number R1.0

Equipment Installation Date

Presentation: (Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization, Appearance)

Good Fair Average Poor Bad N/A

Accessibility: (Contents, Index, Headings, Numbering, Glossary)


Your evaluation of this documentation

Intelligibility: (Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Your suggestions for improvement of this documentation

Please check the suggestions which you feel can improve this documentation: Improve the overview/introduction Make it more concise/brief

Improve the Contents Add more step-by-step procedures/tutorials

Improve the organization Add more troubleshooting information

Include more figures Make it less technical

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 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

Overview of NMS..................................................................................... 17 Introduction to ZXONM NMS Products ....................................................................17

Classification of ZXONM NMS Products ...................................................................................17 Locations and Relationship of ZXONM NMSs in Transmission Network......................................18

Overview of ZXONM E300 .....................................................................................19 Software Structure................................................................................................................19 System Composition..............................................................................................................21

Networking Modes................................................................................................23 Single GUI and Single Manager..............................................................................................23 Multiple GUIs and Single Manager..........................................................................................23 Single Agent and Multiple Managers (Main/Vice EMS)..............................................................24 Remote EMS.........................................................................................................................26 Subnet Management .............................................................................................................26

ZXONM E300 Features..........................................................................................26 Compliant Standards ............................................................................................28

Chapter 2...................................................................................31

Installation Overview.............................................................................. 31 Installation Items .................................................................................................31 Running Environment Requirements of ZXONM E300 ..............................................32

Unix Platform........................................................................................................................32

Windows Platform .................................................................................................................33 Installation Flow ...................................................................................................34

Chapter 3...................................................................................37

Installation and Configuration of Operating System............................. 37 Installation and Configuration of Unix .....................................................................37

Installation............................................................................................................................37 Configuration ........................................................................................................................37 Patch Installation...................................................................................................................40 Database Configuration of HP-UX Platform .............................................................................41

Installation and Configuration of Windows...............................................................43

Chapter 4...................................................................................45

ZXONM E300 Installation in Unix ........................................................... 45

Installation Procedure ...........................................................................................45 Installation Preparations ........................................................................................................45 Typical Installation.................................................................................................................46 Custom Installation ...............................................................................................................53

Setting EMS Parameters........................................................................................54 Setting Dynamic Route..........................................................................................................54 Configuring Communication between GUI and Manager..........................................................54 Configuring Communication between DB and Manager ...........................................................55 Configuring Database Synchronization....................................................................................56

Chapter 5...................................................................................57

ZXONM E300 Installation in Windows ................................................... 57 Installation Procedure ...........................................................................................57

Installation Preparations ........................................................................................................57 Typical Installation.................................................................................................................58 Compact Installation..............................................................................................................66 Custom Installation ...............................................................................................................66 Client Installation...................................................................................................................67

Setting EMS Parameters........................................................................................68 Configuring Communication between GUI and Manager..........................................................68 Configuring Communication between DB and Manager ...........................................................68 Configuring Synchronization of SYBASE Database...................................................................69 Configuring SQL Server Database ..........................................................................................69

Chapter 6...................................................................................73

Uninstallation and Upgrade of ZXONM E300.......................................... 73

Uninstalling ZXONM E300......................................................................................73 Uninstalling ZXONM E300 in Windows ....................................................................................73 Uninstalling ZXONM E300 in Unix...........................................................................................74

Upgrading ZXONM E300........................................................................................75

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

Introduction to Common Commands......................................................................84 Basic Commands...................................................................................................................84 User Operation Commands....................................................................................................85 Process Management Commands...........................................................................................86 Network Commands..............................................................................................................86

Storage Devices ...................................................................................................88 Floppy Drive and Tape Drive..................................................................................................89 CD-ROM Drive.......................................................................................................................89

Appendix B................................................................................91

Upgrade of ZXMP S380/S390................................................................. 91 Software Versions.................................................................................................91

Relationship between Software Versions of ZXMP S380/S390 and ZXONM E300 ......................91 Querying Version...................................................................................................................92 Upgrade Relation...................................................................................................................93

NCP Upgrade........................................................................................................94 NCP Status............................................................................................................................94 Preparations..........................................................................................................................95 Local Data Initialization..........................................................................................................95

Online Upgrade .....................................................................................................................99 Converting Version from V3.1 to V3.2 .................................................................. 100

Appendix C..............................................................................105

Installation FAQ .................................................................................... 105 FAQ for Installation Based on HP-UX .................................................................... 105 FAQ for Installation Based on SUN ....................................................................... 108 Other Installation FAQ......................................................................................... 109

Appendix D .............................................................................113

Abbreviations ........................................................................................ 113

Figures........................................................................................115

Tables .........................................................................................117

Confidential and Proprietary Information of ZTE CORPORATION ix

About this Installation Manual

About the Manual Suite The Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network (ZXONM E300 in short) is a set of NE/subnet layer network management system based on Windows 2000 and Unix platforms. On the basis of guaranteeing hardware functions of transmission equipment, it manages and controls system NEs and regional networks, providing such functions as system management, configuration management, performance management, fault management, security management, and maintenance management.

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

SDH equipment: ZXMP S390, ZXMP S380, ZXMP S360, ZXMP S320, ZXMP S330, ZXMP S385, ZXMP S100, ZXMP S200, ZXMP S325

DWDM equipment: ZXWM-32 (V1.1), ZXWM M900, ZXMP M800

CWDM equipment: ZXMP M600

PCM equipment: ZXMP P210, ZXMP P220, ZXMP P230, ZXMP P240

2. Manual suite

Manual Name Function

Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network Installation Manual

It describes the basic knowledge and installation process of ZXONM E300.

Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network Interface Manual

It is an electrical manual, which describes the operations of ZXONM E300 client/ server interfaces.

Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network Operation Manual

It includes several volumes which describe the operations commonly used in the ZXONM E300 in details.

Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network LCT User’s Manual

It describes the installation and configuration of the ZXONM E300 LCT (Local Craft/maintenance Terminal).

Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network Maintenance Manual

It describes the maintenance knowledge of ZXONM E300.

ZXONM E300 (V3.17) Installation Manual

x Confidential and Proprietary Information of ZTE CORPORATION

Purpose of this Installation Manual This manual is Unitrans ZXONM E300 (V3.17) Unified EMS/SNMS of Optical Network Installation Manual. It provides basic information about how to install the ZXONM E300 (V3.17).

This manual includes six chapters and six appendixes:

Chapter 1 Overview of NMS, introduces the basic composition and features of the ZXONM E300 EMS.

Chapter 2 Installation Overview, introduces installation items, operation environment, and installation procedure of the ZXONM E300 EMS.

Chapter 3 Installation and Configuration of Operating System, describes the installation and configuration of Unix operating system and Windows operating system.

Chapter 4 ZXONM E300 Installation in Unix, describes the installation procedure of ZXONM E300 and setting of EMS parameters based on Unix.

Chapter 5 ZXONM E300 Installation in Windows, describes the installation procedure of ZXONM E300 and setting of EMS parameters based on Windows.

Chapter 6 Uninstallation and Upgrade of ZXONM E300, describes the uninstalling and upgrading of the ZXONM E300 based on Windows and Unix.

Appendix A Introduction to Unix, briefly describes common operations of Unix platform. For any question, refer to books of Unix fundamentals.

Appendix B Upgrade of ZXMP S380/S390, describes NCP program upgrade procedures and software version conversion operations of ZXMP S380/S390.

Appendix C Installation FAQ, gives solutions for possible problems raises during EMS installation.

Appendix D Abbreviations, gives some terms and abbreviations for user’s reference.


Confidential and Proprietary Information of ZTE CORPORATION xi

Typographical Conventions ZTE documents employ the following typographical conventions.

T AB L E 1 TY P O G R AP H I C AL C O N V E N T I O N S

Mouse Operation Conventions T AB L E 2 M O U S E OP E R AT I O N C O N V E N T I O N S

Typeface Meaning

Click Refers to clicking the primary mouse button (usually the left mouse button) once.

Double-click Refers to quickly clicking the primary mouse button (usually the left mouse button) twice.

Right-click Refers to clicking the secondary mouse button (usually the right mouse button) once.

Drag Refers to pressing and holding a mouse button and moving the mouse.

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.


xii Confidential and Proprietary Information of ZTE CORPORATION

Safety Signs T AB L E 3 S AF E T Y S I G N S

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.


Confidential and Proprietary Information of ZTE CORPORATION xiii

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 [email protected]. 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 [email protected]; 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.


xiv Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION 17

C h a p t e r 1

Overview of NMS

In this chapter, you will learn about: Introduction to ZXONM NMS product series

ZXONM E300 EMS software structure and system composition

Networking mode of ZXONM E300

ZXONM E300 features and the compliant standards

Introduction to ZXONM NMS Products Classification of ZXONM NMS Products ZXONM network management product series includes ZXONM NE-layer management products and ZXONM network-layer management products.

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

DWDM equipment: ZXWM-32 (V1.1), ZXWM M900, ZXMP M800

CWDM equipment: ZXMP M600

PCM equipment: ZXMP P210, ZXMP P220, ZXMP P230, ZXMP P240


18 Confidential and Proprietary Information of ZTE CORPORATION

ZXONM E400

ZXONM E400 is an NE-layer EMS based on Windows. It manages the ZXWM-32 (V1.1) equipment.

ZXONM N100

ZXONM N100 is a network-layer NMS based on Windows and Unix. It manages NE equipment by managing NE-layer EMS. It can provide other EMS with such interfaces as Corba and Q3.

Locations and Relationship of ZXONM NMSs in Transmission Network Figure 1 shows the locations of the ZXONM NMS series in transmission network and their relationship.

F I G U R E 1 P O S I T I O N S AN D R E L AT I O N S H I P O F ZXONM NMS S E R I E S

Network-layermanagement system

Service-layermanagement system

NMS

NE

NE

NE

NE

EMS EMS

NE

NE

NE

NMS

SMS

ZXONM N100

ZXONM E100 ZXONM E300

ZXONM E100/E300/E400

NE-layermanagementsystem

Chapter 1 - Overview of NMS


Overview of ZXONM E300 The Unitrans ZXONM E300 is a unified NE and subnet management system (EMS/SNMS) of optical network. It can manage NEs and also has some functions of network-layer management.

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.

F I G U R E 2 S O F T W AR E S T R U C T U R E O F ZXONM E300 EMS

In Figure 2, the core of the NE management Layer is the Manager (Server). The Manager can manage one or more subnets and it supports the access of multiple GUIs (Clients).



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.

Hierarchy of ZXONM E300 Subnet management layer

The structure of the subnet management layer is similar to that of the NE management layer. The configuration and maintenance commands for NEs are implemented through the NE management layer indirectly.

The subnet management system sends commands to the NE management system, which will then forward these commands to a NE. After executing the commands, the NE responds to the subnet management system through the NE management system. The subnet management layer can connect multiple NE management systems to achieve trans-domain management and automatically distribute commands to lower-layer EMS under management. In addition, it provides the Corba interface for the network management layer.

NE management layer (Manager)

It controls and coordinates a series of NEs, including Manager, GUI (graphical user interface), LCT (local craft terminal), and Database.

Manager: also known as Server. It is the core of the NE management layer. It manages multiple subnets at the same time, controls and coordinates NEs.

GUI: provides graphic user interfaces, converts the requirements of user management into the commands in internal formats, and sends them to Manager.

LCT: combines GUI and Manager simply by controlling user authorities and software functional parts; provides weakened NE management functions for commissioning and maintenance of local NEs.

Database: it is not shown Figure 2. It queries information of interfaces and management modules, stores configuration and alarm information, and synchronizes data.

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.



Equipment layer (MCU)

It is the real-time processing center of an EMS. The MCUs (micro control units), distributed in various boards, monitor alarms and performance of boards, receive commands from the EMS, and control boards to perform specific operations.

The MCU communicates with the Agent through the S interface. Upon powered on and initialized, the MCU can work independently without the Agent.

Interfaces of ZXONM E300 Figure 1 shows the locations of interfaces of the ZXONM E300 EMS. The following describes these interfaces:

Qx interface: Interface between Agent and Manager, complying with TCP/IP.

F interface: Interface between GUI and Manager, complying with TCP/IP.

f interface: Interface between Agent and LCT, complying with TCP/IP.

S interface: Interface between Agent and MCU. The S interface adopts the communication mechanism based on HDLC (high digital link control) to provide point-to-multipoint communication.

ECC interface: Interface between Agents. The ECC interface adopts DCC for communication. It can support user-defined communication protocols and standard protocols simultaneously. On Agent, it implements the function of bridge.

Corba interface: Interface between Manager and higher-level NMS.

System Composition The ZXONM E300 EMS consists of GUI, Manager, Database, and Agent. Figure 3 shows the relations among these parts.

F I G U R E 3 S T R U C T U R E O F NE M AN AG E M E N T L AY E R

GUI

Manager

Agent

Database



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.

To implement the ZXONM E300 software, the GUI, Manager, Database, and Agent must work together. Table 4 describes the relationship between software components and software hierarchy.

T AB L E 4 R E L AT I O N S H I P B E T W E E N ZXONM E300 C O M P O N E N T S AN D S O F T W AR E H I E R AR C H Y

Component Software Hierarchy

GUI GUI (NE/Subnet management layer)

Manager/Database Manager (NE/Subnet management layer)

Agent Agent (NE layer)

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.



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.

F I G U R E 4 N E T W O R K I N G O F S I N G L E GUI AN D S I N G L E MAN AG E R

GUI-1

Manager

Subnet1 Subnet2 Subnetn...

Multiple GUIs and Single Manager Multiple GUIs can log into one Manager at the same time, as shown in Figure 5. The higher-level NMS accesses the Manager in the same way as a GUI accesses the Manager. The Manager does not distinguish GUI and higher-level NMS. It ensures that the data of various GUIs are synchronous.

This networking mode is used when the user needs multiple operation terminals which may be distributed in various areas. Therefore, some of the GUIs need to log into the Manager remotely.



F I G U R E 5 N E T W O R K I N G O F M U L T I P L E GUI S AN D S I N G L E M AN AG E R

GUI-2

Manager

Subnet1 Subnet2 Subnetn...

GUI-1 GUI-m

Higher-levelNMS

...

Single Agent and Multiple Managers (Main/Vice EMS) The main EMS and the vice EMS serve for protection and backup of the EMS. Normally, when the main EMS is working normally, the vice EMS can be in the monitoring status only and cannot perform configuration.

Switching Conditions The vice EMS takes over the work of the main EMS in the following cases:

The transmission network is in abnormal status, and the main EMS cannot connect with NEs.

The main EMS is faulty.

Switching between the main/vice EMS is made manually.

Database Synchronization Modes The databases of the main EMS and the vice EMS must be consistent, that is, a synchronization mechanism must be established among all EMSs. The ZXONM E300 supports the following two database synchronization modes:

Database synchronization mode based on EMS DBMS

As shown in Figure 6, the databases of main EMS and vice EMS are connected through the Ethernet or DDN private line. Data is synchronized through the synchronization function of database.



F I G U R E 6 C O N N E C T I O N B E T W E E N M AI N A N D V I C E EMSS

Main EMS DDN/X.25 Vice EMS

Gateway NE NE NE Gateway NE

If the replication server of SYBASE is used as the component of data replication, the data can be synchronized at real time. Most of the synchronization tasks are completed by the database. Even if the DDN private line is interrupted, the replication application components can automatically ensure the consistency of data after the communication recovers. The advantage of this mode is simplicity and reliability. However, in the case of remote connection, DDN private line is required. Therefore, the cost is a relatively high.

Note: Only the SYBASE database supports this database synchronization mode.

Database synchronization mode based on Agent

An EMS uploads the newly modified data from the Agent. After the Agent receives an operation from a Manager and modifies data, it broadcasts the notification about modification to other Managers at real time. And other Managers will upload database automatically upon receiving the data, to ensure data consistency.

Authority Switchover The main and vice EMSs are actually a special case of multiple EMSs. The vice EMS’s 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 EMS’s authority can be upgraded from read only to “read and write”. The authorities of the main and vice EMSs can be modified manually.



The authorities of main and vice EMSs are assigned for a specific NE.

The vice EMS checks whether to change authority by receiving events reported by the NCP. If the main EMS and the vice EMS is connected via DDN, when the DDN private line is faulty, the operation authority of the vice EMS is upgraded; when the DDN private line recovers, the authority of the vice EMS is degraded.

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 Features Powerful management abilities

As shown in Figure 2, the ZXONM E300 adopts the GUI/Manager-DB/Agent three-level structure, and has powerful management abilities.

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.

Remote EMS and multi-GUI/multi-Manager system

The background EMS can provide remote EMS by means of multiple networking modes, and can manage ZTE transmission equipment in distributed areas through the transmission equipment of other manufacturers. The connection between GUI and Manager, and



between Manager and Agent can be managed through DDN remote connection. In this case, the multiple-EMS system can be achieved.

Main/Vice EMS and automatic switching between them

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.

Complete security mechanism

Three-level security mechanism

The EMS adopts three-level security mechanism. GUI, Manager, and Agent have their own security measures to achieve high security.

i. The GUI layer controls user’s operation authority and NEs managed or monitored by user.

ii. The Manager layer implements regional management. Each Manager has its own management region. Different managers may have partially or completely overlapped management regions.

iii. The Agent layer controls access of Managers, including LCT. Only valid Managers can access the Agent.

Multiple data synchronization modes

The system adopts backup and synchronization mechanism for databases to ensure security and data consistency.

For multiple GUIs or multiple Manager-DBs, lock mechanism and database synchronization can ensure consistency between multiple GUIs/Managers.

Supports database upload. The synchronization of data based on Agent covers synchronization of LCT modified data.

Trans-platform solution

The EMS supports Windows 2000 and Unix operating systems, thus satisfying demands of various users at different levels.

Dynamic routing function

Agent adopts the dynamic routing algorithm to establish communication between NEs. Manual intervention is unnecessary.

Standby route of EMS

The EMS can generate standby routes by accessing multiple gateway NEs (GNE) at the same time. For a chain system, when the ECC is blocked, the information of EMS can be transferred through the standby DCN network. In this case, management of NEs is not affected and the EMS becomes more reliable.



Remote online upgrade of NCP Software

Remote download through FTP and online upgrade of NCP software do not affect services. This provides convenience for system maintenance and upgrade, and ensures the reliability of system upgrade.

Compliant Standards Standards and ITU-T recommendations followed by the ZXONM E300 are listed in Table 5.

T AB L E 5 C O M P L I AN T S T AN D AR D S AN D R E C O M M E N D AT I O N S

Standard/ Recommendation Description

ITU-T M.3100 Principles for a Telecommunications Management Network

ITU-T M.3020 TMN Interface Specification Methodology

ITU-T M.3200 TMN Management Services: Overview

ITU-T M.3400 TMN Management Functions

ITU-T X.200 Reference Model for OSI

ITU-T X.710 Common Management Information Service

ITU-T X.711 Common Management Information Protocol

ITU-T X.208 Specification of Abstract Syntax Notation One (ASN.1)

ITU-T X.209 Specification of BER for ASN.1

ITU-T X.720 Information Technology-Open System Interconnection-Structure of Management Information: Management Information Model

ITU-T X.721 Information Technology-Open System Interconnection-Structure of Management Information: Definition of Management Information

ITU-T X.722 Information Technology-Open System Interconnection-Structure of Management Information: Guidelines for the Definition of Managed Objects

ITU-T M.3100 Generic Network Information Model

ITU-T Q.821 Stage 2 and Stage 3 Description for the Q3 Interface-Alarm Surveillance

ITU-T Q.822 Stage 1, Stage 2 and Stage 3 Description for the Q3 Interface 　Performance Management

ITU-T X.730 Object Management Function

ITU-T X.731 State Management Function

ITU-T X.733 Alarm Reporting Function

ITU-T X.734 Event Report Management Function

ITU-T X.735 Log Control Function

ITU-T G.774 SDH Management Information Model for the Network Element View

ITU-T G.774.01 SDH Performance Monitoring for the Network Element View



Standard/ Recommendation Description

ITU-T G.774.02 SDH Configuration of the Payload Structure for the Network Element View

ITU-T G.774.03 SDH Management of Multiplex-Section Protection for the Network Element View

ITU-T G.774.04 SDH Management of the Subnetwork Connection Protection for the Network Element View

NMF 040 ASN.1/C++ Application Programming Interface, Issue 1.0, November 1997

NMF 041 CMIS/C++ Application Programming Interface, Issue 1.0, November 1997

NMF 042-1 GDMO/C++ Application Programming Interface, Part 1: Architecture, Issue 1.0, December 1997

NMF 042-2 GDMO/C++ Application Programming Interface, Part 2: Class Reference, Issue 1.1, May 13, 1998

NMF 042-3 GDMO/C++ Application Programming Interface, Part 3: Specific Aspects, Issue 1.0, December 1997

NMF 043 TMN/C++ Application Programming Interface, Issue 1.0, December 1997


C h a p t e r 2

Installation Overview

In this chapter, you will learn about: ZXONM E300 Installation Items

Software and hardware environment

Installation procedures

Installation Items The ZXONM E300 installation software consists of two service programs and three application programs.

Service programs: software tool service programs used by EMS, including ILOG and SYBASE service programs.

Application programs: include GUI, NE Manager, and database driver which is DB Server (DBSVR).

Based on different networking requirements, the ZXONM E300 can adopt configurations of combined GUI/Manager/DBSVR, of separate GUI/Manager/DBSVR, or of multiple managers. For details, see the section of Networking Modes in Chapter 1.

When the application programs of ZXONM E300 are distributed in different terminals, dependences exist between application programs and service programs, as listed in Table 6. Therefore, it is necessary to install corresponding service programs when installing application programs, so as to implement specified EMS functions.

T AB L E 6 D E P E N D E N C E S B E T W E E N S E R V I C E P R O G R AM S AN D AP P L I C A T I O N P R O G R AM S

Application Program Service Program

GUI ILOG

Manager -

DBSVR SYBASE or SQL Server [Note]



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.

T AB L E 7 H AR D W AR E R E Q U I R E M E N T S B AS E D O N U N I X PL AT F O R M

Hardware Item Requirement

HP B2600 Workstation

HP C8000 Workstation

HP RP3410 (maximum: 2×CPU) Mini computer

HP RP3440 (maximum: 4×CPU) Mini computer

Sun Blade 150 Workstation

Host

Sun Blade 2500 Workstation

Tape drive (optional) 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 ≤ 20: recommend to use HP B2600, HP C8000, Sun Blade 150. The hard disk should be no less than 30 G, and memory should be no less than 1 G.

NE quantity ≥ 20: recommend to use HP RP3410, HP RP3440, Sun Blade 2500. The hard disk should be no less than 36 G, and memory should be no less than 3 G.

Chapter 2 - Installation Overview


Software Requirements Table 8 describes the software environment based on Unix.

T AB L E 8 S O F T W AR E R E Q U I R E M E N T S B AS E D O N U N I X

Software Item Requirement

HP-UX 11.00 HP workstation/mini-computer Operating system

Solaris 8 (SunOS 5.8) 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.

T AB L E 9 M I N I M U M H AR D W A R E R E Q U I R E M E N T S B AS E D O N W I N D O W S

Hardware Item Requirement

Host P III 800 (with network card and CDROM)

Memory 512 MB

Hard disk 20 GB

Monitor 17 inches

Resolution 1024×768

Color Enhanced color (16 bits)

LCT can be a portable computer with the following configurations: PIII 750/128 MB/10 GB/14.1 inch color monitor/24×CDROM/56 K Modem/100 M network card/floppy disk drive, 1024×768 resolution or above, enhanced color (16 bits) or above

Caution: The GUI on Windows platform does not support the color mode of 256.

Select host according to the quantity of NEs to be managed in the network, as listed in Table 10.



T AB L E 10 R E Q U I R E M E N T S F O R H O S T C O N F I G U R AT I O N (W I N D O W S P L AT F O R M )

Minimum Configuration of Host 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 1 G

300 to 500 P4 2.5G 80 G 2 G

Software Requirements Table 11 describes the software requirements based on Windows.

T AB L E 11 S O F T W AR E R E Q U I R E M E N T S B AS E D O N WI N D O W S

Software Item Requirement

Operating system Windows 2000 or above (the GUI, Manager, and Database should be installed on a 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.

Installation Flow Figure 7 shows the installation procedure of the ZXONM E300.

F I G U R E 7 IN S T AL L AT I O N P R O C E D U R E O F ZXONM E300

Install operatingsystem

Prepare forZXONM E300installat ion

InstallZXONM E300

Confirminstallation

components

Installcorrespondingcomponents

Configure theparameters

Completeinstallation

Separateinstallation

Configure theparameters

Chapter 2 - Installation Overview


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.


C h a p t e r 3

Installation and Configuration of Operating System

In this chapter, you will learn about: Installation requirements of Unix and Windows

Configuration requirements of ZXONM E300 for Unix and Windows

For details of installation steps of operating systems, refer to related manuals about operating systems.

Installation and Configuration of Unix This section describes installation requirements of the Unix operating system, and mandatory configurations before installing ZXONM E300.

Installation 1. Select proper host according to NE quantity. Refer to the section of

Unix Platform in Chapter 2.

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.

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.



Configuration of Solaris Platform 1. Execute the following commands to set the kernel parameters in the

file etc/system.

set shmsys:shminfo-shmmax=209715200

set shmsys:shminfo_shmmni=0x1000

shmsys:shminfo_shmseg=0x100

2. Execute the following commands to reboot the computer.

cd /

shutdown -ry 0

Configuration of HP-UX Platform 1. Use HP-UX 11.0 as the operating system and ensure the available

space of the directory /tmp is 1 GB.

If the space is less than 1 GB, follow the steps below to expand it.

i. Execute the following command to enter the single user mode.

#shutdown -y 0

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

iii. Execute the following command to check if the directory /tmp is loaded. If the directory is loaded successfully, record the logical volume name of the directory.

#bdf

Note: It is necessary to expand the logical volume which corresponds to the file system before expanding the file system. Therefore, execute the command bdf to search the logical volume that corresponds to the directory /tmp .

iv. Execute the following commands to expand the directory /tmp.

#umount /tmp //Unmount the directory /tmp. It is necessary to unmount it before changing the its size

#lvextend -L 1024 /dev/vg00/lvol4

//Expand the logical volume /dev/vg00/lvol4 that corresponds to the /tmp file system to 1 GB (1024 MB).

#extendfs /dev/vg00/lvol4

//Expand the logical volume. For the vxfs file system, execute the command extendfs -F vxfs /dev/vg00/lvol4.

Chapter 3 - Installation and Configuration of Operating System


#mount /dev/vg00/lvol4/tmp

//Mount the logical volume onto the directory /tmp.

2. Follow the steps below to adjust kernel parameters of the system and re-create HP-UX kernel.

i. Run the sam program as a ROOT user.

ii. Select Kernel configuration area in the sam menu.

iii. Set the kernel parameters as listed in Table 12.

T AB L E 12 K E R N E L P AR AM E T E R C O N F I G U R AT I O N S O F HP-UX OP E R AT I N G S Y S T E M

Parameter Value

maxdsiz_64bit 3 Gbit

maxssiz_64bit No less than 64 Mbit

maxtsiz_64bit 1 Gbit

maxdsiz 3 Gbit

maxssiz No less than 64 Mbit

maxtsiz 1 Gbit

shmmax 2 Gbit

maxfiles The recommended value is 256, indicating soft restriction on the number of files that can be opened by a process.

nfile The recommended value is 1210, indicating the maximum number of 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.

Pay attention to the meanings of 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 sam.

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.



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 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 install_cluster. 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 attached with the HP-UX. 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 in the year of 2000 in the HP-UX Support Plus CD. The installation commands are as follows:


# swinstall -s /cdrom/XSWGR1100 \

-xpatch_match_target=true \

-x autoreboot=true

# swinstall -s /cdrom/XSWHWCR1100 \

-xpatch_match_target=true \

-x autoreboot=true

Table 13 lists other patches to be installed.

T AB L E 13 P AT C H E S T O B E IN S T AL L E D

Patch Name Function Remarks

PHNE_23876 Used for database, mandatory -

PHNE_24100 GUI -

PHSS_23803 GUI -

PHSS_23823 GUI -



Patch Name Function Remarks

PHSS_23800 - Install this patch after installing the patches of PHNE_24100, PHSS_23803, and PHSS_23823

PHSS_22217 GUI -

The patches in Table 13 can be installed in the following two methods:

Download from the website of itrc.hp.com.

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. 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

Database Configuration of HP-UX Platform

Note: For a computer installed with SYBASE on HP-UX platform, make sure to create database storage devices and asynchronous devices for storage of data before installing patches.

Creating Database Storage Devices

To create database storage devices

1. Check the free space of the disk and confirm that it is no less than 1400 MB.

Login to the system as the ROOT user and execute the following command on the command line:

# 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 1

Act PV 1

Max PE per PV 2500

VGDA 2

PE Size (Mbytes) 4

Total PE 2168

Alloc PE 2133

Free PE 35

Total PVG 0

Total Spare PVs 0

Total Spare PVs in use 0

VG Name is the volume group name, for example, /dev/vg00. Free PE is the free space of the volume group in the unit of PE. PE Size (Mbytes) is the size of a PE in the unit of MB.

The free space of the volume group can be calculated as follows:

Free PE * FE Size (unit: MB)

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 sam as a ROOT user.



2. Select sam -> Kernel configuration to enter the Drivers area.

3. Select asyncdsk and then re-create HP-UX kernel.

i. 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

5. Log in to the system as a 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---- 1 sybase sybase 101 0x000004 Oct 28 10:32 /dev/async

If /dev/async does not exist or the device number is incorrect, delete the device and create it as follows:

# /sbin/mknod /dev/async c 101 0x4

6. Assign 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

Installation and Configuration of Windows For hardware requirements for the computer installed with Windows operating system, refer to Table 9. Select host according to the quantity of NEs to be managed in the network, as listed in Table 10.

If the version of the operating system is later than Windows 2000, install the operating system according to related manuals of the software.

Caution: The ZXONM 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 in to the operating system as the super user (Administrator) to install and operate the ZXONM E300 EMS in the future.


C h a p t e r 4

ZXONM E300 Installation in Unix

In this chapter, you will learn about: ZXONM E300 installation procedure in Unix platform

Setting parameters of ZXONM E300 in Unix platform

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.

T AB L E 14 D I R E C T O R I E S I N IN S T AL L AT I O N CD S

Operating System

Directory Description

doc Saves manuals and operation documents

tools Saves tools, for example, DBMAN

os_patch Patch program directory of the HP-UX operating system HP-UX

install EMS installation directory

doc Saves manuals and operation documents

tools Saves tools, for example, DBMAN

os_patch Patch program directory of the Solaris operating system Solaris




2. Determine installation items based on networking conditions and dependencies between various parts listed in Table 6.

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: db, dbman, doc, gui, ilog, java, manager, report, server and sybase. The sub-directories are described in Table 15.

T AB L E 15 S U B -D I R E C T O R Y D E S C R I P T I O N (U N I X )

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 Saves manuals and operation documents.

gui Saves the items related to Client software, such as executable program, logs, and configuration files.

ilog Saves the graphical interface development tools for ZXONM E300 Client.

java Saves the JAVA realtime running environment to support the report running.

manager Saves the startup programs, logs, and configuration files of the parent manager and various child managers.

report Saves the items related to report.

server Saves the startup programs of the ZXONM E300 Server and the Report Server.

sybase Saves the database support system SYBASE.

To perform typical installation of ZXONM E300 in Unix

1. Load the CD-ROM to the local drive.

The load operation varies in different operating systems.

Solaris platform

i. Put the ZXONM E300 installation CD into the CD-ROM drive.

ii. The CD-ROM is automatically loaded to the /cdrom. If the file manager is working, a window displaying information of the CD-ROM will pop up, as shown Figure 8.

Chapter 4 - ZXONM E300 Installation in Unix


F I G U R E 8 F I L E M AN AG E R W I N D O W

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 Path Driver S/W State H/W Type Description

============================================

disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE LITEON CD-ROM LTN485S

/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0

disk 1 10/0/15/1.6.0 sdisk CLAIMED DEVICE FUJITSU MAJ3182MC


iii. The above result shows that CD-ROM device is /dev/dsk/c0t0d0. Execute the following command to create a mount directory.

# mkdir /cdrom

iv. Execute the following command to mount the CD-ROM into the system.

# mount /dev/dsk/c0t0d0 /cdrom

2. Enter the installation CD and execute the install command.

# cd /cdrom/cdrom0 or cd /cdrom

# ./install

Where, /cdrom/cdrom0 is the fixed location of CD-ROM on the Solaris platform, and /cdrom is the mount directory created on the HP-UX platform.



3. Once the program starts running, it will conduct installation self-test and self-extract. Figure 9 shows self-extract.

F I G U R E 9 S E L F -E X T R AC T I N T E R F AC E

4. After self-extract is completed, the Introduction dialog box is displayed, as shown in Figure 10.

F I G U R E 10 I N S T AL L AT I O N I N T R O D U C T I O N D I AL O G B O X

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.



5. In Figure 10, click Next button to enter the License Agreement dialog box as shown in Figure 11.

F I G U R E 11 L I C E N S E AG R E E M E N T D I AL O G B O X

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.

F I G U R E 12 CH O O S E I N S T AL L FO L D E R D I AL O G B O X

Checkpoint: For initial installation, make sure that the space of the installation directory is no less than 4 GB.



7. Click Restore Default Folder to select a default path, or click Choose to select installation path. Click Next. The Choose Install Set dialog box pops up, as shown in Figure 13.

F I G U R E 13 CH O O S E I N S T AL L S E T D I AL O G B O X

Figure 13 lists three types of installation: Typical, Minimal and Custom.

Typical indicates complete installation of the ZXONM E300 EMS, minimal indicates installation with the minimal options, and custom indicates partial installation of EMS components.

The following description is based on typical installation.

8. In the Choose Install Set dialog box shown in Figure 13, click Typical and then click Next. The Pre-Installation Summary dialog box pops up, as shown in Figure 14.

F I G U R E 14 P R E - I N S T AL L AT I O N S U M M AR Y D I AL O G B O X



9. The Pre-Installation Summary dialog box shown in Figure 14 lists previously set installation information, including product name, install folder, link folder, and disk space information. Click Install to enter the Installing Unitrans ZXONM E300 window, as shown in Figure 15.

F I G U R E 15 I N S T AL L I N G U N I T R AN S ZXONM E300 W I N D O W

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.

F I G U R E 16 CH AN G E F I L E M O D E P R O M P T BO X



F I G U R E 17 S T AR T SYBASE P R O M P T B O X

F I G U R E 18 CR E AT E D AT AB A S E P R O M P T BO X

11. After the above three processes are completed successfully, the Install Complete dialog box pops up, as shown in Figure 19.



F I G U R E 19 I N S T AL L C O M P L E T E D I AL O G B O X

12. Take out the installation CD from the CD-ROM drive.

This operation varies on Solaris platform and HP-UX platform, and is respectively described below:

i. Solaris platform

The Solaris platform supports two types of CD-ROM ejection operations.

Enter the command eject cdrom in the command line.

In the window shown in Figure 8, select File->Eject Disk.

ii. HP-UX platform

Enter the command umount /cdrom in the command line.

13. In Figure 19, click Done to reboot the system automatically.

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.

To perform custom installation of ZXONM E300

1. Perform step 1 to step 7 in the section of Typical Installation to enter the Choose Install Set dialog box shown in Figure 13.



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.

Setting EMS Parameters 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.

2. Modify GATED=0 to GATED=1 in the file /etc/rc.config.d/netconf.

3. Modify the file /etc/gated.conf. Check if such information as ospf yes... exists. 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 file mgrcfg.ini using the editor vi or other file edit modes, 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 file mgrcfg.ini 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, IP represents 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 2000 and can be modified by user.

Configuring Communication between DB and Manager If the Manager and dbsvr are installed on different computers, modify the file installation directory/db/cfg and installation directory/manager/cfg to configure the communication between DB and Manager.

The OIDs in the cfg 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 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

......



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.


C h a p t e r 5

ZXONM E300 Installation in Windows

In this chapter, you will learn about: ZXONM E300 installation procedure in Windows

ZXONM E300 parameters configuration in Windows

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.

T AB L E 16 D I R E C T O R I E S AN D F I L E S I N T H E I N S T AL L AT I O N CD

Directory Sub-directory and File Description

doc Saves manuals and operation file

tools Tools, for example, DBMAN

os_patch Directory of the operating system patch


SYBASE

Sn.txt Serial number of the EMS installation program

doc Saves manuals and operation file

tools Tools, for example, DBMAN

os_patch Directory of the operating system patch


SQL Server

Sn.txt Serial number of the EMS installation program

2. Determine installation items based on networking modes and Table 6.



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.

T AB L E 17 S U B -D I R E C T O R I E S D E S C R I P T I O N ( I N WI N D O W S )

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 Saves the manuals and the operation documents.

gui Saves the items related to Client software, such as program, logs, and configuration files.

ilog Saves the interface developing tools for ZXONM E300 Client

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 Saves the items related to report.

server Saves the startup programs of ZXONM E300 server (Server) and the report server (Report Server).

sybase Saves files related to SYBASE. This sub-directory is created only when SYBASE database serves as the database support system for ZXONM E300.

sqlserver Saves files related to SQL Server. This sub-directory is created only when SQL Server database serves as the suppoort system for ZXONM E300.

The installation procedure of the ZXONM E300 based on SYBASE and that based on SQL Server are quite similar.

Chapter 5 - ZXONM E300 Installation in Windows


To install ZXONM E300 based on SYBASE (Typical)

1. Put the ZXONM E300 installation CD in the CD drive.

2. Run the file setup.exe to enter the Choose Setup Language dialog box, as shown in Figure 20.

F I G U R E 20 CH O O S E S E T U P L AN G U AG E D I AL O G B O X

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.

F I G U R E 21 I N S T AL L S H I E L D W I Z AR D D I AL O G B O X

4. After initialization, the initial window of ZXONM E300 installation will pop up, as shown in Figure 22.



F I G U R E 22 I N I T I AL W I N D O W O F I N S T AL L AT I O N

5. Click Next to enter the software License Agreement dialog box, as shown in Figure 23.

F I G U R E 23 L I C E N S E AG R E E M E N T D I AL O G B O X

6. Click Yes to accept the agreement. The Customer Information dialog box pops up, as shown in Figure 24.



F I G U R E 24 CU S T O M E R I N F O R M AT I O N D I AL O G B O X

Note: Get the serial number from the Sn.txt 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.

F I G U R E 25 CH O O S E D E S T I N AT I O N LO C AT I O N D I AL O G B O X



8. If the default installation directory is selected, go to next step directly. To customize the installation directory, click Browse. The Choose Folder dialog box pops up, as shown in Figure 26.

F I G U R E 26 CH O O S E FO L D E R D I AL O G B O X

9. Select the installation directory and click OK. The Choose Destination Location dialog box is displayed, as shown in Figure 27.

F I G U R E 27 CH O O S E D E S T I N AT I O N LO C AT I O N D I AL O G B O X



10. Click Next. The Setup Type dialog box will pop up, as shown in Figure 28.

F I G U R E 28 S E T U P TY P E D I AL O G B O X

The dialog box lists all types of setups:

The SYBASE database supports typical, custom, and client installations of the ZXONM E300.

The SQL Server database supports typical, client, compact, and custom installations of the ZXONM E300.

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.

F I G U R E 29 S E L E C T D E V I C E TY P E D I AL O G B O X



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.

T AB L E 18 R E L AT I O N B E T W E E N C H I L D M AN AG E R AN D NE

NE Type Child Manager Remarks

ZXMP S380, ZXMP S390 smgr10G (320) -

ZXMP S360 smgr2500 -

ZXMP S320 smgr600 -

ZXMP S330 smgr2500C -

ZXMP S100 smgrt150 -

ZXMP S385 smgr2510

ZXMP S200 smgrs200 -

ZXMP S325 smgrs325 -

ZXMP M800 (2M) smgrV3 2 M monitoring system

ZXMP M800 (100M) smgr100mV3 100 M monitoring system

ZXWM M900 smgrV2 2 M monitoring system

ZXWM M900 (100M) smgr100mV2 100 M monitoring system

ZXWM-32 (V1) smgrV1 -

ZXMP M600 smgrcwdm -

ZXMP P210, ZXMP P220, ZXMP P230, ZXMP P240

smgrpcm -

SDH Virtual - SDH virtual NE

The symbol “√” in front of an NE indicates that the child manager corresponding to this NE will be installed and the EMS can manage this NE type. Otherwise, it indicates that the EMS cannot manage this NE type.

To install all the child managers, click Select All. To clear all selected items, click Clear All. To select a child manager, select the corresponding NE directly.

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.



12. In the Select Device Type dialog box, click Next to enter the Select Program Folder dialog box, as shown in Figure 30.

F I G U R E 30 S E L E C T P R O G R AM FO L D E R D I AL O G B O X

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.

F I G U R E 31 I N S T AL L I N G D I AL O G B O X

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.



F I G U R E 32 S Y S T E M R E S T AR T S E L E C T I O N D I AL O G B O X

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.

To install ZXONM E300 (Compact)

1. Refer to step 1 to step 10 in the section of Typical Installation in Chapter 5 to enter the Setup Type dialog box.

2. Select Compact and follow step 11 to step 16 in the section of Typical Installation in Chapter 5 to complete the compact installation.

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.

To install ZXONM E300 (Custom)

1. Follow step 1 to step 10 in the section of Typical Installation in Chapter 5 to enter the Setup Type dialog box, as shown in Figure 28.



2. Select Custom and click Next to enter the Select Components dialog box, as shown in Figure 33.

F I G U R E 33 S E L E C T C O M P O N E N T S D I AL O G B O X

Figure 33 lists installation components of the ZXONM E300, including gui, manager, db, agent, doc, sybase, ilog, dbman, and server. Refer to Table 17 for the component descriptions.

A "√" in front of a component indicates that this component needs to be installed. Otherwise, the component does not need to be installed.

3. In Figure 33, select the components according to actual conditions and the dependencies listed in Table 6. Then, click Next to enter the Select Program Folder dialog box as shown in Figure 30.

4. Subsequent operations are similar to those of typical installation. Refer to step 13 to step 16 in the section of Typical Installation in Chapter 5.

Client Installation The client installation only installs ZXONM E300 EMS client and report server, and about 300 MB of hard disk space is needed.

To install ZXONM E300 (Client)

1. Follow step 1 to step 10 in the section of Typical Installation in Chapter 5 to enter the Setup Type dialog box, as shown in Figure 28.

2. Select Client and click Next to enter the Select Program Folder dialog box, as shown in Figure 30.

3. Subsequent operations are similar to those of typical installation. Refer to step 13 to step 16 in the section of Typical Installation in Chapter 5.



Setting EMS Parameters 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 file installation directory/gui/etc/mgrcfg.ini to configure communication between the GUI and Manager.

Open the file mgrcfg.ini, as shown in Figure 34.

In the mgrcfg.ini file, you can set the name of the Manager. The IP address of must be the same as the actual login IP address for the Manager. By default, the port of the Manager is 2000. You can modify the port number.

F I G U R E 34 M G R C F G . I N I F I L E W I N D O W

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.

The OID in the cfg 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.


//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

......

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.

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 35.

F I G U R E 35 SQL S E R V E R CL I E N T N E T W O R K U T I L I T Y D I AL O G B O X

In Figure 35, 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 35, click SQL_ZXONM and it will be highlighted. Click Edit to enter the Edit Network Library Configuration dialog box, as shown in Figure 36.

F I G U R E 36 E D I T N E T W O R K L I B R AR Y C O N F I G U R AT I O N D I A L O G B O X



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 37.

F I G U R E 37 E D I T N E T W O R K L I B R AR Y C O N F I G U R AT I O N D I A L O G B O X (M O D I F Y N E T W O R K L I B R AR Y )

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 35. 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.


C h a p t e r 6

Uninstallation and Upgrade of ZXONM E300

In this chapter, you will learn about: Uninstallation of ZXONM E300

Upgrade of ZXONM E300

Uninstalling ZXONM E300

Caution: Before uninstalling the ZXONM E300, make sure that the EMS has exit completely.

Uninstalling ZXONM E300 in Windows

To uninstall ZXONM E300 in Windows 2000

1. Select Start -> Settings -> Control Panel ->Add/Remove Programs to enter Add/Remove Programs dialog box.

2. Select the ZXONM_E300 in the Add/Remove Programs dialog box, as shown in Figure 38.



F I G U R E 38 AD D /R E M O V E PR O G R AM S D I AL O G B O X

3. Click Change/Remove to uninstall the ZXONM E300.

Uninstalling ZXONM E300 in Unix Suppose the ZOXNM E300 runs under the directory /opt/unitrans in the Unix platform, execute the following commands to uninstall the ZOXNM E300.

# cd /opt/unitrans

# ./uninstall

After the commands are executed, check whether the /opt/unitrans directory has been cleared.

If "zdaemon" is terminated abnormally by user during running, it is necessary to manually shut down programs that are still running before uninstalling the ZXONM E300.

Chapter 6 - Uninstallation and Upgrade of ZXONM E300


Upgrading ZXONM E300 To upgrade the ZXONM E300

1. Prepare for upgrade

Before upgrading the ZXONM E300, prepare the software to be upgraded first, and then make sure that all the boards, board programs, and EMS are compatible. If they are incompatible, upgrade board programs or replace boards.

If the NEs managed by the EMS include ZXMP S380 and ZXMP S390 of V3.1, it is necessary to upgrade NCP programs of the NEs while upgrading the ZXONM E300. For details, refer to the section of NCP Upgrade in Appendix B.

2. Back up or configure network data.

If the formats of network configuration data of ZXONM E300 in previous version and new version are compatible, use the backup function of EMS to back up the network configuration data to the EMS computer.

Caution: In Unix, all the files in the ZXONM E300 installation folder unitrans will be cleared during ZXONM E300 uninstallation. Therefore, the EMS data shouldn’t be saved in the unitrans folder. Also, for Windows, it is recommended not to save the EMS data in the installation folder.

If the formats of network configuration data of ZXONM E300 in previous version and new version are incompatible, follow the steps below:

i. Install the ZXONM E300 of new version on another computer.

ii. Configure network configuration data and back up the data.

iii. Copy the backed up data to the computer where the ZXONM E300 is to be upgraded, so that data can be recovered right after the new version of EMS is installed.

3. Uninstall the ZXONM E300 of old version

Refer to the section of Uninstalling ZXONM E300.

4. Install the ZXONM E300 of new version

Refer to Chapter 4 or Chapter 5 to install EMS of new version according to the operating system.

5. Restore or re-configure network configuration data

In need of restoring data, use the data backup/restoration function of ZXONM E300 to restore the backed up data to the ZXONM E300.

6. Connect NEs

For ZXMP S380 and ZXMP S390 of V3.1:



i. Use the ZXONM of new version to clear the NCP database of the NE.

ii. Re-download the configuration data.

iii. Upgrade the software version from V3.1 to V3.2 through DBMAN. For details, refer to the section of Converting Version from V3.1 to V3.2 in Appendix B.

Other NEs:

i. Upload and compare the data to check whether the data of ZXONM E300 and NE are consistent.

ii. If the data are consistent, go to step 7. If the data are inconsistent, check whether the data of ZXONM E300 or the data of NE is correct.

7. Check whether the ZXONM can monitor and manage the NEs normally. If fault exists, locate and remove the fault until all functions are normal.


A p p e n d i x A

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.



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.

Shell is a special program of the Unix operating system. It serves as the interface to kernel and users. That is, shell is a command interpreter of Unix and an advanced interpretative language. At present, common shells include Bourne Shell (or B Shell for short), Korn Shell (K Shell for short) and C-Shell.

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.

To initialize Unix operating system

1. Power on the Unix host, or run the command telnet to log in to the Unix host remotely.

2. Run the command getty to obtain terminal lines. Each terminal line will be initialized, and each terminal displays “login”.

3. Enter the user name and password.

4. The login process checks whether the user name and password are correct. If login is successful, the Shell process and /etc/profile file and $HOME/.login file are started.

5. A Unix prompt appears, waiting for user to enter a command.

Figure 39 shows comparison between the initialization of the Unix system and that of the DOS.

Appendix A - Introduction to Unix


F I G U R E 39 I N I T I AL I Z AT I O N B AS E O N U N I X AN D TH AT B A S E D O N DOS

Turn on Unixterminal

Invoke init

Boot kernel

getty getty

login login

shell shell

Turn on DOSterminal

Command

Boot kernel

……

Start a getty processfor each terminal line

Directory Structure Figure 40 shows the directory structure of Unix operating system.

F I G U R E 40 UN I X F I L E D I R E C T O R Y S T R U C T U R E

/

bin lib usr dev etc

smith sybase

prog d 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 prog file in Figure 40 is /usr/smith/prog. The full name of a



file path for the DOS starts from a drive letter, and names are separated by “\”, for example, c:\tmp\data\fox.

Table 19 lists common directories of the root file.

T AB L E 19 C O M M O N D I R E C T O R I E S O F R O O T F I L E

Directory Description

/ Root directory, the start point of all directories and files

/bin Most of executable Unix commands and shared programs

/dev Device files, for example, /dev/cd0

/etc System administration commands and data files

/lib C program database

/usr Saves family directories of users and shares programs or files of users

/tmp Temporary work directory. Saves some temporary files

Common Terms Terminal, terminal line, and terminal protocol

Users communicate with computers through terminals. A Unix host can connect multiple terminals through terminal lines and terminal protocols.

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.



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:

Common user: Common operators in the system, who are not allowed to perform operations such as setting the system time and shutting down the system. The system prompt this type of user is “$”.

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 /dev. For example, /dev/hd0 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, /dev/rhd0 indicates the raw device of the first floppy disk drive.



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 Line Format 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.

Basic command line format

You can enter Unix commands under prompts.

The basic format of Unix commands is:

# command parameter 1 parameter 2 … parameter n

A Unix command consists of a command and zero to multiple parameters. Space is used to separate command and parameters.

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:

File system commands: ls (list), cat, file, chmod, chown, chgrp, find, tar, cpio, cp (copy), mv (move), rm (remove), ln (link), mkdir, mknod, more, od, cd, pwd, and etc.

Edit commands: ed, vi, more, od, cat, grep, tail, and etc.

Network commands: rcp, rlogin, ftp, ping, and etc.

Process commands: ps, kill, nohup, and etc.

Introduction to Interface Buttons The traditional Unix user interface adopts the command line mode. The commands are difficult to remember. Therefore, the command line is hard to be spread to non-professional computer personnel. Now, graphic interfaces are added for most of Unix systems, thus make the system more operable.



The graphic interfaces of Unix support operation performed through mouse and keyboard. However, interface buttons of Unix are different from those of Windows. Figure 41 shows a graphic interface of Unix.

F I G U R E 41 UN I X GR AP H I C I N T E R F AC E

The following introduces the buttons in Figure 41:

: 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.

: Click this button to minimize a dialogue box or window.

: Click this button to maximize a dialogue box or window.

Special Key Command Table 20 lists commands of special keys supported by the Unix operating system.

T AB L E 20 S P E C I AL K E Y C O M M AN D S

Keys Description

CTRL + d To terminate keyboard input or exit the current Shell.

DEL Interruption key, to stop the current action and return to Shell.

CTRL + s To pause screen output.

CTRL + q To continue screen output.

CTRL + u Kill key, to delete all the characters in the line where the cursor is located.

ESC To terminate the current operation state such as editor.



Introduction to Common Commands This section introduces common commands in Unix.

Basic Commands Table 21 lists basic Unix commands.

T AB L E 21 B A S I C U N I X C O M M AN D S

Command Description Parameters

ls This command is equivalent to dir in DOS. It is used to list files and directory names.

-a : all files

-I : Node No.

-l : Details

-ac : Parse

-F : Format

-R : Recursion

mkdir To create a sub-directory. -

rmdir To delete a sub-directory. -

mv file file2 Change file name

-I : Overwrite existing file. The answer is “y” or “n”.

-f : Overwrite existing file without a prompt.

rm To delete a file -

cd To change the current directory -

pwd The current directory -

man + command name Help -

chmod To change access rights of various users to files -

chown To change the owner or group of various files -

tty Name of user terminal node -

cat Display text information -

cp Copy files -

ln Link -

find Find a file -

grep Search characters that match specified expression in a specified file

-

wc Technology -

ps Display the process status -



Command Description Parameters

kill Terminate a process -

nohup When a shell stops, it continues running. -

who User -

vi Text editor -

df Disk space -

mkfs Construct the file system -

mount Mount the file system -

dd Back up -

telnet hostname Telnet -

shutdown –g0 Shut down the system -

date Date -

exit Log out -

cal Calendar -

sleep Delay -

User Operation Commands Common commands used by users are listed in Table 22.

T AB L E 22 U S E R OP E R AT I O N C O M M AN D S O F U N I X

Command Description

passwd Change password

su Switch from a common user to the super user after login

admintool Start the system administration tool to manage system users

useradd Add a user

userdel Delete a user

userls Display login information of users and system

Note: Only the root user and authorized users can add, modify, or delete users.



Process Management Commands Common process management commands include:

ps

View statuses of processes running in the system, including process No., process status, user that start a process, command line description corresponding to a process, and other attributes of processes.

Run background processes

The Unix system only allows one foreground process only at the same time, and other processes are background processes. To start a background process, add a symbol “&” at the end of the command line.

For example, executing the command find in the background to find the file abc in the current directory and its sub-directories. The command and result are as follows:

$ find . -name abc -print&

10722

Where, 10722 is the process No. When the command find is executed in the background, the system returns the result and displays it.

kill

Terminate a background process. The format of the command is: kill process No.. The process No. is the unique ID of a process. It is obtained through the command ps.

exit

This command has the same effect as the keyboard operation: CTRL+D. It is used to exit the current Shell. In addition, all foreground and the background programs currently operated by a user will exit automatically. After the command is executed, a prompt login: is displayed on the screen, waiting for next user to log in to the terminal.

nohup

After the terminal exits, this command is execute to continue to run background programs.

The command line format is: nohup original command line. For example:

$ nohup find . -name abc -print&

This command line indicates that after the current user exits, the system continues to execute the command find in the background to find the file abc 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



files, telnet, and copy files remotely. Common network commands include :

ftp

It is a file transfer command to copy one or more files in a remote Unix system to a local computer, or copy one or more files from the local computer to a remote Unix system.

Command line format

ftp IP address or domain name of a remote Unix host.

After the command is executed, the screen prompts to enter a user name and password. If the password is correct, a prompt ftp> will appear.

The command ftp must be executed under the prompt.

Common ftp commands

Table 23 lists common ftp commands.

T AB L E 23 C O M M O N F T P C O M M AN D S

ftp Command Description

? [command]

or help [command] Command help

Binary Set binary transmission mode for files

Ascii Set ASCII transmission mode for files (default)

cd [directory] Change remote directory

Pwd List directories of the current remote host

dir [r-dir] [l-file]

Display remote directories. “r-dir” indicates remote directory, and “l-dir” indicates local files. If there are local files, write the result into the local files.

ls [r-dir] [l-file]

It has the same function as dir , but the display format is different.

lcd [directory] Change the local directory.

put file1 [file2] Copy local file1 to remote file2.

get file1 [fine2] Copy the remote file1 into the local file2

mput files Copy multiple local files to remote files

mget files Copy multiple remote files to local files.

Status Display the current FTP status.

!command Execute the local command and return to FTP at once.

open IP address or domain name Re-establish a connection.

Close Shut down a remote connection.

quit or bye To exit ftp



rcp

It is a copy command for remote files, and its function is similar to ftp.

The command line format is:

rcp IP address or domain name of host1: file1 IP address or domain name of host2: file 2.

The command is to copy file1 in host1 to file2 in host2.

rlgoin

It is a remote login command, that is, the command is to enable one computer to telnet another one.

If login is successful, the command line entered in the local computer will be transmitted to the remote host through the network, and the output result will be sent back and displayed in the local computer after the command is executed. For the command rlogin, the command line is executed by the remote host, and the local computer only serves as a terminal.

telnet

It is a remote login command to enable the local computer to log in to the remote Unix host, regarding the local computer as an emulated terminal of the remote Unix host. It has similar function as the command rlogin.


telenet IP address or domain name of remote Unix host.

For example, telent 129.9.98.98 is a command to log in to a host whose IP address is 129.9.98.98.

After the command is executed, a local computer prompts to enter the Unix user name and password and the terminal type. At last, the prompt of the Unix operating system appears.

ping

The ping command is to check the network connections between a local computer and other hosts. It can be used to check if the peer end is switched on or the network connection is correct for both file transmission or remote login.


ping IP address or domain name.

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.



Floppy Drive and Tape Drive In Unix, the command tar is used to save data in the floppy drive or tape drive. Take the tape drive for example. Its basic operations are as follows:

Write data into the tape. # tar cf /dev/rmt/0mb file

Read the tape.

# tar xf /dev/rmt/0mb

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 Path Driver S/W State H/W Type Description

============================================

disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE LITEON CD-ROM LTN485S


disk 1 10/0/15/1.6.0 sdisk CLAIMED DEVICE FUJITSU MAJ3182MC


The above result shows that the device name is /dev/dsk/c0t0d0.

2. Execute the following command to create a mount directory

# mkdir /cdrom

Checkpoint: Before executing the command mount , ensure that a CD has been inserted into the CD-ROM drive. Otherwise, the command will fail.

3. Execute the following command to mount the CD-ROM into the system.

# mount /dev/dsk/c0t0d0 /cdrom

4. Execute the following command to unmount the CD-ROM.

# umount /cdrom


A p p e n d i x B

Upgrade of ZXMP S380/S390

This appendix describes the version conversion of ZXMP S380/S390, and the upgrade procedure of NCP of ZXMP S380/S390 equipment.

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.

T AB L E 24 R E L AT I O N S H I P B E T W E E N S O F T W AR E V E R S I O N S O F ZXMP S380 /S390 AN D ZXONM E300

Software Version of ZXMP S380/S390

Version Description Corresponding Sub-manager

Support from ZXONM E300

V3.1

The NCP program is bound with the ZXONM E300 software.

It is necessary to upgrade the NCP program after the ZXONM E300 is upgraded. Otherwise, the ZXONM E300 of new version cannot manage the NE.

smgr10g

The ZXONM E300 of versions earlier than V3.15 supports V3.1 only.

V3.2

The NCP program is separated from the ZXONM E300 software.

The upgraded ZXONM can manage the NE even if the NCP program of NE is not upgraded. However, some functions can be performed only after the NCP is upgraded.

smgr10g_320

ZXONM E300 of V3.16R1 and later versions support V3.2.



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.

To query software versions of ZXMP S380/S390 equipment

1. In the client operation window, right-click the ZXMP S380/S390 NE to be queried, and the right-click menu of the NE will pop up.

2. Select the menu item of NE Property to enter the NE Property dialog box, as shown in Figure 42.

F I G U R E 42 NE P R O P E R T Y D I AL O G B O X

3. Click Advanced button to enter the Advanced dialog box, as shown in Figure 43. Software version shows the software version of the selected NE.

Appendix B - Upgrade of ZXMP S380/S390


F I G U R E 43 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.



F I G U R E 44 R E L AT I O N S H I P B E T W E E N ZXMP S380 /S390 U P G R AD E AN D EMS U P G R AD E

Upgrade the EMS

The new EMSversion is equal to or later than

V3.16R1?

Begin

End

Query the software version ofZXMP S380/S390

V3.1

Upgrade the NCP

Run the DBMAN programto convert the software

version from V3.1 to V3.2

Yes

No

Need new functions of the EMS?

V3.2

No

Upgrade the NCP

Yes

For NCP upgrade operations, refer to the section of NCP Upgrade. To convert software version from V3.1 to V3.2, refer to the section of Converting Version from V3.1 to V3.2.

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.

T AB L E 25 S T AT U S O F NCP B O AR D

NCP Status Function DIP Switch

DOWNLOAD Download the Agent application and configuration files All ON

Running Start the application on the NCP Not all ON and not all OFF



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.

Local Data Initialization The local data initialization means that the operator downloads and remakes the NCP program at the local place where the equipment is located, and when the IP address of NCP board is the obliged one (192.192.192.11).

To perform local data initialization

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 telnet 192.192.192.11 command on the EMS computer.

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 NCP>:

NCP>format

NCP>exit

5. Configure MAC address of NCP board

i. Execute the telnet 192.192.192.11 command on the EMS computer.

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 configure MAC address of NCP board under the prompt NCP>:

NCP>setup

iv. Input address information according to settings of corresponding software version as listed in Table 26.

T AB L E 26 S E T T I N G S O F S E TU P C O M M AN D

Software Version

Settings of Command

V3.1

Multiple pieces of information will be displayed after the setup command is input. Only the MAC address and the NE IP address are meaningful.

NE IP address must be set to 192.192.192.11

The format of MAC address is: 00:D0:D0:xx:xx:xx. The MAC address of each NCP board in a network should be unique.

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.

v. The system prompts [Save[s]/Cancel[c]]. Input s to save the

configuration. Input c to cancel current configuration and keep the original MAC address of NE.

vi. Input the exit command. The configuration is completed.

NCP>exit

6. Download the Agent application

i. Execute the ftp 192.192.192.11 command under the directory containing the Agent application (ram.bin) on the computer.

ii. The system prompts to enter the user name and password. Leave the user name and password empty and directly press ENTER until the FTP> prompt appears.

iii. Type the following commands under the FTP> prompt:

FTP> bin

FTP> put ram.bin RAM.BIN

//Upload the NCP program to the flash disk. This procedure takes about three to four minutes. ram.bin is the file name of NCP program in the computer.

FTP> bye

7. Download Agent Configuration File

i. Edit the SDH.CFG text file on the computer.



The content template of the SDH.CFG file of V3.1 NE is:

192.1.1.18 255.255.255.0 1 4 5 1 1

The content template of the SDH.CFG file of V3.2 NE can be simplified as:

192.1.1.18 255.255.255.0

Table 27 describes the format of the SDH.CFG file.

T AB L E 27 FO R M AT O F T H E SDH.CFG F I L E

Line No. Content V3.1 Example V3.2 Example

1 NE address when the Agent application is executed

192.1.1.18 192.1.1.18

2 Subnet mask 255.255.255.0 255.255.255.0

3 NE ID 4 -

4 NE rate (1=STM-1, 2=STM-4, 3=STM-16, 4=STM-64)

4 -

5 NE type (1=TM, 2=ADM, 3=REG, 5=ADM&REG)

5 -

6 Single or dual system (1 = single system, 2 = dual systems)

1 -

7

Start ECC or not (1 = start, 0 = not start). Generally, ECC should be started; otherwise, management between NEs via optical fiber is unavailable.

1 -

ii. Execute the ftp 192.192.192.11 command. The system prompts to enter the user name and password. Leave the user name and password empty and directly press ENTER until the FTP> prompt appears.

iii. Type the following commands under the FTP> prompt:

FTP> ascii

FTP> put SDH.CFG

FTP> bye

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.



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 ping NE_IP 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.

Clear NCP database via EMS

Start the ZXONM E300 EMS. In the EMS client operation window, confirm that the NE status is online. Click the System -> NCP Data Management -> Clear NCP DB menu.

Clear NCP database via Command Line

Execute the telnet NE_IP command on the EMS computer. Enter zte for username and ecc for password. Press ENTER until the ZTE+> prompt appears. According to the version of NE, execute the corresponding commands listed below.

NE of V3.1

ZTE+>deldb //Delete the database. Once the command is delivered, the NCP board will automatically reboot and database will be deleted.

ZTE+>exit //Exit telnet.

Note: If the NCP board does not reboot automatically, execute the reboot command to forcibly reboot the NCP.

NE of V3.2

ZTE+>rm –rf DbSys //Delete the database. The prompt of ZTE+> will appear after database is deleted.

ZTE+>d-reboot //Reboot the NCP board.

ZTE+>exit //Exit telnet.



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 ping 188.92.3.18 command on the EMS to make sure that the NE can be pinged through.

2. Execute the ftp 188.92.3.18 command and connect the EMS to the NCP board. Enter zte for the username and ecc for the password.

Caution: The username and password must be lowercases.

3. Input the following commands under the ftp> prompt:

ftp> bin //Set the file sending format as binary

ftp> rm RAM.OLD

//Delete the old NCP program created by previous upgrade. ftp> put ram.bin RAM.NEW //ram.bin is the NCP program used for upgrade on the computer, and the RAM.NEW is the file name of the new NCP program downloaded to the NCP board.

Caution:

RAM.NEW cannot be input as the RAM.BIN which is the name of the running NCP program. Otherwise, once the download process is interrupted, the NCP program will be damaged and cannot be started.

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.



ftp>rename RAM.BIN RAM.OLD //Change the name of the old NCP program to RAM.OLD.

ftp> rename RAM.NEW RAM.BIN

//Change the name of the newly downloaded NCP program to NCP program RAM.BIN. ftp>bye

4. In the EMS client operation window, select this NE and select the System > NCP Data Management > Clear NCP DB menu to clear the NCP database on line. Then the NCP will 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.

Converting Version from V3.1 to V3.2

Note: After NCP upgrade, it is necessary to upgrade the NE software version from V3.1 to V3.2.

For NE of version V3.1, it is necessary to upgrade the software version using the DBMAN tool in the following procedure.

1. Enter the EMS installation directory /dbman to open the dbman.bat file and enter the dbman interface, as shown in Figure 45.



F I G U R E 45 D B M AN I N T E R F AC E

2. Type 7 to enter the Change Ne Software Version interface, as

shown in Figure 46.

F I G U R E 46 CH AN G E NE S O F T W AR E V E R S I O N I N T E R F AC E

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.



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

3. Modify versions of all NEs.

i. In Figure 46, type 3.

ii. If the version conversion succeeds, reboot the ZXONM E300 Server as prompted by the system.

4. Modify the version of the designated NE.

i. In Figure 46, type 2, and then the Change Ne Software Version interface is as shown in Figure 47. Selected NE: becomes null, and 2. Select All Nes : yes is changed to 2. Select All Nes : no.

F I G U R E 47 CH AN G E N E S O F T W AR E V E R S I O N I N T E R F AC E (S E L E C T I N G AL L NE S I S N O T AL L O W E D )

ii. Type 1 to enter the SELECT NE interface shown in Figure 48. It lists NE names and IDs of all the ZXMP S380 and ZXMP S390 equipment.

F I G U R E 48 SELECT NE IN T E R F AC E



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.

F I G U R E 49 CH AN G E N E S O F T W AR E V E R S I O N I N T E R F AC E (C O N V E R T I N G T H E V E R S I O N O F T H E D E S I G N AT E D NE)

iv. Type 3.

v. If the version conversion succeeds, reboot the ZXONM E300 Server as prompted by the system.


A p p e n d i x C

Installation FAQ

This chapter provides solutions to installation problems that may occur on different platforms.

FAQ for Installation Based on 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:

i. Some temporary files are stored under the directory /tmp during installation. After the system is powered off suddenly, these files are not cleared 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 bdf 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 /var/preserve. This information is not released after the system reboots.

iv. Sudden power-off makes temporary files under the directory /var/tmp not released.

Solution:

i. Delete the files in the folders: /tmp, /opt/lost+found, /var/tmp, and /var/preserve.

ii. Delete the EMS installation directory, and re-install the EMS.



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. Execute the command bdf 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 #bdf is executed, the following information will be displayed:

Filesystem kbytes used avail %used Mounted on

/dev/vg00/lvol3 143360 134789 8258 94% /

/dev/vg00/lvol1 83733 27637 47722 37% /stand

/dev/vg00/lvol9 2867200 2639553 213865 93% /home

/dev/vg00/lvol8 532480 426533 99682 81% /var

/dev/vg00/lvol7 512000 507975 3788 99% /usr

/dev/vg00/lvol4 65536 2043 59652 3% /tmp

/dev/vg00/lvol6 3072000 72000 3000000 3% /opt

Filesystem indicates the file system;

kbytes indicates the size of the file system;

used indicates the used space in unit of Kbyte;

avail indicates the available space in unit of Kbyte;

%used indicates the space utilization ratio;

Mounted on indicates the installation location.

According to the above result, select /opt files 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, you can 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:

Appendix C - Installation FAQ


#mount *

#cp –r opt /home/

iv. Delete the logical volume where the filesystemsrc file system is located.

To delete /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 on vg00 and the mounting point is on directory /opt, 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.

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 #vgdisplay, 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 umount command?

After installing the EMS on the HP-UX platform using a CD and rebooting the computer, execute the umount 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 mount 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 umount 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 sam.

ii. Select Display, X Server Configuration, and HP VISUALIZE-FXE in sequence.

iii. Select the Actions -> Modify Default Visual menu.

iv. Set Default Visual to Image, Depth24 True Color.

FAQ for Installation Based on 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.

Format of hosts file is:

127.0.0.1 localhost //Loopback address of local host

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 the IP address for local host?

i. Execute the command netstate-r to query the routing information of local host.

ii. Execute the command ifconfig –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 init 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 Current resolution setting: 1280x1024x76 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 in < >.

Other Installation FAQ 1. 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 setup program again to install the EMS.

2. When installing EMS in Windows operating system, an alert box pops up, as shown in Figure 50. Why does this happen?

F I G U R E 50 S E T U P E R R O R AL E R T B O X



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.

3. 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.

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 correctly.

ii. Set parameters correctly according to Chapter 3.

iii. Start dbman program to check whether the database is successfully created. If no, use dbman to create the database.

iv. Set parameters correctly according to the section of Configuration of Unix in Chapter 3

4. If the ZXONM E300 is installed by compact installation, the alert box shown in Figure 51 appears when starting the server. Why does this happen?

F I G U R E 51 SQL_S E R V E R E R R O R AL L E R T B O X



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.

iii. Reboot the server of ZXONM E300.

5. 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. 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 5.

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 dbman.bat in the installation directory /dbman to enter the main interface of the dbman, as shown in Figure 52.

F I G U R E 52 M AI N I N T E R F AC E O F D B M AN



iv. Type 3 and press ENTER to enter the Database Management window, as shown in Figure 53.

F I G U R E 53 D AT AB AS E M AN A G E M E N T W I N D O W

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?

Solution:

Reinstall the ZXONM E300 supported by SQL Server database. The ZXONM E300 supported by SYBASE database must be installed on Windows 2000 Server.


A p p e n d i x D

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 Union- Telecommunication Standardization Sector

L

LAN Local Area Network

LCT Local Craft Terminal



Abbreviations Full Name

N

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

W

WAN Wide Area Network

WDM Wavelength Division Multiplexing


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



Figure 48 SELECT NE Interface ..................................................................102 Figure 49 Change Ne Software Version Interface (Converting the Version of the

Designated NE) ................................................................................103 Figure 50 Setup Error Alert Box..................................................................109 Figure 51 SQL_Server Error Allert Box.........................................................110 Figure 52 Main Interface of dbman .............................................................111 Figure 53 Database Management Window....................................................112


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

unitrans zxonm e300(v3.17) installation manual

Documents