Huawei-Optix-Imanager-T2000-Operation-Guide 2 PDF

OptiX iManager T2000
V200R003C01
Operator Guide
Operator Guide for SDH
Issue 01
Date 2006-09-15
BOM 31162832
Huawei Technologies Proprietary

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.
Please contact our local ofce or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, 518129, P. R. China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2006. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this manual 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 all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Proprietary

Operator Guide Contents
Contents
About This Document ................................................................................................................. xix

1 Getting Started........................................................................................................................... 1-1
1.1 Starting or Shutting Down the T2000 ...................................................................................... 1-3
1.1.1 T2000 Software Architecture .......................................................................................... 1-3
1.1.2 Starting the T2000 Server............................................................................................... 1-6
1.1.3 Viewing the T2000 Working Status ................................................................................. 1-6
1.1.4 Starting the T2000 Client ............................................................................................... 1-7
1.1.5 Exiting a T2000 Client................................................................................................... 1-7
1.1.6 Shutting Down the T2000 Server .................................................................................... 1-8
1.1.7 Restarting the T2000 Server ........................................................................................... 1-8
1.2 T2000 License ...................................................................................................................... 1-8
1.2.1 Viewing License Information .......................................................................................... 1-8
1.2.2 Applying for License ..................................................................................................... 1-9
1.2.3 Changing the License................................................................................................... 1-10
1.3 T2000 Main Window........................................................................................................... 1-10
1.3.1 Main Topology............................................................................................................ 1-11
1.3.2 NE Explorer ............................................................................................................... 1-15
1.3.3 Protection View........................................................................................................... 1-16
1.3.4 Trail View .................................................................................................................. 1-17
1.3.5 Clock View................................................................................................................. 1-17
1.3.6 SDH NE Panel............................................................................................................ 1-18
1.3.7 Operation Object Status ............................................................................................... 1-20
1.3.8 Key GUI Components.................................................................................................. 1-21
1.3.9 Frequently Used Buttons .............................................................................................. 1-22
1.4 Custom View ...................................................................................................................... 1-23
1.4.1 Creating Custom Views................................................................................................ 1-23
1.4.2 Setting a Custom View as the Startup View .................................................................... 1-23
1.5 Customising Parameter Display ............................................................................................ 1-24
1.6 Copying Table Text Quickly................................................................................................. 1-25
1.7 Filtering Operation Objects on a View ................................................................................... 1-25
1.8 Moving Operation Objects ................................................................................................... 1-26
1.9 Locking Out Operation Objects............................................................................................. 1-26
1.10 Customising View Backgrounds .......................................................................................... 1-26
1.11 Searching for NEs on a View.............................................................................................. 1-27
Issue 01 (2006-09-15) Huawei Technologies Proprietary i

Contents Operator Guide
1.12 Operation Precautions ........................................................................................................ 1-27

1.13 List of Operations That Might Affect Network Running and Monitoring .................................. 1-27
1.14 Interface Typing Rules ....................................................................................................... 1-29
2 Security Management............................................................................................................... 2-1
2.1 Managing NM Users ............................................................................................................. 2-2
2.1.1 T2000 Security Management Strategy.............................................................................. 2-3
2.1.2 Operation Set Type ........................................................................................................ 2-3
2.1.3 Create an NM User ....................................................................................................... 2-4
2.1.4 Creating an NM User Group........................................................................................... 2-5
2.1.5 Creating an Operation Set .............................................................................................. 2-6
2.1.6 Creating an Equipment Set ............................................................................................. 2-8
2.1.7 Assigning Authority and Equipment for an NM User Group ............................................... 2-8
2.1.8 Assigning Authority and Equipment for a Single NM User................................................. 2-9
2.1.9 Setting Client Access Control ....................................................................................... 2-11
2.1.10 Example: Creating a User and Assigning Its Authority................................................... 2-12
2.1.11 Modifying NM User Validity ...................................................................................... 2-16
2.1.12 Modifying NM User Password Validity ........................................................................ 2-16
2.1.13 Changing the NM User Password ................................................................................ 2-17
2.1.14 Setting User Lockout Duration .................................................................................... 2-17
2.1.15 Setting Password Aging Warning Period ...................................................................... 2-18
2.1.16 Deleting an NM User................................................................................................. 2-19
2.1.17 Setting the Password Template .................................................................................... 2-19
2.1.18 Setting the Password Reuse Frequency......................................................................... 2-21
2.1.19 Setting the Password Reuse Period .............................................................................. 2-21
2.1.20 Conguring the Warning Screen for Login.................................................................... 2-22
2.1.21 Conguring the Weakness Password Dictionary ............................................................ 2-22
2.2 Managing T2000 Login ....................................................................................................... 2-23
2.2.1 Locking the T2000 Client Screen .................................................................................. 2-23
2.2.2 Switching an NM User ................................................................................................ 2-23
2.2.3 Forcing an NM User to Log Out of the T2000 ................................................................ 2-24
2.2.4 Switching Between Single User Mode and Multiple User Mode ........................................ 2-24
2.3 Managing Security Log........................................................................................................ 2-25
2.3.1 Operation Log............................................................................................................. 2-25
2.3.2 Viewing the Operation Log........................................................................................... 2-26
2.3.3 Setting a Scheduled Security Log Dump ........................................................................ 2-26
2.3.4 Setting Overow Dump for Security Log ....................................................................... 2-27
2.3.5 Dumping Security Log Immediately .............................................................................. 2-28
2.3.6 Viewing the NE Security Log ....................................................................................... 2-29
2.3.7 Transferring Operation Logs to Syslog Server................................................................. 2-29
2.4 Managing the Remote Maintenance User ............................................................................... 2-29
2.4.1 Enabling a Remote Maintenance User............................................................................ 2-30
2.4.2 Changing the Remote Maintenance User Password.......................................................... 2-31
2.4.3 Setting the Remote Maintenance User Authority ............................................................. 2-32
2.4.4 Setting the Remote Maintenance User Validity................................................................ 2-32
2.5 Conguring Network Security .............................................................................................. 2-33
2.5.1 Setting SSL Protocol Communication Between Server and Client...................................... 2-34
2.5.2 Controlling Communication Between NE and T2000 Through Ethernet Port....................... 2-35
ii Huawei Technologies Proprietary Issue 01 (2006-09-15)

2.5.3 Controlling Communication Between NE and T2000 Through a Serial Port ........................ 2-36
2.5.4 Controlling Communication Between NE and LCT ......................................................... 2-36
2.6 Managing NE Users ............................................................................................................ 2-37
2.6.1 Creating an NE User and Assigning Its Authority ........................................................... 2-37
2.6.2 Changing the NE User Password................................................................................... 2-38
2.6.3 Querying NE Security Parameters ................................................................................. 2-39
2.6.4 Querying NE User Groups ........................................................................................... 2-40
2.7 Managing NE Login ............................................................................................................ 2-40
2.7.1 Locking Out NE Login ................................................................................................ 2-40
2.7.2 Locking Out NE Settings ............................................................................................. 2-41
2.7.3 Switching an NE User ................................................................................................. 2-41
2.7.4 Forcing NE Users to Log Out of the NE ........................................................................ 2-42
3 Backing Up and Restoring Network Data ........................................................................... 3-1
3.1 T2000 Data Backup and Restoration Methods .......................................................................... 3-2
3.2 Keeping Data in the T2000 Consistent with NEs ...................................................................... 3-2
3.2.1 Checking Conguration Data Consistency Between an NE and the T2000 ............................ 3-3
3.2.2 Viewing the Out of Synchronization Information............................................................... 3-3
3.2.3 Synchronizing the NE Conguration Data Manually.......................................................... 3-4
3.2.4 Uploading NE Conguration Data ................................................................................... 3-4
3.2.5 Downloading NE Conguration Data............................................................................... 3-5
3.3 Backing Up the T2000 Data ................................................................................................... 3-5
3.3.1 Backing Up the T2000 MO Data Immediately .................................................................. 3-5
3.3.2 Backing Up the T2000 MO Data Periodically ................................................................... 3-6
3.3.3 Backing Up All Data in the T2000 Database .................................................................... 3-7
3.3.4 Backing Up T2000 Network Layer Data Through Script Export .......................................... 3-7
3.4 Restoring the T2000 Data ...................................................................................................... 3-8
3.4.1 Restoring the T2000 MO Data ........................................................................................ 3-8
3.4.2 Restoring All Data in the T2000 Database........................................................................ 3-9
3.4.3 Restoring T2000 Network Layer Data Through Script Export ........................................... 3-10
3.5 Backing Up NE Conguration Data ...................................................................................... 3-10
3.6 Initializing the T2000 Database............................................................................................. 3-11
3.7 Initializing NE Conguration Data in the T2000 ..................................................................... 3-12
3.8 Conguration Upgrade Wizard.............................................................................................. 3-12
4 Creating Topologies.................................................................................................................. 4-1
4.1 Topology on the T2000.......................................................................................................... 4-3
4.2 Creating Multiple NEs ........................................................................................................... 4-3
4.3 Creating a Single GNE .......................................................................................................... 4-4
4.4 Creating a Non-Gateway NE .................................................................................................. 4-6
4.5 Deleting an NE ..................................................................................................................... 4-7
4.6 Modifying the NE Name........................................................................................................ 4-7
4.7 Downloading Precongured NE Data ...................................................................................... 4-8
4.8 Creating Boards in Conguration Wizard ................................................................................. 4-8
4.9 Adjusting Boards in NE Panel ................................................................................................ 4-9
4.10 Deleting Boards................................................................................................................. 4-10
4.11 Modifying the NM Name ................................................................................................... 4-10
4.12 Creating Fibers Automatically............................................................................................. 4-10
Issue 01 (2006-09-15) Huawei Technologies Proprietary iii

4.13 Creating Fibers Manually ................................................................................................... 4-11

4.14 Deleting Fibers.................................................................................................................. 4-12
4.15 Modifying Fiber Information .............................................................................................. 4-13
4.16 Creating Cables between the T2000 and NEs........................................................................ 4-13
4.17 Creating a Topology Subnet................................................................................................ 4-14
5 Conguring Clocks ................................................................................................................... 5-1
5.1 Setting the NE Clock Source .................................................................................................. 5-3
5.2 Setting Clock Source Protection.............................................................................................. 5-3
5.3 Setting Switching Conditions for Clock Sources ....................................................................... 5-4
5.4 Setting Clock Source Reversion .............................................................................................. 5-5
5.5 Preventing Clock Signal Degrade............................................................................................ 5-6
5.6 Setting Clock Source Quality.................................................................................................. 5-6
5.7 Setting SSM Output .............................................................................................................. 5-7
5.8 Switching a Clock Source ...................................................................................................... 5-8
6 Conguring Orderwire ............................................................................................................ 6-1
6.1 Conguring Local Orderwire .................................................................................................. 6-2
6.2 Conguring Conference Calls ................................................................................................. 6-3
6.3 Conguring Express Orderwire ............................................................................................... 6-4
6.4 Dividing Orderwire Subnets ................................................................................................... 6-5
7 Managing Communication Between the T2000 and NEs.................................................. 7-1
7.1 Conguring Communication Between Subracks Without Fiber Connections ................................. 7-3
7.2 Conguring Communication for Third-Party Equipment Interconnection...................................... 7-3
7.3 Customising Communication Channels Between NEs................................................................ 7-4
7.4 Modifying the GNE’s IP or NSAP Address ........................................................................... 7-5
7.5 Changing a Normal NE to a GNE........................................................................................... 7-5
7.6 Modifying the GNE’s Communication Settings ...................................................................... 7-6
7.7 Changing a GNE to a Normal NE........................................................................................... 7-6
7.8 Changing the GNE for NEs.................................................................................................... 7-7
7.9 Testing the Communication Between the T2000 and the GNE .................................................... 7-7
7.10 Conguring Standby GNEs for NEs ...................................................................................... 7-8
8 Setting NE Time ........................................................................................................................ 8-1
8.1 Time Synchronization Schemes for the T2000 and NEs ............................................................. 8-2
8.2 Synchronizing NE Time with the T2000 Server Automatically ................................................... 8-2
8.3 Synchronizing NE Time with the T2000 Server Manually .......................................................... 8-3
8.4 Synchronizing NE Time with the NTP Server........................................................................... 8-3
9 Conguring Protection Subnets............................................................................................. 9-1
9.1 Searching for Protection Subnets............................................................................................. 9-3
9.2 Conguring MSP Rings ......................................................................................................... 9-3
9.2.1 Creating a Two-Fiber MS-SPRing ................................................................................... 9-4
9.2.2 Creating a Two-Fiber MS-DPRing................................................................................... 9-6
9.2.3 Creating a Four-Fiber MS-SPRing................................................................................... 9-9
9.2.4 Multiplex Section Squelch............................................................................................ 9-12
9.2.5 Conguring the MS Squelch Table ................................................................................ 9-12
9.2.6 Adjusting the Capacity of an MSP Ring......................................................................... 9-12
9.2.7 Expanding Link Capacity of an MSP Ring ..................................................................... 9-13
iv Huawei Technologies Proprietary Issue 01 (2006-09-15)

9.3 Conguring Linear MSP ...................................................................................................... 9-16

9.3.1 Creating 1+1 Linear MSP............................................................................................. 9-16
9.3.2 Creating M:N Linear MSP ........................................................................................... 9-18
9.3.3 Adjusting the Capacity of a Linear MSP ........................................................................ 9-21
9.3.4 Expanding Link Capacity of a Linear MSP..................................................................... 9-21
9.4 Conguring SNCP Protection ............................................................................................... 9-24
9.5 Conguring Path Protection.................................................................................................. 9-24
9.5.1 Creating a Two-Fiber Unidirectional PP Ring ................................................................. 9-25
9.5.2 Creating a Two-Fiber Bidirectional PP Ring ................................................................... 9-26
9.6 Conguring DNI Protection.................................................................................................. 9-27
9.6.1 Creating DNI Protection............................................................................................... 9-27
9.7 Conguring a Non-Protection Ring ....................................................................................... 9-28
9.8 Conguring Non-Protection Chains ....................................................................................... 9-29
9.8.1 Creating a Non-Protection Chain................................................................................... 9-30
9.8.2 Changing an NP Chain to a 1+1 Linear MSP.................................................................. 9-30
9.9 Deleting Protection Subnets.................................................................................................. 9-34
9.10 Conguring RPR Protection................................................................................................ 9-35
9.10.1 Creating Wrapping Protection ..................................................................................... 9-36
9.10.2 Creating Steering Protection........................................................................................ 9-37
9.10.3 Creating Wrapping and Steering Protection................................................................... 9-38
9.11 Conguring Trunk Link-Based RPR Rings ........................................................................... 9-39
9.11.1 Searching for RPR Rings............................................................................................ 9-40
9.11.2 Creating an RPR Ring Network................................................................................... 9-40
9.11.3 Modifying RPR Ring Parameters................................................................................. 9-42
9.11.4 Adjusting Link Bandwidth of an RPR Ring .................................................................. 9-44
10 Conguring SDH Services in the End-to-End Mode..................................................... 10-1
10.1 Principles for SDH Trail Creation........................................................................................ 10-3
10.2 Searching for SDH Trails ................................................................................................... 10-3
10.2.1 Searching for SDH Trails ........................................................................................... 10-4
10.2.2 Discrete Service......................................................................................................... 10-5
10.2.3 Discrete Service Causes and Handling Measures ........................................................... 10-5
10.3 Creating VC4 and VC4-Xc Trails........................................................................................ 10-7
10.3.1 Setting an SDH Optical Interface as an SDH NNI ......................................................... 10-7
10.3.2 Creating a Non-SNCP VC4/VC4-Xc Trail .................................................................... 10-8
10.3.3 Creating an SNCP VC4/VC4-Xc Trail ......................................................................... 10-9
10.4 Creating VC12 and VC3 Trails ..........................................................................................10-10
10.4.1 Creating a VC4 Server Trail ......................................................................................10-11
10.4.2 Creating a Non-SNCP VC12/VC3 Trail.......................................................................10-12
10.4.3 Creating an SNCP VC12/VC3 Trail ............................................................................10-13
10.5 Creating an SDH Trail Manually ........................................................................................10-14
10.6 Conguring Trail Overheads ..............................................................................................10-15
10.6.1 Conguring the Trace Byte for a Trail.........................................................................10-16
10.6.2 Conguring the C2 Byte for a Trail ............................................................................10-17
10.6.3 Setting Overhead Termination for a Trail.....................................................................10-18
10.7 Viewing SDH Trails..........................................................................................................10-19
10.8 Deleting SDH Trails .........................................................................................................10-20
10.9 Modifying Trail Names in Batches .....................................................................................10-21
Issue 01 (2006-09-15) Huawei Technologies Proprietary v

10.10 Changing Between SNCP and Normal Trails .....................................................................10-21

10.10.1 Changing the Non-SNCP Trail to the SNCP Trail .......................................................10-21
10.10.2 Changing the SNCP Trail to the Non-SNCP Trail .......................................................10-22
10.11 Joining and Splitting VC4 Server Trails.............................................................................10-23
10.11.1 Joining VC4 Server Trails........................................................................................10-24
10.11.2 Splitting a VC4 Server Trail.....................................................................................10-25
10.12 Conguring the Handover Plan ........................................................................................10-26
10.12.1 Creating Precongured Trails One by One .................................................................10-26
10.12.2 Creating Precongured Trails in Batches ...................................................................10-28
10.12.3 Deleting Handover Plans .........................................................................................10-29
10.13 Conguring Preconguration Groups ................................................................................10-30
10.13.1 Creating Precongured Trails One by One .................................................................10-30
10.13.2 Creating Precongured Trails in Batches ...................................................................10-32
10.13.3 Deleting Preconguration Groups .............................................................................10-33
11 Conguring Ethernet Services in the End-to-End Mode............................................... 11-1
11.1 Creating Ethernet Services.................................................................................................. 11-2
11.1.1 Relation Between SDH Trails and Ethernet Trails.......................................................... 11-2
11.1.2 Creating a Server Trail ............................................................................................... 11-3
11.1.3 Creating a Trunk Link Trail ........................................................................................ 11-3
11.1.4 Creating an EPL Trail ................................................................................................ 11-4
11.1.5 Creating an EVPL Trail.............................................................................................. 11-5
11.1.6 Creating an EPLn Trail............................................................................................... 11-6
11.1.7 Creating an EVPL(QinQ) Trail.................................................................................... 11-8
11.1.8 Adjusting the Ethernet Trail Bandwidth........................................................................ 11-9
11.1.9 Adjusting VB Mount Ports in an EPLn .......................................................................11-10
11.2 Creating RPR Ethernet Services .........................................................................................11-12
11.2.1 Creating an RPR EVPL Trail .....................................................................................11-12
11.2.2 Creating an RPR EPLn Trail ......................................................................................11-13
11.3 Deleting Services..............................................................................................................11-15
11.3.1 Deleting Ethernet Trails.............................................................................................11-15
11.3.2 Deleting Trunk Link Trails.........................................................................................11-15
11.4 Viewing Services ..............................................................................................................11-16
11.4.1 Viewing Trunk Link Trails.........................................................................................11-16
11.4.2 Viewing Relevant Trails of a Trunk Link Trail .............................................................11-17
11.4.3 Viewing Ethernet Trails .............................................................................................11-17
11.4.4 Viewing the Server Trail of an Ethernet Trail ...............................................................11-18
11.5 Setting the QoS ................................................................................................................11-18
11.6 Conguring the Spanning Tree...........................................................................................11-19
12 Conguring SDH Services Station by Station ................................................................ 12-1
12.1 Querying the NE Software Version ...................................................................................... 12-3
12.2 Dependency of SDH Service Conguration on NE Software Release ....................................... 12-3
12.3 Creating NE Logical Systems ............................................................................................. 12-3
12.4 Creating MSP Rings .......................................................................................................... 12-4
12.5 Creating a Linear MSP....................................................................................................... 12-4
12.6 Create Services Within a Protection Subnet .......................................................................... 12-5
12.6.1 Creating Services for a Non-Protection Chain ............................................................... 12-6
12.6.2 Creating Services for a 1+1 Linear MSP ...................................................................... 12-7
vi Huawei Technologies Proprietary Issue 01 (2006-09-15)

12.6.3 Creating M:N Linear MSP Services ............................................................................. 12-9

12.6.4 Creating Services for a Two-Fiber Unidirectional PP Ring .............................................12-11
12.6.5 Creating Services for a Two-Fiber Bidirectional PP Ring...............................................12-13
12.6.6 Creating Services for a Two-Fiber Unidirectional MSP Ring..........................................12-14
12.6.7 Creating Services for a Two-Fiber Bidirectional MSP Ring............................................12-17
12.6.8 Creating Services for a Four-Fiber Bidirectional MSP Ring ...........................................12-19
12.6.9 Creating SNCP Services ............................................................................................12-21
12.7 Conguration of Services Across Protection Subnets ............................................................12-24
12.8 Changing Between SNCP and Normal Services ...................................................................12-29
12.8.1 Changing a Normal Service to an SNCP Service ..........................................................12-29
12.8.2 Changing an SNCP Service to a Normal Service ..........................................................12-30
13 Conguring Ethernet Services Station by Station.......................................................... 13-1
13.1 Ethernet Services............................................................................................................... 13-2
13.2 Create Ethernet Services..................................................................................................... 13-7
13.2.1 Conguring EPL Services........................................................................................... 13-7
13.2.2 Conguring EVPL Services ........................................................................................ 13-8
13.2.3 Conguring EVPL(QinQ) Services .............................................................................13-10
13.2.4 Conguring EPLn Services ........................................................................................13-11
13.2.5 Conguring EVPLn Services .....................................................................................13-12
13.3 Create RPR Ethernet Services ............................................................................................13-14
13.3.1 Conguring RPR EVPL Services................................................................................13-14
13.3.2 Conguring RPR EVPLn Services..............................................................................13-15
13.4 Congure Ethernet QinQ Services ......................................................................................13-16
13.4.1 QinQ Services ..........................................................................................................13-17
13.4.2 Adding Double-Layer Tags Based on PORT ................................................................13-17
13.4.3 Adding a Single-layer Tag Based on PORT..................................................................13-18
13.4.4 Adding a Single-layer Tag Based on PORT+VLAN ......................................................13-19
13.4.5 Exchanging the User Tag and Adding a Single-Layer Tag..............................................13-20
13.5 Setting the QoS ................................................................................................................13-22
13.6 Conguring the Spanning Tree...........................................................................................13-22
14 Conguring ATM Services ................................................................................................. 14-1
14.1 SDH NNI ......................................................................................................................... 14-2
14.2 Setting the VC4 Port of an ATM Board as an SDH NNI ........................................................ 14-2
14.3 Installing the ATM Interface Board ..................................................................................... 14-2
14.4 Conguring Port Attributes for ATM Boards ........................................................................ 14-3
14.4.1 Conguring Internal Ports........................................................................................... 14-3
14.4.2 Conguring External Ports.......................................................................................... 14-3
14.4.3 Conguring Bound Paths............................................................................................ 14-4
14.5 Creating a Cross-Connection Between the ATM and the Line Boards....................................... 14-5
14.6 Conguring ATM Trafc.................................................................................................... 14-6
14.7 Conguring ATM Cross-Connections................................................................................... 14-7
14.8 Conguring Protection Groups and Protection Pairs for ATM Services..................................... 14-8
14.9 IMA................................................................................................................................. 14-9
14.10 Conguring ATM IMA Groups ......................................................................................... 14-9
15 Conguring Broadcast Services.......................................................................................... 15-1
15.1 Broadcast Data Services ..................................................................................................... 15-2
Issue 01 (2006-09-15) Huawei Technologies Proprietary vii

15.2 Conguring Broadcast Data Ports........................................................................................ 15-3

16 Conguring Board Parameters ........................................................................................... 16-1
16.1 Conguring SDH Boards.................................................................................................... 16-2
16.2 Conguring PDH Boards.................................................................................................... 16-2
16.3 Conguring Ethernet Boards............................................................................................... 16-3
16.3.1 Creating Ethernet Interface Boards .............................................................................. 16-3
16.3.3 Conguring External Ports.......................................................................................... 16-5
16.4 Conguring Ethernet Link Aggregation Groups .................................................................... 16-6
16.4.1 Creating Link Aggregation Groups .............................................................................. 16-7
16.4.2 Deleting Link Aggregation Groups .............................................................................. 16-7
16.4.3 Adding Link Aggregation Ports................................................................................... 16-7
16.4.4 Deleting Link Aggregation Ports ................................................................................. 16-8
16.4.5 Querying Link Aggregation Ports and Aggregation Status .............................................. 16-8
16.5 Conguring ATM Boards ................................................................................................... 16-9
16.5.1 Installing the ATM Interface Board.............................................................................. 16-9
16.5.3 Conguring External Ports.........................................................................................16-10
16.6 Conguring Optical Booster Ampliers ..............................................................................16-10
16.7 Conguring TDA Boards ..................................................................................................16-11
16.8 Conguring Board Protection.............................................................................................16-12
16.8.1 Creating a 1+1 Protection Group for Cross-Connect or Clock Boards ..............................16-13
16.8.2 Performing 1+1 Protection Switching for Clock Boards.................................................16-13
16.8.3 Creating a TPS Protection Group for PDH Boards ........................................................16-14
16.8.4 Performing TPS Switching for PDH Boards.................................................................16-15
16.8.5 Creating a Board Level Protection Group for Data Service Boards..................................16-16
16.8.6 Performing Board-Level Protection Switching for Data Service Boards ...........................16-17
16.8.7 Port Protection Group ...............................................................................................16-17
16.8.8 Creating Intra-Board Port Protection Groups ................................................................16-18
16.8.9 Creating Inter-Board Port Protection Groups ................................................................16-19
16.8.10 Performing a Switch for a Port Protection Group ........................................................16-20
17 Adjusting Networks ............................................................................................................. 17-1
17.1 Adjusting the Capacity of an MSP Ring............................................................................... 17-3
17.2 Expanding Link Capacity of an MSP Ring ........................................................................... 17-3
17.3 Adjusting the Capacity of a Linear MSP .............................................................................. 17-6
17.4 Expanding Link Capacity of a Linear MSP........................................................................... 17-7
17.5 Changing an NP Chain to a 1+1 Linear MSP........................................................................ 17-9
17.6 Adjusting Link Bandwidth of an RPR Ring .........................................................................17-11
17.7 Adjusting Boards..............................................................................................................17-12
17.8 Adding Extended Subracks ................................................................................................17-13
17.9 Adding Nodes to a Protection Subnet .................................................................................17-14
18 Managing ASON Networks................................................................................................ 18-1
18.1 Managing ASON Topology ................................................................................................ 18-6
18.1.1 Creating a Single GNE............................................................................................... 18-6
18.1.2 Uploading NE Data.................................................................................................... 18-8
18.1.3 Creating Domains for an ASON Network..................................................................... 18-8
viii Huawei Technologies Proprietary Issue 01 (2006-09-15)

18.1.4 Setting the Primary/Secondary NE............................................................................... 18-9

18.1.5 Synchronizing ASON NEs.........................................................................................18-10
18.1.6 Viewing ASON NE Software Version .........................................................................18-11
18.2 Managing TE Links ..........................................................................................................18-11
18.2.1 Synchronizing TE Links ............................................................................................18-12
18.2.2 Viewing TE Links ....................................................................................................18-12
18.2.3 Conguring Link Distance .........................................................................................18-13
18.2.4 Conguring SRLGs ..................................................................................................18-14
18.2.5 Creating Fibers .........................................................................................................18-15
18.3 Managing ASON Trails.....................................................................................................18-15
18.3.1 Synchronizing ASON Trails.......................................................................................18-17
18.3.2 Creating a Diamond ASON Trail................................................................................18-17
18.3.3 Creating a Gold ASON Trail......................................................................................18-20
18.3.4 Creating a Silver ASON Trail ....................................................................................18-23
18.3.5 Creating a Copper ASON Trail ..................................................................................18-26
18.3.6 Creating an Iron ASON Trail .....................................................................................18-29
18.3.7 Viewing ASON Trails ...............................................................................................18-32
18.3.8 Viewing ASON Trail Details......................................................................................18-34
18.3.9 Optimizing ASON Trails ...........................................................................................18-37
18.3.10 Activating/Deactivating ASON Trails........................................................................18-38
18.3.11 Deleting ASON Trails .............................................................................................18-39
18.3.12 Locking/Unlocking ASON Trails ..............................................................................18-39
18.3.13 Associating/Disassociating an ASON Trail.................................................................18-40
18.3.14 Setting Priorities for Rerouting ASON Trails..............................................................18-41
18.3.15 Degrading an ASON Trail to an SDH Trail ................................................................18-42
18.3.16 Upgrading an SDH Trail to an ASON Trail................................................................18-43
18.3.17 Switching a Diamond ASON Trail Manually..............................................................18-43
18.4 Viewing Alarms and Abnormal Events................................................................................18-44
18.4.1 Viewing Current Alarms of an ASON Trail .................................................................18-44
18.4.2 Viewing History Alarms of an ASON Trail..................................................................18-45
18.4.3 Viewing ASON Abnormal Events...............................................................................18-45
18.5 Viewing Performance Monitoring Data ...............................................................................18-46
18.5.1 Viewing Current Performance Data of an ASON Trail ..................................................18-46
18.5.2 Viewing History Performance Data of an ASON Trail...................................................18-46
18.6 Customising the ASON View.............................................................................................18-47
18.7 Managing Reserved Resources ...........................................................................................18-48
18.7.1 Conguring Reserved Resources ................................................................................18-48
18.7.2 Querying Reserved Resources ....................................................................................18-49
18.8 Managing Component Links ..............................................................................................18-49
18.8.1 Synchronizing Component Links ................................................................................18-49
18.8.2 Viewing Component Links.........................................................................................18-50
18.8.3 Adding/Deleting Component Links .............................................................................18-51
18.8.4 Setting Resource Reservation .....................................................................................18-52
18.9 Managing the Control Plane ..............................................................................................18-53
18.9.1 Synchronizing Control Links......................................................................................18-53
18.9.2 Viewing Control Links ..............................................................................................18-54
18.9.3 Setting Rerouting Reversion Time ..............................................................................18-54
18.9.4 Setting Route Calculation Strategies ...........................................................................18-55
Issue 01 (2006-09-15) Huawei Technologies Proprietary ix

18.9.5 Enabling OSPF Protocol............................................................................................18-56

18.9.6 Viewing the Link Management Protocol......................................................................18-56
18.9.7 Creating Control Channel ..........................................................................................18-57
18.10 Querying ASON Information on a Per-NE Basis ................................................................18-58
18.10.1 Querying ASON Trails ............................................................................................18-58
18.10.2 Querying TE Links .................................................................................................18-59
18.10.3 Querying Component Links .....................................................................................18-59
18.10.4 Querying Control Links ...........................................................................................18-59
18.11 Advanced Maintenance for ASON Control Plane................................................................18-60
18.11.1 Maintaining ASON Signaling ...................................................................................18-60
18.11.2 Maintaining the ASON Switch Controller ..................................................................18-61
19 Viewing Reports.................................................................................................................... 19-1
19.1 Report Types Supported by the T2000 ................................................................................. 19-3
19.2 Viewing the Networking Diagram ....................................................................................... 19-3
19.3 Viewing the Networkwide Data Report ................................................................................ 19-3
19.4 Viewing the Clock Tracing Diagram .................................................................................... 19-3
19.5 Viewing the Timeslot Allocation Diagram ............................................................................ 19-4
19.6 Viewing the NE Information Report .................................................................................... 19-4
19.7 Viewing the Slot Conguration Report................................................................................. 19-5
19.8 Viewing the Slot Information Report ................................................................................... 19-5
19.9 Viewing the Board Count Report......................................................................................... 19-5
19.10 Viewing the Board Information Report............................................................................... 19-6
19.11 Viewing the Board Details Report...................................................................................... 19-6
19.12 Viewing the Fiber/Cable Connection Report ....................................................................... 19-7
19.13 Viewing the Physical Location Information Report .............................................................. 19-7
20 Guaranteeing Network Performance ................................................................................ 20-1
20.1 Alarm............................................................................................................................... 20-3
20.2 Setting Networkwide Alarm Monitoring Strategy .................................................................. 20-4
20.2.1 Creating Alarm Attribute Templates............................................................................. 20-5
20.2.2 Alarm Correlation...................................................................................................... 20-5
20.2.3 Setting Alarm Correlation Rules.................................................................................. 20-6
20.2.4 Enabling Automatic Alarm Handling ........................................................................... 20-6
20.2.5 Customising Alarm and Abnormal Event Colors ........................................................... 20-7
20.2.6 Setting Alarm Forwarding .......................................................................................... 20-7
20.2.7 Enabling Visual and Audible Alarm in the Alarm Box ................................................... 20-8
20.2.8 Setting Alarm Filter Status.......................................................................................... 20-9
20.2.9 Setting Alarm Dump Conditions.................................................................................. 20-9
20.3 Setting NE Alarm Monitoring Strategy ...............................................................................20-10
20.4 Setting T2000 Alarm Monitoring Strategy ...........................................................................20-10
20.5 Setting Board/Port Alarm Monitoring Strategy.....................................................................20-11
20.5.1 Setting Alarm Severities and Automatic Reporting .......................................................20-11
20.5.2 Setting Alarm Suppression.........................................................................................20-12
20.5.3 Setting Bit Error Alarm Threshold ..............................................................................20-12
20.5.4 Setting the AIS Insertion Switch.................................................................................20-13
20.5.5 Inserting UNEQ........................................................................................................20-13
20.5.6 Setting Alarm Reversion............................................................................................20-14
x Huawei Technologies Proprietary Issue 01 (2006-09-15)

20.6 Setting the Alarm Monitoring Strategy for SDH Trails..........................................................20-14

20.6.1 Setting Alarm Suppression for SDH Trails...................................................................20-14
20.6.2 Setting Alarm Reversion for SDH Trails .....................................................................20-15
20.7 Setting Performance Monitoring Strategy ............................................................................20-15
20.7.1 Creating Performance Threshold Templates .................................................................20-16
20.7.2 Setting Board Performance Threshold .........................................................................20-17
20.7.3 Dumping Performance Data Immediately ....................................................................20-17
20.7.4 Setting Performance Dump Conditions........................................................................20-17
20.7.5 Starting or Stopping Performance Monitoring ..............................................................20-19
20.7.6 Setting Performance Monitoring Objects .....................................................................20-19
20.7.7 Setting ATM Board Performance Monitoring ...............................................................20-19
20.7.8 Setting Ethernet Performance Monitoring ....................................................................20-20
20.7.9 Setting Trail Performance Monitoring Strategy.............................................................20-20
20.8 Viewing Alarms ...............................................................................................................20-20
20.8.1 Synchronizing Networkwide Current Alarms ...............................................................20-22
20.8.2 Synchronizing the Current Alarms for the Specied NE ................................................20-22
20.8.3 Synchronizing Current T2000 Alarms .........................................................................20-23
20.8.4 Viewing Networkwide Current Alarms of a Selected Severity Level................................20-23
20.8.5 Viewing Networkwide Current Alarms for All Severities...............................................20-24
20.8.6 Viewing Current Alarms for an NE.............................................................................20-25
20.8.7 Viewing Current T2000 Alarms..................................................................................20-25
20.8.8 Viewing Current Alarms of an SDH Trail ....................................................................20-26
20.8.9 Viewing Current Alarms of a Trunk Link ....................................................................20-27
20.8.10 Viewing Current Alarms of an Ethernet Trail .............................................................20-27
20.8.11 Acknowledging Alarms ...........................................................................................20-28
20.8.12 Checking Alarms ....................................................................................................20-28
20.8.13 Viewing History Alarms ..........................................................................................20-29
20.8.14 Viewing Abnormal Events .......................................................................................20-29
20.8.15 Viewing Alarm Statistics and Outputting a Report ......................................................20-29
20.8.16 Turning Off Alarm Indicators in the Alarm Box .........................................................20-30
20.8.17 Clearing Visual and Audible Alarm on a Cabinet ........................................................20-30
20.9 Viewing Performance Data ................................................................................................20-31
20.9.1 Viewing Current Performance Data.............................................................................20-32
20.9.2 Viewing History Performance Data.............................................................................20-32
20.9.3 Viewing UAT Records ..............................................................................................20-33
20.9.4 Viewing Performance Threshold Crossings ..................................................................20-33
20.9.5 Analyzing History Performance Data ..........................................................................20-34
20.9.6 Forecasting Medium- and Long-Term Performance.......................................................20-34
20.9.7 Viewing Current Performance Data of an Ethernet Port .................................................20-35
20.9.8 Viewing History Performance Data of an Ethernet Port .................................................20-35
20.9.9 Viewing History Group Performance of an Ethernet Port ...............................................20-35
20.9.10 Setting History Control Group of an Ethernet Port ......................................................20-36
20.9.11 Setting Alarm Group of an Ethernet Port ..................................................................20-36
20.9.12 Viewing Statistic Group Performance of an Ethernet Port ............................................20-37
20.9.13 Viewing Current Performance Data of an ATM Port....................................................20-37
20.9.14 Viewing History Performance Data of an ATM Port ....................................................20-37
20.9.15 Viewing Current Performance Data of an SDH Trail ...................................................20-38
20.9.16 Viewing Current Performance Data of an Ethernet Trail ..............................................20-38
Issue 01 (2006-09-15) Huawei Technologies Proprietary xi

20.10 Resetting Performance Registers.......................................................................................20-39

20.10.1 Resetting Board Performance Registers .....................................................................20-39
20.10.2 Resetting ATM Performance Registers ......................................................................20-39
20.10.3 Resetting Ethernet Performance Registers ..................................................................20-40
20.11 Checking Protection Switching Status ...............................................................................20-40
20.11.1 Checking Networkwide Multiplex Section Parameters .................................................20-41
20.11.2 Checking TPS Switching status ................................................................................20-42
20.11.3 Checking 1+1 Board Switching Status .......................................................................20-42
20.11.4 Checking MSP Ring Switching Status .......................................................................20-42
20.11.5 Checking Linear MSP Switching Status.....................................................................20-43
20.11.6 Exercising MSP Protection Switching........................................................................20-43
20.11.7 Checking SNCP or PP Switching Status ....................................................................20-44
20.11.8 Checking GNE Switching Status...............................................................................20-44
20.11.9 Checking Clock Switching Status..............................................................................20-44
20.11.10 Checking Switching Status of an SNCP Trail............................................................20-45
20.11.11 Checking IMA Group Status...................................................................................20-45
20.11.12 Checking IMA Link Status.....................................................................................20-45
20.12 Managing Overhead Bytes ...............................................................................................20-46
20.13 Managing Logs...............................................................................................................20-47
20.13.1 Viewing the T2000 Security Logs .............................................................................20-48
20.13.2 Setting a Scheduled Security Log Dump....................................................................20-48
20.13.3 Viewing the NE Security logss .................................................................................20-49
20.14 Ethernet OAM Maintenance.............................................................................................20-49
20.14.1 Ethernet OAM ........................................................................................................20-49
20.14.2 Creating MPs .........................................................................................................20-50
20.14.3 Performing CC Check .............................................................................................20-50
20.14.4 Performing LB Check..............................................................................................20-51
20.14.5 Performing LT Check ..............................................................................................20-52
20.15 Maintaining Ethernet OAM at a Station.............................................................................20-53
20.16 Testing the Ethernet Communication Status .......................................................................20-53
20.17 Guaranteeing Laser Performance ......................................................................................20-54
20.18 Collecting Equipment Data ..............................................................................................20-54
20.19 Disabling Service-Affecting Settings Automatically ............................................................20-55
20.20 Cleaning Up the Hard Disk of the Computer......................................................................20-55
21 Troubleshooting .................................................................................................................... 21-1
21.1 Performing a Loopback ...................................................................................................... 21-2
21.1.1 Setting a Loopback at an SDH Interface....................................................................... 21-2
21.1.2 Setting a Loopback at a PDH Interface......................................................................... 21-3
21.1.3 Setting a Loopback at an Ethernet Interface .................................................................. 21-4
21.1.4 Setting a Loopback at an ATM Interface ...................................................................... 21-5
21.1.5 Setting a Loopback at a VC4 Path ............................................................................... 21-6
21.1.6 Setting a Loopback at a VC3 Path ............................................................................... 21-7
21.1.7 Setting a Loopback over a Trail .................................................................................. 21-8
21.2 Diagnosing Alarms ...........................................................................................................21-10
21.2.1 Creating Fault Diagnosis Rules ..................................................................................21-10
21.2.2 Starting the Fault Diagnosis Wizard ............................................................................21-11
21.3 Performing Protection Switching ........................................................................................21-12
xii Huawei Technologies Proprietary Issue 01 (2006-09-15)

21.3.1 MSP Protection Switching Priority .............................................................................21-13

21.3.2 Performing MSP Ring Switching................................................................................21-14
21.3.3 Performing Linear MSP Switching .............................................................................21-15
21.3.4 Performing SNCP Switching......................................................................................21-16
21.3.5 RPR Protection Switching Priority..............................................................................21-16
21.3.6 Performing RPR Protection Switching.........................................................................21-17
21.3.7 Performing RPR Protection Switching.........................................................................21-17
21.3.8 Performing 1+1 Board Protection Switching ................................................................21-18
21.3.9 Performing TPS Switching for PDH Boards.................................................................21-19
21.3.10 Performing Board-Level Protection Switching for Data Service Boards .........................21-19
21.4 Resetting Boards ..............................................................................................................21-20
21.4.1 Reset .......................................................................................................................21-20
21.4.2 Resetting the SCC Board ...........................................................................................21-20
21.4.3 Resetting a Non-SCC Board ......................................................................................21-21
21.5 Performing Remote Maintenance........................................................................................21-21
21.5.1 Remote Maintenance.................................................................................................21-21
21.5.2 Enabling the Remote Maintenance User ......................................................................21-22
21.5.3 Performing Remote Maintenance................................................................................21-23
22 Loading Software and Managing Conguration Data .................................................. 22-1
22.1 Loading NE Software ........................................................................................................ 22-3
22.2 Loading Board Software..................................................................................................... 22-4
22.3 Loading Patches Software .................................................................................................. 22-7
22.4 Backing Up Conguration Data .......................................................................................... 22-8
22.5 Restoring Conguration Data.............................................................................................. 22-9
22.6 Backing Up Database Package ...........................................................................................22-10
22.7 Restoring Database Package ..............................................................................................22-11
22.8 Testing LED Indicators .....................................................................................................22-12
22.9 Setting FTP Parameters .....................................................................................................22-13
A Mutual Exclusion List for Multiclient Operations........................................................... A-1
B Glossary ......................................................................................................................................B-1
C Acronyms and Abbreviations ............................................................................................... C-1
Index ................................................................................................................................................. i-1
Issue 01 (2006-09-15) Huawei Technologies Proprietary xiii

Operator Guide Figures
Figures
Figure 1-1 T2000 software architecture................................................................................................... 1-4

Figure 1-2 GUI .................................................................................................................................. 1-12
Figure 1-3 Menu ................................................................................................................................ 1-13
Figure 1-4 Menu ................................................................................................................................ 1-14
Figure 1-5 NE Explorer ...................................................................................................................... 1-16
Figure 1-6 Protection View.................................................................................................................. 1-17
Figure 1-7 Trail View ......................................................................................................................... 1-17
Figure 1-8 Clock View........................................................................................................................ 1-18
Figure 1-9 NE Panel ........................................................................................................................... 1-19
Figure 1-10 Path View ........................................................................................................................ 1-20
Figure 1-11 View legends.................................................................................................................... 1-20
Figure 9-1 DNI protection example ...................................................................................................... 9-28
Figure 9-2 Trafc ow before ber cut ................................................................................................. 9-36
Figure 9-3 Trafc ow after ber cut ................................................................................................... 9-37
Figure 9-4 Trafc ow before ber cut ................................................................................................. 9-38
Figure 9-5 Trafc ow after ber cut ................................................................................................... 9-38
Figure 9-6 Service route of RPR ring network ....................................................................................... 9-41
Figure 10-1 SDH NNI Services ........................................................................................................... 10-6
Figure 10-2 Joining and Splitting VC4 Server Trails .............................................................................10-23
Figure 10-3 Restrictions on VC4 Server Trail Joining............................................................................10-24
Figure 10-4 Restrictions on VC4 Server Trail Joining............................................................................10-25
Figure 11-1 Relation Between SDH Trails and Ethernet Trails ................................................................. 11-2
Figure 12-1 Service conguration for a non-protection chain ................................................................... 12-6
Figure 12-2 Service conguration for a 1+1 Linear MSP ........................................................................ 12-8
Figure 12-3 Creating M:N Linear MSP Services ...................................................................................12-10
Figure 12-4 Service conguration for a two-ber unidirectional PP ring...................................................12-12
Figure 12-5 Service conguration for a two-ber bidirectional PP ring ....................................................12-14
Figure 12-6 Service conguration for a two-ber unidirectional MSP ring................................................12-16
Figure 12-7 Service conguration for a two-ber bidirectional MSP ring .................................................12-18
Figure 12-8 Service conguration for a four-ber bidirectional MSP ring.................................................12-20
Figure 12-9 SNCP service conguration ..............................................................................................12-23
Issue 01 (2006-09-15) Huawei Technologies Proprietary xv

Figures Operator Guide
Figure 12-10 Path protection ring or SNCP ring with non-protection chain...............................................12-25
Figure 12-11 Path protection ring or SNCP ring with linear MSP............................................................12-26
Figure 12-12 Tangent rings.................................................................................................................12-28
Figure 13-1 Transparent Transmission Services Over Ethernet ................................................................. 13-2
Figure 13-2 Ethernet Convergent Transmission Services Sharing a PORT Port........................................... 13-2
Figure 13-3 Ethernet Convergent Transmission Services Sharing a VCTRUNK Port................................... 13-2
Figure 13-4 EPL services of Port type .................................................................................................. 13-3
Figure 13-5 EPL services sharing a PORT port...................................................................................... 13-3
Figure 13-6 EPL services sharing a VCTRUNK port.............................................................................. 13-3
Figure 13-7 EVPL services.................................................................................................................. 13-4
Figure 13-8 EPLn services .................................................................................................................. 13-4
Figure 13-9 EVPLn services ................................................................................................................ 13-5
Figure 13-10 RPR EVPL services ........................................................................................................ 13-5
Figure 13-11 RPR EVPLn services....................................................................................................... 13-6
Figure 14-1 ATM IMA group .............................................................................................................. 14-9
Figure 15-1 Overhead Byte ................................................................................................................. 15-2
Figure 15-2 The position of broadcast data ports.................................................................................... 15-2
Figure 16-1 Application of Link Aggregation Groups ............................................................................. 16-6
Figure 18-1 Three planes of the ASON................................................................................................. 18-2
Figure 21-1 Remote Maintenance........................................................................................................21-22
Figure A-1 Mutual exclusion list for multiclient operations ...................................................................... A-1
xvi Huawei Technologies Proprietary Issue 01 (2006-09-15)

Operator Guide Tables
Tables
Table 1-1 Description of T2000 functional modules.................................................................................. 1-4

Table 1-2 NE status ............................................................................................................................ 1-20
Table 1-3 Path and port status.............................................................................................................. 1-21
Table 1-4 Working Status .................................................................................................................... 1-21
Table 1-5 Key GUI components ........................................................................................................... 1-22
Table 1-6 Frequently used buttons ........................................................................................................ 1-22
Table 2-1 Comparison of NM application and transport network management system ................................... 2-4
Table 2-2 Operation log danger level .................................................................................................... 2-25
Table 3-1 Characteristics and application scenario of the three ways ........................................................... 3-2
Table 13-1 QinQ services .................................................................................................................... 13-6
Table 13-2 Common QinQ services .....................................................................................................13-17
Table 15-1 Denitions of the broadcast data port pins............................................................................. 15-3
Table 21-1 MSP Protection Switching Priorities ....................................................................................21-13
Table 21-2 RPR Protection Switching Priorities ....................................................................................21-17
Issue 01 (2006-09-15) Huawei Technologies Proprietary xvii

Operator Guide About This Document
About This Document
Purpose
The OptiX iManager T2000 Operator Guide for SDH describes the conguration and
maintenance operations of SDH equipment in the T2000.
This document provides guides for getting the reference information of T2000 operation.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX iManager T2000 V200R003C01
Intended Audience
The intended audiences of this document are:
n Policy planning
n NM conguration engineer
n Technical support engineer
Organization
This document consists of eighteen chapters and is organised as follows.
Chapter Description
Chapter 1 Getting Started This chapter introduces some preparation
operations that will ensure a smooth,
trouble-free launch of T2000.
Chapter 2 Security Management This chapter introduces operations about
security management of the T2000.
Chapter 3 Backing Up and Restoring This chapter introduces how to back up and
Network Data restore the T2000 database.
Chapter 4 Creating Topologies This chapter introduces how to create
topological objects in the T2000.
Chapter 5 Conguring Clock This chapter describes the operations of
conguring the SDH clock.
Chapter 6 Conguring Orderwire This chapter introduces the operations of
congure the orderwire.
Issue 01 (2006-09-15) Huawei Technologies Proprietary xix

About This Document Operator Guide
Chapter Description
Chapter 7 Managing Communication This chapter introduces basic communication
Between the T2000 and NEs conguration operations that ensure normal
communication between the NEs and the
T2000.
Chapter 8 Setting NE Time This chapter introduces the operations of
setting NE time.
Chapter 9 Conguring Protection Subnet This chapter introduces how to congure
equipment protection and protection subnet.
Chapter 10 Conguring SDH Services in the This chapter introduces how to congure
End-to-End Mode SDH services using trail function.
Chapter 11 Conguring Ethernet Services in This chapter introduces how to congure
the End-to-End Mode Ethernet services using trail function.
Chapter 12 Conguring SDH Services This chapter introduces how to congure
Station by Station SDH services at a single station.
Chapter 13 Conguring Ethernet Services This chapter introduces how to congure
Station by Station Ethernet services at a single station.
Chapter 14 Conguring ATM Service This chapter introduces how to congure
ATM services at a single station.
Chapter 15 Conguring Broadcast Service. This chapter introduces how to congure
broadcast services at a single station.
Chapter 16 Conguring Board Parameters This chapter describes how to congure
units.
Chapter 17 Adjusting the Networks This chapter describes how to adjust the
networks.
Chapter 18 Managing ASON Networks This chapter describes how to manage
ASON network.
Chapter 19 Viewing Reports This chapter describes how to view various
reports.
Chapter 20 Guaranteeing Network This chapter introduces how to use T2000 to
Performance maintain SDH equipments.
Chapter 21 Troubleshooting This chapter introduces basic operations of
fault maintenance.
Chapter 22 Loading Software and Managing This chapter describes how to upload and
Conguration Data download the software, and manage the
conguration data on the T2000.
Appendix A Mutual Exclusion List for This part lists the mutual exclusion list for
Multiclient Operations multiclient operation.
Appendix B Glossary This part lists the glossary used in the
document.
Appendix C Acronyms and Abbreviations This part lists the acronyms and abbreviations
used in the document.
xx Huawei Technologies Proprietary Issue 01 (2006-09-15)

Operator Guide About This Document
Symbol Conventions
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
WARNING result in 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.
TIP Indicates a tip that may help you solve a
problem or save you time.
NOTE Provides additional information to emphasize
or supplement important points of the main
text.
General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New
Roman.
Boldface Names of les, directories, folders, and users
are in boldface. For example, log in as user
root.
Italic Book titles are in italics.
Command Conventions
Boldface The keywords of a command line are in
boldface.
Italic Command arguments are in italics.
[] 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.
Issue 01 (2006-09-15) Huawei Technologies Proprietary xxi

About This Document Operator Guide
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.
Key1 + Key2 Press the keys concurrently. For example,
pressing Ctrl+Alt+A means the three keys
should be pressed concurrently.
Key1, Key2 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.
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 (2006-09-15)
Initial commercial release
xxii Huawei Technologies Proprietary Issue 01 (2006-09-15)

Operator Guide 1 Getting Started
1 Getting Started
About This Chapter

The following pages introduces some preparation operations that will ensure a smooth,
trouble-free launch of the T2000.
1.1 Starting or Shutting Down the T2000

The T2000 uses the standard client/server architecture and multi-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.
1.2 T2000 License
The user must apply for an authorized license to ensure that the T2000 is used correctly.
1.3 T2000 Main Window
The T2000 main windows and what you can do in the windows are described here.
1.4 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 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.
1.5 Customising Parameter Display
It is a customisable function of the T2000. You can customise the display of parameters as you
like, by putting important parameters to a place easy to nd and hiding those hardly used.
1.6 Copying Table Text Quickly
The T2000 allows you to copy and paste table text. You can copy texta table to other programs
quickly.
1.7 Filtering Operation Objects on a View
For ease of managing operation objects, you can lter operation objects shown on a view to
display the ones used only.
1.8 Moving Operation Objects
You can move the operation objects shown on the Main Topology.
1.9 Locking Out Operation Objects
You can lock out the operation objects shown on the Main Topology.
1.10 Customising View Backgrounds
When customising the background of topology views, you can select an image le packaged
or not packaged with the T2000.
1.11 Searching for NEs on a View
You can search for NEs on a view.
1.12 Operation Precautions
The operation precautions for ensuring correct operations are as follows:
1.13 List of Operations That Might Affect Network Running and Monitoring
Performing the operations listed below on the T2000 might affect the running or monitoring
of the network. Conrm an operation prior to performing it.
Issue 01 (2006-09-15) Huawei Technologies Proprietary 1-1

1 Getting Started Operator Guide
1.14 Interface Typing Rules

These rules specify the typing requirements for the text boxes in the T2000 operation interface.
These text boxes are used for typing character strings, le names, IP addresses, numerals,
passwords, dates, time, and so on.
1-2 Huawei Technologies Proprietary Issue 01 (2006-09-15)

1.1 Starting or Shutting Down the T2000

The T2000 uses the standard client/server architecture and multi-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
n You are recommended to start the computer and T2000 application by the process below:
start the computer, start the T2000.
n You are recommended to shut down the T2000 application and the computer by following
the process below: stop the T2000, shut down the computer.
1.1.1 T2000 Software Architecture

The T2000 uses the standard client/server architecture. The T2000 client implements
workstation function (WSF) of TMN for users to operate and manage transmission networks.
The T2000 server implements operating system function (OSF) of TMN, saving network data
and providing various management functions for transmission networks.
1.1.2 Starting the T2000 Server
You must start the T2000 server application for network management.
1.1.3 Viewing the T2000 Working Status
When you fail to log in to the T2000 or exit the T2000 abnormally, you can use System
Monitor to view the T2000 status. Using the System Monitor, you can view the status of
T2000 processes, including EMS server, Northbound Interface Module(iPASSAgent)process,
Northbound Interface Module(SNMP)process, Security server, Topo server, Schedulesrv
server, Naming Service, Notify Service, Syslog Agent, and database server.
1.1.4 Starting the T2000 Client
To manage networks through the T2000 client graphical user interface, you need to use the
T2000 client to log in to the T2000 server.
1.1.5 Exiting a T2000 Client
Before shutting down the T2000 server, you must shut down and exit the T2000 client.
1.1.6 Shutting Down the T2000 Server
You can shut down the T2000 server directly from System Monitor.
1.1.7 Restarting the T2000 Server
While the System Monitor is running, you can restart the T2000 server through the System
Monitor’s user interface.
1.1.1 T2000 Software Architecture

The T2000 uses the standard client/server architecture. The T2000 client implements
workstation function (WSF) of TMN for users to operate and manage transmission networks.
The T2000 server implements operating system function (OSF) of TMN, saving network data
and providing various management functions for transmission networks.
See Figure 1-1.

Figure 1-1 T2000 software architecture
Table 1-1 briey introduces the functions of each modules in the T2000 software structure.
Table 1-1 Description of T2000 functional modules

Module Function
T2000 Client client A Java-based graphical
application that can run on
different platforms. Through
the client, the user can
interact with the T2000
system to perform relevant
T2000 functions.

Module Function
T2000 Server EMS The primary process of the
T2000 server. It realizes the
core management functions
including fault, performance,
and conguration.
MDP The message distribution
process. Distributes all
messages between the T2000
server processes, as well as
between the T2000 server
and client.
Topo Server The topo server. Manages
the view information and the
coordinates information for
topological objects, such as
NEs and subnets.
Security Server The security server. Mainly
implements T2000 security
management, for example,
user validity check and user
operation validity check.
Schedulesrv Server The schedule server.
Manages scheduled tasks.
Northbound Interface Naming Service The name service. Publicizes
all objects provided by the
CORBA interface, in the
form of object names.
Before the upper layer
NMS/OSS obtains CORBA
objects, the NMS/OSS must
obtain object references from
the name serivce.
Notify Service The notify service. Reports
all alarms and events
(including conguration
change events, for example,
adding a board) in the T2000
to all monitoring NMS/OSS.
SNMP Agent Reports alarms to the
NMS/OSS through the
SNMP interface.
Northbound CORBA Performs connection
management, message
distribution, security
authentication, and
CORBA request and
response forwarding, for
the northbound CORBA
interface.

Module Function
System Monitor Sysmonitor Server Manages and monitors all
T2000 server processes
except MDP.
Sysmonitor Client A simple GUI monitoring
terminal based on Java.
NOTE
The Database refers to the database management software adopted for the T2000. On Windows, the
database software is SQL Server. On UNIX, the database software is Sybase.
1.1.2 Starting the T2000 Server

You must start the T2000 server application for network management.
Prerequisites
n The computer where the T2000 server is installed must be started correctly.
n The T2000 license must be in the server directory.
Procedure
Step 1 Double-click the T2000 Server icon on the desktop of the T2000 server. The System Monitor
login dialogue box will be displayed in a few seconds.
Step 2 Enter the user, password and server.
For example, User:admin, Password:T2000.
Step 3 Click Login to display the System Monitor window. Wait a few minutes until the Ems
Server, Schedulesrv Server, Security Server, Syslog Agent, Topo Server and Database
Server Process are all in Running status. Now the T2000 server is started successfully.
NOTE
When needed, you can also start the Northbound Interface Module(iPASSAgent) Process,
Northbound Interface Module(SNMP) Process, Naming Service, and Notify Service processes
manually.
----End
1.1.3 Viewing the T2000 Working Status

When you fail to log in to the T2000 or exit the T2000 abnormally, you can use System
Monitor to view the T2000 status. Using the System Monitor, you can view the status of
T2000 processes, including EMS server, Northbound Interface Module(iPASSAgent)process,
Northbound Interface Module(SNMP)process, Security server, Topo server, Schedulesrv
server, Naming Service, Notify Service, Syslog Agent, and database server.
Procedure
Step 1 Start and log in to the System Monitor.
Step 2 Click the Process tab. View the status of EMS Server, Northbound Interface
Module(iPASSAgent) Process, Northbound Interface Module(SNMP) Process, Naming
Service, Notify Service, Schedulesrv Server, Security Server, Syslog Agent, Topo
Serverand Database Server Process.
----End

1.1.4 Starting the T2000 Client

To manage networks through the T2000 client graphical user interface, you need to use the
T2000 client to log in to the T2000 server.
Prerequisite
The T2000 server must be started correctly.
Procedure
Step 1 On the computer of the T2000 client, double-click the T2000 Client icon on the desktop.
Step 2 Enter the user, password of the T2000 server.
For example: User: admin; Password: T2000.
NOTE
n The communication security mode of the server is by default set to the normal mode. You can
set it to the SSL mode as required.
n By default, the initial user name is admin, and the password is T2000. To protect the T2000 from
illegal logins, you need to instantly change this password and keep the new one.
n The administrator needs to create new T2000 users and assign them to certain authority groups.
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, Server, and Mode.
NOTE
n The communication security mode is default to Common. You can change it to the SSL mode
as required.
n The Port number does not need to be entered by the user. After the Mode is specied, the
system selects a Port number automatically.
n If the client and the server are installed on separate computers, they must have the same Mode
setting. Otherwise, the login will fail.
4. Click OK to complete adding a server.

5. Click OK to complete the server settings.
Step 4 Select a server and click Login
----End
1.1.5 Exiting a T2000 Client

Before shutting down the T2000 server, you must shut down and exit the T2000 client.
Prerequisite
The T2000 client must be started normally.
Procedure
Step 1 Select File > Exit from the Main Menu.
Step 2 Click OK in the conrmation dialog box.
----End

1.1.6 Shutting Down the T2000 Server

You can shut down the T2000 server directly from System Monitor.
Procedure
Step 1 Select System > Stop Server in the System Monitor.
NOTE
n Select System > Stop Server to close all processes of T2000 server.
n Select System > Shutdown System to close the T2000 Server and System Monitor.
Step 2 Click OK in the conrmation dialog box. Wait for a moment until the EMS Server, Security
Server, Syslog Agent, Topo Server and Schedulesrv Server are all in Stopped status. Now
the T2000 server is shut down successfully.
----End
1.1.7 Restarting the T2000 Server

While the System Monitor is running, you can restart the T2000 server through the System
Monitor’s user interface.
Prerequisite
The T2000 server must be shut down correctly.
Procedure
Step 1 Select System > Start Server from the Main Menu of the System Monitor.
Step 2 Waiting until Ems Server, Security Server, Topo Server, Syslog Agent,Topo Server and
Schedulesrv Server are all in the Running state. It indicates that the T2000 server has been
started correctly.
----End
1.2 T2000 License

The user must apply for an authorized license to ensure that the T2000 is used correctly.
1.2.1 Viewing License Information

The functions of the T2000 are controlled by license. Without a license, the T2000 can be
started, but the features and management capabilities are limited. So, make sure the license has
been correctly installed before starting the T2000.
1.2.2 Applying for License
The license le is not delivered to customers along with the T2000 installation CD-ROM. It
should be obtained by Huawei engineers according to the contract number and the MAC
address of the server.
1.2.3 Changing the License
You can change the license les in the T2000 server using the T2000 client.
1.2.1 Viewing License Information

The functions of the T2000 are controlled by license. Without a license, the T2000 can be
started, but the features and management capabilities are limited. So, make sure the license has
been correctly installed before starting the T2000.

Prerequisites
n The T2000 license is in the sub-directory "server" of T2000 installation directory.
n The T2000 server must be started correctly.
Procedure
Step 1 Select Help > About from the Main Menu.
Step 2 Click the License Information tab.
Step 3 Check the functions and management capabilities.
NOTE
n If the functions are consistent with what you purchase, the license works normally.
n If not, exit the T2000 client and server rst, and then reinstall the license. The detailed information
about how to install license is described in the OptiX iManager T2000 Installation Guide.
----End
1.2.2 Applying for License

The license le is not delivered to customers along with the T2000 installation CD-ROM. It
should be obtained by Huawei engineers according to the contract number and the MAC
address of the server.
Prerequisite
Huawei engineer applies for T2000 License according to the contract number and the MAC
address.
Context
NOTE
The T2000 License le is not sent to the customer with the T2000 installation CDROM, but is applied by
the Huawei engineer according to the contract number and the MAC address.
Procedure
Step 1 Get the contract number in project documents.
NOTE
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.

n In the Windows XP
1. Click Start and select Programs > Accessories > Command Prompt.
2. In the Command Prompt window, enter ipcong /all.
3. Get the MAC address, for example "00-50-BA-19-58-35".
n In the Solaris 10
1. Open a Terminal.
2. Enter su -root, then enter the password. For example, rootkit (the default password
of user root).
3. Enter ifcong -a.
4. Get the MAC address, for example "8:0:20:a1:7:c7".
Step 3 Send the contract number and the MAC address to the Huawei engineer or the nearer branch.

Step 4 The Huawei engineer will ll in the application form and mail to License Center for the
T2000 License.
NOTE
License Center E-mail: sdh-license@huawei.com; License Center Notes: sdh-license.
Step 5 The Huawei engineer will apply for the T2000 License le and send it to the customer.
----End
1.2.3 Changing the License

You can change the license les in the T2000 server using the T2000 client.
Prerequisites
n You must be an NM user with "NM administrator" authority or higher.
n The T2000 license must be obtained.
Context
NOTE
n When the type of equipment supported by the new license is different from that supported by the
old license, you can do as follows:
– You can change the license if the new license supports more types of equipment than the old
license and if the new equipment type is supported in the current version. You cannot change the
license if the new equipment type is not supported in the current version.
– You can change the license if the new license supports less types of equipment than the old
license and if no NEs are created on the T2000 for the unsupported equipment type. You cannot
change the license if NEs have been created on the T2000 for the unsupported equipment type.
n You cannot change the license if the new license supports different function items than the old license.
n When the new license supports a different number of clients than the old license, you can do as
follows:
– You can change the license if the new license supports less clients than the old license and if
the current logged in clients are less than the number of clients the new license supports. You
cannot change the license if the current logged in clients are more than the number of clients
the new license supports.
– You can change the license if the new license supports more clients than the old license.
For situations where you cannot change the license, you can shut down the server, change the license and
then restart the server.
Procedure
Step 1 Delete the original license from the T2000 server, and copy the authorized new license to the
installation directory of the T2000 server.
NOTE
If the T2000 server is installed on UNIX platform, copy the license to the /T2000/server directory. If
installed on Windows platform, copy the license to the \T2000\server\ directory.
Step 2 Choose Help > About from the Main Menu. Click the License Information tab, and then
click Change License.
----End
1.3 T2000 Main Window

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

1.3.1 Main Topology

Main Topology is the default T2000 client interface, and all of the topology management
functions can be accessed here. These functions include creating topological objects, subnets,
and bers or cables, searching for the existing equipment in the network.
1.3.2 NE Explorer
NE Explorer is the main operation interface of the T2000. For ease of navigation, the NE
Explorer window presents an expandable directory tree (Function Tree) in the lower left pane,
where conguration, management and maintenance of equipment can be accessed. To open the
conguration interface of a function, select an operation object, and then select a function from
the Function Tree. In the NE Explorer, select a board or an NE from the Object Tree and the
Function Tree shows the function(s) the board or NE supports.
1.3.3 Protection View
In the Protection View, you can search, view, create, set and manage the protection subnetwork
as well as manage independent nodes and SDH NNIs.
1.3.4 Trail View
The Trail View enables search, creation, conguration and maintenance management functions
on trails.
1.3.5 Clock View
The Clock View provides a visible platform to enable NE clock settings, networkwide clock
synchronization status query, clock tracing and search functions.
1.3.6 SDH NE Panel
NE Panel displays subracks, boards, and ports in different colors depending on their current
status. In the T2000, most equipment conguration, monitoring, and maintenance are
performed in the NE Panel window.
1.3.7 Operation Object Status
The meaning of legends on a view is described here.
1.3.8 Key GUI Components
The key T2000 GUI components are as follows:
1.3.9 Frequently Used Buttons
The frequently used buttons on the T2000 GUI are as follows:
1.3.1 Main Topology

Main Topology is the default T2000 client interface, and all of the topology management
functions can be accessed here. These functions include creating topological objects, subnets,
and bers or cables, searching for the existing equipment in the network.
GUI
To open the Main Topology, log in to the T2000, or select Window > Main Topology from
the Main Menu.

Figure 1-2 GUI
Menu
The menus of the Main Topology are shown in Figure 1-3 and Figure 1-4. Some menu items
are grayed out if restricted by license and NM user authorities.

Figure 1-3 Menu

Figure 1-4 Menu

Operation
Function Description Operation
Lock Locks the location of NE Right-click on the Main
icons on the Main Topology. Topology and select Lock.
Unlock Releases the locked NE icons Right-click at the blank space
on the Main Topology. on the Main Topology and
select Unlock.
1.3.2 NE Explorer
NE Explorer is the main operation interface of the T2000. For ease of navigation, the NE
Explorer window presents an expandable directory tree (Function Tree) in the lower left pane,
where conguration, management and maintenance of equipment can be accessed. To open the
conguration interface of a function, select an operation object, and then select a function from
the Function Tree. In the NE Explorer, select a board or an NE from the Object Tree and the
Function Tree shows the function(s) the board or NE supports.
NOTE
If you have opened ve NE Explorer windows, close those not in use and try again.
GUI
n For an SDH NE, right-click the NE icon on the Main Topology and choose NE Explorer
from the shortcut menu.
n For a WDM NE, double-click the optical NE icon on the Main Topology. In the displayed
window, right-click a subrack NE on the left-hand pane and choose NE Explorer from
the shortcut menu.
See Figure 1-5.

Figure 1-5 NE Explorer
1.3.3 Protection View

In the Protection View, you can search, view, create, set and manage the protection subnetwork
as well as manage independent nodes and SDH NNIs.
GUI
To open the Protection View, Select Conguration > Protection View from the Main Menu.

Figure 1-6 Protection View
1.3.4 Trail View

The Trail View enables search, creation, conguration and maintenance management functions
on trails.
GUI
To open the Trail View, Select Trail > Trail View from the Main Menu.
Figure 1-7 Trail View
1.3.5 Clock View

The Clock View provides a visible platform to enable NE clock settings, networkwide clock
synchronization status query, clock tracing and search functions.
GUI
To open the Clock View, Select Conguration > Clock View from the Main Menu.

Figure 1-8 Clock View
1.3.6 SDH NE Panel

NE Panel displays subracks, boards, and ports in different colors depending on their current
status. In the T2000, most equipment conguration, monitoring, and maintenance are
performed in the NE Panel window.
GUI
Double-click an NE icon on the Main Topology to display the NE Panel. See Figure 1-9.
To add a new board, just right-click an idle slot, and select a board type.

Figure 1-9 NE Panel
To select an operation related to an installed board, just right-click the installed board and
select it from the shortcut menu. For example, right-click an AUX and select Path View to
display the detailed path information.

Figure 1-10 Path View
1.3.7 Operation Object Status

The meaning of legends on a view is described here.
To view the meaning of legends on a view, select View > Legend from the Main Menu.
Figure 1-11 View legends
NE
The status of an NE icon are shown as follows:
Table 1-2 NE status

NE icon Status
The NE is a non-gateway NE.
The NE is not congured.
The NE is precongured.
The NE is a gateway NE.

NE icon Status
The data on the T2000 and that on the NE
are inconsistent.
Communication is lost. The NE is not logged

in.
Path and Port

In the Board View, the status of a path or a port icon are as follows:
Table 1-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 operation objects (such as NE) are shown in different colors. The
following table lists the default colors and the status related.
Table 1-4 Working Status

Color Description
Red Critical alarm Indicates the current highest
severity alarm of the operation object is
Critical.
Orange Major alarm Indicates the current highest
Major.
Yellow Minor alarm Indicates the current highest
Minor.
Dark magenta Warning alarm Indicates the current highest
Warning.
Green Normal state
Gray Communication interruption The operation
object has lost its communication with the
T2000.
Blue Not reported alarm
Light blue Unknown state
1.3.8 Key GUI Components

The key T2000 GUI components are as follows:

Table 1-5 Key GUI components

Component Example
Button
Shortcut icon
Radio button
Check box
Tab
Field
Drop-down menu
Menu
Function Tree
Dialog box
1.3.9 Frequently Used Buttons

The frequently used buttons on the T2000 GUI are as follows:
Table 1-6 Frequently used buttons

Button Functionality
Selects the objects.
Unfolds and displays all available options.

Folds the display of all available options.
Displays or hides a dialog box.
Switches to other NEs in the NE Explorer.

Button Functionality
Decreases the priority of the selected object.
Increases the priority of the selected object.
Displays a dialog box.
Queries from the NE.
Imposes the current settings.
Displays the latest result(s).
Exports the selected scheduled tasks to

Internet Explorer for printing.
Saves selected data to the specied le.
1.4 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 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.
Context
You can perform the following custom view functions:
1.4.1 Creating Custom Views

You can create a custom view.
1.4.2 Setting a Custom View as the Startup View
You can set a custom view as the startup view.
1.4.1 Creating Custom Views

You can create a custom view.
Procedure
Step 1 Select View > Custom View from the Main Menu.
Step 2 In the View Management dialog box, click Create.
Step 3 Click the Basic Attributes tab. Enter a view name and description, and select the background.
Step 4 Click the Object Selection tab. Select the objects that you want to include in the view.
Step 5 Click OK.
----End
1.4.2 Setting a Custom View as the Startup View

You can set a custom view as the startup view.

Procedure
Step 1 Open a custom view.
Step 2 Right-click in the custom view and select Set As Start View.
NOTE
To set the Main Topology as the startup view, right-click in any custom view and select Set Main
Topology As Start View.
Step 3 Restart the T2000 client, and the custom view is displayed automatically.
----End
1.5 Customising Parameter Display

It is a customisable function of the T2000. You can customise the display of parameters as you
like, by putting important parameters to a place easy to nd and hiding those hardly used.
Prerequisite
You must be an NM user with "NE and network 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 select 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 items in the shortcut menu, the sequence and the
column’s width.

----End
1.6 Copying Table Text Quickly

The T2000 allows you to copy and paste table text. You can copy texta table to other programs
quickly.
Procedure
Step 1 Select text in a table, and press the shortcut keys Ctrl+C.
NOTE
n Select all texts in the table by pressing the shortcut keys Ctrl+A. Only the current screen of the
table is supported.
n To view all data in the current table, click Print or Save As.
The selected text is copied to the system clipboard.

Step 2 Switch to another program, and press Ctrl+V.
----End
1.7 Filtering Operation Objects on a View

For ease of managing operation objects, you can lter operation objects shown on a view to
display the ones used only.
Procedure
Step 1 Select View > Filter from the Main Menu.

In the right-hand pane, click the Filter tab.

Step 2 Under Filter Tree, set lter criteria.
The qualied operation objects are shown on the view.
Step 3 If you want to hide the Filter tab, click the shortcut icon on the toolbar.
----End
1.8 Moving Operation Objects

You can move the operation objects shown on the Main Topology.
Procedure
Step 1 Select View > Unlock from the Main Menu.
Step 2 Select an NE icon on the Main Topology, hold the primary mouse button and drag the object
to the specied position.
----End
1.9 Locking Out Operation Objects

You can lock out the operation objects shown on the Main Topology.
Procedure
Step 1 Select View > Lock from the Main Menu.
There should be no operation object that can be moved on the Main Topology.
----End
1.10 Customising View Backgrounds

When customising the background of topology views, you can select an image le packaged
or not packaged with the T2000.
Prerequisite
You must be an NM user with "system operator" authority or higher.
Procedure
Step 1 Select File > Custom Options from the Main Menu. Click the Set Background tab.
Step 2 Optional: Right-click in the blank space of the view and select Set Background Map from
the shortcut menu.
Step 3 Optional: To add a background image le, click Add New Background.
Step 4 Optional: To delete a background image le, click Delete Background.
Step 5 Double-click the Background eld, and select a background image le.
NOTE
The type of image les can be .jpg or .gif.
Step 6 Click OK.

----End
1.11 Searching for NEs on a View

You can search for NEs on a view.
Procedure
Step 1 Select View > Search from the Main Menu.
The Search NE dialog box is displayed.
Step 2 Select the search conditions: Search Mode and Direction.
Step 3 Enter the NE name or NE ID according to the search mode.
Step 4 Click Search.
The NE found is shown on the Main Topology.
----End
1.12 Operation Precautions

The operation precautions for ensuring correct operations are as follows:
n Do not modify the system time when the T2000 is running. You need to set it before the
T2000 installation.To modify the system time of the server, exit the T2000 server and
restart it after the modication.
To modify the system time of the client, exit the T2000 client and restart it after the
modication.
n Avoid modifying the name and IP address of the T2000 server computer.
n Log in the Solaris CDE as t2000 in UNIX. While in Windows, you must log in as the user
you chosen during T2000 installation. Do not change the user and password of Windows.
n The data created on the NE is consistent with that on the T2000. When an NE is
congured and runs normally, you can keep the data on the NE and that on the T2000
consistent through manual or automatic synchronization.
n Back up the T2000 database periodically to minimize loss caused by system abnormity.
n It is recommended to query the latest data from NE before setting parameters.
n Usually, when a hazardous operation is performed, the T2000 will ask for conrmation.
1.13 List of Operations That Might Affect Network

Running and Monitoring
Performing the operations listed below on the T2000 might affect the running or monitoring
of the network. Conrm an operation prior to performing it.
Operation Impact
Reset a board May be service-affecting.
Initialize NE data Loss of data on the NE
Initialize T2000 data Loss of data on the T2000
Download The data on the T2000 overwrites that on the
NE. If the data on the T2000 is incorrect,
services might be interrupted.

Operation Impact
Upload Loss of the original data of the NE on the
T2000.
Paste The data of an NE overwrites that of other
NEs on the T2000.
Import a networkwide conguration le Overwrites the original network
conguration data.
Import an NE conguration le Overwrites the original NE conguration
data.
Import the NE list Overwrites the original NE list.
Clear the backup board data Loss of the original backup data of a board.
Set PDH path attributes Change the attributes of a PDH path. If the
settings are incorrect, service on this path
might be interrupted.
Set laser switch Turning on or off a laser might interrupt
services at this optical port.
Port or path loopback Services at the port or on the path are
interrupted.
Set overhead byte Incorrect settings might interrupt services on
this path.
2M PRBS test Services on this path are interrupted.
Automatic laser shutdown Services at this port might be interrupted.
Delete a protection group The original protection fails and services
Protection switching The protected services might be interrupted.
Delete a service or trail This service or trail is interrupted.
Activate and deactivate a service or trail This service or trail is interrupted.
Delete ATM trafc The ATM services might be interrupted.
Activate and deactivate ATM trafc The ATM services might be interrupted.
Delete an ATM cross-connection The ATM services are interrupted.
Activate and deactivate an ATM The ATM services might be interrupted.
cross-connection
Start and stop a protocol Services might be interrupted.
Interface loopback Services at this interface are interrupted.
Set NE communication The NE might lose its communication.
Set DCC access control The NE might lose its communication.
Lock Out/Unlock NE login Affects NE security management.
Allow/Inhibit LCT access Affects T2000 security management.
Delete current alarms Loss of alarm information affects the
T2000’s monitoring of the network.
Clear all alarms for an NE Loss of alarm information affects the
T2000’s monitoring of the NE.
Clear audible and visual alarm indications Affects the monitoring of NE status.
for an NE

Operation Impact
Set alarm suppression The T2000 cannot monitor the fault
corresponding to the suppressed alarm.
Set alarm reversion mode Affects the monitoring of NE alarms.
Reset a performance register Loss of performance statistics.
Change a trail Services on this trail might be interrupted.
Set trace bytes for a trail Services might be interrupted.
Set the C2 byte for a trail Services might be interrupted.
Set overhead termination for a trail Services might be interrupted.
Delete a ber cable Loss of the original ber cable data.
Delete a protection subnet The original protection fails and services
Delete an SDH NNI Loss of information on an SDH NNI affects
service conguration.
Delete data from the network layer Loss of network data including protection
subnet, trail and so on.
Delete an SNCP node The original SNCP protection fails and
services might be interrupted.
Modify parameters for a protection subnet Changing the protection mode might be
service affecting.
Scaling Upgrade a board, and scale an Services might be interrupted.
extension subrack and a protection node.
Initialize a database Loss of all T2000 data.
1.14 Interface Typing Rules

These rules specify the typing requirements for the text boxes in the T2000 operation interface.
These text boxes are used for typing character strings, le names, IP addresses, numerals,
passwords, dates, time, and so on.
Types of Character Strings

The character string is a kind of descriptive text so that there is no limitation for the characters
typed in. However, it should be noted that no " |\ /:*?"<> SPACE " can be included in
the character strings for either names of the PDH path, SDH path, NE, virtual NE board,
equipment room, subrack, cabinet, Transmission NM, optical ber, NE user, protection subnet,
circuit, logical system, J0, J1, PMU relay, DIP switch, EMU input and output paths, Ethernet
user, or all remarks.
File Name
General rule: le name + extension name, where, the number of letters, numerals or underlined
characters contained in the le extension name can not exceed 3 in total.
Naming rule: there should be no " \".*;>[]()!${}<> " contained in the le name. And no
SPACE symbol is allowed, if any, use "-" or "_" for substitute.
IP Address
The IP address is decimal, for example, 129.9.0.254:9801 (where 9801 is the port ID, which
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 is allowed.
Password
When password is typed, "*" is present in the password box instead of the specic content.
Date and Time

Generally, date and time can be selected from or typed in the "Time/Date Property" dialog
box, for example:
Time: 16:06:06 (Hour:Minute:Second)
Date: 2000-06-06 (Year-Month-Day)

Operator Guide 2 Security Management
2 Security Management
About This Chapter

Security management is a crucial function to prevent illegal login and ensure network data
security. Security management includes NM user management, NE user management and
security log management.
2.1 Managing NM Users

You can create NM users and assign and change their authorities. The NM user authorities are
role- and domain-based. An equipment set equals a management domain and an operation set
equals an authority group.
2.2 Managing T2000 Login
To ensure network data security, you can manage the users logged in to the T2000.
2.3 Managing Security Log
Save and check the T2000 log on a regular basis, because the log helps to detect illegal logins
and operations as well as to troubleshoot problems.
2.4 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.
2.5 Conguring Network Security
Network security includes the SSL protocol communication between the server and client,
different communication modes between the T2000ny and the NE, and connection control
between the NE and the LCT.
2.6 Managing NE Users
To ensure NE data security, you can manage the authorities and passwords for NE users.
2.7 Managing NE Login
To ensure NE data security, you can manage the users logged in to NEs.

2 Security Management Operator Guide
2.1 Managing NM Users

You can create NM users and assign and change their authorities. The NM user authorities are
role- and domain-based. An equipment set equals a management domain and an operation set
equals an authority group.
Context
It is recommended to create an NM user by the process below:
2.1.1 T2000 Security Management Strategy

The security management function realizes the role- and domain-based management for the
T2000 and NEs. With this function, the T2000 can also monitor in real time the users that
log in to the T2000 and NEs. In this way, the network and data security is ensured and illegal
logins or misoperations are avoided.
2.1.2 Operation Set Type
Operation set type species the application scope of every operation set. Currently there are
two types: NM application and transport network management system.
2.1.3 Create an NM User
For network maintenance purpose, you can create NM users and assign different authorities to
them.
2.1.4 Creating an NM User Group
Use this procedure to create an NM user group.
2.1.5 Creating an Operation Set
After the planning and creation of an operation set, you can assign the set to a specied user
group. In this way, all users in this user group are authorized to perform the operations in the
operation set. This function helps allocate and manage NM user authorities uniformly.
2.1.6 Creating an Equipment Set
After the planning and creation of an equipment set, you can assign the set to a specied
user group. In this way, all users in this user group are authorized to perform the operations
on the equipment within the equipment set. This function helps allocate and manage NM
user authorities uniformly.
2.1.7 Assigning Authority and Equipment for an NM User Group
Use this procedure to assign authority and equipment for an NM user group.
2.1.8 Assigning Authority and Equipment for a Single NM User
Use this procedure to create an NM user and assign its authority and equipment.
2.1.9 Setting Client Access Control
To prevent illegal login, after you create an NM user, you can specify a client IP address range
for the user. In this way, the NM user is able to log in to the T2000 server through only those
clients within the specied IP address range. If the IP address range is not specied, the NM
user can log in to the T2000 server through a client within any IP address ranges.
2.1.10 Example: Creating a User and Assigning Its Authority
The following describes how to create an NM user and assign its authority through an example.
2.1.11 Modifying NM User Validity
You can set whether an NM user is suspended or permanently enabled. For a user account that
is not permanently valid, you can set the date when this account will be aged.
2.1.12 Modifying NM User Password Validity
You can set whether an NM user password is permanently valid. For a password that is not
permanently valid, you can set the date when this password will be aged.
2.1.13 Changing the NM User Password
To ensure the network security, change the password periodically and keep it in a safe place. In
this way, misoperations and damage caused by password theft can be avoided.
2.1.14 Setting User Lockout Duration
If an NM user never logs in to the T2000 within a specied duration, the user will be locked out.

2.1.15 Setting Password Aging Warning Period

Before the user password ages, the user can be informed to change the password. In this way,
troubles caused by an invalid password can be avoided. By default, the warning period on the
T2000 is seven days before password aging.
2.1.16 Deleting an NM User
NM users no longer to be used must be deleted so as to avoid misoperations or damage caused
by user account theft.
2.1.17 Setting the Password Template
The password template denes the elements that are needed to construct a password. A
scientic and reasonable password template enhances the password complexity and makes
it more difcult to crack.
2.1.18 Setting the Password Reuse Frequency
For security purposes, when a password is changed, the new password cannot repeat old
passwords. The password reuse frequency species the number of last passwords that the
user cannot reuse. For example, if the password reuse frequency is set to 8, the user cannot
reuse any of the last 8 passwords.
2.1.19 Setting the Password Reuse Period
passwords. The password reuse period species a number of past days, so that the user cannot
reuse any old password used in these days. For example, if the password reuse period is set to
8 days, the user cannot reuse any old password used in the past 8 days.
2.1.20 Conguring the Warning Screen for Login
At T2000 login, a warning message can be displayed to inform the user of relevant rules that
the user must abide by. This message plays the role of a legal statement. The carrier can dene
this message according to their own rules.
2.1.21 Conguring 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-dene the weakness password dictionary as needed.
2.1.1 T2000 Security Management Strategy

The security management function realizes the role- and domain-based management for the
T2000 and NEs. With this function, the T2000 can also monitor in real time the users that
log in to the T2000 and NEs. In this way, the network and data security is ensured and illegal
logins or misoperations are avoided.
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 operation 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 specied
NEs and through specied clients.
With NM login management, NE login management and log management, the administrator
is able to monitor in real time the users that have logged in to the T2000 or NEs, and force
logged-in users at any time to log out of the T2000 or NEs.
2.1.2 Operation Set Type

Operation set type species the application scope of every operation set. Currently there are
two types: NM application and transport network management system.
Operation sets can be classied according to the two types. When specifying user and user
group authorities, you can assign authorities according to the two types.Table 2-1 lists their
comparison.

Table 2-1 Comparison of NM application and transport network management system

Operation set type Default operation set Application
NM application n NM administrator Applicable to T2000
n NM maintainer operations
n NM operator
n NM monitor
Transport network n Equipment authority Applicable to operations
management system n NE and network on the transport that the
administrator T2000 manages, that is, NE
operations
n NE and network
maintainer
n NE and network operator
n NE and network monitor
2.1.3 Create an NM User

For network maintenance purpose, you can create NM users and assign different authorities to
them.
Prerequisite
You must be an NM user with "NM administrator" authority or higher.
Procedure
Step 1 Select System Administration > NM Security Management > NM User Management
from the Main Menu.
Step 2 Right-click on and select New User from the shortcut menu.
Step 3 Complete the information in the New User dialog box. Click OK.

----End
2.1.4 Creating an NM User Group

Use this procedure to create an NM user group.
Prerequisite
NM You must be an NM user with "NM administrator" authority or higher.
Context
NOTE
When you assign authorities for the users, it is recommended to assign the authorities directly to the user
groups that the users belong to for the convenience of overall management.
Procedure
from the Main Menu.
Step 2 Right-click on and select New User Group from the shortcut menu.
Complete the information in the New User Group dialog box.

Step 3 Click OK or Apply.

----End
2.1.5 Creating an Operation Set

After the planning and creation of an operation set, you can assign the set to a specied user
group. In this way, all users in this user group are authorized to perform the operations in the
operation set. This function helps allocate and manage NM user authorities uniformly.
Prerequisite
Procedure
from the Main Menu.
Step 2 Right-click the icon and select New Operation Set from the shortcut menu.
Complete the information in the New Operation Set dialog box.

Step 3 Click the Member tab. Add new members to the operation set.
Step 4 Click OK.

----End
2.1.6 Creating an Equipment Set

After the planning and creation of an equipment set, you can assign the set to a specied
user group. In this way, all users in this user group are authorized to perform the operations
on the equipment within the equipment set. This function helps allocate and manage NM
user authorities uniformly.
Prerequisite
Procedure
from the Main Menu.
Step 2 Right-click the icon and select New Equipment Set from the shortcut
menu. Complete the information in the New Equipment Set dialog box.
Step 3 Click the Member tab. Add new members to the equipment set.
Step 4 Click OK.

----End
2.1.7 Assigning Authority and Equipment for an NM User Group

Use this procedure to assign authority and equipment for an NM user group.

Prerequisite
Procedure
from the Main Menu.
Step 2 Expand the tree and click a user group under the tree.
Step 3 Click the Authority tab. Click Add and the Add Authority dialog box is displayed.
Step 4 Select an operation type from the drop-down list on the top. Select the operation object and
operation set. Click Add.
NOTE
If you want to delete an authority for the user group, select the relevant record in the bottom list and
click Delete.
Step 5 Click OK.

----End
2.1.8 Assigning Authority and Equipment for a Single NM User

Use this procedure to create an NM user and assign its authority and equipment.

Prerequisite
Context
NOTE
User authority allocation principle:
1. After you create a T2000 user, you assign the user with certain user authorities by adding it to a user
group rather than adding specic authorities for it.
2. If the user authorities are too limited for a user to perform certain operations after it is added to a
default user group, you can create a new user group. 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 specic authorities for a user without creating new user
groups. In this case, follow the rules below.
n To modify specic authorities for a number of NEs, do not directly select these NE. Create
a new equipment set for the NEs that require more authorities, and assign authorities for the
equipment set.
n To add a number of operation authorities for a user, do not directly select all these operation
authorities. Create a new operation set for these operations, and assign this operation set to the
user.
Procedure
from the Main Menu.
Step 2 Right-click on and select New User from the shortcut menu.
Step 3 Complete the information in the New User dialog box. Click OK.
NOTE
Steps 1 through 3 are used to create an NM user.
Step 4 Expand the tree and click the newly created NM user under the tree.
Step 5 Click the Subjected to tab. Click Add and the Add User Group dialog box is displayed.
Step 6 Select a user group and click Add.

NOTE
Steps 4 through 6 are used to assign the user authority.
Step 7 Click OK.

----End
2.1.9 Setting Client Access Control

To prevent illegal login, after you create an NM user, you can specify a client IP address range
for the user. In this way, the NM user is able to log in to the T2000 server through only those
clients within the specied IP address range. If the IP address range is not specied, the NM
user can log in to the T2000 server through a client within any IP address ranges.
Prerequisite
Context
NOTE
If you select Default Access Control, it is allowed to access the T2000 within all IP address ranges
dened in the Client Access Control.
Procedure
Step 1 Select System Administration > NM Security Management > NM User Management from
the Main Menu. Double-click a user in the user list. Click the User Access Control tab. Click
Set Client Access Control, and the Set Client Access Control dialog box is displayed.
Step 2 Click New, and the Add Items of Access Control dialog box is displayed.

Step 3 Set the Start IP Address, End IP Addresses, Subnet Mask and Description parameters.
Click OK.
Step 4 Repeat Steps 2 through 3 to create more access control ranges as needed.
Step 5 Click Close.
Step 6 For the specied IP address range, check the Allow Access check box and click Apply. Then
the NM user is able to log in to the clients within this IP address range.
----End
2.1.10 Example: Creating a User and Assigning Its Authority

The following describes how to create an NM user and assign its authority through an example.
Prerequisites
n The ES_NM_user1 equipment set must be created.
n The OS_NM_user1 operation set must be created.
Context
Background: NM administrator A is responsible for T2000 security management. After the
T2000 installation and commissioning, an NM user NM_user1 needs to be created for NM
maintainer B. The specic requirement is as follows.
n NM user name: NM_user1
n NM user password: bt123456
n The NM_user1 user belongs to the maintainer group.
n Apart from the maintainer group authority, the NM user must also be assigned with the
OS_NM_user1 operation set authority, and allowed to operate on the ES_NM_user1
equipment set.
n NM_user1 is allowed to log in from the clients within a specied IP address range, which
is given below.
– Start IP address: 192.168.0.1
– End IP address: 192.168.0.168
– Subnet mask: 255.255.0.0
Procedure
from the Main Menu.
Step 2 Create the NM user NM_user1.
1. Right-click on and select New User from the shortcut menu.

2. In the New User dialog box, complete the following information.

Name: NM_user1
Password: bt123456
Conrm Password: bt123456
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. Under , select NM_user1 and click the Subjected to tab.

2. Click Add and the Add User Group dialog box is displayed.
3. Select Maintainer Group and click Add.

4. Click OK.
The user group is displayed in the list of the Subjected to tab.
Step 4 Adjust authority for NM_user1 so that the user will have OS_NM_user1 operation set authority
on the ES_NM_user1 equipment set.
1. Click the Authority tab and click Add.
2. In the Add Authority dialog box, complete the following information.
Authority Type: NM for Transmission Network
Operation Object: ES_NM_user1
Operation Set: OS_NM_user1

3. Click Add.
4. Click OK.
The added authorities are displayed in the authority list.
Step 5 Set the IP address range of clients from which NM_user1 is allowed to log in.
1. Click the User Access Control tab, and click Set Client Access Control.
2. Click New in the Set Client Access Control dialog box.
3. In the Add Items of Access Control dialog box, complete the following information.
Start IP Address: 192.168.0.1
End IP Address: 192.168.0.168
Subnet Mask: 255.255.0.0
4. Click OK to close the Add Items of Access Control dialog box.

5. Click Cancel to close the Set Client Access Control dialog box.
6. For the specied IP address range, check the Default Range check box and click Apply.

----End
2.1.11 Modifying NM User Validity

You can set whether an NM user is suspended or permanently enabled. For a user account that
is not permanently valid, you can set the date when this account will be aged.
Prerequisite
Context
CAUTION
Maintain the NM user validity on a regular basis so as to avoid misoperations or damage
caused by user account theft.
Procedure
from the Main Menu.
Step 2 Expand the tree and click an NM user under the tree.
Step 3 Click the General tab.
Step 4 Modify the following user validity parameters:Account Suspended, Account Permanently
Enabled and Account Aged at. Click Apply.
----End
2.1.12 Modifying NM User Password Validity

You can set whether an NM user password is permanently valid. For a password that is not
permanently valid, you can set the date when this password will be aged.
Prerequisite
Context
CAUTION
Maintain the NM user password validity on a regular basis so as to avoid misoperations or
damage caused by password theft.
Procedure
from the Main Menu.


Step 4 Modify the following password validity parameters:Password Permanently Effective and
Password Aged at. Click Apply.
----End
2.1.13 Changing the NM User Password

To ensure the network security, change the password periodically and keep it in a safe place. In
this way, misoperations and damage caused by password theft can be avoided.
Procedure
from the Main Menu.
Step 2 Expand the tree.

Step 3 Right-click an NM user in the expanded user tree and select Set Password from the shortcut
menu. The Set New Password dialog box is displayed.
Step 4 Enter the old password in Old Password, enter the new password in New Password and enter
it again in Conrm New Password. Click OK.
NOTE
If the current user is an NM administrator, he does not need to enter the old password while setting
other user’s password.
----End
2.1.14 Setting User Lockout Duration

If an NM user never logs in to the T2000 within a specied duration, the user will be locked out.
Prerequisites
n The NM user is already created.
Context
During NM user creation, the user can also set this parameter as needed. The description
given here is mainly for a created NM user.
NOTE
When the user account is locked out, it can only be unlocked by the NM administrator.

Procedure
from the Main Menu.
Step 4 Set the Set Login Intervals parameter to Yes.
Step 5 In Login Intervals (day), specify a value of days after which the user will be locked out if the
user never logs in during this period. Click Apply.
----End
2.1.15 Setting Password Aging Warning Period

Before the user password ages, the user can be informed to change the password. In this way,
troubles caused by an invalid password can be avoided. By default, the warning period on the
T2000 is seven days before password aging.
Prerequisites
n The NM user is already created.
n The user password is not permanently valid.
Context
During NM user creation, this parameter should also be set as needed. The description given
here is mainly for a created NM user.
Procedure
from the Main Menu.

Step 4 Modify Password Warning Period. ClickApply.
----End
2.1.16 Deleting an NM User

NM users no longer to be used must be deleted so as to avoid misoperations or damage caused
by user account theft.
Prerequisite
Procedure
from the Main Menu.

Step 3 Right-click an NM user in the expanded user tree and select Delete from the shortcut menu.
Step 4 Click OK.
----End
2.1.17 Setting the Password Template

The password template denes the elements that are needed to construct a password. A
scientic and reasonable password template enhances the password complexity and makes
it more difcult to crack.
Prerequisite
Only the t2000 user of the operating system is authorized to perform this operation.

Context
The password template denes the following elements.
n Password composition: A password may have three types of components: numerals,
letters, and special characters. The user can set the minimum number of characters for
each type of components.
n 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.
n 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 In the T2000 server installation directory, open the ss.cfg le.
NOTE
In Windows platform, the ss.cfg le is stored in the \T2000\server directory. In UNIX platform, the
ss.cfg le is stored in the /T2000/server directory.
Step 2 To specify the minimum number of numerals contained in the password, set the
nMinNumberNum option.
n nMinNumberNum = 0: means there is not such restriction.
n nMinNumberNum = -1: means numerals are not allowed in the password.
n nMinNumberNum = n: means a minimum of n numerals must be contained in the
password.
Step 3 To specify the minimum number of letters contained in the password, set the
nMinAlphabetNum option.
n nMinAlphabetNum = 0: means there is not such restriction.
n nMinAlphabetNum = -1: means letters are not allowed in the password.
n nMinAlphabetNum = n: means a minimum of n letters must be contained in the
password.
Step 4 Optional: To specify the minimum number of upper case letters contained in the password, set
the nMinUppercaseNum option.
If in Step 3 the nMinAlphabetNum value is set to -1, any setting in this step is invalid,
because the password cannot contain any upper case or lower case letters.
n nMinUppercaseNum = 0: means there is not such restriction.
n nMinUppercaseNum = -1: means upper case letters are not allowed in the password.
n nMinUppercaseNum = n: means a minimum of n upper case letters must be contained
in the password.
Step 5 Optional: To specify the minimum number of lower case letters contained in the password, set
the nMinLowercaseNum option.
If in Step 3 the nMinAlphabetNum value is set to -1, any setting in this step is invalid,
because the password cannot contain any upper case or lower case letters.
n nMinLowercaseNum = 0: means there is not such restriction.
n nMinLowercaseNum = -1: means lower case letters are not allowed in the password.
n nMinLowercaseNum = n: means a minimum of n lower case letters must be contained
in the password.
Step 6 To specify the minimum number of special characters contained in the password, set the
nMinSpecCharNum option.
n nMinSpecCharNum = 0: means there is not such restriction.
n nMinSpecCharNum = -1: means special characters are not allowed in the password.
n nMinSpecCharNum = n: means a minimum of n special characters must be contained in
the password.
Step 7 Set the password length.

1. To set the maximum password length, modify the nMaxPwdLength value. By default,
the value is set to 32.
2. To set the minimum password length for a normal user, modify the nMinPwdLength
value. By default, the value is set to 8.
3. To set the minimum password length for a super user, modify the
nSuperUserMinPwdLength value. By default, the value is set to 8.
Step 8 To set the maximum length of repeated character string between the password and the user
name, set the nMaxSameSubstringLenWithName option.
n nMaxSameSubstringLenWithName = 0: means there is not such restriction.
n nMaxSameSubstringLenWithName = -1: means the password cannot contain a
character string that is the full user name.
n nMaxSameSubstringLenWithName = n: means the maximum length of repeated
character string between the password and the user name is n-1 characters. For example,
if the n value is set to 4, the maximum length of repeated character string is 3.
Step 9 Save and close the le.
----End
2.1.18 Setting the Password Reuse Frequency

passwords. The password reuse frequency species the number of last passwords that the
user cannot reuse. For example, if the password reuse frequency is set to 8, the user cannot
reuse any of the last 8 passwords.
Prerequisite
Procedure
NOTE
Step 2 Modify the value of the MaxValidPwdCount option.

n By default, the value is set to 8.
n If the value is set to 0, it means there is not such restriction.
----End
2.1.19 Setting the Password Reuse Period

passwords. The password reuse period species a number of past days, so that the user cannot
reuse any old password used in these days. For example, if the password reuse period is set to
8 days, the user cannot reuse any old password used in the past 8 days.
Prerequisite

Procedure
NOTE
Step 2 Modify the value of the nMinDaysSameWithHisPwd option. By default, the value is set
to 60 days.
----End
2.1.20 Conguring the Warning Screen for Login

At T2000 login, a warning message can be displayed to inform the user of relevant rules that
the user must abide by. This message plays the role of a legal statement. The carrier can dene
this message according to their own rules.
Procedure
Step 1 Create the agreement.txt le in client/features under the T2000 client installation directory.
Step 2 Enter the contents for prompt in the agreement.txt le.
Step 3 Save the le.
----End
2.1.21 Conguring 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-dene the weakness password dictionary as needed.
Procedure
Step 1 Create a temporary directory, such as C:\tmp\client.
Step 2 Copy the imap.jar le from \client\lib (in the T2000 client installation directory) to
C:\tmp\client.
Step 3 Create the common\imap12\security\dict\ subdirectory in the C:\tmp\client directory.
Step 4 Create the dict1.wrd le in the C:\tmp\client\common\imap12\security\dict directory.
Step 5 Enter the contents of the password dictionary in the dict1.wrd le, one row for each character
string.
For example:
a
an
a lot of
Step 6 Save the le and exit.

Step 7 In the command line interface, run the following commands to upgrade the imap.jar le.
cd /d C:\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 le with the updated imap.jar le.
----End
2.2 Managing T2000 Login

To ensure network data security, you can manage the users logged in to the T2000.
Context
On the T2000 you can perform the following T2000 login management.
2.2.1 Locking the T2000 Client Screen

Use this procedure to lock the T2000 client screen.
2.2.2 Switching an NM User
Different NM users have different authorities. You can switch the NM user to perform
different levels of operations.
2.2.3 Forcing an NM User to Log Out of the T2000
For network security management, you can force a specied NM user to log out of the T2000 as
needed. In the single user mode, this function also forces all other users to log out of the T2000.
2.2.4 Switching Between Single User Mode and Multiple 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.
2.2.1 Locking the T2000 Client Screen

Use this procedure to lock the T2000 client screen.
Procedure
Step 1 Select File > Lock Client from the Main Menu.
The T2000 client appears to be locked out.
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 that of the user admin and click OK.
----End
2.2.2 Switching an NM User

Different NM users have different authorities. You can switch the NM user to perform
different levels of operations.
Prerequisite
You are already logged in to the T2000.
Context
NOTE
One NM user cannot log in to multiple clients at the same time.
Procedure
Step 1 Select File > Logout from the Main Menu. The Conrm dialog box is displayed. Click OK.

Step 2 Enter the user name and password in the Login dialog box.
Step 3 Click Login.

----End
2.2.3 Forcing an NM User to Log Out of the T2000

For network security management, you can force a specied NM user to log out of the T2000 as
needed. In the single user mode, this function also forces all other users to log out of the T2000.
Prerequisite
Procedure
from the Main Menu.

Step 3 Right-click an NM user in the expanded user tree and select Force to Exit from the shortcut
menu.
----End
2.2.4 Switching Between Single User Mode and Multiple 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
Procedure
Step 1 In the multiple user mode, select System Administration > Enable Single User Mode from
the Main Menu.
Step 2 Click OK when a warning message is displayed.
NOTE
If you want to switch from the single user mode to the multiple user mode, just select System
Administration > Enable Multiple User Mode from the Main Menu in Step 1.
----End

2.3 Managing Security Log

Save and check the T2000 log on a regular basis, because the log helps to detect illegal logins
and operations as well as to troubleshoot problems.
Context
On the T2000 you can perform the following log management.
2.3.1 Operation Log

Operation log keeps a record of users’ operations on the T2000 and NEs. By viewing logs,
administrator can keep track of and check user operations.
2.3.220.13.1 Viewing the Operation Log
All NM users’ operations on the T2000 and NEs are recorded in the operation log. The
T2000 provides the log browse function.
2.3.3 Setting a Scheduled Security Log Dump
You can set a schedule for security log dump. That is, the T2000 dumps the security log
automatically at a scheduled time, facilitating operation and maintenance.
2.3.4 Setting Overow Dump for Security Log
As time goes on, there will be more and more data stored in the security log. If the data amount
exceeds the maximum capacity, new data will overwrite old data and thus data loss is caused.
To avoid such data loss, security log dump must be performed in time.
2.3.5 Dumping Security Log Immediately
Security log can be dumped exibly. You can set dump conditions for the system to dump
the log automatically, or dump the log manually as needed. Immediate log dump is a manual
dump mode.
2.3.620.13.3 Viewing the NE Security Log
The NE security log records the operations done by all NE users and the results of those
operations. You can view the NE security log and lter the records by NE user, event name
and occurring time.
2.3.7 Transferring Operation Logs to Syslog Server
The T2000 can upload operation logs to the Syslog server. Operation logs keep a record of
all types of operations, alarms and performance events on the T2000, providing reference
information for the analysis of T2000 running status and follow-up maintenance.
2.3.1 Operation Log

Operation log keeps a record of users’ operations on the T2000 and NEs. By viewing logs,
administrator can keep track of and check user operations.
Pay close attention to operation logs. This helps you to learn how the system is running.
Log keeps a record of actions associated with equipment. For example, querying, creating
and deleting an NE or other objects.
You can also learn of user activities. For example, you can view actions done by an user
in the system.
Table 2-2 gives the meaning of danger levels of operation log.
Table 2-2 Operation log danger level

Danger level Meaning
Dangerous Important actions that may modify data in the
system or NE. For example, create a board.

Danger level Meaning

General Less important actions that may cause
problems in the future. For example, set the
user password.
Prompt Actions do not modify data and require to be
recorded for reference. For example, query
alarms.
2.3.2 Viewing the Operation Log

All NM users’ operations on the T2000 and NEs are recorded in the operation log. The
T2000 provides the log browse function.
Prerequisite
You must be an NM user with "NM monitor" authority or higher.
Procedure
Step 1 Select System Administration > Operation Log from the Main Menu.
Step 2 Set the condition for browsing the log.
Step 3 Click Query and browse the log.
----End

You can set a schedule for security log dump. That is, the T2000 dumps the security log
automatically at a scheduled time, facilitating operation and maintenance.
Prerequisite
You must be the user admin.
Context
NOTE
n The scheduled time for a task is based on the server time.
n When creating or modifying a scheduled task, if set the running period to Running once, set the time
to execute the task at least ve minutes later than the current time (that is, the server time).
Procedure
Step 1 Select System Administration > Schedule Task Management from the Main Menu.
Step 2 Click Create, and the Task Creation Wizard is displayed.
Step 3 Select Security Log Dump for the task type, enter the task name, and click Next.

Step 4 Set the running period and click Next.

Step 5 Set the time to run the task and click Next.
Step 6 Click Finish, and the system will dump the security log according to the above settings.
----End
2.3.4 Setting Overow Dump for Security Log

As time goes on, there will be more and more data stored in the security log. If the data amount
exceeds the maximum capacity, new data will overwrite old data and thus data loss is caused.
To avoid such data loss, security log dump must be performed in time.
Prerequisite
Procedure
Step 1 Select System Administration > NM Database Management > Dump To Files from the
Main Menu. The Data Dump dialog box is displayed.
Step 2 Click the Dumping Condition tab.
Step 3 Select Security Log in the Log Type tree.
Step 4 Set the Max. Storage Capacity(Record) parameter, which is default to 300000.
When data records of security log exceed this number, the dump is triggered.
Step 5 Set the Number of Dumped Record(Record/Time) parameter, which is default to 100000.
The system decides how many records to be dumped each time according to this value. For
example, when data records exceed 300000 pieces, a dump will be performed for 100000
pieces of data records.
Step 6 In Dump to (Path), specify the directory to store the dump le.
Step 7 Click OK.

----End
2.3.5 Dumping Security Log Immediately

Security log can be dumped exibly. You can set dump conditions for the system to dump
the log automatically, or dump the log manually as needed. Immediate log dump is a manual
dump mode.
Prerequisites
n There must be more than 10,000 data records in the security log.
Procedure
Step 1 Select System Administration > NM Database Management > Dump To Files from the
Main Menu. The Data Dump dialog box is displayed.
Step 2 Click the Instant Dump tab.
Step 3 Select Security Log for Log Type.
Step 4 Set the Deadline parameter.
All log data generated before the deadline will be dumped.
Step 5 Click Query.
The number and size of records that satisfy the dump conditions can be queried.
Step 6 Click Dump, and the Operation Conrmation dialog box is displayed.
If the dump size is too large, it is recommended to dump the log in batches.
Step 7 Click OK.

----End

2.3.6 Viewing the NE Security Log

The NE security log records the operations done by all NE users and the results of those
operations. You can view the NE security log and lter the records by NE user, event name
and occurring time.
Prerequisite
Context
NOTE
You can view but not delete the NE security log.
Procedure
Step 1 In the NE Explorer, click the NE and select Security > NE Security Log from the Function
Tree.
Step 2 Customise the log lter criteria.
Step 3 Click Query.
----End
2.3.7 Transferring Operation Logs to Syslog Server

The T2000 can upload operation logs to the Syslog server. Operation logs keep a record of
all types of operations, alarms and performance events on the T2000, providing reference
information for the analysis of T2000 running status and follow-up maintenance.
Procedure
Step 1 Choose System Administration > Syslog Conguration from the Main Menu.
The Syslog Conguration window is displayed.
Step 2 View the parameters and status of the current log forwarding server.
Step 3 Click New and the New Syslog Server window is displayed.
Step 4 Set the parameters for log forwarding server.
NOTE
n You must congure the IP address and port of the master server.
n If you want to congure the slave server, you also need to congure the IP address and port of
the slave server.
Step 5 Click OK.

Operation logs will be transferred to the Syslog server.
----End
2.4 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.

2.4.121.5.2 Enabling a Remote Maintenance User

Use this procedure to enable a remote maintenance user and thus enable the T2000 remote
maintenance terminal to access the T2000 server for remote maintenance. A remote
maintenance user is used to log in to the NE for remote maintenance.
2.4.2 Changing the Remote Maintenance User Password
For security purposes, the password for the remote maintenance user must be changed
periodically.
2.4.3 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
conguration.
2.4.4 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.
2.4.1 Enabling a Remote Maintenance User

Use this procedure to enable a remote maintenance user and thus enable the T2000 remote
maintenance terminal to access the T2000 server for remote maintenance. A remote
maintenance user is used to log in to the NE for remote maintenance.
Prerequisite
Procedure
Step 1 Select System Administration > 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
2.4.2 Changing the Remote Maintenance User Password

For security purposes, the password for the remote maintenance user must be changed
periodically.
Prerequisites
n The remote maintenance user must be enabled.
Context
CAUTION
Change the remote maintenance user password periodically to avoid misoperations or intended
damage caused by password disclosure.
Procedure
Menu. The Remote Maintenance User Management dialog box is displayed.
Step 2 Click Set Password and the Set User New Password dialog box is displayed.
Step 3 Type in the new password and conrm it. Click OK.
----End

2.4.3 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
conguration.
Prerequisites
Procedure
Step 2 Set Operation Authority. You can select query or conguration as needed.
Step 3 Click OK.

----End
2.4.4 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.
Prerequisites

Procedure
Menu. TheRemote Maintenance User Management dialog box is displayed.
Step 2 Set Valid Forever or Not to No.
Step 3 Enter the number of hours in Validity Period.
Step 4 Click OK.

----End
2.5 Conguring Network Security

Network security includes the SSL protocol communication between the server and client,
different communication modes between the T2000ny and the NE, and connection control
between the NE and the LCT.
2.5.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.
2.5.2 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.
2.5.3 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.

2.5.4 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 to commission an NE. You can
turn on LCT access for the NE on the T2000.
2.5.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.
Prerequisite
You must be an NM user with "NE and network administrator" authority or higher.
Context
CAUTION
The communication security setting takes effect only after the T2000 is restarted.
Procedure
Step 1 Open the System Monitor window.
Step 2 Select System > Communication Security Setting from the Main Menu. The
Communication Security Setting dialog box is displayed.
Step 3 Click the Security(SSL) radio button.
Step 4 Click OK.
Click OK in the Conrm dialog box. The setting will take effect after the T2000 is restarted.
Step 5 On the computer of the T2000 client, double-click the T2000 Client icon on the desktop.
Step 6 Enter the user, password and the IP address of the T2000 server.
Step 7 Select a server which the Mode is Security(SSL).

Step 8 Click OK.

----End
2.5.2 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
You must be an NM user with "NM maintainer" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE and select Communication > Access Control from the
Function Tree.
Step 2 In the Ethernet Access Control pane, click Refresh to query the Ethernet access enable status.
Step 3 Check the Ethernet Access Control check box and click Apply. The Ethernet access function
for the NE is enabled.
NOTE
If you want to disable this function, uncheck the Ethernet Access Control check box and click Apply.
----End

2.5.3 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
Procedure
Step 1 In the NE Explorer, click an NE and select 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
n If you want to disable this function, uncheck the Access NM check box. Click Apply.
n If you want to connect the serial port to command line, check the Access Command Line check box.
Step 4 Select an appropriate value from the Baud Rate drop-down list. Click Apply.
----End
2.5.4 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 to commission an NE. You can
turn on LCT access for the NE on the T2000.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and select 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 Allowed.
----End
2.6 Managing NE Users

To ensure NE data security, you can manage the authorities and passwords for NE users.
Context
On the T2000 you can perform the following NE user management.
2.6.1 Creating an NE User and Assigning Its Authority

To guarantee NE data security, only an NE user is allowed to log in to the NEs. The NE
user is able to perform operations on the NEs only within its assigned authority. The T2000
administrator is advised to create NE users before conguring services.
2.6.2 Changing the NE User Password
To ensure network security, you are recommended to change the NE user password periodically.
2.6.3 Querying NE Security Parameters
According to the default security settings, the NE is able to tell whether the NE user password
is valid and thus decide whether the login is allowed. The T2000 administrator needs to learn
the NE security settings and modify the NE user password before it becomes invalid.
2.6.4 Querying NE User Groups
NE users at different levels are divided to different NE user groups. In this user interface, you
can query NE users included by various NE user groups of an NE.
2.6.1 Creating an NE User and Assigning Its Authority

To guarantee NE data security, only an NE user is allowed to log in to the NEs. The NE
user is able to perform operations on the NEs only within its assigned authority. The T2000
administrator is advised to create NE users before conguring services.
Prerequisite
Context
NOTE
The default NE user is of the system level. To guarantee NE data security, it is recommended to assign
NE users with different authorities as needed.
Procedure
Step 1 Select System Administration > NE Security Management > NE User Management from
the Main Menu.
Step 2 In the left pane, select a NE and click the double-right-arrow button (red).

Step 3 Click Add.

The Add NE User dialog box is displayed.
Step 4 Enter the NE user name in the NE User eld.
NOTE
The NE user name must contain letters, or it can be a combination of letter, symbol and numeral. It is
recommended that the user name contains a maximum of eight characters.
Step 5 Select User Level as needed.

Step 6 In the NE User Flag eld, 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 eld and enter it again in the Conrm Password
eld.
Step 8 In the NE Name eld, select the NEs that this NE user is allowed to manage.
Step 9 Click OK.
----End
2.6.2 Changing the NE User Password

To ensure network security, you are recommended to change the NE user password periodically.
Prerequisites
n You must be an NM user with "NE and network administrator" authority or higher.
n The NE user must be created.

Context
NOTE
It is recommended to change the password periodically for the purpose of security.
Procedure
Step 1 Select System Administration > NE Security Management > NE User Management from
the Main Menu.
Step 2 In the left pane, select the appropriate NE and select Set Password. The Set Password of
NE User dialog box is displayed. Enter the password in New Password and enter it again in
Conrm Password.
Step 3 Click OK.

----End
2.6.3 Querying NE Security Parameters

According to the default security settings, the NE is able to tell whether the NE user password
is valid and thus decide whether the login is allowed. The T2000 administrator needs to learn
the NE security settings and modify the NE user password before it becomes invalid.
Prerequisite
Context
NOTE
The NE security parameters include: Allowable Used Times for Outdated Password, Password Max.
Valid Period(day), Password Min. Valid Period(day), Password Uniqueness(Entries), Lock Testing
Time(minute), Allowable Illegal Access Times and Lock Time(second).
Procedure
Step 1 In the NE Explorer, click an NE and select Security > NE Security Parameters from the
Function Tree.
Step 2 Click Query to query the settings of NE security parameters.
----End

2.6.4 Querying NE User Groups

NE users at different levels are divided to 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, click an NE and select 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
2.7 Managing NE Login

To ensure NE data security, you can manage the users logged in to NEs.
Context
On the T2000 you can perform the following NE login management.
2.7.1 Locking Out NE Login

An NE user can lock out the NE, to deny the login attempt from other users of the same or
lower level. If there is an NE user of the same or higher level logged in to the NE, the NE
user cannot lock out the NE. NE users of higher levels automatically unlock NE login locked
by lower-level users.
2.7.2 Locking Out NE Settings
An NE user can lock out the settings of an NE, preventing other NE users of the same or
higher level from setting the NE. If there is a user of the same or higher level logged in to the
NE, the NE user cannot lock out the NE. NE users of higher levels automatically unlock NE
settings locked by lower-level users.
2.7.3 Switching an NE User
During a new deployment, after the root NE user creates the NE topology, it can create another
NE user. After switching the NE user, you can log in to NEs with the new NE user.
2.7.4 Forcing NE Users to Log Out of the NE
When you want to log in to NEs with a higher level user, you can force lower-level NE users to
log out of the NEs. In this way, you can avoid an NE being congured by multiple NE users at
the same time, or prevent illegal logins by other NE users.
2.7.1 Locking Out NE Login

An NE user can lock out the NE, to deny the login attempt from other users of the same or
lower level. If there is an NE user of the same or higher level logged in to the NE, the NE
user cannot lock out the NE. NE users of higher levels automatically unlock NE login locked
by lower-level users.
Prerequisites
n The current NE user has the highest level among all login NE users.

Procedure
Step 1 Select System Administration > NE Security Management > NE Login Lock from the
Main Menu.
Step 2 In the left pane, select the appropriate NEs 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 select Lock Login.
----End
2.7.2 Locking Out NE Settings

An NE user can lock out the settings of an NE, preventing other NE users of the same or
higher level from setting the NE. If there is a user of the same or higher level logged in to the
NE, the NE user cannot lock out the NE. NE users of higher levels automatically unlock NE
settings locked by lower-level users.
Prerequisite
Procedure
Step 1 Select System Administration > 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 Permanent Locking check box for permanent locking of the current NE settings or
enter the value of Duration (10-10000) seconds for temporary locking. Click OK.
----End
2.7.3 Switching an NE User

During a new deployment, after the root NE user creates the NE topology, it can create another
NE user. After switching the NE user, you can log in to NEs with the new NE user.
Prerequisites
Context
One NE user cannot be used by multiple clients at the same time to log in to or manage an NE.
If a client logs in to the NE with the NE user already in use by another client, the previous
client will exit automatically.

Procedure
Step 1 Select System Administration > NE Security Management > NE Login Management
from the Main Menu.
Step 2 Select an NE from the NE list to switch its user. Click .

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 the NE user name and password.
Step 5 Click OK.
----End
2.7.4 Forcing NE Users to Log Out of the NE

When you want to log in to NEs with a higher level user, you can force lower-level NE users to
log out of the NEs. In this way, you can avoid an NE being congured by multiple NE users at
the same time, or prevent illegal logins by other NE users.
Prerequisites
n The NE user must be logged in to the NE.
Procedure
Step 1 Select System Administration > NE Security Management > NE Login Management
from the Main Menu.
Step 3 Select the NE entry. Click Logout or right-click it and select Logout. A prompt appears
telling you that the operation was successful.
Step 4 Click Close.
----End

Operator Guide 3 Backing Up and Restoring Network Data
3 Backing Up and Restoring Network Data
About This Chapter

To ensure network data security, the T2000 provides network data backup and restore functions.
3.1 T2000 Data Backup and Restoration Methods

T2000 provides three ways of maintaining data: Backing up and restoring T2000 MO data, all
data in the T2000 database, and network conguration data of the T2000 by script.
3.2 Keeping Data in the T2000 Consistent with NEs
Consistent data in both the T2000 and NEs is an important basis for NE management.
3.3 Backing Up the T2000 Data
T2000 data backup is essential for restoring the T2000 database safely and quickly.
3.4 Restoring the T2000 Data
If the T2000 database fails, you can restore it from a backup le.
3.5 Backing Up NE Conguration Data
In routine maintenance, you need to back up the NE database so that the NE can automatically
recover if the NE software loses data or a power failure occurs on the equipment.
3.6 Initializing the T2000 Database
After installing the T2000 or before restoring the T2000 database, you are recommended
to initialize the T2000 database.
3.7 Initializing NE Conguration Data in the T2000
To recongure all data (board, service, clock, protection) of multiple NEs, you need to
initialize the NE conguration data in the T2000, quickly clearing the conguration data of
the NEs from the T2000.
3.8 Conguration Upgrade Wizard
By using the upgrade wizard, You can restore the T2000 data from the existed conguration
data scripts

3 Backing Up and Restoring Network Data Operator Guide
3.1 T2000 Data Backup and Restoration Methods

T2000 provides three ways of maintaining data: Backing up and restoring T2000 MO data, all
data in the T2000 database, and network conguration data of the T2000 by script.
Table 3-1 Characteristics and application scenario of the three ways

Backup method Characteristics Application scenario
T2000 MO data backup Backs up all data in the The preferred option for
T2000 database as an MO backing up and restoring
le. The data is in the form data between the same
of txt and you can understand versions. The backup
the contents only when MO les correspond to
you want to know the data specic versions and are not
structure of the T2000. interchangeable.
Backs up all data.
The processing speed is slow
and the backup le is small.
T2000 database backup Backs up the structure Requires large storage
and contents of the T2000 medium space. If you want to
database. The data is in 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 le is big.
T2000 network layer data Exports the conguration This method is usually used
backup using script export data in the T2000 to a txt le for T2000 version upgrade.
that is similar to the MML This method is also used
format, to save data. You can to back up and restore the
understand the conguration basic conguration data for
contents. a single NE, or to restore the
Backs up only some data, user-dened data. A new
including basic conguration version is compatible with
data, port naming and old version scripts.
user-dened data.
The processing speed is slow
and the backup le is very
small.
3.2 Keeping Data in the T2000 Consistent with NEs

Consistent data in both the T2000 and NEs is an important basis for NE management.
3.2.1 Checking Conguration Data Consistency Between an NE and the T2000

Consistency check compares the conguration data in NEs and that in the T2000, and a
report of the consistency check result is created. If the result shows the conguration data is
inconsistent, you need to upload the conguration data from the NE to the T2000 or download
the data from the T2000 to the NE for data synchronization. This task does not change the
conguration data in NEs and in the T2000. To ensure that the T2000 manages NEs properly,
it is recommended to run this function periodically to keep the consistency of conguration
data in NEs and the T2000 server.
3.2.2 Viewing the Out of Synchronization Information
For the NEs that have different data than the data in the T2000, you can locate the reason of
out of synchronization by viewing the out of synchronization information.

3.2.3 Synchronizing the NE Conguration Data Manually

To maintain that the data in the T2000 is the same with the data in the NE, you can manually
synchronize the NE conguration data.
3.2.418.1.2 Uploading NE Conguration Data
The NE conguration data in the T2000 may differ from that in the NE. During maintenance,
you need to keep the data in the T2000 and that in the NE consistent. 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.
3.2.5 Downloading NE Conguration Data
you need to keep the data in the T2000 and that in the NE consistent. 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 data consistency check.
3.2.1 Checking Conguration Data Consistency Between an NE

and the T2000
Consistency check compares the conguration data in NEs and that in the T2000, and a
report of the consistency check result is created. If the result shows the conguration data is
inconsistent, you need to upload the conguration data from the NE to the T2000 or download
the data from the T2000 to the NE for data synchronization. This task does not change the
conguration data in NEs and in the T2000. To ensure that the T2000 manages NEs properly,
it is recommended to run this function periodically to keep the consistency of conguration
data in NEs and the T2000 server.
Prerequisite
You must be an NM user with "NE and network operator" authority or higher.
Procedure
Step 1 Select Conguration > Conguration Data Management from the Main Menu.
Step 2 Select an NE in the left pane and click the double-right-arrow button (red).
Step 3 Select one or more NEs from the Conguration Data Management List.
Step 4 Click Consistency Check. Alternatively, right-click the NE and select Consistency Check
Step 5 Click OK.
NOTE
If the result indicates an inconsistency in the conguration data between the NE and the T2000, you need
to upload or download the data to achieve consistency.
----End
3.2.2 Viewing the Out of Synchronization Information

For the NEs that have different data than the data in the T2000, you can locate the reason of
out of synchronization by viewing the out of synchronization information.
Prerequisites
n You must be an NM user with "NE and network operator" authority or higher.
n This operation applies to the OptiX BWS 1600G, OptiX BWS 1600G OLA, OptiX Metro
6100V1E and OptiX Metro 6040V2.

Procedure
Step 1 Choose Conguration > Conguration Data Management from the Main Menu.
The Conguration 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 Conguration Data Management List.
Step 3 Select an NE that is in the Unsynchronized state, and then click Sync Info.
Step 4 In the NE Cong Sync Info dialog box, click Query to view the details of conguration items.
----End
3.2.3 Synchronizing the NE Conguration Data Manually

To maintain that the data in the T2000 is the same with the data in the NE, you can manually
synchronize the NE conguration data.
Prerequisites
n This operation applies to the OptiX BWS 1600G, OptiX BWS 1600G OLA, OptiX Metro
6100V1E and OptiX Metro 6040V2.
Procedure
Step 1 Choose Conguration > Conguration Data Management from the Main Menu.
The Conguration 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 Conguration Data Management List.
Step 3 Select an NE that is in the Unsynchronized state, and then click Synchronize.
Step 4 The Conrm dialog box is displayed, indicating this operation overrides the data in the T2000.
Step 5 Click OK and the Synchronization dialog box is displayed, showing the progress of the
synchronization.
Step 6 A prompt appears telling you that the operation was successful.
----End
3.2.4 Uploading NE Conguration Data

you need to keep the data in the T2000 and that in the NE consistent. 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
You must be an NM user with "NE and network maintainer" authority or higher.
Procedure
Step 2 Select an NE from the Object Tree and click the double-right-arrow button (red).

Step 4 Click Upload. Alternatively, select Upload from the shortcut menu.
----End
3.2.5 Downloading NE Conguration Data

you need to keep the data in the T2000 and that in the NE consistent. 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 data consistency check.
Prerequisite
Procedure
Step 2 Select an NE from the Object Tree and click the double-right-arrow button (red).
Step 4 Click Download. Alternatively, select Download from the shortcut menu.
----End
3.3 Backing Up the T2000 Data

T2000 data backup is essential for restoring the T2000 database safely and quickly.
3.3.1 Backing Up the T2000 MO Data Immediately

In the event of a failure, you can restore data from a backup database le. But, this operation
is not applicable for T2000 upgrade. When you are upgrading the T2000, you can save the
system data through the script import and export function.
3.3.2 Backing Up the T2000 MO Data Periodically
You can set a schedule for database backup, to enable the T2000 to automatically back up the
T2000 database at a scheduled time, facilitating operation and maintenance.
3.3.3 Backing Up All Data in the T2000 Database
You can back up the T2000 database using the database management tool, to quickly restore
the database in the event of a failure.
3.3.4 Backing Up T2000 Network Layer Data Through Script Export
Before upgrading the T2000, you must export data from the database and save as script les.
3.3.1 Backing Up the T2000 MO Data Immediately

In the event of a failure, you can restore data from a backup database le. But, this operation
is not applicable for T2000 upgrade. When you are upgrading the T2000, you can save the
system data through the script import and export function.
Prerequisite
Log in to the T2000 as user admin.

Context
NOTE
The database le is backed up in the default directory. It is:
n /T2000/server/database/dbbackup in UNIX.
n C:\T2000\server\database\dbbackup in Windows.
Procedure
n Backing Up the T2000 MO Data at the Client
1. Select System Administration > Database Management > Backup] from the
Main Menu.
2. Under Backup Immediately, click Backup.
The T2000 backs up the database immediately and a progress bar is displayed.
n Backing Up the T2000 MO Data Using the Database Management Tool
1. Start Database Management Tool.
NOTE
n In UNIX, right-click on the CDE desktop and select Tools > Terminal to display a
terminal window. In the /T2000/server/database directory, run "T2000DM.sh".
n In Windows, open the Resource Browser. In the C:\T2000\server\database directory,
run "T2000DM.exe".
2. In the left-hand Database Server List, select T2000DBServer.

3. Enter the password of user sa.
4. Click Backup MO and the MO Backup Show dialog box is displayed.
5. Enter a description if desired. Click Backup to back up the T2000 MO data.
6. Click OK after the data are successfully backed up. Return to the database
management tool interface.
----End
3.3.2 Backing Up the T2000 MO Data Periodically

You can set a schedule for database backup, to enable the T2000 to automatically back up the
T2000 database at a scheduled time, facilitating operation and maintenance.
Prerequisite
Log in to the T2000 as user admin.
Context
NOTE
n When creating or modifying a scheduled task, if the running period is set to Running once, set the
time to execute the task at least ve minutes later than the current time (that is, the server time).
Procedure
Step 1 Select System Administration > Scheduled Task Management from the Main Menu.
Step 3 Select Database Backup in the Task Type eld and enter the task name. Click Next.
Step 4 Set the running period and click Next.
Step 6 Click Finish, and the system backs up the T2000 database according to the above settings.

----End
3.3.3 Backing Up All Data in the T2000 Database

You can back up the T2000 database using the database management tool, to quickly restore
the database in the event of a failure.
Prerequisites
n In UNIX, the current user must have the Sybase database write authority.
n In Windows, the current user must have the administrator authority of the operating
system. The MS SQL database server must also be started.
Procedure
Step 1 Start Database Management Tool.
n In 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
The password of user sa was set up during T2000 installation. Its default value is empty.
Step 4 Click Backup Database and a dialog box is displayed.

Step 5 Specify a directory to save the backup le.
Step 6 Click Backup to start to back up the T2000 database.
----End
3.3.4 Backing Up T2000 Network Layer Data Through Script Export

Before upgrading the T2000, you must export data from the database and save as script les.
Prerequisites
n The conguration data in the T2000 and that in the NE must be consistent.
Procedure
Step 1 Select System Administration > Import/Export Script File from the Main Menu.
Step 2 Select the script le type from the Script File Type eld.
NOTE
To export a script containing networkwide conguration data, select Conguration le for the whole
network. This operation exports the les "NWCfg_NM name.txt", "NWNeList_NM name.txt",
"NePort_NE ID_NE name.txt" and "NeData_NE ID_Ne name.txt" to the specied directory.
Step 3 Select the NE for which you want to export script les from the Export NE List.
NOTE
You need to specify an NE only when exporting the NE Conguration File and NE Port Naming File.

Step 4 Click Create File Directory to create a directory to save the script les exported.
Step 5 Enter the directory name and click OK.
NOTE
The script le is saved in the T2000\server\script directory on the T2000 server. You can create a new
directory under it.
Step 6 Select a directory and click Apply.

A progress bar appears showing the progress of exporting a script le.
----End
3.4 Restoring the T2000 Data

If the T2000 database fails, you can restore it from a backup le.
3.4.1 Restoring the T2000 MO Data

You can restore the T2000 MO data from the original T2000 database backup in UNIX or
Windows.
3.4.2 Restoring All Data in the T2000 Database
You can restore the T2000 database from a backup le using the database management tool.
3.4.3 Restoring T2000 Network Layer Data Through Script Export
After the T2000 is upgraded, you can restore the T2000 network layer conguration data
from the backup script les.
3.4.1 Restoring the T2000 MO Data

You can restore the T2000 MO data from the original T2000 database backup in UNIX or
Windows.
Prerequisites
n The T2000 MO data must be backed up.
n The T2000 server must be shut down.
n In Windows, the current user must have the NM administrator authority.
n Initializing the T2000 database.
n Start the EMS process of the T2000. Stop the process after the process starts.
Context
CAUTION
The T2000 where the MO is backed up from and the T2000 where the MO will be restored to
must be of the same version.
NOTE
The database le is backed up to the default directory. It is:
n /T2000/server/database/dbbackup in UNIX.
n If the T2000 server was installed in disk C, C:\T2000\server\database\dbbackup in Windows.
Procedure

n In Windows, open the Windows Explorer. In the \T2000\server\database directory,
run "T2000DM.exe".
NOTE
Step 4 Click Restore MO. The Select Backup MO dialog box is displayed.
Step 5 Specify the directory where the MO data for restoration are stored. Click Restore to restore
the T2000 MO data. Click OK in the prompt dialog box to return to the database management
tool interface.
----End
3.4.2 Restoring All Data in the T2000 Database

You can restore the T2000 database from a backup le using the database management tool.
Prerequisites
n The T20000 database must be backed up.
n In Windows, the current user must have the "NM administrator" authority.
Context
CAUTION
The T2000 where the MO is backed up from and the T2000 where the MO will be restored to
must be of the same version.
Procedure
n In Windows 2000, open the Windows Explorer. In the \T2000\server\database directory,
run "T2000DM.exe".
NOTE
Step 4 Click Restore Database. Specify a directory for the backup le.
Step 5 Click Restore to start to restore the T2000 database.
----End

3.4.3 Restoring T2000 Network Layer Data Through Script Export

After the T2000 is upgraded, you can restore the T2000 network layer conguration data
from the backup script les.
Prerequisites
n The License for T2000 script import is provided.
Context
CAUTION
Before importing the script le, you need to back up the T2000 database or the T2000 MO
data. Then, initialize the T2000 database. Import the networkwide conguration script le.
You can restore the data from a backup le if failed to import the script le.
Procedure
Step 1 Select System Administration > Import/Export Script File from the Main Menu.
Step 2 Click the Import radio button.
Step 3 Select the script le type from the Script File Type eld.
NOTE
Network Modeling and Design Information File is not supported.
Step 4 In the Operation Directory List, select the directory where the script le to import is located.
Step 5 Select the script le to import from the Import File List.
Step 6 Click Apply.
NOTE
The system prompts you twice that import of the conguration script will result in data inconsistency
between the T2000 and the NE.
Step 7 Click OK. A progress bar appears showing the progress of importing a script le.
NOTE
The script le is saved in the T2000\server\script directory on the T2000 server. You can create a new
directory under it.
----End
3.5 Backing Up NE Conguration Data

In routine maintenance, you need to back up the NE database so that the NE can automatically
recover if the NE software loses data or a power failure occurs on the equipment.
Prerequisites
n Log in to the NE as user admin.

Procedure
Step 3 Select one or more NEs in the Conguration Data Management List.
Step 4 Click Back Up NE Database. Alternatively you can also right-click and select Back Up NE
Database from the shortcut menu.
Step 5 Click OK.
----End
3.6 Initializing the T2000 Database

After installing the T2000 or before restoring the T2000 database, you are recommended
to initialize the T2000 database.
Prerequisites
n The T2000 client and server applications must be closed.
n In UNIX, the current user must have the Sybase database write authority and the
T2000DBServer must be started.
n In 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. You need to back up the T2000 database
before this operation.
Procedure
NOTE
n In UNIX, right-click on the CDE desktop and select Tools > Terminal to display a terminal window.
In the /T2000/server/database directory, run "T2000DM.sh".
n In Windows, open the Resource Browser. In the \T2000\server\database directory, run
"T2000DM.exe".

NOTE
The password of user sa was set up when the T2000 was installed. Its default value is empty.
Step 4 Click Database Maintenance.

Step 5 Click Initialize Database. The Conrm dialog box is displayed.
Step 6 Click OK to start to initialize T2000 database.
----End

3.7 Initializing NE Conguration Data in the T2000

To recongure all data (board, service, clock, protection) of multiple NEs, you need to
initialize the NE conguration data in the T2000, quickly clearing the conguration data of
the NEs from the T2000.
Prerequisites
n For initializing the conguration data in the T2000 database, you must be an NM user
with "NE and network operator" authority or higher.
n For initializing the conguration data in NE, the NE user logged in to the T2000 must
have the "system level" authority.
Context
CAUTION
After initializing the conguration data of an NE in the T2000, if you download the data in the
T2000 to the NE, the NE loses all data and services on 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 Select NEs from the left-hand Object Tree and click the double-right-arrow button (red).
Step 3 Select one or more NEs from the NE data list.
Step 4 Click Initialize NM Side Data. Alternatively, right-click the NE and select Initializing NM
Side Data from the shortcut menu.
Step 5 Click OK.
A progress bar is displayed.
Step 6 A prompt appears telling you that the operation was successful. Click Close.
The initialized NE is shown in the Uncongured state.
----End
3.8 Conguration Upgrade Wizard

By using the upgrade wizard, You can restore the T2000 data from the existed conguration
data scripts
Prerequisite
Only the user admin can perform this operation on the T2000 client in the single-user mode.
Context
NOTE
As conguration data is uploaded from the NE, ensure association between the T2000 and the NE
is normal.

Procedure
Step 1 Select System Administration > Conguration Upgrade Wizard from the Main Menu.
Open the Upgrade Wizard 1 of 8: Import NE list ledialog box.
Step 2 Optional: Select a directory containing the NE list le and click Import to perform the
operation of importing the NE list le.
Step 3 Click Next to go to Upgrade Wizard 2 of 8: Upload NE data.
Step 4 Optional: Click to upload the conguration data of the selected NE in the Upload below.
Step 5 Click Next to go to Upgrade Wizard 3 of 8: Search ASON trail.
Step 6 Optional: Click Search to search for ASON trails from the network layer in the T2000.
Step 7 Click Next to go to Upgrade Wizard 4 of 8: Import networkwide conguration le.
Step 8 Optional: Select a directory containing the networkwide conguration le and click Import
to perform the operation of importing the networkwide conguration le.
Step 9 Click Next to go to Upgrade Wizard 5 of 8: Search Ethernet trail.
Step 10 Optional: Click Search to search for Ethernet trails from the network layer in the T2000.
Step 11 Click Next to go to Upgrade Wizard 6 of 8: Search WDM trail.
Step 12 Optional: Click Search to search for WDM trails from the network layer in the T2000.
Step 13 Click Next to go to Upgrade Wizard 7 of 8: Import customer data.
Step 14 Optional: Click Import to import customer data.
Step 15 Click Next to go to Upgrade Wizard 8 of 8: View upgrade report.
Step 16 View the operation result of upgrade and make sure the upgrade is successful.
Step 17 Click Finish to exit the wizard.
----End

Operator Guide 4 Creating Topologies
4 Creating Topologies
About This Chapter

NEs and bers/cables can be managed on the T2000 only after their topologies are created.
4.1 Topology on the T2000

The topology on the T2000 refers to an operation object corresponding to the physical
equipment. If you want to manage an NE, board or ber/cable on the T2000, you must create
its topology rst.
4.2 Creating Multiple NEs
When the T2000 communicates with the GNE properly, you can create NEs in batch by
searching for all NEs that communicate with the GNE, through the IP address of the GNE
or the network segment the IP address is associated to or the NSAP address of the NE. This
method is quicker and more accurate than manual creation.
4.318.1.1 Creating a Single GNE
The T2000 can communicate with non-gateway NEs only through the GNE. Therefore, you
need to create the GNE before managing the NEs. By using this method you can only create
GNEs one by one. Even if the GNE does not exist physically or the communication between
the T2000 and the GNE is interrupted, you can still create the GNE.
4.4 Creating a Non-Gateway NE
Non-gateway NEs communicate with the T2000 through the GNE. Therefore, you should
create non-gateway NEs only after creating the GNE. By using this method you can only create
non-gateway NEs one by one. Even if the NE does not exist physically or the communication
between the T2000 and the NE is interrupted, you can still create the NE. You can manage an
NE only when you create it on the T2000.
4.5 Deleting an NE
When you need to adjust the network topology or 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.
4.6 Modifying the NE Name
You can modify the NE name as needed, which does not affect the running of the NE.
4.7 Downloading Precongured NE Data
To effectuate data of a precongured NE, you need to download the data from the T2000 to the
NE. After preconguring the NE, download the data to the NE in time.
4.8 Creating Boards in Conguration Wizard
To congure services for an NE and manage the NE, you need to create boards rst. For
the NE that is not congured on the T2000, you can create a subrack and boards in the
conguration wizard.
4.9 Adjusting Boards in NE Panel
To modify board conguration for an NE or add a board, you can congure the boards in
the NE Panel.
4.10 Deleting Boards
To modify board conguration for an NE, you can delete boards from the NE Panel.

4 Creating Topologies Operator Guide
4.11 Modifying the NM Name

You can modify the NM name as needed, which does not affect the running of the T2000.
4.12 Creating Fibers Automatically
Through the ber search feature, you can check whether the specied optical interface is
connected with a ber. Therefore, you can create a ber for this optical interface on the T2000
quickly. For a newly created network, after conguring boards on the T2000, you can search
for all optical interfaces to create bers for the entire network. In this way, you can monitor
the actual working status of bers.
4.13 Creating Fibers Manually
NEs communicate with each other through bers. After creating boards for each NE, you need
to create bers for further service conguration. Manual ber creation applies to the situation
where there is only a few bers you need to create.
4.14 Deleting Fibers
During the adjustment of the network, if you need to delete the NEs or change the links
between NEs, you need to delete the ber connections between and within the NEs.
4.15 Modifying Fiber Information
When creating a ber, you need to enter the information such as ber name, length, ber type,
attenuation and so on. If the ber is adjusted, you need to update the information so that
maintenance personnel are able to know the actual ber information.
4.16 Creating Cables between the T2000 and NEs
The T2000 can communicate with NEs through the Ethernet port or serial port. NEs can also
communicate with each other through the extended ECC. Depending on the communication
mode, different types of cables are to be created on the T2000 so that the maintainer personnel
are able to know the current communication mode.
4.17 Creating a Topology Subnet
The subnet created here is of a topological concept only, for the convenience of management.
For topology objects in the same network area or with similar attribute, you can put them in
one topology subnet.

4.1 Topology on the T2000

The topology on the T2000 refers to an operation object corresponding to the physical
equipment. If you want to manage an NE, board or ber/cable on the T2000, you must create
its topology rst.
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 physical equipment does. After that, the NE and board conguration on the
T2000 will be sent to physical NEs directly.
The T2000 is able to manage the following topologies: NE, board, port, channel, ber, subnet,
Ethernet cable and serial port cable. Through all these topologies, the T2000 is able to query
the data or working status of corresponding objects in the physical network. The subnet,
Ethernet cable and serial port cable are only logic concepts on the T2000, and cannot be
managed physically through their topologies.
4.2 Creating Multiple NEs

When the T2000 communicates with the GNE properly, you can create NEs in batch by
searching for all NEs that communicate with the GNE, through the IP address of the GNE
or the network segment the IP address is associated to or the NSAP address of the NE. This
method is quicker and more accurate than manual creation.
Prerequisites
n The T2000 communicates with the GNE properly.
Procedure
Step 1 Select File > Search for NE from the Main Menu.
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 the information of the search address. Click OK.

NOTE
You can repeat Steps 2 through 3 to add multiple search elds. You can delete the system default search
eld.
n If you use IP address to search for NEs, and the IP address of the T2000 computer and that of the
GNE are within the same network segment, you can select IP Address Range of GNE or IP
Address of GNE.
n If the IP addresses are not within the same network segment, you can only select IP Address of GNE.
n If you use NSAP address, you can only select NSAP address.
Step 4 Click Start. The NEs found are displayed after the search.
Step 5 When the search ends or if you click Stop, select the uncreated NEs in the NE Found list and
click Create. The Create dialog box is displayed.
Step 6 Enter the NE user name and password. You can select the All NEs use the same User and
Password option, when you create multiple NEs.
Step 7 Click OK.The NE is created in the Main Topology.
----End
4.3 Creating a Single GNE

Prerequisite
Procedure
Step 1 Right-click in the blank space of the Main Topology and select Create > Topology Object
from the shortcut menu. The Create Topology 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 Select Gateway from the Gateway Type drop-down list.

Step 5 Select the protocol type.
If the T2000 communicates with NEs Do...

through
IP protocol Select IP from the Protocol drop-down list.
Enter the IP address and use the default
value for the port number of the GNE.
OSI protocol Select OSI from the Protocol drop-down
list. Enter the NSAP address of the GNE.
NOTE
The NSAP address is a hexadecimal number containing up to 20 bytes. Its format is: domain
address+08003e+NE ID+NSEL.
"domain address" comprising up to 13 bytes is entered by the user. "NSEL" is the port number of the
network-level protocol, with a xed value of 1d (one byte).

Step 6 Enter the NE user and password.
NOTE
n Default NE user: root; default password: password. The NE user must have the authority level of a
system operator or higher.
n If the NE does not exist physically and is only precongured on the T2000, you can check the NE
Preconguration check box. Modifying the precongured NE does not affect the network.
Step 7 Click OK.

Step 8 Click on the Main Topology to appoint the location of the NE in the Main Topology. If the NE
is incorrect or the T2000 communicates with the NE improperly, the NE is shown gray.
----End
4.4 Creating a Non-Gateway NE

Non-gateway NEs communicate with the T2000 through the GNE. Therefore, you should
create non-gateway NEs only after creating the GNE. By using this method you can only create
non-gateway NEs one by one. Even if the NE does not exist physically or the communication
between the T2000 and the NE is interrupted, you can still create the NE. You can manage an
NE only when you create it on the T2000.
Prerequisites
n The GNE must be created.
Procedure
Step 4 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE the NE is
afliated to from the Afliated Gateway drop-down list.
Step 5 Enter the NE User and Password.

NOTE
Step 6 Click OK.

----End
4.5 Deleting an NE
When you need to adjust the network topology or 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.
Prerequisites
n Fibers and cables connected to the NE must be deleted.
Context
NOTE
The T2000 supports deleting NEs one by one. You can delete all NEs by initializing the T2000 database,
and thus all data is removed from the T2000. Therefore, you need to back up the T2000 database before
initializing the database.
Procedure
Step 1 Right-click the NE icon on the Main Topology and select Delete from the shortcut menu. The
Delete NE dialog box is displayed.
Step 2 Click OK. The NE icon is deleted from the Main Topology.
----End
4.6 Modifying the NE Name

You can modify the NE name as needed, which does not affect the running of the NE.
Prerequisite
Procedure
Step 1 Right-click an NE icon on the Main Topology, and choose Attribute from the shortcut menu.
Step 2 In the NE Attribute dialog box, enter a new NE name. Click OK. A prompt appears telling you
that the operation was successful.
NOTE
The NE name can contain alphanumeric characters and symbols, but cannot contain the following special
characters: | \ / : * ? " < >.

Step 3 Click Close.

----End
4.7 Downloading Precongured NE Data

To effectuate data of a precongured NE, you need to download the data from the T2000 to the
NE. After preconguring the NE, download the data to the NE in time.
Prerequisites
n The precongured NE must be created.
Context
CAUTION
Downloading data of a precongured NE sends the NE settings on the T2000 to the physical
NE. If the data is incorrect, this may cause service interruption.
Procedure
Step 1 Right-click an NE icon on the Main Topology and select Attribute from the shortcut menu.
The NE Attribute dialog box is displayed.
Step 2 Uncheck the Yes check box in the NE Preconguration eld and click OK.
A prompt appears telling you that the operation was successful.
Step 3 Click Close.
A dialog box appears asking for conrmation on downloading the NE data.
Step 4 Click Yes.
A dialog box appears prompting this is a potentially service affecting operation.
Step 5 Click OK.
A progress bar displays showing the progress of downloading.
Step 6 Click Close.
----End
4.8 Creating Boards in Conguration Wizard

To congure services for an NE and manage the NE, you need to create boards rst. For
the NE that is not congured on the T2000, you can create a subrack and boards in the
conguration wizard.
Prerequisites
n The NE is not congured.
Procedure
Step 1 Double-click an NE icon on the Main Topology.
The NE Conguration Wizard is displayed.
Step 2 Select Manual Conguration and click Next.

Step 3 Click OK in the Conrm dialog box.

Step 4 Click OK in the Conrm dialog box again.
Step 5 Set the NE attributes and click Next.
The NE Panel is displayed.
Step 6 Right-click the slot where the board you wish to add resides and select the board type. Or click
Query Physical Slot(s) to query the data about the board slots at the NE side.
NOTE
Click Query Logical Slot(s) to query the logical slot number of the board from the NE side.
Step 7 After all the boards have been created, click Next.
Step 8 Click Finish.
----End
4.9 Adjusting Boards in NE Panel

To modify board conguration for an NE or add a board, you can congure the boards in
the NE Panel.
Prerequisites
n The NE must be congured.
n Make sure ber connections are deleted and the board is in the idle state before deleting
a board.
Context
NOTE
The indicator on top of every board icon indicates the status of the board. By default, the meaning of
alarm indicators is as follows:
Indicator shows Description
Green The board is normal.
Red The board detects at least a Critical alarm.
Orange The board detects at least a Major alarm.
Yellow The board detects at least a Minor alarm.
Dark Magenta The board detects at least a Warning alarm.
Procedure
Step 1 Double-click an NE on the Main Topology and
the NE Panel is displayed.
Step 2 In the left-hand pane, click the NE for which you want to adjust board.
Step 3 Right-click the slot where the board you want to delete resides, and choose Delete. Click OK
in the Delete Board dialog box.
Step 4 Click OK.
Step 5 Right-click the slot where the board you want to add resides, and choose Add XXX.
NOTE
"XXX" means the name of the board you want to add.

----End
4.10 Deleting Boards

To modify board conguration for an NE, you can delete boards from the NE Panel.
Prerequisites
n You must be an NM user with "NE and network maintainer" authority or higher.
n Make sure ber connections must be deleted and the board must be in the idle state
before deleting a board.
Procedure
Step 1 Double-click an NE on the Main Topology and the NE Panel is displayed.
Step 2 Right-click the board you want to delete, and choose Delete from the shortcut menu. The
Delete Board dialog box is displayed.
Step 3 Click OK.
----End
4.11 Modifying the NM Name

You can modify the NM name as needed, which 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
4.12 Creating Fibers Automatically

Through the ber search feature, you can check whether the specied optical interface is
connected with a ber. Therefore, you can create a ber for this optical interface on the T2000
quickly. For a newly created network, after conguring boards on the T2000, you can search

for all optical interfaces to create bers for the entire network. In this way, you can monitor
the actual working status of bers.
Prerequisites
n The optical interfaces of every NE must be connected with bers.
n The boards of every NE must be created on the T2000.
Context
n If conicting bers are found during the creation, delete the conicting bers on the
T2000 before starting to create bers.
n When a ber between two SDH NEs passes through a WDM NE, if the normal ber
between an SDH NE and a WDM NE has been created on the T2000, the ber found by
the trail search function is created as a virtual ber. If the WDM NE is not created on the
T2000, the ber is created as a normal ber.
Procedure
Step 1 Select 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
bers or cables. A progress bar is displayed, showing progress of searching.
NOTE
n If Do not search ports with ber/cable created on NM is checked, the system only searches
for ports without ber created on the T2000.
n To check if the created ber is consistent with the actual ber connection, leave the check box
unchecked.
n If checked and all selected ports have bers created, the system prompts that the search eld is null.
Step 4 To create bers, select one or more bers from the Current ber/cable link list and click
Create Fiber.
NOTE
n When one or more bers are selected in the Current ber/cable link list, bers that conict with the
selected bers are shown in the Existing Logical ber link list. If there is any conicting ber, go
to Step 5 and delete it before creating bers.
n During ber creation, if all the selected bers are in an Already created state, the system prompts
with the message No fiber to create.
Step 5 To delete the conicting bers, select from the Existing Logical ber link list one or more
bers, which are valued Yes for the Conict with logical link (Y/N) parameter in the
Unresolved ber/cable link list. Click Delete Fiber/Cable.
----End
4.13 Creating Fibers Manually

NEs communicate with each other through bers. After creating boards for each NE, you need
to create bers for further service conguration. Manual ber creation applies to the situation
where there is only a few bers you need to create.
Prerequisites
n The boards to be connected with bers or cables must be created.

Context
NOTE
It is recommended to perform SDH trail search again, after conguring ber connection for the SDH NNI
with VC4 trail created. This VC4 trail is searched and shown as an extended VC4 server trail.
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 ber or cable on the Main Topology.
Step 3 Select the source board and port in the Select ber/Cable Source dialog box.
Step 4 Click OK and the cursor changes to a + sign.
Step 5 Click the sink NE of the ber or cable on the Main Topology.
Step 6 Select the sink board and port in the Select ber/Cable Sink dialog box.
NOTE
When selecting the wrong source or sink NE, right-click and click Yes in the Object dialog box to exit.
Step 7 Click OK. Enter the information of the ber or cable in the Create ber dialog box.
Step 8 Click OK. The created ber or cable appears between the source and sink NEs on the Main
Topology.
----End
4.14 Deleting Fibers

During the adjustment of the network, if you need to delete the NEs or change the links
between NEs, you need to delete the ber connections between and within the NEs.

Prerequisites
n The ber to be deleted must not be used for any protection subnet.
n There are no server trails on the ber to delete.
Context
If you want to delete a ber that is used for a protection subnet, server trails or other trails, you
need to delete the protection subnet and trails rst.
Procedure
Step 1 Select File > Fiber/Cable Management from the Main Menu.
Step 2 Select the ber you wish to delete, and right-click and select Delete Fiber/Cable from the
shortcut menu.
----End
4.15 Modifying Fiber Information

When creating a ber, you need to enter the information such as ber name, length, ber type,
attenuation and so on. If the ber is adjusted, you need to update the information so that
maintenance personnel are able to know the actual ber information.
Prerequisites
n The ber must be created.
Procedure
Step 1 Right-click the ber you wish to modify and select Attribute from the shortcut menu.
The Link Attributes dialog box is displayed.
Step 2 Enter ber information such as ber name, length, ber type, attenuation and so on, and
click OK.
----End
4.16 Creating Cables between the T2000 and NEs

The T2000 can communicate with NEs through the Ethernet port or serial port. NEs can also
communicate with each other through the extended ECC. Depending on the communication
mode, different types of cables are to be created on the T2000 so that the maintainer personnel
are able to know the current communication mode.
Prerequisite
Procedure

Step 2 Select Link > Transmission Link from the Object Type tree. Then 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
4.17 Creating a Topology Subnet

The subnet created here is of a topological concept only, for the convenience of management.
For topology objects in the same network area or with similar attribute, you can put them in
one topology subnet.
Prerequisite
Context
NOTE
A topology subnet is created only to simplify the user interface and has no impact on the NEs.
Procedure
Step 1 Right-click on the Main Topology and select Create > Subnet.
Step 2 Click the Attributes tab in the Create Subnet dialog box. Enter the attributes of the subnet.
Step 3 Click the Objects tab. Select the created NEs or subnet from the Available Objects pane.
Click .
Step 4 Click OK. Click in the Main Topology to display the icon.
----End

Operator Guide 5 Conguring Clocks
5 Conguring Clocks
About This Chapter

A clock is the basis for the normal running of NEs. You must congure clocks for all NEs
prior to conguring services. In addition, you need to congure clock protection for complex
networks.
Prerequisite
NEs and boards must be created.
Context
Follow the process given below to congure NE clocks:
5.1 Setting the NE Clock Source

Before conguring services, you must congure the NE clock source and specify the priority
level, to ensure that it is the same clock source traceable by all NEs in the network.
5.2 Setting Clock Source Protection
In complex clock networks, synchronization status message (SSM) or extended SSM protocol
prevents the incorrect traceable clock source. After setting a clock source for an NE and
specify the clock priority level, you need to enable the SSM or extended SSM protocol
to provide protection for clocks.
5.3 Setting Switching Conditions for Clock Sources
If the traceable clock source of an NE is line clock, you can customise switching conditions for
the clock source, so that the NE switch to other clocks when the clock source fails and thus
services are not affected.
5.4 Setting Clock Source Reversion
When there are multiple clock sources for an NE, set the clock sources to automatic
reversion mode, so that the deteriorated clock source becomes the traceable timing reference
automatically after it recovers.
5.5 Preventing Clock Signal Degrade
When clock signals are transmitted over 14 or more NEs, frequency offset and drift may occur.
To prevent clock signal degrade, you need to set 2 Mbit/s phase-locked source to optimize
the clock signals. For OSN equipment, you can also set 2M Phase-Locked Source External
Clock Attributes.
5.6 Setting Clock Source Quality
There may be some unknown clock sources in a complex clock network. You can uniformly
dene these clock sources as unavailable clocks so that NEs will not trace wrong clock
sources. For clock sources that are allocated to an NE, the NE obtains their quality information
automatically. The quality level of clock sources need to be dened only during test and
maintenance.

5 Conguring Clocks Operator Guide
5.7 Setting SSM Output

If the synchronization status message (SSM) or extended SSM protocol is enabled, clock
signals carry SSM messages automatically. You can inhibit clock sources from sending SSM
messages to other clock subnets, to avoid the equipment of different clock subnets affecting
one another at the edge of clock networks.
5.8 Switching a Clock Source
When the traceable clock source in a network deteriorates, NEs may not execute a switch on
the clock source. You need to switch the clock source manually to prevent clock deterioration
from affecting the normal running of NEs.

5.1 Setting the NE Clock Source

Before conguring services, you must congure the NE clock source and specify the priority
level, to ensure that it is the same clock source traceable by all NEs in the network.
Prerequisite
Context
NOTE
To implement clock protection, congure at least two traceable clock sources for the equipment. Usually,
tributary clock is not used as the clock source for the equipment.
Procedure
Step 1 Select Conguration > Clock View from the Main Menu.
Step 2 In the Clock View, right-click an NE icon and select Clock Source Priority list.
Step 3 Click Query to query parameter settings.

Step 4 Click Create to display the Add Clock Source dialog box.
Step 5 Select a clock source and click OK. Select more than one clock source by holding the Ctrl key.
Step 6 Optional: If an external clock source is selected, select External Clock Source Mode
according to the type of external clock signals. For 2 Mbit/s clocks, specify the bytes to
deliver SSM message.
Step 7 Select a clock source, and click or to adjust its priority level. Clock
sources are arranged in a descending order. The upmost one is the preferred one for the NE.
NOTE
Internal clock sources have the lowest priority because of its low precision.
Step 8 Click Apply.

Step 9 Click Close.
----End
5.2 Setting Clock Source Protection

In complex clock networks, synchronization status message (SSM) or extended SSM protocol
prevents the incorrect traceable clock source. After setting a clock source for an NE and
specify the clock priority level, you need to enable the SSM or extended SSM protocol
to provide protection for clocks.

Prerequisite
Procedure
Step 2 In the Clock View, right-click an NE icon and select Clock Subnet Settings.
Step 3 Click the Clock Subnet tab. Click Query to query the parameter settings.
Step 4 Select Start Standard SSM Protocol or Start Extended SSM Protocol.
Step 5 Set the subnet number of the clock subnet to which the NE is associated. Assign the same
subnet number to the NEs that have the same traceable clock source.
NOTE
n Assign subnet number to the NEs with SSM protocol protection. Otherwise, the SSM protocol is not
started and incorrect clock source switching is caused.
n When dividing clock subnets, divide the NEs that have the same traceable clock source to the same
subnet. The clock source is referred to as subnet clock source. The division of clock subnets
complies to the principle of "The clock traceable chain cannot be too long" (not more than 20 NEs),
to avoid clock precision degrade.
Step 6 Optional: If the extended SSM protocol is started, set the clock ID of the clock source.
Step 7 Click Apply.
Step 8 Click Close.
Step 9 Optional: If the clock ID is specied for an NE’s line clock, click the Clock ID Status tab,
and set the status to Enabled. Click Apply.
----End
5.3 Setting Switching Conditions for Clock Sources

If the traceable clock source of an NE is line clock, you can customise switching conditions for
the clock source, so that the NE switch to other clocks when the clock source fails and thus
services are not affected.
Prerequisite

Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > Clock > Clock Source Switching
from the Function Tree. Select the Clock Source Switching Condition tab.
Step 2 Click Query to query the parameter settings.
Step 3 Double-click the parameters to set clock switching conditions.
Step 4 Click Apply.

Step 5 Click Close.
----End
5.4 Setting Clock Source Reversion

When there are multiple clock sources for an NE, set the clock sources to automatic
reversion mode, so that the deteriorated clock source becomes the traceable timing reference
automatically after it recovers.
Prerequisite
Procedure
Step 2 In the Clock View, right-click an NE icon and select Clock Source Reversion Parameter.
Step 3 Double-click and set the reversion mode and the WTR time.
NOTE
It is recommended not to set Clock Source WTR Time(min.) to 0, to avoid repeated switching when
the clock is unstable.
Step 4 Click Apply.

Step 5 Click Close.

----End
5.5 Preventing Clock Signal Degrade

When clock signals are transmitted over 14 or more NEs, frequency offset and drift may occur.
To prevent clock signal degrade, you need to set 2 Mbit/s phase-locked source to optimize
the clock signals. For OSN equipment, you can also set 2M Phase-Locked Source External
Clock Attributes.
Prerequisite
Procedure
Step 2 In the Clock View, right-click an NE icon and select Phase-Locked Source Output by
External Clock.
Step 3 Click Query to query parameter settings.
Step 4 Set parameters to the appropriate value.
Step 5 Click Apply.
Step 6 Click Close.
----End
5.6 Setting Clock Source Quality

There may be some unknown clock sources in a complex clock network. You can uniformly
dene these clock sources as unavailable clocks so that NEs will not trace wrong clock
sources. For clock sources that are allocated to an NE, the NE obtains their quality information
automatically. The quality level of clock sources need to be dened only during test and
maintenance.
Prerequisite
Procedure
Step 2 Right-click the NE icon in the Clock View. Select Clock Subnet Setting. Select the Clock
Quality tab.
Step 4 Select the Conguration Quality tab and set Conguration Quality to Automatic
Extraction.

Step 5 Click Apply.

The Operation Result dialog box is displayed and indicates that operation succeeded.
Step 6 Click Close.
Step 7 Select the Manual Setting of 0 Quality Level tab. Set Manual Setting of 0 Quality Level to
Synchronous Source Unavailable.
Step 8 Click Apply.
----End
5.7 Setting SSM Output

If the synchronization status message (SSM) or extended SSM protocol is enabled, clock
signals carry SSM messages automatically. You can inhibit clock sources from sending SSM
messages to other clock subnets, to avoid the equipment of different clock subnets affecting
one another at the edge of clock networks.
Prerequisite
Procedure
Step 2 Right-click the NE icon in the Clock View. Select Clock Subnet Settings. Select the SSM
Output Control tab.
Step 3 Set the control status of the clock source.

Step 4 Click Apply

Step 5 Click Close.
Step 6 Click Query to query the parameter value.
----End
5.8 Switching a Clock Source

When the traceable clock source in a network deteriorates, NEs may not execute a switch on
the clock source. You need to switch the clock source manually to prevent clock deterioration
from affecting the normal running of NEs.
Prerequisite
Procedure
Step 2 In the Clock View, right-click an NE icon and select Clock Source Switching.
Step 3 Select the Clock Source Switching tab.
Step 4 Click Query to query the switching status of a clock source.
Step 5 Optional: If Lock Status is Lock, right-click and select Unlock.
Step 6 Right-click the clock source that you wish to switch and select a switching operation.

NOTE
Before switching the clock source, make sure the new clock source is created in the priority table, of
good quality and not locked.
Step 7 To restore to the automatic clock source selection mode, right-click the switched clock source
and select Clear Switching.
----End

Operator Guide 6 Conguring Orderwire
6 Conguring Orderwire
About This Chapter

You can congure orderwire for NEs on the T2000.
6.1 Conguring Local Orderwire

To provide a dedicated express orderwire channel for maintenance personnel, you can congure
orderwire for NEs. After creating NEs and boards, you can congure orderwire for NEs.
6.2 Conguring Conference Calls
To provide maintenance personnel with a dedicated express channel to allow for concurrent
voice communication among multiple NEs, you can congure conference calls for NEs. After
creating NEs and boards, you can congure the calls.
6.3 Conguring Express Orderwire
For two NEs without ber connection, you can congure express orderwire to provide
maintenance personnel with express orderwire channel between NEs. After creating NEs and
boards on the T2000, you can congure express orderwire for the NEs.
6.4 Dividing Orderwire Subnets
When there are too many NEs, concurrent conference calls affect conversation quality. You
can assign subnet number to optical ports where conference calls are congured, to divide NEs
to different orderwire subnets. You can make conference calls between NEs associated to
the same orderwire subnet.

6 Conguring Orderwire Operator Guide
6.1 Conguring Local Orderwire

To provide a dedicated express orderwire channel for maintenance personnel, you can congure
orderwire for NEs. After creating NEs and boards, you can congure orderwire for NEs.
Prerequisites
n Boards must be created.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > Orderwire from the Function
Tree. Click the General tab.
Step 2 Click Query to query information from the NE.

Step 3 Set Call Waiting Time(s), Telephone No. and orderwire ports.
NOTE
n Call Waiting Time should be set to the same value for all NEs with orderwire communication. When
the number of NEs is smaller than 30, set the value to 5s. Otherwise, set it to 9s.
n There are two dialing modes: Pulse and Dual-Tone Frequency, with Dual-Tone Frequency
as default.
n Orderwire phone numbers are of the same length and a duplicate number is not allowed in the same
subnet.
Step 4 Click Apply.

Step 5 Click Close.
----End

6.2 Conguring Conference Calls

To provide maintenance personnel with a dedicated express channel to allow for concurrent
voice communication among multiple NEs, you can congure conference calls for NEs. After
creating NEs and boards, you can congure the calls.
Prerequisite
Procedure
Tree. Click the Conference Call tab.
Step 2 Click Query to query conference call conguration of the NE.

Step 3 Set Conference Call Authorities to Able to Listen and Speak or Able to Listen but not
Speak.
Step 4 In the Available Conference Call Port pane, select the port where you wish to congure
a conference call, and click .
NOTE
Conference calls cannot be congured as a closed loop to avoid howls.
Step 5 Click Apply.

Step 6 Click Close.
Step 7 Select the General tab, and set Conference Call number to 9999
NOTE
Orderwire phone numbers for all NEs must be the same. It is recommended to set this value to 9999.
Step 8 Click Apply.

----End

Examples
You can follow the sample conguration to avoid conference call loop.
As shown in the gure, if congure conference calls for all optical ports, howls are caused.
Congure a conference call for NE3-7-SL16-1 only, rather than NE3-12-SL16-1. If conference
calls do not form a closed loop, howls are not generated.
6.3 Conguring Express Orderwire

For two NEs without ber connection, you can congure express orderwire to provide
maintenance personnel with express orderwire channel between NEs. After creating NEs and
boards on the T2000, you can congure express orderwire for the NEs.
Prerequisites
n SCC board must be created.
Procedure
Tree. Click the Auxiliary tab.


Step 3 Set Subnet No. Length and SDH NNI Connection.
NOTE
n Set the length of a subnet number according to the size of the network.
n Select a communication port and a phone port. Use a serial port line to connect the communication
ports and a telephone line to connect the phone ports between two NEs.
Step 4 Click Apply.

Step 5 Click Close.
Step 6 Repeat Step 1 through Step 5 to congure the orderwire on other stations.
----End
6.4 Dividing Orderwire Subnets

When there are too many NEs, concurrent conference calls affect conversation quality. You
can assign subnet number to optical ports where conference calls are congured, to divide NEs
to different orderwire subnets. You can make conference calls between NEs associated to
the same orderwire subnet.
Prerequisites
n Conference calls must be congured.
n Applies to most OSN, LH WDM and Metro WDM series products.

Procedure
Tree. Click the Subnet No. for the Optical Interface tab.

Step 3 Select an optical port where conference calls are congured, click the subnet eld and enter a
subnet number.
NOTE
Optical ports with the same subnet number belong to the same orderwire subnet.
Step 4 Click Apply.

----End

Operator Guide 7 Managing Communication Between the T2000 and NEs
7 Managing Communication
Between the T2000 and NEs
About This Chapter

The communication ways and how to congure communication between the T2000 and NEs,
an NE and other NEs are described here.
7.1 Conguring Communication Between Subracks Without Fiber Connections

Between two subracks without ber connections, you can establish extended ECC
communication through an Ethernet line. In this way, the network center manages equipment
in a centralized manner.
7.2 Conguring Communication for Third-Party Equipment Interconnection
In case of multi-vendor networking, you need to allocate the DCC bytes of Huawei’s
equipment to ensure that the bytes are transmitted transparently.
7.3 Customising Communication Channels Between NEs
NEs communicate with each other through data communications channel (DCC). You can
congure D1-D3, D7-D9, D4-D12 as DCC and multirate DCC, to meet the requirements of
network management in a complex network. When conguring DCC, you need to set the DCC
rate and allocate DCC resources according to DCC channel types.
7.4 Modifying the GNE’s IP or NSAP Address
You can modify the GNE’s IP or NSAP address. When the communication protocol between
the GNE and NEs changes, for example, IP protocol is changed to OSI protocol, or when you
need to modify the GNE’s IP or NSAP address, you can perform this operation.
7.5 Changing a Normal NE to a GNE
When you adjust the link that is used for communication between the GNE and the T2000, you
can change a normal NE to a GNE.
7.6 Modifying the GNE’s Communication Settings
When the communication protocol between the GNE and NEs changes, for example, IP
protocol is changed to OSI protocol, or when you need to modied the GNE’s IP or NSAP
address, you can perform this operation.
7.7 Changing a GNE to a Normal NE
When you adjust the link that is used for communication between the GNE and the T2000,
you can change the GNE to a normal NE.
7.8 Changing the GNE for NEs
When there is any change to the GNE to which non-gateway NEs are associated, for
example, the GNE or an NE moves to another place, you need to change the GNE to remain
communication with the T2000. Alternatively, when a GNE manages more then 50 NEs,
change the GNE for some NEs, to avoid decreased communication efciency between the
T2000 and the NEs.
7.9 Testing the Communication Between the T2000 and the GNE
When the network communication fails, you can view the communication between the GNE
and the T2000.

7 Managing Communication Between the T2000 and NEs Operator Guide
7.10 Conguring Standby GNEs for NEs

You can congure standby GNEs for NEs, so that when the GNE fails, NEs can keep the
communication with the T2000. You can congure up to three standby GNEs for an NE.

7.1 Conguring Communication Between Subracks

Without Fiber Connections
Between two subracks without ber connections, you can establish extended ECC
communication through an Ethernet line. In this way, the network center manages equipment
in a centralized manner.
Prerequisite
Context
NOTE
This operation may interrupt the service.
Procedure
Step 1 In the NE Explorer, click an NE and select Communication > ECC Management from the
Function Tree.
Step 2 Select ECC Extended Mode.
n If Specied Mode is selected, you need to specify the IP and Port of the server, and the
Opposite IP and Port.
n If Auto Mode is selected, all parameters are set automatically.
Step 3 Click Apply to send the congurations.
Step 4 Click OK in the warning dialog box.
Step 5 Click Close.
----End
7.2 Conguring Communication for Third-Party

Equipment Interconnection
In case of multi-vendor networking, you need to allocate the DCC bytes of Huawei’s
equipment to ensure that the bytes are transmitted transparently.
Prerequisite
Context
In case of multi-vendor networking, it transparently transmits the DCC bytes of the equipment
from other vendors. You can allocate the DCC bytes of Huawei’s equipment so that the bytes
are transmitted transparently through the idle DCC bytes of the third-party’s equipment. This
may occur in one of the following three ways:

n Huawei’s equipment is in the network center, while a third party’s equipment is at the
edge of the network, and the third party’s network management system uses the D1 to
D3 bytes. In this case, Huawei’s equipment transparently transmits the third party’s
DCC bytes through three consecutive bytes between D4 and D12.
n Huawei’s equipment is at the edge of the network, while a third party’s equipment is
in the network center, and the third party’s network management system uses the D1
to D3 bytes. In this case, Huawei’s equipment adjusts its own D1-D3 bytes to three
consecutive bytes between D4 and D12, to transparently transmit network management
information through the third-party’s equipment.
n Huawei’s equipment also transparently transmits other overhead bytes, for example,
E1-E2, K1-K2, or X1-X3, through the idle D bytes.
Procedure
Step 1 In the NE Explorer, click an NE and select Communication > DCC Management from the
Function Tree.
Step 2 Click the DCC Transparent Transmission Management tab.
Step 3 Click New and the Create DCC Transparent Transmission Byte dialog box is displayed.
Select the source and the sink timeslot, port and overhead bytes.
Step 4 Click OK.
----End
7.3 Customising Communication Channels Between NEs

NEs communicate with each other through data communications channel (DCC). You can
congure D1-D3, D7-D9, D4-D12 as DCC and multirate DCC, to meet the requirements of
network management in a complex network. When conguring DCC, you need to set the DCC
rate and allocate DCC resources according to DCC channel types.
Prerequisite
Context
NOTE
The NE uses D1-D3 as DCC by default and allows for DCC communications.
Procedure
Step 1 In the NE Explorer, click an NE and select Communication > DCC Management from the
Function Tree.
Step 2 Click the DCC Rate Conguration tab. Double-click and set the DCC rate.
Step 3 Click Apply to send the conguration.
Step 4 Click the DCC Resource Allocation tab. Double-click and set the number of DCC channels.

Step 5 Click Apply to send the conguration.

----End
7.4 Modifying the GNE’s IP or NSAP Address

You can modify the GNE’s IP or NSAP address. When the communication protocol between
the GNE and NEs changes, for example, IP protocol is changed to OSI protocol, or when you
need to modify the GNE’s IP or NSAP address, you can perform this operation.
Prerequisite
Procedure
Step 1 Select System Administration > DCN Management from the Main Menu.
Step 2 Click the GNE tab.
Step 3 Right-click a GNE and select Modify GNE.
The Modify GNE dialog box is displayed.
Step 4 Select the Gateway Type and enter the IP Address or NSAP Address.
Step 5 Click OK.
----End
7.5 Changing a Normal NE to a GNE

When you adjust the link that is used for communication between the GNE and the T2000, you
can change a normal NE to a GNE.
Prerequisite
You must be an NM user with authority of "NE and network maintainer" or higher.
Procedure
Step 2 Select the NE tab.
Step 3 Right-click a normal NE and select Change to GNE.
The Change to GNE dialog box is displayed.
Step 4 Select the Gateway Type and enter the IP Address or NSAP Address.
Step 5 Click OK.

The NE is now changed to a GNE and appears in the GNE tab.

----End
7.6 Modifying the GNE’s Communication Settings

When the communication protocol between the GNE and NEs changes, for example, IP
protocol is changed to OSI protocol, or when you need to modied the GNE’s IP or NSAP
address, you can perform this operation.
Prerequisite
Context
NOTE
Procedure
Step 2 Click the GNE tab.
Step 3 Right-click a normal GNE and select Modify GNE from the shortcut menu.
Step 4 Select the Gateway Type and enter the address.
Step 5 Click OK.

----End
7.7 Changing a GNE to a Normal NE

When you adjust the link that is used for communication between the GNE and the T2000,
you can change the GNE to a normal NE.
Prerequisite
Context
NOTE

Procedure
Step 2 Select the GNE tab.
Step 3 Right-click the GNE to be changed and select Delete GNE from the shortcut menu.
Step 4 Click OK in the Conrm dialog box.
Step 5 Click OK in the Reconrm dialog box.
----End
Postrequisite
After changing the GNE to a normal NE, modify the attributes of the NE that uses the GNE
and select another GNE.
7.8 Changing the GNE for NEs

When there is any change to the GNE to which non-gateway NEs are associated, for
example, the GNE or an NE moves to another place, you need to change the GNE to remain
communication with the T2000. Alternatively, when a GNE manages more then 50 NEs,
change the GNE for some NEs, to avoid decreased communication efciency between the
T2000 and the NEs.
Prerequisite
Context
NOTE
Procedure
Step 1 Select System Management > DCN Management from the Main Menu.
Step 2 Click the NE tab.
Step 3 Select an NE entry. Double-click the Primary GNE1 eld and select a GNE from the
drop-down list.
Step 4 Click Apply.
----End
7.9 Testing the Communication Between the T2000 and

the GNE
When the network communication fails, you can view the communication between the GNE
and the T2000.
Prerequisite

Procedure
Step 1 Select System Administration > DCN Management from the Main Menu. Click the GNE
tab.
Step 2 Right-click the GNE to be tested and select Test GNE from the shortcut men.
The Test Result dialog box is displayed. Click Close.
----End
7.10 Conguring Standby GNEs for NEs

You can congure standby GNEs for NEs, so that when the GNE fails, NEs can keep the
communication with the T2000. You can congure up to three standby GNEs for an NE.
Prerequisite
Procedure
Step 2 Select the NE tab.
Step 3 Select an NE entry. Double-click GNE2 and select a GNE from the drop-down list.
NOTE
To congure multiple standby GNEs, select a GNE respectively from the GNE3 and GNE4 drop-down
lists.
Step 4 Click Apply.

----End

Operator Guide 8 Setting NE Time
8 Setting NE Time
About This Chapter

With the time synchronization schemes provided in the T2000, you can correct the time for
all NEs manually or automatically. The NE time accuracy is important for troubleshooting
and networking monitoring, so the NE time synchronization must be set before service
conguration.
Context
To ensure the NE time accuracy, you can set the NE time by the following schemes.
8.1 Time Synchronization Schemes for the T2000 and NEs

With the time synchronization function, the NE time is kept consistent with the T2000 server
time. In this way, the T2000 is able to record the correct occurring time of alarms and
abnormal events reported by NEs.
8.2 Synchronizing NE Time with the T2000 Server Automatically
After proper settings, the NE time can be synchronized with the T2000 server time
automatically. In this way, the time of alarms and logs can be correctly recorded in the T2000.
If the NTP service is not congured for the T2000 and NEs, make proper settings before service
conguration so that the NE time can be synchronized with the T2000 server automatically.
8.3 Synchronizing NE Time with the T2000 Server Manually
For NEs without the NTP service congured, you are suggested to check whether the NE time
is consistent with the T2000 server time. If not, synchronize the NE time with the T2000
server manually.
8.4 Synchronizing NE Time with the NTP Server
The Network Time Protocol (NTP) service can be used to keep NE time synchronized with
the NTP server automatically. In theory, the accuracy of NE time can reach a nanosecond.
If NTP servers are congured in the network, set NTP time synchronization for NEs before

8 Setting NE Time Operator Guide
8.1 Time Synchronization Schemes for the T2000 and NEs

With the time synchronization function, the NE time is kept consistent with the T2000 server
time. In this way, the T2000 is able to record the correct occurring time of alarms and
abnormal events reported by NEs.
When NEs report alarms and abnormal events to the T2000, the occurring time of such alarms
and events is based on the NE time. If the NE time is incorrect, then wrong occurring time of
alarms is recorded in the T2000, which may cause troubles in fault location. The same case
happens to the occurring time of abnormal events that are recorded in the NE security log.
To ensure the NE time accuracy, the T2000 provides two time synchronization schemes:
synchronizing with the T2000 server and synchronizing with the NTP server.
In the former scheme, all NEs use the T2000 server time as the standard time, and can be
synchronized with the T2000 server manually or automatically. The T2000 server time refers
to the time of the computer system where the T2000 server resides. This scheme features easy
operation and applies to a network with relatively low requirement for time accuracy.
In the latter scheme, all NEs and the T2000 are synchronized with the NTP server
automatically. The NTP server can be either the T2000 server or a special time server. This
scheme enables the T2000 and NEs to have a time accuracy of one nanosecond in theory, and
applies to a network with very high requirement for time accuracy.
8.2 Synchronizing NE Time with the T2000 Server

Automatically
After proper settings, the NE time can be synchronized with the T2000 server time
automatically. In this way, the time of alarms and logs can be correctly recorded in the T2000.
If the NTP service is not congured for the T2000 and NEs, make proper settings before service
conguration so that the NE time can be synchronized with the T2000 server automatically.
Prerequisite
Procedure
Step 1 Select Conguration > NE Time Synchronization from the Main Menu.
Step 2 Select the NEs in the left pane and click .

Step 3 Set the Synchronous Mode parameter to NM and click Apply.
Step 4 Click Close when the success prompt appears.
Step 5 Set the Synchronize Starting Time and Synchronization Period (days) parameters in the
lower pane. Click Apply.
Step 6 Click OK when a conrmation dialog box is displayed.
Step 7 Click Close in the Operation Result dialog box.
----End

Operator Guide 8 Setting NE Time
8.3 Synchronizing NE Time with the T2000 Server

Manually
For NEs without the NTP service congured, you are suggested to check whether the NE time
is consistent with the T2000 server time. If not, synchronize the NE time with the T2000
server manually.
Prerequisites
n The synchronous mode of NE time is set to NM or None.
Context
NOTE
Synchronizing NE time does not affect the service. Before synchronizing the NE time, verify that the
system time on the T2000 server is correct. If you want to change the system time, exit the T2000
to reset the time and then start the T2000 again.
Procedure

Step 3 Select one or more NEs in the list. Right-click and select Synchronize with NM from the
shortcut menu.
NOTE
You can perform this operation only when the Synchronous Mode is set to NM or None.
Step 4 Click Yes in the prompt dialog box.

----End
8.4 Synchronizing NE Time with the NTP Server

The Network Time Protocol (NTP) service can be used to keep NE time synchronized with
the NTP server automatically. In theory, the accuracy of NE time can reach a nanosecond.
If NTP servers are congured in the network, set NTP time synchronization for NEs before
Prerequisites
n The NE must support the NTP synchronization mode.
Procedure

Step 3 Set the Synchronous Mode parameter to NTP.
Step 4 Set the Server Enabled parameter to decide whether the NE works as the NTP server.
n If the ECC protocol is adopted for the communication between NEs, set Server Enabled
to ECC Server for gateway NEs, and to Disabled for non-gateway NEs.

8 Setting NE Time Operator Guide
n If the IP protocol is adopted for the communication between NEs, set Server Enabled
to Disabled for all NEs.
Step 5 Set the Client Enabled parameter to decide whether the NE works as a client of the NTP server.
n If the ECC protocol is adopted for the communication between NEs, set Client Enabled
to IP Client for gateway NEs, and set it to ECC Client for non-gateway NEs.
n If the IP protocol is adopted for the communication between NEs, set Client Enabled
to IP Client for all NEs.
Step 6 Set the Synchronous Server parameter.
n If the ECC protocol is adopted for the communication between NEs, for gateway NEs
set Synchronous Server to the IP address of the upper level NTP server, and for
non-gateway NEs set it to the gateway NE ID.
n If the IP protocol is adopted for the communication between NEs, for all NEs set
Synchronous Server to the IP address of the upper level NTP server.
Step 7 Set the Polling Period (min) and The Number of Sampling parameters.
Step 8 Click Apply.
----End

Operator Guide 9 Conguring Protection Subnets
9 Conguring Protection Subnets
About This Chapter

You can provide network level protection to services for NEs in a protection subnet. It is
recommended to create the protection subnet before service conguration. For version 5.0
NEs, you can create PP or SNCP services directly by using the trail management function. For
other NEs, you must create the protection subnet before using the trail management function.
Context
The main topics are:
9.1 Searching for Protection Subnets

For SDH equipment, you can search for protection subnets. In this way, the congured
protection attributes at the NE layer on the T2000 are synchronized to the network layer on the
T2000 to automatically create protection subnets.
9.2 Conguring MSP Rings
You can congure a multiplex section protection (MSP) ring to protect services for NEs on the
ring.
9.3 Conguring Linear MSP
For a link network, you can congure a linear multiplex section protection (MSP) to protect
services in the link.
9.4 Conguring SNCP Protection
Set SNCP nodes on the protection subnet to support SNCP services that cross protection
subnets. The SNCP nodes allow services to be dual-fed in the two directions of a ring, and
selectively received at a timeslot outside the ring, and thus SNCP protection is implemented.
Generally, the incoming point and the outgoing point are created as the SNCP node. SNCP
is a kind of 1+1 protection. An SNCP-protected service is transmitted on the working and
protection channels at the same time. When the working subnet fails or deteriorates to a certain
threshold, the protection channel takes over.
9.5 Conguring Path Protection
You can congure a path protection (PP) ring to protect services for NEs on the ring.
9.6 Conguring DNI Protection
Use the following process to congure DNI protection.
9.7 Conguring a Non-Protection Ring
When services on a ring need no protection, you can congure a non-protection (NP) ring. All
timeslots on the ring can be used to transmit services.
9.8 Conguring Non-Protection Chains
You can create a non-protection chain by wizard.
9.9 Deleting Protection Subnets
Use this procedure to delete protection subnets.
9.10 Conguring RPR Protection
It is recommended to congure an RPR ring by the process below.

9 Conguring Protection Subnets Operator Guide
9.11 Conguring Trunk Link-Based RPR Rings

You can congure RPR rings based on trunk links to protect Ethernet services.

9.1 Searching for Protection Subnets

For SDH equipment, you can search for protection subnets. In this way, the congured
protection attributes at the NE layer on the T2000 are synchronized to the network layer on the
T2000 to automatically create protection subnets.
Prerequisites
n NE data must be congured, and bers must be correctly created.
Procedure
Step 1 Select Conguration > Protection View from the Main Menu. In the Protection View, select
Protection View > SDH Protection Subnet Search. The search wizard is displayed.
Step 2 In the Consistency Verication of Existing Subnet screen, select the protection subnet you
want to check. Click Next.
Step 3 Click Search to start the search. The Subnet Name, Subnet Status and Subnet Type
parameters of the searched protection subnet are shown automatically.
A prompt appears telling you that the operation was successful. Click Close.
Step 4 Click Next. The discrete logical systems are shown in the upper left portion of the window.
Step 5 Optional: Select the nodes that do not form any protection subnet, and click Delete. Click Yes
in the pop-up prompt box.
Step 6 Click Finish. The searched protection subnet is shown in the Protection View.
----End
9.2 Conguring MSP Rings

You can congure a multiplex section protection (MSP) ring to protect services for NEs on the
ring.
Context
It is recommended to congure MSP ring by the process below:
9.2.1 Creating a Two-Fiber MS-SPRing

A MSP ring allows the APS protocol, to provide protection at multiplex section level.
Bidirectional MSP uses uniform routing that increases network utilization greatly. It is more
suitable for networks with large service capacity.
9.2.2 Creating a Two-Fiber MS-DPRing
Compared with a bidirectional MSP ring, a unidirectional MSP ring uses diverse routing to
provide MSP for an STM-1 ring.
9.2.3 Creating a Four-Fiber MS-SPRing
suitable for networks with large service capacity. The four-ber MS-SPRing uses two bers as
the working path and another two as the protection path. The network capacity is double the
capacity of a two-ber MS-SPRing.

9.2.4 Multiplex Section Squelch

Multiplex section squelch is a major solution to service misconnection resulted from protection
switching on the MSP ring. Upon MSP switching, the node where the switching is performed
automatically inserts alarm signals into the services that may be misconnected to make them
unavailable; after the services revert to the working path, the node does not insert the alarm
signals any more.
9.2.5 Conguring the MS Squelch Table
In an MSP ring, when multiple nodes fail or a node fails and becomes an isolated one,
service misconnection may occur. You can congure the MS squelch table to avoid service
misconnection effectively.
9.2.617.1 Adjusting the Capacity of an MSP Ring
You can adjust the VC4 channels that the congured multiplex section protection (MSP) ring
occupies, to increase bandwidth utilization without interrupting services. For example, an
STM-16 two-ber bidirectional MSP ring protects up to eight VC4 services. Actually, only six
VC4 services need to be protected. Therefore, you can adjust the protection capacity of the
MSP ring to six VC4 channels, saving two VC4 channels to carry unprotected services.
9.2.717.2 Expanding Link Capacity of an MSP Ring
To grow your network, you can expand the link capacity of an multiplex section protection
(MSP) ring. According to the MSP protection scheme, you can replace the existing board with
one of a higher rate without interrupting the primary services, to expand the link capacity.
9.2.1 Creating a Two-Fiber MS-SPRing

suitable for networks with large service capacity.
Prerequisites
Context
NOTE
n The number of nodes in an MSP ring cannot exceed 16.
n When creating a protection subnet, select SDH NEs only. There is no need to select REG or WDM
equipment.
Procedure
Protection View > Create SDH Protection Subnet > 2f_MS SPRing. The Wizard for
Creating Two-Fiber Bidirectional MS Shared Protection Ring is displayed.
Step 2 Enter the name of the protection subnet.
The default name is usually used, for example: 2f_MS SPRing_1.
Step 3 Select the rate of the protection subnet. For example: STM-4.

Step 4 Select Assigned by VC4 and Resource Sharing as needed.
NOTE
n Select the Resource Sharing option when the same port of a board is used by multiple protection
subnets. If different protection subnets use different ports of a board, this option is not mandatory.
n Select the Assigned by VC4 option when there are different VC4s belonging to different protection
subnets in order to achieve virtual optical path protection. For example, for an STM-16 ber, the
VC4s 1–4 belong to an STM-4 MSP, while VC4s 5–8 belong to a PP.
Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the Protection View
to add it to the left-hand node list. Meanwhile, is displayed on the NE icon. If you want to
cancel the selection, double-click the NE again.
Double-click the selected NE again to cancel it.
NOTE
For easy maintenance purpose, nodes are recommended to be added anticlockwise to the protection
subnet.
Step 6 Set the attribute of the nodes. Select MSP Node in this example.

Step 7 Click Next to proceed to the Select Link screen of the wizard.
NOTE
n If there are multiple bers between two NEs, select them from the Physical Link Information
drop-down list.
n If Assigned by VC4 is selected, you can select the working and protection VC4 timeslots as needed.
n MSP uses the K1 byte and K2 byte to transmit information. Thus, you must assign the rst timeslot
to the MSP subnet. There must be only one MSP subnet for a ber.

The created protection subnet is displayed on the Protection View.
Step 9 Right-click the protection subnet and select Protection Subnet Attributes.
Step 10 Click the Protection Subnet Maintenance tab to check whether the protocol controller
is started. If not, select all the NEs of the protection subnet. Right-click them and select
Start/Stop Protocol > Start. Ensure that the status of all the values in the Protocol Controller
column is Protocol Started.
Step 11 Click the Protection Subnet Parameters tab and set the WTR time and SD condition as
needed. The WTR time of all NEs in the same protection subnet should be the same.
NOTE
The default value is 600s.
----End
9.2.2 Creating a Two-Fiber MS-DPRing

Compared with a bidirectional MSP ring, a unidirectional MSP ring uses diverse routing to
provide MSP for an STM-1 ring.
Prerequisites

Context
NOTE
equipment.
Procedure
Protection View > Create SDH Protection Subnet > 2f_MS DPRing. The Wizard for
Creating Two-Fiber Unidirectional MS Dedicated Protection Ring is displayed.
The default name is usually used, for example: 2f_MS DPRing_1.
NOTE

NOTE
subnet.
NOTE
drop-down list.


NOTE
----End
9.2.3 Creating a Four-Fiber MS-SPRing

suitable for networks with large service capacity. The four-ber MS-SPRing uses two bers as
the working path and another two as the protection path. The network capacity is double the
capacity of a two-ber MS-SPRing.
Prerequisites
Context
NOTE
equipment.
Procedure
Step 1 In the Protection View, select Protection View > Create SDH Protection Subnet > 4f_MS
SPRing. The Wizard for creating Four-Fiber Bidirectional MS shared protection ring is
displayed.
The default name is usually used, for example: 4f_MS SPRing_1.

NOTE
NOTE
subnet.

NOTE
drop-down list.

NOTE
----End

9.2.4 Multiplex Section Squelch

Multiplex section squelch is a major solution to service misconnection resulted from protection
switching on the MSP ring. Upon MSP switching, the node where the switching is performed
automatically inserts alarm signals into the services that may be misconnected to make them
unavailable; after the services revert to the working path, the node does not insert the alarm
signals any more.
In an MSP ring, every protection timeslot is shared by different sections or occupied by extra
services. Service misconnection may occur under each of the following conditions:
n When the ring contains no extra service, if multiple points fail or a node fails and becomes
an isolated one, services from different sections sharing the same timeslot may preempt
the same timeslot and lead to service misconnection.
n When a node with the cross-connect function fails, the timeslots requiring
cross-connection are looped back from its upstream node and reach the downstream node
without being cross-connected, and lead to service misconnection.
9.2.5 Conguring the MS Squelch Table

In an MSP ring, when multiple nodes fail or a node fails and becomes an isolated one,
service misconnection may occur. You can congure the MS squelch table to avoid service
misconnection effectively.
Prerequisites
n The bEnableSquelch=1 parameter must be set in the /T2000/Server/ems.cfg le.
n The squelch_Switch_DefaultClose=value(1) parameter must be set in the
/T2000/Client/bin/cong.ini le.
n NE data must be congured, and the MS-SPRing and services must be created correctly.
Context
NOTE
n This function can only be used to squelch VC4 and VC4 concatenated services. The alarm inserted
upon switching is AU-AIS.
n Applies to the OptiX 10G(Metro 5000), OptiX Metro 1050 and the OSN series products.
Procedure
Protection View > SDH Protection Subnet Maintenance. Click the Squelch Table tab.
Step 2 Click Calculate to calculate the squelch table. Click Apply.
NOTE
n The squelch table only supports services at VC4 level and above, not lower order services. The
value of Lower Order VC Flag is No.
n Activation Status means whether the service is activated. If it is Activated, the squelch table is sent
to the NEs. A service trail is activated only when all the SDH services carried over it are activated.
----End
9.2.6 Adjusting the Capacity of an MSP Ring


Prerequisites
n The MSP ring must be created.
Context
NOTE
n This function applies to two-ber unidirectional MSP ring, two-ber bidirectional MSP ring and
four-ber bidirectional MSP ring.
n Capacity adjustment cannot be performed when the protection subnet is in the switching state.
Procedure
Protection View > SDH Protection Subnet Management.
Step 2 Select the MSP subnet for which you wish to adjust capacity from the protection subnet list,
right-click and select Capacity adjustment.
Step 3 Select the capacity level in the Modify Information eld, and check the Resource Sharing
check box.
Step 4 Click VC4 in Modify Information. Select the desired VC4 channel from the drop-down list
and click to set it as selected channel. Click Apply.

Step 5 Click OK.
----End
9.2.7 Expanding Link Capacity of an MSP Ring

Prerequisites
n You must log in to the T2000 as user admin in the single user mode.
n The data on the T2000 is consistent with that on the NE.
n Attended expansion is required at both ends of the link to be expanded, so that
replacement of boards can be performed.
n Applies to the OptiX OSN 1500, OptiX OSN 2500, OptiX OSN 3500, OptiX OSN 7500
and OptiX OSN 9500.
n Multi-port optical boards are not supported.
Context
CAUTION
n Read the on-screen prompt messages carefully during the expansion because this is a
potential service affecting operation.
n During the expansion, extra services in the protection path are interrupted.

Procedure
Step 1 Select Conguration > Expansion Wizard > Upgrade Link Capacity from the Main Menu.
The Upgrade Link Capacity dialog box is displayed.
Step 2 Click Next and go to "Step 1: Select the ber to be expanded". Click a link, or click the
icon to select a link from the Main Topology.
NOTE
Only bers between SDH NEs can be expanded. Expansion of bers connecting to REG or OTU is not
supported.
Step 3 Click Next and go to "Step 2 Select a board". Click Replace Source Board with and Replace
Sink Board with respectively to select a board type.
NOTE
The boards for replacement must be of the same or higher rate. The source and the sink boards must be
of the same rate.
Step 4 Click Next and go to "Step 3 Protect MSP service".

n Click Forced Switch Request, and the forced switch command is issued to both ends
of the selected link.
n Click Query to query the current protection subnet status.
CAUTION
n After the forced switch, extra services and unprotected services in the link are interrupted.
The services are restored only when the switch is cleared.
n If Forced Upgrade is selected, go to the fourth step without performing the forced switch.
But the primary services are also interrupted.
n Before performing the forced switch, make sure that the appropriate station is in an attended
mode and that the board is replaced successfully.
Step 5 Replace the board at the appropriate station and re-connect the physical bers.
Step 6 Click Next and go to "Step 4 Conrm the selected data".

Step 7 Click Next and go to "Step 5 Conrm the affected data".
Step 8 Click Next and go to "Step 6 Send conguration".
Click Apply. The conrmation dialog box is displayed saying Please ensure the
board is changed and working, and the fiber is created. Click OK.
NOTE
Clear the switch after the conguration data is sent to the NE.
Step 9 Optional: Repeat Steps 2 through 8 to expand all links in the protection subnet.
----End

9.3 Conguring Linear MSP

For a link network, you can congure a linear multiplex section protection (MSP) to protect
services in the link.
Context
It is recommended to congure a linear MSP by the process below:
9.3.1 Creating 1+1 Linear MSP

In a link network, to protect important services, you need to create 1+1 linear MSP. In this
way, the NE dual feeds services at the source end and selects either of the two services at the
sink end.
9.3.2 Creating M:N Linear MSP
You can create M:N linear MSP for a link network. In this way, the network uses the secondary
path to transmit extra services.
9.3.317.3 Adjusting the Capacity of a Linear MSP
You can adjust the VC4 channels that the congured linear multiplex section protection (MSP)
STM-16 1:1 linear MSP protects up to 16 VC4 services. Actually, only 10 VC4 services need
to be protected. Therefore, you can adjust the protection capacity of the linear MSP to 10 VC4
channels, saving six VC4 channels to carry unprotected services.
9.3.417.4 Expanding Link Capacity of a Linear MSP
To grow your network, you can expand the link capacity of a linear multiplex section
protection (MSP). According to the MSP protection scheme, you can replace the existing
board with one of a higher rate without interrupting the primary services, to expand the link
capacity. For example, change the line boards at both ends of the link to be expanded, to
expand an STM-16 linear MSP to an STM-64 one.
9.3.1 Creating 1+1 Linear MSP

In a link network, to protect important services, you need to create 1+1 linear MSP. In this
way, the NE dual feeds services at the source end and selects either of the two services at the
sink end.
Prerequisites
Procedure
Protection View > Create SDH Protection Subnet > 1+1 linear MSP. The Wizard for
Creating 1+1 Linear MSP Chain is displayed.
The default name is usually used, for example: 1+1_MSP_1.

Step 4 Select the Revertive Mode and the Switching Mode as needed.
NOTE
n Revertive Mode refers to the handling strategy adopted after the faulty line recovers to normal.
– Revertive: The service automatically reverts to the working channel after the faulty line recovers
to normal.
– Non-Revertive: The service does not automatically revert to the working channel after the
faulty line recovers to normal.
n Switching Mode refers to the switching strategy adopted after a fault occurs to the line.
– Single-ended switching: The receive end switches to the protection channel when the working
channel is faulty. In this way, the service is protected.
– Dual-ended switching: To protect the service, the switching starts at the receive and transmit
ends when either end is faulty.

Step 6 Click Next to proceed to the Select Link of the wizard. Select the Working Link and
Protection Link.


Step 9 Click the Protection Subnet Maintenance tab to check whether the protocol controller is
started. If not, select all the NEs of the protection subnet. Select all the NEs of the protection
subnet. Right-click them and select Start/Stop Protocol > Start. Ensure that the status of all
the values in the Protocol Controller column is Protocol Started.
NOTE
----End
9.3.2 Creating M:N Linear MSP

You can create M:N linear MSP for a link network. In this way, the network uses the secondary
path to transmit extra services.

Prerequisites
Procedure
Protection View > Create SDH Protection Subnet > M:N Linear MSP. The Wizard for
Creating M:N Linear MSP Chain is displayed.
Step 2 Enter the name of the protection subnet. The default name is usually used, for example:
M:N_MSP_1.
Step 4 Select the number of working links in the N eld.

M is the number of protection links. It cannot be congured. By default it is 1. N is the
number of working links.
Step 6 Click Next to proceed to the Select Link screen of the wizard. Select the Working Link
and the Protection Link.


Step 9 Click the Protection Subnet Maintenance tab to check whether the protocol controller is
started. If not, select all the NEs of the protection subnet. Select all the NEs of the protection
subnet. Right-click them and select Start/Stop Protocol > Start. Ensure that the status of all
the values in the Protocol Controller column is Protocol Started.
Step 10 Click the Protection Subnet Parameters tab and set WTR time as needed. The WTR time of
all NEs in the same protection subnet should be the same.
----End

9.3.3 Adjusting the Capacity of a Linear MSP

Prerequisites
n The linear MSP must be created.
Context
NOTE
n This function applies to 1+1 linear MSP and M:N linear MSP.
Procedure
check box.

Step 5 Click OK.
----End
9.3.4 Expanding Link Capacity of a Linear MSP

Prerequisites
n The MSP protection must be created.
n Applies to the OptiX OSN series products.

Context
CAUTION
Procedure
Step 1 Select Conguration > Expansion Wizard > Upgrade Link Capacity. The Upgrade Link
Capacity dialog box is displayed.
Step 2 Click Next and go to "Step 1 Select the ber to be upgraded". Click a link, or click the
NOTE
supported.
NOTE
of the same rate.

n Click Query to query the current protection subnet status. Replace the board at the
appropriate station and re-connect the physical bers.

NOTE
n After the forced switch, extra services and unprotected services in the link are interrupted. The
services are restored only when the switch is cleared.
n If Forced Upgrade is selected, go to the fourth step without performing the forced switch. But the
primary services are also interrupted.
n Before performing the forced switch, make sure that the appropriate station is in an attended mode
and that the board is replaced successfully.
Click Apply. The Conrmation dialog box is displayed saying Please ensure the

NOTE
Step 9 Repeat Steps 2 through 8 to expand all links in the protection subnet.
----End
9.4 Conguring SNCP Protection

Set SNCP nodes on the protection subnet to support SNCP services that cross protection
subnets. The SNCP nodes allow services to be dual-fed in the two directions of a ring, and
selectively received at a timeslot outside the ring, and thus SNCP protection is implemented.
Generally, the incoming point and the outgoing point are created as the SNCP node. SNCP
is a kind of 1+1 protection. An SNCP-protected service is transmitted on the working and
protection channels at the same time. When the working subnet fails or deteriorates to a certain
threshold, the protection channel takes over.
Prerequisites
n The protection subnet must be created for release 4.0 NEs. The equipment includes the
OptiX 155/622H(Metro 1000), the OptiX 155/622(Metro 2050), the OptiX 2500+(Metro
3000) and the OptiX Metro 3100.
Context
NOTE
You need to create SNCP nodes and congure SNCP for release 4.0 NEs only. For the method of
querying the NE software, refer to Viewing Unit Version.
Procedure
Step 1 Select Conguration > Protection View from the Main Menu.
Step 2 Right-click the NE that you want to create as the SNCP node, and select Create SNCP Node >
Create xxx SNCP Node.
NOTE
"xxx" refers to the name of the protection subnet of this NE.
----End
9.5 Conguring Path Protection

You can congure a path protection (PP) ring to protect services for NEs on the ring.
Context
It is recommended to congure path protection by the process below:

9.5.1 Creating a Two-Fiber Unidirectional PP Ring

The two-ber unidirectional PP ring is a 1+1 service protection scheme. It adopts the structure
of "bridging at the source and switching at the sink". One ber is used as the primary ber (the
S ber), and the other as the secondary ber (the P ber). The same signals are transmitted
on both bers but in opposite directions. At the receive end, the signals are selected from the
primary or secondary ber according to the signal quality on the two bers. This scheme
applies to a network where there is relatively low requirement for service capacity and where
most services are converged at one node. Compared with the MSP scheme, the two-ber
unidirectional PP ring does not need a protocol for protection switching, and thus features
a shorter switching time.
9.5.2 Creating a Two-Fiber Bidirectional PP Ring
The two-ber bidirectional PP ring is a 1+1 service protection scheme. It adopts the structure
primary or secondary ber according to the signal quality on the two bers. Compared with the
two-ber unidirectional PP ring, the two-ber bidirectional PP ring has the path reuse function
for a non-protected ring or a linear networking with only ADM equipment, and thus increases
the add/drop capacity. Besides, for bidirectional services, this scheme ensures the uniform
routing, which is crucial for delay-sensitive services (like video services). Compared with the
MSP scheme, the two-ber bidirectional PP ring does not need a protocol for protection
switching, and thus features a shorter switching time.
9.5.1 Creating a Two-Fiber Unidirectional PP Ring

The two-ber unidirectional PP ring is a 1+1 service protection scheme. It adopts the structure
primary or secondary ber according to the signal quality on the two bers. This scheme
applies to a network where there is relatively low requirement for service capacity and where
most services are converged at one node. Compared with the MSP scheme, the two-ber
unidirectional PP ring does not need a protocol for protection switching, and thus features
a shorter switching time.
Prerequisites
Procedure
Protection View > Create SDH Protection Subnet > PP (Uniform Route). The Wizard for
Creating PP ring (Uniform route) is displayed.
The default name is usually used, for example: PP (Uniform_Route) _1.
Step 3 Select the rate of the protection subnet.
For example: STM-4.
Step 4 Select Resource Sharing and Assigned by VC4 as needed.

NOTE
subnet.
Step 6 Set the attribute of the nodes. Select PP Node in this example.

----End
9.5.2 Creating a Two-Fiber Bidirectional PP Ring

The two-ber bidirectional PP ring is a 1+1 service protection scheme. It adopts the structure
primary or secondary ber according to the signal quality on the two bers. Compared with the
two-ber unidirectional PP ring, the two-ber bidirectional PP ring has the path reuse function
for a non-protected ring or a linear networking with only ADM equipment, and thus increases
the add/drop capacity. Besides, for bidirectional services, this scheme ensures the uniform
routing, which is crucial for delay-sensitive services (like video services). Compared with the
MSP scheme, the two-ber bidirectional PP ring does not need a protocol for protection
switching, and thus features a shorter switching time.
Prerequisites
Procedure
Protection View > Create SDH Protection Subnet > PP (Diverse Route). The Wizard for
Creating PP ring (Diverse route) is displayed.


The default name is usually used, for example: PP (Diverse_Route) _1.
For example: STM-4.
Step 4 Select Resource Sharing and Assigned by VC4 as needed.
NOTE
subnet.
Step 6 Set the attribute of the nodes. Select PP Node in this example.

----End
9.6 Conguring DNI Protection

Use the following process to congure DNI protection.
9.6.1 Creating DNI Protection

You can create DNI protection for the interworking nodes of two rings, for the protection of
the interworking services between two ring networks. The network can be a combination of
different vendors’ equipment or different protection modes. Moreover, DNI is also available
to ber and node failures.
9.6.1 Creating DNI Protection

You can create DNI protection for the interworking nodes of two rings, for the protection of
the interworking services between two ring networks. The network can be a combination of

different vendors’ equipment or different protection modes. Moreover, DNI is also available
to ber and node failures.
Prerequisites
n Protection subnets for the two rings that the DNI protection is created for must be created.
Context
Figure 9-1 shows a sample networking of DNI protection.
Figure 9-1 DNI protection example

NE3/NE5 is the master node while the NE4/NE6 is the slave node.
Procedure
Step 2 In the Protection View, select Protection View > Create SDH Protection Subnet > DNI. The
"Wizard for creating DNI protection" is displayed.
For example: DNI_1.
Step 4 Double-click the icons of NE3 and NE4 on the view, and select them as the master and slave
nodes respectively for the DNI protection.
NOTE
When selecting DNI nodes on a protection ring, the west node you select is the master node and the
east node is the slave node. When the master or the slave node is selected on the Protection View, the
ag appears on its icon.
Step 5 Click Next to select the protection subnet to which the nodes are associated. Select the
associated protection subnet from the protection subnet list: 2f-MS-SPRING_1.

Step 7 Repeat Steps 2 through 6 to create the master node and the slave node: NE5 and NE6.
----End
9.7 Conguring a Non-Protection Ring

When services on a ring need no protection, you can congure a non-protection (NP) ring. All
timeslots on the ring can be used to transmit services.

Prerequisites
Procedure
Protection View > Create SDH Protection Subnet > NP Ring. The Wizard for creating
non-protection ring is displayed.
The default name is usually used, for example: NP_Ring_1.
For example: STM-4.
NOTE
and add it to the left-hand node list. Meanwhile, is displayed on the NE icon.

----End
9.8 Conguring Non-Protection Chains

You can create a non-protection chain by wizard.

9.8.1 Creating a Non-Protection Chain

When services on a link need no protection, you can congure a non-protection (NP) chain.
All timeslots on the link can be used to transmit services.
9.8.217.5 Changing an NP Chain to a 1+1 Linear MSP
The T2000 allows you to change some protection types without interrupting services, deleting
existing services from the protection subnet, and changing the trail name and other attributes.
To facilitate network management and maintenance, you can change a non-protection (NP)
chain to a 1+1 linear MSP.
9.8.1 Creating a Non-Protection Chain

When services on a link need no protection, you can congure a non-protection (NP) chain.
All timeslots on the link can be used to transmit services.
Prerequisites
Procedure
Step 2 In the Protection View, select Protection View > Create SDH Protection Subnet > NP
Chain. The Wizard for creating chain without protection is displayed.
The default name is usually used, for example: NP_Chain_1.
For example: STM-4.
NOTE
Step 6 Select the nodes contained in the non-protection chain to be created. Double-click the NE on
the Protection View and add it to the left-hand node list. Meanwhile, is displayed on the NE
icon. If you want to cancel the selection, double-click the NE again.
----End
9.8.2 Changing an NP Chain to a 1+1 Linear MSP

The T2000 allows you to change some protection types without interrupting services, deleting
existing services from the protection subnet, and changing the trail name and other attributes.

To facilitate network management and maintenance, you can change a non-protection (NP)
chain to a 1+1 linear MSP.
Prerequisites
n Both of the two NEs are release 5.0 NEs, congured with data correctly. The two NEs
must also be working normally.
n At least two bers of the same class exist between the two NEs and are not occupied by
other protection subnets such as PP, MSP, NP ring, or NP chain with more than two nodes.
n There must be no service on the protection chain.
Procedure
Protection View > SDH Protection Type Change. The protection type change wizard is
displayed.
Step 2 Select a type and the capacity level. Click Next.
NOTE
You are allowed only to change an NP chain to a 1+1 linear MSP. You can select the value for the
change type.
Step 3 Select an NE from List of available NEs and click to move it to List of selected
NEs. Click Next.

NOTE
You can only choose two NEs.
Step 4 Select the Working Link and the Protection Link respectively from Available links. Click
Next.

Step 5 Set the protection subnet attributes.


----End
9.9 Deleting Protection Subnets

Use this procedure to delete protection subnets.
Prerequisite
Context
NOTE
If one or more trails are congured in the protection subnet you want to delete, delete the trails rst.
Procedure
n Method 1:
1. Select Conguration > Protection View and select Protection View > SDH
Protection Subnet Management in the Protection View.
2. Select protection subnets to delete, right-click it and select Delete from the NM or
Deleted from the NE or Deleted All from the NM.

NOTE
You can delete a protection subnet in one of the following three ways:
n Delete from the NM: Selecting this option deletes relation between the protection
subnet and logical systems at the NE side, to allow deleting of bers, re-uploading,
and so on. This command is not delivered to the NE and is not service-affecting. The
deleted protection subnet can be located by the searching feature. And the T2000 will
locate it according to the NE layer protection information.
n Delete from the NE: Selecting this option deletes the protection subnet, logical systems
at the NE side, and all trafc in the protection subnet. The deleted protection subnet
cannot be restored without being created again.
n Delete All from the NM: Selecting this option deletes data other than bers in the
network layer. The deleted protection subnet can be located by the searching feature.
It is recommended that you do not select this option, as a large amount of data will
be deleted.
3. Click OK to delete the protection subnet.

n Method 2:
1. Select Conguration > Protection View from the Main Menu.
2. Select protection subnets to delete.
NOTE
This method deletes the protection subnet from the NE and the operation cannot be restored.
You need to recreate a new protection subnet.
3. Select the protection subnet to delete, right-click it and select Delete Protection
Subnet.
4. Click OK to delete the protection subnet.
----End
9.10 Conguring RPR Protection

It is recommended to congure an RPR ring by the process below.

9.10.1 Creating Wrapping Protection

Wrapping protection: When a fault occurs on the ring, wrapping is performed automatically at
the node close to the failure point.
9.10.2 Creating Steering Protection
Steering protection: When a fault occurs on the ring, the protection information including
failure point and fault type will be sent to each node, and the topology will also change
correspondingly. The source node only needs to send data to the destination node according to
the new topology. The small part of data that have been sent will be discarded at the failure
point.
9.10.3 Creating Wrapping and Steering Protection
Wrapping protection triggers the switching process in a short time. Therefore, loss of frame
can be effectively prevented after a fault occurs. However, this protection mode requires more
ring bandwidth. Steering protection effectively improves utilization of ring bandwidth and
allows signals to be transmitted on the best route. However, this protection mode takes a
longer time to trigger the switching process, and a new route needs to be decided according to
the new topology after the topology becomes stable. When both the protection modes are used,
the wrapping protection is rst performed to avoid loss of packets. The steering protection
is then performed after the topology is stable. In this way, the time for which services are
interrupted is less than or equal to 50 ms.
9.10.1 Creating Wrapping Protection

Wrapping protection: When a fault occurs on the ring, wrapping is performed automatically at
the node close to the failure point.
Prerequisites
n The RPR protocol must be started.
Context
Figure 9-2 and Figure 9-3 illustrate the situations before ber cut and after wrapping protection.
The thick line indicates the normal route, and the thin line indicates the protection route.
Figure 9-2 Trafc ow before ber cut

Figure 9-3 Trafc ow after ber cut
Procedure
Step 1 In the NE Explorer, select a board and select Conguration > RPR Management > Topology
Information from the Function Tree. Select the Local Node tab.
Step 2 Set Protection Mode to Wrapping.
Step 3 Set Hold-off Time (ms), Protection Restoration Mode and Protection Wait-To-Restore (s)
according to specic conditions.
Step 4 Repeat this procedure to set Protection mode of each node on the RPR ring to Wrapping.
----End
9.10.2 Creating Steering Protection

Steering protection: When a fault occurs on the ring, the protection information including
failure point and fault type will be sent to each node, and the topology will also change
correspondingly. The source node only needs to send data to the destination node according to
the new topology. The small part of data that have been sent will be discarded at the failure
point.
Prerequisites
Context
Figure 9-4 and Figure 9-5 illustrate the situations before ber cut and after wrapping protection.
The thick line indicates the normal route, and the thin line indicates the protection route.

Figure 9-4 Trafc ow before ber cut
Figure 9-5 Trafc ow after ber cut
Procedure
Step 2 Set Protection Mode to Steering.
Step 3 Set Hold-off Time(ms), Protection Restoration Mode and Protection Wait-To-Restore(s)
Step 4 Repeat this procedure to set Protection Mode of each node on the RPR ring to Steering.
----End
9.10.3 Creating Wrapping and Steering Protection

Wrapping protection triggers the switching process in a short time. Therefore, loss of frame
can be effectively prevented after a fault occurs. However, this protection mode requires more
ring bandwidth. Steering protection effectively improves utilization of ring bandwidth and
allows signals to be transmitted on the best route. However, this protection mode takes a
longer time to trigger the switching process, and a new route needs to be decided according to
the new topology after the topology becomes stable. When both the protection modes are used,

the wrapping protection is rst performed to avoid loss of packets. The steering protection
is then performed after the topology is stable. In this way, the time for which services are
interrupted is less than or equal to 50 ms.
Prerequisites
Procedure
Step 2 Set Protection mode to Wrap and Steering.
Step 3 Set Hold-off Time (ms), Protection restoration mode and Protection Wait-To-Restore (s)
Step 4 Repeat this procedure to set Protection mode of each node on the RPR ring to Wrap and
Steering.
----End
9.11 Conguring Trunk Link-Based RPR Rings

You can congure RPR rings based on trunk links to protect Ethernet services.
Context
9.11.1 Searching for RPR Rings

The T2000 searches for congured RPR ring networks, from the NE and manage discrete RPR
ring networks. If all trunk links between adjacent nodes on the ring exists, a RPR ring network
can be found. If one or more links do not exist, there is not a complete RPR ring network. The
nodes and links are displayed as discrete services.
9.11.2 Creating an RPR Ring Network
An RPR ring network consists of multiple (2 to 255) RPR nodes and RPR links. The RPR
node consists of eastbound and westbound VCTRUNKs. For the EMR0/EGR2 board, the
westbound VCTRUNK of the RPR node is xed to VCTRUNK1, and the eastbound xed
to VCTRUNK2. When creating an RPR ring network, you need to connect the eastbound
VCTRUNK2 of the local node to the westbound VCTRUNK1 of the next node.
9.11.3 Modifying RPR Ring Parameters
You can modify the following parameters: RPR name, protection delay time, protection mode,
revertive, protection timing and protection wait-to-restore.

9.11.417.6 Adjusting Link Bandwidth of an RPR Ring

You can adjust the channels that the resilient packet ring (RPR) link occupies, to increase
bandwidth utilization without interrupting services. For example, an STM-16 1:1 linear
MSP protects up to 16 VC4 services. Actually, only 10 VC4 services need to be protected.
Therefore, you can adjust the protection capacity of the linear MSP to 10 VC4 channels, saving
six VC4 channels to carry unprotected services.
9.11.1 Searching for RPR Rings

The T2000 searches for congured RPR ring networks, from the NE and manage discrete RPR
ring networks. If all trunk links between adjacent nodes on the ring exists, a RPR ring network
can be found. If one or more links do not exist, there is not a complete RPR ring network. The
nodes and links are displayed as discrete services.
Prerequisites
n The License for the Ethernet end-to-end management function is provided.
n You must search for SDH trails before you search for RPR rings.
Procedure
Step 1 Select Trail > Ethernet Trail Search from the Main Menu.
Step 2 Check the Search for RPR check box under Select Search Mode. Click Next to start
searching for RPR rings and discrete RPR links.
Step 3 After the search is complete, click Next. The searched RPR rings and links are shown in
the Ethernet Trail Search screen.
Step 4 Click Next, and click the Discrete RPR tab. View the information about nodes and links
in the discrete RPR ring.
Step 5 In the Node tab, right-click a node and select Delete to delete a discrete RPR node.
----End
9.11.2 Creating an RPR Ring Network

An RPR ring network consists of multiple (2 to 255) RPR nodes and RPR links. The RPR
node consists of eastbound and westbound VCTRUNKs. For the EMR0/EGR2 board, the
westbound VCTRUNK of the RPR node is xed to VCTRUNK1, and the eastbound xed
to VCTRUNK2. When creating an RPR ring network, you need to connect the eastbound
VCTRUNK2 of the local node to the westbound VCTRUNK1 of the next node.

Prerequisites
n There must be two or more RPR nodes.
n The license for Ethernet end-to-end management is provided.
Context
Figure 9-6 shows the service route of the RPR ring network.
Figure 9-6 Service route of RPR ring network
NOTE
n The number of nodes on an MSP ring cannot exceed 16.
n For an RPR ring network, only SDH NEs can be selected, and REG and DWDM NEs cannot
be selected.
Procedure
Step 1 Select Conguration > RPR > Create from the Main Menu.
Step 2 Enter a name for the RPR ring network.
You can use the default name, for example, RPR1.
Step 3 Select the nodes to be included in the RPR ring network. Double-click an NE in the right-click
topology pane, and the Add Node dialog box is displayed. Select the RPR board and port and
click OK. The RPR node is added to the left-hand list, and at the same time the NE is displayed
as . If you want to cancel the selection, double-click the NE again.

NOTE
To cancel a selected RPR node, right-click the node in the left-hand list and select Delete from the
shortcut menu.
CAUTION
For an RPR ring network, nodes must be added successively in the Ring 0 or Ring 1 direction.
Step 4 Set the name for each node and start the RPR protocol.
Step 5 Click Next to set the bandwidth and route for the RPR ring network.
Step 6 Set the bandwidth and the level of rate.
Step 7 Select a route strategy.
When Automatically Create is selected, the system creates the trunk link
automatically.
When Select Existing Link is selected, the Trunk Link eld displays existing trunk
links that carry no services and satisfy the
source/sink and bandwidth conditions.
Step 8 Click Finish. A prompt appears telling you that the operation was successful.
----End
9.11.3 Modifying RPR Ring Parameters

You can modify the following parameters: RPR name, protection delay time, protection mode,
revertive, protection timing and protection wait-to-restore.
Prerequisites
n The RPR ring must be created.

Procedure
Step 1 Select Conguration > RPR Ring > Management from the Main Menu. Select the RPR
Parameter tab.
Step 2 In the Name eld, double-click and enter a proper name for the RPR ring network.
Step 3 In the Protection Delay Time (ms) eld, double-click and enter a proper value of protection
delay time.
NOTE
n Protection Delay Time: The amount of time to wait before switching takes place after the protection
condition is detected in an RPR ring. After the protection delay time elapses, if the protection
condition persists, the RPR switching is carried out. If the protection condition stops after a timeout,
the RPR switching is not carried out.
n The time unit is ms.
Step 4 Click the Protection mode drop-down list and select a protection mode.
NOTE
n Wrapping: When a fault occurs on the ring, wrapping is performed automatically on the node close
to the failure point. That is, Ring 0 and Ring 1 are connected. Wrapping has a short response time,
which lessens frame loss when fault occurs but takes relatively more bandwidth.
n Steering: When a fault occurs on the ring, the protection information including failure point and
fault type is sent to each node, and the topology also changes correspondingly. The source node only
needs to send data to the destination node according to the new topology. The small part of data
that have been sent will be discarded at the failure point. Steering protection effectively improves
utilization of ring bandwidth and allows signals to be transmitted on the best route. However, it takes
a longer time to trigger the switching process, and a new route needs to be decided according to the
new topology after the topology becomes stable.
n Wrap and Steering: Wrapping is rst performed to avoid packet loss. Steering is then performed
after the topology becomes stable. In this way, the service interruption duration is less than or
equal to 50ms.
Step 5 Click the Revertive drop-down list and select a switching revertive condition.
NOTE
n In the Revertive mode, services revert back to the working path after the working path returns
to normal.
n In the Non-Revertive mode, services do not revert back to the working path after the working
path returns to normal.
Step 6 Double-click in the Protection Timing (ms) eld, and enter a proper value.

NOTE
n There are the fast, slow and WTR timers in the RPR protection protocol. The fast and the slow timers
are used to send TP message, whereas the WTR timer is used for protection switching reversion.
The value specied here is for the slow timer, and the time unit is ms. The value of the fast timer is
xed to 10 ms.
n When the protection information changes, the protection protocol sends eight TP messages by using
the fast timer, to notify other nodes on the ring of the changed protection information. After that,
the protection protocol switches to the slow timer to sends TP messages, to reduce the utilization of
bandwidth.
Step 7 Double-click in the Protection wait-to-restore (s) eld, and enter a proper value.
NOTE
n When a node in SF or SD condition detects that the protection condition no longer exists, it keeps the
protection switching state instead of switching back to the normal state immediately. The node is
now in the wait-to-restore (WTR) state and will be in this state for the period of time that you specify
in the Protection wait-to-restore time (s) eld. After a timeout occurs, the node changes from the
WTR state to the normal state, and the services on the ring resume accordingly.
n The time unit is in seconds.
Step 8 Click Apply.

A prompt appears telling you that the parameters for the RPR ring are modied successfully.
----End
9.11.4 Adjusting Link Bandwidth of an RPR Ring

Prerequisites
n Link capacity adjustment scheme (LCAS) must be enabled.
Procedure
Step 1 In the NE Explorer, select the appropriate Ethernet board and select Conguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select Internal Port
and then the LCAS tab.
Step 2 Set Enabling LCAS to Enabled for the source VCTRUNK port of the RPR link.
Step 3 Click to switch to the sink NE of the RPR link.

Step 5 Set Enabling LCAS to Enabled for the sink VCTRUNK port of the RPR link.
Step 6 Select Conguration > RPR Ring > Management from the Main Menu. Select the Link
Information tab.
Step 7 Select the link for which you wish to adjust capacity from the link list, right-click and select
Adjust Link bandwidth. The Add Link Member dialog box is displayed.
Step 8 Check the Selected check box, to select or deselect a channel for the RPR link.

NOTE
The trunk link is bidirectional. Therefore, if you adjust the capacity of Ring 0 link for a span of the RPR
ring network, Ring 1 link is also adjusted. If Ring 1 link is adjusted, Ring 0 link is also adjusted.
Step 9 Click OK. The Operation Result dialog box is displayed, indicating the link bandwidth is
successfully adjusted for the RPR ring network.
----End

Operator Guide 10 Conguring SDH Services in the End-to-End Mode
10
Conguring SDH
Services in the End-to-End Mode
About This Chapter

In the end-to-end conguration mode, you can congure SDH services of the VC12, VC3,
3*AU3, VC4 and VC4-Xc levels very quickly. During the end-to-end conguration, you need
only to specify the source and sink for the service, and then the T2000 automatically calculates
the route and creates the service for each NE on the route. The end-to-end conguration mode
is also called the trail management function.
Prerequisite
The trail management license must be provided for the T2000.
Context
The T2000 supports the following SDH trail management functions:
10.1 Principles for SDH Trail Creation

When conguring SDH services station by station, the process is very complicated and
operation errors easily occur. Therefore, the trail management function is recommended
for trail creation.
10.2 Searching for SDH Trails
After the SDH trail search, the congured SDH services on each NE are displayed in the
T2000 in an end-to-end fashion. In this way you can view the routes and resources occupied
by each service in an intuitive manner.
10.3 Creating VC4 and VC4-Xc Trails
If you want to create SDH services of the E4, STM-1 and VC4-Xc levels, you can complete
the service conguration quickly by creating end-to-end VC4 and VC4-Xc trails.
10.4 Creating VC12 and VC3 Trails
If you want to create SDH services of the VC12 and VC3 levels, you can complete the service
conguration quickly by creating end-to-end VC12 and VC3 trails.
10.5 Creating an SDH Trail Manually
Due to the limitation with respect to the calculation of trail routes and insufcient support for
complex networking, you can manually create a trail in order to create an end-to-end trail.
Skilled personnel can perform both the operations in the same window.
10.6 Conguring Trail Overheads
If you want to maintain or monitor the trails, you can set the trail overhead bytes.
10.7 Viewing SDH Trails
By viewing SDH trails, the network administrator is able to know about the trail details such as
the working status and source and sink ports.
10.8 Deleting SDH Trails
The deletion of needless SDH trails releases relevant network resources.

10 Conguring SDH Services in the End-to-End Mode Operator Guide
10.9 Modifying Trail Names in Batches

The network administrator can set the trail naming rules and modify trail names in batch
according these rules.
10.10 Changing Between SNCP and Normal Trails
Under such conditions as a protection subnet change, you can change normal trails to SNCP
trails and vice versa by following the process below. This change does not interrupt the service.
10.11 Joining and Splitting VC4 Server Trails
A VC4 server trail is used only to carry the services between the source and sink NEs, and
cannot be used by any intermediate NEs between the source and sink NEs. If you want to
change the source and sink NEs of a congured VC4 server trail, you can use the joining and
splitting functions.
10.12 Conguring the Handover Plan
With the handover plan, you can precongure a trail (namely precongured trail) for an
active trail. When the trail handover begins, the T2000 is able to switch the services on the
active trail to the precongured trail very quickly, and at the same time release the resources
occupied by the active trail.
10.13 Conguring Preconguration Groups
With a preconguration group, the services on the active trail can be switched to the
precongured trail quickly upon an active trail fault. Thus the preconguration group enables
the node failure protection. When the active trail recovers, the services can still be switched
back from the precongured trail to the active trail.

10.1 Principles for SDH Trail Creation

When conguring SDH services station by station, the process is very complicated and
operation errors easily occur. Therefore, the trail management function is recommended
for trail creation.
Restrictions for VC4 Server Trail Creation
n On a unidirectional MSP ring, you can create only unidirectional VC4 server trails. While
across a unidirectional ring, you can create bidirectional VC4 server trails.
n On a PP ring, the created VC4 server trail must form a closed loop and use the same VC4
timeslot. Otherwise VC12 and VC3 trails cannot be created.
n When the VC4 server trail transits multiple protection subnets, the trail source and sink
cannot be on a PP ring or an MSP ring.
n If the VC4 server trail transits a DNI structure, the trail source and sink cannot be on a
ring that includes the DNI structure.
n If a trail transmits multiple server trails, lower order cross-connection is adopted on joint
NEs and terminal NEs of server trails. Therefore, the server trails must be properly
planned on VC4 pass-through NEs. Otherwise, lower order cross-connect resources
will be badly consumed.
n For a non-convergence VC4 server trail, the source and sink cannot be those NEs without
lower order cross-connection support, for example, the OptiX 10G (Metro 5000) and the
OptiX OSN 9500 without lower order cross-connection protection groups congured.
For a convergence VC4 server trail, only one end (instead of both) can be an NE without
lower order cross-connection support.
Principles for VC12 and VC3 Trail Creation
n Before creating VC12 and VC3 trails, the VC4 server trail must be created in the desired
VC 12 or VC3 trail direction.
n The VC12 and VC3 trails are created based on the VC4 server trail and adopts the same
protection scheme as that (if any) of the VC4 server trail.
n When selecting the timeslot, use space division cross-connection whenever possible. If
space division cross-connection is not supported, the use time division cross-connection.
n When creating a trail, the T2000 selects the same VC4 timeslot for each NE by default.
If the same VC4 timeslot is not available on some NEs, the T2000 selects the timeslot
numbered the smallest. The timeslot selection can be modied manually.
n When creating VC12 and VC3 trails, the T2000 selects the same lower order timeslot
within a subnet when possible. The timeslot selection can be modied manually.
n For pass-through services on a PP ring, the positive and negative directions must have
the same VC4 and lower order timeslots settings. For dual-feed and selective-receive
services, the eastbound and westbound directions must have the same VC4 and lower
order timeslots settings.
n Before creating VC12 and VC3 trails on a unidirectional MSP ring or PP ring, the VC4
server trail must be created. The VC4 server trail must form a loop and use the same VC4
timeslot. On a unidirectional MSP ring, no extra trails except those for the working
services can be created.
n To create VC12 and VC3 trails on a bidirectional PP ring, the created VC4 server trail
must form a loop and use the same VC4 timeslot.
10.2 Searching for SDH Trails

After the SDH trail search, the congured SDH services on each NE are displayed in the
T2000 in an end-to-end fashion. In this way you can view the routes and resources occupied
by each service in an intuitive manner.
Prerequisite

Context
Searching for SDH trails includes:
10.2.1 Searching for SDH Trails

After a new network is set up or services are congured station by station, you need to perform
an SDH trail search so that you can manage congured services with the trail management
function.
10.2.2 Discrete Service
After the trail search on the T2000, the services that do not form trails are called discrete
services.
10.2.3 Discrete Service Causes and Handling Measures
After the trail search, discrete services are usually caused by the following factors: unsatised
trail search conditions, T2000 trail search restrictions, incomplete or wrong conguration of
cross-connections, and existence of SDH NNI services.
10.2.1 Searching for SDH Trails

After a new network is set up or services are congured station by station, you need to perform
an SDH trail search so that you can manage congured services with the trail management
function.
Prerequisites
n The license for the trail management function must be provided.
n NE data must be uploaded to the T2000.
n Fiber connections between the NEs must be created correctly.
Context
NOTE
The search only updates the trail information at the network layer on the T2000. Neither the service
operation nor conguration data of the NE will be affected by the search.
Procedure
Step 1 Select Trail > SDH Trail Search from the Main Menu. The SDH Trail Search wizard is
displayed.
Step 2 Click Next to start the trail search.
NOTE
If the end-to-end trail cannot be formed due to the conict of cross-connections, the information about
the cross-connections in conict will be displayed. The search can only be continued after deleting
the conicting trails.
Step 3 The search process will last for some time, with the specic duration depending on the service
volume. Wait until the search is complete as indicated by the progress bar, and then click
Next to view the trail information.
Step 4 Select a trail and right-click to set the management ag.
NOTE
The management ag indicates whether the trail is included in the network trail management. The trail is
under management by default. If you exclude the trail from the network trail management, you can also
manage cross-connections of single NEs during station-by-station service conguration.
Step 5 Click Next and the trails searched out without management ags will be deleted from the
network layer by the T2000. This operation does not affect the NE services or the NM data

of single NEs. Then you can view all discrete services (that is, the cross-connections that
cannot form trails) in the network.
----End
10.2.2 Discrete Service

After the trail search on the T2000, the services that do not form trails are called discrete
services.
Impacts of Discrete Services

When a service is found to be a discrete service, it does not indicate that the service cannot run
properly on the NE. Discrete services have the following impacts on network conguration
and management:
n On Trail Conguration In end-to-end service conguration (by trail), when selecting the
source, sink, route and timeslot of a trail, the T2000 regards the timeslots occupied by
discrete services as free timeslots and may allocate them to other services. Thus the trail
creation will fail. In this case, the T2000 prompts "Timeslot conicted".
If there are lots of discrete services, the success probability of trail creation on the T2000
will be lowered.
n On Trail Resource Query If not all trails are found, the trail query result for a tributary
board may also be incomplete. Trail resources cannot be queried correctly by using
the trail management function.
n On Other Systems Due to the incomplete trail search result, the resource statistics
provided by the T2000 is not accurate and thus cannot serve as a data source for other
systems (such as the service products, including the NMS for VIP customers, the resource
system, the performance analysis system, and the network assessment system).
n On Timeslot Allocation Diagram The timeslot allocation diagram of the T2000 is based
on trails. Only when there are trails on a node in the protection subnet, trail timeslots
used on this node are displayed in the timeslot allocation diagram. The timeslots used by
discrete services cannot be displayed in the timeslot allocation diagram.
n For services that are found to be non trails, the trail-based management and
troubleshooting are not available on the T2000.
n Some discrete services may be needless and thus waste the network resources.
10.2.3 Discrete Service Causes and Handling Measures

After the trail search, discrete services are usually caused by the following factors: unsatised
trail search conditions, T2000 trail search restrictions, incomplete or wrong conguration of
cross-connections, and existence of SDH NNI services.
What Causes Discrete Services

1. Unsatised trail search conditions
n The data on the T2000 are inconsistent with those on NEs.
n The bers created on the T2000 do not match actual ber connections.
n Protection subnets are not created or cannot be searched out.
n The NE data conguration is improper. For example, a non-protection chain service
is created on the protection ring, the NE logic system of the service does not belong
to any protection subnet, or the protection subnet conguration is wrong.
2. T2000 trail search restrictions
n If between two NEs the VC4 server trail is created but the lower order (VC12 and
VC3) trails are not created, services are not sent to NEs. In this case, when another
T2000 performs the trail search on these two NEs, the VC4 server trail cannot be
searched out.

n For a VC4 server trail with multiple sources and multiple sinks, if some sources or
sinks are on SDH NNIs and others are on common optical and electrical interfaces,
the trail cannot be searched out.
3. Incomplete or wrong conguration of cross-connections
n The timeslot for the protection route is not congured. This often happens in a
PP or SNCP protection subnet.
n The timeslot congured for the protection route is wrong.
n The SNCP service conguration is wrong, which results in an incomplete protection
route. The conguration methods for SNCP services are different on version 4.0 and
5.0 NEs. For this reason, the wrong SNCP services may have been congured.
n The service conguration is incomplete. Check whether incomplete services are
congured in the station-by-station mode, for example, pass-through services may
not be congured on pass-through NEs. Complete such service conguration and
then re-search for the trails.
4. Existence of SDH NNI services If there are SDH NNI services on the network, but
SDH NNIs are not created or SDH NNI services pass through within the network, the
cross-connections congured on each NE cannot be searched out as trails. The Figure
10-1 is an example.
Figure 10-1 SDH NNI Services
The T2000 manages NE1 through NE4, but is not able to manage T1 through T3 (other
vendors’ equipment). NE1 and NE2 have the S1 and S2 services to T1 respectively.
There is also the S3 service between T2 and T3.
For the above three services to be searched out as trails, you need to do the following:
For the S1 service, create the SDH NNI on NE2 and then perform the trail search. In
this way, the cross-connections on NE1 and NE2 can be searched out as a trail between
NE1 and NE2.
For the S2 service, create T1 as a preconguration NE or a version 5.0 virtual NE,
create the ber between T1 and NE2, and then create the subnet consisting of T1 and
NE2. Congure the single-station service on T1 in association with the service on NE2.
Perform the trail search and the trail between NE1 and T1 will be searched out.
For the S3 service, create T2 and T3 as preconguration NEs or version 5.0 virtual NEs,
create the bers between T2/T3 and NE4, and then create the subnet consisting of T2,
NE4 and T3. Congure single-station services on T2 and T3 respectively. Perform the
trail search and the trail between T2 and T3 will be searched out.
Handling Discrete Services

1. Perform a consistency check to check whether the data on the T2000 and those on NEs
are consistent or not. If not, upload the conguration data to the T2000.
2. Verify that the ber connections created on the T2000 are consistent with actual ber
connections, and that there are no errors like wrong ber connection on the T2000.
3. Search for protection subnets. Verify that all protection subnets are searched out. Check
whether the parameters for protection subnets and the logical system of each node are set
correctly, and whether SDH NNIs are created for SDH NNI services.
4. Perform a trail search on the T2000.
5. If discrete services are found, analyze and handle them according to the causes displayed
on the T2000 and the handling measures given above. You are recommended to handle

the discrete services at add/drop tributaries rst, then those SDH NNI discrete services,
and at last those pass-through discrete services.
How to Avoid Discrete Services

Use the trail management function whenever possible to congure services because services
congured in this way will not form discrete services. When a discrete service is found, handle
it as soon as possible so that it does not affect subsequent service conguration.
10.3 Creating VC4 and VC4-Xc Trails

If you want to create SDH services of the E4, STM-1 and VC4-Xc levels, you can complete
the service conguration quickly by creating end-to-end VC4 and VC4-Xc trails.
Context
The creation methods for SNCP trails and non-SNCP trails are different as follows:
10.3.1 Setting an SDH Optical Interface as an SDH NNI

For version 4.0 NEs, SDH optical interfaces can be set to SDH NNIs only manually. If the
source and sink of a VC4/VC4-Xc trail are SDH optical interfaces, such optical interfaces
must be SDH NNIs.
10.3.2 Creating a Non-SNCP VC4/VC4-Xc Trail
By creating an end-to-end VC4/VC4-Xc trail, you can create an E4/STM-1/VC4-Xc SDH
service without SNCP quickly. In different protection subnets, the methods for creating a
non-SNCP VC4/VC4-Xc trail are the same.
10.3.3 Creating an SNCP VC4/VC4-Xc Trail
service with SNCP quickly. In different protection subnets, the methods for creating an SNCP
VC4/VC4-Xc trail are the same.
10.3.1 Setting an SDH Optical Interface as an SDH NNI

For version 4.0 NEs, SDH optical interfaces can be set to SDH NNIs only manually. If the
source and sink of a VC4/VC4-Xc trail are SDH optical interfaces, such optical interfaces
must be SDH NNIs.
Prerequisite
Context
NOTE
For version 4.0 NEs, including the OptiX 155/622H (Metro 1000), the OptiX 155/622, the OptiX 2500+
(Metro 3000) and the OptiX Metro 3100, you must create SDH NNIs manually. For version 5.0 NEs, if
an SDH optical interface is not congured with ber connection on the T2000, the interface is an SDH
NNI by default. If the interface is congured with ber connection instead, the interface is not an SDH
NNI and thus cannot be used as the source or sink port for a VC4/VC4-Xc trail.
Procedure
Step 1 Click an NE in the Protection View and select SDH NNI Management. The SDH NNI
Management interface is displayed.
Step 2 In Uncreated Optical Interface, select an optical interface and click . The
optical interface is added to Created Optical Interface.
Step 3 Click Close.

----End
10.3.2 Creating a Non-SNCP VC4/VC4-Xc Trail

service without SNCP quickly. In different protection subnets, the methods for creating a
non-SNCP VC4/VC4-Xc trail are the same.
Prerequisites
n A protection subnet and the SDH NNIs must be created for version 4.0 NEs, including the
OptiX 155/622H (Metro 1000), the OptiX 155/622, the OptiX 2500+ (Metro 3000) and
the OptiX Metro 3100.
Context
n When creating the VC4/VC4-Xc trail, you do not need to create a server trail.
n If the source and sink ports of the VC4/VC4-Xc trail are optical interfaces, such optical
interfaces must be SDH NNIs. For version 4.0 NEs, including the OptiX 155/622H
(Metro 1000), the OptiX 155/622, the OptiX 2500+ (Metro 3000) and the OptiX Metro
3100, you must create SDH NNIs manually. For version 5.0 NEs, if an SDH optical
interface is not congured with ber connection, the interface is an SDH NNI by default.
If this optical interface is congured with ber connection instead, the interface is not an
SDH NNI and thus cannot work as the source or sink port for the VC4/VC4-Xc trail.
Procedure
Step 1 Select Trail > SDH Trail Creation from the Main Menu.
Step 2 Set the service direction according to the protection subnet type. Set the service level to
VC4 or VC4-Xc.
Step 3 Set the Resource Usage Strategy and Protection Priority Strategy.
NOTE
Pay attention to the requirement of parameters:
n Resource Usage Strategy denes the protection subnet resources or timeslots available during trail
creation. The values are Protected Resource, Extra Resource and All Resource.
n Protection Priority Strategy denes the protection subnet resources to be selected rst during trail
creation. The values are Trail Protection First, SNCP First and NP First.
Step 4 Double-click the source NE and the sink NE in turn. Select the port in the Select Board
Port dialog box and click OK. The automatically selected trail is displayed between the
source and sink NEs.
Step 5 Optional: Click a server trail between the NEs to specify the included route. The route will be
displayed in pink. Click the trail again to cancel the selection and then the trail turns gray.

Step 6 Optional: Double-click another NE in this protection subnet to specify the excluded nodes
for the trail. The selected NE will be marked with a sign (double-click the NE again to
cancel the selection).
Step 7 Optional: Click Set Route Timeslot. The Set Route Timeslot dialog box is displayed.
Select the timeslot and click OK.
Step 8 Optional: If the trail passes through an ASON domain, you can check the SPC First check
box and click ASON Attributes Settings to set the Attributes and Class parameters.
Step 9 Set the trail attributes such as Name and ID.
Step 10 Optional: Click the Maintenance Congurationtab to set the alarm reversion.
Step 11 Optional: Check the Activate the trail check box.
Step 12 Optional: If you want to create multiple trails with the same route, check the Copy after
Creation check box.
Step 13 Click Apply. A prompt appears telling you that the operation was successful. Click Close.
----End
10.3.3 Creating an SNCP VC4/VC4-Xc Trail

service with SNCP quickly. In different protection subnets, the methods for creating an SNCP
VC4/VC4-Xc trail are the same.
Prerequisites
n An SNCP protection subnet and the SDH NNIs must be created for version 4.0 NEs,
including the OptiX 155/622H (Metro 1000), the OptiX 155/622, the OptiX 2500+
(Metro 3000) and the OptiX Metro 3100.
Context
n When creating the VC4/VC4-Xc trail, you do not need to create a server trail.
n If the source and sink ports of the VC4/VC4-Xc trail are optical interfaces, such optical
interfaces must be SDH NNIs. For version 4.0 NEs, including the OptiX 155/622H
3100, you must create SDH NNIs manually. For version 5.0 NEs, if an SDH optical
interface is not congured with ber connection, the interface is an SDH NNI by default.
If this optical interface is congured with ber connection instead, the interface is not an
SDH NNI and thus cannot work as the source or sink port for the VC4/VC4-Xc trail.
Procedure
Step 2 Set the service direction to Unidirectional and the level to VC4 or VC4-Xc.
Step 3 Set the resource usage strategy to Protected Resource and the protection priority strategy
to SNCP First.
NOTE

Step 4 Double-click the source NE and the sink NE in turn. Select the port in the Select Board
Port dialog box and click OK. The automatically selected trail is displayed between the
source and sink NEs.
displayed in pink. Click the trail again to cancel the selection and then the trail turns gray.
Step 7 Click Set Route Timeslot. The Set Route Timeslot dialog box is displayed. Select the
timeslot and click OK.
NOTE
If you do not assign the timeslot, the rst available timeslot will be selected automatically.
Step 8 Click the SNCP setting tab. Right-click the dual-feed point and select Set Dual-Feed Point,
and the node is displayed as . Right-click the selective-receiving point and select Set
Selective-Receiving Point, and the node is displayed as .
Step 9 Optional: If the trail passes through an ASON domain, you can check the SPC check box and
click ASON Attributes Settings to set the Attributes and Class parameters.
Step 11 Optional: Click the Maintenance Congurationtab to set the alarm reversion parameter.
Creation check box.
----End
10.4 Creating VC12 and VC3 Trails

If you want to create SDH services of the VC12 and VC3 levels, you can complete the service
conguration quickly by creating end-to-end VC12 and VC3 trails.
Context
The creation methods for SNCP trails and non-SNCP trails are different as follows:
10.4.1 Creating a VC4 Server Trail

A VC4 server trail is used to carry the VC12 and VC3 trails between the NEs. Before creating
a VC12 or VC3 trail, you need to create a VC4 server trail between the NEs.

10.4.2 Creating a Non-SNCP VC12/VC3 Trail

By creating an end-to-end VC12/VC3 trail, you can create an E1/T1 or E3/T3 SDH service
without SNCP quickly. In different protection subnets, the methods for creating a non-SNCP
VC12/VC3 trail are the same.
10.4.3 Creating an SNCP VC12/VC3 Trail
with SNCP quickly. In different protection subnets, the methods for creating an SNCP
10.4.1 Creating a VC4 Server Trail

A VC4 server trail is used to carry the VC12 and VC3 trails between the NEs. Before creating
a VC12 or VC3 trail, you need to create a VC4 server trail between the NEs.
Prerequisites
n A protection subnet must be created for version 4.0 NEs, including the OptiX 155/622H
3100.
n The OptiX 10G (Metro 5000) NE must have the AMXS， EMXS or ETXC board where
the low order cross-connection protection pairs are created.
n The OptiX OSN 9500 NE must have the GXCL or EXCL board where the lower order
cross-connection protection pairs are created.
Context
A VC4 server trail is used only to carry services between the source and sink NEs, and cannot
used by any intermediate NEs. For the convenience of bandwidth use, therefore, VC4 server
trails are usually created between two adjacent NEs, instead of between two NEs that have
intermediate NEs. Before deleting a VC4 server trail, you need to delete its lower order trail.
Procedure
Step 2 Set the service direction to Bidirectional and level to VC4 Server Trail.
Step 3 Set the Resource Usage Strategy and Protection Priority Strategy parameters.
NOTE
Step 4 Double-click the source NE and the sink NE in turn. The automatically selected route is
displayed between the NEs.
displayed in pink. Click the trail again to cancel the selection and then the trail turns green.

Step 7 Click Set Route Timeslot. The Set Route Timeslot dialog box is displayed. Select the
timeslot and click OK.
Step 8 Set the trail attributes such as Name, ID and Remarks.
Step 9 Optional: Click the Maintenance Conguration tab to set the alarm reversion parameter.
Creation check box.
----End
10.4.2 Creating a Non-SNCP VC12/VC3 Trail

without SNCP quickly. In different protection subnets, the methods for creating a non-SNCP
Prerequisites
n The VC4 server trail is created between the source and sink NEs, and free timeslots are
available on the VC4 server trail.
Procedure
Step 2 Select the service direction according to the protection subnet type. Set the service level to
VC12 or VC3.
Step 3 Congure the Resource Usage Strategy and Protection Priority Strategy.
NOTE
Step 4 Double-click the source NE and the sink NE in turn. Select the port in the Select Board Port
dialog box and click OK. The automatically selected trail is displayed between the NEs.

Creation check box.
----End
10.4.3 Creating an SNCP VC12/VC3 Trail

with SNCP quickly. In different protection subnets, the methods for creating an SNCP
Prerequisites
n The VC4 server trail is created between the source and sink NEs, and free timeslots are
available on the VC4 server trail.
n For version 4.0 NEs, including the OptiX 155/622H (Metro 1000), the OptiX 155/622,
the OptiX 2500+ (Metro 3000) and the OptiX Metro 3100, an SNCP protection must be
congured. The dual-feed and selective-receive points must be on the ring.
Procedure
Step 2 Set the service direction to Unidirectional and the level to VC12 or VC3.
Step 3 Set the resource usage strategy to Protected Resource and the protection priority strategy
to SNCP First.
NOTE

Step 4 Double-click the source NE and the sink NE in turn. Select the port in the Select Board Port
dialog box and click OK. The automatically selected trail is displayed between the NEs.
NOTE
If you do not assign the timeslot, the rst available timeslot will be selected automatically.
Step 8 Click the SNCP setting tab. Right-click the dual-feed point and select Set Dual-Feed Point,
and the node is displayed as . Right-click the selective-receiving point and select Set
Selective-Receiving Point, and the node is displayed as .

Step 10 Optional: Click the Maintenance Conguration tab to set the alarm reversion parameter.
Creation check box.
----End
10.5 Creating an SDH Trail Manually

Due to the limitation with respect to the calculation of trail routes and insufcient support for
complex networking, you can manually create a trail in order to create an end-to-end trail.
Skilled personnel can perform both the operations in the same window.

Prerequisites
n The optical ber at the server layer must be created.
n The VC4 server trail must be created before creating a VC12 or VC3 trail.
Procedure
Step 1 Select Trail > SDH Trail Create Manually from the Main Menu.
Step 2 Select the Direction and Level for the service.
NOTE
If you want to create a broadcast trail, set the value of Direction to Unidirectional.
Step 3 Select the source and sink NEs for the trail to be created.
NOTE
Right-click an NE in the Trail View and select Select Source/Select Sink from the shortcut menu to
designate this NE as the source/sink. Or clickBrowse to designate the source and sink NEs for the trail.
Step 4 Optional: Select route computation policy.
NOTE
n In the Calculate Route pane, select Normal reverse route or Reverse route between cross-ring
nodes. The T2000 automatically creates the negative route according to the positive route manually
created by the user.
n In the Calculate Route pane, click Calculate Route. The T2000 automatically computes the route
between the source and sink nodes.
Step 5 Specify the route.
NOTE
Click a route in the Trail View, and available trails on this route are displayed the lower-right Set Route
Timeslot pane. Set the Direction, Timeslot and Route Type parameters for the trail. Click Add and the
trail is displayed in the Selected Route. Or you can click Delete to delete routes from the Selected Route.
Step 6 Repeat Step 4 to specify the route segment by segment.

Step 7 Optional: For a bidirectional trail, you can specify the negative working and protection routes.
Step 8 Complete the route information, such as Name, ID, Customer and Remarks.
Step 9 Optional: Check the Activated check box.
NOTE
When the Activated check box is checked, the trail conguration will be sent to the NE. Otherwise, the
trail conguration remains only at the T2000 side.
Step 10 Optional: If you want to reverse alarms on the trail, you can check the Alarm Reversion
check box.
Step 11 Click Apply.
----End
10.6 Conguring Trail Overheads

If you want to maintain or monitor the trails, you can set the trail overhead bytes.

Context
Set the following trail overheads:
10.6.1 Conguring the Trace Byte for a Trail

The trace byte is used for the receive end to conrm the continuous connection status with the
transmit end. Between equipment of the same vendor, the trace byte can be set to any same
characters. Between equipment of different vendors, the trace byte must be set to the same
characters that are previously agreed, so that the interconnection can be successful.
10.6.2 Conguring the C2 Byte for a Trail
The C2 byte indicates the multiframe structure of VC frames and the type of bearer services
(for example, PDH services or ATM services).
10.6.3 Setting Overhead Termination for a Trail
Overhead termination means SDH equipment processes and terminates the received overhead
signals, and sends the recreated (or default) overhead signals to another optical board at the
opposite end.
10.6.1 Conguring the Trace Byte for a Trail

The trace byte is used for the receive end to conrm the continuous connection status with the
transmit end. Between equipment of the same vendor, the trace byte can be set to any same
characters. Between equipment of different vendors, the trace byte must be set to the same
characters that are previously agreed, so that the interconnection can be successful.
Prerequisites
n Trails must be created and activated.
Procedure
Step 1 Select Trail > SDH Trail Management from the Main Menu. The Set Trail Browse Filter
Conditions dialog box is displayed.
Step 2 Set the lter conditions and click Filter All. The trails are displayed in the list.
NOTE
Filter All is to refresh and display all qualied trails. Secondary Filter is to lter in the trails that
are already displayed. Incremental Filter is to add new qualied trails to the list without refreshing
the trails that are already displayed.
Step 3 Select a trail and its detailed information is displayed in the lower portion of the user interface.
Step 4 Click Maintenance and select Trace Byte. The Set Overhead dialog box is displayed.
Step 5 Double-click Byte to be sent and Byte to be received to modify. Click Apply.

NOTE
You can click Switch Mode to select a overhead processing mode.
Step 6 Click Yes to conrm the operation. A prompt appears telling you that the operation was
successful. Click Close.
----End
10.6.2 Conguring the C2 Byte for a Trail

The C2 byte indicates the multiframe structure of VC frames and the type of bearer services
(for example, PDH services or ATM services).
Prerequisites
Procedure
NOTE
Step 4 Click Maintenance and select C2 Byte. The Set Overhead dialog box is displayed.
Step 5 Double-click Byte to be Sent and Byte to be Received to modify. Click Apply.

NOTE
You can click Change Switching Mode to select a overhead processing mode.
----End
10.6.3 Setting Overhead Termination for a Trail

Overhead termination means SDH equipment processes and terminates the received overhead
signals, and sends the recreated (or default) overhead signals to another optical board at the
opposite end.
Prerequisites
Procedure
NOTE

Step 4 Click Maintenance and select Overhead Termination. The Set Overhead dialog box is
displayed.
Step 5 Select the overhead status and click Apply.
NOTE
You can click Switch Mode to select a overhead processing mode.
----End
10.7 Viewing SDH Trails

By viewing SDH trails, the network administrator is able to know about the trail details such as
the working status and source and sink ports.
Prerequisites
n You must be an NM user with "NE and network monitor" authority or higher.
n The SDH or PDH trail must be created.
Procedure
Step 2 Set the lter conditions.
Step 3 Click Filter All and the trails are displayed in the list.
NOTE

Step 5 Optional: Click Alarm or Performance to view the alarm or performance information of the
trail.
Step 6 Optional: Right-click a trail and select Query Relevant Client Trails from the shortcut menu.
Step 7 Optional: Right-click a trail and select Trail Use Information from the shortcut menu. The
Trail Use Information dialog box is displayed. For a VC4 server trail, you can also view the
information of associated VC3 and VC12 trails.
----End
10.8 Deleting SDH Trails

The deletion of needless SDH trails releases relevant network resources.
Prerequisites
n Make sure the SDH trail to be deleted is inactive.
n Make sure the SDH trail to be deleted does not carry any other SDH trail or trunk link trail.
Context
NOTE
The procedures for deleting server trails and client trails are basically the same. The difference is that,
before deleting a server trail, its client trails must be deleted rst. If the SDH trail to delete is already
used by a trunk link trail, you need to delete the trunk link trail rst.
Procedure
Step 1 Select Trail > SDH Trail Management from the Main Menu.
Step 2 Select one or more SDH trails to delete, and right-click and select Delete from the shortcut
menu.

NOTE
There are the following two schemes for trail deletion:
n Delete: Deletes trails at the NM side and relevant services at the NE side. Be careful when using
this scheme because it will affect the services.
n Delete from Network Layer: Deletes trails at the NM side only. This command is not issued to the
NE side and thus does not affect services. After the deletion, you can perform a trail search to nd
the trails again according the service information at the NE side.
If the trail to delete is activated, deactivate it before you delete it. If you attempt to delete the trail from
the network layer, you need not to deactivate the trail in advance.
Step 3 Click OK.

----End
10.9 Modifying Trail Names in Batches

The network administrator can set the trail naming rules and modify trail names in batch
according these rules.
Prerequisites
n The trail naming rules are set on the T2000.
Procedure
Step 2 After the trail ltering, trail attributes are displayed in the trail list.
Step 3 Select one or more trails from the list, right-click them and select Name from the shortcut
menu. The T2000 automatically modies the names of the selected trails according to the
naming rules.
Step 4 If you want to save the modied names, click OK. If you want to cancel the modications,
click Cancel.
----End
10.10 Changing Between SNCP and Normal Trails

Under such conditions as a protection subnet change, you can change normal trails to SNCP
trails and vice versa by following the process below. This change does not interrupt the service.
10.10.1 Changing the Non-SNCP Trail to the SNCP Trail

Under such conditions as a protection subnet change, you can change the non-SNCP trail to
the SNCP trail. This change does not interrupt the service.
10.10.2 Changing the SNCP Trail to the Non-SNCP Trail
Under such conditions as a protection subnet change, you can change the SNCP trail to the
non-SNCP trail. This change does not interrupt the service.
10.10.1 Changing the Non-SNCP Trail to the SNCP Trail

Under such conditions as a protection subnet change, you can change the non-SNCP trail to
the SNCP trail. This change does not interrupt the service.

Prerequisites
n The trail must be created.
Procedure
NOTE
Step 4 Click Maintenance and select Modify Port/Timeslot/Route.
Step 5 Click the SNCP Setting tab.
Step 6 Right-click the dual-feed point and select Set Dual-Feed Point, and the node is displayed as
. Right-click the selective-receiving point and select Set Selective-Receiving Point, and
the node is displayed as .
Step 7 Click OK. A prompt appears telling you that the operation was successful. Click Close.
----End
10.10.2 Changing the SNCP Trail to the Non-SNCP Trail

Under such conditions as a protection subnet change, you can change the SNCP trail to the
non-SNCP trail. This change does not interrupt the service.
Prerequisites
n The SNCP trail must be created.

Procedure
NOTE
Step 3 Select an SNCP trail and its detailed information is displayed in the lower portion of the
user interface.
Step 4 Click Maintenance and select Modify Port/Timeslot/Route.
Step 5 Click the SNCP Setting tab.
Step 6 Right-click a record of dual-feed and selective-receiving points in the Node List, and select
Delete from the shortcut menu.
----End
10.11 Joining and Splitting VC4 Server Trails

A VC4 server trail is used only to carry the services between the source and sink NEs, and
cannot be used by any intermediate NEs between the source and sink NEs. If you want to
change the source and sink NEs of a congured VC4 server trail, you can use the joining and
splitting functions.
Context
Figure 10-2 shows the joining and splitting of VC4 server trails.
Figure 10-2 Joining and Splitting VC4 Server Trails
There is only one VC4 server trail between NE1 and NE3. If you want to congure a VC12
or VC3 trail between NE1 and NE2 or between NE2 and NE3, you can split Trail 1 into
two VC4 server trails, that is, Trail 2 and Trail 3. On the contrary, you can join Trail 2 and
Trail 3 as Trail 1.
Join and split VC4 server trails by the process below:

10.11.1 Joining VC4 Server Trails

An NE has two VC4 server trails for which the NE functions as the source for one trail and the
sink for the other trail. The two trails carry lower order services that pass through the NE. You
can combine the two trails in to a VC4 server trails. The joining process deletes the lower order
VC4 services that pass through the NE and creates higher order pass-through services at the
same time. After the two VC4 server trails are joined, the VC4 server trail that passes through
the NE does not use lower order cross-connections, and thus the lower order cross-connect
resources on the NE that the trail passes through are saved.
10.11.2 Splitting a VC4 Server Trail
Splitting is the inverse process of joining. During the process of splitting, the VC4 server
trail that passes through an NE is split in to two VC4 server trails. The NE functions as the
source for one VC4 server trail and the sink for the other VC4 server trail. The splitting
process deletes the higher order VC4 services that pass through the NE and creates lower order
pass-through services at the same time. The split two trails carry lower order services that
add or drop from the NE.
10.11.1 Joining VC4 Server Trails

An NE has two VC4 server trails for which the NE functions as the source for one trail and the
sink for the other trail. The two trails carry lower order services that pass through the NE. You
can combine the two trails in to a VC4 server trails. The joining process deletes the lower order
VC4 services that pass through the NE and creates higher order pass-through services at the
same time. After the two VC4 server trails are joined, the VC4 server trail that passes through
the NE does not use lower order cross-connections, and thus the lower order cross-connect
resources on the NE that the trail passes through are saved.
Prerequisites
n The trails to be joined are not carrying lower order services that are added/dropped at
the joining NE.
n All lower order services carried by one trail must be able to pass through to the other trail.
Context
CAUTION
During the joining, services will be interrupted.
The lower order services carried by the trails to be joined cannot be added/dropped at the
joining NE. Otherwise the trails cannot be joined. See the following Figure 10-3. VC4 server
trails 1 and 2 cannot be joined due to the existence of VC12 trail 1.
Figure 10-3 Restrictions on VC4 Server Trail Joining
The two trails can be joined only when all lower order services carried by one trail are able
to pass through to the other trail. The timeslots for the two trails can be different. See the
following Figure 10-4. If any of VC12 trails 1 and 2 exists, VC4 server trails 1 and 2 cannot
be joined.

Figure 10-4 Restrictions on VC4 Server Trail Joining
Procedure
Step 1 Right-click the desired NE in the Trail View and select Join VC4 Server Layer Trails from
the shortcut menu. The Join VC4 Server Trails dialog box is displayed.
Step 2 Select the trail numbers and click Join. If there are several available trails, select the desired
two.
Step 3 Enter the name of the joined trail and click OK. A prompt appears telling you that the
operation was successful.
----End
10.11.2 Splitting a VC4 Server Trail

Splitting is the inverse process of joining. During the process of splitting, the VC4 server
trail that passes through an NE is split in to two VC4 server trails. The NE functions as the
source for one VC4 server trail and the sink for the other VC4 server trail. The splitting
process deletes the higher order VC4 services that pass through the NE and creates lower order
pass-through services at the same time. The split two trails carry lower order services that
add or drop from the NE.
Prerequisites
n The splitting NE has sufcient lower order cross-connect resources.
Context
CAUTION
During the splitting, services will be interrupted.
Procedure
Step 1 Right-click the desired NE in the Trail View and select Split a VC4 Server Layer Trail from
the shortcut menu. The Split a VC4 Server Trail dialog box is displayed.
Step 2 Select the trail to split and click Split.
Step 3 Enter the names of the split trails and click OK. A prompt appears telling you that the
operation was successful. Click Close.
----End

10.12 Conguring the Handover Plan

With the handover plan, you can precongure a trail (namely precongured trail) for an
active trail. When the trail handover begins, the T2000 is able to switch the services on the
active trail to the precongured trail very quickly, and at the same time release the resources
occupied by the active trail.
Context
Conguring the handover plan includes:
10.12.1 Creating Precongured Trails One by One

Use this procedure to create precongured trails one by one.
10.12.2 Creating Precongured Trails in Batches
Use this procedure to create precongured trails in batches at the port level, board level and
equipment level.
10.12.3 Deleting Handover Plans
Use this procedure to delete handover plans.

Prerequisites
n The license for SDH precongured trail management must be provided.
n When creating VC12 or VC3 trails, the related VC4 server trail must be created correctly
beforehand.
n Precongured trail creation only supports VC12, VC13, VC4, VC4-4C, VC4-8C,
VC4-16C, VC4-64C trails.
Context
CAUTION
All the services on the active circuit are deleted after the handover.
Procedure
Step 1 Creating a Handover Plan
1. Select Trail > SDH Precongured Trail Management from the Main Menu.
2. In the Preconguration Group pane, select New > Create Handover Plan.
3. Double-click a eld and set the value.
4. Click Apply. A prompt appears telling you that the operation was successful. Click Close.
Step 2 Adding Active Trails
1. Select the desired handover plan for which you want to create active trails and click Add
Active Trail. The Set Trail Browse Filter Conditions dialog box is displayed.
2. Set the lter conditions.
3. Click Filter All and the trails are displayed in the list.
NOTE
Filter All is to refresh and display all qualied trails. Secondary Filter is to lter in the trails
that are already displayed. Incremental Filter is to add new qualied trails to the list without
refreshing the trails that are already displayed.

4. Select a trail and click OK.

Step 3 Creating Precongured Trails One by One
1. Select the appropriate Handover Plan and Active Trail, select New > Create One by
One to navigate to the Create One by Onewindow.
2. Click Browseto specify the source and sink. In the Select Board Portdialog box
displayed, select the board and prot. Click OK.
3. ClickApply.
The Operation Result dialog box is displayed.
4. Click Close.
6. In the Active Trail pane, right-click an active trail and select Precongured Trails
7. In the Precongured Route Information dialog box, check whether the active and
precongured trails are created correctly.
NOTE
In the gure, the real line represents the active trail and the dashed line represents the precongured
trail.
Step 4 Cutting Over Circuits

1. In the Preconguration Group pane, right-click a handover plan and select Check
from the shortcut menu. A prompt appears telling you that the operation was successful.
Click Close.
NOTE
Check the conguration before the handover. If a dialog box is displayed prompting the operation
failed, check the service conguration and re-create the handover plan.
2. At the pre-set handover effective time, the Scheduled Handover Notication dialog box
is displayed notifying the user to cut over the circuit.
3. In the Preconguration Group pane, right-click a handover plan and select Handover
4. Click Yes in the prompt dialog box.
CAUTION
----End


equipment level.
Prerequisites
beforehand.
Context
CAUTION
Procedure
Step 1 Creating a Handover Plan
2. In the Preconguration Group pane, select New > Create Handover Plan.
Step 2 Creating Precongured Trails in Batches
1. Select the desired handover plan for which you want to create precongured trails in
batches. Select New > Create in Batches.
2. Set Level and Handover Plan.
NOTE
Note the following during parameter settings:
n If you select Port Level, you can select multiple ports on the board as handover objects.
n If you select Board Level, the system selects all the ports on the board as handover objects.
n If you select Equipment Level, the system selects all the ports on the equipment as handover
objects.
3. Double-click the destination sink NEs of before and after the handover in turn. Select
ports in the dialog box. Click OK.
NOTE
If an NE is selected as a handover object, you do not need to select board ports.
4. Double-click an NE to specify it as an excluded NE. The NE is displayed as

(double-click it again to cancel the selection).
5. Select the trail you want to handover. Click Finish. A prompt appears telling you that
the operation was successful. Click Close.
6. Click Cancel to exit the Create Precongured Trail in Batches interface.

NOTE
trail.
Step 3 Cutting Over Circuits

1. In the Preconguration Group pane, right-click a handover plan and select Check
from the shortcut menu. A prompt appears telling you that the operation was successful.
Click Close.
NOTE
Check the conguration before the handover. If a dialog box is displayed prompting the operation
failed, check the service conguration and re-create the handover plan.
2. At the pre-set handover effective time, the Scheduled Handover Notication dialog box
is displayed notifying the user to cut over the circuit.
3. In the Preconguration Group pane, right-click a handover plan and select Handover
CAUTION
----End
10.12.3 Deleting Handover Plans

Use this procedure to delete handover plans.
Prerequisites
n Handover plans must be created.
Procedure
Step 1 Select Trail > SDH Precongured Trail Management from the Main Menu.
Step 2 In the Active Trail pane, right-click the active trail you want to delete, and select Delete from
the shortcut menu.

Step 3 Click Yes and the Delete Failed dialog box is displayed.
NOTE
If you create only the active trail without the precongured trail, a prompt will appear telling you that the
operation was successful. Click Close. In this case skip Step 4 and go directly to Step 5.
Step 4 Click Continue.
NOTE
Before deleting the active trail, you need to delete the related precongured trail. The active trail changes
to a non-precongured trail after the deletion.
Step 5 In the Preconguration Group pane, right-click the handover plan you want to delete, and
select Delete from the shortcut menu.
Step 6 Click Yes. A prompt appears telling you that the operation was successful. Click Close.
----End
10.13 Conguring Preconguration Groups

With a preconguration group, the services on the active trail can be switched to the
precongured trail quickly upon an active trail fault. Thus the preconguration group enables
the node failure protection. When the active trail recovers, the services can still be switched
back from the precongured trail to the active trail.
Context
The preconguration group is a group of circuits with the NM-level protection. In a
preconguration group, one or more routes are precongured to protect an active route. The
preconguration group is mainly used to protect important trails. These trails may not yet be
protected on some route sections or their routes are regarded as unreliable by the user.
Conguring preconguration groups includes:

equipment level.
10.13.3 Deleting Preconguration Groups
Use this procedure to delete preconguration groups.

Prerequisites

beforehand.
Procedure
Step 1 Creating a Preconguration Group
2. In the Preconguration Group pane, select New > Create Preconguration Group.
Step 2 Adding Active Trails
1. Select the desired handover plan for which you want to create active trails and click Add
Active Trail. The Set Trail Browse Filter Conditions dialog box is displayed.
2. Set the lter conditions.
3. Click Filter All and the trails are displayed in the list.
NOTE
Filter All is to refresh and display all qualied trails. Secondary Filter is to lter in the trails
that are already displayed. Incremental Filter is to add new qualied trails to the list without
refreshing the trails that are already displayed.
4. Select a trail and click OK.

Step 3 Creating Precongured Trails One by One
1. Select the appropriate Preconguration Group and Active Trail, select New > Create
One by One to navigate to the Create One by Onewindow.
2. Click Browseto specify the source and sink. In the Select Board Portdialog box
displayed, select the board and prot. Click OK.
3. ClickApply.
The Operation Result dialog box is displayed.
4. Click Close.
NOTE
trail.
8. In the Active pane, right-click an active trail and select Exercise Switching from the
shortcut menu.

9. Select the failed NE and click Exercise Switching. A prompt appears telling you that
NOTE
Exercise switching helps to check whether the precongured trails are congured correctly. Select
the active trail sink as the failed NE for testing.
Step 4 Switching Trails

1. In the Active Trail pane, select an active trail for switching. A prompt appears telling you
that the operation was successful. Click Close.
NOTE
When the active trail is in the normal status, services on the active trail can be switched to the
precongured trail. When services on the the active trail are switched to the precongured trail,
they can be switched back to the active trail. Only when the active trail is already switched, the
active-standby relation can be changed.

3. A prompt appears telling you that the operation was successful. Click Close.
----End

equipment level.
Prerequisites
beforehand.
Procedure
Step 1 Creating a Preconguration Group
2. In the Preconguration Group pane, select New > Create Preconguration Group.
Step 2 Creating Precongured Trails in Batches
1. Select the preconguration group for which you want to create precongured trails in
batches. Select New > Create in Batches.
2. Set Level and Preconguration Group.
NOTE
Note the following during parameter settings:
n If you select Port Level, you can select multiple ports on the board as handover objects.
n If you select Board Level, the system selects all the ports on the board as handover objects.
n If you select Equipment Level, the system selects all the ports on the equipment as handover
objects.
3. Double-click the destination sink NEs of before and after the handover in turn. Select
ports in the dialog box. Click OK.

NOTE
If an NE is selected as a handover object, you do not need to select board ports.
4. Double-click an NE to specify it as an excluded NE. The NE is displayed as

(double-click it again to cancel the selection).
5. Select the trail you want to handover. Click Finish. A prompt appears telling you that
6. Click Cancel to exit the Create Precongured Trail in Batches interface.
NOTE
trail.
10. In the Active pane, right-click an active trail and select Exercise Switching from the
shortcut menu.
11. Select the failed NE and click Exercise Switching. A prompt appears telling you that
NOTE
Exercise switching helps to check whether the precongured trails are congured correctly. Select
the active trail sink as the failed NE for testing.
Step 3 Switching Trails

1. In the Active Trail pane, select an active trail for switching. A prompt appears telling you
that the operation was successful. Click Close.
NOTE
When the active trail is in the normal status, services on the active trail can be switched to the
precongured trail. When services on the active trail are switched to the precongured trail,
they can be switched back to the active trail. Only when the active trail is already switched, the
active-standby relation can be changed.

3. A prompt appears telling you that the operation was successful. Click Close.
----End
10.13.3 Deleting Preconguration Groups

Use this procedure to delete preconguration groups.

Prerequisites
n Preconguration groups must be created.
Procedure
Step 1 Select Trail > SDH Precongured Trail Management from the Main Menu.
Step 2 In the Active Trail pane, right-click the active trail you want to delete, and select Delete from
the shortcut menu.
Step 3 Click Yes and the Delete Failed dialog box is displayed.
NOTE
If you create only the active trail without the precongured trail, a prompt will appear telling you that the
operation was successful. Click Close. In this case skip Step 4 and go directly to Step 5.
Step 4 Click Continue.
NOTE
Before deleting the active trail, you need to delete the related precongured trail. The active trail changes
to a non-precongured trail after the deletion.
Step 5 In the Preconguration Group pane, right-click the preconguration group you want to
delete, and select Delete from the shortcut menu.
----End

Operator Guide 11 Conguring Ethernet Services in the End-to-End Mode
11 Conguring Ethernet
Services in the End-to-End Mode
About This Chapter

In the end-to-end conguration mode, you can create Ethernet services of the EVPL and EPLn
types very quickly. During the end-to-end conguration, you need only to specify the source
and sink for the service, and then the T2000 automatically calculates the route and creates
the service for each NE on the route. The end-to-end conguration mode is also called the
trail management function.
Prerequisite
Context
The T2000 supports the following Ethernet trail management functions:
11.113.2 Creating Ethernet Services

By using the end-to-end trail management function, you can create all types of Ethernet
services quickly on the T2000.
11.213.3 Creating RPR Ethernet Services
To create RPR EVPL and EPLn services, you can complete the service conguration quickly
by using the trail management function.
11.3 Deleting Services
When some services are deleted, the associated resources can be released.
11.4 Viewing Services
The network maintainer or administrator must know about the occupied resources and service
statuses in time.
11.513.5 Setting the QoS
Congure the ow type to select the Ethernet ports, VLANs, VBs, and priorities whose QoS
needs to be set. Bind a CAR ID (corresponding to the CAR ID attribute template) and a
CoS ID (corresponding to the CoS ID attribute template) to the ow to specify the CAR and
CoS attributes of the ow.
11.613.6 Conguring the Spanning Tree
You can congure the spanning tree to avoid possible broadcast storms of Ethernet services.

11 Conguring Ethernet Services in the End-to-End Mode Operator Guide
11.1 Creating Ethernet Services

By using the end-to-end trail management function, you can create all types of Ethernet
services quickly on the T2000.
Context
According to the types of Ethernet trails, the creation includes:
11.1.1 Relation Between SDH Trails and Ethernet Trails

Before creating Ethernet trails, you must create trunk link trails. And before creating trunk link
trails, you must create SDH trails.
11.1.2 Creating a Server Trail
Before creating an Ethernet trail, you must create a server trail as the SDH bearer trail.
11.1.3 Creating a Trunk Link Trail
Before creating EPL, EVPL and EPLn trails, create a trunk link trail as the bearer trail.
11.1.4 Creating an EPL Trail
Use this procedure to create an EPL trail.
11.1.5 Creating an EVPL Trail
Use this procedure to create an EVPL trail.
11.1.6 Creating an EPLn Trail
Use this procedure to create an EPLn trail.
11.1.7 Creating an EVPL(QinQ) Trail
Use this procedure to create an EVPL(QinQ) trail.
11.1.8 Adjusting the Ethernet Trail Bandwidth
By adjusting the bandwidth of a trunk link trail, you can adjust the bandwidth of the Ethernet
trail that the trunk link trail carries.
11.1.9 Adjusting VB Mount Ports in an EPLn
By adjusting the VB mount ports for each EPLn node, you can reallocate Ethernet service
ports, so the accessed Ethernet services can be changed without changing the structure of
the whole EPLn.
11.1.1 Relation Between SDH Trails and Ethernet Trails

Before creating Ethernet trails, you must create trunk link trails. And before creating trunk link
trails, you must create SDH trails.
The following gure shows the relation between SDH trails, trunk link trails and Ethernet trails.
Figure 11-1 Relation Between SDH Trails and Ethernet Trails
The upper level bearer trail is called the server trail, and the lower level trail is called the client
trail. The trunk link trail is the server trail of the Ethernet trail, and oppositely the Ethernet trail

is the client trail of the trunk link trail. The SDH trail is the server trail of the trunk link trail,
and oppositely the trunk link trail is the client trail of the SDH trail.
On the T2000 you can query associated trails. For example, when you are viewing a trunk link
trail, you can view its associated server trail or client trail.
11.1.2 Creating a Server Trail

Before creating an Ethernet trail, you must create a server trail as the SDH bearer trail.
Prerequisites
n A protection subnet and the SDH NNIs must be created for version 4.0 NEs, including
the OptiX 155/622H (Metro 1000), the OptiX 155/622, the OptiX 2500+ (Metro 3000)
and the OptiX Metro 3100.
Procedure
Step 1 Create a VC4 server trail.
NOTE
You do not need to create a VC4 server trail for E4/STM-1/VC4-Xc services.
Step 2 Create the service trail (VC12/VC3 trail or VC4/VC4-Xc trail).
NOTE
When creating a trunk link trail, you can also create a VC12 or VC3 trail.
----End
11.1.3 Creating a Trunk Link Trail

Before creating EPL, EVPL and EPLn trails, create a trunk link trail as the bearer trail.
Prerequisites
n A protection subnet must be created for version 4.0 NEs, including the OptiX 155/622H
(Metro 1000), the OptiX 155/622 (Metro 2050) and the OptiX 2500+ (Metro 3000) and
the OptiX Metro 3100.
n The Ethernet processing board and the corresponding interface board must be installed.
Procedure
Step 1 Select Trail > Trunk Link Creation from the Main Menu.
Step 2 Set the Bandwidth parameter.
Step 3 Optional: Check the Auto Create Server Trail check box.
NOTE
If a VC3/VC12 trail is not created, check the Auto Create Server Trail check box so that you can create
a lower order path trail when creating the trunk link trail. If a VC3/VC12 trail is already created, you can
uncheck the Auto Create Server Trail check box.

Step 4 Set the Source and Sink. Click Browse to select the appropriate VCTRUNK ports.
NOTE
n If the Auto Create Server Trail check box is checked in Step 3, select Bound Timeslot in addition
to the VCTRUNK port. Otherwise you need to select the VCTRUNK port only.
n You need to keep the bandwidth of the source/sink VCTRUNK consistent with the bandwidth setting
in Step 2.
Step 5 Optional: In Available Trail, select an appropriate lower order path trail as the server trail
of the trunk link tail.
NOTE
If Step 3 is executed, skip this step.
Step 6 Optional: Complete the information for this trunk link trail, such as Name, ID and Remarks.
NOTE
If you want to use the default values, skip this step.
Step 7 Optional: If you want to activate the trunk link trail, select Activate the trail.
NOTE
You can also select not to activate the trunk link, but to activate it as needed after the creation.
Step 8 Click Apply. A prompt appears telling that the operation was successful.
----End
11.1.4 Creating an EPL Trail

Use this procedure to create an EPL trail.
Prerequisites
n A trunk link trail must be created.
Procedure
Step 1 Select Trail > Ethernet Trail Creation > EPL Creation from the Main Menu.
Step 2 Set the source and sink for EPL trail. Select Port Usage Strategy for the source and sink.
NOTE
The Port Usage Strategy parameter has the following two values:
n PORT: Use this strategy to congure transparent transmission of the EPL service. This strategy
usually applies to point-to-point communication. The VLAN ID is not editable.
n PORT+VLAN: Use this strategy to congure convergence of the EPL service. This strategy applies
to point-to-point, point-to-multipoint communication, and communication among multiple points.
Step 3 Click Browse to select the appropriate PORT port. If the value of Port Usage Strategy is
PORT+VLAN, the VLAN ID must be set.
Step 4 Set the trunk link trail. Select the route strategy for the trunk link, and perform the next
operation accordingly.
n Strategy 1: Create Trunk Link Automatically. Set the bandwidth of the trunk link and
click Next.
n Strategy 2: Create Trunk Link Manually. Click Next to create the trunk link trail. The
default value of the trunk link route strategy is Using Existing Trunk Link. Select
the created trunk link trail and click Next.

n Strategy 3: Use Existing Trunk Link. Select an existing trunk link trail and clickNext.
n The route strategy for the trunk link depends on the application in practice. Usually it is
recommended to create the trunk link rst, and then create the Ethernet trail. Therefore,
Use Existing Trunk Link is the default value.
n Create Trunk Link Manually and Create Trunk Link Automatically are often used
for service expansion. In the former one, the source and sink of the trunk link need to be
specied manually, but the timeslot allocation can be controlled manually. While in the
latter one, the source and sink of the trunk link can be specied automatically, but the
timeslot allocation cannot be controlled manually.
Step 5 Set port attributes. Set the TAG, LCAS Enabled, Encapsulation Format, Port Enable and
Entry Detection parameters in Port Attribute Setting.
Step 6 Optional: Complete the information for the EPL trail, such as Name, ID and Remarks.
NOTE
Step 7 Optional: If you want to activate the EPL trail, select Activate the trail.
NOTE
You can also select not to activate the EPL trail, but to activate it as needed after the creation.
----End
11.1.5 Creating an EVPL Trail

Use this procedure to create an EVPL trail.
Prerequisites
Procedure
Step 1 Select Trail > Ethernet Trail Creation > EVPL Creation from the Main Menu.
Step 2 Set the EVPL source and sink. Select Port Usage Strategy for the source and sink.
NOTE
The Port Usage Strategy parameter has the following three values:
n PORT: Use this strategy to congure transparent transmission of the EVPL service. This strategy
n PORT+VLAN: Use this strategy to congure convergence of the EVPL service. This strategy applies
n PORT+MPLS: This is the difference between the EVPL service and the EPL service. It can share a
port through the MPLS label even if the services have the same VLAN ID.

Step 3 Click Browse to select the appropriate PORT port. If the value of Usage Strategy is
PORT+VLAN, the VLAN ID must be set. If the value of Usage Strategy is PORT+MPLS,
the tunnel ag must be set.
click Next.
Step 5 Set port attributes. Set the TAG, Port Type, Encapsulation Format, Enabling LCAS,
Mapping Protocol, Port Enable and Entry Detection parameters in Port Attribute Setting.
Step 6 Optional: Complete the information for this EVPL trail, such as Name, ID and Remarks.
NOTE
Step 7 Optional: If you want to activate the EVPL trail, select Activate the trail.
NOTE
You can also select not to activate the EVPL trail, but to activate it as needed after the creation.
----End
11.1.6 Creating an EPLn Trail

Use this procedure to create an EPLn trail.
Prerequisites
n A Trunk Link trail must be created.
Procedure
Step 1 Select Trail > Ethernet Trail Creation > EPLn Creation from the Main Menu.
Step 2 Double-click the appropriate NE in The Trail View. The Select Board Port dialog box is
displayed.
Step 3 Select an appropriate board in Slot Layout. Select appropriate ports in Available
Timeslots/Port and click the double-right-arrow button. Click OK.

Step 4 Repeat Steps 2 and 3 to select as many ports as necessary.

n Strategy 1: Create Trunk Link Manually. Click Next to create the trunk link trail. After
the creation, click Next. The default value of the trunk link route strategy is Using
Existing Trunk Link. Select the created trunk link trail and click Next.
NOTE
n The route strategy for the trunk link trail depends on the application in practice. Usually it is
recommended to create the trunk link trail rst, and then create the Ethernet trail. Therefore, Use
Existing Trunk Link is the default value.
n Create Trunk Link Manually is often used for service expansion.
Step 6 Set port attributes for all ports on the Ethernet trail.
Step 7 Create VLAN. Click Add in VLAN Conguration. The VLAN Conguration for Ethernet
Trail dialog box is displayed.

Step 8 Enter VLAN ID. Select appropriate mounted ports in the Available Mounted Ports pane,
and click .
Step 9 Click OK or Apply. Repeat Steps 7 through 9 to create as many VLANs as necessary.
Step 10 Click Next.
Step 11 If you want to activate the EPLn trail, select Activate the trail.
NOTE
You can also select not to activate the EPLn trail, but to activate it as needed after the creation.
----End
11.1.7 Creating an EVPL(QinQ) Trail

Use this procedure to create an EVPL(QinQ) trail.
Prerequisites
Procedure
Step 1 Select Trail > Ethernet Trail Creation > EVPL(QinQ) Creation from the Main Menu.
Step 2 Set the direction of the trail.
Step 3 Select Port Usage Strategy for the source and sink.
NOTE
n PORT: Use this strategy to congure transparent transmission of the EVPL service. This strategy
usually applies to point-to-point communication.
n PORT+VLAN: Use this strategy to congure convergence of the EVPL service. This strategy applies
Step 4 Select the Operation Type for the source and sink.
Step 5 Click Browse to select the appropriate port.
Step 6 Set S-VLAN and C-VLAN depend on the selected operation type.
click Next.
Step 8 Set port attributes. Set the TAG, Port Type, Mapping Protocol, Port Enable and Entry
Detection parameters in Port Attribute Setting.

Step 9 Optional: Complete the information for this EVPL trail, such as Name, ID and Remarks.
NOTE
Step 10 Optional: If you want to activate the EVPL trail, select Activate the trail.
NOTE
You can also select not to activate the EVPL(QinQ) trail, but to activate it as needed after the creation.
----End
11.1.8 Adjusting the Ethernet Trail Bandwidth

By adjusting the bandwidth of a trunk link trail, you can adjust the bandwidth of the Ethernet
trail that the trunk link trail carries.
Prerequisites
n The trunk link trail is created.
n The LCAS function of the trunk link trail is enabled.
Context
After Ethernet services run for a period, larger transmission capacity is required because of
an increase of trafcs. A simple way for the expansion is to add path members to the trunk
link trail that carries the Ethernet trail. This operation does not interrupt existing services or
require any changes to the source and sink ports of the Ethernet trail. On the other hand, if the
trafc load is overestimated when Ethernet services are initially provided, you can delete extra
path members to avoid wasting bandwidth and save costs.
Procedure
Step 1 Select Trail > Trunk Link Management in the Trail View.
Step 2 Select the trunk link trail from the list.
Step 3 To increase the bandwidth of the trunk link trail, click the Path Member tab. Click Add
and the Add Path Member dialog box is displayed. Select an appropriate path member
and click OK.
NOTE
The path member to add must have the same rate as the original ones.
Step 4 To reduce the bandwidth of the trunk link trail, click the Path Attributes tab. Select an
appropriate path member and click Delete.
----End

11.1.9 Adjusting VB Mount Ports in an EPLn

By adjusting the VB mount ports for each EPLn node, you can reallocate Ethernet service
ports, so the accessed Ethernet services can be changed without changing the structure of
the whole EPLn.
Prerequisites
n The EPLn trail is created.
Context
CAUTION
To delete a port mounted to the VB, make sure it does not belong to any VLAN ltering table.
Otherwise, the deletion will fail.
Procedure
n Adding a VB Mount Port
1. Select Trail > Ethernet Trail Management in the Trail View.
2. Select a trail in the Ethernet trail list and click the Node tab.
3. Right-click an appropriate node in the node list and select Congure VB attached
port from the shortcut menu. The VB Conguration for Ethernet Trail dialog
box is displayed.
4. Select an appropriate port from the Available Mounted Ports pane and click
. ClickOK.

5. Right-click the node icon in the Main Topology and select NE Explorer from
the shortcut menu.
6. Select the Ethernet board used for the EPLn from the Object Tree, and then select
Conguration > Ethernet Service > Ethernet LAN Service from the Function
Tree. Click the VLAN tab.
7. Select an appropriate VLAN from the VLAN list and click Modify. Add the port
mounted in Step 4 to the VLAN ltering table.
8. Repeat Steps 1 to step 7 to add VB mount ports for other nodes as needed.
n Deleting a VB Mount Port
1. To delete a mounted port, make sure it is not a forwarding port of any VLAN
ltering table. Right-click the node icon in the Main Topology and select NE
Explorer from the shortcut menu.
2. Select the Ethernet board used for the EPLn from the Object Tree, and select
Conguration > Ethernet Service > Ethernet LAN Service from the Function
Tree. Click the VLAN tab.
3. Check whether the port is included in any VLAN ltering table. If yes, select the
VLAN and click Modify to delete the port from the VLAN ltering table.
4. Select Trail > Ethernet Trail Management. Select the EPLn trail from the
Ethernet trail list and then click the Node tab.
5. Right-click an appropriate node in the node list and select Congure VB attached
port from the shortcut menu. The VB Conguration for Ethernet Trail dialog
box is displayed.
6. Select an appropriate port from "Select Mounted Ports" and click .

7. Repeat Steps 1 through 6 to delete mounted ports for other nodes.
----End

11.2 Creating RPR Ethernet Services

To create RPR EVPL and EPLn services, you can complete the service conguration quickly
by using the trail management function.
Context
For the two types of services, the conguration methods are as follows:
11.2.1 Creating an RPR EVPL Trail

By using the trail management function, you can congure an RPR EVPL service directly from
the angle of networking. In this way the conguration process is simplied.
11.2.2 Creating an RPR EPLn Trail
The RPR EPLn trail enables the RPR Ethernet service to be dynamically shared by multiple
points, which meets the dynamic feature of data services and saves bandwidth resources. By
using the trail management function, you can congure an RPR EPLn service directly from the
angle of networking. In this way the conguration process is simplied.
11.2.1 Creating an RPR EVPL Trail

By using the trail management function, you can congure an RPR EVPL service directly from
the angle of networking. In this way the conguration process is simplied.
Prerequisites
n A Trunk Link trail must be created.
n The working mode of RPR board external ports must be set.
Procedure
Step 1 Select Trail > Ethernet Trail Creation > RPR EVPL Creation from the Main Menu.
Step 2 Set Port Usage Strategy for the source and sink. If the usage strategy is set to Port+VLAN,
you need to set the VLAN ID.
NOTE
n Port: Use this strategy to congure transparent transmission of the EVPL service. This strategy
n Port+VLAN: Use this strategy to congure convergence of the EVPL service. This strategy applies
Step 3 Set port of source and sink respectively. Click Browse and select a board under Slot Layout, a
port under RPR Port, and a port under Line Port. Then click OK.

Step 4 Set the Route Strategy parameter for the source and sink. There are three route strategies:
Automatically Calculate (802.17), By 0 Ring, and By 1 Ring. Click Next.
NOTE
For the N2RPR board, the Route Strategy can be selected. While for the N1RPR board, the Route
Strategy cannot be selected.
Step 5 Set the attributes for the source port and the sink port of the RPR EVPL trail.
Step 6 Optional: Complete the RPR EVPL trail information, such as Name, Customer, Trail ID
and Remark.
Step 7 Optional: If you want to activate the RPR EVPL trail, select Activate the trail.
NOTE
You can also select not to activate the RPR EVPL trail at this time, but activate it as needed after the
creation.
----End
11.2.2 Creating an RPR EPLn Trail

The RPR EPLn trail enables the RPR Ethernet service to be dynamically shared by multiple
points, which meets the dynamic feature of data services and saves bandwidth resources. By
using the trail management function, you can congure an RPR EPLn service directly from the
angle of networking. In this way the conguration process is simplied.

Prerequisites
n The working mode of RPR board external ports must be set.
Procedure
Step 1 Select Trail > Ethernet Trail Creation > RPR EPLn Creation from the Main Menu.
Step 2 Double-click the appropriate NE on the Trail View.
Step 3 Select a board under Slot Layout and ports under Available Ports, and then click .
Click OK.
Step 4 Repeat Steps 2 and 3 to select required nodes for the RPR EPLn.
Step 5 Click Next.
Step 6 Set the attributes for all ports on the RPR EPLn trail.
Step 7 To create VLAN, click Add in VLAN Conguration. The VLAN Conguration for
Ethernet Trail dialog box is displayed.
Step 8 Enter a value in the VLAN ID eld. Select appropriate mounted ports in the Available
Mounted Ports list, and click .

Step 9 ClickOK or Apply. Repeat Steps 7 through 9 to create as many VLANs as necessary.
Step 10 Click Next.
Step 11 Optional: Complete the RPR EPLn trail information, such as Name, Customer, Trail ID
and Remark.
Step 12 Optional: If you want to activate the RPR EPLn trail, select Activate the trail.
NOTE
You can also select not to activate this RPR EPLn trail at this time, but activate it as needed after the
creation.
----End
11.3 Deleting Services

When some services are deleted, the associated resources can be released.
Context
Ethernet services must be deleted in the following order:
1. 11.3.1 Deleting Ethernet Trails

Only when the Ethernet trail is deleted, the trunk link trail or SDH trail that carries the
Ethernet trail can be deleted.
2. 11.3.2 Deleting Trunk Link Trails
Use this procedure to delete trunk link trails.
11.3.1 Deleting Ethernet Trails

Only when the Ethernet trail is deleted, the trunk link trail or SDH trail that carries the Ethernet
trail can be deleted.
Prerequisites
n Make sure the Ethernet trail to be deleted is inactive.
Procedure
Step 1 Select Trail > Ethernet Trail Management from the Main Menu.
Step 2 Select one or more Ethernet trails to delete, and right-click and select Delete from the shortcut
menu.
Step 3 Click OK.
----End
11.3.2 Deleting Trunk Link Trails

Use this procedure to delete trunk link trails.
Prerequisites
n Make sure the trunk link trail to be deleted does not carry any Ethernet trail.

n Make sure the trunk link trail to be deleted is inactive.
Context
NOTE
If the trunk link trail to delete is already used for an Ethernet trail, you need to delete the Ethernet trail
rst. For details, refer to 11.3.1 Deleting Ethernet Trails.
Procedure
Step 1 Select Trail > Trunk Link Management from the Main Menu.
Step 2 Select one or more trunk link trails to delete, and right-click and select Delete from the
shortcut menu.
Step 3 Delete relevant trails as required.
NOTE
The server trail refers to an SDH trail used by the trunk link trail.
----End
11.4 Viewing Services

The network maintainer or administrator must know about the occupied resources and service
statuses in time.
Context
The bearer trails for Ethernet trails are trunk link trails, and the bearer trails for trunk link trails
are SDH trails. To view the information of Ethernet trails, you can use the following methods.
11.4.1 Viewing Trunk Link Trails

Use this procedure to view the trunk link trail information.
11.4.2 Viewing Relevant Trails of a Trunk Link Trail
The trunk link trail is located between its client layer Ethernet trail and server layer SDH trail.
When you are viewing the trunk link trail, you can also view its relevant server and client
trails. This enables easy management and maintenance.
11.4.3 Viewing Ethernet Trails
By viewing Ethernet trails, you can know about the trail details such as the route and occupied
resources.
11.4.4 Viewing the Server Trail of an Ethernet Trail
The server trail of an Ethernet trail is the trunk link trail. When viewing the Ethernet trail, you
can also view its trunk link trail.
11.4.1 Viewing Trunk Link Trails

Use this procedure to view the trunk link trail information.
Prerequisites
Procedure
Step 2 View the trail attributes in the trunk link trail list.

n If you want to view the details of a trail, right-click the trail in the list and select Details
from the shortcut menu. The Details dialog box is displayed. After viewing it, click OK.
n If you want to view the SDH trail used by the trunk link trail, click the trunk link trail in
the list and click the Path Member tab.
n If you want to view the source/sink port attributes of a trail, click the trail in the list
and click the Port Attributes tab.
----End
11.4.2 Viewing Relevant Trails of a Trunk Link Trail

The trunk link trail is located between its client layer Ethernet trail and server layer SDH trail.
When you are viewing the trunk link trail, you can also view its relevant server and client
trails. This enables easy management and maintenance.
Prerequisites
Procedure
Step 2 If you want to view client trails, right-click a trunk link trail in the list and select Query
Relevant Client Trails from the shortcut menu. The SDH Trail Management interface is
displayed, showing the server trail of the trunk link trail.
NOTE
To go back from the server trail to the trunk link trail, right-click the server trail, and select Query
Relevant Client Trails.
Step 3 If you want to view server trails, right-click a trunk link trail in the list and select Query
Server Layer Trail from the shortcut menu. The SDH Trail Management interface is
displayed, showing the server trail of the trunk link trail.
NOTE
To go back from the server trail to the trunk link trail, right-click the server trail, and select Query
Relevant Client Trails.
----End
11.4.3 Viewing Ethernet Trails

By viewing Ethernet trails, you can know about the trail details such as the route and occupied
resources.
Prerequisites
n The Ethernet trail is created.
Procedure
Step 1 Select Trail > Ethernet Trail Management in the Trail View.
Step 2 View the basic attributes of the Ethernet trail in the Ethernet trail list.

Step 3 If you want to view the route information of each NE on an EPL or EVPL trail, right-click
a trail in the trail list and select Details from the shortcut menu. The Details dialog box is
displayed. Click the Route Information or Attributetab. After viewing it, click OK.
NOTE
The route information is automatically generated by the system. When conguring the Ethernet trail, the
T2000 sets up the corresponding route on each NE according to the sink and source ports of the Ethernet
trail and those of the trunk link trail.
Step 4 If you want to view the node and port information on an Ethernet trail, click a trail in the trail
list and click the Node tab. In the node list, you can view the PORT and VCTRUNK ports
used by each NE. Click Port Attributes and the Ethernet Trail Port Attribute dialog box is
displayed, where you can view the attributes of all ports used by the trail.
Step 5 If you want to view the trunk link trail used by an Ethernet trail, click the trail in the trail
list and click the Trunk Link tab.
Step 6 If you want to view the VLAN ltering table of an EPLn, click the trail in the trail list and
click the VLAN tab.
----End
11.4.4 Viewing the Server Trail of an Ethernet Trail

The server trail of an Ethernet trail is the trunk link trail. When viewing the Ethernet trail, you
can also view its trunk link trail.
Prerequisites
n The Ethernet trail is created.
Procedure
Step 1 Select Trail > Ethernet Trail Management in the Trail View.
Step 2 Right-click a trail in the Ethernet trail list and select Query Relevant Server Layer Trails
from the shortcut menu. The Trunk Link Management interface is displayed, showing the
trunk link trail that the Ethernet trail uses.
NOTE
To go back from the trunk link trail to the Ethernet trail, right-click the trunk link trail and select Query
client trail from the shortcut menu.
----End
11.5 Setting the QoS

Prerequisites
n The Ethernet service must be created.

Procedure
Step 1 In the NE Explorer, click a board and select Conguration > QoS Management > Flow
Management from the Function Tree.
Step 2 Click the CAR Conguration tab. Click New and the Create CAR window is displayed.
Step 3 Set the CAR ID and other parameters.
Step 4 Click OK. The Operation Result window is displayed. Click Close.
Step 5 Optional: If the board provides support for creating CoS, click the CoS Conguration tab.
Click New and the Create CoS window is displayed.
Step 6 Optional: Set the CoS ID and other parameters.
Step 7 Optional: Click OK. The Operation Result window is displayed. Click Close.
Step 8 Optional: If the board provides support for creating ow, click the Flow Conguration tab.
Click Create and the Create Flow window is displayed.
Step 9 Optional: Set the Flow Type and other parameters.
Step 11 Optional: Double-click in the Bound CAR and Bound CoS elds to select a CAR ID and a
CoS ID respectively. The selected IDs are bound to the ow, and thus the ow has relevant
CAR and CoS attributes.
----End
11.6 Conguring the Spanning Tree

Prerequisites
n The VB must be created.
Procedure
Step 1 In the NE explorer, click a board and select Conguration > Layer-2 Switching Management
> Spanning Tree from the Function Tree.
Step 2 Set the priority and other attributes of each VB port and click Apply.
NOTE
The port with a smaller MAC address must have a higher priority.
Step 3 Click the Protocol Enabled tab.

Step 4 Set the Protocol Enabled parameter to Enabled. Select a working mode as needed. Click
Apply.
Step 5 Optional: Click the Port Parameters tab to set VB port parameters.
Step 6 Optional: Click the Bridge Running Information tab to view the bridge information.
Step 7 Optional: Click the Port Running Information tab to view the VB port information.
----End

Operator Guide 12 Conguring SDH Services Station by Station
12 Conguring SDH
Services Station by Station
About This Chapter

When conguring SDH services station by station, you can specify the timeslot and route for
each NE individually. However, this conguration method is of relatively low efciency. The
trail function is recommended for service conguration if the trail function is provided in
the T2000.
Context
In different types of protection subnets, congure SDH services station by station by the
process below:
12.1 Querying the NE Software Version

To ensure proper service conguration, the version mapping relations between NE software,
board software and the T2000 must be met. Such mapping relations can be found in the
version description of the equipment. Before SDH service conguration, the NE software
version must be queried on the T2000.
12.2 Dependency of SDH Service Conguration on NE Software Release
The NE software runs on release 4.0 and 5.0 NE platforms. Therefore, the NE software has
two V-level releases—4.0 and 5.0.
12.3 Creating NE Logical Systems
You can create logical systems for the specied NE. For a logical system, you can set the
attributes including name, network topology type, service direction and protection mode. NEs
can be divided to one or more logical systems, according to the topology structure of the
network where the NEs reside. A network has ve basic topology structures: chain, tree, star,
ring and mesh. Every logical system represents a topology structure (including chain and ring)
of the network that the NEs are connected to. Logical systems can be of TM, ADM and REG
types. TM includes east or west line boards, while ADM and REG include east and west line
boards. For example, NEs in a ring with chain network can be divided to a logical system of
the ADM ring type and one of the TM chain type.
12.4 Creating MSP Rings
You can create MSP rings.
12.5 Creating a Linear MSP
You can create a linear MSP.
12.6 Create Services Within a Protection Subnet
Following the instructions below, you can create services within a protection subnet. That is,
all NEs that the service passes through are within the same protection subnet.

12 Conguring SDH Services Station by Station Operator Guide
12.7 Conguration of Services Across Protection Subnets

When conguring SDH services station by station, you need to congure services at every
station that services pass through according to trafc ow. When conguring services across
protection subnets, you need to focus on the service conguration of the NE at the connection
point of protection subnets. You need to decide how to congure services for the NE by
analyzing specic protection scheme and trafc ow.
12.8 Changing Between SNCP and Normal Services
During a network expansion or cutover, you may need to change the type of a protection
subnet or change the protection type of services. This function enables you to change an SNCP
service to a normal service quickly and vice versa.

12.1 Querying the NE Software Version

To ensure proper service conguration, the version mapping relations between NE software,
board software and the T2000 must be met. Such mapping relations can be found in the
version description of the equipment. Before SDH service conguration, the NE software
version must be queried on the T2000.
Prerequisite
Procedure
Step 1 Double-click an NE on the Main Topology.
The NE Panel is displayed.
Step 2 Right-click on the SCC slot and select SCC Version from the shortcut menu.
A dialog box is displayed with the NE software version.
Step 3 ClickOK.
----End
12.2 Dependency of SDH Service Conguration on NE

Software Release
The NE software runs on release 4.0 and 5.0 NE platforms. Therefore, the NE software has
two V-level releases—4.0 and 5.0.
The major difference between NE software release 4.0 and 5.0 lies in SDH service
conguration.
n For release 5.0, there is no longer the concept of logic system, and service conguration is
based on physical O/E ports and VC4/VC12. For release 4.0, a protection subnet must
be created before service conguration.
n With release 5.0 NEs, the NE software does not duplicate the services automatically, as it
does with release 4.0 NEs. When you congure dual-feed services in a PP ring network
with release 4.0 NEs, for example, the NE software automatically generates the dual-feed
or selective-receive service for the source or sink node, and also automatically generates
the pass-through service in the opposite direction for a pass-through node. With NE
software release 5.0, however, you must congure dual-feed services in both directions.
12.3 Creating NE Logical Systems

You can create logical systems for the specied NE. For a logical system, you can set the
attributes including name, network topology type, service direction and protection mode. NEs
can be divided to one or more logical systems, according to the topology structure of the
network where the NEs reside. A network has ve basic topology structures: chain, tree, star,
ring and mesh. Every logical system represents a topology structure (including chain and ring)
of the network that the NEs are connected to. Logical systems can be of TM, ADM and REG
types. TM includes east or west line boards, while ADM and REG include east and west line
boards. For example, NEs in a ring with chain network can be divided to a logical system of
the ADM ring type and one of the TM chain type.
Prerequisites

n Applies to release 4.0 NEs ( OptiX 155/622H(Metro1000), OptiX 155/622(Metro2050),

OptiX 2500+(Metro3000), and OptiX Metro 3100).
Procedure
Step 1 In the NE Explorer, click an NE and select Conguration > Logical System from the
Function Tree.
Step 2 Click Create and the Create a Common Logical System dialog box is displayed.
Step 3 In the Attribute area, select the Type, Level, Topology Structure, Direction, Protection
Mode, Node Type and Name.
Step 4 In the Slot Mapping Relations area, select the mapping direction and the slots you want to
map, and then click .
Step 5 Click OK.
----End
12.4 Creating MSP Rings

You can create MSP rings.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Conguration > Ring MS from the Function Tree.
Step 2 Click Create and the Create a Multiplex Section Ring dialog box is displayed.
Step 3 In the Attribute area, select the Level, Protection Type, Node Type, Local Node, Max.
Node, WTR Time (s), SD Enable, Protocol Type, Name and so on.
Step 5 Click OK.
----End
12.5 Creating a Linear MSP

You can create a linear MSP.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and choose Conguration > Linear MS from the Function
Tree.
Step 2 Click Create and the Create a Linear Multiplex Section dialog box is displayed.
Step 3 In the Attribute area, select the Protection Type, Switching Mode, Revertive Mode, WTR
Time(s) and SD Enable.

Step 5 Click OK.
----End
12.6 Create Services Within a Protection Subnet

Following the instructions below, you can create services within a protection subnet. That is,
all NEs that the service passes through are within the same protection subnet.
12.6.1 Creating Services for a Non-Protection Chain

station that services pass through according to trafc ow. Use this procedure to congure
services for a non-protection (NP) ring.
12.6.2 Creating Services for a 1+1 Linear MSP
station that services pass through according to trafc ow. In a 1+1 linear MSP, you need
to congure services in the working path only, that in the protection path is duplicated
automatically by the T2000.
12.6.3 Creating M:N Linear MSP Services
station that services pass through according to trafc ow. In a M:N linear MSP, the protection
path can transmit extra services if the working path is normal. When conguring SDH
services, you can congure extra services in the protection path.
12.6.4 Creating Services for a Two-Fiber Unidirectional PP Ring
station that services pass through according to trafc ow. In a two-ber unidirectional path
protection (PP) ring, services are transmitted through the entire ring by diverse routes. You
need to congure add/drop or pass-through services for every node on the ring.
12.6.5 Creating Services for a Two-Fiber Bidirectional PP Ring
station that services pass through according to trafc ow. In a two-ber bidirectional path
protection (PP) ring, services are transmitted through uniform routes. You need to congure
add/drop or pass-through services only at the nodes that the services pass through.
12.6.6 Creating Services for a Two-Fiber Unidirectional MSP Ring
station that services pass through according to trafc ow. In a two-ber unidirectional MSP
ring, services are transmitted through the entire ring by diverse routes. You need to congure
add/drop or pass-through services for every node on the ring.
12.6.7 Creating Services for a Two-Fiber Bidirectional MSP Ring
services for a two-ber bidirectional MSP ring.
12.6.8 Creating Services for a Four-Fiber Bidirectional MSP Ring
services for a four-ber bidirectional MSP ring.
12.6.9 Creating SNCP Services
SNCP services can be dual fed and selectively received and is applicable to protecting services
across subnets. When conguring SDH services station by station, you can create SNCP
services to protect services across subnets.

12.6.1 Creating Services for a Non-Protection Chain

services for a non-protection (NP) ring.
Prerequisites
n For release 4.0 NEs, including the OptiX 155/622H (Metro 1000), the OptiX 155/622
(Metro 2050), the OptiX 2500+ (Metro 3000) and the OptiX Metro 3100, the protection
subnet must be created.
n For VC12/VC3 services, the AMXC， EMXC or ETXC board that supports low order
cross-connection must be installed in the OptiX 10G(Metro 5000), and the low order
cross-connect protection pair must be created.
n For VC12/VC3 services, the GXCL or EXCL board that supports low order
cross-connection must be installed in the OSN 9500, and the low order cross-connect
protection pair must be created.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > SDH Service Conguration
from the Function Tree.
Step 2 Click Query to query the service information from the NE.
Step 3 Click Create and the Create SDH Service dialog box is displayed.
Step 4 Complete the information as required.
NOTE
n To congure add/drop services, you need to congure bidirectional services from the line board
to the tributary board.
n To congure pass-through services, you need to congure bidirectional services between the line
boards that services pass through.
Step 5 Click OK.

----End
Conguration Sample
Figure 12-1 Service conguration for a non-protection chain
In Figure 12-1, NE1, NE2, and NE3 comprise a non-protection ring. Eight bidirectional E1
services are transmitted between NE1 and NE3. The services take 1-8 VC12 timeslots on the
tributary board, and 1-8 VC12 timeslots of the rst VC4 on the line board.

The E1 services ow is as follows: E1←→NE1 tributary board←→NE1 east line

board←→NE2 west line board←→NE2 east line board←→NE3 west line board←→NE3
tributary board.
According to E1 services ow, complete the following congurations:
n Congure add/drop VC12 services at NE1: bidirectional services from the tributary board
to the line board, with the source and the sink timeslots ranging from 1 to 8.
n Congure pass-through VC12 services at NE2: bidirectional services between the west
and the east line boards, with the source and the sink timeslots ranging from 1 to 8.
n Congure add/drop VC12 services at NE3: bidirectional services from the active west line
board to the tributary board, with the source and the sink timeslots ranging from 1 to 8.
12.6.2 Creating Services for a 1+1 Linear MSP

station that services pass through according to trafc ow. In a 1+1 linear MSP, you need
to congure services in the working path only, that in the protection path is duplicated
automatically by the T2000.
Prerequisites
n The 1+1 linear MSP must be created.
n For VC12/VC3 services, the AMXC or EMXC or ETXC board that supports low order
Procedure
Step 2 Click Query to query the SDH service information from the NE.

NOTE
Step 5 Click OK.

----End
Figure 12-2 Service conguration for a 1+1 Linear MSP
In the Figure 12-2, NE1 and NE2 comprise a 1+1 protection chain. Eight bidirectional E1
services are transmitted between NE1 and NE2. The services take 1-8 VC12 timeslots on the
tributary board, and 1-8 VC12 timeslots of the rst VC4 on the line board.
If the network is running normally, the E1 services ow is as follows: E1←→NE1 tributary
board←→NE1 active east line board←→NE2 active west line board←→NE2 tributary board.
In the 1+1 protection chain architecture, the E1 services are running in both the working and
the protection paths. At the receiving end, the tributary board selects the path with better
quality signals.


n Congure add/drop VC12 services for the working path at NE1: bidirectional services
between the tributary board and the active east line board, with the source and the sink
timeslots ranging from 1 to 8.
between the active west line board and the tributary board, with the source and the sink
12.6.3 Creating M:N Linear MSP Services

station that services pass through according to trafc ow. In a M:N linear MSP, the protection
path can transmit extra services if the working path is normal. When conguring SDH
services, you can congure extra services in the protection path.
Prerequisites
n The M:N linear MSP must be created.
n For VC12/VC3 services, the AMXC or EMXC or ETXC board that supports low order
Context
CAUTION
When protection switching occurs, the extra services carried over the protection path are lost.
Procedure

NOTE
Step 5 Click OK.

Step 6 If you want to congure extra services in the protection path, click Create and create extra
services in the pop-up Create SDH Service dialog box. Click OK.
----End
Figure 12-3 Creating M:N Linear MSP Services
In Figure 12-3, NE1 and NE2 comprise a 1:1 protection chain. Eight bidirectional E1 services
are transmitted between NE1 and NE2. The services take 1-8 VC12 timeslots on the tributary
board, and 1-8 VC12 timeslots of the rst VC4 on the line board.
board←→NE1 active east line board←→NE2 active west line board←→NE2 tributary board.

In the 1:1 protection chain architecture, the E1 services are running in the working path and
the protection path is idle.
between the tributary board and the active east line board, with the source and the sink
between the active west line board and the tributary board, with the source and the sink
12.6.4 Creating Services for a Two-Fiber Unidirectional PP Ring

station that services pass through according to trafc ow. In a two-ber unidirectional path
protection (PP) ring, services are transmitted through the entire ring by diverse routes. You
need to congure add/drop or pass-through services for every node on the ring.
Prerequisites
(Metro 2050) the OptiX 2500+ (Metro 3000), and the OptiX Metro 3100, the protection
Context
NOTE
n For release 4.0 NEs, including the OptiX 155/622H(Metro 1000), the OptiX 155/622(Metro 2050)
the OptiX 2500+(Metro 3000), and the OptiX Metro 3100: To congure add/drop services, you
need to congure unidirectional services from the west line board to the tributary board and from
the tributary board to the east line board. To congure pass-through services, you need to congure
unidirectional services between the west and the east line boards.
n For release 5.0 NEs: To congure add/drop services, you need to congure bidirectional services
from the west line board to the tributary board and from the tributary board to the east line board. To
congure pass-through services, you need to congure bidirectional services between the east and
the west line boards.
Procedure
Step 1 In the NE Explorer, click the NE and select the Conguration > SDH Service Conguration
Step 5 Click OK.
----End

Figure 12-4 Service conguration for a two-ber unidirectional PP ring
In Figure 12-4, NE1, NE2, NE3 and NE4 comprise a unidirectional PP ring. Eight bidirectional
E1 services are transmitted between NE1 and NE3. The services take 1-8 VC12 timeslots on
the tributary board, and 1-8 VC12 timeslots of the rst VC4 on the line board.
E1 services are bidirectional. Services from NE1 to NE3 and those from NE3 to NE1 are
transmitted through diverse routes.
n If the network is running normally, the E1 services ow from NE1 to NE3 is as follows:
E1→NE1 tributary board→NE1 east line board→NE2 west line board→NE2 east line
board→NE3 west line board→NE3 tributary board.
n Congure add/drop VC12 services at NE1: unidirectional services from the tributary
board to the east line board, with the source and the sink timeslots ranging from 1 to 8;
bidirectional services between the tributary board and the west line board, with the source
and the sink timeslots ranging from 1 to 8.
n Congure add/drop VC12 services at NE3: unidirectional services from the west line
board to the tributary board, with the source and the sink timeslots ranging from 1 to 8;

bidirectional services between the tributary board and the east line board, with the source
12.6.5 Creating Services for a Two-Fiber Bidirectional PP Ring

station that services pass through according to trafc ow. In a two-ber bidirectional path
protection (PP) ring, services are transmitted through uniform routes. You need to congure
add/drop or pass-through services only at the nodes that the services pass through.
Prerequisites
(Metro 2050) the OptiX 2500+ (Metro 3000), and the OptiX Metro 3100, the protection
Context
NOTE
Procedure
Step 1 In the NE Explorer, click the NE and select the Conguration > SDH Service Conguration
Step 5 Click OK.
----End

Figure 12-5 Service conguration for a two-ber bidirectional PP ring
In Figure 12-5, NE1, NE2, NE3 and NE4 comprise a bidirectional PP ring. Eight bidirectional
E1 services are transmitted between NE1 and NE3. The services take 1-8 VC12 timeslots on
the tributary board, and 1-8 VC12 timeslots of the rst VC4 on the line board.
board←→NE1 east line board←→NE2 west line board←→NE2 east line board←→NE3
west line board←→NE3 tributary board.
n Congure add/drop VC12 services at NE1: bidirectional services between the tributary
board and the east line board, with the source and the sink timeslots ranging from 1 to 8.
n Congure add/drop VC12 services at NE3: bidirectional services between the west line
board and the tributary board, with the source and the sink timeslots ranging from 1 to 8.
12.6.6 Creating Services for a Two-Fiber Unidirectional MSP Ring

station that services pass through according to trafc ow. In a two-ber unidirectional MSP

ring, services are transmitted through the entire ring by diverse routes. You need to congure
add/drop or pass-through services for every node on the ring.
Prerequisites
n The protection subnet must be created.
Procedure
NOTE
n To congure add/drop services, you need to congure the unidirectional services from the west line
board to the tributary board and from the tributary board to the east line board respectively.
n To congure pass-through services, you need to congure the unidirectional services between the
west and the east line boards.
Step 5 Click OK.

----End

Figure 12-6 Service conguration for a two-ber unidirectional MSP ring
In Figure 12-6, NE1, NE2, NE3 and NE4 comprise a two-ber unidirectional MSP ring. Eight
bidirectional E1 services are transmitted between NE1 and NE3. The services take 1-8 VC12
timeslots on the tributary board, and 1-8 VC12 timeslots of the rst VC4 on the line board.
n Congure add/drop VC12 services at NE3: unidirectional services from the west line
board to the tributary board, with the source and the sink timeslots ranging from 1 to 8;

bidirectional services between the tributary board and the east line board, with the source
12.6.7 Creating Services for a Two-Fiber Bidirectional MSP Ring

services for a two-ber bidirectional MSP ring.
Prerequisites
Context
NOTE
n In a two-ber bidirectional MSP ring, services are transmitted through uniform routes. You need to
congure add/drop or pass-through services only at the nodes that the services pass through.
n In a two-ber bidirectional MSP ring, the protection path transmit extra services if the working one is
normal. You can congure extra services in the protection path.
Procedure
Step 5 Click OK.
----End

Figure 12-7 Service conguration for a two-ber bidirectional MSP ring
In Figure 12-7, NE1, NE2, NE3 and NE4 comprise a two-ber unidirectional MSP ring. Eight
transmitted through uniform routes. If the network is running normally, the E1 services
ow is as follows: E1←→NE1 tributary board←→NE1 east line board←→NE2 west line
board←→NE2 east line board←→NE3 west line board←→NE3 tributary board.
to the east line board, with the source and the sink timeslots ranging from 1 to 8.
n Congure add/drop VC12 services at NE3: bidirectional services from the west line board
to the tributary board, with the source and the sink timeslots ranging from 1 to 8.

12.6.8 Creating Services for a Four-Fiber Bidirectional MSP Ring

services for a four-ber bidirectional MSP ring.
Prerequisites
Context
NOTE
n In a four-ber bidirectional MSP ring, services are transmitted through uniform routes. You need to
congure add/drop or pass-through services only at the nodes that the services pass through.
n In a four-ber bidirectional MSP ring, the protection path transmit extra services if the working one is
normal. You can congure extra services in the protection path.
Procedure
Step 5 Click OK.
----End

Figure 12-8 Service conguration for a four-ber bidirectional MSP ring
In Figure 12-8, NE1, NE2, NE3 and NE4 comprise a four-ber unidirectional MSP ring. Eight
transmitted through uniform routes. If the network is running normally, the E1 services ow
is as follows: E1←→NE1 tributary board←→NE1 active east line board←→NE2 active
west line board←→NE2 active east line board←→NE3 active west line board←→NE3
tributary board.
to the active east line board, with the source and the sink timeslots ranging from 1 to 8.
n Congure pass-through VC12 services at NE2: bidirectional services between the active
west and the active east line boards, with the source and the sink timeslots ranging from 1
to 8.
n Congure add/drop VC12 services at NE3: bidirectional services from the active west line
board to the tributary board, with the source and the sink timeslots ranging from 1 to 8.

12.6.9 Creating SNCP Services

SNCP services can be dual fed and selectively received and is applicable to protecting services
across subnets. When conguring SDH services station by station, you can create SNCP
services to protect services across subnets.
Prerequisites
(Metro 2050) and the OptiX 2500+ (Metro 3000), the protection subnet and SNCP nodes
must be created.
n For VC12/VC3 services, the AMXC or EMXC board that supports low order
Context
n For release 4.0 NEs, including the OptiX 155/622H(Metro 1000), the OptiX
155/622(Metro 2050) the OptiX 2500+(Metro 3000), and the OptiX Metro 3100: You
need to congure unidirectional services from the west line board to the tributary board
and from the tributary board to the east line board.
n For release 5.0 NEs: You need to congure a bidirectional SNCP service routed from
both the east and west line boards to the tributary board.
Procedure
n For release 4.0 NEs
1. In the NE Explorer, click the NE and select Conguration > SDH Service
Conguration from the Function Tree.
2. Click Query to query the service information from the NE.
3. Click Create and the Create SDH Service dialog box is displayed.
4. Create the service from the tributary board to the east line board. Click Apply.
NOTE
n The service is unidirectional.
n Set Sink Out Subnet Protection to Protection.
6. Create the service from the west line board to the tributary board.
NOTE
n The service is unidirectional.
n Set Sink Out Subnet Protection to Protection.
7. Click Apply.
n For release 5.0 NEs
2. Click Query to query the service information from the NE.
3. Click Create SNCP Service and the Create SNCP Service dialog box is displayed.

4. Congure the Service Type, Direction, Service Level, SNCP parameters,

Working Service and Protection Service. Click OK, a prompt appears telling
you that the operation was successful.
NOTE
The service from the west line board to the tributary board should be the working service.
5. Click Close.
----End

Figure 12-9 SNCP service conguration
In Figure 12-9, NE1, NE2, NE3 and NE4 comprise a unidirectional SNCP ring. Eight
NE1-NE4 are release 5.0 NEs. According to E1 services ow, complete the following
congurations:
n Congure add/drop VC12 services at NE1: congure a bidirectional SNCP service, select
a west line board as the source of Working Service, an east line board as the source of
Protection Service, and a tributary board as the sink. The timeslot of both the source and
sink ranges from 1 to 8.

n Congure add/drop VC12 services at NE3: congure a bidirectional SNCP service, select
a west line board as the source of Working Service, an east line board as the source of
Protection Service, and a tributary board as the sink. The timeslot of both the source and
sink ranges from 1 to 8.
12.7 Conguration of Services Across Protection Subnets

station that services pass through according to trafc ow. When conguring services across
protection subnets, you need to focus on the service conguration of the NE at the connection
point of protection subnets. You need to decide how to congure services for the NE by
analyzing specic protection scheme and trafc ow.
Path Protection Ring or SNCP Ring with Non-Protection Chain

In the architectures of path protection (PP) ring with non-protection chain and SNCP ring with
non-protection chain, when conguring services across protection subnets, you must congure
SNCP services at the NE where the ring and the chain intersects. Other NEs and those in a
protection subnet have the same service conguration.
The following page describes trafc ow and service conguration process through a sample
conguration of a unidirectional PP ring with a non-protection chain. For other unidirectional
and bidirectional PP rings or SNCP ring with non-protection chain, you can congure SDH
services by referring to this example and analyzing trafc ow.

Figure 12-10 Path protection ring or SNCP ring with non-protection chain
In the gure, NE1, NE2, NE3 and NE4 comprise a unidirectional PP ring. NE4 and NE5
comprise a non-protection chain. Eight bidirectional E1 services are transmitted between
NE1 and NE5. The services take 1-8 VC12 timeslots on the tributary board, and 1-8 VC12
timeslots of the rst VC4 on the line board.
E1→NE1 tributary board→NE1 east line board→NE2 west line board→NE2 east
line board→NE3 west line board→NE3 east line board→NE4 west line board on the
ring→NE4 east line board on the chain→NE5 west line board→NE5 tributary board.
E1→NE5 tributary board→NE5 west line board→NE4 east line board on the chain→NE4
east line board on the ring→NE1 west line board→NE1 tributary board.
n Congure dual feed VC12 services at NE4: unidirectional services from the east line
board on the chain to the east line board on the ring, with the source and the sink timeslots

ranging from 1 to 8; unidirectional services from the east line board on the chain to the
west line board on the ring, with the source and the sink timeslots ranging from 1 to 8.
n Congure selectively received VC12 services at NE4: unidirectional SNCP services from
the west and the east line boards on the ring to the east line board on the chain, with the
source and the sink timeslots ranging from 1 to 8.
board and the west line board, with the source and the sink timeslots ranging from 1 to 8.
Path Protection Ring or SNCP Ring with Linear MSP

In the architectures of PP ring with 1+1 linear MSP, PP ring with 1:1 linear MSP, SNCP ring
with 1+1 linear MSP, and SNCP ring with 1:1 linea MSP, when conguring services across
protection subnets, you must congure SNCP services at the NE where the ring and the chain
intersects. Other NEs and those in a protection subnet have the same service conguration.
conguration of a bidirectional SNCP ring with a 1+1 linear MSP. For other protection
schemes, you can congure SDH services by referring to this example and analyzing trafc
ow.
Figure 12-11 Path protection ring or SNCP ring with linear MSP
In the gure, NE1, NE2, NE3 and NE4 comprise a bidirectional SNCP ring. NE4 and NE5
comprise a 1+1 linear MSP. Eight bidirectional E1 services are transmitted between NE1 and
NE5. The services take 1-8 VC12 timeslots on the tributary board, and 1-8 VC12 timeslots
of the rst VC4 on the line board.
If the network is running normally, the E1 services ow from NE1 to NE5 is as follows:
E1←→NE1 tributary board←→NE1 west line board←→NE4 east line board on the
ring←→NE4 active east line board on the chain←→NE5 active west line board←→NE5
tributary board.


unidirectional services from the tributary board to the west line board, with the source
and the sink timeslots ranging from 1 to 8; unidirectional SNCP services from the west
and the east line boards to the tributary board, with the source and the sink timeslots
ranging from 1 to 8.
n Congure dual feed VC12 services at NE4: unidirectional services from the active east
line board on the chain to the east line board on the ring, with the source and the sink
timeslots ranging from 1 to 8; unidirectional services from the active east line board
on the chain to the west line board on the ring, with the source and the sink timeslots
ranging from 1 to 8.
the west and the east line boards on the ring to the active east line board on the chain,
with the source and the sink timeslots ranging from 1 to 8.
board and the west line board, with the source and the sink timeslots ranging from 1 to 8.
Tangent Rings
In the architectures of MSP ring tangent to SNCP ring, and SNCP ring tangent to SNCP ring,
when conguring services across protection subnets, you must congure SNCP services at the
NE where the ring is tangent to the other ring. Other NEs and those in a protection subnet
have the same service conguration.
conguration of MSP ring tangent to SNCP ring. For other protection schemes, you can
congure SDH services by referring to this example and analyzing trafc ow.

Figure 12-12 Tangent rings
In the gure, NE1, NE2, NE3 and NE4 comprise a bidirectional MSP ring. NE3, NE5, NE6
and NE7 comprise a unidirectional SNCP ring. NE3 is the tangent point of two rings. Eight

E1 services are bidirectional. Service ow is as follows:
board→NE3 west line board 1→NE3 east line board 2→NE5 west line board→NE5 east
line board→NE6 west line board→NE6 tributary board.
board→NE3 west line board 2→NE3 west line board 1→NE2 east line board→NE2 west
line board→NE1 east line board→NE1 tributary board.
According to E1 services ow, you need to congure all NEs that E1 services pass through.
Here describes the conguration process for the tangent point NE3. For other NEs, they are
congured in the same way as those in a single protection subnet.
n Congure dual feed VC12 services at NE4: unidirectional services from the west line
board 1 on the MSP ring to the east line board 2 on the SNCP ring, with the source and
the sink timeslots ranging from 1 to 8; unidirectional services from the west line board
1 on the MSP ring to the west line board 2 on the SNCP ring, with the source and the
sink timeslots ranging from 1 to 8.
the west line board 2 and the east line board 2 on SNCP the ring to the west line board 1
on the MSP ring, with the source and the sink timeslots ranging from 1 to 8.
12.8 Changing Between SNCP and Normal Services

During a network expansion or cutover, you may need to change the type of a protection
subnet or change the protection type of services. This function enables you to change an SNCP
service to a normal service quickly and vice versa.
Context
The following changes are supported:
12.8.1 Changing a Normal Service to an SNCP Service

The SNCP service features the dual-feed and selective-receive function and is used to protect
cross-subnet services. When conguring SDH services station by station, you can perform this
operation to change a congured normal service to an SNCP service.
12.8.2 Changing an SNCP Service to a Normal Service
operation to change a congured SNCP service to a normal service.
12.8.1 Changing a Normal Service to an SNCP Service

operation to change a congured normal service to an SNCP service.
Prerequisites
n The normal service is created.
n Applies to release 5.0 NEs.

Procedure
Step 2 Click Query to query the SDH services from the NE.
Step 3 Click Display and select Expand to Unidirectional from the drop-down menu. Right-click a
desired non-SNCP service and select Convert to SNCP from the shortcut menu. The Specify
the Protection Service dialog box is displayed.
Step 4 Congure the protection service and click OK.
----End
12.8.2 Changing an SNCP Service to a Normal Service

operation to change a congured SNCP service to a normal service.
Prerequisites
n The SNCP service is created.
n Applies to release 5.0 NEs.
Procedure

Step 2 Click Query to query the SDH services from the NE.
Step 3 Click Unfold to display the service one by one. Right-click an SNCP service and select
Change to Normal Service from the shortcut menu. The protection service is then deleted.
----End

Operator Guide 13 Conguring Ethernet Services Station by Station
13 Conguring Ethernet
Services Station by Station
About This Chapter

When conguring Ethernet services station by station, you can specify the timeslot and route
for each NE individually. However, this conguration method is of relatively low efciency.
The trail function is recommended for service conguration if the trail function is provided in
the T2000.
Context
Congure Ethernet services station by station by the process below:
13.1 Ethernet Services

Ethernet services are characterised into: transparent transmission services over Ethernet,
convergent transmission services over Ethernet, EPL, EVPL, EPLn, EVPLn, RPR EVPL,
RPR EVPLn and QinQ services.
11.113.2 Creating Ethernet Services
Following the instructions below, you can create different types of Ethernet services station
by station.
11.213.3 Creating RPR Ethernet Services
Following the instructions below, you can congure RPR Ethernet services station by station.
13.4 Congure Ethernet QinQ Services
Following the instructions below, you can congure Ethernet QinQ services.
11.513.5 Setting the QoS
11.613.6 Conguring the Spanning Tree

13 Conguring Ethernet Services Station by Station Operator Guide
13.1 Ethernet Services

Ethernet services are characterised into: transparent transmission services over Ethernet,
convergent transmission services over Ethernet, EPL, EVPL, EPLn, EVPLn, RPR EVPL,
RPR EVPLn and QinQ services.
Transparent Transmission Services Over Ethernet

Transparent transmission services over Ethernet are used in point to point architecture. See
Figure 13-1.
Figure 13-1 Transparent Transmission Services Over Ethernet
Convergent Transmission Services over Ethernet

Convergent transmission services over Ethernet are used in point to point and point to
multipoint architectures. See Figure 13-2 and Figure 13-3.
n Share a PORT port
Figure 13-2 Ethernet Convergent Transmission Services Sharing a PORT Port
n Share a VCTRUNK port
Figure 13-3 Ethernet Convergent Transmission Services Sharing a VCTRUNK Port
EPL Services
The Ethernet private line (EPL) is of two types:
n Port
n Port + VLAN

EPL services of Port type can be transparently transmitted. See Figure 13-4.
Figure 13-4 EPL services of Port type
EPL services of Port + VLAN type can be converged to save port resources through several
services sharing a PORT port, or save bandwidth by sharing a VCTRUNK port. See Figure
13-5 and Figure 13-6.
n Share a PORT port
Figure 13-5 EPL services sharing a PORT port
n Share a VCTRUNK port
Figure 13-6 EPL services sharing a VCTRUNK port
EVPL Services
The Ethernet virtual private line (EVPL) can converge Ethernet services by identifying
the MPLS label. Therefore, multiple services with the same VLAN ID can share the same
bandwidth. See Figure 13-7.

Figure 13-7 EVPL services
EPLn Services
The Ethernet private LAN (EPLn) can realize Ethernet services that are dynamically shared
among multiple points, conforming to dynamic features of data services and saving bandwidth
resources. See Figure 13-9.
Figure 13-8 EPLn services
To avoid broadcast storm, the EPLn services cannot be set as a ring. If so, the rapid spanning
tree protocol (RSTP) must be started in the network.
EVPLn Services
Ethernet virtual private LAN (EVPLn) services can realize Ethernet services that are
dynamically shared among multiple points. For EVPLn, the difference from EPLn is that there
must be a label switch path (LSP) connected between any two nodes in the network to form a
MESH network. In addition, EVPLn broadcast feature avoids a broadcast storm effectively.
See Figure 13-8.

Figure 13-9 EVPLn services
RPR EVPL Services

Virtual private line services are transmitted on an RPR ring by combining the MPLS label and
RPR ring. LSP paths are congured between different connection points on different nodes
to realize the virtual private line services. The connection point can be a physical port, or
port + VLAN. See Figure 13-10.
Figure 13-10 RPR EVPL services
In this application scheme, RPR ring performs the functions of interface conversion and ber
extension. It is mainly used for accessing various services.

RPR EVPLn Services

EVPLn services are transmitted on the RPR ring by means of VLAN label. The characteristics
of the medium shared by RPR ring are fully used, and full interconnection between logical VBs
is realized. The VLAN label is used to identify different user domains, and further differentiate
users through different VLAN IDs on VB. See Figure 13-11.
Figure 13-11 RPR EVPLn services
In this application scheme, the RPR ring is mainly used for converging services and
constructing the Layer 2 VPN. It is usually used on the access layer and convergence layer.
QinQ Services
With the increase of network users, the number of VLAN IDs is facing a shortage. QinQ is an
embedded technology in VLAN, and tags users with multi-layer VLAN ID, so that VLAN
can be extended. Besides, QinQ can also extend the original LAN services to WAN services.
QinQ supports two kinds of tags: customer-layer C-TAG and service-layer S-TAG. You can
perform operations such as adding, stripping and exchanging of tags in different scenarios.
See Table 13-1.
NOTE
Stripping QinQ tags is the inverse process of adding tags.
Table 13-1 QinQ services

Operation Description Illustration
Adding Double-layer Tags Adds C-TAG and S-TAG
Based on PORT based on the PORT route.
Adding a Single-layer Tag Adds S-TAG based on the

Based on PORT PORT route.


Based on PORT+VLAN PORT+VLAN routes.
Exchanging the User Tag and Exchanges C-TAG and adds

Adding a Single-layer Tag S-TAG.
13.2 Create Ethernet Services

Following the instructions below, you can create different types of Ethernet services station
by station.
13.2.1 Conguring EPL Services

Use this procedure to congure an EPL service station by station.
13.2.2 Conguring EVPL Services
Use this procedure to congure an EVPL service station by station.
13.2.3 Conguring EVPL(QinQ) Services
Use this procedure to congure an EVPL(QinQ) service station by station.
13.2.4 Conguring EPLn Services
Use this procedure to congure an EPLn service station by station.
13.2.5 Conguring EVPLn Services
Use this procedure to congure an EVPLn service station by station.
13.2.1 Conguring EPL Services

Use this procedure to congure an EPL service station by station.
Prerequisites
(Metro 2050) and the OptiX 2500+ (Metro 3000) and the OptiX Metro 3100, the
protection subnet must be created.
n Applies to EFS/EFT/EGS/EGT/EMS boards.
n The Ethernet processing board and the Ethernet interface board must be installed.
Procedure
Step 1 Congure the attributes of ports on the Ethernet board and bound paths.
1. Congure the attributes of an internal port.
NOTE
The value of Port Type must be PE.
2. Congure the attributes of an external port.
NOTE

3. Congure bound paths.

Step 2 Create a cross-connection between the Ethernet and the line boards.
1. In the NE Explorer, click the NE and select Conguration > SDH Service Conguration
NOTE
3. Create the cross-connection between the Ethernet and the line boards.
NOTE
Create the VC12, VC3 or VC4 cross-connection as needed.
4. Click Apply or OK.

Step 3 Create an EPL service.
1. In the NE Explorer, click an Ethernet board and select Conguration > Ethernet Service
> Ethernet Line Service from the Function Tree.
2. Click New and the Create Ethernet Line Service dialog box is displayed.
3. Complete the information of the EPL service. Select an appropriate value in the Service
Direction, Source Port， Sink Port，and input an appropriate value in the Source
VLAN, Sink VLAN elds.
NOTE
n Under Port Attributes, some parameters can be modied. If the port attributes have been
set, take the default values.
n If there is no appropriate path in the Bound Path eld, click Conguration to bind new paths.
For detailed operations, refer to "Conguring Bound Path".
n To congure the VLAN ID, you can set the same or different VLAN ID for both the source and
the sink ports.

----End
13.2.2 Conguring EVPL Services

Use this procedure to congure an EVPL service station by station.

Prerequisites
n Applies to EFS/EGS/EMS boards.
Procedure
NOTE

Step 3 Create an EVPL service.
2. Check the Display MPLS Shared Service check box in the lower right area.
4. Complete the information of the EVPL service. Select an appropriate value in the Service
Type, Service Direction, Source Port, Source Tunnel, Source VC, Source VLAN,
Sink Port, Sink Tunnel, Sink VC and Sink VLAN elds.

NOTE

----End
13.2.3 Conguring EVPL(QinQ) Services

Use this procedure to congure an EVPL(QinQ) service station by station.
Prerequisites
n Applies to EGS4/EMS4 boards.
Procedure
NOTE

Step 3 Create an EVPL(QinQ) service.
2. Check the Display QinQ Shared Service check box.
4. Complete the information of the EVPL(QinQ) service. Select an appropriate value in the
Service Type, Service Direction, Operation Type， Source Port, Source C-VLAN,
Source S-VLAN, Sink Port, Sink C-VLAN and Sink S-VLANelds.

NOTE

----End
13.2.4 Conguring EPLn Services

Use this procedure to congure an EPLn service station by station.
Prerequisites

Procedure
NOTE
NOTE

Step 3 Create an EPLn service.
> Ethernet LAN Service from the Function Tree. Select the VB Mount Port tab.
2. Click New and the Create Ethernet LAN Service dialog box is displayed.
NOTE
3. Complete the information of the EPLn service. Enter a VB name.

4. Click Congure Mounted Port. The VB Mount Port Conguration dialog box is
displayed. Select the appropriate port in the Available Mounted Ports and click .
5. Click OK.
NOTE
If there is no appropriate path in the Binding Path eld, click Conguration to bind new paths.
For detailed operations, refer to "Conguring Binding Path".
Step 4 Create the VLAN ltering table.

1. In the NE Explorer, click the NE and select Conguration > Ethernet Service >
Ethernet LAN Service from the Function Tree. Select the VLAN tab.
2. Click New and the Create VLAN dialog box is displayed.
3. Enter the information of the VLAN. Select a VB, specify a VLAN ID, and select the
appropriate ports as forwarding ports.
4. Click OK or Apply. A prompt appears telling you that the operation was successful.
----End
13.2.5 Conguring EVPLn Services

Use this procedure to congure an EVPLn service station by station.

Prerequisites
Procedure
NOTE
NOTE

Step 3 Create an EVPLn service.
> Ethernet LAN Service from the Function Tree. Click the VB Mount Port tab and
check the Display Shared Service check box.
NOTE
EVPLn can be congured only when the Display Shared Service check box is checked.
3. Complete the information of the EVPLn service. Enter a VB name.

4. Click Congure Mounted Port and the VB Mount Port Conguration dialog box is
displayed. Select the appropriate port in the Available Mounted Ports pane and click
.
5. Click OK.
NOTE
If there is no appropriate path in the Binding Path eld, click Conguration to bind new paths.
For detailed operations, refer to "Conguring Binding Path".

2. Click New and the Create VLAN dialog box is displayed.
----End
13.3 Create RPR Ethernet Services

Following the instructions below, you can congure RPR Ethernet services station by station.
13.3.1 Conguring RPR EVPL Services

Use this procedure to congure an EVPL service on the RPR ring.
13.3.2 Conguring RPR EVPLn Services
Use this procedure to congure an EVPLn service on the RPR ring.
13.3.1 Conguring RPR EVPL Services

Use this procedure to congure an EVPL service on the RPR ring.
Prerequisites
n Applies to EMR0/EGR2 boards.
Procedure
Step 1 Congure RPR topology information.
1. In the NE Explorer, select a board and select Conguration > RPR Management >
Topology Information from the Function Tree. Select the Local Node Information tab.
2. Complete the information of the local node, including Node No and Node Name.
3. Start the RPR protocol. Set the RPR Protocol parameter to Enabled.
4. Set protection parameters, including Slow Timing Value (ms), RPR topology timing
value(s), Protection mode, Protection delay (ms), Protection restoration mode and
Protection wait-to-restore (s).
NOTE
In the same RPR ring, set the same value in the Protection Mode eld.
NOTE
For the EMR0 board, PORT1 corresponds to a GE interface and the other ports to an FE interface.
For the EGR2, both PORT1 and PORT 2 correspond to a GE interfaces.


1. In the NE Explorer, click the NE and select Conguration > SDH service conguration
3. Create the cross-connection between Ethernet board and line board.
NOTE
The cross-connection should be at the same level as the bound path.

Step 4 Create an EVPL service.
1. In the NE Explorer, select a board and select Conguration > Ethernet Service >
Ethernet Line Service from the Function Tree.
3. Complete the information of the EVPL service. Select an appropriate value in the Service
Type, Service Direction, Source Port, Source Tunnel, Source VC, Source VLAN, Sink
Port, Sink Tunnel, Sink VC, Sink VLAN, Up Loop Direction and Sink Node elds.
NOTE
n EPL services are transmitted on the RPR ring by means of MPLS label, the service type can
only be EVPL or Transit.
n For the EVPL service transmitted on the RPR ring, the source/sink port can only be PORT or
RPR port.
n The port attribute of the RPR port must be P, and the encapsulation format is MartinioE.
n If the port attribute of the PORT port is P, the encapsulation format can only be MartinioE.
n Sink Node is specic to RPR rings, which is used to identify the destination node of this EVPL
service on the RPR ring.
----End
13.3.2 Conguring RPR EVPLn Services

Use this procedure to congure an EVPLn service on the RPR ring.
Prerequisites
n Applies to EMR0/EGR2 boards.
Procedure
Step 1 Congure RPR topology information.
1. In the NE Explorer, select a board and select Conguration > RPR Management >
Topology Information from the Function Tree. Select the Local Node Information tab.
2. Complete the information of the local node, including Node No and Node Name.
3. Start the RPR protocol. Set the RPR Protocol parameter to Enabled.
4. Set protection parameters, including Slow Timing Value (ms), RPR topology timing
value(s), Protection mode, Protection delay (ms), Protection restoration mode and
Protection wait-to-restore (s).
NOTE
In the same RPR ring, set the same value in the Protection Mode eld.

NOTE
For the EMR0 board, PORT1 corresponds to a GE interface and the other ports to an FE interface.
For the EGR2, both PORT1 and PORT 2 correspond to a GE interface.

1. In the NE Explorer, click the NE and select Conguration > SDH service conguration
3. Create the cross-connection between Ethernet board and line board.
NOTE
The cross-connection should be at the same level as the bound path.

Step 4 Create an EVPLn service.
Ethernet LAN Service from the Function Tree.
3. Complete the information of the EVPLn service. Enter a VB ID and a VB name.
4. Click Congure Mounted Port and the VB Mount Port Conguration dialog box is
displayed. Select the appropriate port in the Available Mounted Ports pane and click
.
NOTE
n The options for Mount Port are PORT port and RPR port.
n The Port Type of the PORT port can be P or PE.
n The Port Type of the RPR port must be P . The encapsulation format of the RPR port can be
only stack VLAN for N1 series boards, and MartinioE or stack VLAN for N2 series boards.
5. Click OK.
2. Click NEW and the Create VLAN dialog box is displayed.
4. Click Apply or OK. A prompt appears telling you that the operation was successful.
----End
13.4 Congure Ethernet QinQ Services

Following the instructions below, you can congure Ethernet QinQ services.
13.4.1 QinQ Services

embedded technology in VLAN, and can tag users with multi-layer VLAN ID, so that VLAN
13.4.2 Adding Double-Layer Tags Based on PORT
When the data packet has no VLAN tag, the C-TAG and S-TAG are added through the PORT
route.
13.4.3 Adding a Single-layer Tag Based on PORT
The S-Tag label is added to the original packet through the port route.

13.4.4 Adding a Single-layer Tag Based on PORT+VLAN

When the data packet already has a C-TAG, an S-TAG is added through the PORT+VLAN
route.
13.4.5 Exchanging the User Tag and Adding a Single-Layer Tag
When the data packet already has a C-TAG, its C-TAG is exchanged, and then an S-TAG is
added through the PORT+VLAN route.This operation satises the need when the user wants to
exchange a private tag with a generic tag.
13.4.1 QinQ Services

embedded technology in VLAN, and can tag users with multi-layer VLAN ID, so that VLAN
QinQ supports two kinds of tags: customer-layer C-TAG and service-layer S-TAG. You can
perform operations such as adding, stripping and exchanging of tags in different scenarios.
Table 13-2 lists the common QinQ services.
NOTE
Stripping QinQ tags is the inverse process of adding tags.
Table 13-2 Common QinQ services

Adding Double-layer Tags Adds C-TAG and S-TAG
Based on PORT based on the PORT route.

Based on PORT PORT route.

Based on PORT+VLAN PORT+VLAN routes.
Exchanging the User Tag and Exchanges C-TAG and adds

Adding a Single-layer Tag S-TAG.
13.4.2 Adding Double-Layer Tags Based on PORT

When the data packet has no VLAN tag, the C-TAG and S-TAG are added through the PORT
route.

Prerequisites
n Applies to EMS4 and EGS4 boards.
Procedure
n Conguring Ethernet Interfaces and Bound Paths
1. In the NE Explorer, click the Ethernet board and select Conguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select
External Port.
2. Click the General Attributes tab. Set Enable Port to Enabled. Click Apply.
n Conguring Cross-Connections Between the Ethernet Board and the Line Board
2. Click Create. The Create SDH Service dialog box is displayed.
3. Create cross-connections between the Ethernet board and the line board.
NOTE
The level of the cross-connection must be the same as that of the bound path.

n Adding Double-Layer Tags Based on PORT
3. Click New and the Create EPL Service dialog box is displayed.
4. According to the gure above, perform the following settings to create the service.
– Service Type: EVPL(QINQ)
– Service Direction: Unidirectional
– Operation Type: Add S-VLAN and C-VLAN
– Source Port: PORT1
– Sink Port: VCTRUNK1
– Sink C-VLAN(e.g. 1, 3-6):20
– Sink S-VLAN :20
5. Click Apply.
----End
13.4.3 Adding a Single-layer Tag Based on PORT

The S-Tag label is added to the original packet through the port route.
Prerequisites

Procedure
n Conguring Ethernet Interfaces and Bound Paths
Interface Management > Ethernet Interface from the Function Tree. Select
External Port.
n Conguring Cross-Connections Between the Ethernet Board and the Line Board
NOTE

n Adding a Single-Layer Tag Based on PORT
2. Check the Display QINQ Shared Service check box.
– Service Type: EVPL(QinQ)
– Service Direction: Unidirectional
– Operation Type: Add S-VLAN
– Source Port: PORT1
– Sink Port: VCTRUNK1
– Sink S-VLAN(e.g. 1, 3-6): 20
5. Click Apply.
----End
13.4.4 Adding a Single-layer Tag Based on PORT+VLAN

When the data packet already has a C-TAG, an S-TAG is added through the PORT+VLAN
route.
Prerequisites
Procedure
Step 1 Conguring Ethernet Interfaces and Bound Paths

1.In the NE Explorer, click the Ethernet board and select Conguration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
Step 2 Conguring Cross-Connections Between the Ethernet Board and the Line Board
NOTE

Step 3 Adding a Single-layer Tag Based on PORT+VLAN
For PORT1:
n Service Type: EVPL(QinQ)
n Service Direction: Unidirectional
n Operation Type: Add S-VLAN
n Source Port: PORT1
n Source C-VLAN(e.g. 1, 3-6): 20
n Sink Port: VCTRUNK1
n Sink C-VLAN(e.g. 1, 3-6): 20
n Sink S-VLAN: 30
5. Click Apply.
6. Repeat the steps above to create the route from PROT2 to VCTRUNK1.
For PORT2:
n Operation Type: Add S-VLAN
n Sink S-VLAN: 40
----End
13.4.5 Exchanging the User Tag and Adding a Single-Layer Tag

When the data packet already has a C-TAG, its C-TAG is exchanged, and then an S-TAG
is added through the PORT+VLAN route.

This operation satises the need when the user wants to exchange a private tag with a generic
tag.
Prerequisites
Procedure
Step 1 Conguring Ethernet Interfaces and Bound Paths
Interface Management > Ethernet Interface from the Function Tree.
2. Click the Basic Attributes tab. Set Enable Port to Enabled. Click Apply.
3. Congure bound paths. For detailed operations, refer to "Conguring Bound Paths".
Step 2 Conguring Cross-Connections Between the Ethernet Board and the Line Board
NOTE

Step 3 Exchanging the User Tag and Adding a Single-layer Tag
Service > Ethernet Line Service from the Function Tree.
For PORT1:
n Operation Type: Translate C-VLAN and Add S-VLAN
n Sink S-VLAN: 30
5. Click Apply.
6. Repeat the steps above to create the route from PROT2 to VCTRUNK1.
For PORT2:
n Operation Type: Translate C-VLAN and Add S-VLAN


n Sink S-VLAN: 40
----End
13.5 Setting the QoS

Prerequisites
n The Ethernet service must be created.
Procedure
Step 1 In the NE Explorer, click a board and select Conguration > QoS Management > Flow
Step 2 Click the CAR Conguration tab. Click New and the Create CAR window is displayed.
Step 3 Set the CAR ID and other parameters.
Step 4 Click OK. The Operation Result window is displayed. Click Close.
Step 5 Optional: If the board provides support for creating CoS, click the CoS Conguration tab.
Click New and the Create CoS window is displayed.
Step 6 Optional: Set the CoS ID and other parameters.
Step 8 Optional: If the board provides support for creating ow, click the Flow Conguration tab.
Click Create and the Create Flow window is displayed.
Step 9 Optional: Set the Flow Type and other parameters.
Step 11 Optional: Double-click in the Bound CAR and Bound CoS elds to select a CAR ID and a
CoS ID respectively. The selected IDs are bound to the ow, and thus the ow has relevant
CAR and CoS attributes.
----End
13.6 Conguring the Spanning Tree

Prerequisites
n The VB must be created.

Procedure
Step 1 In the NE explorer, click a board and select Conguration > Layer-2 Switching Management
> Spanning Tree from the Function Tree.
Step 2 Set the priority and other attributes of each VB port and click Apply.
NOTE
The port with a smaller MAC address must have a higher priority.
Step 3 Click the Protocol Enabled tab.

Step 4 Set the Protocol Enabled parameter to Enabled. Select a working mode as needed. Click
Apply.
Step 5 Optional: Click the Port Parameters tab to set VB port parameters.
Step 6 Optional: Click the Bridge Running Information tab to view the bridge information.
Step 7 Optional: Click the Port Running Information tab to view the VB port information.
----End

Operator Guide 14 Conguring ATM Services
14 Conguring ATM Services
About This Chapter

Following the instructions below, you can congure ATM services.
14.1 SDH NNI

An SDH network-to-network interface (NNI) refers to an interface congured with a logic
system but without a ber connection.
14.2 Setting the VC4 Port of an ATM Board as an SDH NNI
An SDH network supports the access of ATM services. The VC4 ports provided by ATM
boards are at the network edge and thus are not within the T2000 management scope. In this
case, an SDH NNI is used to set up communication with the equipment which is at the network
edge. That is why the ports of ATM boards should be set as SDH NNIs.
14.316.5.1 Installing the ATM Interface Board
For ATM service processing boards with no interface, you must create an interface board
before conguring services or ports.
14.4 Conguring Port Attributes for ATM Boards
Following the instructions below, you can congure port attributes for ATM boards. The ports
on ATM boars are divided into internal ports and external ports. The external port refers to the
PORT port for service access. The internal port refers to the VCTRUNK port. The internal
ports must also be bound to SDH timeslots at the bearer layer.
14.5 Creating a Cross-Connection Between the ATM and the Line Boards
Use this procedure to congure SDH services that carry ATM services.
14.6 Conguring ATM Trafc
Use this procedure to congure ATM trafc.
14.7 Conguring ATM Cross-Connections
Use this procedure to congure ATM cross-connections.
14.8 Conguring Protection Groups and Protection Pairs for ATM Services
Use this procedure to congure protection groups and protection pairs for ATM services.
14.9 IMA
With the Inverse Multiplexing for ATM (IMA) technology, an ATM cell ow is demultiplexed
to multiple low-speed links, which are then multiplexed at the far end so that the cell ow
is restored to its original form. In this way, the multiplexing of multiple low-speed links
becomes exible and convenient.
14.10 Conguring ATM IMA Groups
Use this procedure to congure ATM IMA groups.

14 Conguring ATM Services Operator Guide
14.1 SDH NNI

An SDH network-to-network interface (NNI) refers to an interface congured with a logic
system but without a ber connection.
The rules for conguring an SDH NNI for release 4.0 or 5.0 NEs:
n For release 4.0 NEs, including the OptiX 155/622H(Metro 1000), the OptiX
155/622(Metro 2050) the OptiX 2500+(Metro 3000), and the OptiX Metro 3100, if an
interface without a ber connection is mapped to a logic system (of any type except PP,
SNCP and DNI) and does not belong to any protection subnet, the interface is regarded as
an SDH NNI in the T2000 by default. If an interface is not mapped to a logic system, you
must congure the interface to an SDH NNI on the T2000 manually.
n For release 5.0 NEs, all interfaces without ber connections are regarded as SDH NNIs,
without the need to congure them manually in the T2000.
14.2 Setting the VC4 Port of an ATM Board as an SDH NNI

An SDH network supports the access of ATM services. The VC4 ports provided by ATM
boards are at the network edge and thus are not within the T2000 management scope. In this
case, an SDH NNI is used to set up communication with the equipment which is at the network
edge. That is why the ports of ATM boards should be set as SDH NNIs.
Prerequisites
n Applies to the OptiX 2500+ (Metro 3000) and the OptiX Metro 3100.
n The ATM board must be created.
Procedure
Step 2 Select the NE where the ATM board resides. Right-click and select SDH NNI Management
from the shortcut menu. The SDH NNI Management dialog box is displayed.
Step 3 Select the appropriate VC4 port of the ATM board in the Uncreated Optical Interface list
and click 。
Step 4 Click Close and the setting is complete.
----End
14.3 Installing the ATM Interface Board

Prerequisites
n The ATM service processing board must be installed.
Procedure
Step 1 In the NE Explorer, select an ATM board and select Conguration > Interface Board

Step 2 If you want to query the information of an ATM interface board from the NE, click Query.
Step 3 If you want to create the information of an ATM interface board, click Create. Alternatively,
right-click the Interface board list eld and select Create.
Step 4 Select the newly created interface board, and modify the values of Interface Slot and Logical
Interface Board at NM to be the same as those in the NE.
Step 5 Click Apply. A prompt appears telling you that the operation was successful.
----End
14.4 Conguring Port Attributes for ATM Boards

Following the instructions below, you can congure port attributes for ATM boards. The ports
on ATM boars are divided into internal ports and external ports. The external port refers to the
PORT port for service access. The internal port refers to the VCTRUNK port. The internal
ports must also be bound to SDH timeslots at the bearer layer.
14.4.116.5.2 Conguring Internal Ports

When conguring ATM services or performing loopback, you need to congure the internal
and external port attributes for an ATM interface board.
14.4.216.5.3 Conguring External Ports
14.4.3 Conguring Bound Paths
Use this procedure to congure bound paths.
14.4.1 Conguring Internal Ports

Prerequisites
n Except for the AL1 board, the path must be bound before conguring the internal port.
Procedure
Step 1 In the NE Explorer, select an ATM board and select Conguration > ATM Interface
Management > ATM Interface Management from the Function Tree. Select the Internal
Port radio button.
Step 2 Click Query to query the internal port attributes of the ATM board.
Step 3 Select an internal port of the ATM board. Set the internal port attributes as needed.
----End
14.4.2 Conguring External Ports


Prerequisites
Procedure
Management > ATM Interface Management from the Function Tree. Select the External
Port radio button.
Step 2 Click Query to query the external port attributes of the ATM board.
Step 3 Select an external port of the ATM board. Set the external port attributes as needed.
----End
14.4.3 Conguring Bound Paths

Use this procedure to congure bound paths.
Prerequisites
n The ATM board is already created.
Procedure
Step 1 On the Main Topology, double-click an NE and the NE Panel is displayed. Right-click an ATM
board and select ATM Conguration > Interface Management.
Step 2 Select Conguration > ATM Interface Management > ATM Bound Path Management
Step 3 Click Query to view the bound paths.
Step 4 Click Conguration and the Bound Path Conguration dialog box is displayed.

Step 5 Select a VCTRUNK port from the Congurable Ports drop-down list. Select direction and a
bearer timeslot in the Available Bound Paths group box. Then Click .
Step 6 Click OK or Apply. A prompt dialog box is displayed.
Step 7 Click Yes. The Operation Result dialog box is displayed telling you that the operation
succeeded.
----End
14.5 Creating a Cross-Connection Between the ATM and

the Line Boards
Use this procedure to congure SDH services that carry ATM services.
Prerequisites
n Applies to the OptiX 155/622H (Metro 1000), the OptiX 2500+ (Metro 3000), the OptiX
Metro 3100, the OptiX OSN 1500, the OptiX OSN 2500, the OptiX OSN 3500 and the
OptiX OSN 7500.
n The ATM board must be installed.
Procedure
Step 3 Create a cross-connection between the ATM board and line board.
Step 4 Click Apply or OK.

----End

14.6 Conguring ATM Trafc

Use this procedure to congure ATM trafc.
Prerequisites
OptiX OSN 7500.
n The ATM board is already installed.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > ATM Trafc Management
Step 2 To query the trafc information of an ATM board, click Query. The trafc information on the
NE is displayed and that on the T2000 is overwritten.
Step 3 Right-click in the ATM Trafc Table and select Create from the shortcut menu. The Create
ATM Trafc Descriptor dialog box is displayed.
Step 4 Set the trafc parameters such as Service Type, Trafc Type, Clp01Pcr, Clp0Pcr, Clp01Scr,
Clp0Scr, MCR and MBS.
Step 5 Click Apply or OK. The Operation Result dialog box is displayed telling you that the
operation succeeded.

----End
14.7 Conguring ATM Cross-Connections

Use this procedure to congure ATM cross-connections.
Prerequisites
OptiX OSN 7500.
n The cross-connection between the ATM board and the line board is congured.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > ATM Service Management
Step 2 Right-click in Cross-Connection and select Add Connection from the shortcut menu. The
Add ATM Cross-Connection dialog box is displayed.
Step 3 Complete the settings as needed in the dialog box.
NOTE
The positive and reverse trafc descriptors can be set to only the values congured in ATM Trafc
Management. Otherwise, an error message will be displayed.

----End
14.8 Conguring Protection Groups and Protection Pairs

for ATM Services
Use this procedure to congure protection groups and protection pairs for ATM services.
Prerequisites
OptiX OSN 7500.
n ATM cross-connections are already congured.
Context
If the protection type of ATM cross-connections is set to Non Protection, then you do not
need to congure protection groups and protection pairs. The 1+1 protection for ATM
cross-connections must be of the PVP and P2P types.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > ATM Service Management
Step 2 To create a protection group, right-click in Protection Group and select Add Protection
Group from the shortcut menu. The Add Protection Group dialog box is displayed.
Step 3 Set the Protection Type, Switching Direction, Switching Type, Revertive Mode, Pause
Time and WTR Time parameters of the protection group.
NOTE
When setting parameters, note the following:
n If the Switching Direction is set to Source, the two cross-connections in a protection pair must have
the same sink but different sources.
n If the Switching Direction is set to Sink, the two cross-connections in a protection pair must have
the same source but different sinks.

Step 5 To add a pair of cross-connections into the protection group, right-click in Cross-Connection
and select Add into Protection Group from the shortcut menu. The Add Connection into
Protection Group dialog box is displayed.
Step 6 Set the Working Connection ID, Protection Connection ID and Protection Group ID
parameters.
----End
14.9 IMA
With the Inverse Multiplexing for ATM (IMA) technology, an ATM cell ow is demultiplexed
to multiple low-speed links, which are then multiplexed at the far end so that the cell ow
is restored to its original form. In this way, the multiplexing of multiple low-speed links
becomes exible and convenient.
This functionality applies to E1 interconnections between ATM networks, and has no special
requirement for service types.
Figure 14-1 ATM IMA group
14.10 Conguring ATM IMA Groups

Use this procedure to congure ATM IMA groups.
Prerequisites
n Applies to N1IDL4 and N1IDQ1 boards.
n The cross-connection between the ATM board and the line board is created.

Context
CAUTION
In an IMA group, only VC12 paths can be bound to the VCTRUNK.
Procedure
Step 1 In the NE Explorer, select a board and select Conguration > ATM Interface Management
> ATM IMA Management from the Function Tree.
Step 2 Conguring IMA Group Parameters
1. Click the IMA Group Management tab.
2. Click New and the Create IMA Group dialog box is displayed.
3. Set the VCTRUNK, IMA Protocol Version, IMA Transmit Frame Length and IMA
Group Conguration Mode parameters of the IMA group.
4. Click Apply or OK. The Operation Result dialog box is displayed saying "Operation
succeeded".
Step 3 Conguring E1 Link Parameters
1. Click the E1 Link Parameter Management tab.
2. Set Enable/Disable Cell Payload Scramble and Link Frame Format.
3. Click Apply.
Step 4 Conguring the IMA 1.0 Mode
1. Click the IMA1.0 Mode Management tab.
2. Set the IMA 1.0 mode.
3. Click Apply .
----End

Operator Guide 15 Conguring Broadcast Services
15 Conguring Broadcast Services
About This Chapter

Following the instructions below, you can congure broadcast data services on the T2000.
15.1 Broadcast Data Services

You can set the RS-232 or RS-422 level broadcast data ports (Serial1-Serial4) to implement
universal asynchronous receiver/transmitter (UART) full-duplex communication. The data is
transmitted transparently, and there is no need to congure port rate or transmission control
protocols on the T2000. The maximum bit rate can be 19.2 kbit/s. The communication
mode can be congured as point to point or point to multipoint and data can be broadcasted
to multiple optical ports.
15.2 Conguring Broadcast Data Ports
Use this procedure to congure broadcast data ports.

15 Conguring Broadcast Services Operator Guide
15.1 Broadcast Data Services

You can set the RS-232 or RS-422 level broadcast data ports (Serial1-Serial4) to implement
universal asynchronous receiver/transmitter (UART) full-duplex communication. The data is
transmitted transparently, and there is no need to congure port rate or transmission control
protocols on the T2000. The maximum bit rate can be 19.2 kbit/s. The communication
mode can be congured as point to point or point to multipoint and data can be broadcasted
to multiple optical ports.
The following page takes the OptiX 2500+(Metro 3000) as an example to describe more
about broadcast data services.
Broadcast data services use overhead bytes (X1-X4) as the broadcast data communication
channel, show inFigure 15-1. Broadcast data ports (Serial1-Serial4) are located in the interface
area on the mother board in the back of a subrack. See Figure 15-2. The DB9 connector is
used, whose pins are dened in Table 15-1.
Figure 15-1 Overhead Byte
Figure 15-2 The position of broadcast data ports

Operator Guide 15 Conguring Broadcast Services
Table 15-1 Denitions of the broadcast data port pins

Front view Pin No. Signal Description
1 PGND Protection ground
2 RS232RX Data receiving end
of RS232
3 RS232TX Data transmitting
end of RS232
4 N.C No connection
5 GND Grounding
6 RS422T+ Positive data
transmitting end
of RS422
7 RS422T- Negative data
transmitting end
of RS422
8 RS422R+ Positive data
receiving end of
RS422
9 RS422R- Negative data
receiving end of
RS422
Requirements for the Environment Monitor

The interface uses RS-232 level, logic 1 being -5 V to -15 V and logic 0 being +5 V to +15 V.
When there is no data transmitted, the port is at RS-232 high level (about -9 V), and at any
one time only one slave station can transmit data to the master station. The maximum bit
rate is not more than 19.2 kbit/s.
15.2 Conguring Broadcast Data Ports

Use this procedure to congure broadcast data ports.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and select Conguration > Orderwire from the Function
Tree. Click the Broadcast Data Port tab.
Step 2 Click Query to query desired information from the NE.
Step 3 Select an overhead byte from the overhead byte drop-down list.
Step 4 Set the Working Mode, Broadcast Data Source and Broadcast Data Sink parameters.
Step 5 Click Apply.
----End

Operator Guide 16 Conguring Board Parameters
16 Conguring Board Parameters
About This Chapter

During the service conguration or test on SDH NEs, board parameters may need to be
congured.
Context
The following boards are included:
16.1 Conguring SDH Boards

When conguring SDH board parameters, you can usually use the default values. When
special functions like TCM are used during conguration or maintenance, however, you need
to modify the SDH board parameters as needed.
16.2 Conguring PDH Boards
When conguring PDH board parameters, you can usually use the default values. When
functions like loopback are used during conguration or maintenance, however, you need to
modify the PDH board parameters as needed.
16.3 Conguring Ethernet Boards
During the service conguration or test on an Ethernet board, the Ethernet board attributes
must be congured.
16.4 Conguring Ethernet Link Aggregation Groups
Through Ethernet link aggregation, multiple links connected to the same equipment can be
bound together.
16.5 Conguring ATM Boards
During the service conguration or test on an ATM board, the ATM board attributes must
be congured.
16.6 Conguring Optical Booster Ampliers
When using an optical booster amplier board, you need to set the board according to the
required output optical power and other factors.
16.7 Conguring TDA Boards
Before conguring audio services for a TDA board, you need to congure the clock source
traced by the board and select the TDA feeding mode according to the service type.
16.8 Conguring Board Protection
On SDH NEs, redundant boards can be used to provide board-level protection for major
boards so that the equipment reliability will be improved. Board protection can be congured
as long as redundant boards are available.

16 Conguring Board Parameters Operator Guide
16.1 Conguring SDH Boards

When conguring SDH board parameters, you can usually use the default values. When
special functions like TCM are used during conguration or maintenance, however, you need
to modify the SDH board parameters as needed.
Prerequisites
n The SDH NE must be created.
Procedure
Step 1 In the NE Explorer, select an SDH board, and select Conguration > SDH Interface from the
Function Tree.
Step 2 Click the By Function radio button, and select a function to from the drop-down list.
Step 3 Click Query to query the parameter values.

Step 4 Double-click a eld and specify a value.
Step 5 Click Apply. Click OK. A prompt appears telling you that the operation was successful.
Click Close.
----End
16.2 Conguring PDH Boards

When conguring PDH board parameters, you can usually use the default values. When
functions like loopback are used during conguration or maintenance, however, you need to
modify the PDH board parameters as needed.
Prerequisites
n The PDH board must be created.
Procedure
Step 1 In the NE Explorer, select a PDH board, and select Conguration > PDH Interface from the
Function Tree.
Step 2 Select By Function, select a function from the drop-down list.


Step 5 Click Apply. Click OK. A prompt appears telling you that the operation was successful.
Click Close.
----End
16.3 Conguring Ethernet Boards

During the service conguration or test on an Ethernet board, the Ethernet board attributes
must be congured.
Context
Follow the process given below to congure an Ethernet board:
1. 16.3.1 Creating Ethernet Interface Boards

For Ethernet service processing boards with no interfaces, you must create an interface
board before conguring services or ports. For release 5.0 NEs, you can add the interface
board in the NE Panel. For release 4.0 NEs, you need to add the interface board in the
NE Explorer.
2. 16.3.2 Conguring Internal Ports
You can congure the internal port of an Ethernet board, that is, the VCTRUNK port.
You can set encapsulation and mapping of Ethernet data packets, enable LCAS, and
bind a VCTRUNK port to the timeslot of an SDH layer. In addition, you can set MPLS
encapsulation protocol as needed.
3. 16.3.3 Conguring External Ports
You can congure the external port of an Ethernet board, that is, the PORT port. Primarily
the basic attributes, ow control and tag attributes of a PORT port are to be congured.
The MPLS encapsulation protocol and advanced attributes can also congured as needed.
16.3.1 Creating Ethernet Interface Boards

For Ethernet service processing boards with no interfaces, you must create an interface board
before conguring services or ports. For release 5.0 NEs, you can add the interface board in
the NE Panel. For release 4.0 NEs, you need to add the interface board in the NE Explorer.
Prerequisites
n The Ethernet service processing board must be created.

Procedure
Step 1 Double-click the NE you want to congure on the Main Topology. The NE Panel is displayed.
Right-click an Ethernet board and choose Ethernet Conguration > Ethernet Interface
Board Management from the shortcut menu.
Step 2 If you want to query the information about Ethernet boards from the NE, click Query.
Step 3 If you want to create the information of an Ethernet interface board, click Create, or right-click
and choose Create from the shortcut menu.
----End

You can congure the internal port of an Ethernet board, that is, the VCTRUNK port. You can
set encapsulation and mapping of Ethernet data packets, enable LCAS, and bind a VCTRUNK
port to the timeslot of an SDH layer. In addition, you can set MPLS encapsulation protocol
as needed.
Prerequisites
n The Ethernet board must be created.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Conguration > Ethernet Interface
Management > Ethernet Interface from the Function Tree. Click the Internal Port radio
button.
Step 2 If you want to set the Tag attribute for the port, click the TAG Attribute tab. Set the TAG,
Default VLAN ID, VLAN priority and Entry detection elds as needed. Click Apply. A
prompt appears telling you that the operation was successful.
NOTE
n If you disable Entry detection, Ethernet data packets are transparently transmitted.
n The Tag label is used for setting which type of data packets can be processed.
– A port set to Tag Aware only processes packets with a Tag label and those data packets without a
Tag label are discarded. The Default VLAN ID and the VLAN priority elds cannot be edited.
– A port set to Access only processes data packets without a Tag label and all those data packets
with a Tag label are discarded. The data packets without a tag label are added with a tag label
based on the VLAN ID of the port.
– A port set to Hybrid processes the two types of data packets and adds a Tag label based on its
VLAN ID to the data packets without a tag label.
n The value of the Default VLAN ID eld ranges from 0 to 4095.
n VLAN priority indicates the QoS level, which can be 0 to 7 in an ascending order. When the
network is busy, data packets of higher VLAN priority are processed rst while those of lower
priority may be discarded.
Step 3 If you want to set the encapsulation/mapping mode for the port, click the
Encapsulation/Mapping tab. Select a mapping protocol and set its parameters. Click Apply.
NOTE
n For the ET1/ET1D/ET1S boards, the encapsulation protocol is ML-PPP. You do not need to set
this eld.
n For other boards, the GFP protocol is recommended.

Step 4 Set the binding path for a port.

1. Click the Bound Pathtab. Click Conguration and the Bound Path Conguration
dialog box is displayed.
2. Select a VCTRUNK port from the Congurable Ports drop-down list. In the Available
Bound Path area, select the timeslot of the bearer layer and click .
3. Click OK and then click Yes. A prompt appears telling you that the operation was
successful.
4. Click Close.
Step 5 Optional: If you want to enable the LCAS function, click the LCAS tab. Set Enabling
LCAS to Enabled.
NOTE
The ET1/ET1D/ET1S boards do not support LCAS.
Step 6 Optional: If you want to set the MPLS encapsulation protocol for the port, click the Network
Attributes tab. Set the P/PE port attribute and the encapsulation format of the P port.
NOTE
The ET1/ET1D/ET1S boards do not support MPLS encapsulation.
Step 7 Optional: If you want to set port attributes for the QinQ board, click the Network Attributes
tab. Set the port attributes.
Step 8 Optional: Set the port advanced attributes.
Step 9 Repeat this procedure to congure the internal port attributes for other Ethernet boards of
the same NE or other NEs.
----End

You can congure the external port of an Ethernet board, that is, the PORT port. Primarily the
basic attributes, ow control and tag attributes of a PORT port are to be congured. The MPLS
encapsulation protocol and advanced attributes can also congured as needed.
Prerequisites
Procedure
Step 1 In the NE Explorer, select the appropriate Ethernet board and then select Conguration >
Ethernet Interface Management > Ethernet Interface from the Function Tree. Select the
External Port radio button.
Step 2 If you want to set the tag attribute for the port, click the TAG Attribute tab. Click Query to
view port physical parameters. Then modify the Name, Enabled/Disabled, Working mode,
Maximum packet length, MAC loopback and PHY loopback parameters as needed. Click
Apply. A prompt appears telling you that the operation was successful.
NOTE
n A port name is given for the sake of easy port management.
n For PORT ports to be used, the Enabled/Disabled parameter must be set to Enabled. Otherwise the
congured services will fail.
n Two ports interconnecting with each other must have the same working mode setting. Otherwise
services will fail.
n Set the MAC loopback and PHY loopback parameters to Inloop or Outloop only for fault location
purpose. Remember to release the loopback after the fault is removed. Otherwise services will fail.

Step 3 If you want to set the ow control for the port, click the Flow Control tab. Set the ow control
mode. Click Apply. A prompt appears telling you that the operation was successful.
NOTE
n The selection of the ow control mode depends on the working mode of the port. If the working
mode is autosensing, the ow control mode must be set to autosensing. If the working mode is xed,
the ow control mode must be set to non-autosensing.
n The N1EMS4 and N1EGS4 boards do not support the autosensing ow control attribute.
Step 4 If you want to set the tag attribute for the port, click the TAG Attribute tab. Set the TAG,
Default VLAN ID, VLAN priority and Enhance detection parameters as needed. Click
Apply. A prompt appears telling you that the operation was successful.
NOTE
n If Entrance detection is disabled, Ethernet data packets are transparently transmitted.
n The tag is used for setting what type of data packets can be processed.
– A port set to Tag aware processes only the data packets with a tag and discards those without a
tag. The Default VLAN ID and the VLAN priority elds are not applicable.
– A port set to Access processes only the data packets without a tag and discards all those with a
tag. The data packets without a tag are added with a tag based on the VLAN ID of the port.
– A port set to Hybrid processes both data packet types and adds a tag based on its VLAN ID
to the data packets without a tag.
n The value of the Default VLAN ID eld ranges from 1 to 4095.
n VLAN priority indicates the QoS level, which can be 0 to 7 in an ascending order. When the
network is busy, data packets with a higher VLAN priority are processed rst while those with
a lower priority may be discarded.
Step 5 Optional: If you want to set the MPLS encapsulation protocol for the port, click the MPLS
tab. Set the Port Type and Encapsulation format of P port parameters.
NOTE
For ET1, ET1D and ET1S boards, the MPLS encapsulation is not supported.
Step 6 Optional: If you want to set port attributes for the QinQ board, click the Network Attributes
and select the port attributes.
Step 7 Optional: Set the advanced attributes for the port.
----End
16.4 Conguring Ethernet Link Aggregation Groups

Through Ethernet link aggregation, multiple links connected to the same equipment can be
bound together.
Context
A link aggregation group looks like a single link supercially, as shown in the Figure 16-1.
Figure 16-1 Application of Link Aggregation Groups
Follow the process given below to congure a link aggregation group:

1. 16.4.1 Creating Link Aggregation Groups

You can congure the port attributes for an Ethernet board.
2. 16.4.3 Adding Link Aggregation Ports
Use this procedure to add Ethernet ports into a link aggregation group.
3. 16.4.5 Querying Link Aggregation Ports and Aggregation Status
You can query link aggregation ports and the aggregation status.
16.4.1 Creating Link Aggregation Groups

You can congure the port attributes for an Ethernet board.
Prerequisites
n Applies to EMS4/EGS4 boards.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and select Conguration > Ethernet Interface
Management > Ethernet Link Aggregation Management from the Function Tree.
Step 2 If you want to create a link aggregation group, click New. The Create Link Aggregation
Group dialog box is displayed. Set the parameters.
Step 3 Click OK. A prompt appears telling you that the operation was successful.
Step 4 Click Close.
----End
16.4.2 Deleting Link Aggregation Groups

Use this procedure to delete link aggregation groups.
Prerequisites
Procedure
Step 2 Select a link aggregation group and click Delete. In the Conrm dialog box displayed, click
OK. A prompt appears telling you that the operation was successful. Click Close.
----End
16.4.3 Adding Link Aggregation Ports

Use this procedure to add Ethernet ports into a link aggregation group.
Prerequisites

Procedure
Step 2 Select a link aggregation group and click Modify. The Modify Link Aggregation Group
Step 3 In Available Ports, select a link aggregation port to add and click .
----End
16.4.4 Deleting Link Aggregation Ports

Use this procedure to delete link aggregation ports.
Prerequisites
Procedure
Step 2 Select a link aggregation group and click Modify. The Modify Link Aggregation Group
Step 3 In Selected Ports, select a link aggregation port to delete and click .
----End
16.4.5 Querying Link Aggregation Ports and Aggregation Status

You can query link aggregation ports and the aggregation status.
Prerequisites
n Applies to EMS4/EGS4 boards.
Procedure
Management > Ethernet Link Aggregation Management from the Function Tree, click
Link Aggregation Group Management tab.
Step 2 Click Query to query the link aggregation ports and the aggregation status.
----End

16.5 Conguring ATM Boards

During the service conguration or test on an ATM board, the ATM board attributes must
be congured.
Context
Follow the process given below to congure an ATM board:
1. 14.316.5.1 Installing the ATM Interface Board

2. 14.4.116.5.2 Conguring Internal Ports
When conguring ATM services or performing loopback, you need to congure the
internal and external port attributes for an ATM interface board.
3. 14.4.216.5.3 Conguring External Ports
When conguring ATM services or performing loopback, you need to congure the
internal and external port attributes for an ATM interface board.
16.5.1 Installing the ATM Interface Board

Prerequisites
n The ATM service processing board must be installed.
Procedure
Step 1 In the NE Explorer, select an ATM board and select Conguration > Interface Board
Step 2 If you want to query the information of an ATM interface board from the NE, click Query.
Step 3 If you want to create the information of an ATM interface board, click Create. Alternatively,
right-click the Interface board list eld and select Create.
----End

Prerequisites
n Except for the AL1 board, the path must be bound before conguring the internal port.

Procedure
Management > ATM Interface Management from the Function Tree. Select the Internal
Port radio button.
Step 2 Click Query to query the internal port attributes of the ATM board.
Step 3 Select an internal port of the ATM board. Set the internal port attributes as needed.
----End

Prerequisites
Procedure
Management > ATM Interface Management from the Function Tree. Select the External
Port radio button.
Step 2 Click Query to query the external port attributes of the ATM board.
Step 3 Select an external port of the ATM board. Set the external port attributes as needed.
----End
16.6 Conguring Optical Booster Ampliers

When using an optical booster amplier board, you need to set the board according to the
required output optical power and other factors.
Prerequisites
n The optical booster amplier must be created.
Procedure
Step 1 In the NE Explorer, select an optical booster amplier board and select Conguration >
Optical Amplier Interface from the Function Tree.
Step 2 Select the Optical Amplier Attributes, Laser Attributes, Path Attributes or Output
Power Attributes radio button.


----End
16.7 Conguring TDA Boards

Before conguring audio services for a TDA board, you need to congure the clock source
traced by the board and select the TDA feeding mode according to the service type.
Prerequisites
n The TDA board must be created.
Context
CAUTION
When a board is powered on, the default status is a non-feeding status. Some of the
non-feeding terminals may be damaged if they are fed, so make sure the feeding status is
correct before cutover.
Procedure
Step 1 In the NE Explorer, select an TDA board and select Conguration > TDA Interface from the
Function Tree. Click the TDA Clock Source Conguration tab.
Step 3 Double-click a eld and set its value.
NOTE
A maximum of four clock sources can be congured, with level 1–4 switching priorities given to
them respectively.
Step 5 Click the TDA Feeding Choices tab.
Step 7 Double-click a eld and set its value.

NOTE
When you choose to feed, you can connect a phone to the TDA board interface and make calls directly.
When you choose not to feed, you can connect a non-feeding terminal (for example, a dedicated line
modem) to transmit data services.
----End
16.8 Conguring Board Protection

On SDH NEs, redundant boards can be used to provide board-level protection for major
boards so that the equipment reliability will be improved. Board protection can be congured
as long as redundant boards are available.
Context
According to what kinds of boards are on the NE, the following one or multiple types of
board protection can be congured for the NE.
16.8.1 Creating a 1+1 Protection Group for Cross-Connect or Clock Boards

You can create 1+1 protection for cross-connect or clock boards. When the primary fails, its
services switch to the secondary board automatically.
16.8.2 Performing 1+1 Protection Switching for Clock Boards
Before replacing an active cross-connect or clock board congured with 1+1 protection, switch
the service to the standby board so as to avoid affecting the service. This function also applies
to the test of the protection group.
16.8.3 Creating a TPS Protection Group for PDH Boards
TPS protection provides a backup tributary board. If the protected board fails, its services
switch to the protection board.
16.8.4 Performing TPS Switching for PDH Boards
Before replacing a PDH board congured with TPS protection, switch the service to the
standby board so as to avoid affecting the service. This function also applies to the test of
the TPS protection group.
16.8.5 Creating a Board Level Protection Group for Data Service Boards
You can create a board level protection group to provide 1+1 protection for Ethernet or ATM
boards. When the primary board fails, its services switch to the secondary board automatically.
16.8.621.3.10 Performing Board-Level Protection Switching for Data Service Boards
Before replacing an Ethernet or ATM board congured with board-level protection, switch the
service to the standby board so as to avoid affecting the service. This function also applies to
the test of the board-level protection group.
16.8.7 Port Protection Group
The port protection group provides protection for the PDH or Ethernet line between the client
equipment and the SDH network.
16.8.8 Creating Intra-Board Port Protection Groups
Intra-port protection is applicable for PDH boards. The protection port and the protected port
exist on the same board.
16.8.9 Creating Inter-Board Port Protection Groups
Inter-board port protection is applicable for Ethernet boards. The protection port and the
protected port exist on different boards.
16.8.10 Performing a Switch for a Port Protection Group
Use this procedure to perform a switch for a port protection group. This operation species the
bearer port of the service manually and helps daily maintenance and fault location.

16.8.1 Creating a 1+1 Protection Group for Cross-Connect or Clock

Boards
You can create 1+1 protection for cross-connect or clock boards. When the primary fails, its
services switch to the secondary board automatically.
Prerequisites
n A pair of cross-connect or clock boards must be installed.
Procedure
Step 1 In the NE Explorer, click an NE and select Conguration > Board 1+1 Protection from the
Function Tree.
Step 2 Click Query to query the current primary and secondary status from the NE.
Step 3 Click New. In the Add Protection Group dialog box, set the protection group type, active
board and standby board.
NOTE
If you select the primary board, the secondary board is shown automatically.
Step 4 Click OK.

----End
16.8.2 Performing 1+1 Protection Switching for Clock Boards

Before replacing an active cross-connect or clock board congured with 1+1 protection, switch
the service to the standby board so as to avoid affecting the service. This function also applies
to the test of the protection group.
Prerequisites
n The cross-connect or clock board must be created.
n The protection pair must be created.

Procedure
Function Tree.
Step 2 Right-click a protection group and select a switching operation from the shortcut menu.
Step 3 Click OK when a conrmation dialog box is displayed. A prompt appears telling you that
Step 4 Click Query to query the switching status.
----End
16.8.3 Creating a TPS Protection Group for PDH Boards

TPS protection provides a backup tributary board. If the protected board fails, its services
switch to the protection board.
Prerequisites
n The tributary board must be installed correctly. The TPS board must be installed for some
equipment (such as the EIPC board of the OptiX 2500+(Metro 3000)).
Procedure
Step 1 In the NE Explorer, click an NE and select Conguration > TPS Protection from the
Function Tree.
Step 2 Click Creat and the Create SDH TPS Protection Group dialog box is displayed.
Step 3 Select the protection board and the working board, and set priorities in the working board list.

Step 4 Set the WTR time.

Step 5 Click OK.
----End

Before replacing a PDH board congured with TPS protection, switch the service to the
standby board so as to avoid affecting the service. This function also applies to the test of
the TPS protection group.
Prerequisites
n The TPS protection group must be created.
Context
CAUTION
If there is an fault with the standby board, the forced switch will interrupt the service.
Procedure
Function Tree.
Step 2 Right-click in the protected board list and select a switching operation from the shortcut menu.

Step 3 Click OK when a conrmation dialog box is displayed.

----End
16.8.5 Creating a Board Level Protection Group for Data Service

Boards
You can create a board level protection group to provide 1+1 protection for Ethernet or ATM
boards. When the primary board fails, its services switch to the secondary board automatically.
Prerequisites
n A pair of Ethernet or ATM boards must be installed.
n Applies to the EMS4 and N2ADL4 boards.
Procedure
Step 1 In the NE Explorer, click an NE and select Conguration > Board-Level Protection from the
Function Tree.
Step 2 Click New and the Create a Board-Level Port Protection Group dialog box is displayed.
Step 3 Select the primary board and the standby board, and set the protection group ID.

NOTE
When conguring board level protection for the N2ADL4 boards, you can set Available Switching
Conditions.
Step 4 Click OK.

Step 5 Click Close.
----End
16.8.6 Performing Board-Level Protection Switching for Data

Service Boards
Before replacing an Ethernet or ATM board congured with board-level protection, switch the
service to the standby board so as to avoid affecting the service. This function also applies to
the test of the board-level protection group.
Prerequisites
n The board-level port protection group must be created.
Procedure
Function Tree.
Step 2 Right-click a protection group and select a switching operation from the shortcut menu. The
conrmation dialog box is displayed.
----End
16.8.7 Port Protection Group

The port protection group provides protection for the PDH or Ethernet line between the client
equipment and the SDH network.
The client equipment and the SDH network can be interconnected through a PDH or Ethernet
line, which can be protected by a port protection group. With this protection scheme, client
services are dual-fed to the access equipment on the SDH network. When one line goes faulty,
the SDH access equipment switches the services to the other line.

16.8.8 Creating Intra-Board Port Protection Groups

Intra-port protection is applicable for PDH boards. The protection port and the protected port
exist on the same board.
Prerequisites
n Applies to the FP2D board.
Context
CAUTION
After the intra-board port protection group is created, the protection port can no longer be used
to transmit other services.
Procedure
Step 1 In the NE Explorer, click an NE and select Conguration > Port Protection from the
Function Tree.
Step 2 Click New and the Create Port Protection Group dialog box is displayed.
Step 3 Select Working Port and Protection Port. Set Revertive Mode and Hold Off Time(100ms).

Step 5 Click Close.
----End
16.8.9 Creating Inter-Board Port Protection Groups

Inter-board port protection is applicable for Ethernet boards. The protection port and the
protected port exist on different boards.
Prerequisites
n Applies to the EMS4, EGS4 and EGT6 boards.
Context
CAUTION
After the inter-board port protection group is created, the protection port can no longer be used
to transmit other services.
Procedure
Function Tree.
Step 2 Click New and the Create Port Protection Group dialog box is displayed.
Step 3 Select Working Port and Protection Port.

Step 5 Click Close.
----End
16.8.10 Performing a Switch for a Port Protection Group

Use this procedure to perform a switch for a port protection group. This operation species the
bearer port of the service manually and helps daily maintenance and fault location.
Prerequisites
n The port protection group must be created.
Procedure
Function Tree.
Step 2 Right-click a protection group and select a switching operation from the shortcut menu. A
prompt appears telling you that the operation was successful. Click Close.


----End

Operator Guide 17 Adjusting Networks
17 Adjusting Networks
About This Chapter

The T2000 helps you to adjust the capacity of the existing network, protection subnets and
boards in a quick and secure manner. The wizard takes you step by step through adjusting the
network.
9.2.617.1 Adjusting the Capacity of an MSP Ring

9.2.717.2 Expanding Link Capacity of an MSP Ring
9.3.317.3 Adjusting the Capacity of a Linear MSP
9.3.417.4 Expanding Link Capacity of a Linear MSP
9.8.217.5 Changing an NP Chain to a 1+1 Linear MSP
The T2000 helps you to change some protection types without affecting services, deleting
existing services in the protection subnet and changing the trail name and other attributes. You
can change an non-protection (NP) chain to a 1+1 linear multiplex section protection (MSP),
to facilitate network management and maintenance.
9.11.417.6 Adjusting Link Bandwidth of an RPR Ring

17 Adjusting Networks Operator Guide
17.7 Adjusting Boards

This function allows you to set boards to be adjusted and the types and slots of the boards after
the adjustment, to expand the system functions. You can replace the existing boards with
ones with more ports and larger capacity and change the inappropriate board slots through
this function. The T2000 changes the related data (such as circuits, protection subnets and so
on) automatically and completes the expansion conguration.
17.8 Adding Extended Subracks
This function helps you to move boards from the original main subrack to the extended
subrack, to expand the add or drop capability of tributary signals.
17.9 Adding Nodes to a Protection Subnet
Adding nodes to a protection subnet adjusts the network and expands the network system
functions. You can add nodes to the protection subnet by inserting nodes on bers.

17.1 Adjusting the Capacity of an MSP Ring

Prerequisites
Context
NOTE
n This function applies to two-ber unidirectional MSP ring, two-ber bidirectional MSP ring and
four-ber bidirectional MSP ring.
Procedure
check box.

Step 5 Click OK.
----End
17.2 Expanding Link Capacity of an MSP Ring

Prerequisites
n Applies to the OptiX OSN 1500, OptiX OSN 2500, OptiX OSN 3500, OptiX OSN 7500
and OptiX OSN 9500.

Context
CAUTION
Procedure
Step 1 Select Conguration > Expansion Wizard > Upgrade Link Capacity from the Main Menu.
The Upgrade Link Capacity dialog box is displayed.
Step 2 Click Next and go to "Step 1: Select the ber to be expanded". Click a link, or click the
NOTE
supported.
NOTE
of the same rate.

n Click Query to query the current protection subnet status.

CAUTION
n After the forced switch, extra services and unprotected services in the link are interrupted.
The services are restored only when the switch is cleared.
n If Forced Upgrade is selected, go to the fourth step without performing the forced switch.
But the primary services are also interrupted.
n Before performing the forced switch, make sure that the appropriate station is in an attended
mode and that the board is replaced successfully.

Click Apply. The conrmation dialog box is displayed saying Please ensure the
NOTE
Step 9 Optional: Repeat Steps 2 through 8 to expand all links in the protection subnet.
----End
17.3 Adjusting the Capacity of a Linear MSP

Prerequisites
Context
NOTE
n This function applies to 1+1 linear MSP and M:N linear MSP.
Procedure
check box.

Step 5 Click OK.

----End
17.4 Expanding Link Capacity of a Linear MSP

Prerequisites
n The MSP protection must be created.
n Applies to the OptiX OSN series products.
Context
CAUTION
Procedure
Step 1 Select Conguration > Expansion Wizard > Upgrade Link Capacity. The Upgrade Link
Capacity dialog box is displayed.
Step 2 Click Next and go to "Step 1 Select the ber to be upgraded". Click a link, or click the
NOTE
supported.

NOTE
of the same rate.

n Click Query to query the current protection subnet status. Replace the board at the
appropriate station and re-connect the physical bers.
NOTE
n After the forced switch, extra services and unprotected services in the link are interrupted. The
services are restored only when the switch is cleared.
n If Forced Upgrade is selected, go to the fourth step without performing the forced switch. But the
primary services are also interrupted.
n Before performing the forced switch, make sure that the appropriate station is in an attended mode
and that the board is replaced successfully.

Click Apply. The Conrmation dialog box is displayed saying Please ensure the
NOTE
Step 9 Repeat Steps 2 through 8 to expand all links in the protection subnet.
----End
17.5 Changing an NP Chain to a 1+1 Linear MSP

The T2000 helps you to change some protection types without affecting services, deleting
existing services in the protection subnet and changing the trail name and other attributes. You
can change an non-protection (NP) chain to a 1+1 linear multiplex section protection (MSP),
to facilitate network management and maintenance.
Prerequisites
n Both NEs for which you wish to change the protection type are release 5.0 NEs, are
congured on the T2000 and running normally.
n At least two bers of the same class lie between the two NEs and are not occupied by
other protection subnets such as path protection (PP), MSP, NP ring, or NP chain with
more than two NEs.
n The protection chain contains no service before performing this operation.

Procedure
Protection View > SDH Protection Type Change. The protection type change wizard is
displayed.
Step 2 Select the change type and the capacity level. Select an appropriate Capacity level under
Protection switching type. Click Next.
NOTE
As the T2000 only allows to change from an NP chain to a 1+1 linear MSP, take the default value for
the change type.
Step 3 Select an NE. Select an appropriate NE in the List of available NEs pane and click the
button to transfer it to the List of selected NEs pane. Click Next.
NOTE
You can only choose two NEs.
Step 4 Select the working chain and the protection chain. Select appropriate chains as the working
chain and the protection chain respectively in the Available links pane. Click Next.

Step 5 Set attributes of the protection subnet. Select values for Protection Subnet Name, Switching
mode, and Revertive Mode, and set WTR time and Enabling SD.

----End
17.6 Adjusting Link Bandwidth of an RPR Ring

Prerequisites

n Link capacity adjustment scheme (LCAS) must be enabled.
Procedure
Step 2 Set Enabling LCAS to Enabled for the source VCTRUNK port of the RPR link.
Step 3 Click to switch to the sink NE of the RPR link.

Step 5 Set Enabling LCAS to Enabled for the sink VCTRUNK port of the RPR link.
Step 6 Select Conguration > RPR Ring > Management from the Main Menu. Select the Link
Information tab.
Step 7 Select the link for which you wish to adjust capacity from the link list, right-click and select
Adjust Link bandwidth. The Add Link Member dialog box is displayed.
Step 8 Check the Selected check box, to select or deselect a channel for the RPR link.
NOTE
The trunk link is bidirectional. Therefore, if you adjust the capacity of Ring 0 link for a span of the RPR
ring network, Ring 1 link is also adjusted. If Ring 1 link is adjusted, Ring 0 link is also adjusted.
Step 9 Click OK. The Operation Result dialog box is displayed, indicating the link bandwidth is
successfully adjusted for the RPR ring network.
----End
17.7 Adjusting Boards

This function allows you to set boards to be adjusted and the types and slots of the boards after
the adjustment, to expand the system functions. You can replace the existing boards with
ones with more ports and larger capacity and change the inappropriate board slots through
this function. The T2000 changes the related data (such as circuits, protection subnets and so
on) automatically and completes the expansion conguration.
Prerequisites
n The NE must be congured on the T2000.
n The NE containing the boards must be an SDH one.
n The data at the network layer on the T2000 is consistent with that at the NE layer.
Procedure
Step 1 Select Conguration > Expansion Wizard > Change Board from the Main Menu.
Step 2 Optional: Click OK in the Conrmation dialog box. The Protection View, SDH Trail
Management window and Fiber/Cable Management window close.
Step 3 Click Next in the Change Board window.

NOTE
The Select Expansion Mode is now Change Board.
Step 4 Step 1 Select the NE to be changed. You can select the NE in the window or click
to select the NE from the Main Topology. Click Next.
Step 5 Step 2 Select the board to change. Select the board by clicking in the NE Panel. Click Next.
Step 6 Step 3 Step 3 Add the board or select the board to be modied into. Right-click on the slot
where the original board resides and select an appropriate board from the shortcut menu.
Click Next.
Step 7 Step 4 Set port relations. Click Next.
NOTE
You may select Display in Combination.
Step 8 Step 5 Conrm selected data. Click Next.

Step 9 Step 6 Conrm affected data. Click Next.
Step 10 Step 7 Send the congurations. Click Apply. In the Conrm dialog box, click OK to conrm
that the board is replaced and starts working, and that the ber connection is completed.
Step 11 When all data are successfully applied, click Finish.
----End
17.8 Adding Extended Subracks

This function helps you to move boards from the original main subrack to the extended
subrack, to expand the add or drop capability of tributary signals.
Prerequisites
n The extended subrack NE you wish to add must be created on the T2000.
n The main subrack NE and the extended subrack NE must be SDH NEs.
Context
NOTE
This operation is applicable only to moving tributary boards from the main subrack to the extended
subrack. This operation is not applicable to situations when you want to create optical or electrical
interface boards and the extended subrack.
Procedure
Step 1 Select Conguration > Expansion Wizard > Add Extended Subrack from the Main Menu.
The Add Extended Subrack wizard is displayed.
Step 2 In the Add Extended Subrack window, click Next.
NOTE
The Select Expansion Mode is now Add Extended Subrack.
Step 3 In Select main subrack NE, select the NE where you want to move the tributary board, click
Next and select the main subrack tributary board.
Step 4 Click Next and select the main subrack line board.

Step 5 Click Next and select the extended subrack NE.

Step 6 Click Next and select the extended subrack line board.
Step 7 Click Next and select the extended subrack tributary board.
Step 8 Click Next and set the port relations.
Step 9 Click Next and select the cross-connect level.
NOTE
Select Lower Order Cross-Connect or Higher Order Cross-Connect according to the actual
conguration.
Step 10 Click Next and conrm the selected data. Then click Next and conrm the affected data.
Step 11 Click Next and send the conguration to the NE. Click Apply. After all data is sent to the
NE, click Finish.
----End
17.9 Adding Nodes to a Protection Subnet

Adding nodes to a protection subnet adjusts the network and expands the network system
functions. You can add nodes to the protection subnet by inserting nodes on bers.
Prerequisites
n Conguration of boards must be completed for the new node.
n The new node must have idle line boards for ber connections.
n The license for T2000 trail management function is provided.
n The number of nodes on the MSP ring must be less than 16 and the multiplex section
protocol must be enabled for all nodes.
Context
NOTE
n This function is available on SDH NEs only.
n To ensure services are not interrupted, you must execute a forced switching on NEs at both ends of
the ber to be cut before expanding the MSP ring.
n No node can be added to the MSP ring with dual node interconnection (DNI).
n During the expansion, select Conguration of the NE is complete. Use the conguration data on
the NE. The same protection subnet must be congured for the new NE and appropriate services
must be congured according to the existing services on the protection subnet. Otherwise, selection
of node port fails.
Procedure
Step 1 Select Conguration > Expansion Wizard > Insert Node on Fiber from the Main Menu.
Step 2 In the Insert Node on Fiber window, click Next.
NOTE
The Select Expansion Mode is now Insert Node on Fiber.
Step 3 In the Insert Node on Fiber dialog box, click Yes to conrm whether you have backed up
the T2000 database.
Step 4 Step 1: Select bers. Select bers connecting the new NE from the list, and click Next.

Step 5 Step 2: Protection subet protocol status. In the Select Subnets Existing in Fiber list, select
the desired subnet. Click Next.
NOTE
If the ber is used by multiplex section, view Protocol Status of Multiplex Section to make sure the
protection protocol is in the started state.
Step 6 Step 3: Fiber Relations. Select the NE to which you wish to add nodes and Port of Added
NE. Click Next.
Step 7 Step 4: Select service conguration strategy. Select the desired strategy from the list and
click Next.
Step 8 Step 5: Conrm the selected data. Click Next.
Step 9 Step 6: Impose the conguration. Click Apply. The Conrmation dialog box is displayed,
prompting you to conrm whether ber connections are correct for the new node. Click OK.
After all data are sent to the NE, click Finish.
----End

Operator Guide 18 Managing ASON Networks
18 Managing ASON Networks
About This Chapter

The automatically switched optical network (ASON) is a new generation optical transmission
network integrating switching and transmission. After the user initiates a service request,
the ASON selects a route automatically, and performs network connection automatically
and dynamically with the establishment and removal of the connection controlled by
signaling. Intelligent NEs refer to the equipment that is equipped with characteristics of SDH
equipment and ASON. The T2000 manages ASON networks by combining ASON and SDH
characteristics.
Getting Started
The process for managing an ASON network using the T2000 is as follows:
Stage Description Remarks
1 Starting an NE with NE commissioning
intelligent software
2 Creating a GNE on the Create the NE connected to
T2000 the T2000 as a GNE
3 Uploading the GNE data A T2000 feature for
managing SDH equipment
4 Creating an ASON domain A T2000 feature for
managing ASON networks
5 Setting the GNE to "Active A T2000 feature for
NE" of the ASON managing ASON networks
6 Synchronizing networkwide A T2000 feature for
data, searching for ASON managing ASON networks
NEs and creating the NEs on
the T2000 topology
7 Uploading NE data A T2000 feature for
8 Managing intelligent A T2000 feature for
resources and preserved managing ASON networks
sources In TE link management,
create bers specic to links
9 Creating a protection subnet A T2000 feature for
(optional) managing SDH equipment
Create an MSP protection
subnet for 1:1 protected
ASON trails

18 Managing ASON Networks Operator Guide
Stage Description Remarks

10 Conguring clocks A T2000 feature for
11 Managing ASON trails A T2000 feature for
12 Conguring board A T2000 feature for
parameters, conguring managing SDH equipment.
services station by station and See Conguring Board
through trail management Parameters, Conguring
function Services Station by Station,
Conguring Services
Through Trail Management.
13 Viewing alarms and A T2000 feature for
abnormal events managing ASON networks
14 Viewing performance data A T2000 feature for
Basic Concepts of ASON

The ASON is an optical network composed of ASON NEs. The ASON performs signaling
transmission and switching. The ASON NEs store the topology and routing information of the
whole network and automatically create and remove services through signaling.
The ASON has three planes: the control plane, the transmission plane, and the management
plane. As shown in Figure 18-1
Figure 18-1 Three planes of the ASON
1. Control Plane
The control plane consists of a group of communication entities. It undertakes calling control
and connection control, including setting up, releasing, monitoring, maintaining connections.
The control plane automatically restores the failed connections through signaling exchange.
2. Transmission Plane
The SDH network is on the transmission plane. It transmits and multiplexes optical signals,
congures cross-connection and protection switching for optical signals, and guarantees the
reliability of all optical signals.
3. Management Plane

The management plane is a complement to the control plane. It maintains the transmission
plane, the control plane and the whole system. Its functions include performance management,
fault management, conguration management and security management.
4. ASON NE
The SCC board of an ASON NE is loaded with NE software which contains ASON software
and the ASON software is started. If the ASON software is not started, the NE is not an
ASON NE.
5. PC
Permanent connection (PC) is a service connection calculated beforehand and then created
through the T2000 by issuing a command to NE. The traditional SDH static service is a PC.
6. SC
Switched Connection (SC) is any connection that is established, as a result of a request from
the end user, between connection end-points using a signaling/control plane and involves the
dynamic exchange of signaling information between signaling elements within the control
plane(s). At present, SC is not supported.
7. SPC
Soft Permanent Connection (SPC) is a user-to-user connection where by the user-to-network
portion of the end-to-end connection is established by the T2000 as a PC. The network portion
of the end-to-end connection is established as a switched connection using the control plane.
In the network portion of the connection, requests for establishment of the connection are
initiated by the management plane and set up by the control plane.
8. Timeslot Reservation
Also called resource reservation. The NE software and ASON software of an ASON NE
manage their own timeslots respectively. The timeslots created with ASON services are
managed by the ASON software and cannot be used by the NE software to create static
services. Timeslot reservation is to reserve part or all of the timeslots of a specied optical
interface to NE software to create static services. Before cancellation, they cannot be used by
the ASON software. It is recommended to congure static services on reserved timeslots.
9. LSP
Label switching path (LSP) is the path ASON services passing through. In an ASON, to create
ASON services is to create LSPs.
10. Control Link
Control links are created and maintained between adjacent nodes by Link Management
Protocol (LMP). Without available control links, component links and TE links between
adjacent nodes cannot be created.
Control link information can pass through in-band (through D4–D12, for example), or is
transmitted out of band (Ethernet, for example). In the in-band mode, the control ink can be
discovered automatically. In out-band mode, you need to congure IP address for the adjacent
NEs connected to the control link.
11. TE Link
TE link is a trafc engineering link. The ASON NE sends its bandwidth information to other
ASON NEs through the TE link to provide data for route calculation. A ber can be congured
with multiple TE links and a TE link can also be bundled with multiple bers.
If the multiplex section protection is congured partially, that is, a 10 Gbit/s (64 VC4s) optical
interface is congured with a 2.5 Gbit/s multiplex section protection, 1–8 VC4s are the
working links, which are a TE link. 33–40 VC4s are the protection links, which are a TE link;
and the rest VC4s are unprotected links, which are also a TE link. Thus there are three TE
links in a ber. If the multiplex section protection is congured completely in a ber, there
are only two TE links in this ber. If the multiplex section protection is not congured in
ber, there is only one TE link in this ber.
12. Multiplex Section Link

Multiplex section links are links which are congured with multiplex section protection.
Multiplex section links are divided into multiplex section working links and multiplex section
protection links. A multiplex section working link is a TE link and a multiplex section
protection link is also a TE link. Iron service will use multiplex section protection links.
13. Component Link
Component link is a bandwidth unit smaller than TE link. One TE link consists of only one
component link in the actual ASON software.
14. Rerouting
Rerouting is a means of recovering services. When an ASON trail is disconnected, the
initial node queries whether there is a best route to resume service and then sends signaling
to downstream nodes hop by hop, and requests them to reserve resources and create
cross-connection. Its nal node returns signaling to upstream nodes hop by hop and nally a
new ASON trail is created.
15. Rerouting Lockout
In some cases, rerouting is not required after failure of ASON trail. Then you need to set
rerouting lockout.
16. Rerouting Priority
When multiple ASON trails reroute simultaneously, the ASON trail of higher priority occupies
resources rst and has more possibility to reroute successfully.
17. Disjoint Strategy
Disjoint strategy means excluding some links or nodes in the process of creating an ASON
trail. The ASON software supports two disjoint strategies: by links or by nodes.
18.1 Managing ASON Topology

An ASON network uses routing protocols to exchange node topology information among
nodes. Therefore, network topology information is available to every node. The T2000 can
nd other intelligent NEs in the network through any one intelligent NE, thus forming a
topology for the overall network. An ASON is a self-managed network. You need to deploy
the ASON topology on the T2000 rst. The procedure is as follows: Start the ASON NE and
enable the ASON software. Create the NE connected to the T2000 as a GNE and upload the
GNE data. In the ASON Topology Management window, create an ASON domain and set
the GNE to "Active NE". In ASON NE, synchronize the networkwide data. The NEs that are
found in the search are displayed in NE to be Created. Create the NEs on the T2000 topology
and upload their conguration data. After the ASON topology is deployed, you can start
component link management, TE link management and ASON trail management.
18.2 Managing TE Links
TE links, also called trunks or TE links, is a resource concept. You can understand it as ber
with bandwidth information and protection attributes. A ber may correspond to multiple TE
links. The TE link indicates the resources available between ASON NEs, utilized by the
control plane for path algorithm and selection.
18.3 Managing ASON Trails
Label switching path (LSP) is the path ASON services passing through. In T2000, LSP is
called ASON trail.
18.4 Viewing Alarms and Abnormal Events
You can view alarm information specic to ASON trails and abnormal events in the network,
to know faults and exceptions in the ASON network.
18.5 Viewing Performance Monitoring Data
Network management personnel need to view performance monitoring data regularly to nd
problems in the network.
18.6 Customising the ASON View
In a large network with many ASON NEs, the display of the ASON view is relatively unclear.
Using the view customisation function, you can customise which ASON NEs to be displayed
on the view.

18.7 Managing Reserved Resources

To specify some resources in the ASON network that are not used by ASON NE software, you
can set reserved resources for every ASON NE. For example, board ports, timeslots (specic to
VC-4). When an ASON trail is rerouted, the NE software avoids using the reserved resources.
18.8 Managing Component Links
ASON component link is a bandwidth unit smaller than TE link. One TE link consists of only
one component link in the actual ASON software.
18.9 Managing the Control Plane
The control plane consists of communication entities for call control and connection control.
The communication entities establish, release, monitor and maintain connections, and recover
connections automatically in the event of failure using signaling.
18.10 Querying ASON Information on a Per-NE Basis
You can query ASON trails, TE links, control links and component links from the NE.
18.11 Advanced Maintenance for ASON Control Plane
When discrete signaling exists in an ASON, you can query or maintain it by using the
advanced maintenance for ASON control plane.

18.1 Managing ASON Topology

An ASON network uses routing protocols to exchange node topology information among
nodes. Therefore, network topology information is available to every node. The T2000 can
nd other intelligent NEs in the network through any one intelligent NE, thus forming a
topology for the overall network. An ASON is a self-managed network. You need to deploy
the ASON topology on the T2000 rst. The procedure is as follows: Start the ASON NE and
enable the ASON software. Create the NE connected to the T2000 as a GNE and upload the
GNE data. In the ASON Topology Management window, create an ASON domain and set
the GNE to "Active NE". In ASON NE, synchronize the networkwide data. The NEs that are
found in the search are displayed in NE to be Created. Create the NEs on the T2000 topology
and upload their conguration data. After the ASON topology is deployed, you can start
component link management, TE link management and ASON trail management.
NOTE
n An ASON NE can only belong to a domain.
n Upload the conguration data from the NEs for all new NEs.
n Affected by data communication network (DCN), the topology information and the TE links
information in the T2000 may differ from those in the NE. To solve it, synchronize the NE data to
keep the data in the T2000 synchronized with the NEs.
4.318.1.1 Creating a Single GNE

3.2.418.1.2 Uploading NE Conguration Data
The status of a newly created NE is Uncongured status. You need to upload the NE data to
the T2000 to change the status to Running.
18.1.3 Creating Domains for an ASON Network
Create domains and group the ASON NEs of the same ASON network into the same domain.
On the T2000, an ASON network comprised of ASON NEs interconnecting by bers is a
domain. Therefore, the T2000 manages more than one ASON network by dividing networks
into domains.
18.1.4 Setting the Primary/Secondary NE
In an ASON network, network topology information is available to every NE. Therefore,
you need to set a primary NE through which the T2000 keeps synchronized with the ASON
network. For reliability purpose, you can set a secondary NE as the backup of the primary
one. You can select the GNE as the primary NE and secondary one so that ECC bandwidths
are not wasted.
18.1.5 Synchronizing ASON NEs
The T2000 keeps synchronized with an ASON network through the active NE and discovers
other ASON NEs in the network. If there is a new ASON NE, it is shown in the NE to be
Created tab. You can decide whether to create the NEs on the T2000 according to specic
conditions. If one or more ASON NEs are added to or deleted from the ASON network, you
need to synchronize NEs and get the changed network topology. If an NE’s node ID is
modied manually, you need to re-synchronize the ASON network topology on the T2000.
18.1.6 Viewing ASON NE Software Version
You can view the version of the ASON NE software equipped with the NE.
18.1.1 Creating a Single GNE


Prerequisite
Procedure
Step 4 Select Gateway from the Gateway Type drop-down list.
Step 5 Select the protocol type.

If the T2000 communicates with NEs Do...

through
IP protocol Select IP from the Protocol drop-down list.
Enter the IP address and use the default
value for the port number of the GNE.
OSI protocol Select OSI from the Protocol drop-down
list. Enter the NSAP address of the GNE.
NOTE
The NSAP address is a hexadecimal number containing up to 20 bytes. Its format is: domain
address+08003e+NE ID+NSEL.
"domain address" comprising up to 13 bytes is entered by the user. "NSEL" is the port number of the
network-level protocol, with a xed value of 1d (one byte).
Step 6 Enter the NE user and password.
NOTE
Step 7 Click OK.

----End
18.1.2 Uploading NE Data

The status of a newly created NE is Uncongured status. You need to upload the NE data to
the T2000 to change the status to Running.
Prerequisites
n The NE is in the Uncongured status.
Procedure
Step 1 Double-click an NE icon on the Main Topology. The NE Conguration Wizard is displayed.
Step 2 Select Upload and click Next.
Step 3 Click OK in the Conrmation dialog box.
Step 4 A progress bar is displayed showing the progress of the uploading.
After the data is uploaded, the NE on the Main Topology is in the Running state.
----End
18.1.3 Creating Domains for an ASON Network

Create domains and group the ASON NEs of the same ASON network into the same domain.
On the T2000, an ASON network comprised of ASON NEs interconnecting by bers is a
domain. Therefore, the T2000 manages more than one ASON network by dividing networks
into domains.

Prerequisites
n The ASON NE must be congured and does not belong to any domain.
Context
NOTE
n An ASON domain is an ASON network composed of interconnected ASON NEs.
n The rst ASON NE created on the T2000 is automatically assigned to the default domain.
Procedure
Step 1 Select Conguration > ASON Topology Management from the Main Menu.
Step 2 ASON NEs that belong to no domain are displayed under "root" of the Object Tree. Right-click
the NE and select Create Domain.
Step 3 In the Domain Attributes dialog box, enter a domain name and select the active NE.
Step 4 Click OK. The domain is successfully created.

----End
18.1.4 Setting the Primary/Secondary NE

In an ASON network, network topology information is available to every NE. Therefore,
you need to set a primary NE through which the T2000 keeps synchronized with the ASON
network. For reliability purpose, you can set a secondary NE as the backup of the primary
one. You can select the GNE as the primary NE and secondary one so that ECC bandwidths
are not wasted.
Prerequisites
n An ASON NE must be created and its data must be uploaded to the T2000.
Context
In this example, the GNE is congured as the primary NE.

Procedure
Step 1 Select Conguration > ASON Topology Management from the Main Menu. Click the
ASON NE tab.
Step 2 Select a domain in the Object Tree and all ASON NEs in the domain are shown in the list.
Step 3 Select an NE, double-click the Node Type eld and select Primary from the drop-down list.
Step 4 Click Apply.
----End
18.1.5 Synchronizing ASON NEs

The T2000 keeps synchronized with an ASON network through the active NE and discovers
other ASON NEs in the network. If there is a new ASON NE, it is shown in the NE to be
Created tab. You can decide whether to create the NEs on the T2000 according to specic
conditions. If one or more ASON NEs are added to or deleted from the ASON network, you
need to synchronize NEs and get the changed network topology. If an NE’s node ID is
modied manually, you need to re-synchronize the ASON network topology on the T2000.
Prerequisites
n The active NE must be congured.
Procedure
ASON NE tab.
Step 2 Select a domain in the Object Tree and all ASON NEs in the domain are shown in the list.
Step 3 Click Synchronization NE and the T2000 searches for the NEs in the ASON domain.
Step 4 If an ASON NE that is not created on T2000 is detected, add it to the NE to be Created tab.
Step 5 If you want to create a detected NE on the T2000, click in the Creation Flag eld. Enter the
user and password.

NOTE
n If the T2000 uses the same user and password to log in to all ASON NEs in the domain, check the
Use the same password networkwide check box, and enter the user and password.
n If you want to upload the NE data after creating the NE, check the Upload after created check box.
Step 6 Click Apply. The Operation Result dialog box is displayed, indicating the operation
succeeded. Click Close.
Step 7 Click OK in the conrmation dialog box. A progress bar displays showing the progress of
uploading.
----End
18.1.6 Viewing ASON NE Software Version

You can view the version of the ASON NE software equipped with the NE.
Prerequisites
n You must be an NM user with "NE and network supervisor" authority or higher.
n Applies to OSN series NEs.
Procedure
ASON NE tab.
Step 2 Select the desired domain in the Object Tree. Click and all ASON NEs in the domain
are shown in the list.
Step 3 View the ASON NE software version.
For example, "5.99.1.30".
----End
18.2 Managing TE Links

TE links, also called trunks or TE links, is a resource concept. You can understand it as ber
with bandwidth information and protection attributes. A ber may correspond to multiple TE
links. The TE link indicates the resources available between ASON NEs, utilized by the
control plane for path algorithm and selection.
NOTE
n Compared with the traditional SDH functions, TE link management can automatically discover and
manage link resources. However, you still need to manually create ber connections on the T2000.
n TE link management is based on correct link information.
18.2.1 Synchronizing TE Links

You can synchronize the TE links. The T2000 queries link resources in the network through
the active NE, to keep the TE links data in the T2000 consistent with the ASON.

18.2.2 Viewing TE Links

Use this procedure to view TE links on the T2000. You can view component links of every TE
link, display TE links in different bandwidth units, view TE links according to specied lter
criteria, print the list of selected links, or save the list to le.
18.2.3 Conguring Link Distance
The link data uploaded from ASON NEs contains no distance information. You can add the
link distance information on the T2000 for route calculation.
18.2.4 Conguring SRLGs
You can congure a share risk link group (SRLG). Fibers in the same optical cable have the
same risk. If the cable is cut, all bers are also cut. During service rerouting, services should
not be rerouted to the link that belong to the same SRLG. Therefore, you need to set the same
SRLG value for TE links with the same risk in the network.
18.2.5 Creating Fibers
The ASON network discovers TE links automatically. Therefore, you can create bers based
on TE links on the T2000.
18.2.1 Synchronizing TE Links

You can synchronize the TE links. The T2000 queries link resources in the network through
the active NE, to keep the TE links data in the T2000 consistent with the ASON.
Prerequisites
n The ASON network is running normally.
Procedure
Step 1 Select Conguration > TE Link Management from the Main Menu.
Step 2 Click Synchronize and a progress bar displays.

Step 3 After the synchronization is complete, a prompt appears telling you that the operation was
successful.
----End
18.2.2 Viewing TE Links

Use this procedure to view TE links on the T2000. You can view component links of every TE
link, display TE links in different bandwidth units, view TE links according to specied lter
criteria, print the list of selected links, or save the list to le.

Prerequisites
Procedure
Step 2 The list shows all links on the T2000. View information of each link.
NOTE
A TE link is unidirectional. For example, a two-ber bidirectional ber is shown as two links.
Step 3 Optional: Select the desired bandwidth unit from the Bandwidth Units drop-down list. For
example, VC4. Then the list refreshes automatically and shows the link information in the
selected bandwidth unit.
NOTE
In some standards, the bandwidth unit of TE links is kbit/s. On the T2000 you can choose a different
bandwidth unit that is more familiar in SDH transmission.
Step 4 Optional: Under Filter Criteria, select Source NE or Sink NE, and click Filter. The
qualied links are shown in the list.
Step 5 Optional: Click Print to export the list to Internet Explorer for printing.
Step 6 Optional: Click Save to File. Enter the start line number, end line number and le name.
Click OK to save the list to le.
----End
18.2.3 Conguring Link Distance

The link data uploaded from ASON NEs contains no distance information. You can add the
link distance information on the T2000 for route calculation.
Prerequisites
n The link data must be congured on the T2000.
Procedure

Step 2 Select a link, double-click the Distance(km) eld, and enter a value.
Step 3 Click Apply.
----End
18.2.4 Conguring SRLGs

You can congure a share risk link group (SRLG). Fibers in the same optical cable have the
same risk. If the cable is cut, all bers are also cut. During service rerouting, services should
not be rerouted to the link that belong to the same SRLG. Therefore, you need to set the same
SRLG value for TE links with the same risk in the network.
Prerequisites
n The TE link data must be congured on the T2000.
Procedure
Step 2 Select one or more TE links, double-click the SRLG eld, and enter a value.
Step 3 Click Apply.
NOTE
The TE link in the opposite direction is set to the same SRLG value automatically. All TE links that
connect to the same end as the TE link are set to the same SRLG value automatically.

----End
18.2.5 Creating Fibers

The ASON network discovers TE links automatically. Therefore, you can create bers based
on TE links on the T2000.
Prerequisites
Procedure
Step 2 The list shows all links on the T2000. View information of each link.
Step 3 Select one or more links and click Create Fiber.
NOTE
After ber(s) is/are created successfully, view ber(s) on the Main Topology.
----End
18.3 Managing ASON Trails

Label switching path (LSP) is the path ASON services passing through. In T2000, LSP is
called ASON trail.
The T2000 provides end-to-end ASON trail management and supports the following ve
classes of services:
n Diamond services: provides protection scheme similar to 1+1 protection, such as SNCP,
with switching time of less than 50ms
n Gold services: provides protection scheme similar to 1:1 protection, such as MSP, with
switching time of less than 50ms
n Silver services: provides real-time rerouting protection with switching time of less than 2s
n Copper services: no protection in the event of failure
n Iron services: preemptible
The most essential ability for ASON trail management is rerouting. In a traditional SDH
network, if there are several failure points, or if the key node fails, the services are not be
protected. In an ASON network, if the services fail, a new route is calculated from the start NE
and the services are recreated. Therefore, as long as there is still free bandwidth in the ASON,

the rerouted services will never be interrupted. Moreover, there is no need to pre-congure the
protection resources and thus the utilization of network resources is greatly enhanced.
18.3.1 Synchronizing ASON Trails

You can synchronize the ASON links to keep the ASON links data in the T2000 consistent
with the ASON.
18.3.2 Creating a Diamond ASON Trail
You can create an ASON trail with the protection type of Diamond.
18.3.3 Creating a Gold ASON Trail
You can create an ASON trail with protection type of Gold on an MSP protected trail only.
You need to make sure MSP ring or linear MSP is congured for all links that the ASON
trail passes through. After you create a gold ASON trail, you are not allowed to modify the
attributes of the MSP protection subnet that the ASON trail passes through.
18.3.4 Creating a Silver ASON Trail
You can create an ASON trail with protection type of Silver.
18.3.5 Creating a Copper ASON Trail
You can create an ASON trail with protection type of Copper.
18.3.6 Creating an Iron ASON Trail
You can create an ASON trail with protection type of Iron.
18.3.7 Viewing ASON Trails
Use this procedure to view ASON trails on the T2000. You can view ASON trails according to
specied lter criteria, the actual route of an ASON trail and the original route of a revertive
rerouting trail. You can customise how many columns can be shown in a list, print the list of
selected links, or save the list to le.
18.3.8 Viewing ASON Trail Details
You can view basic attributes and route constraints of an ASON trail.
18.3.9 Optimizing ASON Trails
You can optimize the routing of an ASON trail by adjusting the route with zero service
interruption.
18.3.10 Activating/Deactivating ASON Trails
You can activate or deactivate ASON trails.
18.3.11 Deleting ASON Trails
Deleting an ASON trail deletes the trail data from the T2000.
18.3.12 Locking/Unlocking ASON Trails
Use this procedure to lock or unlock a rerouting ASON trail.
18.3.13 Associating/Disassociating an ASON Trail
You can associate a rerouting ASON trail. When an ASON trail needs to be rerouted, the
recalculated route and the associated one do not overlap.
18.3.14 Setting Priorities for Rerouting ASON Trails
You can set priorities for rerouting ASON trails. When multiple ASON trails need to
be rerouted at the same time, the one with high priority is rerouted rst. Under special
circumstances, high priority services preempt the link resource of low priority ones to ensure
service survivability.
18.3.15 Degrading an ASON Trail to an SDH Trail
You can degrade an ASON trail to an SDH trail. After the degrade, the ASON trail becomes an
SDH trail and you can manage it in the Trail Management window through the trail search
feature.
18.3.16 Upgrading an SDH Trail to an ASON Trail
You can upgrade an SDH trail to an ASON trail. If the SDH trail is between ASON NEs, you
can upgrade the entire trail to an ASON trail. If part of the SDH trail is between ASON NEs,
you can upgrade the part to an ASON trail.
18.3.17 Switching a Diamond ASON Trail Manually
Use this procedure to manually switch the working route and protection route of an ASON
trail with 1+1 protection.

18.3.1 Synchronizing ASON Trails

You can synchronize the ASON links to keep the ASON links data in the T2000 consistent
with the ASON.
Prerequisites
n The ASON trail data must be congured on the T2000.
Procedure
Step 1 Select Conguration > ASON Trail Management from the Main Menu.

successful.
----End
18.3.2 Creating a Diamond ASON Trail

You can create an ASON trail with the protection type of Diamond.
Prerequisites
n The T2000 must have synchronized networkwide TE links and have sufcient TE link
resources.
Procedure
Step 2 Click Create and the creation wizard is displayed.
Step 3 Enter the basic information of the ASON trail.
Step 4 In the right-hand topology, double-click the source NE and select a slot, port and timeslot from
the pop-up dialog box. Click OK.

Step 5 The same as Step 4. In the right-hand topology, double-click the sink NE and select a slot, port
and timeslot from the pop-up dialog box. Click OK.
Step 6 Optional: Set the compulsory node or compulsory link for the workingor protection route.
Right-click an NE in the right-hand topology and select an option from the shortcut menu.

NOTE
n If you want to specify the timeslot when setting the compulsory link, select Browse from the
shortcut menu.
n After you select the Set Compulsory Link shortcut menu item, its submenu is displayed in a folded
manner if there are more than ten available compulsory links.
n To cancel the compulsory node or link, right-click the NE and select Cancel Compulsory Node or
Cancel Compulsory Link.
Step 7 Optional: Set the excluded node or excluded link for the working or protection route.

NOTE
To cancel the excluded node or link, right-click the NE and select Cancel Excluded Node or Cancel
Excluded Link.
Step 8 Optional: Check the Activate or Duplicate after created check box.
NOTE
If Activate is checked, the created ASON trail is sent to the NE and thus become active. If Duplicate
after created is checked, you can create multiple ASON trails that have the same source and sink by
duplicating this ASON trail.
Step 9 Make sure the ASON trail information and route constraints are entered correctly. Click Apply.
After the ASON trail is successfully created, the system prompts the operation succeeded.
----End
18.3.3 Creating a Gold ASON Trail

You can create an ASON trail with protection type of Gold on an MSP protected trail only.
You need to make sure MSP ring or linear MSP is congured for all links that the ASON
trail passes through. After you create a gold ASON trail, you are not allowed to modify the
attributes of the MSP protection subnet that the ASON trail passes through.
Prerequisites
n The T2000 must have synchronized the links of the overall network and have sufcient
link resources.
n All links that the ASON trail passes through are under MSP protection. Otherwise, you
need to create bers and congure MSP protection before proceeding to create 1:1
protected ASON trails.
Context
NOTE
The procedure for creating a gold ASON trail is similar to that described in "Creating a Diamond ASON
Trail". The only difference is the protection type is Gold.
Procedure


NOTE
shortcut menu.

NOTE
Excluded Link.
NOTE
----End
18.3.4 Creating a Silver ASON Trail

You can create an ASON trail with protection type of Silver.
Prerequisites
link resources.
Context
NOTE
Trail". The only difference is the protection type is Silver.
Procedure


NOTE
shortcut menu.

NOTE
Excluded Link.
NOTE
----End
18.3.5 Creating a Copper ASON Trail

You can create an ASON trail with protection type of Copper.
Prerequisites
link resources.
Context
NOTE
Trail". The only difference is the protection type is Copper.
Procedure


NOTE
shortcut menu.

NOTE
Excluded Link.
NOTE
----End
18.3.6 Creating an Iron ASON Trail

You can create an ASON trail with protection type of Iron.
Prerequisites
link resources.
Context
NOTE
Trail". The only difference is the protection type is Iron.
Procedure


NOTE
shortcut menu.

NOTE
Excluded Link.
NOTE
----End
18.3.7 Viewing ASON Trails

Use this procedure to view ASON trails on the T2000. You can view ASON trails according to
specied lter criteria, the actual route of an ASON trail and the original route of a revertive
rerouting trail. You can customise how many columns can be shown in a list, print the list of
selected links, or save the list to le.
Prerequisites
n The ASON trail must be created.
Procedure
Step 2 The list shows all ASON trails on the T2000. View information of each link.

For example, view whether the service is normal, or whether the working service is normal and
whether the protection service is interrupted.
Step 3 Optional: View ASON trails according to specied lter criteria. Click Filter. The Filter
Conditions dialog box is displayed. Specify the lter criteria and click Filter All. The
qualied ASON trails are shown in the list.
Step 4 Optional: View the actual route of an ASON trail. Select an ASON trail, and its actual route
is shown in the Actual Route list at the lower left side. Meanwhile, its route information is
illustrated in the topology view at the lower right side.
Step 5 Optional: Customise how many columns can be shown in a list. Right-click the heading of the
list, and select Customise Display. The Customise Display dialog box is displayed. Select
the columns you want to display, or adjust the order of the columns. Click Apply.

----End
18.3.8 Viewing ASON Trail Details

You can view basic attributes and route constraints of an ASON trail.
Prerequisites
Procedure
Step 2 Select an ASON trail to view from the list, right-click and select Details.
Step 3 View basic attributes of the ASON trail in the dialog box.

Step 4 Click the Route Constraints tab, and view the route constraints of the ASON trail.

Step 5 Optional: If the ASON trail is congured with associated ASON trails, view the attributes of
the associated ASON trails in the Attributes of associated ASON trails tab.

----End
18.3.9 Optimizing ASON Trails

You can optimize the routing of an ASON trail by adjusting the route with zero service
interruption.
Prerequisites
n The T2000 must have synchronized the links networkwide and have sufcient link
resources.
Procedure
Step 2 Select an ASON trail from the list, click Optimize. The wizard is displayed.

Step 3 Optional: Select the trail you wish to optimize, and set whether the trail comply with link
constraints.
Step 4 Optional: Set the included nodes and included links for the working route.
NOTE
n In the right-hand view, right-click the NE and set the included nodes and included links for the
working route.
n To cancel an included node or link, right-click the NE and select Set/Cancel Compulsory Node.
Step 5 Optional: Set the excluded nodes and excluded links for the working route.
NOTE
In the right-hand view, right-click the NE and set the excluded nodes and excluded links for the working
route.
Step 6 Make sure the information is entered correctly and click Apply.
Step 7 After the operation succeeded, click Cancel The optimization wizard closes.
Step 8 Select the optimized ASON trail from the list, and view its routing information in the Actual
Route eld.
----End
18.3.10 Activating/Deactivating ASON Trails

You can activate or deactivate ASON trails.
Prerequisites
Context
NOTE
Activate sends ASON trail data from the T2000 to the NE and activate the service specic to the trail
on the NE. Deactivate deletes the service specic to an ASON trail from the NE, keeping the ASON
trail data on the T2000 only.
Procedure
Step 2 Select an ASON trail from the list, right-click and select Activate.
NOTE
To deactivate the ASON trail, select Deactivate.

Step 3 After the operation is successfully complete, view whether the ASON trail is activated in
the list.
----End
18.3.11 Deleting ASON Trails

Deleting an ASON trail deletes the trail data from the T2000.
Prerequisites
n The ASON trail to delete must be in the Inactive state.
Procedure
Step 2 Select the ASON trail to delete from the list, right-click and select Delete.
Step 3 After the ASON trail is successfully deleted, the T2000 prompts that the operation was
successful.
----End
18.3.12 Locking/Unlocking ASON Trails

Use this procedure to lock or unlock a rerouting ASON trail.
Prerequisites
n The rerouting ASON trail must be created.
Procedure

Step 2 Select an ASON trail from the list, right-click and select Lock.
NOTE
To unlock a rerouting ASON trail, select Unlock.
Step 3 After the operation is complete, view the lock state of the ASON trail in the list.
----End
18.3.13 Associating/Disassociating an ASON Trail

You can associate a rerouting ASON trail. When an ASON trail needs to be rerouted, the
recalculated route and the associated one do not overlap.
Prerequisites
n At least two rerouting ASON trails must be created.
n The rerouting ASON trails to associate are not intersected.
Procedure
Step 2 Select an ASON trail from the list, right-click and select Set/Cancel Association.

NOTE
To disassociate an ASON trail, select Set/Cancel Association. Click Delete Association.
Step 3 In the ASON trail list below, select an ASON trail to associate with the one already selected.
Click Set Association.
Step 4 Click OK. The T2000 prompts the operation succeeds.
----End
18.3.14 Setting Priorities for Rerouting ASON Trails

You can set priorities for rerouting ASON trails. When multiple ASON trails need to
be rerouted at the same time, the one with high priority is rerouted rst. Under special
circumstances, high priority services preempt the link resource of low priority ones to ensure
service survivability.
Prerequisites
n The rerouting ASON trail must be created.
Procedure

Step 2 Select an ASON trail from the list, right-click and select High Priority.
NOTE
To change a high priority ASON trail to low priority, select Low Priority.
Step 3 After the operation is complete, view the priority of the ASON trail in the list.
----End
18.3.15 Degrading an ASON Trail to an SDH Trail

You can degrade an ASON trail to an SDH trail. After the degrade, the ASON trail becomes
an SDH trail and you can manage it in the Trail Management window through the trail
search feature.
Prerequisites
Context
NOTE
For end-to-end trails passing through an ASON network, perform the following operations if you need
to degrade the ASON part of the trail:
1. In the SDH Trail Management window, delete the ASON part of the trail from the network layer.
2. In the ASON Trail Management window, degrade the ASON part of the trail to an SDH trail.
3. Re-search and manage the trail through the SDH trail search feature.
Procedure
Step 2 Select an ASON trail from the list, right-click and select Degrade to SDH Class.


Step 4 After the operation is complete, select Trail > Trail Search from the Main Menu.
NOTE
Complete the search under the guide of the wizard.
Step 5 Select Trail > Trail Search from the Main Menu.
Step 6 In the Set Trail Browse Filter Criteria dialog box, click Filter All.
NOTE
You can view the SDH trail converted from the ASON trail in the list.
----End
18.3.16 Upgrading an SDH Trail to an ASON Trail

You can upgrade an SDH trail to an ASON trail. If the SDH trail is between ASON NEs, you
can upgrade the entire trail to an ASON trail. If part of the SDH trail is between ASON NEs,
you can upgrade the part to an ASON trail.
Prerequisites
n The SDH trail must pass through ASON NEs.
Procedure
Step 1 Select Trail > SDH Trail Management in the Trail View. The Set Trail Browse Filter
Step 2 Filter trails. The attributes of trails are shown in the list.
Step 3 Select one or more SDH trails, right-click and select Upgrade to ASON Trail > Full or
Upgrade to ASON Trail > Partially.
Step 4 Optional: Select Conguration > ASON Trail Management from the Main Menu. The
ASON trails upgraded from SDH trails are displayed in the list.
----End
18.3.17 Switching a Diamond ASON Trail Manually

Use this procedure to manually switch the working route and protection route of an ASON
trail with 1+1 protection.
Prerequisites
n The diamond ASON trail must be created and the path status is normal.
Procedure

Step 2 Select a diamond ASON Trail from the list, select Maintenance > Switch ASON Trail
Manually.
Step 3 After the operation is complete, select the ASON Trail from the list and check if its working
route and the protection route are switched.
----End
18.4 Viewing Alarms and Abnormal Events

You can view alarm information specic to ASON trails and abnormal events in the network,
to know faults and exceptions in the ASON network.
Context
18.4.1 Viewing Current Alarms of an ASON Trail

You can view the current alarms of an ASON trail.
18.4.2 Viewing History Alarms of an ASON Trail
You can view the history alarms of an ASON trail.
18.4.3 Viewing ASON Abnormal Events
You can view the abnormal events related to ASON network management.
18.4.1 Viewing Current Alarms of an ASON Trail

You can view the current alarms of an ASON trail.
Prerequisites
Procedure

Step 2 Select an ASON trail from the list, click Alarm and select Current Alarm.
Step 3 A dialog box is displayed showing the current alarms of the ASON trail.
----End
18.4.2 Viewing History Alarms of an ASON Trail

You can view the history alarms of an ASON trail.
Prerequisites
Procedure
Step 2 Select an ASON trail from the list, click Alarm and select History Alarm.
Step 3 A dialog box is displayed showing the history alarms of the ASON trail.
----End
18.4.3 Viewing ASON Abnormal Events

You can view the abnormal events related to ASON network management.
Prerequisites
n The ASON NE must be created.

Procedure
Step 1 Choose Fault > Browse Abnormal Event from the Main Menu.
Step 2 View the abnormal events related to ASON network management. Select one or more ASON
NEs in the Object Tree, click and the Abnormal Event Browse shows the abnormal
events of the selected NE.
NOTE
Network administrators decide whether to handle the abnormal events depending on specic conditions.
----End
18.5 Viewing Performance Monitoring Data

Network management personnel need to view performance monitoring data regularly to nd
problems in the network.
Context
18.5.120.9.1 Viewing Current Performance Data of an ASON Trail

You can view the current performance data of an ASON trail, including: 15-minute and
24-hour current performance data.
18.5.220.9.2 Viewing History Performance Data of an ASON Trail
You can view the history performance data of an ASON trail, including: 15-minute and
24-hour history performance data.
18.5.1 Viewing Current Performance Data of an ASON Trail

You can view the current performance data of an ASON trail, including: 15-minute and
24-hour current performance data.
Prerequisites
n Performance monitoring parameters must be congured.
Procedure
Step 2 Select an ASON trail from the list, click Performance and select 15-minute Current
Performance.
NOTE
To view the 24-hour current performance data of the ASON trail, select 24-hour Current Performance.
Step 3 A dialog box is displayed showing the performance data of the ASON trail.
----End
18.5.2 Viewing History Performance Data of an ASON Trail

You can view the history performance data of an ASON trail, including: 15-minute and
24-hour history performance data.

Prerequisites
n Performance monitoring parameters must be congured.
Procedure
Step 2 Select an ASON trail from the list, click Performance and select 15-minute History
Performance.
NOTE
To view the 24-hour history performance data of the ASON trail, select 24-hour History Performance.
Step 3 A dialog box is displayed showing the performance data of the ASON trail.
----End
18.6 Customising the ASON View

In a large network with many ASON NEs, the display of the ASON view is relatively unclear.
Using the view customisation function, you can customise which ASON NEs to be displayed
on the view.
Prerequisites
n The ASON network must be running properly.
Procedure
Step 1 Select Conguration > ASON View Customisation from the Main Menu.
Step 2 Click the View Customisation tab. In the NE tree, select the NEs to be displayed. Enter
a name in the View Name eld.
Step 3 Click OK. The view is successfully customised.
Step 4 Optional: Click the Legend tab to view the legends and their description.
Step 5 Optional: Click the Resource tab.
1. In the Threshold (%) eld, double-click the middle row, change the value, and click
Apply. The values in the other two rows change at the same time.
2. In the Resource Alert eld, double-click a color and the Set Color dialog box is
displayed. Set the color attributes and click OK. Click Apply.

NOTE
Check the Display Usable Resource check box to display the available resources in the view.
----End
18.7 Managing Reserved Resources

To specify some resources in the ASON network that are not used by ASON NE software, you
can set reserved resources for every ASON NE. For example, board ports, timeslots (specic to
VC-4). When an ASON trail is rerouted, the NE software avoids using the reserved resources.
Context
18.7.1 Conguring Reserved Resources

You can congure the board ports and timeslots on an ASON NE that are reserved for the NE
software. If there is ber connection between the reserved port and other ASON NEs, reserve
the same timeslot at the opposite end. That is, if you set an optical port at one end of a ber as
the reserved resource, you need to congure the same settings for the port at the other end.
18.7.2 Querying Reserved Resources
You can query the reserved resources on an ASON NE.
18.7.1 Conguring Reserved Resources

Prerequisites
n The ASON NE must be created and a line board (such as JL64) must be installed.
Procedure
Step 1 In the NE Explorer, select a board and select ASON > Resource Reservation Management
Step 2 Click Query to query the resource reservation of the board from the NE.
Step 3 Select the VC4 channel to be reserved for the management plane and set it to Yes.
Step 4 Click Apply.

----End
18.7.2 Querying Reserved Resources

You can query the reserved resources on an ASON NE.
Prerequisites
n The ASON NE must be created and a line board (such as the JL64) must be installed.
Procedure
Step 1 In the NE Explorer, select a board, and select ASON > Resource Reservation Management
Step 2 Click Query to query the reserved resources of the board from the NE.
NOTE
Repeat Steps 2 through 4 to query the reserved resources of other line boards.
----End
18.8 Managing Component Links

ASON component link is a bandwidth unit smaller than TE link. One TE link consists of only
one component link in the actual ASON software.
Context
18.8.1 Synchronizing Component Links

You can synchronize the component links to keep the component links data in the T2000
consistent with the ASON.
18.8.2 Viewing Component Links
Use this procedure to view component links on the T2000. You can display the component
links in different bandwidth units, view component links according to specied lter criteria,
print the list of selected component links, or save the list to le.
18.8.3 Adding/Deleting Component Links
In some cases, the link management protocol cannot discover TE links automatically. For
example, the J0 byte to be transmitted does not match the one to be received. Therefore, you
need to create TE links manually.
18.8.4 Setting Resource Reservation
18.8.1 Synchronizing Component Links

You can synchronize the component links to keep the component links data in the T2000
consistent with the ASON.
Prerequisites

Procedure
Step 1 Select Conguration > Component link Management from the Main Menu.
successful.
----End
18.8.2 Viewing Component Links

Use this procedure to view component links on the T2000. You can display the component
links in different bandwidth units, view component links according to specied lter criteria,
print the list of selected component links, or save the list to le.
Prerequisites
Procedure
Step 1 Select Conguration > Component link Management from the Main Menu.
Step 2 The list shows all component links on the T2000. View information of each component link.
Step 3 Optional: Select the desired bandwidth unit from the Bandwidth unit drop-down list.
For example, VC4. Then the list refreshes automatically and shows the component link
information in the selected bandwidth unit.
Step 4 Optional: Under Filter Criteria, select Source NE or Sink NE, and click Filter. The
qualied component links are shown in the list.

Step 6 Optional: Click Save As. Enter the start line number, end line number and le name. Click
OK to save the list to le.
----End
18.8.3 Adding/Deleting Component Links

In some cases, the link management protocol cannot discover TE links automatically. For
example, the J0 byte to be transmitted does not match the one to be received. Therefore, you
need to create TE links manually.

Prerequisites
Procedure
n Follow the steps below to create a component link.
1. Select Conguration > Component link Management from the Main Menu.
2. View information about component links in the list.
3. Click Create, the Create Component Link dialog box is displayed.
4. Set the parameters for the link. Click OK.
NOTE
After the component link is successfully created, and is successfully checked by the
ASON NE software, a TE link corresponds to the component link appears in the TE Link
Management window.
n Follow the steps below to delete a component link.

1. Select a link from the list and click Delete.
2. Conrm the operation to delete the link.
NOTE
After the component link is deleted successfully, the corresponding TE link is removed
automatically.
----End
18.8.4 Setting Resource Reservation

Prerequisites
Procedure
Step 1 Choose Conguration > Component Link Management from the Main Menu.
Step 2 The list displays all component links on the T2000. You can view the information of each
component link.
Step 3 Select a link in the list, right-click and choose Set Resource Reservation. The Set Resource
Reservation dialog box is displayed.
Step 4 In the Resource Reservation area, set the timeslot. Click Apply.
Step 6 Set other timeslots in the Set Resource Reservation dialog box and repeat Steps 4 through 5.
NOTE
If you want to cancel the resource reservation settings, click the reserved timeslot(s) you already congure
Step 7 and click Cancel in the Set Resource Reservation dialog box.

----End
18.9 Managing the Control Plane

The control plane consists of communication entities for call control and connection control.
The communication entities establish, release, monitor and maintain connections, and recover
connections automatically in the event of failure using signaling.
Context
The T2000 manages the ASON control plane as follows:
18.9.1 Synchronizing Control Links

You can synchronize the control links to keep the control links data in the T2000 consistent
with the ASON.
18.9.2 Viewing Control Links
Use this procedure to view control links on the T2000. You can view control links according to
specied lter criteria, print the list of selected control links, or save the list to le.
18.9.3 Setting Rerouting Reversion Time
You can set the reversion time for a rerouting ASON trail. After the conguration is sent to
the NE, the conguration is available to all revertive rerouting ASON trails with the NE
as the source.
18.9.4 Setting Route Calculation Strategies
You can set the route calculation strategies for an ASON NE. The strategies includes bandwidth
occupancy ratio, bandwidth weight, distance weight, and hop weight.
18.9.5 Enabling OSPF Protocol
You can set whether to start the OSPF protocol at an optical port on a line board. If the
OSPF protocol is started at an optical port, you need to include it in route planning. If some
optical ports are not connected with bers, or equipment from other vendors is at the opposite
end, route planning fails. Limited control channel resources are wasted. For example, UNI
interface, the exterior network interface is connected to equipment from other vendors. In this
case, you need to set the OSPF protocol to disabled for the port.
18.9.6 Viewing the Link Management Protocol
Use this procedure to view the link management protocol for an Ethernet port. The control
channel on an SDH line board is discovered automatically, and cannot be created or deleted.
18.9.7 Creating Control Channel
Use this procedure to create control channel for an Ethernet port. The control channel on an
SDH line board is discovered automatically, and cannot be created or deleted.
18.9.1 Synchronizing Control Links

You can synchronize the control links to keep the control links data in the T2000 consistent
with the ASON.
Prerequisites
Procedure
Step 1 Select Conguration > Control Link Management from the Main Menu.
successful.

NOTE
Information about control links is shown in the list.
----End
18.9.2 Viewing Control Links

Use this procedure to view control links on the T2000. You can view control links according to
specied lter criteria, print the list of selected control links, or save the list to le.
Prerequisites
Procedure
Step 1 Select Conguration > Control Link Management from the Main Menu.
Step 2 The list shows all control links on the T2000. View information of each component link.
Step 3 Optional: Under Filter Criteria, select lter condition, for examples: Source NE or Sink
NE, and click Filter.
NOTE
The qualied control links are shown in the list. The topology of links is shown in graphical format
in the view.
Step 4 Optional: Click Print to export the list to the browser of the operating system for printing.
----End
18.9.3 Setting Rerouting Reversion Time

You can set the reversion time for a rerouting ASON trail. After the conguration is sent to
the NE, the conguration is available to all revertive rerouting ASON trails with the NE
as the source.
Prerequisites
n The ASON NE must be created and congured.
Procedure
Step 1 In the NE Explorer, click an NE and select ASON > Control Plane Parameters from the
Function Tree.

Step 2 Click Query to query the reversion time of the revertive rerouting ASON trail from the NE.
Step 3 Set a value in the Revertive Rerouting Reversion Time eld.
Step 4 Click Apply.
----End
18.9.4 Setting Route Calculation Strategies

You can set the route calculation strategies for an ASON NE. The strategies includes bandwidth
occupancy ratio, bandwidth weight, distance weight, and hop weight.
Prerequisites
n The ASON NE must be created and congured.
Procedure
Step 1 In the NE Explorer, click an NE and select ASON > Control Plane Parameters from the
Function Tree. Select the Route Calculate Strategy tab.
Step 2 Click Query to query the route calculation strategy from the NE.

Step 3 Set a value in the Route Calculate Strategy eld. Complete the other information.
Step 4 Click Apply.
----End
18.9.5 Enabling OSPF Protocol

You can set whether to start the OSPF protocol at an optical port on a line board. If the
OSPF protocol is started at an optical port, you need to include it in route planning. If some
optical ports are not connected with bers, or equipment from other vendors is at the opposite
end, route planning fails. Limited control channel resources are wasted. For example, UNI
interface, the exterior network interface is connected to equipment from other vendors. In this
case, you need to set the OSPF protocol to disabled for the port.
Prerequisites
n The ASON NE must be created and a line board must be installed.
Context
CAUTION
Disabling the OSPF protocol for all ports in an NE causes route module failure and thus the
NE has no intelligent routing function. Perform this operation with care.
Procedure
Step 1 Click the board as required in the NE Explorer, and select ASON > Enable OSPF Protocol
Step 2 Click Query to query the protocol status of every optical port from the NE.
Step 3 Select an optical port, and select Enabled or Disabled in the Enable OSPF Protocol eld.
Step 4 Click Apply.
----End
18.9.6 Viewing the Link Management Protocol

Use this procedure to view the link management protocol for an Ethernet port. The control
channel on an SDH line board is discovered automatically, and cannot be created or deleted.

Prerequisites
n The ASON network runs properly.
Procedure
Step 1 In the NE Explorer, click the NE and select ASON > Link Management Protocol from the
Function Tree.
Step 2 Optional: Click the Control Channel tab. Click Query to query control channels of the link
management protocol from the NE.
Step 3 Optional: Click the TE Link tab. Click Query to query TE links of the link management
protocol from the NE.
Step 4 Optional: Click the Component Link tab. Click Query to query component links of the link
----End
18.9.7 Creating Control Channel

Use this procedure to create control channel for an Ethernet port. The control channel on an
SDH line board is discovered automatically, and cannot be created or deleted.
Prerequisites
n The ASON network runs properly.
Procedure
Step 1 In the NE Explorer, click the NE and select ASON > Link Management Protocol from the
Function Tree.

Step 2 Optional: Click the Control Channel tab. Click Query to query control channels of the link
Step 3 Click Create and the Create Control Channel dialog box is displayed. Enter a value in the
Remote Address and Next Hop Address elds respectively.
Step 4 Click Apply.
NOTE
You can view the created link in the list.
----End
18.10 Querying ASON Information on a Per-NE Basis

You can query ASON trails, TE links, control links and component links from the NE.
Context
You can query the following ASON information on a per-NE basis:
18.10.1 Querying ASON Trails

You can query ASON trail information on a per-NE basis.
18.10.2 Querying TE Links
You can query TE link information on a per-NE basis.
18.10.3 Querying Component Links
You can query component link information on a per-NE basis.
18.10.4 Querying Control Links
You can query control link information on a per-NE basis.
18.10.1 Querying ASON Trails

You can query ASON trail information on a per-NE basis.
Prerequisites
n The ASON feature of the NE is enabled.
Procedure
Step 1 In the NE Explorer, click the NE and select ASON > ASON Trail from the Function Tree.
Step 2 Optional: Select a query mode in Query ASON Trail.

NOTE
There are four query modes: With this node as source, With this node as the intermediate node, With
this node as sink, and Passing through this node.
Step 3 Click Query.

----End
18.10.2 Querying TE Links

You can query TE link information on a per-NE basis.
Prerequisites
Procedure
Step 1 In the NE Explorer, click the NE and select ASON > TE Link from the Function Tree.
Step 2 Optional: Select a desired unit in Bandwidth Units.
NOTE
There are four bandwidth units: VC4, VC3, VC12, and kbit/s.
Step 3 Click Query.

----End
18.10.3 Querying Component Links

You can query component link information on a per-NE basis.
Prerequisites
Procedure
Step 1 In the NE Explorer, click the NE and select ASON > Component Link from the Function Tree.
Step 2 Optional: Select a desired unit in Bandwidth Units.
NOTE
There are four bandwidth units: VC4, VC3, VC12, and kbit/s.
Step 3 Click Query.

----End
18.10.4 Querying Control Links

You can query control link information on a per-NE basis.
Prerequisites

Context
Procedure
Step 1 In the NE Explorer, click the NE and select ASON > Control Link from the Function Tree.
Step 2 Click Query.
----End
Examples
Postrequisite
18.11 Advanced Maintenance for ASON Control Plane

When discrete signaling exists in an ASON, you can query or maintain it by using the
advanced maintenance for ASON control plane.
Context
18.11.1 Maintaining ASON Signaling

The user can perform maintenance operations, such as querying and degrading, for ASON
signaling of an NE.
18.11.2 Maintaining the ASON Switch Controller
The user can perform maintenance operations, such as querying and degrading, for the ASON
switch controller.
18.11.1 Maintaining ASON Signaling

The user can perform maintenance operations, such as querying and degrading, for ASON
signaling of an NE.
Prerequisites
Procedure
Step 1 In the NE Explorer, select ASON > Advanced Maintenance for ASON Control Plane.
Step 2 Click the ASON Signaling Maintenance tab. Select a query mode under Query ASON Trail,
and click Query to query the ASON signaling information from the NE.

Step 3 Select one or more ASON signalings. Right-click and select Degrade ASON Signaling from
the shortcut menu. A prompt appears telling you that the operation was successful.
----End
18.11.2 Maintaining the ASON Switch Controller

The user can perform maintenance operations, such as querying and degrading, for the ASON
switch controller.
Prerequisites
Procedure
Step 1 In the NE Explorer, select ASON > Advanced Maintenance for ASON Control Plane.
Step 2 Click the ASON Switch Controller Maintenance tab. Click Query to query the ASON
switch controller information from the NE.
Step 3 Select one or more ASON switch controllers. Right-click and select Degrade ASON Switch
Controller from the shortcut menu. A prompt appears telling you that the operation was
successful.
----End

Operator Guide 19 Viewing Reports
19 Viewing Reports
About This Chapter

The network provides a wide variety of reports with the information of network parameters
and running status. From the angle of the whole network, the reports include the networking
diagram and the networkwide data report. From the angle of NEs and boards, the reports
include all kinds of NE and board information reports. All these reports are helpful for
network maintenance.
19.1 Report Types Supported by the T2000

The T2000 provides a variety of reports, helping you to query and save information.
19.2 Viewing the Networking Diagram
You can generate and print the networking diagram. In the networking diagram, you can query
the information of NE name, type, ID, extended ID, orderwire phone, and ber/cable length.
The display and the NE positions of the networking diagram are consistent with those of the
Main Topology. After the networking is complete, save the networking diagram in time.
19.3 Viewing the Networkwide Data Report
You can generate and print the networkwide data report. The NE-based report helps you to
query information about NEs for quick NE localization. After you complete the networking,
you need to update the networkwide data report that you can refer to when you maintain the
network.
19.4 Viewing the Clock Tracing Diagram
The clock tracing diagram includes such NE information as name, type, ID and extended ID,
as well as all clock sources for the NE and their priorities. 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 of the network (for
example, new NEs are added), save the updated clock tracing diagram in time.
19.5 Viewing the Timeslot Allocation Diagram
When managing SDH networks, the timeslot assignment diagram helps you to know what
services have been congured in the selected protection subnet. After conguring new
services, you need to save the latest timeslot assignment diagram immediately.
19.6 Viewing the NE Information Report
In the NE information report, you can view the information of all NEs in the network,
including NE name, equipment type, ID, extended ID, ber/cable count, afliated subnet,
gateway type, and gateway attributes.
19.7 Viewing the Slot Conguration Report
You can generate and print the slot conguration report. After a new board is added to an
NE, you need to update the slot conguration report. Thus you can query information about
board slots for the NE in a quick manner.
19.8 Viewing the Slot Information Report
You can generate and print the slot information report. When conguring a new board, you
need to query the slot information, so you need to update the slot information report when
there is any change with to board slots.

19 Viewing Reports Operator Guide
19.9 Viewing the Board Count Report

You can generate and print the board count report. This report provides the information about
the board types on an NE and the board count of each type.
19.10 Viewing the Board Information Report
You can generate and print 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 conguring or updating a board, update the board information in
time for the sake of easy board management.
19.11 Viewing the Board Details Report
You can generate and print the board details report. After conguring a new board, you need to
update the board details report which you can refer to during board maintenance.
19.12 Viewing the Fiber/Cable Connection Report
You can generate and print the ber/cable connection report. This report provides the
information of ber/cable level, source NE, source port, sink NE and sink port. After
connecting bers, update the ber/cable connection report in time.
19.13 Viewing the Physical Location Information Report
Use this procedure to generate and print the physical location information report. This report
includes the physical equipment information for the equipment room, cabinet and subrack.
The information is useful for the planning of subrack positions in an equipment room.

19.1 Report Types Supported by the T2000

The T2000 provides a variety of reports, helping you to query and save information.
Reports are classied into two types: equipment conguration and service conguration.
n The equipment conguration report provides the equipment hardware conguration
information that you can refer to at the initial stage of network construction.
n The service conguration report provides the service conguration information of a
specic operation entity that you can refer to during network maintenance.
After a report is generated, it can be ltered, viewed, printed or saved as a text le. In the T2000
user interface, almost all the data in the form of a list can be exported to a report and printed.
19.2 Viewing the Networking Diagram

You can generate and print the networking diagram. In the networking diagram, you can query
the information of NE name, type, ID, extended ID, orderwire phone, and ber/cable length.
The display and the NE positions of the networking diagram are consistent with those of the
Main Topology. After the networking is complete, save the networking diagram in time.
Procedure
Step 1 Select Report > Networking Diagram from the Main Menu.
You can view the related information in the generated networking diagram.
Step 2 Optional: Right-click in the networking diagram and select Print or Save to export the
networking diagram.
----End
19.3 Viewing the Networkwide Data Report

You can generate and print the networkwide data report. The NE-based report helps you to
query information about NEs for quick NE localization. After you complete the networking,
you need to update the networkwide data report that you can refer to when you maintain the
network.
Prerequisite
The board software supports the version information function.
Procedure
Step 1 Select Report > Networkwide Data Report from the Main Menu.
You can view the information in the generated report.
Step 2 Optional: Click Print or Save As to export the report.
----End
19.4 Viewing the Clock Tracing Diagram

The clock tracing diagram includes such NE information as name, type, ID and extended ID,
as well as all clock sources for the NE and their priorities. 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 of the network (for
example, new NEs are added), save the updated clock tracing diagram in time.

Procedure
Step 1 Select Report > Clock Tracing Diagram from the Main Menu.
View the information in the generated clock tracing diagram.
Step 2 Optional: Right-click in the clock tracing diagram and select Print or Save to export the
report.
----End
19.5 Viewing the Timeslot Allocation Diagram

When managing SDH networks, the timeslot assignment diagram helps you to know what
services have been congured in the selected protection subnet. After conguring new
services, you need to save the latest timeslot assignment diagram immediately.
Prerequisite
The protection subnet must be created.
Context
NOTE
The T2000 exports the timeslot assignment diagram in SVG format. To view or print the diagram, you
need to install the SVG Viewer. In Windows, refer to client\SVG\PC\pcreadme.txt for how to install
the SVG Viewer; In UNIX, refer to client\SVG\Unix\unixreadme.txt. The installation takes not more
than ve minutes.
Procedure
Step 1 Select Report > Timeslot Allocation Diagram from the Main Menu.
Step 2 Select a protection subnet in the Generate Timeslot Allocation Diagram dialog box. Click
Begin.
The T2000 generates the timeslot allocation diagram of this protection subnet and save it in
the client\report directory.
Step 3 Navigate to the client\report directory, double-click the SVG le 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
19.6 Viewing the NE Information Report

In the NE information report, you can view the information of all NEs in the network,
including NE name, equipment type, ID, extended ID, ber/cable count, afliated subnet,
gateway type, and gateway attributes.
Procedure
Step 1 Select Report > NE Information Report from the Main Menu. Click the NE Information
Report tab.
Step 2 Select NEs from the Object Tree 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.
----End

19.7 Viewing the Slot Conguration Report

You can generate and print the slot conguration report. After a new board is added to an
NE, you need to update the slot conguration report. Thus you can query information about
board slots for the NE in a quick manner.
Prerequisite
The report can be generated only when the board software of the board that you want to query
supports the query of board version information.
Procedure
Step 1 Select Report > Slot Conguration Report from the Main Menu.
Step 2 Select an NE from the Object Tree, and click the double-right-arrow button (red).
You can view the generated report in the right-hand pane.
----End
19.8 Viewing the Slot Information Report

You can generate and print the slot information report. When conguring a new board, you
need to query the slot information, so you need to update the slot information report when
there is any change with to board slots.
Prerequisites
n The board must be installed.
n The board software supports the version information function.
Procedure
Step 1 Select Report > Board Information Report from the Main Menu.
Step 2 Click the Slot Information Report tab.
Step 3 Select NEs or boards from the Object Tree, and click the double-right-arrow button (red).
Step 5 Click the Slot Information tab. Click Print or Save As to export the report.
----End
19.9 Viewing the Board Count Report

You can generate and print the board count report. This report provides the information about
the board types on an NE and the board count of each type.
Procedure
Step 2 Click the Board Count Report tab.

Step 3 Select an NE from the Object Tree, and click the double-right-arrow button (red).
Step 5 Optional: Click Print or Save to File as needed.
----End
19.10 Viewing the Board Information Report

You can generate and print 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 conguring or updating a board, update the board information in
time for the sake of easy board management.
Prerequisite
The report can be generated only when the board software of the board that you wish to query
Procedure
Step 2 Click the Board Information Report tab. Select NEs from the Object Tree and click the
double-right-arrow button (red).
Step 4 Optional: Click Print or Save as to export the report.
----End
19.11 Viewing the Board Details Report

You can generate and print the board details report. After conguring a new board, you need to
update the board details report which you can refer to during board maintenance.
Prerequisite
The report can be generated only when the board software of the board that you wish to query
Procedure
Step 1 Select Report > Board Details Report from the Main Menu.
Step 2 Select NEs from the left Object Tree and click the double-right-arrow button (red).
Step 4 Optional: Click Print or Save to File to export the report.
----End

19.12 Viewing the Fiber/Cable Connection Report

You can generate and print the ber/cable connection report. This report provides the
information of ber/cable level, source NE, source port, sink NE and sink port. After
connecting bers, update the ber/cable connection report in time.
Prerequisite
Fibers/cables must be created on the T2000.
Procedure
Step 1 Select Report > Fiber/Cable Connection Report from the Main Menu.
Step 2 Select NEs from the Object Tree and click the double-right-arrow button (red).
----End
19.13 Viewing the Physical Location Information Report

Use this procedure to generate and print the physical location information report. This report
includes the physical equipment information for the equipment room, cabinet and subrack.
The information is useful for the planning of subrack positions in an equipment room.
Prerequisite
The subrack information has been modied according to the actual situations, and cabinet and
equipment room information have been created.
Procedure
Step 1 Select Report > Physical Location Information Report from the Main Menu.
Step 2 Click the Equipment Room, Cabinet or Subrack tab.
Step 3 Optional: Click Print or Save as to export the report.
----End

Operator Guide 20 Guaranteeing Network Performance
20 Guaranteeing Network Performance
About This Chapter

To guarantee that the network is working normally, network management and maintenance
engineers need to check and monitor the network by using the T2000 regularly.
Context
20.1 Alarm
When an alarm is generated on the T2000, it indicates the T2000 or an NE is malfunctioning,
or a service has degraded or failed. Network maintenance personnel must locate the fault
according to the alarm, and decide what to do according to the alarm severity and alarm type.
20.2 Setting Networkwide Alarm Monitoring Strategy
When there is a large number of NEs, a lot of alarms may exist in the network. Network
maintenance and monitoring engineers can set alarm monitoring strategy, to focus on important
alarms and services and improve management efciency.
20.3 Setting NE Alarm Monitoring Strategy
To facilitate administration, you need to set the storage mode, reversion mode, and alarm
delay time for NE alarms.
20.4 Setting T2000 Alarm Monitoring Strategy
You can suppress a T2000 alarm of less importance or increase the severity level of a T2000
alarm, to improve alarm monitoring efciency.
20.5 Setting Board/Port Alarm Monitoring Strategy
To improve alarm management efciency, network maintenance and monitoring engineers can
set the alarm monitoring strategy for every board or port, according to whether services are
turned up and whether services are important.
20.6 Setting the Alarm Monitoring Strategy for SDH Trails
To focus on important alarms and services and improve alarm handling efciency, you can set
alarm monitoring strategy for SDH trails.
20.7 Setting Performance Monitoring Strategy
Network maintenance engineers can set performance monitoring and performance parameters
for the heavily concerned NEs and boards, to monitor the operation of important equipment
and services.
20.8 Viewing Alarms
To have an idea of the network status, network maintenance personnel can view alarms.
20.9 Viewing Performance Data
To know whether there are potentially service-affecting problems in the network that will not
generate alarms, you can view performance data and take necessary actions to avoid faults.
20.10 Resetting Performance Registers
After a network test or fault recovery, you need to reset the performance register to enter a
new performance monitoring period.

20 Guaranteeing Network Performance Operator Guide
20.11 Checking Protection Switching Status

You can congure protection subnets, board protection and other protection modes for the
OptiX equipment. To detect the fault that makes the protection facility unavailable, you need
to check the protection switching status for protection subnets and boards regularly.
20.12 Managing Overhead Bytes
You can set and query SDH overhead bytes.
20.13 Managing Logs
Logs provide a sequential record of events, which helps network administrators to nd illegal
logins and unauthorized operations, or to analyze faults.
20.14 Ethernet OAM Maintenance
You can perform Ethernet operation, administration and maintenance (OAM) operations.
20.15 Maintaining Ethernet OAM at a Station
You can perform Ethernet operation, administration and maintenance (OAM) operations at a
station. You can maintain Ethernet Layer 2 through the Ethernet OAM function.
20.16 Testing the Ethernet Communication Status
The Ethernet test is used for commissioning and fault location.
20.17 Guaranteeing Laser Performance
The input and output optical power of board ports is an important index for measuring laser
performance. Laser performance is crucial for the quality and transmission distance of
signals. To keep the entire transmission system running stably, you need to guarantee laser
performance, that is, to control the input and output optical power of the ports, and uctuation
of upper and lower threshold of input optical power within the appropriate range, and to
correct or alert optical power offset.
20.18 Collecting Equipment Data
In the event of equipment failure, you need to collect equipment data. The data collection
command and results are saved to a le for fault diagnosis. The equipment data that you
can collect includes: Basic conguration, service conguration, interface conguration,
Metro management, equipment protection, equipment maintenance, testing, performance, NE
communication management and security.
20.19 Disabling Service-Affecting Settings Automatically
Loopback and laser shutdown are useful NE maintenance functions. But they interrupt services
at a port and may interrupt the communication between an NE and the T2000. You can set
automatic disabling before performing loopback or laser shutdown, so that the NE cancels
loopback or laser shutdown automatically.
20.20 Cleaning Up the Hard Disk of the Computer
As the T2000 runs, dumped data accumulates and occupies more server space. You are
recommended to regularly check the server space and the size of the dump folder, and delete
unnecessary les to ensure the space for the proper running of the T2000.

20.1 Alarm
When an alarm is generated on the T2000, it indicates the T2000 or an NE is malfunctioning,
or a service has degraded or failed. Network maintenance personnel must locate the fault
according to the alarm, and decide what to do according to the alarm severity and alarm type.
Alarm Type
Alarms are classied into fault alarms and event alarms.
n Fault alarms: Correspond to specic statuses of the equipment. When an alarm occurs,
the status is set to a value. When the alarm recovers, the status is set to another value.
Usually a fault alarm is severer than an event alarm. A fault alarm always contains an
occurrence value and a recovery value, which are corresponding to each other.
n Event alarms: Thee accidental events during the operation of the equipment and indicate
the transient status of the equipment. The event alarm occurs without recovery as some
event alarms repeat periodically.
Alarm Category for Network Management

Alarms are classied into six categories based on the network management standard.
n Communication alarms: Alarms related to NE communication, ECC communication, and
optical signal communication. For example, loss of NE communication and loss of signal.
n Processing alarms: Alarms related to software processing and abnormal conditions. For
example, equipment bus collision and secondary path check failure.
n Equipment alarms: Alarms related to equipment hardware. For example, laser failure
and optical port loopback.
n Service alarms: Alarms related to the service status and QoS. For example, performance
threshold-crossing of the multiplex section, and excessisve B2 bit errors.
n 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.
n Security alarms: Alarms related to the security of T2000 and NEs. For example, an
NE user is not logged in.
Alarm Severity
Alarm severity is used to identify the severity level, signicance and urgency of an alarm.
Alarms come in the following four levels in descending order of severity: critical, major,
minor and warning. The following table lists the processing for each alarm severity:
Alarm severity Denition Handling
Critical Refers to fault alarms and Should be handled
event alarms that may result immediately. Otherwise,
in breakdown of the NE and the system may break down.
the whole system, such as
AMP board failure and clock
board failure.
Major Refers to fault alarms and Should be handled timely.
event alarms of boards or Otherwise, the important
line in local parts. functions will be affected.

Alarm severity Denition Handling

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 efciently
or line, such as board locate the alarm causes and
resetting, PCM alarm, public eliminate the possible faults.
resource application failure
and occupation timeout.
Warning Refers to fault alarms and Such alarms indicate
event alarms for warning, operating status of the
such as switching alarm. switch and need no handling.
Current Alarms
Fault alarms that have not been recovered or acknowledged by the system, and emergency
event alarms that have been reported to the alarm box but unacknowledged by the user.
Alarm Logs
The T2000 can dump all alarms raised in the system, including recovered fault alarms,
unrecovered fault alarms and all event alarms, and save them in the log le.
20.2 Setting Networkwide Alarm Monitoring Strategy

When there is a large number of NEs, a lot of alarms may exist in the network. Network
maintenance and monitoring engineers can set alarm monitoring strategy, to focus on important
alarms and services and improve management efciency.
Context
You can congure the following alarm settings on the T2000:
20.2.1 Creating Alarm Attribute Templates

You can create templates for most common alarm attribute settings. Based on the preset
templates, you can set alarms that need to be reported to the T2000 and their severity levels for
multiple NEs. So, only the concerned alarms are reported to the T2000. If multiple NEs report
a large number of unimportant alarms frequently, you can perform this operation.
20.2.2 Alarm Correlation
If you dene the correlation between alarm 1 and alarm 2, when alarm 1 occurs, the T2000
automatically suppresses alarm 2 or increase the severity level of alarm 2. This function helps
the network maintenance personnel to focus on root alarms or heavily concerned services only.
20.2.3 Setting Alarm Correlation Rules
Some alarms cause other alarms at the same time, which results in a great deal of alarms raised
at the same time. To locate the fault quickly, you can create alarm correlation rules to suppress
the alarms which are induced by other alarms.
20.2.4 Enabling Automatic Alarm Handling
To reduce the number of alarms and help network administrators to focus the current alarms
only, you need to enable automatic acknowledgement, automatic synchronization and
correlation analysis of alarms.
20.2.5 Customising Alarm and Abnormal Event Colors
Network administrators can customise the colors of NEs shown on the T2000 when alarms and
abnormal events at different severities are generated.
20.2.6 Setting Alarm Forwarding
Use this procedure to enable maintenance engineers to know how the network operates at
any moment. The T2000 provides alarm forwarding. If an alarm occurs, the T2000 sends a
message to the appointed engineer’s email box or mobile phone.

20.2.7 Enabling Visual and Audible Alarm in the Alarm Box

To enable the T2000 to notify the maintenance engineer through the alarm sound and
indicators in the alarm box when an alarm is raised, you need to enable visual and audible
alarm notication.
20.2.8 Setting Alarm Filter Status
After NEs report alarms to the T2000, the T2000 decides whether to display and save the
alarm information depending on the alarm lter status. When there are many NEs, you can
use this function to improve your efciency.
20.2.9 Setting Alarm Dump Conditions
To avoid alarm data overow or damage, you need to dump the alarm data in time. You can
dump the alarm data manually if necessary, or set the alarm dump conditions in the T2000
to automatically dump the alarm data. There are two ways of automatic dump: overow
dump and periodic dump.
20.2.1 Creating Alarm Attribute Templates

You can create templates for most common alarm attribute settings. Based on the preset
templates, you can set alarms that need to be reported to the T2000 and their severity levels for
multiple NEs. So, only the concerned alarms are reported to the T2000. If multiple NEs report
a large number of unimportant alarms frequently, you can perform this operation.
Prerequisite
Context
NOTE
If the template is not created, the T2000 uses the default template to handle all alarms reported from
the NE.
Procedure
Step 1 Select Fault > NM Alarm Attribute from the Main Menu.
Step 2 Click the Alarm Attribute Template tab.
Step 3 Select a template from the Template Name drop-down list.
Step 4 Select the alarm that you want to modify. Modify the values in the Alarm Severity, Alarm
Auto-Report and Alarm Suppression elds.
Step 5 Click Save to save the modication, or click Save As and enter a template name to save it
as a new template.
Step 6 Click Apply to and select the NE to which you want to apply the template. Click OK.
NOTE
After the template is applied to the NE, the T2000 automatically handles the alarms reported from the
NE according to the template.
----End
20.2.2 Alarm Correlation

If you dene the correlation between alarm 1 and alarm 2, when alarm 1 occurs, the T2000
automatically suppresses alarm 2 or increase the severity level of alarm 2. This function helps
the network maintenance personnel to focus on root alarms or heavily concerned services only.
Alarm correlation is illustrated as follows:

NE1, NE2, and NE3 comprise a non-protection chain with services traveling between every
two NEs. If the ber between NE1 and NE2 is cut, NE2 reports an R-LOS alarm. At the
same time, NE2 and NE3 report a lot of TU-AIS alarms that are associated with the R-LOS
alarm of NE2. In this case, you can set the alarm correlation rule to use the R-LOS alarm of
NE2 to suppress the TU-AIS alarms of NE2 and NE3. With less alarms are reported, fault
location is easier.
Alarm correlation rules are applicable in the following cases:
n Alarm 1 and alarm 2 occur on the same object.
n Alarm 1 occurs on the upstream of alarm 2 service.
n Alarm 1 occurs on the opposite end of alarm 2 service.
The following rules are supported:
n Alarm 1 suppresses alarm 2
n Increase the severity level of alarm 1
n Increase the severity level of alarm 2
n Increase the severity level of alarm 1 and alarm 2
20.2.3 Setting Alarm Correlation Rules

Some alarms cause other alarms at the same time, which results in a great deal of alarms raised
at the same time. To locate the fault quickly, you can create alarm correlation rules to suppress
the alarms which are induced by other alarms.
Prerequisite
Procedure
Step 2 Click the Set Alarm Correlation Rules tab.
Step 3 Click Create to add a new rule entry is added.
Step 4 Select a value in the Alarm 1, Alarm 2, Conditions and Action elds respectively.
Step 5 Click Apply.
Step 6 Optional: If you want to enable the alarm correlation rules, click the Set Alarm Function
Switch tab.
Step 7 Optional: Check the Enable Alarm Correlation Analysis check box. Click Apply to enable
the rules.
----End
20.2.4 Enabling Automatic Alarm Handling

To reduce the number of alarms and help network administrators to focus the current alarms
only, you need to enable automatic acknowledgement, automatic synchronization and
correlation analysis of alarms.
Prerequisite

Procedure
Step 1 Select Fault > NM Alarm Attribute from the Main Menu. Click the Alarm Function
Switch tab.
Step 2 In the upper-left corner, check the Auto Acknowledge Switch check box, and select a value
from the Alarm Ending Date drop-down list.
For example, if you set the Alarm Ending Date to 2, the T2000 will automatically
acknowledge alarms, which have been cleared two days, at 3 a.m. every day.
Step 3 In the lower-left corner, select one or more conditions to trigger automatic alarm
synchronization.
NOTE
For example, if When Starting the NM is checked, alarm synchronization is executed automatically
when the T2000 is started up.
Step 4 In the upper-right corner, check the Enable Alarm Correlation Analysis check box.
NOTE
If it is enabled, the reported alarms will be analyzed according to alarm correlation analysis rules. In
this case, only the major alarms will be displayed, and the minor alarms induced by major alarms will
be suppressed. This function benets alarm analysis when too many alarms are reported and interfere
with the alarm analysis.
Step 5 In the lower-right corner, check the Automatically Change End Alarm into History Alarm
check box.
NOTE
If it is enabled, the ended alarms will be acknowledged and transferred to history alarm database
automatically.
Step 6 Click Apply.

----End
20.2.5 Customising Alarm and Abnormal Event Colors

Network administrators can customise the colors of NEs shown on the T2000 when alarms and
abnormal events at different severities are generated.
Prerequisite
Procedure
Step 1 Select File > Custom Options from the Main Menu. Click the Color tab.
Step 2 Select an event, and double-click the Color option.
Step 3 Select a color in the Set Color dialog box, and click OK.
Step 4 Optional: If you want to restore the color to the default setting, click Default.
Step 5 Click OK.
----End
20.2.6 Setting Alarm Forwarding

Use this procedure to enable maintenance engineers to know how the network operates at
any moment. The T2000 provides alarm forwarding. If an alarm occurs, the T2000 sends a
message to the appointed engineer’s email box or mobile phone.

Prerequisite
Procedure
Step 1 Select Fault > Set Alarm Notication from the Main Menu.
Step 2 Click Create to add an entry.
Step 3 Enter the values in the User Name and Communication Number/Email Address elds.
Specify the Communication Mode, Severity, Alarm Type, NE and Switch parameters.
NOTE
There are two communication modes: mobile phone and email.
The T2000 sends messages only when raised alarms are compliant with the alarm settings. You can
create up to 15 entries.
Step 4 Optional: If the communication mode is Email, click Communication Settings and set
the SMTP address.
Step 5 Click Apply.
----End
20.2.7 Enabling Visual and Audible Alarm in the Alarm Box

To enable the T2000 to notify the maintenance engineer through the alarm sound and
indicators in the alarm box when an alarm is raised, you need to enable visual and audible
alarm notication.
Prerequisite
Context
n The alarm box has four alarm severities: emergency, important, common and notication.
They correspond to the four alarm severities of the T2000: critical, major, minor, and
warning.
n The alarm box has different alarm beeps: For an emergency or important alarm, the
alarm box beeps until it is manually stopped or until the alarm is cleared. For a common
or notication alarm, it beeps for a xed time period (one minute) and then stops or
stops beeping when it is manually stopped.
Procedure
Step 1 Select Fault > Set Alarm Box from the Main Menu.
The Warning dialog box is displayed.
Step 2 Click OK.
The Set Alarm Box dialog box is displayed.
Step 3 Click the Set Alarm Box tab. Check the Enable Alarm Box check box. Set the alarm box
parameters.
Step 4 Click Apply. The Prompt dialog box is displayed. Click OK.
Step 5 Restart the T2000 client. Repeat Step 1 and Step 2 to display the Set Alarm Box dialog box.
Step 6 Click the Set Alarm Operations tab.
Step 7 Optional: Turn off one or more indicators as needed.

Step 8 Optional: If you want to mute the sound of the alarm box, click Mute Alarm Sound. To
enable the alarm sound, click Mute Alarm Sound again.
----End
20.2.8 Setting Alarm Filter Status

After NEs report alarms to the T2000, the T2000 decides whether to display and save the
alarm information depending on the alarm lter status. When there are many NEs, you can
use this function to improve your efciency.
Prerequisite
Procedure
Step 2 Click the NM Alarm Filter tab.
Step 3 Select a value in the Filter Status column.
Step 4 Click Apply.
----End
20.2.9 Setting Alarm Dump Conditions

To avoid alarm data overow or damage, you need to dump the alarm data in time. You can
dump the alarm data manually if necessary, or set the alarm dump conditions in the T2000
to automatically dump the alarm data. There are two ways of automatic dump: overow
dump and periodic dump.
Prerequisite
Procedure
Step 1 Select System Administration > Database Management > Dump to File from the Main
Menu.
Step 2 Click the Dumping Conditions tab.
Step 3 In the left-hand Log Type list, select Alarm Event. In the right-hand pane, complete the
information under Dumping when Overow and Dumping in Schedule.

n For the dumping when overow method, enter a value in the Maximum Storage
Capacity, Dump Number and Capacity Alarm Threshold elds respectively.
n For the dumping in schedule method, set Dump Periodically or not to Yes. Set a value
in the Dump Interval and Time Limit elds respectively.
NOTE
n The storage capacity refers to the maximum number of records that can be kept in the T2000 database.
n The dump number refers to the number of performance records to be dumped at a time.
n Capacity Alarm Threshold refers to a number of records, when the records in the T2000 database
exceed this number, an alarm occurs and the T2000 executes dumping operation.
n Time Limit refers to a period, when the T2000 executes dumping operation, only those records
occurred earlier than this period will be dumped.
Step 4 Click OK.

----End
20.3 Setting NE Alarm Monitoring Strategy

To facilitate administration, you need to set the storage mode, reversion mode, and alarm
delay time for NE alarms.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an NE and select Alarm > NE Alarm Attribute from the Function
Tree.
Step 2 Set attributes for the NE.
Step 3 Click Apply to conrm the settings.
----End
20.4 Setting T2000 Alarm Monitoring Strategy

You can suppress a T2000 alarm of less importance or increase the severity level of a T2000
alarm, to improve alarm monitoring efciency.

Prerequisite
Procedure
Step 2 Click the NM Alarm Attributes Setting tab.
Step 3 Modify the T2000 alarm attributes, including Alarm Severity and Status. Click Apply.
NOTE
If an existing alarm is set to the Suppressed state, it clears automatically and changes to a history alarm.
----End
20.5 Setting Board/Port Alarm Monitoring Strategy

To improve alarm management efciency, network maintenance and monitoring engineers can
set the alarm monitoring strategy for every board or port, according to whether services are
turned up and whether services are important.
Context
You can congure the following alarm settings for boards or ports on the T2000:
20.5.1 Setting Alarm Severities and Automatic Reporting

To facilitate maintenance, you can adjust alarm severities and the automatic reporting status
for boards as needed. You can set alarms of less importance to lower severity level or to
the not reported state.
20.5.2 Setting Alarm Suppression
If you specify an alarm to be suppressed on an NE or a board, the alarm is not reported to the
NE and the T2000. You can suppress alarms of less importance as needed. By creating an
alarm template, you can set alarm suppression for multiple alarms at the same time.
20.5.3 Setting Bit Error Alarm Threshold
You can set alarm threshold for bit errors of boards. When the number of bit errors exceeds
the threshold, an alarm is raised.
20.5.4 Setting the AIS Insertion Switch
For services that require good quality of service (QoS), when the T2000 detects a specic
QoS-affecting event (for example, TIM_P), the T2000 inserts an alarm indication signal (AIS)
at the port immediately. In this way, the related protection mechanism is triggered and the
service at this port is switched to a protection path to guarantee the QoS.
20.5.5 Inserting UNEQ
To interrupt services, you can insert UNEQ in a path. None of the alarms of this path except
TA_LOS will be detected. You can decide whether to monitor the LOS alarms of this path.
20.5.6 Setting Alarm Reversion
The port where no service is turned up may report some alarms. For the LOS alarm, if you
set alarm reversion, the alarm status of this port differs from the actual situation. That is, the
NE is shown in the normal state even if there are alarms. In this way, the LOS alarms that
do not need immediate attention can be ltered. When the LOS alarm at the port is set to be
suppressed, it cannot be set to be reversed.
20.5.1 Setting Alarm Severities and Automatic Reporting

To facilitate maintenance, you can adjust alarm severities and the automatic reporting status
for boards as needed. You can set alarms of less importance to lower severity level or to
the not reported state.

Prerequisite
Context
If you disable auto reporting of a specied alarm for an NE or board, the NE does not report
this alarm automatically to the T2000 when the alarm is raised. But the T2000 can query this
alarm from the NE by synchronizing alarms.
Procedure
Step 1 In the NE Explorer, click a board and select Alarm > Set Alarm Severity and Auto
Reporting from the Function Tree.
Step 2 Double-click the Severity and Auto Reporting Status columns and select a value.
Step 3 Click Apply.
NOTE
If you have created an alarm template for the boards, click Use Template and select the desired template.
Step 4 Click OK.

----End
20.5.2 Setting Alarm Suppression

If you specify an alarm to be suppressed on an NE or a board, the alarm is not reported to the
NE and the T2000. You can suppress alarms of less importance as needed. By creating an
alarm template, you can set alarm suppression for multiple alarms at the same time.
Prerequisite
Procedure
Step 1 In the NE Explorer, click a board and select Alarm > Set Alarm Suppression from the
Function Tree.
Step 2 Set the alarm suppression status.
NOTE
Step 3 Click OK.

----End
20.5.3 Setting Bit Error Alarm Threshold

You can set alarm threshold for bit errors of boards. When the number of bit errors exceeds
the threshold, an alarm is raised.
Prerequisite

Procedure
Step 1 In the NE Explorer, click a board and select Alarm > QoS Alarm > Bit Error Alarm
Threshold from the Function Tree.
Step 2 Set a threshold respectively for B1, B2, B3, and so on.
NOTE
There are two thresholds for bit error: threshold-crossing and deterioration.
Step 3 Click Apply.

----End
20.5.4 Setting the AIS Insertion Switch

For services that require good quality of service (QoS), when the T2000 detects a specic
QoS-affecting event (for example, TIM_P), the T2000 inserts an alarm indication signal (AIS)
at the port immediately. In this way, the related protection mechanism is triggered and the
service at this port is switched to a protection path to guarantee the QoS.
Prerequisite
Procedure
Step 1 In the NE Explorer, select a board and select the Alarm > QoS Alarm > Set AIS Insertion
Switch from the Function Tree.
Step 2 Enable the AIS insertion switch.
Step 3 Click Apply.
----End
20.5.5 Inserting UNEQ

To interrupt services, you can insert UNEQ in a path. None of the alarms of this path except
TA_LOS will be detected. You can decide whether to monitor the LOS alarms of this path.
Prerequisite
Procedure
Step 1 In the NE Explorer, click a board and select Alarm > QoS Alarm > Set UNEQ Insertion
Switch from the Function Tree.
Step 2 Enable UNEQ insertion.
NOTE
There are two switches for UNEQ insertion: LOS and Path Not Used.
Step 3 Click Apply.

----End

20.5.6 Setting Alarm Reversion

The port where no service is turned up may report some alarms. For the LOS alarm, if you
set alarm reversion, the alarm status of this port differs from the actual situation. That is, the
NE is shown in the normal state even if there are alarms. In this way, the LOS alarms that
do not need immediate attention can be ltered. When the LOS alarm at the port is set to be
suppressed, it cannot be set to be reversed.
Prerequisite
Context
If the alarm reversion mode is set to Auto Revertive, the NE disables alarm reversion
automatically when the alarm is cleared, and the alarm status returns to normal. If the mode
is set to Manual Revertive, the alarm status returns to normal only when alarm reversion is
disabled manually.
Procedure
Step 1 In the NE Explorer, click an NE and select Alarm > Set NE Alarm Attribute from the
Function Tree.
Step 2 Set the Reversion Mode to Auto Revertive or Manual Revertive as required. Click Apply.
Step 3 In the NE Explorer, click a board and select Alarm > Alarm Reversion from the Function
Tree.
Step 4 Set the Reversion Status of the ports to Enable.
Step 5 Click Apply.
----End
20.6 Setting the Alarm Monitoring Strategy for SDH Trails

To focus on important alarms and services and improve alarm handling efciency, you can set
alarm monitoring strategy for SDH trails.
Context
You can set the following alarm attributes for SDH trails on the T2000:
20.6.1 Setting Alarm Suppression for SDH Trails

If you specify an alarm to be suppressed on a trail, the alarm is not reported to the NE and the
T2000. You can suppress alarms of less importance as needed. By creating an alarm template,
you can set alarm suppression for multiple alarms at the same time.
20.6.2 Setting Alarm Reversion for SDH Trails
The trail where no service is turned up may report some alarms. If you set alarm reversion,
the alarm status of this trail differs from the actual situation. That is, the NE is shown in the
normal state even if there are alarms. In this way, the alarms that do not need immediate
attention can be ltered.
20.6.1 Setting Alarm Suppression for SDH Trails

If you specify an alarm to be suppressed on a trail, the alarm is not reported to the NE and the
T2000. You can suppress alarms of less importance as needed. By creating an alarm template,
you can set alarm suppression for multiple alarms at the same time.

Prerequisites
n The trail must be activated.
Procedure
The Set Trail Browse Filter Conditions dialog box is displayed.
Step 2 Set lter criteria.
Step 3 Click Filter All.
Step 4 Select one or more trails. Click the Alarm button and select Alarm Suppression from the
drop-down list.
Step 5 In the Alarm Suppression dialog box, set the Suppression Status of alarms.
NOTE
Step 6 Click OK.

----End
20.6.2 Setting Alarm Reversion for SDH Trails

The trail where no service is turned up may report some alarms. If you set alarm reversion,
the alarm status of this trail differs from the actual situation. That is, the NE is shown in the
normal state even if there are alarms. In this way, the alarms that do not need immediate
attention can be ltered.
Prerequisites
n The trail must be activated.
Procedure
The Set Trail Browse Filter Conditions dialog box is displayed.
Step 2 Set lter criteria.
Step 4 Select one or more trails. Click the Alarm button and select Alarm Reversion from the
drop-down list.
Step 5 In the Alarm Reversion dialog box, set the reversion status.
Step 6 Click Apply.
----End
20.7 Setting Performance Monitoring Strategy

Network maintenance engineers can set performance monitoring and performance parameters
for the heavily concerned NEs and boards, to monitor the operation of important equipment
and services.

Context
You can congure the following performance monitoring settings on the T2000:
20.7.1 Creating Performance Threshold Templates

Setting individual performance thresholds for each NE is time-consuming. The T2000 provides
an easy way to set performance thresholds for multiple NEs―performance threshold template.
20.7.2 Setting Board Performance Threshold
The NE reports an event when it detects that a performance value exceeds the specied
threshold. You can set different performance thresholds for a board as needed. If you have
created a performance threshold template, you can set performance threshold for one or more
boards at the same time.
20.7.3 Dumping Performance Data Immediately
To avoid performance data overow or damage, you need to dump performance data in time.
You can dump the performance data manually.
20.7.4 Setting Performance Dump Conditions
To avoid performance data overow or damage, you need to dump performance data in
time. There are two methods for automatic dump: dumping when overow and dumping in
schedule. If Dumping when Overow is set, the system dumps performance data automatically
when the data exceeds the preset threshold. If Dumping in Schedule is set, the system dumps
performance data automatically at a scheduled time.
20.7.5 Starting or Stopping Performance Monitoring
Performance monitoring keeps a detailed record of the operation of an NE, helping the
maintenance engineer to monitor and analyze the operation status of the NE. Use this
procedure to start or stop performance monitoring.
20.7.6 Setting Performance Monitoring Objects
You can set the monitoring status and auto 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.
20.7.7 Setting ATM Board Performance Monitoring
Performance monitoring keeps a detailed record of the operation of ATM boards, helping the
maintenance engineer to monitor and analyze the operation of the boards. Use this procedure
to set performance monitoring for ATM boards.
20.7.8 Setting Ethernet Performance Monitoring
Performance monitoring keeps a detailed record of the performance of an Ethernet board,
helping the maintenance engineer to monitor and analyze the operational status of the board.
Use this procedure to enable performance monitoring on an Ethernet board.
20.7.9 Setting Trail Performance Monitoring Strategy
Performance monitoring keeps a detailed record of the performance of services over an SDH
trail, helping the maintenance engineer to monitor and analyze the status of services. Use this
procedure to enable performance monitoring on an SDH trail.
20.7.1 Creating Performance Threshold Templates

Setting individual performance thresholds for each NE is time-consuming. The T2000 provides
an easy way to set performance thresholds for multiple NEs―performance threshold template.
Prerequisite
Procedure
Step 1 Select Performance > Performance Threshold Template from the Main Menu.
Step 2 Select a template from the Template Name drop-down list.
Step 3 Modify the performance thresholds as required.
Step 4 Save the template, you can choose one of the following methods:

n Click Save to save the modication.

n To save as a new template, click Save As and enter a template name.
Step 5 Click OK.
----End
20.7.2 Setting Board Performance Threshold

The NE reports an event when it detects that a performance value exceeds the specied
threshold. You can set different performance thresholds for a board as needed. If you have
created a performance threshold template, you can set performance threshold for one or more
boards at the same time.
Prerequisite
Procedure
Step 1 In the NE Explorer, click a board and select Performance > Performance Threshold from
the Function Tree.
Step 2 Set performance thresholds as you need.
NOTE
If you have created a performance threshold template for the boards, click Use Template and select the
desired template. Click Open.
Step 3 Click Apply.

----End
20.7.3 Dumping Performance Data Immediately

You can dump the performance data manually.
Prerequisite
Procedure
Step 1 Select System Administration > Database Management > Dump from the Main Menu.
Step 2 Click the Instant Dump tab.
Step 3 Under Instant Dump Conditions, set a value in the Record Type and Deadline elds
respectively.
Step 4 Click OK.
Step 5 Click Dump to dump the performance data immediately.
----End
20.7.4 Setting Performance Dump Conditions

There are two methods for automatic dump: dumping when overow and dumping in schedule.

If Dumping when Overow is set, the system dumps performance data automatically when
the data exceeds the preset threshold. If Dumping in Schedule is set, the system dumps
performance data automatically at a scheduled time.
Prerequisite
Procedure
Step 1 Select System Administration > Database Management > Dump to Flie from the Main
Menu.
Step 2 Click the Dumping Conditions tab.
Step 3 In the left-hand Log Type list, select Alarm Event. Complete the information under Dumping
when Overow, Dumping in Schedule and Dump To (Path).
n In the Dumping when Overow area, enter a value in the Maximum Storage Capacity,
Dump Number and Capacity Alarm Threshold elds respectively.
n In the Dumping in Schedule area, set the Dump Periodically or not option to Yes. Set a
value in the Dump Interval and Time Limit elds respectively.
NOTE
n The Maximum Storage Capacity refers to the maximum number of records that can be stored in
the T2000 database.
n The Number of Dumped Records refers to the number of performance records to be dumped
at a time.
n The Capacity Alarm Threshold refers to a certain number of records. When the records in the
T2000 database exceed this number, an alarm occurs and the T2000 executes the dumping operation.
n The Time Limit refers to a time period. When the T2000 executes the dumping operation, only those
records occurring earlier than this period will be dumped.
n There are several types of performance that can be set: 15-minute performance, 24-hour performance,
performance value threshold-crossing and so on.
Step 4 Click OK.

----End

20.7.5 Starting or Stopping Performance Monitoring

Performance monitoring keeps a detailed record of the operation of an NE, helping the
maintenance engineer to monitor and analyze the operation status of the NE. Use this
procedure to start or stop performance monitoring.
Prerequisite
Procedure
Step 1 Select Performance > NE Performance Monitor Time from the Main Menu.
Step 2 Select NEs from the NE list. Click the double-right-arrow button.
Step 3 Select one or more NEs, and set 15-minute and 24-hour performance monitor parameters as
you need.
Step 4 Click Apply.
----End
20.7.6 Setting Performance Monitoring Objects

You can set the monitoring status and auto 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, click a board and select Performance > Performance Monitor Status
Step 2 Select a condition from the Monitoring Object Filter Condition drop-down list.
Step 3 Set the Monitor Status, 15-Minute Auto-Report and 24-Hour Auto-Report parameters.
Step 4 Click Apply.
----End
20.7.7 Setting ATM Board Performance Monitoring

Performance monitoring keeps a detailed record of the operation of ATM boards, helping the
maintenance engineer to monitor and analyze the operation of the boards. Use this procedure
to set performance monitoring for ATM boards.
Prerequisite
Procedure
Step 1 In the NE Explorer, select an ATM board and select Performance > Set ATM Performance
Event Monitor Status from the Function Tree.

Step 2 Select a value in the 15-Minute Monitoring, 24-Hour Monitoring and Custom Period
Monitor elds respectively.
Step 3 Select a value in the 15-Minute Auto-Report, 24-Hour Auto-Report and Custom Period
Auto-Report elds respectively.
Step 4 Click Apply.
----End
20.7.8 Setting Ethernet Performance Monitoring

Performance monitoring keeps a detailed record of the performance of an Ethernet board,
helping the maintenance engineer to monitor and analyze the operational status of the board.
Use this procedure to enable performance monitoring on an Ethernet board.
Prerequisite
Procedure
Step 1 In the NE Explorer, click an Ethernet board and select Performance > Performance Monitor
Status from the Function Tree.
Step 2 Set the Monitor Status,15-Minute Auto-Report and 24-Hour Auto-Report parameters.
Step 3 Click Apply.
----End
20.7.9 Setting Trail Performance Monitoring Strategy

Performance monitoring keeps a detailed record of the performance of services over an SDH
trail, helping the maintenance engineer to monitor and analyze the status of services. Use this
procedure to enable performance monitoring on an SDH trail.
Prerequisite
Procedure
Step 2 In the Set Trail Browse Filter Conditions dialog box, set the lter criteria.
Step 4 Select one or more trails. Click the Performance button and select Performance Parameter
from the drop-down list.
Step 5 In the Performance Parameter dialog box, select an object, and set monitoring status and
auto reporting status.
Step 6 Click Apply.
----End
20.8 Viewing Alarms

To have an idea of the network status, network maintenance personnel can view alarms.

Context
The following tasks are described:
20.8.1 Synchronizing Networkwide Current Alarms

The alarm synchronization operation checks the alarms in the T2000 database against the
alarms in the NE database. If the alarms are inconsistent, the alarms in the NE database are
uploaded to the T2000 database. Existing alarms in the T2000 database are overwritten during
this process. When services are interrupted and then recovered, or when you want to know the
operational status of the whole network, you need to synchronize networkwide alarms.
20.8.2 Synchronizing the Current Alarms for the Specied NE
this process. When services are interrupted and then recovered, or when there is any operation
that may cause alarm inconsistency between the T2000 and the NE, you can synchronize the
current alarms for the specied NE.
20.8.3 Synchronizing Current T2000 Alarms
To synchronize T2000 alarms is to update the T2000 alarm database. This function reports
all uncleared T2000 alarms again to the alarm database, and clears the T2000 alarms that are
actually cleared but not cleared in the alarm database. As a result, the T2000 alarms in the
alarm database conform to the current T2000 status.
20.8.4 Viewing Networkwide Current Alarms of a Selected Severity Level
To query the current operational status of the network, you can view networkwide current
alarms. In network maintenance, you need to update alarm information for troubleshooting.
When viewing networkwide current alarms for a specic severity level, you can synchronize,
refresh, check and acknowledge alarms, and save or print the current alarm information.
20.8.5 Viewing Networkwide Current Alarms for All Severities
alarms for all severity levels. In network maintenance, you need to update alarm information
and perform appropriate alarm operations. When viewing networkwide current alarms for all
severity levels, you can synchronize, refresh, check and acknowledge alarms, and save or
print the current alarm information.
20.8.6 Viewing Current Alarms for an NE
When querying NE status and performing maintenance operations, you need to view current
NE alarms. Use this procedure to view current alarms for an NE.
20.8.7 Viewing Current T2000 Alarms
By viewing the current alarms on the T2000, you can query the information such as the
current running status of the T2000 and whether the communcation status between the T2000
and NEs are normal.
20.8.8 Viewing Current Alarms of an SDH Trail
To query the status of services over the current trail, you can view current alarms of an SDH
trail. In network maintenance, you need to update alarm information for troubleshooting.
20.8.9 Viewing Current Alarms of a Trunk Link
To query the status of services over the current trunk link, you can view current alarms of a
trunk link. In network maintenance, you need to update alarm information for troubleshooting.
20.8.10 Viewing Current Alarms of an Ethernet Trail
To query the status of Ethernet services over the current Ethernet trail, you can view current
alarms of an Ethernet trail. In network maintenance, you need to update alarm information
for troubleshooting.
20.8.11 Acknowledging Alarms
This functionality changes all cleared alarms to history alarms, helping network maintenance
personnel to focus on current alarms only. If acknowledged current alarms are cleared, they
change to history alarms automatically.
20.8.12 Checking Alarms
To check whether a current alarm on the T2000 is cleared on the NE, you can perform this
operation. If the alarm on the NE is cleared and acknowledged , it changes to a history alarm.

20.8.13 Viewing History Alarms

In routine maintenance, you can query the history status of the network by viewing the
history alarms.
20.8.14 Viewing Abnormal Events
In routine maintenance, you need to view abnormal events to check the current status of the
network.
20.8.15 Viewing Alarm Statistics and Outputting a Report
To have an idea of the status of the entire network within a period of time, you can browse the
number of alarms within the specic period of time. You can query alarms for one or more
NEs as needed when you are maintaining the current network.
20.8.16 Turning Off Alarm Indicators in the Alarm Box
To disable the visual and audible alarm notication for a specic alarm severity, you can turn
off alarm indicators in the alarm box. So, network maintenance personnel focus on important
alarms only and increase maintenance efciency.
20.8.17 Clearing Visual and Audible Alarm on a Cabinet
You can clear the visual and audible alarm notication on the T2000 when an alarm indicator
on a cabinet ashes. After the alarm notication is cleared, if there is a new alarm reported,
the alarm indicator on the cabinet is still able to ash and the T2000 provides a visual alarm
notication.
20.8.1 Synchronizing Networkwide Current Alarms

this process. When services are interrupted and then recovered, or when you want to know the
operational status of the whole network, you need to synchronize networkwide alarms.
Prerequisite
Procedure
Step 1 Select Fault > Synchronize Networkwide Alarms from the Main Menu.
A progress bar is displayed. After the operation is complete, a prompt appears telling you
Step 2 Click Close.
----End
20.8.2 Synchronizing the Current Alarms for the Specied NE

this process. When services are interrupted and then recovered, or when there is any operation
that may cause alarm inconsistency between the T2000 and the NE, you can synchronize the
current alarms for the specied NE.
Prerequisite
Procedure
Step 1 Select an NE on the Main Topology.

NOTE
If you select topology subnet form the Main Topology, it indicates all NEs contained in that topology
subnet are selected.
Step 2 Right-click the selected NE icon and select Synchronize Current Alarms from the shortcut
menu.
The progress bar is displayed. After the operation is complete, a prompt appears telling you
Step 3 Click Close.
----End
20.8.3 Synchronizing Current T2000 Alarms

To synchronize T2000 alarms is to update the T2000 alarm database. This function reports
all uncleared T2000 alarms again to the alarm database, and clears the T2000 alarms that are
actually cleared but not cleared in the alarm database. As a result, the T2000 alarms in the
alarm database conform to the current T2000 status.
Prerequisite
Procedure
Step 1 Right-click the local NM icon on the Main Topology and select Synchronize Current Alarms
A process bar displays.
Step 2 After the operation is complete, a prompt appears telling you that the operation was successful.
Click Close.
NOTE
To view whether the alarms are synchronized, right-click the local NM icon on the Main Topology and
select Browse Current Alarms from the shortcut menu.
----End
20.8.4 Viewing Networkwide Current Alarms of a Selected

Severity Level
alarms. In network maintenance, you need to update alarm information for troubleshooting.
When viewing networkwide current alarms for a specic severity level, you can synchronize,
refresh, check and acknowledge alarms, and save or print the current alarm information.
Prerequisite
You must be an NM user with "NM supervisor" authority or higher.
Procedure
Step 1 Click one of the three alarm shortcut icons for critical (red), major (orange) or minor (yellow)
alarm. All the current alarms of the selected severity level are displayed.
Step 2 If you want to display the latest reported alarms, check the Auto Refresh check box.

NOTE
If you check this check box, the system performs the same function as you press the Refresh and
Synchronize buttons, and thus the two buttons are grayed out.
Step 3 If you want to check the selected alarm(s), select one or more alarms and click Check.
NOTE
The check feature compares one or more uncleared alarm in the T2000 with those in the NE. If they are
included in the current alarms in the NE, they are kept in the T2000. If not, they are cleared in the T2000.
Step 4 Select an alarm, the alarm details and alarm causes are shown in the panes below.
Step 5 Select one or more alarms and click Acknowledge . The corresponding parameter values are
shown in the Ack Time and Ack User elds.
NOTE
Acknowledged and cleared alarms change to history alarms automatically.
Step 6 Click Save As to save the results to the le in the specied destination on the client computer.
----End
20.8.5 Viewing Networkwide Current Alarms for All Severities

alarms for all severity levels. In network maintenance, you need to update alarm information
and perform appropriate alarm operations. When viewing networkwide current alarms for all
severity levels, you can synchronize, refresh, check and acknowledge alarms, and save or
print the current alarm information.
Prerequisite
Procedure
Step 1 Select Fault > Browse Current Alarm from the Main Menu.
Step 2 Select one or more NEs in the left pane, and click the double-right-arrow button. Then the
current alarms of selected NEs for all severities are displayed.
Step 3 If you want to display the latest reported alarms, select the Auto Refresh check box.
NOTE
If you check this check box, the system performs the same function as you press the Refresh and
Synchronize buttons, and thus the Refresh button is grayed out.
Step 4 If you want to query NE alarms by certain criteria, click Filter, and then the Filter dialog
box is displayed.
NOTE
If you check the Auto Refresh check box, Cleared Time and Alarm Status are grayed out in the
Filtering dialog box.
Step 5 Select display conditions as you need and then click Filter. The alarm information that meets
the conditions is displayed.
NOTE
The check feature compares one or more uncleared alarms in the T2000 with those in the NE. If they are
included in the current alarms in the NE, they are kept in the T2000. If not, they are cleared in the T2000.

Step 7 Select an alarm, and the alarm details and alarm causes are shown in the panes below.
Step 8 Select one or more alarms and click Acknowledge. The corresponding parameter values are
displayed in the Ack Time and Ack User elds.
NOTE
Acknowledged and cleared alarms change to history alarms automatically.
Step 9 Click Save to File to save the result to the le in the specied destination on the client
computer.
----End
20.8.6 Viewing Current Alarms for an NE

When querying NE status and performing maintenance operations, you need to view current
NE alarms. Use this procedure to view current alarms for an NE.
Prerequisite
Procedure
Step 1 Right-click an NE icon on the Main Topology and select Browse Current Alarms.
NOTE
n If you check this check box, the system performs the same functions as you press the Refresh and
Synchronize buttons, and thus the Refresh button is grayed out.
n The synchronize feature keeps the current alarms in the T2000 synchronized with the NE. Then the
T2000 has the same information of current alarms with the NE.
NOTE
The check feature compares one or more uncleared alarms in the T2000 with those in the NE. If the
alarms are included in the current alarms in the NE, they are kept in the T2000. If not, they are cleared in
the T2000.
Step 4 Select an alarm, and the alarm details and alarm causes are shown in the panes below.
NOTE
Conrmed and cleared alarms change to history alarms automatically.
Step 6 Click Save to File to

save the results to the le in the specied destination on the client computer.
----End
20.8.7 Viewing Current T2000 Alarms

By viewing the current alarms on the T2000, you can query the information such as the
current running status of the T2000 and whether the communcation status between the T2000
and NEs are normal.

Prerequisite
Procedure
Step 2 Select local NM in the left pane, and click the double-right-arrow button.
The current alarms of local NM for all severities are displayed.
NOTE
If you check this check box, the system performs the same functions as you press the Refresh and
Synchronize buttons. Thus the Refresh button is grayed out.
To synchronize the T2000 alarms is to update the T2000 alarm database, report the uncleared alarms to
the alarm database and end those that are actually cleared but uncleared in the alarm database.
Step 4 If you want to query T2000 alarms by certain criteria, click Filter, and the Filter dialog
box is displayed.
NOTE
If Auto Refresh is checked, Cleared Time and Alarm Status are grayed out in the Filtering dialog box.
Step 5 Set alarm display conditions and click Filter.

The qualied alarm information is shown in the list.
NOTE
The check feature acknowledges one or more uncleared T2000 alarms, and ends those that are actually
cleared but remains uncleared in the alarm database.
NOTE
Conrmed and cleared alarms change to history alarms automatically.
computer.
----End
20.8.8 Viewing Current Alarms of an SDH Trail

To query the status of services over the current trail, you can view current alarms of an SDH
trail. In network maintenance, you need to update alarm information for troubleshooting.
Prerequisite
Procedure
Step 2 In the Set Trail Browse Filter Conditions dialog box, select or enter parameters and set lter
criteria. Click Filter All.
Step 3 Select one or more trails. Click the Alarm button and select Current Alarm from the
drop-down list.

The current alarms of all severity levels are shown in the list.
Step 4 If you want to refresh alarms displayed, click Refresh.
NOTE
The refresh feature queries the alarms in the T2000 and the synchronize feature queries the alarms
in the NE.
Step 5 Select an alarm entry, the alarm details and alarm causes are shown in the panes below. Click
OK.
NOTE
When the alarms are cleared, they automatically change to history alarms.
computer.
Step 7 Optional: If you want to display the latest reported alarms, check the Auto Refresh check box.
----End
20.8.9 Viewing Current Alarms of a Trunk Link

To query the status of services over the current trunk link, you can view current alarms of a
trunk link. In network maintenance, you need to update alarm information for troubleshooting.
Prerequisites
n The trunk link must be created.
Procedure
Step 1 Select Trail > Trunk Link Management from the Main Menu.
Step 2 Select one or more trails. Click the Alarm button and select Current Alarm from the
drop-down list.
Step 4 Select an alarm entry, and the alarm details and alarm causes are shown in the panes below.
Step 5 Click OK.
NOTE
Step 6 Click Save to File to save the results to the le in the specied destination on the client
computer.
----End
20.8.10 Viewing Current Alarms of an Ethernet Trail

To query the status of Ethernet services over the current Ethernet trail, you can view current
alarms of an Ethernet trail. In network maintenance, you need to update alarm information
for troubleshooting.
Prerequisites
n The Ethernet trail must be created.

Procedure
Step 2 Click the Alarm button and select Current Alarm from the drop-down list.
The current alarms for all severities are displayed.
Step 4 Select an alarm entry, and the alarm details and alarm causes are shown in the panes below.
Step 5 Click Acknowledge.
NOTE
----End
20.8.11 Acknowledging Alarms

This functionality changes all cleared alarms to history alarms, helping network maintenance
personnel to focus on current alarms only. If acknowledged current alarms are cleared, they
change to history alarms automatically.
Prerequisite
Procedure
Step 1 On the Main Topology, right-click the NE or subnet for which you want to acknowledge
alarms, and select Acknowledge Alarms.
A progress bar displays. After the operation is complete, a prompt appears telling you that the
operation was successful.
Step 2 Click Close.
----End
20.8.12 Checking Alarms

To check whether a current alarm on the T2000 is cleared on the NE, you can perform this
operation. If the alarm on the NE is cleared and acknowledged , it changes to a history alarm.
Prerequisite
Context
Checking an alarm for an NE takes a longer time than acknowledging the alarm. It is
recommended not to check alarms for several NEs at the same time.
Procedure
Step 1 On the Main Topology, right-click the NE for which you want to check alarms, and select
Browse Current Alarms.
Step 2 Select one or more alarms and click Check.
A progress bar is displayed. After the operation is complete, a prompt appears telling you

Step 3 Click Close.

----End
20.8.13 Viewing History Alarms

In routine maintenance, you can query the history status of the network by viewing the
history alarms.
Prerequisite
You must be an NM user with "NM supervisor" authority or higher.
Procedure
Step 1 Select Fault > Browse History Alarms from the Main Menu.
Step 2 Select one or more NEs from the left-hand pane and click double-right-arrow button (red).
The history alarms of selected NEs for all severities are displayed.
Step 3 If you want to query NE alarms by certain criteria, click Filter, and then the Filter dialog
box is displayed.
Step 4 Select display conditions as you need and then click Filter.
The alarm information that meets the conditions is displayed.
Step 5 Select an alarm, the alarm details and alarm causes are shown in the panes below.
Step 6 Click Save As to save the results to the le in the specied destination on the client computer.
----End
20.8.14 Viewing Abnormal Events

In routine maintenance, you need to view abnormal events to check the current status of the
network.
Prerequisite
Procedure
Step 1 Select Fault > Browse Abnormal Events from the Main Menu.
Step 2 Select one or more NEs in the left-hand pane, and click the double-right-arrow button.
Step 3 Click Filter and the Filter dialog box is displayed.
Step 4 Click in the Rising Time area to specify the time range. Select the event names in the
lower list. Click OK.
Step 5 Click Save to File to save the results to le in the specied directory on the client computer.
----End
20.8.15 Viewing Alarm Statistics and Outputting a Report

To have an idea of the status of the entire network within a period of time, you can browse the
number of alarms within the specic period of time. You can query alarms for one or more
NEs as needed when you are maintaining the current network.

Prerequisite
Procedure
Step 1 Select Fault > Current Alarm Statistics from the Main Menu.
Step 2 Select one or more NEs from left Object Tree and click the double-right-arrow button (red).
Step 3 Optional: At the bottom of the user interface, click in the Rising Time area to specify the
time range during which alarms are raised.
Step 4 Click Refresh to query the result.
Step 5 Click Save to File.
Step 6 Select the path to save the le and the le name. Click OK.
----End
20.8.16 Turning Off Alarm Indicators in the Alarm Box

To disable the visual and audible alarm notication for a specic alarm severity, you can turn
off alarm indicators in the alarm box. So, network maintenance personnel focus on important
alarms only and increase maintenance efciency.
Prerequisites
n Alarm box must be enabled in the Alarm Box Settings window.
Procedure
Step 1 Select Fault > Set Alarm Box from the Main Menu. Click the Alarm Box Operations tab.
Step 2 Select an alarm severity for which you want to turn off the indicator.
Step 3 Click Apply.
A dialog box displays and prompts you to restart the client.
Step 4 Click OK.
Step 5 If you want to stop the alarm sound, click Mute Alarm Sound.
Step 6 Exit and restart the client, and the selected alarm indicator and alarm sound are already stopped.
----End
20.8.17 Clearing Visual and Audible Alarm on a Cabinet

You can clear the visual and audible alarm notication on the T2000 when an alarm indicator
on a cabinet ashes. After the alarm notication is cleared, if there is a new alarm reported,
the alarm indicator on the cabinet is still able to ash and the T2000 provides a visual alarm
notication.
Prerequisite

Context
NOTE
This operation clears all alarm records on the T2000 for the selected NE. If alarms are not cleared,
they are reported again.
Procedure
Step 1 Right-click an NE icon on the Main Topology and select Browse Current Alarm from the
shortcut menu. A progress bar is displayed.
After the operation is complete, a prompt appears telling you that the operation was successful.
Step 2 Click Close.
----End
20.9 Viewing Performance Data

To know whether there are potentially service-affecting problems in the network that will not
generate alarms, you can view performance data and take necessary actions to avoid faults.
Context
You can set the following performance monitoring parameters on the T2000:
18.5.120.9.1 Viewing Current Performance Data of an ASON Trail

The current performance data include 15-minute current performance and 24-hour current
performance. To know whether services are normal within the current period of 15 minutes
and 24 hours, you can view the current performance data.
18.5.220.9.2 Viewing History Performance Data of an ASON Trail
The history performance data has 15-minute and 24-hour intervals. To know the operational
status of services within the period of last 15 minutes and last 24 hours, you can view the
history performance data.
20.9.3 Viewing UAT Records
You can view records of unavailable time (UAT) to know equipment performance. You can
perform the following subfunctions: view cleared UAT events, view uncleared UAT events,
set timely prompt of new UAT events, query UAT events from an NE and query UAT events
from the T2000.
20.9.4 Viewing Performance Threshold Crossings
Threshold crossings have 15-minute and 24-hour intervals. To know what services are
abnormal and handle them timely, you can view threshold crossings.
20.9.5 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.
20.9.6 Forecasting Medium- and Long-Term Performance
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 will fail or what
its performance value is at a given time. In this way, you can decide when to replace the
optical component.
20.9.7 Viewing Current Performance Data of an Ethernet Port
You can view current performance statistics of an Ethernet port.
20.9.8 Viewing History Performance Data of an Ethernet Port
To know the operational status of Ethernet services over an Ethernet port within a dened
period, you can view the history performance data of an Ethernet port.
20.9.9 Viewing History Group Performance of an Ethernet Port
You can view the history group performance data of an Ethernet port. The history group
performance data stores the statistics of Ethernet performance data within a period.

20.9.10 Setting History Control Group of an Ethernet Port

The history control group can be used to control the mode of getting Ethernet port history
performance data.
20.9.11 Setting Alarm Group of an Ethernet Port
You can determine whether an Ethernet peformance event is reported as an alarm by setting the
threshold for the alarm group of the Ethernet port.
20.9.12 Viewing Statistic Group Performance of an Ethernet Port
To know the real-time statistics of an Ethernet port, you can view the statistic group
performance data of an Ethernet port.
20.9.13 Viewing Current Performance Data of an ATM Port
To know the operational status of ATM services over an ATM port, you can view the current
performance data of the port.
20.9.14 Viewing History Performance Data of an ATM Port
To know the operational status of ATM services over an ATM port within a dened period, you
can view the history performance data of the port.
20.9.15 Viewing Current Performance Data of an SDH Trail
To know whether services over an SDH trail are normal within the current period of 15 minutes
and 24 hours, you can view the current performance data of the trail.
20.9.16 Viewing Current Performance Data of an Ethernet Trail
Maintenance engineers can view the current performance data of a node, as well as all nodes
on an Ethernet trail. In addition, the T2000 veries whether to call the RMON performance or
the IP real-time performance window, according to the Ethernet board type used by the trail.
20.9.1 Viewing Current Performance Data

The current performance data include 15-minute current performance and 24-hour current
performance. To know whether services are normal within the current period of 15 minutes
and 24 hours, you can view the current performance data.
Prerequisites
n The service must be congured.
n The performance monitoring parameters must be set.
Procedure
Step 1 Select Performance > Browse SDH Performance from the Main Menu. Click the Current
Performance Data tab.
Step 2 Select one or more boards/ports in the left-hand pane, and click the double-right-arrow button
(red).
Step 3 Complete the following information: Monitored Object Filter Condition, Monitor Period
and Performance Event Type.
Step 4 Optional: In the Display Options group box, you can check Current Value or
Maximum/Minimum Value.
Step 5 Click Query to query the data from the NE.
----End
20.9.2 Viewing History Performance Data

The history performance data has 15-minute and 24-hour intervals. To know the operational
status of services within the period of last 15 minutes and last 24 hours, you can view the
history performance data.

Prerequisites
Procedure
Step 1 Select Performance > Browse SDH Performance from the Main Menu. Click the History
Performance Data tab.
Step 2 Select one or more ports in the lower-left pane, and click the double-right-arrow button (red).
Step 3 Complete the information: Monitored Object Filter Condition, Monitor Period, Period
ends at and Data Source.
Step 4 Click Query and the information is shown in the lower pane.
Step 5 If you want to view the 24-hour history performance data, click the 24-Hour radio button and
repeat Steps 2 through 4.
----End
20.9.3 Viewing UAT Records

You can view records of unavailable time (UAT) to know equipment performance. You can
perform the following subfunctions: view cleared UAT events, view uncleared UAT events,
set timely prompt of new UAT events, query UAT events from an NE and query UAT events
from the T2000.
Prerequisites
Procedure
Step 1 Select Performance > Browse SDH Performance from the Main Menu. Click the UAT tab.
Step 2 In the left pane, select one or more boards or ports. Click the double-right-arrow button (red).
Step 3 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 varies with your selection.
Step 4 Click Query to query data from the NE or the T2000.
----End
20.9.4 Viewing Performance Threshold Crossings

Threshold crossings have 15-minute and 24-hour intervals. To know what services are
abnormal and handle them timely, you can view threshold crossings.
Prerequisites

Procedure
Step 1 Select Performance > Browse SDH Performance from the Main Menu. Click the
Performance Threshold-crossing Record tab.
Step 3 Complete the information: Monitored Object Filter Condition, Monitor Period, and start
time.
Step 4 Check the Prompt on New Threshold-Crossing check box.
Step 5 Set Performance Event Type and Display Options. The information displayed varies with
your selection.
Step 6 Click Query to query the data from the T2000.
----End
20.9.5 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 Select Performance > History Performance Data Analysis from the Main Menu.
Step 2 Select one or more boards/ports in the left-hand pane, and click the double-right-arrow button
(red).
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.
----End
20.9.6 Forecasting Medium- and Long-Term Performance

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 will fail or what
its performance value is at a given time. In this way, you can decide when to replace the
optical component.
Prerequisites
n At least ve days of performance data must be collected.
n The board must support the query of performance data.
Procedure
Step 1 Choose Performance > Medium-Term and Long-Term Forecast from the Main Menu.
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 output.
----End
20.9.7 Viewing Current Performance Data of an Ethernet Port

You can view current performance statistics of an Ethernet port.
Prerequisites
n The Ethernet service must be congured.
n Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must
be congured.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and select 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 and Display Number of Data Column drop-down
lists respectively.
Step 4 Click Begin.
----End
20.9.8 Viewing History Performance Data of an Ethernet Port

To know the operational status of Ethernet services over an Ethernet port within a dened
period, you can view the history performance data of an Ethernet port.
Prerequisites
n Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must
be congured.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and select 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
20.9.9 Viewing History Group Performance of an Ethernet Port

You can view the history group performance data of an Ethernet port. The history group
performance data stores the statistics of Ethernet performance data within a period.

Prerequisites
Procedure
Step 1 In the NE Explorer, select an Ethernet board and select Performance > RMON Performance
Step 2 Click the History Group tab.
Step 3 Complete the information: Select port, History Table Type, Query Conditions and Display
Mode.
Step 4 Click Query, and the information is shown in the lower pane.
----End
20.9.10 Setting History Control Group of an Ethernet Port

The history control group can be used to control the mode of getting Ethernet port history
performance data.
Prerequisites
Procedure
Step 2 Click the History Control Group tab.
Step 3 Select a History Table Type.
----End
20.9.11 Setting Alarm Group of an Ethernet Port

You can determine whether an Ethernet peformance event is reported as an alarm by setting the
threshold for the alarm group of the Ethernet port.
Prerequisites
Procedure
Step 2 Click the Alarm Group tab.

----End
20.9.12 Viewing Statistic Group Performance of an Ethernet Port

To know the real-time statistics of an Ethernet port, you can view the statistic group
performance data of an Ethernet port.
Prerequisites
Procedure
Step 2 Click the Statistic Group tab.
Step 3 Select a port.
Step 4 Select the Ethernet RMON par ameters. Set Query Conditions and Display Mode.
Step 5 Click Begin.
----End
20.9.13 Viewing Current Performance Data of an ATM Port

To know the operational status of ATM services over an ATM port, you can view the current
performance data of the port.
Prerequisites
n The ATM service must be congured.
Procedure
Step 1 In the NE Explorer, select an ATM board and select 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 and Display
Number of Data Columns.
Step 4 Click Begin.
----End
20.9.14 Viewing History Performance Data of an ATM Port

To know the operational status of ATM services over an ATM port within a dened period, you
can view the history performance data of the port.

Prerequisites
n The ATM service must be congured.
Procedure
Step 1 In the NE Explorer, select an ATM board and select 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 lower pane.
----End
20.9.15 Viewing Current Performance Data of an SDH Trail

To know whether services over an SDH trail are normal within the current period of 15 minutes
and 24 hours, you can view the current performance data of the trail.
Prerequisites
n The SDH trail must be created.
Procedure
Step 2 In the Set Trail Browse Filter Conditions dialog box, select or enter parameters and set lter
criteria. Click Filter All.
Step 3 Select one or more trails. Click the Performance button and select Query Performance
from the drop-down list. Click the 15-Minute Current Performance or 24-Hour Current
Performance tab.
Step 4 Click Query to refresh the information.
Step 5 Optional: Click Save to File to save the result to the le in the specied destination on the
client computer.
----End
20.9.16 Viewing Current Performance Data of an Ethernet Trail

Maintenance engineers can view the current performance data of a node, as well as all nodes
on an Ethernet trail. In addition, the T2000 veries whether to call the RMON performance or
the IP real-time performance window, according to the Ethernet board type used by the trail.
Prerequisites
n The Ethernet trail must be created.
Procedure

Step 2 If you want to view the current performance data of all nodes on the trail, select one or more
trails and click Performance.
Step 3 If you want to view the current performance data of a node on the trail, select a trail and click
the Node tab. Right-click a desired node and select Performance from the shortcut menu.
Step 4 Select a performance type.
Step 5 Click Query to refresh the display.
----End
20.10 Resetting Performance Registers

Context
Depending on the performance register type, you can reset the following performance registers:
20.10.1 Resetting Board Performance Registers

new performance monitoring period. An NE performance register stores performance data
including optical power and bit errors.
20.10.2 Resetting ATM Performance Registers
20.10.3 Resetting Ethernet Performance Registers
20.10.1 Resetting Board Performance Registers

new performance monitoring period. An NE performance register stores performance data
including optical power and bit errors.
Prerequisite
Procedure
Step 1 In the NE Explorer, select a board and select Performance > Reset Board Performance
Register from the Function Tree.
Step 2 Select the registers you want to reset and click Reset.
Step 3 Click Yes in the conrmation dialog box.
Step 4 Click Close in the result dialog box.
----End
20.10.2 Resetting ATM Performance Registers


Prerequisite
Procedure
Step 1 In the NE Explorer, select an ATM board and select Performance > Reset ATM Performance
Step 2 Select the ATM ports and registers that you want to reset and click Reset.
----End
20.10.3 Resetting Ethernet Performance Registers

Prerequisite
Procedure
Step 1 In the NE Explorer, select an Ethernet board and select Performance > Reset IP Performance
Step 2 Select the Ethernet ports and registers you want to reset and click Reset.
----End
20.11 Checking Protection Switching Status

You can congure protection subnets, board protection and other protection modes for the
OptiX equipment. To detect the fault that makes the protection facility unavailable, you need
to check the protection switching status for protection subnets and boards regularly.
Context
20.11.1 Checking Networkwide Multiplex Section Parameters

In the same MSP subnet, every NE should have the same multiplex section parameter settings.
After conguring or adjusting an MSP subnet, you need to check networkwide multiplex
section parameters.
20.11.2 Checking TPS Switching status
If tributary protection switching (TPS) takes place, it indicates the protected tributary board
failed. Network maintenance engineers can check TPS switching status to detect faults that
make the protection facility unavailable.
20.11.3 Checking 1+1 Board Switching Status
If board 1+1 protection switching is trigger, it indicates the protected board failed. Network
maintenance engineers can check 1+1 board switching status, to detect faults that make the
protection facility unavailable.

20.11.4 Checking MSP Ring Switching Status

To detect faults on NEs or bers in an MSP ring, maintenance engineers can check the
switching status of the MSP ring. Then, engineers can locate the point where the fault is
generated according to the switching status of every NE in the protection subnet.
20.11.5 Checking Linear MSP Switching Status
To detect faults on NEs or bers in a linear MSP protection subnet, maintenance engineers can
check the switching status of linear MSP. Then, engineers can locate the point where the fault
is generated according to the switching status of every NE in the protection subnet.
20.11.6 Exercising MSP Protection Switching
Maintenance engineers can exercise switching for MSP rings or chains to ensure the command
can be issued correctly. So, services are not interrupted because the protection facility is
unavailable in the event of failure.
20.11.7 Checking SNCP or PP Switching Status
To detect faults on NEs or bers in an SNCP or PP protection subnet, maintenance engineers
can check the switching status of SNCP or PP protection. Then, engineers can locate the point
where the fault is generated according to the switching status of every NE in the protection
subnet.
20.11.8 Checking GNE Switching Status
If an NE has a standby GNE, when the active GNE fails, the NE communicates with the T2000
through the standby GNE automatically. To detect GNE communication failure timely, you
can check GNE switching status, to ensure that NEs communicate with the T2000 through
the GNE correctly.
20.11.9 Checking Clock Switching Status
Clock failure may interrupt services. To detect clock source failure timely, you can check
clock switching status.
20.11.10 Checking Switching Status of an SNCP Trail
To detect faults on NEs or bers that an SNCP trail passes through, maintenance engineers can
check the switching status of the trail. Then, engineers can locate the point where the fault is
20.11.11 Checking IMA Group Status
You can check whether the IMA group status is normal.
20.11.12 Checking IMA Link Status
You can check whether the IMA link status is normal.
20.11.1 Checking Networkwide Multiplex Section Parameters

In the same MSP subnet, every NE should have the same multiplex section parameter settings.
After conguring or adjusting an MSP subnet, you need to check networkwide multiplex
section parameters.
Prerequisites
n The MSP protection subnet must be created.
Procedure
Step 2 In the Protection View, right-click and select Check Networkwide MS Parameters.
A progress bar displays.
----End

20.11.2 Checking TPS Switching status

If tributary protection switching (TPS) takes place, it indicates the protected tributary board
failed. Network maintenance engineers can check TPS switching status to detect faults that
make the protection facility unavailable.
Prerequisites
n TPS protection must be congured.
Procedure
Function Tree.
Step 2 Click Query to query the protection switching status.
----End
20.11.3 Checking 1+1 Board Switching Status

If board 1+1 protection switching is trigger, it indicates the protected board failed. Network
maintenance engineers can check 1+1 board switching status, to detect faults that make the
protection facility unavailable.
Prerequisites
n The protection board must be created.
Procedure
Function Tree.
Step 2 Click Query to query the 1+1 board switching status.
----End
20.11.4 Checking MSP Ring Switching Status

To detect faults on NEs or bers in an MSP ring, maintenance engineers can check the
switching status of the MSP ring. Then, engineers can locate the point where the fault is
Prerequisites
n The MSP protection subnet must be created.
Procedure
Protection View > SDH Protection Subnet Maintenance .
Step 2 In the left-hand pane, select an MSP ring. The status of the nodes in the subnet is displayed in
the right-hand pane.

Step 3 Click Query to query the switching status of the nodes.

----End
20.11.5 Checking Linear MSP Switching Status

To detect faults on NEs or bers in a linear MSP protection subnet, maintenance engineers can
check the switching status of linear MSP. Then, engineers can locate the point where the fault
is generated according to the switching status of every NE in the protection subnet.
Prerequisites
Procedure
Protection View > SDH Protection Subnet Maintenance in the Protection View.
Step 2 In the left-hand pane, select a linear MSP subnet. The status of the nodes in the subnet is
displayed in the right-hand pane.
----End
20.11.6 Exercising MSP Protection Switching

Maintenance engineers can exercise switching for MSP rings or chains to ensure the command
can be issued correctly. So, services are not interrupted because the protection facility is
unavailable in the event of failure.
Prerequisites
n The MSP ring or chain must be created.
Procedure
Step 2 Select Protection View > SDH Protection Subnet Maintenance.
Step 3 In the left-hand pane, select the MSP ring that you want to perform exercise switching. In the
right-hand pane, right-click the desired NE and select exercise switching in a direction.
NOTE
Exercise switching is not service-affecting.

Step 5 View whether ofce direction 1 status and ofce direction 2 status of every NE are normal.
If not, check whether NEs on the MSP ring or chain have the same protection subnet
conguration or whether the conguration is correct.
----End

20.11.7 Checking SNCP or PP Switching Status

To detect faults on NEs or bers in an SNCP or PP protection subnet, maintenance engineers
can check the switching status of SNCP or PP protection. Then, engineers can locate the point
where the fault is generated according to the switching status of every NE in the protection
subnet.
Prerequisites
n The SNCP/PP protection subnet must be created.
Procedure
Protection View > SDH Protection Subnet Maintenance.
Step 2 In the left-hand pane, select an SNCP or PP subnet. The status of the nodes in the subnet is
displayed in the right-hand pane.
----End
20.11.8 Checking GNE Switching Status

If an NE has a standby GNE, when the active GNE fails, the NE communicates with the T2000
through the standby GNE automatically. To detect GNE communication failure timely, you
can check GNE switching status, to ensure that NEs communicate with the T2000 through
the GNE correctly.
Prerequisite
The active and standby GNEs must be created for an NE.
Procedure
Step 2 Click the NE tab.
Step 3 Click Refresh to query the GNE switching status.
----End
20.11.9 Checking Clock Switching Status

Clock failure may interrupt services. To detect clock source failure timely, you can check
clock switching status.
Prerequisites
n The reference clock source must be set.
Procedure
Step 1 Select Conguration > Clock View from the Main Menu. In the Clock View, right-click an
NE icon and select Clock Source Switching from the shortcut menu.

Step 2 Click the Clock Source Switching tab. Click Query to query the switching status of the
current clock source.
----End
20.11.10 Checking Switching Status of an SNCP Trail

To detect faults on NEs or bers that an SNCP trail passes through, maintenance engineers can
check the switching status of the trail. Then, engineers can locate the point where the fault is
Prerequisites
n The SNCP trail must be created.
Context
CAUTION
Forced switching is a potentially service-affecting operation.
Procedure
Step 2 The Set Trail Browse Filter Conditions dialog box is displayed. Select or enter parameters
as needed. Set lter criteria and lter trails.
Step 3 Select an SNCP trail from the list. Click the Maintenance button and select SNC Service
Control from the drop-down list. The SNC service control dialog box is displayed.
Step 4 Click Query to query the switching status of the dual-fed point and selective-receiving point.
----End
20.11.11 Checking IMA Group Status

You can check whether the IMA group status is normal.
Prerequisites
n IMA must be created.
Procedure
Step 1 In the NE Explorer, click a board and then select Conguration > ATM Interface
Management > ATM IMA Management from the Function Tree.
Step 2 Click the IMA Group States tab. Click Query to query the current IMA group status.
----End
20.11.12 Checking IMA Link Status

You can check whether the IMA link status is normal.

Prerequisites
n IMA must be created.
n The binding path must be congured correctly.
Procedure
Step 1 In the NE Explorer, click a board and select Conguration > ATM Interface Management >
ATM IMA Management from the Function Tree.
Step 2 Click the IMA Link States tab. Click Query to query the current IMA link status.
----End
20.12 Managing Overhead Bytes

You can set and query SDH overhead bytes.
Prerequisites
n All path overhead bytes, except the J0 byte, must be congured with corresponding
services before you manage them.
Procedure
Step 1 In the NE Explorer, select a line board and choose Conguration > Overhead Management
> Regenerator Section Overhead from the Function Tree.
NOTE
Click the Display in Text Format or Display in Hexadecimal radio button to modify the display mode
Step 2 Click Query to update the information of the overhead bytes.

Step 3 If you want to modify an overhead byte, double-click it. The Overhead byte setting dialog
box is displayed.

Step 4 Modify the overhead byte as required. Click OK. A prompt dialog box is displayed. Click Yes.
Step 5 If you have modied the overhead bytes, click Apply. Click OK in the conrmation dialog
box.
Step 6 Optional: If you want to manage the VC12 path overhead bytes, select a board and choose
Conguration > Overhead Management > VC12 Path Overhead from the Function Tree.
----End
Examples
Postrequisite
20.13 Managing Logs

Logs provide a sequential record of events, which helps network administrators to nd illegal
logins and unauthorized operations, or to analyze faults.
Context
You can manage the logs on the T2000 as follows:
2.3.220.13.1 Viewing the Operation Log

The T2000 security logs keep a record of all T2000 users’ operation activities to the T2000
and equipment. You can view the logs and lter them by T2000 user, operation terminal,
record type, danger level, and start/end time.


To prevent loss of security logs, you need to dump logs manually or automatically. The
T2000 includes a scheduler that can be used for repetitive tasks and is a particularly effective
timesaver. Use this procedure to set a scheduled security log dump.
2.3.620.13.3 Viewing the NE Security Log
The NE security logs keep a record of operations done by all NE users and results of the
operations. You can view the NE security logs and lter the records by NE user, event name
and creation time.
20.13.1 Viewing the T2000 Security Logs

The T2000 security logs keep a record of all T2000 users’ operation activities to the T2000
and equipment. You can view the logs and lter them by T2000 user, operation terminal,
record type, danger level, and start/end time.
Prerequisite
Procedure
Step 1 Select System Administration > Operation Log from the Main Menu.
Step 2 Set the condition for viewing the logs.
Step 3 Click Query and view the logs.
----End

To prevent loss of security logs, you need to dump logs manually or automatically. The
T2000 includes a scheduler that can be used for repetitive tasks and is a particularly effective
timesaver. Use this procedure to set a scheduled security log dump.
Prerequisite
You must log in to the T2000 as super user admin.
Context
NOTE
n If the running period is set to Running once, when creating or modifying a scheduled task, set the
time to execute the task at least ve minutes later than the current time (that is, the server time).
Procedure
Step 1 Select System Administration > Scheduled Task Management from the Main Menu.
Step 3 Select Security Log Dump for the task type, and enter the task name. Click Next.
Step 4 Set the period to run the task and click Next.
Step 6 Click Finish. The T2000 will dump the security logs according to the above settings.
----End

20.13.3 Viewing the NE Security logss

The NE security logs keep a record of operations done by all NE users and results of the
operations. You can view the NE security logs and lter the records by NE user, event name
and creation time.
Prerequisite
Context
NOTE
The NE security logs can be viewed only and cannot be deleted.
Procedure
Step 1 In the NE Explorer, click the NE and select Security > NE Security Log from the Function
Tree.
Step 2 Set the log lter criteria.
Step 3 Click Query to query the logs.
----End
20.14 Ethernet OAM Maintenance

You can perform Ethernet operation, administration and maintenance (OAM) operations.
Context
20.14.1 Ethernet OAM

You can maintain Ethernet Layer 2 through the Ethernet OAM feature.
20.14.2 Creating MPs
You need to create maintenance points (MPs) before executing Ethernet OAM operations.
20.14.3 Performing CC Check
You can perform consecutive check (CC) on Ethernet services, to check the connectivity of
services for fault location and repair.
20.14.4 Performing LB Check
You can perform loopback (LB) check on Ethernet services without interrupting services, to
check the connectivity of services for fault location and repair.
20.14.5 Performing LT Check
You can perform link trace (LT) check on Ethernet services, to check the MIP information in
the link for fault location and repair.
20.14.1 Ethernet OAM

You can maintain Ethernet Layer 2 through the Ethernet OAM feature.
With the growth of Ethernet services, more Ethernet services are applied to MAN and WAN
networks. Therefore, maintainability of Ethernet services is increasingly the focus of attention.
Currently the ways to maintain Ethernet Layer-2 are limited, and thus operating, managing and
maintaining Ethernet services over a transport network are limited.

Ethernet OAM implements automatic fault detection, fault location and fault isolation through
continuity check (CC), in-service loopback (LB) and link trace (LT) operations. In this way,
OAM capability of Ethernet services is improved.
The operation object of Ethernet OAM is maintenance points, which include maintenance end
points (MEPs) and maintenance intermediate points (MIPs).
Ethernet OAM is implemented in this way: An MEP initiate fault detection. When an MP
detects a fault, it reports alarms and the alarms are correctly synchronized to the Ethernet
trails related to MPs.
20.14.2 Creating MPs

You need to create maintenance points (MPs) before executing Ethernet OAM operations.
Prerequisites
n Applies to the EFS, EMS, EMS4 and EGS4 boards.
n The Ethernet trail must be created and activated.
Context
MPs include maintenance end points (MEPs) and maintenance intermediate points (MIPs). All
OAM functions must be initiated by the MEPs. The MIP does not send any OAM frames, but
the MIP responds to LT frames, or LB frames in which the destination node is the MIP itself.
Procedure
Step 1 Select Trail > Ethernet Trail Management from the Main Menu. Right-click an Ethernet
trail and select Ethernet Service OAM Management from the shortcut menu.
Step 2 Click Create and the Create Maintenance Point dialog box is displayed. Complete the
information.
NOTE
n VLAN ID: Leave this eld blank for PORT services. For PORT+VLAN services, set the VLAN ID
of services to be monitored.
n Direction: The direction of transmitting and receiving OAM data from the MP to the maintenance
area. If the data is from interior board, the MP direction is egress. If the data is from exterior board,
the MP direction is ingress. MIPs can be set to bidirectional only.
----End
20.14.3 Performing CC Check

You can perform consecutive check (CC) on Ethernet services, to check the connectivity of
services for fault location and repair.
Prerequisites
n The OAM maintenance point must be created.

Context
During the CC check, the source MEP constructs and transmits CC frames periodically. The
destination MEP receives the CC frames and starts the CC check. If the destination MEP does
not receive the CC frames from the source in a period of time (for example, 3.5 times transmit
period), the MEP reports the CCLOS alarm automatically.
Procedure
Step 2 Right-click the node to be monitored and select Activate CC from the shortcut menu.
----End
20.14.4 Performing LB Check

You can perform loopback (LB) check on Ethernet services without interrupting services, to
check the connectivity of services for fault location and repair.
Prerequisites
Context
During the LB check, the source MEP constructs and transmits LBM frames and starts the timer
for timing. If the destination MP receives the LBM frames, it sends LBR frames back to the
source MEP. The loopback is successful. If the source MEP timer timed out, the loopback fails.
Procedure
Step 2 Right-click the node to be monitored and select Start LB from the shortcut menu. The LB
Sink MP ID dialog box is displayed.

Step 3 Enter the LB test sink maintenance point ID.

----End
20.14.5 Performing LT Check

You can perform link trace (LT) check on Ethernet services, to check the MIP information in
the link for fault location and repair.
Prerequisites
Context
During the LT check, the source MEP constructs and transmits LTM frames and starts the timer
for timing. All MPs that receive the LTM frames send LTR frame response, according to which
you can verify all MIPs that are passed through from the source MEP to the destination one.
Procedure
Step 2 Right-click the node to be monitored and select Start LT from the shortcut menu. The LT
Sink MP ID dialog box is displayed.

Step 3 Enter the LT test sink maintenance point ID.

----End
20.15 Maintaining Ethernet OAM at a Station

You can perform Ethernet operation, administration and maintenance (OAM) operations at a
station. You can maintain Ethernet Layer 2 through the Ethernet OAM function.
Prerequisites
n Applies to the EFS, EMS, EMS4 and EGS4 boards.
Procedure
Step 1 In the NE Explorer, click an NE and select an Ethernet board. Choose Conguration >
Ethernet Maintenance > Ethernet Service OAM Management from the Function Tree.
Step 2 Click Query to query the NE information.
Step 3 Click New and the Create MP dialog box is displayed. Complete the information.
NOTE
When setting parameters, note the following points:
n VLAN ID: Leave this eld blank for services of the Port type. For services of the PORT+VLAN
type, set the VLAN ID of services you want to monitor.
n Direction: The direction of transmitting and receiving OAM data from the MP to the maintenance
area. If the data is from interior board, the MP direction is Egress or bidirectional. If the data is from
exterior board, the MP direction is Ingress or bidirectional. MIPs can be set to bidirectional only.
Step 5 Optional: Click OAM and select Activated CC from the drop-down list, to perform CC
check.
Step 6 Optional: Click OAM and select Start LB from the drop-down list. The LB Test Sink MP
ID dialog box is displayed. After you set the parameter, go back to Step 4.
Step 7 Optional: Click OAM and select Start LT from the drop-down list. The LT Test Sink MP
ID dialog box is displayed. After you set the parameter, go back to Step 4.
----End
20.16 Testing the Ethernet Communication Status

The Ethernet test is used for commissioning and fault location.
Prerequisites
Procedure
Step 1 In the NE Explorer, click an Ethernet board and select Conguration > Ethernet
Maintenance > Ethernet Test from the Function Tree.
Step 2 Set the test parameters for the ports to be tested in the Ethernet Test List.

Step 3 Click Apply to deliver the conguration. Click Query, and compare the data of Counter
of Frames Sent with that of Counter of Received Response Test Frame to check the
performance of the port.
----End
20.17 Guaranteeing Laser Performance

The input and output optical power of board ports is an important index for measuring laser
performance. Laser performance is crucial for the quality and transmission distance of
signals. To keep the entire transmission system running stably, you need to guarantee laser
performance, that is, to control the input and output optical power of the ports, and uctuation
of upper and lower threshold of input optical power within the appropriate range, and to
correct or alert optical power offset.
Prerequisites
n The board with optical power monitoring function must be created.
Procedure
Step 1 Select Conguration > Optical Power Management from the Main Menu.
Step 2 In the NE list, select a board and click .

Step 3 Click Query to query the optical power information from the NE.

Step 4 Optional: Right-click Input Reference Value and select Copy Input Optical Power from
the shortcut menu; or right-click Output Reference Value and select Copy Output Optical
Power from the shortcut menu.
NOTE
Click Save Reference Value to save the settings.
If you think the current adjusted optical power value you query is good, click Save Reference Value and
set it as the reference value. Power offset is based on the reference value.
Step 5 Optional: Click Save Networkwide Reference Value and set the current power value of the
entire network as the reference value.
----End
20.18 Collecting Equipment Data

In the event of equipment failure, you need to collect equipment data. The data collection
command and results are saved to a le for fault diagnosis. The equipment data that you
can collect includes: Basic conguration, service conguration, interface conguration,

Metro management, equipment protection, equipment maintenance, testing, performance, NE

communication management and security.
Prerequisite
Procedure
Step 1 Select System Administration > Equipment Data Collection from the Main Menu.
Step 2 Select the NE for which you want to collect data under Select NE.
Step 3 Select the function for which you want to collect data under Function Selection.
Step 4 Click Begin. Two progress bars are displayed, showing the progress of collecting NE data and
the overall data collection.
NOTE
n The results are saved in T2000\server\nemml\dcdatles on Windows platform.
n The results are saved in /T2000/server/nemml/dcdatles directory on UNIX platform.
----End
20.19 Disabling Service-Affecting Settings Automatically

Loopback and laser shutdown are useful NE maintenance functions. But they interrupt services
at a port and may interrupt the communication between an NE and the T2000. You can set
automatic disabling before performing loopback or laser shutdown, so that the NE cancels
loopback or laser shutdown automatically.
Prerequisite
Context
NOTE
If a port is the only way that an NE communicates with the T2000, performing loopback or laser
shutdown at the port will result in loss of communication. Before performing loopback or laser shutdown,
you must set automatic disabling for this NE. Otherwise, after the communication is lost, you cannot use
the T2000 to log in to the NE to disable loopback or laser shutdown.
Procedure
Step 1 Select Conguration > Automatic Disabling of NE Function from the Main Menu.
Step 2 Select the appropriate NE and click the double-right-arrow button (red).
Step 3 Select a value in the Auto Disabling and Auto Disabling Time panes.
Step 4 Click Apply.
----End
20.20 Cleaning Up the Hard Disk of the Computer

As the T2000 runs, dumped data accumulates and occupies more server space. You are
recommended to regularly check the server space and the size of the dump folder, and delete
unnecessary les to ensure the space for the proper running of the T2000.

Context
NOTE
The T2000 provides automatic and manual dumping for alarm events, abnormal events, security log,
and performance events. The dump location is defaulted to the installation directory of the T2000
/server/Com*Log. For example, the dump location for alarm events is /server/ComAlarmLog under the
installation directory. Similarly, the abnormal events are dumped in the ComEventLog directory, the
security log in the ComSecurityLog directory, and performance events in the PerfLog directory.
Procedure
n On Windows Platform
1. Right-click in the installation directory of the T2000 and select Attributes. View
the used space of the folder.
2. If the used space of the T2000 installation folder is more than 90% of the disk
where it is located, check the size of the dump folder. If there are too many les
in the dump directory, you can check the time the les were created and delete
those that are created earlier.
n On UNIX Platform
1. Check the used space of the /2000 partition.
Use the df-k command to view the used space of each partition, the rate, and the
free space.
2. If the used space of the /T2000 partition is more than 90%, check the size of the
dump folder. If there are too many les in the dump directory, you can check the
time the les were created and delete those that are created earlier.
----End

Operator Guide 21 Troubleshooting
21 Troubleshooting
About This Chapter

On the T2000 you can perform troubleshooting for equipment.
Context
Troubleshooting includes:
21.1 Performing a Loopback

The loopback is a common and effective way to locate faults for equipment. On the T2000 you
can set a loopback for equipment.
21.2 Diagnosing Alarms
The T2000 provides a wizard for fault diagnosis. In daily maintenance, the engineer can create
fault diagnosis rules. When an alarm is raised, the engineer is able to locate the fault by
using the fault diagnosis wizard.
21.3 Performing Protection Switching
You can perform equipment-level and network-level protection switching by following the
instructions below.
21.4 Resetting Boards
You can reset a board on the T2000 by following the instructions below.
21.5 Performing Remote Maintenance
You can perform remote maintenance on the T2000 by following the instructions below.

21 Troubleshooting Operator Guide
21.1 Performing a Loopback

The loopback is a common and effective way to locate faults for equipment. On the T2000 you
can set a loopback for equipment.
Context
According to different loopback objects, a loopback includes:
21.1.1 Setting a Loopback at an SDH Interface

Use this procedure to set a loopback at an SDH interface on the T2000. The SDH interface
loopback is a common fault location method to test and maintain the SDH board. The SDH
interface loopback is used to test the ber connections and interfaces on the SDH board, as
well as to test the SDH service processing module and the cross-connect board.
21.1.2 Setting a Loopback at a PDH Interface
Use this procedure to set a loopback at an PDH interface on the T2000. The PDH interface
loopback is a common fault location method to test and maintain the PDH board. The PDH
interface loopback is used to test the ber connections and interfaces on the PDH board, as
well as to test the PDH service processing module and the cross-connect board.
21.1.3 Setting a Loopback at an Ethernet Interface
Use this procedure to set a loopback at an Ethernet interface on the T2000. The Ethernet
interface loopback is a common fault location method to test and maintain the Ethernet board.
The Ethernet interface loopback is used to test the ber connections on the Ethernet board,
to test the physical and MAC layers of the Ethernet interface, as well as to test the SDH
layer (that is, the line).
21.1.4 Setting a Loopback at an ATM Interface
Use this procedure to set a loopback at an ATM interface on the T2000. The ATM interface
loopback is a common fault location method to test and maintain the ATM board. The ATM
interface loopback is used to test the ber connections and interfaces on the ATM board, as
well as to test the cross-connect board and the line board.
21.1.5 Setting a Loopback at a VC4 Path
Use this procedure to set a loopback at a VC4 path on the T2000. The VC4 path loopback is a
common fault location method to test and maintain the SDH board. The VC4 path loopback is
used to test the ber connections and interfaces on the SDH board, as well as to test the SDH
service processing module and the cross-connect board.
The VC3 path loopback is a common fault location method to test and maintain the SDH
board. The VC3 path loopback is used to test the ber connections and interfaces on the SDH
board, as well as to test the SDH service processing module and the cross-connect board.
21.1.7 Setting a Loopback over a Trail
Use this procedure to set a loopback over an SDH trail. The SDH trail loopback is a common
fault location method to test and maintain the SDH equipment. The SDH trail loopback is used
to test whether the nodes between the source and loopback nodes (including the source and
loopback nodes themselves) work properly, and also whether the nodes between the sink and
loopback nodes (including the sink and loopback nodes themselves) work properly.
21.1.1 Setting a Loopback at an SDH Interface

Use this procedure to set a loopback at an SDH interface on the T2000. The SDH interface
loopback is a common fault location method to test and maintain the SDH board. The SDH
interface loopback is used to test the ber connections and interfaces on the SDH board, as
well as to test the SDH service processing module and the cross-connect board.
Prerequisite

Context
NOTE
The SDH interface loopback can be an outloop or an inloop.
n When an outloop is used, the SDH signal received by the NE is returned at the SDH interface. See the
following gure. An outloop is used to test the bers connections and interfaces on the SDH board.
n When an inloop is used, the SDH signal transmitted by the NE is returned to the cross-connect board
at the SDH interface. See the following gure. An inloop is used to test the SDH service processing
module and the cross-connect board.
CAUTION
As a loopback will interrupt services, it is only used for fault location and must be released
after the fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and select Conguration > SDH Interface from the
Function Tree.
Step 2 Select By function. Select Optical (Electrical) Interface Loopback.
Step 3 Select an SDH interface from the list and double-click Optical (Electrical) Interface
Loopback to choose a loopback mode.
Step 4 Click Apply. The Conrm dialog box is displayed.
----End
21.1.2 Setting a Loopback at a PDH Interface

Use this procedure to set a loopback at an PDH interface on the T2000. The PDH interface
loopback is a common fault location method to test and maintain the PDH board. The PDH
interface loopback is used to test the ber connections and interfaces on the PDH board, as
well as to test the PDH service processing module and the cross-connect board.
Prerequisite

Context
NOTE
The PDH interface loopback can be an outloop or an inloop.
n When an outloop is used, the PDH signal received by the NE is returned at the PDH interface. See the
following gure. An outloop is used to test the bers connections and interfaces on the PDH board.
n When an inloop is used, the PDH signal transmitted by the NE is returned to the cross-connect board
at the PDH interface. See the following gure. An inloop is used to test the PDH service processing
module and the cross-connect board.
CAUTION
Procedure
Step 1 In the NE Explorer, select a board and select Conguration > PDH Interface from the
Function Tree.
Step 2 Select By function. Select Tributary Loopback.
Step 3 Select a PDH interface from the list and double-click Tributary Loopback to choose the
loopback mode.
----End
21.1.3 Setting a Loopback at an Ethernet Interface

Use this procedure to set a loopback at an Ethernet interface on the T2000. The Ethernet
interface loopback is a common fault location method to test and maintain the Ethernet board.
The Ethernet interface loopback is used to test the ber connections on the Ethernet board,
to test the physical and MAC layers of the Ethernet interface, as well as to test the SDH
layer (that is, the line).
Prerequisite

Context
NOTE
The Ethernet interface loopback can be an outloop or an inloop. Both the outloop and inloop are divided
into two layers, that is, the physical layer and the MAC layer.
n When an outloop is used, the Ethernet signal received by the NE is returned at the Ethernet interface
(physical layer or MAC layer). See the following gure. The physical layer outloop is used to
test the ber connections on the Ethernet board. The MAC layer outloop is used to test the MAC
layer of the Ethernet interface.
n When an inloop is used, the Ethernet signal transmitted by the NE is returned to the SDH layer at the
Ethernet interface. See the following gure. The physical layer inloop is used to test the MAC layer
and the SDH layer. The MAC layer inloop is used to test the SDH layer.
CAUTION
Procedure
Step 1 In the NE Explorer, select a board and select Conguration > Ethernet Interface
Management > Ethernet Interface from the Function Tree.
Step 2 Select External Port and click the Basic Attributes tab.
Step 3 Select an Ethernet interface from the list and double-click MAC Loopback or PHY Loopback
to choose the loopback mode.
Step 4 Click Apply.
A result prompt is displayed.
Step 5 Click Close.
----End
21.1.4 Setting a Loopback at an ATM Interface

Use this procedure to set a loopback at an ATM interface on the T2000. The ATM interface
loopback is a common fault location method to test and maintain the ATM board. The ATM
interface loopback is used to test the ber connections and interfaces on the ATM board, as
well as to test the cross-connect board and the line board.

Prerequisite
Context
NOTE
The ATM interface loopback can be an outloop or an inloop.
n When an outloop is used, the ATM signal received by the NE is returned at the ATM interface. See
the following gure. An outloop is used to test the ber connections and interfaces on the ATM board.
n When an inloop is used, the ATM signal transmitted by the NE is returned to the cross-connect
board at the ATM interface. See the following gure. An inloop is used to test the cross-connect
board and the line board.
CAUTION
Procedure
Step 1 In the NE Explorer, select a board and select Conguration > ATM Interface Management
> ATM Interface Management from the Function Tree.
Step 2 Select Internal Port.
Step 3 Select an ATM interface from the list and double-click Loopback to choose the loopback mode.
Step 4 Click Apply.
A result prompt is displayed.
Step 5 Click Close.
----End

Use this procedure to set a loopback at a VC4 path on the T2000. The VC4 path loopback is a
common fault location method to test and maintain the SDH board. The VC4 path loopback is
used to test the ber connections and interfaces on the SDH board, as well as to test the SDH
service processing module and the cross-connect board.

Prerequisite
Context
NOTE
The VC4 path loopback can be an outloop or an inloop.
n When an outloop is used, the VC4 signal received by the NE is returned over the VC4 path. In the
following gure, an outloop is set for the rst VC4 path on the STM-4 line board. An outloop is used
to test the bers connections and interfaces on the SDH board.
n When an inloop is used, the VC4 signal transmitted by the NE is returned to the cross-connect board
over the VC4 path. In the following gure, an inloop is set for the rst VC4 path on the STM-4 line
board. An inloop is used to test the SDH service processing module and the cross-connect board.
CAUTION
Procedure
Function Tree.
Step 2 Select By function. Select VC4 Loopback.
Step 3 Select an SDH interface from the list and double-click VC4 Loopback to choose the loopback
mode.
----End

The VC3 path loopback is a common fault location method to test and maintain the SDH
board. The VC3 path loopback is used to test the ber connections and interfaces on the SDH
board, as well as to test the SDH service processing module and the cross-connect board.

Prerequisite
Context
NOTE
The VC3 path loopback can be an outloop or an inloop.
n When an outloop is used, the VC3 signal received by the NE is returned over the VC3 path. In the
following gure, an outloop is set for the rst VC3 path in the rst VC4 path on the STM-1 line
board. An outloop is used to test the bers connections and interfaces on the SDH board.
n When an inloop is used, the VC3 signal transmitted by the NE is returned over the VC3 path. In the
following gure, an inloop is set for the rst VC3 path in the rst VC4 path on the STM-1 line board.
An inloop is used to test the SDH service processing module and the cross-connect board.
CAUTION
Procedure
Function Tree.
Step 2 Select By function. Select VC3 Loopback.
Step 3 Select an SDH interface from the list and double-click VC3 Loopback to choose the loopback
mode.
----End
21.1.7 Setting a Loopback over a Trail

Use this procedure to set a loopback over an SDH trail. The SDH trail loopback is a common
fault location method to test and maintain the SDH equipment. The SDH trail loopback is used
to test whether the nodes between the source and loopback nodes (including the source and

loopback nodes themselves) work properly, and also whether the nodes between the sink and
loopback nodes (including the sink and loopback nodes themselves) work properly.
Prerequisites
n Trails must be created.
Context
NOTE
The SDH trail loopback includes "Loopback to Source" and "Loopback to Sink".
n When "Loopback to Source" is used, the signal coming from the trail source is returned to the source
over the trail. See the following gure. "Loopback to Source" is used to test whether the nodes
between the source and loopback nodes (including the source and loopback nodes themselves)
work properly.
n When "Loopback to Sink" is used, the signal coming from the trail sink is returned to the sink over
the trail. See the following gure. "Loopback to Sink" is used to test whether the nodes between
the sink node and the loopback node (including the sink node and the loopback node themselves)
work properly.
CAUTION
Procedure
NOTE
Step 3 Select a trail to display its details.

Step 4 Click Maintenance and select Loopback. The Loopback dialog box is displayed.
Step 5 Click the tab according to the loopback location. You can choose to set the loopback status
at the tributary board, VC4 path and optical/electrical port.

Step 6 Select a PDH interface, an SDH interface or a VC path. Double-click the Loopback Status to
select the loopback mode.

----End
21.2 Diagnosing Alarms

The T2000 provides a wizard for fault diagnosis. In daily maintenance, the engineer can create
fault diagnosis rules. When an alarm is raised, the engineer is able to locate the fault by
using the fault diagnosis wizard.
21.2.1 Creating Fault Diagnosis Rules

Fault diagnosis rules are helpful in quick fault location. Network maintenance engineers can
accumulate and share experience by creating fault diagnosis rules.
21.2.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.
21.2.1 Creating Fault Diagnosis Rules

Fault diagnosis rules are helpful in quick fault location. Network maintenance engineers can
accumulate and share experience by creating fault diagnosis rules.
Prerequisite

Context
NOTE
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 Select Fault > Set Fault Diagnosis Rules from the Main Menu.
Step 2 Right-click the Fault Diagnosis Rules and select 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 entry and select Add Steps from the shortcut menu.
The Create Diagnosis Steps dialog box is displayed.
Step 5 Enter the Alarm Causes, Diagnosis Method and Processing Method elds. Click OK.
A step entry is added under the rule entry.
Step 6 Click Apply.
Step 7 Optional: You can right-click a step entry and select Modify to modify the original contents
as needed.
----End
21.2.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.
Prerequisites
n The fault diagnosis rules must be created.
Context
NOTE
n If the selected alarm does not have a relevant fault diagnosis rule, a prompt appears saying that
the wizard cannot be started.
n If the fault diagnosis wizard is ever used, the handling method of the last time is prompted, and then
you can click Diagnose Again to locate the fault.
Procedure
Step 2 Right-click an alarm in the alarm list. Select Fault Diagnosis. The Fault Diagnosis dialog
box is displayed.
Step 3 Select the most possible cause of the fault according to the actual situation. If you cannot
decide which cause is the most possible, then select the rst cause.
Step 4 Click Next. The wizard displays the corresponding diagnosis method.
Step 5 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 6 If fault location fails, click Back to re-select a cause until you locate the fault successfully or
you have tried all the causes.

Step 7 Click Clear to exit the wizard.

----End
21.3 Performing Protection Switching

You can perform equipment-level and network-level protection switching by following the
instructions below.
Context
According to different network protection schemes, the switching for network-level protection
includes:
21.3.1 MSP Protection Switching Priority

MSP protection switching is triggered by automatic switching conditions and external
switching requests. Automatic switching is triggered by signal failure (for example, the LOS,
LOF, MS_AIS and B2OVER alarms raised on the equipment) and signal degrade (for example,
the B2SD alarm raised on the equipment). External switching is performed by the user by
issuing an external switching command, and thus brings a status change of the multiplex
section. External switching requests include lockout, forced switching, manual switching,
exercise switching and clear of switching.
21.3.2 Performing MSP Ring Switching
On the T2000, you can perform or clear external switching for an MSP ring. In deployment
and commissioning, you can perform switching to test whether MSP ring switching works
properly. In fault maintenance, you can perform this operation for fault location.
21.3.3 Performing Linear MSP Switching
On the T2000, you can perform or clear external switching for linear MSP. In deployment
and commissioning, you can perform switching to test whether linear MSP switching works
21.3.4 Performing SNCP Switching
On the T2000, you can perform or clear external switching for SNCP protection. In
deployment and commissioning, you can perform switching to test whether SNCP switching
works properly. In fault maintenance, you can perform this operation for fault location.
21.3.5 RPR Protection Switching Priority
RPR protection switching is triggered by automatic switching conditions and external
switching requests. Automatic switching is triggered by signal failure and signal degrade.
External switching is performed by the user by issuing an external switching command, and
thus brings a status change of the RPR. External switching includes forced switching, manual
switching and clear of switching.
21.3.6 Performing RPR Protection Switching
On the T2000, you can perform or clear external switching for an RPR node. In deployment
and commissioning, you can perform switching to test whether RPR protection switching
On the T2000, you can perform or clear external switching for an RPR ring network. In
deployment and commissioning, you can perform switching to test whether RPR protection
switching works properly. In fault maintenance, you can perform this operation for fault
location.
21.3.8 Performing 1+1 Board Protection Switching
On the T2000, you can perform or clear protection switching for a board, including the SCC
board, the cross-connection board and the clock board. In deployment and commissioning,
you can perform switching to test whether board protection switching works properly. In fault
maintenance, you can perform this operation for fault location.
On the T2000, you can perform or clear switching for a TPS protection group of PDH boards.
In deployment and commissioning, you can perform switching to test whether TPS switching

16.8.621.3.10 Performing Board-Level Protection Switching for Data Service Boards

On the T2000, you can perform or clear switching for board-level protection of data service
boards. In deployment and commissioning, you can perform switching to test whether
board-level protection switching for data service boards works properly. In fault maintenance,
you can perform this operation for fault location.
21.3.1 MSP Protection Switching Priority

MSP protection switching is triggered by automatic switching conditions and external
switching requests. Automatic switching is triggered by signal failure (for example, the LOS,
LOF, MS_AIS and B2OVER alarms raised on the equipment) and signal degrade (for example,
the B2SD alarm raised on the equipment). External switching is performed by the user by
issuing an external switching command, and thus brings a status change of the multiplex
section. External switching requests include lockout, forced switching, manual switching,
exercise switching and clear of switching.
For MSP protection, the following switching requests can bring a status change of the
multiplex section. See the following table for their switching (or preemption) priorities.
NOTE
n In the following table, the switching priorities are given in a descending order, that is, LP_S (SF_P)
has the highest priority, and NR has the lowest. The requests of lockout, forced switching, manual
switching and exercise switching can be cleared as needed.
n For LP_S (SF_P), the lockout of protection is available for only the span instead of the ring. LP_S
and SF_P have the same priority, and perform the same action on both the protocol and the service.
LP_S is triggered by an external command, and SF_P is triggered by the protection channel failure in
a four-ber ring.
n The span switching has a higher priority than the ring switching.
n External commands are issued on the T2000. After the execution of a command, the NE keeps this
request until the command is cleared or preempted by another command with a higher priority. If there
is a switching request with a higher priority in the network, the external command cannot be actually
issued, and thus the NE loses this external command request. An external command can be cleared
only when the clear request is performed in the same direction on the NE as the switching request.
Table 21-1 MSP Protection Switching Priorities

No. Switching request Description Trigger condition
1 LP_S (SF_P) Lockout of An external
Protection - Span command, or signal
failure on the
protection channel of
a four-ber ring
2 FS_S Forced Switching to An external
Protection - Span command
3 FS_R Forced Switching to An external
Protection - Ring command
4 SF_S Signal Failure - Span Signal failure on a
span of the four-ber
ring working channel
5 SF_R Signal Failure - Ring Signal failure on
the working channel
of a four-ber or
two-ber ring
6 SD_P Signal Degrade - Signal degrade on the
Protection protection channel
of a four-ber or
two-ber ring


7 SD_S Signal Degrade - Signal degrade on a
Span span of the four-ber
ring working channel
8 SD_R Signal Degrade - Signal degrade on
Ring the working channel
of a four-ber or
two-ber ring
9 MS_S Manual Switching to An external
Protection - Span command
10 MS_R Manual Switching to An external
Protection - Ring command
11 WTR Wait-to-Restore Status request
between NEs during
the switching
12 EXER_S Exerciser - Span An external
command
13 EXER_R Exerciser - Ring An external
command
14 RR_S Reverse Request - A reverse request
Span during the switching
15 RR_R Reverse Request - A reverse request
Ring during the switching
16 NR No Request
21.3.2 Performing MSP Ring Switching

On the T2000, you can perform or clear external switching for an MSP ring. In deployment
and commissioning, you can perform switching to test whether MSP ring switching works
Prerequisites
Context
NOTE
The external switching for MSP protection includes: lockout, forced switching, manual switching and
exercise switching.
n The forced switching may interrupt the service, and has a higher priority than signal failure and
signal degrade on the protection section. That is, the switching is performed without regard to the
status of the working and protection sections.
n The manual switching has a lower priority than signal failure and signal degrade on the protection
section. The manual switching request is valid only when there are no signal failure or signal degrade
on the protection section.
n The exercise switching is used to test the APS protocol. In fact services will not be switched to the
protection section, and only the calculation result of the protocol is displayed.

Procedure
Step 1 Select Conguration > Protection View from the Main Menu. Select Protection View >
SDH Protection Subnet Maintenance in the Protection View.
Step 2 Select an MSP ring from the subnet list.
Step 3 Right-click the desired NE and select an ofce direction to switch, lock out or clear switching.
The Conrm dialog box is displayed.
NOTE
n The ofce direction can be switched only when it is not locked out.
n For two-ber and four-ber rings, only two ofce directions can be switched.
----End
21.3.3 Performing Linear MSP Switching

On the T2000, you can perform or clear external switching for linear MSP. In deployment
and commissioning, you can perform switching to test whether linear MSP switching works
Prerequisites
Context
NOTE
The external switching for MSP protection includes: lockout, forced switching, manual switching and
exercise switching.
n The exercise switching is used to test the APS protocol. In fact services will not be switched to the
protection section, and only the calculation result of the protocol is displayed.
Procedure
Step 1 Select Conguration > Protection View from the Main Menu. Select Protection View >
SDH Protection Subnet Maintenance in the Protection View.
Step 2 Select the linear MSP from the protection subnet list.
Step 3 Right-click the desired NE and select an ofce direction to switch or lock. The Conrm
NOTE
The ofce direction can be switched only when it is not locked.

----End

21.3.4 Performing SNCP Switching

On the T2000, you can perform or clear external switching for SNCP protection. In
deployment and commissioning, you can perform switching to test whether SNCP switching
Prerequisites
n The SNCP services must be congured.
Context
NOTE
The external switching for SNCP protection includes: lockout, forced switching and manual switching.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > SNCP Service Control from the
Function Tree.
Step 2 Select the service in Working Serviceand double-click on the Current Status. Select the
switching or lock operation.
NOTE
The service can be switched only when it is not locked.
Step 3 A prompt appears telling you that the operation was successful. Click OK.
----End
21.3.5 RPR Protection Switching Priority

RPR protection switching is triggered by automatic switching conditions and external
switching requests. Automatic switching is triggered by signal failure and signal degrade.
External switching is performed by the user by issuing an external switching command, and
thus brings a status change of the RPR. External switching includes forced switching, manual
switching and clear of switching.
For RPR protection, the following switching requests can bring a status change of the RPR.
See the following table for their switching (or preemption) priorities.
NOTE
n In the following table, the switching priorities are given in a descending order, that is, FS has the
highest priority, and MS has the lowest. The forced switching and manual switching can be cleared
as needed.
n External commands are issued on the T2000. After the execution of a command, the NE keeps this
request until the command is cleared or preempted by another command with a higher priority. If there
is a switching request with a higher priority in the network, the external command cannot be actually
issued, and thus the NE loses this external command request. An external command can be cleared
only when the clear request is performed in the same direction on the NE as the switching request.

Table 21-2 RPR Protection Switching Priorities

1 FS Forced Switching An external
command, or signal
failure on the RPR
protection channel
2 SF Signal Failure An external
command
3 SD Signal Degrade An external
command
4 MS Manual Switching Signal failure on
a span of the RPR
working channel

On the T2000, you can perform or clear external switching for an RPR node. In deployment
and commissioning, you can perform switching to test whether RPR protection switching
Prerequisites
n The RPR protocol must be enabled .
Context
NOTE
The external switching for RPR protection includes: forced switching and manual switching.
Procedure
Step 1 In the NE Explorer, select a board and select Conguration > RPR Management > RPR
Protection from the Function Tree.
Step 2 Select the services to be switched, clickSwitch Request, and select Forced Switching,
Manual Switching or Clear as required. The Conrm dialog box is displayed.
Step 3 Click OK.
----End

On the T2000, you can perform or clear external switching for an RPR ring network. In
deployment and commissioning, you can perform switching to test whether RPR protection
switching works properly. In fault maintenance, you can perform this operation for fault
location.

Prerequisites
n The RPR ring network must be created.
n The RPR protocol must be enabled .
Context
NOTE
The external switching for RPR protection includes: forced switching and manual switching.
Procedure
Step 1 Select Conguration > RPR > Management from the Main Menu. Click the Node
Information tab.
Step 2 Click Query to query eastbound and westbound switching status of the RPR node.
Step 3 In the node list, select a node to switch. Right-click this node and select an eastbound or
westbound switching operation from the shortcut menu.
----End
21.3.8 Performing 1+1 Board Protection Switching

On the T2000, you can perform or clear protection switching for a board, including the SCC
board, the cross-connection board and the clock board. In deployment and commissioning,
you can perform switching to test whether board protection switching works properly. In fault
maintenance, you can perform this operation for fault location.
Prerequisites
n The cross-connect board or the clock board must be created.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > Board 1+1 Protection from the
Function Tree.

Step 2 Right-click the protection group and select the switch operation. The Conrm dialog box is
displayed.
Step 4 Click Query to query the status.
----End

On the T2000, you can perform or clear switching for a TPS protection group of PDH boards.
In deployment and commissioning, you can perform switching to test whether TPS switching
Prerequisites
n The TPS protection group must be created.
Procedure
Step 1 In the NE Explorer, click the NE and select Conguration > TPS Protection from the
Function Tree.
Step 2 Right-click the protected unit and select the switching operation.
Step 4 Click Query to query the status.
----End
21.3.10 Performing Board-Level Protection Switching for Data

Service Boards
On the T2000, you can perform or clear switching for board-level protection of data service
boards. In deployment and commissioning, you can perform switching to test whether
board-level protection switching for data service boards works properly. In fault maintenance,
you can perform this operation for fault location.
Prerequisites
n The board-level port protection group must be created.
Procedure
Function Tree.
Step 2 Right-click a protection group and select a switching operation from the shortcut menu.
Step 3 Click OK.
A prompt appears telling you that the operation was successful. Click Close.
----End

21.4 Resetting Boards

You can reset a board on the T2000 by following the instructions below.
21.4.1 Reset
Reset is a protection scheme for applications and data les on equipment. When a board is not
running properly, you can reset the board so that it returns to the normal state. Reset includes
warm reset and cold reset. Cold reset takes more time than warm reset. After a board is reset,
the data on the board will not be lost, but the reset may interrupt the service.
21.4.2 Resetting the SCC Board
Use this procedure to reset the SCC board on the T2000. Resetting the SCC is a maintenance
method in the case of improper SCC working status.
21.4.3 Resetting a Non-SCC Board
Use this procedure to reset a non-SCC board on the T2000. Resetting the SCC is a maintenance
21.4.1 Reset
Reset is a protection scheme for applications and data les on equipment. When a board is not
running properly, you can reset the board so that it returns to the normal state. Reset includes
warm reset and cold reset. Cold reset takes more time than warm reset. After a board is reset,
the data on the board will not be lost, but the reset may interrupt the service.
NOTE
On the T2000 you can warm reset or cold reset a board.
n Warm reset restores the applications and data to the normal state before warm resetting. Warm
reset usually does not affect the running services.
n Cold reset restores the applications and data to the normal state before CPU power failure. Warm
reset usually affects the running services.
21.4.2 Resetting the SCC Board

Use this procedure to reset the SCC board on the T2000. Resetting the SCC is a maintenance
Prerequisite
Context
NOTE
Neither warm reset nor cold reset of the SCC affects the service, unless protection switching occurs in the
network. When the SCC is being reset, however, network communication will be interrupted temporarily
until the SCC returns to the normal state. You can reset the SCC in the following three ways:
n Warm or cold reset the SCC through the T2000.
n Cold reset the SCC by plugging it.
n Cold reset the SCC by pushing the Reset button on the SCC.
Procedure
Step 1 Double-click an NE on the Main Topology and the Slot Layout is displayed.
Step 2 Right-click the SCC and select Cold Reset or Warm Reset from the shortcut menu.
Step 3 Click Close in the prompt dialog box.
----End

21.4.3 Resetting a Non-SCC Board

Use this procedure to reset a non-SCC board on the T2000. Resetting the SCC is a maintenance
Prerequisite
Context
NOTE
Warm reset usually does not affect the service, but cold reset usually does.
You can reset a non-SCC board in the following two ways:
n Warm or cold reset the board through the T2000.
n Cold reset the board by plugging it.
Procedure
Step 1 Double-click an NE on the Main Topology and the Slot Layout is displayed.
Step 2 Right-click a non-SCC board and select Cold Reset or Warm Reset from the shortcut menu.
Step 3 Click Close in the prompt dialog box.
----End
21.5 Performing Remote Maintenance

You can perform remote maintenance on the T2000 by following the instructions below.
21.5.1 Remote Maintenance

Remote maintenance is to monitor and maintain remote equipment through the T2000. It is
a common maintenance method for remote fault location and periodical check. When the
equipment is faulty, remote maintenance helps the user to locate and solve the problem in
time. Remote maintenance is also used for periodical check of remote equipment so that the
equipment security is guaranteed. Remote maintenance can be enabled in the T2000.
2.4.121.5.2 Enabling a Remote Maintenance User
The remote maintenance user is an NM user with which the remote maintenance client logs in
to the T2000 server. The remote maintenance user is disabled by default. Therefore, you need
to enable the remote maintenance user before performing remote maintenance.
21.5.3 Performing Remote Maintenance
Use this procedure to perform remote maintenance through the T2000.
21.5.1 Remote Maintenance

Remote maintenance is to monitor and maintain remote equipment through the T2000. It is
a common maintenance method for remote fault location and periodical check. When the
equipment is faulty, remote maintenance helps the user to locate and solve the problem in
time. Remote maintenance is also used for periodical check of remote equipment so that the
equipment security is guaranteed. Remote maintenance can be enabled in the T2000.
The Figure 21-1 shows the networking of remote maintenance.

Figure 21-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.
21.5.2 Enabling the Remote Maintenance User

The remote maintenance user is an NM user with which the remote maintenance client logs in
to the T2000 server. The remote maintenance user is disabled by default. Therefore, you need
to enable the remote maintenance user before performing remote maintenance.
Prerequisite
You must be the user admin.
Procedure
Step 2 Set the Disable/Enable parameter to Enable. Also set the other attributes of the remote
maintenance user.
Step 3 Click Apply.
Step 4 Click Set Password to set the remote maintenance user password.
Step 5 Click OK.
----End

21.5.3 Performing Remote Maintenance

Use this procedure to perform remote maintenance through the T2000.
Prerequisites
n The communication between the remote maintenance terminal and the T2000 server
must be set up.
Context
NOTE
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\cmdclient.bat le (for Windows)
or the /T2000/cmdclient/cmdclient.sh le (for UNIX).
Step 2 To log in to the T2000, enter the remote maintenance user password and the T2000 server IP
address. After successful login, the NEs managed by the T2000 server 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 the host commands for the
maintained equipment), and click Send to send the command to the NE.
Step 5 When the remote maintenance is complete, select Remote Maintenance Report > Create
to create a remote maintenance report. The remote maintenance report is saved in the
T2000\server\nemml\rm directory of the T2000 server.
----End

Operator Guide 22 Loading Software and Managing Conguration Data
22 Loading Software and

Managing Conguration Data
About This Chapter

The loading software function of the T2000 upgrades and downgrades the NE software
and board software. The conguration data management function of the T2000 backs up
or restores NE data.
22.1 Loading NE Software

The software types that can be loaded include Extbios, Nesoft, Fpga and Ini. The loading
process is the same for all types. For NEs of optical software platform 5.00.3 version or
above, the auto type is included in the loading software types. The auto type means the T2000
automatically identies the software types. Choose the auto type if this type is included in the
NE loading types. When choosing the auto type, you can choose les of nesoft, extbios, fpga
and ini types at the same time to load in batch. But if either Extbios, Nesoft, Fpga or Ini type
is specied, you can load only one le each time. NE software can be batch loaded, which
supports only those NEs on the optical software platform.
22.2 Loading Board Software
The types of board software that can be loaded include Bdsoft/Extbios/Ini, Fpga and OnlyFpga.
The loading process of all types is the same. For NEs of optical software 5.00.3 version or
above, the auto type is included in the loading software types.The auto type means the T2000
automatically identies the software types. Choose the auto type if an NE has this type. When
choosing the auto type, you can choose les of nesoft, extbios, fpga and ini types at the same
time to load in batch. But if either the Extbios, Nesoft, Fpga or ini type is specied, you
can load only one le each time.
22.3 Loading Patches Software
This function of the T2000 can load patches for the SCC board or other boards. To load
patches, the NE must run on OSP07 or a higher version.
22.4 Backing Up Conguration Data
Use this procedure to back up NE conguration data to a data conguration le on the
computer where the T2000 server or FTP server resides. So the data can be restored safely
and quickly in case of accidental data loss.
22.5 Restoring Conguration Data
Use this procedure to restore conguration data in the NE from the backup le.
22.6 Backing Up Database Package
The equipment in OSP platform supports database packet backup.This function backs up the
database le in an NE as a database packet on the computer where the T2000 server or FTP
server resides. So the data can be restored safely and quickly in case of accidental data loss.
22.7 Restoring Database Package
This function restores database package from the computer to the NE. The restoration process
includes copying and activating. Copying supports rollback.

22 Loading Software and Managing Conguration Data Operator Guide
22.8 Testing LED Indicators

This function tests LED indicators on boards. The user can select a board to start test or
stop test.
22.9 Setting FTP Parameters
The T2000 use FTP protocols to upload and download. The FTP Server is stopped by default.
You need to set FTP parameters after starting the FTP Server rst.

22.1 Loading NE Software

The software types that can be loaded include Extbios, Nesoft, Fpga and Ini. The loading
process is the same for all types. For NEs of optical software platform 5.00.3 version or
above, the auto type is included in the loading software types. The auto type means the T2000
automatically identies the software types. Choose the auto type if this type is included in the
NE loading types. When choosing the auto type, you can choose les of nesoft, extbios, fpga
and ini types at the same time to load in batch. But if either Extbios, Nesoft, Fpga or Ini type
is specied, you can load only one le each time. NE software can be batch loaded, which
supports only those NEs on the optical software platform.
Prerequisites
n The related NE must be created in the T2000.
n The computer where the T2000 is installed must communicate with the NE correctly.
Context
n When loading NE software to upgrade or degrade, perform activation after the above
types of software are all loaded.
n For NEs that have two sets of NE software, NE software is loaded as standby NE software
automatically. After it is activated, the newly loaded NE software will become the
working software.
n Before activating the NE, make sure the software that the NE needs is completely loaded.
n If an FPAG le is loaded to two areas of the same NE, this le needs not be activated
during the second loading. In this way, the impact on the services caused by activation is
lessened.
n Loading NE software is only applicable to the loading of the active system control and
communication (SCC) board software. Through "Load Board Software" to load the
standby SCC board software.
n In case of dual SCC boards, load and activate the standby SCC board, and then the
active SCC board.
n Five NEs at most are allowed to load NE software at the same time, and in this case, the
NEs are activated one by one only after loading NE software is complete for all of them.
n In the process of loading NE software, make sure the T2000 and the gateway NE are
connected properly. Otherwise, the T2000 would run wrong.
n For the degradation of the NE software, refer to the appropriate Upgrade Instructions
of the related products.
n If the T2000 is restarted when the NE software is loaded but deactivated, the NE software
needs to be re-loaded and activated.Loaded NE software can be activated by switching
the running area.
Procedure
Step 1 Choose the Load Software > Load NE Software from the Main Menu, and those NEs that
have been added in the Object Tree are displayed.
Step 2 Right-click an NE in the NE list and choose Login NE.
Step 3 Select an NE and then click the double-right-arrow button. Related information of this NE
is displayed in the Operation List.
Step 4 Select this NE in the Operation List, and choose a software type in the Software Type eld. If
batch loading is supported, you can choose Auto.

Step 5 Right-click the File eld in the Operation List, and select Select File. If Auto is selected for
software type, you can also select Add File here. The Open File dialog box is displayed. You
can select multiple les if batch loading is supported.
Step 6 Select software to load, and click Open. The user can view the le by clicking the le name
in the information table.
Step 7 Click the Start button to start loading software. The copying progress is displayed in the
interface, and the state is "Copying". When the state becomes "Unactivated", the loading is
complete. The user can click the Stop button to stop loading.
Step 8 Repeat Steps 4 through 7 to load other software.
Step 9 After the loading is complete, click Activate and the NE state becomes "Activating". The
settings take effect after the NE is restarted. The NE state now becomes "Normal".
NOTE
n The NE software state returns to "Normal" after it is activated. The normal state indicates the
software is running normally, but services may not be running normally.
n Loading NE software can be performed on more than one NE, but only one SCC board can be
activated (including a warm or cold reset). Activating (including warm or cold resetting) cannot be
performed along with copying.
n The activation of NE software is controlled by the user. The user performs the activate (including a
warm or cold resetting) operation, the T2000 issues the command to the NE. The T2000 can prevent
only the operation failure caused by ECC interruption. If the T2000 does not allow activation of
the SCC board, it returns an error. For example, the T2000 issues the cold resetting command to
a GNE. During the process of cold resetting the GNE, the communication between the T2000 and
non-gateway NEs is interrupted. Therefore, the T2000 allows only one NE to be activated at a time.
----End
22.2 Loading Board Software

The types of board software that can be loaded include Bdsoft/Extbios/Ini, Fpga and OnlyFpga.
The loading process of all types is the same. For NEs of optical software 5.00.3 version or
above, the auto type is included in the loading software types.The auto type means the T2000
automatically identies the software types. Choose the auto type if an NE has this type. When
choosing the auto type, you can choose les of nesoft, extbios, fpga and ini types at the same

time to load in batch. But if either the Extbios, Nesoft, Fpga or ini type is specied, you
can load only one le each time.
Prerequisites
n The related board must be created in the T2000.
n The computer where the T2000 is installed can communicate with the NE correctly.
Context
n Before activating the NE, make sure the software of the NE needs is completely loaded.
n Hard resetting is required when you load FPGA. In this case a transient break for service
may occur.
n For the multi-in-one SCC board, only the software of the SCC board rather than the logical
board on it needs to be loaded. Otherwise, the system prompts for an operation failure.
n If the T2000 is restarted when the NE software is loaded but deactivated, the software
needs to be re-loaded and activated.
Procedure
Step 1 Choose Load Software > Load Board Software from the Main Menu, and those NEs that
have been added in the left-hand Object Tree are displayed.
Step 2 Right-click an NE in the NE list and choose Login NE.
Step 3 Right-click the NE and choose Query Board.
Step 4 Select a board and then click the double-right-arrow button. Related information of this board
is displayed in the Operation List.
Step 5 Select this board in the Operation List and select a software type from the Software Type eld.
Step 6 Right-click the File eld in the Operation List and choose Select File. If Auto is selected for
the software type, you can also select Add File here. The Open File dialog box is displayed.
For batch loading, the user can select multiple les at one time.

Step 7 Select software to load and click Open. The user can view the selected le by clicking the
le name in the information table.
Step 8 Click the Start button to start loading software. The copying progress is displayed in the
interface, and the state becomes "Copying". When the state becomes "Unactivated", the
loading is complete. The user can click the Stop button to stop loading.
Step 9 Repeat Steps 5 through 8 to load other related software.
Step 10 After loading succeeded, click Activate to activate loaded software. Click OK when the
following prompt is displayed. And the board state becomes "Activating".
NOTE
n During the activation, the board is cold or warm reset. If the load type is "Fpga", the board is cold
reset. If the load type is not "Fpga", there is a warm resetting attempt for the board. If the warm
resetting fails, the board is then cold reset. After the reset, the board state returns to "Normal". If
the board returns to “Normal” after the activation completes, the software can function normally.
However, whether services run normally cannot be guaranteed.
n Only one board can be cold reset at a time and a cold reset cannot be performed along with copying.
However, multiple boards can be warm reset at a time and a warm reset can be performed along
with copying.
n The activation of board software is controlled by the user. The user performs the activate (including a
warm or cold resetting) operation, the T2000 issues the command to the NE. The T2000 can prevent
only the operation failure caused by ECC interruption. If the T2000 does not allow activation of
the SCC board, it returns an error. For example, the T2000 issues the cold resetting command to
two cross-connect boards on the same NE, and thus NE communication is interrupted. During the
interruption, the T2000 fails to issue commands to other boards on the NE. Therefore, the T2000 does
not allow two boards to be cold reset at a time.
----End

22.3 Loading Patches Software

This function of the T2000 can load patches for the SCC board or other boards. To load
patches, the NE must run on OSP07 or a higher version.
Prerequisites
n The related board must be created in the T2000.
n The loading patch software version must match that of the NE software. Otherwise, the
loading operation fails.
Procedure
Step 1 Choose Load Software > Load Patch Software from the Main Menu, and those NEs that
have been added in the left-hand Object Tree are displayed.
Step 2 Right-click an NE in the NE list and choose Login NE from the shortcut menu.
Step 3 Right-click the NE in the NE list and choose Query Board.
Step 4 Select a board in the NE list and then click the double-right-arrow button. Related information
of this board is displayed in the Operation List.
Step 5 Select this board in the Operation List. Right-click the Patch File eld and choose Select
File. The Open File dialog box is displayed.
Step 6 Select patches to load, and click Open.
Step 7 Click the Start button to start loading patches. The copying progress is displayed in the
interface, and the NE state becomes "Copying". When the NE state becomes "Normal", the
copying is complete. You can click the Stop button to stop copying.
Step 8 After loading succeeded, click Activate to display the Activate Patch Software dialog box.
Click Load to load the patches. You can perform such operations as "Run", "Trial Run" and
"Delete".

Step 9 Click Exit to exit the "Activate Patch Software" dialog box.
----End
22.4 Backing Up Conguration Data

Use this procedure to back up NE conguration data to a data conguration le on the
computer where the T2000 server or FTP server resides. So the data can be restored safely
and quickly in case of accidental data loss.
Prerequisites
n The NE must be created in the T2000.
n The NE must communicate with the T2000 correctly.
n The equipment being operated on must support this function. For detailed information,
refer to the upgrade instruction of related equipment.
Procedure
Step 1 Choose Load Software > Backup/Restore Conguration Data from the Main Menu.
Step 2 Right-click an NE in the Object Tree and choose Login NE. The NE icon turns green.
Step 3 In the Object Tree, select the NE and click the double-right-arrow button. The NE information
is displayed on the right-hand pane of the interface. You can select more than one NE at
the same time.
Step 4 Select an entry in the Operation List. Select Backup from the Backup/Restore drop-down list.
Step 5 Right-click the File eld and choose Select File. The Open File dialog box is displayed.
Step 6 Specify the directory of the backup le, and click Open. If the directory is specied, the system
names the backup le automatically. You can select more than one NE at the same time. In this
case, the backup le directory is generated automatically by the system and cannot be modied.

Step 7 Click Start to back up the data (of one or more NEs). A progress bar displays. The NE state
is "Copying State" when backing up NE data. When it becomes "Normal state", the data
are backed up. IF exception occurs in the backup process, such as interruption of network
communication, the NE state changes to "Abnormal State". The User can click Stop to stop
the backup process. If the operation succeeds, the NE state changes to "Normal State".
----End
22.5 Restoring Conguration Data

Use this procedure to restore conguration data in the NE from the backup le.
Prerequisites
n The NE must be created in the T2000.
n The NE must communicate with the T2000 client correctly.
n The conguration data le to be restored must be prepared. Only the data backed up from
the specied NE can be restored to the NE.
Context
Before using the conguration data le to restore the NE, make sure the conguration data le
is correct; otherwise, it will interrupt services.
Procedure
Step 1 Choose Load Software > Backup/Restore Conguration Data from the Main Menu. The
NEs that have been added in the Object Tree are displayed in the Object Tree.
Step 2 Right-click an NE in the Object Tree and choose Login NE.
Step 3 In the Object Tree, select an NE and click the double-right-arrow button. The NE information is
displayed on the right side of the interface. You can select more than one NE at the same time.
Step 4 Select an entry. Double-click the Backup/Restore eld and select Restore.
Step 5 Right-click the File eld and choose Select File. The Open File dialog box is displayed.
Step 6 Specify the le to restore and click Open. You can select more than one NE at the same time
and specify the same backup le for them.

Step 7 Click Start. The process of restoring the conguration data interrupts services. The system
displays a dialog box to ask you whether to continue the operation. If you click No, the
operation of restoration stops. If you click Yes, the NE state is displayed as "Copying State".
Once the progress bar is full, the NE state is switched to "Unactivated State". The system
automatically issues commands to activate the NE, and the NE state is switched to "Activating
State". Note that the process interrupts service. After restoration, the status is displayed as
"Normal State".
----End
22.6 Backing Up Database Package

The equipment in OSP platform supports database packet backup.This function backs up the
database le in an NE as a database packet on the computer where the T2000 server or FTP
server resides. So the data can be restored safely and quickly in case of accidental data loss.
Prerequisites
n Create an NE that supports the HFCP protocol on the T2000.
n The computer where the T2000 is installed must communicate with the NE normally.
n If the FTP protocol is applied, the FTP server must be started. If the FTP server owned by
the T2000 is used, the status is displayed in the toolbar.
Procedure
Step 1 Choose Load Software > Backup/Restore Database Package from the Main Menu. The
Step 3 Select a logged-in NE and click the double-right-arrow button to transfer it to the right-hand
Operation List. You can select more than one NE at the same time.
Step 4 Select an NE in the Operation List, and select Backup from the Backup/Restore drop-down
list.
Step 5 Select FTP or HFCP from the Protocol drop-down list.
Step 6 Click the button behind File eld.
NOTE
n If the FTP protocol is applied, the FTP File Settings dialog box is displayed. Choose a directory on
FTP Server as the backup directory.
n If the HFCP protocol is selected, the Open File dialog box is displayed. Choose a directory as
the backup directory.
Step 7 Click the Start button to start backing up. During the process, you can execute "rollback"
operation.

NOTE
n When backup begins, the NE changes to the copying state, and Step 4 through 8 cannot be performed.
The progress bar displays the backup progress, and the progress bar in the operation results list
follows.
n If the Start button is clicked, the T2000 creates the following directory in the user dened path: user
dened path/NE-Name/NE-Name_YYYYMMDD_hhmmss/. The NE-Name presents the NE name.
n If the user dened path does not exist, the T2000 reports the error that the path does not exist.
n If the NE-Name or NE-Name_YYYYMMDD_hhmmss directory does not exist, the T2000 creates
the parameters. If the directory fails to be created, the T2000 reports an error.
n If the user dened path or the NE name is too long, a corresponding error is displayed. In the longest
path, 40 characters must be reserved for the name of the le that saves the database backup.
Step 8 A message is displayed in the operation results list saying backing up succeeded.
----End
22.7 Restoring Database Package

This function restores database package from the computer to the NE. The restoration process
includes copying and activating. Copying supports rollback.
Prerequisites
n Create an NE that supports the HFCP protocol on the T2000.
n The computer where the T2000 is installed can communicate with the NE normally.
n The database package to be restored is prepared. Only the data backed up from the
specied NE can be restored to the NE.
Procedure
Step 1 Choose Load Software > Backup/Restore Database Package from the Main Menu. The
Step 3 Select a logged-in NE and click the double-right-arrow button.
Step 4 Select an NE in the Operation List, and select Restore from the Backup/Restore drop-down
list.
Step 5 Select FTP or HFCP from the Protocol drop-down list.
Step 6 Click the button behind File eld.
NOTE
n If the FTP protocol is applied, the FTP File Settings dialog box is displayed. Choose a le on
the FTP Server to restore.
n If the HFCP protocol is selected, the Open File dialog box is displayed. Choose a le to restore.

Step 7 Click the Start button to start restoration.
NOTE
When restoration begins, the NE changes to the copying state, and Step 4 through 8 cannot be performed.
The progress bar displays the backup progress, and the progress bar in the operation results list follows.
Step 8 A message saying restoration succeeded is displayed in the operation results list.
Step 9 Select the restored NE and click Activate. Then click OK when the prompt message is
displayed.
NOTE
The progress bar shows the activating progress in real time, and the progress bar in the operation results
list follows.
Step 10 The NE returns to normal state after activation.

----End
22.8 Testing LED Indicators

This function tests LED indicators on boards. The user can select a board to start test or
stop test.
Prerequisites
n The NE for login must be created in the T2000.
n The NE or board must support LED indicator test.
Procedure
Step 1 Choose Load Software > LED Test from the Main Menu.
Step 2 In the Object Tree, add an NE that supports LED test, and query the boards of the NE.
Step 3 Select the boards that support LED test, and then click the double-right-arrow button. The
selected boards are displayed in the Operation List.
Step 4 Select a board, for example, the 17-ssn1nscc board of NE9-36. Right-click the board and
choose Start LED Test.

Step 5 The test information is displayed in the operation results. If the LED works correctly, the LED
indicators on the board will icker regularly from red to yellow and to green.
Step 6 Right-click the board and select Stop LED Test to stop the test. Related information is
displayed in the operation results. The board stops ickering.
----End
22.9 Setting FTP Parameters

The T2000 use FTP protocols to upload and download. The FTP Server is stopped by default.
You need to set FTP parameters after starting the FTP Server rst.
Prerequisite
Restart the FTP Server after setting FTP parameters successfully. Before setting parameters,
make sure T2000 is not use FTP translation function.
Context
The FTP Server status is displayed on the top of the dialog box.
means the FTP Server is running, and means the FTP Server stopped.
Procedure
Step 1 Choose Load Software > Set FTP Parameters from the Main Menu, and the FTP Properties
Settings dialog box is displayed.
Step 2 Enter the value of the properties. After the settings, and click Start Up.
Step 3 A prompt dialog box is displayed. Click Yes. When the FTP Properties Setting dialog box is
opened for the rst time, both the password and the root directory are default to be empty.
Step 4 Click OK when the following prompt is displayed. Then restart the T2000, because the
settings take effect only when the T2000 is restarted.
----End

Operator Guide A Mutual Exclusion List for Multiclient Operations
A Mutual Exclusion List

for Multiclient Operations
The mutual exclusion list for multiclient operations is given below.
Figure A-1 Mutual exclusion list for multiclient operations
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.
Issue 01 (2006-09-15) Huawei Technologies Proprietary A-1

Operator Guide B Glossary
This document denes the following terms:

B Glossary
A
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.
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.
Alarm correlation analysis In the case alarm2 is raised within ve seconds
after alarm1 is raised, and alarm2 complies with the
conditions dened in the alarm correlation analysis
rule, you can either suppress the alarm2 or raise its
severity level according to the behavior dened in the
alarm correlation rule. Such a process is called alarm
correlation analysis.
Alarm correlation rules Rules that dene the situations where two or more
alarms are regarded as relevant alarms, and the ways the
T2000 processes relevant alarms.
Alarm lter Alarms are detected and reported to the T2000, and
whether the alarm information is displayed and stored is
decided by the status of the alarm lter. An alarm with
the ltering status set to "Filter" is not displayed and
stored on the T2000, but is monitored on the NE.
Alarm indication On the cabinet of an NE, there are three indicators with
different colors indicating the current status of the NE.
You can stop the NE alarm indication through the T2000.
Alarm reversion mode After a service is accessed or a fault is removed, whether
the port is automatically restored to the normal status
depends on the alarm reversion mode of this NE. There
are three alarm reversion modes: automatic, manual and
not-to-revert.
Alarm reversion For the port that has already been congured but not
actually loaded with services, this function can be used
to avoid generating relevant alarm information, thus
preventing alarm interference.
Issue 01 (2006-09-15) Huawei Technologies Proprietary B-1

B Glossary Operator Guide
Alarm severity According to ITU-T recommendations, the alarm is

classied into four severities: Critical, Major, Minor,
Warning.
Alarm suppression The suppressed alarm of a specic object is not reported.
The object here may be the networkwide equipment, a
specic NE, a specic board and even a specic function
module of a specic board.
Alarm A visible or an audible indication to notify the person
concerned that a failure or an emergency has occurred.
See also Event.
APS Automatic Protection Switching. Automatic switching
of a failed communication route to a workable one as a
mean of enhancing system reliability.
ATM protection group An ATM protection group refers to the logically bound
ATM VP network or subnetwork connections that share
the same physical transmission channel. In the VP group
(VPG), a pair of VP connections (working connection
and its protection connection) is used for monitoring
the automatic protection switching, called monitoring
connections (APS VPCs). If the monitoring connections
switch over, the whole VPG will switch over to quicken
the ATM protection switching (as quick as the protection
switching of the SDH layer.
Attribute Property of an object.
B
Binding In virtual concatenated payload conguration,
designating one binding number to identify the VC4s of
the same virtual concatenated payload is called "bind".
If a fault occurs to one of the bound services, all bound
services will switch as a whole.
Bit error alarm threshold When the bit error reaches a specic 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.
Board View The Board View displays the ports and the paths in
different colors depending on their current status, with
legend and description illustrated aside.
C
Client A kind of terminal (PC or workstation) connected to a
network that can send instructions to a server and get
results through a user interface. See also server.
Clock View The Clock View provides a visible platform to enable:
1. NE clock settings
2. Networkwide clock synchronization status query
3. Clock tracing and search functions
B-2 Huawei Technologies Proprietary Issue 01 (2006-09-15)

Concatenation In practice, it may be necessary to transmit the payload

bigger than the VC4 capacity (for instance, the GE
signal). Currently, the concatenated service can combine
the payloads of multiple successive (4, 8, 16 or 64)
AU-4 services and use the same set of higher order path
overhead and AU-4 pointer value to form AU4-xC (x=4,
8, 16 or 64), which is multiplexed, cross-connected and
transmitted in the network as a single entity.
Conguration data The data that congures the NE hardware for
coordination between this NE and other NEs in the
entire network and operation of specied services.
Conguration data is the instruction le of NEs, and
it is the key for efcient network running. The typical
conguration data includes board conguration, clock
conguration and protection relationship.
Congure To set the basic parameters of an operation object.
Connection A "transport entity" which consists of an associated
pair of "unidirectional connections" capable of
simultaneously transferring information in opposite
directions between their respective inputs and outputs.
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-dened view is a subset on the Main Topology.
Included network entities can be NE, T2000, 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.
D
DCC Within an STM-N signal there are two DCC channels,
one is the 192 kbit/s DCC-R channel composed of
bytes D1–D3, and the other is the 576 kbit/s DCC-M
channel composed of bytes D4–D12. All NEs can
communicate with one another through the DCC-R. The
DCC-M is not the regenerator section overhead and does
not support communications among regenerators, and
it is used to support communication channels of more
universal purpose. For example, it supports TMN as a
physical channel of ECC.
DDF Digital Distribution Frame. A frame which is used to
transfer cables.
Discrete service Cross-connections that cannot form trails on the T2000.

DNI Dual Node Interconnection. The protection mode

dened in G. 842 Recommendation for the inter-ring
service . By using the recommended protection modes,
the protection of the interconnecting service between
two ring networks composed of the devices from
different manufacturers and in different protection
modes can be realized. Moreover, in case of ber failure
or node failure, services can also be protected.
Domain The domain of the T2000 species the scope of address
or functions which are available to a certain user.
E
ECC Embedded Control Channel. An ECC provides a logical
operations channel between SDH NEs, utilizing a data
communications channel (DCC) as its physical layer.
Equipment set An aggregate of multiple managed equipment.
Equipment set facilitates the user authority management
on equipment in the management domain of the T2000.
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).
Exercise switching This command tests whether a switching protocol can
work normally without completing the actual switching
operation.
Extended ID The serial number of a subnetwork where an NE resides,
which is usually used to distinguish different network
segments in a WAN. An extended ID and an ID form
the physical ID of an NE.
F
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.
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.
Fiber cable The general name of optical ber and cable. The optical
ber transmits optical signals, while the cable transmits
electrical signals.
Forced switch This command performs the ring switch from working
channels to the protection channels. This switch occurs
regardless of the state of the protection channels, unless
the protection channels are satisfying a higher priority
bridge request.
G

Gateway IP IP address is used for TCP/IP communication between

an NE and the T2000, 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 through an
Ethernet line or a serial port line. The non-gateway
NE communicates with the gateway NE through ECC
and communicates with the NMS through the gateway
NE. The gateway NE is a communication route that the
T2000 must pass through when managing the entire
network.
H
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 T2000
are called history performance data in a unied way.
I
IP address In the TCP/IP protocol, it is used to uniquely identify the
address of the communication port, which consists of
four bytes in decimal digits, for example, 129.9.161.55.
L
Label A mark on a cable, a subrack, or a cabinet for
identication.
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 LCT provides the user
with single-layer management network solutions to
the transmission network of up to ve NEs to realize
integrated management of multi-service transmission
network. Usually it uses the cross-over cable or serial
port cable to connect one NE, so as to congure and
maintain a single NE. See also T2000-LCT.
License A permission provided by a vendor to authorize the use
of specic functions of a product. Usually the license
consists of encrypted codes, and the operation authority
varies with different level of license.
Lock NE login This function prohibits the users at lower levels from
logging in NE and forces logged NE users with lower
level to log out.
Lock status The service will not be switched to the protection board
when fault occurs, if currently no switching takes place.
If currently the switching takes place, after the protected
board becomes normal, the service will not be switched
to the protected board either.
M

MAC port Media Access Control port. A media access control

port, such as the 8 ports of ET1.
Main Topology The default T2000 client interface, and all topology
management functions are accessed here.
Management ag 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 conguration function
performed at a node.
Management information The signal passing across an access point.
Manual switch When the protection channel is efcient and there is
no higher-level switching request, this mode switches
the service from the working channel to the protection
channel, thus testing whether network still has the
protection capability.
MO Managed Object. The management view of a resource
within the telecommunication environment that may be
managed via the agent. Examples of SDH managed
objects are: equipment, receive port, transmit port,
power supply, plug-in card, virtual container, multiplex
section, and regenerator section.
MS Multiplex Section. A multiplex section is the trail
between and including two multiplex section trail
termination functions.
MSP Multiplex section protection. The nodes online achieve
protection switching through the K1 and K2 bytes in the
multiplex section, including linear 1+1 MS protection
switching link, linear 1:n MS protection switching link,
dedicated MS protection ring and shared MS protection
ring.
N
NE database There are three types of database on NE SCC board as
following: (1) DRDB: a dynamic database in a dynamic
RAM, powered by battery; (2) SDB: a static database in
a power-down RAM; (3) FDB0, FDB0: permanently
saved databases in a Flash ROM. In efcient operation,
the NE conguration data is saved in DRDB and SDB
at the same time. Backing up an NE database means
backing up the NE conguration data from SDB to
FDB0 and FDB1.
NE Explorer NE Explorer is the main operation interface of the
T2000. For easy navigation, the NE Explorer window
presents an expandable directory tree (Function Tree) in
the lower left pane. The conguration, management and
maintenance of the equipment are accessed here.

NE ID In a network, each NE corresponds to a unique identier,

that is, the NE ID. In the OptiX transmission equipment,
it is specied 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 sub-network
number. The extended ID is usually used to identify
different sub-networks.
NE Panel NE Panel displays subracks, boards, and ports in
different colors depending on their status. In the
T2000, most equipment conguration, monitoring, and
maintenance are performed in the NE Panel window.
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.
Network segment The range of IP addresses in which the gateway NE
will operate.
NM Network Management. In the telecommunication
management network structure, the T2000 is located
between the NE level and network level, which can
supports all functions at NE level and part of the network
level management functions. See also T2000.
NNI Network Node Interface. NNI identies the interface
between the ATM network nodes. 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.
O
Online help An indexed collection of information on all aspects of
the T2000. They can be accessed at any time from the
Help menu or by pressing the F1 key.
P
Pane A major separate area of a window or dialog box,
usually used for display rather than data entry.
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 matrix sends the signal
dually sent from the opposite end to the tributary board
through the active and standby buses, and the hardware
of the tributary board will selectively receive the signal
from the two groups of buses automatically according to
the AIS number of the lower order path.
Path A trail in a path layer.

Performance register Performance register is the memory space for

performance event counts, including 15-min current
performance register, 24-hour current performance
register, 15-min history performance register, 24-hour
history performance register, UAT register and CSES
register.
Performance threshold Performance events usually have upper and lower
thresholds. When the performance event count
value exceeds the upper threshold, a performance
threshold-crossing event is generated; when the
performance event count value is below the upper
threshold for a period of time, the performance
threshold-crossing event is ended. In this way,
performance jitter caused by some sudden events can
be shielded.
Private line Both communication parties are connected permanently.
Procedure A generic term for an action.
Process A generic term for a collection of actions.
Protection path A specic path that is part of a protection group and is
labeled protection.
Protection service A specic service that is part of a protection group and
is labeled protection.
Protection subnet The resources that form a protection subnetwork include
NEs and ber cables. The creation of the protection
subnetwork actually means that corresponding logical
system is congured for each NE by means of creating
the protection subnetwork, the optical interfaces
(or VC4) of each board are mapped into the logical
system, and then these independent logical systems are
connected with one another to form a complete network
structure.
Protection View The following functions are enabled in the Protection
View.
1. Searching, browsing, creating, setting and managing
the protection subnetwork.
2. Managing umbrella nodes and SDH NNIs.
R
Resource sharing Resource sharing means that a physical resource may
belong to two protection sub-networks.
Route The IP route selection is in table driving mode. In each
host and each router of the Internet, there is a routing
table that contains information about how the service
is transmitted from the source to the sink, providing a
basis for route selection. Ethernet static routing in ET1
refers to the mapping relationship between the Ethernet
port and the bound path. Its routing type includes port
routing and VLAN routing. Port routing: It means
conguring a route between the Ethernet port and the
bound path port, which is usually used for point-to-point
networking communication; VLAN routing: It means
conguring a route between the Ethernet port and the
bound path port based on the VLAN service. It can
be used exibly in point-to-point, point-to-multipoint
or multipoint-to-multipoint communication. The
implementation is to divide and converge the data

stream according to the VLAN ag of the packet. As

a VLAN ag can be added to the Ethernet port, the
equipment can be applied more exibly.
S
Script le It is the text le describing the physical information
and conguration information of the entire network,
including the NE conguration le, port naming le,
end-to-end conguration le, NE physical view script
le, NM information le and service implementation
data script le.
Script A list of instructions for performing a specic task or
action, written in a scripting language.
SD Signal Degrade. A signal indicating the associated data
has degraded in the sense that a degraded defect (DEG)
condition is active.
SDH NNI SDH Network Node Interface. It is applied to build
communications connection with the equipment beyond
the T2000 management area. 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 ber connection.
Search domain Search eld refers to the range of IP addresses being
searched.
Section A trail in a section layer.
Settings Parameters of an operation that can be selected by the
user.
Severity See Alarm Severity.
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.
Shortcut menu A menu that is displayed when right-clicking an
object’s name or icon. Also called a context menu.
SNCP node Set the SNCP node on the protection sub-network to
support sub-network connection protection that spans
protection sub-networks. The SNCP node of the ring
sub-network can support electric circuit dual feed and
selectively receive a time slot out of the ring, thus
implementing sub-network connection protection.
Spread type The spread type of ATM service includes point-to-point
(p2p) and point-to-multipoint (including p2mpRoot
and p2mpLeaf). The p2p spread type supports
real-time bi-directional communication service. The
two communication parties are in the same status
and participate the session actively. p2mpRoot and
p2mpLeaf belong to the point-to-multipoint spread
type. It supports point-to-multipoint multicast service.
During the creation of a point-to-multipoint (multicast)
connection, a connection to identify this group of
connections is necessary. This connection is a p2mpRoot
connection, while other connections are p2mpLeaf
connections. If there is a p2mpLeaf connection in
a group of connections, the p2mpRoot cannot be
deleted. To create a multicast connection, the p2mpRoot

connection must be created before the creation of

p2mpLeaf connection.
Subnet mask Also referred to as the network mask off code, it is used
to dene 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 num b er is used to differentiate the different
network sections in the sub-network conference.
Actually it is the rst 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.
Subnet Sub-network is the logical entity in the transmission
network and comprises a group of network management
objects. A sub-network can contain NEs and other
sub-networks. A sub-network planning can better the
organization of a network view.
Support The frame on the bottom of a cabinet, when installing
the cabinet on the antistatic oor.
T
T2000 The T2000 is a subnetwork management system
(SNMS). In the TMN architecture, the T2000 is located
between the NE level and network level, which can
supports all function of NE-level and part of the
network-level management functions. See also NM.
T2000-LCT A lite version of T2000. It is an element level
management system for the optical transmission
network. It can manage SDH, DWDM and Metro
optical transmission equipment. See also LCT.
TDA clock source TDA is short for Tone Data Access. For the 2500+ NE
equipment, it can be installed with the external TDA
board for which the clock source must be set so that the
TDA board can switch according to the set clock source
sequence when clock source switching occurs.
Topology The T2000 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.
Trail management function A network level management function of the T2000.
Through trail management, you can congure
end-to-end services, view graphic interface and visual
routes of a trail, query detailed information of a trail,
lter, 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 Trail View enables search, creation, conguration
and maintenance management functions on network
trails.

Trail A trail is a kind of transport entity, mainly engaged in

transferring signal from the input of the trail source
to the output of the trail sink, and monitoring the
integrality of the transferred signal. According to the
different levels of the trail, the trail includes various
types (OTS, OCH, OMS, SPI, RS, MS, VC4 server trail,
VC4, VC3 and VC12). Among them, OTS, OCH and
OMS represent the trails in a DWDM layer network.
For the ADM and TM equipment in the SDH network,
each optical ber connection corresponds to an SPI, RS
or MS trail, and a trail is the general name for service
carriers, including SDH and PDH services.
Tributary loopback A fault can be located for each service path by
performing loopback to each path of the tributary board.
There are three kinds of loopback modes: No loopback,
Outloop and Inloop.
U
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.
Unprotected Services transmitted through an ordinary way, once a
failure or interruption occurs, the data cannot be restored
for lack of protection mechanism.
Upload Report all or part of the conguration data of the NE to
the NM and overwrite the conguration data saved in
the NE layer on the NM side.
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.
User The user of the T2000 client, and the user and his/her
password dene the corresponding authority of
operation and management of the T2000.
V
VC4 loopback The fault of each VC4 path on the optical ber can
be located by setting loopback for each VC4 path of
the line. There are three kinds of loopback modes: No
loopback, Outloop, Inloop.
VC4 server trail The path rate of the VC4 server trail is 150. 336Mbit/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-ofce communication path. When
the VC4 server trail is congured, 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.

VCI The VCI, shorted for Virtual Channel Identier, occupies

16 bits in both NNI cell or UNI cell. It indicates the
virtual channel in the path. The VPI and VCI together
indicate a virtual connection.
Virtual NE Like a common NE, a virtual NE is also displayed
with an icon on a view, 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 sub-networks the T2000 cannot manage, or the
equipment is interconnected with other vendors’s
NEs for service conguration, the end-to-end service
conguration method and the trail management
capability are provided.
VLAN ID Namely, it is the virtual LAN identier. One Ethernet
port can support 4K VLAN routes, and one NE can
support up to 8K VLAN routes.
VPI The VPI, shorted for Virtual Path Identier, occupies 12
bits in the NNI cell, and 8 bits in the UNI cell.
W
Working path A specic path that is part of a protection group and is
labeled working.
Working service A specic service that is part of a protection group and
is labeled working.
WTR time A period of time that must elapse before a-from a fault
recovered-trail/connection can be used again to transport
the normal trafc signal and/or to select the normal
trafc signal from.
WTR Wait to Restore. This command is issued when working
channels meet the restoral threshold after an SD or SF
condition. It is used to maintain the state during the
WTR period unless it is pre-empted by a higher priority
bridge request.

Operator Guide C Acronyms and Abbreviations
C Acronyms and Abbreviations

A
AIS Alarm Indication Signal
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
AUX Auxiliary Equipment
B
BIOS Basic Input/Output System
C
CDE Common Desktop Environment
CRC Cyclic Redundancy Code
D
DCC Data Communication Channel
DCN Data Communication Network
DNI Dual Node Interconnection
E
ECC Embedded Control Channel
EMS Element Management System
EPL Ethernet Private Line
EPLn Ethernet Private LAN
EVPL Ethernet Virtual Private Line
EVPLn Ethernet Virtual Private LAN
F
FEC Forward Error Correction
G
GE Gigabit Ethernet
I
ID Identication/Identity
IP Internet Protocol
L
LCAS Link Capacity Adjustment Scheme
LCT Local Craft Terminal
Issue 01 (2006-09-15) Huawei Technologies Proprietary C-1

C Acronyms and Abbreviations Operator Guide
LSP Label Switching Path

M
MAC Media Access Control
MO Managed Object
MPLS Multi-Protocol Label Switching
MSP Multiplex Section Protection
N
NE Network Element
NM Network Management
NSAP Network Service Access Point
O
OSN Optical Switch Network
P
P2P Point To Point
PDH Plesiochronous Digital Hierarchy
PP Path Protection
PVP Permanent Virtual Path
R
RMON Remote monitoring
RPR Resilient Packet Ring
RSTP Rapid Spanning Tree Protocol
S
SDH Synchronous Digital Hierarchy
SMTP Simple Mail Transfer Protocol
SNCP Sub-Network Connection Protection
SSM Synchronization Status Message
T
TCM Time Compressed Multiplex
TDA Tone & Data Access Unit
TPS Tributary Protection Switching
U
UAT User Accepted Test
V
VB Virtual Bridge
VLAN Virtual Local Area Network
VPN Virtual Private Network
W
WAN Wide Area Network
WDM Wavelength Division Multiplexing
WTR Wait-to-Restore
C-2 Huawei Technologies Proprietary Issue 01 (2006-09-15)

Operator Guide Index
Index
A apply, 20-11
abnormal event create, 20-5
color, 20-7 alarm box
view, 20-29 mute alarm sound, 20-30
access control set alarm box parameter, 20-8
LCT access control, 2-36 turn off indicator, 20-30
serial port access control, 2-36 alarm correlation, 20-5
set NE Ethernet access, 2-35 alarm correlation analysis
adjust network, 17-1 create alarm correlation rule, 20-6
add node, 17-14 enable, 20-6
advanced maintenance for ASON control plane enable alarm correlation analysis, 20-6
ASON signaling maintenance, 18-60 alarm forwarding, 20-7
ASON switch controller maintenance, 18-61 alarm indicator
AIS, 20-13 alarm box, 20-30
alarm ASON
acknowledge, 20-28 Advanced Maintenance for ASON Control
AIS insertion, 20-13 Plane, 18-60
alarm forwarding, 20-7 ASON network
alarm reversion, 20-14 legend, 18-47
attribute template, 20-5 manage reserved resources, 18-48
automatic acknowledgement, 20-6 resource, 18-47
automatic synchronization, 20-6 view customisation, 18-47
check, 20-28 ASON trail
color, 20-7 create diamond trail, 18-17
dump condition, 20-9 view alarms and abnormal events, 18-44
report, 20-29 view performance monitoring data, 18-46
set alarm auto reporting, 20-11 ATM board
set alarm severity, 20-11 IMA group status, 20-45
set B1 alarm threshold, 20-12 IMA link status, 20-45
set B2 alarm threshold, 20-12 loopback, 21-5
set B3 alarm threshold, 20-12 reset performance register, 20-39
set lter status, 20-9 ATM performance
severity, 20-3 current performance, 20-37
suppression, 20-12 history performance, 20-37
synchronize, 20-22 history performance data analysis, 20-34
type, 20-3 set performance monitoring parameter, 20-19
UNEQ insertion, 20-13 automatic disabling
view current alarm, 20-24 laser shutdown, 20-55
view history alarm, 20-29 loopback, 20-55
alarm attribute, 20-10
board, 20-11 B
NE, 20-10
networkwide, 20-4 backup and restoration
port, 20-11 data, 3-2
alarm attribute template board
Issue 01 (2006-09-15) Huawei Technologies Proprietary i-1

Index Operator Guide
adjust, 4-9 congure bound path, 14-4

alarm attribute, 20-11 congure cross-connection, 14-7
create, 4-8 congure IMA group, 14-9
delete, 4-10 congure port attribute for ATM board, 14-3
Board congure protection group and protection
reset performance register, 20-39 pair, 14-8
board 1+1 protection create cross-connection, 14-5
check protection switching status, 20-42 set SDH NNI, 14-2
perform protection switching, 21-18 create board
board-level protection ATM interface board, 14-2, 16-9
perform protection switching, 21-19 Ethernet interface board, 16-3
broadcast data service, 15-2 create board protection
1+1 protection for cross-connect or clock
board, 16-13
C board level protection for data service board,
change NE time, 8-1 16-16
check PP switching status, 20-44 TPS protection for PDH board, 16-14
check SNCP switching status, 20-44 create broadcast service
client congure broadcast data port, 15-3
exit, 1-7 create Ethernet service
lock, 2-23 congure spanning tree, 11-19, 13-22
login, 1-7 EPL, 13-7
unlock, 2-23 EPLn, 13-11
client/server, 1-3 EVPL, 13-8
clock EVPL(QinQ), 13-10
congure, 5-1 EVPLn, 13-12
dene uniform quality level for unknown QinQ service, 13-16
clock source, 5-6 RPR EVPLn, 13-15
enable extended SSM protocol, 5-3 RPR service, 13-14
enable standard SSM protocol, 5-3 set QoS, 11-18, 13-22
network interconnection clock setting, 5-7 create Ethernet trail
set clock priority, 5-3 adjust bandwidth, 11-9
set phase-locked clock source, 5-6 adjust VB mount port in EPLn, 11-10
set protection switch condition, 5-4 EPL trail, 11-4
set reversion mode and WTR time, 5-5 EPLn trail, 11-6
set SSM output, 5-7 EVPL trail, 11-5
switch clock source manually, 5-8 EVPL(QinQ) trail, 11-8
clock protection switching status, 20-44 relation between SDH trail and Ethernet trail, 11-2
cold reset, 21-20 RPR EPLn trail, 11-13
collect NE data, 20-55 RPR EVPL trail, 11-12
component link, 18-49 server trail, 11-3
component link management trunk link trail, 11-3
resource reservation, 18-52 create protection
conguration data management wrapping, 9-36
consistency check, 3-3 create protection subnet
download, 3-5 1+1 linear MSP, 9-16
upload, 3-4 congure the MS squelch table, 9-12
congure board DNI protection, 9-28
ATM board external port, 14-3, 16-10 four-ber MS-SPRing, 9-9
ATM board internal port, 14-3, 16-9 linear MSP, 9-16
Ethernet board external port, 16-5 M:N linear MSP, 9-18
Ethernet board internal port, 16-4 MSP ring, 9-3
optical booster amplier board, 16-10 non-protection chain, 9-30
PDH board, 16-2 non-protection ring, 9-28
SDH board, 16-2 path protection, 9-24
TDA board, 16-11 protection mode, 9-1
control plane, 18-53 RPR ring, 9-35
create ASON trail RPR ring network, 9-40
diamond, 18-17 search for existing protection subnet, 9-3
create ATM service SNCP, 9-24
congure ATM trafc, 14-6
i-2 Huawei Technologies Proprietary Issue 01 (2006-09-15)

steering, 9-37 database

trunk link-based RPR ring, 9-39 backup, 3-7
two-ber bidirectional PP ring, 9-26 initialization, 3-11
two-ber MS-SPRing, 9-4 restoration, 3-9
two-ber unidirectional PP ring, 9-25 DCC communication
two-bre MS-DPRing, 9-6 DCC byte transparent transmission, 7-3
wrap and steer, 9-39 DCC communications
create SDH service DCC channel rate, 7-4
change normal service to SNCP service, 12-29 DCC channel resource allocation, 7-4
change SNCP service to normal service, 12-30 delete
create linear MSP, 12-4 Ethernet trail, 11-15
create MSP ring, 12-4 delete trail
create NE logical system, 12-3 SDH trail, 10-20
create service for a 1+1 linear MSP, 12-7 trunk link trail, 11-15
create service for a four-ber bidirectional discrete service
MSP ring, 12-19 cause and measure, 10-5
create service for a non-protection chain, 12-6 denition, 10-5
create service for a two-ber bidirectional impact of discrete service, 10-5
MSP ring, 12-17 download conguration data to NE, 3-5
create service for a two-ber bidirectional
PP ring, 12-13
create service for a two-ber unidirectional E
MSP ring, 12-15 equipment set, 2-8
create service for a two-ber unidirectional Ethernet board
PP ring, 12-11 loopback, 21-4
create service on a M:N linear MSP, 12-9 reset performance register, 20-40
dependency of SDH service conguration Ethernet link aggregation
on NE software release, 12-3 add port, 16-7
service across protection subnet, 12-24 conguration, 16-6
SNCP service, 12-21 create link aggregation group, 16-7
create SDH trail delete link aggregation group, 16-7
change non-SNCP trail to SNCP trail, 10-21 delete port, 16-8
change SNCP trail to non-SNCP trail, 10-22 query port and status, 16-8
create trail manually, 10-14 Ethernet OAM maintenance
join VC4 server trail, 10-24 Ethernet OAM, 20-49
modify trail name in batch, 10-21 Ethernet OAM Maintenance
non-SNCP VC12/VC3 trail, 10-12 Creating MPs, 20-50
non-SNCP VC4/VC4-Xc trail, 10-8 Performing CC Check, 20-50
principle, 10-3 Performing LB Check, 20-51
search for congured trail from NE, 10-4 Performing LT Check, 20-52
set SDH optical interface as SDH NNI, 10-7 Ethernet performance
SNCP VC12/VC3 trail, 10-13 current performance, 20-35
SNCP VC4/VC4-Xc trail, 10-9 history performance, 20-35
split VC4 server trail, 10-25 set monitoring parameter, 20-20
VC4 server trail, 10-11 Ethernet protection
create subnet, 4-14 trunk link-based RPR ring, 9-39
custom view Ethernet service, 13-2
create, 1-23 Ethernet trail
set as startup view, 1-23 current performance, 20-38
customise parameter display, 1-24 view current alarm, 20-27
example: create user and assign authority, 2-12
expansion
D add extended subrack, 17-13
data add protection subnet node, 17-14
back up all data, 3-7 adjust board, 17-12
back up MO data immediately, 3-5 create precongured trail in batches, 10-28, 10-32
restore all data, 3-9 create precongured trail one by one, 10-26, 10-30
restore MO data, 3-8 delete handover plan, 10-29
data consistency check between the, 3-3 delete preconguration group, 10-33
data maintenance expand linear MSP link capacity, 9-21, 17-7
backup and restoration method, 3-2 expand MSP ring link capacity, 9-13, 17-3

expand tributary signal processing lockout of settings, 2-41

capability, 17-13 log
extended ECC communication, 7-3 dump, 2-26
dump security log immediately, 2-28
NE security log, 2-29
F operation log, 2-25, 2-26
fast copy, 1-25 security log dump, 2-26
fault diagnosis wizard set overow dump for security log, 2-27
create fault diagnosis rule, 21-10 view, 2-26
start fault diagnosis wizard, 21-11 loopback
fault maintenance automatic disabling, 20-55
fault diagnosis wizard, 21-10
perform loopback, 21-2
perform remote maintenance, 21-21 M
reset board, 21-20 main window
ber NE Explorer, 1-15
automatic creation, 4-11 SDH NE panel, 1-18
delete, 4-12 maintain Ethernet OAM at a station, 20-53
manual creation, 4-11 MO data
modify ber information, 4-13 immediate backup, 3-5
restoration, 3-8
scheduled backup, 3-6
G MSP
GNE congure squelch table, 9-12
change to normal NE, 7-6 prevent service misconnection, 9-12
congure primary GNE, 7-7 squelch table, 9-12
congure standby GNE, 7-8 MSP protection switching request, 21-13
create, 4-4, 18-6 MSP ring
IP address, 7-5 adjust capacity, 9-13, 17-3
NE type, 7-6 check networkwide multiplex section
NSAP address, 7-5 parameter, 20-41
test communication to, 7-7 check protection switching status, 20-42
exercise switching, 20-43
expand link capacity, 9-13, 17-3
H perform protection switching, 21-14
history control group performance
set performance parameter, 20-36
history group performance N
view, 20-35 NE, 2-40, 2-41
alarm attribute, 20-10
change NE time, 8-1
I change to a GNE, 7-5
IMA, 14-9 check GNE switching status, 20-44
congure primary GNE, 7-7
congure standby GNE, 7-8
L data collection, 20-55
laser shutdown delete, 4-7
automatic disabling, 20-55 forced logout, 2-42
license login, 2-40
change, 1-10 orderwire, 6-1
view license, 1-8 search, 1-27
License search and create, 4-3
apply, 1-9 synchronize alarm, 20-22
linear MSP view current alarm, 20-25
adjust capacity, 9-21, 17-6 NE communication
change NP chain to 1+1 linear MSP, 9-31, 17-9 Ethernet access control, 2-35
check protection switching status, 20-43 serial port access control, 2-36
exercise switching, 20-43 NE conguration data
expand link capacity, 9-21, 17-7 backup, 3-10
perform protection switching, 21-15 NE login, 2-40
lockout of login, 2-40 NE security

LCT access control, 2-36 perform board protection switching

NE security parameter, 2-39 1+1 protection for cross-connect or clock
query NE user group, 2-40 board, 16-13
NE time board level protection for data service board,
synchronization scheme, 8-2 16-17
synchronize with, 8-2, 8-3 TPS protection for PDH board, 16-15
synchronize with NTP server, 8-3 performance
NE user immediate dump, 20-17
create, 2-4, 2-37 monitored object, 20-19
switch, 2-41 overow dump, 20-18
NE user group scheduled dump, 20-18
create, 2-5 performance monitoring
network adjustment start, 20-19
change NP chain to 1+1 linear MSP, 9-31, 17-9 stop, 20-19
delete protection subnet, 9-34 performance threshold template
network security conguration, 2-33 apply, 20-17
NM name, 4-10 create, 20-16
NM user physical location information report
assign authority, 2-9 cabinet, 19-7
client access control, 2-11 equipment room, 19-7
delete, 2-19 subrack, 19-7
equipment set, 2-8 protection switching
forced logout, 2-24 board 1+1 protection, 21-18
operation set, 2-6 board-level protection, 21-19
password, 2-17, 2-38 linear MSP, 21-15
switch, 2-23 MSP ring, 21-14
switch user mode, 2-24 RPR protection, 21-17
user password validity, 2-16 RPR ring network, 21-17
user validity, 2-16 SNCP service control, 21-16
NM user group TPS protection, 21-19
assign authority, 2-8
NM user management, 2-2
non-gateway NE Q
create, 4-6 QinQ service
NP chain add double-layer tag based on PORT, 13-17
change to 1+1 linear MSP, 9-31, 17-9 add single-layer tag based on PORT, 13-18
NTP, 8-3 add tag based on PORT+VLAN, 13-19
exchange user tag and add single-layer tag, 13-21
service introduction, 13-17
O query NE software version, 12-3
operation object
alarm color, 1-20
lter, 1-25 R
lockout, 1-26 remote maintenance
move, 1-26 enable remote maintenance user, 21-22
NE status, 1-20 networking, 21-21
path status, 1-20 perform remote maintenance, 21-23
port status, 1-20 remote maintenance user, 2-30
unlock, 1-26 change remote maintenance user password, 2-31
operation set, 2-6 set remote maintenance user authority, 2-32
operation set type, 2-3 set remote maintenance user validity, 2-32
orderwire remote maintenance user management, 2-29
conference call, 6-3 report
express orderwire, 6-4 board count report, 19-5
local orderwire, 6-2 board details report, 19-6
orderwire subnet, 6-5 board information report, 19-6
clock tracing diagram, 19-3
ber/cable connection report, 19-7
P NE information report, 19-4
PDH board networking diagram, 19-3
loopback, 21-3 physical location information report, 19-7

report type, 19-3 set password template, 2-19

slot conguration report, 19-5 set user lockout duration, 2-17
slot information report, 19-5 server
timeslot allocation diagram, 19-4 restart, 1-8
reset running status, 1-6
non-SCC board, 21-21 shutdown, 1-8
SCC board, 21-20 Server
reset performance register Start, 1-6
ATM board, 20-39 set SDH trail overhead
Ethernet board, 20-40 congure C2 byte, 10-17
NE, 20-39 congure trace byte, 10-16
RMON performance set overhead termination, 10-18
set alarm group performance parameter, 20-36 shut down
set history control group performance shut down, 1-7, 1-8
parameter, 20-36 SNCP service control
view history group performance data, 20-35 perform protection switching, 21-16
view statistic group performance data, 20-37 SNCP trail protection switching status, 20-45
RPR protection SSL protocol communication
perform protection switching, 21-17 access control, 2-34
RPR protection switching request, 21-16 start
RPR ring log into, 1-7
adjust link bandwidth, 9-44, 17-11 restart, 1-8
modify parameter, 9-42 Start
search, 9-40 Start, 1-6
trunk link-based, 9-39 Syslog server, 2-29
RPR ring network System Monitor, 1-6
create, 9-40
perform protection switching, 21-17
T
T2000
S synchronize current alarm, 20-23
script le T2000 client
export, 3-7 forced logout, 2-24
import, 3-10 switch NM user, 2-23
SDH board switch user mode, 2-24
SDH interface loopback, 21-2 T2000 data
VC3 path loopback, 21-7 export script, 3-7
VC4 path loopback, 21-6 import script, 3-10
SDH NNI, 14-2 scheduled MO data backup, 3-6
SDH performance T2000 Login, 2-23
forecast medium- and long-term T2000 main topology
performance, 20-34 main topology, 1-11
history performance, 20-32 T2000 main window
threshold crossing, 20-33 clock view, 1-17
UAT, 20-33 protection view, 1-16
SDH trail trail view, 1-17
current performance, 20-38 T2000 security management
loopback, 21-9 congure warning screen for login, 2-22
set alarm reversion, 20-15 congure weakness password dictionary, 2-22
set alarm suppression, 20-14 set password aging warning period, 2-18
set performance monitoring parameter, 20-20 set password reuse frequency, 2-21
view current alarm, 20-26 set password reuse period, 2-21
security log management set password template, 2-19
upload operation log, 2-29 set user lockout duration, 2-17
Security Management, 2-1 T2000 software architecture, 1-3
security policy, 2-29 table text, 1-25
congure warning screen for login, 2-22 TE link management protocol
congure weakness password dictionary, 2-22 create, 18-57
set password aging warning period, 2-18 view, 18-56
set password reuse frequency, 2-21 topology object
set password reuse period, 2-21 board, 4-8

ber, 4-11
GNE, 4-4, 18-6
link, 4-13
NE, 4-3
non-gateway NE, 4-6
topology subnet, 4-14
TPS protection
check protection switching status, 20-42
perform protection switching, 21-19
troubleshooting
collect equipment data, 20-55
trunk link
view current alarm, 20-27
U
UNEQ, 20-13
upload NE conguration data to, 3-4
V
view trail
Ethernet trail, 11-17
SDH trail, 10-19
server trail of Ethernet trail, 11-18
trunk link relevant trail, 11-17
trunk link trail, 11-16
visual and audible alarm
cabinet, 20-30
W
warm reset, 21-20
WDM performance
history performance, 20-32
threshold crossing, 20-33
UAT, 20-33

Huawei-Optix-Imanager-T2000-Operation-Guide 2 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei-Optix-Imanager-T2000-Operation-Guide 2 PDF

Uploaded by

Copyright:

Available Formats

OptiX iManager T2000

Huawei Technologies Proprietary

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2006. All rights reserved.

Trademarks and Permissions

Huawei Technologies Proprietary

About This Document ................................................................................................................. xix

Issue 01 (2006-09-15) Huawei Technologies Proprietary i

1.12 Operation Precautions ........................................................................................................ 1-27

ii Huawei Technologies Proprietary Issue 01 (2006-09-15)

Issue 01 (2006-09-15) Huawei Technologies Proprietary iii

4.13 Creating Fibers Manually ................................................................................................... 4-11

iv Huawei Technologies Proprietary Issue 01 (2006-09-15)

9.3 Conguring Linear MSP ...................................................................................................... 9-16

Issue 01 (2006-09-15) Huawei Technologies Proprietary v

10.10 Changing Between SNCP and Normal Trails .....................................................................10-21

vi Huawei Technologies Proprietary Issue 01 (2006-09-15)

12.6.3 Creating M:N Linear MSP Services ............................................................................. 12-9

Issue 01 (2006-09-15) Huawei Technologies Proprietary vii

15.2 Conguring Broadcast Data Ports........................................................................................ 15-3

viii Huawei Technologies Proprietary Issue 01 (2006-09-15)

18.1.4 Setting the Primary/Secondary NE............................................................................... 18-9

Issue 01 (2006-09-15) Huawei Technologies Proprietary ix

18.9.5 Enabling OSPF Protocol............................................................................................18-56

x Huawei Technologies Proprietary Issue 01 (2006-09-15)

20.6 Setting the Alarm Monitoring Strategy for SDH Trails..........................................................20-14

Issue 01 (2006-09-15) Huawei Technologies Proprietary xi

20.10 Resetting Performance Registers.......................................................................................20-39

xii Huawei Technologies Proprietary Issue 01 (2006-09-15)

21.3.1 MSP Protection Switching Priority .............................................................................21-13

Issue 01 (2006-09-15) Huawei Technologies Proprietary xiii

Figure 1-1 T2000 software architecture................................................................................................... 1-4

Issue 01 (2006-09-15) Huawei Technologies Proprietary xv

xvi Huawei Technologies Proprietary Issue 01 (2006-09-15)

Table 1-1 Description of T2000 functional modules.................................................................................. 1-4

Issue 01 (2006-09-15) Huawei Technologies Proprietary xvii

About This Document

Issue 01 (2006-09-15) Huawei Technologies Proprietary xix

xx Huawei Technologies Proprietary Issue 01 (2006-09-15)

Issue 01 (2006-09-15) Huawei Technologies Proprietary xxi

xxii Huawei Technologies Proprietary Issue 01 (2006-09-15)

About This Chapter

1.1 Starting or Shutting Down the T2000

Issue 01 (2006-09-15) Huawei Technologies Proprietary 1-1

1.14 Interface Typing Rules

1-2 Huawei Technologies Proprietary Issue 01 (2006-09-15)

1.1 Starting or Shutting Down the T2000

1.1.1 T2000 Software Architecture

1.1.1 T2000 Software Architecture

Issue 01 (2006-09-15) Huawei Technologies Proprietary 1-3

Figure 1-1 T2000 software architecture

Table 1-1 Description of T2000 functional modules

1-4 Huawei Technologies Proprietary Issue 01 (2006-09-15)

Issue 01 (2006-09-15) Huawei Technologies Proprietary 1-5

1.1.2 Starting the T2000 Server

1.1.3 Viewing the T2000 Working Status

1-6 Huawei Technologies Proprietary Issue 01 (2006-09-15)

1.1.4 Starting the T2000 Client

Step 3 Optional: Set the server parameters.

1. Click to display the Setting dialog box.

4. Click OK to complete adding a server.

1.1.5 Exiting a T2000 Client

Issue 01 (2006-09-15) Huawei Technologies Proprietary 1-7