OptiX ToolKit V1R4C01 User Guide (MML)

OptiX Toolkit V100R004C01
User Guide
Issue Date Part Number
01 2008-02-25 00413725
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Copyright Huawei Technologies Co., Ltd. 2008. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
OptiX Toolkit User Guide
Contents
Contents
About This Document.....................................................................................................................1 1 Product Description...................................................................................................................1-1
1.1 Application......................................................................................................................................................1-3 1.2 Features and Functions....................................................................................................................................1-4 1.3 Performance Index........................................................................................................................................1-10 1.4 System Architecture......................................................................................................................................1-10 1.5 Networking and Communication..................................................................................................................1-13
2 Installing and Starting the ToolKit........................................................................................2-1

2.1 Installation and Running Environment...........................................................................................................2-2 2.2 Installing the ToolKit On Windows................................................................................................................2-3 2.3 Starting the ToolKit on Windows...................................................................................................................2-4 2.4 Installing the ToolKit on UNIX......................................................................................................................2-4 2.5 Starting the ToolKit on UNIX.........................................................................................................................2-6
3 Basic Operations.........................................................................................................................3-1
3.1 GUI Description..............................................................................................................................................3-2 3.2 Buttons and GUI Components........................................................................................................................3-4 3.3 NE and Board Management............................................................................................................................3-6 3.3.1 Searching for NEs..................................................................................................................................3-6 3.3.2 Creating NEs..........................................................................................................................................3-7 3.3.3 Querying Boards....................................................................................................................................3-9 3.3.4 Adding Boards......................................................................................................................................3-10 3.3.5 Filter NE/Board....................................................................................................................................3-10 3.4 Login Management.......................................................................................................................................3-11 3.4.1 Logging in to an NE ............................................................................................................................3-12 3.4.2 Switching Login Users.........................................................................................................................3-13 3.4.3 Logging Out of an NE..........................................................................................................................3-14 3.5 Creating Subnet.............................................................................................................................................3-15 3.6 Setting FTP....................................................................................................................................................3-16 3.7 Setting the Activation Mode.........................................................................................................................3-16 3.8 Switching the ToolKit Server........................................................................................................................3-17 3.9 Browseing Logs.............................................................................................................................................3-18
4 Loading Software.......................................................................................................................4-1
Issue 01 (2008-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. i
Contents
4.1 Loading Board Software.................................................................................................................................4-5 4.2 Loading Software Package In Non-diffusion Mode........................................................................................4-7 4.3 Loading a Diffusion Software Package...........................................................................................................4-8 4.3.1 Creating a Diffusion Group....................................................................................................................4-9 4.3.2 Querying the Diffusion Relation..........................................................................................................4-10 4.3.3 Loading a Software Package in Diffusion Mode.................................................................................4-11 4.4 Loading the Simulation Software Package...................................................................................................4-13 4.4.1 Comparing Software Versions.............................................................................................................4-14 4.4.2 Database Backup Setting .....................................................................................................................4-14 4.4.3 Rollback Software Setting ...................................................................................................................4-15 4.4.4 Setting the Activation Order................................................................................................................4-16 4.4.5 Loading a Simulation Software Package to an NE..............................................................................4-18 4.4.6 Generating Upgrade Reports................................................................................................................4-20 4.5 Loading Board Patch Software.....................................................................................................................4-21 4.6 Loading an NE Level Patch Package............................................................................................................4-23
5 Managing the NE License File.................................................................................................5-1

5.1 Querying the NE License File.........................................................................................................................5-2 5.2 Backing Up the NE License File.....................................................................................................................5-2 5.3 Loading the NE License File...........................................................................................................................5-4
6 NE Data Backup and Restoration............................................................................................6-1

6.1 Backing Up Configuration Data......................................................................................................................6-3 6.2 Backing Up Database Package........................................................................................................................6-4 6.3 Backing Up Database Periodically..................................................................................................................6-6 6.4 Backing Up NE Security Logs........................................................................................................................6-8 6.5 Backing Up NE Operation Logs.....................................................................................................................6-9 6.6 Restoring Configuration Data.......................................................................................................................6-10 6.7 Restoring Database Package.........................................................................................................................6-11 6.8 Deleting an NE Database Manually..............................................................................................................6-14
7 FAQ...............................................................................................................................................7-1
7.1 ECC and IP over DCC....................................................................................................................................7-2 7.2 Setting the Access Path...................................................................................................................................7-5 7.3 About Backing Up Databases Periodically.....................................................................................................7-6 7.4 How to Activate the Boards in a Ring Network..............................................................................................7-7 7.5 How to Use the Gateway Resources Correctly...............................................................................................7-7 7.6 How to Handle the Failures That Occurs on a Small Number of the Boards When a Large Number of Data Are Transmitted in the Concurrent Load.....................................................................................................................7-7 7.7 Whether the Automatic Activation Mode Can Be Used in a Complex Network Upgrade.............................7-7
A Glossary.....................................................................................................................................A-1 B Acronyms and Abbreviations.................................................................................................B-1 Index.................................................................................................................................................i-1

ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2008-02-25)
Figures
Figures
Figure 1-1 ToolKit integrated with the T2000.....................................................................................................1-3 Figure 1-2 ToolKit independent of the T2000.....................................................................................................1-4 Figure 1-3 Common hardware connection of the T2000...................................................................................1-11 Figure 1-4 Hardware connection when the ToolKit is used independently.......................................................1-11 Figure 1-5 Software architecture when the ToolKit is integrated into the T2000..............................................1-12 Figure 1-6 Software architecture when the ToolKit is used independently.......................................................1-12 Figure 1-7 Networking diagram through the ECC protocol...............................................................................1-13 Figure 1-8 Networking diagram through the IP protocol...................................................................................1-14 Figure 1-9 Networking diagram through the OSI protocol................................................................................1-14 Figure 3-1 The Backup/Restore Database Package window............................................................................3-2 Figure 7-1 Selecting ECC protocol and accessing the ToolKit server.................................................................7-3 Figure 7-2 Selecting ECC protocol and accessing the FTP server.......................................................................7-4 Figure 7-3 Selecting IP over DCC protocol and accessing the FTP server..........................................................7-5
Issue 01 (2008-02-25)
iii
Tables
Tables
Table 1-1 Comparison between loading board software and loading simulation software package....................1-4 Table 1-2 Comparison between loading board patch and loading patch package................................................1-5 Table 1-3 Comparison between loading software package in non-diffusion mode and loading software package in diffusion mode.......................................................................................................................................................1-7 Table 2-1 Recommended configuration of an ordinary PC..................................................................................2-2 Table 2-2 Recommended configuration of a workstation....................................................................................2-2 Table 3-1 Window component description..........................................................................................................3-3 Table 4-1 Comparison between six ways of upgrading a network by using the ToolKit....................................4-1
Issue 01 (2008-02-25)
About This Document
About This Document

Purpose
This document provides guides for getting the reference information of the OptiX ToolKit installation and operation.
Related Versions
The following table lists the product versions related to this document. Product Name OptiX ToolKit Version V100R004C01
Intended Audience
The intended audience of this document are technical support engineers.
Organization
This document is organized as follows: Chapter Chapter 1 Product Description Description Describes the application, characteristics, performance, software architecture, networking and communication of the ToolKit. Describes how to install and start the ToolKit on the Windows or UNIX platform. Describes the basic operations of the ToolKit Describes how to load software by using the ToolKit.
1
Chapter 2 Installing and Starting the ToolKit Chapter 3 Basic Operations Chapter 4 Loading Software
Issue 01 (2008-02-25)
About This Document
Chapter Chapter 5 Backing up and Restoring NE Data Chapter 6 Managing NE License File Chapter 7 FAQ Appendix A Glossary Appendix B Acronyms and Abbreviations
Description Describes how to back up or restore data by using the ToolKit. Describes how to back up and load the NE License file by using the ToolKit. Describes methods of handling common problems of the ToolKit. Lists the glossary of this guide. Lists the acronyms and abbreviations of this guide.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows: Symbol Description Indicates a hazard with a high level of risk which, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Provides additional information to emphasize or supplement important points of the main text. Indicates a tip that may help you solve a problem or save you time.
General Conventions
Convention Times New Roman Boldface Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2008-02-25)
About This Document
Convention Italic Courier New
Description Book titles are in italics. Terminal display is in Courier New.
Command Conventions
Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] { x | y | ... } * Description The keywords of a command line are in boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars. One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected. Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.
GUI Conventions
Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Keyboard Operation
Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressingCtrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Issue 01 (2008-02-25)
About This Document
Mouse Operation
Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.
Updates in Issue 01 (2008-02-15) Based on Product Version V100R004C01

The updates of the document are as follows: Chapter 1 Product Description Descriptions on the function features of loading the patch package and loading the software package in the diffusion mode are added. The description of the license management function is deleted. Chapter 3 Basic Operations Descriptions of the icons and buttons are updated. Descriptions of locking and unlocking the ToolKit client are added. Chapter 4 Loading Software Descriptions on the operation procedures of loading the software package in the diffusion mode and loading the NE level patch package are added. Chapter 5 Backing up and Restoring NE Data Descriptions on the operation procedures of deleting the database manually are added. Others The section "License Management" is deleted.
Updates in Issue 01 (2007-08-15) Based on Product Version V100R003C01

The updates of the document are as follows: Chapter 1 Product Description Descriptions on the function features of loading the simulation software package, generating an upgrade report and managing the license are added. The description on the function of loading the NE software is integrated into that of loading the board software. Chapter 3 Basic Operations
4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2008-02-25)
About This Document
Descriptions of the user interface, icons and buttons are updated. Descriptions of the NE and board management, and the NE login management are added. Chapter 4 Loading Software The description on the operation procedures of loading the simulation software package is added. Descriptions on the operation procedures of loading the patch software, software package and board software are added. Chapter 6 Managing NE License File The description of managing the NE license file is added.
Issue 01 (2008-02-25)
1 Product Description
1
About This Chapter
Product Description
This chapter describes the orientation, functions, system structure, networking, and communications of the OptiX ToolKit. 1.1 Application The OptiX ToolKit (ToolKit) is a graphic tool that is developed for loading software and managing network data of Huawei optical network products. The ToolKit can be deployed independently or integrated with the OptiX iManager T2000 (T2000). You can use it to upgrade or downgrade the NE software of the equipment and board software. You can also use it to back up the configuration data or database files on NEs so that data can be restored after an NE becomes faulty. Compared to other loading tools, the ToolKit has some advantages such as graphic user interface (GUI), operation wizard and high upgrade efficiency. Besides, the ToolKit installation is simple. The ToolKit can be installed on UNIX (Solaris 8 or Solaris 10) or Windows (Windows 2003, Windows XP) operating system. 1.2 Features and Functions The OptiX ToolKit mainly supports two functions: software loading and data management. Software loading includes board software loading, patch software loading, software package loading and simulation software package loading. Data management includes log backup, configuration data backup and restoration, database package backup and restoration, and periodic database package backup. Besides, the ToolKit also provides functions such as the upgrade reporting, log viewing, FTP parameter setting, the Activation Mode setting, ToolKit server switching, and other basic operations to NEs or boards. 1.3 Performance Index The ToolKit limits both the access quantity of terminals and the NE management capability. 1.4 System Architecture The ToolKit uses the client/server architecture. The client provides you with an interactive interface for operating and managing NEs. You can load software, and back up or restore data on an NE inside the transport network at the client. The server is the interactive and processing center of information between the client and NEs, mainly providing the following two functions: one function is to respond to your operations at the client and send the operation command to the NE, and the other function is to receive and process information from the NE and send the processing result to the client. 1.5 Networking and Communication
Issue 01 (2008-02-25) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-1
There are three ways of networking between the ToolKit and NEs: ECC, IP and OSI networking.
1-2
Issue 01 (2008-02-25)
1.1 Application
The OptiX ToolKit (ToolKit) is a graphic tool that is developed for loading software and managing network data of Huawei optical network products. The ToolKit can be deployed independently or integrated with the OptiX iManager T2000 (T2000). You can use it to upgrade or downgrade the NE software of the equipment and board software. You can also use it to back up the configuration data or database files on NEs so that data can be restored after an NE becomes faulty. Compared to other loading tools, the ToolKit has some advantages such as graphic user interface (GUI), operation wizard and high upgrade efficiency. Besides, the ToolKit installation is simple. The ToolKit can be installed on UNIX (Solaris 8 or Solaris 10) or Windows (Windows 2003, Windows XP) operating system. The ToolKit is usually integrated with the T2000. See Figure 1-1. In the telecommunications management network (TMN) architecture, the T2000 is located between the NE layer and network layer as a subnetwork management system (SNMS), supporting all functions of the NE layer and some functions of the network layer. The T2000 can uniformly manage OptiX series optical transmission equipment from Huawei, such as SDH, SONET and WDM equipment. According to actual requirements, the ToolKit only integrates some functions to the T2000. When you use the ToolKit, all operations are performed on the T2000 Client, and the user interface of the ToolKit is invisible to you. Figure 1-1 ToolKit integrated with the T2000
The ToolKit also runs independently of the T2000. See Figure 1-2. In the case of independent deployment, the ToolKit has both the separate server and client, which can connects to each other through the network. All your operations are carried out on the client, while all commands are sent to NEs through the server.
Figure 1-2 ToolKit independent of the T2000
1.2 Features and Functions

The OptiX ToolKit mainly supports two functions: software loading and data management. Software loading includes board software loading, patch software loading, software package loading and simulation software package loading. Data management includes log backup, configuration data backup and restoration, database package backup and restoration, and periodic database package backup. Besides, the ToolKit also provides functions such as the upgrade reporting, log viewing, FTP parameter setting, the Activation Mode setting, ToolKit server switching, and other basic operations to NEs or boards.
Loading Board Software

When you need to upgrade one or more boards instead of the entire NE, you can use the loading board software function to increase the upgrade efficiency. Refer to Table 1-1. Table 1-1 Comparison between loading board software and loading simulation software package Loading Type Loading board software Definition Board software refers to the software corresponding to a board on an NE. Scenario When you need to upgrade one or more boards instead of the entire NE, you can use the loading board software function to improve the upgrade efficiency. Operation Method In the Board and Software Package (Simulation) window, the board list of the desired NE is expanded when the list is added to the operation list.
1-4
Issue 01 (2008-02-25)
Loading Type Loading simulatio n software package
Definition Loading simulation software package is to integrate all the software that you want to load on an NE and use a package description file to define loading attributes of the software. The ToolKit loads only the software that is defined in the description file.
Scenario When you need to load the entire set of software to an NE and the mapping between each board and software on the NE is defined according to the simulation software package format, you can use the loading simulation software package function to improve the load efficiency.
Operation Method In the Board and Software Package (Simulation) window, the board list of the desired NE is collapsed when the list is added to the operation list.
Loading Patch Software

