OptiX ToolKit V1R4C01 User Guide(MML)

7/30/2019 OptiX ToolKit V1R4C01 User Guide(MML)

1/120

OptiX Toolkit

V100R004C01

User Guide

Issue 01

Date 2008-02-25

Part Number 00413725

Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.


2/120

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

Website: http://www.huawei.com

Email: [email protected]

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.

Huawei Proprietary and Confidential

mailto:[email protected]://www.huawei.com/


3/120

Contents

About This Document.....................................................................................................................1

1 Product Description...................................................................................................................1-1

1.1 Application......................................................................................................................................................1-3

1.2 Features and Functions....................................................................................................................................1-41.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

OptiX Toolkit

User Guide Contents

Issue 01 (2008-02-25) Huawei Proprietary and Confidential


i


4/120

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

Contents

OptiX Toolkit

User Guide

ii Huawei Proprietary and Confidential


Issue 01 (2008-02-25)


5/120

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

OptiX Toolkit

User Guide Figures



iii


6/120


7/120

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

OptiX Toolkit

User Guide Tables



v


8/120


9/120

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 Version

OptiX ToolKit V100R004C01

Intended Audience

The intended audience of this document are technical support engineers.

Organization

This document is organized as follows:

Chapter Description

Chapter 1 Product Description Describes the application, characteristics,

performance, software architecture, networking

and communication of the ToolKit.

Chapter 2 Installing and Starting the

ToolKit

Describes how to install and start the ToolKit on

the Windows or UNIX platform.

Chapter 3 Basic Operations Describes the basic operations of the ToolKit

Chapter 4 Loading Software Describes how to load software by using the

ToolKit.

OptiX Toolkit

User Guide About This Document



1


10/120

Chapter Description

Chapter 5 Backing up and Restoring NE

Data

Describes how to back up or restore data by using

the ToolKit.

Chapter 6 Managing NE License File Describes how to back up and load the NELicense file by using the ToolKit.

Chapter 7 FAQ Describes methods of handling common

problems of the ToolKit.

Appendix A Glossary Lists the glossary of this guide.

Appendix B Acronyms and

Abbreviations

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 Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface. For

example, log in as userroot.

About This Document

OptiX Toolkit

User Guide

2 Huawei Proprietary and Confidential


Issue 01 (2008-02-25)


11/120


Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] are

optional.

{ x | y | ... } Alternative items are grouped in braces and separated by

vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.

{ x | y | ... } * 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


Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in

boldface. For example, clickOK.

> Multi-level menus are in boldface and separated by the ">" signs. For

example, choose File > Create > Folder.

Keyboard Operation

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressingCtrl+Alt+A means the

three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys

should be pressed in turn.

OptiX Toolkit




3


12/120

Mouse Operation

Action Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly without

moving the pointer.

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

About This Document

OptiX Toolkit

User Guide

4 Huawei Proprietary and Confidential


Issue 01 (2008-02-25)


13/120

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.

OptiX Toolkit




5


14/120


15/120

1 Product DescriptionAbout This Chapter

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

OptiX Toolkit

User Guide 1 Product Description



1-1


16/120

There are three ways of networking between the ToolKit and NEs: ECC, IP and OSI networking.

1 Product Description

OptiX Toolkit

User Guide

1-2 Huawei Proprietary and Confidential


Issue 01 (2008-02-25)


17/120

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

OptiX Toolkit




1-3


18/120

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

LoadingType

Definition Scenario Operation Method

Loading

board

software

Board software refers to

the software

corresponding to a board

on an NE.

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.

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.


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


19/120

LoadingType

Definition Scenario Operation Method

Loading

simulatio

n

software

package

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.

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.

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

Loading Type

Definition Scenario Operation Method Merits andDemerits

Loading

board

patch

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.

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.

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

.

Loading board

patch

consumes a lot

of time of the

upgrade

personnel.

OptiX Toolkit




1-5


20/120

Loading Type

Definition Scenario Operation Method Merits andDemerits

Loading

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

software

package.

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 thecorresponding

board. After that,

you can use the

press-to-install

function to install

each hot patch to

the

corresponding

board.

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

.

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.

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


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


21/120

Table 1-3 Comparison between loading software package in non-diffusion mode and loading

