OG For Common Features - (V100R002C01 - 03)

iManager U2000 Unified Network Management
System
V100R002C01
Operation Guide for Common

Features
Issue 03
Date 2010-11-19
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. 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 trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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 all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2010-11-19) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
Operation Guide for Common Features About This Document
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager U2000 V100R002C01
Intended Audience
This document describes the operations for common feature on the U2000.
This document guides the user to understand basic operations of the U2000.
The intended audiences of this document are:
l Data Configuration Engineer
l NM Administrator
l System Maintenance Engineer
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
DANGER serious injury.
Indicates a hazard with a medium or low level

of risk which, if not avoided, could result in
WARNING minor or moderate injury.
Issue 03 (2010-11-19) Huawei Proprietary and Confidential iii

About This Document Operation Guide for Common Features
Symbol Description
Indicates a potentially hazardous situation

that, if not avoided, could cause equipment
CAUTION
damage, data loss, and performance
degradation, or unexpected results.
NOTE Provides additional information to emphasize

or supplement important points of the main
text.
TIP Indicates a tip that may help you solve a
problem or save you time.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
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.
[ x | y | ... ] * Optional alternative items are grouped in

square brackets and separated by vertical
bars. A maximum of all or none can be
selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
iv Huawei Proprietary and Confidential Issue 03 (2010-11-19)

Operation Guide for Common Features About This Document
Convention Description
Boldface 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.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Changes in Issue 03 (2010-11-19) Based on Product Version V100R002C01

The third commercial release. It has the following updates:
l In the chapter "Inventory Management", the Relevant Subnet Path parameter is added to
the NE list.
l Other chapters are optimized.

The second commercial release. Updates between document issues are cumulative. Therefore,
the latest document issue contains all updates made in previous issue.

Initial field trial release. It has the following updates:
l In chapter "Getting Started", the steps for starting and shutting down the U2000 system are
optimized, the functions of "Collecting NE Data" is added.
l In chapter "Security Management", section "RADIUS Configuration" is added.
l In chapter "Topology Management", the functions of "Configuring NEs Automatically",
"Querying the Performance Data of a Radio Link" are described.
l In chapter "Alarm Management", some new functions are described, including, the
functions of "Managing the Alarm Maintenance Status", the functions of "Masking All NE
Interface Alarms Quickly", the function of "Downloading Remote Notification Logs", and
the function of "Setting the Default Alarm Correlation Rules".
l In chapter "Inventory Management", the functions of "Querying a PTN Interface Resource
Report" is added.
l In chapter "Keeping Data Consistency Between the U2000 and NEs", the functions of
"Configuration Data Management Specifications of the NA WDM", "Configuration Data
Management Specifications of the NG WDMA" are added.
Issue 03 (2010-11-19) Huawei Proprietary and Confidential v

Operation Guide for Common Features Contents
Contents
About This Document...................................................................................................................iii

1 Getting Started............................................................................................................................1-1
1.1 Precautions for Using the U2000 Safely.........................................................................................................1-4
1.2 Starting the U2000 System..............................................................................................................................1-4
1.2.1 Starting a Single-Server System (Windows)..........................................................................................1-5
1.2.2 Starting a Single-Server System (Solaris)..............................................................................................1-6
1.2.3 Starting the Single-Server System (SUSE Linux-Distributed)..............................................................1-9
1.2.4 Starting the High Availability System (Windows)..............................................................................1-12
1.2.5 Starting the High Availability System (Solaris)...................................................................................1-14
1.2.6 Starting the High Availability System (SUSE Linux-Distributed)......................................................1-17
1.2.7 Logging In to the U2000 Client...........................................................................................................1-18
1.3 Shutting Down the U2000.............................................................................................................................1-21
1.3.1 Shutting Down the U2000 Client.........................................................................................................1-21
1.3.2 Shutting Down the Single-Server System (Windows).........................................................................1-22
1.3.3 Shutting Down the Single-Server System (Solaris).............................................................................1-22
1.3.4 Shutting Down the Single-Server System (SUSE Linux-Distributed).................................................1-24
1.3.5 Shutting Down the High Availability System (Windows)...................................................................1-24
1.3.6 Shutting Down the High Availability System (Solaris).......................................................................1-26
1.3.7 Shutting Down the High Availability System (SUSE Linux-Distributed)..........................................1-27
1.4 Changing the Password of the Current User.................................................................................................1-29
1.5 Using the Workbench and Favorites Folder..................................................................................................1-30
1.5.1 Placing a Shortcut Icon on the Workbench..........................................................................................1-30
1.5.2 Adding a Common Function to the Favorites Folder...........................................................................1-31
1.5.3 Viewing Common Functions...............................................................................................................1-32
1.6 Setting the Parameters for the Communication Between the U2000 and NEs.............................................1-34
1.6.1 Protocols for Communications Between the U2000 and NEs.............................................................1-34
1.6.2 Configuring the Default SNMP Parameters Template.........................................................................1-35
1.6.3 Setting NE SNMP Parameters..............................................................................................................1-37
1.6.4 Configuring a Telnet/STelnet Parameter Template..............................................................................1-38
1.6.5 Setting Telnet/STelnet Parameters with a Template............................................................................1-39
1.6.6 Manually Modifying Equipment Telnet/STelnet Parameters..............................................................1-40
1.7 Setting or Modifying the Character Set of an NE.........................................................................................1-41
1.7.1 Character Set........................................................................................................................................1-41
Issue 03 (2010-11-19) Huawei Proprietary and Confidential vii

Contents Operation Guide for Common Features
1.7.2 Setting or Modifying Character Sets in Batches..................................................................................1-43

1.8 Main Windows and Common Operations of the U2000...............................................................................1-44
1.8.1 Components of the Client GUI.............................................................................................................1-45
1.8.2 Key GUI Components..........................................................................................................................1-46
1.8.3 Frequently Used Buttons......................................................................................................................1-48
1.8.4 Shortcut Icon........................................................................................................................................1-50
1.8.5 Common Shortcut Keys.......................................................................................................................1-55
1.8.6 Main Windows.....................................................................................................................................1-56
1.8.6.1 Workbench........................................................................................................................................1-57
1.8.6.2 Main Topology..................................................................................................................................1-58
1.8.6.3 NE Explorer.......................................................................................................................................1-60
1.8.6.4 Clock View........................................................................................................................................1-61
1.8.6.5 NE Panel............................................................................................................................................1-64
1.8.6.6 WDM NE Signal Flow Diagram.......................................................................................................1-65
1.8.6.7 Browse Alarm...................................................................................................................................1-66
1.8.6.8 Browse Event....................................................................................................................................1-67
1.8.6.9 Browse Performance Window..........................................................................................................1-68
1.8.7 Menu Description.................................................................................................................................1-70
1.8.7.1 File Menu..........................................................................................................................................1-71
1.8.7.2 Edit Menu..........................................................................................................................................1-72
1.8.7.3 View Menu........................................................................................................................................1-73
1.8.7.4 Fault Menu........................................................................................................................................1-74
1.8.7.5 Performance Menu............................................................................................................................1-77
1.8.7.6 Configuration Menu..........................................................................................................................1-78
1.8.7.7 Service Menu.....................................................................................................................................1-83
1.8.7.8 Inventory Menu.................................................................................................................................1-86
1.8.7.9 Administration Menu........................................................................................................................1-88
1.8.7.10 Window Menu.................................................................................................................................1-93
1.8.7.11 Help Menu.......................................................................................................................................1-94
1.8.8 Operations Frequently-Performed on the User Interface.....................................................................1-95
1.8.8.1 Filtering Operation Objects in a View..............................................................................................1-95
1.8.8.2 Moving Operation Objects................................................................................................................1-96
1.8.8.3 Searching for NEs in a View.............................................................................................................1-96
1.8.8.4 Counting the Number of NEs............................................................................................................1-97
1.8.8.5 Customizing Parameter Display........................................................................................................1-98
1.8.8.6 Copying Table Text Quickly.............................................................................................................1-99
1.8.8.7 Setting Board Color...........................................................................................................................1-99
1.8.9 Custom View......................................................................................................................................1-100
1.8.9.1 Creating Custom Views..................................................................................................................1-100
1.8.9.2 Setting Startup subnet......................................................................................................................1-101
1.9 How to Obtain Version Information About the U2000...............................................................................1-101
1.10 Customizing the Client GUI Effect...........................................................................................................1-102
viii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

1.10.1 Setting the Font Size........................................................................................................................1-103

1.10.2 Setting the Skin................................................................................................................................1-104
1.10.3 Setting the Output Information........................................................................................................1-104
1.10.4 Setting the Time and Date Formats of the Client.............................................................................1-106
1.10.4.1 Setting the Time Format of the Client...........................................................................................1-106
1.10.4.2 Setting the Date Format of the Client............................................................................................1-107
1.10.4.3 Setting the Time Mode of the Client.............................................................................................1-108
1.10.5 Setting the Workbench.....................................................................................................................1-109
1.10.6 Set the Menu Collapse......................................................................................................................1-112
1.10.7 Setting the Number Format of the Client.........................................................................................1-113
1.10.8 Setting the Alarm Display in the Topology View............................................................................1-114
1.10.9 Setting the Topology View Display.................................................................................................1-116
1.10.10 Setting Prompt Colors of Alarms...................................................................................................1-118
1.10.11 Setting the Alarm Highlight...........................................................................................................1-118
1.10.12 Setting the Alarm Font...................................................................................................................1-119
1.10.13 Setting the Alarm Display Mode....................................................................................................1-120
1.10.14 Setting the Display Property of a New Alarm/Event.....................................................................1-122
1.10.15 Setting the Toolbar.........................................................................................................................1-123
1.11 Setting the Alarm Sound at Network Disconnection................................................................................1-123
1.12 Checking Whether the Client Needs Upgrade..........................................................................................1-124
1.13 Setting the Interval of Client Upgrade Check...........................................................................................1-125
1.14 Locking the Client.....................................................................................................................................1-125
1.15 Unlocking the Client.................................................................................................................................1-126
1.16 Setting a Scheduled Task..........................................................................................................................1-127
1.17 Broadcast Messages..................................................................................................................................1-127
1.17.1 Setting Broadcast Parameters...........................................................................................................1-128
1.17.2 Sending Broadcast Messages...........................................................................................................1-128
1.18 Applying for and Updating the License....................................................................................................1-129
1.18.1 U2000 License Precautions..............................................................................................................1-130
1.18.2 Applying for the U2000 License......................................................................................................1-131
1.18.3 Updating the U2000 License............................................................................................................1-132
1.18.4 Checking the Status of the U2000 License......................................................................................1-137
1.18.5 Setting the Threshold of the Accessing NEs....................................................................................1-138
1.18.6 Verifying the U2000 License...........................................................................................................1-138
1.19 Starting the Web Client.............................................................................................................................1-139
1.20 Collecting NE Data...................................................................................................................................1-139
1.21 Customizing Naming Rule........................................................................................................................1-140
1.22 U2000 Process List....................................................................................................................................1-142
1.23 Rules for Entering Information on User Interface.....................................................................................1-158
1.24 Mutual Exclusion List for Multiclient Operations....................................................................................1-160
2 Network Management Process................................................................................................2-1

2.1 Access Network Management Process........................................................................................................... 2-2
Issue 03 (2010-11-19) Huawei Proprietary and Confidential ix

2.2 MSTP Network Management Process............................................................................................................2-4

2.3 WDM Network Management Process.............................................................................................................2-5
2.4 RTN Network Management Process...............................................................................................................2-8
2.5 PTN Network Management Process...............................................................................................................2-9
2.6 Security Equipment Network Management Process.....................................................................................2-10
2.7 Router Network Management Process..........................................................................................................2-10
2.8 Switch Network Management Process..........................................................................................................2-11
3 Security Management................................................................................................................3-1
3.1 Security Management Strategy.......................................................................................................................3-3
3.1.1 User Security Policy...............................................................................................................................3-4
3.1.2 Log Management Policy........................................................................................................................3-6
3.1.3 Database Security Policy........................................................................................................................3-7
3.1.4 NE Security Management......................................................................................................................3-7
3.2 Setting Security Policies of U2000 Users.......................................................................................................3-9
3.2.1 Setting the U2000 Login Mode..............................................................................................................3-9
3.2.2 Setting the Access Control List............................................................................................................3-10
3.2.3 Setting the Password Policy.................................................................................................................3-12
3.2.4 Setting the Account Policy...................................................................................................................3-13
3.3 Creating U2000 Users and Assigning Permissions.......................................................................................3-13
3.3.1 Procedure for Creating U2000 Users...................................................................................................3-14
3.3.2 Example for Creating User Accounts and Assigning Rights in the Authority- and Domain-based
Management Scenario...................................................................................................................................3-15
3.3.3 Creating an Object Set..........................................................................................................................3-18
3.3.4 Creating an Operation Set....................................................................................................................3-19
3.3.5 Creating a U2000 User Group..............................................................................................................3-21
3.3.6 Creating a U2000 User Account..........................................................................................................3-22
3.4 Comparing the U2000 User Rights...............................................................................................................3-24
3.5 Querying the Authorization...........................................................................................................................3-25
3.6 Modifying a U2000 User...............................................................................................................................3-26
3.6.1 Resetting the Password of a U2000 User.............................................................................................3-26
3.6.2 Modifying an Object Set......................................................................................................................3-27
3.6.3 Modifying an Operation Set.................................................................................................................3-28
3.6.4 Modifying a User Group......................................................................................................................3-30
3.6.5 Modifying the Information About a U2000 User.................................................................................3-31
3.7 Managing U2000 Object Sets.......................................................................................................................3-32
3.7.1 U2000 Object Set.................................................................................................................................3-33
3.7.2 Creating an Object Set..........................................................................................................................3-33
3.7.3 Modifying an Object Set......................................................................................................................3-34
3.7.4 Deleting an Object Set..........................................................................................................................3-36
3.8 Managing U2000 Operation Sets..................................................................................................................3-36
3.8.1 U2000 Operation Set............................................................................................................................3-37
3.8.2 Creating an Operation Set....................................................................................................................3-37
x Huawei Proprietary and Confidential Issue 03 (2010-11-19)

3.8.3 Modifying an Operation Set.................................................................................................................3-38

3.8.4 Deleting an Operation Set....................................................................................................................3-40
3.8.5 Exporting or Importing Operation Sets................................................................................................3-41
3.9 Monitoring a U2000 User.............................................................................................................................3-43
3.9.1 Monitoring the U2000 User Sessions...................................................................................................3-44
3.9.2 Monitoring the U2000 User Operations...............................................................................................3-44
3.9.3 Forcing a U2000 User to Quit..............................................................................................................3-45
3.9.4 Unlocking a User Account...................................................................................................................3-45
3.9.5 Sending Messages to Online Users......................................................................................................3-46
3.10 Managing the Remote Maintenance User...................................................................................................3-47
3.11 Managing NE Users....................................................................................................................................3-48
3.11.1 Querying the NE User Information....................................................................................................3-49
3.11.2 Creating an NE User..........................................................................................................................3-50
3.11.3 Modifying NE Users..........................................................................................................................3-51
3.11.4 Changing the NE User Password.......................................................................................................3-52
3.11.5 Querying NE Security Parameters.....................................................................................................3-53
3.11.6 Querying NE User Groups.................................................................................................................3-53
3.11.7 Deleting NE Users..............................................................................................................................3-54
3.12 Managing NE Login....................................................................................................................................3-54
3.12.1 Locking Out NE Login.......................................................................................................................3-55
3.12.2 Locking Out NE Settings...................................................................................................................3-55
3.12.3 Querying the Information About an Online NE User........................................................................3-56
3.12.4 Switching a Logged-In NE User........................................................................................................3-56
3.12.5 Forcing an NE User to Log Out of the U2000...................................................................................3-57
3.12.6 Setting NE Login Prompt Message....................................................................................................3-58
3.13 Setting the Security Access of an NE..........................................................................................................3-58
3.13.1 Controlling Communication Between NE and U2000 Through Ethernet Port..................................3-59
3.13.2 Controlling Communication Between NE and U2000 Through a Serial Port...................................3-60
3.13.3 Setting the NE OAM Access..............................................................................................................3-61
3.13.4 Setting the NE COM Access..............................................................................................................3-61
3.13.5 Controlling Communication Between NE and LCT..........................................................................3-62
3.14 Setting the NE ACL....................................................................................................................................3-63
3.14.1 Overview of ACL...............................................................................................................................3-63
3.14.2 Setting Basic ACL Rules....................................................................................................................3-64
3.14.3 Setting the Advanced ACL Rules......................................................................................................3-64
3.15 RADIUS Configuration...............................................................................................................................3-65
3.15.1 Overview............................................................................................................................................3-65
3.15.2 Adding a RADIUS Server..................................................................................................................3-70
3.15.3 Setting NE RADIUS Parameters........................................................................................................3-71
3.15.4 Setting an NE as a RADIUS Client or Proxy Server.........................................................................3-72
3.16 Auditing Changes........................................................................................................................................3-73
3.16.1 Viewing Information About Change Auditing...................................................................................3-74
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xi

3.16.2 Dumping Information About Change Audit......................................................................................3-74

3.16.3 Deleting Information About Change Audit........................................................................................3-75
3.17 NE License Management............................................................................................................................3-75
3.17.1 Getting to Know NE License Management.......................................................................................3-76
3.17.2 Querying the NE License Information...............................................................................................3-77
3.17.3 Applying for an NE License...............................................................................................................3-78
3.17.4 Installing an NE License....................................................................................................................3-79
3.17.5 Synchronize NE Information.............................................................................................................3-80
3.17.6 Adjusting the NE License Capacity...................................................................................................3-81
3.17.7 Changing an NE License....................................................................................................................3-82
4 Log Management........................................................................................................................4-1
4.1 Getting to Know Log Management.................................................................................................................4-3
4.1.1 Log Management Policy........................................................................................................................4-3
4.1.2 Log Types...............................................................................................................................................4-4
4.1.2.1 Security Logs.......................................................................................................................................4-4
4.1.2.2 Operation Logs....................................................................................................................................4-5
4.1.2.3 NE Syslog............................................................................................................................................4-7
4.1.2.4 System Logs........................................................................................................................................4-9
4.2 Managing Operation Logs.............................................................................................................................4-10
4.2.1 Querying Operation Logs.....................................................................................................................4-10
4.2.2 Collecting Statistics on Operation Logs...............................................................................................4-11
4.3 Managing System Logs.................................................................................................................................4-13
4.3.1 Querying System Logs.........................................................................................................................4-13
4.3.2 Collecting Statistics on System Logs...................................................................................................4-14
4.4 Managing Security Logs...............................................................................................................................4-15
4.4.1 Querying Security Logs.......................................................................................................................4-15
4.4.2 Collecting Statistics on Security Logs.................................................................................................4-16
4.5 Managing NE Logs.......................................................................................................................................4-18
4.5.1 Browsing the NE Syslog Operation Logs............................................................................................4-18
4.5.2 Browsing the NE Syslog Running Logs..............................................................................................4-20
4.5.3 Synchronizing SNMP Device Logs.....................................................................................................4-21
4.6 Setting Log Templates..................................................................................................................................4-21
4.7 Setting a Log Forwarding Server..................................................................................................................4-23
4.8 Managing Log Data.......................................................................................................................................4-25
4.8.1 Setting U2000 Log Timing Dumping..................................................................................................4-25
4.8.2 Setting U2000 Log Overflow Dump....................................................................................................4-26
4.8.3 Manually Dumping U2000 Logs..........................................................................................................4-26
4.8.4 Setting U2000 Log Export...................................................................................................................4-28
4.9 Managing NE Syslog....................................................................................................................................4-28
4.9.1 Syslog Management Overview............................................................................................................4-28
4.9.1.1 Functions of Syslog Management.....................................................................................................4-29
4.9.1.2 Basic Concepts..................................................................................................................................4-29
xii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

4.9.2 Configuring the Information Center on the NEs..................................................................................4-29

4.9.2.1 Enabling the Information Center.......................................................................................................4-30
4.9.2.2 Configuring the Syslog Source Interface..........................................................................................4-30
4.9.2.3 Adding the Syslog Host.....................................................................................................................4-31
4.9.2.4 Configuring the Advanced Attributes of the Syslog Service............................................................4-32
4.10 Transferring NE Logs to Log Servers.........................................................................................................4-32
4.10.1 Syslog Service....................................................................................................................................4-33
4.10.2 Configuring the Syslog Server...........................................................................................................4-37
4.10.3 Configuring the Syslog GNE.............................................................................................................4-37
4.10.4 Configuring the Syslog Type and Severity........................................................................................4-38
4.10.5 Starting the Syslog Service................................................................................................................4-38
5 Topology Management.............................................................................................................5-1
5.1 Flow of Constructing the Network Topology.................................................................................................5-3
5.2 Basic Concepts................................................................................................................................................5-5
5.2.1 Main Topology.......................................................................................................................................5-6
5.2.2 Optical NE..............................................................................................................................................5-8
5.2.3 GNE and Non-Gateway NE...................................................................................................................5-9
5.2.4 Virtual NE..............................................................................................................................................5-9
5.2.5 Connection Types.................................................................................................................................5-10
5.3 Designing a Topology...................................................................................................................................5-12
5.4 Creating a Topology Subnet..........................................................................................................................5-12
5.5 Creating NEs.................................................................................................................................................5-13
5.5.1 Setting SNMPv1/v2c Parameters on NEs............................................................................................5-14
5.5.2 Setting SNMPv3 Parameters on NEs...................................................................................................5-15
5.5.3 Configuring the Default SNMP Parameters Template.........................................................................5-16
5.5.4 Creating NEs In Batches......................................................................................................................5-18
5.5.4.1 Creating Transport/PTN NEs in Batches..........................................................................................5-18
5.5.4.2 Creating SNMP/ICMP NEs in Batches.............................................................................................5-20
5.5.4.3 Importing NEs in Batches.................................................................................................................5-22
5.5.5 Creating a Single NE............................................................................................................................5-25
5.5.5.1 Creating a Single Transport NE........................................................................................................5-26
5.5.5.2 Creating a Single PTN NE................................................................................................................5-28
5.5.5.3 Creating a Single Router NE.............................................................................................................5-30
5.5.5.4 Creating a Single Switch NE.............................................................................................................5-31
5.5.5.5 Creating a Single Security Gateway NE...........................................................................................5-32
5.5.5.6 Creating a Single Access NE............................................................................................................5-33
5.5.6 Configuring NEs Automatically...........................................................................................................5-34
5.5.6.1 Auto-Discovering NEs......................................................................................................................5-35
5.5.6.2 Creating Discovered NEs Manually..................................................................................................5-35
5.5.6.3 Creating NEs Automatically.............................................................................................................5-36
5.5.7 Adding NEs Periodically......................................................................................................................5-36
5.5.8 Creating Optical NEs...........................................................................................................................5-38
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xiii

5.5.9 Creating Virtual NEs............................................................................................................................5-38

5.5.10 Setting NE SNMP Parameters............................................................................................................5-39
5.6 Configuring the NE Data...............................................................................................................................5-40
5.6.1 Synchronizing the NE Configuration Data.......................................................................................... 5-41
5.6.2 Configuring the NE Data Manually.....................................................................................................5-42
5.6.3 Replicating the NE Data.......................................................................................................................5-44
5.6.4 Uploading the NE Data........................................................................................................................5-46
5.6.5 Configuring Virtual NE Data...............................................................................................................5-48
5.7 Adding Boards...............................................................................................................................................5-49
5.7.1 Adding Boards......................................................................................................................................5-49
5.7.2 Adding Sub-Boards..............................................................................................................................5-50
5.8 Creating Connections....................................................................................................................................5-50
5.8.1 Creating Fibers Manually.....................................................................................................................5-52
5.8.2 Searching for Fibers/Cables Automatically......................................................................................... 5-53
5.8.3 Creating Fibers/Cables in the Synchronization Mode..........................................................................5-55
5.8.4 Creating Fiber Connections in Graphic Mode..................................................................................... 5-56
5.8.5 Creating Fiber/Cable Connections in Batches..................................................................................... 5-57
5.8.6 Creating DCN Communication Cable..................................................................................................5-58
5.8.7 Creating a Link Manually.................................................................................................................... 5-59
5.8.8 Creating Links Automatically..............................................................................................................5-60
5.8.9 Automatically Creating Radio Links....................................................................................................5-63
5.8.10 Manually Creating Radio Links.........................................................................................................5-64
5.8.11 Creating Virtual Fibers.......................................................................................................................5-65
5.8.12 Restoring the Fiber Connection..........................................................................................................5-67
5.9 Browsing Fibers/Cables................................................................................................................................ 5-67
5.9.1 Querying Fiber/Cable Information.......................................................................................................5-68
5.9.2 Querying Relevant Trails of a Fiber/Cable..........................................................................................5-68
5.9.3 Querying Relevant Optical Power of a Fiber/Cable.............................................................................5-69
5.9.4 Querying the Performance Data of a Radio Link.................................................................................5-70
5.10 Adjusting Topology Objects....................................................................................................................... 5-71
5.10.1 Balancing Load of the NE Explorer Process......................................................................................5-72
5.10.2 Modifying the NE ID and the Extended ID....................................................................................... 5-74
5.10.3 Modifying the NE Name....................................................................................................................5-75
5.10.4 Modifying the NE IP..........................................................................................................................5-75
5.10.5 Modifying the Optical NE Name.......................................................................................................5-76
5.10.6 Adjusting Optical NE Resource.........................................................................................................5-76
5.10.7 Modifying the Status of a Preconfigured NE.....................................................................................5-77
5.10.8 Modifying the NM Name...................................................................................................................5-78
5.10.9 Modifying Fiber/Cable Information...................................................................................................5-78
5.10.10 Naming a Fiber/Cable...................................................................................................................... 5-79
5.10.11 Copying Topology Objects.............................................................................................................. 5-79
5.10.12 Moving Topology Objects............................................................................................................... 5-80
xiv Huawei Proprietary and Confidential Issue 03 (2010-11-19)

5.11 Setting the NE Maintenance Information....................................................................................................5-80

5.12 Setting the Maintenance Personnel Information.........................................................................................5-81
5.13 Deleting Topology Objects.........................................................................................................................5-82
5.13.1 Deleting a Topology Subnet...............................................................................................................5-83
5.13.2 Deleting Boards..................................................................................................................................5-83
5.13.3 Deleting Sub-boards...........................................................................................................................5-84
5.13.4 Deleting Connections.........................................................................................................................5-84
5.13.5 Deleting NEs......................................................................................................................................5-85
5.13.6 Deleting an Optical NE......................................................................................................................5-86
6 Time Localization Management..............................................................................................6-1

6.1 Time Localization...........................................................................................................................................6-2
6.2 Setting Time Localization on the U2000........................................................................................................6-2
6.2.1 Setting the Time Display Format...........................................................................................................6-3
6.2.2 Setting the Time Mode of the Client......................................................................................................6-3
6.3 Setting Time Localization on NEs..................................................................................................................6-4
6.3.1 Setting a Time Zone for an NE..............................................................................................................6-4
6.3.2 Setting DST on NEs...............................................................................................................................6-5
7 Alarm Management...................................................................................................................7-1
7.1 Basic Concepts................................................................................................................................................7-3
7.1.1 Alarms and Events.................................................................................................................................7-4
7.1.2 Alarm Reporting Process.......................................................................................................................7-4
7.1.3 Alarm Handling Procedure.....................................................................................................................7-7
7.1.4 Alarm Template......................................................................................................................................7-9
7.1.5 Alarm Viewing Operations..................................................................................................................7-10
7.1.6 Alarm Setting Operations.....................................................................................................................7-12
7.1.7 Alarm Correlation Analysis.................................................................................................................7-18
7.1.8 Alarm Notification...............................................................................................................................7-20
7.1.9 Alarm Severity.....................................................................................................................................7-22
7.1.10 Alarm States.......................................................................................................................................7-24
7.1.11 Alarm Category..................................................................................................................................7-25
7.1.12 Current Alarms and History Alarms..................................................................................................7-26
7.1.13 Alarm Statistics..................................................................................................................................7-26
7.1.14 Alarm Dumping..................................................................................................................................7-27
7.2 Setting Trap Parameters on the NE...............................................................................................................7-27
7.3 Setting Automatic Alarm Reporting.............................................................................................................7-28
7.3.1 Setting Automatic Reporting Status for Alarms of an NE...................................................................7-29
7.3.2 Setting Automatic Reporting Status for Alarms of a Board.................................................................7-29
7.4 Customizing Alarm Template.......................................................................................................................7-30
7.4.1 Alarm/Event Template.........................................................................................................................7-31
7.4.2 Setting an Alarm/Event Template........................................................................................................7-32
7.4.3 Setting Template Properties for the Current User................................................................................7-33
7.4.4 Customizing Alarm Attribute Template...............................................................................................7-34
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xv

7.5 Synchronizing Alarms...................................................................................................................................7-36

7.5.1 Synchronizing Networkwide Current Alarms......................................................................................7-36
7.5.2 Synchronizing the Current Alarms for an NE......................................................................................7-36
7.5.3 Setting Alarm Auto Synchronization...................................................................................................7-37
7.6 Monitoring Network Alarms.........................................................................................................................7-38
7.6.1 Alarm Reporting Process..................................................................................................................... 7-39
7.6.2 Monitoring Alarms Through the Topology View................................................................................7-42
7.6.3 Monitoring Alarms Through the Alarm Panel.....................................................................................7-42
7.6.4 Browsing the Current Alarm................................................................................................................7-43
7.6.5 Browse History Alarms........................................................................................................................7-44
7.6.6 Querying Alarm Logs...........................................................................................................................7-45
7.6.7 Querying Event Logs........................................................................................................................... 7-46
7.6.8 Monitoring Alarms Through the Alarm Bar Chart.............................................................................. 7-47
7.6.9 Displaying Current Alarms by State.................................................................................................... 7-49
7.6.10 Displaying Current Alarms by Severity.............................................................................................7-50
7.6.11 Setting Columns on an Alarm/Event Interface.................................................................................. 7-51
7.6.12 Viewing the Statistics of Alarms........................................................................................................7-52
7.6.13 Querying Alarms on the Opposite Port..............................................................................................7-52
7.7 Managing the Alarm Maintenance Status.....................................................................................................7-53
7.7.1 Importing Alarm Maintenance Criteria................................................................................................7-53
7.7.2 Configuring Alarm Maintenance Criteria............................................................................................7-56
7.7.3 Activating and Deactivating Maintenance Criteria..............................................................................7-56
7.7.4 Browsing Alarms in the Maintenance State.........................................................................................7-56
7.8 Collecting Statistics on Alarms/Events.........................................................................................................7-57
7.8.1 Setting an Alarm/Event Template........................................................................................................7-57
7.8.2 Collecting Statistics on Alarm Logs.....................................................................................................7-59
7.8.3 Collecting Statistics on Event Logs..................................................................................................... 7-61
7.9 Handling Alarms...........................................................................................................................................7-63
7.9.1 Alarm Handling Procedure...................................................................................................................7-64
7.9.2 Locating an Alarm Through a Fault Object.........................................................................................7-66
7.9.3 Collecting the Fault Information..........................................................................................................7-67
7.9.3.1 Viewing the Alarm Information........................................................................................................7-67
7.9.3.2 Creating a Collection Item................................................................................................................ 7-67
7.9.3.3 Obtaining the Equipment Information.............................................................................................. 7-68
7.9.4 Viewing Alarm Details.........................................................................................................................7-69
7.9.5 Checking Alarms..................................................................................................................................7-70
7.9.6 Acknowledging an Alarm.................................................................................................................... 7-70
7.9.7 Locating Objects Where Alarms Occur............................................................................................... 7-71
7.9.8 Locating an Object Through an Alarm.................................................................................................7-71
7.9.9 Clearing an Alarm Manually................................................................................................................7-72
7.9.10 Masking Alarm...................................................................................................................................7-73
7.9.11 Masking All NE Interface Alarms Quickly........................................................................................7-74
xvi Huawei Proprietary and Confidential Issue 03 (2010-11-19)

7.9.12 Suppressing Alarms............................................................................................................................7-75

7.9.13 Recording Alarm/Event Maintenance Experience.............................................................................7-75
7.9.14 Exporting Alarm/Event Maintenance Experience..............................................................................7-76
7.9.15 Importing Alarm/Event Maintenance Experience..............................................................................7-77
7.9.16 Example of Alarm Handling..............................................................................................................7-78
7.10 Setting the Alarm Auto Processing.............................................................................................................7-79
7.10.1 Automatic Alarm/Event Processing Policy........................................................................................7-79
7.10.2 Setting an Automatic Alarm Acknowledgement Rule.......................................................................7-80
7.10.3 Setting Alarm Auto Synchronization.................................................................................................7-82
7.10.4 Setting an Alarm/Event Redefinition Rule.........................................................................................7-82
7.10.5 Setting an Alarm/Event Mask Rule....................................................................................................7-84
7.10.6 Setting an Alarm/Event Postprocessing Rule.....................................................................................7-85
7.10.7 Setting Conversion from an Events to an ADMC Alarm...................................................................7-86
7.10.8 Setting the Lifecycle of the Current Alarm........................................................................................7-87
7.11 Setting Audible and Visual Alarm Notification..........................................................................................7-87
7.11.1 Setting the Alarm Sound....................................................................................................................7-88
7.11.2 Setting Prompt Colors of Alarms.......................................................................................................7-90
7.11.3 Setting the Alarm Panel......................................................................................................................7-90
7.11.4 Setting Audible and Visual Alarm Indication in the Alarm Box.......................................................7-92
7.11.5 Clearing the Audible and Visual Alarm Indication of an NE Cabinet Temporarily..........................7-93
7.11.6 Clearing the Audible and Visual Alarm Indication of an NE Cabinet Permanently..........................7-94
7.11.7 Setting the Alarm Highlight...............................................................................................................7-94
7.11.8 Setting the Alarm Font.......................................................................................................................7-95
7.11.9 Setting the Alarm Display Mode........................................................................................................7-96
7.11.10 Setting the Display Property of a New Alarm/Event.......................................................................7-98
7.11.11 Setting the Alarm Display in the Topology View............................................................................7-99
7.12 Setting Remote Alarm/Event Notification................................................................................................7-101
7.12.1 Setting the Communication Parameters for Remote Notification....................................................7-102
7.12.2 Setting the Format of Remote Alarm/Event Notification Messages................................................7-103
7.12.3 Setting Delay Delivery of Remote Alarm/Event Notification Messages.........................................7-104
7.12.4 Setting the Remote Alarm/Event Notification Rule.........................................................................7-105
7.12.5 Downloading Remote Notification Logs.........................................................................................7-106
7.13 Modifying Alarm Severity........................................................................................................................7-106
7.13.1 Changing the U2000 Alarm Severity...............................................................................................7-107
7.13.2 Modifying the Alarm Severity for an NE.........................................................................................7-107
7.13.3 Modifying the Alarm Severity for a Board......................................................................................7-108
7.14 Analyzing Alarm Correlation....................................................................................................................7-108
7.14.1 Alarm Correlation Analysis.............................................................................................................7-110
7.14.2 Alarm Correlation............................................................................................................................7-112
7.14.3 Setting the Default Alarm Correlation Rules...................................................................................7-114
7.14.4 Setting an Alarm Correlation Rule...................................................................................................7-114
7.14.5 Setting an Alarm/Event Frequency Analysis Rule...........................................................................7-116
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xvii

7.14.6 Setting an Intermittent Alarm or Repeat Event Analysis Rule........................................................7-117

7.14.7 Setting an Acknowledged and Uncleared Alarm Time Analysis Rule............................................7-118
7.14.8 Example of Alarm/Event Correlation Analysis...............................................................................7-119
7.14.9 Example of Alarm/Event Frequency Analysis.................................................................................7-121
7.14.10 Example of Intermittent Alarm/Repeat Event Analysis.................................................................7-122
7.14.11 Example of Acknowledged and Uncleared Alarm Time Analysis................................................7-122
7.14.12 Setting the Rules for the Correlation Analysis of Trail Alarms.....................................................7-123
7.14.13 Analyzing Trail Alarm Correlation................................................................................................7-124
7.14.14 Configuring a Fiber-Related Alarm...............................................................................................7-125
7.15 Managing Alarm/Event Data....................................................................................................................7-126
7.15.1 Setting Alarm/Event Timing Dump.................................................................................................7-126
7.15.2 Setting Alarm/Event Overflow Dump..............................................................................................7-127
7.15.3 Manually Dumping Alarms/Events..................................................................................................7-128
7.16 Alarm Management (MSTP&WDM&RTN NE)......................................................................................7-129
7.16.1 Suppressing Alarms..........................................................................................................................7-130
7.16.1.1 Suppressing NE Alarms................................................................................................................7-131
7.16.1.2 Suppressing Alarms of a Board or Port.........................................................................................7-131
7.16.1.3 Suppressing the Alarms on an ATM Connection..........................................................................7-132
7.16.1.4 Checking Path Alarm Suppression Status.....................................................................................7-133
7.16.2 Setting Alarm Reversion..................................................................................................................7-134
7.16.2.1 Setting the Alarm Reversion Mode of an NE...............................................................................7-134
7.16.2.2 Setting the Alarm Reversion for Specified Resources..................................................................7-135
7.16.2.3 Setting Alarm Reversion for a Specified Port...............................................................................7-139
7.16.2.4 Setting Alarm Reversion for an SDH Trail...................................................................................7-140
7.16.2.5 Checking Path Alarm Reversion Status........................................................................................7-140
7.16.3 Setting the Types of Lower Order Services in the VC4 Path...........................................................7-141
7.16.4 Monitoring the Alarms and Performance of Lower Order Services in the VC4 Path......................7-142
7.16.5 Setting the Insertion Mode for Channels Not Configured with Services.........................................7-143
7.16.6 Specifying the Port QoS Alarm........................................................................................................7-144
7.16.6.1 Specifying Bit Error Alarm Threshold..........................................................................................7-144
7.16.6.2 Enabling AIS Insertion for a Specified Channel...........................................................................7-145
7.16.6.3 Enabling UNEQ Insertion for a Specified Path............................................................................7-145
7.16.7 Configuring Alarm Insertion............................................................................................................7-146
7.16.7.1 Inserting an Alarm at a Specified Path..........................................................................................7-146
7.16.7.2 Inserting an Alarm on an SDH Trail.............................................................................................7-147
7.16.7.3 Checking Path Alarm Insertion Status..........................................................................................7-147
7.16.8 Inserting a Maintenance Signal to the ODU Layer..........................................................................7-148
7.16.9 Setting NE Alarm Attributes............................................................................................................7-149
7.16.9.1 Setting the Saving Mode for NE alarms........................................................................................7-149
7.16.9.2 Setting the Enabling Status of NE Alarm Correlation Suppression..............................................7-150
7.16.9.3 Querying NE Alarm Correlation Rules.........................................................................................7-151
7.16.9.4 Setting NE Alarm Delay...............................................................................................................7-151
xviii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

7.16.10 Enabling the Alarm Monitoring for Lower Order Paths................................................................7-152

7.16.11 Configuring Housekeeping............................................................................................................7-152
7.16.11.1 Configuring Environment Property.............................................................................................7-153
7.16.11.2 Configuring Control Property.....................................................................................................7-154
8 Performance Management(MSTP&WDM&RTN)...............................................................8-1
8.1 Basic Concept..................................................................................................................................................8-4
8.1.1 Performance Event Type........................................................................................................................8-4
8.1.2 Performance Reporting Process.............................................................................................................8-5
8.1.3 Performance Monitoring Settings..........................................................................................................8-7
8.1.4 Operation of Viewing Performance Data...............................................................................................8-8
8.1.5 RMON Performance..............................................................................................................................8-8
8.1.6 Performance Threshold..........................................................................................................................8-9
8.1.7 Current Performance and History Performance...................................................................................8-10
8.1.8 Performance Dumping......................................................................................................................... 8-10
8.1.9 Performance Analysis.......................................................................................................................... 8-11
8.2 Viewing Performance Data...........................................................................................................................8-11
8.2.1 Creating a Performance Filtering Template.........................................................................................8-12
8.2.2 Viewing Current Performance Data.....................................................................................................8-13
8.2.3 Viewing History Performance Data.....................................................................................................8-14
8.2.4 Viewing UAT Records.........................................................................................................................8-16
8.2.5 Viewing Performance Threshold Crossings.........................................................................................8-17
8.2.6 Viewing Current Performance Data of an Ethernet Port......................................................................8-18
8.2.7 Viewing History Performance Data of an Ethernet Port......................................................................8-18
8.2.8 Viewing Current Performance Data of an ATM Port.......................................................................... 8-19
8.2.9 Viewing History Performance Data of an ATM Port...........................................................................8-19
8.2.10 Querying the NE Temperature...........................................................................................................8-20
8.2.11 Query Ethernet Port Flow Monitoring...............................................................................................8-20
8.3 Viewing RMON Performance Data..............................................................................................................8-21
8.3.1 Viewing History Group Performance.................................................................................................. 8-21
8.3.2 Viewing Statistics Group Performance of an Ethernet Port.................................................................8-23
8.4 Managing Lower Order Performance Data...................................................................................................8-25
8.4.1 Enabling Performance Monitoring for a Lower Order Path.................................................................8-26
8.4.2 Setting the Lower Order Performance Threshold................................................................................ 8-27
8.4.3 Setting the Lower Order Performance Monitoring Status....................................................................8-28
8.4.4 Viewing Current Lower Order Performance Data...............................................................................8-29
8.4.5 Viewing History Lower Order Performance Data............................................................................... 8-30
8.4.6 Viewing UAT Records for a Lower Order Service..............................................................................8-31
8.4.7 Viewing Lower Order Performance Threshold-Crossing Records......................................................8-33
8.5 Creating Performance Threshold Templates.................................................................................................8-34
8.6 Setting the Board Performance Threshold....................................................................................................8-35
8.7 Customizing a Performance Event Monitoring Status Template..................................................................8-36
8.8 Setting Performance Monitoring Parameters................................................................................................8-37
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xix

8.8.1 Setting the Performance Reporting Status for a Single NE.................................................................8-38

8.8.2 Setting the Performance Reporting Status for Multiple NEs...............................................................8-39
8.8.3 Setting the Performance Reporting Status for a Single NE.................................................................8-40
8.8.4 Setting Performance Monitoring Parameters of an NE........................................................................8-40
8.8.5 Setting IP Performance Monitoring Parameters of an NE...................................................................8-41
8.8.6 Setting ATM Performance Monitoring Parameters of an NE..............................................................8-42
8.8.7 Setting Performance Monitoring Parameters of a Board.....................................................................8-43
8.8.8 Setting IP Performance Monitoring Parameters of a Board.................................................................8-43
8.8.9 Setting ATM Performance Monitoring Parameters of an ATM Board................................................8-44
8.8.10 Setting Ethernet Port Flow Monitoring..............................................................................................8-44
8.9 Setting RMON Performance Monitoring Parameters...................................................................................8-45
8.9.1 Customizing the RMON Performance Attribute Template..................................................................8-45
8.9.2 Setting the RMON Performance Threshold.........................................................................................8-47
8.9.3 Setting the RMON History Control Group..........................................................................................8-49
8.9.4 Setting the RMON Performance Monitor Object................................................................................8-49
8.9.5 Setting the RMON Performance Monitor Status.................................................................................8-51
8.9.6 Setting Performance Monitoring Parameters of an Alarm Group for an Ethernet Port.......................8-53
8.9.7 Setting Performance Monitoring Parameters of a History Control Group for an Ethernet Port..........8-54
8.9.8 Setting the RMON Performance Monitoring Parameters for an Ethernet Port....................................8-54
8.9.9 Setting Automatic Reporting of RMON Performance Events.............................................................8-55
8.10 Dumping Performance Data........................................................................................................................8-56
8.10.1 Dumping Performance Data Manually..............................................................................................8-56
8.10.2 Dumping Performance Data Periodically...........................................................................................8-57
8.10.3 Dumping Performance Data in the Overflow Way............................................................................8-58
8.11 Collecting the History RMON Performance Data......................................................................................8-59
8.12 Periodically Collecting the Performance Data............................................................................................8-61
8.13 Analyzing History Performance Data.........................................................................................................8-62
8.14 Forecasting the Failure Time of the Laser...................................................................................................8-63
8.15 Resetting Performance Registers................................................................................................................8-63
8.15.1 Resetting Board Performance Registers.............................................................................................8-64
8.15.2 Resetting ATM Performance Registers..............................................................................................8-64
8.15.3 Resetting Ethernet Performance Registers.........................................................................................8-65
8.16 Power Consumption Management..............................................................................................................8-65
8.16.1 Querying the Power Consumption of NEs and Boards......................................................................8-65
8.16.2 Setting the NE Power Consumption Threshold.................................................................................8-66
8.17 Configuring the Q Value Performance Monitoring....................................................................................8-66
8.17.1 Querying the Current Q Value Performance......................................................................................8-67
8.17.2 Querying the History Q Value Performance......................................................................................8-68
8.17.3 Setting and Querying the Threshold of the Q Value Performance.....................................................8-68
9 Inventory Management.............................................................................................................9-1
9.1 Telecommunication Room Management........................................................................................................9-4
9.1.1 Creating a Telecommunications Room..................................................................................................9-4
xx Huawei Proprietary and Confidential Issue 03 (2010-11-19)

9.1.2 Installing a Rack or an NMS Server in a Telecommunications Room..................................................9-5

9.1.3 Querying Telecommunications Rooms..................................................................................................9-6
9.1.4 Modifying a Telecommunications Room...............................................................................................9-6
9.1.5 Deleting a Telecommunications Room..................................................................................................9-7
9.1.6 Setting a Flag for a Telecommunications Room....................................................................................9-7
9.1.7 Exporting telecommunications Room Information................................................................................9-8
9.1.8 Collecting Statistics on a Telecommunications Room...........................................................................9-8
9.2 Rack Management...........................................................................................................................................9-9
9.2.1 Creating a Rack....................................................................................................................................9-10
9.2.2 Installing a shelf on a Rack..................................................................................................................9-10
9.2.3 Querying Racks....................................................................................................................................9-11
9.2.4 Modifying a Rack.................................................................................................................................9-11
9.2.5 Deleting a Rack....................................................................................................................................9-12
9.2.6 Setting a Rack Flag.............................................................................................................................. 9-12
9.2.7 Exporting Rack Information.................................................................................................................9-13
9.2.8 Collecting Statistics on a Rack.............................................................................................................9-13
9.3 NE Management............................................................................................................................................9-14
9.3.1 Querying NEs.......................................................................................................................................9-15
9.3.2 Setting a Flag for an NE.......................................................................................................................9-15
9.3.3 Exporting NE Information................................................................................................................... 9-16
9.3.4 Collecting Statistics on an NE..............................................................................................................9-17
9.3.5 Collecting Statistics on an Equivalent NE........................................................................................... 9-18
9.4 Shelf Management.........................................................................................................................................9-18
9.4.1 Querying shelf......................................................................................................................................9-18
9.4.2 Setting a Flag for a Shelf......................................................................................................................9-19
9.4.3 Exporting shelf Information.................................................................................................................9-20
9.4.4 Collecting Statistics on a Shelf.............................................................................................................9-20
9.5 Board Management.......................................................................................................................................9-21
9.5.1 Querying Boards.................................................................................................................................. 9-21
9.5.2 Setting a Flag for a Board.................................................................................................................... 9-22
9.5.3 Exporting Board Information...............................................................................................................9-23
9.5.4 Collecting Statistics on a Board...........................................................................................................9-23
9.6 Subboard Management..................................................................................................................................9-24
9.6.1 Querying Subboards.............................................................................................................................9-25
9.6.2 Setting a Flag for a Subboard...............................................................................................................9-25
9.6.3 Exporting Subboard Information......................................................................................................... 9-26
9.6.4 Collecting Statistics on a Subboard......................................................................................................9-27
9.7 Port Management.......................................................................................................................................... 9-28
9.7.1 Querying Ports......................................................................................................................................9-28
9.7.2 Setting a Port Flag................................................................................................................................9-29
9.7.3 Exporting Port Information..................................................................................................................9-29
9.7.4 Collecting Statistics on a Port.............................................................................................................. 9-30
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xxi

9.8 Collecting Statistics on the Slot Usage......................................................................................................... 9-30

9.9 Fiber/Cable Management..............................................................................................................................9-31
9.9.1 Creating Fibers/Cables in Batches.......................................................................................................9-32
9.9.2 Importing a Link...................................................................................................................................9-33
9.9.3 Querying a Fiber/Cable........................................................................................................................9-33
9.9.4 Modifying a Fiber/Cable......................................................................................................................9-34
9.9.5 Modifying Fibers/Cables in Batches....................................................................................................9-34
9.9.6 Deleting a Fiber/Cable.........................................................................................................................9-35
9.9.7 Exporting the Fiber/Cable Information................................................................................................9-35
9.9.8 Creating an Intermediate Office...........................................................................................................9-36
9.9.9 Checking the Fiber/Cable Connection.................................................................................................9-36
9.9.10 Creating Links Automatically............................................................................................................9-37
9.9.11 Searching for Fibers/Cables Automatically.......................................................................................9-40
9.9.12 Querying the Fiber/Cable Pipe Associated to a Fiber/Cable..............................................................9-41
9.9.13 Querying Alarms Related to a Fiber/Cable........................................................................................9-42
9.10 Fiber/Cable Pipe Management....................................................................................................................9-42
9.10.1 Creating a Fiber/Cable Pipe...............................................................................................................9-43
9.10.2 Adding a Fiber/Cable into a Fiber/Cable Pipe...................................................................................9-43
9.10.3 Querying a Fiber/Cable Pipe..............................................................................................................9-44
9.10.4 Modifying the Information About a Fiber/Cable Pipe.......................................................................9-44
9.10.5 Removing a Fiber/Cable from a Fiber/Cable Pipe.............................................................................9-45
9.10.6 Deleting a Fiber/Cable Pipe...............................................................................................................9-45
9.11 Link Resource Management........................................................................................................................9-46
9.11.1 Synchronizing Trunk Links................................................................................................................9-47
9.11.2 Querying a Link.................................................................................................................................9-47
9.11.3 Creating a Link...................................................................................................................................9-48
9.11.4 Viewing Link Information.................................................................................................................9-48
9.11.5 Viewing Link Alarms.........................................................................................................................9-49
9.11.6 Creating a Link View.........................................................................................................................9-49
9.11.7 Creating a Link Group........................................................................................................................9-50
9.11.8 Adding a Link to the Link Group.......................................................................................................9-50
9.12 Interface Resource Management.................................................................................................................9-51
9.12.1 Querying Router/Switch Interface Resources....................................................................................9-51
9.12.2 Setting a Router/Switch Interface Flag..............................................................................................9-52
9.12.3 Exporting Router/Switch Interface Information.................................................................................9-53
9.12.4 Querying a PTN Interface Resource Report.......................................................................................9-54
9.13 Collecting Statistics on the ONU................................................................................................................9-55
9.14 Collecting Statistics on the Split Status of PON Ports................................................................................9-55
9.15 Exporting Electronic Labels of NEs............................................................................................................9-56
9.16 SDH Report.................................................................................................................................................9-58
9.16.1 Collecting Statistics on the SDH Ports...............................................................................................9-58
9.16.2 Collecting Statistics on the SDH lower Order Cross-Connections....................................................9-59
xxii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

9.16.3 Collecting Statistics on SDH Tributary Port Resources.....................................................................9-60

9.16.4 Collecting Statistics on Trails Between SDH NEs.............................................................................9-60
9.16.5 Collecting Statistics on the SDH Protection Subnet Resources.........................................................9-61
9.16.6 Collecting Statistics on SDH Trail Resources....................................................................................9-61
9.16.7 Collecting Statistics on SDH Fiber Resource Usage.........................................................................9-62
9.16.8 Creating a Timing Task for Collecting Statistics on SDH Resources................................................9-63
9.17 Microwave Report.......................................................................................................................................9-63
9.17.1 Collecting Statistics on the Microwave License Capacity.................................................................9-64
9.17.2 Collecting Statistics on Microwave Links.........................................................................................9-64
9.17.3 Collecting Statistics on Microwave Link Resource Usage................................................................9-64
9.18 WDM Statistic Report.................................................................................................................................9-65
9.18.1 Collecting Statistics on the WDM Protection Group Switching State...............................................9-66
9.18.2 Collecting Statistics on WDM NE Master/Slave Shelf Information..................................................9-67
9.18.3 Collecting Statistics on WDM Client-Side Port Resources...............................................................9-67
9.18.4 Collecting Statistics on Wavelength Resources Between WDM Sites..............................................9-68
9.18.5 Statistics Report of WDM Link Resources........................................................................................9-69
9.18.6 Collecting Statistics on Wavelength Resource Usage........................................................................9-70
9.18.7 Creating a Timing Task for Collecting Statistics on WDM Resources.............................................9-70
9.18.8 Viewing WDM Channel Resources...................................................................................................9-71
9.19 MSTP Ethernet Report................................................................................................................................9-72
9.19.1 Collecting Statistics on Ethernet Port Resources...............................................................................9-72
9.19.2 Collecting Statistics on Service Resources Between Ethernet NEs...................................................9-72
9.20 Project Document........................................................................................................................................9-73
9.20.1 Viewing the Board Manufacturer Information Report.......................................................................9-74
9.20.2 Viewing Common Manufacturer Information Report........................................................................9-74
9.20.3 Viewing the Clock Tracing Diagram.................................................................................................9-75
9.20.4 Viewing the Networking Diagram.....................................................................................................9-76
9.20.5 Viewing the Timeslot Allocation Diagram........................................................................................9-77
10 Backing Up and Restoring the U2000 Database...............................................................10-1

10.1 Basic Concepts and Application Scenarios.................................................................................................10-3
10.2 Methods of Backing Up and Restoring the U2000 Data.............................................................................10-4
10.3 U2000 Database List...................................................................................................................................10-6
10.4 Suggestions on Data Backup and Restoration.............................................................................................10-8
10.5 Backing Up and Restoring All Data in U2000 Database............................................................................10-8
10.5.1 Immediately Backing Up the U2000 Database to a Local Server Through the U2000 Client..........10-9
10.5.2 Periodically Backing Up the U2000 Data to a Local Server Through the U2000 Client..................10-9
10.5.3 Periodically Backing Up the U2000 Data to a Remote Server Through the U2000 Client.............10-11
10.5.4 Restoring a U2000 Database............................................................................................................10-12
10.6 Backing Up and Restoring the U2000 Network Configuration Data by Using Scripts............................10-12
10.6.1 Script Files........................................................................................................................................10-14
10.6.2 Immediately Backing Up the U2000 Data by Script........................................................................10-19
10.6.3 Backing Up the U2000 Data Through Script Exporting in a Scheduled Manner............................10-20
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xxiii

10.6.4 Restoring the U2000 Data by Using the Script................................................................................10-21

10.7 Setting Alarm/Event Timing Dump..........................................................................................................10-22
10.8 Setting U2000 Log Timing Dumping....................................................................................................... 10-23
10.9 Dumping Performance Data......................................................................................................................10-24
10.9.1 Dumping Performance Data Manually............................................................................................ 10-24
10.9.2 Dumping Performance Data Automatically.....................................................................................10-25
11 Keeping Data Consistency Between the U2000 and NEs...............................................11-1

11.1 Data Management Policy of the U2000......................................................................................................11-3
11.2 Checking Consistency of Configuration Data Between an NE and the U2000..........................................11-8
11.3 Viewing the Asynchronous Information.....................................................................................................11-9
11.4 Synchronizing the NE Configuration Data.................................................................................................11-9
11.5 Uploading NE Configuration Data............................................................................................................11-11
11.6 Downloading NE Configuration Data.......................................................................................................11-11
11.7 Configuration Data Management Information List...................................................................................11-12
11.7.1 Configuration Data Management Specifications of the General Operations...................................11-12
11.7.2 Configuration Data Management Specifications of the SDH..........................................................11-16
11.7.3 Configuration Data Management Specifications of the WDM........................................................11-33
11.7.4 Configuration Data Management Specifications of the NG WDM.................................................11-61
11.7.5 Configuration Data Management Specifications of the NA WDM.................................................11-78
11.7.6 Configuration Data Management Specifications of the NG WDMA.............................................. 11-87
11.7.7 Configuration Data Management Specifications of the PTN...........................................................11-96
11.7.8 Configuration Data Management Specifications of the Ethernet.....................................................11-98
11.7.9 Configuration Data Management Specifications of the ATM.......................................................11-129
11.7.10 Configuration Data Management Specifications of the ASON...................................................11-134
11.7.11 Configuration Data Management Specifications of the alarm and performance.........................11-134
12 Backing Up and Restoring the NE Data............................................................................12-1

12.1 Comparison of NE Data Backup and Restoration Methods........................................................................12-3
12.2 Backing Up the NE Database to the SCC Board........................................................................................12-4
12.3 Backing Up History Alarms to a Flash Card...............................................................................................12-5
12.4 Backing Up the NE Database to a CF Card................................................................................................12-5
12.4.1 Automatically Backing Up the NE Database to a CF Card...............................................................12-6
12.4.2 Manually Backing Up the NE Database to a CF Card.......................................................................12-6
12.5 Restoring the NE Database from the SCC Board.......................................................................................12-7
12.6 Restoring the NE Database from the CF Card............................................................................................12-7
13 Customer Management.........................................................................................................13-1
13.1 Relation Between User and Customer........................................................................................................13-3
13.2 Creating a Customer Group.........................................................................................................................13-3
13.3 Creating a Customer....................................................................................................................................13-3
13.4 Browsing Customer Information.................................................................................................................13-4
13.5 Viewing Relevant Trails of a Customer......................................................................................................13-4
13.6 Browsing Current Alarms of a Customer....................................................................................................13-5
xxiv Huawei Proprietary and Confidential Issue 03 (2010-11-19)

13.7 Browsing History Alarms of a Customer....................................................................................................13-6

13.8 Modifying Customer Information...............................................................................................................13-6
13.9 Deleting a Customer....................................................................................................................................13-7
13.10 Viewing the Customers Affected by an Alarm.........................................................................................13-7
13.11 Specifying the Customer of a Service.......................................................................................................13-8
13.12 Enabling VCN Status of a Customer.........................................................................................................13-8
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xxv

Operation Guide for Common Features Figures
Figures
Figure 1-1 Workbench........................................................................................................................................1-33

Figure 1-2 Workbench........................................................................................................................................1-33
Figure 1-3 Topology for communications between the U2000 and NEs in the IP/access domain....................1-34
Figure 1-4 Topology for communications between the U2000 and NEs in the transport domain.....................1-35
Figure 1-5 Client GUI........................................................................................................................................1-45
Figure 1-6 Main Topology.................................................................................................................................1-59
Figure 1-7 Clock View.......................................................................................................................................1-62
Figure 1-8 Signal flow diagram..........................................................................................................................1-66
Figure 1-9 Browsing alarms...............................................................................................................................1-67
Figure 1-10 Browse Event Logs.........................................................................................................................1-68
Figure 1-11 Browse SDH Performance..............................................................................................................1-69
Figure 1-12 Browse WDM Performance...........................................................................................................1-69
Figure 1-13 Browse NA WDM Performance.....................................................................................................1-70
Figure 1-14 Browse Control Plane Performance...............................................................................................1-70
Figure 1-15 Mutual exclusion list for multiclient operations...........................................................................1-161
Figure 1-16 Mutual exclusion list for multiclient operations on ASON SDH trails........................................1-162
Figure 1-17 Mutual exclusion list for multiclient operations on ASON WDM trails......................................1-162
Figure 2-1 Flowchart of managing an access network.........................................................................................2-3
Figure 2-2 MSTP network management process.................................................................................................2-4
Figure 2-3 Metro WDM&LH WDM network management process...................................................................2-5
Figure 2-4 OptiX OSN 6800OptiX OSN 6800A equipment management process.............................................2-6
Figure 2-5 OptiX OSN 8800 series equipment management process..................................................................2-7
Figure 2-6 OptiX OSN 18001800(NA) equipment management process............................................................2-7
Figure 2-7 RTN network management process....................................................................................................2-8
Figure 2-8 PTN network management process....................................................................................................2-9
Figure 2-9 Flowchart of managing a security equipment network.....................................................................2-10
Figure 2-10 Flowchart of managing a router network........................................................................................2-11
Figure 2-11 Flowchart of managing a switch network.......................................................................................2-12
Figure 3-1 Implementation of security management............................................................................................3-3
Figure 3-2 Networking of authority and domain-based management................................................................3-15
Figure 3-3 Structure of a RADIUS Packet.........................................................................................................3-66
Figure 3-4 Structure of RADIUS Protocol Stack...............................................................................................3-67
Figure 3-5 RADIUS Networking Structure........................................................................................................3-68
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xxvii

Figures Operation Guide for Common Features
Figure 3-6 RADIUS Packet Exchange Process..................................................................................................3-69

Figure 4-1 IP and ECC hybrid networking-1.....................................................................................................4-34
Figure 4-2 IP and ECC hybrid networking-2.....................................................................................................4-35
Figure 4-3 ECC independent networking...........................................................................................................4-36
Figure 5-1 Flow of constructing the network topology........................................................................................5-3
Figure 5-2 Main Topology...................................................................................................................................5-7
Figure 5-3 Imported Excel.................................................................................................................................5-24
Figure 7-1 Alarm reporting flow chart 1..............................................................................................................7-5
Figure 7-2 Alarm reporting flow chart 2..............................................................................................................7-6
Figure 7-3 Procedure for handling an alarm.........................................................................................................7-8
Figure 7-4 NE Alarm Correlation......................................................................................................................7-19
Figure 7-5 Non-NA NEs Alarm status...............................................................................................................7-21
Figure 7-6 NA NEs Alarm status.......................................................................................................................7-21
Figure 7-7 Alarm state change model................................................................................................................7-25
Figure 7-8 Alarm reporting flow chart 1............................................................................................................7-40
Figure 7-9 Alarm reporting flow chart 2............................................................................................................7-41
Figure 7-10 Alarm panel....................................................................................................................................7-43
Figure 7-11 Procedure for handling an alarm.....................................................................................................7-65
Figure 7-12 NE Alarm Correlation..................................................................................................................7-111
Figure 7-13 Relationships between a root alarm and its correlative alarms.....................................................7-113
Figure 8-1 Performance reporting process...........................................................................................................8-6
Figure 11-1 NE Data Management Operation....................................................................................................11-5
Figure 11-2 U2000 Data Management Operation..............................................................................................11-7
xxviii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

Operation Guide for Common Features Tables
Tables
Table 1-1 Server parameter settings...................................................................................................................1-19

Table 1-2 The shortcut icons on the Main Topology.........................................................................................1-50
Table 1-3 The shortcut icons on the other GUI..................................................................................................1-54
Table 1-4 Querying and configuring clocks network-wide................................................................................1-63
Table 1-5 Alarm background color in various display mode...........................................................................1-121
Table 1-6 U2000 process list............................................................................................................................1-142
Table 3-1 Parts of a .csv file...............................................................................................................................3-42
Table 3-2 Field Description of a RADIUS Packet.............................................................................................3-66
Table 3-3 NE license states................................................................................................................................3-77
Table 3-4 States of the queried NE licenses and handling suggestions..............................................................3-77
Table 4-1 Configuration List..............................................................................................................................4-34
Table 4-2 Configuration List..............................................................................................................................4-36
Table 5-1 Description of the flow of constructing the network topology............................................................5-4
Table 5-2 Imported Excel Description...............................................................................................................5-24
Table 5-3 Exported Excel Description...............................................................................................................5-25
Table 7-1 Procedure for handling an alarm..........................................................................................................7-9
Table 7-2 Alarm Template Type........................................................................................................................7-10
Table 7-3 Impacts of alarm viewing operations on NEs....................................................................................7-10
Table 7-4 Impacts of alarm setting operations on NEs and services..................................................................7-13
Table 7-5 Impacts of alarm setting operations on alarms...................................................................................7-14
Table 7-6 Alarm reversion handling mode.........................................................................................................7-16
Table 7-7 Template functions.............................................................................................................................7-31
Table 7-8 Description of script parameters for maintenance criteria.................................................................7-54
Table 7-9 Procedure for handling an alarm........................................................................................................7-66
Table 7-10 Alarm background color in various display mode...........................................................................7-97
Table 10-1 Characteristics and application scenarios of two data maintenance methods..................................10-5
Table 10-2 U2000 database list..........................................................................................................................10-6
Table 10-3 Script files the U2000 provides......................................................................................................10-14
Table 12-1 Backup and Restoration Methods and Application Scenarios.........................................................12-3
Issue 03 (2010-11-19) Huawei Proprietary and Confidential xxix

Operation Guide for Common Features 1 Getting Started
1 Getting Started
About This Chapter
The following topics introduce some preparation operations that will ensure a smooth, trouble-
free launch of the U2000.
1.1 Precautions for Using the U2000 Safely

This topic describes the precautions for using the U2000 safely. The operation precautions that
have to be taken to ensure correct operations are as follows:
1.2 Starting the U2000 System
This topic describes how to start the U2000 System.
1.3 Shutting Down the U2000
This topic describes how to shut down the U2000 server and client. The shutdown procedure
varies according to the deployment scheme.
1.4 Changing the Password of the Current User
This topic describes how to change the password of your account. It is suggested that you should
change the password periodically to improve the password security of your account.
1.5 Using the Workbench and Favorites Folder
This topic describes how to use the workbench and the favorites folder of commonly used
functions to rapidly locate the commonly used functions of the U2000.
1.6 Setting the Parameters for the Communication Between the U2000 and NEs
This topic describes how to set parameters for the communication between the U2000 and NEs.
Properly setting these parameters is the prerequisite to the normal communication between the
U2000 and NEs. You need to set these parameters in time.
1.7 Setting or Modifying the Character Set of an NE
To meet the global requirements, the U2000 provides the function of setting or modifying NE
character sets to prevent the language change from resulting in illegible characters.
1.8 Main Windows and Common Operations of the U2000
This topic describes the main windows of the U2000 client. Learning the main windows helps
you to locate the entrances to operations quickly, which increased your operation efficiency.
1.9 How to Obtain Version Information About the U2000
Introduce how to obtain version information about the U2000.
Issue 03 (2010-11-19) Huawei Proprietary and Confidential 1-1

1 Getting Started Operation Guide for Common Features
1.10 Customizing the Client GUI Effect

You can customize the GUI effect of the U2000 client as required.
1.11 Setting the Alarm Sound at Network Disconnection
After you set the disconnection alarm sound on the U2000 client, the sound box connected to
the client plays the sound if the U2000 client is disconnected from the server.
1.12 Checking Whether the Client Needs Upgrade
You can perform this operation to check whether the version of the client matches that of the
server. If the versions do not match, you must upgrade the client.
1.13 Setting the Interval of Client Upgrade Check
After the server is upgraded, the server version and the client version do not match. Therefore,
the client has to be upgraded accordingly. After the interval for upgrade checking is set, the
U2000 periodically checks whether the client needs to be upgraded.
1.14 Locking the Client
You can lock the client to prevent unauthorized operations.
1.15 Unlocking the Client
This section describes how to unlock the locked U2000 client.
1.16 Setting a Scheduled Task
The U2000 can automatically executing certain tasks in a scheduled time without manual
intervention. You can set and modify these scheduled tasks as required.
1.17 Broadcast Messages
The broadcast message function includes setting the broadcast parameter and sending the
broadcast message. The broadcast message function of the U2000 enables you to send messages
to other users with ease.
1.18 Applying for and Updating the License
This topic describes the license file of the U2000, and how to apply for, install, and use the
U2000 license.
1.19 Starting the Web Client
Certain NEs must be configured by using the Web LCT. Before you configure services for these
NEs, you need to first start the Web LCT client.
1.20 Collecting NE Data
When an NE is faulty, you can collect the NE data for fault identification and analysis. There
are fast fault collection and full fault collection.
1.21 Customizing Naming Rule
When you create fibers or trails, the U2000 automatically creates the names of the fibers, trails,
ASON trails, Tunnel and PWE3 Service based on the naming rule. The settings can be modified
according to actual requirements. This section takes the fiber naming rule as an example to
illustrate how to customize the naming rule.
1.22 U2000 Process List
This topic describes the information about U2000 processes,such as the functions and dependent
processes of each process and the port occupied by each process.
1.23 Rules for Entering Information on User Interface
This topic describes the rules for entering information on the user interface. These rules specify
the typing requirements for the text boxes in the U2000 operation interface. These text boxes
are used to enter character strings, file names, IP addresses, MAC addresses, numerals,
passwords, dates, time, and so on.
1-2 Huawei Proprietary and Confidential Issue 03 (2010-11-19)

1.24 Mutual Exclusion List for Multiclient Operations

The mutual exclusion list for multiclient operations is given below.

1.1 Precautions for Using the U2000 Safely

This topic describes the precautions for using the U2000 safely. The operation precautions that
have to be taken to ensure correct operations are as follows:
l Do not modify the system time when the U2000 is running. Set the time before installing
the U2000.
– To modify the system time of the server, exit the U2000 server and restart it after the
modification.
– To modify the system time of the client, exit the U2000 client and restart it after the
modification.
l Avoid modifying the name and IP address of the U2000 server computer.
l Log in to the U2000 server as nmsuser on Solaris. Log in to the U2000 server as
nmsuser on SUSE Linux. On Windows, log in to the U2000 server with the same user ID
that you had chosen when installing the U2000. Do not change the Windows user name.
l The data created on the NE is consistent with that on the U2000. When an NE is configured
and runs normally, you can store the data on the NE and the data on the U2000 consistent
through manual or automatic synchronization.
l Back up the U2000 database periodically to minimize the loss caused by abnormal
functioning of the system.
l It is recommended to synchronizing the NE configuration data to the NMS, and query the
latest data from NE before setting the parameters.
l When a hazardous operation is performed, the U2000 asks for confirmation. For example:
When you downloading the U2000 data to the NE, it can interrupt the services.
l The installation directory of U2000 can contain only the letter, number, and underscore.
Otherwise, the U2000 Online Help cannot be used.
l If you select a non-English language for an NE when maintaining it, the GUIs are in illegible
characters when you query the information about the NE.
1.2 Starting the U2000 System

This topic describes how to start the U2000 System.
1.2.1 Starting a Single-Server System (Windows)
This topic describes how to start a Windows single-server system. After the U2000 server is
started, you must start the U2000. Then, log in to the U2000 to manage networks.
1.2.2 Starting a Single-Server System (Solaris)
This topic describes how to start a Solaris single-server system. After the U2000 server is started,
you must start the U2000. Then, log in to the U2000 to manage networks.
1.2.3 Starting the Single-Server System (SUSE Linux-Distributed)
This topic describes how to start the Single-Server System (SUSE Linux-Distributed). After the
Single-Server System (SUSE Linux-Distributed) is started, you must start U2000 server
processes before starting a U2000 client to monitor and manage the network.
1.2.4 Starting the High Availability System (Windows)

This topic describes how to start the high availability system. Starting the U2000 high availability
system includes starting the U2000 server and logging in to the U2000 client.
1.2.5 Starting the High Availability System (Solaris)
1.2.6 Starting the High Availability System (SUSE Linux-Distributed)
1.2.7 Logging In to the U2000 Client
Log in to a U2000 using the client, and then perform management operations in the GUI of the
U2000 client.
1.2.1 Starting a Single-Server System (Windows)

This topic describes how to start a Windows single-server system. After the U2000 server is
started, you must start the U2000. Then, log in to the U2000 to manage networks.
Context
l U2000 services run as background processes. Maintain the U2000 services using a System
Monitor client.
l The client is installed at the same time as the U2000 software. The client described in this
topic is the one installed on the server.
l During installation of the U2000 software, only one default U2000 user, that is, the
admin user, is provided. The admin user is the administrator of a U2000 and has the highest
rights of the U2000.
Procedure
1 Log in to the OS as a user with administrator rights. The system automatically starts the
database and U2000 service.
NOTE
If the database has not been started, choose Start > Programs > Microsoft SQL Server > Service
Manager, and then click Start/Continue to start the database. If the database has been started, the manual
operation is not required.
If U2000 services have not been started, run the startnms.bat file in the U2000 installation path \server
\bin to start U2000 services manually. If the U2000 has been started, the manual operation is not required.
2 Check the shortcut icons.
CAUTION
If you cannot log in to the server through the GUI, skip this step.
The following shortcut icons are displayed on the desktop:
l U2000 Client
l U2000 System Monitor

l U2000 Server
l U2000 NMS Maintenance Suite
l NE Software Management
3 Choose Start > Programs > Network Management System > U2000 System Monitor or
double-click the associated shortcut icon on the desktop to start the System Monitor.
4 In the Login dialog box, enter a user name and password to access the System Monitor window.
The user name is admin and the initial password is blank by default. When you log in to the
System Monitor for the first time, you must change the initial password.
5 Check whether U2000 processes can be properly started. The processes whose startup mode is
manual must be started manually.
6 Start a U2000 client.
1. On the desktop, double-click the U2000 Client shortcut icon.
2. In the dialog box that is displayed, enter a U2000 user name and password. If you have
changed the password for the admin user when logging in to the System Monitor, enter
the new password.
NOTE
There are two data transmission modes, namely, Common and Security(SSL). You can query data
transmission modes on the server. The default data transmission mode is Common. For details, see
How to Set the Communication Mode on the U2000 server for the Single-Server System (Windows).
----End
1.2.2 Starting a Single-Server System (Solaris)

This topic describes how to start a Solaris single-server system. After the U2000 server is started,
you must start the U2000. Then, log in to the U2000 to manage networks.
Prerequisite
The OS of the server must be started.
Context
l The client is installed at the same time as the centralized system.
l During installation of the U2000 software, the OS user nmsuser is created automatically.
The nmsuser user is used to regularly maintain a U2000.
l During installation of the U2000 software, only one default NMS user, that is, user
admin, is provided. The admin user is the administrator of the U2000 and has the highest
rights of the U2000. The default password of user admin is blank. You must change the
default password during first-time login.
Procedure
1 Log in to the OS of the server as the nmsuser user.
2 Ensure that the database is running.
Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase

Information similar to the following is displayed:

sybase 4848 4847 0 May 18 ? 167:11 /opt/sybase/ASE-15_0/bin/data
server -sDBSVR -d/opt/sybase/data/lv_master -e/opt
sybase 5250 5248 0 May 18 ? 0:00 /opt/sybase/ASE-15_0/bin/back
upserver -SDBSVR_back -e/opt/sybase/ASE-15_0/insta
sybase 4847 1 0 May 18 ? 0:00 /usr/bin/sh /opt/sybase/ASE-1
5_0/install/RUN_DBSVR
5_0/install/RUN_DBSVR_back
...
NOTE
The database is running if the displayed information contains /opt/sybase/ASE-15_0/install/

RUN_DBSVR and /opt/sybase/ASE-15_0/install/RUN_DBSVR_back.
Run the following commands to start the Sybase database if it is not running:
$ su - sybase
$ . /opt/sybase/SYBASE.sh
$ cd /opt/sybase/ASE-15_0/install
$ ./startserver -f ./RUN_DBSVR &
$ ./startserver -f ./RUN_DBSVR_back &
$ exit
NOTE
Leave a space between the dot (.) and the command /opt/sybase/SYBASE.sh.
NOTE
l DBSVR is the name of the database server and DBSVR_back is the name of the database backup
server. These names must be consistent with the actual database names.
l View the database name and database backup server name by running the more /opt/sybase/
interfaces command.
3 Ensure that the U2000 is running.

Run the following command to check whether the U2000 is running:
$ daem_ps

nmsuser 27069 1 0 10:31:39 ? 1:39 imapmrb
nmsuser 27079 1 0 10:31:39 ? 0:00 imapwatchdog -cmd start
nmsuser 27075 1 0 10:31:39 ? 0:50 imapsysd -cmd start
nmsuser 27086 1 0 10:31:39 ? 0:09 imapeventmgr
nmsuser 23679 1 1 17:57:06 pts/8 0:02 imap_sysmonitor -cmd start
nmsuser 27116 1 0 10:31:40 ? 0:52 ResourceMonitor -cmd start
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start.
Run the following command to start the U2000 if it is not running:

$ cd /opt/U2000/server/bin
$ ./startnms.sh
4 Ensure that the network management system maintenance suite process is started.
Run the following command to switch to the root user:
$ su - root
password: password_of_the_root_user
Run the following command to check whether the network management system maintenance
suite process is started:
# ps -ef | grep java

root 19913 19907 0 04:04:09 pts/1 0:00 grep java

...
root 18382 18311 0 03:42:33 pts/2 12:20 /opt/HWNMSJRE/jre_sol/bin/java -
server -Dlanguage=en -Xverify:none -Xmx128m -Xm
NOTE
If the displayed information contains /opt/HWNMSJRE/jre_sol/bin/java -server, it indicates that the

network management system maintenance suite process is started.
If the network management system maintenance suite process is not started, run the following
commands to start the network management system maintenance suite process:
# cd /opt/HWENGR/engineering
# ./startserver.sh
Run the following command to switch back to the nmsuser user:

# exit
5 View the running status of each process through the System Monitor as user nmsuser to log in
to the server GUI, as follows:
CAUTION
If you cannot log in to the GUI of the server, run the svc_adm -cmd status command to view
the status of processes as user nmsuser.
1. On the desktop of the OS, double-click the U2000 System Monitor shortcut icon.
NOTE
The default ACL range is the entire network segment. It is recommended that you set the ACL
restriction range based on the security requirements. For details, see 3.2.2 Setting the Access Control
List.
2. In the dialog box that is displayed, enter the U2000 user name and password (to open the
System Monitor window). The default password of user admin is blank. You must change
the default password during first-time login.
NOTE
There are two data transmission modes, namely, Common and Security(SSL). You can run the
ssl_adm -cmd query command to query data transmission modes on the server. The ssl_adm -cmd
query command must be run as user nmsuser in Solaris and SUSE Linux OS. The default data
transmission mode is Common.
For details about how to set the communication mode on the U2000 server for the single-server
system (Solaris), see How to Set the Communication Mode on the U2000 server for the Single-Server
System (Solaris).
The U2000 is functioning properly if it can initiate in automatic startup mode, indicating
that the U2000 is functioning properly.
If a process cannot start, right-click the process and choose Start the Process from the
shortcut menu.
If the U2000 works properly, contact Huawei engineers.
6 Start the U2000 client as user nmsuser to log in to the server GUI.

CAUTION
The U2000 should be logged in to through a standalone client in the event that login to the server
through the GUI fails and login to the client on the server is not possible. For details, see 1.2.7
Logging In to the U2000 Client.
1. On the desktop of the OS, double-click the U2000 Client shortcut icon.
2. In the dialog box that is displayed, enter the U2000 user name and password to open the
main window of the client. The user name is admin and the password is the one changed
in the previous step.
NOTE
System (Solaris).
----End
1.2.3 Starting the Single-Server System (SUSE Linux-Distributed)

This topic describes how to start the Single-Server System (SUSE Linux-Distributed). After the
Single-Server System (SUSE Linux-Distributed) is started, you must start U2000 server
processes before starting a U2000 client to monitor and manage the network.
Prerequisite
The OSs of the master server and slave server must be started.
Context
l In normal cases, the network management system maintenance suite process and the daem
process of the slave server start along with the server OS.
l In normal cases, the network management system maintenance suite process and the
database process of the master server start along with the server OS.
Procedure
1 Ensure that the network management system maintenance suite process and daem process on
the slave server is started.
NOTE
If there are multiple slave servers, check them respectively.

1. Log in to the OS of the slave server as the root user.
2. Do as follows to check whether the network management system maintenance suite process
has been started:
...

root 18382 18311 0 03:42:33 pts/2 12:20 /opt/HWNMSJRE/jre_linux/bin/java

-server -Dequinox.conf=engineering/conf/installE
NOTE
If the displayed information contains /opt/HWNMSJRE/jre_linux/bin/java -server, it indicates

that the network management system maintenance suite process is started.
If the network management system maintenance suite process has not been started, run the
following commands to start it:
# ./startserver.sh
3. Do as follows to check whether the daem process of the slave server has been started:
# ps -ef|grep start

root 1702 1 0 20:48 pts/0 00:00:00 /bin/bash ./start_daem -type
StandbyNode
root 1770 1702 1 20:48 pts/0 00:00:00 /opt/U2000/server/3rdTools/
python/bin/python /opt/U2000/server/bin/script/start_daem.py -type StandbyNode
root 1782 1355 0 20:48 pts/0 00:00:00 grep start
Or a message similar to the following will be displayed:

root 27069 1 0 10:31:39 ? 1:39 imapmrb
root 27079 1 0 10:31:39 ? 0:00 imapwatchdog -cmd start
root 27075 1 0 10:31:39 ? 0:50 imapsysd -cmd start
root 27086 1 0 10:31:39 ? 0:09 imapeventmgr
root 23679 1 1 17:57:06 pts/8 0:02 imap_sysmonitor -cmd start
root 27116 1 0 10:31:40 ? 0:52 ResourceMonitor -cmd start
NOTE
If /bin/bash ./start_daem -type StandbyNode, /opt/U2000/server/3rdTools/python/bin/python,
or imapsysd -cmd start is displayed, the daem process of the slave server has been started.
If the daem process has not been started, run the following command to start it:
# /etc/init.d/u2kdaem start
2 Ensure that the network management system maintenance suite process on the master server is
started.
1. Log in to the OS of the master server as the root user.
2. Do as follows to check whether the network management system maintenance suite process
has been started:
...
root 18382 18311 0 03:42:33 pts/2 12:20 /opt/HWNMSJRE/jre_linux/bin/java
-server -Dequinox.conf=engineering/conf/installE
NOTE
If the displayed information contains /opt/HWNMSJRE/jre_linux/bin/java -server, it indicates

that the network management system maintenance suite process is started.
If the network management system maintenance suite process has not been started, run the
following commands to start it:
# ./startserver.sh
3 On the master server, do as follows to ensure that the Oracle process and the database listening
process have been started:
1. To check whether the Oracle process has been started, run the following command:
# su - oracle

> ps -ef | grep ora_

oracle 4055 1 0 20:00 ? 00:00:00 ora_j000_U2KDB
oracle 4174 4107 0 20:00 pts/1 00:00:00 grep ora_
oracle 23333 1 0 Nov15 ? 00:00:20 ora_pmon_U2KDB
oracle 23335 1 0 Nov15 ? 00:00:00 ora_vktm_U2KDB
oracle 23339 1 0 Nov15 ? 00:00:00 ora_diag_U2KDB
oracle 23341 1 0 Nov15 ? 00:00:00 ora_dbrm_U2KDB
oracle 23343 1 0 Nov15 ? 00:00:01 ora_psp0_U2KDB
oracle 23347 1 0 Nov15 ? 00:03:35 ora_dia0_U2KDB
oracle 23349 1 0 Nov15 ? 00:00:00 ora_mman_U2KDB
oracle 23351 1 0 Nov15 ? 00:00:03 ora_dbw0_U2KDB
oracle 23353 1 0 Nov15 ? 00:00:13 ora_lgwr_U2KDB
oracle 23355 1 0 Nov15 ? 00:00:15 ora_ckpt_U2KDB
oracle 23357 1 0 Nov15 ? 00:00:06 ora_smon_U2KDB
...
NOTE
l If the displayed information contains the following five processes, it indicates that the database
service is started normally.
l ora_pmon_U2KDB
l ora_dbw0_U2KDB
l ora_lgwr_U2KDB
l ora_ckpt_U2KDB
l ora_smon_U2KDB
l If the database process is not started, run the following commands to start the Oracle database
process.
> sqlplus / as sysdba
SQL> startup
ORACLE instance started.
Total System Global Area 1610612736 bytes

Fixed Size 2046264 bytes
Variable Size 385877704 bytes
Database Buffers 1207959552 bytes
Redo Buffers 14729216 bytes
Database mounted.
Database opened.
Run the following command to exit the SQL Server database.
SQL> exit
2. Run the following command to check whether the listener is started.

> lsnrctl status
...
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.1.0.7.0 - Production
Start Date 17-DEC-2009 20:35:58
Uptime 0 days 0 hr. 5 min. 2 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
...

NOTE
l If the displayed information contains Alias LISTENER, it indicates that the listener is started
normally.
l If the listen has not been started, run the following command to start it:
> lsnrctl start
3. Run the following command to log out the Oracle user:

> exit
4 On the master server, start U2000 server processes.

1. To check whether U2000 server processes have been started, run the following commands:
# cd /opt/U2000/server
# . svc_profile.sh
# daem_ps
NOTE
Leave a space between the dot . and the command svc_profile.sh.

root 27069 1 0 10:31:39 ? 1:39 imapmrb
root 27079 1 0 10:31:39 ? 0:00 imapwatchdog -cmd start
root 27075 1 0 10:31:39 ? 0:50 imapsysd -cmd start
root 27086 1 0 10:31:39 ? 0:09 imapeventmgr
root 23679 1 1 17:57:06 pts/8 0:02 imap_sysmonitor -cmd start
root 27116 1 0 10:31:40 ? 0:52 ResourceMonitor -cmd start
NOTE
2. If the U2000 processes are not started, run the following command to start U2000 processes:
# cd /opt/U2000/server/bin
# ./startnms.sh
5 Start the U2000 client.

NOTE
Because no U2000 client and System Monitor client are available in the SUSE Linux OS, log in to the
independent U2000 client. For details, see 1.2.7 Logging In to the U2000 Client.
----End
1.2.4 Starting the High Availability System (Windows)

Procedure
1 Log in to the OS of the server of the active site.
2 Choose Start > Programs > Symantec > Veritas Cluster Server > Veritas Cluster Manager
- Java Console to start the VCS client.

3 Choose File > New Cluster, as shown in the following figure.
4 Enter the IP address of the system of the primary site. Then, click OK.
5 Enter the default user name admin and the initial password password of the VCS client. Then,
click OK. The Cluster Explorer window is displayed.
6 In the Cluster Explorer window, right-click the AppService resource group in the navigation
tree and choose Online > primary from the shortcut menu to start the database process and the
NMS server process.
TIP
Click the Resources tab to view the start status of each resource.
Normally, on the Status tab page, State of the server of the active site in the Group Status on
Member Systems area is Online, and Status in the Resource Status area is Online on
primary.
NOTE
In actual configuration, use the actual host name.
7 View the running status of each process through the System Monitor. Details are as follows:
NOTE
List.

NOTE
System (Solaris).
shortcut menu.

1. On the desktop, double-click the U2000 Client shortcut icon.
2. In the dialog box that is displayed, enter a U2000 user name and password. If you have
changed the password for the admin user when logging in to the System Monitor, enter
the new password.
NOTE
There are two data transmission modes, namely, Common and Security(SSL). You can query data
transmission modes on the server. The default data transmission mode is Common. For details, see
How to Set the Communication Mode on the U2000 Server for the High Availability System
(Windows).
----End
1.2.5 Starting the High Availability System (Solaris)

Procedure
1 Log in to the OS of the server of the active site as the root user.
2 Run the following command to start the VCS client:

# hagui &

4 Enter the IP address of the Heartbeat network service of the primary site. Then, click OK.
tree and choose Online > primary from the shortcut menu to start the Sybase process and the
NMS server process.
TIP
primary.
NOTE
l In actual configuration, use the actual host name.

l If a fault has occurred when the AppService process is started before, right-click AppService and choose
clear fault from the shortcut menu. Then, choose Online > host_name to start the AppService process.
7 In the dialog box that is displayed, click Yes.
8 View the running status of each process through the System Monitor as user nmsuser to log in
to the server GUI, as follows:
CAUTION
If you cannot log in to the GUI of the server OS, do as follows to view the process status:
1. Run the su - nmsuser command to switch to the nmsuser user.
2. Run the svc_adm -cmd status command to view the process status.
1. Log in the OS as nmsuser user.


NOTE
l If the client and server applications are on the same host and the server uses the SSL mode, then
the client can use the Common or SSL mode. The client can only use the Common mode if the
server uses the Common mode.
l If the client and server applications are not on the same host, the client can log in to the server
only when it uses the same mode as the server.
For details about how to set the communication mode on the U2000 server for the HA system
(Solaris), see How to Set the Communication Mode of the Server in a High Availability System
(Solaris)?.
shortcut menu.
9 Log in to the U2000 client.
If the server is equipped with a monitor, you can directly log in to the U2000 client from the
server. If the server is not equipped with any monitor, you can log in to the server through the
remote desktop control software.
NOTE
If you fail to log in to the server through the GUI, you cannot log in to the client on the server side. In this case,
you need to log in to the server through an independent client. For details, see 1.2.7 Logging In to the U2000
Client.
1. Access the Java Desktop System, Release 3 session process of the OS as the nmsuser
user.
NOTE
If the Solaris Registration Wizard dialog box is displayed, click the Run the Solaris software
without registering option button and then click Next. In the dialog box that is displayed, click
Never Register.
2. Log in to the U2000 client.
a. On the desktop of the Java Desktop System, Release 3, double-click the U2000
Client shortcut icon.
b. In the dialog box that is displayed, enter the U2000 user name and password to access
the main window of the client.
c. If you need to log in to the server through another client, you must set the ACL login
control right of other servers in the main window of the client. For details, see the
Help.
----End

1.2.6 Starting the High Availability System (SUSE Linux-

Distributed)
Prerequisite
The OSs of all the servers, including the master server and slave server, of the primary and
secondary sites must be started.
Procedure
1 Log in to the OS of the master server of the active site as the root user.
2 Run the following command to start the VCS client:
# hagui &
4 Enter the system IP address of the master server of the primary site. Then, click OK.
tree and choose Online > primary from the shortcut menu to start the Oracle process and the
NMS server process.
TIP

primary.
NOTE
In actual configuration, use the actual host name.

NOTE
Because no U2000 client and System Monitor client are available in the SUSE Linux OS, log in to the
independent U2000 client. For details, see 1.2.7 Logging In to the U2000 Client.
----End
1.2.7 Logging In to the U2000 Client

Log in to a U2000 using the client, and then perform management operations in the GUI of the
U2000 client.
Prerequisite
Before logging in to the U2000 client, ensure that the following conditions are met:
l The U2000 processes are started.
l The network communication between the U2000 client and the U2000 is available.
NOTE
Run the ping peer_IP_address command to check network communication.

– In a single-server system (centralized), the IP address is the system IP address of the
server.
– In a single-server system (distributed), the IP address is the system IP address of the
master server.
– In a high availability system (centralized), the IP address is the IP address of NMS
application network in the active site server.
– In a high availability system (distributed), the IP address is the IP address of NMS
application network in the master server of active site.
l The ports used between the U2000 client and the U2000 are opened by the firewall. See
Ports Between the U2000 Server and the Clients.
l The IP address of the client must be contained in the access control list (ACL) that is
configured on the U2000.
NOTE
List.
l The legitimate U2000 user account and password must be allocated.
Context
By default, after you enter an incorrect password for three consecutive times, the user account
that you use is locked by the U2000. The super user admin can unlock the account of a common
user. In addition, the system can automatically unlock the account in 30 minutes.

Procedure
1 Log in to the OS where the client program is installed.
l On Windows OS, log in to the OS as user administrator.
l On Solaris OS, log in to the GUI as user nmsuser.
2 On the OS desktop, double-click the U2000 Client shortcut icon. The Login dialog box is
displayed.
TIP
l In the case of a Windows OS, you can double-click the startup_all_global.bat file in the D:\U2000
\client directory to start the client.
l In the case of a Solaris OS, you can run the command of ./startup_all_global.sh in the /opt/U2000/
client directory to start the client.
3 In the Server drop-down list, select the server to be logged in to. Then, set User Name and
Password to the valid values, and click Login.
l If the intended server is not configured, perform the following operations to add a server:
1. Click the ... button. In the Server List dialog box, click Add.
2. In the Add Server Information dialog box, set the parameters of the U2000 server to
be added, and then click OK.
Table 1-1 Server parameter settings

Parameter Settings
Name It is recommended that you set this parameter to the IP address

for login or the related host name.
Server Name (or It is recommended that you set this parameter to an IP address.
IP Address) l In a single-server system (centralized), the IP address is the
system IP address of the server.
l In a single-server system (distributed), the IP address is the
system IP address of the master server.
l In a high availability system (centralized), the IP address is
the IP address of NMS application network in the active site
server.
l In a high availability system (distributed), the IP address is the
IP address of NMS application network in the master server
of active site.
Port There are two data transmission modes, namely, Common and
Security(SSL). By default, port 31037 is used in Common mode
and port 31039 is used in Security(SSL) mode.

Parameter Settings
Mode There are two data transmission modes, namely, Common and
Security(SSL). You can run the ssl_adm -cmd query command
to query data transmission modes on the server. The ssl_adm -
cmd query command must be run as user nmsuser in Solaris and
SUSE Linux OS. The default data transmission mode is
Common.
For details about how to set the communication mode on the
U2000 server for the single-server system (Solaris), see How to
Set the Communication Mode on the U2000 server for the Single-
Server System (Solaris).
l For details about how to set the communication mode on the
U2000 server for the single-server system (Windows), see
How to Set the Communication Mode on the U2000 server
for the Single-Server System (Windows).
U2000 server for the single-server system (Solaris), see How
to Set the Communication Mode on the U2000 server for the
Single-Server System (Solaris).
U2000 server for the single-server system (Linux), see How
to Configure the Communication Mode for a Linux-based
U2000 Server?.
U2000 server for the High Availability System (Windows),
see How to Set the Communication Mode on the U2000
Server for the High Availability System (Windows).
U2000 server for the High Availability System (Solaris), see
How to Set the Communication Mode of the Server in a High
Availability System (Solaris)?.
U2000 server for the High Availability System (Linux), see
How to Set the Communication Mode of the Server in a High
Availability System (SUSE Linux-Distributed).
NOTE
l If the client and server applications are on the same host and the server
uses the SSL mode, then the client can use the Common or SSL mode.
The client can only use the Common mode if the server uses the
Common mode.
l If the client and server applications are not on the same host, the client
can log in to the server only when it uses the same mode as the server.
3. In the Server List dialog box, select a record from the record list. Then, click OK.
l When you log in to the U2000 client, if the system detects that the local version is earlier
than the server version, a prompt is displayed, asking you whether to upgrade the client.
– Click Yes to upgrade the client.

– Click No to log in to the client.
----End
Result
After the login to the U2000 client is successful, the U2000 client obtains related data from the
U2000.
1.3 Shutting Down the U2000

This topic describes how to shut down the U2000 server and client. The shutdown procedure
varies according to the deployment scheme.
1.3.1 Shutting Down the U2000 Client
This topic describes how to shut down the U2000 client. You need to shut down the U2000 client
before the U2000 server.
1.3.2 Shutting Down the Single-Server System (Windows)
In any situation, you must follow the correct procedure for powering off the server as required,
ensuring that the server is shut down in a secure manner.
1.3.3 Shutting Down the Single-Server System (Solaris)
This topic describes how to shut down the system. Do not power off the U2000 when it is properly
managing NEs. The U2000 only needs to be shut down in special circumstances (such as
switching the power supply).
1.3.4 Shutting Down the Single-Server System (SUSE Linux-Distributed)
This topic describes how to shut down the U2000 Single-Server System (SUSE Linux-
Distributed).
1.3.5 Shutting Down the High Availability System (Windows)
1.3.6 Shutting Down the High Availability System (Solaris)
1.3.7 Shutting Down the High Availability System (SUSE Linux-Distributed)
1.3.1 Shutting Down the U2000 Client

This topic describes how to shut down the U2000 client. You need to shut down the U2000 client
before the U2000 server.
Prerequisite
The U2000 client must start normally.

Procedure
1 Choose File > Exit from the main menu.
2 In the Confirm dialog box, click OK.
If certain operations on the system topology are performed but not saved, a prompt is displayed,
asking you whether to save the operations.
----End
1.3.2 Shutting Down the Single-Server System (Windows)

In any situation, you must follow the correct procedure for powering off the server as required,
ensuring that the server is shut down in a secure manner.
Procedure
1 Exit all running U2000 clients.
2 Stop U2000 services and processes.
1. Run the stopserver.bat file in the U2000 path, that is, C:\HWENGR\engineering, to end
the U2000 MSuite processes.
2. Run the stopnms.bat file in the U2000 path, for example, D:\U2000\server\bin, to end
U2000 processes.
3 Stop the SQL Server database service.
1. Choose Start > Programs > Microsoft SQL Server > Service Manager.
2. In the dialog box shown in the following figure, click .
3. In the dialog box that is displayed, click Yes.

4 Shut down the Windows OS.
----End
1.3.3 Shutting Down the Single-Server System (Solaris)


Context
l Always follow site-specific procedures for powering off the server to ensure that it is safely
shut down.
l The system may fail to recover if the halt command is used to shut down the server or if
the server is directly powered off.
Procedure
2 Log in to the OS of the server as the nmsuser user.
3 Ensure that the U2000 is not running:
To check the running status of the U2000 process, run the following command:
$ daem_ps

nmsuser 27069 1 0 10:31:39 ? 1:39 imapmrb
nmsuser 27079 1 0 10:31:39 ? 0:00 imapwatchdog -cmd start
nmsuser 27075 1 0 10:31:39 ? 0:50 imapsysd -cmd start
nmsuser 27086 1 0 10:31:39 ? 0:09 imapeventmgr
nmsuser 23679 1 1 17:57:06 pts/8 0:02 imap_sysmonitor -cmd start
nmsuser 27116 1 0 10:31:40 ? 0:52 ResourceMonitor -cmd start
NOTE
Run the following commands to stop U2000 if it is running:

$ cd /opt/U2000/server/bin
$ ./stopnms.sh
4 Ensure that the Sybase database is not running.

Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase

sybase 4848 4847 0 May 18 ? 167:11 /opt/sybase/ASE-15_0/bin/data
server -sDBSVR -d/opt/sybase/data/lv_master -e/opt
sybase 5250 5248 0 May 18 ? 0:00 /opt/sybase/ASE-15_0/bin/back
upserver -SDBSVR_back -e/opt/sybase/ASE-15_0/insta
5_0/install/RUN_DBSVR
5_0/install/RUN_DBSVR_back
...
NOTE
The database is running if the displayed information contains /opt/sybase/ASE-15_0/install/

RUN_DBSVR and /opt/sybase/ASE-15_0/install/RUN_DBSVR_back.
Run the following commands to stop the Sybase database if it is running:

$ su - sybase
$ . /opt/sybase/SYBASE.sh
$ cd /opt/sybase/OCS-15_0/bin
$ ./isql -SDBSVR -Usa -Pchangeme
1> shutdown SYB_BACKUP

2> go
1> shutdown
2> go
$ exit
NOTE
l Leave a space between the dot (.) and the command /opt/sybase/SYBASE.sh.
l In the ./isql -SDBSVR -Usa -Pchangeme command, changeme is the password of user sa of the Sybase
database.
5 Run the following commands to switch to user root:

$ su
password: password_of_root_user
6 Run the following commands to shut down the OS:

# sync;sync;sync;sync
# shutdown -y -g0 -i5
----End
1.3.4 Shutting Down the Single-Server System (SUSE Linux-

Distributed)
This topic describes how to shut down the U2000 Single-Server System (SUSE Linux-
Distributed).
Context
Shutting down the Single-Server System (SUSE Linux-Distributed) includes stopping the
U2000 server processes and database.
Procedure
2 Log in to the OS of the master server as the root user.
3 Run the following commands to stop the U2000:

# cd /opt/U2000/server/bin
# ./stopnms.sh
4 Run the following commands to stop the Oracle process.

> su - oracle
> sqlplus / as sysdba
SQL> shutdown immediate
SQL> exit
> exit
----End
1.3.5 Shutting Down the High Availability System (Windows)


Procedure
2 On the primary site, do as follows to stop the U2000 processes:

1. Choose Start > Programs > Symantec > Veritas Cluster Server > Veritas Cluster
Manager - Java Console to start the VCS client.
2. Choose File > New Cluster. A dialog box is displayed, as shown in the following figure.
3. Enter the IP address of the system of the primary site. Then, click OK.
4. Enter the default user name admin and the default password password of the VCS client.
Then, click OK.
5. Right-click AppService in the navigation tree and choose Offline > host_name from the
shortcut menu.
6. In the dialog box that is displayed, click Yes.
Wait patiently. If all the resources on the Resources tab page turn grey, it indicates that the NMS
processes are stopped.
3 Log in to the server of the active site and run the following commands to stop the VCS service:
C:\> hastop -all -force
In the Task Manager, check whether the had.exe process exists. If yes, right-click the process
and stop it.
4 Log in to the server of the standby site and perform the preceding step to stop the VCS service
on the server of the standby site.
5 Shut down the OS of the standby site.

1. Choose Start > Shut Down.

2. In the dialog box that is displayed, select Shut Down. Then, click OK.
6 Shut down the OS of the active site.
1. Choose Start > Shut Down.
2. In the dialog box that is displayed, select Shut Down. Then, click OK.
----End
1.3.6 Shutting Down the High Availability System (Solaris)

Procedure
2 Stop the U2000 processes.
The U2000 processes consist of the U2000 server process and the Sybase process.
Check whether the U2000 processes are stopped and perform the following operations:
1. Access the Java Desktop System, Release 3 session of the OS of the server of the active
site as the root user.
2. Run the following command to start the VCS client:
# hagui &
4. Enter the IP address of the Heartbeat network service of the primary site. Then, click
OK.

Then, click OK.
6. Select the AppService resource group from the navigation tree, click the Status tab, and
then view the status of the U2000 processes.
l If Group Status on Member Systems is displayed as Offline, it indicates that the
U2000 processes are stopped.
l If Group Status on Member Systems is displayed as Online, it indicates that the
U2000 processes are started. Do as follows to stop the U2000 processes:
Right-click AppService and choose Offline > host_name from the shortcut menu.
3 Log in to the server of the active site as user root and run the following commands to stop the
VCS service:
# cd /opt/VRTSvcs/bin
# hastop -local -force
4 Run the following command to verify that the VCS service is stopped:
# ps -ef|grep had
A message similar to the following will be displayed:

root 27663 17299 0 00:31:00 pts/2 0:00 grep had
NOTE
If the had and hadshadow processes are not displayed, the VCS service is successfully stopped; otherwise,
run the kill -9 process ID command to stop the related processes.
5 Log in to the server of the standby site as the root user and perform the preceding two steps to
stop the VCS service on the server of the standby site.
6 Shut down the OS of the standby site.
1. Log in to the OS of the standby site as the root user.
2. Run the following command to shut down the OS of the standby site:
7 Run the following command to shut down the OS of the active site:
----End
1.3.7 Shutting Down the High Availability System (SUSE Linux-

Distributed)

Procedure
2 Stop the U2000 processes.
The U2000 processes consist of the U2000 server process and the Oracle process.
Check whether the U2000 processes are stopped. Do as follows:
1. Access the GNOME session process of the OS of the master server of the active site as the
root user.
NOTE
Do as follows to access the GNOME session process: Select GNOME from Session Type.
2. Run the following command to start the VCS client:
# hagui &
4. Enter the system IP address of the master server of the primary site. Then, click OK.
Then, click OK.
6. Select the AppService resource group from the navigation tree, click the Status tab, and
then view the status of the U2000 processes.
l If Group Status on Member Systems is displayed as Offline, it indicates that the
U2000 processes are stopped.
l If Group Status on Member Systems is displayed as Online, it indicates that the
U2000 processes are started. Do as follows to stop the U2000 processes:
Right-click AppService and choose Offline > host_name from the shortcut menu.

3 Log in to the OS of the master server of the active site as the root user and run the following
commands to stop the VCS service:
# cd /opt/VRTSvcs/bin
# hastop -local -force
4 Run the following command to verify that the VCS service is stopped:
# ps -ef|grep had

root 27663 17299 0 00:31:00 pts/2 0:00 grep had
NOTE
If the had and hadshadow processes are not displayed, the VCS service is successfully stopped; otherwise,
run the kill -9 process ID command to stop the related processes.
5 Log in to the master server of the standby site as the root user and perform the 3 and 4 orderly
to stop the VCS service on the master server of the standby site.
6 Shut down the OS of the slave server of the standby site.
NOTE
If the standby site has multiple slave servers, do as follows on each slave server:
1. Log in to the OS of the slave server of the standby site as the root user.
2. Run the following command to shut down the OS of the slave server of the standby site:
# shutdown -h now
7 Shut down the OS of the master server of the standby site.

1. Log in to the OS of the master server of the standby site as the root user.
2. Run the following command to shut down the OS of the master server of the standby site:
# shutdown -h now
8 Shut down the OS of the slave server of the active site.

NOTE
If the active site has multiple slave servers, do as follows on each slave server:
1. Log in to the OS of the slave server of the active site as the root user.
2. Run the following command to shut down the OS of the slave server of the active site:
# shutdown -h now
9 Run the following command to shut down the OS of the master server of the active site:
# shutdown -h now
----End
1.4 Changing the Password of the Current User

This topic describes how to change the password of your account. It is suggested that you should
change the password periodically to improve the password security of your account.
Context
The new password must comply with the password policy.

Procedure
1 Choose File > Change Password from the main menu.
2 In the Change Password dialog box, set the new password for the current user.
3 Click OK.
4 In the dialog box, click OK.
----End
1.5 Using the Workbench and Favorites Folder

This topic describes how to use the workbench and the favorites folder of commonly used
functions to rapidly locate the commonly used functions of the U2000.
1.5.1 Placing a Shortcut Icon on the Workbench
This topic describes how to place the shortcut icons of the commonly used functions on the
workbench and create function links. You can use the shortcut icons to improve the operation
efficiency.
1.5.2 Adding a Common Function to the Favorites Folder
This topic describes how to add a common function to the favorites folder. You can easily open
a common function view through the customized favorites folder.
1.5.3 Viewing Common Functions
This topic describes how to view common functions on the workbench or in the favorites folder.
1.5.1 Placing a Shortcut Icon on the Workbench

This topic describes how to place the shortcut icons of the commonly used functions on the
workbench and create function links. You can use the shortcut icons to improve the operation
efficiency.
Context
If + is appended to a menu option on the main menu of the NMS, it indicates that you can create
the shortcut of this menu option on the workbench.
Procedure
1 In the main window of the U2000, click the drop-down button to the right of the icon and
then choose Style of Desktop to access the workbench.
2 Right-click Workbench and choose Create Shortcut from the shortcut menu.
1. In the Create Shortcut dialog box, select the function that needs to be added with a shortcut
icon.

2. Click Create. The shortcut icon of the related function is displayed on the workbench.
3 Right-click Workbench and choose Create Executable Application from the shortcut menu.
1. In the Create Executable Application dialog box, enter or select the parameters of the
function that needs to be added with a shortcut icon.
2. Click Create. The shortcut icon of the related function is displayed on the workbench.
----End
1.5.2 Adding a Common Function to the Favorites Folder

This topic describes how to add a common function to the favorites folder. You can easily open
a common function view through the customized favorites folder.
Prerequisite

Context
When the NMS is started for the first time, the shortcut function view of the favorites folder is
displayed as a floating window on the Workbench. The default shortcut nodes, such as the alarm,
and Main Topology are displayed in the floating window.
Procedure
1 Click the drop-down arrow in the icon on the toolbar.
2 In the drop-down list that is displayed, click Style of Favorites Folder.
3 Right-click the Default Workbench node.
4 Choose Add Menu Shortcut from the shortcut menu.
5 The Add Menu Shortcut window is displayed.
6 Select the node to be added to the favorites folder, and then click Create.
----End
Result
The added node is displayed in the Default Workbench node in the favorites folder.
1.5.3 Viewing Common Functions

This topic describes how to view common functions on the workbench or in the favorites folder.
Prerequisite
Context
When the NMS is started for the first time, the shortcut function view of the favorites folder is
displayed as a floating window on the Workbench. The default shortcut nodes, such as the alarm,
and Main Topology are displayed in the floating window.
Procedure
1 Click the drop-down arrow in the icon on the toolbar.
2 In the drop-down list that is displayed, click Style of Desktop or Style of Favorites Folder.
3 If Style of Desktop is clicked, the Workbench window is displayed, and the common functions
are displayed as floating icons, as shown in Figure 1-1.

Figure 1-1 Workbench
4 If Style of Favorites Folder is clicked, the Workbench dialog is displayed. If you click + of
the Default Workbench node or double-click the Default Workbench node, the common
functions are expanded, as shown in Figure 1-2.
Figure 1-2 Workbench
----End
Follow-up Procedure
Right-click each common function and then you can choose to delete or modify it.

1.6 Setting the Parameters for the Communication Between

the U2000 and NEs
This topic describes how to set parameters for the communication between the U2000 and NEs.
Properly setting these parameters is the prerequisite to the normal communication between the
U2000 and NEs. You need to set these parameters in time.
1.6.1 Protocols for Communications Between the U2000 and NEs
This topic describes the protocols for communications between the U2000 and NEs.
1.6.2 Configuring the Default SNMP Parameters Template
This topic describes how to correctly set the default SNMP parameters on the U2000 to ensure
the normal communication between the U2000 and the managed NEs.
1.6.3 Setting NE SNMP Parameters
This topic describes how to correctly set NE SNMP parameters to ensure the normal
communication between the U2000 and the managed NEs.
1.6.4 Configuring a Telnet/STelnet Parameter Template
This topic describes how to configure a Telnet/STelnet parameter template. With the Telnet/
STelnet parameter template, you can set the Telnet/STelnet parameters for multiple equipment
at the same time.
1.6.5 Setting Telnet/STelnet Parameters with a Template
This topic describes how to use a template to set the Telnet/STelnet parameters of the U2000
for the communication with equipment.
1.6.6 Manually Modifying Equipment Telnet/STelnet Parameters
This topic describes how to manually modify equipment Telnet/STelnet parameters.
1.6.1 Protocols for Communications Between the U2000 and NEs

This topic describes the protocols for communications between the U2000 and NEs.
Communications between the U2000 and NEs in the IP/access domain

Figure 1-3 shows the topology for the communication between the U2000 and NEs in the IP
domain.
Figure 1-3 Topology for communications between the U2000 and NEs in the IP/access domain
U2000
SNMP/Telnet/SFTP/FTP/SSH
GGSN
Enterprise1
2G/3G RAN
PE P P PE
Enterprise2 Switch
IPv6 IPv6 IPv6 IPv6
IP/MPLS CORE ATM/FR
Enterprise3 IPv6 IPv6

GGSN
IPv6 IPv6
PE P PE Internet
P
DSLAM
Internet

The SNMP and Telnet parameters need to be set for the NEs such as routers, switches, Metro
Ethernet, security gateways, service interception gateways, SVN NEs, and access NEs,.
Communications between the U2000 and NEs in the transport domain

U2000The NMS manages and maintains NEs by communicating with NEs through TCP/IP and
the OSI protocol.Figure 1-4 shows the topological diagram of the communications between the
NMS and NEs.
Figure 1-4 Topology for communications between the U2000 and NEs in the transport domain
U2000
IP/OSI
DCN Extenal DCN
HW ECC or
IP/OSI over
DCC
Internal DCN
OptiX optical transmission equipment
LAN switch
The NEs in the transport domain support two types of protocols for communications with the
U2000. The MSTP, WDM, RTN, PTN and Marine cable NEs support the TCP/IP, and OSI
protocols. The NG WDM and the NA OTN, however, do not support the OSI protocol.

Prerequisite
l You must be an NM user with the "Topo Maintainer" authority or higher.
l This operation is applicable to the Router series, Switch series, Security series, Access
series NEs.

Context
It is forbidden to delete the default access protocol parameter template.
Procedure
1 Choose Administration > NE Communicate Parameter > Default Access Protocol
Parameters from the main menu. Click Display.
2 In the Default Access Protocol Parameters dialog box, click the related tab to switch to the
page for configuring protocol parameters. The following figure shows how to set SNMPv3
parameters.
3 Configure the NE SNMP parameter template as follows:

l Add a parameter template.
Click Add. After setting all the parameters in the parameter setting area at the bottom of
the window, click OK.
l Modify a parameter template.
Double-click the template to be modified in the parameter template list. Modify the related
parameters in the Common parameters and SNMP v3 Security Parameters areas. Then,
click Apply.
NOTE
l Associated parameters in only the Common parameters area need to be modified for SNMPv1
and SNMPv2.
l The Template Name parameter cannot be modified.
l Delete a parameter template.
Select the template to be deleted in the parameter template list and then click Delete. In the
Confirm dialog box, click Yes.
----End


Prerequisite
l Applies to the Router series, Switch series, Security series, Access series NEs.
Context
According to different NE types, the U2000 can access the NEs to be managed through SNMP
or MML. During the manual or automatic creation of an SMMP or a /MML NE, the U2000 uses
the default /MML parameter template to map to the specified NEs so that the SNMP/MML
protocol parameters that are supported by the NEs to be managed can be determined. The
SNMP/MML parameter template that is successfully mapped acts as the SNMP/MML parameter
setting for the NE. All further management operations on the NE take the SNMP/MML
parameter. When the NE access protocol parameter changes, you need to modify the access
protocol parameter of the specified NE.
Procedure
1 Select a NE node or subnet in the navigation tree.
NOTE
l To select multiple NE nodes simultaneously, press Ctrl and then click the desired NE nodes.
l When no NE node is selected, the SNMP/MML parameter setting list displays the SNMP/MML
parameter settings of all NEs.
2 Choose Administration > NE Communicate Parameter > NE Access Protocol

Parameters from the main menu.
3 The template details are as follows:

l In the NE Access Protocol Parameters window, select a parameter template and then click
Display.
l In the NE Access Protocol Parameters window, double-click a record in the NE parameter
list.
The details about the selected record are displayed in the lower part of the window.
4 Modify the relate parameters as follows:

1. Enter the desired value in the related text box.

2. Click Test.
The test result is displayed in a dialog box.
3. Click Apply to save the modification.
NOTE
l In the NE Access Protocol Parameters window, click Reset. In the dialog box that is displayed, select,
add, or delete the protocol template of the related SMMP version as required. Then, click Display. The
details about the related protocol template are displayed. The template parameters cannot be set in this
dialog box.
l Set a parameter of the protocol template. Choose Administration > NE Communicate Parameter >
Default Access Protocol Parameters from the main menu. Double-click a record in the parameter
list. Then, click Apply to save the modification.
----End
1.6.4 Configuring a Telnet/STelnet Parameter Template

This topic describes how to configure a Telnet/STelnet parameter template. With the Telnet/
STelnet parameter template, you can set the Telnet/STelnet parameters for multiple equipment
at the same time.
Prerequisite
This operation is applicable to the Router series, Switch series, Security series NEs.
Procedure
1 Choose Administration > NE Communicate Parameter > NE Telnet/STelnet Template
Management from the main menu.
2 In the dialog box that is displayed, click Create.

NOTE
In the scenario where only part of the parameters of a default template or created template need to be modified,
select the desired template, and then modify associated parameters in the Details area.
3 In the dialog box that is displayed, select the desired protocol type, set Template Name, and
then click OK. The following figure shows how to create a STelnet template.
Add a template record in the Telnet/STelnet Template Information area.

4 Select the created template. Then, set associated parameters in the Details area.
5 Click Apply.
The Telnet/STelnet parameter template is configured.
6 Click OK.
The dialog box is closed.
----End
1.6.5 Setting Telnet/STelnet Parameters with a Template

This topic describes how to use a template to set the Telnet/STelnet parameters of the U2000
for the communication with equipment.
Prerequisite
l The related parameters, such as the user name and password, must be set on equipment.
l The Telnet/STelnet template must be configured on the U2000.
l This operation is applicable to the Router series, Switch series, Security series NEs.
Context
Security authentication modes are not adopted for the Telnet mode. Packets are transmitted
through TCP in plain text, which brings security risks. The U2000 adopts STelnet to reduce
security risks, using SSH features to ensure security and effective authentication.
Procedure
1 In the Main Topology, select the equipment whose Telnet or STelnet parameters need to be set.
2 Choose Administration > NE Communicate Parameter > Set NE Telnet/STelnet

Parameter from the main menu.

NOTE
You can also right-click the selected equipment and then choose Set NE Telnet/STelnet Parameter from
the shortcut menu.
3 In the dialog box that is displayed, select a desired template, and then click OK.
4 In the Select Telnet/STelnet Template dialog box, select the template to be used, and then click
OK.
5 Click Test.
l If the message indicating successful test is displayed, click OK.
l If the message indicating test failure is displayed, modify the settings of the Telnet/STelnet
parameters according to the prompt.
6 Click OK.
----End
1.6.6 Manually Modifying Equipment Telnet/STelnet Parameters

This topic describes how to manually modify equipment Telnet/STelnet parameters.
Prerequisite
Context
In the U2000, you can configure one Telnet parameter template and one STelnet parameter
template. If required, you can manually modify the configured templates to set the Telnet/
STelnet parameters for equipment.
Procedure
1 In the Main Topology, select the equipment whose Telnet/STelnet parameters need to be
modified.

2 Choose Administration > NE Communicate Parameter > Set NE Telnet/STelnet

Parameter from the main menu.
NOTE
You can also right-click the selected equipment and then choose Set NE Telnet/STelnet Parameter from
the shortcut menu.
3 In the Details group box of the Device Telnet/STelnet Parameter Management dialog box,
modify Telnet/STelnet parameters manually.
l To modify Telnet parameters:
Set Protocol Name to Telnet.
l To modify STelnet parameters:
Set Protocol Name to STelnet.
4 Click Apply.
5 Click Test.
l If the message indicating successful test is displayed, click OK.
l If the message indicating test failure is displayed, modify the settings of the Telnet/STelnet
parameters according to the prompt.
6 Click OK.
----End
1.7 Setting or Modifying the Character Set of an NE

To meet the global requirements, the U2000 provides the function of setting or modifying NE
character sets to prevent the language change from resulting in illegible characters.
1.7.1 Character Set
This topic describes the GBK, ISO-8859-1, and UTF-8 character sets of the U2000 and the
precautions of setting character sets.
1.7.2 Setting or Modifying Character Sets in Batches
This topic describes how to set or modify character sets in batches.
1.7.1 Character Set

This topic describes the GBK, ISO-8859-1, and UTF-8 character sets of the U2000 and the
precautions of setting character sets.
Character Set Introduction

Character Set Description
GBK Chinese character set which indicates that the

NEs support only Chinese characters.
ISO-8859-1 Latin character set which indicates that the

NEs support only western-Europe characters.

Character Set Description
UTF-8 Unicode encoding mode which indicates that

the NEs support Chinese, English, Spanish,
Russian, German, Portuguese, Italian,
French, and Arabic characters.
Description of Character Sets on the U2000

l If the character set that an NE transfers to the U2000 is different from the character set of
the interface data (NE source file) on the U2000, the data transferred to the U2000 is
displayed as illegible characters. The data that the U2000 applies to the NE is also displayed
as illegible characters, resulting in the read failure of the NE. Therefore, modifying
character sets is not allowed. Character sets are set only when illegible characters are
displayed. The setting rules are as follows:
NMS Language Character Set
Chinese GBK
English ISO-8859-1
Spanish UTF-8
Russian
German
Portuguese
Italian
French
Arabic
l In the case of the MSTP, WDM, RTN, PTN, router, and switch NEs, if the character sets
on an NE are changed, the U2000 refreshes the character sets in real time so that the
character sets on the U2000 are the same as those of the NE. At the same time, the
U2000 notifies the user that the NE character sets are changed by means of an event.
l In the case of a new NE, if the data on the U2000 has illegible characters or the language
changes, you can query and modify the character set attribute of a single NE or NEs in
batches in the NE Charset Management window.
l The character set of an old NE cannot be modified because it does not have the character
set attribute interface. In the NE Charset Management window, if the queried NE an old
NE, the related record is grayed out.
CAUTION
Modifying character sets is not a commonly performed operation. Generally, it is not allowed
to modify character sets. If there is a definite multi-language requirement and the character set
needs to be changed to UTF-8, you need to transcode the data of original character set on the
NE to ensure that the original data is normally displayed.

Relationship Between Characters and Bytes

In user manuals, the description of the restrictions on entering characters in text boxes is specific
to only the English characters. For the restrictions on other languages, see the following table
and calculate the occupied bytes of each language.
Language Bytes occupied by a character
Chinese 3
English 1
Spanish 3
Russian 3
German 3
Portuguese 3
Italian 3
French 3
Arabic 2
List of New NEs

The NEs supporting the preceding nine languages are the globalized NEs. The NEs that are
globalized are new NEs, whereas the NEs that are not planed with globalization are old NEs.
The following table lists the NEs that are globalized.
Field NE
Access MA5600T V800R007, MxU V800R307C01, MA5600

V300R005C00
Transport OSN8800 V100R005, OSN6800/3800 V100R005,

OSN6800A/3800A V100R005, OSN1800 V100R002,
OSN1600S V100R004, OSN7500/3500/2500/1500
V100R010, Metro1000 V300R007, OSN500 V100R003,
RTN900 V100R002, RTN600 V100R004
Router NE40E&80E V300R008, NE40E&80E V300R009,

NE5000E V600R001
MetroEth PTN Frame-shape (PTN3900/1900) V100R002C02 and Box-

ernet shape (PTN950/910/912) V100R002C01
Switch Switch 93 V100R003
1.7.2 Setting or Modifying Character Sets in Batches

This topic describes how to set or modify character sets in batches.

Prerequisite
You must be an NM user with "NE administrator" authority or higher.
The U2000 client must be started.
Context
l If multiple languages are required when an NE is created, set the character set to UTF-8
to support multiple language entering.
l If multiple languages are required when an NE is upgraded, set the character set of the NE
to UTF-8 to support multiple language entering.
l If illegible characters are displayed after an NE is upgraded and the character set is set for
the NE, you can restore the setting to the original character set.
Procedure
1 Choose Configuration > NE Batch Configuration > NE Charset Management from the main
menu.
2 In the NE Charset Management window, select one or more NEs in the left pane and click the
double-right-arrow button (red).
3 Click the Query button in the lower right corner.
4 Click Close in the Operation Result dialog box.
5 Select one or more NEs which to be modified, right-click in the Charset column and then choose
from the shortcut menu to modify the character set.
CAUTION
The setting of an error character set may cause illegible characters.
6 After setting or modifying the character set, click the Apply.
----End
1.8 Main Windows and Common Operations of the U2000

This topic describes the main windows of the U2000 client. Learning the main windows helps
you to locate the entrances to operations quickly, which increased your operation efficiency.
1.8.1 Components of the Client GUI

This topic describes the components of the client GUI.
1.8.2 Key GUI Components
The key U2000 GUI components are as follows:
1.8.3 Frequently Used Buttons
The frequently used buttons on the U2000 GUI are as follows:
1.8.4 Shortcut Icon

This topic describes the frequently used shortcut icons on the U2000 Client.
1.8.5 Common Shortcut Keys
This topic describes the common shortcut keys. Using shortcut keys, you can increase the
operation efficiency. The shortcut keys include Enter, Ctrl, Esc, and Tab.
1.8.6 Main Windows
This topic describes the main windows of the U2000 client. And tells you what you can do in
the windows.
1.8.7 Menu Description
The Main Menu and submenus of the U2000 are described as follows.
1.8.8 Operations Frequently-Performed on the User Interface
This topic describes the operations that are frequently performed on the U2000 user interface.
1.8.9 Custom View
In the U2000, different users have different network management scopes. The user can customise
a view for the network topologies and equipment under administration as a working interface.
The U2000 provides many view setting modes, including customizing views and setting to start
views. The custom view window displays the topological structure of the network, including
links, subnets or NEs. You can set a corresponding view according to requirements to facilitate
the management of network topologies.
1.8.1 Components of the Client GUI

This topic describes the components of the client GUI.
Figure 1-5 shows the client GUI.
Figure 1-5 Client GUI

1

1: Menu bar 2: Toolbar 3: Workbench list
4: Output pane 5: Status bar 6: Workbench
Menu Bar
The menu bar provides the entries to all the functions of the U2000 client. It consists of the
following menus: File, Edit, View, Fault, Performance, Configuration, Service, Inventory,
Administration, Window, and Help.
Toolbar
The toolbar provides the shortcut icons for major operation tasks. The shortcut icons are refer
to 1.8.4 Shortcut Icon.
Workbench list
You can create or modify a workbench through the shortcut icons.
Output Pane
The output pane displays the returned information and other relevant information.
Status Bar
The status bar displays the information such as the system status, the login users, and the IP
address of the connected server. The information displayed from left to right is as follows:
l Server: Displays the name and IP address used for logging in to the server.
l Login user: Displays the name of the login user.
l Connection duration: Displays the client time in real time.
l System pop-up pane: Display a message in real time when the operation on the client is
affected. It can be disable and enable.
l Login mode: Displays the login mode. It can be single-user mode and multi-user mode.
l Connection status: Displays the status of the connection between the client and the server.
l Logo: Displays the logo of Huawei Technologies Co., Ltd..
Workbench
The shortcut icons on the workbench help you perform operations.
1.8.2 Key GUI Components

The key U2000 GUI components are as follows:
Component Example
Button

Component Example
Shortcut icon
Radio button
Check box
Tab
Field
Drop-down
menu
Menu
Function Tree

Component Example
Dialog box
1.8.3 Frequently Used Buttons

The frequently used buttons on the U2000 GUI are as follows:
Button Functionality
Selects the objects.
Expands all available options.
Collapses all available options.
Displays or hides a dialog box.
Selects the objects.
Selects the objects as a batch.
Increases the priority of the selected object.
Decreases the priority of the selected object.
Displays a dialog box.

Queries results from the NE.
Imposes the current settings.
Displays the latest result(s).
Exports the selected scheduled tasks to the

browser of the operating system for printing.
Saves selected data to the specified file.
Makes the current setting effective and closes

the dialog box.
Cancels the current setting and closes the

dialog box.
Closes the operation wizard.
Allows the user to view and select the board

ports.
Deletes the selected data or icon.
Creates a new service, protection or physical

inventory information etc.
Proceeds to the next step.
Returns to the previous step.
Closes the dialog box.
Expands the Object Tree.
Collapses the Object Tree.
Makes the current setting effective and closes

the dialog box.
Cancels the current setting and closes the

dialog box.
Search the correlative information.

Sets the correlative condition.
1.8.4 Shortcut Icon

This topic describes the frequently used shortcut icons on the U2000 Client.
You can customize the toolbar so that only the frequently-used shortcut icons are displayed on
the toolbar. To customize the toolbar, right-click the toolbar and choose a menu item from the
shortcut menu.
Table 1-2 The shortcut icons on the Main Topology

Button Name Description
Workbench l Style of Favorites Folder: By

selecting Style of Favorites
Folder, you can modify or delete
the default workbench.
l Style of Desktop: By selecting
Style of Desktop, you can return
to the workbench.
Exit Exits the U2000 client.
Logout Logs out the current user.
Lock Terminal Locks the current client.
Full Screen Display the Main Topology in full

screen mode.
NMS User Manages the user information on the

Management U2000.
SDH Protection Displays the Protection Subnet

Subnet Maintenance Maintenance window.
SDH Trail Displays the SDH Trail

Management Management window.
SDH Trail Creation Displays the SDH Trail Creation

window.
WDM Trail Displays the WDM Trail

Management Management window.

Browse Current Displays the Filter dialog box. After

Alarm the filter criteria is set, displays the
Browse Current Alarm window.
Browse Alarm Logs Displays the Filter dialog box. After

the filter criteria is set, displays the
Browse Alarm Logs window.
Stop the Current Clicks this shortcut to stop the current

Alarm Sound alarm sound at the U2000 side. The
alarm sound starts again when the
new alarm happens. To permanently
stop the alarm sound, you can choose
Fault > Stop the Alarm Sound
Permanently from the main menu.
Main Topology Switches to the Main Topology.
NE Explorer Displays the window of NE

Explorer.
Create Fiber Creates fiber.
Browse SDH Displays the Browse SDH

Performance Performance window.
Browse WDM Displays the Browse WDM

Performance Performance window.
IPA Management Displays the presence of the IPA that

is in the disabled state. This icon
blinks if the disabled IPA exists.
When you click this icon, the IPA
Management window is displayed.
NM Tasks Displays the process of NM Tasks

Management management. When you click this
Progress icon, the NM Tasks Management
Progress window is displayed.

Networkwide Performs centralized monitoring over

Maintenance Status the maintenance and operation status
of the equipment managed by the
U2000, including:
l Loopback Status
l Laser Status
l Path Loading
l Alarm Suppression
l Alarm Loading
l Alarm Reversion
l DCC Enabling Status
Show alarm board Displays the Alarm Board dialog

box. By default, the statistics of all the
current alarms are displayed.
Critical Alarm Dynamically displays critical alarms.

When you click this icon, the
information of all the critical alarms
is displayed.
Major Alarm Dynamically displays major alarms.

information of all the major alarms is
displayed.
Minor Alarm Dynamically displays minor alarms.

information of all the minor alarms is
displayed.
Warning/Not Dynamically displays warnings/not

Alarmed Alarm alarmed. When you click this icon,
the information of all the warnings/
not alarmed is displayed.
No new events Dynamically displays abnormal

events. This icon indicates that there
are no newly reported events. When
you click this icon, the Query Event
Logs window is displayed.
New events Dynamically displays abnormal

events. This icon indicates that there
are newly reported events. When you
click this icon, the Query Event
Logs window is displayed.

New To create a custom view, subnet, NE,

and link.
NOTE
The NE cannot be created in the custom
view.
Back to Parent To return the parent interface.
Select To select a topology object.
Move Hand To move the topology view.
Search Displays the Search dialog box. You

can locate objects in the topology.
Print To print the topology view.
Print Preview To preview the print effect of the

topology view.
Overview To provide a general view of

topology.
NE Statistics To collect statistics on the NEs in the

current subnet, including the device
types and the number of devices.
Refresh Rreshes the current view after you

click the button when the data in the
view is changed.
Save Position To save the position information of

the topology objects in the current
Filter & Legend & To display the legend/filter/attribute

Attribute panel.
Alarm Browse To display the list of alarms.

Region
Layout To arrange the topology objects in the

topology view.
Zoom In Zooms in topology view.
Zoom Out Zooms out topology view.
Local Amplification To enlarge the selected area.
Lock View/Unlock Locks/Unlocks the current NE(s).

View

Ascending Lists the objects on the Object Tree

in an ascending order.
Descending Lists the objects on the Object Tree

in an descending order.
Table 1-3 The shortcut icons on the other GUI

Verify Policy Verifies the validity of a configuration

policy before the policy is deployed on
devices.
Deploy Policy Deploys a policy to the selected

devices or device groups.
Undeploy Policy Undeploys all the policies in the

current policy package from the
selected devices and clear the related
commands deployed on these devices.
Discover Policy Policy auditing is to audit the policy

configuration differences between the
NMS and device, so as to determine
whether the policy needs to be
deployed or discovered.
Audit Policy Policy discovery is to recover the data

synchronized to the database to the
NMS for management.
Save Saves a policy package.
View History Queries the history record of policy

Record deployment or undeployment
according to the device name, device
IP address, status, and operator.
Topology Views the navigation tree in the

Navigator Topology.
View Navigator Views the view navigation tree in the

Topology.
NE Time Synchronizes the NE time and NMS

Sychronization time.
Synchronize Synchronizes the current alarms of an

Current Alarms NE.

Browse Current Browses the current alarms of an NE.

ALarms
Clear ALarm Clears the current alarm indications of

Indication an NE.
Refresh NE Panel Refreshes the NE panel status to make

Status the NE panel display the latest data.
Back Up NE Backs up the NE data to the SCC.

Database To SCC
Display/Hide Displays or hides the extended slot on

Extended Slot the Extended Slot tab page.
Legend Displays a legend and its description.
Shrink all Shrinks Alarm/Event Name.
Classify by group id Classifies alarms by group ID.
Classify by severity Classifies alarms by severity.
Classify by type Classifies alarms by type.
Classify by Classifies alarms by category.

category
1.8.5 Common Shortcut Keys

This topic describes the common shortcut keys. Using shortcut keys, you can increase the
operation efficiency. The shortcut keys include Enter, Ctrl, Esc, and Tab.
Shortcut Key Description
F1 Opens the Help.
Enter Confirms the operation or moves downward to the next line. If the
cursor is on a button, pressing Enter means to confirm the operation.
If the cursor is in the list box, press Enter once and the cursor then
moves downward to the next line.
Esc Closes a dialog box.
Tab Switches between buttons if the cursor is on a button. Switch between

text boxes if the cursor is in the list box.
Ctrl+F Searches resources such as the NEs, subnets, cards, frames, interfaces,
and VLANs in basic and rapid modes by pressing Ctrl+F in all views.

Shortcut Key Description
Ctrl+A Selects all NEs or selects all contents in the list. If the cursor is in the
view, press Ctrl+A to select all NEs. If the cursor is in the list box,
press Ctrl+A to select all contents in the list.
Ctrl+C Quickly copies the table texts.
Ctrl+V Pastes the copied data to another text area.
Alt+F Opens the File menu from the Main Menu.
Alt+E Opens the Edit menu from the Main Menu.
Alt+V Opens the View menu from the Main Menu.
Alt+U Opens the Fault menu from the Main Menu.
Alt+P Opens the Performance menu from the Main Menu.
Alt+C Opens the Configuration menu from the Main Menu.
Alt+R Opens the Service menu from the Main Menu.
Alt+I Opens the Inventory menu from the Main Menu.
Alt+S Opens the Administration menu from the Main Menu.
Alt+W Opens the Window menu from the Main Menu.
Alt+H Opens the Help menu from the Main Menu.
1.8.6 Main Windows

This topic describes the main windows of the U2000 client. And tells you what you can do in
the windows.
1.8.6.1 Workbench
This topic describes the workbench. After a client is started, the system automatically accesses
the default workbench. The default shortcut icons are displayed on the workbench.
1.8.6.2 Main Topology
This topic describes the items in the Main Topology. All topology management functions can
be accessed through the Main Topology in U2000. These functions include creating topological
objects, subnets, searching for the existing equipment in the network. You can search, view,
create, set, and manage NEs and subnets; and search, create, configure, and maintain
management functions on trails.
1.8.6.3 NE Explorer
The NE Explorer is the main user interface used to manage equipment. In the NE Explorer, a
user can configure, manage and maintain the NE, boards, and ports on a per-NE basis. The NE
Explorer is the main user interface for commissioning and configuration on a per-NE basis. The
NE Explorer contains a Function Tree that makes the operations easy. To display the
configuration window for an object, the user can just select the object and then choose a desired
function in the Function Tree.

1.8.6.4 Clock View

The Clock View provides a visible platform to enable NE clock settings, query of network-wide
clock synchronization status, and clock tracing and search functions, supports the synchronous
Ethernet clock, 1588 clock, SDH clock, TOP clock, ACR clock, TDM clock, PON clock, and
E1 clock, and applies to the MSTP, RTN, NG WDM, PTN series NEs and the router NE40E
V3R7 NE.
1.8.6.5 NE Panel
The NE Panel displays boards and ports in different colors depending on their current status. In
the U2000, most operations such as equipment configuration, monitoring, and maintenance are
performed in the NE Panel window.
1.8.6.6 WDM NE Signal Flow Diagram
WDM NE signal flow diagram provides a signal flow diagram for the optical layer trails of each
WDM NE. The signal flow diagram is one of the views where you configure, monitor and
maintain the WDM equipment.
1.8.6.7 Browse Alarm
This topic describes the user interface for viewing the current and history alarms, Alarm Logs.
In this user interface, buttons are provided, such as Filter, Synchronize, Refresh, and
Acknowledge, to help you quickly locate the alarm cause.
1.8.6.8 Browse Event
In the Browse Event Logs window, you can view events at different levels. This window
provides buttons, such as Filter by Template, Filter and Refresh, to help you to quickly locate
the alarm cause.
1.8.6.9 Browse Performance Window
You can view the current and history performance data, UAT events and performance threshold
crossings.
1.8.6.1 Workbench
This topic describes the workbench. After a client is started, the system automatically accesses
the default workbench. The default shortcut icons are displayed on the workbench.
l In the main window of the U2000, click the drop-down button to the right of the icon
and then select Style of Desktop to access the workbench.
l You can do as follows to modify a workbench: On the left side of the Workbench, right-
click the icon of the workbench and choose Modify Workbench from the shortcut menu
to modify the name, description, icon or background of a workbench.
l You can do as follows to delete a workbench: On the left side of the Workbench, right-
click the icon of the workbench and choose Closed Workbench from the shortcut menu.
In the Confirm dialog box, click Yes.
l You can expand and order workbenches to separate the customized workbenches from the
default workbench.
l You can view the description about the function of the workbench in the background picture
of the workbench and press F1 to view the Help.
l NOTE
You must navigate to the Main Topology to make certain menu items available in the main menu.

1.8.6.2 Main Topology

Navigation Path
l In the Workbench Window, double-click the shortcut icon of Main Topology.
l Choose View > Main Topology from the main menu.
l If the preceding operation closes the Main Topology, you can click the shortcut button
to open the Main Topology.

NOTE
l The U2000 provides multiple display modes of the client. For example, you can set a particular mode
of displaying alarms of a particular object. For information about the meanings and setting methods of
display modes, see 1.10 Customizing the Client GUI Effect.
l The U2000 provides the focus display function. When the mouse cursor stays on a shortcut button for
about 2 seconds, the U2000 will provide a focus display, presenting its meaning.
l The U2000 provides a variety of view windows according to different functions, and the views can be
switched at will.
l In the Current View drop-down list, select Physical Root to display the Physical Root view.
l In the Current View drop-down list, select Clock View to display the Clock View.
l In the Current View drop-down list, select Tunnel View to display the Tunnel View.
l In the Current View drop-down list, select Custom View to display the custom view.
Figure 1-6 shows the Main Topology of the U2000.

Figure 1-6 Main Topology
1 2 3 4 5
12 11 10 9 8 7 6
1: Network management 2: Menu bar 3: Shortcut icon

system name You can operate the NM and Click the icon, you can
the NE with submenu bar, perform a simple task
include configure tasks, quickly. For example: exit
manage tasks and so on. NM, lock terminal, log out,
NMS user management, stop
the current alarm sound,
1.8.6.3 NE Explorer, 1.8.6.7
Browse Alarm, 1.8.6.9
Browse Performance
Window, 5.8 Creating
Connections.

4: Shortcut icon 5: Alarm button bar 6: Filter Tree and Legend

Click the icon, you can The Alarm buttons for In this area, you can set the
perform a simple task quickly alarms at different severity display types of the objects in
on the Main Topology. For levels are in different colors. a view, and view the
example: zoom in or zoom You can click the button to descriptions of legends in the
out or refresh or save the view the number of the view. To locate an operation
view, show or hide the uncleared alarms generated object quickly, refer to
navigators, search objects, on the current U2000. You 1.8.8.1 Filtering Operation
see object attributes, lock or can click the button to view Objects in a View.
unlock the view. current alarms. For example:
7.6.4 Browsing the Current
Alarm, show alarm panel.
When the U2000 has
abnormal events, the
Abnormal event indicator
turn to red from green. You
can click the indicator to
view current abnormal
events.
7: Displays the client time in 8: Views user name of the 9: Views the name which is
real time. logged-in U2000 user set by the current U2000
currently. client, and views the IP
address of the current
U2000 server.
10: Physical Map 11: Display the mouse 12: Views the current
Views the managed coordinate on the Main location of the cursor in the
equipment. Topology currently. Main Topology.
On the Physics Map, you can
perform operations, such as
5.5 Creating NEs, 5.13
Deleting Topology Objects,
1.8.6.3 NE Explorer, 5.8
Creating Connections, 5.9
Browsing Fibers/Cables,
5.6 Configuring the NE
Data, 1.8.6.9 Browse
Performance Window,
Alarm, 1.20 Collecting NE
Data and so on.
1.8.6.3 NE Explorer
The NE Explorer is the main user interface used to manage equipment. In the NE Explorer, a
user can configure, manage and maintain the NE, boards, and ports on a per-NE basis. The NE
Explorer is the main user interface for commissioning and configuration on a per-NE basis. The
NE Explorer contains a Function Tree that makes the operations easy. To display the
configuration window for an object, the user can just select the object and then choose a desired
function in the Function Tree.

NOTE
l For the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, you can open a maximum of five
NE Explorer windows at the same time.
l Currently, the OptiX OSN 6800, OptiX OSN 8800 T32, OptiX OSN 8800 T64, OptiX OSN 6800A,
OptiX OSN 8800 T32(NA), OptiX OSN 8800 T64(NA) NEs can be managed individually as an NE,
and can also be managed in an optical NE.
Navigation Path
l Double-click an NE on the Main Topology. Or right-click an NE on the Main Topology
and choose NE Explorer from the shortcut menu.
l In the left-hand pane of the Main Topology, double-click an NE. Or right-click an NE and
choose NE Explorer from the shortcut menu.
l Double-click an optical NE on the Main Topology. In the displayed window, right-click
an NE in the left-hand pane and choose NE Explorer from the shortcut menu.
Correlation operation
l Click the in NE Explorer window, display the 1.8.6.5 NE Panel.
l Click the in NE Explorer window, switch to other NE.
1.8.6.4 Clock View

The Clock View provides a visible platform to enable NE clock settings, query of network-wide
clock synchronization status, and clock tracing and search functions, supports the synchronous
Ethernet clock, 1588 clock, SDH clock, TOP clock, ACR clock, TDM clock, PON clock, and
E1 clock, and applies to the MSTP, RTN, NG WDM, PTN series NEs and the router NE40E
V3R7 NE.
GUI
Open the Clock View. In the Main Topology window, select Clock View from the Current
View drop-down list. Select the NE to be queried or configured from the Object Tree. Figure
1-7 shows the Clock View.

Figure 1-7 Clock View
Legends
l By choosing View > Display Setting > Legend from the main menu, you can learn
meanings of various legends in different colors in the Clock View.
l By choosing View > Display Setting > Filter from the main menu, you can display the
required elements in the Clock View based on the filter function.
l The Clock View uses continuous lines to represent the tracing relationships between NEs.
Smaller number indicates higher priority. The number displayed on the continuous line
indicates the priority of the traceable clock. The Clock View displays the line clock source
numbers only. Internal and tributary clock sources are also numbered, but they are not
displayed in the Clock View.
l The arrow direction in the Clock View indicates the clock tracing direction. For example,
if NE(9-3513) points to NE(9-3514), it indicates that NE(9-3514) traces the clock
information transmitted from NE(9-3513).
l When you place the cursor on a port icon, for example, the in Figure 1-7, the ID of
the optical port on the card of the NE for connection to another NE are displayed
automatically.
l The arrow direction in the Clock View indicates the clock tracing direction.
l An internal clock source is the clock provided by an NE, and has no tracing relationships
with other NEs. Therefore, internal clock sources are not displayed on the Clock View.
l Tributary clock sources have no relation with the clock sources that are not provided by
the U2000. Therefore, the clock tracing relationships are not displayed in the Clock View.

l In the Clock View, you can select multiple NEs, right-click, and query the clock
synchronization status or search for clock tracing relations.
NOTE
The rule of verifying an invalid clock tracing relation is as follows: First, verify whether a clock source is in the
SSM protocol mode. In the non-SSM protocol mode, verify the status of a clock source. The status directly
determines whether a clock tracing relation is invalid. In the SSM protocol mode, verify the status of a clock
source. If the status is unavailable, it indicates that the clock tracing relation is invalid. If the status is available,
you also need to verify the S1 byte (clock quality). When you manually cancel settings of the quality of the S1
byte and the quality of the S1 byte is unknown, the clock tracing relation is invalid.
Relevant Operations
In the Clock View, you can query and configure NE clocks network-wide. For details on the
clock operations, see Table 1-4.
Table 1-4 Querying and configuring clocks network-wide
Operation Navigation Path Description
Querying clock topology Clock View In the clock topology, you

can learn directly the clock
NEs, clock tracing relations,
and clock synchronization
status.
Clock NEs are discovered
automatically by the U2000,
which does not require the
manual search.
Creating a virtual clock In the Clock View, right- You can create a virtual clock
device click and choose Create device to identify a device
Virtual Clock Device from that is outside the managed
the shortcut menu. domain.
A virtual clock device
represents a clock device that
exits in the network but not
within the local managed
domain. Generally, virtual
clock devices are relevant to
NEs in the local managed
domain in terms of tracing
relationships. In this case,
you need to create virtual
clock links on the U2000 to
view and identify the clock
tracing relationships between
NEs easily.
Creating a virtual clock link In the Clock View, right- You can create a virtual clock
click and choose Create link to identify the tracing
Virtual Clock Link from the relationships between a local
shortcut menu. NE and a device that is
outside the managed domain.

Operation Navigation Path Description
Searching for clock links In the Clock View, right- You can search for clock
click and choose Search links of NEs network-wide to
Clock Link from the shortcut learn the clock tracing
menu. relationships between NEs.
In this function, you can
specify the search scope
based on the NE or clock link
types.
When the NE traced clock
source has changed, you need
to re-search for the clock
trace relation.
Configuring clocks Right-click an NE and In the NE Explorer, you can

choose Configure Clock configure NE clocks on the
from the shortcut menu. GUI for configuring clocks.
The NE clocks can be the
IEEE 1588 clock, SDH
clock, synchronous Ethernet
clock, and PON clock, but
different clocks are
supported by different NEs.
Switching between clock Right-click the required By switching between clock

links clock link and choose Switch links, you can change the
to this Clock Link from the current clock tracing
shortcut menu. relationships between NEs.
Relevant Concepts
Clock link: A clock link represents the clock tracing relationships between clock NEs. For
example, a clock link from NE A to NE B represents that NE B follows the clock signal from
NE A.
1.8.6.5 NE Panel
The NE Panel displays boards and ports in different colors depending on their current status. In
the U2000, most operations such as equipment configuration, monitoring, and maintenance are
performed in the NE Panel window.
GUI
Double-click an NE on the Main Topology to display the NE Panel.

NOTE
l Choose the Always On Top for the Slot Layout window to always remain on top. Applies to the
MSTP, WDM, NA WDM, PTN, RTN, Marine NEs.
l When a board occupies multiple slots, the slot ID of the main slot is displayed in boldface, and the slot
ID of the slave slot is grayed out.
l In the NE panel, when you click the processing board that is accompanied by an interface board, the
slot ID of this interface board is displayed in orange.
Click the icon on the toolbar, to view the legends of the boards and ports on the right of the
Slot Layout.
To select an operation related to an installed board, right-click the installed board and choose it
from the shortcut menu. For example, right-click an AUX board and choose Path View to display
the detailed path information.
1.8.6.6 WDM NE Signal Flow Diagram

WDM NE signal flow diagram provides a signal flow diagram for the optical layer trails of each
WDM NE. The signal flow diagram is one of the views where you configure, monitor and
maintain the WDM equipment.
GUI
NOTE
l As in the NE Panel, you can perform operations on each board such as viewing alarms, viewing WDM
performance data, querying versions, and configuring a WDM NE in the signal flow diagram rather
than the NE Panel. More importantly, the signal flow diagram provides the relation of fiber connections
between each board of the ONE. It visually shows the direction of traffic, improving the U2000's ability
to maintain ONEs.
l In the signal flow diagram, you can also create a fiber connection, query information about wavelength
and port of each board, and rotate a board icon 90, 180 or 270 degrees. You can divide the same boards
into a group, and print the signal flow diagram and so on. The smallest unit of the signal flow diagram
is a board. Boards of different type have different icons. See legends for more information.
l Signal flow diagram is not applied to idle resource optical NE.
Navigation Path
l Double-click an optical NE on the Main Topology. In the displayed window, select an NE
and click Signal Flow Diagram. SeeFigure 1-8.
l Right-click an NE on the Main Topology. In the displayed window, select an NE and click
Signal Flow Diagram. SeeFigure 1-8.

Figure 1-8 Signal flow diagram
1.8.6.7 Browse Alarm

This topic describes the user interface for viewing the current and history alarms, Alarm Logs.
In this user interface, buttons are provided, such as Filter, Synchronize, Refresh, and
Acknowledge, to help you quickly locate the alarm cause.
Background Information
l The current alarm represents the merged alarm logs. The alarm merging rule is that alarm
logs with the same alarm ID, alarm location information, and alarm source are merged into
one record in the current alarm.
l Alarm log records all the alarms received by U2000. In the alarm log, each alarm is
displayed as a record.
l For a newly reported alarm log, if the current alarm contains the record that meets the alarm
merging rule, the alarm log is merged into the previous record in the current alarm regardless
of the acknowledgement and clearance state of the record. After merging, the frequency of
the record is added by 1. The displayed acknowledgement and clearance state of the record
is subject to that of the latest alarm log.
l You can query details of every alarm in the alarm log browsing window.
l Acknowledged and cleared alarms become history alarms after you set the lifecycle. All
non-history alarms are called current alarms. For details on how to set the lifecycle, see
7.10.8 Setting the Lifecycle of the Current Alarm.

GUI
l Choose Fault > Browse Current Alarm from the main menu.
l Choose Fault > Browse History Alarm from the main menu.
l Choose Fault > Browse Alarm Logs from the main menu.
Figure 1-9 shows the alarm window.
Figure 1-9 Browsing alarms
1.8.6.8 Browse Event

In the Browse Event Logs window, you can view events at different levels. This window
provides buttons, such as Filter by Template, Filter and Refresh, to help you to quickly locate
the alarm cause.
GUI
Choose Fault > Browse Event Logs from the main menu.
Figure 1-10 shows the window of Event.

Figure 1-10 Browse Event Logs
1.8.6.9 Browse Performance Window

You can view the current and history performance data, UAT events and performance threshold
crossings.
GUI
Choose Performance > Browse SDH Performance from the main menu.
Choose Performance > Browse WDM Performance from the main menu.
Choose Performance > Browse NA WDM Performance from the main menu.
Choose Performance > Browse Control Plane Performance from the main menu.
Figure 1-11 shows the window of SDH performance.
Figure 1-12 shows the window of WDM performance.
Figure 1-13 shows the window of NA WDM performance.
Figure 1-14 shows the window of control plane performance.

Figure 1-11 Browse SDH Performance
Figure 1-12 Browse WDM Performance

Figure 1-13 Browse NA WDM Performance
Figure 1-14 Browse Control Plane Performance
1.8.7 Menu Description

The Main Menu and submenus of the U2000 are described as follows.

1.8.7.1 File Menu

This topic describes the options on the File menu.
1.8.7.2 Edit Menu
This topic describes the options on the Edit menu.
1.8.7.3 View Menu
This topic describes the options on the View menu.
1.8.7.4 Fault Menu
This topic describes the options on the Fault menu.
1.8.7.5 Performance Menu
This topic describes the options on the Performance menu.
1.8.7.6 Configuration Menu
This topic describes the options on the Configuration menu. The Configuration menu allows
you to configure and manage the network.
1.8.7.7 Service Menu
This topic describes the options on the Service menu.
1.8.7.8 Inventory Menu
This topic describes the options on the Inventory menu.
1.8.7.9 Administration Menu
This topic describes the options on the Administration menu.
1.8.7.10 Window Menu
This topic describes the options on the Window menu.
1.8.7.11 Help Menu
This topic describes the Help menu. The Help menu allows you to view the online Help topics,
the version and registration information about the U2000. TheHelp menu also allows you to
change a license.
1.8.7.1 File Menu

This topic describes the options on the File menu.
Menu Description
Option Description
Create NE Accesses the Create NE dialog box on which you can

create NEs and U2000.
Link Accesses the Create Link dialog box on which you can
create links.
Discovery NE Enables the subnet to search for the NEs in the specified
IP address and add the results to the topology view
automatically.
Time Discovery Sets the time to search for the NEs.
Fiber Searches and creates fiber.

Option Description
Link Searches and creates Link.
NE Auto Searches and creates NE.

Discovery
Batch Import NE Batch Import NEs to the NMS.
Find Searches objects such as the NEs, links, and cards by

specifying the search condition.
Preferences Sets the tile of the client main window, output window,
auto-locking, time format, date format, and view
effects.
Customize Toolbar Moves the icons of the commonly used tools to the
toolbar by customizing the toolbar function.
Workbench Accesses the Workbench window.
Print Preview Previews the topology view before printing it.
Print Prints the topology view on a paper.
Page Setup Sets the print attributes.
Lock Terminal Locks the U2000 client manually.
Change Password Enables you to change the password of the current user.
Log Out Enables you to log out the current U2000 client and
return to the user login interface.
Switch Login Server Logs in to the other server while you do not exit the
current U2000 client.
Exit Enables you to exit the U2000 client.
1.8.7.2 Edit Menu

This topic describes the options on the Edit menu.
Menu Description
Option Description
Cut Cuts an NE or more and the related fiber

cables.
Copy Copies an NE or more and the related fiber

cables.
Paste Pastes the contents that are cut or copied.

Option Description
Copy to Copies the selected contents to the specified

path.
Move to Moves the selected contents to the specified

path.
Select All Selects all the NEs in the current window.
Delete Deletes all the NEs in the current window.
1.8.7.3 View Menu

This topic describes the options on the View menu.
Menu Description
Option Description
Main Topology Access the Main Topology.
Creating Subnet Accesses the Create Physical Subnet dialog box on

which you can create subnets.
View Accesses the Create Custom View dialog box on

which you can create views.
Modify Custom View Modifies the custom view.

The Modify Custom View menu is displayed only
after you navigate to the customer view.
Delete Custom View Deletes the custom view.

The Delete Custom View menu is displayed only after
you navigate to the customer view.
Refresh Refreshes the current view.
Display Topology Navigator Opens or closes the topology navigation tree.

Setting
Legend Opens or closes the legend panel.
Filter Opens or closes the Filter panel.
Attribute Opens or closes the Attribute panel.
Aerial View Accesses the Overview window to view the entire

network.
NE Statistics Accesses the NE Statistics window to view the

statistics of the U2000 and NE.
Current Alarm Opens or closes the Browse Current Alarm window.
Lock Locks the location of an object in the view.

Option Description
Set Startup Subnet Sets the current subnet as the startup subnet.
Layout Lays out the current subnet in the mode selected.
Set Background Sets the background for the current subnet.
Up Enables you to return to the parent subnet of the current

subnet.
To Top Enables you to return to the topmost subnet, which is

the root.
Zoom Zoom out Zooms out the current subnet.
Zoom in Zooms in the current subnet.
Zoom in Partially Enables you to enlarge a selected area of the subnet.
Fit Window Adjusts the subnet to fit the window.
Restore Enables you to restore the subnet to the 1:1 proportion.
Save Picture Saves the specified pictures.
Save Position Saves the icon position in the main topology.
1.8.7.4 Fault Menu

This topic describes the options on the Fault menu.
Menu Description
Option Function
Browse Current Alarm Sets the filter criteria to browse the current alarms.
Browse History Alarm Sets the filter conditions to browse the history
alarms.
Browse Alarm Logs Sets the filter conditions to browse the alarm logs.
Browse Event Logs Sets the filter criteria to browse the events logs.
Browse Current Alarm By Status Queries the current alarms according to the alarm
status.
Browse Current Alarm By Severity Queries the current alarms according to the alarm
severity.
Alarm Bar Chart Views alarms in a bar chart.
Display Alarm Board Views all alarm statistics.
Download Remote Notification Logs Download remote notification logs.

Option Function
Query Alarm Log Statistics Collects statistics by specifying statistic conditions.
Query Event Log Statistics Collects statistics by specifying statistic conditions.
Synchronize Networkwide Alarms Synchronizing the networkwide alarms.
Synchronize Alarm Box Synchronizing the alarm box.
Correlation Analyze Trail Analyses the trail alarm based on the alarm
Analysis Alarm Correlation correlation analysis rule
Trail Alarm Sets the trail alarm correlation rule.

Correlation Rules
Fiber Relating Views the alarms related to the fiber.

Alarm
Settings Options Configures the information related to Alarm Box,

Alarm Lifecycle, Auto Acknowledge, and Auto
Synchronize.
Object Group Manages the object groups.

Management
Alarm/Event Name Manages the groups according to the alarm/event

Group Management name.
Template Manages the templates of alarms and events.

Management
Alarm Wavelength Customizes alarm wavelength information and

Info Template applies the template to NEs.
Fault Diagnosis Sets the rules for fault diagnosis.

Rules
NE Alarm/Event Configures the alarms and events of NEs.

Config
Mask Ne Interface Configuring to mask the interface alarm of NEs.

Alarm
Remote Sets the remote notification rules of alarms and

Notification events.
Redefine Sets the rules for redefining alarms and events.
Correlation Sets the correlation rules of alarms and events.
Postprocessing Sets the postprocessing rules of alarms and events.
Mask Rule Sets the rules for shielding alarms and events. The
alarms and events that meet the conditions are
shielded.

Option Function
Experience Views the common diagnosis rules of faults. You

can customize the diagnosis rules including the
alarm cause, diagnosis method, and processing
method.
Set Events as Sets events as ADMC alarms. During the

ADMC Alarms maintenance of the U2000, if you need to view a
certain type of events, you can switch events to
ADMC alarms.
Stop the Alarm Sound Permanently Sets the alarm board not to play the alarm sound
permanently.
Stop the Current Alarm Sound Stops the current alarm sound of the alarm board.
The alarm sound is played when a new alarm is
reported.
Router/Switch Test Sets the parameters of the Router/Switch test.
Test Suite Provides the information about the service test suite.
Start OAMS Starts OAMS.
Access Service Diagnosis Provides the information about the Access service
diagnosis.
FTTx Fault Diagnosis Provides the fault diagnosis information about the
FTTx.
Access Subscriber Test Provides the Access subscriber test results.
Query PVC Route Queries the PVC route information.
MAC Location Provides the MAC address location results.
Service Service Monitoring Monitoring the service with the template.

Monitoring Template
Real-time Faulty Real-time management for the faulty trail of SDH

SDH Trail NE.
Management
Real-time Faulty Real-time management for the faulty trail of WDM

WDM Trail NE.
Management
Real-time Faulty Real-time management for the faulty trail of MSTP

MSTP Ethernet ethernet NE.
Trail Management
Access Start Environment Start U2000 Environment Power Monitoring

Environment Power Monitoring
Monitoring
Configure Configure U2000 Environment Power Monitoring
Environment Power
Monitoring

Option Function
Dump History Data Specifies the dump history data of dump options.
Add PSE Add U2000 PSE power supply.
Delete PSE Delete U2000 PSE power supply.
Configuration Maintenance Sets maintenance parameters to manage NEs.
1.8.7.5 Performance Menu

This topic describes the options on the Performance menu.
Menu Description
Option Description
Browse History Performance Queries, compares, views, and saves the performance
Data data of resources.
Browse SDH Performance Queries or sets the current performance data and history
performance data for a SDH NE, a board or a port.
Browse WDM Performance Queries or sets the current performance data and history
performance data for a WDM NE, a board or a port.
Browse Control Plane Queries or sets the current performance data, history
Performance performance data, and threshold-crossing records of the
NEs on the control plane.
Browse NA WDM Performance Queries or sets the current performance data and history
performance data for a NA WDM NE, a board or a port.
Browse Top N Query Queries or sets the data and status of Top N performance.
Performance Data
Query Top N Faulty Resource Queries Top N faulty resource.
Analysis History Performance Sets the monitoring filter criteria, such as the monitor
Data period, time range and data source of the performance
time so that the U2000 can analyze the history
performance data of the monitored object.
Medium-Term and Long-Term Sets different forecast conditions by which the U2000 can
Performance Forecast forecast the medium-term and long-term performance
data. The U2000 can forecast the bias current, output
optical power, and input optical power according to time,
and forecast time according to the bias current, output
optical power, and input optical power.
Performance Monitoring Monitors performance data for specific indicators.

Management

Option Description
Performance Schedule Policy Sets the time segments and repeat period at which the data
management needs to be collected. The schedule policy can be applied
on the resources while creating or modifying a monitoring
instance.
Performa Data Monitor Sets the performance data monitor template.

nce Template
Template
Managem TCA Monitor Sets the TCA monitor template.
ent Template
Performance Sets the performance threshold template.

Threshold Template
Performance Event Sets the performance event monitor status template.

Monitor Status
Template
Set NE Performance Monitoring Set NE performance monitoring time.

Time
Set RMON Customer Period Set RMON customer period.
Monitor Group Performance Monitoring group performance data.
Deploy Collector Browses the collector load status.
Performa Automatic Dump Dumps the performance data automatic.

nce Dump Setting
Managem
ent Manual Dump Dumps the performance data manual.
Performance Data
1.8.7.6 Configuration Menu

This topic describes the options on the Configuration menu. The Configuration menu allows
you to configure and manage the network.
Menu Description
Option Description
Node Redundancy E-Trunk Queries the information about the E-Trunk NE

Management group.
Synchronize NE Data Enables you to keep the NE data synchronous.
NE Configuration Data Management Displays the NE configuration data, and

enables you to perform operations to ensure that
the NE configuration data on the U2000 is
consistent with that on the NEs.

Option Description
PTN Qos Profile V-UNI Ingress Manages V-UNI Ingress Profile.

Profile
V-UNI Egress Manages V-UNI Egress Profile.

Profile
PW Profile Manages PW Profile.
ATM Profile Manages ATM Profile.
Car Profile Manages Car Profile.
DS Profile Manages DS Profile.
ATM Cos Mapping Manages ATM Cos Mapping Profile.

Profile
Port Profile Manages PORT Profile.
Wfq Profile Manages WFQ Profile.
Port WRED Profile Manages PORT WRED Profile.
Service WRED Manages SERVICE WRED Profile.

Profile
Cos Queue Manages Cos Queue Mapping Profile.

Mapping Profile
IP QoS Profile CBQoS Profile Lists the names, aliases, and statistics of
CBQoS and whether the sharing mode is
enabled.
DS Domain Profile Lists the names of aliases of DS domains.
HQoS Profile Lists the names and aliases of HQoS and

whether the HQoS is used in a VPN.
Port Queue Profile Lists the names and aliases of the port queue.
Interface CAR Lists the names and aliases of the interface

Profile CAR, and the related information about CIR
and PIR.
Access QoS Profile Lists the names of aliases of the access QoS.
NE Batch NE Time Enables you to keep the NE time synchronous

Configuration Synchronization with the U2000 server time or the system time
of the network time protocol (NTP).
Alarm Reversion Set NE alarm reversion mode.

Mode
NE Charset Sets or modifies the NE character set.

Management

Option Description
NE Time Enables you to query or modify the NE time

Localization zone and set the daylight saving time.
Management
Batch Clock Enables you to query the clock synchronization

Operation status, set the clock source reversion parameter,
and set the NE clock quality.
Power Management Queries the power consumption of a board.

Sets the power consumption threshold and
queries the power consumption of an NE.
NE Reporting Manage the NE reporting status.

Status Management
Automatic Enables you to set whether to automatically

Disabling of NE disable the NE maintenance functions and set
Function the automatic disabling time.
IP Network ACL Manages the IP Network ACL.
Port IP Address Management Manages the IP address of the port.
Optical Power Management Enables you to query the board optical power
and save the input power reference value and
the networkwide reference value.
WDM ALC Management Enables you to manage the WDM ALC link.
For example, you can enable and disable the
ALC, set the working band of an ALC link and
set the working mode of the nodes on an ALC
link.
WDM Fiber Link Detection Enables you to configure the WDM fiber link.
For example, you can create and query the links
or link groups, set the timing period, enable
automatic link reporting, set the link group
status, and adjust the optical power of a link.
MSTP QoS Template Adds, deletes, modifies, or queries the rules in

the MSTP QoS template.
SDH Network Expansion Wizard Guides you to complete the smooth SDH
network expansion and improvement. For
example, it guides you to change boards, insert
node on fiber, add extended shelf, upgrade link
capacity and reduce nodes for expansion.

Option Description
Access Profile Management Queries and sets the access profile. Include
ADSL Profile, NGADSL Profile, VDSL
Profile, VDSL2 Profile, G.SHDSL Profile,
TR165 DSL Profile, GPON Profile, EPON
Profile, Service Provisioning Profile, MDU
SNMP Profile, Optical Alarm Profile, IGMP
Profile, Traffic Profile, MGC Profile,
Impedance Profile, VLAN CAR Profile, TID
Profile, UAS Profile, Profile Set, VLAN Group
Profile, VLAN Service Profile, ONT VAS
Profile, WRED Profile, System Parameter
Profile, Generate System Parameters Profile,
Local Digital Map Profile and GCTL
Management.
Access Service Management Queries and sets the access service. Include
Ethernet Port, ADSL Port, VDSL2 Port, ATM
G.SHDSL Port, TDM G.SHDSL Port, EPON
UNI Port, EPON ONU, GPON UNI Port,
GPON ONU, TDM STM-1, TDM E1/T1, CES
E1/T1, IMA E1/T1, E3/T3, HSL V.35, POTS,
PWE3, PVC, Service Port, VLAN, MultiCast
User and Dual Homing.
FTTx Service Pre-Deployment Guides you to complete the FTTx service

predeploy policy. Include Configuration Script
Management, Import Network Deployment
Sheets, Import Configuration Script Sheet,
EPON MDU Batch Bind MAC, GPON MDU
Batch Bind SN, MDU Remote Acceptance
Sheet, Create Task, View Results.
Router/Switch/Security Configuration Guides you to complete the Router/Switch/

Security batch configuration. Include Batch
Deploy Switches, Batch Deploy Switches/
Security, Switch EPON Template, Smart
Configuration Tool.
Network Security Queries and sets the network security. Include

Policy Management, View History Record.
SDH ASON Applies ASON management on SDH NEs,

including ASON Topology Management,
Control Link Management, Component Link
Management, TE Link Management, ASON
Trail Management, Link Timeslot
Management, UNI Trail Management, ASON
Clock Subnet Management, Recover ASON
NE, and SRG Management.

Option Description
WDM ASON Applies ASON management on WDM NEs,

including ASON Topology Management,
Control Link Management, TE Link
Management, and ASON Trail Management.
IP Multicast Profile Queries and sets IP multicast templates,

including L2 CAC Profile and L2 static
multicast Profile.
Switch QoS Profile Switch CBQoS Lists the information about Policy Profile,
Profile Classifier Profile, and Behavior Profile.
Switch Port Queue Lists the names and aliases of the switch queue
Profile templates.
WLAN and Home Network View Manages the WLAN equipment and TR069
terminals that are controlled in a centralized
manner.
WLAN/CPE AC/AP Service Manages the template for the provisioning of

Template and Provisioning AC/AP services. You can view, add, delete, and
Configuration Template duplicate such a template and deliver AC/AP
services.
CWMP Service Manages the template for the provisioning of

Provisioning CWMP services. You can view, add, modify,
Template delete, and duplicate such a template.
QOS Template Manages WMM and traffic templates. You can

view, add, modify, delete, and duplicate such a
QoS template.
RF Template Manages RF templates. You can view, add,

modify, delete, and duplicate such an RF
template.
Security Template Manages security templates. You can view,

add, modify, delete, and duplicate such a
security template.
ESS Template Manages ESS templates. You can view, add,

modify, delete, and duplicate such an ESS
template.
AP Type Manages AP types. You can view, add, modify,

delete, and duplicate an AP type.
AP Template Manages AP templates. You can view, add,

modify, delete, and duplicate such an AP
template.
AP Upgrade Manages AP upgrade templates and upgrades

Template APs. You can view, add, modify, delete, and
duplicate such an AP upgrade template.

Option Description
AC/AP Device Configures the configuration policy and polling

Global policy for the AC/AP.
Configuration
Policy
1.8.7.7 Service Menu

This topic describes the options on the Service menu.
Menu Description
Option Description
Service Template Lists the service name, service type, creation time,
and modification time of the service template. You
can create a L3VPN service template, VPLS service
template, PWE3 service template, and RSVP-TE
tunnel service template.
Service Resource Common Lists the resource type, resource value, and service
Resource number of common resources.
Management
SAI Lists the interface resource bound to a service.
Customer Management Lists the information related to customers, such as

the customer name, phone number, email, and
address.
Customer Authorize Sets the operation rights of users.
SDH Protection Subnet Enables you to create, search for, and manage SDH
protection subnets.
SDH Trail Enables you to create, search for, and manage the
SDH trail.
MSTP Trail Enables you to create, search for, and manage the
MSTP trail.
WDM Trail Enables you to create, search for, and manage the
WDM trail.
WDM Protection Subnet Enables you to search for, and manage WDM
protection subnets.
RTN Protection Subnet Enables you to create RTN protection subnets.
Security VPN Service Enables you to create and manage security VPN
Service Management services.

Option Description
Discover Enables you to discover security VPN services.

Security VPN
Service
Search for IP Service Searches NEs according to the protocol type or

signalling type.
L3VPN Service Create L3VPN Provides the settings for the creation of a VPN
Service service based on the BGP/MPLS protocol. The
settings include the service name, customer name,
network type, and template.
Manage Lists the information related to the VPN service

L3VPN based on the BGP/MPLS protocol.
Service
Manage VRF Lists the information related to the VRF resource.

Resource
Manage Authorizes users to manage the BGP/MPLS VPN

L3VPN service.
Service
Authority
VPLS Service Create VPLS Provides the settings for the creation of a VPN
Service service based on the VPLS protocol. The settings
include the service name, service description,
customer name, service type, and customized
attribute.
Manage VPLS Lists the information related to the VPN service

Service based on the VPLS protocol.
Manage VSI Lists the information related to the VSI resource.

Resource
Manage VPLS Authorizes users to manage the VPLS service.

Service
Authority
E-AGGR Service Create E- Provides the information related to the creation of a

AGGR Service VPN service based on the E-AGGR protocol. The
information includes the attribute, value, and node
settings.
Manage E- Lists the information related to the VPN service

AGGR Service based on the E-AGGR protocol. The information
includes the service ID, service name, service type,
and deployment status.

Option Description
Manage E- Lists the information related to the VPN discrete

AGGR service based on the E-AGGR protocol. The
Discrete information includes the related node, service type,
Service cause of discrete service, lack of source LSR ID, and
lack of sink LSR ID, etc.
Manage E- Authorizes users to manage the E-AGGR service.

AGGR Service
Authority
PWE3 Service Create PWE3 Provides the information related to the creation of a
Service VPN service based on the PWE3 protocol. The
information includes the attribute, value, and node
settings.
Manage PWE3 Lists the information related to the VPN service

Service based on the PWE3 protocol. The information
includes the service ID, service name, service type,
and deployment status.
Manage PWE3 Lists the information related to the VPN discrete

Discrete service based on the PWE3 protocol. The
Service information includes the related node, service type,
cause of discrete service, lack of source LSR ID, and
lack of sink LSR ID, etc.
Manage PWE3 Authorizes users to manage the PWE3 service.

Service
Authority
Create Tunnel Provides the settings for the creation of a tunnel. The
settings include the tunnel name, protocol type,
signaling type, and template, etc.
Manage Lists the tunnel information, which includes the

Tunnel tunnel name, tunnel ID, and deployment status, etc.
Manage Lists the information about a discrete tunnel, which

Discrete includes the related node, protocol type, and
Tunnel signaling type, etc.
Batch Create Creates tunnels in batches. The related settings

Tunnel include the tunnel name, signaling type, and protocol
type, etc.
Manage LDP Lists the information related to an LDP session. The

Session information includes the local equipment, local LSR
ID, local role, peer equipment, and peer LSR ID.
Manage Lists the information related to the protection group.

Protection The information includes the group name, source
Group node, sink node, and protection type.

Option Description
Create Provides the settings for the creation of a protection

Protection group. The settings include the group name, group
Group ID, and protection type.
Search for Performs the automatic search for the protection

Protection group.
Group
Composite Service Create Creates the Composite Service. The related

Composite information includes service name, service
Service component and connection point, etc.
Manage Lists the information about a composite service. The

Composite information includes the service name, deployment
Service status, and running status.
Search for Searches for the composite service according to the

Composite protocol type.
Service
1.8.7.8 Inventory Menu

This topic describes the options on the Inventory menu.
Menu Description
Option Description
Physical Inventory Displays the information of telecommunication

rooms, racks, NEs, shelves, boards, subboards,
ports, ONU, slot information report, slot used
statistics, and SFP information report.
Fiber/Cable Fiber/Cable Enables you to create, query, modify and manage

Management fibers/cables.
Fiber/Cable Pipe Enables you to create, query, modify and manage

Management fibers/cables pipe.
WDM Fiber/Cable Searches and synchronizes the WDM fibers/

Synchronization cables.
Link Management Enables you to create, query, and modify links.
LinkGroup Management Enables you to manage links as link groups.
Router/Switch Interface Provides the information about the interfaces of

Router/Switch NEs.
SDH Report Port Resource Report Provides the information of ports on all cards of
the selected NE.

Option Description
Statistics Report of Displays the SDH tributary port information,

SDH Tributary Port such as Total Ports, Configured Port, and Used
Resources Port.
Lower Order Cross- Displays the capacity of lower order cross-

Connections Statistic connections, available lower order cross-
Report connections on each NE, and specifies thresholds
of lower order cross-connection alerts.
SDH Fiber/Microwave Provides the information of fiber name, level,

Link Resource Usage source NE, source card, source port, sink NE, sink
Report card, sink port, direction.
Statistics Report of Displays the trail information between SDH NEs.

Trails Between SDH
NEs
Statistics Report of Displays the information of SDH protection

SDH Protection Subnet subnet resources.
Resources
Statistics Report of Displays the information of SDH circuit

SDH Circuit Resources resources.
Microwave Microwave Link Collects the statistics on microwave link

Report Report information.
Microwave License Collects the statistics on microwave license

Capacity Report capacity information.
MSTP Statistics Report of Displays the port resources of the Ethernet card
Ethernet Ethernet Port of the NE that is selected, such as NE Name,
Report Resources Board Name, Used MAC Port, and Unused Trunk
Port.
Statistics Report of Displays the resources of the services between the

Service Resources NEs that are selected, such as Source NE, Sink
Between Ethernet NEs NE, EPL Number, EVPL Number, and EVPL
(QinQ) Number.
WDM WDM Protection Displays the switching status information of

Statistic Group Switching State WDM protection groups.
Report Report
WDM NE Master/ Provides the information of WDM NE Master/

Slave Shelf info Report Slave Subrack.
Statistics Report of Displays the WDM client-side port information

WDM Client-Side Port of the NE that is selected, such as Service Type,
Resources Total Port Number, and Activated Port Number.
Statistics Report of Collects the statistics on WDM link resources.

WDM Link Resources

Option Description
Statistics Report of Collects the statistics on the resources of

Inter-Station wavelengths among WDM stations.
Wavelength Resources
Statistics Report of Browses the information about WDM bandwidth

WDM Bandwidth resources.
Resources
Browse WDM Channel Browses the information about WDM channel

Resource resources.
Wavelength Resource Provides the information about wavelength

Usage Report resource usage.
PTN Statistic Interface Resource Provides the information about PTN interface
Report Report resources.
PON Port Splitting Status Collects the statistics on PON Port Splitting
Status.
Project Board Manufacturer Provides the information of card code, type,

Document Information manufacturing data and BOM.
Export Electronic Label Exports the electronic label from U2000.
Clock Tracing Diagram Creates the clock tracing diagram. This report
contains the NE ID, NE name, equipment type,
and fiber cable connections.
Networking Diagram Creates the networking diagram. This report

contains information about NEs, fiber cables and
fiber cable length.
Timeslot Allocation Creates the timeslot allocation diagram. This

Diagram report contains detailed information about
timeslot allocation for the specified protection
subnet.
1.8.7.9 Administration Menu

This topic describes the options on the Administration menu.
Menu Description
Option Description
Log Management Query Operation Sets the filter conditions to query operation logs.
Logs
Query System Logs Sets the filter conditions to query system logs.

Option Description
Query Security Sets the filter conditions to query security logs.

Logs
Operation Log Sets the statistics filter conditions to query

Statistics operation log statistics.
System Log Sets the statistics filter conditions to query

Statistics system log statistics.
Security Log Sets the statistics filter conditions to query

Statistics security log statistics.
NMS Security NMS User Manages NE users, user groups, and operation
Management sets. For example, set the security properties and
assign the related rights.
Monitor User Monitors the user sessions.

Sessions
Monitor User Sets the filter conditions to monitor user

Operations operations.
ACL Sets the global ACL. Only the IP addresses in

the ACL can access the U2000.
Security Policies Sets the global security policy of the U2000,

including the password policy and the account
policy.
Remote Displays the Remote Maintenance User

Maintenance User Management window for you to set the remote
Management maintenance user parameters.
Maintenance Sets the remote maintenance user parameters.

Personnel
Information
NE Maintenance Sets the information about the NE location and

Information maintenance engineer.
NE Security NE User Manages NE users for the specific NE. You can
Management Management query, add, delete and modify an NE user, and
set password for the NE user.
NE Login Views the default NE user that the U2000 uses

Management to log in to the current NE. You can log in, log
out and switch to another NE user.
Lock Out NE Login An NE user can lock out the NE, to deny login
attempts from other users of the same level or
lower level.

Option Description
Lock Out NE The NE functional modules include the

Settings configuration module, the alarm module, the
performance module, and other modules. These
modules can be locked out, so that other NE
users cannot perform any settings on the locked
modules until the lockout is manually or
automatically cleared.
RADIUS Configures and manages the Radius server for a

Configuration specific NE; enables or disables the function of
Management specifying an NE as the Radius client.
LCT User Manages the Access NE users for the specific

Management NE. You can query, add, delete and modify an
NE user, and set password for the NE user.
NE Syslog Run Log Views the NE running log.
NE Syslog Views the NE Operation logs.

Operation Logs
Synchronize Synchronizes the SNMP NE logs of all NEs to

SNMP NE Logs of the U2000. This helps the maintenance
ALL NEs personnel to view the SNMP NE logs.
Change Audit Queries the information about the changes. If

changes occur on an NE in the network, you can
query information about the changes through
U2000.
NE Communicate NE Access Sets the access protocol parameters for

Parameter Protocol equipment. Different devices may use different
Parameters access protocol parameters. You need to set
different access protocol parameters for
different devices.
Set SNMP Sets or queries the NE SNMP extended

Extended parameter.
Parameter
Default Access Sets the default values of access protocol

Protocol parameters. When you manually add a device or
Parameters the system automatically searches for a device,
the U2000 uses default access protocol
parameters to adapt to the device.
Set NE Telnet/ Sets the NE Telnet/STelnet parameter.

STelnet Parameter
NE Telnet/STelnet Sets or queries the NE Telnet/STelnet template.

Template
Management

Option Description
Batch Configure Batch Configure NM Parameter.

NM Parameter
NETCONF Manages the NETCONF parameter template.

Parameter
Template
Management
NE NETCONF Manages the NE NETCONF parameter.

Parameter
Management
NE License Management Queries, apply for, installs, and changes NE

license.
NE Software NE Data Backup/ Backups, saves, and recovers the device data.
Management Restoration
NE Upgrade Task Manages the NE upgrade task.

Management
NE Software Manages the NE software library.

Library
Management
Automatic Upgrade Performs automatic upgrade after card

After Board replacement. When you replace a card with a
Replacement new one, the system automatically checks
whether the version of the new card matches the
version of the equipment. This operation
implements the automatic upgrade of an online
card.
NE Software Log Views, backups, deletes, or filters the NE

Management software log information.
Default Policy Sets a default policy of the new devices added

to NE Software Management.
User-Defined Sets the user-defined policy for the devices

Policy added to NE Software Management.
Auto Upgrade Sets the auto upgrade policy. Before the plug-in/
Policy plug-out and fault autorun function, you must set
NE upgrade policy.
FTP Settings Performs the FTP settings. You must set the FTP
to use the NE Software Management
application.
HA Policy Log Views the HA policy log information.

Information

Option Description
NE Software Views and backs up the license and loads the

License new license to the equipment by using this
Management software.
Board Software Creates a software upgrade task that enables you

Upgrade to upgrade the software to the target version on
a device.
Board Patch Creates a card patch software upgrade task. The

Software Upgrade patch upgrade flow refers to a process wherein
the patch software in the patch package is loaded
to the control card and other cards. This flow is
applicable to the devices that support the
upgrade through a patch package.
NE License Manages the NE License.

Management
NE Log Backup Backs up the NE log.
TL1 Command Starts the TL1 command line terminal.

Lines Terminal
Upgrade Service Starts or stops services relevant to upgrade.

Management
WLAN/CPE CWMP Terminal Manages the models and versions of CWMP

Software and Task Software terminals.
Management
CWMP Task Manages the tasks for CWMP terminals and

Management upgrades the terminals.
File Server Manages file servers. You can view, add,

Management modify, and delete a file server.
View Bulk AP Views, stops, and re-performs the task of adding

Addition Tasks AP upgrades in batches.
View AP Upgrade Views, stops, and re-performs the task of adding

Tasks an AP upgrade.
View WLAN Views, stops, and re-performs the task of

Service WLAN service provisioning.
Provisioning Tasks
Log Management Configures and deletes logs.
WLAN/CPE When the quantity of the WLAN equipment and

License Alarm family terminals that are connected reaches the
threshold, an alarm is generated and prompts are
displayed at a scheduled interval in the U2000.
DCN Management Enables you to configure NEs and the gateway

NE.

Option Description
Task Schedule Enables you to set or query the task information.

Include task management, scheduling center,
TL1 scheduled task, ONT task list.
Back Up/Restore Database Backup Back up the database to the specified directory.
NMS Data
Import/Export Imports or exports the script files to restore or
Script File back up the data of the U2000 NE and network
configuration.
Configuration Upgrade Wizard Guides you to use the backup configuration data
script to restore the U2000 database.
Broadcast Message Sends broadcast messages to other clients.
Settings Log Forwarding Sets log forwarding server parameters.

Server
NE License Alert Sets alerts for the NE license. A set alert reminds
you to apply for the NE license in time.
xFtpWatcher Sets xFtp Watcher parameters.
Naming Define Names rules. The U2000 provides some fields

Rule by default. You can add new fields, modify or
delete the existing fields and adjust the field
position according to the actual requirements, to
customize the naming rule.
Alias Recycle Queries the information about the alias ever used
Management by an NE and performs related operations.
NE Partition Deploy the NE according to the NE partition

rules.
NE Partition Rules Set the NE partition rule.
Automatic NE Configuration Creates, modifies, imports, exports, and deletes

automatic NE configuration rules.
1.8.7.10 Window Menu

This topic describes the options on the Window menu.
Menu Description
Option Description
Full Screen Mode Selects the full screen mode by pressing F11.
Close Closes the current window.
Close All Closes all open windows exclude the Workbench.

Option Description
Minimize Minimizes the current window.
Minimize All Minimizes all the open windows.
Display Tab Bar Sets whether to display the tab bar.
Toggle Message Output Area Enables or disables the message output area.
Cascade Cascades all the open windows.
Tile Tiles all the open windows.
Tile Horizontally Tiles all the open windows horizontally.
Tile Vertically Tiles all the open windows vertically.
NOTE
The Window menu also includes a list of all windows that are currently open. The check mark to the left
of the window name indicates that the window is active. Select a window from the list to make it the active
window.
1.8.7.11 Help Menu

This topic describes the Help menu. The Help menu allows you to view the online Help topics,
the version and registration information about the U2000. TheHelp menu also allows you to
change a license.
Menu Description
Option Description
Help Topics To view the Help.
License License To display the information about a license and update the
Management Information license.
Query Invalid To view the invalidation code of a license on the U2000

License Code client. When applying for a license, you need to provide
the invalidation code of the old license.
Invalidate To invalidate an unnecessary license. After invalidation,

License the invalidation code of the license is generated. You can
use the invalidation code to apply for a license.
Check For Upgrades To manually check whether the version of the U2000
matches the version of the server and then determines
whether to update the client.
About Contains the U2000 version Component and registration

information.

1.8.8 Operations Frequently-Performed on the User Interface

This topic describes the operations that are frequently performed on the U2000 user interface.
1.8.8.1 Filtering Operation Objects in a View

The topology view displays subnets, links, and device nodes. When there are too many objects,
to be located in, you can use the filter tree to filter the objects in the view according to the object
type.
1.8.8.2 Moving Operation Objects
You can move the operation objects that are shown in the Main Topology.
1.8.8.3 Searching for NEs in a View
This operation enables you to find an NE quickly.
1.8.8.4 Counting the Number of NEs
By counting the number of NEs, you can learn the number of NEs that are created on the
U2000. The NEs contain real, preconfigured, and virtual NEs.
1.8.8.5 Customizing Parameter Display
You can customize the display of parameters by placing the important parameters that you use
on a regular basis, in a place that is easy to find. You can also hide the parameters that are not
regularly used.
1.8.8.6 Copying Table Text Quickly
The U2000 allows you to copy and paste table text. You can copy text from a table to other
programs quickly.
1.8.8.7 Setting Board Color
On the U2000, you can customize a board color, which indicates that the board works in the
normal state.
1.8.8.1 Filtering Operation Objects in a View

The topology view displays subnets, links, and device nodes. When there are too many objects,
to be located in, you can use the filter tree to filter the objects in the view according to the object
type.
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
l When the U2000 is started, the filter criterias are empty by default. All the topology objects
are displayed.
l When you deselect a filter criteria, the objects matching the criteria are not displayed.
Procedure
1 Do as follows to access the Legend/Filter/Attribute panel:
l Choose View > Display Setting > Filter from the main menu.
l Choose View > Display Setting > Legend from the main menu.
l Choose View > Display Setting > Attribute from the main menu.

The Legend/Filter/Attribute Panel is displayed on the right of the topology view.

2 In the Legend/Filter/Attribute panel, click the Filter tab.
3 Click Filter Tree and select Switch. In the Switch Filter Tree dialog box, select the filter tree
template. Click Open.
4 Choose Display Setting > Legend/Filter/Attribute. You can close the Legend/Filter/
Attribute panel.
----End
1.8.8.2 Moving Operation Objects

You can move the operation objects that are shown in the Main Topology.
Prerequisite
Procedure
1 Optional: If the view is locked out, choose View > Lock from the Main Menu.
NOTE
You can also click the shortcut icon displayed as in the Main Topology to unlock the view.
2 Select one or more NEs icon on the Main Topology, hold the primary mouse button and drag
the object to the specified position.
----End
1.8.8.3 Searching for NEs in a View

This operation enables you to find an NE quickly.
Prerequisite
l If you find NEs in the Physical Root, Tunnel View or Clock View on the Main
Topology window, the find operation is applicable to the current view.
l If you find NEs in the window outside the Main Topology, the find operation is application
to the Physical Root view.
l You must have the right of object management.
l When you search for a NE, dynamic fuzzy search is used. That is, when you enter the search
content, the result is displayed dynamically.
Procedure
1 Use the shortcut key of Ctrl+F on the Main Topology, or choose File > Find from the Main
Menu, or right-click on the Main Topology,choose Find from the shortcut menu, or click

The Search dialog box is displayed.

2 Select the search conditions, which are Type and Mode.
3 Enter the keyword according to the search conditions.
4 Optional: You can select Match whole, Case sensitive or Auto search with specified
keyword according to actual requirement.
5 Click Search.
All the found records are displayed in the windows of Search. Include name, type, address,
view and subnet.
6 Select an NE from the search result list, and then click Locate, select the locate to Topo from
the menu. You can also double-click the NE. If you want to locate the NE panel, click locate to
NE, select the NE Panel from the menu.
The NE is located in the topology view and navigation tree.
If the Minimized after locating check box is selected, the Search window is minimized after
the location.
----End
1.8.8.4 Counting the Number of NEs

By counting the number of NEs, you can learn the number of NEs that are created on the
U2000. The NEs contain real, preconfigured, and virtual NEs.
Prerequisite
Context
By default, the NE Statistics list is displayed on the left lower corner of the Main Topology
view of the client. If it is not displayed, Choose View > Display Setting > NE Statistics from
the main menu.
Procedure
1 Choose View > Display Setting > NE Statistics from the main menu.
2 In the NE Statistics list displayed on the left lower corner of the Main Topology view, check
the number of NEs.

----End
1.8.8.5 Customizing Parameter Display

You can customize the display of parameters by placing the important parameters that you use
on a regular basis, in a place that is easy to find. You can also hide the parameters that are not
regularly used.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
1 Right-click on the top of a parameter list, and choose the desired items from the shortcut menu.
The unselected items are not shown in the parameter list.
2 Optional: Click Setting in the shortcut menu and the Column Setting dialog box is displayed.
You can set whether to show a column in the parameter list, set the sequence of columns and
the column width.

----End
1.8.8.6 Copying Table Text Quickly

The U2000 allows you to copy and paste table text. You can copy text from a table to other
programs quickly.
Procedure
1 Select the text in a table, and press the shortcut keys Ctrl+C.
NOTE
l Select all texts in the table by pressing the shortcut keys Ctrl+A. Only the current screen of the table
is supported.
l To view all data in the current table, click Print or Save As.
2 Switch to another program, and press Ctrl+V. The selected text is copied to the system clipboard.
----End
1.8.8.7 Setting Board Color

On the U2000, you can customize a board color, which indicates that the board works in the
normal state.
Context
l The U2000 provides two colors, which indicate that a board works in the normal state: gray
and green.

l After setting the skin color of the board, you need to restart the U2000 client for the setting
to take effect.
Procedure
1 Choose File > Preferences from the main menu.
2 In the Preferences window, choose Board State in the navigation tree on the left.
3 In Normal State, select a skin color for the board.
4 Click OK.
----End
1.8.9 Custom View

In the U2000, different users have different network management scopes. The user can customise
a view for the network topologies and equipment under administration as a working interface.
The U2000 provides many view setting modes, including customizing views and setting to start
views. The custom view window displays the topological structure of the network, including
links, subnets or NEs. You can set a corresponding view according to requirements to facilitate
the management of network topologies.
Context
You can perform the following custom view functions:
1.8.9.1 Creating Custom Views
A physical view may contain many objects. It is difficult to find a specific object. If you are only
concerned about some devices and links, you can create a view to display the objects you are
concerned about.
1.8.9.2 Setting Startup subnet
You can set a custom subnet as the startup subnet.
1.8.9.1 Creating Custom Views

A physical view may contain many objects. It is difficult to find a specific object. If you are only
concerned about some devices and links, you can create a view to display the objects you are
concerned about.
Prerequisite

l You can create at most five views.
l When the selected two devices are connected with a link, the link is added to the Selected
Links table.
l Custom views are user-based. Users can view only their own custom views.
Procedure
1 Choose View > Creating > View from the main menu.
The Create Custom View dialog box is displayed.
2 In the Create Custom View dialog box, select the General tab.
3 In Name, enter the view name.
4 Click Topology, the Select Object dialog box is displayed.
5 Move the cursor to the topology navigation tree or the topology view. Right-click a device or
link and then choose Select. The selected submap, node, or link is displayed in the Select
Object dialog box.
NOTE
When you create a custom view, do not select devices in access domain, because they cannot be configured
or managed in custom views.
6 In the Select Object dialog box, click Finish.

7 On the Selected Nodes and Selected Links tabs of the Create Custom View dialog box, view
the object selected in the custom view.
8 In the Create Custom View dialog box, click OK.
----End
1.8.9.2 Setting Startup subnet

You can set a custom subnet as the startup subnet.
Prerequisite
Procedure
1 Choose View > Set Startup Subnet from the main menu. The Set My Startup Subnet dialog
box is displayed.
2 Select a subnet in the Set My Startup Subnet dialog box, click OK.
3 Restart the U2000 client, and the custom subnet is displayed automatically.
----End
1.9 How to Obtain Version Information About the U2000

Introduce how to obtain version information about the U2000.

Procedure
1 Server version
1. Log in to the U2000 System Monitor.
2. Click the Component Information tab to view version information about the server.
NOTE
In Solaris or SUSE Linux, you can run the more command to view the component files in /opt/U2000/
server/conf/about directory.
2 Client version
1. Log in to the U2000 client.
2. On the menu bar, choose Help > About.
3. In the About dialog box, view version information about the client.
NOTE
In Solaris, you can run the more command to view the component files in /opt/U2000/client/style/
defaultstyle/conf/about directory.
----End
1.10 Customizing the Client GUI Effect

You can customize the GUI effect of the U2000 client as required.
1.10.1 Setting the Font Size

You can set the font size on the U2000 client.
1.10.2 Setting the Skin
You can set the skin of the client as required.
1.10.3 Setting the Output Information
The output window is at the bottom of the U2000 client. It displays the prompt messages and
feedback information of the events that affect the running of the U2000.
1.10.4 Setting the Time and Date Formats of the Client
You can set the time format, time mode, and date format that are displayed on the client.
1.10.5 Setting the Workbench
This topic describes how to set the workbench display for the client. In addition, you can create
function links and executable links on the workbench to access operation GUIs quickly.
1.10.6 Set the Menu Collapse
On the U2000 client, you can enable or disable the menu folding feature. You can also set
Default visible menu item count and Least used count for menu item.
1.10.7 Setting the Number Format of the Client
You can customize the number display format of the client, such as, the display mode of the
system monitoring data.
1.10.8 Setting the Alarm Display in the Topology View
After you set the alarm display in the topology view, when an alarm in the certain state is
generated on an NE, the color of the NE in the topology view changes to the color that indicates
the highest alarm severity in this state. Thus, you can know the latest alarm information.

1.10.9 Setting the Topology View Display

You can set the topology node icon, such as its size, border color, and font.
1.10.10 Setting Prompt Colors of Alarms
You can set the prompt color for each alarm severity. This helps you browse different alarms
clearly.
1.10.11 Setting the Alarm Highlight
After you set the alarm highlight, an alarm is highlighted in the alarm query result window when
it is not handled in the preset period. The highlight prompts you to pay attention to the alarm.
1.10.12 Setting the Alarm Font
You can set font, size, style, and color for alarms displayed in the current alarm, alarm logs,
event logs, and other windows to distinguish alarms that are not viewed from alarms that are
already viewed.
1.10.13 Setting the Alarm Display Mode
You can set the alarm and event background colors in the current alarm, alarm logs, event logs,
and other windows.
1.10.14 Setting the Display Property of a New Alarm/Event
You can set the new alarm/event display property to view the newly reported alarm/event.
1.10.15 Setting the Toolbar
You can perform this task to set the shortcut buttons shown on the toolbar.
1.10.1 Setting the Font Size

You can set the font size on the U2000 client.
Context
After you set the font size, you need to log in to the U2000 client again for the setting to take
effect.
Procedure
2 From the navigation tree on the left of the Preferences window, select Font.
3 Select an option in Font Size.

NOTE
Font Size can be as follows:
l Small: The font size is 11 points.
l Middle (Default): The font size is 12 points.
l Large: The font size is 13 points.
4 Click OK.
----End
1.10.2 Setting the Skin

You can set the skin of the client as required.
Context
l The skin of the U2000 client supports two colors: gray and green.
l After setting the skin color, you need to restart the U2000 client for the setting to take effect.
Procedure
2 In the Preferences window, choose Skin in the navigation tree on the left.
3 In Skin Settings, select a skin color for the client.
4 Click OK.
----End
1.10.3 Setting the Output Information

The output window is at the bottom of the U2000 client. It displays the prompt messages and
feedback information of the events that affect the running of the U2000.
Procedure
2 From the navigation tree on the left of the Preferences window, select Output Window.

3 Set relevant parameters in the Output Window area, and then click OK.
4 You can perform the following operations in the information output area at the bottom of the
interface.
Option Description
Copy 1. Choose the displayed output information.

2. Right-click and choose Copy to copy the information
to the clipboard.
Select All 1. Right-click in the output window and choose Select

All.
2. Right-click again and choose Copy to copy all the
displayed output information to the clipboard.
Clear Right-click in the output window and choose Clear to clear

all the displayed output information.
Find 1. Right-click in the output window and choose Find.

2. In the Find dialog box, type the key words to be
searched for in Find what.
NOTE
l Match: To set whether the search content is case sensitive.
The default is case insensitive.
l Match whole word only: To perform a fuzzy search, clear
Match whole word only. To perform a precise search, select
Match whole word only.
l Direction: To set the direction for a key word search.

Option Description
Save As Right-click to choose Save As. In the Save dialog box,

save the current output to a .txt file.
AutoScroll Right-click in the output window and choose

AutoScroll. The output information scrolls automatically
to the latest information. Right-click in the output window
again and choose AutoScroll, the auto scroll is disabled.
Parameter Settings Right-click in the output window and choose Parameter

Settings. The Output Window pane is displayed in the
Preferences window.
----End
1.10.4 Setting the Time and Date Formats of the Client

You can set the time format, time mode, and date format that are displayed on the client.
1.10.4.1 Setting the Time Format of the Client

This topic describes how to set the time format of the client.
1.10.4.2 Setting the Date Format of the Client
This topic describes how to set the date format of the client.
1.10.4.3 Setting the Time Mode of the Client
This topic describes how to set the time mode of the client to determine whether the time is
displayed according to the U2000 server time or the NE time.
1.10.4.1 Setting the Time Format of the Client

This topic describes how to set the time format of the client.
Context
l After you set the time format, you need to log in to the client again for the settings to take
effect.
l Next time when you log in to the client, the U2000 client automatically uses the settings
that you set last time.
l The time display effect that you set is displayed in the Time Format Notation area.
Procedure
2 From the navigation tree on the left of the Preferences window, expand the Region Settings
node and choose Time.

3 In the Time group box, set the time format.

4 Click OK.
----End
1.10.4.2 Setting the Date Format of the Client

This topic describes how to set the date format of the client.
Context
l After you set the date format, you need to restart the U2000 client again for the settings to
take effect.
that you used last time.
l The date display effect that you set is displayed in Appearance Example.
Procedure
2 In the navigation tree on the left of the Preferences window, expand the Region Settings node
and select Date.

3 In the Date group box, set the date format.

NOTE
l Date Separator: symbol to separate the date. There are three symbols for you to select: "/", "-", and
".". The default is "/".
l Date Format: display format of the date. It can be set to "yyyy/MM/dd", "dd/MM/yyyy", or "MM/dd/
yyyy". The default is "MM/dd/yyyy".
4 Click OK.
----End
1.10.4.3 Setting the Time Mode of the Client

Context
The settings take effect after you log in to the client again.
l After you set the time mode, you need to restart the U2000 client for the settings to take
effect.
Procedure
2 In the navigation tree on the left of the Preferences window, select Time Mode.

3 In the Time Mode group box, select Time Mode.

NOTE
l Server time mode: If you select this mode, the alarms are queried according to the server time.
l Client time mode: If you select this mode, the alarms are queried according to the client time. You are
advised to retain the default value Client time mode.
4 Click OK.
----End
1.10.5 Setting the Workbench

This topic describes how to set the workbench display for the client. In addition, you can create
function links and executable links on the workbench to access operation GUIs quickly.
Context
l After you set the workbench display, you need to restart the U2000 client for the setting to
take effect.
l The maximum number of links on the workbench is 100.
Procedure
l You can perform the following operations on the workbench.
Option Description
Enable/disable the workbench l Enable/disable the workbench

1. Choose File > Preferences from the main
menu.
2. In the Preferences window, choose
Workbench in the navigation tree on the left.
3. Select or deselect Enable Workbench.
4. Click OK.
NOTE
After enabling the workbench, the workbench
interface is directly displayed when you log in to
the U2000 client next time.

Option Description
Create workbench 1. Log in to the U2000 client to go to the workbench

operation interface.
2. Right-click the blank space on the left of the
interface and choose Create Workbench.
3. In the Create Workbench dialog box, enter the
workbench name and description, and then select
a workbench icon and background.
4. Click Create.
Modify workbench 1. On the left of the interface, right-click the icon

of the workbench to be modified and choose
Modify workbench.
2. In the Modify Workbench Link dialog box,
modify the workbench information such as the
workbench name, description, and icon.
3. Click Modify.
Remove workbench l On the left of the interface, right-click the icon

of the workbench to be deleted and choose
Remove workbench.
l In the Confirm dialog box, click Yes.
Import Workbench The U2000 provides the function of importing the

workbench data from a file. You can import the
workbench data from a file to a new workbench of
the U2000. This facilitates you to create a
workbench.
1. On the left of the interface, right-click the icon
of a workbench and choose Import
Workbench.
2. In the Import Workbench dialog box, select the
workbench file to be imported, and then click
Import.
Export Workbench The U2000 provides the function of exporting the

workbench data. You can export the data on the
workbench to a file on the local client for future
maintenance and browse.
1. On the left of the interface, right-click the icon
of a workbench and choose Export
Workbench.
2. In the Export Workbench dialog box, set the
name and format of the export file, and then click
Export.

Option Description
Create a shortcut for U2000 In the Workbench window, you can create the
function shortcut for the U2000 function.
1. In the right-hand pane of Workbench window,
right-click the blank space and choose Create
Shortcut.
2. In Create Shortcut dialog box, select function
option.
3. Click Create.
Create a shortcut for executable In the right-hand pane of Workbench window, you
application can create links of executable programs.
1. In the Workbench window, right-click the blank
space and choose Create Executable
Application.
2. In the Create Executable Application dialog
box, enter the name and description of an
executable application, and then select the
application and icon of the executable
application.
3. Click Create
.
NOTE
l To check whether the executable command is valid,
click Test.
l You can use the local images of the operating system
as the icon of shortcuts according to your
requirements.
Modify a shortcut of U2000 1. In the right-hand pane of Workbench window,

function or executable right-click a shortcut icon of U2000 function or
application executable application and choose Modify.
2. In the Modify Shortcut dialog box, change the
name, description, icon, or move to. Or in the
Modify Executable Link dialog box, change the
name, description, application, icon, or move to.
3. Click Modify.
Arrange icons by name In the right-hand pane of Workbench window,

right-click the blank space and choose Arrange
icons by name to sort shortcut icons or executable
link icons. After sorting, icons are listed in
horizontal lines.

Option Description
Delete a shortcut of U2000 1. In the right-hand pane of Workbench window,

function or executable right-click a shortcut icon of U2000 function or
application executable application and choose Remove.
2. In the Confirm dialog box, click Yes. Then the
function link icon or executable application link
icon is deleted from the Workbench window.
Copy an icon Copy the selected workbench icon to the clipboard.

Then choose the shortcut menu Paste to copy the
icon to another workbench.
Cut an icon Cut the selected workbench icon to the clipboard.

Then choose the shortcut menu Paste to move the
icon to another workbench.
Drag an icon to another position In the Workbench window, drag an icon to a proper
position.
----End
1.10.6 Set the Menu Collapse

On the U2000 client, you can enable or disable the menu folding feature. You can also set
Default visible menu item count and Least used count for menu item.
Procedure
2 In the Preferences window, choose Menu Settings in the navigation tree on the left.
3 Select Enable menu folding feature to enable the menu folding feature.
NOTE
If you select Enable menu folding feature, Default visible menu item count and Least used count for
menu item become editable.

4 Set Default visible menu item count and Least used count for menu item.
5 Click OK.
----End
1.10.7 Setting the Number Format of the Client

You can customize the number display format of the client, such as, the display mode of the
system monitoring data.
Context
l The settings take effect after you log in to the client again.
l After you modify the number settings, the display of the number may be changed. You can
view the display effect in the Positive number text box and Negative number text box.
Procedure
2 In the Preferences dialog box, select Number from the navigation tree on the left.
3 Set the number display format in the Number Settings area.

NOTE
l Digits of decimal fraction: number of digits after the decimal. The value ranges from 0 to 3, and the
default value is 2.
l Number separator: whether to use comma (,) to group the integer part of a number. The value can be
null or comma.
l Start with 0: whether to add 0 before the decimal point. By default, 0 is added before the decimal
point.
4 Click OK.
----End


Context
l Acknowledged and cleared alarms are not displayed in the topology view, because they
indicate that the faults are already rectified. To know the meaning of each alarm state, see
7.1.10 Alarm States.
l In the Example pane, you can view the display effect after setting.
l You can click Default to restore the settings in the Topology Status Display (For the
current user) dialog box to the defaults.
Procedure
2 In the Preferences dialog box, choose the Topology Status Display node.

3 Set the alarm display attributes of the topology view.
Set the Alarm Display in the Operation

Topology View
Display Style of Alarm States In the Display Style of Alarm States area, set the alarm
state display mode in the topology view.
NOTE
When an alarm in a certain state is generated by an NE, the topology
icon of the NE in the topology view is displayed in the
corresponding color. For details on how to set alarm colors, see
1.10.10 Setting Prompt Colors of Alarms.


Topology View
Alarm States to Be Displayed In the Alarm States to Be Displayed area, set the alarm
states to be displayed in the topology view. If you select
Customize the alarm states to be displayed, click the
Up or Down button to change the state display priority.
NOTE
The state listed on the top has the highest priority. When there are
alarms in multiple states, the color of the topology icon depends
on that of the alarm state in the highest priority.
Additional Display Effects In the Additional Display Effects pane, set the additional
display effects, such as Blink, Show alarm prompt, and
Add an icon frame for an unacknowledged alarm.
4 Click OK.
----End
1.10.9 Setting the Topology View Display

You can set the topology node icon, such as its size, border color, and font.
Procedure
2 In the Preferences dialog box, choose the Set Topology Display node.

3 In the Set Topology Display (For the current user) dialog box, set the View Background
Color, Subnet, Link Line, Node Icon, and Node Label.
4 Click OK.
NOTE
Click Default to restore the settings in the Set Topology Display (For the current user) dialog box to
their defaults.
----End


clearly.
Context
After setting, the alarm icon in the topology view, the alarm record you have queried, and the
alarm indicator on the alarm panel are shown in the specified colors.
Procedure
2 In the Preferences dialog box, choose Color Setting in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
3 In the Color Setting group box, click in each row to select prompt colors of alarms.
NOTE
You can click Default in the Preferences dialog box to restore a color to the default.
4 Click OK.
----End


Context
l For the alarm that meets the highlight condition, if the difference between the local time
of the client and the time of alarm occurrence reaches the threshold time for highlight, the
alarm is highlighted.
l You can click Default to reset the settings to defaults.
Procedure
2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
Highlight in the navigation tree on the left.
NOTE
3 In the Highlight group box, set the time and alarm status for alarms of a certain severity, and
then select Enable.
NOTE
The validity period ranges from 1 to 1000000 minutes.
4 Click OK.
----End

already viewed.
Context
To restore all settings in this area to defaults, click Default.

Procedure
2 In the Preferences dialog box, in the navigation tree on the left, expand the Alarm Local
Terminal Settings node, and then select Alarm Fonts.
3 In the Alarm Fonts area, set fonts, sizes, styles, and colors for alarms that are not read and that
are already read.
4 Click OK.
----End

and other windows.
Context
Procedure
Terminal Settings node, and then select Alarm Display Mode.

NOTE
3 In the Alarm Display Mode area, select the alarm display mode, and set background colors for
different alarm states.
Table 1-5 Alarm background color in various display mode

Display Mode Field Alarm Background Color
Icon Severity The background color is displayed based on the

color of the state. The severity icon is displayed
in the Severity field, and the color of the
severity icon is displayed based on the color of
its severity.
All the other fields The background colors of all the other fields are
displayed based on the colors of their status.
CellBackground Severity The background color is displayed based on the

color of the severity.
RowBackground Severity The background color is displayed based on the

All the other fields The background colors of the unacknowledged

and uncleared alarms are displayed based on
the colors of their severities, whereas the
background colors of the alarms in other status
are displayed based on the colors of their status.

NOTE
The Identifier field has no background color. Therefore, it is not affected by the setting of the alarm display
mode.
4 Click OK.
----End

Procedure
Terminal Settings node, and then select New Alarm/Event.
NOTE
3 In the New Alarm/Event group box, select The Client Is on Top When a New Alarm Is
Reported and the alarm severity.
4 In the New Alarm/Event group box, select Display on top or Display at the bottom.

5 In the Visible Level in Alarm Lamps group box, select the severity to be displayed on the alarm
indicator.
6 In the Additional Options group box, set the display properties.
7 Click OK.
----End
1.10.15 Setting the Toolbar

You can perform this task to set the shortcut buttons shown on the toolbar.
Procedure
1 Choose File > Customize Toolbar from the main menu.
2 In the Customize Toolbar dialog box, select System or Fault in the Toolbar Groups group
box.
3 Click Advanced. The Toolbar dialog box displays the Toolbar Buttons group box.
NOTE
l The Toolbar Buttons group box consists of two parts: Usable Tools and Customized Tools. All the
buttons in Customized Tools are displayed on the toolbar, and the buttons in Usable Tools are not
displayed on the toolbar.
l Click Advanced again. The Toolbar Buttons group box is hidden.
l Click Reset All to restore the Customized Tools to the initial state so that you can reset the toolbar.
l Click Reset to restore the toolbar buttons of the selected toolbar group to the initial state so that you
can reset the toolbar buttons.
4 In the Toolbar Buttons group box, set the buttons you want to display on the toolbar.
l In the Usable Tools group box, select one button or hold down Ctrl or Shift to select
multiple buttons you want to display. Click to move the selected buttons to the
Customized Tools group box.
l In the Customized Tools group box, select one or hold down Ctrl or Shift to select multiple
buttons you do not want to display. Click to move the selected buttons to the
Usable Tools group box.
5 Click OK.
----End
1.11 Setting the Alarm Sound at Network Disconnection

After you set the disconnection alarm sound on the U2000 client, the sound box connected to
the client plays the sound if the U2000 client is disconnected from the server.
Context
The sound files used for prompting network disconnection support only the sound files of the
Wav type in the PCM format. The sound files of the Wav type can be recorded in two formats:
PCM and Microsoft ADPCM.

Procedure
2 In the Preferences dialog box, select Disconnection Sound from the navigation tree on the left.
3 In the Disconnection Sound group box, select Enable.
4 Click . In the Open dialog box, select a sound file, and then click Open.
5 Click to play the sound.

6 Click OK.
----End
1.12 Checking Whether the Client Needs Upgrade

You can perform this operation to check whether the version of the client matches that of the
server. If the versions do not match, you must upgrade the client.
Context
If the U2000 server is upgraded but the client is not upgraded, it may cause the version of the
client does not match that of the server.
Procedure
1 Choose Help > Check For Upgrades from the main menu to check whether the client version
matches the server version.
l When the versions match, the client does not need to be upgraded. In this case, click OK.
l When the versions do not match, you must upgrade the client. In this case, perform the
following operations to upgrade the client:
1. Click OK.
2. In the Update Wizard: Update Applications window, click Continue. The upgrade
progress is displayed.
3. In the Update Wizard: Update Applications window, click Finish.
----End

1.13 Setting the Interval of Client Upgrade Check

After the server is upgraded, the server version and the client version do not match. Therefore,
the client has to be upgraded accordingly. After the interval for upgrade checking is set, the
U2000 periodically checks whether the client needs to be upgraded.
Procedure
2 In the Preferences dialog box, in the navigation tree on the left, select Upgrade.
3 Select the interval for upgrade checking in the Time Interval drop-down list box.
4 Click OK.
----End
1.14 Locking the Client

You can lock the client to prevent unauthorized operations.
Context
l This function is applicable to only the local client.
l In the Preferences dialog box, select Visible on Terminal Lock in the Locking
Settings area. Thus, after the client is locked, the main window of the client is visible.
Procedure
l The following table describes how to set the client to be locked manually or automatically.

Lock Mode Operations
Automatically After you set the client to be locked automatically, the client is
automatically locked if it does not receive any operation
instructions in the specified period. To set the client to be locked
automatically, do as follows:
1. Choose File > Preferences.
2. Select Lock Settings in the navigation tree in the left pane of
the Preferences dialog box. In the Locking Interval area,
select Automatically Locked.
3. Enter the lock time for the Automatically Locked mode.
4. Click OK.
5. In the Information dialog box, click OK.
The client is locked automatically when the specified time arrives.
Manually To ensure U2000 system security, if you do not perform operations

on the U2000 client for a period, you can lock the client to prevent
others from performing illegal operations on the U2000 client. You
can lock the client manually by using the following method:
l Choose File > Lock Terminal from the menu bar.
l Click on the toolbar.
----End
1.15 Unlocking the Client

This section describes how to unlock the locked U2000 client.
Context
CAUTION
If your user account is in the Administrators user group and you unlock a user account of
someone else, the unlocked account is logged out, and the previous operation data is lost.
If you unlock your own account, the U2000 becomes operable after the account is unlocked.
Procedure
1 When the client is locked, press Ctrl+Alt+U.
2 In the Unlock dialog box, enter the user name and the password, and then click OK.
----End

1.16 Setting a Scheduled Task

The U2000 can automatically executing certain tasks in a scheduled time without manual
intervention. You can set and modify these scheduled tasks as required.
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
If a large number of performance data need to be collected, this may cause communication
congestion and thus the communication between the U2000 and NEs stops. Hence, observe the
following rules to collect the performance data:
l When creating a single performance data collection task, the number of NEs related to the
same GNE does not exceed 5.
l Run the performance data collection task when network traffic is low.
Procedure
1 Choose Administration > Task Schedule > Task Management from the main menu.
2 Optional: Create a scheduled task.
1. Click New and the New Task is displayed.
2. Enter a task name and select the task type of the scheduled task and the run type. Then,
click Next.
3. Set the Time Setting or the Period Setting. Click Next.
4. Follow the task creation wizard to set the parameters of the scheduled task and click
Next for several times until the Finish button is displayed.
5. Click Finish. A scheduled task is successfully created.
3 Optional: Double-click a scheduled task to modify the parameters of the task.
4 Optional: Right-click a scheduled task and choose Timely Suspend/Resume to set the suspend
time or the resume time for the task. Click OK.
5 Optional: Right-click a scheduled task and choose Run At Once to start executing the task.
NOTE
Run At Once means to immediately execute the task, no matter the scheduled time comes or not.
Resume means to start the scheduled task. The task is executed at the scheduled time.
----End
1.17 Broadcast Messages

The broadcast message function includes setting the broadcast parameter and sending the
broadcast message. The broadcast message function of the U2000 enables you to send messages
to other users with ease.
1.17.1 Setting Broadcast Parameters

Setting the broadcast parameters on the U2000 client refers to setting the number of latest
messages and the total number of stored messages, that is, setting the number of broadcast
messages to be displayed on the client and the total number of broadcast messages to be cached
in the server.
1.17.2 Sending Broadcast Messages
This topic describes how to send broadcast messages from the client.
1.17.1 Setting Broadcast Parameters

Setting the broadcast parameters on the U2000 client refers to setting the number of latest
messages and the total number of stored messages, that is, setting the number of broadcast
messages to be displayed on the client and the total number of broadcast messages to be cached
in the server.
Context
The task of the following procedure is to set broadcast parameters and apply them to the current
client.
Procedure
1 Choose Administration > Broadcast Message from the main menu.
2 In the Broadcast Message dialog box, click Options.
3 In the Broadcast Messages Options dialog box, enter the values in Number of messages to
display and Saved message count, click Save.
4 In the Information dialog box, click OK.
----End
1.17.2 Sending Broadcast Messages

This topic describes how to send broadcast messages from the client.
Context
l The client can receive its own broadcast messages. The output area in the lower part of the
U2000 client displays corresponding prompts.
l You have both permissions to set broadcast message parameters and send broadcast
messages.
l Only the online U2000 client can receive the broadcast messages.

Procedure
1 Choose Administration > Broadcast Message from the main menu.
2 In the Broadcast Message dialog box, enter the message content in the Sending message field.
NOTE
l A broadcast message cannot be null, and cannot exceed 128 characters.

l The U2000 automatically adds line feeds according to the length of broadcast messages.
3 Click Send.
When the sending is complete, the Message dialog box is displayed on other clients. Users can
click Detail to view the message.
4 In the Information dialog box, click OK.
----End
1.18 Applying for and Updating the License

This topic describes the license file of the U2000, and how to apply for, install, and use the
U2000 license.
1.18.1 U2000 License Precautions
This topic describes the U2000 license file. The license file is used to control the functions and
management capabilities of the U2000. If the license file is unavailable, you cannot log in to the
U2000 client but can only log in to the System Monitor client.
1.18.2 Applying for the U2000 License
This topic describes how to apply for the U2000 license.

1.18.3 Updating the U2000 License

This topic describes how to update the U2000 license.
1.18.4 Checking the Status of the U2000 License
This topic describes how to check the status of the U2000 license. By checking the license status,
you can learn the usage of the license, so as to apply for a new license file from Huawei in time
before the NMS needs to be expanded or the validity of the license is due.
1.18.5 Setting the Threshold of the Accessing NEs
When the number of accessing NEs reaches the preset threshold, the U2000 sends an NE license
alarm and displays an Information dialog box periodically.
1.18.6 Verifying the U2000 License
Introduce how to correctly use a U2000 License.
1.18.1 U2000 License Precautions

This topic describes the U2000 license file. The license file is used to control the functions and
management capabilities of the U2000. If the license file is unavailable, you cannot log in to the
U2000 client but can only log in to the System Monitor client.
l The U2000 license file naming format is: ONxxxxxxx.dat.
l One license file corresponds to the equipment serial number (ESN) in an NMS computer
and can be used only on the corresponding computer.
l The number of ESNs is the same as the number of network interfaces on the U2000 server.
The U2000 license is valid as long as it is bound to any of the server ESNs. To avoid
applying for a new license due to replacing certain network interface cards (NICs), save
all the ESNs to ensure proper use of the U2000 license.
l Do not make any change to the license file. Otherwise, the license becomes invalid.
l The license folder contains only one license file in the server/etc/conf/license directory of
the U2000.
l The license control items vary according to the versions of the U2000. When you fill in the
application form, use the template that matches the intended version of the U2000.
l The requirements for the server ESN to which a license needs to be bound vary according
to the installation scheme. You need to obtain the server ESN based on the installation
scheme.
– In the single-server System (centralized) scheme, the license needs to be bound to the
ESN of the server.
– In the single-server System (distributed) scheme, the license needs to be bound to the
ESN of the master server.
– In the high availability system (Veritas hot standby-centralized) scheme, the license
needs to be bound to the ESNs of both the primary site server and the secondary site
server.
– In the high availability system (Veritas hot standby-distributed) scheme, the license
needs to be bound to the ESNs of the master servers of both the primary site and the
secondary site.
l The licenses of different R versions of the U2000 are incompatible. For example, the license
of V100R001 cannot be used by V100R002.

1.18.2 Applying for the U2000 License

This topic describes how to apply for the U2000 license.
Context
l The license file is not delivered to customers along with the U2000 installation DVD.
Contact Huawei engineers to apply for the licenses according to the contract number and
the equipment serial number (ESN) of the U2000 server.
l The ESN is a string consisting of 40-digit numerals or letters obtained through encrypted
calculation on the MAC addresses of the U2000 server network interface. The number of
ESNs is the same as the number of network interfaces on the U2000 server.
The U2000 license is valid as long as it is bound to any of the server ESNs. To avoid
applying for a new license due to replacing certain network interface cards (NICs), save
all the ESNs to ensure proper use of the U2000 license.
l The requirements for the server ESN to which a license needs to be bound vary according
to the installation scheme. You need to obtain the server ESN based on the installation
scheme.
– In the single-server System (centralized) scheme, the license needs to be bound to the
ESN of the server.
– In the single-server System (distributed) scheme, the license needs to be bound to the
ESN of the master server.
– In the high availability system (Veritas hot standby-centralized) scheme, the license
needs to be bound to the ESNs of both the primary site server and the secondary site
server.
– In the high availability system (Veritas hot standby-distributed) scheme, the license
needs to be bound to the ESNs of the master servers of both the primary site and the
secondary site.
Procedure
1 Obtain the contract number.
2 Use the ESN tool provided by the NMS to view the server ESN.
NOTE
Before installing the U2000, you can do as follows to view the ESN of the U2000 server by using the ESN
tool provided with the U2000. Alternatively, you can obtain an ESN tool from http://support.huawei.com
to generate the ESN. The ESN tool names are as follows:
l Solaris OS: U2000version_ESN_solaris_SPARC.tar
l Linux OS: U2000version_ESN_sles_x64.tar
l Windows OS: U2000version_ESN_win32_x86.zip
In Solaris or SUSE Linux OS
1. Log in to the OS of the U2000 server as the root user.

NOTE
When the Veritas hot standby HA system is used, you need to log in to the primary and secondary
sites OS as the nmsuser user.
2. Run the following command to view the ESN:

l In Solaris OS
# . /export/home/nmsuser/.profile
# cd /opt/U2000/server/lbin
# ./esn
l In the SUSE Linux OS

# . /export/home/nmsuser/.profile
# cd /opt/U2000/server/lbin
# ./esn
NOTE
There must be a space between the dot (.) and the command (/nmsuser/.profile) in the commands.

ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4
ESN1:BDA706C825FE0543DC028209778AA66396545412
ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BD
ESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4
.....
NOTE
When the Veritas hot standby HA system is used, you need to respectively save the ESNs of the network
interfaces on the primary and secondary sites. During the application for the formal license file, you need to
provide the ESNs of the network interfaces of the primary and secondary sites for external communication.
In the Windows OS,you can do as follows to obtain the ESN:
1. Choose Start > Run.

2. In the Run dialog box, enter cmd. The CLI is displayed.
3. Run the following commands:
>esn

ESN0:EBB74B99612CEDC82AD0A59886EC5018CE44DDD4
ESN1:BDA706C825FE0543DC028209778AA66396545412
ESN2:E1B00EEF6947DD95687AA5C608B72ACC532AB2BD
ESN3:F72F9EC08AEE78AA05A42EFD7BFD89F5E03139C4
.....
3 Send the contract number and the server ESN to Huawei engineers or the local Huawei office.
NOTE
Huawei engineers need the contract number and ESN to procure the license from http://license.huawei.com.
For details about how to apply for the license file, see the iManager U2000V100R002C01 License
Instructions.
4 Huawei engineers send the license file to you after obtaining it.
The license file provided with the U2000 exist as a .dat file.
----End
1.18.3 Updating the U2000 License

This topic describes how to update the U2000 license.
Prerequisite
l The OS and database must run properly.
l The processes of the U2000 must be properly started.

l You must log in to the U2000 as the admin user.

l The license file of the U2000 must be obtained.
– Through the GUI of the client: Save the new U2000 license to the server where the
U2000 client is located.
– Through the CLI: The new license file must be transferred to the U2000 server through
FTP.
– In the Solaris OS, upload the license file to the /export/home/nmsuser path on the
server as the nmsuser user.
– In the SUSE Linux OS, upload the license file to the /export/home/nmsuser path
on the server as the root user.
– In the high availability system, upload the new U2000 license file to the /export/
home/nmsuser path on the server on the primary site through FTP.
l Confirm that the license file is transferred in text mode, that is, in ASCII mode.
Context
l In the case that the device types supported by the new license are different from those
supported by the original license, the license is updated as follows:
– If the device types supported by the new license are more than the device types supported
by the original license and the added device types are supported by the current version,
the license can be updated. If the added device types are not supported by the current
version, the license cannot be updated.
– If the device types supported by the new license are less than the device types supported
by the original license and no NEs of the reduced device types are created in the NMS,
the license can be updated. If certain NEs of the reduced device types are created in the
NMS, the license cannot be updated.
l If the function items supported by the new license are less those supported by the original
license, the license cannot be updated.
l In the case that the number of clients supported by the new license is different from that
supported by the original license, the license is updated as follows:
– If the number of clients supported by the new license is less than that supported by the
original license but the number of online clients is less than the number of clients
supported by the new license, the license can be updated. If the number of online clients
is greater that the number of clients supported in the new license, the license cannot be
updated.
– If the number of clients supported by the new license is greater than that supported by
the original license, the license can be updated.
In scenarios where you can change the license, you can update the U2000 license through the
following methods.
CAUTION
l It is recommended that you update the U2000 license through the GUI of the client.
l To ensure the normal running of the U2000, do not manually replace the license file.
l Through the GUI of the Client

– Application scenario: This method is recommended if you can log in to the U2000 client
and access the GUI.
– Operation method: Log in to the U2000 client, and then click Update License to update
the license.
Restart the client after you update the license. Then, the client automatically reloads
GUI elements according to control items defined in the new license.
l Through the CLI
– Application scenario: This method is applicable to the scenario where you need to
remotely update the license through commands because logging in to the U2000 client
is not allowed and the client does not provide any GUI.
– Operation method: Check that the processes of the U2000 are properly started, and then
run the updateLicense -file filename command to update the license file.
Procedure
l Through the GUI of the Client
For the single-server system
1. On the U2000 workstation, back up the original license file.
– In the Windows OS: Create the backup folder in the default directory D:\U2000
\server\etc\conf\license. Copy the original license file to the created folder.
– In the Solaris or SUSE Linux OS: Create the backup folder in the default
directory /opt/U2000/server/etc/conf/license. Copy the original license file to the
created folder.
2. Choose Help > License Management > License Information from the client main
menu. Then, click Update License. In the Open dialog box that is displayed, select
the new license file and click Open.
For the HA system
1. Log in to the U2000 server on the primary site.
2. Back up the original U2000 license file.
Create the backup folder in the default path. Then, copy the original license file to
this folder.
NOTE
l The default path of U2000 license file in the Solaris or SUSE Linux OS is /opt/U2000/
server/etc/conf/license.
l The default path of U2000 license file in the Windows OS is D:\U2000\server\etc\conf
\license.
3. Update the license file on the primary site.
(1) Log in to the U2000 client on the primary site.
(2) Choose Help > License Management > License Information from the client
main menu.
(3) Then, click Update License.
(4) In the Open dialog box that is displayed, select the new license file and click
Open.
4. Log in to the U2000 server on secondary site.
5. Update the license file on the secondary site.

this folder.
NOTE
\license.
6. Update the license file on secondary site.
(1) Log in to the U2000 client on the primary site.
(2) Choose Help > License Management > License Information from the client
main menu.
(3) Then, click Update License.
(4) In the Open dialog box that is displayed, select the new license file and click
Open.
l Through the CLI
For the single-server system
1. On the U2000 workstation, back up the original license file.
– In the Windows OS: Create the backup folder in the default directory D:\U2000
\server\etc\conf\license. Copy the original license file to the created folder.
– In the Solaris or SUSE Linux OS: Create the backup folder in the default
directory /opt/U2000/server/etc/conf/license. Copy the original license file to the
created folder.
2. Update the U2000 license.
(1) In the Windows OS:
a. Log in to the OS of the server.
b. Run the following command to update the U2000 license file:
> updateLicense -file License_file_name
NOTE
In the command, License_file_name indicates a file name or the combination of an

absolute path and a file name.
state product feature item
name old value new value
no change: U2000 COMMON LSW1CAPA01
Client 500 500
Client 1 1
no change: U2000 COMMON LSW1FMCLT01 Alarm
Export 1 1
no change: U2000 COMMON LSW1RENOTI01
Client 1 1
Are you sure to update the license?(Y/N)
c. Enter Y, and then press Enter.

(2) In the Solaris OS:
a. log in to the OS of the U2000 server as the nmsuser user.
b. Run the following command to update the U2000 license file:
$ cd /export/home/nmsuser

$ updateLicense -file License_file_name
NOTE

Client 500 500
Client 1 1
Export 1 1
Client 1 1
c. Enter Y, and then press Enter.

(3) In the SUSE Linux OS:
a. log in to the OS of the U2000 server as the root user.
b. Run the svc_profile script to set environment variables.
Run the following command:
# cd /opt/U2000/server
# . svc_profile.sh
NOTE
Leave a space between the dot (.) and svc_profile.sh.

c. Run the following command to update the U2000 license file:
# cd /export/home/nmsuser
# updateLicense -file License_file_name
NOTE

Client 500 500
Client 1 1
Export 1 1
Client 1 1
d. Enter Y, and then press Enter.

For the HA system
1. Log in to the U2000 server on the primary site.
2. Back up the original U2000 license file.
this folder.

NOTE
\license.
3. Run the updateLicense command to update the license file on the primary site. For
details, see 2.
4. Log in to the U2000 server on secondary site.
5. Update the license file on the secondary site.
this folder.
NOTE
\license.
6. Transfer the updated license file on the primary site to the /opt/U2000/server/etc/
conf/license path on the server on the secondary site in text mode, that is, ASCII mode.
NOTE
\license.
l In the Solaris or SUSE Linux OS: You should transfer the updated license file on the
primary site to the server on the secondary site in text mode, that is, ASCII mode. In the
Windows OS: Copy and paste the updated license file on the primary site to the the server
on the secondary site.
----End
Result
After the preceding operations are performed, the license file is automatically loaded to the /opt/
U2000/server/etc/conf/license path.
1.18.4 Checking the Status of the U2000 License

This topic describes how to check the status of the U2000 license. By checking the license status,
you can learn the usage of the license, so as to apply for a new license file from Huawei in time
before the NMS needs to be expanded or the validity of the license is due.
Procedure
1 Log in to the U2000 Client.
2 Choose Help > License Information.
3 In the License Information dialog box that is displayed to view the condition of the license.
----End

1.18.5 Setting the Threshold of the Accessing NEs

When the number of accessing NEs reaches the preset threshold, the U2000 sends an NE license
alarm and displays an Information dialog box periodically.
Procedure
1 Choose Administration > Settings > NE License Alert from the main menu.
2 In the NE License Alarm Setting dialog box, enter the license threshold in License
threshold.
3 Select the Enable license alarm sending check box to enable the function of sending the license
alarms.
4 Select the Enable license timing alarm check box and set the interval of sending the alarms.
5 Click OK.
----End
1.18.6 Verifying the U2000 License

Introduce how to correctly use a U2000 License.
Context
NOTE
Do not modify the name, the content, or the format of the license file. Otherwise the license will be invalid.
If the license file is invalid, follow the procedure described as follows to check the correctness
of the license.
Procedure
l Check the correctness of the license on Solaris.
Check whether the text mode, namely ASCII mode, is adopted to transfer the license file.

NOTE
To check the transfer mode, open the licenseXXXXXXX.dat file at the workstation by the vi
command. If every line is ended with "^M", it indicates that the transfer mode is incorrect, and the
transfer should be repeated in the mode of ASCII.
l Check the correctness of the license on SUSE Linux.
Check whether the text mode, namely ASCII mode, is adopted to transfer the license file.
NOTE
To check the transfer mode, open the licenseXXXXXXX.dat file at the workstation by the vi
command. If every line is ended with "^M", it indicates that the transfer mode is incorrect, and the
transfer should be repeated in the mode of ASCII.
l Check the correctness of the license on Windows.
– Check whether the network adapter is available or not.
If not, the MAC address cannot be detected, and the license will be invalid.
– Check whether there is any error during the transfer of the license.
If yes, re-transfer the license file and store it in the D:\U2000\server\etc\conf\license
directory. Re-activate the U2000 to see whether it is valid.
----End
1.19 Starting the Web Client

Certain NEs must be configured by using the Web LCT. Before you configure services for these
NEs, you need to first start the Web LCT client.
Prerequisite
l You must be an NM user with "NE operator" authority or higher.
l It is applicable to the OptiX OTU40000, OptiX PFE 1670, and OptiX OSN 900A.
Procedure
1 Optional: Double-click an optical NE on the topology. The NE Panel is displayed. Select an
NE from the object tree on the left.
2 Right-click an NE and choose Start WEB Client from the shortcut menu. The Web LCT user
interface is displayed.
----End
1.20 Collecting NE Data

When an NE is faulty, you can collect the NE data for fault identification and analysis. There
are fast fault collection and full fault collection.
Prerequisite
l It is applicable to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.

Procedure
1 In the Main Topology, right-click an NE and choose Collect NE Data from the shortcut menu.
The Datacollector window is displayed.
NOTE
In the Datacollector window, press F1 to display the Online Help topic relevant to data collection
operations and troubleshooting methods of common problems.
----End
1.21 Customizing Naming Rule

When you create fibers or trails, the U2000 automatically creates the names of the fibers, trails,
ASON trails, Tunnel and PWE3 Service based on the naming rule. The settings can be modified
according to actual requirements. This section takes the fiber naming rule as an example to
illustrate how to customize the naming rule.
Context
l Applies to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, and Access series
NEs.
l The naming rule is a string that comprises a series of fields. The U2000 provides some
fields by default. The user can add new fields, modify or delete the existing fields and adjust
the field position according to the actual requirements, to customize the naming rule.

Procedure
1 Choose Administration > Settings > Naming Define Rule from the main menu. The Rule
Naming dialog box is displayed.
2 Choose the fiber or trail which want to be named from the Function Tree of Function
Configuration. The naming rule is displayed on the right-hand pane.
3 Optional: Click Refresh to obtain the latest naming rule customized by other users.
4 Click Create Rule and enter the name of the newly created rule in the first row.
5 Add new fields.
1. Right-click on the Field Description list, and choose Add Field from the shortcut menu
to add a new field.
2. Select the field type in the Type list and define its value.
There are four types of fields.
l Fixed Field: This type of field defines fixed strings contained in all names. Enter the
string in Fixed Field field.
l Connector Field: This type of field defines the connector used in the name. Select the
connector in the Connector Field field.
l Dynamic Field: In this type of field, you can select some attributes of the fiber or cable
and add the value to the name, for example, contain the name of Source NE in the
naming rule. Select the attributes in the Dynamic Field field.
l Digital Field: In this type of field, the numerals contained in the naming rule can be set
to change regularly so that the names of fibers or cables following the same rule is not
repeated. In the Digital Field field, set Current Value, Min. Value, Max. Value and
Step Length.
NOTE
It is recommended that there is only one Digital Field in the naming rule. If there are multiple digital
fields, it is recommended to set others to Fixed Field.
3. Define the field name in the Name list.
4. Define the field length in the Length list.
6 Optional: Delete fields. Select the field to delete in the Field Descriptions list. Right-click it
and choose Delete Field from the shortcut menu.
7 Optional: Set how the field is sequenced in the naming rule. Select the field and click
to move the field forward and click to move it backward.

8 Click Apply to set the current naming rule as the default rule on the client.
9 In the Such As field, you can preview the current naming rule.

10 Click Save to save the current naming rule and set it as the default rule.
11 Click Apply to set whether to apply the current naming rule as the naming rule of the current
client.
----End
1.22 U2000 Process List

This topic describes the information about U2000 processes,such as the functions and dependent
processes of each process and the port occupied by each process.
Table 1-6 shows the description of U2000 services and processes.
Table 1-6 U2000 process list

Process Path Port Requi Protoc Function Description
Name red ol
Proce Type
ss
EmfGnl server/bin None None None General Device Process.

DevDm General device service
provides the function of
managing the third-party
NEs.


Name red ol
Proce Type
ss
StdCltsi server/nemgr/ 9002, BmsT TCP, 112 Test. This process

Dm nemgr_access/bin 9003, est TCP, provides the 112 test.
13027 TCP,
, TCP
13028
LDAPAg server/common/ip/ None sm_ag None LDAP Agent. This

ent dmf/bin ent process provides the IP
LDAP agent service.
snmpserv server/common/ip/ None None None SNMP Service(H3C).

er dmf/bin This process provides the
SNMP forwarding
function of H3C
switches.
DmsBase server/common/ip/ None sm_ag None IP Base Service. This

Dm base/bin ent process provides the
basic IP services, such as
link search, system log,
interface inventory, and
change audit.
DmsIPD server/common/ip/ None sm_ag None IP View Manager. This

m ipview/bin ent,ea process provides the IP
m_age view management
nt service.
DmsBatc server/common/ip/ None None None Batch Config. This

hConfig batchconfig/bin process provides the
Dm function of configuring
NEs in batches.
DmsNet server/common/ip/ None None None NetACL. This process

AclDm netacl/bin provides the function of
configuring the multi-
NE ACL in batches.
QosPolic server/common/ip/ None None None Qos Manager. This

yDm qos/bin process provides the QoS
management function.
VasDiag server/common/ip/vas/ None sm_ag None Test and Diagnoisi

Dm bin ent Manager. This process
provides the test
diagnosis function.


Name red ol
Proce Type
ss
DeployD server/common/ip/ None None None Deployment Manager.

m deployment/bin This process provides the
deployment center
function.
GctlDm server/common/ip/ None eam_a None General Configuration

gctl/bin gent Template. This process
provides the general
configuration template
function.
gcli server/common/ip/ 13003 None TCP, IP Graphic CLI. This

guicli/bin , TCP process provides the
13004 switch and router GCL
function.
nemgr_pt server/nemgr/ 11000 Eml_P TCP, PTN NE Manager. This

n nemgr_ptn/bin ~111 ubSvr UDP process provides the
00, function of managing
35600 Metro Ethernet PTN
~356 frame-shaped and
54 caseshaped NEs.
BoxSW server/nemgr/ None eam_a None Switch NE Manager

MgrDm nemgr_switchmgr/ gent (Box). This process
switchmgr_box/bin provides the function of
managing Quidway
case-shaped switches.
FrameS server/nemgr/ None eam_a None Switch NE Manager

WMgrD nemgr_switchmgr/ gent (Frame). This process
m switchmgr_frame/bin provides the function of
managing Quidway
frame-shaped switches.
itnotify server/server/nbi/ 12002 None TCP, CORBA Notify Service

corba/bin , TCP (Orbix). This process
22002 provides the CORBA
NBI management
service (Orbix).
Agent_C server/server/nbi/ 12003 None TCP, CORBA Service. This

ORBA corba/bin , TCP process provides the
22003 CORBA NBI
management service.
xmlagent server/server/nbi/xml/ 443, None TCP, XML Service. This

bin 9997, TCP, process provides the
XML NBI management
443 TCP service.


Name red ol
Proce Type
ss
RouterM server/nemgr/ None eam_a None Router NE Manager.

grDm nemgr_router/ gent This process provides the
routermgr/bin function of managing
Quidway routers.
SGMgrD server/nemgr/ None eam_a None Service Gateway

m nemgr_router/sgmgr/ gent Manager. This process
bin provides the function of
managing Quidway
service gateways.
Security server/nemgr/ None eam_a None Security NE Manager.

MgrDm nemgr_securitymgr/ gent This process provides the
bin function of managing
FW/USG, SIG, and SVN
series security
equipment.
secpolicy server/vsm/ None None None Policy Manager. This

mgr secpolicymgr/bin process provides the
functions such as
centralized policy
configuration and attack
defense configuration.
secvpnm server/vsm/ None None None VPN Manager. This

gr secvpnmgr/bin process provides the
IPSec/L2TP VPN
Eml_We server/server/common/ 11000 Eml_ TCP, WEB LCT Service. This

bLCTSvr trans_core/bin ~111 monito TCP process provides the
00, mcat function of managing
8250 Web LCT NEs.
Nml_aso server/nml/ason_otn/ None Eml_P None OTN ASON Network

n_otn bin ubSvr Manager. This process
provides the OTN ASON
network management
function.
Nml_aso server/nml/ason_sdh/ None Eml_P None SDH ASON Network

n_sdh bin ubSvr Manager. This process
provides the SDH ASON
network management
function.


Name red ol
Proce Type
ss
Eml_mm server/mml/bin 15000 None TCP, MML Service. This

l , TCP process provides the
15001 MML NBI service.
nemgr_e server/nemgr/ 11000 Eml_P TCP, EXT NE Manager. This

xt nemgr_ext/bin ~111 ubSvr UDP process provides the
00, function of managing the
35600 OSN900A and
~356 OTU40000.
54
nemgr_m server/nemgr/ 11000 Eml_P TCP, MARINE NE Manager.

arine nemgr_marine/bin ~111 ubSvr UDP This process provides the
35600 submarine cable series
~356 equipment.
54
nemgr_n server/nemgr/ 11000 Eml_P TCP, OTN(TL1). This process

aotn nemgr_naotn/bin ~111 ubSvr UDP provides the function of
00, managing North
35600 America OTN series
~356 equipment.
54
nemgr_n server/nemgr/ 11000 Eml_P TCP, WDM(TL1). This

awdm nemgr_nawdm/bin ~111 ubSvr UDP process provides the
35600 North America WDM
~356 series equipment.
54
nemgr_ot server/nemgr/ 35600 Eml_P UDP OTN NE Manager. This

n nemgr_otn/bin ~356 ubSvr process provides the
54 function of managing
OTN series equipment.
nemgr_rt server/nemgr/ 11000 Eml_P TCP, RTN NE Manager. This

n nemgr_rtn/bin ~111 ubSvr UDP process provides the
35600 RTN series equipment.
~356
54


Name red ol
Proce Type
ss
nemgr_s server/nemgr/ 11000 Eml_P TCP, SDH NE Manager. This

dh nemgr_sdh/bin ~111 ubSvr UDP process provides the
35600 SDH/MSTP/OSN series
~356 equipment.
54
nemgr_w server/nemgr/ 11000 Eml_P TCP, WDM NE Manager. This

dm nemgr_wdm/bin ~111 ubSvr UDP process provides the
35600 LHWDM/Metro WDM
~356 series equipment.
54
Eml_Pub server/common/ 1500 lic_ag UDP Transmit Common

Svr trans_core/bin ent,mc Service. This process
inter-NE management on
transferdomain NEs and
reports.
Eml_Perf server/common/ None Eml_P None Transmit Performance

Svr trans_core/bin ubSvr Service. This process
provides the transfer-
domain performance
profile server/common/frame/ None None None Global Profile Manager.

profile/bin This process provides the
profile management
function.
itm_agen server/bin 31015 None TCP, Integrated Task

t , TCP Management. Provides
31065 the functions of
integrated task
management.
lic_agent server/bin 31001 None TCP, License Process. A

, TCP service interface is
31051 provided to check the
validity of the license file
of the current version
imap_sys server/bin 31003 None TCP, System Monitor.

monitor , TCP Provides service to
31053 monitor the process of
the system


Name red ol
Proce Type
ss
log_agen server/bin 31005 None TCP, Log/Syslog/Access

t , TCP, Device Log Process.
31055 This process provide the
TCP, functions as follow: 1.
,
TCP Records the system logs.
31006 It receives, manages, and
, stores the system logs of
31056 other processes through a
port 2. Syslog
forwarding service is
used to forward the
iMAP logs to the third-
party Syslog Server
based through the BSD
Syslog protocol 3.
Provides the
management of access
NES device log
sm_agent server/bin 31008 lic_ag TCP, Security Process.

, ent TCP Provides the functions of
31058 managing network
management system
(NMS) users, NMS user
rights, and NE user
rights.
tm_agent server/bin 31010 None TCP, Topo Process. Provides

, TCP the functions of
31060 integrated task
management.
ifms_age server/bin 31011 None TCP, Fault Process. Collects

nt , TCP and saves the alarm
31061 information from the
managed devices
through the NE engine. It
also provides the
function of querying and
analyzing the alarm
information.


Name red ol
Proce Type
ss
snmp_ag server/bin 31012 None TCP, SNMP Service. Provides

ent , TCP, the northbound interface
31062 which adopts the SNMP
TCP, protocol.
,
UDP,
982,
UDP
9812,
9813
manager server/bin 31013 None TCP, System Service.

_agent , TCP Provides the
31063 management interface
for network management
system (NMS) version
information, including
querying the version
information of the
operating system,
checking the software
version of the client,
querying the software
version of the server and
client, and querying the
upgrade information of
the client.
porttrunk server/bin 31035 None TCP Port Trunk Service . The

_agent port trunking service is
used to have the ports of
independent services
converge at one port.
CAU server/bin None None None Client Auto Upgrade

Service. Provides Client
Auto Upgrade Service


Name red ol
Proce Type
ss
ds_agent server/bin 31037 None TCP, Desktop Service

, TCP, Process. The DS
31038 provides data
TCP, presentation and
,
TCP, operation services on
31039 various types of client
, TCP
interfaces, such as Java
31040 GUI and Web. If
, multiple DSs are
31041 deployed, they reduce
~310 the pressure of the server
50 for connecting to a large
number of clients.
eam_age server/bin 31036 None TCP, EAM Process. EAM

nt , TCP Maintains a global NE
31086 list in network
management.
JMSServ server/bin 8161, None TCP, JMS Service

er 61616 TCP, (ActiveMQ). The Thrid
, Software, JMS(Java
TCP Message Service)
61617
bmsmoni server/nemgr/ 12216 None TCP Acccess Apache Service.

apache nemgr_access/bin This process provides the
function of monitoring
the Apache service
status.
BmsHG server/nemgr/ None None None HGMP Manager

MPDm nemgr_access/bin Process. HGMP
manager service
managing HGMP
EmfTrap server/bin 161, None UDP, Trap Receiver Process.

Receiver 11101 TCP, This Trap Receiver
~111 receives the Trap
UDP messages sent to the
04,
server through SNMP.
32162
EmfProj server/bin None None None Project Document

DocDm Process. Provide the
function of exporting the
project data of the
network management
system.


Name red ol
Proce Type
ss
Notify_S server/bin 12002 None TCP, CORBA Notification

ervice , TCP Service(TAO). CORBA
22002 notification service
Naming_ server/bin 12001 None TCP, CORBA Naming

Service , TCP Service(TAO). CORBA
22001 naming service
HedExSe server/bin None None None Help Process. Provides

rvice help document.
BmsAtur server/nemgr/ None ifms_a None Access Device ATUR

nemgr_access/bin gent,m Manager. This process
c provides the xDSL
terminal management
service.
BmsCom server/nemgr/ None ifms_a None Access Device Common

mon nemgr_access/bin gent,m Service. This process
c provides licnese, task
scheduling,etc.
management of the
access domain.
BmsGdm server/nemgr/ None ifms_a None Access Device Manager.

nemgr_access/bin gent,m This process provides the
c equipment management
of the access domain.
BmsProfi server/nemgr/ None mc None Access Device Profile

le nemgr_access/bin Manager. This process
provides the profile
service management of
the access domain.
BmsPvc server/nemgr/ None ifms_a None Access Device PVC

nemgr_access/bin gent,m Service Manager . This
c process provides the
PVC,ServicePort service
management of the
access domain.
BmsRack server/nemgr/ None mc None Access Device Rack

nemgr_access/bin Manager. This process
provides rack
management of the
access domain.


Name red ol
Proce Type
ss
BmsServ server/nemgr/ None ifms_a None Access Device

ice nemgr_access/bin gent,m Generated Service
c Manager. This process
provides
IGMP,VLAN,Voice,Eth
ernet
port,Protocol,etc.man-
agement of the access
domain.
BmsTest server/nemgr/ None ifms_a None Access Device Line Test.

nemgr_access/bin gent,m This process provides
c line test of the access
domain.
BmsTimi server/nemgr/ None mc None TL1 Timing Task

ngTask nemgr_access/bin Manager. This process
provides TL1 timing task
management.
bmsXdsl server/nemgr/ None ifms_a None Access Device xDSL

nemgr_access/bin gent,m Service Manager. This
xDSL service
management service.
BmsXpo server/nemgr/ None ifms_a None Access Device xPON

n nemgr_access/bin gent,m Service Manager. This
xPON service
management service.
cltsi server/nemgr/ 8888 BmsT TCP 112 Test(CLTSi). This

nemgr_access/bin est process provides the
CLTSi 112 test.
inTL1NB server/nemgr/ 9820 mc TCP TL1 Proxy Inner

iDm nemgr_access/bin Interface. This process
provides the XML NBI
Proxy,Service
Provisioning Profile
management.
TL1NBi server/nemgr/ 9819 lic_ag TCP TL1NBiDm Process.

Dm nemgr_access/bin ent,mc This process provides
TL1 NBI Management
service.


Name red ol
Proce Type
ss
CFMSiD server/nemgr/ 8001, None TCP, Customer Feature

m nemgr_access/bin 9001 TCP Management NBI. This
process provides
Customer Feature
Management NBI
service.
DSLMgr server/nemgr/ None mc None Port Conformity

Dm nemgr_access/bin Statistics. This process
provides port conformity
statistics of the access
domain.
lte_agent server/bin 31033 lic_ag TCP, Common License

, ent TCP Process. A service
31083 interface is provided to
manager the ne license.
BmsPon server/nemgr/ 13027 mc TCP Access PON TL1

EmsTL1 nemgr_access/bin Processs. This process
provides PON TL1
Management service.
U2560W server/nemgr/ None None None WLAN Equipment

LANDm nemgr_cnm/bin Management Service.
This process provides
WLAN device
management of customer
network devices.
U2560T server/nemgr/ None None None TR069 Terminals

R069Dm nemgr_cnm/bin Management Service.
This process provides
TR069 teminals
network devices.
U2560Co server/nemgr/ None None None Customer Network

mmonD nemgr_cnm/bin Device Common
m Service. This process
provides license, poll
manage, etc.
network.
trapdispa server/common/ 162 ifms_a UDP Trap Dispatcher. Provide

tcher trapdispatcher/bin gent trap receiving and
dispatching function


Name red ol
Proce Type
ss
TrapRece server/bin 11101 None TCP Default Trap Receiver.

iver ~111 Receive the trap reported
04 from network elements,
mainly for the SNMP
interface device.
EmfTrap server/bin 11101 None TCP Extended Trap Receiver.

Receiver ~111 Receive the trap reported
1 04 from network elements,
as the extension of
default Trap Receiver,
SNMP interface device
used.
datacolle server/tools/ None None None Data Collector Process.

ctorsvr datacollector/bin The Datacollector is
mainly used for
collecting the complete
and correct fault data in
case of NE failure and
helps to locate faults
quickly
neproxy server/tools/ None None None DataCollector Neproxy

datacollector/bin Process. DataCollector
Neproxy Process
PnpMgr server/common/ 67 None UDP Automatic NE

DM pnpmgr/dhcp/bin Configuration. This
process provides router
automatic NE
configuration function
Diagnose server/common/ipda/ None None None Fault Diagnose

Controlle controller/bin Controller Process.
r Provide fault diagnose
function of Access
network and PTN
network


Name red ol
Proce Type
ss
DCServe server/common/dc/bin 21, None TCP, DC. This process

r 69, TCP, provides the function of
NE software
22, TCP, management and disaster
22, TCP, recovery management.
69, TCP, The detailed functions
are NE software upgrade,
21 TCP patch installation, data
backup and recovery for
disaster recovery, and
plug-andplay automatic
upgrade of case-shaped
equipment.
toolkit server/common/dc/ 8999, None TCP, Toolkit. This process

toolkit/server 13006 TCP provides the service of
upgrading boardlevel
transmission equipment.
Enpower server/common/env/ None itm_ag None Access environment and

Dm bin ent power monitor. This
process provides the
function of centralized
monitoring on the access
NE environment status
and the power supply
status.
PMDataS server/common/pms/ None None None Remote Data

ynchroni bin Synchronizer. This
zer process provides the
function of importing
data in text files.
PMSDm server/common/pms/ None None None Performance Service.

bin This process provides the
collector management
function.
PQMDm server/common/pms/ None Eml_ None Group Monitor. This

bin monito process provides the
mcat function of grouping
performance monitoring
and display.


Name red ol
Proce Type
ss
TXTNBI server/common/pms/ 21 None TCP Text Export. This

Dm bin process provides the NBI
function. It is used to
transmit performance
data in the text format
through FTP.
BulkColl server/common/ None None None Bulk Collector. This

ectorDm pmscollector/bin process provides the
function of collecting
performance data in
batches.
SNMPCo server/common/ None None None SNMP Collector. This

llectorD pmscollector/bin process provides the
m function of collecting
performance data
through SNMP.
XftpDm server/common/xftp/ None None None XFTP. This process

bin provides the function of
setting XFTP connection
parameters.
SyslogCo server/common/ 514 None UDP System Log Collector.

llectorD devicelog/bin This process provides the
M function of collecting NE
operation and running
log data, and managing
files.
inventory server/common/ None None None Inventory Manager. This

dm inventory/bin process provides the
inventory data
management function,
such as physical resource
management, cable
management, and
customer management.
Nmslogzi server/common/ None None None Zip Server. This process

pDm unitedmgr/bin provides the function of
compressing NMS files.


Name red ol
Proce Type
ss
UniteUitl server/common/ 13005 None UDP United Manager. This

DM unitedmgr/bin process provides the
basic functions, such as
importing and exporting
scripts, managing NE
time, synchronizing
NEs, and managing NE
objects, of the inter-
domain universal NMS.
Nml_co server/nml/ None None None Network Common

mmon nmlcommon/bin Service. This process
provides the E2E
common management
service. The other E2E
processes all depend on
this process.
Nml_cps server/nml/nmlcps/bin None None None Composite Service

Manager. This process
provides the composite
service management
function.
Nml_eth server/nml/nmleth/bin None Nml_c None MSTP ETH and ATM.

ommo This process provides the
n MSTP ETH/ATM E2E
management service.
Nml_ip server/nml/nmlip/bin None None None IP Service Manager. This

process provides the IP
E2E management
service.
Nml_otn server/nml/nmlotn/bin None Nml_c None OTN Network Manager.

ommo This process provides the
n OTN E2E management
service.
Nml_sdh server/nml/nmlsdh/bin None Nml_c None SDH Network Manager.

ommo This process refers to the
n Web service process. It
provides Web services.


Name red ol
Proce Type
ss
Nemgr_v server/nemgr/ 13001 None TCP, Router NE Manager

mf nemgr_vmf/bin , TCP, (VRP V8). This process
21, provides the function of
TCP, managing V8 routers
22, TCP, equipment.
9801, TCP
8099
Eml_mo common/Tomcat/bin None None None Tomcat Service. This

nitomcat process provides the
function of monitoring
the Tomcat service
status.
mc server/common/frame/ None None None Distribution Manager.

mc/bin This process provides the
basic NE distribution
service.
dam server/common/frame/ None None None Device Access Manager.

dam/bin This process provides the
function of creating
SNMP equipment.
1.23 Rules for Entering Information on User Interface

This topic describes the rules for entering information on the user interface. These rules specify
the typing requirements for the text boxes in the U2000 operation interface. These text boxes
are used to enter character strings, file names, IP addresses, MAC addresses, numerals,
passwords, dates, time, and so on.
Types of Character Strings

The character string is a kind of descriptive text and usually there is no limitation for the
characters typed in. But, when you enter the names in the U2000 (including the names of the
PDH path, MSTP path, NE, subnet, virtual NE board, equipment room, subrack, cabinet,
Transmission NM, optical fiber, NE user, protection subnet, circuit, logical system, J0, J1, PM
(C)U relay, DIP switch, EMU input and output paths and Ethernet user) and all remarks, or when
some functions involve typing in characters that are subject to naming rules, you are
recommended to use the standard characters listed as follows:
l Languages used in nine countries, namely, China, America, Italy, Spain, France, UAE,
Germany, Russia, and Portugal.
l Input of various types of characters.

NOTE
l The name of a rule, trail, fiber, subnet, or customer can contain "+" and ":",
l A subnet name can contain "+".
l The Tab key input cannot be contained in the above names or the values of overheads J0, J1, and J2.
l These rules are made in order to avoid database operation errors or errors occurred when an HTML
report is generated. The Tab key input cannot be contained in command lines.
CAUTION
When you enter characters in Microsoft Pinyin IME and keep pressing a key, too many characters
will be typed in. This leads to the exit of the U2000 client.
Directory
l When files are transfered between different OSs, both chinese and english directories are
supported.
l When performance data is dumped at the server end, both chinese and english directories
are supported. In other cases, only english directories are supported.
File Name
The general rule is file name + extension name. The extension name consists of letters, numerals
or underscores, and should not exceed three characters.
The naming rule is that a file name consists of letters, numerals or underscores. It cannot exceed
eight characters. A file name cannot contain spaces or any of the following characters: \ " . * ;
> [ ] ( ) ! $ { } < >. If you need to separate two characters, you may use "_".
Nine languages are supported, with each language corresponding to a naming rule.
Folder Name Language
zh_CN China
en_US America
it_IT Italy
es_ES Spain
fr_FR France
ar_SA Saudi Arabia
de_DE Germany
ru_RU Russia
pt_PT Portugal

IP Address
The IP address is decimal, for example, 129.9.0.254:9801 (9801 is the port ID, and can be
omitted).
MAC Address
The MAC address is hexadecimal, for example, 00-06-5B-84-50-84.
Types of Numerals
Integer type: In this mode, only integral numbers can be typed in.
Decimal fraction type: In this mode, besides numerals, characters f and e, as well as the decimal
point are allowed.
Password
When the password is entered, "*" is present in the password box instead of the actual characters
entered.
Date and Time

Generally, the date and time can be selected from or typed in the Time/Date Attribute dialog
box.
To navigate to the window for customizing the type of the date and time, choose File >
Preferences > Region Settings from the Main Menu and click the Time or Date tab.
The default format of time and date is as follows:
l Time: 16:06:06 (Hour:Minute:Second)
l Date: 2000-06-06 (Year-Month-Day)
1.24 Mutual Exclusion List for Multiclient Operations

The mutual exclusion list for multiclient operations is given below.

Figure 1-15 Mutual exclusion list for multiclient operations

Figure 1-16 Mutual exclusion list for multiclient operations on ASON SDH trails
Figure 1-17 Mutual exclusion list for multiclient operations on ASON WDM trails

Example
The "script import" and "upload" operations are mutually exclusive. If "script import" is being
performed on one client, "upload" cannot be performed on another client.

Operation Guide for Common Features 2 Network Management Process
2 Network Management Process
About This Chapter
This topic describes the process of managing network equipment on the U2000.
2.1 Access Network Management Process
This topic describes the operation tasks of managing an access network with the U2000 and the
relations between these operation tasks.
2.2 MSTP Network Management Process
The MSTP network management process describes the operation tasks of managing a MSTP
network by using the U2000, and the relations between the operation tasks.
2.3 WDM Network Management Process
The WDM network management process describes the operation tasks of managing a WDM
2.4 RTN Network Management Process
The RTN network management process describes the operation tasks of managing a RTN
2.5 PTN Network Management Process
The PTN network management process describes the operation tasks of managing an PTN
2.6 Security Equipment Network Management Process
This topic describes the operation tasks of managing a security equipment network with the
U2000 and the relations between these operation tasks.
2.7 Router Network Management Process
This topic describes the operation tasks of managing a router network with the U2000 and the
2.8 Switch Network Management Process
This topic describes the operation tasks of managing a switch network with the U2000 and the

2 Network Management Process Operation Guide for Common Features
2.1 Access Network Management Process

This topic describes the operation tasks of managing an access network with the U2000 and the
It is recommended that you configure and manage an access network in accordance with the
flowchart shown in Figure 2-1.

Figure 2-1 Flowchart of managing an access network
Feature Network Bulk network

Network deployment configuration maintenance configuration
Topology Device Alarm FTTx pre-

management management management deployment
General Interface Inventory

configuration management management
template
Ethernet feature Performance
management management
Ethernet OAM NE software

GPON Test diagnosis

management
EPON
management
xDSL management
Multicast
management
TDM management
VoIP management
PWE3
management
ACL management
BFD management
QoS management
DHCP Relay
management
MSTP
management
The horizontal direction of the flowchart shows the primary stages of managing an access
network with the U2000, which include:
l Network deployment

l Feature configuration
l Network maintenance
l Bulk network configuration
The vertical direction of the flowchart shows the relations between the operation tasks of these
stages.
2.2 MSTP Network Management Process

The MSTP network management process describes the operation tasks of managing a MSTP
Configure and manage the MSTP network by referring to the processes as shown in Figure
2-2.
Figure 2-2 MSTP network management process

Configuring Configuring SDH ASON
Deploying a Maintaining a Configuring End-
Services on a Feature Feature
Network Network to-End Services
Per-NE Basis Management
Configuring Configuring Managing the

Topology Customer Configuring
SDH Services QOS Optical Power
Management Management SDH ASON
Networks
Configuring Configuring Alarm Manage SDH
DCN Ethernet LPT Management Protection
Management Services Routine
Subnet
Maintenance
Configuring Performance
Configuring the Configuring RPR for an ASON
LCAS Management Manage SDH
NE Time Services Network
Trail
Configuring Configuration
Configuring Configuring QinQ Service Data Handling
Clocks ATM Services Management ASON Network
Failures
Configuring Software
Configuring Configuring STP and RSTP Management
Orderwire DDN Services
Configuring
Report
Configuring IGMP Snooping
Configuring Management
Protection
SAN Services
Configuring Configuring
Configuring LAG/DLAG The Ethernet
Board Configuring Port OAM
Parameters Broadcast Data
Port Services Configuring
Configuring
BPS/RPS
Ethernet
Configuring F1 Service OAM
Data Port
Services Configuring
SNCTP Configuring
Data Test
Configuring Frame
Built-in WDM Configuring
Transmux
Configuring
BPS/RPS/
Configuring PRBS
TCM
Adjusting
Configuring Networks
AU3
Configuring
IPA

The landscape orientation of the configuration flow chart shows the main phases of managing
the MSTP network by using the U2000. The phases include network deployment, service
configuration, network maintenance, and SDH ASON feature management. In the case of the
service configuration, the end-to-end service configuration mode requires a license that supports
the end-to-end SDH management, and the SDH ASON feature management requires a license
that supports the SDH ASON feature.
The portrait orientation of the flow chart shows the relations between operation tasks in each
phase.
2.3 WDM Network Management Process

The WDM network management process describes the operation tasks of managing a WDM
Configure and manage the Metro WDM&LH WDM network by referring to the processes as
shown in Figure 2-3.
Figure 2-3 Metro WDM&LH WDM network management process

Deploying a Configuring Maintaining a
Configuring Services
Network WDM Features Network
Configuring Services Configuring End-

Creating a Configuring Managing the
Network on a Per-NE Basis to-End Services ROADM Optical Power
Configuring Optical Customer Alarm

Configuring DCN Cross-Connections Management Configuring IPA Management
Configuring WDM Manage WDM

Configuring the Performance
Services Protection Configuring ALC
NE Time Management
Subnet
Configuration
Configuring Configuring Manage WDM Data
Clocks Overhead Trail Configuring APE
Management
Configuring Configuring Software

Ethernet Services Configuring
Orderwire Management
EAPE
Configuring
Configuring Broadcast Data Configuring Fiber Report
Board Port Services Link Check Management
Parameters
Configuring F1 Data
Configuring
Port Services
Protection
For the detailed process for managing the OptiX OSN 6800, refer to Figure 2-4.
NOTE
The procedure for managing the OptiX OSN 3800 is similar to the procedure for managing the OptiX OSN
6800.
For the detailed process for managing the OptiX OSN 6800A, refer to Figure 2-4.
NOTE
The procedure for managing the OptiX OSN 3800A is similar to the procedure for managing the OptiX
OSN 6800A.

Figure 2-4 OptiX OSN 6800OptiX OSN 6800A equipment management process
WDM ASON
Deploying a Configuring Maintaining a Feature
Network WDM Features Network Management
Creating a Services on a Per- End-to-End Configuring Managing the Configuring WDM
Network NE Basis Services ROADM Optical Power ASON Networks
Configuring Routine
Configuring Optical Cross- Customer Alarm
Management Configuring IPA Maintenance for an
DCN Connections Management
ASON Network

Configuring the Configuring Performance Handling ASON
Services Protection
NE Time ALC Management Network Failures
Subnet
Configuration
Configuring Configuring Manage WDM Configuring Data
Clocks Overhead Trail APE Management

EAPE
Configuring Report
Board Management
Parameters
Configuring
Protection

Network WDM Features Network
Creating a Services on a Per- End-to-End Configuring Managing the
Network NE Basis Services ROADM Optical Power
Configuring
Configuring Optical Cross- Customer Alarm
Management Configuring IPA Management
DCN Connections

Configuring the Configuring Performance
Services Protection
NE Time ALC Management
Subnet
Configuration

Board Management
EAPE
Parameters
Report
Configuring
Management
Protection
For the detailed process of managing the OptiX OSN 8800 series equipment, see Figure 2-5.
NOTE
The OptiX OSN 8800 T32 V100R001 does not support orderwire and Ethernet service configuration.
The OptiX OSN 8800 T32 V100R002 or a later version supports the SDH-related functions, including
configuring SDH protection, SDH features, and SDH-ASON feature management.

Figure 2-5 OptiX OSN 8800 series equipment management process

WDM ASON SDH ASON
Deploying a Configuring Configuring Maintaining a Feature Feature
Configuring WDM Services
Network WDM Features SDH Features Network Management Management
Creating a Services on a Per- End-to-End Configuring Configuring Managing the Configuring WDM Configuring SDH
Network NE Basis Services ROADM SDH Services Optical Power ASON Networks ASON Networks
Configuring Routine Routine

Configuring Optical Cross- Customer Configuring Alarm
Management Configuring IPA Management Maintenance for an Maintenance for an
DCN Connections Overhead ASON Network ASON Network

Configuring the Configuring Performance Handling ASON Handling ASON
Services Protection Configuring
NE Time ALC Management Network Failures Network Failures
Subnet Ethernet Services
Configuration

EAPE
Configuring Report
Board Management
Parameters
WDM Protection SDH Protection
For the detailed process for managing the OptiX OSN 1800, refer to Figure 2-6.
For the detailed process for managing the OptiX OSN 1800(NA), refer to Figure 2-6.
Figure 2-6 OptiX OSN 18001800(NA) equipment management process
Deploying a Maintaining a
Network Network
Creating a Services on a Per- End-to-End Managing the
Network NE Basis Services Optical Power
Configuring Configuring WDM Customer Alarm

DCN Services Management Management
Manage WDM
Configuring the Configuring Performance
Protection
NE Time Overhead Management
Subnet
Configuration
Configuring Manage WDM Data
Clocks Trail Management
Configuring Software
Board Management
Parameters
Configuring Report
Protection Management
the WDM network by using the U2000Web LCT. The phases include network deployment,

service configuration, WDM feature configuration, network maintenance, and WDM ASON
feature management. In the case of the service configuration, the end-to-end service
configuration mode requires a license that supports the end-to-end WDM management, and the
WDM ASON feature management requires a license that supports the WDM ASON feature.
The WDM ASON feature is unique to the NG WDM. An NG WDM NE can use the WDM
ASON feature management function only after the WDM ASON feature is enabled.
phase.
2.4 RTN Network Management Process

The RTN network management process describes the operation tasks of managing a RTN
Configure and manage the RTN network by referring to the processes as shown in Figure 2-7.
Figure 2-7 RTN network management process

Deploying a Maintaining a Configuring End-
Services on a Feature
Network Network to-End Services
Per-NE Basis
Topology Configuring Alarm

Configuring IF Customer
Management Radio Links Management
Protection Management
Performance Manage RTN

DCN Configuring Configuring
Management Protection
Management SDH Services ATPC Subnet
Configuration
Configuring the Configuring Data
Configuring Manage RTN
NE Time Ethernet Management
XPIC Trail
Services
Software
Configuring
Configuring Configuring Management
Clocks
DDN Services Hybird/AM
Configuring Report
Orderwire Configuring Management
Configuring
Broadcast Data
QOS
Port Services Configuring
Configuring The Ethernet
Protection Configuring F1 Configuring Port OAM
Data Port LPT
Services
Configuring
Board Configuring
Parameters QinQ Service
Configuring
LAG
the RTN network by using the U2000. The phases include network deployment, service
configuration, and network maintenance. In the case of the service configuration, the end-to-end
service configuration mode requires a license that supports the end-to-end RTN and SDH
management.

phase.
2.5 PTN Network Management Process

The PTN network management process describes the operation tasks of managing an PTN
Configure and manage the PTN network by referring to the processes as shown in Figure 2-8.
Figure 2-8 PTN network management process

Services on a End-to-End
Network Feature Network
Per-NE Basis Services
Creating Configuring
Configuring the Configuring Configuring
Network Network Level
Control Plane CES Services the MSTP
Protection
Configuring Configuring Configuring Configuring
OAM
Communicatio MPLS /IP/GRE an ATM the BFD
Tunnel Management
ns Service
Configuring
Configuring Configuring the Configuring Configuring
the LPT
Inband DCN QoS Policy Ethernet Orderwire
Service
Configuring
Configuring Configuring the IGMP
Configuring Port Mirror
the NE Time CES Services Snooping
L3VPN
Service
Configuring Configuring an Common
Clocks ATM Service Maintenance
Operations
Configuring Configuring an
PTP Clock Ethernet
Service
Configuring a
Configuring
TOP Clock
Services for
Configuring the the Offload
Equipment- Solution
Level Protection
Configuring
Interfaces
Hop
Management
the PTN network by using the U2000. The phases include network deployment, service
configuration, configuring feature and network maintenance.
phase.

2.6 Security Equipment Network Management Process

This topic describes the operation tasks of managing a security equipment network with the
U2000 and the relations between these operation tasks.
It is recommended that you configure and manage a security equipment network in accordance
with the flowchart shown in Figure 2-9.
Figure 2-9 Flowchart of managing a security equipment network
Network Feature Network Security Bulk network

deployment configuration maintenance service configuration
IPSec end-to- Centralized

Topology Device Alarm end service
management management management security policy
management configuration
Remote
Interface Inventory
management management access service
management
Ethernet
Performance
feature
management
management
Single-point
NE software
Web management
configuration
iWeb report
management
The horizontal direction of the flowchart shows the primary stages of managing a security
equipment network with the U2000, which include:
l Security service
stages.
2.7 Router Network Management Process

This topic describes the operation tasks of managing a router network with the U2000 and the

It is recommended that you configure and manage a router network in accordance with the
Figure 2-10 Flowchart of managing a router network

Feature Network Bulk network
Network deployment configuration maintenance End-to- end service configuration
Topology NE Alarm
management management management L3VPN Service IP QoS Profile
Cluster Smart Inventory IP Network ACL

management management VPLS Service
configuration tool
Automatic Node Performance

NE Configuration E-AGGR Service IP Multicast Profile
Redundancy management
NE software PWE3 Service

management
Test diagnosis Tunnel
Report Composite Service

management
The horizontal direction of the flowchart shows the primary stages of managing a router network
with the U2000, which include:
l End-to-end service
stages.
2.8 Switch Network Management Process

This topic describes the operation tasks of managing a switch network with the U2000 and the
It is recommended that you configure and manage a switch network in accordance with the

Figure 2-11 Flowchart of managing a switch network
Network deployment Feature Network End-to- end service Bulk network

configuration maintenance configuration
Topology Device Alarm VPN service Network QoS

management management management management configuration
Cluster Interface Inventory LSP service Network ACL

management management management management configuration
Batch Deploy Ethernet feature Performance

Switches management management
Ethernet OAM NE software

NE channel Test diagnosis

management
Route iWeb report

MPLS
management
ACL management
LLDP
management
VRRP
management
BFD management
QoS management
VPN management
...
The horizontal direction of the flowchart shows the primary stages of managing a switch network
with the U2000, which include:
l End-to-end service
stages.

Operation Guide for Common Features 3 Security Management
3 Security Management
About This Chapter
Security management is a crucial function to prevent unauthorized logins and ensure network
data security. Security management includes the NM user management, NE user management,
and security log management.
3.1 Security Management Strategy
The security management function provides the management for the U2000 and NEs. With this
function, the U2000 can also monitor in real time the users that already log in to the U2000 and
NEs. In this way, the network and data security ensures that login failures or illegal operations
are captured.
3.2 Setting Security Policies of U2000 Users
A user of the SMManagers group can set the password policy and account policy of the
U2000 user, to enhance the security.
3.3 Creating U2000 Users and Assigning Permissions
This topic describes a user of the SMManagers group to create U2000 users and assign rights
to them.
3.4 Comparing the U2000 User Rights
By comparing the rights of two U2000 users, a user of the SMManagers group can understand
the differences between their rights.
3.5 Querying the Authorization
In the U2000, a user of the SMManagers group can query the users or user groups that certain
operation rights are assigned to.
3.6 Modifying a U2000 User
This topic describes a user of the SMManagers group to modify the password, general properties,
managed domain, and operation rights of the U2000 user.
3.7 Managing U2000 Object Sets
This topic describes a user of the SMManagers group to create, modify, and delete object sets.
3.8 Managing U2000 Operation Sets
This topic describes how to create, modify, and delete operation sets.
3.9 Monitoring a U2000 User

3 Security Management Operation Guide for Common Features
This topic describes how to monitor U2000 user sessions and operations, force U2000 users to
exit, unlock U2000 user accounts and send messages to online users.
3.10 Managing the Remote Maintenance User
The U2000 remote maintenance function allows login to the U2000 server from a remote
maintenance terminal. Strict management for the remote maintenance user not only ensures
U2000 system security, but also makes maintenance operations easier.
3.11 Managing NE Users
To ensure NE data security, you can manage the authorities and passwords for NE users.
3.12 Managing NE Login
To ensure NE data security, you can manage the users who are logged in to NEs.
3.13 Setting the Security Access of an NE
To ensure the NE security, you need to disable the unused interfaces on the NE.
3.14 Setting the NE ACL
You can ensure the security of NEs by setting the NE ACL.
3.15 RADIUS Configuration
Remote authentication dial in user service (RADIUS) is the industrial standards. RADIUS
provides the authentication and accounting functions for the remote access to a network or dialup
access to a network.
3.16 Auditing Changes
If changes occur on a device in the network, you can query information about the changes through
U2000.
3.17 NE License Management
By using the NE license management function, you can query, apply for, install, and change NE
licenses. In addition, you can adjust capacities in licenses. By setting licenses for NEs, you can
obtain the rights to use certain functions according to service requirements. Because licenses
control NE validity periods or functions, you can understand the NE status in real time and
perform operations properly by using the license management function. Currently, only certain
versions of the OSN equipment, NG WDM equipment, OptiX PTN 910, and OptiX PTN 950
support this function.

3.1 Security Management Strategy

The security management function provides the management for the U2000 and NEs. With this
function, the U2000 can also monitor in real time the users that already log in to the U2000 and
NEs. In this way, the network and data security ensures that login failures or illegal operations
are captured.
The U2000 security management includes NM user management, NE user management, NM
login management, NE login management, and log management. Before using the U2000, you
must create an NM user, and specify what authority the user has, what equipment the user is
able to operate on, and what clients the user is allowed to log in to. If you want to operate on
NEs, you must also create an NE user and assign its authority. With NM user management and
NE user management, the user is only able to perform authorized operations on specified NEs
and through specified clients.
With NM login management, NE login management and log management, the administrator can
monitor in real time the users that already log in to the U2000 or NEs, and force the logged-in
users at any time to log out of the U2000 or NEs.
Figure 3-1 shows the mechanism for implementing security management.
Figure 3-1 Implementation of security management

iManager U2000
Client
NMS User
Management Log Management
NE User DB Security Policy
Management
NE Security
Management
NE User
Management Managed Network and NEs
RADIUS Server
NOTE
For details about the Log management and database security policy, see chapter "Log Management" and
"Backing Up and Restoring the U2000 Database".
3.1.1 User Security Policy

The U2000 security management mainly involves the objects management, password
management, access control management, and role-based and domain-based management.
3.1.2 Log Management Policy
Log security management includes the U2000 operation log, U2000 security log, NE security
log, log dump, and log forwarding management.
3.1.3 Database Security Policy

The U2000 data is saved in the database. Therefore, ensure the database security with priority,
including protecting the security of the database password, backing up the database periodically,
viewing the database status, and dumping the database.
3.1.4 NE Security Management
The NE security management includes NE access control, NE user management, NE operation
right management and NE data security management.
3.1.1 User Security Policy

The U2000 security management mainly involves the objects management, password
management, access control management, and role-based and domain-based management.
Security Management Objects

User: The user name and the password of a U2000 client user uniquely identifies the U2000
management rights entitled to the user. When a user is added to a user group, the user has all the
operation rights of this user group.
l The U2000 provides a default user: admin. It is the super user of the system and has a higher
authority than the system administrator group. You can neither modify the rights of the
user admin, nor add user admin to other user groups.
l The user name assigned to NE Software Management, also called Data Center (DC),
cannot be the same as a user name that is already used to log in to the U2000.
User Group: This is a collection of the U2000 users that have the same management rights. The
attributes of the user groups include general (name, description, user group type, maximum
sessions), members, domain, operation rights and current session.
l The U2000 provides the following default user groups: administrator group, maintenance
group, monitor group, operator group, and SMManager group.
l The administrator group and security administrator group have operation and maintenance
rights for security management, while the other groups do not have security management
rights.
l By default, the maintainer group has the rights of any operation set for maintenance, the
operator group has the rights of any operation set for operation, and the monitor group has
the rights of any operation set for monitoring. The default rights are in the descending
sequence of maintainer group rights, operator group rights, and monitor group rights.
NOTE
You can perform Export operation Sets operation to view detail operation rights.
Object Set: This is a collection of multiple pieces of managed object. Object sets are established
to facilitate the user right management. If a user (or user group) is authorized with the operation
rights of an object set, the user (or user group) can perform all the authorized operations on all
the objects within the object set. This saves you the trouble of setting the management rights for
each NE one by one. Object sets can be created by geographical area, network layer, equipment
type and so on.
Operation Set: This is a collection of client-side operations. Operation sets are established to
facilitate the user right management. Different client-side operations have different impacts on
the system security. Those operations that impose similar impacts on the system security are
allocated to the same operation set. In this way, if a user (or user group) is authorized with the
rights of an operation set, the user (or user group) can perform all the operations in the operation
set. The U2000 has default operation sets. If the default operation sets do not meet the
requirements for the right allocation, you can create new operation sets as required.

Account Policy and Password Policy
Account Policy: The password policy specifies the minimum length of the user name, login
policy, and unlock policy. You can set the account policy to ensure account security.
Password Policy: The password policy specifies the password complexity, update period, and
character restrictions. Using the password policy prevents users from setting a very simple
password or using the same password for a long time.
Client Access Control

Remote Maintenance User Management: The U2000 supports the remote maintenance. It
allows a remote maintenance terminal to log in to the U2000 server to perform operations on
the NEs managed by the U2000. This is a way of maintenance that is commonly used during
the remote equipment fault location and the scheduled check. The remote maintenance user is
the U2000 user that logs in to the U2000 server through the remote maintenance client. By
default, the remote maintenance user is disabled. Before you start the remote maintenance, you
need to enable the remote maintenance user, and set related parameters of the user as required.
SSL Protocol: If the server and the client communicate by the SSL protocol, the data
interchanged between the server and the client is encrypted. In this way, the security of the
network data is guaranteed.
Single-User Mode: If the U2000 switches from the multiuser mode to the single-user mode, all
other users are forced to log out and cannot log in again unless the multiuser mode is enabled.
If no user is logged in under the single-user mode, only the user that has the right of switching
user mode can log in to the U2000.
Client Lockout: To ensure the network security, the U2000 locks out a U2000 client if the user
does not perform any operations on the client for a long time. This operation only locks out the
client, but not affect the normal running of the U2000.
Role-Based and Domain-Based Management

The role-based and domain-based management is based on the allocation of the object set and
operation set. The role-based management function (operation set) enables you to divide the
U2000 rights to different function domains. The domain-based management function (object
set) enables you to construct different network domains in unit of NE. You can easily control
the user rights by entitling the rights of any function domain and network domain portfolio to a
U2000 user.
Usually you can use the following two ways to allocate rights to a user or a user group:
l Add a user to a user group. The user added to the user group enjoys all the rights of the
user group. This way is always used to allocate basic user rights.
l Adjust user rights. Some operation rights can be added or deleted. This way is always used
when the current user or user group does not meet the requirements for the user right.
Operation rights of the default user and user groups be adjusted except admin user,
administrators user group, and SMManager user group.
ACL
The ACL is a secure access control mechanism. It restricts a user to log in to the server through
only the clients with the specified IP addresses.

ACL can effectively control the client IP address from which the user can log in to the U2000.
In this case, even if the user account and the password are obtained by illegal users, these users
cannot log in to the U2000, thus the U2000 security is improved. The U2000 provides two ACLs:
l System ACL
The ACL of the entire U2000. All the users can log in to the U2000 only through specific
IP addresses or network segments.
l User ACL
The ACL of a user. The current user can log in to the U2000 only through specific IP
addresses or network segments.
NOTE
The IP addresses or the network segments for the user ACL need to be within the range of the IP
addresses or the network segments for the system ACL.
Network Management System Maintenance Suite

To ensure the security of the network management system, the password for the network
management system maintenance suite should be modified periodically.

Operation Log and Security Log

Operations and operation results of all the U2000 users are recorded in the U2000 operation log
or security log.
l U2000 operation log: Records user operations irrelevant to the security on the client. For
example, scheduled alarm acknowledgement and NE time synchronization.
l U2000 security log: Records user operations relevant to the security on the client. For
example, creating a user and setting the user operation rights.
The U2000 provides a log browse function. You can also filter logs according to operation user,
operation terminal, log type, severity level, and start and end time.
By querying logs, the administrator can track and check user operations. Pay close attention to
operation logs. This helps you to learn the running information of the system. The logs keep a
record of events relevant to the equipment operations. For example, querying, creating, and
deleting an NE or other objects. The logs also help you to learn the user activities. For example,
you can view operations performed by a user in the system.
NE Security Log
Operations and operation results of all the NE users are recorded in the NE security log. The
U2000 provides an NE log browse function. You can also filter the logs according to the NE
user name, event name, and start and end time. You can view but not delete the NE security log.
Log Dump
By setting the scheduled task dump, you can enable the U2000 to periodically save the log to a
specified directory. This function facilitates log viewing, reduces records in the database, and

speeds up the running of the system. By default, the dump path of the security log is NMS
installation path/server/dump/ThresholdExport/Log. The dumped log can be saved in CSV
or XML format.
Log Forwarding
U2000 log forwarding: The U2000 can forward the U2000 operation log to the Syslog server,
and save all operations. This function provides references for maintenance and relieves the
storage burden of the U2000 server.
NE log forwarding: The U2000 forwards various types of NE information to the Syslog server
in a format that complies with the system log protocol. Network management and maintenance
personnel can learn the NE status according to emergency of the information.
3.1.3 Database Security Policy

The U2000 data is saved in the database. Therefore, ensure the database security with priority,
including protecting the security of the database password, backing up the database periodically,
viewing the database status, and dumping the database.
To ensure the database security, you can take measures as follows:
l To ensure security of the database password, change the password regularly. After the
U2000 is installed, database users sa and NMSuser are automatically created.
l Back up the database periodically. Copy each backup file to other storage devices. In the
case of a U2000 or database fault, you can use the backup database for restoration. In general
situations, do as follows:
– Back up all databases of the U2000 once a week at scheduled time. For details of the
operation method, refer to Periodically Backing Up the U2000 Data to a Local Server
Through the U2000 Client and 10.5.3 Periodically Backing Up the U2000 Data to a
Remote Server Through the U2000 Client.
– Back up the network configuration data of the database by script weekly. For details,
refer to 10.6.3 Backing Up the U2000 Data Through Script Exporting in a
Scheduled Manner.
l View the database status and dump the database periodically.
3.1.4 NE Security Management

The NE security management includes NE access control, NE user management, NE operation
right management and NE data security management.
NE Access Control
LCT Access Control: If you need to use the U2000 LCT or Web LCT for the NE management
and commissioning, you can enable the LCT access control so that the LCT can access the NE.
ACL: The access control list (ACL) provides the basic filtering function for the data flow. All
NEs that have the ACL configured can determine whether to filter out an IP packet when the IP
packet passes the NE. The ACL controls the direction of a specific data flow as to whether the
data flow is transmitted in or out of a network.
Communication Port Access Control: An NE can access the U2000 by using the OAM, COM,
Ethernet port or serial port. You can set the port for the NE access by enabling the access control
of the port. By default, an NE is allowed to access the U2000 by Ethernet ports.

NE User Management
NE User: To ensure the security of the NE data, you must use the previously created NE user
to log in to the NE. Also, you can only perform the operations that are authorized to the NE user.
NE User Level: According to the operation types authorized to a user, the NE users are regarded
as having different operation levels. This level is known as the NE user level. The NE users of
different levels are allocated to different NE user groups.
NE Security Parameters: According to the security settings of the NE, an NE automatically

determines whether the password of the NE user remains valid, and whether the NE user is
allowed to log in. The network manager should know the security settings of the NE, and modify
the password of the NE user before it expires. The NE security parameters include the following:
Allowable Used Times for Outdated Password, Password Max. Valid Period, Password
Min. Valid Period , Password Uniqueness, Lock Testing Time, Allowable illegal Access
Times and Lock Time.
NE Operation Rights
NE Operation Rights: The operation right of NE users has different levels. The user with a
higher right level can perform all operations that are authorized to a user with a lower right level.
For example, the user of the operation level has all the operation rights authorized to the user of
the monitor level. The following describes what operations are authorized to each level.
For Non-NA NEs, the NE user has the following five levels in ascending order: monitor level,
operation level, maintenance level, system level, and debug level. The authorities of the five
user levels are as follows:
l Monitor level: all the query commands, login, logout, password modification
l Operation level: all the fault and performance settings, part of security settings, part of
configurations
l Maintenance level: part of security settings, part of configurations, communication settings,
log management
l System level: all the security settings, all the configurations
l Debug level: all the security settings, all the configurations, debug commands
For the NA NEs, the NE user has the following four levels in ascending order: RTRV, MAINT,
PROV, and SUPER. The authorities of the four user levels are as follows:
l RTRV: This user level has the right to use all query commands, to log in, to log out, and
to change its own password.
l MAINT: This user level has all fault performance authorities, some security authorities,
and some configuration authorities.
l PROV: This user level has some security authorities, some configuration authorities, the
communication setting authority, and the log management authority.
l SUPER: This user level has all security and configuration authorities.
Authority Management: To ensure the security of the NE data, any one who wants to perform
operations for an NE must log in to the NE as an NE user, and can only perform the operations
authorized to this user. It is recommended that you create an NE user before configuring services.
Make sure that when you create a common user account that can be used on all NEs, keep the
right levels consistent to avoid the disorder of user right.

NE Data Backup/Restoration
NE Data Backup: Backing up the NE database is necessary for the daily maintenance. With
the backup of the database, the NE can automatically restore the NE data and run normally in
case the data in SCC is lost or the equipment powers off.
NE Data Restoration: During the daily maintenance, if an NE becomes faulty, the NE data is
restored based on the data backup on the SCC or CF card.
3.2 Setting Security Policies of U2000 Users

A user of the SMManagers group can set the password policy and account policy of the
U2000 user, to enhance the security.
3.2.1 Setting the U2000 Login Mode

The U2000 provides two login modes: multiuser mode and single-user mode. In normal state,
the U2000 runs in multiuser mode. When you need to maintaon the U2000 server (for example,
changing the user group, managed domain, or operation rights of a user), you can set the
U2000 to run in single-user mode to avoid the interference from other users.
3.2.2 Setting the Access Control List
By setting the system or current user access control list (ACL), a user of the SMManagers can
allow the client or user to log in to the U2000 from the computer with specified IP address or
network segment.
3.2.3 Setting the Password Policy
To improve U2000 security, a user of the SMManagers group can set the password policy to
prevent the user from using insecure passwords.
3.2.4 Setting the Account Policy
A user of the SMManagers group can set the account policy to ensure account security.
3.2.1 Setting the U2000 Login Mode

The U2000 provides two login modes: multiuser mode and single-user mode. In normal state,
the U2000 runs in multiuser mode. When you need to maintaon the U2000 server (for example,
changing the user group, managed domain, or operation rights of a user), you can set the
U2000 to run in single-user mode to avoid the interference from other users.
Context
Only the admin user can set the U2000 login mode.
CAUTION
Only the admin user can log in to the U2000 through a client and all the other users are forced
to log out after the U2000 is switched from the multiuser mode to single-user mode. Switch to
the multiuser mode after you complete the operations in the single-user mode to ensure that
others can use the U2000 normally.

Procedure
2 In the Preferences dialog box, choose System Login Mode in the navigation tree on the left.
3 Set the U2000 login mode in the area on the right.
Setting Login Mode Operations
Switch to a single-user mode Choose Single-user mode and click OK. In the Set Switch
Delay dialog box, set the delay of login mode switch, and
then click OK.
l If the delay time is not 0, a dialog box is displayed. After
the switch delay, the U2000 is switched to the single-user
mode.
l If the delay time is 0, the warning dialog box is not
displayed. The U2000 is switched to the single-user
mode immediately.
On the status bar, the single-user mode information is
displayed. It indicates that the U2000 works in single-user
mode.
Switch to a multiuser mode Choose Multiuser mode, and then click OK.
The U2000 is switched to the multiuser mode immediately.
On the status bar, the multiuser mode information is
displayed. It indicates that the U2000 works in multiuser
mode.
----End
3.2.2 Setting the Access Control List

By setting the system or current user access control list (ACL), a user of the SMManagers can
allow the client or user to log in to the U2000 from the computer with specified IP address or
network segment.

Context
l The admin user has the permission to set the ACL of any user in the U2000. The user in
the security administrator group has the permission to set the ACLs of the other users except
the admin.
l The system ACL allows all the U2000 users to log in to the U2000 only through the clients
of the specific IP addresses or network segment. The user ACL is a subset of the system
ACL. The user ACL is effective only for the current user.
CAUTION
If there are multiple network adapters on the host where the client exists, you need to add
the IP addresses of all network adapters to the ACL. This ensures that the U2000 client
logs in normally.
Procedure
l Set the system ACL.
1. Choose Administration > NMS Security > ACL from the main menu.
2. In the ACL dialog box, set the system ACL.
Set the system ACL Operation
Add a system ACL item Click Add. In the New System Access Control
Item dialog box, set the IP address or network
segment, Start IP address, End IP Address or
Description, and then click OK.
Modify a system ACL item 1. In the ACL dialog box, select the system ACL
item to be modified, and then click Modify.
2. In the Modify System Access Control Item
dialog box, modify IP address or network
segment, Start IP address, End IP Address
or Description, and then click OK.
Delete a system ACL item In the ACL dialog box, select the system ACL item
to be deleted, and then click Delete. In the
l Use the user ACL.

1. Choose Administration > NMS Security > NMS User Management from the main
menu.
2. In the NMS User Management navigation tree, expand the User node, and then select
a user.
3. On the right of the interface, click the ACL tab and set the user ACL.
– Use all the ACLs in the system: The ACL is not separately set for the user. Instead,
the system ACL is used to control the IP addresses and network segments that the
user can use for login.

– Use the specified ACLs: The ACL is separately set for the user. The items in the
user ACL must be selected from the system ACL. That is, the user ACL is a subset
of the system ACL, and it functions for the current user only.
NOTE
When applying the system ACL to a user, you can click Set ACL at the lower right corner on
the ACL tab to access the system ACL dialog box and modify the system ACL.
----End
3.2.3 Setting the Password Policy

To improve U2000 security, a user of the SMManagers group can set the password policy to
prevent the user from using insecure passwords.
Context
l After the password policy is modified, the modification takes effect immediately for all
user of the U2000. For example, after the minimum length of the user password is changed,
when the online user changes a password, the minimum password length must comply with
the password policy.
l The password policy specifies the password complexity, update period, and character
restrictions. Using the password policy prevents users from setting a very simple password
or using the same password for a long time.
Procedure
1 Choose Administration > NMS Security > Security Policies from the main menu.
2 In the Security Policy dialog box, click the Password Policy tab.
3 Set the basic and advanced parameters of the password policy as required. For details about the
parameters displayed on the Password Policy tab, see Password Policy.

4 Click OK.
----End
3.2.4 Setting the Account Policy

A user of the SMManagers group can set the account policy to ensure account security.
Procedure
1 Choose Administration > NMS Security > Security Policies from the main menu.
2 In the Security Policy dialog box, click the Account Policy tab.
3 Set the account policy as required. For details about the parameters displayed on the Account
Policy tab, see Account Policy.
4 Click OK.
----End
3.3 Creating U2000 Users and Assigning Permissions

This topic describes a user of the SMManagers group to create U2000 users and assign rights
to them.
3.3.1 Procedure for Creating U2000 Users

This topic describes how to create U2000 users after the initial installation of the U2000 and
during routine maintenance.
3.3.2 Example for Creating User Accounts and Assigning Rights in the Authority- and Domain-
based Management Scenario
This topic provides the example for creating user accounts and assigning rights in the authority-
and domain-based management scenario.
3.3.3 Creating an Object Set
Devices and device services can be allocated and managed in a unified manner based on object
sets.
3.3.4 Creating an Operation Set

The operation set is a collection of operations. Permissions on devices and applications can be
assigned and managed in a unified manner based on operation sets.
3.3.5 Creating a U2000 User Group
A user of the SMManagers group can create a U2000 user group. The users with the same
permissions assigned belong to the same user group. After you set the managed domain and
operation rights for a user group, all users in this group have the rights. This helps you to assign
rights to multiple users conveniently.
3.3.6 Creating a U2000 User Account
A user of the SMManagers group can create a user account of the U2000 and assign rights to
U2000 users based on their responsibilities.
3.3.1 Procedure for Creating U2000 Users

This topic describes how to create U2000 users after the initial installation of the U2000 and
during routine maintenance.
Scenario Procedure Description
Operations 1. Creating a Object Set In this scenario, the object sets,

performed after 2. Creating an Operation Set operation sets, and user groups have
the initial not been created and configured.
installation of 3. Creating a U2000 User Group Therefore, you need to create and
the U2000 is 4. Assigning the Managed configure them before creating
successful Domain for a U2000 User users.
Group
5. Assigning Operation Rights to
a U2000 User Group
6. Creating a U2000 User
Account
7. Adding a U2000 User to a User
Group
8. Assigning the Managed
Domain for a U2000 User
9. Assigning Operation Rights to
a U2000 User
10.Assigning the User ACL
Operations 1. Creating a U2000 User In this scenario, the object sets,

performed Account operation sets, and user groups are
during routine 2. Adding a U2000 User to a User already created and configured.
maintenance of Group Therefore, you need to create
the U2000 U2000 users and add them to the
user groups only.

3.3.2 Example for Creating User Accounts and Assigning Rights in

the Authority- and Domain-based Management Scenario
This topic provides the example for creating user accounts and assigning rights in the authority-
and domain-based management scenario.
Application Scenario
Create a new office. Monitor and manage NEs in the new office through the U2000 in a
centralized manner. The NEs are divided into two parts according to the NE domain (transport
domain or IP domain), and are monitored and maintained separately. To enable different users
to monitor and maintain NEs through the U2000, associated U2000 user accounts and rights
need to be assigned to them.
Figure 3-2 shows the networking.
Figure 3-2 Networking of authority and domain-based management
transport and IP
domain maintainer
NMS
transport domain IP domain
maintainer maintainer
PTN
PTN CX600
CX600
SDH
SDH
NE80E MA5200
RTN RTN ME60

NE80E
transport domain network IP domain network
Data Planning
Plan the following subnets according to the NE domain:
l Transport domain subnet: All managed transport NEs are included.

l IP domain subnet: All managed IP NEs are included.

Plan four user groups according to user group types:
User User Responsibility Management Operation Right
Group Group Domain
Type Name
Transpo T2000gro Responsible for NEs in the Operation set of the

rt up-admin maintaining NEs in transport transport domain NE
domain the transport domain. domain maintainer
maintain Operation set of the
er group transport domain service
maintainer
Transpo T2000gro Responsible for NEs in the Operation set of the

rt up-view monitoring NEs in transport transport domain NE
domain the transport domain. domain monitor
monitor Operation set of the
group transport domain service
monitor
IP DMSgrou Responsible for NEs in the IP Operation set of the IP

domain p-admin maintaining NEs in domain domain NE maintainer
maintain the IP domain. Operation set of the IP
er group domain service
maintainer
IP DMSgrou Responsible for NEs in the IP Operation set of the IP

domain p-view monitoring NEs in domain domain NE monitor
monitor the IP domain. Operation set of the IP
group domain service monitor
NOTE
The operation sets listed in the Operation Right column refer to general operation sets associated with
NEs in the transport and IP domains. Determine the actual operation sets to be added according to the types
of managed NEs and the operation rights of user groups.
Plan the seven users according to user responsibilities:

User User Responsibility User Group
Type Name
Transport T2000- Responsible for maintaining Transport domain maintainer

domain admin NEs in the transport domain. group
maintaine
r
Transport T2000- Responsible for monitoring Transport domain monitor

domain view NEs in the transport domain. group
monitor

User User Responsibility User Group

Type Name
IP DMS- Responsible for maintaining IP domain maintainer group

domain admin NEs in the IP domain.
maintaine
r
IP DMS-view Responsible for monitoring IP domain monitor group

domain NEs in the IP domain.
monitor
Transport T2000- Responsible for maintaining Transport domain maintainer

domain admin- NEs in the transport domain and group
maintaine DMS-view monitoring NEs in the IP and
r & IP domain. IP domain monitor group
domain
monitor
IP DMS- Responsible for maintaining IP domain maintainer group

domain admin- NEs in the IP domain and and
maintaine T2000- monitoring NEs in the transport Transport domain monitor
r& view domain. group
transport
domain
monitor
Transport T2000- Responsible for maintaining Transport domain monitor

domain view- NEs in the transport and IP group
monitor DMS-view domains. and
& IP IP domain monitor group
domain
monitor
Configuration Process
on the U2000, do as follows to create a user account and assign associated rights:
1. Create subnets.
Create a transport domain subnet and an IP domain subnet, and add NEs in the transport
and IP domains to the subnets.
For details about how to create a subnet, see 5.4 Creating a Topology Subnet.
For details about how to add an NE, see 5.5 Creating NEs.
2. Create user groups and assign management domains and operation sets of the user groups.
You can easily assign rights to multiple users by using the user group function.
l According to responsibilities of user groups, configure management domains of the user
groups so that different user groups can manage different NE domains.
l According to responsibilities of user groups, configure operation rights of the user
groups so that different user groups have different operation rights.
For details about how to create a user group, see 3.3.5 Creating a U2000 User Group.

3. Create user accounts.

Create user accounts according to actual personnel condition, and configure user groups
according to responsibilities of users. Then, each user account has the management domain
and operation rights of the user group.
For details about how to create a user account, see 3.3.6 Creating a U2000 User
Account.
NOTE
When creating user accounts, do as follows to ensure the security of the U2000:
l Set different login times based on the shifts.
l Bind IP addresses of area workstations to users.
l Change the user password when you are logging in for the first time.
When the configuration is complete, the administrator can provide the accounts to relevant
personnel.

sets.
Context
l Object sets can be allocated to users or user groups.
l If an object set is allocated to a user group, all members in the user group have the
permissions of the object included in the object set.
l The U2000 provides default object set: AllObjects. The AllObjects contains all security
objects.
Procedure
1 Choose Administration > NMS Security > NMS User Management from the main menu.
2 In the NMS User Management navigation tree, right-click the Object Set node and then choose
New Object Set. Otherwise, click on the toolbar of the navigation tree, choose New Object
Set.
3 In the New Object Set dialog box, set the properties of the new Object set.

Properties of Operations
Object Set
Details of Object set On the Details tab, enter the name, type, and description of the new
Object set.
NOTE
Name is mandatory.
Members of Object On the Members tab, perform the following operations:

set 1. Click Select.
2. Select an devices or object set, and move it to Selected devices and
object sets.
l You can click to move all devices and object sets

to Selected devices and object sets.
l You can select devices or object sets from the Available devices
and object sets navigation tree, and then click
to move the selected devices or object sets to Selected devices
and object sets.
3. Click OK.
NOTE
Click Copy member from Object Set. In the Copy member from Object Set dialog box, select object
sets and copy the permissions of these object sets.
4 In the New Object Set dialog box, click OK.
----End

Context
l Operation sets can be allocated to users or user groups.
l If an operation set is allocated to a user group, all members in the user group have the
permissions of the operations included in the operation set.
l AllApplicationOperations and AllObjectOperations are default operation sets provided
by the U2000. AllObjectOperations is the operation set of network devices.
AllApplicationOperations is the operation set of network management applications.
Procedure

2 In the NMS User Management navigation tree, right-click the Operation Set node and then
choose New Operation Set. Otherwise, click on the toolbar of the navigation tree, choose
New Operation Set.
3 In the New Operation Set dialog box, set the properties of the new operation set. See New
Operation Set.
Operation Set
Details of Operation On theDetails tab, enter the type, name, and description of the new
set operation set.
NOTE
Name is mandatory.
Members of On the Members tab, perform the following operations:

Operation set 1. Click Select.
2. Select an operation or operation set, and move it to Selected
Rights.
l You can click to move all operations and

operation sets to Selected Rights.
l You can select operations or operation sets from the Available
Rights navigation tree, and then click to move
the selected operations or operation sets to Selected Rights.
3. Click OK.
NOTE
Click Copy member from operation set. In the Copy member from operation set dialog box, select
operation sets and copy the members of these operation sets.
4 In the New Operation Set dialog box, click OK.
----End

3.3.5 Creating a U2000 User Group

A user of the SMManagers group can create a U2000 user group. The users with the same
permissions assigned belong to the same user group. After you set the managed domain and
operation rights for a user group, all users in this group have the rights. This helps you to assign
rights to multiple users conveniently.
Procedure
2 In the NMS User Management navigation tree, right-click the User Group node and choose
New User Group.
3 In the New User Group dialog box, set the properties of the new user group.
You must manually set the name of the user group. For the other properties of user group, you
can set them after you create the user group successfully.
User Group Operations

Properties
User group name On the Details tab, set the user group name, description, type and
information maximum sessions.

User Group Operations

Properties
Members of user l To add members, on the Details tab, click Add. In the Add User
group dialog box, set the members to be added to the user group.
l To delete members, on the Details tab, select the members to be
deleted from Members, and then click Delete.
Management On the Domain tab, click Select. In the Select Domain dialog box, set
domain of user the management domain of the user group, and then click OK.
group
Operation On the Operation Rights tab, click Select, in the Select Operation
permissions of user Rights dialog box, set the operation rights of the user group, and then
group click OK.
NOTE
Click Copy Rights from User Group. In the Copy Rights from User Group dialog box, select user
groups and copy the management domain rights and operation permissions of these user groups.
4 In the New User Group dialog box, click OK.
----End
3.3.6 Creating a U2000 User Account

A user of the SMManagers group can create a user account of the U2000 and assign rights to
U2000 users based on their responsibilities.
Context
When you create a U2000 user, the property settings must comply with the password policy and
the account policy. For details about how to set a password policy and an account policy, see
3.2.3 Setting the Password Policy and 3.2.4 Setting the Account Policy.
Procedure
2 In the NMS User Management navigation tree, right-click the User node and choose New
User.

3 In the New User dialog box, set the properties of the new user.
You must manually set the user name and password. For the other properties, you can use default
values or set them after you create the user account successfully.
User Properties Operations
Normal properties On the Details tab, set user properties, such as user name,
description content, and password.
Owner group l To add owner groups, on the User Groups tab, click
Add, select the user groups to which you want to add the
user.
NOTE
Only users of the the SMManagers group can view their own
rights.
l To delete owner groups, on the User Groups tab, select
the user groups to be deleted from the user group list, and
then click Delete.
Management domain of user On the Domain tab, click Select. In the Select Domain dialog
box, set the management domain of the user.

User Properties Operations
Operation rights of user On the Operation Rights tab, click Select. In the Select
Operation Rights dialog box, set operation rights of the user.
Access control list (ACL) On the ACL tab, set the ACL for the user.
NOTE
Click Copy Rights from User. In the Copy Rights from User dialog box, select user groups and copy
the management domain rights and operation permissions of these users.
4 In the New User dialog box, click OK.
----End
3.4 Comparing the U2000 User Rights

By comparing the rights of two U2000 users, a user of the SMManagers group can understand
the differences between their rights.
Procedure
2 On the top of the NMS User Management navigation tree click .
3 In the Select User for Compare dialog box, select a user from the left and right group boxes
respectively.
NOTE
On the U2000, you cannot compare the same user. If you select the same user in the left and right areas,
the Compare button becomes unavailable.
4 Click Compare.
In the Compare User Rights Result dialog box, the U2000 can display user rights in the
following two modes:
l Display all rights: All user rights are displayed in the group box.

l Display only differences: Only the differences between user rights are displayed in the group
box.
----End
3.5 Querying the Authorization

In the U2000, a user of the SMManagers group can query the users or user groups that certain
operation rights are assigned to.
Context
The Administrators group contains all U2000 operation rights except the security management
rights. In the query authorization dialog box, if you select an operation node or operation set
node, the Authorized User/User Group area always displays the information that the operation
rights are assigned to the Administrator group.
Procedure
2 On the top of the NMS User Management navigation tree, click .
3 In the Authorization Details dialog box, expand the root node or parent node in the navigation
tree, and select a node.
After selection, the corresponding operations or operation sets are displayed in the Operation
area.
4 In the Operation area, expand the root node or parent node, and then select an operation.
On the right of the interface, the users and user groups that the operation rights are assigned to
are displayed in the Authorization User/User Group area.
----End

3.6 Modifying a U2000 User

This topic describes a user of the SMManagers group to modify the password, general properties,
managed domain, and operation rights of the U2000 user.
3.6.1 Resetting the Password of a U2000 User

This topic describes how the user in SMManagers reset the password of a U2000 user.
3.6.2 Modifying an Object Set
A user of the SMManagers group can modify the common properties of the specified object set,
add or delete members of a object set.
3.6.3 Modifying an Operation Set
A user of the SMManagers group can modify an operation set, such as the name and description
of an operation set. You can also add operations to an operation set, or delete operations from
an operation set.
3.6.4 Modifying a User Group
This topic describes a user of the SMManagers group to modify the basic information about a
U2000 user group, permissions, and manageable devices.
3.6.5 Modifying the Information About a U2000 User
U2000 user, permissions, and manageable devices.
3.6.1 Resetting the Password of a U2000 User

This topic describes how the user in SMManagers reset the password of a U2000 user.
Context
l The password setting must comply with the password policy. For details on how to set a
password policy, see 3.2.3 Setting the Password Policy.
l The SMManagers user can reset the passwords of other users (excluding the admin user).
The password of the admin can be changed by only the admin through the U2000 client.
l If you forget your password, contact the user in SMManagers to reset the password.
Procedure
2 In the NMS User Management navigation tree, expand the User node. Right-click the user
whose password is to be reset and choose Reset Password.
3 In the Reset Password dialog box, set New Password and Confirm Password, and then click
OK.

NOTE
If User must change password for next login is selected, you need to change the password when you log
in to the U2000 next time. Otherwise, you need not to change the user password when you log in to the
U2000 next time.
4 In the displayed dialog box, click OK.
----End

Context
l You are not allowed to change names, type and members of the default object sets.
l Only the users in Sub Domain User Group and SMManagers Group have the right to modify
object sets.
Procedure
2 In the NMS User Management navigation tree, expand the Object Set node, and then select
the object set to be modified.
3 In the area on the right , select a tab to modify the information about the object set.
Modifying a Object Set Operations
Modify normal properties Click the Details tab. In the list on the right, modify the name
and description of the object set. At the bottom of the list box,
click Apply.
Modify members of a object Click the Members tab. At the bottom of the tab, click
set Select. In the Select Object Set Member dialog box, set the
object set member, and then click OK.

View the users or user groups On the Applicable for tab, you can view only the users or user
served by an object set groups served by the object set. The Applicable for tab
displays the users or user groups served by the object set.
NOTE
To allocate a object set to a user or user group, do as follows:
1. Expand the User or User Group node and choose a user or user
group.
2. Click the Domain tab on the right of the interface.
3. Click Select.
In Select, select a object set and move it to Selected device and
object sets.
4. Click OK.
----End

an operation set.
Prerequisite
Operation sets and operation permissions are already created on the U2000.
Context
l You cannot modify the default operation set.
l Only the users in Sub Domain User Group and Security Manager User Group have the right
to modify operation sets.
Procedure
2 In the NMS User Management navigation tree, expand the Operation Set node, and then select
the operation set to be modified.

3 In the area on the right , select a tab to modify the information about the operation set.
Modifying an Operation Operations

Set
Modify normal properties Click the Details tab. Modify the operation set name and
description (the type of operation set cannot be changed). After
modification, click Apply.
Set members of a operation Click the Members tab. At the bottom of the tab, click
set Select. In the Select Operation Set Member dialog box, set
the member of the operation set, and then click OK.
Set parameters on the On the Applicable for tab, you can view only the users or user
Applicable for tab page groups served by the operation set. The Applicable for tab
displays the users or user groups served by the operation set.


Set
Allocate an operation set To allocate an operation set to a user or user group, do as

follows:
1. Expand the User or User Group node and choose a user
or user group.
2. Click the Domain tab on the right of the interface. Click
Select.
3. In the displayed Select Domain dialog box, add a object
set to the user or user group. Click OK.
4. Click the Operation Rights tab on the right of the window.
Click Select.
5. Select network device operations or network management
applications.
l Network Device
In the Select Operation Rights dialog box, select a
operation set. In the Operations area, select the
corresponding operation set.
l Network Management Application
In the Select Operation Rights dialog box, choose
Network Management Application in the navigation
tree of authorized objects. In the Operations area,
select the corresponding operation set.
6. Click to move the selected operation set to

Selected Rights.
7. Click Ok.
----End
3.6.4 Modifying a User Group

U2000 user group, permissions, and manageable devices.
Procedure
2 On the top of the NMS User Management navigation tree, expand the User Group node. Select
the user group to the modified.

3 In the area on the right , select a tab to modify the information about the user group.
Modify Properties Operation
Modify general Click the Details tab. Modify the user group name, maximum sessions
properties and description (the type of user group cannot be changed). After
Modify members To add users, click Add on the Members tab. In Add User, add users.
To delete users, select the user group and then click Delete.
On the Members tab, view the users that belong to the user group.
Modify the managed On the Domain tab, click Select. In Select Domain dialog box, add or
domain delete devices or object sets.
Modify operation On the Operation Rights tab, click Select. In Select Rights dialog
rights box, add or delete the permissions to operate network management
applications and network device operate sets.
Query current Click the Current Session tab to view the online users of the user
sessions group.
----End
3.6.5 Modifying the Information About a U2000 User

U2000 user, permissions, and manageable devices.
Procedure
2 In the NMS User Management navigation tree, expand the User node.

3 Select the user whose information you want to modify, and then modify the information about
this user on a tab in the right area.
Modify Properties Operation
Modify general Perform operations on the Details tab, modify user information(The
properties dimmed controls are unavailable).
Change the owner To add a user group, click Add on the User Groups tab. In Add User
user group Group, add a user group. To delete a user group, click Delete.
Modify the managed On the Domain tab, click Select. In Select Domain, you can perform
domain the following operations:
l Add objects or object sets.
l Delete objects or object sets.
Modify operation On the Operation Rights tab, click Select. In Select Rights, you can
rights perform the following operations:
l Add the permissions to operate NMS applications, object, object
sets and so on.
l Delete the permissions to operate NMS applications, object, object
sets and so on.
Modify the ACL To set the IP addresses that the user can access, select Use all the ACLs
in the system and Use the specified ACLs on the ACL tab. To add,
modify, or delete IP addresses or network segments, select ACL.
----End
3.7 Managing U2000 Object Sets

This topic describes a user of the SMManagers group to create, modify, and delete object sets.

3.7.1 U2000 Object Set

This topic describes the basic meaning and function of the object set.
sets.
3.7.4 Deleting an Object Set
The object set used no longer must be deleted immediately by a user of the SMManagers group.
3.7.1 U2000 Object Set

This topic describes the basic meaning and function of the object set.
The object set is a collection of manageable devices and device services. By default, the
U2000 provides AllObjects. If a user or user group can manage an object set, it indicates that
the user or user group can manage all the objects in the object set.
The administrator can create a object set, add objects that can be managed in a centralized manner
to the object set, and specify a user or user group to manage the objects in the object set. In this
way, the management cost of the administrator can be reduced.

sets.
Context
l Object sets can be allocated to users or user groups.
l If an object set is allocated to a user group, all members in the user group have the
permissions of the object included in the object set.
l The U2000 provides default object set: AllObjects. The AllObjects contains all security
objects.
Procedure
2 In the NMS User Management navigation tree, right-click the Object Set node and then choose
New Object Set. Otherwise, click on the toolbar of the navigation tree, choose New Object
Set.

3 In the New Object Set dialog box, set the properties of the new Object set.
Object Set
Details of Object set On the Details tab, enter the name, type, and description of the new
Object set.
NOTE
Name is mandatory.
Members of Object On the Members tab, perform the following operations:

set 1. Click Select.
2. Select an devices or object set, and move it to Selected devices and
object sets.
l You can click to move all devices and object sets

to Selected devices and object sets.
l You can select devices or object sets from the Available devices
and object sets navigation tree, and then click
to move the selected devices or object sets to Selected devices
and object sets.
3. Click OK.
NOTE
Click Copy member from Object Set. In the Copy member from Object Set dialog box, select object
sets and copy the permissions of these object sets.
4 In the New Object Set dialog box, click OK.
----End


Context
l You are not allowed to change names, type and members of the default object sets.
l Only the users in Sub Domain User Group and SMManagers Group have the right to modify
object sets.
Procedure
2 In the NMS User Management navigation tree, expand the Object Set node, and then select
the object set to be modified.
3 In the area on the right , select a tab to modify the information about the object set.
Modify normal properties Click the Details tab. In the list on the right, modify the name
and description of the object set. At the bottom of the list box,
click Apply.
Modify members of a object Click the Members tab. At the bottom of the tab, click
set Select. In the Select Object Set Member dialog box, set the
object set member, and then click OK.
View the users or user groups On the Applicable for tab, you can view only the users or user
served by an object set groups served by the object set. The Applicable for tab
displays the users or user groups served by the object set.
NOTE
To allocate a object set to a user or user group, do as follows:
1. Expand the User or User Group node and choose a user or user
group.
2. Click the Domain tab on the right of the interface.
3. Click Select.
In Select, select a object set and move it to Selected device and
object sets.
4. Click OK.
----End

3.7.4 Deleting an Object Set

The object set used no longer must be deleted immediately by a user of the SMManagers group.
Context
You are not allowed to delete the default object set AllObjects.
Procedure
2 In the NMS User Management navigation tree, choose the Object Set node.
The table on the right displays all the object sets on the U2000.
3 Right-click the object sets you want to delete and then choose Delete or click Delete at the
bottom of the list.
4 In the Confirm dialog box, click Yes.
----End
3.8 Managing U2000 Operation Sets

This topic describes how to create, modify, and delete operation sets.
3.8.1 U2000 Operation Set

This topic describes the basic meaning and function of the operation set.
an operation set.
3.8.4 Deleting an Operation Set
The operation set used no longer should be deleted immediately by a user of the SMManagers
group.

3.8.5 Exporting or Importing Operation Sets

The U2000 supports the export and import of operation sets. You can arrange the operation sets
on the U2000 by importing an operation set file.
3.8.1 U2000 Operation Set

This topic describes the basic meaning and function of the operation set.
The U2000 operation set is a collection of operation rights provided by the U2000. By default,
the U2000 provides two operation sets: All Application Operations and All Object
Operations. If a user or user group can manage an operation set, it indicates that the user or user
group has all the operation rights in the operation set.
The administrator can create a operation set, and then add the operation rights required in a
service to the operation set. Thus, the administrator can assign the operation rights to the related
user or user group in a centralized manner. In this way, the management cost of the administrator
is greatly reduced.

Context
l Operation sets can be allocated to users or user groups.
l If an operation set is allocated to a user group, all members in the user group have the
permissions of the operations included in the operation set.
l AllApplicationOperations and AllObjectOperations are default operation sets provided
by the U2000. AllObjectOperations is the operation set of network devices.
AllApplicationOperations is the operation set of network management applications.
Procedure
2 In the NMS User Management navigation tree, right-click the Operation Set node and then
choose New Operation Set. Otherwise, click on the toolbar of the navigation tree, choose
New Operation Set.

3 In the New Operation Set dialog box, set the properties of the new operation set. See New
Operation Set.
Operation Set
Details of Operation On theDetails tab, enter the type, name, and description of the new
set operation set.
NOTE
Name is mandatory.
Members of On the Members tab, perform the following operations:

Operation set 1. Click Select.
2. Select an operation or operation set, and move it to Selected
Rights.
l You can click to move all operations and

operation sets to Selected Rights.
l You can select operations or operation sets from the Available
Rights navigation tree, and then click to move
the selected operations or operation sets to Selected Rights.
3. Click OK.
NOTE
Click Copy member from operation set. In the Copy member from operation set dialog box, select
operation sets and copy the members of these operation sets.
4 In the New Operation Set dialog box, click OK.
----End

an operation set.
Prerequisite
Operation sets and operation permissions are already created on the U2000.
Context
l You cannot modify the default operation set.
l Only the users in Sub Domain User Group and Security Manager User Group have the right
to modify operation sets.

Procedure
2 In the NMS User Management navigation tree, expand the Operation Set node, and then select
the operation set to be modified.
3 In the area on the right , select a tab to modify the information about the operation set.

Set
Modify normal properties Click the Details tab. Modify the operation set name and
description (the type of operation set cannot be changed). After
Set members of a operation Click the Members tab. At the bottom of the tab, click
set Select. In the Select Operation Set Member dialog box, set
the member of the operation set, and then click OK.
Set parameters on the On the Applicable for tab, you can view only the users or user
Applicable for tab page groups served by the operation set. The Applicable for tab
displays the users or user groups served by the operation set.


Set
Allocate an operation set To allocate an operation set to a user or user group, do as

follows:
1. Expand the User or User Group node and choose a user
or user group.
2. Click the Domain tab on the right of the interface. Click
Select.
3. In the displayed Select Domain dialog box, add a object
set to the user or user group. Click OK.
4. Click the Operation Rights tab on the right of the window.
Click Select.
5. Select network device operations or network management
applications.
l Network Device
In the Select Operation Rights dialog box, select a
operation set. In the Operations area, select the
corresponding operation set.
l Network Management Application
In the Select Operation Rights dialog box, choose
Network Management Application in the navigation
tree of authorized objects. In the Operations area,
select the corresponding operation set.
6. Click to move the selected operation set to

Selected Rights.
7. Click Ok.
----End
3.8.4 Deleting an Operation Set

The operation set used no longer should be deleted immediately by a user of the SMManagers
group.
Context
You are not allowed to modify default operation sets All Object Operations and All
Application Operations.
Procedure
2 In the NMS User Management navigation tree, choose the Operation Set node.

The table on the right displays all the operation sets on the U2000.
3 Select the operation sets you want to delete, right-click to choose Delete or click Delete at the
bottom of the list.
----End
3.8.5 Exporting or Importing Operation Sets

The U2000 supports the export and import of operation sets. You can arrange the operation sets
on the U2000 by importing an operation set file.
Context
l Only the administrator has the permissions to export and import operation sets.
l The U2000 supports the export and import of .csv files.
l The U2000 supports the function of adding the information about operation sets in columns
one by one. After a .csv file that contains the operation set information is imported to the
U2000, the information is displayed as operation sets of the U2000.
l To add a column of operation set information to a .csv file, you need to fill in the following
two types of information so that operation sets can be imported to the U2000 successfully:
– Apart from the information that already exists in a .csv file, you must enter the name of
the operation set in the first row of the column where operation sets are to be added.
– Apart from the information that already exists in a .csv file, if you want to add operation
rights, enter an uppercase Y in the other rows of the column where operation sets are
to be added. Y indicates that the information in the rows with Y is included in operation
sets and is to be displayed on the U2000.
Procedure
2 On the top of the NMS User Management navigation tree click .
3 Export and import operation sets.

Export and import Operation

operation sets
Export operation 1. Select Export operation Sets in the drop-down list.

Sets 2. In the Save dialog box, set the path and file name for saving the
exported operation sets.
NOTE
The number of the operation set files that are generated by the U2000 is the
same as that of the existing operation set types.
3. Click Save.
Import operation 1. Select Import operation Sets in the drop-down list.

Sets 2. In the Open dialog box, select the file to be imported.
NOTE
If the names of the operation sets in a column of a file are the same as those
on the U2000, the U2000 cannot import the operation set information of this
column.
3. Click Open.
The following table describes the function of each part of a .csv file and helps you to understand
specific operations.
The following is a sample of an exported .csv file:
Table 3-1 Parts of a .csv file

Colum Description
n/Row
Columns U2000This part displays the information about operation rights that is provided
A to E by default.
WARNING
If service requirements are met, do not modify this part. If you modify it, the U2000 may
run abnormally. If an exception occurs after modification, contact Huawei technical support
engineers.

Colum Description
n/Row
Column In column F, OpeSet_A indicates the exported operation sets.

F Y indicates a member that belongs to OpeSet_A on the U2000. The following
figure shows that the operations sets in a .csv file are displayed on the U2000:
Columns You can add an operation set to the tenth row according to service requirements,
G to the and fill Y in the corresponding column.
end
----End
3.9 Monitoring a U2000 User

This topic describes how to monitor U2000 user sessions and operations, force U2000 users to
exit, unlock U2000 user accounts and send messages to online users.
3.9.1 Monitoring the U2000 User Sessions

User sessions record the login time, group, client, and status of the user. By monitoring the user
sessions, you can know the users who have logged in to the system and force the users who may
affect system security to log out as required, thus ensuring system security.
3.9.2 Monitoring the U2000 User Operations
A user of the SMManagers group can monitor operations of U2000 users to prevent unauthorized
operations.
3.9.3 Forcing a U2000 User to Quit
A user of the SMManagers group can force a U2000 user to quit session if the user performs
dangerous operations or initiates illegal sessions.
3.9.4 Unlocking a User Account
This topic describes how the user with the right to unlock a user unlocks a locked user.
3.9.5 Sending Messages to Online Users
A user of the SMManagers group can send messages to the users of the specified sessions or all
sessions. Thus, users in different regions can communicate with each other on the U2000
maintenance experience in real time.

3.9.1 Monitoring the U2000 User Sessions

User sessions record the login time, group, client, and status of the user. By monitoring the user
sessions, you can know the users who have logged in to the system and force the users who may
affect system security to log out as required, thus ensuring system security.
Context
l A session refers to the connection established between the client and the server. The session
starts when the user logs in to the client, and ends when the user logs out of the client.
l Multiple sessions can be created by using one U2000 user account.
In the U2000, a user account can be used to log in to multiple clients concurrently. You
can set the maximum number of clients that a user account can log in to concurrently in
Maximum of online users on the Details tab. If this user account is used to log in to a
certain number of clients, the same number of sessions are established.
l When the client uses multiple network adapters, the value of Operation Terminal is
selected randomly among available IP addresses of the client.
Procedure
1 Choose Administration > NMS Security > Monitor User Sessions from the main menu.
2 In the Monitor User Sessions window, view the information about login and other operations
performed by U2000 users.
3 In the Session Monitor area, you can view the information about online users and sessions.
NOTE
l After the U2000 server is restarted or the network is recovered from a disconnection, you need to click
Refresh to update the session monitoring table.
l If you select the local client in the Session Monitor area, Force User to Log Out becomes unavailable.
----End
3.9.2 Monitoring the U2000 User Operations

A user of the SMManagers group can monitor operations of U2000 users to prevent unauthorized
operations.
Procedure
1 Choose Administration > NMS Security > Monitor User Operations from the main menu.
2 Click Filter. In the displayed Filter dialog box, set the operation information to be displayed.
3 In the User Session Monitoring window, view the information about login and other operations
performed by U2000 users.

When an operation affects the U2000, you can restrict the user who performs this operation
according to the actual U2000 applications. For example, you can force the user to log out in
the User Session Monitoring window.
----End
3.9.3 Forcing a U2000 User to Quit

A user of the SMManagers group can force a U2000 user to quit session if the user performs
dangerous operations or initiates illegal sessions.
Context
l Only administrators, users of the SMManagers group, and subdomain security
administrators can force a user to quit. If you force a user to quit session, only the user
corresponding to a session is logged out forcibly. For example, user user_z logs in to the
same U2000 server through clients A and B. In this case, sessions a and b are generated. If
you want to force the user user_z of session a to quit, session b of user A is not affected.
l Current users logged in cannot force themselves to quit from their corresponding sessions.
Procedure
2 From the session monitoring table, select the records of the sessions to quit forcibly, and then
click Force User to Log Out.
3 In the confirm dialog box, click Yes.
----End
3.9.4 Unlocking a User Account

This topic describes how the user with the right to unlock a user unlocks a locked user.

Context
l The SMManagers user has the permission to unlock a user.
l In the U2000, a user can be unlocked manually or automatically.
l You can set the automatic unlocking time in Account Policy.
Choose Administration > NMS Security > Security Policies from the main menu. In the
displayed Security Policy dialog box, click the Account Policy tab, and then set Auto
Unlock.
Procedure
1 The U2000 supports the following user unlocking modes.
Unlocking Mode Operation
Manual unlocking Only the user with the rights of the SMManagers group can perform
the following operations:
1. Choose Administration > NMS Security > NMS User
Management.
2. In the NMS User Management navigation tree, expand the User
node.
3. Right-click the locked user account, and choose Unlock User.
After that, the unlocked user can log in to the U2000 successfully.
Automatic The locked user can log in successfully only when the time reaches the
unlocking preset automatic unlocking time.
----End
3.9.5 Sending Messages to Online Users

A user of the SMManagers group can send messages to the users of the specified sessions or all
sessions. Thus, users in different regions can communicate with each other on the U2000
maintenance experience in real time.
Context
On the U2000, the user of the current session cannot send messages to himself or herself.

Procedure
2 In the Session Monitor area, send messages to the users of the specified sessions or all sessions.
Sessions to Be Sent Operation
A session Right-click a session and choose Send Message. Enter the message
contents, and then click Send.
Multiple sessions Press the Ctrl or Shift to select multiple sessions. Right-click the
selected sessions and choose Send Message. Enter the message
All sessions Use the combination key Ctrl+A to select all sessions. Right-click the
selected sessions and choose Send Message. Enter the message
----End
3.10 Managing the Remote Maintenance User

The U2000 remote maintenance function allows login to the U2000 server from a remote
maintenance terminal. Strict management for the remote maintenance user not only ensures
U2000 system security, but also makes maintenance operations easier.
Prerequisite
l You must be an NM user with "NM maintainer" authority or higher.
l The remote maintenance user must be enabled before you set operation authority or set
validity parameters.
Context
l To facilitate easy maintenance, the U2000 supports remote maintenance functions. In the
maintenance field, maintenance personnel can log in to the remote maintenance terminal
as the remote maintenance user and maintain NEs. Under normal conditions, do not enable
this option for security reasons. Enable this option for a user only when a fault occurs or
in special conditions.
l For security purposes, it is recommended to set a valid period for the remote maintenance
user.

Procedure
1 Choose Administration > NMS Security > Remote Maintenance User Management from
the main menu.
2 Enable the remote maintenance user.

3 Set the Operation Authority. You can select Query or Configuration as needed.
4 Set Valid Forever or Not to No. Set Validity Period.
5 Click OK.
----End
3.11 Managing NE Users

To ensure NE data security, you can manage the authorities and passwords for NE users.
By using the U2000 you can perform the following NE user management tasks.
NOTE
The following functions are applies to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
3.11.1 Querying the NE User Information

By querying the additional information of an NE user, you can learn the basic information of
this user for the purpose of management or task allocation.

3.11.2 Creating an NE User

To ensure NE data security, only the users with NE user authority can log in to the NEs. An NE
user is able to perform operations on the NEs according to the assigned authority. The U2000
administrator is advised to create NE users before configuring services.
3.11.3 Modifying NE Users
You need to modify the settings of an NE user, so that the NE user can use the special functions
of the NE.
3.11.4 Changing the NE User Password
To ensure network security, you are recommended to change the NE user password periodically.
3.11.5 Querying NE Security Parameters
According to the default security settings, the NE is able to determine whether the NE user
password is valid and decide whether the login is allowed. The U2000 administrator needs to
know the NE security settings and modify the NE user password before it becomes invalid.
3.11.6 Querying NE User Groups
NE users of different levels are divided into different NE user groups. In this user interface, you
can query NE users included by various NE user groups of an NE.
3.11.7 Deleting NE Users
To ensure NE and network security, you need to delete the NE users that are no longer used.
This prevents misoperations or damage caused by user account theft.
3.11.1 Querying the NE User Information

By querying the additional information of an NE user, you can learn the basic information of
this user for the purpose of management or task allocation.
Prerequisite
l You must be an NM user with "NE monitor" authority or higher, and belonged to
"SMManager" user group.
l The level of the NE user to be queried must be lower than that of the NE user who has
logged in.
NOTE
Choose Administration > NE Security Management > NE Login Management. You can view the
logged in information of NE users on the NE Login Management tab.
Procedure
1 Choose Administration > NE Security Management > NE User Management from the main
menu.
2 In the NE list on the left, select an NE and click .
3 Optional: Click Query to query the NE user information from the NE.
4 Click User Additional Information to query the additional information of this NE user (such
as login policy, password validity policy, and last login time).
----End

3.11.2 Creating an NE User

To ensure NE data security, only the users with NE user authority can log in to the NEs. An NE
user is able to perform operations on the NEs according to the assigned authority. The U2000
administrator is advised to create NE users before configuring services.
Prerequisite
l You must be an NM user with "NE administrator" authority or higher, and belonged to
l The level of the NE user to be created must be lower than that of the NE user who has
logged in.
NOTE
Context
The default NE user has the monitor level authority. To ensure NE data security, it is
recommended that you assign NE users with different authorities as required.
Procedure
menu.
2 In the NE list on the left, select an NE and click .

3 Click Add and the Add NE User dialog box is displayed.
4 Optional: For the NA NE, you can click the Add NA User button, and the Add NA NE User
dialog box is displayed.

5 Enter the NE user name in the NE User field.
6 Select the User Level as needed.
7 In the NE User Flag field, select a user type according to the type of the terminal through which
the user logs in to the NE.
8 Enter the password in the New Password field and enter it again in the Confirm Password
field.
NOTE
The password is a string of 6-16 characters. It can consist of letters, symbols and numerals, and must contain
at least one letter and one numeral.
9 In the NE Name field, select one or mutiple NEs that this NE user is allowed to manage.
10 Click OK.
----End
3.11.3 Modifying NE Users

You need to modify the settings of an NE user, so that the NE user can use the special functions
of the NE.
Prerequisite
l The NE user must be created.
l The level of the NE user to be modified must be lower than that of the NE user who has
logged in.

NOTE
Procedure
menu.
2 In the left-hand NE list, select an NE and click .

3 In NE User Management Table, select the NE user to be modified and click Modify. A dialog
box is displayed.
4 In the dialog box displayed, modify the settings of the attributes of the NE user. Click Apply.
5 Click OK.
----End
3.11.4 Changing the NE User Password

To ensure network security, you are recommended to change the NE user password periodically.
Prerequisite
l The level of the NE user to be modified must be lower than that of the NE user who has
logged in.
NOTE
Context
CAUTION
Change the password periodically for security purposes.
Procedure
menu.
2 In the Object Tree, select an NE that you want to query and click .
3 Select an NE user whose password need to be modified from the NE user list and choose Set
Password. The Set Password of NE User dialog box is displayed. Enter the password in the
New Password field and enter the new password again in the Confirm Password field.

4 Click OK.
----End
3.11.5 Querying NE Security Parameters

According to the default security settings, the NE is able to determine whether the NE user
password is valid and decide whether the login is allowed. The U2000 administrator needs to
know the NE security settings and modify the NE user password before it becomes invalid.
Prerequisite
Applies to the release 5.0 NEs of transport domain equipments.
Procedure
1 In the NE Explorer, select an NE and choose Security > NE Security Parameters from the
Function Tree.
2 Click Query to query the settings of NE security parameters.
----End
3.11.6 Querying NE User Groups

NE users of different levels are divided into different NE user groups. In this user interface, you
can query NE users included by various NE user groups of an NE.
Prerequisite
Applies to the MSTP, WDM, RTN, PTN NEs.

Procedure
1 In the NE Explorer, select an NE and choose Security > NE User Group Management from
the Function Tree.
2 Click Query to query NE users included by various NE user groups of the NE.
----End
3.11.7 Deleting NE Users

To ensure NE and network security, you need to delete the NE users that are no longer used.
This prevents misoperations or damage caused by user account theft.
Prerequisite
l You must be an NM user with "NE administrator" authority or higher.
l The level of the NE user to be deleted must be lower than that of the NE user who has
logged in.
NOTE
Procedure
menu.
2 In the left-hand NE list, select an NE and click .

3 In NE User Management Table, select the NE user to be deleted and click Delete. A dialog
box is displayed asking you whether to delete the NE user.
4 Click OK.
----End
3.12 Managing NE Login

To ensure NE data security, you can manage the users who are logged in to NEs.
Context
By using the U2000 you can perform the following NE login management tasks:
3.12.1 Locking Out NE Login
An NE user can lock out the NE, to deny login attempts from other users of the same level or
lower level. If there is an NE user of the same level or higher level logged in to the NE, the NE
user cannot lock out the NE. NE users of higher levels automatically unlock the NE login that
is locked by lower-level users.
3.12.2 Locking Out NE Settings
An NE user can lock out the settings of an NE, preventing other NE users of the same level or
higher level from performing any settings on the NE. If a user of the same level or higher level

has logged in to the NE, the NE user cannot lock out the NE settings. NE users of higher levels
automatically unlock the NE settings locked by lower-level users.
3.12.3 Querying the Information About an Online NE User
To ensure the security of NE operations, the NMS maintainers or administrators can use the
U2000 to view all the online NE users within the management rights and the way in which the
users log in to the NEs. The NE user at a higher level can forcibly kick off the NE user at a lower
level.
3.12.4 Switching a Logged-In NE User
During a new deployment, after the root NE user creates the NE, this user can create another
NE user. You can log in to the NE with the new NE user name.
3.12.5 Forcing an NE User to Log Out of the U2000
For network security management, you can force a specified NE user to log out of the U2000
as required. In the single user mode, this function also forces all other users to log out of the
U2000. In addition, an NE user will be forced to log out by the U2000 after a long period of
time without any activities.
3.12.6 Setting NE Login Prompt Message
You can set the custom information of an NE logs in to the U2000 in this interface.
3.12.1 Locking Out NE Login

An NE user can lock out the NE, to deny login attempts from other users of the same level or
lower level. If there is an NE user of the same level or higher level logged in to the NE, the NE
user cannot lock out the NE. NE users of higher levels automatically unlock the NE login that
is locked by lower-level users.
Prerequisite
l The current NE user has the highest level among all login NE users.
l The NE must be a release 4.0 transport equipment.
Procedure
1 Choose Administration > NE Security Management > Lock Out NE Login from the main
menu.
2 In the Object Tree, select an NE and click the double-right-arrow button (red).
3 Click Query to query the Login Lock Status.
4 Optional: If the value of Login Lock Status is Not Locked out, select it and click Lock
Login or right-click it and choose Lock Login.
----End
3.12.2 Locking Out NE Settings

An NE user can lock out the settings of an NE, preventing other NE users of the same level or
higher level from performing any settings on the NE. If a user of the same level or higher level
has logged in to the NE, the NE user cannot lock out the NE settings. NE users of higher levels
automatically unlock the NE settings locked by lower-level users.

Prerequisite
l Applies to the release 4.0 transport NEs.
Procedure
1 Choose Administration > NE Security Management > Lock Out NE Settings from the main
menu.
2 In the left pane, select an NE and click the double-right-arrow button (red).
3 Click Query to query the Set Lock Status.
4 If the value of Set Lock Status is No, select it and click Lockout or right-click it and select
Lockout. The Set Lock Window dialog box is displayed.
5 Check the Lock Permanently check box to permanently lock the current NE settings or enter
the value of Continues Time to temporarily lock the settings. Click OK.
----End
3.12.3 Querying the Information About an Online NE User

To ensure the security of NE operations, the NMS maintainers or administrators can use the
U2000 to view all the online NE users within the management rights and the way in which the
users log in to the NEs. The NE user at a higher level can forcibly kick off the NE user at a lower
level.
Prerequisite
You must be a U2000 user with NMS maintainer or NMS administrator rights or higher.
This operation is applicable to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
Procedure
1 Choose Administration > NE Security Management > NE Login Management from the main
menu. Click the Online User Management tab.
2 Select the NE to be queried from the NE list and click .
3 Click Query to query the user of the online NE and the login way of this user.
4 Optional: Click Filter. Set Current Connected User and Login Mode as the filter criteria to
view the information about the online NE user.
----End
3.12.4 Switching a Logged-In NE User

During a new deployment, after the root NE user creates the NE, this user can create another
NE user. You can log in to the NE with the new NE user name.

Prerequisite
l This operation is applicable to the MSTP, WDM, NA WDM, RTN, PTN, Marine series
NEs.
One NE user cannot log in or manage an NE at multiple clients at the same time. After you use
an NE user to log in to an NE through a U2000 server, if you use the same NE user to log in to
the same NE through another U2000 server, the NE user is forced to log out from the first
U2000 server.
Procedure
menu.
2 Click NE Login Management or DC Login User Management tab.
3 Select an NE from the NE list to switch its user. Click .
4 Click Query to query the current NE user.
5 In the table, select the NE and click Switch NE User. In the Switch Current NE User dialog
box, enter the NE user name and password.
6 Click OK.
----End
3.12.5 Forcing an NE User to Log Out of the U2000

For network security management, you can force a specified NE user to log out of the U2000
as required. In the single user mode, this function also forces all other users to log out of the
U2000. In addition, an NE user will be forced to log out by the U2000 after a long period of
time without any activities.
Prerequisite
l The NE user must be logged in to the NE.
l The current NE user has the higher level than the other login NE users.
Context
Applies to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.

Procedure
menu.
3 Click NE Login Management or Online User Management tab, select the NE entry. Click
Logout or Forced Logout. A prompt appears telling you that the operation was successful.
4 Click Close.
----End
3.12.6 Setting NE Login Prompt Message

You can set the custom information of an NE logs in to the U2000 in this interface.
Prerequisite
Procedure
1 In the NE Explorer, select an NE and choose Security > NE Security Parameters from the
Function Tree.
2 Optional: Click Query to query the settings of NE security parameters.
3 Select an NE, double-click Warning Screen Switching and choose whether to enable the
warning screen.
4 Double-click Warning Screen Information and enter the information.
NOTE
You can enter information in the Warning Screen Information field only when you set Warning Screen
Switching to Enabled.
5 Click Apply. A prompt appears telling you that the operation was successful. Click Close.
----End
3.13 Setting the Security Access of an NE

To ensure the NE security, you need to disable the unused interfaces on the NE.

Prerequisite
3.13.1 Controlling Communication Between NE and U2000 Through Ethernet Port
By default, an NE can be connected to the U2000 through an Ethernet port. This operation
enables you to query and set the Ethernet access function for an NE.
3.13.2 Controlling Communication Between NE and U2000 Through a Serial Port
NEs can be accessed to the U2000 through a serial port or the command line tool. This operation
views and sets the serial port access function of NEs.
3.13.3 Setting the NE OAM Access
The U2000 installed in a PC or a workstation can use the OAM port of an NE to manage and
maintain the NE. The OAM port can also be used in remote maintenance if necessary. To
configure an NE through the OAM port, you need to enable the OAM access function of the
NE.
3.13.4 Setting the NE COM Access
The COM port of an NE is a port used for on-site commissioning. If you need to use the COM
port to configure an NE, you need to enable the COM access function of the NE.
3.13.5 Controlling Communication Between NE and LCT
For NE operation security, NEs are managed by the U2000 under normal circumstances. But
under special circumstances, you need to use the U2000 LCT or Web LCT to commission an
NE. You can turn on LCT access for the NE on the U2000.
3.13.1 Controlling Communication Between NE and U2000

Through Ethernet Port
By default, an NE can be connected to the U2000 through an Ethernet port. This operation
enables you to query and set the Ethernet access function for an NE.
Prerequisite
Context
CAUTION
This operation may affect the communication between the U2000 and NEs.
Procedure
1 In the NE Explorer, select an NE and choose Communication > Access Control from the
Function Tree.
2 In the Ethernet Access Control area, click Refresh to query the Ethernet access enable status.

3 Set The First Network Port as Enabled and click Apply. The Ethernet access function for the
NE is enabled.
NOTE
l If you want to disable this function, set The First Network Port as Disabled and click Apply.
l If the second network port exists, you can enable Ethernet access for the port. For OptiX OSN
equipment, the second network port is EXT port.
For certain types of devices, you can click the Enable Ethernet Access checkbox to enable the
Ethernet access function.
----End
3.13.2 Controlling Communication Between NE and U2000

Through a Serial Port
NEs can be accessed to the U2000 through a serial port or the command line tool. This operation
views and sets the serial port access function of NEs.
Prerequisite
Procedure
1 In the NE Explorer, select an NE and choose Communication > Access Control from the
Function Tree.
2 Check the Enable Serial Port Access check box. Click Refresh to query whether the current
NE allows serial port access. Click Apply to enable the serial access function of the NE.
3 Set the Baud Rate. Click Apply.
----End

3.13.3 Setting the NE OAM Access

The U2000 installed in a PC or a workstation can use the OAM port of an NE to manage and
maintain the NE. The OAM port can also be used in remote maintenance if necessary. To
configure an NE through the OAM port, you need to enable the OAM access function of the
NE.
Prerequisite
Applies to the MSTP, Metro WDM, LH WDM, RTN, PTN, Marine NEs.
Procedure
1 In the NE Explorer, click an NE and choose Communication > Access Control from the
Function Tree.
2 Select Enable OAM Access and click Apply. The OAM access of the NE is now enabled.
----End
3.13.4 Setting the NE COM Access

The COM port of an NE is a port used for on-site commissioning. If you need to use the COM
port to configure an NE, you need to enable the COM access function of the NE.
Prerequisite
Applies to the MSTP, Metro WDM, LH WDM, RTN, PTN Marine equipment.
Context
l The COM port directly connects to the SCC board, improper usage may affect the normal
service handling on the NE, and the rate of the COM port is slow. Hence, it is recommended
to use Ethernet access for the LCT (U2000 or Web LCT) in most cases.
l Use COM port access only when the Ethernet access fails, or the NE already connects to
the U2000, or certain lower layer commissioning commands need be run.
l For security measures, the COM port access is disabled by default after NE initialization
or downloading. If necessary, you can use the U2000 to temporarily enable COM access.
Procedure
1 In the NE explorer, click an NE and choose Communication > Access Control from the
Function Tree.

2 Select Enable COM Access and click Apply. The COM access of the NE is now enabled.
----End
3.13.5 Controlling Communication Between NE and LCT

For NE operation security, NEs are managed by the U2000 under normal circumstances. But
under special circumstances, you need to use the U2000 LCT or Web LCT to commission an
NE. You can turn on LCT access for the NE on the U2000.
Prerequisite
You must log in to the NM as user admin.
This operation is applicable to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
l When no U2000 user logs in to an NE and an LCT user requests to log in to the NE, the
NE does not refer to the LCT Access Control Switch parameter and allows the LCT access
directly.
l When a U2000 user has logged in to an NE and then an LCT user requests to log in to the
NE, the NE determines whether to allow the LCT user to log in according to the LCT
Access Control Switch parameter.
l When an LCT user has logged in to an NE and then a U2000 user requests to log in to the
NE, the login of the LCT user does not affect the login of the U2000 user, and the successful
login of the U2000 user does not affect the logged-in LCT user.
l When the LCT user and the U2000 user log in to the NE at the same time, set LCT Access
Control Switch to Disable Access. This does not affect the LCT user that is already logged
in.
l After the OptiX OSN 500 is disconnected to the U2000 for over 30 minutes, the OptiX
OSN 500 automatically allows the LCT access.
Procedure
l If you want to manage LCT access network-wide, use the following method to navigate to
the window.
1. Choose Administration > NE Security Management > NE Login Management
from the main menu. Click the LCT Access Control tab.
2. Select the NE to be set from the NE list and click .

3. Click Query to query whether the current NE allows LCT access.
4. Optional: Select an NE and click Access Allowed to enable LCT access.
5. Optional: Select an NE and click Disable Access to disable LCT access.
6. Optional: To set LCT access for multiple NEs in batches, select the NEs, right-click,
and then choose a menu item from the shortcut menu.

l If you want to manage LCT access for a certain NE, use the following method.
1. In the NE Explorer, select an NE and choose Security > LCT Access Control from
the Function Tree.
2. Click Query to query whether the current NE allows LCT access.
3. Click Access Allowed to enable LCT access.

NOTE
If you want to disable this function, click Disable Access.
----End
3.14 Setting the NE ACL

You can ensure the security of NEs by setting the NE ACL.
Prerequisite
3.14.1 Overview of ACL
Access control list (ACL) can be used for basic traffic filtering. ACL can be configured for all
the NEs to filter IP packets as they pass through an NE. ACL can prevent certain traffic from
entering or exiting a network.
3.14.2 Setting Basic ACL Rules
In the case of ordinary NEs that do not have high security requirements, you can set the basic
ACL rules. The basic ACL rules examine the source IP address of the packets. The basic ACL
rules do not use many system resources.
3.14.3 Setting the Advanced ACL Rules
In the case of NEs that have very high security requirements, you can set the advanced ACL
rules. The advanced ACL rule, examines the source and the sink IP address, the source and the
sink port number, and the protocol type. The implementation of advanced ACL rules use many
system resources. The advanced ACL rules have higher priority than the basic ACL rules.
3.14.1 Overview of ACL

Access control list (ACL) can be used for basic traffic filtering. ACL can be configured for all
the NEs to filter IP packets as they pass through an NE. ACL can prevent certain traffic from
entering or exiting a network.
Purpose
The most important reason to configure ACL is to provide security for the network. With proper
ACL rules, the entire network can be prevented from security threats. ACL can also provide the
basic flow control function.

Implementation
The ACL can control whether the IP packets are received or dropped by certain NEs. Every IP
packets is examined by the NEs according to predefined ACL rules. After the examination, the
NEs determine whether to receive or to drop this packet.
3.14.2 Setting Basic ACL Rules

In the case of ordinary NEs that do not have high security requirements, you can set the basic
ACL rules. The basic ACL rules examine the source IP address of the packets. The basic ACL
rules do not use many system resources.
Prerequisite
l It is applicable to the MSTP, WDM, PTN and RTN equipment.
Procedure
1 In the NE Explorer, select an NE and choose Security > ACL from the Function Tree.
2 Click the Basic ACL tab. The basic ACL rule list is displayed.
NOTE
If the equipment only supports basic ACL settings, by clicking ACL from the Function Tree, you directly
access the list of the basic ACL rule.
3 Click Query to load the basic ACL rules from the NE.
4 Click New.
An undefined basic ACL rule is added to the basic ACL rules list.
5 Set the proper values for all the parameters according to the network requirements.
6 Click Apply to apply the new configuration data to the NE.
A prompt appears indicating the operation was successful.
7 Click Close to complete the operation.
8 Optional: Repeat Step 4 through Step 7 to set more basic ACL rules to this NE.
9 Optional: Repeat Step 1 through Step 7 to set the basic ACL rules to other NEs.
----End
3.14.3 Setting the Advanced ACL Rules

In the case of NEs that have very high security requirements, you can set the advanced ACL
rules. The advanced ACL rule, examines the source and the sink IP address, the source and the
sink port number, and the protocol type. The implementation of advanced ACL rules use many
system resources. The advanced ACL rules have higher priority than the basic ACL rules.
Prerequisite
It is applicable to the MSTP, WDM, PTN and RTN equipment.

Procedure
1 In the NE Explorer, select an NE and choose Security > ACL from the Function Tree.
2 Click the Advanced ACL tab. The advanced ACL rule list is displayed.
3 Click Query to load the advanced ACL rules from the NE.
4 Click New.
An undefined advanced ACL rule is added to the list.
5 Set proper values for all the parameters according to the network requirements.
6 Click Apply to apply the new configuration data to the NE.
A prompt appears indicating the operation was successful.
7 Click Close to complete the operation.
8 Optional: Repeat Step 4 through Step 7 to set more advanced ACL rules to this NE.
9 Optional: Repeat Step 1 through Step 7 to set the advanced ACL rules to other NEs.
----End
3.15 RADIUS Configuration

Remote authentication dial in user service (RADIUS) is the industrial standards. RADIUS
provides the authentication and accounting functions for the remote access to a network or dialup
access to a network.
NOTE
3.15.1 Overview
This topic describes the remote authentication dial-in user service (RADIUS) in terms of
definition, standard and protocol compliance, implementation principles, and packet exchange
process.
3.15.2 Adding a RADIUS Server
Before using the RADIUS function, you need to add a remote authentication dial-in user service
(RADIUS) server and configure the function of authentication, accounting, or authentication
and accounting depending on the actual network demands.
3.15.3 Setting NE RADIUS Parameters
A remote authentication dial-in user service (RADIUS) server can provide authentication and
accounting services after relevant parameters of the RADIUS are set on the corresponding NE.
3.15.4 Setting an NE as a RADIUS Client or Proxy Server
An NE can be set as a remote authentication dial-in user service (RADIUS) client or proxy server
after the RADIUS Client and Proxy Server parameters are set on the corresponding NE. If
these parameters are not set on the NE, the RADIUS function of the NE cannot be used.
3.15.1 Overview
This topic describes the remote authentication dial-in user service (RADIUS) in terms of
definition, standard and protocol compliance, implementation principles, and packet exchange
process.

RADIUS protocol is an information exchange protocol used to authenticate remote connections

to the system and prevent unauthorized user access to the network.
RFC 2865 is the standard and protocol compliance of the RADIUS protocol.
Structures of a RADIUS Packet and RADIUS Protocol Stack

Figure 3-3 shows the structure of a RADIUS packet. Table 3-2 provides detailed description
on fields in a RADIUS packet.
Figure 3-3 Structure of a RADIUS Packet
0-1-2-3-4-5-6-7-0-1-2-3-4-5-6-7-0-1-2-3-4-5-6-7-0-1-2-3-4-5-6-7
Code Identifier Length
Authenticator
Attribute - - - - - -
0-1-2-3-4-5-6-7-0-1-2-3-4-5-6-7-0-1-2-3-4-5-6-7-0-1-2-3-4-5-6-7
Type Length Value
Table 3-2 Field Description of a RADIUS Packet
Field Length Limit Description
Code 8 bits Indicates the type of a

RADIUS packet. Frequently
used codes are as follows:
l Code = 1: Access-request
l Code = 2: Access-accept
l Code = 3: Access-reject
l Code = 4: Accounting
request
l Code = 5: Accounting
response
Identifier 8 bits Indicates the identifier for

matching a request packet
with a response packet.

Field Length Limit Description
Length 16 bits Indicates the length of a

packet.
Authenticator 32 bits Indicates the authentication

word for ensuring the
security of a packet.
Attribute Not specified Indicates the attributes of a

packet. It is set in the type-
length-value (TLV) format.
A RADIUS client communicates with the server by using the user datagram protocol (UDP).
Figure 3-4 shows the structure of RADIUS protocol stack.
Figure 3-4 Structure of RADIUS Protocol Stack
RADIUS
IP
PPP Ether
NOTE
The data transmitted between the network access server (NAS, namely, the RADIUS client) and the
RADIUS server are of tens of or even a hundred of bits. The RADIUS protocol is required to provide
retransmission mechanism and standby server mechanism. RADIUS protocol demands for good timer
management mechanism. A user can accept the authentication that lasts only tens of seconds.
l In the case of many users, multiple threads are required on a server. The UDP protocol helps the
server to achieve this by simplifying the procedure.
l The TCP protocol, however, cannot be used to transmit data until a connection is created successfully.
Hence, the TCP protocol is weak in the real-time aspect when many users are involved. In addition,
the TCP protocol cannot fully meet the requirements of RADIUS in the aspect of timing.
Thus, the UDP protocol is used in the communication instead of the transmission control protocol (TCP).
Implementation Principles
RADIUS adopts a distributed client/server model. Generally, the model is used to manage a
huge number of distributed dial-in users.
Figure 3-5 shows the networking structure of RADIUS. An NE is set as a RADIUS client or
proxy server. By managing a simple user database, the RADIUS server implements
authentication and accounting and adjusts the user service information based on the service type
and rights of a user. The RADIUS protocol specifies how the NAS and the RADIUS server
should exchange the user information and the accounting information.
l The NAS extracts configuration information of a user, encapsulates the information into a
standard RADIUS packet, and then send the packet to the RADIUS server for processing.

l The RADIUS server receives the connection request of the user, authenticates the user, and
then returns to the NAS the configuration information required for delivering services to
the user.
l The NAS and RADIUS exchange authentication information by using a key. The password
of a user is encrypted before being transmitted on the network, which prevents the password
from being intercepted on an insecure network.
l A RADIUS server can be used as a proxy client of other RADIUS servers or as an
authentication server of other types.
Figure 3-5 RADIUS Networking Structure
U2000
Client
RADIUS RADIUS
Client Server
127.7.66.66
RADIUS
Client
RADIUS
Server
127.7.66.67
RADIUS
Client
RADIUS
RADIUS Server
Client 127.7.66.68
Packet Exchange Process

The password authentication protocol (PAP) is used for the exchange of RADIUS packets
between RADIUS clients and RADIUS servers. Figure 3-6 describes the packet exchange
processes of authentication and accounting of a user between the NAS and the RADIUS server.

Figure 3-6 RADIUS Packet Exchange Process
Client NAS Radius

Server
Authentication Rep
Code=1
Code=2(3)
Authentication Ack
Code=4(start)
Code=5
Code=4(stop)
Code=5
The authentication process is as follows:

1. A remote dial-in user initiates an authentication request and sends relevant authentication
information about the user to the RADIUS client.
2. The RADIUS client encapsulates the received authentication information into a standard
RADIUS packet by using a shared key and initiates an authentication request (Code = 1)
to the RADIUS server. In the request packet, relevant attributes are included, such as the
user name, password, client ID and the access port ID.
NOTE
l If no response is returned within the retransmission interval, the RADIUS client retransmits the
request packet to the RADIUS server repeatedly. The packet retransmission interval and
retransmission times can be set by the user.
l The RADIUS client can also forward the request to the standby or proxy server in the event that
the active server is down or unreachable.
3. After receiving the authentication request packet, the RADIUS server checks whether the
packet is sent from a configured RADIUS client. The RADIUS server uses the shared key
to decapsulate the authentication request packet, examines the data in the packet, and then
determines whether the RADIUS client is legal or illegal.
4. If the RADIUS client is legal, the RADIUS server returns an Access-Accept packet (Code
= 2). If the client is illegal, the server returns an Access-Reject packet (Code = 3).
5. Then the RADIUS client returns the authentication response to the user.
The accounting process is as follows:

1. At the start of service delivery, the RADIUS client submits an Accounting Start request
[Code = 4 (Start)] to the RADIUS Accounting server. The request packet shall contain
information about the service type and the service sink.

2. When receiving the packet, the RADIUS Accounting server returns an Accounting-
Response packet (Code = 5) to the client.
3. At the end of service delivery, the RADIUS client sends an Accounting Stop request [Code
= 4 (Stop)] to the RADIUS Accounting server. The request packet shall contain the service
type and statistics (optional), such as elapsed time, input and output octets, or input and
output packets.
NOTE
l If no response is returned within the retransmission interval, the RADIUS client retransmits the
Accounting Start request and Accounting Stop request to the RADIUS server repeatedly. The
packet retransmission interval and retransmission times can be set by the user.
l The RADIUS client can also forward the requests to the standby or proxy server in the event that
the active server is down or unreachable.
4. When receiving the Accounting Start request, the RADIUS server returns an Accounting-
Response packet (Code = 5) to the client.
3.15.2 Adding a RADIUS Server

Before using the RADIUS function, you need to add a remote authentication dial-in user service
(RADIUS) server and configure the function of authentication, accounting, or authentication
and accounting depending on the actual network demands.
Prerequisite
l An NE must be set as a RADIUS client.
Procedure
1 Choose Administrator > NE Security Management > RADIUS Configuration
Management from the main menu. In the window that is displayed, click the NE RADIUS
Configuration tab.
2 Click RADIUS Server Configuration. The RADIUS Server Information dialog box is
displayed.
3 Click Query to query the current configuration of the RADIUS server from the NE.

4 Click New. The New RADIUS Server Information dialog box is displayed.
5 Configure the RADIUS server information and click OK.

NOTE
l When adding a RADIUS server, identify the RADIUS server uniquely by entering the IP address of the NE.
l When adding a proxy server, identify the proxy server by entering the IP address or name of the NE.
l Before adding a proxy server, you need to set the NE as a RADIUS proxy server.
6 Optional: Repeat 4 to 5 to add more RADIUS servers.
7 Optional: In the RADIUS Server Information dialog box, select the RADIUS server to be
deleted. Then, click Delete.
----End
Follow-up Procedure
After the RADIUS server is added, you need to configure the RADIUS parameters on the NE.
3.15.3 Setting NE RADIUS Parameters

A remote authentication dial-in user service (RADIUS) server can provide authentication and
accounting services after relevant parameters of the RADIUS are set on the corresponding NE.
Prerequisite
l A RADIUS server must be added.
Procedure
Configuration tab.

2 In the left navigation tree, select the NE and subnet to be queried. Click to query the
current configuration of the RADIUS from the U2000.
3 Click Query to query the current configuration of the RADIUS from the NE.
4 Click New. The New NE RADIUS Configuration dialog box is displayed.
NOTE
If the type of the server to be added is Proxy Server, you do not need to set Shared Key.
5 Set RADIUS parameters. Then, click OK.
----End
3.15.4 Setting an NE as a RADIUS Client or Proxy Server

An NE can be set as a remote authentication dial-in user service (RADIUS) client or proxy server
after the RADIUS Client and Proxy Server parameters are set on the corresponding NE. If
these parameters are not set on the NE, the RADIUS function of the NE cannot be used.
Prerequisite
The NE must communicate with the U2000 successfully.

Context
l You can set the RADIUS parameters on an NE can be set only after the NE is set as a
RADIUS client.
l If an NE is set as a RADIUS client without a RADIUS server, the NE fails to implement
RADIUS authentication.
Procedure
Function Configuration tab.
2 In the left navigation tree, select the NE and subnet to be queried. Click to query the
current configuration of the NE RADIUS function from the U2000.
3 Click Query to query the current configuration of the NE RADIUS function from the NE.
4 Double-click RADIUS Client and Proxy Server and set them to Open respectively.
5 Click Apply.
----End
Follow-up Procedure
After an NE is set as a RADIUS client or proxy server, you need to add a RADIUS server.
3.16 Auditing Changes

If changes occur on a device in the network, you can query information about the changes through
U2000.
With change audit, you can view the following changes:
l Entity changes
The system generates a change record after the change of the device entity is found by
polling or manually refreshing the device.
l Device configuration changes
After a device configuration file is backed up in DC management, you can find the change
of the device configuration file by comparing it with the previous configuration file. A
device configuration change record is generated.
l Software image changes
The change record is generated when the system polls the device and finds the change of
the software version.
3.16.1 Viewing Information About Change Auditing
This describes how to view information about change auditing. If changes occur on a device in
the network, you can query information about the changes through change auditing.

3.16.2 Dumping Information About Change Audit

This describes how to dump information about change audit.
3.16.3 Deleting Information About Change Audit
This describes how to delete information about change audit.
3.16.1 Viewing Information About Change Auditing

This describes how to view information about change auditing. If changes occur on a device in
the network, you can query information about the changes through change auditing.
Prerequisite
Procedure
1 Choose Administration > NE Security Management > Change Audit from the main menu.
2 On the Change Audit tab, click Condition.
3 In the Set Filter Condition dialog box, set the query conditions and then click OK.
4 On the Change Audit tab, click Query.
All eligible records are displayed in the query result area. The records displayed in the query
result area cannot be refreshed in real time. To view the latest records, you need to click
Query before viewing.
5 Click a record. The details about the record are displayed in the detailed information area.
NOTE
l For a record with Change Type being Software Image, the Details tab displays two records. The
upper one shows software version information before change and the lower one shows the latest
software version information after change.
l For a record with Change Type being Entity, the Details tab displays the specific change type, either
Add or Delete.
----End
3.16.2 Dumping Information About Change Audit

This describes how to dump information about change audit.
Prerequisite
Context
The U2000 deletes the records in the database after information about change audit is dumped.
Thus, you cannot query the dumped records through the client.
Procedure

2 On the Change Audit tab, set query conditions and then click Query.
All records meeting the conditions are displayed in the query result area.
3 In the query result area, select one or more records to be dumped and then right-click them.
Then, select Dump.
The system automatically generates a .dat file and dumps it to a specified file folder.
NOTE
The files are dumped to the path %IMAPROOT%\server\dump in Windows and $IMAPROOT/server/
dump/ in Solaris with the file name as current time.dat. For example, if the file is dumped at 16:30:40 on
July 15, 2007, then the file name is 20070715163040.dat.
5 Click OK.
----End
3.16.3 Deleting Information About Change Audit

This describes how to delete information about change audit.
Prerequisite
Context
The U2000 deletes the records in the database after information about change audit is deleted.
Thus, you cannot query the deleted records through the client.
Procedure
2 On the Change Audit tab, set query conditions and then click Query.
All records meeting the conditions are displayed in the query result area.
3 In the query result area, select one or more records to be deleted and then right-click them. Then,
select Delete.
----End
3.17 NE License Management

By using the NE license management function, you can query, apply for, install, and change NE
licenses. In addition, you can adjust capacities in licenses. By setting licenses for NEs, you can
obtain the rights to use certain functions according to service requirements. Because licenses
control NE validity periods or functions, you can understand the NE status in real time and
perform operations properly by using the license management function. Currently, only certain
versions of the OSN equipment, NG WDM equipment, OptiX PTN 910, and OptiX PTN 950
support this function.
3.17.1 Getting to Know NE License Management

This topic describes the scenarios and states that you need to understand for managing NE
licenses. By viewing operation scenarios, you can know how to manage NE licenses in different
scenarios. By viewing NE license states, you can judge whether licenses meet service
requirements.
3.17.2 Querying the NE License Information
By querying the NE license information, you can understand the status of NE licenses and find
out the NE licenses to be maintained.
3.17.3 Applying for an NE License
In certain situations such as NE installation, debugging, capacity adjustment, software upgrade,
and hardware replacement, you need to apply for an NE license.
3.17.4 Installing an NE License
You need to install a valid license file for an NE to ensure that communications between NEs
and NE functions are normal.
3.17.5 Synchronize NE Information
You can upload the ESN and license information of an NE to the U2000. This function is
applicable when an NE accesses the U2000 or after communications recovery after network
disconnection between an NE and the U2000.
3.17.6 Adjusting the NE License Capacity
You can adjust the capacity in an NE license to improve the license usage and flexibility and
reduce the maintenance cost of the carrier.
3.17.7 Changing an NE License
If an NE ESN changes or the capacity specified in a license is adjusted for the other NE, you
need to change the NE license.
3.17.1 Getting to Know NE License Management

This topic describes the scenarios and states that you need to understand for managing NE
licenses. By viewing operation scenarios, you can know how to manage NE licenses in different
scenarios. By viewing NE license states, you can judge whether licenses meet service
requirements.
NE License Operation Scenarios

The NE license operation scenarios include:
l Querying the NE license status. For details, see 3.17.2 Querying the NE License
Information.
l Applying for an NE license. For details, see 3.17.3 Applying for an NE License.
l Installing an NE license. For details, see 3.17.4 Installing an NE License.
l Changing the capacity specified in an NE license. For details, see 3.17.6 Adjusting the
NE License Capacity.
l Changing an equipment serial number (ESN) or NE license. For details, see 3.17.7
Changing an NE License.
NE License States
An NE license has five states. Before maintaining NE licenses, you need to familiarize yourself
with each state. Table 3-3 shows the NE license states.

Table 3-3 NE license states
State Description
No valid license file In this state, the NE license is incorrect, does not exist, or expires and
exceeds the protection period. The NE whose license is in this state is
unavailable.
Debugging During NE debugging, a dedicated NE license is usually applied for.

After this NE license is used, the NE license is in the Debugging state.
In this state, the NE is restricted based on the validity period, and all
functions run normally.
Commercial use When the NE license obtained from a commercial contract is used, this
License is in the Commercial use state. In this state, you can use the
resources and functions in the NE license.
Protected After an NE license expires, it has a protection period. In this period,

you can apply for a new license. In the protection period, all control
items in the NE license are available.
Critical In emergent situations such as a disaster, the NE license state can be

set to Critical. In this state, the NE license control is cancelled, and the
device capacity is set to the maximum. This prevents the NE services
from being damaged.
To set the NE license state to Critical, contact Huawei technical support
engineers.
3.17.2 Querying the NE License Information

By querying the NE license information, you can understand the status of NE licenses and find
out the NE licenses to be maintained.
Context
Table 3-4 shows the NE license states and related operations.
Table 3-4 States of the queried NE licenses and handling suggestions
States of the Handling Suggestions

Queried NE
licenses
No valid license file l After a commercial NE license is loaded, the state changes to
Commercial use.
l After a debugging NE license is loaded, the state changes to
Debugging.
Debugging After debugging, you need to load a commercial NE license, and then
the state changes to Commercial use.
Commercial use You do not need to handle it.

States of the Handling Suggestions

Queried NE
licenses
Protected After a commercial NE license is loaded, the state changes to

Commercial use.
Critical When the Critical state ends, contact Huawei technical support
engineers to go back to the Commercial use state.
Procedure
1 Choose Administration > NE License Management from the main menu.
2 On the NE License Management tab, click License Information Query in the NE License
Management navigation tree.
3 Click Filter.
NOTE
When you start the U2000 client and then access the NE License Management for the first time, the
Filter dialog box is displayed by default. If you close the Filter dialog box, you can choose License
Information Query in the navigation tree on the left of the NE License Management window, and then
click Filter to access the Filter dialog box.
1. In the Filter dialog box, select the license state to be queried from License status. Select
the NE software version to be queried from the Select version drop-down list.
2. In the Filter dialog box, click Select in the Device area.
3. In the Select NE dialog box, select the NE software version to be queried from the Select
version drop-down list in the Available device area.
4. In the Select NE dialog box, click , , , and to

select or remove devices from Available device and Selected devices.
5. In the Select NE and Filter dialog boxes, click OK.
4 In the license list, view NE Name, NE Description, NE Type, Version, ESN, and License
Status of the license.
5 Select an NE license record. In the Detail Message area, OperatorIndex, OperatorName,
LicenseItem, LicenseDesc, and AssignedValue are displayed.
6 Select one or more NE license records. Right-click them and choose Export Selected Record
or Export All Record to save the details of the queried NE licenses to the local computer.
----End
3.17.3 Applying for an NE License

In certain situations such as NE installation, debugging, capacity adjustment, software upgrade,
and hardware replacement, you need to apply for an NE license.
Context
The procedures for applying for an NE license are as follows:

1. Export the NE application information.

2. Apply for an NE license.
Procedure
2 In the NE License Management navigation tree, choose NE License Maintenance. On the

NE License Management tab, click Export NE Application Information.
3 In the Export NE Application Information dialog box, click Select.
4 In the Select NE dialog box, select an NE.

1. Select the required NE software version from the Select version drop-down list in the
Available device area.
2. In the Select NE dialog box, click , , , and to

select or remove devices from Available device and Selected devices. In the Select NE
dialog box, click OK.
5 Click next to Select export file.
6 In the Open dialog box, set the path and file for storing the exported NE license application file.
In the Open dialog box, click Open.
7 In the Export NE Application Information dialog box, click OK. The system exports the NE
application information to the specified location and provides a prompt.
8 Send the exported NE application information to Huawei technical support engineers to apply
for an NE license.
----End
3.17.4 Installing an NE License

You need to install a valid license file for an NE to ensure that communications between NEs
and NE functions are normal.
Prerequisite
The NE license file applied for exists on the local host.
Procedure
2 In the NE License Management navigation tree, choose NE License Maintenance.
3 Click Load License File.
4 In the Load License File dialog box, click .
5 In the Open dialog box, select a license file and click Open. Then click Next.

license File Loading Operation

Format Mode
TXT or DAT Single If the U2000 fails to automatically identify the NE matching
with a license, do as follows to manually match the license
with the NE:
1. In the Load License File dialog box, click Select.
2. In Select NE, change the version in the Select version
drop-down list.
a. Click , , , or
to change the devices in Selected
devices. Then click OK.
b. In the Load License File dialog box, click Finish.
ZIP Batch 1. On the right of the Load License File dialog box, right-
click a license file and choose Match.
2. In the Select NE dialog box, select an NE to be matched.
Then click OK.
In the Load License File dialog box, the ESN Name
column displays the matched NE.
3. In the Is Loaded column, select the license file to be
loaded.
4. Click Finish.
NOTE
In the steps for matching an NE, the matched license file list is displayed on the right of the Load License
File dialog box.
6 Click Finish.
----End
3.17.5 Synchronize NE Information

You can upload the ESN and license information of an NE to the U2000. This function is
applicable when an NE accesses the U2000 or after communications recovery after network
disconnection between an NE and the U2000.
Procedure
1 Choose Fault > Browse Current Alarm from the main menu.
3 Click Synchronize NE Information.
4 In the Synchronize NE Information dialog box, click Select.
5 In the Select NE dialog box, set the device for which you want to synchronize the NE
information. Click OK to go back to the Synchronize NE Information dialog box.

NOTE
Set the selected device: In the Select NE dialog box, click , , , or
to modify the NEs in Available devices.
6 In the Synchronize NE Information dialog box, click OK to synchronize the NE information.
----End
3.17.6 Adjusting the NE License Capacity

You can adjust the capacity in an NE license to improve the license usage and flexibility and
reduce the maintenance cost of the carrier.
Prerequisite
You have applied for a new NE license.
Context
l The U2000 supports the exchange of license capacities among different NEs. For example,
a carrier has NE A and NE B. The capacities specified in the licenses of both NEs are 50.
According to the service requirements, the capacity for NE B needs to increase to 80, and
that for NE A needs to decrease to 20. In the precondition that the total capacity specified
in the licenses of the carrier is unchanged, you can add the redundant capacity in the
license of NE A to the license of NE B by using the NE license capacity exchange function.
l When you adjust the NE license capacity, it changes the state of the old license to No valid
license file, and then applies the new NE license. After that, the adjustment is complete.
Procedure
3 Click Adjust License Capacity, then click Yes in the displayed dialog box.
The Confirm dialog box prompts that the license functions become invalid if you adjust the
license capacity.
4 In the Adjust License Capacity dialog box, click Select.
5 In the Select NE dialog box, move the NE to Selected devices. This indicates that you have
selected the NE whose license you want to adjust. Click OK.
6 In the Adjust License Capacity dialog box, click next to Select export file to set the name
of the file to be saved, and save NE license information. Click OK.
NOTE
Export the NE license information that you will use when applying for a new NE license.
7 In the NE License Management window, click Load License File to add the NE license applied
for to the U2000. For details, see 3.17.4 Installing an NE License.
----End

3.17.7 Changing an NE License

If an NE ESN changes or the capacity specified in a license is adjusted for the other NE, you
need to change the NE license.
Context
The procedures for changing an NE license are described as follows:
1. Invalidate the old NE license.
2. Apply for a new NE license.
3. Install the new NE license.
Procedure
1 Invalidate the old NE license.
1. Choose Administration > NE License Management from the main menu.
2. In the NE License Management navigation tree, choose NE License Maintenance.
3. Click Invalidate License.
4. In the confirm dialog box, confirm that you want to invalidate the NE license.
5. In the Invalidate License dialog box, click Select. In Select NE, change the version in the
Select version drop-down list.
6. Click , , or to change the devices in Selected

devices. Then click OK.
7. Click . In the Open dialog box, select a path for exporting a file, and then enter the
name of the file to be exported.
The U2000 exports the NE invalidation information to the file.
8. In the Invalidate License dialog box, click OK.
2 Apply for a new NE license. For details, see 3.17.3 Applying for an NE License.
3 Install the new NE license. For details, see 3.17.4 Installing an NE License.
----End

Operation Guide for Common Features 4 Log Management
4 Log Management
About This Chapter
The log records the operations and important system events on the U2000. You can use log
management to query and collect statistics on logs.
4.1 Getting to Know Log Management

You can understand conceptual knowledge of log management such as log management
functions and log types. The knowledge helps you to perform log operations.
4.2 Managing Operation Logs
You can query and collect statistics on operation logs of the U2000 to understand the operation
status of the U2000.
4.3 Managing System Logs
You can query and collect statistics on system logs of the U2000 to understand the running status
of the U2000.
4.4 Managing Security Logs
You can query and collect statistics on security logs of the U2000 to understand the security
operation status of the U2000.
4.5 Managing NE Logs
You can use this function of The U2000 to query, dump, and synchronize logs on the U2000
after the logs of the managed NEs are synchronized. The U2000 also provides the function of
collecting statistics on NE log commands.
4.6 Setting Log Templates
By setting log templates, you can save the specific query and statistical conditions in log
templates. This helps you to query and collect statistics on logs conveniently.
4.7 Setting a Log Forwarding Server
You can set a log forwarding server to forward the U2000 logs to a third-party server.
4.8 Managing Log Data
By dumping logs, you can periodically or manually clear the log information that is not required,
preventing the log information from occupying many resources. By exporting logs to files, you
can view logs and identify faults.
4.9 Managing NE Syslog

4 Log Management Operation Guide for Common Features
Syslog management provides the occurrence time, severity, and cause of a fault on a NE, which
helps you analyze and solve the problem.
4.10 Transferring NE Logs to Log Servers
The Syslog protocol allows you to transfer the logs of an NE to the log servers, in the format
defined by the Syslog protocol.

4.1 Getting to Know Log Management

You can understand conceptual knowledge of log management such as log management
functions and log types. The knowledge helps you to perform log operations.

4.1.2 Log Types
The U2000 has operation logs, system logs, security logs and NE logs. The four types of logs
record different log information.

Operation Log and Security Log

Operations and operation results of all the U2000 users are recorded in the U2000 operation log
or security log.
l U2000 operation log: Records user operations irrelevant to the security on the client. For
example, scheduled alarm acknowledgement and NE time synchronization.
l U2000 security log: Records user operations relevant to the security on the client. For
example, creating a user and setting the user operation rights.
The U2000 provides a log browse function. You can also filter logs according to operation user,
operation terminal, log type, severity level, and start and end time.
By querying logs, the administrator can track and check user operations. Pay close attention to
operation logs. This helps you to learn the running information of the system. The logs keep a
record of events relevant to the equipment operations. For example, querying, creating, and
deleting an NE or other objects. The logs also help you to learn the user activities. For example,
you can view operations performed by a user in the system.
NE Security Log
Operations and operation results of all the NE users are recorded in the NE security log. The
U2000 provides an NE log browse function. You can also filter the logs according to the NE
user name, event name, and start and end time. You can view but not delete the NE security log.
Log Dump
By setting the scheduled task dump, you can enable the U2000 to periodically save the log to a
specified directory. This function facilitates log viewing, reduces records in the database, and
speeds up the running of the system. By default, the dump path of the security log is NMS
installation path/server/dump/ThresholdExport/Log. The dumped log can be saved in CSV
or XML format.

Log Forwarding
U2000 log forwarding: The U2000 can forward the U2000 operation log to the Syslog server,
and save all operations. This function provides references for maintenance and relieves the
storage burden of the U2000 server.
NE log forwarding: The U2000 forwards various types of NE information to the Syslog server
in a format that complies with the system log protocol. Network management and maintenance
personnel can learn the NE status according to emergency of the information.
4.1.2 Log Types

The U2000 has operation logs, system logs, security logs and NE logs. The four types of logs
record different log information.
4.1.2.1 Security Logs
This topic describes the meaning, path, and parameters of security logs. In security logs, the
maintenance personnel can view security information that the U2000 records. In addition, by
collecting statistics on security logs, you can count the number of statistics items based on the
statistics conditions.
4.1.2.2 Operation Logs
This topic describes the meaning, path, and parameters of operation logs. In operation logs, the
maintenance personnel can view the user operation information that the U2000 records. In
addition, by collecting statistics on operation logs, you can count the number of statistics items
based on the statistics conditions.
4.1.2.3 NE Syslog
U2000 NE logs record the operations on the managed NEs. The U2000 NE syslog running logs
record the running information about U2000 NEs. The NE syslog operation logs and NE syslog
running logs help you to know the NE running information.
4.1.2.4 System Logs
This topic describes the meaning, path, and parameters of system logs. In system logs, the
maintenance personnel can view the system operation information that the U2000 records. In
addition, you can collect statistics on system logs based on the log severity or source.
4.1.2.1 Security Logs

This topic describes the meaning, path, and parameters of security logs. In security logs, the
maintenance personnel can view security information that the U2000 records. In addition, by
collecting statistics on security logs, you can count the number of statistics items based on the
statistics conditions.
Description
Security logs record the security operations that the user performs in the U2000, for example,
login, logout, locking, and unlocking.
Path
Security logs are stored in the database. You can query them through the client. The entry for
querying security logs through the client is Administration > Log Management > Query
Security Logs.
Security logs can be dumped to a file from the database. The navigation path is
Administration > Task Schedule > Task Management. By default, the dump path of the

security logs is $installation path of the NMS/dump/ThresholdExport/Log(Solaris/

Linux), %installation path of the NMS%\dump\ThresholdExport\Log(Windows).
After the security logs are dumped, the U2000 generates the relative folder and log file.
l Folder: The folder is named in the format YYMMDD in the dump path. "YYMMDD"
indicates the date when the security logs are dumped.
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-
security-log-dateThreshold_info.xml and YYMMDDHHMMSS-security-log-
dateThreshold-Number.Filename extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix -
Number.Filename extension saved the dumped logs.
NOTE
Security logs can be dumped to a .csv or .xml file, and the file can be compressed to a .zip package.
Parameters
Parameter Name Parameter Meaning
Security Event Event that is related to U2000 security.
Risk Level Level of risks caused by the operations that

are performed on the U2000. There are three
risk levels: Warning, Minor, and Risk.
Operation User U2000 user.
User Type Type of an U2000 user.
Operation Time Time when an operation is performed. It is

accurate to second.
Operation Terminal IP address of the host where an operation is

performed.
Operation Object Object that an operation is performed on.
Operation Result Result of an operation: succeeded, failed or

partly succeeded.
Details Other useful information about an operation.
4.1.2.2 Operation Logs

This topic describes the meaning, path, and parameters of operation logs. In operation logs, the
maintenance personnel can view the user operation information that the U2000 records. In
addition, by collecting statistics on operation logs, you can count the number of statistics items
based on the statistics conditions.
Description
Operation logs record the information about the non-security operations that the user performs
in the U2000, for example, muting and unmuting the alarm sound.

Path
Operation logs are stored in the database. You can query them through the client. The entry for
querying operation logs through the client is Administration > Log Management > Query
Operation Logs.
Operation logs can be dumped to a file from the database. The navigation path is
operation logs is $installation path of the NMS/dump/ThresholdExport/Log(Solaris/
Linux), %installation path of the NMS%\dump\ThresholdExport\Log(Windows).
After the operation logs are dumped, the U2000 generates the relative folder and log file.
indicates the date when the operation logs are dumped.
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-
operation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-log-
dateThreshold-Number.Filename extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix -
Number.Filename extension saved the dumped logs.
NOTE
Operation logs can be dumped to a .csv or .xml file, and the file can be compressed to a .zip package.
Parameters
Operation Name Name of an operation that a user performs on

the U2000.
Risk Level Levels of risks caused by the operations that

are performed on the U2000: Warning,
Minor, and Risk.
Operation User U2000 user.
User Type Type of an U2000 user.
Operation Time Time when an operation executes. It is

accurate to second.
Operation Category Type of an U2000 operation.
Operation Terminal IP address of the host where an operation is

performed.
Operation Object Object that an operation is performed on.
Operation Result Result of an operation: succeeded, failed and

partly succeeded.

4.1.2.3 NE Syslog
U2000 NE logs record the operations on the managed NEs. The U2000 NE syslog running logs
record the running information about U2000 NEs. The NE syslog operation logs and NE syslog
running logs help you to know the NE running information.
Description
NE syslog operation logs record the operations on the managed NEs. You can query the NE
syslog operation logs through the U2000 client GUI. You do not need to query the NE syslog
operation logs on each NE.
The NE syslog running logs record the running information of U2000 NEs. By obtaining all NE
syslog running logs from NEs through the U2000, you can view the NE syslog running logs
managed by the U2000 through the U2000, instead of viewing the NE syslog running logs on
each NE.
Path
The entry for querying NE syslogs through the client is Administration > NE Security
Management > NE Syslog Run Log.
NE syslog operation logs are saved in client/report(Solaris/Linux) or client\report

(Windows). The path description is as follows.
Path Description
client/report (Solaris/Linux) NEs logs in this path record the NMS user
client\report (Windows) operations on the U2000. The naming
convention of NE logs is
DevLog_year_month_day_hour_minute_se
cond.a suffix.
The suffix of the log file name supports
the .csv, .html, .txt, and .xls formats.
NE syslog running logs are saved in server/log/syslog(Solaris/Linux) or server\log\syslog

(Windows). The path description is as follows.
Path Description
server/log/syslog(Solaris/Linux) The NE syslog running logs in this directory

server\log\syslog(Windows) record the results of operations performed on
U2000 NEs.
The NE syslog running log files are named in
the format of
year_month_day_hour_minute_second.a
suffix.
The suffix of a log file name can be .txt
or .zip.

Parameters
NE Name The name of the NE managed by the NMS.
Time The specific time when an operation is

performed. It is accurate to second.
User Name The user name of the NE managed by the

NMS.
Access Method The access method of a NE user for NEs.
IP Address The IP address of the host used to perform an

operation.
User Command The command used to perform operations on

the NE.
Result There are four kinds of operation results:

Failed, Succeeded, Unknown, and - .
NOTE
l Unknown: Other NE operation results
reported in MML mode are displayed as
Unknown except for succeeded and failed
operation results.
l -: There is no Result in the NE operation logs
reported in SNMP mode. Therefore, the NE
operation logs reported in SNMP mode are
displayed as -.
Memo The remark for NE operation logs.
User Command Detail The details of the commands used by the user.
NE Name The name of the NE managed by the NMS.
IP Address The IP address of the NE managed by the

NMS.
Digest The digest of the NE syslog running log.
Content The details of the NE syslog running log.
Module Name The name of the module corresponding to the

NE syslog running log.
Level The level of the NE syslog running log.
Sending Time The time when the NE syslog running log is

sent.

4.1.2.4 System Logs

This topic describes the meaning, path, and parameters of system logs. In system logs, the
maintenance personnel can view the system operation information that the U2000 records. In
addition, you can collect statistics on system logs based on the log severity or source.
Description
System logs record the operations or tasks that the U2000 performs automatically, for example,
scheduled tasks and system tasks.
Path
System logs are stored in the database. You can query them through the client. The entry for
querying system logs through the client is Administration > Log Management > Query
System Logs.
System logs can be dumped to a file from the database. The navigation path is
system logs is $installation path of the NMS/dump/ThresholdExport/Log(Solaris/Linux),
%installation path of the NMS%\dump\ThresholdExport\Log(Windows).
After the system logs are dumped, the U2000 generates the relative folder and log file.
indicates the date when the system logs are dumped.
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-system-
log-dateThreshold_info.xml and YYMMDDHHMMSS-system-log-dateThreshold-
Number.Filename extension. The file with the suffix _info.xml saves the configuration
information of the dumped logs, and the file with the suffix -Number.Filename
extension saved the dumped logs.
NOTE
System logs can be dumped to a .csv or .xml file, and the file can be compressed to a .zip package.
Parameters
Level Levels of risks caused by the operations

performed on the U2000: Warning, Minor,
and Risk.
Source Module where the U2000 performs an

operation.
Time Time when an operation is performed. It is

accurate to second.
Basic Information Information about basic operations.
Operation Result Result of an operation: succeeded, failed or

unkonwn.

4.2 Managing Operation Logs

You can query and collect statistics on operation logs of the U2000 to understand the operation
status of the U2000.
4.2.1 Querying Operation Logs

You can query operation logs to know the operation records of the U2000.
4.2.2 Collecting Statistics on Operation Logs
You can know the operation status by collecting statistics and analyzing operation logs. For
example, you can know the period during which a maximum number of operations are performed
and the operations that are performed most frequently.
4.2.1 Querying Operation Logs

You can query operation logs to know the operation records of the U2000.
Context
l When you query operation logs by user name, only names of the users that have performed
operations are displayed under Available Operation User in the Select Operation User
dialog box.
l The statistical result is generated based on the existing data in the database. If the database
is empty, there is no statistical result.
Procedure
1 Choose Administration > Log Management > Query Operation Logs from the main menu.
2 In the Filter window, set the filtering conditions, and then click OK.

NOTE
You can also click Cancel, and then query logs in the Query Operation Logs window in the following
ways:
l Click Template Filter, and then select Open. Select a template from the template list, and then click
Open to use an existing template to query logs. If no template exists on the U2000, see 4.6 Setting
Log Templates to create a template.
l Click Filter. Set the query conditions in the Filter dialog box, and then click OK to query logs.
----End
4.2.2 Collecting Statistics on Operation Logs

You can know the operation status by collecting statistics and analyzing operation logs. For
example, you can know the period during which a maximum number of operations are performed
and the operations that are performed most frequently.
Context
The statistical result is generated based on the existing data in the database. If the database is
empty, there is no statistical result.

Procedure
1 Choose Administration > Log Management > Operation Log Statistics from the main
menu.
2 In the Statistic Filter window, set the statistical items and statistical conditions, and then click
OK.
NOTE
You can also click Cancel, and then collect statistics in the Operation Log Statistics window in the
following ways:
l Click Template, and then select Open. Select a template from the template list, and then click Open
to use an existing template to collect statistics on operation logs. If no template exists on the U2000,
see 4.6 Setting Log Templates to create a template.
l Click Statistic Filter. Set Statistical Items and Filter Condition in the Statistic Filter window, and
then click OK to collect statistics on operation logs.
----End
Result
In the Operation Log Statistics window, the statistical result is displayed.
Perform the following operations as required:

l Click Print to print the statistical result.

l Click Save As to save the statistical result.
4.3 Managing System Logs

You can query and collect statistics on system logs of the U2000 to understand the running status
of the U2000.
4.3.1 Querying System Logs

You can query system logs to know the important events that occur when the U2000 is running.
4.3.2 Collecting Statistics on System Logs
You can know the system status by collecting statistics and analyzing the system log. For
example, you can know the type of the services that raise the most alarms.
4.3.1 Querying System Logs

You can query system logs to know the important events that occur when the U2000 is running.
Context
Procedure
1 Choose Administration > Log Management > Query System Logs from the main menu.

NOTE
You can also click Cancel, and then query logs in the Query System Logs window in the following ways:
Open to use an existing template to query logs. If no template exists on the U2000, see 4.6 Setting
Log Templates to create a template.
l Click Filter. Set the query conditions in the Filter window, and then click OK to query logs.
----End
4.3.2 Collecting Statistics on System Logs

You can know the system status by collecting statistics and analyzing the system log. For
example, you can know the type of the services that raise the most alarms.
Context
Procedure
1 Choose Administration > Log Management > System Log Statistics from the main menu.
2 In the Statistic Filter window, set the statistical condition, and then click OK.

NOTE
You can also click Cancel, and then collect statistics in the System Log Statistics window in the following
ways:
to use an existing template to collect statistics on system logs. If no template exists on the U2000, see
4.6 Setting Log Templates to create a template.
l Click Statistic Filter. Set the statistical condition in the Statistic Filter window, and then click OK
to collect statistics on system logs.
----End
Result
In the System Log Statistics window, the statistical result is displayed.
4.4 Managing Security Logs

You can query and collect statistics on security logs of the U2000 to understand the security
operation status of the U2000.
4.4.1 Querying Security Logs

You can query security logs to know the security operations of the U2000.
4.4.2 Collecting Statistics on Security Logs
You can know the security operations by collecting statistics and analyzing security logs. For
example, you can know the period during which maximum number of security operations are
performed and the operations that are performed most frequently.
4.4.1 Querying Security Logs

You can query security logs to know the security operations of the U2000.
Context
Procedure
1 Choose Administration > Log Management > Query Security Logs from the main menu.

NOTE
You can also click Cancel, and then query logs in the Query Security Logs window in the following ways:
Open to use an existing template to query logs.
If no template exists on the U2000, see 4.6 Setting Log Templates to create a template.
l Click Filter. Set the query conditions in the Filter window, and then click OK to query logs.
----End
4.4.2 Collecting Statistics on Security Logs

You can know the security operations by collecting statistics and analyzing security logs. For
example, you can know the period during which maximum number of security operations are
performed and the operations that are performed most frequently.
Context

Procedure
1 Choose Administration > Log Management > Security Log Statistics from the main menu.
2 In the Statistic Filter window, set the statistical items and filtering conditions, and then click
OK.
NOTE
You can also click Cancel, and then collect statistics in the Security Log Statistics window in the following
ways:
to use an existing template to collect statistics on security logs. If no template exists on the U2000, see
4.6 Setting Log Templates to create a template.
l Click Statistic Filter. Set Statistical Items and Filter Condition in the Statistic Filter window, and
then click OK to collect statistics on security logs.
----End
Result
In the Security Log Statistics window, the statistical result is displayed.

4.5 Managing NE Logs

You can use this function of The U2000 to query, dump, and synchronize logs on the U2000
after the logs of the managed NEs are synchronized. The U2000 also provides the function of
collecting statistics on NE log commands.
4.5.1 Browsing the NE Syslog Operation Logs

By obtaining all the NE syslog operation logs through U2000 at the NE side, you can browse
the NE syslog operation logs of the NEs managed by the U2000 on the U2000 rather than query
the operation logs on each NE.
4.5.2 Browsing the NE Syslog Running Logs
By obtaining all the NE syslog running logs through U2000 on the NE side, you can browse the
NE syslog running logs of the NEs managed by the U2000 on the U2000, rather than query the
running logs on each NE.
4.5.3 Synchronizing SNMP Device Logs
You can synchronize the SNMP device logs to the U2000. This helps you to view the SNMP
device logs.
4.5.1 Browsing the NE Syslog Operation Logs

By obtaining all the NE syslog operation logs through U2000 at the NE side, you can browse
the NE syslog operation logs of the NEs managed by the U2000 on the U2000 rather than query
the operation logs on each NE.
Prerequisite
l You must be an NMS user with the Security Watcher authority or higher.
l The parameters on the NE side must be set correctly.
CAUTION
In Solaris, both the NMS syslog process and the Solaris syslogd service use the UDP port 514
to collect information. Because of the port occupation conflict, two services cannot be used at
the same time. Thus, the Solaris syslogd service must be disabled. You can use one of the
following methods to disable the Solaris syslogd service:
l Run the following command in the terminal window:
#syslogd -t
The command is applicable to the current configuration only. If the operating system (OS)
restarts, you need to run this command again.
l Modify the file /etc/default/syslogd:
Modify the last line LOG_FROM_REMOTE=YES to LOG_FROM_REMOTE=NO,
delete the number sign (#) in this line, and save the file. Then restart the system.

Context
l This feature is used to browse the NE syslog operation logs related to MA5606T,
MA5680T, and MA5600T.
l Normal users can query only the logs of the NEs of their own management domains.
l admin can query NE logs of all users.
Procedure
1 Log in to the System Monitor client, and check whether SyslogCollectorDM is started. If it is
not started, select the process, right-click, and then choose Start Process.
2 Telnet to the device whose log needs to be viewed, and switch to the privilege mode. Run the
loghost add ip-addr hostname command to add a Syslog server.
NOTE
The ip-addr parameter indicates the IP address of the U2000 server, and the hostname parameter indicates
the name of the U2000 server.
3 Run the loghost activate name hostname command to activate the Syslog server.
NOTE
The hostname parameter indicates the name of the U2000 server.
4 Run the display loghost list command. If the returned message includes the IP address and name
of the added Syslog server, and the Terminal state parameter is Normal, it indicates that the
Syslog server is configured successfully.
5 1.2.7 Logging In to the U2000 Client.
6 Synchronize the network-wide SNMP NE logs. For details, see 4.5.3 Synchronizing SNMP
Device Logs.
7 Choose Administration > NE Security Management > NE Syslog Operation Logs from the
main menu.
8 In the NE Syslog Operation Logs window, double-click a record to view the log details.
l Click a field in the header of the query result table to sort the query results by field.
l A white upward triangular icon indicates that you can sort the results by field. A black
upward triangular icon indicates that the results are sorted in the ascending order by
field. The black downward triangular icon indicates that the results are sorted in the
descending order by field.
l Click the NE Name, Access Method, or Result field. Different from other table header
fields, these fields are displayed in groups. Therefore, they are not sorted in alphabetic
order.
9 Choose to perform the following operations:

l Click Filter. In the Filter dialog box, set the conditions to filter the NE logs you browse.
l Click Refresh to refresh the NE logs.
----End

4.5.2 Browsing the NE Syslog Running Logs

By obtaining all the NE syslog running logs through U2000 on the NE side, you can browse the
NE syslog running logs of the NEs managed by the U2000 on the U2000, rather than query the
running logs on each NE.
Prerequisite
l You must be a U2000 user with the Security Watcher authority or higher.
l You must configure the information center on the NE side so that the NE syslog running
logs can be sent to the U2000. For details about configure the information center on the
NE side , refer to 4.9.2 Configuring the Information Center on the NEs.
l Configure the U2000 server as the receiver of NE logs. That is, set Log Host IP Address
to the IP address of the U2000 server. For details, see 4.9.2.3 Adding the Syslog Host.
Context
admin can query the NE syslog running logs of all applicable NEs.
Procedure
1 Choose Administration > NE Security Management > NE Syslog Run Log from the main
menu.
2 In the DRL File List navigation tree, double-click a NE syslog running log file, such as
20090824142136. In the right-hand pane, click a record to view log details.

NOTE
l The files in the DRL file list are ordered by time.

l You can enter the file name in the text box above the DRL File List navigation tree to filter the DRL
files. Only numbers from 0 to 9 are allowed. Then, the matched files are displayed in the DRL File
List navigation tree.
3 Perform the following operations as required:

Click Condition. In the Set Filter Condition dialog box that is displayed, set the filter criteria
for filtering out NE syslog running logs.
----End
4.5.3 Synchronizing SNMP Device Logs

You can synchronize the SNMP device logs to the U2000. This helps you to view the SNMP
device logs.
Procedure
1 Choose Administration > NE Security Management > Synchronize SNMP NE Logs of ALL
Nes from the main menu.
2 In the displayed dialog box, click OK.
----End
4.6 Setting Log Templates

By setting log templates, you can save the specific query and statistical conditions in log
templates. This helps you to query and collect statistics on logs conveniently.
Context
The operations on the log query template and log statistics template are similar.
Procedure
1 Choose Administration > Log Management from the main menu.
2 Among the displayed menus, you can choose Query Operation Logs, Query System Logs,
Query Security Logs, Operation Log Statistics, System Log Statistics and Security Log
Statistics. The following takes the template for querying and collecting statistics on operation
logs as an example.

Task Operation
Create a template 1. Choose Administration > Log Management > Query Operation
Logs.
2. In the Filter dialog box, click Cancel.
For the operation of collecting statistics on logs, the Statistic
Filter dialog box is displayed. Click Cancel.
3. In the Query Operation Logs window, click Template Filter and
choose New.
For the operation of collecting statistics on logs, click Template in
the window for collecting statistics on logs and then choose New.
4. In the Enter the Template Name dialog box, enter the template
name, and then click OK.
5. In the Filter dialog box, set the filtering conditions of template
parameters, and then click OK.
Modify a template If there is already a log query template or a log statistics template on
the U2000, you can do as follows to modify the template:
1. In the window for querying or collecting statistics on logs, click
Template Filter. Among the displayed menus, choose Open. The
Open dialog box is displayed. Select a template.
2. Modify the operations in the template.
l Querying logs
a. In the window for querying logs, click Filter.
b. In the Filter dialog box, modify the query conditions in the
log template, and then click OK.
c. In the window for querying logs, click Template Filter.
Among the displayed menus, choose Save.
l Collecting statistics on logs
a. In the window for collecting statistics on logs, click Statistic
Filter.
b. In the Statistic Filter dialog box, modify the statistical
conditions in the log template, and then click OK.
c. In the window for collecting statistics on logs, click
Template. Among the displayed menus, choose Save.
Save You can do as follows to save and modify a log query or statistics
template:
l In the window for querying logs, click Template Filter. Among
the displayed menus, choose Save.
l In the window for collecting statistics on logs, click Template.
Among the displayed menus, choose Save.

Task Operation
Save As You can do as follows to save and modify a log query or statistics
template:
l In the window for querying logs, click Template Filter. Among
the displayed menus, choose Save As.
l In the window for collecting statistics on logs, click Template.
Among the displayed menus, choose Save As.
Delete a template If there is already a log query template or a log statistics template on
the U2000, you can do as follows to delete the template:
1. Delete the operations in the template.
l In the window for querying logs, click Template Filter.
l In the window for collecting statistics on logs, click
Template.
2. Click Delete.
3. In the displayed Delete dialog box, select the specified template.
4. Click Delete.
----End
4.7 Setting a Log Forwarding Server

You can set a log forwarding server to forward the U2000 logs to a third-party server.
Context
The log forwarding server forwards only security logs and operation logs.
Procedure
1 Choose Administration > Settings > Log Forwarding Server from the main menu.

2 You can perform the following operations in the Log Forwarding Server window.
Task Operation
Add In the Create Log Forwarding Server dialog box, set the server that receives the
logs.
l To enable the log forwarding function, select Yes from the Enable drop-down
list.
l The IP address cannot be set to a loopback address.
l String Filter does not support wildcards.
l The switchover between the primary and secondary servers is supported when
the value of Protocol is TCP. When the primary sever fails, the secondary server
takes over the service and receives the logs. When the primary server is recovered,
the service is switched back to the primary server.
l You can set a maximum of five servers to receive logs.
Modify In the Log Forwarding Servers dialog box, select a server record, and then click
Modify. In the displayed Modify Log Forwarding Server dialog box, set the server
information of logs.
Delete In the Log Forwarding Servers dialog box, select a server record, and then click
Delete.
Refresh To refresh the server information.

NOTE
After another user updates the information about the log forwarding server, you can click
Refresh to obtain the updated information. The U2000 does not automatically update the
information about the log forwarding server.

Task Operation
Cancel To exit the Log Forwarding Server dialog box.
----End
4.8 Managing Log Data

By dumping logs, you can periodically or manually clear the log information that is not required,
preventing the log information from occupying many resources. By exporting logs to files, you
can view logs and identify faults.
4.8.1 Setting U2000 Log Timing Dumping

By setting U2000 log dump, you can periodically or instantly dump security logs, operation logs,
and system logs of the U2000. The dumped logs are saved in files and deleted from the database.
This prevents database space insufficiency.
4.8.2 Setting U2000 Log Overflow Dump
The U2000 supports log overflow dump. When the capacity of logs reaches the specified
threshold, the U2000 periodically dump logs. Dumped logs are saved in files and deleted from
the database. This prevents database space insufficiency.
4.8.3 Manually Dumping U2000 Logs
The U2000 supports the function of manually dumping logs. Dumped logs are saved in files and
deleted from the database. This prevents database space insufficiency.
4.8.4 Setting U2000 Log Export
By setting U2000 log export, you can periodically or instantly export security logs, operation
logs, and system logs of the U2000. The exported logs are saved in files. Thus, they cannot be
deleted from the database.
4.8.1 Setting U2000 Log Timing Dumping

Context
Each of the types Operation Log Dump, Security Log Dump and System Log Dump has a
default system task that is provided by the U2000. You are not allowed to delete this system
task, but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
2 In the Task Type navigation tree, choose Database Capacity Management > Alarm/Event
Log Dump,Database Capacity Management > Operation Log Dump,Database Capacity
Management > Security Log Dump or Database Capacity Management > System Log
Dump.

3 Double-click the task in the task list.

NOTE
In the task list, right-click the log dump task and choose Run At Once. The log dump task is performed
instantly.
4 In the displayed Attribute dialog box, set the parameters on the Common Parameters and
Extended Parameters tabs. For the parameter descriptions, see Setting Log Dump and Export.
5 Click OK.
----End
4.8.2 Setting U2000 Log Overflow Dump

The U2000 supports log overflow dump. When the capacity of logs reaches the specified
threshold, the U2000 periodically dump logs. Dumped logs are saved in files and deleted from
the database. This prevents database space insufficiency.
Context
Each of the types Operation Log Overflow Dump, Security Log Overflow Dump and System
Log Overflow Dump has a default system task that is provided by the U2000. You are not
allowed to delete the system task, but you can modify its setting. In addition, you cannot create
new tasks of these three types.
Procedure
2 In the Task Type navigation tree, choose Overflow Dump > Operation Log Overflow
Dump, Overflow Dump > Security Log Overflow Dump or Overflow Dump > System Log
Overflow Dump.select the type of the log overflow dump task, and then double-click the
selected log dump task in the right area.
NOTE
In the right area, right-click the log dump task and choose Run At Once. The log dump task is performed
instantly.
4 In the Attribute dialog box, modify the parameters on the Common Parameters and Extended
Parameters tabs. For the parameter descriptions, see Setting Log Dump and Export.
5 Click OK.
----End
4.8.3 Manually Dumping U2000 Logs

The U2000 supports the function of manually dumping logs. Dumped logs are saved in files and
deleted from the database. This prevents database space insufficiency.
Context
Each of the types Operation Log Manual Dump, Security Log Manual Dump and System
Log Manual Dump has a default system task that is provided by the U2000. You are not allowed

to delete the system task, but you can modify its setting. In addition, you cannot create new tasks
of these three types.
Procedure
2 In the navigation tree on the left of the Task Management window, choose Manual Dump >
Operation Log Manual Dump,Manual Dump > Security Log Manual Dump or Manual
Dump > System Log Manual Dump.
3 In the task list, right-click Manual Dumpand task and choose Run.
4 In the Attribute dialog box, set the dump parameters.

NOTE
l Dumping to (path) indicates the path of the dump file. The dump file is stored on the U2000 server.
The path of manually dumped log data is %installation path of the NMS%\dump\ThresholdExport
\Log in windows and $installation path of the NMS/dump/ThresholdExport/Log in Solaris and
Linux.
l For details on the dump parameters, see Manually Dumping U2000 Logs.
Dumping to (path) indicates the path of the dump file. The dump file is stored on the U2000 server. The
path of manually dumped log data is %installation path of the NMS%\dump\ThresholdExport\Log in
windows and $installation path of the NMS/dump/ThresholdExport/Log in Solaris and Linux.
5 Click Dump to dump log.
----End

4.8.4 Setting U2000 Log Export

By setting U2000 log export, you can periodically or instantly export security logs, operation
logs, and system logs of the U2000. The exported logs are saved in files. Thus, they cannot be
deleted from the database.
Context
Each of the types NM Operation Log Export, NM Security Log Export and NM System Log
Export has a default system task that is provided by the U2000. You are not allowed to delete
the system task, but you can modify its setting. In addition, you cannot create new tasks of these
three types.
Procedure
2 In the Task Type navigation tree, choose File Interface > NM Operation Log Export,File
Interface > NM Security Log Export or File Interface > NM System Log Export.
NOTE
To perform the operations such as executing an export task instantly, suspending an task, and setting timing
suspending and resuming, right-click the log export task in the right area and choose the corresponding
menus.
4 In the Attribute dialog box, set the parameters on the Common Parameters and Extended
Parameters tabs. For the parameter descriptions, see Setting Log Dump and Export.
5 Click OK.
----End
4.9 Managing NE Syslog

Syslog management provides the occurrence time, severity, and cause of a fault on a NE, which
helps you analyze and solve the problem.
This feature is related to routers, switches, and service gateways.
4.9.1 Syslog Management Overview
This describes basic concepts and functions of Syslog Management.
4.9.2 Configuring the Information Center on the NEs
This describes how to configure the information center on the NEs. You need to configure the
information center on the NEs before using the Syslog management function of the U2000.
4.9.1 Syslog Management Overview

This describes basic concepts and functions of Syslog Management.
4.9.1.1 Functions of Syslog Management

Syslog management can implement functions such as sending, receiving, and parsing Syslog
packets sent by a NE. It also provides the functions of querying NE syslog running logs.

4.9.1.2 Basic Concepts

This describes basic concepts of Syslog management.
4.9.1.1 Functions of Syslog Management

Syslog management can implement functions such as sending, receiving, and parsing Syslog
packets sent by a NE. It also provides the functions of querying NE syslog running logs.
NE logs record various situations occurred during the NE operation in real time. Logs can be
exported to the log buffer, log file, console, terminal display, and log host for storage and
browsing. When a fault occurs and you need to know the NE syslog running information, you
can query the logs to locate the fault. Because the disk space of the NEis limited, the U2000
Syslog management can implement functions such as receiving, parsing, and viewing Syslog
packets sent by the NEs.
4.9.1.2 Basic Concepts

This describes basic concepts of Syslog management.
Syslog Packets
The output format of the NE log is Syslog. To enable the NMS to receive Syslog packets sent
by the NEs, you need to configure related commands for sending log information to the log host
on the NEs. Syslog packets are transmitted through the User Datagram Protocol (UDP) and sent
to the log host (the U2000) through port 514. The U2000 parses and writes the received Syslog
packets to the database. Then you can query NE logs on the U2000 client.
4.9.2 Configuring the Information Center on the NEs

This describes how to configure the information center on the NEs. You need to configure the
information center on the NEs before using the Syslog management function of the U2000.
CAUTION
In Solaris, both the NMS syslog process and the Solaris syslogd service use the UDP port 514
to collect information. Because of the port occupation conflict, two services cannot be used at
the same time. Thus, the Solaris syslogd service must be disabled. You can use one of the
following methods to disable the Solaris syslogd service:
l Run the following command in the terminal window:
#syslogd -t
The command is applicable to the current configuration only. If the operating system (OS)
restarts, you need to run this command again.
l Modify the file /etc/default/syslogd:
Modify the last line LOG_FROM_REMOTE=YES to LOG_FROM_REMOTE=NO,
delete the number sign (#) in this line, and save the file. Then restart the system.
4.9.2.1 Enabling the Information Center

This describes how to enable the information center. You need to enable the information center
before configuring parameters of the information center on the NEs.

4.9.2.2 Configuring the Syslog Source Interface

This describes how to configure the service status of Syslog source interface. After you configure
a specified interface IP address for the Syslog service, the log host can classify logs according
to the source IP address.
4.9.2.3 Adding the Syslog Host
This describes how to configure the IP Address, channel number, log tool, and log language of
the log host.
4.9.2.4 Configuring the Advanced Attributes of the Syslog Service
This describes how to set the parameters about log buffer and the channel number of a log file.
4.9.2.1 Enabling the Information Center

This describes how to enable the information center. You need to enable the information center
before configuring parameters of the information center on the NEs.
Context
l After the information center is enabled, the classification and output of information
(especially much information for processing) may affect the system performance to some
extent.
l By default, the information center is enabled. You can use the display info-center
command to check the information center status.
If
Information Center:enabled
is displayed, the information center is enabled.
If this information is not displayed, do as follows to enable the information center.
Procedure
1 Run the system-view command to enter the system view.
2 Run the info-center enable command to enable the information center.
----End
4.9.2.2 Configuring the Syslog Source Interface

This describes how to configure the service status of Syslog source interface. After you configure
a specified interface IP address for the Syslog service, the log host can classify logs according
to the source IP address.
Prerequisite
l The selected NE supports the log service function on the U2000.
l The NE is configured with Telnet/STelnet parameters and its configurations are
synchronized to the U2000.
l The Syslog source interface and its IP address are known.

Procedure
1 In the topology navigation tree or the topology view, select the NE to be operated and right-click
it. Then select NE Explorer on the shortcut menu.
2 In the service tree, expand NE Channel Management, and then click Syslog Service.
3 Click Enable or Disable to change the service status of the Syslog source interface.
NOTE
If the Syslog source of the host is in use, you cannot select the Syslog source interface from the drop-down
list box. The displayed status button is Disable. Click Disable to disable the log source. Then you can
select the Syslog source interface from the drop-down list box. The displayed status button changes to
Enable.
4 When the Syslog source is disabled, select the source interface for sending Syslog files, and then
click Enable.
----End
4.9.2.3 Adding the Syslog Host

This describes how to configure the IP Address, channel number, log tool, and log language of
the log host.
Prerequisite
The IP address of the log host is known.
Procedure
3 Right-click on the Syslog Service tab and select Create on the shortcut menu.
4 In the Create Log Host dialog box, set the related parameters.
5 Click OK or Apply.

NOTE
If more than one log host is added, the Create Log Host progress bar is displayed.
After all the log hosts are added, click OK.
----End
4.9.2.4 Configuring the Advanced Attributes of the Syslog Service

This describes how to set the parameters about log buffer and the channel number of a log file.
Procedure
3 On the Syslog Service tab, click Advanced.
4 In the Advanced dialog box, set the related parameters.
5 Click OK.
----End
4.10 Transferring NE Logs to Log Servers

The Syslog protocol allows you to transfer the logs of an NE to the log servers, in the format
defined by the Syslog protocol.
Context
NOTE
Applies to the SDH and WDM series NEs.
4.10.1 Syslog Service

The syslog service is a part of the NE security management. All types of information is
transmitted to the syslog server. All this information is in the format defined by the syslog
protocol. The network administrator and maintainer can estimate the status of the NEs based on
the severities of these information.

4.10.2 Configuring the Syslog Server

In the case of NEs that can communicate with syslog servers directly, you need to configure the
syslog server on the NEs. Then, the NEs can transmit the syslog to the syslog server.
4.10.3 Configuring the Syslog GNE
In the case of For the NEs that cannot communicate with the syslog server directly, you need to
configure the syslog GNE. The syslog GNE transmits all the syslog that it receives d to the syslog
server.
4.10.4 Configuring the Syslog Type and Severity
Different types of syslog have different severities. The NE report the relevant information based
on the severity of the syslog.
4.10.5 Starting the Syslog Service
After the syslog service is started, the NE can transmit the syslog to syslog servers.
4.10.1 Syslog Service

The syslog service is a part of the NE security management. All types of information is
transmitted to the syslog server. All this information is in the format defined by the syslog
protocol. The network administrator and maintainer can estimate the status of the NEs based on
the severities of these information.
Definition
l Syslog Server is a workstation or a server that stores the syslog of the NEs in the network.
l Syslog GNE is an NE that receives the syslogs of other NEs and transmits all the syslogs
to the Syslog Server.
Networking Solution
For the security reasons, a transmission network must be connected to at least two syslog servers.
The NEs and syslog servers usually communicate by IP protocol. Among the NEs, many
protocols can be applied. For example, the NEs can communicate with each other through the
ECC protocol.
Case 1:
Core NEs communicating with each other using the IP protocol, and Different syslog servers
connected with different NEs. A typical type of network is shown in Figure 4-1.

Figure 4-1 IP and ECC hybrid networking-1

Syslog Server 1 Syslog Server 2
IP IP IP IP
NE1
NE2 NE3
NE4
IP IP
ECC
ECC ECC
NE5
NE6 NE8
NE7
ECC ECC
NE1, NE2, NE3 and NE4 form an IP network. NE5, NE6, NE7 and NE8 form an ECC network.
NE2 and NE3 communicate with Syslog Server 1 and Syslog Server 2 through the IP protocol
separately. NE4 communicates with NE5 through the ECC channel.
In this situation, NE1, NE2, NE3 and NE4 can communicate with two different syslog servers
through the IP protocol directly. So, you only need to set the IP address and port number of the
syslog server for these NEs. The NE transmits the NE syslog to the syslog servers through the
IP protocol. You need not set the syslog GNE.
NE5, NE6, NE7 and NE8 cannot communicate with syslog servers directly. Their syslog is
transmitted to the syslog GNE through the ECC channel. Then, the syslog GNE transmits the
syslog to the syslog servers. So, you only need to set the syslog GNE for these NEs. For example,
NE2 may be the syslog GNE of NE5.
Table 4-1 Configuration List

NE Syslog Server IP Address Syslog GNE
NE1, NE2, NE3, NE4 129.1.0.1 None

129.2.0.1
NE5, NE6, NE7, NE8 None NE2

NE3

Case 2:
Core NEs communicating with each other using the IP protocol, and Different syslog servers
connected with the same NE. This type of network is similar to the one shown in Figure 4-1.
See Figure 4-2.
Figure 4-2 IP and ECC hybrid networking-2

IP IP
IP IP
NE1
NE2 NE3
NE4
IP IP
ECC
ECC ECC
NE5
NE6 NE8
NE7
ECC ECC
In this situation, NE1, NE2, NE3 and NE4 can also communicate with two different syslog
servers through the IP protocol. So, all the NE settings are exactly the same as the settings in
Table 4-1.
Case 3:
Core NEs communicating with each other using the ECC protocol, and Different syslog servers
connected with different NEs. A typical type of network is shown in Figure 4-3.

Figure 4-3 ECC independent networking

IP ECC ECC IP
NE1
NE2 NE3
NE4
ECC ECC
ECC
ECC ECC
NE5
NE6 NE8
NE7
ECC ECC
NE1, NE2, NE3 and NE4 form an ECC network. NE5, NE6, NE7 and NE8 form another ECC
network. NE2 and NE3 communicate with Syslog Server 1 and Syslog Server 2 separately
through the IP protocol. NE4 communicates with NE5 through the ECC channel.
In this situation, NE2 can only communicate with Syslog Server 1 directly. NE2 cannot
communicate with Syslog Server 2 directly. So, you need to set the IP address and port number
of Syslog Server 1 for NE2. Then, you need set the Syslog GNE which can transmit the syslogs
to Syslog Server 2. After that, NE2 can transmit the syslogs to Syslog Server 1 through the IP
protocol and Syslog Server 2 through the Syslog GNE. The setting of NE3 is similar to the setting
of NE2. You need to set the IP address and port number of Syslog Server 2, and then set the
Syslog GNE which can transmit the syslogs to Syslog Server 1.
All other NEs cannot communicate with two syslog servers directly. Their syslog is transmitted
to the syslog GNE through the ECC channel. Then, the syslog GNE transmits the syslog to the
syslog servers. So, you only need to set the syslog GNE for these GNEs. For example, NE2 and
NE3 may be the syslog GNEs of NE5. For details about the configurations, refer to Table 4-2.
Table 4-2 Configuration List
NE1, NE4, NE5, NE6, NE7, None NE2

NE8 NE3

NE2 129.1.0.1 NE3
NE3 129.2.0.1 NE2
4.10.2 Configuring the Syslog Server

In the case of NEs that can communicate with syslog servers directly, you need to configure the
syslog server on the NEs. Then, the NEs can transmit the syslog to the syslog server.
Prerequisite
l The NE must be able to communicate with the syslog server directly.
Procedure
2 In the NE Explorer, select an NE and choose Security > NE Log Forwarding from the Function
Tree.
3 Click the Syslog Server tab. The list of syslog servers is displayed.
4 Click Query to load the configuration data of the syslog server from the NE.
5 Click New and the Add Syslog Server dialog box is displayed.
6 Set the IP Address, Send Mode and Port based on the network settings.
7 Click OK. A prompt appears telling you that the operation was successful.
----End
4.10.3 Configuring the Syslog GNE

In the case of For the NEs that cannot communicate with the syslog server directly, you need to
configure the syslog GNE. The syslog GNE transmits all the syslog that it receives d to the syslog
server.
Prerequisite
Procedure
Tree.

3 Click the Syslog GNE tab. The list of syslog GNEs is displayed.
4 Click Query to load the syslog GNE configuration from the NE.
5 Click New and the Object Select dialog box is displayed.
6 Choose proper NEs as the syslog GNEs.
7 Click OK. A prompt appears indicating the operation was successful.
----End
4.10.4 Configuring the Syslog Type and Severity

Different types of syslog have different severities. The NE report the relevant information based
on the severity of the syslog.
Prerequisite
Procedure
2 In the NE Explorer, select an NE and choose Security > NE Log Forwarding.
3 On the Basic Info tab, click Query to load the configuration data from the NE.
4 Click New. The Add Basic Info dialog box is displayed.
5 Choose proper Log Type and Log Severity based on the network requirements.
6 Click OK. A prompt appears indicating the operation was successful.
----End
4.10.5 Starting the Syslog Service

After the syslog service is started, the NE can transmit the syslog to syslog servers.
Prerequisite
Procedure
Tree.
3 On the Basic Info tab, click Query to load the configuration data from the NE.
4 Check the Start the log forwarding service check box.

5 Click Apply to deploy the latest configuration data. A prompt appears indicating the operation
was successful.
----End

Operation Guide for Common Features 5 Topology Management
5 Topology Management
About This Chapter
Topology management is basic network O&M functions that the U2000 provides. By using the
topology management functions, network maintenance personnel can construct and manage the
topology structure of a network and monitor the status of the entire network in real time.
Specifically, after associating NEs in a real network with visualized operation objects in the
topology, maintenance personnel can learn networking of the NEs and NE statuses based on
colors of NE icons, alarm statuses of NEs, connection statuses between NEs in the topology
view. By using the topology management functions, maintenance personnel can manage NEs
conveniently.
5.1 Flow of Constructing the Network Topology

The flow of constructing the network topology describes the flows of constructing the subnet,
NE, board, and connection, and the relations of the operation tasks.
5.2 Basic Concepts
Topology structure helps you to learn the layout of the entire network, and the networking and
running information of the NE. An understanding of basic topology concepts facilitates the
topology management.
5.3 Designing a Topology
Before deploying NEs in a physical view, you need to design the physical topology view. The
physical topology view should clearly reflect the actual communication network structure to
facilitate routine maintenance and operations.
5.4 Creating a Topology Subnet
The subnet created here is based on a topological concept to facilitate management. In the case
of topology objects in the same network area or with similar attributes, you can allocate them
in one topology subnet.
5.5 Creating NEs
Each equipment is represented as an NE on the U2000. Before the U2000 manages the actual
equipment, you need to create the corresponding NEs on the U2000. There are two ways of
creating NEs: creating a single NE and creating NEs in batches. When you need to create a large
number of NEs, for example, during deployment, it is recommended that you create NEs in
batches. When you need to create just a few NEs, it is recommended that you create the NEs
one by one.

5 Topology Management Operation Guide for Common Features
5.6 Configuring the NE Data

Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the U2000 can manage and operate the NE.
5.7 Adding Boards
In the NE Panel, you can add a board.
5.8 Creating Connections
You can create link and fiber/cable by using the U2000.
5.9 Browsing Fibers/Cables
Fibers/Cables are at the physical layer of a transmission network. This section describes how to
query the physical and engineering information of fibers/cables, and detailed information of
trails that the fibers/cables carry.
5.10 Adjusting Topology Objects
You can modify the settings when creating the network topology by using the U2000. For
example, modify the NE name, adjust the optical NE source, and modify the status of the
preconfigured NE and so on.
5.11 Setting the NE Maintenance Information
NE maintenance information includes the NE location information and maintenance personnel
information. If a fault occurs on an NE, you can refer to the NE maintenance information to
contact the maintenance personnel in time for handling the fault.
5.12 Setting the Maintenance Personnel Information
You can manage the maintenance personnel information in a centralized manner, including
adding, modifying, and deleting the maintenance personnel information.
5.13 Deleting Topology Objects
When adjusting the network topology, generally, you need to delete some objects of the topology.

5.1 Flow of Constructing the Network Topology

The flow of constructing the network topology describes the flows of constructing the subnet,
NE, board, and connection, and the relations of the operation tasks.
It is recommended to construct the network topology, with reference to the flow that is shown
in Figure 5-1.
Figure 5-1 Flow of constructing the network topology
The landscape orientation of the configuration flow chart shows the four main phases of
constructing the network topology. They are managing subnets, managing NEs, managing
boards, and managing connections.
The portrait orientation of the configuration flow chart shows the operation tasks and the
relations between the operation tasks in each phase.
Flow Description
For details of the flow of constructing the network topology shown in Figure 5-1, refer to Table
5-1.

Table 5-1 Description of the flow of constructing the network topology

Pha Operation Description
se
5.3 Designing a Topology Design the way in which subnets are divided before
deploying NEs in the topology view. The physical
topology should reflect the topology structure of the
actual communication network, and should also
Man facilitate the routine maintenance operations.
age
5.4 Creating a Topology To facilitate management, you can put topological
subn
Subnet objects that are in the same area of a network or with
ets
similar attributes to the same topology subnet.
5.13.1 Deleting a When adjusting the topological structure of the network,

Topology Subnet you can delete a subnet from the Main Topology if it is
not needed any more.
5.5 Creating NEs Every actual equipment is displayed as an NE on the

U2000. When you use the U2000 to manage the actual
equipment, you must create the corresponding NE on the
U2000. There are two ways of creating NEs: creating
NEs individually and in batches. When you need to
create a large number of NEs, for example, during
deployment, it is recommended to create NEs in batches.
When you need to create just a few NEs, it is
recommended to create the NEs individually.
5.5.9 Creating Virtual To display the topology relation between the

NEs manageable equipment and unmanageable equipment
on the U2000 in , you need to create virtual NEs so that
you can manage the virtual NEs and actual NEs in a
centralized manner.
Man 5.6 Configuring the NE After an NE is successfully created, it is not configured.

age Data You need to configure the NE first and then the U2000
NEs can manage and operate the NE.
5.10.2 Modifying the NE The ECC protocol uses the NE ID to identify an NE

ID and the Extended ID uniquely. Hence, when planning a network, you must
assign a unique ID to each NE. If an NE ID conflicts with
an existing one, ECC routing collision is caused. In this
case, certain NEs cannot be managed. In the
commissioning or expansion process, if you need to
change the NE ID because of planning adjustment, you
can change the NE ID on the U2000.
5.10.3 Modifying the NE You can change the NE name at any time as required,
Name which does not affect the NE running.
5.13.5 Deleting NEs If you create an incorrect NE, you can delete it from the
U2000. If you delete an NE, all information about the
NE on the U2000 is lost, but this does not affect the
equipment running.

Pha Operation Description

se
5.7.1 Adding Boards After you configure the NE data manually, if you add a
physical board, you need to add the board on the NE
Man Panel. You can either add the physical boards that
age actually operate on the NE or the logical boards that do
boar not exist on the actual equipment.
ds 5.13.2 Deleting Boards If the network configuration changes or you need to
change the board configuration of an NE, you can delete
the board from the NE Panel.
5.8 Creating You can create links, fibers/cables, Ethernet cables,

Connections serial cables, extended ECCs, microwave links, and
virtual fibers on the U2000.
5.10.9 Modifying Fiber/ You can modify the name, attenuation, length, and type
Cable Information of a fiber/cable according to its connection status and
Man physical features.
age
conn 5.10.10 Naming a Fiber/ In the network management, you need to strictly plan the
ectio Cable fiber/cable names, to ensure that faults can be located
ns quickly during maintenance and troubleshooting. On the
U2000, you can use the pre-defined naming rules to
name the fibers/cables.
5.13.4 Deleting During network adjustment, you must delete the fiber/
Connections cable connection between NEs if you need to delete an
NE or modify the link between NEs.
5.2 Basic Concepts

Topology structure helps you to learn the layout of the entire network, and the networking and
running information of the NE. An understanding of basic topology concepts facilitates the
topology management.
5.2.1 Main Topology

5.2.2 Optical NE
An optical NE represents a type of WDM equipment, for example, OTM. The WDM equipment
belongs to an optical NE and each optical NE can contain multiple WDM equipment. The optical
NE concept is applicable to the WDM equipment only.
5.2.3 GNE and Non-Gateway NE
The U2000 communicates with the NEs through the network to manage the network NE. This
type of NE that communicates directly with the U2000 through the network is called gateway

NE (GNE). The other NEs that communicate with the U2000 through the GNE are called non-
gateway NEs.
5.2.4 Virtual NE
An virtual NE is an abstraction of an NE or a network that cannot be directly managed by the
U2000. Virtual NEs represent the topological relations between the equipment that the U2000
manages directly and the equipment the U2000 manages indirectly on the topology. If the
equipment that is not managed by the U2000 exists in the network and there are trails created
on the equipment, you can create a virtual NE on the U2000 to represent the equipment.
5.2.5 Connection Types
U2000 can manage connections, include links and fiber/cables in a centralized manner.
5.2.1 Main Topology

Navigation Path
l In the Workbench Window, double-click the shortcut icon of Main Topology.
l Choose View > Main Topology from the main menu.
l If the preceding operation closes the Main Topology, you can click the shortcut button
to open the Main Topology.

NOTE
l The U2000 provides multiple display modes of the client. For example, you can set a particular mode
of displaying alarms of a particular object. For information about the meanings and setting methods of
display modes, see 1.10 Customizing the Client GUI Effect.
l The U2000 provides the focus display function. When the mouse cursor stays on a shortcut button for
about 2 seconds, the U2000 will provide a focus display, presenting its meaning.
l The U2000 provides a variety of view windows according to different functions, and the views can be
switched at will.
l In the Current View drop-down list, select Physical Root to display the Physical Root view.
l In the Current View drop-down list, select Clock View to display the Clock View.
l In the Current View drop-down list, select Tunnel View to display the Tunnel View.
l In the Current View drop-down list, select Custom View to display the custom view.
Figure 5-2 shows the Main Topology of the U2000.

Figure 5-2 Main Topology
1 2 3 4 5
12 11 10 9 8 7 6
1: Network management 2: Menu bar 3: Shortcut icon

system name You can operate the NM and Click the icon, you can
the NE with submenu bar, perform a simple task
include configure tasks, quickly. For example: exit
manage tasks and so on. NM, lock terminal, log out,
NMS user management, stop
the current alarm sound,
1.8.6.3 NE Explorer, 1.8.6.7
Browse Alarm, 1.8.6.9
Browse Performance
Window, 5.8 Creating
Connections.

4: Shortcut icon 5: Alarm button bar 6: Filter Tree and Legend

Click the icon, you can The Alarm buttons for In this area, you can set the
perform a simple task quickly alarms at different severity display types of the objects in
on the Main Topology. For levels are in different colors. a view, and view the
example: zoom in or zoom You can click the button to descriptions of legends in the
out or refresh or save the view the number of the view. To locate an operation
view, show or hide the uncleared alarms generated object quickly, refer to
navigators, search objects, on the current U2000. You 1.8.8.1 Filtering Operation
see object attributes, lock or can click the button to view Objects in a View.
unlock the view. current alarms. For example:
Alarm, show alarm panel.
When the U2000 has
abnormal events, the
Abnormal event indicator
turn to red from green. You
can click the indicator to
view current abnormal
events.
7: Displays the client time in 8: Views user name of the 9: Views the name which is
real time. logged-in U2000 user set by the current U2000
currently. client, and views the IP
address of the current
U2000 server.
10: Physical Map 11: Display the mouse 12: Views the current
Views the managed coordinate on the Main location of the cursor in the
equipment. Topology currently. Main Topology.
On the Physics Map, you can
perform operations, such as
5.5 Creating NEs, 5.13
Deleting Topology Objects,
1.8.6.3 NE Explorer, 5.8
Creating Connections, 5.9
Browsing Fibers/Cables,
5.6 Configuring the NE
Data, 1.8.6.9 Browse
Performance Window,
Alarm, 1.20 Collecting NE
Data and so on.
5.2.2 Optical NE
An optical NE represents a type of WDM equipment, for example, OTM. The WDM equipment
belongs to an optical NE and each optical NE can contain multiple WDM equipment. The optical
NE concept is applicable to the WDM equipment only.

l Optical Network Element (ONE) is the transport entity that implements the NE functions
(terminal multiplexing, add/drop multiplexing, cross-connection and regeneration) in a
DWDM layer network.
l The locating of an ONE is equivalent to that of a common NE. In a view, an ONE is
displayed with an icon, like a common NE and its alarm status can be displayed with colors.
Logically, an ONE consists of different subracks.
l Like a common NE, an ONE cannot be expanded or entered like a sub-network. Similar to
a common NE, an ONE provides a list of the subracks that form the NE to display the board
layout.
l The U2000 manages the WDM equipment by means of optical NEs. The WDM equipment
is no longer referred to as NE, but as a subrack. The SDH equipment has only one subrack.
Hence, the NE layer need not be distinguished from the subrack layer.
l There are four types of optical NEs, which are WDM_OTM, WDM_OLA, WDM_OADM
and WDM_OEQ.
NOTE
Currently, the OptiX OSN 6800, OptiX OSN 8800 T32, OptiX OSN 8800 T64, OptiX OSN 8800 T32(NA)
and OptiX OSN 8800 T64(NA) NE can be managed individually as an NE, and can also be managed in an
optical NE.
5.2.3 GNE and Non-Gateway NE

The U2000 communicates with the NEs through the network to manage the network NE. This
type of NE that communicates directly with the U2000 through the network is called gateway
NE (GNE). The other NEs that communicate with the U2000 through the GNE are called non-
gateway NEs.
GNE
The U2000 manage the network NE through the GNE. The communicate protocol of GNE is IP
or OSI.
Each U2000 must connect to at least one GNE.
NOTE
l The non-gateway NE applies to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
l If the number of non-gateway NEs that connect to a GNE is more than 50, an alarm is reported to the
U2000.
Non-Gateway NE
The non-gateway NE communicates with the GNE by using the ECC or the extended ECC, and
thus the non-gateway NE can communicate with the U2000.
The recommended number of non-gateway NEs (including non-gateway NEs that connects to
the GNE by using the extended ECC) that connect to each GNE is fewer than 50.
5.2.4 Virtual NE
An virtual NE is an abstraction of an NE or a network that cannot be directly managed by the
U2000. Virtual NEs represent the topological relations between the equipment that the U2000
manages directly and the equipment the U2000 manages indirectly on the topology. If the

equipment that is not managed by the U2000 exists in the network and there are trails created
on the equipment, you can create a virtual NE on the U2000 to represent the equipment.
Different from actual NEs, a virtual NE does not need to be hardware-specific. It can be used to
represent any unknown equipment. On the U2000, it is usually used to simulate the equipment
that cannot be directly managed by the U2000, for example, the equipment that is not managed
by the U2000, such as the third-party equipment.
You can customize the boards in a virtual NE on the U2000. The process of creating and deleting
a virtual NE is similar to that of an actual NE.
Virtual NEs are not restricted by the license. The license does not define the maximum number
of virtual NEs on the U2000.
NOTE
l The concept of virtual NE just for the SDH and PTN NE.
l Currently, the virtual NEs support the simulation of the features of only SDH NEs.
5.2.5 Connection Types

U2000 can manage connections, include links and fiber/cables in a centralized manner.
Link
A network communications channel consisting of a circuit or transmission path and all related
equipment between a sender and a receiver. A link is used to connect signaling points (SPs) and
signaling transfer points (STPs) and transmit signaling messages.
Type Description
IP Link An IP link is the Layer 3 link between

equipment. The side-by-side link can be
displayed in the a physical root view.
L2 Link A Layer-2 link is the Layer-2 link between

equipment in a physical root view.
Extended ECC When there is no optical path between two or

more NEs, the Ethernet ports of the NEs can
be used to achieve the extended ECC
communication. By default, the NEs use the
auto-extended ECC communication. If the
number of Huawei equipment that uses the
extended ECC communication exceeds four,
the manually extended ECC communication
must be used instead.
Virtual Link A virtual link is used to identify the logical

connection relation between two managed
objects. Hence, a virtual link is also referred
to as a virtual connection.

Fiber/Cable
Fiber & Cable is the general name of optical fiber and cable. It refers to the physical entities that
connect the transmission equipment, carry transmission objects (user information and network
management information) and perform transmission function in the transmission network. The
optical fiber transmits optical signal, while the cable transmits electrical signal. The fiber/cable
between NEs represents the optical fiber connection or cable connection between NEs.
Type Description
Serial Port Line A serial port line is used to connect the ports
that are used for serial communication. The
ports can transmit and receive the
communication data.
Cable A cable is used to connect communication

interfaces of different equipment and to
provide an extra transmission channel at the
physical layer for the management
information.
Fiber A fiber is used to connect the optical

interfaces between different equipment and to
provide a transmission channel at the physical
layer for service signals. According to the
physical feature of a fiber, the U2000
classifies the fiber as four types, which are G.
652, G.653, G.654, G.655-LEAF, G.655-
TWC, G.655-TWRS, G.655-LS fibers.
Microwave Back To Back When an RTN station needs to converge

services, multiple RTN equipment needs to
be connected through fibers or 2 Mbit/s or 155
Mbit/s cables. In this manner, low-capacity
services are converged to the high-capacity
equipment.
Microwave Link A microwave link uses the microwave to

connect different outdoor units of microwave
equipment.
Virtual Fiber Virtual fiber is a logical concept. It may

contains several physical fibers, radio links,
or even one or more complete networks.
Ethernet Line The Ethernet line that the U2000 can manage
is used to connect the communication
interface of the gateway NE and the U2000
server.

5.3 Designing a Topology

Before deploying NEs in a physical view, you need to design the physical topology view. The
physical topology view should clearly reflect the actual communication network structure to
facilitate routine maintenance and operations.
The topology management window consists of a navigation tree on the left and a topology view
on the right. The navigation tree displays all the topology objects and their hierarchical relations
in a tree, and the topology view displays all the topology objects and their positions on the
physical topology view.
When designing a topology, pay attention to the following points:

l It is recommended that the number of layers in the subnet of the physical topology view
should not exceed five. Too many hierarchies may make the operations inconvenient.
l It is recommended that the number of devices in each subnet should not exceed 300. If
there are too many devices, the devices may be overlapped, and this makes the device query
difficult.
You can divide the physical topology view as follows:

l By region: based on the regions where the NEs are located.
l By NE type: based on the types of the NEs.
l By IP Address: based on the IP addresses of the NEs.
l By responsible person: based on the responsible persons of the NEs.
5.4 Creating a Topology Subnet

The subnet created here is based on a topological concept to facilitate management. In the case
of topology objects in the same network area or with similar attributes, you can allocate them
in one topology subnet.
Prerequisite
A topology subnet is created only to simplify the user interface and has no impact on the NEs.
Procedure
1 Right-click in the blank space of the Main Topology and choose New > Subnet from the shortcut
menu.
2 In the displayed dialog box, click the Property tab. Enter the attributes of the subnet.
3 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane
and click to add the NEs or subnet to the Selected Objects pane.

NOTE
In the case of a similar dialog box for selecting objects,

l indicates that to select the objects to be selected on the left to the selected objects on the right.
l indicates that to select all the objects to be selected on the left to the selected objects on the right.
4 Click OK.
----End
5.5 Creating NEs

Each equipment is represented as an NE on the U2000. Before the U2000 manages the actual
equipment, you need to create the corresponding NEs on the U2000. There are two ways of
creating NEs: creating a single NE and creating NEs in batches. When you need to create a large
number of NEs, for example, during deployment, it is recommended that you create NEs in
batches. When you need to create just a few NEs, it is recommended that you create the NEs
one by one.
Context
NOTE
When you create a transport, router, or switch NE, the name of the new NE cannot be the same as an existing
one. When you create an access NE, however, the name of the new NE can be the same as an existing one.
It is recommended that access NEs use different names.
5.5.1 Setting SNMPv1/v2c Parameters on NEs

This topic describes how to set SNMPv1/v2c parameters on NEs. Before an NE is created on
the U2000, you need to set SNMP parameters on the NE through commands. Generally, the
applied SNMP version is v1 or v2c.
5.5.2 Setting SNMPv3 Parameters on NEs
This topic describes how to set SNMPv3 parameters on NEs. Before an NE is created on the
U2000, you need to set SNMP parameters on the NE through commands. In comparison,
SNMPv3 features higher security than SNMPv1 or SNMPv2c. You can use SNMPv3 to ensure
the communications between the U2000 and NEs.
5.5.4 Creating NEs In Batches
The U2000 supports the ability to search out all NEs according to the IP addresses of NEs, IP
address or IP network segment of the GNE, or NSAP addresses of the NEs, and create the NEs
in batches. The U2000 also can import and create in batches the NEs that register with the
U2000 according to the active registration information of the NEs. Creating NEs by using this
method is faster and more reliable than creating the NEs manually.
5.5.5 Creating a Single NE
You need to create an NE before you can manage it by using the U2000. Although creating a
single NE is not as fast and accurately as creating NEs in batches. The method of creating the
NE of different types cannot be the same.
5.5.6 Configuring NEs Automatically
The U2000 can automatically create and configure auto-discovered NEs in the topology view.

5.5.7 Adding NEs Periodically

When you set the time discovery policy, the U2000 searches the specific IP network segment
and NE type at the specific intervals based on the settings and adds the found NEs to the topology
view.
5.5.8 Creating Optical NEs
The U2000 manages the WDM equipment and OptiX BWS 1600S by using optical NEs. There
are four types of optical NEs. They are WDM_OADM, WDM_OEQ, WDM_OLA and
WDM_OTM. OptiX OSN 1800 only supports WDM_OTM and WDM_OADM. OptiX BWS
1600S only supports WDM_OTM.
5.5.9 Creating Virtual NEs
To display the topological relations between the equipment that is directly managed by the
U2000 and the equipment that is indirectly managed by the U2000 on the topology, you must
create virtual NEs so that the U2000 manages them together with the regular NEs in a uniform
manner.
5.5.1 Setting SNMPv1/v2c Parameters on NEs

This topic describes how to set SNMPv1/v2c parameters on NEs. Before an NE is created on
the U2000, you need to set SNMP parameters on the NE through commands. Generally, the
applied SNMP version is v1 or v2c.
Context
It is applicable to the Router series, Switch series, Security series NEs.
The prerequisites for the U2000 to discover and manage NEs through SNMP are as follows:
l SNMP parameters must be set correctly on NEs.
l The default SNMP parameters on the U2000 must be consistent with the SNMP parameters
set on NEs.
Procedure
1 To enter the system view, run the following command:
system-view
2 To start the SNMP Agent service, run the following command:
snmp-agent
3 To set the SNMP protocol version, run the following command:
snmp-agent sys-info version { { v1 | v2c }* }
NOTE
For the meaning of every field in the command, see the command reference of the associated NE.
4 To set the read community name, run the following command:

snmp-agent community read community-name [ [ mib-view view-name ] | [ acl acl-

number ] ]*
5 To set the write community name, run the following command:
snmp-agent community write community-name [ [ mib-view view-name ] | [ acl acl-
number ] ]*
----End
Example
The following takes the setting of basic SNMPv1 parameters on a router as an example.
l Set SNMP version to v1.
l Set Read community name to public.
l Set Write community name to private.
After the CLI of the router is displayed, do as follows:
1. Enter the system-view command, and then press Enter.
2. Enter the snmp-agent command, and then press Enter.
3. Enter the snmp-agent sys-infoversion v1 command, and then press Enter.
4. Enter the snmp-agent communityread public command, and then press Enter.
5. Enter the snmp-agent communitywrite private command, and then press Enter.
The setting of basic SNMPv1 parameters is complete.
5.5.2 Setting SNMPv3 Parameters on NEs

This topic describes how to set SNMPv3 parameters on NEs. Before an NE is created on the
U2000, you need to set SNMP parameters on the NE through commands. In comparison,
SNMPv3 features higher security than SNMPv1 or SNMPv2c. You can use SNMPv3 to ensure
the communications between the U2000 and NEs.
Context
It is applicable to the Router series, Switch series, Security series NEs.
The prerequisites for the U2000 to discover and manage NEs through SNMP are as follows:
l SNMP parameters must be set correctly on NEs.
l The default SNMP parameters on the U2000 must be consistent with the SNMP parameters
set on NEs.
Procedure
1 To enter the system view, run the following command:
system-view
2 To start the SNMP Agent service, run the following command:

snmp-agent
3 To set the SNMP protocol version, run the following command:
snmp-agent sys-info version v3
4 To set the SNMP user group, run the following command:
snmp-agent group v3 group-name [ authentication | privacy] [ read-view read-view ] [ write-

view write-view ] [ notify-view notify-view ] [ acl acl-number ]
NOTE
For the meaning of every field, see the command reference of the corresponding NE.
5 To add a new user to the SNMPv3 group, run the following command:
snmp-agent usm-user v3 user-name group-name [ [ authentication-mode { md5 | sha }

password ] [ privacy-mode des56 password ] ] [ acl acl-number ]
----End
Example
The following takes the setting of basic SNMPv3 parameters on a router as an example.
l Set SNMP version to v3.
l Set SNMP user group to routergroup.
l Set new SNMPv3 group user to routeruser1.
After the CLI of the router is displayed, do as follows:
1. Enter the system-view command, and then press Enter.
2. Enter the snmp-agent command, and then press Enter.
3. Enter the snmp-agent sys-infoversion v3 command, and then press Enter.
4. Enter the snmp-agent group v3 routergroup command, and then press Enter.
5. Enter the snmp-agent usm-user v3 routeruser1 routergroup command, and then press
Enter. The setting of basic SNMPv3 parameters is complete.

Prerequisite
l This operation is applicable to the Router series, Switch series, Security series, Access
series NEs.

Context
It is forbidden to delete the default access protocol parameter template.
Procedure
1 Choose Administration > NE Communicate Parameter > Default Access Protocol
Parameters from the main menu. Click Display.
2 In the Default Access Protocol Parameters dialog box, click the related tab to switch to the
page for configuring protocol parameters. The following figure shows how to set SNMPv3
parameters.
3 Configure the NE SNMP parameter template as follows:

l Add a parameter template.
Click Add. After setting all the parameters in the parameter setting area at the bottom of
the window, click OK.
l Modify a parameter template.
Double-click the template to be modified in the parameter template list. Modify the related
parameters in the Common parameters and SNMP v3 Security Parameters areas. Then,
click Apply.
NOTE
l Associated parameters in only the Common parameters area need to be modified for SNMPv1
and SNMPv2.
l The Template Name parameter cannot be modified.
l Delete a parameter template.
Select the template to be deleted in the parameter template list and then click Delete. In the
----End

5.5.4 Creating NEs In Batches

The U2000 supports the ability to search out all NEs according to the IP addresses of NEs, IP
address or IP network segment of the GNE, or NSAP addresses of the NEs, and create the NEs
in batches. The U2000 also can import and create in batches the NEs that register with the
U2000 according to the active registration information of the NEs. Creating NEs by using this
method is faster and more reliable than creating the NEs manually.
5.5.4.1 Creating Transport/PTN NEs in Batches
When the U2000 communicates with a GNE normally, the U2000 supports the ability to search
out all NEs that communicate with the GNE according to the IP address or IP network segment
of the GNE, or NSAP addresses of the NEs, and create the NEs in batches.
5.5.4.2 Creating SNMP/ICMP NEs in Batches
SNMP/ICMP NEs include Router series, Switch series, Security series, Access series NEs. When
the U2000 communicates with SNMP/ICMP NEs normally, the U2000 supports the ability to
search out all SNMP/ICMP NEs according to the IP addresses or IP network segments of the
NEs, and create them in batches.
5.5.4.3 Importing NEs in Batches
This topic describes how to import NEs in batches. When the U2000 communicates with NEs
normally, the U2000 can import and create the security NEs in batches.
5.5.4.1 Creating Transport/PTN NEs in Batches

When the U2000 communicates with a GNE normally, the U2000 supports the ability to search
out all NEs that communicate with the GNE according to the IP address or IP network segment
of the GNE, or NSAP addresses of the NEs, and create the NEs in batches.
Prerequisite
l U2000 communicates with the GNE normally.
Context
Except the OptiX OSN 6800, OptiX OSN 8800 T32, OptiX OSN 8800 T64 equipment, to
facilitate management, create optical NEs before creating NEs in batches. Otherwise, the new
NEs are allocated to idle optical NEs automatically.
Procedure
1 Choose File > Discovery > NE from the main menu.
2 Click the Transport NE Search tab.
3 Select the search mode from the drop-down list of Search Mode.
l Sets the Search Mode is Search for NE:
1. Enter the network segment or IP addresses NEs to search for the NEs.
a. Click Add and the Input Search Domain dialog box is displayed.
b. Set the address type to IP Address Range of GNE, IP Address of GNE, or
NSAP Address. Enter the Search Address, User Name, and Password. Click
OK.

NOTE
Repeat the above steps to add more search domains. You can also delete the system-
default search domain.
l If you search by IP address,
l only the NEs (not across routers) in the same network segment can be searched
out in normal conditions if you select the IP Address Range of GNE because
broadcasting is usually disabled for the routers in the network (to prevent network
storm).
l search out the NEs in the network segment by using the IP Address of GNE if
you need to search for the NEs across routers.
l If you search for NEs by using the NSAP address, you can only select NSAP
Address.
2. In the Search for NE area, perform the following operations:
– Select Create device after search, enter the NE User and Password.
NOTE
l The default NE user is root.

l The default password is password.
– Select Upload after create. The data related to the NEs are uploaded to the
U2000 after the NEs are created.
NOTE
You can select all options in the Search for NE area to search for NEs, create NEs, and upload
the NE data at a time.
l Sets the Search Mode is IP auto discovery:
NOTE
If you fail to enter a network segment correctly, enable IP auto discovery. After enabling IP auto
discovery, you can obtain the IP address of the GNE and search out all the NEs related to the GNE.

CAUTION
In the case of NEs that are connected to the NMS through the router, these NEs cannot be
searched out by IP auto discovery. They can be searched out only by network segment.
4 Click Next and the Result area is displayed.
5 Optional: Click Change NE ID. Then, the Change NE ID dialog box is displayed. Users can
check against the Bar Code List by the value of Bar Code, and then modify the NE Name,
Extend NE ID, Base NE ID, and IP Address fields accordingly.
NOTE
The Bar Code List is provided by the hardware installation personnel to the software commissioning
personnel. The list contains the bar codes of stations.
6 Optional: If you select only Search for NE, after the U2000 completes the search, you can
select the uncreated NEs from the Relust list and click Create. The Create dialog box is
displayed. Enter the NE User and Password. Click OK.
----End
Follow-up Procedure
If you fail to log in to an NE after you create it, the probable causes are as follows:
l The password of the NE user is incorrect. Enter the correct password.

l The NE user is invalid or is already logged in. Specify a valid NE user.
5.5.4.2 Creating SNMP/ICMP NEs in Batches

SNMP/ICMP NEs include Router series, Switch series, Security series, Access series NEs. When
the U2000 communicates with SNMP/ICMP NEs normally, the U2000 supports the ability to
search out all SNMP/ICMP NEs according to the IP addresses or IP network segments of the
NEs, and create them in batches.
Prerequisite
l U2000 communicates with the router NEs normally.
l Only one client can use the automatic discovery function at a time.
l The existing NEs are excluded for the automatic discovery. In the More Information
dialog box, those NEs are displayed as the existing NEs.

l If you clear the selection of Automatically Create NEs, the NEs that are searched out are
not automatically created. You need to manually create the NEs as required.
Context
In the case of switch and router NEs, the function of creating an NE uses the license for dedicated
upgrade items or the license for NE resources. If there is no remaining license for dedicated
upgrade items or license for NE resources, a message is displayed indicating that NE creation
fails. It is recommended that you apply for a new license for NE resources.
Procedure
1 Choose File > Discovery > NE from the main menu.
2 Click the SNMP/ICMP NE Search tab.
3 Set the search parameters, such as NE Type and Ping Times. If you select the Automatically
Create NEs check box, the equipment that is searched out is created automatically. Otherwise,
you need to create the equipment manually.
4 Click Default SNMP Parameter to set the SNMP parameters to values that are consistent with
the parameter values on the equipment side.
CAUTION
If the settings of the SNMP parameters are inconsistent with the parameter settings on the
equipment side, the equipment cannot be searched out.
5 In the IP Address Range (History Records are already loaded) area, click Add and the IP
Address Range dialog box is displayed. Enter the Start IP Address, End IP Address, and
Subnet Mask. Click OK.
6 Click Next. The SNMP/ICMP NE Search tab page of the Auto Discovery dialog box displays
the equipment data that is searched out and the operation records.

NOTE
l When setting the parameters for NE search, if you select Automatically Create NEs, NEs are
automatically created and added to the physical topology tree of the U2000.
l When setting the parameters for NE search, if you deselect Automatically Create NEs, you need to
manually create NEs. In the NE Data, select a NE that to create, click Create.
7 Optional: Click More and the More Information dialog box is displayed. View the details of
Undiscovered Equipment in the operation records.
----End
5.5.4.3 Importing NEs in Batches

This topic describes how to import NEs in batches. When the U2000 communicates with NEs
normally, the U2000 can import and create the security NEs in batches.
Prerequisite
l The U2000 can communicate with the NEs that register with the U2000.
l The function applies to only the security gateway, service monitoring gateway, and SVN
series security NEs.
Context
With active registration management, the U2000 receives the active registration information
regularly transmitted from NEs to the U2000 server, including the IP address of the NEs. When
the IP address of an NE changes, active registration management of the U2000 can synchronize
the IP address of the NE in time.

Procedure
1 Choose File > Batch Import NE from the main menu.
2 In the Import NE in Batches dialog box, set Physical Path, SNMP Parameter, and IP Address
List.
l Set Physical Path.
Click . In the Select a Path of Parent Subnet dialog box, select the location where the
imported NEs are stored. Then, click OK.
l Set SNMP Parameter.
Click . In the Set default SNMP Parameters dialog box, set the SNMP parameter to
the value that is consistent with the setting on the NE side.
NOTE
To make sure that the NEs are created successfully, the SNMP parameter setting needs to be consistent
with that on the NEs side.
l Obtain the NE IP to be imported
– Get Registered IP: Click Get Registered IP to send a message to the server and obtain
the NE IPs that register with the U2000 through the active registration function. Then
select the security NEs (to be imported) in the IP Address List group box.
NOTE
Make sure port 4999 on the U2000 server is available and the U2000 can obtain the active
registration information of NEs only after the following operations are performed on the NEs:
1. Run system-view to access the system view.
2. Run secoway-server ip-address ip-address to enable the active registration function. ip-
address is the IP address of the U2000 server for the intended NE.

– Import IP From File: Click Import IP From File to obtain the IP list from an Excel file.
Then select the security NEs (to be imported) in the IP Address List group box. By
default, U2000 imports data since the second row. The imported excel is shown as Figure
5-3.The description of the imported excel is shown as Table 5-2.
Figure 5-3 Imported Excel
Table 5-2 Imported Excel Description
Column Name Mandatory Remarks
NE Name Optional A maximum of 64

If an NE is imported for the characters are valid and the
first time, the NE name NE names can be the same.
specified in the excel
document is displayed in IP
Address List; If the NE is
already imported, the
original NE name is not
replaced by the new one.
IP Address Mandatory -
If the IP address is not
specified, the establishment
of an NE fails.
MAC Address Optional -

Whether the MAC address
is correctly specified does
not affect the establishment
of an NE.
NOTE
l If both Get Registered IP and Import IP From File are selected, the data imported through the
two methods is displayed in the IP Address List group box.
l Double-click NE Name group box or right-click Modify Name in the IP Address List to modify
the name of an NE.
l Right-click on Selection in the displayed IP address list. Then, click Select All or Unselect All to
select or clear the NEs to be imported.
3 Click Create.
In the Import NE dialog box, the progress bar displays the progress of importing selected NEs.

Click Details. The details about the import operation are displayed in the information area under
the progress bar, as shown in the following.
Click Export Result To File to export the result to an Excel file. The description of the imported
excel is shown asTable 5-3.
Table 5-3 Exported Excel Description
Column Name Description
NE Name The name of the NE
IP Address The IP address of the NE
MAC Address The MAC address of the NE
Result The result details of creating NE.
Success Flag Prompts whether the import operation

succeeds
4 Click Close to close the Import NE in Batches window.
----End
Result
The NEs imported in batches are displayed in the main topology.
5.5.5 Creating a Single NE

You need to create an NE before you can manage it by using the U2000. Although creating a
single NE is not as fast and accurately as creating NEs in batches. The method of creating the
NE of different types cannot be the same.

Prerequisite
When creating an NE on the U2000, ensure that the IP address of the NE does not conflict with
the IP address of any existed NE. If the IP addresses conflict with each other, the NE will fail
to be created.
5.5.5.1 Creating a Single Transport NE
This topic describes how to create a single transport NE.
5.5.5.2 Creating a Single PTN NE
After the NE is created, you can use the U2000 to manage the NE. Although creating a single
NE is not as fast and exact as creating NEs in batches, you can use this method regardless of
whether the data is configured on the NE or not.
5.5.5.3 Creating a Single Router NE
This topic describes how to create a single router NE.
5.5.5.4 Creating a Single Switch NE
This topic describes how to create a single switch NE.
5.5.5.5 Creating a Single Security Gateway NE
This topic describes how to create a single security gateway NE.
5.5.5.6 Creating a Single Access NE
This topic describes how to create a single access NE.
5.5.5.1 Creating a Single Transport NE

This topic describes how to create a single transport NE.
Prerequisite
l It is applicable to MSTP, WDM, NA WDM, RTN, Marine series NEs.
l The license file that supports the NE type must be installed.
l The NE Explorer instance of the NE must be created.
Context
l Before creating a non-gateway NE, you need to create a GNE first.
l For the WDM equipment except for the OptiX OSN 6800, OptiX OSN 8800 T32, OptiX
OSN 8800 T64, to facilitate management, create an optical NE before creating an NE.
Otherwise, the new NE is allocated to an idle optical NE automatically.
l If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray.
l If you do not know the IP address of the NE which you want to create, you can use the IP
auto discovery. You can view 5.5.4.1 Creating Transport/PTN NEs in Batches
Procedure
1 Right-click in the Main Topology and choose New > NE from the shortcut menu.
2 On the Object Type tree of the displayed dialog box, select the equipment type of the NE to be
created.

3 Set the attributes of the NE.

For example, add the OptiX 2500 in the product family of SDH series equipment. The NE
attributes are shown in the following figure:
NOTE
When you create an NE, its default name is expressed in the NE(extended ID-NE ID) format, such as NE
(9-81).
4 To create a GNE or non-gateway NE, do as follows:

l Select the gateway type and protocol, and set the IP or NSAP address.
NOTE
If the NE of the version does not support the OSI protocol, you cannot create a communication
connection between the U2000 and the NE even if you select the OSI protocol when you create the
NE.
1. Select Gateway from the Gateway Type drop-down list.

2. Select the protocol type of the gateway.
If the U2000 Do...
communicates with
NEs through
IP protocol Select IP from the Protocol drop-down list. Enter the

IP Address and use the default value for the Port
number of the GNE.
OSI protocol Select OSI from the Protocol drop-down list. Enter the
NSAP Address of the GNE.
NOTE
The NSAP address consists of hexadecimal digits of a maximum of 20 bytes, and is of the
following format: domain address+08003e+NE ID+NSEL. The Domain Address comprises
of 13 bytes and is entered by the user. NSEL is the port number of the network-layer protocol,
with a fixed value of 1d (one byte).
l Select Non-Gateway from the Gateway Type drop-down list, and select the GNE for the
NE.

5 Optional: In the case of a WDM NE, select an optical NE for the WDM NE.
6 Specify NE User and Password.

NOTE
The default NE user is root and the default password is password.
7 Optional: If the NE data on the U2000 is not delivered to the NE, select the NE
Preconfiguration check box, and set NE Software Version.
NOTE
l If the configuration data of a preconfigured NE is inconsistent with the configuration data of the actual
NE, delivering the configuration data of the preconfigured NE affects the actual services on the NE.
l The SONET, RTN, NG WDM, NA WDM, and Marine series equipment do not support NE
preconfiguration.
8 Click OK. Then, click in the blank space of the Main Topology and the NE icon appears in the
position where you clicked.
----End
Result
After you create the NE successfully, the system automatically saves the IP address, NSAP
address, subnet mask, and ID of the NE to the U2000 database.
Follow-up Procedure
If you fail to log in to an NE after you create it, the probable causes are as follows:
l The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as IP address and ID of the NE.
l The password of the NE user is incorrect. Enter the correct password.
l The NE user is invalid or is already logged in. Specify a valid NE user.
5.5.5.2 Creating a Single PTN NE

After the NE is created, you can use the U2000 to manage the NE. Although creating a single
NE is not as fast and exact as creating NEs in batches, you can use this method regardless of
whether the data is configured on the NE or not.
Prerequisite
l You must be an NM user with "NM operator" authority or higher.
l The license file that supports the NE type must be installed.
l The NE Explorer instance of the NEs must be created.
Context
First create a GNE, and then create a non-gateway NE.
If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray color.

Procedure
1 Right-click in the blank space of the Main Topology and choose New > NE from the shortcut
menu.
2 On the Object Type tree of the displayed dialog box, select the NE type to be created.
3 Complete the following information: ID, Extended ID, Name and Remarks.
For example, add the OptiX PTN 3900 in the product family of PTN series equipment. The NE
attributes are shown in the following figure:
NOTE
When you create an NE, its default name is expressed in the NE(extended ID-NE ID) format, such as NE
(9-81).
4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.
5 Choose Gateway Type, Protocol and set the IP address and NSAP address.
NOTE
If the NE of the version does not support the OSI protocol, you cannot create a communication connection
between the U2000 and the NE even if you select the OSI protocol when you create the NE.
1. Select Gateway from the Gateway Type drop-down list.
2. Select the Protocol type.
If the U2000 Do...

communicates with
NEs through
IP protocol Select IP from the Protocol drop-down list. Enter the IP

Address and use the default value for the Port number of
the GNE.
OSI protocol Select OSI from the Protocol drop-down list. Enter the
NSAP Address of the GNE.

NOTE
The NSAP address is a hexadecimal number that contains a maximum of 20 bytes. Its format is:
domain address+08003e+NE ID+NSEL. The domain address that contains a maximum of 13 bytes
is entered by the user. NSEL is the port number of the network-level protocol, with a fixed value of
1d (one byte).
6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NE
is associated to from the Affiliated Gateway drop-down list.
7 Enter the NE User and Password.

NOTE
The default NE user is root, and the default password is password.
8 Click OK. Then, click in the blank space of the Main Topology and the NE icon appears in the
position where you clicked.
----End
Result
After an NE is successfully created, the system automatically saves the information, such as the
IP address, NSAP address, subnet mask, and NE ID to the U2000 database.
Follow-up Procedure
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as the IP address of the NE and NE ID.
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
5.5.5.3 Creating a Single Router NE

This topic describes how to create a single router NE.
Prerequisite
It is applicable to router NEs, such as NE series routers and CX series routers.
Procedure
created.

For example, add the NE40E in the product family of NE series routers. The NE attributes are
shown in the following figure:
4 Click OK.
----End
Result
After you create the NE successfully, the system saves the NE information to the U2000 database
automatically.
5.5.5.4 Creating a Single Switch NE

This topic describes how to create a single switch NE.
Prerequisite
It is applicable to switch NEs, such as CX200D and S series NEs.
Procedure
2 On the Object Type tree of the displayed dialog box, select the NE type of the NE to be created.
For example, add the S8016 in the product family of S series NE. The NE attributes are shown
in the following figure:

4 Click OK.
----End
Result
automatically.
5.5.5.5 Creating a Single Security Gateway NE

This topic describes how to create a single security gateway NE.
Prerequisite
It is applicable to security gateway NEs, such as USG series equipment.
Procedure
created.
For example, add the USG50 in the product family of USG series gateways. The NE attributes
are shown in the following figure:

4 Click OK.
----End
Result
automatically.
5.5.5.6 Creating a Single Access NE

This topic describes how to create a single access NE.
Prerequisite
It is applicable to access NEs. For example, multi-service access modules.
Procedure
created.
For example, add the Access NE in the product family of Access NE. The NE attributes are
shown in the following figure:

4 Click OK.
----End
Result
automatically.
5.5.6 Configuring NEs Automatically

The U2000 can automatically create and configure auto-discovered NEs in the topology view.
Context
NOTE
The following functions are applicable to PTN series NEs.
5.5.6.1 Auto-Discovering NEs

The U2000 auto-discovers connected NEs and displays information about the NEs so that
engineers handle the NEs according to planning.
5.5.6.2 Creating Discovered NEs Manually
This topic describes how to manually create and configure auto-discovered NEs on the U2000
according to network planning. For NEs that you do not concern, you do not need to create the
NEs on the U2000 to enhance maintainability.
5.5.6.3 Creating NEs Automatically
A large number of NEs need to be created in network construction or expansion. You can start
NEs first and bulk create the NEs on the U2000 by using the automatic NE creation function of
the U2000.

5.5.6.1 Auto-Discovering NEs

The U2000 auto-discovers connected NEs and displays information about the NEs so that
engineers handle the NEs according to planning.
Procedure
1 Choose File > Discovery > NE Auto Discovery from the main menu.
2 In the Auto Discovery Configuration area, select the Discover automatically check box.
3 Optional: Click Filter. In the dialog box that is displayed, specify the filter criteria for NE auto-
discovery.
4 Click Apply.
5 In the NE Found list, the information about the auto-discovered NEs is displayed.
----End
Follow-up Procedure
For NEs that are discovered but are not created on the U2000, create the NEs manually. For
details, see 5.5.6.2 Creating Discovered NEs Manually.
5.5.6.2 Creating Discovered NEs Manually

This topic describes how to manually create and configure auto-discovered NEs on the U2000
according to network planning. For NEs that you do not concern, you do not need to create the
NEs on the U2000 to enhance maintainability.
Prerequisite
NEs must be auto-discovered.
Procedure
discovery.
4 Click Apply.
5 In the NE Found list, the information about the auto-discovered NEs is displayed.
6 In the NE Found list, select an NE to be created and click Create NE.
7 In the dialog box that is displayed, enter the information about the NE and click OK.
8 Optional: If a discovered NE is not required, click Delete Record to delete the NE.
----End

5.5.6.3 Creating NEs Automatically

A large number of NEs need to be created in network construction or expansion. You can start
NEs first and bulk create the NEs on the U2000 by using the automatic NE creation function of
the U2000.
Prerequisite
NEs must be auto-discovered.
Context
When an NE goes online, the U2000 automatically discovers the NE, creates the NE, uploads
configuration data, and adds the NE for management. In the process, NMS operators do not need
to manually confirm the NE that goes online.
Procedure
discovery.
4 In the Auto Discovery Configuration area, select the Create automatically check box. Set
NE User, NE password, and Connection Mode.
5 In the Auto Discovery Configuration area, select the Upload automatically check box.
6 Click Apply.
7 In the NE Found list, the information about the auto-discovered NEs is displayed. In addition,
the U2000 automatically creates NEs that are discovered but are not created and uploads the
data of these NEs in batches.
----End
5.5.7 Adding NEs Periodically

When you set the time discovery policy, the U2000 searches the specific IP network segment
and NE type at the specific intervals based on the settings and adds the found NEs to the topology
view.
Context
l The time discovery supports the SNMP/ICMP NEs.
l SNMP/ICMP NEs include Router series, Switch series, Security series, Access series
NEs.
l If you clear Enable time discovery, click OK, and save only the preset parameters, the
U2000 does not perform the time discovery.
Procedure
1 Choose File > Discovery > Time Discovery from the main menu.

2 Click on the right of NE Type. In the Select NE Types dialog box, select the type of the
NE to be searched for.
3 In Ping Times, select the times to ping the NE.
4 In Timeout(s), select the timeout for the ping operation.
5 In Layers, select the number of layers you want to search.
6 Click Default SNMP Parameters. In the Set Default SNMP Parameters dialog box, select
the SNMP parameters template used for adapting the searched NEs.
NOTE
By default, the default SNMP parameters template is used for adapting the searched NEs.
7 Select Name NE Using IP address. Then the name of the found NE is its IP address.
8 Click next to Physical Path. In the Select a Path of Parent Subnet dialog box, select the
target subnet of the searched NEs. The path of the target subnet is displayed in Path. Click
OK.
9 Click Add. In the IP Address Range dialog box, set the start IP address, end IP address, and
subnet mask of the found NE, and then click OK. A new IP address range is added to the IP
Address Range table.
NOTE
The record lists the start IP addresses, end IP address, and subnet mask of the IP network segment to be
searched. If you want to select the IP address range to search the NEs, select Enable.
10 Click Filter to mask the IP addresses of the NEs that you do not want to search.

11 In the Time Discovery dialog box, select Start Periodical Search. In Start Time, set the start
time for the U2000 Time Discovery.
12 Click OK to save the settings. The U2000 searches the specific IP network segment and NE
type at the specific intervals based on the settings.
13 In the NE Data, select a NE that to create, click Create.
----End
5.5.8 Creating Optical NEs

The U2000 manages the WDM equipment and OptiX BWS 1600S by using optical NEs. There
are four types of optical NEs. They are WDM_OADM, WDM_OEQ, WDM_OLA and
WDM_OTM. OptiX OSN 1800 only supports WDM_OTM and WDM_OADM. OptiX BWS
1600S only supports WDM_OTM.
Prerequisite
l The license must be installed and the license must support creating the NE of the type.
l Applies to the WDM equipment and OptiX BWS 1600S.
Procedure
1 Right-click in the blank space of the Main Topology and choose New > NE from the shortcut
menu.
2 Select the optical NE type for the optical NE in the displayed dialog box.
3 In the General Attributes tab, set the attributes of the optical NE.
NOTE
An OEQ NE is an OLA NE that enables the equalization of optical power and dispersion. If an OLA NE
has the boards for dispersion compensation and power compensation, the OLA NE should be changed to
an OEQ NE.
4 Click the Resource Division tab. Select NEs or boards from the Idle ONE and click .
5 Click OK.
6 Click in the blank space of the Main Topology and the NE icon appears in the position where
you clicked.
----End
5.5.9 Creating Virtual NEs

To display the topological relations between the equipment that is directly managed by the
U2000 and the equipment that is indirectly managed by the U2000 on the topology, you must
create virtual NEs so that the U2000 manages them together with the regular NEs in a uniform
manner.

Prerequisite
l Applies to the SDH and PTN NE.
Procedure
1 Right-click the Main Topology and choose New > NE from the shortcut menu.
2 On the Object Type tree of the displayed dialog box, choose SDH Series > Virtual NE or PTN
Series > Virtual L2 NE or PTN Series > Virtual L3 NE or PTN Series > Virtual Physical
Layer NE from the Object Tree.
3 Enter the ID, Name, and Remarks of the NE.
4 Click OK. Then click the Main Topology. The NE icon is displayed at the spot where you clicked
the mouse button.
----End

Prerequisite
l Applies to the Router series, Switch series, Security series, Access series NEs.
Context
According to different NE types, the U2000 can access the NEs to be managed through SNMP
or MML. During the manual or automatic creation of an SMMP or a /MML NE, the U2000 uses
the default /MML parameter template to map to the specified NEs so that the SNMP/MML
protocol parameters that are supported by the NEs to be managed can be determined. The
SNMP/MML parameter template that is successfully mapped acts as the SNMP/MML parameter
setting for the NE. All further management operations on the NE take the SNMP/MML
parameter. When the NE access protocol parameter changes, you need to modify the access
protocol parameter of the specified NE.
Procedure
1 Select a NE node or subnet in the navigation tree.
NOTE
l To select multiple NE nodes simultaneously, press Ctrl and then click the desired NE nodes.
l When no NE node is selected, the SNMP/MML parameter setting list displays the SNMP/MML
parameter settings of all NEs.
2 Choose Administration > NE Communicate Parameter > NE Access Protocol

Parameters from the main menu.

3 The template details are as follows:

l In the NE Access Protocol Parameters window, select a parameter template and then click
Display.
l In the NE Access Protocol Parameters window, double-click a record in the NE parameter
list.
The details about the selected record are displayed in the lower part of the window.
4 Modify the relate parameters as follows:
1. Enter the desired value in the related text box.
2. Click Test.
The test result is displayed in a dialog box.
3. Click Apply to save the modification.
NOTE
l In the NE Access Protocol Parameters window, click Reset. In the dialog box that is displayed, select,
add, or delete the protocol template of the related SMMP version as required. Then, click Display. The
details about the related protocol template are displayed. The template parameters cannot be set in this
dialog box.
l Set a parameter of the protocol template. Choose Administration > NE Communicate Parameter >
Default Access Protocol Parameters from the main menu. Double-click a record in the parameter
list. Then, click Apply to save the modification.
----End
5.6 Configuring the NE Data

Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the U2000 can manage and operate the NE.
Context
NOTE
The function of Synchronizing the NE Configuration Data is applicable to all series NEs. The other
functions of Configuring the NE data Manually, Replicating the NE Data, Uploading the NE Data,
and Configuring Virtual NE Data are applicable to MSTP, WDM, NA WDM, RTN, PTN, Marine series
NEs only.
5.6.1 Synchronizing the NE Configuration Data

Introduce the method of synchronize the NE configuration data manually.
5.6.2 Configuring the NE Data Manually

By configuring NE data manually, you can configure the board slot information of an NE.
5.6.3 Replicating the NE Data
During the network planning, preconfiguration NEs are used to simulate the entire network. In
this situation, you need to configure a lot of identical NE data. The function of duplicating the
NE configuration data can simplify your operation and improve the efficiency.
5.6.4 Uploading the NE Data
By uploading the NE data, you can synchronize the current NE configuration data to the network
management system directly.
5.6.5 Configuring Virtual NE Data
When planning a network, a user uses virtual NEs to simulate the whole network. Virtual NEs
can be configured separately or in batches on the U2000.
5.6.1 Synchronizing the NE Configuration Data

Prerequisite
The NE must be in the Unsynchronized state.
Context
l For the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, If the data in the
U2000 is inconsistent with the data in the NE, the NE icon has the sign.
l Before synchronizing Layer 2 VLAN data from switches, you must enable the privilege
function and set the privilege level and password when setting Telnet parameters.
Procedure
l Method 1
1. Choose Configuration > Synchronize NE Data from the main menu.
2. In the Object Tree, select one or more NEs and click .

3. Select one or more unsynchronized NEs, click the Synchronize button or right-click
and choose Synchronize from the shortcut menu. The U2000 begins to synchronize
the data.
NOTE
Click the buttons in the Option column and you can select the advance attributes that you wan
to synchronize.
The buttons in the Option column are applicable to the routers, switches, Metro services
platforms, security gateway, service monitoring gateway, and the SVN equipments.
l Method 2
NOTE
1. On the Main Topology, select the NE that is marked with . Right-click and choose
Synchronize NE Data.

2. In the Synchronize NE Data window, click the Synchronize button or right-click

the data.
l Method 3
NOTE
1. Choose Configuration > NE Configuration Data Management from the main
menu.

and choose Synchronize from the shortcut menu.
4. Click OK. The U2000 begins to synchronize the data.
5. Click Close in the Operation Result dialog box.
l Method 4
NOTE
Applies to the Router series, Switch series, Security series NEs.

1. Right-click the NE on the Main Topology and choose NE Explorer from the shortcut
menu.
2. In the NE Explorer, after querying the services informations, right-click the result
and select Synchronize.
----End
5.6.2 Configuring the NE Data Manually

By configuring NE data manually, you can configure the board slot information of an NE.
Prerequisite
l The NE must be created successfully.
Procedure
1 Select the NE whose data you want to configure.
If the NE to be configured is the You need
MSTP series NEs Double-click the unconfigured NE on the

Main Topology. The NE Configuration
Wizard dialog box is displayed.
RTN series NEs Double-click the unconfigured NE on the


WDM series NEs Double-click the optical NE with

unconfigured NE on the Main Topology.
Then, double-click the unconfigured NE in
the left-hand pane and the NE Configuration
Double-click the unconfigured NE on the
Marine series NEs Double-click the optical NE with

2 Choose Manual Configuration and click Next. The Confirm dialog box is displayed indicating
that manual configuration clears the data on the NE side.
3 Click OK. The Confirm dialog box is displayed indicating that manual configuration interrupts
the service on the NE.
4 Click OK. The Set NE Attribute dialog box is displayed.
5 Optional: If you need to modify the NE Attribute, set NE Name, NE Type, NE Remarks and
Subrack Type.
6 Click Next, and the NE slot window is displayed.
7 Optional: Click Query Logical Information to query the logical boards of the NE.

8 Optional: Click Query Physical Information to query the physical boards of the NE.
NOTE
The Query Logical Information and Query Physical Information operations cannot be performed for
a preconfigured NE.
9 Optional: Right-click on the slot to add a board.

10 Click Next to display the Send Configuration window.
11 Choose Verify and Run as required and click Finish.
NOTE
Verification is to run the verification command. Click Finish to deliver the configuration to NEs and the
basic configuration of the NEs is complete. After the successful verification, the NEs start to work normally.
----End
5.6.3 Replicating the NE Data

During the network planning, preconfiguration NEs are used to simulate the entire network. In
this situation, you need to configure a lot of identical NE data. The function of duplicating the
NE configuration data can simplify your operation and improve the efficiency.
Prerequisite
l The NE type and NE software version of the source NE must be consistent with those of
the copied NE.
Procedure
1 Select the NE whose data you want to Replicate.


PTN series NEs Double-click the unconfigured NE on the




2 Choose Copy NE Data and click Next. The NE Replication dialog box is displayed.
3 Select the NE in the drop-down list and click Start. The Confirm dialog box is displayed
indicating that the replication operation will overwrite all the data of the selected NE.

NOTE
After the NE data is replicated, only the data on the U2000 side is changed, but the data on the equipment
side is not changed.
4 Optional: If you select different equipment type, the Confirm dialog box is displayed indicating
that whether you sure to force to copy data from different equipment type.
5 Click OK. The Confirm dialog box is displayed indicating that the replication operation will
result in the NM data loss.
6 Click OK to start the replication. Wait for a few seconds. The Operation Result dialog box is
displayed.
7 Click Close.
----End
5.6.4 Uploading the NE Data

By uploading the NE data, you can synchronize the current NE configuration data to the network
management system directly.
Prerequisite
Procedure
1 Select the NE whose data you want to Replicate.



PTN series NEs Double-click the unconfigured NE on the



2 Choose Upload and click Next. The Confirm dialog box is displayed indicating that the upload
may take a long time.
3 Click OK to start the upload. The Operation Result dialog box is displayed when the uploading
is completed.
4 Click Close.
----End

5.6.5 Configuring Virtual NE Data

When planning a network, a user uses virtual NEs to simulate the whole network. Virtual NEs
can be configured separately or in batches on the U2000.
Prerequisite
l The type and NE software version of the source NE must be the same as those of the
destination NE.
l Applies to the SDH and PTN NE.
Context
A large amount of same NE data needs to be configured. In this case, NE data can be configured
in batches to simplify the operation. As a result, the working efficiency is improved. To configure
NE data in batches, copy the specified NE data to one or more NEs so that the data of the virtual
NEs is consistent with each other.
NOTE
l Duplicating the NE configuration data leads to the loss of the original data of the destination NE on
the U2000 side.
l Data duplication between the virtual NE and non-virtual NE is not supported.
Procedure
l Configure Data Separately:
1. On the Main Topology, double-click an empty NE to display the NE Panel.
2. Right-click the NE Panel and choose Add a New Board.
NOTE
Add a New Board is used to add the board type of the virtual NE. Then add the board according
to the board type.
3. After setting Name, Port Type, Level and Port Number for the board, click OK.
In this case, you can right-click the NE Panel to query the added board type.
4. Right-click the NE slot and choose the board type. Then add the board. After adding
the board, exit from the NE Panel.
l Configure Data in Batches:
menu.
2. Select the source NE and the required virtual NE from the Object Tree, and then click
.
NOTE
The source NE refers to the virtual NE that is configured with the NE data. Its data needs to be
copied to other empty NEs.
3. Select the source NE from the NE list. Right-click it and choose Copy.
4. Select one or more destination NEs, right-click and choose Paste from the shortcut
menu.

A confirmation dialog box is displayed, indicating that duplicating the NE

configuration data leads to the loss of the original data of the destination NE on the
U2000 side.
5. Click OK to start the duplication. Wait for several seconds and the Operation
Result dialog box is displayed.
6. Click Close.
----End
5.7 Adding Boards

In the NE Panel, you can add a board.
NOTE
The following functions are applies to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
5.7.1 Adding Boards

After the NE data is configured, if physical boards are added, you need to add boards on the NE
Panel. You can either add the physical boards that actually operate on the NE or add the logical
boards that do not exist on the actual equipment.
5.7.2 Adding Sub-Boards
The equipment can realize different functions after you add different sub-boards to a processing
board.
5.7.1 Adding Boards

After the NE data is configured, if physical boards are added, you need to add boards on the NE
Panel. You can either add the physical boards that actually operate on the NE or add the logical
boards that do not exist on the actual equipment.
Prerequisite
l This operation is not applicable to access NEs MA5620E and MA5626E, routers, switches,
and security NEs.
l The NE must be created.
l There must be idle slots on the NE Panel.
Context
The physical boards are the actual boards inserted in the subrack. The logical boards are created
on the U2000 and are saved on the SCC board, but may not exist on the actual equipment.
NOTE
The NE panel is able to indicate the mapping relation between slots that house processing boards and
interface boards. When you click a processing board that is paired with an interface board in the NE panel,
the ID of the slot that houses the mapping interface board is displayed in orange.
Procedure
1 In the Main topology, double-click the icon of the NE to open the NE Panel.

NOTE
For the WDM NE, select the NE to be added in the left pane on the NE Panel after performing the preceding
operation.
2 Right-click the selected idle slot and select the board you want to add.
3 Optional: For the PTN NE, click the to add physical boards in batches.
----End
5.7.2 Adding Sub-Boards

The equipment can realize different functions after you add different sub-boards to a processing
board.
Prerequisite
l You must be an NM user with "NE maintainer" authority or higher.
l Applies to only the MP1 board and the CXP board.
Context
Hot swappable service sub-board interfaces are provided on the MP1 board and the CXP
board. When different service sub-boards are inserted, the TDM E1, IMA E1, ML-PPP E1, ATM
STM-N and channelized STM-N signals can be assessed and processed.
Procedure
1 Double-click an NE on the Main Topology and the NE Panel is displayed in the user interface.
2 Select the desired processing board, right-click in the blank area that displays sub-boards, and
select the desired sub-board.
----End
5.8 Creating Connections

You can create link and fiber/cable by using the U2000.

Context
NOTE
The U2000 does not support the ability to directly create connections for access NEs in a topology view.
5.8.1 Creating Fibers Manually

You must create fibers before configuring services. You can manually create fibers one by one
in the scenario where a few fibers are required.
5.8.2 Searching for Fibers/Cables Automatically
By using the fiber/cable search feature, you can check whether the specified optical interface is
connected to a fiber. You can quickly create a fiber for this optical interface by using the
U2000. For a newly created network, after configuring boards on the U2000, you can search for
all optical interfaces to create fibers for the entire network. In this way, you can monitor the
actual working status of fibers.
5.8.3 Creating Fibers/Cables in the Synchronization Mode
After the equipment commissioning is completed, the fiber/cable connections might exist on the
NE. You can synchronize on the U2000 the internal fiber/cable connection data of the NE with
the U2000 side.
5.8.4 Creating Fiber Connections in Graphic Mode
In graphic mode, you can create fiber connections on the Main Topology or the signal flow
diagram directly. This mode is applicable to scenarios where a small number of fiber connections
are to be created one by one.
5.8.5 Creating Fiber/Cable Connections in Batches
In Fiber/Cable Management, you can manage the Fiber/Cable connections between NEs and
inside NEs in a unified manner. In this case, Fiber/Cable connections can be created in an easy
manner. This mode is applicable to scenarios where a large number of Fiber/Cable connections
are to be created.
5.8.6 Creating DCN Communication Cable
The U2000 can communicate with NEs through the Ethernet port or serial port. The NEs also
communicate with each other through the extended ECC(Embedded Control Channel).
Depending on the communication mode, different types of cables can be created on the
U2000.
5.8.7 Creating a Link Manually
This topic describes how to create a link manually.
5.8.8 Creating Links Automatically
Using the link search function, you can know whether any links are connected at a specified
interface. This helps you quickly create links in batches at the interface. For a newly created
network, you can search for all the interfaces networkwide to create links after you complete
the board configuration on the U2000. In this way, you can monitor the actual working state of
each link.
5.8.9 Automatically Creating Radio Links
Using the fiber/cable search function, you can know whether any radio links are connected at a
specified IF interface. This helps you quickly create radio links at the IF interface. For a newly
created network, you can search for all the IF interfaces networkwide to create radio links after
you complete the board configuration on the U2000. In this way, you can monitor the actual
working state of each radio link.
5.8.10 Manually Creating Radio Links

After you manually fill in the table, the U2000 can create radio links according to the
configuration information about the links. This operation is often used when actual radio link is
not formed.
5.8.11 Creating Virtual Fibers
When the U2000 manages the SDH, PTN and WDM NE at the same time, you can create virtual
fibers for SDH or PTN NE with WDM NE in between, to facilitate administration.
5.8.12 Restoring the Fiber Connection
Due to misoperations or other causes, the fiber connection is deleted on the U2000. This does
not affect the service transport, but you need to restore the fiber connection quickly, to restore
the monitoring on the U2000.
5.8.1 Creating Fibers Manually

You must create fibers before configuring services. You can manually create fibers one by one
in the scenario where a few fibers are required.
Prerequisite
l The boards to be connected with fibers or cables must be created.
l You must create a REG before creating a fiber that passes the REG.
l The dynamic port must be created.
Context
When a fiber is created, it is usually bidirectional. But when the fiber is connected to the ports
of the REG functions or the MSTP and WDM NE, the fiber is unidirectional.
Procedure
1 Right-click in the Main Topology and choose New > Link.
2 On the Object Type tree of the displayed dialog box, choose Fiber/Cable > Fiber.
3 Click the button in Source NE. Then, the cursor is display as +.
4 Click the source NE of the fiber in the Main Topology.
5 In the Select Fiber/Cable Source dialog box, select the source board and source port.
6 Click OK. The Add Object dialog box is displayed.
7 Click the button in Sink NE. Then, the cursor is display as +.
8 In the Select Fiber/Cable Sink dialog box, select the sink board and sink port.
TIP
When selecting a wrong source or sink NE, right-click and click OK in the Coordinate Selection dialog
box to exit.
9 Click OK. In the Add Object dialog box, enter the information about the attributes of the fiber.

10 Click OK.
The created fiber appears between the source and sink NEs in the Main Topology.
11 Select the fiber you create, right-click and choose Detect Link from the shortcut menu.
The Operation Result dialog box is displayed indicating the fiber connection information.
----End

Prerequisite
l The optical interfaces of every NE must be connected using fibers.
l The boards of every NE must be created on the U2000.
l Applying to the MSTP, WDM, NA WDM, RTN, Marine NEs, but the OptiX OSN 1800
does not support. For PTN NEs, searching for fibers/cables automatically please see 5.8.8
Creating Links Automatically.

Context
l If conflicting fibers are found during the creation, delete the conflicting fibers on the
U2000 before you start creating fibers.
l When a fiber between two MSTP NEs passes through a WDM NE, if the normal fiber
between an MSTP NE and a WDM NE has been created on the U2000, the fiber found by
the trail search function is created as a virtual fiber. If the WDM NE is not created on the
U2000, the fiber is created as a normal fiber.
l Fibers that connect two WDM NEs cannot be searched.
l When a fiber is created, it is usually bidirectional. But when the fiber is connected to the
ports of the REG functions or the MSTP and WDM equipment, the fiber is unidirectional.
Procedure
1 Choose File > Discovery > Fiber from the main menu.
2 In the left pane select some ports from one or more NEs and click Search to search for the fibers
or cables. A progress bar is displayed showing the progress of the search.
NOTE
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system
only searches for the ports that do not have fibers.
l To check if the created fiber is consistent with the actual fiber connection, leave the check box
unchecked.
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, and if all
the selected ports have fibers created, the system displays a message indicating that the search field is
null.
3 A prompt appears telling you that the operation was successful. Click Close.
4 To create fibers, select one or more fibers from the Physical Fiber/Cable Link List list and
click Create Fiber/Cable.
NOTE
l The NA WDM NEs do not support the function of conflicting fiber.

l When one or more fibers are selected in the Physical Fiber/Cable Link List list, fibers that conflict
with the selected fibers, are shown in the Logical Fiber/Cable Link List list. If there is any conflicting
fiber, proceed to Step 5 and delete it before creating fibers.
l During fiber creation, if all the selected fibers are in the Already created state, the system displays
the message as follows: No fiber to create.
5 To delete the conflicting fibers, from the Logical Fiber/Cable Link List list select one or more
fibers whose values are Yes for the Conflict with logical link(Y/N) parameter in the
Misconnected Fiber/Cable list. Click Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the fiber that is created through search is incomplete, you can
supplement the information about the fiber by modifying the fiber/cable information.

5.8.3 Creating Fibers/Cables in the Synchronization Mode

After the equipment commissioning is completed, the fiber/cable connections might exist on the
NE. You can synchronize on the U2000 the internal fiber/cable connection data of the NE with
the U2000 side.
Prerequisite
l The corresponding logical board must be created.
l Applies to OptiX OSN 3800, OptiX OSN 6800, OptiX OSN 8800 T32, OptiX OSN 8800
T64, OptiX OSN 3800A, OptiX OSN 6800A, OptiX OSN 8800 T32(NA), OptiX OSN
8800 T64(NA).
Context
Conflicting fibers/cables refer to the different fibers configured on the NE and U2000 sides.
Click Synchronize and Create Fiber/Cable, and then the conflicting fibers/cables are displayed
in the Uncreated Fiber/Cable in NMS and Uncreated Fiber in NE user interfaces. The
conflicting fibers/cables cannot be synchronized between the U2000 and the NE. In this case,
based on the networking design, delete the incorrect fibers/cables. After that, click Create Fiber/
Cable and re-create the remaining fibers/cables.
Procedure
1 In the Main Topology, double-click an optical NE, right-click an NE from the left tree and choose
NE Explorer from the shortcut menu.
NOTE
For the OptiX OSN 6800, OptiX OSN 8800 T32, OptiX OSN 8800 T64, OptiX OSN 6800A, OptiX OSN
8800 T32(NA), OptiX OSN 8800 T64(NA), you can right-click an NE in the Main Topology and choose
NE Explorer from the shortcut menu.
2 In the NE Explorer, select an NE and choose Function Tree > Configuration > Fiber
Synchronization.
3 Click Synchronize, and the data of the internal fiber connections on the U2000 side and that on
the NE side is displayed.
NOTE
l Synchronized Fiber/Cable: Indicates the fibers that exist on both the U2000 and NE sides.
l Uncreated Fiber/Cable in NMS: Indicates the fibers that exist on only the NE side.
l Uncreated Fiber/Cable in NE: Indicates the fibers that exist on only the U2000 side.
4 If Uncreated Fiber/Cable in NMS or Uncreated Fiber/Cable in NE exists, select all the fibers.
Click Create Fiber/Cable, and the Operation Result dialog box is displayed. Click Close. The
synchronized fibers/cables are displayed in the Synchronized Fiber/Cable list.
5 If conflicting fibers/cables exist and thus you fail to create the fibers/cables, click Delete Fiber/
Cable to delete the incorrect Uncreated Fiber/Cable in U2000, or click Create Fiber/Cable and
then re-create the remaining fibers/cables.
----End

5.8.4 Creating Fiber Connections in Graphic Mode

In graphic mode, you can create fiber connections on the Main Topology or the signal flow
diagram directly. This mode is applicable to scenarios where a small number of fiber connections
are to be created one by one.
Prerequisite
l Optical NEs and NEs must be created.
l Line boards that have ports of the same level must be properly created.
l Applies to WDM equipment.
Context
l Boards that require fiber connection are the wavelength conversion board, multiplexer
board, demultiplexer board, and optical amplifier board.
l If wavelength pass-through exists, ensure direct fiber connection from the demultiplexer
board to the multiplexer board. No cross-connection is allowed.
Procedure
l To create fiber connections inside an NE, do as follows:
1. Double-click an optical NE on the Main Topology. Click the Signal Flow Diagram
tab.
2. In the Signal Flow Diagram, right-click in the blank area and choose Create Fiber
from the shortcut menu. The cursor is displayed as "+".
3. Select the source board and port and click OK. The cursor is displayed as "+".
4. Select the sink board and port and click OK.
TIP
When a wrong source or sink board or port is selected, right-click to cancel the operation and
exit object selection.
5. In the Create Fiber/Cable dialog box, enter the attributes of the fiber.

6. Click OK.
l To creating fiber connections between NEs, do as follows:
1. Click the shortcut icon , and click the Main Topology tab. The cursor is displayed
as "+" .
2. Click the source NE of the fiber on the Main Topology.
3. Select the source board and source port in the Select the source end of the link dialog
box displayed.
4. Click OK. The Main Topology is displayed and the cursor is displayed as "+" again.
5. Click the sink NE of the fiber in the Main Topology.
6. Select the sink board and sink port in the Select the sink end of the link dialog box
displayed.
7. Click OK and enter the attributes of the fiber in the Create Fiber/Cable dialog box
displayed.
8. Click OK. The created fiber is displayed between the source NE and the sink NE on
the Main Topology.
----End
5.8.5 Creating Fiber/Cable Connections in Batches

In Fiber/Cable Management, you can manage the Fiber/Cable connections between NEs and
inside NEs in a unified manner. In this case, Fiber/Cable connections can be created in an easy
manner. This mode is applicable to scenarios where a large number of Fiber/Cable connections
are to be created.
Prerequisite
l The boards to be connected with the fiber or cable have been created.

Context
For service configuration, Fiber/Cable between NEs and boards inside NEs need to be connected.
Procedure
1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the main menu.
2 Click Create, and the Create Fibers in Batches dialog box is displayed.
3 Click New, modify the attribute value according to actual requirements.
NOTE
The transmission system adopts the two-fiber bidirectional mode to achieve bidirectional transmission.
When the created fiber connection is single-fiber unidirectional, you need to create another fiber connection
in the other direction.
4 Click Apply. Repeat Step 3 to create another fiber connection.
5 Click Cancle to complete the settings. The created fiber connections are displayed in the Fiber/
Cable Information list.
----End
5.8.6 Creating DCN Communication Cable

The U2000 can communicate with NEs through the Ethernet port or serial port. The NEs also
communicate with each other through the extended ECC(Embedded Control Channel).
Depending on the communication mode, different types of cables can be created on the
U2000.
Prerequisite
l Applies to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
Procedure
1 Right-click in the blank space of the Main Topology and choose New > Link from the shortcut
menu.
2 On the Object Type tree of the displayed dialog box, choose Fiber/Cable > Cable.
3 Enter the cable attributes in the right-hand pane.

4 Click OK. The cable is displayed on the Main Topology between the U2000 and the GNE.
----End
Follow-up Procedure
If the NEs at the two ends of the DCN(Data Communication Network) communication cables
do not belong to the same subnet, you have to return to the upper-level view of the subnet to
view the created DCN communication cables.
5.8.7 Creating a Link Manually

This topic describes how to create a link manually.
Prerequisite
l The NE must be added to the U2000 and the interface data must be loaded successfully.
l Applying to the Router series, Switch series, Security series NEs, 3rd-Party series NEs.
Procedure
l Method 1
1. Right-click in the Main Topology and choose New > Link.
NOTE
You can also click the , select the Link from the drop-down list.
2. On the Object left of the displayed dialog box, choose Link > IP Link or Link > L2
Link or Link > Virtual Link.
3. On the Object right of the displayed dialog box, set the Link Name, Source NE,
Source Port, Sink NE, Sink Port.
4. Optional: On the Object right of the displayed dialog box, set the Remarks, User
Label, Owner.
5. Click OK.
The created link appears between the source and sink NEs in the Main Topology.
l Method 2
1. Choose Inventory > Link Management from the main menu.
2. In the Link Management window, click New.
NOTE
Alternatively, right-click in the query area and choose New from the shortcut menu.
3. In the Create Link dialog box that is displayed, click New, set Link Type, and specify
Source NE, Source Port, Sink NE, and Sink Port.
NOTE
l After you specify Source NE, Source Port, Sink NE, and Sink Port, a name is created
automatically in the Link Name field. You can rename the link according to your naming
conventions.
l To select a source NE or sink NE, expand or double-click a submap record and select the
required NE in the submap.

4. Click Apply. In the Operation Result dialog box, Operation succeeded is displayed.
Then, click Close.
The created link is displayed in the query result area of link management.
NOTE
If creating a link is abnormal, the cause is displayed in the Operation Result dialog box. You
can rectify the fault based on the cause.
----End

each link.
Prerequisite
l This operation is applicable to PTN series, Router series, Switch series, Security series
NEs, 3rd-Party series NEs.
l NEs must be created on the U2000 and the interface data must be successfully loaded.
l In the case of an LLDP link, you need to configure the SNMP, MIB view, and trap on the
NEs and enable the global LLDP on the NEs or on the U2000. For details, see the topic
LLDP Management for each NE Explorer in the topic Router and Switch Network
Management in the Online Help.
Context
l Links are logic and they cannot present the fiber/cable connections between devices.
Certain links must be imported to the U2000 as fibers/cables for management.
l LLDP discovery link: It refers to the Link Layer Discovery Protocol (LLDP) link. The Link
Layer Discovery Protocol (LLDP) is an L2D protocol defined in the IEEE 802.1ab. When
the LLDP protocol runs on the NEs, the U2000 can obtain the Layer 2 information about
all the NEs it connects and the detailed information about the network topology. This
expands the scope of network management. LLDP also helps find unreasonable
configurations on the network and reports the configurations to the U2000. This helps to
remove the errors in configurations timely.
l RPR link: It refers to the Resilient Packet Ring (RPR) link. The RPR protocol is a new
MAC layer protocol defined by IEEE 802.17. It is defined with the purpose of optimizing
the transmission of data packages and establishing an Ethernet MAN standard of sharing
bandwidth fairly over transmission media. Based on the high bandwidth usage, multi-server
access, high bandwidth of optical network, and powerful self-healing capability, the RPR
technology has the following features:
– Two-ring structure
– Space multiplexing mechanism
– Flexible service bandwidth granularity
– Dynamic bandwidth sharing and allocation
– Statistic multiplexing

– Service level
– Automatic recognition of the structure of network topology
– Protection switching based on the source route
l Cluster link: It refers to the cluster link. A cluster is a management domain with a group
of switches, including a command switch and multiple member switches. It manages all
the switches in the cluster, through a public IP address.
l SideBySide link: The IP addresses of the interfaces at both ends of the link are a pair of IP
addresses with 30-bit subnet mask.
Procedure
1 Choose File > Discovery > Link from the main menu.
2 Optional: In the Link Search window, select Nonexistent Links in NMS, Existed Links in
NMS, or Error Links as required.
3 Optional: Above the left-hand Object Tree, select Do you want to synchronize LLDP data
on the equipment? as required.
4 On the left-hand Object Tree, select one or more NEs, and click Search.
5 In the LLDP Status Management dialog box, set LLDP Status of the NEs to Open. Click
OK. After you complete the operation, a dialog box is displayed indicating that the operation is
successful. Click Close.
NOTE
l The LLDP Status Management function is applicable to only routers, switches, the security NE.
l If a network does not have the preceding NE, the LLDP Status Management dialog box is not
displayed.
A dialog box is displayed indicating that It takes 30s before the enabled LLDP takes effect.
Are you sure to perform search? You can make the confirmation according to the actual
situation.
6 The progress bar shows the operation progress.
7 In the dialog box that prompts the success, click Close. In the window, the search results for
each links are displayed.
NOTE
l Nonexistent Links in NMS: The link exists only on NEs and is not created on the NMS.
l Existed Links in NMS: The link exists on the NMS and on the NEs.
l Error Links: The link has certain different data on NEs and the NMS.
8 Optional: You can select Nonexistent Links in NMS, Existed Links in NMS, or Error
Links to view the status of links. You can select a conflicting link and click Delete Error
Links to delete the link.
9 In the window, select one or more nonexistent links, and click Create.
The progress bar is displayed showing the progress of link creation.
10 In the dialog box that prompts the success, click Close.

The Are you sure to import links as fibers/cables dialog box is displayed.
11 Click OK in the Confirm dialog box.

l 1. The Import Link dialog box is displayed.

2. In the Import Link dialog box, select the one or more links and do as follows:
– Click . The selected link is moved to the Selected Link area.
– Click . All links in the Available Link area are moved to the Selected Link
area. This operation is applicable to batch import.
– Click . The selected link is moved to the Available Link area.
– Click . All links in the Selected Link area are moved to the Available Link
area.
NOTE
For PTN NEs, when import the link, you can set whether to allot IP address automatic on the
ports of the link.
3. Click OK.
NOTE
l After you successfully create a link in the U2000, the status of the link is displayed as Existed.
l The created links are displayed in the Link Management area.
l The imported fibers/cables are displayed in the Fiber/Cable Management area.
\
l Click Cancel in the Confirm dialog box.
NOTE
12 Optional: Select conflicted links and click Error Links to delete the records.
----End
Follow-up Procedure
If you want to import links as fibers/cables after clicked the Cancel in the Import Link displayed
dialog box, you can perform the follow steps:
1. Choose Inventory > Fiber/Cable > Fiber/Cable Management from the main menu.
2. In the Fiber/Cable Management area, right-click, and choose Import Link from the
shortcut menu.
l Click . The selected link is moved to the Selected Link area.
l Click . All links in the Available Link area are moved to the Selected Link area.
This operation is applicable to batch import.
l Click . The selected link is moved to the Available Link area.
l Click . All links in the Selected Link area are moved to the Available Link area.
NOTE
For PTN NEs, when import the link, you can set whether to allot IP address automatic on the ports
of the link.
4. Click OK. The imported fibers/cables are displayed in the Fiber/Cable Management area.

5.8.9 Automatically Creating Radio Links

Using the fiber/cable search function, you can know whether any radio links are connected at a
specified IF interface. This helps you quickly create radio links at the IF interface. For a newly
created network, you can search for all the IF interfaces networkwide to create radio links after
you complete the board configuration on the U2000. In this way, you can monitor the actual
working state of each radio link.
Prerequisite
l Applies to the RTN and PTN NEs.
l The IF board for each NE must be created on the U2000.
Context
The radio frequency wireless signals within the frequency range of 300 MHz to 300 GHz are
called radio signals. The links that transmit radio signals are called radio links.
Procedure
2 In the left-hand pane, select IF interfaces for one or multiple radio NEs. Click Search. A progress
bar is displayed.
NOTE
l If you check the Do not search the ports with Fiber/Cable Created on NMS check box, the system
does not search for the ports at which radio links are already created.
l If you need to check consistency between the created radio links and the actual radio links, do not check
this check box.
l If you check this check box and if all the selected ports radio links are created, a dialog box is displayed
after the search is complete, telling that the search domain is empty.
3 After the search is complete, a dialog box is displayed, telling that the operation was successful.
Click Close.
4 In the Physcal Fiber/Cable Link List list, select one or multiple radio links. Click Create Fiber/
Cable.
NOTE
l When you select one or multiple radio links in the Physcal Fiber/Cable Link List list, the radio links
that conflict with the selected ones are automatically displayed in the Logical Fiber/Cable Link
List list. In this case, refer to Step 5 to delete the conflicting radio links before the creation.
l During the creation of radio links, if the selected links are all in the Already created state, the system
prompts No fiber to create.
5 In the Logical Fiber/Cable Link List list, select one or multiple conflicting radio links (the
Conflict with logical link (Y/N) value of which in the Misconnected Fiber/Cable list is
displayed as Yes), Click Delete Fiber/Cable.
----End

Subsequent Handling
When the information about the radio link that is created through search is incomplete, you can
supplement the information about the radio link by modifying the fiber/cable information.
5.8.10 Manually Creating Radio Links

After you manually fill in the table, the U2000 can create radio links according to the
configuration information about the links. This operation is often used when actual radio link is
not formed.
Prerequisite
l Applies to the RTN and PTN NEs.
l The boards to be connected with radio links must be created.
Context
Usually, the radio frequency wireless signal within the frequency range of 300 MHz to 300 GHz
is called a radio signal. The link that transmits radio signals is called a radio link.
Procedure
1 Click the shortcut icon on the toolbar of the Main Topology and the cursor changes to a
+ sign.
2 Click the source NE of the radio link on the Main Topology.
3 Select the source board and port in the Select the source end of the link dialog box.
4 Click OK and the cursor changes to a + sign.
5 Click the sink NE of the radio link on the Main Topology.
6 Select the sink board and port in the Select the sink end of the link dialog box.
TIP
When selecting the wrong source or sink NE, right-click and click OK in the Object Selection dialog box
to exit.
7 Click OK. Enter the information of the fiber or cable in the Create Microwave Link dialog
box.

8 Click OK. The created radio link appears between the source and sink NEs on the Main
Topology.
----End
5.8.11 Creating Virtual Fibers

When the U2000 manages the SDH, PTN and WDM NE at the same time, you can create virtual
fibers for SDH or PTN NE with WDM NE in between, to facilitate administration.
Prerequisite
l You must create fiber connections according to the true fibers that connect the SDH and
WDM NE.
l You must create fiber connections according to the true fibers that connect the PTN and
WDM NE.
l The U2000 must manage the SDH, PTN and WDM NE at the same time.
Context
l For SDH NE, the virtual fibers ensure the independence of automatic fiber search and SDH
trail management.
l For WDM NE, when true fibers change into virtual fibers at the bearer layer, wavelength
management is not affected even if the true fibers are deleted.
l The source and sink ports of the virtual fibers must be the SDH ports. On the source and
sink ports, there must be two physical fibers that are connected to the WDM NE.
l The source and sink ports of the virtual fibers must be the PTN ports. On the source and
sink ports, there must be two physical fibers that are connected to the WDM NE.
l The virtual fiber does not support the expansion function.

Procedure
1 Right-click in the blank space of the Main Topology, and choose New > Link from the shortcut
menu.
2 On the Object Type tree of the displayed dialog box, choose Fiber/Cable > Virtual Fiber.
3 Click the button in Source NE. Then, the cursor is display as +.
4 Click the source NE of the virtual fiber in the Main Topology.
5 In the Select Fiber/Cable Source dialog box, select the source board and source port.
6 Click OK. The Add Object dialog box is displayed.
7 Click the button in Sink NE. Then, the cursor is display as +.
8 In the Select Fiber/Cable Sink dialog box, select the sink board and sink port.
TIP
When selecting a wrong source or sink NE, right-click and click OK in the Coordinate Selection dialog
box to exit.
9 Click OK. In the Add Object dialog box, enter the information about the attributes of the virtual
fiber.
10 Click OK.
The created virtual fiber appears between the source and sink NEs in the Main Topology.
11 Select the virtual fiber you create, right-click and choose Detect Link from the shortcut menu.
The Operation Result dialog box is displayed indicating the virtual fiber connection
information.
----End

5.8.12 Restoring the Fiber Connection

Due to misoperations or other causes, the fiber connection is deleted on the U2000. This does
not affect the service transport, but you need to restore the fiber connection quickly, to restore
the monitoring on the U2000.
Prerequisite
Context
NOTE
Except the method describes in this section, you can search out the actual fiber connections of the equipment
by using the fiber search function, and restore the fiber connection on the U2000. For details, see 5.8.2
Searching for Fibers/Cables Automatically.
Procedure
1 Choose Administration > Log Management > Query Operation Logs from the main menu.
2 According to the operation user that deletes the fiber and the time, select the corresponding
operation log. Double click the operation log. The Log Details dialog box is displayed.
3 In Log Details, view the information of the source and sink.
4 According to the information of the source and sink, create the fiber again.
NOTE
For the details of creating fibers, see 5.8 Creating Connections.
----End
5.9 Browsing Fibers/Cables

Fibers/Cables are at the physical layer of a transmission network. This section describes how to
query the physical and engineering information of fibers/cables, and detailed information of
trails that the fibers/cables carry.
5.9.1 Querying Fiber/Cable Information

On the U2000, you can view detailed information about a fiber/cable to learn its current status.
5.9.2 Querying Relevant Trails of a Fiber/Cable
In a real running network, a fiber/cable that is in use carries some trails. The number and
importance of the trails carried vary from different fiber/cable. You can view the relevant trails
of a fiber/cable to know the importance of the fiber/cable.
5.9.3 Querying Relevant Optical Power of a Fiber/Cable
The power of the optical signal is an important index for a transmission network. The optical
power has direct influence on the signal quality. The physical feature of the fiber/cable that
carries the optical signal has direct influence on the optical signal. Hence, you need to
periodically query the optical power of a fiber/cable.
5.9.4 Querying the Performance Data of a Radio Link

You can query the performance data of a radio link on the U2000. In addition, you can view the
performance data such as the power of the source and sink NEs and the bit error rate in charts.
5.9.1 Querying Fiber/Cable Information

On the U2000, you can view detailed information about a fiber/cable to learn its current status.
Prerequisite
Procedure
The information about all the fibers/cables is displayed in the Fiber/Cable Management
window.
2 Optional: Click Print. After setting the range in the window displayed, you can set parameter
for the printing in the Print dialog box.
3 Optional: Click Save As. After setting the range in the window displayed, you can save the
information about the fiber/cable within the specified range as a file.
NOTE
The fiber/cable information can be saved as a .xls, .txt, .html, or .csv file.
----End
5.9.2 Querying Relevant Trails of a Fiber/Cable

In a real running network, a fiber/cable that is in use carries some trails. The number and
importance of the trails carried vary from different fiber/cable. You can view the relevant trails
of a fiber/cable to know the importance of the fiber/cable.
Prerequisite
Applicable to MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
Procedure
window.
2 Right-click a fiber/cable in the pane and choose Browse Relevant Trails from the shortcut
menu.
Trails that the fiber/cable carries are displayed in the trail management window.
3 Optional: Click Print. After setting the range in the window displayed, you can set parameter
for the printing in the Print dialog box.
4 Optional: Click Save As. After setting the range in the window displayed, you can save the
information about the trail within the specified range as a file.

NOTE
The trail information can be saved as a .xls, .txt, .html, or .csv file.
----End
5.9.3 Querying Relevant Optical Power of a Fiber/Cable

The power of the optical signal is an important index for a transmission network. The optical
power has direct influence on the signal quality. The physical feature of the fiber/cable that
carries the optical signal has direct influence on the optical signal. Hence, you need to
periodically query the optical power of a fiber/cable.
Prerequisite
Applicable to MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
Context
If the fibers/cables color are turned to red which on the Main topology, that is because the fibers/
cables had R_LOS, MUT_LOS, ETH_LOS alarm.
Procedure
1 On the Main Topology or a subnet topology, right-click a fiber/cable. Choose Query Relevant
Optical Power from the shortcut menu.
The Optical Power Management window is displayed.
2 Click the Port Optical Power tab.
3 Click Query.
The input and output optical power of the fiber/cable is displayed. The Operation Result
window is displayed.
4 Click Close.
5 Click the Graphic tab. The optical power values of the source and sink of the fiber/cable are
displayed in the coordinates.

----End
5.9.4 Querying the Performance Data of a Radio Link

You can query the performance data of a radio link on the U2000. In addition, you can view the
performance data such as the power of the source and sink NEs and the bit error rate in charts.
Prerequisite
l A radio link must be configured on the U2000.
l The source and sink NEs of a radio link must work in the normal state.
Procedure
1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the main menu. In the
window that is displayed, right-click a radio link and choose Radio Link Performance
Statistics from the shortcut menu.
NOTE
Alternatively, you can right-click a radio link in the Main Topology and choose Radio Link Performance
Statistics from the shortcut menu.
2 In the Radio Link Performance Statistics dialog box, click Query. Then, you can view the
performance statistics of the radio link in a chart.

NOTE
If the performance monitoring function is disabled on the sink and source NEs of a radio link, the system
will display an error message and prompt you to enable the function before starting the performance
measurement jobs.
3 Optional: In the Radio Link Performance Statistics dialog box, set the time for measuring
the performance of the radio link, including the Monitor Period parameter.
NOTE
If you set invalid query conditions, for example, the start time is later than the end time, the system will
prompt you to modify the conditions.
4 Optional: On the Options tab page of the Radio Link Performance Statistics dialog box, set
the parameters for measuring the performance of the radio link. This helps you view the
performance statistical charts of different indicators.
5 Optional: Print or save the performance statistical charts.
----End
5.10 Adjusting Topology Objects

You can modify the settings when creating the network topology by using the U2000. For
example, modify the NE name, adjust the optical NE source, and modify the status of the
preconfigured NE and so on.
5.10.1 Balancing Load of the NE Explorer Process

To ensure a load balance of the NE Explorer process, you need to migrate NEs. When an NE
Explorer instance manages too many NEs, you can create a new NE Explorer process and migrate
some NEs to the new NE Explorer instance for management.

5.10.2 Modifying the NE ID and the Extended ID

The ECC protocol uses the NE ID to identify an NE uniquely. You need to assign a unique NE
ID to each NE when planning a network. If an NE ID conflicts with another NE ID, it results a
collision in the ECC route. As a result, it becomes difficult to manage some NEs. In the
commissioning or expansion process, when you need to adjust the original planning and modify
the NE ID, you can use the U2000 to achieve it.
5.10.3 Modifying the NE Name
You can modify the NE name as required. This operation does not affect the running of the NE.
5.10.4 Modifying the NE IP
Incorrect settings of the IP address may affect the communication between the U2000 and an
NE, and between NEs. You can rectify the fault of this type by modifying the IP address of the
NE.
5.10.5 Modifying the Optical NE Name
You can modify the optical NE name at any time as required. This operation does not affect the
running of the optical NE.
5.10.6 Adjusting Optical NE Resource
This operation re-allocates all or part of the boards on the subracks contained in the optical NE.
You can release the subracks or part of the boards on the subrack to the idle optical NE or obtain
resources from the idle optical NE.
5.10.7 Modifying the Status of a Preconfigured NE
To effectuate data of a preconfigured NE, you need to download the data from the U2000 to the
NE. After preconfiguring the NE, download the data to the NE in time.
5.10.8 Modifying the NM Name
You can modify the NM name as required. This operation does not affect the running of the
U2000.
5.10.9 Modifying Fiber/Cable Information
You can modify the name, attenuation, length, and type of a fiber/cable according to its
connection status and physical features.
5.10.10 Naming a Fiber/Cable
In the network management, you need to strictly plan the fiber/cable names, to ensure that faults
can be located quickly during maintenance and troubleshooting. On the U2000, you can use the
pre-defined naming rules to name the fibers/cables.
5.10.11 Copying Topology Objects
In the current topology view, you can copy a topology object from one subnet to another.
5.10.12 Moving Topology Objects
In the current topology view, you can move a topology object from one subnet to another.
5.10.1 Balancing Load of the NE Explorer Process

To ensure a load balance of the NE Explorer process, you need to migrate NEs. When an NE
Explorer instance manages too many NEs, you can create a new NE Explorer process and migrate
some NEs to the new NE Explorer instance for management.
Prerequisite

l The NMS maintenance tool server is started.

l Applies to the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, switcher series
NEs, and firewall series NEs.
Context
NOTE
The type of the new NE Explorer instance must be the same as that of the NE Explorer instance with
overloaded NEs.
Procedure
1 Choose Administration > Settings > NE Partition from the main menu.
2 In the left-hand pane, select a subnode and the NE name and other information of the subnode
are displayed in the right-hand pane.
3 In the information area of the right-hand pane, select the NEs that are wanted to be transferred.
4 Click the Move To button in the lower-right corner and the Ne transfer dialog box is displayed.
5 Select one or more destination NE explorers, and click Confirm.
6 The Move NE dialog box is displayed. A progress bar is displayed. When the progress bar shows
100%, it indicates that migration is complete.

7 Click Close.
----End
5.10.2 Modifying the NE ID and the Extended ID

The ECC protocol uses the NE ID to identify an NE uniquely. You need to assign a unique NE
ID to each NE when planning a network. If an NE ID conflicts with another NE ID, it results a
collision in the ECC route. As a result, it becomes difficult to manage some NEs. In the
commissioning or expansion process, when you need to adjust the original planning and modify
the NE ID, you can use the U2000 to achieve it.
Prerequisite
l The NE must be created.
CAUTION
Modifying the NE ID may interrupt NE communication and reset the NE.
Procedure
1 In the Main Topology, right-click an NE and choose NE Explorer from the shortcut menu.
2 In the NE Explorer, select an NE and choose Function Tree > Configuration > NE
Attribute.
3 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
4 Enter the New ID and the New Extended ID. Click OK.
5 Click OK in the Warning dialog box.

6 In the Operation Result dialog box, click Close.
----End
5.10.3 Modifying the NE Name

You can modify the NE name as required. This operation does not affect the running of the NE.
Prerequisite
Procedure
2 In the NE Explorer, select an NE and choose Function Tree > Configuration > NE
Attribute.
3 In the NE attribute dialog box, enter a new NE name, and click Apply. A dialog box is displayed,
indicating that the operation is successful.
NOTE
The NE name can contain up to 64 alphanumeric characters and symbols, but cannot contain the following
special characters: | : * ? " < >.
4 Click Close.
----End
5.10.4 Modifying the NE IP

Incorrect settings of the IP address may affect the communication between the U2000 and an
NE, and between NEs. You can rectify the fault of this type by modifying the IP address of the
NE.
Prerequisite
Precautions
l After you change the IP address, if the IP address of the NE and the IP address of the
U2000 server are in the same network segment, the communication between the U2000
and the NE is normal. Re-log the NE.
l If the IP address of the NE and the IP address of the U2000 server are in different network
segments, the communication between the U2000 and the NE stops. In this case, set a new
IP address for the computer where U2000 is installed restore the communication. Ensure
that it is in the same IP subnet segment as the original NE IP. Because of the restriction of
the SQL database, after you have changed the IP address of the computer, you must shut
down the U2000 client/server, restart the computer and start the U2000 client/server again.

Procedure
2 In the NE Explorer, select an NE and choose Function Tree > Communication >
Communication Parameters.
3 Set the IP, Extended ID, Gateway IP and Subnet Mask of the NE, in the Set NE Communication
Parameters.
4 Click Apply. Click OK in the two displayed Warning dialog boxes. Then click Close in the
displayed Operation Result dialog box.
----End
5.10.5 Modifying the Optical NE Name

You can modify the optical NE name at any time as required. This operation does not affect the
running of the optical NE.
Prerequisite
Procedure
1 On the Main Topology, right-click an optical NE, and choose Attribute from the shortcut menu.
2 In the displayed dialog box, enter the new optical NE name, and click OK.
NOTE
An optical NE name can contain letters, symbols, and numerals, but cannot contain the following special
characters: | : * ? " < >.
----End
5.10.6 Adjusting Optical NE Resource

This operation re-allocates all or part of the boards on the subracks contained in the optical NE.
You can release the subracks or part of the boards on the subrack to the idle optical NE or obtain
resources from the idle optical NE.
Prerequisite
l The optical NE or idle optical NE must have the resource.
Procedure
1 Right-click an optical NE and choose Attribute from the shortcut menu. The Object
Attributes dialog box is displayed.
2 In the displayed dialog box, click the Resource Division tab. In the Available Boards pane,
select the subrack or board resource that you want to add and click to add it to the
optical NE.

3 In the Selected Board pane, select the subrack or board resource that you want to delete and
click to release it to the idle optical NE.
4 Click OK.
----End
5.10.7 Modifying the Status of a Preconfigured NE

To effectuate data of a preconfigured NE, you need to download the data from the U2000 to the
NE. After preconfiguring the NE, download the data to the NE in time.
Prerequisite
l The preconfigured NE must be created.
l Applies to the SDH, Metro WDM and LH WDM NE.
Context
CAUTION
Downloading data of a preconfigured NE applies the NE settings on the U2000 to the physical
NE. If the data is incorrect, this may cause service interruption.
Procedure
1 Choose Configuration > NE Configuration Data Management from the main menu.
2 In the left-hand pane, select NEs and click .
3 Select all preconfigured NEs that you want to modify, right-click on the NE
Preconfiguration and choose No from the shortcut menu.
4 Click Apply. A progress bar is displayed.
5 A message is displayed indicating that the operation is successful. Click Close.
6 A dialog box is displayed asking you whether to download the NEs immediately. Click Yes.
7 A message is displayed indicating that the operation may affect services. Click OK.
8 A message is displayed again indicating that the operation may affect services. Click OK. A
progress bar is displayed.
9 After the download is complete, a message is displayed indicating that the operation is
----End

5.10.8 Modifying the NM Name

You can modify the NM name as required. This operation does not affect the running of the
U2000.
Prerequisite
Procedure
1 Right-click the NM icon on the Main Topology and choose Object Attributes from the shortcut
menu.
2 In the NMS Attributes dialog box, enter a new NM name. Click OK.
NOTE
The name of the NM can contain letters, symbols, and numbers.
----End
5.10.9 Modifying Fiber/Cable Information

You can modify the name, attenuation, length, and type of a fiber/cable according to its
connection status and physical features.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
2 Modify the name of a fiber/cable.
1. In the Name column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box displayed, enter a proper name for the fiber/cable
and click OK. Click Close in the Operation Result dialog box.
3 Modify the length of a fiber/cable.
1. In the Length (km) column, right-click the value for a fiber/cable and choose Modify
Fiber/Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box displayed, enter the actual length for the fiber/cable
and click OK. Click Close in the Operation Result dialog box.
4 Modify the attenuation of a fiber/cable.

1. In the Attenuation column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box, enter the actual attenuation and click OK. Click
Close in the Operation Result dialog box.
5 Modify the medium type of the fiber/cable.
1. In the Medium Type column, right-click the value for a fiber/cable and choose Modify
Fiber/Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box displayed, select the actual medium type of the fiber/
cable from the drop-down list and click OK. Click Close in the Operation Result dialog
box.
----End
5.10.10 Naming a Fiber/Cable

In the network management, you need to strictly plan the fiber/cable names, to ensure that faults
can be located quickly during maintenance and troubleshooting. On the U2000, you can use the
pre-defined naming rules to name the fibers/cables.
Prerequisite
Procedure
window.
2 Right-click a fiber/cable and choose Name by Rule from the shortcut menu.
The value in the Name field automatically changes according to the configured naming rule.
----End
5.10.11 Copying Topology Objects

In the current topology view, you can copy a topology object from one subnet to another.
Prerequisite
You must be an NM user with the "Topo Operator" authority or higher.
Context
l You cannot paste the same NE or subnet to the destination subnet.
l You can press and hold Ctrl to select two or more objects. You can copy and paste multiple
objects at a time.

Procedure
1 In the topology view, go to the source subnet of the object that you want to copy. Click the
object.
2 Choose Edit > Copy to copy the object to the clipboard.
3 Go to the destination subnet, choose Edit > Paste to paste the object in the subnet.
----End
5.10.12 Moving Topology Objects

In the current topology view, you can move a topology object from one subnet to another.
Prerequisite
Context
l When you cut and paste an object, the object is copied to the destination subnet and deleted
from the source subnet.
l You cannot paste the same device or subnet to the destination subnet.
Procedure
1 In the topology view, go to the source subnet of the object that you want to move. Click the
object.
2 Choose Edit > Cut to copy the object to the clipboard.
3 Go to the destination subnet, choose Edit > Paste to paste the object in the subnet.
----End
5.11 Setting the NE Maintenance Information

NE maintenance information includes the NE location information and maintenance personnel
information. If a fault occurs on an NE, you can refer to the NE maintenance information to
contact the maintenance personnel in time for handling the fault.
Procedure
1 Choose Administration > NMS Security > NE Maintenance Information from the main
menu.
2 In the NE Maintenance Info window, click Display.

3 In the NE Maintenance Info dialog box, set the following information:

l To set the location information, do as follows:
In the Location Info group box, set the NE location information.
l To set the maintenance personnel information, do as follows:
In the Maintenance Personnel Information group box, click Personnel Info. In the
displayed NE Personnel Info dialog box, set Maintainer, Company, Phone, Email.
4 Click Apply.
----End
5.12 Setting the Maintenance Personnel Information

You can manage the maintenance personnel information in a centralized manner, including
adding, modifying, and deleting the maintenance personnel information.
Context
You are not recommended to name a maintenance personnel All.
Procedure
1 Choose Administration > NMS Security > Maintenance Personnel Information from the
main menu.

2 In the Maintenance Personnel Information dialog box, set the maintenance personnel
information.
Set the maintenance Operations

personnel information
Add the maintenance Click Add. Set the parameters in the parameter setting area
personnel information at the bottom of the dialog box. Click OK. The new
maintenance personnel information is displayed in the
information list.
Modify the maintenance In the maintenance personnel information list, double-click

personnel information the information to be modified. Then modify the associated
parameters in the parameter setting area at the bottom of the
dialog box. Click Apply. The modification takes effect, and
the information list is updated.
Delete the maintenance In the maintenance personnel information list, select the
personnel information information to be deleted, and then click Delete. In the
displayed confirmation dialog box, click Yes.
----End
5.13 Deleting Topology Objects

When adjusting the network topology, generally, you need to delete some objects of the topology.
5.13.1 Deleting a Topology Subnet

When adjusting the topological structure of the network, you can delete a subnet from the Main
Topology if the subnet is not needed.
5.13.2 Deleting Boards
To modify the network configuration or the NE configuration, you may need to delete the boards
from the NE Panel.

5.13.3 Deleting Sub-boards

Before adding a new sub-board, you need to delete the sub-boards that are already added.
5.13.4 Deleting Connections
When adjusting the network if you need to delete the NEs or change the connections between
NEs, you need to delete the connections between the NEs or between the NMS and the NE.
5.13.5 Deleting NEs
If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes
all information of the NE from the U2000 but does not affect the running of the equipment.
5.13.6 Deleting an Optical NE
You can delete an optical NE.
5.13.1 Deleting a Topology Subnet

When adjusting the topological structure of the network, you can delete a subnet from the Main
Topology if the subnet is not needed.
Prerequisite
Context
After a subnet is deleted, the topological objects in the original subnet are moved to the upper-
level subnet that the original subnet belongs to.
Procedure
1 Right-click the subnet on the Main Topology, and choose the Delete shortcut menu.
2 Click Yes to delete the subnet in the Confirm dialog box.
3 Click Close in the Delete Object Results dialog box.
----End
5.13.2 Deleting Boards

To modify the network configuration or the NE configuration, you may need to delete the boards
from the NE Panel.
Prerequisite
l This operation is not applicable to access NEs MA5620E and MA5626E, control boards
and upstream boards of other access NEs, routers, switches, and security NEs.
l The services and protection groups of the boards must be deleted.
Procedure
1 Double-click the icon of the NE to open the NE Panel.
2 Right-click the board that you want to delete and choose Delete from the shortcut menu.

NOTE
When you delete the board, the inactive single-station optical cross-connections are also deleted.
3 Click OK in the Delete Board dialog box.

4 Click OK to delete the board.
----End
5.13.3 Deleting Sub-boards

Before adding a new sub-board, you need to delete the sub-boards that are already added.
Prerequisite
l Before deleting the sub-board, delete fibers/cables connected to the sub-board, and make
sure that the sub-board is in the idle state.
l Applies to only the MP1 board and the CXP board.
Procedure
1 Double-click an NE on the Main Topology and the NE Panel is displayed in the user interface.
2 Select the sub-board to be deleted, right-click and choose Delete from the shortcut menu. A
dialog box is displayed. Click OK.
----End
5.13.4 Deleting Connections

When adjusting the network if you need to delete the NEs or change the connections between
NEs, you need to delete the connections between the NEs or between the NMS and the NE.
Prerequisite
Procedure
l Delete the fibers/cables between NEs.
2. Select the fiber/cable you want to delete, right-click and choose Delete Fiber/Cable
from the shortcut menu. The Warning dialog box is displayed. Click OK to delete
the fiber/cable.
CAUTION
The deletion of the fiber/cable will delete the related protection subnets, trails and
user-defined information. Exercise caution before you delete the fiber/cable. You can
export the script of the entire network first to avoid deletion by mistake.


l Delete the links between NEs.
1. Choose Inventory > Link Management from the main menu.
2. Select the link you want to delete, right-click and choose Delete from the shortcut
menu. The Confirm dialog box is displayed. Click Yes to delete the link.
l Delete the connections between the NMS and NEs.
1. In the Main Topology, right-click the connection to be deleted and choose Delete from
the shortcut menu.
NOTE
The Ethernet Line or Serial Port Line connections are set up between the NMS and NEs.
2. The Confirm dialog box is displayed. Click Yes to delete the connection.
3. The Deletion Result dialog box is displayed indicating the deletion result. Click
Close.
----End
5.13.5 Deleting NEs

If you have created a wrong NE, you can delete the NE from the U2000. Deleting an NE removes
all information of the NE from the U2000 but does not affect the running of the equipment.
Prerequisite
You must be an NM user with "NM operator" authority or higher.
Context
When the NE is not logged in, you can delete the NE on the U2000.
In the case of switch and router NEs, the function of deleting an NE uses the license for dedicated
upgrade items or the license for NE resources. If the sum of the returned license and the remaining
license exceeds the limit in the license for dedicated upgrade items or the license for NE
resources, a message is displayed indicating that NE deletion fails. It is recommended that you
apply for a new license for NE resources.
CAUTION
If an NE is deleted, the links related to the NE are also deleted.
Procedure
l Delete a single NE.
1. Right-click the NE on the Main Topology and choose Delete from the shortcut menu.
2. The Confirm dialog box is displayed, click Yes.
3. In the operation result dialog box, click Close.
l Delete NEs in batches.


menu.
2. In the left-hand pane, select multiple NEs and click . The Configuration Data
Management List pane displays the configuration data of all the selected NEs.
3. Select the NEs to be deleted, right-click and choose Delete from the shortcut menu.
The Delete the NE dialog box is displayed.
4. Click OK.
5. In the Operation Result dialog box, click Close.
----End
5.13.6 Deleting an Optical NE

You can delete an optical NE.
Prerequisite
l Applies to the WDM equipment.
Procedure
1 Right-click an optical NE on the Main Topology and choose Delete > Delete NE from the
shortcut menu.
2 The Confirm dialog box is displayed, click Yes.
3 The Delete Object Results dialog box is displayed, click Close.
NOTE
Except the OptiX OSN 6800, OptiX OSN 8800 T32, OptiX OSN 8800 T64, all the other NEs that are
associated to this optical NE are moved to an idle optical NE. After the optical NE is deleted, the OptiX
OSN 6800, OptiX OSN 8800 T32, OptiX OSN 8800 T64 are divided to the Main Topology.
----End

Operation Guide for Common Features 6 Time Localization Management
6 Time Localization Management
About This Chapter
In a network that covers one or more time zones, you can configure time localization by using
the U2000 and on NEs for easier network maintenance.
6.1 Time Localization

Time localization ensures that the time on the U2000 is correctly displayed when the U2000
crosses time zones and Daylight Saving Time (DST).
6.2 Setting Time Localization on the U2000
By setting time localization, you can set the time localization mode by using the U2000. This
ensures that the NE data that is displayed is based on the standard time on the U2000.
6.3 Setting Time Localization on NEs
You can set time localization on NEs to ensure the consistent time displayed on NEs and the
U2000.

6 Time Localization Management Operation Guide for Common Features
6.1 Time Localization

Time localization ensures that the time on the U2000 is correctly displayed when the U2000
crosses time zones and Daylight Saving Time (DST).
UTC and Time Localization

Universal Time Coordinated (UTC) was formerly called the Greenwich Mean Time (GMT).
The UTC is an absolute time and is used in most communications standards.
All data in the U2000 and NEs are stored based on the UTC. The time on the U2000 client is
displayed in twe modes, which are by client local time and by server local time. The local time
displayed on the U2000 client varies with the different time display modes.
Time Zone
Time zone: The world is split into 24 time zones, each of which spans 15 longitudinal bands.
The time offset between adjacent time zones is one hour.
If the preset time zone of the system is incorrect, the backup operation timed at 04:00 am (the
time when the traffic on the network is small) may be performed in the daytime (the time when
the traffic on the network is heavy). As a result, the CPU is overloaded, and it is also difficult
to locate problems. Therefore, we need to use the time zone of the device location as the time
zone of the system.
Daylight Saving Time

The daylight saving time (DST) is ahead of or behind the standard time. If the country or the
region of the carrier uses the DST, synchronize the system time with the DST, and adjust, based
on the DST, the time-sensitive services to ensure that time information of the accounting, the
billing, the alarm, and the log records is correct.
The time when data is generated in the U2000, is irrelevant to DST. But, when the U2000 transits
the display of history data, the U2000 may need to implement DST transition for some regions.
For example, the U2000 generated a time stamp "A" for an operation in June. The time stamp
"A" is held in the UTC format. Consider that the time zone observes DST and in June the time
stamp "A" is adjusted according to DST. When DST ends in October, the time stamp "A" cannot
be transited by simply adding or subtracting the time zone, without considering the DST.
6.2 Setting Time Localization on the U2000

By setting time localization, you can set the time localization mode by using the U2000. This
ensures that the NE data that is displayed is based on the standard time on the U2000.
1. 6.2.1 Setting the Time Display Format

The U2000 provides different time display formats to meet the requirements of users in
different areas.
2. 6.2.2 Setting the Time Mode of the Client
This topic describes how to set the time mode of the client to determine whether the time
is displayed according to the U2000 server time or the NE time.

6.2.1 Setting the Time Display Format

The U2000 provides different time display formats to meet the requirements of users in different
areas.
Context
l After setting the time format, you need to log in to the server again to make the settings
take effect.
l When you log in to the client next time, the U2000 client automatically uses your last
settings.
l The new time display format is listed in the Appearance Example area.
Procedure
1 Choose File > Preferences from the main menu. Click the Region Settings > Time tab.
2 Set the time display format in the Time Settings area according to the instructions displayed in
the Time Format Notation area. Then, select the required record from the Time Format drop-
down list. You can set the time format to determine whether the time zone and DST flag.
NOTE
If the Time Format is hh:mm:ss tt, you can setting the Time Indicator.
3 Select the required record from the Time Format drop-down list.
4 After you set the time format, click Apply.
5 Click OK.
----End
6.2.2 Setting the Time Mode of the Client

Context
The settings take effect after you log in to the client again.
l After you set the time mode, you need to restart the U2000 client for the settings to take
effect.
Procedure
2 In the navigation tree on the left of the Preferences window, select Time Mode.

3 In the Time Mode group box, select Time Mode.

NOTE
l Server time mode: If you select this mode, the alarms are queried according to the server time.
l Client time mode: If you select this mode, the alarms are queried according to the client time. You are
advised to retain the default value Client time mode.
4 Click OK.
----End
6.3 Setting Time Localization on NEs

You can set time localization on NEs to ensure the consistent time displayed on NEs and the
U2000.
NOTE
The security NE does not support time localization.
1. 6.3.1 Setting a Time Zone for an NE

You can set the time zone where an NE is located.
2. 6.3.2 Setting DST on NEs
Different regions have a different DST. You need to set the DST to ensure that the display
time for history data in the U2000 can be correctly transited.
6.3.1 Setting a Time Zone for an NE

You can set the time zone where an NE is located.
Prerequisite
For MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs and Router series, Switch series,
Security series NEs, the time zone of the U2000 are automatically synchronized with those on
the NE, though you do not change them by using the U2000. Meanwhile, the NE reports an event
indicating that the time zone are changed at the NE side.
Procedure
1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the main menu.

NOTE
For Router series, Switch series, Security series, Access series NEs, on the Main Topology, right-click the
NE whose attributes you want to view, and choose Object Attributes . In the dialog box that is displayed,
click the Time Zone and DST tab.
3 Click Query to query the time zone for an NE.
4 Select a time zone from the TimeZone.
5 Click Apply.
----End
6.3.2 Setting DST on NEs

Different regions have a different DST. You need to set the DST to ensure that the display time
for history data in the U2000 can be correctly transited.
Prerequisite
For MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs and Router series, Switch series,
Security series NEs, the DST rule of the U2000 are automatically synchronized with those on
the NE, though you do not change them by using the U2000. Meanwhile, the NE reports an event
indicating that the DST rule is changed at the NE side.
After you set the DST time for an NE, a time gap is generated between the non-DST time and
DST time. An error message is displayed if you configure data on the U2000 for this time gap.
Procedure
1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
from the main menu.

NOTE
For Router series, Switch series, Security series, Access series NEs, on the Main Topology, right-click the
NE whose attributes you want to view, and choose Object Attributes . In the dialog box that is displayed,
click the Time Zone and DST tab.
3 Click Query to query the time zone for an NE.
4 Select DST.
5 Set the DST attributes.
6 Click Apply. A prompt appears telling you that the operation was successful. Click Close.
----End

Operation Guide for Common Features 7 Alarm Management
7 Alarm Management
About This Chapter
Alarms are the important information for learning the running status of the equipment and
locating faults. Therefore, the alarms need to be obtained and managed effectively. To ensure
the normal running of the network, the network management and maintenance staff should
monitor and process the alarms periodically.
7.1 Basic Concepts

Alarm is the primary information source for you to learn the network running status and to locate
faults. Hence, you need to familiarize yourself with the basic concepts and related operations of
the alarm management so that you can effectively obtain and manage the alarms.
7.2 Setting Trap Parameters on the NE
A trap receiver receives trap messages of the NE. This describes how to set trap parameters on
the NE. The NE actively sends fault information to the U2000 through trap packets defined by
SNMP. After the trap function is configured, the NE can actively send fault information.
7.3 Setting Automatic Alarm Reporting
If you set alarms on an NE to be automatically reported, once the alarm is raised on the NE, it
is automatically reported to the U2000. You can disable the automatic reporting for unimportant
alarms to reduce the impact on the U2000 performance. A large volume of alarm information
affects the performance of the U2000.
7.4 Customizing Alarm Template
The U2000 provides the customized alarm browsing template and alarm attributes template.
You can quickly set the alarm browsing filtering criteria and the alarm attributes, by using the
preset customized alarm template.
7.5 Synchronizing Alarms
You can synchronize the current alarms of the NE and the U2000. This feature ensures that the
alarms on the NEs are synchronous with the alarms on the U2000, and that the current NM
alarms are synchronous with the alarms in the U2000 alarm database.
7.6 Monitoring Network Alarms
The network maintenance engineer can monitor network alarms to learn about the running status
of the network in time. The U2000 provides multiple alarm browsing methods through which
you can view alarms on different objects.

7 Alarm Management Operation Guide for Common Features
7.7 Managing the Alarm Maintenance Status

This topic describes how to manage the maintenance status of the alarms that are generated in
scenarios where alarm tests are performed on the NMS or NEs. You can configure the status of
these alarms as in maintenance. As a result, when the NMS receives such alarms, it marks them
as being maintained, thus giving prominence to these alarms. This function is applicable to router
series NEs and switch series NEs.
7.8 Collecting Statistics on Alarms/Events
By collecting statistics on alarms/events through templates or statistical conditions, you can
know the fault status of the network and obtain associated data. This helps you to rectify the
fault and optimize the network.
7.9 Handling Alarms
After you receive an alarm, you need to handle it. The procedure for handling an alarm include
viewing the alarm details, acknowledging the alarm, identifying the alarm, and clearing the
alarm.
7.10 Setting the Alarm Auto Processing
You can set an auto processing policy to enable the U2000 to process the alarms that match the
preset conditions. This helps to improve the work efficiency.
7.11 Setting Audible and Visual Alarm Notification
The U2000 can select different sounds and colors for the alarms and abnormal events of different
severities based on customized settings, to facilitate maintenance.
7.12 Setting Remote Alarm/Event Notification
Alarms/events that meet the remote notification rules are notified to maintenance engineers after
you set the remote notification rules including the notification conditions, notification time, and
notification methods. This helps maintenance engineers who are not on site to know the alarm/
event information on the U2000 server and take proper measures. On the U2000, you can set
the formats of emails and short messages, delay the sending of remote notification messages,
disable remote notification sending for alarms cleared in the specified time period. In addition,
you can control the traffic of emails and short messages. If the traffic reaches the specified value,
new emails and short messages are discarded, that is, remote notification message are not sent.
7.13 Modifying Alarm Severity
You can adjust the alarm severity of each NM alarm, NE alarm and board alarm. This facilitates
management and improves the efficiency of alarm monitoring.
7.14 Analyzing Alarm Correlation
Certain alarms or events that NEs report are correlated. This topic describes how to set alarm
correlation rules so that the U2000 can handle alarms or events automatically according to the
preset operations, and thus improving the alarm or event handling efficiency.
7.15 Managing Alarm/Event Data
You need to clean up alarm/event data in the database in time, thereby preventing insufficiency
of database space. The U2000 supports periodical dump, overflow dump, and manual dump of
alarms/events. Dumped alarms/events are deleted from the database.
7.16 Alarm Management (MSTP&WDM&RTN NE)
To ensure the normal running of the network, the network management and maintenance staff
should periodically check and monitor the network by taking appropriate alarm management
measures.

7.1 Basic Concepts

Alarm is the primary information source for you to learn the network running status and to locate
faults. Hence, you need to familiarize yourself with the basic concepts and related operations of
the alarm management so that you can effectively obtain and manage the alarms.
7.1.1 Alarms and Events

This topic describes the similarities and differences between an alarm and an event on the
U2000.
7.1.2 Alarm Reporting Process
The alarm reporting process starts with the detection of the alarm on a board, and ends with the
U2000 notifying the alarm to a user. The alarm reporting process is instructive in guiding a user
to handle alarms.
7.1.3 Alarm Handling Procedure
This topic describes the alarm handling procedure. After the U2000 detects an alarm, you are
recommended to handle the alarm according to the following procedure.
7.1.4 Alarm Template
An alarm template simplifies the operations of setting alarms. By using the alarm template, you
can quickly set alarm browsing and alarm attributes..
7.1.5 Alarm Viewing Operations
By viewing the alarms, the network maintainer can know the running status of the network in
time. You can view the current or history alarms of the U2000, network equipment, trails and
services. Meanwhile, you can synchronize, check and acknowledge these alarms.
7.1.6 Alarm Setting Operations
Alarm setting operations include a series of alarm management operations, such as setting the
alarm suppression. You can set the alarm attributes as required in favor of the alarm management.
7.1.7 Alarm Correlation Analysis
The root alarms always generate some alarms of lower severity levels in the network. This brings
confusions when you need to locate and handle alarms. Through alarm correlation analysis, you
can effectively suppress correlative alarms, reduce the alarm count, and quickly locate faults.
The alarm correlation includes the NE alarm correlation and the U2000 alarm correlation.
7.1.8 Alarm Notification
To get informed of the alarm information is critical to handling alarms and to the network
maintenance. The U2000 provides various ways of notifying alarms.
7.1.9 Alarm Severity
Alarm severity is used to identify the severity level, significance and urgency of an alarm.
7.1.10 Alarm States
Alarm states are defined based on alarm acknowledgement and clearance. You can take
corresponding processing measures based on alarm states.
7.1.11 Alarm Category
The alarms can be categorized according to the generating location and the U2000 standards
and functions.
7.1.12 Current Alarms and History Alarms
Current alarms and history alarms have the following four types: current NE alarms, history NE
alarms, current U2000 alarms and history U2000 alarms.

7.1.13 Alarm Statistics

The function of performing statistics on alarm logs allows you to set filter conditions to statistics,
save a statistics condition as a template, save statistics on a local computer, and print statistics.
7.1.14 Alarm Dumping
When the history alarm data in the U2000 database exceeds a certain amount, the U2000
operations will be affected, or even worse, the entire system could be down. The alarm dumping
function is used to save the history alarm data in the U2000 database to a specified directory as
a file. In this way, the U2000 performance is improved.
7.1.1 Alarms and Events

This topic describes the similarities and differences between an alarm and an event on the
U2000.
Similarities
On the U2000, an alarm or event is raised when the U2000 detects a state change of a managed
object.
Differences
An alarm is raised when the system detects a fault.
An event is raised when the state of a managed object changes.
The differences between an alarm and an event are described as follows:
l An alarm is a special type of event. An alarm indicates that a fault occurs on the U2000 or
a managed object. The fault must be rectified in time. Otherwise, the U2000 services cannot
run properly because the fault affects the functions of the U2000 or its devices.
l An event indicates that the state of a managed object changes. The change may not affect
the U2000 services.

to handle alarms.
Alarm reporting flow chart

l For Router series, Switch series, Security series, Access series NEs, Figure 7-1 shows the
activities performed to report an alarm.
l For MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, Figure 7-2 shows the

Figure 7-1 Alarm reporting flow chart 1

Alarm Monitoring by Board

When monitoring an alarm, the board immediately reports the alarm to the SCC continuously.
If the alarm database of the SCC does not have this alarm, the alarm data is saved into the database
and a notification is reported. Otherwise, the alarm data is discarded directly.

Automatic Alarm Reporting

When the SCC receives a new alarm notification, it determines whether to report the alarm to
the U2000 according to the settings of the alarm automatic reporting. After the U2000 receives
an alarm notification, it responds to the SCC a confirm message. If the SCC does not receive
any confirm message within a time period, it reports the alarm to the U2000 again. This scheme
ensures the reliability of the alarm reporting.
If the communication between the U2000 and the NE is interrupted, when the U2000 is restarted,
it automatically synchronizes the alarm library of the SCC to keep the alarm data on the
U2000 synchronous with the alarm data on NE.
U2000 Alarm Notification

Based on the user-defined alarm filter criteria, the U2000 decides whether to discard the alarm
reported from an NE. As for the alarms saved in the U2000 database, the U2000 analyzes them
according to the alarm correlation rules. Then it presents the analysis result on the U2000 client
and notifies the information to the user.

Procedure Chart
Figure 7-3 shows the alarm handling procedure.

Figure 7-3 Procedure for handling an alarm
Procedure Description
Figure 7-3 lists the procedure for handling an alarm.

Table 7-1 Procedure for handling an alarm

Step Operation Description
1 Receive an alarm Follow the alarm handling procedure after you receive an
alarm. To ensure that you are notified in time after an alarm
occurs, you need to set alarm notification methods on the
U2000.
2 View the alarm details View the alarm details, including the alarm location, alarm
help, and alarm maintenance experience after an alarm
occurs.
3 Acknowledge the Acknowledge the alarm to avoid others from handling the
alarm same alarm. After you acknowledge the alarm, it indicates
that the alarm has been handled.
4 Collect the fault Identify the alarm and query the alarm information to find
information out the symptom of the alarm.
5 Analyze the causes of Analyze the causes for the alarm based on the alarm
the alarm symptom.
6 Work out the fault Work out the fault handling scheme according to the alarm
handling scheme details, device manuals, network status, and maintenance
experience.
7 Carry out the fault Carry out the fault handling scheme to rectify the fault that
handling scheme leads to the alarm.
8 Clear the alarm Clear the conditions that cause the alarm. After the alarm is
cleared, the U2000 receives a clearance alarm.
9 Check whether the Check the handling results after you rectify the fault.
fault is rectified
10 Record the Record the maintenance experience when the alarm

maintenance handling is complete.
experience
7.1.4 Alarm Template

An alarm template simplifies the operations of setting alarms. By using the alarm template, you
can quickly set alarm browsing and alarm attributes..
Alarm template consist of the alarm browsing template and the alarm attribute template.

Table 7-2 Alarm Template Type
Type Description
Alarm browsing templates l Alarm browsing templates can be divided

into the current alarm template, history
alarm template, alarm logs template, and
alarm logs statistics template.
l An alarm browsing template is a
combination of filter conditions that are
used to browse alarm information or alarm
statistics.
l Certain common filter conditions used to
browse alarm information and statistics
are specified in a template. As a result, you
do not need to reset the filter conditions
when browsing alarm information or
alarm statistics.
Alarm attribute template l An alarm attribute template specifies the

alarm severity, automatic alarm report,
and alarm mask of NE alarms.
l You can use the default alarm attribute
template or customize an alarm attribute
template according to a particular alarm
monitoring policy.
l By applying an alarm attribute template to
a specified NE, you can set attributes of
alarms in a simple manner.
NOTE
An alarm template is applicable to the MSTP,
WDM, NA WDM, RTN, PTN, Marine series
NEs and CX NEs.
7.1.5 Alarm Viewing Operations

By viewing the alarms, the network maintainer can know the running status of the network in
time. You can view the current or history alarms of the U2000, network equipment, trails and
services. Meanwhile, you can synchronize, check and acknowledge these alarms.
Table 7-3 lists the impacts of the alarm operations on NEs.
Table 7-3 Impacts of alarm viewing operations on NEs
Operation Affect NE or Not
Alarm Viewing No
Alarm Acknowledgement No
Alarm Synchronization No

Operation Affect NE or Not
Alarm Check No
Alarm Refreshing No
Alarm Clear Yes
Alarm Filtering No
Alarm Memo No
Alarm Viewing
You can view the alarms of the equipment and services on the U2000 to learn the running status
of the network or the equipment.
l Viewing current alarms: You can view the networkwide current alarms of all the severity
levels.
l Viewing all current alarms of a specified severity level: By clicking the alarm icon on the
toolbar, you can conveniently view the networkwide critical, major or minor alarms.
l Viewing alarms of a specified NE or U2000: You can select an NE or a U2000 on the Main
Topology to view the current alarms of the selected object.
l Viewing history alarms: By viewing all the history alarms recorded in the U2000, you can
know the faults that once occurred on the NEs and on the U2000. This helps in the long-
term performance analysis.
Alarm Acknowledgement
An acknowledged alarm indicates that this alarm has been handled by a user. An alarm can be
acknowledged in the following two ways:
l Manual acknowledgement: You can select an alarm from the current alarm browsing
window to acknowledge it.
l Automatic acknowledgement: If you enable the automatic alarm acknowledgement, the
U2000 acknowledges an alarm after it is cleared or automatically acknowledges the alarms
that are cleared within specified time at 01:00 every day.
Alarm Synchronization
When the communication between the U2000 and equipment is interrupted and then restored,
or when the U2000 is restarted, you need to synchronize the alarm information to keep the
consistency of the alarm data. To synchronize the alarms, the U2000 compares the alarms in the
U2000 with the alarms in the NE. If the alarm data is inconsistent, the U2000 uploads the NE
alarm data to the U2000 database and overwrites the original information. The alarm
synchronization can be performed in the following two ways:
l Manual synchronization: You can specify an alarm in the current alarm browsing window
and synchronize it.

l Automatic synchronization: You can specify the trigger conditions for the automatic alarm
synchronization, such as when the U2000 starts, when the communication is restored from
an interruption, or when an LCT user logs out.
Alarm Check
The alarm check function is used to compare one or more uncleared alarms on the U2000 with
those on the NE. If the alarm exists as a current alarm in the NE, it means that the alarm
information remains unchanged on the U2000. If the alarm does not exist in the NE, the alarm
is cleared on the U2000.
Alarm Refreshing
When you refresh the alarms, the latest alarm information is obtained from the alarm database
of the U2000 and displayed on the U2000 client.
Alarm Clear
When you delete an alarm, the alarm is cleared from the NE and the current alarm library of the
U2000. After that, the alarm is moved to the history alarm library.
NOTE
The NA NEs do not support the function of alarm clear.
Alarm Filtering
By setting the filter criteria, you can filter out the unconcerned alarms in the alarm browsing
window. The filter criteria include:
l Alarm Name
l Severity
l Status
l Type
l Last Occurrence Time Range
l Clearance Time Range
l Duration
l Memo
l Alarm Source
Alarm Memo
You can add remarks for the handled alarms. This is useful when you manage a large number
of alarms.
7.1.6 Alarm Setting Operations

Alarm setting operations include a series of alarm management operations, such as setting the
alarm suppression. You can set the alarm attributes as required in favor of the alarm management.
Table 7-4 lists the impacts of alarm setting operations on NEs and services.

Table 7-4 Impacts of alarm setting operations on NEs and services

Operation Affect NE or Not Affect Service or Not
Setting the Alarm Suppression Yes No
Setting the Automatic Alarm Yes No

Reporting
Applies to theMSTP, WDM, NA
WDM, RTN, PTN, Marine series
NEs.
Setting the Alarm Hold-Off Yes No

NEs.
Setting the Alarm Saving Mode Yes No

NEs.
Setting the Alarm Reversion Yes No

Applies to the MSTP, WDM,
RTN, submarine NEs.
Setting the Bit Error Alarm Yes No

Threshold
NEs.
Setting the AIS Insertion Yes Yes

Applies to the MSTP, WDM, NA
NEs.
Setting the UNEQ Insertion Yes Yes

WDM, RTN, submarine NEs.
Setting the Alarm Insertion Yes Yes

WDM, submarine NEs.
Setting the Alarm Severity Yes No
Setting the NE Alarm Masking No No
Setting Automatic Alarm No No

Acknowledgment
Setting Automatic Alarm No No

Synchronization

Operation Affect NE or Not Affect Service or Not
Setting the Alarm Correlation No No

Rule
Setting Alarm Attributes No No

NEs.
Table 7-5 lists the impacts of alarm setting operations on alarms. You can refer to Alarm
Reporting Process.
Table 7-5 Impacts of alarm setting operations on alarms

Operation Impact
Setting the Alarm Suppression l After an alarm is suppressed, the

responsible NE or the board stops
reporting the alarm.
l After an alarm is suppressed, the alarm
that has been reported is cleared.
Setting the Automatic Alarm Reporting l If an alarm is set to not automatically

Applies to theMSTP, WDM, NA WDM, reported, the alarm data is retained in the
RTN, PTN, Marine series NEs. NE but not reported to the U2000.
l If an alarm is set to not automatically
reported, you can still obtain the alarm
information by synchronizing the alarm.
Setting the Alarm Reversion l When you set the alarm reversion for a
Applies to the MSTP, WDM, RTN, port, the alarm status on this port is
submarine NEs. opposite to the actual situation. That is,
alarms are not reported even if they exist.
l When you set the alarm reversion for a
port, the alarm status of the board does not
change, and the alarm indicator still
indicates the actual running status of the
equipment.
Setting the NE Alarm Masking l After an alarm is masked, it is not

displayed on the U2000.
l After an alarm is masked, it is not stored
on the U2000.

Setting the Alarm Suppression

You can suppress some alarms of the specified NE so that the U2000 does not monitor these
alarms. In this way, you can focus on important alarms. If you suppress a certain alarm of a
specified NE, the alarm is not reported.
Setting the Automatic Alarm Reporting

If the automatic alarm reporting is enabled, the alarm is immediately reported to the U2000 as
long as the alarm is raised from the equipment. When the alarm is reported, the alarm indicator
on the U2000 flashes and displays the number of alarms that are not cleared currently. For some
unnecessary alarms, you can set them to not automatically reported. In this way, the impacts that
may be imposed on the U2000 by a large number of alarms are reduced.
Setting the Alarm Hold-Off

If you set the alarm hold-off for an NE, the NE does not immediately report the alarm it detected.
Instead, the NE keeps monitoring the alarm for a period of time. If the alarm persists during the
period, the NE reports the alarm. The same reporting scheme applies to the reporting of the
clearance status of the alarm.
A reasonable alarm hold-off time effectively prevents the transient reporting and mis-reporting
of the alarms, and thus reduces the impact on the U2000 performance.
Setting the Alarm Saving Mode

The alarm saving mode refers to the mode in which an NE register saves alarms. There are two
modes of alarm saving, Wrap and Stop.
l Wrap: When the NE alarm register is full, the register discards the earliest alarms to save
the latest alarm information when new alarms are raised. This is the default mode, which
is also the most used one.
l Stop: When the NE alarm register is full, it does not accept any new alarms so that you
cannot be informed of the new alarms. Hence, usually this mode is not used.
Setting the Alarm Reversion

During a new deployment, certain alarms that are reasonable but meaningless occur. For
example, when you configure a tributary board, line board, or Ethernet board for a service but
not connect cables, the corresponding LOS alarm is generated. After the alarm reversion is set,
the alarm is not displayed. This does not affect the network monitoring that is performed by
maintainers.
The alarm reversion has three modes: non-revertive, automatic reversion and manual reversion.
Table 7-6 shows respective ways of handling alarms in the three modes.

Table 7-6 Alarm reversion handling mode

Reversion Mode Handling
Non-revertive This is the normal alarm monitoring status, which is also the default
setting. If the Reversion Mode of the NE alarm is set to Non-
Revertive, the system returns an failure prompt when you attempt to
enable the alarm reversion for a port. This is because the alarm
reversion of a port cannot be enabled in the Non-Revertive mode.
Automatic reversion When the Reversion Status of a port is set to Enabled,

l If there is no actual alarm at the port, the setting fails.
l If an actual alarm exists at the port, the setting successfully takes
effect as the port becomes in the revertive mode. When the alarm
is cleared, the alarm reversion at the port is automatically stopped.
In the automatic reversion mode, the alarm reversion status of a
port automatically changes. This may be different from the alarm
reversion status of the U2000.
When the Reversion Status of a port is set to Disabled, the status of
the alarm reported from the port is kept consistent with the actual
alarm status regardless of the actual alarm status at the port.
Manual reversion When the Reversion Status of a port is set to Enabled, the status of
the alarms reported from the port immediately changes to the opposite
of the actual alarms regardless of the actual alarm status at the port.
To be specific, when there is an actual alarm, the alarm is not reported.
When there is not an actual alarm, the alarm is reported.
When the Reversion Status of a port is set to Disabled, the status of
the alarms reported from the port is kept consistent with the actual
alarm status regardless of the actual alarm status at the port.
NOTE
l The alarm reversion is configured based on individual ports.

l When you set the alarm reversion for a port, the alarm status of the board does not change, and the
alarm indicator still indicates the actual running status of the equipment.
l You can obtain the actual alarm status by querying the alarm from the related board.
Setting the Bit Error Alarm Threshold

The NE reports a bit error alarm when the amount of the bit error reaches a certain value. This
value is known as the bit error threshold. The bit error alarm threshold can be divided into the
threshold-crossing threshold and the degrade threshold.
l When the bit error rate (BER) exceeds the degrade threshold, it indicates the signal is
already degraded. In this case, the NE reports the SD alarm.
l When the BER exceeds the threshold-crossing threshold, it indicates that the errored bits
are too much. In this case, the NE reports the excessive error (EXC) alarm.
Setting the AIS Insertion

You can insert an AIS alarm at a port to guarantee the quality of service (QoS) for the services
that requires high QoS. When a specific service-affecting event, such as B3_EXC, is detected,

you can immediately insert an AIS alarm to trigger the related protection scheme so that the
service at the port can be switched to a protection channel that has a better quality.
Inserting the UNEQ Insertion

When you need to interrupt a service that is already in operation, you can insert the Unequipped
(UNEQ) in the NE path and decide whether to monitor the LOS alarm on this path as required.
The UNEQ has the two switches, LOS and Path Not Used.
Setting the Alarm Insertion

The alarm insertion is an action that a user inserts an alarm (such as AIS and RDI) into a port
of a trail for the purpose of commissioning and maintenance. When the alarm is inserted, you
can see whether any alarm is generated at the opposite end (upstream or downstream). In this
way, the connectivity and the correctness of the trail connection can be examined.
Setting the Alarm Severity

Alarms in the U2000 has the following four severity levels: critical, major, minor and warning.
Different alarms have different severities. You can adjust the severity of an alarm according to
the actual situation.
NOTE
For NA NEs, alarms in the U2000 has the following five severity levels: critical, major, minor, not alarmed
and not reported.
Setting the NE Alarm Masking

You can set the masking for the NE alarms of the specified type. The alarms masked are neither
displayed on the U2000, nor saved in the U2000 database.
By default, the alarms of all types are not masked.
Setting Automatic Alarm Acknowledgment

The U2000 can acknowledge the cleared alarms immediately or periodically based on automatic
alarm acknowledgment. Therefore, you need not acknowledge these alarms manually.
Setting Automatic Alarm Synchronization

If automatic alarm synchronization is set, the alarms are synchronized automatically after the
communication between the U2000 and the NE is interrupted and restored, the U2000 is
restarted, or the LCT user exits. Therefore, the alarm consistency between the U2000 and the
NE is ensured.
Setting the Alarm Correlation Rule

After the alarm correlation rule is set and the alarm correlation analysis function is enabled, the
system analyzes the reported alarms according to the correlation rule and displays only the root
alarms. In this manner, you can effectively suppress the correlative alarms and quickly locate
faults.

Setting U2000 Alarm Attributes

Setting the U2000 alarm attributes includes setting the alarm severity and the alarm suppression
for the U2000. This function is particularly for the alarms of the U2000 itself, such as the alarms
about insufficient disk space and the communication interruption between the U2000 and an
NE.

NE Alarm Correlation
The NE alarm correlation rule is the alarm performance monitoring mechanism of the logical
function module of the equipment. The rule is fixed and cannot be manually set. A good
understanding of the mechanism helps you improve the efficiency of analyzing and locating
faults during equipment maintenance.
Root alarm is directly caused by the abnormal events or faults in the network. A root alarm
always generates some other alarms of lower severity level. These alarms derived from the root
alarm are correlative alarms.
For example, if a fiber is cut off, the SPI functional module in the optical board detects the
occurrence of the R_LOS alarm (root alarm). This alarm in turn causes the RST functional
module in the regenerator section (RS) to generate alarms (correlative alarm) such as RLOF,
R_OOF, B1_SD and B1_EXC. To avoid this problem, you can set correlation rules between the
previously mentioned alarms, and enable the alarm correlation suppression. In this way, the NE
reports only the root alarm, R_LOS.
Figure 7-4 shows the alarm flow of each function module of the SDH equipment in detail. In
this flow, you can view the relation between alarm maintenance signals generated by each
function module of the SDH equipment.

Figure 7-4 NE Alarm Correlation
U2000 Alarm Correlation

For the U2000 alarm correlation analysis, you need to set the alarm correlation rule and enable
the alarm correlation analysis to use the alarm correlation analysis function for suppressing
correlative alarms.
CAUTION
l The alarm correlation rule is the basis for the alarm correlation analysis, and is thus closely
related to the analysis result. Be cautious when you set the alarm correlation rule.
l Usually, it is recommended that you use the default alarm correlation analysis rule.
l The alarm correlation suppression is set to disabled by default. To enable the alarm
correlation rules for alarm analysis, you need to manually enable the alarm correlation
suppression.

Example of the Alarm Correlation
NE1, NE2 and NE3 form a non-protection (NP) chain with services running between each two
of them. If the fiber between NE1 and NE2 is broken, NE2 reports the R_LOS alarm. Meanwhile
NE2 and NE3 report a lot of TU_AIS alarms. These TU_AIS alarms are, however, generated
by the R_LOS alarm on NE2. In this case, you can set alarm correlation rules for the R_LOS
alarm of NE2 to suppress the TU_AIS alarms of NE2 and NE3. This reduces the alarm amount
and eases the fault location.
The alarm correlation rule takes effect only in the following cases:
l Alarm 1 and alarm 2 are generated on the same object.

l Alarm 1 is generated at the upstream of alarm 2.
l Alarm 1 is generated at the opposite service end of alarm 2.
The alarm correlation rule realizes the following functions:
l Enable alarm 1 to suppress alarm 2.

l Adjust the severity level of alarm 1 to a higher level.
l Adjust the severity levels of alarm 1 and alarm 2 to higher levels.
The alarm correlation rule can adjust the severity levels of root alarms and correlative alarms to
higher levels on condition that the alarms are generated in compliance with the alarm correlation
rule. For example, the severity level of TU_AIS is major. If you set the TU_AIS as the correlative
alarm of the R_LOS and adjust the severity level of the TU_AIS to a higher level in an alarm
correlation rule, the TU_AIS is adjusted to a critical alarm only when the TU_AIS is generated
by R_LOS. If the TU_AIS is not generated by R_LOS, it is still displayed as a major alarm on
the U2000.
7.1.8 Alarm Notification

To get informed of the alarm information is critical to handling alarms and to the network
maintenance. The U2000 provides various ways of notifying alarms.
Alarm Color
The U2000 uses evident color changes on the GUI to help you quickly locate the alarmed
monitoring point.
l The alarm indicators on the toolbar display the number of all the uncleared and
unacknowledged critical, major, minor and warning alarms networkwide. When a new
alarm is reported, the alarm indicator flashes while the statistics on the indicator change.
You can navigate to the alarm browsing window by clicking the alarm indicator to view
the networkwide alarms of this severity level.
NOTE
For NA NEs, alarms in the U2000 has the following five severity levels: critical, major, minor, not
alarmed and not reported.

l On the main topology, the alarms of Non-NA NEs and subnets are represented by colored
icons. These icons are in different colors to indicate different alarm severities, as shown in
Figure 7-5.
Figure 7-5 Non-NA NEs Alarm status
l On the main topology, the alarms of NA NEs and subnets are represented by colored icons.
These icons are in different colors to indicate different alarm severities, as shown in Figure
7-6.
Figure 7-6 NA NEs Alarm status
l On the main topology, if a fiber is affected by an alarm, the fiber color varies with the alarm
that is currently at the highest severity level on the fiber.
l On the NE Panel, the board color varies with the alarm that is at the highest severity level
on the board.
l On the board view, the color of each channel varies with the alarm that is currently at the
highest severity level on the corresponding channel.
l On the Trail View, the alarmed trails are displayed in different colors.
By default, the U2000 displays different colors for different alarm severities. You can define
different colors for the alarms at different severity levels.
l For Non-NA NEs, the U2000 displays critical alarms in red, major alarms in orange, minor
alarms in yellow, and warning alarms in blue.
l For NA NEs, by default, the U2000 displays critical alarms in red, major alarms in orange,
minor alarms in yellow, and not alarmed alarms in blue.
Alarm Browsing Window

Alarm browsing is the basic alarm function provided for a network manager. The alarm browsing
windows display the alarm information in text. The alarm browsing windows include the
following:
l Browse Current Alarm

l Query Alarm Logs
l Alarm Statistics

In the Browse Current Alarm window, if you select Display latest alarms , the newly reported
alarms are automatically displayed in this window. If this option is not turned on, the Refresh
button flashes when a new alarm is reported. When you click the button, the alarm is immediately
displayed in this window.
Alarm Box
The U2000 client connects to the alarm box device commonly used in Huawei to provide audible
and visual alarms. You can determine the alarm severity according to the indicators and sounds
of the alarm box. When a new alarm is reported, the alarm box instantly beeps and flashes the
alarm indicator of the corresponding severity.
Sound Box
Connected to a sound box, the U2000 client uses different sounds to indicate alarms at different
severity levels. When a new alarm is reported, the sound box immediately beeps. The sound is
muted when the alarm is acknowledged or when the preset duration for the sound to persist
elapses.
The alarm sound is realized at the U2000 client. You can set different sounds for alarms of
different severity levels.
Alarm Remote Notification

With the alarm remote notification, a user absent from the telecommunications room can be
informed of the alarms. Currently the alarm notification is realized in the following two ways:
l Send the alarm information through an email to the email box of the specified user.
l Send the alarm information through the mobile phone short message to the mobile phone
of the specified user.
7.1.9 Alarm Severity

Alarm severity is used to identify the severity level, significance and urgency of an alarm.
The follow table describes the alarms of different severity levels and the corresponding handling
methods.
For Non-NA NEs, alarms come in the following four levels in descending order of severity:
Critical, Major, Minor and Warning.
Alarm severity Definition Handling
Critical Refers to fault alarms and Should be handled

events that may result in immediately. Otherwise, the
breakdown of the NE or the system may break down.
whole system, such as board
failure and clock board
failure.
Major Refers to fault alarms and Should be handled timely.

events of boards or line in Otherwise, the important
local parts. functions will be affected.

Minor Refers to general fault alarms Such alarms are used to

and events that indicate the remind the maintenance
operating status of boards or engineer to efficiently locate
line. the alarm causes and
eliminate the possible faults.
Warning Refers to the fault alarms and The maintenance engineer

events that do not affect the can learn the information
system performance and about the running status of
services but may impose the network and the
potential impacts on the equipment and handle the
service quality of the alarms according to the
equipment or resources. actual situations.
Some refers to the prompt
information of the system
when equipment restores to
normal, for example, the
switching alarm.
For NA NEs, alarms come in the following five levels in descending order of severity: Critical,
Major, Minor, Not Alarmed and Not Reported.
NOTE
The five alarms for the NEs for NA version can be displayed only when you select the NA version during
the U2000 installation.
Critical Refers to fault alarms and Should be handled

events that may result in immediately. Otherwise, the
breakdown of the NE or the system may break down.
whole system, such as board
failure and clock board
failure.
Major Refers to fault alarms and Should be handled timely.

events of boards or line in Otherwise, the important
local parts. functions will be affected.
Minor Refers to general fault alarms Such alarms are used to

and events that indicate the remind the maintenance
operating status of boards or engineer to efficiently locate
line. the alarm causes and
eliminate the possible faults.

Not Alarmed Refers to the fault alarms and The maintenance engineer
events that do not affect the can learn the information
system performance and about the running status of
services but may impose the network and the
potential impacts on the equipment and handle the
service quality of the alarms according to the
equipment or resources. actual situations.
Some refers to the prompt
information of the system
when equipment restores to
normal, for example, the
switching alarm.
Not Reported Refers to alarms that can be If the maintenance engineer

neglected. The equipment need some type of alarms do
usually does not report this not report, you can set the
type of alarms. This type of alarm status in the NE
alarms are displayed on the explorer according to the
U2000 only after you actual situations.
perform synchronization on
the U2000.
You can take different measures for alarms of different severities. On the U2000, you can
redefine the severity level for an alarm as required. You need to adjust the severity for an alarm
only when the alarm has severer or less severe impacts than when it is at the original severity
level.
7.1.10 Alarm States

Alarm states are defined based on alarm acknowledgement and clearance. You can take
corresponding processing measures based on alarm states.
l Alarm states
On the U2000, alarms have four states based on alarm acknowledgement and clearance:
– unacknowledged and uncleared
– acknowledged and uncleared
– unacknowledged and cleared
– acknowledged and cleared
NOTE
Acknowledged and cleared alarms become history alarms after you set the lifecycle. All the other
alarms are included in the current alarms. For details on how to set the lifecycle, see 7.10.8 Setting
the Lifecycle of the Current Alarm.
l Changing alarm states
– Changing the clearance status
When the condition that causes an alarm disappears, the NE or the U2000 server
recovers to its normal state. In this case, the NE or the U2000 server reports a clearance

alarm. Thus, the alarm state changes from uncleared to cleared. You can also manually
clear an alarm.
– Changing the acknowledgement status
If an alarm is acknowledged, it indicates that the alarm will be processed or has been
processed. After acknowledgement, the alarm state changes from unacknowledged to
acknowledged.
You can unacknowledge an acknowledged alarm. After the alarm is unacknowledged,
the alarm state changes from acknowledged to the unacknowledged.
l Alarm state change model
Figure 7-7 shows the alarm state change model.
Figure 7-7 Alarm state change model
7.1.11 Alarm Category

The alarms can be categorized according to the generating location and the U2000 standards
and functions.
The alarms can be categorized into the following two types according to the generating location:
l NE alarms: refer to the alarms generated when the NE equipment is faulty.
l U2000 alarms: refer to the alarms generated when the U2000 environment or the connection
between the U2000 and NE is faulty.
Based on the standards and functions of the U2000, alarms can be categorized into six types as
follows:
l Communication alarms: refer to the alarms related to NE communication, ECC
communication, and optical signal communication. For example, the interruption of NE
communication and the loss of optical signals.
l Process alarms: refer to the alarms related to the software processing and exception. For
example, equipment bus collision and the standby path check failure.
l Equipment alarms: refer to the alarms related to equipment hardware. For example, the
laser failure and the optical port loopback.

l Service alarms: refer to the alarms related to the service status and network QoS. For
example, the multiplex section performance threshold-crossings and the excessive B2 bit
errors.
l Environment alarms: refer to the alarms related to the power supply system and the
environment, such as temperature, humidity, and access control. For example, the
temperature of the power module exceeds the threshold.
l Security alarms: refer to the alarms related to the security of the U2000 and NEs. For
example, an NE user is not logged in.
7.1.12 Current Alarms and History Alarms

Current alarms and history alarms have the following four types: current NE alarms, history NE
alarms, current U2000 alarms and history U2000 alarms.
Current NE Alams and Current U2000 Alarms

The current NE alarms indicate the alarm data stored in the current alarm database of the system
control board on the NE. If the alarm suppression is set, the current alarms may not indicate the
actual condition.
The U2000 alarm refers to the alarm data stored in the current alarm library of the U2000.
Whether the current U2000 alarm is consistent with the current NE alarm depends on the
following factors:
l Whether the automatic alarm reporting is configured.
l Whether the alarm filtering is configured.
l Whether the alarm reversion is configured.
l Whether the alarm synchronization or the alarm check is performed.
l Whether the alarm deletion or the alarm acknowledgement is performed.
l Whether the alarms generated by the U2000 itself exist.
History NE Alarm and History U2000 Alarm

History NE alarms refer to the alarms cleared on the NE. These alarms are stored in the history
alarm library of the SCC. The history U2000 alarms refer to the alarms moved from the current
alarm library to the history alarm library after a user acknowledges them when they are cleared
on the U2000. Whether the history U2000 alarm is consistent with the history NE alarm depends
on the following factors:
l Whether the automatic alarm reporting is configured.
l Whether the alarm filtering is configured.
l Whether the alarm deletion or the alarm acknowledgement is performed.
l Whether the alarms generated by the U2000 itself exist.
7.1.13 Alarm Statistics

The function of performing statistics on alarm logs allows you to set filter conditions to statistics,
save a statistics condition as a template, save statistics on a local computer, and print statistics.
On the U2000, the statistics about the current alarms can be collected. The U2000 collects the
current alarm statistics in unit of node according to the statistics items, such as alarm severity
and alarm status. You can set a time range for the U2000 to collect the alarm statistics within
this time range.

7.1.14 Alarm Dumping

When the history alarm data in the U2000 database exceeds a certain amount, the U2000
operations will be affected, or even worse, the entire system could be down. The alarm dumping
function is used to save the history alarm data in the U2000 database to a specified directory as
a file. In this way, the U2000 performance is improved.
Overflow Dumping
You can set the maximum storage capacity of the alarms using the U2000. The U2000
periodically checks the number of history alarms. Once the history alarm data exceeds the
capacity, the U2000 automatically dumps the data in the history alarm library to a file to relieve
the burden of the U2000 computer. This alarm dumping mode is known as the overflow dumping.
Usually, you do not need to manually configure the overflow dumping parameters. However,
on some occasions such as in a larger-scaled network, or when a large amount of alarms are
raised within a short period, you can set the upper threshold to two or three times the original
value. Before you do this, ensure that sufficient database and disk spaces are available.
Periodical Dumping
The U2000 automatically dumps the alarm data stored in the U2000 to a specified directory
according to the preset period. This alarm dumping mode is known as the periodical dumping.
In this mode, you can set the dumping period and save the alarm records in recent days. For
example, if you set the dumping period to five days, save the alarm records of the last day, and
enable the settings to take effect since January 1, the U2000 performs the dumping in January
5. The dumped history alarms are the alarms that are ended before January 4.
Manual Dumping
By using this function, you can dump the history alarm data in the U2000 database to a specified
directory at any time. This mode is known as the manual dumping. In this mode, you can specify
the period for manual dumping. All alarms cleared within this period are dumped to the specified
directory. You can manually back up or delete these files.
NOTE
l On windows, the dump files are usually saved to the %IMAP%\server\dump directory.
l On UNIX, the dump files are usually saved to the $IMAP/server/dump directory.
7.2 Setting Trap Parameters on the NE

A trap receiver receives trap messages of the NE. This describes how to set trap parameters on
the NE. The NE actively sends fault information to the U2000 through trap packets defined by
SNMP. After the trap function is configured, the NE can actively send fault information.
Context
l This operation is applicable to the following SNMP NE: Router series, Switch series,
Security series, Access series NEs.
l Make sure that the source port and interface of trap packets configured on the NMS is
consistent with the source port and interface for sending packets configured on the NE.
Otherwise, the NMS cannot receive trap packets.

l To start the trap receiver on the U2000, ensure that Trap Receiver Process on the Process
Monitor tab page is in the running state. This process is automatically started by default.
If it is not automatically started, log in to the System Monitor client, click the Process
Monitor tab, right-click Trap Receiver Process, and then choose Start the Process from
the shortcut menu.
NOTE
The following section considers routers as an example to describe how to set trap parameters on the NE.
For details, see the documents relevant to the NE.
Procedure
1 Run the following command to telnet to the host.
telnet Host name of the server
2 Run the following command to enter the system view.

system-view
3 Run the following command to enable the function of sending trap packets:
snmp-agent trap enable [ trap-type [ trap-list ] ]
If no parameter is carried in this command, it indicates that all modules can send all types of
trap packets.
4 Run the following command to set the target host, that is, the NMS server:
snmp-agent target-host trap address udp-domain ip-address [ udp-port port-number ]
[ vpn-instance vpn-intance-name ] params securityname security-string [ v1 | v2c | v3
[ authentication | privacy ] ]
5 Run the following command to specify the source interface for sending trap packets:
snmp-agent trap source interface-type interface-number
----End
7.3 Setting Automatic Alarm Reporting

If you set alarms on an NE to be automatically reported, once the alarm is raised on the NE, it
is automatically reported to the U2000. You can disable the automatic reporting for unimportant
alarms to reduce the impact on the U2000 performance. A large volume of alarm information
affects the performance of the U2000.
7.3.1 Setting Automatic Reporting Status for Alarms of an NE
You can set the automatic reporting status of the alarms of specific boards so that the U2000
only monitors important alarms, thus improving the network maintenance efficiency. To
implement automatic reporting of the alarms of an NE, you can apply an alarm attribute template
to the NE.
7.3.2 Setting Automatic Reporting Status for Alarms of a Board
implement the function, you can manually set the automatic reporting status for each alarm or
apply the alarm attribute template to a board.

7.3.1 Setting Automatic Reporting Status for Alarms of an NE

implement automatic reporting of the alarms of an NE, you can apply an alarm attribute template
to the NE.
Prerequisite
l You must be an NM user with the "NE maintainer" and "NM monitor" authority or higher.
l The alarm attribute template that has the alarm reporting status configured as required must
be customized first.
Context
After you set alarms not to be automatically reported, if alarms are generated in an NE, the NE
does not automatically report them to the U2000. You can use the U2000, however, to
synchronize and query the alarms so that the alarms are reported to the U2000.
NOTE
The following steps are not applicable to the OptiX PFE 1670. The navigation path to this function for the
OptiX PFE 1670 is as follows: In th NE Panel, select the NE, right-click, and then choose NE Report
Status from the shortcut menu.
Procedure
1 Choose Fault > Settings > NE Alarm/Event Config from the main menu.
The NE Alarm/Event Config tab page is displayed.
2 Choose SDH/WDM/NAWDM from the Function Tree. In the right pane, select the pre-
customized template from the Template drop-down list and click Apply to. The Apply Alarm
Attribute Template to NE dialogue box is displayed.
NOTE
If the appropriate alarm attribute template is not available, you need to customize a template first.
3 Check the Alarm Auto-Report in the Alarm Attribute group box.
4 Select the NE you need from the List of Optional Objects, and move it to List of Selected
Objects. Click OK.
Wait for a few seconds and the Operation Result dialog box is displayed.
5 Click Close.
----End
7.3.2 Setting Automatic Reporting Status for Alarms of a Board

implement the function, you can manually set the automatic reporting status for each alarm or
apply the alarm attribute template to a board.

Prerequisite
l You must be an NM user with "NE operator" authority or higher.Y
l If you use the template to set the alarm suppression status, You must be an NM user with
"NM monitor" authority or higher.
Context
After you set alarms not to be automatically reported, if alarms are generated in an NE, the NE
does not automatically report them to the U2000. You can use the U2000, however, to
synchronize and query the alarms so that the alarms are reported to the U2000.
Procedure
1 In the NE Explorer, select a board and choose Alarm > Alarm Severity and Auto Reporting
from the Function Tree.
2 Set the Auto Reporting Status for the alarms and click Apply. The Operation Result dialog
box is displayed.
NOTE
If you have already created an alarm attribute template, you can click Use Template to set the automatic
reporting status of the alarms.
3 Click Close.
----End
7.4 Customizing Alarm Template

The U2000 provides the customized alarm browsing template and alarm attributes template.
You can quickly set the alarm browsing filtering criteria and the alarm attributes, by using the
preset customized alarm template.
7.4.1 Alarm/Event Template
An alarm/event template is used to save the alarm/event query or statistical conditions.
7.4.2 Setting an Alarm/Event Template
You can save frequently used query conditions or statistical conditions of alarms/events as a
template. If you want to query or collect statistics on alarms/events that meet the same conditions,
you can use the template. Thus, you do not need to set conditions.
7.4.3 Setting Template Properties for the Current User
On the U2000 client, you can set the monitor template, startup template, and default template
for the current user. These templates helps you to monitor, query, and collect statistics on alarms
and events.
7.4.4 Customizing Alarm Attribute Template
You can customize an alarm management template to quickly set the alarms to be reported and
the alarm severities for multiple NEs. This helps you to focus on important alarms and thus
facilitates the network maintenance.

7.4.1 Alarm/Event Template

An alarm/event template is used to save the alarm/event query or statistical conditions.
Template Types
Alarm/event templates are classified into several types. Table 7-7 describes the functions of
each type of template.
Table 7-7 Template functions
Template Type Function
Current alarm template Used for browsing the current alarm.
Browse current alarm by status template Used for browsing the current alarm by status.
Browse current alarm by severity template Used for browsing the current alarm by severity.
Alarm log template Used for querying alarm logs.
Event log template Used for querying event logs.
Alarm log statistics template Used for collecting statistics on alarm logs.
Event log statistics template Used for collecting statistics on event logs.
History alarm template Used for querying acknowledged and cleared

alarm logs.
Template Sharing
When you create a template, you can set it to be shared. The shared template is visible to all
users.
l The users other than Administrators can open only templates created by themselves and
shared by other users. Administrators can open all templates.
l The users other than Administrators can set only the templates created by themselves to be
shared. Administrators can set the templates created by any user to be shared.
Template States
for the current user:
l Monitor template: It is used for the alarm indicator at the upper right corner on the
U2000 client GUI to display the statistics of alarms at different severity levels. It must be
the current alarm templates.
l Startup template: The U2000 opens some current alarm windows automatically according
to the templates after you successfully log in to the U2000 client. You can set a maximum
of five startup templates.

l Default template: When a user chooses the menu for querying or collecting statistics on
alarms or events, the U2000 uses this template to open the window corresponding to this
menu. You can set only one default template for a functional window.

Context
l Choose Fault > Browse Current Alarm, Fault > Browse Alarm Logs, Fault > Browse
Event Logs, Fault > Browse Current Alarm by Severity, Fault > Browse Current
Alarm by Status or Fault > Browse History Alarm from the main menu. In the Filter
dialog box, set the alarm query conditions. Click OK. In the query window, you can click
Template in the lower left area to display a menu list. By choosing a menu from this menu
list, you can create, open, save, save as or delete a query template.
NOTE
If you set the default template, you need to click Filter to access the Filter dialog box.
l Choose Fault > Query Alarm Log Statistics or Fault > Query Event Log Statistics from
the main menu. In the statistics window, click Template in the lower left area to display a
menu list. By choosing a menu from this menu list, you can create, open, save, save as or
delete a statistics template.
Procedure
1 Choose Fault > Settings > Template Management from the main menu.
2 In the Template Management window, you can perform the following operations to set an
alarm/event template.
Set a Template Operation

Create a template 1. Click New.
2. In the Add Template dialog box, enter a template name and
description, select a template type and template sharing, and
then click Next.
3. In the Add Template dialog box, set the basic information and
filtering conditions.
4. Click Finish.


Delete a template 1. Select one or more templates, and then click Delete.
2. In the Confirm dialog box, click Yes.
Rename a template 1. Select a template, and then click Rename.
2. In the Enter the template name dialog box, modify the
template name.
3. Click OK.
Modify a template 1. Select a template, and then click Property.
2. In the Property dialog box, modify the template name,
template sharing, description, and filtering conditions.
3. Click OK.
NOTE
To change the template attribute, you can right-click the template and
choose Monitor Template, Default Template, Startup Template, or
Share.
Open a template Right-click a template and choose Open.
Save as another template 1. Right-click a template and choose Save As.

2. In the Enter the template name dialog box, enter a name that
is different from all existing template names, select Set as
shared Template, Set as default template or Set as startup
template as required, and then click OK.
----End
7.4.3 Setting Template Properties for the Current User

for the current user. These templates helps you to monitor, query, and collect statistics on alarms
and events.
Context
l Monitor template: It is used for the alarm indicator at the upper right corner on the
U2000 client GUI to display the statistics of alarms at different severity levels. It must be
the current alarm templates.
l Startup template: The U2000 opens some current alarm windows automatically according
to the templates after you successfully log in to the U2000 client. You can set a maximum
of five startup templates.
l Default template: When a user chooses the menu for querying or collecting statistics on
alarms or events, the U2000 uses this template to open the window corresponding to this
menu. You can set only one default template for a functional window.
Procedure

2 In the Template Management dialog box, click Config.
3 In the Template Configuration dialog box, click on the right of Monitor

Template. Select a template in the Choose dialog box, and then click OK.
4 Click on the right of Startup Template. Select one or more templates in the
Choose dialog box, and then click OK.
5 In the Default Template area, click on the right of each type of template. Select a
template in the Choose dialog box, and then click OK.
6 Click OK.
----End
7.4.4 Customizing Alarm Attribute Template

You can customize an alarm management template to quickly set the alarms to be reported and
the alarm severities for multiple NEs. This helps you to focus on important alarms and thus
facilitates the network maintenance.

Prerequisite
l You must be an NM user with "Fault Operator" authority or higher.
l The alarm attribute template function is applicable to the MSTP, WDM, NA WDM, RTN,
PTN, Marine series NEs.
Context
l If the alarm attribute template is not created, the U2000 handles the alarms reported from
NEs according to the default alarm attribute template.
l If a template on one of the U2000 servers is customized, you are recommended to customize
the same template on other U2000 servers, to ensure that the alarms are consistently
monitored on each server.
l You can set different alarm management templates for different NEs.
l After a customized alarm attribute template is applied to NEs, the alarm settings on the
NEs are updated according to the alarm attribute template. If the alarm severity and
reporting mode are modified in the alarm attribute template and the alarm attribute template
is applied to NEs, the settings of the NEs, such as alarm masking and alarm reversion, are
invalid.
Procedure
2 Choose SDH/WDM/NAWDM from the Function Tree. In the right pane, select a template from
the Template drop-down list.
3 Select the desired alarm, right-click the fields corresponding to Severity, Auto Reporting
Status, and Status and choose proper values from the shortcut menus.
4 Click Save to save your modifications, or click Save As and enter a template name to save it as
a new template.
NOTE
The default alarm template cannot be changed.
5 Click Close in the dialog box that is displayed.
6 Click Apply to.
7 Select the alarm attributes to be applied in the dialog box that is displayed. Select the required
NEs in OPTIONAL_OBJECT and add them to SELECTED_OBJECT. Click OK.
8 Click Close in the dialog box that is displayed.

NOTE
After the alarm attribute template is applied to the NE, the U2000 automatically handles the alarms reported
from the NE according to the settings in the template.
----End

7.5 Synchronizing Alarms

You can synchronize the current alarms of the NE and the U2000. This feature ensures that the
alarms on the NEs are synchronous with the alarms on the U2000, and that the current NM
alarms are synchronous with the alarms in the U2000 alarm database.
7.5.1 Synchronizing Networkwide Current Alarms
The alarm synchronization operation compares the alarms in the U2000 database and the alarms
in the NE database. If the alarms are inconsistent, the alarms in the NE database are uploaded
to the U2000 database. The existing alarms in the U2000 database are overwritten. When the
services are interrupted and then recovered, or when you need to check the operational status of
the entire network, synchronize the networkwide alarms.
7.5.2 Synchronizing the Current Alarms for an NE
services are interrupted and then recovered, or when there is any operation that may cause
inconsistency between the U2000 and the NE alarms, you can synchronize the current alarms
for the specified NE.
7.5.3 Setting Alarm Auto Synchronization
You can set alarm auto synchronization. After the U2000 resumes the communication with an
NE or is restarted, the U2000 automatically synchronizes the alarms with those on the NE. This
helps keep alarm data consistency between the U2000 and NEs.
7.5.1 Synchronizing Networkwide Current Alarms

services are interrupted and then recovered, or when you need to check the operational status of
the entire network, synchronize the networkwide alarms.
Prerequisite
You must be an NM user with "Fault Operator" authority or higher.
The security NE of the Eudemon, USG, SIG, SVN ,SRG and EGW series does not support the
function of synchronizing the networkwide current alarms.
Procedure
1 Choose Fault > Synchronize Networkwide Alarms from the main menu.
A progress bar is displayed. After the operation is complete, a prompt appears telling you that
the operation was successful.
2 Click Close.
----End
7.5.2 Synchronizing the Current Alarms for an NE


services are interrupted and then recovered, or when there is any operation that may cause
inconsistency between the U2000 and the NE alarms, you can synchronize the current alarms
for the specified NE.
Prerequisite
The security NE of the Eudemon, USG, SIG, SVN ,SRG and EGW series does not support the
function of synchronizing the networkwide current alarms.
Procedure
1 In the Workbench window, double-click the icon, then enter the Main Topology
window.
2 Select an NE on the Main Topology.

NOTE
If you select topology subnet form the Main Topology, it indicates that all NEs in that topology subnet are
selected.
3 Right-click the selected NE and choose Synchronize Current Alarms from the shortcut menu.
The progress bar is displayed. After the operation is complete, a prompt appears telling you that
the operation was successful.
4 Click Close.
----End

Prerequisite
The security equipment of the Eudemon, USG, SIG, SVN ,SRG and EGW series does not support
the function of synchronizing the networkwide current alarms.
Procedure
1 Choose Fault > Settings > Options from the main menu.
2 In the Alarm Option dialog box, in the navigation tree on the left, select Auto Synchronize.
In the dialog box that is displayed, set the alarm synchronization parameters.
l Synchronize all alarms at NMS start indicates that the U2000 automatically synchronizes
the alarms with those on all the NEs when it is started.

l Synchronize device alarms after recovery from a communication interruption

indicates that the U2000 automatically synchronizes the alarms with those on a specific
NE when it resumes the communication with the NE.
l After LCT user logout indicates that the U2000 automatically synchronizes the alarms
with those on a specific NE when the LCT user logs out.
NOTE
The After LCT user logout parameter is available only when you select the Transmit Common
component during the installation of the U2000.
3 Click OK.
----End
7.6 Monitoring Network Alarms

The network maintenance engineer can monitor network alarms to learn about the running status
of the network in time. The U2000 provides multiple alarm browsing methods through which
you can view alarms on different objects.

to handle alarms.
7.6.2 Monitoring Alarms Through the Topology View
You can monitor the alarm data of NEs in real time through the topology view.
7.6.3 Monitoring Alarms Through the Alarm Panel
On the alarm panel on the U2000 client, you can view the number of alarms of different severities,
and know the latest alarm information by using the alarm panel functions of automatic display
or automatic flash of the alarm indicator. In addition, you can open the alarm browse windows
through the alarm panel.
7.6.4 Browsing the Current Alarm
You can browse the alarms that require attention and processing by setting the filtering
conditions of the current alarm.
7.6.5 Browse History Alarms
This section describes how to query history alarms and how to perform the associated operations.
7.6.6 Querying Alarm Logs
You can view the log of each alarm in the log library after setting the conditions for querying
alarm logs.
7.6.7 Querying Event Logs
You can view the log of each event in the log library after setting conditions for querying event
logs.
7.6.8 Monitoring Alarms Through the Alarm Bar Chart
Through the bar chart in the Query Alarm Bar Chart window, you can know the statistical
results (in the form of figures and numerals) of the current alarm templates that correspond to
specific bar charts.
7.6.9 Displaying Current Alarms by State

This function enables you to view current alarms by state in one window. By using this function,
a window is divided into four small panels to display alarms by state.
7.6.10 Displaying Current Alarms by Severity
This function enables you to view the current alarms by severity in one window. By using this
function, a window is divided into four small panels to display alarms by severity.
7.6.11 Setting Columns on an Alarm/Event Interface
In the alarm/event query window, you can display only the information of the preset fields by
setting the displayed columns of alarms/events.
7.6.12 Viewing the Statistics of Alarms
The U2000 enables you to collect statistics on alarms by condition. You can use an existing
alarm statistics template or create a template to collect statistics on alarms.
7.6.13 Querying Alarms on the Opposite Port
To facilitate locating faults, the U2000 supports the function of querying the alarms of the
opposite port, that is, query the alarms of the opposite port that is connected by the optical fiber
through the current alarms.

to handle alarms.
Alarm reporting flow chart

l For Router series, Switch series, Security series, Access series NEs, Figure 7-8 shows the
l For MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, Figure 7-9 shows the


Alarm Monitoring by Board

When monitoring an alarm, the board immediately reports the alarm to the SCC continuously.
If the alarm database of the SCC does not have this alarm, the alarm data is saved into the database
and a notification is reported. Otherwise, the alarm data is discarded directly.

Automatic Alarm Reporting

When the SCC receives a new alarm notification, it determines whether to report the alarm to
the U2000 according to the settings of the alarm automatic reporting. After the U2000 receives
an alarm notification, it responds to the SCC a confirm message. If the SCC does not receive
any confirm message within a time period, it reports the alarm to the U2000 again. This scheme
ensures the reliability of the alarm reporting.
If the communication between the U2000 and the NE is interrupted, when the U2000 is restarted,
it automatically synchronizes the alarm library of the SCC to keep the alarm data on the
U2000 synchronous with the alarm data on NE.
U2000 Alarm Notification

Based on the user-defined alarm filter criteria, the U2000 decides whether to discard the alarm
reported from an NE. As for the alarms saved in the U2000 database, the U2000 analyzes them
according to the alarm correlation rules. Then it presents the analysis result on the U2000 client
and notifies the information to the user.
7.6.2 Monitoring Alarms Through the Topology View

You can monitor the alarm data of NEs in real time through the topology view.
Context
l In the topology view, the color of an NE icon depends on the alarm severity. If an NE
generates multiple alarms at the same time, its icon displays the color of the highest severity
among these generated alarms.
l When you move the pointer to the icon of the NE that generates alarms, a tip is displayed,
prompting the alarm state, severity, and count.
l After choosing File > Preferences > Topology Status Display, if you set Display Style
of Alarm States to Use state icons, the upper left corner of the NE that generates an alarm
displays the alarm state icon and alarm severity icon.
l In the Main Topology window, click on the toolbar. An current alarm is displayed in
the lower area of the topology view. Click again. The current alarm is hidden. Select
a topology object in the topology view, and then select the Display alarms of selected
objects check box. The current alarm displays the alarms of the selected object only.
Procedure
1 Choose View > Main Topology from the main menu.
2 In the Main Topology window, right-click the icon of an NE that generates alarms. From the
displayed shortcut menu, choose menu items such as Browse Alarm.
NOTE
In the window such as Browse Current Alarm-Alarm Source, all alarms generated by the NE are
displayed.
----End
7.6.3 Monitoring Alarms Through the Alarm Panel

On the alarm panel on the U2000 client, you can view the number of alarms of different severities,
and know the latest alarm information by using the alarm panel functions of automatic display

or automatic flash of the alarm indicator. In addition, you can open the alarm browse windows
through the alarm panel.
Procedure
l Monitoring alarms through the alarm panel
Choose Fault > Display Alarm Board from the main menu or click the icon on the
menu bar to display the alarm panel. See Figure 7-10. You can add current alarm templates
to the alarm panel. The alarm panel displays alarm information according to the preset
template.
NOTE
The bar charts in the Query Alarm Bar Chart window correspond to the template displayed on the
alarm panel. When you add or delete a alarm bar chart (alarm template) in the Query Alarm Bar
Chart window, the corresponding alarm template is automatically added or deleted on the alarm
panel. In the same way, when you perform add or delete operation on the alarm panel, the bar chart
in the Query Alarm Bar Chart window is modified accordingly.
Figure 7-10 Alarm panel
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not
Alarmed.
l Opening the alarm browse windows through the alarm panel
When monitoring alarms through the alarm panel, you can double-click specific current
alarm templates on the alarm panel and open the alarm browsing windows and view alarm
details.
----End
7.6.4 Browsing the Current Alarm

You can browse the alarms that require attention and processing by setting the filtering
conditions of the current alarm.

Context
l The current alarm displays the merged alarm logs. The alarm merging rule is that alarm
l For a newly reported alarm log, if the current alarm contains the record that meets the alarm
merging rule, the alarm log is merged into the previous record in the current alarm regardless
of the acknowledgement and clearance status of the record. After merging, the frequency
of the record is added by 1. The displayed acknowledgement and clearance state of the
record is subject to that of the latest alarm log.
l You can query details of every alarm in the alarm log browse window.
l When you filter current alarm based on the template, if a user has modified the parameters
in the template, you can click No in the Confirm window that is displayed after you close
the Browse Alarm List window to revoke the template modification.
Procedure
1 Choose Fault > Browse Current Alarm from the main menu, or click on the toolbar.
2 In the Filter dialog box, set the alarm query conditions.
NOTE
3 Click OK.
The result is displayed in the window.
NOTE
l indicates an intermittent alarm.
l indicates a high-frequency intermittent alarm.
l indicates a correlative alarm.
l indicates a root alarm.

l If you sort alarms by Alarm Source, alarms are sorted by the NE FDN (A NE identity) of alarm source,
rather than the name of alarm source.
l Select Display Latest Alarm to refresh alarms displayed in the window in real time.
l Select Scroll Lock to keep the alarms displayed in the window unchanged.
l Click Template and choose Open. In the Choose window, you can re-select a template for filtering.
l Click Filter to reset the conditions for filtering alarms.
l Click Refresh to refresh alarms displayed in the window.
l Select one or more alarms in the window, and click Acknowledge to acknowledge the alarms.
l Select one or more alarms in the window, and click Clear to clear the alarms.
l Select one or more alarms in the window, and press Ctrl+C to copy the contents to the clipboard.
l Click in the browse window. The Details and Handling Suggestion panels are hidden. Click
in the browse window. The Details and Handling Suggestion panels are shown.
----End
7.6.5 Browse History Alarms

This section describes how to query history alarms and how to perform the associated operations.

Context
If no history alarm is displayed in the Browse History Alarm window, you can search for
relevant history alarms in the dump file by navigating to the dump path of alarms. For information
about the dump path that stores alarm dump files, see 7.1.14 Alarm Dumping.
Procedure
1 Choose Fault > Browse History Alarm from the main menu.
2 In the Filter dialog box, set the alarm query conditions. Click OK.
NOTE
The result is displayed in the window.
NOTE
----End
7.6.6 Querying Alarm Logs

You can view the log of each alarm in the log library after setting the conditions for querying
alarm logs.
Context
l Alarm logs record all the alarms received by the U2000. In alarm logs, each alarm is
displayed as a record.
l The current alarm displays the merged alarm logs. The alarm merging rule is that alarm
l Acknowledged and cleared alarms become history alarms after you set the lifecycle. All
the other alarms are included in the current alarms. For details on how to set the lifecycle,
see 7.10.8 Setting the Lifecycle of the Current Alarm.
l When you filter alarm logs based on the template, if a user has modified the parameters in
the template, you can click No in the Confirm window that is displayed after you close the
Query Alarm Logs window to revoke the template modification.
Procedure
1 Choose Fault > Browse Alarm Logs from the main menu, or click on the toolbar.

NOTE
If you set the default template, you need to click Filter to display the Filter dialog box.
3 Click OK.
The result is displayed in the query window.
NOTE
l indicates an intermittent alarm.
l indicates a high-frequency intermittent alarm.
l indicates a correlative alarm.
l indicates a root alarm.

----End
7.6.7 Querying Event Logs

You can view the log of each event in the log library after setting conditions for querying event
logs.
Context
When you filter event logs based on the template, if a user has modified the parameters in the
template, you can click No in the Confirm window that is displayed after you close the Query
Event Logs window to revoke the template modification.
Procedure
1 Choose Fault > Browse Event Logs from the main menu, or click on the toolbar.
NOTE
3 Click OK.
The result is displayed in the query window.

NOTE
l indicates a repeat event.
l indicates a high-frequency repeat event.

l Select Display Latest Event to refresh events displayed in the window in real time.
l Select Scroll Lock to keep the events displayed in the window unchanged.
----End
7.6.8 Monitoring Alarms Through the Alarm Bar Chart

Through the bar chart in the Query Alarm Bar Chart window, you can know the statistical
results (in the form of figures and numerals) of the current alarm templates that correspond to
specific bar charts.
Context
l The U2000 provides the bar chart named All objects by default. The default bar chart is
used to monitor all the alarms in the current alarm and cannot be deleted.
l The bar charts in the Query Alarm Bar Chart window correspond to the template
displayed on the alarm panel. When you add or delete a alarm bar chart (alarm template)
in the Query Alarm Bar Chart window, the corresponding alarm template is automatically
added or deleted on the alarm panel. In the same way, when you perform add or delete
operation on the alarm panel, the bar chart in the Query Alarm Bar Chart window is
modified accordingly.
Procedure
1 Choose Fault > Alarm Bar Chart from the main menu.
The statistical results of the added current alarm templates are displayed in the Query Alarm
Bar Chart window.

NOTE
2 In the Query Alarm Bar Chart window, you can perform the following operations.
Task Operations
Set the contents and outlook Click Options. In the Options dialog box, set the contents and
to be displayed outlook to be displayed as required. Click OK.
Add an current alarm 1. Click Add.

template 2. In the Choose dialog box, select an current alarm template
and click OK.
NOTE
l The statistical results of the new current alarm template are
displayed in the Query Alarm Bar Chart window.
l If you select Display the templates created by the current user
only, the dialog box displays only the templates created by
yourself.
Delete a bar chart 1. Select one bar chart that does not belong to All objects,
and click Delete to delete current alarm templates.
Locate a bar chart to the Select one bar chart, and then click Locate to Current
current alarm Alarm to display the Browse Current Alarm window.

Task Operations
Set as the monitoring 1. Select one bar chart and click Show on Alarm Lamp.
template 2. In the Confirm dialog box, click Yes.
NOTE
The alarm indicator on the right of the toolbar counts alarms of all
severities according to the filtering conditions defined in the template.
----End
7.6.9 Displaying Current Alarms by State

This function enables you to view current alarms by state in one window. By using this function,
a window is divided into four small panels to display alarms by state.
Context
When you filter Current alarm based on the template, if a user has modified the parameters in
Browse Current Alarm by Status window to revoke the template modification.
Procedure
1 Choose Fault > Browse Current Alarm by Status from the main menu.

NOTE
3 Click OK.
Current alarms are displayed by state in the window.

NOTE
l Click the number buttons 1, 2, 3, and 4 to open or close the panes corresponding to the numbers.
----End
7.6.10 Displaying Current Alarms by Severity

This function enables you to view the current alarms by severity in one window. By using this
function, a window is divided into four small panels to display alarms by severity.
Context
When you filter Current alarm based on the template, if a user has modified the parameters in
Browse Current Alarm by Severity window to revoke the template modification.
Procedure
1 Choose Fault > Browse Current Alarm by Severity from the main menu.
NOTE
3 Click OK.
Current alarms are displayed by severity in the window.

NOTE
l Click the number buttons 1, 2, 3, and 4 to open or close the panes corresponding to the numbers.
----End
7.6.11 Setting Columns on an Alarm/Event Interface

In the alarm/event query window, you can display only the information of the preset fields by
setting the displayed columns of alarms/events.
Procedure
1 Choose Fault > Browse Current Alarm, Fault > Browse Alarm Logs, Fault > Browse Event
Logs, Fault > Browse Current Alarm by Severity, Fault > Browse Current Alarm by
Status or Fault > Browse History Alarm from the main menu. In the Filter dialog box, set the
alarm query conditions. Click OK. In the query window, right-click the table head or the blank
space at the bottom of the table, and choose Configure Columns.
2 In the Configure Columns dialog box, set the fields to be displayed and select Effective for
the current window and new windows of the same type or Effective for the current pane
only as required.

NOTE
l Specify a field name on the right of the dialog box and click or to
change the order for displaying fields in the table.
l The window of the same type indicates the window that is of the same type as the active window. For
example, if the active window is an current alarm window, the newly opened window of the same type
is another current alarm window.
3 Click OK.
----End
7.6.12 Viewing the Statistics of Alarms

The U2000 enables you to collect statistics on alarms by condition. You can use an existing
alarm statistics template or create a template to collect statistics on alarms.
Prerequisite
You must be an NM user with "Fault Watcher" authority or higher.
Procedure
1 Choose Fault > Query Alarm Log Statistics from the main menu.
2 In the dialog box that is displayed, set the statistical conditions and click OK.
NOTE
l All alarms are selected in the default alarm filtering template.

l If you set the startup template for alarm statistics, the Statistic Filter dialog box is not displayed. The
statistical result obtained by the startup template is displayed instead.
3 In the alarm statistics window, check the statistical result.

l Click the Table tab. Then, the alarm information is displayed in a customized table.
l Click the Pie tab. Then, the alarm information is displayed in a customized pie chart.
4 According to the buttons at the bottom of the Alarm Statistics window, you can perform the
following operations:
l Click Template to create, open, or save an alarm statistical template.
l Click Statistical Filter to set the statistical condition.
l Click Refresh to collect statistics on alarms again based on the current statistical condition.
l Click Print to print the statistical result in a specified medium.
l Click Save As to save the statistical result as a file.
----End
7.6.13 Querying Alarms on the Opposite Port

To facilitate locating faults, the U2000 supports the function of querying the alarms of the
opposite port, that is, query the alarms of the opposite port that is connected by the optical fiber
through the current alarms.

Prerequisite
To query the alarms of the opposite port, ensure that the NEs are connected by optical fibers.
Procedure
1 Choose Fault > Browse Current Alarm, Fault > Browse Current Alarm by Severity or
Fault > Browse Current Alarm by Status from the main menu.
NOTE
l Alternatively, click Copy from Template. In the dialog box that is displayed, select an existing
template, and then click OK to add the filtering criteria of the selected profile to the Filter dialog box.
l If the startup template for browsing the current alarms is set, the Filter dialog box is not displayed.
Instead, the alarms that meet the filter conditions set in the startup template are displayed directly.
3 In the alarm browsing window, select an alarm, right-click, and then choose Query Opposite
Port Alarms.
4 On the Browse Alarms Related to Opposite Port tab page, view the alarms of the opposite
port associated to this port.
----End
7.7 Managing the Alarm Maintenance Status

This topic describes how to manage the maintenance status of the alarms that are generated in
scenarios where alarm tests are performed on the NMS or NEs. You can configure the status of
these alarms as in maintenance. As a result, when the NMS receives such alarms, it marks them
as being maintained, thus giving prominence to these alarms. This function is applicable to router
series NEs and switch series NEs.
7.7.1 Importing Alarm Maintenance Criteria
This topic describes how to import an alarm maintenance criteria into the NMS after the script
for the criteria is ready. Multiple criteria can be imported synchronously.
7.7.2 Configuring Alarm Maintenance Criteria
This topic describes how to set the alarm maintenance criteria in the NMS.
7.7.3 Activating and Deactivating Maintenance Criteria
This topic describes how to activate and deactivate maintenance criteria. Only after the activated
maintenance criteria take effect in the NMS can the alarms meeting the criteria be displayed as
in the maintenance status.
7.7.4 Browsing Alarms in the Maintenance State
This topic describes how to browse alarms that are in the maintenance state.
7.7.1 Importing Alarm Maintenance Criteria

This topic describes how to import an alarm maintenance criteria into the NMS after the script
for the criteria is ready. Multiple criteria can be imported synchronously.

Prerequisite
Script of the maintenance criteria must be complete before the criteria can be imported. The
following table shows the description of script parameters.
NOTE
The script is in the XLS format.
Table 7-8 Description of script parameters for maintenance criteria

Parameter Description
Product Name Specifies the name of the project that the alarm belongs to.
Mandatory. The value contains a maximum of 255 characters.
Start Time Specifies the time when the project begins.

Mandatory. The value is in the format of 2010-1-2 13:10.
End Time Specifies the time when the project ends.

Mandatory. The value is in the format of 2010-1-2 13:10.
Administrative Specifies whether a maintenance criterion takes effect.

Status Yes.
NE Name Specifies the name of the NE that generates alarms.

Mandatory. The value contains a maximum of 255 characters.
NE IP Address Specifies the IP address of the NE that generates alarms.

Mandatory. In dotted decimal notation.
NE Card Specifies the shelf or card of the NE that generates alarms.

Optional. If an NE card includes multiple shelves, identify the card in
the format of Shelf number, Slot number, and Card number. For
example, 2.4.1. If an NE card includes only a single shelf, identify the
card in the format of Slot number and Card number. For example,
4.1.
If multiple cards exist, separate the cards by the symbol ",". For example,
4.1,4.3,4.5. If the subcard numbers of multiple cards are consecutive,
you can use the symbol "~" to represent the subcard numbers. For
example, 4.1~4.4.
NE Port Specifies the port of the NE that generates alarms.

Optional. The value is in the format of Interface type+Slot number/
interface card number/port number. For example,
GigabitEthernet3/0/0.
If multiple ports exist, separate the ports by the symbol ",". For example,
GigabitEthernet3/0/0,GigabitEthernet3/0/2,GigabitEthernet3/0/4.
If the numbers of multiple ports are consecutive, you can use the symbol
"~" to represent the port numbers. For example,
GigabitEthernet3/0/0~GigabitEthernet3/0/3.
Peer NE Name Specifies the name of the peer NE that generates alarms.
Optional. The value contains a maximum of 255 characters.

Parameter Description
Peer NE IP Specifies the IP address of the peer NE that generates alarms.

Address Optional. The value is required when setting the Peer NE Name, in
dotted decimal notation.
Peer NE Card Specifies the shelf or card of the peer NE that generates alarms.
Optional. If an NE card includes multiple shelves, identify the card in
the format of Shelf number, Slot number, and Card number. For
example, 2.4.1. If an NE card includes only a single shelf, identify the
card in the format of Slot number and Card number. For example,
4.1.
If multiple cards exist, separate the cards by the symbol ",". For example,
4.1,4.3,4.5. If the subcard numbers of multiple cards are consecutive,
you can use the symbol "~" to represent the subcard numbers. For
example, 4.1~4.4.
Peer NE Port Specifies the port of the peer NE that generates alarms.
Optional. The value is in the format of Interface type+Slot number/
interface card number/port number. For example,
GigabitEthernet3/0/0.
If multiple ports exist, separate the ports by the symbol ",". For example,
GigabitEthernet3/0/0,GigabitEthernet3/0/2,GigabitEthernet3/0/4.
If the numbers of multiple ports are consecutive, you can use the symbol
"~" to represent the port numbers. For example,
GigabitEthernet3/0/0~GigabitEthernet3/0/3.
Type of Masked Specifies the remarks of the type of masked alarms.

Alarms Optional.
Operation Specifies the operations of the project.

Optional.
Contact Specifies the name of the contact person.

Optional.
Telephone Specifies the phone number of the contact person.

Optional.
Others Specifies other related information.

Optional.
Procedure
1 Choose Fault > Configuration Maintenance from the main menu.
2 In the Maintenance Status dialog box, click Import.
3 In the Import dialog box, select the script to be imported and click Import.

The maintenance criteria will be displayed in the query result area after the script is successfully
imported.
----End
7.7.2 Configuring Alarm Maintenance Criteria

This topic describes how to set the alarm maintenance criteria in the NMS.
Procedure
2 In the Maintenance Status dialog box, click Configure.
3 In the New Maintenance Status dialog box, set the related parameters.
4 Click OK.
The created alarm maintenance criteria will be displayed in the result query area.
----End
7.7.3 Activating and Deactivating Maintenance Criteria

This topic describes how to activate and deactivate maintenance criteria. Only after the activated
maintenance criteria take effect in the NMS can the alarms meeting the criteria be displayed as
in the maintenance status.
Prerequisite
If there are maintenance criteria in the NMS, do as follows to activate or deactivate a maintenance
criterion:
Procedure
2 In the Maintenance Status dialog box, click Condition to set the filter criteria.
3 Click Query.
4 Select a maintenance criterion, right-click, and then choose Active or Deactive from the shortcut
menu to activate or deactivate it.
Alternatively, you can select a maintenance criterion, and then click Modify to access the
Modify Maintenance Status dialog box. Then, set Administrative Status to Activate or
Deactivate to activate or deactivate the criterion. Click OK to complete the setting.
----End
7.7.4 Browsing Alarms in the Maintenance State

This topic describes how to browse alarms that are in the maintenance state.

Procedure
2 In the Filter dialog box, set the filter criteria.
3 Click OK.
The alarms meeting the criteria will be displayed in the query result area.
4 Select an alarm of which the status appears to be In Maintaining and view details about the
alarm in the Details and Handling Suggestion areas.
NOTE
If no column of Maintenance Status is displayed, right-click in the list header field and choose Configure
Columns from the shortcut menu. Then, move Maintenance Status to Selected Column and click OK.
----End
7.8 Collecting Statistics on Alarms/Events

By collecting statistics on alarms/events through templates or statistical conditions, you can
know the fault status of the network and obtain associated data. This helps you to rectify the
fault and optimize the network.

7.8.2 Collecting Statistics on Alarm Logs
The function of collecting statistics on alarm logs enables you to set the statistical conditions,
save the statistical conditions as a template, save statistics, and print statistics.
7.8.3 Collecting Statistics on Event Logs
The function of performing statistics on event logs enables you to set the statistical conditions,

Context
dialog box, set the alarm query conditions. Click OK. In the query window, you can click
Template in the lower left area to display a menu list. By choosing a menu from this menu
list, you can create, open, save, save as or delete a query template.
NOTE
l Choose Fault > Query Alarm Log Statistics or Fault > Query Event Log Statistics from
the main menu. In the statistics window, click Template in the lower left area to display a

menu list. By choosing a menu from this menu list, you can create, open, save, save as or
delete a statistics template.
Procedure
2 In the Template Management window, you can perform the following operations to set an
alarm/event template.

Create a template 1. Click New.
2. In the Add Template dialog box, enter a template name and
description, select a template type and template sharing, and
then click Next.
3. In the Add Template dialog box, set the basic information and
filtering conditions.
4. Click Finish.
Delete a template 1. Select one or more templates, and then click Delete.
Rename a template 1. Select a template, and then click Rename.
2. In the Enter the template name dialog box, modify the
template name.
3. Click OK.
Modify a template 1. Select a template, and then click Property.
2. In the Property dialog box, modify the template name,
template sharing, description, and filtering conditions.
3. Click OK.
NOTE
To change the template attribute, you can right-click the template and
choose Monitor Template, Default Template, Startup Template, or
Share.
Open a template Right-click a template and choose Open.


Save as another template 1. Right-click a template and choose Save As.
2. In the Enter the template name dialog box, enter a name that
is different from all existing template names, select Set as
shared Template, Set as default template or Set as startup
template as required, and then click OK.
----End
7.8.2 Collecting Statistics on Alarm Logs

The function of collecting statistics on alarm logs enables you to set the statistical conditions,
Context
l The U2000 supports up to 400,000 statistical results. The total number of statistical results
is the sum of statistical results based on the selected statistical items. If the number of
statistical results is 0, this statistical result is not displayed on the client. Therefore, the
number of statistical results displayed on the client is smaller than the total number of
statistical results.
l The statistical results can be displayed in a table or pie chart. By default, they are displayed
in a table.
l Statistical results based on the selected statistical items are displayed in different pie charts.
You can click a tab named a statistical item to view the corresponding pie chart.
l When you filter alarm logs based on the template, if a user has modified the parameters in
Query Alarm Log Statistics window to revoke the template modification.
Procedure
1 Choose Fault > Query Alarm Log Statistics from the main menu.

2 In the Statistic Filter dialog box, set the statistical conditions of alarm logs, and then click
OK.
3 In Query Alarm Log Statistics window, you can perform the following operations.
Task Operations
Display statistical results in Click the Table tab at the lower left corner, and then expand
a table the collapsed items in the statistical result table to view all
statistics.
Display statistical results in Click the Pie tab at the lower left corner, and then click a tab
a pie chart named a statistical item at the upper left corner to view the
statistics based on this statistical item.
Open a statistical template 1. Click Template, and then click Open.

2. Select one template in the Choose window, and then click
OK.
Re-set the statistical 1. Click Statistic Filter.
conditions 2. In the Statistic Filter dialog box, set the statistical
conditions of alarm logs, and then click OK.
Refresh statistical results Click Refresh.

Task Operations
Save statistical results 1. Click Save As.
2. In the Save dialog box, select the path for saving records,
and then click Save.
Print statistical results 1. Click Print.
2. In the Print dialog box, set the print parameters, and then
click Print.
----End
7.8.3 Collecting Statistics on Event Logs

The function of performing statistics on event logs enables you to set the statistical conditions,
Context
l The U2000 supports up to 400,000 statistical results. The total number of statistical results
is the sum of statistical results based on the selected statistical items. If the number of
statistical results is 0, this statistical result is not displayed on the client. Therefore, the
number of statistical results displayed on the client is smaller than the total number of
statistical results.
l The statistical results can be displayed in a table or pie chart. By default, they are displayed
in a table.
l Statistical results based on the selected statistical items are displayed in different pie charts.
You can click a tab named a statistical item to view the corresponding pie chart.
l When you filter event logs based on the template, if a user has modified the parameters in
Query Event Log Statistics window to revoke the template modification.
Procedure
1 Choose Fault > Query Event Log Statistics from the main menu.

2 In the Statistic Filter dialog box, set the statistical conditions of event logs, and then click
OK.
3 In Query Alarm Log Statistics window, you can perform the following operations.
Task Operations
Display statistical results in Click the Table tab at the lower left corner, and then expand
a table the collapsed items in the statistical result table to view all
statistics.
Display statistical results in Click the Pie tab at the lower left corner, and then click a tab
a pie chart named a statistical item at the upper left corner to view the
statistics based on this statistical item.
Open a statistical template 1. Click Template, and then click Open.

2. Select one template in the Choose window, and then click
OK.
Re-set the statistical 1. Click Statistic Filter.
conditions 2. In the Statistic Filter dialog box, set the statistical
conditions of alarm logs, and then click OK.
Refresh statistical results Click Refresh.

Task Operations
Save statistical results 1. Click Save As.
2. In the Save dialog box, select the path for saving records,
and then click Save.
Print statistical results 1. Click Print.
2. In the Print dialog box, set the print parameters, and then
click Print.
----End
7.9 Handling Alarms

After you receive an alarm, you need to handle it. The procedure for handling an alarm include
viewing the alarm details, acknowledging the alarm, identifying the alarm, and clearing the
alarm.

7.9.2 Locating an Alarm Through a Fault Object
The NMS provides multiple functions of jumping to the alarm browsing window through a fault
object. The functions help to view the alarms of the object quickly.
7.9.3 Collecting the Fault Information
You can collect the information about some routers, such as NE40E, NE80E, and NE5000E by
collection items. The collected NE information can be used as a reference for troubleshooting.
There are default and customized collection items.
7.9.4 Viewing Alarm Details
By querying alarm details, you can view the information such as the alarm name, alarm cause,
solution, and fault location. In the Details dialog box, you can add or modify alarm experience
that you can refer to when similar alarms occur in the future.
7.9.5 Checking Alarms
When you check the alarm, you are comparing one or more uncleared alarms on the U2000 with
7.9.6 Acknowledging an Alarm
Alarm acknowledgement indicates that an alarm has been handled and do not require much
attention.
7.9.7 Locating Objects Where Alarms Occur
When you query alarms/events in the topology view or through a menu, you can use the locating
function of topology to identify the NE that raises an alarm/event based on the alarm/event
record.
7.9.8 Locating an Object Through an Alarm
Through the alarm locating function, you can locate the object that generates the concerned
alarm.

7.9.9 Clearing an Alarm Manually

If an alarm cannot be cleared automatically or does not exist on an NE, You can manually clear
the alarm. After the alarm is cleared, the U2000 considers that the fault that causes the alarm is
rectified.
7.9.10 Masking Alarm
Masking alarm refers to that the alarms that are set to be masked are not reported to the NMS
any more or the U2000 does not monitor unimportant alarms . During the device maintenance,
test, or deployment, the device may report numerous alarms. In this case, you can set the alarm
mask conditions to mask the alarms or events that meet the conditions. The mask alarms are not
displayed or saved. You can also mask unimportant U2000 alarms so that the U2000 does not
monitor these alarms. This operation helps fault location. After the alarm mask is set for a
selected alarm, the same alarms that are reported later can be masked in a fast manner.
7.9.11 Masking All NE Interface Alarms Quickly
During network O&M, a large number of networkwide subinterface alarms and FE interface
alarms are generated on NEs when a daily service is provisioned. Therefore, you need to mask
these alarms because they are not concerned by users. The U2000 provides the function of
masking NE interface alarms, which facilitates the operation of quickly masking subinterface
alarms and FE interface alarms on certain NEs on the U2000.
7.9.12 Suppressing Alarms
Suppressing alarms refers to that the alarms that are set to be suppressed are not reported from
NEs any more. The alarms can be generated from network NEs, or a particular NE or board, or
even from a particular functional module on a certain board.
7.9.13 Recording Alarm/Event Maintenance Experience
You can record alarm/event maintenance experience to the experience base. Thus, when a similar
alarm/event occurs, you can consult the database to handle it.
7.9.14 Exporting Alarm/Event Maintenance Experience
By using the function of exporting alarm/event maintenance experience, you can export alarm/
event maintenance experience on the U2000 to a file. This facilitates you to view alarm/event
maintenance experience in the file. If the file format is XML, you can use the file for backup
and restoration or synchronization to another server.
7.9.15 Importing Alarm/Event Maintenance Experience
By using the function of importing alarm/event maintenance experience, you can import the
exported alarm/event maintenance experience to the U2000.
7.9.16 Example of Alarm Handling
This topic takes a high disk usage alarm as an example to describe the procedure and method
for handling an alarm. You can know the basic procedure and operations of alarm handling from
this example.

Procedure Chart
Figure 7-11 shows the alarm handling procedure.

Figure 7-11 Procedure for handling an alarm
Procedure Description
Figure 7-11 lists the procedure for handling an alarm.

Table 7-9 Procedure for handling an alarm

Step Operation Description
1 Receive an alarm Follow the alarm handling procedure after you receive an
alarm. To ensure that you are notified in time after an alarm
occurs, you need to set alarm notification methods on the
U2000.
2 View the alarm details View the alarm details, including the alarm location, alarm
help, and alarm maintenance experience after an alarm
occurs.
3 Acknowledge the Acknowledge the alarm to avoid others from handling the
alarm same alarm. After you acknowledge the alarm, it indicates
that the alarm has been handled.
4 Collect the fault Identify the alarm and query the alarm information to find
information out the symptom of the alarm.
5 Analyze the causes of Analyze the causes for the alarm based on the alarm
the alarm symptom.
6 Work out the fault Work out the fault handling scheme according to the alarm
handling scheme details, device manuals, network status, and maintenance
experience.
7 Carry out the fault Carry out the fault handling scheme to rectify the fault that
handling scheme leads to the alarm.
8 Clear the alarm Clear the conditions that cause the alarm. After the alarm is
cleared, the U2000 receives a clearance alarm.
9 Check whether the Check the handling results after you rectify the fault.
fault is rectified
10 Record the Record the maintenance experience when the alarm

maintenance handling is complete.
experience
7.9.2 Locating an Alarm Through a Fault Object

The NMS provides multiple functions of jumping to the alarm browsing window through a fault
object. The functions help to view the alarms of the object quickly.
Procedure
1 In the Workbench window, double-click the icon.

2 On the Main Topology tab page, double-click a fault object to display the NE Panel window.
Then, you can view the related faulty objects, as shown in the following figure.

3 Select the required faulty port or panel, right-click, and then choose View Alarm or Browse
Current Alarms to view the alarm details.
----End
7.9.3 Collecting the Fault Information

You can collect the information about some routers, such as NE40E, NE80E, and NE5000E by
collection items. The collected NE information can be used as a reference for troubleshooting.
There are default and customized collection items.
7.9.3.1 Viewing the Alarm Information

In the Collect Fault Information window, you can view the details of an alarm, including the
cause and handling suggestion of the alarm.
7.9.3.2 Creating a Collection Item
By creating a collection item, you can set the equipment information to be viewed during
troubleshooting as a template. In this way, faults can be located easily.
7.9.3.3 Obtaining the Equipment Information
By running a collection item or command lines, you can obtain the equipment information, which
can be used as a reference during troubleshooting.
7.9.3.1 Viewing the Alarm Information

In the Collect Fault Information window, you can view the details of an alarm, including the
cause and handling suggestion of the alarm.
Prerequisite
Only some of the routers, such as NE40E, NE80E, and NE5000E, support this operation.
Procedure
NOTE
l If you set the default template, you need to click Filter to display the Filter dialog box.
3 Select an alarm to be viewed, right-click, and choose Collect Fault Information from shortcut
menu.
On the left-hand of Alarm Information area in the window that is displayed, the details of the
alarm are displayed, including General, Alarm Cause, and Recovery Suggestion.
----End
7.9.3.2 Creating a Collection Item

By creating a collection item, you can set the equipment information to be viewed during
troubleshooting as a template. In this way, faults can be located easily.

Prerequisite
Only some of the routers, such as NE40E, NE80E, and NE5000E, support this operation.
Procedure
NOTE
3 Select an alarm to be viewed, right-click, and choose Collect Fault Information from the
shortcut menu.
4 In the Collection Item List area of the window that is displayed, right-click, and choose
Manage from the shortcut menu.
5 In the dialog box that is displayed, click Create. Alternatively, you can right-click and choose
Create from the shortcut menu.
6 In the dialog box that is displayed, set the parameters of the collection item.
NOTE
For a new collection item, you can enter only the commands related to display in the Command Line
field.
8 Click Close.
----End
7.9.3.3 Obtaining the Equipment Information

By running a collection item or command lines, you can obtain the equipment information, which
can be used as a reference during troubleshooting.
Prerequisite
Only some of the routers, such as NE40E, NE80E, and NE5000E support this operation.
Context
You can obtain the equipment information in the following two modes:
l Run the collection item in Collection Item List.

Collection items are divided into the following two types:
– Default collection item: The system predefines different collection items according to
different alarms and equipment that generates the alarms.

– Customized collection item: You can customize the concerned equipment information.
For details of how to customize a collection item, see 7.9.3.2 Creating a Collection
Item.
l In the Enter Command Line field on the Default tab page, enter commands and then run
the commands.
Procedure
NOTE
3 Select an alarm to be viewed, right-click, and choose Collect Fault Information from the
shortcut menu.
4 You can run the collection item or command lines to obtain the equipment information.
l In the Collection Item List area of the window that is displayed, select one or more collection
items and click Execute. Alternatively, you can select one or more collection items, right-
click, and choose Execute from shortcut menu.
NOTE
l In the case of certain default collection items, you need to manually set the Command Line and
Check Criteria parameters.
l In the case of the collection item whose Check Criteria is set, related suggestions are provided in
Check Results.
l In the Enter Command Line field on the Default tab page, enter commands and then click
Run.
In the details area on the Default tab page, the result of running the commands are displayed.
NOTE
When you run multiple commands, up to 20,000 results of running the commands accumulated. When
there are more than 20,000 results, the earliest results are deleted, and a maximum of 20,000 results
are displayed on the tab page.
----End
7.9.4 Viewing Alarm Details

By querying alarm details, you can view the information such as the alarm name, alarm cause,
solution, and fault location. In the Details dialog box, you can add or modify alarm experience
that you can refer to when similar alarms occur in the future.
Procedure
Logs, Fault > Browse Current Alarm by Severity, Fault > Browse Current Alarm by
Status or Fault > Browse History Alarm from the main menu. In the Filter dialog box, set the
alarm query conditions. Click OK. In the query window, right-click an alarm and choose
Details.

NOTE
2 In the Details dialog box, click on the left of Alarm Experience, and then click Modify. In
the Experience dialog box, enter the alarm maintenance experience. Then click OK.
3 In the Details dialog box, click Close.
NOTE
You can click Previous to view the details of the previous alarm record, or click Next to view the details
of the next alarm record.
----End
7.9.5 Checking Alarms

When you check the alarm, you are comparing one or more uncleared alarms on the U2000 with
Prerequisite

l The alarm check function is applicable to the MSTP, WDM, NA WDM, RTN, PTN, Marine
series NEs.
Procedure
1 Choose Fault > Browse Current Alarm or Fault > Browse Alarm Logs from the main
menu, or click on the toolbar.
NOTE
l Only the uncleared alarms can be checked.

l If the startup template for browsing the current alarms is set, the Filter dialog box is not displayed.
Instead, the alarms that meet the filter conditions set in the startup template are displayed directly.
3 Select one or more alarms, right-click, and choose Check.
----End
7.9.6 Acknowledging an Alarm

Alarm acknowledgement indicates that an alarm has been handled and do not require much
attention.
Context
If you need to focus on the alarm again, you can right-click the alarm and choose
Unacknowledge to restore the alarm state to unacknowledged.

Procedure
NOTE
3 In the Browse Current Alarm window, choose one or more alarms, and then click
Acknowledge.
----End
7.9.7 Locating Objects Where Alarms Occur

When you query alarms/events in the topology view or through a menu, you can use the locating
function of topology to identify the NE that raises an alarm/event based on the alarm/event
record.
Context
The locating function of topology is applicable for one alarm/event at a time.
Procedure
l In the Main Topology window, click on the toolbar. At the bottom of the alarms/events
browse area, right-click an alarm/event and choose Locate in Topology.
The NE that raises the alarm/event is identified on the client.
dialog box, set the alarm query conditions. Click OK. In the query window, right-click an
alarm/event record and choose Locate in Topology.
The NE that raises the alarm/event is identified on the client.
----End
7.9.8 Locating an Object Through an Alarm

Through the alarm locating function, you can locate the object that generates the concerned
alarm.
Procedure
1 Choose Fault > Browse Current Alarm, Fault > Browse Alarm Logs, Fault > Browse
Current Alarm by Severity or Fault > Browse Current Alarm by Status from the main
menu.
2 In the dialog box that is displayed, set the alarm filtering criteria, and click OK, as shown in the
following figure.

NOTE
3 Select a concerned alarm, right-click, and then choose Locating to NE Panel.

NOTE
Only the alarms that are related to the hardware can be located on the NE panel.
4 On the NE Explorer tab page, the faulty port is displayed in the NE panel. See the following
figure.
----End
7.9.9 Clearing an Alarm Manually

If an alarm cannot be cleared automatically or does not exist on an NE, You can manually clear
the alarm. After the alarm is cleared, the U2000 considers that the fault that causes the alarm is
rectified.
Context
An alarm correspond to a clearance alarm. If a device is faulty, an alarm is reported to the
U2000. After the fault is rectified, the clearance alarm is reported to the U2000. This indicates
that the alarm is cleared automatically.
Procedure

NOTE
3 In the Browse Current Alarm window, choose one or more alarms, and then click Clear.
----End
7.9.10 Masking Alarm

Masking alarm refers to that the alarms that are set to be masked are not reported to the NMS
any more or the U2000 does not monitor unimportant alarms . During the device maintenance,
test, or deployment, the device may report numerous alarms. In this case, you can set the alarm
mask conditions to mask the alarms or events that meet the conditions. The mask alarms are not
displayed or saved. You can also mask unimportant U2000 alarms so that the U2000 does not
monitor these alarms. This operation helps fault location. After the alarm mask is set for a
selected alarm, the same alarms that are reported later can be masked in a fast manner.
Prerequisite
You must be a U2000 user with common fault operator rights or higher.
Context
l The function of masking alarms or events does not take effect for the alarms or events that
are already reported. That is, after you set a masking policy, only the newly reported alarms
that meet the mask conditions are masked.
l A new masking policy is displayed in the Mask Rule dialog box. The same alarms that are
reported later continue to be masked.
l If you need to receive the masked alarms again, choose Fault > Settings > Mask Rule
from the main menu. In the Mask Rule dialog box, select the required masking policy, and
deselect the Enable check box or delete the policy.
Procedure
Logs, Fault > Browse Current Alarm by Severity or Fault > Browse Current Alarm by
Status from the main menu.

NOTE
3 Select an alarm or event from the alarm or event browse window, right-click, and then choose
Mask.
4 In the Mask dialog box that is displayed, you can set the Mask Scope and Effect Time according
the requirements.

5 In the Mask dialog box, click OK.
6 In the Confirm dialog box that is displayed, click OK.
----End
7.9.11 Masking All NE Interface Alarms Quickly

During network O&M, a large number of networkwide subinterface alarms and FE interface
alarms are generated on NEs when a daily service is provisioned. Therefore, you need to mask
these alarms because they are not concerned by users. The U2000 provides the function of
masking NE interface alarms, which facilitates the operation of quickly masking subinterface
alarms and FE interface alarms on certain NEs on the U2000.
Prerequisite
It is applicable to Router series, Switch series, Security series NEs.
Procedure
1 Choose Fault > Settings > Mask Ne Interface Alarm from the main menu.
2 The Mask Ne Interface Alarm window is displayed.
3 Click the Mask Alarm of NE Subinterface tab. In the Object Tree, select the NE on which the
subinterface alarms need to be masked.
4 Click the Mask Alarm of NE FE Subinterface tab. In the Object Tree, select the NE on which
the FE interface alarms need to be masked.
5 Click OK.
----End


Suppressing alarms refers to that the alarms that are set to be suppressed are not reported from
NEs any more. The alarms can be generated from network NEs, or a particular NE or board, or
even from a particular functional module on a certain board.
Prerequisite
l You must be a U2000 user with common fault operator rights or higher.
l The alarm suppression function is supported by the MSTP, WDM, NA WDM, RTN, PTN,
Marine series NEs only.
Context
In the case of the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, if you need to
receive the suppressed alarms again from an NE, select the NE on the Main Topology, right-
click, and then choose NE Explorer from the shortcut menu. On the right-hand Function
Tree, expand Alarm > Alarm Suppression branches, select the required alarm event, and then
set Status to Not Suppressed.
Procedure
2 In the Filter dialog box, set filter criteria and click OK.
NOTE
l Alternatively, click Copy from Template. In the dialog box that is displayed, select an existing profile,
and then click OK to add the filtering criteria of the selected profile to the Filter dialog box.
l If you already set the startup template for the current alarms, the alarms that meet the startup template
criteria are directly displayed, without the displaying of the Filter dialog box.
3 Select an alarm from the Current Alarms window, right-click, and then choose Suppress NE
Alarm.
4 In the prompt that is displayed, click Yes.
5 In the dialog box that is displayed, click Close.
----End
Result
l After the alarm suppression is set successfully for an alarm, NEs do not report this alarm
any more.
l After the alarm suppression is set successfully for an alarm, the alarm that has been reported
is cleared.
7.9.13 Recording Alarm/Event Maintenance Experience

You can record alarm/event maintenance experience to the experience base. Thus, when a similar
alarm/event occurs, you can consult the database to handle it.

Context
The initial experience base is empty.
Procedure
1 Choose Fault > Settings > Experience from the main menu.
2 In the Experience window, click Range, specify a search range in the Search Range dialog
box, and click OK. Enter an alarm/event name in the Filter by name text box or enter the key
word of the maintenance base, and press Enter.
In the Alarm/Event Name navigation tree, alarm/event names with the keyword are listed.
3 In the Alarm/Event Name navigation tree, select an alarm/event name, and then click
Modify.
NOTE
l Click to collapse all objects.
l Click one or multiple icons from , , , and to classify alarms/events and increase the speed
of locating alarm/event names in the navigation tree.
4 In the Experience dialog box, enter alarm/event maintenance experience. Click OK.
----End
7.9.14 Exporting Alarm/Event Maintenance Experience

By using the function of exporting alarm/event maintenance experience, you can export alarm/
event maintenance experience on the U2000 to a file. This facilitates you to view alarm/event
maintenance experience in the file. If the file format is XML, you can use the file for backup
and restoration or synchronization to another server.

Context
l Alarm/event experience can only be exported to XML, TXT, HTML, CSV, XLS, or PDF
files. A file can be imported back to the U2000 only when the file format is XML.
l Modifying the XML export files may damage these files. As a result, these files cannot be
imported back to the U2000.
Procedure
2 In the Experience window, click Export.
3 In the Export Experience dialog box, click the icon.
4 In the Export dialog box, set the path, file name, and file type for the export file. Then click
OK.
5 In the Export Experience dialog box, select Export all or Export by NE type, and click
Export.
----End
7.9.15 Importing Alarm/Event Maintenance Experience

By using the function of importing alarm/event maintenance experience, you can import the
exported alarm/event maintenance experience to the U2000.
Context
l Only the files in the XML format can be imported to the alarm/event experience base.
l Modifying the XML export files may damage these files. As a result, these files cannot be
imported back to the U2000.
Procedure
2 In the Experience window, click Import.

3 In the Import Experience dialog box, click .

4 In the Open dialog box, select the target file, and then click Open.
5 In the Import Experience dialog box, select Add or Update, and then click Import.
----End
7.9.16 Example of Alarm Handling

This topic takes a high disk usage alarm as an example to describe the procedure and method
for handling an alarm. You can know the basic procedure and operations of alarm handling from
this example.
Background
Administrator A finds that the U2000 receives a new alarm.
Operation Guide
Based on the Alarm Handling Procedure, administrator A needs to take the following actions:
1. Receive an alarm.
On the client, choose Fault > Browse Current Alarm from the main menu to browse the
current alarm. The high disk usage alarm exists alarm exists in the list.
2. View the alarm details.
Double-click the high disk usage alarm, and then view its details in the Details dialog box.
3. Acknowledge the alarm.
According to the alarm details, rectify the fault that leads to the alarm. After that, in the
current alarm, right-click this alarm and choose Acknowledge. In the Configuration dialog
box, click OK to acknowledge the alarm.
4. Work out the alarm handling scheme.
According to the handling suggestions and maintenance experience in the alarm details as
well as the running status of the U2000, administrator A determines to delete the redundant
files and back up the export files to other disks.
5. Rectify the fault.

Delete the redundant files of the U2000. Back up the export files to other disks. Then delete
the export files from the source disk. Thus, the U2000 server has more available disk space.
6. Check the handling result.
Choose Fault > Browse Current Alarm from the main menu to browse the current
alarm. The state of the alarm is changed from uncleared to cleared.
7. Record the alarm handling experience.
Choose Fault > Settings > Experience from the main menu. In the Experience window,
search for the alarm name and then modify the maintenance experience.
7.10 Setting the Alarm Auto Processing

You can set an auto processing policy to enable the U2000 to process the alarms that match the
preset conditions. This helps to improve the work efficiency.
7.10.1 Automatic Alarm/Event Processing Policy

After you set an automatic alarm processing policy, the U2000 automatically processes the
alarms that match the preset conditions. This improves the alarm/event processing efficiency on
the U2000.
7.10.2 Setting an Automatic Alarm Acknowledgement Rule
For the purpose of maintenance, the U2000 supports automatic acknowledgement by severity
and by rule for unacknowledged and cleared alarms.
7.10.4 Setting an Alarm/Event Redefinition Rule
On the U2000, you can redefine the names, types, severities of alarms/events that the U2000
receives from NEs according to actual requirements. For example, you can decrease the
severities of the alarms/events that do not require attention and increase the severities of the
alarms/events that require attention.
7.10.5 Setting an Alarm/Event Mask Rule
You can set a mask rule on the U2000 to discard the unconcerned alarms or events reported to
the U2000. In this case, these alarms or events are not saved on the U2000 alarm database.
7.10.6 Setting an Alarm/Event Postprocessing Rule
You can set an alarm/event postprocessing rule on the U2000. Thus, when an alarm or an event
is raised, the U2000 runs the specified command automatically.
7.10.7 Setting Conversion from an Events to an ADMC Alarm
You can convert an event to an automatically detected and manually cleared (ADMC) alarm
and display the alarm in the current alarm to draw more attention to the event.
7.10.8 Setting the Lifecycle of the Current Alarm
You can set the period when cleared and acknowledged alarms are stored in the current alarm.
7.10.1 Automatic Alarm/Event Processing Policy

After you set an automatic alarm processing policy, the U2000 automatically processes the
alarms that match the preset conditions. This improves the alarm/event processing efficiency on
the U2000.

The automatic processing policy includes:

l Alarm/event mask
If certain alarms/events are unnecessary or do not require attention, you can set a mask rule.
Thus, the U2000 masks them and leaves only the concerned alarms/events. For example,
when a device is under maintenance or test, a large number of alarms/events are raised.
These alarms/events are necessary, and you can mask them.
l Alarm/event redefinition
You can redefine the names, severities, and types of alarms or events on the U2000
according to actual requirements. For example, you can decrease the severity of the alarms
that does not require attention, and increase the severity of the alarms that require attention.
l Alarm postprocessing
You can set the alarm postprocessing policy. The U2000 then processes the alarms that
match the preset conditions based on the policy.
l Automatic alarm acknowledgement
After the fault that leads to an alarm is rectified, you can set the automatic acknowledgement
condition. Thus, the U2000 automatically acknowledges the alarm based on the condition.
l Conversion from an event to an ADMC alarm
You can convert an event to an Auto Detected Manual Cleared (ADMC) alarm and display
the alarm in the current alarm to draw more attention to the event.
l Lifecycle of the current alarm
If the larger between the acknowledgement time and clearance time of an Auto Detected
Auto Cleared (ADAC) alarm exceeds the preset value or the acknowledgement time of the
ADMC alarm exceeds the preset value, the alarm record is deleted from the current
alarm.
7.10.2 Setting an Automatic Alarm Acknowledgement Rule

For the purpose of maintenance, the U2000 supports automatic acknowledgement by severity
and by rule for unacknowledged and cleared alarms.
Procedure
2 In the Alarm Option dialog box, select Auto Acknowledge from the navigation tree on the left.

NOTE
3 In the Auto Acknowledge group box, set an automatic alarm acknowledgement rule.
Setting an Automatic Alarm Operations

Acknowledgement Rule
Setting automatic 1. Select Auto acknowledge by severity.
acknowledgement by severity 2. Set acknowledgement for each severity and then set
the delay acknowledgement time.
3. Click OK.
Setting automatic 1. Choose Auto acknowledge by rule.
acknowledgement by rule 2. Click Add.
3. In the Add Acknowledgement Rule dialog box, set
the acknowledgement condition, acknowledgement
mode, memo, and enable/disable state, and then click
OK.
4. Set the execution start time and duration.
5. Click OK.
----End


Prerequisite
The security equipment of the Eudemon, USG, SIG, SVN ,SRG and EGW series does not support
the function of synchronizing the networkwide current alarms.
Procedure
2 In the Alarm Option dialog box, in the navigation tree on the left, select Auto Synchronize.
In the dialog box that is displayed, set the alarm synchronization parameters.
l Synchronize all alarms at NMS start indicates that the U2000 automatically synchronizes
the alarms with those on all the NEs when it is started.
l Synchronize device alarms after recovery from a communication interruption
indicates that the U2000 automatically synchronizes the alarms with those on a specific
NE when it resumes the communication with the NE.
l After LCT user logout indicates that the U2000 automatically synchronizes the alarms
with those on a specific NE when the LCT user logs out.
NOTE
The After LCT user logout parameter is available only when you select the Transmit Common
component during the installation of the U2000.
3 Click OK.
----End
7.10.4 Setting an Alarm/Event Redefinition Rule

On the U2000, you can redefine the names, types, severities of alarms/events that the U2000
receives from NEs according to actual requirements. For example, you can decrease the
severities of the alarms/events that do not require attention and increase the severities of the
alarms/events that require attention.
Context
l The redefinition rule takes effect for only the alarms reported during the validity period of
the redefinition rule.
l The query and statistical results are displayed based on alarm/event redefinition.
l The redefinition of alarm/event names takes effect for all NEs. It cannot take effect for only
the specified NEs. The redefinition of types and severities can take effect for either the
specified NEs or all NEs.
l In redefinition setting, the validity period takes effect for only the redefinition of types and
severities and does not take effect for the redefinition of names. The validity period is
subject to the server time.

Procedure
1 Choose Fault > Settings > Redefine from the main menu.
2 In the Redefine window, set an alarm/event redefinition rule.
Setting a Redefinition Rule Operations

Adding an alarm/event 1. Click Add.
redefinition rule
2. In the Add Redefinition Rule dialog box, click next
to Name in the Alarm/Event Original Setting group box
to set the original alarm/event .
3. Change the name, the type and the severity of the alarm
as required. Then, set the validity period for the type and
severity redefinition.
4. In the Memo text box, enter the remarks.
5. Select the Enable check box.
6. Select the Alarm/Event Source tab to set the alarm/event
source.
7. In the Add Redefinition Rule dialog box, click OK.
Modifying an alarm/event 1. Select a rule, and then click Property.
redefinition rule 2. In the Property dialog box, modify the parameters
settings.
NOTE
l You can also select a rule, and then double-click the relevant
field to modify the parameters settings.
l The fields displayed in white can be changed. The fields
displayed in cannot be changed. The fields displayed
in are already changed but are not used.
3. Click OK.
Deleting an alarm/event 1. Select the rule you want to delete. Click Delete.
redefinition rule NOTE
You can choose more than one record by using Shift or Ctrl.
----End

7.10.5 Setting an Alarm/Event Mask Rule

You can set a mask rule on the U2000 to discard the unconcerned alarms or events reported to
the U2000. In this case, these alarms or events are not saved on the U2000 alarm database.
Context
l The mask rule takes effect only for the alarms reported in the validity period after the mask
rule is enabled. The mask rule does not take effect for the alarms reported before the mask
rule is set.
l If both the alarm/event redefinition and alarm mask rule are set for an alarm/event, the
alarm/event is masked first and then redefined. Therefore, the alarm/event is masked based
on the original attributes (the attributes before redefinition) of the alarm/event.
Procedure
1 Choose Fault > Settings > Mask Rule from the main menu.
2 In the Mask Rule window, set an alarm/event mask rule.
Setting a Mask Rule Operations

Adding an alarm/event mask 1. Click Add. Choose Alarm Mask Rule or Event Mask
rule Rule.
2. In the Add Alarm Mask Rule or Add Event Mask
Rule dialog box, set the mask conditions, time mode, and
other parameters, and then click Enable the mask rule.
3. Click Finish.
mask rule 2. In the Property dialog box, modify the parameters
settings.
NOTE
3. Click OK.

Setting a Mask Rule Operations

mask rule NOTE
----End
7.10.6 Setting an Alarm/Event Postprocessing Rule

You can set an alarm/event postprocessing rule on the U2000. Thus, when an alarm or an event
is raised, the U2000 runs the specified command automatically.
Context
l Running commands rashly may have a negative impact on the system. The following types
of alarm/event postprocessing commands are prohibited: infinite-loop commands and GUI
commands. The postprocessing script can start and stop automatically. You are
recommended to test the script before you use them. For the example of the postprocessing
script, see An Instance of the Alarm or Event Postprocessing Script.
l The procedure for setting an alarm postprocessing rule are the same as that for setting an
event postprocessing rule. The following example describes how to set an alarm
postprocessing rule.
Procedure
1 Choose Fault > Settings > Postprocessing from the main menu.
2 In the Alarm/Event Postprocessing window, click Add, and then choose Alarm
Postprocessing Rule.
3 On the Basic Setting tab of the Add Postprocessing Rule dialog box, set the parameters such
as Alarm name, Severity, and Type.
4 Click the Alarm Source tab. On the Alarm Source tab, set the alarm source. Click Next.
5 In the Add Postprocessing Rule dialog box, set the Postprocessing Action , Start Time, End
Time, and Memo. Select Enable.
NOTE
The name of the script in Postprocessing Action Settings can be in the format script name+parameters.
The script must meet the following requirements:
l The script exists in bin/fm/action in the installation directory of the U2000 server in Solaris or Linux.
The file format of the script is *.sh. If there is an output file, it exists in etc/conf in the installation
directory of the U2000 server.
l The script exists in bin\fm\action in the installation directory of the U2000 server in Windows. The
file format of the script is *.cmd. If there is an output file, it exists in etc\conf in the installation directory
of the U2000 server.
l The syntax of the script is correct, and the script is executable.
6 Click Finish.
----End

7.10.7 Setting Conversion from an Events to an ADMC Alarm

You can convert an event to an automatically detected and manually cleared (ADMC) alarm
and display the alarm in the current alarm to draw more attention to the event.
Context
l An ADMC alarm is defined with a specific fault generation condition but without a fault
rectification condition. When the fault generation condition is met, an alarm occurs, but a
clearance alarm does not occur. The maintenance personnel needs to check whether the
fault is already rectified. If the fault is already rectified, the maintenance personnel needs
to clear the alarm manually.
l After you set conversion from an event to an ADMC alarm, the alarm is displayed only in
the current alarm. After you cancel the setting, the alarm is not displayed in the current
alarm.
Procedure
1 Choose Fault > Settings > Set Events as ADMC Alarms from the main menu.
2 In the Set Event as ADMC Alarms dialog box, select an event from Available Event and move
it to Selected Event.
NOTE
l To query an event, you can enter the event name in Filter by name on the top of Available Event or
Selected Event, and press Enter.
l To collapse the navigation tree, click .
l To group object names by group ID in the navigation tree, click .
l To group event names by alarm severity in the navigation tree, click .
l To group event names by alarm type in the navigation tree, click .

3 Click OK.
----End
7.10.8 Setting the Lifecycle of the Current Alarm

You can set the period when cleared and acknowledged alarms are stored in the current alarm.
Context
If the larger between the acknowledgement time and clearance time of an automatically detected
and automatically cleared (ADAC) alarm exceeds the preset value or the acknowledgement time
of the ADMC alarm exceeds the preset value, the alarm record is deleted from the current
alarm.
Procedure
2 In the Alarm Option dialog box, select Lifecycle in the navigation tree on the left.
3 In the Lifecycle group box, set the period when cleared and acknowledged alarms are stored in
the current alarm.
4 Click OK.
----End
7.11 Setting Audible and Visual Alarm Notification

The U2000 can select different sounds and colors for the alarms and abnormal events of different
severities based on customized settings, to facilitate maintenance.
7.11.1 Setting the Alarm Sound
You can set the alarm sound for each alarm severity, state or alarm name. When an alarm is
raised, the sound box connected to the client plays the sound.
clearly.

7.11.3 Setting the Alarm Panel

By setting the alarm panel, you can enable the alarm panel to pop up automatically and the alarm
indicator to blink when an alarm is raised. The alarm panel can also display the alarm information
in the bound current alarm template.
7.11.4 Setting Audible and Visual Alarm Indication in the Alarm Box
The alarm box plays different sounds and enables the indicators to display different colors
according to the severity level of the NE alarms. You can enable or disable the audible and visual
alarms by using the U2000.
7.11.5 Clearing the Audible and Visual Alarm Indication of an NE Cabinet Temporarily
When an alarm is raised from an NE, the NE cabinet displays different visual alarms and
generates different audible alarms according to the alarm severities. You can clear these audible
and visual alarms by using the U2000.
7.11.6 Clearing the Audible and Visual Alarm Indication of an NE Cabinet Permanently
When an alarm is generated on an NE, the NE displays different audible and visual alarm
notifications according to the alarm levels. By disabling alarm sound and alarm indicator on the
U2000, all the audible and visual alarm notifications on the NE are closed permanently unless
you enable the alarm sound and alarm indicator again on the U2000.
already viewed.
and other windows.
7.11.1 Setting the Alarm Sound

You can set the alarm sound for each alarm severity, state or alarm name. When an alarm is
raised, the sound box connected to the client plays the sound.
Context
l You can use the sound file of the U2000. You can also use the customized sound file.
l The sound files of the WAV type can be recorded in two formats: PCM and Microsoft
ADPCM. Only the sound files of the WAV type in the PCM format are supported.
l The sound files of the four alarm severities are located in client\plugins\alarmclientbase
\style\conf\ in the U2000 client installation folder. The file names are Critical.wav,
Major.wav, Minor.wav and Warning.wav.

Procedure
2 In the Preferences dialog box, choose Sound Setting in the navigation tree on the left.
NOTE
3 You can perform the following operations on each row in the Sound Setting area:
NOTE
You can click Default to restore the alarm sound to the default.
1. Select proper check boxes under Sound.
2. Click the path of sound files and then click on the right. In the Choose Sound File
dialog box, select a sound file, and then click Open.
3. Click the play time, and then click the fine tune button to set the duration of alarm sound.
NOTE
l The play time ranges from 0 to 1000, in the unit of second. 0 indicates that the play time is
unlimited.
l If you enable automatic blinking of alarm indicators on the alarm panel, when an alarm is
generated, the alarm indicator corresponding to this alarm blinks for the preset duration. If alarms
of different severities are raised, only the alarm indicator corresponding to the highest alarm
severity blinks.
l If you set the play time of the alarm sound of an alarm severity to 0, when an alarm of this severity
is generated, the alarm indicator keeps blinking until the alarm is cleared.
4. Click to listen to the sound. Click to stop the sound.

5. In the lower part of this area, select the sound state.
NOTE
To set Sound by alarm name, click . In the Select Alarm dialog box, select an
alarm name, and then click OK.

4 Click OK.
----End

clearly.
Context
After setting, the alarm icon in the topology view, the alarm record you have queried, and the
alarm indicator on the alarm panel are shown in the specified colors.
Procedure
2 In the Preferences dialog box, choose Color Setting in the navigation tree on the left.
NOTE
3 In the Color Setting group box, click in each row to select prompt colors of alarms.
NOTE
You can click Default in the Preferences dialog box to restore a color to the default.
4 Click OK.
----End
7.11.3 Setting the Alarm Panel

By setting the alarm panel, you can enable the alarm panel to pop up automatically and the alarm
indicator to blink when an alarm is raised. The alarm panel can also display the alarm information
in the bound current alarm template.

Procedure
1 Choose Fault > Display Alarm Board from the main menu or click on the toolbar.
NOTE
2 In the Alarm Panel dialog box, click Option, and then set whether to display alarm panel after
startup and, whether to pop up or flash on reception a alarm.
3 In the Alarm Panel dialog box, click Add.
NOTE
You can select a template except All objects in the Alarm Panel dialog box, and then click Delete to delete
the template.
4 In the Choose dialog box, select one or more current alarm templates. Then click OK.
NOTE
If you select Show current user template, the dialog box displays only the template created by yourself.
5 Set the alarm panel.
Set the Alarm Panel Operation

Select an option 1. In the Alarm Panel dialog box, click Option.
2. Select Display alarm panel after startup, Pops up on
reception an alarm, or Flash on receiving an alarm.

Set the Alarm Panel Operation

Add/Delete a template 1. In the Alarm Panel dialog box, click Add.
NOTE
In the Alarm Panel dialog box, you can select a template except
All Object, and then click Delete to delete the template.
2. In the Choose dialog box, select one or more Current
alarm templates, and then click OK.
NOTE
If you select Display the templates created by the current user
only, the dialog box displays only the template created by the
current user.
Set an alarm indicator 1. In the Alarm Panel dialog box, right-click a template and
display template choose Show on alarm lamp.
NOTE
The template with the icon is the alarm indicator display

template that you set.
You are not allowed to select the template with the icon.
NOTE
The alarm indicator on the right of the toolbar counts alarms of
all severities according to the filtering conditions defined in the
template.
----End
7.11.4 Setting Audible and Visual Alarm Indication in the Alarm

Box
The alarm box plays different sounds and enables the indicators to display different colors
according to the severity level of the NE alarms. You can enable or disable the audible and visual
alarms by using the U2000.
Prerequisite
You must be an NM user with "Fault Watcher" authority or higher.
Context
l If several clients of the same version are running on a host, you need only to set the alarm
box on the first client.
l For the U2000 to control the alarm box, you need to correctly set the communication
parameters of the alarm box in the Communication Parameters tab, and enable the alarm
box.
l The alarm box beeps in two ways. In the case of a critical and major alarm, the alarm box
keeps beeping until it is manually stopped or until the alarm is cleared. In the case of a
minor and warning/not alarmed alarm, the alarm box beeps for a fixed time period (one
minute) and stops. It can also be manually stopped.

Procedure
2 In the Alarm Option dialog box, choose Alarm Box from the navigation tree in the left pane.
3 In the Alarm Box group box, set By severity or By template.
4 Select the serial port that communicates with the alarm box, and then select the Enable alarm
box check box.
5 Click OK.
----End
7.11.5 Clearing the Audible and Visual Alarm Indication of an NE

Cabinet Temporarily
When an alarm is raised from an NE, the NE cabinet displays different visual alarms and
generates different audible alarms according to the alarm severities. You can clear these audible
and visual alarms by using the U2000.
Prerequisite

Procedure
1 Right-click an NE on the Main Topology and choose Clear Alarm Indication from the shortcut
menu.
The Operation Result dialog box is displayed.
2 Click Close.
----End
7.11.6 Clearing the Audible and Visual Alarm Indication of an NE

Cabinet Permanently
When an alarm is generated on an NE, the NE displays different audible and visual alarm
notifications according to the alarm levels. By disabling alarm sound and alarm indicator on the
U2000, all the audible and visual alarm notifications on the NE are closed permanently unless
you enable the alarm sound and alarm indicator again on the U2000.
Prerequisite
Procedure
1 In the NE Explorer, select an NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
2 Click Query to query the settings of audible and visual alarm notifications of the NE from the
NE side.
3 Set Alarm light switch and Alarm sound switch of the NE:
l Double-click the Alarm light switch and Alarm sound switch lists respectively, and select
Disabled or Enabled from the drop-down list.
l If you want to set Alarm light switch and Alarm sound switch to Enabled, click
Default.
4 Click Apply. The Confirm dialog box is displayed asking you whether to proceed.
5 Click OK. A prompt is displayed indicating that the operation is successful.
6 Click Close.
----End


Context
l For the alarm that meets the highlight condition, if the difference between the local time
of the client and the time of alarm occurrence reaches the threshold time for highlight, the
alarm is highlighted.
l You can click Default to reset the settings to defaults.
Procedure
2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
Highlight in the navigation tree on the left.
NOTE
3 In the Highlight group box, set the time and alarm status for alarms of a certain severity, and
then select Enable.
NOTE
The validity period ranges from 1 to 1000000 minutes.
4 Click OK.
----End

already viewed.
Context

Procedure
Terminal Settings node, and then select Alarm Fonts.
3 In the Alarm Fonts area, set fonts, sizes, styles, and colors for alarms that are not read and that
are already read.
4 Click OK.
----End

and other windows.
Context
Procedure
Terminal Settings node, and then select Alarm Display Mode.

NOTE
3 In the Alarm Display Mode area, select the alarm display mode, and set background colors for
different alarm states.
Table 7-10 Alarm background color in various display mode

Display Mode Field Alarm Background Color
Icon Severity The background color is displayed based on the

color of the state. The severity icon is displayed
in the Severity field, and the color of the
severity icon is displayed based on the color of
its severity.
CellBackground Severity The background color is displayed based on the

RowBackground Severity The background color is displayed based on the

All the other fields The background colors of the unacknowledged

and uncleared alarms are displayed based on
the colors of their severities, whereas the
background colors of the alarms in other status
are displayed based on the colors of their status.

NOTE
The Identifier field has no background color. Therefore, it is not affected by the setting of the alarm display
mode.
4 Click OK.
----End

Procedure
Terminal Settings node, and then select New Alarm/Event.
NOTE
3 In the New Alarm/Event group box, select The Client Is on Top When a New Alarm Is
Reported and the alarm severity.
4 In the New Alarm/Event group box, select Display on top or Display at the bottom.

5 In the Visible Level in Alarm Lamps group box, select the severity to be displayed on the alarm
indicator.
6 In the Additional Options group box, set the display properties.
7 Click OK.
----End

Context
l Acknowledged and cleared alarms are not displayed in the topology view, because they
indicate that the faults are already rectified. To know the meaning of each alarm state, see
7.1.10 Alarm States.
l In the Example pane, you can view the display effect after setting.
l You can click Default to restore the settings in the Topology Status Display (For the
current user) dialog box to the defaults.
Procedure
2 In the Preferences dialog box, choose the Topology Status Display node.

3 Set the alarm display attributes of the topology view.

Topology View
Display Style of Alarm States In the Display Style of Alarm States area, set the alarm
state display mode in the topology view.
NOTE
When an alarm in a certain state is generated by an NE, the topology
icon of the NE in the topology view is displayed in the
corresponding color. For details on how to set alarm colors, see
7.11.2 Setting Prompt Colors of Alarms.


Topology View
Alarm States to Be Displayed In the Alarm States to Be Displayed area, set the alarm
states to be displayed in the topology view. If you select
Customize the alarm states to be displayed, click the
Up or Down button to change the state display priority.
NOTE
The state listed on the top has the highest priority. When there are
alarms in multiple states, the color of the topology icon depends
on that of the alarm state in the highest priority.
Additional Display Effects In the Additional Display Effects pane, set the additional
display effects, such as Blink, Show alarm prompt, and
Add an icon frame for an unacknowledged alarm.
4 Click OK.
----End
7.12 Setting Remote Alarm/Event Notification

Alarms/events that meet the remote notification rules are notified to maintenance engineers after
you set the remote notification rules including the notification conditions, notification time, and
notification methods. This helps maintenance engineers who are not on site to know the alarm/
event information on the U2000 server and take proper measures. On the U2000, you can set
the formats of emails and short messages, delay the sending of remote notification messages,
disable remote notification sending for alarms cleared in the specified time period. In addition,
you can control the traffic of emails and short messages. If the traffic reaches the specified value,
new emails and short messages are discarded, that is, remote notification message are not sent.
7.12.1 Setting the Communication Parameters for Remote Notification

Before using a remote notification device to send an short message or email, you need to set the
communication parameters of the remote notification device.
7.12.2 Setting the Format of Remote Alarm/Event Notification Messages
You can set the format of the contents in a mail or short message, including the title, message
start character, message end character, alarm/event fields, and display order of the fields.
7.12.3 Setting Delay Delivery of Remote Alarm/Event Notification Messages
You can set the delay time for remote alarm notification. After an alarm is generated, if it is not
cleared within the delay time, a remote alarm notification is sent; otherwise, no remote alarm
notification is sent.
7.12.4 Setting the Remote Alarm/Event Notification Rule
You can set the remote notification conditions, notification time, and notification modes by
setting the remote alarm/event notification rule.
7.12.5 Downloading Remote Notification Logs
Remote notification logs of alarms and events are stored in a file. On the U2000, you can
download remote notification logs to the local computer and then view them.

7.12.1 Setting the Communication Parameters for Remote

Notification
Before using a remote notification device to send an short message or email, you need to set the
communication parameters of the remote notification device.
Context
l You can set the communication parameters of the remote notification not only on the remote
notification client but also on the integrated client.
l There are four types of sending devices: Email, GSM Modem, CDMA Modem, and SMS
Gateway(SMS Center). If the type of the sending device is Email, remote notification is
sent through emails; if the type of the sending device is any of the other three, remote
notification is sent through short messages. The U2000 supports the WMOD2B GSM/
GPRS Modem and TD-8022R Modem.
l When the type of the sending device is modem, If the server is selected, you need to install
modem correctly on the server. Then you can send short messages from any client of this
server through setting modem notification parameters. If the client is selected, you need to
install modem on the specified client. Then you can send remote notification through short
messages from this client.
Procedure
1 Choose Fault > Settings > Remote Notification from the main menu.
2 In the Remote Notification window, click Setting in the lower left part, and then choose
Communication Settings.
3 In the Communication Settings dialog box, set the communication parameters.

Setting communication parameters Operation

Adding communication parameters 1. Click Add.
2. In the Add Notification Device
Communication Settings dialog box, enter the
device setting name, select the sending device,
and then click Next.
3. In the Add Notification Device
Communication Settings dialog box, set
related parameters and select Enable.
4. Click Finish.
Modifying communication parameters 1. Select a row in the list and click Modify.
2. In the Modify Notification Device
Communication Settings dialog box, modify
device setting name and communication
parameters.
3. Click OK.
Deleting communication parameters 1. Select a row in the list and click Delete.
----End
7.12.2 Setting the Format of Remote Alarm/Event Notification

Messages
You can set the format of the contents in a mail or short message, including the title, message
start character, message end character, alarm/event fields, and display order of the fields.
Procedure
2 In the Remote Notification window, click Setting and select Message Format Settings at the
left bottom corner.

3 In the Message Format Settings dialog box, set the format of emails or short messages.
4 Click Email Content Setting. Select the contents in an email, such as the NE name and location
information.
5 Select the SMS Content tab. Click SMS Content Setting, and select the contents in a short
message, such as the NE name and location information.
6 Click OK.
----End
7.12.3 Setting Delay Delivery of Remote Alarm/Event Notification

Messages
You can set the delay time for remote alarm notification. After an alarm is generated, if it is not
cleared within the delay time, a remote alarm notification is sent; otherwise, no remote alarm
notification is sent.
Procedure
2 In the Remote Notification window, click Setting in the lower left part, and then choose Delay
Settings.

3 In the Delay Settings dialog box, you can set the delay time for remote alarm notification.
4 Click OK.
----End
7.12.4 Setting the Remote Alarm/Event Notification Rule

You can set the remote notification conditions, notification time, and notification modes by
setting the remote alarm/event notification rule.
Context
l In notification conditions, you can set the alarm name, severity, and other properties for
remote notification. The notification time indicates the time when the remote notification
is sent. The notification mode indicates the email address and mobile phone number of the
receiver.
l The U2000 supports at most fifty remote notification rules for alarms/events.
l In an email or SMS, the alarm/event occurrence time and the alarm clearance time are the
time of the U2000 server.
l The procedures for setting remote event notification rule and remote alarm notification rule
are the same. The following takes the remote alarm notification rule as an example.
Procedure
2 In the Remote Notification window, click Add, and then choose Alarm Notification Rule.

NOTE
3 On the Base Setting tab of the Add Remote Notification Rule dialog box, set the parameters
such as Alarm name and Severity.
4 Click the Alarm Source tab. On the Alarm Source tab, select All objects, and then select all
NEs or select Custom to set alarm sources by NE or NE type. Click Next.
5 In the Add Remote Notification Rule dialog box, set the notification time, time segment, and
time zone. Click Next.
6 In the Add Remote Notification Rule dialog box set the email address or SMS number.
NOTE
To instantly enable the rule, select Enable. In the Remote window, you can select or deselect Enable of this
record, and then click Apply to save the setting.
7 Click Finish.
----End
7.12.5 Downloading Remote Notification Logs

Remote notification logs of alarms and events are stored in a file. On the U2000, you can
download remote notification logs to the local computer and then view them.
Procedure
1 Choose Fault > Download Remote Notification Logs from the main menu.
2 In the Download Remote Notification Logs window, select the remote notification log file to
be downloaded, and then click Download.
NOTE
l To directly open the remote notification log file or save the file to the local computer, right-click the
file and choose Open.
l To immediately download the remote notification log file, right-click the file and choose Download.
l To refresh the information in the left area of the window, right-click any place in the left area and
choose Refresh.
l To delete a download task, select the task in the right area, and then click Delete task. If a download
task is complete, deleting the task does not delete the remote notification log file that is downloaded
to the local computer.
----End
7.13 Modifying Alarm Severity

You can adjust the alarm severity of each NM alarm, NE alarm and board alarm. This facilitates
management and improves the efficiency of alarm monitoring.
7.13.1 Changing the U2000 Alarm Severity
You can set the alarm severity levels for the U2000 alarms as required to improve the efficiency
of alarm monitoring.
7.13.2 Modifying the Alarm Severity for an NE

You can set the alarm severity for an NE by applying the customized alarm template to the NE.
With the alarm severity defined, the alarm monitoring efficiency is improved.
7.13.3 Modifying the Alarm Severity for a Board
You can modify the severity of the board alarms according to the requirement. In this way, you
can focus on the important alarms, thus facilitating maintenance.
7.13.1 Changing the U2000 Alarm Severity

You can set the alarm severity levels for the U2000 alarms as required to improve the efficiency
of alarm monitoring.
Prerequisite
Procedure
1 Choose Fault > Settings > Redefine from the main menu.
2 Click Add to create an alarm redefinition.
3 Click the Redefined Severity column of a certain alarm redefinition record, and change the
severity of the alarm.
4 Click Apply.
----End
7.13.2 Modifying the Alarm Severity for an NE

You can set the alarm severity for an NE by applying the customized alarm template to the NE.
With the alarm severity defined, the alarm monitoring efficiency is improved.
Prerequisite
l You must be an NM user with "NM monitor" authority or higher.
l The alarm attribute template that has the alarm severity configured as required must be
customized first.
Context
NOTE
If you apply the alarm template that contains the changed alarm severity and reporting mode to another
NE, the settings of alarm suppression and alarm reversion for the NE are lost.
Procedure
2 Choose SDH/WDM/NAWDM from the Function Tree. In the right pane, select the pre-
customized template from the Template drop-down list and click Apply to. The Apply Alarm
Attribute Template to NE dialogue box is displayed.

NOTE
If the appropriate alarm attribute template is not available, you need to customize a template first.
3 Check the Alarm Severity in the Alarm Attribute group box.
4 Select the NE you need from the List of Optional Objects, and move it to List of Selected
Objects. Click Apply. Wait for a few seconds and the Operation Result dialog box is displayed.
5 Click Close.
----End
7.13.3 Modifying the Alarm Severity for a Board

You can modify the severity of the board alarms according to the requirement. In this way, you
can focus on the important alarms, thus facilitating maintenance.
Prerequisite
Procedure
1 In the Workbench window, double-click to navigate to the Main Topology.
2 In the Main Topology, double-click the failed object to navigate to the NE Explorer window.
3 In the NE Explorer, select a board and choose Alarm > Alarm Severity and Auto Reporting
4 Adjust the Severity of the alarm you want.
5 Optional: To restore to the default settings, click Default.
6 Click Apply. The Operation Result dialog box is displayed.
7 Click Close.
----End
7.14 Analyzing Alarm Correlation

Certain alarms or events that NEs report are correlated. This topic describes how to set alarm
correlation rules so that the U2000 can handle alarms or events automatically according to the
preset operations, and thus improving the alarm or event handling efficiency.

7.14.2 Alarm Correlation

Alarms or events are correlated to each other, and you can set correlation rules. After setting,
the U2000 automatically processes alarms or events according to the preset operations, thereby
improving the alarm or event processing efficiency.
7.14.3 Setting the Default Alarm Correlation Rules
The U2000 provides the default Alarm correlation rules. You can set whether to enable these
rules as required.
7.14.4 Setting an Alarm Correlation Rule
After you set a correlation rule, the U2000 redefines the alarm severity, makes correlative alarm
marks (saves alarms to the suppression library), or discard alarms, thereby reducing the
unnecessary alarms or ignoring the non-root alarms. This helps you can to handle the important
alarms and quickly identity and rectify faults.
7.14.5 Setting an Alarm/Event Frequency Analysis Rule
After you set an alarm/event frequency analysis rule, the U2000 analyzes the frequency of
alarms/events. When the number of alarms/events exceeds the preset threshold in the specified
period, the U2000 processes the alarms/events according to the preset processing actions.
7.14.6 Setting an Intermittent Alarm or Repeat Event Analysis Rule
After you set an intermittent alarm or repeat event analysis rule, the U2000 can abandon the
alarms or events that meet the rule.
7.14.7 Setting an Acknowledged and Uncleared Alarm Time Analysis Rule
After you set the acknowledged and uncleared alarm time analysis rule, the U2000 can change
the severity of an alarm that is acknowledged but not cleared in a long period. This helps you to
handle the alarm in time.
7.14.8 Example of Alarm/Event Correlation Analysis
This topic provides two examples of correlation analysis to help you to understand correlation
analysis.
7.14.9 Example of Alarm/Event Frequency Analysis
This topic describes an example of alarm/event frequency analysis to help you to understand
alarm/event frequency analysis.
7.14.10 Example of Intermittent Alarm/Repeat Event Analysis
This topic describes an example of intermittent alarm or repeat event analysis to help you
understand the intermittent alarm or repeat event analysis.
7.14.11 Example of Acknowledged and Uncleared Alarm Time Analysis
This topic describes an example of the acknowledged and uncleared alarm time analysis to help
you understand the acknowledged and uncleared alarm time analysis.
7.14.12 Setting the Rules for the Correlation Analysis of Trail Alarms
The occurrence of some faults, such as fiber disconnection, generates a large number of alarms,
of which some alarms are derived from others. Automatic analysis of the trail root alarms enables
the U2000 to analyze the alarms that are reported to the U2000 from the NEs. According to the
alarm correlation analysis rules, the U2000 adjusts the severity levels of the root alarms and
correlative alarms. Thus, you can focus on the root alarms or important services.
7.14.13 Analyzing Trail Alarm Correlation
In the root alarm analysis, the U2000 does not mask any alarm, but analyze all alarms according
to the alarm correlation rules and filter for the root alarms. This function helps the maintenance
personnel to focus on the root alarms or highly concerned services so that they can quickly locate
the faults.
7.14.14 Configuring a Fiber-Related Alarm

After the fiber-related alarm is configured, the fiber connecting two NEs in the topology view
is marked in red when an alarm is reported to the ports connected by fibers. This helps the
maintenance engineer to focus on the root alarms or the highly concerned services.

NE Alarm Correlation
The NE alarm correlation rule is the alarm performance monitoring mechanism of the logical
function module of the equipment. The rule is fixed and cannot be manually set. A good
understanding of the mechanism helps you improve the efficiency of analyzing and locating
faults during equipment maintenance.
Root alarm is directly caused by the abnormal events or faults in the network. A root alarm
always generates some other alarms of lower severity level. These alarms derived from the root
alarm are correlative alarms.
For example, if a fiber is cut off, the SPI functional module in the optical board detects the
occurrence of the R_LOS alarm (root alarm). This alarm in turn causes the RST functional
module in the regenerator section (RS) to generate alarms (correlative alarm) such as RLOF,
R_OOF, B1_SD and B1_EXC. To avoid this problem, you can set correlation rules between the
previously mentioned alarms, and enable the alarm correlation suppression. In this way, the NE
reports only the root alarm, R_LOS.
Figure 7-12 shows the alarm flow of each function module of the SDH equipment in detail. In
this flow, you can view the relation between alarm maintenance signals generated by each
function module of the SDH equipment.

Figure 7-12 NE Alarm Correlation
U2000 Alarm Correlation

For the U2000 alarm correlation analysis, you need to set the alarm correlation rule and enable
the alarm correlation analysis to use the alarm correlation analysis function for suppressing
correlative alarms.
CAUTION
l The alarm correlation rule is the basis for the alarm correlation analysis, and is thus closely
related to the analysis result. Be cautious when you set the alarm correlation rule.
l Usually, it is recommended that you use the default alarm correlation analysis rule.
l The alarm correlation suppression is set to disabled by default. To enable the alarm
correlation rules for alarm analysis, you need to manually enable the alarm correlation
suppression.

Example of the Alarm Correlation
NE1, NE2 and NE3 form a non-protection (NP) chain with services running between each two
of them. If the fiber between NE1 and NE2 is broken, NE2 reports the R_LOS alarm. Meanwhile
NE2 and NE3 report a lot of TU_AIS alarms. These TU_AIS alarms are, however, generated
by the R_LOS alarm on NE2. In this case, you can set alarm correlation rules for the R_LOS
alarm of NE2 to suppress the TU_AIS alarms of NE2 and NE3. This reduces the alarm amount
and eases the fault location.
The alarm correlation rule takes effect only in the following cases:
l Alarm 1 and alarm 2 are generated on the same object.
l Alarm 1 is generated at the upstream of alarm 2.
l Alarm 1 is generated at the opposite service end of alarm 2.
The alarm correlation rule realizes the following functions:
l Enable alarm 1 to suppress alarm 2.
l Adjust the severity levels of alarm 1 and alarm 2 to higher levels.
The alarm correlation rule can adjust the severity levels of root alarms and correlative alarms to
higher levels on condition that the alarms are generated in compliance with the alarm correlation
rule. For example, the severity level of TU_AIS is major. If you set the TU_AIS as the correlative
alarm of the R_LOS and adjust the severity level of the TU_AIS to a higher level in an alarm
correlation rule, the TU_AIS is adjusted to a critical alarm only when the TU_AIS is generated
by R_LOS. If the TU_AIS is not generated by R_LOS, it is still displayed as a major alarm on
the U2000.
7.14.2 Alarm Correlation

Alarms or events are correlated to each other, and you can set correlation rules. After setting,
the U2000 automatically processes alarms or events according to the preset operations, thereby
improving the alarm or event processing efficiency.
Alarm Correlation Analysis

Alarm correlation analysis focuses on alarm correlation suppression, trail-related alarms, and
custom alarms. For details, see 7.14.1 Alarm Correlation Analysis.
Custom alarm correlation analysis involves two interfaces: Default Correlation and
Correlation Analysis. The Default Correlation interface displays the alarm correlation rules
defined by the U2000. You can set whether to use these rules. On the Correlation Analysis
interface, you can create correlation rules.
Correlated alarms indicate that the causes for these alarms are correlated. One alarm has the root
cause for the other alarms.
Faults may result in multiple types of alarms. Correlative alarms affect fault identification or
analysis by the maintenance personnel. Therefore, on the U2000, you can set a correlation rule

based on the alarm features such as the alarm generation time and physical location, to discard
the correlative alarms that meet the rule, make correlative alarm marks (save the alarms to the
suppression library), or decrease the alarm severities.
Figure 7-13 shows the relationships between a root alarm and its correlative alarms.
Figure 7-13 Relationships between a root alarm and its correlative alarms
The high service memory usage alarm leads to two alarms: high memory usage alarm and high
CPU usage alarm. The high CPU usage alarm leads to another alarm: abnormal U2000 service
exit alarm. Therefore, the high service memory usage alarm is the root alarm, and the other
alarms are its correlative alarms.
Alarm/Event Frequency Analysis

The same alarms/events generated during a period may be correlated to each other. In alarm/
event frequency analysis, if the number of the same alarms/events generated during a period of
time reaches the specified value, these alarms/events are considered to be correlated to each
other.
Through alarm/event frequency analysis, when the number of the same alarms/events generated
during a period reaches the specified threshold, the alarms/events are considered to be correlated
to each other. In this case, the U2000 performs the preset operations.
Intermittent Alarm and Repeat Event Analysis

When the reporting interval of clearance alarms of an alarm is shorter than or equal to the
specified value, this alarm is defined as an intermittent alarm.
When the reporting interval of the same events is shorter than or equal to the specified value,
this event is defined as a repeat event.
Faults may result in multiple same alarms/events in a short period. These alarms/events are
redundant for the maintenance personnel. Therefore, for these potential intermittent alarms and
repeat events, you can set an intermittent alarm and repeat event analysis rule on the U2000.
Thus, the U2000 discards the intermittent alarms and repeat events that meet the rule and displays
only the first repeat event or cleared intermittent alarm.

Acknowledged and Uncleared Alarm Analysis

If acknowledged alarms are not cleared for a long time, you can increase the alarm severities
through acknowledged and uncleared alarm analysis. This helps the maintenance personnel to
pay attention to the alarms and handle them in time.
7.14.3 Setting the Default Alarm Correlation Rules

The U2000 provides the default Alarm correlation rules. You can set whether to enable these
rules as required.
Context
l The Default Correlation interface displays the default correlation rules provided by the
U2000. These rules are automatically generated during installation or imported by using a
tool after installation. You can set whether to use these rules, but cannot modify them.
l After you select a correlation rule on the Default Correlation interface, the details about
this rule is displayed in Details in the lower part of the interface.
Procedure
1 Choose Fault > Settings > Correlation from the main menu.
2 On the Default Correlation tab, set whether to enable the default correlation rules.
Setting the Default Operation Method

Correlation Rules
Enabling the default 1. To enable a correlation rule, click the Enable column to
correlation rules select the rule. You can also right-click the correlation rule
and choose Enable.
2. To enable all default correlation rules, right-click any
correlation rule and choose Enable All.
Disabling the default 1. To disable a correlation rule, click the Enable column to
correlation rules deselect the rule. You can also right-click the correlation
rule and choose Disable.
2. To disable all default correlation rules, right-click any
correlation rule and choose Disable All.
----End
7.14.4 Setting an Alarm Correlation Rule

After you set a correlation rule, the U2000 redefines the alarm severity, makes correlative alarm
marks (saves alarms to the suppression library), or discard alarms, thereby reducing the
unnecessary alarms or ignoring the non-root alarms. This helps you can to handle the important
alarms and quickly identity and rectify faults.
Context
l The U2000 redefines the alarm severity, makes correlative alarm marks (saves alarms to
the suppression library), or discard alarms.

l The U2000 carries out the correlation rule in higher severity, and then the rule in lower
severity. When the severities of two correlation rules are the same, the U2000 carries out
them according to the sequence in which they are loaded to the correlation analysis
template.
Procedure
2 On the Correlation Analysis tab, set a correlation rule.
Setting a Correlation Rule Operation

Adding a correlation rule 1. Click Add.
2. In the Create a Correlation Rule dialog box, set the
parameters such as the root alarm, correlative alarm, and
action, and then click Next.
3. Set the conditions of the correlation rule, and then click
Next.
4. Set the analysis period, priority, and memo, select Enable
the correlation rule, and then click Finish.
Modifying a correlation rule 1. Select a rule, and then click Property.
2. In the Property dialog box, modify the parameters
settings.
NOTE
3. Click OK.
Deleting a correlation rule 1. Select the rule you want to delete. Click Delete.
NOTE
----End

7.14.5 Setting an Alarm/Event Frequency Analysis Rule

After you set an alarm/event frequency analysis rule, the U2000 analyzes the frequency of
alarms/events. When the number of alarms/events exceeds the preset threshold in the specified
period, the U2000 processes the alarms/events according to the preset processing actions.
Context
If the processing policy is Generate Local NM alarms, when the alarm/event frequency
analysis rule is met, the U2000 generates an avalanche alarm.
Procedure
2 On the Alarm/Event Frequency Analysis tab, set an alarm/event frequency analysis rule.
Setting an Alarm/Event Operation

Frequency Analysis Rule
Adding an alarm/event 1. Click Add.
frequency analysis rule 2. In the Add Alarm/Event Frequency Analysis Rule
dialog box, set the parameters.
3. Click OK.
frequency analysis rule 2. In the Property dialog box, modify the parameters
settings.
NOTE
3. Click OK.
frequency analysis rule NOTE
----End

7.14.6 Setting an Intermittent Alarm or Repeat Event Analysis Rule

After you set an intermittent alarm or repeat event analysis rule, the U2000 can abandon the
alarms or events that meet the rule.
Context
l When the interval between two reports on the clearance of an alarm is shorter than or equal
to the specified interval, this alarm is defined as an intermittent alarm.
l When the interval of reporting an event is shorter than or equal to the specified interval,
this event is defined as a repeat event.
l The U2000 abandons the intermittent alarms or repeat events that met the rule. Only the
first repeat event or cleared intermittent alarm is displayed.
Procedure
2 On the Intermittent Alarm/Repeat Event Analysis tab, set an intermittent alarm or repeat
event analysis rule.
Setting an Intermittent Operation

Alarm or Repeat Event
Analysis Rule
Adding an intermittent alarm 1. Click Add.
or repeat event analysis rule 2. In the Add Intermittent Alarm/Repeat Event Analysis
Rule dialog box, set the parameters.
3. Click OK.
Modifying an intermittent 1. Select a rule, and then click Property.
alarm or repeat event 2. In the Property dialog box, modify the parameters
analysis rule settings.
NOTE
3. Click OK.

Setting an Intermittent Operation

Alarm or Repeat Event
Analysis Rule
Deleting an intermittent 1. Select the rule you want to delete. Click Delete.
alarm or repeat event NOTE
analysis rule
----End
7.14.7 Setting an Acknowledged and Uncleared Alarm Time

Analysis Rule
After you set the acknowledged and uncleared alarm time analysis rule, the U2000 can change
the severity of an alarm that is acknowledged but not cleared in a long period. This helps you to
handle the alarm in time.
Procedure
2 On the Acknowledged and Uncleared Alarm Time Analysis tab, set the acknowledged and
uncleared alarm time analysis rule.
Setting an Acknowledged Operation

and Uncleared Alarm Time
Analysis Rule
Adding an acknowledged and 1. Click Add.
uncleared alarm time 2. In the Add Acknowledged and Uncleared Alarm Time
analysis rule Analysis dialog box, set the parameters.
3. Click OK.

Setting an Acknowledged Operation

and Uncleared Alarm Time
Analysis Rule
Modifying an acknowledged 1. Select a rule, and then click Property.
and uncleared alarm time 2. In the Property dialog box, modify the parameters
analysis rule settings.
NOTE
3. Click OK.
Deleting an acknowledged 1. Select the rule you want to delete. Click Delete.
and uncleared alarm time NOTE
analysis rule
----End
7.14.8 Example of Alarm/Event Correlation Analysis

This topic provides two examples of correlation analysis to help you to understand correlation
analysis.
Example of the Correlation Analysis of a Single Alarm

Background
Alarm M of NE Z prompts that the service quality declines. Generally, the priority of alarm M
is low. In the case of an important activity, however, the priority of alarm M becomes high to
ensure the high quality of communications in the activity.
District Y of city X held an important activity from August 8 to August 15 in 2008. During this
period, the high quality of communications must be ensured. In this case, correlation rules were
set to raise the severity of alarms M that were generated by NE Z in district Y. Thus, alarms M
took high priority for processing.
Operation Guide
1. Click the Correlation Analysis tab.

Choose Fault > Settings > Correlation from the main menu. In the Correlation window,
click the Correlation Analysis tab.
2. Create an alarm or event correlation analysis rule and set the associated parameters.
Click Add and set the parameters according to the following table.
Parameter Value
Root alarm Set it to critical alarm M.

Parameter Value
Action Set it to Raise level.
Correlative alarm You do not need to set it.
Action You do not need to set it.
Value You do not need to set it.
Property, Operator, Value Set three rules:

l The value of Location Information is
A.
l The value of Generation time is later
than 00:00:00 August 8, 2008.
l The value of Generation time is earlier
than 23:59:59 August 15, 2008.
.
Analysis period (Seconds) Use the default value.
Priority Use the default value.
Memo Use the default value.
Enable the correlation rule Select or deselect the check box.
Example of the Correlation Analysis of Two Alarms

Background
When a link to an NE is faulty, the NE raises alarm M regularly. At the same time, a large number
of similar alarms N are raised by this NE or other NEs because of this faulty link. Therefore, the
root alarm of fault alarms N is fault alarm M. In correlation analysis, you only need to analyze
and handle alarm M but do not need to analyze alarm N. By setting an alarm correlation analysis
rule, you can suppress alarm N that is raised after alarm M and ignore alarms N.
Operation Guide
1. Click the Correlation Analysis tab.
click the Correlation Analysis tab.
2. Create an alarm/event correlation analysis rule and set the associated parameters.
Click Add and set the parameters according to the following table.
Parameter Value
Root alarm Set it to alarm M.
Action Use the default value.
Correlative alarm Set it to alarm N.
Action Set it to Import to suppressed library.

Parameter Value
Value Use the default value.
Property Set it to Generation time of alarm M.
Operator Set it to Smaller than.
Value Set it to alarm N.
Priority Use the default value.
Analysis period (Seconds) Use the default value.
Enable the correlation rule Select the check box.
7.14.9 Example of Alarm/Event Frequency Analysis

This topic describes an example of alarm/event frequency analysis to help you to understand
alarm/event frequency analysis.
Background
If major alarm M is reported more than five times in an hour, the service availability is considered
to be greatly decreased. You need to rectify the fault to recover the service availability. To handle
the alarm in time, you can set the alarm/event frequency analysis rules. You can set the triggering
condition to five times in 60 minutes. If major alarm M is reported more than five times in 60
minutes, the alarm severity changes to Critical.
Operation Guide
1. Click the Alarm/Event Frequency Analysis tab.
click the Alarm/Event Frequency Analysis tab.
2. Create an alarm/event frequency analysis rule and set the associated parameters.
Click Add. Set the parameters according to the following table.
Parameter Value
Alarm/Event name Set it to major alarm M.
Time range Set it to 60 minutes.
Alarm count Set it to 5.
Change the alarm Set it to Critical.

severity to
Enable Select the check box.

7.14.10 Example of Intermittent Alarm/Repeat Event Analysis

This topic describes an example of intermittent alarm or repeat event analysis to help you
understand the intermittent alarm or repeat event analysis.
Background
If you receive minor alarm M frequently in a short period of time, it indicates that the state of a
device or service frequently switches between normal and abnormal. To deal with the situation,
you can set intermittent alarm or repeat event analysis. If alarm M is reported and cleared five
times in 10 seconds, it is abandoned.
Operation Guide
1. Click the Intermittent Alarm/Repeat Event Analysis tab.

click the Intermittent Alarm/Repeat Event Analysis tab.
2. Create an intermittent alarm or repeat event analysis rule and set the associated parameters.
Parameter Value
Alarm/Event Set it to minor alarm M.

name
Interval(second) Set it to 10.
Intermittence/ Set it to 5.
Repeat times
Action Set it to Abandon.
7.14.11 Example of Acknowledged and Uncleared Alarm Time

Analysis
This topic describes an example of the acknowledged and uncleared alarm time analysis to help
you understand the acknowledged and uncleared alarm time analysis.
Background
Experience shows that major alarm M can be cleared 30 minutes after certain measures are taken.
If alarm M is not cleared 30 minutes after certain measures are taken, you need to set
acknowledged and uncleared alarm time analysis by changing the alarm severity to critical. Thus,
the alarm can be processed in time.
Operation Guide
1. Click the Acknowledged and Uncleared Alarm Time Analysis tab.

click the Acknowledged and Uncleared Alarm Time Analysis tab.

2. Create an acknowledged and uncleared alarm time analysis rule and set the associated
parameters.
Parameter Value
Alarm name Set it to major alarm M.
Time range Set it to 30.
Change the alarm severity to Set it to Critical.
7.14.12 Setting the Rules for the Correlation Analysis of Trail

Alarms
The occurrence of some faults, such as fiber disconnection, generates a large number of alarms,
of which some alarms are derived from others. Automatic analysis of the trail root alarms enables
the U2000 to analyze the alarms that are reported to the U2000 from the NEs. According to the
alarm correlation analysis rules, the U2000 adjusts the severity levels of the root alarms and
correlative alarms. Thus, you can focus on the root alarms or important services.
Prerequisite
l Only the SDH NEs, WDM NEs, and NA WDM NEs support the dynamic analysis of root
alarms in a trail.
Procedure
1 Choose Fault > Correlation Analysis > Trail Alarm Correlation Rules from the main menu.
2 Add a new rule:

l For SDH and WDM NEs, click the SDH/WDM tab. Then, click Create to add a new rule.
l For NA WDM NEs, click the NAWDM tab. Then, click Create to add a new rule.
NOTE
You can also modify an existing alarm correlation analysis rule.
3 Set the Alarm 1, Alarm 2, Conditions, and Action for the new rule.
4 Optional: Select Enable Automatic Correlation Analysis as required.

NOTE
If you select Enable Automatic Correlation Analysis, the alarm correlation analysis is dynamically
performed when alarms are reported. In this case, you can view root alarms in the Browse Current
Alarm window. If you do not select Enable Automatic Correlation Analysis, you need to perform the
correlation analysis and view root alarms in the trail alarm analysis window.
5 Click Apply.
6 In the dialog box, click Close.

7 Optional: Choose Fault > Browse Current Alarm from the main menu. Right-click a root
alarm and choose Query Correlative Alarms from the shortcut menu to display the correlative
alarms suppressed by this root alarm. Click Close.
----End
7.14.13 Analyzing Trail Alarm Correlation

In the root alarm analysis, the U2000 does not mask any alarm, but analyze all alarms according
to the alarm correlation rules and filter for the root alarms. This function helps the maintenance
personnel to focus on the root alarms or highly concerned services so that they can quickly locate
the faults.
Prerequisite
l Only the SDH NEs, WDM NEs, and NA WDM NEs support the dynamic analysis of root
alarms in a trail.
l The correlation analysis rules for trail alarms must be created.
Context
Note that correlation analysis only filters out non-root alarms, but cannot increase the severity
level of the non-root alarms.
Procedure
1 Choose Fault > Correlation Analysis > Trail Alarm Correlation Rules from the main menu.
2 Add a new rule:
l For SDH and WDM NEs, click the SDH/WDM tab. Then, click Create to add a new rule.
l For NA WDM NEs, click the NAWDM tab. Then, click Create to add a new rule.
NOTE
You can also modify an existing alarm correlation analysis rule.
3 Set the Alarm 1, Alarm 2, Conditions and Action fields for the new rule.
4 Click Apply.
7 Click Filter.
8 In the dialog box that is displayed, set the filtering criteria, and click OK.
9 Choose Fault > Correlation Analysis > Analyze Trail Alarm Correlation from the main
menu.
10 In the dialog box that is displayed, select a time segment and click OK.
11 In the dialog box that is displayed, click OK to obtain the root alarm information.
----End

7.14.14 Configuring a Fiber-Related Alarm

After the fiber-related alarm is configured, the fiber connecting two NEs in the topology view
is marked in red when an alarm is reported to the ports connected by fibers. This helps the
maintenance engineer to focus on the root alarms or the highly concerned services.
Prerequisite
Procedure
1 Choose Fault > Correlation Analysis > Fiber Relating Alarm from the main menu.
2 In the dialog box that is displayed, click Query to query the status of the fiber-related alarm.
3 In the dialog box that is displayed, select the alarm to be related, and then select Related or Not
Related from the drop-down list in the Status column.
NOTE
If you do not need to monitor a certain type of alarms, select the alarm, and then select Not Related from
the drop-down list in the Status column. In this case, the alarms of this type are not reported to the
U2000.
4 Click Apply.

CAUTION
The setting of Fiber relating alarm status takes effect only on subsequent alarms that will be
reported to the U2000. For the existing alarms on the U2000, fibers are not related to the alarm
status.
5 Click Query to query the latest configuration of the alarm from the database, which is displayed
on the U2000.
NOTE
For multiple clients, if Status of an alarm is changed on one client, the latest configuration of the alarm
can be displayed on the U2000 by the query function of the other clients.
6 Click Close.
----End
7.15 Managing Alarm/Event Data

You need to clean up alarm/event data in the database in time, thereby preventing insufficiency
of database space. The U2000 supports periodical dump, overflow dump, and manual dump of
alarms/events. Dumped alarms/events are deleted from the database.
7.15.1 Setting Alarm/Event Timing Dump

The U2000 automatically dumps alarms or events based on the specified period. Dumped alarms/
events are deleted from the database, thereby preventing insufficiency of database space.
7.15.2 Setting Alarm/Event Overflow Dump
After you set alarm/event overflow dump, the U2000 periodically checks whether the capacity
of the alarms/events in the database reaches the specified threshold. If the overflow dump
condition is met, the U2000 automatically dumps alarms/events. Dumped alarms/events are
deleted from the database, thereby preventing insufficiency of database space.
7.15.3 Manually Dumping Alarms/Events
You can manually dump alarms/events. Dumped alarms/events are deleted from the database,
thereby preventing insufficiency of database space.
7.15.1 Setting Alarm/Event Timing Dump

Context
The alarm/event timing dump is performed everyday and the alarm/event overflow dump is
performed every 10 minutes. In this way, these two actions may be performed at the same time.
As performing these two actions deletes the data of one table, if these two actions are performed
at the same time, task execution failure alarm is generated. Therefore, you need to set the start
time of these two actions to be different. For example, the start time of the alarm/event timing
dump is set to 2007-01-01 10:05:00 whereas the start time of the alarm/event overflow dump is
set to 2007-01-01 10:00:00. The interval between two actions is five minutes, so they can be
performed at different time.

Procedure
2 In the Task Management window, choose Database Capacity Management in the navigation
tree.
3 In the Task Management window, double-click the Alarm/Event Log Dump task in the task
list.
4 In the Attribute dialog box, modify common and extended parameters.

5 Click OK.
----End
7.15.2 Setting Alarm/Event Overflow Dump

After you set alarm/event overflow dump, the U2000 periodically checks whether the capacity
of the alarms/events in the database reaches the specified threshold. If the overflow dump
condition is met, the U2000 automatically dumps alarms/events. Dumped alarms/events are
deleted from the database, thereby preventing insufficiency of database space.
Context

Procedure
2 In the navigation tree on the left of the Task Management window, choose Overflow Dump.
3 In the task list, double-click Alarm Overflow Dump or Event Overflow Dump.
4 In the Attribute dialog box, modify common and advanced parameters.
5 Click OK.
----End
7.15.3 Manually Dumping Alarms/Events

You can manually dump alarms/events. Dumped alarms/events are deleted from the database,
thereby preventing insufficiency of database space.
Procedure
2 In the navigation tree on the left of the Task Management window, choose Manual Dump.

3 In the task list, right-click Alarm Manual Dump or Event Manual Dump and choose Run.
4 In the Attribute dialog box, set the dump parameters.

Click Query to view the number of records to be dumped.
NOTE
l Dumping to (path) indicates the path of the dump file. The dump file is stored on the U2000 server.
The dump path of alarm data is NMS installation path/server/var/AlarmManualDump/FM. The
dump path of event data is NMS installation path/server/var/EventManualDump/FM.
l For details on the dump parameters, see Attribute.
5 Click Dump to dump alarms/events.
----End
7.16 Alarm Management (MSTP&WDM&RTN NE)

To ensure the normal running of the network, the network management and maintenance staff
should periodically check and monitor the network by taking appropriate alarm management
measures.

You can suppress alarms, so that the U2000 does not monitor these alarms. These alarms can
be generated from networkwide equipment, a particular NE, board, or even from a particular
functional module of a board.
7.16.2 Setting Alarm Reversion

You can set alarm reversion so that the status of the alarms reported from this port is displayed
as "no alarm". In this way, these alarms can be suppressed.
7.16.3 Setting the Types of Lower Order Services in the VC4 Path
The LP_UNEQ indication can be inserted for the port timeslots that are not configured with
lower order services, only after you set the TUG structure of the VC4 path in the transmit
direction.
7.16.4 Monitoring the Alarms and Performance of Lower Order Services in the VC4 Path
Set the TUG structure in the receiving direction of the VC4 path. By enabling the monitoring
of lower order alarms and setting the specific alarms to be monitored, you can monitor the
performance of the lower order services in the VC4 path of the network.
7.16.5 Setting the Insertion Mode for Channels Not Configured with Services
On the U2000, you can set the insertion mode of alarms in the channel according to the
networking and service requirements.
7.16.6 Specifying the Port QoS Alarm
You can set the QoS for a port depending on whether there are services on the port or whether
the services are important. In this way, you can effectively manage alarms. You can set the QoS
by specifying the bit error alarm threshold and setting the port switching conditions.
7.16.7 Configuring Alarm Insertion
For convenient commissioning and maintenance, you can manually insert an alarm or a
maintenance signal that can causes an alarm into a port of a trail. Thus, you can check the
correctness, connectivity and transmission performance of the trail connection by querying
whether any alarm occurs at opposite ends (upstream or downstream).
7.16.8 Inserting a Maintenance Signal to the ODU Layer
The alarm insertion at the ODU layer includes the AIS insertion, CLK insertion and OCI
insertion. The alarm insertion at the ODU layer is for the purpose of commissioning and
maintenance.
7.16.9 Setting NE Alarm Attributes
NE alarm attributes include the storage mode, reversion mode, correlation suppression of the
alarm, and alarm delay. You can set NE alarm attributes to effectively decrease the occurrence
frequency of invalid alarms and to improve the efficiency of alarm monitoring.
7.16.10 Enabling the Alarm Monitoring for Lower Order Paths
If you enable the alarm monitoring function for the lower order paths when you configure lower
order services in a VC4 higher order path, you can monitor the alarms of an individual lower
order path.
7.16.11 Configuring Housekeeping
By browsing housekeeping alarms, the network maintainer can learn the network running
environment in time. This ensures that the equipment runs properly.

You can suppress alarms, so that the U2000 does not monitor these alarms. These alarms can
be generated from networkwide equipment, a particular NE, board, or even from a particular
functional module of a board.
7.16.1.1 Suppressing NE Alarms
To facilitate management, you can suppress some alarms of the specified NE so that the
U2000 does not monitor these alarms. In this way, you can focus on important alarms. If you
suppress a certain alarm of a specified NE, the alarm is not reported.

7.16.1.2 Suppressing Alarms of a Board or Port

To suppress alarms of a specified board or port, you can directly perform the relevant operations
to the NE or the board in the NE Explorer. If you suppress a certain alarm of a specified board
or a port, the alarm is not reported to the NE or to the U2000. You can suppress the unimportant
alarms.
7.16.1.3 Suppressing the Alarms on an ATM Connection
You can suppress non-root alarms that are generated from a specified ATM connection. This
function facilitates the fault diagnosis and network maintenance.
7.16.1.4 Checking Path Alarm Suppression Status
You can view all alarms for which you configure alarm suppression in the network. You can
also restore the suppression status of an alarm to the default value, so that the alarm monitoring
of the service is not affected by improper settings.
7.16.1.1 Suppressing NE Alarms

To facilitate management, you can suppress some alarms of the specified NE so that the
U2000 does not monitor these alarms. In this way, you can focus on important alarms. If you
suppress a certain alarm of a specified NE, the alarm is not reported.
Prerequisite
Procedure
1 In the NE Explorer, click an NE and choose Alarm > Alarm Suppression from the Function
Tree.
2 Select an alarm that you want to suppress, and set the Status of the alarm as Suppressed.
NOTE
l If you have already created an alarm attribute template, click Use Template to select the template, and
then set alarm suppression for the NE.
l To suppress alarms for multiple NEs, you can customize an alarm attribute template, and apply the
alarm attribute template to these NEs.
3 Click Apply.
The Operation Result dialog box is displayed.
4 Click Close.
----End
Result
l After an alarm is suppressed, the NE does not monitor the alarm.
l After an alarm is suppressed, the U2000 does not clear the reported alarms, until an alarm
cleared notification is received.
7.16.1.2 Suppressing Alarms of a Board or Port

To suppress alarms of a specified board or port, you can directly perform the relevant operations
to the NE or the board in the NE Explorer. If you suppress a certain alarm of a specified board

or a port, the alarm is not reported to the NE or to the U2000. You can suppress the unimportant
alarms.
Prerequisite
Applies to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.
Procedure
1 In the NE Explorer, select a board and choose Alarm > Alarm Suppression from the Function
Tree.
2 Select a port from the Monitored Object drop-down list in the right-hand pane.
NOTE
In the Monitored Object field, you can select the current board to include all ports of the board, or select
multiple individual ports at the same time.
3 Set the Status of the alarms that need to be suppressed to Suppressed.

Click Apply and the Operation Result dialog box is displayed.
4 Click Close.
NOTE
If you have already created an alarm template for a board, click Use Template to select a suitable template.
----End
Result
l After an alarm is suppressed, the board does not monitor the alarm.
7.16.1.3 Suppressing the Alarms on an ATM Connection

You can suppress non-root alarms that are generated from a specified ATM connection. This
function facilitates the fault diagnosis and network maintenance.
Prerequisite
l Cross-connections must be created on the ATM board (For example: the AL1 board on the
4.0 equipment).
Procedure
1 In the NE Explorer, select an ATM board and choose Alarm > ATM Connection Alarm
Suppression from the Function Tree.
2 Click Query to query the alarm information from the NE.
3 Click Select Connection. The Select Connection dialog box is displayed.

4 In the Select Connection dialog box, select a connection and click OK.
5 You can use any of the following ways to set alarm suppression:
l Click Default.
l Click Use Template. Select a template from the Select Template dialog box displayed,
and click OK.
l Set Status for each Event.
6 Click Apply.
----End
Result
l After an alarm is suppressed, the board does not monitor the alarm.
7.16.1.4 Checking Path Alarm Suppression Status

You can view all alarms for which you configure alarm suppression in the network. You can
also restore the suppression status of an alarm to the default value, so that the alarm monitoring
of the service is not affected by improper settings.
Prerequisite
Procedure
1 Click the networkwide maintenance status icon on the toolbar, and the Networkwide
Maintenance Status dialog box is displayed.
2 Choose Alarm Suppression, select one or more NEs from the Object Tree and click ,
view the alarm suppression status for a path.
NOTE
If the queried information is null, it indicates that the alarm suppression is not set for any path.
3 Optional: To restore the suppression status to the default value, right-click and choose
Default from the shortcut menu. Click Apply. A prompt is displayed indicating that the operation
is successful. Click Close.
NOTE
You must be an NM user with "NE operator" authority or higher to set the alarm suppression status for a
path.
----End

7.16.2 Setting Alarm Reversion

You can set alarm reversion so that the status of the alarms reported from this port is displayed
as "no alarm". In this way, these alarms can be suppressed.
7.16.2.1 Setting the Alarm Reversion Mode of an NE
During the new deployment or expansion deployment, you can set alarm reversion modes for
NEs in batches and then set the specific reversion status respectively. Therefore, the alarms,
such as R_LOS, are not displayed in the U2000 user interface. This helps network maintainers
to correctly determine faults.
7.16.2.2 Setting the Alarm Reversion for Specified Resources
During the new deployment or expansion deployment, some reasonable but meaningless alarms
are generated on NEs. You can set the alarm reversion for specified resources and then those
alarms are not displayed in the U2000. This helps network maintainers to determine network
faults in time.
7.16.2.3 Setting Alarm Reversion for a Specified Port
maintainers.
7.16.2.4 Setting Alarm Reversion for an SDH Trail
example, when you configure an SDH trail but not connect cables, the corresponding LOS alarm
is generated. After the alarm reversion is set, the alarm is not displayed. This does not affect the
network monitoring that is performed by maintainers.
7.16.2.5 Checking Path Alarm Reversion Status
You can view all paths for which you configure alarm reversion in the network and modify the
alarm reversion status, to avoid impact on services due to misconfiguration.
7.16.2.1 Setting the Alarm Reversion Mode of an NE

During the new deployment or expansion deployment, you can set alarm reversion modes for
NEs in batches and then set the specific reversion status respectively. Therefore, the alarms,
such as R_LOS, are not displayed in the U2000 user interface. This helps network maintainers
to correctly determine faults.
Prerequisite
Applies to the MSTP and WDM equipment.
After you set the alarm reversion for an NE, the alarm status of the NE in the U2000 is contrary
to the actual alarm status on the NE. To be specific, when alarms are generated on the NE, the
NE does not report the alarms to the U2000.
Currently, you can set the alarm reversion for the following alarms:
l MSTP equipment: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and DDN_ALOS

l WDM equipment: R_LOS and MUT_LOS
Procedure
1 Choose Configuration > NE Batch Configuration > NE Alarm Reversion Mode from the
main menu.
2 In the Object Tree on the left, select one or more NEs, and click .
4 Click Query to query the alarm reversion modes of NEs from the NE side.
6 Select an NE and set Reversion Mode to Automatic Reversion or Manual Reversion.
NOTE
l If you set Reversion Mode to Automatic Reversion, when an alarm of an NE ends, the alarm reversion
is automatically disabled on the NE and the alarm status returns to normal.
l If you set Reversion Mode to Manual Reversion, the alarm status can return to normal only after the
alarm reversion is manually disabled.
l When you set Reversion Mode to Non-Revertive, the alarm reversion cannot be set for the NE and
the NE reports alarms in the normal state.
7 Click Apply.
----End
7.16.2.2 Setting the Alarm Reversion for Specified Resources

During the new deployment or expansion deployment, some reasonable but meaningless alarms
are generated on NEs. You can set the alarm reversion for specified resources and then those
alarms are not displayed in the U2000. This helps network maintainers to determine network
faults in time.
Prerequisite
Applies to some alarms of the MSTP and WDM equipment.
Reversion Mode of the NE where the alarm is generated must be set to Automatic
Reversion or Manual Reversion. For details, see 7.16.2.1 Setting the Alarm Reversion Mode
of an NE.

Currently, you can set the alarm reversion for the following alarms:
Procedure
2 In the Filter dialog box, set filter criteria and click OK.
When setting filter criteria, you can filter alarms by equipment according the actual situation.
This helps you to fast locate and analyze the fault of a certain set of equipment.
NOTE
l Alternatively, you can click Copy From Template. In the dialog box that is displayed, select a template
and click OK to import the filter criteria that are defined in the template to the Filter dialog box.
l If you set the startup template for viewing current alarms, the Filter dialog box is not displayed and
the alarms that meet the filter criteria are displayed directly.

3 In the alarm list, select one or more alarms, right-click, and choose Alarm Reversion from the
shortcut menu.

NOTE
If one or more alarms of the selected alarms support the alarm reversion, the Alarm Reversion shortcut
menu item is available. The alarm reversion is set for only the alarms that support the function.
If all selected alarms do not support the alarm reversion, the Alarm Reversion shortcut menu item is grayed
out.
----End
Result
l On the corresponding ports of the specified resources, Reversion Status of the alarms is
changed to Enabled.
l If the alarm of the specified resource is in the uncleared state, the alarm is changed to the
cleared state automatically.

7.16.2.3 Setting Alarm Reversion for a Specified Port

maintainers.
Prerequisite
If you set the alarm reversion for a port, the displayed status of all alarms that support the alarm
reversion on this port is contrary to their actual status. Currently, you can set the alarm reversion
for the following alarms:
Procedure
1 In the NE Explorer, select the NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
2 Set Reversion Mode to Automatic Restoration or Manual Restoration. Click Apply.

NOTE
After the port alarm is cleared, if you set the Reversion Mode to Automatic Restoration, the reversion
setting is automatically cancelled at the NE side. Thus, the alarm status returns to normal. If the reversion
mode is set to Manual Restoration, the alarm status can return to normal only after the alarm reversion
setting is manually cancelled. If the reversion mode is set to Non-Revertive, you cannot set alarm reversion
at the port.
3 In the NE Explorer, select a board and choose Alarm > Alarm Reversion from the Function
Tree.
4 In the Alarm Reversion, set the Reversion Status to Enabled.
6 Click Close.
----End
Result
l When you set the alarm reversion for a port, the alarm status on this port is opposite to the
actual situation. That is, alarms are not reported even if they exist.
l When you set the alarm reversion for a port, the alarm status of the board does not change,
and the alarm indicator still indicates the actual running status of the equipment.

7.16.2.4 Setting Alarm Reversion for an SDH Trail

example, when you configure an SDH trail but not connect cables, the corresponding LOS alarm
is generated. After the alarm reversion is set, the alarm is not displayed. This does not affect the
network monitoring that is performed by maintainers.
Prerequisite
l You must be an NM user with "network operator" authority or higher.
l The trail must be activated.
l Reversion Mode of the NE where the alarm is generated must be set to Automatic
Reversion or Manual Reversion.
Context
If you set alarm reversion for a trail, all alarms of this trail which support the function are reverted.
You cannot set alarm reversion for a single alarm of the trail. Currently, you can set the alarm
reversion for the following alarms: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and
DDN_ALOS.
Procedure
1 Choose Service > SDH Trail > Manage SDH Trail from the Main Menu.
2 In the Set Trail Browse Filter Criteria dialog box, set the filter criteria and click Filter All.
The trails are displayed in the list.
NOTE
l Click Filter All to refresh and display all the qualified trails.
l Click Secondary Filter to filter the trails that are already displayed.
l Click Incremental Filter to add newly qualified trails to the list without refreshing the trails that are
already displayed.
3 Select one or more trails, click Alarm and select Alarm Reversion from the drop-down list.
NOTE
Alarm reversion is not applicable to the VC4 server trail.
4 In the Alarm Reversion dialog box displayed, set Reversion Status of the trail to Enabled.
5 Click Apply. In the Operation Result dialog box displayed, click Close.
----End
7.16.2.5 Checking Path Alarm Reversion Status

You can view all paths for which you configure alarm reversion in the network and modify the
alarm reversion status, to avoid impact on services due to misconfiguration.
Prerequisite

Procedure
2 Choose Alarm Reversion, select one or more NEs from the Object Tree and click ,
view the alarm reversion status for a path.
NOTE
If the queried information is null, it indicates that the alarm reversion is not set for any port.
3 Optional: Set the alarm reversion status and then click Apply. A prompt is displayed indicating
that the operation is successful. Click Close.
NOTE
l If the alarm reversion is set for a port, the alarm status of this port is opposite to the actual status. That
is, when an alarm exists, the status is displayed as normal. This setting helps filter out negligible alarms.
When alarm suppression is set for a LOS alarm of the port, you cannot set alarm reversion at the same
time.
l You must be an NM user with "NE operator" authority or higher to set the alarm reversion status for
a path.
----End
7.16.3 Setting the Types of Lower Order Services in the VC4 Path
The LP_UNEQ indication can be inserted for the port timeslots that are not configured with
lower order services, only after you set the TUG structure of the VC4 path in the transmit
direction.
Prerequisite
l Applies to the N3SL64 and N4SL16 boards.
Context
When a third-party lower order service enters the local equipment through the VC4 path, you
can monitor the performance of this service. This helps you determine whether the performance
or alarms of this service are of the local equipment. By setting the TUG structure in the receiving
direction of the VC4 path, you can determine the class of the lower order service. If the class of
a third-party lower order service is already determined, you can enable the monitoring of lower
order alarms and set the specific alarms to be monitored, to monitor the performance of the
service.
VC4
Third-party
network
Configured Service
Unconfigured Service

Procedure
1 In the NE Explorer, select a board and choose Configuration > Set TUG Structure from the
Function Tree.
2 Set Direction to Send, and set TUG3-1 Structure Type, TUG3-2 Structure Type and TUG3-3
Structure Type to Not Configured, VC12 or VC3 as required.
3 Click Apply. Then, in the Operation Result dialog box, click Close.
----End
7.16.4 Monitoring the Alarms and Performance of Lower Order

Services in the VC4 Path
Set the TUG structure in the receiving direction of the VC4 path. By enabling the monitoring
of lower order alarms and setting the specific alarms to be monitored, you can monitor the
performance of the lower order services in the VC4 path of the network.
Prerequisite
Context
service.
VC4
Third-party
network
Configured Service
Procedure
1 In the NE Explorer, select a board and choose Configuration > Set TUG Structure from the
Function Tree.
2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.

4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu. In the Lower Order Performance Management window, select Monitored
Object and set Monitor Status to Enabled.
6 Click Close.
7 In the NE Explorer, select a line board and choose Alarm > Lower Order Path Alarm from
the Function Tree.
8 Select Level and double-click Type of Monitored Alarm to set the alarm monitoring type.
Click OK.
----End
7.16.5 Setting the Insertion Mode for Channels Not Configured

with Services
On the U2000, you can set the insertion mode of alarms in the channel according to the
networking and service requirements.
Prerequisite
Procedure
Tree.
2 Set Insertion Mode to AIS Mode or UNEQ Mode as required.

NOTE
The default insertion mode is UNEQ Mode. In the case of hybrid networking with the third-party network, the
insertion mode can be set to AIS Mode or UNEQ Mode according to the requirements of the third-party network.
----End

7.16.6 Specifying the Port QoS Alarm

You can set the QoS for a port depending on whether there are services on the port or whether
the services are important. In this way, you can effectively manage alarms. You can set the QoS
by specifying the bit error alarm threshold and setting the port switching conditions.
7.16.6.1 Specifying Bit Error Alarm Threshold
You can set an alarm threshold for the board bit error according to the requirement. When the
value of bit error exceeds the threshold, alarms are generated.
7.16.6.2 Enabling AIS Insertion for a Specified Channel
To switch services at a certain port, you need to set the alarm indication signal (AIS) insertion
switch. For services that require good quality of service (QoS), when the U2000 detects a specific
QoS-affecting event (for example, the TIM_P), the U2000 immediately inserts an AIS at the
port. In this way, the related protection mechanism is triggered and the service at this port is
switched to a protection channel to guarantee the QoS. You can also insert an AIS at the port
and then query the opposite NE, either in the upstream direction or in the downstream direction,
to see whether any alarm is generated. In this way you can check the correctness and connectivity
of a trail.
7.16.6.3 Enabling UNEQ Insertion for a Specified Path
7.16.6.1 Specifying Bit Error Alarm Threshold

You can set an alarm threshold for the board bit error according to the requirement. When the
value of bit error exceeds the threshold, alarms are generated.
Prerequisite
Procedure
1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > Bit Error Alarm
Threshold from the Function Tree.
NOTE
You can set the bit error alarm thresholds for the ports that the trail traverses. In the trail management window,
select a trail, click Alarm and select Alarm Threshold from the drop-down list.
2 Set the related threshold according to the requirement.

NOTE
There are two types of bit error thresholds for the excessive bit error and signal degrade.
3 Click Apply. The Warning dialog box is displayed.
5 Click Close.
----End

7.16.6.2 Enabling AIS Insertion for a Specified Channel

To switch services at a certain port, you need to set the alarm indication signal (AIS) insertion
switch. For services that require good quality of service (QoS), when the U2000 detects a specific
QoS-affecting event (for example, the TIM_P), the U2000 immediately inserts an AIS at the
port. In this way, the related protection mechanism is triggered and the service at this port is
switched to a protection channel to guarantee the QoS. You can also insert an AIS at the port
and then query the opposite NE, either in the upstream direction or in the downstream direction,
to see whether any alarm is generated. In this way you can check the correctness and connectivity
of a trail.
Prerequisite
l Applies to the equipment of SDH series equipment.
l Applies to the equipment of RTN series equipment.
l Applies to the equipment of PTN series equipment.
l Applies to the OptiX Metro 6100 of the WDM series.
Procedure
1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > AIS Insertion from the
Function Tree.
2 Select Port/Path and set the event you concern to Enabled.
3 Click Apply.
The Operation Result is displayed.
4 Click Close.
----End
7.16.6.3 Enabling UNEQ Insertion for a Specified Path

Prerequisite
l Applies to the SDH and RTN equipment. The PDH tributary board must be created.
Context
NOTE
This operation may affect services.
Procedure
1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > UNEQ Insertion
Switch from the Function Tree.

2 Click Query to query the UNEQ insertion status of each Port/Path from the NE.
3 Set the UNEQ insertion switch for each Port/Path as required.

NOTE
The UNEQ has the two switches, LOS and Path Not Used.
4 Click Apply.
----End
7.16.7 Configuring Alarm Insertion

For convenient commissioning and maintenance, you can manually insert an alarm or a
maintenance signal that can causes an alarm into a port of a trail. Thus, you can check the
correctness, connectivity and transmission performance of the trail connection by querying
whether any alarm occurs at opposite ends (upstream or downstream).
7.16.7.1 Inserting an Alarm at a Specified Path

To facilitate the commissioning and maintenance, you can intentionally insert an alarm at a port
of a trail to see whether any alarm is generated at the opposite end (upstream or downstream).
This is a way to check the connectivity and correctness of a trail.
7.16.7.2 Inserting an Alarm on an SDH Trail
In the case of an SDH trail of VC4 level, during maintenance, you can manually insert an MS-
AIS or MS-RDI alarm at the source end of the trail. If the sink end of the trail can correctly
receive the alarm, it indicates that the trail works normally.
7.16.7.3 Checking Path Alarm Insertion Status
You can view all paths for which you configure alarm insertion in the network and modify the
alarm insertion status, to avoid impact on services due to misconfiguration.
7.16.7.1 Inserting an Alarm at a Specified Path

To facilitate the commissioning and maintenance, you can intentionally insert an alarm at a port
of a trail to see whether any alarm is generated at the opposite end (upstream or downstream).
This is a way to check the connectivity and correctness of a trail.
Prerequisite
Context
This operation may affect services.
Procedure
1 In the NE Explorer, select a board and choose Alarm > Alarm Insertion from the Function
Tree.
2 Select a path from Monitored Object to insert an alarm.
3 Select an alarm whose Insertion Status is Not Inserting. Click Insert.

The information about the alarm inserted to the specified path is displayed in the Inserted Alarm
List pane.
4 Repeat Steps 2 through 3 to inset more alarms to different paths.
5 Optional: To stop the alarm insertion, select one or more alarms from the Inserted Alarm
List pane, and click Clear.
----End
7.16.7.2 Inserting an Alarm on an SDH Trail

In the case of an SDH trail of VC4 level, during maintenance, you can manually insert an MS-
AIS or MS-RDI alarm at the source end of the trail. If the sink end of the trail can correctly
receive the alarm, it indicates that the trail works normally.
Prerequisite
You must be an NM user with "network operator" authority or higher.
Procedure
1 Choose Service > SDH Trail > Manage SDH Trail from the Main Menu.
2 In the Set Trail Browse Filter Criteria dialog box displayed, set the filter criteria and click
Filter All. The trails are displayed in the list.
NOTE
l Click Filter All to refresh and display all the qualified trails.
l Click Secondary Filter to filter the trails that are already displayed.
l Click Incremental Filter to add newly qualified trails to the list without refreshing the trails that are
already displayed.
3 Select a VC4 trail or VC4 server trail. Click Maintenance and choose Alarm Insertion from
the drop-down menu.
4 In the Alarm Insertion dialog box displayed, set the value of AIS Alarm Insertion or RDI
Alarm Insertion to Insert.
5 Click Apply. In the Operation Result dialog box displayed, click Close.
----End
7.16.7.3 Checking Path Alarm Insertion Status

You can view all paths for which you configure alarm insertion in the network and modify the
alarm insertion status, to avoid impact on services due to misconfiguration.
Prerequisite

Procedure
2 Choose Alarm Insertion, select one or more NEs from the Object Tree and click , view
the alarm insertion status for a path.
NOTE
If the queried information is null, it indicates that the alarm insertion is not set for any path.
3 Optional: Set the alarm insertion operation and then click Apply. A prompt is displayed
indicating that the operation is successful. Click Close.
CAUTION
Inserting alarm may interrupt the service.
NOTE
You must be an NM user with "NE operator" authority or higher to set the alarm insertion operation for a
path.
----End
7.16.8 Inserting a Maintenance Signal to the ODU Layer

The alarm insertion at the ODU layer includes the AIS insertion, CLK insertion and OCI
insertion. The alarm insertion at the ODU layer is for the purpose of commissioning and
maintenance.
Prerequisite
l Applies to the WDM equipment.
Procedure
1 In the NE Explorer, select a board and choose Configuration > WDM Interface from the
Function Tree.
2 Click the Overhead Byte tab.
3 To query the details about the alarm inserted at the ODU layer from the NE, do as follows:
l Click Quick Query to query the information about the selected parameters from the NE.
l Click Query to query the information about all the parameters from the NE.
4 Set AIS Insertion in the ODU Layer, LCK Insertion in the ODU Layer and OCI Insertion
in the ODU Layer as required.

CAUTION
Configuring the parameter LCK Insertion in the ODU Layer as Enabled for PM overhead
may interrupt service.
5 Click Apply.
----End
7.16.9 Setting NE Alarm Attributes

NE alarm attributes include the storage mode, reversion mode, correlation suppression of the
alarm, and alarm delay. You can set NE alarm attributes to effectively decrease the occurrence
frequency of invalid alarms and to improve the efficiency of alarm monitoring.
7.16.9.1 Setting the Saving Mode for NE alarms

You can set different saving modes for NE alarms. Based on different saving modes, the NE
alarm register follows different rules to save the alarm information. This function helps in fault
analysis.
7.16.9.2 Setting the Enabling Status of NE Alarm Correlation Suppression
You can enable or disable the NE alarm correlation suppression. This function helps you focus
on the root alarms or the services that you concern the most.
7.16.9.3 Querying NE Alarm Correlation Rules
By default, the alarm correlation rules are configured for an NE. After the Alarm Correlation
Rules is enabled, an NE only reports the root alarm to the U2000 according to the alarm
correlation rules. By querying the alarm correlation rules of an NE, you can query the suppression
rules of NE alarms.
7.16.9.4 Setting NE Alarm Delay
You can set NE alarm delay to effectively prevent alarms from being transiently reported or
misreported, thus reducing the impact imposed on equipment.
7.16.9.1 Setting the Saving Mode for NE alarms

You can set different saving modes for NE alarms. Based on different saving modes, the NE
alarm register follows different rules to save the alarm information. This function helps in fault
analysis.
Prerequisite
Context
You can set the saving mode for NE alarms to Wrap or Stop.
l Wrap: When the NE alarm register is full, the register discards the earliest alarms to save
the latest alarm information when new alarms are raised. This is the default mode, which
is also the most used one.

l Stop: When the NE alarm register is full, it does not accept any new alarms so that you
cannot be informed of the new alarms. Hence, usually this mode is not used.
Procedure
Tree.
2 Click Query to query the alarm saving mode of the NE from the NE.
3 Set Saving Mode for the NE alarms as follows:

l Double-click the Saving Mode list and choose Wrap or Stop from the drop-down list.
l To set Saving Mode to Wrap, you can click Default.
4 Click Apply.
----End
7.16.9.2 Setting the Enabling Status of NE Alarm Correlation Suppression

You can enable or disable the NE alarm correlation suppression. This function helps you focus
on the root alarms or the services that you concern the most.
Prerequisite
Context
You can set the NE alarm correlation suppression to the following two status: Enabled and
Disabled.
l Enabled: When alarms are raised from an NE, the U2000 records only the root alarm while
suppresses the alarms generated by the root alarm.
l Disabled: When alarms are raised from an NE, the U2000 records all the alarms, including
the root alarm and correlative alarms. By default NEs use this mode.
Procedure
Tree.
2 Click Query to query the enabling status of the NE alarm correlation suppression from the NE.
3 Set Correlation Analysis for the NE alarms as follows:
Double-click the Correlation Analysis list and choose Enabled or Disabled from the drop-
down list.
l Double-click the Correlation Analysis list and choose Enabled or Disabled from the drop-
down list.
l To set Correlation Analysis to Disabled, you can click Default.

4 Click Apply.
----End
7.16.9.3 Querying NE Alarm Correlation Rules

By default, the alarm correlation rules are configured for an NE. After the Alarm Correlation
Rules is enabled, an NE only reports the root alarm to the U2000 according to the alarm
correlation rules. By querying the alarm correlation rules of an NE, you can query the suppression
rules of NE alarms.
Prerequisite
Procedure
Tree.
2 Click the Alarm Correlation Rules tab and query the NE alarm correlation rules from the NE.
3 Click Query and the result is displayed.
----End
7.16.9.4 Setting NE Alarm Delay

You can set NE alarm delay to effectively prevent alarms from being transiently reported or
misreported, thus reducing the impact imposed on equipment.
Prerequisite
Context
l Occurring Delay Time (s): Indicates the duration for the alarm monitoring to persist before
the NE reports a newly raised alarm.
l Clearing Delay Time (s): Indicates the duration for the alarm monitoring to persist before
the NE reports that the alarm is cleared.
Procedure
Tree.
2 Click Query to query the alarm delay status of the NE from the NE side.
3 Set Delayed Report for the NE alarms as follows:

l Double-click the Delayed Report list. Choose Enabled or Disabled from the drop-down
list. If Delayed Report is set to Enabled, you still need to set Occurring Delay Time
(s) and Clearing Delay Time (s).
l To set Delayed Report to Disabled, you can click Default.
4 Click Apply.
5 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
6 Set Occurring delay Time(s) and Clearing delay Time(s) as required.
7 Click Apply.
----End
7.16.10 Enabling the Alarm Monitoring for Lower Order Paths

If you enable the alarm monitoring function for the lower order paths when you configure lower
order services in a VC4 higher order path, you can monitor the alarms of an individual lower
order path.
Prerequisite
l The equipment type must be OptiX OSN 1500, OptiX OSN 2500, OptiX OSN 3500 or
OptiX OSN 7500.
l Lower order service (VC3 or VC12) must be configured on the line board.
Context
When you configure higher order pass-through cross-connections, if you enable the alarm
monitoring function for lower order paths without monitoring lower order services, the
performance is affected.
Procedure
1 In the NE Explorer, select a line board and choose Alarm > Lower Order Path Alarm from
the Function Tree.
2 Click Query to query the alarm monitoring status of the lower order paths from the NE.
3 Select Port and VC4.
4 Set whether to monitor the alarms on the VC3-1, VC3-2 and VC3-3 path.
5 Set Monitor Status for each VC12 path.
6 Click Apply.
----End
7.16.11 Configuring Housekeeping

By browsing housekeeping alarms, the network maintainer can learn the network running
environment in time. This ensures that the equipment runs properly.

7.16.11.1 Configuring Environment Property

You can configure the environment properties. You can set the alarm AID, alarm severity, alarm
type, alarm message, and normal state. When the NE environment changes, an alarm is raised
on the U2000. In NE management, this function is used to set environment alarm attributes.
7.16.11.2 Configuring Control Property
Use this procedure to configure the control property. In NE management and maintenance, this
function is used to set output control attributes for housekeeping.
7.16.11.1 Configuring Environment Property

You can configure the environment properties. You can set the alarm AID, alarm severity, alarm
type, alarm message, and normal state. When the NE environment changes, an alarm is raised
on the U2000. In NE management, this function is used to set environment alarm attributes.
Prerequisite
Applies to OptiX OSN 1800(NA), OptiX OSN 3800A, OptiX OSN 6800A, OptiX OSN 8800 I
(NA), OptiX BWS 1600A, OptiX BWS 1600G(NA).
Procedure
1 In the NE Explorer, select an NE and choose Configuration > Housekeeping Management
from the Function Tree. Click the Environment Property tab.
2 Click Query to update the environment properties.
3 Click New and the Create Environment Alarm Attribute dialog box is displayed.
4 Select appropriate values from AID, Severity and Alarm Type. Enter the Alarm Message.

.
5 Click OK to create a new environment alarm.
6 In the Environment Property window, set the general status of environment alarm inputs and
outputs for the NE in the Normal State field.
7 Click Apply.
8 The Operation Result dialog box indicating the operation is successful is displayed. Click
Close.
----End
7.16.11.2 Configuring Control Property

Use this procedure to configure the control property. In NE management and maintenance, this
function is used to set output control attributes for housekeeping.
Prerequisite
Applies to OptiX OSN 1800(NA), OptiX OSN 3800A, OptiX OSN 6800A, OptiX OSN 8800 I
(NA), OptiX BWS 1600A, OptiX BWS 1600G(NA).
Procedure
1 In the NE Explorer, select an NE and choose Configuration > Housekeeping Management
from the Function Tree. Click the Control Property tab.
2 Click Query to update the current control property.
3 Click New, and the Create Control Alarm Attribute dialog box is displayed.
4 Select AID, Control Type and State.

5 Click OK to create a new control alarm.

6 Optional: Click Release for Several Seconds or Operate for Several Seconds to set Control
State of the control property. The Control State starts counting down and returns to the original
control state after passing the persistence time.
7 The Operation Result dialog box indicating the operation is successful is displayed. Click
Close.
----End

Operation Guide for Common Features 8 Performance Management(MSTP&WDM&RTN)
8 Performance Management
(MSTP&WDM&RTN)
About This Chapter
To ensure the normal functioning of the network, the network management and maintenance
personnel should periodically check and monitor the network by taking proper performance
management measures.
8.1 Basic Concept

You can use the performance management function to determine the potential risks of the
network running and to reduce the network failure risks. You need to know some basic concepts
before perform operations of performance monitoring.
8.2 Viewing Performance Data
To know whether potential problems that affect services and that are not accompanied by alarms,
exist in the network, view the performance data and take the necessary steps to avoid these
problems.
8.3 Viewing RMON Performance Data
To know whether potential problems that affect Ethernet services and that are not accompanied
by alarms, exist in the network, view the performance data. Then, take the necessary steps to
avoid these problems.
8.4 Managing Lower Order Performance Data
You can set the TUG structure to monitor the performance data of the lower order services in
VC4s in the N3SL64 and N4SL16 boards. The maintenance personnel manage lower order
performance data, to monitor and analyze the running status of lower order services.
8.5 Creating Performance Threshold Templates
Setting an individual performance threshold for each NE is time-consuming. Hence, the
U2000 provides an easy way to set performance thresholds for multiple NEs by means of a
performance threshold template.
8.6 Setting the Board Performance Threshold
The NE reports an event when it detects that a performance value exceeds the specified threshold.
According to the requirement, you can set different performance thresholds for a board, port, or
channel. If you have already created a performance threshold template, you can set performance
thresholds for one or more boards, ports, or channels at the same time.

8 Performance Management(MSTP&WDM&RTN) Operation Guide for Common Features
8.7 Customizing a Performance Event Monitoring Status Template

The U2000 provides the function of customizing performance event monitoring status templates.
By using the function, you can fast and conveniently set the monitoring and reporting of
performance events for multiple cards that may be on different NEs. By customizing a
performance event monitoring status template, you can fast and bulk set the monitoring of
performance events for multiple NEs. This helps to improve the maintenance efficiency.
8.8 Setting Performance Monitoring Parameters
By setting performance monitoring parameters of a specified NE or board properly, and starting
the performance monitoring for this NE or board, you can obtain the detailed performance record
during the running of the NE or board. This facilitates the performance status monitoring of
services and NEs.
8.9 Setting RMON Performance Monitoring Parameters
By setting RMON performance monitoring parameters of an Ethernet board properly, starting
the RMON performance monitoring for this board, and setting the automatic reporting status of
the RMON performance data, you can obtain the detailed performance record during the running
of the Ethernet board.
8.10 Dumping Performance Data
The performance data should be dumped in time to avoid the overflow of the performance data
or damage. You can manually dump the performance data or set the performance dumping
conditions so that the U2000 automatically dumps the data. There are two types of automatic
dumping, which are overflow-triggered dumping and scheduled dumping.
8.11 Collecting the History RMON Performance Data
Set parameters related to the object and performance event. In this way, the U2000 can
automatically and periodically collect the history RMON performance data.
8.12 Periodically Collecting the Performance Data
If you need to periodically query and handle the performance data, you can use the function of
periodical performance data collection. This function can periodically simulate the user
operation of querying the performance data, and export the query result to a text file. This helps
reduce the repeated operations that would otherwise be performed by you.
8.13 Analyzing History Performance Data
To know the operational status of the equipment, you can analyze the history performance data
recorded on the U2000 or on the NE.
8.14 Forecasting the Failure Time of the Laser
According to the changes in the history performance data of an optical component that is stored
in the U2000, the U2000 can forecast when the optical component fails or what the performance
value of an optical component is at a given time. In this way, you can decide when to replace
the optical component.
8.15 Resetting Performance Registers
After a network test or fault recovery, you need to reset the performance register to enter a new
performance monitoring period.
8.16 Power Consumption Management
To ensure the normal running of a network, network management and maintenance engineers
need to regularly check and monitor the power consumption of NEs and boards by taking power
consumption measures.
8.17 Configuring the Q Value Performance Monitoring

Configuring the Q value performance monitoring can query current and history Q value
performance. Also, you can query and set the Q value performance threshold.

8.1 Basic Concept

You can use the performance management function to determine the potential risks of the
network running and to reduce the network failure risks. You need to know some basic concepts
before perform operations of performance monitoring.
8.1.1 Performance Event Type
When the optical transport network is running normally, the internal and external factors, such
as noise sources, dispersion, and fiber break, may affect the transmission quality in the forms of
bit error, jitter, drift, and delay. The influence is called transmission impairment. These
impairments are presented as various performance events on the U2000.
8.1.2 Performance Reporting Process
The performance reporting process starts when the board detects a performance event and ends
when the U2000 informs you the performance event. Performance reporting consists of
procedures such as enabling performance monitoring, automatically reporting the performance .
8.1.3 Performance Monitoring Settings
You can use the function of performance monitoring settings to select different monitoring policy
for monitoring the network performance.
8.1.4 Operation of Viewing Performance Data
You can view the performance data to know the network running quality and finds failure risks
beforehand.
8.1.5 RMON Performance
RMON is used to monitor and evaluate the communication quality of the ports that carry data
services. It is one network management standard that is widely applied. RMON contains
Statistics Group, History Group, History Control Group, and Alarm Group.
8.1.6 Performance Threshold
You can set the performance threshold to mask the performance events that change within the
normal range. In this way, you can focus on the performance events that are severely degraded.
8.1.7 Current Performance and History Performance
Performance data consists of current performance data and history performance data. You can
use the function of viewing performance data to know the running status of services in a specific
time.
8.1.8 Performance Dumping
You can use the performance dumping function to dump the history performance data on the
U2000 to a specified folder as a file. In this way, the running performance of U2000 is improved.
8.1.9 Performance Analysis
The performance analysis function is used to predict the development trend of the performance
value in a specific period in the future. It helps you to make the middle or long term maintenance
plan.
8.1.1 Performance Event Type

When the optical transport network is running normally, the internal and external factors, such
as noise sources, dispersion, and fiber break, may affect the transmission quality in the forms of
bit error, jitter, drift, and delay. The influence is called transmission impairment. These
impairments are presented as various performance events on the U2000.

The performance is different from an alarm. When a performance event is reported, the service
is not interrupted. The transmission quality, however, is degraded compared to the normal
situation and the degradation is temporarily compensated by the error correction mechanism of
the equipment. As the degradation factors increases, the performance threshold crossing and
even an alarm may occur.
You can use the performance management function to detect the degrade trend and to handle
the trouble before the failure actually occurs.
The indicator of a performance event is mainly reflected by the performance value.
NOTE
For example, in FEC_BEF_CORER_FLOAT, FEC_AFT_CORER_FLOAT, FEC-AFTCOR-ER(BER) and
FC-BEFCOR-ER(BER) four performance events about BER, the performance values show the BER before FEC
and BER after FEC as well as the Q factor (unit: dB) converted from the BERs. The Q-factor is basically another
kind of description of BER, and its advantage is that it has the potential to show the system margin simply in
decibel unit.
Q factors are converted from BERs as follows:
If the BER is very small (close to the smallest real number of the OS 1e-307) or very big (up to 0.15) while the
transmission system functions properly, the BER before the FEC is not displayed. In this case, no Q factor is
converted from BERs.

The performance reporting process starts when the board detects a performance event and ends
when the U2000 informs you the performance event. Performance reporting consists of
procedures such as enabling performance monitoring, automatically reporting the performance .
Figure 8-1 shows the process for reporting a performance event.

Figure 8-1 Performance reporting process
Enable performance N
End
monitoring
The board collects the

performance monitoring
result and saves it to the
performance register
The current Report to the NMS as a

Y
performance crosses performance exception
the threshold event
Enable automatic N
End
reporting
Report the performance

data to the NMS and save it
to the database
Description
l Performance Monitoring
Performance monitoring is realized on the board. By default, the board performance
monitoring is enabled. For example, if 15-minute performance monitoring is set. Every
time when a period starts, the board finds a free performance register and clears the data.
Then, the board starts to count the performance events. When the monitoring period ends,
the performance data is updated to the register.
NOTE
The data in the performance register supports wrapped saving.

l Automatic Reporting
If the automatic reporting function is enabled, the SCC board automatically reports the
performance event to the U2000 when a performance monitoring period ends.

NOTE
The reporting of performance data shares DCC bandwidth with the reporting of normal NE
management information and the reporting of large performance data affects the network
communication. As a result, you are not recommended to modify the configuration of performance
reporting. By default, the performance monitoring can be available in the entire network but the
function of automatically reporting the performance events should be configured only at the ports
that have potential failure risks.
l Performance Threshold Reporting
If the U2000 detects the performance threshold crossing, it reports the problem as an
abnormal event of performance threshold crossing. The abnormal event of performance
threshold crossing is different from other abnormal events. The U2000 has special handling
and supports special setting of the abnormal event of performance threshold crossing.
Related Tasks

You can use the function of performance monitoring settings to select different monitoring policy
for monitoring the network performance.
You can set the performance monitoring parameters described as follows on the U2000.
NE Time Synchronization
NE Time Synchronization is used to keep consistency between the NE time and the system time
of the U2000 server , the time of the network time protocol (NTP) server or the time of the
standard network time protocol (NTP) server. After the setting, the U2000 supports
automatically synchronizing the NE time periodically.
NE Performance Monitoring Parameters

The U2000 supports setting the starting or stopping, type, start time and end time of the NE
performance monitoring.
Performance Monitoring Object and Automatic Reporting Status

The U2000 can set the monitoring objects. It can also set the 15-minute automatic reporting or
24-hour automatic reporting.
Performance Threshold
When an NE detects that a certain performance value is beyond the specified threshold, the NE
reports the corresponding performance threshold crossing event. The performance threshold can
divided into two types.
l Single threshold: When the performance count value reaches or exceeds the single
threshold, a performance threshold crossing event is generated on the NE. When the
performance count value is smaller than the single threshold, an event is generated on the
NE indicating that the performance threshold crossing ends.
l Double Thresholds: When the performance count value is beyond the range between the
upper and lower thresholds, a performance threshold crossing event is generated on the NE.

If the performance count value is in the range between the upper and lower thresholds, an
event is generated on the NE indicating that the performance threshold crossing ends.
NOTE
If you want to set a large number of performance threshold values, you can use the template that the
U2000 provides to customize the performance threshold values.
UAT Automatic Reporting

You can set whether an NE automatically reports the event to the U2000 when the NE detects
an unavailable time (UAT) performance event.
The occurrence of ten consecutive severely errored seconds (SESs) indicates the UAT. The UAT
starts at the beginning of the ten seconds. The occurrence of ten consecutive non-SESs indicates
the end of the UAT and that the available time starts.
Automatic Reporting of Performance Threshold Crossing

After you set the automatic reporting of the performance threshold crossing, if a performance
threshold crossing event is generated on the NE, the NE automatically reports the event to the
U2000.
You can set this parameter to monitor the performance events of certain objects.
Related Tasks

You can view the performance data to know the network running quality and finds failure risks
beforehand.
The operation of viewing performance data includes the following: viewing current performance
data, viewing history performance data, viewing UAT record, viewing automatically reported
UAT, viewing performance threshold crossing record,viewing automatically reported
performance threshold crossing, resetting the NE performance register, and viewing the RMON
performance data at the Ethernet port and that of the service objects.
You can use a performance filtering template to view the performance events related to NEs or
boards on NEs quickly.
Related Tasks

RMON is used to monitor and evaluate the communication quality of the ports that carry data
services. It is one network management standard that is widely applied. RMON contains
Statistics Group, History Group, History Control Group, and Alarm Group.

Statistics Group
Statistics group information indicates the statistic value of every monitoring port on the
equipment. It collects statistics on the accumulated or incremental information after the statistics
group is created.
You can use the function of RMON statistics and management to monitor the using status of the
port and collect statistics on the faults occurs when the port is used.
History Group
After the RMON history group is configured, the port periodically collects the network statistics
information. The statistics information is temporarily saved for easy handling. You can view the
history groups to read the statistics information.
History Control Group

You can set the history control group to modify the method that the port obtains the statistics
information of history groups.
Alarm Group
You can set the alarm group to monitor the specified alarm variables such as port statistics data.
When the value of the monitored data is beyond the defined threshold, an alarm occurs. You can
handle the alarm based on the alarm definition.
RMON Setting
The RMON settings mainly refer to the settings of the collection period of the monitored object,
the monitoring period of each event and the threshold detection. By setting the RMON, you can
collect the history performance data of the monitored objects on the U2000. You can set the
RMON in batches by using the templates.
Related Tasks
8.9.6 Setting Performance Monitoring Parameters of an Alarm Group for an Ethernet Port
8.9.7 Setting Performance Monitoring Parameters of a History Control Group for an Ethernet
Port

You can set the performance threshold to mask the performance events that change within the
normal range. In this way, you can focus on the performance events that are severely degraded.
Threshold, also called tolerance, is the extreme value that supports the normal running of the
transport network. The performance threshold is used to check whether the equipment is
normally running. If a certain performance index exceeds the threshold, you need to notice the
performance degrade and handle it.
Normally, you need to leave some margin when setting the performance threshold to ensure that
you determine the problem beforehand.
Related Tasks

8.1.7 Current Performance and History Performance

Performance data consists of current performance data and history performance data. You can
use the function of viewing performance data to know the running status of services in a specific
time.
Current Performance
Current performance means the data that is saved in the current performance register of an NE.
The current performance can be classified as 15-minute current and 24-hour current based on
the monitoring period. When the current performance is viewed, the U2000 queries the
performance data from the current performance register on the NE side.
History Performance
History performance means the performance data that the NE detects in a specific period in the
past. When the history performance data is queried, the system queries the performance data
from the NE side or from the NM side depending on the location in which the data is saved.
The ended current performance data is dumped to the history performance register of the NE.
The process for synchronizing the history performance data in the NE history performance
register to the database on the NM side is described as follows.
l After the automatic reporting of performance events is enabled on an NE, the NE
automatically reports the performance event every time the monitoring period of the current
performance ends. After the U2000 receives the event, it automatically saves the event to
the history performance database.
NOTE
Once the U2000 receives the performance event, it immediately gathers new current history data.
l When you query the NE history performance data on the U2000, the U2000 updates the
contents that are not wrapped in the NE history performance register to the database.

You can use the performance dumping function to dump the history performance data on the
U2000 to a specified folder as a file. In this way, the running performance of U2000 is improved.
When an NE is running, a large number of performance data is generated. If the data is reported
to the U2000, it is saved to the U2000 database. If the history performance data that is stored on
the U2000 exceeds a certain limit, the U2000 operations is severely affected. In certain cases,
the entire system may be crashed. Hence, you can set automatic dumping or periodical dumping
on the U2000. After you set the parameters about dumping, the U2000 automatically dumps the
data in the history library to a file to reduce the loads of the U2000 computer. You can manually
back up or delete the dumped files.
Normally, you need not manually configure the performance dumping parameters. In certain
situations, for example, in a large network or if large performance changes occur in the short
period, you can set a higher upper threshold value or a shorter dumping period. Before you
change the dumping parameters, make sure that there is enough free space in the database and
disk. If the speed of filtering history performance data is severely degraded after modification,
you need to fine adjust the parameters later.

Related Tasks

The performance analysis function is used to predict the development trend of the performance
value in a specific period in the future. It helps you to make the middle or long term maintenance
plan.
Work Principle
The performance index of the physical component on an NE develops according to its own
development trend if there are no external factors. The performance analysis function considers
this natural trend and at least five periods of history performance data to predict the trend of the
performance index.
Applied Scenario
If the fibers or services in a subnet of the network often become faulty, you can perform
performance analysis and think of solutions beforehand, such as replacing a board or fiber.
Related Tasks

To know whether potential problems that affect services and that are not accompanied by alarms,
exist in the network, view the performance data and take the necessary steps to avoid these
problems.
8.2.1 Creating a Performance Filtering Template

By creating and modifying performance filtering template, a network maintainer can quickly
view the specific performance events of specific NEs when the maintainer enables the
performance monitoring next time.
8.2.2 Viewing Current Performance Data
The current performance data has 15-minute and 24-hour intervals. To know whether services
are normal within the current period of 15 minutes and 24 hours, you can view the current
performance data.
8.2.3 Viewing History Performance Data
The history performance data has 15-minute and 24-hour intervals. You can view the history
performance data to learn the running status of services in a specified 15-minute or 24-hour
period in the past.
8.2.4 Viewing UAT Records
You can view records of unavailable time (UAT) to know the equipment performance. You can
perform the following subfunctions: view cleared UAT events, view uncleared UAT events,
query UAT events from an NE, and query UAT events from the U2000.
8.2.5 Viewing Performance Threshold Crossings
The threshold crossings have 15-minute and 24-hour intervals. To detect the abnormal services
and handle them in time, you can view the threshold crossings.

8.2.6 Viewing Current Performance Data of an Ethernet Port

You can view the current performance data of an Ethernet port.
8.2.7 Viewing History Performance Data of an Ethernet Port
To know the operational status of Ethernet services through an Ethernet port within a defined
period, you can view the history performance data of an Ethernet port.
8.2.8 Viewing Current Performance Data of an ATM Port
You can view the current performance data of the port to know the operational status of ATM
services through an ATM port.
8.2.9 Viewing History Performance Data of an ATM Port
You can view the history performance data of the port to know the operational status of ATM
services through an ATM port, within a specified period.
8.2.10 Querying the NE Temperature
An NE can work in a normal state only at a proper temperature. When the working temperature
of the NE is too high due to the faulty board or fan, the NE cannot work in the normal state.
8.2.11 Query Ethernet Port Flow Monitoring
By querying the Ethernet port flow monitoring, you can accurately learn the actual bandwidth
usage of the base and then adjust the bandwidth of trails. This helps to improve the bandwidth
utilization.
Related Concepts
8.2.1 Creating a Performance Filtering Template

By creating and modifying performance filtering template, a network maintainer can quickly
view the specific performance events of specific NEs when the maintainer enables the
performance monitoring next time.
Prerequisite
Context
The Filter by Template function involves the following windows: viewing the SDH
performance, viewing the WDM performance, and viewing the control panel performance.
Procedure
1 In the Object Tree on the left of the window for viewing performance, select one or more NEs
or boards on NEs. In filter criteria area of the table on the right of the window, set parameters
for filtering performance events.
2 On the lower portion of the window for viewing performance, click Filter by Template and
select Save. from the drop-down list.
3 In the Enter the Name dialog box, enter the template name and click OK.

NOTE
l After the template is saved, the name of the current template is displayed next to the window title.
l When you save the template, the filtering parameters in only the current window are saved.
l When you modify the original template, select Save from the drop-down list. The template needs not
to be renamed.
----End
8.2.2 Viewing Current Performance Data

The current performance data has 15-minute and 24-hour intervals. To know whether services
are normal within the current period of 15 minutes and 24 hours, you can view the current
performance data.
Prerequisite
l You must be an NM user with "NE monitor" authority or higher.
l The service must be configured.
l The performance monitoring parameters must be set.
l The NE time must be synchronized with the time of the computer where the U2000 is
installed.
l Applies to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.
Procedure
1 In the NE Explorer, select an NE, and navigate to the user interface of viewing the performance
data of boards or service objects in the following ways from the Function Tree.
Equipment Type Application Object Navigation Path
SDH, WDM, PTN, RTN and Physical port Select a desired board and
Submarine equipment choose Performance >
Current Performance from
the Function Tree.
NA WDM equipment Physical port Select a desired board and

choose Performance >
WDM Performance from
the Function Tree. And click
Current Performance
Data tab.

PTN equipment Unicast tunnel Choose Configuration >

MPLS Management >
Unicast Tunnel
Management from the
Function Tree. Select one or
more ingress tunnels, right-
click and choose Browse
Performance from the
shortcut menu. In the dialog
box displayed, click the
Current Performance tab.
PTN equipment MEP point Choose Configuration and

then choose a desired service
type from the Function Tree.
Select one or more MEP
points, right-click and choose
Browse Performance from
the shortcut menu. In the
dialog box displayed, click
the Current Performance
tab.
2 Optional: Complete the following information: Monitored Object Filter Criteria, Monitor
Period and Performance Event Type.
NOTE
All performance events supported by the board are provided as options for setting the performance event.
3 Optional: In the Display Options group box, check the Display Current Value or Display
Maximum and Minimum Values check box.
4 Click Query to query the data from the NE.
5 Optional: Click Reset to reset the performance register of the queried performance event.
NOTE
After the performance register is reset, the current performance data of this type is cleared. Then, a new
performance monitoring period is started.
----End
8.2.3 Viewing History Performance Data

The history performance data has 15-minute and 24-hour intervals. You can view the history
performance data to learn the running status of services in a specified 15-minute or 24-hour
period in the past.
Prerequisite


Procedure
Equipment Type Application Object Entry
SDH, WDM, PTN, RTN and Physical port Select the related board, and
Submarine equipment then choose Performance >
History Performance.
NA WDM equipment Physical port Select a desired board and

choose Performance >
WDM Performance from
the Function Tree. And click
History Performance Data
tab.
PTN equipment Unicast tunnel Click Configuration >

MPLS Management >
Unicast Tunnel
Management. Select one or
multiple ingress tunnels, and
then right-click to choose
Browse Performance. Click
History Group tab.
PTN equipment MEP point Click Configuration to enter

the related service type.
Select one or multiple MEP
points, and then right-click to
choose Browse
Performance. Click History
Group tab.
2 Optional: Complete the information: Monitored Object Filter Criteria, Monitor Period,
From/To, Data Source and Performance Event Type.
NOTE
3 Optional: Select the Display Current Value or Display Maximum and Minimum Values in
the Display Options.
4 Click Query and the information is shown in the lower pane.
5 Optional: Click Graph. Select the Performance Event and Monitor Object in the dialog box.
Click Show to view the graphic result.
NOTE
It only applies to the performance events related to the optical power.

6 Optional: Click Reset to reset the performance registers.

NOTE
After the resetting, the history performance data is delete and a new performance monitoring period is
beginning.
----End
8.2.4 Viewing UAT Records

You can view records of unavailable time (UAT) to know the equipment performance. You can
perform the following subfunctions: view cleared UAT events, view uncleared UAT events,
query UAT events from an NE, and query UAT events from the U2000.
Prerequisite
Procedure
SDH, WDM,PTN, RTN and Physical port Select the related board, and
UAT Event.

MPLS Management >
Unicast Tunnel
UAT tab.

choose UAT tab.
2 Optional: Complete the following information: Monitored Object Filter Criteria, start time,
Data Source, Functional Block Type and Display Options. The information displayed
according to your selection.
NOTE
All function blocks supported by the board are provided as options for setting the function block.

3 Click Query to query data from the NE or the U2000.
4 Optional: Click Reset to reset the performance registers.

NOTE
After the resetting, the UAT performance data is delete and a new performance monitoring period is
beginning.
----End
8.2.5 Viewing Performance Threshold Crossings

The threshold crossings have 15-minute and 24-hour intervals. To detect the abnormal services
and handle them in time, you can view the threshold crossings.
Prerequisite
Procedure
SDH, WDM, PTN, RTN and Physical port Select the related board, and
UAT Event.

MPLS Management >
Unicast Tunnel
UAT tab.

choose UAT tab.
2 Optional: Complete the information: Monitored Object Filter Criteria, Monitor Period,
Performance Event Type and start/end time. The information displayed according to your
selection.Display Options and start/end time. The information displayed according to your
selection.

NOTE
3 Click Query to query the data from the U2000.
----End
8.2.6 Viewing Current Performance Data of an Ethernet Port

You can view the current performance data of an Ethernet port.
Prerequisite
l The Ethernet service must be configured.
l Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must be
configured.
Procedure
1 In the NE Explorer, select an Ethernet board and choose Performance > IP Performance Real-
time Monitor from the Function Tree.
2 Select a value from the Monitored Object drop-down list.
3 Select a value from the Monitor Interval(s) and Display Number of Data Column drop-down
lists.
4 Click Query.
----End
8.2.7 Viewing History Performance Data of an Ethernet Port

To know the operational status of Ethernet services through an Ethernet port within a defined
period, you can view the history performance data of an Ethernet port.
Prerequisite
configured.
Procedure
1 In the NE Explorer, select an Ethernet board and choose Performance > IP History
Performance from the Function Tree.
2 Complete the information: Monitored Object, Query Period, and Time Range.

3 Click Query.
----End
8.2.8 Viewing Current Performance Data of an ATM Port

You can view the current performance data of the port to know the operational status of ATM
services through an ATM port.
Prerequisite
The ATM service must be configured.
The performance monitoring parameters must be set.
Applies to the MSTP, WDM, RTN, PTN, submarine equipment.
Procedure
1 In the NE Explorer, select an ATM board and choose Performance > ATM Performance Real-
Time Monitor > Port Performance Data from the Function Tree.
2 Select a port.
3 Complete the following information: Monitor Period, Monitor Interval(s) and Display
Number of Data Column.
4 Click Start.
----End
8.2.9 Viewing History Performance Data of an ATM Port

You can view the history performance data of the port to know the operational status of ATM
services through an ATM port, within a specified period.
Prerequisite
The ATM service must be configured.
The performance monitoring parameters must be set.
Procedure
1 In the NE Explorer, select an ATM board and choose Performance > ATM History
Performance > Port Performance Data from the Function Tree.
2 Complete the following information: Monitored Object, Query Period and time range.
3 Click Query, and the information is displayed in the Query Result pane.
----End

8.2.10 Querying the NE Temperature

An NE can work in a normal state only at a proper temperature. When the working temperature
of the NE is too high due to the faulty board or fan, the NE cannot work in the normal state.
Prerequisite
l The NE time must be synchronized with the time of the computer where the U2000 is
installed.
Procedure
SDH, WDM, PTN and Physical port Select a desired board and
Submarine equipment choose Performance >
Current Performance from
the Function Tree.
2 Complete the following information: Monitored Object Filter Criteria, Monitor Period.
Select the Working Temperature in the performance event type of the Gauge field.
3 Optional: In the Display Options group box, check the Display Current Value or Display
Maximum and Minimum Values check box.
5 Optional: Click Reset to reset the performance register of the queried performance event.
NOTE
After the performance register is reset, the current performance data of this type is cleared. Then, a new
performance monitoring period is started.
----End
8.2.11 Query Ethernet Port Flow Monitoring

By querying the Ethernet port flow monitoring, you can accurately learn the actual bandwidth
usage of the base and then adjust the bandwidth of trails. This helps to improve the bandwidth
utilization.
Prerequisite
Applies to the N4EGS4 board.

Status Monitoring must be set to Enabled for the Ethernet port flow. For details, see 8.8.10
Setting Ethernet Port Flow Monitoring.
The NE collects the data every 15 minutes. An NE can collect the statistics on the flow data of
the Ethernet ports in the latest 30 days from now.
Procedure
1 In the NE Explorer, select an Ethernet board and choose Performance > Ethernet Port Flow
Monitoring from the Function Tree. Click the Query Flow tab.
2 Select a port from the Monitored Object drop-down list. Then, set Start Time, End Time, and
Display Mode.
NOTE
l When Display Mode is set to List, the data of the Ethernet port flow is displayed as a list in the
U2000 user interface.
l When Display Mode is set to Graphics, the data of the Ethernet port flow is displayed as a graph in
the U2000 user interface.
3 Click Query. The flow data on the port within the specific period is displayed.
----End
8.3 Viewing RMON Performance Data

To know whether potential problems that affect Ethernet services and that are not accompanied
by alarms, exist in the network, view the performance data. Then, take the necessary steps to
avoid these problems.
8.3.1 Viewing History Group Performance

You can view the history group performance data. The history group performance data contains
the statistics of Ethernet performance data within a period.
8.3.2 Viewing Statistics Group Performance of an Ethernet Port
To know the real-time statistics, you can view the statistic group performance data of an Ethernet
port.
8.3.1 Viewing History Group Performance

You can view the history group performance data. The history group performance data contains
the statistics of Ethernet performance data within a period.
Prerequisite

Procedure
1 Select the NE in the NE Explorer. To display the performance browse interface for physical
ports or service objects, follow the listed entries in the Function Tree.
SDH, WDM, PTN, RTN and Physical port Select the board and choose
Submarine equipment Performance > RMON
Performance.
PTN equipment Sub-board Select the board and choose

Performance > RMON
Performance.

MPLS Management >
Unicast Tunnel
Management. Right-click
one or several tunnels and
select Browse
Performance.
PTN equipment PW Choose Configuration >

MPLS Management > PW
one or several PWs and select
Browse Performance.
If you need to browse the
RMON performance of the
PW used by each service
type, such as the ATM
service, CES service and
Ethernet service, right-click
one or several PWs in the
corresponding service
interface and select Browse
Performance.
PTN equipment ATM service Choose Configuration >

ATM Service
one or several ATM services
and select Browse
Performance.

PTN equipment CES service Choose Configuration >

CES Service Management.
Right-click one or several
CES services, or right-click
one or several PWs in PW
General Attributes, and
then select Browse
Performance.
NOTE
The UNI-UNI CES service
does not support the
performance browse function.
PTN equipment Ethernet service Choose Configuration >

Ethernet Service. Select one
Ethernet service type, right-
click one or several services,
and then select Browse
Performance.
PTN equipment Link aggregation group Choose Configuration >

Interface Management >
Link Aggregation Group
one or several link
aggregation groups and
select Browse
Performance.
PTN equipment MEP point Click Configuration and

select the corresponding
service type. Right-click one
or several MEP points, and
select Browse
Performance.
2 Click the History Group tab.

3 Complete the information: Select port, performance events, History Table Type, Query
Conditions and Display Mode.
4 Click Query, and the information is shown in the lower pane.
----End
8.3.2 Viewing Statistics Group Performance of an Ethernet Port

To know the real-time statistics, you can view the statistic group performance data of an Ethernet
port.

Prerequisite
l The Ethernet service must be configured. Refer to Configuring Ethernet Services.
Procedure
SDH, WDM, PTN, RTN and Physical port Select the board and choose
Submarine equipment Performance > RMON
Performance.
PTN equipment Sub-board Select the board and choose

Performance > RMON
Performance.

MPLS Management >
Unicast Tunnel
one or several tunnels and
select Browse
Performance.
PTN equipment PW Choose Configuration >

MPLS Management > PW
one or several PWs and select
Browse Performance.
If you need to browse the
RMON performance of the
PW used by each service
type, such as the ATM
service, CES service and
Ethernet service, right-click
one or several PWs in the
corresponding service
interface and select Browse
Performance.
PTN equipment ATM service Choose Configuration >

ATM Service
one or several ATM services
and select Browse
Performance.

PTN equipment CES service Choose Configuration >

CES Service Management.
Right-click one or several
CES services, or right-click
one or several PWs in PW
General Attributes, and
then select Browse
Performance.
NOTE
The UNI-UNI CES service
does not support the
PTN equipment Ethernet service Choose Configuration >

Ethernet Service. Select one
Ethernet service type, right-
click one or several services,
and then select Browse
Performance.
PTN equipment Link aggregation group Choose Configuration >

Interface Management >
Link Aggregation Group
one or several link
aggregation groups and
select Browse
Performance.
PTN equipment MEP point Click Configuration and

select the corresponding
service type. Right-click one
or several MEP points, and
select Browse
Performance.
2 Click the Statistics Group tab.

3 Select a port.
4 Select the performance events. Set the Query Conditions and Display Mode.
5 Click Start.
----End
8.4 Managing Lower Order Performance Data

You can set the TUG structure to monitor the performance data of the lower order services in
VC4s in the N3SL64 and N4SL16 boards. The maintenance personnel manage lower order
performance data, to monitor and analyze the running status of lower order services.

8.4.1 Enabling Performance Monitoring for a Lower Order Path

You can enable performance monitoring for a lower order path, to obtain the detailed
performance data of the lower order path in the running state. The performance data helps the
maintenance personnel to monitor and analyze the running status of services.
8.4.2 Setting the Lower Order Performance Threshold
The NE reports an event when it detects that a lower order performance value exceeds the
specified threshold. According to the requirement, you can set different thresholds for lower
order performance events.
8.4.3 Setting the Lower Order Performance Monitoring Status
After you enable performance monitoring for a lower order path, you can set which performance
events you can monitor for this path.
8.4.4 Viewing Current Lower Order Performance Data
8.4.5 Viewing History Lower Order Performance Data
History lower order performance data has 15-minute and 24-hour intervals. To know the
operational status of services within the period of the last 15 minutes and last 24 hours, you can
view the history performance data.
8.4.6 Viewing UAT Records for a Lower Order Service
If an UAT event occurs in a board, it indicates that the performance of a service is deteriorated,
you need to handle and troubleshoot the UAT event as soon as possible. You can view the UAT
records to monitor the performance of a lower order service.
8.4.7 Viewing Lower Order Performance Threshold-Crossing Records
The lower order performance threshold crossings have 15-minute and 24-hour intervals. To
detect the abnormal services and handle them in time, you can view the threshold crossings.
8.4.1 Enabling Performance Monitoring for a Lower Order Path

You can enable performance monitoring for a lower order path, to obtain the detailed
performance data of the lower order path in the running state. The performance data helps the
maintenance personnel to monitor and analyze the running status of services.
Prerequisite
l Applies to the MSTP equipment.
Context
service.

VC4
Third-party
network
Configured Service
Procedure
1 In the NE Explorer, select a board and select Configuration > Set TUG Structure from the
Function Tree.
shortcut menu. In the Lower Order Performance Management window, select Monitored
Object and set Monitor Status to Enabled.
----End
8.4.2 Setting the Lower Order Performance Threshold

The NE reports an event when it detects that a lower order performance value exceeds the
specified threshold. According to the requirement, you can set different thresholds for lower
order performance events.
Prerequisite
Context

service.
VC4
Third-party
network
Configured Service
Procedure
Function Tree.
shortcut menu. In the Lower Order Performance Management window, click the
Performance Threshold-Crossing Setting tab.
5 Double-click the parameter field, enter the threshold value.
----End
8.4.3 Setting the Lower Order Performance Monitoring Status

Prerequisite
Context

service.
VC4
Third-party
network
Configured Service
Procedure
Function Tree.
5 Set the Monitor Status and Threshold-Crossing Enable Status of a performance event.
----End
8.4.4 Viewing Current Lower Order Performance Data

Prerequisite

Context
service.
VC4
Third-party
network
Configured Service
Procedure
Function Tree.
shortcut menu. In the Lower Order Performance Management window, click the Current
Performance tab.
5 Select the Object, Monitor Period, and duration. Click Query to view the current lower order
performance data. In the Operation Result dialog box, click Close.
----End
8.4.5 Viewing History Lower Order Performance Data

History lower order performance data has 15-minute and 24-hour intervals. To know the
operational status of services within the period of the last 15 minutes and last 24 hours, you can
view the history performance data.
Prerequisite


Context
service.
VC4
Third-party
network
Configured Service
Procedure
Function Tree.
shortcut menu. In the Lower Order Performance Management window, click the History
Performance tab.
5 Select the Object, Monitor Period, Data Source and duration. Click Query to view the history
lower order performance data. In the Operation Result dialog box, click Close.
----End
8.4.6 Viewing UAT Records for a Lower Order Service

If an UAT event occurs in a board, it indicates that the performance of a service is deteriorated,
you need to handle and troubleshoot the UAT event as soon as possible. You can view the UAT
records to monitor the performance of a lower order service.

Prerequisite
Context
service.
VC4
Third-party
network
Configured Service
Procedure
Function Tree.
shortcut menu. In the Lower Order Performance Management window, click the UAT tab.
5 Select the Object, Options, Data Source and duration, and click Query to view the UAT
records.In the Operation Result dialog box, click Close.
----End

8.4.7 Viewing Lower Order Performance Threshold-Crossing

Records
The lower order performance threshold crossings have 15-minute and 24-hour intervals. To
detect the abnormal services and handle them in time, you can view the threshold crossings.
Prerequisite
Context
service.
VC4
Third-party
network
Configured Service
Procedure
Function Tree.

5 Select the Object, Monitor Period, Options and duration. Click Query to view threshold
crossings. In the Operation Result dialog box, click Close.
----End

Setting an individual performance threshold for each NE is time-consuming. Hence, the
U2000 provides an easy way to set performance thresholds for multiple NEs by means of a
performance threshold template.
Prerequisite
Procedure
1 Choose Performance > Performance Template Management > Performance Threshold
Template from the main menu.
2 In the case of the SDH/WDM NE.
1. Select the SDH/WDM tab.
2. Select a template from the Template Name drop-down list.
NOTE
If a newly-created performance threshold template does not exist, you can only select the Default
Template.
3. Modify the performance thresholds as required.
4. Save the template, you can choose one of the following methods:
NOTE
l Click Save to save the modification.

l To save as a new template, click Save As and enter a template name.
5. The Operation Result dialog box is displayed. Click Close.
3 In the case of the SONET/NA WDM NE.
1. Select the SONET/NAWDM tab.
2. Select a template from the Template Name drop-down list.
NOTE
If a newly-created performance threshold template does not exist, you can only select the Default
Template.
3. Modify the performance thresholds as required.
4. Save the template, you can choose one of the following methods:
NOTE
l Click Save to save the modification.

l To save as a new template, click Save As and enter a template name.
5. The Operation Result dialog box is displayed. Click Close.
----End

Related Concepts
Related Tasks

The NE reports an event when it detects that a performance value exceeds the specified threshold.
According to the requirement, you can set different performance thresholds for a board, port, or
channel. If you have already created a performance threshold template, you can set performance
thresholds for one or more boards, ports, or channels at the same time.
Prerequisite
Procedure
1 In the NE Explorer, select the NE. In the Function Tree, enter the performance browsing interface
of the board or service object in the following way.
Application Object Entry
Physical port Select the related board, and then choose

Performance > Performance Threshold.
Unicast tunnel Choose Configuration > MPLS

Management > Unicast Tunnel
Management. Select one or multiple tunnels,
and then right-click to choose Browse
Performance. Click the Performance
Threshold-Crossing Setting tab.
MEP point Click Configuration to enter the related

service type. Select one or multiple MEP
points, and then right-click to choose Browse
Performance. Click the Performance
Threshold-Crossing Setting tab.
2 In the Monitor Object pane, select the desired board, port, or channel.
3 Set performance thresholds according to the requirement.

NOTE
If you have already created a performance threshold template for the boards, click Use Template and select
the desired template. Click Open.
4 Optional: Click Default to restore the default settings.

5 Click Apply.
----End
Related Concepts
Related Tasks
8.7 Customizing a Performance Event Monitoring Status

Template
The U2000 provides the function of customizing performance event monitoring status templates.
By using the function, you can fast and conveniently set the monitoring and reporting of
performance events for multiple cards that may be on different NEs. By customizing a
performance event monitoring status template, you can fast and bulk set the monitoring of
performance events for multiple NEs. This helps to improve the maintenance efficiency.
Prerequisite
It is applicable to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.
Procedure
1 Choose Performance > Performance Template Management > Performance Event
Monitor Status Template from the main menu.
2 Select a desired template from the Template Name drop-down list.

NOTE
When you customize the first performance event monitoring status template, you can set Template
Name to Default Template only.
3 Optional: Click Refresh to refresh the information about the template.

4 According to the actual monitoring requirement, select a performance event and changes the
values of the corresponding Monitor Status, 15-Minute Auto-Report, and 24-Hour Auto-
Report parameters.
NOTE
When you set the Monitor Status parameter of a performance event to Disabled, the corresponding 15-
Minute Auto-Report and 24-Hour Auto-Report parameters are automatically changed to Disabled and
grayed out.
5 You can save the performance event monitoring status template as follows:
l Click Save to directly save the modification.
NOTE
The default template cannot be directly saved. That is, the Save button is grayed out for the default
template.
l Alternatively, you can click Save As to save the template as a new template and enter the
name of the new template.
6 In the Operation Result dialog box, click Close.
7 Optional: Click Apply to. In the Apply to dialog box, select the objects that you apply the
template to and click OK. In the Operation Result dialog box, click Close to apply the template
to the selected objects in batches.
NOTE
You can apply a performance event monitoring status template to optical NEs, NEs, and cards.
----End
Related Tasks
8.8.7 Setting Performance Monitoring Parameters of a Board

By setting performance monitoring parameters of a specified NE or board properly, and starting
the performance monitoring for this NE or board, you can obtain the detailed performance record
during the running of the NE or board. This facilitates the performance status monitoring of
services and NEs.
8.8.1 Setting the Performance Reporting Status for a Single NE
After you disable the performance auto-reporting of a specified NE, and then the NE does not
report any performance events automatically to the NM when the performance events on the NE
are raised.
8.8.2 Setting the Performance Reporting Status for Multiple NEs
After you disable the performance auto-reporting of multiple specified NEs, the NEs do not
report anyperformance events automatically to the NM when the performance events on the NEs
are raised.

are raised.
8.8.4 Setting Performance Monitoring Parameters of an NE
By setting performance monitoring parameters of an NE properly and starting the performance
monitoring for the NE, you can obtain the detailed performance record during the running of
the NE. This facilitates the monitoring and analysis of the NE running status performed by
maintenance personnel.
8.8.5 Setting IP Performance Monitoring Parameters of an NE
By setting IP performance monitoring parameters of an NE properly and starting the IP
performance monitoring for the NE, you can obtain the detailed IP performance record during
the running of the NE.
8.8.6 Setting ATM Performance Monitoring Parameters of an NE
By setting ATM performance monitoring parameters of an NE properly and starting the ATM
performance monitoring for the NE, you can obtain the detailed ATM performance record during
You can set the monitoring status and the automatic reporting status of monitored objects. The
U2000 monitors the performance of all boards in the network, but the automatic reporting feature
is disabled by default. You can modify the value of the attribute according to the requirement.
8.8.8 Setting IP Performance Monitoring Parameters of a Board
By setting IP performance monitoring parameters properly and starting the IP performance
monitoring of a specified board, you can obtain the detailed IP performance record during the
running of the board.
8.8.9 Setting ATM Performance Monitoring Parameters of an ATM Board
By setting ATM performance monitoring parameters of an ATM board properly and starting the
performance monitoring for the ATM board, you can obtain the detailed performance record
during the running of the board. This facilitates the monitoring and analysis of the board running
status performed by maintenance personnel.
8.8.10 Setting Ethernet Port Flow Monitoring
By setting the Ethernet port flow monitoring, you can monitor the flow of the Ethernet port and
display the flow data of the last month on the U2000.
Related Concepts

are raised.
Prerequisite
Applies to the WDM NA NE.

Procedure
1 In the NE Explorer, select the NE and choose Configuration > NE Attribute from the Function
Tree.
2 Click the Status Reporting drop-down list and select Enable Performance Report to enable
the performance reporting status. A dialog box is displayed indicating that the operation was
successful.
NOTE
If you click Disable Performance Report, the NE does not report any performance events automatically
to the NM when the performance events are raised. However, you can query these performance events
from the NE manually.
3 Click Close.
----End
8.8.2 Setting the Performance Reporting Status for Multiple NEs

After you disable the performance auto-reporting of multiple specified NEs, the NEs do not
report anyperformance events automatically to the NM when the performance events on the NEs
are raised.
Prerequisite
Applies to the WDM NA NEs.
Procedure
1 Choose Configuration > NE Batch Configuration > NE Reporting Status Management from
the main menu.
2 Select NEs from the left-hand pane and click the double-right-arrow button (red).
3 Click Query to query the current performance reporting status from all the NEs.
4 Select an NE, double-click Performance Reporting Status field to activate the drop-down
menu, and then choose ENABLED or DISABLED.
NOTE
If you choose DISABLE, the NE does not report any performance events automatically to the NM when
the performance events are raised. However, you can query these events from the NE manually.
5 Click Apply.
----End


are raised.
Prerequisite
Applies to OptiX PFE 1670.
Procedure
1 Double-click an NE on the Main Topology.
2 Right-click the NE Panel and choose NE Reporting Status from the shortcut menu.
3 Click the Performance Reporting Status drop-down list and select Enabled to enable the
performance reporting status. A dialog box is displayed indicating that the operation was
successful.
NOTE
If you click Disabled, the NE does not report any performance events automatically to the NM when the
performance events are raised. However, you can query these performance events from the NE manually.
4 Click Apply.
5 Click Close in the Operation Result dialog box. The "Operation succeeded" information
indicates that the operation was successful.
----End
8.8.4 Setting Performance Monitoring Parameters of an NE

By setting performance monitoring parameters of an NE properly and starting the performance
monitoring for the NE, you can obtain the detailed performance record during the running of
the NE. This facilitates the monitoring and analysis of the NE running status performed by
maintenance personnel.
Prerequisite
The NE time must be synchronized with the U2000 server time.
Procedure
1 Choose Performance > Set NE Performance Monitoring Time from the main menu.
2 Select NEs from the NE list. Click .

4 Select one or more NEs, and set 15-minute and 24-hour performance monitor parameters
according to the requirement.
NOTE
l The start time must be later than the current time of the network management system and the end time
must be later than the start time.
l If the end time is not set, this indicates that the performance monitoring starts from the start time and
does not stop.
5 Click Apply and then click Close in the Operation Result dialog box.
----End
8.8.5 Setting IP Performance Monitoring Parameters of an NE

By setting IP performance monitoring parameters of an NE properly and starting the IP
performance monitoring for the NE, you can obtain the detailed IP performance record during
Prerequisite
Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must be
configured.
NE time is synchronized with the U2000 server.
Procedure
1 In the NE Explorer, select an NE and choose Performance > IP Performance Monitor
Period from the Function Tree to set the monitor period.

3 Click Close.
4 In the NE Explorer, select an NE and choose Performance > IP Performance Monitor

Time from the Function Tree.
5 Select the Enabled option button.
6 Set the Start Time and End Time.
7 Click Apply and the Operation Result dialog box is displayed.
8 Click Close.
----End
8.8.6 Setting ATM Performance Monitoring Parameters of an NE

By setting ATM performance monitoring parameters of an NE properly and starting the ATM
performance monitoring for the NE, you can obtain the detailed ATM performance record during
Prerequisite
The ATM board must be installed.
NE time is synchronized with the U2000 server.
Procedure
1 In the NE Explorer, select an NE and choose Performance > ATM Performance Monitor
Period from the Function Tree to set the monitor period.
3 Click Close.
4 In the NE Explorer, select an NE and choose Performance > ATM Performance Monitor
Time from the Function Tree.
5 Specify the Monitor Period and select the Enabled option button in the Set Monitor Time
box.
NOTE
Three options of monitor period are available. They are 15-minute, 24-hour, and custom period. To set the
custom period, refer to Steps 1 through 3.
6 Set the Start Time and End Time fields and click Apply.
7 The Operation Result dialog box is displayed indicating that the operation was successful.
8 Click Close.
----End


You can set the monitoring status and the automatic reporting status of monitored objects. The
U2000 monitors the performance of all boards in the network, but the automatic reporting feature
is disabled by default. You can modify the value of the attribute according to the requirement.
Prerequisite
Procedure
1 In the NE Explorer, select a board and choose Performance > Performance Monitor Status
2 Select a condition from the Monitored Object Filter Criteria drop-down list.
3 Set the Monitor Status, 15-Minute Auto-Report and 24-Hour Auto-Report. Click Apply.
NOTE
If you have already created a performance event monitoring status template for the boards, click Use
Template and then select the desired template. Click Open.
4 Optional: Click Default to restore the default settings.

5 In the Operation Result dialog box displayed, click Close.
----End
Related Tasks
8.7 Customizing a Performance Event Monitoring Status Template
8.8.8 Setting IP Performance Monitoring Parameters of a Board

By setting IP performance monitoring parameters properly and starting the IP performance
monitoring of a specified board, you can obtain the detailed IP performance record during the
running of the board.
Prerequisite
configured.
Procedure
1 In the NE Explorer, select a board and choose Performance > IP Performance Event Monitor
Status from the Function Tree.
2 In the Monitored Object Filter Criteria, set the monitor object.
3 Set the Monitor Status, 30-Second Auto-Report, 30-Minute Auto-Report and Custom
Period Auto-Report fields.

4 Click Apply. The Operation Result is displayed indicates that the operation was successful.
5 Click Close.
----End
8.8.9 Setting ATM Performance Monitoring Parameters of an ATM

Board
By setting ATM performance monitoring parameters of an ATM board properly and starting the
performance monitoring for the ATM board, you can obtain the detailed performance record
during the running of the board. This facilitates the monitoring and analysis of the board running
status performed by maintenance personnel.
Prerequisite
Procedure
1 In the NE Explorer, select an ATM board and choose Performance > ATM Performance Event
Monitor Status from the Function Tree.
2 Set the monitored object in the Monitored Object Filter Criteria.
3 Select a value in the 15-Minute Monitor, 24-Hour Monitor, Custom Period Monitor, 15-
Minute Auto-Report, 24-Hour Auto-Report and Custom Period Auto-Report fields.
4 Click Apply.
----End
8.8.10 Setting Ethernet Port Flow Monitoring

By setting the Ethernet port flow monitoring, you can monitor the flow of the Ethernet port and
display the flow data of the last month on the U2000.
Prerequisite
Applies to the N4EGS4 board.
Procedure
1 In the NE Explorer, select an Ethernet board and choose Performance > Ethernet Port Flow
Monitoring from the Function Tree. Click the Set Monitoring tab.
2 Select a port and set the Status Monitoring parameter.

NOTE
An Ethernet board can monitor the flow of up to 10 Ethernet ports, including IP ports and VC TRUNK
ports. That is, you can set Status Monitoring to Enabled for up to 10 Ethernet ports on an Ethernet board.

3 Click Apply. A dialog box is displayed indicating that the operation is successful. Click
Close.
----End
8.9 Setting RMON Performance Monitoring Parameters

By setting RMON performance monitoring parameters of an Ethernet board properly, starting
the RMON performance monitoring for this board, and setting the automatic reporting status of
the RMON performance data, you can obtain the detailed performance record during the running
of the Ethernet board.
8.9.1 Customizing the RMON Performance Attribute Template
Customize the RMON performance attribute template to provide a method of quickly setting
the RMON performance.
8.9.2 Setting the RMON Performance Threshold
Set the parameters related to the threshold detection for the RMON performance event. In this
way, the reporting of abnormal performance events can be controlled.
8.9.3 Setting the RMON History Control Group
Set the RMON history control group to control how the history data is obtained and stored.
8.9.4 Setting the RMON Performance Monitor Object
Set the monitor status and collecting period for the RMON performance monitor object. In this
way, the performance data can be periodically collected.
8.9.5 Setting the RMON Performance Monitor Status
Enable each period for monitoring the RMON performance event. In this way, the RMON
performance event can be monitored.
8.9.6 Setting Performance Monitoring Parameters of an Alarm Group for an Ethernet Port
You can set the threshold of the alarm group of the Ethernet port to determine if an Ethernet
performance event is reported as an alarm.
8.9.7 Setting Performance Monitoring Parameters of a History Control Group for an Ethernet
Port
The history control group can control the mode of obtaining the history performance data of an
Ethernet port.
8.9.8 Setting the RMON Performance Monitoring Parameters for an Ethernet Port
By setting parameters of the RMON performance monitoring of Ethernet ports, you can set the
threshold and enable the reporting of the threshold-crossing events within a period.
8.9.9 Setting Automatic Reporting of RMON Performance Events
You can set automatic reporting of RMON performance events for a board.
8.9.1 Customizing the RMON Performance Attribute Template

Customize the RMON performance attribute template to provide a method of quickly setting
the RMON performance.
Prerequisite
Applies for PTN equipment.

The PTN equipment supports the RMON performance monitoring for the physical ports and
service objects. Hence, the PTN equipment also supports the customization of the RMON
performance attribute template for physical ports or service objects.
Procedure
Type (Example) Entry
Physical port or sub-board Select the board and choose Performance >
RMON Performance.

Management. Right-click one or several
tunnels and select Browse Performance.
ML-PPP Choose Configuration > Interface

Management > MP Group Management .
Right-click one or several MP groups and
select Browse Performance.
PW Choose Configuration > MPLS

Management > PW Management. Right-
click one or several PWs and select Browse
Performance.
If you need to browse the RMON
performance of the PW used by each service
type, such as the ATM service, CES service
and Ethernet service, right-click one or
several PWs in the corresponding service
interface and select Browse Performance.
ATM service Choose Configuration > ATM Service

ATM services and select Browse
Performance.
CES service Choose Configuration > CES Service

CES services, or right-click one or several
PWs in PW General Attributes, and then
NOTE
The UNI-UNI CES service does not support the
Ethernet service Choose Configuration > Ethernet Service.

Select one Ethernet service type, right-click
one or several services, and then select
Browse Performance.

Link aggregation group Choose Configuration > Interface

Management > Link Aggregation Group
Management. Right-click one or several link
aggregation groups and select Browse
Performance.
MEP point Click Configuration and select the

corresponding service type. Right-click one
or several MEP points, and select Browse
Performance.
2 Click the RMON Setting tab.
3 Click Event and set parameters related to Event as required.
4 Click Save As Template. A dialog box is displayed for saving the template.
5 Enter a name for Template Name.
6 Click Save. A dialog box is displayed to show the operation result.
7 Click Close to finish the setting.
----End
8.9.2 Setting the RMON Performance Threshold

Set the parameters related to the threshold detection for the RMON performance event. In this
way, the reporting of abnormal performance events can be controlled.
Prerequisite
Procedure
RMON Performance.




Performance.

Performance.

NOTE

Browse Performance.

Performance.

Performance.

3 Set the Threshold Detect state, Upper Threshold and Lower Threshold for related
performance events as required.

NOTE
l The threshold detect attribute cannot be set for all performance events. Whether the threshold detect
attribute can be set for all performance events depends on the equipment.
l According to the Threshold Detect status, a comparison is made between the performance event and
Upper Threshold or Lower Threshold to decide whether to report the performance event.
4 Click Apply. A dialog box is displayed to show the operation result.
5 Click Close.
----End
8.9.3 Setting the RMON History Control Group

Set the RMON history control group to control how the history data is obtained and stored.
Prerequisite
Procedure
1 Select the NE in the NE Explorer. Choose Performance > RMON History Control Group
2 Set parameters related to 30-Second, 30-Minute, Custom Period 1 and Custom Period 2.
NOTE
l The collecting period for 30-Second and 30-Minute is fixed.

l Set Period Length to set the collecting period for Custom Period 1 and Custom Period 2.
4 Click Close.
----End
8.9.4 Setting the RMON Performance Monitor Object

Set the monitor status and collecting period for the RMON performance monitor object. In this
way, the performance data can be periodically collected.
Prerequisite
Procedure

RMON Performance.



Performance.

Performance.

NOTE

Browse Performance.

Performance.

Performance.

3 Select the object from Object, set the monitor status, and enable or disable each collecting period.
NOTE
l Enable or disable the collecting period in the Object interface only after you enable the collecting
period in the RMON History Control Group interface.
l Select several objects, and right-click the monitor status or each collecting period to set the enable
status.
5 Click Close.
----End
8.9.5 Setting the RMON Performance Monitor Status

Enable each period for monitoring the RMON performance event. In this way, the RMON
performance event can be monitored.
Prerequisite
Procedure
RMON Performance.




Performance.

Performance.

NOTE

Browse Performance.

Performance.

Performance.

3 Select the performance event in Event and set the enable status for each monitor period.
NOTE
You can also select several performance events, and enable or disable the enable status for each monitor
period.

5 Click Close.
----End
8.9.6 Setting Performance Monitoring Parameters of an Alarm

Group for an Ethernet Port
You can set the threshold of the alarm group of the Ethernet port to determine if an Ethernet
performance event is reported as an alarm.
Prerequisite
l Applies to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment. But The
version after V100R009C03 of MSTP, OptiX RTN 910, OptiX PTN 950, OptiX PTN 910,
OptiX PTN 912 and OptiX PTN 950 do not support.
l The version after V100R004C02 of OptiX OSN 6800 and OptiX OSN 3800 V100R004C02
do not support, OptiX OSN 8800 series, OptiX OSN 9560 does not support either.
Procedure
1 In the NE Explorer, select an Ethernet board and choose Performance > RMON
2 Click the Alarm Group tab.
3 Set Sampling Interval(s), Upper Threshold, Lower Threshold, Report Mode and Monitor
Status as required.
NOTE
If you set Monitor Status to Enabled, the NE monitors the performance indexes of the Ethernet port.
4 Click Apply. A prompt is displayed indicating that the operation is successful.
5 Click Close.
----End
Related Concepts

8.9.7 Setting Performance Monitoring Parameters of a History

Control Group for an Ethernet Port
The history control group can control the mode of obtaining the history performance data of an
Ethernet port.
Prerequisite
l Applies to MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.
Procedure
1 In the NE Explorer, select an Ethernet board and choose Performance > RMON
2 Click the History Control Group tab.
3 Select a History Table Type.
4 Set Number of Items and Monitor Status as required.

NOTE
l If you set History Table Type to Custom Period, you can define the Sampling Period.
l If you set History Table Type to Custom Period1 or Custom Period2, you can define the Sampling
Period.
l If you set Monitor Status to Enabled, in History Group, you can query the corresponding port and
the performance of the history group in History Table Type.
5 Click Apply. A prompt appears telling you that the operation was successful.
6 Click Close.
----End
Related Concepts
8.9.8 Setting the RMON Performance Monitoring Parameters for an

Ethernet Port
By setting parameters of the RMON performance monitoring of Ethernet ports, you can set the
threshold and enable the reporting of the threshold-crossing events within a period.
Prerequisite

Procedure
1 Optional: Click the NE in the NE Explorer, and choose Performance > RMON History
Control Group from the Function tree.
2 Optional: Set the 30-Sencond, 30-MinuteMinute, Custom Period1, Custom Period2 as

Enabled as required. Click Apply.
3 Optional: Click OK in the Confirm dialog box. A prompt is displayed indicating that the
operation is successful.
4 In the NE Explorer, select a board and choose Performance > RMON Performance from the
Function Tree.
6 Select the port number of the board that you want to query.
7 Click Query to query the current values of the performance events.
8 Set values for the parameters as required. Click Apply. A prompt is displayed indicating that
the operation is successful.
9 Click Close.
----End
8.9.9 Setting Automatic Reporting of RMON Performance Events

You can set automatic reporting of RMON performance events for a board.
Prerequisite
Procedure
1 In the NE Explorer, select a board and choose Performance > Automatic RMON Performance
Data Reporting Settings from the Function Tree.
2 Optional: Click Query to query the status of automatic reporting of performance events.
3 Select a performance event, right-click and choose 15-Min Automatic Reporting Status from
the shortcut menu, to set the status of automatic reporting in the 15-minute interval.
4 Select a performance event, right-click and choose 24-Hour Automatic Reporting Status from
the shortcut menu, to set the status of automatic reporting in the 24-hour interval.
5 Click Apply. A prompt appears telling you that the operation was successful.
6 Click Close.
----End


The performance data should be dumped in time to avoid the overflow of the performance data
or damage. You can manually dump the performance data or set the performance dumping
conditions so that the U2000 automatically dumps the data. There are two types of automatic
dumping, which are overflow-triggered dumping and scheduled dumping.
Context
A maximum of 50 Ethernet performance indicators can be queried on the U2000. If more than
50 indicators are queried, wrapping occurs.
8.10.1 Dumping Performance Data Manually
By manually dumping performance data, you can save the history performance data, which is
recorded in the U2000 to the specified directory at any time. The number of records in the
databases is reduced, and as a result the running speed of the system is increased.
8.10.2 Dumping Performance Data Periodically
By periodically dumping the performance data, you can save the history performance data, which
is recorded in the U2000 to the specified directory. When the number of records in the databases
is reduced, the running speed of the system increases.
8.10.3 Dumping Performance Data in the Overflow Way
By dumping the performance data in the overflow way, you can save the history performance
data, which is recorded in the U2000 to the specified directory. When the number of records in
the databases is reduced, the running speed of the system increases.
Related Concepts

By manually dumping performance data, you can save the history performance data, which is
recorded in the U2000 to the specified directory at any time. The number of records in the
databases is reduced, and as a result the running speed of the system is increased.
Prerequisite
Procedure
2 In the navigation tree on the left of the Task Management window, choose Manual Dump.
3 In the task list, double-click Performance Event Manual Dump to check the task attribute.
4 Right-click to select Run At Once to complete the task.
----End

Result
The manually dumped performance data is saved as a file in the specified directory, but not
displayed in the History Performance Data window. To view the dumped performance data,
you can collect the dumped performance data by using the network management system
maintenance tool and then open the collected data by using the text editor.
NOTE
When the value of the performance data, including bit errors, is 0, services are normal and are not displayed
in the exported dumping data.
8.10.2 Dumping Performance Data Periodically

By periodically dumping the performance data, you can save the history performance data, which
is recorded in the U2000 to the specified directory. When the number of records in the databases
is reduced, the running speed of the system increases.
Prerequisite
Context
You can use Overflow Dump or Periodic Dump to automatically dump the data.
l If you select the overflow dump mode, the U2000 automatically dumps some data to the
specified path when the data exceeds the threshold.
l If you select the periodic dump mode, the U2000 periodically dumps the data to the
specified path.
l Overflow dump and periodic dump can work together. In this case, the U2000 dumps the
data or log according to the settings of overflow dump and periodic dump.
Procedure
2 In the navigation tree on the left of the Task Management window, choose Database Capacity
Management.
3 In the task list, double-click Performance Event Period Dump.
4 In the Attribute dialog box, modify common parameters and extended parameters.
5 Click OK.
----End
Result
The automatically dumped performance data is saved as a file in the specified directory, but not
displayed in the History Performance Data window. To view the dumped performance data,
you can collect the dumped performance data by using the network management system

NOTE
8.10.3 Dumping Performance Data in the Overflow Way

By dumping the performance data in the overflow way, you can save the history performance
data, which is recorded in the U2000 to the specified directory. When the number of records in
the databases is reduced, the running speed of the system increases.
Prerequisite
Context
You can use Overflow Dump or Periodic Dump to automatically dump the data.
l If you select the overflow dump mode, the U2000 automatically dumps some data to the
specified path when the data exceeds the threshold.
l If you select the periodic dump mode, the U2000 periodically dumps the data to the
specified path.
l Overflow dump and periodic dump can work together. In this case, the U2000 dumps the
data or log according to the settings of overflow dump and periodic dump.
Procedure
2 In the navigation tree on the left of the Task Management window, choose Overflow Dump.
3 In the task list, double-click Performance Event Overflow Dump.
4 In the Attribute dialog box, modify common parameters and extended parameters.
5 Click OK.
----End
Result
The dumped performance data in the overflow way is saved as a file in the specified directory,
but not displayed in the History Performance Data window. To view the dumped performance
data, you can collect the dumped performance data by using the network management system
NOTE

8.11 Collecting the History RMON Performance Data

Set parameters related to the object and performance event. In this way, the U2000 can
automatically and periodically collect the history RMON performance data.
Prerequisite
Procedure
RMON Performance.



Performance.

Performance.


NOTE

Browse Performance.

Performance.

Performance.

3 Select the object from Object, set the monitor status, enable or disable each collecting period.
NOTE
l Enable or disable the collecting period in the Object interface only after you enable the collecting
period in the RMON History Control Group interface.
l Select several objects, right-click the monitor status or each collecting period to set the enable status.

5 Click Close.
6 Select the performance event in Event and set the enable status for each monitor period.
TIP
You can also select several performance events and set the enable status for each monitor period.


8 Click Close.
----End
8.12 Periodically Collecting the Performance Data

If you need to periodically query and handle the performance data, you can use the function of
periodical performance data collection. This function can periodically simulate the user
operation of querying the performance data, and export the query result to a text file. This helps
reduce the repeated operations that would otherwise be performed by you.
Prerequisite
The performance monitoring function of the NE must be enabled.
l Since the performance data collection always involves large data volumes, it is
recommended that you perform the data collection once a week when the network traffic
is not heavy.
l The time difference between two tasks must be longer than the execution duration of the
previous task. (The time duration approximately equals 30 (s) x the number of boards
involved in the previous task.)
Procedure
2 Click New and the New Task is displayed.
3 Enter the task name and select the Run Type, and select the Task Type as the Transfers NE
Perfoamance Collection And Export. Then, click Next.
4 Click SDH or WDM, and click to refresh.

5 Select the NE and board from which you want to periodically collect the performance data and
click Next.
NOTE
You can use the search function to quickly search the desired NE or board.

6 Set the Monitored Object Filter Criteria, Monitor Period, and Performance Event Type.
Then, click Next.
NOTE
For the Performance Event Type, you can select items on the Gauge tab and/or Count tab.
7 Optional: Check the Export File check box and select the type of the performance events that
you want to export from the Performance Event Type. Click Finish. A scheduled task is
successfully created.
NOTE
l For the Performance Event Type, you can select items on the Gauge tab and/or Count tab.
l The Path displays the relative path in the /server/dump/PerfLog directory and cannot be modified.
l The file is exported in .txt format.
8 Optional: Double-click a scheduled task to modify the parameters of the task.
9 Optional: Right-click a scheduled task and choose Timely Suspend/Resume to set the suspend
time or the resume time for the task.
10 Optional: Right-click a scheduled task and choose Run At Once to start executing the task.
NOTE
Run At Once means to immediately execute the task, no matter the scheduled time comes or not.
Resume means to start the scheduled task. The task is executed at the scheduled time.
----End

To know the operational status of the equipment, you can analyze the history performance data
recorded on the U2000 or on the NE.
Prerequisite
Procedure
1 Choose Performance > Analyze History Performance Data from the main menu.
2 In the Object Tree, select one module of a board and click .
3 Complete the following information: Monitor Period, Display Mode and Time Range.
4 Select Query from NE or Query from U2000.
5 Click Query to query the data on the NE or that stored in the U2000.
----End
Related Concepts

8.14 Forecasting the Failure Time of the Laser

According to the changes in the history performance data of an optical component that is stored
in the U2000, the U2000 can forecast when the optical component fails or what the performance
value of an optical component is at a given time. In this way, you can decide when to replace
the optical component.
Prerequisite
At least five days of performance data must be collected.
The board must support the query of performance data.
Procedure
1 Choose Performance > Medium-Term and Long-Term Performance Forecast from the
main menu.
2 In the Object Tree, select one module of a board, and click .

3 Complete the information: Category of Forecast Basis and Forecast Input Conditions.
4 Click Forecast. The results are shown under Forecast Output Value and the corresponding
diagram is displayed.
----End
8.15 Resetting Performance Registers

Context
Based on the type of the performance register, you can reset the following performance registers:
8.15.1 Resetting Board Performance Registers
performance monitoring period. A performance register of the board stores performance data
including optical power and bit errors., you need to reset the performance register to enter a new
including optical power and bit errors.
8.15.2 Resetting ATM Performance Registers
8.15.3 Resetting Ethernet Performance Registers

8.15.1 Resetting Board Performance Registers

including optical power and bit errors., you need to reset the performance register to enter a new
including optical power and bit errors.
Prerequisite
Procedure
1 In the NE Explorer, select a board and choose Performance > Reset Board Performance
Register from the Function Tree.
2 In the NE Explorer, select a board and choose Performance > Reset Performance Register
3 Select the ports and registers that you want to reset and click Reset.
4 Click Yes in the confirmation dialog box. A prompt appears indicating that the operation is
successful.
5 Click Close.
----End
8.15.2 Resetting ATM Performance Registers

Prerequisite
Procedure
1 In the NE Explorer, select an ATM board and choose Performance > Reset ATM Performance
successful.
4 Click Close.
----End

8.15.3 Resetting Ethernet Performance Registers

Prerequisite
configured.
Procedure
1 In the NE Explorer, select an Ethernet board and choose Performance > Reset IP Performance
successful.
4 Click Close.
----End
8.16 Power Consumption Management

To ensure the normal running of a network, network management and maintenance engineers
need to regularly check and monitor the power consumption of NEs and boards by taking power
consumption measures.
8.16.1 Querying the Power Consumption of NEs and Boards

After querying the power consumption of NEs and boards, if you find that the power
consumption of NEs exceeds the threshold, you should replace these high power-consuming
boards with low power-consuming boards, or remove some unused boards.
8.16.2 Setting the NE Power Consumption Threshold
After the NE power consumption threshold is set, if the NE power consumption crosses the
threshold, the U2000 displays a prompt to inform you of the situation. In this manner, the NE
can be protected from the damage that results from excessive power consumption.
8.16.1 Querying the Power Consumption of NEs and Boards

After querying the power consumption of NEs and boards, if you find that the power
consumption of NEs exceeds the threshold, you should replace these high power-consuming
boards with low power-consuming boards, or remove some unused boards.
Prerequisite

Procedure
1 Choose Configuration > NE Batch Configuration > Power Management from the main
menu.
2 Query the power consumption according to the requirement.
l Query the NE power consumption as follows.
1. Click the NE Power tab.

3. Click Query to display the query result.
l Query the board power consumption as follows.
1. Click the Board Power tab.
2. In the Object Tree, select one or more boards and click .

3. Click Query to display the query result.
----End
8.16.2 Setting the NE Power Consumption Threshold

After the NE power consumption threshold is set, if the NE power consumption crosses the
threshold, the U2000 displays a prompt to inform you of the situation. In this manner, the NE
can be protected from the damage that results from excessive power consumption.
Prerequisite
Procedure
1 Choose Configuration > NE Batch Configuration > Power Management from the main
menu.
2 In the Object Tree, select one or more NEs and click .

3 In the NE Power Consumption Threshold(W) field, set the NE power consumption threshold.
NOTE
A default value is set in the NE Power Consumption Threshold(W) field for each type of NE. It is
recommended that you do not modify the value.
4 Click Apply to display the Operation Result dialog box.

5 Click Close.
----End
8.17 Configuring the Q Value Performance Monitoring

Configuring the Q value performance monitoring can query current and history Q value
performance. Also, you can query and set the Q value performance threshold.

8.17.1 Querying the Current Q Value Performance

If you want to check whether the Q value performance in the current 15 minutes or 24 hours is
normal, query the current Q value performance on the U2000.
8.17.2 Querying the History Q Value Performance
If you want to check whether the Q value performance in the past 15 minutes or 24 hours is
normal, query the history Q value performance on the U2000.
8.17.3 Setting and Querying the Threshold of the Q Value Performance
You can set a proper threshold. When the service failure is about to occur because of the Q value
performance, an event is reported to indicate that the performance crosses the threshold and
manual handling is required.
8.17.1 Querying the Current Q Value Performance

If you want to check whether the Q value performance in the current 15 minutes or 24 hours is
normal, query the current Q value performance on the U2000.
Prerequisite
Applies to OptiX OSN 3800, OptiX OSN 6800, OptiX OSN 8800 seriesOptiX OSN 9560, OptiX
BWS 1600S, OptiX OSN 3800A, OptiX OSN 6800A and OptiX OSN 8800(NA) series.
The performance monitoring must be started
Procedure
1 Choose Performance > Browse WDM Performance from the main menu. Click the Current
Performance Data tab.
2 In the Object Tree, select one or more boards, and click the double-right-arrow button (red).
3 Complete the following information: Monitored Object Filter Criteria and Monitor Period.
4 Click the Count tab. In the Performance Event Type group box, check the FEC
Performance check box.
5 Optional: In the Display Options group box, check the Display Zero Data or Display
Consecutive Severely Errored Seconds check box.

----End
8.17.2 Querying the History Q Value Performance

If you want to check whether the Q value performance in the past 15 minutes or 24 hours is
normal, query the history Q value performance on the U2000.
Prerequisite
Applies to OptiX BWS 1600S.
Procedure
1 Choose Performance > Browse WDM Performance from the main menu. Click the History
Performance Data tab.
2 In the Object Tree, select one or more boards, and click the double-right-arrow button (red).
3 Complete the following information: Monitored Object Filter Criteria, Monitor Period,
From: To: and Data Source.
4 Click the Count tab. In the Performance Event Type group box, check the Other Errors check
box.
5 Optional: In the Display Options group box, check the Display Zero Data check box.
6 Click Query. Click Close in the Operation Result dialog box.
----End
8.17.3 Setting and Querying the Threshold of the Q Value

Performance
You can set a proper threshold. When the service failure is about to occur because of the Q value
performance, an event is reported to indicate that the performance crosses the threshold and
manual handling is required.

Prerequisite
Applies to OptiX BWS 1600S.
Procedure
1 In the NE Explore, select a board and choose Configuration > WDM Interface from the
Function Tree.
2 Select the By Board/Port(Channel) option button. Select Channel from the drop-down list.
3 Select the Basic Attributes tab.
4 Click the Query.
5 Double-click the Q Threshold and enter a proper value.
6 Click Apply to confirm the settings.
----End

Operation Guide for Common Features 9 Inventory Management
9 Inventory Management
About This Chapter
This topic describes the inventory management, including managing the telecommunications
room, rack, NE, shelf, board, subboard, port, fiber/cable, fiber and cable pipe, link resource,
interface resource, ONU, and PON optical splitting status. Inventory management provides the
unified network resource query and statistics functions and supports carriers' service planning
and capacity expansion plans.
9.1 Telecommunication Room Management

With the telecommunication room management function, you can query, maintain, and collect
statistics on telecommunications room. Telecommunication room management provides
information such as the quantity and locations of telecommunication rooms on the network so
that network status can be learned in time and carriers' service planning and capacity expansion
plans can be supported.
9.2 Rack Management
With the rack management function, you can query and maintain racks, and collect statistics on
racks. Rack management provides information such as the quantity, type, and located
telecommunication rooms of racks on the network so that network status can be learned in time
and carriers' service planning and capacity expansion plans can be supported.
9.3 NE Management
With the NE management function, you can query, maintain, and collect statistics on NEs. NE
management provides information such as an .xls, quantity, equivalent quantity, and locations
of NEs on the network so that network status can be learned in time and carriers' service planning
and capacity expansion plans can be supported.
9.4 Shelf Management
With the shelf management function, you can query, maintain, and collect statistics on shelf.
Shelf management provides information such as the types, quantity, and belonging NEs of
shelves on the network so that network status can be learned in time and carriers' service planning
9.5 Board Management
With the board management function, you can query and maintain boards, and collect statistics
on boards. Board management provides information such as the types, quantity, and belonging
NEs of boards on the network so that network status can be learned in time and carriers' service
planning and capacity expansion plans can be supported.

9 Inventory Management Operation Guide for Common Features
9.6 Subboard Management

With the subboard management function, you can query and maintain subboards, and collect
statistics on subboards. Subboard management provides information such as the types, quantity,
slot numbers, subslot numbers, and belonging NEs of subboards on the network so that network
status can be learned in time and carriers' service planning and capacity expansion plans can be
supported. Access NEs do not support functions described in this topic.
9.7 Port Management
With the port management function, you can query and maintain ports. Port management
provides information such as the types, quantity, and belonging NEs of ports on the network so
9.8 Collecting Statistics on the Slot Usage
This topic describes how to measure the number of total slots and the number of in-use slots
based on the NE type to help determine the board capacity and future capacity expansion.
9.9 Fiber/Cable Management
Fiber/Cable management refers to the operations of querying, collecting statistics on, and
maintaining fibers/cables. Fiber/cable management covers fiber/cable query, statistics, and
maintenance. Fiber/cable management provides information such as the types, levels/capacities,
lengths, and media of fibers/cables among NEs so that network status can be learned in time and
carriers' service planning and capacity expansion plans can be supported. Current alarms and
history alarms of fibers/cables can also be queried.
9.10 Fiber/Cable Pipe Management
A fiber/cable pipe is a model for fiber/cable management. That is, multiple fibers/cables are
combined and considered as a pipe for management. The fibers/cables that are laid outdoors
often are combined and coated. A fiber/cable pipe contains multiple fibers/cables and a fiber/
cable belongs to multiple fiber/cable pipes. Fiber/cable pipe management helps to implement
unified management of fibers/cables through pipes.
9.11 Link Resource Management
This describes the function that the NMS provides to manage link resources between Datacomm
devices. Link source management provides information such as the types and levels of links
among NEs so that link alarm severities and networking information can be learned in time and
carriers' service planning can be supported. Users can view link alarm information to quickly
locate and rectify faults according to detailed alarm information and handling suggestions. This
function is applicable to Router series, Switch series, Security series, Access series NEs.
9.12 Interface Resource Management
This topic describes how to manage the interface resources of datacom devices through the NMS.
Interface resource management provides information such as the names, types, belonging NEs,
IPv4 addresses, and MAC addresses of interfaces on the network so that detailed NE interface
information can be learned in time and carriers' service planning and capacity expansion plans
can be supported.
9.13 Collecting Statistics on the ONU
This topic describes how to collect statistics on the ONU types on the entire network based on
the equipment type or collect statistics on each terminal type and ONU version based on the
submap.
9.14 Collecting Statistics on the Split Status of PON Ports
This topic describes how to collect statistics on the split status of PON ports. By checking the
split ratio usage of PON ports, you can determine whether to perform capacity expansion.
9.15 Exporting Electronic Labels of NEs

Before upgrading the U2000, you need to export the information about the NEs or cards, such
as hardware electronic labels and versions, from the U2000 and save the information in TXT or
XML format. This facilities the management and statistics of inventory resources on a network.
9.16 SDH Report
The SDH report includes various statistics reports on different dimensions, such as on the SDH
NEs, cards, ports. These reports offer useful data for the project maintenance.
9.17 Microwave Report
The microwave report includes various statistics reports on different dimensions, such as on the
microwave equipment and links. These reports offer useful data for the project maintenance.
9.18 WDM Statistic Report
The WDM statistics report includes various statistics reports on different dimensions, such as
on the WDM NEs, cards and ports. These reports offer useful data for the project maintenance.
9.19 MSTP Ethernet Report
The MSTP Ethernet report includes various statistics reports on different dimensions, such as
on the MSTP Ethernet ports and NEs. These reports offer useful data for the project maintenance.
9.20 Project Document
The project document includes various information reports on different dimensions, such as NE
information report, card manufacturer information report, clock tracing diagram, networking
diagram, and timeslot allocation diagram. These reports offer useful data for the project
maintenance.

9.1 Telecommunication Room Management

With the telecommunication room management function, you can query, maintain, and collect
statistics on telecommunications room. Telecommunication room management provides
information such as the quantity and locations of telecommunication rooms on the network so
9.1.1 Creating a Telecommunications Room

This describes how to create a telecommunications room. When a telecommunications room is
added to the network, you need to create the information about the telecommunications room
on the NMS for maintaining and managing the telecommunications room.
9.1.2 Installing a Rack or an NMS Server in a Telecommunications Room
This describes how to install a rack or an NMS server in a telecommunications room. If a rack
or an NMS is required for a telecommunications room, you need to install the rack or the NMS
server in the telecommunications room for maintenance and management.
9.1.3 Querying Telecommunications Rooms
This topic describes how to query telecommunications rooms. You can query either all
telecommunications rooms or the specified telecommunications rooms.
9.1.4 Modifying a Telecommunications Room
This describes how to refresh the information about a telecommunications room when the actual
information about a telecommunications room changes.
9.1.5 Deleting a Telecommunications Room
This describes how to delete a telecommunications room from the NMS when the actual
telecommunications room leaves the network.
9.1.6 Setting a Flag for a Telecommunications Room
This describes how to set a flag for a telecommunications room as required.
9.1.7 Exporting telecommunications Room Information
This describes how to export telecommunications room information and save it as a file
in .xls, .txt, .html, or .csv format.
9.1.8 Collecting Statistics on a Telecommunications Room
The telecommunications room information includes attributes such as the name, address, and
flag. You can collect the statistics on a telecommunications room based on each attribute.
9.1.1 Creating a Telecommunications Room

This describes how to create a telecommunications room. When a telecommunications room is
added to the network, you need to create the information about the telecommunications room
on the NMS for maintaining and managing the telecommunications room.
Prerequisite

Procedure
1 Choose Inventory > Physical Inventory > Telecommunications Room from the main menu.
2 On the Telecommunications Room List tab, click New and set the related parameters.
NOTE
The parameters with the asterisk (*) are mandatory.
3 After configuration, click OK.

The Operation Result dialog box is displayed, displaying Operation succeeded.
4 Click Close to return to the Telecommunications Room List tab.
----End
9.1.2 Installing a Rack or an NMS Server in a Telecommunications

Room
This describes how to install a rack or an NMS server in a telecommunications room. If a rack
or an NMS is required for a telecommunications room, you need to install the rack or the NMS
server in the telecommunications room for maintenance and management.
Prerequisite
Procedure
2 Right-click on the Telecommunications Room List tab and choose Refresh from the shortcut
menu.
All the telecommunications room records are displayed in the query result area.
3 Select a telecommunications room record, and then click Install Racks/NMSs. Select the rack
or the NMS server to be installed and click OK.
Information about the installed rack or NMS server is displayed on the Racks/NMS
Information tab.
----End

9.1.3 Querying Telecommunications Rooms

This topic describes how to query telecommunications rooms. You can query either all
telecommunications rooms or the specified telecommunications rooms.
Prerequisite
You must be an NM user with "NM monitor" authority or higher.
Procedure
2 Query the telecommunications room information.

l To query the information about all telecommunications rooms, right-click on the
Telecommunications Room List tab page and choose Refresh from the shortcut menu.
l To query the information about the specified telecommunications rooms, click Filter, set
the filter criteria, and click OK. All records meeting the filter criteria are displayed in the
query result area.
----End
9.1.4 Modifying a Telecommunications Room

This describes how to refresh the information about a telecommunications room when the actual
information about a telecommunications room changes.
Prerequisite
Procedure
menu.
3 Select the telecommunications room to be modified and click Modify to modify the related
parameters.
4 After modification, click OK.

5 Click Close to return to Telecommunications Room List tab.

The modified telecommunications information is displayed in the query result area.
6 Optional: If racks and NMS servers are installed in the telecommunications room, select the
records of the intended racks and NMS servers for uninstallation on the Rack/NMS
Information tab. Then, click UnInstall Racks/NMSs.

The information about the racks and NMS servers to be uninstalled is deleted from the Rack/
NMS Information tab.
----End
9.1.5 Deleting a Telecommunications Room

This describes how to delete a telecommunications room from the NMS when the actual
telecommunications room leaves the network.
Prerequisite
Procedure
menu.
3 Select the telecommunications room to be deleted and click Delete. The Confirm dialog box is
displayed.
4 Click OK to return to the Telecommunications Room List tab.
----End
Result
When the telecommunications room is deleted, the racks or NMSs installed in the
telecommunications room are automatically uninstalled.
9.1.6 Setting a Flag for a Telecommunications Room

This describes how to set a flag for a telecommunications room as required.
Prerequisite
Procedure
menu.
3 Select one or more telecommunications rooms and right-click them. Then choose Set User
Label from the shortcut menu to set Customized Column.
NOTE
When you need to set Customized Column for a certain record, click Next or Previous to set the next or
previous record. Then, click Apply.

4 After configuration, click OK to return to the Telecommunications Room List tab.

5 Optional: You can define the name of the column with the asterisk (*) as required. Do as follows:
1. Right-click on the heading of the query result area and choose Setting from the shortcut
menu.
2. In the Column Setting dialog box, define the name of the column with the asterisk (*) as
required.
3. After configuration, click OK.
----End
9.1.7 Exporting telecommunications Room Information

This describes how to export telecommunications room information and save it as a file
Prerequisite
Procedure
menu.
3 Click Save as. Then set Start row, End row, and File name.
NOTE
The selected records are saved as a file in .xls, .txt, .html, or .csv format. By default, the file is saved in the
report folder of the client directory. You can modify the directory as required.
4 Click OK to return to the Telecommunications Room List tab.
----End
9.1.8 Collecting Statistics on a Telecommunications Room

The telecommunications room information includes attributes such as the name, address, and
flag. You can collect the statistics on a telecommunications room based on each attribute.
Prerequisite
Procedure
2 Click the Telecommunications Room Statistics tab. Then, select the statistics type from the
Statistics Type drop-down list.
The telecommunications room records conforming to the statistics type are displayed in the
query result area.

NOTE
When the operation is performed on multiple clients at the same time, click Count to refresh the client
windows with the real-time data in the server database.
3 Optional: If there is no statistics type satisfying the requirements in the drop-down list, you can
customize the statistics type. Do as follows:
1. Select Customize from the Statistics Type drop-down list.
2. In the Customize Telecommunications Room Statistics Type dialog box, click New.
3. In the New Customize Telecommunications Room Statistics Type dialog box, set the
related parameters, and then click OK.
4. In the Customize Telecommunications Room Statistics Type dialog box, click OK.
The information about the customized statistics type of the telecommunications room, is
displayed in the query result area.
4 Optional: Click Save as. Then set Start row, End row, and File name.
NOTE
5 Optional: Click Print. Set Start Row and End Row. Then, click OK.
In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
9.2 Rack Management

With the rack management function, you can query and maintain racks, and collect statistics on
racks. Rack management provides information such as the quantity, type, and located
telecommunication rooms of racks on the network so that network status can be learned in time
and carriers' service planning and capacity expansion plans can be supported.
9.2.1 Creating a Rack

This describes how to create a rack. When a rack is added to the network, you need to create the
information about the rack on the NMS for the maintainance and management of the rack.
9.2.2 Installing a shelf on a Rack
This describes how to install a shelf on a rack. When installing a shelf on a rack, you need to
create the information about the shelf on the NMS to facilitate maintenance and management.
9.2.3 Querying Racks
This describes how to query racks. You can query all racks or the specified racks.
9.2.4 Modifying a Rack
This describes how to modify a rack. When the information about a rack is modifed, you need
to synchronize the modified rack information on the NMS.
9.2.5 Deleting a Rack
This describes how to delete a rack. When a rack is removed from the network, you need to
delete the corresponding rack information on the NMS.
9.2.6 Setting a Rack Flag
This describes how to set a rack flag. You can set a flag for a rack as required.
9.2.7 Exporting Rack Information

This describes how to export rack information. The rack information can be exported and saved
as a file in .xls, .txt, .html, or .csv format.
9.2.8 Collecting Statistics on a Rack
This describes how to collect statistics about a rack. The rack information includes rack attributes
such as the rack type, height, and width. You can collect the statistics on a rack based on each
attribute.
9.2.1 Creating a Rack

This describes how to create a rack. When a rack is added to the network, you need to create the
information about the rack on the NMS for the maintainance and management of the rack.
Prerequisite
Procedure
1 Choose Inventory > Physical Inventory > Rack from the main menu.
2 On the Rack List tab, click New.
3 In the New Rack dialog box, set related parameters.

5 Click Close to return to the Rack List tab.
----End
9.2.2 Installing a shelf on a Rack

This describes how to install a shelf on a rack. When installing a shelf on a rack, you need to
create the information about the shelf on the NMS to facilitate maintenance and management.

Prerequisite
l Number of Shelves is set during the installation of a new rack.
Procedure
2 Right-click on the Rack List tab and choose Refresh from the shortcut menu.
All the rack records are displayed in the query result area.
3 Select the rack on which the shelf is to be installed. On the Shelf Information tab, right-click
a record, and then select Install Shelf on the shortcut menu.
4 In the Install Shelf dialog box, select the shelf to be installed and click . The shelf is
displayed in Select Object. Then click OK.
5 In the Operation Result dialog box that is displayed, click Close.

The added shelf is displayed on the Shelf Information tab.
----End
9.2.3 Querying Racks

This describes how to query racks. You can query all racks or the specified racks.
Prerequisite
Procedure
2 Query the rack information.

l To query the information about all racks, right-click on the Rack List tab page and choose
Refresh from the shortcut menu. All the rack records are displayed in the query result area.
l To query the information about the specified racks, click Filter, set the filter criteria, and
click OK. All records meeting the filter criteria are displayed in the query result area.
----End
9.2.4 Modifying a Rack

This describes how to modify a rack. When the information about a rack is modifed, you need
to synchronize the modified rack information on the NMS.
Prerequisite

Procedure
3 Select the rack record to be modified and click Modify to modify the related parameters.

5 Click Close to return to the Rack List tab.

The modified rack information is displayed in the query result area.
6 Optional: If the rack is installed with a shelf, select the record of the shelf for uninstallation on
the Shelf Information tab and right-click it. Then, choose Uninstall Shelf from the shortcut
menu. In the Operation Result dialog box that is displayed, click Close.
----End
9.2.5 Deleting a Rack

This describes how to delete a rack. When a rack is removed from the network, you need to
delete the corresponding rack information on the NMS.
Prerequisite
Procedure
3 Select the rack record to be deleted, and then click Delete.

The Confirm dialog box is displayed, asking you whether to delete the selected rack record.
4 Click OK to return to the Rack List tab.

The shelves installed on the rack are also deleted. The deleted rack record is not displayed in
the query result area.
----End
9.2.6 Setting a Rack Flag

This describes how to set a rack flag. You can set a flag for a rack as required.
Prerequisite

Procedure
3 Select one or more racks and right-click them. Then choose Set User Label from the shortcut
menu to set Customized Column.
NOTE
4 After configuration, click OK to return to the Rack List tab.

menu.
required.
----End
9.2.7 Exporting Rack Information

This describes how to export rack information. The rack information can be exported and saved
as a file in .xls, .txt, .html, or .csv format.
Prerequisite
Procedure
NOTE
4 Click OK to return to the Rack List tab.
----End
9.2.8 Collecting Statistics on a Rack

This describes how to collect statistics about a rack. The rack information includes rack attributes
such as the rack type, height, and width. You can collect the statistics on a rack based on each
attribute.

Prerequisite
Procedure
2 Click the Rack Statistic tab. Then, select the Statistics Type from the Statistics Type drop-
down list.
The rack records in accordance with the statistics type are displayed in the query result area.
NOTE
1. Select Customize from the Statistics Type drop-down list box.
2. In the Customize Rack Statistics Type dialog box, click New.
3. In the New Customize Rack Statistics Type dialog box, set related parameters, and then
click OK.
4. In the Customize Rack Statistics Type dialog box, click OK.
The information about the rack statistics types, which meets the set conditions, is displayed
in the query result area.
NOTE
----End
9.3 NE Management
With the NE management function, you can query, maintain, and collect statistics on NEs. NE
management provides information such as an .xls, quantity, equivalent quantity, and locations
of NEs on the network so that network status can be learned in time and carriers' service planning
9.3.1 Querying NEs

This topic describes how to query NEs. You can query either all NEs or the specified NEs.
9.3.2 Setting a Flag for an NE
You can set a flag for an NE as required.
9.3.3 Exporting NE Information
This describes how to export NE information and save it as a file in .xls, .txt, .html, or .csv
format.

9.3.4 Collecting Statistics on an NE

The NE information includes attributes such as the name, type, and IP address. You can collect
the statistics on an NE based on each attribute.
9.3.5 Collecting Statistics on an Equivalent NE
The management capability of an NMS is measured by the number of equivalent NEs that can
be managed by the NMS.
9.3.1 Querying NEs

This topic describes how to query NEs. You can query either all NEs or the specified NEs.
Prerequisite
Procedure
1 Choose Inventory > Physical Inventory > NE from the main menu.
2 Query the NE information.

l To query the information about all NEs, right-click on the NE List tab page and choose
Refresh from the shortcut menu. All the records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The
timeliness of data cannot be guaranteed. To query the real-time data of a record, do as follows:
1. Select a record and click Query.

2. In the dialog box that is displayed, select Query Range. Then, click OK.
NOTE
l If the selected NE does not support query on the NE side, the Prompt dialog box is
displayed, prompting that the selected record does not support query on the NE side.
l If the selected NE supports query on the NE side, the Operation Result dialog box is
displayed, prompting Operation succeeded or Operation succeeded partially or
Operation failed.
l To query the information about the specified NEs, click Filter, set the filter criteria, and
click OK.All records meeting the filter criteria are displayed in the query result area.
----End
9.3.2 Setting a Flag for an NE

You can set a flag for an NE as required.
Prerequisite
Procedure
2 Right-click on the NE List tab and choose Refresh from the shortcut menu.

All the records are displayed in the query result area.

NOTE
The information queried through the preceding method is the information in the database. The timeliness
of data cannot be guaranteed. To query the real-time data of a record, do as follows:
NOTE
l If the selected NE does not support query on the NE side, the Prompt dialog box is displayed,
prompting that the selected record does not support query on the NE side.
l If the selected NE supports query on the NE side, the Operation Result dialog box is displayed,
prompting Operation succeeded or Operation failed.
3 Select one or more NEs and right-click them. Then choose Set User Label from the shortcut
menu to set Remark and Customized Column.
NOTE
4 Click OK to return to the NE List tab.
menu.
required.
----End
9.3.3 Exporting NE Information

This describes how to export NE information and save it as a file in .xls, .txt, .html, or .csv
format.
Prerequisite
Procedure
2 Right-click on the NE List tab and choose Refresh from the shortcut menu.
NOTE

NOTE
l If the selected NE does not support query on the NE side, the Prompt dialog box is displayed,
l If the selected NE supports query on the NE side, the Operation Result dialog box is displayed,
NOTE
4 Click OK to return to the NE List tab.
----End
9.3.4 Collecting Statistics on an NE

The NE information includes attributes such as the name, type, and IP address. You can collect
the statistics on an NE based on each attribute.
Prerequisite
Procedure
2 Click the NE Statistics tab. Select the NE type from the Statistics Type drop-down list and set
Statistics Scope.
The NE records in accordance with the statistics type are displayed in the query result area.
NOTE
3 Optional: If no statistics type that is in accordance with the statistics type is displayed, you can
2. In the Customize NE Statistics Type dialog box, click New.
3. In the New Customize NE Statistics Type dialog box, set related parameters, and then
click OK.
4. In the Customize NE Statistics Type dialog box, click OK.
The information about the NE statistics types, which meets the set conditions, is displayed
in the query result area.
NOTE

----End
9.3.5 Collecting Statistics on an Equivalent NE

The management capability of an NMS is measured by the number of equivalent NEs that can
be managed by the NMS.
Prerequisite
Procedure
2 Click the Equivalent NE Statistic tab, click Count.
NOTE
----End
9.4 Shelf Management

With the shelf management function, you can query, maintain, and collect statistics on shelf.
Shelf management provides information such as the types, quantity, and belonging NEs of
shelves on the network so that network status can be learned in time and carriers' service planning
9.4.1 Querying shelf

This describes how to query shelf. You can query either all shelves or the specified shelves.
9.4.2 Setting a Flag for a Shelf
This describes how to set a flag for a shelf as required.
9.4.3 Exporting shelf Information
This describes how to export shelf information and save it as a file in .xls, .txt, .html, or .csv
format.
9.4.4 Collecting Statistics on a Shelf
The shelf information includes attributes such as the name, type, and model. You can collect the
statistics on a shelf based on each attribute.
9.4.1 Querying shelf

This describes how to query shelf. You can query either all shelves or the specified shelves.

Prerequisite
Procedure
1 Choose Inventory > Physical Inventory > Shelf from the main menu.
2 Query the shelf information.

l To query the information about all shelves, right-click on the Shelf List tab page and choose
Refresh from the shortcut menu. All the shelf records are displayed in the query result area.
l To query the information about the specified shelves, click Filter, set the filter criteria, and
click OK. All records meeting the filter criteria are displayed in the query result area.
----End
9.4.2 Setting a Flag for a Shelf

This describes how to set a flag for a shelf as required.
Prerequisite
Procedure
2 Right-click on the Shelf List tab and choose Refresh from the shortcut menu.
All the shelf records are displayed in the query result area.
3 Select one or more shelves and right-click them. Then choose Set User Label from the shortcut
NOTE
The following types of devices do not support the remark setting function (the Remark parameter is
unavailable):
l SONET series
l MSTP series
l RTN series
l PTN series
l WDM series
l NA WDM series
l DMT series
4 After the configuration is complete, click OK to return to the Shelf List tab.
menu.

required.
----End
9.4.3 Exporting shelf Information

This describes how to export shelf information and save it as a file in .xls, .txt, .html, or .csv
format.
Prerequisite
Procedure
2 Right-click on the Shelf List tab and choose Refresh from the shortcut menu.
All the shelf records are displayed in the query result area.
NOTE
4 Click OK to return to the Shelf List tab.
----End
9.4.4 Collecting Statistics on a Shelf

The shelf information includes attributes such as the name, type, and model. You can collect the
statistics on a shelf based on each attribute.
Prerequisite
Procedure
2 Click the Shelf Statistics tab. Select the shelf type from the Statistics Type drop-down list and
set Statistics Scope.
The shelf records in accordance with the statistics type are displayed in the query result area.
NOTE

1. Select Customize from the Statistics Type drop-down list.

2. In the Customize Shelf Statistics Type dialog box, click New.
3. In the New Customize Shelf Statistics Type dialog box, set the related parameters, and
then click OK.
4. In the Customize Shelf Statistics Type dialog box, click OK.
The information about the customized statistics type of the shelf, is displayed in the query
result area.
NOTE
----End
9.5 Board Management

With the board management function, you can query and maintain boards, and collect statistics
on boards. Board management provides information such as the types, quantity, and belonging
NEs of boards on the network so that network status can be learned in time and carriers' service
planning and capacity expansion plans can be supported.
9.5.1 Querying Boards

You can query all boards or the specified boards.
9.5.2 Setting a Flag for a Board
You can set a flag for a board as required.
9.5.3 Exporting Board Information
The board information can be exported as a file in .xls, .txt, .html, or .csv format.
9.5.4 Collecting Statistics on a Board
The board information includes board attributes such as name, type, and affiliated NE. You can
collect the statistics on a board based on each attribute.
9.5.1 Querying Boards

You can query all boards or the specified boards.
Prerequisite
Procedure
1 Choose Inventory > Physical Inventory > Board from the main menu.
2 Query the board information.

l To query the information about all Boards, right-click on the Board List tab page and
choose Refresh from the shortcut menu. All the records are displayed in the query result
area.
NOTE

NOTE
l If the selected Board does not support query on the NE side, the Prompt dialog box is
l If the selected Board supports query on the NE side, the Operation Result dialog box is
displayed, prompting Operation succeeded or Operation succeeded partially or
Operation failed.
l To query the information about the specified boards, click Filter, set the filter criteria, and
click OK.All records meeting the filter criteria are displayed in the query result area.
----End
9.5.2 Setting a Flag for a Board

You can set a flag for a board as required.
Prerequisite
Procedure
2 Right-click on the Board List tab and choose Refresh from the shortcut menu.
All the board records are displayed in the query result area.
NOTE
NOTE
l If the selected board does not support query on the NE side, the Prompt dialog box is displayed,
l If the selected board supports query on the NE side, the Operation Result dialog box is displayed,
3 Select one or more boards and right-click them. Then choose Set User Label from the shortcut
NOTE

menu.
required.
----End
9.5.3 Exporting Board Information

The board information can be exported as a file in .xls, .txt, .html, or .csv format.
Prerequisite
Procedure
2 Right-click on the Board List tab and choose Refresh from the shortcut menu.
All the board records are displayed in the query result area.
NOTE
NOTE
l If the selected board does not support query on the NE side, the Prompt dialog box is displayed,
l If the selected board supports query on the NE side, the Operation Result dialog box is displayed,
NOTE
4 Click OK to return to the Board List tab.
----End
9.5.4 Collecting Statistics on a Board

The board information includes board attributes such as name, type, and affiliated NE. You can
collect the statistics on a board based on each attribute.
Prerequisite

Procedure
2 Click the Board Statistics tab. Select the board type from the Statistics Type drop-down list
and set Statistics Scope.
The board records in accordance with the statistics type are displayed in the query result area.
NOTE
2. In the Customize Board Statistics Type dialog box, click New.
3. In the New Customize Board Statistics Type dialog box, set related parameters, and then
click OK.
4. In the Customize Board Statistics Type dialog box, click OK.
The information about the Board statistics types, which meets the set conditions, is
NOTE
----End
9.6 Subboard Management

With the subboard management function, you can query and maintain subboards, and collect
statistics on subboards. Subboard management provides information such as the types, quantity,
slot numbers, subslot numbers, and belonging NEs of subboards on the network so that network
status can be learned in time and carriers' service planning and capacity expansion plans can be
supported. Access NEs do not support functions described in this topic.
9.6.1 Querying Subboards

You can query all subboards or the specified subboards.
9.6.2 Setting a Flag for a Subboard
You can set a flag for a subboard as required.
9.6.3 Exporting Subboard Information
The subboard information can be exported as a file in .xls, .txt, .html, or .csv format.
9.6.4 Collecting Statistics on a Subboard
The subboard information includes subboard attributes such as name, type, and version. You
can collect the statistics on a subboard based on each attribute.

9.6.1 Querying Subboards

You can query all subboards or the specified subboards.
Prerequisite
Context
Applies to the PTN series, Router series, Switch series, Security series NEs.
Procedure
1 Choose Inventory > Physical Inventory > Subboard from the main menu.
2 Query the subboard information.

l To query the information about all subboards, right-click on the Subboard List tab page
and choose Refresh from the shortcut menu. All the records are displayed in the query
result area.
NOTE

NOTE
l If the selected subboard does not support query on the NE side, the Prompt dialog box is
l If the selected subboard supports query on the NE side, the Operation Result dialog box
is displayed, prompting Operation succeeded or Operation succeeded partially or
Operation failed.
l To query the information about the specified subboards, click Filter, set the filter criteria,
and click OK.All records meeting the filter criteria are displayed in the query result area.
----End
9.6.2 Setting a Flag for a Subboard

You can set a flag for a subboard as required.
Prerequisite
Procedure
2 Right-click on the Subboard List tab and choose Refresh from the shortcut menu.

NOTE
NOTE
l If the selected Subboard does not support query on the NE side, the Prompt dialog box is
l If the selected Subboard supports query on the NE side, the Operation Result dialog box is
displayed, prompting Operation succeeded or Operation failed.
3 Select one or more subboards and right-click them. Then choose Set User Label from the
shortcut menu to set Remark and Customized Column.
NOTE
menu.
required.
----End
9.6.3 Exporting Subboard Information

The subboard information can be exported as a file in .xls, .txt, .html, or .csv format.
Prerequisite
Procedure
2 Right-click on the Subboard List tab and choose Refresh from the shortcut menu.
NOTE

NOTE
l If the selected Subboard does not support query on the NE side, the Prompt dialog box is
l If the selected Subboard supports query on the NE side, the Operation Result dialog box is
displayed, prompting Operation succeeded or Operation failed.
NOTE
4 Click OK to return to the Subboard List tab.
----End
9.6.4 Collecting Statistics on a Subboard

The subboard information includes subboard attributes such as name, type, and version. You
can collect the statistics on a subboard based on each attribute.
Prerequisite
Procedure
2 Click the Subboard Statistics tab. Select the subboard type from the Statistics Type drop-down
list and set Statistics Scope.
The subboard records in accordance with the statistics type are displayed in the query result area.
NOTE
2. In the Customize Subboard Statistics Type dialog box, click New.
3. In the New Customize Subboard Statistics Type dialog box, set related parameters, and
then click OK.
4. In the Customize Subboard Statistics Type dialog box, click OK.
The information about the Subboard statistics types, which meets the set conditions, is
NOTE

----End
9.7 Port Management

With the port management function, you can query and maintain ports. Port management
provides information such as the types, quantity, and belonging NEs of ports on the network so
9.7.1 Querying Ports

This topic describes how to query ports. To learn information about ports on the network, you
can query ports.
9.7.2 Setting a Port Flag
This describes how to set a port flag. You can set a flag for a port as required.
9.7.3 Exporting Port Information
This describes how to export port information. The port information can be exported as a file
9.7.4 Collecting Statistics on a Port
This topic describes how to measure the number of ports based on the port type.
9.7.1 Querying Ports

This topic describes how to query ports. To learn information about ports on the network, you
can query ports.
Prerequisite
Procedure
1 Choose Inventory > Physical Inventory > Port from the main menu.
2 Select the port type to be viewed from the Port Type drop-down list box.
3 Select the NE type to be viewed from the NE Type drop-down list box.
NOTE
In the query result area, all the records of the ports that comply with Port Type and NE Type are displayed.
4 Set the query condition to query specified ports.

The query GUI varies according to the type of port and NE. The following describes two methods
of querying ports by taking different NE types as examples.
l If the selected NE type is router or switch:
1. Click Condition. Set the filter criteria and click OK.
2. Click Query. In the query result area, the information about the ports meeting the
filter criteria is displayed.
l If the selected NE type is access NE, transport NE or PTN NE:

Click Filter. Set the filter criteria and click OK. In the query result area, the information
about the ports meeting the filter criteria is displayed.
----End
9.7.2 Setting a Port Flag

This describes how to set a port flag. You can set a flag for a port as required.
Prerequisite
Context
Applies to the router, switcher and firewall series equipment.
Procedure
NOTE
4 Select one or more port records and right-click them. Then choose Set User Label from the
shortcut menu to set Remark and Custom Column.
5 After the configuration is complete, click OK to return to the Port List tab.
menu.
required.
----End
9.7.3 Exporting Port Information

This describes how to export port information. The port information can be exported as a file
Prerequisite
Procedure

NOTE
NOTE
5 Click OK.
----End
9.7.4 Collecting Statistics on a Port

This topic describes how to measure the number of ports based on the port type.
Prerequisite
Procedure
2 Click the Port Statistics tab. Configure that the port statistics is implemented based on Port
Type.
The port statistics are displayed in the query result area.
NOTE
NOTE
----End
9.8 Collecting Statistics on the Slot Usage

This topic describes how to measure the number of total slots and the number of in-use slots
based on the NE type to help determine the board capacity and future capacity expansion.
Prerequisite

Procedure
1 Choose Inventory > Physical Inventory > Slot Used Statistics from the main menu.
2 Click the button to the right of NE Object. In the dialog box that is displayed, select the
required NE and click OK.
The information about the slots that match the NE is displayed in the query result area.
NOTE
When selecting an NE object, in the dialog box that is displayed, you can select the check box to the left
of the NE on which statistics are to be collected, or click Search and then set Content and Search
Mode in the Find Object dialog box.
NOTE
----End
9.9 Fiber/Cable Management

Fiber/Cable management refers to the operations of querying, collecting statistics on, and
maintaining fibers/cables. Fiber/cable management covers fiber/cable query, statistics, and
maintenance. Fiber/cable management provides information such as the types, levels/capacities,
lengths, and media of fibers/cables among NEs so that network status can be learned in time and
carriers' service planning and capacity expansion plans can be supported. Current alarms and
history alarms of fibers/cables can also be queried.
9.9.1 Creating Fibers/Cables in Batches

When fibers/cables are added in the network, you need to create the fibers/cables on the
U2000 for maintenance and management of the fibers/cables.
9.9.2 Importing a Link
This describes how to import a link. You can import the fiber/cables on NEs to Fiber/Cable
Management tab for management.
9.9.3 Querying a Fiber/Cable
You can query the details of all fibers/cables or a specified fiber/cable on the U2000.
9.9.4 Modifying a Fiber/Cable
When the information about the actual fiber/cable is changed, you need to synchronize the
change to the U2000.
9.9.5 Modifying Fibers/Cables in Batches
This topic describes how to modify cables/fibers in batches. If the information about several
actual fibers/cables changes and the changes are the same, you can modify the cables/fibers in
batches to quickly update the fiber/cable information on the NMS.
9.9.6 Deleting a Fiber/Cable

When the real fiber/cable is removed from the network, you need to delete the corresponding
fiber/cable data from the U2000.
9.9.7 Exporting the Fiber/Cable Information
The fiber/cable information can be exported and saved as a XLS, TXT, HTML, or CSV file.
9.9.8 Creating an Intermediate Office
When the fiber/cable between two NEs are forwarded through an intermediate office, you need
to create an intermediate office for the fiber/cable on the U2000.
9.9.9 Checking the Fiber/Cable Connection
The fibers/cables that are created on the U2000 may be inconsistent with the actual fibers/cables
on NEs. You can check the consistency by using the Detect Link function.
each link.
9.9.12 Querying the Fiber/Cable Pipe Associated to a Fiber/Cable
You can query the information about the fiber/cable pipe to which a fiber/cable belongs for easy
management.
9.9.13 Querying Alarms Related to a Fiber/Cable
This topic describes how to query alarms related to a fiber/cable, including current alarms and
history alarms.
9.9.1 Creating Fibers/Cables in Batches

When fibers/cables are added in the network, you need to create the fibers/cables on the
U2000 for maintenance and management of the fibers/cables.
Prerequisite
Procedure
2 In the window that is displayed, click Create. The Create Fibers in Batches window is
displayed.
3 Click New. A record of creating fiber/cable is displayed. You can modify the settings of the new
fiber/cable.
4 Optional: When you need to create more fibers/cables, you can do the step 3 repeatability

5 Click Apply, the fibers/cables are created.
----End
9.9.2 Importing a Link

This describes how to import a link. You can import the fiber/cables on NEs to Fiber/Cable
Management tab for management.
Prerequisite
l The links are displayed on the NMS. For details about how to links, see 9.11.2 Querying
a Link.
Context
l The following links can be imported: side-by-side links (links in the same network segment
with the 30-digit subnet mask), PPP links and links automatically discovered by LLDP.
l Applies to the Router, Switcher, Security, MSTP, WDM, NA WDM, RTN, PTN, Marine
series NEs.
Procedure
2 Right-click in the window that is displayed, and then choose Import Link from the shortcut
menu.
3 In the Import Link dialog box that is displayed, select one or more links. Perform the following
operations as required:
l Click . All links in the Available Link area are moved to the Selected Link area. This
operation is applicable to batch import.
4 Click OK.
The imported links are displayed on the Fiber/Cable Management tab.
----End
9.9.3 Querying a Fiber/Cable

You can query the details of all fibers/cables or a specified fiber/cable on the U2000.
Prerequisite

Procedure
2 In the window that is displayed, view the information about all fibers/cables.
3 Optional: Click Filter. The Set Fiber/Cable Browse Filter Conditions window is displayed.
Query the information about a specified fiber/cable after specifying filter criteria.
4 Optional: Click Print. After specifying the range of the fibers/cables to be printed in the window
that is displayed, you can specify the settings for printing in the Print dialog box.
5 Optional: Click Save As. In the window that is displayed, specify the range of the fibers/cables
and save them as an independent file.
----End
9.9.4 Modifying a Fiber/Cable

When the information about the actual fiber/cable is changed, you need to synchronize the
change to the U2000.
Prerequisite
Procedure
2 In the window that is displayed, select the cable to be modified and right-click the parameter to
be modified, and choose Modify Fiber/Cable from the shortcut menu.
3 In the dialog box that is displayed, modify the information about the fiber/cable and click OK.
4 Click Close. The actual fiber/cable information is updated on the NMS.
----End
9.9.5 Modifying Fibers/Cables in Batches

This topic describes how to modify cables/fibers in batches. If the information about several
actual fibers/cables changes and the changes are the same, you can modify the cables/fibers in
batches to quickly update the fiber/cable information on the NMS.
Prerequisite
Procedure
2 In the window that is displayed, select the fiber/cable records to be modified in batches, right-
click the parameters to be modified, and choose Modify Fiber/Cable from the shortcut menu.
3 In the dialog box that is displayed, modify the information about the fiber/cable and click OK.

4 Click Close. The actual fiber/cable information is updated on the NMS.
----End
9.9.6 Deleting a Fiber/Cable

When the real fiber/cable is removed from the network, you need to delete the corresponding
fiber/cable data from the U2000.
Prerequisite
Procedure
2 In the window that is displayed, select the fiber/cable record to be deleted and click Delete Fiber/
Cable, or right-click the record and choose Delete Fiber/Cable from the shortcut menu.
3 The Warning dialog box is displayed indicating the impacts brought by the deletion. Click
OK.
NOTE
When deleting a fiber/cable, you delete the protection subnets and trails that passes through the fiber/cable
and customized information of the fiber/cable. Exercise caution when deleting the fiber/cable. You can
export the script of the entire network in case of misoperation before deleting the fiber/cable.
4 After the deletion is complete, the Operation Result dialog box is displayed indicating that the
fiber/cable is successfully deleted from the U2000. Click Close.
----End
9.9.7 Exporting the Fiber/Cable Information

The fiber/cable information can be exported and saved as a XLS, TXT, HTML, or CSV file.
Prerequisite
Procedure
2 Optional: In the window that is displayed, set Filter to filter the fiber/cable information to be
exported.
3 Click Save As in the Fiber/Cable Management window.
4 In the dialog box that is displayed, set Start row and End row. Click the button after the File
name.
5 In the dialog box that is displayed, set the path, file name, and file type for saving the fiber/cable
information and click Save.

NOTE
l The default save path is \client\report\.

l The exported fiber/cable information can be saved as a XLS, TXT, HTML, or CSV file.
6 Click OK.
----End
9.9.8 Creating an Intermediate Office

When the fiber/cable between two NEs are forwarded through an intermediate office, you need
to create an intermediate office for the fiber/cable on the U2000.
Prerequisite
Applies to the router, switch series NEs and the MSTP, WDM, NA WDM, RTN, PTN, Marine
series NEs.
Context
Certain NEs are not connected through fibers/cables only. An intermediate office, which
functions as a Digital Distribution Frame (DDF), may exist between the two NEs. Hence, you
need to create an intermediate office of the fiber/cable on the U2000 for convenient maintenance.
Procedure
2 In the window that is displayed, click in the lower part. The Intermediate Office
Information tab page is displayed.
3 In the Fiber/Cable Information list, select the fiber/cable that you want to create an intermediate
office for.
4 Click Create Intermediate Office. A record of the new intermediate office is displayed. You
can modify the settings of the new intermediate office.
5 Click Apply.
----End
9.9.9 Checking the Fiber/Cable Connection

The fibers/cables that are created on the U2000 may be inconsistent with the actual fibers/cables
on NEs. You can check the consistency by using the Detect Link function.
Prerequisite
Context
Applies to the Router series, Switch series and the MSTP, WDM, NA WDM, RTN, PTN, Marine
series NEs.

Procedure
2 Right-click a fiber/cable in the Fiber/Cable Information list, choose Detect Link from the
shortcut menu. A progress bar of the check is displayed.
3 When the check is completed, the Operation Result dialog box is displayed indicating the check
result.
4 Click Close to complete the fiber/cable connection check.
----End
Result
If the fiber/cable that is created on the U2000 is inconsistent with the actual fiber/cable on NEs.
You can create the fiber/cable with the operation as follows.
l Method one: Right-click the fiber/cable, choose Delete Fiber/Cable From NM from the
shortcut menu, delete the misconnected fiber/cable from NM, then click Create to create
a new fiber/cable again, see 9.9.1 Creating Fibers/Cables in Batches.
l Method two: See 9.9.11 Searching for Fibers/Cables Automatically.

each link.
Prerequisite
l This operation is applicable to PTN series, Router series, Switch series, Security series
NEs, 3rd-Party series NEs.
l NEs must be created on the U2000 and the interface data must be successfully loaded.
l In the case of an LLDP link, you need to configure the SNMP, MIB view, and trap on the
NEs and enable the global LLDP on the NEs or on the U2000. For details, see the topic
LLDP Management for each NE Explorer in the topic Router and Switch Network
Management in the Online Help.
Context
l Links are logic and they cannot present the fiber/cable connections between devices.
Certain links must be imported to the U2000 as fibers/cables for management.
l LLDP discovery link: It refers to the Link Layer Discovery Protocol (LLDP) link. The Link
Layer Discovery Protocol (LLDP) is an L2D protocol defined in the IEEE 802.1ab. When
the LLDP protocol runs on the NEs, the U2000 can obtain the Layer 2 information about
all the NEs it connects and the detailed information about the network topology. This
expands the scope of network management. LLDP also helps find unreasonable
configurations on the network and reports the configurations to the U2000. This helps to
remove the errors in configurations timely.

l RPR link: It refers to the Resilient Packet Ring (RPR) link. The RPR protocol is a new
MAC layer protocol defined by IEEE 802.17. It is defined with the purpose of optimizing
the transmission of data packages and establishing an Ethernet MAN standard of sharing
bandwidth fairly over transmission media. Based on the high bandwidth usage, multi-server
access, high bandwidth of optical network, and powerful self-healing capability, the RPR
technology has the following features:
– Two-ring structure
– Space multiplexing mechanism
– Flexible service bandwidth granularity
– Dynamic bandwidth sharing and allocation
– Statistic multiplexing
– Service level
– Automatic recognition of the structure of network topology
– Protection switching based on the source route
l Cluster link: It refers to the cluster link. A cluster is a management domain with a group
of switches, including a command switch and multiple member switches. It manages all
the switches in the cluster, through a public IP address.
l SideBySide link: The IP addresses of the interfaces at both ends of the link are a pair of IP
addresses with 30-bit subnet mask.
Procedure
1 Choose File > Discovery > Link from the main menu.
2 Optional: In the Link Search window, select Nonexistent Links in NMS, Existed Links in
NMS, or Error Links as required.
3 Optional: Above the left-hand Object Tree, select Do you want to synchronize LLDP data
on the equipment? as required.
4 On the left-hand Object Tree, select one or more NEs, and click Search.
5 In the LLDP Status Management dialog box, set LLDP Status of the NEs to Open. Click
OK. After you complete the operation, a dialog box is displayed indicating that the operation is
NOTE
l The LLDP Status Management function is applicable to only routers, switches, the security NE.
l If a network does not have the preceding NE, the LLDP Status Management dialog box is not
displayed.
A dialog box is displayed indicating that It takes 30s before the enabled LLDP takes effect.
Are you sure to perform search? You can make the confirmation according to the actual
situation.
6 The progress bar shows the operation progress.
7 In the dialog box that prompts the success, click Close. In the window, the search results for
each links are displayed.

NOTE
l Nonexistent Links in NMS: The link exists only on NEs and is not created on the NMS.
l Existed Links in NMS: The link exists on the NMS and on the NEs.
l Error Links: The link has certain different data on NEs and the NMS.
8 Optional: You can select Nonexistent Links in NMS, Existed Links in NMS, or Error
Links to view the status of links. You can select a conflicting link and click Delete Error
Links to delete the link.
9 In the window, select one or more nonexistent links, and click Create.
The progress bar is displayed showing the progress of link creation.
10 In the dialog box that prompts the success, click Close.

The Are you sure to import links as fibers/cables dialog box is displayed.
11 Click OK in the Confirm dialog box.

l 1. The Import Link dialog box is displayed.
– Click . The selected link is moved to the Selected Link area.
– Click . All links in the Available Link area are moved to the Selected Link
area. This operation is applicable to batch import.
– Click . The selected link is moved to the Available Link area.
– Click . All links in the Selected Link area are moved to the Available Link
area.
NOTE
For PTN NEs, when import the link, you can set whether to allot IP address automatic on the
ports of the link.
3. Click OK.
NOTE
l The imported fibers/cables are displayed in the Fiber/Cable Management area.
\
l Click Cancel in the Confirm dialog box.
NOTE
12 Optional: Select conflicted links and click Error Links to delete the records.
----End
Follow-up Procedure
If you want to import links as fibers/cables after clicked the Cancel in the Import Link displayed
dialog box, you can perform the follow steps:

2. In the Fiber/Cable Management area, right-click, and choose Import Link from the
shortcut menu.
l Click . All links in the Available Link area are moved to the Selected Link area.
This operation is applicable to batch import.
NOTE
For PTN NEs, when import the link, you can set whether to allot IP address automatic on the ports
of the link.
4. Click OK. The imported fibers/cables are displayed in the Fiber/Cable Management area.

Prerequisite
l The optical interfaces of every NE must be connected using fibers.
l The boards of every NE must be created on the U2000.
l Applying to the MSTP, WDM, NA WDM, RTN, Marine NEs, but the OptiX OSN 1800
does not support. For PTN NEs, searching for fibers/cables automatically please see 9.9.10
Creating Links Automatically.
Context
l If conflicting fibers are found during the creation, delete the conflicting fibers on the
U2000 before you start creating fibers.
l When a fiber between two MSTP NEs passes through a WDM NE, if the normal fiber
between an MSTP NE and a WDM NE has been created on the U2000, the fiber found by
the trail search function is created as a virtual fiber. If the WDM NE is not created on the
U2000, the fiber is created as a normal fiber.
l Fibers that connect two WDM NEs cannot be searched.
l When a fiber is created, it is usually bidirectional. But when the fiber is connected to the
ports of the REG functions or the MSTP and WDM equipment, the fiber is unidirectional.
Procedure
2 In the left pane select some ports from one or more NEs and click Search to search for the fibers
or cables. A progress bar is displayed showing the progress of the search.

NOTE
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system
only searches for the ports that do not have fibers.
l To check if the created fiber is consistent with the actual fiber connection, leave the check box
unchecked.
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, and if all
the selected ports have fibers created, the system displays a message indicating that the search field is
null.
3 A prompt appears telling you that the operation was successful. Click Close.
4 To create fibers, select one or more fibers from the Physical Fiber/Cable Link List list and
click Create Fiber/Cable.
NOTE
l The NA WDM NEs do not support the function of conflicting fiber.

l When one or more fibers are selected in the Physical Fiber/Cable Link List list, fibers that conflict
with the selected fibers, are shown in the Logical Fiber/Cable Link List list. If there is any conflicting
fiber, proceed to Step 5 and delete it before creating fibers.
l During fiber creation, if all the selected fibers are in the Already created state, the system displays
the message as follows: No fiber to create.
5 To delete the conflicting fibers, from the Logical Fiber/Cable Link List list select one or more
fibers whose values are Yes for the Conflict with logical link(Y/N) parameter in the
Misconnected Fiber/Cable list. Click Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the fiber that is created through search is incomplete, you can
supplement the information about the fiber by modifying the fiber/cable information.
9.9.12 Querying the Fiber/Cable Pipe Associated to a Fiber/Cable

You can query the information about the fiber/cable pipe to which a fiber/cable belongs for easy
management.
Prerequisite
l The fiber/cable must be added into the fiber/cable pipe.
Context
l A fiber/cable can belong to multiple fiber/cable pipes. Therefore, the information about all
the pipes to which the fiber/cable belongs are listed after the query.
l Applies to the Router series, Switch series MSTP, WDM, NA WDM, RTN, PTN, Marine
series NEs.
Procedure

2 In the Fiber/Cable Information pane, right-click a fiber/cable, and then choose Query Fiber/
Cable Pipe from the shortcut menu. The Fiber/Cable Pipe Management window is displayed.
3 In the Pipe Information pane, the information about all the pipes to which the fiber/cable
belongs are displayed.
----End
9.9.13 Querying Alarms Related to a Fiber/Cable

This topic describes how to query alarms related to a fiber/cable, including current alarms and
history alarms.
Prerequisite
Procedure
2 In the window that is displayed, right-click the fiber/cable of which the related alarms are to be
queried, and then choose Browse Relevant Current Alarms or Browse Relevant Historical
Alarms from the shortcut menu. The Browse Current Alarms or Browse History Alarms
window is displayed.
3 In the Browse Current Alarms or Browse History Alarms window, you can browse the current
or history alarms of the fiber/cable, and query Details and Handling Suggestion of the alarms.
----End
9.10 Fiber/Cable Pipe Management

A fiber/cable pipe is a model for fiber/cable management. That is, multiple fibers/cables are
combined and considered as a pipe for management. The fibers/cables that are laid outdoors
often are combined and coated. A fiber/cable pipe contains multiple fibers/cables and a fiber/
cable belongs to multiple fiber/cable pipes. Fiber/cable pipe management helps to implement
unified management of fibers/cables through pipes.
9.10.1 Creating a Fiber/Cable Pipe

To manage certain fibers/cables as a pipe, you need to create a fiber/cable pipe.
9.10.2 Adding a Fiber/Cable into a Fiber/Cable Pipe
To use the function of platinum services, you need to perform the fiber/cable pipe management.
You can add a fiber/cable into a fiber/cable pipe for fiber/cable pipe management.
9.10.3 Querying a Fiber/Cable Pipe
You can query the fiber/cable to view the information about the pipe and the fibers/cables
contained in the pipe.
9.10.4 Modifying the Information About a Fiber/Cable Pipe
In the fiber/cable pipe management window, you can modify the information about a fiber/cable
pipe, including the name and remarks of the fiber/cable pipe.
9.10.5 Removing a Fiber/Cable from a Fiber/Cable Pipe

You can remove a fiber/cable from a fiber/cable pipe during fiber/cable pipe management.
9.10.6 Deleting a Fiber/Cable Pipe
You can delete the fiber/cable pipe that is no longer required.
9.10.1 Creating a Fiber/Cable Pipe

To manage certain fibers/cables as a pipe, you need to create a fiber/cable pipe.
Prerequisite
Procedure
1 Choose Inventory > Fiber/Cable > Fiber/Cable Pipe Management from the main menu.
2 Click Create in the Fiber/Cable Pipe Management window. In the New Pipe window that is
displayed, set Name, Memo, and Created by for the fiber/cable pipe. Click OK.
After you create a fiber/cable pipe, you can view the information about the new fiber/cable pipe
in the Pipe Information pane.
----End
9.10.2 Adding a Fiber/Cable into a Fiber/Cable Pipe

You can add a fiber/cable into a fiber/cable pipe for fiber/cable pipe management.
Prerequisite
l The fiber/cable and fiber/cable pipe must be created.
Context
A fiber/cable pipe can contain multiple fibers/cables and a fiber/cable can belong to multiple
fiber/cable pipes. When the probability of the simultaneous interruption of fibers/cables almost
reaches 100%, you can add those fibers/cables into the same fiber/cable pipe.
Procedure
2 Right-click a fiber cable in the Fiber/Cable Information pane and choose Query Fiber/Cable
Pipe from the shortcut menu. The Fiber/Cable Pipe Management window is displayed and
click Query.
3 In the pipe list, select the fiber/cable pipe that you want to add the fiber/cable into and then click
Move In Fiber.
4 In the Fiber/Cable Management window, right-click the fiber/cable pipe to be added into the
fiber/cable pipe and then choose Add to Fiber/Cable Pipe from the shortcut menu.

NOTE
You can select multiple fibers/cables and then add them into a certain pipe at the same time.
5 In the Pipe Information window displayed, select the pipe that you want to add the fiber/cable
into and then click OK.
NOTE
When selecting a pipe, you can set filter criteria to filter fiber/cable pipes. In the Pipe Information window,
click Filter. In the Pipe Filter window that is displayed, set the filter criteria and then click Filter.
6 In the operation result dialog box displayed, click Close.
7 Optional: In the Fiber/Cable Pipe Management window, click the pipe where the fiber/cable
is added in the Pipe Information list and then you can view the information about the fiber/
cable in the Fiber Information pane.
8 Optional: When the information about the fiber/cable pipe is changed, the platinum services
are affected. Therefore, you need to synchronize the platinum services. To synchronize platinum
services, click Synchronize Platinum Service. In the Operation Result dialog box displayed,
click Close.
NOTE
The U2000 license that is used must support platinum services.

If platinum services are not synchronized before you close the Fiber/Cable Pipe Management window,
a prompt is displayed, asking you to synchronize platinum services.
You can ensure that the platinum services are normal only after you synchronize platinum services.
Otherwise, the new platinum service may use incorrect pipe information.
----End
9.10.3 Querying a Fiber/Cable Pipe

You can query the fiber/cable to view the information about the pipe and the fibers/cables
contained in the pipe.
Prerequisite
l A fiber/cable pipe must be created.
Procedure
2 In the Pipe Information pane, you can view the information about all fiber/cable pipes.
3 Select a fiber/cable pipe and then you can view the information about the fibers/cables that are
contained in the pipe in the Fiber/Cable Information pane.
----End
9.10.4 Modifying the Information About a Fiber/Cable Pipe

In the fiber/cable pipe management window, you can modify the information about a fiber/cable
pipe, including the name and remarks of the fiber/cable pipe.

Prerequisite
l A fiber/cable pipe must exist.
Procedure
2 In the pipe list in the Pipe Information pane, double-click Pipe Name and Pipe Memo of a
certain pipe. Then, you can modify the name and remarks of the pipe.
3 After the modifications, click Apply.
4 In the Operation Result dialog box that is displayed, click Close.
----End
9.10.5 Removing a Fiber/Cable from a Fiber/Cable Pipe

You can remove a fiber/cable from a fiber/cable pipe during fiber/cable pipe management.
Prerequisite
l The fiber/cable must be added into a certain fiber/cable pipe.
Procedure
2 In the Pipe Information list, select a pipe. Then, the fibers/cables contained in the pipe are
displayed in the Fiber/Cable Information pane.
3 In the Fiber/Cable Information list, select the fiber/cable to be removed and then click Move
Fiber/Cable.
click Close.
NOTE

----End
9.10.6 Deleting a Fiber/Cable Pipe

You can delete the fiber/cable pipe that is no longer required.

Prerequisite
l A fiber/cable pipe must exist.
Context
When a fiber/cable pipe is deleted, the fibers/cables that are contained in the pipe are not deleted.
Procedure
2 In the pipe information list, select the fiber/cable pipe to be deleted and then click Delete.
click Close.
NOTE

----End
9.11 Link Resource Management

This describes the function that the NMS provides to manage link resources between Datacomm
devices. Link source management provides information such as the types and levels of links
among NEs so that link alarm severities and networking information can be learned in time and
carriers' service planning can be supported. Users can view link alarm information to quickly
locate and rectify faults according to detailed alarm information and handling suggestions. This
function is applicable to Router series, Switch series, Security series, Access series NEs.
9.11.1 Synchronizing Trunk Links

This topic describes how to synchronize trunk links between equipment. Trunk links are used
to bear VLANs. If trunk links are unavailable, the NMS cannot determine whether the VLANs
between equipment are connected.
9.11.2 Querying a Link
This describes how to query a link. When you query a link, such as the virtual link, Layer-2 link
and IP link, the link information is displayed.
9.11.3 Creating a Link
This topic describes how to create a link. You can create a virtual link, Layer-2 link and IP link
in Link Management.
9.11.4 Viewing Link Information
This describes how to view link information. The details include the alarm status, source NE,
sink NE, source port and sink port.
9.11.5 Viewing Link Alarms

This describes how to view link alarms, which are alarms from the NE on the source or sink of
the link.
9.11.6 Creating a Link View
Creating a link group is premised with the link view creation. You can manage many link groups
in a link view.
9.11.7 Creating a Link Group
This describes how to create a link group. To ease link management, the links are logically
divided into link groups according to a certain rule.
9.11.8 Adding a Link to the Link Group
This describes how to add a link to the link group. You can add links to a link group and manage
the links in compliance with the same rule in a unified manner.
9.11.1 Synchronizing Trunk Links

This topic describes how to synchronize trunk links between equipment. Trunk links are used
to bear VLANs. If trunk links are unavailable, the NMS cannot determine whether the VLANs
between equipment are connected.
Prerequisite
Procedure
1 Choose Inventory > Link Management from the main menu.
2 In the Link Management window, right-click in the query result area and choose Synchronize
Trunk Link from the shortcut menu.
3 Whether the synchronization is successful is displayed in the dialog box that is displayed.
l If Operation succeeded is displayed, click Close. The synchronized trunk links are displayed
in the physical view.
l If Operation failed is displayed, the failure cause is displayed.
----End
9.11.2 Querying a Link

This describes how to query a link. When you query a link, such as the virtual link, Layer-2 link
and IP link, the link information is displayed.
Prerequisite
Procedure
2 On the Link Management tab, click Filter to set filter criteria.

NOTE
To select a source NE or sink NE, expand or double-click a submap record and select the required NE in
the submap.
3 Click OK.
The information about the links meeting the query conditions is displayed in the query result
area.
----End
9.11.3 Creating a Link

This topic describes how to create a link. You can create a virtual link, Layer-2 link and IP link
in Link Management.
Prerequisite
Procedure
2 Click New.
3 In the Create Link dialog box that is displayed, click New, set Link Type, and specify Source
NE, Source Port, Sink NE, and Sink Port.
NOTE
l After you specify Source NE, Source Port, Sink NE, and Sink Port, a name is created automatically
in the Link Name field. You can rename the link according to your naming conventions.
l To select a source NE or sink NE, expand or double-click a submap record and select the required NE
in the submap.
4 Click Apply. In the Operation Result dialog box, Operation succeeded is displayed. Then,
click Close.
The created link is displayed in the query result area of link management.
NOTE
If creating a link is abnormal, the cause is displayed in the Operation Result dialog box. You can rectify
the fault based on the cause.
----End
9.11.4 Viewing Link Information

This describes how to view link information. The details include the alarm status, source NE,
sink NE, source port and sink port.
Prerequisite

Procedure

NOTE
the submap.
3 Click OK.
All the link information meeting the query conditions is displayed in the query result area.
----End
9.11.5 Viewing Link Alarms

This describes how to view link alarms, which are alarms from the NE on the source or sink of
the link.
Prerequisite
Procedure

NOTE
the submap.
3 Click OK.
All the link information meeting the query conditions is displayed in the query result area.
4 Select a link in the link list and right-click it. Then, select View Alarm.
5 In the Browse Current Alarms window, check the alarms of the NE related to the link, including
Alarm Detail Information and Process Advice.
----End
9.11.6 Creating a Link View

Creating a link group is premised with the link view creation. You can manage many link groups
in a link view.
Prerequisite
Procedure
1 Choose Inventory > LinkGroup from the Main Menu.

2 Right-click in the Link View group box and select Create Link View.
3 In the Create Link View dialog box, set Name and Description.
4 Click OK.
----End
9.11.7 Creating a Link Group

This describes how to create a link group. To ease link management, the links are logically
divided into link groups according to a certain rule.
Prerequisite
l You must create a link view first, and then the link group. For detailed operation, see 9.11.6
Creating a Link View.
Procedure
2 In the Link View group box, select the link view in which the link group is to be created.
3 Right-click in the Link Group box. Select Create Link Group.
4 In the Create Link Group dialog box, set Name and Description.
5 Click OK.
----End
9.11.8 Adding a Link to the Link Group

This describes how to add a link to the link group. You can add links to a link group and manage
the links in compliance with the same rule in a unified manner.
Prerequisite
l A link is created. For details about how to create a link, see 9.11.3 Creating a Link.
Context
Only the links in the physical view can be imported.
Procedure
2 In the Link View area, select the link view containing the link group to which a link is to be
added.
Information about the link groups contained in this link view is displayed in the Link Group
area.

3 In the Link Group area, select a link group where a link will be added.
4 Right-click in the Link area, and then choose Import Link from the shortcut menu.
5 In the Import Link dialog box that is displayed, set query conditions, and then click OK.
6 Select one or more links you want to import to the link group. Click OK to start the import.
If the imported link is displayed in the query result area of Link, it indicates that the link is
successfully added to the link group.
----End
9.12 Interface Resource Management

This topic describes how to manage the interface resources of datacom devices through the NMS.
Interface resource management provides information such as the names, types, belonging NEs,
IPv4 addresses, and MAC addresses of interfaces on the network so that detailed NE interface
information can be learned in time and carriers' service planning and capacity expansion plans
can be supported.
9.12.1 Querying Router/Switch Interface Resources

This topic describes how to query interface resources such as the interface description,
administrative status, and running status.
9.12.2 Setting a Router/Switch Interface Flag
This topic describes how to set a flag for an interface as required.
9.12.3 Exporting Router/Switch Interface Information
This topic describes how to export interface information and save it as a file in .xls, .txt, .html,
or .csv format.
9.12.4 Querying a PTN Interface Resource Report
This topic describes how to query a PTN interface resource report. During deployment, you can
export a networkwide PTN interface resource report that includes the information such as the
NE name, port, IP address, and MAC address for checking and modifying interface
configurations of NEs.
9.12.1 Querying Router/Switch Interface Resources

This topic describes how to query interface resources such as the interface description,
administrative status, and running status.
Prerequisite
Context
Interface resources include port resources. Thus, all port resources are displayed when you query
interface resources.
Procedure
1 Choose Inventory > Router/Switch Interface from the main menu.

2 In the Confirm dialog box, determine whether to start synchronizing the inventory of the router/
switch interfaces.
l If you need to instantly synchronize the inventory of the router/switch interfaces, click
OK. A dialog box is displayed, indicating the synchronization progress. After a while, the
synchronization result is displayed. Click Close. The Filter Criteria dialog box is displayed.
Set the filter criteria and click OK. The Router/Switch Interface tab page is displayed.
l If you do not need to instantly synchronize the inventory of the router/switch interfaces, click
Cancel. The system returns to the Router/Switch Interface tab page.
3 Optional: On the Router/Switch Interface tab, click Filter to set the filter criteria.
4 Optional: Click OK.

All records meeting the filter criteria are displayed in the query result area.
NOTE
l When the Router/Switch Interface tab page is displayed, if router/switch interface inventories are
synchronized, you can skip Steps 3 and 4.
l If router/switch interface inventories are not synchronized immediately, you need to perform Steps 3
and 4.
5 Optional: The heading of the query result area supports the customization function. Concerned
parameters can be displayed as required. There are two customization methods:
Method one
l Right-click on the heading of the query result area and choose Setting from the shortcut
menu.
l In the Column Setting dialog box that is displayed, select the check boxes of the parameters
to be displayed.
l Click OK.
Method two: Right-click on the heading of the query result area and select the parameters to be
displayed.
NOTE
Trough method one, all the concerned parameters can be selected once. Through method two, only one
parameter can be selected after each right click.
----End
9.12.2 Setting a Router/Switch Interface Flag

This topic describes how to set a flag for an interface as required.
Prerequisite
Procedure
switch interfaces.


NOTE
and 4.
5 In the query result area, right-click an interface record and choose Set UserMaker from the
shortcut menu to set Remark.
6 After configuration, click OK to return to the Router/Switch Interface tab page.
----End
9.12.3 Exporting Router/Switch Interface Information

This topic describes how to export interface information and save it as a file in .xls, .txt, .html,
or .csv format.
Prerequisite
Procedure
switch interfaces.


NOTE
and 4.
5 Optional: Export the information about interface resources.

1. Click Save As. Then, set Start row, End row and File Name.
NOTE
By default, the information about interface resources is saved as XLS, TXT, HTML, or CSV files in
the client folder. You can change the saving path as required.
2. After configuration, click Save.
----End
9.12.4 Querying a PTN Interface Resource Report

This topic describes how to query a PTN interface resource report. During deployment, you can
export a networkwide PTN interface resource report that includes the information such as the
NE name, port, IP address, and MAC address for checking and modifying interface
configurations of NEs.
Prerequisite
Procedure
1 Choose Inventory > PTN Statistic Report > Interface Resource Report from the main menu.
2 On the Physical Root navigation tree, select the NE to be queried and click .
The existing interface resource information in the NMS database is displayed.
NOTE
You can click to refresh the NE list on the Physical Root navigation tree.
3 Click Query.
The current interface resource information about the NE is displayed.
NOTE
----End

9.13 Collecting Statistics on the ONU

This topic describes how to collect statistics on the ONU types on the entire network based on
the equipment type or collect statistics on each terminal type and ONU version based on the
submap.
Prerequisite
Context
This function is applicable only to access-domain NEs.
Procedure
1 Choose Inventory > Physical Inventory > ONU from the main menu.
2 Click Filter. In the dialog box that is displayed, set the statistics range and click OK.
The ONU information within in the statistics range is displayed in the query result area.
----End
9.14 Collecting Statistics on the Split Status of PON Ports

This topic describes how to collect statistics on the split status of PON ports. By checking the
split ratio usage of PON ports, you can determine whether to perform capacity expansion.
Prerequisite
l PON Port Splitting Status is displayed on the main menu only after the OLT is added and
synchronized successfully.
Context
This function is applicable only to access-domain NEs.
Procedure
1 Choose Inventory > PON Port Splitting Status from the main menu.
2 Click the GPON Port Statistics tab.
3 Click the drop-down list box to the left of Find and select All.
The statistics of all GPON ports are displayed in the query result area.
4 Optional: Click Find. In the dialog box that is displayed, set the filter criteria to query the
statistics of a specified GPON port.
5 Click the EPON Port Statistics tab.

6 Click the drop-down list box to the left of Find and select All.
The statistics of all EPON ports are displayed in the query result area.
7 Optional: Click Find. In the dialog box that is displayed, set the filter criteria to query the
statistics of a specified EPON port.
----End
9.15 Exporting Electronic Labels of NEs

Before upgrading the U2000, you need to export the information about the NEs or cards, such
as hardware electronic labels and versions, from the U2000 and save the information in TXT or
XML format. This facilities the management and statistics of inventory resources on a network.
Prerequisite
l Before you export the script files, you must check configuration data consistency to ensure
that configuration data on the U2000 is consistent with that on NEs.
Context
With the increase of devices on existing networks, the lack of electronic labels will lead to
difficult device maintenance and management and rising costs.
An electronic label is the unique traceable identifier of a card throughout the whole lifecycle.
With electronic labels, operation and maintenance engineers can obtain card manufacturing
information such as the production data and place, software version information, and hardware
version information remotely or through the U2000. Also, operation and maintenance engineers
can learn the card source and destination, whether the card has been back to fix, and the current
version, which facilitates card maintenance, management, and tracing and reduces maintenance
and management costs in the whole lifecycle.
Procedure
l Method 1
NOTE
This method is applicable to MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs.
1. Choose Administration > Back Up/Restore NMS Data > Import/Export Script
File from the main menu.
2. Set the format of the exported script file as TXT.
3. Select CEAS as the script file type from the Script File Type drop-down list.
4. Set the script file to the Export form.
5. In Export NE List, select the NEs where you want to export script files.
6. In Operation Directory List, specify the directory where you want to save the
exported script files.

NOTE
You can select a subdirectory in the default directory. You can also create a subdirectory.
To create a subdirectory, do as follows: Click Create File Directory. In the Input dialog box,
enter the name of the new subdirectory. Click OK.
7. Click Apply. The Confirm dialog box is displayed, indicating "Exporting will
overwrite all the script files that were previously exported. Are you sure to
continue?" You can choose whether to continue the export operation as required.
8. Click OK. A progress bar is displayed.
9. After the export operation is complete, the Operation Result dialog box is displayed
indicating the successful exporting operation and the directory where the exported
files are saved.
NOTE
The script file is saved on the U2000 server. In Windows, the backup directory is %
IMAPROOT%\server\script. In Solaris and SUSE Linux, the backup directory is
$IMAPROOT/server/script. You can create a new directory under it.
IMAPROOT is the NMS installation path.
You can view the exported script files in the preceding directory.
l Method 2
NOTE
This method is applicable to Router series, Switch series, Security series, Access series NEs.
1. Choose Inventory > Project Document > Export Electronic Label from the main
menu.
2. In the Export Electronic Label dialog box, enter the file name according to the
prompts.
3. In the Export Electronic Label dialog box, click Select the export NE.
4. In the Select the export NE dialog box, select the NEs where you want to export
electronic labels.
NOTE
l To select all NEs, select Export electronic label files of all NEs.
l To select a specific NE, clear Export electronic label files of all NEs and select the
required NE in the Navigation Tree.
5. In the Select the export NE dialog box, click OK.
6. In the Export Electronic Label dialog box, click OK.
7. After the electronic labels of the NEs are exported, a dialog box is displayed indicating
the directory where the exported electronic label files are saved.
NOTE
In Windows, the electronic label exporting path is %U2000%\server\var\projdoc\dump. In

Solaris and Linux, the electronic label exporting path is $U2000/server/var/projdoc/dump.
You can view exported electronic label files in the electronic label exporting path.
U2000 is the NMS installation path.
8. In the Confirm dialog box, click OK.
----End

9.16 SDH Report

The SDH report includes various statistics reports on different dimensions, such as on the SDH
NEs, cards, ports. These reports offer useful data for the project maintenance.
9.16.1 Collecting Statistics on the SDH Ports

In this report, you can view different types of ports that are used by services or protection.
9.16.2 Collecting Statistics on the SDH lower Order Cross-Connections
The lower order cross-connection statistics report provides the information of capacity of lower
order cross-connections and available lower order cross-connections on each NE in a network.
You can also customize the thresholds of lower order cross-connection alerts. By planning before
adding services, you can prevent insufficient lower order cross-connections during actual service
configuration.
9.16.3 Collecting Statistics on SDH Tributary Port Resources
Before creating an SDH trail, you can query the SDH tributary port resources, according to which
you can determine the trail creation scheme.
9.16.4 Collecting Statistics on Trails Between SDH NEs
By collecting statistics on the trail resource inventory between SDH NEs, you can check whether
the resources are sufficient before configuring services.
9.16.5 Collecting Statistics on the SDH Protection Subnet Resources
The statistics on the information about protection subnet resources include the basic information
about protection subnets and detailed parameters of each node.
9.16.6 Collecting Statistics on SDH Trail Resources
Through the statistics report of SDH circuit resources, you can learn the usage of SDH trail
resources.
9.16.7 Collecting Statistics on SDH Fiber Resource Usage
You can collect the occupancy of the SDH fiber resource in a topological subnet or a protection
subnet. Based on the occupancy, you can plan the services.
9.16.8 Creating a Timing Task for Collecting Statistics on SDH Resources
You can create a timing task so that statistics can be collected automatically at the specified
time.
9.16.1 Collecting Statistics on the SDH Ports

In this report, you can view different types of ports that are used by services or protection.
Prerequisite
The configured service must form the trail on the U2000 by using the trail search.
Procedure
1 Choose Inventory > SDH Report > Port Resource Report from the main menu.

2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red). In the
right-hand pane, view the generated report.
3 Optional: Click Alarm Threshold Set. In the Alarm Threshold Set dialog box, you can set
parameters as required.
NOTE
The default values are as follows:

l 90% to 100%: Urgent Threshold. The corresponding cell in the report is displayed in red.
l 70% to 89%: Emergency Threshold. The corresponding cell in the report is displayed in orange.
l 60% to 69%: Attention Threshold. The corresponding cell in the report is displayed in yellow.
l Less than 60% means normal. The corresponding cell in the report is in the regular color.
4 Optional: Click Print or Save As to output the report.
----End
9.16.2 Collecting Statistics on the SDH lower Order Cross-

Connections
The lower order cross-connection statistics report provides the information of capacity of lower
order cross-connections and available lower order cross-connections on each NE in a network.
You can also customize the thresholds of lower order cross-connection alerts. By planning before
adding services, you can prevent insufficient lower order cross-connections during actual service
configuration.
Prerequisite
l Lower order cross-connections must be created.
Procedure
1 Choose Inventory > SDH Report > Lower Order Cross-Connections Statistic Report from
the main menu.
2 In the Object Tree on the left, select one or more NEs and click the double-right-arrow button
(red). On the right, you can view the lower order cross-connection statistics report of the selected
NE queried from the U2000.
NOTE
Only NEs that support lower order cross-connection querying are displayed in the Object Tree.
3 Click Alarm Threshold Set, you can view or modify the threshold value. If the lower order
cross-connections occupancy reaches a specified threshold, a pre-alarm at different levels is
generated.
NOTE
The default values of alerts are as follows:

l 90% to 100%: Urgent Threshold. The corresponding cell in the report is displayed in red.
l 70% to 89%: Emergency Threshold. The corresponding cell in the report is displayed in orange.
l 60% to 69%: Attention Threshold. The corresponding cell in the report is displayed in yellow.
l Less than 60% means normal. The corresponding cell in the report is in the regular color.

----End
9.16.3 Collecting Statistics on SDH Tributary Port Resources

Before creating an SDH trail, you can query the SDH tributary port resources, according to which
you can determine the trail creation scheme.
Prerequisite
You must be an NM user with "network monitor" authority or higher.
Context
You can schedule a timing task for automatic statistics collection. For details, see 9.16.8
Creating a Timing Task for Collecting Statistics on SDH Resources.
Procedure
1 Choose Inventory > SDH Report > Statistics Report of SDH Tributary Port Resources from
the Main Menu.
2 In the Object Tree in the left pane, select one or more NEs for statistics and click the double-
right-arrow button (red). In the right pane, the details of the tributary port resources of the selected
NEs is displayed.
3 Click Statistics to query the resource information of the SDH tributary ports.
----End
9.16.4 Collecting Statistics on Trails Between SDH NEs

By collecting statistics on the trail resource inventory between SDH NEs, you can check whether
the resources are sufficient before configuring services.
Prerequisite
Context
Procedure
1 Choose Inventory > SDH Report > Statistics Report of Trails Between SDH NEs from the
Main Menu.
right-arrow button (red). In the right pane, the detailed information of the trail resources between
NEs is displayed.

3 Optional: Click Statistics Condition. In the Statistics Condition dialog box that is displayed,
set the level of the desired trails.
----End
9.16.5 Collecting Statistics on the SDH Protection Subnet Resources

The statistics on the information about protection subnet resources include the basic information
about protection subnets and detailed parameters of each node.
Prerequisite
Procedure
1 Choose Inventory > SDH Report > Statistics Report of SDH Protection Subnet
Resources from the main menu.
2 In the Filter window, select the protection subnet type and click Filter.
3 In the Statistics Report of SDH Protection Subnet Resource window, view the resources of
the qualified protection subnets.
----End
9.16.6 Collecting Statistics on SDH Trail Resources

Through the statistics report of SDH circuit resources, you can learn the usage of SDH trail
resources.
Prerequisite
Context
They can be counted in the following two ways:
Statistics by... Description
Subnet Counts the number of trails at each level and

get the total number of trails according to
every selected subnet.
Customer Counts the number of leased trails at each

level and get the total number of trails
according to every selected customer.

Procedure
1 Choose Inventory > SDH Report > Statistics Report of SDH Circuit Resources from the
main menu.
2 Click the Statistics by Subnet or Statistics by Customer tab in the left-hand pane.
3 In the Object Tree, select one or more subnets or customers and click the double-right-arrow
button (red). You can view the generated report in the right-hand pane.
----End
9.16.7 Collecting Statistics on SDH Fiber Resource Usage

You can collect the occupancy of the SDH fiber resource in a topological subnet or a protection
subnet. Based on the occupancy, you can plan the services.
Prerequisite
Context
Procedure
1 Choose Inventory > SDH Report > SDH Fiber/Microwave Link Resource Usage Report
from the main menu.
2 Choose Statistics by Affiliated Subnet or Statistics by Protection Subnet tab.
3 Select a subnet from the Object Tree, and then click the double-right-arrow button (red). The
occupancy of the relevant fiber/cable resource is displayed on the right side.
4 Optional: Select Contain discrete service, you can view the information of the discrete services
in the Port Resource Report resource usage report.
5 Optional: Click Filter and set the filtering criteria to display the required information in the
fiber/cable resource usage report.
6 Optional: Click Alarm Threshold Set, you can view or modify the threshold value. If the fiber
cable resource occupancy reaches a specified threshold, a pre-alarm at different levels is
generated.

NOTE

l 90% to 100%: Urgent Threshold. The corresponding information in the report is displayed in red.
l 50% to 89%: Attention Threshold. The corresponding information in the report is displayed in yellow.
l Less than 50% means normal. The corresponding information in the report is displayed in green.
----End
9.16.8 Creating a Timing Task for Collecting Statistics on SDH

Resources
time.
Context
The items for timing statistics include fiber cable occupancy resources, SDH trail statistics
between NEs, and TU port resource statistics.
Procedure
1 Choose Administration > Task Schedule > Task Management from the Main Menu.
2 Click SDH Resource Statistic in Task Type in the pane on the left.
3 Click New.
4 In the displayed dialog box, enter a name for the Task Name field.
5 Choose Run Type. Click Next.
6 Set Start Time. Click Next.
NOTE
When you set Run Type to Period, you need to specify the period for running the task. When you set Run
Type to Once, you can select the Run At Once to immediately run the task and the setting of a period is
not required.
7 Select Report file type, File type, and Storage path on server.
8 Optional: To collect statistics on the resources of a specified object, select Statistic by
Affiliated Subnet or Statistic by protection Subnet, and select the object.
9 Click OK.
----End
9.17 Microwave Report

The microwave report includes various statistics reports on different dimensions, such as on the
microwave equipment and links. These reports offer useful data for the project maintenance.
9.17.1 Collecting Statistics on the Microwave License Capacity

The microwave license capacity report provides the information about the RTN NE service
capacity supported by the license and the actual service capacity.
9.17.2 Collecting Statistics on Microwave Links
You can collect the information of the microwave links in a topological subnet. Based on the
occupancy, you can plan the services.
9.17.3 Collecting Statistics on Microwave Link Resource Usage
You can collect the occupancy of the microwave link resource in a topological subnet or a
protection subnet. Based on the occupancy, you can plan the services.
9.17.1 Collecting Statistics on the Microwave License Capacity

The microwave license capacity report provides the information about the RTN NE service
capacity supported by the license and the actual service capacity.
Prerequisite
Procedure
1 Choose Inventory > Microwave Report > Microwave License Capacity Report from the
main menu.
2 Select NEs from the Object Tree, and then click the double-right-arrow button (red). The
information of the microwave license capacity is displayed on the right side.
----End
9.17.2 Collecting Statistics on Microwave Links

You can collect the information of the microwave links in a topological subnet. Based on the
occupancy, you can plan the services.
Prerequisite
Procedure
1 Choose Inventory > Microwave Report > Microwave Link Report from the main menu.
2 Select NEs from the Object Tree, and then click the double-right-arrow button (red). The
occupancy of information of the microwave links is displayed on the right side.
----End
9.17.3 Collecting Statistics on Microwave Link Resource Usage

You can collect the occupancy of the microwave link resource in a topological subnet or a
protection subnet. Based on the occupancy, you can plan the services.

Prerequisite
Context
Menu item names displayed on the U2000 vary with different licenses.
Procedure
1 Choose Inventory > SDH Report > SDH Fiber/Microwave Link Resource Usage Report
from the Main Menu.
2 Choose Statistics by Affiliated Subnet or Statistics by Protection Subnet tab.
3 Select a subnet from the Object Tree, and then click the double-right-arrow button (red). The
occupancy of the relevant microwave link resource is displayed on the right side.
4 Optional: Click Filter and set the filtering criteria to display the required information in the
microwave link resource usage report.
5 Optional: Click Alarm Threshold Set, you can view or modify the threshold value. If the
microwave link resource occupancy reaches a specified threshold, a pre-alarm at different levels
is generated.
NOTE

l 90% to 100%: Urgent Threshold. The corresponding information in the report is displayed in red.
l 50% to 89%: Attention Threshold. The corresponding information in the report is displayed in yellow.
l Less than 50% means normal. The corresponding information in the report is displayed in green.
----End
9.18 WDM Statistic Report

The WDM statistics report includes various statistics reports on different dimensions, such as
on the WDM NEs, cards and ports. These reports offer useful data for the project maintenance.
9.18.1 Collecting Statistics on the WDM Protection Group Switching State

You can view the switching status of all WDM protection groups in a network in the WDM
protection group switching status report.
9.18.2 Collecting Statistics on WDM NE Master/Slave Shelf Information
By viewing the WDM NE master/slave shelf information report, you can learn about the basic
information of the master/slave shelf on an NE, such as the shelf name, shelf equipment type,
and slave shelf ID.
9.18.3 Collecting Statistics on WDM Client-Side Port Resources
By collecting statistics on resource inventory for WDM client-side ports (Ethernet service and
client-side ports of the OTU board), you can check whether the resources are sufficient before
configuring services.
9.18.4 Collecting Statistics on Wavelength Resources Between WDM Sites

The statistics report of inter-station wavelength resources shows the usage of the wavelength
resources of one or more trails between the selected stations. This provides reference for service
planning and increases the service availability ratio.
9.18.5 Statistics Report of WDM Link Resources
By using this function, you can learn about the usage of the WDM link resources between the
specific stations. This provides reference for service planning and increases the service
availability ratio.
9.18.6 Collecting Statistics on Wavelength Resource Usage
Through the wavelength resource usage report, you can learn the usage of wavelength resources.
9.18.7 Creating a Timing Task for Collecting Statistics on WDM Resources
time.
9.18.8 Viewing WDM Channel Resources
This topic describes how to view the occupancy of WDM channel resources.
9.18.1 Collecting Statistics on the WDM Protection Group

Switching State
You can view the switching status of all WDM protection groups in a network in the WDM
protection group switching status report.
Prerequisite
l A WDM protection group must be created.
Context
You can query the basic information and switching status of a WDM protection group from the
U2000 in the WDM protection group switching status report. You can also print the report or
save it as a file. The navigation path for an external switching is not provided.
Procedure
1 Choose Inventory > WDM Statistic Report > WDM Protection Group Switching State
Report from the main menu. Click the WDM Protection Group Switching Status Report or
WXCP Switching Status Report tab.
(red). On the right, you can view the WDM protection group switching status report of the
selected NE queried from the U2000.
3 Click Query to refresh the switching status of the protection groups from the NE.
5 Optional: Select one or more records in the list, right-click, and choose Browse Relevant
Trails from the shortcut menu. The WDM Trail Management window is displayed. You can
view the information about the trails that are relevant to the protection.

NOTE
In the case of the TPS protection, the Browse Relevant Trails shortcut menu item is not available. That
is, you cannot switch to the WDM Trail Management window.
----End
9.18.2 Collecting Statistics on WDM NE Master/Slave Shelf

Information
By viewing the WDM NE master/slave shelf information report, you can learn about the basic
information of the master/slave shelf on an NE, such as the shelf name, shelf equipment type,
and slave shelf ID.
Prerequisite
Procedure
1 Choose Inventory > WDM Statistic Report > WDM NE Master/Slave Shelf Info Report
from the main menu.
2 In the left-hand Object Tree, select an NE and click . In the right-hand pane, you can
view the generated WDM NE master/slave shelf information report.
3 Click Query to query the actual WDM NE master/slave shelf information from the NE.
4 Optional: Click Print to print the report or click Save As to export the report.
----End
9.18.3 Collecting Statistics on WDM Client-Side Port Resources

By collecting statistics on resource inventory for WDM client-side ports (Ethernet service and
client-side ports of the OTU board), you can check whether the resources are sufficient before
configuring services.
Prerequisite
Context
Creating a Timing Task for Collecting Statistics on WDM Resources.
Procedure
1 Choose Inventory > WDM Statistic Report > Statistics Report of WDM Client-Side Port
Resources from the Main Menu.
2 In the left-hand pane, select an NE and click the double-right-arrow button (red).
3 Click Statistics to query the resource information of the WDM client-side ports.

4 Click Used Port, Idle Port or Dynamic Port tab to query details of the ports.
NOTE
l If a client-side port is not used by a trail, this port is idle. Otherwise, this port is used.
l Discrete services are taken as idle resources.
----End
9.18.4 Collecting Statistics on Wavelength Resources Between

WDM Sites
The statistics report of inter-station wavelength resources shows the usage of the wavelength
resources of one or more trails between the selected stations. This provides reference for service
planning and increases the service availability ratio.
Prerequisite
l You must be an NM user with "network monitor" authority or higher.
l You cannot collect statistics on the wavelengths that are used by WDM ASON trails at the
OCh level.
Context
To ensure that statistics are correct, it is recommended that you search for WDM trails before
you collect statistics on wavelength resources.
Procedure
1 Choose Inventory > WDM Statistic Report > Statistics Report of Inter-Station Wavelength
2 Set the Level and Direction of the trail to be counted.

NOTE
Currently, only OCh trails are supported.
3 Click Browse to select the source end and click the button again to select the sink end. Click
OK in the Search NE dialog box.
NOTE
The source and sink ends can be optical NEs or NEs.
4 Optional: Click Browse to select the intermediate NE.

NOTE
You can select multiple intermediate NEs to determine the trail to be counted out of multiple trails between
the source and sink ends.
5 Click Count. The Confirm dialog box is displayed prompting you to search for trails before
collecting statistics.

6 Click OK. The Operation Result dialog box is displayed indicating that the operation was
successful. Click Close. You can view the created report in the right-hand pane.
NOTE
If there is a large number of network data, it takes a long time to create the report.
----End
9.18.5 Statistics Report of WDM Link Resources

By using this function, you can learn about the usage of the WDM link resources between the
specific stations. This provides reference for service planning and increases the service
availability ratio.
Prerequisite
Context
Procedure
1 Choose Inventory > WDM Statistic Report > Statistics Report of WDM Link Resources
from the main menu.
2 In the left pane, select NEs and click .

NOTE
You can select a maximum of ten NEs.
3 In the Statistics Report of WDM Link Resources pane, view the link resources among stations.
4 In the Statistics Report of WDM Link Resources pane, select a record. Then, in the Link
List pane, view the details of all the links between the two stations.

5 Optional: Right-click one or more links in the Link List pane and choose Browse Relevant
Client Trails from the shortcut menu to view the client trail of this link.
----End
9.18.6 Collecting Statistics on Wavelength Resource Usage

Through the wavelength resource usage report, you can learn the usage of wavelength resources.
Prerequisite
Procedure
1 Choose Inventory > WDM Statistic Report > Wavelength Resource Usage Report from the
Main Menu.
(red). On the right, you can view the wavelength resource usage report.
3 Optional: Click Print to print the report or click Save As to export the report.
----End
9.18.7 Creating a Timing Task for Collecting Statistics on WDM

Resources
time.
Context
The items for timing statistics include WDM client port resource statistics, WDM statistics on
inter-station wavelength resource, and WDM link resource statistics.
Procedure
1 Choose Administration > Task Schedule > Task Management from the Main Menu.
2 Click WDM Resource Statistic in Task Type in the pane on the left.
3 Click New.
4 In the displayed dialog box, enter a name for the Task Name field.

5 Choose Run Type. Click Next.

6 Set Start Time. Click Next.
NOTE
When you set Run Type to Period, you need to specify the period for running the task. When you set Run
Type to Once, you can select the Run At Once to immediately run the task and the setting of a period is
not required.
7 Select Report file type, File type, and Storage path on server.
8 Click OK.
----End
9.18.8 Viewing WDM Channel Resources

This topic describes how to view the occupancy of WDM channel resources.
Prerequisite
Context
You can collect the information automatically through scheduled tasks. For details, see 9.18.7
Procedure
1 Choose Inventory > WDM Statistic Report > Browse WDM Channel Resource from the
main menu.
2 Specify filter criteria and click . In the list on the right, the number of channels of the
OMS trails and the occupancy of the channels are displayed.
3 Select a route where you want to check WDM channel resources. In the Wavelength Allocation
Table area, all channels are displayed. Meanwhile, you can learn whether the channels are
occupied by OCh trails.

NOTE
If a channel is occupied by an OCh trail, the name of the OCh trail is displayed in the OCh Trail column.
You can right-click the channel and choose Client Trail Information from the shortcut menu to switch
to the WDM Trail Management window. In the window, you can view the details of the OCh trail.
4 Select one or more trails and click Detailed Trail Information below the list to switch to the
WDM Trail Management window. In the window, you can view the details of the OMS trail.
----End
9.19 MSTP Ethernet Report

The MSTP Ethernet report includes various statistics reports on different dimensions, such as
on the MSTP Ethernet ports and NEs. These reports offer useful data for the project maintenance.
9.19.1 Collecting Statistics on Ethernet Port Resources

By collecting statistics on the Ethernet port resources, you can check whether the resources are
sufficient before configuring services.
9.19.2 Collecting Statistics on Service Resources Between Ethernet NEs
By collecting statistics on the Ethernet inter-NE service resources, you can check whether the
resources are sufficient before configuring services.
9.19.1 Collecting Statistics on Ethernet Port Resources

By collecting statistics on the Ethernet port resources, you can check whether the resources are
sufficient before configuring services.
Prerequisite
Procedure
1 Choose Inventory > MSTP Ethernet Report > Statistics Report of Ethernet Port
2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red).
3 Click Statistics and the statistics results are displayed in the right-hand pane. You can view
details of the Ethernet ports.
----End
9.19.2 Collecting Statistics on Service Resources Between Ethernet

NEs
By collecting statistics on the Ethernet inter-NE service resources, you can check whether the
resources are sufficient before configuring services.
Prerequisite

Procedure
1 Choose Inventory > MSTP Ethernet Report > Statistics Report of Service Resources
Between Ethernet NEs from the Main Menu.
right-arrow button (red).
3 Click Statistics and the statistics results are displayed in the right-hand pane. You can view
details of the Ethernet service information.
4 Optional: Click Print or Save As to output the details of the Ethernet inter-NE service resource
statistics.
----End
9.20 Project Document

The project document includes various information reports on different dimensions, such as NE
information report, card manufacturer information report, clock tracing diagram, networking
diagram, and timeslot allocation diagram. These reports offer useful data for the project
maintenance.
9.20.1 Viewing the Board Manufacturer Information Report

The board manufacturer information report provides the information of board, such as the bar
code, type, manufacture date, BOM code, and manufacturer information of the optical module.
After configuring a new board, you need to update the board manufacturer information report.
You can refer to this report during board maintenance.The board manufacturer information
report provides the information of board. After configuring a new board, you need to update the
board manufacturer information report. You can refer to this report during board maintenance.
9.20.2 Viewing Common Manufacturer Information Report
The common manufacturer information report provides information about the bar code, type,
production date, BOM, and CLEI code for all boards that do not occupy slot numbers.
9.20.3 Viewing the Clock Tracing Diagram
The clock tracing diagram includes NE information such as ID, extended ID, name, equipment
type. The display and the NE positions of the clock tracing diagram are consistent with those of
the Main Topology. You can print and save the clock tracing diagram. After a change of the
clock scheme or a change in the network (for example, new NEs are added), save the updated
clock tracing diagram in time.
9.20.4 Viewing the Networking Diagram
You can generate and print the networking diagram. In the networking diagram, you can query
the information such as NE name, type, ID, extended ID and fiber or cable length. The positions
of the NEs in the networking diagram are consistent with the positions of the NEs in the Main
Topology. After the networking is complete, save the networking diagram in time.
9.20.5 Viewing the Timeslot Allocation Diagram
When managing SDH networks, the timeslot allocation diagram shows the services that have
been configured in the selected protection subnet. After configuring new services, you need to
immediately save the latest timeslot allocation diagram.

9.20.1 Viewing the Board Manufacturer Information Report

The board manufacturer information report provides the information of board, such as the bar
code, type, manufacture date, BOM code, and manufacturer information of the optical module.
After configuring a new board, you need to update the board manufacturer information report.
You can refer to this report during board maintenance.The board manufacturer information
report provides the information of board. After configuring a new board, you need to update the
board manufacturer information report. You can refer to this report during board maintenance.
Prerequisite
The board software (of the board that you want to query) supports querying of the board version
information.
Procedure
1 Choose Inventory > Project Document > Board Manufacturer Information from the main
menu.
2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red). You
can view the generated report in the right-hand pane.
3 Click Query to query the information from the NE.
----End
9.20.2 Viewing Common Manufacturer Information Report

The common manufacturer information report provides information about the bar code, type,
production date, BOM, and CLEI code for all boards that do not occupy slot numbers.
Prerequisite
The board software (of the board that you want to query) supports querying of the board version
information.
Context
The boards that do not occupy slot numbers mainly include the backplane, fan board, and power
supply board. In the common manufacturer information report, the slot number is displayed as
0.

Procedure
1 Choose Inventory > Project Document > Board Manufacturer Information from the main
menu.
2 Click the Common Manufacturer Information tab.
3 Select one or more NEs from the left-hand Object Tree, and click the double-right-arrow button
(red). You can view the generated common manufacturer information report in the right-hand
pane.
4 Click Query to query the actual common manufacturer information from the NE.
----End
9.20.3 Viewing the Clock Tracing Diagram

The clock tracing diagram includes NE information such as ID, extended ID, name, equipment
type. The display and the NE positions of the clock tracing diagram are consistent with those of
the Main Topology. You can print and save the clock tracing diagram. After a change of the
clock scheme or a change in the network (for example, new NEs are added), save the updated
clock tracing diagram in time.
Prerequisite
Procedure
1 Choose Inventory > Project Document > Clock Tracing Diagram from the main menu. View
the information in the generated clock tracing diagram.
2 Optional: In the clock tracing diagram, right-click and choose Zoom In, Zoom Out and
Restore from the shortcut menu to set the display size of the diagram.
3 Optional: In the clock tracing diagram, right-click and choose Add Comments from the
shortcut menu to add comments to an object in the diagram.
NOTE
l After you add comments, use the mouse to drag the comments to the position around the corresponding
NE or subnet.
l If you want to modify the comments, double-click the comments and modify them in the Edit
Comments dialog box.
l If you want to delete the comments, right-click the comments and choose Delete Comments from the
shortcut menu.
4 Optional: In the clock tracing diagram, right-click and choose Customize from the shortcut
menu to select the parameters that you want to display in the clock tracing diagram.
5 Optional: In the clock tracing diagram, right-click and choose Page from the shortcut menu to
set the page size of the diagram.

6 Optional: In the clock tracing diagram, right-click and choose Font Size from the shortcut menu
to select the appropriate font size.
7 Optional: In the clock tracing diagram, right-click and choose Print or Save As to output the
report.
----End
9.20.4 Viewing the Networking Diagram

You can generate and print the networking diagram. In the networking diagram, you can query
the information such as NE name, type, ID, extended ID and fiber or cable length. The positions
of the NEs in the networking diagram are consistent with the positions of the NEs in the Main
Topology. After the networking is complete, save the networking diagram in time.
Prerequisite
Procedure
1 Choose Inventory > Project Document > Networking Diagram from the main menu. View
the information in the generated networking diagram.
2 In the Object Tree, select the NEs that you want to display in the networking diagram and click
the double-right-arrow button (red).
3 Optional: In the networking diagram, right-click and choose Customize from the shortcut menu.
The Customize dialog box is displayed. Select the parameters that you want to display in the
networking diagram, and click OK.
4 Optional: In the networking diagram, right-click and choose Add Comments from the shortcut
menu to add comments to an object in the diagram.
NOTE
l After you add comments, you can use the mouse to drag the comments to the position around the
corresponding NE or subnet.
l If you want to modify comments, double-click the comments and then modify them in the Edit
Comments dialog box.
l If you want to delete comments, right-click the comments and choose Delete Comments from the
shortcut menu.
5 Optional: In the networking diagram, right-click and choose Font Size from the shortcut menu
to select a proper font size.
6 Optional: In the networking diagram, right-click and choose Zoom In, Zoom Out and
Restore to set the display size of the networking diagram.
7 Optional: In the networking diagram, right-click and choose Page to set the page size for the
networking diagram.
NOTE
After the networking diagram is generated, some objects and information may be overlapped. In this case,
use the mouse to drag them to proper positions.

8 Optional: In the networking diagram, right-click and choose Print to print the networking
diagram or choose Save As to export the networking diagram.
----End
Result
l In the Save As field, enter the directory where you want to save reports.
l After the networking diagram is saved, you can view the saved report in the directory that
is indicated in the Save As
9.20.5 Viewing the Timeslot Allocation Diagram

When managing SDH networks, the timeslot allocation diagram shows the services that have
been configured in the selected protection subnet. After configuring new services, you need to
immediately save the latest timeslot allocation diagram.
Prerequisite
The protection subnet must be created.
Context
The U2000 exports the timeslot assignment diagram in SVG format. To view or print the
diagram, install the SVG Viewer. On Windows, refer to common/SVG/PC/pcreadme.txt on
how to install the SVG Viewer; On UNIX, refer to common/SVG/Unix/unixreadme.txt. The
installation process takes five minutes or less.
Procedure
1 Choose Inventory > Project Document > Timeslot Allocation Diagram from the main menu.
2 Select a protection subnet in the Generate Timeslot Allocation Diagram dialog box. Click
Start. The U2000 generates the timeslot allocation diagram of this protection subnet and save
it in the client\report directory.
NOTE
On UNIX, the timeslot allocation diagram that the U2000 automatically creates is saved in the client/
report directory.
3 Navigate to the client\report directory, double-click the SVG file to view the timeslot allocation
diagram. If there are more than three NEs in a protection subnet, use the Alt key to view all NEs
in the diagram.
----End

Operation Guide for Common Features 10 Backing Up and Restoring the U2000 Database
10 Backing Up and Restoring the U2000

Database
About This Chapter
To ensure the security of network data, the U2000 provides the function of backing up and
restoring network data.
10.1 Basic Concepts and Application Scenarios

This topic describes basic concepts and application scenarios of backup and restoration of
U2000 data.
10.2 Methods of Backing Up and Restoring the U2000 Data
This topic describes how to configure the policies for backing up and restoring data. You can
back up and restore the U2000 data in two ways: Back up and restore all data in U2000 databases,
and back up and restore the U2000 network configuration data by using scripts.
10.3 U2000 Database List
This topic describes the list of databases and function for the U2000. The database files of the
U2000 server are used to store data or store the log information that is generated during the
running of the database.
10.4 Suggestions on Data Backup and Restoration
This topic provides suggestions on backup and restoration of U2000 data.
10.5 Backing Up and Restoring All Data in U2000 Database
This topic describes how to back up and restore all data in U2000 databases.
10.6 Backing Up and Restoring the U2000 Network Configuration Data by Using Scripts
This topic describes how to back up and restore the U2000 network configuration data by using
scripts.
10.7 Setting Alarm/Event Timing Dump
10.8 Setting U2000 Log Timing Dumping

10 Backing Up and Restoring the U2000 Database Operation Guide for Common Features

This topic describes how to dump performance data. The performance data can be dumped in
two modes, namely, automatic dumping and manual dumping.

10.1 Basic Concepts and Application Scenarios

This topic describes basic concepts and application scenarios of backup and restoration of
U2000 data.
Basic Concepts
l Backup
Back up is a method used to store important data to prevent the damage of the original data.
You can back up network configuration data, alarm data and performance data.
The U2000 provides the following schemes to backup the database: backup of the U2000
databases and the data by using scripts. For details on the differences between the three
schemes, refer to the 10.2 Methods of Backing Up and Restoring the U2000 Data.
l Restoration
Restoration coexists with backup. When certain data is damaged or destroyed, you can
restore the data.
Restoration is to restore database data from the backup file, and then overwrite the existing
data file. Both backup and restoration are used to ensure the security of network data.
l Dump
Dump is a method used to store the log information in databases as operating system files
in text format, to clear database space.
The dumped objects are various types of logs, including alarm events, abnormal events,
operation logs and different types of performance events.
The U2000 provides three methods of dumping logs. The three methods are overflow dump,
scheduled dump and immediate dump.
– The overflow dump is performed when the logs in the databases reach the maximum
storage capacity. You can specify the number of logs to dump.
– The scheduled dump, which is the alternative method of overflow dump, is optional.
You can set whether to create a scheduled task, and if you create a scheduled task you
can specify the schedule time and duration.
– The immediate dump is also referred to as manual dump. This method is used to dump
data that was created on a specific date.
The three methods of dumping logs automatically delete the corresponding data in
databases. You can open a text file to view the log contents.
Application Scenarios
l Backup and restoration of U2000 data can be implemented in the following scenarios based
on the OS type:
– Single-server system (Solaris)
– Single-server system (SUSE Linux)
– Single-server system (Windows)
– High availability system (Solaris)
– High availability system (SUSE Linux)
– High availability system (Windows)
on the location of backup data:

– Local data backup and restoration

Data of a specific server is backed up to a local disk and the backup data is then used
to restore U2000 data. For example, back up data of server A to disk D on server A, and
then use the backup data on disk D to restore data of server A.
– Remote data backup and restoration
Data of the U2000 server is backed up to a remote server and the backup data on the
remote server is then used to restore U2000 data. For example, back up data of server
A to remote server B, and then use the backup data on remote server B to restore data
of server A.
on the source of data for restoration.
– Local data restoration
Backup data of the local server is used to restore server data. For example, use backup
data of server A to restore data of server A.
– Remote data restoration
Backup data of another server is used to restore data of the specific server. For example,
use backup data of server B to restore data of server A.
10.2 Methods of Backing Up and Restoring the U2000 Data

This topic describes how to configure the policies for backing up and restoring data. You can
back up and restore the U2000 data in two ways: Back up and restore all data in U2000 databases,
and back up and restore the U2000 network configuration data by using scripts.
Backing Up and Restoring the U2000 Databases

The U2000 databases are automatically created during the initial installation of the U2000. When
you back up the U2000 databases, the databases are saved as operating system files. The
information that is backed up includes the user-defined data at the U2000 side, network layer
trail data, NE-side configuration data, alarm data and performance data. In addition, a backup
is created for the structure of the entire database, all database tables (including the system tables
and the user tables), table structure, and stored procedures.
NOTE
The following data is not backed up when you back up the U2000 database:
l The data that is not saved at the NE side, that is, the data that cannot be uploaded. For details, refer to
the appendix Configuration Data Management Information List of the online help.
l The custom options of the system.
Importing and Exporting Script Files (This Function is Applicable Only to the
Transport Domain)
The U2000 provides the function of exporting and importing script files, to back up and restore
the network configuration data of the U2000. This realizes the upgrade of the configuration data
with zero loss during the U2000 upgrade. For details, see 10.6 Backing Up and Restoring the
U2000 Network Configuration Data by Using Scripts.

NOTE
l The default coding format in a script file is UTF-8. To change the coding format of the script file, in
the Windows OS, you can change encoding configuration item in the installation path of the NMS/
server/cbb/trans/core/conf/xml/script/script_enum.xml configuration file; In the Solaris or SUSE
Linux OS, you can change encoding configuration item in the installation path of the NMS/server/
cbb/trans/core/conf/xml/script/script_enum.xml configuration file.
l By default, the name of a script file contains the NE name. To exclude the NE name from a script file
name, in the Windows OS, you can change the scriptname configuration item in the installation path
of the NMS/server/cbb/trans/core/conf/xml/script/script_enum.xml configuration file. In the
Solaris or SUSE Linux OS, you can change the scriptname configuration item in the installation path
of the NMS/server/cbb/trans/core/conf/xml/script/script_enum.xml configuration file.
l The data are exported from the U2000 database.
l The imported script files update the data on the U2000 only, with no impact on the data on the NEs.
Comparison of Two Data Maintenance Methods

The characteristics of the two data maintenance methods determine their application
scenarios.Table 10-1 lists the characteristics and application scenarios of the three methods.
Table 10-1 Characteristics and application scenarios of two data maintenance methods
Method Characteristics Application Scenario
Backing up and restoring all l Backs up the structure and l This requires a large
data in the U2000 databases contents of the U2000 storage medium space. If
database. you want to back up the
l The data is in the binary U2000 database in a
mode. scheduled manner, large-
size disk is
l Backs up all data of the recommended.
U2000 database.
l Backup data of an OS
l The processing speed is cannot be used for data
fast. restoration of another
l The backup file is big. version or type of OS.
l Backup data of a database
cannot be used for data
restoration of another
version or type of
database.

Method Characteristics Application Scenario
Backing up and restoring the l Exports the configuration l This method is usually
U2000 network data in the U2000 to a txt used to upgrade the
configuration data by using file that is similar to the U2000. The new U2000
the script files MML format. This is version is compatible
done to save data. You with the scripts of the old
can directly understand version.
the configuration l This method is usually
contents of the txt file. used to back up and
l Backs up only some of the restore the basic
data, including the basic configuration data for a
configuration data, port single NE. This method
naming data and user- also restores the user-
defined data. defined data.
l The processing speed is
slow.
l The backup file is small.
10.3 U2000 Database List

This topic describes the list of databases and function for the U2000. The database files of the
U2000 server are used to store data or store the log information that is generated during the
running of the database.
Table 10-2 shows the descriptions of databases for the U2000.
Table 10-2 U2000 database list
Database Name Function
MCDB Distribution Manager Database
InventoryDB Inventory Manage system Database
ReportDB Report Manage system Database
BMSDB Access Service Management Database
nemgr_sdhDB SDH NE Management Database
nemgr_rtnDB RTN NE Management Database
ason_sdh_db ASON SDH Management Database
ason_wdm_db ASON WDM Management Database
nemgr_ngwdmDB (nemgr_otnDB) OTN NE Management Database
TransPerfDB Transmits Perfomance Manage system Database
nemgr_wdmDB WDM NE Management Database

nemgr_extDB Extended NE Management Database
nemgr_ngwdmaDB (nemgr_naotnDB) NAOTN NE Management Database
nemgr_nawdmDB NAWDM NE Management Database
nemgr_marineDB Marine NE Management Database
ason_naotn_db ASON NAOTN Management Database
ason_otn_db ASON OTN Management Database
OAMSDB OAMS Management Database
nemgr_ptnDB PTN/ATN Service Management Database
TNCOMMONDB Service Management Base Component Database
TNSDHDB SDH Service Management Database
TNOTNDB WDM Service Management Database
TNETHDB MSTP Service Management Database
TNIPDB IP Service Management Database
TNCPSDB Composite Service Management Database
IPCommonDB IP Common Application Database
IPBaseDB IP Base Service Database
RouterMgrDB Router Manage System Database
SgMgrDB Service Gateway Manage System Database
GctlDB General configuration template Database
DmsBatchConfigDB IP domain Batch Config Database
DmsNetAclDB IP domain NetAcl Database
FrameSWMgrDB Switch NE Manager(Frame) Database
BoxSwitchMgrDB Switch NE Manager(Box ) Database
SecurityMgrDB Security NE Database
SecServiceDB Security Service Database
PMSDB Perfomance Manage system Database
XFTPDB XFTP Database
EnpowerDB Environment Power Database
ALARMDB Database of FaultService
IMAPEAMDB Database of EAMService

IMAPLOGDB Database of LogService
IMAPSMDB Database of SecurityService
IMAPTEMPDB Temporary Database
IMAP_DB Common Database
IMAPTMDB Database of TopoService
10.4 Suggestions on Data Backup and Restoration

This topic provides suggestions on backup and restoration of U2000 data.
l When you install the U2000 for the first time, back up the U2000 databases. Back up the
U2000 databases once, if you do not expand the databases. If the hard disk is large (if the
available space exceeds 10 GB), you can back up the U2000 databases on a quarterly basis.
l Before backing up the data, upload the NE data, and perform the search of the protection
subnets and trails.
l To avoid a situation in which data occupies too much disk space, clean the data that is
previously backed up, on a regular basis.
l Before restoring U2000 databases, you must shut down the U2000 server and ensure that
the databases are not used by other users.
10.5 Backing Up and Restoring All Data in U2000 Database

This topic describes how to back up and restore all data in U2000 databases.
10.5.1 Immediately Backing Up the U2000 Database to a Local Server Through the U2000
Client
When a fault occurs on the system, you can quickly restore system data by using the backup
data of the database.
10.5.2 Periodically Backing Up the U2000 Data to a Local Server Through the U2000 Client
This topic describes how to enable the periodically backup of the U2000 database to the local
server. After this configuration, the database can be safely and quickly restored after a fault
occurs.
10.5.3 Periodically Backing Up the U2000 Data to a Remote Server Through the U2000 Client
This topic describes how to back up the U2000 database to a remote server in a scheduled manner.
It is recommended that dedicated data backup server be configured for importance sites such as
central telecommunication room and the U2000 database be backed up to this server periodically.
In this way, the U2000 database can be safely and quickly restored in the case of a database
fault.
10.5.4 Restoring a U2000 Database
This describes how to restore all data in the U2000 database. When necessary, you can use the
backed up data to restore a database to the status during backup.

10.5.1 Immediately Backing Up the U2000 Database to a Local

Server Through the U2000 Client
When a fault occurs on the system, you can quickly restore system data by using the backup
data of the database.
Prerequisite
Context
The backup process cannot be canceled once it is started.
Back up the database file to the default path as follows. The backed up data is generated in a
folder named by time:
l On Solaris and SUSE Linux, back up the database file to the installation path of the NMS/
server/var/backup.
l On Windows, back up the database file to the installation path of the NMS\server\var
\backup.
Procedure
NOTE
The default user name is admin and password is null. When you log in to the system for the first time, the
system requires you to change the password.
2 Choose Administration > Back Up/Restore NMS Data > Database Backup from the main
menu.
3 Set the backup path on the server, and then click Backup.The U2000 atabase backup starts and
a dialog box is displayed showing the backup progress.
NOTE
Customizing a backup path helps to avoid the affect of system reinstallation and disk formatting on backup
data. This improves the maintainability of the system.
The backup path should be short, and cannot contain any space, punctuation, or Chinese character.
----End
10.5.2 Periodically Backing Up the U2000 Data to a Local Server

Through the U2000 Client
This topic describes how to enable the periodically backup of the U2000 database to the local
server. After this configuration, the database can be safely and quickly restored after a fault
occurs.
Prerequisite
l The database is running.
l Ensure that all users have been logged out of the NMS maintenance suite client.

l If you need to create a backup path in the Solaris OS or the SUSE Linux OS, log in to the
OS as the root user, and then run the following commands to create a backup path and
assign read, write, and execute rights to the backup path:
# mkdir backup path
# chmod -R 775 backup path
Context
l The time of executing the scheduled tasks of different types cannot be the same, neither
can the involved NEs. Otherwise, task execution fails because of conflicts in obtaining
resources.
l The U2000 does not support multiple periodic backup tasks at the same time. The difference
between the time points to start scheduled tasks must be greater than the maximum running
period of the tasks.
l It is recommended that you set the scheduled backup time to the time when network service
traffic is light, such as at midnight.
Procedure
NOTE
3 Click New. The New Task dialog box is displayed.
4 Choose Task Type > Backup. Select DB Backup as the task type and enter a name for the
scheduled task. Select Once or Period as the run type. Then click Next.
5 In Time Setting, set the planed start time of the task. If Period is selected, in Period Setting,
set the planed period and execution times of the task. Then, click Next.
CAUTION
If multiple scheduled backup tasks are configured, ensure that times set for theses tasks do not
overlap; otherwise, backup fails.
6 Select Back up the data to the local server and enter a backup path on the local server. Then
click Finish.
----End
Result
On the Task Management tab page, choose Task Type > Backup > DB Backup from the
service tree. Then, the created task is displayed.

10.5.3 Periodically Backing Up the U2000 Data to a Remote Server

Through the U2000 Client
This topic describes how to back up the U2000 database to a remote server in a scheduled manner.
It is recommended that dedicated data backup server be configured for importance sites such as
central telecommunication room and the U2000 database be backed up to this server periodically.
In this way, the U2000 database can be safely and quickly restored in the case of a database
fault.
Prerequisite
l The database is running.
l In the case of remote backup and recovery, the FTP or SFTP server programs must be
running on the remote server, and the relevant port must be enabled on the local server.
The port of FTP server is 21, and the port of SFTP server is 22.
NOTE
You can run the following commands to confirm that the SFTP service can be connected normally
on the server:
1. # vi /etc/ssh/sshd_config
2. Add # to the front of "PAMAuthenticationViaKBDInt yes", and enter the :wq! command to save
the setting and exit.
3. # svcadm restart network/ssh
l The FTP or SFTP user must have the write authority in a remote FTP server.
Context
resources.
Procedure
3 Choose Task Type > Backup. Select DB Backup as the task type and enter a name for the
scheduled task. Select Once or Period as the run type. Then click Next.
4 In Time Setting, set the planed start time of the task. If Period is selected, in Period Setting,
set the planed period and execution times of the task. Then, click Next.

CAUTION
If multiple scheduled backup tasks are configured, ensure that times set for theses tasks do not
overlap; otherwise, backup fails.
5 Select Back up the data to the remote server and enter a backup path on the remote server.
Then click Finish.
----End
Result
On the Task Management tab page, choose Task Type > Backup > DB Backup from the
service tree. Then, the created task is displayed.
10.5.4 Restoring a U2000 Database

This describes how to restore all data in the U2000 database. When necessary, you can use the
backed up data to restore a database to the status during backup.
Procedure
1 Log in to the NMS maintenance suite to restore the U2000 database. The procedure for restoring
the U2000 database varies according to the OS environment. For details about how to restore
U2000 data, see Backing Up and Restoring the U2000 Database in the iManager U2000 Unified
Network Management System Administrator Guide or the U2000 data restoration procedure
described in Managing Databases in the Help of the U2000 NMS maintenance suite.
----End
10.6 Backing Up and Restoring the U2000 Network

Configuration Data by Using Scripts
This topic describes how to back up and restore the U2000 network configuration data by using
scripts.

CAUTION
Not all U2000 data can be backed up or restored by using scripts. Instead, backing up and
restoring all data in the U2000 database is recommended.
Using scripts to back up and restore data makes the following impacts:
l NBIs are affected. The upper-layer OSS must use physical IDs or logical IDs of NEs as
indexes to interwork with the U2000. During U2000 upgrade, physical IDs of NEs are
constant and logical IDs are assigned by the U2000 again. Physical IDs are recommended
if the U2000 is interconnected to an upper-layer OSS. If the upper-layer OSS uses logical
IDs as indexes, NEs must be uploaded after data restoration. Fibers/cables, subnets, and
optical NEs have only logical IDs. If the upper-layer OSS uses data about the fibers/cables,
subnets, or optical NEs, the fibers/cables, subnets, or optical NEs must be uploaded again.
l Only basic information is stored in scripts, whereas other information must be obtained by
uploading NEs. Therefore, you must manually restore customized information that is stored
on neither NEs nor scripts; otherwise, the information will be lost. Information that requires
manual restoration includes but is not limited to:
l Customized information (background and sound configurations) on clients
l Alarm performance template configurations
l Security information, such as NMS user name and password
l Path naming rule
l ACL
l The following information cannot be restored manually or using scripts. It is recommended
that you dump the information before restoration by using the dumping function of the
U2000.
l History alarm
l History performance
l U2000 operation log
l Abnormal event
10.6.1 Script Files

When you upgrade the U2000, you can upgrade the configuration data with zero data loss by
importing and exporting the scripts. Script files that contain the basic data are required for
importing and exporting scripts.
10.6.2 Immediately Backing Up the U2000 Data by Script
Before upgrading the U2000, you must export the data from the database to script files and save
these files to import the data back to the U2000 after the upgrade.
10.6.3 Backing Up the U2000 Data Through Script Exporting in a Scheduled Manner
In routine maintenance, you can use the scheduled task function to export network configuration
data as script files in a scheduled manner to ensure timely backup of customized information.
In addition, this function can be performed without any manual intervention and thus reduces
maintenance costs.
10.6.4 Restoring the U2000 Data by Using the Script
After upgrading the U2000, you can restore the U2000 network layer configuration data from
the backup script files.

10.6.1 Script Files

When you upgrade the U2000, you can upgrade the configuration data with zero data loss by
importing and exporting the scripts. Script files that contain the basic data are required for
importing and exporting scripts.
Script File Type

Table 10-3 lists the types of the script files in the .txt format that the U2000 provides and the
contents of the data.
Table 10-3 Script files the U2000 provides

Script File Type Naming Rule Contained Data Whether the
Import or Export
Feature Is
Supported
Networkwide None The networkwide This file can be

Configuration File configuration file is imported and
the whole set of the exported.
following script files.
When the network-
wide configuration
file is exported, the
NE port naming file,
NE configuration
file, NE list file,
network layer
information file, and
other scripts are
exported. When the
network-wide
configuration file is
imported, the NE
configuration file
and the NE port
naming file are
imported in sequence
according to the NEs
contained in the NE
list file. The network
layer information file
is also imported.
NE Port Naming File NEPort_extension This file contains the This file can be
ID-basic ID_NE naming information imported and
name_coding about every port on exported.
format.txt the NE.


Import or Export
Feature Is
Supported
NE Configuration NEData_extension This file contains the This file can be

File ID-basic ID_NE configuration imported and
name_coding information that is exported.
format.txt similar to the
command lines. The
configuration
information contains
all data that is
required to recreate
an NE and to ensure
that the NE is
functioning
normally. The
version and
manufacturing
information of the
board are listed at the
end of the file.
NE List File NWNeList_U2000 This file contains This file can be

name_coding information about imported and
format.txt NEs, U2000, and exported.
their physical
location. When the
NE list file is
imported or
exported, the NE port
naming file and the
NE configuration file
are imported or
exported in sequence
according to the NE
list file.


Import or Export
Feature Is
Supported
NM Computer NMInfo_U2000 This file contains the This file can be

Information File name_coding configuration exported but cannot
format.txt information about be imported.
the U2000 server. NOTE
The configuration It can be used to
information is as import third-party
follows: software such as
MDS.
l Hardware
information such
as the operating
system name and
its version,
operating system
patch version,
physical memory,
CPU count and
frequency
l Network
information such
as the host name
and IP address
l Database
information such
as the database
name and its
version


Import or Export
Feature Is
Supported
Service NWSvcData_U2000 This file provides This file can be

Actualization Script name_coding service actualization exported but cannot
format.txt data scripts for the be imported.
transport service
actualization system.
The service
actualization data
scripts are as follows:
l NE attributes
l Board installation
l Board protection
l Protection
relationship
l Service
configuration
l Protection
subnets
l Trail
configuration
Network Layer NWCfg_U2000 This file contains This file can be

Information File name_coding information on the imported and
format.txt network layer exported.
configuration,
including the
following:
l Fiber cable
connections
l Protection
subnets
l Trail
configuration
Network Modeling None This file contains This file can be

and Design information on MDS imported and
Information File network modeling exported.
and design.
CEAS NEData_extension This file provides This file can be

ID-basic ID_NE scripts for the exported but cannot
name_coding operation that is be imported.
format.txt performed on
multiple NEs in
batches.

In addition, the U2000 provides the script files in the .xml format for the network planning and
design, containing the network-wide configuration file, NE configuration file, network layer
information file, and ASON information file. The ASON information file can be imported and
exported, but other types of script files in the .xml format can be exported only.
NOTE
l The default coding format in a script file is UTF-8. To change the coding format of the script file,
you can change encoding configuration item in the installation path of the NMS/server/cbb/trans/
core/conf/xml/script/script_enum.xml configuration file.
l By default, the name of a script file contains the NE name. To exclude the NE name from a script
file name, you can change the scriptname configuration item in the installation path of the NMS/
server/cbb/trans/core/conf/xml/script/script_enum.xml configuration file.
Main Usage
The main usage of the script files is as follows:
l Realizing the upgrade of the configuration data with zero loss during the U2000 upgrade.
This is an important method for the U2000 upgrade. This is the main usage of the script
files.
l After the network data is modified, restoring the customized information of the U2000,
such as the trail name, fiber name, port name, and the customer information.
l By modifying the script files, realizing the division and combination of the U2000 data and
realizing the import of the desired data only, such as the NE list (with no configuration
data), fiber connection, protection subnet, or trail.
l Supporting the simplified implementation of the project design.
Compatibility
l The scripts exported from the U2000 of an earlier version can be imported to the U2000
of a later version. But an error may occur if the scripts exported from the U2000 of a later
version is imported to the U2000 of a earlier version. The U2000 of an earlier version does
not support the features and functions that are added and the parameters that are modified
in the U2000 of a later version. After the scripts are imported, an error message is displayed.
But this does not affect the import of other information.
l The scripts generated on Windows and on UNIX are compatible.
Application
During the network adjustment, such as adding or deleting a node in the network, if the fiber
connection is deleted, the protection subnet and trail carried on the fiber are deleted from the
network layer of the U2000. After the network adjustment, if the source and sink ports of the
trail are not changed, you can find the trail again by performing the trail search. But the original
customized information of the trail, such as the trail name, customized information of the trail,
and remarks, cannot be restored through the search.
To restore the customized information of the trail, you need:

1. Before the network adjustment, export the network layer information file.
2. After the network adjustment, import the network layer information file.

NOTE
l When the source and sink ports of the trail are not changed after the network adjustment, you can use
the scripts to restore the customized information. Otherwise, you need restore the customized
information manually.
l When the network layer information file is imported after the network adjustment, errors may be
displayed for part of the data, because certain objects, such as NEs, boards, and ports, are changed.
This does not affect the restoration of the customized information.
10.6.2 Immediately Backing Up the U2000 Data by Script

Before upgrading the U2000, you must export the data from the database to script files and save
these files to import the data back to the U2000 after the upgrade.
Prerequisite
l Before you export the script files, you must check the consistency of the configuration data
to ensure that the configuration data in the U2000 is consistent with that in the NE.
For details, see 11.2 Checking Consistency of Configuration Data Between an NE and
the U2000.
Procedure
NOTE
2 Choose Administration > Back Up/Restore NMS Data > Import/Export Script File from
the main menu.
3 Click the Export option button.
4 Click the TXT or XML option button.
5 Select a script file type from the Script File Type field. For details, see 10.6.1 Script Files.
NOTE
l To export the networkwide script file, select Networkwide Configuration File. Export the following
files to a specified directory: NWCfg_NM Name.txt, NWNeList_NM Name.txt, NEPort_Port ID-Basic
ID_NE Name.txt, and NEData_Extended ID-Basic ID_NE Name.txt.
l The following script types are available for the export: Networkwide Configuration File, NE Port
Naming File, NE Configuration File, NE List File, NM Computer Information File, Service
Actualization Script, Network Layer Information File, Network Modeling and Design
Information File, and CEAS.
6 Select the NE for which you want to export script files from the Export NE List.
NOTE
Specify the NE only when you export the NE Configuration File, NE List File, NE Port Naming File,
Networkwide Configuration File and CEAS.
7 Click Create File Directory to create a directory where the exported script files are to be saved.

NOTE
The script file is saved on the U2000 server. On Windows, the backup directory is installation path of the
NMS\server\script. On Solaris and SUSE Linux, the backup directory is installation path of the NMS/
server/script. You can create a new directory under it.
8 Enter the directory name and click OK.
9 Select the created directory and click Apply.

A progress bar appears showing the status of the export.
----End
10.6.3 Backing Up the U2000 Data Through Script Exporting in a

Scheduled Manner
In routine maintenance, you can use the scheduled task function to export network configuration
data as script files in a scheduled manner to ensure timely backup of customized information.
In addition, this function can be performed without any manual intervention and thus reduces
maintenance costs.
Prerequisite
Context
resources.
Procedure
NOTE
4 Select Script Export as the task type and enter a name for the scheduled task. Select Period as
the run type. Then click Next.
5 In Time Setting, set the planed start time of the task.
6 In Period Setting, set the execution interval and execution times of the task. Then, click Next.

7 Select the NEs and the type of the script file to be exported. For details, see 10.6.1 Script
Files. Then click Finish. Then the created scheduled task is displayed in the Task
Management window.
----End
10.6.4 Restoring the U2000 Data by Using the Script

After upgrading the U2000, you can restore the U2000 network layer configuration data from
the backup script files.
Prerequisite
l The NMS subsystem deployment during data restoration must be the same as the that during
data backup.
l You must have the license for the U2000 script import.
Context
CAUTION
Before importing the script file, you need to back up the U2000 database, and then initialize the
U2000 database. Then, import the configuration file. It is recommended that you import the
network-wide configuration file. You can restore the data from a backup file if you failed to
import the script file.
Procedure
NOTE
2 Choose Administration > Back Up/Restore NMS Data > Import/Export Script File from
the main menu.
3 Click the Import option button.
4 Click the TXT or XML option button.
5 Select the script file type from the Script File Type field.
NOTE
Service Actualization Script and NM Computer Information File are not supported.
6 In the Operation Directory List, select the directory where the script file is to be imported is
located.
7 Select the script file to import from the Import File List.

8 In the Import Subnet List, select the sunbets to be imported. All subnets are required to be
selected.
9 Click Apply. The system prompts you twice that the import of the configuration script will result
in data inconsistency between the U2000 and the NE.
10 Click OK. A progress bar appears showing the status of the import.
----End
10.7 Setting Alarm/Event Timing Dump

Context
Procedure
2 In the Task Management window, choose Database Capacity Management in the navigation
tree.
3 In the Task Management window, double-click the Alarm/Event Log Dump task in the task
list.

4 In the Attribute dialog box, modify common and extended parameters.
5 Click OK.
----End
10.8 Setting U2000 Log Timing Dumping

Context
Each of the types Operation Log Dump, Security Log Dump and System Log Dump has a
default system task that is provided by the U2000. You are not allowed to delete this system
task, but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
2 In the Task Type navigation tree, choose Database Capacity Management > Alarm/Event
Log Dump,Database Capacity Management > Operation Log Dump,Database Capacity
Management > Security Log Dump or Database Capacity Management > System Log
Dump.


NOTE
In the task list, right-click the log dump task and choose Run At Once. The log dump task is performed
instantly.
4 In the displayed Attribute dialog box, set the parameters on the Common Parameters and
Extended Parameters tabs. For the parameter descriptions, see Setting Log Dump and Export.
5 Click OK.
----End

This topic describes how to dump performance data. The performance data can be dumped in
two modes, namely, automatic dumping and manual dumping.

This topic describes how to dump performance data manually. This operation enables you to
configure the user-defined conditions to dump the performance data manually.
10.9.2 Dumping Performance Data Automatically
This topic describes how to dump performance data automatically. This operation enables you
to configure the default condition to automatically dump the performance data.

This topic describes how to dump performance data manually. This operation enables you to
configure the user-defined conditions to dump the performance data manually.
Prerequisite
l Performance data for at least one day exists.
l There is sufficient memory to save the dumped performance data.
Procedure
1 Choose Performance > Performance Dump Management > Manual Dump Performance
Data from the Main Menu.
2 In the Path on the server text box, enter the path to save the dumped performance data.
3 In the Specify the end date area, click to select the end date to dump the performance data.

4 In the Specify Granularity area, in the Dump drop-down list, select the dump mode for different
granularities.
Granularities are 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, and 1 day.
Dump can be classified as no dump, dump to file, and delete.
5 Click Dump data to dump the performance data.
The progress bar displays the status of the number of total records and the number of dumped
records.
6 A dialog box is displayed, prompting that the operation succeeds. Click OK.
----End
10.9.2 Dumping Performance Data Automatically

This topic describes how to dump performance data automatically. This operation enables you
to configure the default condition to automatically dump the performance data.
Prerequisite
l Performance data for at least one day exists.
l There is sufficient memory to save the dumped performance data.
Procedure
1 Choose Performance > Performance Dump Management > Automatic Dump Setting from
the Main Menu.
2 In the Path on Server text box, enter the path to save the dumped performance data.
3 In the Granularity-based Lifecycle area, in the Lifecycle(day) text box, enter the number of
days according to the granularity.
Granularities are 10 seconds, 20 seconds, 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour,
and 1 day.

4 Select Dump to File after Lifecycle check box to save the dumped performance data from the
database to a file or from one file to another file in Path on Server path.
NOTE
If you do not select the Dump to file after lifecycle check box, the performance data is deleted without
being saved.
5 In the Proportion dumped(%) text box, enter the percentage of performance data to be dumped
according to the granularity.
Granularities are 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, and 1 day.
NOTE
For dumping the performance data from database to file, Maximum disk space occupied by Data specifies
the percentage of performance data retained in the database.
6 Select Dump to File check box to save the dumped performance data from the database to a file
or from one file to another file mentioned in Path on Server path.
If you do not select the Dump to file check box, the performance data is deleted from the database
without being saved.
7 Click Apply or OK.
----End
Example
l If the number of days in the Lifecycle(day) text box is 2 days for 15 minutes granularity,
the latest 2 days performance data is stored and the remaining data is dumped.

l For performance data dump from database to file, if the performance data for the last 2 days
exceeds the percentage of performance data in Maximum disk space occupied by Data
and if the percentage of performance data in Proportion dumped(%) text box is 10, the
oldest 10 percent performance data is dumped from the database.

Operation Guide for Common Features 11 Keeping Data Consistency Between the U2000 and NEs
11 Keeping Data Consistency Between the

U2000 and NEs
About This Chapter
When you use multiple U2000s to manage NEs, and if a U2000 modifies an NE's configuration
data, the data in the other U2000s becomes inconsistent with the data in the NE. Incorrect
configuration data may lead to misjudgement or misoperation. For proper management of NEs,
the data in the NEs and the data in the U2000 should be consistent.
11.1 Data Management Policy of the U2000

The U2000 provides rich data management functions to ensure the security and consistency of
the configuration data. In different network construction phases, different data management
functions can be adopted.
11.2 Checking Consistency of Configuration Data Between an NE and the U2000
A consistency check is done to compare the configuration data in the NEs with the data in the
U2000. After the check, a report of the result is created. If the result shows the configuration
data is inconsistent, you need to upload the configuration data from the NE to the U2000 or
download the data from the U2000 to the NE for data synchronization.
11.3 Viewing the Asynchronous Information
If the data in the NEs is different from the data in the U2000, you can locate the reason for the
data being out of synchronization by viewing the out-of-synchronization information.
11.4 Synchronizing the NE Configuration Data
11.5 Uploading NE Configuration Data
The NE configuration data in the U2000 may differ from that in the NE. During maintenance,
you need to keep the data in the U2000 consistent with the data in the NE. If the network runs
normally and the data in the NE is correct, upload the data from the NE to the U2000. After
uploading, you need to perform a consistency check.
11.6 Downloading NE Configuration Data
you need to keep the data in the U2000 consistent with the data in the NE. When you want the
NE to operate according to the data in the U2000, for example, during a deployment or loss of

11 Keeping Data Consistency Between the U2000 and NEs Operation Guide for Common Features
NE data, you can download the data to the NE. After the download, you need to perform a data
consistency check.
11.7 Configuration Data Management Information List
The configuration data management information list describes whether each U2000 function
supports upload, download, consistency check or data replication.

11.1 Data Management Policy of the U2000

The U2000 provides rich data management functions to ensure the security and consistency of
the configuration data. In different network construction phases, different data management
functions can be adopted.
Basic Concepts
In the data management of the transmission network, the following basic concepts, which should
be learned first, are involved.
l NE-side data. NE-side data is the NE data. It is saved in the DRDB database on the SCC
board of the NE.
l NM-side data. The NM-side data contains the data at the NE layer and the data at the
network layer. It is saved in the database of the NM.
– NE-layer data at the NM side. It is the data of each NE on the NM. The NE-layer data
at the NM side should be consistent with the NE-side data. To download the NE
configuration data is to issue the NE-layer data at the NM side to the NE. To upload the
NE configuration data is to upload the NE-side data to the NM to update the NE-layer
data at the NM side.
– Network-layer data at the U2000 side. It is the configuration data at the network layer
on the U2000. The network-layer data at the U2000 side contains the information about
fiber connections, protection subnets, and trails.
Data Management Functions

The U2000 provides rich functions to ensure the security and consistency of the configuration
data.
l The basic configuration data management functions include the uploading, downloading,
consistency check, synchronization, duplication, pre-configuration and the initialization of
the NE-layer data at the NM side.
– Uploading: In the case of uploading, the NE-side data is reported to the NM to overwrite
the NE-layer data at the NM side. The data that is present at the NM side but absent at
the NE side is not deleted.
– Downloading: In the case of downloading, the NE-layer data at the NM side is issued
to the NE to overwrite the data at the NE side.
– Consistency check: Check whether the NE-layer data at the NM side is consistent with
the NE-side data. If inconsistent, you need to synchronize or upload the NE
configuration data.
– Synchronization: Upload the inconsistent data (including the collision data, and the data
that is present at the NE side but absent at the NM side) to the NE layer at the NM side.
The data that is present both at the NM side and the NE side is not uploaded, and the
data that is present at the NM side but absent at the NE side is not deleted.
– Duplication: In the case of NEs that are of the same NE type and of the same NE software
version, if the configuration data of an NE to be configured is the same as that of an NE
already configured, you can configure the NE by duplicating the NE data. Duplicating
the NE data only changes the data at the U2000 side and does not affect the NE-side

data. To make the duplicated data take effect on the NE, you need to perform the
downloading operation.
– Pre-configuration: In the case of pre-configuration, the configuration data of an NE is
only saved on the NE layer at the NM side and does not affect the actual configuration
data of the NE. The pre-configuration function is generally used for the large-scale
service adjustment or expansion.
– Initialization of the NE-layer data at the NM side: The NE-layer data at the NM side is
cleared and the NE becomes unconfigured after the initialization.
l To back up and restore the NE data, refer to 12 Backing Up and Restoring the NE
Data.
NOTE
The RTN, PTN,NA WDM and NG WDM product series do not support preconfiguration and the
downloading of configuration data. Then, the U2000 provides a more reliable function, that is, the database
package backup and restoration function, to solve the data restoration problem. This is because:
l In the case of configuration data, the NE data is not complete. The complete data, however, can be
obtained by using the database package restoration function.
l During the downloading of configuration data, the U2000 needs to convert the configuration data to
the Qx interface information. Then, the data can be exchanged between the U2000 and the NE. Thus,
the efficiency is relatively low. In the database package restoration mode, databases are directly
downloaded to the NE, which ensures a high efficiency.
l On the U2000, only one set of configuration data can be saved, but the database package can have
many backup copies. You can select the backup package as needed.
Basic Principles of the Data Management

In different network construction phases and different application scenarios, different data
management functions can be adopted. Basic principles of the data management are as follows:
l Before the configuration changes, you need to upload the NE data to ensure that the data
on the U2000 is consistent with the data on the NE.
l Before the configuration changes, you need to back up the NE database and the U2000
database for the data restoration in case of an operation failure.
l After the configuration changes, you need to back up the NE database and the U2000
database for the data restoration in case of an NE anomaly.
NE Data Management Policy

Figure 11-1 describes the NE data management operation that you need to perform in different
engineering phases and different scenarios.

Figure 11-1 NE Data Management Operation

NE software Service Routine
Configure NE data Troubleshooting
upgrade expansion maintenance
Initial Pre- Upload NE Upload NE Upload NE Restore NE

Duplication data data data data
configuration configuration
Onsite Pre- Create an Upgrade Back up Synchroniz

configuration configuration NE operation NMS data ation
Back up NE Download Duplicate Consistency Expansion Back up NE

data NE data NE data check operation data
Upload NE Consistency Download Back up NE Consistency

data check NE data data check
Consistency Back up NE Consistency Back up NE

check data check data
Back up NE
data
NE Data Configuration
In the case of the initial configuration for a new equipment, neither the U2000 nor the NE has
the configuration data. Thus, engineers need to manually configure the data.
1. Use the U2000 to perform the NE configuration on site.
2. Back up the NE database to the SCC board.
3. In the NM center, create the NE and upload the NE configuration data.
4. Check whether the data on the U2000 is consistent with that on the NE.
If the pre-configuration is already performed on the U2000, download the configuration data to
the NE.
1. Use the pre-configuration function to complete the NE configuration.
2. Cancel the pre-configuration attribute of the NE and download the NE configuration data.
CAUTION
Before downloading the data, verify the data in the lab environment to ensure that the data can
be normally downloaded.
If the configuration data of an NE to be configured is the same as that of an NE already

configured, the two NEs are of the same type and the NE to be configured supports the
downloading function, you can simplify the operation by duplicating the configuration data.
1. Create an NE.
2. Duplicate the NE configuration data.

3. Download the NE configuration data.

NE Software Upgrade
1. Upload the NE configuration data.
2. Perform the upgrade operation.
Service Expansion
1. Upload the NE database.
2. Back up the U2000 database.
3. Perform the expansion operation.
Routine Maintenance
1. In the case of the NE configuration change, such as the service adjustment or rerouting,
back up the NE database immediately after the relevant operation is complete.
2. If the NE data is configured by using different network NMs (such as the U2000), you need
to synchronize the data on the U2000 after the configuration is complete.
3. Perform the monthly (recommended) consistency check for all the NEs. In the case of any
data inconsistency, synchronize or upload the data.
4. Back up the NE database periodically. For the RTN, NG WDM ,NA WDM and the OSN
equipment that is enabled with the ASON features, the database package backup mode
must be adopted for the database backup.
Troubleshooting
When the database files are lost due to the SCC board replacement or NE anomalies, restore the
NE data in time.
U2000 Data Management Policy

Figure 11-2 describes the U2000 data management operation that you need to perform in
different engineering phases and different scenarios.

Figure 11-2 U2000 Data Management Operation
Routine
Construct NMS data NMS software upgrade Troubleshooting
maintenance
Export networkwide Back up NMS Restore NMS

Upload NE data
configuration files data data
Create fibers and NMS software

Dump logs
cables upgrade
Search
Configuration
protection
Upgrade Wizard
subnets
Search trails
U2000 Data Construction
1. Upload the NE configuration data to form the NE-layer data at the NM side.
2. Create fibers and cables.
3. Based on the NE-layer data at the NM side and the fiber connection information, search
the protection subnets to form the protection subnet information in the network-layer data
at the NM side.
4. Based on the NE-layer data at the NM side, the fiber connection information and the
protection subnet information, search the paths to form the path information in the network-
layer data at the NM side.
U2000 Software Upgrade
Before the U2000 software upgrade, you must make sure that the data on the U2000 is consistent
with the that on the NE. The U2000 software upgrade is performed as follows:
1. Export the network-wide configuration files for the data restoration after the software
upgrade.
2. Upgrade the U2000 software.
3. Based on the configuration upgrade wizard, upload the NE configuration data. Import the
network-wide configuration files and search the protection subnets and trails again.
Routine Maintenance
In daily maintenance, back up the U2000 data periodically and clear unnecessary databases to
arrange the database space in time.
1. After the important configuration data changes, backup the U2000 database immediately.
2. Back up the U2000 database periodically in a monthly (recommended) manner.
3. To vacate the database space, perform the log dump periodically.
Troubleshooting

When the U2000 becomes abnormal due to the U2000 fault, computer hardware fault, or other
causes, restore the U2000 data in time.
11.2 Checking Consistency of Configuration Data Between

an NE and the U2000
A consistency check is done to compare the configuration data in the NEs with the data in the
U2000. After the check, a report of the result is created. If the result shows the configuration
data is inconsistent, you need to upload the configuration data from the NE to the U2000 or
download the data from the U2000 to the NE for data synchronization.
Prerequisite
You must be an NM user with "NE and network operator" authority or higher.
Context
l Configuration data consistency check between the U2000 and NEs does not change the
configuration data in the NEs and in the U2000.
l To ensure that the U2000 properly manages the NEs, it is recommended that you run this
function on a monthly basis to keep the consistency of configuration data in NEs and the
U2000 server.
Procedure
The Configuration Data Management window is displayed.
2 Select one or more NEs in the left pane and click the double-right-arrow button (red).
3 Select one NE from the Configuration Data Management List.
4 Click Consistency Check. Alternatively, right-click the NE and select Consistency Check from
the shortcut menu.
5 Click OK when the Confirm dialog box is displayed.
NOTE
Click Save As to save inconsistent information to a file.
----End
Reference Standard
The result indicates a consistency in the configuration data between the NE and the U2000.
Troubleshooting
If the result indicates an inconsistency in the configuration data between the NE and the
U2000, you need to upload or download the data to achieve consistency.

11.3 Viewing the Asynchronous Information

If the data in the NEs is different from the data in the U2000, you can locate the reason for the
data being out of synchronization by viewing the out-of-synchronization information.
Prerequisite
l The NE is in the unsynchronized state.
Context
l If the configuration data is not synchronous between the U2000 and the NE, the NE icon
has a sign.
l If another U2000 client modifies the NE data when the current U2000 client is uploading
or synchronizing data, asynchronous information will be displayed in the NE Config Sync
Info dialog box of the current U2000 client. In this case, the current U2000 client can
perform an upload or synchronization again to eliminate the asynchronous information.
Procedure
The Configuration Data Management window is displayed.
2 In the Object Tree, select one or more NEs, and click . The NEs you select are shown
in the Configuration Data Management List.
3 Select an NE that is in the Unsynchronized state, and then click Sync Info.
4 In the NE Config Sync Info dialog box, click Query to view the details of the configuration
items.
----End
11.4 Synchronizing the NE Configuration Data

Prerequisite
The NE must be in the Unsynchronized state.
Context
l For the MSTP, WDM, NA WDM, RTN, PTN, Marine series NEs, If the data in the
U2000 is inconsistent with the data in the NE, the NE icon has the sign.

l Before synchronizing Layer 2 VLAN data from switches, you must enable the privilege
function and set the privilege level and password when setting Telnet parameters.
Procedure
l Method 1
1. Choose Configuration > Synchronize NE Data from the main menu.

the data.
NOTE
Click the buttons in the Option column and you can select the advance attributes that you wan
to synchronize.
The buttons in the Option column are applicable to the routers, switches, Metro services
platforms, security gateway, service monitoring gateway, and the SVN equipments.
l Method 2
NOTE
1. On the Main Topology, select the NE that is marked with . Right-click and choose
Synchronize NE Data.
2. In the Synchronize NE Data window, click the Synchronize button or right-click
the data.
l Method 3
NOTE
menu.

and choose Synchronize from the shortcut menu.
4. Click OK. The U2000 begins to synchronize the data.
l Method 4
NOTE
Applies to the Router series, Switch series, Security series NEs.

1. Right-click the NE on the Main Topology and choose NE Explorer from the shortcut
menu.
2. In the NE Explorer, after querying the services informations, right-click the result
and select Synchronize.
----End

11.5 Uploading NE Configuration Data

you need to keep the data in the U2000 consistent with the data in the NE. If the network runs
normally and the data in the NE is correct, upload the data from the NE to the U2000. After
uploading, you need to perform a consistency check.
Prerequisite
Procedure
2 Select one or more NEs from the Object Tree and click the double-right-arrow button (red).
3 Select one or more NEs from the Configuration Data Management List.
4 Click Upload. Alternatively, right-click and select Upload from the shortcut menu.
5 Click OK in the confirmation dialog box.
----End
11.6 Downloading NE Configuration Data

you need to keep the data in the U2000 consistent with the data in the NE. When you want the
NE to operate according to the data in the U2000, for example, during a deployment or loss of
NE data, you can download the data to the NE. After the download, you need to perform a data
consistency check.
Prerequisite
CAUTION
Downloading NE configuration data can interrupt the services.

l During a deployment or loss of NE data, you need to create or restore NE data by using the
Downloading NE Configuration Data function. In this way, only the services and core
configuration data on the NE are restored.
l The MSTP, WDM, NA WDM, Marine, PTN, RTN 900 equipment support the downloading
of configuration data, but the NG WDM series equipment does not support the downloading
of configuration data.
l When you download the NE configuration data from the U2000 to the NE, the U2000 first
initializes the NE, and then downloads the configuration data to the NE. If you cancel the
download before it is complete, the configuration data may be incomplete.
Procedure
2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red).
3 Select one or more NEs from the Configuration Data Management List.
4 Click Download. Alternatively, right-click and choose Download from the shortcut menu.
5 Click OK in the two Confirm dialog boxes.
----End
11.7 Configuration Data Management Information List

The configuration data management information list describes whether each U2000 function
supports upload, download, consistency check or data replication.
The configuration data management information list contains the following:
11.7.1 Configuration Data Management Specifications of the General Operations
11.7.2 Configuration Data Management Specifications of the SDH
11.7.3 Configuration Data Management Specifications of the WDM
11.7.4 Configuration Data Management Specifications of the NG WDM
11.7.5 Configuration Data Management Specifications of the NA WDM
11.7.6 Configuration Data Management Specifications of the NG WDMA
11.7.7 Configuration Data Management Specifications of the PTN
11.7.8 Configuration Data Management Specifications of the Ethernet
11.7.9 Configuration Data Management Specifications of the ATM
11.7.10 Configuration Data Management Specifications of the ASON
11.7.11 Configuration Data Management Specifications of the alarm and performance
11.7.1 Configuration Data Management Specifications of the

General Operations

Function Function Upload Download Consistenc Data

Category y Check Replicatio
n
Basic virtual Virtual NE N N N N

NE ID
configuratio
n Virtual NE N N N N
name
Card N N N Y
installed in a
virtual NE
Remarks N N N Y
Card type Card type N N N N

definition for definition
a virtual NE
NE attribute NE name Y Y Y N
NE location N N N N
NE remarks Y Y N Y
SDH Y Y Y Y
timeslot
configuratio
n mode
(Huawei
mode/
Lucent
mode)
Setting the Y N Y Y
NE type and
subrack type
Support for Y N N Y
the time
division
mode
PMU Relay Y Y Y Y
control mode
State of the Y Y Y Y
alert relay
K0
State of the Y Y Y Y
alert relay
K1


n
Second Y Y Y Y
power
supply in use
or not
Temperature Y Y Y Y
upper limit
Temperature Y Y Y Y
lower limit
EMU Serious Y Y Y Y
overvoltage
Common Y Y Y Y
overvoltage
Serious Y Y Y Y
undervoltage
Common Y Y Y Y
undervoltage
Upper limit Y Y Y Y
of the
temperature
value
Lower limit Y Y Y Y
of the
temperature
value
Input Y Y Y Y
channel
name
Output Y Y Y Y
channel
name
Use or not Y Y Y Y
Working Y Y Y Y
mode
Correspondi Y Y Y Y
ng input
Alarm mode Y Y Y Y
CAU N Y N N
interface


n
FAN N N N N
interface
OHP General Y Y Y Y
interface OHP
attribute
Advanced Y Y Y Y
OHP
attribute
Auxiliary Y Y Y Y
OHP
attribute
F1 data port Y Y Y Y
Conference Y Y Y Y
call
Setting the Y Y Y Y
broadcast
data port
COMM Y Y Y Y
Data port & Y Y Y Y

outgoing
loop route
Subnet Y Y Y Y
number
supported by
the optical
interface
Equipment Card N N N N
maintenance temperature
threshold
NE fan N N N N
setting
Saving card N N N N
configuratio
ns
Automatic Y N N N
release of
NEs
NE security Advanced N N N N
ACL


n
Syslog N N N N
11.7.2 Configuration Data Management Specifications of the SDH

n
PDH loopback Y N N N
interface
Tributary Path Y Y Y Y
protection
Path N N N N
impedance
Service load Y Y Y Y
indication
(load/
unload)
Input signal Y Y Y Y
equalization
Output Y Y Y Y
signal
equalization
Pattern (T1 Y Y Y Y
pattern
B8ZS/AMI)
Path service Y Y Y Y
type (E1/T1)
Path phase Y Y Y Y
lock
Tributary Y Y Y Y
timing mode
Service Y Y Y Y
selection
(34M/45M)
Retiming Y Y Y Y
mode


n
External Y Y Y Y
retiming
clock source
SXT Y Y Y Y
working
mode
Retiming Y Y Y Y
working
mode
Path using Y Y Y N
status
CRC4 Y Y Y Y
E1 frame Y Y Y Y
structure
T1 frame Y Y Y Y
structure
Output Y Y Y Y
tunable
wavelength
J2 byte to be Y Y Y Y
transmitted
received
J2 byte N N N N
received
Path name N N N N
Port protocol Y Y Y Y
mode of
tributary
path
SDH Laser switch N N N N

interface
Optical Y N N N
interface
loopback
VC4 Y N N N
loopback


n
VC4 N N N N
overhead
termination
AIS insertion N N N N
due to B3
byte
threshold-
crossing
SPQ4 port Y Y Y Y
working
mode
FEC Y Y Y Y
working
status
Having the N N N N
SDH
interface
card or not
Laser-in- N N N N
position
status
Setting N N Y N
automatic
laser
shutdown
(ALS)
ALS time N N Y N
parameter
VC3 Y N N N
loopback
VC12 Y N N N
loopback
REG Y Y Y Y
enabling for
the optical
port of the
line card
Overhead Y Y Y Y
mode of the
optical port


n
DCC/GCC Y Y Y Y
mode
Enabling the Y Y Y Y
source of
tandem
connection
sink of
tandem
connection
APId value Y Y Y Y
to be
transmitted
at source
APId value Y Y Y Y
to be
received at
sink
APId byte Y Y Y Y
mode at
source
APId value N N N N
received at
sink
APId byte Y Y Y Y
mode at sink
Laser switch N N N N
transmission
distance
Scheduled N N N N
release of
port
loopback
Output N N N N
wavelength
of the SDH
optical port
Input N N N N
wavelength
of the SDH
optical port


n
Shared Y Y Y Y
attributes of
the multiplex
section
transmission
distance
Number of N N N N
outputs of
the alarm
relay
Regenerator J0 byte to be Y Y Y Y
section transmitted
overhead
received
J0 byte N N N N
received
Higher order J1 byte to be Y Y Y Y

path transmitted
overhead (VC4 path)
received
(VC4 path)
J1 byte N N N N
received
(VC4 path)
C2 byte to be Y Y Y Y
received
(VC4 path)
transmitted
(VC4 path)
C2 byte N N N N
received
(VC4 path)
transmitted
(VC3 path)


n
received
(VC3 path)
J1 byte N N N N
received
(VC3 path)
received
(VC3 path)
transmitted
(VC3 path)
C2 byte N N N N
received
(VC3 path)
received
(PDH card)
transmitted
(PDH card)
Lower order J2 byte to be Y Y Y Y

path transmitted
overhead (VC12 path)
received
(VC12 path)
J2 byte N N N N
received
(VC12 path)
V5 byte to be N N N N
transmitted
(VC12 path)
V5 byte to be N N N N
received
(VC12 path)
V5 byte N N N N
received
(VC12 path)


n
V5 byte to be Y Y Y Y
transmitted
(VC12 path;
EFGS)
V5 byte to be Y Y Y Y
received
(VC12 path;
EFGS)
V5 byte N N N N
received
(VC12 path;
EFGS)
SDH clock Synchroniza N N N N

interface tion status
Clock source Y Y Y Y
priority
failure
condition
Phase- Y Y Y Y
locked
source
output by
external
clock
Clock source N N N N
switching
Clock subnet Y Y Y Y
TDA clock Y Y Y Y
source
configuratio
n
restoration
parameter
SSM output Y Y Y Y
control
quality


n
Clock ID Y Y Y Y
status
Manually Y Y Y Y
setting the
level-0 clock
quality
Customized Y Y Y Y
clock quality
2M phase- Y Y Y Y
locked
source
priority list
Clock Y Y Y Y
binding
Test function Automatic N N N N

laser
shutdown
2M PRBS N N N N
test
Frame N N N N
overhead
information
management
PRBS test N N N N
SDH service SDH Y Y Y Y

common
cross-
connect
SNC Y Y Y Y
protection
group
SNC Y Y Y Y
protection
group card
mapping
Multi-trail Y Y Y Y
protection
group


n
SDH service SDH N N N N

of a virtual common
NE cross-
connect
SNC N N N N
protection
group
SNC N N N N
protection
group card
mapping
Multi-trail N N N N
protection
group
SNC service Hold-off Y Y Y Y

attribute time
Switching Y Y Y Y
WTR time
Revertive Y Y Y Y
mode
Monitoring Y Y Y Y
condition
Service Y Y Y Y
group
Service type Y Y Y Y
Current N N N N
status
Overhead Overhead Y Y Y Y
service service
SNC service Hold-off N N N N

attribute of a time
virtual NE
Switching N N N N
WTR time
Revertive N N N N
mode
Monitoring N N N N
condition


n
Service N N N N
group
Service type N N N N
Current N N N N
status
Multi-trail Hold-off Y Y N Y
service time
attribute
Switching Y Y N Y
WTR time
Revertive Y Y N Y
mode
Monitoring Y Y N Y
condition
Logical Logical Y Y Y Y
system system ID
Name Y Y Y Y
Type Y Y Y Y
STM level Y Y Y Y
Topology Y Y Y Y
type
Fiber/Cable Y Y Y Y
number
Service Y Y Y Y
direction
Node type Y Y Y Y
Protection Y Y Y Y
type
Slot mapping Y Y Y Y
Multiplex MS Y Y Y Y
section protection
group
protocol type
MS local Y Y Y Y
node ID


n
MS Y Y Y Y
westbound
node ID
MS Y Y Y Y
eastbound
node ID
MS Y Y Y Y
maximum
node ID
MS Y Y Y Y
switching
revertive
time
MS SD Y Y Y Y
enabling flag
MS Y Y Y Y
suppression
enabling flag
Configuratio N Y N N
n of MS
suppression
on all spans
Logical Logical N N N Y
system of a system ID
virtual NE
Name N N N Y
Type N N N Y
STM level N N N Y
Topology N N N Y
type
Fiber/Cable N N N Y
number
Service N N N Y
direction
Node type N N N Y
Protection N N N Y
type
Slot mapping N N N Y


n
MS N N N Y
protection
group
protocol type
MS local N N N Y
node ID
MS N N N Y
westbound
node ID
MS N N N Y
eastbound
node ID
MS N N N Y
switching
revertive
time
MS SD N N N Y
enabling flag
Logical Logical Y Y Y Y
system system
relation relation
(protection
group) ID
Protection Y Y Y Y
type
Revertive Y Y Y Y
mode
Switching Y Y Y Y
mode
MS Y Y Y Y
switching
revertive
time
MS SD Y Y Y Y
enabling flag
Equipment 1 Protection Y Y Y Y
+1 protection group ID
Active card Y Y Y Y


n
Standby card Y Y Y Y
Service level Y Y Y Y
Protection Y Y Y Y
type
TPS Protection Y Y Y Y
protection group ID
Enabled or Y Y Y Y
not
Revertive Y Y Y Y
time
Protection Y Y Y Y
unit ID
Protection Y Y Y Y
unit slot
Protection Y Y Y Y
unit priority
Switching/ N N N N
Lock status
64 kbit/s 64 kbit/s Y Y Y Y
service service
Equipment TDA feeding Y Y Y Y

maintenance choice
Basic Dynamic Y Y Y Y
configuratio port
n
Wavelength SF64 N N N N
adjustment wavelength
adjustment
PP service Switchover Y Y Y Y
protection
MCPPS MCPPS Y Y Y Y
protection protection
Port Protection Y Y Y Y
protection group ID
WTR time Y Y Y Y
and revertive
mode


n
Hold-off Y Y Y Y
time
Protection Y Y Y Y
unit and
working unit
Switching/ N N N N
Lock status
NE time NE Y Y N N
localization
management Time zone Y Y N N
Daylight Y Y N N
saving time
Daylight Y Y N N
saving time
rule
Daylight Y Y N N
saving time
offset
Start time Y Y N N
End time Y Y N N
IF interface IF port Y Y Y Y
working
mode
IF port Y N N N
loopback
Single-port Enabling the Y Y Y Y

multiple single-port
multiplex multiple
section multiplex
section
SNCTP Group ID Y Y Y Y
group
information
about the
working
channel


n
information
about the
protection
channel
WTR time of Y Y Y Y
a protection
group
Revertive Y Y Y Y
mode of a
protection
group
Trigger Y Y Y Y
condition
and hold-off
time of the
working
channel
Trigger Y Y Y Y
condition
and hold-off
time of the
protection
channel
High- 1588 packet Y Y Y Y

precision configuratio
time n
transmission
High- Y Y Y Y
precision
clock
priority list
Cock port Y Y Y Y
configuratio
n
Configuratio Y Y Y Y
n of the
external
clock port
Multiplex Check the Y Y Y Y

section standby
channel


n
Card 1+1 Optimizatio Y Y Y Y

protection n of higher
order pass-
through
IF 1+1 Protection Y Y Y Y
protection group ID
group
Working Y Y Y Y
mode
Revertive Y Y Y Y
mode
WTR time Y Y Y Y
Enabling Y Y Y Y
reverse
switching
Switching N N N N
status on the
equipment
side
Switching N N N N
state on the
channel side
IF N+1 Protection Y Y Y Y
protection group ID
group
Working Y Y Y Y
mode
Revertive Y Y Y Y
mode
WTR time Y Y Y Y
Enabling Y Y Y Y
reverse
switching
Switching N N N N
status on the
equipment
side
Switching N N N N
state on the
channel side


n
MSTP+ Ethernet Y N Y Y
packet service: E-
feature LAN/E-
LINE/E-
AGGR
V-UNI Y N Y Y
group
Service QoS Y N Y Y
Ethernet Y N Y Y
OAM
Port Y N Y Y
management
: basic port
Port Y N Y Y
management
: link
aggregation
group
Port OAM Y N Y Y
Static tunnel Y N Y Y
Basic MPLS Y N Y Y
configuratio
n
Tunnel Y N Y Y
OAM
Tunnel Y N Y Y
protection
group
PW Y N Y Y
management
QinQ link Y N Y Y
MCSP Y N Y Y
MC-LAG Y N Y Y
MS_PW Y N Y Y
VLAN_VP Y N Y Y
ORT
BFD Y N Y Y


n
VRRP Y N Y Y
L3VPN Y N Y Y
DHCP_REA Y N Y Y
LY
L2VPN Y N Y Y
Tunnel Y N Y Y
TUNNEL_A Y N Y Y
PS
ARP Y N Y Y
CES Y N Y Y
Overhead Y N Y Y
11.7.3 Configuration Data Management Specifications of the WDM

n
Card Auto- Y Y Y Y
parameter negotiation
of the LDG
card
Monitor Y Y Y Y
wavelength
Searching Y Y Y Y
interval of
the
wavelength
monitor card
Monitoring Y N N N
channel
wavelength
of the
channel
monitor card
Card clock N N N N
mode


n
Card Y N N N
receiving/
transmitting
attribute
Card cross- Y N N N
connection
loopback
Gain of the Y N N N
optical
booster
amplifier
card
Return of the N N N N
SCC card
clock
Card tracing Y Y Y Y
clock source
Status of the Y N N N
MCA card
optical
switch
Laser status Y N N N
Optical Y Y Y Y
interface for
orderwire
Optical Y Y Y Y
interface
attenuation
rate
Input power N N N N
Output N N N N
power
Maximum Y N N N
attenuation
rate
Minimum Y N N N
attenuation
rate


n
WBA output Y N N N
power
Path using Y Y Y N
status
LDG card Y N N N
loopback
Synthesized N N N N
input optical
power loss of
threshold
Synthesized N N N N
output
optical
power loss of
threshold
Maximum Y Y Y Y
packet length
of the
Ethernet
access card
OTU Y Y Y Y
working
wavelength
OTU Y Y Y Y
planning
wavelength
OADM add/ Y N N N
drop
wavelength
OUT band Y Y Y Y
type
OADM band Y Y Y Y
type
OUT Y Y Y Y
planned band
Working Y N N N
waveband of
the optical
layer card


n
Working Y N N N
waveband
parity of the
optical layer
card
Automatic Y N N N
laser
shutdown
RPC natural Y Y Y Y
band
Current Y Y Y Y
working
waveband
Whether Y N N N
VOA is
available in
the card
Flow control Y Y Y Y
enabling
Switching N N N N
status of the
OCP optical
interface
Whether Y Y Y Y
FEC is
allowed
Optical Y Y Y Y
interface rate
at the client
Maximum Y N N N
optical
interface rate
at the client
Minimum Y N N N
optical
interface rate
at the client


n
Frequency Y Y Y Y
band of the
optical
interface rate
Card clock Y Y Y Y
source
configuratio
n (OCU,
LQS, LGS,
and SMC)
Enabling Y Y Y Y
wavelength
identificatio
n
Received Y N N N
wavelength
identificatio
n
Identificatio Y Y Y Y
n for
wavelength
to be
received
Insertion loss Y N N N
(you can
only query
the real-time
status)
Nominal Y Y N Y
gain
Optical port Y Y Y Y
remarks
Service Y Y Y Y
working
mode
Client-side Y Y Y Y
service
protocol
Card Y Y Y Y
working
mode


n
to be
transmitted
Service type Y N N N
received
LOS alarm N N N N
threshold
LOG Y Y Y Y
working
mode
Setting the Y Y Y Y
ESC
auxiliary
switch
Minimum Y N N N
fixed pump
optical
power
Maximum Y N N N
fixed pump
optical
power
Fixed pump Y Y Y Y
optical
power
Single path Y Y Y Y
attenuation
rate
adjustment
Path Y N N N
attenuation
rate
Wavelength Y N N N
ID received
Wavelength Y Y Y Y
ID to be
received
Service rate Y Y Y Y


n
Guaranteed Y Y Y Y
bandwidth
for the client
GE service
LPT Y Y Y Y
enabling
Add/drop Y N N N
band number
Return of the Y Y Y Y
SCC card
clock
Single-Fed Y N N N
single-
receiving
and dual-Fed
dual-
receiving
attributes of
LWM and
LWX cards
Working Y N N N
band query
for a card
Card Y N N N
working
frequency
Optical port Y N N N
loopback
STAT byte Y Y Y Y
to be
transmitted
at the ODU
layer
PT byte to be Y Y Y Y
transmitted
at the ODU
layer


n
IAE byte to N N N N
be
transmitted
at the OTU
layer
TTI Y Y Y Y
identifier at
the OTU
layer
Current Y N N N
bearer rate
Monitoring Y N N N
wavelength
band type
Input optical N N N N
power
Reference N N N N
value of the
input optical
power
Reference N N N N
time of the
input optical
power
Input status N N N N
Output N N N N
optical
power
Reference N N N N
value of the
output
optical
power
Reference N N N N
time of the
output
optical
power
Output status N N N N


n
Input lower Y Y Y Y
threshold
Input upper Y Y Y Y
threshold
Maximum Y N N N
output
optical
power of the
pump
Minimum Y N N N
output
optical
power of the
pump
wavelength
flag
Upper N N N N
threshold of
the tunable
wavelength
Lower N N N N
threshold of
the tunable
wavelength
Guaranteed Y Y Y Y
bandwidth
for the client
GE service
Whether the N N N N
wavelength
type is
adjustable
Whether the Y N N N
extended
wavelength
is supported
Setting the Y Y Y Y
ESC
auxiliary
switch


n
Planned Y Y Y Y
wavelength
type
ODU1 Y N N N
channel
loopback
ODU2 Y N N N
channel
loopback
ODU3 Y N N N
channel
loopback
FEC mode Y Y Y Y
FE Y Y Y Y
transparent
transmission
Enabling an Y Y Y Y
Ethernet port
Working Y Y Y Y
mode of an
Ethernet port
OTN service Y N N N
type
MCA coding N N N N
mode
Inclination N N N N
of the optical
amplifier
card
FC distance N N N N
expansion
Output lock Y Y Y Y
mode
Forced Y Y Y Y
transmitted
power
received


n
received
(WDM)
J0 byte Y N N N
received
J0 byte Y N N N
received
(WDM)
transmitted
transmitted
(WDM)
PRBS test on Y N Y N
an auxiliary
card
TTI Y Y Y Y
identifier to
be
transmitted
at the OTS
layer
TTI Y Y Y Y
identifier to
be received
at the OTS
layer
TTI N N N N
identifier
received at
the OTS
layer
TIM Y Y Y Y
detection
mode
monitored at
the optical
layer
Port service Y Y Y Y
mapping
path


n
In-service Y N N N
status of the
optical
amplifier of
the pump
Status of the Y N N N
optical
amplifier of
the pump
FC internal Y Y Y N
operation
mode
Power offset Y Y Y N
of the
working and
protection
channels
Overhead in PT byte to be Y Y Y Y
OPU transmitted
at the OPU
layer
PT byte N N N N
received at
the OPU
layer
OTU layer TTI to be Y Y Y Y

transmitted
at the OTU
layer
TTI to be Y Y Y Y
received at
the OTU
layer
TTI received N N N N
at the OTU
layer
IAE byte to N N N N
be received
at the OTU
layer


n
IAE byte N N N N
received at
the OTU
layer
BEI at the N N N N
OTU layer
BDI at the N N N N
OTU layer
Overhead in TTI Y Y Y Y
ODU identifier to
be
transmitted
at the ODU
layer
TTI Y Y Y Y
identifier to
be received
at the ODU
layer
TTI N N N N
identifier
received at
the ODU
layer
STAT byte Y Y Y Y
to be
transmitted
at the ODU
layer
STAT byte N N N N
received in
the ODU
layer
BEI at the N N N N
ODU layer
BDI at the N N N N
ODU layer
at the ODU
layer


n
CLK N N N N
insertion at
the ODU
layer
OCI N N N N
insertion at
the ODU
layer
SDH 1-byte J0 to Y Y Y Y
overhead be
transmitted
1-byte J0 to Y Y Y Y
be received
1-byte J0 N N N N
received
64-byte J0 to Y Y Y Y
be received
64-byte J0 N N N N
received
Card clock Revertive Y Y Y Y

mode
WTR Y Y Y Y
S1 byte
protocol
attribute
Lock status Y Y Y Y
Input mode Y Y Y Y
of the
external
source
External Y Y Y Y
source S1
timeslot
Configuratio Y Y Y Y
n of the S1
byte


n
ID
WTR status N N N N
Card clock N N N N
source
holdover
mode
Clock N N N N
transparent
transmission
configuratio
n
Clock N N N N
transparent
transmission
protection
group
Setting the Y Y Y Y
clock mode
Optical line Revertive Y Y Y Y

protection mode
Revertive Y Y Y Y
time
Working N N N N
channel
Switching N N N N
status
Channel Y Y Y Y
hold-off time
Optical Revertive Y Y Y Y
channel flag
protection
Revertive Y Y Y Y
time
Switching N N N N
status
Channel Y Y Y Y
hold-off time


n
1:N optical Protection Y Y Y Y

channel type
protection
Revertive Y Y Y Y
mode
WTR time Y Y Y Y
Remaining N N N N
WTR time
SD Y Y Y Y
switching
enabling flag
Parameter Y N N N
consistency
check flag
Protection Y Y Y Y
priority
IPA (APR) Protection Y Y Y N

protection group ID
pair
Band Y Y Y N
Detection Y Y Y N
card
Control Y Y Y N
implementat
ion card
Raman Y Y Y N
amplifier
Auxiliary Y Y Y N
Raman card
Remote Y Y Y N
optical pump
card
IPA status Y Y Y N
Restart mode Y Y Y N
Off period Y Y Y N
On period Y Y Y N
Testing Y Y Y N
period


n
Start latency Y Y N N
Security Y Y Y N
control
switch
Detection Y Y Y Y
card
threshold
Raman Y Y Y Y
amplifier
threshold
Raman
amplifier
alarm
IPA Y Y Y Y
auxiliary
detect
interface
Pulse restart Y Y Y Y
switch
APE Subrack N N N N
(NE) ID of
the power
monitoring
unit
Power Y Y Y N
monitoring
unit
Power Y Y Y N
regulating
subrack of
the odd
wavelength
Power Y Y Y N
regulating
subrack of
the even
wavelength


n
Monitoring Y Y Y N
subrack of
the transmit
end
Monitoring Y Y Y N
subrack of
the receive
end
Power Y Y N N
unbalance
threshold
Wavelength Y Y N N
enabling flag
Standard Y Y Y N
power offset
Actual N N N N
power offset
Standard N N N N
power offset
reference
320G ALC Link ID Y Y Y N
Node type Y Y Y N
Node ID Y Y Y N
Power Y Y Y N
detection
unit
Variable Y Y Y N
optical
attenuation
unit
Upstream Y Y Y N
supervisory
channel
Downstream Y Y Y N
supervisory
channel
Node ID of Y Y Y N
the reference
unit


n
Working Y Y Y N
mode
Reference Y Y Y N
unit
Abnormal Y Y Y N
power
detection
threshold
Single- Y Y Y N
wavelength
ASE noise
compensatio
n
Overall Y Y Y N
optical
power offset
compensatio
n
Automatic Y Y Y N
adjustment
switch
1600G ALC Link ID Y Y Y N
Node ID Y Y Y N
Direction Y Y Y N
Band type Y Y Y N
Number of Y Y Y N
nodes
Monitored N N N N
NE
Working Y Y Y N
mode
Power Y Y Y N
detection
unit
Variable Y Y Y N
optical
attenuation
unit


n
Node ID of Y Y Y N
the reference
unit
Reference Y Y Y N
unit
Abnormal Y Y Y N
power
detection
threshold
Standard Y Y Y N
output power
of a single
wavelength
Standard Y Y Y N
power offset
value
Single- Y Y Y N
wavelength
ASE noise
compensatio
n
Overall Y Y Y N
optical
power offset
compensatio
n
Gain Y Y Y N
detection
input unit of
the power
reference
node
Standard Y Y Y N
gain of the
power
reference
node
Automatic Y Y Y N
adjustment
switch


n
Westbound Y Y Y N
supervisory
channel
Eastbound Y Y Y N
supervisory
channel
Test function Laser N N N N

spectrum
analysis
Automatic N N N N
WDM power
shutdown
PRBS test N N N N
Wavelength Group ID Y Y Y Y
protection
group Protection Y Y Y Y
type
Revertive Y Y Y Y
mode
Revertive Y Y Y Y
time
Remaining N N N N
revertive
time
Switching Y Y Y Y
mode
Switching Y Y Y Y
time
Active path Y Y Y Y
SD enabling Y Y Y Y
Card Y Y Y Y
mapping
SD event N N N N
Channel Y Y Y Y
hold-off time


n
WDM WDM Y Y Y Y
service common
configuratio cross-
n connection
WXCP Y Y Y Y
protection
group
Card Y Y Y Y
mapping of
the WXCP
protection
group
Card service Y Y Y Y
timeslot
configuratio
n
WXCP Revertive Y Y Y Y
service mode
attribute
WTR time Y Y Y Y
SD enabling Y Y Y Y
flag
SD trigger Y Y Y Y
condition
Current N N N N
status
Trail status N N N N
Current N N N N
working path
OWSP Wavelength Y Y Y Y
protection
group and
WTR


n
Wavelength Y N Y N
protection
group status
(current
working
channel,
switching
status, active
channel
status, and
standby
channel
status)
ROADM Logical Y Y Y N
wavelength
group
Wavelength Y Y Y N
blocking
monitor unit
Optical Y Y Y N
power
equalization
monitor unit
OTU Y Y Y N
mapping
OTU Y Y Y N
dependent
optical
attenuator
unit
Wavelength Y Y Y N
pass-
through/
blocking flag
Optical Y Y Y N
power
equalization
enabling flag
Optical Y Y Y N
power
equalization
monitor
threshold


n
Standard Y Y Y N
optical
power offset
Actual N N N N
optical
power offset
TPS/DPPS Card Y Y Y Y
mapping of
the DPPS
protection
group
Revertive Y Y Y Y
mode of the
DPPS
protection
group
DPPS Y Y Y Y
protection
WTR time
Card Y Y Y Y
mapping of
the TPS
protection
group
Revertive Y Y Y Y
mode of the
TPS
protection
group
TPS Y Y Y Y
protection
WTR time
Channel Y Y Y Y
hold-off time
Optical Slot of the Y Y Y Y

cross- edge port
connection
management Optical port Y Y Y Y
station by of the edge
station port


n
In/Out Y Y Y Y
attribute of
the edge port
Edge port Y Y Y Y
flag
Optical Y Y Y Y
cross-
connection
ID, parent ID
Source/Sink Y Y Y Y
slot of
optical cross-
connection
Source/Sink Y Y Y Y
wavelength
of optical
cross-
connection
Source/Sink Y Y Y Y
waveband of
optical cross-
connection
Optical Y Y Y Y
cross-
connection
type
OCCE Logical Y Y Y N
wavelength
group
Power Y Y Y N
equalization
monitoring
unit
OTU Y Y Y N
mapping
Optical Y Y Y N
attenuation
unit related
to OTU


n
Wavelength Y Y Y N
pass-
through/
blocking flag
Power Y Y Y N
equalization
enabling
Power Y Y Y N
equalization
detection
threshold
Standard Y Y Y N
power offset
Actual N N N N
power offset
Wavelength Wavelength Y Y Y N
lockout monitoring
unit
Wavelength Y Y Y N
monitoring
object
Wavelength Y N N N
Adding a N N N N
mapping
Deleting a N N N N
mapping
Calculating N N N N
the OTU
Application N N N N
Querying Y Y Y N
mappings
from the NE
Querying N N N N
mappings
from the
U2000
Dispersion Compensati N N N N
compensatio on value
n


n
Fine-tune Y Y Y Y
mode
OTU Y Y Y Y
Optimum N N N N
value
scanning
E1 cross- E1 cross- Y Y Y Y
connection connection
Master and Subrack ID Y N Y Y

slave
subrack Subrack Y N Y Y
management name
DPS Y Y Y Y
protection
group
TCM Object N N N N
overhead
Layer N N N N
Source mode Y Y Y Y
Sink mode Y Y Y Y
Source Y Y Y Y
enabling
Sink Y Y Y Y
enabling
TTI to be Y Y Y Y
transmitted
TTI to be Y Y Y Y
received
DEG Y Y Y Y
threshold
DEG Y Y Y Y
monitoring
time
BIP8 bit Y Y Y Y
error
detection
mode


n
TIM follow-
up response
BIP8 bit Y Y Y Y
error
threshold for
threshold
crossing
BIP8 bit Y Y Y Y
error degrade
threshold
TIM Y Y Y Y
detection
mode
LCK Y Y Y Y
insertion
1+N optical Protection Y Y Y Y

channel type
protection
Revertive Y Y Y Y
mode
WTR time Y Y Y Y
Remaining N N N N
WTR time
Hold-off Y Y Y Y
time
Switching Y Y Y Y
status
SD Y Y Y Y
switching
enabling flag
Status of Y N N N
parameter
consistency
check
Status of Y Y Y Y
redundant
service
access


n
Enabling Y N N N
status of the
protection
group
protocol
Protection Y Y Y Y
priority
OMP Enabling N N N N
status of
WSS
protection
11.7.4 Configuration Data Management Specifications of the NG

WDM

n
Card Auto- N N N N
parameter negotiation
of the LDG
card
Monitor Y N N N
wavelength
Searching N N N N
interval of
the
wavelength
monitor card
Monitoring N N N N
channel
wavelength
of the
channel
monitor card
Card clock N N N N
mode


n
Card N N N N
receiving/
transmitting
attribute
Card cross- N N N N
connection
loopback
Gain of the N N N N
optical
booster
amplifier
card
Return of the N N N N
SCC card
clock
Card tracing N N N N
clock source
Status of the N N N N
MCA card
optical
switch
Laser status Y N N Y
Optical N N N N
interface for
orderwire
Optical N N N N
interface
attenuation
rate
Input power N N N N
Output N N N N
power
Maximum N N N N
attenuation
rate
Minimum N N N N
attenuation
rate


n
WBA output N N N N
power
Path using N N N N
status
LDG card N N N N
loopback
Input optical N N N N
power
Reference N N N N
value of the
input optical
power
Reference N N N N
time of the
input optical
power
Input status N N N N
Output N N N N
optical
power
Reference N N N N
value of the
output
optical
power
Reference N N N N
time of the
output
optical
power
Output status N N N N
Lower Y N Y Y
threshold of
the input
optical
power


n
Upper Y N Y Y
threshold of
the input
optical
power
Maximum Y N N N
pump output
optical
power
Minimum Y N N N
pump output
optical
power
Synthesized N N N N
input optical
power loss of
threshold
Synthesized N N N N
output
optical
power loss of
threshold
Maximum N N N N
packet length
of the
Ethernet
access card
Automatic N N N N
laser
shutdown
OTU Y N Y Y
working
wavelength
OADM add/ Y N N N
drop
wavelength
OTU/ Y N Y Y
OADM
waveband
type


n
Working Y N N N
waveband of
the optical
layer card
Working Y N N N
waveband
parity of the
optical layer
card
Whether N N N N
VOA is
available in
the card
Flow control N N N N
enabling
Switching N N N N
status of the
OCP optical
interface
Whether N N N N
FEC is
allowed
Optical N N N N
interface rate
at the client
Maximum N N N N
optical
interface rate
at the client
Minimum N N N N
optical
interface rate
at the client
Frequency N N N N
band of the
optical
interface rate


n
Card clock N N N N
source
configuratio
n (OCU,
LQS, LGS,
and SMC)
Wavelength N N N N
ID
Insertion loss N N N N
(You can
only query
the real-time
status)
Nominal N N N N
gain
Optical port N N N N
remarks
Service N N N N
working
mode
Client-side N N N N
service
protocol
Card N N N N
working
mode
to be
transmitted
received
LOS alarm N N N N
threshold
LOG N N N N
working
mode
Setting the N N N N
ESC
auxiliary
switch


n
Minimum N N N N
fixed pump
optical
power
Maximum N N N N
fixed pump
optical
power
Fixed pump N N N N
optical
power
Single path N N N N
attenuation
rate
adjustment
Path N N N N
attenuation
rate
WDM ID N N N N
received
WDM ID to N N N N
be received
Service rate N N N N
Port Y N N N
loopback
ODU1 Y N N N
channel
loopback
ODU2 Y N N N
channel
loopback
ODU3 Y N N N
channel
loopback
OTN service Y N Y Y
type
Laser status Y N N Y


n
Guaranteed N N N N
bandwidth
for client GE
service
LPT Y N Y Y
enabling flag
Overhead in PT byte to be N N N N
OPU received at
the OPU
layer
PT byte N N N N
received at
the OPU
layer
OTU layer TTI to be N N N N

transmitted
at the OTU
layer
TTI to be N N N N
received at
the OTU
layer
at the OTU
layer
IAE byte to N N N N
be received
at the OTU
layer
IAE byte N N N N
received at
the OTU
layer
BEI at the N N N N
OTU layer
BDI at the N N N N
OTU layer


n
Overhead in TTI N N N N
ODU identifier to
be
transmitted
at the ODU
layer
TTI N N N N
identifier to
be received
at the ODU
layer
TTI N N N N
identifier
received at
the ODU
layer
STAT byte N N N N
to be
received at
the ODU
layer
STAT byte N N N N
received at
the ODU
layer
BEI at the N N N N
ODU layer
BDI at the N N N N
ODU layer
at the ODU
layer
CLK N N N N
insertion at
the ODU
layer
OCI N N N N
insertion at
the ODU
layer


n
SDH 1-byte J0 to N N N N
overhead be
transmitted
1-byte J0 to N N N N
be received
1-byte J0 N N N N
received
64-byte J0 to N N N N
be received
64-byte J0 N N N N
received
Card clock Revertive N N N N

mode
WTR N N N N
Enabling the N N N N
S1 byte
protocol
attributes
Lock status N N N N
Input mode N N N N
of the
external
source
External N N N N
source S1
timeslot
Manual N N N N
configuratio
n of S1 byte
ID
WTR status N N N N
Card clock N N N N
source
holdover
mode


n
Clock N N N N
transparent
transmission
configuratio
n
Clock N N N N
transparent
transmission
protection
group
IPA (APR) Detection Y N Y N

protection card
pair
Shut off card Y N Y N
Raman Y N Y N
amplifier
Enabling Y N Y N
flag
Restart mode Y N Y N
Off period Y N Y N
On period Y N Y N
Testing Y N Y N
period
Start latency Y N N N
Security Y N Y N
control
switch
Restart pulse Y N Y N
switch
IPA Y N Y N
auxiliary
detection
interface
APE Automatic
power
equilibrium


n
Subrack Y N Y N
(NE) ID of
the power
monitoring
unit
Power Y N Y N
monitoring
unit
Power Y N Y N
regulating
subrack of
the odd
wavelength
Power Y N Y N
regulating
subrack of
the even
wavelength
Monitoring Y N Y N
subrack at
the transmit
end
Monitoring Y N Y N
subrack at
the receive
end
Power Y N N N
unequalizati
on threshold
Wavelength Y N N N
enabling flag
Standard Y N Y N
power offset
Actual N N N N
power offset
Standard N N N N
power offset
reference
NGWDM Link ID Y N Y N
ALC
Subrack ID Y N N N


n
Power Y N Y N
detection
unit
Variable Y N Y N
attenuation
unit
Adjacent Y N Y N
node in the
upstream
direction
Adjacent Y N Y N
node in the
downstream
direction
Reference Y N Y N
unit
Line Y N Y N
attenuation
exception
detection
threshold
Node gain Y N Y N
compensatio
n offset
Automatic Y N Y N
adjustment
switch
Test function Laser N N N N

spectrum
analysis
Automatic N N N N
WDM power
shutdown
Port Group ID Y N Y Y
protection
group Protection Y N Y Y
type
Slot mapping Y N Y Y
Revertive Y N Y Y
mode


n
WTR time Y N Y Y
SD enabling Y N Y Y
Working Y N Y Y
channel
hold-off time
Protection Y N Y Y
channel
hold-off time
Detection Y N Y Y
channel
hold-off time
Optical Slot of the Y N Y Y

cross- edge port
connection
management Optical port Y N Y Y
station by of the edge
station port
In/Out Y N Y Y
attribute of
the edge port
Edge port Y N Y Y
flag
Optical Y N Y Y
cross-
connection
ID, parent ID
Source/Sink Y N Y Y
slot of
optical cross-
connection
Source/Sink Y N Y Y
wavelength
of optical
cross-
connection
Source/Sink Y N Y Y
waveband of
optical cross-
connection


n
Optical Y N Y Y
cross-
connection
type
OCCE Logical N N N N
wavelength
group
Power N N N N
equalization
monitoring
unit
OTU N N N N
mapping
Optical N N N N
attenuation
unit related
to the OTU
Wavelength N N N N
pass-
through/
blocking flag
Power N N N N
equalization
enabling
Power N N N N
equalization
detection
threshold
Standard N N N N
power offset
Actual N N N N
power offset
Electrical Cross- Y N Y Y
cross- connection
connection level
management
Service type Y N Y Y
Direction Y N Y Y
Source Y N Y Y
channel


n
Sink channel Y N Y Y
Activation Y N Y Y
status
SNCP Service Y N Y Y
management source
Service sink Y N Y Y
Protection Y N Y Y
type
Level Y N Y Y
Revertive Y N Y Y
mode
WTR time Y N Y Y
Working Y N Y Y
channel
hold-off time
Protection Y N Y Y
channel
hold-off time
SD enabling Y N Y Y
SD trigger Y N Y Y
condition
ODUk Level Y N N Y
SPRing
single station WTR Y N N Y
configuratio SD enabling Y N N Y
n flag
Whether Y N N Y
management
node or not
Protection Y N N Y
unit
Trail Y N N Y
mapping
Span ID Y N N Y
Hold-off Y N N Y
time


n
ASON Cross- Y N N N
electrical connection
cross- level
connection
management Service type Y N N N
Direction Y N N N
Source Y N N N
channel
Sink channel Y N N N
Activation Y N N N
status
Service Y N N N
source
ASON Service Y N N N
SNCP source
management
Service sink Y N N N
Protection Y N N N
type
Level Y N N N
Revertive Y N N N
mode
WTR Y N N N
Delay time Y N N N
of the
working
channel
Delay time Y N N N
of the
protection
channel
SD enabling Y N N N
flag
SD Y N N N
triggering
condition
Service Y N N N
source


n
Master/slave Subrack ID Y N Y Y
subrack
management Subrack Y N Y Y
name
Service Service Y N Y Y
package package
11.7.5 Configuration Data Management Specifications of the NA

WDM
Function Function Upload Consistency Synchronize

Category Check
NE attribute NE equipment Y Y Y
type
NE shelf type Y Y Y
NE location Y Y Y
NE memo Y Y Y
NE start time of Y Y Y
daily PM data
collection
period
NE timezone Y Y Y
NE daylight Y Y Y
saving time
NE auto- Y Y Y
configuration
status
NE LAN Y Y Y
enabling flag
NE MAC Y Y Y
address
NE IP address Y Y Y
NE subnet mask Y Y Y
address


Category Check
Subrack name Y Y Y
Subrack memo Y Y Y
Subrack state Y Y Y
Card Logical unit Y Y Y

installation type
provisioned by
user
Payload type Payload type of Y Y Y

LWM client
port
APE Power Y Y Y
monitoring unit
Band type Y Y Y
Power Y Y Y
adjustment unit
of odd
wavelength
Power Y Y Y
adjustment unit
of even
wavelength
Power Y Y Y
unbalance
threshold
Automatic Y Y Y
adjustment
Monitoring flag Y Y Y
Standard power Y Y Y
bias
IPA Band type Y Y Y
Detection card Y Y Y
Shutdown card Y Y Y
Enabling flag Y Y Y
Restart mode Y Y Y
Off duration Y Y Y
On duration Y Y Y


Category Check
Testing duration Y Y Y
Safety control Y Y Y
switch
Alarm delay Y Y Y
time
Raman unit flag Y Y Y
Restart pulse Y Y Y
Assistant Y Y Y
detection
equipment unit
DCC Protocol of Y Y Y
DCC channel
ALC Chain identifier Y Y Y

which the node
belongs to
AID of the Y Y Y
reference
equipment in the
node
Position of the Y Y Y
upstream node
Position of the Y Y Y
downstream
node
AID of the Y Y Y
detect
equipment in the
node
AID of the Y Y Y
attenuation
adjust
equipment
(VOA) in the
node
Switch of chain Y Y Y
automatic to
adjust


Category Check
Threshold that Y Y Y
will induce the
node state to
abnormal
Node adjusts Y Y Y
compensation
Optical WTR time Y Y Y

wavelength
shared
protection
Optical line Revertive mode Y Y Y

protection
WTR time Y Y Y
1+1 optical Type of the Y Y Y

channel protection
protection group
Revertive mode Y Y Y
WTR time Y Y Y
Signal degrade Y Y Y
flag
1:N optical Revertive mode Y Y Y

channel
protection WTR time Y Y Y
Verify type of Y Y Y
protection
parameters in
1:n bidirectional
switching
Signal Degrade Y Y Y
flag
Inter-subrack Revertive mode Y Y Y

protection
WTR time Y Y Y
ROADM OXC logic Y Y Y

group type
Band type Y Y Y
Parity attribute Y Y Y
of the OXC
logic group


Category Check
Number of pass- Y Y Y
through
wavelengths in
the OXC logic
group
Number of the Y Y Y
added
wavelengths in
the OXC logic
group
State of the Y Y Y
OXC logic
group
TID of the MCA Y Y Y

card which is
used to check
the block state
of the
wavelength
Bid and port Y Y Y

number of the
MCA which is
used to check
the block
parameters of
the wavelength

card which is
used to check
the power
equalization of
the wavelength
Bid and port Y Y Y

number of the
MCA which is
used to check
the power
equalization of
the wavelength
Detecting BIAS Y Y Y
threshold of the
power
equalization


Category Check
TID of the OTU Y Y Y

specified by the
OXC logic
group and the
wavelength
number
Bid and port Y Y Y

number of the
OTU specified
by the OXC
logic group and
the wavelength
number
Block state of Y Y Y
the specified
wavelength in
DWD card
Power Y Y Y
equalization
enabling flag of
the specified
wavelength
Target power of Y Y Y
all the
wavelengths in
dB
curve of the
wavelength in
dB
Average power Y Y Y
of all the
wavelengths in
dB
Fact curve of the Y Y Y

wavelength in
dB
Bid of the DWC Y Y Y

card


Category Check
LAMBDA-N- Y Y Y
M, where N is
the index of the
OXC logic
group and M is
the lambda ID of
this OUT map
Wavelength Y Y Y
tunable flag
State of the Y Y Y
wavelength
Bid, port, and Y Y Y

path number of
the VOA card
TID of the OXC Y Y Y

logic group
WDM service From Y Y Y

configuration
To Y Y Y
WXCP Protection path Y Y Y
Working path Y Y Y
Protection Y Y Y
group memo
information
WTR time Y Y Y
flag
condition
Edge port Bid and port Y Y Y

number of the
edge port
In attribute of Y Y Y
the edge port
Out attribute of Y Y Y
the edge port
Optical cross- Optical cross ID Y Y Y

connection


Category Check
Optical cross Y Y Y
type
Bid and port Y Y Y

number of the
source card
Bid and port Y Y Y

number of the
destination card
Number of the Y Y Y
wavelength
Band type Y Y Y
Parent cross ID Y Y Y
State of cross Y Y Y
Optical cross- Bid of the Y Y Y

connection WSSD card
power
equalization OXC logic Y Y Y
group type
Number of pass- Y Y Y
through
wavelengths in
the OXC logic
group
Number of the Y Y Y
added
wavelengths in
the OXC logic
group
Band type Y Y Y
Parity attribute Y Y Y
of the OXC
logic group
State of the Y Y Y
OXC logic
group

card which is
used to check
the power
equalization of
the wavelength


Category Check
Bid and port Y Y Y

number of the
MCA which is
used to check
the power
equalization of
the wavelength
Detecting BIAS Y Y Y
threshold of the
power
equalization
TID of the Y Y Y
WSSM card
Bid of the Y Y Y
WSSM card
LAMBDA-N- Y Y Y
M, where N is
the index of the
OXC logic
group and M is
the lambda ID of
this OUT map
TID of the OTU Y Y Y

specified by the
OXC logic
group and the
wavelength
number
Bid and port Y Y Y

number of the
OTU specified
by the OXC
logic group and
the wavelength
number
State of the Y Y Y
wavelength
Power Y Y Y
equalization
enabling flag of
the specified
wavelength


Category Check
Target power of Y Y Y
all the
wavelengths in
dB
curve of the
wavelength in
dB
Reference Y Y Y
power curve of
the wavelength
in dB
Average power Y Y Y
of all the
wavelengths in
dB
Fact curve of the Y Y Y

wavelength in
dB
Lock state of the Y Y Y

wavelength
Bid, port, and Y Y Y

path number of
the VOA card
Wavelength Wavelength Y Y Y
lock monitored
object
Wavelength Y Y Y
State Y Y Y
11.7.6 Configuration Data Management Specifications of the NG

WDMA

Category Check
NE attribute Type Y Y Y
Name Y Y Y


Category Check
Location Y Y Y
Remarks N N N
Subrack type Y Y Y
Gateway type Y Y Y
Affiliated Y Y Y
gateway IP
address
Affiliated Y Y Y
gateway port
Daily Y Y Y
monitoring
pPeriod starts at
Timezone Y Y Y
Daylight saving Y Y Y
time
Auto-card Y Y Y
installation
ARP proxy Y Y Y
enabling
LAN port access Y Y Y

control enabling
MAC address Y Y Y
IP address Y Y Y
Subnet mask Y Y Y
Gateway N N N
Occurring delay Y Y Y
time (s)
Clearing delay Y Y Y
time (s)
Serial port baud Y Y Y

rate (bit/s)
Serial port link Y Y Y

type
Serial port Y Y Y
enabling


Category Check
State model Y Y Y
level
Buzzer on-off Y Y Y
Country code Y Y Y
National Y Y Y
segment code
Card parameter Input optical N N N

power
Reference value N N N
of the input
optical power
Reference time N N N
of the input
optical power
Input status N N N
Lower threshold N N N
of the input
optical power
Upper threshold N N N
of the input
optical power
Lower threshold N N N
of the output
optical power
Upper threshold N N N
of the output
optical power
Output optical N N N
power
Reference value N N N
of the output
optical power
Reference time N N N
of the output
optical power
Output status N N N
WDM interface Port name N N N
Loopback N N N


Category Check
Service type Y N Y
Laser status N N N
Service working Y N Y
mode
Actual N N N
wavelength No./
Wavelength
(nm)/Frequency
(THz)
Actual band Y N Y
type
Configuring the Y N Y
wavelength No./
Wavelength
(nm)/Frequency
(THz)
Actual speed Y N Y
(M)
Housekeeping Using status Y Y Y
Alarm mode Y Y Y
Alarm level Y Y Y
Control type N N N
Control state Y Y Y
Overhead in PT byte to be N N N
OPU received
PT byte N N N
received
OTU layer TTI to be N N N

transmitted
TTI to be N N N
received
TTI received N N N
IAE byte to be N N N
received
IAE byte N N N
received


Category Check
BEI at the OTU N N N

layer
BDI at the OTU N N N

layer
Overhead in TTI identifier to N N N

ODU be transmitted
TTI identifier to N N N
be received
TTI identifier N N N
received
STAT byte to be N N N
received at the
ODU layer
STAT byte N N N
received at the
ODU layer
BEI at the ODU N N N

layer
BDI at the ODU N N N

layer
AIS insertion at N N N
the ODU layer
CLK insertion at N N N
the ODU layer
OCI insertion at N N N
the ODU layer
OCH overhead Trace J0 mode N N N
Expected J0 N N N
mode
J0 to be received N N N
J0 received N N N
IPA (APR) Band Y Y Y

protection pair
Shut off card Y Y Y
Enabling flag Y Y Y
Restart mode Y Y Y


Category Check
Off duration (s) Y Y Y
On duration (s) Y Y Y
Testing period Y Y Y
Security control Y Y Y
switch
Restart pulse Y Y Y
switch
IPA auxiliary Y Y Y
detection
interface
Shelf ID of the Y Y Y
Raman card
Slot ID of the Y Y Y
Raman card
threshold
Raman card Y Y Y
threshold
auxiliary
Raman card
ROP card
Enabling the Y Y Y
Raman card
alarm
APE Power Y Y Y
monitoring unit
Band Y Y Y
Power Y Y Y
regulating
subrack/Unit of
odd wavelength
Power Y Y Y
regulating
subrack/Unit of
even
wavelength


Category Check
Power Y Y Y
unbalance
threshold
Automatic Y Y Y
adjustment
Monitoring flag Y Y Y
offset
Actual power Y Y Y
offset
ALC Link ID Y Y Y
Subrack ID N N N
Power detection Y Y Y
unit
Variable Y N Y
attenuation unit
Adjacent node Y Y Y
in the upstream
direction
Adjacent node Y Y Y
in the
downstream
direction
Reference unit Y Y Y
Line attenuation Y Y Y
exception
detection
threshold
Node gain Y Y Y
compensation
offset
Automatic Y Y Y
adjustment
switch
Test function Laser spectrum N N N

analysis


Category Check
Automatic N N N
WDM power
shutdown
Port protection Group ID Y Y Y

group
Protection type Y Y Y
Slot mapping Y Y Y
parameter
WTR time (s) Y Y Y
SD enabling Y Y Y
Delay time of Y Y Y
the working
channel
Delay time of Y Y Y
the protection
channel
Optical cross- Slot of the edge Y Y Y

connection port
management
station by Optical port of Y Y Y
station the edge port
In/Out attribute Y Y Y
of the edge port
Edge port flag Y Y Y
Source/Sink slot Y Y Y
of optical cross-
connection
Source/Sink Y Y Y
wavelength of
optical cross-
connection
Source/Sink Y Y Y
waveband of
optical cross-
connection
Optical cross- Y Y Y
connection type
Activation Y Y Y
status


Category Check
Direction Y Y Y
Adjustment Y Y Y
mode
Remarks Y Y Y
Electrical cross- Cross- Y Y Y

connection connection level
management
Service type Y Y Y
Direction Y Y Y
Source slot/ Y Y Y
port/channel
Sink slot/port/ Y Y Y
channel
Activation Y Y Y
status
SNCP Service source Y Y Y

management
Service sink Y Y Y
Service type Y Y Y
Protection type Y Y Y
Level Y Y Y
WTR time Y Y Y
Hold-off time of Y Y Y
the working
channel
Hold-off time of Y Y Y
the protection
channel
SD enabling Y Y Y
Direction Y Y Y
Remarks Y Y Y
Master/Slave Subrack ID Y Y Y
subrack
management Subrack name Y Y Y
Subrack FIC Y Y Y


Category Check
Subrack type Y Y Y
11.7.7 Configuration Data Management Specifications of the PTN

n
CES service CES service Y N Y Y
ATM service ATM service Y N Y Y
ATM OAM ATM OAM Y N Y Y
Ethernet E-LAN/E- Y N Y Y
service LINE/E-
AGGR
IEEE 1588 IEEE 1588 Y N Y Y

clock service clock service
V-UNI V-UNI Y N Y Y
group group
Service QoS Service QoS Y N Y Y
Ethernet Ethernet Y N Y Y
OAM OAM
Port
management Basic port Y N Y Y
Serial port Y N Y Y
LAG Y N Y Y
ATM IMA Y N Y Y
port
Virtual Y N Y Y
Ethernet port
MLPPP Y N Y Y
Microwave Y N Y Y
port
MC LSP Y N Y Y
ADSL2+ Y N Y Y
MCLAG Y N Y Y


n
Port OAM Port OAM Y N Y Y
Dynamic Dynamic Y N Y Y
tunnel tunnel
Static tunnel Static tunnel Y N Y Y
Basic MPLS Basic MPLS Y N Y Y

configuratio configuratio
n n
Tunnel Tunnel Y N Y Y
OAM OAM
Tunnel Tunnel Y N Y Y
group group
PW PW Y N Y Y
PW OAM PW OAM Y N Y Y
GRE tunnel GRE tunnel Y N Y Y
IP tunnel IP tunnel Y N Y Y
QinQ link QinQ link Y N Y Y
TPS TPS Y N Y Y
Card 1+1 Card 1+1 Y N Y Y

Basic Basic Y N Y Y
n n
Usage Usage Y N Y Y
Dynamic Dynamic Y N Y Y
L3VPN L3VPN
RMON History Y N Y N
control
group
MPLS LDP MPLS LDP Y N Y Y

tunnel tunnel
PW PW APS Y N Y Y
protection
group MC PW APS Y N Y Y


n
PW APS Y N Y Y
slave
protection
pair
PW Y N Y Y
redundancy
PW FRR Y N Y Y
PW multi- PW multi- Y N Y Y
hop hop
PTP clock PTP clock Y N Y Y
Physical Physical Y N Y Y
clock clock
ACR clock ACR clock Y N Y Y

service service
QoS QoS Y N Y Y
DS domain DS domain Y N Y Y
Mirroring Mirroring Y N Y Y
service service
NOTE
l Only the case-shape PTN equipment supports the PW redundancy function.

l Only the shelf-shape PTN equipment supports the mirroring service function.

Ethernet

n
High-speed Laser switch N N N N

Ethernet status
interface
Interval for Y Y Y Y
adjacent
packets (8
ns)


n
Maximum Y Y Y Y
packet length
Dead time Y Y Y Y
after the
control
packet is sent
(512 ns)
Auto- Y Y Y Y
negotiation
enabling
Data N N N N
statistics
counter for
the correct
packets in
the receiving
direction
Data N N N N
statistics
counter for
the incorrect
packets in
the receiving
direction
Data N N N N
statistics
counter for
all the
packets in
the
transmitting
direction
Optical Y N N N
interface
loopback
Data Y Y Y Y
encapsulatio
n protocol
Maximum Y Y Y Y
frame length


n
Dead time Y Y Y Y
after the
control
packet is sent
Optical Y N N N
interface
loopback
Laser state N N N N
Interval for Y Y Y Y
adjacent
packets
Ethernet user User ID and Y Y Y Y

management name
Ethernet TAG flag Y Y Y Y

interface
management VLAN ID Y Y Y Y
User priority Y Y Y Y
User ID Y Y Y Y
Port enabling Y Y Y Y
Working Y Y Y Y
mode
Binding path Y Y Y Y
Maximum Y Y Y Y
packet length
Loopback at Y N N N
the MAC
layer
Loopback at Y N N N
the PHY
layer
Encapsulatio Y Y Y Y
n protocol
PPT Y Y Y Y
enabling
Scramble Y Y Y Y


n
CRC reverse Y Y Y Y
Check field Y Y Y Y
length
FCS Y Y Y Y
calculation
sequence
LPT Y Y Y Y
enabling
LPT port and Y Y Y Y

VC trunk
relation
Default port Y Y Y Y
forwarding
priority
Port control Y Y Y Y
mode
Port sharing Y Y Y Y
type (MPLS
haring/stack
VLAN
sharing/not
sharing)
Port type (P/ Y Y Y Y

PE)
n method of
the P port
(CCC/
Martini)
Port data Y Y Y Y
format
entrance
check
(enable/
disable)
Port LCAS Y Y Y Y
enabling/
disabling
Stack VLAN Y Y Y Y
ID


n
Flow Y Y Y Y
message
priority
classificatio
n method and
forwarding
priority
Mapping Y Y Y Y
from TAG
priority to
forwarding
priority
LAPS/ Y Y Y Y
HDLC/GFP
encapsulatio
n parameter
Port point- Y Y Y Y
to-point
attribute
Threshold Y Y Y Y
for enabling
broadcast
message
suppression
Broadcast Y Y Y Y
message
suppression
Link Y Y Y Y
aggregation
configuratio
n
Default Y Y Y Y
VLAN ID
Default Y Y Y Y
VLAN
priority
enabling
Actual N N N N
physical
parameter


n
MAC Y N N N
loopback
PHY Y N N N
loopback
Laser switch Y N N N
Forwarding Y Y Y Y
priority
Non-auto- Y Y Y Y
negotiation
mode
Actual flow Y N Y Y
control mode
Broadcast Y Y Y Y
packet
suppression
enabling/
disabling
Broadcast Y Y Y Y
packet
suppression
threshold
Auto- Y Y Y Y
negotiation
flow control
attribute
Port type Y Y Y Y
n format of
the P port
Entrance Y Y Y Y
detection
QinQ Y Y Y Y
enabling
Default Y Y Y Y
QinQ ID
QinQ Y Y Y Y
priority


n
QinQ tag Y Y Y Y
attribute
Traffic Y Y Y Y
threshold
Traffic Y Y Y Y
threshold
time window
QinQ type Y Y Y Y
domain of
the Ethernet
port
Tag Y Y Y Y
Jumbo frame Y Y Y Y
type
Loopback Y Y Y Y
detection
Port Y Y Y Y
blocking
Port N N N N
mirroring
Port traffic Y N N N
query
Forced port Y Y Y Y
auto-
negotiation
TAG Tag Y Y Y Y
attribute
Default Y Y Y Y
VLAN ID
VLAN Y Y Y Y
priority
Entrance Y Y Y Y
detection
MPLS P/PE Y Y Y Y
attribute attribute
n format of
the P port


n
n protocol
Scramble Y Y Y Y
CRC reverse Y Y Y Y
Check field Y Y Y Y
length
FCS Y Y Y Y
calculation
sequence
Extended Y Y Y Y
header
selection
LCAS Y Y Y Y
enabling
LPT Y Y Y Y
enabling on
the VC trunk
port
Point-to- Y Y Y Y
point
attribute
QinQ Y Y Y Y
enabling
Default Y Y Y Y
QinQ ID
QinQ Y Y Y Y
priority
QinQ tag Y Y Y Y
attribute
QinQ type QinQ type Y Y Y Y

VCG
attribute Port enabling Y Y Y Y
Actual N N N N
physical
parameter
Forwarding Y Y Y Y
priority


n
Port priority Y Y Y Y
(ATTR_ET
HOVERSD
H_MAC_PR
IMODE)
Port priority Y Y Y Y
(ATTR_ET
HOVERSD
H_VCG_PR
IMODE)
HO Y Y Y Y
procedure
timer
duration
WTR Y Y Y Y
procedure
timer
duration
LCAS mode Y Y Y Y
TSD Y Y Y Y
enabling in
the switching
condition
LCAS at the N N N N
peer end
Port MAC N N N N
address
Port MAC N N N N
address
Working Y Y Y Y
mode
Maximum Y Y Y Y
packet length
Non-auto- Y Y Y Y
negotiation
mode
Auto- Y Y Y Y
negotiation
flow control
attribute


n
DCN system DCN query Y N N N

function
DCN system N Y Y Y
data
FDB Querying the Y N N N

function configuratio
n item of the
VLAN filter
table
Querying the Y N N N
configuratio
n of the
VLAN filter
table
Querying Y N N N
ToS
configuratio
ns
packet
priority
classificatio
n mode
Querying Y N N N
created
VLAN items
multicast
addresses of
VLANs
Deleting the N Y N N
configuratio
n item of
VLAN filter
table
Configuratio N Y N N
n of the
VLAN filter
table
VLAN item


n
VLAN N N Y Y
unicast
routing table
VLAN N N N Y
multicast
table
VLAN table N N Y Y
MAC N N Y Y
address
disabling
LPT Querying the Y N N N

mapping
between the
port and VC-
Trunk (LPT)
mapping
between the
port and VC-
Trunk (LPT)
Setting the N Y N N
mapping
between the
port and VC-
Trunk (LPT)
LPT data N N N Y
Ethernet port N N Y N
Activated or N N Y N
not
LPT N N Y N
direction
Mapped port N N Y N
list in the
LPT
mapping
New FDB Entry of the Y Y Y Y

forwarding
filter table


n
VLAN Y Y Y Y
unicast
MAC Y Y Y Y
address
disabling
Aging time Y Y Y Y
New QoS CAR Y Y Y Y

information
CoS Y Y Y Y
information
Flow Y Y Y Y
shaping
information
Flow Y Y Y Y
information
PTMP LPT Point-to- Y Y Y Y

multipoint
LPT
mapping
LPT bearer Y Y Y Y
mode
LPT hold-off Y Y Y Y
time mode
Shaping Querying the Y N N N

shaping
enabling of
the port
queue
port queue
parameter
Setting the N Y N N
shaping
enabling of
the port
queue
Setting the N Y N N
port queue
parameter


n
Shaping N N Y Y
parameter
SRP function Querying the Y N N N

SRP protocol
status
node ID of
the local
node
node name of
the local
node
hold-off time
of SDH
protection
switching
IPS
switching
restoration
time
SRP aging
time
SRP priority
partition
value
SRP
mapping
mode
SRP VLAN
priority
mapping


n
SRP TOS
priority
mapping
Setting the N Y N N
SRP protocol
status
Setting the N Y N N
node ID of
the local
node
Setting the N Y N N
node name of
the local
node
Setting the N Y N N
hold-off time
of SDH
protection
switching
Setting the N Y N N
IPS
switching
restoration
time
Setting the N Y N N
SRP aging
time
Setting the N Y N N
SRP priority
partition
value
Setting the N Y N N
SRP
mapping
mode
Setting the N Y N N
SRP VLAN
priority
mapping


n
Setting the N Y N N
SRP TOS
priority
mapping
Node name N N Y Y
Node SRP N N Y Y
protocol
enabling
WTR time N N Y Y
Restoration N N Y Y
time
Forwarding N N Y Y
aging time
Priority N N Y Y
partition
value
ToS priority N N Y Y
mapping
table
Priority N N Y Y
mapping
mode
VLAN N N Y Y
priority
mapping
table
STP function Querying the Y N N N

bridge
priority
bridge
timing
parameter
bridge MAC
address
Setting the N Y Y Y
STP
enabling


n
Point-to- Y Y Y Y
point
attribute
Setting the N Y Y Y
STP working
mode
Spanning Bridge Y Y Y Y
tree parameter
management
module Bridge port N N N N
parameter
Protocol Y Y Y Y
enabling
Bridge N N N N
running
information
Port running N N N N
information
VB bridge N N N N
port
parameter
Port role N N N N
Forwarding VLAN filter Y Y Y Y

filter table table
management (including
module the attributes
of VLAN
items)
Unicast filter Y Y Y Y
table
(including
unicast and
VLAN
unicast)
Multicast Y Y Y Y
filter table
Priority Y Y Y Y
mapping


n
Aging time Y Y Y Y
(including
Ethernet
aging time
and multicast
aging time)
GARP GARP Y Y Y Y
protocol protocol
module (including
management
of GVRP,
GMRP, and
GMRP in
VLAN)
CAR CAR Y Y Y Y
management configuratio
n
CAR Y Y Y Y
enabling/
disabling
CAR Y Y Y Y
parameter
(CIR/CBS/
PIR/MBS)
CAR Y Y Y Y
allocated by
VLAN
VB VB Y Y Y Y
management configuratio
n and name
Disabled N N N N
MAC
address in
VB
VB Y Y Y Y
mounting
Ethernet EPL/EVPL/ Y Y Y Y
service transit
service
configuratio
n


n
EPLn/ Y Y Y Y
EVPLn
service
configuratio
n
EPL LSP Y Y Y Y
forwarding
priority
LAN LSP Y Y Y Y
forwarding
priority
VLAN Y Y Y Y
switch
configuratio
n
VLAN Y Y Y Y
SNCP
configuratio
n
VLAN N N N N
SNCP
switching
status
Bridge STP Y Y Y Y
priority
QinQ type Y Y Y Y
domain
Miscellaneo Ethernet Y Y Y Y
us static route
DPT module Y Y Y Y
function
Flow Y Y Y Y
classificatio
n
Other N N N N
attribute
management
of the bridge


n
Ring Y Y Y Y
network
service
Card IP Y Y Y Y
address
Ethernet IGMP Y Y Y Y
IGMP snooping
function enabling
Maximum Y Y Y Y
response
time for
multicast
query
messages
Router aging Y Y Y Y
time
Port N N N N
configuratio
n and
management
of multicast
routers
Static N N N N
multicast
entry
VC trunk Bandwidth Y Y Y Y
management binding of
the VC trunk
Shared Y Y Y Y
attribute of
the VC trunk
Service QoS/ QoS Y Y Y Y

CoS management
management of
transparent
transmission
services
Shaping Y Y Y Y
management
RPR Protection Y Y Y Y
protection mode


n
Protection Y Y Y Y
reversion
mode
Delay time Y Y Y Y
of RPR
protection
switching
WTR time of Y Y Y Y
RPR
protection
RPR external N N N N
switching
command
RPR N N N N
protection
switching
information
RPR RPR Y Y Y Y
topology protocol
management enabling
status
Topology Y Y Y Y
timing
Node Y Y Y Y
number
Node name Y Y Y Y
Querying the N N N N
topology
information
RPR Y Y Y Y
bandwidth
use priority
Link sending Y Y Y Y
priority
Related RPR N N N N
attribute of protection
the RPR status
protection
information
query


n
RPR N N N N
switching
status
Total RPR N N N N
switching
times
Total RPR N N N N
protection
times
Last RPR N N N N
switching
request
RPR N N N N
switching
command
RPR Y Y Y Y
protection
mode
RPR Y Y Y Y
protection
restoration
mode
Delay time Y Y Y Y
RPR
protection
WTR time of Y Y Y Y
RPR
protection
RPR node ID Y Y Y Y
RPR node Y Y Y Y
name
RPR Y Y Y Y
enabling
RPR timer Y Y Y Y
duration
Related RPR node ID N N N N

attribute of
the RPR RPR node N N N N
topology name


n
information RPR N N N N
query direction
RPR N N N N
protection
mode
RPR zero N N N N
ring reached
RPR one ring N N N N

reached
Number of N N N N
hops on RPR
zero ring
Number of N N N N
hops on RPR
one ring
RPR N N N N
eastbound
ring next
node ID
RPR N N N N
westbound
ring next
node ID
RPR N N N N
eastbound
protection
status
RPR N N N N
westbound
protection
status
RPR N N N N
eastbound
switching
status
RPR N N N N
westbound
switching
status


n
RPR N N N N
eastbound
transmitting
link weight
RPR N N N N
westbound
transmitting
link weight
RPR N N N N
eastbound
link A0
reserved
bandwidth
RPR N N N N
westbound
link A0
reserved
bandwidth
Related RPR Y Y Y Y
attribute of transmitting
the RPR link link weight
information
query and RPR used Y Y Y Y
setting bandwidth of
priority A
RPR Y Y Y Y
reserved
bandwidth of
priority A
RPR used Y Y Y Y
bandwidth of
priority B-
CIR
Static link Setting the Y Y Y Y

aggregation link
aggregation
system or
port priority
LAG and
actual LAG
status


n
LAG system
or port
priority and
the system
MAC
address
LAG
abstract
LAG details
details about
the LAG port
LAG packet
statistics
LAG Querying the Y N N N

function LAG name
LAG
system
priority of
the LAG
port priority
of the LAG
system MAC
address of
the LAG
Adding the N Y N N
LAG
Setting the N Y N N
system
priority of
the LAG


n
Setting the N Y N N
port priority
of the LAG
LAG N N N N
information
LAG priority N N N Y
Link group N N Y N
ID
Link group N N Y N
name
Link group N N Y N
type
Class for N N Y N
middle
storage
Main port N N Y N
LAG port list N N Y N
Selected port N N Y N
list
Inter-card Querying the Y N N N

LAG inter-card
LAG
inter-card
LAG name
protection
switching
revertive
mode of the
inter-card
LAG
system
priority of
the inter-card
LAG


n
port priority
of the inter-
card LAG
Setting the N Y N N
inter-card
LAG name
Setting the N Y N N
protection
switching
revertive
mode of the
inter-card
LAG
Setting the N Y N N
system
priority of
the inter-card
LAG
Setting the N Y N N
port priority
of the inter-
card LAG
Inter-card N N Y Y
LAG
information
Port LAG Querying the Y N N N

LAG port
LAG port
Adding the N Y N N
LAG
(branch) port
LAG record N N N Y
LAG record N N Y N
Service Ethernet N N N N
mirroring service
mirroring


n
Ethernet Querying the Y N N N

OAM MP attribute
by the MP ID
(0 parameter
query)
CCM
sending
period
LB timeout
period
LT timeout
period
CC
activation
status
Creating N Y N N
(Adding) the
MP
Setting the N Y N N
CCM
sending
period
Setting the N Y N N
LB timeout
period
Setting the N Y N N
LT timeout
period
Setting the N Y N N
CC
activation
status
ID of the last N N Y Y
tested peer
MP


n
Type of the N N Y Y
service
maintained
by the MP
Service ID N N Y Y
Port ID N N Y Y
Port type N N Y Y
VLAN ID N N Y Y
MP level N N Y Y
(0-7)
MP type N N Y Y
MP direction N N Y Y
CC sending N N Y Y
period
LB timeout N N Y Y
period
LT timeout N N Y Y
period
CC N N Y Y
activation
status
Related Enabling the Y Y Y Y

attribute of Ethernet P2P
Ethernet port OAM
OAM protocol
Ethernet P2P Y Y Y Y
OAM
working
mode
Link event Y Y Y Y
notification
Unidirection Y Y Y Y
al operation
response to
remote
loopback


n
Maximum N N N N
OAM packet
length
Error frame Y Y Y Y
monitor
window
Error frame Y Y Y Y
monitor
threshold
Error frame Y Y Y Y
period
window
Error frame Y Y Y Y
period
threshold
Error frame Y Y Y Y
second
window
Error frame Y Y Y Y
second
threshold
Loopback N N N N
status
Response to N N N N
remote
loopback
Remote N N N N
Ethernet P2P
OAM
working
mode
Remote link N N N N
event
notification
Remote N N N N
unidirection
al operation


n
Remote N N N N
maximum
OAM packet
length
Ethernet port MP Y Y Y Y
OAM
function MP attribute Y Y Y Y
LB timeout Y Y Y Y
period
LT timeout Y Y Y Y
period
Multicast CC Y Y Y Y
sending
period
Activation Y Y Y Y
status of
multicast CC
monitoring
Ethernet test Whether to N N N N

frame respond to
management the test frame
In sending N N N N
test frame
status (real-
time)
Test frame N N N N
configuratio
n (including
the sending
mode,
sending
direction,
and number
of test frames
sent)


n
Three N N N N
counters
(sent test
frame timer.
received
response
frame timer,
received test
frame timer)
Protocol N N N N
fault
diagnosis/
restoration
MPLS tunnel Transit

configuratio tunnel
n management
Tunnel type Y Y Y Y
Inbound port Y Y Y Y
ID
Inbound port Y Y Y Y
type
Incoming Y Y Y Y
label
Outbound Y Y Y Y
port ID
Outbound Y Y Y Y
port type
Outgoing Y Y Y Y
label
Next-hop IP Y Y Y Y
address
Static ARP Static ARP

entry entry
n n
IP address Y Y Y Y
MAC Y Y Y Y
address

11.7.9 Configuration Data Management Specifications of the ATM

n
ATM service ATM traffic Y Y Y Y

configuratio descriptor
n
ATM cross- Y Y Y Y
connection
ATM Y Y Y Y
protection
pair
ATM Y Y Y Y
protection
group
ATM Port type Y Y Y Y

interface
attribute Maximum Y Y Y Y
number of
VPI bits
Maximum Y Y Y Y
number of
VCI bits
Maximum Y Y Y Y
number of
VPCs
Maximum Y Y Y Y
number of
VCCs
Number of N N N N
VPCs
configured
currently
Number of N N N N
VCCs
configured
currently
Maximum Y Y Y Y
number of
VPIs
supporting
VC
switching


n
Minimum Y Y Y Y
number of
VPIs
supporting
VC
switching
Activation Y N N N
status
UPC/NPC Y Y Y Y
enabling/
disabling
Loopback Y N N N
Number of Y Y Y Y
VPIs of the
VCC
supported by
the ATM
port
VC trunk VC trunk Y Y Y Y
management bandwidth
binding
ATM port ATM logical Y Y Y Y

attribute port type
Maximum Y Y Y Y
number of
VPI bits of
the ATM
port
Maximum Y Y Y Y
number of
VCI bits of
the ATM
port
Maximum Y N Y N
number of
VPCs of the
ATM port
Maximum Y N Y N
number of
VCCs of the
ATM port


n
Current N N N N
number of
VPCs of the
ATM port
Current N N N N
number of
VCCs of the
ATM port
ATM logical Y N N N
port status
UPC/NPC Y Y Y Y
enabling of
the ATM
logical port
ATM logical Y N N N
port
loopback
Number of Y Y Y Y
VPIs of
VCCs
supported by
ATM
Maximum N N N N
VPI range of
the VC
switching
supported by
the ATM
port
Minimum N N N N
VPI range of
the VC
switching
supported by
the ATM
port
Port name N N N N
ATM logical Y Y Y Y
port type


n
Maximum Y Y Y Y
number of
VPI bits of
the ATM
port
Maximum Y Y Y Y
number of
VCI bits of
the ATM
port
Maximum Y Y Y Y
number of
VPCs of the
ATM port
Maximum Y Y Y Y
number of
VCCs of the
ATM port
Current N N N N
number of
VPCs of the
ATM port
Current N N N N
number of
VCCs of the
ATM port
ATM logical Y N N N
port status
UPC/NPC Y Y Y Y
enabling of
the ATM
logical port
ATM logical Y N N N
port
loopback
Number of Y Y Y Y
VPIs of
VCCs
supported by
ATM


n
Maximum N N N N
VPI range of
the VC
switching
supported by
the ATM
port
Minimum N N N N
VPI range of
the VC
switching
supported by
the ATM
port
OAM Segment Y Y Y Y
attribute of
the connect
point
CC Y Y Y Y
activation
status of the
connection
point
NE LLID Y Y Y Y
IMA IMA group Y Y Y Y

E1 link Y Y Y Y
parameter
IMA mode Y Y Y Y
information
Real-time N N N N
port rate
query
ATM port J0 byte to be Y Y Y Y

overhead transmitted
received
J0 byte N N N N
received


n
transmitted
received
J1 byte N N N N
received
received
transmitted
C2 byte N N N N
received

ASON

n
Intelligent Channel N N N N
trail status
refreshing
SDH ASON OSPF Y N Y Y

disaster authenticatio
recovery n parameter
RSVP Y N Y Y
authenticatio
n parameter
LMP auto- Y N Y Y
discovery
type

alarm and performance


n
Alarm Severity Y N N N
management
Automatic Y N N N
alarm report
Alarm Y N N N
masking
Alarm Y N N N
reversion
Setting the Y N N N
bit error
alarm
threshold
Setting NE Y N N N
alarm
attributes
Alarm Y N N N
insertion
Setting the Y N N N
automatic
alarm
acknowledge
ment
Setting the Y N N N
automatic
alarm
synchronizat
ion
Setting the Y N N N
enabling of
the alarm
dynamic
correlation
analysis
Setting the Y N N N
automatic
conversion
of current
alarms to
history
alarms


n
Alarm Y N N N
correlation
rule
Alarm Y N N N
attribute
template
Equipment Y N N N
alarm
filtering
NMS alarm Y N N N
attribute
Setting alarm Y N N N
diagnosis
rules
Setting the Y N N N
alarm
notification
Setting alarm Y N N N
performance
dump
conditions
Performance Performance N N N N
management monitoring
status
Performance N N N N
threshold
Performance Y N N N
monitoring
time
IP Y N N N
performance
monitoring
time
ATM Y N N N
performance
monitoring
time
Performance Y N N N
threshold
template


Operation Guide for Common Features 12 Backing Up and Restoring the NE Data
12 Backing Up and Restoring the NE Data
About This Chapter
For the security of the NE data, you can back up and restore the NE data. Applies to the MSTP,
WDM, NA WDM, RTN, PTN, Marine series NEs.
12.1 Comparison of NE Data Backup and Restoration Methods

You need to back up important NE data during daily maintenance. You can back up and restore
the NE database, to ensure the SCC board of the NE automatically restores to normal operation
after the NE data in the DRDB database of the SCC board loss or equipment power failure. This
section describes several NE data backup and restoration methods. You can select the method
as required.
12.2 Backing Up the NE Database to the SCC Board
You need to back up the NE database during daily maintenance, to ensure that the SCC board
of the NE automatically restores to normal operation after a data loss or equipment power failure.
When you back up the NE database to the SCC board, you actually back up the NE data in the
DRDB database of the SCC board to the Flash database. When the NE is restarted after a power
failure, the SCC board automatically reads the configuration from the FLASH and issues the
configuration to the boards.
12.3 Backing Up History Alarms to a Flash Card
Equipment upgrade or resetting leads to the loss of history alarm information in the equipment
memory. You can use the backup function to back up the history alarm information in the DRDB
database of the SCC board to a flash card.
12.4 Backing Up the NE Database to a CF Card
To improve the security of the NE configuration data and prevent the loss of the configuration
data due to the NE fault, you need to back up the NE database. You can back up the NE database
to a CF card, to ensure the automatic restoration of the operation after the data loss on the SCC
board of the NE or equipment power failure. Applies to the MSTP, WDM, PTN, RTN, and
Marine series NE whose SCC boards are configured with CF cards.
12.5 Restoring the NE Database from the SCC Board
When the database file is lost due to the NE maintenance or NE fault, you can restore the NE
data from the DRDB database file that is already backed up to Flash database on the SCC board.
12.6 Restoring the NE Database from the CF Card

12 Backing Up and Restoring the NE Data Operation Guide for Common Features
database from the database file that is already backed up on the CF card.

12.1 Comparison of NE Data Backup and Restoration

Methods
You need to back up important NE data during daily maintenance. You can back up and restore
the NE database, to ensure the SCC board of the NE automatically restores to normal operation
after the NE data in the DRDB database of the SCC board loss or equipment power failure. This
section describes several NE data backup and restoration methods. You can select the method
as required.
Comparison of Backup and Restoration Methods

The locations for backing up and restoring the NE database include the SCC board, CF card,
local server and remote server. Different storage locations decide different types of backup and
restoration methods. See Table 12-1.
Table 12-1 Backup and Restoration Methods and Application Scenarios

Backup and Restoration Method Application Scenario
Back up/Restore the NE database to/from an Backs up the NE data in the DRDB database
SCC board of the SCC board to the FLASH database,
when the SCC board is without a CF card.
During the restoration, after a warm reset or
a cold reset on the SCC board, the SCC board
reads the configuration from the FLASH and
issues the configuration to other boards.
Back up/Restore the NE database to/from a Backs up the NE data in the DRDB database
CF card of the SCC board to the CF card, when the
SCC board is with a CF card.
During the restoration, the database is
restored from the CF card to the DRDB
database of the SCC board. After a warm reset
or cold reset on the SCC board, the memory
database on the SCC board is updated. Then,
after the warm resets on other boards, the NE
memory data is issued to the boards.
Back up/Restore the NE data to/from a NMS Stores the data in the computer where the
server NMS server resides.
During restoration, you can select the backup
file in the directory where the NE data is
saved.
Back up/Restore the NE data to/from a NMS Stores the data in the computer where the
client NMS client resides.
During restoration, you can select the backup
file in the directory where the NE data is
saved.

NE Database
The NE configuration data is saved in the NE database. There are three types of NE databases
as follows:
l MDB: Memory database. The data in a MDB database is changed when the configuration
information is changed. The data is lost when the SCC board is reset or a power failure
occurs.
l DRDB: Dynamic random database. The data that is verified is automatically saved in the
DRDB database.
l FDB: Flash database. There are the FDB0 and FDB1 databases. The data need to be copied
to the database manually and can be saved permanently.
When the NE configuration data is issued to the SCC board, it is saved in the MDB database. If
the verification is successful, the SCC board automatically copies the contents in the MDB
database to the DRDB database and issues the verified configuration data to the boards. You
need to manually copy the DRDB database to the FDB database, as a backup of the DRDB
database. When the NE is restarted after a power failure, the SCC board checks whether there
is configuration data in the DRDB database. If yes, the data are restored from the DRDB
database. If the data in the DRDB database is damaged, the data is restored from the FDB0 and
FDB1 databases.
NE Configuration Data
The NE configuration data refers to the information in the DRDB database of the NE, such as
the board configuration, clock configuration and protection relations of the NE. It is the
instruction file of the NE and the key for the NE to perform normally in the entire network.
NE Database Package
The NE database package is a package that contains all database files on an NE and a file list
that defines and manages those files.
The NE database package and NE configuration data are the same data on the NE in different
releases. You can perform the NE database package backup and restoration on the release 5.00.06
NE or the NE of later release.
12.2 Backing Up the NE Database to the SCC Board

You need to back up the NE database during daily maintenance, to ensure that the SCC board
of the NE automatically restores to normal operation after a data loss or equipment power failure.
When you back up the NE database to the SCC board, you actually back up the NE data in the
DRDB database of the SCC board to the Flash database. When the NE is restarted after a power
failure, the SCC board automatically reads the configuration from the FLASH and issues the
configuration to the boards.
Prerequisite
l You must log in to the NE as an NE user with system level authority.

Procedure
2 In the Object Tree on the left, select an NE and click .

3 In Configuration Data Management List, select an NE or multiple NEs.
4 Choose Back Up NE Data > Back Up Database to SCC.
6 The Operation Result dialog box is displayed. After the backup is successful, click Close.
----End
12.3 Backing Up History Alarms to a Flash Card

Equipment upgrade or resetting leads to the loss of history alarm information in the equipment
memory. You can use the backup function to back up the history alarm information in the DRDB
database of the SCC board to a flash card.
Prerequisite
l It is suitable for OptiX OSN 1500, OptiX OSN 2000, OptiX OSN 2500, OptiX OSN 3500,
OptiX OSN 7500, OptiX OSN 9500.
Procedure

4 Choose Back Up NE Data > Back Up History Alarm to FLASH.
5 After the backup is successful, in the Operation Result dialog box, click Close.
----End
12.4 Backing Up the NE Database to a CF Card

To improve the security of the NE configuration data and prevent the loss of the configuration
data due to the NE fault, you need to back up the NE database. You can back up the NE database
to a CF card, to ensure the automatic restoration of the operation after the data loss on the SCC
board of the NE or equipment power failure. Applies to the MSTP, WDM, PTN, RTN, and
Marine series NE whose SCC boards are configured with CF cards.
12.4.1 Automatically Backing Up the NE Database to a CF Card
You need to back up the NE database during the daily maintenance. You can back up the NE
data in the DRDB database of the SCC board to a CF card automatically, to ensure the automatic

restoration of the operation after the data in the DRDB database loss on the SCC board of the
NE or equipment power failure.
12.4.2 Manually Backing Up the NE Database to a CF Card
data in the DRDB database of the SCC board to a CF card manually, to ensure the automatic
restoration of the operation after the data in the DRDB database loss on the SCC board or
equipment power failure.
12.4.1 Automatically Backing Up the NE Database to a CF Card

data in the DRDB database of the SCC board to a CF card automatically, to ensure the automatic
restoration of the operation after the data in the DRDB database loss on the SCC board of the
NE or equipment power failure.
Prerequisite
l Log in to the NE as an NE user with "System Level" authority.
l The SCC board must be configured with the CF card. Applies to the MSTP, WDM, PTN,
RTN, and Marine series NE whose SCC boards are configured with CF cards.
Procedure
2 In the Object Tree on the left, select an NE and click the double-right-arrow button (red).
3 Select one or more NEs in the Configuration Data Management List.
4 Choose Back Up NE Data > Automatically Back Up to CF Card. The Automatically Back
Up NE Data to CF Card window is displayed. Set the Automatic Backup Enabling Status
and Automatic Backup Period(min).
NOTE
Before the setting, you can click Query to query the current status of the automatic backup of NE data to
a CF card.
5 Click Close in the Operation Result dialog box is displayed.
----End
12.4.2 Manually Backing Up the NE Database to a CF Card

data in the DRDB database of the SCC board to a CF card manually, to ensure the automatic
restoration of the operation after the data in the DRDB database loss on the SCC board or
equipment power failure.
Prerequisite
l Log in to the NE as an NE user with "System Level" authority.

l The SCC board must be configured with the CF card. Applies to the MSTP, WDM, PTN,
RTN, and Marine series NE whose SCC boards are configured with CF cards.
Procedure
2 In the Object Tree on the left, select an NE and click the double-right-arrow button (red).
3 Select one or more NEs in the Configuration Data Management List.
4 Choose Back Up NE Data > Manually Back Up Database to CF Card.
6 Click Close in the Operation Result dialog box is displayed.
----End
12.5 Restoring the NE Database from the SCC Board

data from the DRDB database file that is already backed up to Flash database on the SCC board.
Prerequisite
l The DRDB database must be backed up to Flash database on SCC board.
Procedure
1 Double-click an NE or ONE on the Main Topology and the Slot Layout is displayed.
2 Right-click the active SCC board, choose Warm Reset or Cold Reset or SCC Reset.
NOTE
l The reset modes for different SCC board are different. You need to choose the reset mode as required.
l When you choose Cold Reset or SCC Reset, the Warning dialog box is displayed. Click OK to start
the reset.
3 A dialog box is displayed. Click OK to complete the reset.
----End
12.6 Restoring the NE Database from the CF Card

database from the database file that is already backed up on the CF card.
Prerequisite


l The NE database must be backed up to the CF card.
l Applies to the MSTP, WDM, PTN, RTN, and Marine series NE whose SCC boards are
configured with CF cards.
Procedure

4 Click Restore NE Database. The Confirm dialog box is displayed, indicating that the
restoration of the NE database may lead to service interruption.
5 Click OK to start to restore the NE database.
6 Click Close.
----End
Follow-up Procedure
After the NE database is restored, the database on the CF card is restored to the memory of the
SCC board, but not issued to the boards. If you want to restore the configuration data of the
boards, you need to perform a warm reset on the SCC board. Then, perform warm resets on other
boards. During the reset of the boards, the NE issues the configuration data to the boards again.

Operation Guide for Common Features 13 Customer Management
13 Customer Management
About This Chapter
By using the U2000, you can manage and maintain the customer information as required.
13.1 Relation Between User and Customer

The U2000 defines user and customer. You can authorize a customer to a user.
13.2 Creating a Customer Group
Customers can be grouped for easy management.
13.3 Creating a Customer
You can create customer information as required, so that you can set a specific customer and a
maintenance network for the trail.
13.4 Browsing Customer Information
By browsing customer information, you can know the name, legal representative and contact
modes of the relevant customer of the service.
13.5 Viewing Relevant Trails of a Customer
In a normally running network, the trail is the carrier of the customer service and is the resource
of the customer. In the network management, knowing the trails of different customers is very
helpful to take care of the interests of different customers.
13.6 Browsing Current Alarms of a Customer
Each customer has a number of services that can report alarms when they run in the network.
These alarms show the current status of the service. For this reason, you must query the current
alarms of the customer.
13.7 Browsing History Alarms of a Customer
By querying the history alarms of a customer, you can learn about the long-term status of the
services that run in the network. When maintaining the services of the customer, you can use
the history alarm information for reference.
13.8 Modifying Customer Information
If the customer information such as contact mode is changed, you need to modify the customer
information in time.
13.9 Deleting a Customer

13 Customer Management Operation Guide for Common Features
The information of customers with whom contracts are fulfilled must be deleted. This operation
ensures that the customer information is not disclosed, and decreases the redundant information
in the database.
13.10 Viewing the Customers Affected by an Alarm
When an alarm occurs on a service, you need to query the customers that are affected by the
alarm. According to the query result, you can determine whether to notify the customer of the
alarm.
13.11 Specifying the Customer of a Service
When creating and modifying a service, you need to specify the customer that the service belongs
to. This can facilitate the trail management.
13.12 Enabling VCN Status of a Customer
A customer can view relevant trails only when the VCN function is enabled.

13.1 Relation Between User and Customer

The U2000 defines user and customer. You can authorize a customer to a user.
Definition of Customer and User

Customer: As an attribute of a service trail, "customer" identifies the customer that the service
trail belongs to.
User: You can log in to the U2000 client as a user. The unique user name and password determine
the operation and management rights of the user on the U2000.
Relation Between User and Customer

When a customer is authorized to a user, the user can manage all the trails that belong to the
customer.
13.2 Creating a Customer Group

Customers can be grouped for easy management.
Prerequisite
Procedure
1 Choose Service > Customer Management from the Main Menu.
2 Right-click an existing customer group and choose Create Group from the shortcut menu.
3 In the displayed dialog box, enter a name for the Group Name field.
4 Click OK.
----End
13.3 Creating a Customer

You can create customer information as required, so that you can set a specific customer and a
maintenance network for the trail.
Prerequisite
l You must be an NM user with "network operator" authority or higher.
l The customer group must be created.

Procedure
1 Choose Service > Customer Management from the Main Menu. The Customer
Management window is displayed.
2 Select a customer group and click Create. The Create Customer window is displayed.
3 According to actual requirements, enter the new customer information, such as Customer
Name, Legal Representative, and Phone.
NOTE
If the customer is required to perform the ASON OVPN management, set OVPN ID or select the
Automatch OVPN ID check box.
4 Click OK. The new customer information is displayed in the customer list.
----End
13.4 Browsing Customer Information

By browsing customer information, you can know the name, legal representative and contact
modes of the relevant customer of the service.
Prerequisite
Procedure
1 Choose Service > Customer Management from the Main Menu. In the Customer
Management window, all customer information is displayed.
2 Optional: If the customer information is changed, you can click Refresh to browse the changed
customer information.
----End
13.5 Viewing Relevant Trails of a Customer

In a normally running network, the trail is the carrier of the customer service and is the resource
of the customer. In the network management, knowing the trails of different customers is very
helpful to take care of the interests of different customers.
Prerequisite
Procedure
The information of all customers is displayed in the Customer Management window.
2 You can view the SDH/WDM/Ethernet/ATM trails seperately.

l Right-click a record of customer information, and choose Browse Relevant Trails > SDH
Trail from the shortcut menu.
l Right-click a record of customer information, and choose Browse Relevant Trails > WDM
l Right-click a record of customer information, and choose Browse Relevant Trails >
Ethernet Trail from the shortcut menu.
l Right-click a record of customer information, and choose Browse Relevant Trails > ATM
The SDH/WDM/Ethernet/ATM trails of the customer are displayed in the SDH/WDM/
Ethernet/ATM Trail Management window.
----End
13.6 Browsing Current Alarms of a Customer

Each customer has a number of services that can report alarms when they run in the network.
These alarms show the current status of the service. For this reason, you must query the current
alarms of the customer.
Prerequisite
Procedure
The Customer Managementdialog box displays the information about all the customers.
2 You can view the SDH/WDM/Ethernet/ATM current alarms separately.
l Right-click a customer and choose Browse Relevant Alarms > SDH Current Alarm.
l Right-click a customer and choose Browse Relevant Alarms > WDM Current Alarm.
l Right-click a customer and choose Browse Relevant Alarms > Ethernet Current
Alarm.
l Right-click a customer and choose Browse Relevant Alarms > ATM Current Alarm.
The current SDH/WDM/Ethernet/ATM service alarms of the customer are displayed in the
Current Alarms dialog box.
3 To display the latest alarms, select the Display latest alarms check box in the bottom-left corner.
4 Select an alarm. The detail information and handling suggestions of the alarm are displayed in
the following list.
5 Optional: Select one or more alarms. Click Acknowledge to display the Confirm dialog box.
6 Optional: Click Yes. The Acknowledgement Time, Acknowledgement Status and
Acknowledgement User columns of the selected alarm shows the relevant values.
NOTE
The confirmed and terminated alarms are changed to history alarms.
7 Optional: Select one or more alarms, and then click Clear. In the Confirm prompt box, click
Yes. The Clearance Time, Clearance Status and Clearance User columns of the selected
alarm shows the relevant values.

NOTE
The confirmed and terminated alarms are changed to history alarms.
----End
13.7 Browsing History Alarms of a Customer

By querying the history alarms of a customer, you can learn about the long-term status of the
services that run in the network. When maintaining the services of the customer, you can use
the history alarm information for reference.
Prerequisite
Procedure
The Customer Management dialog box displays the information about all the customers.
2 You can view the SDH/WDM/Ethernet/ATM history alarms separately.

l Right-click a customer and choose Browse Relevant Alarms > SDH History Alarm.
l Right-click a customer and choose Browse Relevant Alarms > WDM History Alarm.
l Right-click a customer and choose Browse Relevant Alarms > Ethernet History
Alarm.
l Right-click a customer and choose Browse Relevant Alarms > ATM History Alarm.
The history alarms of the SDH/WDM/Ethernet/ATM service are displayed in the History
Alarms dialog box.
3 Optional: Select an alarm. The detail information and handling suggestions of the alarm are
displayed in the following list.
----End
13.8 Modifying Customer Information

If the customer information such as contact mode is changed, you need to modify the customer
information in time.
Prerequisite
Procedure
1 Choose Service > Customer Management from the Main Menu to display the Customer
Management dialog box.
2 In the customer list, select a customer, double-click the required field, and modify the
information. Then, click Apply.

3 The Operation Result prompt box is displayed. Click Close.
----End
13.9 Deleting a Customer

The information of customers with whom contracts are fulfilled must be deleted. This operation
ensures that the customer information is not disclosed, and decreases the redundant information
in the database.
Prerequisite
Procedure
1 Choose Service > Customer Management from the Main Menu to display the Customer
Management dialog box.
2 Select the customer to be deleted. Click Delete. In the Warning dialog box, select Yes.
NOTE
Deleting the customer does not affect the information of the trails and alarms that are related to the customer.
3 The Operation Result prompt box is displayed. Click Close.
----End
13.10 Viewing the Customers Affected by an Alarm

When an alarm occurs on a service, you need to query the customers that are affected by the
alarm. According to the query result, you can determine whether to notify the customer of the
alarm.
Prerequisite
Procedure
1 Choose Fault > Browse Current Alarm or Fault > Browse History Alarm from the main
menu. The window of viewing alarms is displayed.
2 Right-click an alarm and choose Alarm Affect Object > Customers of Transport Service or
Alarm Affect Object > Customers of IP Service from the shortcut menu.
NOTE
You can query the customers affected by only the alarms that occur on trails.
3 In the Customer Management window, view the information about the customers that are
affected by the alarm.
----End

13.11 Specifying the Customer of a Service

When creating and modifying a service, you need to specify the customer that the service belongs
to. This can facilitate the trail management.
Prerequisite
Context
l For WDM trails, you can not specify the customers of OTS, OMS, OSC level trails.
l For SDH trails, you can not specify the customers of VC4 server trails.
Procedure
1 Choose Service > SDH Trail > Manage SDH Trail, Service > WDM Trail > Manage WDM
Trail, Service > MSTP Trail > Manage ATM Trail, Service > MSTP Trail > Manage
Ethernet Trail, Service > L3VPN Service > Manage L3VPN Service, Service > VPLS
Service > Manage VPLS Service, Service > E-AGGR Service > Manage E-AGGR
Service, or Service > PWE3 Service > Manage PWE3 Service from the main menu.
2 Right-click a trail and choose Details from the shortcut menu.
3 Select the required customer for the trail in the drop-down list.
4 Click OK.
----End
13.12 Enabling VCN Status of a Customer

A customer can view relevant trails only when the VCN function is enabled.
Prerequisite
Procedure
1 Choose Service > Customer Management from the main menu.
The information about all customers is displayed in the Customer Management window.
2 Optional: If the customer information is changed, you can click Refresh to browse the changed
customer information.
3 In the customer list, select a customer whose VCN Status is Disable, double-click the VCN
Status field, and then choose Enable from the shortcut menu.
4 Click Apply.
5 The Operation Result dialog box is displayed. Click Close.

You can create users of the customer in the VCN network system and the created users have the
rights to view the information about all trails of the customer.
----End


OG For Common Features - (V100R002C01 - 03)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OG For Common Features - (V100R002C01 - 03)

Uploaded by

Copyright:

Available Formats

iManager U2000 Unified Network Management

Operation Guide for Common

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2010-11-19) Huawei Proprietary and Confidential i

About This Document

Product Name Version

iManager U2000 V100R002C01

Indicates a hazard with a high level of risk

Indicates a hazard with a medium or low level

Issue 03 (2010-11-19) Huawei Proprietary and Confidential iii

Indicates a potentially hazardous situation

NOTE Provides additional information to emphasize

Boldface The keywords of a command line are in

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square

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

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

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

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

iv Huawei Proprietary and Confidential Issue 03 (2010-11-19)

Boldface Buttons, menus, parameters, tabs, window,

> Multi-level menus are in boldface and

Changes in Issue 03 (2010-11-19) Based on Product Version V100R002C01

Changes in Issue 02 (2010-09-24) Based on Product Version V100R002C01

Changes in Issue 01 (2010-08-16) Based on Product Version V100R002C01

Issue 03 (2010-11-19) Huawei Proprietary and Confidential v

About This Document...................................................................................................................iii

Issue 03 (2010-11-19) Huawei Proprietary and Confidential vii

1.7.2 Setting or Modifying Character Sets in Batches..................................................................................1-43

viii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

1.10.1 Setting the Font Size........................................................................................................................1-103

2 Network Management Process................................................................................................2-1

Issue 03 (2010-11-19) Huawei Proprietary and Confidential ix

2.2 MSTP Network Management Process............................................................................................................2-4

x Huawei Proprietary and Confidential Issue 03 (2010-11-19)

3.8.3 Modifying an Operation Set.................................................................................................................3-38

Issue 03 (2010-11-19) Huawei Proprietary and Confidential xi

3.16.2 Dumping Information About Change Audit......................................................................................3-74

xii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

4.9.2 Configuring the Information Center on the NEs..................................................................................4-29

Issue 03 (2010-11-19) Huawei Proprietary and Confidential xiii

5.5.9 Creating Virtual NEs............................................................................................................................5-38

xiv Huawei Proprietary and Confidential Issue 03 (2010-11-19)

5.11 Setting the NE Maintenance Information....................................................................................................5-80

6 Time Localization Management..............................................................................................6-1

Issue 03 (2010-11-19) Huawei Proprietary and Confidential xv

7.5 Synchronizing Alarms...................................................................................................................................7-36

xvi Huawei Proprietary and Confidential Issue 03 (2010-11-19)

7.9.12 Suppressing Alarms............................................................................................................................7-75

Issue 03 (2010-11-19) Huawei Proprietary and Confidential xvii

7.14.6 Setting an Intermittent Alarm or Repeat Event Analysis Rule........................................................7-117

xviii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

7.16.10 Enabling the Alarm Monitoring for Lower Order Paths................................................................7-152

Issue 03 (2010-11-19) Huawei Proprietary and Confidential xix

8.8.1 Setting the Performance Reporting Status for a Single NE.................................................................8-38

xx Huawei Proprietary and Confidential Issue 03 (2010-11-19)

9.1.2 Installing a Rack or an NMS Server in a Telecommunications Room..................................................9-5

Issue 03 (2010-11-19) Huawei Proprietary and Confidential xxi

9.8 Collecting Statistics on the Slot Usage......................................................................................................... 9-30

xxii Huawei Proprietary and Confidential Issue 03 (2010-11-19)

9.16.3 Collecting Statistics on SDH Tributary Port Resources.....................................................................9-60