Due to some reasons, some equipment in a network needs to run continuously in a long period of time. If you want to fix a bug in or add new features to the software that is running on the equipment, you can load a hot patch. Loading patch software is classified into loading board patch and loading patch package. Refer to Table 1-2. Table 1-2 Comparison between loading board patch and loading patch package Loadin g Type Loading board patch Definition The ToolKit loads the patch software to a board to fix existing bugs in the running software or provide new functions. Loading a hot patch does not affect services on an NE. Scenario The board patch is a supplement to the NE software or other board software. You can use the board patch to fix bugs of the mentioned software or to enhance the performance of an NE. Operation Method The patch software is loaded in the Patch window. You can load the patch software to NEs in this way only when the NE icon is . Merits and Demerits Loading board patch consumes a lot of time of the upgrade personnel.
Issue 01 (2008-02-25)
1-5
Loadin g Type Loading patch package
Definition Loading patch package is to integrate all the patch software to be loaded. Each patch software corresponds to a type of board and is encapsulated according to a certain definition to form a patch software package.
Scenario On an NE, many boards require loading patches. The ToolKit loads the desired patch package that is selected by the upgrade personnel to the NE, and then the NE issues a command to load the patch to the memory of the corresponding board. After that, you can use the press-to-install function to install each hot patch to the corresponding board.
Operation Method The patch software package is loaded in the Patch window. You can load the patch software package to NEs in this way only when the NE icon is .
Merits and Demerits Loading patch software package has merits as follows: Reduces the intervention of the upgrade personnel during loading. Saves the upgrade time and improves the upgrade efficiency. Reduces the possibility of incorrect software loading during upgrading.
A patch file has two characteristics as follows:

l
Accumulatability. In the same basic version, the patch file that is released later must contain the formal patches in all patch files that are previously released. Dependentability. The patch units in the same patch file are sorted, with the later patch units always dependent on the previous ones. For example, if a patch file contains 10 patch units,
to activate or run the fifth unit, you must activate or run five patch units from the first to the fifth. to delete the fifth patch unit, you must delete five patch units from the fifth to the tenth at the same time.
Loading Software Package

A software package consists of all software that you want to load to an NE. All the software is encapsulated according to a certain definition to form a file package. You can use the ToolKit to load all software in the package to an NE. Loading software package is classified into loading software package in non-diffusion mode and loading software package in diffusion mode. Refer to Table 1-3.
1-6
Issue 01 (2008-02-25)
Table 1-3 Comparison between loading software package in non-diffusion mode and loading software package in diffusion mode Loadi ng Mode Loadin g softwa re packag e in nondiffusi on mode Definition Scenario Operation Method The software package is loaded in the Software Package window. You can load the software package to NEs in this way no matter whether the NEs support diffusion or not. Merits and Demerits You can load software package to only one NE each time. In a network, when many NEs of the same type require loading software, the loading efficiency is low.
When you load a software package in non-diffusion mode, the ToolKit copies the file package to the system control and communication (SCC) board of the NE, and then the SCC board sends each software data in the package to a corresponding board according to the definition of encapsulation. After the loading is complete, the original software package is retained on the SCC board. If a new board is online, the software in the package is automatically loaded to the board.
On an NE, many boards require loading software.
Loadin g softwa re packag e in diffusi on mode
When loading a software package in diffusion mode, you can use the ToolKit to set a diffusion path of software package and then load all the software in the file package to the initial node NE regarding the preset diffusion path at a time. During loading, the initial node diffuses the software package to downstream nodes according to the diffusion path. The downstream nodes diffuse the software package in the same way.
In a network, many NEs of the same type require loading software. Besides, many boards on NEs of this type require loading software.
The software package is loaded in the Software Package window. You can load the software package to NEs in this way only when the NEs support diffusion loading and the NE icon is .
You can synchronously load a software package to many NEs of the same type. When the software package is synchronously loaded to many NEs, only one package file is transmitted in the network. This increases the bandwidth utilization of the network and improves the loading efficiency.
Issue 01 (2008-02-25)
1-7
Loading Simulation Software Package

A simulation software package consists of all software that you want to load to an NE, and a package description file that defines the attributes of loading software. The ToolKit loads only the software that is defined in the description file. When you load a simulation software package, the ToolKit analyzes the package description file to determine the required software, and then copies the required software to a corresponding board. Before loading the software, you can filter out the software that need not be loaded from the package and set the activation order of software after the loading is complete, to realize a personalized loading by using the ToolKit. As the software package is not retained in the NE, the loading operation is performed to online boards only. If a new board is online, the software package is not automatically loaded to the board. You need to perform the loading operation again.
Backing Up and Restoring NE Configuration Data

NE configuration data is the information in the memory of an NE, such as the board configuration, clock configuration and protection relations of the NE. As an instruction file of the NE, the NE configuration data is the key factor for the normal operation of the NE in the network. You can use the function of configuring data backup and restoration to back up the NE configuration data in a data configuration file and save it to the ToolKit server computer or the FTP server computer. In the case of an NE failure, you can use this file to quickly restore the data. The function of restoring NE configuration data is used to restore data to the NE memory based on the configuration data file backed up in the computer.
NOTE
NE configuration data and database package are the same data on the NE in different platforms. You can back up and restore the NE configuration data for version 5.00.02 NEs or earlier version NEs.
Backing Up and Restoring NE Database Packages

Database package is a package that contains all the database files on an NE and a file list which defines and manages the database files. You can use the function of backing up the NE database package to back up the NE database files on the local or another computer. In the case of an NE failure, you can use the package to quickly restore the data. The function of restoring NE database package is used to restore data to the NE based on the database package backed up in the computer. when restoring the NE database files, you can apply the new configuration data to boards.
NOTE
NE configuration data and database package are the same data on the NE in different platforms. You can back up and restore the NE database package for version 5.00.06 NEs or later version NEs.
Backing Up NE Logs
The NE logs are classified into the NE security logs and NE operation logs. The backup of security logs is to save the security logs on the NEs to a local or remote computer. NE security log records all the operations that NE users performed on the NE and the operation
1-8 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2008-02-25)
results. The operations contain querying NE login information, delete NE users and forcibly logging out NE users. You need to back up the security logs on NEs in order to prevent a loss of security logs in the event of an NE failure. You can use the security log backup function to back up the security logs on NEs to the local or another computer. The backup of operation logs is to save the operation logs on the NEs to a local or remote computer.
Generating Upgrade Report

You can collect all upgrade records during a past period to generate a upgrade report in the html format by using the ToolKit. The records only include upgrade operations performed to the NE by using the ToolKit. The upgrade report records in detail all the process information when you upgrade the NE or board by using the ToolKit:
l
Upgrade time: includes the start time and end time of such operations as loading, activation, backup and restoration, and the total upgrade duration. The total upgrade duration refers to the duration between the beginning of the first loading operation and the end of the last loading operation. It is not an accumulated value of the time of all loading processes. Upgrade quantity: includes the total quantity of NEs and boards upgraded. Equipment profile: includes the types and quantities of equipment upgraded. Software version: includes the software package version and board software version before and after upgrade. Other information: includes the user used in the upgrade and result of the upgrade availability check.
l l l
Switching ToolKit Server

One ToolKit server can be connected with multiple clients at the same time, while one client can only connect to one server each time. To connect the client to any other server, switch the ToolKit server.
Setting FTP
The ToolKit can use the FTP protocol to perform uploading and downloading software, and backing up and restoring data on NEs. By default, the FTP server is not started. When you use the FTP server for the first time, you need to set the FTP parameters and start the FTP server. When the FTP server is started, the ToolKit clients that are in the same network segments as the server can access the server. When connecting to the FTP server, you need to enter the IP address, user name, password and port of the started FTP server in the dialog box displayed on the client. If the connection is successful, you can access files on the FTP server just like accessing the local files.
Setting the Activation Mode

There are two types of activation modes, which are efficient and secure modes.
In the efficient mode, the ToolKit allows you to activate software for multiple boards at the same time, to increase the upgrade efficiency. Concurrent activation, however, may result in NE ECC disconnection or service interruption. In the secure mode, the ToolKit does not allow you to activate software for multiple boards at the same time, to maximize network security.
Viewing Logs
The ToolKit server records all the operations performed on the ToolKit in the log. The ToolKit provides the function of viewing logs so that you can query the operations that the ToolKit performed on NEs. In the Browse Log window, you can set the filter criteria to select logs that you want to view and save the query result in the local computer.
1.3 Performance Index

The ToolKit limits both the access quantity of terminals and the NE management capability.
Access Quantity of Terminals

By using the client/server architecture, the ToolKit supports the deployment of seperate client and server.
l l
One client can access to only one server each time. One server can be accessed by a maximum of 32 clients.
NE Management Capability
The ToolKit does not limit the number of NEs managed in the Navigation Tree. However, the number of login NEs at the same time cannot exceed 20.
1.4 System Architecture

The ToolKit uses the client/server architecture. The client provides you with an interactive interface for operating and managing NEs. You can load software, and back up or restore data on an NE inside the transport network at the client. The server is the interactive and processing center of information between the client and NEs, mainly providing the following two functions: one function is to respond to your operations at the client and send the operation command to the NE, and the other function is to receive and process information from the NE and send the processing result to the client.
Hardware Architecture
When the ToolKit is integrated into the T2000, the server and client of the ToolKit are respectively integrated at the server and client of the T2000 with the same hardware connection method as that of the T2000. Figure 1-3 is a common hardware connection method of the T2000.
1-10
Issue 01 (2008-02-25)
Figure 1-3 Common hardware connection of the T2000
When the ToolKit is used independently, the client and server can run either on the same computer, or on different computers. Figure 1-4 shows the hardware connection between the client and the server that run on different computers. Figure 1-4 Hardware connection when the ToolKit is used independently
Software Architecture
When the ToolKit is integrated into the T2000, all the functions serve as a Software Management module of the T2000. See Figure 1-5. Both of the server and the client are invisible to you. You can use all functions in the Software Management menu of the Main Window of the T2000 client. All the operation instructions and information from the NE are processed and forwarded by the ToolKit server that is integrated into the T2000.
Issue 01 (2008-02-25)
1-11
Figure 1-5 Software architecture when the ToolKit is integrated into the T2000
When the ToolKit is used independently, it mainly provides functions as the following two modules for you: the loading software module and the managing data module. See Figure 1-6. The loading software module is used to update the NE software, and the managing data module is used to back up and restore the NE configuration data. Figure 1-6 Software architecture when the ToolKit is used independently
1-12
Issue 01 (2008-02-25)
1.5 Networking and Communication

There are three ways of networking between the ToolKit and NEs: ECC, IP and OSI networking.
ECC
In this mode of networking, there must be one gateway NE (GNE). The GNE is connected with the ToolKit through an Ethernet interface, and communicates with it by using the TCP/IP protocol. The GNE is connected with other NEs through the ECC channel, and transmits the OAM information through D bytes. See Figure 1-7. The ECC protocol uses the NE ID as the unique identifier of the NE. For communications between NEs, the addressing is performed through the NE ID. A non-gateway NE communicates with the outside network through the GNE. Hence, the GNE is a basic route for the interaction of data both inside and outside the transport network. Each GNE has an independent IP address. Figure 1-7 Networking diagram through the ECC protocol
IP
In this mode of networking, NEs communicate with each other through the IP over DCC. Communications between NEs or between the NE and the ToolKit are carried out by using the TCP/IP protocol. In the transport network, each NE has an independent IP address. Hence, any one NE can directly set up a TCP connection with communication objects both inside and outside the transport network. See Figure 1-8. IP over DCC has the following characteristics:
l l
Provides flexible networking modes. Uses the standard TCP/IP protocol and ensures easy compatibility with third-party equipment and simplifies network management. Provides good compatibility. IP over DCC can be used with new application layer forwarding features.
Issue 01 (2008-02-25)
1-13
Figure 1-8 Networking diagram through the IP protocol
OSI
In this mode of networking, communications between NEs or between the NE and the ToolKit are carried out by using the OSI protocol. The ToolKit can directly set up a TP4 connection with any one NE inside the transport network. See Figure 1-9. The OSI protocol is a widely used communication protocol in an SDH network. Using OSI over DCC communication, a network that consists of equipment from multiple vendors allows for transparent transmission of management information at the network layer. Hence, the interconnection with the equipment that supports OSI protocol from the third party can be realized. Figure 1-9 Networking diagram through the OSI protocol
1-14
Issue 01 (2008-02-25)
2 Installing and Starting the ToolKit
Installing and Starting the ToolKit
About This Chapter

You can install and start the ToolKit on the Windows or UNIX platform by following the instructions below. 2.1 Installation and Running Environment The ToolKit is a software product and must be installed in a hardware environment where it can run properly and implement its functions. When you use the ToolKit to perform backup and loading operations to an NE, the ToolKit needs to interact with a transport network in the real time. The efficiency and effect of the ToolKit depends on the hardware configuration and operating system of the running environment. 2.2 Installing the ToolKit On Windows Uncompress the ToolKit installation package to a specified directory to complete the installation. 2.3 Starting the ToolKit on Windows You can start the client and server of the ToolKit at the same time, or start them separately. 2.4 Installing the ToolKit on UNIX A complete ToolKit installation installs the server and the client at the same time. 2.5 Starting the ToolKit on UNIX You can start the ToolKit after the installation is complete.
Issue 01 (2008-02-25)
2-1
2.1 Installation and Running Environment

The ToolKit is a software product and must be installed in a hardware environment where it can run properly and implement its functions. When you use the ToolKit to perform backup and loading operations to an NE, the ToolKit needs to interact with a transport network in the real time. The efficiency and effect of the ToolKit depends on the hardware configuration and operating system of the running environment.
Configuration Requirements
Multiple ToolKit clients can be installed on the computer where the server resides. Alternatively, the client and server can run on different computers. Different deployment ways have different requirements on the software and hardware of a computer. The following describes the deployment of one server and one client on the same computer. For other deployment ways, refer to this deployment way. Table 2-1 Recommended configuration of an ordinary PC Configuration Item CPU frequency Memory Quantity 1 1 Recommended Configuration P4 1.7 GHz 256 MB Remarks Required Required. In actual application, ensure that the system has a virtual memory of over 150 MB. Required Required. The ToolKit is accessed to an optical transport network through a network card. Required
Hard disk Network card
1 1
40 GB 100 Mbit/s
Operating System System resolution
1 -
Windows XP Professional 1024 x 768
Table 2-2 Recommended configuration of a workstation Configuration Item CPU frequency Quantity 1 Recommended Configuration UltraSPARC 2 x 1.60 GHz Remarks Required
2-2
Issue 01 (2008-02-25)
Configuration Item Memory
Quantity 1
Recommended Configuration 2 GB
Remarks Required. In actual application, ensure that the system has a virtual memory of over 150 MB. Required Required. The ToolKit is accessed to an optical transport network through a network card. Required
Hard disk Network card
1 1
2 x 146 GB 100 Mbit/s
Operating system System resolution
1 -
Solaris 10 1024 x 768
2.2 Installing the ToolKit On Windows

Uncompress the ToolKit installation package to a specified directory to complete the installation.
Context
NOTE
l l
The directory name you specify when installing the ToolKit can consist of numerals and characters. The ToolKit directory of the compressed package consists of the following subfiles:
l l l l
client: including the client application, local logs, configuration information and online Help. server: including the server application, system logs. ToolKit.bat: including the batch files that are used to start the ToolKit client. versionInfo.ini: including file that contains the version of the ToolKit.
Procedure
Step 1 Copy the compressed package of ToolKit to the computer. Step 2 Uncompress the package. ----End
Issue 01 (2008-02-25)
2-3
2.3 Starting the ToolKit on Windows