software package in diffusion mode

Loading

Mode

Definition Scenario OperationMethod

Merits andDemerits

Loadin

g

softwa

re

packag

e in

non-

diffusi

on

mode

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

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

or not.

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

loadingefficiency is low.

Loading

softwa

re

packag

e in

diffusi

on

mode

When loading a softwarepackage 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 softwarepackage 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 softwarepackage 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 cansynchronously

load a software

package to many

NEs of the same

type.

When the

software

package is

synchronously

loaded to many

NEs, only onepackage file is

transmitted in the

network. This

increases the

bandwidth

utilization of the

network and

improves the

loading

efficiency.

OptiX Toolkit




1-7


22/120

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


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


23/120

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.

l Upgrade quantity: includes the total quantity of NEs and boards upgraded.

l Equipment profile: includes the types and quantities of equipment upgraded.

l Software version: includes the software package version and board software version before

and after upgrade.

l

Other information: includes the user used in the upgrade and result of the upgradeavailability check.

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

OptiX Toolkit




1-9


24/120

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 One client can access to only one server each time.

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


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


25/120

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.

OptiX Toolkit




1-11


26/120

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


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


27/120

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 Provides flexible networking modes.

l Uses the standard TCP/IP protocol and ensures easy compatibility with third-party

equipment and simplifies network management.

l Provides good compatibility. IP over DCC can be used with new application layer

forwarding features.

OptiX Toolkit




1-13


28/120

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


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


29/120

2 Installing and Starting the ToolKitAbout 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.

OptiX Toolkit

User Guide 2 Installing and Starting the ToolKit



2-1


30/120

2.1 Installation and Running Environment

The ToolKit is a software product and must be installed in a hardware environment where it canrun 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

ConfigurationItem

Quantity RecommendedConfiguration

Remarks

CPU frequency 1 P4 1.7 GHz Required

Memory 1 256 MB Required. In actual

application, ensure

that the system has a

virtual memory ofover 150 MB.

Hard disk 1 40 GB Required

Network card 1 100 Mbit/s Required. The

ToolKit is accessed

to an optical

transport network

through a network

card.

Operating System 1 Windows XP

Professional

Required

System resolution - 1024 x 768

Table 2-2 Recommended configuration of a workstation

ConfigurationItem


Remarks

CPU frequency 1 UltraSPARC 2 x 1.60

GHz

Required

2 Installing and Starting the ToolKit

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


31/120

ConfigurationItem


Remarks

Memory 1 2 GB Required. In actual

application, ensure

that the system has a

virtual memory of

over 150 MB.

Hard disk 1 2 x 146 GB Required

Network card 1 100 Mbit/s Required. The

ToolKit is accessed

to an optical

transport network

through a network

card.

Operating system 1 Solaris 10 Required

System resolution - 1024 x 768

2.2 Installing the ToolKit On Windows

Uncompress the ToolKit installation package to a specified directory to complete the installation.

ContextNOTE

l The directory name you specify when installing the ToolKit can consist of numerals and characters.

l The ToolKit directory of the compressed package consists of the following subfiles:

l client: including the client application, local logs, configuration information and online Help.

l server: including the server application, system logs.

l ToolKit.bat: including the batch files that are used to start the ToolKit client.

l 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

OptiX Toolkit




2-3


32/120

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 When you enter the local IP address, the local server starts automatically.

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

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

NOTE

l The uncompression command on UNIX: gunzip file name

l 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 theshortcut menu. The Create Action dialog box is displayed.

Step 3 Fill in the blanks according to the following information:

l Action Name (Icon Label): ToolKit

l Command When Action is Opened (Double-clicked): /ToolKit installation path/ToolKit.bat

l Window Type: Graphical(X-Window)


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


33/120

Step 4 Choose File > Save to save the new action (saved in the start directory).

Step 5 ClickOK.

Step 6 Right-click in the blank space of the desktop and choose Files > File Manager from the shortcutmenu.

Step 7 Select the ToolKit file and choose Selected > Move to from the menu to move the ToolKiticon to the installation directory.

OptiX Toolkit




2-5


34/120

Step 8 In the ToolKit installation directory, right-click the ToolKit file and choose Put inWorkspace 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 If the ToolKit icon is created, double-click the icon to run the ToolKit.

