Operation Guide For Common Features

OptiX iManager T2000
V200R007C03
Operation Guide for Common Features
Issue 01
Date 2009-06-30
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

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

1 T2000 V200R007C03 Overview................................................................................................1-1
1.1 Network Position.............................................................................................................................................1-2
1.2 Product Characteristics....................................................................................................................................1-3
1.3 Manageable Equipment...................................................................................................................................1-3
1.4 What's New in T2000 V200R007C03.............................................................................................................1-7
1.5 Updates in the T2000 V200R007C03 for SDH Equipment............................................................................1-9
1.6 Updates in the T2000 V200R007C03 for WDM Equipment........................................................................1-10
1.7 Updates in the T2000 V200R007C03 for Submarine Line Equipment........................................................1-13
1.8 Updates in the T2000 V200R007C03 for RTN Equipment..........................................................................1-13
1.9 Updates in the T2000 V200R007C03 for PTN Equipment..........................................................................1-16
2 Getting Started............................................................................................................................2-1
2.1 T2000 Process.................................................................................................................................................2-3
2.2 Starting or Shutting Down the T2000.............................................................................................................2-5
2.2.1 Starting the Computer............................................................................................................................2-6
2.2.2 Starting the T2000 Server......................................................................................................................2-7
2.2.3 Viewing the T2000 Process Status.........................................................................................................2-8
2.2.4 Logging In to the T2000 Client..............................................................................................................2-9
2.2.5 Changing the Login Server..................................................................................................................2-11
2.2.6 Exiting a T2000 Client.........................................................................................................................2-11
2.2.7 Shutting Down the T2000 Server.........................................................................................................2-11
2.2.8 Shutting Down the Computer...............................................................................................................2-12
2.3 Changing the Current User Password...........................................................................................................2-13
2.4 Setting Client Display...................................................................................................................................2-14
2.4.1 Setting the Main Frame Title...............................................................................................................2-14
2.4.2 Setting Output Display.........................................................................................................................2-14
2.4.3 Setting Topology Display Style...........................................................................................................2-15
2.4.4 Setting the Topology Background........................................................................................................2-16
2.4.5 Setting Alarm Colors............................................................................................................................2-17
2.4.6 Setting Alarm Local Display Properties...............................................................................................2-17
2.5 Customizing the Client Time Format............................................................................................................2-18
2.5.1 Setting the Time Format.......................................................................................................................2-18
Issue 01 (2009-06-30) Huawei Proprietary and Confidential i

Contents Operation Guide for Common Features
2.5.2 Setting the Date Format........................................................................................................................2-19

2.6 Locking the Client.........................................................................................................................................2-20
2.6.1 Locking the Client Automatically........................................................................................................2-20
2.6.2 Locking the Client Manually................................................................................................................2-21
2.7 Unlocking the Client.....................................................................................................................................2-21
2.8 Obtaining and Installing a T2000 License....................................................................................................2-21
2.8.1 About the T2000 License.....................................................................................................................2-22
2.8.2 Obtaining a T2000 License..................................................................................................................2-22
2.8.3 Installing a T2000 License...................................................................................................................2-24
2.8.4 Changing the License...........................................................................................................................2-24
2.8.5 How to Correctly Use a License..........................................................................................................2-28
2.9 Starting the Web Client.................................................................................................................................2-29
2.10 T2000 Main Window..................................................................................................................................2-30
2.10.1 Main Topology...................................................................................................................................2-31
2.10.2 NE Explorer........................................................................................................................................2-32
2.10.3 Clock View.........................................................................................................................................2-34
2.10.4 SDH NE Panel....................................................................................................................................2-35
2.10.5 RTN NE Panel....................................................................................................................................2-38
2.10.6 WDM NE Panel.................................................................................................................................2-40
2.10.7 PTN NE Panel....................................................................................................................................2-43
2.10.8 Browse Alarm and Event Window.....................................................................................................2-45
2.10.9 Browse Performance Window...........................................................................................................2-46
2.10.10 Operation Object Status...................................................................................................................2-48
2.10.11 Key GUI Components......................................................................................................................2-50
2.10.12 Frequently Used Buttons..................................................................................................................2-51
2.10.13 Shortcut Icon....................................................................................................................................2-53
2.10.14 Common Shortcut Keys...................................................................................................................2-57
2.11 Menu Description........................................................................................................................................2-58
2.11.1 File Menu...........................................................................................................................................2-59
2.11.2 Edit Menu...........................................................................................................................................2-60
2.11.3 View Menu.........................................................................................................................................2-61
2.11.4 Configuration Menu...........................................................................................................................2-62
2.11.5 Protection Subnet Menu.....................................................................................................................2-65
2.11.6 Clock View Menu..............................................................................................................................2-67
2.11.7 Fault Menu.........................................................................................................................................2-68
2.11.8 Performance Menu.............................................................................................................................2-70
2.11.9 Trail Menu..........................................................................................................................................2-71
2.11.10 Report Menu.....................................................................................................................................2-75
2.11.11 System Menu....................................................................................................................................2-76
2.11.12 Data Center Menu............................................................................................................................2-79
2.11.13 Window Menu..................................................................................................................................2-79
2.11.14 Help Menu........................................................................................................................................2-80
ii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

2.12 Custom View...............................................................................................................................................2-80

2.12.1 Creating Custom Views.....................................................................................................................2-81
2.12.2 Setting Startup Subnet........................................................................................................................2-81
2.13 Customizing Parameter Display..................................................................................................................2-82
2.14 Customizing Naming Rule..........................................................................................................................2-83
2.15 Copying Table Text Quickly.......................................................................................................................2-85
2.16 Filtering Operation Objects in a View........................................................................................................2-85
2.17 Moving Operation Objects..........................................................................................................................2-86
2.18 Searching for NEs in a View.......................................................................................................................2-87
2.19 Counting the Number of NEs......................................................................................................................2-87
2.20 Setting Parameters in the List......................................................................................................................2-88
2.21 Operation Precautions.................................................................................................................................2-89
2.22 Rules of Entering Information on User Interface........................................................................................2-89
3 Security Management................................................................................................................3-1
3.1 Security Management Strategy.......................................................................................................................3-3
3.1.1 Operating System Security Policy..........................................................................................................3-3
3.1.2 Database Security Policy........................................................................................................................3-4
3.1.3 Network Security Isolation Policy.........................................................................................................3-4
3.1.4 T2000 User Security Policy...................................................................................................................3-5
3.1.5 Log Management Policy........................................................................................................................3-7
3.1.6 NE Security............................................................................................................................................3-8
3.2 Users and Rights............................................................................................................................................3-10
3.2.1 OS User................................................................................................................................................3-10
3.2.2 Database Users and Authorities...........................................................................................................3-11
3.2.3 NMS Users and Rights.........................................................................................................................3-11
3.2.4 NE Users and Authorities.....................................................................................................................3-12
3.2.5 Concepts Related to the T2000 Users..................................................................................................3-12
3.2.6 T2000 User Rights Assignment Policies..............................................................................................3-14
3.3 Security Management Processes...................................................................................................................3-15
3.4 Managing SolarisSUSE Linux OS Security..................................................................................................3-17
3.4.1 Changing the Password of User root....................................................................................................3-18
3.4.2 Changing the Password of User sybase................................................................................................3-18
3.4.3 Changing the Password of User t2000.................................................................................................3-19
3.4.4 Removing Redundant Hosts Configuration Files.................................................................................3-19
3.4.5 Inhibitting User sybase from Using FTP..............................................................................................3-20
3.5 Managing Database Users.............................................................................................................................3-20
3.5.1 Changing the Password of sa...............................................................................................................3-20
3.5.2 Changing the Password of T2000user..................................................................................................3-21
3.6 Setting the Security Access of the T2000.....................................................................................................3-23
3.6.1 Setting SSL Protocol Communication Between Server and Client.....................................................3-23
3.6.2 Setting the System ACL of T2000.......................................................................................................3-25
3.7 Setting Security Policy for a T2000 User......................................................................................................3-26
Issue 01 (2009-06-30) Huawei Proprietary and Confidential iii

3.7.1 Setting the Password Template............................................................................................................3-27

3.7.2 Setting the Password Reuse Frequency................................................................................................3-29
3.7.3 Configuring the Warning Screen for Login.........................................................................................3-29
3.7.4 Configuring the Weakness Password Dictionary.................................................................................3-30
3.7.5 Modifying the T2000 User Validity.....................................................................................................3-31
3.7.6 Modifying the T2000User Password Validity.....................................................................................3-32
3.7.7 Setting the User Lockout Duration.......................................................................................................3-33
3.7.8 Unlocking a T2000 User......................................................................................................................3-34
3.7.9 Initializing the T2000 User Password..................................................................................................3-35
3.8 Managing T2000 User Groups......................................................................................................................3-36
3.8.1 Creating User Groups...........................................................................................................................3-36
3.8.2 Specifying Members of a User Group..................................................................................................3-37
3.8.3 Assigning a Managed Domain to a User Group..................................................................................3-38
3.8.4 Assigning Operation Authorities for User Groups...............................................................................3-39
3.8.5 Setting a User Group Administrator.....................................................................................................3-40
3.8.6 Modifying a User Group......................................................................................................................3-40
3.8.7 Deleting a User Group..........................................................................................................................3-41
3.9 Managing NM Users.....................................................................................................................................3-42
3.9.1 Creating T2000 Users...........................................................................................................................3-42
3.9.2 Changing the User Group That an T2000 User Belongs To................................................................3-44
3.9.3 Assigning a Managed Domain to a T2000 User..................................................................................3-44
3.9.4 Assigning Operation Authorities for T2000 Users..............................................................................3-46
3.9.5 Setting the Access Control List of T2000 Users..................................................................................3-48
3.9.6 Modifying the Properties of an T2000 User.........................................................................................3-49
3.9.7 Changing the NM User Password........................................................................................................3-50
3.9.8 Deleting an NM User...........................................................................................................................3-51
3.9.9 Example: Creating a T2000 User.........................................................................................................3-51
3.10 Managing T2000 Operation Sets.................................................................................................................3-55
3.10.1 Operation Set Types...........................................................................................................................3-55
3.10.2 Creating an Operation Set..................................................................................................................3-57
3.10.3 Modifying the Service Objects of an Operation Set...........................................................................3-59
3.10.4 Deleting an Operation Set..................................................................................................................3-59
3.11 Managing T2000 Equipment Sets...............................................................................................................3-60
3.11.1 Creating an Equipment Set.................................................................................................................3-61
3.11.2 Modifying a Device Set......................................................................................................................3-61
3.11.3 Modifying the Service Objects of a Device Set.................................................................................3-62
3.11.4 Deleting a Device Set.........................................................................................................................3-62
3.12 Managing T2000 Login...............................................................................................................................3-63
3.12.1 Locking the T2000 Client Screen.......................................................................................................3-63
3.12.2 Switching a Logged-In NM User.......................................................................................................3-64
3.12.3 Forcing an NM User to Log Out of the T2000..................................................................................3-64
3.12.4 Switching to the Single User Mode....................................................................................................3-65
iv Huawei Proprietary and Confidential Issue 01 (2009-06-30)

3.12.5 Setting Automatical Log-In for T2000 Users ...................................................................................3-65

3.13 Managing the Remote Maintenance User...................................................................................................3-66
3.13.1 Enabling a Remote Maintenance User...............................................................................................3-66
3.13.2 Setting the Remote Maintenance User Authority..............................................................................3-67
3.13.3 Setting the Remote Maintenance User Validity.................................................................................3-68
3.14 Setting the Security Access of an NE..........................................................................................................3-69
3.14.1 Controlling Communication Between NE and T2000 Through Ethernet Port..................................3-70
3.14.2 Controlling Communication Between NE and T2000 Through a Serial Port....................................3-70
3.14.3 Setting the NE OAM Access..............................................................................................................3-71
3.14.4 Setting the NE COM Access..............................................................................................................3-72
3.14.5 Controlling Communication Between NE and LCT..........................................................................3-73
3.15 Setting the NE ACL....................................................................................................................................3-74
3.15.1 ACL....................................................................................................................................................3-74
3.15.2 Setting Basic ACL Rules....................................................................................................................3-75
3.15.3 Setting the Advanced ACL Rules......................................................................................................3-75
3.16 Managing NE Users....................................................................................................................................3-76
3.16.1 Creating an NE User..........................................................................................................................3-76
3.16.2 Changing the NE User Password.......................................................................................................3-78
3.16.3 Querying the NE User Information....................................................................................................3-79
3.16.4 Querying NE Security Parameters.....................................................................................................3-79
3.16.5 Deleting NE Users..............................................................................................................................3-80
3.16.6 Querying NE User Groups.................................................................................................................3-80
3.17 Managing NE Login....................................................................................................................................3-81
3.17.1 Locking Out NE Login.......................................................................................................................3-81
3.17.2 Locking Out NE Settings...................................................................................................................3-82
3.17.3 Switching a Logged-In NE User........................................................................................................3-82
3.17.4 Switching a DC User..........................................................................................................................3-83
3.17.5 Forcing an NE User to Log Out of the NE.........................................................................................3-84
3.17.6 Setting NE Login Prompt Message....................................................................................................3-84
4 Log Management........................................................................................................................ 4-1

4.1 Log Types........................................................................................................................................................4-2
4.1.1 T2000 Security Log................................................................................................................................4-2
4.1.2 T2000 Operation Log.............................................................................................................................4-2
4.1.3 NE Security Log.....................................................................................................................................4-3
4.2 Managing T2000 Security Log.......................................................................................................................4-3
4.2.1 Browsing Security Logs.........................................................................................................................4-4
4.2.2 Periodically dump security logs.............................................................................................................4-5
4.2.3 Setting the Overflow Dump for Security Logs......................................................................................4-5
4.2.4 Dumping Security Logs Manually.........................................................................................................4-6
4.3 Managing Operation Logs...............................................................................................................................4-7
4.3.1 Browsing Operation Logs......................................................................................................................4-8
4.3.2 Periodically Dumping Operation Logs..................................................................................................4-9
Issue 01 (2009-06-30) Huawei Proprietary and Confidential v

4.3.3 Setting the Overflow Dump for Operation Logs....................................................................................4-9

4.3.4 Dumping Operation Logs Manually....................................................................................................4-11
4.4 Forwarding the T2000 Logs to the Syslog Server.........................................................................................4-12
4.5 Browse NE Security Logs.............................................................................................................................4-12
4.6 Transferring NE Logs to Log Servers...........................................................................................................4-13
4.6.1 Syslog Service......................................................................................................................................4-13
4.6.2 Configuring the Syslog Server.............................................................................................................4-17
4.6.3 Configuring the Syslog GNE...............................................................................................................4-17
4.6.4 Configuring the Syslog Type and Severity..........................................................................................4-18
4.6.5 Starting the Syslog Service..................................................................................................................4-18
5 Topology Management.............................................................................................................5-1
5.1 Basic Concepts................................................................................................................................................5-3
5.1.1 Topology Management Functions..........................................................................................................5-3
5.1.2 Topology Objects...................................................................................................................................5-4
5.1.3 Optical NE..............................................................................................................................................5-4
5.1.4 GNE and Non-Gateway NE...................................................................................................................5-4
5.1.5 Virtual NE..............................................................................................................................................5-5
5.1.6 Fiber Types.............................................................................................................................................5-5
5.1.7 Fiber/Cable Pipe.....................................................................................................................................5-6
5.1.8 Flow of Constructing the Network Topology........................................................................................5-6
5.2 Creating NEs...................................................................................................................................................5-7
5.2.1 Creating NEs in Batches........................................................................................................................ 5-8
5.2.2 Creating a Single NE............................................................................................................................5-10
5.2.3 Creating Optical NEs...........................................................................................................................5-12
5.2.4 Creating Virtual NE.............................................................................................................................5-13
5.3 Configuring the NE Data...............................................................................................................................5-14
5.3.1 Configuring the NE Data Manually.....................................................................................................5-14
5.3.2 Replicating the NE Data.......................................................................................................................5-16
5.3.3 Uploading the NE Data........................................................................................................................5-18
5.3.4 Configuring Virtual NE Data...............................................................................................................5-19
5.4 Configuring Master/Slave Subrack...............................................................................................................5-20
5.4.1 Master/Slave Subrack Configuration...................................................................................................5-21
5.4.2 Adding a Slave Subrack.......................................................................................................................5-23
5.4.3 Modifying Subrack Name....................................................................................................................5-23
5.4.4 Querying the Status of a Slave Subrack...............................................................................................5-24
5.4.5 Deleting a Slave Subrack.....................................................................................................................5-25
5.5 Adding Boards and Ports...............................................................................................................................5-25
5.5.1 Adding Boards......................................................................................................................................5-26
5.5.2 Adding Sub-Boards..............................................................................................................................5-27
5.5.3 Adding Dynamic Ports.........................................................................................................................5-27
5.5.4 Adding Client Side Ports......................................................................................................................5-28
5.5.5 Adding a Line-Side Port.......................................................................................................................5-29
vi Huawei Proprietary and Confidential Issue 01 (2009-06-30)

5.6 Query Path Status of the Board.....................................................................................................................5-30

5.7 Creating Links...............................................................................................................................................5-30
5.7.1 Creating Fibers Automatically.............................................................................................................5-32
5.7.2 Creating Fibers for SDH Equipment Manually....................................................................................5-33
5.7.3 Creating Fibers for PTN Equipment Manually....................................................................................5-34
5.7.4 Creating Fibers in the Synchronization Mode......................................................................................5-35
5.7.5 Creating Fiber Connections in Graphic Mode.....................................................................................5-36
5.7.6 Creating Fiber Connections in List Mode............................................................................................5-40
5.7.7 Creating Fibers Between an OTU Board and a Mux/Demux Board in Batches..................................5-41
5.7.8 Automatically Creating Radio Links....................................................................................................5-41
5.7.9 Manually Creating Radio Links...........................................................................................................5-42
5.7.10 Creating DCN Communication Cable................................................................................................5-43
5.7.11 Creating Virtual Fibers.......................................................................................................................5-44
5.7.12 Restoring the Fiber Connection..........................................................................................................5-45
5.7.13 Creating a Fiber/Cable Pipe...............................................................................................................5-45
5.7.14 Adding a Fiber/Cable into a Fiber/Cable Pipe...................................................................................5-46
5.8 Browsing Fiber/Cable...................................................................................................................................5-47
5.8.1 Querying Fiber/Cable Information.......................................................................................................5-48
5.8.2 Querying Relevant Trails of a Fiber/Cable..........................................................................................5-48
5.8.3 Querying Relevant Optical Power of a Fiber/Cable.............................................................................5-49
5.8.4 Querying a Fiber/Cable Pipe................................................................................................................5-49
5.8.5 Querying the Fiber/Cable Pipe Associated to a Fiber/Cable................................................................5-50
5.8.6 Querying the Physical Fiber Connection Between NEs.......................................................................5-50
5.9 Creating a Topology Subnet..........................................................................................................................5-51
5.10 Adjusting Topology Objects.......................................................................................................................5-52
5.10.1 Balancing Load of the NE Explorer Process......................................................................................5-54
5.10.2 Modifying the NE ID.........................................................................................................................5-55
5.10.3 Modifying the NE Name....................................................................................................................5-56
5.10.4 Modifying the NE IP Address............................................................................................................5-57
5.10.5 Modifying the Optical NE Name.......................................................................................................5-58
5.10.6 Adjusting Optical NE Resource.........................................................................................................5-58
5.10.7 Modifying the Status of a Preconfigured NE.....................................................................................5-59
5.10.8 Modifying the NM Name...................................................................................................................5-59
5.10.9 Modifying the Port Type for a Board.................................................................................................5-60
5.10.10 Modifying the Client-Side Port Type...............................................................................................5-61
5.10.11 Modifying the Type of a Line-Side Port..........................................................................................5-62
5.10.12 Modifying Fiber/Cable Information.................................................................................................5-63
5.10.13 Modifying the Information About a Fiber/Cable Pipe.....................................................................5-64
5.10.14 Removing a Fiber/Cable from a Fiber/Cable Pipe...........................................................................5-64
5.10.15 Naming a Fiber/Cable......................................................................................................................5-65
5.10.16 Copying Topology Objects..............................................................................................................5-65
5.10.17 Moving Topology Objects...............................................................................................................5-66
Issue 01 (2009-06-30) Huawei Proprietary and Confidential vii

5.11 Deleting Topology Objects.........................................................................................................................5-66

5.11.1 Deleting Topology Subnets................................................................................................................5-67
5.11.2 Deleting Boards..................................................................................................................................5-67
5.11.3 Deleting Sub-boards...........................................................................................................................5-68
5.11.4 Deleting Fibers...................................................................................................................................5-68
5.11.5 Deleting a Fiber/Cable Pipe...............................................................................................................5-69
5.11.6 Deleting NEs......................................................................................................................................5-69
5.11.7 Deleting an Optical NE......................................................................................................................5-70
6 Time Localization Management..............................................................................................6-1

6.1 Time Localization...........................................................................................................................................6-2
6.2 Setting Time Localization on the T2000.........................................................................................................6-2
6.2.1 Setting the Time Display Format...........................................................................................................6-3
6.2.2 Setting the Time Localization Mode......................................................................................................6-3
6.3 Setting Time Localization on NEs..................................................................................................................6-3
6.3.1 Setting a Time Zone for an NE..............................................................................................................6-4
6.3.2 Setting DST on NEs...............................................................................................................................6-4
7 Alarm Management...................................................................................................................7-1
7.1 Basic Concepts................................................................................................................................................7-4
7.1.1 Alarm Reporting Process.......................................................................................................................7-5
7.1.2 Alarm Handling Procedure.....................................................................................................................7-7
7.1.3 Alarm template.......................................................................................................................................7-9
7.1.4 Alarm Viewing Operations..................................................................................................................7-10
7.1.5 Alarm Setting Operations.....................................................................................................................7-12
7.1.6 Alarm Correlation Analysis.................................................................................................................7-16
7.1.7 Alarm Notification...............................................................................................................................7-19
7.1.8 Alarm Severity.....................................................................................................................................7-21
7.1.9 Alarm Status.........................................................................................................................................7-22
7.1.10 Alarm Category..................................................................................................................................7-23
7.1.11 Current Alarms and History Alarms..................................................................................................7-23
7.1.12 Alarm Statistics..................................................................................................................................7-24
7.1.13 Alarm Dumping..................................................................................................................................7-24
7.2 Customizing Alarm Template.......................................................................................................................7-25
7.2.1 Creating an Alarm or Event Browse Template....................................................................................7-25
7.2.2 Exporting or Importing an Alarm Template........................................................................................7-27
7.2.3 Creating the Alarm Statistics Template...............................................................................................7-28
7.2.4 Setting the Startup Template................................................................................................................7-30
7.2.5 Customizing Alarm Attribute Template...............................................................................................7-31
7.3 Synchronizing Alarms...................................................................................................................................7-32
7.3.1 Synchronizing Networkwide Current Alarms......................................................................................7-32
7.3.2 Synchronizing the Current Alarms for an NE......................................................................................7-33
7.3.3 Synchronizing the Current Alarms for the T2000................................................................................7-33
7.3.4 Setting Alarm Auto Synchronization...................................................................................................7-33
viii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

7.4 Viewing Alarms............................................................................................................................................7-34

7.4.1 Monitoring Alarms Through the Topology View................................................................................7-36
7.4.2 Monitoring Alarms Through the Alarm Panel.....................................................................................7-36
7.4.3 Viewing Current Alarms......................................................................................................................7-37
7.4.4 Viewing History Alarms......................................................................................................................7-38
7.4.5 Viewing Abnormal Events...................................................................................................................7-39
7.4.6 Viewing the Statistics of Alarms..........................................................................................................7-39
7.4.7 Viewing Correlative Alarms................................................................................................................7-40
7.4.8 Viewing Current Alarms of a Fiber/Cable...........................................................................................7-40
7.4.9 Viewing History Alarms of a Fiber/Cable...........................................................................................7-41
7.4.10 Brows Remote Notification Logs.......................................................................................................7-42
7.4.11 Managing Networkwide SDH Alarm Trails in Real Time.................................................................7-42
7.4.12 Managing Networkwide WDM Alarm Trails in Real Time..............................................................7-42
7.4.13 Viewing Current Alarms of an SDH Trail.........................................................................................7-43
7.4.14 Viewing History Alarms of an SDH Trail.........................................................................................7-45
7.4.15 Viewing Current Alarms of a WDM Trail.........................................................................................7-45
7.4.16 Viewing History Alarms of a WDM Trail.........................................................................................7-46
7.4.17 Viewing Current Alarms of a Trunk Link..........................................................................................7-46
7.4.18 Viewing History Alarms of a Trunk Link..........................................................................................7-47
7.4.19 Viewing Current Alarms of an Ethernet Trail....................................................................................7-48
7.4.20 Viewing History Alarms of an Ethernet Trail....................................................................................7-49
7.5 Handling an Alarm........................................................................................................................................7-49
7.5.1 Browsing Current Alarms....................................................................................................................7-50
7.5.2 Viewing the Alarm Details...................................................................................................................7-51
7.5.3 Checking Alarms..................................................................................................................................7-51
7.5.4 Acknowledging an Alarm....................................................................................................................7-52
7.5.5 Position an Alarm on Topology Object................................................................................................7-52
7.5.6 Querying Device Maintenance Information.........................................................................................7-53
7.5.7 Deleting Alarms...................................................................................................................................7-54
7.5.8 Example of Alarm Handling................................................................................................................7-55
7.6 Setting the Alarm Auto Processing...............................................................................................................7-55
7.6.1 Setting the Alarm Auto Acknowledgement.........................................................................................7-56
7.6.2 Setting Alarm Auto Synchronization...................................................................................................7-56
7.7 Suppressing Alarms.......................................................................................................................................7-57
7.7.1 Suppressing NE Alarms.......................................................................................................................7-57
7.7.2 Suppressing Alarms of a Board or Port................................................................................................7-58
7.7.3 Suppressing the Alarms on an ATM Connection.................................................................................7-59
7.7.4 Checking Path Alarm Suppression Status............................................................................................7-59
7.8 Setting Alarm Reversion...............................................................................................................................7-61
7.8.1 Setting Alarm Reversion for a Specified Port......................................................................................7-61
7.8.2 Setting Alarm Reversion for an SDH Trail..........................................................................................7-62
7.8.3 Checking Path Alarm Reversion Status...............................................................................................7-63
Issue 01 (2009-06-30) Huawei Proprietary and Confidential ix

7.9 Filtering Alarms Raised on T2000................................................................................................................7-64

7.10 Filtering Alarms Raised on NE...................................................................................................................7-64
7.11 Setting Automatic Alarm Reporting...........................................................................................................7-65
7.11.1 Setting Automatic Reporting Status for Alarms of an NE.................................................................7-65
7.11.2 Setting Automatic Reporting Status for Alarms of a Board...............................................................7-66
7.12 Setting the Types of Lower Order Services in the VC4 Path......................................................................7-66
7.13 Monitoring the Alarms and Performance of Lower Order Services in the VC4 Path.................................7-67
7.14 Setting the Insertion Mode for Channels Not Configured with Services....................................................7-68
7.15 Setting Audible and Visual Alarm Notification..........................................................................................7-69
7.15.1 Setting Alarm Sounds.........................................................................................................................7-69
7.15.2 Setting Alarm Colors..........................................................................................................................7-70
7.15.3 Setting the Alarm Panel Style............................................................................................................7-71
7.15.4 Setting Audible and Visual Alarm Indication in the Alarm Box.......................................................7-72
7.15.5 Clearing the Audible and Visual Alarm Indication of an NE Cabinet Temporarily..........................7-73
7.15.6 Clearing the Audible and Visual Alarm Indication of an NE Cabinet Permanently..........................7-73
7.16 Setting Alarm Remote Notification.............................................................................................................7-74
7.16.1 Forwarding Alarms to Email Automatically......................................................................................7-74
7.16.2 Forwarding Alarm to Mobile Phone Automatically..........................................................................7-75
7.17 Modifying Alarm Severity..........................................................................................................................7-76
7.17.1 Changing the T2000 Alarm Severity.................................................................................................7-76
7.17.2 Modifying the Alarm Severity for an NE...........................................................................................7-77
7.17.3 Modifying the Alarm Severity for a Board........................................................................................7-77
7.18 Analyzing the Root Alarm of a Fault..........................................................................................................7-78
7.18.1 Analyzing Root Alarms Automatically..............................................................................................7-78
7.18.2 Performing Alarm Correlation Analysis............................................................................................7-79
7.19 Specifying the Port QoS Alarm...................................................................................................................7-80
7.19.1 Specifying Bit Error Alarm Threshold...............................................................................................7-80
7.19.2 Enabling AIS Insertion for a Specified Channel................................................................................7-81
7.19.3 Enabling UNEQ Insertion for a Specified Path.................................................................................7-81
7.20 Configuring Alarm Insertion.......................................................................................................................7-82
7.20.1 Inserting an Alarm at a Specified Path...............................................................................................7-82
7.20.2 Inserting an Alarm on an SDH Trail..................................................................................................7-83
7.20.3 Checking Path Alarm Insertion Status...............................................................................................7-83
7.21 Inserting a Maintenance Signal to the ODU Layer.....................................................................................7-85
7.22 Setting NE Alarm Attributes.......................................................................................................................7-85
7.22.1 Setting the Saving Mode for NE alarms.............................................................................................7-86
7.22.2 Setting the Enabling Status of NE Alarm Correlation Suppression...................................................7-86
7.22.3 Querying NE Alarm Correlation Rules..............................................................................................7-87
7.22.4 Setting NE Alarm Delay....................................................................................................................7-87
7.23 Enabling the Alarm Monitoring for Lower Order Paths.............................................................................7-88
7.24 Dumping Alarms.........................................................................................................................................7-89
7.24.1 Dumping Alarms Manually................................................................................................................7-89
x Huawei Proprietary and Confidential Issue 01 (2009-06-30)

7.24.2 Dumping Alarms Automatically........................................................................................................7-90

7.25 Deleting History Alarms.............................................................................................................................7-91
7.26 Diagnosing Faults........................................................................................................................................7-92
7.26.1 Creating Fault Diagnosis Rules..........................................................................................................7-92
7.26.2 Starting the Fault Diagnosis Wizard..................................................................................................7-92
7.27 Configuring the Suppression of Power Status Alarm.................................................................................7-93
8 Performance Management........................................................................................................8-1
8.1 Basic Concept..................................................................................................................................................8-3
8.1.1 Performance Event Type........................................................................................................................8-3
8.1.2 Performance Reporting Process.............................................................................................................8-4
8.1.3 Performance Monitoring Settings.......................................................................................................... 8-5
8.1.4 Operation of Viewing Performance Data...............................................................................................8-6
8.1.5 RMON Performance.............................................................................................................................. 8-7
8.1.6 Performance Threshold..........................................................................................................................8-7
8.1.6.1 Current Performance and History Performance..................................................................................8-8
8.1.7 Performance Dumping........................................................................................................................... 8-8
8.1.8 Performance Analysis............................................................................................................................ 8-9
8.2 Viewing Performance Data.............................................................................................................................8-9
8.2.1 Viewing Current Performance Data.....................................................................................................8-10
8.2.1.1 Viewing History Performance Data..................................................................................................8-11
8.2.2 Viewing UAT Records.........................................................................................................................8-12
8.2.3 Viewing Performance Threshold Crossings.........................................................................................8-13
8.2.4 Viewing Current Performance Data of an Ethernet Port......................................................................8-14
8.2.5 Viewing History Performance Data of an Ethernet Port......................................................................8-15
8.2.6 Viewing Current Performance Data of an ATM Port..........................................................................8-15
8.2.7 Viewing History Performance Data of an ATM Port...........................................................................8-16
8.2.8 Viewing the Current Performance Data of an SDH Trail....................................................................8-16
8.2.9 Viewing History Performance Data of an SDH Trail..........................................................................8-17
8.2.10 Querying Current Performance of WDM Trails................................................................................8-17
8.2.11 Browsing the History Performance of WDM Trails..........................................................................8-18
8.2.12 Browsing the Performance of an Ethernet Trail.................................................................................8-18
8.2.13 Querying the NE Temperature...........................................................................................................8-19
8.3 Viewing RMON Performance Data..............................................................................................................8-20
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-25
8.4.2 Setting the Lower Order Performance Threshold................................................................................8-26
8.4.3 Setting the Lower Order Performance Monitoring Status....................................................................8-27
8.4.4 Viewing Current Lower Order Performance Data...............................................................................8-28
8.4.5 Viewing History Lower Order Performance Data...............................................................................8-29
8.4.6 Viewing UAT Records for a Lower Order Service..............................................................................8-30
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xi

8.4.7 Viewing Lower Order Performance Threshold-Crossing Records......................................................8-31

8.5 Creating Performance Threshold Templates.................................................................................................8-33
8.6 Setting the Board Performance Threshold....................................................................................................8-33
8.7 Setting Performance Monitoring Parameters................................................................................................8-34
8.7.1 Setting Performance Monitoring Parameters of an NE........................................................................8-35
8.7.2 Setting IP Performance Monitoring Parameters of an NE...................................................................8-36
8.7.3 Setting ATM Performance Monitoring Parameters of an NE..............................................................8-37
8.7.4 Setting Performance Monitoring Parameters of a Board.....................................................................8-37
8.7.5 Setting IP Performance Monitoring Parameters of a Board.................................................................8-38
8.7.6 Setting ATM Performance Monitoring Parameters of an ATM Board................................................8-38
8.7.7 Setting Performance Monitoring Parameters of an SDH Trail............................................................8-39
8.7.8 Setting Performance Monitoring Parameters of an WDM Trail..........................................................8-39
8.8 Setting RMON Performance Monitoring Parameters...................................................................................8-40
8.8.1 Customizing the RMON Performance Attribute Template..................................................................8-41
8.8.2 Setting the RMON Performance Threshold.........................................................................................8-42
8.8.3 Setting the RMON History Control Group..........................................................................................8-44
8.8.4 Setting the RMON Performance Monitor Object................................................................................8-44
8.8.5 Setting the RMON Performance Monitor Status.................................................................................8-46
8.8.6 Setting Performance Monitoring Parameters of an Alarm Group for an Ethernet Port.......................8-48
8.8.7 Setting Performance Monitoring Parameters of a History Control Group for an Ethernet Port..........8-48
8.8.8 Setting the RMON Performance Monitoring Parameters for an Ethernet Port....................................8-49
8.8.9 Setting Automatic Reporting of RMON Performance Events.............................................................8-50
8.9 Dumping Performance Data..........................................................................................................................8-50
8.9.1 Dumping Performance Data Manually................................................................................................8-50
8.9.2 Dumping Performance Data Automatically.........................................................................................8-51
8.10 Collecting the History RMON Performance Data......................................................................................8-52
8.11 Periodically Collecting the Performance Data............................................................................................8-54
8.12 Analyzing History Performance Data.........................................................................................................8-55
8.13 Forecasting the Failure Time of the Laser...................................................................................................8-56
8.14 Resetting Performance Registers................................................................................................................8-56
8.14.1 Resetting Board Performance Registers.............................................................................................8-57
8.14.2 Resetting ATM Performance Registers..............................................................................................8-57
8.14.3 Resetting Ethernet Performance Registers.........................................................................................8-58
8.15 Power Consumption Management..............................................................................................................8-58
8.15.1 Querying the Power Consumption of NEs and Boards......................................................................8-58
8.16 Configuring the Q Value Performance Monitoring....................................................................................8-59
8.16.1 Querying the Current Q Value Performance......................................................................................8-59
8.16.2 Querying the History Q Value Performance......................................................................................8-60
8.16.3 Setting and Querying the Threshold of the Q Value Performance.....................................................8-61
9 Keeping Data in the T2000 Consistent with NEs.................................................................9-1

9.1 Data Management Policy of the T2000...........................................................................................................9-3
9.2 Checking Consistency of Configuration Data Between an NE and the T2000...............................................9-8
xii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

9.3 Viewing the Asynchronous Information.........................................................................................................9-9

9.4 Synchronizing the NE Configuration Data Manually.....................................................................................9-9
9.5 Uploading NE Configuration Data................................................................................................................9-10
9.6 Downloading NE Configuration Data...........................................................................................................9-10
10 Backing Up and Restoring T2000 Data..............................................................................10-1

10.1 Dump and Backup.......................................................................................................................................10-3
10.2 Script Files...................................................................................................................................................10-3
10.3 Methods of Backing Up and Restoring the T2000 Data.............................................................................10-9
10.4 Backing Up T2000 Data to a Local Server...............................................................................................10-12
10.4.1 Immediately Backing Up the T2000 MO Data ...............................................................................10-13
10.4.2 Periodically Backing Up the T2000 MO Data.................................................................................10-15
10.4.3 Immediately Backing Up All Data in the T2000 Database..............................................................10-16
10.4.4 Periodically Backing Up All Data in the T2000 Database...............................................................10-17
10.4.5 Immediately Backing Up the T2000 Data by Script........................................................................10-18
10.4.6 Periodically Backing Up the T2000 Data by Script.........................................................................10-19
10.5 Backing Up T2000 Data to a Remote Server............................................................................................10-20
10.5.1 Backing Up the T2000 MO Data Immediately................................................................................10-20
10.5.2 Backing Up the T2000 MO Data Periodically.................................................................................10-22
10.5.3 Backing Up All Data in the T2000 Database Immediately..............................................................10-23
10.5.4 Backing Up All Data in the T2000 Database in a Scheduled Manner.............................................10-25
10.5.5 Configuring a Scheduled Task.........................................................................................................10-26
10.6 Initializing the T2000 Database................................................................................................................10-28
10.7 Initializing NE Configuration Data in the T2000......................................................................................10-29
10.8 Restoring T2000 Data from a Local Server..............................................................................................10-30
10.8.1 Restoring the T2000 MO Data.........................................................................................................10-30
10.8.2 Restoring All Data in the T2000 Database.......................................................................................10-32
10.8.3 Restoring the T2000 Data by Using the Script................................................................................10-33
10.9 Restoring T2000 Data from a Remote Server...........................................................................................10-34
10.9.1 Restoring the T2000 MO Data.........................................................................................................10-35
10.9.2 Restoring All Data in the T2000 Database.......................................................................................10-37
10.10 Viewing the Status of Databases.............................................................................................................10-38
10.11 Dumping the T2000 Log Data................................................................................................................10-39
10.11.1 Dumping Alarms Manually............................................................................................................10-39
10.11.2 Dumping Alarms Automatically....................................................................................................10-40
10.11.3 Dumping Performance Data Manually..........................................................................................10-41
10.11.4 Dumping Performance Data Automatically...................................................................................10-42
10.12 Clearing the T2000 Log Data..................................................................................................................10-43
10.13 Configuration Upgrade Wizard...............................................................................................................10-45
11 Backing Up and Restoring the NE Data............................................................................11-1

11.1 Comparison of NE Data Backup and Restoration Methods........................................................................11-3
11.2 Backing Up the NE Database to the SCC Board........................................................................................11-4
11.3 Forcibly Backing Up the NE Database to an SCC Board...........................................................................11-5
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xiii

11.4 Backing Up History Alarms to a Flash Card...............................................................................................11-5

11.5 Backing Up the NE Database to a CF Card................................................................................................11-6
11.5.1 Automatically Backing Up the NE Database to a CF Card............................................................... 11-6
11.5.2 Manually Backing Up the NE Database to a CF Card.......................................................................11-7
11.6 Backing Up Device Data to the NMS Server or the NMS Client...............................................................11-7
11.7 Restoring the NE Database from the SCC Board....................................................................................... 11-9
11.8 Restoring the NE Database from the CF Card............................................................................................11-9
11.9 Restoring Device Data from the NMS Server or the NMS Client............................................................11-10
12 Viewing Reports.....................................................................................................................12-1
12.1 Report Types Supported by the T2000....................................................................................................... 12-3
12.2 Viewing the Networking Diagram..............................................................................................................12-3
12.3 Viewing the Clock Tracing Diagram..........................................................................................................12-4
12.4 Viewing the Timeslot Allocation Diagram.................................................................................................12-5
12.5 Viewing the NE Information Report...........................................................................................................12-6
12.6 Viewing the Physical Location Information Report................................................................................... 12-7
12.7 Viewing the Equivalent NE Statistics Report.............................................................................................12-7
12.8 Viewing the Port Resource Statistics Report.............................................................................................. 12-8
12.9 Viewing the Board Information Report...................................................................................................... 12-8
12.10 Viewing the Slot Information Report........................................................................................................12-9
12.11 Viewing the Board Count Report............................................................................................................12-10
12.12 Viewing the Board Manufacturer Information Report............................................................................12-11
12.13 Viewing Common Manufacturer Information Report.............................................................................12-11
12.14 Viewing WDM NE Master/Slave Subrack Info Report..........................................................................12-12
12.15 Viewing the Lower Order Cross-Connection Statistics Report..............................................................12-12
12.16 Viewing the WDM Protection Group Switching Status Report.............................................................12-13
12.17 Browsing the Fiber Cable/Radio Link Resource Occupancy..................................................................12-14
13 Appendix..................................................................................................................................13-1
13.1 Performing Remote Maintenance................................................................................................................13-2
13.1.1 Remote Maintenance..........................................................................................................................13-2
13.1.2 Enabling a Remote Maintenance User...............................................................................................13-3
13.1.3 Performing Remote Maintenance.......................................................................................................13-4
13.2 Mutual Exclusion List for Multiclient Operations......................................................................................13-4
13.3 Timeslot Numbering Policy........................................................................................................................13-7
13.4 Configuration Data Management Information List.....................................................................................13-8
13.4.1 General Configuration Data Management Information List..............................................................13-9
13.4.2 SDH Configuration Data Management Information List.................................................................13-11
13.4.3 PTN Configuration Data Management Information List.................................................................13-21
13.4.4 WDM Configuration Data Management Information List...............................................................13-23
13.4.5 NG WDM Configuration Data Management Information List........................................................13-41
13.4.6 RTN Configuration Data Management Information List.................................................................13-51
13.4.7 Ethernet Configuration Data Management Information List...........................................................13-54
13.4.8 ATM Configuration Data Management Information List................................................................13-71
xiv Huawei Proprietary and Confidential Issue 01 (2009-06-30)

13.4.9 ASON Configuration Data Management Information List..............................................................13-74

13.4.10 DDN Configuration Data Management Information List..............................................................13-75
13.4.11 Alarm and Performance Configuration Data Management Information List................................13-76
13.5 Standards Followed...................................................................................................................................13-78
A Glossary.....................................................................................................................................A-1
B Acronyms and Abbreviations.................................................................................................B-1
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xv

Operation Guide for Common Features Figures
Figures
Figure 1-1 The position of the T2000 in TMN....................................................................................................1-2

Figure 2-1 GUI...................................................................................................................................................2-32
Figure 2-2 The NE Explorer window of an NE.................................................................................................2-33
Figure 2-3 Clock View.......................................................................................................................................2-34
Figure 2-4 NE Panel...........................................................................................................................................2-36
Figure 2-5 Legends.............................................................................................................................................2-37
Figure 2-6 Path View.........................................................................................................................................2-37
Figure 2-7 NE Panel...........................................................................................................................................2-38
Figure 2-8 Legends............................................................................................................................................2-39
Figure 2-9 Path View.........................................................................................................................................2-40
Figure 2-10 NE Panel.........................................................................................................................................2-41
Figure 2-11 Legends...........................................................................................................................................2-42
Figure 2-12 Path View.......................................................................................................................................2-42
Figure 2-13 NE Panel.........................................................................................................................................2-43
Figure 2-14 Legends...........................................................................................................................................2-44
Figure 2-15 Path View.......................................................................................................................................2-45
Figure 2-16 Browse Alarm and Event................................................................................................................2-46
Figure 2-17 Browse SDH Performance..............................................................................................................2-47
Figure 2-18 Browse WDM Performance...........................................................................................................2-48
Figure 2-19 View legends..................................................................................................................................2-48
Figure 3-1 Sample of the DCN protection...........................................................................................................3-5
Figure 3-2 Flow chart of T2000 security management......................................................................................3-16
Figure 3-3 Flow chart of the NE security management.....................................................................................3-17
Figure 4-1 IP and ECC hybrid networking-1.....................................................................................................4-14
Figure 4-2 IP and ECC hybrid networking-2.....................................................................................................4-15
Figure 4-3 ECC independent networking...........................................................................................................4-16
Figure 5-1 Flow of constructing the network topology........................................................................................5-7
Figure 7-1 Alarm reporting flow chart.................................................................................................................7-6
Figure 7-2 alarm handling procedure...................................................................................................................7-8
Figure 7-3 NE Alarm Correlation......................................................................................................................7-18
Figure 7-4 Alarm status conversion module......................................................................................................7-22
Figure 8-1 Performance reporting process...........................................................................................................8-4
Figure 9-1 NE Data Management Operation........................................................................................................9-5
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xvii

Figures Operation Guide for Common Features
Figure 9-2 T2000 Data Management Operation..................................................................................................9-7

Figure 13-1 Remote Maintenance......................................................................................................................13-2
Figure 13-2 Mutual exclusion list for multiclient operations.............................................................................13-5
Figure 13-3 Mutual exclusion list for multiclient operations on ASON SDH trails..........................................13-6
Figure 13-4 Mutual exclusion list for multiclient operations on ASON WDM trails........................................13-6
Figure 13-5 The by order mode..........................................................................................................................13-7
Figure 13-6 The interleaved mode.....................................................................................................................13-8
xviii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Operation Guide for Common Features Tables
Tables
Table 1-1 Manageable SDH series equipment.....................................................................................................1-3

Table 1-2 Manageable MSTP series equipment...................................................................................................1-4
Table 1-3 Manageable OSN series equipment.....................................................................................................1-5
Table 1-4 Manageable WDM equipment.............................................................................................................1-5
Table 1-5 Manageable RTN series equipment.....................................................................................................1-6
Table 1-6 Manageable submarine line equipment................................................................................................1-7
Table 1-7 Manageable PTN series equipment......................................................................................................1-7
Table 1-8 New boards...........................................................................................................................................1-9
Table 1-9 New boards.........................................................................................................................................1-11
Table 1-10 New boards.......................................................................................................................................1-13
Table 1-11 New equipment................................................................................................................................ 1-14
Table 1-12 New boards.......................................................................................................................................1-14
Table 1-13 New equipment supported................................................................................................................1-16
Table 1-14 New Board....................................................................................................................................... 1-16
Table 2-1 T2000 processes...................................................................................................................................2-3
Table 2-2 NE status............................................................................................................................................ 2-49
Table 2-3 Path and port status............................................................................................................................ 2-49
Table 2-4 Working Status...................................................................................................................................2-50
Table 3-1 Database users and authorities...........................................................................................................3-11
Table 3-2 Operation Set Type............................................................................................................................ 3-56
Table 4-1 Security log danger level......................................................................................................................4-2
Table 4-2 Operation log danger level...................................................................................................................4-3
Table 4-3 Configuration List..............................................................................................................................4-15
Table 4-4 Configuration List..............................................................................................................................4-17
Table 7-1 alarm handling procedure.....................................................................................................................7-9
Table 7-2 Impacts of alarm viewing operations on NEs....................................................................................7-10
Table 7-3 Impacts of alarm setting operations on NEs and services..................................................................7-12
Table 7-4 Impacts of alarm setting operations on alarms...................................................................................7-13
Table 7-5 Alarm reversion handling mode.........................................................................................................7-14
Table 7-6 Alarm severity....................................................................................................................................7-21
Table 7-7 Power output parameters of the PMU................................................................................................7-95
Table 10-1 Script files the T2000 provides........................................................................................................10-4
Table 10-2 Comparison of three data maintenance methods............................................................................10-10
Issue 01 (2009-06-30) Huawei Proprietary and Confidential xix

Tables Operation Guide for Common Features
Table 10-3 Characteristics and application scenarios of three data maintenance methods..............................10-11
Table 11-1 Backup and restoration methods and application scenarios.............................................................11-3
xx Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Operation Guide for Common Features About This Document
About This Document
Purpose
The Operation Guide for Common Features describes the operations for common feature on the
T2000. This document also provides the glossary and the acronyms and abbreviations.
This document guides the user to understand basic operations of the T2000.
Related Version
The following table lists the product version related to this document.
Product Name Version
OptiX iManager T2000 V200R007C03
Intended Audience
The intended audiences of this document are:
l Network Monitoring Engineer
l Data Configuration Engineer
l NM Administrator
l System Maintenance Engineer
Organization
This document is organized as follows.
Chapter Description
1 T2000 V200R007C03 Overview This chapter describes its position in the

telecommunication management network
(TMN), the main functions and the new
features of the T2000.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential 1

About This Document Operation Guide for Common Features
Chapter Description
2 Getting Started This chapter describes some preparation

operations that ensure a smooth, trouble-free
launch of T2000.
3 Security Management This chapter describes operations about

security management of the T2000.
4 Log Management This chapter describes how to perform log

management in the T2000.
5 Topology Management This chapter describes how to create

topological objects in the T2000.
6 Time Localization Management This chapter describes how to set time

localization in the T2000.
7 Alarm Management This chapter describes how to perform alarm

management in the T2000.
8 Performance Management This chapter describes how to perform

performance management in the T2000.
9 Keeping Data in the T2000 Consistent This chapter describes how to keep data in the
with NEs T2000 consistent with NEs.
10 Backing Up and Restoring T2000 Data This chapter describes how to back up and
restore the T2000 data.
11 Backing Up and Restoring the NE Data This chapter describes how to back up and
restore the NE Data.
12 Viewing Reports This chapter describes how to view various

reports in the T2000.
13 Appendix This chapter describes the reference

information related to the T2000.
A Glossary This part lists the glossary used in the

document.
B Acronyms and Abbreviations This part lists the acronyms and abbreviations
used in the document.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

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.
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.
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users

are in boldface. For example, log in as user
root.
Italic Book titles are in italics.

Courier New Terminal display is in Courier New.
Command Conventions
Boldface The keywords of a command line are in

boldface.
Italic Command arguments are in italic.
[] Items (keywords or arguments) in square

brackets [ ] are optional.
{ x | y | ... } Alternative items are grouped in braces and

separated by vertical bars. One is selected.

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

square brackets and separated by vertical
bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and

separated by vertical bars. A minimum of one
or a maximum of all can be selected.
[ 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
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.
Keyboard Operation
Format Description
Key Press the key. For example, press Enter and

press Tab.
Key 1+Key 2 Press the keys concurrently. For example,

pressing Ctrl+Alt+A means the three keys
should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing

Alt, A means the two keys should be pressed
in turn.
Mouse Operation
Action Description
Click Select and release the primary mouse button

without moving the pointer.

Action Description
Double-click Press the primary mouse button twice

continuously and quickly without moving the
pointer.
Drag Press and hold the primary mouse button and

move the pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 01 (2009-06-30) Based on Product Version V200R007C03

The updated contents are as follows.
Chapter 3 Security Management
l The function of deleting NM User.
l The function of switching a DC User.
Chapter 4 Topology Management

l The function of fiber/cable pipe.
l The function of adding and modifying a Line-Side Port.
l The function of querying the path status of a board.
l The function of querying the physical fiber connection between NEs.
Chapter 7 Alarm Management

The function of deleting history alarms.
Chapter 8 Performance Management
l The function of querying NE temperature.
l The function of setting performance monitoring parameters of an WDM trail.
l The function of setting RMON performance monitoring parameters for an Ethernet Port.
Chapter 11 Backing Up and Restoring the NE Data

l The function of forcibly backing up the NE database to an SCC board.
l The function of backing up history alarms to a flash card.
l The function of backing up device data to the NMS server or the NMS client.
l The function of restoring device data from the NMS server or the NMS client.
Chapter 13 Appendix
l The function of datacenter operator operation set.

l The function of datacenter maintainer operation set.

l The function of datacenter monitor operation set.
Updates in Issue 01 (2009-03-30) Based on Product Version V200R007C02

Initial release.

Operation Guide for Common Features 1 T2000 V200R007C03 Overview
1 T2000 V200R007C03 Overview
About This Chapter
The following pages describe the main functions of the T2000, its position in the
telecommunication management network (TMN), and the new features of the T2000
V200R007C03 version.
1.1 Network Position

The OptiX iManager T2000 SNMS for Transmission Network (Sub-network Level) is produced
by Huawei Technologies Co., Ltd. (hereinafter referred to as Huawei). It provides solutions for
the transport network management.
1.2 Product Characteristics
This topic describes the main characteristics of the T2000.
1.3 Manageable Equipment
The T2000 can uniformly manage OptiX series optical transmission equipment from Huawei,
such as SDH, WDM, RTN, PTN and submarine line equipment.
1.4 What's New in T2000 V200R007C03
This topic describes the new features of the basic network management function in the T2000
V200R007C03.
1.5 Updates in the T2000 V200R007C03 for SDH Equipment
This topic describes the new features of the SDH equipment in the T2000 V200R007C03.
1.6 Updates in the T2000 V200R007C03 for WDM Equipment
This topic describes the new features of the WDM equipment in the T2000 V200R007C03.
1.7 Updates in the T2000 V200R007C03 for Submarine Line Equipment
This topic describes the new features of the submarine line equipment in the T2000
V200R007C03.
1.8 Updates in the T2000 V200R007C03 for RTN Equipment
The T2000 V200R007C03 has the following new features.
1.9 Updates in the T2000 V200R007C03 for PTN Equipment
This topic describes the new features of the PTN equipment in the T2000 V200R007C03.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential 1-1

1 T2000 V200R007C03 Overview Operation Guide for Common Features
1.1 Network Position

The OptiX iManager T2000 SNMS for Transmission Network (Sub-network Level) is produced
by Huawei Technologies Co., Ltd. (hereinafter referred to as Huawei). It provides solutions for
the transport network management.
The T2000 is a subnetwork management system (SNMS). In the TMN architecture, SNMS is
located between the NE layer and network layer. The T2000 supports all functions of the NE
layer and some of the network layer management functions. Figure 1-1 shows the position of
the T2000 in the TMN architecture.
Figure 1-1 The position of the T2000 in TMN
Business Management Layer BMS
Service Management Layer SMS
Network Management Layer NMS
Subnetwork Management Layer

(iManager T2000)
SNMS
Element Management Layer EMS EMS
Network Element Layer GNE GNE GNE
NE NE ... NE NE NE NE
NE NE NE
BMS: Business Management System
SMS: Service Management System
NMS: Network Management System
SNMS: Subnetwork Management System
EMS: Element Management System
GNE: Gateway Network Element
NE: Network Element
NOTE
The T2100 is a network management system (NMS), and manages the subnetwork management system
(SNMS).
1-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

1.2 Product Characteristics

This topic describes the main characteristics of the T2000.
l Uniformly manage multiple types of equipment and services, including SDH, WDM, PTN,
RTN, submarine cable system, Ethernet, ATM, ASON, and SAN.
l Provide the Network Management System Maintenance Suite to complete the T2000
deployment and expansion, fault data collection, and northbound interface configuration.
l Deploy the processes of the NE management service, network service, and NBI service
independently.
l As a subnetwork management system (SNMS), provide all element management functions
and some network management functions.
l Support end-to-end trail management.
l Support both Windows, Solaris and SUSE Linux platforms, on which the same operations
are provided.
l Support distributed deployment.
l Support several open external interfaces, such as CORBA, SNMP, and MML.
l Provide Java-based graphical user interface, in a structure of "tree on the left and table on
the right".
l Provide powerful equipment search function, with which the user can search for and then
create NEs and fibers in batches.
l Provide complete alarm, configuration, performance and security (FCPS) management
functions.
l Support the IP, OSI and ECC communication protocols.
l Provide three high availability solutions, including Veritas hot standby, Veritas warm
standby, and 1:N cold standby.
l Provide several tools and methods for data backup and restoration , to ensure network data
security.
l Provide various reports and drawings.
1.3 Manageable Equipment

The T2000 can uniformly manage OptiX series optical transmission equipment from Huawei,
such as SDH, WDM, RTN, PTN and submarine line equipment.
Table 1-1, Table 1-2 and Table 1-3 lists the SDH equipment that the T2000 V200R007C03
manages.
Table 1-1 Manageable SDH series equipment
Equipment Name in the T2000
OptiX 155C SDH transmission unit for the OptiX 155C

access network

OptiX 155S simplified STM-1 optical OptiX 155S

transmission system
OptiX 155/622B STM-1/STM-4 compatible OptiX 155/622B_I

optical transmission system (19-inch rack) OptiX 155/622B_II
OptiX 2500 STM-4/STM-16 compatible OptiX 2500

optical transmission system
OptiX 2500 REG STM-16 regenerator OptiX 2500 REG
Table 1-2 Manageable MSTP series equipment

OptiX Metro 100 terminal STM-1 optical OptiX Metro 100

transmission system
OptiX Metro 200 ultra compact STM-1 OptiX Metro 200

optical transmission system
OptiX Metro 500 ultra compact STM-1 OptiX Metro 500

multi-service transmission system
OptiX 155/622H(Metro1000) STM-1/STM-4 OptiX 155/622H (Metro 1000)

MSTP optical transmission system
OptiX 155/622H(Metro1000) STM-1/STM-4 OptiX Metro 1000V3

MSTP optical transmission system V3 series
OptiX Metro 1050 compact STM-1/STM-4 OptiX Metro 1050

multi-service optical transmission system
OptiX Metro 1100 compact container OptiX Metro 1100

STM-16 multi-service transmission system
OptiX 155/622(Metro2050) STM-1/STM-4 OptiX 155/622 (Metro 2050)

compatible optical transmission system
OptiX 2500+(Metro3000) STM-16 MADM/ OptiX 2500+ (Metro 3000)

MSTP optical transmission system
OptiX Metro 3100 STM-16 multi-service OptiX Metro 3100

transmission system
OptiX 10G(Metro5000)STM-64 MADM optical OptiX 10G (Metro 5000)

transmission system

Table 1-3 Manageable OSN series equipment

OptiX OSN 500 STM-1/STM-4 multi- OptiX OSN 500

service CPE optical transmission system
OptiX OSN 1500 intelligent optical OptiX OSN 1500

transmission system
OptiX OSN 2000 enhanced STM-1/STM-4 OptiX OSN 2000

multi-service optical transmission system

transmission system
OptiX OSN 2500 REG STM-16 regenerator OptiX OSN 2500 REG

transmission system

switching system

switching system
Table 1-4 lists the WDM equipment that the T2000 V200R007C03 manages.
Table 1-4 Manageable WDM equipment

Category Equipment Version Name in the T2000
Metro WDM series OptiX Metro 6020 compact OptiX Metro 6020
container CWDM system
V100R001
OptiX Metro 6040 compact OptiX Metro 6040

container WDM system
V100R001
OptiX Metro 6040 compact OptiX Metro 6040 V2

container DWDM system
V200R001 or higher
OptiX Metro 6100 DWDM OptiX Metro 6100

multi-service transmission
system V100R002
OptiX Metro 6100 DWDM OptiX Metro 6100V1

system V100R003

Category Equipment Version Name in the T2000
OptiX Metro 6100 WDM OptiX Metro 6100V1E

system V100R004 or higher
OptiX OSN 900A compact OptiX OSN 900A

WDM system (A Type)
LH WDM series OptiX BWS 320G backbone OptiX BWS OAS, OptiX
DWDM optical transmission BWS OCS, OptiX BWS OIS
system V300R002
OptiX BWS 320G backbone OptiX BWS 320GV3

DWDM optical transmission
system V300R004
OptiX BWS 1600G OptiX BWS 1600G, OptiX

backbone DWDM optical BWS 1600G OLA
transmission system
V100R003 or higher
OptiX OTU 40000 backbone OptiX OTU 40000

DWDM optical transmission
system
NG WDM series OptiX OSN 3800 compact OptiX OSN 3800

intelligent optical transport
platform
OptiX OSN 6800 intelligent OptiX OSN 6800

optical transport platform
OptiX OSN 8800 I intelligent OptiX OSN 8800 I

optical transport platform
OptiX OSN 1800 Compact OptiX OSN 1800

Multi-Service Edge Optical
Transport Platform
NOTE
The OptiX BWS 1600G OLA is an independent power supply subrack. It is supported by the OptiX BWS
1600G backbone DWDM optical transmission system V100R004 and higher versions.
Table 1-5 lists the RTN equipment that the T2000 V200R007C03 manages.
Table 1-5 Manageable RTN series equipment
OptiX RTN 605 radio transmission system OptiX RTN 605

Table 1-6 lists the submarine line equipment that the T2000 V200R007C03 manages.
Table 1-6 Manageable submarine line equipment
OptiX SLM 1630 Submarine Line Monitor OptiX SLM 1630
OptiX BWS 1600S Submarine Line Terminal OptiX BWS 1600S

Equipment
Table 1-7 lists the PTN equipment that the T2000 V200R007C03 manages.
Table 1-7 Manageable PTN series equipment
OptiX PTN 1900 optical network PTN series OptiX PTN 1900
multi-service packet transmission platform
1.4 What's New in T2000 V200R007C03

This topic describes the new features of the basic network management function in the T2000
V200R007C03.
T2000 Deployment
l The T2000 server supports the SUSE Linux + Sybase platform.

l The T2000 server supports the distributed deployment on the Solaris and SUSE Linux.
Specifically, the functions includes deleting and migrating instances from a slave server,
monitoring the NMS status of a slave server, starting and stopping the T2000 on the master
server and slave servers simultaneously.
l The T2000 client supports the Windows Vista.
l The T2000 supports the blade server that can run on SUSE Linux and Windows.
l The T2000 supports the installation of single servers on Solaris and SUSE Linux in a
distributed manner.
l The T2000 supports the installation of the HA system (Veritas hot standby) in a distributed
manner.
l The MSuite supports the fault analysis tool for the T2000.
l The MSuite supports the functions of downloading the dump files and downloading files
from the server.
l The MSuite client can be automatically upgraded by using the CAU tool.
Optimized T2000 Alarm

l The T2000 supports the ability to report service alarms according to trails.
l In the setting of filter conditions for alarms to be browsed, you can filter alarms by board,
port, and functional block.
Optimized T2000 Topology

l For the NE nodes on the Main Topology, icons are added to display the ASON status of
the NEs.
l The equipment can be searched, created and uploaded in a whole process, which can
simplify the process of finding equipment.
Optimized Network Function

Support the ability to query the protection subnet related to a topology object or an optical
interface alarm.
Other Changes
l Based on the original upgrade scheme, the T2000 supports a new upgrade scheme, to
achieve a quick version upgrade.
NOTE
The new upgrade scheme is only applicable to an upgrade from T2000 V200R007C01, T2000
V200R007C02 to T2000 V200R007C03 by the database upgrade mode.
l The T2000 V200R006C01 and V200R006C03 can be directly upgraded to V200R007C03
by using the upgrade wizard.
l In the Veritas hot standby and warm standby schemes, the version of the Veritas software
is changed from 4.1 to 5.0.
l In the case of the HA system (Veritas hot or warm standby), the T2000 supports a quick
installation of the Solaris operating system and its patch, and the HA software.
l In the Veritas hot standby scheme, the VCS no longer directly monitors the NMS processes.
The VCS monitors only the NMSServer and NMSAgent processes. With the NMSServer
process, you can start and stop the T2000, and monitor the status of the T2000 server. With

the NMSAgent process, you can ensure that the T2000 is shut down during the automatic
switching triggered by a T2000 failure. The service processes of the T2000 are monitored
on the System Monitor.
NOTE
With the preceding changes, the only difference between the operations on the T2000 for single server
and HA system schemes is in the operations to start and stop the T2000. The other operations to start
and stop the service processes of the T2000 between the two schemes are the same.
l In the function of backing up the NMS information (include the deployment information
about the T2000 and the database of the T2000). After the backup operation, the backup
data is saved simultaneously in the backup directory on the client of the NMS maintenance
suite.
l In the function of restoring the NMS information (include the deployment information
about the T2000 and the database of the T2000). In addition, cross-operating system, cross-
scheme (HA scheme or single server scheme) restoration is supported. In this case,
however, only the deployment information about the T2000 can be restored. The data of
the database cannot be restored.
l The T2000 supports the ability to import and export script files by subnet.
l The networkwide maintenance status indicator is optimized. When the maintenance status
indicator is on, no query is performed before a specific status category is specified for query.
l The T2000 supports the ability to manage DC user login.
l The T2000 supports the ability to modify the NE ID on the T2000.
l The T2000 supports the ability to configure the equipment to automatically enable LCT
access rights after the communication between the equipment and T2000 stops.
1.5 Updates in the T2000 V200R007C03 for SDH Equipment

This topic describes the new features of the SDH equipment in the T2000 V200R007C03.
New Equipment
The T2000 V200R007C03 supports no new equipment.
New Boards
Table 1-8 lists the new boards supported in the T2000 V200R007C03.
Table 1-8 New boards
Equipment Board
OptiX OSN 1500 V100R009C03 SSR1PEFS8, SSQ1PEGS2, SSR1PEGS1,

SSR1PCXL
OptiX OSN 3500 V100R009C03 SSN1PSXCS, SSN1PEX1, SSN1PETF8,

SSN1PEG16

New Features
The T2000 V200R007C03 supports the following new features:
l New Features for OSN 1500, OSN 3500
– Supports the features of L2VPN.
– Supports the management of multiprotocol label switching (MPLS) tunnels.
– Supports OAM management for MPLS tunnels, OAM management for Ethernet
services and OAM management for Ethernet port.
– Supports the following QoS features: configuring the differentiated service (DiffServ)
domains, port policy, CAR policy, Port WRED Policy, V-UNI ingress policy, V-UNI
egress policy, PW policy, weighted random early detection (WRED) congestion and
discarding policy of services, QinQ policy, weighted fair queuing (WFQ) schedule
policy, and mapping between the CoS priority and the scheduling queue.
– Supports the control plane for configuring the static routes and address resolution.
– Supports the management of the Ethernet multi-service transmission platform (MSTP)
protocol and the Internet group management protocol (IGMP) Snooping.
– Supports the management of the Ethernet interface.
– Supports the automatic protection switching (APS) of MPLS tunnels.
– Supports the packet Ethernet services including E-Line service, E-LAN service, E-
AGGR service and clock service.
– Supports the management of inband DCN.
l New Features of SDH Network
– Supports the ability to manage SDH platinum services.
– Supports the ability to manage fiber/cable pipes.
– Supports the service alarm analysis function.
l Optimize the SDH ASON Features
– Supports the SDH UNI service management.
– Supports the ability to create associated SDH services of the same source and query the
synchronization status of associated SDH services of different source nodes.
– Supports the in-service migration between a diamond SDH ASON trail and a gold SDH
ASON trail.
– Supports the ability to query the timeslot segmentation of links.
1.6 Updates in the T2000 V200R007C03 for WDM

Equipment
This topic describes the new features of the WDM equipment in the T2000 V200R007C03.
New Equipment
New Boards

Equipment Board
OptiX OSN 1800 V100R001C02 TNF1OPU, TNF1LSX, TNF1LOE
OptiX OSN 3800 V100R004C03 TN11HSC1, TN12OAU1, TN12OBU1,

TN12OBU2, TN11WSMD2, TN12LDX,
TN12LOG, TN12LOM, TN12TMX,
TN13LSX, TN12NS2
OptiX OSN 3800 V100R004C04 TN52NS2, TN52TOM
OptiX OSN 6800 V100R004C03 TN11HSC1, TN12OAU1, TN12OBU1,

TN12OBU2, TN11WSMD2, TN11STG,
TN12ND2, TN12LDX, TN12LOG,
TN12LOM, TN12TMX, TN13LSX,
TN12ELQX, TN12PTQX, TN11RDU9,
TN11BMD8
OptiX OSN 6800 V100R004C04 TN52NS2, TN52TOM
OptiX OSN 8800 I V100R001C02 TN52STG, TN52XCH, TN52NS2,

TN52TOM, TN11MR2, TN11MR4,
TN11MR8, TN11MB2, TN11CMR2,
TN11CMR4, TN11DMR1
OptiX BWS 1600G V100R007C02 E1SCU
OptiX Metro 6100V1E V100R008C04 SSE1LUR40S, SSE1LUR40, SSE1LU40S,

SSE1LU40, SSE1TMX40S, SSE1TMX40,
IMX4, SSE1CP40
New Features
The T2000 V200R007C03 supports the following new features.
l New Features for the OptiX OSN 1800: The LQG board supports the mapping of client-
side services to WDM-side FEC5G or OTU5G services.
l New Features for the OptiX OSN 3800, OptiX OSN 6800
– Supports the ability to enable scrambling for FC services.
– Supports the WDM ports for the black-and-white light on the OTU board.
– Supports IEEE-1588 clocks and Ethernet synchronous clocks.
– Supports the relay mode for the TN12ND2 board, and supports the ability to set and
query the working mode for the TN12ND2 board.
– Supports the ability to set and query new fiber types and the dispersion coefficient.
– Supports the ability to set and query the compensation value of a dispersion
compensation module (DCM).
– Supports the ability to set and query the cable length for cascaded clock ports.
– Supports the ability to set and query time precision compenstation and the compensation
mode.

– Supports ODU0 trails at different layers.

– Supports two board working modes and 14 port working modes of the TN52TOM board.
– Supports the OTU2V, Infiniband 2.5G, Infiniband 5G, FC800, and FICON8G service
types.
l New Features for the OptiX OSN 8800 I
– Supports ODU0 trails at different layers.
– Supports synchronous and asynchronous board working modes.
– Supports two board working modes and 14 port working modes of the TN52TOM board.
l New Features for the OptiX BWS 1600G
– Supports the function that a master subrack can manage 13 slave subracks.
– Supports the alarms about subrack offline in the master and slave subrack management.
– Supports the ability to manage the wavelength selective switch (WSS) enabling status
and WSS protection switching in the WSS multipath management.
– Supports the ability to delete the rerouted optical cross-connections that are inactive in
the WSS multipath management.
– Supports the ability to display the protection status when you configure the wavelength
protection.
– Supports the ability to associate the physical subrack with the logical subrack for a
WDM NE.
– Supports the AIS and OCI maintenance signal types when you insert a maintenance
signal to the TMX40 board.
– Supports the FC working mode of the LOM or LOMS board.
– The extended intra-board protection is not supported for the TMR or TMRS board.
– Supports slow and middle rates for fan speed levels.
– Supports the TIM detection mode for the ELOG(S), LBF(S), TMR(S), and ETMX(S)
boards.
– Supports the non-intrusive mode for the LBF(S), LWF(S), ETMX(S), and LQM boards.
l New Features for the OptiX Metro 6100V1E: Supports the ability to configure four service
types for the TMR or TMRS board in the non-adaptive mode. The four service types are
OTU2 (10.7G), OTU2e (11.1G), OTU2e (11.3G), and OTU2v (10.7G).
l New Features of WDM Network
– Supports the ability to provide a report on WDM statistics on inter-station wavelength
resources.
– Supports the WSS protection management function.
l New Features of WDM ASON
– Supports the rerouting of the WDM ASON services at the electrical layer that is
triggered by the SD alarm.
– Supports specifying the channel number when creating and optimizing WDM ASON
services at the electrical layer.
– Supports revertive rerouting and tunable wavelengths for the WDM ASON services at
the optical layer.
– Supports virtual TE links.

1.7 Updates in the T2000 V200R007C03 for Submarine Line

Equipment
This topic describes the new features of the submarine line equipment in the T2000
V200R007C03.
New Equipment
New Boards
Equipment Board
OptiX BWS 1600S V100R003C01 TN91SOCP, TN91ASE, TN91UHBA,

SSE1LUR40S, SSE1LU40S, SSE1TMX40S
New Features
The T2000 V200R007C03 supports the following new features:
l Supports the 1+N optical path protection.
l Supports the ability to set the rights of users to manage the laser switch of the UHBA board.
Maintainers are assigned with the rights by default.
l Supports the ability to configure return loss detection thresholds for the UHBA, OPA, and
OBA boards.
l Supports the orderwire functions of the LU40S, LUR40S, and TMX40S boards.
l Supports the E1 cross-connect functions of the LU40S, TMX40S, and LUR40S boards.
l Supports the pseudo-random binary sequence (PRBS) functions of the LU40S and
TMX40S boards.
l Supports the ESC protocol mode for the LU40S, TMX40S, and LUR40S boards.
l Supports the ability to release disabling IPA function automatically in the automatic release
of NE functions.
1.8 Updates in the T2000 V200R007C03 for RTN Equipment

The T2000 V200R007C03 has the following new features.
New Equipment
Table 1-11 lists the new equipment supported in theT2000 V200R007C03.

Table 1-11 New equipment
New Boards
Equipment Board
OptiX RTN 605 V100R003 SL72EMS4, SL72IFH1, SL72PH1,

SL72SCC
OptiX RTN 620 V100R003 SL61IFH2
OptiX RTN 910 V100R001C01 TNC1CXPA, TNC1CXPB, TNC1PIU,

TNC1FAN, TND1EF8T, TND1EF8F,
TND1EG2, TND1ML1, TND1ML1A,
TND1IFE2, TND1ODU
OptiX RTN 950 V100R001C01 TND1CXP, TND1PIU, TND1FAN,

TND1AUXQ, TND1EF8T, TND1EF8F,
TND1IFE2, TND1ODU
New Features
T2000 V200R007C03 supports the following new features:
l The RTN 605 supports the following new features:
– Supports the Hybrid and AM features. Therefore, the E1+Ethernet services can be
carried, thus enhancing the usability of links.
– Supports the clock features of setting the priority table of NE clock sources and querying
the currently-traced clock source.
– Supports Ethernet services.
– Supports the QoS management.
– Supports the link aggregation group.
– Supports 802.3 ah ETH OAM and 802.1 ag ETH OAM.
– Supports the ability to manage Ethernet interfaces.
– Supports the RMON performance.
l The RTN 610/620 supports the following new features:

– Supports the Hybrid and AM features. Therefore, the E1+Ethernet services can be
carried, thus enhancing the usability of links.
– Supports the ability to configure board shaping in the QoS management.
– Supports the ability to manage Ethernet interfaces.
– Supports the RMON performance functions such as browsing history groups of Ethernet
ports, collecting performance statistics of a group, setting an alarm group of Ethernet
ports, and setting a history control group.
– Supports LPT management and point-to-multipoint LPT management.
– Supports the 802.1 ad bridge.
– Supports the link aggregation group.
– Supports 802.3 ah ETH OAM and 802.1 ag ETH OAM.
– Supports the SDH performance.
– Supports the ability to diagnose protocol faults and restore protocols.
– Supports the ability to configure the traffic load sharing algorithm for the EMS6 board
in an LAG.
– Supports the ability to set the LAG revertive mode.
– Enable IEEE-1588 overhead bytes.
– Supports the ability to query the Ethernet license.
– Supports the ability to set the maximum transmit power of the ODU interface.
– Supports the feature of packet-based microwave.
– Supports the offload protection between MPLS tunnels and IP or GRE tunnels.
– Supports the IEEE 1588 packet clock.
– Supports PWs with UDP encapsulation that are carried in IP tunnels.
– Supports the ability to configure the long and short serial numbers for an MP group.
– Supports the ability to set the maximum transmit power of the ODU interface. The
function of compressing the MAC address for a microwave interface is deleted.
– Supports a centralized clock domain. An ACR clock can be configured as a system clock
source.
– Supports the feature of packet-based microwave.
– Supports the offload protection between MPLS tunnels and IP or GRE tunnels.
– Supports the IEEE 1588 packet clock.
– Supports PWs with UDP encapsulation that are carried in IP tunnels.
– Supports the ability to configure the long and short serial numbers for an MP group.
– Supports the ability to set the maximum transmit power of the ODU interface. The
function of compressing the MAC address for a microwave interface is deleted.
– Supports a centralized clock domain. An ACR clock can be configured as a system clock
source.

1.9 Updates in the T2000 V200R007C03 for PTN Equipment

This topic describes the new features of the PTN equipment in the T2000 V200R007C03.
New Equipment
Table 1-13 lists the new equipment supported in the T2000 V200R007C03.
Table 1-13 New equipment supported

New Boards
Table 1-14 New Board

Equipment Board
OptiX PTN 910 V100R001C01 TNC1CXPA, TNC1CXPB, TNC1PIU,

TNC1FAN, TND1EF8T, TND1EF8F,
TND1IFE2, TND1ADS2A, TND1ADS2B,
TND1SHD4, TND1ODU
OptiX PTN 950 V100R001C01 TND1CXP, TND1PIU, TND1FAN,

TND1AUXQ, TND1EF8T, TND1EF8F,
TND1IFE2, TND1ADS2A, TND1ADS2B,
TND1SHD4, TND1ODU
OptiX PTN 912 V100R001C02 TND1SHD4I
OptiX PTN 1900 V100R001C03 TN81EFF8, TN72CXP
OptiX PTN 3900 V100R001C03 TN82EG16, TN81EFF8, TN82XCS
OptiX PTN 1900 V100R002C01 TN81IFE2, TN81AFO1
OptiX PTN 3900 V100R002C01 TN81IFE2, TN81AFO1, TN82SCA

New Features
The T2000 V200R007C03 has the following new functions:
l Supports the ability to replace board.
l Supports the mixed Ethernet interfaces at Layer 2 and Layer 3.
l Supports the mixed VLAN sub-interfaces at Layer 2 and Layer 3.
l Supports the ability to configure the long and short serial numbers for an MP group.
l Supports the features of packet-based microwave.
– Supports the ability to configure a microwave interface, including basic attributes, IF
attribute, L2 attribute, L3 attribute, and advanced attributes.
– Supports the ability to configure a radio link, including the IF 1+1 protection, IF boards,
and ODU boards.
– Supports the HOP management.
– Supports the ODU interface.
l Supports the ability to configure an IS-IS protocol instance.
l Supports the ability to create CES service carried by IP/GRE Tunnel.
l Supports the ability to configure the timeslot mode of the E1/VC12.
l Supports the ability to configure the OSPF protocol.
l Supports the ability to configure the MP-BGP protocol.
l Supports the ability to configure the IEEE 1588 packet clock.
l Supports the ability to configure the TOP packet clock.
l Supports the PWs with UDP encapsulation that are carried in IP tunnels.
l Supports the offload protection between MPLS tunnels and IP or GRE tunnels.
l Supports the ability to configure L3VPN trails.
– Supports the ability to create L3VPN trails.
– Supports the ability to search for L3VPN trails.
– Supports the ability to filter L3VPN trails.
– Supports the ability to view alarms generated on L3VPN trails.
– Supports the ability to view performance events generated on L3VPN trails.
– Supports the ability to view PE nodes on L3VPN trails.
– Supports the ability to view the UNI interfaces of L3VPN trails.
– Supports the ability to view the ARP table of L3VPN trails.
– Supports the ability to view the tunnels of L3VPN trails.
– Supports the ability to view the routing protocol of L3VPN trails.
– Supports the ability to view the router target rule of L3VPN trails.
– Supports the ability to view the FIB table of L3VPN trails.
– Supports the ability to view the routing table of L3VPN trails.
l Supports the ability to configure L2VPN trails.
– Supports the ability to create L2VPN E-Line trails.
– Supports the ability to search L2VPN trails.

– Supports the ability to filter L2VPN trails.

– Supports the ability to view alarms generated on L2VPN trails.
– Supports the ability to view performance events generated on L2VPN trails.
– Supports the ability to view the UNI interfaces of L2VPN trails.
– Supports the ability to view the UNI QoS of L2VPN trails.
– Supports the ability to view the PW of L2VPN trails.
– Supports the ability to view the PW QoS of L2VPN trails.
l Supports a centralized clock domain. An ACR clock can be configured as a system clock
source.
l Supports the alarms for loss of external clock source and active and standby board type
mismatch.
l Supports the ability to configure the TOD protocol data format of an external time interface.
l Supports the Franction E1 function.
l Supports UBR+ for an ATM policy.
l Supports the ability to bind inverse multiplexing over ATM (IMA) to G.SHDSL ports.
l Supports the ability to configure the egress bandwidth for an FE interface.
l Apply the QoS policy to multiple NEs.

Operation Guide for Common Features 2 Getting Started
2 Getting Started
About This Chapter
The following pages introduces some preparation operations that will ensure a smooth, trouble-
free launch of the T2000.
2.1 T2000 Process

The T2000 manages different function modules by using processes. After starting the T2000
server, you can view each process in the user interface of the System Monitor client.
2.2 Starting or Shutting Down the T2000
The T2000 uses the standard client/server architecture and multiple-user mode. So, you are
recommended to start or shut down the T2000 by strictly observing the following procedure, in
order not to affect other users that are operating the T2000.
2.3 Changing the Current User Password
You can change the password of the current user. The new password takes effect on the next
login.
2.4 Setting Client Display
You can customize the display effect and features of the T2000 client as required.
2.5 Customizing the Client Time Format
You can customize the time format as required.
2.6 Locking the Client
This section describes the functions of locking the T2000 client.
2.7 Unlocking the Client
You can unlock a locked client.
2.8 Obtaining and Installing a T2000 License
The topic describes the T2000 license file and how to obtain, install and use the T2000 license.
2.9 Starting the Web Client
OptiX OTU40000 and OptiX OSN 900A must be configured through the Web LCT.
2.10 T2000 Main Window
The T2000 main windows and what you can do in the windows are described here.
2.11 Menu Description

2 Getting Started Operation Guide for Common Features
The Main Menu and submenus of the T2000 are described as follows.
2.12 Custom View
The custom view is a topological view similar to the Main Topology. In the T2000, different
users have different network management scopes. The T2000 provides many view setting modes,
including customizing views and setting to start views. The user can customise a view for the
network topologies and equipment under administration as a working interface. 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.
2.13 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.
2.14 Customizing Naming Rule
When you create fibers or trails, the T2000 automatically creates the names of the fibers, trails
and ASON trails 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.
2.15 Copying Table Text Quickly
The T2000 allows you to copy and paste table text. You can copy text from a table to other
programs quickly.
2.16 Filtering Operation Objects in a View
The topology view displays submaps, 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.
2.17 Moving Operation Objects
You can move the operation objects that are shown in the Main Topology.
2.18 Searching for NEs in a View
This operation enables you to find an NE quickly.
2.19 Counting the Number of NEs
By counting the number of NEs,you can learn the number of NEs that are created on the T2000
and the number of the equivalent NEs. The NEs contain real, preconfigured, and virtual NEs.
2.20 Setting Parameters in the List
On the T2000 GUI, the Object Tree is arranged on the left and the parameter list is arranged on
the right. All the parameters are set in the list. To perform operations in the NE Explorer, follow
the procedure.
2.21 Operation Precautions
The operation precautions that have to be taken to ensure correct operations are as follows:
2.22 Rules of Entering Information on User Interface
These rules specify the typing requirements for the text boxes in the T2000 operation interface.
These text boxes are used to enter character strings, file names, IP addresses, MAC addresses,
numerals, passwords, dates, time, and so on.

2.1 T2000 Process

The T2000 manages different function modules by using processes. After starting the T2000
server, you can view each process in the user interface of the System Monitor client.
Table 2-1 describes the processes in the software structure of the T2000.
Table 2-1 T2000 processes

Process Service Name Function Dependent
Process
Fault Process Process for fault EmfTopo

EmfFaultDm management.
EmfSchdSvr Schedule Task Process Schedule task Mdp

management of the
network management
system.
EmfSecuDm Security Process Security management Mdp

of the network
management system.
EmfSysmoniDm Sysmonitor Process Process for system Mdp

monitor client.
EmfTopoDm Topology Process Provides the Mdp

management function
of topology objects in
the network
management system.
Eml_monitomcat Tomcat Process Tomcat Process. Mdp
Eml_PerfSvr T2000 Public Perf Process for public perf Eml_PubSvr

Server service.
Eml_PubSvr T2000 Public Server Process for public Mdp

service.
Eml_WebLCTSv Web LCT Process Process Web service. Eml_monitomcat

r
Nemgr_ext Extended NE Provides the Eml_PubSvr

Management Process management function
of extended NE.
Nemgr_ngwdm NGWDM NE Provides NE Explorer Eml_PubSvr

Management Process for NG WDM NEs.
Nemgr_rtn RTN NE Management Provides NE Explorer Eml_PubSvr

Process for RTN NEs.


Process
Nemgr_sdh SDH NE Management Provides NE Explorer Eml_PubSvr

Process for SDH NEs.
Nemgr_wdm WDM NE Management Provides NE Explorer Eml_PubSvr

Process for WDM NEs.
Nemgr_marine Marine NE Provides NE Explorer Eml_PubSvr

Management Process for Marine NEs.
Nemgr_ptn PTN NE Management Provides NE Explorer Eml_PubSvr

Process for PTN NEs.
Nml_ason_wdm ASON WDM Provides the Eml_PubSvr

of ASON WDM.
Nml_common End-to-End Common Provides the common Mdp

of end-to-end.
Nml_eth End-to-End Eth Provides the Nml_common

of end-to-end Ethernet.
Nml_otn End-to-End OTN Provides the Nml_common

of end-to-end OTN.
Nml_sdh End-to-End SDH Provides the Nml_common

of end-to-end SDH.
Nml_ptn End-to-End PTN Provides the Nml_common

of end-to-end PTN.
SNMPAgent Northbound Interface Forward alarms from EmfFaultDm

Module(SNMP) T2000 to other system.
Process
Naming_Service Naming Service CORBA Naming All T2000

Service. processes
Notify_Service Notify Service CORBA Notify All T2000

Service. processes
Agent_CORBA AgentCORBA CORBA Northbound All T2000

(Northbound CORBA Interface Management. processes
Interface Process)
Eml_mml Eml_mml(MML MML Management Eml_PubSvr

Management Process) Process.


Process
sqlserver Database Server Process Provides database -

management function.
Cau Client Upgrader Upgrade the client Eml_monitomcat

which connects to this
server. The service is
not available when this
process is down.
t2kzip Zip Server File compress Mdp

management of the
network management
system.
toolkit Toolkit Process Provides software None

DCServer DCServer Process Provides software None

2.2 Starting or Shutting Down the T2000

The T2000 uses the standard client/server architecture and multiple-user mode. So, you are
recommended to start or shut down the T2000 by strictly observing the following procedure, in
order not to affect other users that are operating the T2000.
Context
l You are recommended to start the computer and the T2000 application in the following
sequence: Start the computer, start the T2000 server, and then start the T2000 client.
l You are recommended to shut down the T2000 application and the computer in the
following sequence: Exit the T2000 client, stop the T2000 server, and then shut down the
computer.
2.2.1 Starting the Computer
To avoid equipment damage or data loss, strictly follow the procedure provided, to start the
computer. The startup procedures of the workstation are different from that of a normal PC.
Perform the startup procedure according to the actual situation.
2.2.2 Starting the T2000 Server
For network management first start the T2000 server, and then start the T2000 server application.
2.2.3 Viewing the T2000 Process Status
If the process status of the T2000 server is abnormal, the T2000 client may fail to be logged in
or may run abnormally. In this event, you can view the status of each process of the T2000 server
in the user interface of the System Monitor client.
2.2.4 Logging In to the T2000 Client
To manage networks through the T2000 client graphical user interface, you need to use the
T2000 client to access to the T2000 server.

2.2.5 Changing the Login Server

By switching the T2000 server, you can log in to another server without exiting from the current
client.
2.2.6 Exiting a T2000 Client
Before shutting down the T2000 server, you must exit the T2000 client.
2.2.7 Shutting Down the T2000 Server
When the T2000 server is managing the system normally, do not perform this operation. In
special circumstances, for example, when modifying the system time of the computer where the
T2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the T2000 server.
2.2.8 Shutting Down the Computer
Normally, do not shut down the computer where the T2000 resides. In special situations, for
example, when the computer becomes faulty, shut down the computer in the correct sequence.
The shutdown procedures of the workstation are different from that of a normal PC. Perform
the startup procedure according to the actual situation.
2.2.1 Starting the Computer

To avoid equipment damage or data loss, strictly follow the procedure provided, to start the
computer. The startup procedures of the workstation are different from that of a normal PC.
Perform the startup procedure according to the actual situation.
Prerequisite
l The T2000 must be installed successfully.
l The power cable of the workstation or the computer, the power cable of the monitor, data
line and Ethernet line must be connected correctly.
l If there is printer, modem or other peripherals, their power line and data line must be
connected correctly.
l If there is disk array, start the disk array first.
Context
The T2000 supports Windows, Solaris and SUSE Linux operating systems. For details on the
hardware, refer to the OptiX iManager T2000 Product Description.
Procedure
l On Windows
1. Power on the printer, modem and other peripherals.
2. Power on the computer and the Windows is automatically started. The Login dialog
box is displayed.
3. Enter the Username and the Password in the Login dialog box.
4. Click OK to open the Windows user interface.
l On Solaris
NOTE
In the case of a distributed system, you need to start the master server, slave servers, and then slave
protection servers.


2. Power on the workstation and the Solaris is automatically started. The Prompt dialog
box is displayed.
4. Click OK to open the Desktop Environment window.
l On SUSE Linux
NOTE
In the case of a distributed system, you need to start the master server, slave servers, and then slave
protection servers.
2. Power on the computer and the Windows is automatically started. The Prompt dialog
box is displayed.
4. Click OK to open the Desktop Environment window.
----End
2.2.2 Starting the T2000 Server

For network management first start the T2000 server, and then start the T2000 server application.
Prerequisite
l The computer where the T2000 is installed must be started correctly.
l The operating system of the T2000 server must be running correctly and the database must
be started normally.
l The T2000 license must be in the correct directory.
l In the case of the distributed system, the slave server must be started and the communication
among the master server and slave server must be normal.
l In the case of the distributed system, the server of the network management system
maintenance suite on the T2000 server, including the master server and slave server must
be started.
l The instance must be deployed.
Context
NOTE
Normally, when the operating system is started, the network management system maintenance server is
started automatically along. You can also manually start the network management system maintenance
server by running the following commands:
l On Windows,
> cd C:\HWMSuite\server\
> msserver
l On Solaris,
# /etc/rc3.d/S91msserver start
l On SUSE Linux:
# /opt/HWMSuite/server/bin/msdaemon.sh start

Procedure
l If the operating system of the server is Windows:
1. Double-click the T2000Server icon on the desktop of the T2000 server. The Login
dialog box is displayed in a few seconds.
2. Enter the User Name, Password and Server.
For example, User Name: admin, Password: T2000 (T2000 by default) and Server:
Local.
NOTE
Periodically change the password and memorize it.
3. Click Login to display the System Monitor window.
NOTE
If the System Monitor client application is started, you can restart the T2000 server on the
System Monitor client. Perform the following step:
Choose System > Start All NMS Service on the Main Menu of the System Monitor client.
l If the operating system of the server is Solaris:
1. Double-click the T2000Server icon on the desktop of the T2000 server. The Login
dialog box is displayed in a few seconds.
2. Enter the User Name, Password and Server.
For example, User Name: admin, Password: T2000 (T2000 by default) and Server:
Local.
NOTE
Periodically change the password and memorize it.
3. Click Login to display the System Monitor window.
NOTE
If the System Monitor client application is started, you can restart the T2000 server on the
System Monitor client. Perform the following step:
Choose System > Start All NMS Service on the Main Menu of the System Monitor client.
– In the case of the non-distributed system, if the database process, T2000 core
process, and the processes that are optional according to the actual situation are in
the Running state, it indicates that the T2000 server is started.
– In the case of the distributed system, if the database process, T2000 core process,
and the processes that are optional according to the actual situation of the master
server, slave server, and slave protection server (optional) are in the Running state,
it indicates that the T2000 server is started.
l If the operating system of the server is SUSE Linux:
1. Use the t2000 to logging in the server.
2. You can manually start the T2000 server by running the following commands:
% /T2000/server/bin/t2000server
----End
2.2.3 Viewing the T2000 Process Status

If the process status of the T2000 server is abnormal, the T2000 client may fail to be logged in
or may run abnormally. In this event, you can view the status of each process of the T2000 server
in the user interface of the System Monitor client.

Context
NOTE
l To view the status of the T2000 processes by Solaris command line, run the following command as
user t2000:
% /T2000/server/bin/showt2000server
If each process entered has a corresponding process ID and the specific ID does not change, the T2000
processes are normal.
l To view the status of the T2000 processes by SUSE Linux command line, run the following command
as user t2000:
% /T2000/server/bin/showt2000server
If each process entered has a corresponding process ID and the specific ID does not change, the T2000
processes are normal.
Procedure
Step 1 Start and log in to the System Monitor.
Step 2 In the user interface of the System Monitor, click the Process tab, and view whether the status
of each process is Running.
NOTE
When the Sybase database is used and the number of CPUs configured for the T2000 server exceeds eight,
the database management tool automatically increases the number of engines configured for the Sybase
database to enhance the performance of the Sybase database. The number of CPUs configured for the
Sybase database is increased according to the principle of 1/4 of total number of CPUs (the value down
to a nearest integer). For example, if the number of CPUs is 9, the database management tool automatically
configures two engines for the Sybase database. In this case, the System Monitor of the T2000 displays
two database processes.
l If the process status is Stopped, right-click on the process, and choose Start Process from
the shortcut menu. In this way, the status of the process is Running.
l If the manual startup fails, it indicates that the process is abnormal.
l To save resources, you can close unwanted processes. Set the startup mode of the desired
process to Manual, and then select Stop Process.
----End
2.2.4 Logging In to the T2000 Client

To manage networks through the T2000 client graphical user interface, you need to use the
T2000 client to access to the T2000 server.
Prerequisite
The T2000 server must be started correctly.

Context
NOTE
When the T2000 server and the T2000 client are not on a computer, the IP address that is used during the
first login to the T2000 client is added to the ACL automatically. Other IP addresses, however, can be used
during login to the T2000 client only after they are added to the ACL manually.
l On the T2000 client, choose System > NMS Security Settings > ACL from the Main Menu.
l Click Add. In the dialog box displayed, enter related information.
l Select IP address or segment and set an IP address or network section that can be accessed
according to the Example of format.
l Select Start IP address to end IP address and set the range of IP addresses that can be accessed
according to the Example of format.
Procedure
Step 1 On the computer that is installed the T2000 client, double-click the T2000Client icon on the
desktop.
NOTE
In the case of the SUSE Linux operating system, the T2000 client cannot be installed on a local computer.
Therefore, you need to double-click the T2000Client icon on the desktop of the remote computer where
the T2000 client is installed.
The version of the T2000 client must be consistent with the version of the server to be logged in.
Step 2 Enter the User Name, Password of the T2000 client.

For example: User Name: admin; Password: T2000.
NOTE
l By default, the initial user name is admin, and the password is T2000. To protect the T2000 from
unauthorized logins, you need to immediately change this password.
l The administrator needs to create new T2000 users and assign them to certain authority groups.
l After the automatic login is selected, you do not need to enter the user name and password.
Step 3 Optional: Set the server parameters.
1. Click to display the Setting dialog box.

2. Click New to display another Setting dialog box.
3. In the Setting dialog box, specify the IP Address, Port, Mode and Server Name.
NOTE
l The IP address is the IP address used by the T2000 server. In the case of a distributed system,
select the IP address of the main server.
l The Mode has two options including Common and Security (SSL). When you choose the
Security (SSL) mode, the communication between the client and the server is encrypted.
l The communication mode of the client must be consistent with that of the server. Otherwise, the
client cannot log in to the server. To view the communication mode of the server, choose
System > Communication Security Setting on the Main Menu of the System Monitor client.
l You need not enter the Port number. After the Mode is specified, the system selects a Port
number automatically. It is recommended to use the default port.
4. Click OK to complete adding a server.
5. Click OK to complete the server settings.

Step 4 Select a server and click Login to access the Main Topology of T2000.
----End
2.2.5 Changing the Login Server

By switching the T2000 server, you can log in to another server without exiting from the current
client.
Prerequisite
l The login account is set for the server to be switched.
l The IP address of the client is added to the ACL of the server to be switched.
l In the Server Settings dialog box, the settings of the server to be switched are added.
Procedure
Step 1 Choose File > Change Login Server from the main menu.
Step 2 In the Change Login Server dialog box, select the server you want to access, and then click
OK.
Step 3 In the Change Login User dialog box, enter User Name and Password, and then click OK.
----End
2.2.6 Exiting a T2000 Client

Before shutting down the T2000 server, you must exit the T2000 client.
Prerequisite
The T2000 client must be started normally.
Procedure
Step 1 Choose File > Exit from the Main Menu.
Step 2 Click OK in the confirmation dialog box.
NOTE
If the layout of the view is changed and not saved, the Confirm dialog box appears asking you whether to
save the changes. After you confirm the dialog box, automatically exit the client.
----End
2.2.7 Shutting Down the T2000 Server

When the T2000 server is managing the system normally, do not perform this operation. In
special circumstances, for example, when modifying the system time of the computer where the
T2000 resides, or when upgrading the version, you can use the System Monitor Client to shut
down the T2000 server.
Prerequisite
All the T2000 clients connected to the T2000 server must be shut down.

Context
NOTE
l when performing the operations related to the database (such as initializing the T2000 database,
restoring T2000 databases and restoring T2000 MO data) or the operations related to the T2000 (such
as the upgrade, installing patches and re-installing the T2000), you need to shut down the T2000 server
first. You are recommended to shut down the T2000 server in the way of shutting down the T2000
server and the System Monitor Client.
l In the case of a distributed system, perform this operation on only the master server.
Procedure
l Shut down the T2000 server only.
1. From the Main Menu of System Monitor Client, choose System > Stop All NMS
Services to close all processes of the T2000 server.
2. Click OK in the confirmation dialog box. Wait until the T2000 core process, and the
processes that are optional according to the actual situation are in the Stopped state.
Now the T2000 server is shut down successfully.
Now you cannot shut down the MDP process or initialize the database.
l Shut down the T2000 server and the System Monitor Client.
From the Main Menu of System Monitor Client, choose System > Shutdown System to
shut down the T2000 server and the System Monitor Client. Click OK in the confirmation
dialog box.
On Solaris, you can run /T2000/server/bin/shutdownserver in the terminal window of
master server also.
On SUSE Linux, you can run /T2000/server/bin/shutdownserver in the terminal window
of master server also.
After all the T2000 processes are finished, you can initialize the database.
----End
Postrequisite
Perform the following operation to ensure that the T2000 server is already shut down. On
Windows, if the T2000 core process, and the processes that are optional according to the actual
situation do not exist, this indicates that the T2000 server is already shut down.
Perform the following operation to ensure that the T2000 server is already shut down. Run /
T2000/server/bin/showt2000server on the master server as user t2000. If the ID of each process
displayed does not exist, this indicates that the T2000 server is already shut down.
2.2.8 Shutting Down the Computer

Normally, do not shut down the computer where the T2000 resides. In special situations, for
example, when the computer becomes faulty, shut down the computer in the correct sequence.
The shutdown procedures of the workstation are different from that of a normal PC. Perform
the startup procedure according to the actual situation.
Prerequisite
The T2000 server and client applications must be stopped.

Context
CAUTION
To avoid equipment damages or data loss, perform the following step one by one to shut down
the workstation.
Procedure
l On Solaris or SUSE Linux platform
1. Enter the following commands in the terminal window, the UNIX workstation shuts
down automatically.
% su root
Password: rootkit
# sync;sync;sync;sync;sync
# shutdown -y -g0 -i5
NOTE
l rootkit is the default password of super user root. If the password is changed, enter the
new password.
l To restart the Sun workstation, the last command is # shutdown -y -g0 -i6.
2. Turn off the monitor and the peripheral equipment.
l On Windows platform
1. Choose Start > Shut down from the Windows desktop.
2. Choose Shut down and click OK in the dialog box. The computer shuts down
automatically.
3. Turn off the monitor and the peripheral equipment.
----End
2.3 Changing the Current User Password

You can change the password of the current user. The new password takes effect on the next
login.
Prerequisite
The user already logs in to the T2000 server.
Procedure
Step 1 Choose File > Change Password from the main menu.
Step 2 In the Change Password dialog box, set Current Password, New Password, and Confirm
Password.
Step 3 Click OK.
----End

2.4 Setting Client Display

You can customize the display effect and features of the T2000 client as required.
2.4.1 Setting the Main Frame Title

This section describes how to set the main frame title displayed in the title bar.
2.4.2 Setting Output Display
The T2000 client provides an output window in the bottom of the client. This window displays
the prompts and responses that can affect the T2000 or other clients. For example, the
initialization information upon a system start.
2.4.3 Setting Topology Display Style
This section describes how to set the topology display style on the T2000 client.
2.4.4 Setting the Topology Background
You can set the geographical background for different submaps. You can know the geographical
position of a device from the background.
2.4.5 Setting Alarm Colors
You can set the alarm colors displayed on the client.
2.4.6 Setting Alarm Local Display Properties
You can set the alarm local display properties to define the alarm display mode and effect on
the T2000 client.
2.4.1 Setting the Main Frame Title

This section describes how to set the main frame title displayed in the title bar.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, click the Main Frame Title tab.
Step 3 In Main Frame Title, enter the title you want to display.
Step 4 Click OK.
----End
Result
The main frame title that you set is displayed.
2.4.2 Setting Output Display

The T2000 client provides an output window in the bottom of the client. This window displays
the prompts and responses that can affect the T2000 or other clients. For example, the
initialization information upon a system start.

Procedure
Step 2 In the Preferences dialog box, click the Output Window tab.
Step 3 In Output Window, set Maximum Output Lines for the output information. Select
Automatically scroll to the new message and Automatic dump as required.
Step 4 Click OK.
----End
2.4.3 Setting Topology Display Style

This section describes how to set the topology display style on the T2000 client.
Procedure
Step 2 In the Preferences dialog box, click the View Display tab.
Step 3 Click the View Display tab to set the parameters for display effect.

Step 4 Click OK.
----End
2.4.4 Setting the Topology Background

You can set the geographical background for different submaps. You can know the geographical
position of a device from the background.
Prerequisite
You must be an NMS user with the "Topo Watcher" authority or higher.
Context
l The background image supports the JPG and the GIF formats. It is recommended that the
background image is provided by Huawei Technologies Co., Ltd..
l The background image is saved on the local client. If the image file does not exist on the
client, the corresponding submap has no background.
Procedure
Step 1 Choose View > Set Background from the main menu.
Step 2 In the Set Background dialog box, in the submap list, select the submap that you want to modify.
Click Select Background.
Step 3 In the Open dialog box, set the background image file, and then click Open.
Step 4 In the Set Background dialog box, click OK.
----End
Result
The selected image is set to the background of the submap.


Prerequisite
You must be an NMS user with the "Fault Watcher" authority or higher.
Procedure
Step 2 In the Preferences dialog box, click the Color tab.
Step 3 Set the colors for Critical Alarm, Major Alarm, Minor Alarm, and Warning as required.
Step 4 Click OK.
----End
2.4.6 Setting Alarm Local Display Properties

You can set the alarm local display properties to define the alarm display mode and effect on
the T2000 client.
Procedure
Step 2 In the Preferences dialog box, click the Local Fault Settings tab.
Step 3 In the Local Fault Settings tab, set the alarm display mode and effect on the T2000 as required.

Step 4 Click OK.
----End
2.5 Customizing the Client Time Format

You can customize the time format as required.
2.5.1 Setting the Time Format

You can set the time format on the client as required.
2.5.2 Setting the Date Format
You can set the date format on the client as required.
2.5.1 Setting the Time Format

You can set the time format on the client as required.
Context
You need to restart the client to have the settings take effect after you change the time format.

Procedure
Step 2 In the Preferences dialog box, click the Time tab.
Step 3 In the Time Settings group box, set the time format.
NOTE
The format is displayed in the Time Example text box in real time.
Step 4 Click OK.
Step 5 In the Information dialog box, click OK.
----End
2.5.2 Setting the Date Format

You can set the date format on the client as required.
Context
You need to restart the client to have the settings take effect after you change the client date
format.
Procedure
Step 2 In the Preferences dialog box, click the Date tab.
Step 3 In the Date Settings group box, set the date format.

NOTE
l Date separator: It can be "/", "-", or ".". The default is "/".

l Date format: It can be "dd/MM/yyyy", "MM/dd/yyyy", and "yyyy/MM/dd". The default is "dd/MM/yyyy".
l The date format after set is displayed in the Appearance Example.
Step 4 Click OK.
Step 5 In the Information dialog box, click OK.
----End
2.6 Locking the Client

This section describes the functions of locking the T2000 client.
2.6.1 Locking the Client Automatically

After you enable the auto locking function, the client is locked automatically when you do not
operate the client for a period of time. This function prevents other users from performing
improper operations on the client.
2.6.2 Locking the Client Manually
If you do not operate the client for a period of time, you can lock the client manually. In this
way, others cannot operate the client.
2.6.1 Locking the Client Automatically

After you enable the auto locking function, the client is locked automatically when you do not
operate the client for a period of time. This function prevents other users from performing
improper operations on the client.
Procedure
Step 2 In the Preferences dialog box, click the Lock Settings tab.
Step 3 Select Automatically locked. In the minutes later, this terminal will be automatically
locked text box, enter the time to enable the lock time.
NOTE
l Locking time ranges from 1 to 35000 minutes.

l Clear the Automatically locked check box to cancel client auto locking.
Step 4 Click OK.
----End
Result
If you set auto locking and do not perform any operations in the preset interval, the client is
locked automatically.

2.6.2 Locking the Client Manually

If you do not operate the client for a period of time, you can lock the client manually. In this
way, others cannot operate the client.
Procedure
Step 1 Choose File > Lock Terminal from the main menu.
----End
Result
The client is locked.
2.7 Unlocking the Client

You can unlock a locked client.
Prerequisite
The client is locked.
Procedure
Step 1 Press Ctrl+Alt+U.
Step 2 In the Unlock dialog box, enter the user password. Click OK.
NOTE
You can also enter the admin account and password to unlock the client.
----End
Result
If the password is correct, the client is unlocked, and you can perform operations on it.
2.8 Obtaining and Installing a T2000 License

The topic describes the T2000 license file and how to obtain, install and use the T2000 license.
2.8.1 About the T2000 License

The T2000 license controls the management capability and functions of the T2000. Without a
license file, T2000 can be started, but the functions are limited.
2.8.2 Obtaining a T2000 License
Use this procedure to obtain for the T2000 license.
2.8.3 Installing a T2000 License
Use this procedure to install the a license on the computer of the T2000 server.
2.8.4 Changing the License
You can change the license in the T2000 server by using the T2000 client.

2.8.5 How to Correctly Use a License

If the T2000 server is installed on the Solaris or SUSE Linux platform, the
licenseXXXXXXX.txt file is installed in the /T2000/server/license directory. If the T2000 server
is installed on Windows platform, the licenseXXXXXXX.txt file is installed in the C:\T2000
\server\license directory. After you restart the T2000 server program, the license can be
normally applied.
2.8.1 About the T2000 License

The T2000 license controls the management capability and functions of the T2000. Without a
license file, T2000 can be started, but the functions are limited.
Precautions
l A T2000 license exists in the form of text file. The file name is in the format of
licenseXXXXXXX.txt.
l One license file corresponds to the MAC address of the network card of a T2000 computer,
which can only be used on the corresponding computer.
l For the server that has multiple network cards, obtain the license for only the master network
card that is used by the T2000.
l Never make any modifications to the license file. Otherwise, the license will fail.
l Ensure that there is only one License file in the license folder of the T2000 server directory.
l On Solaris, FTP the license file to a workstation as user t2000 in the mode of ASCII.
l On SUSE Linux, FTP the license file to a workstation as user t2000 in the mode of ASCII.
l The license of the T2000 V200 is incompatible with that of the T2000 V100. If you have
upgraded the T2000, reapply for a license.
l The items that the license supports vary with different versions of the T2000. You must
use the application form template specific to that T2000 version when applying for the
license.
2.8.2 Obtaining a T2000 License

Use this procedure to obtain for the T2000 license.
Context
l The T2000 license file is not sent to the customer with the T2000 installation DVD-ROM,
but is applied by the Huawei engineer according to the contract number and the MAC
address.
l When users need to change the T2000 computer server or increase the management
capability of the server, they need to feed back the MAC address and the contract number
to a Huawei engineer for the T2000 license.
l The Huawei engineer applies for a T2000 license according to the contract number and the
MAC address.
Procedure
Step 1 Get the contract number in project documents.
There are 14 integers in the contract number.

For example, 123456 (post code) 010811 (date) 10 (serial number).
Step 2 Get the MAC address of the server.
In Windows:
1. Click Start,select Programs > Accessories > Command Prompt.

2. In the Command Prompt window, enter ipconfig /all.
The display is as below:
3. Get the MAC address.

In this example, the MAC address is 00-50-BA-19-58-35.
In Solaris 10:
1. Open a Terminal.
2. Run the following command to switch to user root:
% su - root
NOTE
Enter the password of user root according to the screen prompt. The default password is root.
3. Run the following command to view the MAC address:
# ifconfig -a
The terminal display is as below:

4. Get the MAC address in the interface.

In this example, the MAC address is 0:14:4f:f:e2:20.
Step 3 Send the contract number and the MAC address to a Huawei engineer or the nearest branch.
Step 4 The Huawei engineer fills in the application form to obtain a T2000 license.
Step 5 After the Huawei engineer obtains the T2000 license, she or he sends it to the customer.
----End
2.8.3 Installing a T2000 License

Use this procedure to install the a license on the computer of the T2000 server.
Prerequisite
The T2000 license file is ready.
Context
To install the T2000 license, you can copy the license file to the license directory of the
T2000.
NOTE
l If the T2000 server is installed on SolarisSUSE Linux, copy the license to the T2000/server/license
directory (the default directory is /T2000/server/license).
l If the T2000 server is installed on Windows, copy the license to the T2000\server\license directory
(the default directory is C:\T2000\server\license).
Procedure
Step 1 Exit all the T2000 client software.
Step 2 Shut down the T2000 server software.
Step 3 On the computer where the T2000 server is installed, transfer the license file in ASCII mode by
FTP to the T2000 installation directory server/license as user t2000.
Step 4 On the computer where the T2000 server is installed, copy the authorized license file to the
T2000 installation directory server\license as the user that installs the T2000.
Step 5 Restart the T2000 server software.
----End
Result
Then the license can take effect. Choose Help > About from the Main Menu and then click
License to check the license information when the T2000 client is started.
2.8.4 Changing the License

You can change the license in the T2000 server by using the T2000 client.

Prerequisite
l Log in to the T2000 as user admin.
l The T2000 license must be obtained.
Context
NOTE
l When the types of equipment supported by the new license are different from those supported by the
old license, do as follows:
l You can change the license if additional types of equipment are supported by the new license and
if the additional equipment types are supported by the current T2000 version. You cannot change
the license if the additional equipment types are not supported by the current T2000 version.
l You can change the license if some types of equipment are no longer supported by the new license
and if no NEs are created on the T2000 for the unsupported equipment types. You cannot change
the license if NEs have been created on the T2000 for the unsupported equipment types.
l You cannot change the license if the new license supports different function items than the old license.
l When the new license supports a different number of clients than the old license, do as follows:
l You can change the license if the new license supports lesser number of clients than the old license
and if the number of the currently logged-in clients is lesser compared to the clients of the new
license. You cannot change the license if the currently logged-in clients are more than the number
of clients of the new license.
l You can change the license if the new license supports more clients than the old license.
For situations where you cannot change the license, shut down the T2000 server, change the license and
then restart the server.
Procedure
Step 1 Backup the original license from the T2000 server.
NOTE
l If the T2000 server is installed on Solaris, create a folder backup in the default directory /T2000/
server/license/backup, and copy the license to the directory /T2000/server/license/backup.
l If the T2000 server is installed on SUSE Linux, create a folder backup in the default directory /T2000/
server/license/backup, and copy the license to the directory /T2000/server/license/backup.
l If installed on Windows, create a folder backup in the default directory \T2000\server\license\, and
copy the license to the directory \T2000\server\license\backup.
Step 2 Delete the original license from the T2000 server, and copy the new license that is authorized
to the license directory of the T2000 server.
NOTE
l If the T2000 server is installed on Solaris, copy the license to the default directory /T2000/server/
license/.
l If the T2000 server is installed on SUSE Linux, copy the license to the default directory /T2000/server/
license/.
l If installed on Windows, copy the license to the default directory\T2000\server\license\.
Step 3 Choose Help > About from the Main Menu. Click the License tab. Then, click Update. In the
Open dialog box displayed, select the new license file and click Open.
Step 4 If the license file is invalid, follow the procedure described as follows to check the correctness
of the license.

Check the correctness of the license on Solaris.
1. Run the following command to get the MAC address of the host computer.
# ifconfig -a
The screen displays:

eri0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.70.76.221 netmask ffffff00 broadcast 10.70.76.255
ether 8:0:20:c4:8f:db
The characters that follow "ether" is the MAC address of the network card. The MAC
address format is xx:xx:xx:xx:xx:xx, where xx is one or two hexadecimal numbers.
NOTE
You must run the ifconfig -a command as user root to get the MAC address of the host computer.
2. View the license file by the more command.
# cd /T2000/server/license
# more licenseXXXXXXX.txt

SupportIPEndToEnd = 1
SupportWaveEndToEnd = 1
MAC = 8:0:20:c4:8f:db
License = A26F90385ACE5FD947F057C36786A4C5E33E1C854AB410A11292
0687F007548AF4A586BBE902313F309F6A82DD19
The characters that follow "MAC=" is the MAC address of the network card that
corresponds to the license. Check whether the two MAC addresses are the same or not. If
not, get the proper license file.
3. Make sure that /T2000/server/bin/imapgetmac is owned by root, and the permission is
4755.
4. Check whether the text mode, namely ASCII mode, is adopted to transfer the license file.
NOTE
To check the transfer mode, open the licenseXXXXXXX.txt 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.
Check the correctness of the license on SUSE Linux.
# ifconfig -a

NOTE
You must run the ifconfig -a command as user root to get the MAC address of the host computer.



MAC = 8:0:20:c4:8f:db
0687F007548AF4A586BBE902313F309F6A82DD19
3. Make sure that /T2000/server/bin/imapgetmac is owned by root, and the permission is
4755.
4. Check whether the text mode, namely ASCII mode, is adopted to transfer the license file.
NOTE
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.
Check the correctness of the license on Windows.
1. Choose Start > Programs > Accessories > Command Prompt to start a command
terminal. Run the following command.
ipconfig /all

Connection-specific DNS Suffix . : huawei.com
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 8:0:20:c4:8f:db
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
The characters that follow "Physical Address" is the MAC address of the network card.
2. Open the license file.

MAC = 8:0:20:c4:8f:db
License = A26F90385ACE5FD947F057C36786A4C5E33E1C854AB410
A112920687F007548AF4A586BBE902313F309F6A82DD19
3. Check whether the network adapter is available or not.
l 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.

l If yes, re-transfer the license file and store it in the C:\T2000\server\license directory.
Restart the T2000 to see whether it is valid.
----End
2.8.5 How to Correctly Use a License

If the T2000 server is installed on the Solaris or SUSE Linux platform, the
licenseXXXXXXX.txt file is installed in the /T2000/server/license directory. If the T2000 server
is installed on Windows platform, the licenseXXXXXXX.txt file is installed in the C:\T2000
\server\license directory. After you restart the T2000 server program, the license can be
normally applied.
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 or SUSE Linux.
# ifconfig -a

NOTE
You must uses ifconfig -a command as user root to get the MAC address of the host computer.

MAC = 8:0:20:c4:8f:db
0687F007548AF4A586BBE902313F309F6A82DD19
corresponds to the license. Check whether the two MAC addresses are the same or
not. If not, get the appropriate license file.
3. Make sure that $IMAP/imapgetmac is owned by root, and the permission is 4755.
4. Check whether the text mode, namely ASCII mode, is adopted to transfer the license
file.

NOTE
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.
1. Choose Start > Programs > Accessories > Command Prompt to start a command
terminal. Run the following command.
ipconfig /all

Connection-specific DNS Suffix . : huawei.com
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 8-0-20-c4-8f-db
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
The characters that follow "Physical Address" is the MAC address of the network
card.
2. Open the license file.

MAC = 8:0:20:c4:8f:db
License = A26F90385ACE5FD947F057C36786A4C5E33E1C854AB410
A112920687F007548AF4A586BBE902313F309F6A82DD19
corresponds to the license. Check whether the two MAC addresses are the same or
not. If not, get the appropriate license file.
3. 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 C:\T2000\server\license
directory. Re-activate the T2000 to see whether it is valid.
----End
2.9 Starting the Web Client

OptiX OTU40000 and OptiX OSN 900A must be configured through the Web LCT.
Prerequisite
l You must be an NM user with "NE operator" authority or higher.
l Applies to OptiX OTU40000 and OptiX OSN 900A.
Procedure
Step 1 Double-click an optical NE on the topology. The NE Panel is displayed.

Step 2 Right-click an NE and choose Start WEB Client from the shortcut menu. The Web LCT user
interface is displayed.
----End
2.10 T2000 Main Window

The T2000 main windows and what you can do in the windows are described here.
2.10.1 Main Topology

Main Topology is the default T2000 client interface, and all topology management functions
can be accessed through this window. These functions include creating topological objects,
subnets, searching for the existing equipment in the network. You can search, view, create, set,
and manage protection subnets; and search, create, configure, and maintain management
functions on trails.
2.10.2 NE Explorer
The NE Explorer is the main user interface used to manage OptiX 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.
2.10.3 Clock View
The Clock View provides a visible platform to enable NE clock settings, networkwide clock
synchronization status query, clock tracing and search functions. Applies to the SDH and RTN
equipment.
2.10.4 SDH NE Panel
The SDH NE Panel displays boards and ports in different colors depending on their current
status. In the T2000, most operations such as equipment configuration, monitoring, and
maintenance are performed in the NE Panel window.
2.10.5 RTN NE Panel
The RTN NE Panel displays boards and ports in an NE. The color of the component icon indicates
the current status. On the T2000, the NE Panel is an important user interface for configuring,
monitoring and maintaining the equipment.
2.10.6 WDM NE Panel
The WDM NE Panel displays subracks, boards, and ports in different colors depending on their
current status. In the T2000, most operations such as equipment configuration, monitoring, and
2.10.7 PTN NE Panel
The NE Panel displays boards and ports in different colors depending on their current status. In
the T2000, most operations such as equipment configuration, monitoring, and maintenance are
performed in the NE Panel window.
2.10.8 Browse Alarm and Event Window
You can view the current and history alarms, abnormal events, and alarm statistics. This window
provides buttons, such as correlation analysis, filter, refresh, synchronize, check and
acknowledge, to help you to quickly locate the alarm cause.
2.10.9 Browse Performance Window

You can view the current and history performance data, UAT events and performance threshold
crossings.
2.10.10 Operation Object Status
The meaning of legends on a view is described here.
2.10.11 Key GUI Components
The key T2000 GUI components are as follows:
2.10.12 Frequently Used Buttons
The frequently used buttons on the T2000 GUI are as follows:
2.10.13 Shortcut Icon
The shortcut icons in the Main Topology, NE Explorer and NE Panel are described.
2.10.14 Common Shortcut Keys
Using shortcut keys, you can increase the operation efficiency. The shortcut keys include Enter,
Ctrl, Esc, Tab and so on.
2.10.1 Main Topology

Main Topology is the default T2000 client interface, and all topology management functions
can be accessed through this window. These functions include creating topological objects,
subnets, searching for the existing equipment in the network. You can search, view, create, set,
and manage protection subnets; and search, create, configure, and maintain management
functions on trails.
GUI
To open the Main Topology, log in to the T2000, and choose Window > Main Topology from
the Main Menu. Figure 2-1 shows the Main Topology of the T2000.

Figure 2-1 GUI
2.10.2 NE Explorer
The NE Explorer is the main user interface used to manage OptiX 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
You can open a maximum of five NE Explorer windows at the same time.
GUI
To display the SDH NE Explorer, right-click an NE on the Main Topology and choose NE
Explorer from the shortcut menu.

To display the WDM NE Explorer, 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.
The NE Explorer window is shown in Figure 2-2.
Figure 2-2 The NE Explorer window of an NE
Customizing a Window
You can select either of the two options to customize the NE Explorer window: Display in
Maximization and Display in Window. By default, the NE Explorer window is displayed in
the display mode that you select.
Choose File > Preferences > Custom Window from the Main Menu. Set the initial display
mode for the NE Explorer window.
NOTE
The window display mode you set is enabled when you open the NE Explorer next time.
If the NE Explorer is already open before you modify the settings, close and open the window again. Thus,
the settings take effect.

2.10.3 Clock View

The Clock View provides a visible platform to enable NE clock settings, networkwide clock
synchronization status query, clock tracing and search functions. Applies to the SDH and RTN
equipment.
GUI
To open the Clock View, choose Configuration > Clock View from the Main Menu. In the
object tree on the left, select the NE that you want to query or set. Figure 2-3 shows the GUI of
the Clock View.
Figure 2-3 Clock View
Legends
l The Clock View uses continuous lines to represent the trace relations 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 NE2 points to NE3, it indicates that NE3 traces the clock information transmitted from
NE2, and that NE3 traces the primary PRC NE1-External 1.
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 trace relations 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 T2000. Therefore, the clock trace relations are not displayed on the Clock View.
l On the T2000, the four clock trace relations of free-run, tracing, holdover, and invalid are
respectively identified in blue, green, yellow, and red.

l In the Clock View, you can select multiple NEs, right-click, and query the clock
synchronization status or search for clock trace 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.
2.10.4 SDH NE Panel

The SDH NE Panel displays boards and ports in different colors depending on their current
status. In the T2000, most operations such as equipment configuration, monitoring, and
GUI
Double-click an NE on the Main Topology to display the NE Panel. See Figure 2-4.
To add a new board, right-click an idle slot and choose a board type.

Figure 2-4 NE Panel
NOTE
l Choose the Always On Top for the Slot Layout window to always remain on top.
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 on the right of the Slot Layout. For example,
Figure 2-5 shows the legends of the OptiX OSN 3500.

Figure 2-5 Legends
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. See Figure 2-6.
Figure 2-6 Path View

2.10.5 RTN NE Panel

The RTN NE Panel displays boards and ports in an NE. The color of the component icon indicates
the current status. On the T2000, the NE Panel is an important user interface for configuring,
monitoring and maintaining the equipment.
GUI
To display the NE Panel, double-click an NE icon on the Main Topology. Figure 2-7 shows the
NE Panel.
To add a board in an empty slot, right-click the slot and select a board type from the shortcut
menu.
Figure 2-7 NE Panel

NOTE
Check the Always On Top check box and the Slot Layout window is not hidden by other windows.
Click on the toolbar, to view the information on the legends of boards and ports in the right-
hand pane. For example, Figure 2-8 shows the legends of the OptiX RTN 620.
Figure 2-8 Legends
To perform an operation on an installed board, right-click the board and select an operation from
the shortcut menu. For example, right-click the PO1 and choose Path View to view the status
of each channel. See Figure 2-9.

2.10.6 WDM NE Panel

The WDM NE Panel displays subracks, boards, and ports in different colors depending on their
current status. In the T2000, most operations such as equipment configuration, monitoring, and
GUI
Double-click an ONE icon on the Main Topology to display the NE Panel, and select the NE.
See Figure 2-10.

Figure 2-10 NE Panel
NOTE
l Choose the Always On Top for the Slot Layout window to always remain on top.
ID of the slave slot is grayed out. For example, in Figure 2-10, slot 11 is the main slot, and slot 12 is
the slave slot.
Figure 2-11 shows the legends of the OptiX 1600G.

Figure 2-11 Legends
from the shortcut menu. For example, right-click an FIU and choose Path View to display the
detailed path information. See Figure 2-12.

2.10.7 PTN NE Panel

The NE Panel displays boards and ports in different colors depending on their current status. In
the T2000, most operations such as equipment configuration, monitoring, and maintenance are
performed in the NE Panel window.
GUI
Take the OptiX PTN 3900 as an example. Double-click an NE on the Main Topology to display
the NE Panel. See Figure 2-13.
Figure 2-13 NE Panel

NOTE
l Check the Always On Top check box for the Slot Layout window to always remain on top.
ID of the slave slot is grayed out. For example, in Figure 2-13, slot 05 is the main slot, and slot 06 is
the slave slot.
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.
Figure 2-14 shows the legends of the OptiX PTN 3900.
Figure 2-14 Legends
from the shortcut menu. For example, right-click an MP1 board and choose Path View to display
the detailed path information. See Figure 2-15.

2.10.8 Browse Alarm and Event Window

You can view the current and history alarms, abnormal events, and alarm statistics. This window
provides buttons, such as correlation analysis, filter, refresh, synchronize, check and
acknowledge, to help you to quickly locate the alarm cause.
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 Event from the Main Menu.
l Choose Fault > Alarms Statistics from the Main Menu.
See Figure 2-16.

Figure 2-16 Browse Alarm and Event
2.10.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.
Figure 2-17 shows the window of SDH performance.
Figure 2-18 shows the window of WDM performance.

Figure 2-17 Browse SDH Performance

Figure 2-18 Browse WDM Performance
2.10.10 Operation Object Status

The meaning of legends on a view is described here.
On the Main Topology view, click Legend and obtain the meaning of the legends. See Figure
2-19.
Figure 2-19 View legends

NE
Table 2-2 describes each status of the NE icon.
Table 2-2 NE status

NE icon Status
The NE is a non-gateway NE.
The NE is not configured.
The NE is preconfigured.
The NE is a gateway NE.
The data on the T2000 and that on the NE are

inconsistent.
Communication is lost. The NE is not logged

in.
Path and Port

Table 2-3 describes the status of each path and port icon in the Board View.
Table 2-3 Path and port status

Path/Port icon Status
This path is loaded with services (only

applicable to path).
Inloop is set for this path or port.
Outloop is set for this path or port.
Working Status
The working status of an operation object, such as an NE, is shown in different colors. The
Table 2-4 describes the default colors and the corresponding alarm status.

Table 2-4 Working Status

Color Description
Red Critical alarm. Indicates that the current

highest severity alarm of the operation object
is Critical.
Orange Major alarm. Indicates that the current

is Major.
Yellow Minor alarm. Indicates that the current

is Minor.
Dark magenta Warning alarm. Indicates that the current

is Warning.
Green Normal state
Gray Communication interruption. The operation

object has lost its communication with the
T2000.
Light blue Unknown state
2.10.11 Key GUI Components

The key T2000 GUI components are as follows:
Component Example
Button
Shortcut icon
Radio button
Check box
Tab
Field

Component Example
Drop-down
menu
Menu
Function Tree
Dialog box
2.10.12 Frequently Used Buttons

The frequently used buttons on the T2000 GUI are as follows:
Button Functionality
Selects the objects.

Queries the data from the T2000.
Expands all available options.
Collapses all available options.

Displays or hides a dialog box.
Decreases the priority of the selected object.
Increases 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.
Allows the user to view and select the board

ports.
Deletes the selected data or icon.
Closes the operation wizard.
Creates a new service or protection.
Proceeds to the next step.
Returns to the previous step.

Closes the dialog box.
Expands the Object Tree.
Collapses the Object Tree.
2.10.13 Shortcut Icon

The shortcut icons in the Main Topology, NE Explorer and NE Panel are described.
Icon Name Function
Exit Exits the T2000 client.
Lock Terminal Locks the current client.
Log Out Logs out the current user.
Topology Browser Switches to the Main Topology.
NMS User Manages the user information on the

Management T2000.
Browse Current Accesses the Current Alarms tab.

Alarm
Stop the Current Clicks this shortcut to stop the current

Alarm Sound alarm sound at the T2000 side. The
alarm sound starts again when the new
alarm occurs. To permanently stop the
alarm sound, you can choose Fault >
Stop the Alarm Sound Permanently
from the Main Menu.
NE Explorer Displays the window of NE

Explorer.
Create Link Creates fiber and radio links.
SDH Protection Displays the Protection Subnet

Subnet Maintenance window.
Maintenance
SDH Trail Displays the window of SDH trail

Management management.

Icon Name Function
SDH Trail Creation Displays the window of SDH trail

creation.
WDM Trail Displays the window of WDM trail

Management management.
Browse SDH Displays the window for viewing SDH

Performance performance data.
Browse WDM Displays the window for viewing

Performance WDM performance data.
Up Returns to the previous level.
Zoom out Zooms out the Main Topology.
Zoom in Zooms in the Main Topology.
Zoom in Partially Zooms in an area selected in the Main

Topology.
Restore Recovers the view to the size 1:1.
Fit Window According to the position of the NE

icons, changes the display proportion
of the window so that all the NE icons
are displayed in the Main Topology.
Full Screen Mode Displays the view in full screen.
View Move When you click this icon, the Main

Topology display can be moved. When
you click the icon again, the Main
Topology cannot be moved.
Search Locates the NE on the Main Topology.
Topology Displays the navigation tree in the

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

Topology.
Filter Tree and Opens the setting area of the view to

Legend display the filter plane and legends.
Aerial View Opens the Aerial View dialog box to

display the position of the NE icons in
the allover background diagram.

Icon Name Function
Device Statistics Views the quantity of the equipment in

the network, the equivalent coefficient,
and the number of equivalent NEs.
Save the Location Saves the location of the current subnet

of the Current icons.
Subnet Icons
Save the Location Saves the location of all the current

of ALL the Current subnet icons.
Subnet Icons
Refresh View Refreshes the current view.
Lock View Locks the current NE(s).
Unlock View Unlocks the current NE(s).
Show Alarm Panel Opens the Alarm Panel dialog box to

display the statistic data of all the
current alarms by default.
Critical alarms Dynamically displays the number of

current critical alarms that have not
been cleared. When you click this icon,
the information about all the critical
alarms is displayed.
Major alarms Dynamically displays the number of

current major alarms that have not been
cleared. When click this icon, the
information about all the major alarms
is displayed.
Minor alarms Dynamically displays the number of

current minor alarms that have not
been cleared. When click this icon, the
information about all the minor alarms
is displayed.
No new events Dynamically displays abnormal

events. When you click this icon, the
Events window is displayed.
IPA Management Displays the status of IPA

management. When you click this
icon, the IPA Management window is
displayed.

Icon Name Function
NM Tasks Displays the progress 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
T2000.
Switch NE Switches to the NE Explorer of another

NE.
NE Panel Displays the slot layout of the NE.
Back Up NE Backs up the NE database to the SCC.

Database To SCC
Help Opens the Help dialog box.
Tile Tiles the NEs in the Object Tree.
Ascending Lists the objects in the Object Tree in

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

a descending order.
Verify Applies the service settings of the SCC

Configuration board to boards. This operation may
interrupt services.
NE Time Opens the NE Time

Synchronization Synchronization window. You can
click Query to maintain the time
consistency between the NE, T2000
and the NTP server.
Synchronize Keeps the current alarm data on the

Current Alarms T2000 consistent with the alarm data
on NE.
Browse Current Displays a new window for viewing

Alarms current alarms.
Clear Alarm Clears the current alarm indication of

Indication the NE.
Refresh Board Refreshes the board status of the

Status selected NE.

Icon Name Function
Display/Hide Displays or hides the extended slot.

Extended Slot
Legend Displays the Legend pane.
2.10.14 Common Shortcut Keys

Using shortcut keys, you can increase the operation efficiency. The shortcut keys include Enter,
Ctrl, Esc, Tab and so on.
Shortcut Description
Key
Ctrl+A Selects all contents in the list if the cursor is in the list box.
Ctrl+F Quickly finds the desired NE in all views.
Enter If the cursor is in the list box, press Enter once and the cursor moves
downward to the next line. If the cursor locates on a button, pressing
Enter means to confirm the operation.
Esc Closes an alert box and a dialog box.
Tab Switches between text boxes if the cursor is in the list box. Switches between
buttons if the cursor is on a button.
Ctrl+P Prints data.
Ctrl+S Saves data.
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+C Opens the Configuration menu from the Main Menu.
Alt+L Opens the Fault menu from the Main Menu.
Alt+P Opens the Performance menu from the Main Menu.
Alt+N Opens the Protection Subnet menu from the Main Menu.
Alt+C+V Opens the Clock View menu from the Main Menu.
Alt+T Opens the Trail menu from the Main Menu.
Alt+R Opens the Report menu from the Main Menu.

Shortcut Description
Key
Alt+S Opens the System 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.
2.11 Menu Description

The Main Menu and submenus of the T2000 are described as follows.
2.11.1 File Menu

Describes the menu items on the File menu.
2.11.2 Edit Menu
This section describes the menu items on the Edit menu.
2.11.3 View Menu
This topic describes the menu items on the View menu.
2.11.4 Configuration Menu
The configuration menu allows you to configure and manage the network.
2.11.5 Protection Subnet Menu
Describes the menu items on the Protection Subnet menu. It is applicable to the SDH and WDM
and RTN equipment.
2.11.6 Clock View Menu
Describes the menu items on the Clock View menu. It is applicable to the SDH and the RTN
equipment.
2.11.7 Fault Menu
This section describes the menu items of the Fault menu.
2.11.8 Performance Menu
This section describes the menu items on the Performance menu.
2.11.9 Trail Menu
The trail menu allows you to implement the SDH end-to-end management, Ethernet end-to-end
management, WDM end-to-end management, SDH and Ethernet discrete service
management. It is applicable to the SDH and WDM equipment.
2.11.10 Report Menu
The Report menu allows you to create different types of reports.
2.11.11 System Menu
Describe the menu items on the System menu.
2.11.12 Data Center Menu
Data Center menu are used to upgrade the NE software, including backing up NE data before
upgrade and restoring the NE data in the case of an upgrade exception.
2.11.13 Window Menu
Describes the menu items on the Window menu.

2.11.14 Help Menu

The Help menu allows you to view the online Help topics, the version and registration
information about the T2000. The Help menu also allows you to change a license.
2.11.1 File Menu

Describes the menu items on the File menu.
Menu Items
Menu Item Description
New Device Displays the Add Object

dialog box on which you can
create NEs and T2000s.
Link Displays the Add Object

create links.
Subnet Displays the Add Object

create subnets.
View Displays the Create View

create views.
Search for NE Enables to search for the NEs

in the specified IP address
and add the results to the
topology view automatically.
Ping Enables you to check the

communication status
between the NE and the
T2000 on the network layer.
Delete Deletes the selected objects

and their links from the
current subnet.
Delete Device Deletes the selected devices

and their links from the
T2000.
Attribute Displays the information of

the selected topology object.
Fiber/Cable Management Displays the Fiber/Cable

Management window for
you to manage fibers.

Search for Fiber/Cable Displays the Search for

Fiber/Cable window.
Searches and creates fiber/
cable and radio links in
batches.
Fiber/Cable Pipe Management Displays the Fiber/Cable

Pipe Management window
for you to manage fiber pipes.
Print Preview Previews the topology view

before printing it.
Print Prints the topology view on a

paper.
Page Setup Sets the print attributes.
Preferences Sets the tile of the client main

window, output window,
auto-locking, time format,
date format, and view effects.
Lock Terminal Locks the T2000 client

manually.
Change Password Enables you to change the

password of the current user.
Log Out Enables you to log out the

current T2000 client and
return to the user login
interface.
Change Login Server Logs in to the other server

while you do not exit the
current T2000 client.
Exit Enables you to exit the

T2000 client.
2.11.2 Edit Menu

This section describes the menu items on the Edit menu.
Menu Items
Menu Item Function
Search Displays the Search dialog box to search

NEs.

Menu Item Function
Cut Cuts an NE or more and the related fiber/

cable.
Copy Copies an NE or more and the related fiber/

cable.
Paste Pastes the contents that are cut or copied.
Copy to Copies the selected contents to the specified

path.
Move to Moves the selected contents to the specified

path.
Select All Selects all data in the entire network or

subnet.
2.11.3 View Menu

This topic describes the menu items on the View menu.
Menu Items
Menu Item Function
Refresh View Refreshes the current view.
Display Topology Navigator Opens or closes the topology

Navigation Tree.
View Navigator Opens or closes the view

navigation tree.
Filter Tree and Legend Opens or closes the filter tree

and legend panel.
Aerial View Displays the Aerial View

window to view the entire
network.
Device Statistics Displays the Device

Statistics window to view
the statistics of NE.
Move View Moves the current submap as

a whole. You can press Esc to
exit the removing status of
the submap.
Lock View/Unlock View Locks or unlocks the location

of an object in the view.

Menu Item Function
Set Startup Subnet Sets the current submap as

the startup submap.
Save Icon Location Current Subnet Saves the icon location in the
current subnet.
All Subnets Saves the icon location in all

the subnets.
Synchronize View Coordinates Enables you to enter another

T2000 and synchronize the
coordinates of the current
user with the coordinates of
the user that you entered in
the view.
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.
2.11.4 Configuration Menu

The configuration menu allows you to configure and manage the network.

Menu Items
NE Explorer Displays the NE Explorer of

a selected NE, and enables
you to manage NE, configure
board and perform other
operations.
Configuration Data Management Displays the NE

configuration data, and
enables you to perform
operations to ensure that the
NE configuration data on the
T2000 is consistent with that
on the NEs.
NE Time Synchronization Enables you to keep the NE

time synchronous with the
T2000 server time or the
system time of the network
time protocol (NTP).
Automatic Disabling of NE Function Enables you to set whether to

automatically disable the NE
maintenance functions and
set the automatic disabling
time.
Batch Clock Operation Enables you to set the NE

clock quality in batch.
Power Consumption Management Queries the power

consumption of a board.
Sets the power consumption
threshold and queries the
power consumption of an
NE.
ASON Clock Subnet Management Enables you to create or

delete clock subnets, and
manage reference sources
and interface modes.
Expansion Wizard Guides you to complete the

smooth network expansion
and improvement. For
example, it guides you to
change boards, insert nodes
on a fiber, add extended
subracks, upgrade the link
capacity and delete nodes on
a fiber.

Clock View Enables you to configure NE

clock, query the
networkwide clock
synchronous status, and
search for the clock trace
relation.
QoS Template Management Enables you to add, delete,

modify and query the
parameters in the QoS
template.
RPR Enables you to create and

manage the RPR network,
and manage the ER4.
ALC Management Enables you to manage the

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.
Optical Fiber Link Detection Enables you to configure the

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.
Optical Power Management Enables you to query the

board optical power and save
the input power reference
value and the networkwide
reference value.
OVPN Customer Management Enables you to add, modify,

or delete the information
about OVPN customers and
the authority that the T2000
user has to manage OVPN
customers.
Recover ASON NE Guides you to recover the

data of ASON NEs.
SDH ASON ASON Trail Management Displays the SDH ASON

Trail Management window
and manages ASON
services.

TE Link Management Displays the SDH TE Link

Management window and
manages TE links.
Component Link Displays the SDH

Management Component Link
manages component links.
ASON Topology Displays the SDH ASON

Management Topology Management
window and manages the
ASON topology.
Control Link Management Displays the SDH Control

Link Management window
and manages control links.
WDM ASON ASON Trail Management Displays the WDM ASON

Trail Management window
and manages ASON WDM
services.
TE Link Management Displays the WDM TE Link

manages ASON WDM TE
links.
ASON Topology Displays the WDM ASON

Management Topology Management
window and manages ASON
WDM topology.
Control Link Management Displays the WDM Control

Link Management window
and manages WDM control
link.
2.11.5 Protection Subnet Menu

Describes the menu items on the Protection Subnet menu. It is applicable to the SDH and WDM
and RTN equipment.
Note
A wavelength protection subnet cannot be created by using the T2000. You need to successfully
complete the physical connections, and use the T2000 to search for the wavelength protection
subnet.

Menu Items
Create Radio Protection Subnet Create a radio protection subnet. For

example, IF_1+1, IF_N+1.
Create SDH Protection Subnet Creates an SDH protection subnet. For

example, 2f_MS SPRing, 2f_MS DPRing,
4f_MS SPRing, PP(Diverse Route), PP
(Uniform Route), DNI, 1+1 linear MSP, M:N
linear MSP, NP ring and NP chain.
SDH Protection Subnet Search Searches for SDH protection subnets for the
management and maintenance of protection
subnets.
SDH Isolated Node Management Uniformly manages SDH isolated nodes.

You can query and delete the SDH isolated
nodes.
SDH Protection Subnet Management Manages SDH protection subnets. You can
adjust the capacity, set protection subnet
parameters and query information about
protection subnet configuration.
SDH Protection Subnet Maintenance Maintains SDH protection subnets. You can
start and stop the MSP protocol, perform
protection switching and view the protection
status.
SDH Protection Type Change Changes the protection type from non-
protection chain to 1+1 linear MSP.
Query Networkwide MS Switching Status Query information about all MS Switching

Status in the T2000.
Check Networkwide MS Parameters Check all the parameters of MS in the

T2000.
SDH NNI Browse Provides information about all SDH NNIs in

the T2000.
SDH NNI Management Manages SDH NNIs. You can create and
delete an SDH NNI, and view its details.
WDM Protection Subnet Search Searches for wavelength protection subnets.

You can set the name of a protection subnet,
and view its status and type.
WDM Isolated Node Management Uniformly manages isolated nodes in a

wavelength protection subnet. You can query
and delete the isolated nodes.

WDM Protection Subnet Management Manages wavelength protection subnets. For

example, you can set protection subnet
parameters and query information about
protection subnet configuration.
WDM Protection Maintenance Maintains WDM protection subnets. You can

perform protection switching and view the
protection status.
2.11.6 Clock View Menu

Describes the menu items on the Clock View menu. It is applicable to the SDH and the RTN
equipment.
Navigation Path
Choose Configuration > Clock View from the Main Menu and the Clock View menu is
displayed.
Menu Items
NE Clock Setting Clock Synchronization Enables you to query the

Status clock synchronization status
of an NE. In detail, you can
view the NE clock working
mode, S1 byte
synchronization quality
information, S1 byte
synchronous clock source,
and data output method in
holdover mode.
Clock Source Priority List Enables you to query and set

the clock source priority list.
Clock Source Reversion Enables you to query and set

Parameter clock source reversion
parameters. For example,
you can set the higher priority
clock source reversion mode
and clock source WTR time.

Clock Source Switching Enables you to query and set

Condition the switching condition of a
clock source. For example,
you can display and set the
enable status of the switching
conditions.
Clock Source Switching Enables you to query the

clock source switching
status, and perform clock
source switching.
Phase-Locked Source Output Enables you to query and set

by External Clock the phase-locked source
output by the external clock,
and all parameters of the
external clock output
interface.
Clock Subnet Settings Enables you to query and set

the clock subnet to which an
NE is associated, and enables
you to set the clock source ID
and the SSM protocol.
Query Networkwide Clock Synchronization Status Enables you to query the

clock synchronization status
of each NE managed by the
T2000.
Clock Trace Search Enables you to search for the

current clock trace relations.
2.11.7 Fault Menu

This section describes the menu items of the Fault menu.
Menu Items
Menu Item 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 Event Sets the filter criteria to

browse the events.

Menu Item Function
Synchronize Networkwide Alarms Sends the data of uncleared

alarms on the NE to the
T2000 so that the T2000 can
correctly display the current
alarm status.
Alarm Statistics Collects alarm statistics.
Show Alarm Panel Shows or hides the alarm

panel.
Brows Remote Notification Logs Sets the filter criteria to

browse the remote
notification logs
Settings Alarm Attribute Template Customizes alarm attributes

and applies the template to
NEs.
Alarm Correlation Analysis Sets the alarm correlation

rules.
Remote Notification Sets alarm remote

notification to notify the
maintenance personnel of the
specific alarms by email or
SMS.
Auto Acknowledgement Sets the rules of alarm auto

acknowledgement.
Auto Synchronization Sets the rules of alarm auto

synchronization.
Redefine Alarm/Event Sets the rules of redefining

alarms or events.
NE Alarm/Event Filter Sets the rules of masking

device alarms or events. The
alarms or events that meet the
condition are filtered.
NMS Alarm/Event Filter Sets the rules of masking

NMS alarms or events. The
alarms or events that meet the
condition are filtered.
Set Fault Diagnosis Rules The system provides

diagnosis rules of common
faults. You can customize the
fault diagnosis rules,
including alarm cause,
diagnosis methods, and
troubleshooting methods.

Menu Item Function
Stop the Alarm Sound Permanently Sets the alarm panel not to
play the alarm sound.
Stop the Current Alarm Sound Stops the current alarm sound
and plays the alarm sound
again when a new alarm is
raised.
Alarm Box Sets alarm communication

parameters and alarm
severities for audio-visual
notification.
Synchronize Alarm Box Data Sends the current alarm data

to the alarm box so that the
alarm box can indicate the
current alarm status.
Import/Export Template Exports the alarm or event

browse template as a file.
You can import the template
from the file in the future.
Start OAMS Starts OAMS.
2.11.8 Performance Menu

This section describes the menu items on the Performance menu.
Menu Items
Browse SDH Performance Views 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 SDH Control Plane Performance Queries or sets the current performance data,
history performance data, and threshold-
crossing records of the NEs on the SDH
control plane.
Browse WDM Control Plane Performance Queries or sets the current performance data,
history performance data, and threshold-
crossing records of the NEs on WDM the
control plane.

History Performance Data Analysis Sets the monitoring filter criteria, such as the
monitor period, time range and data source of
the performance time so that the T2000 can
analyze the history performance data of the
monitored object.
Medium-Term and Long-Term Performance Sets different forecast conditions by which

Forecast the T2000 can forecast the medium-term and
long-term performance data. The T2000 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 Threshold Template Customizes different performance threshold

templates for different NEs.
NE Performance Monitoring Time Sets a time range during which the NE

performance is monitored, and set the 15-
minute or 24-hour monitor mode.
2.11.9 Trail Menu

The trail menu allows you to implement the SDH end-to-end management, Ethernet end-to-end
management, WDM end-to-end management, SDH and Ethernet discrete service
management. It is applicable to the SDH and WDM equipment.
Menu Items
SDH Trail Creation Enables you to create an SDH

trail. You need to set the
parameters such as the trail
direction, level, resource usage
strategy, protection priority
strategy, source and sink of the
route, customer name and so on.
SDH Trail Create Manually Enables you to manually create

an SDH trail. You need to set the
direction, level, source and sink
of the route, customer name and
so on.

SDH Trail Search Searches for the NE layer service

data on the T2000 and the
network-layer protection subnet
information on the T2000 to
form trails and display related
information.
SDH Trail Management Enables you to set the filter

criteria, view and set alarms,
view the performance data and
trail status, modify the trail name
and so on.
SDH Discrete Service Management Enables you to set the filter

criteria and view the discrete
service information in the
network, probable cause, and the
direction of the selected discrete
services.
ATM Circuit ATM Trail Creation Enables you to create ATM

trails. You need to set the
parameters such as the source
and sink of the route, Trunk
Link .
ATM Trail Management Enables you to set the filter

criteria, view the alarm and
performance data, ATM Service
OAM, query the trail
information and so on.
ATM Trail Search Searches for the NE layer service

data on the T2000 to form trails
and display related information.
ATM Discrete Service Display the ATM Discrete

Management Service Management window,
Query the information of ATM
Discrete Service Management.
Ethernet Circuit EPL Creation Enables you to create the EPL

trails.
EVPL Creation Enables you to create the EVPL

trails.
Unterminated EPL Enables you to create the

Creation unterminated EPL trails.
EPLAN Creation Enables you to create the

EPLAN trails.

RPR EVPL Creation Enables you to create the RPR

EVPL trails.
RPR EVPLAN Creation Enables you to create the RPR

EVPLAN trails.
EVPL (QinQ) Creation Enables you to create the EVPL

(QinQ) trails.
Ethernet Trail Search Enables you to select a search

mode to search for Ethernet
trails, including Ethernet trail,
trunk link and discrete Ethernet
service.
Ethernet Trail Management Enables you to configure, view

and maintain the Ethernet trails.
Ethernet Discrete Service Enables you to view and count

Management the Ethernet discrete services,
including private line service,
LAN service, binding relation
and discrete RPR.
Trunk Link Trunk Link Creation Enables you to create trunk links
after you set parameters such as
the bandwidth, port attributes
and so on.
Unterminated Trunk Link In a single station mode, create

Creation the Trunk Link at an NE.
Trunk Link Management Enables you to configure, view

and maintain the trunk links, and
to adjust the bandwidth of a trunk
link.
Tunnel Tunnel Creation Enables you to create static

Tunnel and dynamic Tunnel.
Static Tunnel Management Enables you to manage the static

tunnel.
Dynamic Tunnel Enables you to manage the

Management dynamic tunnel.
PTN Service L3VPN Service Creation Enables you to create L3VPN

service.
L3VPN Service Enables you to manage L3VPN

Management service.
Create L2VPN E-Line Enables you to create L2VPN E-

Service Line service.

L2VPN Service Enables you to manage L2VPN

Management service.
CES Service Creation Enables you to create CES

service.
ATM Service Creation Enables you to create ATM

service.
CES Service Management Enables you to manage CES

service.
ATM Service Management Enables you to manage ATM

service.
Emulation Service Search Enables you to search emulation

service, including ATM service,
CES service and static Tunnel.
WDM Trail Creation Enables you to create WDM

trails. You need to set the
direction, level, source and sink
of the route, customer name and
so on.
WDM Trail Management Enables you to set the filter

criteria, view the alarm and
performance data, maintain the
trails, query the trail information
and so on.
WDM Trail Search Enables you to set the pre-search

handling, collision trails
handling and after-search
handling policies. In addition, it
searches for the NE layer service
data on the T2000 to form trails
and display related information.
Alarm Affected SDH Trails Displays the Alarm Affected

SDH Trails window on which
you can set the filter criteria and
view the alarm and performance
data.
Alarm Affected WDM Trails Displays the Alarm Affected

WDM Trails window on which
data.

Alarm Affected ETH Trails Displays the Alarm Affected

ETH Trails window on which
data.
Customer Management Enables you to create, modify

and delete the customer
information including the
customer name, legal
representative, phone number,
email, address, postal code and
remarks.
2.11.10 Report Menu

The Report menu allows you to create different types of reports.
Menu Items
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/Cable
and Fiber/Cable length.
Timeslot Allocation Diagram Creates the timeslot allocation diagram. This

report contains detailed information about
timeslot allocation for the specified
protection subnet.
NE Information Report Creates the NE information report. This

report contains the configuration information
of the selected NE.
Physical Location Information Report Creates the physical location information

report. This report contains information about
the equipment rooms, cabinets and subracks.
Equivalent NE Statistics Report Displays the NE type, NE Count, Statistics of

Equivalent Number.
Port Resource Report Provides the information of ports on all

boards of the selected NE.

Board Information Report Creates the board information report. This

report contains information about the board
configuration, slots and board count.
Board Manufacturer Information Report Provides the information of board code, type,
manufacturing data and BOM.
Low Order Cross-Connections Statistic Displays the capacity of lower order cross-
Report connections, available lower order cross-
connections on each NE, and specifies
thresholds of lower order cross-connection
alerts.
WDM Protection Group Switching State Displays the switching status information of
Report WDM protection groups.
WDM NE Master-Slave Subrack info Report Provides the information of WDM NE

Master/Slave Subrack.
Fiber Cable Occupancy Resources Provides the information of fiber name, level,
source NE, source board, source port, sink
NE, sink board, sink port, direction.
SDH Trail Statistics between NEs Displays the trail information between SDH
NEs.
TU Port Resource Statistics Displays the SDH tributary port information,

such as Total Ports, Configured Port, and
Used Port.
WDM Client Port Resource Statistics Displays the WDM client-side port
information of the NE that is selected, such as
Service Type, Total Port Number, and
Activated Port Number.
WDM Statistics on Inter-Station Wavelength Displays the statistics on the resources of

Resources wavelengths among WDM stations.
Port Resource Statistics EPL Displays the port resources of the Ethernet
board of the NE that is selected, such as NE
Name, Board Name, Used MAC Port, and
Unused Trunk Port.
Ethernet Inter-NE Service Resource Statistic Displays the resources of the services
between the NEs that are selected, such as
Source NE, Sink NE, EPL Number, EVPL
Number, and EVPL(QinQ) Number.
2.11.11 System Menu

Describe the menu items on the System menu.

Menu Items
Browse NMS Log Sets the filter conditions to

browse the operation logs
and security logs.
Log Forwarding Server Sets log forwarding server

parameters.
Import/Export Script File Imports or exports the script

files to restore or backup the
data of the T2000, NE and
network configuration.
Configuration Upgrade Wizard Guides you to use the backup

configuration data script to
restore the T2000 database.
NMS User Management Manages NE users, user

groups, and operation sets.
For example, set the security
properties and assign the
related rights.
Monitor User Operations Sets the filter conditions to

monitor user operations.
Remote Maintenance User Management Displays the Remote

Maintenance User
Management window for
you to set the remote
maintenance user
parameters.
NMS Security Settings ACL Sets the global ACL. Only

the IP addresses in the ACL
can access the T2000.
Security Policies Sets the global security

policy of the T2000,
including the password
policy and the account
policy.
Single User Mode Sets whether the T2000 uses

the single user mode. In
single user mode, only one
client can log in to the
T2000 server.
NE Security Management Enables you to perform NE

user management, NE login
management, NE login lock,
NE setting lock.

Database Dump Settings Sets the parameters for alarm

dump, event dump, and log
dump.
Dump Manually Enables you to manually

dump the logs or data, such as
user logs, device logs, alarm
data, or event data.
Database Backup Backs up all the data in the

database to a specified
location.
Schedule Task Management Enables you to set, cancel or

issue the command of the
following functions:
scheduled database backup,
scheduled security log
dumping, scheduled script
export, periodical
performance data collection
and scheduled ASON
information refreshing.
DCN Management Enables you to configure

NEs and the gateway NE.
Naming Define Rule Displays the Naming Define

Rule window for you to
customize the naming rule of
a fiber/cable, or a trail.
NE Deploy Management Enables you to deploy an NE

Manager of the NE. In this
case, you can migrate the NE
from an NE Manager to
another NE Manager of the
same type.
NE Time Localization Management Enables you to query or

modify the NE time zone and
set the daylight saving time.
Data Collection Run the data collection

module, When the NE is
faulty, you can use this
module to collect the fault
data accurately and
completely. This helps to
locate the equipment fault
quickly.

Maintenance Personnel Information Enables you to add, modify,

or delete the information on
the maintenance personnel.
Device Maintenance Information Enables you to view the

maintenance information on
the selected device in the
topology view.
2.11.12 Data Center Menu

Data Center menu are used to upgrade the NE software, including backing up NE data before
upgrade and restoring the NE data in the case of an upgrade exception.
Menu Items
Field Description
Device Operation Manages the equipment in the network.
Task Management Manages software loading tasks.
Software Archive Management Manages board or path software.
Log Management Provides logs of software loading tasks.
Options Configures the data management and system

policies and manages the license file.
Board Level Software Upgrade Configures the board level software upgrade.
Board Level Patch Software Upgrade Configures the board level patch software
upgrade.
License Management Manages the license.
Backup Log Backup logs.
2.11.13 Window Menu

Describes the menu items on the Window menu.
Menu Items
Menu Item Function
Close Closes the current window.

Menu Item Function
Close All Closes all open windows exclude theMain

Topology.
Minimize Minimizes the current window.
Minimize All Minimizes all the open windows.
Display Tab Bar Sets whether to display the tab bar.
Cascade Cascades 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.
2.11.14 Help Menu

The Help menu allows you to view the online Help topics, the version and registration
information about the T2000. The Help menu also allows you to change a license.
Menu Items
Help Topics Contains topics that provide information

about the T2000 functions.
About Contains the T2000 version Component and

registration information. You can also change
a license.
2.12 Custom View

The custom view is a topological view similar to the Main Topology. In the T2000, different
users have different network management scopes. The T2000 provides many view setting modes,
including customizing views and setting to start views. The user can customise a view for the
network topologies and equipment under administration as a working interface. 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:

2.12.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.
2.12.2 Setting Startup Subnet
You can set a custom subnet as the startup subnet.
2.12.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
You must be an NM user with "NE maintainer" authority or higher.
Context
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
Step 1 Choose File > New > View from the Main Menu.
The Create View dialog box is displayed.
Step 2 In the Create View dialog box, select the General tab.
Step 3 In Name, enter the view name.
Step 4 Click on the right of the Background text box. In the Open dialog box, set the background
of the custom view.
Step 5 Click Select Object, and then 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, device, or link is displayed in the Select Object dialog box.
Step 6 In the Select Object dialog box, click Finish.
Step 7 On the Selected Nodes and Selected Links tabs of the Create View dialog box, view the object
selected in the custom view.
Step 8 In the Create View dialog box, click OK.
----End
2.12.2 Setting Startup Subnet

You can set a custom subnet as the startup subnet.

Prerequisite
Procedure
Step 1 Choose View > Set Startup Subnet from the Main Menu. The Set Startup Subnet dialog box
is displayed.
Step 2 Select a subnet in the Set Startup Subnet dialog box, click OK.
Step 3 Restart the T2000 client, and the custom subnet is displayed automatically.
----End
2.13 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 monitor" authority or higher.
Procedure
Step 1 In the right-hand pane of a window, 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.
Step 2 Optional: Click Setting in the shortcut menu and the Column Settings 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
2.14 Customizing Naming Rule

When you create fibers or trails, the T2000 automatically creates the names of the fibers, trails
and ASON trails 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
The naming rule is a string that comprises a series of fields. The T2000 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
Step 1 Choose System > Naming Define Rule from the Main Menu. The Naming Rule dialog box is
displayed.
Step 2 Choose Function Configuration > Fiber/Cable from the Function Tree. The naming rule is
displayed on the right-hand pane.

Step 3 Optional: Click Refresh to obtain the latest naming rule customized by other users.
Step 4 Click Create Rule and enter the name of the newly created rule in the first row.
Step 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.
Step 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.
Step 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.

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

Step 10 Click Save to save the current naming rule and set it as the default rule.
----End
2.15 Copying Table Text Quickly

The T2000 allows you to copy and paste table text. You can copy text from a table to other
programs quickly.
Procedure
Step 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.
Step 2 Switch to another program, and press Ctrl+V. The selected text is copied to the system clipboard.
----End
2.16 Filtering Operation Objects in a View

The topology view displays submaps, 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
Context
l When the T2000 is started, the filter criteria are empty by default. All the topology objects
are displayed.
l When you deselect a filter criterion, the objects matching the criterion are not displayed.
Procedure
Step 1 Choose View > Display > Filter Tree and Legend from the Main Menu, or click on the
toolbar.
The Filter/Legend Panel is displayed on the right of the topology view.
Step 2 In the Filter/Legend panel, click the Filter tab.
Step 3 Click Filter Tree and select Switch. In the Switch Filter Tree dialog box, select the filter tree
template. Click Open.
NOTE
If the object to be filtered is a single NE, connection, or submap, you can click Other Conditions, and
directly enter the object name for filtering.
Step 4 Choose View > Display > Filter Tree and Legend again to close the Filter Tree and
Legend panel.
----End
2.17 Moving Operation Objects

You can move the operation objects that are shown in the Main Topology.
Prerequisite
Procedure
Step 1 Optional: If the view is locked out, choose View > Unlock View from the Main Menu.
NOTE
l In the Main Topology, if a shortcut icon displayed as exists, this indicates that the view is locked
out.
l In the Main Topology, if a shortcut icon displayed as exists, this indicates that the view is
unlocked.
Step 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

2.18 Searching for NEs in a View

This operation enables you to find an NE quickly.
Context
l This operation applies to all the submaps in the topology view, not limited within the current
submap.
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
Step 1 Choose Edit > Search from the Main Menu, or click .
The Search dialog box is displayed.
Step 2 Select the search conditions, which are Search By and Direction.
Step 3 Enter the keyword according to the search mode.
Step 4 Click Search.
All the found records are displayed in the area of NE ID and NE Name.
Step 5 Select an NE from the search result list, and then click Locate. You can also double-click the
NE.
The NE is located in the topology view and navigation tree.
----End
2.19 Counting the Number of NEs

By counting the number of NEs,you can learn the number of NEs that are created on the T2000
and the number of the equivalent NEs. The NEs contain real, preconfigured, and virtual NEs.
Procedure
Step 1 Choose View > Display > Device Statistics from the Main Menu.
Step 2 In the Device Statisticsdialog box displayed, view the number of the NEs.

----End
2.20 Setting Parameters in the List

On the T2000 GUI, the Object Tree is arranged on the left and the parameter list is arranged on
the right. All the parameters are set in the list. To perform operations in the NE Explorer, follow
the procedure.
Context
l If an item in the list is grayed out, it indicates that it cannot be edited.
l If the value of an item in the list is "/", it means that the value of this item is unknown.
l If the value of an item in the list is "-", it means this operation object does not support this
item.
Procedure
Step 1 Select the operation object in the upper left pane of the NE Explorer: NE or board. The functions
that are supported by this operation are displayed on the Function Tree in the lower left pane.
Step 2 Select the desired function in the Function Tree. Click to the left of an icon to expand the
contained subdirectory.
Step 3 Optional: Click and the data saved on the T2000 is displayed in the list.
Step 4 Optional: Click Query and the data queried from the NE is displayed on the list.
Step 5 Select either of the following ways to set the parameters in the list.
l Double-click a column and the drop-down list or the text box is displayed. Select a proper
item from the drop-down list or enter a desired value in the text box.
l Right-click the item you want to modify, and directly select the proper item from the
shortcut menu.

NOTE
If you want set multiple items, repeat Step 5.
Step 6 Click Apply.
----End
2.21 Operation Precautions

The operation precautions that have to be taken to ensure correct operations are as follows:
l Do not modify the system time when the T2000 is running. Set the time before installing
the T2000.
– To modify the system time of the server, exit the T2000 server and restart it after the
modification.
– To modify the system time of the client, exit the T2000 client and restart it after the
modification.
l Avoid modifying the name and IP address of the T2000 server computer.
l Log in to the T2000 serverE as t2000 on SUSE Linux or Solaris. On Windows, log in with
the same user ID that you had chosen when installing the T2000. Do not change the
Windows user name.
l The data created on the NE is consistent with that on the T2000. When an NE is configured
and runs normally, you can store the data on the NE and the data on the T2000 consistent
through manual or automatic synchronization.
l Back up the T2000 database periodically to minimize the loss caused by abnormal
functioning of the system.
l It is recommended to query the latest data from NE before setting the parameters.
l When a hazardous operation is performed, the T2000 asks for confirmation.
2.22 Rules of Entering Information on User Interface

These rules specify the typing requirements for the text boxes in the T2000 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 T2000 (including the names of the
PDH path, SDH 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 Upper case and/or lower case English letters

l Numerals

l Common symbols: "(", ")", "-", "_", "/", "\", ".", "&", and a space
l When the Western European character set is supported in the operating system, you can
enter Western European characters in certain user interfaces, for example, the user
interfaces of the NE name, trail name, subnet name, and customer name.
The symbols / and \ can only be used in names of an NM (T2000), NE, fiber, trail and protection
subnet and be used in remarks. Note that these characters must be entered in English input mode.
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 T2000 client.
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 "_".
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 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)

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 NM user management, NE user management and
log management.
3.1 Security Management Strategy
The security management function provides the role-based and domain-based management for
the T2000 and NEs. With this function, the T2000 can also monitor in real time the users that
already log in to the T2000 and NEs. In this way, the network and data security ensures that
login failures or illegal operations are captured.
3.2 Users and Rights
This section describes the OS users, database users, and T2000 users. It also describes the
T2000 user management concepts and rights management policies.
3.3 Security Management Processes
Security management processes include the T2000 security management process and NE
security management process.
3.4 Managing SolarisSUSE Linux OS Security
To enhance the Solaris operating system security, the Huawei SetSolaris product is
recommended. SetSolaris complies with the A019 and A020 standards. For SetSolaris security
policy settings, refer to the SetSolaris user manual. Some regular SolarisSUSE Linux security
operations are described here, such as modifying the user password and setting the password
valid period.
3.5 Managing Database Users
The database stores all data for the T2000 system, and is required for data security management.
3.6 Setting the Security Access of the T2000
To ensure the T2000 security, the server communicates with the client by using the SSL protocol.
The system ACL is used to control the IP address of the client that accesses the server.
3.7 Setting Security Policy for a T2000 User
This section describes how to set the security policy for a T2000 user.
3.8 Managing T2000 User Groups

3 Security Management Operation Guide for Common Features
Usually, the T2000 is used by multiple users. You can divide the users into different groups to
control their authorities.
3.9 Managing NM Users
You can create NM users and assign and change their authorities. The NM user authorities are
role-based and domain-based. An equipment set equals a management domain and an operation
set equals an authority group.
3.10 Managing T2000 Operation Sets
The T2000 default operation sets do not meet all user requirements. Hence, the NM administrator
can define an operation set to assign authorities conveniently.
3.11 Managing T2000 Equipment Sets
After the planning and creation of equipment sets, you can assign an equipment set to a specified
user group. In this way, all users in this user group are authorized to operate the equipment in
the equipment set. This management mode helps you uniformly allocate and manage authorities
of the T2000 users.
3.12 Managing T2000 Login
To ensure network data security, you can manage the users who are logged in to the T2000.
3.13 Managing the Remote Maintenance User
The T2000 remote maintenance function allows login to the T2000 server from a remote
maintenance terminal. Strict management for the remote maintenance user not only ensures
T2000 system security, but also makes maintenance operations easier.
3.14 Setting the Security Access of an NE
To ensure the NE security, you need to disable the unused interfaces on the NE.
3.15 Setting the NE ACL
You can ensure the security of NEs by setting the NE ACL.
3.16 Managing NE Users
To ensure NE data security, you can manage the authorities and passwords for NE users.
3.17 Managing NE Login
To ensure NE data security, you can manage the users who are logged in to NEs.

3.1 Security Management Strategy

The security management function provides the role-based and domain-based management for
the T2000 and NEs. With this function, the T2000 can also monitor in real time the users that
already log in to the T2000 and NEs. In this way, the network and data security ensures that
login failures or illegal operations are captured.
The T2000 security management includes NM user management, NE user management, NM
login management, NE login management, and log management. Before using the T2000, 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 T2000 or NEs, and force the logged-in
users at any time to log out of the T2000 or NEs.
3.1.1 Operating System Security Policy
The operating system security is the basic of the secure running of the T2000. It involves many
aspects such as the security of the operating system, anti-virus, and disk security protection.
3.1.2 Database Security Policy
The T2000 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.3 Network Security Isolation Policy
In the network planning, you can configure and plan the data transmission according to certain
network security isolation policy. In this way, you can ensure the security and reliability of the
network and data of the T2000 system, and avoid illegal login and data loss or theft.
3.1.4 T2000 User Security Policy
The T2000 security management mainly involves the objects management, password
management, access control management, and role-based and domain-based management.
3.1.5 Log Management Policy
Log security management includes the T2000 operation log, T2000 security log, NE security
log, log dump, and log forwarding management.
3.1.6 NE Security
The NE security management includes NE access control, NE user management, NE operation
right management and NE data security management.
3.1.1 Operating System Security Policy

The operating system security is the basic of the secure running of the T2000. It involves many
aspects such as the security of the operating system, anti-virus, and disk security protection.
You can take measures in the following aspects to ensure the security of the operating system:
l Operating system security management.
In the case of SUSE LinuxSolaris, refer to 3.4 Managing SolarisSUSE Linux OS
Security to perform the SUSE LinuxSolaris security management.

To use Windows, you can set a password for the CMOS of the T2000 computer and for the
user administrator to ensure the security of the operating system.
l Anti-virus. In Windows, you need to install the anti-virus software. In SUSE
LinuxSolaris, this is not required currently.
3.1.2 Database Security Policy

The T2000 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 Protect the security of the database password. After the T2000 is installed, database users
sa and T2000 user are automatically created. Use the database user password management
tool to change the password immediately . For details, refer to 3.5 Managing Database
Users.
l Back up the database periodically. Copy each backup file to other storage devices. In the
case of a T2000 or database fault, you can use the backup database for restoration. In general
situations, do as follows:
– Back up the MO data once in a day. For details, refer to 10.4.2 Periodically Backing
Up the T2000 MO Data.
– Back up all the T2000 databases once in a week. For details, refer to 10.4.4 Periodically
Backing Up All Data in the T2000 Database.
– Back up the network configuration data of the database by script weekly. For details,
refer to 10.4.6 Periodically Backing Up the T2000 Data by Script.
l View the database status and dump the database periodically. For details, refer to 10.10
Viewing the Status of Databases .
3.1.3 Network Security Isolation Policy

In the network planning, you can configure and plan the data transmission according to certain
network security isolation policy. In this way, you can ensure the security and reliability of the
network and data of the T2000 system, and avoid illegal login and data loss or theft.
To ensure the network security, set as follows:
l Set the network firewall to ensure the network security. You can close some unwanted
service ports of the system to avoid network attacks to the system. For details, refer to
Appendix "Service Ports".
l Set the client-side access control. You can specify the login-permitted range of client IP
addresses to prevent a client beyond this range from accessing the T2000 server. For details,
refer to 3.9.5 Setting the Access Control List of T2000 Users.
l Enable the SSL protocol between the server and client. You can ensure the communication
security if the client logs in to the server in the security mode (SSL). For details, refer to
3.6.1 Setting SSL Protocol Communication Between Server and Client.
l Set the NE access control. By using the T2000, you can control different access modes of
an NE, including 3.14.1 Controlling Communication Between NE and T2000 Through
Ethernet Port, 3.14.3 Setting the NE OAM Access, 3.14.4 Setting the NE COM
Access, 3.14.2 Controlling Communication Between NE and T2000 Through a Serial
Port, and 3.14.5 Controlling Communication Between NE and LCT.
You can also configure DCN protection and set standby GNEs to ensure the reliability of the
network communication. The T2000 communicates with the equipment in a transmission

network by using the primary and standby GNEs. When the communication between the primary
GNE of an NE and the T2000 is interrupted, the T2000 automatically switches to the standby
GNE and communicates with it. After the working DCN channel returns to normal, the
communication automatically switches to the working channel. You can set the switching mode
and the primary and standby GNEs on the T2000. Figure 3-1 shows a sample of the DCN
protection.
Figure 3-1 Sample of the DCN protection

T2000
Primary GNE Standby GNE
DCN
3.1.4 T2000 User Security Policy

The T2000 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 T2000 client user uniquely identifies the T2000
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. The T2000 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.
User Group: This is a collection of the T2000 users that have the same management rights. The
default user groups are administrator group, maintainer group, operator group and monitor
group. The attributes of the user groups include name, description, member and authority.
Equipment Set: This is a collection of multiple pieces of managed equipment. Equipment sets
are established to facilitate the user right management. If a user (or user group) is authorized
with the operation rights of an equipment set, the user (or user group) can perform all the
authorized operations on all the NEs within the equipment set. This saves you the trouble of
setting the management rights for each NE one by one. Equipment 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 T2000 has the following operation sets by default: NM Maintainer Operation Set, NM
Operator Operation Set, NM Monitor Operation Set, Security Maintainer Operation Set, Security

Operator Operation Set, Security Watcher Operation Set, NE Administrator Operation Set, NE
Maintainer Operation Set, NE Operator Operation Set, NE Monitor Operation Set, SDH Network
Maintainer Operation Set, SDH Network Operator Operation Set, SDH Network Monitor
Operation Set, WDM Network Maintainer Operation Set, WDM Network Operator Operation
Set, WDM Network Monitor Operation Set, Ethernet Maintainer Operation Set, Ethernet
Operator Operation Set, Ethernet Monitor Operation Set. If the default operation sets do not
meet the requirements for the right allocation, you can create new operation sets as required.
Password Management
Password Template: The password template defines all the elements required to construct a
password. A good password template effectively raises the complexity of the password and
prevents the password from being decoded. The password template has the following parts:
password composition, password length, and the relation between the password and the user
name.
Password Reuse Frequency and Password Reuse Period: For the purpose of password
security, when you modify a password, you are not allowed to use a previously used password.
The password reuse frequency determines that a new password cannot repeat the one used in
the last N times. For example, if the password reuse frequency is set to 8, the new password
cannot repeat any one that was used during the last eight times. The password reuse period
determines that a password cannot repeat the one used in the past N days. For example, if the
password reuse period is set to 8, the new password cannot repeat any one that was used during
the past eight days.
The Weakness Password Dictionary: This is a collection of the passwords that are easy to be
decoded. If the password being constructed matches an entry in the dictionary, the password is
regarded as invalid. In this case you need to reconstruct a new password. The T2000 provides
a weakness password dictionary that helps to exclude some common passwords that are easy to
be decoded. You can redefine the dictionary as required.
Client Access Control

Remote Maintenance User Management: The T2000 supports the remote maintenance. It
allows a remote maintenance terminal to log in to the T2000 server to perform operations on the
NEs managed by the T2000. 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
T2000 user that logs in to the T2000 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.
Client Access Control: To avoid the illegal login, after you create a T2000 user, you can specify
an IP address range for the accessible clients. In this case, the T2000 user can only log in to the
T2000 server from the clients that are within the IP address range. If you do not specify an IP
address range, a T2000 user can log in to the T2000 server from the clients of local server.
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 T2000 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 T2000.

Client Lockout: To ensure the network security, the T2000 locks out a T2000 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 T2000.
Role-Based and Domain-Based Management

The role-based and domain-based management is based on the allocation of the equipment set
and operation set. The role-based management function (operation set) enables you to divide
the T2000 rights to different function domains. The domain-based management function
(equipment 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 T2000 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 groups cannot be adjusted.
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 T2000.
In this case, even if the user account and the password are obtained by illegal users, these users
cannot log in to the T2000, thus the T2000 security is improved. The T2000 provides two ACLs:
l System ACL
The ACL of the entire T2000. All the users can log in to the T2000 only through specific
IP addresses or network segments.
l User ACL
The ACL of a user. The current user can log in to the T2000 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.
3.1.5 Log Management Policy

Log security management includes the T2000 operation log, T2000 security log, NE security
log, log dump, and log forwarding management.

T2000 Operation Log and Security Log

Operations and operation results of all the T2000 users are recorded in the T2000 operation log
or security log. The T2000 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.
The types of the T2000 logs are as follows:
l T2000 operation log: Records user operations irrelevant to the security on the client. For
example, alarm acknowledgement and alarm synchronization.
l T2000 security log: Records user operations relevant to the security on the client. For
example, user creation and user group creation.
NE Security Log
Operations and operation results of all the NE users are recorded in the NE security log. The
T2000 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 T2000 to periodically save the security
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 dumped file is saved to the \T2000
\server\dump\ directory. The dumped log is saved as a text file and you can view it in EXCEL
format.
Log Forwarding
T2000 log forwarding: The T2000 can forward the T2000 operation log to the Syslog server,
and save all operations. This function provides references for maintenance and relieves the
storage burden of the T2000 server.
NE log forwarding: The T2000 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.6 NE Security
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 T2000 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 T2000 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 T2000 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 five levels. From the lowest level
to the highest level, they are monitor level, operation level, maintenance level, system level and
debug level. 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.
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
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 Users and Rights

This section describes the OS users, database users, and T2000 users. It also describes the
T2000 user management concepts and rights management policies.
3.2.1 OS User
This section describes the OS user types and their rights related to T2000.
3.2.2 Database Users and Authorities
After you install the Sybase database, the system provides a default administrator account sa.
During the database initialization, the system also automatically creates a user account
T2000user.
3.2.3 NMS Users and Rights
This section describes the NMS users and related rights. The NMS user account is used to
perform operations on the T2000 client. In the T2000, the NMS user refers to the T2000 user.
3.2.4 NE Users and Authorities
NE users are mainly used for NE operations. If an NE user wants to operate an NE, the user
must log in to the NE first. Authority of the NE user restricts relevant operations performed to
the NE.
3.2.5 Concepts Related to the T2000 Users
When you perform user management tasks, you need to know some basic concepts, such as the
user, user group, operation set, ACL, managed domain, and operation right. Knowing these
concepts helps you perform user management, especially when rights management is complex.
3.2.6 T2000 User Rights Assignment Policies
When assigning user rights, you need to know the management policies such as the general
policy, user group management policy, and user management policy. These policies help you
to complete user rights management more quickly and accurately.
3.2.1 OS User
This section describes the OS user types and their rights related to T2000.
root
The root user is the default system administrator of the solarislinux operating system.
With the highest right of the operating system, the root user controls all resources, creates other
users, assigns rights to other users, and performs all operations of the operating system. The
root user is responsible for installing or uninstalling the T2000 server application.
administrator
The administrator user is the default system administrator of the Windows operating system.
With the highest right of the operating system, the administrator user controls all resources,
creates other users, assigns rights to other users, and performs all operations of the operating
system. The administrator user is responsible for installing or uninstalling the T2000 server
application.

nmsuser
During the T2000 installation, the T2000 creates a nmsuser user of the operating system
automatically. The nmsuser user is responsible for setting environment variables of the T2000
server and starting the T2000 client at the server.
The nmsuser user has all the rights of its home directory. The file .profile in this directory records
environment variables for the T2000 running.
sybase
The sybase user is responsible for setting Sybase environment variables, installing, maintaining
and managing the Sybase database.
With all the rights of the directory /opt/sybase, the sybase user can manage the Sybase database,
for example, configuring Sybase environment variables and starting/stopping the Sybase service.
3.2.2 Database Users and Authorities

After you install the Sybase database, the system provides a default administrator account sa.
During the database initialization, the system also automatically creates a user account
T2000user.
Table 3-1This section describes the common database users of sa and T2000user and their
authorities.
Table 3-1 Database users and authorities

User Authority
sa sa is the database system administrator account. This account has the highest
database operation authorities. It can manage all resources, create other users,
assign authorities for other users, and perform all operation functions that the
database provides.
T2000user T2000user is a user account that accesses the T2000 database server. This
account is responsible to add, delete, query, and modify the contents of the
T2000 database.
3.2.3 NMS Users and Rights

This section describes the NMS users and related rights. The NMS user account is used to
perform operations on the T2000 client. In the T2000, the NMS user refers to the T2000 user.
After you install the T2000, one default users are created: admin.
The T2000 user accounts and their rights are described as follows:
l admin
The admin user has all the operation rights of NMS operation. You use it to manage the
T2000. The default password is admin. When you for the first time log in to the T2000 as
admin, the system forces you to change the password.
l Other T2000 users

Other T2000 users are created by the admin user. These T2000 users are created base on
the requirements of management.
3.2.4 NE Users and Authorities

NE users are mainly used for NE operations. If an NE user wants to operate an NE, the user
must log in to the NE first. Authority of the NE user restricts relevant operations performed to
the NE.
NE user has the following five levels in ascending order: monitor level, operation level,
maintenance level, system level, and commissioning level. The authorities of the five user levels
are as follows:
l Monitor level: all query commands, NE login and logout, and password change.
l Operation level: all fault and performance settings, some security settings, and some
configurations.
l Maintenance level: some security settings, some configurations, communication settings,
and log management.
l System level: all security settings and all configurations.
l Commissioning level: all security settings, all configurations, and commissioning
command execution.
NOTE
A higher level user has all functions of a lower level user. For example, an operation level user has all authorities
of a monitor level user.
NE user has four user flags. That is, you need to log in to the NE as different NE users for
different network management systems.
l LCT NE user: The NE user used to manage NEs on the LCT.
l EMS NE user: The NE user used to manage NEs on the T2000.
l CMD NE user: The NE user used to manage NEs on the CMD.
l General NE user: The NE user used to manage NEs in the case of any network management
system.
3.2.5 Concepts Related to the T2000 Users

When you perform user management tasks, you need to know some basic concepts, such as the
user, user group, operation set, ACL, managed domain, and operation right. Knowing these
concepts helps you perform user management, especially when rights management is complex.
l User
In different scenarios, the concept of user has different meanings:
– A user who logs in to the T2000 by using a user account and performs operations.
– A user account. For example, creating a user refers to creating a user account.
l Normal user
A user who has non-security operation rights.
l Security administrator
A user who has security subtype rights.
According to the managed groups, there are two types of administrators:

– Local security administrator

The local security administrator (local administrator for short) can query only the user
groups in the managed groups. The local administrator cannot perform the operations
at the group level.
– Global security administrator
The global security administrator (global administrator for short) can query all user
groups and perform the operations at the group level.
l User group
A set of user accounts and rights.
You can assign rights to users by creating a user group and then adding the users to the user
group. The users then automatically inherit all the rights of the user group. You can manage
user rights better by grouping the users.
l Security user group
A user group that has the right to perform the security subtype operations or operation sets.
If a user group has the security rights, the group belongs to the security user group.
l Group administrator
The administrator of a user group that can manage the users in the user group.
l Global group administrator
The administrator of a user group that can manage all user groups. The super user admin
is also a global group administrator.
l Operation set
A set of the operations that can be performed in the T2000.
You can assign an operation set to a user or a user group. This helps you to avoid the trouble
caused by assigning operation rights to users individually and managing users and rights
individually. You can conveniently assign a set of operations to users by creating and
managing an operation set.
l Security operation set
A security operation set is a set of security operations.
l Device set
Device set management enables you to manage the operation rights to the devices in a
device set.
After you plan and create a device set, you can assign the device set to a specified user
group. Then the users in the user group have the operation rights to the devices in the device
set. This helps you to uniformly assign and manage the T2000 user rights.
l ACL
The T2000 supports the function of ACL. The ACL is a secure access control mechanism.
It restricts a user of logging in to the server through only the clients with the specified IP
addresses.
The ACL can effectively control the client IP addresses through which the user can log in
to the T2000. In this case, even if the user account and the password are obtained by illegal
users, these users cannot log in to the T2000; thus the T2000 security is improved. The
T2000 provides two ACLs:
– System ACL
The ACL of the entire T2000. All the users can log in to the T2000 only through specific
IP addresses or network segments.

– User ACL
The ACL of a user. The current user can log in to the T2000 only through specific IP
addresses or network segments.
NOTE
The IP addresses or the network segments for the user ACL cannot exceed the range of the IP addresses
or the network segments for the system ACL.
l Managed domain
A managed domain refers to the physical resources and logical resources managed by the
user or the specific domains managed by the user group.
In the topology view or on the device panel, only the managed objects are displayed. You
can change the managed domain of a user or a user group to change the user rights. The
managed domain is represented as a submap tree (consistent with the physical topology
view).
– If the entire submap tree is selected, the parent submap and all the child submaps in the
parent submap can be managed.
– If the tree is partially selected, the parent submap can be managed, but some child
submaps under it cannot be managed.
– If the tree is not selected, the parent submap cannot be managed, but some child
submaps under it may be manageable.
l Operation rights
Operation rights determine the operations that a user can perform.
l Group-level operations
These are operations performed on user groups. For example, the operations such as setting
the managed domain or operation rights to a user group, creating a user group, or deleting
a user group.
3.2.6 T2000 User Rights Assignment Policies

When assigning user rights, you need to know the management policies such as the general
policy, user group management policy, and user management policy. These policies help you
to complete user rights management more quickly and accurately.
l General policy
Only admin can assign and modify security operation rights, and add a user to a user group
that has security rights. Other operation rights can be assigned by the administrator who
has the assignment right.
l User group management policy
Only admin can create and delete security user groups. As a global administrator, you can
query all user groups, perform the operations at the group level, set the members for normal
user groups, and change the general properties of your own user group. But you cannot
change the operation rights and managed domain of your own user group. As a local
administrator, you can only view the user groups in your managed groups, but you cannot
perform the operations at the group level. If you have no managed group, you cannot view
any user group. You can manage a user group only when it is in your managed user groups.
l User management policy
Only admin can create and delete a security administrator, and manage the validity of a
security administrator. The admin user can change some general properties of admin while
other users cannot change their own general properties. Security administrators can manage

the normal users in the managed user groups of the security administrators. Security
administrators can manage users only when the users are in the managed user groups of
the security administrators.
User management realizes simple division of authority and domain. Division of authority
specifies the operation rights that a user has and division of domain specifies the user groups
that can be managed by a user. You can manage users only when you have security rights
and manageable user groups. If you have manageable user groups and you have the rights
to query the information on a single user and set user operation rights, you can assign all
non-security rights to other users. If you can manage all user groups and you have the rights
to query the information on a single user group and set operation rights of user groups, you
can assign all non-security rights to other user groups. In this case, you cannot assign non-
security rights to your own user group.
l Operation set management policy
Operation set management is not restricted by managed user groups. Only admin can
create, delete, and modify security operation sets. Normal operation sets can be managed
by security administrators, and they are not related to the user groups or users that they
belong to. As a security administrator, if you have the right to manage operation sets, you
can add non-security operation sets.
l Login rights management policy
User login rights are related to security properties. You can set security properties to manage
the login period and the IP address range for login.
3.3 Security Management Processes

Security management processes include the T2000 security management process and NE
security management process.
The T2000 security management process describes the security management operations of the
T2000, and the relations between the operation tasks. See Figure 3-2. During the T2000
deployment, the system administrator should determine the T2000 access control scheme and
security policy, and classify the basic operation set, equipment set, user group, and users
according to the planning and design. In general, the allocation of user authorities and
management domains is controlled by the operation set, equipment set, and user group.
NOTE
A user can use the default operation set, equipment set, and user group provided by the T2000, or customize
them according to the planning.

Figure 3-2 Flow chart of T2000 security management

Required
Optional
Role-Based and
T2000 Access Security Policy of T2000 Login
Domain-Based
Control T2000 User Management
Management
Setting SSL Protocol Setting the Password Creating an Locking the T2000
Communication Template Operation Set Client Screen
Setting the System Setting the Password Creating an Switching a Logged-

ACL of T2000 Reuse Frequency Equipment Set In T2000 User
Configuring the Forcing a T2000 User

Warning Screen for Creating User Groups to Log Out of the
Login T2000
Configuring the Assigning a Managed

Switching to the
Weakness Password Domain to a User
Single User Mode
Dictionary Group
Assigning Operation Setting Automatical

Modifying the T2000 Log-In for T2000
Authorities for User
User Validity Users
Groups
Modifying the T2000

User Password Creating T2000 Users
Validity
Assigning a Managed
Setting the User
Domain to a T2000
Lockout Duration
User
Assigning Operation
Unlocking a T2000
Authorities for T2000
User
Users
Setting the Access

Initializing the T2000
Control List of T2000
User Password
Users
The NE security management process describes the security management operations of the NE,
and the relations between the operation tasks. See Figure 3-3.

Figure 3-3 Flow chart of the NE security management

Required
Optional
NE User NE Login
NE Access Control
Management Management
Controlling Communication
Between NE and T2000 Through Creating an NE User Locking Out NE Login
Ethernet Port
Controlling Communication Changing the NE Locking Out NE

Between NE and T2000 Through User Password Settings
Serial Port
Controlling Communication Querying the NE Switching a Logged-

Between NE and T2000 Through User Information In NE User
OAM Port
Controlling Communication Querying NE Security Forcing an NE User

Between NE and T2000 Through Parameters to Log Out of the NE
COM Port
Controlling Communication Querying NE User Setting NE Login

Between NE and LCT Groups Prompt Message
Setting the NE ACL
3.4 Managing SolarisSUSE Linux OS Security

To enhance the Solaris operating system security, the Huawei SetSolaris product is
recommended. SetSolaris complies with the A019 and A020 standards. For SetSolaris security
policy settings, refer to the SetSolaris user manual. Some regular SolarisSUSE Linux security
operations are described here, such as modifying the user password and setting the password
valid period.
3.4.1 Changing the Password of User root
The password is the proof which can authorize the user to log in the operating system. To meet
the safety and security requirements, you must change the password of user root and keep it
safe.
3.4.2 Changing the Password of User sybase
the security requirements, you must change the password of user sybase and keep it safe.
3.4.3 Changing the Password of User t2000
The password is the proof which can authorize the user to login the operating system. To meet
the safety and security requirements, you must change the password of user t2000 and keep it
safe.

3.4.4 Removing Redundant Hosts Configuration Files

Usually it is not recommended to perform this operation. To prevent the host from being attacked,
you can delete redundant configuration files.
3.4.5 Inhibitting User sybase from Using FTP
The user sybase is used to start and stop the database application. To prevent data in the database
from leakage, this user should be inhibited from using FTP.
3.4.1 Changing the Password of User root

the safety and security requirements, you must change the password of user root and keep it
safe.
Prerequisite
Only the root user of the operating system is authorized to perform this operation.
Context
CAUTION
Periodically change the password of the root user to avoid unauthorized login or intended
damage caused by password disclosure.
Procedure
Step 1 Log in as user root.
Step 2 Run the following command to change the password of user root:
# passwd root
----End
3.4.2 Changing the Password of User sybase

the security requirements, you must change the password of user sybase and keep it safe.
Prerequisite
The root user of the operating system is authorized to perform this operation.
Context
CAUTION
Periodically change the password of the sybase user to avoid misoperations or intended damage
caused by password disclosure.

Procedure
Step 2 Run the following command to change the password of user sybase:
# passwd sybase
----End
3.4.3 Changing the Password of User t2000

The password is the proof which can authorize the user to login the operating system. To meet
the safety and security requirements, you must change the password of user t2000 and keep it
safe.
Prerequisite
The root user of the operating system is authorized to perform this operation.
Context
CAUTION
Periodically change the password of the t2000 user to avoid unauthorized login or intended
damage caused by password disclosure.
Procedure
Step 2 Run the following command to change the password of user t2000:
# passwd t2000
----End
3.4.4 Removing Redundant Hosts Configuration Files

Usually it is not recommended to perform this operation. To prevent the host from being attacked,
you can delete redundant configuration files.
Procedure
Step 1 Enter the following commands:
# rm -f /.netrc
# rm -f /export/home/t2000/.rhosts
# rm -f /export/home/t2000/.netrc
# rm -f /opt/sybase/.rhosts
# rm -f /opt/sybase/.netrc
# rm -f /etc/hosts.equiv
----End

3.4.5 Inhibitting User sybase from Using FTP

The user sybase is used to start and stop the database application. To prevent data in the database
from leakage, this user should be inhibited from using FTP.
Procedure
Step 1 Enter the following command:
# echo sybase >> /etc/ftpd/ftpusers
# echo sybase >> /etc/ftpusers
----End
3.5 Managing Database Users

The database stores all data for the T2000 system, and is required for data security management.
3.5.1 Changing the Password of sa
Change the database user of sa password by using the password management tool, to avoid
misoperations or intended damage caused by password disclosure.
3.5.2 Changing the Password of T2000user
Change the database user of T2000user password by using the password management tool, to
avoid misoperations or intended damage caused by password disclosure.
3.5.1 Changing the Password of sa

Change the database user of sa password by using the password management tool, to avoid
misoperations or intended damage caused by password disclosure.
Prerequisite
Only the t2000 user of the operating system is authorized to perform this operation.
Context
CAUTION
Periodically change the password of a database user to avoid misoperations or intended damage
Procedure
Step 1 Run the password management tool.
l In Solaris, open a terminal window, and run the following commands as user t2000.
% cd /T2000/server/bin
% ./DbPwdTool
l In SUSE Linux, open a terminal window, and run the following commands as user
t2000.

% ./DbPwdTool
l In Windows, switch to the server\bin directory of the T2000 installation path, and double-
click dbpwdtool.exe.
The following information appears.
iManager NMS Database Password Tool
Input '1' to modify sa password.

Input '2' to modify NMS normal user password.
Input 'x' to exit the tool.
Please input your choice:
Step 2 Input 1, and press Enter.

You can press Esc to abort the operation!
Please input the old password of the NMS normal user or sa:
Step 3 Input the old password of sa, and press Enter.

Please input the new password:<sa new password>
Step 4 Input the new password of sa, and press Enter.

Reinput the new password:<sa new password>
Step 5 Input the new password again, and press Enter.

You have changed the password!
Please check the above informations. Be sure there is no any error before restar
ting your NMS.
Step 6 Input x and press Enter.

Thanks,Exit!
Press any key to continue
----End
3.5.2 Changing the Password of T2000user

Change the database user of T2000user password by using the password management tool, to
avoid misoperations or intended damage caused by password disclosure.
Prerequisite
Only the t2000 user of the operating system is authorized to perform this operation.

Context
CAUTION
Periodically change the password of a database user to avoid misoperations or intended damage
Procedure
Step 1 Run the password management tool.
l In Solaris, open a terminal window, and run the following commands as user t2000.
% ./DbPwdTool
l In SUSE Linux, open a terminal window, and run the following commands as user
t2000.
% ./DbPwdTool
l In Windows, switch to the server\bin directory of the T2000 installation path, and double-
click dbpwdtool.exe.
iManager NMS Database Password Tool
Input '1' to modify sa password.

Input '2' to modify NMS normal user password.
Input 'x' to exit the tool.
Step 2 Input 2, and press Enter.

You can press Esc to abort the operation!
Please input the old password of the NMS normal user or sa:
Step 3 Input the old password of T2000user, and press Enter.

Please input the new password:<T2000user new password>
Step 4 Input the new password of T2000user, and press Enter.

Reinput the new password:<T2000user new password>
Step 5 Input the new password again, and press Enter.

You have changed the password!
Please check the above informations. Be sure there is no any error before restar
ting your NMS.
Step 6 Input x and press Enter.


Thanks,Exit!
Press any key to continue
----End
3.6 Setting the Security Access of the T2000

To ensure the T2000 security, the server communicates with the client by using the SSL protocol.
The system ACL is used to control the IP address of the client that accesses the server.
3.6.1 Setting SSL Protocol Communication Between Server and Client
You need to set the SSL protocol communication between the server and client. In this way,
authentication, integrity check and validity check are supported for the input and output data on
the server. After the SSL protocol is enabled, the communication between the client and server
is encrypted and secured. This can avoid hacker attacks.
3.6.2 Setting the System ACL of T2000
The system ACL is the access control of IP addresses for the entire T2000. All the users can log
in to the T2000 only through specific IP addresses or network segments.
3.6.1 Setting SSL Protocol Communication Between Server and

Client
You need to set the SSL protocol communication between the server and client. In this way,
authentication, integrity check and validity check are supported for the input and output data on
the server. After the SSL protocol is enabled, the communication between the client and server
is encrypted and secured. This can avoid hacker attacks.
Prerequisite
You must be an NM user with the "Security Maintainer" authority or higher.
Context
CAUTION
The communication security setting takes effect only after the T2000 server is restarted.
Procedure
Step 1 If the T2000 server is installed on Windows, follow the steps below to enable the SSL protocol
at the server.
1. Open the System Monitor window.
2. Choose System > Communication Mode Settings from the Main Menu. The
Communication Mode Settings dialog box is displayed.
3. Click the Security (SSL) option button.
4. Click OK.

Click OK in the Confirmation dialog box. The settings take effect after the T2000 is
restarted.
Step 2 If the T2000 server is installed on SolarisSUSE Linux, follow the steps below to enable the SSL
protocol at the server.
1. Open a terminal window.
2. Run the following commands on the server:
# cd /opt/HWICMR/bin
# ./enablerootlogin.sh
3. Run the following commands:

# ./runtaskflow.sh all-request.tf
You only need to select or enter a value when setting the SSL. For other steps, press
Enter to proceed until the terminal displays the following information:
======= SSL Protocol =======
Select whether to enable the SSL protocol.

Select "Y" to enable it. Select "N" to disable it.
With the SSL protocol enabled, communication of the client program and server
program are securely encrypted to minimize possible hacker attacks.
Select[N]:
4. Enter Y to enable the SSL protocol.
The terminal displays:

======= Information Confirmation =======
Confirm if the following configuration is correct. Choose "Y" to

continue,
or choose "N" to modify the configuration.
Enable the SSL protocol: Y
Confirm[Y]:
5. Enter Y.

All operations defined in the task flow have been completed.
All operation logs are saved in:
/var/ICMR/ICMR_LOG_20060313150632
6. Run the following command:

# ./runtaskflow.sh config_t2000.tf

Configure OptiX iManager T2000 software........................Done
......
All operations defined in the task flow have been completed.
All operation logs are saved in:
/var/ICMR/ICMR_LOG_20060313150731
After all these operations are complete, the SSL of the server is successfully enabled. The
settings take effect after the T2000 is restarted.

7. Run the following commands on the server:

# ./disablerootlogin.sh
Step 3 On the computer of the T2000 client, double-click the T2000 Client icon on the desktop.
Step 4 Enter the User Name, Password.
NOTE
The server mode of the user need to be set to SSL. The setting method is as follows:
l Setting the mode when creating a server: click , and the Setting window is displayed. Click New.
In the dialog box displayed, set Mode to Security(SSL).
l Modifying the mode for an existing server: click , and the Setting window is displayed. Click
Modify. Set Mode of the server to Security(SSL).
Step 5 Click Login.
----End
3.6.2 Setting the System ACL of T2000

The system ACL is the access control of IP addresses for the entire T2000. All the users can log
in to the T2000 only through specific IP addresses or network segments.

Prerequisite
Procedure
Step 1 Choose System > NMS Security Settings > ACL from the Main Menu. The ACL dialog
box is displayed.
Step 2 Click Add and the Add dialog box is displayed.
Step 3 Set parameters of the IP address or network segment, and click OK.
Step 4 Click Close to close the System ACL dialog box.
----End
3.7 Setting Security Policy for a T2000 User

This section describes how to set the security policy for a T2000 user.
3.7.1 Setting the Password Template

The password template defines the elements that are needed to construct a password. A scientific
and reasonable password template enhances the password complexity and makes it more difficult
to crack.
3.7.2 Setting the Password Reuse Frequency
For security purposes, when a password is changed, the new password cannot repeat old
passwords. The password reuse frequency specifies the number of last passwords that the user
cannot reuse. For example, if the password reuse frequency is set to eight, the user cannot reuse
any of the last eight passwords.
3.7.3 Configuring the Warning Screen for Login
When a user logs in to the T2000, a warning message is displayed to inform the user of relevant
rules that the user must abide by. This message serves as a legal statement. Carriers can define
this message according to their own rules.
3.7.4 Configuring the Weakness Password Dictionary
The weakness password dictionary collects some passwords that can be easily cracked. If a
password repeats any one in the weakness password dictionary, the password is regarded as
invalid, and the user is required to create another one. The T2000 has its own weakness password

dictionary, which includes some common passwords that can be easily cracked. The user can
also re-define the weakness password dictionary as needed.
3.7.5 Modifying the T2000 User Validity
For security purpose, it is not recommended to set a normal T2000 user to be permanently valid.
However, for special users (such as super user and administrator) who always need to manage
the entire system, it is recommended to set these T2000 users to be permanently valid.
3.7.6 Modifying the T2000User Password Validity
To protect the T2000 from illegal logins, you need to periodically change the password of a
T2000 user. You can specify the validity period of passwords, so that the T2000 prompts you
to change the password on a regular basis. You can also set automatic password expiration
warning.
3.7.7 Setting the User Lockout Duration
If a T2000 user never logs in to the T2000 within a specified duration, the user will be locked
out.
3.7.8 Unlocking a T2000 User
To ensure network data security, you can manage users that have logged in to the T2000. You
can lock a user if the user fails to log in for three consecutive times. You can also unlock the
user if necessary.
3.7.9 Initializing the T2000 User Password
If you forget the password, or the password expires, ask the administrator to initialize the
password.
3.7.1 Setting the Password Template

The password template defines the elements that are needed to construct a password. A scientific
and reasonable password template enhances the password complexity and makes it more difficult
to crack.
Prerequisite
You must be an NM user with the "Security Operator" authority or higher.
Context
The password template defines the following elements.
l Password composition: A password may be a combination of numerals, letters, and special
characters. The user can set the minimum number of characters for each type of
components.
l Password length: The user can set the maximum and minimum lengths for a password.
Note that the password minimum length cannot be smaller than the total of the minimum
number settings for the three types of characters.
l Password relation with the user name: The user can set the maximum length of repeated
character string between the password and the user name. In this way, user name and
password repetition can be avoided.
Procedure
Step 1 Choose System > NMS Security Settings > Security Policies from the Main Menu. The
Security Policies dialog box is displayed.

Step 2 Set the password length and modify the Minimum length of normal user password, Minimum
length of super user password, and Maximum password length according to requirements.
l By default, the Minimum length of normal user password is 8.
l By default, the Minimum length of super user password is 8.
l By default, the Maximum password length is 16.
Step 3 Set the minimum number of letters in a password and modify the Minimum letters in the
password according to requirements.
l When you click Cannot enter characters, the password cannot contain letters. In this case,
the Minimum letters in the password cannot be set.
l When the Minimum letters in the password is 0, it indicates that the number of letters in
the password is not restricted.
Step 4 Set the minimum number of upper case letters in a password and modify the Minimum
uppercase letters in the password according to requirements.
l When you click Cannot enter characters, the password cannot contain uppercase letters.
In this case, the Minimum uppercase letters in the password cannot be set.
l When the Minimum uppercase letters in the password is 0, it indicates that the number
of upper case letters in the password is not restricted.
Step 5 Set the minimum number of lower case letters in a password and modify the Minimum
lowercase letters in the password according to requirements.
l When you click Cannot enter characters, the password cannot contain lowercase letters.
In this case, the Minimum lowercase letters in the password cannot be set.
l When the Minimum lowercase letters in the password is 0, it indicates that the number of
lower case letters in the password is not restricted.
Step 6 Set the minimum number of numerals in a password and modify the Minimum numbers in the
password according to requirements.
l When you click Cannot enter characters, the password cannot contain numbers. In this
case, the Minimum numbers in the password cannot be set.
l When the Minimum numbers in the password is 0, it indicates that the number of numerals
in the password is not restricted.
Step 7 Set the minimum number of special characters in a password and modify the Minimum special
characters in the password according to requirements.
l When you click Cannot enter characters, the password cannot contain special characters.
In this case, the Minimum special characters in the password cannot be set.
l When the Minimum special characters in the password is 0, it indicates that the number
of special characters in the password is not restricted.
Step 8 Set the Same Adjacent Characters Allowed in Both User Name and Password.
NOTE
l If you click No requirement, the user name and password are not mutually restricted.
l If you click Cannot contain the full user name, the user name cannot be used as the password.
l If you click Cannot contain n characters, the password cannot contain the same n consecutive characters
in the user name when you set the password. "n" represents the number of characters.

Step 9 Optional: Set the The password cannot contain a word that has the same meaning of
password, The password cannot be a string of the related user name in reverse order, and
The password must meet the complexity requirements according to requirements.
Step 10 Click OK.
----End
3.7.2 Setting the Password Reuse Frequency

For security purposes, when a password is changed, the new password cannot repeat old
passwords. The password reuse frequency specifies the number of last passwords that the user
cannot reuse. For example, if the password reuse frequency is set to eight, the user cannot reuse
any of the last eight passwords.
Prerequisite
Procedure
Step 1 Choose System > NMS Security Settings > Security Policies from the Main Menu. The
Security Policies dialog box is displayed.
Step 2 Set the password reuse frequency and modify the Number of old passwords that cannot be
repeated according to requirements.
NOTE
By default, the Number of old passwords that cannot be repeated is 8.
Step 3 Click OK.
----End
3.7.3 Configuring the Warning Screen for Login

When a user logs in to the T2000, a warning message is displayed to inform the user of relevant
rules that the user must abide by. This message serves as a legal statement. Carriers can define
this message according to their own rules.
Procedure
Step 1 On Windows, open the SecurityConfig.xml file in the %IMAPROOT%\client\style
\defaultstyle\conf\security path. Set the value of PARA name="POPUP_AGREEMENT" to
true.

NOTE
On UNIX, open the SecurityConfig.xml file in the $IMAPROOT/client/style/defaultstyle/conf/

security path. Set the value of PARA name="POPUP_AGREEMENT" to true.
Step 2 Create the loginagreement.txt file in %IMAPROOT%\client\style\defaultstyle\locale

\en_US\security\resources directory.
NOTE
In the case of UNIX, save the file to the $IMAPROOT/client/style/defaultstyle/locale/en_US/security/

resources directory.
Step 3 Enter the contents of the message in the loginagreement.txt file.
Step 4 Save the file.
----End
Postrequisite
Restart the T2000 client to apply the settings.
3.7.4 Configuring the Weakness Password Dictionary

The weakness password dictionary collects some passwords that can be easily cracked. If a
password repeats any one in the weakness password dictionary, the password is regarded as
invalid, and the user is required to create another one. The T2000 has its own weakness password
dictionary, which includes some common passwords that can be easily cracked. The user can
also re-define the weakness password dictionary as needed.
Context
The following illustrates the operations on the UNIX platform. The operations on the Windows
platform are similar.
Procedure
Step 1 Create a temporary directory, for example, /tmp/client.
Step 2 Copy the imap.jar file from /client/lib (in the T2000 client installation directory) to /tmp/
client.
Step 3 Create the common/imap12/security/dict/ subdirectory in the /tmp/client directory.
Step 4 Create the dict1.wrd file in the /tmp/client/common/imap12/security/dict directory.
Step 5 Enter the contents of the password dictionary in the dict1.wrd file, one row for each character
string.
For example:
a
an
a lot of
Step 6 Save the file and exit.
Step 7 Open a terminal window, run the following commands to upgrade the imap.jar file.
# cd /tmp/client
# jar -uf imap.jar common/imap12/security/dict/dict1.wrd

NOTE
If the computer prompts that jar does not exist, install jdk.
Step 8 Replace the existing file with the updated imap.jar file.
----End
Postrequisite
Restart the T2000 client to apply the settings.
3.7.5 Modifying the T2000 User Validity

For security purpose, it is not recommended to set a normal T2000 user to be permanently valid.
However, for special users (such as super user and administrator) who always need to manage
the entire system, it is recommended to set these T2000 users to be permanently valid.
Prerequisite
Context
CAUTION
Maintain the T2000 user validity on a regular basis so as to avoid misoperations or damage
caused by user account theft.
Procedure
Step 1 Choose System > NMS User Management from the Main Menu.
Step 2 In the Security Object area, double-click Users, and select a corresponding T2000 user.
Step 3 Click the General tab.
Step 4 Modify the following user validity parameters: Disable user account and Account validity
(days).

NOTE
l To set permanent validity for the T2000 user, check the Always valid check box on the right of the
Account validity(days) field. In this event, the Account validity(days) cannot be set.
l You cannot set Disable user account and Account validity(days) for user admin.
Step 5 Click Apply.
----End
3.7.6 Modifying the T2000User Password Validity

To protect the T2000 from illegal logins, you need to periodically change the password of a
T2000 user. You can specify the validity period of passwords, so that the T2000 prompts you
to change the password on a regular basis. You can also set automatic password expiration
warning.
Prerequisite
Context
CAUTION
Maintain the T2000 user password validity on a regular basis so as to avoid misoperations or
damage caused by password thefts.

Procedure
Step 4 Modify the following password validity parameters: Password validity(days).
NOTE
To set permanent validity for the T2000 user, check the Always valid check box on the right of the Password
validity(days) field. In this event, the Account validity(days) cannot be set.
Step 5 Click Apply.
----End
3.7.7 Setting the User Lockout Duration

If a T2000 user never logs in to the T2000 within a specified duration, the user will be locked
out.
Prerequisite
l You must be an NM user with the "Security Operator" authority or higher.
l The T2000 user is already created.
Context
During T2000 user creation, the user can also set this parameter as needed. The description given
here is mainly for a created T2000 user.

NOTE
When the user account is locked out, it can only be unlocked by the T2000 administrator.
Procedure
Step 4 Set the period of freezing the user account, and modify the value of Disable user account unused
for(days) according to requirements.
NOTE
l If you do not want to freeze the user account, check the Unrestricted check box on the right of the
Disable user account unused for(days) field. In this event, the Disable user account unused for
(days) cannot be set.
l You cannot set Disable user account unused for(days) for user admin.
Step 5 Click Apply.
----End
3.7.8 Unlocking a T2000 User

To ensure network data security, you can manage users that have logged in to the T2000. You
can lock a user if the user fails to log in for three consecutive times. You can also unlock the
user if necessary.
Prerequisite
When operating in SolarisSUSE Linux, you must log in as user t2000.

Context
There are two ways of unlocking a user, which are automatic unlocking and manual unlocking.
If you choose automatic unlocking, the user automatically changes to the unlocked state after a
specified locking duration. Manual unlocking means that an unlocked administrator unlocks the
locked user in the T2000.
To unlock the locked user "admin", switch to the Sysmonitor Client, and restart the security
process (EmfSecuDm).
Procedure
l Automatic unlocking
1. Choose System > NMS Security Settings > Security Policies from the Main Menu.
The Security Policies dialog box is displayed.
2. Click the Account Policy tab.
3. Modify the value of Auto unlocking time (minutes).
– By default, the value of Auto unlocking time (minutes) is 30. That is, the locking
duration of the user is 30 minutes.
– The minimum locking duration is 1 minutes. The maximum is 600 minutes.
4. Click OK.
After the specified locking duration, the locked user is automatically unlocked.
l Manual unlocking
NOTE
1. Choose System > NMS User Management from the Main Menu.
2. In the Security Object pane, double-click User and select a locked T2000 user from
the T2000 user list.
3. Right-click the user and choose Unlock from the shortcut menu.
----End
3.7.9 Initializing the T2000 User Password

If you forget the password, or the password expires, ask the administrator to initialize the
password.
Prerequisite
Context
When initializing the password, enter a new password. The old password is not required.
However, the old password is required for changing password of the administrator. That is, the
password of the administrator cannot be initialized.
Procedure

Step 2 In the Security Object area, double-click Users and select a corresponding user of the network
management system.
Step 3 Right-click the user and choose Set Password. The Set New Password dialog box is displayed.
Step 4 Enter a new password in the New Password field, and enter it again in the Confirm
Password field for confirmation.
Step 5 click OK.
----End
3.8 Managing T2000 User Groups

Usually, the T2000 is used by multiple users. You can divide the users into different groups to
control their authorities.
1. 3.8.1 Creating User Groups

You can allocate the users that have the same user authority to the sameT2000 user group
so that you can manage users in a uniform manner. This objective can be achieved after
you create user groups that have self-defined authorities.
2. 3.8.2 Specifying Members of a User Group
You can control authorities of the T2000 users in batches by specifying members of the
user group.
3. 3.8.3 Assigning a Managed Domain to a User Group
You can assign a managed domain to a user group, and then the user group can manage the
specific objects, such as a specific submap or a specific device set. By default, a user in a
user group inherits all the rights of the user group. You can change the managed domain
of a user to adjust the user rights.
4. 3.8.4 Assigning Operation Authorities for User Groups
You can assign authority to a T2000 user group. In addition, you can specify the equipment
that the T2000 user group is able to manage.
5. 3.8.5 Setting a User Group Administrator
You can set a user group administrator to manage the users in a user group.
6. 3.8.6 Modifying a User Group
This section describes how to modify the properties of a user group, including the general
properties, members, operation rights, and management rights.
7. 3.8.7 Deleting a User Group
For security purposes, you can delete a user group that is no longer used.
3.8.1 Creating User Groups

You can allocate the users that have the same user authority to the sameT2000 user group so
that you can manage users in a uniform manner. This objective can be achieved after you create
user groups that have self-defined authorities.
Prerequisite

Context
When you assign authorities for users, it is recommended that you directly assign the authorities
to the user groups to which the users belong, to facilitate overall management.
Procedure
Step 2 In the Security Object area, double-click User Groups, right-click and choose New User
Group from the shortcut menu. In the New User Group dialog box that is displayed, enter the
information of a new user group.
Step 3 Click OK.
----End
3.8.2 Specifying Members of a User Group

You can control authorities of the T2000 users in batches by specifying members of the user
group.
Prerequisite
Procedure
Step 2 In the Security Object area, double-click User Groups, and select a T2000 user group.
Step 3 In the right-hand pane, click the Members tab.
Step 4 Optional: Select one or more desired T2000 users and click Delete.
Step 5 Click Add and the Add Users dialog box is displayed.

Step 6 Select one or more user groups that you want to add, and click OK.
----End
3.8.3 Assigning a Managed Domain to a User Group

You can assign a managed domain to a user group, and then the user group can manage the
specific objects, such as a specific submap or a specific device set. By default, a user in a user
group inherits all the rights of the user group. You can change the managed domain of a user to
adjust the user rights.
Prerequisite
l You must be an NMS user with the "Security Operator" authority or higher.
l You can set the managed domain of a user group only when you have the right to manage
all the user groups.
Context
l When the managed domain of a submap is assigned to a user group, the users in the group
can manage all the resources under the submap by default.
l You can manage the resources under a submap only when you have the right to the managed
domain of the submap.
Procedure
Step 1 Choose System > NMS User Management from the main menu.
Step 2 In the Security Object navigation tree, expand the User Groups node, and then select a user
group.

Step 3 Click the Managed Domain tab to view the managed domain of the user group.
Step 4 Click Modify. In the Modify User Group Managed Domain dialog box, modify the state of
the managed domain in the submap navigation tree.
Step 5 Click OK.
----End
3.8.4 Assigning Operation Authorities for User Groups

You can assign authority to a T2000 user group. In addition, you can specify the equipment that
the T2000 user group is able to manage.
Prerequisite
l You must be an NM user with the "Security Maintainer" authority or higher.
l The T2000 user group is already created.
Procedure
Step 2 In the Security Object area, double-click User Groups, and select a T2000 user group.
Step 3 In the right-hand pane, click the Operation Rights tab.
Step 4 Optional: Select one or more desired operation authorities and click Delete.
Step 5 Click Add and the Add Rights dialog box is displayed.
Step 6 Select the type, operation object, subtype, and operation set.

NOTE
l When the type is Transport network NM management and Transport network network
management, the operation objects are transmission network and NM by default. Therefore, you need not
select the Operation Object.
l To search for an operation set, enter the name of the desired operation set in the Operation Set field, and
click Search. This operation applies to the query of multiple operation sets.
Step 7 Click OK.
----End
3.8.5 Setting a User Group Administrator

You can set a user group administrator to manage the users in a user group.
Prerequisite
l You can set a user group administrator only when you have the right to manage all the user
groups.
Procedure
group.
Step 3 On the General tab, click next to Group Managers.

Step 4 In the Set User Group Managers dialog box, select the administrator of the user group.
Step 5 Click OK.
----End
3.8.6 Modifying a User Group

This section describes how to modify the properties of a user group, including the general
properties, members, operation rights, and management rights.
Prerequisite
You must be an NMS user with the "Security Operator" authority or higher.
Procedure
group.
Step 3 on the right area, you can perform the following operations about the user group:
l Click the General tab. on the right list, modify the general properties of the user group, and
then click Apply.

l Click the Members tab to modify the members of the user group.
– Adding a user group member: At the bottom of the list box, click Add. In the Add
User dialog box, select a member you want to add to the group, and then click OK.
– Deleting a user group member: on the right list box, select a user you want to delete, and
then click Delete.
– Printing user group members: on the right list box, select Print. In the Print dialog box,
set print parameters, and then click Print.
– Saving user group members: on the right list box, select Save As. In the Save As dialog
box, specify File name, and then click OK.
l Click the Managed Domain tab. Click Modify. In the Modify User Group Managed
Domain dialog box, modify the status of the managed domain in the submap navigation tree,
and then click OK.
l Click the Operation Rights tab to modify the operation rights of the user group.
– Adding a right: At the bottom of the list box, click Add. In the Add Right dialog box,
select the right you want to add, and then click OK.
– Deleting a right: on the right list box, select the operation right you want to delete, and
then click Delete.
----End
3.8.7 Deleting a User Group

For security purposes, you can delete a user group that is no longer used.
Prerequisite
l You must be an NMS user with the "Security Maintainer" authority or higher.
l You can delete user groups only when you have the right to manage all user groups.
l You can delete the default group only when you have the global managed domain and the
right to delete user groups.
Context
After a user group is deleted, the users in this group do not have the rights of the group and do
not belong to the group.
Procedure
Step 2 In the Security Object navigation tree, double-click the User Groups node. The table on the
right displays all the user groups.
Step 3 Select the user group you want to delete, and then click Delete.
Step 4 In the confirm dialog box, click OK.
----End

3.9 Managing NM Users

You can create NM users and assign and change their authorities. The NM user authorities are
role-based and domain-based. An equipment set equals a management domain and an operation
set equals an authority group.
Context
3.9.1 Creating T2000 Users
For network maintenance purposes, you can create T2000 users and assign different authorities
to them. Apart from user admin, all the users to operate the T2000 need to create corresponding
accounts, that is, the T2000 user accounts, on the T2000.
3.9.2 Changing the User Group That an T2000 User Belongs To
You can modify the user group of an T2000 user so that the user can have the management rights
and operation rights of the user group.
3.9.3 Assigning a Managed Domain to a T2000 User
You can assign a managed domain to a user so that the user can have a managed domain besides
the managed domains of the user group. You can perform this operation when you want to assign
a managed domain to a specific user.
3.9.4 Assigning Operation Authorities for T2000 Users
You can create a T2000 user and assign authority to the user. In addition, you can specify the
equipment that the user is able to manage.
3.9.5 Setting the Access Control List of T2000 Users
After you create a T2000 user, you can specify a client IP address range for the user to prevent
unauthorized logins. In this way, the T2000 user can log in to the T2000 server only through
those clients within the specified IP address range. If the IP address range is not specified, the
T2000 user can log in to the T2000 server by using the clients of the local server.
3.9.6 Modifying the Properties of an T2000 User
You can modify the information on an T2000 user, including the general properties, user groups,
ACL, managed domain, and operation rights.
3.9.7 Changing the NM User Password
To ensure network security, change the password periodically and keep it safe. In this way,
misoperations and damage caused by password disclosure can be avoided.
3.9.8 Deleting an NM User
NM users who do not use the T2000 must be deleted to avoid misoperations or damage caused
by user account thefts. The T2000 automatically deletes NM users who are not logged in during
the recent six months.
3.9.9 Example: Creating a T2000 User
This section describes how to create a T2000 user and assign an authority to that user by means
of an example.
3.9.1 Creating T2000 Users

For network maintenance purposes, you can create T2000 users and assign different authorities
to them. Apart from user admin, all the users to operate the T2000 need to create corresponding
accounts, that is, the T2000 user accounts, on the T2000.

Prerequisite
Procedure
Step 2 In the Security Object area, double-click Users, right-click and choose New User from the
shortcut menu.
Step 3 Complete the information in the New User dialog box.
NOTE
If Must modify password is set to Yes, when a new user logs in for the first time, a prompt is displayed to ask
the user to change the initial password before the user logs in.
Step 4 Click OK.
----End
Postrequisite
After a user is created, you need to set the following:

l Joining a user group. For details, see 3.9.2 Changing the User Group That an T2000
User Belongs To.
l Setting the management domain. For details, see 3.9.3 Assigning a Managed Domain to
a T2000 User.
l Setting the operation authority. For details, see 3.9.4 Assigning Operation Authorities
for T2000 Users.
l Setting the address access control list. For details, see 3.9.5 Setting the Access Control
List of T2000 Users.
3.9.2 Changing the User Group That an T2000 User Belongs To

You can modify the user group of an T2000 user so that the user can have the management rights
and operation rights of the user group.
Prerequisite
Context
You cannot set the user group that the admin user belongs to.
Procedure
Step 2 In the Security Object navigation tree, expand the User node, and then select a user.
Step 3 Click the Groups tab.
Step 4 Change the user group to which the NMS user belongs.
l Add the user group to which the NMS user belongs.
Click Add. Choose the user group to be added from the list, and then click OK.
l Delete the user group to which the NMS user belongs.
Choose the user group to be deleted, click Delete, and then click OK in the Confirm dialog
box.
----End
3.9.3 Assigning a Managed Domain to a T2000 User

You can assign a managed domain to a user so that the user can have a managed domain besides
the managed domains of the user group. You can perform this operation when you want to assign
a managed domain to a specific user.
Prerequisite

Context
l If a user has the right to set the management domain, then the user can assign all
management domains to managed users, including management domains that the user does
not belong to.
l When the operation that a T2000 user performs involves the equipment that is beyond the
managed domain of the T2000 user, the operation fails. Therefore, when you assign a
managed domain to a T2000 user, you need to cover all the NEs involved in the operations
that the T2000 user needs to perform.
Procedure
Step 2 In the Security Object navigation tree, expand the Users node. Select a user.
Step 3 Click the Managed Domain tab to view the managed domain of the user.
Step 4 Click Modify, and then modify the state of the managed domain in the submap navigation tree.
Step 5 Click OK.

----End

3.9.4 Assigning Operation Authorities for T2000 Users

You can create a T2000 user and assign authority to the user. In addition, you can specify the
equipment that the user is able to manage.
Prerequisite
Context
The principle of assigning user authorities is as follows:
1. After you create a T2000 user, you assign the user with certain user authorities by adding
the user to a user group rather than assigning specific authorities for the user.
2. If the user authorities are limited, and the user cannot perform certain operations after the
user is added to a default user group, you can 3.8.1 Creating User Groups. After you add
authorities for this user group, assign the user to this new user group.
3. In practice, you may need to add or delete specific authorities for a user without creating
new user groups. In this case, follow the rules below.
l To modify specific authorities for a number of NEs, do not directly select these NEs.
3.11.1 Creating an Equipment Set for the NEs that require more authorities, and assign
authorities for the equipment set.
l To assign a number of operation authorities to a user, do not directly select all these
operation authorities. 3.10.2 Creating an Operation Set for these operations and assign
the operation set to the user.
l If you want to assign an authority or a few authority to a user, you can select the user
that you want to set the authority directly. In the right portion of the window, click the
Operation Level tab, and add the corresponding operation authority to the user.
Procedure
Step 2 In the Security Object area, double-click Users and select a desired user.
Step 3 In the right-hand pane, click the Groups tab.
Step 4 Optional: Select a desired user group and click Delete.
Step 5 Click Add and the Add User Groups dialog box is displayed.

Step 6 Select a user group that you want to add, and click OK.
Step 7 In the right-hand pane, click the Operation Rights tab.
Step 8 Optional: Select a desired user operation rights and click Delete.
Step 9 Click Add and the Add Rights dialog box is displayed.

Step 10 Select a user group that you want to add, and click OK.
----End
3.9.5 Setting the Access Control List of T2000 Users

After you create a T2000 user, you can specify a client IP address range for the user to prevent
unauthorized logins. In this way, the T2000 user can log in to the T2000 server only through
those clients within the specified IP address range. If the IP address range is not specified, the
T2000 user can log in to the T2000 server by using the clients of the local server.
Prerequisite
Only the admin user can set the user access control.
Context
l If you select Use System ACL, the T2000 user can log in to the clients corresponding to
all IP addresses or network segments in the list by default.
l If you select Use User ACL, you need to select an IP address or network segment of the
client that the T2000 user can log in to.
Procedure
Step 2 In the Security Object area, double-click Users and select a desired user.

Step 3 In the right-hand pane, click the ACL Setting tab.

Step 4 Select Use System ACL or Use User ACL according to requirements.
Step 5 Click Set ACL and the Set ACL dialog box is displayed.
Step 6 Click Add and the Add dialog box is displayed.
Step 7 Set parameters of the IP address or network segment, and click OK.
Step 8 Click Close to close the Set ACL dialog box.
Step 9 Optional: If Use User ACL is selected, you need to check the Access Allowed check box
corresponding to the IP address or network segment. Click Apply.
----End
3.9.6 Modifying the Properties of an T2000 User

You can modify the information on an T2000 user, including the general properties, user groups,
ACL, managed domain, and operation rights.
Prerequisite
Procedure
Step 2 In the Security Object navigation tree, expand the Users node, and then select a user.

Step 3 Click the General tab. In the right list, modify the general properties of the user, and then click
Apply.
Step 4 Click the Groups tab. At the bottom of the list box, click Add. In the Add User Group dialog
box, select a user group, and then click OK.
Step 5 Click the ACL Setting tab, choose Use User ACL. Choose the ACL, and then click Apply.
Step 6 Click the Managed Domain tab. Click Modify. In the Modify User Managed Domain dialog
box, modify the managed domain of the user. Click OK.
Step 7 Click the Operation Rights tab, and then modify the operation rights of the user.
l Add an operation right.
At the bottom of the list box, click Add. In the Add Rights dialog box, select a right you
want to add, and click OK.
l Delete an operation right.
In the right list box, select an operation right you want to delete, and then click Delete.
----End
3.9.7 Changing the NM User Password

To ensure network security, change the password periodically and keep it safe. In this way,
misoperations and damage caused by password disclosure can be avoided.
Prerequisite

Context
CAUTION
Periodically change the password to avoid misoperations or intended damage caused by
password disclosure.
Procedure
Step 1 Choose File > Change Password from the Main Menu. The Change Password dialog box is
displayed.
Step 2 Enter the old password in the Old PasswordCurrent Password field. Enter the new password
in the New Password field and then enter the new password again in the Confirm Password
field.
Step 3 Click Confirm.
----End
3.9.8 Deleting an NM User

NM users who do not use the T2000 must be deleted to avoid misoperations or damage caused
by user account thefts. The T2000 automatically deletes NM users who are not logged in during
the recent six months.
Prerequisite
The NM user must be created.
Procedure
Step 1 Choose System > NM User Management from the Main Menu.
Step 2 Expand the tree.
Step 3 Right-click an NM user and choose Delete from the shortcut menu.
Step 4 Click OK.
----End
3.9.9 Example: Creating a T2000 User

This section describes how to create a T2000 user and assign an authority to that user by means
of an example.
Prerequisite
l You must be an NM user with the "Security Maintainer" authority or higher.

l You must be the admin user to set user access control. You can only query the user access
control with NM administrator authority.
l The ES_NM_user1 equipment set must be created.
l The OS_NM_user1 operation set must be created.
l The SS subnet must be created.
Context
The T2000 administrator A is responsible for T2000 security management. After the T2000
installation and commissioning, a T2000 user NM_user1 needs to be created for the T2000
maintainer B. The specific requirement is as follows.
l T2000 user name: NM_user1
l T2000 user password: User1368
l The T2000 user NM_user1 belongs to the maintainer group.
l The T2000 user NM_user1 can manage all the equipment in only the SS subnet.
l Apart from the maintainer group authority, the T2000 user must also be assigned with the
OS_NM_user1 operation set authority, and allowed to operate on the ES_NM_user1
equipment set.
l NM_user1 is allowed to log in by using the clients within a specified IP address range,
which is given below.
– Start IP address: 192.168.0.1
– End IP address: 192.168.0.168
Procedure
Step 2 Create the T2000 user NM_user1.
1. In the Security Object area, double-click Users, right-click and choose New User from
the shortcut menu.
2. In the New User dialog box, complete the following information:
Name: NM_user1
Password: User1368
Confirm Password: User1368

3. Click OK.
In the right-hand user list, the newly created NM_user1 is displayed.
Step 3 Add the NM_user1 user to the maintainer group.
1. In the Security Object area, double-click Users and select the T2000 user NM_user1.
2. In the right-hand pane, click the Groups tab.
3. Click Add and the Add User Groups dialog box is displayed.
4. Select Maintainer Group and click OK. The newly added user group is displayed in the
user group list of the Groups tab.
Step 4 Set the managed domain of the T2000 user NM_user1.

1. Click the Managed Domain tab and click Modify. The Modify User Managed
Domain dialog box is displayed.

2. Cancel the selection of Manage the entire network, and select the SS subnet of the root
Object Tree.
3. Click OK.
Step 5 Adjust authority for NM_user1 so that the user has OS_NM_user1 operation set authority on
the ES_NM_user1 equipment set.
1. Click the Operation Rights tab and click Add.
2. In the Add Rights dialog box, complete the following information:
Authority Type: Transmission Network NE Management
Operation Object: ES_NM_user1
Operation Set: OS_NM_user1
3. Click OK.
The added authorities are displayed in the authority list.
Step 6 Set the IP address range of clients from which NM_user1 is allowed to log in.
1. Click the ACL Setting tab.
2. Click Use User ACL.
3. Click Set ACL and the Set ACL dialog box is displayed.
4. Click Add and the Add dialog box is displayed..
5. Click Start IP address to end IP address and set the following parameters:
Start IP Address: 192.168.0.1
End IP Address: 192.168.0.168

6. Click OK to close the Add dialog box.

7. Click Close to close the Set ACL dialog box.
8. For the specified IP address range, check the Access Allowed check box and click
Apply.
----End
3.10 Managing T2000 Operation Sets

The T2000 default operation sets do not meet all user requirements. Hence, the NM administrator
can define an operation set to assign authorities conveniently.
3.10.1 Operation Set Types

Operation set type specifies the application scope of every operation set. Currently there are
three types: Transport network NM management, Transport network network management and
Transport network NE management.
3.10.2 Creating an Operation Set
Usually, the default operation sets on the T2000 cannot well meet requirements of users.
Therefore, the T2000 administrator can define some operation sets to allocate authorities to the
T2000 users in a better way.
3.10.3 Modifying the Service Objects of an Operation Set
You can modify the service objects of an operation set by setting the operation rights of a user
or a user group so that the user or the user group can perform relevant operations.
3.10.4 Deleting an Operation Set
When an operation set is no longer used, you need to delete it in time.
3.10.1 Operation Set Types

Operation set type specifies the application scope of every operation set. Currently there are
three types: Transport network NM management, Transport network network management and
Transport network NE management.
Operation sets can be classified according to these three types. When specifying user and user
group authorities, you can assign authorities according to the three types. Table 3-2 lists their
comparison.

Table 3-2 Operation Set Type

Operation Set Type Default Operation Set Application
Transport network NM l NM Maintainer Operation Applies to operations

management Set performed on the T2000.
l NM Operator Operation
Set
l NM Monitor Operation
Set
l Security Maintainer
Operation Set
l Security Operator
Operation Set
l Security Watcher
Operation Set
Transport network network l SDH Network Maintainer Applies to operations on the

management Operation Set transport network managed
l SDH Network Operator by the T2000.
Operation Set
l SDH Network Monitor
Operation Set
l WDM Network
Maintainer Operation Set
l WDM Network Operator
Operation Set
l WDM Network Monitor
Operation Set
l Ethernet Network
Maintainer Operation Set
l Ethernet Network
Operator Operation Set
l Ethernet Network Monitor
Operation Set
Transport network NE l NE Administrator Applies to operations on the

management Operation Set transport network NE
l NE Maintainer Operation managed by the T2000.
Set
l NE Operator Operation
Set
l NE Monitor Operation Set

NOTE
l In the Transport network NM management, the NM maintainer operation set has the highest authority
and the NM monitor operation set has the lowest authority.
l In the Transport network network management, the network maintainer operation set has the highest
authority and the network monitor operation set has the lowest authority.
l In the Transport network NE management, the NE administrator operation set has the highest authority
and the NE monitor operation set has the lowest authority.
l Be default, an operation set of a higher authority contains all authority of an operation set of a lower authority.
For the default authority of each operation set, refer to "Default Operation Set List" in "Appendix" of the
T2000 help.
3.10.2 Creating an Operation Set

Usually, the default operation sets on the T2000 cannot well meet requirements of users.
Therefore, the T2000 administrator can define some operation sets to allocate authorities to the
T2000 users in a better way.
Prerequisite
Procedure
Step 2 In the Security Object area, right-click Operation Sets and choose New Operation Set from
the shortcut menu.
Step 3 In the New Operation Set dialog box displayed, enter the information of a new operation set.
Click Apply.

Step 4 Click the Members tab. Check the Add operations or Copy operation sets option button to
add members to the operation set.

Step 5 Click OK.
----End
3.10.3 Modifying the Service Objects of an Operation Set

You can modify the service objects of an operation set by setting the operation rights of a user
or a user group so that the user or the user group can perform relevant operations.
Prerequisite
l Only the admin user can assign the security operation rights.
l Only the global group administrator can set user groups.
Procedure
Step 2 In the Security Object navigation tree, expand the Users or User Groups node, and then select
a user or a user group.
Step 3 Click the Operation Rights tab, and then click Add.
Step 4 In the Add Rights dialog box, set All Operation Sets. In Subtype, select the operation set you
want to add, and then click OK.
NOTE
In the Security Object navigation tree, expand the Operation Sets node, and then select the added operation
set. Click the Applicable for tab. The service objects of the current operation set are displayed on the Applicable
for tab.
----End
3.10.4 Deleting an Operation Set

When an operation set is no longer used, you need to delete it in time.
Prerequisite
You must be an NMS user with the "Security Maintainer" authority or higher.
Context
If you delete a operation set, the operation set of a user or user group is also deleted.
Procedure
Step 2 In the Security Object navigation tree, click the Operation Sets node. The table on the right
displays all the operation sets.

Step 3 Select the operation set that you want to delete, and then click Delete.
Step 4 In the Confirm dialog box, click OK.
----End
3.11 Managing T2000 Equipment Sets

After the planning and creation of equipment sets, you can assign an equipment set to a specified
user group. In this way, all users in this user group are authorized to operate the equipment in
the equipment set. This management mode helps you uniformly allocate and manage authorities
of the T2000 users.
3.11.1 Creating an Equipment Set

Usually, the default equipment set of networkwide objects on the T2000 cannot meet
requirements of users well. Therefore, the T2000 administrator can define some equipment sets
to allocate authorities to the T2000 users in a better way.
3.11.2 Modifying a Device Set
You can modify the properties of an T2000 device set.
3.11.3 Modifying the Service Objects of a Device Set
You can modify the service objects of a device set by setting the managed domain of a user or
a user group so that the user or the user group can manage a specified device set.
3.11.4 Deleting a Device Set
When a device set is no longer used, you need to delete it in time.

3.11.1 Creating an Equipment Set

Usually, the default equipment set of networkwide objects on the T2000 cannot meet
requirements of users well. Therefore, the T2000 administrator can define some equipment sets
to allocate authorities to the T2000 users in a better way.
Prerequisite
Procedure
Step 2 In the Security Object area, click Device Sets, right-click and choose New Device Set from the
shortcut menu.
Step 3 In the New Device Set dialog box that is displayed, enter the information of a new equipment
set.
Step 4 Click the Members tab and add members for the equipment set.
Step 5 Click OK.
----End
3.11.2 Modifying a Device Set

You can modify the properties of an T2000 device set.
Prerequisite
Procedure

Step 2 In the Security Object navigation tree, expand the Device Sets node, and then select a device
set.
Step 3 In the panel on the right, do as follows:

l Click the General tab, modify the general properties of the device set, and then click
Apply.
l Click the Members tab. At the bottom of the list box, click Modify. In the Change Members
of a Device Set dialog box, modify the members of the device set. Click OK.
l Click the Applicable for tab to view the users or user groups using the device set. Do as
follows:
1. In the Security Object navigation tree, expand the Users or User Groups node, and
then select a user or user group.
2. Click the Managed Domain tab, and then click Modify.
3. In the Modify User Managed Domain or Modify User Group Managed Domain
dialog box, select the required device set, and then click OK.
----End
3.11.3 Modifying the Service Objects of a Device Set

You can modify the service objects of a device set by setting the managed domain of a user or
a user group so that the user or the user group can manage a specified device set.
Prerequisite
Procedure
Step 2 In the Security Object navigation tree, expand the Users or User Groups node, and then select
a user or user group.
Step 3 Click the Managed Domain tab, and then click Modify.
Step 4 In the Modify User Managed Domain or Modify User Group Managed Domain dialog box,
select the required device set, and then click OK.
NOTE
In the Security Object navigation tree, expand the Device Sets node, and then select the added device set. Click
the Applicable for tab.The service objects of the device set are displayed on the Applicable for tab.
----End
3.11.4 Deleting a Device Set

When a device set is no longer used, you need to delete it in time.
Prerequisite
You must be an NMS user with the "Security Maintainer" authority or higher.

Context
If you delete a device set, the device set of a user or user group is also deleted.
Procedure
Step 2 In the Security Object navigation tree, expand the Device Sets node. The table on the right
displays all the device sets.
Step 3 Select the device set that you want to delete, and click Delete.
----End
3.12 Managing T2000 Login

To ensure network data security, you can manage the users who are logged in to the T2000.
Context
By using the T2000 you can perform the following T2000 login management tasks:
3.12.1 Locking the T2000 Client Screen
If you do not use the T2000 for a time period, you can lock out the client to ensure network
security. This function only locks out the client screen and does not affect the network.
3.12.2 Switching a Logged-In NM User
Different NM users have different authorities. You can log in as another user to perform
operations of different levels.
3.12.3 Forcing an NM User to Log Out of the T2000
For network security management, you can force a specified NM user to log out of the T2000
as required. In the single user mode, this function also forces all other users to log out of the
T2000. In addition, an NM user will be forced to log out by the T2000 after a long period of
time without any activities.
3.12.4 Switching to the Single User Mode
To avoid being affected by other NM users during a network expansion, you can switch to the
single user mode so that all other users are forced to log out.
3.12.5 Setting Automatical Log-In for T2000 Users
After setting the automatic login function, a NM user can log in to the T2000 next time by using
the specified user name and password. You can also set the display mode after you log in to the
T2000.
3.12.1 Locking the T2000 Client Screen

If you do not use the T2000 for a time period, you can lock out the client to ensure network
security. This function only locks out the client screen and does not affect the network.

Procedure
Step 1 Choose File > Lock Terminal from the Main Menu.
The T2000 client is locked.
Step 2 If you want to unlock the client, press CTRL+ALT+U at the same time. Enter the password of
the current user or the password of user admin and click OK.
----End
3.12.2 Switching a Logged-In NM User

Different NM users have different authorities. You can log in as another user to perform
operations of different levels.
Prerequisite
You have already logged in to the T2000.
Procedure
Step 1 Choose File > Logout from the Main Menu. The Confirm dialog box is displayed. Click OK.
Step 2 The Save coordinates dialog box is displayed. Click OK.
NOTE
This step is to executed when the view deploy is changed.
Step 3 Enter the user name and password in the Login dialog box.
Step 4 Click Login.
----End
3.12.3 Forcing an NM User to Log Out of the T2000

For network security management, you can force a specified NM user to log out of the T2000
as required. In the single user mode, this function also forces all other users to log out of the
T2000. In addition, an NM user will be forced to log out by the T2000 after a long period of
time without any activities.

Prerequisite
You must be the admin user.
Procedure
Step 1 Choose System > NM User Management from the Main Menu.
Step 2 Choose Security Object > Users and click the Login User tab.
Step 3 Right-click an NM user and choose Force to Exit from the shortcut menu.
Step 4 Confirm dialog box is displayed. Click OK.
----End
3.12.4 Switching to the Single User Mode

To avoid being affected by other NM users during a network expansion, you can switch to the
single user mode so that all other users are forced to log out.
Prerequisite
Only the admin user can enable single-user or multiple-user mode.
Context
In the single user mode, only user with "NM maintainer" authority or higher can log in to the
T2000.
Procedure
Step 1 In the multiple user mode, choose System > NMS Security Settings > Single User Mode from
the Main Menu.
Step 2 Click OK when the Confirm dialog box is displayed.
NOTE
To switch from the single user mode to the multiple user mode, set System > NMS Security Settings >
Single User Mode as unchecked.
----End
3.12.5 Setting Automatical Log-In for T2000 Users

After setting the automatic login function, a NM user can log in to the T2000 next time by using
the specified user name and password. You can also set the display mode after you log in to the
T2000.
Procedure
Step 1 On the Main Menu, choose File > Preferences. In the Preferences dialog box, click the
Automatic Login tab.
Step 2 Select Log in automatically, and then enter the required user name and password.

NOTE
If Full Screen mode after login is selected, the Physical Diagram is fully displayed next time after you
log in to the T2000.
Step 3 Click OK or Apply.
----End
3.13 Managing the Remote Maintenance User

The T2000 remote maintenance function allows login to the T2000 server from a remote
maintenance terminal. Strict management for the remote maintenance user not only ensures
T2000 system security, but also makes maintenance operations easier.
3.13.1 Enabling a Remote Maintenance User
To facilitate easy maintenance, the T2000 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.
3.13.2 Setting the Remote Maintenance User Authority
Operation authority must be assigned to the remote maintenance user reasonably to guarantee
the T2000 security. Currently there are two types of operation authority: query and configuration.
3.13.3 Setting the Remote Maintenance User Validity
For security purposes, it is recommended to set a valid period for the remote maintenance user.
In the T2000, the remote maintenance is permanently valid by default. While in practical
application, the user can set the valid period as needed.

conditions.
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
Procedure
Step 1 Choose System > Remote Maintenance User Management from the Main Menu. The Remote
Maintenance User Management dialog box is displayed. Enable the remote maintenance user
and set its other parameters.

Step 2 Click OK.
----End
3.13.2 Setting the Remote Maintenance User Authority

Operation authority must be assigned to the remote maintenance user reasonably to guarantee
the T2000 security. Currently there are two types of operation authority: query and configuration.
Prerequisite
l You must be an NM user with "NM maintainer" authority or higher.
l The remote maintenance user must be enabled.
Procedure
Maintenance User Management dialog box is displayed.
Step 2 Set the Operation Authority. You can select Query or Configuration as needed.

Step 3 Click OK.
----End
3.13.3 Setting the Remote Maintenance User Validity

For security purposes, it is recommended to set a valid period for the remote maintenance user.
In the T2000, the remote maintenance is permanently valid by default. While in practical
application, the user can set the valid period as needed.
Prerequisite
Procedure
Maintenance User Management dialog box is displayed.
Step 2 Set Valid Forever or Not to No.
Step 3 Set Validity Period.

Step 4 Click OK.
----End
3.14 Setting the Security Access of an NE

To ensure the NE security, you need to disable the unused interfaces on the NE.
3.14.1 Controlling Communication Between NE and T2000 Through Ethernet Port
An NE can be connected to the T2000 through an Ethernet port. By default, an NE allows access
from the T2000 through an Ethernet port. This operation enables you to query and set the Ethernet
access function for an NE.
3.14.2 Controlling Communication Between NE and T2000 Through a Serial Port
NEs can be accessed to the T2000 through a serial port or the command line tool. This operation
views and sets the serial port access function of NEs.
3.14.3 Setting the NE OAM Access
The T2000 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.14.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.14.5 Controlling Communication Between NE and LCT
For NE operation security, NEs are managed by the T2000 under normal circumstances. But
under special circumstances, you need to use the T2000 LCT or Web LCT to commission an
NE. You can turn on LCT access for the NE on the T2000.

3.14.1 Controlling Communication Between NE and T2000 Through

Ethernet Port
An NE can be connected to the T2000 through an Ethernet port. By default, an NE allows access
from the T2000 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 T2000 and NEs.
l It is recommended to use Ethernet access for the LCT (T2000 LCT or Web LCT) in most
cases.
l If you use the LCT (T2000 LCT or Web LCT) to initialize NEs or perform download, use
Ethernet access.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Access Control from the
Function Tree.
Step 2 In the Ethernet Access Control area, click Refresh to query the Ethernet access enable status.
Step 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.
----End
3.14.2 Controlling Communication Between NE and T2000 Through

a Serial Port
NEs can be accessed to the T2000 through a serial port or the command line tool. This operation
views and sets the serial port access function of NEs.
Prerequisite

Context
CAUTION
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Access Control from the
Function Tree.
Step 2 Check the Enable Serial Port Access check box. Click Refresh to query whether the current
NE allows serial port access.
Step 3 Check the Access NM check box. Click Apply to enable the serial access function of the NE.
NOTE
l If you want to disable this function, uncheck the Access NM check box. Click Apply.
l If you want to connect the serial port to command line, check the Access Command Line check box.
Step 4 Set the Baud Rate. Click Apply.
----End
3.14.3 Setting the NE OAM Access

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

Context
CAUTION
Procedure
Step 1 In the NE Explorer, click an NE and choose Communication > Access Control from the
Function Tree.
Step 2 Select Enable OAM Access and click Apply. The OAM access of the NE is now enabled.
----End
3.14.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
Context
CAUTION
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 (T2000 LCT or Web LCT) in most cases.
l Use COM port access only when the Ethernet access fails, or the NE already connects to
the T2000, 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 T2000 to temporarily enable COM access.

Procedure
Step 1 In the NE explorer, click an NE and choose Communication > Access Control from the
Function Tree.
Step 2 Select Enable COM Access and click Apply. The COM access of the NE is now enabled.
----End
3.14.5 Controlling Communication Between NE and LCT

For NE operation security, NEs are managed by the T2000 under normal circumstances. But
under special circumstances, you need to use the T2000 LCT or Web LCT to commission an
NE. You can turn on LCT access for the NE on the T2000.
Prerequisite
l You must log in to the T2000 as user admin
l Applies to the SDH and WDM equipment.
Context
CAUTION
l When no T2000 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 T2000 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 T2000 user requests to log in to the
NE, the login of the LCT user does not affect the login of the T2000 user, and the successful
login of the T2000 user does not affect the logged-in LCT user.
l When the LCT user and the T2000 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.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > LCT Access Control from the Function
Tree.

Step 2 Click Query to query whether the current NE allows LCT access.
Step 3 Click Access Allowed to enable LCT access.

NOTE
If you want to disable this function, click Disable Access.
----End
3.15 Setting the NE ACL

You can ensure the security of NEs by setting the NE ACL.
3.15.1 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.15.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.15.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.15.1 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.15.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 SDH and WDM equipment.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > ACL from the Function Tree.
Step 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.
Step 3 Click Query to load the basic ACL rules from the NE.
Step 4 Click New.

An undefined basic ACL rule is added to the basic ACL rules list.
Step 5 Set the proper values for all the parameters according to the network requirements.
Step 6 Click Apply to apply the new configuration data to the NE.
A prompt appears indicating the operation was successful.
Step 7 Click Close to complete the operation.
Step 8 Optional: Repeat Step 4 through Step 7 to set more basic ACL rules to this NE.
Step 9 Optional: Repeat Step 1 through Step 7 to set the basic ACL rules to other NEs.
----End
3.15.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
You must be an NM user with "NE operator" authority or higher.
It is applicable to the SDH and WDM equipment.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > ACL from the Function Tree.

Step 2 Click the Advanced ACL tab. The advanced ACL rule list is displayed.
Step 3 Click Query to load the advanced ACL rules from the NE.
Step 4 Click New.

An undefined advanced ACL rule is added to the list.
Step 5 Set proper values for all the parameters according to the network requirements.
Step 6 Click Apply to apply the new configuration data to the NE.
A prompt appears indicating the operation was successful.
Step 7 Click Close to complete the operation.
Step 8 Optional: Repeat Step 4 through Step 7 to set more advanced ACL rules to this NE.
Step 9 Optional: Repeat Step 1 through Step 7 to set the advanced ACL rules to other NEs.
----End
3.16 Managing NE Users

To ensure NE data security, you can manage the authorities and passwords for NE users.
By using the T2000 you can perform the following NE user management tasks:
3.16.1 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 T2000
administrator is advised to create NE users before configuring services.
3.16.2 Changing the NE User Password
To ensure network security, you are recommended to change the NE user password periodically.
3.16.3 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.16.4 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 T2000 administrator needs to
know the NE security settings and modify the NE user password before it becomes invalid.
3.16.5 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.16.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.16.1 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 T2000
administrator is advised to create NE users before configuring services.

Prerequisite
You must be an NM user with "NE administrator" authority or higher.
You must create an NE user after logging in to the NE.
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
Step 1 Choose System > NE Security Management > NE User Management from the Main Menu.
Step 2 In the NE list on the left, select one or more NEs and click .
Step 3 Click Add and the Add NE User dialog box is displayed.
Step 4 Enter the NE user name in the NE User field.

NOTE
The NE user name must contain letters, or it can be a combination of letters, symbols and numerals. For
release 4.0 NEs, the NE user name contains at least 2, but not more than 8 characters. For release 5.0 NEs,
the NE user name contains at least 4, but not more than 16 characters.
Step 5 Select the User Level as needed.
Step 6 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.
Step 7 Enter the password in the New Password field and enter it again in the Confirm Password
field.
NOTE
For release 5.0 NEs, you also need to set the Whether the password is allowed to be modified
immediately parameter.
For release 5.0 NEs, you also need to set the For the OptiX Metro 500 equipment, you also need to set the
Login Allowed, Permanently Valid or not, Valid From and Valid Till.
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.
Step 8 In the NE Name field, select the NEs that this NE user is allowed to manage.
Step 9 Click OK.
----End
3.16.2 Changing the NE User Password

To ensure network security, you are recommended to change the NE user password periodically.
Prerequisite
l You must be an NM user with "NE administrator" authority or higher.
l The NE user must be created.
Context
CAUTION
Change the password periodically for security purposes.
Procedure
Step 2 In the Object Tree, select an NE that you want to query and click .
Step 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.

Step 4 Click OK.
----End
3.16.3 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
Procedure
Step 2 In the left-hand NE list, click .

Step 3 In the NE User Management Table pane, select a desired NE user.
Step 4 Click User Additional Information to query the basic information of this NE user.
----End
3.16.4 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 T2000 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.

Context
The NE security parameters contain: Warning Screen Switching, Warning Screen
Information, Allowable Used Times for Outdated Password, Password Max. Valid Period
(day), Password Min. Valid Period (day), Password Uniqueness (Entries), Lock Testing
Time (minute) and Allowable Illegal Access Times.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Security Parameters from the
Function Tree.
Step 2 Click Query to query the settings of NE security parameters.
----End
3.16.5 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
Procedure
Step 2 In the left-hand NE list, select an NE and click .

Step 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.
Step 4 Click OK.
----End
3.16.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
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE User Group Management from
the Function Tree.
Step 2 Click Query to query NE users included by various NE user groups of the NE.
----End

3.17 Managing NE Login

To ensure NE data security, you can manage the users who are logged in to NEs.
By using the T2000 you can perform the following NE login management tasks:
3.17.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.17.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.17.3 Switching a Logged-In NE User
During a new deployment, after the root NE user creates an NE, this user can create another NE
user. You can log in to the NE with the new NE user name.
3.17.4 Switching a DC User
By querying and switching a DC user on the T2000, you can log in to and manages an NE as a
new DC user.
3.17.5 Forcing an NE User to Log Out of the NE
When you want to log in to an NE as a user who has a higher level of authority, you can force
a lower-level NE user to log out of the NE. In this way, you can avoid an NE being configured
by multiple NE users at the same time, or prevent unauthorized logins by other NE users.
3.17.6 Setting NE Login Prompt Message
You can turn on the warning screen, and set the information displayed in the warning screen. If
you turn on the warning screen, after the T2000 logs in to an NE, the queried warning screen
information is displayed.
3.17.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 equipment.
Procedure
Step 1 Choose System > NE Security Management > NE Login Lock from the Main Menu.

Step 2 In the Object Tree, select an NE and click the double-right-arrow button (red).
Step 3 Click Query to query the Login Lock Status.
Step 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.17.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 NEs.
Procedure
Step 1 Choose System > NE Security Management > NE Setting Lock from the Main Menu.
Step 2 In the left pane, select an NE and click the double-right-arrow button (red).
Step 3 Click Query to query the Set Lock Status.
Step 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.
Step 5 Check the Lock Permanently or Not check box to permanently lock the current NE settings or
enter the value of Lock Remaining Time(s) to temporarily lock the settings. Click OK.
----End
3.17.3 Switching a Logged-In NE User

During a new deployment, after the root NE user creates an NE, this user can create another NE
user. You can log in to the NE with the new NE user name.
Prerequisite
Background Information
An NE user cannot log in to 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 T2000 server, if you use the same NE user to log in to
the same NE through another T2000 server, the NE user is forced to log out from the first
T2000 server.

Procedure
Step 1 Choose System > NE Security Management > NE Login Management from the Main Menu,
click the NE Login Management tab.
Step 2 Select the required NE from the NE list, and click .

NOTE
When this button is used for the first time, or the configuration data is changed, or the selected object on the
Object Tree on the left is changed, this button becomes red.
Step 3 Click Query to query the current NE user.

Step 4 In the NE Login Management Table, select the NE and click Switch NE User. In the Switch
Current NE User dialog box, enter User and Password, and set Offline Switching.
Step 5 Click OK.
----End
3.17.4 Switching a DC User

By querying and switching a DC user on the T2000, you can log in to and manages an NE as a
new DC user.
Prerequisite
l The DC user must be created.
Context
l A user cannot log in to the DC and the T2000 at the same time. As a result, if you switch
to a DC user that log in to the T2000 currently, an error occurs.
l One NE user cannot log in or manage an NE at multiple clients at the same time. If a user
already logs in to an NE and the same user tries to log in at another client, the client that
the user logged in earlier automatically exits.
Procedure
Step 1 Choose System > NE Security Management > NE Login Management from the Main Menu,
click the DC Login User Management tab.
Step 2 Select an NE from the NE list to switch its user. Click .

NOTE
When this button is used for the first time, or the configuration data is changed, or the selected object on the
Object Tree on the left is changed, this button becomes red.
Step 3 Click Query to query the current NE user.

Step 4 In the NE Login Management Table, select the NE and click Switch NE User. In the Switch
DC Login User, enter the User and Password.
Step 5 Click OK.
----End

3.17.5 Forcing an NE User to Log Out of the NE

When you want to log in to an NE as a user who has a higher level of authority, you can force
a lower-level NE user to log out of the NE. In this way, you can avoid an NE being configured
by multiple NE users at the same time, or prevent unauthorized logins by other NE users.
Prerequisite
l The NE user must be logged in to the NE.
Procedure
Step 1 Choose System > NE Security Management > NE Login Management from the Main Menu.
Step 3 Select the NE entry. Click Logout or right-click it and choose Logout. A prompt is displayed
indicating that the operation is successful.
Step 4 Click Close.
----End
3.17.6 Setting NE Login Prompt Message

You can turn on the warning screen, and set the information displayed in the warning screen. If
you turn on the warning screen, after the T2000 logs in to an NE, the queried warning screen
information is displayed.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Security Parameters from the
Function Tree.
Step 2 Optional: Click Query to query the settings of NE security parameters.
Step 3 Select an NE, double-click Warning Screen Switching and choose whether to enable the
warning screen.
Step 4 Double-click Warning Screen Information and enter the information.

NOTE
l You can enter information in the Warning Screen Information field only when you set Warning
Screen Switching to Enabled.
l In the Warning Screen Information field, enter the information that contains a maximum of 1500
characters.
Step 5 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.
----End

Operation Guide for Common Features 4 Log Management
4 Log Management
About This Chapter
Log management includes the T2000 log management and NE log management. Querying and
saving the log information periodically helps network managers to detect illegal logins and
operations in time, and analyze faults.
4.1 Log Types

The logs include the T2000 security log, the T2000 operation log, and the NE security log. The
logs record operations performed by operators to the T2000 or an NE.
4.2 Managing T2000 Security Log
Save and check the T2000 log on a regular basis, because the log helps you to detect unauthorized
logins and operations, and also troubleshoot problems.
4.3 Managing Operation Logs
The T2000 provides the function of managing operation logs. This function enables you to query
and dump unsecure operation logs.
4.4 Forwarding the T2000 Logs to the Syslog Server
The T2000 can upload operation logs to a Syslog server. An operation log keeps a record of all
types of operations on the T2000. It provides the reference information for the analysis of the
T2000 running status and the follow-up maintenance.
4.5 Browse NE Security Logs
The NE security log records the operations performed by all NE users and the results of those
operations. You can view the NE security log and filter the records by NE user, event name and
occurring time..
4.6 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. Applies to the SDH and WDM equipment.

4 Log Management Operation Guide for Common Features
4.1 Log Types

The logs include the T2000 security log, the T2000 operation log, and the NE security log. The
logs record operations performed by operators to the T2000 or an NE.
4.1.1 T2000 Security Log

An security log records NM users' operations relevant to the security on the T2000, such as user
login, user exit and so on. By viewing the logs, an administrator can track and check the user
operations.
4.1.2 T2000 Operation Log
An operation log records NM users' operations on the T2000. By viewing the logs, an
administrator can track and check the user operations.
4.1.3 NE Security Log
NE security log records operation events of NE users to the equipment. By viewing the NE
security log, the administrator can track and check operations of an NE user.
4.1.1 T2000 Security Log

An security log records NM users' operations relevant to the security on the T2000, such as user
login, user exit and so on. By viewing the logs, an administrator can track and check the user
operations.
You can view the T2000 security log periodically to find the insecure operations performed to
the T2000 in a timely manner. You can also check the T2000 security log to effectively ensure
the security of the T2000.
Table 4-1 provides the meaning of danger levels of security log.
Table 4-1 Security log danger level
Risk Level Meaning
Dangerous Important actions that may do harm to the

network management system.
Warning Less important actions that may cause

problems in the future.
Normal Actions that do not modify data and require

to be recorded for reference.
4.1.2 T2000 Operation Log

An operation log records NM users' operations on the T2000. By viewing the logs, an
administrator can track and check the user operations.
The T2000 operation log records user operations irrelevant to the security on the T2000. Viewing
the operation log helps you to learn the running information of the system.

According to preset filter criteria, you can learn the activity record of a user or client. For
example, you can view operations performed by a user in the system.
Table 4-2 provides the meaning of danger levels of operation log.
Table 4-2 Operation log danger level

Risk Level Meaning
Dangerous Important actions that may modify data in the

system or NE. For example, delete alarms.
Warning Less important actions that may cause

problems in the future.
Normal Actions that do not modify data and require

to be recorded for reference. For example,
create a board.
4.1.3 NE Security Log

NE security log records operation events of NE users to the equipment. By viewing the NE
security log, the administrator can track and check operations of an NE user.
The NE security log records operations performed by each NE user to an NE. The NE security
log includes the information such as the name of NE user performing the operations, the event
name, and the operation time and result. Viewing the NE security log helps you to learn the
running information of the NE.
According to preset filter criteria, you can learn the operation record of an NE user or operation
event, or learn the running record of an NE during a specific period.
4.2 Managing T2000 Security Log

Save and check the T2000 log on a regular basis, because the log helps you to detect unauthorized
logins and operations, and also troubleshoot problems.
Context
By using the T2000, you can perform the following log management tasks:
4.2.1 Browsing Security Logs
You can query security logs to know the information about the security operations of the
T2000.
4.2.2 Periodically dump security logs
After the periodical dumping task is set, the T2000 can periodically dump the security logs. As
a result, logs are not lost.
4.2.3 Setting the Overflow Dump for Security Logs
The data amount in an security log keeps increasing as the system runs day by day. If the data
amount exceeds the maximum capacity, the new data overwrites the old data and thus causes
the data loss. To avoid the problem, you need to dump the security logs in time.

4.2.4 Dumping Security Logs Manually

You can dump the security logs manually on the T2000. The dumped logs are saved as files and
deleted from the database.
4.2.1 Browsing Security Logs

You can query security logs to know the information about the security operations of the
T2000.
Prerequisite
You must be an NMS user with the "Security Watcher" authority or higher.
Procedure
Step 1 Choose System > Browse Log.
Step 2 In the Log Class navigation tree, select Security Logs. In the right pane, double-click a security
log to view its details.
Step 3 Choose to perform the following operations.

l Click Refresh to refresh the security logs.
l Click Filter. In the Filter dialog box, set the conditions to filter the security logs you
browse.
l Click Print. In the Range dialog box, set the start row and the end row. Then click OK.
l Click Save As. In the Save As dialog box, set the start row, end row, and file name. Then
click OK to save the logs to your local disk.
l Click Dump. In the Confirm dialog box, click OK. The security logs are saved to the
server.
----End
Reference Standard
The log does not record any abnormal, malicious, or illegal login.

Troubleshooting
If the log records illegal operations, you need to reset the operation authority and management
authority of the user. For details, refer to 3 Security Management
4.2.2 Periodically dump security logs

After the periodical dumping task is set, the T2000 can periodically dump the security logs. As
a result, logs are not lost.
Prerequisite
You must log in to the T2000 as user admin.
Context
The scheduled time for a task is based on the server time.
Procedure
Step 1 Choose System > Database > Dump Settings from the Main Menu.
Step 2 In the Dump Settings tree, select Security Logs.
Step 3 In the Enable Dumping Periodically area, set the Periodic dump to Yes.
Step 4 Set the Dump interval (days) and period of saving the record.
Step 5 In the Dump Settings area, set Dumping to (path).
Step 6 Click OK.
----End
Result
Navigate to the directory that is indicated in Dumping to (path) and then view the dumped
security log files.
4.2.3 Setting the Overflow Dump for Security Logs

The data amount in an security log keeps increasing as the system runs day by day. If the data
the data loss. To avoid the problem, you need to dump the security logs in time.
Prerequisite
Procedure
Step 1 Choose System > Database > Dump Settings from the Main Menu. The Dump Settings dialog
box is displayed.
Step 2 Select Security Logs in the Dump Settings tree.

Step 3 Set the Maximum capacity parameter, which is 100000 by default.

When the number of records in the operation log exceeds this number, the dump is triggered.
Step 4 Set the Dump percent of the database(%) parameter, which is 100 by default.
The system decides how many records to dump each time according to this value. For example,
when the number of the records exceeds 100000, a dump is performed for 100000 pieces of data
records.
Step 5 Set the Record threshold-crossing value(%), which is 90 by default.
When data of the security log exceeds the value of multiplying Maximum Capacity by Record
threshold-crossing value(%), a threshold-crossing alarm is reported on the T2000.
Step 6 In Dumping to (Path), specify the directory to store the dumped file.
NOTE
If you specify a period in the Automatic Deletion of Dump Files area, the dumped files beyond the period
are automatically deleted.
Step 7 Click OK.

----End
4.2.4 Dumping Security Logs Manually

You can dump the security logs manually on the T2000. The dumped logs are saved as files and
deleted from the database.

Prerequisite
Procedure
Step 1 Choose System > Database > Dump Manually from the main menu.
Step 2 In the Manual Dump navigation tree, select Security Logs.

Step 3 In the Generation Time of Security Logs group box, set the dump condition.
Step 4 In the Records That Meet The Dump Condition group box, click Query.
Step 5 Click Dump.
Step 6 Click Close.
----End
Result
Navigate to the directory that is indicated in the Dumping to (path) of the File group box, view
the dumped security log files.
4.3 Managing Operation Logs

The T2000 provides the function of managing operation logs. This function enables you to query
and dump unsecure operation logs.

4.3.1 Browsing Operation Logs

You can browse the operation logs to know the non-security operations and their results on the
T2000.
4.3.2 Periodically Dumping Operation Logs
After the periodical dumping task is set, the T2000 can periodically dump the operation logs to
avoid log loss.
4.3.3 Setting the Overflow Dump for Operation Logs
The data amount in an operation log keeps increasing as the system runs day by day. If the data
the data loss. To avoid the problem, you need to dump the operation logs in time.
4.3.4 Dumping Operation Logs Manually
You can dump the operation logs manually on the T2000. The dumped logs are saved as files
and deleted from the database.
4.3.1 Browsing Operation Logs

You can browse the operation logs to know the non-security operations and their results on the
T2000.
Prerequisite
You must be an NMS user with the "Security Watcher" authority or higher.
Procedure
Step 1 Choose System > Browse Log.
Step 2 In the Log Class navigation tree, select Operation Logs. In the right pane, double-click a log
to view its details.
Step 3 Choose to perform the following operations.

l Click Refresh to refresh the security logs.
l Click Filter. In the Filter dialog box, set the conditions to filter the security logs you
browse.

l Click Print. In the Range dialog box, set the start row and the end row. Then click OK.
l Click Save As. In the Save As dialog box, set the start row, end row, and file name. Then
click OK to save the logs to your local disk.
l Click Dump. In the Confirm dialog box, click OK. The operation logs are saved to the
server.
----End
4.3.2 Periodically Dumping Operation Logs

After the periodical dumping task is set, the T2000 can periodically dump the operation logs to
avoid log loss.
Prerequisite
You must log in to the T2000 as user admin.
Context
The scheduled time for a task is based on the server time.
Procedure
Step 2 In the Dump Settings tree, select Operation Logs.
Step 3 In the Enable Dumping Periodically area, set the Periodic dump to Yes.
Step 4 Set the Dump interval (days) and period of saving the record.
Step 5 In the Dump Settings area, set Dumping to (path).
Step 6 Click OK.
----End
Result
Navigate to the directory that is indicated in Dumping to (path) and then view the dumped
operation log files.
4.3.3 Setting the Overflow Dump for Operation Logs

The data amount in an operation log keeps increasing as the system runs day by day. If the data
the data loss. To avoid the problem, you need to dump the operation logs in time.
Prerequisite

Procedure
Step 1 Choose System > Database > Dump Settings from the Main Menu. The Dump Settings dialog
box is displayed.
Step 2 Select Operation Logs in the Dump Settings tree.
Step 3 Set the Maximum capacity parameter, which is 100000 by default.

When the number of records in the operation log exceeds this number, the dump is triggered.
Step 4 Set the Dump percent of the database(%) parameter, which is 100 by default.
The system decides how many records to dump each time according to this value. For example,
when the number of the records exceeds 100000, a dump is performed for 100000 pieces of data
records.
Step 5 Set the Record threshold-crossing value(%), which is 90 by default.

When data of the security log exceeds the value of multiplying Maximum Capacity by Record
threshold-crossing value(%), a threshold-crossing alarm is reported on the T2000.
Step 6 In Dumping to (Path), specify the directory to store the dumped file.
NOTE

Step 7 Click OK.
----End
4.3.4 Dumping Operation Logs Manually

You can dump the operation logs manually on the T2000. The dumped logs are saved as files
and deleted from the database.
Prerequisite
Procedure
Step 1 Choose System > Database > Dump Manually from the main menu.
Step 2 In the Manual Dump navigation tree, select Operation Logs.
Step 3 In the Generation Time of Operation Logs group box, set the dump condition.
Step 4 In the Records That Meet The Dump Condition group box, click Query.
Step 5 Click Dump.
Step 6 Click Close.
----End

Result
Navigate to the directory that is indicated in the Dumping to (path) of the File group box, view
the dumped operation log files.
4.4 Forwarding the T2000 Logs to the Syslog Server

The T2000 can upload operation logs to a Syslog server. An operation log keeps a record of all
types of operations on the T2000. It provides the reference information for the analysis of the
T2000 running status and the follow-up maintenance.
Prerequisite
Procedure
Step 1 Choose System > Log Forwarding Server from the Main Menu.
The Log Forwarding Server window is displayed.
Step 2 Click Refresh and view the parameters and status of the current log forwarding server.
Step 3 Click Add and the Create Log Forwarding Server window is displayed.
Step 4 Set the parameters for the Syslog server.

NOTE
l You must configure the IP address and port of the master server.
l If you want to configure the slave server, you also need to configure the IP address and port of the slave
server.
Step 5 Click OK.

The T2000 logs are transferred to the Syslog server.
----End
4.5 Browse NE Security Logs

The NE security log records the operations performed by all NE users and the results of those
operations. You can view the NE security log and filter the records by NE user, event name and
occurring time..
Prerequisite
l You must be an NM user with "NE monitor" authority or higher.
l Applied to release 5.0 NEs only.
Context
You can view the NE security logs, but you cannot delete them.

Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Security Log from the Function
Tree.
Step 2 Set the conditions for viewing the logs.
Step 3 Click Query.
----End
4.6 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. Applies to the SDH and WDM equipment.
4.6.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.6.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.6.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.6.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.6.5 Starting the Syslog Service
After the syslog service is started, the NE can transmit the syslog to syslog servers.
4.6.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
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-3 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
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-3.

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

Table 4-4 Configuration List
NE Syslog Server IP Address Syslog GNE
NE1, NE4, NE5, NE6, NE7, None NE2

NE8 NE3
NE2 129.1.0.1 NE3
NE3 129.2.0.1 NE2
4.6.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
Step 1 In the NE Explorer, select an NE and choose Security > NE Syslog from the Function Tree.
Step 2 Click the Syslog Server tab. The list of syslog servers is displayed.
Step 3 Click Query to load the configuration data of the syslog server from the NE.
Step 4 Click New and the Add Syslog Server dialog box is displayed.
Step 5 Set the IP, Send Mode and Port based on the network settings.
Step 6 Click OK. A prompt is displayed indicating that the operation is successful.
----End
4.6.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
Step 2 Click the Syslog GNE tab. The list of syslog GNEs is displayed.
Step 3 Click Query to load the syslog GNE configuration from the NE.

Step 4 Click New and the Object Select dialog box is displayed.
Step 5 Choose proper NEs as the syslog GNEs.
Step 6 Click OK. A prompt appears indicating the operation was successful.
----End
4.6.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
Step 1 In the NE Explorer, select an NE and choose Security > NE Syslog .
Step 2 Click Query to load the configuration data from the NE.
Step 3 Click New. The Add Basic Info dialog box is displayed.
Step 4 Choose proper Log Type and Log Severity based on the network requirements.
Step 5 Click OK. A prompt appears indicating the operation was successful.
Step 6 Click Close.
----End
4.6.5 Starting the Syslog Service

After the syslog service is started, the NE can transmit the syslog to syslog servers.
Prerequisite
Procedure
Step 2 Click Query to load the configuration data from the NE.
Step 3 Check the Start Syslog Service check box.
Step 4 Click Apply. A prompt appears indicating the operation was successful.
----End

Operation Guide for Common Features 5 Topology Management
5 Topology Management
About This Chapter
You can manage NEs and fibers through the T2000 after creating their topologies on the
T2000.
5.1 Basic Concepts

Topology structure helps you to learn the layout of the entire network, and the networking and
running information of the equipment. An understanding of basic topology concepts facilitates
the topology management.
5.2 Creating NEs
Each equipment is represented as an NE on the T2000. Before the T2000 manages the actual
equipment, you need to create the corresponding NEs on the T2000. There are two methods 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 only a few NEs, it is recommended that you create the NEs
one by one.
5.3 Configuring the NE Data
Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the T2000 can manage and operate the NE.
5.4 Configuring Master/Slave Subrack
The WDM equipment supports the management of master/slave subracks. When multiple
subracks are required for an NE, the master/slave subrack mode must be adopted for centralized
management. In this mode, multiple subracks are displayed as one NE in the T2000. The
T2000 supports the adding, deletion, and modification of slave subracks, and query of slave
subrack status.
5.5 Adding Boards and Ports
In the NE Panel, you can add a board and set port attributes for the board.
5.6 Query Path Status of the Board
The path status of a board can be idle or occupied.
5.7 Creating Links

5 Topology Management Operation Guide for Common Features
A link is a physical or logical connection between two topological objects in the Main Topology.
When configuring or managing the network by using the T2000, you need to create links between
different topological objects.
5.8 Browsing Fiber/Cable
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 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.10 Adjusting Topology Objects
You can modify the settings when creating the network topology by using the T2000. For
example, adjust the optical NE source, modify the status of the preconfigured NE and so on.
5.11 Deleting Topology Objects
When adjusting the network topology, generally, you need to delete some objects of the topology.

5.1 Basic Concepts

Topology structure helps you to learn the layout of the entire network, and the networking and
running information of the equipment. An understanding of basic topology concepts facilitates
the topology management.
5.1.1 Topology Management Functions

By topology management, you can set up and manage the entire network topology to present
the networking and the status of the devices. You can browse the topology view to know and
monitor the entire network status in real time.
5.1.2 Topology Objects
Topology object refers to an operation object corresponding to the physical equipment. If you
want to manage an NE, board, or fiber/cable on the T2000, you must first create its topology.
5.1.3 Optical NE
An optical NE represents a type of WDM equipment, such as an OTM. An optical NE can contain
one or more NEs. The concepts of optical NE are only for WDM equipment.
5.1.4 GNE and Non-Gateway NE
The T2000 communicates with the NEs through the network to manage the network equipment.
This type of NE that communicates directly with the T2000 through the network is called
gateway NE (GNE). The other NEs that communicate with the T2000 through the GNE are
called non-gateway NEs.
5.1.5 Virtual NE
An virtual NE is an abstraction of an NE or a network that cannot be directly managed by the
T2000. Virtual NEs represent the topological relations between the equipment that the T2000
manages directly and the equipment the T2000 manages indirectly on the topology. If the
equipment that is not managed by the T2000 exists in the network and there are trails created
on the equipment, you can create a virtual NE on the T2000 to represent the equipment.
5.1.6 Fiber Types
You can use the T2000 to manage fibers, radio links, Ethernet cables, DCN communication
cables, and virtual fiber/cable in a centralized manner.
5.1.7 Fiber/Cable Pipe
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.
5.1.8 Flow of Constructing the Network Topology
The flow of constructing the network topology describes the flows of constructing the subnet,
NE, board, port, and link, and the relations of the operation tasks.
5.1.1 Topology Management Functions

By topology management, you can set up and manage the entire network topology to present
the networking and the status of the devices. You can browse the topology view to know and
monitor the entire network status in real time.
Topology management allows you to perform the following operations:
l Customize the view. You can define and organize different views as required.
l Add, delete, modify, cut, or paste submaps.

l Add, delete, modify, copy, paste, or cut topology nodes.

l Adjust the size of a topology view for convenient viewing.
l Set the background. You can obtain the location information on a device node through the
location of the corresponding icon in the background.
l Search for a topology object globally to help the user identify the topology object.
l Present topology object types with different icons. For example, small icons are used to
indicate the topology object status, such as the link status.
l Switch between views quickly through the navigation tree.
l Manage the topology with the auxiliary tools such as the aerial view, print, and filter.
5.1.2 Topology Objects

Topology object refers to an operation object corresponding to the physical equipment. If you
want to manage an NE, board, or fiber/cable on the T2000, you must first create its topology.
By creating topologies, the T2000 sets up the communication with physical equipment in the
network. When the NE data are uploaded to the T2000, the topology in the T2000 has the same
data as the physical equipment. After that, the NE and board configuration on the T2000 are
directly sent to physical NEs.
The T2000 is able to manage the following topologies, which are NE, board, port, channel, fiber,
virtual fiber, microwave link, subnet, Ethernet cable, serial port cable, and extended ECC. Based
on all these topologies, the T2000 can query the data or working status of corresponding objects
in the physical network. The subnet, Ethernet cable and serial port cable are only logical concepts
on the T2000, and cannot be managed physically through their topologies.
5.1.3 Optical NE
An optical NE represents a type of WDM equipment, such as an OTM. An optical NE can contain
one or more NEs. The concepts of optical NE are only for WDM equipment.
NE
An NE represents a WDM equipment subrack. There are several subrack types such as OptiX
BWS 1600G and OptiX Metro 6100. Applies to the WDM equipment.
Optical NE
An optical NE refers to the isolated physical entity that provides the NE functions in the optical
transmission network.
The T2000 manages the WDM equipment through different optical NEs. There are four types
of optical NEs. They are WDM_OTM, WDM_OLA, WDM_OADM and WDM_OEQ. Applies
to the WDM equipment. Each optical NE can contain multiple NEs.
5.1.4 GNE and Non-Gateway NE

The T2000 communicates with the NEs through the network to manage the network equipment.
This type of NE that communicates directly with the T2000 through the network is called
gateway NE (GNE). The other NEs that communicate with the T2000 through the GNE are
called non-gateway NEs.

GNE
The GNE communicates with the T2000 by using the communication protocol. The T2000
manages the network through GNEs.
Each T2000 must connect to at least one GNE.
Non-gateway NE
The non-gateway NE communicates with the GNE by using the ECC or the extended ECC.
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. Do not connect
more than 60 non-gateway NEs to a GNE.
NOTE
If the number of non-gateway NEs that connect to a GNE is more than 50, an alarm is reported on the
T2000.
5.1.5 Virtual NE
An virtual NE is an abstraction of an NE or a network that cannot be directly managed by the
T2000. Virtual NEs represent the topological relations between the equipment that the T2000
manages directly and the equipment the T2000 manages indirectly on the topology. If the
equipment that is not managed by the T2000 exists in the network and there are trails created
on the equipment, you can create a virtual NE on the T2000 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 T2000, it is usually used to simulate the equipment
that cannot be directly managed by the T2000, for example, the equipment that is not managed
by the T2000, such as the third-party equipment.
You can configure boards for a virtual NE on the T2000. 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 T2000.
The concept of virtual NE just for the SDH equipment.
5.1.6 Fiber Types

You can use the T2000 to manage fibers, radio links, Ethernet cables, DCN communication
cables, and virtual fiber/cable in a centralized manner.
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 T2000 classifies the fiber as four types, which are G.652, G.653, G.654, and G.
655 fibers.
Radio Link
A radio link uses the microwave to connect different outdoor units of radio equipment.

Ethernet Cable
The Ethernet cable that the T2000 can manage is used to connect the communication interface
of the gateway NE and the T2000 server.
DCN Communication Cable

A DCN communication 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.
Virtual Fiber/Cable
Virtual fiber/cable is a logical concept. It may contains several physical fibers, radio links, or
even one or more complete networks.
5.1.7 Fiber/Cable Pipe

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. For example, optical
cables.
A fiber/cable pipe contains multiple fibers/cables and a fiber/cable belongs to multiple fiber/
cable pipes.
5.1.8 Flow of Constructing the Network Topology

The flow of constructing the network topology describes the flows of constructing the subnet,
NE, board, port, and link, 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
Manage Manage
Manage NEs Manage links
subnets boards/ports
Create
Create NEs Add boards Create links
subnets
Modify subnet Create optical Modify the fiber

Add ports
names NEs information
Delete Create virtual Modify types of

Name fibers
subnets NEs boards and ports
Configure the
Delete boards Delete fibers
NE data
Modify NE
IDs
Modify NE
names
Required
Delete NEs Optional
The landscape orientation of the configuration flow diagram shows the four main phases of
constructing the network topology. They are managing subnets, managing NEs, managing
boards or ports, and managing links.
The portrait orientation of the configuration flow chart shows the operation tasks and the
relations between the operation tasks in each phase.
5.2 Creating NEs

Each equipment is represented as an NE on the T2000. Before the T2000 manages the actual
equipment, you need to create the corresponding NEs on the T2000. There are two methods 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 only a few NEs, it is recommended that you create the NEs
one by one.
5.2.1 Creating NEs in Batches

When the T2000 communicates properly with a GNE, you can search for all NEs that
communicate with the GNE by using the IP address of the GNE or the network segment to which
the IP address is associated, or by using the NSAP address of the NE. Then, you can create NEs
in batches. This method is quicker and more accurate than manual creation.

5.2.2 Creating a Single NE

The T2000 can manage an NE after the NE is created. Although creating a single NE is not as
fast and accurate as creating NEs in batches, you can perform this operation regardless of whether
the data is configured on the NE or not.
5.2.3 Creating Optical NEs
The T2000 allocates the WDM equipment and OptiX BWS 1600S into different optical NEs for
management. There are four types of optical NEs. They are WDM_OADM, WDM_OEQ,
WDM_OLA and WDM_OTM.
5.2.4 Creating Virtual NE
To display the topological relations between the equipment that is directly managed by the
T2000 and the equipment that is indirectly managed by the T2000 on the topology, you must
create virtual NEs so that the T2000 manages them together with the regular NEs in a uniform
manner.
5.2.1 Creating NEs in Batches

When the T2000 communicates properly with a GNE, you can search for all NEs that
communicate with the GNE by using the IP address of the GNE or the network segment to which
the IP address is associated, or by using the NSAP address of the NE. Then, you can create NEs
in batches. This method is quicker and more accurate than manual creation.
Prerequisite
The T2000 must communicate properly with the GNE.
The NE Explorer instance of the NEs must be created.
Procedure
Step 1 Choose File > Search for NE from the Main Menu. The Search for NE window is displayed.
Step 2 Click Add and the Input Search Domain dialog box is displayed.
Step 3 Set Address type to IP Address Range of GNE, IP Address of GNE, or NSAP Address, and
enter Search Address, User Name, and Password. Then, click OK.

NOTE
You can repeat Steps 2 through 3 to add more search domains. You can delete the system default search
domain.
l If you use IP address to search for NEs:
l Usually, the broadcast function is disabled on the routers on a network, to avoid network broadcast
storm. Therefore, by using the IP Address Range of GNE method, only the NEs in the same
network segment can be searched out.
l To search the network segments across routers, the IP Address of GNE method is recommended.
Through a gateway NE, you can search out the NEs in the network segment of the gateway NE.
l If you use NSAP address, you can only select NSAP address.
Step 4 Click Start. The Search for NE dialog box is displayed.

Step 5 In the Search for NE dialog box, you can perform the following operations:
l Select Search for NE and click OK to search for all NEs in the selected domain.
l Select Create device after search, and enter NE user and Password. Then, click OK.
NOTE
l The default NE user is root.

l The default password is password.
l Select Upload after create and click OK, so that the NE data can be uploaded to the
T2000 after the NE is created.
NOTE
If you select all options in the Search for NE dialog box, you can search for NEs, create the NEs, and
upload the NE data at one time.
Step 6 Optional: If you select Search for NE only, you can select the NEs, which are not yet created,
in the Result list after the search for NEs is complete. Click Create and then the Create dialog
box is displayed. Enter User Name and Password in the Create dialog box, and then click
OK.
Step 7 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.
----End
Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
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.2.2 Creating a Single NE

The T2000 can manage an NE after the NE is created. Although creating a single NE is not as
fast and accurate as creating NEs in batches, you can perform this operation regardless of whether
the data is configured on the NE or not.
Prerequisite
The license must be installed and the license must support creating the NE of the type.
The NE Explorer instance of the NEs must be created.
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 T2000 is
abnormal, the NE is displayed in gray color.
Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Device from the shortcut
menu. The Add Object dialog box is displayed.
Step 2 Select the NE type from the Object Type tree.
Step 3 Complete the following information: ID, Extended ID, Name and Remarks.

Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.
Step 5 Choose Gateway Type, Protocol and set the IP address and NSAP address.
NOTE
OptiX OSN 1800/3800/6800/8800 I do not support NSAP address setting.
1. Select Gateway from the Gateway Type drop-down list.
2. Select the Protocol type.
If the T2000 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.
If the T2000 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.

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).
Step 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.
Step 7 In the case of a WDM NE, select the optical NE to which the WDM NE is associated.
Step 8 Enter the NE User and Password.

NOTE
The default NE user is root, and the default password is password.
Step 9 Optional: If you do not want to apply the NE configuration data in the T2000 to the NE, check
the NE Preconfiguration check box, and set NE Software Version.
NOTE
If you apply the configuration data of the preconfigured NE to the actual NE when the configuration data
on the preconfigured NE is inconsistent with that on the actual NE, the actual services will be affected.
Step 10 Click OK. Then, click in the blank space of the Main Topology and the NE icon appears in the
position where you clicked.
Step 11 Click OK. Then, click Open in the dialog box displayed.
----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 T2000 database.
Postrequisite
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 T2000 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.2.3 Creating Optical NEs

The T2000 allocates the WDM equipment and OptiX BWS 1600S into different optical NEs for
management. There are four types of optical NEs. They are WDM_OADM, WDM_OEQ,
WDM_OLA and WDM_OTM.
Prerequisite
l You must be an NM user with "NM operator" authority or higher.

l The license must be installed and the license must support creating the NE of the type.
l Applies to the WDM equipment.
l Applies to Submarine Line Equipment.
Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Device from the shortcut
menu.
Step 2 Select the optical NE type for the optical NE in the Add Object dialog box.
Step 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.
Step 4 Click the Resource Division tab. Select NEs or boards from the Idle ONE and click .
Step 5 Click OK.
Step 6 Click in the blank space of the Main Topology and the NE icon appears in the position where
you clicked.
----End
5.2.4 Creating Virtual NE

To display the topological relations between the equipment that is directly managed by the
T2000 and the equipment that is indirectly managed by the T2000 on the topology, you must
create virtual NEs so that the T2000 manages them together with the regular NEs in a uniform
manner.
Prerequisite
l You must be an NM user with "NM operator" authority or higher.
l Applies to the SDH equipment.
Procedure
Step 1 Right-click the Main Topology and choose New > Device from the shortcut menu. The Add
Object dialog box is displayed.
Step 2 Choose NE > SDH Series > Virtual NE from the Object Tree.
Step 3 Enter the ID, Name, and Remarks of the NE.
Step 4 Click OK. Then click the Main Topology. The NE icon is displayed at the spot where you clicked
the mouse button.
----End

5.3 Configuring the NE Data

Though an NE is successfully created, it is not configured. You need to configure the NE first
so that the T2000 can manage and operate the NE.
5.3.1 Configuring the NE Data Manually

By configuring NE data manually, you can configure the board slot information of an NE.
5.3.2 Replicating the NE Data
You can replicate the data of an existing NE to a new NE, if the existing NE is already
configuration and if the existing NE is of the same NE type and the same NE version as the new
NE.
5.3.3 Uploading the NE Data
By uploading the NE data, you can synchronize the current NE configuration data to the network
management system directly.
5.3.4 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 T2000.
5.3.1 Configuring the NE Data Manually

By configuring NE data manually, you can configure the board slot information of an NE.
Prerequisite
The NE must be created successfully.
Procedure
Step 1 Select the NE whose data you need to configure.
NE to Be Configured Operation
SDH equipment Double-click the unconfigured NE on the

Main Topology. Then, the NE
Configuration Wizard dialog box is
displayed.
RTN equipment Double-click the unconfigured NE on the

Main Topology. The NE Configuration
Wizard dialog box is displayed.
PTN equipment Double-click the unconfigured NE on the


WDM equipment 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
Submarine equipment Double-click the optical NE with

Step 2 Select Manual Configuration and click Next. The Confirm dialog box is displayed, indicating
that manual configuration clears the data on the NE side.
Step 3 Click OK. The Confirm dialog box is displayed, indicating that manual configuration interrupts
the service on the NE.
Step 4 Click OK. The Set NE Attribute dialog box is displayed.

Step 5 Optional: If you need to modify the NE Attribute, set NE Name, Equipment Type, NE
Remarks, and Subrack Type.
Step 6 Click Next, and the NE slot window is displayed.
Step 7 Optional: Click Query Logical Information to query the logical boards of the NE.
Step 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.
Step 9 Optional: Right-click on the slot to add a board.
Step 10 Click Next to display the Send Configuration window.
Step 11 Select Verify and Run as required and click Finish.

NOTE
Verification involves running the verification command. Click Finish to deliver the configuration to the
NE and complete the basic configurations for the NE. After the verification is successful, the NE starts to
work normally.
----End
5.3.2 Replicating the NE Data

You can replicate the data of an existing NE to a new NE, if the existing NE is already
configuration and if the existing NE is of the same NE type and the same NE version as the new
NE.
Prerequisite
The type and NE software version of the source NE must be consistent with the type and software
version of the replicated NE.

Procedure
Step 1 Select the NE whose data you need to replicate.

displayed.

displayed.



Step 2 Select Copy NE Data and click Next. The NE Replication dialog box is displayed.
Step 3 Select the NE from the drop-down list and click Start. The Confirm dialog box is displayed,
indicating that the replication operation copies all the data of the source NE.

NOTE
After the NE data is replicated, only the data on the T2000 side is changed, but the data on the equipment
side is not changed.
Step 4 Click OK. The Confirm dialog box is displayed, indicating that the replication operation results
in the loss of the original data of the NE to which the data is copied.
Step 5 Click OK to start the replication. The Operation Result dialog box is displayed after a few
seconds.
Step 6 Click Close.
----End
5.3.3 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
Step 1 Select the NE whose data you need to Replicate.

displayed.


displayed.

unconfigured subrack on the Main Topology.
Then, double-click the unconfigured subrack
in the left-hand pane and the NE
displayed.


unconfigured subrack on the Main Topology.
Then, double-click the unconfigured subrack
in the left-hand pane and the NE
displayed.
Step 2 Select Upload and click Next. The Confirm dialog box is displayed, indicating that the upload
may take a long time.
Step 3 Click OK to start the upload. The Operation Result dialog box is displayed when the uploading
is complete.
Step 4 Click Close.
----End
5.3.4 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 T2000.
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 equipment.
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 T2000 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 slot diagram.
2. Right-click the NE slot diagram 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 slot diagram 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 slot diagram.
l Configure Data in Batches:
1. Choose Configuration > Configuration Data Management from the Main 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
T2000 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.4 Configuring Master/Slave Subrack

The WDM equipment supports the management of master/slave subracks. When multiple
subracks are required for an NE, the master/slave subrack mode must be adopted for centralized
management. In this mode, multiple subracks are displayed as one NE in the T2000. The
T2000 supports the adding, deletion, and modification of slave subracks, and query of slave
subrack status.
5.4.1 Master/Slave Subrack Configuration

In the master/slave subrack mode, the master subrack and its multiple slave subracks are
displayed as one NE in the network management system. They share the same NE ID and IP
address.
5.4.2 Adding a Slave Subrack
After slave subracks are added, these subracks can communicate with the T2000 through a master
subrack. Thus, the service grooming capability of the equipment is enhanced.
5.4.3 Modifying Subrack Name
You can set the attributes of the master or slave subrack to modify the name of the master or
slave subrack.
5.4.4 Querying the Status of a Slave Subrack
You can query the status of a slave subrack. The status includes Physical Installed, Logical
Installed, and Not Installed.
5.4.5 Deleting a Slave Subrack
You can delete the slave subrack that is not required.

5.4.1 Master/Slave Subrack Configuration

In the master/slave subrack mode, the master subrack and its multiple slave subracks are
displayed as one NE in the network management system. They share the same NE ID and IP
address.
Generally, the subrack where the optical amplifier board, optical supervisory channel (OSC)
board, and fiber interface unit (FIU) exist is selected as the master subrack.
The SCC boards that support master/slave subrack configuration on the OptiX BWS 1600G
include E4SCC and E4SCU. E4SCC is the SCC board on the master subrack and E4SCU is the
SCC board on the slave subrack. The master subrack can be cascaded to a maximum of 13 slave
subracks. The E4SCC board communicates with the other boards on the slave subrack through
the E4SCU board.
A subrack and other subracks can be cascaded through the ETHERNET2 interface on the subrack
or the ETH interface on the front panel of the E4SCC or E4SCU board on the subrack, but the
two interfaces are not connected directly and communication is unavailable. Therefore, when
the ETH interface of the local subrack is connected with the ETHERNET2 interface of the
downstream subrack and the ETHERNET2 interface of the local subrack is connected to the
ETH interface of the upstream subrack, the NE needs to transmit data between the ETH interface
and ETHERNET2 interface of the local subrack. In this way, the communication between the
master and slave subracks is realized.
NOTE
For details about the interfaces, refer to the OptiX BWS 1600G Backbone DWDM Optical Transmission
System Hardware Description.
During the process of cascading the master and slave subracks, the E4SCC board cannot be used
as the SCC board on a slave subrack. If there are multiple E4SCC boards on the NE that has the
master and slave subracks, an alarm that indicates a master subrack ID conflict is reported to the
user. The user removes the master subrack ID conflict by making the redundant master subrack
offline.
The master and slave subracks can be cascaded to form a star, chain, or ring network. The star
network, however, requires a HUB additionally. In addition, the slave subrack IDs cannot be
allocated in an order. Hence, the chain and ring networks are recommended, and the star network
is not recommended.
NOTE
l The slave subrack IDs between 1 and 13 are allocated automatically.
l The allocated slave subrack ID is stable and does not change when the subrack connection changes.
l You can configure an interface manually. When the allocated slave subrack ID is incorrect, you can
correct the ID.
l The MAC addresses of the ETHERNET2 and ETH interfaces are unique.
l The ETHERNET1 interface on the subrack and the ETHERNET2 and ETH interfaces cannot be
connected to the same HUB.
Rules of Allocating Slave Subrack IDs Automatically

In the case of the OptiX BWS 1600G, slave subrack IDs are allocated automatically by observing
the following rules:

l If the master and slave subracks are cascaded to form a ring, IDs are allocated to the slave
subrack that is connected to the ETHERNET2 interface on the master subrack and other
slave subracks one by one.
l When the ring is disconnected at a certain point, IDs are allocated one by one to the slave
subracks that are connected to the ETHERNET2 interface on the master subrack, and then
IDs are allocated one by one to the slave subracks that are connected to the ETH interface
on the master subrack.
l IDs are allocated one by one to new subracks according to the preceding rules.
l To ensure that the IDs of the master and slave subracks are stable, the master subrack saves
the IDs that are already allocated to subracks based on the MAC addresses of the
ETHERNET2 and ETH interfaces on the slave subracks. If an ID is allocated to a slave
subrack, after the slave subrack is online, the NE sends the corresponding ID to the slave
subrack instead of allocating a new ID.
Methods of Allocating Slave Subrack IDs Automatically

In the case of the OptiX BWS 1600G, slave subrack IDs are allocated automatically by using
the following methods:
l After a slave subrack is online, the slave subrack sends an ID request frame to the
ETHERNET2 and ETH interfaces on the master subrack periodically. When the master
subrack receives the frame, the master subrack allocates an unallocated ID whose value is
the smallest to the slave subrack.
l To ensure that slave subrack IDs are allocated according to the connection order, each slave
subrack does not forward the ID request frames from other slave subracks before its ID is
allocated.
l When the ring is disconnected at a certain point, to ensure that slave subrack IDs are
allocated according to the connection order, the master subrack allocates an ID to the slave
subrack immediately when the ETHERNET2 interface receives an ID request frame. The
master subrack does not allocate an ID immediately when the ETH interface receives an
ID request frame. Instead, the master subrack waits a period. During the period if the
ETHERNET2 interface does not receive an ID request frame, the master subrack allocates
IDs to the slave subrack that is connected to the ETH interface and to other slave subracks
according to the connection order.
l The IP address of a slave subrack derives from the ID of the slave subrack. After a slave
subrack is offline, the slave subrack ID saved on the master subrack is not released. When
there is no idle ID, the master subrack selects the ID of the slave subrack that is offline for
a longer time to the new online slave subrack. This ensures that slave subrack IDs are stable.
Process of Allocating Slave Subrack IDs Automatically

In the case of the OptiX BWS 1600G, slave subrack IDs are dynamically allocated by the master
subrack and are bound to the MAC addresses of the ETHERNET2 and ETH interfaces on the
slave subracks. The allocation result of the slave subrack IDs is saved to the database on the
master subrack. After a slave subrack is powered on, the slave subrack negotiates an ID with
the master subrack. If the ID is negotiated successfully, the ID allocated by the master subrack
is saved to the reserved area in the flash memory on the E4SCU board and the NE software is
started. If negotiated unsuccessfully, the NE software is not started. The slave subrack first uses
the ID saved in the reserved area in the flash memory on the E4SCU board to negotiate with the
master subrack. Otherwise, the slave subrack requests the master subrack to allocate an idle ID.
When the master and slave subracks are cascaded, the slave subrack broadcasts request frames
periodically. After receiving the request frame from the slave subrack, the master subrack

allocates an ID to the slave subrack based on the MAC address of the request frame and notifies
the slave subrack of the ID. Then, the slave subrack checks the received ID. If this new ID is
different from the original ID, or the MAC address of the master subrack is changed (for example,
the slave subrack is connected to another master subrack), the slave subrack is reset and
negotiates with the master subrack about the ID. If the slave subrack ID repeats an existing slave
subrack ID, the master subrack allocates a new ID to the salve subrack and notifies the slave
subrack of the new ID.
When you replace the SCC board of the OptiX BWS 1600G,
l the MAC address changes after you replace the SCC board on the slave subrack. Hence,
the master subrack allocates a new ID to the slave subrack. The board configuration and
other configuration of the slave subrack are related to the slave subrack ID. If the slave
subrack ID changes after you replace the SCC board on the slave subrack, you need to
modify the slave subrack ID and reset the slave subrack, to ensure that the configuration
data of the slave subrack is consistent.
l you need to restore the configuration data of the original master subrack after you replace
the SCC board on the master subrack, to ensure that the IDs of all slave subracks remain
unchanged.
5.4.2 Adding a Slave Subrack

After slave subracks are added, these subracks can communicate with the T2000 through a master
subrack. Thus, the service grooming capability of the equipment is enhanced.
Prerequisite
Applies to the OptiX OSN 6800 and OptiX OSN 8800 I.
Applies to the OptiX BWS 1600G.
Procedure
Step 1 On the Main Topology, double-click an optical NE and the NE Panel is displayed. In the left-
hand pane of the NE Panel, select the NE.
Step 2 In the Add Slave Subrack dialog box, set parameters and click OK.
NOTE
For the OptiX OSN 8800 I, you need to set the Service Type and Service Capacity for the subracks.
Step 3 The Operation Result dialog box is displayed telling you that the operation was successful.
Click Close.
----End
5.4.3 Modifying Subrack Name

You can set the attributes of the master or slave subrack to modify the name of the master or
slave subrack.
Prerequisite

The master and slave subracks must be created.
Procedure
Step 2 In the upper portion of the NE Panel, select the master or slave subrack for which you want to
modify the name, right-click, and choose Modify Subrack Name from the shortcut menu. The
Modify Subrack Name dialog box is displayed.
Step 3 Modify the Subrack name and click OK.

NOTE
For the OptiX OSN 8800 I, you need to set the Service Type and Service Capacityervice Capacity for the
subracks.
----End
5.4.4 Querying the Status of a Slave Subrack

You can query the status of a slave subrack. The status includes Physical Installed, Logical
Installed, and Not Installed.
Prerequisite
The master and slave subracks must be created.
Procedure
Step 2 In the upper portion of the NE Panel, select a slave subrack and query the status of the slave
subrack.

NOTE
Click the toolbar button to view legends to know the running status of the subrack.
----End
5.4.5 Deleting a Slave Subrack

You can delete the slave subrack that is not required.
Prerequisite
All boards in the slave subrack must be deleted.
Procedure
Step 2 In the upper portion of the NE Panel, select the slave subrack to be deleted, right-click, and
choose Delete the Subrack from the shortcut menu.
Step 3 In the Confirm dialog box displayed, click OK.
----End
5.5 Adding Boards and Ports

In the NE Panel, you can add a board and set port attributes for the board.
5.5.1 Adding Boards

When manually configuring the NE dataWhen configuring the NE data, 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.5.2 Adding Sub-Boards
The equipment can realize different functions after you add different sub-boards to a processing
board.

5.5.3 Adding Dynamic Ports

Before you create fiber connections for some preconfigured NEs, you must create dynamic ports
on the NE boards.
5.5.4 Adding Client Side Ports
Client side ports of the OTU board on the NG WDM equipment support color light and colorless
light. You need to add different ports on the T2000 according to the SFP optical module used
on the equipment.
5.5.5 Adding a Line-Side Port
Line-side (WDM-side) ports of the OTU board on the NG WDM equipment support color light
and black-and-white light. You need to add different ports to the T2000 according to the SFP
optical module used on the equipment.
5.5.1 Adding Boards

When manually configuring the NE dataWhen configuring the NE data, 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 The NE must be created.
l There must be idle slot on the NE Panel.
Context
The physical boards are the actual boards inserted in the subrack. A logical board refers to a
board that is created on the T2000. After a logical board is created, you can configure the relevant
services. If the corresponding physical board is online, the configured services can be available.
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
Step 1 Open the NE Panel.
For the SDH equipment, double-click the icon of the NE.
For the RTN equipment, double-click the icon of the NE.
For the PTN equipment, double-click the icon of the NE.
For the WDM equipment, double-click the icon of the optical NE. In the left pane of the NE
Panel, click the NE that you want to add the board.
Step 2 Right-click the selected idle slot. Select the board you want to add from the drop-down list.
----End

5.5.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 MP1 boardCXP board.
Context
Hot swappable service sub-board interfaces are provided on the MP1 boardCXP 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
Step 1 Double-click an NE on the Main Topology and the NE Panel is displayed in the user interface.
Step 2 Select the desired processing board, right-click in the blank area that displays sub-boards, and
select the desired sub-board.
----End
5.5.3 Adding Dynamic Ports

Before you create fiber connections for some preconfigured NEs, you must create dynamic ports
on the NE boards.
Prerequisite
l The board must be created on the preconfigured NE.
l Applies to the OpitX OSN 1500, OpitX OSN 2500, OpitX OSN 3500, OpitX OSN 7500
and OpitX OSN 9500.
Procedure
Step 1 Double-click the icon of the preconfigured NE in the Main Topology. The NE panel is displayed.

Step 2 Right-click the port to which you want to add a dynamic port and choose Add Port from the
shortcut menu. The Add Port dialog box is displayed.
Step 3 Specify the Port, Type and Level. Click OK.
----End
5.5.4 Adding Client Side Ports

Client side ports of the OTU board on the NG WDM equipment support color light and colorless
light. You need to add different ports on the T2000 according to the SFP optical module used
on the equipment.
Prerequisite
l Applies to the OTU boards on the NG WDM equipment.
l The OTU boards not supported are as follows: LDGD, LDGS, LWX2, LWXD, LWXS,
TDG, TSXL, TQX, and TQS.
l There are client-side ports that are not added on the T2000.
Context
By default, each board is added with client side ports. To add ports, you need to delete the client
side ports that are added by default on the T2000.
Procedure
Step 1 On the Main Topology, double-click an optical NE, and the NE Panel is displayed.
Step 2 In the NE Panel, select a board, right-click, and choose Path View from the shortcut menu.
Step 3 In the Path View, right-click in the blank area and choose Add Port from the shortcut menu.
The Add Port dialog box is displayed.

Step 4 Select the Port, Type, and Level. Click OK.
----End
5.5.5 Adding a Line-Side Port

Line-side (WDM-side) ports of the OTU board on the NG WDM equipment support color light
and black-and-white light. You need to add different ports to the T2000 according to the SFP
optical module used on the equipment.
Prerequisite
l The OTU boards must be applicable to the NG WDM equipment.
l The following OTU boards are supported: 2LDX, 12TMX, 12LOG, 12LOM, 12TQS,
11TOG, 12NQ2, 12ND2, and 13LSX.
l There must be line-side (WDM-side) ports that are not added to the board.
By default, each board is added with line-side (WDM-side) ports. To add ports, you need to
delete the line-side (WDM-side) ports that are added by default on the T2000.
Procedure
Step 1 On the Main Topology, double-click an optical NE, and the NE Panel is displayed.
Step 2 In the NE Panel, select a board, right-click, and choose Path View from the shortcut menu.
Step 3 In the Path View, right-click in the blank area and choose Add Port from the shortcut menu.
The Add Port dialog box is displayed.

Step 4 Select the Port, Type, and Level. Click OK.
----End
5.6 Query Path Status of the Board

The path status of a board can be idle or occupied.
Prerequisite
Procedure
Step 1 On the Main Topology, double-click an NE.
Step 2 In the NE Panel, double-click the required board.
Step 3 In the Board View window, query the path status of a board.
NOTE
You can view the meanings of various icons and colors in the right pane of the channel view.
----End
5.7 Creating Links

A link is a physical or logical connection between two topological objects in the Main Topology.
When configuring or managing the network by using the T2000, you need to create links between
different topological objects.
5.7.1 Creating Fibers Automatically

By using the fiber 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
T2000. For a newly created network, after configuring boards on the T2000, 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.7.2 Creating Fibers for SDH Equipment Manually

NEs communicate with each other through fibers. After creating boards for each NE, you need
to create fibers for further configuration of services. In this situation, you can manually create
fibers one by one.
5.7.3 Creating Fibers for PTN Equipment Manually
fibers one by one.
5.7.4 Creating Fibers in the Synchronization Mode
On the T2000, you can synchronize the fiber connection data of the T2000 with the internal fiber
connection data of the NEs.
5.7.5 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 the scenario where you create a large number of
fibers one by one.
5.7.6 Creating Fiber Connections in List Mode
In Fiber/Cable Management, you can manage the fiber connections between NEs and inside
NEs in a unified manner. Compared with the graphic mode, the creating fiber connections in the
list mode is not visual. Hence, the list mode is applicable to the scenario where you create a few
fiber connections only.
5.7.7 Creating Fibers Between an OTU Board and a Mux/Demux Board in Batches
To create a great number of fibers between an OTU board and a Mux/Demux board, you can
connect fibers in batches to improve the efficiency.
5.7.8 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 T2000. In this way, you can monitor the actual
working state of each radio link.
5.7.9 Manually Creating Radio Links
After you manually fill in the table, the T2000 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.7.10 Creating DCN Communication Cable
The T2000 can communicate with NEs through the Ethernet port or serial port. The NEs also
communicate with each other through the extended ECC. Depending on the communication
mode, different types of cables can be created on the T2000.
5.7.11 Creating Virtual Fibers
When the T2000 manages the SDH, PTN and WDM equipment at the same time, you can create
virtual fibers for SDH or PTN equipment with WDM equipment in between, to facilitate
administration.
5.7.12 Restoring the Fiber Connection
Due to misoperations or other causes, the fiber connection is deleted on the T2000. This does
not affect the service transport, but you need to restore the fiber connection quickly, to restore
the monitoring on the T2000.
5.7.13 Creating a Fiber/Cable Pipe
To manage certain fibers/cables as a pipe, you need to create a fiber/cable pipe.

5.7.14 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.
5.7.1 Creating Fibers Automatically

By using the fiber 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
T2000. For a newly created network, after configuring boards on the T2000, 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.
Prerequisite
l The optical interfaces of every NE must be connected using fibers.
l The boards of every NE must be created on the T2000.
Context
l If conflicting fibers are found during the creation, delete the conflicting fibers on the
T2000 before you start creating fibers.
l When a fiber between two SDH NEs passes through a WDM NE, if the normal fiber
between an SDH NE and a WDM NE has been created on the T2000, the fiber found by
the trail search function is created as a virtual fiber. If the WDM NE is not created on the
T2000, 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 SDH and WDM equipment, the fiber is unidirectional.
CAUTION
Fiber/Cable search may interrupt services. Exercise caution when performing this operation.
Procedure
Step 1 Choose File > Search for Fiber/Cable from the Main Menu.
Step 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 for ports of created fibers on T2000 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 for ports of created fibers on T2000 check box, and if all the selected
ports have fibers created, the system displays a message indicating that the search field is null.
Step 3 A prompt is displayed indicating that the operation is successful. Click Close.

Step 4 To create fibers, select one or more fibers from the Newly Searched Fiber list and click Create
Fiber/Cable.
NOTE
l When one or more fibers are selected in the Newly Searched Fiber list, fibers that conflict with the
selected fibers, are shown in the Existing Conflicting Fiber 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.
Step 5 To delete the conflicting fibers, from the Existing Conflicting Fiber list select one or more
fibers whose values are Yes for the Existing Conflicting link (Y/N) parameter in the
Misconnected Fiber 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.7.2 Creating Fibers for SDH Equipment Manually

fibers one by one.
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.
When a fiber is created, it is usually bidirectional. But when the fiber is connected to the ports
of the REG functions or the SDH and WDM equipment, the fiber is unidirectional.
Procedure
Step 1 Right-click in the Main Topology and choose New > Link. The Add Object dialog box is
displayed.
Step 2 Choose Link > Fiber/Cable from the left pane.
Step 3 Click the button in Source NE. Select the source board and port in the Select the source end
of the link dialog box.
Step 4 Click OK and the cursor changes to a + sign.
Step 5 Click the sink NE of the fiber or cable on the Main Topology.
Step 6 Click the button in Sink NE. Select the sink board and port in the Select the sink end of the
link dialog box.

TIP
When selecting a wrong source or sink NE, right-click and click OK in the Object Selection dialog box
to exit.
Step 7 Click OK. Enter the information of the fiber or cable in the Create Fiber/Cable dialog box.
Step 8 Click OK. The created fiber or cable appears between the source and sink NEs on the Main
Topology.
Step 9 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
5.7.3 Creating Fibers for PTN Equipment Manually

fibers one by one.
Prerequisite
l The boards to be connected with fibers or cables must be created.
Procedure
displayed.
Step 2 Choose Link > Fiber/Cable from the left pane.

Step 3 Click the button in Source NE. Select the source board and port in the Select the source end
of the link dialog box.
Step 5 Click the sink NE of the fiber or cable on the Main Topology.
Step 6 Click the button in Sink NE. Select the sink board and port in the Select the sink end of the
link dialog box.
TIP
When selecting a wrong source or sink NE, right-click and click OK in the Object Selection dialog box
to exit.
Step 7 Click OK. Enter the information of the fiber or cable in the Create Fiber/Cable dialog box.
NOTE
Automatically Allocate IP: When you create a fiber/cable, if both ends of the fiber/cable are the PTN
equipment, the system can automatically allocate IP addresses to microwave ports, Ethernet ports, and POS
ports. If this parameter is set to Yes, the system automatically allocates IP addresses to the ports on the two
ends of a fiber after the fiber is created. In this case, after the fiber is created, you can directly configure
the static tunnel as required without considering the port IP addresses. To configure the dynamic tunnel,
you need to configure the corresponding routing protocol.
Step 8 Click OK. The created fiber or cable appears between the source and sink NEs on the Main
Topology.
Step 9 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
5.7.4 Creating Fibers in the Synchronization Mode

On the T2000, you can synchronize the fiber connection data of the T2000 with the internal fiber
connection data of the NEs.
Prerequisite

The corresponding logical board must be created.
Applies to OptiX OSN 3800, OptiX OSN 6800 and OptiX OSN 8800 I.
Context
Conflicting fibers refer to the fibers that are configured on the T2000 and NEs and that share
neither the same source or sink.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Fiber Synchronization from the
Function Tree.
Step 2 Click Synchronize, and the data of the internal fiber connections on the T2000 side and that on
the NE side are displayed.
NOTE
Synchronized Fiber: Indicates the fibers that exist on both the T2000 and NEs. In addition, the fiber data
on the T2000 is the same as the fiber data on NEs.
Uncreated Fiber in T2000: Indicates the fibers that exist on only NEs.
Uncreated Fiber in NE: Indicates the fibers that exist on only the T2000.
Step 3 Handle different situations as follows:

l If uncreated fiber in T2000 or uncreated fiber in NE exists, select all the fibers. Click Create
Fiber/Cable, and the Operation Result dialog box is displayed. Click Close. The
synchronized fibers are displayed in the Synchronized Fiber list.
l If conflicting fibers exist, fibers cannot be created. You can click Delete Fiber/Cable to
delete the uncreated fibers in T2000 or uncreated fibers in NEs, and then click Create
Fiber/Cable to re-create the remaining fibers.
----End
5.7.5 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 the scenario where you create a large number of
fibers one by one.
Prerequisite
l Optical NEs and NEs must be created.
l The line boards that have the ports at the same level must be created on the T2000 or the
physical boards must be installed correctly.
l Applies to WDM equipment.
l Applies to Submarine Line Equipment.
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:
NOTE
Creating fiber connections between NEs is performed on the Main Topology. Actually, the FIU fiber
connections between stations are created.
1. Click the shortcut icon on the Main Topology and 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

Postrequisite
After you create fiber connections, you need to scan wavelengths to ensure that the fiber
connections are correct and the line communication is available.
5.7.6 Creating Fiber Connections in List Mode

In Fiber/Cable Management, you can manage the fiber connections between NEs and inside
NEs in a unified manner. Compared with the graphic mode, the creating fiber connections in the
list mode is not visual. Hence, the list mode is applicable to the scenario where you create a few
fiber connections only.
Prerequisite
The board on relevant NEs must be created.
Procedure
Step 1 Choose File > Fiber/Cable Management from the Main Menu.
Step 2 Click Create, and the Create Fibers in Batches dialog box is displayed.
Step 3 Click Select Object, select all the NEs you need to create fiber/cable in the dialog box.
Step 4 Click OK.
Step 5 Click New in the Create Fibers in Batches dialog box.
Step 6 Set Direction, Source NE, Source Port, Sink NE and Sink Port.
Step 7 Click Apply.

TIP
You can create multiple fibers/cables and set parameters in step 5, click Apply.
Step 8 Repeat Step 5-7 to create another fiber connection.
Step 9 Click Cancel to complete the settings. The created fiber connections are displayed in the Fiber/
Cable Information list.
----End

Postrequisite
After you create fiber connections, you need to scan wavelengths to ensure that the fiber
connections are correct and the line communication is available.
5.7.7 Creating Fibers Between an OTU Board and a Mux/Demux

Board in Batches
To create a great number of fibers between an OTU board and a Mux/Demux board, you can
connect fibers in batches to improve the efficiency.
Prerequisite
l All OTU boards on a station must be configured with different wavelengths.
l The source end supports only the Mux/Demux board and add/drop multiplexing board.
l Creating intra-subrack fibers in batches is not supported.
Procedure
displayed.
Step 2 Choose Link > Fiber/Cable from the Object Tree.
Step 3 Set Create Ways as batch ways.
Step 4 Select the source Slot Diagram and the corresponding ONE. Select the sink OTU Physical
Subrack and the corresponding ONE.
Step 5 Click OK.
----End
5.7.8 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 T2000. In this way, you can monitor the actual
working state of each radio link.

Prerequisite
l The IF board for each NE must be created on the T2000.
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
Step 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 for ports of created fibers on T2000 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.
Step 3 After the search is complete, a dialog box is displayed, telling that the operation was successful.
Click Close.
Step 4 In the Newly Searched Fiber list, select one or multiple radio links. Click Create Fiber/
Cable.
NOTE
l When you select one or multiple radio links in the Newly Searched Fiber list, the radio links that
conflict with the selected ones are automatically displayed in the Existing Conflicting Fiber 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.
Step 5 In the Existing Conflicting Fiber list, select one or multiple conflicting radio links (the Conflict
with logical link (Y/N) value of which in the Misconnected Fiber 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.7.9 Manually Creating Radio Links

After you manually fill in the table, the T2000 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 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
Step 1 Click the shortcut icon on the toolbar of the Main Topology and the cursor changes to a
+ sign.
Step 2 Click the source NE of the radio link on the Main Topology.
Step 3 Select the source board and port in the Select the source end of the link dialog box.
Step 5 Click the sink NE of the radio link on the Main Topology.
Step 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.
Step 7 Click OK. Enter the information of the fiber or cable in the Create Microwave Link dialog
box.
Step 8 Click OK. The created radio link appears between the source and sink NEs on the Main
Topology.
----End
5.7.10 Creating DCN Communication Cable

The T2000 can communicate with NEs through the Ethernet port or serial port. The NEs also
communicate with each other through the extended ECC. Depending on the communication
mode, different types of cables can be created on the T2000.

Prerequisite
You must be an NM user with "NM operator" authority or higher.
Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > Link from the shortcut
menu.
Step 2 Select a cable type from the expanded items.
Step 3 Enter the cable attributes in the right-hand pane.
Step 4 Click OK. The cable is displayed on the Main Topology between the T2000 and the GNE.
----End
Postrequisite
If the NEs at the two ends of the DCN 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.7.11 Creating Virtual Fibers

When the T2000 manages the SDH, PTN and WDM equipment at the same time, you can create
virtual fibers for SDH or PTN equipment with WDM equipment in between, to facilitate
administration.
Prerequisite
l You must create fiber connections according to the true fibers that connect the SDH and
WDM equipment.
l You must create fiber connections according to the true fibers that connect the PTN and
WDM equipment.
l The T2000 must manage the SDH, PTN and WDM equipment at the same time.
Context
l For SDH equipment, the virtual fibers ensure the independence of automatic fiber search
and SDH trail management. .
l For WDM equipment, 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 equipment.
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 equipment.
l The virtual fiber does not support the expansion function.

Procedure
Step 1 Right-click in the blank space of the Main Topology, and choose New > Link from the shortcut
menu.
Step 2 In the Add Object dialog box, choose Link > Virtual Fiber/Cable .
Step 3 Set the attributes of the fiber or cable in the right-hand list.
Step 4 Click OK.
----End
5.7.12 Restoring the Fiber Connection

Due to misoperations or other causes, the fiber connection is deleted on the T2000. This does
not affect the service transport, but you need to restore the fiber connection quickly, to restore
the monitoring on the T2000.
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 T2000. For details, see 5.7.1
Creating Fibers Automatically.
Procedure
Step 1 Choose System > Browse Log from the Main Menu.
Step 2 In the Navigation Tree on the left, select Operation Logs.
Step 3 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.
Step 4 In Details, view the information of the source and sink.
Step 5 According to the information of the source and sink, create the fiber again.
NOTE
For the details of creating fibers, see 5.7 Creating Links.
----End
5.7.13 Creating a Fiber/Cable Pipe

To manage certain fibers/cables as a pipe, you need to create a fiber/cable pipe.
Prerequisite
You must be an NM user with "network operator" authority or higher.

Procedure
Step 1 Choose File > Fiber/Cable Pipe Management from the Main Menu.
Step 2 Click Create. In the Add Pipe window that is displayed, set Name, Memo, and Builder for the
fiber/cable pipe. Click OK.
Step 3 Optional: After you create a fiber/cable pipe, you can view the information about the new fiber/
cable pipe in the Pipe Information pane.
----End
5.7.14 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.
Prerequisite
l You must be an NM user with "network operator" authority or higher.
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
Step 2 In the pipe list, select the fiber/cable pipe that you want to add the fiber/cable into and then click
Add Fiber/Cable.
Step 3 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.
Step 4 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 Filter Pipe window that is displayed, set the filter criteria and then click Filter.
Step 5 In the operation result dialog box displayed, click Close.
Step 6 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/Cable Information pane.
Step 7 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 T2000 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
5.8 Browsing Fiber/Cable

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.8.1 Querying Fiber/Cable Information

On the T2000, you can view detailed information about a fiber/cable to learn its current status.
5.8.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.8.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.8.4 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.
5.8.5 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.
5.8.6 Querying the Physical Fiber Connection Between NEs
After physical fibers are connected between NEs, you need to manually create corresponding
fibers on the T2000 for management. If fibers are incorrectly created on the T2000, the fibers
on the T2000 are inconsistent with the physical fibers. At this time, you need to query the physical
fiber connections between NEs.
5.8.1 Querying Fiber/Cable Information

On the T2000, you can view detailed information about a fiber/cable to learn its current status.
Prerequisite
Procedure
The information of all fiber/cable is displayed in the pane on the right.
Step 2 Optional: In the Object Tree on the left, select the object about which you want to view the
relevant fiber/cable information, and click the object.
The detailed information of the fiber/cable is displayed in the pane on the right.
Step 3 Optional: Click Print. After setting the range in the window displayed, you can set parameter
for the printing in the Print dialog box.
Step 4 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 .txt, .html, or .csv file.
----End
5.8.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
Procedure
The information about all fiber/cables is displayed in the pane on the right.
Step 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.

Step 3 Optional: Click Print. After setting the range in the window displayed, you can set parameter
for the printing in the Print dialog box.
Step 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 .txt, .html, or .csv file.
----End
5.8.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
Procedure
Step 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.
Step 2 Click the Table tab.
Step 3 Click Query.

The input and output optical power of the fiber/cable is displayed. The Operation Result
window is displayed.
Step 4 Click Close.
Step 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.8.4 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 You must be an NM user with "network monitor" authority or higher.
l A fiber/cable pipe must be created.
Procedure

Step 2 In the Pipe Information pane, you can view the information about all fiber/cable pipes.
Step 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
5.8.5 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
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.
Procedure
Step 2 In the Fiber/Cable Information pane, right-click a fiber/cable, and then choose Query Fiber/
Cable Pipe from the shortcut menu.
Step 3 In the Pipe Information pane, the information about all the pipes to which the fiber/cable
belongs are displayed.
----End
5.8.6 Querying the Physical Fiber Connection Between NEs

After physical fibers are connected between NEs, you need to manually create corresponding
fibers on the T2000 for management. If fibers are incorrectly created on the T2000, the fibers

on the T2000 are inconsistent with the physical fibers. At this time, you need to query the physical
fiber connections between NEs.
Prerequisite
l NEs cannot be ASON NEs, because physical fiber connections between ASON NEs cannot
be queried.
l The NEs to be queried cannot have the J0_MM alarms.
Context
You can modify the J0 byte of an optical interface to check whether the optical interface reports
the J0_MM alarm. In this way, you can query the physical fiber connections between NEs.
Procedure
Step 2 In the left pane select some ports from one or more NEs and unchecked the Do not search for
ports of created fibers on T2000 check box, click Search to search for the fibers or cables. A
progress bar is displayed showing the progress of the search.
Step 3 A prompt is displayed indicating that the operation is successful. Click Close.
NOTE
If fibers are connected properly, the Operation Result dialog box is displayed, indicating that the fibers
on the T2000 are consistent with the physical fibers between NEs.
Step 4 If fibers are connected improperly, in the Main Topology, you can locate the NEs that are
displayed in the Misconnected Fiber area. Then, navigate to the NE Explorers of the source
NE.
Step 5 In the NE Explorer, select the source board of the improperly connected fiber and then choose
Configuration > Overhead Management from the Function Tree. You can view the J0 byte
information of the board.
Step 6 You can modify the J0 byte of the optical interface of this board and then query the optical
interface of the opposite NE that reports the J0_MM alarm. In this way, you can query the
physical fiber connection between the two NEs and quickly modify the fiber information on the
T2000.
----End
5.9 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
Step 1 Right-click in the blank space of the Main Topology and choose New > Subnet from the shortcut
menu.
Step 2 Click the Properties tab in the Add Object dialog box. Enter the attributes of the subnet.
Step 3 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane.
Click .
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.
Step 4 Click OK. Click in the blank space of the Main Topology, the icon appears in the position
where you clicked.
----End
5.10 Adjusting Topology Objects

You can modify the settings when creating the network topology by using the T2000. For
example, adjust the optical NE source, 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
The ECC protocol uses the NE ID as the unique identifier of an NE. Hence, 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 causes an ECC route conflict and the T2000 cannot manage certain NEs. During the
commissioning or expansion process, when you need to adjust the original network planning
and change NE IDs, you can use the T2000 to change NE IDs.
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 Address
Incorrect settings of the IP address may affect the communication between the T2000 and an
NE and the communication 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 change the optical NE name at any time as required with no effect on the running of
the 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 T2000 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
T2000.
5.10.9 Modifying the Port Type for a Board
The T2000 helps you to modify the port type for a board without interrupting the services on
other ports on the same board. This facilitates network management and maintenance.
5.10.10 Modifying the Client-Side Port Type
The client-side port of the OTU board can be a color port or a colorless port. Set the port type
based on the small form-factor pluggable (SFP) optical module used in the equipment.
5.10.11 Modifying the Type of a Line-Side Port
Line-side (WDM-side) ports of the OTU board support colored light and colorless light. You
need to set the different port type according to the specifications of the small form-factor
pluggable (SFP) optical module used on the equipment.
5.10.12 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.13 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.

5.10.14 Removing a Fiber/Cable from a Fiber/Cable Pipe

To use the function of platinum services, you need to perform the fiber/cable pipe management.
You can remove a fiber/cable from a fiber/cable pipe during fiber/cable pipe management.
5.10.15 Naming a Fiber/Cable
In the network management, you need to strictly plan the fiber names, to ensure that faults can
be fast located during maintenance and troubleshooting. On the T2000, you can use the preset
naming rules to name the fiber/cable.
5.10.16 Copying Topology Objects
In the current topology view, you can copy a topology object from one subnet to another.
5.10.17 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 deployment tool server is started.
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
Step 1 Choose System > NE Deploy Management from the Main Menu. The NE Deploy
Management window is displayed.
Step 2 In the left-hand pane, select an NE Explorer instance, and click Migrate NE. The Migrate
NE dialog box is displayed.
Step 3 In Sink NE Explorer, select the new NE Explorer instance.
Step 4 In the left-hand pane, select an NE that you want to move to the Sink NE Explorer, and click
. The NE is displayed in the right-hand pane.

NOTE
You can repeat Step 4 to move multiple NEs.
Step 5 Optional: In the right-hand pane, select an NE that you want to move to the Source NE
Explorer, and click . The NE is displayed in the left-hand pane.

NOTE
You can repeat Step 5 to move multiple NEs.

Step 6 Click OK. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 7 Click Close.
----End
5.10.2 Modifying the NE ID

The ECC protocol uses the NE ID as the unique identifier of an NE. Hence, 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 causes an ECC route conflict and the T2000 cannot manage certain NEs. During the
commissioning or expansion process, when you need to adjust the original network planning
and change NE IDs, you can use the T2000 to change NE IDs.
Prerequisite
l The NE must be created.
In the case of the equipment whose NE ID is set by DIP switch, T2000 supports the in-service
modification of the NE ID, but the new NE ID is not applied to the NE. You only need to set
the DIP switch to modify the NE ID manually on site. In this way, the T2000 can monitor the
NE again without recreating the NE and its network-layer data.

Precautions
CAUTION
l Inter-subrack wavelength protection.
l IPA function at the local NE and IPA functions of other NEs that involving the Raman board
of the local NE.
l ALC function.
l Fiber connections of the local NE and fiber connections of other NEs that involving the local
NE.
l APE/EAPE function of the local NE and APE/EAPE functions of other NEs that involving
the board of the local NE.
l Logical wavelength group where the OTU board of the local NE is located.
Before modifying the NE ID, delete the following configurations and reconfigure the following
items after the NE ID is modified:
l Inter-subrack wavelength protection.
l IPA function at the local NE and IPA functions of other NEs that involving the Raman board
of the local NE.
NE.
l APE/EAPE function of the local NE and APE/EAPE functions of other NEs that involving
the board of the local NE.
l Logical wavelength group where the OTU board of the local NE is located.
Before modifying the NE ID, delete the following configurations and reconfigure the following
items after the NE ID is modified:
l All protection groups at the local NE.
NE.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
Step 3 Enter the New ID and the New Extended ID. Click OK.
Step 4 Click OK in the Warning dialog box.
----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
Step 1 In the NE Explorer, click the NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 In the NE Attribute dialog box, enter a new NE name in Name. Click Apply. A prompt is
displayed indicating that the operation is successful.
NOTE
An NE name consists of up to 64 characters, including letters, symbols, and numerals, except the following
special characters | : * ? " < >.
Step 3 Click Close.
----End
5.10.4 Modifying the NE IP Address

Incorrect settings of the IP address may affect the communication between the T2000 and an
NE and the communication between NEs. You can rectify the fault of this type by modifying
the IP address of the NE.
Prerequisite
Precautions
CAUTION
After you change the IP address, if the IP address of the NE and the IP address of the T2000
server are in the same network segment, the communication between the T2000 and the NE
remains normal. In this case, re-log in to the NE.
If the IP address of the NE and the IP address of the T2000 server are in different network
segments, the communication between the T2000 and the NE is interrupted. In this case, set a
new IP address for the computer where T2000 server is installed to restore the communication.
Ensure that this new IP address and the NE IP address are in the same network segment. Because
of the restriction of the SQL database, after you have changed the IP address of the computer,
you must shut down the T2000 client and server, restart the computer and then the T2000 client
and server.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication
Parameters from the Function Tree.
Step 2 Set the communication parameters of the NE, including the IP address, extended IP address,
gateway NE IP address, and subnet mask.

Step 3 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 change the optical NE name at any time as required with no effect on the running of
the NE.
Prerequisite
Procedure
Step 1 Right-click an optical NE on the Main Topology and choose Attribute from the shortcut menu.
The NE Attribute dialog box is displayed.
Step 2 Enter the new optical NE name and click OK.

NOTE
An Optical NE name can contain a maximum of 64 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
Step 1 Right-click an optical NE and choose Attribute from the shortcut menu. The NE Attribute
dialog box is displayed.
Step 2 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.
Step 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.
Step 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 T2000 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 equipment.
Context
CAUTION
Downloading data of a preconfigured NE applies the NE settings on the T2000 to the physical
NE. If the data is incorrect, this may cause service interruption.
Procedure
Step 1 Choose Configuration > Configuration Data Management from the Main Menu. The
Configuration Data Management dialog box is displayed.
Step 2 In the left-hand pane, select NEs and click .
Step 3 Select all preconfigured NEs that you want to modify, right-click on the NE
Preconfiguration and choose No from the shortcut menu.
Step 4 Click Apply. A prompt appears asking you whether to download immediately. Click Yes. A
prompt appears telling you that the operation may affect the service.
Step 5 Click OK. A prompt appears telling you that the operation may affect the service.
Step 6 Click OK. A progress bar is displayed.
Step 7 After the download is complete, a prompt appears telling you that the operation is successful.
Click Close.
----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
T2000.
Prerequisite

Procedure
Step 1 Right-click the NM icon on the Main Topology and choose Attribute from the shortcut menu.
Step 2 In the NM Attribute dialog box, enter a new NM name. Click OK.
NOTE
The NM name can contain alphanumeric characters and symbols, but cannot contain the following special
characters: | : * ? " < >.
----End
5.10.9 Modifying the Port Type for a Board

The T2000 helps you to modify the port type for a board without interrupting the services on
other ports on the same board. This facilitates network management and maintenance.
Prerequisite
l Applies to the N1SLQ1, N1SL1 and OU08 boards.
l The interface module on the board must be changed.
Context
CAUTION
Modifying the board port type interrupts all services on the port.
Procedure
Step 1 Double-click an NE on the Main Topology and the NE Panel is displayed.
Step 2 Right-click the board for which you want to modify the port type and choose Modify Port from
the shortcut menu. The Modify Port Level dialog box is displayed.
Step 3 Modify the port type.

Step 4 Click OK. The Confirm dialog box is displayed. Click OK.
----End
5.10.10 Modifying the Client-Side Port Type

The client-side port of the OTU board can be a color port or a colorless port. Set the port type
based on the small form-factor pluggable (SFP) optical module used in the equipment.
Prerequisite
When adding a port, ensure that the port is not fully configured. (The port is fully configured by
default. Before you add a port, delete certain ports to ensure that the port to be added is not
configured.)
Context
The following equipment is supported: OptiX OSN 8800 I, OptiX OSN 6800, OptiX OSN 3800,
OptiX OSN 6800A, and OptiX OSN 3800A.
During the creation of OTU boards, the client-side port is added by default. The port type is the
client-side colorless optical port by default.
The LSXR and LSXL/LSXLR boards do not support this function.
Procedure
Step 1 Double-click the ONE on the Main Topology, select the NE to open the NE Panel.
Step 2 Right-click the board where the client-side port need be modified, and choose Path View from
the shortcut menu.
Step 3 Right-click the port for which you want to modify the port type and choose Modify Port from
the shortcut menu. The Modify Port dialog box is displayed. Set Type and click OK to apply
the configuration.

NOTE
If you need to modify Type to Line Side Color Optical Port, you must first delete the port, and then add
the port. Otherwise the port cannot be modified successfully.
Step 4 Optional: In Path View, right-click the desired client-side port, and click Delete Port. Then,
the client-side ports are updated.
Step 5 Optional: In Path View, right-click a blank space and select Add Port. In the Add Port dialog
box displayed, set the Type of the port. Click OK to apply the configuration.
----End
5.10.11 Modifying the Type of a Line-Side Port

Line-side (WDM-side) ports of the OTU board support colored light and colorless light. You
need to set the different port type according to the specifications of the small form-factor
pluggable (SFP) optical module used on the equipment.
Prerequisite
The following types of equipment are supported: OptiX OSN 8800 I, OptiX OSN 6800, OptiX
OSN 3800, OptiX OSN 6800A, and OptiX OSN 3800A.
The OTU board must be applicable to the equipment.
When the OTU board is created, the line-side (WDM-side) ports are added to the board by
default. The default port type is line-side (WDM-side) colored optical interface.
The following OTU boards are supported: 12LDX, 12TMX, 12LOG, 12LOM, 12TQS, 11TOG,
12NQ2, and 12ND2.
Procedure
Step 1 Double-click the ONE on the Main Topology, select the NE and open the NE Pannel.
Step 2 Right-click the board for which you want to change line-side (WDM-side) ports and choose
Path View from the shortcut menu.
Step 3 Right-click the port for which you want to modify the port type and choose Modify Port from
the shortcut menu. The Modify Port dialog box is displayed. Set Type and click OK to apply
the configuration.

Step 4 Optional: In Path View, right-click the line-side (WDM-side) ports that you want to delete,
and click Delete Port. The line-side (WDM-side) ports are deleted.
Step 5 Optional: In Path View, right-click a blank space and select Add Port. In the Add Port dialog
box displayed, set Type. Click OK to apply the configuration.
----End
5.10.12 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
Procedure
Step 1 Choose File > Fiber/Cable Management from the Main Menu. The information of all fiber/
cable is displayed in the pane on the right.
Step 2 Modifying the fiber/cable information.

l In the Name column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu. 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.
l In the Length(km) column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu. 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.
l Modify the attenuation of a fiber.
1. In the Attenuation column, right-click the value for a fiber and choose Modify Fiber/
Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box, enter the actual loss and click OK. Click
Close in the Operation Result dialog box.
l Modify the type of the fiber.

1. In the Type column, right-click the value for a fiber and choose Modify Fiber/
Cable from the shortcut menu.
2. In the Modify Fiber/Cable dialog box displayed, select the actual type of the fiber
from the drop-down list and click OK. Click Close in the Operation Result dialog
box.
----End
5.10.13 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
Step 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.
Step 3 After the modifications, click Apply.
Step 4 In the Operation Result dialog box that is displayed, click Close.
----End
5.10.14 Removing a Fiber/Cable from a Fiber/Cable Pipe

To use the function of platinum services, you need to perform the fiber/cable pipe management.
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
Step 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.
Step 3 In the Fiber/Cable Information list, select the fiber/cable to be removed and then click Move
Fiber/Cable.
click Close.

NOTE

----End
5.10.15 Naming a Fiber/Cable

In the network management, you need to strictly plan the fiber names, to ensure that faults can
be fast located during maintenance and troubleshooting. On the T2000, you can use the preset
naming rules to name the fiber/cable.
Prerequisite
Procedure
The information of all fiber/cable is displayed in the pane on the right.
Step 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.16 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 device or subnet to the destination subnet.
l You can press and hold Shift to select two or more objects. You can copy and paste multiple
objects at a time.
Procedure
Step 1 In the topology view, go to the source subnet of the object that you want to copy. Click the
object.
Step 2 Choose Edit > Copy to copy the object to the clipboard.
Step 3 Go to the destination subnet, choose Paste to paste the object in the subnet.
----End

5.10.17 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
Step 1 In the topology view, go to the source subnet of the object that you want to move. Click the
object.
Step 2 Choose Edit > Cut to copy the object to the clipboard.
Step 3 Go to the destination subnet, choose Paste to paste the object in the subnet.
----End
5.11 Deleting Topology Objects

When adjusting the network topology, generally, you need to delete some objects of the topology.
5.11.1 Deleting Topology Subnets

When adjusting the topological structure of the network, you can delete a subnet from the Main
Topology if the subnet is not needed.
5.11.2 Deleting Boards
To modify the network configuration or the NE configuration, you may need to delete the boards
from the NE Panel.
5.11.3 Deleting Sub-boards
Before adding a new sub-board, you need to delete the sub-boards that are already added.
5.11.4 Deleting Fibers
When adjusting the network if you need to delete the NEs or change the links between NEs, you
need to delete the fiber connections between the NEs.
5.11.5 Deleting a Fiber/Cable Pipe
You can delete the fiber/cable pipe that is no longer required.
5.11.6 Deleting NEs
If you have created a wrong NE, you can delete the NE from the T2000. Deleting an NE removes
all information of the NE from the T2000 but does not affect the running of the equipment.
5.11.7 Deleting an Optical NE
You can delete an optical NE.

5.11.1 Deleting Topology Subnets

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
Step 1 Right-click the subnet on the Main Topology, and choose the Delete shortcut menu.
Step 2 Click Yes to delete the subnet.
Step 3 Click Close in the Delete Object Results dialog box.
----End
5.11.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 The fibers, trails, services and protection groups must be deleted.
Procedure
Step 1 Open the NE Panel.
For the SDH equipment, double-click the icon of the NE on the Main Topology.
For the PTN equipment, double-click the icon of the NE on the Main Topology.
For the RTN equipment, double-click the icon of the NE on the Main Topology.
For the WDM equipment, double-click the icon of the optical NE on the Main Topology. In the
left pane of the NE Panel, select the NE from which you want to delete the board.
Step 2 Right-click the board you want to delete and choose Delete from the shortcut menu.
NOTE
Certain boards, such as PIUAUX boards, cannot be deleted. The boards that can be deleted vary with
different types of equipment. For details, see the Hardware Description of each type of the equipment.
When you delete the board, the inactive single-station optical cross-connections are also deleted.
Step 3 Click OK in the Delete Board dialog box.

Step 4 Click OK to delete the board.
----End
5.11.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 connected to the sub-board, and make sure that
the sub-board is in the idle state.
Procedure
Step 1 Double-click an NE on the Main Topology and the NE Panel is displayed in the user interface.
Step 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.11.4 Deleting Fibers

When adjusting the network if you need to delete the NEs or change the links between NEs, you
need to delete the fiber connections between the NEs.
Prerequisite
Procedure
Step 2 Select the fiber 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.
Step 3 Click Close in the Operation Result dialog box.
----End
5.11.5 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
Step 2 In the pipe information list, select the fiber/cable pipe to be deleted and then click Delete.
click Close.
NOTE

----End
5.11.6 Deleting NEs

If you have created a wrong NE, you can delete the NE from the T2000. Deleting an NE removes
all information of the NE from the T2000 but does not affect the running of the equipment.
Prerequisite

Context
When the NE is not logged in, you can delete the NE on the T2000.
CAUTION
If an NE is deleted, the links related to the NE are also deleted.
When a GNE is deleted, if no standby GNE is provided for the NEs that were originally managed
by the deleted GNE, the communication between those NEs and the T2000 is interrupted.
Procedure
l Delete a single SDH,PTN or RTN NE.
1. Right-click the NE on the Main Topology and choose Delete > Delete Device from
the shortcut menu. The Confirm dialog box is displayed.
2. Click Yes. The NE icon is deleted from the Main Topology.
l Delete a single WDM NE.
1. Double-click an optical NE on the Main Topology. Right-click the NE in the left pane
and choose Delete from the shortcut menu.
2. Click OK.
l Delete NEs in batches.
The Configuration Data Management window is displayed.
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.
----End
5.11.7 Deleting an Optical NE

You can delete an optical NE.
Prerequisite
Procedure
Step 1 Right-click an optical NE on the Main Topology and choose Delete > Delete Device from the
shortcut menu. The Confirm dialog box is displayed.
Step 2 Click Yes. The optical NE is deleted from the Main Topology.

NOTE
All the NEs that are associated to this optical NE are moved to the Idle ONE.
----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 T2000 and on NEs for easier network maintenance.
6.1 Time Localization

Time localization ensures that the time on the T2000 is correctly displayed when the T2000
crosses time zones and Daylight Saving Time (DST).
6.2 Setting Time Localization on the T2000
By setting time localization, you can set the time localization mode by using the T2000. This
ensures that the NE data that is displayed is based on the standard time on the T2000.
6.3 Setting Time Localization on NEs
You can set time localization on NEs to ensure the consistent time displayed on NEs and the
T2000.

6 Time Localization Management Operation Guide for Common Features
6.1 Time Localization

Time localization ensures that the time on the T2000 is correctly displayed when the T2000
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 T2000 and NEs are stored based on the UTC. The time on the T2000 client is
displayed in two modes, which are by client local time, and by server local time. The local time
displayed on the T2000 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.
In the time localization policy, if you select the local time of the NE as the standard time, the
T2000 needs to transit the display time of the NE by converting UTC to the local time of the
time zone where the NE is located.
Daylight Saving Time

DST also known as summer time, is a widely used system of time. During the "longer" days of
spring and summer, DST saves energy and fully uses the daylight. Some countries pass
legislation to set the clock forward one hour in the spring and revert the clock by one hour in
the winter.
The time when data is generated in the T2000, is irrelevant to DST. But, when the T2000 transits
the display of history data, the T2000 may need to implement DST transition for some regions.
For example, the T2000 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 T2000

By setting time localization, you can set the time localization mode by using the T2000. This
ensures that the NE data that is displayed is based on the standard time on the T2000.
1. 6.2.1 Setting the Time Display Format

The T2000 provides different time display formats to meet the requirement of users in
different regions.
2. 6.2.2 Setting the Time Localization Mode
Alarms are stored in the T2000 based on UTC. The T2000 provides different time
localization modes so that the display time of the alarms that the server receives at the same
time is the same.

6.2.1 Setting the Time Display Format

The T2000 provides different time display formats to meet the requirement of users in different
regions.
Prerequisite
Procedure
Step 1 Choose File > Preferences from the Main Menu. Click the Time tab.
Step 2 Select the desired option from the Time Format drop-down list.
Step 3 Click Apply.
Step 4 Click OK.
----End
6.2.2 Setting the Time Localization Mode

Alarms are stored in the T2000 based on UTC. The T2000 provides different time localization
modes so that the display time of the alarms that the server receives at the same time is the same.
Prerequisite
Procedure
Step 1 Choose File > Preferences from the Main Menu. Click the Time Mode tab.
Step 2 In the Time Localization Mode area, select the desired mode.
NOTE
l Use client local time: The local time of the T2000 client is the standard time displayed on the user
interface.
l Use server local time: The local time of the T2000 server is the standard time displayed on the user
interface.
Step 3 Click Apply.

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

6 Time Localization Management Operation Guide for Common Features
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 T2000 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
Applies to the OptiX OSN 1500, OptiX OSN 2500, OptiX OSN 3500, OptiX OSN 7500 and
Metro 1000.
Procedure
Step 1 Choose System > NE Time Localization Management from the Main Menu.
Step 3 Click Query to query the time zone for an NE.
Step 4 Double-click TimeZone and select a time zone from the drop-down list.
NOTE
l You can modify the NE time zone setting for many times according to the actual situation.
l The old time data in the NE may be incorrect. Hence, the correctness of the time displayed in the NE
cannot be guaranteed after the NE time zone is changed.
----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 T2000 can be correctly transited.

Prerequisite
Applies to the OptiX OSN 1500, OptiX OSN 2500, OptiX OSN 3500, OptiX OSN 7500 and
Metro 1000.
Procedure
Step 1 Choose System > NE Time Localization Management from the Main Menu.
Step 3 Click Query to query the time zone for an NE.
Step 4 Double-click DST and select Enabled from the drop-down list.
Step 5 Set the DST attributes, including DST Rule, DST Offset, Start Time and Stop Time.
----End

Operation Guide for Common Features 7 Alarm Management
7 Alarm Management
About This Chapter
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.2 Customizing Alarm Template
The T2000 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.3 Synchronizing Alarms
You can synchronize the current alarms of the NE and the T2000. This feature ensures that the
alarms on the NEs are synchronous with the alarms on the T2000, and that the current NM alarms
are synchronous with the alarms in the T2000 alarm database.
7.4 Viewing Alarms
The network maintenance personnel can view alarms to know the network status.
7.5 Handling an Alarm
When an alarm is raised, you need to take actions to handle it. You need to rectify the network
fault or the device fault to recover the network or device to its normal state.
7.6 Setting the Alarm Auto Processing
You can set an auto processing policy to enable the T2000 to process the alarms that match the
preset conditions. This helps to improve the work efficiency.
7.7 Suppressing Alarms
You can suppress alarms, so that the T2000 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.8 Setting Alarm Reversion

7 Alarm Management Operation Guide for Common Features
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.9 Filtering Alarms Raised on T2000
You can filter unimportant T2000 alarms so that the T2000 does not monitor these alarms. This
operation helps fault location.
7.10 Filtering Alarms Raised on NE
After an NE reports an alarm to the T2000, the T2000 determines whether to display and save
the alarm according to the alarm filtering status. You can use this function to filter out the
negligible alarms when the T2000 manages multiple NEs.
7.11 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 T2000. You can disable the automatic reporting for unimportant
alarms to reduce the impact on the T2000 performance. A large volume of alarm information
affects the performance of the T2000.
7.12 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.13 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.14 Setting the Insertion Mode for Channels Not Configured with Services
On the T2000, you can set the insertion mode of alarms in the channel according to the
networking and service requirements.
7.15 Setting Audible and Visual Alarm Notification
The T2000 can select different sounds and colors for the alarms and abnormal events of different
severities based on customized settings, to facilitate maintenance.
7.16 Setting Alarm Remote Notification
This function helps the maintenance engineer to learn the running status of the network at any
time. When the T2000 detects that an relevant alarm is raised, the alarm remote notification
function enables the T2000 to automatically send the alarm information to the preset receive
terminal. Currently, the T2000 can only forward the alarm information to users by way of short
message and EMAIL.
7.17 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.18 Analyzing the Root Alarm of a Fault
Due to the hierarchical relation of the service signals, normally, when alarms occur on a higher
order signal, some derived alarms occur on the lower order signals that are demultiplexed from
higher order signals. As for the WDM trails, some alarms raised from the upstream equipment
can generate some other alarms on downstream equipment. The T2000 can analyze the alarm
events. It displays or reports the most critical root alarms, and suppresses the alarms derived
from the root alarms according to the alarm correlation. The T2000 supports both the alarm
correlation analysis and the automatic alarm correlation analysis when analyzing the root alarms.
7.19 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.20 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.21 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.22 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.23 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.24 Dumping Alarms
The alarm data should be dumped in time to avoid overflow of alarm data or damage. You can
either manually dump the alarm data or set the alarm dumping conditions so that the T2000
automatically dumps the data. There are two types of automatic dumping, which are overflow-
triggered dumping and scheduled dumping.
7.25 Deleting History Alarms
Deleting history alarms is to dump the history alarms from the database and save them as a file.
The deleted alarms are not displayed in the History Alarms window. For details, see 7.24.1
Dumping Alarms Manually.
7.26 Diagnosing Faults
The T2000 provides a wizard for fault diagnosis. In daily maintenance, the engineer can create
fault diagnosis rules. When an alarm is generated, the engineer can locate the fault by using the
fault diagnosis wizard.
7.27 Configuring the Suppression of Power Status Alarm
During the operation, if the cabinet is not configured with three subracks or if the two power
supplies are not accessed completely, the corresponding tributary power reports the power status
alarm. If you are sure that the current configuration is correct, suppress the power status alarm.

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 Alarm Reporting Process

The alarm reporting process starts with the detection of the alarm on a board, and ends with the
T2000 notifying the alarm to a user. The alarm reporting process is instructive in guiding a user
to handle alarms.
7.1.2 Alarm Handling Procedure
This section describes the alarm handling procedure. If an alarm is detected by the T2000, it is
recommended to handle the alarm according to the alarm handling procedure.
7.1.3 Alarm template
The alarm template simplifies the operations of setting alarms. With the alarm template, you can
quickly set the alarm browsing and alarm attributes.
7.1.4 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 T2000, network equipment, trails and
services. Meanwhile, you can synchronize, check and acknowledge these alarms.
7.1.5 Alarm Setting Operations
Alarm setting operations include a series of alarm management operations, such as setting the
alarm suppression, automatic alarm reporting and alarm reversion. You can set the alarm
attributes as required in favor of the alarm management.
7.1.6 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 T2000 alarm correlation.
7.1.7 Alarm Notification
To get informed of the alarm information is critical to handling alarms and to the network
maintenance. The T2000 provides various ways of notifying alarms.
7.1.8 Alarm Severity
Alarm severity is used to identify the severity level, significance and urgency of an alarm. Alarms
come in the following four levels in descending order of severity: critical, major, minor and
warning.
7.1.9 Alarm Status
Alarms can be categorized according to their status based on whether they are acknowledged or
cleared. A network operator can take different measures to handle alarms according to the status,
severity level and causes of the alarms.
7.1.10 Alarm Category
The alarms can be categorized according to the generating location and the T2000 standards and
functions.
7.1.11 Current Alarms and History Alarms

Current alarms and history alarms have the following four types: current NE alarms, history NE
alarms, current T2000 alarms and history T2000 alarms. The T2000 alarm includes the alarms
reported from NEs and the alarms generated by the T2000 itself.
7.1.12 Alarm Statistics
The alarm statistics are displayed in the tabular format according to the user-defined conditions.
This helps you to analyze the running status of the equipment.
7.1.13 Alarm Dumping
When the history alarm data in the T2000 database exceeds a certain amount, the T2000
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 T2000 database to a specified directory as
a file. In this way, the T2000 performance is improved.
7.1.1 Alarm Reporting Process

The alarm reporting process starts with the detection of the alarm on a board, and ends with the
T2000 notifying the alarm to a user. The alarm reporting process is instructive in guiding a user
to handle alarms.
Figure 7-1 shows the activities performed to report an alarm.

Figure 7-1 Alarm reporting flow chart

Alarm is detected by board,
Save the alarm to the board
alarm library
Set alarm Yes The alarm is suppressed.

suppression? Stop monitoring this alarm.
No
Process the alarm according

to the specified alarm
reversion mode
Save the alarm to the SCC

alarm library
Yes Process alarm

synchronization?
No
No The alarm is not reported,

Alarm automatic reporting but the board keeps
monitoring the alarm.
Yes
Set equipment Yes

Discard the alarm data
alarm filter?
No
The EMS detects the EMS
Save the alarm data to the alarm, and saves it to the
EMS server EMS server.
Alarm
correlation analysis Yes
Set EMS alarm filter?
No
Display the alarm on the

client
Set alarm No
notification?
Yes
Send alarm data to the

receive end
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 T2000 according to the settings of the alarm automatic reporting. After the T2000 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 T2000 again. This scheme
ensures the reliability of the alarm reporting.
If the communication between the T2000 and the NE is interrupted, when the T2000 is restarted,
it automatically synchronizes the alarm library of the SCC to keep the alarm data on the
T2000 synchronous with the alarm data on NE.
T2000 Alarm Notification

Based on the user-defined alarm filter criteria, the T2000 decides whether to discard the alarm
reported from an NE. As for the alarms saved in the T2000 database, the T2000 analyzes them
according to the alarm correlation rules. Then it presents the analysis result on the T2000 client
and notifies the information to the user.
7.1.2 Alarm Handling Procedure

This section describes the alarm handling procedure. If an alarm is detected by the T2000, it is
recommended to handle the alarm according to the alarm handling procedure.
Flow Chart
Figure 7-2 shows the alarm handling procedure.

Figure 7-2 alarm handling procedure
Start
Receive an alarm
View the alarm details
Acknowledge the alarm
Collect fault information Information

collection
Analyze the causes of the

fault
Work out the fault handling Fault

scheme location
Carry out the fault handling

scheme
Fault
removal
Clear the alarm
No Check whether the

fault is removed?
Ye
s
Record the maintenance
experience
End

Procedure
The alarm handling procedure, as shown in Figure 7-2, is described inTable 7-1.
Table 7-1 alarm handling procedure
Step Operation Description
1 Receive an alarm When receiving an alarm, the administrator starts the alarm
handling procedure. To ensure that the operators can receive
notifications in time when a fault occurs, you need to set
alarm notification methods on the T2000.
2 View the alarm details This is where you start. View the alarm details, including
the alarm location information, alarm help, and alarm
maintenance experience.
3 Acknowledge the To avoid others handling the same alarm, you need to
alarm acknowledge it. When you acknowledge an alarm, it
indicates that the alarm is being processed.
4 Collect fault By locating an alarm, you can query the fault information
information and analyze the causes of the fault.
5 Analyze the causes of Analyze the causes of the fault according to the fault
the fault information.
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 remove the fault.
handling scheme
8 Clear the alarm When the fault is removed, the alarm is cleared, and the
T2000 receives the cleared alarm.
9 Check the handling After the fault is removed, check the handling results.
results
10 Record the After you complete the fault handling, record the
maintenance maintenance experience.
experience
7.1.3 Alarm template

The alarm template simplifies the operations of setting alarms. With the alarm template, you can
quickly set the alarm browsing and alarm attributes.
The alarm template is divided into two types: alarm browsing template and alarm attribute
template.

l Alarm browsing templates include the current alarm browsing template, the history alarm
browsing template, the event browsing template, and the alarm statistics template. Alarm
browsing templates combine a group of filter conditions that are used to browse the alarm
information or alarm statistics. Some common filter conditions used to browse the alarm
information and statistics are set in a template. As a result, when browsing alarm
information or alarm statistics in the future, you do not need to reset the filter conditions.
l Alarm attribute templates combine the attributes of the NE alarms, such as alarm level,
automatically reported alarm state, and masked alarm state. You can use the default
template of the system. You can also customize the alarm attribute template according to
the alarm monitoring policy. You can apply the alarm attribute template to the specified
NE. You can also simplify the operations of setting alarm attributes.
7.1.4 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 T2000, network equipment, trails and
services. Meanwhile, you can synchronize, check and acknowledge these alarms.
Table 7-2 lists the impacts of the alarm operations on NEs.
Table 7-2 Impacts of alarm viewing operations on NEs
Operation Affect NE or Not
Alarm Viewing No
Alarm Acknowledgement No
Alarm Synchronization No
Alarm Check No
Alarm Refreshing No
Alarm Deletion Yes
Alarm Filtering No
Alarm Remarks No
Alarm Viewing
You can view the alarms of the equipment and services on the T2000 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 T2000: You can select an NE or a T2000 on the Main
TopologyNE List to view the current alarms of the selected object.

l Viewing current alarms of a trail: In the Trail View, you can quickly view the alarms of
the concerned trail or of the currently managed trail. This facilitates the maintenance.
l Viewing history alarms: By viewing all the history alarms recorded in the T2000, you can
know the faults that once occurred on the NEs and on the T2000. This helps in the long-
term performance analysis.
Alarm Acknowledgement
An acknowledged alarm indicates that this alarm has been handled by a user. The cleared alarms,
after being acknowledged, disappear from the current alarm browsing window, and are moved
to the history alarm library. 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
T2000 automatically acknowledges the alarms cleared before a specified time at 3:00 every
morning.
Alarm Synchronization
When the communication between the T2000 and equipment is interrupted and then restored,
or when the T2000 is restarted, you need to synchronize the alarm information to keep the
consistency of the alarm data. To synchronize the alarms, the T2000 compares the alarms in the
T2000 with the alarms in the NE. If the alarm data is inconsistent, the T2000 uploads the NE
alarm data to the T2000 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 T2000 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 the clearance status of the current alarms on the
T2000 with the actual status of the alarms on the NE. If the alarm is already cleared on the NE,
the alarm is marked as cleared on the T2000.
Alarm Refreshing
When you refresh the alarms, the latest alarm information is obtained from the alarm database
of the T2000 and displayed on the T2000 client.
Alarm Deletion
When you delete an alarm, the alarm is cleared from the NE and the current alarm library of the
T2000. After that, the alarm is moved to the history alarm library.
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 Remarks
l Rising Time
l Cleared Time
l Alarm Status
l Severity
l Alarm Type
l Alarm Plane
Alarm Remarks
You can add remarks for the handled alarms. This is useful when you manage a large number
of alarms.
7.1.5 Alarm Setting Operations

Alarm setting operations include a series of alarm management operations, such as setting the
alarm suppression, automatic alarm reporting and alarm reversion. You can set the alarm
attributes as required in favor of the alarm management.
Table 7-3 lists the impacts of alarm setting operations on NEs and services.
Table 7-3 Impacts of alarm setting operations on NEs and services
Operation Affect NE or Not Affect Service or Not
Setting the Alarm Yes No

Suppression
Setting the Automatic Yes No

Alarm Reporting
Setting the Alarm Hold-Off Yes No
Setting the Alarm Saving Yes No

Mode
Setting the Alarm Yes No

Reversion
Setting the Bit Error Alarm Yes No

Threshold
Setting the AIS Insertion Yes Yes
Setting the UNEQ Insertion Yes Yes
Setting the Alarm Insertion Yes Yes
Setting the Alarm Severity Yes No
Setting the NE Alarm No No

Filtering

Operation Affect NE or Not Affect Service or Not
Setting Alarm Functional No No

Switches
Setting the Alarm No No

Correlation Rule
Setting Alarm Attributes No No
Table 7-4 lists the impacts of alarm setting operations on alarms. You can refer to Alarm
Reporting Process.
Table 7-4 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
monitoring the alarm.
l After an alarm is suppressed, the alarm
data is not stored in the NE.
l After an alarm is suppressed, the T2000
does not clear the reported alarms, until an
alarm cleared notification is received.
Setting the Automatic Alarm Reporting l If an alarm is set to not automatically

reported, the alarm data is retained in the
NE but not reported to the T2000.
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
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.
Setting the NE Alarm Filtering l After an alarm is filtered, it is not displayed

on the T2000.
l After an alarm is filtered, it is not stored on
the T2000.

Setting the Alarm Suppression

You can set the alarm suppression for all the alarms of an NE or of a board on an NE.
Setting the Automatic Alarm Reporting

If the automatic alarm reporting is enabled, the alarm is immediately reported to the T2000 as
long as the alarm is raised from the equipment. When the alarm is reported, the alarm indicator
on the T2000 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 T2000 by a large amount 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 T2000 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, Stop and Wrap.
l In the Stop mode, if the NE alarm register reaches its capacity limit, the newly reported
alarm data is discarded.
l In the Wrap mode, if the NE alarm register reaches its capacity limit, the newly reported
alarm data overwrites the original alarm data, and is saved in the register from the initial
address.
Setting the Alarm Reversion

The alarm reversion has three modes: non-revertive, automatic reversion and manual reversion.
Table 7-5 shows respective ways of handling alarms in the three modes.
Table 7-5 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.

Reversion Mode Handling
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 T2000.
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.
CAUTION
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 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 a UNEQ at the
specified channel of the NE. You can select whether to monitor the LOS alarm at the channel
as required.
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 T2000 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.
Setting the NE Alarm Filtering

You can set the filtering for the NE alarms of the specified type. The alarms filtered out are
neither displayed on the T2000, nor saved in the T2000 database.
By default, the alarms of all types are not in the filtered status.
Setting Alarm Functional Switches

The alarm functional switches include the following:
l Automatic alarm acknowledgement switch: If the switch is enabled, the T2000
automatically acknowledges the alarms cleared before a specified time at 3:00 every
morning.
l Automatic alarm synchronization switch: You can specify trigger conditions for the
automatic alarm synchronization, such as when the T2000 starts, when the communication
is restored from an interruption, or when an LCT user logs out.
l Alarm correlation analysis switch: If the alarm correlation analysis is enabled, the system
analyzes the reported alarms according to the correlation analysis rule so that only the root
alarms are displayed while the non-root alarms generated by the root alarms are suppressed.
Setting the Alarm Correlation Rule

By setting the alarm correlation rule and enable the alarm correlation analysis function, you can
effectively suppress the correlative alarms. This function helps you to quickly locate faults.
Setting T2000 Alarm Attributes

Setting the T2000 alarm attributes includes setting the alarm severity and the alarm suppression
for the T2000. This function is particularly for the alarms of the T2000 itself, such as the alarms
about insufficient disk space and the communication interruption between the T2000 and an NE.
7.1.6 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 T2000 alarm correlation.
NE Alarm Correlation
The NE alarm correlation rule is the alarm performance monitoring mechanism of the logical
function module of the SDH 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. An root alarm
always generate 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 R-LOF,
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-3 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-3 NE Alarm Correlation
RST MST MSA HPT HPA LPT
"1"
LOS/LOF
RS-TIM AIS
J0
BIP Err
B1
MS-AIS "1"
K2 AIS
MS-BIP Err
B2
MS-REI
M1
MS-REI
K2
AU-AIS "1"
AU-LOP
HP-SLM HP-UNEG "1"
C2
HP-TIM
J1 AIS
HP-BIP Err
B3
HP-RDI
G1
HP-RDI
G1
TU-AIS "1"
V1-V3 TU-LOP
LP-UNEQ "1"
V5
LP-TIM
J2
LP-BIP Err AIS
V5
LP-REI
V5
LP-RDI
V5 "1" AIS
LP-SIM
V5
indicates that the corresponding alarm or signal is generated

indicates that the corresponding alarm is detected
T2000 Alarm Correlation

For the T2000 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 NE3
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 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 Elevate the severity level of alarm 1.
l Elevate the severity level of alarm 2.
l Elevate the severity level of alarm 1 and alarm 2.
The alarm correlation rule can elevate the severity level of root alarms and correlative alarms
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 elevate the severity level of the TU_AIS in an alarm correlation rule, the
TU_AIS is elevated 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 T2000.
7.1.7 Alarm Notification

To get informed of the alarm information is critical to handling alarms and to the network
maintenance. The T2000 provides various ways of notifying alarms.
Alarm Color
The T2000 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 critical, major
and minor 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.
l On the Main Topology, the colors of the NE and subnet icons are displayed according to
the alarm that is currently at the highest severity level. The frame outside the icon indicates
all the unacknowledged alarms.
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 T2000 displays critical alarms in red, major alarms in orange, minor alarms in
yellow, and warning alarms in purple. You can define different colors for the alarms at different
severity levels.
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 Browse History Alarm
l Current Alarm Statistics
In the Browse Current Alarm window, if you select Display the 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 T2000 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 the a sound box, the T2000 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 T2000 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 equipment 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.8 Alarm Severity

Alarm severity is used to identify the severity level, significance and urgency of an alarm. Alarms
come in the following four levels in descending order of severity: critical, major, minor and
warning.
Table 7-6 shows how to handle the alarms of different severity levels.
Table 7-6 Alarm severity

Alarm severity Definition Handling
Critical Refers to fault alarms and Should be handled

event alarms that may result immediately. Otherwise, the
in breakdown of the NE or the system may break down.
whole system, such as board
failure.
Major Refers to fault alarms and Should be handled timely.

event alarms of boards or line Otherwise, the important
in local parts. functions will be affected.
Minor Refers to general fault alarms Such alarms are used to

and event alarms that indicate remind the maintenance
the operating status of boards engineer to efficiently locate
or line. the alarm causes and
eliminate the possible faults.
Warning Refers to fault
alarms and event alarms for
warning.
Warning Refers to the fault alarms and Such alarms indicate

event alarms that do not operating status of the
affect the system equipment and need no
performance and services but handling.
may impose potential
impacts on the service quality
of the equipment or
resources. Some refers to the
prompt information of the
system when equipment
restores to normal, for
example, the switching
alarm.
You can take different measures for alarms of different severities. On the T2000, 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.9 Alarm Status

Alarms can be categorized according to their status based on whether they are acknowledged or
cleared. A network operator can take different measures to handle alarms according to the status,
severity level and causes of the alarms.
Alarm Status
Based on whether an alarm is acknowledged or cleared, an alarm can be in the following status:
unacknowledged and uncleared, acknowledged and uncleared, unacknowledged and cleared,
acknowledeged and cleared. Figure 7-4 is a module about the alarm status conversion.
Figure 7-4 Alarm status conversion module
NE
Report alarm
Unacked&uncleared
Clear Unacked&cleared alarm
alarm
(current alarm)
(current alarm)
Acknowledge Acknowledge
Acked&uncleared alarm Clear Acked&cleared alarm

(current alarm) (history alarm)
NOTE
The acknowledged and cleared alarms are called history alarms. The alarms in other status (that is,
unacknowledged and uncleared, acknowledged and uncleared, unacknowledged and cleared) are called current
alarms.
Alarm Status Switching Conditions

The change in the alarm clearance status and the alarm acknowledgement status triggers the
switching of the alarm status.
l Alarm clearance:
When the factor that causes an alarm to disappear, the NE detects that the alarm is cleared.
In this case, the NE notifies the T2000 to refresh the alarm status, and at the same time
deletes the alarms in the alarm library of the SCC.
l Alarm acknowledgement:
The alarm acknowledgement function enables you to identify whether an alarm has been
handled. By viewing the alarm status, you can clearly differentiate between the handled
and not handled alarms, and then take different measures for them.

7.1.10 Alarm Category

The alarms can be categorized according to the generating location and the T2000 standards and
functions.
The alarms can be categorized into the following two types according to the generating location:
l NE alarms: alarms generated when the NE equipment is faulty.
l T2000 alarms: alarms generated when the T2000 environment or the connection between
the T2000 and NE is faulty.
The alarms can be categorized into the following six types according to the T2000 standards and
functions:
l Communication alarms: alarms related to NE communication, ECC communication, and
optical signal communication. For example, loss of NE communication and loss of signal.
l Processing alarms: alarms related to software processing and abnormal conditions. For
example, equipment bus collision and secondary path check failure.
l Equipment alarms: alarms related to equipment hardware. For example, laser failure and
optical port loopback.
l Service alarms: alarms related to the service status and QoS. For example, performance
threshold-crossing of the multiplex section, and excessive B2 bit errors.
l Environment alarms: alarms related to the power supply system and equipment room
environment (temperature, humidity, access control and so on). For example, the
temperature of the power module exceeds a certain threshold.
l Security alarms: alarms related to the security of T2000 and NEs. For example, an NE user
is not logged in.
7.1.11 Current Alarms and History Alarms

Current alarms and history alarms have the following four types: current NE alarms, history NE
alarms, current T2000 alarms and history T2000 alarms. The T2000 alarm includes the alarms
reported from NEs and the alarms generated by the T2000 itself.
Current NE Alams and Current T2000 Alarms

The current NE alarm refers to the alarm data stored in the current alarm library of the SCC.
Whether the current NE alarm reflects the actual alarm status of each board on an NE depends
on the following factors:
l Whether the alarm suppression is configured
l Whether the alarm reversion is configured
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 T2000 alarm refers to the alarm data stored in the current alarm library of the T2000. Whether
the current T2000 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 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 T2000 itself exist
History NE Alarm and History T2000 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 T2000 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 T2000. Whether the history T2000 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 T2000 itself exist
7.1.12 Alarm Statistics

The alarm statistics are displayed in the tabular format according to the user-defined conditions.
This helps you to analyze the running status of the equipment.
On the T2000, the statistics about the current alarms can be collected. The T2000 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 T2000 to collect the alarm statistics within
this time range.
7.1.13 Alarm Dumping

When the history alarm data in the T2000 database exceeds a certain amount, the T2000
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 T2000 database to a specified directory as
a file. In this way, the T2000 performance is improved.
Overflow Dumping
You can set the maximum storage capacity of the alarms using the T2000. The T2000
periodically checks the number of history alarms. Once the history alarm data exceeds the
capacity, the T2000 automatically dumps the data in the history alarm library to a file to relieve
the burden of the T2000 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 T2000 automatically dumps the alarm data stored in the T2000 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 T2000 performs the dumping in January
5. The dumped history alarms are the alarms that are ended before January 4.

Immediate Dumping
The T2000 dumps the history alarm data in the T2000 database to a specified directory
immediately when an alarm is cleared. This mode is known as the immediate dumping. In this
mode, you can specify a stop time for the immediate dumping. All alarms cleared before this
time are dumped to the specified directory.
NOTE
l On UNIX, the dump files are usually saved to the /T2000/server/dump directory. You can manually back
up or delete these files.
l On Windows, the dump files are usually saved to the \T2000\server\dump directory. You can manually
back up or delete these files.
7.2 Customizing Alarm Template

The T2000 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.2.1 Creating an Alarm or Event Browse Template
Alarm or event browse conditions are complicated. To prevent setting conditions repeatedly,
you can save the preset conditions as a template. You can use the template to browse the alarms
or events conveniently.
7.2.2 Exporting or Importing an Alarm Template
You can export an alarm template so that you can directly import the template when you use it
next time. Therefore, the template becomes portable.
7.2.3 Creating the Alarm Statistics Template
Alarm statistical conditions are complicated. To prevent setting conditions repeatedly, you can
save the preset conditions as a template. When an alarm statistics template is set, you can double-
click the template to collect statistics on the alarms.
7.2.4 Setting the Startup Template
You can set the startup template for the Current Alarms, History Alarms, Events, or Alarm
Statistics window. After you select a menu, the window displays the alarms, events, or alarm
statistics information according to the settings of the startup template.
7.2.5 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.2.1 Creating an Alarm or Event Browse Template

Alarm or event browse conditions are complicated. To prevent setting conditions repeatedly,
you can save the preset conditions as a template. You can use the template to browse the alarms
or events conveniently.
Prerequisite
You must be an NMS user with the "Fault Operator" authority or higher.

Context
l For each template type, up to 50 templates can be created.
l The Save button of the default template is disabled. In other words, the default template
cannot be modified.
l A template name cannot contain the special characters such as: ~ ` ! @ # $ % ^ * ( ) { } |
\ /.
Procedure
Step 1 In the alarm or event browse window, click Filter by Template, and then choose New.
Step 2 In the New Template dialog box, specify a template name. Click OK.
Step 3 In the New Template dialog box, on the Basic Settings and Alarm Source tabs, set the filter
conditions, and then click Save.
NOTE
l On the Basic Settings tab, in the Severity, Acknowledge Status, Clear Status, or Type group box, you
need to select at least one parameter. On the Alarm Source tab, you need to select at least one object or
type. Otherwise, the T2000 prompts that a certain parameter is not selected.
l The history alarm browse template does not contain the Ack Status or Clear Status parameter. The event
browse template does not contain the Ack Status, Clear Status, Cleared Time, or Duration parameter.
The GUI is similar to the following figure.

Step 4 In the Confirm dialog box, click Yes or No.
----End
7.2.2 Exporting or Importing an Alarm Template

You can export an alarm template so that you can directly import the template when you use it
next time. Therefore, the template becomes portable.
Prerequisite
Context
l The default alarm template cannot be exported.
l For security purposes, the exported template does not contain the resource condition you
choose, that is, it does not contain the specific device information.
Procedure
Step 1 Choose Fault > Import/Export Template.

Step 2 In the Import/Export template dialog box, export or import the alarm template.
l Export the template to a file.
1. Choose Export to file.
2. Click next to the File name text box. In the Save dialog box, set the destination
path and file name. Click Save.
3. Click OK.
4. In the Information dialog box, click OK.
l Import the template from a file.
1. Choose Import from file.
2. Click next to the File name text box. In the Open dialog box, choose the template
file, and then click Open.
3. Click OK.
4. In the Information dialog box, click OK.
----End
7.2.3 Creating the Alarm Statistics Template

Alarm statistical conditions are complicated. To prevent setting conditions repeatedly, you can
save the preset conditions as a template. When an alarm statistics template is set, you can double-
click the template to collect statistics on the alarms.
Context
l For each template type, up to 50 templates can be created.
l A template name cannot contain the special characters such as: ~ ` ! @ # $ % ^ * ( ) { } |
\ /.
l Usability is an index used to indicate the availability of a resource (such as a device) in a
period. The calculation formula is as follows:
Usability = (Statistical time range – Total alarm duration) / Statistical time range.
The total alarm duration (Time Length) does not contain the repeated duration. For
example, if alarm A lasts three minutes, alarm B lasts two minutes, and the two alarms
overlap for one minute, the total alarm duration is four minutes.
l When time is taken as the row name, the statistics range is specified as follows:

– When statistics is collected by month, the statistics time range does not exceed one year.
– When statistics is collected by day, the statistics time range does not exceed 90 days.
– When statistics is collected by hour, the statistics time range does not exceed 240 hours.
– When statistics is collected by time (five minutes), the statistics time range does not
exceed 24 hours.
l The parameters for statistics conditions are correlated. If you set a parameter to a specific
value, another parameter may cannot be set or cannot be set to a specific value. For example,
if you set Row heading to month, Anytime and Since cannot be set.
Procedure
Step 1 In the Alarm Statistics window, click Statistic by Template, and then select New.
Step 2 In the New Template dialog box, specify a template name. Click OK.
Step 3 In the New Template dialog box, configure appropriate settings, and then click Save. In the
New Template dialog box, on the Basic Settings and Alarm Source tabs, set the filter
conditions, and then click Save.

Step 4 In the Confirm dialog box, click Yes. In the Confirm dialog box, click Yes or No.
----End
7.2.4 Setting the Startup Template

You can set the startup template for the Current Alarms, History Alarms, Events, or Alarm
Statistics window. After you select a menu, the window displays the alarms, events, or alarm
statistics information according to the settings of the startup template.
Prerequisite
Procedure
Step 1 In the Current Alarms, History Alarms, Events, or Alarm Statistics window, click Filter by
Template, and then choose Open .
NOTE
In the Alarm Statistics window, click Statistics by Template.
Step 2 In the Open dialog box, select a template that you want to set to the startup template. Click Set
Startup Template.

When you set the startup template for a window, and then choose the corresponding menu to
access the window, the alarm or event information is displayed according to the settings of the
template.
----End
7.2.5 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
You must be an NM user with the "NE operator" authority or higher.
Context
l If the alarm attribute template is not created, the T2000 handles the alarms reported from
NEs according to the default alarm attribute template.
l If a template on one of the T2000 servers is customized, you are recommended to customize
the same template on other T2000 servers, to ensure that the alarms are consistently
monitored on each server.
l You can set different alarm management templates for different NEs.
Procedure
Step 1 Choose Fault > Settings > Alarm Attribute Template from the Main Menu.
Step 2 Select a template from the Template drop-down list.
Step 3 Select the desired alarm, and modify the Severity, Auto Reporting Status, and Status.
Step 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.
Step 5 Click Apply to. The Apply Alarm Attribute Template to NE dialog box is displayed.
Step 6 Select the alarm attributes to be applied and the target NE. Click OK.

NOTE
After the alarm attribute template is applied to the NE, the T2000 automatically handles the alarms reported
from the NE according to the settings in the template.
----End

7.3 Synchronizing Alarms

You can synchronize the current alarms of the NE and the T2000. This feature ensures that the
alarms on the NEs are synchronous with the alarms on the T2000, and that the current NM alarms
are synchronous with the alarms in the T2000 alarm database.
7.3.1 Synchronizing Networkwide Current Alarms
The alarm synchronization operation compares the alarms in the T2000 database and the alarms
in the NE database. If the alarms are inconsistent, the alarms in the NE database are uploaded
to the T2000 database. The existing alarms in the T2000 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.3.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 T2000 and the NE alarms, you can synchronize the current alarms
for the specified NE.
7.3.3 Synchronizing the Current Alarms for the T2000
By synchronizing the current NM alarms, you can update the T2000 alarm database. This
function reports all uncleared NM alarms again to the T2000 alarm database. In addition, it clears
the NM alarms that are actually cleared but are uncleared in the alarm database. As a result, the
alarms in the T2000 alarm database are consistent with the current NM alarms.
7.3.4 Setting Alarm Auto Synchronization
You can set alarm auto synchronization. After the T2000 resumes the communication with an
NE or is restarted, the T2000 automatically synchronizes the alarms with those on the NE. This
helps keep alarm data consistency between the T2000 and NEs.
7.3.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
Procedure
Step 1 Choose Fault > Synchronize Networkwide Alarms from the Main Menu.
A progress bar is displayed. After the operation is complete, a prompt is displayed indicating
that the operation is successful.
Step 2 Click Close.
----End

7.3.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 T2000 and the NE alarms, you can synchronize the current alarms
for the specified NE.
Prerequisite
Procedure
Step 1 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.
Step 2 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 is displayed indicating
that the operation is successful.
Step 3 Click Close.
----End
7.3.3 Synchronizing the Current Alarms for the T2000

By synchronizing the current NM alarms, you can update the T2000 alarm database. This
function reports all uncleared NM alarms again to the T2000 alarm database. In addition, it clears
the NM alarms that are actually cleared but are uncleared in the alarm database. As a result, the
alarms in the T2000 alarm database are consistent with the current NM alarms.
Prerequisite
Procedure
Step 1 Right-click the local NM icon on the Main Topology, and choose Synchronize Current
Alarms from the shortcut menu. Wait for the end of operation. The Operation Result dialog
box is displayed.
Step 2 Click Close.
----End


Prerequisite
Procedure
Step 1 Choose Fault > Settings > Auto Synchronization from the Main Menu.
Step 2 In the Auto Synchronization dialog box, set the alarm synchronization parameters.
l When Starting the NM indicates that the T2000 automatically synchronizes the alarms
with those on all the NEs when it is started.
l When communication is lost and recovers indicates that the T2000 automatically
synchronizes the alarms with those on a specific NE when it resumes the communication
with the NE.
l LCT User Logs Out indicates that the T2000 automatically synchronizes the alarms with
those on a specific NE when the LCT user logs out.
Step 3 Click OK.
----End
7.4 Viewing Alarms

The network maintenance personnel can view alarms to know the network status.
7.4.1 Monitoring Alarms Through the Topology View

In the topology view, you can check the status of a device icon to know if an alarm is raised by
this device. You can also browse the alarm details through the topology view.
7.4.2 Monitoring Alarms Through the Alarm Panel
You can monitor alarms through the alarm panel to obtain a brief understanding of the current
alarms.
7.4.3 Viewing Current Alarms
By viewing the current alarms, you can know the running status of the network. This helps during
the network maintenance when you need to update the alarm information and take proper
measures on time. When you view the current alarms, you can at the same time perform other
operations for these alarms. For example, synchronize, refresh, check, acknowledge and filter
alarms.
7.4.4 Viewing History Alarms
By viewing all the history alarms recorded by the T2000, you can know the faults that once
occurred on NEs or on the T2000. This helps you to analyze the faults. When you view the
history alarms, you can perform other operations for these alarms at the same time, for example,
refresh and filter alarms.
7.4.5 Viewing Abnormal Events
During routine maintenance, you should view abnormal events to check the current status of the
network.
7.4.6 Viewing the Statistics of Alarms
The T2000 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.4.7 Viewing Correlative Alarms

By viewing suppressed correlative alarms, you can know more information about the faults.
7.4.8 Viewing Current Alarms of a Fiber/Cable
The alarm generated on a fiber/cable is from the source or sink end of the fiber/cable, the trail
that the fiber/cable carries, or the fiber/cable itself. Viewing current alarms of a fiber/cable can
obtain the relevant fault information of the fiber/cable in time, to fast and accurately locate the
fault.
7.4.9 Viewing History Alarms of a Fiber/Cable
Viewing history alarms of a fiber/cable can know the long-term statuses of the fiber/cable during
network running. The history alarm information can be the reference when you maintain the
fiber/cable.
7.4.10 Brows Remote Notification Logs
You can brows remote notification logs on T2000.
7.4.11 Managing Networkwide SDH Alarm Trails in Real Time
The T2000 can manage the networkwide SDH alarm trails in real time. It manages all the SDH
trails that have current alarms. If an alarm ends, the related trail is automatically removed from
the user interface.
7.4.12 Managing Networkwide WDM Alarm Trails in Real Time
The T2000 can manage the networkwide WDM alarm trails in real time. It manages all the WDM
the user interface.
7.4.13 Viewing Current Alarms of an SDH Trail
By viewing the current alarms of an SDH trail, you can know the running status of the services
carried on this trail. This helps during the network maintenance when you need to update the
alarm information and take proper measures on time. When you view the current alarms of an
SDH trail, you can perform other operations for these alarms at the same time. For example,
synchronize, refresh, check, acknowledge and filter alarms.
7.4.14 Viewing History Alarms of an SDH Trail
By viewing history alarms of an SDH trail, you can learn history faults of the trail for reference
of operation and maintenance.
7.4.15 Viewing Current Alarms of a WDM Trail
By querying current alarms of a WDM trail, you can learn about faults on this trail to perform
maintenance in a timely and effective manner.
7.4.16 Viewing History Alarms of a WDM Trail
By querying history alarms of a WDM trail, you can learn about history faults on this trail and
provide reference for maintenance of current faults.
7.4.17 Viewing Current Alarms of a Trunk Link
By viewing current alarms of a trunk link, you can query the running status of services that the
current trail carries. During the network maintenance, you need to update alarm information and
properly handle the alarms in time. When viewing the current alarms of the trunk link, you can
also synchronize, refresh, check, acknowledge and filter the alarms.
7.4.18 Viewing History Alarms of a Trunk Link
By viewing history alarms of a specified trunk link, you can learn history faults of the trail for
reference of operation and maintenance.
7.4.19 Viewing Current Alarms of an Ethernet Trail
By viewing current alarms of an Ethernet trail, you can query the running status of services that
the current trail carries. During the network maintenance, you need to update alarm information

and properly handle the alarms in time. When viewing the current alarms of the Ethernet trail,
you can also synchronize, refresh, check, acknowledge and filter the alarms.
7.4.20 Viewing History Alarms of an Ethernet Trail
By viewing history alarms of an Ethernet trail, you can learn history faults of the trail for
reference of the operation and maintenance.
7.4.1 Monitoring Alarms Through the Topology View

In the topology view, you can check the status of a device icon to know if an alarm is raised by
this device. You can also browse the alarm details through the topology view.
Prerequisite
Procedure
Step 1 In the topology view or the navigation tree, right-click the device that raises an alarm and choose
Browse Current Alarms.
Step 2 On the Current Alarms tab, view the information on the current alarm of the device.
----End
7.4.2 Monitoring Alarms Through the Alarm Panel

You can monitor alarms through the alarm panel to obtain a brief understanding of the current
alarms.
Prerequisite
Procedure
l Monitor alarms through the thumbnail of the alarm panel.
The thumbnail of the alarm panel consists of three color blocks and an event indicator at
the upper right corner of the client. Each color block represents an alarm severity. The
number on a color block represents the number of the current uncleared alarms of the
specific severity in the T2000. When a new alarm occurs, the corresponding color block
blinks to prompt you. You can check the thumbnail of the alarm panel for new alarms,
alarm severities, current alarm statistics, and new events.
You can click a color block on the thumbnail to view the details on the alarms of a specific
severity. If you move the cursor to the button that is at the upper right corner of the
client, the number of the new events is displayed. When a new event occurs, this button
turns red and blinks to prompt you. Click this button. Then an event browse window is
displayed.
l Monitor alarms through the alarm panel.
Choose Fault > Show Alarm Panel , or click on the toolbar to display the alarm
panel. You can add a current alarm browse template or an event browse template to the
alarm panel. The alarm panel displays alarms information based on the template.

When you monitor alarms through the alarm panel and you want to know the alarm details,
you can double-click an alarm or event template on the alarm panel to open the
corresponding alarm or event template window. Then you can query the alarm details.
----End
7.4.3 Viewing Current Alarms

By viewing the current alarms, you can know the running status of the network. This helps during
the network maintenance when you need to update the alarm information and take proper
measures on time. When you view the current alarms, you can at the same time perform other
operations for these alarms. For example, synchronize, refresh, check, acknowledge and filter
alarms.
Prerequisite
To perform the browse operation, You must be an NM user with the "NM monitor" authority or
higher. To perform the acknowledgement or clearance operation, you must be an NM user with
the "NE operator" authority or higher.
Procedure
Step 1 Choose Fault > Browse Current Alarm from the Main Menu.
Step 2 In the Filter dialog box, set filter criteria and click OK. The current alarm viewing window is
displayed.
NOTE
l The default alarm viewing template chooses all current alarms. If you want to view the correlative alarms
caused by the current alarms, click Display correlative alarms.
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.
Step 3 Optional: Right-click an alarm in the query result list, and you can perform the following
operations:
l Choose Correlative Alarms from the shortcut menu to query the correlative alarms.
l Choose Remark from the shortcut menu to set remarks for this alarm.
l Choose Acknowledge from the shortcut menu to acknowledge the alarm.
NOTE
l If the selected alarm is an unacknowledged and uncleared alarm, it changes to an acknowledged but
uncleared alarm.
l If the selected alarm is an unacknowledged but cleared alarm, the alarm changes to a history alarm.
l Choose Locating to Topo Object from the shortcut menu to locate the alarm to the
topological object where the alarm occurs.

l Choose Fault Diagnosis from the shortcut menu to locate and remove the fault using the
fault diagnosis wizard on the T2000.
l Choose Suppress from the shortcut menu to suppress the alarm.
Step 4 Optional: Select the Display latest alarms check box to view the real-time alarms reported.
Step 5 Optional: Select one or more alarms. Click Check to check the selected alarms.
NOTE
When you check the alarm, you are comparing one or more uncleared alarms on the T2000 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 T2000. If the alarm does not exist in the NE, the alarm is cleared on the T2000.
Step 6 Optional: Select an alarm. Its details and handling suggestions are displayed in the table below.
Step 7 Optional: Select one or more NE alarms and click Delete. The Delete the Alarms dialog box
is displayed. Click Yes.
The progress bar about the alarm deletion is displayed.
Step 8 Optional: Click Print or Save As to output the alarm data.

NOTE
For operations of backing up the T2000 data, see related sections in the OptiX iManager T2000 Administrator
Guide.
----End
Reference Standard
All current alarms are cleared.
Troubleshooting
If an NM alarm is reported, handle this alarm according to the repairing suggestion. For details,
press F1 to view "The T2000 Alarm References" of the Online Help.
7.4.4 Viewing History Alarms

By viewing all the history alarms recorded by the T2000, you can know the faults that once
occurred on NEs or on the T2000. This helps you to analyze the faults. When you view the
history alarms, you can perform other operations for these alarms at the same time, for example,
refresh and filter alarms.
Prerequisite
You must be an NM user with the "NE monitor" authority or higher.
Procedure
Step 1 Choose Fault > Browse History Alarm from the Main Menu.
Step 2 In the Filter dialog box, set filter criteria and click OK. The history alarm viewing window is
displayed.

NOTE
l All history alarms are selected in the default alarm browsing template.
l If you set the startup template of viewing history alarms, the Filter dialog box is not displayed. Alarms that
meet the startup template condition are displayed instead.
Step 3 Optional: Select an alarm. Its details and handling suggestions are displayed in the panes below.
----End
Postrequisite
If there is no relevant history alarm in the Browse History Alarm window, you can query the
alarm data of a specific time by accessing the directory of the dumped alarm data.
7.4.5 Viewing Abnormal Events

During routine maintenance, you should view abnormal events to check the current status of the
network.
Prerequisite
Procedure
Step 1 Choose Fault > Browse Event from the Main Menu.
Step 2 In the Filter dialog box, set filter criteria and click OK. The event viewing window is displayed.
NOTE
l All abnormal events are selected in the default event browsing template.
l If you set the startup template of viewing abnormal events, the Filter dialog box is not displayed. Alarms
that meet the startup template condition are displayed instead.
----End
7.4.6 Viewing the Statistics of Alarms

The T2000 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
Procedure
Step 1 Choose Fault > Alarms Statistics from the Main Menu.
Step 2 In the Statistical Condition dialog box, 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 Statistical Condition dialog box is not displayed. The
statistical result obtained by the startup template is displayed instead.
Step 3 In the alarm statistics window, check the statistical result.

l Click the Alarm Statistics tab. The alarm information collected based on the row and
column headings are displayed.
l Click the Alarm Average Ack Time tab. The mean alarm acknowledgement time collected
based on the row and column headings is displayed.
l Click the Alarm Average Cleared Time tab. The mean alarm clearance time collected
based on the row and column headings is displayed.
Step 4 According to the buttons at the bottom of the Alarm Statistics window, you can perform the
following operations:
l Click Statistics by Template to create, open, or save an alarm statistical template.
l Click Statistical Condition 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.4.7 Viewing Correlative Alarms

By viewing suppressed correlative alarms, you can know more information about the faults.
Prerequisite
l You must be an NM user with the "NE monitor" authority or higher.
l The alarm correlation rules must be created.
Procedure
Step 1 Choose Fault > Browse Current Alarms from the Main Menu.
Step 2 Select the alarm that you want, right-click and choose Correlative Alarms from the shortcut
menu.
Step 3 View the details about the alarms in the Correlative Alarms dialog box displayed.
----End
7.4.8 Viewing Current Alarms of a Fiber/Cable

The alarm generated on a fiber/cable is from the source or sink end of the fiber/cable, the trail
that the fiber/cable carries, or the fiber/cable itself. Viewing current alarms of a fiber/cable can
obtain the relevant fault information of the fiber/cable in time, to fast and accurately locate the
fault.
Prerequisite

Procedure
Step 2 Right-click a fiber/cable in the pane and choose Browse Relevant Current Alarms from the
shortcut menu.
Current alarms generated on the fiber/cable are displayed in the Current Alarms window.
Step 3 To display the latest alarms, check the Display latest alarms check box in the lower left corner.
NOTE
The effect of checking the check box is equivalent to refreshing. When the check box is checked, the
Refresh button is grayed out.
Step 4 Optional: Select one or more alarms and click Check to check the selected alarms.
NOTE
Checking alarms is to compare one or more uncleared alarms on the T2000 with those on the NE. If an
alarm exists as a current alarm on the NE, the alarm information remains unchanged on the T2000. If the
alarm does not exist on the NE, the alarm is cleared on the T2000.
Step 5 Select an alarm, and the alarm details and alarm causes are displayed in the panes in the lower
area.
Step 6 Select one or more alarms and click Acknowledge. The Operation Result dialog box is
displayed.
Step 7 Click Close. The Ack User and Ack Time fields display the corresponding values of the selected
alarms.
NOTE
Acknowledged and cleared alarms automatically change to history alarms.
Step 8 Select one or more alarms and click Delete. In the Delete the Alarms dialog box, click Yes.
The progress bar of Delete Alarm is displayed.
Step 9 In the Operation Result dialog box, click Close.
Step 10 Optional: Click Print or Save As to export the alarm data.
----End
7.4.9 Viewing History Alarms of a Fiber/Cable

Viewing history alarms of a fiber/cable can know the long-term statuses of the fiber/cable during
network running. The history alarm information can be the reference when you maintain the
fiber/cable.
Prerequisite
Procedure
Step 1 Choose Trail > Fiber/Cable Management from the Main Menu.
Step 2 Right-click a fiber/cable in the pane and choose Browse Relevant Historical Alarms from the
shortcut menu.
History alarms generated on the fiber/cable are displayed in the History Alarms window.

Step 3 Optional: Select an alarm, and the alarm details and alarm causes are displayed in the panes in
the lower area.
----End
7.4.10 Brows Remote Notification Logs

You can brows remote notification logs on T2000.
Prerequisite
You must be an NM user with "NM monitor" authority or higher.
Procedure
Step 1 Choose FaultBrows Remote Notification Logs from the Main Menu.
Step 2 Optional: Click Filter, the Filter dialog box is displayed.
Step 3 Optional: Set the related parameters.
----End
7.4.11 Managing Networkwide SDH Alarm Trails in Real Time

The T2000 can manage the networkwide SDH alarm trails in real time. It manages all the SDH
the user interface.
Prerequisite
l The license for trail management must be available.
Procedure
Step 1 Choose Trail > Alarm Affected SDH Trails from the Main Menu.
Step 2 In the Set Trail Browse Filter Condition dialog box, set the filter criteria and click Filter
All. The trails are displayed in the list.
Step 3 Optional: To manage the trail alarms, select a trail, click Alarm, select Current Alarm or
History Alarm from the drop-down list, and manage the alarms in the corresponding window.
Step 4 Optional: To manage the trail performance, select a trail, click Performance, select Query
Performance or Performance Parameter from the drop-down list, and manage the
performance in the corresponding window.
----End
7.4.12 Managing Networkwide WDM Alarm Trails in Real Time

The T2000 can manage the networkwide WDM alarm trails in real time. It manages all the WDM
the user interface.

Prerequisite
l The license for trail management must be available.
Procedure
Step 1 Choose Trail > Alarm Affected WDM Trails from the Main Menu.
Step 2 Set the trail filter criteria and click Filter All.
Step 3 In the Alarm Affected WDM Trails window displayed, the alarm affected WDM trails that
meet the criteria are displayed.
Step 4 Optional: Right-click the title of a parameter column and set the trail attributes to be displayed.
Step 5 Choose Alarm. Select the corresponding command from the drop-down menu to query or set
the alarm data of each trail.
Step 6 Optional: To query the performance data of a trail, click Performance > Browse
Performance.
Step 7 Optional: To print the trail information, click Print. To save the trail information, click Save
As.
----End
7.4.13 Viewing Current Alarms of an SDH Trail

By viewing the current alarms of an SDH trail, you can know the running status of the services
carried on this trail. This helps during the network maintenance when you need to update the
alarm information and take proper measures on time. When you view the current alarms of an
SDH trail, you can perform other operations for these alarms at the same time. For example,
synchronize, refresh, check, acknowledge and filter alarms.

Prerequisite
l To view the alarms, You must be an NM user with "network monitor" authority or
higher. To acknowledge, check, synchronize and delete alarms, You must be an NM user
with "network operator" authority or higher.
l The SDH trail must be created.
Procedure
Step 1 Choose Trail > SDH Trail Management from the Main Menu.
Step 2 In the Set Trail Browse Filter Conditions dialog box displayed, select or enter parameters and
set filter criteria. Click Filter All.
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.
Step 3 Optional: Select a trail on which there are alarms. Then, right-click in the Transmission Media
Layer Route window and then choose Display Alarm. If the NEs have alarms, each of the NE
icons is indicated with a specific alarm color. When you hold the cursor on any one of the NE
icons, alarm information of the NE is displayed.
Step 4 Select one or more trails. Click the Alarm and select Current Alarm.
NOTE
Click an alarm. The details of the alarm and the recommended handling are displayed in the pane below.
Step 5 Optional: To display the latest alarms, check the Display latest alarms check box.
NOTE
The function of the checked check box is equivalent to the automatic refresh function. Thus, when the
check box is checked, the Refresh button is grayed out.
Step 6 Optional: To check the alarms, select one or more alarms. Right-click alarms and choose Check
Alarms.
NOTE
When you check the alarm, you are comparing one or more uncleared alarms on the T2000 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 T2000. If the alarm does not exist in the NE, the alarm is cleared on the T2000.
Step 7 Optional: To acknowledge the alarms, select one or more alarms and click Acknowledge. In
the Acknowledge Alarms dialog box displayed, click Yes.
NOTE
Acknowledged and cleared alarms automatically change to history alarms.
Step 8 Optional: To delete the alarms, select one or more alarms and click Delete. In the Delete the
Alarms dialog box displayed, click Yes.
----End

7.4.14 Viewing History Alarms of an SDH Trail

By viewing history alarms of an SDH trail, you can learn history faults of the trail for reference
of operation and maintenance.
Prerequisite
l The SDH trail must be created.
Procedure
Step 2 In the Set Trail Browse Filter Condition dialog box displayed, set the filter criteria and click
Filter All. The trails are displayed in the list.
NOTE
already displayed.
Step 3 Select a trail. Click Alarm and choose History Alarm.

Step 4 In the History Alarms-[Custom] window, view history alarms of the specified SDH trail.
----End
7.4.15 Viewing Current Alarms of a WDM Trail

By querying current alarms of a WDM trail, you can learn about faults on this trail to perform
maintenance in a timely and effective manner.
Prerequisite
You must be an NM user with "network monitor" authority or higher.
Procedure
Step 1 Choose Trail > WDM Trail Management from the Main Menu.
Step 2 The Set Trail Browse Filter Conditions dialog box is displayed. Set the filter criteria and view
the desired trails in the trail list.
l If you need to filter all the trails, click Filter All.
l If you need to add to the list more trails that match the requirement, click Incremental
Filter.
l If you need to filter the trails in the list, click Secondary Filter.
Step 3 Select a desired trail, click Alarm, and choose Current Alarm from the drop-down menu.
The current alarms on this trail are displayed in the window.
Step 4 Perform maintenance according to the current alarms reported on this trail.
----End

7.4.16 Viewing History Alarms of a WDM Trail

By querying history alarms of a WDM trail, you can learn about history faults on this trail and
provide reference for maintenance of current faults.
Prerequisite
Procedure
Filter.
Step 3 Select a desired trail, click Alarm, and choose History Alarm from the drop-down menu.
The history alarms on this trail are displayed in the window.
Step 4 Learn about the history alarms reported on this trail to provide reference for maintenance of
current faults.
----End
7.4.17 Viewing Current Alarms of a Trunk Link

By viewing current alarms of a trunk link, you can query the running status of services that the
current trail carries. During the network maintenance, you need to update alarm information and
properly handle the alarms in time. When viewing the current alarms of the trunk link, you can
also synchronize, refresh, check, acknowledge and filter the alarms.
Prerequisite
l The trunk link must be created.
l To view alarms, You must be an NM user with "network monitor" authority or higher. To
acknowledge, check, synchronize and delete alarms, You must be an NM user with
"network operator" authority or higher.
Procedure
Step 1 Choose Trail > Trunk Link > Trunk Link Management from the Main Menu.
Step 2 In the Set Trunk Link browse filtering conditions window, select or enter parameters and set
filter criteria. Click Filter All.

NOTE
l Filter All refreshes and displays all trails that meet the filter criteria.
l Secondary Filter performs filtering on the trails that are already displayed according to the filter
criteria.
l Incremental Filter does not refresh the trail information that is already displayed. This function
displays the updated filter result below the existing trail information.
Step 3 Select one or more trails. Click Alarm and select Current Alarm from the drop-down list. The
window that is displayed shows the current alarms of all severity levels.
Step 4 Optional: Select one or more alarms and choose Check from the shortcut menu to check the
selected alarms.
NOTE
Step 5 Optional: Select an alarm. The detailed information and cause of the alarm are displayed in the
panes below.
Step 6 Optional: Select one or more alarms and click Acknowledge. The Acknowledge Alarms dialog
box is displayed. Click Yes. The Ack User, Ack Time and Ack Status fields display the
corresponding values of the selected alarms.
NOTE
Acknowledged and cleared alarms change to history alarms automatically.
----End
7.4.18 Viewing History Alarms of a Trunk Link

By viewing history alarms of a specified trunk link, you can learn history faults of the trail for
reference of operation and maintenance.
Prerequisite
l The trunk link must be created.
Procedure
Step 1 Choose Trail > Trunk Link > Trunk Link Management from the Main Menu.
Step 2 In the Set Trunk Link browse filtering conditions window, select or enter parameters and set
filter criteria. Click Filter All.
NOTE
criteria.

Step 3 Select one or more trails. Click Alarm and select History Alarm from the drop-down list. In
the window displayed, view the details of the history alarms of the specified trail.
----End
7.4.19 Viewing Current Alarms of an Ethernet Trail

By viewing current alarms of an Ethernet trail, you can query the running status of services that
the current trail carries. During the network maintenance, you need to update alarm information
and properly handle the alarms in time. When viewing the current alarms of the Ethernet trail,
you can also synchronize, refresh, check, acknowledge and filter the alarms.
Prerequisite
l The Ethernet trail must be created.
l To view alarms, You must be an NM user with "network monitor" authority or higher. To
acknowledge, check, synchronize and delete alarms, You must be an NM user with
"network operator" authority or higher.
Procedure
Step 1 Choose Trail > Ethernet Circuit > Ethernet Trail Management from the Main Menu.
Step 2 In the Set Trail Browse Filter Conditions window, select or enter parameters and set filter
criteria. Click Filter All.
NOTE
criteria.
Step 3 Select one or more trails. Click Alarm and select Current Alarm from the drop-down list. The
window that is displayed shows the current alarms of all severity levels.
Step 4 Optional: Select one or more alarms and choose Check from the shortcut menu to check the
selected alarms.
NOTE
Step 5 Optional: Select an alarm. The detailed information and cause of the alarm are displayed in the
panes below.
Step 6 Optional: Select one or more alarms and click Acknowledge. The Acknowledge Alarms dialog
box is displayed. Click Yes. The Ack User, Ack Time and Ack Status fields display the
corresponding values of the selected alarms.
NOTE
Acknowledged and cleared alarms change to history alarms automatically.
----End

7.4.20 Viewing History Alarms of an Ethernet Trail

By viewing history alarms of an Ethernet trail, you can learn history faults of the trail for
reference of the operation and maintenance.
Prerequisite
l The Ethernet trail must be created.
Procedure
Step 1 Choose Trail > Ethernet Circuit > Ethernet Trail Management from the Main Menu.
Step 2 In the Set Trail Browse Filter Conditions window, select or enter parameters and set filter
criteria. Click Filter All.
NOTE
criteria.
Step 3 Select one or more trails. Click Alarm and select History Alarm from the drop-down list. In
the window displayed, view the details of the history alarms of the specified trail.
----End
7.5 Handling an Alarm

When an alarm is raised, you need to take actions to handle it. You need to rectify the network
fault or the device fault to recover the network or device to its normal state.
7.5.1 Browsing Current Alarms

This section describes how to browse current alarms.
7.5.2 Viewing the Alarm Details
You can view the alarm details to know the alarm information. You can then take actions based
on the information.
7.5.3 Checking Alarms
When you check the alarm, you are comparing one or more uncleared alarms on the T2000 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 T2000. If the alarm does not exist in the NE, the alarm
is cleared on the T2000.
7.5.4 Acknowledging an Alarm
The function of alarm acknowledgement provides a method to identify whether an alarm is being
handled. By alarm acknowledgement, you can identify the alarms that are not handled so that
you can handle these alarms in time.
7.5.5 Position an Alarm on Topology Object

By locating an alarm, you can find the topology object that raises the alarm. The position of the
object is focused in the topology view.
7.5.6 Querying Device Maintenance Information
You can query device maintenance information to obtain the information on the device location
and the maintenance personnel. You can then notify the maintenance personnel if a device is
faulty.
7.5.7 Deleting Alarms
Alarms may be missing due to some faults. For example, when the T2000 fails to communicate
with the device, the clearance alarms reported by the device may be missing. For maintenance
purposes, the T2000 allows you to delete the alarms manually.
7.5.8 Example of Alarm Handling
This section provides an example on how to handle the alarm of insufficient disk space. It shows
the procedure and method for handling alarms. It helps you to know the basic procedure and
operations of alarm handling.
7.5.1 Browsing Current Alarms

This section describes how to browse current alarms.
Prerequisite
To perform the browse operation, you must be an NMS user with the "Fault Maintainer" authority
or higher. To perform the acknowledgement or clearance operation, you must be an NMS user
with the "Fault Operator" authority or higher.
Procedure
Step 1 Choose Fault > Browse Current Alarm from the main menu.
Step 2 In the Filter dialog box, set the filter conditions. Click OK.
NOTE
If the startup template for browsing the current alarms is set, the Filter dialog box is not displayed. The alarms
that meet the filter conditions are displayed.
Step 3 In the query result table, click a column heading to sort the results.
NOTE
l If you click Alarm Source or Alarm Source Type, the NEs are grouped by NE ID. If you click a different
field, the alarm records are sorted in alphabetical order.
l If you click , the fields are sorted in ascending order. If you click , the fields are sorted in descending
order. Switch between and to switch between the ascending and descending orders.
Step 4 In the query result table, right-click an alarm and do as follows:

l Choose Select All to select all the records in the query result table.
l Choose Correlative Alarms to query correlative alarms.
l Choose Remark to set the remarks on the alarm.
l Choose Acknowledge to acknowledge the alarm.
– If the alarm is unacknowledged and uncleared, the alarm status becomes
Ack&Uncleared.
– If the alarm is unacknowledged and cleared, it is moved to the history alarm database.

l Choose Locating to Topo Object to locate the topology object that raises the alarm.
Step 5 Optional: Choose Display latest alarms to query new alarms in real time.
NOTE
If you clear Display latest alarms, pay attention to the following:

l If new alarms that meet the filter conditions are generated, the Refresh button turns to red. Click Refresh
to update records.
l You can click a field in the table head to sort alarm records. The effect of this operation is the same with
that of refreshment.
l The status change in alarm acknowledgement and clearance does not cause that the Refresh button becomes
red. This avoids that the Refresh button is in red for a long time.
Step 6 In the query result table, choose an alarm, and do as follows:

l Click Filter by Template to create, open, or save a browse template.
l Click Filter to set filter conditions to query current alarms.
l Click Refresh to query current alarms again based on the current filter condition.
l Click Acknowledge to acknowledge the alarm if it is unacknowledged.
l Click Delete to clear the alarm if it is not cleared.
l Click Print to print the alarm information.
l Click Save As to save the alarm information as a file.
----End
7.5.2 Viewing the Alarm Details

You can view the alarm details to know the alarm information. You can then take actions based
on the information.
Prerequisite
Procedure
Step 1 Choose Fault > Browse Current Alarm from the main menu.
NOTE
Step 3 Select an alarm in the alarm browse window, viewing the alarm details at the lower left part of
the alarm list.
----End
7.5.3 Checking Alarms

When you check the alarm, you are comparing one or more uncleared alarms on the T2000 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 T2000. If the alarm does not exist in the NE, the alarm
is cleared on the T2000.

Prerequisite
Procedure
Step 2 In the Current Alarms window, select one or more alarms and click Check.
----End
7.5.4 Acknowledging an Alarm

The function of alarm acknowledgement provides a method to identify whether an alarm is being
handled. By alarm acknowledgement, you can identify the alarms that are not handled so that
you can handle these alarms in time.
Prerequisite
Procedure
Step 1 Choose Fault > Browse Current Alarm.
NOTE
Step 3 In the Current Alarm window, right-click an alarm and choose Acknowledge .
Step 4 In the Acknowledge Alarms dialog box, click Yes.
----End
Result
l A progress bar indicates the progress if you acknowledge two or more alarms at a time.
l When the T2000 receives the command for acknowledging the alarm, the alarm status
becomes Ack. The T2000 records when the alarm is acknowledged and who performs this
task. It also refreshes the information in all the windows on the client and updates the data
of the alarm panel and alarm box.
l If an alarm is acknowledged and cleared, it is dumped to the history database.
7.5.5 Position an Alarm on Topology Object

By locating an alarm, you can find the topology object that raises the alarm. The position of the
object is focused in the topology view.
Prerequisite

Context
l All the alarm browse windows provide the access of locating alarms.
l In the Root Alarms and Correlative Alarms dialog boxes, you can use the shortcut menu
to locate the topology object that generates the root or correlative alarm.
l You can position an alarm on a topology node or an object on the panel.
l If the object that raises the alarm is deleted, the Locating to Topo Object menu is disabled.
Procedure
Step 1 In the alarm browse window, right-click an alarm and choose Locating to Topo Object.
After the alarm is located, the object that raises the alarm is focused in the topology view.
----End
7.5.6 Querying Device Maintenance Information

You can query device maintenance information to obtain the information on the device location
and the maintenance personnel. You can then notify the maintenance personnel if a device is
faulty.
Prerequisite
Procedure
Step 1 In the alarm browse window, right-click an alarm and choose Locating to Topo Object.
The topology object that raises the alarm is focused.

Step 2 Choose System > Device Maintenance Info from the main menu.
Step 3 In the Device Maintenance Info window, double-click the records in the maintenance
information list or click Display to view the device maintenance information.
NOTE
If you do not select any device in the topology view and choose System > Device Maintenance
Information, the maintenance information on all the devices is displayed.
----End
7.5.7 Deleting Alarms

Alarms may be missing due to some faults. For example, when the T2000 fails to communicate
with the device, the clearance alarms reported by the device may be missing. For maintenance
purposes, the T2000 allows you to delete the alarms manually.
Prerequisite
Context
You cannot roll back the operation of deleting an alarm.
Procedure
Step 1 In the Current Alarms window, select an alarm and click Delete.
Step 2 In the Delete the Alarms dialog box, click Yes.
----End

Result
The T2000 dumps the alarm to the history database and refreshes the information in all the
windows on the client and updates the data of the alarm panel and alarm box.
7.5.8 Example of Alarm Handling

This section provides an example on how to handle the alarm of insufficient disk space. It shows
the procedure and method for handling alarms. It helps you to know the basic procedure and
operations of alarm handling.
Background
The T2000 reports an alarm of insufficient disk space.
Operation Guide
Based on the Fault Handling Procedure, do as follows:
1. Receive the alarm notification.
On the client, choose Fault > Browse Current Alarm to open the current alarm window.
An uncleared hard disk alarm of the T2000 is found. The alarm indicates that the T2000
server has insufficient disk space.
2. View the alarm details.
Select this alarm record, and then browse the details and handling suggestions of the alarm
at the bottom of the browse window.
3. Acknowledge the alarm
To avoid others handling the same alarm, you need to acknowledge it. When you
acknowledge the alarm, it indicates that the alarm is being processed. Right-click the alarm
and choose Acknowledge.
4. Work out the alarm handling method.
According to the handling suggestion and operation status of the T2000, you can delete the
redundant files and back up the dump data on another disk to solve the problem of
insufficient disk space.
5. Remove the relevant fault.
Delete the redundant files of the T2000. Back up the dump files from $IMAPROOT/
server/dump to other disk. Then delete the source dump data. The T2000 server then
obtains more available disk space.
6. Check the handling results.
The alarm is dumped from the current alarm database to the history alarm database. In the
Current Alarms window, the alarm is disappeared. You can find the cleared alarm in the
History Alarms window.
7.6 Setting the Alarm Auto Processing

You can set an auto processing policy to enable the T2000 to process the alarms that match the
preset conditions. This helps to improve the work efficiency.
7.6.1 Setting the Alarm Auto Acknowledgement

The T2000 can acknowledge the cleared alarms immediately or periodically. Therefore, you do
not need to acknowledge the cleared alarms manually.
7.6.1 Setting the Alarm Auto Acknowledgement

The T2000 can acknowledge the cleared alarms immediately or periodically. Therefore, you do
not need to acknowledge the cleared alarms manually.
Prerequisite
Context
l The auto acknowledgement applies to only the cleared alarms.
l The time acknowledgement starts at 01:00 every day.
Procedure
Step 1 Choose Fault > Settings > Auto Acknowledgement from the Main Menu.
Step 2 In the Auto Acknowledgement dialog box, set the auto acknowledgement.
l Set the immediate acknowledgement.
Select Acknowledge Immediately After an Alarm Is Cleared and specify the alarm
severity.
l Set the time acknowledgement.
Select Acknowledge in * Days After an Alarm Is Cleared and specify the time and the
alarm severity.
NOTE
The immediate acknowledgement applies to only the alarms that are cleared after the immediate
acknowledgement configuration, but it does not apply to those alarms that are cleared before the
configuration.
Step 3 Click OK.
----End
Result
The alarms that match the preset conditions are automatically acknowledged. The user who
acknowledges the alarms is recorded as NMS.


Prerequisite
Procedure
Step 1 Choose Fault > Settings > Auto Synchronization from the Main Menu.
Step 2 In the Auto Synchronization dialog box, set the alarm synchronization parameters.
l When Starting the NM indicates that the T2000 automatically synchronizes the alarms
with those on all the NEs when it is started.
l When communication is lost and recovers indicates that the T2000 automatically
synchronizes the alarms with those on a specific NE when it resumes the communication
with the NE.
l LCT User Logs Out indicates that the T2000 automatically synchronizes the alarms with
those on a specific NE when the LCT user logs out.
Step 3 Click OK.
----End
7.7 Suppressing Alarms

You can suppress alarms, so that the T2000 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.7.1 Suppressing NE Alarms
To facilitate management, you can suppress some alarms of the specified NE so that the
T2000 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.7.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 T2000. You can suppress the unimportant
alarms.
7.7.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.7.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.7.1 Suppressing NE Alarms

To facilitate management, you can suppress some alarms of the specified NE so that the
T2000 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
Step 1 In the NE Explorer, click an NE and choose Alarm > Alarm Suppression from the Function
Tree.
Step 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.
Step 3 Click Apply.

The Operation Result dialog box is displayed.
Step 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 T2000 does not clear the reported alarms, until an alarm
cleared notification is received.
7.7.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 T2000. You can suppress the unimportant
alarms.
Prerequisite
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > Alarm Suppression from the Function
Tree.
Step 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.
Step 3 Set the Status of the alarms that need to be suppressed to Suppressed.
Click Apply and the Operation Result dialog box is displayed.
Step 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.7.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 You must be an NM user with the "NE operator" authority or higher.
l Cross-connections must be created on the ATM board (For example: the AL1 board on the
4.0 equipment).
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Alarm > ATM Connection Alarm
Suppression from the Function Tree.
Step 2 Click Query to query the alarm information from the NE.
Step 3 Click Select Connection. The Select Connection dialog box is displayed.
Step 4 In the Select Connection dialog box, select a connection and click OK.
Step 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.
Step 6 Click Apply.
----End
Result
l After an alarm is suppressed, the board does not monitor the alarm.
7.7.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
Step 1 Click the networkwide maintenance status icon on the toolbar, and the Networkwide
Maintenance Status dialog box is displayed.
Step 2 Choose Maintenance Status > Alarm Suppression and 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.
Step 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.8 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.8.1 Setting Alarm Reversion for a Specified Port
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.
7.8.2 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.8.3 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.8.1 Setting Alarm Reversion for a Specified Port

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.
Prerequisite
Context
If you set alarm reversion for a port, the status of all alarms on this port is displayed as "no alarm"
even though the alarms occur.
Procedure
Step 1 In the NE Explorer, select the NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
Step 2 Set Reversion Mode to Automatic Reversion or Manual Reversion. Click Apply.
NOTE
After the port alarm is cleared, if you set the Reversion Mode to Automatic Reversion, 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 Reversion, 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.

Step 3 In the NE Explorer, select a board and choose Alarm > Alarm Reversion from the Function
Tree.
Step 4 In the Alarm Reversion, set the Reversion Status to Enabled.
Step 5 Click Apply. The Operation Result dialog box is displayed.
Step 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.8.2 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 The trail must be activated.
Context
If you set alarm reversion for a trail, all alarms of this trail are reverted. You cannot set alarm
reversion for a single alarm of the trail.
Procedure
All. The trails are displayed in the list.
NOTE
already displayed.
Step 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.
Step 4 In the Alarm Reversion dialog box displayed, set Reversion Status of the trail to Enabled.

Step 5 Click Apply. In the Operation Result dialog box displayed, click Close.
----End
7.8.3 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
Step 2 Choose Maintenance Status > Alarm Reversion and 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.
Step 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.9 Filtering Alarms Raised on T2000

You can filter unimportant T2000 alarms so that the T2000 does not monitor these alarms. This
operation helps fault location.
Prerequisite
Procedure
Step 1 Choose Fault > Settings > NMS Alarm/Event Filter from the Main Menu.
Step 2 Change the filter status of the T2000 alarms that you want to filter, click Apply.
----End
7.10 Filtering Alarms Raised on NE

After an NE reports an alarm to the T2000, the T2000 determines whether to display and save
the alarm according to the alarm filtering status. You can use this function to filter out the
negligible alarms when the T2000 manages multiple NEs.
Prerequisite
Context
Alarms are filtered based on their original properties (the properties before redefinition).
Therefore, if you set the redefinition and filter for an alarm, the filter settings take effect before
the redefinition settings take effect.
Procedure
Step 1 Choose Fault > Settings > NE Alarm/Event Filter from the Main Menu.
Step 2 Click New in the NE Alarm/Event Filter window. An alarm or event filter record is created.
Step 3 Double-click Filter Condition, and specify the filter condition in the Filter Condition dialog
box.
Step 4 Set Start Time, End Time, Alarm Duration (Second) and Remarks.

Step 5 Click Apply.
----End
7.11 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 T2000. You can disable the automatic reporting for unimportant
alarms to reduce the impact on the T2000 performance. A large volume of alarm information
affects the performance of the T2000.
7.11.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 T2000
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.11.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.11.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.
Procedure
Step 1 Choose Fault > Settings > Alarm Attribute Template from the Main Menu.
The Alarm Attribute Template window is displayed.
Step 2 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.
Step 3 Check the Alarm Auto-Report check box in the Alarm Attribute pane.
Step 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.

Step 5 Click Close.
----End
7.11.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.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > Alarm Severity and Auto
Reporting from the Function Tree.
Step 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.
Step 3 Click Close.
----End
7.12 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
Step 1 In the NE Explorer, select a board and choose Configuration > Set TUG Structure from the
Function Tree.
Step 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.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
----End
7.13 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
Step 1 In the NE Explorer, select a board and choose Configuration > Set TUG Structure from the
Function Tree.
Step 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.
Step 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.
Step 6 Click Close.
Step 7 In the NE Explorer, select a line board and choose Alarm > Lower Order Path Alarm from
the Function Tree.
Step 8 Select Level and double-click Type of Monitored Alarm to set the alarm monitoring type.
Click OK.
----End
7.14 Setting the Insertion Mode for Channels Not

Configured with Services
On the T2000, you can set the insertion mode of alarms in the channel according to the
networking and service requirements.
Prerequisite

Procedure
Step 1 In the NE Explorer, select an NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
Step 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.15 Setting Audible and Visual Alarm Notification

The T2000 can select different sounds and colors for the alarms and abnormal events of different
severities based on customized settings, to facilitate maintenance.
7.15.1 Setting Alarm Sounds
You can set the alarm sounds for different severities of alarms. When the T2000 receives an
alarm, it plays the sound corresponding to the severity of the alarm to notify you of the alarm.
7.15.3 Setting the Alarm Panel Style
You can set the style of the alarm panel.
7.15.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 T2000.
7.15.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 T2000.
7.15.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
T2000, 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 T2000.
7.15.1 Setting Alarm Sounds

You can set the alarm sounds for different severities of alarms. When the T2000 receives an
alarm, it plays the sound corresponding to the severity of the alarm to notify you of the alarm.
Prerequisite
l You must be an NMS user with the "Fault Watcher" authority or higher.
l When modifying the alarm sound settings, you need to stop the current alarm sound,
because you need to initialize the sound.

Context
l The alarm sound settings are effective for the only local client.
l You can click Restore Defaults to restore the alarm sound to the default values.
l Do not stop the sounds of all severities, because you may miss some critical or major alarms
and delay the alarm handling.
l The alarm prompt tone has a higher priority than the event prompt tone.
l Sound playing policy: If the alarm priority corresponding to the current alarm sound is
higher than that of the new one, no action needs to be taken. If the current alarm priority is
lower than or equal to the new alarm priority, stop the current alarm sound and play the
new alarm sound.
l When an alarm sound is reset, the sound is not played again according to the alarm statistics
but played when a new alarm is received.
l After an alarm sound is set, check whether the system is set to silent, if the sound is not
displayed when an alarm is generated.
Procedure
Step 2 In the Preferences dialog box, click the Sound tab.
Step 3 On the Sound tab, set the parameters for the sound corresponding to the related alarm severity.
NOTE
l If you set the playing duration to -1, the alarm sound will last until you stop the sound or clear the alarm.
l To set alarm sounds by alarm name, click Advanced. In the Advanced dialog box, on the Set by Name tab,
select alarms, select an audio file, and set the playing duration. Then click OK.
Step 4 In the Preferences dialog box, click OK.
----End

Prerequisite

Procedure
Step 2 In the Preferences dialog box, click the Color tab.
Step 3 Set the colors for Critical Alarm, Major Alarm, Minor Alarm, and Warning as required.
Step 4 Click OK.
----End
7.15.3 Setting the Alarm Panel Style

You can set the style of the alarm panel.
Prerequisite
Context
The settings are effective for only the current client.
Procedure
Step 2 In the Preferences dialog box, click the Local Fault Settings tab.

Step 3 On the Local Fault Settings tab, set the display mode of the alarm panel.
NOTE
l Display alarm panel at startup: The alarm panel is displayed when the client is started.
l Display the alarm panel when a new alarm is reported: The client displays the alarm panel automatically
when receiving a new alarm.
Step 4 Click OK.
----End
7.15.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 T2000.
Prerequisite

Context
l For the T2000 to control the alarm box, you need to correctly set the communication
parameters of the alarm box in the Communication Parameters tab.
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 alarm, the alarm box beeps for a fixed time period (one minute) and
stops. It can also be manually stopped.
Procedure
Step 1 Choose Fault > Alarm Box from the Main Menu.
Step 2 Click the Communication Parameters tab and properly set the parameters.
Step 3 Click the Audio-Visual Indication tab. Enable or disable audible and visual indications for the
alarm of each severity level as required.
Step 4 Click OK.
----End
7.15.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 T2000.
Prerequisite
Procedure
Step 1 Right-click an NE and choose Clear Alarm Indication from the shortcut menu.
The Operation Result dialog box is displayed.
Step 2 Click Close.
----End
7.15.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
T2000, 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 T2000.
Prerequisite
Applies to the OptiX OSN 9500.

Procedure
Tree.
Step 2 Click Query to query the settings of audible and visual alarm notifications of the NE from the
NE side.
Step 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.
Step 4 Click Apply. The Confirm dialog box is displayed asking you whether to proceed.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful.
Step 6 Click Close.
----End
7.16 Setting Alarm Remote Notification

This function helps the maintenance engineer to learn the running status of the network at any
time. When the T2000 detects that an relevant alarm is raised, the alarm remote notification
function enables the T2000 to automatically send the alarm information to the preset receive
terminal. Currently, the T2000 can only forward the alarm information to users by way of short
message and EMAIL.
7.16.1 Forwarding Alarms to Email Automatically
You can set parameters for alarm notifications so that when an alarm is generated, the T2000
automatically sends the alarm information to the email box of the engineer concerned. In this
way, the engineer can know the network running status at any time.
7.16.2 Forwarding Alarm to Mobile Phone Automatically
You can set parameters for alarm notification so that when an alarm is generated, the T2000
automatically sends the alarm information to the mobile phone of the engineer concerned,
through a wireless modem or SMS gateway. In this way, the engineer can learn the network
running status at any time.
7.16.1 Forwarding Alarms to Email Automatically

You can set parameters for alarm notifications so that when an alarm is generated, the T2000
automatically sends the alarm information to the email box of the engineer concerned. In this
way, the engineer can know the network running status at any time.
Prerequisite
l You must be an NM user with "NM monitor" authority or higher.

Context
l You can set to forward alarms to an email box, a mobile phone, or both.
l You can also set to forward alarms to several email boxes or mobile phones.
Procedure
Step 1 Choose Fault > Settings > Remote Notification from the Main Menu.
Step 2 In the Remote Notification window, click New to add a new alarm notification.
Step 3 Set the Remote Notification Condition and select an alarm for which you want to set remote
notification.
NOTE
l The conditions in the Basic Settings and Alarm Source tabs work together. That is, an alarm can be
forwarded only when it meets the conditions specified in the Basic Settings and Alarm Source tabs.
l In the Basic Settings tab, the Alarm name, Severity, and Type also work together.
Step 4 Set parameters including the Email, Time Zone, and Remark.
NOTE
l You can set a mobile phone number, so that the alarm is also forwarded to the mobile phone.
l If you want to forward the alarm to several email boxes, separate email addresses by ;.
Step 5 Click Communication Settings to set the communication parameters of remote notification,
and click OK.
NOTE
After setting, click Test and select the test email address to check whether the communication is normal.
Step 6 Optional: Click Delay Settings to set the delay time of remote notification as required. This
avoids irrelevant alarm notification information.
Step 7 Click Apply.
----End
7.16.2 Forwarding Alarm to Mobile Phone Automatically

You can set parameters for alarm notification so that when an alarm is generated, the T2000
automatically sends the alarm information to the mobile phone of the engineer concerned,
through a wireless modem or SMS gateway. In this way, the engineer can learn the network
running status at any time.
Prerequisite
Context
l You can set to forward alarms to an email box, a mobile phone, or both.
l You can also set to forward alarms to several mobile phones.

Procedure
Step 1 Choose Fault > Settings > Remote Notification from the Main Menu.
Step 2 In the Remote Notification window, click New to add a new alarm notification.
Step 3 Set the Remote Notification Condition and select an alarm for which you want to set remote
notification.
NOTE
l The conditions in the Basic Settings and Alarm Source tabs work together. That is, an alarm can be
forwarded only when it meets the conditions specified in the Basic Settings and Alarm Source tabs.
l In the Basic Settings tab, the Alarm name, Severity, and Type also work together.
Step 4 Set parameters including the Mobile Phone, Time Zone, and Remarks.
NOTE
l You can set the email address, so that the alarm is forwarded to the email box.
l If you want to forward the alarm to several mobile phones, separate the phone numbers by ;.
Step 5 Click Communication Settings to set the communication parameters of remote notification,
and click OK.
NOTE
After setting, click Test and select the test mobile phone to check whether the communication is normal.
Step 6 Click Delay Settings to set the delay time of remote notification as required. This avoids
irrelevant alarm notification information.
Step 7 Click Apply.
----End
7.17 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.17.1 Changing the T2000 Alarm Severity
You can set the alarm severity levels for the T2000 alarms as required to improve the efficiency
of alarm monitoring.
7.17.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.17.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.17.1 Changing the T2000 Alarm Severity

You can set the alarm severity levels for the T2000 alarms as required to improve the efficiency
of alarm monitoring.

Prerequisite
Procedure
Step 1 Choose Fault > Settings > Redefine Alarm/Event from the Main Menu.
Step 2 Click New to create an alarm redefinition.
Step 3 Double-click the Alarm/Event field. The Select Alarm/Event dialog box is displayed.
Step 4 Select a suitable T2000 alarm and click OK.
Step 5 Change the Severity for the T2000 alarm and click Apply.
----End
7.17.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 The alarm attribute template that has the alarm severity configured as required must be
customized first.
Procedure
Step 1 Choose Fault > Settings > Alarm Attribute Template from the Main Menu. The Alarm
Attribute Template window is displayed.
Step 2 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.
Step 3 Check the Alarm Severity check box in the Alarm Attribute pane.
Step 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.
Step 5 Click Close.
----End
7.17.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
Step 1 In the NE Explorer, select a board and choose Alarm > Alarm Severity and Auto Reporting
from the Function Tree.
Step 2 Adjust the Severity of the alarm you want.
Step 3 Optional: To restore to the default settings, click Default.
Step 5 Click Close.
----End
7.18 Analyzing the Root Alarm of a Fault

Due to the hierarchical relation of the service signals, normally, when alarms occur on a higher
order signal, some derived alarms occur on the lower order signals that are demultiplexed from
higher order signals. As for the WDM trails, some alarms raised from the upstream equipment
can generate some other alarms on downstream equipment. The T2000 can analyze the alarm
events. It displays or reports the most critical root alarms, and suppresses the alarms derived
from the root alarms according to the alarm correlation. The T2000 supports both the alarm
correlation analysis and the automatic alarm correlation analysis when analyzing the root alarms.
7.18.1 Analyzing Root Alarms Automatically

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 root alarms enables the
T2000 to analyze the alarms that are reported to the T2000 from the NEs. According to the alarm
correlation analysis rules, the T2000 adjusts the severity levels of the root alarms and correlative
alarms. Thus, you can focus on the root alarms or important services.
7.18.2 Performing Alarm Correlation Analysis
The alarm correlation analysis enables the T2000 to analyze all alarms based on the alarm
correlation rules to filter out the root alarms. The alarm correlation analysis, however, does not
suppress any alarm. This function helps the maintenance personnel to focus on the root alarms
and important services so that they can quickly locate the faults.
7.18.1 Analyzing Root Alarms Automatically

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 root alarms enables the
T2000 to analyze the alarms that are reported to the T2000 from the NEs. According to the alarm
correlation analysis rules, the T2000 adjusts the severity levels of the root alarms and correlative
alarms. Thus, you can focus on the root alarms or important services.
Prerequisite
Procedure
Step 1 Choose Fault > Settings > Alarm Correlation Analysis from the Main Menu.

Step 2 Click Create to add a new rule.

NOTE
You can also modify an existing alarm correlation analysis rule.
Step 3 Set the Alarm 1, Alarm 2, Conditions, and Action for the new rule.
Step 4 Select Enable Automatic Alarm Correlation Analysis and click Apply. The Operation
Result dialog box is displayed.
Step 5 Click Close.
Step 6 Optional: Choose Fault > Browse Current Alarm from the Main Menu. Right-click a root
alarm and choose Correlative Alarms from the shortcut menu to display the correlative alarms
suppressed by this root alarm.
----End
7.18.2 Performing Alarm Correlation Analysis

The alarm correlation analysis enables the T2000 to analyze all alarms based on the alarm
correlation rules to filter out the root alarms. The alarm correlation analysis, however, does not
suppress any alarm. This function helps the maintenance personnel to focus on the root alarms
and important services so that they can quickly locate the faults.
Prerequisite
Context
Note that this function filters out the correlative alarms. It cannot increase the severity levels of
the correlative alarms.
Procedure
Step 1 Choose Fault > Settings > Alarm Correlation Analysis from the Main Menu.
Step 2 Click Create to add a new rule.

NOTE
You can also modify an existing alarm correlation analysis rule.
Step 3 Set the Alarm 1, Alarm 2, Conditions, and Action for the new rule.
Step 4 Click Apply.
Step 6 In the Filter dialog box, set filter criteria and click OK.
Step 7 Click Correlation Analysis.

The Correlation Analysis for Current Alarm dialog box is displayed.
Step 8 Select the corresponding time period and click OK. The Confirm dialog box is displayed.
Step 9 Click OK to obtain the root alarm information.
----End

7.19 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.19.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.19.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 T2000 detects a specific
QoS-affecting event (for example, the TIM_P), the T2000 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.19.3 Enabling UNEQ Insertion for a Specified Path
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.
7.19.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
Step 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.
Step 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.
Step 3 Click Apply. The Warning dialog box is displayed.
Step 5 Click Close.
----End

7.19.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 T2000 detects a specific
QoS-affecting event (for example, the TIM_P), the T2000 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
Step 1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > AIS Insertion from the
Function Tree.
Step 2 Select Port/Path and set the event you concern to Enabled.
Step 3 Click Apply.

The Operation Result is displayed.
Step 4 Click Close.
----End
7.19.3 Enabling UNEQ Insertion for a Specified Path

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.
Prerequisite
l Applies to the SDH and RTN equipment. The PDH tributary board must be created.
Context
NOTE
This operation may affect services.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > UNEQ Insertion
Switch from the Function Tree.

Step 2 Click Query to query the UNEQ insertion status of each Port/Path from the NE.
Step 3 Set the UNEQ insertion switch for each Port/Path as required.
NOTE
The UNEQ has the two switches, LOS and Path Not Used.
Step 4 Click Apply.
----End
7.20 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.20.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.20.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.20.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.20.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
Step 1 In the NE Explorer, select a board and choose Alarm > Alarm Insertion from the Function
Tree.
Step 2 Select a path from Monitored Object to insert an alarm.
Step 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.
Step 4 Repeat Steps 2 through 3 to inset more alarms to different paths.
Step 5 Optional: To stop the alarm insertion, select one or more alarms from the Inserted Alarm
List pane, and click Clear.
----End
7.20.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
Procedure
The Set Trail Browse Filter Condition dialog box is displayed.
Step 2 In the Set Trail Browse Filter Condition dialog box displayed, set the filter criteria and click
Filter All. The trails are displayed in the list.
NOTE
already displayed.
Step 3 Select a VC4 trail or VC4 server trail. Click Maintenance and choose Alarm Insertion from
the drop-down menu.
Step 4 In the Alarm Insertion dialog box displayed, set the value of AIS Alarm Insertion or RDI
Alarm Insertion to Insert.
----End
7.20.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
Step 2 Choose Maintenance Status > Alarm Insertion and 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.
Step 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.21 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
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > WDM Interface from the
Function Tree.
Step 2 Click the Overhead Byte tab.
Step 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.
Step 4 Set AIS Insertion in the ODU Layer, LCK Insertion in the ODU Layer and OCI Insertion
in the ODU Layer as required.
Step 5 Click Apply.
----End
7.22 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.22.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.22.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.22.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 T2000 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.22.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.22.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.
Step 2 Click Query to query the alarm saving mode of the NE from the NE.
Step 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.
Step 4 Click Apply.
----End
7.22.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 T2000 records only the root alarm while
suppresses the alarms generated by the root alarm.

l Disabled: When alarms are raised from an NE, the T2000 records all the alarms, including
the root alarm and correlative alarms. By default NEs use this mode.
Procedure
Tree.
Step 2 Click Query to query the enabling status of the NE alarm correlation suppression from the NE.
Step 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.
Step 4 Click Apply.
----End
7.22.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 T2000 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.
Step 2 Click the Alarm Correlation Rules tab and query the NE alarm correlation rules from the NE.
Step 3 Click Query and the result is displayed.
----End
7.22.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.
Step 2 Click Query to query the alarm delay status of the NE from the NE side.
Step 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.
Step 4 Click Apply.
----End
7.23 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
Step 1 In the NE Explorer, select a line board and choose Alarm > Lower Order Path Alarm from
the Function Tree.
Step 2 Click Query to query the alarm monitoring status of the lower order paths from the NE.
Step 3 Select Port and VC4.
Step 4 Set whether to monitor the alarms on the VC3-1, VC3-2 and VC3-3 path.

Step 5 Set Monitor Status for each VC12 path.
Step 6 Click Apply.
----End
7.24 Dumping Alarms

The alarm data should be dumped in time to avoid overflow of alarm data or damage. You can
either manually dump the alarm data or set the alarm dumping conditions so that the T2000
automatically dumps the data. There are two types of automatic dumping, which are overflow-
triggered dumping and scheduled dumping.
7.24.1 Dumping Alarms Manually
By manually dumping alarms, you can save the history alarm data, which is recorded On the
T2000 to the specified directory at any time. Thus, you can view the history alarm data more
easily. The number of records in the databases is reduced, and the running speed of the system
is increased.
7.24.2 Dumping Alarms Automatically
By automatically dumping the alarm data, you can save the history alarm data, which is recorded
on the T2000 to the specified directory at any time. Thus, you can view the history alarm data
more easily. In this way, the number of the records in the databases is reduced, and the running
speed of the system is increased. There are two types of automatic dump, which are the overflow
dump and periodic dump.

is increased.
Prerequisite
Procedure
Step 1 Choose System > Database > Dump Manually from the Main Menu.
Step 2 Select the Alarm Data and specify a suitable File type.
Step 3 Select the Start time and End time, and specify the alarm generation time.
Step 4 Click Dump to manually dump the alarm data.
----End
Result
The dumped alarms are saved as a file in the specified directory, but not displayed in the History
Alarms window. To view the dumped alarms, you can collect the dumped alarm data by using
the network management system maintenance tool and then open the collected data by using the
text editor.


Prerequisite
Context
You can use Overflow Dump or Periodic Dump to automatically dump the data.
l If you select the overflow dump mode, the T2000 automatically dumps some data to the
specified path when the data exceeds the threshold.
l If you select the periodic dump mode, the T2000 periodically dumps the data to the specified
path.
l Overflow dump and periodic dump can work together. In this case, the T2000 dumps the
data or log according to the settings of overflow dump and periodic dump.
Procedure
Step 2 Select the Alarm Data, and set the parameters of overflow dump or periodic dump.

Step 3 Set the Dump mode, File type, and Dump to (path).
NOTE
Step 4 Click OK.
----End
Result
text editor.
7.25 Deleting History Alarms

Deleting history alarms is to dump the history alarms from the database and save them as a file.
The deleted alarms are not displayed in the History Alarms window. For details, see 7.24.1
Dumping Alarms Manually.

7.26 Diagnosing Faults

The T2000 provides a wizard for fault diagnosis. In daily maintenance, the engineer can create
fault diagnosis rules. When an alarm is generated, the engineer can locate the fault by using the
fault diagnosis wizard.
7.26.1 Creating Fault Diagnosis Rules
Fault diagnosis rules are helpful in quick fault location. The network maintenance engineers can
accumulate and share experience by creating fault diagnosis rules.
7.26.2 Starting the Fault Diagnosis Wizard
When an alarm (for which the relevant diagnosis rule is created) is raised on the equipment, the
maintenance engineer can use the fault diagnosis wizard on the T2000 to locate and remove the
fault.
7.26.1 Creating Fault Diagnosis Rules

Fault diagnosis rules are helpful in quick fault location. The network maintenance engineers can
accumulate and share experience by creating fault diagnosis rules.
Prerequisite
Context
Some common fault diagnosis rules are pre-set in the T2000, such as R_LOS, TU_AIS, HP_TIM
and B1_EXC.
Procedure
Step 1 Choose Fault > Settings > Set Fault Diagnosis Rules from the Main Menu.
Step 2 Right-click the Fault Diagnosis Rules and choose Add Rules from the shortcut menu. The
Create Fault Diagnosis Rules dialog box is displayed.
Step 3 Select an alarm for which you want to add the diagnosis rule and click OK. A new rule entry is
added.
Step 4 Right-click the new rule and choose Add Steps from the shortcut menu. The Create Diagnosis
Steps dialog box is displayed.
Step 5 Set the Alarm Causes, Diagnosis Method and Processing Method. Click OK.
Step 6 Click Apply.
Step 7 Optional: You can right-click a step entry and choose Modify from the shortcut menu to modify
the original contents as required.
----End
7.26.2 Starting the Fault Diagnosis Wizard

When an alarm (for which the relevant diagnosis rule is created) is raised on the equipment, the
maintenance engineer can use the fault diagnosis wizard on the T2000 to locate and remove the
fault.

Prerequisite
l The fault diagnosis rules must be created.
Context
l If the selected alarm does not have a relevant fault diagnosis rule, a message appears
indicating that the wizard cannot be started.
l If the fault diagnosis wizard is ever used, the handling method of the previous time is
prompted, and then you can click Diagnose Again to locate the fault.
Procedure
Step 2 In the Filter dialog box, set filter criteria and click OK.
Step 3 Right-click an alarm in the alarm list and choose Fault Diagnosis from the shortcut menu. The
Fault Diagnosis dialog box is displayed.
Step 4 Select the probable cause of the fault according to the actual situation. If you cannot decide
which cause is the most possible, then select the first cause.
Step 5 Click Next. The wizard displays the corresponding diagnosis method.
Step 6 Follow the diagnosis method to locate the fault. If successful, click Next to remove the fault by
following the suggestions in the handling method.
Step 7 If fault location fails, click Back to re-select a cause until you locate the fault successfully or
until you have tried all the causes.
Step 8 Click Clear or Cancel to exit the wizard.
----End
7.27 Configuring the Suppression of Power Status Alarm

During the operation, if the cabinet is not configured with three subracks or if the two power
supplies are not accessed completely, the corresponding tributary power reports the power status
alarm. If you are sure that the current configuration is correct, suppress the power status alarm.
Prerequisite
Applies to OptiX BWS 1600G and OptiX BWS 1600S.
The PMU board must be installed correctly.
It is not applicable to the OLA subrack with independent power system.t is not applicable to the
OLA subrack with independent power system.

Context
CAUTION
If a subrack is to be added or the two power supplies are to be accessed completely in a future
expansion, cancel the suppression setting and ensure that the power status is under control.
Procedure
Step 1 In the NE Explorer, select the PMU board and choose Alarm > Alarm Suppression in the
Function Tree.
Step 2 Refer to Table 7-7. Select the power output to be enabled with alarm suppression from the drop-
down list of Monitored Object.
Step 3 Click Query.
Step 4 In the Alarm Suppression, set Status of the Event that is POWERALM to Suppressed.

Step 5 Click Apply. A prompt appears to indicate that the operation was successful. Click Close.
----End
Parameters
Table 7-7 lists the power output parameters of the PMU board.
Table 7-7 Power output parameters of the PMU

OUTPUT Parameter Description
1 Subrack power 1 of the PDU1 (upper subrack)
2 Subrack power 2 of the PDU1 (middle subrack)
3 Subrack power 3 of the PDU1 (lower subrack)
4 Auxiliary power of the PDU1
5 Subrack power 1 of the PDU2 (upper subrack)
6 Subrack power 2 of the PDU2 (middle subrack)
7 Subrack power 3 of the PDU2 (lower subrack)
8 Auxiliary power of the PDU2

Operation Guide for Common Features 8 Performance Management
8 Performance Management
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
T2000 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,
and channel. If you have already created a performance threshold template, you can set
performance thresholds for one or more boards, ports, and channels at the same time.
8.7 Setting Performance Monitoring Parameters

8 Performance Management Operation Guide for Common Features
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 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 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 T2000 automatically dumps the data. There are two types of automatic
dumping, which are overflow-triggered dumping and scheduled dumping.
8.10 Collecting the History RMON Performance Data
Set parameters related to the object and performance event. In this way, the T2000 can
automatically and periodically collect the history RMON performance data.
8.11 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.12 Analyzing History Performance Data
To know the operational status of the equipment, you can analyze the history performance data
recorded on the T2000 or on the NE.
8.13 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 T2000, the T2000 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.14 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.15 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 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 T2000.
8.1.2 Performance Reporting Process
The performance reporting process starts when the board detects a performance event and ends
when the T2000 informs you the performance event. Performance reporting consists of
procedures such as enabling performance monitoring, automatically reporting the performance
and notifying the performance threshold crossing event.
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 Performance Dumping
You can use the performance dumping function to dump the history performance data on the
T2000 to a specified folder as a file. In this way, the running performance of T2000 is improved.
8.1.8 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 T2000.
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.
8.1.2 Performance Reporting Process

The performance reporting process starts when the board detects a performance event and ends
when the T2000 informs you the performance event. Performance reporting consists of
procedures such as enabling performance monitoring, automatically reporting the performance
and notifying the performance threshold crossing event.
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 T2000 as a

Y
performance crosses performance exception
the threshold event
Enable automatic N
End
reporting
Report the performance

data to the T2000 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 T2000 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 T2000 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 T2000 has special handling
and supports special setting of the abnormal event of performance threshold crossing. When
this abnormal event occurs, a dialog box is displayed on the T2000 asking you to take notice
of the event.
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.
You can set the performance monitoring parameters described as follows on the T2000.
NE Time Synchronization
NE Time Synchronization is used to keep consistency between the NE time and the system time
of the T2000 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 T2000 supports automatically
synchronizing the NE time periodically.
NE Performance Monitoring Parameters

The T2000 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 T2000 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
T2000 provides to customize the performance threshold values.
UAT Automatic Reporting

You can set whether an NE automatically reports the event to the T2000 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
T2000 and you are also informed.
You can set this parameter to monitor the performance events of certain objects.
NOTE
If many performance events are generated in the network, you are recommended to disable this function.
If this function is enabled when there are many performance events, many dialog boxes are displayed asking
you to confirm, which may affect the normal operation.
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.
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.

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.
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 T2000. You can set the
RMON in batches by using the templates.
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.
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.
8.1.6.1 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.6.1 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 T2000 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 T2000 receives the event, it automatically saves the event to
the history performance database.
NOTE
Once the T2000 receives the performance event, it immediately gathers new current history data.
l When you query the NE history performance data on the T2000, the T2000 updates the
contents that are not wrapped in the NE history performance register to the database.
8.1.7 Performance Dumping

You can use the performance dumping function to dump the history performance data on the
T2000 to a specified folder as a file. In this way, the running performance of T2000 is improved.
When an NE is running, a large number of performance data is generated. If the data is reported
to the T2000, it is saved to the T2000 database. If the history performance data that is stored on
the T2000 exceeds a certain limit, the T2000 operations is severely affected. In certain cases,
the entire system may be crashed. Hence, you can set automatic dumping or periodical dumping
on the T2000. After you set the parameters about dumping, the T2000 automatically dumps the
data in the history library to a file to reduce the loads of the T2000 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.

8.1.8 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.
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.
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.2.1 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.2 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, set
the prompt for new UAT events, query UAT events from an NE, and query UAT events from
the T2000.
8.2.3 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.4 Viewing Current Performance Data of an Ethernet Port
You can view the current performance data of an Ethernet port.
8.2.5 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.6 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.7 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.8 Viewing the Current Performance Data of an SDH Trail

To know whether services in an SDH trail are normal, view the current performance data.
8.2.9 Viewing History Performance Data of an SDH Trail
To know whether services in an SDH trail are normal, view the history performance data.
8.2.10 Querying Current Performance of WDM Trails
You can find out the running status of the service carried by the WDM trails by querying the
performance data.
8.2.11 Browsing the History Performance of WDM Trails
By querying the history performance data of a WDM trail, you can learn about the running status
of the services carried on the trail in a specific period in the past.
8.2.12 Browsing the Performance of an Ethernet Trail
By browsing the performance of the Ethernet trail, you can learn about the running status of the
services in the existing trail.
8.2.13 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.1 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 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 T2000 is
installed.
Procedure
Step 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 and Submarine Physical port Select a desired board and
equipment choose Performance >
Current Performance from
the Function Tree.

PTN equipment Unicast tunnel Choose Configuration >

MPLS Management >
Unicast Tunnel
Management from the
Function Tree. Select one or
more 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.
Step 2 Complete the following information: Monitored Object Filter Condition, Monitor Period.
Select the performance event type in the Gauge field and the Count field.
Step 3 Optional: In the Display Options area, check Display Current Value, Display Maximum
and Minimum Values, Display Zero Data and Display Continuous Severely Errored
Seconds check boxes.
Step 4 Click Query to query the data from the NE.
Step 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.1.1 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.1.1 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 and Submarine Physical port Select the related board, and
equipment then choose Performance >
History Performance .
PTN equipment Unicast tunnel Click Configuration >

MPLS Management >
Unicast Tunnel
Management . Select one or
multiple 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.
Step 2 Complete the information: Monitored Object Filter Condition, Monitor Period, From/To,
Data Source and Performance Event Type.
Step 3 Select the Display Current Value or Display Maximum and Minimum Values in the Display
Options.
Step 4 Click Query and the information is shown in the lower pane.
Step 5 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.2 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, set

the prompt for new UAT events, query UAT events from an NE, and query UAT events from
the T2000.
Prerequisite
Procedure
UAT Event .

MPLS Management >
Unicast Tunnel
Performance. Click UAT
tab.

choose UAT tab.
Step 2 Complete the following information: Monitored Object Filter Condition, start time, Data
Source, Functional Block Type and Display Options. Check the Prompt on New UAT Event
Reported check box. The information displayed according to your selection.
Step 3 Click Query to query data from the NE or the T2000.
Step 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.3 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
UAT Event .

MPLS Management >
Unicast Tunnel
Performance. Click UAT
tab.

choose UAT tab.
Step 2 Complete the information: Monitored Object Filter Condition, Monitor Period, Prompt on
New Threshold-Crossing, Performance Event Type, Display Options and start/end time. The
information displayed according to your selection.
Step 3 Click Query to query the data from the T2000.
----End
8.2.4 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
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > IP Performance Real-
time Monitor from the Function Tree.
Step 2 Select a value from the Monitored Object drop-down list.
Step 3 Select a value from the Monitor Interval(s) and Display Number of Data Column drop-down
lists.
Step 4 Click Query.
----End
8.2.5 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
l Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must be
configured.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > IP History
Performance from the Function Tree.
Step 2 Complete the information: Monitored Object, Query Period, and Time Range.
Step 3 Click Query.
----End
8.2.6 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
l The ATM service must be configured.
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Performance > ATM Performance Real-
Time Monitor > Port Performance Data from the Function Tree.

Step 2 Select a port.
Step 3 Complete the following information: Monitor Period, Monitor Interval(s) and Display
Number of Data Column.
Step 4 Click Start.
----End
8.2.7 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
l The ATM service must be configured.
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Performance > ATM History
Performance > Port Performance Data from the Function Tree.
Step 2 Complete the following information: Monitored Object, Query Period and time range.
Step 3 Click Query, and the information is displayed in the Query Result pane.
----End
8.2.8 Viewing the Current Performance Data of an SDH Trail

To know whether services in an SDH trail are normal, view the current performance data.
Prerequisite
l The trail must be created.
Procedure
All.
NOTE
already displayed.
Step 3 Select one or more trails. Click the Performance and select Query Performance.

Step 4 Click the 15-Minute Current Performance or 24-Hour Current Performance tab and view
the current performance of the trail.
Step 5 Optional: Click Filter. In the Filter dialog box, set the filter criteria and click OK. The qualified
performance events are displayed.
----End
8.2.9 Viewing History Performance Data of an SDH Trail

To know whether services in an SDH trail are normal, view the history performance data.
Prerequisite
l The trail must be created.
Procedure
All.
NOTE
already displayed.
Step 3 Select one or more trails. Click the Performance button and select Query Performance.
Step 4 Click the 15-Minute History Performance or 24-Hour History Performance tab and view
the history performance of the trail.
----End
8.2.10 Querying Current Performance of WDM Trails

You can find out the running status of the service carried by the WDM trails by querying the
performance data.
Prerequisite
Procedure

Filter.
Step 3 Select a trail, click Performance and select Query Performance from the drop-down list.
Step 4 Click the 15-Minute Current Performance or 24-Hour Current Performance tab and query
the latest 15-minute or 24-hour performance data of the trail. Perform the maintenance operation
according to the current performance events.
----End
8.2.11 Browsing the History Performance of WDM Trails

By querying the history performance data of a WDM trail, you can learn about the running status
of the services carried on the trail in a specific period in the past.
Prerequisite
Procedure
Filter.
Step 3 Select a desired trail, click Performance and select Query Performance from the drop-down
list.
Step 4 Click the 15-Minute History Performance or 24-Hour History Performance tab and view
the history performance data.
----End
8.2.12 Browsing the Performance of an Ethernet Trail

By browsing the performance of the Ethernet trail, you can learn about the running status of the
services in the existing trail.
Prerequisite
Procedure
Step 1 On the Main Menu, choose Trail > Ethernet Circuit > Ethernet Trail Management to display
the Set Trail Browse Filter Conditions dialog box.
Step 2 Select the filter conditions in the dialog box, and then click Filter All.

NOTE
l Click Filter All to refresh all the trails that meet the specified conditions.
l Click Secondary Filter to filter the displayed trails based on the filter conditions.
l Click Incremental Filter not to refresh the displayed trails. Instead, the new result is added to the end of
the displayed trails.
Step 3 Select one or more trails. Click Performance. The Monitor Ethernet Performance Window
is displayed. Then, the Filter dialog box is displayed.
Step 4 Optional: At the Alarm Group tab, set the information of the alarm group, including Port/Path,
alarm name, sampling interval(s), report mode, upper threshold, lower threshold and monitoring
status.
Step 5 Optional: At the History Control Group tab, Set the history table type. Browse the Ethernet
performance information, including monitored object, sampling period(s), number of items and
monitor status.
Step 6 Optional: At the History Group tab, set the Ethernet performance information, including port,
history table type, query conditions, display mode, browse the information of History Group.
Step 7 Optional: At the Statistics Group tab, set the Ethernet performance information, including
port, query conditions, display mode, browse the information of Statistics Group.
----End
8.2.13 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 T2000 is
installed.
Procedure
SDH, WDM and Submarine Physical port Select a desired board and
equipment choose Performance >
Current Performance from
the Function Tree.


MPLS Management >
Unicast Tunnel
Management from the
Function Tree. Select one or
more 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.
Step 2 Complete the following information: Monitored Object Filter Condition, Monitor Period.
Select the Working Temperature in the performance event type of the Gauge field.
Step 3 Optional: In the Display Options group box, check the Display Current Value or Display
Maximum and Minimum Values check box.
Step 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.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
Step 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 and Submarine Physical port Select the board and choose
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
Management. Right-click
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.
Step 2 Click the History Group tab.

Step 3 Complete the information: Select port, performance events, History Table Type, Query
Conditions and Display Mode.
Step 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
Procedure
SDH, WDM and Submarine Physical port Select the board and choose
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.
Step 2 Click the Statistics Group tab.
Step 3 Select a port.
Step 4 Select the performance events. Set the Query Conditions and Display Mode.
Step 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
Context

service.
VC4
Third-party
network
Configured Service
Procedure
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 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.
Step 5 Select the Object, Monitor Period, Options and duration. Click Query to view threshold
crossings. In the Operation Result dialog box, click Close.
----End

8.5 Creating Performance Threshold Templates

Setting an individual performance threshold for each NE is time-consuming. Hence, the
T2000 provides an easy way to set performance thresholds for multiple NEs by means of a
performance threshold template.
Prerequisite
Procedure
Step 1 Choose Performance > Performance Threshold Template from the Main Menu.
Step 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.
Step 3 Modify the performance thresholds as required.
Step 4 Save the template, you can choose one of the following methods:
l Click Save to save the modification.
l To save as a new template, click Save As and enter a template name.
Step 5 The Operation Result dialog box is displayed. Click Close.
----End
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,
and channel. If you have already created a performance threshold template, you can set
performance thresholds for one or more boards, ports, and channels at the same time.
Prerequisite
Procedure
Step 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 .

Application Object Entry
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.
Step 2 In the Monitor Object pane, select the desired board, port, and channel.
Step 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.
Step 4 Optional: Click Default to restore the default settings.
Step 5 Click Apply.
----End
8.7 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.7.1 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.7.2 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.7.3 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
8.7.4 Setting Performance Monitoring Parameters of a Board

You can set the monitoring status and the automatic reporting status of monitored objects. The
T2000 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.7.5 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.7.6 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.7.7 Setting Performance Monitoring Parameters of an SDH Trail
Performance monitoring keeps a detailed record of the performance of services over a trail,
helping the maintenance engineer to monitor and analyze the states of services.
8.7.8 Setting Performance Monitoring Parameters of an WDM Trail
8.7.1 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 T2000 server time.
Procedure
Step 1 Choose Performance > NE Performance Monitoring Time from the Main Menu.
Step 2 Select NEs from the NE list. Click .

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

Step 4 Click Apply and then click Close in the Operation Result dialog box.
----End
8.7.2 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
The ET1 board has been configured. The interface board is already configured for the ET1 board
if required.
NE time is synchronized with the T2000 server.
Procedure
Step 1 In the NE Explorer, select an NE and choose Performance > IP Performance Monitor
Period from the Function Tree to set the monitor period.
Step 3 Click Close.
Step 4 In the NE Explorer, select an NE and choose Performance > IP Performance Monitor
Time from the Function Tree.

Step 5 Select the Enabled option button.

Step 6 Set the Start Time and End Time.
Step 7 Click Apply and the Operation Result dialog box is displayed.
Step 8 Click Close.
----End
8.7.3 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 T2000 server.
Procedure
Step 1 In the NE Explorer, select an NE and choose Performance > ATM Performance Monitor
Period from the Function Tree to set the monitor period.
Step 3 Click Close.
Step 4 In the NE Explorer, select an NE and choose Performance > ATM Performance Monitor
Time from the Function Tree.
Step 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.
Step 6 Set the Start Time and End Time fields and click Apply.
Step 7 The Operation Result dialog box is displayed indicating that the operation was successful.
Step 8 Click Close.
----End
8.7.4 Setting Performance Monitoring Parameters of a Board

You can set the monitoring status and the automatic reporting status of monitored objects. The
T2000 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
Step 1 In the NE Explorer, select a board and choose Performance > Performance Monitor Status
Step 2 Select a condition from the Monitored Object Filter Condition drop-down list.
Step 3 Set the Monitor Status, 15-Minute Auto-Report and 24-Hour Auto-Report. Click Apply.
Step 4 In the Operation Result dialog box displayed, click Close.
----End
8.7.5 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
l Applies to the ET1 board. The interface board is already configured for the ET1 board if
required.
Procedure
Step 1 In the NE Explorer, select a board and choose Performance > IP Performance Event Monitor
Status from the Function Tree.
Step 2 In the Monitored Object Filter Condition, set the monitor object.
Step 3 Set the Monitor Status, 30-Second Auto-Report, 30-Minute Auto-Report and Custom
Period Auto-Report fields.
Step 4 Click Apply. The Operation Result is displayed indicates that the operation was successful.
Step 5 Click Close.
----End
8.7.6 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
Step 1 In the NE Explorer, select an ATM board and choose Performance > ATM Performance Event
Monitor Status from the Function Tree.
Step 2 Set the monitored object in the Monitored Object Filter Condition.
Step 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.
Step 4 Click Apply.
----End
8.7.7 Setting Performance Monitoring Parameters of an SDH Trail

Prerequisite
Procedure
All.
NOTE
already displayed.
Step 3 Select a trail. Click Performance and choose Performance Parameter from the drop-down
menu.
Step 4 In the Performance Parameter dialog box displayed, select an object, and set the monitoring
status and auto reporting status.
----End
8.7.8 Setting Performance Monitoring Parameters of an WDM Trail

Prerequisite

Procedure
All.
NOTE
already displayed.
Step 3 Select a trail. Click Performance and choose Performance Parameter from the drop-down
menu.
Step 4 In the Performance Parameter dialog box displayed, select an monitored object, and set the
monitor status and auto reporting status.
----End
8.8 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.8.1 Customizing the RMON Performance Attribute Template
Customize the RMON performance attribute template to provide a method of quickly setting
the RMON performance.
8.8.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.8.3 Setting the RMON History Control Group
Set the RMON history control group to control how the history data is obtained and stored.
8.8.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.8.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.8.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.8.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.8.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.8.9 Setting Automatic Reporting of RMON Performance Events
You can set automatic reporting of RMON performance events for a board.
8.8.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.
Context
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.
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

Management. Right-click one or several
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
select Browse Performance.
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
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.
Step 2 Click the RMON Setting tab.

Step 3 Click Event and set parameters related to Event as required.
Step 4 Click Save As Template. A dialog box is displayed for saving the template.
Step 5 Enter a name for Template Name.
Step 6 Click Save. A dialog box is displayed to show the operation result.
Step 7 Click Close to finish the setting.
----End
8.8.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


Performance.

Performance.

Step 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.
Step 4 Click Apply. A dialog box is displayed to show the operation result.
Step 5 Click Close.
----End
8.8.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
Step 1 Select the NE in the NE Explorer. Choose Performance > RMON History Control Group
Step 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.
Step 4 Click Close.
----End
8.8.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


Performance.

Performance.
Step 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.
Step 5 Click Close.
----End
8.8.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


Performance.

Performance.

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

Step 5 Click Close.
----End
8.8.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
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > RMON
Step 2 Click the Alarm Group tab.
Step 3 Set 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.
Step 4 Click Apply. A prompt is displayed indicating that the operation is successful.
Step 5 Click Close.
----End
8.8.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

Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > RMON
Step 2 Click the History Control Group tab.
Step 3 Select a History Table Type.
Step 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 Monitor Status to Enabled, in History Group, you can query the corresponding port and
the performance of the history group in History Table Type.
Step 6 Click Close.
----End
8.8.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
l The function of setting the RMON is applicable to the OptiX OSN 8800 I, and the OptiX
OSN 3800 and OptiX OSN 6800 of the V100R004C02 version or a later version
Procedure
Step 1 In the NE Explorer, select a board and choose Performance > RMON Performance from the
Function Tree.
Step 3 Select the port number of the board that you want to query.
Step 4 Click Query to query the current values of the performance events.
Step 5 Set values for the parameters as required. Click Apply. A prompt is displayed indicating that
the operation is successful.
Step 6 Click Close.
----End

8.8.9 Setting Automatic Reporting of RMON Performance Events

You can set automatic reporting of RMON performance events for a board.
Prerequisite
Procedure
Step 1 In the NE Explorer, select a board and choose Performance > Automatic RMON Performance
Data Reporting Settings from the Function Tree.
Step 2 Optional: Click Query to query the status of automatic reporting of performance events.
Step 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.
Step 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.
Step 6 Click Close.
----End
8.9 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 T2000 automatically dumps the data. There are two types of automatic
dumping, which are overflow-triggered dumping and scheduled dumping.
8.9.1 Dumping Performance Data Manually
By manually dumping performance data, you can save the history performance data, which is
recorded in the T2000 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.9.2 Dumping Performance Data Automatically
By automatically dumping the performance data, you can save the history performance data,
which is recorded in the T2000 to the specified directory. When the number of records in the
databases is reduced, the running speed of the system increases. There are two types of automatic
dump, which are the overflow dump and scheduled dump.

Prerequisite

Procedure
Step 2 Choose the performance data that you want to dump from the list and set Deadline in Instant
Dump Conditions.
Step 3 Optional: Click Query to query Number of Records (Piece) and Record Size (kB) in Record
Suitable for Instant Dump Conditions.
Step 4 Click Dump and the Confirm dialog box is displayed. Click OK to dump the performance data.
Step 5 When the dumping is complete, the Operation Result dialog box is displayed indicating the
path of saving the performance data. Click Close.
----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.

Prerequisite
Context
path.
Procedure
Step 2 Choose the performance data from the list, and set parameters of the Dumping when
Overflow or the Dumping in Schedule.

Step 3 Set the path of saving the performance data in Dump To(Path).
Step 4 Click OK.
----End
Result
The automatically dumped performance data is saved as a file in the specified directory, but not
NOTE
8.10 Collecting the History RMON Performance Data

Set parameters related to the object and performance event. In this way, the T2000 can
automatically and periodically collect the history RMON performance data.
Prerequisite

Procedure
RMON Performance.


Performance.

Performance.

NOTE


Performance.

Performance.

Step 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.
Step 5 Click Close.
Step 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.
Step 8 Click Close.
----End
8.11 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
l The performance monitoring function of the NE must be enabled.

Context
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
Step 1 Choose System > Scheduled Task Management from the Main Menu.
Step 2 Click New and the Task Creation Wizard is displayed.
Step 3 Set the Please select task type to Performance Data Collection and enter the task name in the
Please enter task name field. Then, click Next.
Step 4 Click SDH or WDM, and click to refresh.

Step 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.
Step 6 Set the Monitored Object Filter Condition, 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.
Step 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.
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.
Step 8 Click Next and select the running period.

Step 9 Click Next and select the start time and the running period each time.
Step 10 Click Finish.
----End
8.12 Analyzing History Performance Data

To know the operational status of the equipment, you can analyze the history performance data
recorded on the T2000 or on the NE.
Prerequisite

Procedure
Step 1 Choose Performance > History Performance Data Analysis from the Main Menu.
Step 2 In the Object Tree, select one module of a board and click .
Step 3 Complete the following information: Monitor Period, Display Mode and Time Range.
Step 4 Select Query from NE or Query from T2000.
Step 5 Click Query to query the data on the NE or that stored in the T2000.
----End
8.13 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 T2000, the T2000 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
l At least five days of performance data must be collected.
l The board must support the query of performance data.
Procedure
Step 1 Choose Performance > Medium-Term and Long-Term Performance Forecast from the
Main Menu.
Step 2 In the Object Tree, select one module of a board, and click .
Step 3 Complete the information: Category of Forecast Basis and Forecast Input Conditions.
Step 4 Click Forecast. The results are shown under Forecast Output Value and the corresponding
diagram is displayed.
----End
8.14 Resetting Performance Registers

Context
Based on the type of the performance register, you can reset the following performance registers:
8.14.1 Resetting Board Performance Registers
After a network test is performed or a fault is rectified, you need to reset the performance register
to enter a new performance monitoring period. A performance register of the board stores
performance data including optical power and bit errors.

8.14.2 Resetting ATM Performance Registers

8.14.3 Resetting Ethernet Performance Registers
8.14.1 Resetting Board Performance Registers

After a network test is performed or a fault is rectified, you need to reset the performance register
to enter a new performance monitoring period. A performance register of the board stores
performance data including optical power and bit errors.
Prerequisite
Procedure
Step 1 In the NE Explorer, select a board and choose Performance > Reset Board Performance
Register from the Function Tree.
Step 2 Select the ports and registers that you want to reset and click Reset.
Step 3 Click Yes in the confirmation dialog box. A prompt appears indicating that the operation is
successful.
Step 4 Click Close.
----End
8.14.2 Resetting ATM Performance Registers

Prerequisite
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Performance > Reset ATM Performance
successful.
Step 4 Click Close.
----End

8.14.3 Resetting Ethernet Performance Registers

Prerequisite
l The ET1 board must be configured.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > Reset IP Performance
successful.
Step 4 Click Close.
----End
8.15 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.15.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.15.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
Step 1 Choose Configuration > Power Consumption Management from the Main Menu.
Step 2 Query the power consumption according to the requirement.

l Query the NE power consumption as follows.
1. Click the NE Power tab.

2. In the Object Tree, select one or more NEs and click .

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 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.16.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 T2000.
8.16.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 T2000.
8.16.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.16.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 T2000.
Prerequisite
Applies to OptiX BWS 1600S.
The performance monitoring must be started
Procedure
Step 1 Choose Performance > Browse WDM Performancefrom the Main Menu. Click the Current
Performance Data tab.
Step 2 In the Object Tree, select one or more boards, and click the double-right-arrow button (red).
Step 3 Complete the following information: Monitored Object Filter Condition and Monitor
Period.
Step 4 Click the Count tab. In the Performance Event Type group box, check the Other Errors check
box.

Step 5 Optional: In the Display Options group box, check the Display Zero Data or Display
Consecutive Severely Errored Seconds check box.
----End
8.16.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 T2000.
Prerequisite
Procedure
Step 1 Choose Performance > Browse WDM Performancefrom the Main Menu. Click the History
Performance Data tab.
Step 2 In the Object Tree, select one or more boards, and click the double-right-arrow button (red).
Step 3 Complete the following information: Monitored Object Filter Condition, Monitor Period,
From: To: and Data Source.
Step 4 Click the Count tab. In the Performance Event Type group box, check the Other Errors check
box.

Step 5 Optional: In the Display Options group box, check the Display Zero Data check box.
Step 6 Click Query. Click Close in the Operation Result dialog box.
----End
8.16.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
Procedure
Step 1 In the NE Explore, select a board and choose Configuration > WDM Interface from the
Function Tree.
Step 2 Select the By Board/Port(Channel) option button. Select Channel from the drop-down list.
Step 3 Select the Basic Attributes tab.
Step 4 Click the Query.
Step 5 Double-click the Q Threshold and enter a proper value.
Step 6 Click Apply to confirm the settings.
----End

Operation Guide for Common Features 9 Keeping Data in the T2000 Consistent with NEs
9 Keeping Data in the T2000 Consistent with

NEs
About This Chapter
When you use multiple T2000s to manage NEs, and if a T2000 modifies an NE's configuration
data, the data in the other T2000s 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 T2000 should be consistent.
9.1 Data Management Policy of the T2000

The T2000 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.
9.2 Checking Consistency of Configuration Data Between an NE and the T2000
A consistency check is done to compare the configuration data in the NEs with the data in the
T2000. 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 T2000 or
download the data from the T2000 to the NE for data synchronization.
9.3 Viewing the Asynchronous Information
If the data in the NEs is different from the data in the T2000, you can locate the reason for the
data being out of synchronization by viewing the out-of-synchronization information.
9.4 Synchronizing the NE Configuration Data Manually
If an NE is in the Unsynchronized state, you can manually synchronize the NE configuration
data.
9.5 Uploading NE Configuration Data
The NE configuration data in the T2000 may differ from that in the NE. During maintenance,
you need to keep the data in the T2000 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 T2000. After
uploading, you need to perform a consistency check.
9.6 Downloading NE Configuration Data
you need to keep the data in the T2000 consistent with the data in the NE. When you want the

9 Keeping Data in the T2000 Consistent with NEs Operation Guide for Common Features
NE to operate according to the data in the T2000, you can download the data to the NE. After
the download, you need to perform a data consistency check.

9.1 Data Management Policy of the T2000

The T2000 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 T2000 side. It is the configuration data at the network layer
on the T2000. The network-layer data at the T2000 side contains the information about
fiber connections, protection subnets, and trails.
Data Management Functions

The T2000 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 T2000 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 11 Backing Up and Restoring the NE
Data.
l To back up and restore the T2000 data, refer to 10 Backing Up and Restoring T2000
Data.
NOTE
The RTN, PTN and NG WDM product series do not support preconfiguration and the downloading of
configuration data. Then, the T2000 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 T2000 needs to convert the configuration data to
the Qx interface information. Then, the data can be exchanged between the T2000 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 T2000, 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 T2000 is consistent with the data on the NE.
l Before the configuration changes, you need to back up the NE database and the T2000
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 T2000
database for the data restoration in case of an NE anomaly.
NE Data Management Policy

Figure 9-1 describes the NE data management operation that you need to perform in different
engineering phases and different scenarios.

Figure 9-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 T2000 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 T2000 nor the NE has
the configuration data. Thus, engineers need to manually configure the data.
1. Use the T2000 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 T2000 is consistent with that on the NE.
If the pre-configuration is already performed on the T2000, 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 T2000 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 T2000), you need
to synchronize the data on the T2000 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 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.
T2000 Data Management Policy

Figure 9-2 describes the T2000 data management operation that you need to perform in different
engineering phases and different scenarios.

Figure 9-2 T2000 Data Management Operation
T2000 software Routine

Construct T2000 data Troubleshooting
upgrade maintenance
Export networkwide Back up T2000 Restore T2000

Upload NE data
configuration files data data
Create fibers and T2000 software

Dump logs
cables upgrade
Search protection Configuration

subnets Upgrade Wizard
Search trails
T2000 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.
T2000 Software Upgrade
Before the T2000 software upgrade, you must make sure that the data on the T2000 is consistent
with the that on the NE. The T2000 software upgrade is performed as follows:
1. Export the network-wide configuration files for the data restoration after the software
upgrade.
2. Upgrade the T2000 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 T2000 data periodically and clear unnecessary databases to
arrange the database space in time.
1. After the important configuration data changes, backup the T2000 database immediately.
2. Back up the T2000 database periodically in a monthly (recommended) manner.
3. To vacate the database space, perform the log dump periodically.
Troubleshooting

When the T2000 becomes abnormal due to the T2000 fault, computer hardware fault, or other
causes, restore the T2000 data in time.
9.2 Checking Consistency of Configuration Data Between

an NE and the T2000
A consistency check is done to compare the configuration data in the NEs with the data in the
T2000. 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 T2000 or
download the data from the T2000 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 T2000 and NEs does not change the
configuration data in the NEs and in the T2000.
l To ensure that the T2000 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
T2000 server.
Procedure
Step 1 Select Configuration > Configuration Data Management from the Main Menu.
Step 2 Select one or more NEs in the left pane and click the double-right-arrow button (red).
Step 3 Select one or more NEs from the Configuration Data Management List.
Step 4 Click Consistency Check. Alternatively, right-click the NE and select Consistency Check
from the shortcut menu.
Step 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 T2000.
Troubleshooting
If the result indicates an inconsistency in the configuration data between the NE and the
T2000, you need to upload or download the data to achieve consistency.

9.3 Viewing the Asynchronous Information

If the data in the NEs is different from the data in the T2000, 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 T2000 and the NE, the NE icon
has a sign.
l If another T2000 client modifies the NE data when the current T2000 client is uploading
or synchronizing data, asynchronous information will be displayed in the NE Config Sync
Info dialog box of the current T2000 client. In this case, the current T2000 client can
perform an upload or synchronization again to eliminate the asynchronous information.
Procedure
Step 1 Choose Configuration > Configuration Data Management from the Main Menu.
The Configuration Data Management window is displayed.
Step 2 In the Object Tree, select one or more NEs, and click . The NEs you select are shown
in the Configuration Data Management List.
Step 3 Select an NE that is in the Unsynchronized state, and then click Sync Info.
Step 4 In the NE Config Sync Info dialog box, click Query to view the details of the configuration
items.
----End
9.4 Synchronizing the NE Configuration Data Manually

If an NE is in the Unsynchronized state, you can manually synchronize the NE configuration
data.
Prerequisite
The NE must be in the Unsynchronized state.
Context
If the data in the T2000 is inconsistent with the data in the NE, the NE icon has the sign.

Procedure
l Method 1
2. In the Object Tree, select an NE and click the double-right-arrow button (red).
3. In the configuration data management list, select one or more NEs that are in the
Unsynchronized state.
4. Click Synchronize or right-click and choose Synchronize from the shortcut menu.
5. Click OK. The T2000 begins to synchronize the data.
6. Click Close in the Operation Result dialog box.
l Method 2
1. On the Main Topology, select the NE that is marked with .
2. Right-click and choose Synchronize NE Data.
3. In the Confirm dialog box, click OK.
4. In the Synchronize dialog box, the T2000 begins to synchronize the data.
5. Click Close in the Operation Result dialog box.
----End
9.5 Uploading NE Configuration Data

you need to keep the data in the T2000 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 T2000. After
uploading, you need to perform a consistency check.
Prerequisite
Procedure
Step 1 Select Configuration > Configuration Data Management from the Main Menu.
Step 2 Select one or more NEs from the Object Tree and click the double-right-arrow button (red).
Step 4 Click Upload. Alternatively, right-click and select Upload from the shortcut menu.
----End
9.6 Downloading NE Configuration Data

you need to keep the data in the T2000 consistent with the data in the NE. When you want the

NE to operate according to the data in the T2000, you can download the data to the NE. After
the download, you need to perform a data consistency check.
Prerequisite
Context
CAUTION
Downloading NE configuration data can interrupt the services.
l NG WDM and RTN series equipment does not support the downloading of configuration
data.
l When you download the NE configuration data from the T2000 to the NE, the T2000 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.
l The function of downloading configuration data is only used in the implement phase of a
project or for the recovery of NE service and core configuration data in case of emergency.
This function dose not support downloading of all configuration data of NEs. If you want
to restore all data of the NEs, you must use the Recover function in the Data Center.
Procedure
Step 2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red).
Step 4 Click Download. Alternatively, right-click and choose Download from the shortcut menu.
Step 5 Click OK in the two Confirm dialog boxes.
----End

Operation Guide for Common Features 10 Backing Up and Restoring T2000 Data
10 Backing Up and Restoring T2000 Data
About This Chapter
To ensure network data security, the T2000 provides the option of network data backup and
restoration functions.
10.1 Dump and Backup

Dump and backup are two important features that are used to manage the T2000 databases.
10.2 Script Files
When you upgrade the T2000, 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.3 Methods of Backing Up and Restoring the T2000 Data
You can back up and restore the T2000 data in three ways: Back up and restore the T2000
managed object (MO) data, back up and restore all data in T2000 databases, and back up and
restore the T2000 network configuration data by using scripts.
10.4 Backing Up T2000 Data to a Local Server
The T2000 data backup is essential to restore the T2000 database safely and quickly.
10.5 Backing Up T2000 Data to a Remote Server
10.6 Initializing the T2000 Database
After installing the T2000 or before restoring the T2000 database, you need to initialize the
T2000 database.
10.7 Initializing NE Configuration Data in the T2000
To reconfigure all data (board, service, clock, protection) of multiple NEs, you need to initialize
the NE configuration data in the T2000, to quickly clear the configuration data of the NEs from
the T2000.
10.8 Restoring T2000 Data from a Local Server
When the T2000 database fails, you can restore the T2000 data from a local server where the
T2000 data was backed up.
10.9 Restoring T2000 Data from a Remote Server

10 Backing Up and Restoring T2000 Data Operation Guide for Common Features
When the T2000 database fails, you can restore the T2000 data from a remote server where the
10.10 Viewing the Status of Databases
Using the System Monitor client, you can monitor the status of databases on the T2000 server.
10.11 Dumping the T2000 Log Data
To ensure that the system runs stably and efficiently, you need to dump the alarm and
performance data to another place when the data in the database reaches a certain amount. The
data can be manually and automatically dumped.
10.12 Clearing the T2000 Log Data
During the routine maintenance of the T2000, you can clear the unwanted log data to save spaces
for the computer.
10.13 Configuration Upgrade Wizard
By using the upgrade wizard, you can restore the T2000 data from the existing configuration
data scripts.

10.1 Dump and Backup

Dump and backup are two important features that are used to manage the T2000 databases.
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 T2000 provides three methods of dumping logs. The three methods are overflow dump,
scheduled dump and immediate dump.
l 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.
l 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.
l 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.
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 T2000 provides the following schemes to backup the database:
l Backup of the MO data
l Backup of the T2000 databases
l Backup of the data by using scripts
For details on the differences between the three schemes, refer to the 10.3 Methods of Backing
Up and Restoring the T2000 Data.
In the case of the data being damaged, you can restore the data. To restore the damaged data,
you can restore the databases from the back up files and overwrite the existing database files.
The backup and restoration features are used for the purpose of network data security.
10.2 Script Files

When you upgrade the T2000, 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-1 lists the types of the script files in the .txt format that the T2000 provides and the
contents of the data.

Table 10-1 Script files the T2000 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 a imported and
script file set. When exported.
the networkwide
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 networkwide
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.txt about every port on exported.
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.txt information that is exported.
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_T2000 This file contains This file can be

name.txt information about imported and
NEs, T2000, and exported.
subracks, and 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_T2000 This file contains the This file can be

Information File name.txt configuration exported but cannot
information about be imported.
the T2000 server.
The configuration
information is as
follows:
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_T2000 This file provides This file can be

Actualization Script name.txt service actualization exported but cannot
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_T2000 This file contains This file can be

Information File name.txt information on the imported and
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 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.txt operation that is be imported.
performed on
multiple NEs in
batches.
In addition, the T2000 provides the script files in the .xml format for the network planning and
design, containing the networkwide 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.
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 T2000 upgrade.
This is an important method for the T2000 upgrade. This is the main usage of the script
files.
l After the network data is modified, restoring the customized information of the T2000,
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 T2000 data.
l By modifying the script files, 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 T2000 of a earlier version can be imported to the T2000 of
a later version. But an error may occur if the scripts exported from the T2000 of a later
version is imported to the T2000 of a earlier version. The T2000 of a earlier version does
not support the features and functions that are added and the parameters that are modified
in the T2000 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, on SUSE Linux and on Solaris 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 T2000. 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 optical ports, are
changed. This does not affect the restoration of the customized information.

10.3 Methods of Backing Up and Restoring the T2000 Data

You can back up and restore the T2000 data in three ways: Back up and restore the T2000
managed object (MO) data, back up and restore all data in T2000 databases, and back up and
restore the T2000 network configuration data by using scripts.
Backing Up and Restoring the T2000 Databases

The T2000 databases are automatically created during the initial installation of the T2000. When
you back up the T2000 databases, the databases are saved as operating system files. The
information that is backed up includes the user-defined data at the T2000 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 T2000 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.
Backing Up and Restoring the T2000 MO Data

When you back up the T2000 MO data, the database tables in the MO structure are copied to
the operating system file by using the Huawei-compiled script. The information that is backed
up by way of MO backup and that is backed up by way of T2000 database backup is the same.
The information contains the user-defined data at the T2000 side, network layer trail data, NE-
side configuration data, alarm data and performance data. However, the MO backup includes
the data in the tables, but not the table frame, storage process, trigger, user name, authority and
so on.
NOTE
The data that cannot be backed up by way of MO backup is the same as that cannot be backed up by way
of T2000 database backup. The data contains:
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

The T2000 provides the function of exporting and importing script files, to back up and restore
the network configuration data of the T2000. This realizes the upgrade of the configuration data
with zero loss during the T2000 upgrade. For more details of script files, see 10.2 Script
Files.
NOTE
l The data are exported from the T2000 database, containing the configuration data at the network and
NE layers on the T2000.
l The imported script files update the data on the T2000 only, with no impact on the data on the NEs.

Comparison of Three Data Maintenance Methods

The characteristics of the three data maintenance methods determine their application scenarios.
Table 10-2 lists the characteristics and application scenarios of the three methods.
Table 10-2 Comparison of three data maintenance methods

Item Backing up and Backing up and Backing up and
restoring all data restoring the restoring the
in the T2000 T2000 MO data T2000 network
databases configuration data
by using the script
files
Backup contents Backs up the Backs up only the Backs up only the
structure and data in all database configuration data on
contents of the tables, but not the the T2000.
T2000 database. structure of the
Backs up all data. database.
Saving format Binary Text Text
Version The data that is The data that is The data that is
compatibility backed up can be backed up can be backed up can be
restored on the restored on the restored on the
T2000 of the same T2000 of the same T2000 of different
version only. version only. versions.
Platform The data that is The data that is The data that is
compatibility backed up cannot be backed up cannot be backed up can be
restored on the restored on the restored on the
T2000 that is T2000 that is T2000 that is
installed on a installed on a installed on a
different platform. different platform. different platform.
Maintenance time Fast (The backup Medium(The backup Slow(The backup

time is time is time is
approximately 8 to approximately 20 to approximately 30 to
12 minutes and the 40 minutes and the 60 minutes and the
restoration time is 10 restoration time is 30 restoration time is
to 15 minutes in the to 60 minutes in the more than 10 hour in
case of 6000 case of 6000 the case of 6000
equivalent NEs.) equivalent NEs.) equivalent NEs.)
Backup file size Large (The backup Medium(The backup Small (The backup
file is 100 MB-150 file is 50 MB-100 file is 50 MB-80 MB
MB after it is MB after it is and the backup file
automatically automatically cannot be
compressed by the compressed by the automatically
DM tool in the case DM tool in the case compressed.)
of 6000 equivalent of 6000 equivalent
NEs.) NEs.)

Item Backing up and Backing up and Backing up and

restoring all data restoring the restoring the
in the T2000 T2000 MO data T2000 network
databases configuration data
by using the script
files
Application scenario This method is This method is used This method is

recommended in when the data in the usually used to
most scenarios as database needs to be upgrade the T2000
follows: The backup located. and to back up and
file is used to quickly restore the basic
restore the T2000 configuration data
data; the procedures for a single NE. This
of backing up and method also restores
restoring the data of a the user-defined
network need to be data. The new T2000
simulated. version is compatible
with the scripts of the
old version.
Table 10-3 Characteristics and application scenarios of three data maintenance methods
Method Characteristics Application Scenario
Backing up and restoring the Backs up all data in the The backup MO files
T2000 MO data T2000 database as an MO correspond to the specific
file. The data is in the txt versions and are not
format and the user who interchangeable.
knows the data structure of
the T2000 can understand the
contents of the MO file.
Backs up all data.
The processing speed is fast,
and the backup file is big.
Backing up and restoring all Backs up the structure and This requires a large storage
data in the T2000 databases contents of the T2000 medium space. If you want to
database. The data is in the back up the T2000 database
binary mode. in a scheduled manner, tapes
Backs up all data. are recommended.
The processing speed is fast,
and the backup file is big.

Method Characteristics Application Scenario
Backing up and restoring the Exports the configuration This method is usually used
T2000 network data in the T2000 to a txt file to upgrade the T2000 and to
configuration data by using that is similar to the MML back up and restore the basic
the script files format. This is done to save configuration data for a
data. You can directly single NE. This method also
understand the configuration restores the user-defined
contents of the txt file. data. The new T2000 version
Backs up only some of the is compatible with the scripts
data, including the basic of the old version.
configuration data, port
naming data and user-defined
data.
The processing speed is slow
and the backup file is very
small.
Suggestion
When you back up the T2000 database, do as follows:
l Before backing up the data, upload the NE data, and perform the search of the protection
subnets and trails.
l When you install the T2000 for the first time, back up the T2000 databases. Back up the
T2000 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 T2000 databases on a quarterly basis.
l During the daily maintenance of the T2000, it is recommended that you back up the T2000
databases. Whenever there is a change in the service configuration data, ensure that you
immediately back up the T2000 databases. You can also set up a scheduled task to back up
the T2000 databases on a monthly basis.
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 You must shut down the T2000 server firstly and then restore the T2000 MO data or restore
T2000 databases.
l You need to back up the deployment information of the network management system by
using the network management system maintenance suite immediately after you back up
the database, MO data or modify the deployment.
10.4 Backing Up T2000 Data to a Local Server

10.4.1 Immediately Backing Up the T2000 MO Data

In the event of a failure, you can restore the data from a backup database file. This operation is,
however, not applicable to the upgrade of the T2000. When you upgrade the T2000, you can
export the system data to script files to save the system data.
10.4.2 Periodically Backing Up the T2000 MO Data

You can set a scheduled backup task for the database so that the T2000 automatically backs up
the T2000 database at a scheduled time. This facilitates the operation and the maintenance.
10.4.3 Immediately Backing Up All Data in the T2000 Database
To quickly restore the database in the event of a failure, back up the T2000 database by using
the database management tool.
10.4.4 Periodically Backing Up All Data in the T2000 Database
Using the Database Management Tool, you can back up the T2000 database in a scheduled
manner, so that the T2000 database can be safely and quickly restored in the case of a database
failure.
10.4.5 Immediately Backing Up the T2000 Data by Script
Before upgrading the T2000, you must export the data from the database to script files and save
these files.
10.4.6 Periodically Backing Up the T2000 Data by Script
During the routine maintenance, you can use the scheduled task function to periodically export
the network configuration data to script files. In this way, the data can be migrated smoothly
when you upgrade the T2000 software. This way of backup reduces the maintenance cost as no
human intervention is required.
10.4.1 Immediately Backing Up the T2000 MO Data

In the event of a failure, you can restore the data from a backup database file. This operation is,
however, not applicable to the upgrade of the T2000. When you upgrade the T2000, you can
export the system data to script files to save the system data.
Prerequisite
l On Windows, the current user must have the administrator authority of the operating
system. The database server must also be started.
l Make sure the current user is root and the Sybase database must be started.
l The network management system maintenance suite server must be started.
Context
CAUTION
l In the case of a distributed system, back up T2000 M0 data only on the Master server.
l This operation backs up both the MO data and T2000 deployment information.
To back up the MO data periodically by using the command line, run the following commands
as user root:
# cd /T2000/server/database
# ./backupmo.sh
Procedure
l Follow the steps below to back up the MO data using the T2000 client.

1. Choose System > Database > Database Backup from the Main Menu.
2. Select the data source MO, set a backup directory for the server, and click Backup.
The T2000 starts to back up the database. A progress bar is displayed showing the
status of the operation.
NOTE
By self-defining a backup directory, you can avoid the impacts on the backup data that may be
caused when you reinstall the system or format disk C. In this way, the maintainability of the
system is improved.
Make sure that no space, punctuation or non-English character exists in the path.
l Use the T2000database management tool to back up the T2000 MO data.
NOTE
To back up the MO data by using the command line, run the following commands on the active
server:
# ./backupmo.sh
1. Start the Database Management Tool.

NOTE
l On Solaris, open a terminal window. In the /T2000/server/database directory, run the

T2000DM.sh file.
l On SUSE Linux, open a terminal window. In the /T2000/server/database directory, run
the T2000DM.sh file.
l On Windows, open the Window Explorer. In the \T2000\server\database directory, run
the T2000DM.exe file.
2. In the left-hand Database Server List, select T2000DBServer.
3. Enter the password of user sa in the dialog box displayed.
NOTE
The default password of user sa is null.

4. Click Backup MO and the Description dialog box is displayed.
5. Set a backup directory for the server, enter the information in the Description field
and click Backup. The Back Up MO dialog box is displayed. The system starts to
back up the T2000 MO data.
NOTE
By self-defining a backup directory, you can avoid the impacts on the backup data that may be
caused when you reinstall the system or format disk C. In this way, the maintainability of the
system is improved.
The database file is backed up in the default directory.
l On Solaris, the default directory is /T2000/server/database/dbbackup.
l On SUSE Linux, the default directory is /T2000/server/database/dbbackup.
l On Windows, the default directory is \T2000\server\database\dbbackup.
6. Click OK in the Back Up MO dialog box to return to the Database Management

Tool window.
----End

10.4.2 Periodically Backing Up the T2000 MO Data

You can set a scheduled backup task for the database so that the T2000 automatically backs up
the T2000 database at a scheduled time. This facilitates the operation and the maintenance.
Prerequisite
Context
CAUTION
l To back up the MO data periodically by using the command line, run the following
commands as user root:
# ./configTask.sh
Follow the instructions displayed on the terminal to perform operations.

l On SUSE Linux, to back up the MO data periodically by using the command line, run the
following commands as user t2000:
% su
Password: Password_of_user_root
# ./configTask.sh
Follow the instructions displayed on the terminal to perform operations.
Procedure
Step 1 Choose System > Schedule Task Management from the Main Menu.
Step 2 Click New, and the Task Creation Wizard is displayed.

NOTE
If you have not defined a scheduled task, a prompt is displayed.
Step 3 Select Database Backup in the Select task type field and enter the task name. Click Next.
Step 4 Select the data source MO, set a backup directory for the server, and click Next.
NOTE
By self-defining a backup directory, you can avoid the impacts on the backup data that may be caused
when you reinstall the system or format disk C. In this way, the maintainability of the system is improved.

Step 5 Set the running period and click Next.

NOTE
The interval of different scheduled tasks must be set above 20 minute.
l The scheduled time for a task is based on the server time.
l When creating or modifying a scheduled task, if the running period is set to Running once
or Daily, set the start time of the scheduled task at least five minutes later than the current
time (the server time).
Step 6 Set the time to run the task.
Step 7 Click Finish. The system backs up the T2000 database according to the time settings.
Step 8 If the T2000 server uses the Windows XP SP2 operating system, you also need to configure the
scheduled task that was created. For details, refer to 10.5.5 Configuring a Scheduled Task.
----End
10.4.3 Immediately Backing Up All Data in the T2000 Database

To quickly restore the database in the event of a failure, back up the T2000 database by using
the database management tool.
Prerequisite
Context
CAUTION
l In the case of a distributed system, back up T2000 database only on the Master server.
l This operation backs up both the database and T2000 deployment information.
On UNIX, to back up the T2000 database by using the command line, run the following
commands on the active server:
# ./backupdatabase.sh
Procedure
Step 1 Start the Database Management Tool.

NOTE
On SolarisSUSE Linux, open a terminal window and run the following commands to tart the Database
Management Tool.
# ./T2000DM.sh
On Windows, open the Resource Browser. In the \T2000\server\database directory, run T2000DM.exe.
Step 2 Select T2000DBServer from the left-hand Database Server List.
Step 3 Enter the password of user sa.

NOTE
Step 4 Click Backup Database. The Description dialog box is displayed.
Step 5 Specify a directory to save the backup file.

NOTE
Step 6 Click Backup to back up the T2000 database.
----End
10.4.4 Periodically Backing Up All Data in the T2000 Database

Using the Database Management Tool, you can back up the T2000 database in a scheduled
manner, so that the T2000 database can be safely and quickly restored in the case of a database
failure.
Prerequisite
l On UNIX, the current user is root and the Sybase database must be started.
system. The MS SQL database server must also be started.
Context
NOTE
To back up the T2000 database periodically by using the command line, run the following
commands:
% su
# ./configTask.sh
Follow the prompts.
Procedure

NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Step 4 Click the Scheduled Backup tab.
Step 5 Click the Back up Local tab.
Step 6 Select Database in the Backup Type pane, and then set other relevant attributes for the task.
NOTE
Step 7 Click Configure, and a dialog box is displayed prompting you to enter the administrator
password.
Step 8 Enter the administrator password and click OK. A prompt appears telling you that the scheduled
task was successfully created. Click OK.
----End
10.4.5 Immediately Backing Up the T2000 Data by Script

Before upgrading the T2000, you must export the data from the database to script files and save
these files.
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 T2000 is consistent with that in the NE.
Procedure
Step 1 Choose System > Import/Export Script File from the Main Menu.
Step 2 Select a file format. Then select a script file type from the Script File Type field.

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. For details, see 10.2 Script Files.
Step 3 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.
Step 4 Click Create File Directory to create a directory where the exported script files are to be saved.
Step 5 Enter the directory name and click OK.

NOTE
The script file is saved on the T2000 server. On Windows, the backup directory is \T2000\server\script.
On UNIX, the backup directory is /T2000/server/script. You can create a new directory under it.
Step 6 Select a directory and click Apply.

A progress bar appears showing the status of the export.
----End
10.4.6 Periodically Backing Up the T2000 Data by Script

During the routine maintenance, you can use the scheduled task function to periodically export
the network configuration data to script files. In this way, the data can be migrated smoothly
when you upgrade the T2000 software. This way of backup reduces the maintenance cost as no
human intervention is required.
Prerequisite
Context
NOTE
l For scheduled tasks of different types, the running time cannot be the same, and the involved NEs cannot
be the same. Otherwise, the tasks may fail as a result of the resource conflict.
l The start time difference between each two scheduled tasks must be greater than the maximum running time
of the tasks.
Procedure
Step 1 Choose System > Schedule Task Management from the Main Menu.
Step 2 Click New, and the Task Creation Wizard dialog box is displayed.

NOTE
If you have not define a scheduled task, a prompt is displayed.
Step 3 Select Export Script File as the task type, and enter the name of this scheduled task. Click
Next.
Step 4 Select a script type and an NE list for the export. Click Next.
Step 5 Select a running period for the scheduled task. Click Next.
NOTE
It is recommended that you set the running period to Weekly.
Step 6 Specify the start data and time, and then select the daily running time.
Step 7 Click Finish. The created scheduled task is displayed in the Scheduled Task Management
window.
----End
10.5 Backing Up T2000 Data to a Remote Server

10.5.1 Backing Up the T2000 MO Data Immediately

Using the database management tool, you can immediately back up the T2000 MO data to a
remote server, so that the T2000 MO data can be safely and quickly restored in the event of a
database failure.
10.5.2 Backing Up the T2000 MO Data Periodically
Using the Database Management Tool, you can back up the T2000 MO data to a remote server
in a scheduled manner, so that the T2000 database can be safely and quickly restored in the case
of a database failure.
10.5.3 Backing Up All Data in the T2000 Database Immediately
Using the database management tool, you can immediately back up the T2000 database to a
remote server, so that the T2000 database can be safely and quickly restored in the event of a
database failure.
10.5.4 Backing Up All Data in the T2000 Database in a Scheduled Manner
Using the Database Management Tool, you can back up the T2000 database to a remote server
10.5.5 Configuring a Scheduled Task
By configuring a scheduled task on the T2000 server that runs on Windows operating system,
you can back up the T2000 database at scheduled time.
10.5.1 Backing Up the T2000 MO Data Immediately

Using the database management tool, you can immediately back up the T2000 MO data to a
remote server, so that the T2000 MO data can be safely and quickly restored in the event of a
database failure.

Prerequisite
l On SolarisSUSE Linux, the current user is root and the Sybase database must be started.
l The FTP server program must be running on the remote server, and the relevant port must
be enabled.
l The current user must have the write authority in a remote FTP server.
Context
CAUTION
Procedure
NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Step 4 Click the Remote Backup/Restoration tab.
Step 5 Enter the IP Address of Data Backup Server, Port, User Name and Password. Click
Login.

Step 6 Under the Select path area, click to specify the backup path on the remote server.
NOTE
Step 7 Under the Select type area, check the Back Up MO check box, and set other attributes for the
task.
Step 8 Click Backup.
----End
10.5.2 Backing Up the T2000 MO Data Periodically

Using the Database Management Tool, you can back up the T2000 MO data to a remote server
Prerequisite
l On Solaris, the current user is root and the Sybase database must be started.
l On SUSE Linux, the current user is root and the Sybase database must be started.
be enabled.
Context
NOTE
l On Solaris, to back up the T2000 MO data periodically by using the command line, run the
following commands as user t2000:
% su
# ./configTask.sh
Procedure

NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Login.
Step 6 Select MO in the Backup Type pane, and then set other relevant attributes for the task.
NOTE
password.
----End
10.5.3 Backing Up All Data in the T2000 Database Immediately

Using the database management tool, you can immediately back up the T2000 database to a
remote server, so that the T2000 database can be safely and quickly restored in the event of a
database failure.

Prerequisite
l On SolarisSUSE Linux, the current user is root and the Sybase database must be started.
be enabled.
Context
CAUTION
l In the case of a distributed system, back up T2000 database only on the Master server.
l This operation backs up both the database and T2000 deployment information.
Procedure
NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Login.

Step 6 Under the Select path area, click to specify the backup path on the remote server.
NOTE
Step 7 Under the Select type area, check the Backup the database check box, and set other attributes
for the task.
Step 8 Click Backup.
----End
10.5.4 Backing Up All Data in the T2000 Database in a Scheduled

Manner
Using the Database Management Tool, you can back up the T2000 database to a remote server
Prerequisite
be enabled.
Context
NOTE
To back up the T2000 database periodically by using the command line, run the following
commands:
% su
# ./configTask.sh
Follow the prompts.
Procedure

NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Login.
Step 6 Select Database in the Backup Type pane, and then set other relevant attributes for the task.
NOTE
password.
----End
10.5.5 Configuring a Scheduled Task

By configuring a scheduled task on the T2000 server that runs on Windows operating system,
you can back up the T2000 database at scheduled time.

Prerequisite
The scheduled task must be created.
Context
This section describes how to configure a scheduled task on Windows XP SP2. To perform the
configuration on other Windows operating systems, refer to this section.
Procedure
Step 1 On the desktop of the Windows XP SP2, choose Start > Control Panel > Scheduled Tasks.
Step 2 Right-click the scheduled task that was created by using the Database Management Tool, and
choose Properties from the shortcut menu.
Step 3 In the Run as field, enter the full name of user administrator, in the format of "computer name
\administrator user name".

Step 4 Click Set password, and enter the password for user administrator. Click OK.
Step 5 Click OK.
----End
10.6 Initializing the T2000 Database

After installing the T2000 or before restoring the T2000 database, you need to initialize the
T2000 database.
Prerequisite
l The T2000 server applications must be closed.
l On Windows, the current user must have the "system administrator" authority and the MS
SQL Server database must be started.

Context
CAUTION
This operation clears all data in the T2000 database. Thus, make sure that you back up the T2000
database and the deployment information of the network management system before this
operation.
NOTE
In a distributed system, initialize T2000 database on the Master server.
Procedure
NOTE
l On Solaris, open a terminal window. In the /T2000/server/database directory, run "T2000DM.sh".

l On Linux, open a terminal window. In the /T2000/server/database directory, run "T2000DM.sh".
l On Windows, open the Resource Browser. In the \T2000\server\database directory, run
"T2000DM.exe".

NOTE
Step 4 Click Database Maintenance.

Step 5 Click Initialize Database. The Confirm dialog box is displayed.
Step 6 Click OK to initialize the T2000 database.
----End
10.7 Initializing NE Configuration Data in the T2000

To reconfigure all data (board, service, clock, protection) of multiple NEs, you need to initialize
the NE configuration data in the T2000, to quickly clear the configuration data of the NEs from
the T2000.
Prerequisite
l You must log in to the NE as an NE user with "system level" authority.

Context
CAUTION
After initializing the NE configuration data in the T2000, if you download the data to the NE
from the T2000, the NE loses all data, and the services in the NE are interrupted. But, if you do
not perform the download operation, the data in the NE and services are not affected.
Procedure
Step 2 In the Object Tree, select NEs and click the double-right-arrow button (red).
Step 3 Select one or more NEs from the NE list.
Step 4 Click Initialize NM Side Data. Alternatively, right-click the NE and choose Initializing NM
Side Data from the shortcut menu.
Step 5 Click OK in the Confirm dialog box.

A progress bar is displayed.
Step 6 A prompt is displayed indicating that the operation is successful. Click Close. The initialized
NE is shown in the Unconfigured state.
----End
10.8 Restoring T2000 Data from a Local Server

When the T2000 database fails, you can restore the T2000 data from a local server where the
10.8.1 Restoring the T2000 MO Data

You can restore the T2000 MO data from the original T2000 database backup.
10.8.2 Restoring All Data in the T2000 Database
You can restore the T2000 database from a backup file by using the database management tool.
10.8.3 Restoring the T2000 Data by Using the Script
After upgrading the T2000, you can restore the T2000 network layer configuration data from
the backup script files.

You can restore the T2000 MO data from the original T2000 database backup.
Prerequisite
l The deployment information about the network management system that matches the MO
data of the T2000 is restored. For details, see Restoring the Data of the Network
Management System.

l The T2000 MO data must be backed up.

l The T2000 server must be shut down.
l On Solaris, the Sybase database must be started and the current user is root.
l On SUSE Linux, the Sybase database must be started and the current user is root.
l On Windows, the MS SQL server database must also be started and the current user must
have the administrator authority of the operating system.
l The T2000 database must be initialized. The T2000 server must be started and then shut
down.
Context
CAUTION
The T2000 version and deployment information (containing the number and names of instances)
of the MO data that is used for restoration must be consistent with the T2000 version and
deployment information of the MO data to be restored.
NOTE
In a distributed system, restore T2000 data on the Master server.
To restore the MO data by using the command line, run the following commands:
# ./restoremo.sh
Procedure
NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Step 4 Click Restore MO. The Select MO dialog box is displayed.

NOTE
The database file is backed up in the default directory.

l On Solaris, the default directory is /T2000/server/database/dbbackup.
l On SUSE Linux, the default directory is /T2000/server/database/dbbackup.
l On Windows, the default directory is C:\T2000\server\database\dbbackup if the T2000 server was
installed in disk C.
Step 5 Select the MO data that is used for restoration. Click Restore to restore the T2000 MO data.

When restoring the MO data, the database management tool first checks whether the current
T2000 deployment information is the same as the T2000 deployment information in the backup
file package. If the information is the same, click OK in the Confirm to Restore MO dialog
box to begin to restore the T2000 MO data.
CAUTION
If the information is different, restore the data by following the instructions in the prompts.
1. In the Confirm to Restore MO dialog box, click OK.
2. A Confirm to Restore MO dialog box is displayed indicating that the MO to be restored is
not consistent with the current deployment. The deployment info will be restored automatic
and the restoration can not be rollbacked. Are you sure to continue? In the Confirm to
Restore MO dialog box, click OK to begin to restore the T2000 deployment information.
3. After you restore the information, a message is displayed indicating that the T2000
information is restored. In addition, you are prompted to start and shut down the T2000 and
click OK to continue to restore the MO data.
4. Start and then shut down the T2000. For details, refer to Starting and Shutting Down the
T2000.
5. Click OK to restore the T2000 MO data.
Step 6 Click OK in the prompt dialog box to return to the database management tool interface.
----End

You can restore the T2000 database from a backup file by using the database management tool.
Prerequisite
l The deployment information about the network management system that matches the
database data of the T2000 is restored. For details, see Restoring the Data of the Network
Management System.
l The T2000 database must be backed up.
l The T2000 server must be shut down.
l On UNIX, the Sybase database must be started and the current user is root.
l On Windows, the MS SQL server database must be started and the current user must have
the administrator authority of the operating system.
Context
CAUTION
of the T2000 database that is used for restoration must be consistent with the T2000 version and
deployment information of the T2000 database to be restored.

NOTE
To restore the T2000 database by using command line, run the following commands:
# ./restoredatabase.sh
Procedure
NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Step 4 Click Restore Database. Select the database that is used for restoration.
Step 5 Click Restore to start restoring the T2000 database.
When restoring the database, the database management tool first checks whether the current
file package. If the information is the same, click OK in the Confirm to Restore Database
dialog box to begin to restore the T2000 database.
CAUTION
1. In the Confirm to Restore Database dialog box, click OK.
2. A Confirm to Restore Database dialog box is displayed indicating that the database to be
restored is not consistent with the current deployment. The deployment info will be restored
automatic. Are you sure to continue? In the Confirm to Restore Database dialog box, click
OK to begin to restore the T2000 deployment information and the database.
----End
10.8.3 Restoring the T2000 Data by Using the Script

After upgrading the T2000, you can restore the T2000 network layer configuration data from
the backup script files.
Prerequisite
l You must have the license for the T2000 script import.

Context
CAUTION
Before importing the script file, you need to back up the T2000 database or the T2000 MO data,
and then initialize the T2000 database. Import the networkwide configuration script file. You
can restore the data from a backup file if you failed to import the script file.
Procedure
Step 1 Choose System > Import/Export Script File from the Main Menu.
Step 2 Click the Import option button.
Step 3 Select the file format and select the script file type from the Script File Type field.
NOTE
Service Actualization Script and NM Computer Information File are not supported.
Step 4 In the Operation Directory List, select the directory where the script file is to be imported is
located.
Step 5 Select the script file to import from the Import File List.
Step 6 In the Import Subnet List, select the sunbets to be imported. All subnets are required to be
selected.
Step 7 Click Apply. The system prompts you twice that the import of the configuration script will result
in data inconsistency between the T2000 and the NE.
Step 8 Click OK. A progress bar appears showing the status of the import.
NOTE
The script file is saved on the T2000 server. On Windows, the backup directory is \T2000\server\script.
On UNIX, the backup directory is /T2000/server/script.
----End
10.9 Restoring T2000 Data from a Remote Server

When the T2000 database fails, you can restore the T2000 data from a remote server where the

Using the Database Management Tool, you can restore the T2000 MO data from a remote server
where the T2000 MO data was backed up.
You can restore the T2000 data from a remote server where the T2000 data was backed up by
using the database management tool.


Using the Database Management Tool, you can restore the T2000 MO data from a remote server
where the T2000 MO data was backed up.
Prerequisite
l The T2000 MO data must be backed up.
l The T2000 server program must be shut down.
l The T2000 database must be initialized. Start the T2000 server program and then shut it
down.
be enabled.
Context
CAUTION
of the MO data that is used for restoration must be consistent with the T2000 version and
deployment information of the MO data to be restored.
NOTE
Procedure
NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Step 5 Enter the IP Address of Data Backup Server, Port, User Name and Password, and then click
Login.

Step 6 Click the Remote Restoration tab.
Step 7 Click in the Select Path pane, and the Select path dialog box is displayed. Select the
backup MO data on the remote server as required.
Step 8 Under the Select type area, check the Restore MO check box.
Step 9 Click Restore. When a prompt appears, click OK.

When restoring the MO data, the database management tool first checks whether the current
file package. If the information is the same, click OK in the Confirm to Restore MO dialog
box to begin to restore the T2000 MO data.
CAUTION
1. In the Confirm to Restore MO dialog box, click OK.
2. A Confirm to Restore MO dialog box is displayed indicating that the MO to be restored is
not consistent with the current deployment. The deployment info will be restored automatic
and the restoration can not be rollbacked. Are you sure to continue? In the Confirm to
Restore MO dialog box, click OK to begin to restore the T2000 deployment information.
3. After you restore the information, a message is displayed indicating that the T2000
information is restored. In addition, you are prompted to start and shut down the T2000 and
click OK to continue to restore the MO data.
4. Start and then shut down the T2000. For details, refer to Starting and Shutting Down the
T2000.
5. Click OK to restore the T2000 MO data.
----End


You can restore the T2000 data from a remote server where the T2000 data was backed up by
using the database management tool.
Prerequisite
l The T2000 database must be backed up.
l The T2000 server program must be shut down.
be enabled.
Context
CAUTION
of the T2000 database that is used for restoration must be consistent with the T2000 version and
deployment information of the T2000 database to be restored.
NOTE
Procedure
NOTE
Management Tool.
# ./T2000DM.sh

NOTE
Step 5 Enter the IP Address of Data Backup Server, Port, User Name and Password, and then click
Login.

Step 6 Click the Remote Restoration tab.
Step 7 Click in the Select Path pane, and the Select path dialog box is displayed. Select the
backup database on the remote server as required.
Step 8 Under the Select type area, check the Restore the Database check box.
Step 9 Click Restore. When a prompt appears, click OK.

When restoring the database, the database management tool first checks whether the current
file package. If the information is the same, click OK in the Confirm to Restore Database
dialog box to begin to restore the T2000 database.
CAUTION
1. In the Confirm to Restore Database dialog box, click OK.
2. A Confirm to Restore Database dialog box is displayed indicating that the database to be
restored is not consistent with the current deployment. The deployment info will be restored
automatic. Are you sure to continue? In the Confirm to Restore Database dialog box, click
OK to begin to restore the T2000 deployment information and the database.
----End
10.10 Viewing the Status of Databases

Using the System Monitor client, you can monitor the status of databases on the T2000 server.
Prerequisite
The System Monitor client must be started on the T2000 server.

Context
NOTE
To view the status of the databases by command line, run the following command as user sybase:
$ /opt/sybase/ASE-12_5/install/showserver
if the dataserver and the backupserver are running, the status of databases is normal.
Procedure
Step 1 Switch to the System Monitor client user interface.
Step 2 Click the Database tab and view the status of all the databases.
Step 3 In the Database List, select one or more entries, right-click and choose Refresh to refresh the
status of the selected database(s).
NOTE
When the database utilization exceeds the preset alarm threshold, the System Monitor server sends an alarm
to the T2000 server. At the same time, the corresponding records in the System Monitor client are displayed
in red.
----End
10.11 Dumping the T2000 Log Data

To ensure that the system runs stably and efficiently, you need to dump the alarm and
performance data to another place when the data in the database reaches a certain amount. The
data can be manually and automatically dumped.

is increased.


is increased.
Prerequisite
Procedure
Step 2 Select the Alarm Data and specify a suitable File type.
Step 3 Select the Start time and End time, and specify the alarm generation time.
Step 4 Click Dump to manually dump the alarm data.
----End
Result
text editor.

Prerequisite
Context
path.
Procedure
Step 2 Select the Alarm Data, and set the parameters of overflow dump or periodic dump.

Step 3 Set the Dump mode, File type, and Dump to (path).
NOTE
Step 4 Click OK.
----End
Result
text editor.

Prerequisite

Procedure
Step 2 Choose the performance data that you want to dump from the list and set Deadline in Instant
Dump Conditions.
Step 3 Optional: Click Query to query Number of Records (Piece) and Record Size (kB) in Record
Suitable for Instant Dump Conditions.
Step 4 Click Dump and the Confirm dialog box is displayed. Click OK to dump the performance data.
Step 5 When the dumping is complete, the Operation Result dialog box is displayed indicating the
path of saving the performance data. Click Close.
----End
Result
The manually dumped performance data is saved as a file in the specified directory, but not
NOTE

Prerequisite
Context
path.
Procedure
Step 2 Choose the performance data from the list, and set parameters of the Dumping when
Overflow or the Dumping in Schedule.

Step 3 Set the path of saving the performance data in Dump To(Path).
Step 4 Click OK.
----End
Result
The automatically dumped performance data is saved as a file in the specified directory, but not
NOTE
10.12 Clearing the T2000 Log Data

During the routine maintenance of the T2000, you can clear the unwanted log data to save spaces
for the computer.
Prerequisite

Context
CAUTION
Clearing the T2000 log data will directly delete the log data from the database. This affects the
fault location in future. You are recommended to clear the database space by dumping.
Procedure
l Clear Automatically dumped log data.
1. Choose System > Database > Dump Settings from the Main Menu.
2. In the Dump Settings window, Click Delete All Dump Files.
3. The Confirm dialog box is displayed. Click Yes.

l Clear manually dumped log data.
1. Choose System > Database > Dump Manually from the Main Menu.
2. In the Manual Dump window, Click Delete All Dump Files.

3. The Confirm dialog box is displayed. Click Yes.
----End
10.13 Configuration Upgrade Wizard

By using the upgrade wizard, you can restore the T2000 data from the existing configuration
data scripts.
Prerequisite
You must log in to the T2000 as user admin
Context
When configuration data is being uploaded from the NE, ensure that the communication between
the T2000 and the NE is normal.
Procedure
Step 1 Choose System > Configuration Upgrade Wizard from the Main Menu. The Upgrade Wizard
1 of 9: Import NE list file dialog box is displayed.
Step 2 Optional: Select a directory that contains the NE list file and click Import to import the NE list
file.
Step 3 Click Next to go to Upgrade Wizard 2 of 9: Upload NE data.

Step 4 Optional: Click Upload to upload the configuration data of the selected NE. The uploading
progress is displayed in the Upload dialog box.
Step 5 Click Next to go to Upgrade Wizard 3 of 9: Import Inactive Cross-Connection.
Step 6 Optional: Click Import Inactive Cross-Connection. The Import NE list file dialog box is
displayed. Import the inactive cross-connections of the selected NE.
Step 7 Click Next to go to Upgrade Wizard 4 of 9: Search Ason Trail.
Step 8 Optional: Click Search to search for Ason trails from the network layer in the T2000.
Step 9 Click Next to go to Upgrade Wizard 5 of 9: Import networkwide configuration file.
Step 10 Optional: Select a directory that contains the networkwide configuration file and click
Import to import the networkwide configuration file.
Step 11 Click Next to go to Upgrade Wizard 6 of 9: Search Ethernet Trail.
Step 12 Optional: Click Search to search for Ethernet trails from the network layer in the T2000.
Step 13 Click Next to go to Upgrade Wizard 7 of 9: Search WDM Trail.
Step 14 Optional: Click Search to search for WDM trails from the network layer in the T2000.
Step 15 Click Next to go to Upgrade Wizard 8 of 9: Import Customer Data.
Step 16 Optional: Click Import to import customer data.
Step 17 Click Next to go to Upgrade Wizard 9 of 9: View upgrade report.
Step 18 View the result of the upgrade and make sure that the upgrade is successful.
Step 19 Click Finish to exit the wizard.
----End

Operation Guide for Common Features 11 Backing Up and Restoring the NE Data
11 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.
11.1 Comparison of NE Data Backup and Restoration Methods

You need to back up important NE data during daily maintenance. This ensures that the SCC
board of the NE automatically restores to normal operation after the NE data in the DRDB
database of the SCC board is lost or a power failure occurs on the equipment. This section
describes several NE data backup and restoration methods. You can select the method as
required.
11.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.
11.3 Forcibly Backing Up the NE Database to an SCC Board
In the case of the SDH equipment that supports the packet feature, you can forcibly back up the
NE database to the standby SCC board if required. For example, you need to perform the forcible
backup before the switching from the active SCC board to the standby SCC board.
11.4 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.
11.5 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.
11.6 Backing Up Device Data to the NMS Server or the NMS Client
This topic describes how to manually back up the device data of multiple devices of the same
type. You can back up device data to the NMS server or the NMS client.

11 Backing Up and Restoring the NE Data Operation Guide for Common Features
11.7 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 the Flash database on the SCC
board.
11.8 Restoring the NE Database from the CF Card
When the database file is lost due to the NE maintenance or NE fault, you can restore the DRDB
database of the SCC board from the database file that is already backed up on the CF card.
11.9 Restoring Device Data from the NMS Server or the NMS Client
This topic describes how to restore the device data from the NMS Server or the NMS Client.

11.1 Comparison of NE Data Backup and Restoration

Methods
You need to back up important NE data during daily maintenance. This ensures that the SCC
board of the NE automatically restores to normal operation after the NE data in the DRDB
database of the SCC board is lost or a power failure occurs on the equipment. 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 determine different types of backup
and restoration methods. See Table 11-1.
Table 11-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 does not have 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
database 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 has 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 an 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 an 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.
11.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
You must log in to the NE as an NE user with system level authority.

Procedure
Step 1 In the Main Menu, choose Configuration > Configuration Data Management.
Step 2 In the Object Tree on the left, select an NE and click .

Step 3 In Configuration Data Management List, select an NE or multiple NEs.
Step 4 Click Back Up NE Data and then choose Back Up Database to SCC.
Step 6 The Operation Result dialog box is displayed. After the backup is successful, click Close.
----End
11.3 Forcibly Backing Up the NE Database to an SCC Board

In the case of the SDH equipment that supports the packet feature, you can forcibly back up the
NE database to the standby SCC board if required. For example, you need to perform the forcible
backup before the switching from the active SCC board to the standby SCC board.
Prerequisite
Applies to the SDH equipment that supports the packet feature.
Procedure
Step 2 In the Object Tree on the left, select an NE or multiple NEs and click .
Step 4 Choose Back Up NE Data > Forcibly Back Up to Standby SCC Board.
Step 5 In the confirmation dialog box, click OK.
----End
11.4 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

It is suitable for OptiX OSN 1500, OptiX OSN 2000, OptiX OSN 2500, OptiX OSN 3500, OptiX
OSN 7500, OptiX OSN 9500.
Procedure
Step 1 In the Main Menu, choose Configuration > Configuration Data Management.
Step 2 In the Object Tree on the left, select an NE and click .
Step 4 Choose Back Up NE Data > Back Up History Alarm to FLASH.
----End
11.5 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.
11.5.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.
11.5.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 is lost on the SCC board or a
power failure occurs on the equipment.
11.5.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.

Procedure
Step 2 In the Object Tree on the left, select an NE and click the double-right-arrow button (red).
Step 3 Select one or more NEs in the Configuration Data Management List.
Step 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.
Step 5 Click Close in the Operation Result dialog box is displayed.
----End
11.5.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 is lost on the SCC board or a
power failure occurs on the equipment.
Prerequisite
l You must have logged in to the NE as an NE user with "System Level" authority.
l The SCC board must be configured with the CF card.
Procedure
Step 2 In the Object Tree, select an NE and click .
Step 3 Select one or more NEs in the Configuration Data Management List.
Step 4 Click Back Up NE Data and then choose Manually Back Up Database to CF Card.
Step 6 Click Close in the Operation Result dialog box is displayed.
----End
11.6 Backing Up Device Data to the NMS Server or the NMS

Client
This topic describes how to manually back up the device data of multiple devices of the same
type. You can back up device data to the NMS server or the NMS client.

Prerequisite
The FTP/TFTP/SFTP server is configured and the FTP/TFTP/SFTP service is started.
l The backup operation can be performed only for multiple devices of the same type.
l When you select the device type in the device tree, all the devices and the device type
versions related to the device type are displayed in the Device View table.
l The files backed up from the server can be viewed in the Backup Information tab.
Procedure
Step 1 On the Main Topology, choose Data Center > Device Operation from the main menu. The
Device View table is displayed.
Step 2 In the Device View table, right-click the device(s) whose data you want to back up.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
Step 3 Select Backup.... The Backup dialog box is displayed.
Step 4 Select the NMS Server or NMS Client option button to back up the data of the selected device.
NOTE
By default, the NMS Server option button is selected. If the NMS Server option button is selected, the
data of the selected device is stored on the NMS server.
Step 5 Optional: If the NMS Client option button is selected, click to select the location where
the device data needs to be backed up.
Step 6 Click Start to start the backup operation for the selected device(s).
----End

11.7 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 the Flash database on the SCC
board.
Prerequisite
l You must log in to the NE as an NE user with system level authority.
l The NE data from DRDB database must be backed up to the flash database on the SCC
board.
Procedure
Step 1 Double-click an NE or ONE on the Main Topology and the NE Panel is displayed.
Step 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.
Step 3 A dialog box is displayed. Click OK to complete the reset.
----End
11.8 Restoring the NE Database from the CF Card

When the database file is lost due to the NE maintenance or NE fault, you can restore the DRDB
database of the SCC board from the database file that is already backed up on the CF card.
Prerequisite
l You must be an NM user with "NE or network operator" authority or higher.
l You must log in to the NE as an NE user with system level authority.
l The SCC card must have a CF card and the NE data in the DRDB database must be backed
up to the CF card.
Procedure
Step 2 In the Object Tree, select an NE and click .
Step 4 Click Restore NE Database. The Confirm dialog box is displayed, indicating that the
restoration of the NE database may lead to service interruption.

Step 5 Click OK to start to restore the NE database.

Step 6 Click Close.
----End
Postrequisite
After the NE database is restored, the database on the CF card is restored to the DRDB database
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.
11.9 Restoring Device Data from the NMS Server or the

NMS Client
This topic describes how to restore the device data from the NMS Server or the NMS Client.
Prerequisite
l The FTP/TFTP/SFTP server is configured and the FTP/TFTP/SFTP service is started.
l To restore the device data from the NMS client, the SFTP server must be configured, and
the SFTP service must be started.
l You cannot restore device data for multiple devices of different device types.
l When you select the device type in the device tree, all the device information related to the
device type is displayed in the Device View table.
Procedure
Step 1 On the Main Topology, choose Data Center > Device Operation from the main menu. The
Device View table is displayed.
Step 2 In the Device View table, right-click the device(s) whose data you want to restore.
Step 3 Select Recover... to open the Recover dialog box.
Step 4 Select the backup file to be restored from the File Name drop-down list. If the backup files are
not listed in the File Name drop-down list, select Browse... to select the backup file to be restored
in the Select File dialog box, as shown below.

Step 5 Select the NMS Server or NMS Client option button to restore the backup file for the selected
device(s). By default, the NMS Server option button is selected.
l If the NMS Server option button is selected, select the backup file to be restored from the
NMS Server. The selected backup file path is displayed in the Select File dialog box.
l If the NMS Client option button is selected, click to select the backup file to be
restored from the NMS client. The selected backup file path is displayed in the following
Selected File dialog box.
Step 6 Click OK.
The selected backup file path from the NMS Server or NMS Client is displayed in the File
Name drop-down list.
Step 7 Click Start and the Operation Confirmation dialog box is displayed. Click Yes to start the
restoration operation.
----End
Result
After you restore the device data, right-click the device in the Device View table, and choose
Activation Database... from the shortcut menu. The Activation Database dialog box is
displayed. Click Start to activate the device database.
NOTE
If you do not activate the software within five minutes after the restoration is successfully complete, the
T2000 automatically rolls back the software and cancels the restoration operation.

Operation Guide for Common Features 12 Viewing Reports
12 Viewing Reports
About This Chapter
The reports provide information regarding the network parameters and running status. From the
viewpoint of the entire network, the reports include the networking diagram and the timeslot
allocation diagram. From the viewpoint of the NEs and the boards, the reports include NE and
board information reports. All these reports help during network maintenance.
12.1 Report Types Supported by the T2000

The T2000 provides a variety of reports that help you to query and save information.
12.2 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.
12.3 Viewing the Clock Tracing Diagram
The clock tracing diagram includes NE information such as ID, extended ID, name, 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.
12.4 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.
12.5 Viewing the NE Information Report
In the NE information report, you can view the information of all NEs in the network, such as
NE name, NE type, subrack type, NE ID, extended ID, NE version, number of fiber/cable,
affiliated subnet, affiliated ONE, gateway type, gateway attributes and so on.
12.6 Viewing the Physical Location Information Report
The physical location information report includes the physical equipment information of the
equipment room, cabinet and subrack. The information is useful when planning the subrack
positions in an equipment room.

12 Viewing Reports Operation Guide for Common Features
12.7 Viewing the Equivalent NE Statistics Report

In this report, you can view the number of the actual NEs that are managed by theT2000 based
on NE types and the number of corresponding equivalent NEs.
12.8 Viewing the Port Resource Statistics Report
In this report, you can view different types of ports that are used by services or protection.
12.9 Viewing the Board Information Report
The board information includes the board type, status, BIOS version, software version, Logic
version, PCB version, and the associated NE and slot. After configuring or updating a board,
update the board information in time to facilitate management of the board.
12.10 Viewing the Slot Information Report
The slot information report provides board information from the viewpoint of slots. The
information includes the logical and physical boards in a slot, whether a board is created by
using the T2000, whether a board is online, and the attributes (ID and relevant NE) of a board
slot. When configuring a new board, you need to query the slot information. You can update the
slot information report when there is any change with board slots.
12.11 Viewing the Board Count Report
The board count report provides information about the board types on an NE and the number of
boards of each type.
12.12 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.
12.13 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.
12.14 Viewing WDM NE Master/Slave Subrack Info Report
By viewing the WDM NE master/slave subrack information report, you can learn about the basic
information of the master/slave subrack on an optical NE, such as the subrack name, subrack
equipment type, and slave subrack ID.
12.15 Viewing the Lower Order Cross-Connection Statistics Report
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.
12.16 Viewing the WDM Protection Group Switching Status Report
You can view the switching status of all WDM protection groups in a network in the WDM
protection group switching status report.
12.17 Browsing the Fiber Cable/Radio Link Resource Occupancy
You can collect the occupancy of the fiber cable/radio link resource in a topological subnet or
a protection subnet. Based on the occupancy, you can plan the services.

12.1 Report Types Supported by the T2000

The T2000 provides a variety of reports that help you to query and save information.
Reports are classified into two types, which are equipment configuration reports and service
configuration reports.
l The equipment configuration report provides the equipment hardware configuration
information. You can refer to this information at the initial stage of network construction.
l The service configuration report provides the service configuration information. You can
refer to this information during the network maintenance.
After a report is generated, it can be filtered, viewed, printed or saved as a file. The file could
be in text format, html format or Excel spread sheet format. In the T2000 user interface, almost
all the data in the form of a list can be exported to a report and printed.
12.2 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
Step 1 Choose Report > Networking Diagram from the Main Menu. View the information in the
generated networking diagram.
Step 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).
Step 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.
Step 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.
Step 5 Optional: In the networking diagram, right-click and choose Font Size from the shortcut menu
to select a proper font size.

Step 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.
Step 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.
Step 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
12.3 Viewing the Clock Tracing Diagram

The clock tracing diagram includes NE information such as ID, extended ID, name, 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
Step 1 Choose Report > Clock Tracing Diagram from the Main Menu. View the information in the
generated clock tracing diagram.
Step 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.
Step 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.
Step 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.

Step 5 Optional: In the clock tracing diagram, right-click and choose Page from the shortcut menu to
set the page size of the diagram.
Step 6 Optional: In the clock tracing diagram, right-click and choose Font Size from the shortcut menu
to select the appropriate font size.
Step 7 Optional: In the clock tracing diagram, right-click and choose Print or Save As to output the
report.
----End
12.4 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 T2000 exports the timeslot assignment diagram in SVG format. To view or print the
diagram, install the SVG Viewer. On Windows, refer to client\SVG\PC\pcreadme.txt on how
to install the SVG Viewer; On UNIX, refer to client/SVG/Unix/unixreadme.txt. The
installation process takes five minutes or less.
Procedure
Step 1 Choose Report > Timeslot Allocation Diagram from the Main Menu.
Step 2 Select a protection subnet in the Generate Timeslot Allocation Diagram dialog box. Click
Start. The T2000 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 T2000 automatically creates is saved in the client/
report directory.
Step 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
12.5 Viewing the NE Information Report

In the NE information report, you can view the information of all NEs in the network, such as
NE name, NE type, subrack type, NE ID, extended ID, NE version, number of fiber/cable,
affiliated subnet, affiliated ONE, gateway type, gateway attributes and so on.
Prerequisite
Procedure
Step 1 Choose Report > NE Information Report from the Main Menu.
Step 2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red). The
information of the selected NEs is displayed on the right.
Step 3 Click Query to query the information from the NE.

Step 4 Optional: Click Print or Save As to output the report.
----End
12.6 Viewing the Physical Location Information Report

The physical location information report includes the physical equipment information of the
equipment room, cabinet and subrack. The information is useful when planning the subrack
positions in an equipment room.
Prerequisite
The subrack information must be modified according to the actual situations. In addition, the
cabinet and equipment room information must be created.
Procedure
Step 1 Choose Report > Physical Location Information Report from the Main Menu.
Step 2 Click the Equipment Room, Cabinet or Subrack tab to view the information.
----End
12.7 Viewing the Equivalent NE Statistics Report

In this report, you can view the number of the actual NEs that are managed by theT2000 based
on NE types and the number of corresponding equivalent NEs.
Prerequisite
Procedure
Step 1 Choose Report > Equivalent NE Statistics Report from the Main Menu.
Step 2 Click Query, view the Equivalent NE Statistics Report.
----End

12.8 Viewing the Port Resource Statistics Report

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 T2000 by using the trail search.
Procedure
Step 1 Choose Report > Port Resource Report from the Main Menu.
Step 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.
Step 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 information in the report is displayed in red.
l 70% to 89%: Emergency Threshold. The corresponding information in the report is displayed in orange.
l 60% to 69%: Attention Threshold. The corresponding information in the report is displayed in yellow.
l Less than 60% means normal. The corresponding information in the report is in the regular color.
----End
12.9 Viewing the Board Information Report

The board information includes the board type, status, BIOS version, software version, Logic
version, PCB version, and the associated NE and slot. After configuring or updating a board,
update the board information in time to facilitate management of the board.
Prerequisite
The board software (of the board that you want to query) supports querying of the board version
information.
Procedure
Step 1 Choose Report > Board Information Report from the Main Menu.
Step 2 Click the Board Information Report tab.

Step 3 In the Object Tree, select one or more NEs or a or more board on the NE and click the double-
right-arrow button (red). You can view the generated report in the right-hand pane.
NOTE
Enter the information in the Remarks field and click Apply to save the information.
----End
Result
NOTE
If the number of the queried boards is different from the number of actual boards, you can upload the NE
data and then query the boards again.
12.10 Viewing the Slot Information Report

The slot information report provides board information from the viewpoint of slots. The
information includes the logical and physical boards in a slot, whether a board is created by
using the T2000, whether a board is online, and the attributes (ID and relevant NE) of a board
slot. When configuring a new board, you need to query the slot information. You can update the
slot information report when there is any change with board slots.
Prerequisite
The board must be installed.
information.
Procedure
Step 2 Click the Slot Information Report tab.
Step 3 In the Object Tree, select one or more NEs or boards and click the double-right-arrow button
(red). You can view the generated report in the right-hand pane.


Step 6 Optional: Click Statistics of Number of Boards to view the number of physical boards, logical
boards and offline boards.
----End
12.11 Viewing the Board Count Report

The board count report provides information about the board types on an NE and the number of
boards of each type.
Prerequisite
Procedure
Step 2 Click the Board Count Report tab.
Step 3 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.

NOTE
The Bord Count displays the count of logical board.
----End
12.12 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.
Prerequisite
information.
Procedure
Step 1 Choose Report > Board Manufacturer Information Report from the Main Menu.
Step 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.
----End
12.13 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
information.

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
Step 1 Choose Report > Board Manufacturer Information Report from the Main Menu. Click the
Common Manufacturer Information tab.
Step 2 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.
Step 3 Click Query to query the actual common manufacturer information from the NE.
----End
12.14 Viewing WDM NE Master/Slave Subrack Info Report

By viewing the WDM NE master/slave subrack information report, you can learn about the basic
information of the master/slave subrack on an optical NE, such as the subrack name, subrack
equipment type, and slave subrack ID.
Prerequisite
Procedure
Step 1 Choose Report > WDM NE Master/Slave Subrack Info Report from the Main Menu.
Step 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 subrack information report.
Step 3 Click Query to query the actual WDM NE master/slave subrack information from the NE.
Step 4 Optional: Click Print to print the report or click Save As to export the report.
----End
12.15 Viewing the Lower Order Cross-Connection Statistics

Report
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
Lower order cross-connections must be created.
Procedure
Step 1 Choose Report > Lower Order Cross-Connections Statistic Report from the Main Menu.
Step 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 T2000.
NOTE
l Only NEs that support lower order cross-connection querying are displayed in the Object Tree.
l There are alerts of different levels that correspond to different thresholds of used lower order cross-
connections. The default levels of alerts are as follows:
l 90% to 100%: urgent alert. The corresponding information in the report is in red.
l 70% to 89%: emergency alert. The corresponding information in the report is in orange.
l 60% to 69%: attention alert. The corresponding information in the report is in yellow.
l Less than 60%: normal. The corresponding information in the report is in the normal color.
l Click Alarm Threshold Set to set the alert thresholds. You must be an NM user with "NM operator"
authority or higher.
----End
12.16 Viewing the WDM Protection Group Switching Status

Report
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
T2000 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
Step 1 Choose Report > WDM Protection Group Switching State Report from the Main Menu.
Step 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 WDM protection group switching status report of the
selected NE queried from the T2000.

Step 3 Click Query to refresh the switching status of the protection groups from the NE.
----End
12.17 Browsing the Fiber Cable/Radio Link Resource

Occupancy
You can collect the occupancy of the fiber cable/radio 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 T2000 vary with different licenses.
Procedure
Step 1 Choose Report > Fiber Cable/Radio Link Occupancy Resources from the Main Menu.
Choose Statistics by Affiliated Subnet or Statistics by Protection Subnet tab.
Step 2 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.
NOTE
Click Alarm Threshold Set, you can view or modify the threshold value. If the fiber cable/radio link
resource occupancy reaches a specified threshold, a pre-alarm at different levels is generated.
----End

Operation Guide for Common Features 13 Appendix
13 Appendix
About This Chapter
You can refer to the reference information related to the T2000.

The following is covered:
13.1 Performing Remote Maintenance
You can perform remote maintenance by using the T2000 by following the instructions below.
13.2 Mutual Exclusion List for Multiclient Operations
The mutual exclusion list for multiclient operations is given below.
13.3 Timeslot Numbering Policy
As the ITU Recommendations do not define in what order VC12 timeslots are arranged in a
VC4, currently there are two timeslot numbering policies: by order (ITU-T) and interleaved.
13.4 Configuration Data Management Information List
The configuration data management information list describes whether each T2000 function
supports upload, download, consistency check or data replication.
13.5 Standards Followed
The standards followed are listed below.

13 Appendix Operation Guide for Common Features
13.1 Performing Remote Maintenance

You can perform remote maintenance by using the T2000 by following the instructions below.
13.1.1 Remote Maintenance
Remote maintenance involves monitoring and maintaining remote equipment by using the
T2000. It is a common maintenance method for remote fault location and periodical check. When
the equipment is faulty, you can perform remote maintenance to locate and solve the problem
in time. In this way, on time maintenance is guaranteed. Remote maintenance is also used to
periodically check remote equipment so that the equipment security is guaranteed.
conditions.
13.1.3 Performing Remote Maintenance
You can perform remote maintenance by using the T2000.
13.1.1 Remote Maintenance

Remote maintenance involves monitoring and maintaining remote equipment by using the
T2000. It is a common maintenance method for remote fault location and periodical check. When
the equipment is faulty, you can perform remote maintenance to locate and solve the problem
in time. In this way, on time maintenance is guaranteed. Remote maintenance is also used to
periodically check remote equipment so that the equipment security is guaranteed.
The Figure 13-1 shows the networking of remote maintenance.
Figure 13-1 Remote Maintenance
The remote maintenance terminal serves as the access client, and the T2000 server serves as the
access server. The remote maintenance process is as follows:

1. Set up the communication for remote maintenance.

(1) Set the access client.
(2) Set the access server.
(3) Set up the communication.
2. Perform remote maintenance.
(1) Start the T2000 server as the access server.
(2) Start the client on the remote maintenance terminal.
(3) Perform remote maintenance.

conditions.
Prerequisite
Procedure
Maintenance User Management dialog box is displayed. Enable the remote maintenance user
and set its other parameters.
Step 2 Click OK.

----End

13.1.3 Performing Remote Maintenance

You can perform remote maintenance by using the T2000.
Prerequisite
l The communication between the remote maintenance terminal and the T2000server must
be set up.
Context
To ensure network security, set the remote maintenance user to Disabled when the remote
maintenance is complete.
Procedure
Step 1 On the remote maintenance terminal, run the T2000\cmdclient\bin\cmdClient.bat file (for
Windows) or the /T2000/cmdclient/bin/cmdClient.sh file (for UNIX).
Step 2 To log in to the T2000, enter the password of the remote maintenance user and the IP address
of the T2000server. After successful login, the NEs managed by the T2000server are displayed
in the object list (the gateway NEs of all subnets are displayed by default).
NOTE
The IP address must be followed by the port number 9801, which cannot be changed or omitted.
Step 3 Click the gateway NE to display all NEs in the subnet and double-click an NE to log in.
Step 4 Enter the command in the input box (this tool supports all host commands for the maintained
equipment), and click Send to issue the command to the NE.
Step 5 When the remote maintenance is complete, select Remote Maintenance Report > Create to
create a remote maintenance report.
NOTE
l In Windows, the remote maintenance report is saved to the T2000\cmdclient\report directory of the
T2000 client.
l In UNIX, the remote maintenance report is saved to the T2000/cmdclient/report directory of the
T2000 client.
----End
13.2 Mutual Exclusion List for Multiclient Operations

The mutual exclusion list for multiclient operations is given below.

Figure 13-2 Mutual exclusion list for multiclient operations
protection subnets
section parameter
protection subnet
Create protection
Delete protection
Check protection
Check multiplex
Deactivate trail
Create/Modify/
Duplicate trail
Delete SNCP
Search for trail
Duplicate trail
Export script
Duplicate NE
Import script
Consistency
Delete fiber
T2000 data
Delete trail
Search for
Download
Delete all
View trail
Activate/
Initialize
Set trail
Upload
Step 1
subnet
subnet
check
subnet
node
data
Search for
trail
View trail
Activate/
Deactivate trail
Create/Modify/
Duplicate trail
Delete trail
Duplicate
trail Step 1
Delete fiber
Create protection
subnet
Delete protection
subnet
Delete all
protection subnets
Search for
protection subnet
Download
Upload
Consistency
check
Initialize
T2000 data
Duplicate NE
data
Import script
Export script
Set trail
Delete SNCP
node
Check protection
subnet
Check multiplex
section parameter
Compatible Mutually
exclusive

Figure 13-3 Mutual exclusion list for multiclient operations on ASON SDH trails
Figure 13-4 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.
13.3 Timeslot Numbering Policy

As the ITU Recommendations do not define in what order VC12 timeslots are arranged in a
VC4, currently there are two timeslot numbering policies: by order (ITU-T) and interleaved.
By Order
The timeslot numbering by order is shown in Figure 13-5.
NOTE
Huawei uses the by order mode.
Figure 13-5 The by order mode
The calculation formula for VC12 numbering by order is as follows: VC12 number = TUG3
number + (TUG2 number - 1) x 3 + (TU12 number - 1) x 21
Interleaved
The timeslot numbering in the interleaved mode is shown in Figure 13-6.

Figure 13-6 The interleaved mode
The calculation formula for VC12 numbering in the interleaved mode is as follows: VC12
number = (TUG3 number - 1) x 21 + (TUG2 number - 1) x 3 + TU12 number
The Timeslot Numbering Policy for Interconnection with Third-Party Equipment

When equipment from different vendors requires 2 Mbit/s service interconnections, service
configuration is not easy as the same VC12 in a VC4 can be numbered differently depending
on the numbering policy used by a vendor. As a result, you need to translate the VC12 number.
The T2000V2 processes timeslot numbering as follows:
l The T2000V2 does not allow you to query and set the timeslot mode for a single NE. Hence,
the by order mode is used by default on the T2000regardless of which mode is set on the
NE. For a single NE, you can query and set the timeslot mode using the Qx interface.
l To set the timeslot mode on the T2000, you can modify the slotmodflg item in the ems.cfg
file. If the value of slotmodflg is 1, it indicates the timeslot mode is interleaved on the
T2000. If the value of slotmodflg is 0, it indicates the timeslot mode is by order on the
T2000. The default timeslot mode is by order.
l In the T2000 V200R002C01 and later versions, a button is added to switch the timeslot
mode. The switching operation only switches the display of the user interface. This change
is not applied to the NE and the timeslot configuration on the NE is not affected.
13.4 Configuration Data Management Information List

The configuration data management information list describes whether each T2000 function
supports upload, download, consistency check or data replication.
The configuration data management information list contains the following:
13.4.1 General Configuration Data Management Information List
The table describes the general configuration data management information.
13.4.2 SDH Configuration Data Management Information List
The table describes the SDH configuration data management information.
13.4.3 PTN Configuration Data Management Information List
The table describes the PTN configuration data management information.

13.4.4 WDM Configuration Data Management Information List

The table describes the WDM configuration data management information.
13.4.5 NG WDM Configuration Data Management Information List
The table describes the NG WDM configuration data management information.
13.4.6 RTN Configuration Data Management Information List
The table describes the RTN configuration data management information.
13.4.7 Ethernet Configuration Data Management Information List
The table describes the Ethernet configuration data management information.
13.4.8 ATM Configuration Data Management Information List
The table describes the ATM configuration data management information.
13.4.9 ASON Configuration Data Management Information List
The table describes the ASON configuration data management information.
13.4.10 DDN Configuration Data Management Information List
The table describes the DDN configuration data management information.
13.4.11 Alarm and Performance Configuration Data Management Information List
The table describes the alarm and performance configuration data management information.
13.4.1 General Configuration Data Management Information List

The table describes the general configuration data management information.
Function Function Uploa Downlo Consistenc Data

List d ad y Check Replicatio
n
Virtual NE Virtual NE ID N N N N
Basic (Extension ID + NE ID)
Configurati
on Virtual NE Name N N N N
Boards Installed in an N N N Y
Virtual NE
Board Type Board Type Definition N N N N

Definition
for an
Virtual NE
NE NE Name Y Y Y N
Attributes
NE Location N N N N
NE Remarks Y Y N Y
SDH Timeslot Y Y Y Y
Configuration Mode
(Huawei Mode/Lucent
Mode)
Set NE type and subrack Y N Y Y

type


n
Support Time Division Y N N Y

Mode
PMU Relay Control Mode Y Y Y Y
State of the Alert Relay Y Y Y Y

K0
State of the Alert Relay Y Y Y Y

K1
Second Power Supply in Y Y Y Y

use or not
Temperature Upper Y Y Y Y
Limit
Temperature Lower Y Y Y Y
Limit
EMU Serious Overvoltage Y Y Y Y
Common Overvoltage Y Y Y Y
Serious Undervoltage Y Y Y Y
Common Undervoltage Y Y Y Y
Upper Limit of the Y Y Y Y

Temperature Value
Lower Limit of the Y Y Y Y

Temperature Value
Input Channel Name Y Y Y Y
Output Channel Name Y Y Y Y
Use or Not Y Y Y Y
Working Mode Y Y Y Y
Corresponding Input Y Y Y Y
Alarm Mode Y Y Y Y
CAU Interface N Y N N
FAN Interface N N N N
OHP General OHP Attributes Y Y Y Y

Interface
Advanced OHP Y Y Y Y
Attributes


n
Auxiliary OHP Y Y Y Y
Attributes
F1 Data Port Y Y Y Y
Conference Call Y Y Y Y
Set Broadcast Data Port Y Y Y Y
COMM Y Y Y Y
Data Port & Outgoing Y Y Y Y

Loop Route
Subnet Number Y Y Y Y
Supported by the
Optical Interface
Equipment Board Temperature N N N N

Maintenanc Threshold
e
SET NE Fan N N N N
Save Board N N N N
Configuration
NE Auto Release Y N N N
NE Security Advanced ACL N N N N
Syslog N N N N
13.4.2 SDH Configuration Data Management Information List

The table describes the SDH configuration data management information.
Function Function Upload Downloa Consiste Data

List d ncy Replicati
Check on
PDH Tributary loopback Y N N N

Interface
Path protection Y Y Y Y
Path impedance N N N N
Service load indication Y Y Y Y

(load/unload)
Input signal equalization Y Y Y Y
Output signal equalization Y Y Y Y


Check on
Pattern (T1 pattern B8ZS/ Y Y Y Y

AMI)
Path service type (E1/T1) Y Y Y Y
Path phase lock Y Y Y Y
Tributary timing mode Y Y Y Y
Service selection Y Y Y Y
Retiming mode Y Y Y Y
External retiming clock Y Y Y Y

source
SXT working mode Y Y Y Y
Retiming working mode Y Y Y Y
Path using status Y Y Y N
CRC4 Y Y Y Y
E1 frame structure Y Y Y Y
T1 frame structure Y Y Y Y
Output tunable Y Y Y Y
wavelength
J2 byte to be transmitted Y Y Y Y
J2 byte to be received Y Y Y Y
J2 byte received N N N N
Path name N N N N
Port protocol mode of Y Y Y Y

tributary path
SDH Laser switch N N N N

Interface
Optical interface loopback Y N N N
VC4 loopback Y N N N
VC4 overhead termination N N N N
AIS insertion due to B3 N N N N

byte threshold-crossing
SPQ4 port working mode Y Y Y Y
FEC working status Y Y Y Y


Check on
Have SDH interface board N N N N

or not
Laser-in-position status N N N N
Set automatic laser N N Y N

shutdown (ALS)
ALS time parameter N N Y N
Line board optical port Y Y Y Y

REG enabled
Optical port overhead Y Y Y Y

mode
DCC/GCC mode Y Y Y Y
Enable source of tandem Y Y Y Y

connection
Enable sink of tandem Y Y Y Y

connection
APId value to be Y Y Y Y
transmitted at source
APId value to be received Y Y Y Y

at sink
APId byte mode at source Y Y Y Y
APId value received at N N N N

sink
APId byte mode at sink Y Y Y Y
Laser switch transmission N N N N

distance
Scheduled release of port N N N N

loopback
SDH optical port output N N N N

wavelength
SDH optical port input N N N N

wavelength
Shared attributes of the Y Y Y Y

multiplexing section


Check on

distance
Number of outputs of the N N N N

alarm relay
Regenerato J0 to be transmitted Y Y Y Y
r Section
Overhead J0 to be received Y Y Y Y
J0 received N N N N
Higher J1 to be transmitted (VC4 Y Y Y Y

Order Path path)
Overhead
J1 to be received (VC4 Y Y Y Y
path)
J1 received (VC4 path) N N N N
C2 to be received (VC4 Y Y Y Y
path)
C2 to be transmitted (VC4 Y Y Y Y
path)
C2 received (VC4 path) N N N N
J1 to be transmitted (VC3 Y Y Y Y
path)
J1 to be received (VC3 Y Y Y Y
path)
J1 received (VC3 path) N N N N
C2 to be received (VC3 Y Y Y Y
path)
C2 to be transmitted (VC3 Y Y Y Y
path)
C2 received (VC3 path) N N N N
J1 to be received (PDH Y Y Y Y
Board)
J1 to be transmitted (PDH Y Y Y Y
Board)
Lower J2 to be transmitted Y Y Y Y
Order Path
Overhead J2 to be received Y Y Y Y
J2 received N N N N


Check on
V5 to be sent N N N N
V5 to be received N N N N
V5 received N N N N
VC12 path V5 to be Y Y Y Y
transmitted (EFGS)
VC12 path V5 to be Y Y Y Y
received (EFGS)
VC12 path V5 received N N N N

(EFGS)
SDH Clock Synchronization status N N N N

Interface
Clock source priority Y Y Y Y
Clock failure conditions Y Y Y Y
Phase-locked source Y Y Y Y
output by external clock
Clock source switching N N N N
Clock subnet Y Y Y Y
TDA clock source Y Y Y Y

configuration
Clock source restoration Y Y Y Y

parameter
SSM output control Y Y Y Y
Clock source quality Y Y Y Y
Clock ID status Y Y Y Y
Setting for 0 level clock Y Y Y Y

quality
Customer clock quality Y Y Y Y
2M phase-locked source Y Y Y Y
priority list
Clock binding Y Y Y Y
Test Automatic laser shutdown N N N N

Function
2M pseudo number test N N N N


Check on
Frame overhead N N N N
information management
PRBS test N N N N
SDH SDH common cross- Y Y Y Y

Service connect
SNC protection group Y Y Y Y
SNC protection group Y Y Y Y

board mapping
Multi-trail protection Y Y Y Y
group
SDH SDH common cross- N N N N

Service of connect
Virtual NE
SNC protection group N N N N
SNC protection group N N N N

board mapping
Multi-trail protection N N N N
group
SNC Hold-off time Y Y Y Y

Service
Attributes Switching WTR time Y Y Y Y
Revertive mode Y Y Y Y
Monitoring condition Y Y Y Y
Service group Y Y Y Y
Service type Y Y Y Y
Current status N N N N
Overhead Overhead service Y Y Y Y

Service
SNC Hold-off time N N N N

Service
Attributes Switching WTR time N N N N
of Virtual Revertive mode N N N N
NE
Monitoring condition N N N N
Service group N N N N
Service type N N N N


Check on
Current status N N N N
Multi-Trail Hold-off time Y Y N Y

Service
Attributes Switching WTR time Y Y N Y
Revertive mode Y Y N Y
Monitoring condition Y Y N Y
Logical Logical system ID Y Y Y Y

System
Name Y Y Y Y
Type Y Y Y Y
STM level Y Y Y Y
Topology type Y Y Y Y
Fiber/Cable number Y Y Y Y
Service direction Y Y Y Y
Node type Y Y Y Y
Protection type Y Y Y Y
Slot mapping Y Y Y Y
Multiplex MS protection group Y Y Y Y

Section protocol type
MS local node ID Y Y Y Y
MS west node ID Y Y Y Y
MS east node ID Y Y Y Y
MS max. node ID Y Y Y Y
MS switching revertive Y Y Y Y
time
MS SD enabled flag Y Y Y Y
MS suppression enable Y Y Y Y
flag
Configure MS N Y N N
suppression on all spans
Logical Logical system ID N N N N

System of
virtual NE Name N N N N


Check on
Type N N N N
STM level N N N N
Topology type N N N N
Fiber/Cable number N N N N
Service direction N N N N
Node type N N N N
Protection type N N N N
Slot mapping N N N N
MS protection group N N N N
protocol type
MS local node ID N N N N
MS west node ID N N N N
MS east node ID N N N N
MS switching revertive N N N N
time
MS SD enabled flag N N N N
Logical Logical system relation ID Y Y Y Y

System
Relation Protection type Y Y Y Y
Revertive mode Y Y Y Y
Switching mode Y Y Y Y
Slot mapping Y Y Y Y
MS switching revertive Y Y Y Y
time
MS SD enabled flag Y Y Y Y
Equipment Protection group ID Y Y Y Y

1+1
Protection Active board Y Y Y Y
Standby board Y Y Y Y
Level Y Y Y Y
Protection type Y Y Y Y


Check on
TPS Protection group ID Y Y Y Y

protection
Enabled or not Y Y Y Y
Revertive time Y Y Y Y
Protection unit ID Y Y Y Y
Protection unit slot Y Y Y Y
Protection unit priority Y Y Y Y
Switching status/Lock N N N N
status
64 kbit/s 64 kbit/s service Y Y Y Y

Service
Equipment TDA feeding choices Y Y Y Y

Maintenan
ce
basic Dynamic port Y Y Y Y

configurati
on
Port Protection group ID Y Y Y Y

Protection
WTR time and revertive Y Y Y Y
mode
Hold-off time Y Y Y Y
Protection unit and Y Y Y Y

working unit
Switching status/Lockout N N N N
status
NE Time NE Y Y N N
Localizatio
n Time zone Y Y N N
Manageme Daylight saving time Y Y N N
nt
Daylight saving time rule Y Y N N
Daylight saving time Y Y N N

offset
Start time Y Y N N
End time Y Y N N
IF Interface IF port working mode Y N Y Y


Check on
IF port loopback Y N N N
Single-Port Enable single-port Y Y Y Y

Multiple multiple multiplex section
Multiplex
Section
SNCTP Group ID Y Y Y Y
Group
Slot mapping information Y Y Y Y
of working channel

of protection channel
WTR rime of a protection Y Y Y Y

group
Revertive mode of a Y Y Y Y
protection group
Trigger condition and Y Y Y Y

hold-off time of working
channel

hold-off time of protection
channel
High Configure 1588 packet Y Y Y Y

Precision
Time High precision clock Y Y Y Y
Transmissi priority table
on configure clock port Y Y Y Y
Configure the external Y Y Y Y

port of a clock
Multiplex Check the standby channel Y Y Y Y

section
IF 1+1 protection Y Y Y Y
protection
group
N+1 protection Y Y Y Y
Board 1+1 Optimize higher order Y Y Y Y

protection pass-through
MSTP Ethernet service E-LAN/ Y N Y Y

+Packet E-LINE/E-AGGR
features


Check on
V-UNI group Y N Y Y
Service QoS Y N Y Y
Ethernet OAM Y N Y Y
Management of basic Y N Y Y
ports
Management of link Y N Y Y
aggregation group
OAM management of Y N Y Y
ports
Static Tunnel Y N Y Y
Basic management of Y N Y Y
MPLS
Tunnel OAM Y N Y Y
Tunnel protection group Y N Y Y
PW management Y N Y Y
QinQ Link Y N Y Y
Overhead Y N Y Y
13.4.3 PTN Configuration Data Management Information List

The table describes the PTN configuration data management information.
Function Function Uplo Downl Consistenc Data

List ad oad y Check Replication
CES CES service Y N Y Y

service
ATM ATM service Y N Y Y

service
ATM ATM OAM Y N Y Y

OAM
Ethernet E-LAN/E-LINE/E- Y N Y Y
service AGGR
Clock 1588 Clock service Y N Y Y

service


Clock ACR clock Y N Y Y

service
Clock TOP clock Y N Y Y

service
UDP PW Basic configuration for Y N Y Y

basic the UDP PW
configurati
on
V-UNI V-UNI group Y N Y Y

group
Service Service QoS Y N Y Y

QoS
Ethernet Ethernet OAM Y N Y Y

OAM
Port Basic port Y N Y Y

manageme
nt Serial port Y N Y Y
Link aggregation group Y N Y Y

(LAG)
ATM IMA port Y N Y Y
Virtual Ethernet port Y N Y Y
MLPPP Y N Y Y
Port OAM Port OAM Y N Y Y
Dynamic Dynamic tunnel Y N Y Y

tunnel
Static Static tunnel Y N Y Y

tunnel
Basic Basic configuration of Y N Y Y

configurati the MPLS
on of the
MPLS
Tunnel Tunnel OAM Y N Y Y

OAM
Tunnel Tunnel protection Y N Y Y

protection group
group


PW PW management Y N Y Y
manageme
nt
GRE GRE Tunnel Y N Y Y

Tunnel
IP Tunnel IP Tunnel Y N Y Y
QinQ Link QinQ Link Y N Y Y
TPS TPS Y N Y Y
Board 1+1 Board 1+1 protection Y N Y Y

protection
Basic Basic configuration Y N Y Y

configurati
on
Usage Usage Y N Y Y
Dynamic Dynamic L3VPN Y N Y Y

L3VPN management
manageme
nt
Routing Routing protocol Y N Y Y

protocol
13.4.4 WDM Configuration Data Management Information List

The table describes the WDM configuration data management information.

Check on
Board Auto-Negotiation of Y Y Y Y
parameter the LDG Board
Monitor Wavelength Y Y Y Y
Searching time interval Y Y Y Y

of Wavelength monitor
Board
Monitoring Channel Y N N N
Board Monitor
Channel Wavelength


Check on
Board clock mode N N N N
Board Receiving/ Y N N N
Transmitting
Attributes
Board Cross- Y N N N
connection loopback
Optical booster Y N N N
amplifier board gain
Return the SCC board N N N N

clock
Board tracing clock Y Y Y Y

source
Status of MCA board Y N N N

optical switch
Laser status Y N N N
Optical interface for Y Y Y Y

orderwire
Optical interface Y Y Y Y
attenuation rate
Input power N N N N
Output power N N N N
Max. attenuation rate Y N N N
Min. attenuation rate Y N N N
WBA Output Power Y N N N
Path Using Status Y Y Y N
LDG Board loopback Y N N N
Synthesized input N N N N
optical power loss of
threshold
Synthesized output N N N N
threshold
Max. packet length of Y Y Y Y

Ethernet Access Board


Check on
OTU Working Y Y Y Y
Wavelength
OTU planning Y Y Y Y
wavelength
OADM add/Drop Y N N N
wavelength
OUT band type Y Y Y Y
OADM band type Y Y Y Y
OUT planned band Y Y Y Y
Working Waveband of Y N N N
Optical Layer Board
Working Waveband Y N N N
Parity of Optical Layer
Board
Automatic Laser Y N N N
Shutdown
RPC natural band Y Y Y Y
Current working Y Y Y Y
waveband
Whether VOA is Y N N N
available in the board
Flow control enabled Y Y Y Y
OCP optical interface N N N N

switching status
Service type Y Y Y Y
Whether FEC is Y Y Y Y
allowed
Optical interface rate at Y Y Y Y

the client
Max. optical interface Y N N N

rate at the client
Min. optical interface Y N N N

rate at the client
Optical interface rate Y Y Y Y

frequency band


Check on
Board Clock Source Y Y Y Y

Configuration (OCU,
LQS, LGS, SMC)
Enable wavelength Y Y Y Y
identification
Received wavelength Y N N N
identification
Identification for Y Y Y Y
wavelength to be
received
Insertion Loss (You Y N N N

can only query the real-
time status)
Nominal Gain Y Y N Y
Optical Port Remarks Y Y Y Y
Service Working Mode Y Y Y Y
Client-side Service Y Y Y Y
Protocol
Board Working Mode Y Y Y Y
Service Type to Be Y Y Y Y
Sent
Service Type Received Y N N N
LOS Alarm Threshold N N N N
LOG Working Mode Y Y Y Y
Set ESC Auxiliary Y Y Y Y

Switch
Min. Fixed Pump Y N N N

Optical Power
Max. Fixed Pump Y N N N

Optical Power
Fixed Pump Optical Y Y Y Y

Power
Single Path Y Y Y Y
Attenuation Rate
Adjustment


Check on
Path Attenuation Rate Y N N N
Wavelength ID Y N N N
Received
Wavelength ID to Be Y Y Y Y
Received
Service Rate Y Y Y Y
Guaranteed Bandwidth Y Y Y Y
for Client GE Services
Enable LPT Y Y Y Y
Add/Drop Band Y N N N
Number
Return the SCC Board Y Y Y Y

Clock
The Single Fed Single Y N N N

Receiving and Dual
Fed Dual Receiving
Attribute of the LWM
and LWX Boards
Query the Working Y N N N

Band for a Board
Board Working Y N N N
Frequency
Optical Port Loopback Y N N N
STAT Byte to Be Y Y Y Y
Transmitted at ODU
Layer
PT Byte to Be Y Y Y Y
Transmitted at ODU
Layer
IAE Byte to Be N N N N
Transmitted at OTU
Layer
OTU Layer TTI Y Y Y Y

Identifier
Current Bearer Rate Y N N N


Check on
Monitoring Y N N N
Wavelength Band
Type
Input Optical Power N N N N
Reference Value of the N N N N

Input Optical Power
Reference Time of the N N N N

Input Optical Power
Input Status N N N N
Output Optical Power N N N N
Reference Value of the N N N N

Output Optical Power
Reference Time of the N N N N

Output Optical Power
Output Status N N N N
Input Lower Threshold Y Y Y Y
Input Upper Threshold Y Y Y Y
Maximum Output Y N N N
Optical Power of the
Pump
Minimum Output Y N N N
Optical Power of the
Pump
Enable Wavelength Y Y Y Y
Flag
Upper Threshold of N N N N
Tunable Wavelength
Lower Threshold of N N N N
Tunable Wavelength
Guaranteed Bandwidth Y Y Y Y
Whether Wavelength N N N N
Type Adjustable
Whether Extended Y N N N
Wavelength Supported


Check on
Set ESC Auxiliary Y Y Y Y

Switch
Planned Wavelength Y Y Y Y
Type
ODU1 Channel Y N N N
Loopback
Loopback
Loopback
FEC Mode Y Y Y Y
FE Transparent Y Y Y Y
Transmission
Enable an Ethernet Y Y Y Y
Port
Working Mode of an Y Y Y Y
Ethernet Port
OTN Service Type Y N N N
MCA Coding Mode N N N N
Optical Amplifier N N N N
Board Inclination
FC Distance N N N N
Expansion
Output Lockout Mode Y Y Y Y
Forced Transmitted Y Y Y Y
Power
J0 Byte to Be Received Y Y Y Y
WDM J0 Byte to Be Y Y Y Y
Received Mode
J0 Byte Received Y N N N
WDM Received J0 Y N N N
Byte Mode
J0 Byte to Be Y Y Y Y
Transmitted


Check on
WDM J0 Byte to Be Y Y Y Y
Transmitted Mode
PRBS Test on an Y N Y N
Auxiliary Board
TTI Identifier to Be Y Y Y Y
Transmitted at OTS
Layer
TTI Identifier to Be Y Y Y Y
Received at OTS Layer
TTI Identifier N N N N
Received at OTS Layer
TIM Detection Mode Y Y Y Y

Monitored at Optical
Layer
Port Service Mapping Y Y Y Y

Path
In-Service Status of the Y N N N

Optical Amplifier of
the Pump
Status of the Optical Y N N N

Amplifier of the Pump
FC internal operation Y Y Y N
mode
Power offset of the Y Y Y N

working and protection
channels
Overhead PT byte to be Y Y Y Y
in OPU transmitted in the OPU
layer
PT byte received N N N N
OTU Layer TTI to be Sent Y Y Y Y
TTI to be Received Y Y Y Y
TTI Received N N N N
IAE Byte to be N N N N
Received


Check on
IAE Byte Received N N N N
BEI in the OTU layer N N N N
BDI in the OTU layer N N N N
Overhead TTI identifier to be sent Y Y Y Y

in ODU
TTI identifier to be Y Y Y Y
received
TTI identifier received N N N N
STAT byte to be Y Y Y Y
transmitted in the ODU
layer
STAT byte received in N N N N

the ODU layer
BEI in the ODU N N N N
BDI in the ODU N N N N
AIS insertion in the N N N N

ODU layer
CLK insertion in the N N N N

ODU layer
OCI insertion in the N N N N

ODU layer
SDH 1-byte J0 to be sent Y Y Y Y

Overhead
1-byte J0 to be received Y Y Y Y
1-byte J0 received N N N N
64-byte J0 to be Y Y Y Y
received
Board Basic Attributes

clock
Revertive Mode Y Y Y Y
WTR Y Y Y Y
SSM Protocol Y Y Y Y
Clock Source Y Y Y Y
Attributes


Check on
Lock Status Y Y Y Y
Input Mode of External Y Y Y Y

Source
External Source S1 Y Y Y Y
Timeslot
Configuration of S1 Y Y Y Y
Byte
Clock Source ID Y Y Y Y
WTR Status N N N N
Board Clock Source N N N N

Holdover Mode
Clock Transparent N N N N
Transmission
Configuration
Transmission
Protection Group
Set Clock Mode Y Y Y Y
Optical Optical Line Protection

Line (OLP)
Protection
Revertive Mode Y Y Y Y
Revertive Time Y Y Y Y
Active Path N N N N
Switching Status N N N N
Channel Hold-off Y Y Y Y
Time
Optical Revertive Flag Y Y Y Y

Channel
Protection Revertive Time Y Y Y Y
Switching Status N N N N
Time
1:N Protection Type Y Y Y Y

Optical
Channel Revertive Mode Y Y Y Y
Protection


Check on
WTR Time Y Y Y Y
Remain WTR Time N N N N
SD Switching Enabled Y Y Y Y
Flag
Parameter Check Y N N N
Consistency Flag
Protection Priorities Y Y Y Y
IPA(APR) Protection Group ID Y Y Y N

Protection
Pair Band Y Y Y N
Detection Board Y Y Y N
Control Y Y Y N
Implementation Board
Raman Amplifier Y Y Y N
Auxiliary Raman Y Y Y N
Board
Remote Optical Pump Y Y Y N

Board
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 Period Y Y Y N
Start Latency Y Y N N
Security Control Y Y Y N
Switch
Detection Board Y Y Y Y
Treshold
Raman Amplifer Y Y Y Y
Threshold
Enable the Raman Y Y Y Y

Amplifier Alarm
IPA Auxiliary Detect Y Y Y Y

Interface


Check on
Pulse restart switch Y Y Y Y
APE Automatic Power

Equilibrium
Subrack (NE) ID of N N N N
Power Monitoring Unit
Power Monitoring Unit Y Y Y N
Power Regulating Y Y Y N
Subrack of Odd
Wavelength
Power Regulating Y Y Y N
Subrack of Even
Wavelength
Monitoring Subrack of Y Y Y N
Transmit End
Monitoring Subrack of Y Y Y N
Receive End
Power Unbalance Y Y N N
Threshold
Wavelength Enabling Y Y N N
Flag
Standard Power Offset Y Y Y N
Actual Power Offset N N N N
Standard Power Offset N N N N

Reference
320G ALC Link ID Y Y Y N
Node Type Y Y Y N
Node ID Y Y Y N
Power Detection Unit Y Y Y N
Variable Optical Y Y Y N
Attenuation Unit
Upstream Supervisory Y Y Y N
Channel
Downstream Y Y Y N
Supervisory Channel


Check on
Node ID of the Y Y Y N
Reference Node
Working Mode Y Y Y N
Reference Unit Y Y Y N
Abnormal Power Y Y Y N
Detection Threshold
Single-Wavelength Y Y Y N
ASE Noise
Compensation
Overall Optical Power Y Y Y N

Offset Compensation
Auto Adjustment Y Y Y N
Switch
1600G Link ID Y Y Y N
ALC
Node ID Y Y Y N
Direction Y Y Y N
Band Type Y Y Y N
Node Number Y Y Y N
Monitored NE N N N N
Working Mode Y Y Y N
Power Detection Unit Y Y Y N
Variable Optical Y Y Y N
Attenuation Unit
Node ID of the Y Y Y N
Reference Node
Reference Unit Y Y Y N
Abnormal Power Y Y Y N
Detection Threshold
Standard Output Power Y Y Y N

of a Single Wavelength

Value


Check on
Single-Wavelength Y Y Y N
ASE Noise
Compensation
Overall Optical Power Y Y Y N

Offset Compensation
Gain Detection Input Y Y Y N

Unit of the Power
Reference Node
Standard Gain of the Y Y Y N

Power Reference Node
Auto Adjustment Y Y Y N
Switch
West Supervisory Y Y Y N
Channel
East Supervisory Y Y Y N
Channel
Test Laser Spectrum N N N N

Function Analysis
Automatic WDM N N N N
Power Shutdown
PRBS test N N N N
Wavelengt Group ID Y Y Y Y
h
Protection Protection Type Y Y Y Y
Group Revertive Mode Y Y Y Y
Revertive Time Y Y Y Y
Remain Revertive N N N N
Time
Switching Mode Y Y Y Y
Switching Time Y Y Y Y
Active Path Y Y Y Y
Enable SD Y Y Y Y
Slot Mapping Y Y Y Y
Board Mapping Y Y Y Y
SD Event Y Y Y Y


Check on
Time
WDM WDM Common Cross- Y Y Y Y

Service Connections
Configurat
ion WXCP Protection Y Y Y Y
Group
WXCP Protection Y Y Y Y
Group Board Mapping
WXCP Revertive Mode Y Y Y Y

Service
Attributes WTR time Y Y Y Y
SD Enabling Flag Y Y Y Y
SD Trigger Condition Y Y Y Y
Current Status N N N N
Trail Status N N N N
Current Working Path N N N N
OWSP Wavelength Protection Y Y Y Y

Group And WTR
Wavelength Protection Y N Y N
Group Status
ROADM Logical Wavelength Y Y Y N

Group
Wavelength Blocking Y Y Y N
Monitor Unit
Optical Power Y Y Y N
Equalization Monitor
Unit
OTU Mapping Y Y Y N
OTU Dependent Y Y Y N
Optical Attenuator
Unit
Wavelength Pass- Y Y Y N
through/Blocking Flag
Equalization Enable
Flag


Check on
Equalization Monitor
Threshold
Standard Optical Y Y Y N
Power Offset
Actual Optical Power N N N N

Offset
TPS/DPPS DPPS Protection Y Y Y Y

Group Board Mapping
DPPS Protection Y Y Y Y
Group Revertive Mode
DPPS Protection WTR Y Y Y Y

Time
TPS Protection Group Y Y Y Y

Board Mapping
TPS Protection Group Y Y Y Y

Revertive Mode
TPS Protection WTR Y Y Y Y

Time
Time
Optical Edge Port Slot Y Y Y Y

Cross-
Connectio Edge Port Optical Port Y Y Y Y
n Edge Port In/Out Y Y Y Y
Manageme Attribute
nt Station
by Station Edge Port Flag Y Y Y Y
Optical Cross- Y Y Y Y
Connection ID, Parent
ID
Source/Sink Slot of Y Y Y Y
Optical Cross-
Connection
Source/Sink Y Y Y Y
Wavelength of Optical
Cross-Connection


Check on
Source/Sink Y Y Y Y
Waveband of Optical
Cross-Connection
Optical Cross- Y Y Y Y
Connection Type
OCCE Logical Wavelength Y Y Y N

Group
Power Equalization Y Y Y N
Monitoring Unit
OTU Mapping Y Y Y N
Optical Attenuation Y Y Y N
Unit Related to OTU
Wavelength Pass- Y Y Y N
Through/Blocking
Flag
Enabling
Detection Threshold
Wavelengt Wavelength Y Y Y N
h Lockout monitoring object
Wavelength Y Y Y N
monitoring object
Wavelength Y N N N
Add Mapping N N N N
Delete Mapping N N N N
Calculate OTU N N N N
Apply N N N N
Query Mapping from Y Y Y N

NE
Query Mapping from N N N N

T2000


Check on
Dispersion Compensation Value N N N N

Compensat
ion Fine-Tune Mode Y Y Y Y
OTU Y Y Y Y
Optimum Value N N N N
Scanning
E1 Cross- E1 Cross-Connection Y Y Y Y
Connectio
n
Manageme Subrack ID Y N Y Y
nt of
Master and Subrack Name Y N Y Y
Slave
Subracks
DPS Protection Group Y Y Y Y
TCM Object N N N N
Overhead
Layer N N N N
Source mode Y Y Y Y
Sink mode Y Y Y Y
Enable the source Y Y Y Y
Enable the sink Y Y Y Y
TTI to be transmitted Y Y Y Y
TTI to be Received Y Y Y Y
Received TTI N N N N
DEG threshold Y Y Y Y
DEG monitoring time Y Y Y Y
BIP8 bit error detection Y Y Y Y

mode
Enable TIM follow-up Y Y Y Y

response
BIP8 bit error Y Y Y Y

threshold for threshold
crossing
BIP8 bit error degrade Y Y Y Y

threshold


Check on
TIM detection mode Y Y Y Y
LCK insertion Y Y Y Y
1+N Protection type Y Y Y Y

Optical
Channel Revertive Mode Y Y Y Y
Protection WTR time Y Y Y Y
Remaining time to N N N N
restore
Delay time Y Y Y Y
Switching Status Y Y Y Y
SD Switching Enabled Y Y Y Y
Flag
Status of parameter Y N N N
consistency check
Status of redundant Y Y Y Y
service access
Enabling status of the Y N N N

protection group
protocol
Protection Priorities Y Y Y Y
OMP Enabling Status OF N N N N

WSS Protection
13.4.5 NG WDM Configuration Data Management Information List

The table describes the NG WDM configuration data management information.
Function Function Uploa Downl Consistency Data

List d oad Check Replication
Board Auto-Negotiation of N N N N
parameter the LDG Board
Monitor Wavelength Y N N N
Searching time interval N N N N

of Wavelength monitor
Board


Monitoring Channel N N N N
Board Monitor
Channel Wavelength
Board clock mode N N N N
Board Receiving/ N N N N
Transmitting
Attributes
Board Cross- N N N N
connection loopback
Optical booster N N N N
amplifier board gain
Return the SCC board N N N N

clock
Board tracing clock N N N N

source
Status of MCA board N N N N

optical switch
Laser status Y N N Y
Optical interface for N N N N

orderwire
Optical interface N N N N
attenuation rate
Input power N N Y Y
Output power N N Y Y
Max. attenuation rate N N N N
Min. attenuation rate N N N N
WBA Output Power N N N N
Path Using Status N N N N
LDG Board loopback N N N N
Input optical power N N N N

reference value

reference time
Input status N N N N


Output optical power N N N N

reference value

reference time
Output status N N N N
Lower threshold of Y N Y Y
input optical power
Upper threshold of Y N Y Y
input optical power
Max. pump output Y N N N

optical power
Min. pump output Y N N N

optical power
Synthesized input Y N Y Y
threshold
Synthesized output Y N Y Y
threshold
Max. packet length of N N N N

Ethernet Access Board
Automatic laser N N N N
shutdown
OTU working Y N Y Y
wavelength
OADM Add/Drop Y N N N
Wavelength
OTU/OADM Y N Y Y
Waveband Type
Working Waveband of Y N N N
Optical Layer Board
Working Waveband Y N N N
Parity of Optical Layer
Board
Whether VOA is N N N N
available in the board


Flow control enabled N N N N
OCP optical interface N N N N

switching status
Service type N N N N
Whether FEC is N N N N
allowed
Optical interface rate at N N N N

the client
Max. optical interface N N N N

rate at the client
Min. optical interface N N N N

rate at the client
Optical interface rate N N N N

frequency band

Configuration (OCU,
LQS, LGS, SMC)
Wavelength ID N N N N
Insertion Loss (You N N N N

can only query the real-
time status)
Nominal Gain N N N N
Optical Port Remarks N N N N
Service Working Mode N N N N
Client-side Service N N N N
Protocol
Board Working Mode N N N N
Service Type to Be N N N N
Sent
Service Type Received N N N N
LOS Alarm Threshold N N N N
LOG Working Mode N N N N
Set ESC Auxiliary N N N N

Switch


Min. Fixed Pump N N N N

Optical Power
Max. Fixed Pump N N N N

Optical Power
Fixed Pump Optical N N N N

Power
Single Path N N N N
Attenuation Rate
Adjustment
Path Attenuation Rate N N N N
WDM ID Received N N N N
WDM ID to Be N N N N
Received
Service rate N N N N
Guaranteed Bandwidth N N N N
LPT enabling flag Y Y Y Y
Port working mode Y N Y Y
Overhead PT Byte to be Received N N N N

in OPU
PT Byte Received N N N N
OTU Layer TTI to be Sent N N N N
TTI to be Received N N N N
TTI Received N N N N
IAE Byte to be N N N N
Received
IAE Byte Received N N N N
BEI in the OTU layer N N N N
BDI in the OTU layer N N N N
Overhead TTI identifier to be sent N N N N

in ODU
TTI identifier to be N N N N
received
TTI identifier received N N N N


STAT byte to be N N N N
received in the ODU
layer
STAT byte received in N N N N

the ODU layer
BEI in the ODU N N N N
BDI in the ODU N N N N
AIS insertion in the N N N N

ODU layer
CLK insertion in the N N N N

ODU layer
OCI insertion in the N N N N

ODU layer
SDH 1-byte J0 to be sent N N N N

Overhead
1-byte J0 to be received N N N N
64-byte J0 to be N N N N
received
Board Revertive Mode N N N N

clock
WTR N N N N
Enable S1 Byte N N N N
Protocol
Clock Source N N N N
Attributes
Lock Status N N N N
Input Mode of External N N N N

Source
External Source S1 N N N N
Timeslot
Manual Configuration N N N N
of S1 Byte
Clock Source ID N N N N
WTR Status N N N N



Holdover Mode
Transmission
Configuration
Transmission
Protection Group
IPA(APR) Detection Board Y N Y N

Protection
Pair Shut Off Board Y N Y N
RAMAN Amplifier Y N Y N
Enable Flag Y N Y N
Restart Mode Y N Y N
Off Period Y N Y N
On Period Y N Y N
Testing Period Y N Y N
Start Latency Y N N N
Security Control Y N Y N
Switch
Restart Pulse Switch Y N Y N
IPA Auxiliary Y N Y N
Detection Interface
APE Automatic Power

Equilibrium
Subrack (NE) ID of Y N Y N
Power Monitoring Unit
Power Monitoring Unit Y N Y N
Power Regulating Y N Y N
Subrack of Odd
Wavelength
Power Regulating Y N Y N
Subrack of Even
Wavelength
Monitoring Subrack at Y N Y N
Transmit End


Monitoring Subrack at Y N Y N
Receive End
Power Unequalization Y N N N
Threshold
Wavelength Enabling Y N N N
Flag
Standard Power Offset Y N Y N

Reference
NGWDM Link ID Y N Y N
ALC
Subrack ID Y N N N
Power detection unit
Variable attenuation
unit
Adjacent Node in Y N Y N
Upstream Direction
Adjacent Node in Y N Y N
Downstream Direction
Reference Unit Y N Y N
Line Attenuation Y N Y N
Exception Detection
Threshold
Node Gain Y N Y N
Compensation Offset
Automatic Adjustment Y N Y N
Switch
Test Laser Spectrum N N N N

Function Analysis
Automatic WDM N N N N
Power Shutdown
Port Group ID Y N Y Y
Protection
Group Protection Type Y N Y Y
Slot Mapping Y N Y Y
Revertive Mode Y N Y Y


WTR Time $s$ Y N Y Y
Enable SD Y N Y Y
Working Channel Y N Y Y
Hold-off Time
Protection Channel Y N Y Y
Hold-off Time
Channel Hold-off Y N Y Y
Time Dectection
Optical Edge Port Slot Y N Y Y

Cross-
Connection Edge Port Optical Port Y N Y Y
Manageme Edge Port In/Out Y N Y Y
nt Station Attribute
by Station
Edge Port Flag Y N Y Y
Optical Cross- Y N Y Y
Connection ID, Parent
ID
Source/Sink Slot of Y N Y Y
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
Optical Cross- Y N Y Y
Connection Type
OCCE Logical Wavelength N N N N

Group
Power Equalization N N N N
Monitoring Unit
OTU Mapping N N N N
Optical Attenuation N N N N
Unit Related to OTU
Wavelength Pass- N N N N
Through/Blocking
Flag


Enabling
Detection Threshold
Electrical Cross-connection Y N Y Y
Cross- Level
Connection
Manageme Service Type Y N Y Y
nt Direction Y N Y Y
Source Channel Y N Y Y
Sink Channel Y N Y Y
Activation Status Y N Y Y
SNCP Service Source Y N Y Y

Manageme
nt Service Sink Y N Y Y
Protection Type Y N Y Y
Level Y N Y Y
Revertive Mode Y N Y Y
WTR Time Y N Y Y
Working Channel Y N Y Y
Hold-off Time
Protection Channel Y N Y Y
Hold-off Time
Enable SD Y N Y Y
SD Trigger Condition Y N Y Y
ODUk Level Y N N Y
SPRing
Single WTR Y N N Y
Station SD Enabling Flag Y N N Y
Configurati
on Whether Management Y N N Y
Node or Not
Protection Unit Y N N Y
Path Mapping Y N N Y


Span ID Y N N Y
Hold-Off Time Y N N Y
ASON Cross-connection Y N N N
electrical Level
cross-
connection Service Type Y N N N
manageme Direction Y N N N
nt
Source Channel Y N N N
Sink Channel Y N N N
Activation Status Y N N N
Service source Y N N N
ASON Service source Y N N N

SNCP
Manageme Service sink Y N N N
nt Protection type Y N N N
Level Y N N N
Revertive mode Y N N N
WTR Y N N N
Delay time of the Y N N N

working channel
Delay time of the Y N N N

protection channel
SD enabling flag Y N N N
SD triggering Y N N N
condition
Service Source Y N N N
Master/ Subrack ID Y N Y Y
Slave
subrack Subrack name Y N Y Y
manageme
nt
Service Package Management Y N Y Y
13.4.6 RTN Configuration Data Management Information List

The table describes the RTN configuration data management information.

Function Function Uploa Downl Consistenc Data

List d oad y Check Replication
PDH Tributary loopback Y N N N

Interface
Path impedance N N N N
Service load indication Y Y Y Y

(load/unload)
Retiming mode Y Y Y Y
J2 byte to be transmitted Y Y Y Y
J2 byte to be received Y Y Y Y
J2 byte received N N N N
Path name N N N N
SDH Laser switch N N N N

Interface
Optical interface Y N N N
loopback
Set automatic laser N N Y N

shutdown (ALS)
Enable source of tandem Y Y Y Y

connection
Enable sink of tandem Y Y Y Y

connection
APId value to be Y Y Y Y
transmitted at source
APId value to be received Y Y Y Y

at sink
APId byte mode at source Y Y Y Y
APId value received at N N N N

sink
APId byte mode at sink Y Y Y Y

distance
Scheduled release of port N N N N

loopback
SDH optical port output N N N N

wavelength


SDH optical port input N N N N

wavelength
2M pseudo number test N N N N
PRBS test N N N N
Single-Port Enable single-port Y Y Y Y

Multiple multiple multiplex section
Multiplex
Section
SNCTP Group ID Y Y Y Y
Group
of working channel

of protection channel
WTR rime of a protection Y Y Y Y

group
Revertive mode of a Y Y Y Y
protection group

hold-off time of working
channel

hold-off time of
protection channel
High Configure 1588 packet Y Y Y Y

Precision
Time High precision clock Y Y Y Y
Transmissi priority table
on configure clock port Y Y Y Y
Configure the external Y Y Y Y

port of a clock
Multiplex Check the standby Y Y Y Y

section channel
IF 1+1 protection Y Y Y Y
protection
group N+1 protection Y Y Y Y
Board 1+1 Optimize higher order Y Y Y Y

protection pass-through


MSTP Ethernet service E-LAN/ Y N Y Y

+Packet E-LINE/E-AGGR
features
V-UNI group Y N Y Y
Service QoS Y N Y Y
Ethernet OAM Y N Y Y
Management of basic Y N Y Y
ports
Management of link Y N Y Y
aggregation group
OAM management of Y N Y Y
ports
Static Tunnel Y N Y Y
Basic management of Y N Y Y
MPLS
Tunnel OAM Y N Y Y
Tunnel protection group Y N Y Y
PW management Y N Y Y
QinQ Link Y N Y Y
Overhead Y N Y Y
13.4.7 Ethernet Configuration Data Management Information List

The table describes the Ethernet configuration data management information.
Function Function Uplo Down Consistenc Data

List ad load y Check Replicatio
n
High Speed Laser Switch State N N N N

Ethernet
Interface Time Interval of Adjacent Y Y Y Y
Packets(8ns)
Max. Packet Length Y Y Y Y
Dead Time After the Y Y Y Y

Control Packet is Sent
(512ns)
Auto-Negotiation Enabled Y Y Y Y


n
Data Statistics Counter for N N N N

the Correct Packets in the
Receiving Direction

the Incorrect Packets in the
Receiving Direction

All the Packets in the
Transmitting Direction
Optical Interface Y N N N
Loopback
Data Encapsulation Y Y Y Y
Protocol
Max. Frame Length Y Y Y Y
Dead Time upon Sending Y Y Y Y

the Control Packet
Optical Interface Y N N N
Loopback
Laser State N N N N
Interval for Adjacent Y Y Y Y

Packets
Ethernet User ID and Name Y Y Y Y

User
Manageme
nt
Ethernet TAG Flag Y Y Y Y

Interface
Manageme VLANID Y Y Y Y
nt User Priority Y Y Y Y
User ID Y Y Y Y
Flow Control Y Y Y Y
Port Enable Y Y Y Y
Binding Path Y Y Y Y
Loopback at MAC Layer Y N N N


n
Loopback at PHY Layer Y N N N
Encapsulation Protocol Y Y Y Y
Enable PPT Y Y Y Y
Scramble Y Y Y Y
CRC retrieve Y Y Y Y
Check Field Length Y Y Y Y
FCS Calculation Sequence Y Y Y Y
Enable LPT Y Y Y Y
LPT Port and VCTRUNK Y Y Y Y

Relation
Port Default Forwarding Y Y Y Y

Priority
Port Control Mode Y Y Y Y
Port Common Attributes Y Y Y Y

Management
Port Type (P/PE) Y Y Y Y
Port Encapsulation Y Y Y Y
Method (CCC/Martini)
Port Data Format Entrance Y Y Y Y

Check (Enable/Disable)
Enable/Disable Port LCAS Y Y Y Y
Stack VLAN ID Y Y Y Y
Flow Message Priority Y Y Y Y

Classification Method and
Forwarding Priority
Mapping from TAG Y Y Y Y

Priority to Forwarding
Priority
LAPS/HDLC/GFP Y Y Y Y
Encapsulation parameters
Point-to-Point Attribute of Y Y Y Y
Port


n
Threshold for Enabling Y Y Y Y

Broadcast Message
Suppression
Broadcast Message Y Y Y Y
Suppression
Link Aggregation Y Y Y Y
Configuration
Default VLAN ID Y Y Y Y
Default VLAN Priority Y Y Y Y
Flow Control Enabled Y Y Y Y
Port Physical Parameters N N N N
MAC Loopback Y N N N
Phy Loopback Y N N N
Laser Switch Y N N N
Default Forwarding Y Y Y Y
Priority
Non-Auto-Negotiation Y Y Y Y
Mode
Actual Flow Control Mode Y N Y Y
Enable/Disable Broadcast Y Y Y Y
Packet Suppression
Broadcast Packet Y Y Y Y
Suppression Threshold
Auto-Negotiation Flow Y Y Y Y
Control Attribute
Port Type Y Y Y Y
Encapsulation Format of P Y Y Y Y
Port
Entrance Detection Y Y Y Y
Enable QinQ Y Y Y Y
Default QinQ ID Y Y Y Y
QinQ Priorities Y Y Y Y
QinQ TAG Attributes Y Y Y Y


n
Traffic Threshold Y Y Y Y
Traffic Threshold Time Y Y Y Y

Window
QinQ Type Domain of the Y Y Y Y

Ethernet Port
Tag Y Y Y Y
Jumbo Frame Type Y Y Y Y
Loopback Detect Y Y Y Y
Port Blocking Y Y Y Y
Port Mirroring N N N N
TAG TAG Y Y Y Y
Attributes
Default VLAN ID Y Y Y Y
VLAN Priority Y Y Y Y
Entry Detection Y Y Y Y
MPLS P/PE Attributes Y Y Y Y

Attributes
Encapsulation Format of P Y Y Y Y
Port
Encapsulation Protocol Y Y Y Y
Scramble Y Y Y Y
CRC Reverse Y Y Y Y
Check Field Length Y Y Y Y
FCS Calculation Sequence Y Y Y Y
Extended Header Y Y Y Y
Selection
Enable LCAS Y Y Y Y
Enable LPT at the Y Y Y Y

VCTRUNK port
Point to Point Attributes Y Y Y Y
Enabling QinQ Y Y Y Y
Default QID Y Y Y Y
QinQ Priority Y Y Y Y


n
QQTAG Attributes Y Y Y Y
QinQ Type QinQ Type Y Y Y Y

VCG
Attributes Port Enabled Y Y Y Y
Port Physical Parameters N N N N
Forwarding Priority Y Y Y Y
Port Priority Y Y Y Y
(ATTR_ETHOVERSDH_
MAC_PRIMODE)
Port Priority Y Y Y Y
(ATTR_ETHOVERSDH_
VCG_PRIMODE)
HO Procedure Timer Y Y Y Y
Duration
WTR Procedure Timer Y Y Y Y

Duration
LCAS Mode Y Y Y Y
TSD in the Switching Y Y Y Y

Condition
LCAS at Opposite End N N N N
Port MAC-Address N N N N
Port MAC-Address N N N N
Non-Autonegotiation Y Y Y Y
Mode
Non-Autonegotiation Y Y Y Y
Flow Control Attributes
DCN Query DCN Y N N N

System
Functions DCN System Data N Y Y Y
FDB Query Configuration Item Y N N N

Function of VLAN Filtering Table
Query Configuration of Y N N N
VLAN Filtering Table


n
Query Configuration of Y N N N
TOS
Query Packet Priority Y N N N

Classification Mode
Query Created VLAN Y N N N

Items
Query Multicast Y N N N
Addresses of VLAN
Delete Configuration Item N Y N N

of VLAN Filtering Table
Configuration of VLAN N Y N N
Filtering Table
Delete VLAN Item N Y N N
VLAN Unicast Routing N N Y Y

Table
VLAN Multicast Table N N N Y
VLAN Table N N Y Y
MAC Address Disabled N N Y Y
LPT Query the Mapping Y N N N

Between the Port and VC-
Trunk (LPT)
Delete the Mapping N Y N N

Between the Port and VC-
Trunk (LPT)
Set the Mapping Between N Y N N

the Port and VC-Trunk
(LPT)
LPT Data N N N Y
Ethernet Port N N Y N
Activate or Not N N Y N
LPT Direction N N Y N
Mapped Port List in the N N Y N

LPT Mapping
NEWFDB Forwarding Filter Table Y Y Y Y

Item


n
VLAN Unicast Y Y Y Y
MAC Address Disabled Y Y Y Y
Aging Time Y Y Y Y
NEWQOS CAR Information Y Y Y Y
COS Information Y Y Y Y
Flow Shaping Information Y Y Y Y
Flow Information Y Y Y Y
PTMPLPT Point-to-Multipoint LPT Y Y Y Y

Mapping
LPT Bearer Mode Y Y Y Y
LPT Hold-Off Time Mode Y Y Y Y
SHAPING Query Shaping Enabling Y N N N

of Port Queue
Query Port Queue Y N N N

Parameters
Set Shaping Enabling of N Y N N

Port Queue
Set Port Queue Parameters N Y N N
Shaping Parameters N N Y Y
SRP Query SRP Protocol Status Y N N N

Function
Query Node ID of Local Y N N N
Node
Query Node Name of Y N N N

Local Node
Query Hold-Off Time of Y N N N

SDH Protection Switching
Query IPS Switching Y N N N

Restoration Time
Query SRP Aging Time Y N N N
Query SRP Priority Y N N N

Partition Value
Query SRP Mapping Y N N N

Mode


n
Query SRP VLAN Priority Y N N N

Mapping
Query SRP TOS Priority Y N N N

Mapping
Set SRP Protocol Status N Y N N
Set Node ID of Local Node N Y N N
Set Node Name of Local N Y N N

Node
Set Hold-Off time of SDH N Y N N

Protection Switching
Set IPS Switching N Y N N

Restoration Time
Set SRP Aging Time N Y N N
Set SRP Priority Partition N Y N N

Value
Set SRP Mapping Mode N Y N N
Set SRP VLAN Priority N Y N N

Mapping
Set SRP TOS Priority N Y N N

Mapping
Node Name N N Y Y
Node SRP Protocol N N Y Y

Enabling
WTR Time N N Y Y
Restoration Time N N Y Y
Forwarding Aging Time N N Y Y
Priority Partition Value N N Y Y
TOS Priority Mapping N N Y Y

Table
Priority Mapping Mode N N Y Y
VLAN Priority Mapping N N Y Y

Table
STP Query Bridge Priority Y N N N

Function


n
Query Bridge Timing Y N N N

Parameters
Query Bridge MAC Y N N N

Address
Set STP Enabling N Y Y Y
Point-to-Point Attribute Y Y Y Y
Set STP Working Mode N Y Y Y
Spanning Bridge Parameters Y Y Y Y

Tree
Manageme Bridge Port Parameters N N N N
nt Module Enable Protocol Y Y Y Y
Bridge Running N N N N
Information
Port Running Information N N N N
VB Bridge Port Parameter N N N N
Forwarding VLAN Filter Table Y Y Y Y

Filter Table
Manageme Unitcast Filter Table Y Y Y Y
nt Module Multicast Filter Table Y Y Y Y
The Priority Mapping Y Y Y Y
Aging Time Y Y Y Y
GARP GARP Protocol Y Y Y Y

Protocol Management(including
Manageme management of GVRP,
nt Module GMRP and GMRP in
VLAN)
CAR CAR Configuration Y Y Y Y

Manageme
nt CAR Enabled/Disabled Y Y Y Y
CAR Parameters (CIR/ Y Y Y Y

CBS/PIR/MBS)
CAR Allocated by VLAN Y Y Y Y
VB VB Configuration and Y Y Y Y
Manageme Name
nt
Disabled MAC Address in N N N N
VB


n
VB Mounting Y Y Y Y
Ethernet EPL/EVPL/Transit Y Y Y Y
Service Service Configuration
EPLn/EVPLn Service Y Y Y Y
Configuration
EPL LSP Forwarding Y Y Y Y

Priority
LAN LSP Forwarding Y Y Y Y

Priority
VLAN Switch Y Y Y Y
Configuration
VLANSNCP Y Y Y Y
Configuration
VLANSNCP Switching N N N N
Status
Bridge STP Priority Y Y Y Y
QinQ Type Domain Y Y Y Y
Miscellane Ethernet Static Route Y Y Y Y

ous
DPT Module Function Y Y Y Y
Flow Classification Y Y Y Y
Other Attributes N N N N
Management of Bridge
Ring Network Service Y Y Y Y
Ethernet IGMP Snooping Enabled Y Y Y Y

IGMP
Function Maximum Response Time Y Y Y Y
for Query Message of
Multicast
Router Ageing Time Y Y Y Y
Port Configuration and N N N N

Management of Multicast
Router
Static Multicast Table N N N N

Items
VC VCTRUNCK Bandwidth Y Y Y Y
TRUNK Binding


n
Manageme VCTRUNK Shared Y Y Y Y

nt Attributes
Service QoS Management of Y Y Y Y

QOS/COS Transpartent Transmission
Manageme Service
nt
Shaping Management Y Y Y Y
RPR Protection Mode Y Y Y Y

Portection
Protection Reversion Y Y Y Y
Mode
RPR Protection Switching Y Y Y Y

Delay Time
RPR Protection WTR Y Y Y Y

Time
RPR External Switching N N N N

Command
RPR Protectiong N N N N
Switching Information
RPR Topo RPR Protocol Status Y Y Y Y

Manageme
nt Topo Timing Y Y Y Y
Node Number Y Y Y Y
Node Name Y Y Y Y
Query Topology N N N N
Information
RPR Bandwith Use Y Y Y Y

Priority
Link Sending Priority Y Y Y Y
Related RPR Protect State N N N N

Attributes
of the RPR RPR Switch State N N N N
Protection RPR Switch Total Times N N N N
Informatio
n Querying RPR Protect Total Time N N N N
RPR Last Switch Request N N N N
RPR Switch Command N N N N
RPR Protect Mode Y Y Y Y


n
RPR Protect Restore Mode Y Y Y Y
RPR Protect Delay Time Y Y Y Y
RPR Protect WTR Time Y Y Y Y
RPR Node ID Y Y Y Y
RPR Node Name Y Y Y Y
RPR Enabled Y Y Y Y
RPR Control Time Y Y Y Y
Related RPR Node ID N N N N

Attributes
of the RPR RPR Node Name N N N N
Topology RPR Direction N N N N
Informatio
n Querying RPR Protection Mode N N N N
RPR Zero Ring Reached N N N N
RPR One Ring Reached N N N N
Number of Hops on RPR N N N N

Zero Ring
Number of Hops on RPR N N N N

One Ring
RPR East Ring Next Node N N N N

ID
RPR West Ring Next Node N N N N

ID
RPR East Protect State N N N N
RPR West Protect State N N N N
RPR East Switch State N N N N
RPR West Switch State N N N N
RPR East Transmitting N N N N

Link Weight
RPR West Transmitting N N N N

Link Weight
RPR East Link A0 N N N N

Reserved Bandwidth


n
RPR West Link A0 N N N N

Reserved Bandwidth
Related RPR Transmitting Link Y Y Y Y

Attributes Weight
of the RPR
Link RPR Used Bandwidth of Y Y Y Y
Informatio Priority A
n Querying RPR Reserved Bandwidth Y Y Y Y
and Setting of Priority A
RPR Used Bandwidth of Y Y Y Y

Priority B-CIR
Static Link Set Link Aggregation Y Y Y Y

Aggregatio System Priority and Port
n Priority
Query LAG and actual N N N N

LAG status
Query LAG System N N N N

Priority or Port Priority
and System MAC Address
Query LAG Abstract N N N N
Query LAG Details N N N N
Query Details of LAG Port N N N N
Query LAG Packet N N N N

Statistics
LAG Query LAG Name Y N N N

Function
Query LAG Group Y N N N
Query System Priority of Y N N N

LAG
Query Port Priority of Y N N N

LAG
Query System MAC Y N N N

Address of LAG
Add LAG Group N Y N N
Set System Priority of N Y N N

LAG
Set Port Priority of LAG N Y N N


n
LAG Group Information N N N N
LAG Group Priority N N N Y
Link Group ID N N Y N
Link Group Name N N Y N
Link Group Type N N Y N
Class for Middle Storage N N Y N
Main Port N N Y N
LAG Port List N N Y N
Selected Port List N N Y N
Inter-Board Query Inter-Board LAG Y N N N

LAG Group
Query Inter-Board LAG Y N N N

Group Name
Query Protection Y N N N
Switching Revertive Mode
of Inter-Board LAG Group
Query System Priority of Y N N N

Inter-Board LAG Group
Query Port Priority of Y N N N

Set Inter-Board LAG N Y N N

Group Name
Set Protection Switching N Y N N

Revertive Mode of Inter-
Board LAG Group
Set System Priority of N Y N N

Set Port Priority of Inter- N Y N N

Board LAG Group
Inter-Board LAG Group N N Y Y

Information
Port LAG Query LAG Port Y N N N
Delete LAG Port N Y N N
Add LAG (Branch) Port N Y N N


n
LAG Record N N N Y
LAG Record N N Y N
Service Ethernet Service Mirror N N N N

Mirroring
Ethernet Query MP Attributes by Y N N N

OAM MP ID (0 Parameter
Query)
Query CCM Sending Y N N N

Period
Query LB Timeout Y N N N
Query LT Timeout Y N N N
Query CC Activation Y N N N
Status
Create (Add) MP N Y N N
Set CCM Sending Period N Y N N
Set LB Timeout N Y N N
Set LT Timeout N Y N N
Set CC Activation Status N Y N N
ID of Last Opposite MP N N Y Y
Tested
Type of Service N N Y Y
Maintained by 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 (0-7) N N Y Y
MP Type N N Y Y
MP Direction N N Y Y
CC Sending Period N N Y Y
LB Timeout N N Y Y
LT Timeout N N Y Y


n
CC Activation Status N N Y Y
Related Enable OAM Protocol Y Y Y Y

Attributes
of Ethernet OAM Working Mode Y Y Y Y
Port OAM Link Event Notification Y Y Y Y
Unidirectional Operation Y Y Y Y
Enable Response to Y Y Y Y
Remote Loopback
Max. OAM Packet Length N N N N
Error Frame Monitor Y Y Y Y

Window
Error Frame Monitor Y Y Y Y

Threshold
Error Frame Period Y Y Y Y

Window
Error Frame Period Y Y Y Y

Threshold
Error Frame Second Y Y Y Y

Window
Error Frame Second Y Y Y Y

Threshold
Loopback State N N N N
Remote Side Loopback N N N N

Response
Remote OAM Working N N N N

Mode
Remote Link Event N N N N

Notification
Remote Unidirectional N N N N
Operation
Remote Max. OAM Packet N N N N

Length
Ethernet Maintenance Point Y Y Y Y

Port OAM
Function Maintenance Point Y Y Y Y
Attribute


n
LB Timeout Y Y Y Y
LT Timeout Y Y Y Y
Multicast CC Sending Y Y Y Y
Period
Activation Status of Y Y Y Y
Multicast CC monitoring
Ethernet Response Test Frame or N N N N

Test Not
Frames
Manageme In Sending Test Frame N N N N
nt Status
Test Frames Configuration N N N N
Three Counters N N N N
Protocol Fault Diagnosis/ N N N N

Restoration
MPLS tunnel Type Y Y Y Y

Tunnel
Ingress Port Y Y Y Y
Ingress Port Type Y Y Y Y
Ingress lable Y Y Y Y
Egress Port Y Y Y Y
Egress Port Type Y Y Y Y
Egress label Y Y Y Y
Next hop Y Y Y Y
ARP IP Address Y Y Y Y
MAC Address Y Y Y Y
13.4.8 ATM Configuration Data Management Information List

The table describes the ATM configuration data management information.
Function Function Uplo Downl Consistency Data

List ad oad Check Replication
ATM ATM Traffic Descriptor Y Y Y Y

Service


Configura ATM Cross-Connect Y Y Y Y

tion
ATM Protection Pair Y Y Y Y
ATM Protection Group Y Y Y Y
ATM Port Type Y Y Y Y

Interface
Attributes Max. Number of VPI Bits Y Y Y Y
Max. Number of VCI Bits Y Y Y Y
Max. Number of VPC Y Y Y Y
Max. Number of VCC Y Y Y Y
Number of VPC N N N N
Configured Currently
Number of VCC N N N N
Configured Currently
Max. Number of VPI Y Y Y Y

Supporting VC Switching
Min. Number of VPI Y Y Y Y

Supporting VC Switching
Activated Status Y N N N
UPC/NPC Enable/ Y Y Y Y
Disable
Loopback Y N N N
Number of VPIs of ATM Y Y Y Y

Port Supporting VCC
VC VCTRUNCK Bandwidth Y Y Y Y
TRUNK Binding
Managem
ent
Descriptio ATM Logical Port Type Y Y Y Y

ns of ATM
Port Maximum VPI Bits of the Y Y Y Y
Attributes ATM Port
Maximum VCI Bits of the Y Y Y Y

ATM Port
Maximum VPCs of the Y N Y N

ATM Port
Maximum VCCs of the Y N Y N

ATM Port


Current VPC Number of N N N N

the ATM Port
Current VCC Number of N N N N

the ATM Port
ATM Logical Port Status Y N N N
Enable the UPC/NPC of Y Y Y Y

the ATM Logical Port
ATM Logical Port Y N N N

Loopback
Number of VPIs of VCCs Y Y Y Y

Supported by the ATM
Maximum VPI Range of N N N N

the VC Switching
Port
Minimum VPI Range of N N N N

the VC Switching
Port
Port Name N N N N
Laser Switch N N N N
ATM Logical Port Type Y Y Y Y
Maximum VPI Bits of the Y Y Y Y

ATM Port
Maximum VCI Bits of the Y Y Y Y

ATM Port
Maximum VPCs of the Y Y Y Y

ATM Port
Maximum VCCs of the Y Y Y Y

ATM Port
Current VPC Number of N N N N

the ATM Port
Current VCC Number of N N N N

the ATM Port
ATM Logical Port Status Y N N N
Enable the UPC/NPC of Y Y Y Y

the ATM Logical Port


ATM Logical Port Y N N N

Loopback
Number of VPIs of VCCs Y Y Y Y

Maximum VPI Range of N N N N

the VC Switching
Port
Minimum VPI Range of N N N N

the VC Switching
Port
OAM Segment Attribute of Y Y Y Y

Connect Point
Activated Status of CC Y Y Y Y
NE LLID Y Y Y Y
IMA IMA Group Management Y Y Y Y

Managem
ent E1 Link Parameters Y Y Y Y
IMA Protocol Mode Y Y Y Y
Query Port Rate in Real N N N N

Time
ATM Port J0 Byte to Be Sent Y Y Y Y

Overhead
J0 Byte Received N N N N
J1 Byte to Be Sent Y Y Y Y
J1 Byte Received N N N N
C2 Byte to Be Received Y Y Y Y
C2 Byte to Be Sent Y Y Y Y
C2 Byte Received N N N N
13.4.9 ASON Configuration Data Management Information List

The table describes the ASON configuration data management information.

Data
Functio Downloa Consistenc Replicatio
n List Function Upload d y Check n
ASON Refresh Path Status N N N N

Trail
SDH OSPF Protocol Y N Y Y

ASON Authentication
Disaster Parameter
Recovery
RSVP Protocol Y N Y Y
Authentication
Parameter
LMP Auto Discovery Y N Y Y

Type
13.4.10 DDN Configuration Data Management Information List

The table describes the DDN configuration data management information.
Consiste Data
Function Uplo Downl ncy Replicati
List Function ad oad Check on
SHDSL DSL port protocol mode Y Y Y Y

Configurati
on DSL port standard mode Y Y Y Y
DSL line rate Y Y Y Y
DSL line working mode Y Y Y Y
DSL remote port management Y Y Y Y

enabled
DSL port power compensation Y Y Y Y

enabled
DSL port activation enabled Y Y Y Y
DSL port loopback Y N N N
DSL port connection status N N N N
Remote equipment restart N N N N
SHDSL version N N N N
Manufacturer directory N N N N
Manufacturer issue N N N N

Consiste Data
Function Uplo Downl ncy Replicati
List Function ad oad Check on
Version of manufacturer N N N N
software
Unit identifier N N N N
Manufacturer ID N N N N
Manufacturer type N N N N
Manufacturer serial No. N N N N
Information about other N N N N

manufacturers
DDN N64 port working mode Y Y Y Y
N64 port protocol mode Y Y Y Y
V.35 port line rate Y Y Y Y
V.35 port clock mode Y Y Y Y
V.35 port clock sampling mode Y Y Y Y
The CRC4 function of E1 port Y Y Y Y

enabled
Port loopback N N N N
Port impedance N N N N
N64 board clock source tracing Y Y Y Y
LL/RTS/DSR control signal Y Y Y Y

status
RL/DTR/CTS control signal Y Y Y Y

status
13.4.11 Alarm and Performance Configuration Data Management

Information List
The table describes the alarm and performance configuration data management information.

Alarm and Performance Management

Data
Function Downlo Consisten Replicati
List Function Upload ad cy Check on
Alarm Severity Y N N N
manageme
nt Automatic report of Y N N N
alarms
Alarm Suppression Y N N N
Alarm reversion Y N N N
Settings of the bit error Y N N N

alarm threshold
Settings of NE alarm Y N N N
attributes
Alarm insertion Y N N N
Settings of the automatic Y N N N

alarm acknowledgement

synchronization of alarms
Settings of enabling the Y N N N

alarm dynamic
correlation analysis

conversion from current
alarms to history alarms
Alarm correlation rule Y N N N
Alarm attribute template Y N N N
Equipment alarm filtering Y N N N
T2000 alarm attributes Y N N N
Settings of alarm Y N N N
diagnosis rules
Settings of the alarm Y N N N

notification
Settings of alarm Y N N N
performance dump
conditions
Performan Performance monitoring Y N N N

ce status
Performance threshold Y N N N

Data
Function Downlo Consisten Replicati
List Function Upload ad cy Check on
manageme Performance monitoring Y N N N

nt time
IP performance Y N N N
monitoring time
ATM performance Y N N N
monitoring time
Performance threshold Y N N N
template
13.5 Standards Followed

The standards followed are listed below.
Standards Followed
ITU-T G.707 Network node interface for the synchronous
digital hierarchy (SDH)
ITU-T G.773 Protocol suites for Q-interfaces for

management of transmission systems
ITU-T G.774 (01, 02, 03, 04) Synchronous Digital Hierarchy (SDH)
management information model for the NE
view
ITU-T G.783 Features of SDH functional blocks
ITU-T G.784 Synchronous digital hierarchy (SDH)

management
ITU-T G.803 Architecture of transport networks based on

the synchronous digital hierarchy (SDH)
ITU-T G.831 Management capabilities of transport

networks based on the synchronous digital
hierarchy (SDH)
ITU-T G0.851.1 Management of the transport network -

Application of the RM-ODP framework
ITU-T G.852.1 Management of the transport network

Enterprise viewpoint for simple sub-network
connection management
ITU-T G.852.2 Enterprise viewpoint description of transport

network resource model

ITU-T G.852.3 Enterprise viewpoint for topology

management
ITU-T G.852.6 Enterprise viewpoint for route management
ITU-T G.853.1 Common elements of the information

viewpoint for the management of a transport
network
ITU-T G.853.2 Sub-network connection management

information viewpoint
ITU-T G.853.3 Information viewpoint for topology

management
ITU-T G.853.6 Information viewpoint for trail management
ITU-T G.854.1 Computational interfaces for basic transport

network model
ITU-T G.854.3 Computational viewpoint for topology

management
ITU-T G.854.6 Computational viewpoint for trail

management
ITU-T M.3010 Principles for a telecommunications

management network
ITU-T M.3100 Generic network information model
ITU-T M.3400 TMN management functions
ITU-T X.720 Management information model
ITU-T X.721 Definition of management information
ITU-T X.722 Guidelines for the definition of managed

objects
ITU-T X.733 Information technology - Open Systems

Interconnection - Systems Management:
alarm reporting function
ITU-T X.903 Information technology - Open distributed

processing - Reference Model: architecture
Sif99025 EML-NML interface models
TMF513 Multi Technology Network Management

Information Agreement

Business Agreement

Solution Set Conformance Document

Operation Guide for Common Features A Glossary
A Glossary
1+1 optical path protection At the place where the signals are input, the
same channel of optical signals are input to
two boards or ports of the WDM equipment
through two fibers. The two boards or ports
are backed up mutually. When a fault occurs
to the working path, the input end of the
WDM equipment switches to the protection
path. If the working path recovers, the input
end of the WDM equipment switch back to
the working path.
Access Control List (ACL) Access Control List (ACL) is a list of IP

address. The addresses listed in the ACL are
used for authentication. If the ACL for the
user is not null, it indicates that the address
where the user logged in is contained in the
list.
Adjacent Concatenation For SDH, the virtual containers (VC) to carry

concatenated services are consecutive in
terms of their service in the frame structures,
so that they use the same path overhead
(POH).
Alarm A visible or an audible indication to notify the

person concerned that a failure or an
emergency has occurred. See also Event.
AIS Alarm Indication Signal. A signal sent

downstream in a digital network if an
upstream failure has been detected and
persists for a certain time.
Issue 01 (2009-06-30) Huawei Proprietary and Confidential A-1

A Glossary Operation Guide for Common Features
Alarm acknowledgement The process during which when an alarm is

generated, the operator needs to acknowledge
the alarm and take the right step to clear the
alarm.
AIS insertion If there are excessive errors in a channel, AIS

can be inserted in this channel to indicate it is
unavailable. For a line board, you can set
whether to insert AIS when there are
excessive errors in the B1, B2 and B3 bytes.
For a tributary board at the E1 or T1 level, you
can set whether to insert AIS when there are
excessive errors in BIP-2. For a tributary
board at the E3 level or higher, you can set
whether to insert AIS when there are
excessive errors in the B3 byte.
Alarm delay time Alarm delay includes start delay and end
delay. An alarm is not regarded as being
generated until the NE has been detecting it
for a period of time, and this period of time is
the alarm start delay time. An alarm is not
regarded as being cleared until the NE has
been detecting the ending of it for a period of
time, and this period of time is the alarm end
delay time. Setting the delay time can avoid
the generation of unnecessary alarms due to
misreport or jitter.
Alarm reversion For the port that has already been configured
but has no service, this function can be used
to avoid generating relevant alarm
information, thus preventing alarm
interference.
Alarm suppression The suppressed alarm of a specific object is

not reported. The object here may be the
networkwide equipment, a specific NE, a
specific board and even a specific function
module of a specific board.
ALC Automatic Level Control. A technique

(procedure) to automatically reduce the
output power of optical amplifiers to avoid
exposure to hazardous levels.
All-ONEs The entire capacity of the adapted or

characteristic information is set to logic "1".
ALS The ALS function of an optical line system

automatically switches off the transmitter of
a regenerator section in case of cable break in
this section.
A-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

APS Automatic Protection Switching.

Autonomous switching of a signal between
and including two MS_TT, Sn_TT, or
Sm_TT functions, from a failed working trail/
SNC to a protection trail/SNC and subsequent
restoration using control signals carried by
the K-bytes in the MSOH, HO POH, or LO
POH.
Auto-negotiation The rate/work mode of the communication

party set as self-negotiation is specified
through negotiation according to the
transmission rate of the opposite party.
Attribute Property of an object.
Bidirectional (protection) switching For a unidirectional fault, both directions (of

the trail, subnetwork connection, and so on),
including the affected and unaffected
direction, are switched.
Bit error alarm threshold When the bit error reaches a specific limit, the
equipment will report an alarm. This limit is
the bit error alarm threshold. The threshold
can be divided into crossing threshold and
defect threshold.
Broadcast service The unidirectional services from one service

source to multiple service sinks are called the
broadcast service.
Concatenation When the standard virtual containers

(including VC4/VC3/VC12/VC11) are
incapable of carrying the volume of a SDH
signal, the containers can be concatenated to
function as a larger container.
CoS Class of Service. CoS keeps the priority

mapping rules. It works in internal ports,
especially when there is congestion, CoS is
even more important. The services at
different levels are processed according to the
corresponding priorities. The service with
higher priority is processed first and the
service with lower priority is discarded when
the bandwidth is insufficient.

Client trail There is an inclusion relation between the

trails of different levels, for example, a trail
of a certain level contains multiple trails of
lower levels. In such a structure, the lower
level trail is called the client trail.
CI Characteristic Information. The information

passing across a CP or TCP. It is a signal with
a specific format, which is transferred on
"network connections". The specific formats
will be defined in the technology specific
Recommendations.
Client A kind of terminal (PC or workstation)

connected to a network that can send
instructions to a server and get results through
a user interface. See also server.
Collision trails The data of a trail at the NE layer is changed.

After the trail is re-searched, the original trail
becomes a collision trail.
CoS Class of Service. CoS keeps the priority

mapping rules. It works in internal ports,
especially when there is congestion, CoS is
even more important. The services at
different levels are processed according to the
corresponding priorities. The service with
higher priority is processed first and the
service with lower priority is discarded when
the bandwidth is insufficient.
Cross-Connection Network services are realized through the

cross-connections of NEs. The cross-
connection is the connection of channels
between the tributary board and the line
board, or between line boards inside the NE.
Current alarms Alarms that do not clear, or has cleared but is

not acknowledged.
Current performance data The performance data stored in the current

register is called current performance data.
The current 15-minute or 24-hour register
(only one for each) is applied to collect the
performance data in the current monitoring
period. It changed within the monitor period.

Custom view The user-defined view is a subset on the Main

Topology. Included network entities can be
NE, network management system, link and
subnetwork. Generally, the network
management personnel need to customize
some views and select the network entity
under their management from the Main
Topology.
Clock View The Clock View provides a visible platform

to implement the clock management
function.
Data interface service The service that uses the F1 byte in an SDH
frame or some undefined bytes to transmit
information such as call charge, network
management system information and power
supply monitoring.
DCC Data Communications Channel. The data

channel that uses the D1–D12 bytes in the
overhead of an STM-N signal to transmit
information on operation, management,
maintenance and provision (OAM&P)
between NEs. The DCC channels that are
composed of bytes D1–D3 is referred to as the
192 kbit/s DCC-R channel. The other DCC
channel that are composed of bytes D4–D12
is referred to as the 576 kbit/s DCC-M
channel.
Discrete service The cross-connection that exists on an NE but

cannot form trails on the network
management system.
Disk Mirroring A procedure that involves duplicating data

from a NetWare partition on one hard disk to
the NetWare partition on another disk. Disk
mirroring pairs multiple hard disks on the
same channel, and like disk duplexing, writes
data to both the original and secondary disk.
If the original disk fails, the secondary disk
automatically takes over. Disk mirroring
cannot protect against failures that occur
along the channel between the disks and the
NetWare server, because the duplicate disks
exist on the same channel.

DNI Dual node interconnection is an architecture

between two rings where two nodes in each
ring are interconnected. The two
interconnections between the two rings can
be arranged to provide protection of the
traffic crossing from one ring to the other.
Extra traffic During fault-free conditions, it is possible to

use the protection channels to carry additional
traffic. This additional traffic, which is
referred to as extra traffic, has lower priority
than the normal traffic on the working
channels and has no means for protection.
Equipment set An aggregate of multiple managed

equipment. Equipment set facilitates the user
authority management on equipment in the
management domain of the network
management system. If some operation
authorities over one equipment set are
assigned to a user (user group), these
operation authorities over all equipment of
the equipment set are assigned to the user
(user group).
ECC Embedded Control Channel. An ECC

provides a logical operations channel
between SDH NEs,utilizing a data
communications channel (DCC) as its
physical layer.
EMU Environment Monitoring Unit. A type of

power and environment monitoring unit that
is used to monitor the environment variables,
such as the power supply and temperature.
With external signal input through the relay,
fire alarm, smoke alarm, burglary alarm, and
so on can be monitored as well.
Exercise switching This command tests whether a switching

protocol can work normally without
completing the actual switching operation.
Exerciser - Ring This command exercises ring protection

switching of the requested channel without
completing the actual bridge and switch. The
command is issued and the responses are
checked, but no working traffic is affected.

Exerciser - Span This command exercises span protection of

the requested channel without completing the
actual bridge and switch. The command is
issued and the responses are checked, but no
working traffic is affected.
Extended ID of NE The serial number of a subnetwork where an

NE resides, which is usually used to
distinguish different network segments. An
extended ID and an ID form the physical ID
of an NE.
Extended protection subnet An unprotected chain like ADM-ADM-TM

or ADM-ADM-ADM. The end-point NEs of
a link is of the ADM type. As this type of
protection subnetwork can be extended, we
name it extended protection subnetwork.
Failure The fault cause persisted long enough to

consider the ability of an item to perform a
required function to be terminated. The item
may be considered as failed; a fault has now
been detected.
Fault A fault is the inability of a function to perform

a required action. This does not include an
inability due to preventive maintenance, lack
of external resources, or planned actions.
F1 byte The user path byte, which is reserved for the

user but usually it is special for network
providers. The F1 byte is mainly used to
provide the temporary data or voice path for
special maintenance objectives. It belongs to
the regenerator section overhead byte.
F2,F3 bytes The user channel bytes. These two bytes

provide the user with the communication
between path units related to payload. They
belong to the higher order path overhead byte.
fiber/cable The general name of optical fiber and cable.

The physical entity that connects transport
equipment in a transport network, bears the
transmitted object (user information, network
management information) and implements
the transport function.

Forced switching This command performs the ring switch from

working channels or boards to the protection
channels or boards. This switch occurs
regardless of the state of the protection
channels or boards, unless the protection
channels or boards are satisfying a higher
priority bridge request.
Full duplex The system that can transmit information in

both directions on a communication link.
Full filtering trail In this search mode, the network management

system first deletes all the trail data on the
network management system and reserves the
service configuration data of respective NEs,
and then re-searches for the service
configuration data of respective NEs on the
network management system to form the new
trail information.
Full search In the full search mode, all the trail

information on the network management
system will be deleted first (Only the trail
information at the network layer on the
network management system is deleted,
while the service configuration information
of NE in NE layer on the network
management system and on the NE still
remain). Then the service configuration
information of respective NEs in the NE layer
on the network management system is re-
searched to form the trail information in the
network layer on the network management
system.
Gateway The equipment that is used to connect two

independent networks that use different
communication protocols.
Gateway IP IP address is used for TCP/IP communication

between an NE and the network management
system, which is effective only when it is used
for TCP/IP communication. That is, only the
gateway NE needs the IP address. IP address
cannot be used to identify an NE uniquely.
NEs in different TCP/IP networks may have
the same IP address. And one NE may have
several IP addresses (for example: an IP
address of a dial-up network, an IP address of
the Ethernet port and so on).

Gateway NE The NE that communicates with the NMS and

other NEs through a data communication
network.
GUI Cut-Through (GCT) Through the GUI Cut-Through (GCT)

function, you can view the GUI of the T2000
client and operate the T2000 directly on the
T2100 client, thus to realize centralized
monitoring and management of the network.
Host name Name of the computer that functions as a

main controlling point in a network and
provides special service to the users.
Half duplex The system that transmits information in only

one direction on the communication link at
any time.
High Availability The ability of a system to continuously

perform its functions during a long period,
which may exceeds the suggested working
time of the independent components. You can
obtain the high availability (HA) by using the
error tolerance method. Based on learning
cases one by one, you must also clearly
understand the limitations of the system that
requires an HA ability and the degree to
which the ability can reach.
History alarms Alarms that have cleared and been

acknowledged.
History performance data The performance data stored in the history

register and the auto-report performance data
stored on the network management system
are called history performance data in a
unified way.
Hotline phone The hotline phone number can be called

immediately by picking up only, but not by
dialing.
Idle resource optical NE When the T2000 is started successfully, an

NE icon called "Idle ONE" will be displayed
on the topological view. In this NE, the
subracks and boards that are not divided to
other optical NEs (such as OTM, OADM and
other NEs) are retained.

In-Service Trail Modifying A way of trail modification that allows you to

configure new routes for a trail and enables
the system to automatically delete the original
trail after you apply the settings to the NE.
Incremental filtering trail In this search mode, the network management

system first reserves the trail data of the
current client and then re-searches the service
configuration data of respective NEs on the
network management system according to the
newly given search condition to form the new
trail data and combine it with the original trail
data to get the result.
Incremental search The increment search mode compares the

trail information in network layer on the
network management system with the service
configuration information of respective NEs
on the network management system. If they
are inconsistent, the trail information will be
fed back into the list as an "Inconsistent
Trail". When the user has deleted the
inconsistent trail information, the system will
re-search for the service configuration
information that has not formed the trail in the
NE layer on the network management system.
Inloop An output signal is returned back to the

corresponding input port.
Inter-board wavelength protection This function is implemented by the

wavelength conversion boards that are
capable of dual fed and selective receiving.
The dual fed is implemented by adding a
passive optical splitter to the tributary. The
signal selection is implemented by the SCC
turning off the laser at the tributary side with
poorer signal quality according to the signal
quality of the lines of two wavelength
conversion boards, and letting the channel of
light with higher quality pass through the
coupler. The coupler is also a passive device
and only one channel of light can pass through
it. If there are two channels of light passing
through the coupler, they interferes each other
that would cause bit error to the service.
Hence, it is necessary to ensure that only the
channel of light with higher quality pass
through the coupler at the same time.
Intermediate office A concept in the telecommunications area. A

site that manages fiber/cable or grooms
services

Intra-Board wavelength protection The intra-board wavelength protection is

mainly implemented by the wavelength
conversion board with dual fed and signal
selection function. The dual fed is
implemented by the optical divider inside the
board, while the signal selection is
implemented by the board turning off the
laser of one of the receiving optical interfaces.
Hence, this protection mode is also called
optical wavelength intra-board path
protection. The switching in this protection
mode can be completed within a short time,
but the services must be interrupted during
the maintenance of the damaged board or
equipment. Hence, this protection mode has
a relatively lower reliability.
IP address Internet Protocol Address. A 32-bit address

that uniquely identifies a node in an IP
Internet network. An IP address consists of a
network ID and a unique host ID. An IP
address consists of the decimal values of its
eight bytes, separated with periods; for
example,192.168.7.27.
Isolated node A type of special NE or an optical port on an

NE. Logically, an isolated node does not
comprise an SDH NE of any types, which are
TM, ADM, REG and DXC
Layer A concept used to allow the transport network

functionality to be described hierarchically as
successive levels; each layer being solely
concerned with the generation and transfer of
its characteristic information.
LCT Local Craft Terminal. The terminal software

that is used for local maintenance and the
management of NEs in the singer-user mode,
to realize integrated management of multi-
service transmission network. See also
T2000.
License A permission provided by a vendor to

authorize the use of specific functions of a
product. Usually the license consists of
encrypted codes, and the operation authority
varies with different level of license.

Lock status Services are not switched to the protection

board or channel when a fault occurs, if
currently no switching takes place. If
currently the switching takes place, after the
working board or channel recovers to normal,
the services are not switched back to the
working board or channel.
Lockout of Switching When the switching condition is satisfied, this

function disables the service from being
switched from the working channel to the
protection channel. When the service has
been switched, the function enables the
service to be restored from the protection
channel to the working channel.
Login mode The client login mode includes single-user

and multi-user login modes. The multi-user
mode is the default mode.
Management flag A check box helps you to determine whether

the trail is a managed object of the trail
management function at the network layer.
By default, trails are managed objects. If
choosing not to manage it through the trail
management function, you can manage the
cross-connections of an individual NE
through the service configuration function
performed at a node.
Management information The information that is used for network

management in a transport network.
Manual switching When the protection channel is efficient and

there is no higher-level switching request,
services are manually switched from the
working channel to the protection channel,
thus testing whether the network still has the
protection capability.
MS node The WDM network node that has the

spectrum analysis unit in the link for which
the ALC function is configured.

Multi-trail protection service It is a protection mode in which multiple

services with different trails but with the same
sink protect an important service with the
same sink. This protection mode supports
protecting important services through non-
optical network trails, such as microwave. It
presently supports that three protection trails
protect one service trail. At the trail sink, it
monitors the quality of protection trail signals
and protects important services according to
the priority and the signal quality.
Main Topology The default network management system

client interface, and all topology management
functions are accessed here.
NE Network Element. NE includes the hardware

unit and the software running on it. Usually,
one NE has at least an SCC (system control
and communication) board which responsible
for the management and monitoring of the
NE. The NE software runs on the SCC board.
NE side The NE configuration data saved on the SCC

board of the equipment, which can be
uploaded to the network management system
and then stored in databases on the network
management system NE side.
Network layer The logical layer of the network management

system that saves the network data. The
configuration data related to a network is
saved in databases.
NNI Network Node Interface. The interface at a

network node which is used to interconnect
with another network node. See also SDH
NNI.
Non-revertive In non-revertive switching, there is a working

and protection line, board and so on. Services
remain on the protection line or board if the
switch requests are terminated; that is, when
the fault that caused them to switch to the
protection line or board is cleared.
NE database The databases that are saved in an NE.

Usually, the databases are saved in the SCC
board of an NE.

NE ID In a network, each NE corresponds to a

unique identifier, that is, the NE ID. In the
OptiX transmission equipment, it is specified
that the NE ID is a 24-bit binary digit, that is,
three bytes. The DIP switch on the SCC board
of the NE constitutes the lower 16 bits of the
NE ID. The higher eight bits of the NE ID is
the extended ID (default value: 9), which is
also called the subnetwork number. The
extended ID is usually used to identify
different subnetworks.
NE layer data on the T2000 The NE configuration data saved in the

T2000 databases. If data exists in an NE, the
T2000 uploads the data in an NE and saves it
at the NE layer. If data does not exist in an
NE, the T2000 downloads the data at the NE
layer to the NE. Consistency between the data
on the T2000 and the data on the NE is the
precondition of efficient running of the
transmission equipment.
Network layer data on the T2000 The network configuration data that is saved
in T2000 databases and is the data source for
the network function of the T2000. The
network layer data on the T2000 includes
three parts: fiber connection data, protection
subnetwork and SDH NNI data and trail
information.
NM Network Management. See T2000.
Non-protection subnet A subnet that has no protection.
Network segment The range of IP addresses in which the

gateway NE functions.
NE Explorer The main operation interface, of the T2000,

which is used to manage the OptiX
equipment. In the NE Explorer, the user can
configure, manage and maintain the NE,
boards, and ports on a per-NE basis.
NE Panel A graphical user interface, of the network

management system, which displays
subracks, boards, and ports on an NE. In the
NE Panel, the user can complete most of the
configuration, management and maintenance
functions for an NE.
Outloop An input signal is directly returned back to the

corresponding output port.

OWSP Optical Wavelength Shared Protection.

OWSP is a bidirectional ring, where each
node is equipped with an OWSP. There are
two channels (λ1 and λ2) in the main optical
path on the internal and external rings in each
span on a ring. The fibre and the OWSP on
the main optical path are connected with the
optical ports inputting λ1 and λ2 on the mux/
demux board (unnecessary to be connected
with the OTU), and thus λ1 and λ2 can be
added and dropped at every node.
Path A trail in a path layer.
Path protection The working principle of path protection:

When the system works in path protection
mode, the PDH path uses the dual fed and
signal selection mode. Through the tributary
unit and cross-connect unit, the tributary
signal is sent simultaneously to the east and
west lines. Meanwhile, the cross-connect unit
sends the dual fed signals from the opposite
end to the tributary unit, and the tributary unit
selectively receive the signal from the two
signals.
Performance register The memory space that is used to store

performance events.
Performance threshold A thresholding mechanism can be used to

generate an autonomous event report when
the performance of a transport entity falls
below a predetermined level.
PMU The unit that is used to monitor power supply

in the equipment.
Protection policy In case the service route provides multiple

service protections, different protection
strategies can be selected as required.
Protection strategy refers to the protection
mode given the priority in use for the trail:
protection, no protection, and extra traffic. Of
the above, the protection preference is
divided into trail protection and sub-network
connection protection.
Protection subnet A network concept in the network

management system. A protection subnet is
not an MSP ring or a path protection ring. A
protection subnet consist of NEs and fiber
connections.

Protocol controller status The status of the protocol controller of the

protection subnet of the MSP or SNCP type.
The statuses are not started, started, starting,
partially started.
Pane A major separate area of a window or dialog

box, usually used for display rather than data
entry.
Protection View The user interface, of the network

management system, which is used to manage
protection in the network.
Remote Network Monitoring (RMON) A manage information base (MIB) defined by

the Internet Engineering Task Force (IETF).
RMON is mainly used to monitor the data
flow of one network segment or the entire
network.
Revertive switching In revertive operation, the traffic signal

(service) always returns to (or remains on) the
working SNC/trail if the switch requests are
terminated; i.e. when the working SNC/trail
has recovered from the defect or the external
request is cleared.
Resource sharing Resource sharing means that a physical link

resource may belong to multiple protection
subnetworks.
Route The path that a trail passes through.
Route constraint The constraint conditions for calculating a

route. When creating a trail, the user can
specify the explicit route and the NEs that the
trail cannot pass. The explicit route and the
NEs are the constraints for calculating the
route.
RS232 The 25-pin interface standard that is defined

by EIA. In the asynchronous transfer mode
and there is no hand-shaking signal. It can
communicate with RS232 and RS422 of other
stations in point-to-point mode and the
transmission is transparent. Its highest speed
is 19. 2 kbit/s.
RS422 The specification that defines the electrical

characteristics of balanced voltage digital
interface circuits. The interface can change to
RS232 via the hardware jumper.

ROADM Reconfiguration Optical Add/Drop

Multiplexing. ROADM helps you to
terminate or pass through any one wavelength
at every node without affecting the existing
services. At the same time, ROADM can
change wavelengths through the network
management system remotely, to adjust
wavelengths added or dropped in a quick and
convenient manner. In addition, ROADM
enables power equalization at path level
through a built-in power equalization
function, and thus adjusts power for pass-
through paths in a better way than a band-
based dynamic gain equalizer (DGE) does.
Section A trail in a section layer.
S1 byte To implement protection switching of clocks

in the whole network, the NE must learn
about the clock quality information of the
clock reference source it traces. Therefore,
ITU-T defines S1 byte to transmit the
network synchronization status information.
Safe control switch The IPA safe switch is set in consideration of

the long-span networking requirement, which
cannot allow too low output optical power. If
the safe control switch is turned off, IPA
restarting optical power is the specified
output power of the OAU. Otherwise, the IPA
restarting optical power is restricted to less
than 10 dBm.
Script file It is the text file describing the physical

information and configuration information of
the entire network, including the
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 ASON
Information File.
SD trigger condition SD refers to signal degradation. The

multiplex section protocol defaults to start
switching in case of signal loss. In practice,
signal degradation severely affects some
services, so protection switching is needed.
Or, you can turn off this trigger condition
through the switch to avoid MS switching
when the signal degrades.

SD Signal Degrade. A signal indicating the

associated data has degraded in the sense that
a degraded defect (dDEG) condition is active.
SDH-ASON Trail A trail that spans both the SDH and ASON
domains.
SF Signal Fail. A signal indicating the associated

data has failed in the sense that a near-end
defect condition (not being the degraded
defect) is active.
SDH NNI SDH Network Node Interface. It is applied to

build communications connection with the
equipment beyond the management area of
the network management system. Usually,
the NM creates an SDH NNI by creating a
logical system on the port of an idle line
board, and the NE must be a TM without
protection and fiber connection.
Search domain The range of searching for NEs.
Server trail There is an inclusion relation between the

trails of different levels, for example, a trail
of a certain level contains multiple trails of
lower levels. In such a structure, the bearer
trail that bears another trail of lower level is
called the server trail.
Secondary filter trail In this search mode, the NM re-searches the

trail data displayed by the current client
according to the given search conditions,
helping the customer find the trail data which
interests him the most.
Shortcut menu A menu that is displayed when right-clicking

an object’s name or icon. Also called a
context menu.
Serial port extended ECC The ECC channel realized by means of serial
port.
Service clock working route The route of a service clock from the source
to the sink in a WDM system. The working
route can be in the form of point-to-point or
broadcast (That is, an input clock source
corresponds to multiple output clock
sources).

Service configuration policy When pass-through services are configured

on the newly added nodes, the mode of high-
order or low-order to pass through can be
selected. When the VC12 service over a VC4
exceeds a preset threshold, higher order
cross-connect is selected, otherwise lower
order cross-connect is selected. When the
services are not VC12 ones, they are
converted into VC12 equivalents. For
example: if there are two VC3 and four VC12
services on a VC4, there should be 21x2+4 =
46 VC12 services.
Service loading indication To indicate the status of loading services in

an SDH frame by using the C2 or V5 byte in
the SDH path overhead.
SLA (Service Level Agreement) An agreement signed between the network

carrier and the client, concerning the
treatments that the client can receive when
services are transferred in the network. The
agreement contains the information on
technology and commerce. Usually, SLA
refers to a specific QoS.
SLIP Serial Line Interface Protocol, defines the

framing mode over the serial line to
implement transmission of messages over the
serial line and provide the remote host
interconnection function with a known IP
address.
Subnet The network that consists of a group of

interconnected or correlated NEs, according
to different functions. For example,
protection subnet, clock subnet and so on.
Subnet connection protection Subnetwork connection protection uses the 1

+1 mode. SNCP is of 1+1 protection mode.
Payloads are transmitted simultaneously on
both the working and the protection sub-
network connections. When the working sub-
network connection fails, or when its
performance deteriorates to a certain level, at
the receiving end of the sub-network
connection, the signal from the protection
sub-network connection is selected according
to the preference rule. Switching usually
takes the single-end switching mode, thus no
protocol is needed.

Subnet mask Also referred to as the network mask off code,

it is used to define network segments, so that
only the computers in the same network
segment can communicate with one another,
thus suppressing broadcast storm between
different network segments.
Subnet number Subnetwork number is used to differentiate

the different network sections in the sub-
network conference. Actually it is the first
several digits (one or two) of the user phone
number. An orderwire phone number is
composed of the sub-network number and the
user number.
SNCP node The SNCP node of a ring subnet that can

support the ability to dually feed and
selectively receive trails. In this way, subnet
connection protection is realized . Usually,
the node of the path protection type is set as
an SNCP node.
Spread type The spread type of ATM service includes

point-to-point (p2p) and point-to-multipoint
(including p2mpRoot and p2mpLeaf).
Switching priority There may be the case that several protected

boards need to be switched; thus the tributary
board switching priority should be set. If the
switching priority of each board is set the
same, the tributary board that fails later
cannot be switched. The board with higher
priority can preempt the switching of that
with lower priority.
Synchronize Alarm When synchronizing the alarms, the network

management system checks the alarms in the
network management system database and
the alarms in the NE. If they are inconsistent,
the alarms in the NE are uploaded to the
network management system database and
overwrite the old ones.
Synchronize Fiber Service To re-upload all services carried on the

physical fiber links.
Synchronize NE time To apply the system time of the network

management system server to NEs so as to
keep the time of all NEs consistent.

T2000 The subnetwork management system

(SNMS) in the telecommunication
management network (TMN) hierarchy. The
T2000 is located between the NE level and
network level. The T2000 provides all
management functions at the NE layer and
some of the management functions at the
network layer. See also NM.
T2100 The network level management system for

the optical transport network, and is located
in the network management layer (NML) in
the TMN hierarchy.
T2000 LCT The NE layer management system for the

optical transport network. It can manage a
maximum of 37 NEs. The T2000 LCT can
uniformly manage OptiX series transmission
equipment from Huawei,
such as SDH, WDM, PTN equipment. See
also LCT.
Tag/Untag The Ethernet port that can identify and

transmit the packets with an 802.1q tag
header is referred to as a Tag port; otherwise
it is referred to as an Untag port.
Terminal NE A source NE or a sink trail.
Topology The network management system topology is

a basic component of the man-machine
interactive interface. The topology clearly
shows the structure of the network, the alarms
of different NEs,sub-networks in the
network, the communication status as well as
the basic network operation status.
Traffic frame discard flag It is the traffic frame discard control. Two
options are provided: enable and disable. It
indicates the means by which the NE discards
cells when the network is congested. When
the frame discard mark is closed, the cells will
be discarded at the cell level; when it is
opened, they will be discarded at the frame
level. Here, "frame" refers to the AAL
protocol data unit.
Trail A "transport entity" which consists of an

associated pair of "unidirectional trails"
capable of simultaneously transferring
information in opposite directions between
their respective inputs and outputs.

Trail consistency check Check whether the circuit route and the
activation status of the NM side and NE side
are the same, clear the superfluous MOs and
combine some of the circuits. During network
expansion, such an operation as adding fibers
to the SDH NNI or configuring/deleting
services through the configuration layer will
result in circuit inconsistency.
Trail management function A network level management function of the

network management system. Through trail
management, you can configure end-to-end
services, view graphic interface and visual
routes of a trail, query detailed information of
a trail, filter, search and locate a trail quickly,
manage and maintain trails in a centralized
manner, manage alarms and performance
data by trail, and print a trail report.
Trail View The user interface of the network

management system, that is used to manage
trails based on topologies. The Trail View
helps the user to quickly configure and
maintain trails. See also Protection View,
Clock View.
Transmission media layer route The route that consists of the physical media
(such as fibers and NEs)that a trail passes
through.
Trunk link A route that bears Ethernet services in the

network management system.
TPS protection The equipment level protection that uses one

standby tributary board to protect N tributary
boards . When a fault occurs on the working
board, the SCC issues the switching
command, and the payload of the working
board can be automatically switched over to
the specified protection board and the
protection board takes over the job of the
working board . After the fault is cleared, the
service is automatically switched to the
original board
Upper threshold The value that can generate a performance

threshold crossing if exceeded.

UAT Unavailable Time. A UAT event is reported

when the monitored object generates 10
consecutive severely errored seconds (SES)
and the SESs begin to be included in the
unavailable time. The event will end when the
bit error ratio per second is better than 10-3
within 10 consecutive seconds.
Unidirectional (protection) switching Unidirectional (Protection) Switching . For a

unidirectional fault (that is, a fault affecting
only one direction of transmission), only the
affected direction (of the trail, subnetwork
connection) is switched.
UNI User Network Interface. The interface

between the user and a network node.
Unprotected Services transmitted through an ordinary

way, once a failure or interruption occurs, the
data cannot be restored for lack of protection
mechanism.
Unterminated Service The service that is not terminated within the

management domain of the network
management system.
UPC/NPC Usage Parameter Control/Network

Parameter Control.During the
communication, the UPC is implemented to
monitor the actual traffic on each virtual
circuit that is input to the network. Once the
specified parameter is exceeded, measures
will be taken to control. NPC is similar to the
UPC in function. The difference is that the
incoming traffic monitoring function is
divided into UPC and NPC according to their
positions. The UPC locates at the user/
network interface, while the NPC at the
network interface.
Upload To query all or some of the configuration data

of the NE to the network management system
and overwrite the configuration data saved at
the NE layer of the network management
system.
User The user of the network management system

client or NE user.The user and password
define the corresponding authority of
operation and management.

User group User set refers to the set of NMS users with
the same management authorities. The
default user group includes: system
administrator, system maintainer, system
operator and system supervisor. The
attributes of user set include name and
detailed description.
Virtual fiber The fiber that is created between different

equipments. A virtual fiber is used to
represent the optical path that bears SDH
services in a WDM system.
VC12,VC3 trail The channels (that is trail group) provided for

trail-layer network nodes (such as a switch)
in a path-layer network, and act as the basic
unit of transport capacity of paths between
trail-layer network nodes.
VC4 server trail The path rate of the VC4 server trail is
150.336 Mbit/s. The VC4 server trail
provides transparent channels (that is, circuit
group) for circuit-layer network nodes (for
example, a switch) in a path-layer network,
and acts as the basic unit of inter-office
communication path. When the VC4 server
trail is configured, only the higher order
cross-connection of VC4 is generated in the
intermediate NE, but no cross-connection is
generated at the two ends, that is, no service
is added/dropped. Therefore, the VC4 server
trail is not a traditional service. It is only the
basis for VC3 and VC12 trail creation.
VCC Virtual Channel Connection. The VC logical

trail that carries data between two end points
in an ATM network.
VCI Virtual Channel Identifier . The identifier in

the ATM (Asynchronous Transfer Mode) cell
header that identifies to which virtual channel
the cell belongs.
VPI The field in the ATM (Asynchronous

Transfer Mode) cell header that identifies to
which VP (Virtual Path) the cell belongs.
Virtual concatenation For SDH, the virtual containers (VC) to carry

concatenated services are independent in
terms of their location in the frame structures,
so that they can be located flexibly.

Virtual NE Like a normal NE, a virtual NE is also

displayed with an icon on a window , but it is
only an NE simulated according to the
practical situation, which does not represents
an actual NE. Therefore, the actual status of
this NE cannot be queried and its alarm status
cannot be displayed with colors. Usually,
when the trail management function is used
for the NEs or subnets the network
management system cannot manage, or the
equipment is interconnected to the equipment
from other vendors for service configuration,
the end-to-end service configuration method
and the trail management capability are
provided.
Wave band A board like the MB2 divides the wavelength

resources into such fixed wavelength groups
as 1 – 4, 5 – 8 and 9 – 12, and so on. A
wavelength group is called a wave band, and
a wave band carrying services to be added or
dropped is called add/drop wave band.
WTR Wait to Restore. This command is issued

when working channels meet the restore
threshold after an SD or SF condition. It is
used to maintain the state during the WTR
period unless it is preempted by a higher
priority bridge request.
WTR time A period of time that must elapse before a

trail/connection that is recovered from a fault
can be used again to transport the normal
traffic signal and/or to select the normal
traffic signal.
Wavelength path protection ring The wavelength path protection ring

comprises the working ring and the protection
ring. Service signals are transmitted in the
two rings in opposite directions. In the
wavelength path protection ring, service
signals from one node (such as node A) to
another node (such as node C) are transmitted
via the working ring and the protection ring
at one time. Node C receives the signals from
the two rings at the same time and selects the
signal with higher quality.

Wavelength protection group The important data that is used to describe the
wavelength protection structure. The
wavelength path protection can only work
with the correct configuration of the
wavelength protection group.
Wavelength protection subnet The ring-chain structure that is used to

describe wavelength protection . The
wavelength protection subnet is the basic
network-level information and the basic
network-level data oriented to user . The user
can create or delete a protection subnet, set
parameters for the protection subnet as
required. In this way, the management at the
network layer is realized.
Working path A specific path that is part of a protection

group and is labeled working.
WXCP service Wavelength Cross-Connection Protection.

The services that have path protection on a
ring network. Services are dually fed and
selectively received. The working service and
the protection services are switched by using
the cross-connection function.

Operation Guide for Common Features B Acronyms and Abbreviations
B Acronyms and Abbreviations
ADM Add/Drop Multiplexer
AIS Alarm Indication Signal
ALC Automatic Level Control
ALS Automatic Laser Shutdown
AMI Alternate Mark Inversion code
APE Automatic Optical Power Equalization
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
AUX Auxiliary Equipment
BIOS Basic Input/Output System
BITS Building Integrated Timing Supply System
BWS Backbone WDM System
CDE Common Desktop Environment
CRC Cyclic Redundancy Code
DCC Data Communication Channel
DCN Data Communication Network
DDN Digital Data Network
DNI Dual Node Interconnection
Issue 01 (2009-06-30) Huawei Proprietary and Confidential B-1

B Acronyms and Abbreviations Operation Guide for Common Features
DGE Dynamic Gain Equalizer
DPC Destination (signalling) Point Code
DSE Dispersion Slope Equalizer
DWDM Dense Wavelength Division Multiplexing
ECC Embedded Control Channel
EGT Gigabit Ethernet Transparent Transmission Board
EML Element Management Layer
EMS Element Management System
EPL Ethernet Private Line
EPLAN Ethernet Private LAN
ESCON Enterprise System Connection
EVPL Ethernet Virtual Private Line
EVPLAN Ethernet Virtual Private LAN
FEC Forward Error Correction
FTP File Transfer Protocol
GCM Global Cluster Manager
GE Gigabit Ethernet
GNE Gate Network Element
GUI Graphical User Interface
HA High-Availability
HTTP Hyper-Text Transmission Protocol
ID Identification/Identity
IGMP Internet Group Management Protocol
IMA Inverse Multiplexing for ATM
iMAP Integrated Management Application Platform
IP Internet Protocol
B-2 Huawei Proprietary and Confidential Issue 01 (2009-06-30)

IPA Intelligent Power Adjustment
ISDN Integrated Services Digital Network
ITL Interleaver Unit
ITU-T International Telecommunication Union - Telecommunication

Standardization Sector
LAN Local Area Network
LCAS Link Capacity Adjustment Scheme
LCS Leased Circuit Service
LCT Local Craft Terminal
LOS Loss Of Signal
LPT Link-state Pass Through
LSP Label Switching Path
MAC Media Access Control
MCA Multi-channel Spectrum Analyzer Unit
MDI Medium Dependent Interface
MDP Message Dispatch Process
Mgr Manager
MIB Management Information Base
MML Man Machine Language
MO Managed Object
MODEM Modulator-Demodulator
MOIT Managed Object Instance Tree
MON MONitor
MPLS Multi-Protocol Label Switching
MS Multiplex Section
MSP Multiplex Section Protection
NE Network Element
NEL Network Element Level

NM Network Management
NML Network Management Layer
NMS Network Management System
NNI Network-network Interface
NSAP Network Service Access Point
NTP Network Time Protocol
OA Optical Amplifier
OADM Optical Add/Drop Multiplexer
OAM Operations, Administration and Maintenance
OAMS Optical fibre line Automatic Monitoring System
OCh Optical Channel
OCP Optical Channel Protection
OD Optical Demultiplexing
ODU Optical Demultiplexing Unit
ODUk Optical Channel Data Unit-k
OEQ Optical Equalizer
OIF Optical Internetworking Forum
OLA Optical Line Amplifier
OLP Optical Line Protection
OM Optical Multiplexing
OMS Optical Multiplexing Section
OMU Optical Multiplexer Unit
ONE Optical Network Element
OPUk Optical Channel Payload Unit-k
OSC Operation Supervisory Channel
OSF Operation System Function
OSI Open Systems Interconnection
OSN Optical Switch Node
OSNR Optical Signal to Noise Ratio
OSPF Open Shortest Path First

OTDR Optical Time-Domain Reflectometer
OTM Optical Terminal Multiplexer
OTN Optical Transmit Network
OTS Optical Transmission Section
OTU Optical Transponder Unit
OTUk Optical Channel Transport Unit-k
P2P Point To Point
PC Personal Computer
PDH Plesiochronous Digital Hierarchy
PE Provider Edge
PP Path Protection
PSTN Public Switched Telephone Network
PVP Permanent Virtual Path
QoS Quality of Service
RAS Remote Access Server
RDMS Relational Database Management System
RMON Remote Monitoring
RPR Resilient Packet Ring
RS Regenerator Section
RSTP Rapid Spanning Tree Protocol
RSVP Resource Reservation Protocol
RTN Radio Transmission Node
RUP Rational Unified Process
SAN Storage Area Network
SCC System Control & Communication Unit
SCS Sync Optical Channel Separator Board
SD Signal Degradation

SDH Synchronous Digital Hierarchy
SF Signal Failure
SMC Optical Supervisory Channel Unit
SML Service Management Layer
SMS Service Management System
SMTP Simple Mail Transfer Protocol
SNCMP Sub-Network Connection Multiple Protection
SNCP Sub-Network Connection Protection
SNCTP Sub-Network Connection Tunnel Protection
SNML Sub-Network Management Layer
SNMS Subnetwork Management System
SONET Synchronous Optical Network
SRLG Shared Risk Link Group
SSM Synchronization Status Message
SSU Synchronization Supply Unit
TCM Time Compressed Multiplex
TCP/IP Transmission Control Protocol/ Internet Protocol
TDA Tone & Data Access Unit
TDC Tunable Dispersion Compensator
TE Traffic Engineering
TIM Trail trace Identifier Mismatch
TMN Telecommunication Management Network
TPS Tributary Protection Switching
TU Tributary Unit
UAT Unavailable Time
UML Unified Modeling Language
UPC/NPC Usage Parameter Control/Network Parameter Control
UPSR Unidirectional Path Switched Ring
UTC Universal Time Coordinated

VB Virtual Bridge
VCI Virtual Channel Identifier
VCS Veritas Cluster Server
VLAN Virtual Local Area Network
VOA Variable Optical Attenuator Unit
VPI Virtual Path Identifier
VPN Virtual Private Network
VVR Veritas Volume Replicator
WAN Wide Area Network
WBA WDM Optical Booster Amplifier Unit
WDM Wavelength Division Multiplexing
WSF Work Station Function
WTR Wait-to-Restore
WXCP Wavelength Cross-Connection Protection


Operation Guide For Common Features - (V200R007C03 - 01) PDF

Загружено:

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

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

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

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

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

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

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

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

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

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

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

Operation Guide For Common Features - (V200R007C03 - 01) PDF

Загружено:

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

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

OptiX iManager T2000

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

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

Issue 01 (2009-06-30) Huawei Proprietary and Confidential i

2.5.2 Setting the Date Format........................................................................................................................2-19

ii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

2.12 Custom View...............................................................................................................................................2-80

Issue 01 (2009-06-30) Huawei Proprietary and Confidential iii

3.7.1 Setting the Password Template............................................................................................................3-27

iv Huawei Proprietary and Confidential Issue 01 (2009-06-30)

3.12.5 Setting Automatical Log-In for T2000 Users ...................................................................................3-65

4 Log Management........................................................................................................................ 4-1

Issue 01 (2009-06-30) Huawei Proprietary and Confidential v

4.3.3 Setting the Overflow Dump for Operation Logs....................................................................................4-9

vi Huawei Proprietary and Confidential Issue 01 (2009-06-30)

5.6 Query Path Status of the Board.....................................................................................................................5-30

Issue 01 (2009-06-30) Huawei Proprietary and Confidential vii

5.11 Deleting Topology Objects.........................................................................................................................5-66

6 Time Localization Management..............................................................................................6-1

viii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

7.4 Viewing Alarms............................................................................................................................................7-34

Issue 01 (2009-06-30) Huawei Proprietary and Confidential ix

7.9 Filtering Alarms Raised on T2000................................................................................................................7-64

x Huawei Proprietary and Confidential Issue 01 (2009-06-30)

7.24.2 Dumping Alarms Automatically........................................................................................................7-90

Issue 01 (2009-06-30) Huawei Proprietary and Confidential xi

8.4.7 Viewing Lower Order Performance Threshold-Crossing Records......................................................8-31

9 Keeping Data in the T2000 Consistent with NEs.................................................................9-1

xii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

9.3 Viewing the Asynchronous Information.........................................................................................................9-9

10 Backing Up and Restoring T2000 Data..............................................................................10-1

11 Backing Up and Restoring the NE Data............................................................................11-1

Issue 01 (2009-06-30) Huawei Proprietary and Confidential xiii

11.4 Backing Up History Alarms to a Flash Card...............................................................................................11-5

xiv Huawei Proprietary and Confidential Issue 01 (2009-06-30)

13.4.9 ASON Configuration Data Management Information List..............................................................13-74

Issue 01 (2009-06-30) Huawei Proprietary and Confidential xv

Figure 1-1 The position of the T2000 in TMN....................................................................................................1-2

Issue 01 (2009-06-30) Huawei Proprietary and Confidential xvii

Figure 9-2 T2000 Data Management Operation..................................................................................................9-7

xviii Huawei Proprietary and Confidential Issue 01 (2009-06-30)

Table 1-1 Manageable SDH series equipment.....................................................................................................1-3

Issue 01 (2009-06-30) Huawei Proprietary and Confidential xix

xx Huawei Proprietary and Confidential Issue 01 (2009-06-30)

About This Document

Product Name Version

OptiX iManager T2000 V200R007C03

1 T2000 V200R007C03 Overview This chapter describes its position in the

Issue 01 (2009-06-30) Huawei Proprietary and Confidential 1

2 Getting Started This chapter describes some preparation

3 Security Management This chapter describes operations about

4 Log Management This chapter describes how to perform log

5 Topology Management This chapter describes how to create

6 Time Localization Management This chapter describes how to set time

7 Alarm Management This chapter describes how to perform alarm

8 Performance Management This chapter describes how to perform

12 Viewing Reports This chapter describes how to view various

13 Appendix This chapter describes the reference