You can start the client and server of the ToolKit at the same time, or start them separately.
Prerequisite
The ToolKit must be correctly installed.
Procedure
Step 1 Double-click the ToolKit.bat file in the installation directory.
NOTE
When starting the ToolKit for the first time, the Connecting to ToolKit Server dialog box is displayed. You need to enter the IP address of the server to be connected to.
l l
When you enter the local IP address, the local server starts automatically. When you enter the IP address of the other server, the local server does not start.
Step 2 Optional: When you double-click the ToolKit.exe in the server directory, only the local server starts. ----End
2.4 Installing the ToolKit on UNIX

A complete ToolKit installation installs the server and the client at the same time.
Context
NOTE
The directory name you specify when installing the ToolKit can consist of numerals and characters.
Procedure
Step 1 On UNIX, copy the compressed package of ToolKit to the computer, and then uncompress the package.
NOTE
l l
The uncompression command on UNIX: gunzip file name The package uncompression command on UNIX: tar xvf file name
Step 2 Right-click in the blank space of the desktop, and choose Tools > Create Action from the shortcut menu. The Create Action dialog box is displayed. Step 3 Fill in the blanks according to the following information:
l l l
Action Name (Icon Label): ToolKit Command When Action is Opened (Double-clicked): /ToolKit installation path/ToolKit.bat Window Type: Graphical(X-Window)
2-4
Step 4 Choose File > Save to save the new action (saved in the start directory). Step 5 Click OK.
Step 6 Right-click in the blank space of the desktop and choose Files > File Manager from the shortcut menu. Step 7 Select the ToolKit file and choose Selected > Move to from the menu to move the ToolKit icon to the installation directory.
Step 8 In the ToolKit installation directory, right-click the ToolKit file and choose Put in Workspace from the shortcut menu. The ToolKit icon appears on the desktop.
Step 9 Exit the file manager. ----End
2.5 Starting the ToolKit on UNIX

You can start the ToolKit after the installation is complete.
Prerequisite
When the ToolKit is running on UNIX, make sure that the user has the read, write and administration rights to the ToolKit installation directory, the subdirectory and the files in them.
Procedure
l l If the ToolKit icon is created, double-click the icon to run the ToolKit. If not, follow the steps below: 1. 2. Right-click in the blank space of the desktop, and choose Tools > Terminal from the shortcut menu. The Terminal dialog box is displayed. In the ToolKit installation directory, enter the following command and the ToolKit is started.
----End
2-6
Issue 01 (2008-02-25)
3 Basic Operations
3
About This Chapter
Basic Operations
The basic operations of the OptiX ToolKit are described as follows. 3.1 GUI Description The ToolKit uses the graphic user interface. You can select a function from the Main Menu of the ToolKit to display the corresponding operation window. Most windows of the ToolKit are composed of three areas: Navigation Tree, Operation List and Operation Result. This section describes the windows by taking the Backup/Restore Database Package window as an example. 3.2 Buttons and GUI Components The frequently used buttons and common icons on the main window of the ToolKit are described. 3.3 NE and Board Management In the ToolKit, NEs and boards are the most basic operation objects. Before you add NEs and boards to the operation list, you need to search for, add and filter them. 3.4 Login Management The login management of the NE includes logging in to an NE, switching the login user of the NE, and exiting the NE. 3.5 Creating Subnet You need to create a subnet before you use it to manage NEs. 3.6 Setting FTP You can perform this operation to set a local directory as the FTP server directory. 3.7 Setting the Activation Mode In this user interface, you can set the activation mode, to increase the loading efficiency for an NE and to guarantee network security. 3.8 Switching the ToolKit Server To change the server that the client connects to, you can use the switch ToolKit server function. 3.9 Browseing Logs You can use the view log function to query the records of operations performed by using the ToolKit. You can also save the logs to a file.
3 Basic Operations
3.1 GUI Description

The ToolKit uses the graphic user interface. You can select a function from the Main Menu of the ToolKit to display the corresponding operation window. Most windows of the ToolKit are composed of three areas: Navigation Tree, Operation List and Operation Result. This section describes the windows by taking the Backup/Restore Database Package window as an example.
Backup/Restore Database Package Window

To display the Backup/Restore Database Package window, choose Backup/Restore > Backup/Restore Database Package. The window is shown in Figure 3-1. Figure 3-1 The Backup/Restore Database Package window
Window Component Description

You can correctly and skillfully use the ToolKit only after you have accurately understood all components in the window.
3 Basic Operations
Table 3-1 Window component description Component Navigation Tree Description The area in which the ToolKit manages NEs. The NE searched out in the transmission network is displayed in the root directory of the Navigation Tree, after the NE is successfully created. Choose an item from the menu to display the corresponding window. Click the button to quickly display a window. Clicking a button equals to clicking a menu item. The area in which the ToolKit performs operations to NEs. You should add NEs into the Operation List before setting different operation tasks to them. After setting the operation tasks, you can click the corresponding button to perform different operations. Indicates whether the current FTP Server starts. By using the ToolKit, you can set a public directory on the computer where the server resides. Other ToolKit servers in the same network segment can access the directory by using the FTP protocol, including reading data from the directory and writing data into the directory. Displays the IP address of the server which the current client connects to. For example, in the IP address 127.0.0.1:8999-2, "127.0.0.1" represents that the IP address of the server is 127.0.0.1 (that is, the local computer); "8999" represents the port address that is not encrypted by using SSL, and if the value is 9000, it indicates that the port address is encrypted by using SSL; "2" represents that the current client is the second terminal that is connected to the server. Display the information relates to the current operation. For example, NE name and loading progress. Displays the information that is reported during the execution of tasks. Displays the system time of the computer that the current Client resides.
Menu Toolbar Button
Operation List
Operation Button
FTP Server Status
ToolKit Server IP
NE Information
Operation Result Client System Time
Issue 01 (2008-02-25)
3-3
3 Basic Operations
3.2 Buttons and GUI Components

The frequently used buttons and common icons on the main window of the ToolKit are described.
Frequently Used Buttons

Button Name Exit Search NE Create NE Software Package Board and Software Package (Simulation) Patch Backup/Restore Configuration Data Backup/Restore Database Package Timing Backup Database Package Backup Security Log Browse Log FTP Setting Topics Refresh Description Exits the current terminal. Searches for the NEs for the specified gateway NE. Displays the Add NE dialog box. Displays the Load Software Packagewindow. Displays the Board and Software Package (Simulation) window. Displays the Load Patch Software window. Displays the Backup/ Restore Configuration Data window. Displays the Backup/ Restore Database Package window. Displays the Timing Backup Database Package window. Displays the Backup Security Log window. Displays the Browse Log window. Displays the FTP Setting dialog box. Displays the ToolKit Help. Refreshes the Navigation Tree.
3-4
Issue 01 (2008-02-25)
3 Basic Operations
Button
Name Shrink Expand Add to list
Description Collapses the Navigation Tree. Expands the Navigation Tree. Adds the NE or board in the Navigation Tree to the operation list.
Key GUI Components

Component Name Available Not logged in Logged in, but not supported Description The NE is logged in. The current function is available. The NE is not logged in. The NE is logged in. The current function is not available. The NE is logged in. The current function is available. The NE is Gateway NE. The NE is Gateway NE, but not logged in. The NE is logged in. The current function is not available. The NE is Gateway NE. The NE is logged in. support Loading a Software Package in Diffusion Mode. and the NE is the initial node NE of the diffusion group. The NE is logged in. and support Loading a Software Package in Diffusion Mode The FTP Server is running. The FTP Server is stopped.
Available
Not logged in Logged in, but not supported
Logged in, the initial node NE of the diffusion group
Logged in, and supported diffusion FTP Server Running FTP Server Stop
Issue 01 (2008-02-25)
3-5
3 Basic Operations
3.3 NE and Board Management

In the ToolKit, NEs and boards are the most basic operation objects. Before you add NEs and boards to the operation list, you need to search for, add and filter them. 3.3.1 Searching for NEs You can search for all NEs of the specified gateway NE by using the NE search function of the ToolKit. The NEs are displayed in a form of list. You can add the NE that is searched out into the Navigation Tree. 3.3.2 Creating NEs Before you manage an NE by using the ToolKit, you need to create it in the Navigation Tree. 3.3.3 Querying Boards Before performing operations on a board on an NE, you must add the board to the Navigation Tree. 3.3.4 Adding Boards You can use this function to add a board on the NE to the Navigation Tree. 3.3.5 Filter NE/Board You can use the filtering feature to display the NEs or boards that meet the condition in the navigation tree. The ToolKit does not support secondary filtering. That is, after you set new filter criteria, the ToolKit re-filters NEs or boards in the selected network range.
3.3.1 Searching for NEs

You can search for all NEs of the specified gateway NE by using the NE search function of the ToolKit. The NEs are displayed in a form of list. You can add the NE that is searched out into the Navigation Tree.
Prerequisite
l l
The computer where the ToolKit is installed must communicate with the NE normally. Make sure that you have obtained the port, user name and password of the gateway NE to be searched. If you want to create an NE, make sure that you have obtained the user name and password of the NE to be created.
Procedure
Step 1 Choose System > Search NE from the Main Menu. The Search NE window is displayed. Step 2 Click Search, and the ToolKit automatically searches for all gateway NEs and displays them in the Gateway list. Step 3 Select the gateway NE to be searched, click Edit..., and the Gateway Parameter dialog box is displayed. Step 4 In the Gateway parameter dialog box, enter the port, user name and password. Click OK.
3-6
Issue 01 (2008-02-25)
3 Basic Operations
Step 5 Click Start Search, and the ToolKit begins to search for all NEs of this gateway NE and displays them in the result list.
NOTE
You can click Create NE... to add the NE that is searched out into the Navigation Tree. For details on how to add an NE, refer to Creating NEs.
----End
Related Topics
3.3.2 Creating NEs
3.3.2 Creating NEs

Before you manage an NE by using the ToolKit, you need to create it in the Navigation Tree.
Prerequisite
l l
The NE must communicate with the ToolKit client normally. The NE ID, NE name, gateway address, port, user name and password of the NE must be provided.
Context
When adding an NE, you can choose whether to directly log in to the NE. If you choose to directly log in to the NE, the ToolKit automatically logs in to the NE after the NE is successfully added. Before you add an NE in this way, make sure that the ToolKit communicates normally with the NE. If you do not choose to directly log in to the NE, enter the NE ID and NE name. Note that the NE ID and NE name cannot be the same as any existing NE. After the NE is successfully added, the NE status is not logged in. You can log in to the NE later.
NOTE
l l l l
If you change the NE ID and gateway address by using other tools, use the ToolKit to delete the original NE and re-create it. Otherwise, you cannot manage the NE. You must specify the ID for NEs (OptiX BWS 1600G and Metro 500) that are in the BIOS state. Otherwise, the NE creation fails. If you choose Login directly, click Apply to add an NE, this NE ID is the ID number of the previously created NE plus 1. The real name of the NE is displayed if the NE has a real name. In this case, the NE name that you set is invalid.
Issue 01 (2008-02-25)
3-7
3 Basic Operations
Procedure
Step 1 Choose Load Software > Software Package from the Main Menu. The NEs that have been added in the Navigation Tree are displayed.
NOTE
l l
You can also choose other functions to display the ToolKit management window. If the Navigation Tree already exists, skip this step.
Step 2 Click Step 3 Click
to refresh the NE list. , and the Create NE dialog box is displayed.
Step 4 Enter the information of the NE and NE user in the Create NE dialog box. The options marked with a red * in the dialog box are required to be set.
NOTE
l l
Click Search, and the ToolKit automatically searches for the IP addresses of all gateway NEs that communicate normally with the ToolKit and displays them in the drop-down list. The ToolKit adds the NE to the root directory by default. If other subnets have been created in the Navigation Tree, you can select a subnet that the NE you add into the Navigation Tree belongs to.
Step 5 Click OK to close the Create NE dialog box.

NOTE
Click Apply to add another NE.
----End
Related Topics
3.3.1 Searching for NEs
3 Basic Operations
3.3.3 Querying Boards

Before performing operations on a board on an NE, you must add the board to the Navigation Tree.
Prerequisite
The NEs must be logged in.
Context
By using the ToolKit, you can choose to manually add boards or add boards by querying, according to actual requirements. Manually adding boards is usually used to add only a few boards when there are many boards. Adding boards by querying is used to add many boards to the same NE. When you add boards by querying, the ToolKit queries the actual in-service boards on the NE and adds all the boards that are displayed after querying to the Navigation Tree.
NOTE
For release 4.0 NEs, you need to create logical boards before you query the board list.
Procedure
Step 1 Choose Load Software > Board and Software Package (Simulation) from the Main Menu. The NEs and boards that have been added in the Navigation Tree are displayed.
NOTE
l l
Step 2 Click
to refresh the NE and board list.
Step 3 Right-click the NE in the NE List and choose Query Board. The boards on the NE are automatically created and shown in the list.
NOTE
When querying the board, you must wait for a period for its display. This is a normal situation for NEs. To query boards in batches, you need to select the NEs in the list, right-click on root and choose Query Boards of the Selected NE.
----End
3 Basic Operations
Related Topics
3.3.4 Adding Boards
3.3.4 Adding Boards

You can use this function to add a board on the NE to the Navigation Tree.
Prerequisite
l l
The related NE must be logged in. The physical slot ID of the board that you want to add must be provided.
Context
If the added board actually exists, the actual name of the board is displayed in the Navigation Tree. Otherwise, the board name displayed is Unknown, which is common when you preconfigure the board.
Procedure
Step 1 Choose Load Software > Board and Software Package (Simulation) from the Main Menu. The NEs and boards that have been added in the Navigation Tree are displayed.
NOTE
l l
to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click the NE in the Navigation Tree and choose Add Board.... The Add Board dialog box is displayed.
Step 4 Enter the physical slot ID of the board and click OK. ----End
Related Topics
3.3.3 Querying Boards
3.3.5 Filter NE/Board

You can use the filtering feature to display the NEs or boards that meet the condition in the navigation tree. The ToolKit does not support secondary filtering. That is, after you set new filter criteria, the ToolKit re-filters NEs or boards in the selected network range.
3 Basic Operations
Filter Window
In any window that contains a navigation tree, click Filter... and the Filter NE/Board window is displayed.
GUI Description
Field Entire Network Only Subnet Selected Search for Network Elements NE Type NE Name Search for Boards Board Type Description Click the option button to filter the objects that are contained under the root node. Click the option button to filter NEs or boards in the selected subnet. Click the option button to filter NEs. Select an NE type from the drop-down list that displays all NE types under the root node. Enter the name of an NE. If you select a correct NE type, the ToolKit correctly filters the required NE. Click the option button to filter boards. Select a board type from the drop-down list that displays all board types under the root node.
3.4 Login Management

The login management of the NE includes logging in to an NE, switching the login user of the NE, and exiting the NE. 3.4.1 Logging in to an NE Before you perform operations to the NE by using the ToolKit, log in to the NE in the Navigation Tree. 3.4.2 Switching Login Users
3 Basic Operations
By default, the ToolKit uses the NE user that is successfully logged in last time to log in to the NE. You can change the login user of the NE. 3.4.3 Logging Out of an NE For NEs that require no more operations, log out of them by using the ToolKit in a timely manner, to release communication resources.
3.4.1 Logging in to an NE
Before you perform operations to the NE by using the ToolKit, log in to the NE in the Navigation Tree.
Prerequisite
l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly.
Procedure
NOTE
l l
Step 2 Click
to refresh the NE list.
Step 3 In the NE list, right-click an NE and choose Login NE from the shortcut menu.
NOTE
l l l
The icons of the logged in NEs are shown in green, and the others are in gray. If the NE user is used by another application to log in to the NE, your login forces the other application to log out. To log in to multiple NEs at the same time, select the NEs from the NE list, right-click on root and choose Login Selected NE from the shortcut menu.
----End
Related Topics
3.4.3 Logging Out of an NE 3.4.2 Switching Login Users
3 Basic Operations
3.4.2 Switching Login Users