l If not, follow the steps below:

1. Right-click in the blank space of the desktop, and choose Tools > Terminal from

the shortcut menu. The Terminal dialog box is displayed.

2. In the ToolKit installation directory, enter the following command and the ToolKit is

started.

----End


OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


35/120

3 Basic OperationsAbout This Chapter

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.

OptiX Toolkit

User Guide 3 Basic Operations



3-1


36/120

3.1 GUI Description

The ToolKit uses the graphic user interface. You can select a function from the Main Menu ofthe 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

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


37/120

Table 3-1 Window component description

Component Description

Navigation Tree The area in which the ToolKit manages NEs.

The NE searched out in the transmissionnetwork is displayed in the root directory of

the Navigation Tree, after the NE is

successfully created.

Menu Choose an item from the menu to display the

corresponding window.

Toolbar Button Click the button to quickly display a window.

Clicking a button equals to clicking a menu

item.

Operation List The area in which the ToolKit performs

operations to NEs. You should add NEs intothe Operation List before setting different

operation tasks to them.

Operation Button After setting the operation tasks, you can

click the corresponding button to perform

different operations.

FTP Server Status 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 thedirectory by using the FTP protocol,

including reading data from the directory and

writing data into the directory.

ToolKit Server IP 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 isencrypted by using SSL; "2" represents that

the current client is the second terminal that

is connected to the server.

NE Information Display the information relates to the current

operation. For example, NE name and

loading progress.

Operation Result Displays the information that is reported

during the execution of tasks.

Client System Time Displays the system time of the computer that

the current Client resides.

OptiX Toolkit




3-3


38/120

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 Description

Exit Exits the current terminal.

Search NE Searches for the NEs for the

specified gateway NE.

Create NE Displays the Add NE dialog

box.

Software Package Displays the Load Software

Packagewindow.

Board and Software Package

(Simulation)

Displays the Board and

Software Package

(Simulation) window.

Patch Displays the Load Patch

Software window.

Backup/Restore

Configuration Data

Displays the Backup/

Restore Configuration

Data window.

Backup/Restore Database

Package

Displays the Backup/

Restore Database Package

window.

Timing Backup Database

Package

Displays the Timing Backup

Database Package window.

Backup Security Log Displays the Backup

Security Log window.

Browse Log Displays the Browse Log

window.

FTP Setting Displays the FTP Setting

dialog box.

Topics Displays the ToolKit Help.

Refresh Refreshes the Navigation

Tree.

3 Basic Operations

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


39/120

Button Name Description

Shrink Collapses the Navigation

Tree.

Expand Expands the NavigationTree.

Add to list Adds the NE or board in the

Navigation Tree to the

operation list.

Key GUI Components

Component Name Description

Available The NE is logged in. The

current function is available.

Not logged in The NE is not logged in.

Logged in, but not supported The NE is logged in. The

current function is not

available.

Available The NE is logged in. The

current function is available.

The NE is Gateway NE.

Not logged in The NE is Gateway NE, but

not logged in.

Logged in, but not supported The NE is logged in. The

current function is not

available. The NE is Gateway

NE.

Logged in, the initial node

NE of the diffusion group

The NE is logged in. support

Loading a Software Package

in Diffusion Mode. and the

NE is the initial node NE ofthe diffusion group.

Logged in, and supported

diffusion

The NE is logged in. and

support Loading a Software

Package in Diffusion Mode

FTP Server Running The FTP Server is running.

FTP Server Stop The FTP Server is stopped.

OptiX Toolkit




3-5


40/120

3.3 NE and Board Management

In the ToolKit, NEs and boards are the most basic operation objects. Before you add NEs andboards 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.


You can search for all NEs of the specified gateway NE by using the NE search function of theToolKit. The NEs are displayed in a form of list. You can add the NE that is searched out into

the Navigation Tree.

Prerequisite

l The computer where the ToolKit is installed must communicate with the NE normally.

l Make sure that you have obtained the port, user name and password of the gateway NE to

be searched.

l 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 ClickSearch, and the ToolKit automatically searches for all gateway NEs and displays them inthe Gateway list.

Step 3 Select the gateway NE to be searched, clickEdit..., and the Gateway Parameter dialog box isdisplayed.

