sjzl20090609-unitrans zxonm e300(v3.19r2) maintenance manual_516854

of 129/129
ZXONM E300 Unified EMS/SNMS of Optical Network Maintenance Manual Version 3.19R2 ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: [email protected]

Post on 06-Feb-2016

59 views

Category:

Documents

24 download

Embed Size (px)

DESCRIPTION

Unitrans ZXONM

TRANSCRIPT

  • ZXONM E300Unified EMS/SNMS of Optical Network

    Maintenance Manual

    Version 3.19R2

    ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755 26771900 800-9830-9830 Fax: (86) 755 26772236 URL: http://support.zte.com.cn E-mail: [email protected]

  • LEGAL INFORMATION

    Copyright 2006 ZTE CORPORATION.

    The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.

    All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION or of their respective owners.

    This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the information contained herein.

    ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter herein.

    ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

    Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

    The ultimate right to interpret this product resides in ZTE CORPORATION.

    Revision History

    Date Revision No. Serial No. Description

    Jun. 18, 2007 R1.0 sjzl20071700 First edition

    May. 4, 2008 R1.0 sjzl20081489 Upgrade parts of the operating interfaces according to the new EMS version

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

  • ZTE CORPORATION Values Your Comments & Suggestions! Your opinion is of great value and will help us improve the quality of our product documentation and offer better services to our customers.

    Please fax to: (86) 755-26772236; or mail to Publications R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057.

    Thank you for your cooperation!

    Document Name

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

    Product Version V3.19R2

    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)

    Good Fair Average Poor Bad N/A

    Your evaluation of this documentation

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

    Good Fair Average Poor Bad N/A

    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 Manual .......................................................................................i Purpose .................................................................................................................. i Intended Audience................................................................................................... i Prerequisite Skill and Knowledge...............................................................................i What is in this Manual .............................................................................................. i Related Documentation........................................................................................... ii Conventions...........................................................................................................iii How to Get in Touch ...............................................................................................v

    Customer Support...................................................................................................................v Documentation Support...........................................................................................................v

    Chapter 1........................................................................................ 1

    Maintenance Overview...............................................................................1 Maintenance Classification.......................................................................................1

    Routine Maintenance...............................................................................................................1 Emergency Maintenance..........................................................................................................1

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

    Chapter 2........................................................................................ 3

    Routine Maintenance .................................................................................3 Operation Instructions.............................................................................................3 Managing Users......................................................................................................3

    Purpose ..................................................................................................................................3 Operations..............................................................................................................................3 Inspection Criteria ...................................................................................................................4 Troubleshooting ......................................................................................................................4

    Checking EMS Connection .......................................................................................4 Purpose ..................................................................................................................................4 Operations..............................................................................................................................4 Inspection Criteria ...................................................................................................................4 Troubleshooting ......................................................................................................................5

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

  • Inspection Criteria ...................................................................................................................5 Troubleshooting ......................................................................................................................5

    Monitoring Alarms...................................................................................................6 Purpose ..................................................................................................................................6 Operations..............................................................................................................................6 Inspection Criteria ...................................................................................................................6 Troubleshooting ......................................................................................................................6

    Monitoring Performance ..........................................................................................6 Purpose ..................................................................................................................................6 Operations..............................................................................................................................6 Inspection Criteria ...................................................................................................................7 Troubleshooting ......................................................................................................................7

    Querying System Configuration ...............................................................................7 Purpose ..................................................................................................................................7 Operations..............................................................................................................................7 Inspection Criteria ...................................................................................................................7 Troubleshooting ......................................................................................................................7

    Querying User Operation Log...................................................................................8 Purpose ..................................................................................................................................8 Operations..............................................................................................................................8 Inspection Criteria ...................................................................................................................8 Troubleshooting ......................................................................................................................8

    Printing Report .......................................................................................................8 Purpose ..................................................................................................................................8 Operations..............................................................................................................................8 Inspection Criteria ...................................................................................................................9 Troubleshooting ......................................................................................................................9

    Saving/Printing Alarm/Performance Messages...........................................................9 Purpose ..................................................................................................................................9 Operations..............................................................................................................................9 Inspection Criteria ...................................................................................................................9 Troubleshooting ....................................................................................................................10

    Backing up Data...................................................................................................10 Purpose ................................................................................................................................10 Operations............................................................................................................................10 Inspection Criteria .................................................................................................................11 Troubleshooting ....................................................................................................................11

    Restoring Data .....................................................................................................11 Purpose ................................................................................................................................11 Operations............................................................................................................................11 Inspection Criteria .................................................................................................................12 Troubleshooting ....................................................................................................................12

  • Chapter 3......................................................................................13

    Maintenance of Operating System ......................................................... 13 Running Environment Requirements of ZXONM E300 ..............................................13

    Unix Platform........................................................................................................................13 Windows Platform .................................................................................................................14

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

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

    Chapter 4......................................................................................25

    EMS Installation and Upgrade ................................................................ 25 Installation Flow ...................................................................................................25 Upgrading ZXONM E400 to ZXONM E300 ...............................................................26

    Preparing for Upgrade ...........................................................................................................26 Upgrade Operations ..............................................................................................................27

    Upgrading ZXONM E300........................................................................................28 Applicable Scope ...................................................................................................................29 Preparing for Upgrade ...........................................................................................................29 Upgrading EMS in Unix ..........................................................................................................29 Upgrading EMS in Windows ...................................................................................................36 Sharing Data between EMS in Unix and EMS in Windows ........................................................39

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

    Setting EMS Parameters in Unix.............................................................................44 Setting Dynamic Route..........................................................................................................44 Configuring Communication between GUI and Manager..........................................................45 Configuring Communication between DB and Manager ...........................................................45 Configuring Database Synchronization....................................................................................46

    FAQ.....................................................................................................................46 FAQ for EMS Installation in HP-UX..........................................................................................46 FAQ for EMS Installation in SUN.............................................................................................49 Other Installation FAQ ...........................................................................................................52

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

    Maintenance of EMS................................................................................ 57

  • EMS Connection Fault ...........................................................................................57 Common Faults.....................................................................................................................57 Typical Faults and Analysis.....................................................................................................58

    Database Fault .....................................................................................................59 Manager Fault ......................................................................................................60 Agent Fault ..........................................................................................................60 Other Faults .........................................................................................................61 Setting Environment Variables...............................................................................62

    Overview ..............................................................................................................................62 Setting Environment Variable.................................................................................................63

    Appendix A ...................................................................................67

    DBMAN Operations.................................................................................. 67 DBMAN Overview .................................................................................................67

    Major Functions.....................................................................................................................67 Launching DBMAN.................................................................................................................67 DBMAN Main Window in Windows 2000 .................................................................................68

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

    Database Management Operations.........................................................................73 Monitoring Database..............................................................................................................73 Creating Database.................................................................................................................75 Deleting Database.................................................................................................................75 Extending Database ..............................................................................................................76 Clearing Database.................................................................................................................78 Recreating Tables & Stored Procedure....................................................................................78

    Backing Up and Restoring Data..............................................................................78 Backing up Data....................................................................................................................79 Restoring Data ......................................................................................................................80 Merging Another EMSs Data..................................................................................................81 Backing up NE Timeslot .........................................................................................................82 Restoring NE Timeslot ...........................................................................................................83 Backing up NE Information ....................................................................................................83 Restoring NE Information.......................................................................................................84

    Checking Timeslot ................................................................................................85 Restoring ZXONM E100 data in ZXONM E300..........................................................85 Changing NE Software Version...............................................................................86

    Changing Software Versions of All NEs ...................................................................................86

  • Changing Software Version of Selected NE .............................................................................87 Changing NE ID....................................................................................................88 V3.16 Backup File Update to V3.17 ........................................................................89 Analyse and Process Network Data ........................................................................90 Replication System Management Operations...........................................................90

    Installing/Uninstalling Replication Server ................................................................................91 Configuring Replication System..............................................................................................92 Maintaining Replication System..............................................................................................99 Monitoring Replication System .............................................................................................105

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

    Abbreviations ........................................................................................ 109

    Figures........................................................................................111

    Tables .........................................................................................113

  • Confidential and Proprietary Information of ZTE CORPORATION i

    About this Manual

    Purpose This manual provides the basic information about how to maintain the ZXONM E300 (V3.19R2).

    Intended Audience This manual is intended for engineers and technicians who perform maintenance activities on ZXONM E300.

    Prerequisite Skill and Knowledge To use this manual effectively, users should have a general understanding of optical transmission technology and network management system. Familiarity with the following is helpful:

    System and various components of transmission equipment of ZTE User interfaces of the ZXONM E300 Basic operations of the ZXONM E300

    What is in this Manual This manual is the Unitrans ZXONM E300 (V3.19R2) Unified EMS/SNMS of Optical Network Maintenance Manual. It provides basic information about how to maintain the ZXONM E300 (V3.19R2).

    This manual includes five chapters and two appendixes:

    Chapter Description

    Chapter 1 Maintenance Overview Describes the classification of ZXONM E300 maintenance operations, and the system management rules.

    Chapter 2 Routine Maintenance Describes the routine maintenance operations on ZXONM E300.

    Chapter 3 Maintenance of Describes the requirements for ZXONM E300 running

  • ZXONM E300 (V3.19R2) Maintenance Manual

    ii Confidential and Proprietary Information of ZTE CORPORATION

    Chapter Description

    Operating System environment, the installation and configuration of Windows and Unix operating systems, and FAQ.

    Chapter 4 EMS Installation and Upgrade

    Describes the installation procedure, upgrade procedure, and parameter settings of ZXONM E300.

    Chapter 5 Maintenance of EMS Describes how to maintain the EMS and how to set environment variables when fault occurs to the EMS connection, database, Manager, or Agent.

    Appendix A DBMAN Operations Takes the DBMAN tool in Windows 2000 operating system to illustrate various functions of DBMAN.

    Appendix B Abbreviations Gives some terms and abbreviations for users reference.

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

    1. Management scope of ZXONM E300 (V3.19R2)

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

    DWDM equipment: ZXWM-32(V1), ZXWM M900, ZXMP M800, ZXMP M720, ZXMP M820, ZXMP M920

    CWDM equipment: ZXMP M600

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

    2. Manual suite

    Manual Name Function

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

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

    Unitrans ZXONM E300 (V3.19R2) 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.19R2) 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.19R2) Unified EMS/SNMS of Optical Network LCT Users Manual

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

    Unitrans ZXONM E300 (V3.19R2) Unified It describes the maintenance

  • About this Manual

    Confidential and Proprietary Information of ZTE CORPORATION

    iii

    Manual Name Function

    EMS/SNMS of Optical Network Maintenance Manual

    knowledge of ZXONM E300.

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

    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.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    iv Confidential and Proprietary Information of ZTE CORPORATION

    Typeface Meaning

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

    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.

  • About this Manual

    Confidential and Proprietary Information of ZTE CORPORATION

    v

    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.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    vi Confidential and Proprietary Information of ZTE CORPORATION

    This page is intentionally blank.

  • Confidential and Proprietary Information of ZTE CORPORATION 1

    C h a p t e r 1

    Maintenance Overview

    In this chapter, you will learn about: Classification of EMS maintenance operations Management rules for the EMS

    Maintenance Classification The maintenance operations on EMS fall into two categories: routine maintenance and emergency maintenance.

    Routine Maintenance Routine maintenance involves checking the EMS running status periodically, and handling the problems promptly; so as to find hidden trouble, prevent accident, find fault, and handle them as early as possible.

    Emergency Maintenance Emergency maintenance is also called troubleshooting. It involves maintenance tasks brought by transmission equipment faults or network adjustments, such as the maintenance tasks to handle equipment damage, line faults, and emergency events found and recorded in routine maintenance.

    Management Rules for EMS 1. Do not exit the EMS when it working normally. Exiting the EMS will not

    interrupt services; however, the EMS would be unable to monitor the NEs.

    2. Create a unique account for each user to log into the EMS, assign proper authorities to each account, and change the EMS password periodically to ensure its security.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    2 Confidential and Proprietary Information of ZTE CORPORATION

    3. Do not use the EMS to dispatch services during the traffic peak hours. Otherwise, any wrong operation will seriously affect the services. Choose the period when the traffic is the least to dispatch services.

    4. Back up the data in time after dispatching services, so that the services can be recovered promptly in the case of fault.

    5. Do not play games on the EMS computer or copy irrelevant files/software to the EMS computer. Use the anti-virus software to kill virus on the EMS computer periodically to prevent the EMS computer from getting infected by virus.

  • Confidential and Proprietary Information of ZTE CORPORATION 3

    C h a p t e r 2

    Routine Maintenance

    Operation Instructions The EMS is a very important tool for routine maintenance. To ensure the EMS is running reliably, the maintenance personnel at the site where the EMS is located should check the running status of the equipment via EMS everyday.

    This chapter briefly describes the EMS maintenance operations. For operation details, refer to the Unitrans ZXONM E300 (V3.19R2) Unified SNMS/EMS of Optical Network Operation Manual.

    Managing Users Purpose In order to prevent illegal user from logging into the EMS, and to guarantee normal running and service security of equipment, it is necessary to change the password of an EMS user and assign proper operation authority to an EMS user.

    Operations 1. Assign an EMS user with a unique username, a password,

    management objects, and a user level according to his operation authorities.

    Note: The EMS provides four levels of users: administrator, maintainer, operator, and monitoring user; each of which has certain operation authorities.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    4 Confidential and Proprietary Information of ZTE CORPORATION

    2. Change the login password for each EMS user periodically.

    Tip: An administrator has all the operation authorities on the EMS, and an improper operation taken by him may result in serious damage to the system. Therefore, it is suggested no to log into the EMS as an administrator during routine operations. Instead, create a monitoring user and log into the EMS as a monitoring user.

    Inspection Criteria 1. An EMS user can log into the EMS using the designated username and

    password; and he has been assigned with proper operation authorities.

    2. An EMS user can change his password periodically.

    Troubleshooting 1. If an EMS user has improper operation authorities or cannot change

    the password, ask the administrator to check the configuration data of the user or change the authorities and password of the user.

    2. To troubleshoot fault of EMS connection, refer to the Handling EMS Connection Fault section in Chapter 5.

    Checking EMS Connection Purpose To ensure that the EMS can reflect the equipment running status in time and accurately, and can monitor the equipment effectively, it is necessary to check the connection between the equipment and the EMS.

    Operations 1. On the computer installed with the EMS client software, run the

    ZXONM E300 client software and log into the server.

    2. In the EMS client operation window, select an online NE, and click the Maintenance -> Time Management menu item.

    Inspection Criteria 1. Based on the Operations described in step 1, the user can log into the

    server normally from the client computer.

    2. Based on the Operations described in step 2, the NE's NCP time can be queried.

  • Chapter 2 - Routine Maintenance

    Confidential and Proprietary Information of ZTE CORPORATION 5

    Troubleshooting To troubleshoot fault of EMS connection, refer to the Handling EMS Connection Fault section in Chapter 5.

    Monitoring Topology Purpose The ZXONM E300 client operation window can give audible and visible alarms. User can monitor the running status of the current subnet and NEs via the navigation tree, topology, NE icons, and the board management dialog box; and can judge the alarm level through the sound or color given with the alarm.

    Operations 1. Log into the EMS server on the client computer, and enters the EMS

    client operation window.

    2. Observe the NE icons in the client operation window, and the board icons in the board management dialog box.

    Note: The EMS software can only monitor or manage the NEs that are communicating with the EMS computer normally.

    Inspection Criteria 1. The NE icon is not grey which indicates that the NE is online.

    2. The NE icon bears no alarm identifier.

    3. The optical connections are normal.

    Troubleshooting 1. To troubleshoot fault of EMS connection, refer to the Handling EMS

    Connection Fault section in Chapter 5.

    2. If the NE icon bears alarm identifier, query the detailed alarm message in the current alarm monitoring dialog box or window. To handle alarm messages, refer to the maintenance manual of the SDH equipment.

    3. If the optical connection is a dotted line in the EMS, check the corresponding optical fiber and fiber pigtail.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    6 Confidential and Proprietary Information of ZTE CORPORATION

    Monitoring Alarms Purpose In the ZXONM E300 EMS, user can monitor the alarm messages of a NE, so as to know about the NE current running status, to discover and handle the NE alarm messages.

    Note: The EMS software can only monitor or manage the NEs that are communicating with the EMS computer normally.

    Operations 1. In the EMS client operation window, open the monitoring window to

    monitor all the NEs alarms at real-time.

    2. Query the NEs current or history alarm messages in the EMS client operation window.

    Inspection Criteria 1. The NE has no alarm message at present.

    2. The NE has no unacknowledged history alarm.

    Troubleshooting 1. To troubleshoot fault of EMS connection, refer to the Handling EMS

    Connection Fault section in Chapter 5.

    2. To handle alarm messages, refer to the maintenance manual of the SDH equipment.

    Monitoring Performance Purpose In the ZXONM E300 EMS, the user can monitor the performance message of the NE; thus keep aware of the current service performance of the NE, and detect/handle the performance message of the NE in time.

    Operations In the client operation window of the EMS software, query the latest 15 minutes and 24 hours performance data of the NE.

  • Chapter 2 - Routine Maintenance

    Confidential and Proprietary Information of ZTE CORPORATION 7

    Inspection Criteria 1. For digital performance, the NE has no over-threshold event.

    2. For analog performance, the NEs performance should comply with corresponding index.

    Troubleshooting To handle performance messages, refer to the maintenance manual of the SDH equipment.

    Querying System Configuration Purpose In the ZXONM E300 EMS software, user can query the configuration information of the network through the configuration menus. The result of this query is the network configuration in the EMS software, not necessarily the actual configuration of the NE. To obtain the actual configuration and current working status of the NE, user needs to perform the operations such as automatically uploading data, backing up NE data, and comparing the EMS database and the NE database.

    Operations 1. In the client operation window of the EMS software, select an NE, and

    then click the System -> NCP Data Management -> Auto Upload and Compare menu item. Then the EMS will automatically issue the upload and compare command according to the period set by the user. Or

    2. In the client operation window of the EMS software, select an NE, and then click the System -> NCP Data Management -> DB Upload and Compare menu item. Then the EMS will issue the upload and compare command for one time.

    Inspection Criteria The current network/NE configurations agree with the actual networking.

    Troubleshooting If the current service meets the user requirements, the network

    configuration data should be corrected to comply with the actual networking.

    If the current service does not meet the user requirements, the network configuration data should be corrected to comply with the user requirements.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    8 Confidential and Proprietary Information of ZTE CORPORATION

    Querying User Operation Log Purpose The ZXONM E300 EMS software can record all the operations performed by the user into the user operation log. It is one of the security guarantees. Query the user operation log periodically; and check whether there is any illegal access and any improper operation that affects the system running.

    Operations 1. In the client operation window of the EMS software, click the System

    -> Log Management menu item to open the Log Administration window.

    2. Click the Operation Log tab to enter the Operation Log page.

    3. Enter the query conditions and then click the Query button to query the user operation log.

    Inspection Criteria There is no illegal login. There is no user operation that affects system operation or service

    functions.

    Troubleshooting When any illegal user or operation is found, use the user management function of the EMS software to check the user identity and the authority settings, and change the user password in time.

    Printing Report Purpose With the printing function of the EMS software, user can print out the network configuration, user operation log, equipment performance and alarm messages. The printed reports can serve as the basis for operation/maintenance records and network analysis.

    Operations 1. In Windows operating system, if the Report Server is not started up,

    click the Windows menu of Start -> Programs -> ZXONM E300 -> Report Server to start up it.

  • Chapter 2 - Routine Maintenance

    Confidential and Proprietary Information of ZTE CORPORATION 9

    2. In the client operation window of the EMS software, select an NE. Click the submenu items in the Report menu item to query the corresponding dialog box.

    3. Enter the query conditions and then click the Print button to print the report.

    Inspection Criteria None

    Troubleshooting 1. Check whether the Report Server is started up on the client computer.

    2. In Windows operating system, if the Report Server is not started up, click the Windows menu of Start -> Programs -> ZXONM E300 -> Report Server to start up it.

    Saving/Printing Alarm/Performance Messages Purpose Use the save and print function of the EMS to save the queried alarm/performance data as a txt file onto the local computer, or to print out the data as a report. Keep the file or report for future maintenance.

    Operations 1. In Windows operating system, if the Report Server is not started up,

    click the Windows menu of Start -> Programs -> ZXONM E300 -> Report Server to start up it.

    2. Query the alarm or performance in the Alarm Management or Performance Management dialog box.

    3. Click the button to open the Unitrans Report window.

    4. To save the queried alarm or performance messages, click the File -> Save As menu item.

    5. To print the queried alarm or performance messages, click the File -> Print menu item

    Inspection Criteria None

  • ZXONM E300 (V3.19R2) Maintenance Manual

    10 Confidential and Proprietary Information of ZTE CORPORATION

    Troubleshooting 1. Check whether the Report Server is started up on the client computer.

    2. In Windows operating system, if the Report Server is not started up, click the Windows menu of Start -> Programs -> ZXONM E300 -> Report Server to start up it.

    Backing up Data Purpose In the ZXONM E300 EMS software, database backup is primarily used to copy and save the data of the Manager database. In the network operation and maintenance, it is necessary to backup the system data often so that the network data can be restored quickly in the case of network fault or EMS data loss.

    Note: It is recommended to save the backup data in a mobile storage device lest backup loss in the case of hard disk fault of the EMS host.

    Operations There are two methods to back up the data:

    Use the DBMAN tool to back up the data including the history data. 1. Run the dbman.exe file in the directory of

    EMS_installation_directory\dbman.

    2. In the DBMAN main window, enter 4 which represents for Backup and Restore.

    3. In the Backup and Restore window, enter 1 which represents for Backup database.

    4. In the Backup database window, enter 1 which represents for Backup directory.

    5. Input the directory where the data to be backed up.

    6. Enter 4 which represents for Backup to start backing up the data.

    Use the EMS software to back up the current data only with no history data.

    1. In the client operation window of the EMS software, click the System -> System Data Management -> DB Backup or Restore menu item.

  • Chapter 2 - Routine Maintenance

    Confidential and Proprietary Information of ZTE CORPORATION 11

    2. In the Database Backup/Restore dialog box, click the DB Backup/Restore tab.

    3. Select the Backup option button. Input or select the backup file directory, and input the backup file folder name.

    4. Click the Backup DB button to start backing up the data.

    Inspection Criteria A folder with the same name as the backup file name shall exist in the backup file directory.

    Troubleshooting If the backup files do not exist, back up the data again.

    Restoring Data Purpose In the case of network upgrade, network fault, or EMS data loss, restore the data that had been backed up.

    Warning: The restore of ZXONM E300 data would overwrite all the current data. Therefore, back up current data before restoring the data.

    Operations There are two methods to restore the data:

    Use the DBMAN tool to restore the data including the history data. 1. Run the dbman.exe file in the directory of

    EMS_installation_directory\dbman.

    2. In the DBMAN main window, enter 4 which represents for Backup and Restore.

    3. In the Backup and Restore window, enter 2 which represents for Restore database.

    4. In the Restore database window, enter 1 which represents for Backup directory.

    5. Input the directory where the data is backed up.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    12 Confidential and Proprietary Information of ZTE CORPORATION

    6. Enter 4 which represents for Restore to enter the data restore confirmation window. Then, start to restore the data according to the system prompt information.

    Use the EMS software to restore the data, which only include the data when the backup operation was performed and no history data.

    1. In the client operation window of the EMS software, click the System -> System Data Management -> DB Backup or Restore menu item.

    2. In the Database Backup/Restore dialog box, click the DB Backup/Restore tab.

    3. Select the Restore option button. Input or select the backup file directory, and input the backup file folder name.

    4. Click the Restore DB button to start restoring the data.

    Inspection Criteria None

    Troubleshooting If the EMS cannot work normally after the data restore operation, the data used for data restore are of later version than the current EMS. Upgrade the current EMS.

  • Confidential and Proprietary Information of ZTE CORPORATION 13

    C h a p t e r 3

    Maintenance of Operating System

    In this chapter, you will learn about: Running environment requirements of ZXONM E300 Installation and configuration of EMS in Unix operating system Installation and configuration of EMS in Windows operating system Frequently asked questions and the answers

    Running Environment Requirements of ZXONM E300 Before installing the ZXONM E300, determine configuration requirements of the EMS based on actual networking conditions, check configurations of EMS computer based on software and hardware requirements, and determine the software installation items.

    Unix Platform Hardware Requirements Table 4 describes the hardware requirements based on Unix platform.

    T AB L E 4 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: 2CPU) Mini computer

    HP RP3440 (maximum: 4CPU) Mini computer

    Host

    Sun Blade 150 Workstation

  • ZXONM E300 (V3.19R2) Maintenance Manual

    14 Confidential and Proprietary Information of ZTE CORPORATION

    Hardware Item Requirement

    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 < 200: recommend to use HP B2600, HP C8000, Sun Blade 150. The hard disk should be no less than 30 GB, and memory should be no less than 1 GB.

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

    Software Requirements Table 5 describes the software requirements based on Unix platform.

    T AB L E 5 S O F T W A R E R E Q U I R E M E N T S B AS E D O N U N I X P L AT F O R M

    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 GB

    Windows Platform Hardware Requirements Table 6 describes the minimum hardware requirements based on Windows.

    T AB L E 6 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 1024768

    Color Enhanced color (16 bits)

  • Chapter 3 - Maintenance of Operating System

    Confidential and Proprietary Information of ZTE CORPORATION 15

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

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

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

    T AB L E 7 M I N I M U M R E Q U I R E M E N T S F O R HO 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 1 G 30 G 512 M

    100 to 300 P4 2 G 60 G 1 G

    300 to 500 P4 2.5 G 80 G 2 G

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

    T AB L E 8 S O F T 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

    Software Item Requirement

    Operating system Windows 2000 or above (the GUI, Manager, and Database should be installed on the same computer)

    Database SYBASE [Note] or SQL Server

    Available space of hard disk No less than 9 GB

    Note: The ZXONM E300 which uses SYBASE as its database must be installed on Windows 2000, and Windows XP is not supported.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    16 Confidential and Proprietary Information of ZTE CORPORATION

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

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

    Unix Platform in Chapter 3.

    2. Install the Unix operating system according to manuals about Unix.

    If the host is HP workstation or mini computer, install the HP-UX 11.0 operating system

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

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

    Configuring Solaris Platform 1. Execute the following command to set the kernel parameter in the file

    named etc/system.

    set shmsys:shminfo-shmmax=209715200 2. Execute the following commands to reboot the computer.

    cd / shutdown i6 g0 -y

    Configuring HP-UX Platform 1. If the operating system is HP-UX 11.0, make sure the available space

    of the directory /tmp is no less than 1 GB. If the space is less than 1 GB, follow the steps below to extend it.

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

    #shutdown -y 0 ii. Log in as the ROOT user and execute the following command under

    the root directory prompt to load all the file systems.

    #mount -a iii. Execute the #bdf command to check if the directory named /tmp

    has been loaded successfully. If yes, record the logical volume name of the directory.

  • Chapter 3 - Maintenance of Operating System

    Confidential and Proprietary Information of ZTE CORPORATION 17

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

    iv. Execute the following commands to extend the directory named /tmp. #umount /tmp //Unmount the directory /tmp. This step is necessary before changing its size

    #lvextend -L 1024 /dev/vg00/lvol4 //Extend the logical volume /dev/vg00/lvol4 that corresponds to the /tmp file system to 1 GB (1024 MB). #extendfs /dev/vg00/lvol4 //Extend the logical volume. For the vxfs file system, execute the command extendfs -F vxfs /dev/vg00/lvol4. #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 the ROOT user. ii. Select Kernel configuration area in the menu of sam window. iii. Set the kernel parameters as listed in Table 9.

    T AB L E 9 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 0XC0000000

    maxssiz_64bit 0X4000000

    maxtsiz_64bit 0x40000000

    maxdsiz 0XC0000000

    maxssiz 0X4000000

    maxtsiz 0x40000000

    shmmax 0x80000000

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

    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.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    18 Confidential and Proprietary Information of ZTE CORPORATION

    Pay attention to the following parameters

    shmseg The default value is 120, indicating the maximum number of shared memory sections that can be associated with a process at any time.

    maxuprc Maximum number of processes that can be run simultaneously by a user.

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

    ninode Maximum number of inodes that can be opened by the kernel. Each file has an inode. The ninode value is generally greater than the nfile value.

    iv. Follow the steps below to re-create HP-UX kernel in 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.

    Installing Patch Install patches after installing the operating system. For different Unix platforms, the patches to be installed and the operations are different.

    Solaris Platform The patch is in os_patch/8_Recommended.zip of the installation CD.

    To install the patch

    1. Execute the following command to extract the 8_Recommended.zip file to the directory 8_Recommended.

    unzip 8_Recommended.zip 2. Enter the directory 8_Recommended and run the install_cluster

    program. This process may take two hours.

    3. Reboot the computer.

    HP-UX Platform For HP-UX 11.00, make sure to install QPK1100 in the HP-UX Support

    Plus CD coming with the HP-UX installation CD. The installation commands are as follows:

    # mount /dev/dsk/c0t0d0/cdrom # swinstall -s /cdrom/QPK1100

    If the version of HP-UX is earlier than June 2001, install patches XSWGR1100 and XSWHWCR1100 of year 2000 in the HP-UX Support Plus CD. The installation commands are as follows:

    # mount /dev/dsk/c0t0d0/cdrom # swinstall -s /cdrom/XSWGR1100 \

  • Chapter 3 - Maintenance of Operating System

    Confidential and Proprietary Information of ZTE CORPORATION 19

    -xpatch_match_target=true \ -x autoreboot=true # swinstall -s /cdrom/XSWHWCR1100 \ -xpatch_match_target=true \ -x autoreboot=true

    Table 10 lists other patches to be installed.

    T AB L E 10 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 -

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

    PHSS_22217 GUI -

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

    Download the patches from the website of http://itrc.hp.com, and then install them.

    Install from the ZXONM E300 installation CD. The patches are in the patch directory os_patch of the CD, with file suffix as tar. Extract the .tar file first before installation. The operations are as follows:

    i. Execute the following commands to extract the .tar file to directory /tmp.

    # mount /dev/dsk/c0t0d0/cdrom # cd /tmp # tar xvf /cdrom/patch/hppatch.tar

    ii. Taking the patch PHNE_24100 as an example, execute the following commands to install it. Other patches are installed according to this operation.

    # cd /tmp/patch # sh PHNE_24100 # swinstall -s /tmp/patch/PHNE_24100.depot

  • ZXONM E300 (V3.19R2) Maintenance Manual

    20 Confidential and Proprietary Information of ZTE CORPORATION

    Configuring Database on HP-UX Platform

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

    Creating Database Storage Devices To create database storage devices

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

    Log into the system as the ROOT user and execute the following command:

    # vgdisplay The following information will be displayed:

    --- Volume groups --- VG Name /dev VG Write Access read/write VG Status available Max LV 255 Cur LV 10 Open LV 10 Max PV 16 Cur PV 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)

  • Chapter 3 - Maintenance of Operating System

    Confidential and Proprietary Information of ZTE CORPORATION 21

    2. Create database storage devices.

    i. Execute the following command to create a database data storage device at the size of 600 M and with sybdat as the logical volume name and vg00 as the volume group:

    # lvcreate -L 600 -n sybdat vg00 ii. Execute the following command to create a database log storage

    devices at the size of 800 M and with syblog as the logical volume name and vg00 as the volume group:

    # lvcreate -L 800 -n syblog vg00 3. The database storage devices are created completely.

    Creating Asynchronous Devices By default, the HP-UX does not have asynchronous devices. Therefore, it is necessary to create asynchronous devices.

    To create asynchronous devices

    1. Run the sam program as the ROOT user.

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

    3. Select asyncdsk and then perform the following operations to re-create the HP-UX kernel.

    i. Select sam -> Actions -> Add Driver to Kernel to create a new HP-UX kernel.

    ii. Select sam -> Actions -> Process New Kernel, and then select Move kernel into place and shutdown/reboot system now or Do not move kernel into place; do not shutdown/reboot now in the popup dialog box.

    4. Execute the following command to reboot the system and load the asynchronous I/O driver:

    # /sbin/shutdown -r 0 5. Log into the system as the ROOT user, create the device file

    /dev/async with 101 as the host device number, and execute the following command to ensure the authority of the file is correct.

    # ls -l /dev/async The result may be as follows:

    crw-rw---- 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 then execute the following command to re-create it:

    # /sbin/mknod /dev/async c 101 0x4 6. Create sybase group and user for the device:

    # /sbin/mknod /dev/async c 101 0x4 # /usr/bin/chown sybase:sybase /dev/async # /usr/bin/chmod 660 /dev/async

  • ZXONM E300 (V3.19R2) Maintenance Manual

    22 Confidential and Proprietary Information of ZTE CORPORATION

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

    Install the Windows operating system according to its related manuals.

    Caution: The ZXONM E300 which uses SYBASE as its database must be installed on Windows 2000 Server, and Windows XP is not supported.

    After installation, it is required to log into the operating system as the super user to install and operate the ZXONM E300 EMS.

    FAQ In the Unix operating system, various problems may come up. Sometimes, the system administrator has to retrieve the loss caused by serious accident.

    This section introduces some emergency cases and the solutions in the Unix operating system.

    What are emergency startup floppy disks? How to make them? The emergency startup floppy disks are very important tools for system administration. They include a system boot floppy disk and a root file system floppy disk.

    When the system is working normally, a qualified administrator should make an emergency startup floppy disk for Unix system. Use the emergency startup floppy disk to restore the system when the system suffers disastrous damage and would not respond when being restarted. The emergency startup floppy disk can restore the damaged root file system, so that the operating system needs no reinstallation.

    To make the emergency floppy disks

    1. Startup the operating system in the single-user maintenance mode.

    2. Format the two floppy disks that are to be used for the emergency startup floppy disks.

    3. Make two emergency startup floppy disks: a system boot floppy disk and a root file system floppy disk.

  • Chapter 3 - Maintenance of Operating System

    Confidential and Proprietary Information of ZTE CORPORATION 23

    Warning: Each computer has its own emergency startup floppy disks which cannot be used by another computer; since the emergency startup floppy disks would not work on another computer, and evern worse, they may bring severer damage to another computer.

    What to do when forgetting the super user password? First, the system administrator needs to use the emergency startup floppy disks to start up the operating system. Then install the root file system on the hard disk to the /mnt directory. After that, edit corresponding files to delete the password of the root account.

    The detailed steps are as follows:

    1. Insert the system boot disk into the floppy drive.

    2. Power on the computer.

    3. Insert the root file system disk into the floppy drive as per the system prompt.

    4. After system has started up, log into it as a super user (administrator).

    5. Execute the following command to install the root file system on the hard disk to the /mnt directory.

    # mount /dev/hd0root /mnt

    Then the /etc/passwd file changes its location to /mnt/etc/passwd.

    6. Follow the steps below to edit the corresponding files using the vi editor and delete the password of the root account.

    For an operating system configured with lower security level

    Need to edit the /mnt/etc/passwd file in which each line has the format Loginname:Password:UID:GID:Userinformation:Home:Shell. Delete the password information in the second domain of root account.

    For example:

    Change the line of root:Ctsf6P/L/nav6,..1k:0:1:Superuser:/: into the following line:

    root:,..1k:0:1:Superuser:/:

    For an operating system configured with higher security level

    Need to edit the /mnt/etc/shadow file. The root account information in the /mnt/etc/passwd file is:

    root:x:0:1:Superuser:/: adm:x:4:4:System accounting:/usr/adm:

    doug:x:200:50:Dougs account:/usr/doug:/bin/sh

  • ZXONM E300 (V3.19R2) Maintenance Manual

    24 Confidential and Proprietary Information of ZTE CORPORATION

    The passwords of all the accounts are saved in the /mnt/etc/shadow file. For example:

    root:Ctsf6P/L/nav6:9881:0:0

    adm:*:9926:0:0 doug:oTDTuBctxUBtc:9926::

    Delete the password information in the second domain of root account.

    For example, the root:Ctsf6P/L/nav6:9881:0:0 is changed to root::9881:0:0 &gt

    Warning: Be careful not to delete other information by accident when editing a file in the hard disk file system.

    How to retrieve lost files? If user deletes important files by accident, there is no command in Unix to retrieve the files directly. Follow the steps below to retrieve the lost files:

    1. Copy the corresponding files from the emergency startup floppy disk into the hard disk file system.

    2. If the deleted file is not in the emergency startup floppy disk, choose one of the following methods:

    Copy the file from another system.

    Retrieve the file from the backup system.

    3. If none of the above methods can retrieve the lost files, the user would have to recreate the file.

  • Confidential and Proprietary Information of ZTE CORPORATION 25

    C h a p t e r 4

    EMS Installation and Upgrade

    In this chapter, you will learn about: ZXONM E300 installation flow Upgrade of ZXONM E300 Parameter settings of ZXONM E300

    Installation Flow Figure 1 shows the installation flowchart of the ZXONM E300.

    F I G U R E 1 IN S T AL L AT I O N FL O W C H AR T O F ZXONM E300

    Install operating system

    InstallZXONM E300

    Confirm installation components

    Install corresponding components

    Configure the parameters

    Typical installation

    Customized installation

    Configure the parameters

    Prepare for ZXONM E300

    installation

    The ZXONM E300 EMS can be installed on Unix or Windows platform based on networking requirements. For installation details, refer to the Unitrans

  • ZXONM E300 (V3.19R2) Maintenance Manual

    26 Confidential and Proprietary Information of ZTE CORPORATION

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

    Upgrading ZXONM E400 to ZXONM E300 Preparing for Upgrade This section takes the network shown in Figure 2 as an example to illustrate how to prepare for upgrading ZXONM E400 to ZXONM E300.

    F I G U R E 2 N E T W O R K E X AM P L E

    NE ECC link IP link

    NE A NE B NE C

    EMS

    In Figure 2, ZXONM E400 uses NE A as the access NE. After upgrade, it is required that ZXONM E300 also uses NE A as the access NE.

    To prepare for upgrading ZXONM E400 to ZXONM E300

    1. Install the standby ZXONM E400 on the computer which is connected with NE B.

    2. Install the ZXONM E300 on the EMS computer which is connected with NE A.

    3. Make sure that the free space on the hard disk of ZXONM E300 computer is no less than 2GB.

    4. Make sure that the database server of ZXONM E300 is running in the TCP/IP mode.

  • Chapter 4 - EMS Installation and Upgrade

    Confidential and Proprietary Information of ZTE CORPORATION 27

    5. If the ZXONM E300 computer has multiple IP addresses, make sure that the IP address of the ZXONM E300 database server is the IP address in DCN (Data Communications Network).

    6. Make sure that the ZXONM E300 configuration file named $INSTALL/Sybase/ini/sql.ini has the following content:

    [SQL_ZXONM]

    master=TCP,*.*.*.*,4001

    query=TCP,*.*.*.*,4001

    //*.*.*.* is the IP address of ZXONM E300 computer.

    7. Restart the ZXONM E300.

    8. Make sure that the standby ZXONM E400 can manage the network consisting of ZXWM-32(V1) NEs with NE B as the access NE, lest that the NEs cannot be managed for a long time once the upgrade fails.

    9. Prepare the Agent program of the ZXWM-32(V1) NE which is to be upgraded.

    10. Make sure that both the ZXONM E400 and the ZXONM E300 can ping through NE A.

    Caution: For ZXWM-32(V1) NE, the performance data during the upgrade procedure may be lost. Therefore, make sufficient preparations for the upgrade and make the upgrade procedure as short as possible.

    Upgrade Operations Follow the steps below to upgrade ZXONM E400 to ZXONM E300:

    1. Check the network of ZXWM-32(V1) NEs using the standby ZXONM E400. Make sure that the optical powers of all main optical paths are normal, and no OTU board reports alarm.

    2. Run the data transfer tool on the ZXONM E400 computer to transfer the data of active ZXONM E400 onto ZXONM E300.

    Note:

    The data transferred include the configuration data and the history data, thus ensures that these data would not get lost.

    The length of time spent on data transfer varies with the amount of history data.

    Make sure that the ZXONM E300 employs the correct ManagerID for data transfer.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    28 Confidential and Proprietary Information of ZTE CORPORATION

    3. Restart ZXONM E300 upon completion of data transfer. Once ZXONM E300 is started up normally, set the NE A to be the access NE in ZXONM E300.

    4. Now, ZXONM E300 should be able to display the data of ZXWM-32(V1) NEs. However, it cannot manage these NEs yet.

    5. Upgrade the program of NE A to V1.40 using ZXONM E400. NE A will reset upon successful upgrade, and ZXONM E400 cannot manage NE A any more. Instead, ZXONM E300 can manage NE A. And it can manage the whole ZXWM-32(V1) network before long.

    6. Use ZXONM E300 to upgrade the programs of all the other ZXWM-32(V1) NEs to V1.40. After this, the standby ZXONM E400 cannot manage the ZXWM-32(V1) NEs any more. Instead, the ZXONM E300 can manage the whole network of ZXWM-32(V1).

    7. Use the ZXONM E300 to download database for each ZXWM-32(V1) NE, so as to synchronize the NE data with ZXONM E300 data.

    Caution: If a ZXWM-32(V1) NE is connected with ZXONM E300 through DCN, it is forbidden to download database to this NE.

    Because, in order to use ZXONM E300 to download database to a NE wich accesses the DCN, it is necessary to set the gateway information on this NE via a serial port. Otherwise, the routes on DCN will be lost and the monitoring on the NE will be interreupted. However, current ZXONM E300 cannot set gateway on ZXWM-32(V1) NE.

    8. Observe the ZXWM-32(V1) NEs in ZXONM E300 for about four hours. If no problem comes up, the upgrade had succeeded.

    Upgrading ZXONM E300

    Caution: If both the NCP program and the ZXONM E300 need to be upgraded, upgrade the NCP program in current ZXONM E300 first. After that, upgrade the ZXONM E300.

    Note: ZXMP S380/S390/S385/S330/S325/S200 equipments all support the remote online upgrade of NCP program, which makes the NCP program upgrade very convenient. The upgrade operations of NCP program vary with equipment type. For detailed operations, refer to the Unitrans ZXONM E300 (V3.19R2) Unified EMS/SNMS of Optical Network Operation Manual (Volume IV) Agent Configurations.

  • Chapter 4 - EMS Installation and Upgrade

    Confidential and Proprietary Information of ZTE CORPORATION 29

    Applicable Scope The upgrade operations of ZXONM E300 are applicable to:

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

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

    Preparing for Upgrade 1. Make sure that the ZXONM E300 is working normally. Remove any

    fault before upgrading.

    2. Make sure that the free space on EMS computers hard disk is enough. In Windows operating system, at least 4 GB free space is required; in Unix operating system at least 5 GB free space is required, and the vgdisplay command can be executed to check the free space.

    3. Make sure that the free space under the root directory is at least 80 MB. In Unix operating system. The df-k command can be used to check free space of a file system.

    4. Make sure that no NE is in the switching state. Otherwise, find out the reason for the switching. Do not perform the upgrade until the switching disappears.

    5. Make sure that the version of ZXONM E300 installation software is correct and is compliant with the NEs NCP program.

    6. Make a copy of the old version installation software of ZXONM E300; so that once the upgrade fails, the EMS can be recovered to the old version.

    7. To upgrade ZXONM E300 in Unix, check if the patch of Unix system is correct. For patch requirement, refer to the Installing Patch section in Chapter 3.

    Upgrading EMS in Unix Suppose the original EMS was installed under the /opt/Unitrans directory.

    Note: It is recommended to back up the /opt directory.

    1. Back up the following critical configuration files:

    /opt/unitrans/gui/etc/mgrcfg.ini

    /opt/unitrans/db/cfg

    /opt/unitrans/manager/cfg

  • ZXONM E300 (V3.19R2) Maintenance Manual

    30 Confidential and Proprietary Information of ZTE CORPORATION

    For example, to back up the configuration files to the /opt/cfg_bak directory, execute the following commands:

    #cd /opt #mkdir cfg_bak #mkdir cfg_bak/db #mkdir cfg_bak/manager #cp /opt/unitrans/gui/etc/mgrcfg.ini cfg_bak #cp /opt/unitrans/db/cfg cfg_bak/db #cp /opt/unitrans/manager/cfg cfg_bak/manager

    Warning: The backup files cannot be saved under the EMS installation directory.

    2. Map the CD ROM file system

    i. Log into the Unix workstation as the root user. Insert the installation CD into the CD ROM.

    ii. Execute the following commands to search for the device name of the CD ROM, as shown in Figure 3.

    #cd / #ioscan -fnkC disk

    F I G U R E 3 S E AR C H I N G F O R DE V I C E N AM E O F CD ROM

    The result shows that the device name of CD ROM is /dev/dsk/c0t0d0.

    iii. Execute the #mkdir /cdrom to create the cdrom directory. iv. Execute the # mount -ocdcase /dev/dsk/c0t0d0 /cdrom

    command to mount the CD ROM to the system.

    3. Choose one of the following three methods to back up the database:

    Use the backup.sh script

    Use the DBMAN tool

    Use the database backup function provided by EMS

  • Chapter 4 - EMS Installation and Upgrade

    Confidential and Proprietary Information of ZTE CORPORATION 31

    Note: To backup not only the current data but also the history data, use the DBMAN tool.

    To backup database using the backup.sh script

    i. Execute the following commands:

    #cd /opt/unitrans/db #vi cfg //Check the database server name. Suppose it is hp9ase. Check if it is correct in the cfg file. Then exit vi. #./backup.sh hp9ase //Back up the data to the /opt/unitrans/db/backup directory.

    ii. Copy the /opt/unitrans/db/backup directory to a directory which is not used for EMS installation, such as /opt/data_bak directory.

    iii. Execute the following commands:

    #cd /opt #mkdir data_bak #cp -R /opt/unitrans/db/backup data_bak

    Note: The database backed up using this method cannot be used for the new EMS. It is only a preventive measure, so that once the EMS upgrade fails, the old data can be restored by running the restore.sh script after the old EMS has been restored.

    To backup database using the DBMAN tool

    i. Run the DBMAN tool. Suppose DBMAN is located under the /opt/unitrans/db directory, execute the following commands to run DBMAN:

    #cd /opt/unitrans/db/dbman #export LANG=C #./dbman The DBMAN interface may vary with the EMS version. Taking the ZXONM E300 V3.19R2 in Unix as example, the DBMAN main interface is shown in Figure 4.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    32 Confidential and Proprietary Information of ZTE CORPORATION

    F I G U R E 4 DBM AN M AI N I N T E R F AC E I N U N I X

    ii. Enter 4 which represents for Backup and Restore in Figure 4 to enter the BACKUP AND RESTORE interface, as shown in Figure 5.

    F I G U R E 5 BACKUP AND RESTORE I N T E R F AC E O F DBM AN I N U N I X

    iii. Enter 1 which represents for Backup database to enter the BACKUP DATABASE interface, as shown in Figure 6.

  • Chapter 4 - EMS Installation and Upgrade

    Confidential and Proprietary Information of ZTE CORPORATION 33

    F I G U R E 6 BACKUP DAT AB ASE I N T E R F AC E O F DBM AN I N U N I X

    iv. Enter 1 which represents for Backup directory. Then input the database backup directory, e.g. /opt/data_bak. Press ENTER.

    v. In Figure 6, enter 4 which represents for Backup to back up the database.

    vi. Exit DBMAN once database backup is completed.

    Note: For operation details of DBMAN, refer to Appendix A DBMAN Operations.

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

    To backup database using the EMS database backup function

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

    ii. In the Database Backup/Restore dialog box, click the DB Backup/Restore tab.

    iii. Select the Backup option button. Input or select the backup file directory, and input the backup file folder name.

    iv. Click the Backup DB button to start backing up the data.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    34 Confidential and Proprietary Information of ZTE CORPORATION

    4. Remove the old version EMS

    i. Execute the following commands:

    #cd /opt/unitrans #./unistall

    ii. Check if the /opt/unitrans directory is empty. If not, follow the steps below to delete it manually:

    #ps -ef|grep dataserver //Obtain the dataserver process ID. Suppose it is 2002. #kill -9 2002 //Kill the dataserver process #cd /opt #rm -rf /opt/unitrans //Delete the EMS installation directory.

    5. Install the new version ZXONM E300 in Unix according to the Unitrans ZXONM E300 (V3.19R2) Unified EMS/SNMS of Optical Network Installation Manual.

    6. Choose one of the following two methods to restore the data.

    To restore data using the EMS data restore function

    To restore data using the DBMAN tool

    To restore data using the DBMAN tool

    i. Run the DBMAN tool. Suppose DBMAN is located under the /opt/unitrans/db directory, execute the following commands to run DBMAN:

    #cd /opt/unitrans/db/dbman #export LANG=C #./dbman The DBMAN interface may vary with the EMS version. Taking the ZXONM E300 V3.19R2 in Unix as example, the DBMAN main interface is shown in Figure 4.

    ii. Enter 4 which represents for Backup and Restore in Figure 4 to enter the BACKUP AND RESTORE interface, as shown in Figure 5.

    iii. Enter 2 which represents for Restore database to enter the RESTORE DATABASE interface, as shown in Figure 7.

  • Chapter 4 - EMS Installation and Upgrade

    Confidential and Proprietary Information of ZTE CORPORATION 35

    F I G U R E 7 RESTORE DATAB ASE I N T E R F AC E O F DBMAN I N U N I X (1 )

    iv. Enter 1 which represents for Backup directory. Then input the database backup directory, e.g. /opt/0603. Press ENTER, then the RESTORE DATABASE interface turns into Figure 8.

    F I G U R E 8 RESTORE DATAB ASE I N T E R F AC E O F DBMAN I N U N I X (2 )

    v. In Figure 8, enter 4 which represents for Restore to start to restore the data. After restoring the data successfully, the interface will prompt database restore successfully.

  • ZXONM E300 (V3.19R2) Maintenance Manual

    36 Confidential and Proprietary Information of ZTE CORPORATION

    To restore data using the EMS data restore function

    i. In the client operation window of the EMS software, click the System -> System Data Management -> DB Backup or Restore menu item.

    ii. In the Database Backup/Restore dialog box, click the DB Backup/Restore tab.

    iii. Select the Restore option button. Input or select the backup file directory, and input the backup file folder name.

    iv. Click the Restore DB button to start restoring the data.

    7. Execute the following commands to restore the configuration files

    #cd /opt/cfg_bak #cp mgrcfg.ini /opt/unitrans/gui/etc #cp cfg /opt/unitrans/db #cp cfg /opt/unitrans/manager

    8. Execute the following commands to set the opt/unitrans/gui/etc/test file to be writable.

    #cd /opt/unitrans/gui/etc #chmod +w test

    9. Execute the following commands to restart the workstation.

    #cd / #shutdown -ry 0

    10. Follow the steps below to download the NE database using the new ZXONM E300.

    Note: If the NCP database has been cleared when upgrading the NCP board, the NE database must be downloaded.

    i. Start up the ZXONM E300 of new version.

    ii. Once the EMS get able to manage NEs, select an NE, then click the System -> NCP Data Management -> DB Download menu item.

    iii. Select the Select All The Files check box.

    iv. Click the Apply button to start downloading the NE database.

    Upgrading EMS in Windows In Windows operating system, suppose the original EMS was installed under the d:\zte\zxonm e300 directory. Follow the steps below to upgrade the EMS.

  • Chapter 4 - EMS Installation and Upgrade

    Confidential and Proprietary Information of ZTE CORPORATION 37

    1. Back up the critical configuration files including d:\zte\zxonm e300\gui\etc\mgrcfg.ini, d:\zte\zxonm e300\db\cfg, d:\zte\zxonm e300\manager\cfg. Suppose these files are backed up under the corresponding subdirectories of the d:\zte\e300_bak directory.

    2. Choose one of the following two methods to back up the EMS data:

    Use the DBMAN tool

    Use the EMS data backup function

    To back up the EMS data using the DBMAN tool

    i. Start up the ZXONM E300 server to start up the database server.

    ii. Double-click the dbman.bat file to open the DBMAN main interface shown in Figure 9.

    F I G U R E 9 DBM AN M AI N I N T E R F AC E I N W I N D O W S

    iii. Refer to the corresponding steps in the Upgrading EMS in Unix section for subsequent steps.

    To back up the EMS data using the EMS data backup function

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

    ii. In the Database Backup/Restore dialog box, click the DB Backup/Restore tab.

    iii. Select the Backup option button. Input or select the backup file directory, and input the backup file folder name.

    iv. Click the Backup DB button to start backing up the data.

    3. Follow the steps below to remove the old version EMS

  • ZXONM E300 (V3.19R2) Maintenance Manual

    38 Confidential and Proprietary Information of ZTE CORPORATION

    i. On the client computer, click the Start -> Settings -> Control Panel menu item.

    ii. Double-click the Add/Remove Programs icon to open the Add/Remove Programs window.

    iii. Select ZXONM_E300 in the currently installed program list. Then click the Change/Remove bu