By default, the ToolKit uses the NE user that is successfully logged in last time to log in to the NE. You can change the login user of the NE.
Prerequisite
l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly.
Context
NOTE
l l
To operate NEs by using the ToolKit, make sure that the login user of the NE is a super user. When the ToolKit is loading software to the NE, backing up data or restoring data, you cannot modify the login account.
Procedure
NOTE
l l
Step 2 Click
Step 3 In the NE list, right-click an NE and choose Set Login Account... from the shortcut menu.
NOTE
l l
The account you set must already exist at the NE side. To set the same login account for multiple NEs, select the NE in the NE list, right-click on root, and choose Set Login User for Selected... from the shortcut menu.
Step 4 Enter the new NE user and password in the Set Login Account dialog box. Step 5 Click OK. ----End
Related Topics
3.4.1 Logging in to an NE
3 Basic Operations
3.4.3 Logging Out of an NE
3.4.3 Logging Out of an NE

For NEs that require no more operations, log out of them by using the ToolKit in a timely manner, to release communication resources.
Prerequisite
l l
The NE must be in the logged-in state in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly.
Context
NOTE
l l
The NE is logged out automatically when the ToolKit exits. When the ToolKit is loading software to an NE, backing up data or restoring data, you cannot log out of the NE.
Procedure
NOTE
l l
Step 2 Click
Step 3 In the NE list, right-click an NE and choose Logout from the shortcut menu.
NOTE
l l
The logged-in NE is shown in green. After you log out of the NE, it is shown in gray. To log out of multiple NEs at the same time, select the NEs in the NE list, right-click on root and choose Logout Selected NE from the shortcut menu.
----End
Related Topics
3.4.1 Logging in to an NE 3.4.2 Switching Login Users
3 Basic Operations
3.5 Creating Subnet

You need to create a subnet before you use it to manage NEs.
Context
The ToolKit supports both the embedded management between subnets and the subnet management functions to NEs in order to manage NEs in an easy way. You can manage NEs in the Navigation Tree in categories according to your need thus to make NEs belong to different subnets.
Procedure
Step 1 Choose Load Software > Software Package (Simulation) from the Main Menu. The NEs that have been added in the Navigation Tree are displayed.
NOTE
l l
Step 2 Click
Step 3 Right-click on the root, and choose Create Subnet... from the shortcut menu. The Create Subnet dialog box is displayed.
Step 4 In the Create Subnet dialog box, enter the name of the subnet you want to create.
NOTE
When creating the subnet, you can edit its attributes.

l l
In the Children Objects tab, add or delete the object managed by the subnet. In the Remark tab, add a description of the subnet. The description must not exceed 256 characters.
Issue 01 (2008-02-25)
3-15
3 Basic Operations
Step 5 Click OK. ----End
Related Topics
3.3.2 Creating NEs
3.6 Setting FTP

You can perform this operation to set a local directory as the FTP server directory.
Context
NOTE
After you set the FTP parameters, the FTP server is restarted and the previous FTP server is also stopped. Before you set the parameters, make sure that ToolKit is not using the FTP translation function.
Procedure
Step 1 Choose System > FTP Setting from the Main Menu. The FTP Setting dialog box is displayed. Step 2 Set the FTP parameters, and then click Start Up.
NOTE
To stop the FTP server, click Stop. You cannot stop the FTP server that is in use.
Step 3 Click OK or Yes in the confirmation dialog box. ----End
Related Topics
7.2 Setting the Access Path
3.7 Setting the Activation Mode

In this user interface, you can set the activation mode, to increase the loading efficiency for an NE and to guarantee network security.
3-16
Issue 01 (2008-02-25)
3 Basic Operations
Context
CAUTION
There are two types of activation modes, which are efficient and secure modes. In the efficient mode, the ToolKit allows you to activate software for multiple boards or multiple NEs at the same time, to increase the upgrade efficiency. Concurrent activation, however, may result in NE ECC disconnection or service interruption. In the secure mode, the ToolKit does not allow you to activate software for multiple boards or multiple NEs at the same time, to maximize network security.
Procedure
Step 1 Choose System > Activate Mode Setting from the Main Menu. The Activate Mode Setting dialog box is displayed. Step 2 Select an activation mode and click OK. The Activate Mode Setting dialog box is displayed asking you whether you want to continue. Step 3 Click Yes. A prompt appears telling you that the operation was successful. Step 4 Click Close.
NOTE
In the Software Package window, you can perform rollback of the Efficiency Mode and Security Mode concurrently.
----End
3.8 Switching the ToolKit Server

To change the server that the client connects to, you can use the switch ToolKit server function.
Prerequisite
l l
Make sure that you have obtained the address of the server to be connected to. In the current user interface, all tasks must be complete.
Context
When switching the ToolKit Server, you can enable the security socket layer (SSL) protocol to encrypt the communication between the Client and the Server for the sake of security.
Procedure
Step 1 Choose System > Switch ToolKit Server from the Main Menu. The Switch ToolKit Server dialog box is displayed. Step 2 Enter the IP address of the server to be connected to, and click OK.
3 Basic Operations
Step 3 Click Yes in the confirmation dialog box. The ToolKit client is connected to the corresponding ToolKit server. ----End
3.9 Browseing Logs

You can use the view log function to query the records of operations performed by using the ToolKit. You can also save the logs to a file.
Prerequisite
You must use the ToolKit to perform this operation.
Context
NOTE
l l
Important or milestone events or operation information must be saved to a file for future use. The time range for querying the logs cannot exceed one year.
Procedure
Step 1 Choose System > Browse Log from the Main Menu. Step 2 Select or enter an operation object, for example, NE9_8961.
Step 3 Select a type of the log that you want to view.
Step 4 Click
to set the time range.
3-18
Issue 01 (2008-02-25)
3 Basic Operations
Step 5 Click Query and the log information within the time range is displayed. Double-click a record to display its detailed information.
NOTE
Click Save and a dialog box is displayed. Select a path to save the log file. Click Save and the log is successfully saved.
----End
Issue 01 (2008-02-25)
3-19
4 Loading Software
4
About This Chapter
Context
Loading Software
The six ways of upgrading a network by using the ToolKit are as follows: loading board software, loading software package in non-diffusion mode, loading software package in diffusion mode, loading simulation software package, loading board patch, and loading patch package.
The following table lists the comparison between the six loading ways: Table 4-1 Comparison between six ways of upgrading a network by using the ToolKit Loading Way Description Whether ToolKit Directly Operates to Target Board Yes Upgra de Efficie ncy Low Recommende d Application Scenario
Loading board software
Load files one by one on a perboard basis. You can also load multiple files to a board at the same time if the board supports this feature.
When there is not much board software that requires upgrade for an NE.
Issue 01 (2008-02-25)
4-1
4 Loading Software
Loading Way
Description
Whether ToolKit Directly Operates to Target Board No
Upgra de Efficie ncy High
Recommende d Application Scenario
Loading software package in nondiffusion mode
The ToolKit loads the encapsulated software set to the SCC board, and the SCC board distributes the software to the corresponding board. The software package is saved in the SCC board, and the SCC board automatically upgrades the software of the new online board.
When much board software requires upgrade. In addition, the software version after the upgrade is stable and the software need not be upgraded frequently. When much board software on the NE requires upgrade. In addition, the software version after upgrading is stable and the software need not be frequently upgraded. In a network, many NEs of the same type require upgrade.
Loading software package in diffusion mode
Before using the ToolKit to load a software package, you need to create the diffusion relation between desired NEs. During loading, the ToolKit loads the software package to the initial node NE according to the diffusion relation. The initial node NE diffuses the software package to downstream nodes according to the diffusion relation. The process of loading the software package to the initial node NE during diffusion loading is the same as that during non-diffusion loading. The NE automatically diffuses the software package to downstream nodes.
Yes
High
Loading simulation software package
The ToolKit directly loads the software in the software set to a board. The loading way supports NE-level and boardlevel group activation.
Yes
Medium
When much board software requires upgrade for an NE and there is a requirement on the sequence in which the NE software or board software is activated.
4-2
Issue 01 (2008-02-25)
4 Loading Software
Loading Way
Description
Whether ToolKit Directly Operates to Target Board Yes
Upgra de Efficie ncy Lower than loading a patch package
Recommende d Application Scenario
Loading board patch
The ToolKit loads the patch software to a board. A patch software is a fix to the existing bug in the running software, or it provides a new feature. Loading a hot patch does not affect the services in an NE. Loading a patch software package is to integrate all the patch software to be loaded. Each patch software corresponds to a type of board and is encapsulated according to a certain definition to form a patch package. The ToolKit loads the desired patch package to the NE, and then the NE issues a command to load the patch to the memory of the corresponding board.
When you need to fix an existing bug in the software or add new features. When you need to fix an existing bug in the software or add new features. When much board software on the NE requires loading patches. In addition, the software version after loading is stable and the software need not be frequently upgraded.
Loading patch package
Yes
Higher than loading a board patch
NOTE
l l
As the six ways use different loading schemes, they cannot be compared in terms of upgrade efficiency. The comparison between the six ways is for your reference only. Your selection of a loading way depends on the software to be upgraded and the current running software version. For example, if the current NE software version supports only loading simulation software package, you can use this loading way only.
4.1 Loading Board Software To load software to only a part of a board on an NE, you can use the function of loading board software. 4.2 Loading Software Package In Non-diffusion Mode You can use the function of loading software package to load all NE software and board software on the NE at the same time, so that you need not repeat the operation of loading software for one board at a time. This loading mode cannot diffuse the loaded software package to other NEs.
4 Loading Software
4.3 Loading a Diffusion Software Package Loading a software package can load all the software defined in the package format to NEs. For NEs that support package diffusion, you can load the software package to the initial node NE only. The initial node NE automatically diffuses the software package to downstream nodes according to the diffusion relation. This greatly improves the loading efficiency. 4.4 Loading the Simulation Software Package To load a set of software to an NE whose mapping relations between boards and software are defined according to the format of a simulation software package, you can use the function of loading the simulation software package to improve the efficiency. 4.5 Loading Board Patch Software The patch software is a supplement to the NE software or other board software. You can use the patch software to fix bugs of the mentioned software or to enhance the performance of an NE. 4.6 Loading an NE Level Patch Package Loading patch package is to integrate all the patch software to be loaded. Each patch software corresponds to a type of board and is encapsulated according to a certain definition to form a patch package. The ToolKit loads the desired patch package that is selected by the upgrade personnel to the NE, and then the NE issues a command to load the patch to the memory of the corresponding board.
4-4
Issue 01 (2008-02-25)
4 Loading Software
4.1 Loading Board Software

To load software to only a part of a board on an NE, you can use the function of loading board software.
Prerequisite
l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE must support this function. The software package to be loaded must match the target NE.
Context
NOTE
Before you load the NE software to an SCC board, pay attention to the following:
l l
For the SCC boards that have two sets of NE software, the newly loaded software can reside on the SCC board only as the standby software. It functions as the active software only after being activated. Activating the Fpga software may result in the hard reset of the NE and interrupt the services. Hence, if you need to load the same Fpga file to two different areas of the same SCC board, do not activate the Fpga file when the file is loaded at the second time. For NEs that have double SCC boards, if you directly load and activate the NE software on the active SCC board, services may be interrupted. Therefore, load and activate the NE software on the standby SCC board first, and then load the NE software on the active SCC board. The ToolKit can load NE software to the SCC board for a maximum of five NEs at the same time. When you load the software for multiple NEs at the same time, you must activate the software on each NE one by one after all the loading tasks are complete. When the NE software is successfully loaded but not activated, you need to reload and activate the NE software if you restarts the ToolKit. You cannot perform multiple operations on the same NE at the same time, such as software loading, data backup and restoration. Do not load software to the SCC board and other boards on the same NE at the same time. The ToolKit provides a separate navigation path for deleting an NE database. You can manually delete the NE database. Refer to 6.8 Deleting an NE Database Manually. During loading, when Abnormal is displayed, you can right-click and choose Refresh from the shortcut menu. In this way, the NE status returns to Normal.
l l l l l
Procedure
Step 1 Choose Load Software > Board and Software Package (Simulation) from the Main Menu. The NEs that have been added to the Navigation Tree are displayed. Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Click
Issue 01 (2008-02-25)
to expand the board list.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-5
4 Loading Software
Step 5 Check the check box before the board to be loaded, and unfold the board list. Click to add the board to the operation list.
NOTE
When querying the board, you must wait for a period for its display. This is a normal situation for NEs.
Step 6 In the Upgrade Version field, click Setting Board Software.
. The Board software setting window is displayed. See
Step 7 Select a type of software loading, and click Add Software... or Select Software.... The Choose File window is displayed.
NOTE
If you click Add Software..., you can add multiple files at a time. If you click Select Software..., you can add only one file at a time.
Step 8 Select the file to be loaded in the Choose File window.

NOTE
l l l l
refer to ECC and IP over DCC. If the file path contains non-alphanumeric characters, you may fail to access the file. If you do not select File on FTP Server, you can access the files on the ToolKit Server. If you select File on FTP Server, enter the address, user name, password and port of the FTP server, and then click . After the ToolKit is successfully connected to the FTP server, you can access the files on the FTP server.
If your computer uses multiple network cards and has multiple IP addresses, ensure that the IP address of the FTP server and the IP address of your computer are in the same network segment. Otherwise, the connection may fail and you may fail to obtain the file list. For problems encountered during the use of the FTP server, refer to Setting File Path.
Step 9 In the Board software setting window, click OK. Step 10 In the operation list, select a board, and click Start.
NOTE
During the process, you can click Stop to stop the loading. During loading, when Abnormal is displayed, you can right-click and choose Refresh from the shortcut menu. In this way, the NE status returns to Normal. The ToolKit provides a separate navigation path for deleting an NE database. You can manually delete the NE database. Refer to 6.8 Deleting an NE Database Manually.
Step 11 When the loading is complete, click Activate. The Warning dialog box is displayed. Confirm whether to activate the software. Step 12 Click Yes to start activating the software. Step 13 After the activation, the Operation Result dialog box is displayed indicating that the activation is successful. Click Close. ----End
Related Topics
4.4.5 Loading a Simulation Software Package to an NE
4 Loading Software
4.2 Loading Software Package In Non-diffusion Mode