Step 4 In the Gateway parameter dialog box, enter the port, user name and password. ClickOK.

3 Basic Operations

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


41/120

Step 5 ClickStart Search, and the ToolKit begins to search for all NEs of this gateway NE and displaysthem in the result list.

NOTE

You can clickCreate 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 The NE must communicate with the ToolKit client normally.

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

l You must specify the ID for NEs (OptiX BWS 1600G and Metro 500) that are in the BIOS state.

Otherwise, the NE creation fails.

l If you choose Login directly, clickApply to add an NE, this NE ID is the ID number of the previously

created NE plus 1.

lThe real name of the NE is displayed if the NE has a real name. In this case, the NE name that you setis invalid.

OptiX Toolkit




3-7


42/120

Procedure

Step 1 Choose Load Software > Software Package from the Main Menu. The NEs that have beenadded in the Navigation Tree are displayed.

NOTE

l You can also choose other functions to display the ToolKit management window.

l If the Navigation Tree already exists, skip this step.

Step 2 Click to refresh the NE list.

Step 3 Click , 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 markedwith a red * in the dialog box are required to be set.

NOTE

l ClickSearch, 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.

l 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 ClickOKto close the Create NE dialog box.

NOTE

ClickApply to add another NE.

----End

Related Topics


3 Basic Operations

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


43/120


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



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

OptiX Toolkit




3-9


44/120

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 The related NE must be logged in.

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

If the Navigation Tree already exists, skip this step.

Step 2 Click to refresh the NE list. If an NE is not in the NE list, Creating NEs and it is shown inthe Navigation Tree.

Step 3 Right-click the NE in the Navigation Tree and choose Add Board.... The Add Board dialogbox is displayed.

Step 4 Enter the physical slot ID of the board and clickOK.

----End

Related Topics


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

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


45/120

Filter Window

In any window that contains a navigation tree, clickFilter... and the Filter NE/Board window

is displayed.

GUI Description

Field Description

Entire Network Click the option button to filter the objects that are contained under

the root node.

Only Subnet Selected Click the option button to filter NEs or boards in the selected subnet.

Search for Network

Elements

Click the option button to filter NEs.

NE Type Select an NE type from the drop-down list that displays all NE types

under the root node.

NE Name Enter the name of an NE. If you select a correct NE type, the ToolKit

correctly filters the required NE.

Search for Boards Click the option button to filter boards.

Board Type Select a board type from the drop-down list that displays all board

types under the root node.

3.4 Login ManagementThe 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

OptiX Toolkit




3-11


46/120

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.


Before you perform operations to the NE by using the ToolKit, log in to the NE in the Navigation

Tree.

Prerequisite

l The related NE must be created in the ToolKit.

l The computer where the ToolKit is installed must communicate with the NE correctly.

Procedure


NOTE




Step 3 In the NE list, right-click an NE and choose Login NE from the shortcut menu.

NOTE

l The icons of the logged in NEs are shown in green, and the others are in gray.

l If the NE user is used by another application to log in to the NE, your login forces the other application

to log out.

l 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 Basic Operations

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


47/120


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 The related NE must be created in the ToolKit.


Context

NOTE

l To operate NEs by using the ToolKit, make sure that the login user of the NE is a super user.

l When the ToolKit is loading software to the NE, backing up data or restoring data, you cannot modify

the login account.

Procedure


NOTE




Step 3 In the NE list, right-click an NE and choose Set Login Account... from the shortcut menu.

NOTE

l The account you set must already exist at the NE side.

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

----End

Related Topics


OptiX Toolkit




3-13


48/120



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 The NE must be in the logged-in state in the ToolKit.


Context

NOTE

l The NE is logged out automatically when the ToolKit exits.

l When the ToolKit is loading software to an NE, backing up data or restoring data, you cannot log out

of the NE.

Procedure


NOTE




Step 3 In the NE list, right-click an NE and choose Logout from the shortcut menu.

NOTE

l The logged-in NE is shown in green. After you log out of the NE, it is shown in gray.

l 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 Basic Operations

OptiX Toolkit

User Guide



Issue 01 (2008-02-25)


49/120

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 categori

Documents

OptiX ToolKit V1R4C01 User Guide(MML)