You can use the function of loading software package to load all NE software and board software on the NE at the same time, so that you need not repeat the operation of loading software for one board at a time. This loading mode cannot diffuse the loaded software package to other NEs.
Prerequisite
l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE must support this function. The software package to be loaded must match the target NE.
Context
NOTE
The non-diffusion loading mode of software packages applies to NEs that support diffusion loading. The ToolKit provides a separate navigation path for deleting an NE database. You can manually delete the NE database or. Refer to 6.8 Deleting an NE Database Manually.
Procedure
Step 1 Choose Load Software > Load Software Package from the Main Menu. The NEs that have been added to the Navigation Tree are displayed. Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Select an NE, and select the protocol for backup from the Protocol drop-down list. In the event of ECC networking, select ECC. Refer to ECC and IP over DCC.
Step 6 Click
in the File field to select a file.
Issue 01 (2008-02-25)
4-7
4 Loading Software
NOTE
l l l l
Step 7 Click Start to start loading the software package. The NE status is Copying.
NOTE
During loading, you can perform a rollback operation. After the copy is complete, the NE status changes to Undispensed.
Step 8 Click Dispense to dispense the software package that is loaded to the SCC board of the NE to each board on the NE.
NOTE
During loading, you can click Rollback to perform a rollback operation. The window displays the dispense progress, and the status is Dispensing.
Step 9 After the dispense is complete, click Activate. The Warning dialog box is displayed. Confirm whether to proceed. Step 10 Click Yes to start activating the software. The window displays the activating progress, and the NE status is activating.
NOTE
During loading, you can click Rollback to perform a rollback operation. After the activate is complete, the NE status is Activated and Uncommitted.
Step 11 Click Commit. The window displays the committing progress, and the NE status is Committing. After the commission is complete, the NE status changes to Normal-Unstable. The loading is successful.
NOTE
After you click Commit, you cannot perform the rollback operation and the software of lower levels on the NE is cleared.
----End
4.3 Loading a Diffusion Software Package

Loading a software package can load all the software defined in the package format to NEs. For NEs that support package diffusion, you can load the software package to the initial node NE only. The initial node NE automatically diffuses the software package to downstream nodes according to the diffusion relation. This greatly improves the loading efficiency. 4.3.1 Creating a Diffusion Group
4 Loading Software
Before loading a software package in diffusion mode, you need to create a diffusion group for NEs to set up the diffusion relation. An initial node is created after you create a diffusion group. 4.3.2 Querying the Diffusion Relation Before loading a software package in the diffusion mode, you need to query the diffusion relation between NEs and learn the initial node of the diffusion and the diffusion path. During the loading, you can load the software package to the initial node only. The initial node NE automatically diffuses the software package to downstream nodes according to the diffusion path. 4.3.3 Loading a Software Package in Diffusion Mode Loading a software package can load all the software defined in the package format to NEs. For NEs that support package diffusion, you can load the software package to the initial node NE only. The initial node NE automatically diffuses the software package to downstream nodes according to the diffusion relation. This greatly improves the loading efficiency.
4.3.1 Creating a Diffusion Group

Before loading a software package in diffusion mode, you need to create a diffusion group for NEs to set up the diffusion relation. An initial node is created after you create a diffusion group.
Prerequisite
l
A GNE of NEs for which you want to create a diffusion group must exist in the Navigation Tree, and the GNE must be logged in. The desired NEs support package diffusion, and the current NE status is normal. No diffusion group is created. At least two desired NEs that support package diffusion must exist. The types of NEs in the same diffusion group that is to be created must be the same. The desired NEs must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NEs must support this function.
l l l l l
Context
NOTE
In the operation list, right-click an NE for which the group is created, and choose Cancel Diffuse Group from the shortcut menu to cancel the diffusion group. To successfully cancel the group, the status of the desired NE must be normal and the group must already be created. You must perform the Cancel Diffuse Group operation before using the ToolKit to perform other operations on an NE for which the diffusion group is created.
Procedure
Step 1 Choose Load Software > Load Software Package from the Main Menu. The NEs and boards that have been added to the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE.
4 Loading Software
Step 4 Select an NE and click list.
. The information about the NE is displayed in the operation
Step 5 View whether the NE supports creating a diffusion group.

NOTE
You can create a diffusion group for an NE only when the NE icon is displayed as
Step 6 In the Availability field, click . Query the NE health in the Information of NE's health dialog box displayed.
NOTE
You cannot upgrade an NE if the NE fails to pass the health check. The results of NE health check are as follows:
l l l
OK indicates that the NE is running normally and can be upgraded safely. POK indicates that the NE is running abnormally. In this case, do not upgrade the NE. NG indicates that the NE is running abnormally. In this case, do not upgrade the NE.
Step 7 Press and hold Ctrl, and click the NE for which you want to create a diffusion group. Step 8 Right-click the NE and choose Create Diffuse Group from the shortcut menu. The Please confirm you will Create Diffuse Group dialog box is displayed. Confirm whether to create a diffusion group. Step 9 Click Yes to create the diffusion group. Step 10 In the Operation Result list, view whether the group is successfully created after the creation is complete.
NOTE
After the diffusion group is successfully created, the icon of the initial node NE changes to
After the diffusion group is successfully created, the system automatically assigns a number for this group. You can view the group number in the Diffuse Group field of the operation list.
----End
4.3.2 Querying the Diffusion Relation

Before loading a software package in the diffusion mode, you need to query the diffusion relation between NEs and learn the initial node of the diffusion and the diffusion path. During the loading, you can load the software package to the initial node only. The initial node NE automatically diffuses the software package to downstream nodes according to the diffusion path.
Prerequisite
l
The desired NE supports package diffusion, and the current status is normal. A diffusion group must be created. The desired NE must be logged in and communicate normally. The desired NE must be created by using the ToolKit. The computer where the ToolKit is installed must communicate normally with the NE. The NE must support this function.
l l l l
4-10
4 Loading Software
Context
NOTE
After the loading in the diffusion mode is started, if you already perform Rollback on the initial node NE, you cannot query the diffusion relation.
Procedure
Step 1 Choose Load Software > Load Software Package from the Main Menu. The NEs and boards that have been added in the Navigation Tree are displayed. Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Right-click the desired NE and a shortcut menu is displayed. Step 6 Choose Query Diffuse Connection... from the shortcut menu and the Diffuse Connection dialog box is displayed. Step 7 In the Object area, view the information such as NE name, NE type, and upstream nodes.
NOTE
Focus on the NE that serves as the initial node. During loading, you can load the software package to the initial node only.
Step 8 In the Diffuse Connection area, view the diffusion path of the NE. ----End
4.3.3 Loading a Software Package in Diffusion Mode

Loading a software package can load all the software defined in the package format to NEs. For NEs that support package diffusion, you can load the software package to the initial node NE only. The initial node NE automatically diffuses the software package to downstream nodes according to the diffusion relation. This greatly improves the loading efficiency.
Prerequisite
l l l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The software package to be loaded must match the target NE. A diffusion group must be created for the desired NE. The desired NE supports diffusion loading of software packages. The NE must run on a platform of OSP 10 or a later version.
Issue 01 (2008-02-25)
4-11
4 Loading Software
Context
NOTE
During diffusion loading, the software package is loaded to all the NEs in a diffusion group. The system provides a separate navigation path for deleting an NE database or a board database. You can manually delete the NE database or the board database. Refer to 6.8 Deleting an NE Database Manually.
Procedure
Step 1 Refer to Creating a Diffusion Group to create a diffusion group of NEs. Step 2 Refer to Querying Diffusion Relation to query the initial node and diffusion path of the diffusion group. Step 3 In the operation list, select the initial node NE of the diffusion group, and select the desired protocol from the Protocol drop-down list. In the event of ECC networking, select ECC. Refer to ECC and IP over DCC.
NOTE
After a diffusion group is created, the Protocol field of a non-initial node NE becomes . In this case, a loading protocol of this NE cannot be set. By default, all NEs in the group use the protocol of the initial node NE.
Step 4 In the Upgrade Version field, click . Select the desired software package in the dialog box displayed. The path to be accessed cannot contain non-alphanumeric characters.
NOTE
l l l l
refer to ECC and IP over DCC. If the file path contains non-alphanumeric characters, you may fail to access the file. If you do not select File on FTP Server, you can access the files on the ToolKit Server. If you select File on FTP Server, enter the address, user name, password and port of the FTP server, . After the ToolKit is successfully connected to the FTP server, you can access and then click the files on the FTP server.
Step 5 Click Start to start loading the software package to the SCC board of the NE.
NOTE
During loading, you can click Rollback to perform a rollback operation.
The window displays the copy progress, and the NE status is Copying Files. After the copy is complete, the NE status changes to Undispensed. Step 6 Click Dispense to dispense the software package that is loaded to the SCC board of the NE to each desired board on the NE.

NOTE
4 Loading Software
During loading, you can click Rollback to perform a rollback operation. The window displays the dispense progress, and the status is Dispensing.
Step 7 After the dispense is complete, click Activate. The Warning dialog box is displayed. Step 8 Click Yes to start activating the software.
NOTE
During loading, you can click Rollback to perform a rollback operation.
Step 9 Click Commit. The window displays the committing progress, and the NE status is Committing. After the commission is complete, the NE status changes to Normal-Unstable. The loading is successful.
NOTE
After you click Commit, you cannot perform the rollback operation and the software of lower levels on the NE is cleared.
----End
4.4 Loading the Simulation Software Package

To load a set of software to an NE whose mapping relations between boards and software are defined according to the format of a simulation software package, you can use the function of loading the simulation software package to improve the efficiency. 4.4.1 Comparing Software Versions You can compare software versions to view the detailed difference between the version of software that is running on the NE and the version of software to be upgraded. 4.4.2 Database Backup Setting NE upgrading has potential risks, so you must manually back up the database on the NE to a local or remote computer before upgrading. Loading simulation software package supports automatic NE database backup. If you set an automatic backup task, the NE automatically backs up the NE database file to the ToolKit server or FTP server before loading the software. 4.4.3 Rollback Software Setting If an anomaly occurs when the simulation software package is being loaded or activated on an NE, you can use the software package whose version is consistent with the version before loading to perform rollback and restore the software that runs on the NE to the version before loading. 4.4.4 Setting the Activation Order You can set groups for NE activation or board activation to activate NEs or boards in order. 4.4.5 Loading a Simulation Software Package to an NE When a simulation software package is being loaded, the ToolKit automatically copies the software in the software package to the target board. Set a software package whose version is consistent with the version of the running software for rollback before upgrading. 4.4.6 Generating Upgrade Reports You can view details of the upgrade process by viewing the upgrade report.
Issue 01 (2008-02-25)
4-13
4 Loading Software
4.4.1 Comparing Software Versions

You can compare software versions to view the detailed difference between the version of software that is running on the NE and the version of software to be upgraded.
Procedure
Step 1 Set the upgrade software package for an NE. Step 2 Right-click an NE and choose Version Compare from the shortcut menu. The detailed comparison information is displayed. Step 3 Select a board and view the changes between the versions before and after upgrading.
NOTE
l l l l
If the board is not upgraded this time, only the version of the running software is displayed. If new software needs to be loaded on the board, the version of software to be loaded and the version of running software are displayed. The version of the software that is running on the board contains the version information of the software, such as BdSoft, ExtBios, and Fpga. The version of the software to be loaded contains version information of the specific file in the software package to be loaded.
Step 4 Click OK to close the window.

NOTE
Click Refresh to update the comparison information.
----End
4.4.2 Database Backup Setting

NE upgrading has potential risks, so you must manually back up the database on the NE to a local or remote computer before upgrading. Loading simulation software package supports automatic NE database backup. If you set an automatic backup task, the NE automatically backs up the NE database file to the ToolKit server or FTP server before loading the software.
Context
By default, the ToolKit backs up the database to the path as follows: ***/server/databack/NEName/NE-Name_yymmdd_hhmmss/.
l l
*** is the installation path of the ToolKit. NE-Name/NE-Name_yymmdd_hhmmss is the folder that the ToolKit automatically creates. NE-Name indicates the NE name, yyyymmdd indicates the date, and hhmmss indicates the backup time.
If the ToolKit fails to back up the NE database to the default path, it automatically backs up the NE database to the FTP server, and the back up path is ***/databack/NE-Name/NEName_yymmdd_hhmmss/. *** is the FTP server path. databack/NE-Name/NEName_yymmdd_hhmmss is the path that the ToolKit automatically creates.
4-14
Issue 01 (2008-02-25)

NOTE
4 Loading Software
The FTP server must be on the same computer as the ToolKit server. That is, make sure that the FTP server status displayed on the current terminal user interface is .
If the FTP server status is server and re-load the NE database.
, the backup may fail. In this case, you must start the FTP
Hence, you must start the FTP server before loading to guarantee the backup continuity. For details, refer to Setting FTP Parameters.
NOTE
If the NE upgrading fails or becomes abnormal, the backup data is restored to the NE. After the upgrading is complete, the backup data is automatically deleted. Do not manually delete the backup data and do not shut down the FTP server before upgrading.
Procedure
Step 1 Select the desired NE from the operation list, and click Advance. A drop-down menu is displayed. Step 2 Choose Database Backup Setting... from the drop-down menu and the Database Backup Setting dialog box is displayed. Step 3 Select the Auto backup database option button. Step 4 Click OK. ----End
4.4.3 Rollback Software Setting

If an anomaly occurs when the simulation software package is being loaded or activated on an NE, you can use the software package whose version is consistent with the version before loading to perform rollback and restore the software that runs on the NE to the version before loading.
Parameters
Field NE Name NE Type Board Name Rollback Software File Version Value For example: NE35 For example: OptiX OSN 3500 For example: ssn1sl16 For example: 5.21.13.10T03 For example: 5.21.17.10 Description Displays the NE name. Displays the equipment type of the NE. Displays the name of the board. Displays the version of the software to be rolled back. Displays the version information of the software.
Issue 01 (2008-02-25)
4-15
4 Loading Software
Procedure
l Set NE rollback software. 1. 2. 3. 4. 5. Select the desired NE from the operation list, and click Advance. A drop-down menu is displayed. Choose Rollback Setting... from the drop-down menu and the Rollback Software Setting dialog box is displayed. In the Rollbacking Software column, click Choose File dialog box is displayed. that corresponds to the NE. The
In the Choose File dialog box, select the software package for rollback. In the Rollback Software Setting dialog box, click OK.
NOTE
To clear the added software, click Clear software.
Set board rollback software. Board rollback means to set rollback software for each board. During rollback on an NE, loading and activation are performed only on the boards for which rollback software is set. 1. 2. 3. 4. 5. 6. 7. Select the desired NE from the operation list, and click Advance. A drop-down menu is displayed. Choose Rollback Setting... from the drop-down menu and the Rollback Software Setting dialog box is displayed. Click to extend the board list.
In the Rollbacking Software column, click that corresponds to the board. The Board Rollback Software Setting window is displayed. Click Add.... The Choose File dialog box is displayed. In the Choose File dialog box, select the software package for rollback. In the Board Rollback Software Setting window, click OK.
NOTE
l l
The Auto in the Software Type means that the ToolKit can automatically recognize this software type. If the software type is not Auto, you must verify the software type and choose the correct software type from the drop-down list of the Software Type field. Otherwise, an error may occur during rollback.
8.
In the Rollback Software Setting window, click OK.

NOTE
To clear the added software, click Clear Selected.
----End
4.4.4 Setting the Activation Order

You can set groups for NE activation or board activation to activate NEs or boards in order.
4-16
Issue 01 (2008-02-25)
4 Loading Software
Parameters
Field NE Name NE Type Slot ID Board Name Group Activate Order Board Activate by Group Sequence NE Activate Sequence Value For example: NE35 For example: OptiX OSN 3500 For example: 6 For example: ssn1sl16 For example: osn For example: 1 Description Displays the NE name. Displays the equipment type of the NE. Displays the slot ID of the board. Displays the name of the board. Displays the group of the board activation. Displays the order of the NE activation. If this option is selected, group and order are set for board activation. If this option is selected, group and order are set for NE activation.
Procedure
l Set the order for NE activation.
NOTE
If several NEs cannot be activated at the same time, you can set the group and priority of activation for them. Setting the activation order for an NE automatically cancels the setting of activation order of boards on the NE.
1. 2. 3. 4.
Select multiple desired NEs from the operation list, and click Advance. A drop-down menu is displayed. Choose Activate Order... from the drop-down menu and the Activate Order Setting dialog box is displayed. Click NE Activate Sequence and the NE Activate Sequence Setting window is displayed. In the Activate Order field, enter the value of the activation order.
NOTE
l l l
Enter an integer that is in the range of 1 to 9999. The smaller value indicates higher priority of activation. You can set the same activation order for multiple NEs, but you must evaluate whether there are interference between the NEs to be activated at the same time. Deleting this value cancels the activation order of the NE.
Issue 01 (2008-02-25)
4-17
4 Loading Software
5. l
Click OK. The activation order of each NE is displayed in the Activation Order field of the main window.
NOTE
Set the order for board activation.

The setting of board activation order supports grouping of boards on a single NEs and grouping of boards on different NEs. If you set the order of board activation, the existing activation order of NEs is automatically cancelled. You can set the board activation order for only NEs on which the board icons support resetting.
1. 2. 3. 4.
Select multiple desired NEs from the operation list, and click Advance. A drop-down menu is displayed. Choose Activate Order... from the drop-down menu and the Activate Order Setting dialog box is displayed. Click Board Activate by Group Sequence and the Board Activate Sequence Setting window is displayed. Click Create Group... and create the grouping information one by one under the Activate Order node.
NOTE
Under the Activate Order node, the group displayed in an upper location has a higher activation priority. That is, the nearer to the Activate Order node, the higher priority the group has. You can click Up or Down to adjust the activation priority for each group.
5.
In the board list, select the group that the desired board belongs to from the drop-down list of the corresponding Group field.
NOTE
l l l
Repeat the step to set the activation orders for other boards. Do not set two SCC boards or two cross-connect boards on the same NE to the same activation group. To change the activation order of a board, right-click the board and add it to another group.
6. ----End
Click OK. The activation order of each board is displayed in the Activation Order field of the main window.
4.4.5 Loading a Simulation Software Package to an NE

When a simulation software package is being loaded, the ToolKit automatically copies the software in the software package to the target board. Set a software package whose version is consistent with the version of the running software for rollback before upgrading.
Prerequisite
l l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE must support this function. The software package to be loaded must match the target NE. The FTP server must be started before the loading.
4-18
4 Loading Software
Context
NOTE
During loading, when Abnormal is displayed, you can right-click and choose Refresh from the shortcut menu. In this way, the NE status returns to Normal. The system provides a separate navigation path for deleting an NE database. You can manually delete the NE database. Refer to 6.8 Deleting an NE Database Manually.
Procedure
Step 1 Choose Load Software > Board and Software Package (Simulation) from the Main Menu. The NEs that have been added to the Navigation Tree are displayed. Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 In the NE list, right-click an NE and choose Query Board from the shortcut menu. Query the information of the NE.
NOTE
Step 5 Click
before the NE to collapse the board list of the NE. . The information about the NE is displayed in the operation
Step 6 Select an NE and click list.
Step 7 Optional: In the operation list, click of all boards. Step 8 In the Upgrade Version field, click
to expand the board list. You can view the information
. The Software Package Setting window is displayed.
Step 9 Click Select package.... The Choose File window is displayed. Step 10 In the Choose File window, select a file to be loaded.
NOTE
l l l l
Step 11 In the Software Package Setting window, confirm the software to be loaded, and click OK.
4 Loading Software
NOTE
If you select Compel Loading, the ToolKit performs the loading regardless of whether the version of the software to be loaded matches the version of the software running on the NE. If you do not select this option, the ToolKit skips this operation. After you select the software package, the ToolKit loads all the software in the package to the NE by default. If you need not to load some specific software, do not select the corresponding Is Load option button.
Step 12 In the operation list, select an NE and click Start. During the loading, the status of the NE and the corresponding board is Loading. When the loading is complete, the status becomes Loaded.
NOTE
If you do not set the parameters of some functions below the Advance button, the ToolKit prompts a dialog box, indicating possible operation risks. You can decide whether to set these parameters according to the actual situation.
l
Choose Advance > Activate Order... to group and sequence the NEs or boards to be activated. When the GNE is activated, the NEs connected to the GNE may fail to communicate with the GNE. Therefore, you need to set a reasonable activation order for the GNE (especially the SCC board). Choose Advance > Rollback Setting... to set a path for the software rollback. Choose Advance > Database Backup setting... to set whether the NE database file is automatically backed up before being loaded. During the process of backing up the database, you may need to use the FTP server. If the FTP server is not started, the backup procedure may fail. Hence, to ensure that the loading operation is smoothly performed, you need to start the FTP server before the loading.
l l l
Step 13 When the loading is complete, click Activate. The Warning dialog box is displayed. Step 14 Click Yes to start activating the software. Step 15 When the activation is successful, click Finish to confirm that the load operation is complete. Once you click Finish, the rollback is unavailable.
NOTE
After the activation is complete, observe the NE for a period (for example, 24 hours) to make sure that the NE is running normally and then perform this step.
----End
Related Topics
4.1 Loading Board Software
4.4.6 Generating Upgrade Reports

You can view details of the upgrade process by viewing the upgrade report.
Prerequisite
In the defined time period, you have successfully performed the loading operations by using the ToolKit and have not deleted the log information.
Context
When setting the time range for generating the upgrade report, pay attention to the following:

l l
4 Loading Software
The start time must be earlier than the current system time. The end time must be an exact time during the next calendar month of the start time.
Procedure
Step 1 Choose Report > Upgrade Report from the Main Menu, and the Upgrade Report dialog box is displayed.
Step 2 Set the start time and end time. Step 3 Select the NEs included in the upgrade report from the NE not Selected list.
NOTE
l l
In the NE not Selected list, you can double-click an NE to add it to the NE Selected list. In the NE Selected list, you can double-click an NE to delete it.
Step 4 Click Generate to..., and the Save File dialog box is displayed. Step 5 Set the path and name of the file to be saved. Step 6 Click Save, and the Operation Result dialog box is displayed. Step 7 Click Close. Step 8 In the Upgrade Report dialog box, click Cancel to close it.
NOTE
When the operation is successful, you can view the generated upgrade report in the directory where you save the file.
----End
4.5 Loading Board Patch Software

The patch software is a supplement to the NE software or other board software. You can use the patch software to fix bugs of the mentioned software or to enhance the performance of an NE.
4 Loading Software
Prerequisite
l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The loading patch software version must match that of the NE software. Otherwise, the loading operation fails. The NE must support this function. The software package to be loaded must match the target NE.
l l
Context
NOTE
indicates that the NE supports loading only patch packages. indicates that the NE supports loading only board patches. You can learn whether an NE supports loading board patches only after logging in to the NE. The patch software supports upgrade loading only, instead of repeated loading or downgrade loading. During loading, when Abnormal is displayed, you can right-click and choose Refresh from the shortcut menu. In this way, the NE status returns to Normal.
Procedure
Step 1 Choose Load Software > Load Patch Software from the Main Menu. The NEs and boards that have been added to the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 In the NE list, right-click an NE and choose Query Board from the shortcut menu. Step 5 Expand all boards of the NE, select the board to be loaded, and click about the desired NE is displayed in the operation list.
NOTE
. The information
Step 6 In the operation list, select a board and click in the Patch File field. The Choose File dialog box is displayed. Select the software that you want to load. The path to be accessed cannot contain non-alphanumeric characters.
4-22
Issue 01 (2008-02-25)

NOTE
4 Loading Software
l l l l
Step 7 Click Start to begin to load a patch.

NOTE
l l l l
After the loading starts, a progress bar is displayed indicating the loading progress. The status is Loading. When the status changes to Loaded and Unactivated, the loading is complete. During the process, you can click Stop to stop the loading. During the process, you can click Rollback to roll back the NE to the status before the loading. In some cases, the Normal-Unstable status is displayed in the user interface of the ToolKit. For example, when a rollback operation is performed after of a failure of file copying, the user interface displays Normal-Unstable. The Normal-Unstable status persists for a period, and then the NE becomes Normal.
Step 8 After the loading is complete, click Activate to activate the patch software.
NOTE
You can click Rollback to perform a rollback operation.
Step 9 Click Finish to complete the patch upgrade.

NOTE
After you click Finish, the NE rolls back to the status before the loading if the upgrade fails. After you click Finish, you cannot perform the rollback operation if the upgrade succeeds. The NE status is Normal.
----End
4.6 Loading an NE Level Patch Package

Loading patch package is to integrate all the patch software to be loaded. Each patch software corresponds to a type of board and is encapsulated according to a certain definition to form a patch package. The ToolKit loads the desired patch package that is selected by the upgrade personnel to the NE, and then the NE issues a command to load the patch to the memory of the corresponding board.
Prerequisite
l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. Make sure the version mapping between the patch software package to be loaded and the NE software is correct.
Issue 01 (2008-02-25)
4 Loading Software
l l
The NE must run on a platform of OSP 10 or a later version. The NE supports this function.
Context
NOTE
indicates that the NE supports loading only patch packages. indicates that the NE supports loading only board patches. You can learn whether an NE supports loading patch packages only after logging in to the NE. The patch software supports upgrade loading only, instead of repeated loading or downgrade loading.
Procedure
Step 1 Choose Load Software > Load Patch Software from the Main Menu. The NEs and boards that have been added in the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
in the Patch File field. The Choose File dialog Step 5 In the operation list, select an NE and click box is displayed. Select the desired software. The path to be accessed cannot contain nonalphanumeric characters.
NOTE
l l l l
Step 6 Click Start to start loading a patch.

NOTE
After the loading starts, the window displays the loading progress, and the status is Loading. When the status changes to Loaded and Unactivated, it indicates that the loading is complete.
Step 7 After the loading is complete, click Activate to activate the patch software package.
4-24
Issue 01 (2008-02-25)

NOTE
4 Loading Software
You can click Rollback to perform a rollback operation. After the activation starts, the window displays the activation progress, and the status is Activating. When the status changes to Activated, it indicates that the activation is complete. By default, the system automatically makes a submission in 24 hours of activation. After the submission, the NE status changes to Normal. In some cases, the Normal-Unstable status is displayed in the user interface of the ToolKit. For example, when a rollback operation is performed after of a failure of file copying, the user interface displays NormalUnstable. The Normal-Unstable status persists for a period, and then the NE becomes Normal.
----End
Issue 01 (2008-02-25)
4-25
5 Managing the NE License File
5
About This Chapter
Managing the NE License File
You can use the OptiX ToolKit to back up the License file of an NE to a computer, or to load the License file of a computer to an NE. 5.1 Querying the NE License File In the ToolKit, you can view the detailed information of the NE license file, including license serial number, creator, creation time, and effective date. 5.2 Backing Up the NE License File To prevent the License loss in the event of an equipment failure, you need to back up the License for the equipment that requires a License to manage. It is recommended that you back up the License immediately after the License of the equipment is updated. 5.3 Loading the NE License File The License file of the equipment may be lost or unavailable because of an equipment failure. You need to restore the License file that is previously backed up to the equipment. To update the License file of a piece of equipment, you also need to use the function of NE License loading.
Issue 01 (2008-02-25)
5-1
5.1 Querying the NE License File

In the ToolKit, you can view the detailed information of the NE license file, including license serial number, creator, creation time, and effective date.
Prerequisite
l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. NEs support license file management.
Procedure
Step 1 Choose License Management > License File Management from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Select an NE from the operation list and click Query. The license file information is displayed in the lower part of the Operation result field. ----End
Related Topics
5.2 Backing Up the NE License File 5.3 Loading the NE License File
5.2 Backing Up the NE License File

To prevent the License loss in the event of an equipment failure, you need to back up the License for the equipment that requires a License to manage. It is recommended that you back up the License immediately after the License of the equipment is updated.
Prerequisite
l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE can be managed by the License file.
Context
Part of the Huawei optical network equipment can be managed by License. With the License, you can control the authorities of the functions that are realized by NEs. The NE License resides
on the SCC board, and each NE has only one License. The applicable functions of an NE vary with the authority of the License. To back up the License file is to copy the License file to a specified directory and then save the License file.
Procedure
Step 1 Choose License Management > License File Management from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Select Backup from the Backup/Load drop-down list.
Step 6 Click box.

NOTE
in the File field, and then select the path of the files you want to back up in the dialog
l l l l
Step 7 Click Start. The ToolKit copies the License file to the specified directory, and creates the NEName_License.lcs file. "NE-Name" represents the name of the NE, for example, NE3500_License.lcs. ----End
Related Topics
5.1 Querying the NE License File 5.3 Loading the NE License File
5.3 Loading the NE License File

The License file of the equipment may be lost or unavailable because of an equipment failure. You need to restore the License file that is previously backed up to the equipment. To update the License file of a piece of equipment, you also need to use the function of NE License loading.
Prerequisite
l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE can be managed by the License file. The ESN in the License file that you want to load must match the NE ESN.
Context
To load an NE License file is to copy the existing License file to an NE and then activate the file. When the loading is successful, the new License file replaces the original License file on the equipment and is automatically synchronized to the standby SCC board. When the copy is complete, the NE automatically activates the License file. During the activation, the NE checks the License file to be loaded. If the authority of the License file is lower than that of the currently used License file, the NE reports this event to the ToolKit. The ToolKit then prompts a dialog box, asking you whether to update the License. If you select to continue the loading, the new License replaces the one currently used on the NE. If you select to cancel the loading or do not make any choice within 15 minutes, the loading stops and the rollback starts. In this case, the License file of the NE is not replaced.
Procedure
Step 1 Choose License Management > License File Management from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Select Load from the Backup/Load drop-down list.
Step 6 Click
5-4
in the File field, and select the License to be loaded in the dialog box displayed.

NOTE
l l l l
Step 7 Click Start. Step 8 Click Yes in the dialog box displayed. The ToolKit starts to load the License.
NOTE
l l l
When the loading starts, the NE status is switched to Copying. And when the copying is successful, the NE status becomes Normal. If you select to cancel the operation in the dialog box during the loading, the ToolKit starts to roll back. the NE status becomes Rollback. If the loading or rollback fails, the NE status becomes Abnormal. If the loading fails, you can try to reload the License.
----End
Related Topics
5.1 Querying the NE License File 5.2 Backing Up the NE License File
Issue 01 (2008-02-25)
5-5
6 NE Data Backup and Restoration
NE Data Backup and Restoration
About This Chapter

As the upgrade operation may affect the configuration data in an NE, you need to back up the data before the upgrade, so that you can restore the data to the NE in the event of an upgrade exception. The ToolKit provides the manual and scheduled NE database backup functions. 6.1 Backing Up Configuration Data To reinforce the security of NE configuration data and prevent configuration data loss after NE failure, you should periodically back up the NE configuration data. 6.2 Backing Up Database Package To reinforce the security of NE database and prevent database file loss after NE failure, you should periodically back up the database file. 6.3 Backing Up Database Periodically You can perform this operation to set the period and time for the NE to automatically back up the database file based on the schedule. 6.4 Backing Up NE Security Logs To improve the reliability of NE security logs, you should periodically back up the security logs on the local or another computer. 6.5 Backing Up NE Operation Logs To improve the reliability of NE logs, you should periodically back up the operation logs on the local or another computer. 6.6 Restoring Configuration Data In the case of configuration data loss after an NE failure or in order to cater for NE maintenance requirements, you can use the restore configuration data function to restore the configuration data that is backed up earlier to the NE memory. 6.7 Restoring Database Package In the case of database file loss after an NE failure or in order to cater for NE maintenance requirements, you can use the restore database package function to restore the database files that are backed up earlier to the NE. 6.8 Deleting an NE Database Manually
Issue 01 (2008-02-25)
6-1
In the software package loading window and the board and simulation package loading window, the system provides a separate navigation path for deleting an NE database. You can manually delete the NE database.
6-2
Issue 01 (2008-02-25)
6.1 Backing Up Configuration Data

To reinforce the security of NE configuration data and prevent configuration data loss after NE failure, you should periodically back up the NE configuration data.
Prerequisite
l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE must support this function.
Context
NOTE
Procedure
Step 1 Choose Backup/Restore > Backup/Restore Configuration Data from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Select Backup from the Backup/Restore drop-down list.
Step 6 Right-click in the File field and choose Select File from the shortcut menu. Select the path of the files you want to back up in the dialog box.
Issue 01 (2008-02-25)
6-3

NOTE
l l l l
Step 7 Click Start to back up the configuration data.

NOTE
l l l l
When the backup starts, the NE status is Copying. When the backup ends, the NE status is Normal. If an exception occurs during the backup, the NE status turns to Abnormal. You can try the backup again. During the process, you can click Stop to stop the backup. When the data is successfully backed up, the ToolKit creates the following file in a specified directory: NE-Name_yyyymmdd_hhmm.dat. "NE-Name" represents the name of the NE. "yyyymmdd" represents the backup time that is accurate to the year, month and day. "hhmm" represents the backup time that is accurate to the hour and minute. For example, NE35_20061122_1122.dat.
----End
Related Topics
6.6 Restoring Configuration Data
6.2 Backing Up Database Package

To reinforce the security of NE database and prevent database file loss after NE failure, you should periodically back up the database file.
Prerequisite
l l l
Context
NOTE
6-4
Issue 01 (2008-02-25)
Procedure
Step 1 Choose Backup/Restore > Backup/Restore Database Package from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 6 Select Backup from the Backup/Restore drop-down list.
Step 7 Click box.

NOTE
l l l l
Step 8 Click Start to back up the database package.
Issue 01 (2008-02-25)
6-5

NOTE
l l l
When the backup starts, the NE status is Copying. When the backup or rollback is complete, the NE status is Normal. If an exception occurs during the backup or rollback, the NE status turns to Normal-Cancelled. You can try the backup again in this case. When the database is successfully backed up, the ToolKit creates the following directory in a specified path: NE-Name/NE-Name_yymmdd_hhmmss/dbf.pkg. "NE-Name" represents the name of the NE. "yyyymmdd" represents the backup time that is accurate to the year, month and day. "hhmm" represents the backup time that is accurate to the hour and minute. If the ToolKit fails to create a directory, an error is prompted. By default, the file name or path contains a maximum of 255 bytes. If the specified path or the NE name is too long, the ToolKit prompts an error.
----End
Related Topics
6.3 Backing Up Database Periodically 6.7 Restoring Database Package
6.3 Backing Up Database Periodically

You can perform this operation to set the period and time for the NE to automatically back up the database file based on the schedule.
Prerequisite
l l l
Context
In order to reinforce the security and simplify the maintenance of the NE database, you need to periodically back up the NE database files so that you can quickly restore data after database failure. The common database backup, however, requires manual operation and cannot satisfy the versatile requirements of users. You can assign periodical backup tasks of different attributes to different NEs according to the actual requirements. After you set the correct and complete information of periodical backup and save the information, the ToolKit automatically backs up the NE database files accordingly. In the case of an NE for which you set a scheduled database backup task, if the NE is in the copying state, you can perform no operations except the query operation.
NOTE
6-6
Issue 01 (2008-02-25)
Procedure
Step 1 Choose Backup/Restore > Timing Backup Database Package from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Select the NE for which you want to back up database, and select the scheduled time in the Cycle field. Step 6 Click box.
NOTE
in the Start Time field, and set the start time in the Time/Date Properties dialog
The ToolKit follows the time displayed on the ToolKit Server to handle the information of the periodical backup task. If the Client and the Server are deployed on different computers, the time displayed on the Client may not be consistent with the time displayed on the Server.
Step 8 Click box.

NOTE
l l l l
Step 9 Click Save to save the settings.The NE status changes from Normal-Unset to Normal-Set.
NOTE
The ToolKit will execute the scheduled task. After the backup starts, the NE status becomes Copying. If an exception occurs during the process, the NE status becomes Abnormal.
----End
Related Topics
7.3 About Backing Up Databases Periodically 6.2 Backing Up Database Package 6.7 Restoring Database Package
6.4 Backing Up NE Security Logs

To improve the reliability of NE security logs, you should periodically back up the security logs on the local or another computer.
Prerequisite
l l l
Procedure
Step 1 Choose Backup/Restore > Backup Log from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 select Security Log for backup from the Log Type drop-down list. Step 6 Select an NE, and select the protocol for backup from the Protocol drop-down list. In the event of ECC networking, select ECC. Refer to ECC and IP over DCC.
Step 7 Click box.
6-8
Issue 01 (2008-02-25)

NOTE
l l l l
Step 8 Click Start to begin to back up security logs. The NE status is Copying. After the backup is complete, the NE status is Normal. ----End
6.5 Backing Up NE Operation Logs

To improve the reliability of NE logs, you should periodically back up the operation logs on the local or another computer.
Prerequisite
l l l
Procedure
Step 1 Choose Backup/Restore > Backup Log from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 select Operation Log for backup from the Log Type drop-down list. Step 6 Select an NE, and select the protocol for backup from the Protocol drop-down list. In the event of ECC networking, select ECC. Refer to ECC and IP over DCC.
Step 7 Click box.

NOTE
l l l l
Step 8 Click Start to begin to back up logs. The NE status is Copying. After the backup is complete, the NE status is Normal. ----End
6.6 Restoring Configuration Data

In the case of configuration data loss after an NE failure or in order to cater for NE maintenance requirements, you can use the restore configuration data function to restore the configuration data that is backed up earlier to the NE memory.
Prerequisite
l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE must support this function. Before using the configuration data file to restore the NE, make sure the configuration data file is correct. Otherwise, the services may be interrupted.
Context
NOTE
Procedure
Step 1 Choose Backup/Restore > Backup/Restore Configuration Data from the Main Menu. The NEs that have been added in the Navigation Tree are displayed.
Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 5 Select Restore from the Backup/Restore drop-down list.
Step 6 Right-click in the File field and choose Select File from the shortcut menu. Then select a path for the files you want to restore in the dialog box.
NOTE
l l l l
Step 7 Click Start and then click Yes in the confirmation dialog box.
NOTE
l l l
During the restoration, the ToolKit automatically copies and activates the configuration data. The NE status becomes Copying, Unactivated, Activating and Normal in turn. If an exception occurs during the restoration, the NE status becomes Abnormal. You can try to restore the configuration data again. When the NE status is Copying, you can click Stop to stop the restoration operation.
----End
Related Topics
6.1 Backing Up Configuration Data
6.7 Restoring Database Package

In the case of database file loss after an NE failure or in order to cater for NE maintenance requirements, you can use the restore database package function to restore the database files that are backed up earlier to the NE.
Issue 01 (2008-02-25)
6-11
Prerequisite
l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE must support this function. The database package you want to restore must be available. Only the data backed up from the specified NE can be restored to the NE.
Context
NOTE
Procedure
Step 1 Choose Backup/Restore > Backup/Restore Database Package from the Main Menu. The NEs that have been added in the Navigation Tree are displayed. to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown in Step 2 Click the Navigation Tree. Step 3 Right-click an NE and choose Login NE from the shortcut menu to log in to the NE. Step 4 Select an NE and click list. . The information about the NE is displayed in the operation
Step 6 Select Restore from the Backup/Restore drop-down list.
Step 7 Click box.
in the File field, and then select an path for the files you want to restore in the dialog
6-12
Issue 01 (2008-02-25)

NOTE
l l l l
Step 8 Click Start to start restoring the database. After the database is restored, the Operation Result dialog box is displayed to report the operation result.
NOTE
When the restoration starts, the NE status is Copying. When the restoration ends, the NE status is Unactivated. If an exception occurs during the restoration, the NE status becomes NormalCancelled. You can try to restore the database again. During the restoration, you can click Rollback to cancel the operation. During the rollback process, the NE status is Rollback. When the rollback is complete, the NE status becomes Normal. If an exception occurs during the rollback, the NE status becomes Normal-Cancelled. During the restoration process, do not issue the reset command to the NE that is in the Copying or Rollback state.
Step 9 Click Close to close the dialog box. Step 10 click Activate and the Warning dialog box is displayed indicating that this operation may interrupt services. Confirm whether to proceed.
NOTE
If you do not activate the software within five minutes after the restoration is successfully complete, the ToolKit automatically rolls back the software and cancels the restoration operation.
Step 11 Click Yes in the confirmation dialog box and the Prompt dialog box is displayed. Confirm whether to automatically apply the configuration data to boards.
NOTE
PTN NEs do not support the function of automatically applying configuration data to boards. In this case, in the Prompt dialog box displayed, select No.
Step 12 Click Yes to start activating the software.

NOTE
During the activation, the NE status is Activating. When the activation is complete, the NE status becomes Normal. If an exception occurs during the activation, the NE status becomes NormalCancelled. During the activation process, the NE is warm reset. If an NE is restoring the database, do not activate the GNE that is connected to the NE.
----End
Related Topics
6.2 Backing Up Database Package 6.3 Backing Up Database Periodically
6.8 Deleting an NE Database Manually

In the software package loading window and the board and simulation package loading window, the system provides a separate navigation path for deleting an NE database. You can manually delete the NE database.
Prerequisite
l l l l
The related NE must be created in the ToolKit. The computer where the ToolKit is installed must communicate with the NE correctly. The NE must support this function. The desired NE or an SCC board is already added to the operation list.
Context
CAUTION
Deleting the database may interrupt services.
Procedure
Step 1 Choose Load Software > Board and Software Package (Simulation) or Load Software > Software Package from the Main Menu. A user interface is displayed. In the operation list of this user interface, right-click an NE or an SCC board. A shortcut menu is displayed.
NOTE
Only the software package loading window and the board and simulation package loading window provide the navigation path for manually deleting the database. For the boards in the Board and Software Package (Simulation) window, only the SCC board provides the navigation path for manually deleting the database.
Step 2 Choose Delete Database from the shortcut menu. The Please confirm you will delete database dialog box is displayed. Confirm whether to delete the database. Step 3 Click Yes. The system starts to delete the database. Step 4 After a period, in the Operation Result area, Remove database completed is displayed. The database is successfully deleted.
6-14
Issue 01 (2008-02-25)

NOTE
During the deletion, the status of the NE or SCC board is Deleting Database. After the deletion, the status becomes Deleted Database. Right-click in the operation list and choose Refresh from the shortcut menu. The NE status becomes Normal. When the database fails to be deleted, the status of the NE or SCC board becomes Delete Database Exceptionally. Right-click in the operation list and choose Refresh from the shortcut menu. The NE status becomes Normal. When the status of the NE or SCC board is Deleted Database or Delete Database Exceptionally, you can perform the Load Software operation. In the Process(%) field, you can view the current progress of deleting the database.
----End
Issue 01 (2008-02-25)
6-15
7 FAQ
7
About This Chapter
This chapter describes methods of handling common problems of the ToolKit.
FAQ
7.1 ECC and IP over DCC ECC and IP over DCC are two means of communication between a gateway NE and an NE. 7.2 Setting the Access Path In this user interface, you can set the read path to the software to be upgraded or to the restored data. You can also set the save path to the NE data to be backed up. 7.3 About Backing Up Databases Periodically The ToolKit allows you to back up databases at a scheduled time. Set a scheduled task, and the ToolKit will automatically back up the database file on the NE. Depending on whether an NE supports the ToolKit server or the FTP server, you can choose to back up the database to the computer where the ToolKit server or the FTP server resides. 7.4 How to Activate the Boards in a Ring Network 7.5 How to Use the Gateway Resources Correctly 7.6 How to Handle the Failures That Occurs on a Small Number of the Boards When a Large Number of Data Are Transmitted in the Concurrent Load 7.7 Whether the Automatic Activation Mode Can Be Used in a Complex Network Upgrade
Issue 01 (2008-02-25)
7-1
7 FAQ
7.1 ECC and IP over DCC

ECC and IP over DCC are two means of communication between a gateway NE and an NE.
Terms
Embedded control channel (ECC) is a communication channel between NEs in the event of ECC networking. The NE ID is the unique identifier of non-gateway NEs in this networking mode. The communication data between NEs are transmitted over the ECC channel. File transfer protocol (FTP) is a standard file transfer protocol in the TCP/IP protocol. In the event of IP networking, you can use FTP to load a software package, back up or restore a database package, periodically back up databases for the NE that supports these operations. FTP server is the third-party access object, which is set in the ToolKit for saving the software to be loaded or the data to be restored. It also serves as a location to back up the NE data. The FTP server can be on the same computer as the ToolKit server or the client, or on a different computer. After you correctly configure the parameters for the FTP server, the ToolKit server can directly access them. NEs in the transport network can also directly or indirectly access them by using the ToolKit server. The ToolKit server is connected with both the transport network and the ToolKit client (also with the FTP server sometimes) to complete the information interaction between the user and the transport network. The ToolKit client, by providing a graphic user interface (GUI), reports the operation request of the user to the ToolKit server, which then sends the command to NEs. The client also receives operation result information from the server and displays it in the GUI in a way that can be understood by the user. For the connection relations between the ToolKit client, ToolKit server, FTP server and transport network, see Figure 7-1, Figure 7-2 and Figure 7-3.
Selecting ECC Protocol and Accessing the ToolKit Server

For example, to back up the database of NE3 to the computer where the ToolKit server resides, the communication modes between the ToolKit and NEs are shown in Figure 7-1 (in the event of ECC networking).
7-2
Issue 01 (2008-02-25)
7 FAQ
Figure 7-1 Selecting ECC protocol and accessing the ToolKit server
Inside the transport network, data between NE3 and GNE1 is transmitted over the ECC channel; while outside the transport network, communication between GNE1 and the ToolKit server is carried out by using the TCP/IP protocol. To back up the database, the database file on NE3 is transferred to GNE1 over the ECC channel, then to the computer where the ToolKit server resides by using the TCP/IP protocol, and finally saved in the computer.
Selecting ECC Protocol and Accessing the FTP Server

For example, to back up the database of NE3 to the computer where the FTP Server resides, the communication modes between the FTP server, ToolKit server and NEs are shown in Figure 7-2 (in the event of ECC networking).
Issue 01 (2008-02-25)
7-3
7 FAQ
Figure 7-2 Selecting ECC protocol and accessing the FTP server
Inside the transport network, data between NE3 and GNE1 is transmitted over the ECC channel; while outside the transport network, communications between GNE1 and ToolKit server, or between the ToolKit server and FTP server are carried out by using the TCP/IP protocol. To back up the database, the database file on NE3 is transferred to GNE1 over the ECC channel, then to the ToolKit server and FTP server in turn by using the TCP/IP protocol, and finally saved in the computer where the FTP server resides. Files between the ToolKit server and FTP server are transferred by using the FTP protocol.
Selecting IP over DCC Protocol and Accessing the FTP Server

For example, to back up the database of NE3 to the computer where the FTP server resides, the communication modes between the FTP server, ToolKit server and NEs are shown in Figure 7-3 (in the event of IP networking).
7-4
Issue 01 (2008-02-25)
7 FAQ
Figure 7-3 Selecting IP over DCC protocol and accessing the FTP server
Both inside and outside the transport network, communications between NE3 and GNE1, GNE1 and ToolKit server, or GNE1 and FTP server are carried out by using the TCP/IP protocol. To back up the database, the database file on NE3 is transferred to GNE1 and the FTP server in turn by using the TCP/IP protocol, and finally saved in the computer where the FTP server resides. Files between GNE1 and FTP Server are transferred by using the FTP protocol.
7.2 Setting the Access Path

In this user interface, you can set the read path to the software to be upgraded or to the restored data. You can also set the save path to the NE data to be backed up.
Accessing the ToolKit Server

The ToolKit server is the default object to be accessed. For the detailed information on the ToolKit server and FTP server, refer to ECC and IP over DCC. Navigate to the Select File window and select the access address from the directory tree.
Accessing the FTP Server

To save the software to be loaded to the FTP server or to back up the data on the FTP server, you must create the connection between the ToolKit server and FTP server. The procedure for creating the connection is as follows: 1. Check whether the FTP server to be connected is started and whether the obtained information, including the IP address, user name, password, and port of the FTP server, is correct. Select the File on FTP Server option button. Enter the information such as the FTP server, user name, password, and port.
2. 3.
Issue 01 (2008-02-25)
7 FAQ
4. 5.
Click to connect to the FTP server. Select the access address from the directory tree of the FTP server.
Common Causes and Solutions of Failure in Connecting to the FTP Server

Cause The FTP server is not started. The information of the server, user name, password or port is incorrect. The FTP server and the ToolKit client are not in the same network segment. Solution Start the FTP server and try again. Make sure that the obtained information is correct. The server address means the IP address of the FTP server. For a computer that has multiple network cards and multiple IP addresses, the IP address of the FTP server must be in the same network segment as the IP address of the ToolKit client. That is, if the address of the ToolKit client is 10.71.*.*, the address of the FTP server must be 10.71.*.*. Otherwise, the connection may fail. The third and the fourth octets can be different. If this is the failure cause, contact the network administrator to solve the problem. The failure is caused by a network configuration or network failure. Contact the network administrator to solve the problem.
7.3 About Backing Up Databases Periodically

The ToolKit allows you to back up databases at a scheduled time. Set a scheduled task, and the ToolKit will automatically back up the database file on the NE. Depending on whether an NE supports the ToolKit server or the FTP server, you can choose to back up the database to the computer where the ToolKit server or the FTP server resides.
ToolKit Does Not Perform Backup at the Scheduled Time

Under normal conditions, if you correctly save the settings of a scheduled task, the ToolKit will begin the backup at the scheduled time. At that time, click Query and the NE status changes from Normal-set to Copying. But sometimes the ToolKit does not perform the backup at the scheduled time until a delay of 0s to 300s elapses. This is because the ToolKit queries scheduled tasks periodically instead of in the real time. It is normal that a delay occurs.
Failed to Delete the Backup Directory After Deleting the Scheduled Backup Task
After the ToolKit uses the FTP protocol to perform a scheduled backup task, cancel the scheduled backup settings. If you immediately delete the backup directory, the system may prompt that
7 FAQ
the file cannot be deleted. The reason is that the FTP server has not released resources. To delete the directory, wait several minutes and then try again.
The Number of Backup Results Retained in the Backup Directory

By default, the ToolKit retains the latest three backup results in the same backup directory. As the later backup tasks delete the previous backup data, you need to back up the previous data in a timely manner. You can modify the number of backup results in the ToolKit configuration file. To achieve this, open the ToolKit.cfg file in the server folder in the installation directory, and modify the value of SAME_DIR_MAX_BAKUP.
7.4 How to Activate the Boards in a Ring Network

In a ring network, when you need to hard reset the boards after the upload, the activation of the boards may interrupt the services. Thus, exercise caution when you perform this operation. In this operation scenario, it is strongly recommended to activate the boards one by one, but not in batches.
7.5 How to Use the Gateway Resources Correctly

The upload sequence is as follows: the non-gateway NEs and then the gateway NEs. In this way, you can minimize the ECC channel competition.
7.6 How to Handle the Failures That Occurs on a Small Number of the Boards When a Large Number of Data Are Transmitted in the Concurrent Load
For the boards where the loading fails, click Reload. Normally, the reloading is successful.
7.7 Whether the Automatic Activation Mode Can Be Used in a Complex Network Upgrade
The application scenarios of the automatic activation mode is special. In this mode, the activation of the boards cannot be controlled. Thus, in a complex network upgrade, the manual activation is strongly recommended.
Issue 01 (2008-02-25)
7-7
A Glossary
A
A Alarm B Back up Board software
Glossary
A visible or an audible indication to notify the person concerned that a failure or an emergency has occurred. See also Event.
A method to copy the important data into a backing storage in case that the original is damaged or corrupted. All kinds of files running on the boards except the SCC board. The board can run properly only on condition that the whole set of board software is loaded.
C Client A kind of terminal (PC or workstation) connected to a network that can send instructions to a server and get results through a user interface. See also server. The data that configures the NE hardware for coordination between this NE and other NEs in the entire network and operation of specified services. Configuration data is the instruction file of NEs, and it is the key for efficient network running. The typical configuration data includes board configuration, clock configuration and protection relationship. To set the basic parameters of an operation object. A "transport entity" which consists of an associated pair of "unidirectional connections" capable of simultaneously transferring information in opposite directions between their respective inputs and outputs. To clear the software of lower levels on the NE. After the committing operation, rollback cannot be performed.
Configuration data
Configure Connection
Commit D
Issue 01 (2008-02-25)
A-1
A Glossary
Database package
A file package that defines all kinds of database files on NE through a file list. ToolKit can implement several database files at one time by backing up or restoring the database package.
Dispense E ECC
To dispense the software package that is loaded to the SCC board of an NE to each desired board on the NE.
Embedded Control Channel. An ECC provides a logical operations channel between SDH NEs, utilizing a data communications channel (DCC) as its physical layer.
F FTP The standard file transfer protocol in the TCP/IP protocol. In IP networking, you can back up or restore a database package through FTP. G GNE and non-gateway NE The NE that serves as a service agent for other NEs and has direct transmission connection of the transport layer with the ToolKit is called a GNE. Other NEs that communicate with the ToolKit through the GNE are called non-gateway NEs. H HFCP Huawei File Copy Protocol. Huawei's customized file transfer protocol. In ECC networking, IP networking and TP4 networking, you can back up or restore a database package through HFCP. Hot patches Some equipment requires long-term uninterrupted operations. When a defect is found in the software, a process of replacing old codes with new codes is performed to solve the defect, without interrupting services (that is, without restarting software modules). These new codes are referred to as hot patches.
I IP address In the TCP/IP protocol, it is used to uniquely identify the address of the communication port, which consists of four bytes in decimal digits, for example, 129.9.161.55. The IP Over DCC follows TCP/IP telecommunications standards and controls the remote NEs through the Internet. The IP Over DCC means that the IP over DCC uses overhead DCC byte (the default is D1D3) for communication. L
IP over DCC
A-2
Issue 01 (2008-02-25)
A Glossary
Load M Mapping Normal-Unstable MML N NE
The process of copying software to an NE and running the software, including two sub-processes: copying and activating.
A procedure by which tributaries are adapted into virtual containers at the boundary of an SDH network. A state in which the NE is unstable. The package loading can be performed only after the NE becomes stable. A language from ITU-T for telecommunications applications. It has a complex natural-language syntax.
Network Element. NE includes the hardware unit and the software running on it. Usually, one NE has at least an SCC (system control and communication) board which responsible for the management and monitoring of the NE. The NE software runs on the SCC board. A unique identifier to which each NE corresponds in a network. In the OptiX transmission equipment, it is specified that the NE ID is a 24-bit binary digit, that is, three bytes. The DIP switch on the SCC board of the NE constitutes the lower 16 bits of the NE ID. The higher eight bits of the NE ID is the extended ID (default value: 9), which is also called the subnet number. The extended ID is typically used to identify different subnets.
NE ID
NE configuration data
The database information stored in the NE memory. Like database package, the NE configuration data is also database information. They differ in that the former is single files, applicable to NEs with NE software version 5.00.6 or higher, whereas the latter is the information in the NE memory, applicable to NEs with NE software 5.00.0 or previous versions.
NE software
All kinds of files running on the SCC board. The SCC board can run properly only on condition that the whole set of NE software is loaded. The range of IP addresses in which the gateway NE will operate. Network Management. In the telecommunication management network structure, the T2000 is located between the NE level and network level, which can supports all functions at NE level and part of the network level management functions. See also T2000.
Network segment NM
O OnlyFpga The field programmable gate array (FPGA) software embedded in the board without CPU. Currently this type of boards are only applied to the Metro 1050.
Issue 01 (2008-02-25)
A-3
A Glossary
Patch software
The patch files of the NE software and board software. After the patch files are downloaded to a board and activated, they will be integrated to the NE software package and board software package, and run together with them.
Procedure Process R Rollback S Script file
A generic term for an action. A generic term for a collection of actions.
Cancel an operation and restore to the status before the operation.
It is the text file describing the physical information and configuration information of the entire network, including the NE configuration file, port naming file, end-to-end configuration file, NE physical view script file, NM information file and service implementation data script file. A list of instructions for performing a specific task or action, written in a scripting language. A menu that is displayed when right-clicking an object's name or icon. Also called a context menu. Also referred to as the network mask off code, it is used to define network segments, so that only the computers in the same network segment can communicate with one another, thus suppressing broadcast storm between different network segments. Subnetwork is the logical entity in the transmission network and comprises a group of network management objects. A subnetwork can contain NEs and other subnetworks. A subnetwork planning can better the organization of a network view.
Script Shortcut menu Subnet mask
Subnet
T T2000 The T2000 is a subnet management system (SNMS). In the telecommunication management network architecture, the T2000 is located between the NE level and network level, which can supports all NE level functions and part of the network level management functions. See also NM. TCP/IP Transmission Control Protocol/Internet Protocol. Common name for the suite of protocols developed to support the construction of worldwide internetworks.
U Upload To report all or part of the configuration data of the NE to the T2000 and overwrite the configuration data saved in the NE layer on the T2000.
A-4
Issue 01 (2008-02-25)
A Glossary
WDM
Wavelength-Division Multiplexing. WDM technology utilizes the characteristics of broad bandwidth and low attenuation of single mode optical fiber, employs multiple wavelengths as carriers, and allows multiple channels to transmit simultaneously in a single fiber.
Issue 01 (2008-02-25)
A-5
B Acronyms and Abbreviations
B
B BIOS BOM D DCC DCN DNI E ECC EMS ESN F FTP H HFCP I ID IP M MAC MO N
Acronyms and Abbreviations
Basic Input/Output System Bill of Material
Data Communication Channel Data Communication Network Dual Node Interconnection
Embedded Control Channel Element Management System Equipment Serial Number
File Transfer Protocol
Huawei File Copy Protocol
Identity Internet Protocol
Media Access Control Managed Object
Issue 01 (2008-02-25)
B-1
B Acronyms and Abbreviations
NE NM NSAP O OSI OSN OSP P P2P PDH S SBS SDH SMTP SNCP SSL T TCP V VLAN VRP W WAN WDM
Network Element Network Management Network Service Access Point
Open Systems Interconnection Optical Switch Network Optical Software Platform
Point To Point Plesiochronous Digital Hierarchy
Synchronous Information Backbone System Synchronous Digital Hierarchy Simple Mail Transfer Protocol Sub-Network Connection Protection Security Socket Layer
Transmission Control Protocol
Virtual Local Area Network Versatile Routing Platform
Wide Area Network Wavelength Division Multiplexing
B-2
Issue 01 (2008-02-25)
Index
Index
A
adding board physical slot ID, 3-10 slot ID, 3-10 application independent, 1-3 integrated, 1-3
L
License backup License, 5-2 load License, 5-4 query License, 5-2 load software package non-diffusion, 4-7 loading software board patch software, 4-21 loading board software, 4-5 simulation software package, 4-18
B
backup backing up database package, 6-4 backup configuration data, 6-3 backup operation log, 6-9 backup security log, 6-8 periodically backup database package, 6-6
N
networking and communication ECC, 1-13 IP, 1-13 OSI, 1-13
C
Creating NE direct login, 3-7 gateway address, 3-7 gateway type, 3-7 NE ID, 3-7 port, 3-7 creating subnet children object, 3-15 remark, 3-15
Q
querying querying board, 3-9 querying board of the selected NE, 3-9
R
restore restore configuration data, 6-10 restoring restoring database package, 6-11
G
generating upgrade reports, 4-20 GUI navigation tree, 3-2 operation list, 3-2 operation result, 3-2
S
search NE, 3-6 starting UNIX, 2-6 Windows, 2-4 switching switching login users, 3-13 switching the ToolKit Server, 3-17 system architecture
I
installing UNIX, 2-4 Windows, 2-3
Issue 01 (2008-02-25)
i-1
Index
hardware architecture, 1-10 software architecture, 1-10
i-2
Issue 01 (2008-02-25)

OptiX ToolKit V1R4C01 User Guide (MML)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

OptiX ToolKit V1R4C01 User Guide (MML)

Загружено:

Авторское право:

Доступные форматы

OptiX Toolkit V100R004C01

Issue Date Part Number

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

2 Installing and Starting the ToolKit........................................................................................2-1

OptiX Toolkit User Guide

5 Managing the NE License File.................................................................................................5-1

6 NE Data Backup and Restoration............................................................................................6-1

OptiX Toolkit User Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX Toolkit User Guide

OptiX Toolkit User Guide

About This Document

Convention Italic Courier New

Description Book titles are in italics. Terminal display is in Courier New.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX Toolkit User Guide

Updates in Issue 01 (2008-02-15) Based on Product Version V100R004C01

Updates in Issue 01 (2007-08-15) Based on Product Version V100R003C01

OptiX Toolkit User Guide

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

OptiX Toolkit User Guide

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

OptiX Toolkit User Guide

Figure 1-2 ToolKit independent of the T2000

1.2 Features and Functions

Loading Board Software

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

Loading Type Loading simulatio n software package

Loading Patch Software

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

Loadin g Type Loading patch package

A patch file has two characteristics as follows:

Loading Software Package

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

On an NE, many boards require loading software.

Loadin g softwa re packag e in diffusi on mode

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX Toolkit User Guide

Loading Simulation Software Package

Backing Up and Restoring NE Configuration Data

Backing Up and Restoring NE Database Packages

OptiX Toolkit User Guide

Generating Upgrade Report

Switching ToolKit Server

Setting the Activation Mode