Ason User Guide (v100r006c00 - 03)

OptiX OSN 8800 Intelligent Optical Transport
Platform
V100R006C00
ASON User Guide
Issue 03
Date 2011-09-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

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

Copyright © Huawei Technologies Co., Ltd.
OptiX OSN 8800 Intelligent Optical Transport Platform
ASON User Guide About This Document
About This Document
Related Versions
The following table lists the product versions related to this document.
Product Name Version
OptiX OSN 8800 V100R006C00
OptiX GSP V100R006C00
iManager U2000 V100R003C00
Intended Audience
This document describes the function, concept, planning, commissioning, configuring, routine
maintenance, troubleshooting and the causes and the handling procedures of the alarms of the
ASON.
This document is intended for:
l Network Planning Engineer
l Installation and Commissioning Engineer
l Field Maintenance Engineer
l Network Monitoring Engineer
l Data Configuration Engineer
l NM Administrator
l System Maintenance Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 03 (2011-09-15) Huawei Proprietary and Confidential ii

Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation that, if not

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

supplement important points of the main text.
TIP Indicates a tip that may help you solve a problem or save
you time.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 03 (2011-09-15) Based on Product Version

V100R006C00
The updates of the document are as follows:
Issue 03 (2011-09-15) Huawei Proprietary and Confidential iii

Update Description
Commissioning The updates in this chapter are as follows:

the OTN ASON l Synchronizing TE Links: Some bugs are fixed.

V100R006C00
Update Description
About the ASON The updates in this chapter are as follows:

l LSP Rerouting Process: In this section, "Rerouting Triggered by
Channel Alarms" is added.
l Service Association: Suggestions for configuring associated services
are added.
l ASON Features Based on Separate Optical and Electrical NEs:
Requirements for configuring boards on separate optical and
electrical NEs are provided.
l Trail Pre-Computation and Adjustment: In this section, the
description of presetting restoration trails against more than one fiber
cut is supplemented.
l Service Reversion Mechanism: In this section, optimization of
automatic reversion of optical-layer wavelengths is supplemented.
l Trail Sharing: This section is updated with the description of active/
standby trail sharing and associated service sharing.

the OTN ASON l Setting Link Cost: Information on how to set Custom Cost is
provided.
Configuring The updates in this chapter are as follows:

OTN ASON l Creating WDM ASON Trails: The sequence for setting explicit nodes
Networks and explicit links is specified.
l Setting Preset Restoration Trails: A description is added to emphasize
that the nodes on preset restoration trails must be in strict compliance
with the node sequences as specified in the network plan.
Issue 03 (2011-09-15) Huawei Proprietary and Confidential iv


V100R006C00
This is the first release of OptiX OSN 8800 V100R006C00. Compared with OptiX OSN 8800
V100R005C00 provides the following updates.
Update Description
Configuring In this chapter, the "Creating ASON Trails for Services with Tributary
OTN ASON SNCP Protection" and "Performing Conversion Between ASON Trails
Networks for Services with Tributary SNCP and Those for Services Without
Tributary SNCP" sections are added.

V100R005C00
Some bugs in the manual of the previous version are fixed.

V100R005C00
Update Description
About the ASON The updates in this chapter are as follows:

l LSP Rerouting Process: In this section, "Rerouting Triggered by
Channel Alarms" is added.
l Service Association: Suggestions for configuring associated services
are added.
l ASON Features Based on Separate Optical and Electrical NEs:
Requirements for configuring boards on separate optical and
electrical NEs are provided.
l Trail Sharing: This section is updated with the description of active/
standby trail sharing and associated service sharing.
Issue 03 (2011-09-15) Huawei Proprietary and Confidential v

Update Description

the OTN ASON l Setting Link Cost: Information on how to set Custom Cost is
provided.
l Preparations: In this section, "Commissioning Process and
Commissioning Items" is updated.
l The "Commissioning Preset Restoration Trails" section is added.
Configuring The updates in this chapter are as follows:

OTN ASON l Creating WDM ASON Trails: The sequence for setting explicit nodes
Networks and explicit links is specified.
l Setting Preset Restoration Trails: A description is added to emphasize
that the nodes on preset restoration trails must be in strict compliance
with the node sequences as specified in the network plan.

V100R005C00
This is the first release of OptiX OSN 8800 V100R005C00. Compared withOptiX OSN 8800
V100R002C02, OptiX OSN 8800 V100R005C00 provides the following updates.
Update Description
About the ASON The structure is reorganized and the contents are updated and
supplemented. The updates in chapter 1 are as follows:
l Network Traffic Engineering: In this section, the descriptions of the
optical-layer SRLG inheritance (inter-layer attribute inheritance) and
user-defined link cost features are supplemented.
l Rerouting of an LSP: In this section, more alarms, which trigger
rerouting, on optical-layer path are supplemented.
l Service Association: In this section, the description of the feature of
pre-calculation of associated nodes that have different source nodes
is supplemented.
l Service Priorities and Preemption: This section is a new section
describing service priorities and resource preemption.
l Resource Sharing of the Trails: This section is updated with the
description of working/protection trail sharing and associated service
trail sharing.
Issue 03 (2011-09-15) Huawei Proprietary and Confidential vi

Update Description
Commissioning In this chapter, the "Setting Link Cost" section is added to describe how
the OTN ASON to set a link cost. Regarding the rerouting test procedure, rerouting of
ASON ODU3 services is described.
The "Automatic Commissioning Process and Commissioning Items"
section is added.
Steps in the "Setting Optical Parameters" are updated.
Configuring This chapter has the following updates:

OTN ASON l Regarding the methods of configuring an ASON service, the methods
Networks of configuring an ODU3 service are added.
l "Activating WDM ASON Trails", "Managing OVPN Users and
Services", and "Creating Services Between ASON NEs and
Traditional NEs" sections are added.
l The operation procedure for setting a preset restoration trail is
updated.
l The operation procedure and corresponding screen captures are
updated according to the mapping NMS version.
Routine The maintenance item list is updated and the procedure for backing up
Maintenance for data is added.
an ASON
Network
Handling ASON "Handling an LSP Creation Timeout Fault", "Handling the Fault with
Network Unavailable Wavelengths at the Service Adding/Dropping Ports",
Failures "Handling an Optical Parameter Verification Failure", "Handling the
Failure to Reroute Services" and "Restoration Against Disasters" sections
are added.
Alarm This chapter has the following updates:

Reference l The CP_LSP_NO_PRERRT alarm is added.
l The ODU3 service-related alarms are added and the procedure for
handling these alarms are described.
l The procedure for handling the CPC_OSPF_CL_DOWN,
CPW_ODUk_TEL_DOWN, CPW_OMS_TEL_DOWN, and
CPW_OTUk_TEL_DOWN alarms is updated.
Issue 03 (2011-09-15) Huawei Proprietary and Confidential vii

ASON User Guide Contents
Contents
About This Document.....................................................................................................................ii

1 About the ASON............................................................................................................................1
1.1 Overview............................................................................................................................................................3
1.1.1 Background and Advantages.....................................................................................................................3
1.1.2 Features of the ASON................................................................................................................................4
1.1.3 Huawei OTN ASON Solution...................................................................................................................4
1.1.4 Huawei OCS ASON Solution....................................................................................................................6
1.1.5 Introduction and Development of the OTN ASON...................................................................................8
1.1.6 Introduction and Development of the OCS ASON...................................................................................9
1.2 ASON Software and ASON Functions............................................................................................................10
1.2.1 Basic Concepts of ASON........................................................................................................................10
1.2.2 Structure of the ASON Transmission Network.......................................................................................11
1.2.3 Location of ASON Software...................................................................................................................12
1.2.4 Structure of ASON Software...................................................................................................................13
1.2.5 ASON Standards......................................................................................................................................15
1.2.6 ASON Protocol........................................................................................................................................16
1.2.7 OTN ASON Links...................................................................................................................................19
1.2.8 OCS ASON Links...................................................................................................................................23
1.2.9 Function Structure of the OTN ASON....................................................................................................25
1.2.10 Function Structure of the OCS ASON..................................................................................................27
1.2.11 ASON Network Protection and Restoration..........................................................................................29
1.3 Automatic Discovery of Topologies and Resources........................................................................................30
1.3.1 Auto-Discovery of ASON NEs...............................................................................................................30
1.3.2 Auto-Discovery of Control Links............................................................................................................31
1.3.3 Auto-Discovery of TE Links...................................................................................................................33
1.4 Creation and Deletion of the ASON Trail........................................................................................................33
1.4.1 Creation of an LSP..................................................................................................................................33
1.4.2 Deletion of an LSP..................................................................................................................................35
1.4.3 Rerouting of an LSP................................................................................................................................36
1.4.4 Change of an LSP....................................................................................................................................37
1.5 OTN ASON Feature.........................................................................................................................................37
1.5.1 End-to-End Service Configuration..........................................................................................................37
1.5.2 Mesh Networking Protection and Restoration.........................................................................................38
Issue 03 (2011-09-15) Huawei Proprietary and Confidential viii

1.5.3 SLA Classification of Services................................................................................................................39

1.5.4 Diamond WDM ASON Trail..................................................................................................................41
1.5.5 Silver WDM ASON Trail........................................................................................................................44
1.5.6 Copper WDM ASON Trail......................................................................................................................46
1.5.7 OVPN......................................................................................................................................................47
1.5.8 Crankback Mechanism ...........................................................................................................................49
1.5.9 Network Traffic Engineering...................................................................................................................50
1.5.10 Service Association...............................................................................................................................52
1.5.11 Service Optimization.............................................................................................................................53
1.5.12 Service Migration..................................................................................................................................54
1.5.13 Preset Restoration Trail.........................................................................................................................54
1.5.14 Trail Pre-Computation and Adjustment................................................................................................56
1.5.15 Service Reversion Mechanism..............................................................................................................56
1.5.16 Resource Sharing of Trails....................................................................................................................58
1.5.17 ASON Features Based on the Split of Optical and Electrical NEs........................................................60
1.6 OCS ASON Feature..........................................................................................................................................64
1.6.1 End-to-End Service Configuration..........................................................................................................64
1.6.2 Mesh Networking Protection and Restoration.........................................................................................65
1.6.3 SLA Classification of Services................................................................................................................65
1.6.4 Diamond Services....................................................................................................................................67
1.6.5 Gold Services...........................................................................................................................................71
1.6.6 Silver Services.........................................................................................................................................73
1.6.7 Copper Services.......................................................................................................................................75
1.6.8 Iron Services............................................................................................................................................76
1.6.9 Tunnels....................................................................................................................................................77
1.6.10 Shared Mesh Restoration Trail..............................................................................................................79
1.6.11 Crankback Mechanism .........................................................................................................................80
1.6.12 Network Traffic Engineering.................................................................................................................80
1.6.13 Service Association...............................................................................................................................83
1.6.14 Service Optimization.............................................................................................................................84
1.6.15 Service Migration..................................................................................................................................84
1.6.16 Preset Restoration Trail.........................................................................................................................84
1.6.17 Trail Pre-Computation and Adjustment................................................................................................85
1.6.18 Reverting Services to Original Routes..................................................................................................85
1.6.19 Amalgamation of ASON and LCAS.....................................................................................................85
1.6.20 Merging an ASON Network with a Traditional SDH Network............................................................86
1.7 Optical-Layer and Electrical-Layer ASON Services........................................................................................93
1.7.1 Protection and Restoration Mechanisms for Services.............................................................................93
1.7.2 Quick Finding of Optical-Layer and Electrical-Layer Functions............................................................94
1.7.3 Prerequisites for Enabling ASON Features.............................................................................................97
1.7.4 Conditions for Configuring ASON Services...........................................................................................97
2 Planning the OTN ASON........................................................................................................100
Issue 03 (2011-09-15) Huawei Proprietary and Confidential ix

2.1 Requisite Knowledge on ASON Planning......................................................................................................101

2.1.1 Functions of an ASON Network...........................................................................................................101
2.1.2 Use of the Planning and Simulation Tool..............................................................................................101
2.2 ASON Network Planning Process..................................................................................................................101
2.2.1 Planning Flow........................................................................................................................................101
2.2.2 Specifying Planning Objective and Strategy.........................................................................................102
2.2.3 Collecting Network Information...........................................................................................................103
2.2.4 Analyzing Services................................................................................................................................104
2.2.5 Designing Network Structure................................................................................................................104
2.2.6 Planning Network Capacity...................................................................................................................106
2.2.7 Network Capacity Verification and Reliability Analysis......................................................................108
3 Planning the OCS ASON.........................................................................................................111

3.1 Requisite Knowledge on ASON Planning......................................................................................................112
3.1.1 Functions of an ASON Network...........................................................................................................112
3.1.2 Use of the Planning and Simulation Tool..............................................................................................112
3.2 ASON Network Planning Process..................................................................................................................112
3.2.1 Planning Flow........................................................................................................................................112
3.2.2 Specifying Planning Objective and Strategy.........................................................................................113
3.2.3 Collecting Network Information...........................................................................................................114
3.2.4 Analyzing Services................................................................................................................................116
3.2.5 Designing Network Structure................................................................................................................117
3.2.6 Planning Network Capacity...................................................................................................................121
3.2.7 Network Capacity Verification and Reliability Analysis......................................................................126
3.3 ASON Network Planning Technologies.........................................................................................................127
3.3.1 Planning MS..........................................................................................................................................127
3.3.2 Combining ASON Networks with SDH Networks...............................................................................128
3.3.3 Planning Lower Order Services.............................................................................................................131
3.3.4 Planning the Node ID............................................................................................................................133
3.3.5 Planning a Large-Scale ASON Network...............................................................................................134
4 Commissioning the OTN ASON............................................................................................136

4.1 Preparations....................................................................................................................................................138
4.1.1 Preparing Engineering Documents........................................................................................................138
4.1.2 Preparing Software Versions.................................................................................................................138
4.1.3 Preparing Dual SCC Boards..................................................................................................................138
4.1.4 Preparing Tools and Meters...................................................................................................................138
4.1.5 Checking ASON Commissioning Conditions.......................................................................................139
4.1.6 Automatic Commissioning Process and Commissioning Items............................................................139
4.2 Configuring an ASON NE..............................................................................................................................144
4.2.1 Setting the Node ID...............................................................................................................................144
4.2.2 Checking Consistency Between Logical Boards and Physical Boards.................................................145
4.2.3 Setting the DCC Bytes...........................................................................................................................146
4.2.4 Enabling the ASON Feature .................................................................................................................148
Issue 03 (2011-09-15) Huawei Proprietary and Confidential x

4.2.5 Uploading NE Configuration Data........................................................................................................149

4.2.6 Configuring a Station with Separate Optical and Electrical NEs..........................................................149
4.2.7 Creating Domains for an ASON Network.............................................................................................152
4.2.8 Setting the Primary NE or Secondary NE.............................................................................................152
4.2.9 Synchronizing ASON NEs....................................................................................................................153
4.2.10 Synchronizing Control Links Networkwide........................................................................................154
4.2.11 Synchronizing TE Links......................................................................................................................155
4.2.12 Automatically Creating Fibers Between Sites.....................................................................................156
4.2.13 Creating Out-Fiber Control Channels..................................................................................................157
4.2.14 Creating a Virtual TE Link..................................................................................................................159
4.3 Managing the ASON Protocol........................................................................................................................160
4.3.1 Configuring the LMP Protocol..............................................................................................................160
4.3.2 Configuring the OSPF Protocol.............................................................................................................162
4.3.3 Configuring the OSPF Protocol Authentication....................................................................................163
4.3.4 Configuring the RSVP Protocol Authentication...................................................................................164
4.4 Configuring the Link Parameter.....................................................................................................................165
4.4.1 Creating an SRLG.................................................................................................................................165
4.4.2 Configuring the Link Distance..............................................................................................................166
4.4.3 Setting Link Cost...................................................................................................................................167
4.4.4 Setting Resource Reservation................................................................................................................168
4.5 Commissioning Preset Restoration Trails......................................................................................................169
4.6 Testing Resource and Topology Auto-Discovery..........................................................................................170
4.6.1 Testing the Auto-Discovery of ASON NEs..........................................................................................170
4.6.2 Testing the Auto-Discovery of Control Links.......................................................................................170
4.6.3 Testing the Auto-Discovery of TE Links..............................................................................................171
4.7 Testing ASON Features of a Service..............................................................................................................173
4.7.1 Testing Creation and Deletion of ASON Services................................................................................173
4.7.2 Testing Creation Disabling of the Rerouting Function of ASON Services...........................................174
4.7.3 Testing Query and Change of ASON Services.....................................................................................175
4.7.4 Testing the Rerouting Lockout Function of ASON Services................................................................176
4.7.5 Testing Trail Pre-computation of ASON Services................................................................................177
4.7.6 Testing Restoration of ASON Services to the Preset Trail...................................................................178
4.7.7 Testing Modification and Adjustment of ASON Service Trails...........................................................179
4.7.8 Testing ASON Service Restoration on the Entire Network..................................................................180
4.7.9 Testing Route Computation Based on Constraints................................................................................182
4.7.10 Testing Rerouting of Associated Services...........................................................................................183
4.7.11 Testing Conversion Between ASON Services and Traditional Services............................................185
4.7.12 Testing the Conversion Between ASON Services with Different SLAs.............................................186
4.8 Testing the Rerouting Capability of ASON Services.....................................................................................188
4.8.1 Testing an Electrical-Layer Diamond WDM ASON ODUk Trail........................................................188
4.8.2 Testing an Optical-Layer Silver WDM ASON OCh Trail....................................................................190
4.8.3 Testing an Electrical-Layer Silver WDM ASON ODUk Trail.............................................................192
Issue 03 (2011-09-15) Huawei Proprietary and Confidential xi

5 Commissioning the OCS ASON............................................................................................ 195

5.1 Preparations....................................................................................................................................................196
5.1.1 Networking Diagram.............................................................................................................................196
5.1.2 Tools and Documents............................................................................................................................197
5.1.3 Checking Consistency Between Logical Boards and Physical Boards.................................................197
5.1.4 Setting DCC Mode................................................................................................................................198
5.1.5 Setting the Node ID...............................................................................................................................199
5.1.6 Enabling the ASON Feature .................................................................................................................200
5.1.7 Uploading NE Configuration Data........................................................................................................202
5.1.8 Creating Domains for an ASON Network.............................................................................................202
5.1.9 Synchronizing ASON NEs....................................................................................................................203
5.1.10 Setting the Primary NE or Secondary NE...........................................................................................204
5.1.11 Synchronizing Control Links Networkwide........................................................................................205
5.1.12 Synchronizing TE Links......................................................................................................................205
5.2 Testing Resource and Topology Auto-Discovery..........................................................................................206
5.2.1 Testing Topology Auto-Discovery........................................................................................................206
5.2.2 Testing Resource Auto-Discovery.........................................................................................................207
5.3 Testing the ASON Services............................................................................................................................208
5.3.1 Testing Permanent 1+1 Diamond Services...........................................................................................208
5.3.2 Testing Rerouting 1+1 Diamond Services.............................................................................................209
5.3.3 Testing Non-rerouting 1+1 Diamond Services......................................................................................210
5.3.4 Testing Gold Services............................................................................................................................211
5.3.5 Testing Silver Services..........................................................................................................................212
5.3.6 Testing Copper Services........................................................................................................................213
5.3.7 Testing Iron Services.............................................................................................................................213
5.3.8 Test Gold Tunnels.................................................................................................................................214
5.3.9 Testing Silver Tunnels...........................................................................................................................216
5.3.10 Testing Copper Tunnels.......................................................................................................................216
5.4 Testing Batch Rerouting.................................................................................................................................217
6 Configuring OTN ASON Networks......................................................................................219

6.1 Creating WDM ASON Trails.........................................................................................................................221
6.1.1 Creating an Optical-Layer Silver WDM ASON OCh Trail..................................................................221
6.1.2 Creating an Optical-Layer Copper WDM ASON OCh Trail................................................................227
6.1.3 Creating an Electrical-Layer Diamond WDM ASON ODUk Trail......................................................232
6.1.4 Creating an Electrical-Layer Silver WDM ASON ODUk Trail............................................................239
6.1.5 Creating an Electrical-Layer Copper WDM ASON ODUk Trail.........................................................244
6.1.6 Creating ASON Trails for Services with Tributary SNCP Protection..................................................250
6.1.7 Setting Association of WDM ASON Trails..........................................................................................257
6.1.8 Creating WDM ASON Trails in Batches..............................................................................................260
6.1.9 Activating WDM ASON Trails.............................................................................................................264
6.1.10 Deactivating ASON Trail....................................................................................................................264
6.1.11 Deleting an ASON Trail......................................................................................................................265
Issue 03 (2011-09-15) Huawei Proprietary and Confidential xii

6.1.12 Configuring the Explicit Link..............................................................................................................266

6.2 Modifying the Attributes of ASON WDM Trails..........................................................................................268
6.2.1 Viewing WDM ASON Trail Attributes.................................................................................................268
6.2.2 Setting the Routing Attributes...............................................................................................................270
6.2.3 Setting the Scheduled Reversion Time..................................................................................................270
6.2.4 Setting Rerouting Triggered by SD.......................................................................................................271
6.2.5 Setting Preset Restoration Trail.............................................................................................................272
6.2.6 Setting the Original Route.....................................................................................................................273
6.2.7 Disabling Electrical-Layer ASON Links...............................................................................................274
6.3 Modifying the Route of an ASON Service.....................................................................................................275
6.3.1 Reverting the WDM ASON OCh Trail Manually.................................................................................275
6.3.2 Reverting A WDM ASON Trail to the Original Route.........................................................................275
6.3.3 Optimizing WDM ASON OCh Trail.....................................................................................................276
6.3.4 Optimizing WDM ASON ODUk Trail.................................................................................................277
6.4 Converting ASON Services............................................................................................................................279
6.4.1 Converting a WDM ASON Trail to a Traditional WDM Trail.............................................................279
6.4.2 Converting a Traditional WDM Trail to an WDM ASON Trail...........................................................280
6.4.3 Performing Conversion Between the Diamond and Silver or Copper WDM ASON Trails.................282
6.4.4 Performing Conversion Between the Silver and Copper WDM ASON Trails.....................................283
6.4.5 Performing Conversion Between ASON Trails for Services with Tributary SNCP and Those for Services
Without Tributary SNCP................................................................................................................................283
6.5 Managing the OVPN Customers and OVPN Services...................................................................................286
6.5.1 Enabling OVPN Function of ASON NE...............................................................................................286
6.5.2 Creating NM User for OVPN Customer...............................................................................................287
6.5.3 Creating OVPN Customer.....................................................................................................................289
6.5.4 Allocating TE Links for OVPN Customers...........................................................................................291
6.5.5 Creating OVPN Services.......................................................................................................................292
6.5.6 Querying the TE Link Resources of the OVPN Customers..................................................................298
6.5.7 Querying the Services of the OVPN Customers...................................................................................299
6.6 Creating Services Between an ASON NE and a Traditional NE...................................................................299
6.6.1 Creating Services Between Two Traditional NEs with ASON NEs in Between..................................300
6.6.2 Creating 1+1 Services Between Two Traditional NEs with ASON NEs in Between...........................302
6.6.3 Creating Services Between ASON NEs with a Traditional NE in Between.........................................305
6.7 Managing Services Between a WDM ASON NE and a Traditional WDM NE............................................307
6.7.1 Searching for WDM Trails Crossing the ASON Domain.....................................................................308
6.7.2 Querying the ASON Trails Related to the Traditional WDM Trail......................................................308
6.7.3 Setting the Span ID of the ASON-WDM Trail.....................................................................................309
6.8 Managing Control Plane Alarms and Performance Events............................................................................310
6.8.1 Querying Control Plane Alarms............................................................................................................310
6.8.2 Management of the Suppression Status of Alarms on the Control Plane..............................................311
6.8.3 Management of the Suppression Status of Alarms Events on the Control Plane..................................311
6.8.4 Querying the Performance of the Control Plane....................................................................................312
6.8.5 Monitoring the Control Plane Performance...........................................................................................313
Issue 03 (2011-09-15) Huawei Proprietary and Confidential xiii

6.8.6 Setting the Auto-Report Status of the Control Plane Performance Data...............................................313
6.8.7 Setting the Control Plane Performance Threshold ...............................................................................314
7 Configuring OCS ASON Networks.......................................................................................315

7.1 Managing the ASON Protocol........................................................................................................................317
7.1.1 Modifying the LMP Discovery Type....................................................................................................317
7.1.2 Disabling/Enabling the LMP Protocol..................................................................................................319
7.1.3 Disabling/Enabling the OSPF Protocol.................................................................................................319
7.1.4 Configuring the OSPF Protocol Authentication....................................................................................320
7.1.5 Configuring the RSVP Protocol Authentication...................................................................................321
7.1.6 Creating Out-Fiber Control Channels....................................................................................................322
7.2 Managing Link Resources..............................................................................................................................324
7.2.1 Configuring the Link Distance..............................................................................................................324
7.2.2 Setting the Usage Threshold of Fiber Resources...................................................................................325
7.2.3 Creating an SRLG.................................................................................................................................325
7.2.4 Querying the Information About the Timeslots on the Link Sections..................................................327
7.2.5 Setting Resource Reservation................................................................................................................327
7.2.6 Creating a Virtual TE Link....................................................................................................................330
7.3 Creating ASON Services................................................................................................................................332
7.3.1 Creating a Diamond ASON Service......................................................................................................333
7.3.2 Creating a Gold ASON service.............................................................................................................337
7.3.3 Creating a Silver ASON Service...........................................................................................................341
7.3.4 Creating a Copper ASON Service.........................................................................................................345
7.3.5 Creating an Iron ASON Service............................................................................................................349
7.3.6 Creating an ASON Server Trail.............................................................................................................352
7.3.7 Creating Two Associated ASON Trails................................................................................................356
7.3.8 Setting ASON Trail Association...........................................................................................................358
7.3.9 Creating ASON Services in Batches.....................................................................................................359
7.3.10 Deactivating the ASON Trail..............................................................................................................363
7.3.11 Deleting an ASON Trail......................................................................................................................364
7.4 Modifying the Attributes of ASON WDM Trails..........................................................................................364
7.4.1 Viewing WDM ASON Trail Attributes.................................................................................................365
7.4.2 Setting the Routing Attributes...............................................................................................................366
7.4.3 Setting the Scheduled Reversion Time..................................................................................................367
7.4.4 Setting the B3 Alarm to Trigger Rerouting...........................................................................................367
7.4.5 Setting Preset Restoration Trail.............................................................................................................368
7.4.6 Setting Shared MESH Restoration Trail...............................................................................................369
7.4.7 Setting the Original Route.....................................................................................................................370
7.5 Modifying the Route of an ASON Service.....................................................................................................370
7.5.1 Reverting ASON Trails.........................................................................................................................370
7.5.2 Optimizing an ASON Service...............................................................................................................372
7.6 Migrating ASON Services..............................................................................................................................373
7.6.1 Converting an ASON Service to a Traditional Service.........................................................................374
Issue 03 (2011-09-15) Huawei Proprietary and Confidential xiv

7.6.2 Converting a Traditional Service to an ASON Service.........................................................................374

7.6.3 Migration Between ASON Services......................................................................................................375
7.6.4 Migrating an ASON Server Trail to a Traditional Server Trail.............................................................377
7.6.5 Migrating a Traditional Server Trail to an ASON Server Trail.............................................................378
7.6.6 Migration Between ASON Server Trails...............................................................................................378
7.7 Creating ASON Trail Groups.........................................................................................................................379
7.8 Creating Services Between an ASON NE and a Traditional NE...................................................................382
7.8.1 Creating a VC4 Service Between Two Traditional NEs with ASON NEs in Between........................382
7.8.2 Creating a VC12 Service Between Two Traditional NEs within ASON NEs in Between...................385
7.8.3 Creating a VC4 Service Between a Traditional NE and an ASON NE.................................................389
7.8.4 Creating the 1+1 VC4 Service Between a Traditional NE and an ASON NE......................................393
7.8.5 Creating 1+1 VC12 Services Between Two Traditional NEs with ASON NEs in Between................398
7.8.6 Creating 1+1 VC4 Services Between Two Traditional NEs with ASON NEs in Between..................402
7.9 Accessing a Traditional Network to an ASON Through Linear MSP...........................................................406
7.10 Managing Control Plane Alarms and Performance Events..........................................................................410
7.10.1 Querying Control Plane Alarms..........................................................................................................410
7.10.2 Suppressing Control Plane Alarms......................................................................................................410
7.10.3 Suppressing Control Plane Alarm Events...........................................................................................411
7.10.4 Querying the Performance of the Control Plane..................................................................................412
7.10.5 Monitoring the Control Plane Performance.........................................................................................412
7.10.6 Setting the Auto-Report Status of the Control Plane Performance Data.............................................413
7.10.7 Setting the Control Plane Performance Threshold .............................................................................414
8 Routine Maintenance for an ASON Network.....................................................................415

8.1 Precautions for Routine Maintenance.............................................................................................................416
8.2 Routine Maintenance List...............................................................................................................................418
8.3 Routine Maintenance Items............................................................................................................................419
8.3.1 Backing Up Device Data to the NMS Server or the NMS Client.........................................................419
8.3.2 Checking ASON Services.....................................................................................................................420
8.3.3 Querying the Alarms of an ASON Trail................................................................................................421
8.3.4 Querying Control Plane Alarms............................................................................................................423
8.3.5 Querying Control Link Alarms..............................................................................................................423
8.3.6 Querying TE Link Alarms.....................................................................................................................424
8.3.7 Querying the Performance of the Control Plane....................................................................................425
9 Handling ASON Network Failures.......................................................................................427

9.1 Handling Link Failures...................................................................................................................................428
9.1.1 Handling Impassable Control Channels................................................................................................428
9.1.2 Handling Impassable Control Links......................................................................................................431
9.1.3 Handling Impassable TE Links.............................................................................................................431
9.1.4 Handling Degraded TE Links................................................................................................................433
9.2 Handling the Failure in Creating Trails..........................................................................................................434
9.2.1 Handling the Failure of Route Calculation............................................................................................434
9.2.2 Handling the Failure of Label Allocation..............................................................................................435
Issue 03 (2011-09-15) Huawei Proprietary and Confidential xv

9.2.3 Handling the Cross-Connection Control Failure...................................................................................436

9.2.4 Handling an LSP Creation Timeout Fault.............................................................................................437
9.2.5 Handling the Fault with Unavailable Wavelengths at the Service Adding/Dropping Ports..................438
9.2.6 Handling an Optical Parameter Verification Failure.............................................................................439
9.3 Handling Trail Interruption............................................................................................................................440
9.3.1 Methods of Identifying a Service Interruption Fault.............................................................................440
9.3.2 Handling the Fault of Trail Interruption................................................................................................441
9.3.3 Handling the Failure to Reroute Services..............................................................................................441
10 Alarm Reference......................................................................................................................443
10.1 Alarm Suppression Relationships.................................................................................................................444
10.2 Control Plane Alarms(OTN)........................................................................................................................445
10.3 Control Plane Alarms(OCS).........................................................................................................................449
10.4 Alarm Handling(OTN).................................................................................................................................450
10.4.1 CPC_CC_DOWN................................................................................................................................450
10.4.2 CPC_NODE_ID_CONFLICT.............................................................................................................452
10.4.3 CPC_NODE_ID_ERR.........................................................................................................................454
10.4.4 CPC_OSPF_AUTH_ERR...................................................................................................................455
10.4.5 CPC_OSPF_CL_DOWN.....................................................................................................................456
10.4.6 CPC_OSPF_NB_DOWN....................................................................................................................458
10.4.7 CPC_RSVP_AUTH_ERR...................................................................................................................460
10.4.8 CPC_RSVP_NB_DOWN....................................................................................................................461
10.4.9 CPW_OCH_LSPOVPN_MM.............................................................................................................463
10.4.10 CPW_OCH_SER_INT......................................................................................................................465
10.4.11 CPW_OCH_SER_NOTOR...............................................................................................................467
10.4.12 CPW_OCH_SER_RRTLOCK..........................................................................................................469
10.4.13 CPW_OCH_SER_SLADEG.............................................................................................................471
10.4.14 CPW_OCH_SER_SYNFAIL............................................................................................................473
10.4.15 CPW_ODUk_SER_INT....................................................................................................................475
10.4.16 CPW_ODUk_SER_NOTOR.............................................................................................................477
10.4.17 CPW_ODUk_SER_RRTLOCK........................................................................................................479
10.4.18 CPW_ODUk_SER_SLADEG...........................................................................................................480
10.4.19 CPW_ODUk_SER_SYNFAIL..........................................................................................................482
10.4.20 CPW_ODUk_TEL_DEG..................................................................................................................484
10.4.21 CPW_ODUk_TEL_DOWN..............................................................................................................486
10.4.22 CPW_ODUk_TEL_ODURMIS........................................................................................................488
10.4.23 CPW_ODUk_TEL_PATHMIS.........................................................................................................490
10.4.24 CPW_OMS_TEL_DEG....................................................................................................................492
10.4.25 CPW_OMS_TEL_DOWN................................................................................................................493
10.4.26 CPW_OMS_TEL_EXHAUST..........................................................................................................496
10.4.27 CPW_OMS_TELOVPN_MM...........................................................................................................498
10.4.28 CPW_OMS_TEL_OCHMIS.............................................................................................................500
10.4.29 CPW_OMS_TEL_PATHMIS...........................................................................................................501
Issue 03 (2011-09-15) Huawei Proprietary and Confidential xvi

10.4.30 CPW_OTUk_TEL_DEG...................................................................................................................503
10.4.31 CPW_OTUk_TEL_DOWN...............................................................................................................505
10.4.32 CPW_OTUk_TEL_ODURMIS.........................................................................................................507
10.4.33 CPW_OTUk_TEL_PATHMIS.........................................................................................................509
10.4.34 CPW_SER_XC_EXCEPT.................................................................................................................511
10.5 Alarm Handling(OCS)..................................................................................................................................512
10.5.1 CP_ASER_SYNC_FAIL.....................................................................................................................512
10.5.2 CP_FIBER_CONNECT_FAULT.......................................................................................................515
10.5.3 CP_LSP_NO_PRERRT.......................................................................................................................516
10.5.4 CP_LSP_OVPN_MM.........................................................................................................................517
10.5.5 CP_MSP_EWUOVPN_MM...............................................................................................................520
10.5.6 CP_MSP_WPOVPN_MM..................................................................................................................521
10.5.7 CP_REROUTE_LOCK.......................................................................................................................523
10.5.8 CP_SRV_INT......................................................................................................................................525
10.5.9 CP_SER_NOT_OR.............................................................................................................................526
10.5.10 CP_SER_SLA_DEG.........................................................................................................................527
10.5.11 CP_TEL_DEG...................................................................................................................................531
10.5.12 CP_TEL_DOWN...............................................................................................................................533
10.5.13 CP_TEL_MSP_MIS..........................................................................................................................536
10.5.14 CP_TEL_OVPN_MM.......................................................................................................................538
10.5.15 CP_TEL_PATH_MIS.......................................................................................................................540
10.5.16 CP_TEL_EXHAUST........................................................................................................................545
10.5.17 CPC_CC_DOWN..............................................................................................................................546
10.5.18 CPC_NODE_ID_CONFLICT...........................................................................................................548
10.5.19 CPC_NODE_ID_ERR.......................................................................................................................550
10.5.20 CPC_OSPF_AUTH_ERR.................................................................................................................551
10.5.21 CPC_OSPF_CL_DOWN...................................................................................................................552
10.5.22 CPC_OSPF_NB_DOWN..................................................................................................................554
10.5.23 CPC_RSVP_AUTH_ERR.................................................................................................................556
10.5.24 CPC_RSVP_NB_DOWN..................................................................................................................557
A Glossary......................................................................................................................................560
Issue 03 (2011-09-15) Huawei Proprietary and Confidential xvii

ASON User Guide 1 About the ASON
1 About the ASON
About This Chapter
The ASON, the automatically switched optical network, is a new generation of the optical
transmission network, all called ASON optical network. This section describes some basic
concepts of the ASON and application of the ASON software.
1.1 Overview
The ASON software provided by Huawei can be applied to the OptiX OSN series products to
support the evolution from traditional network to ASON network. It complies with the ITU and
IETF ASON/GMPLS-related standards.
1.2 ASON Software and ASON Functions
Huawei provides the software on the ASON control plane, which implements the functions such
as network callings and connections and dynamic control of the transport plane through signaling
switching.
1.3 Automatic Discovery of Topologies and Resources
On an ASON network, link resources, network topologies, and fibers between sites can be
automatically discovered, and then a network map is automatically generated. The ASON
software dynamically obtains the resource status of the wavelength/sub-wavelength services in
real time, including the occupied and idle resources, providing a quick approach to know the
current network capacity.
1.4 Creation and Deletion of the ASON Trail
The RSVP-TE signaling is needed during the process of creation, deletion, change and rerouting
of the ASON trail.
1.5 OTN ASON Feature
The OptiX OSN WDM series products of Huawei can provide the OTN ASON function after
the ASON software is loaded.
1.6 OCS ASON Feature
The OptiX OSN series products of Huawei can provide the OCS ASON function after the ASON
software is loaded.
1.7 Optical-Layer and Electrical-Layer ASON Services
Issue 03 (2011-09-15) Huawei Proprietary and Confidential 1

The ASON software provides the wavelength-level ASON services at the optical layer and sub-
wavelength level ASON services at the electrical layer. Hence, customers can implement flexible
service grooming at different layers.

1.1 Overview
The ASON software provided by Huawei can be applied to the OptiX OSN series products to
support the evolution from traditional network to ASON network. It complies with the ITU and
IETF ASON/GMPLS-related standards.
1.1.1 Background and Advantages

Compared with the WDM network, the transmission network that applies the new ASON
technology shows advantages in service configuration, bandwidth utilization and protection
schemes.
In the traditional transmission network, the WDM transmission equipment functions as fibers.
Currently, the WDM transmission equipment also carries services. As a result, more
requirements are for the operability of the WDM equipment. The traditional network has the
following problems:
l The service configuration is complex and capacity expansion or service provision takes a
long period.
l The bandwidth utilization is of a low rate and low efficiency. In a ring network, half of the
bandwidth should be reserved.
l Just a few protection schemes are available and the performance of self-healing protection
is poor.
The ASON has been developed to solve these problems. This technology involves signaling
switching and a control plane to enhance its network connection management and recovery
capability. It supports end-to-end service configuration and the service level agreement (SLA).
Service Configuration
Traditional WDM networks are generally chains and rings. The trails and timeslots of their
services are manually configured ring by ring and point by point, which consumes a lot of time
and effort. As networks become increasingly large and complicated, this service configuration
mode cannot meet the rapidly increasing user demands.
The ASON successfully solves this problem by end-to-end service configuration. To configure
a service, you only need to specify its source node, sink node, bandwidth requirement and
protection type; the network automatically performs the required operations.
Bandwidth Utilization
Traditional WDM optical transmission networks have a large amount of resources reserved and
lack advanced service protection, and the restore and routing functions. In contrast, with the
routing function the ASON can provide protection by reserving fewer resources, thus increasing
network resource utilization.
Protection and Restoration

Chain and ring are the main topologies used in a traditional WDM network. Optical line
protection or board-level protection are the main protection schemes for the services. In ASON,
mesh is the main topology. Besides protections, the dynamic restoring function is available to

restore the services dynamically. In addition, when there are multiple failures in a network, the
services can be restored as many as possible.
According to the difference in the service restoration time, multiple service types are defined in
ASON networks to meet different customer requirements.
1.1.2 Features of the ASON

As a new technology on the transmission network, the ASON has its own features.
Compared with the traditional network, the ASON has the following features:
l Supports the route calculation strategy that is based on optics parameters and eliminates
the route that does not comply with optics parameters automatically.
l Supports the automatic adjustment of wavelengths during rerouting or optimization, which
solves the wavelength conflict problem. (For OTN network)
l Wavelengths can be automatically allocated for newly created services.
l Configures end-to-end services automatically.
l Discovers the topology automatically.
l Provides mesh networking that enhances the survivability of the network.
l Supports different services which are provided with different levels of protection.
l Provides traffic engineering and dynamically adjusts the network logic topology in real
time to optimize the configuration of network resources.
1.1.3 Huawei OTN ASON Solution

Huawei provides detailed OTN ASON solutions for different layers.
The OTN ASON solution provided by Huawei involves the following products:
l Control plane software: OptiX GSP
l Network management software: iManager U2000
l Equipment on the transport plane: OptiX OSN series equipment
NOTE
The OTN ASON solution provided by Huawei includes optical-layer (OTN_O) and electrical-layer
(OTN_E) ASON services. The optical-layer ASON service achieves OCh-level service grooming and the
electrical-layer ASON service achieves ODUk-level service grooming. Users can determine whether to
choose optical-layer or electrical-layer ASON based on the network situations and service requirements.
Figure 1-1 illustrates the relation among them.

Figure 1-1 Huawei ASON model

Network management
system
Contol plane supported by

OptiX GCP/GSP software
ASON composed
of OSN series
equipment
Currently, Huawei can provide the integral ASON metropolitan transport solution formed by
the OptiX OSN 8800 and OptiX OSN 6800, as shown in the Figure 1-2. The mesh network can
be used in the short long-haul to perform the flexible service grooming. For the ASON products
for different layers, refer to the Table 1-1.

Figure 1-2 ASON metropolitan solution (OTN networking)
Area
backbones
OptiX OSN 8800 T64

OptiX OSN 8800 T32
Short long-hual
OptiX OSN 8800 T16

OptiX OSN 6800
Local networks and
metropolitan core layers
ASON NE
Internet data center
Multi-tenant building
Enterprise
Banks and financial institutions
Intelligent residential community
Table 1-1 ASON WDM NE in the OptiX OSN series products

ASON NE Remarks
OptiX OSN 8800 T64 and ASON NE in short long-haul

OptiX OSN 8800 T32
OptiX OSN 8800 T16 and ASON NE in local network and metropolitan core layers
OptiX OSN 6800
NOTE
In the actual networking of the ASON WDM series products, the reconfigurable optical add/drop
multiplexer board (such as ROAM, WSMD2, RMU9, WSD9, WSM9, WSMD9 and WSMD4) needs to
be configured to implement the automatic rerouting and restoration of WDM ASON OCh trail.
1.1.4 Huawei OCS ASON Solution

Huawei provides detailed OCS ASON solutions for different layers.
The OCS ASON solution provided by Huawei involves the following products:

l Control plane software: OptiX GSP

l Network management software: iManager U2000
l Equipment on the transport plane: OptiX OSN series equipment
Figure 1-3 illustrates the relation among them.
Figure 1-3 Huawei ASON model

Network management
system
Contol plane supported by

OptiX GCP/GSP software
ASON composed
of OSN series
equipment
The OptiX OSN 8800 can be networked with the NG SDH/PTN equipment or data
communication equipment to provide a complete transport solution. This solution is mainly
applied to OCS networking, as shown in Figure 1-4.

Figure 1-4 ASON transport solution (OCS networking)

OptiX OSN 9500 OptiX OSN 8800 OptiX OSN 9500
Backbone layer
OptiX OSN 3500 OptiX OSN 3500
Convergence layer
OptiX OSN 1500 OptiX OSN 2500
Access layer
GSM/CDMA/
PSTN Ethernet ... ATM DDN
WCDMA
Table 1-2 OptiX OSN series products
ASON NE Applied at
OptiX OSN 8800 Backbone layer
OptiX OSN 3500 Convergence layer
OptiX OSN 3500 II Convergence layer
OptiX OSN 2500 Access layer
OptiX OSN 1500 Access layer
1.1.5 Introduction and Development of the OTN ASON

The concepts and standards of the ASON appear on the premise that the traditional SDH
transmission system is widely used. The reasonable introduction schemes are necessary.
Introduction Scheme
Two basic introduction schemes are described as follows.
l To create an ASON network:

When the backbone network and MAN need to expand the capacity, you can consider
creating the ASON network.
l To upgrade a traditional WDM network to an ASON network:
If Huawei OptiX OSN series products are deployed in existing network, new software can
be loaded to upgrade the network to an ASON network. If NEs on the existing network can
be used to deploy ASON features, this scheme does not require new equipment and the
network can be smoothly upgraded. If NEs on the existing network cannot be used to deploy
ASON features, the network needs to be reconstructed and then upgraded.
Interconnection between ASON and WDM networks

A great number of WDM networks are currently in service. Hence, for the development of the
ASON, the interconnection between ASON and WDM networks becomes a key factor.
The ASON and WDM networks share the same service granularities, such as ODU2, and ODU1.
Hence, the interconnection between ASON and WDM networks is not a problem from the
viewpoint of service.
The ASON and WDM networks can be uniformly managed only if the equipment in the network
is the Huawei OptiX series equipment.
1.1.6 Introduction and Development of the OCS ASON

The concepts and standards of the ASON appears on the premise that the SDH fiber transmission
system is widely used. The reasonable introduction schemes and development schemes are
necessary. As the ASON concepts and standards continue to develop, and as considerable SDH
fiber transmission systems already exist, the introduction schemes and development schemes
become very important.
Introduction Scheme
Two basic introduction schemes are described as follows.
l To create an ASON network:
When the backbone network and MAN need to expand the capacity, you can consider
creating the ASON network.
l To upgrade a traditional SDH network to an ASON network:
If Huawei OptiX OSN series products are deployed in existing network, new software can
be loaded to upgrade the network to an ASON network. If NEs on the existing network can
be used to deploy ASON features, this scheme does not require new equipment and the
network can be smoothly upgraded. If NEs on the existing network cannot be used to deploy
ASON features, the network needs to be reconstructed and then upgraded.
Interconnection between ASON and SDH

A great number of SDH networks are currently in service. Hence, for the development of the
ASON, the interconnection between ASON and SDH networks becomes a key factor.
The ASON and SDH networks share the same service granularities such as VC-4, VC-3 and
VC-12. Hence, the interconnection between ASON and SDH networks is not a problem from
the viewpoint of service.
The ASON and SDH networks can be uniformly managed only if the equipment in the network
is the Huawei OptiX series equipment.

1.2 ASON Software and ASON Functions

Huawei provides the software on the ASON control plane, which implements the functions such
as network callings and connections and dynamic control of the transport plane through signaling
switching.
1.2.1 Basic Concepts of ASON

The basic concepts related to the ASON are the label switched path (LSP) and rerouting.
ASON
ASON is a new generation optical network that has the following features:
l Customers launch a service request dynamically.
l Routes are selected automatically.
l Signaling controls the creation and removal of connections.
l Network connections are automatically and dynamically completed.
l Switching and transmission are integrated into one system.
LSP
Label switched path (LSP) is the path ASON services pass through. In an ASON, to create ASON
services is to create LSPs. On U2000, LSP is also called ASON Trail.
WDM ASON Trail

WDM ASON Trail is classified into WDM ASON OCh Trail and WDM ASON ODUk Trail.
See Figure 1-5.
l The WDM ASON OCh trail can be created when there are sufficient OCh TE link resources.
l The WDM ASON ODUk trail can be created when there are sufficient TE link resources
where the payload type is ODUk.
Figure 1-5 WDM ASON Trail
ODUk trail
OCh trail
OTU OM OA OA OD OTU

NOTE
The OptiX OSN 8800 does not support the WDM ASON client route.
Rerouting
Rerouting is a means of resuming services. For a non-revertive service, when an LSP is
disconnected, the source node queries and finds the best route to resume services. Then, the
initial node creates a new LSP to transmit the service. After creating a new LSP, the source node
deletes the original LSP.
NOTE
After a revertive service is rerouted, the original LSP is not deleted.

NOTE
For more information on service restoration, refer to 1.2.11 ASON Network Protection and
Restoration.
Rerouting Lockout
In some cases, rerouting is not required after failure of LSP. Then you need to set rerouting
lockout.
Rerouting Policy
Diamond and silver services all support the several rerouting polices. You can flexibly choose
a rerouting policy and properly use network resources according to different network conditions.
l Overlapping policy
During rerouting, the route of the new LSP overlaps the original route whenever possible.
This policy helps save network resources. When bandwidth resources are insufficient, the
service gets more chances to reroute successfully.
l Separating policy
During rerouting, the route of the new LSP is separated from the original route whenever
possible. This policy is applicable to a network with sufficient link resources.
l Best route policy
During rerouting, the best route is computed for the new LSP. Whether the new or old route
resources are utilized again is not considered. This policy chooses a route with the minimum
cost as the new route after rerouting according to network conditions.
l Simulated span restoration policy
During rerouting, the services must reuse the original routes without involving faulty spans.
End-to-end rerouting is enabled only when rerouting on the faulty spans fails, and thus
service route can be controlled and managed more easily.
NOTE
The rerouting policy can be set on the U2000 according to actual conditions.
1.2.2 Structure of the ASON Transmission Network

the ASON has three planes: the control plane, the transport plane, and the management plane.
The most outstanding feature of the ASON compared with the traditional optical network lies
in the introduction of an independent control plane to the transport network. The control plane

brings the revolutionary change to the entire optical network and enables the latter to have the
ability to automatically implement network bandwidth allocation and dynamically configure
trails.
Functions of the three planes of the ASON are as follows:
l Control plane
The control plane mainly controls callings and connections of the network and dynamically
controls the transport plane through signaling exchange (involving setup, release,
monitoring, and maintenance of connections, and provision of protection restoration in case
of a connection failure).
l Transport plane
The traditional WDM network is the transport plane. It transmits optical signals, configures
cross-connection and protection switching for optical signals, and guarantees the reliability
of all optical signals. The switching operations on the transport plane are performed under
the control of the management plane and control plane.
l Management plane
The management plane is a complement to the control plane. It maintains the transport
plane, the control plane and the entire system. On this plane, the end-to-end configuration
can be supported. Its functions include performance management, fault management,
configuration management and security management. The functions of the management
plane are coordinated with the functions of the control plane and transport plane.
As shown in Figure 1-6, the three planes are independent but they interact with each other
through interfaces and defined functions. The management plane communicates with the control
plane and the transport plane through network management interfaces (NMIs). The control plane
communicates with the transport plane through connection control interfaces (CCIs).
Figure 1-6 Three planes of the ASON
NMI
Control plane
Management
CCI plane
NMI
Transmission plane
1.2.3 Location of ASON Software

The ASON software is included in the NE software.

Figure 1-7 shows where ASON software is located in the whole product software system. The
ASON software and NE software run on the SCC board, whereas the board software and network
management (NM) software run on the boards and NM computer respectively, to implement
corresponding functions. The structure of the software for all the OptiX OSN series products is
the same. You can upgrade traditional versions to ASON by loading the NE software that
contains ASON software. Some boards should be upgraded.
Figure 1-7 Software structure of the OptiX OSN series
NM software
NE software ASON software
Board software
1.2.4 Structure of ASON Software

The ASON software is formed by several modules. Each module implements different functions.
According to ITU-T recommendations, ASON has three planes: a control plane, a management
plane, and a transport plane. The management plane refers to the NM layer, and the transport
plane refers to the WDM network. ASON software is used in the control plane, using LMP,
OSPF-TE, and RSVP-TE.
Table 1-3 Acronyms and abbreviations
Acronym Full Spelling
RSVP-TE Resource Reservation Protocol-Traffic Engineering
OSPF-TE Open Shortest Path First-Traffic Engineering
LMP Link Management Protocol
CSPF Constrained Shortest Path First
Figure 1-8 shows the structure of the ASON software, which consists of a signaling module, a
routing module and a cross-connection management module.

Figure 1-8 Structure of ASON software
ASON software
NMS Signaling
module NE
Cross-connection software
management
module
Routing module
Link management module
Link Management Module

The link management module uses the LMP protocol to perform the following functions.
l Creates and maintains the control channels

l Checks component links and TE links
Signaling Module
The signaling module uses the RSVP-TE protocol to create or remove services according to the
requests from users, and synchronizes and restores services as needed.
Routing Module
The routing module uses the OSPF-TE protocol to perform the following functions.
l Collects and floods TE link information.

l Collects and floods control link information.
l Calculates control route.
The routing module mainly uses the CSPF protocol to perform the following function:
Compute service routes based on information about network-wide TE links
Cross-connection Management Module

The cross-connection management module performs the following functions.
l Creates/Deletes cross-connections.
l Reports link state and alarms.

1.2.5 ASON Standards

Huawei implements the functions of ASON, which comply with the recommendations of ITU-
T and IETF.
ITU-T Standards
International Telecommunication Union-Telecommunication Standardization Sector (ITU-T) is
an authoritative organization in the telecommunication standardization field. Its standardization
work covers all the telecommunication domains. Regarding the ASON optical network domain,
ITU-T presents the automatically switched transmission network (ASTN) and automatically
switched optical network (ASON) concepts.
Currently, the ASTN and ASON indicate the ASON optical network. Different from other
standardization organizations, ITU-T applies the traditional top-to-down design scheme. ITU-
T attaches much importance to the system structure and defines the specific protocols and
regulations on the basis of the overall structure. ITU-T G.8080 defines the overall structure of
the GCP/ASON network. ITU-T presents a series standards related to the ASON optical network
on the basis of ITU-T G.8080. The series standards include G.7713 for call and connection
management, G.7714 for auto-discovery technology, G.7712 for DCN, G.7715 for routing and
G.7716 for link management.
Figure 1-9 shows the ITU-T standards related to the ASON optical network and relations among
them.
Figure 1-9 ITU-T standards related to the ASON optical network
NOTE
Huawei ASON/GMPLS Solution adopt the recommendatory signaling protocol: RSVP-TE. So the Huawei
does not use CR-LDP.
IETF Standards
Internet Engineering Task Force (IETF) is an open international standardization organization
set up jointly by Internet designers, operators, equipment vendors and researchers. IETF is
devoted to the definition of standards related to Internet and attaches much importance to
protocols and technologies. The multi-protocol label switching (MPLS) protocol is widely
accepted as the basis of the standards for the next-generation data transmission.

IETF features in work openness. All protocols and standards it released are fully open and thus
IETF draws the attention of the vendors and research institutions. At present, IETF focuses on
the study of improving the existing protocols in the field of ASON and thus further extends to
the optical transmission networks. IETF takes the lead in launching the GCP architecture and
defines the signaling and routing protocols of ASON related to GCP. Part or all of these protocols
have been adopted by ITU-T.
The protocols of ASON IETF studies include:
l Signaling protocol(GCP-RSVP-TE/CR-LDP)
l Routing protocol (GCP-OSPF-TE/IS-IS)
l Link management protocol(LMP)
For the detailed IETF recommendations, refer to Table 1-4.
Table 1-4 IETF standards related to the ASON optical network

Standard Description
RFC 3945 Generalized Multi-Protocol Label Switching (GMPLS)

Architecture

Signaling Functional Description

Signaling Resource Reservation Protocol-Traffic
Engineering (RSVP-TE) Extensions
RFC 4204 Link Management Protocol (LMP)
RFC 4258 Requirements for Generalized Multi-Protocol Label

Switching (GMPLS) Routing for the Automatically Switched
Optical Network (ASON)
RFC 4203 OSPF Extensions in Support of Generalized Multi-Protocol

Label Switching (GMPLS)
RFC 4257 Framework for Generalized Multi-Protocol Label Switching

(GMPLS)-based Control of Synchronous Digital Hierarchy/
Synchronous Optical Networking (SDH/SONET) Networks
RFC 4426 Generalized Multi-Protocol Label Switching

(GMPLS).Recovery Functional Specification
1.2.6 ASON Protocol

Huawei ASON applies the link management protocol (LMP) as the link management protocol,
OSPF-TE as the routing protocol, and RSVP-TE as the signaling protocol.
The following sections describe the functions of these protocols in an ASON network.
LMP
The LMP performs the following functions in an ASON network.

l Creating and maintaining the control channels between adjacent nodes.

The following is the procedure of creating control channels.
– See Figure 1-10. When two adjacent ASON NEs start up, the LMP uses the OTN
overheads or the DCC channels of the OSC to transmit messages. Node 1 transmits
messages to Node 2, which performs the check to the received messages. If the messages
pass the check, Node 2 returns messages to Node 1. If the messages do not pass the
check, Node 2 returns a message to Node 1, indicating that the messages fail to pass the
check. In this way, Node 2 waits for another check. Hence, a control channel between
the two adjacent nodes is created.
– After the control channel is created, the two nodes store the information about the control
channel and identify the control channel according to the ID.
Figure 1-10 Creating control channels

LMP LMP
Message
Node 1 Node 2
Message
l Verifying component links and TE links.

The following is the procedure of verifying component links and TE Links.
– After the control channels are configured, an attribute consistency check is performed
to the TE links to see if the information is identical at both ends of dynamically
discovered or manually configured TE links. If the check succeeds, the OSPF protocol
is used to flood the information of the TE links to the entire network.
– As shown in Figure 1-11, Node 1 transmits messages and the content to be checked to
Node 2, which checks if it has the same information and returns the check result to Node
1.
– On the OCS network, after a logical board is created for an ASON NE, the ASON
software creates component links for the optical interfaces of the board. Then, the
attributes of component links are configured according to the attributes of the optical
interface. The attributes include slot number, optical interface number, bandwidth and
node ID.
– On the OCS network, after component links are created, the ASON software creates
corresponding TE links. In this case, the LMP starts to verify the component links and
TE links. The LMP performs the verification to verify the consistency of information
at both ends of a link. As shown in Figure 1-11, Node 1 transmits messages and the
content to be checked to Node 2, which checks if it has the same information and returns
the check result to Node 1. If the verification shows consistency, the OSPF-TE can then
flood the information about the TE links to the entire network.

Figure 1-11 Verifying component links and TE links

LMP LMP
Message
Node 1 Node 2
Message
OSPF-TE
The control plane of Huawei ASON applies the OSPF-TE, which is an extended protocol for
OSPF, and performs the following functions.
l Creates and maintains control links.
l Creates neighbor relations.
l Floods and collects the information about the control links on the control plane. According
to the information, the protocol then generates the information about the routes that are
required for forwarding messages on the control plane.
l Floods and collects the information about the TE links on the transport plane. The protocol
then generates the information about the network service topologies for service trail
computation.
RSVP-TE
The RSVP-TE is a protocol for resource reservation. It is a type of signaling. In terms of traffic
engineering, the RSVP is extended to RSVP-TE. The RSVP-TE mainly supports the following
functions:
l LSP creation
l LSP deletion
l LSP attribute modification
l LSP rerouting
l LSP trail optimization
Protocol Authentication
An external entity may modify the OSPF-TE protocol packets of the network, counterfeit a node
of this network and transmit packets, or receive the packets transmitted by nodes in the network
and repeat the attack. To prevent these network insecurities, the ASON provides the function to
authentication protocols. In an ASON domain, the RSVP and OSPF-TE protocols are
authenticated.
The RSVP authentication is configured for nodes and the OSPF-TE authentication for
interconnected interfaces (slots and optical interfaces).
The authentication can be non-authentication, plain text authentication or MD5 authentication.

l Non-authentication: No authentication is required in this mode.

l Plain text authentication: To verify the preset password. The authentication code must be
a character string with no more than eight characters.
l MD5 authentication: To verify the information that is encrypted by the MD5 algorithm.
The authentication code must be a character string with no more than 64 characters.
NOTE
The RSVP does not support plain text authentication.
The check succeeds only when the authentication modes and passwords of adjacent nodes are
the same.
1.2.7 OTN ASON Links

OTN ASON Links include control tunnels, control links and TE links.
Control Channels
The LMP creates and maintains the control channel between NEs. The control channel then
provides a physical channel for the LMP packets. The control channels are classified into in-
fiber and out-fiber control channels. The in-fiber control channels automatically find and use
OTN overhead or the D4-D12 bytes of DCC. The out-fiber control channel uses the Ethernet
links, which should be manually configured.
The verification of TE links can be performed if the control channels are available between two
adjacent nodes.
At least one control channel should be present between two adjacent nodes. If several fibers
exist between adjacent nodes, several control channels can be created.
Control Links
Control links are the communication links created for the communication between the protocol
entities of NEs.
The OSPF control links are created and maintained by the OSPF protocol between two nodes.
The information of the OSPF control links is flooded to the entire network. In this way, each
NE can attain the information and then can form the control topology. The OSPF protocol of
each NE computes the shortest control routes to each NE according to the control topology. The
routes are then recorded in the forward table. The signaling RSVP then uses the routes to transmit
message packets.
By default, control links are created in fibers. Control links can also be created outside fibers on
the condition that the OSPF protocol of the Ethernet ports is enabled.
NOTE
Although the control links and control channels are created in the OTN overheads or DCC channels (D4-
D12), they differ in terms of functions and are independent of each other. The OSPF protocol floods the
information about the control links to the entire network. Each ASON NE stores the information about the
network-wide control links. The ASON NEs do not flood the information about the control channels to the
entire network. Each NE manages and stores the information only about its own control channels.
The OSPF and RSVP protocols transmit messages through the GCC or RES bytes of the OTN.
The gray part in Figure 1-12 indicates the RES byte of OTN overhead.

Figure 1-12 ASON protocol information uses the OTN overhead
3824
3825
4080
14
15
16
17
1
7
8
OTUk[V]
1 Alignm
OH
OPUk OH
Client Signal OTUk
3 ODUk OH FEC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 FAS SM RES
MFAS GCC0 RES JC
2 TCM TCM6 TCM5 TCM4

RES FTFL RES JC
ACT
3 TCM3 TCM2 TCM1 PM EXP RES JC
GCC1 GCC2 APS/PCC RES PSI NJO

4
TE Links
TE link is a traffic engineering link. An ASON NE transmits its bandwidth information to other
ASON NEs on the network in the format of a TE link through the LSA, so as to provide data
for route computation. The TE link is a concept of resources. Different boards generate different
TE links. TE links can be classified into the following types:
l OMS TE link
l OTUk TE link k = 1, 2, 3
l ODUk TE link k = 0, 1, 2, 3
Figure 1-13 shows the layered model of TE links.

Figure 1-13 Layered model of TE links
FIU OMS TE Link FIU
Line Unit Line Unit

OTUk TE Link
ODUk
OTUk
ODUk
OTUk
Tributary Unit ODUk TE Link Tributary Unit
ODUk
ODUk
The corresponding relation between each layer of TE link and its payload type is as follows:
l OMS TE link: bears the OCh.
l OTU3 TE link: bears the ODU3.
l ODU3 TE link: bears the ODU1/ODU2
l ODU2 TE link: bears the ODU1
l ODU1 TE link: bears the ODU0
Certain types of boards are taken as examples to describe the creation process of TE links at
various layers.
See Figure 1-14. After the wavelength trail is created between the FIU boards at two ASON
NEs, the OMS TE link is generated automatically.
See Figure 1-14. After the wavelength trail is created between the NS3 boards at two ASON
NEs, the OTU3 TE link and ODU3 TE link are generated automatically. The payload type of
the OTU3 TE link is ODU3. The payload type of the OTU3 TE link is ODU2.

Figure 1-14 OTU3 TE link and ODU3 TE link

NE1 NE2
NS3 NS3
ODU2 O O O O ODU2
F F
ODU2 D T T D ODU2
I I
ODU2 U U
U U
U U ODU2
3 3 3 3
ODU2 ODU2
O O
S S
C C
OCh TE link
OTU3 TE link
ODU3 TE link
See Figure 1-15. After the wavelength trail is created between the NS2 boards at two ASON
NEs, the OTU2 TE link and ODU2 TE link are generated automatically. The payload type of
the OTU2 TE link is ODU2. The payload type of the OTU2 TE link is ODU1. See Figure
1-15.
Figure 1-15 OTU2 TE link and ODU2 TE link

NE1 NE2
NS2 NS2
ODU1 O O O O ODU1
F F
ODU1 D T T D ODU1
I I
ODU1 U U
U U
U U ODU1
2 2 2 2
ODU1 ODU1
O O
S S
C C
OCh TE link
OTU2 TE link
ODU2 TE link

See Figure 1-16. The ODU1 TE link will be automatically created only after the ODU2 TE link
generates, and the cross-connection between the TOM and NS2 boards is created. The payload
type of the ODU1 TE link is ODU0.
Figure 1-16 ODU1 TE link

NE1 NE2
TOM XCS NS2 NS2 XCS TOM

LP1 ODU1 ODU1 ODU1 ODU1 LP1
O O O O O O O
O D
D D T T D D
D U
U U U U U U
U 0
0 2 2 2 2 1
1
ODU2 TE link
ODU1 TE link
1.2.8 OCS ASON Links

ASON Links include control tunnels, control links, component links and TE links.
Control Channels
The LMP creates and maintains the control channel between NEs. The control channel then
provides a physical channel for the LMP packets. The control channels are classified into in-
fiber and out-fiber control channels. The in-fiber control channels automatically find and use
OTN overhead or the D4-D12 bytes of DCC. The out-fiber control channel uses the Ethernet
links, which should be manually configured.
The verification of TE links can be performed if the control channels are available between two
adjacent nodes.
At least one control channel should be present between two adjacent nodes. If several fibers
exist between adjacent nodes, several control channels can be created.
Control Links
Control links are the communication links created for the communication between the protocol
entities of NEs.
The OSPF control links are created and maintained by the OSPF protocol between two nodes.
The information of the OSPF control links is flooded to the entire network. In this way, each
NE can attain the information and then can form the control topology. The OSPF protocol of
each NE computes the shortest control routes to each NE according to the control topology. The
routes are then recorded in the forward table. The signaling RSVP then uses the routes to transmit
message packets.

By default, control links are created in fibers. Control links can also be created outside fibers on
the condition that the OSPF protocol of the Ethernet ports is enabled.
NOTE
Although the control links and control channels are created in the OTN overheads or DCC channels (D4-
D12), they differ in terms of functions and are independent of each other. The OSPF protocol floods the
information about the control links to the entire network. Each ASON NE stores the information about the
network-wide control links. The ASON NEs do not flood the information about the control channels to the
entire network. Each NE manages and stores the information only about its own control channels.
The OSPF and RSVP protocols transmit messages through the GCC or RES bytes of the OTN.
The gray part in Figure 1-17 indicates the RES byte of OTN overhead.
Figure 1-17 ASON protocol information uses the OTN overhead
3824
3825
4080
14
15
16
17
1
7
8
OTUk[V]
1 Alignm
OH
2
OPUk OH
Client Signal OTUk

3 ODUk OH FEC
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 FAS SM RES
MFAS GCC0 RES JC
2 TCM TCM6 TCM5 TCM4

RES FTFL RES JC
ACT
3 TCM3 TCM2 TCM1 PM EXP RES JC
GCC1 GCC2 APS/PCC RES PSI NJO

4
TE Links
On the OCS network formed by the OptiX OSN 8800 equipment and NG SDH equipment, a TE
link is a traffic engineering link. The ASON NE sends its bandwidth information to other ASON
NEs through the TE link to provide data for route computation. As a type of resources, TE links
can be regarded as fibers that have bandwidth information and protection attributes. However,
the TE link does not correspond to a fiber respectively, because each fiber may correspond to
many TE links. Currently, a fiber can be configured with one TE link.
The resources of a TE link can be classified into three types: non-protection resources, working
resources, and protection resources.
l If the MSP is configured on some channels of a fiber, there are three types of resources.
For example, if a 10 Gbit/s (64 VC4s) optical interface is configured with a 2.5 Gbit/s MSP,
the TE links are allocated as follows.
– 1-8 VC4s are the working resources of the TE link.

– 33-40 VC4s are the protection resources of the TE link.

– The rest VC4s are non-protection resources of the TE link.
l If the MSP is configured completely in a fiber, there are only working and protection
resources in this fiber.
l If the MSP is not configured in a fiber, there are only non-protection resources in this fiber.
Component Links
Component link is a bandwidth unit smaller than a TE link. One TE link consists of only one
component link in the actual ASON software.
NOTE
Each ASON NE floods its own TE links to the whole network through OSPF-TE. Each NE obtains the
network-wide TE links. ASON NEs do not flood their own component links to the whole network. They
only manage and store their own component links.
1.2.9 Function Structure of the OTN ASON

An OTN ASON network consists of ASON NEs, TE links, domains and SPC (soft permanent
connections).
See Figure 1-18.
Figure 1-18 Function structure of the OTN ASON
ASON NE TE link
R1 R4
SPC
R2
R3
ASON domain : ASON NE

: User equipment
ASON NE
An ASON NE is one of the topology components in the ASON. An ASON NE has the following
functions in relation to a traditional NE. See Figure 1-19.

Figure 1-19 ASON NE (OTN networking)

ASON NE
Signaling Routing
( RSVP-TE ) ( OSPF-TE )
Link management protocol ( LMP )
Communication and control Traditional NE
WDM-side/Client- Wavelength WDM-side/Client-

side interface grooming side interface
Node ID is the unique identification of the ASON NE in the control plane. The format of the
node ID is the same as that of the IP address. But the node ID and the IP address of the NE must
be at different network sections.
As a unique identification for NEs on the transport plane, the node ID has the same meaning
regarding an ASON NE and a traditional NE.
The node ID, the NE ID, and the NE IP address are independent of one another.
TE Link
TE link is a traffic engineering link. The ASON NE sends its bandwidth information to other
ASON NEs through the TE link to provide data for route computation. One inter-station fiber
between two FIU boards can be configured with one TE link.
If the ODUk SPRing is configured in an ASON network, the TE links within the ODUk SPRing
can generate working resources and protection resources, which are corresponding to the
working unit and protection unit of the protection group. The TE links without ODUk SPRing
protection are non-protection resources.
ASON Domain
An ASON domain is a subset of a network, which is classified by function for the purpose of
route selection and management. An ASON domain consists of several ASON NEs and TE links.
One ASON NE belongs to one ASON domain.
SPC
In the case of soft permanent connection (SPC), the connection between the user and the
transmission network is configured directly by the NM. The connection within the transmission
network, however, is requested by the NM and then created by the NE's control plane through
signaling. When ASON service is mentioned, it usually refers to SPC.
Permanent connection (PC) is a service connection calculated beforehand and then created
through the NM by issuing a command to NE. A traditional OTN service is a PC.
Switched connection (SC) is a service connection requested by a terminal user (for example, a
router) and is then created in the ASON control plane through signaling.

CAUTION
ASON software only supports SPC. SC is not supported at present.
1.2.10 Function Structure of the OCS ASON

An OCS ASON network consists of ASON NEs, TE links, domains and SPC (soft permanent
connections).
See Figure 1-20.
Figure 1-20 Function structure of the OCS ASON
ASON NE TE link
R1 R4
SPC
R2
R3
ASON domain : ASON NE

: User equipment
ASON NE
An ASON NE is one of the topology components in the ASON. An ASON NE has the following
functions in relation to a traditional NE. See Figure 1-21.
Figure 1-21 ASON NE (OCS networking)

ASON NE
Signaling Routing
(RSVP-TE) (OSPF-TE)
Link management protocol(LMP)
Communication and control Traditional NE

Cross-
Line unit Line unit
connection

Node ID is the unique identification of the ASON NE in the control plane. The format of the
node ID is the same as that of the IP address. But the node ID and the IP address of the NE must
be at different network sections.
As a unique identification for NEs on the transport plane, the node ID has the same meaning
regarding an ASON NE and a traditional NE.
The node ID, the NE ID, and the NE IP address are independent of one another.
TE Link
TE link is a traffic engineering link. The ASON NE sends its bandwidth information to other
ASON NEs through the TE link to provide data for route computation. One inter-station fiber
can be configured with one TE link.
In OCS networking, the resources of a TE link can be classified into three types: non-protection
resources, working resources, and protection resources.
If the MSP is configured on some channels of a fiber, there are three types of resources. For
example, if a 10 Gbit/s (64 VC4s) optical interface is configured with a 2.5 Gbit/s MSP, the TE
links are allocated as follows.
l 1-8 VC4s are the working resources of the TE link.
l 33-40 VC4s are the protection resources of the TE link.
l The rest VC4s are non-protection resources of the TE link.
If the MSP is configured completely in a fiber, there are only working and protection resources
in this fiber.
If the MSP is not configured in a fiber, there are only non-protection resources in this fiber.
Component Link
Component link is a bandwidth unit smaller than a TE link. One TE link consists of only one
component link in the actual ASON software.
NOTE
Each ASON NE floods its own TE links to the whole network through OSPF-TE. Each NE obtains the
network-wide TE links. ASON NEs do not flood their own component links to the whole network. They
only manage and store their own component links.
ASON Domain
An ASON domain is a subset of a network, which is classified by function for the purpose of
route selection and management. An ASON domain consists of several ASON NEs and TE links.
One ASON NE belongs to one ASON domain.
SPC
In the case of soft permanent connection (SPC), the connection between the user and the
transmission network is configured directly by the NM. The connection within the transmission
network, however, is requested by the NM and then created by the NE's control plane through
signaling. When ASON service is mentioned, it usually refers to SPC.

Permanent connection (PC) is a service connection calculated beforehand and then created
through the NM by issuing a command to NE. A traditional SDH service is a PC.
Switched connection (SC) is a service connection requested by a terminal user (for example, a
router) and is then created in the ASON control plane through signaling.
CAUTION
ASON software only supports SPC. SC is not supported at present.
1.2.11 ASON Network Protection and Restoration

As the transmission network develops, the survivability of the network becomes a key factor in
the design, operation and maintenance of the network. An ASON network must have effective
and flexible protection and restoration schemes.
Difference between Protection and Restoration

Generally, protection involves the capacity pre-allocated among NEs. Simple protection
schemes such as the intra-board 1+1 protection and complex protection schemes such as the
ODUk SPRing protection can be configured. Protection only involves NEs and does not involve
the management system. The protection switching time is short and is generally not more than
50ms. The backup resources, however, cannot be shared in the network.
Generally, restoration involves the usage of any usable capacity among NEs. Even the extra
capacity of low priority can be used for restoration. When a service trail fails, the network
automatically searches for a new route and switches the services from the faulty route. The
algorithm that restores is the same as the algorithm that selects the trail. Restoration requires
spare resources in the network for service rerouting. Service rerouting involves the computation
of routes. Service rerouting involves the computation of routes, route switching, and re-creation
of cross-connections and routes. The service restoration takes a relatively long time.
Protection in an ASON Network

The traditional protection schemes can still be applied in an ASON network. When a fault occurs,
the protection switching is performed by the transport plane. In this case, the protection switching
does not involve the control plane.
Restoration in an ASON Network

In the case of an ASON network, the rerouting scheme is applied to restore services. When an
LSP fails, the source node computes the best trail for service restoration and then uses signaling
to create an LSP. Then, the new trail carries the services. For the non-revertive services, the
original LSP is deleted after the new LSP is created, however, for the revertive services, the
original LSP would not be deleted.
The advantages of rerouting are listed as follows.

l The services can be restored in a fast and automatic manner.
l After the technology for service restoration is applied in an ASON network, less spare
capacity is required when such an ASON network is restored in real time. The bandwidth

utilization is increased considerably. Generally, if a network involves more nodes, the

routes are more complicated and less spare resources are required.
l For OCS network, after the technology for service restoration is applied in an ASON
network, only 30% to 60% of spare capacity is required when such an ASON network is
restored in real time compared with the APS protection or a self-healing ring network. The
bandwidth utilization is increased considerably. Generally, if a network involves more
nodes, the routes are more complicated and less spare resources are required.
Service Restoration
The network restoring schemes can be classified into the centralized restoring scheme and
distributed restoring scheme according to the control mechanism. Huawei ASON applies the
distributed restoring scheme.
If the centralized restoring scheme is applied, a central control system is required to control the
entire network in a comprehensive manner. The central control system contains a very large
network database, which stores all the information about all nodes, links and spare resources.
When a link or a node fails, the fault information is reported to the central control system along
other routes. The central control system then computes a route to replace the faulty route
according to the information stored in the database. The central control system then issues control
commands to each node. A route is created to restore the services.
The distributed restoring scheme does not require any central control system. When a link fails,
the nodes at both ends of the faulty link detect the fault and flood this information to the entire
network. When a node fails, the adjacent nodes detect the fault and flood this information to the
entire network. All LSPs that are involved with the faulty link or node then reroute and new
LSPs are created to restore services.
In a WDM ASON network, when a fiber cut occurs, the WDM ASON OCh trail, WDM ASON
ODUk trail, and WDM ASON Client trail can restore separately. You can set the delay time for
the trail recovery. There is, however, no delay by default.
1.3 Automatic Discovery of Topologies and Resources

On an ASON network, link resources, network topologies, and fibers between sites can be
automatically discovered, and then a network map is automatically generated. The ASON
software dynamically obtains the resource status of the wavelength/sub-wavelength services in
real time, including the occupied and idle resources, providing a quick approach to know the
current network capacity.
For any change to network resources and topologies, such as adding/deleting links, changing
link parameters, adding/deleting network nodes, the ASON software may refresh the relevant
information in real time and inform the network management plane. This facilitates the network
expansion and network reconstruction.
1.3.1 Auto-Discovery of ASON NEs

In the ASON network, the OSPF protocol discovers ASON NEs automatically by sending the
protocol packets.
After discovering the neighbor NEs, the OSPF protocol floods the information about the
neighbor NEs to other NEs. In the end, every ASON NE in the domain has the information about
all ASON NEs in the entire ASON domain.

l When an ASON NE is added to an ASON network, other NEs are able to automatically
discover the new NE by using the OSPF protocol.
l When an ASON NE is removed from an ASON network (for example, power off the NE,
remove the SCC board, or shut down the physical channel), other NEs are able to
automatically detect the missing of this NE.
As shown in Figure 1-22, if two ASON NEs are added, the source topology on the U2000 is
automatically updated in real time.
Figure 1-22 TE link automatic discovery
R1 R4
New NE
R2
R3
:ASON NE
:User equipment
1.3.2 Auto-Discovery of Control Links

The ASON network automatically discovers the control links through the OSPF-TE protocol.
When the fiber connection (including the inter-station fiber automatically discovered and the
intra-station fiber manually configured) is complete in an ASON network, each ASON NE uses
the OSPF protocol to discover the control links and then floods the information about its own
control links to the entire network. See Figure 1-23. As a result, each NE obtains the information
of the control links in the entire network and also obtains the information about the network-
wide control topology. The following figure shows the details. Each ASON NE then computes
the shortest route to any ASON NE and writes these routes into the route forwarding table, which
is used for the signaling RSVP to transmit and receive packets.

Figure 1-23 Auto-discovery of control links
ASON Domain
When the fiber connection in the entire network is complete, ASON NEs automatically discover
the network-wide control topology and report the topology information to the management
system. See Figure 1-24.
Figure 1-24 Management of control topology
R1 R4
R2
R3
:ASON NE
: User equipment

1.3.3 Auto-Discovery of TE Links

The ASON network spreads the TE links to the entire network through the OSPF-TE protocol.
After an ASON NE creates a control channel between neighboring NEs through LMP, the TE
link verification can be started. Each ASON NE floods its own TE links to the entire network
through OSPF-TE. Each NE then gets the network-wide TE links, that is, the network-wide
resource topology.
ASON software detects change in the resource topology in real time, including the deletion and
addition of links, and the change in the link parameters, and then reports the change to U2000,
which performs a real-time refresh.
As shown in Figure 1-25, if one TE link is cut, the NM updates the resource topology displayed
on the NM in real time.
Figure 1-25 TE link auto-discovery
R1 R4
R2
R3
:ASON NE
:User Equipment
1.4 Creation and Deletion of the ASON Trail

The RSVP-TE signaling is needed during the process of creation, deletion, change and rerouting
of the ASON trail.
1.4.1 Creation of an LSP

The creation of an ASON trail is the creation of an LSP.

As shown in the Figure 1-26, create a bidirectional based on the wavelength services from NE1
to NE3.
Figure 1-26 Creation of an LSP
1 A bi-directional service is to
be created from NE1 to NE3
NE 2
7 4
3
NE 1
5 R2
6
R1 NE 3
2 Compute the route

from NE1 to NE3
The process of LSP creation is as follows:
1. Select the basic information such as service level on the NM, and click the source and sink
nodes that are NE1 and NE3. Respectively select the WDM-side optical interfaces of the
corresponding OTU boards and set the constraint condition of the route according to the
actual use. After confirming the information, the NM issues a command for service creation
to source node NE1.
2. NE1 invokes the CSPF algorithm to compute the most suitable service route according to
the control topology and service topology, which are obtained by the OSPF-TE through
convergence. For example, such a service route is NE1-NE2-NE3.
3. NE1 uses the RSVP-TE signaling protocol to transmit a message to NE2 according to the
service route. NE1 requests NE2 to reserve resources and create a cross-connection.
4. NE2 uses the RSVP-TE signaling protocol to transmit a message to NE3. NE2 requests
NE3 to reserve resources and create a cross-connection.
5. After NE3 creates the cross-connection, NE3 provides feedback message to NE2.
6. NE2 provides a feedback message to NE1.
7. NE1 receives the feedback message and stores the related information. NE2 then reports
the successful creation of the LSP to the management system.
Configuration Trait
The service configuration of the ASON WDM products has the following traits:
l Support the end-to-end bidirectional services of wavelength level based on the OCh trail.
The source and sink of the services must be the WDM-side optical interfaces of the OTU
board.

l Supports the end-to-end bidirectional services on the level of ODUk. That is, after you
specify the source/sink node, source/sink slot, source/sink port, source/sink channel ID,
service level, rate, and protection attributes, a sub-wavelength LSP is created automatically.
l The ODUk SPRing protection configuration can be added or deleted on the ASON ODUk
sub-wavelength service. The span ID, however, cannot be bound with the ASON service.
l Only notice the source and sink of the services but not the intermediate trail in the
configuration of the end-to-end wavelength services.
l Users can set the explicit node, link, the excluded node and link to restrict the service route.
l During route calculation, the ASON software considers the fiber distance, number of node
hops and available bandwidth according to the weights and user cost set by the users to
choose the best route.
1.4.2 Deletion of an LSP

The deletion of an LSP is the deletion of an ASON trail.
As shown in the Figure 1-27, the bidirectional service from NE1 to NE3 is deleted.
Figure 1-27 Deletion of an LSP
1 Delete a service
from NE1 to NE3
NE 2
6 3
2
NE 1
4 R2
5
R1 NE 3
The process for deleting an LSP is described as follows.
1. The management system issues a command to NE1. The requirement is that a bidirectional
service from NE1 to NE3 has to be deleted.
2. NE1 deletes the resources used by the LSP and uses the RSVP-TE signaling to transmit a
message to NE2.
3. After receiving the message from NE1, NE2 deletes the resources used by the LSP and
uses the RSVP-TE signaling to transmit a message to NE3.
4. After receiving the message from NE2, NE3 deletes the resources used by the LSP and
provides feedback message to NE2.
5. NE2 provides a feedback message to NE1.

6. NE1 receives the feedback message and stores the related information. NE2 then reports
the successful deletion of the LSP to the management system.
1.4.3 Rerouting of an LSP

After the trigger conditions of rerouting is detected, for the non-revertive services, a new LSP
is created and the original LSP is deleted, while for the revertive services, the original LSP would
be reserved.
Trigger Conditions of Rerouting

For the WDM service of the OTN networking, Table 1-5 lists the trigger conditions of LSP
rerouting.
Table 1-5 Trigger conditions of rerouting
Event Alarms That Trigger Rerouting

Type
SF The trigger conditions of optical-layer service rerouting include the following

alarms of the FIU board:
FIU: BD_STATUS, MUT_LOS
The trigger conditions of electrical-layer service rerouting include the following
alarms of the OTU board:
ODUk_PM_AIS, ODUk_PM_OCI, ODUk_PM_LCK, ODUk_PM_SSF
OTUk_AIS, OTUk_LOF, OTUk_LOM.
SD The trigger conditions of electrical-layer service rerouting include the following

electrical-layer service alarms of the OTU board:
ODUk_PM_DEG, ODUk_PM_EXC
OTUk_DEG, OTUk_EXC
NOTE
When the BIP detection is of the burst mode, the ODUk_PM_DEG or OTUk_DEG alarm
is reported. When the BIP detection is of the Poisson mode, the ODUk_PM_DEG,
OTUk_DEG, ODUk_PM_EXC or OTUk_EXC alarm is reported.
NOTE
The default state of SD conditions is Disabled. Hence, SD conditions can serve as the
trigger conditions of service rerouting only when the state of SD conditions is set to
Enabled.
NOTE
For details of the above alarms, refer to the Alarms and Performance Events Reference.
For the SDH service of the OCS networking the following alarms trigger the LSP rerouting:
R_LOS, R_LOF, B2_EXC, B2_SD, MS_AIS, MS_RDI, B3_EXC, B3_SD and AU_AIS.
Rerouting Process
When an LSP fails, the faulty LSP sends a rerouting request to the control plane to create a new
LSP. After receiving the request, the source node re-computes the route and allocates resources

for the new LSP. Then, the source node starts the creation of the new LSP. For details on the
process of creating the LSP, refer to 1.4.1 Creation of an LSP.
For a non-revertive service, after the new LSP is created, the original LSP is deleted. For details
on the process of deleting the LSP, refer to 1.4.2 Deletion of an LSP.
1.4.4 Change of an LSP

The change of an LSP is to improve an ASON trail.
The process for the change of an LSP is as follows.
1. The management system issues the command to the source node to change the LSP. After
receiving the request, the source node starts creating a new LSP. Refer to 1.4.1 Creation
of an LSP.
2. After the new LSP is created, the source node and the destination node start to switch the
cross-connection from the original LSP to the new LSP.
3. After the switching, the source node starts the process for the deletion of the original LSP.
Refer to 1.4.2 Deletion of an LSP.
1.5 OTN ASON Feature

The OptiX OSN WDM series products of Huawei can provide the OTN ASON function after
the ASON software is loaded.
1.5.1 End-to-End Service Configuration

The ASON network supports end-to-end service configuration, which is very convenient.
The ASON supports both WDM permanent connections and end-to-end ASON services. To
configure an ASON service, you only need to specify its source node, sink node, and protection
level. Service routing and cross-connection at intermediate nodes are all automatically
completed by the network. You can also set explicit node, excluded node, explicit link and
excluded link to constrain the service routing.
For example, consider the configuration of an ASON service between A and I in Figure 1-28.
The network automatically finds the A-D-E-I route and configures cross-connection at nodes A,
D, E and I. Although there is more than one route from A to I, the network calculates the best
route according to the configured algorithm. It is assumed that A-D-E-I is the best route.
The service is created as follows:
l Choose the bandwidth granularity.

l Choose the server level.
l Choose the source node.
l Choose the sink node.
l According to the service bandwidth and existing network resources, the ASON software
computes a proper service trail through the routing protocol.
l The ASON software sets up end-to-end service connections between sites through the
RSVP-TE signaling protocol.

Figure 1-28 End-to-end service configuration
R1 R4
E
I
D
F
C
A
B
H
G
R2
R3
:ASON NE
:User Equipment
The system support optical-layer ASON services that cross electrical regeneration NEs,
including:
l Creation, reroute, and optimization of SLA services, and wavelength-tunable ASON
services crossing electrical regeneration NEs.
l Conversion of crossing electrical regenerator service from static wavelength services to
ASON wavelength services and the vice versa.
l Pre-calculation of the optical-layer ASON services when the services cross electrical
regeneration NEs, including the creation, optimization, and restoration trail preset of SLA
services.
NOTE
The end-to-end wavelengths of the ASON services that cross the electrical regeneration NEs must be the
same.
The regeneration mode of the electrical regeneration NEs that the ASON services cross must be in the
transparent transmission mode and cannot be in the electrical cross-connect back-to-back mode.
1.5.2 Mesh Networking Protection and Restoration

The ASON provides mesh networking protection to enhance service survivability and network
security.
As a main networking mode of ASON, mesh features high flexibility and scalability. Compared
with the traditional WDM network, this networking mode also provides more than one recovery
route for each services so it can best utilize the network resources and enhance the network
security.
On a mesh network, to make the interrupted services available, you can immediately restore the
services through the rerouting mechanism in addition to the traditional protection scheme such
as 1+1 protection and shared protection scheme such as ODUk SPRing. That is, the mesh
network can support traditional protection schemes, the services that can be dynamically

restored, and service restoration mechanisms in case of protection failures. In this manner,
services are not interrupted only if the resources are available.
As shown in Figure 1-29, when the C-G link fails, to restore the service, the network calculates
another route from D to H and creates a new LSP to transmit the service.
Figure 1-29 Trail restoration
Recovery route
R1 R4
E
I
D
F
C
A
B
H
G
R2
R3
:ASON NE
:User Equipment
NOTE
In the case of the optical-layer ASON, a wavelength service must be in a channel from end to end. Hence,
the restoration trail with the same channel as that of the original trail may not be found during rerouting.
In this case, the ASON software supports the wavelength tunable function during rerouting. If an end-to-
end restoration trail with the same channel as that of the original trail cannot be found (for example, the
channel in a span is used), the ASON software will try to find another end-to-end restoration trail with
another channel so that the services can be restored to the greatest extent. Note that this function is available
only when the OTU board supports the wavelength tunable function.
1.5.3 SLA Classification of Services

The ASON network can provide services of different QoS to different clients.
The service level agreement (SLA) is used to classify services according to the service protection,
as listed in Table 1-6.

Table 1-6 Service level (WDM Service)

Service Protection Implement Switchi Rerouting Bandwidth
and ation ng Time Time Utilization
Restoratio Means
n Scheme
Diamond Protection intra-board 1 Less than The rerouting 33% (1+1

service and +1 50 ms time varies with protection. One
restoration protection, the network restoration trail
ODUk size, capacity is reserved.)
SNCP and and service
rerouting types.
Silver Restoration Rerouting - 75% (Dynamic

service rerouting and
shared mesh
protection,
resulting in high
utilization of
resources.
Consider a four-
dimensional
node as an
example. The
resource
utilization is
75% in the case
of a single fiber
break.)
Copper No - - - 100% (No

service protection protection.
No Theoretically,
restoration the resources
can be fully
occupied.)
Table 1-7 lists details of the TE links used by ASON services.
Table 1-7 TE links used by WDM ASON trails (WDM Service)

Service Level Working Resource Protection Non-Protection
of TE Link Resource of TE Resource of TE Link
Link
Diamond Not used Not used Used

service
Silver service Not used Not used Used
Copper service Not used Not used Used

1.5.4 Diamond WDM ASON Trail

Diamond WDM ASON trails have the best protection ability. When there are enough resources
on the network, diamond WDM ASON trails provide a permanent 1+1 protection for the WDM
ASON diamond ODUk trail. Diamond services are applicable to voice and data services, VIP
private line, such as banking, security and aviation.
A diamond service is a service with 1+1 protection from the source node to the sink node. It is
also called a 1+1 service. For a diamond service, there are two different LSPs available between
the source node and the sink node. The two LSPs should be as separate as possible. One is the
working LSP and the other is the protection LSP. The same service is transmitted to the working
LSP and the protection LSP at the same time. If the working LSP is proper, the sink node receives
the service from the working LSP; otherwise, from the protection LSP.
NOTE
The optical-layer diamond service specification is removed because of the following factors: (the optical-
layer diamond service solution will be replaced by the associated silver ASON service solution)
l When two LSPs share the same OTU, they use the same wavelength. Therefore, rerouting of the two
LSPs also must use the same wavelength, which makes finding a route very difficult.
l Service switching within 50 ms cannot be guaranteed when 40G OTUs are used because the TDC
adjustment requires more than 50 ms.
l When the service runs on the working LSP, the service performance monitoring is not available for
the backup LSP. This cannot ensure that the backup LSP is in normal state or available, which will
impair the service SLA.
Figure 1-30 shows a diamond service.
Figure 1-30 Diamond Services
Working LSP
R1 R4
E I
D
F
C
A
B
H
G
R2
R3
Protection LSP : ASON NE
: User equipment
NOTE
In the creation of diamond services, two LSPs are generated, which have the feature of 1+1 protection for
traditional WDM services. The working trail corresponds to the working LSP, and the protection trail
corresponds to the protection LSP. When the working trail fails, the protection switching is performed
through the traditional WDM 1+1 protection and then a new LSP is created through rerouting.

There are three types of diamond services.

l Permanent 1+1 diamond service: rerouting is triggered once an LSP fails.
l Rerouting 1+1 diamond service: rerouting is triggered only when both LSPs fail.
l Non-rerouting diamond service: rerouting is never triggered.
Table 1-8 lists the attributes of the permanent 1+1 diamond service.
Table 1-9 lists the attributes of the rerouting 1+1 diamond service.
Table 1-10 lists the attributes of the non-rerouting 1+1 diamond service.
Table 1-8 Attributes of the permanent 1+1 diamond services
Attribute Permanent 1+1 Diamond Service
Requirements for Sufficient non-protection resources are available between the

creation source node and the sink node.
Protection type During creation, diamond services generate the services that have
the traditional WDM 1+1 protection attribute at the same time.
Different ASON trails support different protection schemes.
For WDM ASON ODUk trail: supports ODUk SNCP
Protection and l If the resources are sufficient, two LSPs are always available
restoration for a permanent 1+1 diamond service. One is the active LSP
and the other is the standby LSP.
l If the resources are not sufficient, one valid LSP can still be
reserved for a permanent 1+1 diamond service to ensure the
service survivability. The other LSP is also available but may
be invalid.
Rerouting l Supports rerouting lockout.

l Supports rerouting priority.
l Supports several rerouting policies:
– Use existing trails whenever possible
– Do not use existing trails whenever possible
– Best route
– Simulated span restoration policy
Revertive Supports reverting to the previous route.
Preset restoring trail Supports setting the preset restoring trail.
Service conversion l Supports conversion between diamond services and traditional

1+1 services.
l Supports conversion between diamond WDM ASON trails
and silver WDM ASON trails.
l Supports conversion between diamond WDM ASON trails
and copper WDM ASON trails.
Service switching Supports manual switching.

Service optimization Supports manual service optimization.
Table 1-9 Attributes of the rerouting 1+1 diamond service

Attribute Rerouting 1+1 Diamond Service
Requirements for Sufficient non-protection resources are available between the source node
creation and the sink node.
Protection type During creation, diamond services generate the services that have the
traditional WDM 1+1 protection attribute at the same time. Different
ASON trails support different protection schemes.
Protection and l When the standby LSP fails, services are not switched. Rerouting is
restoration not triggered.
l When the active LSP fails, services are switched to the standby LSP
for transmission. Rerouting is not triggered.
l When both the active and the standby LSPs fail, rerouting is triggered
to create a new LSP to restore services.

– Best route
Revertive Supports reverting to the previous route.
Preset restoring Supports setting the preset restoring trail.

trail
Service l Supports conversion between diamond services and traditional 1+1

conversion services.
l Supports conversion between diamond WDM ASON trails and silver
WDM ASON trails.
l Supports conversion between diamond WDM ASON trails and copper
WDM ASON trails.
Service Supports manual switching.

switching
Service Supports manual service optimization.

optimization

Table 1-10 Attributes of the non-rerouting 1+1 diamond service

Attribute Non-rerouting 1+1 diamond service
Requirements Sufficient non-protection resources are available between the source node
for creation and the sink node.
Protection type During creation, diamond services generate the services that have the
traditional WDM 1+1 protection attribute at the same time. Different
ASON trails support different protection schemes.
Protection and l When the active LSP fails, services are switched to the standby LSP
restoration for transmission. Rerouting is not triggered.
l When the standby LSP fails, services are not switched. Rerouting is
not triggered.
l When both the active and the standby LSPs fail, rerouting is not
triggered.
Preset restoring Supports setting the preset restoring trail.

trail
Service l Supports conversion between diamond services and traditional 1+1

conversion services.
l Supports conversion between diamond WDM ASON trails and silver
WDM ASON trails.
l Supports conversion between diamond WDM ASON trails and copper
WDM ASON trails.

switching

optimization
NOTE
When diamond ODUk ASON WDM trails are created, setting the SNC/N(PM) and SNC/S(TCM) modes
is supported.
When k is 0, only the non-intrusive monitoring (SNC/N(PM)) is supported. When k is 1, 2 or 3, the sub-
layer monitoring (SNC/S(TCM)) and non-intrusive monitoring (SNC/N(PM)) are supported.
When the SNCP type is set as sub-layer monitoring, the U2000 supports setting TCM layers (TCM=1–5).
Traditional services in SNC/I, SNC/N, and SNC/S protection modes can be upgraded into diamond ASON
services with the protection modes unchanged. After rerouting, SNC protection for services in the SNC/I
and SNC/N(TCM) protection modes changes into SNC/N(PM).
1.5.5 Silver WDM ASON Trail

Silver WDM ASON services, including WDM ASON OCh trails, ODUk trails, the revertive
time is several seconds. The silver level service is suitable for those data or internet services that
have low real-time requirement.
Silver services refer to the service connections from the source node to the destination node with
the rerouting protection attribute. They are also called rerouting services. If the LSP of the silver

services fails, rerouting is repeatedly initiated to restore the services until the rerouting is
successful. The silver services compute the restoration tail in real time, and thus no resource
needs to be reserved in advance. Hence, the bandwidth utilization is high. If there are not enough
resources, the services may be interrupted.
As shown in Figure 1-31, A-B-G-H-I is a silver service trail. If the fiber between B and G is
cut, the ASON triggers rerouting from A to create a new LSP that does not pass the cut fiber.
Hence, services are protected.
Figure 1-31 A silver service
R1 R4
E
LSP after rerouting
I
D
F
C
A
B
H
G
R2
Original LSP R3
: ASON NE
: User equipment
Table 1-11 lists the attributes of silver services.
Table 1-11 Attributes of silver services
Attribute Silver Services
Requirements for creation Sufficient non-protection resources are available between the
source node and the sink node.
Service restoration When the original LSP fails, rerouting is triggered to create a
new LSP to restore services.

– Best route

Revertive Services in the WDM ASON ODUk, OCh trail support reverting
to the previous route manually or automatically.
Service migration l Supports migration between silver services and traditional

unprotected services without affecting them.
l Supports migration between silver services and diamond
services.
l Supports migration between silver services and copper
services.
NOTE
In the case of the WDM ASON OCh trails, the conversion between the
silver and diamond or copper is not supported.
Service optimization Supports manual service optimization.
Service association Supports service association.
1.5.6 Copper WDM ASON Trail

The copper services are seldom used. Generally, temporary services, such as the abrupt services
in holidays, are configured as copper services. The copper WDM ASON trails are classified into
OCh trail, ODUk trail.
Copper services are also called non-protection services. If an LSP fails, services do not reroute
and are interrupted. Table 1-12 lists the attributes of copper services.
Table 1-12 Attributes of copper services
Attribute Silver Service
Requirements for Sufficient non-protection resources are available between the source
creation node and the sink node.
Service restoration Does not support rerouting.
Service migration l Supports migration between copper services and traditional

services.
l Supports migration between copper services and diamond services.
l Supports migration between copper services and silver services.
NOTE
In the case of the WDM ASON OCh trails, the conversion between the copper
and diamond or silver levels is not supported.

optimization

1.5.7 OVPN
In the case of an optical virtual private network (OVPN), multiple operators share one ASON.
When multiple operators share one ASON, different TE link resources are allocated to each
operator. In this case, an operator can use and manage its own TE link resources and ASON
services only. The operators are called OVPN customers.
As shown in Figure 1-32, certain resources are separately allocated to OVPN customers 1 and
2. The network management (NM) users of OVPN customers 1 and 2 are separately created on
the U2000. Then, OVPN customers 1 and 2 can log in to the U2000 through their respective
clients and NM users. OVPN customers 1 and 2 can separately manage and maintain their
resources and ASON services.
Multiple NM users can be created for one OVPN customer. One NM user can manage multiple
OVPN customers.
Figure 1-32 Networking diagram of an OVPN
U2000 Server
U2000 Client U2000 Client

U2000 Client
OVPN OVPN
Customer1 NM User Admin
Customer2
: Resource of OVPN customer 1
: Resource of OVPN c ustomer 2
NOTE
The OVPN function is available only to the optical-layer ASON services.

Enabling the OVPN Function

To perform the OVPN function, you must ensure that all the ASON NEs in the ASON domain
enable the OVPN function. In addition, the OVPN License can be started on the NMS side.
Partitioning the TE Link Resources

The TE link resources are divided into three types: shared resources, unshared resources, and
OVPN customer resources, as shown in Figure 1-33.
Figure 1-33 Partitioning the TE link resources
VC-4
timeslot
. Shared
resources
.
.
.
TE links . Unshared
resources
.
.
.
Resources of OVPN
. customers
.
VC-4
timeslot
Table 1-13 shows the principle for the NM user to use the resources. The NM users are classified
into the following three types:
l NM user (admin): By default, admin is the superuser. The NM user uniquely has the right
to manage the OVPN customers, to partition the OVPN resources, and to use all the TE
link resources.
l OVPN NM user: The OVPN NM user can use the OVPN customer resources (colored) and
shared resources that are partitioned by the NM user admin.
l NM user without the authorities of OVPN customers: This NM user can use the shared
resources only.
Table 1-13 Principle for an NM user to use resources

User Level Shared Resource OVPN User Unshared
Resource Resource
admin Available Available Available
OVPN NM user Available Available Unavailable
NM user without the Available Unavailable Unavailable

authorities of OVPN
customers

NOTE
To allocate the TE links on the MSP ring for OVPN customers, ensure that the timeslots are consistent
with each other in each segment.
OVPN Services
Table 1-14 lists the OVPN service attributes.
Table 1-14 OVPN service attributes

Attribute OVPN Service
Creating a service l When creating a service, the NM user admin can use the shared
resources and OVPN customer resources. Each OVPN service can
use only the timeslot resources of the same color.
l An OVPN customer can create a service on the resources only
allocated to the OVPN customer.
Rerouting When the OVPN service is rerouted, it can use the resources allocated to
the OVPN customer first. If the OVPN customer resources are not
available, the OVPN service can use the shared resources.
Presetting the A restoration trail can be preset. An OVPN customer can use the allocated
restoration trail resources only.
Shared Mesh A shared Mesh restoration trail can be preset. An OVPN customer can
restoration trail use the allocated resources only.
Service switching OVPN services and traditional services can be mutually switched from
each other.
l To switch an SDH service to an ASON service, you need to switch
the static SDH resources to the ASON resources.
l After an ASON service is degraded to an SDH service, the original
ASON service switch to the static SDH resources.
Service An ASON service of an OVPN customer can be optimized on the

optimization resources only allocated to the OVPN customer.
1.5.8 Crankback Mechanism

The Crankback mechanism during rerouting, optimization, and creation of the wavelength/sub-
wavelength LSP is supported.
It takes a certain time to spread network routing information. When rerouting is performed, the
source node may use the outdated network status information to calculate the trail. Therefore,
the selected route may be unavailable, resulting in a rerouting failure.
The ASON software supports the Crankback rerouting mechanism. When setting up connections
according to the calculated trail, the ASON software informs the source node of the information
related to the faulty network nodes or links if the connection setup process is baffled due to
insufficient network resources or network faults. In this case, the source node recalculates a trail
that meets the constraint conditions but does not traverse the obstacle node and then establishes
the connections for the calculated trail. This effectively restores a service by means of rerouting.

1.5.9 Network Traffic Engineering

An ASON network has one network traffic engineering policies, that is, network traffic
equilibrium, so as to make network resources distributed in the best state. In addition, various
restraint conditions for route selection are developed. In this manner, network resources are
properly used.
Network Traffic Equilibrium

Due to manual planning of services on a traditional network, it is difficult for the traditional
network to achieve traffic equilibrium on the entire network. The introduction of ASON features
makes the network resources automatically adjusted. With the traffic engineering algorithm, the
resources of the entire network can be automatically and evenly allocated, which avoids
congestion and improves network security and operability.
On an ASON network, the traffic of each trail is equalized, and thus the situation where the
traffic of certain trails is large but certain trails are idle can be avoided.
The ASON computes a best route according to the CSPF algorithm. If there are many services
between two nodes, there may be several services sharing a same route. The traffic equilibrium
function is used to avoid this situation. As shown in Figure 1-34, there are many silver services
between R2 and R4. To make the network more safe and reliable, the ASON allocates them to
different routes such as A-D-E-I, A-B-C-F-I and A-B-G-H-I as evenly as possible. In this
manner, network security and stability are enhanced.
Figure 1-34 Traffic equilibrium
R1 R4
E
I
D
F
C
A
B
H
G
R2
R3
: ASON NE
: User equipment
Route Selection Policy

With traffic engineering, Huawei ASON equipment develops various constraint conditions on
the control plane for route selection based on the WDM/OTN ASON network. The constraint
conditions for route selection are as follows:

l Constraint conditions for network resources (explicit node, explicit link, explicit
wavelength, and explicit channel)
l Constraint conditions for exclusion of network resources (excluded node and excluded link)
l Strict route and number of nodes (hops) that a service traverses
l Fiber length of a service, load balancing, SRLG, and associated services
l Combination of the preceding constraint conditions
The constraint conditions for the ASON wavelength or sub-wavelength services are mainly
reflected in the trail cost. The trail cost includes the following factors:
l Link bandwidth occupancy
l Link length
l Number of nodes (hops) that a service traverses
During service route computation, you should consider the preceding factors of the trail cost
(the function of setting the weight of each factor is provided), and thus you can select the route
with the minimum trail cost. In this manner, the traffic is equalized and the network resources
are properly used.
Customized Link Cost

The ASON software supports the customized link cost. Hence, users can adjust the link cost and
select the expected link according to actual situations. After the customized link cost is
introduced, the trail with the lowest cost is selected according to the integrated cost of a link
during service creation or rerouting.
The customized link cost is used to describe the customized link attributes. By using the
customized link cost, users can assign different meanings to a link. The examples are as follows:
l Link age
The cost of a link ascends with the age of the link. When computing a trail, the ASON
software is more likely to select a new trail.
l Link price
The cost of a link ascends with the price of the link. When computing a trail, the ASON
software is more likely to select a cheap trail.
l Link interruption rate
The cost of a link ascends with the link interruption rate. When computing a trail, the ASON
software is more likely to select a trail with a low link interruption rate.
The customized link cost can be queried, and a change of the customized link cost on a node
can be flooded to all nodes on the entire network. In this manner, all nodes on the network
acknowledge the customized link cost information, which can be used as a basis of computing.
Shared Risk Link Group

On an ASON network, a shared risk link group (SRLG) needs to be set when a group of optical
fibers are in one cable.
SRLG represents the shared risk link group. Fibers in the same optical cable have the same risk.
That is, when the cable is cut, all fibers are cut. Hence, an ASON service should not be rerouted
to another link that has the same risk.
Hence, an SRLG needs to be correctly set for the links sharing the same risk on a network so as
to avoid the situation where an LSP after rerouting of ASON services traverses a link that has

the same risk as that of the faulty link. In this manner, the service restoration time during ASON
service rerouting is shortened. You can change the SRLG attribute.
When an electrical-layer service selects its trail, the electrical-layer link inherits the SRLG
information of the links involved in its electrical server layer and the SRLG information of the
links involved in its optical server layer. As a result, during rerouting, the electrical-layer service
follows the principle of separating SRLGs as possible.
1.5.10 Service Association

Service association can be used to associate the same services accessed from different points
into an ASON network.
Service association involves associating two ASON services that have different routes. During
rerouting or optimization of either service, the rerouting service avoids the route of its associated
service. Service association is mainly used for services (dual-source) accessed from two points.
As shown in Figure 1-35, D-E-I and A-B-G-H are two associated LSPs. When the fiber between
B and G is cut, rerouting of A-B-G-H LSP avoids D-E-I LSP.
Figure 1-35 Service association
R1 R4
E
1+1protection
I 1+1protection
D
F
C
A
B
H
G
R2
R3
: ASON NE
: User equipment
Table 1-15 lists the attributes of service association.
Table 1-15 Attributes of service association

Attribute Service Association
Service creation The ASON software supports the following operations:

l Creating two associated WDM ASON trails at one time.
l Associating two created WDM ASON trails.
Service Supports optimization of associated services.

optimization
Rerouting When a service is rerouted, it avoids the route of its associated service.

Service type l Supports association of two silver services.

l Supports association of two copper services.
l Supports association of a silver service and a copper service.
NOTE
In the case of the associated optical-layer or electrical-layer services that have the same source, you can
set a rerouting condition on the U2000. The rerouting condition can be either of the following:
l Rerouting is triggered when one service is interrupted (default condition).
l Rerouting is triggered only when both services are interrupted.
NOTE
The product supports the pre-computation function of optical-layer or electrical-layer associated services
with different source nodes. On the NMS, after a user selects two pairs of service source and sink nodes
and route constraint, the system can precalculate or directly create associated services.
It is recommended that you configure two services that originate from the same node as associated services.
The following problems may occur if two associated services originate from different nodes.
l If two associated services originate from different nodes and travel along the same LSP, they will be
also switched to the same LSP after rerouting.
l If two associated services (for example, services A and B) originate from different nodes and travel
along different LSPs, the current LSP of service A may overlap with the original LSP of service B after
rerouting. If service B is switched back to the original LSP subsequently, it will travel along the current
LSP of service A.
1.5.11 Service Optimization

After the topology changes several times, the ASON may have less satisfactory routes and thus
requires service optimization. Service optimization involves creating a new LSP, switching the
optimized service to the new LSP, and deleting the original LSP to change and optimize the
service. Of course, the service route can be restricted during the service optimization.
CAUTION
The LSP must be changed in wavelength trail optimization, which will cause switching between
WSS components. As a result, services may be interrupted during service optimization.
Especially, optical-layer services will be interrupted for seconds. Be cautious to use the function.
LSP optimization has the following features.
l Only manual optimization is supported.

l The optimization does not change the protection level of the optimized service.
l During optimization, rerouting, degrade/upgrade, or deleting operations are not allowed.
l During creation, rerouting, degrading/upgrading, starting or deleting operations,
optimization is not allowed.
l The following service types support optimization: diamond, silver, copper, iron and
tunnel services.

NOTE
When the OptiX OSN 8800 V100R005 is used as a WDM or an OTN device, resources on the original
trail will be reserved during revertive service optimization. When a fault occurs on the optimized trail, the
service can be rerouted back to the original trail if the original trail has no fault.
l During maintenance, lock the revertive function of an optimized revertive service. After performing
the maintenance, unlock the revertive function to manually reroute the service back to the original trail.
l In typical scenarios, it is recommended to set the new trail for an optimized revertive service as the
service's original trail.
1.5.12 Service Migration

The ASON software supports the migration between ASON services and traditional services.
The ASON software also supports migration of the ASON services with different SLAs. The
service migration is hitless and does not interrupt the existing services.
Service Migration between ASON Trails and Permanent Connections

Currently, Huawei ASON software supports the following migration between the traditional
WDM services and ASON services:
l Migration between static 1+1 services and diamond services
NOTE
For ODUk trail, the 1+1 service denotes the ODUk SNCP.
l Migration between static unprotected services and silver services
l Migration between static unprotected services and copper services
Service Migration between ASON Trails

The ASON software supports the following migration between the traditional WDM services
and ASON services:
l Migration between diamond WDM ASON trails and silver WDM ASON trails.
l Migration between diamond WDM ASON trails and copper WDM ASON trails.
l Migration between silver WDM ASON trails and copper WDM ASON trails.
1.5.13 Preset Restoration Trail

Customers may require that the services route to a specified trail in the case of trail failure. To
this end, the ASON software provides the function of presetting the trail for restoration. This
function helps increase the controllability of service routing. The preset restoration trail
information is stored only on the control plane and requires no physical resource.
For SDH ASON service, in the case of a service configured with a preset restoration trail, when
this preset restoration trail fails, the system recalculates a new preset restoration trail during
regular detection (at default intervals of 60 minutes). After recalculating a preset restoration trail,
the system reports a preset restoration trail update event to the NMS.
NOTE
If the resources are sufficient, the system currently supports two preset restoration trails for one ASON
service.
In the case of an optical-layer silver trail, if a wavelength the same as the original wavelength
is not available, the ASON software presets a restoration trail to set up a wavelength-tunable
trail.

ASON software supports pre-set restoration trail in the case of multiple fiber cuts:
l Pre-set restoration trail in the case of multiple fiber cuts
To ensure the route after rerouting in the case of multiple fiber cuts, the ASON software
configures multiple pre-set restoration trails for an end-to-end reroutable service (optical-
layer or electrical-layer service). Users can configure a maximum of two pre-set restoration
trails for a service or an LSP, and specify the priorities of the two trails.
NOTE
Users can configure two pre-set restoration trails for the working and protection LSPs of a diamond
service.
To ensure that services can be restored after multiple fiber cuts, when planning pre-set
trails, users need to separate the routes between multiple pre-set restoration trails as
possible.
l Change of the priority of a pre-set restoration trail in the case of multiple fiber cuts
The ASON software can configure, delete, or query multiple pre-set restoration trails. In
addition, the ASON software can change the priority of a pre-set restoration trail in the case
of multiple fiber cuts. After the pre-set restoration trail in the case of multiple fiber cuts is
configured, if the network condition changes, users can change the priority of the configured
pre-set restoration trail. The change does not immediately trigger rerouting, because the
change is valid only in the next rerouting.
l Route selection policy of the pre-set restoration trail during rerouting in the case of multiple
fiber cuts
The route selection policies of the pre-set restoration trail during rerouting in the case of
multiple fiber cuts are as follows:
– Select the pre-set restoration trail with the highest priority.
– When multiple pre-set restoration trails with the same priority are available, take priority
to select the trail with a small number.
– If services are rerouted to a pre-set restoration trail with a low priority, rerouting is not
triggered after the fault on the pre-set restoration trail with a high priority is rectified.
l Principle of service protection level conversion in the case of multiple pre-set restoration
trails
The protection level conversion principle in the case of multiple pre-set restoration trails
is as follows:
– If a service that has the rerouting capability is converted to a service of another type
that also has the rerouting capability, the pre-set restoration trail in the case of multiple
fiber cuts is retained.
– If a service that has the rerouting capability is converted to a service of another type
that does not have the rerouting capability, the pre-set restoration trail in the case of
multiple fiber cuts is cleared.
– When a diamond service is converted to a silver service, the ASON software determines
whether to retain the pre-set restoration trail of the working LSP or protection LSP
according to the parameters of the working and protection trails set by users.
– When a silver service is converted to a diamond service, the ASON software determines
whether the pre-set restoration trail is used as the pre-set restoration trail of the working
LSP or protection LSP according to the parameters of the working and protection trails
set by users.

1.5.14 Trail Pre-Computation and Adjustment

When optimizing the routes of new ASON wavelength/sub-wavelength services or original
wavelength/sub-wavelength services, users can issue the route pre-computation command
through the U2000. In this manner, users can acknowledge the service routes to be created, routes
after optimization, specific routes involving service restoration trails in advance. In addition,
users can properly adjust the pre-computed trail according to service trail requirements.
1.5.15 Service Reversion Mechanism

The ASON software supports service reversion. After a fault is rectified, services are reverted
to the previous trail.
ASON services can be classified into revertive services and non-revertive services.
l For revertive services, the previous trail is retained after rerouting. After the fault is
rectified, the services are reverted to the previous trail.
l For non-revertive services, the previous trail is not retained after rerouting. After the fault
is rectified, the services are not reverted to the previous trail.
The reversion mechanisms of revertive services include manual reversion, scheduled reversion,
and automatic reversion.
l Scheduled reversion
Services are rerouted because of a fault on the previous trail. After the fault is rectified and
the manually set reversion time elapses, the services are reverted to the previous trail.
l Automatic reversion
Services are rerouted because of a fault on the previous trail. The system periodically checks
the link status. After the fault on the previous trail is rectified and the service alarm ends,
the services are automatically reverted to the previous trail when the wait to revert time is
due.
l Manual reversion
After services are rerouted or optimized to another trail, the information about the previous
trail is retained. When the press-to-revert command is issued, the services are reverted to
the previous trail. If the previous trail is normal and no resource is occupied, the services
are successfully reverted to the previous trail. Otherwise, the reversion fails.
Users can set whether services can be reverted during service creation or change the revertive
attribute of the services without service interruption.
NOTE
The previous trail refers to the trail before rerouting, and the previous route may not be the route initially
set up for ASON services.
NOTE
After several topology changes on an ASON network, the actual service routes may be different from the
original routes. The ASON software provides the function of reverting the services on the entire network
to the original trails. Generally, the route during ASON service creation is the original route of the ASON
service. After services are rerouted or optimized to another trail, the information about the original trail is
retained. If the original route recovers, the services can be adjusted to the original route manually.
NOTE
The OptiX OSN 8800 V100R002 and later supports the automatic reversion function of optical-layer ASON
services.

Adhere to the following principles for changing the service reversion mode:
l For a non-revertive service,

– It can be modified as revertive when the current trail is consistent with the original trail.
– It cannot be modified as revertive when the current trail is inconsistent with the original
trail.
l For a revertive service,
– It can be modified as non-revertive when the current trail is consistent with the original
trail.
– It cannot be modified as non-revertive when the current trail is inconsistent with the
original trail.
Adhere to the following principles for changing the original trail:
l For a non-revertive service,

– The current trail can be set as the original trail regardless whether the current trail is
consistent with the oringinal trail or not.
l For a revertive service,
– The current trail can be set as the original trail if the current trail is consistent with the
original trail.
– The current trail can be set as the original trail if the current trail is inconsistent with
the original trail, but the previous original trail needs to be deleted and the revertive
mode of the current service needs to be set as revertive.
TIP
The features of automatic reversion of optical-layer ASON services are as follows:

l If no port alarm is detected on the link between the FIU boards at two stations, optical-layer services
are automatically reverted to the trail before rerouting. If a wavelength channel alarm is detected, the
services are reverted to the trail before reversion in the case that the trail before reversion has no alarm.
That is, when the optical-layer services are reverted, system does not delete the rerouted trail. If no
service alarm is detected two minutes after the services are reverted to the trail before rerouting, the
system deletes the rerouted trail. Two minutes later, if a service alarm persists, the services are reverted
to the rerouted trail and a reversion failure event is reported. No automatic reversion operation is
performed later, and the service enters the "stopping automatic reversion" state until users manually
revert the services (or in timed manner). In this case, the "stopping automatic reversion" state changes.
l Within the two minutes when the services are automatically reverted but the rerouted trail is not deleted,
if a port on the FIU of the rerouted trail reports an alarm, the two-minute wait is stopped. In this case,
the rerouted trail is directly deleted and the reversion operation is complete.
l If a port on the FIU of the trail before rerouting reports an alarm, the two-minute wait is stopped and
the services are directly reverted to the rerouted trail.
NOTE
When the OptiX OSN 8800 V100R005 is used as a WDM or an OTN device, resources on the original
trail will be reserved during revertive service optimization. When a fault occurs on the optimized trail, the
service can be rerouted back to the original trail if the original trail has no fault.
l During maintenance, lock the revertive function of an optimized revertive service. After performing
the maintenance, unlock the revertive function to manually reroute the service back to the original trail.
l In typical scenarios, it is recommended to set the new trail for an optimized revertive service as the
service's original trail.
NOTE
For the ODU1 ASON service, revertive mode is recommended.

1.5.16 Resource Sharing of Trails

In the case of optical-layer or electrical-layer permanent 1+1 diamond services, rerouting 1+1
diamond services, and associated services with the same source (wavelengths of the associated
silver services are the same), the ASON software supports the function of resource sharing of
the working and protection trails or resource sharing of the associated service trails.
l Resource sharing of the working and protection trails
Resource sharing of the working and protection trails can provide restoration resources as
many as possible. Figure 1-36 shows the main application scenario of tangent rings. The
blue and red continuous lines indicate the working and protection trails. The working and
protection trails are invalid when fibers at points 1 and 2 are cut. In this case, if resources
of the working and protection trails cannot be shared, services cannot get resources for
restoration. If resources can be shared, you can combine part of the working trail and part
of the protection trail together to form a restoration trail, which is the green dashed line in
the figure. Similarly, if the fiber at point 3 is cut, the trail (purple dashed line) can be used
for service restoration.
Figure 1-36 Application of resource sharing of the working and protection trails
NOTE
When both trails for 1+1 diamond ASON services are interrupted, the system by default allows
resources sharing on the working and protection trails during service rerouting. Resource sharing of
the working and protection trails provides a possible solution to protect services in the case of multiple
fiber cuts on a network other than a mesh network.

NOTE
l When both the working and protection trails for a permanent 1+1 diamond ASON service are
interrupted, the system allows resources sharing on the working and protection resources only
when no diverse route is available for service restoration.
l When the "using original trail resources as possible" rerouting policy is used for a rerouting 1+1
diamond service, the system shares the resources on the working and protection trails with
precedence to restore the service.
l In the case of creating a new ASON service or optimizing an ASON service, resource sharing of
the working and protection trails is not allowed. Optimization, pre-computation, and
configuration of a preset restoration trail can still be performed on a service with resource sharing
of the working and protection trails enabled.
l A static service with resource sharing of the working and protection trails enabled cannot be
upgraded to a 1+1 diamond service, and an ASON service where resource sharing of the working
and protection trails is performed cannot be downgraded but can be deleted.
l If resource sharing of the working and protection trails is performed on the original trail of a
revertive service, automatic reversion is not initiated, but the service can be reverted in a manual
or timed manner.
l During rerouting of a diamond service, if the routing policy of the service is section restoration,
you need to take priority to follow this policy.
l The trail of a service where resource sharing of the working and protection trails is performed
cannot be set as the original trail.
l During sharing, directions of services must be the same. A forward trail and a reverse trail cannot
share resources of each other. Figure 1-37 shows application of resource sharing of a forward
and reverse tail.
l An ASON service with the same working and protection trail cannot be enabled with resource
sharing of the working and protection trails.
l If the working and protection trails already share resources, the working and protection trails are
separated to the most when one or all trails are optimized. If resources are insufficient, the
optimized trails can still share resources. (Only the currently shared resources can be shared.)
l When the system choose to share the resources on the working and protection trails for an optical-
layer ASON service, the service will be transmitted over the original wavelength. Resource
sharing and wavelength adjustment are not allowed at the same time.
Figure 1-37 Resource sharing of a forward and reverse tail
A service is added at point A and dropped at point D. The original trail is A->B->C->D
(blue lines). When the fibers between A and B and between C and D are cut, the service

can be rerouted to trail A->C->B->D (red lines). Hence, between B and C, the forward trail
and reverse trail share resources.
l Resource sharing of associated trails
The ASON software provides the trail sharing function to associated ASON services with
the same source. Figure 1-36 shows the main application scenarios of a tangent ring
network. The blue lines and red lines indicate two associated trails with the same source.
When fibers at 1 and 2 are cut, the two trails fail. If resources of the associated trails cannot
be shared, the services cannot be restored. If the resources can be shared, you can combine
the associated trails to make a restoration trail, which is the trail in green as shown in the
figure. Similarly, if the fiber at 3 is cut, you can still use the trail in purple to restore the
services.
NOTE
When both trails that have the same source for two associated optical-layer wavelength services are
interrupted, the system by default allows resources sharing on the associated trails for the associated
services to reroute if there are no other resources available. On the U2000, users can specify whether
to share resources on the associated trails as required.
NOTE
l During rerouting of associated services that come from the same source, the system will take
precedence to share the resources on the two trails for the services if the two trails are configured
with a policy to use resources on the original trail.
l In the case of creating a new service or optimizing a service, resource sharing of associated trails
is not allowed.
l After associated trails share resources, do not cancel the association.
l If associated services are of different types, resource sharing of associated trails is not supported.
For example, the associated OTN services must have the same granularity and rate. The protection
level, however, is not restricted. For example, sharing is allowed when a silver service and a
copper service are associated.
l If resource sharing of associated trails is performed on the original trail of a revertive service,
automatic reversion is not initiated, but the service can be reverted in a manual or timed manner.
l During rerouting of associated services with the same source, if the routing policy of the services
is restoration by section, you need to take priority to follow this policy.
l The trail of a service where resource sharing of associated trails is performed cannot be set as
the original trail. Before canceling association of associated services, you can delete the services
and clear the association information.
l If the trails of associated services already share resources, the trails of the associated services are
separated to the most when one or all trails are optimized. If resources are insufficient, the
optimized trails can still share resources. (Only the currently shared resources can be shared.)
l During sharing, directions of services must be the same. A forward trail and a reverse trail cannot
share resources of each other. Figure 1-37 shows application of resource sharing of a forward
and reverse tail.
l An ASON service with the same associated trail cannot be enabled with resource sharing of
associated trails.
1.5.17 ASON Features Based on the Split of Optical and Electrical

NEs
For ASON network, users need to split the NE into different NEs. The splitting rule is that all
optical boards and regeneration boards are allocated to one or more optical NEs and all electrical
boards are allocated to one or more electrical NEs. Based on the split of optical and electrical
NEs, the ASON software supports resource locating and creation of ASON services.

Figure 1-38 shows the schematic diagram of separate optical and electrical NEs (Colored). In
the figure, NE1 is an optical NE taking the M40 and D40 boards as the edge points. NE2 is the
electrical NE taking the OTU board as the edge points.
Figure 1-39 shows the schematic diagram of separate optical and electrical NEs (Colorless). In
the figure, NE1 is an optical NE taking the WSM9 and WSD9 boards as the edge points. NE2
is the electrical NE taking the OTU board as the edge points.
Figure 1-38 Schematic diagram of the split of optical and electrical NEs (Colored)
W R NE1
S D
M U
F 9 9 F
I I
U R W U
D S
U M
9 9
RDU9 WSM9
OCh
D40 M40 OCh
NE2
OCh OTU OTU OCh

Figure 1-39 Schematic diagram of the split of optical and electrical NEs (Colorless)
W R NE1
S D
M U
F 9 9 F
I I
U R W U
D S
U M
9 9
RDU9 WSM9
OA
OA
DM1~DM 9 AM1~AM 9
WSD 9 WSM9
Drop 73~80 Drop 1~9 Add 1~9 Add 73~80
WSD9 WSD9 WSM9 WSM9
OCh OCh
NE2
OCh OTU OTU OCh
NOTE
When there is no optical path between two or more NEs, the Ethernet ports of the NEs can be used to
achieve the extended ECC communication. By default, the NE takes the auto-extended ECC
communication. When more than eight Huawei devices need to use the extended ECC communication, the
manually extended ECC communication must be used instead. See the "Setting Manually Extended ECC
Communication" of the Commissioning Guide of the OptiX OSN 8800 for details.
In the case that optical and electrical NEs are not split, ASON NEs can only take the OTU or
FIU board as the edge points and the matching TE link is generated when a board is added. In
the case that optical and electrical NEs are split, the multiplexer and demultiplexer boards or
another optical-layer board can be considered as the edge points of the optical NE. In this case,
when an intra-NE fiber connection is created between the optical port on the multiplexer and
demultiplexer boards and the optical port on the OTU board of the electrical NE, an intra-NE
link that carries OCh signals can be generated.

The ASON software processes stations where optical and electrical NEs are split and not split
in different modes. In the case of a station where optical and electrical NEs are split, the
connections between the optical NE and the electrical NE are described as intra-NE links. In
this case, a complete TE link is formed by the OMS TE links between upstream and downstream
stations and the intra-NE links at one station.
NOTE
The multiplexer and demultiplexer board and OTU board at the NE edges configure each other as the link
far end to form an abstract OMS TE link. The link is then used for creating optical-layer services.
After optical and electrical NEs are split at a station, bidirectional fiber connections and link far ends of
the optical and electrical NEs must be configured correctly according to the planning.
After optical and electrical NEs are split at a station, perform configurations on the U2000 to ensure proper
communication between optical NEs and electrical NEs and successful creation of TE links. For details on
how to perform the configurations, see Configuring a Station with Separate Optical and Electrical
NEs.
The U2000 can create and manage optical-layer ASON services based on the split of optical and
electrical NEs, including creation, reroute, optimization, deletion, and pre-calculation of various
SLA services, and the conversion between static ASON and dynamic services. The operation
methods are the same as those of the services not based on the split of optical and electrical NEs.
NOTE
The electrical regeneration boards and the optical-layer boards must be installed on the same optical NE.
The total number of subracks of an optical NE cannot exceed 24 and the total number of wavelengths that
traverse electrical regeneration boards cannot exceed 32.
For separate optical and electrical NEs, active and standby system control boards must be used in the master
subracks of the optical and electrical NEs.
NOTE
Two regeneration boards need to be used to bidirectionally regenerate services if each of them can
regenerate services unidirectionally. The two regeneration boards must be installed in paired slots.
The LSXR and TN54NS3 board require one slot. The principles for configuring the LSXR and TN54NS3
boards are as follows:
l OptiX OSN 8800 T32: The LSXR and TN54NS3 boards for transmitting and receiving the same
wavelength must be installed in IU1 and IU2, IU3 and IU4, IU5 and IU6, IU7 and IU8, IU12 and IU13,
IU14 and IU15, IU16 and IU17, IU18 and IU19, IU20 and IU21, IU22 and IU23, IU24 and IU25, IU26
and IU27, IU29 and IU30, IU31 and IU32, IU33 and IU34, or IU35 and IU36.
l OptiX OSN 8800 T64: The LSXR and TN54NS3 boards for transmitting and receiving the same
wavelength must be installed in IU1 and IU2, IU3 and IU4, IU5 and IU6, IU7 and IU8, IU11 and IU12,
and IU26, IU27 and IU28, IU29 and IU30, IU31 and IU32, IU33 and IU34, IU35 and IU36, IU37 and
IU38, IU39 and IU40, IU41 and IU42, IU45 and IU46, IU47 and IU48, IU49 and IU50, IU51 and IU52,
and IU66, IU67 and IU68.
The TN12LSXLR board requires two slots. The principles for configuring the TN12LSXLR board are as
follows:
l OptiX OSN 8800 T32: The TN12LSXLR boards for transmitting and receiving the same wavelength
must be installed in IU2 and IU4, IU6 and IU8, IU13 and IU15, IU17 and IU19, IU21 and IU23, IU25
and IU27, IU30 and IU32, or IU34 and IU36.
l OptiX OSN 8800 T64: The TN12LSXLR boards for transmitting and receiving the same wavelength
must be installed in IU2 and IU4, IU6 and IU8, IU12 and IU14, IU16 and IU18, IU20 and IU22, IU24
and IU26, IU28 and IU30, IU32 and IU34, IU36 and IU38, IU40 and IU42, IU46 and IU48, IU50 and
IU52, IU54 and IU56, IU58 and IU60, IU62 and IU64, IU66 and IU68.

1.6 OCS ASON Feature

The OptiX OSN series products of Huawei can provide the OCS ASON function after the ASON
software is loaded.
1.6.1 End-to-End Service Configuration

The ASON network supports end-to-end service configuration, which is very convenient.
The ASON supports both SDH permanent connections and end-to-end ASON services. To
configure an ASON service, you only need to specify its source node, sink node, bandwidth
requirement, and protection level. Service routing and cross-connection at intermediate nodes
are all automatically completed by the network. You can also set explicit node, excluded node,
explicit link and excluded link to constrain the service routing.
Compared with the service configuration of SDH networks, it fully utilizes the routing and
signaling functions of the ASON NEs and thus it is convenient to configure services. For
example, consider the configuration of a 155 Mbit/s ASON service between A and I in Figure
1. The network automatically finds the A-D-E-I route and configures cross-connection at nodes
A, D, E and I. Although there is more than one route from A to I, the network calculates the best
route according to the configured algorithm. It is assumed that A-D-E-I is the best route.
The service is created as follows:
l Choose the bandwidth granularity.

l Choose the server level.
l Choose the source node.
l Choose the sink node.
l Create the service.
Figure 1-40 End-to-end service configuration
R1 R4
E
I
D
F
C
A
B
H
G
R2
R3
:ASON NE
:User Equipment

1.6.2 Mesh Networking Protection and Restoration

security.
security.
As a main networking mode of ASON, mesh features high flexibility and scalability. Compared
with the traditional SDH networking mode, the mesh networking does not need to reserve 50%
bandwidth. Thus, it can save bandwidth resources to satisfy increasingly large bandwidth
demand. In addition, this networking mode also provides more than one recovery route for each
services so it can best utilize the network resources and enhance the network security.
As shown in Figure 1-41, when the C-G link fails, to restore the service, the network calculates
another route from D to H and creates a new LSP to transmit the service.
Figure 1-41 Trail restoration
Recovery route
R1 R4
E
I
D
F
C
A
B
H
G
R2
R3
:ASON NE
:User Equipment
1.6.3 SLA Classification of Services

The ASON network can provide services of different QoS to different clients.
The service level agreement (SLA) is used to classify services according to the service protection,
as listed in Table 1-16.

Table 1-16 Service level (SDH Service)

Service Protection and Implementation Switching and
Restoration Scheme Means Rerouting Time
Diamond Protection and restoration SNCP and rerouting Switching time < 50 ms
service Rerouting time < 2s
Gold Protection and restoration MSP and rerouting Switching time < 50 ms
service Rerouting time < 2s
Silver Restoration Rerouting Rerouting time < 2s

service
Copper No protection - -
service No restoration
Iron Preemptable MSP -

service
Table 1-17 lists details of the TE links used by ASON services.
Table 1-17 TE links used by ASON services

Service Level Working Protection Non-Protection
Resource Resource of TE Resource of TE
of TE Link Link Link
Diamond Service creation Not used Not used Used

service
Service rerouting Not used Used when the Used with the
resource is not priority
enough
Service optimization Not used Not used Used
Gold Service creation Used with Not used Used when the
service the priority resource is not
enough
Service rerouting Used with Used when the Used when the
the priority resource is not resource is not
enough enough
Service optimization Used with Not used Used when the

the priority resource is not
enough
Silver Service creation Not used Not used Used

service
Service rerouting Not used Used when the Used with the
resource is not priority
enough

Service Level Working Protection Non-Protection

Resource Resource of TE Resource of TE
of TE Link Link Link
Copper Service creation Not used Not used Used

service
Iron Service creation Not used Used with the Used when the
service priority resource is not
enough
Service optimization Not used Used with the Used when the
priority resource is not
enough
1.6.4 Diamond Services

Diamond services have the best protection ability. When there are enough resources in the
network, diamond services provide a permanent 1+1 protection. Diamond services are applicable
to voice and data services, VIP private line, such as banking, security and aviation.
A diamond service is a service with 1+1 protection from the source node to the sink node. It is
also called a 1+1 service. For a diamond service, there are two different LSPs available between
the source node and the sink node. The two LSPs should be as separate as possible. One is the
working LSP and the other is the protection LSP. The same service is transmitted to the working
LSP and the protection LSP at the same time. If the working LSP is normal, the sink node receives
the service from the working LSP; otherwise, from the protection LSP.
Figure 1-42 shows a diamond service.
Figure 1-42 Diamond Services

Working LSP
R1 R4
E
I
D
F
A C
B
H
G
R2
R3
Protection LSP
:ASON NE
:User equipment

There are three types of diamond services.

l Permanent 1+1 diamond service: rerouting is triggered once an LSP fails.
l Rerouting 1+1 diamond service: rerouting is triggered only when both LSPs fail.
l Non-rerouting diamond service: rerouting is never triggered.
Table 1-18 lists the attributes of the permanent 1+1 diamond service.
Table 1-19 lists the attributes of the rerouting 1+1 diamond service.
Table 1-20 lists the attributes of the non-rerouting 1+1 diamond service.
Table 1-18 Attributes of the permanent 1+1 diamond services

Requirements for Sufficient non-protection resources are available between the

creation source node and the sink node.
Protection and If the resources are sufficient, two LSPs are always available for a
restoration permanent 1+1 diamond service. One is the active LSP and the
other is the standby LSP.

l Supports three rerouting policies:
– Best route
Revertive Supports Automatically Revertive, Non-Revertive, and

Scheduled revertive.
l After the automatically revertive diamond service is rerouted,
the service is automatically reverted to the original path if the
fault in the original path is rectified.
l After the scheduled revertive diamond service is rerouted, the
user can set the service to be reverted to the original path at a
specific future time (ranging from 10 minutes to 30 days) on the
NMS if the fault in the original path is rectified.
l After the non-revertive diamond service is rerouted, the service
is not reverted to the original route after the fault is rectified.
NOTE
The original route is the route before rerouting but may not be the original
route set up when the ASON trail is created.

Service migration l Supports migration between diamond services and permanent

SNCP connections.
l Supports migration between diamond services and gold
services.
l Supports migration between diamond services and silver
services.
l Supports migration between diamond services and copper
services.
Service optimization Supports service optimization.
Service association Does not support service association.
ASON server trail Support diamond ASON server trails.
Alarms to trigger R_LOS, R_LOF, B2_EXC, B2_SD, MS_AIS, MS_RDI, AU_AIS,

rerouting B3_EXC (can be set), B3_SD (can be set)
Table 1-19 Attributes of the rerouting 1+1 diamond service

creation and the sink node
Protection and l When the standby LSP fails, services are not switched. Rerouting is
restoration not triggered.
l When the active LSP fails, services are switched to the standby LSP
for transmission. Rerouting is not triggered.
l When both the active and the standby LSPs fail, rerouting is triggered
to create a new LSP to restore services.

– Best route

Revertive Supports Automatically Revertive, Non-Revertive, and Scheduled

revertive.
l After the automatically revertive diamond service is rerouted, the
service is automatically reverted to the original path if the fault in the
original path is rectified.
l After the scheduled revertive diamond service is rerouted, the user can
set the service to be reverted to the original path at a specific future
time (ranging from 10 minutes to 30 days) on the NMS if the fault in
the original path is rectified.
l After the non-revertive diamond service is rerouted, the service is not
reverted to the original route after the fault is rectified.
NOTE
The original route is the route before rerouting but may not be the original route
set up when the ASON trail is created.
Service l Supports migration between diamond services and permanent SNCP

migration connections.
l Supports migration between diamond services and gold services.
l Supports migration between diamond services and silver services.
l Supports migration between diamond services and copper services.

switching
Service Supports service optimization.

optimization
Service Does not support service association.

association
ASON server Support diamond ASON server trails.

trail
Alarms to trigger R_LOS, R_LOF, B2_EXC, B2_SD, MS_AIS, MS_RDI, AU_AIS,

rerouting B3_EXC (can be set), B3_SD (can be set)
Table 1-20 Attributes of the non-rerouting 1+1 diamond service

creation and the sink node

Protection and l When the active LSP fails, services are switched to the standby LSP
restoration for transmission. Rerouting is not triggered.
l When the standby LSP fails, services are not switched. Rerouting is
not triggered.
l When both the active and the standby LSPs fail, rerouting is not
triggered.
Service l Supports migration between diamond services and permanent SNCP

l Supports migration between diamond services and gold services.
l Supports migration between diamond services and silver services.
l Supports migration between diamond services and copper services.

switching

optimization
Service Does not support service association.

association
ASON server Support diamond ASON server trails.

trail
1.6.5 Gold Services

Gold services are applicable to voice and significant data services. Compared with diamond
services, gold services have greater bandwidth utilization.
A gold service needs only one LSP. This LSP must use working resource of TE links or non-
protection resource of TE links. When a fiber on the path of a gold service is cut, the ASON
triggers MSP switching to protect the service at first. If the multiplex section protection fails,
the ASON triggers rerouting to restore the service.
As shown in Figure 1-43, a gold service can be configured from A to I.

Figure 1-43 Gold services
R4
R1 E MSP
I
D
F
MSP C
A
B MSP
H
G
R2
R3
:ASON NE
:User equipment
Table 1-21 lists the attributes of gold services.
Table 1-21 Attributes of gold services

Attribute Gold Service
Requirements for creation Sufficient working resources or non-protection resources are

available between the source node and the sink node.
Multiplex section l Supports using the working resources of a 1:1 linear multiplex
protection section protection chain to create gold services.
l Supports using the working resources of a 1+1 linear
multiplex section protection chain to create gold services.
l Supports using the working resources of a 1:N linear
multiplex section protection chain to create gold services.
l Supports using the working resources of a two-fiber
bidirectional multiplex section protection ring to create gold
services.
l Supports using the working resources of a four-fiber
bidirectional multiplex section protection ring to create gold
services.
Protection and restoration When a fiber is cut for the first time, MS switching is performed
to protect services. When MS switching fails, rerouting is then
triggered to restore services.

Attribute Gold Service

– Best route

l After the automatically revertive gold service is rerouted, the
service is automatically reverted to the original path if the
l After the scheduled revertive gold service is rerouted, the user
can set the service to be reverted to the original path at a
specific future time (ranging from 10 minutes to 30 days) on
the NMS if the fault in the original path is rectified.
l After the non-revertive gold service is rerouted, the service
NOTE
Service migration l Supports migration between permanent connections and gold

services.
l Supports migration between gold services and diamond
services.
l Supports migration between gold services and silver services.
l Supports migration between gold services and copper
services.
ASON server trail Supports gold ASON server trails.
Alarms to trigger R_LOS, R_LOF, B2_EXC, B2_SD, MS_AIS, MS_RDI,

rerouting AU_AIS, B3_EXC (can be set), B3_SD (can be set)
1.6.6 Silver Services

Silver services, the revertive time is hundreds of milliseconds to several seconds. The silver level
service is suitable for those data or internet services that have low real-time requirement.
Silver services are also called rerouting services. When an LSP failure, the ASON triggers
rerouting to restore the service. If there are not enough resources, service may be interrupted.

As shown in Figure 1-44, A-B-G-H-I is a silver service trail. If the fiber between B and G is
cut, the ASON triggers rerouting from A to create a new LSP that does not pass the cut fiber.
Hence, services are protected.
Figure 1-44 A silver service
E
R1 R4
E
LSP after rerouting
I
D F
A C
B
H
G
R2
R3
Original LSP
: ASON NE
: User equipment
Table 1-22 lists the attributes of silver services.
Table 1-22 Attributes of silver services

Requirements for creation Sufficient non-protection resources are available between the
source node and the sink node.
Service restoration When the original LSP fails, rerouting is triggered to create a
new LSP to restore services.

– Best route


l After the automatically revertive silver service is rerouted,
the service is automatically reverted to the original path if the
l After the scheduled revertive silver service is rerouted, the
user can set the service to be reverted to the original path at
a specific future time (ranging from 10 minutes to 30 days)
on the NMS if the fault in the original path is rectified.
l After the non-revertive silver service is rerouted, the service
NOTE
Shared mesh restoration Supports setting the shared mesh restoration trial for revertive
trail silver trials.
Service migration l Supports migration between permanent connections and

silver services.
l Supports migration between diamond services and silver
services.
l Supports migration between gold services and silver
services.
l Supports migration between silver services and copper
services.
ASON server trail Supports silver ASON server trails.
Alarms to trigger rerouting R_LOS, R_LOF, B2_EXC, B2_SD, MS_AIS, MS_RDI,

AU_AIS, B3_EXC (can be set), B3_SD (can be set)
1.6.7 Copper Services

The copper services are seldom used. Generally, temporary services, such as the abrupt services
in holidays, are configured as copper services.
Copper services are also called non-protection services. If an LSP fails, services do not reroute
and are interrupted. Table 1-23 lists the attributes of copper services.

Table 1-23 Attributes of copper services

Attribute Silver Service
Requirements for Sufficient non-protection resources are available between the source
creation node and the sink node.
Service restoration Does not support rerouting.
Service migration l Supports migration between copper services and traditional

services.
l Supports migration between copper services and diamond services.
l Supports migration between copper services and gold services.
l Supports migration between copper services and silver services.

optimization
ASON server trail Supports ASON server trails.
1.6.8 Iron Services

The iron services are also seldom used. Generally, temporary services are configured as iron
services. For example, when service volume soars, during holidays, the services can be
configured as iron services to fully use the bandwidth resources.
An iron service is also called a preemptable service. Iron services apply non-protection resources
or protection resources of the TE link to create LSPs. When an LSP fails, services are interrupted
and rerouting is not triggered.
l When the iron service uses the protection resources of the TE link, if the MS switching
occurs, the iron service is preempted and the service is interrupted. After the MS is
recovered, the iron service is restored. The interruption, preemption and restoration of the
iron service are all reported to the U2000.
l When the iron service uses the non-protection resources, if the network resources are
insufficient, the iron service may be preempted by the rerouted silver service or diamond
service. Thus, the service is interrupted.
Table 1-24 lists the attributes of iron service.
Table 1-24 Attributes of iron services

Attribute Iron Service
Requirements Sufficient protection resources or non-protection resources are available

for creation between the source node and the sink node.

Attribute Iron Service
Multiplex To create iron services, the following resources can be used:

section l Protection resources of 1:1 linear MSP
protection
l Protection resources of 1:N linear MSP
l Protection resources of two-fiber bidirectional MSP
l Protection resources of four-fiber bidirectional MSP
Service Does not support rerouting.

restoration
Service Supports migration between iron services and extra permanent


optimization
1.6.9 Tunnels
Tunnels are mainly used to carry VC-12 or VC-3 services. Tunnels are also called as ASON
server trails.
When lower order services are to be created, first create a VC-4 tunnel. The protection level for
the tunnel can be diamond, gold, silver or copper. Then, use the management system to complete
the configuration of the lower order service. See Figure 1-45.
Figure 1-45 Tunnel
VC-4 tunnel VC-12 service
R4
R1
R3
R2
: ASON NE
ASON domain : User equipment
The configuration of a tunnel is different from that of the above-mentioned service types. Its
cross-connection from the tributary board to the line board can only be configured manually. As
shown in Figure 1-46, there is a tunnel between NE1 and NE2 which can be a diamond ASON

server trail, a gold ASON server trail, silver ASON server trail or copper ASON server trail.
During service creation, the ASON automatically chooses the line boards of NE1 and NE2 and
the timeslots of the line boards.
After creating tunnels, you must manually create and delete the lower order cross-connection
from the tributary board to the line board. During rerouting or optimization of the tunnels,
however, the cross-connections at the source and sink nodes automatically switch to the new
ports.
NOTE
In addition, the end-to-end tunnel and lower order service can be created.
Figure 1-46 Lower cross-connection
VC-12 ASON server trail VC-12
NE1 VC-4 NE2
Cross-
connection
VC-12
Tributary unit Line unit
Table 1-25 lists the attributes of tunnels.
Table 1-25 Attributes of tunnels

Attribute Gold Tunnel Silver Tunnel Copper Tunnel
Requirement Same as gold services Same as silver services Same as copper

s for creation services
Service Same as gold services Same as silver services Does not support
restoration rerouting
Rerouting l Supports rerouting l Supports rerouting Does not support

lockout. lockout. rerouting
l Supports rerouting l Supports rerouting
priority. priority.
Revertive Supported Supported Not supported
Pre- Supported Supported Not supported

configuratio
n of restoring
route
Service Not supported Supported Supported

association

Attribute Gold Tunnel Silver Tunnel Copper Tunnel
Service l Supports migration between tunnel services and permanent connections.

migration l Supports migration between silver tunnels and copper tunnels.
l Supports migration between gold tunnels and silver tunnels.
l Supports migration between gold tunnels and copper tunnels.

optimization
Tunnel level VC-4
1.6.10 Shared Mesh Restoration Trail

On the OCS network, in the case of a revertive silver service, a restoration trail can be reserved.
In the case of rerouting, the silver service reroutes to the reserved restoration trail. Such a
restoration trail is called a shared mesh restoration trail.
When a service configured with the shared mesh restoration trail reroutes, the service uses the
resources on this trail with priority. If all resources on the shared mesh restoration trail are usable,
these resources are used for service restoration. If only partial resources on the shared mesh
restoration trail are usable, these resources are used with priority for computation of a restoration
trail. The other resources may be faulty or used by other services that share the trail.
As shown in Figure 1-47, the shared mesh restoration trail for two revertive silver services share
the TE link and timeslots between G and H. When the revertive silver service 1 (A-B-C) reroutes,
the service directly reroutes to the shared mesh restoration trail 1 (A-G-H-C). When the revertive
silver service 2 (D-E-F) reroutes, the service directly reroutes to the shared mesh restoration trail
2 (D-G-H-F). If both silver services reroute, only one of them can reroute to the shared mesh
restoration trail, for the two restoration trails share the TE link and timeslots between G and H.
Figure 1-47 Shared mesh restoration trail

Revertive silver service 1
A B C
Share MESH
restoration trail 1
G H
Share MESH
restoration trail 2
D E F
Revertive silver service 2

Features of the Shared Mesh Restoration Trail

The shared mesh restoration trail has the following features.
l Only the revertive silver service can be configured with the shared mesh restoration trail.
l A shared mesh restoration trail cannot be set to concatenation services at different levels.
l For a silver service configured with the shared mesh restoration trail, the revertive attribute
cannot be changed.
l The resources on a shared mesh restoration trail can only be the unprotected resources of
TE links.
l For a silver service configured with the shared mesh restoration trail, do not set the preset
restoration trail.
Differences Between Shared Mesh Restoration Trail and Preset Restoration Trail
The shared mesh restoration trail and the preset restoration trail have the following differences.
l For a preset restoration trail, only route information of the trail is recorded and no resources
are actually reserved. In this way, the resources for a preset restoration trail may be used
by other services. When the service reroutes, the preset restoration trail cannot be used.
l For a shared mesh restoration trail, resources are actually reserved. The reserved resources
cannot be used by other services. In this way, services can be restored with the best effort.
In addition, to increase the resource utilization, the shared mesh restoration trails for
different services can share some resources.
NOTE
The preset restoration trail and the shared mesh restoration trail adopt different restoration mechanisms
and thus cannot be used at the same time.
1.6.11 Crankback Mechanism

The Crankback mechanism during rerouting, optimization, and creation of the wavelength/sub-
wavelength LSP is supported.
It takes a certain time to spread network routing information. When rerouting is performed, the
source node may use the outdated network status information to calculate the trail. Therefore,
the selected route may be unavailable, resulting in a rerouting failure.
The ASON software supports the Crankback rerouting mechanism. When setting up connections
according to the calculated trail, the ASON software informs the source node of the information
related to the faulty network nodes or links if the connection setup process is baffled due to
insufficient network resources or network faults. In this case, the source node recalculates a trail
that meets the constraint conditions but does not traverse the obstacle node and then establishes
the connections for the calculated trail. This effectively restores a service by means of rerouting.
1.6.12 Network Traffic Engineering

An ASON network has one network traffic engineering policies, that is, network traffic
equilibrium, so as to make network resources distributed in the best state. In addition, various
restraint conditions for route selection are developed. In this manner, network resources are
properly used.

Network Traffic Equilibrium

Due to manual planning of services on a traditional network, it is difficult for the traditional
network to achieve traffic equilibrium on the entire network. The introduction of ASON features
makes the network resources automatically adjusted. With the traffic engineering algorithm, the
resources of the entire network can be automatically and evenly allocated, which avoids
congestion and improves network security and operability.
On an ASON network, the traffic of each trail is equalized, and thus the situation where the
traffic of certain trails is large but certain trails are idle can be avoided.
The ASON computes a best route according to the CSPF algorithm. If there are many services
between two nodes, there may be several services sharing a same route. The traffic equilibrium
function is used to avoid this situation. As shown in Figure 1-48, there are many silver services
between R2 and R4. To make the network more safe and reliable, the ASON allocates them to
different routes such as A-D-E-I, A-B-C-F-I and A-B-G-H-I as evenly as possible. In this
manner, network security and stability are enhanced.
Figure 1-48 Traffic equilibrium
R1 R4
E
I
D
F
C
A
B
H
G
R2
R3
: ASON NE
: User equipment
Route Selection Policy

With traffic engineering, Huawei ASON equipment develops various constraint conditions on
the control plane for route selection based on the WDM/OTN ASON network. The constraint
conditions for route selection are as follows:
l Constraint conditions for network resources (explicit node, explicit link, explicit
wavelength, and explicit channel)
l Constraint conditions for exclusion of network resources (excluded node and excluded link)
l Strict route and number of nodes (hops) that a service traverses
l Fiber length of a service, load balancing, SRLG, and associated services
l Combination of the preceding constraint conditions

The constraint conditions for the ASON wavelength or sub-wavelength services are mainly
reflected in the trail cost. The trail cost includes the following factors:
l Link bandwidth occupancy
l Link length
l Number of nodes (hops) that a service traverses
During service route computation, you should consider the preceding factors of the trail cost
(the function of setting the weight of each factor is provided), and thus you can select the route
with the minimum trail cost. In this manner, the traffic is equalized and the network resources
are properly used.
Customized Link Cost

The ASON software supports the customized link cost. Hence, users can adjust the link cost and
select the expected link according to actual situations. After the customized link cost is
introduced, the trail with the lowest cost is selected according to the integrated cost of a link
during service creation or rerouting.
The customized link cost is used to describe the customized link attributes. By using the
customized link cost, users can assign different meanings to a link. The examples are as follows:
l Link age
The cost of a link ascends with the age of the link. When computing a trail, the ASON
software is more likely to select a new trail.
l Link price
The cost of a link ascends with the price of the link. When computing a trail, the ASON
software is more likely to select a cheap trail.
l Link interruption rate
The cost of a link ascends with the link interruption rate. When computing a trail, the ASON
software is more likely to select a trail with a low link interruption rate.
The customized link cost can be queried, and a change of the customized link cost on a node
can be flooded to all nodes on the entire network. In this manner, all nodes on the network
acknowledge the customized link cost information, which can be used as a basis of computing.
Shared Risk Link Group

On an ASON network, a shared risk link group (SRLG) needs to be set when a group of optical
fibers are in one cable.
SRLG represents the shared risk link group. Fibers in the same optical cable have the same risk.
That is, when the cable is cut, all fibers are cut. Hence, an ASON service should not be rerouted
to another link that has the same risk.
Hence, an SRLG needs to be correctly set for the links sharing the same risk on a network so as
to avoid the situation where an LSP after rerouting of ASON services traverses a link that has
the same risk as that of the faulty link. In this manner, the service restoration time during ASON
service rerouting is shortened. You can change the SRLG attribute.
When an electrical-layer service selects its trail, the electrical-layer link inherits the SRLG
information of the links involved in its electrical server layer and the SRLG information of the
links involved in its optical server layer. As a result, during rerouting, the electrical-layer service
follows the principle of separating SRLGs as possible.

1.6.13 Service Association

Service association can be used to associate the same services accessed from different points
into an ASON network.
Service association involves associating two ASON services that have different routes. During
rerouting or optimization of either service, the rerouting service avoids the route of its associated
service. Service association is mainly used for services (dual-source) accessed from two points.
As shown in Figure 1-49, D-E-I and A-B-G-H are two associated LSPs. When the fiber between
B and G is cut, rerouting of A-B-G-H LSP avoids D-E-I LSP.
Figure 1-49 Service association
R1 R4
E
1+1protection
I 1+1protection
D
F
C
A
B
H
G
R2
R3
: ASON NE
: User equipment
Table 1-26 lists the attributes of service association.
Table 1-26 Attributes of service association

Service creation Supports the creation of the associated services with the same source
node.
Service Supports optimization of associated services.

optimization
Rerouting When one service reroutes, it avoids the route of the associated service.
Service type l Supports the association of two silver services.

l Supports association of two copper services.
l Supports the association of a silver service and a copper service.
l Supports the association of two silver tunnels.
l Supports the association of two copper tunnels.
l Supports the association of a silver tunnel and a copper tunnel.

1.6.14 Service Optimization

After the topology changes several times, the ASON may have less satisfactory routes and thus
requires service optimization. Service optimization involves creating a new LSP, switching the
optimized service to the new LSP, and deleting the original LSP to change and optimize the
service without disrupting the service. Of course, the service route can be restricted during the
service optimization.
LSP optimization has the following features.
l Only manual optimization is supported.
l The optimization does not change the protection level of the optimized service.
l During optimization, rerouting, downgrade/upgrade, or deleting operations are not allowed.
l During creation, rerouting, downgrading/upgrading, starting or deleting operations,
optimization is not allowed.
l The following service types support optimization: diamond, gold, silver, copper, iron and
tunnel services.
1.6.15 Service Migration

OptiX ASON software supports the conversion between ASON services, and between ASON
services and traditional services. The service conversion is in-service conversion, which would
not interrupt the services.
Service Migration between ASON Trails and Permanent Connections

Currently, Huawei ASON software supports the following migration between the traditional
SDH services and ASON services:
l Migration between diamond services and permanent SNCP connections
l Migration between gold services and permanent connections
l Migration between silver services and permanent connections
l Migration between copper services and permanent connections
l Migration between iron services and permanent connections
l Migration between tunnel services and server trail.
Service Migration between ASON Trails

The ASON software supports the following migration between the traditional SDH services and
ASON services:
l Migration between diamond, gold, silver, and copper services
l Migration between diamond, gold, silver, and copper tunnels
1.6.16 Preset Restoration Trail

Customers may require that the services route to a specified trail in the case of trail failure. To
this end, the ASON software provides the function of presetting the trail for restoration. This
function helps increase the controllability of service routing. The preset restoration trail
information is stored only on the control plane and requires no physical resource.
The ASON software supports setting a preset restoration trail for a diamond/silver/gold ASON
trail. When the ASON trail reroutes, the service is restored to the preset restoration trail first.

In the case of a service configured with a preset restoration trail, when this preset restoration
trail fails, the system recalculates a new preset restoration trail during regular detection (by
default, the interval is 60 minutes) and reports a preset restoration trail update event to the NMS.
1.6.17 Trail Pre-Computation and Adjustment

When optimizing the routes of new ASON services or original services, users can issue the route
pre-computation command through the U2000. In this manner, users can acknowledge the
service routes to be created, routes after optimization, specific routes involving service
restoration trails in advance. In addition, users can properly adjust the pre-computed trail
according to service trail requirements.
1.6.18 Reverting Services to Original Routes

After many changes in an ASON network, service routes may differ from the original routes.
You can revert all service to the original routes.
Generally, the route during ASON service creation is the original route of the ASON service. If
the original route recovers after rerouting of the ASON services, the services can be adjusted to
the original route manually.
1.6.19 Amalgamation of ASON and LCAS

In OCS networking, the ASON supports amalgamation of ASON and LCAS.
LCAS
LCAS is Link Capacity Adjustment Scheme. With LCAS enabled, the bandwidth of VCTRUNK
can be adjusted dynamically without affecting services. As shown in Figure 1-50, VCTRUNK1
is bound with four VC4s, with two transmitted over path 1 and two over path 2. If the VC-4 in
path 1 fails, the two VC4s in path 2 will transmit all Ethernet service without affecting the service
of VCTRUNK1. You can add VC-4 on either path if necessary.
Figure 1-50 LCAS (different path)
Path 1
VCTRUNK1
Router A Router B
NE1 NE2
Path 2
If these VC4s are transmitted over a path, adding/deleting VC-4 will not affect the service. As
shown in Figure 1-51, VCTRUNK1 is bound with four VC4s. If the first VC-4 fails, the Ethernet
service remains unaffected.

Figure 1-51 LCAS (same path)
VCTRUNK1
Router A Router B
NE1 NE2
ASON Trail Group

An ASON trail group associates all member trails for the same LCAS service within one LSP
group. These member trails then can be added, deleted or modified. To provide virtual services
with the error tolerance ability, these member trails must be as separate as possible.
Each ASON trail group is identified by an ID. The ASON NE allocates an ID to each ASON
trail group. The member trails within an ASON trail share the same source and sink. The trails
must also be as separated as possible.
1.6.20 Merging an ASON Network with a Traditional SDH

Network
An ASON network can be used with an SDH network to form a hybrid network. In this case, an
end-to-end service can be managed and created in a centralized manner.
A Traditional SDH Network Connected to an ASON Network in 1+1 or 1:1 MSP

Mode
A traditional SDH network is connected to an ASON network in 1+1 or 1:1 MSP mode. The
connection between the SDH network and the ASON network is protected in linear MSP mode.
The ASON network adopts the intelligent protection or restoration mode. In addition, the ASON
network can access a diamond service, a gold service, or a silver service, as shown in Figure
1-52.

Figure 1-52 A traditional SDH network connected to an ASON network in 1+1 or 1:1 MSP
mode
1+1 or 1:1 MSP
MSP Ring
ASON
: ASON NE
: SDH NE
A Traditional SDH Network Connected to an ASON Network in SNCP Mode

A traditional SDH network is connected to an ASON network in SNCP mode. In this case, a
service can be protected in SNCP mode. The SDH network adopts the traditional SNCP mode.
The ASON network adopts the intelligent protection or restoration mode. As shown in Figure
1-53, the service can also be protected if two fiber cuts occur.
Figure 1-53 A traditional SDH network connected to an ASON network in SNCP mode
SNCP Access SNCP Access
Dual-fed
selective
receiving
SNCP
SDH ASON SDH
Dual-fed
selective
receiving
SNCP
: ASON NE
: SDH NE
VC-4 Services Between SDH NEs That Cross the ASON Network
As shown in Figure 1-54, a VC-4 service is created between SDH NEs 5 and 6 and crosses the
ASON network. The ASON network adopts the intelligent protection or restoration mode. The
SDH network is not protected.

Figure 1-54 VC-4 services between SDH NEs that cross the ASON network
NE1 NE4
NE6 NE5
VC-4 VC-4
NE2 NE3
: ASON NE
: SDH NE
VC-12 Services Between SDH NEs That Cross the ASON Network
As shown in Figure 1-55, a VC-12 service is created between SDH NEs 5 and 6 and crosses the
ASON network. The ASON network adopts the intelligent protection or restoration mode. The
SDH network is not protected.
Figure 1-55 VC-12 services between SDH NEs that cross the ASON network
NE1 NE4
NE6 NE5
VC-12
VC-12
NE2 NE3
: ASON NE
: SDH NE

1+1 VC-4 Services Between Traditional NEs That Cross the ASON Network
As shown in Figure 1-56, a 1+1 VC-4 service is created between SDH NEs 5 and 6 and crosses
the ASON network. The ASON network adopts the intelligent protection or restoration mode.
The SDH network adopts the SNCP protection mode.
Figure 1-56 1+1 VC-4 services between SDH NEs that cross the ASON network
NE1 NE4
NE6 NE5
VC-4
VC-4
NE2 NE3
: ASON NE
: SDH NE
1+1 VC-12 Services Between SDH NEs That Cross the ASON Network
As shown in Figure 1-57, a 1+1 VC-12 service is created between SDH NEs 5 and 6 and crosses
the ASON network. The ASON network adopts the intelligent protection or restoration mode.
The SDH network adopts the SNCP protection mode.

Figure 1-57 1+1 VC-12 services between SDH NEs that cross the ASON network
NE1 NE4
NE6 NE5
VC-12 VC-12
NE2 NE3
: ASON NE
: SDH NE
VC-4 Services Between ASON NEs and Traditional NEs

As shown in Figure 1-58, a VC-4 service is created between traditional NE5 and ASON NE1.
The ASON network adopts the intelligent protection or restoration mode. The SDH network is
not protected.
Figure 1-58 VC-4 services between ASON NEs and SDH NEs
NE1 NE4
VC-4
NE6 NE5
VC-4
NE2 NE3
: ASON NE
: SDH NE

VC-12 Services Between ASON NEs and SDH NEs

As shown in Figure 1-59, a VC-12 service is created between SDH NE5 and ASON NE1. The
ASON network adopts the intelligent protection or restoration mode. The SDH network is not
protected.
Figure 1-59 VC-12 services between ASON NEs and SDH NEs
NE1 NE4
VC-12
NE6 NE5
VC-12
NE2 NE3
: ASON NE
: SDH NE
1+1 VC-4 Services Between ASON NEs and SDH NEs

As shown in Figure 1-60, a 1+1 VC-4 service is created between SDH NE5 and ASON NE1.
The ASON network adopts the intelligent protection or restoration mode. The SDH network
adopts the SNCP protection mode.

Figure 1-60 1+1 VC-4 services between ASON NEs and SDH NEs
NE1 NE4
VC-4
NE6 NE5
VC-4
NE2 NE3
: ASON NE
: SDH NE
1+1 VC-12 Services Between ASON NEs and SDH NEs

As shown in Figure 1-61, a 1+1 VC-12 service is created between SDH NE5 and ASON NE1.
The ASON network adopts the intelligent protection or restoration mode. The SDH network
adopts the SNCP protection mode.
Figure 1-61 1+1 VC-12 services between ASON NEs and SDH NEs
NE1 NE4
VC-12
NE6 NE5
VC-12
NE2 NE3
: ASON NE
: SDH NE

1.7 Optical-Layer and Electrical-Layer ASON Services

The ASON software provides the wavelength-level ASON services at the optical layer and sub-
wavelength level ASON services at the electrical layer. Hence, customers can implement flexible
service grooming at different layers.
1.7.1 Protection and Restoration Mechanisms for Services

Optical-layer and electrical-layer services have different protection and restoration mechanisms.
Protection and Restoration Mechanism for Optical-Layer ASON Services

Optical-layer ASON services combine protection mechanisms for the traditional WDM network
and the rerouting mechanism for the ASON network, and thus provide the capability of resisting
multiple faults. In the case of the rerouting mechanism for optical-layer ASON services, after
the services are interrupted, rerouting is initiated at the source node. Then, a new trail is set up
through ROADM cross-connections. Figure 1-62 shows the model of the traditional WDM
protection and restoration corresponding to optical-layer silver ASON services of source node
association. For the implementation principles of the client-side protection, see Client 1+1
Protection in the Feature Description.
Figure 1-62 Model of the protection for optical-layer ASON services
Optical-Layer Silver Service of source

node association (Client 1+1 Protection)
OTU FIU
OLP
ROADM
OTU FIU
Protection and Restoration Mechanism for Electrical-Layer ASON Services

Electrical-layer ASON services combine protection mechanisms for the traditional WDM
network and the rerouting mechanism for the ASON network, and thus provide the capability
of resisting multiple faults. In the case of the rerouting mechanism for electrical-layer ASON
services, after the services are interrupted, new services are created through the cross-
connections on the centralized cross-connect boards or tributary boards.Figure 1-63 shows the
model of the traditional WDM protection and restoration corresponding to typical type of
electrical-layer ASON services. For the implementation principles of the ODUk SNCP
protection, see ODUk SNCP in the Feature Description.

Figure 1-63 Model of the protection for electrical-layer ASON services
Electrical-Layer Diamond (ODUk SNCP Protection)
Line Unit
Tributary Unit ROADM
Line Unit
1.7.2 Quick Finding of Optical-Layer and Electrical-Layer Functions

The functions of optical-layer and electrical-layer services implemented by the ASON software
are different.
The WDM ASON features support the optical-layer ASON function and the electrical-layer
ASON function, as described in Table 1-27.
Table 1-27 Optical-layer ASON and electrical-layer ASON

Item Optical-Layer ASON Electrical-Layer ASON
Control channel D4-D12 bytes of the optical RES or SM_TTI and

supervisory channel (OSC) PM_TTI bytes of the OTN
in outband manner. overhead.
The system uses RES bytes
by default.
Supported service type Services of OCh wavelength Services of ODUk

level. wavelength level (k=0, 1,
2or 3).
Supported SLA Silver and copper. Diamond, silver, and copper.
Hardware configuration FIU board, SC1/2 board, and Cross-connect boards and
requirements WSS board. relevant tributary boards.
Rerouting trigger conditions Optical-layer SF and SD Electrical-layer SF and SD

alarms. For detailed alarms. For detailed
information refer to information refer to
Rerouting of an LSP. Rerouting of an LSP.
Rerouting mechanism After a service is interrupted, After a service is interrupted,

rerouting is initiated on the a new service is created
source node, and a new trail through cross-connections
is created through ROADM on the centralized cross-
cross-connections. connect board or tributary
board.

Item Optical-Layer ASON Electrical-Layer ASON
Special technology Wavelength tunable NA

rerouting, which solves the
wavelength blocking
problem in rerouting.
Table 1-28 lists the functions of optical-layer ASON services of different SLAs.
Table 1-28 Functions of optical-layer ASON services of different SLAs

Item Silver Service Copper Service
Protection and restoration Restoration No protection

policy No restoration
Technologies for Rerouting -

implementation
Technical implementation Real-time computation -

without presetting protection
channels
Bandwidth utilization High Excessively high
Supported Route pre- Supported Supported

functions computation
Route Supported Supported

optimization
and service
reversion
Conversion Supported Supported

between
traditional and
ASON services
Switching - -
between
services of
different SLAs
Pre-set Supported -
restoration trail
Service Supported Supported

association
Wavelength Supported -
tunable
rerouting

Item Silver Service Copper Service
Optical Supported Supported

parameters
Table 1-29 lists the functions of electrical-layer ASON services of different SLAs.
Table 1-29 Functions of electrical-layer ASON services of different SLAs
Item Diamond Service Silver Service Copper Service
Protection and Protection and Restoration No protection

restoration policy restoration No restoration
Technologies for ODUk SNCP and Rerouting -

implementation rerouting
Technical Protection always Real-time -

implementation provided when the computation without
network bandwidth presetting protection
is available channels
Bandwidth utilization Low High Excessively high
Support Routing Supported Supported Supported

ed pre-
function computatio
s n
Route Supported Supported -

optimizatio
n and
service
reversion
Conversio Supported Supported Supported

n between
traditional
and ASON
services
Switching Supported Supported Supported

between
services of
different
SLAs
Pre-set Supported Supported -

restoration
trail
Service - Supported Supported

association

Item Diamond Service Silver Service Copper Service
Wavelengt - - -
h tunable
rerouting
Optical - - -
parameters
1.7.3 Prerequisites for Enabling ASON Features

Certain hardware and software prerequisites must be available when the optical-layer and
electrical-layer ASON features are enabled.
The prerequisites for enabling the optical-layer ASON features are as follows:
l The OSC board must be configured.
l The FIU board must be configured.
l The WSS board must be configured.
l It is required to configure two SCC boards in the master subrack.
The prerequisites for enabling the electrical-layer ASON features are as follows:
l The centralized cross-connect board must be configured.
l It is required to configure two SCC boards in the master subrack.
The software prerequisites for enabling ASON features are as follows:
l The NE software version must support the ASON features. Contact Huawei engineers to
determine whether the current NE software version supports the ASON features.
l The version of the mapping NMS that is delivered must support the ASON features.
l The ASON features are controlled by the license on the NMS. The ASON features can be
enabled for only users who apply for and purchase this license or obtain a special permission
from Huawei.
NOTE
There are two types of license: the license for basic ASON features and the license for enabling services.
The first type of license is used to control the ASON features of a single station. The second type of license
is specific for the services on the entire network and is used to control the number of services of different
rates on an ASON network.
NOTE
l 2.5G and 5G boards do not support optical-layer ASON services.

l Individual tributary boards do not support optical-layer ASON services on their client sides.
1.7.4 Conditions for Configuring ASON Services

Certain configuration conditions must be met to ensure successful creation of the optical-layer
and electrical-layer ASON services.
NOTE
The optical power of each channel of an ASON NE must be controlled by the software, and thus an EVOA
must be configured inside the ASON NE.

Configuring Electrical-Layer ASON Services

In the case of electrical-layer ASON services, a centralized cross-connect board must be used
to groom sub-wavelength services. In the case of a site where the main and slave subracks are
configured, electrical-layer cross-connections cannot be groomed between subracks (between
the master and slave subracks and between slave subracks). Hence, the working trail and
protection trail (or restoration trail) of the electrical-layer services must be led out from the site
through the same subrack. See Figure 1-64.
Figure 1-64 Configuring electrical-layer ASON services

Tributary Working Cross-Connect Protection Retrieve
board board board board board
T N N N
Q S S S
X 2 2 2
Configuring Optical-Layer ASON Services

The process of configuring the optical-layer ASON services is more complex than the process
of configuring the electrical-layer ASON services.
The optical-layer ASON services are dynamic, and their restoration routes are not fixed.
Therefore, the reconfigurable optical add/drop multiplexer (ROADM) board should be
configured.
l One pair of WSS boards should be configured for each dimension.

l In the case of silver services, one pair of WSS boards should be configured at each
wavelength add/drop node.
l In the case of permanent 1+1 diamond service and rerouting 1+1 diamond service, two
pairs of WSS boards should be configured at each wavelength add/drop node (one pair is
for the working channel, and the other pair is for the protection channel).
The ASON protocol is embedded in the OSC overheads. Hence, the OSC board must be
configured.
Figure 1-65, which is the diagram for configuring the optical-layer ASON services, shows the
number of WSS boards required by the sliver services. If the services are diamond services with
the rerouting function, a pair of WSS boards (a pair of working boards and a pair of protection
boards) must be configured at points where the services are added and dropped.

Figure 1-65 Configuring optical-layer ASON services

Does not
support
OTU reroute
MR4
WSD9 RMU9
W E
FIU FIU
RMU9 WSD9
OSC WSD9 RMU9 OSC
MR4 Protection
trail Support
Working reroute
trail
OTU

ASON User Guide 2 Planning the OTN ASON
2 Planning the OTN ASON
About This Chapter
This chapter is a guide for planning the OTN ASON network, and describes the planning rules,
methodology and flow. It can be used as a reference for the ASON network design and expansion.
2.1 Requisite Knowledge on ASON Planning

To plan an ASON network, attain familiarity with the ASON-related knowledge and usage of
required planning tools.
2.2 ASON Network Planning Process
The planning of an ASON network covers several phases. For each phase, flow the specified
flow to perform operations.


2.1.1 Functions of an ASON Network

Before planning an ASON network, attain familiarity with the functions of an ASON network.
See 1.5 OTN ASON Feature.
2.1.2 Use of the Planning and Simulation Tool

Planning and simulation of ASON networks need to be performed using a specific tool.
The tool is composed of Planner and Modeler. The Planner is used to plan network capacity and
service route. The Modeler is used to verify the outcome obtained from the Planner.

2.2.1 Planning Flow

To plan an ASON network, follow the specified flow.
Figure 2-1 shows the flow for planning an ASON network.

Figure 2-1 Flow for planning an ASON network
Start
Specify planning
objective and strategy
Collect network
information
Analysis services
Design network
structure
If the network No
capacity meets the
requirements?
Yes
If the network No
reliability meets
the requirements?
Yes
Output the planning
result
End
2.2.2 Specifying Planning Objective and Strategy

Definite objectives and strategies are preconditions for planning an ASON network.
Before planning ASON network, specify the strategy and objective.
l Determine whether your planning objective is to improve bandwidth utilization or to
improve network reliability.
l Determine whether your planning strategy is to construct a new ASON network or to expand
the present network.
Specifying Planning Objective

Follow the following rules to determine your planning objective.
If you construct an ASON network aiming at the high network reliability, so as to allow the
network to withstand multiple fiber breakage incidents, more idle resources must be reserved.

Consequently, the construction cost is raised accordingly and is more likely to be higher than
the cost of a traditional ring network. Thus, the issue of balancing the network reliability against
the increase of construction cost must be considered.
If you construct an ASON network aiming at the protection function when the fiber is broken
and aiming at high bandwidth utilization, not many resources must be reserved and you can build
up an ASON network at a relatively low cost and take advantage of high bandwidth utilization.
Specifying Planning Strategy

Follow the following rules to determine your planning strategy.
All equipment used for network building or expansion should be WDM equipment. Based on
practice, it is recommended that you adopt the master-slave subrack mode for ASON services.
The master-slave subrack mode does not support electrical-layer grooming. Therefore, do not
adopt the master-slave subrack mode if the electrical-layer grooming between subracks is
required.In addition, the FIU, OSC, and WSS boards must be configured for the optical-layer
ASON services.
2.2.3 Collecting Network Information

This portion of work is similar to the work you do in planning a traditional network.
To construct an ASON network, you need to collect the following information, including fiber,
physical topology, nodes, and services.
NOTE
When planning the ASON network, you must learn the real-time requirement of services. The real-time
requirement is a major concern in classifying the service level.
Collecting Physical Topology and Fiber Information

The information of physical topology and fiber includes the following, but is not limited to the
following:
l Physical topology of a network

l Node placement
l Fiber amount, distance and speed among the nodes
l SRLG
l Wavelength amount
Collecting Service Matrix Information

Service matrix information is the basis for network planning, because it determines the position
of the network nodes, node equipment type, protection manner, restoration and size of network
resources.
Service matrix information should cover the current request and the potential requests that can
arise 3-5 years from now. The following information should be contained.
l Source node and sink node

l Service type (voice service or data service)

l Requirements for protection and restoration, such as the times that services can recover
from cable breakage and restoration time
l Service granularity and quantity
l Route constraints
NOTE
In practice, if you cannot provide the detailed information on a particular service, a reference service matrix
in line with your anticipation of service development must be delivered.
2.2.4 Analyzing Services

After collecting service information, analyze the services.
Analyzing Characteristic of Service Distribution

Analyze the service distribution based on the service matrix and confirm the characteristics of
the service distribution.
l Whether the services are centralized or decentralized.

l Whether a partitioned area is provided (each partitioned small area comprises one or two
large nodes and a number of small nodes). In addition, the nodes where substantial amount
of traffic is added and dropped must be spotted and must serve as a reference for network
structure design and ASON node selection.
Classifying the Service Level

ASON designed by Huawei can provide a five-level service protection: diamond, silver, copper,
and iron. The protection mechanism and bandwidth utilization supported by each level are
different. Classify the service level based on the following rules.
l Diamond services are suitable for services that are critical and require high reliability, such
as financial and banking services. In addition, diamond services are suitable for services
that have high real-time requirement.
l Silver services are suitable for data services that have low real-time requirement. Silver
services can improve the bandwidth utilization.
l Copper services are suitable for services that do not need protection, or for temporary or
contingent services.
l Iron services can be preempted. Iron services are suitable for services that do not need
protection, or for temporary or contingent services.
2.2.5 Designing Network Structure

After collecting information and performing service analysis, continue to design the network
structure.
Selecting ASON Nodes

Considering the physical topology, service matrix, geographical location and fiber resources,
you can select the core nodes as ASON nodes. As shown in Figure 2-2, the ASON node is
recommended to connect more than two other nodes, to secure network reliability. In other
words, the degree of each ASON node is more than two.

NOTE
The degree of ASON node is the number of fiber directions from this node to other nodes. If fibers between
two nodes are more than two, the degree is calculated as one. The degree of ASON network is the average
of the degree of all ASON nodes.
Figure 2-2 Selecting ASON nodes
For cases where a node is crucial and the degree of node is two, the node should be incorporated
in the ASON domain. In addition, you should add optical fibers to increase the degree and to
improve the protection ability.
The degree not only affects network reliability, but is also closely related to bandwidth
utilization. If a fiber is broken and services need to be restored, the available link number
increases when the degree of the node ascends. Because the resources used for restoration are
shared by all services, if the same reliability is requested, less sharing resources are reserved on
a link when the degree of the network ascends. In this manner, the network-wide bandwidth
utilization is raised and the cost is decreased.
In addition, the selection of ASON nodes is also associated with fiber connection. When planning
the fiber connection, take the following items into consideration.
l Distance between the two nodes

l Whether the optical fiber resources are available
l Whether the WDM system is applicable
l Possibility of branching out new fibers
Choosing Equipment Type

The equipment type can preliminarily be determined based on network topology, traffic at nodes,
and equipment feature. After the network capacity computation is complete, a particular
rearrangement can be made in line with the link and capacity situation of each node.
The following equipments support the ASON feature.
l OptiX OSN 8800

l OptiX OSN 6800

Access Means of ASON Services

In the case of accessing ASON services, do as follows.
l You can build up a new independent ASON network, in which the ASON nodes can directly
add and drop ASON services. In such a case, the tributary optical boards can be used to
directly access the ASON services.
l You can build up an ASON network at the backbone layer to groom the services at the
convergence layer that adopts the non-ASON equipment.
If the ASON equipment provides the optical-layer ASON services but the source node of
the services is on the non-ASON equipment, the ASON equipment and non-ASON
equipment should be interconnected through the FIU. In addition, the non-ASON
equipment should be configured with intra-board 1+1 wavelength protection, and two
associated optical-layer ASON services should be created on the ASON network.
2.2.6 Planning Network Capacity

The planning of network capacity is an important operation in planning an ASON network.
The network capacity is resource consumed by the network. The network capacity is closely
related to network structure and service constraint conditions, such as traffic, service reliability,
SLA, and route. The planning should be built upon the existing network information. On
condition that the constraint conditions are fulfilled, the network capacity should be fully used
after calculation for the purpose of cutting down on construction cost.
An ASON network is managed based on ASON domain. Try to manage one ASON network as
one ASON domain unless it is too large and needs to be divided. Table 2-1 provides the
limitations on the scale of an ASON domain.
Table 2-1 Limitations on the scale of ASON domain
ASON Domain Scale Limitation
Optical-Layer 1. The number of ASON NEs on the entire network cannot exceed 350.
ASON 2. The number of ROADM sites on the entire network cannot exceed
100.
3. The number of OLA sites on the entire network cannot exceed 250.
Electrical-Layer The number of electrical subracks on the entire network cannot exceed
ASON 150 OptiX OSN 8800 T32 equivalent subracks.
(one OptiX OSN 8800 T64 subrack = two OptiX OSN 8800 T32
subracks = four OptiX OSN 6800 subracks)
Service Reliability
When there is a fiber break on a WDM ASON network, services can be recovered as long as
reserved resources are enough. There is a contradiction between reliability and cost. The
reliability is increased when more idle resources are reserved and then more network cost is
induced.

On the network, it can be concluded that though the service is the same, the reliability level
increases from one fiber break incident to two fiber break incidents. Thus, the bandwidth
utilization is dropped by half and the network capacity is doubled.
Thus, in the network design, it is critical to clarify requirement for reliability, which is directly
related to network capacity and construction cost. The capability of a network to withstand fiber
breaks depends on the customer requirement on service protection and restoration.
If all links are required to have the capability to withstand multiple fiber breaks, a large number
of resources must be reserved. Hence, in order to reduce the cost, several critical links are
designed to withstand multiple fiber breaks and the remaining links are provided with protection
against one fiber break.
Route Constraint
Regarding service route on ASON networks, the following factors must be taken into account:
l The number of nodes that a service passes, which is technically termed as hop. On the
condition that other variables remain unchanged, a lesser hop count is preferred.
l Total transmission distance, which is a vital factor that induces time delay. On the condition
that other variables remain unchanged, a shorter distance is preferred.
l Load balance: services select the links that are less loaded to balance the traffic among
links.
In fact, the conditions mentioned above are rarely fulfilled at the same time. In practice, proper
weight should be allocated to each variable to achieve a satisfying overall performance. The
rules that should be obeyed are as follows.
l Service route on metropolitan networks: the least hop count on the basis of load balance
and shortest distance.
l Service route on trunk networks: the shortest distance on the basis of load balance and least
hop.
l As for the backup route, the rule of separating the backup routes from the working routes
must be applied in the first place. It helps protect the working and backup routes from being
affected at the same time in the case of a fiber or a node failure. The rules for separating
are as follows:
– Link disjoint
– Node disjoint
– SRLG disjoint
Commonly, link disjoint is chosen unless otherwise requested. If you are concerned with
node failures, then choose node disjoint. If multiple fibers are within the same channel,
then use SRLG disjoint. Other route constraints, such as double-accessed data services,
need to be allotted to varied routes.
Different route constraints may result in different routes and the network resource consumption
differs accordingly, sometimes considerably. Thus, you should set the route constraint prior to
the network capacity computation to gain sufficient capacity for the route constraint. Typically,
metropolitan networks emphasize on a minimum hop count and trunk networks emphasize on
the shortest distance.

Network Capacity Computation

In ASON networks, services of different levels occupy different amount of resources. See Table
2-2.
Table 2-2 Resource occupation of different services

Service Working Resource Protection Resource Restoration Resource
Diamond Bandwidth of working Bandwidth of protection Network-wide

routes routes restoration resource
Silver Bandwidth of working None Network-wide

routes restoration resource
Copper Bandwidth of working None None

routes
Network capacity = total working resources + total protection resources + total restoration
resources + reserved resources
Restoration resources are shared network-wide to support restoration of diamond services, and
silver services. In addition, for the purpose of subsequent expansion, partial resources, such as
20% of the resources, are reserved.
ASON network capacity computation involves substantial amount of counting work and needs
specialized software.
The software needs the input of the following parameters:
l Network topology
l Service matrix
l Link distance
The software outputs the following parameters:
l Network capacity, including the number of ports on each node and bandwidth of each link
l Bandwidth utilization
l Working route, protection or restoration route of each service
At present, regarding service reliability, the capacity is currently calculated on the basis of
protection against one fiber break. In the case of multiple fiber breaks, refer to the following
solutions that are used in the case of two-time fiber breaks.
l Certain amount of network resources must be reserved. Commonly the requested amount
equals 2/N of the overall network capacity. "N" represents the network degree.
l The bandwidth utilization is set to be 1 - 2 / N (max).
l When the planning is complete, verification can be carried out using the software. If there
is an alert, the bandwidth at the bottleneck link should be increased.
2.2.7 Network Capacity Verification and Reliability Analysis

After the network capacity calculation is complete, you need to verify the network capacity and
analyze reliability.

In other words, you need to perform the simulation of the fiber break based on the capacity that
is currently available. Then, you can evaluate whether the capacity is sufficient and whether the
reliability meets the requirement by analyzing the service restoration situation after the fiber
break.
If the network capacity is insufficient and the reliability fails to meet your requirement, you need
to readjust or recount the network capacity. The fiber break simulation also helps identify the
key link and the bottleneck link. This information can be used for analysis to improve the network
structure. For example, fiber break simulation can determine the two nodes between which
capacity can be increased on the link.
At present, the tool software can be used to verify the network capacity and to analyze network
reliability. The tool can provide the following functions.
l Fault simulation: Simulate the condition in which the designated fiber (s) is (are) broken,
and then output the service restoration information:
– Services affected
– Services downgraded
– Services interrupted
– New service routes.
l Survivability analysis: After the fibers are chosen, use the method of exhaustion to simulate
the condition, and then output the service restoration information:
– Services affected during each break
– Services interrupted during each break.
During the simulation, the amount of counting work is too sizable if all fibers are selected. Thus,
as far as efficiency is concerned, you can first choose the vital links where heavy traffic is added
and dropped for simulation. Once you confirm the service restoration performance of those links,
you can carry out the simulation for other links.
Besides the size of traffic, you can also identify the vital links by means of network cutting.
Using this method, you can divide a network into two separate areas. The links that connect the
two areas are more likely vital ones. See Figure 2-3. After the network is cut, if A-F and B-C
are broken at the same time, the nodes between these two areas cannot communicate. Thus, these
two links are vital links.
Figure 2-3 Identifying vital links by network cutting

A B
F C
E D

If the network reliability meets your requirement, you can output the planning results including
the following factors.
l Network topology
l Network capacity
l Bandwidth of each link
l Port or timeslot amount of each node
l Service route

ASON User Guide 3 Planning the OCS ASON
3 Planning the OCS ASON
About This Chapter
This chapter is a guide for planning the OCS ASON network, and describes the planning rules,
methodology and flow. It can be used as a reference for the ASON network design and expansion.

3.3 ASON Network Planning Technologies
When planning an ASON network, some topologies may be involved, such as the MS and lower
order service.


3.1.1 Functions of an ASON Network

Before planning an ASON network, attain familiarity with the functions of an ASON network.
See 1.5 OTN ASON Feature.
3.1.2 Use of the Planning and Simulation Tool

Planning and simulation of ASON networks need to be performed using a specific tool.
The tool is composed of Planner and Modeler. The Planner is used to plan network capacity and
service route. The Modeler is used to verify the outcome obtained from the Planner.

3.2.1 Planning Flow

To plan an ASON network, follow the specified flow.
Figure 3-1 shows the flow for planning an ASON network.

Figure 3-1 Flow for planning an ASON network
Start
Specify planning
objective and strategy
Collect network
information
Analysis services
Design network
structure
If the network No
capacity meets the
requirements?
Yes
If the network No
reliability meets
the requirements?
Yes
Output the planning
result
End
3.2.2 Specifying Planning Objective and Strategy

Definite objectives and strategies are preconditions for planning an ASON network.
Before planning ASON network, specify the strategy and objective.
l Determine whether your planning objective is to improve bandwidth utilization or to
improve network reliability.
l Determine whether your planning strategy is to construct a new ASON network or to expand
the present network.
Specifying Planning Objective

Follow the following rules to determine your planning objective.
If you construct an ASON network aiming at the high network reliability, so as to allow the
network to withstand multiple fiber breakage incidents, more idle resources must be reserved.

Consequently, the construction cost is raised accordingly and is more likely to be higher than
the cost of a traditional ring network. Thus, the issue of balancing the network reliability against
the increase of construction cost must be considered.
If you construct an ASON network aiming at the protection function when the fiber is broken
and aiming at high bandwidth utilization, not many resources must be reserved and you can build
up an ASON network at a relatively low cost and take advantage of high bandwidth utilization.
Specifying Planning Strategy

Follow the following rules to determine your planning strategy.
Huawei OSN series equipment supports the ASON feature but the Metro series equipment does
not. To construct an ASON network, the OSN series equipment other than the Metro series
equipment, must be applied.
In the case of expanding an existing network, if the equipment in use belongs to the OSN series,
you only need to add the OSN equipment or links. For some OSN equipment that is not provided
with the ASON feature, if the physical equipment meets the requirement, the ASON feature can
be realized by upgrading the software. Contact Huawei to check if the SCC boards in the existing
network support the ASON feature. If the SCC boards in the present network do not support the
ASON feature, replace these SCC boards with SCC boards of a later version.
If the Metro equipment is used in the present network, the ASON feature cannot be realized
through the upgrade. But you can achieve the ASON feature using the same means as what is
applied in constructing a new network, such as adding an ASON core layer on the existing
network, or constructing a new ASON transport network by installing the OSN equipment in
each Metro node.
3.2.3 Collecting Network Information

This portion of work is similar to the work you do in planning a traditional SDH network.
To construct an ASON network, you need to collect the following information, including fiber,
physical topology, nodes, and services.
NOTE
When planning the ASON network, you must learn the real-time requirement of services. The real-time
requirement is a major concern in classifying the service level.
Collecting Physical Topology and Fiber Information

The information of physical topology and fiber includes the following, but is not limited to the
following:
l Physical topology of a network

l Node placement
l Fiber amount, distance and speed among the nodes
l SRLG
l WDM equipment
l Wavelength amount
Figure 3-2 shows the physical topology and fiber information from an operator.

Figure 3-2 Physical topology and fiber information
Collecting Service Information

Service information is the basis for network planning, because it determines the position of the
network nodes, node equipment type, protection manner, restoration and size of network
resources.
Service information should cover the current request and the potential requests that can arise
3-5 years from now. The following information should be contained.
l Source node and sink node
l Service type (voice service or data service)
l Requirements for protection and restoration, such as the times that services can recover
from cable breakage and restoration time
l Service granularity and quantity
l Route constraints
NOTE
In practice, if you cannot provide the detailed information on a particular service, a reference service matrix
in line with your anticipation of service development must be delivered.
Table 3-1 shows the service matrix information supplied by operator A. The service matrix
information encompasses the data and voice services in the years of 2007 and 2008. Table
3-2 shows the service matrix information supplied by operator B.
Table 3-1 Service information of operator A
Source Sink Node Voice Service Data Service

Node
2007 2008 2007 2008
STM-1 STM-1 GE GE
A C 4 6 1 4
A D 1 4 1 3
A E 1 3 3 5

Source Sink Node Voice Service Data Service

Node
2007 2008 2007 2008
STM-1 STM-1 GE GE
B C 3 5 1 2
B D 1 6 2 5
Table 3-2 Service information of operator B
Node A B C D E F G H I Tot
al
A 30 5 9 9 7 3 9 3 75
B 30 5 4 4 5 3 9 6 66
C 5 5 - - - - - - 10
D 9 4 - - - - - - 13
E 9 4 - - - - - - 13
F 7 5 - - - 2 - - 14
G 3 3 - - - 2 1 - 9
H 9 9 - - - - 1 3 22
I 3 6 - - - - - 3 12
Total 75 66 10 13 13 14 9 22 12 234
The unit of services is 155 Mbit/s.
3.2.4 Analyzing Services

After collecting service information, analyze the services.
Classifying the Service Type

You can classify services into the following types according to service source.
l VIP private line

l Voice service
l Date service
You can classify services into the following types according to the service rate.
l Service of large granularity (such as concatenation service)

l Higher order service (such as 155 Mbit/s service)

l Lower order service (such as 2 Mbit/s service)
Analyzing Characteristic of Service Distribution

Analyze the service distribution based on the service matrix and confirm the characteristics of
the service distribution.
l Whether the services are centralized or decentralized.
l Whether a partitioned area is provided (each partitioned small area comprises one or two
large nodes and a number of small nodes). In addition, the nodes where substantial amount
of traffic is added and dropped must be spotted and must serve as a reference for network
structure design and ASON node selection.
Classifying the Service Level

ASON designed by Huawei can provide a five-level service protection: diamond, gold, silver,
copper, and iron. The protection mechanism and bandwidth utilization supported by each level
are different. Classify the service level based on the following rules.
l Diamond services are suitable for services that are critical and require high reliability, such
as financial and banking services. In addition, diamond services are suitable for services
that have high real-time requirement.
l Gold services are suitable for services that are important and request good real-time
requirement, such as voice services. The gold services have better reliability than the
traditional MSP services.
l Silver services are suitable for data services that have low real-time requirement. Silver
services can improve the bandwidth utilization.
l Copper services are suitable for services that do not need protection, or for temporary or
contingent services.
l Iron services can be preempted. Iron services are suitable for services that do not need
protection, or for temporary or contingent services.
The service level relates to the QoS feature and network resource occupation. Follow the
following rules to determine the service level in advance.
l Permanent 1+1 diamond services need large consumption of network resources and are
suitable for very important services. In addition, the rerouting 1+1 diamond service and
non-rerouting diamond service have different bandwidth utilization and protection ability.
You can select a type according to the actual situation.
l Common voice data can use the gold service, but for cases where the voice data fails to be
centralized to an MS ring, the diamond service can be applied as an alternative.
l Data services typically use the silver service because of their low real-time requirement.
You can also take advantage of virtual concatenation function which allows GE to be
managed in terms of divided VC-4 services. In addition, you can use higher level services
for data services that are very important.
l For double-accessed data services, you can use two associated services, including one silver
service, and one silver service, copper service, or iron service. In this way, resources can
be saved.
3.2.5 Designing Network Structure

After collecting information and performing service analysis, continue to design the network
structure.

Selecting ASON Nodes

Considering the physical topology, service matrix, geographical location and fiber resources,
you can select the core nodes as ASON nodes. As shown in Figure 3-3, the ASON node is
recommended to connect more than two other nodes, to secure network reliability. In other
words, the degree of each ASON node is more than two.
NOTE
The degree of ASON node is the number of fiber directions from this node to other nodes. If fibers between
two nodes are more than two, the degree is calculated as one. The degree of ASON network is the average
of the degree of all ASON nodes.
Figure 3-3 Selecting ASON nodes
For cases where a node is crucial and the degree of node is two, the node should be incorporated
in the ASON domain. In addition, you should add optical fibers to increase the degree and to
improve the protection ability.
The degree not only affects network reliability, but is also closely related to bandwidth
utilization. If a fiber is broken and services need to be restored, the available link number
increases when the degree of the node ascends. Because the resources used for restoration are
shared by all services, if the same reliability is requested, less sharing resources are reserved on
a link when the degree of the network ascends. In this manner, the network-wide bandwidth
utilization is raised and the cost is decreased.
In addition, the selection of ASON nodes is also associated with fiber connection. When planning
the fiber connection, take the following items into consideration.
l Distance between the two nodes
l Whether the optical fiber resources are available
l Whether the WDM system is applicable
l Possibility of branching out new fibers
Choosing Network Structure

The core nodes are the nodes where large amounts of traffic are added and dropped, and they
hold important positions, demand high reliability, and have ample fiber resources. Thus, ASON
is introduced to the backbone layer. Figure 3-4 shows the typical network architecture. The

ASON backbone layer uses the MESH topology and the traditional SDH ring is used for
convergence and access layers.
Figure 3-4 ASON network architecture
Backbone layer
Access Layer
Traditional SDH network
Design the network according to the following rules.
l Increase the degree of nodes as much as possible.

l For nodes where large amounts of traffic are added and dropped, use straight fiber
connections between them as much as possible.
Figure 3-5 shows the ASON network in a city. The five core nodes are mutually connected and
the degree is four. The network has a high level of reliability and proper use of bandwidth.
Figure 3-5 ASON network in a city
OSN 9500
Metro 5000
Degree = 4
Metro 3000
10Gbit/s link

Choosing Link Bandwidth

Regarding the link bandwidth between the ASON nodes, there may be multiple 2.5 Gbit/s or 10
Gbit/s links. The bandwidth is related to traffic. You can adjust the link bandwidth after
subsequent network capacity computation.
Choosing Equipment Type

The equipment type can preliminarily be determined based on network topology, traffic at nodes,
and equipment feature. After the network capacity computation is complete, a particular
rearrangement can be made in line with the link and capacity situation of each node.
The following equipments support the ASON feature.
l OSN 8800
l OSN 9500
l OSN 7500
l OSN 3500
l OSN 3500 II
l OSN 2500
l OSN 1500
Choose equipment type according to the following rules.
l The OptiX OSN 9500 and OptiX OSN 8800 that has a great service grooming capacity is
mainly used on a core node in the backbone layer.
l In the case of the nodes whose services increase on a yearly basis, equipment with large
capacity, such as the OptiX OSN 8800, is highly recommended during the initial phase of
the network construction.
l The OptiX OSN 7500 and OptiX OSN 3500 are mainly used on convergence nodes to
access E1 or FE service.
l The OptiX OSN 2500 and OptiX OSN 1500 are mainly used on access nodes.
CAUTION
The OptiX OSN 9500 has a capacity of 20 Gbit/s lower order cross-connection, but it cannot
directly access E1 or FE service. The OptiX OSN 9500 can use the OptiX OSN 7500 or the
OptiX OSN 3500 as its extended subrack, to access E1 or FE service. The extended subrack
accesses the OptiX OSN 9500 by using the 1+1 or 1:1 linear MS.
Planning MSP
Gold services run on the working link of MS ring or 1:1 linear MS. Iron services run on the
protection link of MS ring or 1:1 linear MS. Other services cannot run on the link of MS. Thus,
you should determine which links should be configured with MSP.
Plan the MSP according to the following rules.
l All links of the gold services should be configured with MSP.

l All links of the iron services should be configured with MSP.

l Partial fiber resource is recommended to be applied for the MSP, so that the remaining non-
protected timeslots can be used for creating or rerouting of other services. This arrangement
shows its significance when the fiber resources are insufficient. As shown in Figure 3-6,
the partial timeslot resource of an STM-64 link is used for an STM-32 MSP.
Figure 3-6 Timeslot allocation of an MSP occupying the partial resource of a fiber
1-16 Working timeslot

17-32 Non-protection timeslot
49-64 Non-protection timeslot
33-48 Protection timeslot
Access Means of ASON Services

In the case of accessing ASON services, do as follows.
l You can build up a new independent ASON network, in which the ASON nodes can directly
add and drop ASON services. In such a case, the tributary optical boards can be used to
directly access the ASON services.
l You can build up a new independent ASON network, in which the ASON services are
added and dropped through the extended subracks. In such a case, the extended subrack
dose not support the ASON feature, so consideration must be taken into how an ASON
network accesses the ASON services from the subracks. Commonly, the ASON services
can be accessed by means of 1:1 or 1+1 linear MSP. One benefit of configuring 1+1
protection is that if the subracks support ASON feature in future, the operation is much
easier.
You can build up an ASON network at the backbone layer to groom the services at the
convergence layer. In such a case, how the ASON network accesses the services from the
convergence layer is determined by how the ASON backbone layer and the SDH convergence
layer are connected.
l If the convergence layer and the backbone layer are connected with one tangent point, the
services can be accessed to the ASON backbone layer in the form of the ring MS services.
l If the convergence layer and the backbone layer intersect at two points, the services can be
accessed to the ASON backbone layer in the form of either the MS services or the SNCP
services. If the services are accessed through MS, the services are interrupted when the NE
at the accessing point becomes invalid. SNCP can protect the services from being affected
in case of the access node failure.
3.2.6 Planning Network Capacity

The planning of network capacity is an important operation in planning an ASON network.
The network capacity is resource consumed by the network. The network capacity is closely
related to network structure and service constraint conditions, such as traffic, service reliability,
SLA, and route. The planning should be built upon the existing network information. On

condition that the constraint conditions are fulfilled, the network capacity should be fully used
after calculation for the purpose of cutting down on construction cost.
Service Reliability and Network Capacity

When there is a fiber break on an ASON network, services can be recovered as long as reserved
resources are enough. There is a contradiction between reliability and cost. The reliability is
increased when more idle resources are reserved and then more network cost is induced.
Figure 3-7 shows a simple network in which four nodes are connected with one another. The
silver 20xVC4 services are running between these four nodes. Assume that the link between
node A and node D is disconnected and the 20xVC4 services running between the two nodes
need to be recovered. In this case, the degree of node A is three, so 10xVC4 is requested to be
reserved on A-B, A-C, B-D, and C-D. To ensure that all services are protected from one fiber
break incident, the resource that must be reserved for each link is 10xVC4 and the resource that
must be reserved for the entire network is 6x10VC4.
Figure 3-7 Relation between reliability and network capacity

A A
20VC4 10VC4 20VC4 20+20VC4
D B D B
10VC4
20VC4
C C
In the case of the services related to In the case of the services related to
node A, the A-B link and the A-C link node A, the A-B link needs to
need to reserve a 10xVC-4 capacity reserve a (20+20)xVC-4 capacity to
to protect the service on the A-D protect the services on the A-D link
link, when a one-time fiber cut and on the A-C link, when a two-time
occurs in the network. fiber cut occurs in the network.
In this case, bandwidth utilization and network capacity are listed as follows.
l Bandwidth utilization ratio: 20 x 6/(20 x 6 + 10 x 6) = 66.6%

l Network capacity amount: 20 x 6 + 10 x 6 = 180VC4
Assume that the links A-D and A-C are disconnected and the 20+20VC4 services need to be
recovered. In such a case, only the link A-B is available. 20+20VC4 must be reserved on link
A-B and 20VC4 must be separately reserved on link B-D and link B-C. Thus, to ensure that all
services are protected from two-fiber break incident, the resource that must be reserved for each
link is 40VC4 and the resource that must be reserved for the entire network is 6x40VC4.
In this case, bandwidth utilization and network capacity are listed as follows.
l Bandwidth utilization ratio: 20 x 6 / (20 x 6 + 40 x 6) = 33.3%

l Network capacity amount: 20 x 6 + 40 x 6 = 360VC4
From the two previous examples, it can be concluded that though the service is the same, the
reliability level increases from one fiber break incident to two fiber break incidents. Thus, the
bandwidth utilization is dropped by half and the network capacity is doubled.
Thus, in the network design, it is critical to clarify requirement for reliability, which is directly
related to network capacity and construction cost. Typically, the fiber break incident is set once
or twice so that excessive network resources are not occupied. The probability of a fiber break
occurring three times is less.
If all links are required to have the capability to withstand multiple fiber breaks, a large number
of resources must be reserved. Hence, in order to reduce the cost, several critical links are
designed to withstand multiple fiber breaks and the remaining links are provided with one-time
fiber break protection.
Route Constraint
Regarding service route on ASON networks, the following factors must be taken into account.
l The number of nodes that a service passes, which is technically termed as hop. On the
condition that other variables remain unchanged, a lesser hop count is preferred.
l Total transmission distance, which is a vital factor that induces time delay. On the condition
that other variables remain unchanged, a shorter distance is preferred.
l Load balance: services select the links that are less loaded to balance the traffic among
links.
In fact, the conditions mentioned above are rarely fulfilled at the same time. In practice, proper
weight should be allocated to each variable to achieve a satisfying overall performance. The
rules that should be obeyed are as follows.
l Service route on metropolitan networks: the least hop count on the basis of load balance
and shortest distance.
l Service route on trunk networks: the shortest distance on the basis of load balance and least
hop.
l As for the backup route, the rule of separating the backup routes from the working routes
must be applied in the first place. It helps protect the working and backup routes from being
affected at the same time in the case of a fiber or a node failure. The rules for separating
are as follows:
– Link disjoint
– Node disjoint
– SRLG disjoint
Commonly, link disjoint is chosen unless otherwise requested. If you are concerned with
node failures, then choose node disjoint. If multiple fibers are within the same channel,
then use SRLG disjoint. Other route constraints, such as double-accessed data services,
need to be allotted to varied routes.
Figure 3-8 shows a service traveling from node A to node B. Different route constraints may
result in different routes.
l If hop count is emphasized, the route can be planned as A-C-B.

l If distance is emphasized, the route can be planned as A-C-G-B.

l If load balance is emphasized, the route can be planned as A-D-E-F-B.
Figure 3-8 Selecting service route for double-accessed data services
15km 15km
35VC4 free 16VC4 free
15km
Shortest path
G
64VC4 free least hop
10km 5km
48VC4 free 28VC4 free
35km
45VC4 free
C 45km B
15km 48VC4 free
48VC4 free 25km
A 60VC4 free
15km 18km
15km 64VC4 free 64VC4 free Less Load
64VC4 free
F
D
E
Different route constraints may result in different routes and the network resource consumption
differs accordingly, sometimes considerably. Thus, you should set the route constraint prior to
the network capacity computation to gain sufficient capacity for the route constraint. Typically,
metropolitan networks emphasize on a minimum hop count and trunk networks emphasize on
the shortest distance.
Network Capacity Computation

In ASON networks, services of different levels occupy different amount of resources. See Table
3-3.
Table 3-3 Resource occupation of different services
Diamond Bandwidth of working Bandwidth of protection Network-wide

routes routes restoration resource
Gold Bandwidth of working Bandwidth of MSP Network-wide

Silver Bandwidth of working None Network-wide

Copper Bandwidth of working None None

routes
Iron Bandwidth of working None None

routes with MS ring or
bandwidth of
unprotected links

Network capacity = total working resources + total protection resources + total restoration
resources + reserved resources
Restoration resources are shared network-wide to support restoration of diamond services, gold
services, and silver services. In addition, for the purpose of subsequent expansion, partial
resources, such as 20% of the resources, are reserved.
ASON network capacity computation involves substantial amount of counting work and needs
specialized software.
The software needs the input of the following parameters:
l Network topology
l Service matrix
l Link distance
The software outputs the following parameters:
l Network capacity, including the number of ports on each node and bandwidth of each link
l Working route, protection or restoration route of each service
At present, regarding service reliability, the capacity is currently computed on the basis of one-
time fiber break protection. In the case of multiple fiber breaks, refer to the following solutions
that are used in the case of two-time fiber breaks.
l Certain amount of network resources must be reserved. Commonly the requested amount
equals 2/N of the overall network capacity. "N" represents the network degree.
l The bandwidth utilization is set to be 1 - 2 / N (max).
l When the planning is complete, verification can be carried out using the software. If there
is an alert, the bandwidth at the bottleneck link should be increased.
Table 3-4 shows the capacity outcome calculated by the software. For node S1, The capacity is
40 VC4 from boards on the tributary side and 6x2.5 Gbit/s optical interfaces on the line side.
Table 3-4 Node capacity output by software
Node Network Link/Service Signal Type Port Type Amo

Layer unt
S1 Service Service E4 E4 G.703 75R 40

layer

layer

layer

Node Network Link/Service Signal Type Port Type Amo

Layer unt

layer

layer
S1 VC-4_1 Facility VC4-16c STM16 1310 SM SH 6
3.2.7 Network Capacity Verification and Reliability Analysis

After the network capacity calculation is complete, you need to verify the network capacity and
analyze reliability.
In other words, you need to perform the simulation of the fiber break based on the capacity that
is currently available. Then, you can evaluate whether the capacity is sufficient and whether the
reliability meets the requirement by analyzing the service restoration situation after the fiber
break.
If the network capacity is insufficient and the reliability fails to meet your requirement, you need
to readjust or recount the network capacity. The fiber break simulation also helps identify the
key link and the bottleneck link. This information can be used for analysis to improve the network
structure. For example, fiber break simulation can determine the two nodes between which
capacity can be increased on the link.
The software can provide the following functions.
l Fault simulation: Simulate the condition in which the designated fiber (s) is (are) broken,
and then output the service restoration information:
– Services affected
– Services downgraded
– Services interrupted
– New service routes.
l Survivability analysis: After the fibers are chosen, use the method of exhaustion to simulate
the condition, and then output the service restoration information:
– Services affected during each break
– Services interrupted during each break.
During the simulation, the amount of counting work is too sizable if all fibers are selected. Thus,
as far as efficiency is concerned, you can first choose the vital links where heavy traffic is added
and dropped for simulation. Once you confirm the service restoration performance of those links,
you can carry out the simulation for other links.

Besides the size of traffic, you can also identify the vital links by means of network cutting.
Using this method, you can divide a network into two separate areas. The links that connect the
two areas are more likely vital ones. See Figure 3-9. After the network is cut, if A-F and B-C
are broken at the same time, the nodes between these two areas cannot communicate. Thus, these
two links are vital links.
Figure 3-9 Identifying vital links by network cutting

A B
F C
E D
If the network reliability meets your requirement, you can output the planning results including
the following factors.
l Network topology
l Network capacity
l Bandwidth of each link
l Port or timeslot amount of each node
l Service route
3.3 ASON Network Planning Technologies

When planning an ASON network, some topologies may be involved, such as the MS and lower
order service.
3.3.1 Planning MS
If any gold service or iron service is configured, you need to plan the MS.
Typically, in planning MS, the following principles should be considered:
l MSP should cover as many nodes as possible, where gold services are configured. With
regard to complex networks, multiple MSP rings can be employed.
l Services should be evenly allocated within the same MSP ring. Avoid severe imbalance of
the use of working bandwidth between different spans.
l If the gold services fail to take up half the link resources, then configure an MS that only
uses a portion of the VC4 channels. The remaining VC4 resources can be used to configure
other services, or for service restoration, to raise the level of resource utilization.

l An MS is configured to save the bandwidth resources on condition that the requirement for
service level is met. In some cases, if configuring diamond services shows a better
performance regarding the use of bandwidth than configuring gold services, configure
diamond services instead of gold services.
3.3.2 Combining ASON Networks with SDH Networks

The ASON network supports the combination with the traditional SDH network.
At present, the optical transport network is mainly traditional SDH networks. Thus, the
combination of ASON and SDH cannot be avoided.
The U2000 can manage the SDH subnets and ASON subnets at the same time. In SDH subnets,
services are configured in a traditional manner, whereas services of the ASON subnets are
configured based on the ASON. The U2000 helps fulfill the end-to-end service configuration
between the subnets. See Figure 3-10.
l If there is a fiber break incident in an SDH network, services are protected based on the
traditional protection mode.
l If there is a fiber break incident in an ASON network, services are protected or restored
based on the ASON protection or restoration mode.
Figure 3-10 Managing ASON network and SDH network at the same time
Network management system
Traditional SDH
ASON
In the crossing area of the two subnets, the following types of protection can be configured to
protect services between subnets.
l 1+1 linear MSP
l 1:1 linear MSP
l SNCP or associated services
SDH and ASON can be combined well, as described in the following sections.
Accessing SDH Network to ASON Network Through a 1:1 or 1+1 MSP

You can access an SDH network to an ASON network with a 1:1 or 1+1 linear MSP. This access
ensures that the entire services are protected from end to end. Services passing the SDH networks

are protected in a traditional way, and services traveling the ASON networks are protected by
ASON protection. See Figure 3-11.
Figure 3-11 Accessing SDH network to ASON network through a 1:1 or 1+1 MSP
SDH
1+1/1:1
ASON
1+1/1:1 :ASON NE
SDH
:Traditionanl NE
Accessing an SDH Ring to an ASON Network

You can access an SDH network to an ASON network with an SDH ring. The ASON network
is responsible for the service grooming and the edge ASON nodes play a dual role, situated at
the ASON network and the SDH network. The edge ASON nodes form the SDH ring in the
SDH network and also join other SDH nodes to constitute a ring network. See Figure 3-12.
Figure 3-12 Hybrid of an ASON network and an SDH ring
ASON
SDH ring
: ASON NE
: Traditionanl NE

Regarding the hybrid of an ASON network and an SDH ring, there are two different means, a
network with one tangent point and a network with two intersecting points. The former is used
in cases where an SDH ring accesses an ASON network by means of multiplex section rings
and the network cannot withstand the failure of the tangent node. In the latter means, an SDH
ring can access an ASON network by means of either MSP or SNCP. If one of the two intersecting
nodes fails, the services cannot be affected.
Accessing Services to SDH and ASON Through Separate Routes

Services are configured in a dual fed and selective receiving manner at the source and sink nodes
and then access the independent SDH and ASON. The service in the ASON is configured to be
a silver service. Though the service in the ASON is protected in the manner in which silver
services are protected, SNCP is achieved from an overall perspective. See Figure 3-13.
Figure 3-13 Accessing services to SDH and ASON through dual fed and selective receiving
Silver service
ASON
Dual fed and

Dual fed and
selective receiving
selective receiving
SDH
:ASON NE
:Traditionanl NE
Accessing SDH to ASON Through Dual Nodes

You can access an SDH network to an ASON network through dual nodes. In this case, services
can also be configured in a dual fed and selective receiving manner. The permanent 1+1
protection can be realized by means of silver tunnel configuration within the ASON network.
See Figure 3-14.

Figure 3-14 Accessing SDH to ASON through dual nodes

Dual fed and
selective receiving
ASON
SDH
:ASON NE
Dual fed and :Traditionanl NE
selective receiving
3.3.3 Planning Lower Order Services

Commonly, in ASON networks, tunnels bear lower order services, to implement the lower order
service protection.
During network planning, if the services are directly added/dropped on ASON nodes, tunnels
are applicable.
Planning End-to-End Tunnels

The lower-order services in the ASON network include:
l Services converged from the SDH layer
l Services dropped and added on the ASON nodes
For the lower order services converged from the SDH layer, they should be converged as much
as possible to the VC4 at the SDH layer and should enter the ASON layer before they are
groomed.
For the lower order services that cannot be converged at the SDH layer, they should be combined
with the lower order services of the ASON nodes when they access the ASON nodes. Then, the
lower order services can be bound in a tunnel, to achieve the grooming in an ASON network.
See Figure 3-15. This type of tunnel is configured end-to-end in the ASON network. The lower
order services cannot be added/dropped on the source, sink and the intermediate nodes

Figure 3-15 Combining lower-order services in ASON tunnels

VC4 tunnel
SDH ring Lower order

services
Converge and adjust

lower order services :ASON NE
Lower order
:Traditionanl NE
services
The tunnels include the following:

l Silver tunnels: simple, bandwidth saving, but poor restoration capability, especially when
there is heavy traffic. A majority of lower order services are voice services, which have a
strict requirement for time delay, so single silver-level tunnel is typically not applicable.
l Diamond tunnels: The switching time for services to recover from the first fiber break
incident is less than 50 ms. In the case of a second fiber break, services are recovered by
means of rerouting, and the restoration time equals the restoration time of the silver-level
tunnels.
l Gold tunnels: The switching time for services to recover from the first fiber break incident
is less than 50 ms. In the case of a second fiber break, services are recovered by means of
rerouting, and the restoration time equals the restoration time of the silver-level tunnels.
l Copper tunnels: no protection ability.
Planning Segment Tunnel

Tunnels are configured from end to end, and lower order services cannot be added or dropped
at the nodes in between. If the lower order services are widely scattered and cannot form one
complete VC4, there may be some VC-12s in a tunnel and evidently many bandwidth resources
are wasted.
To increase bandwidth utilization, the tunnel can be configured section by section. That means
configuring the separate single-hop tunnels for each of the sections between the source nodes
and sink nodes. In this way, the lower-order services can be added and dropped at any of the
passing nodes in the tunnel and the lower order timeslots in each section of the ASON tunnel
are shared. Thus, the higher order timeslot resources can be saved. See Figure 3-16.

Figure 3-16 Segment tunnels

Lower order Lower order Lower order
service service service
Silver tunnel Silver tunnel
Silver tunnel
A segment tunnel can protect services from fiber break incidents. In fact, the protection is a span
protection. The span protection can only protect services in the case of a link failure, but it cannot
withstand a node failure. In application, the span protection should be used in conjunction with
other protection types based on the actual service quality requirement.
For example, for the lower order services with a high requirement, SNCP can be configured at
the points where services enter and exit an ASON network. SNCP enables the services to be
protected from end to end and can be used with the segment tunnel. It is recommended that gold
or silver level be used for the segment tunnel.
3.3.4 Planning the Node ID

The node ID must be allocated during network planning.
Each ASON NE has a unique node ID to represent itself in the ASON network. If two nodes
have the same node ID, ASON cannot function normally. You have to allocate all node IDs
during network planning.
An ASON NE has a control plane address and a management plane address. The control plane
address is the node ID, and the management address is the IP address of the NE.
The format of the node ID and IP address must be the same. Note that the node ID and the IP
address of the NE can neither be the same nor in the same network segment. And they must be
unique in the entire network. The node ID, NE ID and NE IP are independent from each other.
In an actual network, plan the node ID as follows.
l The address of the network segment used with priority: 172.16.0.0-172.31.255.255. In this
network segment, the number of the available IP address is 1048574 (the 172.16.0.0 and
172.31.255.255 are exceptional).
l If the previous network segment address conflicts with the network segment address of the
management plane or the DCN network address, use the following network segment
address with priority: 10.0.0.0-10.255.255.255. In this network segment, the number of the
available IP address is 16777214 (the 10.0.0.0 and 10.255.255.255 are exceptional).
l If the previous network segment address is still conflicting, use the following network
segment address: 192.168.0.0-192.168.255.255. In this network segment, the number of
the available IP address is 65534 (the 192.168.0.0 and 192.168.255.255 are exceptional).
l If all the previous network segment address cannot meet the requirements of users, plan
the node ID in other schemes and contact Huawei for further discussion.

3.3.5 Planning a Large-Scale ASON Network

A large-scale ASON network should be divided into several control domains.
The commercial ASON version currently released by Huawei supports only a single ASON
domain. The number of nodes of the single ASON domain must be restricted and should be
under 100. If the number of nodes exceeds 100, you can divide the ASON network into multiple
independent control domains and connect them through the traditional SDH.
Generally, if two domains are connected through the traditional SDH, the following three
formations are available.
l Dual-chain construction: The domain-crossing services are configured to be SNCP. See

Figure 3-17. Channel D4-D9 of the DCC of the interconnected fibers should be shut down.
l MS ring construction: See Figure 3-18. Channel D4-D9 of the DCC of the interconnected
fibers should be shut down.
l 1:1 or 1+1 linear MS construction: See Figure 3-19.
Figure 3-17 Dual domain interconnection: dual-chain construction

Associated Associated
silver services silver services
SNCP SNCP
ASON ASON
Traditional services
Figure 3-18 Dual domain interconnection: MS ring construction
MSP ring
ASON ASON
Traditional MSP
ASON service service ASON service

Figure 3-19 Dual domain interconnection: linear MS construction
Traditional MSP
service
ASON ASON
Linear MS
ASON service
ASON service

ASON User Guide 4 Commissioning the OTN ASON
4 Commissioning the OTN ASON
About This Chapter
This chapter describes the ASON software commissioning by using the U2000.
4.1 Preparations
This section describes the preparations before the ASON commissioning.
4.2 Configuring an ASON NE
This section describes the method of and procedure for configuring an ASON NE.
4.3 Managing the ASON Protocol
After the ASON software is enabled, the default ASON protocols are configured for the NE.
After the ASON topology is created, you can set again the ASON protocols you need to facilitate
the management of ASON link resources and ASON services.
4.4 Configuring the Link Parameter
A reasonable way of link parameter management is required to make the most of the network
resources and to improve the network efficiency.
4.5 Commissioning Preset Restoration Trails
If the working trail of an ASON service configured with a preset restoration trail experiences a
fiber break, the ASON service will be switched to the preset restoration trail with precedence.
To ensure that the preset restoration trial functions properly, commission optical power for the
preset restoration trail.
4.6 Testing Resource and Topology Auto-Discovery
The auto-discovery of topologies and resources is a major function of an ASON network and is
the foundation of network routing computation. The ASON software supports the auto-discovery
of ASON NEs, TE links, control links and inter-NE fibers. The internal fibers of an NE, however,
need be manually created.
4.7 Testing ASON Features of a Service
ASON features ensure normal running of an ASON network. After an ASON NE is configured,
you should test and verify the related ASON features according to the project situations.
4.8 Testing the Rerouting Capability of ASON Services

The ASON network can provide multiple ASON services. Each ASON service has different
protection and restoration abilities. All ASON services supported by the network must be tested
during commissioning.

4.1 Preparations
4.1.1 Preparing Engineering Documents

Before ASON commissioning, the related engineering documents must be prepared.
An engineering document contains the detailed information about a specific engineering
deployment. An engineering document contains the following items:
l Service route report, which identifies various possible service routes and trails for guiding
deployment commissioning
l Network diagram, including the slot layout, fiber connection view, basic topological view,
wavelength distribution view, table of the data about the entire network, and table of optical
attenuators.
l Basic topology diagram, which depicts the topology structure of the network, equipment
type of each site, types and number of NEs, NE IDs, Node IDs, and IP addresses of the
external network interfaces.
l Networking diagram of the entire network, which provides planning of network topologies
l Table of the data about the entire network and table of fiber connection relations
l Slot layout diagram of the cabinet, which provides the slot layout information, such as the
subrack position in the cabinet, slot layout in the subrack, and name and ID of the NE
4.1.2 Preparing Software Versions

Before ASON commissioning, the software of mapping versions must be prepared.
l The NE software version must support the ASON features. Contact Huawei engineers to
determine whether the current NE software version supports the ASON features.
l The U2000 version must support the ASON features.
l The ASON features are controlled by the license on the U2000. The ASON features can
be enabled for only users who apply for and purchase this license or obtain a special
permission from Huawei.
4.1.3 Preparing Dual SCC Boards

During deployment of the equipment with the ASON features, dual SCC boards must be
configured, and thus you should determine whether the current equipment configuration is
correct.
If only one SCC board is configured, contact Huawei engineers for handling.
NOTE
The slave subrack does not need to be configured with dual SCC boards. Only the master subrack needs
to be configured with dual SCC boards.
4.1.4 Preparing Tools and Meters

The tools and meters must be prepared before the commissioning of the ASON.

The following tools and meters are required:

l U2000
l Optical power meter
l Optical attenuator, including fixed attenuator and variable attenuator
l Flange, fiber cleaning tissue
l Fiber jumper
l Signal analyzers, for example, SDH analyzer, SmartBits analyzer and optical spectrum
analyzer
4.1.5 Checking ASON Commissioning Conditions

Before ASON commissioning, check and determine the equipment conditions and make sure
that the equipment meets the conditions for ASON commissioning.
Before ASON commissioning, hardware installation on the entire network and system
commissioning in the traditional WDM must be complete (test for specifications of boards must
be complete). For details on the method of commissioning the equipment in the traditional
WDM, see the following documents:
l OptiX OSN 8800 Intelligent Optical Transport Platform Commissioning Guide

NOTE
Before commissioning of the equipment in the traditional WDM, upgrade the software to the version that
supports the ASON features.
NOTE
Due to the rerouting feature of the ASON, you need to commission the optical power of each planned trail
on the ASON network, including the working trail, protection trail, and revertive trail.
Before ASON commissioning, check and determine the equipment conditions as follows:
l Make sure that the board is normal.

l Make sure that the physical board is online.
l Make sure that the optical power is commissioned.
l Make sure that the physical and logical fiber connections are correct.
NOTE
Correct physical fiber connections ensure availability of actual links, and correct logical fiber
connections ensure availability of ASON services.
l Make sure that the logical boards for all boards are created.
NOTE
If the logical slots are not created or the created logical slots are different from the physical slots,
data links cannot be generated.
l During system commissioning, certain temporary services may be configured or other
settings are performed on the NE. Remove these unnecessary configurations before the
ASON features are enabled.
4.1.6 Automatic Commissioning Process and Commissioning Items

This section describes the automatic commissioning process and commissioning items after an
ASON network is deployed.

NOTE
For the scenarios of the automatic commissioning, see Network Models and Application Scenarios in the
Commissioning Guide.
Prepare for the automatic commissioning. For the preparation requirements, see Preparing for New
Deployment Commissioning in the Commissioning Guide.
Table 4-1 and Table 4-2 list the recommended commissioning procedures and items for the
automatic commissioning of an ASON network.
Table 4-1 Commissioning procedures and items for the automatic commissioning of an Optical-
Layer ASON network
Commissioning Procedure Item
Commissioning system optical Configuring NE and Network

power
Uploading Commissioning Data
Setting Commissioning Parameters for a Subnet
Creating a WDM Link
Presetting Insertion Loss for OPA During Deploymentc
Recording the Optical Power Before Commissioning
Commissioning the Optical Power
Viewing the Commissioning Result
Configuring an ASON NE Setting the Node ID
Checking Consistency Between Logical Boards and

Physical Boards
Setting the DCC Bytes
Enabling the ASON Feature
Uploading NE Configuration Data
Configuring a Station with Separate Optical and

Electrical NEs
Creating Domains for an ASON Network
Setting the Primary NE or Secondary NE
Synchronizing ASON NEs
Synchronizing Control Links Networkwide
Synchronizing TE Links
Automatically Creating Fibers Between Sites
Creating Out-Fiber Control Channels (Optional)

(Optional) Managing the Configuring the LMP Protocol

ASON protocol
Configuring the OSPF Protocol
Encrypting the OSPF Protocol
Encrypting the RSVP Protocol
Managing link resources Creating an SRLG
Configuring the Link Distance
Setting Resource Reservation (Optional)
Setting Link Cost (Optional)
Commissioning ASON Configuring Monitor of ASON Reroutes

services
Migrating a Traditional WDM Trail to a WDM ASON
Traila
Setting Preset Restoration Trailb
Commissioning Preset Restoration Trails
Testing resource and topology Testing the Auto-Discovery of ASON NEs

auto-discovery
Testing the Auto-Discovery of Control Links
Testing the Auto-Discovery of TE Links
Testing ASON features of a Testing Creation and Deletion of ASON Services

service
Testing Disabling of the Rerouting Function of ASON
Services
Testing Query and Change of ASON Services
Testing the Rerouting Lockout Function of ASON

Services
Testing Trail Pre-computation of ASON Services
Testing Restoration of ASON Services to the Preset Trail
Testing Modification and Adjustment of ASON Service

Trails
Testing ASON Service Restoration on the Entire

Network
Testing Route Computation Based on Constraints
Testing Rerouting of Associated Services

Testing Conversion Between ASON Services and

Traditional Services
Testing the Conversion Between ASON Services with

Different SLAs
Testing reroutes of ASON Testing an Electrical-Layer Diamond WDM ASON

services ODUk Trail
Testing an Optical-Layer Silver WDM ASON OCh Trail
Testing an Electrical-Layer Silver WDM ASON ODUk

Trail
NOTE
a: Upgrade a service that is created in traditional mode to an ASON service on the NMS.
b: Configure the preset restoration trail for a service based on the planning result.
c: Computes the insertion loss between an OTU board and an OA board and that between OA boards. Then, the
insertion loss is applied to an NE to facilitate optical power adjustment.
Table 4-2 Commissioning procedures and items for the automatic commissioning of an
Electrical-Layer ASON network
Commissioning system optical Configuring NE and Network

power
Uploading Commissioning Data
Setting Commissioning Parameters for a Subnet
Creating a WDM Link
Presetting Insertion Loss for OPA During Deploymentc
Recording the Optical Power Before Commissioning
Commissioning the Optical Power
Configuring an ASON NE Setting the Node ID
Checking Consistency Between Logical Boards and

Physical Boards
Setting the DCC Bytes
Enabling the ASON Feature
Uploading NE Configuration Data

Configuring a Station with Separate Optical and

Electrical NEs
Creating Domains for an ASON Network
Setting the Primary NE or Secondary NE
Synchronizing ASON NEs
Synchronizing Control Links Networkwide
Synchronizing TE Links
Automatically Creating Fibers Between Sites
Creating Out-Fiber Control Channels (Optional)
(Optional) Managing the Configuring the LMP Protocol

ASON protocol
Configuring the OSPF Protocol
Encrypting the OSPF Protocol
Encrypting the RSVP Protocol
Managing link resources Creating an SRLG
Configuring the Link Distance
Setting Resource Reservation (Optional)
Setting Link Cost (Optional)
Commissioning ASON Creating ASON Servicesa

services
Setting Preset Restoration Trailb
Testing resource and topology Testing the Auto-Discovery of ASON NEs

auto-discovery
Testing the Auto-Discovery of Control Links
Testing the Auto-Discovery of TE Links
Testing ASON features of a Testing Creation and Deletion of ASON Services

service
Testing Disabling of the Rerouting Function of ASON
Services
Testing Query and Change of ASON Services
Testing the Rerouting Lockout Function of ASON

Services
Testing Trail Pre-computation of ASON Services
Testing Restoration of ASON Services to the Preset Trail

Testing Modification and Adjustment of ASON Service

Trails
Testing ASON Service Restoration on the Entire

Network
Testing Route Computation Based on Constraints
Testing Rerouting of Associated Services
Testing Conversion Between ASON Services and

Traditional Services
Testing the Conversion Between ASON Services with

Different SLAs
Testing reroutes of ASON Testing an Electrical-Layer Diamond WDM ASON

services ODUk Trail
Testing an Optical-Layer Silver WDM ASON OCh Trail
Testing an Electrical-Layer Silver WDM ASON ODUk

Trail
NOTE
a: Configure electrical layer ASON services based on the planning result.

b: Configure the preset restoration trail for a service based on the planning result.
c: Computes the insertion loss between an OTU board and an OA board and that between OA boards. Then, the
insertion loss is applied to an NE to facilitate optical power adjustment.
4.2 Configuring an ASON NE

This section describes the method of and procedure for configuring an ASON NE.
4.2.1 Setting the Node ID

The node ID, NE ID and IP address of the NE are independent from each other. In an ASON
network, each ASON NE is assigned with a unique node ID within a network. The node ID must
be specified during the network planning.
Prerequisite
l You must be an NM user with "NE operator" authority or higher.
l No ASON services exist on the NE.
Background Information
The node ID must meet the following requirements:

l Node IDs cannot repeat each other in the same ASON domain.
l The node ID of an NE cannot be in the same network segment as the IP address of the NE.
l The node ID, NE ID and IP address of the NE are independent from each other.
l The format of a node ID is the same as that of an IP address. The node ID cannot be 0.0.0.0,
1.2.3.4 or 255.255.255.255. For details on the range of the node ID, refer to Planning the
Node ID.
l The node ID must be set before an ASON feature is enabled. If the node ID is set after an
ASON feature is enabled, a warm reset is performed automatically on the NE.
CAUTION
When a delivered network is running, do not change the node ID. To change the node ID, contact
NOTE
The IP addresses include primary IP address and secondary IP address.

Secondary IP addresses are used to enable communication between the optical and electrical NEs. The
secondary IP address of the optical NE must be in the same network segment as that of the electrical NE.
A primary IP address is configured for the traditional network level. The primary and secondary IP
addresses and node IDs must belong to different network segments and must be unique networkwide.
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > ASON Feature Management from the
Function Tree. Click the Node ID Management tab.
Step 2 Click Query to view the current node ID of the NE.
Step 3 Double-click the Node ID field to enter a node ID for the NE.
Step 4 Click Apply. After you confirm the operation twice, a prompt appears telling you that the
operation was successful.
NOTE
You can also set the NE node ID in ASON Topology Management.
----End
4.2.2 Checking Consistency Between Logical Boards and Physical

Boards
When the types of the logical board and physical board are inconsistent, the board cannot work
normally. As a result, the user services are affected. Hence, check the consistency between the
logical board and physical board before service commissioning.

Prerequisite
l The logical board must be created and the physical board must be installed.
When the type of the logical board is inconsistent with the type of the physical board, the board
reports the WRG_BD_TYPE alarm. The alarm, however, does not necessarily mean that the
type inconsistency between the logical board and physical board. The alarm may also be
generated when the board software is inconsistent with the hardware or when the board is faulty.
Procedure
Step 1 Click the major alarm indicator (orange) on the right upper part of the U2000 interface
to browse the current major alarms in the entire network.
NOTE
The number inside the indicator indicates the number of the current major alarms in the entire network.
When the indicator is circled with a line, as shown in , it indicates that there are major alarms
to be confirmed.
Step 2 Check whether the WRG_BD_TYPE alarm exists in the alarm list. If the WRG_BD_TYPE
alarm is not found, it indicates that the type of the logical board is consistent with the type of
the physical board. If the WRG_BD_TYPE alarm is found, it indicates that the type of the logical
board may be inconsistent with the type of the physical board. Then, perform the following steps.
Step 3 Double-click the ONE icon to display the NE panel on the Main Topology. Select the NE where
the WRG_BD_TYPE alarm is reported from the NE list on the left side. Check whether the type
of the logical board is consistent with the type of the physical board. If the type of the logical
board is inconsistent with the type of the physical board, check whether the logical board or the
physical board is configured incorrectly according to the configuration requirements.
l If the logical board is configured incorrectly, reconfigure the logical board on the U2000.
l If the physical board is of an incorrect type, insert a physical board of the correct type.
Step 4 If the alarm persists when the logical board and the physical board are of the same type, check
whether the board software version matches the hardware version. If the board software version
mismatches the hardware version, reload the board software or use a board with the correct
software version to replace the board.
Step 5 If the alarm persists when the board software version matches the hardware version, it indicates
that the board may be faulty. Replace the board.
----End
4.2.3 Setting the DCC Bytes

The control channel of the ASON optical path uses the D4-D12 bytes or OTN overhead bytes
to transmit messages. If the DCC bytes are not enabled, you must enable the DCC bytes on the
U2000.
Prerequisite
l You must be an NM user with "NE and network administrator" authority or higher.

Context
In the case of an ASON network, ensure that the required DCC channels of the stations with the
enabled ASON features are enabled.
In normal situations:
l The ASON features of the stations (including OLA stations) where ASON services traverse
must be enabled in the case of optical-layer ASON.
l The ASON features of an OLA station or optical NE do not need to be enabled in the case
of electrical-layer ASON.
Procedure
Step 1 Select the NE from the NE Explorer. Choose Communication > DCC Management from the
Function Tree.
Step 2 Click Query in DCC Rate Configuration to check whether the enabling status of each port on
the existing NE is set.
Step 3 In the case of the port whose enabling status needs to be changed, double-click Enabled/
Disabled, and then select Enabled or Disabled from the drop-down list. Then, click Apply to
make the setting take effect.
NOTE
l The optical-layer ASON services use the D4-D12 bytes to transmit messages, and the electrical-layer
ASON services use the OTN overhead bytes to transmit messages.
l On the DCC Rate Configuration tab page, set Bind of the port to determine whether to use the GCC
bytes to transmit ASON messages or management information. If Bind is set to Disabled, the GCC
bytes are used to transmit ASON messages.
l In the case of a pure optical-layer ASON network, set the enabling status of the electrical-layer overhead
bytes to Disabled. In this manner, the working efficiency of the NE is enhanced.
l It is recommended to set the usage status of ASON overhead bytes to Disabled for tributary boards
when electrical-layer ASON features are enabled.
----End

4.2.4 Enabling the ASON Feature

The NE obtains the ASON feature after this feature is enabled. The ASON feature is disabled
by default during delivery.
Prerequisite
l The node ID must be set.
l The NE must be in the running state.
l The NE must be created on the U2000 and the NE data must be already uploaded.
l A unique node ID is allocated to each ASON NE to identify the NE in the ASON network.
In the same ASON network, node IDs cannot be duplicate or in the same network segment
as the IP address of the corresponding NE. The format of a node ID is the same as that of
an IP address. The node ID cannot be 0.0.0.0, 1.2.3.4 or 255.255.255.255. Properly set the
NE node ID before you enable the ASON feature of the NE.
l After you enable the ASON feature, synchronize the NE data to keep the consistency of
data between the U2000 and the NE. Refer to 5.1.7 Uploading NE Configuration Data
for the process.
l You can disable the ASON feature of an ASON NE according to the project requirement.
After you disable the ASON feature, the NE is possessed of only traditional NE features.
NOTE
To disable the ASON feature, the NE must meet the following requirements:
l The NE must be in the running state and does not have any ASON cross-connection or ASON
service residual
l The fiber between the local NE and the adjacent node must not carry ASON services.
l The ASON feature has been enabled.
l The TE link information is correct and no exception occurs.
l The network is stable.
CAUTION
In the case of the ASON NEs of GCP versions earlier than V200R001, disabling the ASON
feature causes a reset operation on the specific NE. Therefore, before disabling the ASON
feature, ensure that all services have been migrated to other optimized trails; in the case of
V200R001 or later versions, disabling the ASON feature does not cause a reset operation
on the specific NE.
Procedure
Function Tree.
Step 2 Click Query to view the current enabling status of the ASON feature.

Step 3 Set ASON Feature to Enabled.
NOTE
Set the ASON Feature to Disabled to disable the ASON feature.
NOTE
After you disable the ASON feature, synchronize the NE data to keep the consistency of data between the
U2000 and the NE. For related operations, see 5.1.7 Uploading NE Configuration Data.
Enter the ASON Feature Management interface again. If Running is displayed in ASON
Software Running Status, it indicates that the ASON software is running normally.
----End
4.2.5 Uploading NE Configuration Data

During equipment commissioning, NE data exists on the U2000. After the ASON feature of the
NE is enabled, the NE cannot be initialized and data cannot be downloaded to the NE. After the
ASON feature of the ASON NE is enabled or disabled, data of the NE need be uploaded to the
U2000 to ensure that the data on the U2000 is consistent with that on the NE.
Prerequisite
l The NE must be created successfully.The NE must be in running state.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management from the Main Menu.
Step 2 Select one or more NEs in the lower-left pane, and click .
Step 3 Select one or more NEs in the Configuration Data Management List, and click Upload.
Step 4 In the Confirm dialog box, click OK to start the upload.
Step 5 In the Operation Result dialog box, click Close.
----End
4.2.6 Configuring a Station with Separate Optical and Electrical NEs

If the station consists of separate optical and electrical NEs, related configurations must be made
on the U2000 to ensure proper communication between the optical and electrical NEs and
successful creation of TE links.

Prerequisite
l You must be an NMS user with "NE and network administrator" authority or higher.
l Cables between optical NEs and electrical NEs are correctly connected.
l Embedded control channels (ECCs) between optical NEs and electrical NEs are configured
properly and communication between NEs is proper.
Context
For details on how to divide an NE into optical and electrical NEs, see ASON Features Based
on Separate Optical and Electrical NEs.
Procedure
Step 1 Configure secondary IP addresses.
1. In the NE Explorer, select the optical NE and choose Function Tree > ASON > OSPF
Protocol Management > OSPF IP Address from the Function Tree. Configure a
secondary IP address for the optical NE. Then, repeat this step to configure a secondary IP
address for the electrical NE.
NOTE
Secondary IP addresses are used to enable communication between the optical and electrical NEs.
The secondary IP address of the optical NE must be in the same network segment as that of the
electrical NE.
A primary IP address is configured for the traditional network level. The primary and secondary IP
addresses and node IDs must belong to different network segments and must be unique networkwide.
2. In the NE Explorer, click the required optical NE and choose Function Tree > ASON >
Advanced Maintenance > OSPF Protocol Status from the Function Tree. Then, click
Query. Ensure that the OSPF state of the newly-created ETH control port is Enabled. If
the OSPF state is not Enabled, enable the OSPF protocol for ETH ports.
3. Choose Configuration > WDM ASON > Control Link Management from the Main
Menu. Click Synchronize. In the Control Link list, the newly-created ETH control link
is displayed. Make sure that Status of this link is Up.
Step 2 Configure the optical and electrical NEs as the opposite NEs of each other and create virtual TE
links.

1. Make sure that bidirectional fiber connections are created between the optical and electrical
NEs on the U2000.
NOTE
In the case of an optical NE, the fiber connection port for connecting to an electrical NE is usually
the port on the multiplexer/demultiplexer board for wavelength adding or dropping. In the case of
an electrical NE, the fiber connection port for connecting to an optical NE is usually the line-side
port on the OTU board.
2. In the NE Explorer, click the optical NE and choose Function Tree > ASON > Advanced
Maintenance > LMP Protocol Status from the Function Tree. Set the LMP state of the
downlink D40 board connecting to the electrical NE to Disabled.
3. In the NE Explorer, click the electrical NE and choose Function Tree > ASON >
Advanced Maintenance > LMP Protocol Status from the Function Tree. Set the LMP
state of the uplink OTU board connecting to the optical NE to Disabled.
4. By using the virtual TE link configuration function of the NMS, configure the multiplexer/
demultiplexer board and OTU board at the NE edges as the opposite boards of each other.
For the detailed procedure, see Creating a Virtual TE Link.
NOTE
l When creating a virtual TE link, set its source as the downstream port on the demultiplexer board and
sink as the WDM-side port on the OTU board.
l When separate optical and electrical NEs are configured, parameters such as link distance, bandwidth,
count of hops, and line loss do not affect virtual TE links between the optical and electrical NEs.
l Optical and electrical NEs communicate with each other using out-band channels. The links between
them cannot be identified in the control topology.
l To identify virtual TE links between the optical and electrical NEs, users need to first find the links
of which Link Signal Type is OMS/OTS in the WDM TE Link Management window. Then they
can identify the virtual TE links between optical and electrical NEs by the source and sink NE names
and board types. As shown in the figure for step d, the blue TE link is a virtual TE link between the
OTU board on electrical NE163 and the M40 board on optical NE153.
----End

4.2.7 Creating Domains for an ASON Network

The U2000 manages an ASON network based on ASON domains. Usually, ASON domains are
automatically created. If for some reason, there are NEs that fail to be synchronized to the ASON
domain during the NE upload, you can create an ASON domain and assign the ASON NEs that
belong to the same ASON network to the ASON domain.
Prerequisite
l The ASON NE must be configured and does not belong to any domain.
l An ASON domain is an ASON network composed of interconnected ASON NEs.
l The first ASON NE created on the U2000 is automatically assigned to the default domain.
Procedure
Step 1 Choose Configuration > WDM ASON > ASON Topology Management from the Main Menu.
Step 2 ASON NEs that do not belong to any domain are displayed under root of the Object Tree. Right-
click an NE and choose Create Domain.
Step 3 In the Domain Attributes dialog box, enter the Current Name and select the Primary NE.
Step 4 Click OK. The domain is successfully created.

Step 5 Optional: In root of the Object Tree, right-click the created ASON domain and choose
Rename. In the displayed Domain Attributes dialog box, enter New Name, and then click
OK. In this case, the domain successfully modified.
NOTE
If an ASON domain exists by default and the ASON NEs are in the default ASON domain, you should just
modify the name of the ASON domain without creating a new domain.
----End
4.2.8 Setting the Primary NE or Secondary NE

In an ASON network, each ASON NE is capable of obtaining the networkwide topology
information. The primary NE is the ASON NE that represents the ASON to communicate with

the U2000. It obtains the information of the ASON control plane and reports ASON events to
the U2000. To improve the reliability, another NE can be set as the standby of the primary NE.
If the primary NE fails, the secondary NE takes over to communicate with the U2000. Usually,
you can select the GNE as the primary NE or as the secondary NE to avoid waste of the ECC
bandwidth.
Prerequisite
l An ASON NE must be created and its data must be uploaded to the U2000.
The U2000 only needs to communicate with one NE in an ASON network. This NE is called
the communication NE. It is the NE that represents the ASON network to communicate with
the U2000. Usually, the communication NE is the primary NE. When the primary NE fails, the
secondary NE becomes the communication NE. If both the primary and secondary NEs fail, the
system automatically selects an ASON NE as the communication NE. You can set only one
primary NE and one secondary NE in an ASON domain.
Procedure
Step 1 Choose Configuration > WDM ASON > ASON Topology Management. Click the
Configured 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 and set it to Primary in the Node Type column.
Step 4 Optional: Select an NE and set it to Secondary in the Node Type column.
Step 5 Click Apply to apply the settings.
----End
4.2.9 Synchronizing ASON NEs

By communicating with the primary NE, the U2000 is kept synchronous with an ASON network
and automatically discovers other ASON NEs in the network.
Prerequisite
l The primary NE must exist.
l 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.

l If the node ID of an NE is modified manually, you need to re-synchronize the ASON

network topology on the U2000.
Procedure
Step 1 Choose Configuration > WDM ASON > ASON Topology Management from the Main Menu,
and click the Configured NE tab.
Step 3 Click Synchronize NE. The U2000 searches for the NEs in the ASON domain.
If an ASON NE that is unconfigured on U2000 is detected, add it to the Unconfigured NE tab.
Step 4 Optional: In the Unconfigured NE tab, view the NEs that are not created. You can create those
NEs according to actual requirements on the U2000.
Step 5 Upload the NE configuration data in the Main Topology according to the information of the
NEs to be configured.
After the uploading is completed, the original NE to be configured is automatically added to the
ASON domain and is displayed on the corresponding list.
----End
4.2.10 Synchronizing Control Links Networkwide

By synchronizing the control links, the control link data on the U2000 is kept consistent with
that on the NEs of the ASON network.
Prerequisite
l The ASON network must be running properly.
Procedure
Step 1 Choose Configuration > WDM ASON > Control Link Management from the Main Menu.
Step 2 In the Filter dialog box displayed, choose Domain and Source/Sink NE of the control links
that need to be synchronized, and then click Filter.

Step 3 Click Synchronize. In the Synchronize dialog box displayed, choose Domain.
Step 4 Click Synchronize.
NOTE
After the synchronization is complete, all the information about the control links is displayed in the list.
----End
4.2.11 Synchronizing TE Links

You can synchronize the TE links. The U2000 queries link resources in the network by the
primary NE to keep the TE link data on the U2000 consistent with the ASON data.
Prerequisite
l The ASON network is running normally.
In current ASON software versions, one TE link contains only one component link. In this sense,
to synchronize a TE link is the same as to synchronize a component link.
Procedure
Step 1 Choose Configuration > WDM ASON > TE Link Management from the Main Menu.
Step 2 In the Filter dialog box displayed, choose Domain, Payload Type, Line Signal Type, and
Source/Sink NE of the TE links that need to be synchronized, and then click Filter.
Step 3 Click Synchronize. In the Synchronize dialog box displayed, choose Domain and Payload
Type.


NOTE
After the synchronization is complete, all the information about the TE links is displayed in the list.
----End
4.2.12 Automatically Creating Fibers Between Sites

ASON supports the capability to automatically create fibers between sites by using TE links.
Prerequisite
l The NE software must contain ASON features, which must be successfully enabled.
l The physical fiber connections must be correct.
l The communication between NEs must be available.
Context
TE links involve the links describing the connection relation between two NEs. In an ASON
domain, the optical fiber connections between ASON NEs can be automatically created through
these TE links.
TE links are discovered through internal logical fiber connections on an NE, and thus you must
correctly create the fibers before system commissioning. You can create the fiber connections
between NEs only through the automatic fiber creation function.
If the fibers between NEs are created on the U2000, you can check whether the logical fiber
connections are created properly by automatically creating the fibers between the two NEs
through a TE link. If an error occurs, an alarm is reported.
Test Standard
Fibers can be automatically created by using TE links on the U2000. In the Main Topology of
the U2000, you can view the fibers just created.

Procedure
Step 1 In the Main Menu, choose Configuration > WDM ASON > TE Link Management.
Step 2 In the displayed Filter window, select Domain, Link Signal Type, Payload Type, and Source/
Sink NE for the required TE links, and then click Filter. After that, the two TE links between
the source and sink NEs are displayed in the window.
Step 3 Select the two TE links and click Maintenance. Choose Create Fiber, and the Operation
Result dialog box is displayed, indicating that the operation is successful. At this point, the fibers
just created are displayed in the Main Topology.
----End
4.2.13 Creating Out-Fiber Control Channels

The out-fiber control channel implements interconnection between two ASON domains. You
can use an Ethernet cable to connect two edge NEs of two ASON domains, and then manually
create an out-fiber control channel on the U2000. In this way, the communication between the
two ASON domains is realized at the control plane.
Prerequisite
Service Requirements
You can create an out-fiber control channel as shown in Figure 4-1. In this example, NE3 in the
ASON001 domain and NE6 in the ASON002 domain are connected by an Ethernet line. NE3
and NE6 are connected to NE9 through fibers.
Figure 4-1 Creating out-fiber control channels

NE1 NE4 NE5 NE8
NE2 NE3 NE6 NE7

ASON001 NE9 ASON002
: ASON NE
: Traditional NE
: Fiber
: Ethernet link

NOTE
You need to create an out-fiber control channel on the NE that connects the two ASON domains.
Procedure
Step 1 Configure secondary IP addresses.
1. Two NEs in two ASON domains are connected to each other to achieve the connection of
the two ASON domains. In the NE Explorer, select one of the NEs and choose Function
Tree > ASON > OSPF Protocol Management > OSPF IP Address from the Function
Tree. Configure a secondary IP address for the NE. Then, repeat this step to configure a
secondary IP address for the other NE.
NOTE
Secondary IP addresses are used to enable communication between the NEs. The secondary IP
address of the NE must be in the same network segment as that of the other NE.
A primary IP address is configured for the traditional network level. The secondary IP address cannot
be the same as the primary IP address or Node ID.
2. In the NE Explorer, click the required NE and choose Function Tree > ASON > Advanced
Maintenance > OSPF Protocol Status from the Function Tree. Then, click Query. Make
sure that the OSPF state of the newly-created ETH control port is Enabled.
3. Choose Configuration > WDM ASON > Control Link Management from the Main
Menu. Click Synchronize. In the Control Link list, the newly-created ETH control link
is displayed. Make sure that Status of this link is Up.
Step 2 Set attributes of a control channel.
1. In the NE Explorer, select an NE and choose ASON > Link Management Protocol from
the Function Tree.
2. Click the LMP Control Channel tab. Click Query to query control channels of the link
management protocol from the NE.
3. Click New and the Create Control Channel dialog box is displayed. Enter a value in the
Remote Address and Next Hop Address field respectively.
NOTE
A remote address refers to the secondary IP address of the opposite NE.

A next hop address depends on actual network configurations.
l As shown in Figure 4-1, if only one Ethernet link exists between the source and the sink, the two
addresses are consistent.
l If a hub exists on the Ethernet link between the source and the sink, the two addresses are
consistent.
l If a switch exists on the Ethernet link between the source and the sink, the remote address is the
secondary IP address of the sink NE and the next hop address is the IP address of the switch.
l If a router exists on the Ethernet link between the source and the sink, the remote address is the
secondary IP address of the sink NE and the next hop address is the IP address of the router.
l If a local area network (LAN) exists on the Ethernet link between the source and the sink, the
remote address is the secondary IP address of the sink NE and the next hop address is the IP
address of the LAN that connects to the source NE.
For example, if NE3 is the source, the remote address and the next hop address are the
secondary IP of NE6.
4. Click Apply for the settings to take effect.
----End

4.2.14 Creating a Virtual TE Link

An ASON topology is based on TE links. Generally, TE links are automatically discovered and
updated by ASON. In some scenarios, TE links cannot be automatically discovered. When this
occurs, you need to manually configure opposite ends for those TE links. In other words, you
need to create virtual TE links. Create virtual TE links in the following scenarios: When optical
NEs and electrical NEs are split at a station, you need to create virtual TE links between separated
optical NEs and electrical NEs; when an ultra-long span uses an ESC instead of an OSC (specific
to optical-layer ASON services), you need to create virtual TE links between NEs at the two
ends of the span; when ASON links pass through traditional NEs, you need to create virtual TE
links between the traditional NEs and ASON NEs.
Prerequisite
l You must be an NMS user with "NE operator" authority or higher.
l There must be at least two configured ASON NEs.
l No alarm exists on the ports that you use to create a TE link.
l Set the LMP protocol state of the ports on the two ends between which a virtual TE link is
created to Disable. For details, see Configuring the LMP Protocol.
Procedure
Step 3 Click Maintenance and choose Create Virtual TE Link. The Create Virtual TE Link dialog
box is displayed.
Step 4 Enter the attributes of the TE link.
Example configurations for creating a virtual TE link between separated optical NEs and
electrical NEs:
l Extended Type: Optical-Layer ASON Trail Creation
l Signal Type: OCh
l Source NE: NE3; Source Port:D40-2(D01)
l Sink NE: NE3; Sink Port: ND2-1(IN1/OUT1)
Example configurations for creating a virtual TE link when an ultra-long span uses an ESC
instead of OSC:
l Signal Type: OCh
l Source NE: NE3; Source Port: FIU-1(IN/OUT)
l Sink NE: NE4; Sink Port: FIU-1(IN/OUT)
Example configurations for creating a virtual TE link to create electrical-layer ASON services
when ASON links pass through traditional NEs:
l Extended Type: Electrical-Layer ASON Trail Creation
l Signal Type: ODU2
l Source NE: NE3; Source Port: ND2-1(IN1/OUT1)
l Sink NE: NE4; Sink Port: ND2-1(IN1/OUT1)

Example configurations for creating a virtual TE link to create optical-layer ASON services
when ASON links pass through traditional NEs:
l Signal Type: OCh
l Source NE: NE3; Source Port: FIU-1(IN/OUT)
l Sink NE: NE4; Sink Port: FIU-1(IN/OUT)
NOTE
l The extended type has two options: ASON Trail Creation or Fault Detection Only.
l When the TE link is used to create a service, select ASON Trail Creation.
l Automatic verification is not performed on virtual TE links. You need to manually check the
connectivity of the link.
Step 5 Click OK.
----End

Precautions
CAUTION
l Usually, you do not need to modify the protocol configurations.
l You can modify the protocol configurations when the ASON networking is a special one, or
when a higher security is required.
4.3.1 Configuring the LMP Protocol

Generally, the LMP protocol should not be disabled. In certain cases, however, you need to
disable the protocol to release idle resources, and thus rationally use resources.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The LMP protocol for corresponding optical paths must be disabled in the following application
scenarios:
l Optical path between ASON NEs but not used by ASON services

NOTE
The LMP protocol for control channels, which is not used for ASON features and always fails the
negotiation, can be disabled, so that resources can be released for other control channels that require
negotiation.
Make sure that at least one control channel is retained between two ASON NEs. Two control channels are
recommended for redundancy backup.
On the network where only optical-layer ASON is deployed, disable the LMP protocol (the type of link
signals is ODUk or OTUk) of the control channels related to electrical-layer links.
l Optical path between an ASON NE and a non-ASON NE
WARNING
If the LMP is disabled, the ASON feature of the corresponding optical interface is disabled,
which severely affects ASON services. Between ASON NEs, the LMP protocol for the optical
path used by ASON services should not be disabled.
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > Advanced Maintenance from the
Function Tree.
Step 2 Click the LMP Protocol Status tab. Click Query to query the ASON protocol information from
the NE.
Step 3 Select the port at which the LMP is to be disabled. Double-click the LMP Protocol Status
column and choose Disabled from the drop-down list.
NOTE
If you need to enable the LMP, choose Enabled.
Step 4 Click Apply. A confirm dialog box is displayed.
Step 5 Click Yes. The operation result dialog box is displayed, click Close.
Step 6 Click Query. Queries LMP protocol status from the NE.
1. Right-click the required NE whose LMP control channel needs to be queried, and choose
NE Explorer.
2. Choose ASON > Link Management Protocol from the Function Tree.
3. Click the LMP Control Channel tab. Click Query, and then query the information about
the LMP control channel from the NE.

If Administration Status and Operational Status are displayed as UP, the LMP control
channel status is normal.
----End
4.3.2 Configuring the OSPF Protocol

Generally, the OSPF protocol should not be disabled. In certain cases, however, you can disable
the protocol to release idle resources, and thus rationally use resources.
Prerequisite
The OSPF protocol involves the following types of interfaces:
l Interface for the connection between ASON NEs
l Ethernet interface of ASON NEs
l Interface for the connection between an ASON NE and a non-ASON NE
By default, the first type of interface runs the OSPF protocol. By default, the second type of
interface does not run the OSPF protocol. For the former two types of interfaces, use the default
settings, which should not be modified. By default, the third type of interface runs the OSPF
protocol. Due to the connection to a non-ASON NE, however, the OSPF protocol for this type
of interface must be disabled.
On the network where only optical-layer ASON is deployed, disable the OSPF protocol at
electrical-layer interfaces (the type of control interfaces is PM_RES) if virtual TE links are not
configured.
WARNING
If the OSPF protocol is disabled, the ASON feature of the corresponding optical interface is
disabled, which severely affects ASON services. Hence, do not disable the OSPF protocol if not
necessary.
Procedure
Function Tree.
Step 2 Click the OSPF Protocol Status tab. Click Query to query the ASON protocol information
from the NE.
Step 3 Select the port at which the OSPF protocol is to be disabled. Double-click the OSPF Protocol
Status column. Choose Disabled from the drop-down list.

NOTE
If you need to enable the OSPF protocol, choose Enabled.

Step 6 Click Query. Queries OSPF protocol status from the NE.
----End
4.3.3 Configuring the OSPF Protocol Authentication

You can query and set the OSPF protocol authentication to ensure the security of the ASON
network.
Prerequisite
The authentication conditions for an NE and its remote NE must be the same.
CAUTION
If the authentication conditions for an NE and its remote NE are different, the protocol
communication is interrupted and services are affected.
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > OSPF Protocol Management from the
Function Tree.
Step 2 Click the OSPF Protocol Authentication tab.
Step 3 Click Query.
Step 4 Double-click Authentication Mode or Authentication Key to set the two parameters.

NOTE
l The following three options are available for Authentication Mode: Unconfigured, Plain Text
Password Authentication and MD5 Encryption Authentication.
l When the value is Plain Text Password Authentication, the authentication is performed based on the
specified password. In this case, the Authentication Key must be a string of a maximum of eight
characters.
l When the value is MD5 Encryption Authentication, the authentication is performed based on the
password obtained by using the MD5 encryption algorithm. In this case, the Authentication Key must
be a non-empty string of a maximum of 64 characters.
Step 6 Click OK.
----End
4.3.4 Configuring the RSVP Protocol Authentication

You can query and set the resource reservation protocol (RSVP) authentication to ensure the
security of the ASON network.
Prerequisite
Context
The RSVP authentication is set for nodes. The authentication conditions for an NE and its
neighbors must be the same.
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > RSVP Protocol Management from the
Function Tree.
Step 2 Click Query.
Step 3 Click New. The RSVP Authentication Create dialog box is displayed.
Step 4 Set Neighboring Node, Type and Key.
NOTE
l The following two options are available for Authentication Mode: Unconfigured and MD5
Encryption Authentication.

Step 5 Click OK.

NOTE
To create multiple entries of RSVP authentication, click Apply.
----End
4.4 Configuring the Link Parameter

A reasonable way of link parameter management is required to make the most of the network
resources and to improve the network efficiency.
4.4.1 Creating an SRLG

Fibers in the same optical cable have the same risk. If the cable is cut, all fibers are also cut.
During the service rerouting, services should not be rerouted to the link that belongs to the same
shared risk link group (SRLG). Therefore, you need to set the same SRLG value for TE links
that share the same risks in the network.
Prerequisite
l The TE link data has been synchronized on the U2000.
Service Requirement
See Figure 4-2. All NEs are ASON NEs. NE4 and NE5 are in the same equipment room. The
fiber between NE1 and NE4, and the fiber between NE1 and NE5 are within the same cable. In
this situation, the TE links of the two fibers share the same risk.
Figure 4-2 SRLG schematic diagram
Two fibers in one cable
NE1 NE4
NE5
NE2 NE3
Procedure
l Configure the SRLG attribute of TE links for electrical-layer ASON services.
1. Choose Configuration > WDM ASON > TE Link Management from the main
menu.

2. Select the TE links. Double-click the SRLG field and enter a value. In this example,
the same field value should be applied to the SRLG of the TE link between NE1 and
NE4 and the SRLG of the TE link between NE1 and NE5.
3. Click Apply for the settings to take effect.

NOTE
After you modify the attributes, the TE link in the opposite direction is automatically set to the same
SRLG value.
The values of the SRLG field for the links in the same SRLG should be the same. The field value 0
indicates no SRLG.
l Configure the SRLG attribute of TE links for optical-layer ASON services.
1. Choose Configuration > WDM ASON > SRG Management from the main menu.
2. Click New. The Create SRG dialog box is displayed.
3. Enter the basic information about the SRLG.
– Name: SRG_pipe_001
– ID: 1
– ASON Domain: ASON
– Type: Pipe
– Remarks: pipe
4. In the SRG Member Information window, select the trails corresponding to the links
from NE1 to NE4 and from NE1 to NE5 in the Unselected Objects area and click
to add the trails to SelectedObjects.

5. Click OK. After the operation succeeds, the Result dialog box is displayed. Click
Close.
NOTE
l When configuring the SRLG attribute of TE links for optical-layer ASON services, perform
configurations on the TE links carrying OMS signals between FIU boards that the services
traverse.
l When configuring the SRLG attribute of TE links for electrical-layer ASON services, perform
configurations on the service links carrying OTUk signals.
l If the opposite end of an ODUk TE link is manually configured, configure the SRLG attribute
for the link separately.
----End
4.4.2 Configuring the Link Distance

You can set the link distance on the U2000 for route calculation. If you want to use the physical
distance between NEs as one element for the route calculation, you need to set the TE link
distance according to the actual physical distance.

Prerequisite
l TE link management is based on correct link information.
Procedure
Step 2 Click Synchronize. In the Synchronize dialog box displayed, choose Domain and Payload
Type.
NOTE
Step 4 Select a link, double-click the Distance(km) field, and enter a value.
Step 5 Click Apply for the settings to take effect.
----End
4.4.3 Setting Link Cost

You can set the link cost on the NMS. After you customize the link cost, the system takes into
account the overall cost of a link including the custom link cost and selects the trail with the
minimum link cost.
Prerequisite
l You must be an NM user with the "NE operator" authority or higher.
l TE link data must exist on the NMS.
Context
Setting the custom link cost is actually to set the user-defined attributes of a link. Such cost
enables a user to set many attributes of a link. For example:
l Aging level of a link: The link cost increases with the link aging level. It is less likely for
the ASON software to choose a link with a higher link cost when calculating routes.
l Link price: The link cost increases with the link price. It is less likely for the ASON software
to choose a link with a higher link cost when calculating routes.
l Interruption probability of a link: The link cost increases with the interruption probability.
It is less likely for the ASON software to choose a link with a higher link cost when
calculating routes.
With this function, users can adjust the link cost as required and select the expected link. During
service creation or service rerouting, the system determines whether to transmit the service over

a link according to the custom cost of the link. The custom cost and custom cost weight must
be set together.
Procedure
Step 2 Click Synchronize. In the displayed Synchronize dialog box, choose Domain and Payload
Type.
Step 3 Click Synchronize to confirm the synchronization information.

NOTE
When the synchronization is successful, information about TE links is displayed.
Step 4 Select the required TE link and double-click the Custom Cost field. Then, enter a required value.
NOTE
The value of Custom Cost ranges from 0 to 100. A greater value indicates a higher cost.
When the custom cost weight is the same as the hop quantity weight, the value of Custom Cost is equal
to the quantity of hops. For example, the value 1 indicates the cost of one hop, and the value 10 indicates
the cost of ten hops.
Step 5 Click Apply to apply the setting.
Step 6 Navigate to the NE Explorer of the source node with ASON services. Then, choose
ASONControl Plane Parameters from the Function Tree and enter a value in the Custom Cost
Weight field to set the custom cost weight.
NOTE
The value of Custom Cost Weight ranges from 0 to 500. A greater value indicates a higher cost weight.
----End
4.4.4 Setting Resource Reservation

You can reserve resource for traditional WDM trails on ASON NEs. In an ASON, you can also
create traditional services in addition to ASON services. The reserved resources at a port are
used for the creation of traditional WDM trail. These resources cannot be used when you create
ASON-WDM services or when the ASON-WDM services are rerouted.
Prerequisite

Procedure
Step 1 In the NE Explorer, click a board and choose ASON > Resource Reservation Management
from the Function Tree.
Step 2 Click Query to query the wavelength resource reservation status of the board from the NE.
Step 3 Select the wavelength to be reserved. Double-click Resource Reservation to set the value to
Enabled.
NOTE
Resource Reservation represents whether the wavelength resources at the optical port are reserved for
traditional services. If you select Enabled, the resource is reserved for traditional services. In this case,
you must configure the remote end in the same way.
Step 4 Click Apply. A dialog box appears, telling that the settings are applied.
----End
4.5 Commissioning Preset Restoration Trails

If the working trail of an ASON service configured with a preset restoration trail experiences a
fiber break, the ASON service will be switched to the preset restoration trail with precedence.
To ensure that the preset restoration trial functions properly, commission optical power for the
preset restoration trail.
Prerequisite
l You must be an NM user with "network operator" authority or higher.
l A preset restoration trail has been configured.
l The ASON service must be locked during commissioning; otherwise, the ASON service
may be rerouted.
Procedure
Step 1 Switch the ASON service to the preset restoration trail. For details, see Testing Restoration of
ASON Services to the Preset Trail.
Step 2 Lock rerouting of the ASON service. For details, seeSetting Route Attributes.
Step 3 Generate a WDM link. For details, see Creating a WDM Link.
Step 4 Commission optical power of the preset restoration trail. For details, see Commissioning Preset
Trails.
Step 5 Unlock rerouting of the service. For details, see Setting Route Attributes.
NOTE
If there is another preset restoration trail for the ASON service, repeat Steps 1–5 to commission optical
power for it.
Step 6 Revert the ASON service to the original route. For details, see Reverting A WDM ASON Trail
to the Original Route.
Step 7 Re-generate a WDM link.
----End


the foundation of network routing computation. The ASON software supports the auto-discovery
of ASON NEs, TE links, control links and inter-NE fibers. The internal fibers of an NE, however,
need be manually created.
4.6.1 Testing the Auto-Discovery of ASON NEs

ASON supports the auto-discovery of ASON NEs.
Prerequisite
l The NE must be in operating state.
l The NE software must contain ASON features and must be successfully enabled.
Test Standard
After the NE configuration data are synchronized, the NEs whose ASON features are just enabled
are automatically added to the ASON domain where the NEs reside.
Procedure
Step 1 In the Main Menu, choose Configuration > NE Configuration Data Management, and the
NE Configuration Data Management user interface is displayed. On the NE list, select the
desired NE. Click to add the NE to Configuration Data Management List.
Step 2 In Configuration Data Management, select the NE and click Upload. After the upload, click
OK in the displayed prompt box.
Step 3 In the Main Menu, choose Configuration > WDM ASON > ASON Topology Management,
and the WDM ASON Topology Management user interface is displayed. The NEs whose
ASON features are just enabled are displayed in the ASON domain where the NEs reside.
Step 4 Disconnect the fiber connection of an NE to make the NE an isolated one. By Synchronizing
ASON NEs on the U2000, you can see that the NE is displayed as an isolated NE.
Step 5 Restore the fiber connection of the NE. By Synchronizing ASON NEs on the U2000, you can
see that the fiber connection of the NE is restored.
----End
4.6.2 Testing the Auto-Discovery of Control Links

ASON supports the auto-discovery of control links. You can view in real time any change of
the ASON network topology in the WDM control link management window.
Prerequisite
l The NE software must contain ASON features and must be successfully enabled.

l The inter-node communication must be available.
Test Standard
Any change of the ASON network topology can be viewed in real time in the WDM Control
Link Management window.
Procedure
l Testing the auto-discovery of control links of the WDM ASON OCh trail
1. In the Main Menu, choose Configuration > WDM ASON > Control Link
Management. Click Synchronize, and you can view the network topology.
2. Refer to Figure 4-17 and Figure 4-18. Disable the laser on the NE2-directed OSC
board on NE1. In the WDM Control Link Management window, click
Synchronize, and you find that the control link between NE1 and NE2 is deleted.
3. Enable the laser on the NE2-directed OSC board on NE1 and wait until the laser
normally operates. In the WDM Control Link Management window, click
Synchronize, and you find that the control link between NE1 and NE2 is automatically
added.
4. Remove the fiber between NE2 and other NE. In the WDM Control Link
Management window, click Synchronize, and you find that all control links to NE2
are deleted.
5. Connect the fiber between NE2 and other NE. In the WDM Control Link
are automatically added.
l Testing the auto-discovery of control links of the WDM ASON ODUk trail
1. In the Main Menu, choose Configuration > WDM ASON > Control Link
Management. Click Synchronize, and you can view the network topology.
2. Refer to Figure 4-15 and Figure 4-16. Remove the fiber between NE1-22-NS2 and
NE2-22-NS2.Click Synchronize, and you find that the control link between NE1 and
NE2 is automatically deleted.
3. Connect the fiber between NE1-22-NS2 and NE2-22-NS2. In the WDM Control
Link Management window, click Synchronize, and you find that the control link
between NE1 and NE2 is automatically added.
4. Remove the fiber between NE2 and other NE. In the WDM Control Link
are deleted.
5. Connect the fiber between NE2 and other NE. In the WDM Control Link
are automatically added.
----End
4.6.3 Testing the Auto-Discovery of TE Links

ASON supports the auto-discovery of TE links. You can view in real time any change of the
ASON network topology in the TE link management window.

Prerequisite
l The NE software must contain ASON features and must be successful enabled.
l The inter-node communication must be available.
Test Standard
Any change of the ASON network topology can be viewed in real time in the WDM TE Link
Management window.
Procedure
l Testing the auto-discovery of TE links of the WDM ASON OCh trail
1. In the Main Menu, choose Configuration > WDM ASON > TE Link
Management. Click Synchronize, and you can view the following network topology.
2. Refer to Figure 4-17 and Figure 4-18. Turn off the laser on the NE2-directed OSC
board on NE1. In the WDM TE Link Management window, click Synchronize, and
you find that the TE link between NE1 and NE2 is deleted.
3. Reopen the laser on the NE2-directed OSC board on NE1 and wait until the laser
normally operates. In the WDM TE Link Management window, click
Synchronize, and you find that the TE link between NE1 and NE2 is automatically
added.
4. Remove the fiber between NE2 and other NE. In the WDM TE Link Management
window, click Synchronize, and you find that all TE links to NE2 are displayed as
interrupted.
5. Connect the fiber between NE2 and other NE. In the WDM TE Link Management
window, click Synchronize, and you find that all TE links to NE2 are automatically
added.
l Testing the auto-discovery of TE links of the WDM ASON ODUk trail
1. In the Main Menu, choose Configuration > WDM ASON > TE Link
Management. Click Synchronize, and you can view the following network topology.
2. Refer to Figure 4-15 and Figure 4-16. Remove the fiber between NE1-22-NS2 and
NE2-22-NS2. In the WDM TE Link Management window, click Synchronize, and
you find that the TE link between NE1 and NE2 is deleted.
3. Connect the fiber between NE1-22-NS2 and NE2-22-NS2. In the WDM TE Link
Management window, click Synchronize, and you find that the TE link between NE1
and NE2 is automatically added.
4. Remove the fiber between NE2 and other NE. In the WDM TE Link Management
window, click Synchronize, and you find that all TE links to NE2 are displayed as
interrupted.
5. Connect the fiber between NE2 and other NE. In the WDM TE Link Management
window, click Synchronize, and you find that all TE links to NE2 are automatically
added.
----End

4.7 Testing ASON Features of a Service

ASON features ensure normal running of an ASON network. After an ASON NE is configured,
you should test and verify the related ASON features according to the project situations.
4.7.1 Testing Creation and Deletion of ASON Services

The functions of creation and deletion of ASON services on a network are tested through the
U2000.
Prerequisite
l The NE under test must be in the running state.
l The software of the NE under test must contain ASON features and the ASON features
must be successfully enabled.
Test Standard
ASON services can be created or deleted according to requirements.
Test Networking Diagram

Figure 4-3 shows a mesh network consisting of eight NEs. NE1, NE4, and NE7 are ROADM
sites, and NE2, NE3, NE5, NE6, and NE8 are OLA sites.
Figure 4-3 Networking diagram for the ASON feature test

NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
Procedure
Step 1 Create an ASON service from NE1 to NE7 according to the operation steps in Creating WDM
ASON Trails, and set NE8 as an explicit node.

Step 2 Activate this ASON service, and then creating the ASON service is complete.
Step 3 On the Main Menu, choose Configuration > WDM ASON > ASON Trail Management and
check the created ASON trail. The displayed trail information must be consistent with the created
trail, and the trail must involve NE8.
Step 4 Deactivate and delete this ASON service, and then you can query the ASON service on the
U2000 to verify the deletion..
----End
4.7.2 Testing Creation Disabling of the Rerouting Function of

ASON Services
Creation disabling of the rerouting function caused by insufficient ASON network resources is
tested.
Prerequisite
Test Standard
When the network resources are insufficient, the system denies the request of creating ASON
services.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8

Procedure
Step 1 Break the fiber connections between NE1 and other NEs, and then no link is available between
NE1 and NE7.
ASON Trails.
Step 3 On the U2000, a message indicating a connection failure is returned, and thus the ASON service
cannot be created.
Step 4 After the test is complete, recover the fiber connections between NE1 and other NEs.
----End
4.7.3 Testing Query and Change of ASON Services

The query and change functions of ASON services are tested on the U2000.
Prerequisite
Test Standard
The attributes of ASON services can be queried and changed.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8

Procedure
ASON Trails.
Step 2 Check the attributes of this ASON service according to the steps in Viewing WDM ASON Trail
Attributes.
Step 3 Change the trail attributes of this service such as Name in the Viewing WDM ASON Trail
Attributes interface.
Step 4 Then, query the trail attributes of this service, and determine whether the query results are correct.
Step 5 Deactivate and then delete this ASON service.
----End
4.7.4 Testing the Rerouting Lockout Function of ASON Services

The rerouting lockout function of ASON services is tested on the U2000.
Prerequisite
Test Standard
The rerouting attribute of ASON services can be set to lockout.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8

Procedure
ASON Trails.
Step 2 Set the lockout status of the routing attribute for this service to Locked according to the operation
steps in Setting the Routing Attributes.
Step 3 Break the fiber connections between NE1 and NE7 which this ASON service traverses. In this
case, this ASON service cannot be rerouted, and a control-plane alarm indicating service
interruption is reported on the U2000.
Step 4 Set the lockout status of the routing attribute for this service to Unlocked according to the
operation steps in Setting the Routing Attributes.
Step 5 In this case, this service is rerouted, and reporting of the control-plane alarm indicating service
interruption ends.
Step 6 Recover the fiber connections between NE1 and NE7, and deactivate and delete this service.
----End
4.7.5 Testing Trail Pre-computation of ASON Services

The trail pre-computation function of ASON services is tested on the U2000. Users can create,
reroute, and optimize ASON services through the trail pre-computation function.
Prerequisite
Test Standard
Before an ASON service is created, the service trail can be pre-computed.



NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
Procedure
ASON Trails.
NOTE
Select Automatic Pre-Calculation, and then click Pre-Calculation. Then, the ASON service can be
created through the pre-computation function.
During service creation, set reroute constraints for the service. For example, set NE3 as an explicit node.
check the created ASON trail. The displayed trail information must be consistent with the created
trail, and the trail must involve NE3.
Step 3 Deactivate and delete this ASON service.
----End
4.7.6 Testing Restoration of ASON Services to the Preset Trail

The function of restoring ASON services to the preset trail is tested on the U2000.
Prerequisite
Test Standard
When ASON services are faulty, the services can be rerouted to the preset restoration trail.



NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
Procedure
ASON Trails. The restoration trail is NE1–NE2–NE3–NE4–NE6–NE7.
Step 2 Preset a restoration trail from NE1 to NE7 according to the operation steps in Setting Preset
Restoration Trail. The restoration trail is NE1–NE5–NE4–NE8–NE7.
Step 3 Break the fiber connections between NE1 and NE2, and thus this ASON service is restored to
the preset restoration trail.
Step 4 Recover the fiber connections, and deactivate and delete this service.
----End
4.7.7 Testing Modification and Adjustment of ASON Service Trails

The function of modifying and adjusting ASON service trails is tested on the U2000.
Prerequisite
Test Standard
ASON services can be optimized so that they are rerouted along specified trails.



NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
Procedure
Step 1 Create a sliver ASON service from NE1 to NE7 according to the operation steps in Creating
WDM ASON Trails. The service trail is NE1–NE2–NE3–NE4–NE6–NE7.
Step 2 Optimize this service according to the operation steps in Modifying the Route of an ASON
Service, and specify NE5 as an explicit node.
check the optimized ASON trail. The displayed trail information must be consistent with the
optimized trail and the trail must involve NE5.
Step 4 Optimize this service according to the operation steps in Modifying the Route of an ASON
Service, and specify NE8 as an explicit node.
check the optimized ASON trail. The displayed trail information must be consistent with the
specified trail and the trail must involve NE8.
----End
4.7.8 Testing ASON Service Restoration on the Entire Network

The ASON service restoration function is tested on the U2000.
Prerequisite

Test Standard
ASON services can be restored to the trails that are initially planned.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
Procedure
Step 1 Create an ASON sliver service from NE1 to NE7 according to the operation steps in Creating
WDM ASON Trails. The service trail must involve NE3 and NE6.
Step 2 Create an ASON copper service from NE1 to NE7 according to the operation steps in Creating
WDM ASON Trails. The service trail must involve NE3 and NE6.
Step 3 Optimize these services according to the operation steps in Modifying the Route of an ASON
Service, and make sure that the service trails involve NE5.
check the optimized ASON trails. The displayed trail information must be consistent with the
specified trails.
Step 5 Perform network-wide restoration on these ASON services according to the operation steps in
Reverting A WDM ASON Trail to the Original Route, and thus the services are restored to
the trails that are initially planned.
check the restored ASON trails. The displayed trail information must be consistent with the trails
that are initially planned.

Step 7 Deactivate and delete these ASON services.
----End
4.7.9 Testing Route Computation Based on Constraints

The ASON route computation function based on constraints is tested on the U2000.
Prerequisite
Test Standard
An explicit node, excluded node, explicit link, and excluded link can be set for an ASON service
trail.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
Procedure
WDM ASON Trails.
NOTE
During creation, specify NE5 and NE8 as explicit nodes.

check the created ASON trail. The displayed trail information must be consistent with the
specified trail and the trail must involve NE5 and NE8.
Step 4 Create a sliver ASON service from NE1 to NE7 according to the operation steps in Creating
WDM ASON Trails.
NOTE
During creation, specify NE5 and NE8 as excluded nodes.
specified trail and the trail should not involve NE5 and NE8.
WDM ASON Trails.
NOTE
During creation, specify the link between NE6 and NE7 an explicit link.
specified trail and the trail must involve the link between NE6 and NE7.
WDM ASON Trails.
NOTE
During creation, specify the link between NE6 and NE7 and the link between NE1 and NE2 as explicit
links.
specified trail and the trail should not involve the link between NE6 and NE7 and the link between
NE1 and NE2.
Step 12 Test the service by using a meter and make sure that the ASON service is normal without any
bit error or alarm.
----End
4.7.10 Testing Rerouting of Associated Services

The rerouting function of associated services is tested.
Prerequisite

Test Standard
When an ASON service associated with other ASON services is faulty, the ASON service can
be successfully rerouted. If the network resources are sufficient, the new service trail does not
overlap with the trails of the associated services.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
Procedure
Step 1 Create two associated ASON services from NE1 to NE7 according to the operation steps in
Setting Association of WDM ASON Trails.
NOTE
The trail of one service is NE1–NE2–NE3–NE4–NE6–NE7, and the service wavelength is λn. This trail is
called trail A. The trail of another service is NE1–NE5–NE4–NE8–NE7, and the service wavelength is
λn+1. This trail is called trail B. Both trails are for silver ASON services.
Step 2 Test the services by using a meter and make sure that the ASON service is normal without any
bit error or alarm.
check the created ASON trails. The displayed trail information must be consistent with the
specified trails.
Step 4 Break the fiber connections between NE1 and NE2, and then trail A starts rerouting. In this case,
check the ASON trail information. The new trail is NE1–NE5–NE4–NE6–NE7.
bit error or alarm.

Step 6 Break the fiber connections between NE4 and NE6, and then the new trail starts rerouting. In
this case, check the ASON trail information, and the new trail is NE1–NE5–NE4–NE8–NE7.
bit error or alarm.
NOTE
In the case of the associated optical-layer or electrical-layer services that have the same source, you can
set the rerouting conditions on the U2000. The rerouting condition can be either of the following:
l Rerouting is triggered when only one service is interrupted (default condition).
l Rerouting is triggered only when both services are interrupted.
----End
4.7.11 Testing Conversion Between ASON Services and Traditional

Services
The function of conversion between ASON services and traditional services is tested on the
U2000.
Prerequisite
Test Standard
The ASON services and traditional services can be converted between each other, and the
conversion process does not affect the services.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8

Procedure
Step 1 The conversion from an ASON service to a traditional service is tested.
1. Create an ASON service from NE1 to NE7 according to the operation steps in Creating
WDM ASON Trails.
2. On the Main Menu, choose Configuration > WDM ASON > ASON Trail
Management and check the converted ASON trail. The displayed trail information must
be consistent with the specified trails.
3. Convert the ASON service to a traditional service according to the operation steps in
Migrating a WDM ASON Trail to a Traditional WDM Trail.
4. Test the service by using a meter and make sure that the ASON service is not normal during
conversion without any bit error or alarm.
5. On the Main Menu, choose Configuration > WDM Trail > WDM Trail Management
and query the trail of the traditional service.
NOTE
After the conversion between the ASON service and traditional service is complete, wait for one minute
and then query the traditional service on the U2000.
If you need to query the traditional trail after conversion in real time, you should synchronize the cross-
connection resources on each NE along the trail of the traditional service.
6. Delete this service.
Step 2 Conversion between traditional services and ASON services is tested.

1. Create a traditional service from NE1 to NE7 according to the Configuration Guide.
2. On the Main Menu, choose Configuration > WDM Trail > WDM Trail Management
and query the trail of the traditional service.
3. Convert the traditional service to an ASON service according to the operation steps in
Migrating a Traditional WDM Trail to a WDM ASON Trail.
4. Test the service by using a meter and make sure that the ASON service is normal during
5. On the Main Menu, choose Configuration > WDM ASON > ASON Trail
Management and check the new ASON trail.
6. Deactivate and delete this ASON service.
----End
4.7.12 Testing the Conversion Between ASON Services with

Different SLAs
The conversion function between electrical-Layer ASON services with different SLAs is tested
on the U2000.
Prerequisite
l The software of the NE under test must contain ASON features and must be successfully
enabled.

NOTE
The conversion between optical-Layer WDM ASON OCh trails is not supported.
Test Standard
The ASON services with different SLAs can be converted into each other.


NE3 NE6
NE2
NE1 NE4 NE7
NE5 NE8
This section describes how to convert a diamond service to a silver service.
Procedure
Step 1 Create a diamond ASON service from NE1 to NE7 according to the operation steps in Creating
WDM ASON Trails.
Step 2 Choose Configuration > WDM ASON > ASON Trail Management from the Main Menu and
check the ASON trail after conversion. The displayed trail information must be consistent with
the specified trails.
Step 3 Convert the diamond service into a silver service according to the operation steps in Conversion
Between the Diamond and Silver or Copper WDM ASON Trails.
Step 4 Choose Configuration > WDM ASON > ASON Trail Management from the Main Menu and
check the ASON trail information after conversion. The displayed trail information does not
change, but the service level changes to silver.
Step 5 Test the service by using a meter and make sure that the ASON service is normal during

NOTE
l When a diamond ASON service is converted to a silver or copper ASON service, if reserve the
protection route is selected, the service is transiently interrupted during switching.
----End
4.8 Testing the Rerouting Capability of ASON Services

The ASON network can provide multiple ASON services. Each ASON service has different
Context
4.8.1 Testing an Electrical-Layer Diamond WDM ASON ODUk

Trail
The diamond WDM ASON ODUk (k = 0, 1, 2, 3) trail is classified into the following types:
permanent 1+1 diamond service (rerouting is triggered once an LSP fails), rerouting 1+1
diamond service (rerouting is triggered only when both LSPs fail), and non-rerouting diamond
service (rerouting is never triggered). The permanent 1+1 diamond WDM ASON ODU1 trail is
considered as an example in this section to describe the commissioning process. Test methods
vary according to granularities, and the only difference is the service level. This section considers
the ODU1 trail as an example.
Prerequisite
l The SRLGs should be correctly set.
l There should be sufficient network resources.
l There is no alarm that can trigger rerouting in the ASON subnet.
l There is no alarm that can trigger protection switching in the ASON subnet.
Networking Diagram
As shown in Figure 4-15, a permanent 1+1 diamond WDM ASON ODU1 trail needs to be
configured between NE1 and NE3. The active LSP must pass NE2 and the standby LSP must
pass NE4. Then, commission the service.
Figure 4-15 Networking diagram of the diamond WDM ASON ODU1 trail
NE1
Working 11 7 Potection
LSP LSP
7 8 11
8
NE2 NE4
8
11 8 7
7 11 : ASON NE
NE3 : LSP

Board Configuration
In this example, NE1, NE2, NE3, and NE4 share the same board configuration. In the case of
the OptiX OSN 8800, see Figure 4-16.
Figure 4-16 Board configuration
FAN
A
EF U
EFI2 PIU PIU X PIU PIU ATE
I1
N S S S F F F
S C C C I I I
2 C 2 1 U U U
X X
C C
H H
M
R T T N N S
8 O D S S C
V M X 2 2 C
FAN
Specifications
The switching time of diamond services is less than 50 ms. The service rerouting time is about
500ms in this networking. The rerouting time varies with the network size, capacity and service
types. The test in this section is based on the previous networking scenario.
Procedure
Step 1 At NE1, respectively connect the output and input optical interfaces of the SDH signal analyzer
to the Rx1 and Tx1 interfaces on the client side of the TOM board through the fixed optical
attenuator.
Step 2 At NE3, use fibers to connect the Rx1 and Tx1 interfaces on the client side of the TOM board
through the fixed optical attenuator, realizing the client-side loopback.
Step 3 Refer to Creating Diamond WDM ASON ODUk Trails to create the trail. The source port
is"NE1-4-TOM-201(LP1/LP1)-1" and the sink port is "NE3-4-TOM-201(LP1/LP1)-1". The
working trail is NE1->NE2->NE3 and the protection trail is NE1->NE4->NE3.
Step 4 Remove the fiber at the IN interface on the 12-NS2 board connecting to NE2 at NE1. Then, the
working trail switches to NE1->NE4->NE3. The protection trail is NE1->NE3 after rerouting
is complete. Check the SDH analyzer. The switching time is less than 50 ms.

Step 5 Remove the fiber at the IN interface on the 7-NS2 board connecting to NE4 at NE1. The service
is rerouted to NE1->NE3. A new protection trail cannot be found based on the current resources.
Check the SDH analyzer. The rerouting time is less than 50 ms.
is interrupted.
Step 7 Connect the removed fibers back to the original interfaces and delete the diamond service.
----End
4.8.2 Testing an Optical-Layer Silver WDM ASON OCh Trail

For a silver WDM ASON OCh trail, when an LSP failure occurs, periodical rerouting is
performed until the rerouting succeeds. If there are not enough resources, service may be
interrupted.
Prerequisite
Networking Diagram
Figure 4-17 shows a mesh network that consists of four NEs. NE1, NE2, NE3, and NE4 are
ASON NEs.
Figure 4-17 Networking diagram of the silver WDM ASON OCh trail
NE1
15 1
116
1 15
116
NE2 NE4
116
15 116 1
1 15 : ASON NE
NE3 : LSP
Board Configuration
OptiX OSN 8800, see Figure 4-18.

Slave Subrack 1 FAN

A
EF U
I1
R W W R
N N N N N N N N S N N N N N N N T
M S S M
Q Q Q Q Q Q Q Q C Q Q Q Q Q Q Q Q
U D D U
2 2 2 2 2 2 2 2 C 2 2 2 2 2 2 2 X
9 9 9 9
X X
C C
S S
O W
T T
L T R
F S T TW T T T O O
M S B SM BM40A
Q Q
S I Q
C Q Q Q Q Q D40
U D U D U U
X X
U M
1 M M M M M 1 4
9 9 1 1
FAN
Master Subrack FAN

A
EF U
EFI2
EFI2 PIU PIU X PI
PI
UU PI
PI
UU ATE
I1
R W W W R
S
M S S SSM M
M40 D40 C D40 M40
U D M D U
C
9 9D 4 9
4 9
O O OO O O
F S S S S
F O F
B A BB A B
I C C C C
I A I
U U UU U U
U C 2 2 2
U U 1 U
1 1 11 1 1
FAN

Specifications
The service rerouting time is about 3s to 5s in this networking. The rerouting time varies with
the network size, capacity and service types. The test in this section is based on the previous
networking scenario.
Procedure
to the Rx and Tx interfaces on the client side of the OTU board through the fixed optical
attenuator.
Step 2 At NE3, use fibers to connect the Rx and Tx interfaces on the client side of the OTU board
Step 3 Refer to Creating Silver WDM ASON OCh Trails to create the trail. The source port is
"NE1-101-LSX-1(IN/OUT)-2/1529.16/196.050" and the sink port is "NE3-101-LSX-1(IN/
OUT)-2/1529.16/196.050". The working trail is NE1->NE2->NE3.
Step 4 Remove the fiber at the IN interface on the FIU board connecting to NE2 at NE1. The service
is interrupted. Check the SDH analyzer. The rerouting time is about 2 seconds.
is rerouted to NE1->NE4->NE3. Check the SDH analyzer. The rerouting time is about 2 seconds.
is interrupted because a new protection trail cannot be found based on the current resources.
Step 7 Connect the removed fibers back to the original interfaces and delete the silver WDM ASON
OCh trail.
----End
4.8.3 Testing an Electrical-Layer Silver WDM ASON ODUk Trail

For a silver WDM ASON ODUk (k = 0, 1, 2, 3) trail, when an LSP failure occurs, periodical
rerouting is performed until the rerouting succeeds. If there are not enough resources, service
may be interrupted. Test methods vary according to granularities, and the only difference is the
service level. This section considers the ODU1 trail as an example.
Prerequisite
Networking Diagram
Figure 4-19 shows a mesh network that consists of four NEs. NE1, NE2, NE3, and NE4 are
ASON NEs.

Figure 4-19 Networking diagram of the silver WDM ASON ODU1 trail
NE1
11 7
8
7 11
8
NE2 NE4
8
11 8 7
7 11 : ASON NE
NE3 : LSP
Board Configuration
the OptiX OSN 8800, see Figure 4-20.
FAN
A
EF U
I1
N S S S F F F
S C C C I I I
2 C 2 1 U U U
X X
C C
H H
M
R T T N N S
8 O D S S C
V M X 2 2 C
FAN
Specifications
The service rerouting time is about 500ms in this networking. The rerouting time varies with
the network size, capacity and service types. The test in this section is based on the previous
networking scenario.

Procedure
to the Rx1 and Tx1 interfaces on the client side of the TOM board through the fixed optical
attenuator.
Step 2 At NE3, use fibers to connect the Rx1 and Tx1 interfaces on the client side of the TOM board
Step 3 Refer to Creating Silver WDM ASON ODUk Trails to create the trail. The source port is
"NE1-4-TOM-201(LP1/LP1)-1" and the sink port is "NE3-4-TOM-201(LP1/LP1)-1". The
working trail is NE1->NE2->NE3.
is rerouted to NE1->NE3. Check the SDH analyzer. The rerouting time is about 500ms.
is rerouted to NE1->NE4->NE3. Check the SDH analyzer. The rerouting time is about 500ms.
is interrupted because a new protection trail cannot be found based on the current resources.
Step 7 Connect the removed fibers back to the original interfaces and delete the silver WDM ASON
ODU1 trail.
----End

ASON User Guide 5 Commissioning the OCS ASON
5 Commissioning the OCS ASON
About This Chapter
This chapter describes the ASON software commissioning by using the U2000.
5.1 Preparations
the foundation of network routing computation. The OptiX GCP V100R003 supports the auto-
discovery of ASON NEs, TE links, control links and inter-NE fibers. The internal fibers of an
NE, however, need be manually created.An ASON topology consists of ASON NEs, fibers and
TE Links. Resources refer to VC4s on TE links.
5.3 Testing the ASON Services
The ASON network can provide multiple ASON services. Each ASON service has the different
5.4 Testing Batch Rerouting
This section describes the method to test the performance of rerouting 16 silver services.

5.1 Preparations
5.1.1 Networking Diagram

To conveniently describe the whole process of commissioning the ASON software, all
commissioning items described in this chapter are based on the following network.
Figure 5-1is an STM-64 mesh network composed of four OptiX OSN 8800: NE1, NE2, NE3,
and NE4. NE1 is the gateway NE.
Figure 5-1 Networking diagram
NE1
24 26
26 25 25
24 24 NE4
NE2
25 24 26
26 25
NE3 : ASON NE
24: Slot 24
25: Slot 25
26: Slot 26
Figure 5-2 shows the board configuration of NE1, NE2, NE3, and NE4.

FAN
A
EF U
I1
S
S S S
L S S S F F F
L L L
H C C C I I I
6 6 6
4 C 2 1 U U U
4 4 4
1
X X
C C
M H
M
T T N N S N
R
O D S S C S
8
M X 2 2 C 2
V
FAN
NOTE
An ASON NE should be configured with two SCC boards.

l In the case of the OptiX OSN 8800, the SCC boards that support the ASON features are the 51SCC
and 52SCC.
5.1.2 Tools and Documents

The commissioning documents, tools and meters must be prepared before the commissioning
of the ASON.
The following documents and tools are required before the commissioning.
l Construction files
l ASON User Guide
l SDH analyzer
l Optical attenuator
5.1.3 Checking Consistency Between Logical Boards and Physical

Boards
When the types of the logical board and physical board are inconsistent, the board cannot work
normally. As a result, the user services are affected. Hence, check the consistency between the
logical board and physical board before service commissioning.
Prerequisite
l The logical board must be created and the physical board must be installed.
l You must be an NM user with "NE monitor" authority or higher.

When the type of the logical board is inconsistent with the type of the physical board, the board
reports the WRG_BD_TYPE alarm. The alarm, however, does not necessarily mean that the
type inconsistency between the logical board and physical board. The alarm may also be
generated when the board software is inconsistent with the hardware or when the board is faulty.
Procedure
Step 1 Click the major alarm indicator (orange) on the right upper part of the U2000 interface
to browse the current major alarms in the entire network.
NOTE
The number inside the indicator indicates the number of the current major alarms in the entire network.
When the indicator is circled with a line, as shown in , it indicates that there are major alarms
to be confirmed.
Step 2 Check whether the WRG_BD_TYPE alarm exists in the alarm list. If the WRG_BD_TYPE
alarm is not found, it indicates that the type of the logical board is consistent with the type of
the physical board. If the WRG_BD_TYPE alarm is found, it indicates that the type of the logical
board may be inconsistent with the type of the physical board. Then, perform the following steps.
Step 3 Double-click the ONE icon to display the NE panel on the Main Topology. Select the NE where
the WRG_BD_TYPE alarm is reported from the NE list on the left side. Check whether the type
of the logical board is consistent with the type of the physical board. If the type of the logical
board is inconsistent with the type of the physical board, check whether the logical board or the
physical board is configured incorrectly according to the configuration requirements.
l If the logical board is configured incorrectly, reconfigure the logical board on the U2000.
l If the physical board is of a incorrect type, insert a physical board of the correct type.
Step 4 If the alarm persists when the logical board and the physical board are of the same type, check
whether the board software version matches the hardware version. If the board software version
mismatches the hardware version, reload the board software or use a board with the correct
software version to replace the board.
Step 5 If the alarm persists when the board software version matches the hardware version, it indicates
that the board may be faulty. Replace the board.
----End
5.1.4 Setting DCC Mode

Before the ASON software is started, query the DCC working mode of the NE, and re-set the
DCC working mode.
Context
Only one mode is available for the SCC board of the OptiX OSN 8800 to allocate DCC resources,
as shown in Table 5-1. This mode supports the D1-D3 and D4-D12 channels.

Table 5-1 DCC Resource Allocation of the OptiX OSN 8800
SCC board 51SCC/52SCC board

DCC resource
Channel type Supporting six channel types: D1-D3, D4-D12, GCC0, GCC12_9,
GCC12_18, GCCM_24 and RES_ODU.
Worki Mode 1 l 3 bytes (D1-D3, GCC0) channel : 150

ng l 9 bytes (D4-D12, GCC12_9, RES_ODU) channel : 150
mode
l 18 bytes (GCC12_18) channel : 100
l 24 bytes (GCCM_24) channel : 100
The SDH signal uses the D1-D3 bytes as physical transmission channels.
The transmission rate of each D byte is 64 kbit/s. The OTN signal uses
the GCC0, GCC12_9, GCC12_18 and GCCM_24 channel as
transmission channels. The transmission rate of each GCC0 channel of
OTU boards at different rates is 64 kbit/s. The transmission rate of each
GCC12_9 channel is 576 kbit/s. The transmission rate of each
GCC12_18 channel is 1152 kbit/s. The transmission rate of each
GCCM_24 channel is 1536 kbit/s.
The ASON information uses the D4-D12 and RES_ODU bytes as
physical transmission channels. The transmission rate of each D byte is
64 kbit/s.
Default protocol D1-D3/GCC0/GCC12_9/ D4-D12/RES_ODU/GCCM_24

type GCC12_18
HWECC IP
Default mode Mode 1
Procedure
Step 1 Right-click the NE icon in the Main Topology and choose NE Explorer.
Step 2 Choose Communication > DCC Management from the Function Tree.
Step 3 Click the DCC Rate Configuration option button. Click Create, Set the Port, Channel
Type, Protocol Type and DCN Domain.
Step 4 Click Apply.

NOTE
When the setting is complete, the SCC will restart.
----End
5.1.5 Setting the Node ID

The node ID, NE ID and IP address of the NE are independent from each other. In an ASON
network, each ASON NE is assigned with a unique node ID within a network. The node ID must
be specified during the network planning.

Prerequisite
l No ASON services exist on the NE.
The node ID must meet the following requirements:
l Node IDs cannot be duplicate in the same ASON domain.
l The node ID of an NE cannot be in the same network segment as the IP address of the NE.
l The node ID, NE ID and IP address of the NE are independent from each other.
l The format of a node ID is the same as that of an IP address. The node ID cannot be 0.0.0.0,
1.2.3.4 or 255.255.255.255. For details on the range of the node ID, refer to 3.3.4 Planning
the Node ID.
l The node ID must be set before an ASON feature is enabled. If the node ID is set after an
ASON feature is enabled, a warm reset is performed automatically on the NE.
CAUTION
When a delivered network is running, do not change the node ID. To change the node ID, contact
Procedure
Function Tree. Click the Node ID Management tab.
Step 2 Click Query to view the current node ID of the NE.
Step 3 Double-click the Node ID field to enter a node ID for the NE.
NOTE
You can also set the NE node ID in ASON Topology Management.
----End
5.1.6 Enabling the ASON Feature

The NE obtains the ASON feature after this feature is enabled. The ASON feature is disabled
by default during delivery.
Prerequisite

l The NE software must contain the ASON feature and must be successfully enabled.
l The node ID must be set.
l The NE must be in the running state.
l The NE must be created on the U2000 and the NE data must be already uploaded.
l A unique node ID is allocated to each ASON NE to identify the NE in the ASON network.
In the same ASON network, node IDs cannot be duplicate or in the same network segment
as the IP address of the corresponding NE. The format of a node ID is the same as that of
an IP address. The node ID cannot be 0.0.0.0, 1.2.3.4 or 255.255.255.255. Properly set the
NE node ID before you enable the ASON feature of the NE.
l The ASON feature can be enabled after the equipment commissioning is complete.
l Add the correct logical boards on the NE before enabling the ASON features.
l Set the correct DCC working mode for the NE before enabling the ASON features.
l After you enable the ASON feature, synchronize the NE data to keep the consistency of
data between the U2000 and the NE. For relevant operations, refer to 5.1.7 Uploading NE
Configuration Data.
l You can disable the ASON feature of an ASON NE according to the project requirement.
After you disable the ASON feature, the NE is possessed of only traditional NE features.
NOTE
To disable the ASON feature, the NE must meet the following requirements:
l The NE must be in the running state and does not have any ASON cross-connection or ASON
service residual
l The fiber between the local NE and the adjacent node must not carry ASON services.
l The ASON Clock is disabled for the NE.
Procedure
Function Tree.
Step 2 Click Query to view the current enabling status of the ASON feature.
Step 3 Set ASON Feature to Enabled.
NOTE
Set the ASON Feature to Disabled to disable the ASON feature.
After you disable the ASON feature, upload the NE data to keep the consistency of data between
the U2000 and the NE. For relevant operations, refer to 5.1.7 Uploading NE Configuration
Data.
----End

5.1.7 Uploading NE Configuration Data

During equipment commissioning, NE data exists on the U2000. After the ASON feature of the
ASON NE is enabled, the NE cannot be initialized and data cannot be downloaded to the NE.
After the ASON feature of the ASON NE is enabled or disabled, data of the NE need be uploaded
to the U2000 to ensure that the data on the U2000 is consistent with that on the NE.
Prerequisite
l The NE must be created successfully.The NE must be in running state.
l The NE commissioning and system commissioning are complete.
Procedure
Step 1 Choose Configuration > Configuration Data Management from the Main Menu.
Step 2 Select one or more NEs in the lower-left pane, and click .
Step 3 Select one or more NEs in the Configuration Data Management List, and click Upload.
Step 4 In the Confirm dialog box, click OK to start the upload.
Step 5 In the Operation Result dialog box, click Close.
----End
5.1.8 Creating Domains for an ASON Network

The U2000 manages an ASON network based on ASON domains. Usually, ASON domains are
automatically created. If for some reason, there are NEs that fail to be synchronized to the ASON
domain during the NE upload, you can create an ASON domain and assign the ASON NEs that
belong to the same ASON network to the ASON domain.
Prerequisite
l The ASON NE must be configured and does not belong to any domain.
l An ASON domain is an ASON network composed of interconnected ASON NEs.
l The first ASON NE created on the U2000 is automatically assigned to the default domain.
Procedure
Step 1 Choose Service > SDH ASON > ASON Topology Management from the Main Menu.
Step 2 ASON NEs that do not belong to any domain are displayed under root of the Object Tree. Right-
click an NE and choose Create Domain.
Step 3 In the Domain Attributes dialog box, enter the Current Name and select the Primary NE.

Step 4 Click OK. The domain is successfully created.
----End
5.1.9 Synchronizing ASON NEs

By communicating with the primary NE, the U2000 is kept synchronous with an ASON network
and automatically discovers other ASON NEs in the network.
Prerequisite
l The primary NE must exist.
l 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.
l If the node ID of an NE is modified manually, you need to re-synchronize the ASON
network topology on the U2000.
Procedure
Step 1 Choose Service > SDH ASON > ASON Topology Management from the Main Menu. Click
the ASON NE tab.
Step 3 Click Synchronize NE. The U2000 searches for the NEs in the ASON domain.
If an ASON NE that is not created on U2000 is detected, add it to the NE to Be Created tab.
Step 4 If you want to create a detected NE on the U2000 click in the Creation Flag field. Enter the
user name and password.

NOTE
l If the U2000 uses the same user name 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 name and password.
l If you want to upload the NE data after creating the NE, check the Upload after created check box.
Step 5 Click Apply. The Operation Result dialog box is displayed. Click Close. The Confirm dialog
box is displayed.
Step 6 Click OK. A progress bar is displayed, showing the uploading progress.
----End
5.1.10 Setting the Primary NE or Secondary NE

In an ASON network, each ASON NE is capable of obtaining the networkwide topology
information. The primary NE is the ASON NE that represents the ASON to communicate with
the U2000 It obtains the information of the ASON control plane and reports ASON events to
the U2000 To improve the reliability, another NE can be set as the standby of the primary NE.
If the primary NE fails, the secondary NE takes over to communicate with the U2000 Usually,
you can select the GNE as the primary NE or as the secondary NE to avoid waste of the ECC
bandwidth.
Prerequisite
l An ASON NE must be created and its data must be uploaded to the U2000
The U2000 only needs to communicate with one NE in an ASON network. This NE is called
the communication NE. It is the NE that represents the ASON network to communicate with
the U2000 Usually, the communication NE is the primary NE. When the primary NE fails, the
secondary NE becomes the communication NE. If both the primary and secondary NEs fail, the
system automatically selects an ASON NE as the communication NE. You can set only one
primary NE and one secondary NE in an ASON domain.
Procedure
Step 1 Choose Service > SDH ASON > ASON Topology Management from the Main Menu. Click
the ASON NE tab.
Step 3 Select an NE and set it to Primary in the Node Type column.
Step 4 Optional: Select an NE and set it to Secondary in the Node Type column.

Step 5 Click Apply to apply the settings.
----End
5.1.11 Synchronizing Control Links Networkwide

By synchronizing the control links, the control link data on the U2000 is kept consistent with
that on the NEs of the ASON network.
Prerequisite
Procedure
Step 1 Choose Service > SDH ASON > Control Link Management from the Main Menu.
Step 2 Click Filter. In the Filter dialog box displayed, choose Domain and Source/Sink NE of the
control links that need to be synchronized, and then click Filter.

NOTE
After the synchronization is complete, all the information about the control links are displayed in the list.
----End
5.1.12 Synchronizing TE Links

You can synchronize the TE links. The U2000 queries link resources in the network by the
primary NE to keep the TE link data on the U2000 consistent with the ASON data.

Prerequisite
In current ASON software versions, one TE link contains only one component link. In this sense,
to synchronize a TE link is the same as to synchronize a component link.
Procedure
Step 1 Choose Service > SDH ASON > TE Link Management from the Main Menu.
NOTE
----End

the foundation of network routing computation. The OptiX GCP V100R003 supports the auto-
discovery of ASON NEs, TE links, control links and inter-NE fibers. The internal fibers of an
NE, however, need be manually created.An ASON topology consists of ASON NEs, fibers and
TE Links. Resources refer to VC4s on TE links.
5.2.1 Testing Topology Auto-Discovery

The topology auto-discovery is a major function of the ASON network and is the foundation of
network route computation.
Prerequisite
The ASON feature of the ASON NEs is enabled.
The fibers are correctly connected.
Specifications
Any change of the ASON network topology can be viewed in real time in the TE Link
Management window.
Procedure
Step 1 Select Configuration > SDH ASON > ASON Topology Management from the Main Menu
and click the domain to query. Click Refresh and all ASON NEs in the domain are displayed.
Step 2 Select Configuration > SDH ASON > TE Link Management from the Main Menu. Click
Synchronize, and the following networking diagram is displayed.

Step 3 Shut down all the lasers between NE1 and NE2. Select Configuration > SDH ASON > TE
Link Management from the Main Menu and click Synchronize. The TE link between NE1 and
NE2 is deleted from the TE Link Management window.
Step 4 Open the lasers again. Select Configuration > SDH ASON > TE Link Management from the
Main Menu and click Synchronize. The TE link between NE1 and NE2 is displayed in the TE
Link Management window.
Step 5 Turn off the power of NE2. Select Configuration > SDH ASON > TE Link Management
from the Main Menu and click Synchronize. All TE Links connecting NE2 are deleted from
the TE Link Management window.
Step 6 Turn on the power of NE2 again and wait for NE2 to start. Select Configuration > SDH
ASON > TE Link Management from the Main Menu and click Synchronize. All TE links
connecting NE2 are displayed in the TE Link Management.
----End
5.2.2 Testing Resource Auto-Discovery

Resource auto-discovery is a major function of the ASON network.
Prerequisite
The ASON feature of the ASON NEs is enabled.
The fibers are correctly connected.
Specifications
In TE Link Management window, TE links are displayed.
Procedure
Step 1 Select Configuration > SDH ASON > TE Link Management from the Main Menu and the
TE link resources of the ASON are displayed.

Step 2 Select Configuration > SDH ASON > Component Link Management from the Main Menu
and the component link resources of the ASON are displayed. One TE link may consist of several
component links.
Step 3 Create a VC4 silver trail from NE1 to NE3.
Step 4 Select Configuration > SDH ASON > TE Link Management from the Main Menu and a VC4
bandwidth is reduced from the available non-protection bandwidth of the TE Link between
NE1 and NE3.
Step 5 Delete the silver trail, and select Configuration > SDH ASON > TE Link Management from
the Main Menu. The VC4 bandwidth is added to the available non-protection bandwidth of
the TE Link between NE1 and NE3.
----End
5.3 Testing the ASON Services

The ASON network can provide multiple ASON services. Each ASON service has the different
5.3.1 Testing Permanent 1+1 Diamond Services

For permanent 1+1 diamond services, the rerouting can be triggered when one LSP is interrupted.
Prerequisite
l There should be no alarms, such as R_LOS, R_LOF, MS_AIS, MS_RDI, B2_SD,
B2_EXC, AU_AIS, B3_EXC and B3_SD that may trigger rerouting in the ASON.
l There should be no alarms, such as R_LOS, AU_LOP, TU_LOP, MS_AIS, AU_AIS,
TU_AIS, HP_UNEQ, HP_TIM, B2_EXC, B2_SD, B3_EXC and B3_SD that may cause
SNCP switching in the ASON.
Specifications
l The switching time is less than 50 ms.
l The rerouting time is expressed in seconds.
Procedure
Step 1 Connect the SDH analyzer to interface 1 of the SLH41 board of NE1, and loopback interface 1
of the SLH41 board of NE3. When performing the loopback, add proper optical attenuators.
Step 2 Create a diamond service. Its working trail is NE1->NE3, and the protection trail is NE1->NE4-
>NE3. The source port is NE1-22-SLH41-1, and the sink port is NE3-22-SLH41-1.
NOTE
Use route that constraints to set the working and protection trails. The working trail is constrained by
Compulsory Links and the protection trail by the Compulsory Node (NE4).

Step 3 Shut down all the lasers between NE1 and NE3 to switch the working trail to NE1->NE4->NE3
and the protection trail to NE1->NE2->NE3. Observe the SDH analyzer to check whether the
switching time is less than 50 ms.
Step 4 Shut down the laser in NE2->NE3 direction. The protection trail reroutes to "NE1->NE2->NE4-
>NE3". At that time parts of the protection trail and the working trail are the same. Query the
service attributes at that time, the detailed information of the SLA compliance is link joint.
NOTE
When you check the service attributes, the SLA compliance is displayed as node joint when the following
conditions are true.
l The working and the protection trails share one or more intermediate nodes.
l The working and the protection trails do not share any links.
Step 5 Open all the lasers between NE2 and NE3.
Step 6 Shut down all the lasers between NE3 and NE4. The network triggers rerouting and the service
is switched to NE1-> NE4->NE2->NE3, but the protection trail is NE1-> NE2->NE3. Observe
the SDH analyzer to check whether the rerouting time is expressed in seconds.
Step 7 Turn on all the lasers, and delete the diamond service.
----End
5.3.2 Testing Rerouting 1+1 Diamond Services

For rerouting 1+1 diamond services, the rerouting can be triggered only when both LSPs are
interrupted.
Prerequisite
Specifications
l The switching time is less than 50 ms.
l The rerouting time is expressed in seconds.
Procedure
>NE3. The source port is NE1-22-SLH41-1, and the sink port is NE3-22-SLH41-1.

NOTE
l During service creation, set the Trigger Condition to Reroute when both trails fail in the Rerouting
Attributes interface.
l Use route that constraints to set the working and protection trails. The working trail is constrained by
Step 3 Shut down all the lasers between NE1 and NE3. The working trail switches to "NE1->NE4-
>NE3". Observe the SDH analyzer to check whether the switching time is less than 50 ms.
Step 4 Shut down all the lasers between NE3 and NE4. The working reroutes to "NE1->NE2->NE3".
Observe the SDH analyzer to check whether the rerouting time is expressed in seconds.
----End
5.3.3 Testing Non-rerouting 1+1 Diamond Services

For non-rerouting diamond services, the rerouting would not be triggered no matter the LSP is
interrupted or not.
Prerequisite
Specifications
The switching time is less than 50 ms.
Procedure
>NE3. The source port is NE1-22-SLH41-1 and the sink port is E3-22-SLH41-1.
NOTE
l During service creation, set the Trigger Condition to Never reroute in the Rerouting Attributes
interface.
l Use route that constraints to set the working and protection trails. The working trail is constrained by
Step 3 Shut down all the lasers between NE1 and NE3. The working trail switches to the "NE1->NE4-
>NE3". Observe the SDH analyzer to check whether the switching time is less than 50 ms.
Step 4 Shut down all the lasers between NE3 and NE4. The service is not rerouted. Observe the SDH
analyzer. The service is interrupted.

----End
5.3.4 Testing Gold Services

As gold services require working resource of TE links, create an MSP ring, 1:1 linear MSP, 1:N
linear MSP or 1+1 linear MSP before starting the test.
Prerequisite
An MSP ring subnet should be present within the ASON subnet and should work normally
without switching.
No alarms such as R_LOS, R_LOF, MS_AIS, MS_RDI, B2_SD, B2_EXC, AU_AIS, B3_EXC
and B3_SD are generated in an ASON subnet to trigger rerouting.
Sufficient network resources must be available.
Networking Diagram
As shown in Figure 5-3, create an STM-16 MSP ring composed of NE1, NE2, NE3, and NE4.
Figure 5-3 An MSP ring for gold services
NE1
MSP
NE2 NE4
NE3
Specifications
l The switching time is less than 50ms.
l The rerouting time is less than 2s.
Procedure
Step 1 Connect the SDH analyzer to interface 1 of the SLQ1 board of NE1 and loopback interface 1 of
the SLQ1 board of NE3 (add a proper attenuator).
Step 2 Create a gold service whose working trail is NE1->NE4->NE3. The source port is NE1-13-
SLQ1-1 and the sink port is NE3-13-SLQ1-1.

Step 3 Shut down all the lasers between NE1 and NE4 to perform MSP switching, and the working
trail is switched to NE1->NE2->NE3->NE4->NE3. Look at the SDH analyzer to check whether
the switching time is less than 50ms.
Step 4 Shut down all the lasers between NE1 and NE2. Then the ASON reroutes the working trail to
NE1->NE3. Look at the SDH analyzer to check whether the rerouting time is less than 2s.
Step 5 Turn on all the lasers. After the MS is switched, in ASON Trail Management window, select
the gold service. Click Maintenance and select Optimize. In Optimize window, click Apply.
Then the service is rerouted to MS links.
Step 6 Delete the gold service.
----End
5.3.5 Testing Silver Services

Silver services are also called rerouting services. When an LSP failure occurs, the ASON triggers
rerouting to restore the service. If there are not enough resources, service may be interrupted.
Prerequisite
Specifications
The rerouting time is expressed in seconds.
Procedure
Step 2 Create a silver trail NE1->NE2-> NE3 by using the U2000 The source port is NE1-22-SLH41-1
and the sink port is NE3-22-SLH41-1.
Step 3 Shut down all the lasers between NE1 and NE2 to switch the service to NE1->NE3. Observe
the SDH analyzer to check whether the rerouting time is expressed in seconds.
Step 4 Shut down all the lasers between NE1 and NE3, the service reroutes to NE1->NE4->NE3.
Step 5 Shut down all the lasers between NE4 and NE3, the service reroutes to NE1->NE4->NE2->NE3.

Step 6 Connect all removed fibers, and delete the silver trail.
----End
5.3.6 Testing Copper Services

The rerouting would not be triggered if the copper services are interrupted.
Prerequisite
Specifications
None
Procedure
Step 2 Create a copper service NE1->NE2-> NE3 by using the U2000 The source port is NE1-22-
SLH41-1, and the sink port is NE3-22-SLH41-1.
Step 3 Shut down all the lasers between NE1 and NE2, and the trail breaks.
Step 4 Turn on all the lasers, and delete the copper service.
----End
5.3.7 Testing Iron Services

The preemption and restoration of the iron service is tested.
Prerequisite
An MSP ring subnet should be present within the ASON subnet and should work normally
without switching.

No alarms such as R_LOS, R_LOF, MS_AIS, MS_RDI, B2_SD, B2_EXC, AU_AIS, B3_EXC
and B3_SD are generated in an ASON subnet to trigger rerouting.
Sufficient network resources must be available.
Networking Diagram
Since iron services require protection resource of TE links, an MSP ring or linear MSP needs to
be created before testing iron services. Create an STM-16 MSP ring composed of NE1, NE2,
NE3 and NE4 as shown in Figure 5-4.
Figure 5-4 An MSP ring for iron services
NE1
MSP
NE2 NE4
NE3
Specifications
Iron service is resumed after the reverting of the multiplex section.
Procedure
Step 1 Connect the SDH analyzer to interface 1 of the SLH41 board of NE1 and loop back interface 1
of the SLH41 board of NE3 (add a proper attenuator).
Step 2 Create an Iron service NE1->NE4-> NE3 through the U2000.
Step 3 Shut down all the lasers between NE1 and NE2 perform MSP switching and the iron trail breaks.
Step 4 Turn on all the lasers. The iron service is restored after the MS switching is recovered.
Step 5 Delete the iron service.
----End
5.3.8 Test Gold Tunnels

Gold tunnels require the working resources of TE links. Thus, the MSP ring or 1:1 linear MSP
should be created before testing gold tunnels.
Prerequisite
l An MSP ring subnet should be present within the ASON subnet and should work normally
without switching.

l No alarms such as R_LOS, R_LOF, MS_AIS, MS_RDI, B2_SD, B2_EXC, AU_AIS,

B3_EXC and B3_SD are generated in an ASON subnet to trigger rerouting.
l Sufficient network resources must be available.
Networking Diagram
See Figure 5-5, an STM-16 MS-shared ring that involves NE1, NE2, NE3 and NE4 of OSN
8800 ASON NEs and NE5 and NE6 of OSN 3500 ASON NEs are to be created.
Figure 5-5 MSP ring for gold tunnels
VC12
NE5
Gold Tunnels
NE1
MSP
NE2 NE4
NE3
:OSN 8800 ASON NE
NE6
VC12 :OSN 3500 ASON NE
Specifications
The protection switching time should be less than 50ms and the service rerouting time should
be less than 2s.
Procedure
Step 1 Use an E1 cable to connect the SDH analyzer to port 1 of the interface board for the PQ1 of
NE5. Perform a loopback at port 1 of the interface board for the PQ1 of NE6.
Step 2 Create a gold tunnel, whose working trail is NE5->NE1->NE4->NE3->NE6.
Step 3 Create a VC-12 service from NE5-2-PQ1-1 to NE6-2-PQ1-1 on the gold tunnel.
Step 4 Shut down the laser of NE1 that is connected with NE4. Perform MS switching and switch the
working trail to NE5->NE1->NE2->NE3->NE6->NE3->NE4->NE3. Check the SDH analyzer,
which shows that the switching time is less than 50ms.

Step 5 Shut down the laser of NE1 that is connected with NE2. The ASON subnet then performs
computation of service routes. The working trail changes to NE5->NE1->NE3->NE6. Check
the SDH analyzer, which shows that the rerouting time is expressed in seconds.
Step 6 Open all the lasers that are shut down. Delete the gold tunnel and VC-12 service.
----End
5.3.9 Testing Silver Tunnels

The silver tunnel can implement the silver-level protection for the lower order services.
Prerequisite
There is no alarm that may trigger rerouting in the ASON, such as R_LOS, R_LOF, MS_AIS,
MS_RDI, B2_SD, B2_EXC, AU_AIS, B3_EXC and B3_SD.
There are enough network resources.
Specifications
The service rerouting time should be less than 2s.
Procedure
Step 2 Create a silver tunnel, whose working trail is NE5->NE1->NE2->NE3->NE6.
Step 3 Create a VC-12 service from E5-2-PQ1-1 to NE6-2-PQ1-1 on the silver tunnel.
Step 4 Shut down the laser of NE1 that is connected with NE2. The service reroutes to NE5->NE1-
>NE3->NE6. Check the SDH analyzer, which shows that the rerouting time is expressed in
seconds.
Step 5 Shut down the laser of NE1 that is connected with NE3. The service reroutes to NE5->NE1-
>NE4->NE3->NE6. Check the SDH analyzer, which shows that the rerouting time is expressed
in seconds.
Step 6 Shut down the laser of NE4 in connection to NE3. The service reroutes to NE5->NE1->NE4-
>NE2->NE3->NE6. Check the SDH analyzer, which shows that the rerouting time is expressed
in seconds.
Step 7 Open the lasers that are shut down. Delete the silver tunnel and VC-12 service.
----End
5.3.10 Testing Copper Tunnels

The copper tunnel does not provide protection for the lower order services. If a fiber cut occurs,
the services in the copper tunnel are interrupted.
Prerequisite
There is no alarm that may trigger rerouting in the ASON, such as R_LOS, R_LOF, MS_AIS,
MS_RDI, B2_SD, B2_EXC, AU_AIS, B3_EXC and B3_SD.

There are enough network resources.
Specifications
None
Procedure
Step 2 Create a copper tunnel, whose working trail is NE5->NE1->NE2->NE3->NE6.
Step 3 Create a VC-12 service from NE5-2-PQ1-1 to NE6-2-PQ1-1 on the tunnel service.
Step 4 Shut down the laser of NE1 in connection to NE2. The service is interrupted.
Step 5 Open the lasers that are shut down. Delete the copper tunnel and VC-12 service.
----End
5.4 Testing Batch Rerouting

This section describes the method to test the performance of rerouting 16 silver services.
Prerequisite
l There is no alarm that may trigger rerouting in the ASON, such as R_LOS, R_LOF,
MS_AIS, MS_RDI, B2_SD, B2_EXC, AU_AIS, B3_EXC and B3_SD.
l There are enough network resources.
Figure 5-6is an STM-64 mesh network composed of four OptiX OSN 8800: NE1, NE2, NE3,
and NE4. NE1 is the gateway NE.
Figure 5-6 Networking diagram
NE1
24 26
26 25 25
24 24 NE4
NE2
25 24 26
26 25
NE3 : ASON NE
24: Slot 24
25: Slot 25
26: Slot 26

Figure 5-7 shows the board configuration of NE1, NE2, NE3, and NE4.
FAN
A
EF U
I1
S
S S S
L S S S F F F
L L L
H C C C I I I
6 6 6
4 C 2 1 U U U
4 4 4
1
X X
C C
M H
M
T T N N S N
R
O D S S C S
8
M X 2 2 C 2
V
FAN
Specifications
All services are successfully rerouted and the rerouting time is less than 2sexpressed in
seconds.
Procedure
Step 1 Connect the SDH analyzer to the No.1 optical interface of the SLH41 board of NE1. Perform a
loopback at the No.1 optical interface of the SLH41 of NE3. When performing the loopback,
add proper optical attenuators.
Step 2 Use the U2000 to create 16 silver trails from NE1 to NE3, which should also involve NE4. or
one trail, the source port is NE1-22-SLH41-1 and the sink port is NE3-22-SLH41-1. Set the
priority of this service to low, and set the priorities of the other 15 services to high.
Step 3 Shut down the laser of NE1 that is connected with NE4. Some trails reroute to NE1->NE3 and
the trails reroute to NE1->NE2->NE3. No services are interrupted. Observe the SDH analyzer
to check whether the rerouting time is expressed in seconds.
Step 4 Open the laser that is shut down and delete all the services.
----End

ASON User Guide 6 Configuring OTN ASON Networks
6 Configuring OTN ASON Networks
About This Chapter
You can configure an ASON network using the U2000.
6.1 Creating WDM ASON Trails

The trail levels that a WDM ASON trail supports are as follows: diamond, silver and copper. A
label switched path (LSP) is a trail passed through by an ASON service. It is also called an
ASON trail.
6.2 Modifying the Attributes of ASON WDM Trails
As an ASON network is changing, you need to modify the attributes of ASON WDM Trails in
the network according to different ASON features. This facilitates the configuration,
management and maintenance of the ASON network.
6.3 Modifying the Route of an ASON Service
As an ASON network is changing, you need to modify the route of an ASON service in the
network according to different situations. This facilitates the configuration, management and
maintenance of the ASON network.
6.4 Converting ASON Services
An ASON network supports the convertion between traditional trails and ASON trails and the
convertion between ASON trails with different level.
6.5 Managing the OVPN Customers and OVPN Services
In the case of the OVPN, an ASON network is shared by multiple operators. When multiple
operators need to share an ASON network, you can allocate different TE link resources for each
operator. Each operator can use and manage its own TE link resources and ASON services.
6.6 Creating Services Between an ASON NE and a Traditional NE
A network can consist of ASON NEs and traditional NEs. This implements end-to-end service
configuration and management.
6.7 Managing Services Between a WDM ASON NE and a Traditional WDM NE
A network can consist of WDM ASON NEs and traditional WDM NEs. This implements end-
to-end service configuration and management.
6.8 Managing Control Plane Alarms and Performance Events

Users can suppress the control plane alarms, monitor the control plane performance, set the auto-
report status of the control plane performance, and set the control plane performance threshold
based on actual requirements.

6.1 Creating WDM ASON Trails

The trail levels that a WDM ASON trail supports are as follows: diamond, silver and copper. A
label switched path (LSP) is a trail passed through by an ASON service. It is also called an
ASON trail.
The U2000 provides the end-to-end WDM ASON trail management feature and supports
services at three classes of service (CoS) as follows:
l Diamond WDM ASON trail: provides 1+1 protection and rerouting ability.
l Silver WDM ASON trail: provides rerouting services and re-calculates a route in the real
time.
l Copper WDM ASON trail: does not provide protection in the case of a fault.
The corresponding server-layer trails must be available for configuring the end-to-end ASON
services. The following table lists the requirements for creating various levels of ASON services.
Table 6-1 Requirements for creating various levels of ASON services.
ASON Requirement for Service Creation

Service
Level
OCh level Directly create an end-to-end ASON service of the OCh level.
ODU2 level Create an end-to-end ASON service of the OCh level, and then create end-
to-end ASON service of the ODU2 level.
ODU1 level Create an end-to-end ASON service of the OCh level, create an end-to-end
ASON service of the ODU1 level.
ODU0 level Create an end-to-end ASON service of the OCh level, create an end-to-end
ASON service of the ODU1 level, and then create an end-to-end ASON
service of the ODU0 level.
6.1.1 Creating an Optical-Layer Silver WDM ASON OCh Trail

You can create a WDM ASON OCh trail with the silver-class protection. If a silver WDM ASON
OCh trail fails, the rerouting is periodically initiated until the OCh trail is successfully rerouted.
If the network resource is insufficient, the service may be interrupted. Since the system calculates
the reverting trail for a silver WDM ASON OCh trail in real time, you do not need to reserve
resources for it. In this sense, the silver services have high bandwidth utilization.
Prerequisite

l The wavelength of the OTU board on the ASON trail has been set according to the
requirements of actual services. In this example, the wavelength of the LSX board should
be set.
l The working band parity of the mux/demux board on the ASON trail has been set.
l The U2000 must have synchronized network-wide TE links and have sufficient TE link
resources.
l WDM ASON Trail is classified into WDM ASON OCh Trail, WDM ASON ODU3
Trail, WDM ASON ODU2 Trail, WDM ASON ODU1 Trail, WDM ASON ODU0 Trail.
l Silver services are also called rerouting services. When an LSP failure, the ASON triggers
rerouting to restore the service.
NOTE
The system supports an optical-layer ASON service traversing an electrical regeneration NE. The method
of configuring such an ASON service is the same as that of configuring an ASON service that does not
traverse an electrical regeneration NE. When configuring such an ASON service, however, you need to
set the working mode of the regeneration board to Optical Relay Mode.
The system supports an electrical-layer ASON service traversing an electrical regeneration NE. The method
traverse an electrical regeneration NE.
Service Requirement
As shown in Figure 6-1, a silver service need be configured between NE1 and NE3, and the
service must go through NE2.
Figure 6-1 Silver WDM ASON OCh Trail requirement

NE1
LSP
NE2 NE4
: ASON NE
NE3 : LSP
Board Configuration
In the case of the OptiX OSN 8800, Figure 6-2 shows the board configuration of NE1 and NE3.

Figure 6-2 Board configuration for NE1 and NE3
Slave Subrack 1 FAN

A S S
EF U T T
EFI2 PIU PIU X G G PIU PIU STI ATE
I1
R W W R
M S S M
U D D U
2 2 2 2 2 2 2 2 C 2 2 2 2 2 2 2 X
9 9 9 9
X X
C C
S S
O W
T T
L T R
F S T TW T T T O O
M S B SM BM40A
Q Q
S I Q
C Q Q Q Q Q D40
U D U D U U
X X
U M
1 M M M M M 1 4
9 9 1 1
FAN
Master Subrack FAN

A S S
EF U T T
EFI2
EFI2 PIU PIU X G G PI
PI
UU PI
PI
UU STI ATE
I1
R W W W R
S
M S S SSM M
M40 D40 C D40 M40
U D M D U
C
9 9D 4 9
4 9
O O OO O O
F S S S S
F O F
B A BB A B
I C C C C
I A I
U U UU U U
U C 2 2 2
U U 1 U
1 1 11 1 1
FAN

Service Planning
To meet the service requirement, you can refer to Table 6-2 to plan a silver WDM ASON OCh
Trail.
Table 6-2 Silver WDM ASON OCh Trail planning

Attribute NE1<->NE3
Source NE NE1
Source board-port 101-LSX-1(IN/OUT)
Source Wavelength 2
Sink NE NE3
Sink board-port 101-LSX-1(IN/OUT)
Sink Wavelength 2
Protection class Silver
Route constraint The service route must pass NE2.
Routing attribute Revertive Mode Non-Revertive
Lockout Unlocked
CrankBack 1
Policy Use existing trails whenever possible
Rerouting Hold-off time 0
Procedure
Step 1 Choose Configuration > WDM ASON > ASON Trail Management from the Main Menu.
Click Cancel in the Filter dialog box.
Step 2 In the displayed WDM ASON Trail Management interface, choose Create > ASON Trail to
display the WDM ASON Trail Creation interface.
Step 3 Enter the basic information of the OCh trail in the Basic Information tab. Click Browse. In the
dialog box displayed, select the slot, port and wavelength of the source and sink.
l Name: NE1-NE3-WDM-ASON-Trail-0005
l Level: OCh
l Class: Silver
l Direction: Bidirectional
l Source: NE1-101-LSX-1(IN/OUT)-2/1529.16/196.050
l Sink: NE3-101-LSX-1(IN/OUT)-2/1529.16/196.050

NOTE
l The protection type must be set after the level and rate parameters.
l The Rate of the Source or Sink must be set with the same service rate.
Step 4 In the Routing Attributes field, enter the rerouting attributes for the OCh trail.
For example, set the attributes as follows:
l Revertive Mode: Non-Revertive
l Lockout: Unlocked
l CrankBack: 1

l Policy: Use existing trails whenever possible

l Rerouting Hold-off time: 0
l Rerouting Triggered by SD: No
NOTE
Policy is classified into four policies: No rerouting constraint, Use existing trails whenever possible,
Do not use existing trails whenever possible and Use simulated section restoration.
Step 5 Optional: Click Pre-Calculate to pre-calculate the route. Click the Pre-Calculate Route tab
to view the pre-calculated route information.
NOTE
Check the Automatic Pre-Calculate and the U2000 issues a command for the NE to perform the automatic
pre-calculation. Every change of the route constraints, the source/sink, or the protection type triggers an
automatic pre-calculation.
Step 6 Configure the explicit trail based on the actual service plan. For details, see Configuring the
Explicit Link.
Step 7 Optional: If you select the Active check box, the created trail is applied to the NE so that the
trail is in the activated state.
Step 8 Optional: Select the Duplicate after created check box to create multiple trails that share the
same source and sink by duplicating the created trail.
Step 9 Optional: Select the Enable Optical Parameter Constraints check box.
Step 10 Verify that the trail information and route constraints are correctly entered. Click Apply.
Step 11 The system prompts that the operation was successful. Click Close in the Operation Result
dialog box.
Step 12 Optional: Choose Configuration > WDM ASON > ASON Trail Management from the Main
Menu to view the created ASON trail.
----End

6.1.2 Creating an Optical-Layer Copper WDM ASON OCh Trail

You can create a WDM ASON OCh trail with the copper-class protection. A copper WDM
ASON OCh trail is an unprotected trail. If it fails, no rerouting is initiated and the service is
interrupted.
Prerequisite
l The wavelength of the OTU board on the ASON trail has been set according to the
requirements of actual services. In this example, the wavelength of the LSX board should
be set.
l The working band parity of the mux/demux board on the ASON trail has been set.
resources.
Trail, WDM ASON ODU2 Trail, WDM ASON ODU1 Trail, WDM ASON ODU0 Trail
l Copper services are also called non-protection services. If an LSP fails, the service do not
reroute and are interrupted.
NOTE
Service Requirement
As shown in Figure 6-3, a copper WDM ASON OCh Trail need be configured between NE1
and NE3, and the service must go through NE2.
Figure 6-3 Copper WDM ASON OCh Trail requirement

NE1
LSP
NE2 NE4
: ASON NE
NE3 : LSP

Board Configuration
In the case of the OptiX OSN 8800, Figure 6-4 shows the board configuration of NE1 and NE3.

Slave Subrack 1 FAN

A S S
EF U T T
I1
R W W R
M S S M
U D D U
2 2 2 2 2 2 2 2 C 2 2 2 2 2 2 2 X
9 9 9 9
X X
C C
S S
O W
T T
L T R
F S T TW T T T O O
M S B SM BM40A
Q Q
S I Q
C Q Q Q Q Q D40
U D U D U U
X X
U M
1 M M M M M 1 4
9 9 1 1
FAN
Master Subrack FAN

A S S
EF U T T
EFI2
PI
UU PI
PI
UU STI ATE
I1
R W W W R
S
M S S SSM M
M40 D40 C D40 M40
U D M D U
C
9 9D 4 9
4 9
O O OO O O
F S S S S
F O F
B A BB A B
I C C C C
I A I
U U UU U U
U C 2 2 2
U U 1 U
1 1 11 1 1
FAN

Service Planning
To meet the service requirement, you can refer to Table 6-3 to plan a copper WDM ASON OCh
trail.
Table 6-3 Copper WDM ASON OCh trail planning

Attribute NE1<->NE3
Source NE NE1
Source board-port 101-LSX-1(IN/OUT)
Source wavelength 2
Sink NE NE3
Sink board-port 101-LSX-1(IN/OUT)
Sink wavelength 2
Protection class Copper
Procedure
Step 3 In the Basic Information field, enter the basic information of the OCh trail. Click Browse. In
the dialog box displayed, select the slot, port, and wavelength of the source and the sink.
For example, set the parameters as follows:
l Level: OCh
l Class: Copper
l Source: NE1-101-LSX-1(IN/OUT)-2/1529.16/196.050
l Sink: NE3-101-LSX-1(IN/OUT)-2/1529.16/196.050

NOTE
NOTE

Explicit Link.
Step 8 Optional: Select the Enable Optical Parameter Constraints check box.
dialog box.
----End
6.1.3 Creating an Electrical-Layer Diamond WDM ASON ODUk

Trail
This section describes how to create a WDM ASON ODUk trail with the diamond-class
protection. According to different rerouting policy, diamond-class WDM ASON trails can be
classified into three types: permanent 1+1 diamond WDM ASON ODUk trail, rerouting 1+1
diamond WDM ASON ODUk trail, non-rerouting diamond WDM ASON ODUk trail, in which
k = 0, 1, 2 or 3. The following descriptions are based on the permanent 1+1 diamond WDM
ASON ODU1 trail.
Prerequisite
l Service Mode has been set for the OTU board or line board on the ASON trail. In this
example, Service Mode is set to ODU1 for the NS2 board. For details on the operations,
see Configuring the Service Mode.
l Board Mode has been set for the line board on the ASON trail. In this example, Board
Mode is set to Line Mode for the NS2 board.
l Some boards (such as the NS3, NS2, NQ2, and ND2 boards) support hybrid transmission
of ODUk ASON services. When using these boards to transmit different ODUk ASON
services, users need to set the Service Mode for service channels on the boards.
The rules of setting service modes for service channels on the boards are given below. For
details on the settings, see Configuring the Service Mode.
– When these boards are used to transmit ODU0 services, Service Mode must be set to
ODU0 for ODU1 service channels and set to ODU1 for ODU2 service channels.
ODU1 for both ODU1 and ODU2 service channels.
ODU2 for ODU2 service channels.
resources with ODU1 payload.

l Diamond services are classified into Permanent 1+1 diamond service, Rerouting 1+1
diamond service and Non-rerouting diamond service.
NOTE
Service Requirement
As shown in Figure 6-5 and Figure 6-6, a permanent 1+1 diamond WDM ASON ODU1 trail
need be configured between NE1 and NE3. The working LSP is required to pass NE2 and the
protection LSP is required to pass NE4.
Figure 6-5 Service Requirements

NE1
Working LSP Protection LSP
NE2 NE4
: ASON NE
NE3
: LSP

Figure 6-6 Diamond WDM ASON ODU1 trail

NE1 NE3
NS2 NS2
ODU1 ODU1
O O O O
TOM XCS D T T D XCS TOM
LP U U U U
LP
1 2 2 2 2
1
O O
D D
ODU1 ODU1
U U
1 O O O O 1
D T T D
U U U U
2 2 2 2
NS2 NS2
ODU1 TE link
ODU1 Trail
Board Configuration
In the case of the OptiX OSN 8800,Figure 6-7 shows the board configuration of NE1 and NE3.

FAN
A S S
EF U T T
I1
N S S S F F F
S C C C I I I
2 C 2 1 U U U
X X
C C
H H
/ /
X X
C C
M M
M
R T T N N S
8 O D S S C
V M X 2 2 C
FAN
NOTE
These boards must be installed on the same subrack.
Service Planning
To meet the previously mentioned service requirement, you can refer to Table 6-4 plan the
diamond WDM ASON ODU1 trail.
Table 6-4 Diamond WDM ASON ODU1 trail planning
Attribute NE1<->NE3
Source NE NE1
Source board-port 22-52NS2-51(ODU1LP1/ODU1LP1)-1
Sink NE NE3
Sink board-port 22-52NS2-51(ODU1LP1/ODU1LP1)-1
Protection class Diamond
Route constraint Working path: NE1-NE2-NE3

Protection path: NE1-NE4-NE3

Attribute NE1<->NE3
Routing Attributes Revertive Mode Non-Revertive
Lockout Unlocked
CrankBack 1
Rerouting Triggered No
by SD
Trigger Condition Reroute when one trail fails
Rerouting Hold-off 0
time
Procedure
Step 3 Enter the basic information of the trail in the Basic Information tab, and click Browse. In the
dialog box displayed, select the slot, port and wavelength for the source and the sink.
l Name: NE1-NE3-ASON-WDM-ODU1-Trail-0005
l Level: ODU1
l Rate: ODU1
l Class: Diamond
l SNCP Type: SNC/N
l OTN Level: PM
l Source: NE1-22-52NS2-51(ODU1LP1/ODU1LP1)-1
l Sink: NE3-22-52NS2-51(ODU1LP1/ODU1LP1)-1
NOTE
When diamond ODUk ASON WDM trails are created, setting the SNC/N(PM) and SNC/S(TCM) modes is
supported.
When k is 0, only the non-intrusive monitoring (SNC/N) is supported. When k is 1, 2 or 3, the sub-layer
monitoring (SNC/S) and non-intrusive monitoring (SNC/N) are supported.
When the SNCP type is set as sub-layer monitoring, the U2000 supports setting TCM layers (TCM1–TCM6).
Traditional services in the SNC/I, SNC/N, and SNC/S modes can be upgraded into diamond ASON services.
After rerouting, the SNC mode of services in the SNC/I and SNC/N(TCM) modes is changed into SNC/N(PM).

NOTE
The protection type must be set after the Level and Rate parameters.
Step 4 In the Routing Attributes field, enter the routing attributes of the trail.
l Lockout: Unlocked
l Priority: High
l CrankBack: 1


l Trigger Condition: Reroute when one trail fails
NOTE
Among the routing attributes, Trigger Condition is a unique feature of diamond services and is classified
into three policies: Reroute when one trail fails, Reroute when both trails fail and Never reroute.
NOTE
Explicit Link.
dialog box.
----End

6.1.4 Creating an Electrical-Layer Silver WDM ASON ODUk Trail

You can create a WDM ASON ODUk trail with the silver-class protection. If a silver WDM
ASON ODUk trail fails, the rerouting is periodically initiated until the ODUk trail is successfully
rerouted. If the network resource is insufficient, the service may be interrupted. Since the system
calculates the reverting trail for a silver WDM ASON ODUk trail in real time, you do not need
to reserve resources for it. In this sense, the silver services have high bandwidth utilization, in
which k = 0, 1, 2 or 3. The following descriptions are based on the silver WDM ASON ODU1
trail.
Prerequisite
l The U2000 must have synchronized the TE links of the entire network and have sufficient
link resources with ODU1 payload.
l Silver services are also called rerouting services. When an LSP failure, the ASON triggers
rerouting to restore the service.
NOTE
Service Requirement
As shown in Figure 6-8 and Figure 6-9, a silver WDM ASON ODU1 trail need be configured
between NE1 and NE3, and the service must pass through NE2.

Figure 6-8 Silver WDM ASON ODU1 Trail requirement

NE1
NE2 NE4
: ASON NE
NE3 : LSP
Figure 6-9 Silver WDM ASON ODU1 trail

NE1 NE3

O O O O O O
D D T T D D
U U U U U U
1 2 2 2 2 1
ODU1 TE link
ODU1 Trail
Board Configuration
In the case of the OptiX OSN 8800, Figure 6-10 shows the board configuration of NE1 and
NE3.

FAN
A S S
EF U T T
I1
N S S S F F F
S C C C I I I
2 C 2 1 U U U
X X
C C
H H
/ /
X X
C C
M M
M
R T T N N S
8 O D S S C
V M X 2 2 C
FAN
NOTE
Service Planning
To meet the service requirement, you can refer to Table 6-5 to plan a silver WDM ASON ODU1
Trail.
Table 6-5 Silver WDM ASON ODU1 Trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3

Attribute NE1<->NE3
Routing attribute Revertive Mode Non-Revertive
Lockout Unlocked
CrankBack 1
Rerouting No
Triggered by SD
Rerouting Hold-off 0
time
Procedure
Step 3 Enter the basic information of the ODU1 trail in the Basic Information tab. Click Browse. In
the dialog box displayed, select the slot, port and wavelength of the source and sink.
l Name: NE1-NE3-ASON-WDM-Trail-0005
l Level: ODU1
l Rate: ODU1
l Class: Silver

NOTE
The protection type must be set after the level and rate parameters.
l Lockout: Unlocked
l Priority: Low

l CrankBack: 1
NOTE
NOTE
Explicit Link.
dialog box.
----End
6.1.5 Creating an Electrical-Layer Copper WDM ASON ODUk Trail

You can create a WDM ASON ODUk trail with the copper-class protection. A copper WDM
ASON ODUk trail is an unprotected trail. If it fails, no rerouting is initiated and the service is

interrupted, in which k = 0, 1, or 2. The following descriptions are based on the copper WDM
ASON ODU1 trail.
Prerequisite
l The U2000 must have synchronized the TE links of the entire network and have sufficient
link resources with ODU1 payload.
Trail, WDM ASON ODU2 Trail, WDM ASON ODU1 Trail, WDM ASON ODU0 Trail
l Copper services are also called non-protection services. If an LSP fails, the service do not
reroute and are interrupted.
NOTE
Service Requirement
As shown in Figure 6-11 and Figure 6-12, a copper WDM ASON ODU1 trail need be
configured between NE1 and NE3, and the service must pass through NE2.

Figure 6-11 Copper service requirements

NE1
NE2 NE4
: ASON NE
NE3 : LSP
Figure 6-12 Copper WDM ASON ODU1 trail

NE1 NE3

O O O O O O
D D T T D D
U U U U U U
1 2 2 2 2 1
ODU1 TE link
ODU1 Trail
Board Configuration
In the case of the OptiX OSN 8800,Figure 6-13 shows the board configuration of NE1 and NE3.

FAN
A S S
EF U T T
I1
N S S S F F F
S C C C I I I
2 C 2 1 U U U
X X
C C
H H
/ /
X X
C C
M M
M
R T T N N S
8 O D S S C
V M X 2 2 C
FAN
NOTE
Service Planning
To meet the service requirement, you can refer to Table 6-6 to plan a copper service.
Table 6-6 Copper WDM ASON ODU1 trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3

Procedure
Step 3 In the Basic Information field, enter the basic information of the ODU1 trail. Click Browse.
In the dialog box displayed, select the slot, port, and wavelength of the source and the sink.
l Name: NE1-NE3-ASON-WDM-Trail-0005
l Level: ODU1
l Rate: ODU1
l Class: Copper

NOTE
Explicit Link.

dialog box.
----End
6.1.6 Creating ASON Trails for Services with Tributary SNCP

Protection
Diamond, silver, and copper ASON trails can be configured for services with tributary SNCP
protection. Users can create such ASON trails on the NMS.
Prerequisite
example, Service Mode is set to ODU2. For details on the operations, see Configuring the
Service Mode.
l Service Type has been set for the OTU board or tributary board on the ASON trail. In this
example, Service Type is set to STM-64 for the TQX board.
l Working Mode has been set for the ports on some OTU boards or tributary boards such
as TOM boards on the ASON trail.
resources with ODU1 payload.
Context
Figure 6-14 shows a typical application of diamond ASON trails for services configured with
tributary SNCP protection at both ends. Users can create electrical-layer ODUk (k = 0, 1, 2, or
3) ASON trails as required.

Figure 6-14 Diamond ASON trails for services with tributary SNCP protection
Tributary Primary
SNCP LSP Tributary
SNCP
T1 N1 N1 T1
STM-16 ASON STM-16/
/STM-64 network STM-64
T2 N2 N2 T2
Tributary Line Secondary

boards XCS Line Tributary
boards LSP XCS
boards boards
Working signals on the primary LSP Working signals on the secondary LSP
Protection signals on the primary LSP Protection signals on the secondary LSP
Figure 6-15 shows a typical application of silver ASON trails for services configured with
tributary SNCP protection at both ends. Users can create electrical-layer ODUk (k = 0, 1, 2, or
3) ASON trails as required.
Figure 6-15 Silver ASON trails for services configured with tributary SNCP protection
Observe the following points when creating ASON trails for services with tributary SNCP
protection:
l Single-ended or dual-ended tributary SNCP protection can be configured. In other words,
tributary SNCP protection can be configured at both ends or only one end of an ASON
trail.
l ASON trails for services with tributary SNCP protection and associated ASON services
cannot be configured at the same time.
l When the source node supports services with tributary SNCP protection but the sink node
does not, users can create ASON trails for services and configure tributary SNCP protection
for the services at the source node.

NOTE
This section describes how to create silver ASON trails for services with tributary SNCP protection. The methods
for creating diamond and copper ASON trails for services with tributary SNCP protection are similar except for
the following differences:
l For a diamond ASON trail, Class must be set to Diamond.
l For a copper ASON trail, Class must be set to Copper.
l For a diamond ASON service, the NMS automatically creates the working and protection ASON trails for
the protection LSP after users manually create working and protection ASON trails for the working LSP.
As shown in Figure 6-16, a silver ODU2 ASON trail for service with tributary SNCP protection
needs to be configured between NE1 and NE3. The ASON trail must traverse NE2.
Figure 6-16 Silver ASON trails for services with tributary SNCP protection
NE1
NE2 NE4
: ASON NE
NE3 : LSP
Board Configurations
Figure 6-17 shows the board configurations of NE1 and NE3, which are OptiX OSN 8800 NEs.

Figure 6-17 Board configurations of NE1 and NE3
Service Planning
Table 6-7 list the requirements on silver ODU2 ASON trails for services with tributary SNCP
protection.
Table 6-7 Requirements on silver ODU2 ASON trails for services with tributary SNCP
protection
Attribute NE1<->NE3
Working Trail Source NE NE1
Source board-port 4-TQX-201(ClientLP1/ClientLP1)-1
Sink NE NE3
Sink board-port 4-TQX-201(ClientLP1/ClientLP1)-1
Protection Path Source NE NE1
Source board-port 5-TQX-201(ClientLP1/ClientLP1)-1
Sink NE NE3
Sink board-port 5-TQX-201(ClientLP1/ClientLP1)-1
Route constraint The service trail must traverse NE2.
Routing Attributes Revertive Mode Non-Revertive

Attribute NE1<->NE3
Lockout Unlocked
Priority 1
CrankBack 1
Trigger Condition Reroute when one trail fails
Procedure
Step 3 Creating the working trail: In Basic Information, set the basic information about the trail, click
Browse and then select the source and sink board IDs, ports, and wavelengths in the displayed
dialog box.
l Level: ODU2
l Rate: ODU2
l Class: Silver
l Source of the working trail: NE1-4-TQX-201(ClientLP1/ClientLP1)-1
l Sink of the working trail: NE3-4-TQX-201(ClientLP1/ClientLP1)-1
l Source of the protection trail: NE1-5-TQX-201(ClientLP1/ClientLP1)-1
l Sink of the protection trail: NE3-5-TQX-201(ClientLP1/ClientLP1)-1

NOTE
l Set the protection type after setting the service level and rate.
Step 4 Creating the protection trail: In SNCP Access, set the basic information about the trail, click
Browse and select the source and sink board IDs, ports, and wavelengths in the displayed dialog
box.

Step 5 Specify the trail rerouting attributes in Routing Attributes.

l Lockout: Unlocked
l Priority: 1
l CrankBack: 1

NOTE
Step 6 Optional: Click Precalculate to precalculate routes. On the Pre-Calculate Route tab page,
view information about the precalculated routes.
NOTE
If the Automatic Pre-Calculate check box is selected, the NMS will instruct the source and sink NEs to
automatically precalculate routes. The NEs will automatically precalculate routes every time a change
occurs in route constraints, sink, source, or protection type.
Explicit Link.
Step 8 Optional: Select the Active check box. When this check box is selected, the NMS will deliver
trail configurations to an NE so that the trail is in Active state immediately after being created.
Step 9 Optional: Select the Duplicate after created check box. Then, users can create multiple trails
with the same source and sink.
Step 10 Verify that the route information and route restriction are correctly set, and then click Apply.
Step 11 In the displayed Operation Result dialog box indicating that the operation was successful, click
Close.
Step 12 Optional: Choose Configuration > WDM ASON > ASON Trail Management from the main
menu to view the newly created ASON trails.
----End
6.1.7 Setting Association of WDM ASON Trails

You can use this function to associate two WDM ASON trails. Two associated WDM ASON
trails should be separated whenever possible during optimization and rerouting. When a WDM
ASON trail is being rerouted or optimized after association, the ASON NE tries to avoid using
the associated WDM ASON trail for the rerouting or optimization, based on the 1+1 route disjoint
policy.

Prerequisite
Context
This function supports setting association of two existing WDM ASON trails. It also supports
creating two associated WDM ASON trails at a time.
Two associated WDM ASON trails need to be disassociated before they can be deleted.
NOTE
Currently, association is supported between silver trails, between copper trails, and between silver and
copper trails.
Procedure
l To create two associated WDM ASON trails, do as follows:
1. Choose Configuration > WDM ASON > ASON Trail Management from the Main
Menu. Perform filter and confirmation.
2. Click Create > Association Trail. The Create Associated ASON WDM Trail user
interface is displayed.
3. Set the basic information of trail 1, including the Name, Level, Class, Rate,
Source, and Sink.
NOTE
l Only the association between routes in silver or copper protection is supported. Hence, set the
protection type of trail 1 and trail 2 to silver or copper. The default protection type is silver.
l In the view on the right, right-click an NE and set route constraints such as explicit node and
excluded node.
4. Repeat Step 3 to set the information of trail 2.

NOTE
The ASON software supports setting association of two WDM ASON trails that have the same
ingress node or different ingress nodes or have the same egress node or different egress nodes.
5. Set the common attributes, including the Lockout, CrankBack, Rerouting
Triggered by SD, Policy and Rerouting Hold-off time.

NOTE
Trigger Condition for Rerouting Associated Route is classified into two policies: Reroute
when one trail fails and Reroute when both trails fail.
6. Select Automatic Pre-Calculation or click Pre-Calculate. After the operation is
successful, close the operation result dialog box.
7. Click Apply. After confirmation, apply the configuration.
l To set association of two existing WDM ASON trails, do as follows:
2. Select a WDM ASON trail from the trail list, right-click, and choose Set Association
Source from the shortcut menu.
3. Select another WDM ASON trail, right-click, and choose Set Association from the
shortcut menu.
4. In the confirmation dialog box, click OK. The operation result dialog box is displayed
indicating that the association is successfully set.
NOTE
To cancel the association of WDM ASON trails, right-click a WDM ASON trail, and choose
Remove Association from the shortcut menu. A dialog box is displayed indicating that the
operation may decrease the protection capability of the service.
5. In the lower left area of the window, click the Associated Route tab to view the two
associated trails.
----End
6.1.8 Creating WDM ASON Trails in Batches

If you want to create a large number of ASON services, you can create them in batches. You
can duplicate the routes during the creation of WDM ASON routes or after the creation.
Prerequisite
l Networkwide TE link synchronization must be complete on the U2000, and TE link
resources are enough.
Service Requirement
See Figure 6-18. The four NEs are all ASON NEs. Three non-revertive silver services at the
rate of 155 Mbit/s are required to be configured between NE1 and NE3.

Figure 6-18 Batch silver service requirement

NE1
NE2 NE4
: ASON NE
NE3 : LSP
Board Configuration
To meet the previously mentioned service requirement, you can configure the boards as shown
in Figure 6-19.

Slave Subrack 1 FAN

A S S
EF U T T
EFI2 PIU
PIU PIU X G PIU PIU STI ATE
I1 G
R W
N N N N N N N N S N
S F
N N N N N N T
M S
Q Q Q Q Q Q Q Q C C
Q Q
I Q Q Q Q Q Q
U D
2 2 2 2 2 2 2 2 C 2
1 2
U 2 2 2 2 2 X
9 9
X X
C C
S S
W
R W O O O
T
L L T T T T T T
F S
M S B B A
Q
O D
I Q Q Q Q Q Q M D40 M40
U D U U U
X
G M M M M M M M
U D
9 9 1 1 1
4
FAN
Master Subrack FAN

A S S
EF U T T
EFI2
EFI2 PIU PIU X G G PIU
PIU PIU
PIU STI ATE
I1
W
R W W W R
S S
M S S S M
M40 D40 C M D40 M40
U D M D U
C D
9 9D 4 9 9
4
O O OO O O O
F L S S S S
F F
B A BB A A B
I D C C C C
I I
U U UU U U U
U M C 2 2 U
2 U
1 1 11 1 1 1
FAN

Service Planning
To meet the service requirement, plan a silver service according to Table 6-8.
Table 6-8 Silver service planning
Attribute NE1<->NE3
Source NE NE1
Source board-port 2-12LDM-1(IN/ 101-12LOG-1(IN/ 102-12LDM-1

OUT) OUT) (IN/OUT)
Source Wavelength 2 42 68
Sink NE NE3
Sink board-port 2-12LDM-1(IN/ 101-12LOG-1(IN/ 102-12LDM-1

OUT) OUT) (IN/OUT)
Sink Wavelength 2 42 68
Routing attribute Lockout Unlocked
CrankBack 1
Rerouting policy Use the existing trail whenever possible
Procedure
l To duplicate trails when a WDM ASON trail is created, do as follows:
Menu. Click Cancel in the Filter dialog box.
2. In the displayed WDM ASON Trail Management interface, choose Create > WDM
Trail to display the WDM ASON Trail Creation interface.
3. Create a WDM ASON trail as required.
4. Check the Duplicate after created check box.
5. Click Apply. The Operation Result dialog box is displayed indicating that the
operation is successful. Click Close.
6. In the Duplicate window, select the source and sink from the available wavelengths,
and click Add.
For example:
– Source: NE621-102-12LDM-1(IN1/OUT1)-68/1555.75/192.700
– Sink: NE623-102-12LDM-1(IN1/OUT1)-68/1555.75/192.700
7. Select the Activate after Duplicate and Duplicate Route Constraint as required.
8. Click OK to confirm after successful operation.
l To duplicate based on an existing WDM ASON trail, do as follows:

2. Select a WDM ASON trail that you want to duplicate, right-click, and choose
Duplicate from the shortcut menu. The Duplicate dialog box is displayed.
3. Select the source and sink from the available wavelengths, and click Add.
4. Select the Activate after Duplicate, Duplicate Route Constraint, and Duplicate
the route as the route constraint as required.
5. Click OK to confirm after successful operation.
----End
6.1.9 Activating WDM ASON Trails

A WDM ASON trail must be activated to apply the configuration on an NE after it is created.
Prerequisite
You must be an NM user with the "NE operator" authority or higher.
Context
NOTE
A WDM ASON trail can be activated when it is created if the Activate check box is selected in the WDM
ASON Trail Creation window.
If the Activate check box is deselected, you can manually activate a WDM ASON trail after you create it.
Procedure
Step 2 Select the required ASON trail in the ASON trail list, right-click it, and then choose Activate
from the shortcut menu.
Step 3 Click OK in the dialog boxes displayed sequentially.
Step 4 The system displays a prompt, indicating that the operation is successful. Click Close. Then, the
activiation status of the selected WDM ASON trail is displayed as Activate.
----End
6.1.10 Deactivating ASON Trail

Deactivating an ASON trail can release the resources that the trail occupies.
Prerequisite

NOTE
You do not need to cancel the association configured before deactivating the associated ASON trail, because
the system automatically cancels the association during the deactivation operation.
If an ASON trail in managed state carries client services, users need to change the ASON trail into
unmanaged state before deactivating the ASON trail. In other words, users first need to delete the client
services on the ASON trail.
Procedure
Step 2 In the list, select the ASON trail to be deactivated. Right-click and choose Deactivate.
NOTE
After you deactivate trails in batches, wait for several minutes (for example, five minutes) before you
perform other operations. It is recommended not to deactivate trails in batches.
Step 3 Click Yes in the confirmation dialog box displayed twice.

NOTE
If the selected trails contain the trails that are managed by WDM trails, the confirmation dialog box is
displayed for the third time. Click Yes. The Operation Result dialog box is displayed indicating that the
operation fails. You can click Detail to view failure causes.
Step 4 After the operation is complete, the system prompts that the operation was successful. Click
Close. The list shows that the ASON trail is in the Inactive state.
----End
6.1.11 Deleting an ASON Trail

The operation of deleting ASON trails removes the trail data from the U2000 and the NE.
Prerequisite
l The ASON trail must be inactive.
NOTE
l Deleting an ASON trail removes the trail data from the U2000 and the NE. Exercise caution when you
perform this operation.
l When deactivating associated ASON trail, do not delete the association first. The system automatically
deletes the association during deactivation.
l When an ASON trail is deleted, the system automatically retains the protection groups preset by a user.
l If WDM-ASON trail management is supported, ASON trails will be automatically managed by the
NMS after end-to-end WDM trails are searched out. If users attempt to delete an ASON trail in managed
state, the system will prompt that client services exist on the ASON trail and subsequently deleting the
ASON trail will fail. Users need to delete the client services on the ASON trail before deleting the
ASON trail.

Procedure
Step 2 Select a deactivated ASON trail from the list, right-click, and choose Delete from the shortcut
menu.
Step 3 Click OK in the confirmation dialog box.
Step 4 After the deletion is complete, a dialog box is displayed indicating that the operation was
successful. Click Close.
----End
6.1.12 Configuring the Explicit Link

When creating ASON WDM trails, you must specify routes and configure the explicit link based
on the actual service plan.
Prerequisite
l All the TE links on the entire network have been synchronized on the NMS and there are
sufficient TE links.
Service Requirement
This section describes how to specify the explicit link NE1 -> NE2 -> NE3 when configuring a
silver WDM ASON ODU1 trail, as shown in Figure 6-20 and Figure 6-21.
Figure 6-20 Silver WDM ASON ODU1 trail requirement

NE1
NE2 NE4
: ASON NE
NE3 : LSP

Figure 6-21 Silver WDM ASON ODU1 trail

NE1 NE3

O O O O O O
D D T T D D
U U U U U U
1 2 2 2 2 1
ODU1 TE link
ODU1 Trail
Board Configuration
For the OptiX OSN 8800, the board configurations for NE1, NE2, and NE3 are shown in Figure
6-22.
Figure 6-22 Board configurations for NE1, NE2, and NE3
FAN
A S S
EF U T T
I1
N S S S F F F
S C C C I I I
2 C 2 1 U U U
X X
C C
H H
/ /
X X
C C
M M
M
R T T N N S
8 O D S S C
V M X 2 2 C
FAN

NOTE
The boards for a same NE must be configured in a same subrack.
Procedure
Step 3 Click Route Restriction. Right-click NE1 in the topology view on the right, and choose Set
Explicit Link > NE1->NE2 > NE1-Shelf1(subrack)-22-52NS2-51(ODU1LP1/
ODU1LP1)-1-->NE2-Shelf1(subrack)-22-52NS2-51(ODU1LP1/ODU1LP1)-1 from the
displayed shortcut menu.
Step 4 Right-click NE2 and choose Set Explicit Link > NE2->NE3 > NE2-Shelf1
(subrack)-22-52NS2-51(ODU1LP1/ODU1LP1)-2-->NE3-Shelf1(subrack)-22-52NS2-51
(ODU1LP1/ODU1LP1)-2 from the displayed shortcut menu.
Step 5 After configuring the explicit link, you can view the related information on the Route
Restriction tab.
NOTE
l To change route constraints, select required route constraints from the Route Restriction pane, right-
click and choose Delete from the shortcut menu to delete the selected route constraints. Then repeat
the preceding steps to configure new route constraints.
l The route constraints listed in Route Restriction follow a specific sequence. For the same route
constraints, the route computation will fail if the sequence is incorrect.
----End

6.2.1 Viewing WDM ASON Trail Attributes

You can view the detailed information about a WDM ASON trail, including the basic attributes,
constraint routes and SLA-compliance.

Prerequisite
l A WDM ASON trail must be created.
Procedure
Step 2 The Filter dialog box is displayed. In this dialog box, click Filter All to display the WDM
ASON Trail Management window.
Step 3 In the trail list, right-click the WDM ASON trail that you want to view and choose Details from
the shortcut menu.
Step 4 In the dialog box displayed, view the basic attributes of the WDM ASON trail.
Step 5 Click the Restrictive Route tab. View the route constraint information about the WDM ASON
trail.
Step 6 Optional: If an associated ASON trail is set for the WDM ASON trail, click the Associated
ASON Trail Attribute tab to view the attributes of the associated WDM ASON trail.
Step 7 Click the SLA-Compliant Details tab to view the details of the SLA-compliance of the WDM
ASON trail.
----End

6.2.2 Setting the Routing Attributes

You can set the routing attributes for an ASON trail, including rerouting revertive mode, WTR
time, rerouting lockout status, revertive lockout, rerouting priority, trigger condition, route
selection policy, times of crankbacks, and rerouting triggered by SD bit error.
Prerequisite
l An ASON NE must be configured and the NE data must be uploaded.
Procedure
Step 2 In the list displayed, select one or more WDM ASON trails, right-click and choose Set Routing
Attributes from the shortcut menu. The Set Routing Attributes dialog box is displayed.
Step 3 In the Set Routing Attributes user interface, set attributes of routing and click OK.
NOTE
When you create a WDM ASON trail, you can set the rerouting attributes. Choose Create > ASON
Trail. In the WDM ASON Trail Creation user interface, click Routing Attributes tab to set the rerouting
attributes.
NOTE
l Currently, you can set trigger conditions of routing for diamond WDM ASON trails only.
Step 4 Click Close in the Operation Result dialog box.
----End
6.2.3 Setting the Scheduled Reversion Time

If the ASON service is rerouted successfully, you can set the scheduled reversion time after the
original trail is restored. Before the scheduled reversion time expires, the service is automatically
returned to the original trail. If you set the scheduled reversion time when the fault in the original
path is not rectified, the service may be interrupted.
Prerequisite
l The ASON service must be rerouted successfully.
l Revertive Mode of the ASON service must be set to Scheduled revertive.

l The NE time must be synchronous with the NM time.
Procedure
Step 3 In Set Routing Attributes, select the Scheduled revertive time check box and set the time
limit within which the service must be returned to the original trail after the original trail is
restored.
NOTE
Scheduled revertive time can be set only when the revertive mode is Scheduled revertive.
Step 4 Set the other items according to the actual planning information. Then, click OK.
Step 5 Then, another dialog box is displayed indicating that the operation is successful. Click Close.
----End
6.2.4 Setting Rerouting Triggered by SD

SD alarms in optical-layer and electrical-layer ASON services of WDM equipment can be used
as rerouting trigger conditions.
Prerequisite
Procedure
Step 3 In Set Routing Attributes, set Rerouting Triggered by SD to Yes.

NOTE
When you create a WDM ASON trail, you can set the rerouting attributes. Choose Create > ASON
Trail. In the WDM ASON Trail Creation user interface, click Routing Attributes tab to set the rerouting
attributes.
Step 5 In the dialog box displayed to indicate that the operation is successful, click Close.
----End
6.2.5 Setting Preset Restoration Trail

You can preset a restoration trail for ASON services. When an ASON WDM trail is being
rerouted, the service has the priority to be restored to the preset trail. If the preset restoration
trail is occupied, the system computes the route again.
Prerequisite
l The ASON WDM trail of the preset restoration trail must have been created.
l The U2000 must have synchronized networkwide TE links and have sufficient TE link
resources.
Currently, the diamond, and silver WDM ASON trails support setting of a preset restoration
trail.
If the resources are sufficient, the system currently supports two preset restoration trails for one
ASON service.
Procedure
Step 2 Select an ASON WDM trail and click Maintenance. Choose Set Preset Restoration Trail from
the drop-down menu.
Step 3 In the displayed Set Preset Restoration Trail Route dialog box, set the information about
Preset Restoration Trail and then click Pre-Calculation to view the relevant information.
Click Apply to apply the setting of the preset restoration trail.

NOTE
If the Automatic Pre-Calculation check box is selected, the U2000 sends a command to ask the NE to
automatically precalculate the route. Any change to the route constraints triggers the automatic
precalculation.
The nodes on the preset restoration trails must be in strict compliance with the node sequences as specified
in the network plan.
The Automatic Pre-Calculation function can calculate a preset restoration trail, but the route calculated
by this function may not be the best. To determine the best route, users can manually specify the route
constraints based on the results displayed in Automatic Pre-Calculation according to the network plan.
Step 4 Optional: On the topology, right-click an NE and set the route constraints, include Explicit
Node, Excluded Node, Explicit Link and Excluded Link
When setting Explicit Node or Explicit Link for route computation, ensure that Explicit
Node or Explicit Link is set along a link from the source to the sink..
Step 5 Optional: Click the Route Restriction tab to view or set the information of Explicit Node and
Excluded Node.
Step 6 Click Apply to complete the settings of the preset restoration trail.
----End
6.2.6 Setting the Original Route

The route of an ASON trail is usually the original route when the service is created. If the route
of an ASON trail changes, you can also set the route after change to the original route.
Prerequisite
After several topology changes on an ASON network, the actual service routes may be different
from the original routes. The ASON software provides the function of reverting the services on

the entire network to the original trails. Generally, the route during ASON service creation is
the original route of the ASON services. If the original route recovers after rerouting of the
ASON services, the services can be adjusted to the original route manually.
Procedure
Step 2 Set a trail that you want to set and click Maintenance. Choose Set As Original Route from the
drop-down menu.
Step 3 In the confirmation dialog box displayed, click Yes.
Step 4 A dialog box is displayed indicating that the operation was successful. Click Close to complete
the setting of the original route.
Step 5 Optional: Set a trail for which the original route is already set and click Maintenance. Choose
Refresh Original Route from the drop-down menu.
----End
6.2.7 Disabling Electrical-Layer ASON Links

WDM ASON features fall into two groups: electrical-layer ASON features and optical-layer
ASON features. When only optical-layer ASON features are required, users can disable
electrical-layer ASON links to reduce the system load and resource consumption.
Prerequisite
l The electrical-layer ASON trail cannot exist on ASON NEs.
NOTE
The product provides the function of enabling or disabling electrical ASON links on a per-NE basis. When
only optical-layer ASON features are required, users can disable electrical-layer ASON links. When
electrical ASON features are used, do not disable electrical-layer ASON links.
If electrical-layer ASON links need to be enabled again after being disabled, Electrical Layer must be set
to Enabled for the NEs at the two ends of the ASON links. Otherwise, link verification will fail.
Procedure
Step 2 In the WDM ASON Topology Management window, select an ASON domain.
Step 3 Click the ASON Feature of Each Layer tab. Select ASON NE, double-click the corresponding
Electrical Layer field, and select Disabled from the drop-down list.

TIP
Press Ctrl+A to select all NEs. In the Electrical Layer area, right-click and choose Disabled from the
shortcut menu to fast disable the electrical-layer ASON features of all the NEs in the domain.
Step 4 Click Apply.
Step 5 A dialog box is displayed, indicating that the operation will make the electrical-layer ASON
resources unavailable. After confirmation, click OK.
Step 6 A reconfirmation dialog box is displayed. Click OK.
Step 7 A dialog box is displayed, indicating that the operation is successful. Click Close.
Step 8 Optional: Select the Configured NE tab, click Synchronize NE at the right bottom corner to
view the status of the electrical-layer ASON feature of the ASON NE.
----End

6.3.1 Reverting the WDM ASON OCh Trail Manually

When rerouting occurs in the revertive WDM ASON OCh trail, the original trail resource is
reserved. If the fault in the original trail is rectified, you can revert the WDM ASON OCh trail
manually to the original trail.
Prerequisite
l It is applicable for the revertive WDM ASON OCh trail.
l Rerouting occurs in the WDM ASON OCh trail and the fault in the original trail is rectified.
Procedure
Step 2 In the list displayed, select one or more WDM ASON trails, choose Maintenance > Manual
Revert.
Step 3 Click Close in the Operation Result dialog box.
----End
6.3.2 Reverting A WDM ASON Trail to the Original Route

The ASON feature supports reverting a WDM ASON trail to the original route. After a WDM
ASON trail is rerouted for several times, it can be reverted to the original route.

Prerequisite
l There are idle resources on the TE link on the original route.
Procedure
Step 2 Optional: Click Filter to set the filter criteria and set Whether Original Route Is Active to
No. Click Filter All. In the Prompt dialog box displayed, click Yes.
Step 3 In the list displayed, select one WDM ASON trail to be reverted. Click the Original Route tab
to view the original route of the WDM trail.
NOTE
If you select multiple WDM ASON trails, the original route of the first trail is displayed.
Step 4 Choose Configuration > WDM ASON > TE Link Management from the Main Menu. Check
whether there are idle resources on the TE link of the original route.
Step 5 Navigate to the WDM ASON Trail Management window.

l To restore an optical-layer service, click Maintenance and choose Revert To Original
Route > Revert To Wavelength from the drop-down menu. The WDM ASON trail is
reverted to the original route. The WDM ASON trail is reverted to the original route.
l To restore an electrical-layer service, you can click Maintenance and choose Revert To
Original Route > Revert To Port or Revert To Original Route > Revert To Channel
according to different service types. The WDM ASON trail is reverted to the original route.
NOTE
If you select electrical-layer and optical-layer services at the same time, only Revert To Wavelength can
be performed only for optical-layer services.
----End
6.3.3 Optimizing WDM ASON OCh Trail

To manually adjust one or more WDM ASON OCh Trail, you can use the optimization function
to transfer the WDM ASON OCh Trail to the expected trails.
Prerequisite
l A WDM ASON OCh Trail must be created.
l For a revertive silver WDM ASON OCh Trail, you cannot perform the optimization
operation when the service is being reverted upon rerouting.
l WDM OCh trail cannot be optimized in batches at the same time.
l WDM ASON OCh trail in different domains cannot be optimized in batches.

Procedure
Step 2 In the list displayed, select one or more WDM ASON OCh trails that you want to adjust. Click
Maintenance and choose Optimize Route from the drop-down menu. The wizard is displayed.
Step 3 In the Topology View, right-click the icon of an NE. Then specify the explicit nodes, explicit
links, excluded nodes, or excluded links to set the trail after optimization.
Step 4 Check whether the route adjustment is correctly set and click Apply.
Step 5 In the Operation Result dialog box displayed, click Close.
Step 6 In the WDM ASON trail list, select the optimized trails. Click Maintenance and then choose
Refresh Original Route.
Step 7 In the WDM ASON trail list, select the trail after optimization. You can view the route
information of the WDM ASON trail after optimization in the Actual Route.
----End
6.3.4 Optimizing WDM ASON ODUk Trail

To manually adjust one or more WDM ASON ODUk trails, you can use the optimization
function to migrate the WDM ASON ODUk trails to the expected trails.

Prerequisite
l A WDM ASON ODUk trail must be created.
Context
l For a revertive silver WDM ODUk trail, you cannot perform the optimization operation
when the service is being reverted upon rerouting.
l Diamond and non-diamond WDM ODUk trail cannot be optimized in batches at the same
time.
l ASON WDM ODUk trail in different domains cannot be optimized in batches.
l ODU1 and ODU2 trails cannot be optimized at the same time.
l ODUk trails and other trails of a different level cannot be optimized at the same time.
Procedure
Step 2 In the list displayed, select one or more WDM ASON ODUk trails that you want to adjust. Click
Step 3 In the Topology View, right-click the icon of an NE. Then specify the explicit nodes, explicit
links, excluded nodes, or excluded links to set the trail after optimization.
Step 4 Check whether the route adjustment is correctly set and then click Apply.

Step 5 In the Operation Result dialog box displayed, click Close.
Step 6 In the WDM ASON trail list, select the optimized trails. Click Maintenance and then choose
Refresh Original Route.
Step 7 In the WDM ASON trail list, select the trail after optimization. You can view the route
information of the WDM ASON ODUk trail after optimization in the Actual Route.
----End
6.4 Converting ASON Services

An ASON network supports the convertion between traditional trails and ASON trails and the
convertion between ASON trails with different level.
6.4.1 Converting a WDM ASON Trail to a Traditional WDM Trail

You can convert a WDM ASON trail at diamond, silver or copper level to a traditional WDM
trail. This is applicable to network reconstruction, expansion and upgrade.
Prerequisite
l The WDM ASON trail must be created.
l The WDM ASON trail that you want to downgrade must be in the active state.
Procedure
l Conversion at the ASON Layer
Menu.
2. Optional: Set the filter criteria in the Filter dialog box and methods as needed.
– If you need to filter all trails, click Filter All.
– If you need to add more trails that match the requirement to the list, click
Incremental Filter.
– If you need to filter the trails in the list, click Secondary Filter.
3. In the Prompt dialog box, click Yes. The list displays the trails that meet the filter
criteria.
4. Select an ASON trail to be downgrade from the list, right-click and choose
Downgrade to Traditional WDM Trail from the shortcut menu.
5. In the Prompt dialog box, click Yes. A prompt is displayed indicating that the
operation is successful. Click Close.
NOTE
Choose Service > WDM Trail > WDM Trail Search from the Main Menu to search for WDM
trails. In the Management WDM Trail window, manage the WDM ASON trails that are
successfully downgraded.

NOTE
If the ASON trail is under traditional end-to-end management (that is, the trail is searched out
in the WDM Trail Management window), the NMS will display a message indicating that
the downgrade fails. To successfully downgrade the ASON trail, perform the following
operations:
l Downgrade the ASON trail at the traditional network layer based on the guidelines
described in "Conversion at the Traditional Network Layer."
l Search out the trail at the traditional network layer and delete all client trails related to the
ASON service based on descriptions in step 6. Then downgrade the trail according to the
preceding steps.
6. Optional: On the main menu, choose Service > WDM Trail > WDM Trail
Management. Select end-to-end trails corresponding to the ASON service. Right-
click and choose Browse Relevant Client Trails from the shortcut menu. Select all
the client trails that are searched out. Right-click and choose Delete from Network
Layer from the shortcut menu to delete client trails related to the ASON service.
NOTE
Sometimes, you need to search client trails for multiple times to ensure that all client trails
related to the ASON service are deleted.
l Conversion at the Traditional Network Layer
1. Choose Service > WDM Trail > WDM Trail Management from the Main Menu.
2. Optional: Set the filter criteria in the Filter dialog box and methods as needed.
– If you need to filter all trails, click Filter All.
– If you need to add more trails that match the requirement to the list, click
Incremental Filter.
– If you need to filter the trails in the list, click Secondary Filter.
3. Select an ASON-WDM trail to be downgrade from the list, right-click and choose
Downgrade to Traditional WDM Trail from the shortcut menu. The Downgrade
to Traditional WDM Trail window is displayed.
4. In the Trail List, select the required trail and then click Add to add the trail to the
ASON Trail to Be Downgraded list.
5. In the ASON Trail to Be Downgraded list, select the required trail for downgrade.
6. Click Apply. A prompt is displayed indicating that the operation is successful. Click
Close.
----End
6.4.2 Converting a Traditional WDM Trail to an WDM ASON Trail

During network upgrade, expansion, and reconstruction, you can upgrade a traditional WDM
trail to a WDM ASON trail. The WDM ASON trail is classified into OCh and ODUk trails.
Prerequisite
l The bidirectional WDM trail must be created.
l The NEs that the WDM trail to be upgraded passes through must be WDM ASON NEs and
the trail crosses the uniform route.
l The WDM trail to be upgraded is in the active state.

l If the station consists of separate optical and electrical NEs, related configurations must be
made on the U2000 before upgrading to ensure normal communication between the optical
and electrical NEs and normal creation of TE links. For details, see Configuring a Station
with Separate Optical and Electrical NEs.
Context
NOTE
l A uniform route means that the port on the FIU board and the port on the OTU board in the route are
consistent.
Procedure
Step 1 Choose Service > WDM Trail > WDM Trail Management from the Main Menu.
Step 2 In the Set Trail Browse Filter Conditions dialog box, enter the filter criteria to filter out the
OCh, OTUk, ODUk, and Client trails.
l If you need to filter all trails, click Filter All.
l If you need to add more trails that match the requirement to the list, click Incremental
Filter.
l If you need to filter the trails in the list, click Secondary Filter.
Step 3 In the list, select a WDM trail to be upgraded, right-click and choose Update to WDM ASON
Trail from the shortcut menu. The Upgrade to WDM ASON Trail dialog box is displayed.
Step 4 In the Trail List, select the trail to be updated and click Add to add the trail to the ASON Trail
to Be Upgraded list.
Step 5 Select a trail in the ASON Trail to Be Upgrade list. To set the ASON trail attributes, double-
click Class and set the relevant rerouting attributes.

Step 6 Select the trail that you want to upgrade and click OK.
Step 8 A prompt appears telling you that the operation was successful. Click OK.
NOTE
Search WDM trails immediately after an OCh trail is upgraded to the WDM ASON trail, and this trail is still
displayed. After a certain period when new cross-connections are reported from the NE or when you manually
synchronize optical cross-connections in the NE Explorer, the WDM trails that are searched out are updated.
----End
6.4.3 Performing Conversion Between the Diamond and Silver or

Copper WDM ASON Trails
The conversion between the electrical-layer diamond WDM ASON trail and silver or copper
WDM ASON trail can be performed.
Prerequisite
l Associated WDM trails cannot be converted to diamond WDM trails.
l The levels of the WDM ASON trail before and after the conversion must be consistent. For
example, the ODU1 trails must be converted into ODU1 trails.
l This section describes how to convert a diamond WDM trail to a silver WDM trail. The
conversion from a diamond WDM trail to a copper WDM trail, from a silver WDM trail
to a diamond WDM trail, or from a copper WDM trail to a diamond WDM trail is similar.
Procedure

Step 2 In the list displayed, right-click the desired diamond service and then choose In-Service
Migration > Silver from the shortcut menu.
Step 4 The Confirm the route that you want to reserve dialog box is displayed. Confirm whether to
reserve the working route or the protection route for the desired diamond ASON service, and
correspondingly select Working Route or Protection Route.
NOTE
The route that you want to reserve can be selected only when a diamond service is converted to a silver or copper
service.
Step 5 After the conversion, a prompt is displayed indicating that the operation was successful. Click
Close and then you can query the rerouting attributes of the ASON service as indicated.
----End
6.4.4 Performing Conversion Between the Silver and Copper WDM

ASON Trails
The conversion between the electrical-layer silver WDM ASON trail and copper WDM ASON
trail can be performed.
Prerequisite
l This section describes how to convert the silver WDM ASON trail to copper WDM ASON
trail. The conversion from the copper WDM ASON trail to silver WDM ASON trail is
similar.
Procedure
Step 2 In the list displayed, right-click the desired silver service and then choose In-Service
Migration > Copper from the shortcut menu.
Step 4 After the conversion, wait for one minute. Then, the U2000 displays that the silver WDM ASON
trail is converted to a copper WDM ASON trail.
----End
6.4.5 Performing Conversion Between ASON Trails for Services

with Tributary SNCP and Those for Services Without Tributary
SNCP
This section describes how to perform conversion between ASON trails for services with
tributary SNCP protection and ASON trails for services without tributary SNCP protection.

Prerequisite
Context
l This section describes how to convert silver WDM ASON trails for services without
tributary SNCP protection into silver WDM ASON trails for services with tributary SNCP
protection through an example. Conversion between WDM ASON trails at other levels is
similar.
Procedure
Step 1 Convert silver WDM ASON trails for services without tributary SNCP protection into silver
WDM ASON trails for services with tributary SNCP protection.
Menu.
2. In the trail list, select the desired WDM ASON trail, click Maintenance and choose SNCP
Accessed Service from the drop-down list.
3. In Service Accessed at Source Node and Service Accessed at Sink Node of the SNCP
Accessed Service window, select the WDM ASON trail and click Add Access Point2 to
set information about access point 2 on the source and sink nodes.

4. In Add Access Point2, select the ports on the tributary boards at the source and sink nodes
and click Apply. Then, the WDM ASON trail conversion is completed.
Step 2 Convert silver WDM ASON trails for services with tributary SNCP protection into silver WDM
ASON trails for services without tributary SNCP protection.
Menu.
2. In the trail list, select the desired WDM ASON trail, click Maintenance and choose SNCP
Accessed Service from the drop-down list.
3. In Service Accessed at Source Node and Service Accessed at Sink Node of the SNCP
Accessed Service window, select the WDM ASON trail and click Delete Access Point2
to delete information about access point 2 on the source and sink nodes. Then, the WDM
ASON trail conversion is completed.

----End
6.5 Managing the OVPN Customers and OVPN Services

In the case of the OVPN, an ASON network is shared by multiple operators. When multiple
operators need to share an ASON network, you can allocate different TE link resources for each
operator. Each operator can use and manage its own TE link resources and ASON services.
6.5.1 Enabling OVPN Function of ASON NE

The optical virtual private network (OVPN) function can be used only when the OVPN function
is enabled for all the NEs in the ASON domain. The OVPN function of the ASON NEs is
controlled through the license of the NMS. The OVPN function of the ASON NEs can be enabled
only if the license of the NMS supports the OVPN function.
Prerequisite
l The license of the NMS must support the OVPN function.
CAUTION
The OVPN function must be enabled or disabled for all the ASON NEs in the ASON domain.
Otherwise, the service creation may be affected.
Procedure

Step 2 In the WDM ASON Topology Management window, select the domain for which the OVPN
function needs to be enabled. Set OVPN Enable Status of all the NEs in this domain to
Enabled.
Step 3 Click Apply. A dialog box is displayed indicating that the operation is successful.
----End
6.5.2 Creating NM User for OVPN Customer

To ensure that each OVPN Customer can manage its own resources and services, an independent
NM user needs to be created for each OVPN Customer.
Prerequisite
l You must log in to the U2000 as the superuser admin.
l The license of the NMS must support the OVPN function.
NOTE
To facilitate management, only one NM user is created for each OVPN Customer.
For the OVPN working principles and authorities of the NM user, see 1.5.7 OVPN.
Procedure
Step 1 Choose Administration > NMS Security > NMS User Management from the Main Menu.
Step 2 Create the NM user nmuser1.
1. In the User window, click New User.
2. In the New User dialog box, enter the information of the new user.
An example is provided as follows:
l Name: nmusesr1
l Password: osninfo123
l Confirm password: osninfo123
l For the other parameters, adopt the default values.

3. Click OK.
Step 3 Add the NM user nmuser1 into Administrator Group.

1. In the User field, select the newly created NM user nmuser1, and then click Add on the
User Groups tab page.
2. In the displayed dialog box, select Administrator and click OK. At this point, the added
user group is displayed in the User Groups list.
Step 4 Adjust the authority of the NM user nmuser1 to ensure that the equipment set has the authorities
of the ASON end to end operation set.
1. Click the Operation Rights tab. Click Select.
2. In the Select Rights dialog box, select and add the ASON end to end operation set to
Selected Rights.
3. Click OK. The authorities that are added are displayed in the authority list.
Step 5 Set the access control list of the NM user nmuser1.

1. In the right pane, click the ACL Settings tab.
2. Select the Use the Current User ACL option box.
3. Click Set ACL. Then, the Set ACL dialog box is displayed.
4. Click Add. Then, the Add dialog box is displayed.
5. Select the Start IP address to the end IP address option box and set the following
parameters.


l Start IP address: 192.168.0.1
l End IP address: 192.168.255.255
6. Click OK.
7. Click Close.
8. Select the Access Allowed check box that corresponds to the IP address range. Click
Apply.
----End
6.5.3 Creating OVPN Customer

Before the resources are allocated for different OVPN customers, the corresponding OVPN
customers need to be created on the NMS.
Prerequisite
l The OVPN function must be enabled for the ASON NEs.
l The NM users of the OVPN customers must be created.
CAUTION
To facilitate management, it is recommended that each NM user should correspond to an OVPN
customer.
Procedure
Step 1 Choose Service > Customer Management from the Main Menu.
Step 2 In the Customer Management window, click Create.
Step 3 In the Create Customer window, enter the customer information.

l Name: OVPN1
l Legal representative: abc
l Telephone number: 12345678
l Email: abc@mail.com
l Address: FFFF
l Postcode: 123456
l ID: 2

Step 4 Click OK. After the creation is complete, a dialog box is displayed indicating that the operation
is successful.
Step 5 Select the created OVPN customer in the list, Right-click and select Authorize to User, a dialog
box Customer Authorize Management is displayed. Select and add the corresponding NM
user nmuser1 to Selected Users.

Step 6 Click OK, the associations between OVPN custom and the NM user is complete.
Step 7 Repeat Steps 1-6 to create the NM users of other OVPN customers.
----End
6.5.4 Allocating TE Links for OVPN Customers

Each OVPN customer can use only the allocated TE links to create services. The timeslots in
the TE links allocated for each OVPN customer should be planned properly according to the
actual situations before the services are configured.
Prerequisite
l You must log in to the U2000 by using the superuser admin.
l The OVPN function must be enabled for the ASON NEs.
l The OVPN customers must be created on the NMS.
l The timeslots in the TE links that are allocated for each OVPN customer must be planned
properly.

NOTE
When you partition the TE links on the ODUk SPRing for OVPN customers, ensure that the timeslots of
each section are consistent.
Procedure
Step 2 In the WDM TE Link Management window, select the TE link that needs to be partitioned.
Click Partition Resource.
TIP
You can select multiple TE links to be partitioned, by holding down the Ctrl key and clicking the target
TE links.
Step 3 In the Partition Resource window, select the TE link that needs to be partitioned. Double-click
OVPN Customer that corresponds to the specific timeslot and set the OVPN customer.
Step 4 Click Apply. A dialog box is displayed indicating that the operation is successful.
Step 5 Optional: After the TE link resources are allocated, select a TE link and right-click Copy.
Step 6 Optional: Select another TE link to copy the previously selected TE link to. Right-click and
choose Paste from the shortcut menu.
Step 7 Then, a dialog box is displayed indicating that the operation is successful. Close the window.
Step 8 Optional: Click Synchronize and select a TE link. Then, you can check the TE link allocation
in the OVPN Customer Information window on the lower left.
----End
6.5.5 Creating OVPN Services

The OVPN services may be diamond services, silver services or copper services.
Prerequisite
l The TE link resources must be allocated for the OVPN customers.
l There must be NM users who use the OVPN resources.
As shown in Figure 6-23, the four NEs are ASON NEs. An OVPN silver service needs to be
configured for the OVPN1 customer between NE1 and NE3.

Figure 6-23 OVPN service requirements

NE1
NE2 NE4
: ASON NE
NE3 : ASON Trail
Board Configuration
Figure 6-24 shows the board configurations of NE1 and NE3, which are OptiX OSN 8800 NEs.

Figure 6-24 Board configurations of NE1 and NE3
Slave Subrack 1 FAN

A S S
EF U T T
I1
R W W R
M S S M
U D D U
2 2 2 2 2 2 2 2 C 2 2 2 2 2 2 2 X
9 9 9 9
X X
C C
S S
O W
T T
L T R
F S T TW T T T O O
M S B SM BM40A
Q Q
S I Q
C Q Q Q Q Q D40
U D U D U U
X X
U M
1 M M M M M 1 4
9 9 1 1
FAN
Master Subrack FAN

A S S
EF U T T
EFI2
PI
UU PI
PI
UU STI ATE
I1
R W W W R
S
M S S SSM M
M40 D40 C D40 M40
U D M D U
C
9 9D 4 9
4 9
O O OO O O
F S S S S
F O F
B A BB A B
I C C C C
I A I
U U UU U U
U C 2 2 2
U U 1 U
1 1 11 1 1
FAN

Service Planning
The OVPN services are planned according to the service requirements.Table 6-9 provides the
service planning information.
Table 6-9 OVPN service planning
Attribute NE1<->NE3
Source board-port NE1
Source board-port 101-12LQMD-1(IN1/OUT1)
Source wavelength 2
Sink NE NE3
Sink board-port 101-12LQMD-1(IN1/OUT1)
Sink wavelength 2
OVPN customer OVPN1
Rerouting Revertive mode Non-revertive

attributes
Lockout Unlocked
Priority Low
CrankBack 1
Rerouting policy Use existing trails whenever possible.
Rerouting hold-off time 0
NOTE
Before you create the OVPN services, ensure that the TE link resources are already allocated for the OVPN
users.
Procedure
Step 3 Enter the basic information of the OCh trail in the Basic Information tab. Click Browse. In the
dialog box displayed, select the slot, port and wavelength of the source and sink.
l Level: OCh

l Class: Silver
l Source: NE1-101-12LQMD-1(IN1/OUT1)-2/1529.55/196.000
l Sink: NE3-101-12LQMD-1(IN1/OUT1)-2/1529.55/196.000
l OVPN Customer: OVPN1

NOTE
l When the Rate is set as 2.5G, 5G, 10G or 40G, as least one of the Source or Sink of the trail must be
an OTU unit.
l When the Rate is set as -, both of the Source and Sink of the trail should be FIU unit.
Step 4 In the Routing Attributes field, enter the rerouting attributes for the OCh trail.
l Revertive Mode: Non-revertive
l Lockout: Unlocked
l Priority: Low
l CrankBack: 1
l Rerouting hold-off time: 0
NOTE
Among the routing attributes, Trigger Condition is a unique feature of diamond WDM ASON trail and
is classified into three policies: Reroute when one trail fails, Reroute when both trails fail and Never
reroute.
NOTE
Step 6 Optional: Configure the explicit trail based on the actual service plan. For details, see
Configuring the Explicit Link.

dialog box.
----End
6.5.6 Querying the TE Link Resources of the OVPN Customers

After the TE link resources are allocated for the OVPN customers, you can query the TE link
resources of each OVPN customer.
Prerequisite
l The TE link resources must be allocated for the OVPN customers.
Procedure
Step 2 Click Filter. Enter the filtering information in the Filter dialog box.
l Domain: ASON
l Source NE: All
l Sink NE: All
l OVPN Customer: OVPN1
Step 3 Click Filter. Then, the NMS returns the information about the queried TE link resources of the
OVPN customer.
----End

6.5.7 Querying the Services of the OVPN Customers

After the ASON services are created for the OVPN customers, you can query the ASON services
of each OVPN customer.
Prerequisite
l The ASON services must be created for the OVPN customers.
Procedure
Step 2 Click Filter. In the Filter dialog box, select Select OVPN Customer.
Step 3 Select the OVPN customer whose ASON services need to be queried. Click OK.
Step 4 In the Filter dialog box, click Filter All. Click Yes in the dialog box that is displayed.
Step 5 The NMS returns the query result.
----End
6.6 Creating Services Between an ASON NE and a

Traditional NE

6.6.1 Creating Services Between Two Traditional NEs with ASON

NEs in Between
You can create services between two traditional NEs with ASON NEs in between. This section
considers ODU1 services as an example for illustration.
Prerequisite
l ASON NEs must be configured.
l There must be server trail of ODU1 trail, such as ODU2 or OTU1.
Service Requirement
See Figure 6-25. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.
An ODU1 trail needs to be configured between NE5 and NE6. This service is required to be an
unprotected service in the traditional network, but a silver service in the ASON network.
Figure 6-25 ODU1 trail requirement between traditional NEs

NE1 NE4
NE6 NE5
ODU1 ODU1
NE2 NE3
: ASON NE
: Traditional NE
Service Planning
You can refer to Table 6-10 to plan a service.
Table 6-10 ODU1 trail planning between traditional NEs
Attribute NE6<->NE5
Source NE NE6
Source board-port 13-TDG-201(LP/LP)-1
Sink NE NE5
Sink board-port 13-TDG-201(LP/LP)-1
Service route Automatically calculated by the system

Attribute NE6<->NE5
ASON service type Silver
Traditional service type Unprotected
You can use the following two ways to create an ODU1 trail between two traditional NEs with
ASON NEs in between.
l Use the trail feature of the U2000 to directly create an ODU1 trail.
l Create a silver service within the ASON domain. Then create ODU1 cross-connections on
NE5 and NE6.
The following illustrates how to create such an ODU1 trail in the first way.
Procedure
Step 1 Choose Service > WDM Trail > Manage WDM Trail from the Main Menu.
Step 2 Choose Create/Modify > Create WDM Trail.
Step 3 Enter the service information as follows:

l Level: ODU1
l Rate: ODU1
l Source: NE6-13-TDG-201(LP/LP)-1
l Sink: NE5-13-TDG-201(LP/LP)-1
Step 4 Check the SPC First check box. Click ASON Attributes Settings tab and choose the Silver
protection type.
l Lockout: Unlocked
l Priority: Low
l CrankBack: 1
Step 5 Check the Activate the trail check box and click Apply. The system prompts that the operation
was successful. Click Close.
Step 6 In the WDM Trail Management window, click Filter and select Filter All.
Step 7 Choose Service > WDM Trail > Manage WDM Trail from the Main Menu. View the detailed
route information of the trail that is created. You can also view the value of ASON-WDM
Trail to check whether the ASON section of the ASON-WDM trail is successfully created.

You can view the ASON trail information.
----End
6.6.2 Creating 1+1 Services Between Two Traditional NEs with

ASON NEs in Between
You can create 1+1 services between two traditional NEs with ASON NEs in between. This
section considers ODU1 services as an example for illustration.
Prerequisite
Service Requirement
As shown in Figure 6-26, NE1, NE2, NE3, and NE4 are ASON NEs whereas NE5 and NE6 are
traditional NEs. A 1+1 ODU1 service needs to be configured between NE5 and NE6. To
implement the 1+1 protection, the service association is configured in the ASON domain and
the SNCP is configured on the traditional NEs.
Figure 6-26 1+1 ODU1 trail requirement between traditional NEs

NE1 NE4
NE6 NE5
ODU1 ODU1
NE2 NE3
: ASON NE
: Traditional NE
Service Planning
Refer to Table 6-11, Table 6-12 and Table 6-13 for service planning.
Table 6-11 Planning of Two Silver ASON Trails
Attribute NE1<->NE4 NE2<->NE3
Source NE NE1 NE1
Source Slot 2-12NS2 2-12NS2

Source Optical 1(IN/OUT)-1 1(IN/OUT)-1

Port-Optical
Channel
Sink NE NE4 NE3
Sink Slot 2-12NS2 2-12NS2
Sink Optical 1(IN/OUT)-1 1(IN/OUT)-1

Port-Optical
Channel
Protection type Silver Silver
Level ODU1 ODU1
Trail type Working trail Protection trail
Table 6-12 SNCP service planning of NE5

Attribute Transmit direction Receive direction
Working Protection Working Protection

service service service service
Source Slot 13-TDG 1-12NS2 2-12NS2
Source Optical 201(LP/LP) 51(ODU1LP/ 51(ODU1LP/

Port-Optical ODU1LP)-1 ODU1LP)-1
Channel
Sink Slot 1-12NS2 2-12NS2 13-TDG
Sink Optical 51(ODU1LP/ 51(ODU1LP/ 201(LP/LP)

Channel
Level ODU1 ODU1
Direction Unidirectional Unidirectional


Source Slot 1-12NS2 1-12NS2 2-12NS2


Source Optical 201(LP/LP) 51(ODU1LP/ 51(ODU1LP/

Channel
Sink Slot 1-12NS2 2-12NS2 13-TDG
Sink Optical 51(ODU1LP/ 51(ODU1LP/ 201(LP/LP)

Channel
Level ODU1 ODU1
Context
The two ways of creating 1+1 ODU1 service between traditional NEs that cross an ASON
domain are as follows:
l Use the trail function of the U2000 to create an ODU1 service.
l Create a silver ASON service between NE1 and NE4 and a silver ASON service between
NE2 and NE3. Associate these two silver ASON services. Configure ODU1 cross-
connections for NE5 and NE6.
The following procedure describes how to 1+1 ODU1 services between traditional NEs that
cross an ASON domain in the first way.
Procedure
Step 2 Choose Create/Modify > Create WDM Trail.
l Level: ODU1
l Rate: ODU1
l Source: NE6-13-TDG-201(LP/LP)-1
l Sink: NE5-13-TDG-201(LP/LP)-1
protection type.
l Lockout: Unlocked
l Priority: Low

l CrankBack: 1
Step 5 Click the Protection Setting tab. Right-click NE5 and choose Set Dual-Fed Point from the
shortcut menu.
Step 6 Right-click NE6 and choose Set Selective-Receiving Point from the shortcut menu.
Step 8 In the WDM Trail Management window, click Filter and select Filter All.
Step 9 Choose Service > WDM Trail > Manage WDM Trail from the Main Menu. View the detailed
route information of the trail that is created. You can also view the value of ASON-WDM
Trail to check whether the ASON section of the ASON-WDM trail is successfully created.
You can view the ASON trail information.
----End
6.6.3 Creating Services Between ASON NEs with a Traditional NE

in Between
You can configure an end-to-end ASON service between two ASON NEs with a traditional NE
in between. This section considers ODU1 services as an example for illustration.
Prerequisite
l A virtual TE link must be created between the two ASON NEs. For the detailed procedure,
see Creating a Virtual TE Link.
Service Planning
Table 6-14 shows the planning of ODU1 services between two ASON NEs.
Table 6-14 Planning of ODU1 services between two ASON NEs
Attribute NE1<->NE3
Source NE NE1
Source board-port ND2-1(IN1/OUT1)
Sink NE NE3
Sink board-port ND2-1(IN1/OUT1)

Attribute NE1<->NE3
Route constraint The service trail must traverse NE2.
Routing attributes Revertive mode Non-revertive
Lockout Unlocked
Priority Low
CrankBack 1
Rerouting triggered by No
SD
Rerouting hold-off 0
time
Procedure
Step 3 In Basic Information, set the basic information of a trail, click Browse and then in the displayed
dialog box select the source and sink board IDs, ports, and wavelengths.
NOTE
After that, set Level and Rate before setting the protection type.
l Lockout: Unlocked
l Priority: Low
l CrankBack: 1

NOTE
NOTE
Explicit Link.
dialog box.
----End
6.7 Managing Services Between a WDM ASON NE and a

Traditional WDM NE
A network can consist of WDM ASON NEs and traditional WDM NEs. This implements end-
to-end service configuration and management.

6.7.1 Searching for WDM Trails Crossing the ASON Domain

A WDM ASON trail can be managed by a traditional WDM trail. Currently, you can search for
the WDM trails that cross the ASON domain in the WDM trail management so that customers
can manage the network in a centralized manner.
Prerequisite
l An ASON NE must be created and the NE data must be uploaded.
l The ASON data on the U2000 must be consistent with the ASON data on the NE.
Procedure
Step 1 Choose Service > WDM Trail > Search for WDM Trail from the Main Menu.
Step 2 WDM Trail Search dialog box is displayed. Set Pre-search handling Policy, Collision Trails
handling Policy and After-search handling Policy. ClickNext.
Step 3 Wait until the trail search is complete as indicated by the progress bar below the dialog box.
Click Next.
Step 4 Click Finish. The Information dialog box is displayed telling you to view the trails that are
searched out in the WDM Trail Management window.
Step 6 In the Filter dialog box displayed, set the filter criteria and then click Filter All.
Step 7 The WDM Trail Management interface displays all the WDM trails that meet the criteria.
Right-click the table heading and then choose ASON-WDM Trail.
After ASON-WDM Trail is selected, the ASON-WDM Trail column is displayed in the table.
Step 8 Determine whether the WDM trails cross the ASON domain based on the attribute values
displayed in the ASON-WDM Trail column.
NOTE
If the attribute values are Yes, the WDM trails cross the ASON domain; if the attribute values are No, the
WDM trails are traditional WDM trails.
TIP
Click the heading of the ASON-WDM Trail table, the trails recorded in the table are sorted according to
the attribute values. In this way, the WDM trails that cross the ASON domain and the WDM trails that do
not cross the ASON domain are organized into two groups for display.
----End
6.7.2 Querying the ASON Trails Related to the Traditional WDM

Trail
WDM ASON trails can be managed by traditional WDM trails. Currently, in the user interface
of the WDM trail management, you can query the ASON trails that are related to the traditional
WDM trail. This can help you to manage the network in a centralized manner.

Prerequisite
l The traditional WDM trail that crosses the ASON domain must exist.
Procedure
Step 2 In the Filter dialog box displayed, set the filter criteria and then click Filter All.
Step 3 The WDM Trail Management interface displays all the WDM trails that meet the criteria.
Right-click the table heading and then choose ASON-WDM Trail.
After ASON-WDM Trail is selected, the ASON-WDM Trail column is displayed in the table.
Step 4 For the ASON-WDM Trail parameter of which the attribute is Yes, right-click the trail record
and then choose Browse relevant ASON Trails from the shortcut menu.
Step 5 The ASON trails related to the WDM trail that crosses the ASON domain are displayed in the
WDM ASON Trail Management dialog box displayed.
----End
6.7.3 Setting the Span ID of the ASON-WDM Trail

The ASON software supports ring network protection and calculating span IDs. The span ID
obtained through calculation performed by the ASON software is separated from the span ID
obtained on the U2000 by different sections to avoid conflict. The ASON-WDM trail supports
querying span IDs. The ID of the traditional section is queried from the NE software on the
U2000, and the ID of the ASON section is queried from the ASON software on the U2000.
Prerequisite
l Traditional WDM trails crossing ASON domain must exist.
Context
In the case of the ASON-WDM trail, the IDs of traditional sections can be set. The U2000
calculates the IDs of the traditional sections and then deliver them to the NE software for
configuration. The U2000, however, cannot set or modify the IDs of ASON sections but query
the IDs of ASON sections.
Procedure
l Querying the IDs of the ASON sections on the ASON-WDM trail:
1. Choose Service > WDM Protection Subnet > Maintain WDM Protection
Subnet from the Main menu.
2. Right-click the required protection subnet and then choose Protection Subnet
Attributes from the shortcut menu.
3. Click the Protection Subnet Parameters tab and then click Query.
l Setting the IDs of traditional sections on the ASON-WDM trail:

1. Choose Service > WDM Protection Subnet > Maintain WDM Protection
Subnet from the Main menu.
2. Right-click the required protection subnet and then choose Protection Subnet
Attributes from the shortcut menu.
3. Click the Protection Subnet Parameters tab and then click Calculate Span ID.
----End
6.8 Managing Control Plane Alarms and Performance

Events
6.8.1 Querying Control Plane Alarms

For maintenance purposes, you can query the current alarms or historical alarms that specified
trails generate on the control plane, to learn whether there are any faults on the control plane.
Prerequisite
Maintenance Period
Daily
Tools, Meters, and Materials

U2000
Procedure
Step 1 Click the current alarm indicator on the upper right of the U2000 window to view all the current
networkwide alarms. In the window of the current alarms, click Filter.
NOTE
To browse the current alarms, you can also choose Fault > Browse Current Alarm or Fault > Browse
History Alarm from the Main Menu.
Step 2 In the Filter dialog box displayed, select Alarm Name check box. Click , the Select
Alarm dialog box displayed.
Step 3 In the option alarm tree, select Control Plane Alarms, click , select all of the control
plane alarms, click OK.
Step 4 Click OK. The alarms generated on the control plane are then displayed in the alarm list.
----End

6.8.2 Management of the Suppression Status of Alarms on the

Control Plane
The control plane alarms consist of NE alarm, ASON WDM trail alarm, TE link alarm, control
link alarm, and control channel alarm. Users can suppress the specific control plane alarms as
required.
Prerequisite
Context
This section considers suppressing the NE alarms as an example to describe how to suppress
control plane alarms.
Procedure
Step 1 In the function tree of the NE Explorer, double-click ASON to display the ASON feature setting
options.
Step 2 Select Control Plane Alarm Suppression > NE Alarm Suppression to display event names
and corresponding suppression status.
Step 3 Double-click Status, and then choose Suppressed or Not Suppressed from the drop-down
menu.
Step 4 Click Apply to submit the alarm suppression setting.

Step 5 Optional: After the operation is complete, click Query to view the suppression status of the
current alarms.
----End
6.8.3 Management of the Suppression Status of Alarms Events on

the Control Plane
Users can suppress control plane alarms at the service layer if required.
Prerequisite
Procedure

Step 2 Choose an ASON trail from the list, click Alarm and then select Control Plane Alarm
Suppression.
Step 3 Double click Suppression Status in the Control Plane Alarm Suppression interface, and then
choose Suppressed or Not Suppressed from the drop-down menu.
Step 4 Click Apply to activate the alarm suppression setting.
----End
6.8.4 Querying the Performance of the Control Plane

Users can view the current and historical performance data and the record of performance
threshold crossing events of the control plane. In this manner, users can monitor the performance
of the ASON Trail.
Prerequisite
l The 24-hour performance monitoring of the NE must be enabled.
Maintenance Period
Daily

U2000
Procedure
l Query the data on a network basis.
1. Choose Performance > Browse Control Plane Performance from the Main Menu.
2. Click Current Performance Data tab to view the current performance data.
3. Optional: Click History Performance Data tab to view the historical performance
data.
4. Optional: Click Performance Threshold-Crossing Record tab to view the data of
the performance threshold crossing events.
5. Click Query.
l Query the data on a station basis.
1. In the NE Explorer, click the NE and then choose ASON > Control Plane
Performance > Current Performance from the Function Tree to view the current
performance data.
2. Optional: Choose ASON > Control Plane Performance > History Performance
from the Function Tree to view the historical performance data.
3. Optional: Choose ASON > Control Plane Performance > Performance
Threshold-Crossing from the Function Tree to view the data of the performance
threshold crossing events.
4. Click Query.
----End

6.8.5 Monitoring the Control Plane Performance

The control plane performance monitoring involves NE performance monitoring, WDM ASON
trail performance monitoring and control channel performance monitoring. The control plane
performance monitor status defaults to be disabled. Users can enable the monitoring function if
required so that they can discover and handle problems at the earliest time.
Prerequisite
This section considers enabling the NE monitoring function as an example to describe how to
enable or disable monitoring of the control plane performance.
Procedure
Step 1 In the NE Explorer, click the NE and then choose ASON > Control Plane Performance >
Performance Monitor Status.
Step 2 Click the NE Performance Monitor Status tab. Double-click Monitor Status of the required
performance event, and then choose Enabled from the drop-down menu.
Step 3 Click Apply to submit the setting.
Step 4 Optional: Click Query to view the control plane monitoring status of ASON NE.
----End
6.8.6 Setting the Auto-Report Status of the Control Plane

Performance Data
The control plane performance is monitored on a 24-hour basis. The performance is not reported
automatically by default. Users can enable the auto-report function if required. The control plane
performance monitoring involves NE performance monitoring, WDM ASON trail performance
monitoring, and control channel performance monitoring.
Prerequisite

This section considers enabling the auto-report function as an example to describe how to enable
or disable auto report of the control plane performance data.
Procedure
Performance Monitor Status. options.
Step 2 Click the NE Performance Monitor Status tab. Double-click 24-Hour Auto-Report of the
required performance event, and then choose Enabled from the drop-down menu.
Step 4 Optional: Click Query to view the auto-report status of the control plane of the ASON NE.
----End
6.8.7 Setting the Control Plane Performance Threshold

When an NE detects that a certain performance value exceeds the specified threshold, the NE
reports a performance threshold crossing event. Set the performance threshold for every WDM
ASON trail properly based on the requirements. In this way, the performance of every WDM
ASON trail can be monitored.
Prerequisite
Procedure
Performance Threshold.
Step 2 In the WDM ASON Trail list on the interface, select the desired WDM ASON trail.
Step 3 In the WDM ASON Trail Performance Threshold list, double-click the Threshold Value
field of the WDM ASON trail, and then enter a new performance threshold value.
Step 5 Click Query to query the control plane performance threshold of the WDM ASON trail.
----End

ASON User Guide 7 Configuring OCS ASON Networks
7 Configuring OCS ASON Networks
About This Chapter
You can configure an ASON network using the U2000.

7.2 Managing Link Resources
ASON is capable of automatically switching optical network connections under the control of
the signaling network. It dynamically allocates network resources as required. As the network
is growing larger, a more reasonable way of resource management is required to make the most
of the network resources and to improve the network efficiency. Link resource management is
one aspect of resource management. In an actual network, thousands of connections may exist
between two nodes, while each connection may be composed of multiple data links. Usually,
there are links that have the same attributes according to a route protocol. These links are
regarded as a whole, which is known as the traffic engineer link (TE link), serving as the
processing object of the route information.
7.3 Creating ASON Services
The trail levels that an ASON trail supports are as follows: diamond, gold, silver, copper and
iron. The trail levels that an ASON server trail supports are as follows: diamond, gold, silver
and copper. A label switched path (LSP) is a trail passed through by an ASON service. It is also
called an ASON trail.
7.6 Migrating ASON Services

An ASON network supports the migration between traditional Services and ASON services, and
supports the in-service migration between ASON services at different levels.
7.7 Creating ASON Trail Groups
An ASON trail group is often used with LCAS.
7.8 Creating Services Between an ASON NE and a Traditional NE
7.9 Accessing a Traditional Network to an ASON Through Linear MSP
When accessing services from a traditional network, to ensure that reliability of the accessed
services, you can create a 1+1 or 1:1 linear MSP at the edge of the traditional network and an
ASON domain. You can configure services in an ASON domain to the diamond, gold, and silver
level.
7.10 Managing Control Plane Alarms and Performance Events


Precautions
CAUTION
l Usually, you do not need to modify the protocol configurations.
l You can modify the protocol configurations when the ASON networking is a special one, or
when a higher security is required.
7.1.1 Modifying the LMP Discovery Type

There are two types of LMP discovery. One is by using the J0 byte (default). The other one is
by using the D4-D12 bytes. When a REG NE is between two ASON NEs, you need to modify
the LMP discovery type for the corresponding boards of the two ASON NEs. That is, use D4-
D12 bytes.
Prerequisite
l The ASON feature of the NEs is enabled.
If the service requirement is as shown in Figure 7-1, where NE1-NE4 are ASON NEs and NE5
is a REG NE, you need to modify the LMP discovery type for the boards of NE3 and NE4.
Figure 7-1 LMP discovery mode

NE1 NE4
NE5
NE2 NE3
: ASON NE
:REGl NE

NOTE
The OptiX OSN 8800 does not support REG. Therefore, the equipment on NE5 should be OptiX OSN
3500 or OptiX OSN 7500.
Board Configuration
Figure 7-2 shows how the boards are configured for the case of the previously illustrated service
requirements.
Figure 7-2 Board configuration of NE3 and NE4
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
H Q Q Q C C C I I I
4 6 6 6 C 2 1 U U U
1 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Procedure
Step 1 In the NE Explorer, click the NE and choose ASON > Link Management Protocol from the
Function Tree. Click LMP Auto Discovery Type tab.
Step 2 Click Query to query the LMP automatic discovery type.
Step 3 Double-click Configuration Mode to set the LMP automatic discovery type.
For example, set the discovery type of 11-N2SL64 on both NE3 and NE4 to DCC.
Step 4 Click Apply. Click Close in the Operation Result dialog box.
Step 5 Choose Configuration > SDH ASON > Control Link Management from the Main Menu.
Step 6 Click Synchronize. Check whether the control links between NEs are normal.
Step 7 Choose Configuration > SDH ASON > TE Link Management from the Main Menu.
Step 8 Click Synchronize. Check whether the TE links between NEs are normal.
----End

7.1.2 Disabling/Enabling the LMP Protocol

Usually it is not allowed to disable the LMP except in the following two cases. One is when an
ASON NE is connected with a traditional NE that is incapable of transparent transmission. The
other one is when an ASON NE has an optical interface that does not connect any fiber. In these
two cases, you can disable the LMP to release idle resources for a better resource allocation.
Prerequisite
WARNING
If the LMP is disabled, the ASON feature of the corresponding optical interface is disabled,
which severely affects ASON services. Hence, do not disable the LMP if not necessary.
Procedure
Function Tree.
Step 2 Click the ASON Protocol Management tab. Click Query to query the ASON protocol
information from the NE.
Step 3 Select the port at which the LMP is to be disabled. Double-click the LMP Protocol Status
column and choose Disabled from the drop-down list.
NOTE
If you need to enable the LMP, choose Enabled.

Step 6 Click Query. Queries LMP protocol status from the NE.
----End
7.1.3 Disabling/Enabling the OSPF Protocol

Usually it is not allowed to disable the OSPF protocol except in the following two cases. One
is when an ASON NE is connected with a traditional NE that is incapable of transparent
transmission. The other one is when an ASON NE has an optical interface that does not connect

any fiber. In the two cases, you can disable OSPF to release idle resources for a better resource
allocation.
Prerequisite
WARNING
If the OSPF protocol is disabled, the ASON feature of the corresponding optical interface is
disabled, which severely affects ASON services. Hence, do not disable the OSPF protocol if not
necessary.
Procedure
Function Tree.
Step 2 Click the ASON Protocol Management tab. Click Query to query the ASON protocol
information from the NE.
Step 3 Select the port at which the OSPF protocol is to be disabled. Double-click the OSPF Protocol
Status column. Choose Disabled from the drop-down list.
NOTE
If you need to enable the OSPF protocol, choose Enabled.
Step 5 Click Yes.The operation result dialog box is displayed, click Close.
Step 6 Click Query. Queries OSPF protocol status from the NE.
----End
7.1.4 Configuring the OSPF Protocol Authentication

You can query and set the OSPF protocol authentication to ensure the security of the ASON
network.
Prerequisite

The authentication conditions for an NE and its remote NE must be the same.
Procedure
Function Tree.
Step 2 Click the OSPF Protocol Authentication tab.
Step 3 Click Query.
Step 4 Double-click Authentication Mode or Authentication Key to set the two parameters.
NOTE
l The following three options are available for Authentication Mode: Unconfigured, Plain Text
Password Authentication and MD5 Encryption Authentication.
l When the value is Plain Text Password Authentication, the authentication is performed based on the
specified password. In this case, the Authentication Key must be a string of a maximum of eight
characters.

Step 6 Click OK.
----End
7.1.5 Configuring the RSVP Protocol Authentication

You can query and set the resource reservation protocol (RSVP) authentication to ensure the
security of the ASON network. The authentication operation needs to be performed for two
neighboring NEs. Two neighboring NEs can implement protocol interworking only if the two
NEs have the same authentication type and authentication key.
Prerequisite
l The authentication conditions for an NE and its remote NE must be the same.
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > RSVP Protocol Management from the
Function Tree.
Step 2 Click Query.

Step 3 Click New. The RSVP Authentication Create dialog box is displayed.
Step 4 Set Neighboring Node, Type and Key.
NOTE
l The following two options are available for Authentication Mode: Unconfigured and MD5
Encryption Authentication.
Step 5 Click Apply and then click OK.
NOTE
After the RSVP authentication is successfully created. You can double-click the Authentication Mode column
and change the authentication type. Click Apply. The dialog box displayed, prompt the service survivability
may be affected, click Yes to apply the change.
----End
7.1.6 Creating Out-Fiber Control Channels

The out-fiber control channel implements the interconnection between two ASON domains. You
can use an Ethernet cable to connect two edge NEs of two ASON domains, and then manually
create an out-fiber control channel on the U2000.In this way, the communication between the
two ASON domains is realized at the control plane.
Prerequisite
You can create an out-fiber control channel as shown in Figure 7-3. In this example, NE3 in the
ASON001 domain and NE6 in the ASON002 domain are connected by an Ethernet line. NE3
and NE6 are connected to NE9 through fibers.

Figure 7-3 Creating out-fiber control channels

NE1 NE4 NE5 NE8
NE2 NE3 NE6 NE7

ASON001 NE9 ASON002
: ASON NE
: Traditional NE
: Fiber
: Ethernet link
NOTE
l You need to create an out-fiber control channel and a TE link on the NE that connects the two ASON
domains.
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > Link Management Protocol from the
Function Tree.
Step 2 Click the LMP Control Channel tab. Click Query to query control channels of the link
management protocol from the NE.
Step 3 Click New and the Create Control Channel dialog box is displayed. Enter a value in the Remote
Address and Next Hop Address fields respectively.

NOTE
The remote address and the next hop address are the node ID of the remote NE. As shown in the Figure
7-3, the two addresses are consistent.
l As shown in Figure 7-3, if only one Ethernet link exists between the source and the sink, the two
addresses are consistent.
l If a hub exists on the Ethernet link between the source and the sink, the two addresses are consistent.
l If a switch exists on the Ethernet link between the source and the sink, the remote address is the node
ID of the sink NE and the next hop address is the IP address of the switch.
l If a router exists on the Ethernet link between the source and the sink, the remote address is the node
ID of the sink NE and the next hop address is the IP address of the router.
l If a local area network (LAN) exists on the Ethernet link between the source and the sink, the remote
address is the node ID of the sink NE and the next hop address is the IP address of the LAN that connects
to the source NE.
For example, if NE3 is the source, the remote address and the next hop address are the node ID
of NE6.
Function Tree.
Step 6 Click the OSPF IP Address Management tab.
Step 7 Click Query.
Step 8 Find the source or sink NE of the newly created out-fiber control channel. Double-click IP or
Mask to set the parameters.
Step 9 Click Apply. Click Close in the Operation Result dialog box.
Step 10 Creating a Virtual TE Link.

If NE3 is the source, you need to create the virtual TE link between NE3 and NE6.
----End
7.2 Managing Link Resources

ASON is capable of automatically switching optical network connections under the control of
the signaling network. It dynamically allocates network resources as required. As the network
is growing larger, a more reasonable way of resource management is required to make the most
of the network resources and to improve the network efficiency. Link resource management is
one aspect of resource management. In an actual network, thousands of connections may exist
between two nodes, while each connection may be composed of multiple data links. Usually,
there are links that have the same attributes according to a route protocol. These links are
regarded as a whole, which is known as the traffic engineer link (TE link), serving as the
processing object of the route information.
7.2.1 Configuring the Link Distance

You can set the link distance on the U2000 for route calculation. If you want to use the physical
distance between NEs as one element for the route calculation, you need to set the TE link
distance according to the actual physical distance.

Prerequisite
l TE link management is based on correct link information.
Procedure
Step 1 Choose Configuration > SDH ASON > TE Link Management from the Main Menu.

NOTE
Step 4 Select a link, double-click the Distance(km) field, and enter a value.
----End
7.2.2 Setting the Usage Threshold of Fiber Resources

The usage threshold of the fiber resources can be set according to the requirements of the
customer. When the fiber resource occupancy exceeds the usage threshold, the system reports
the CP_TEL_EXHAUST alarm.
Prerequisite
l The ASON network must run normally.
Procedure
Step 1 Select the NE in the Main Topology. Right-click and choose NE Explorer from the shortcut
menu.
Step 2 Choose ASON > Optical Fiber Resource Threshold Management from the Function Tree.
Step 3 Select the fiber. Click the Resource Threshold column and enter the planned resource usage
threshold.
NOTE
The default value of Resource Threshold is 75.
Step 4 Click Apply to validate the settings.
----End
7.2.3 Creating an SRLG

Fibers in the same optical cable have the same risk. If the cable is cut, all fibers are also cut.
During the service rerouting, services should not be rerouted to the link that belongs to the same
shared risk link group (SRLG). Therefore, you need to set the same SRLG value for TE links
that share the same risks in the network.

Prerequisite
l The TE link data has been synchronized on the U2000.
Service Requirement
See Figure 7-4. All NEs are ASON NEs. NE4 and NE5 are in the same equipment room. The
fiber between NE1 and NE4, and the fiber between NE1 and NE5 are within the same cable. In
this situation, the TE links of the two fibers share the same risk.
Figure 7-4 SRLG schematic diagram
NE1 NE4
NE5
NE2 NE3
NE1 NE4
NE5
NE2 NE3
Procedure
Step 1 Choose Service > SDH ASON > TE Link Management from the Main Menu.
Step 2 Choose Service > WDM ASON > TE Link Management from the Main Menu.
Step 3 Select the TE links. Double-click the SRLG field and enter a value. In this example, the same
field value should be applied to the SRLG of the TE link between NE1 and NE4 and the one of
the TE link between NE1 and NE5.

NOTE
After you modify the attributes, the TE link in the opposite direction is automatically set to the same SRLG
value.
----End
7.2.4 Querying the Information About the Timeslots on the Link

Sections
The TE link that is configured with MSP is divided into several sections. The sections of the TE
link can be of the working, protection, non-protection attribute, or virtual link. You can query
Protection, Switching Status, Total Timeslots, Timeslots Available for ASON, and Idle
Timeslots for each link section.
Prerequisite
l You must be an NM user with "NE operator" authority or higher..
l The ASON feature must be enabled.
Procedure
Step 1 Choose Configuration > SDH ASON > Component Link Management from the Main Menu.
Step 2 In the SDH Component Link Management window, click Synchronize.
Step 3 Select the member link to be queried. Right-click and choose Query Link Timeslot
Segmentation from the shortcut menu.
Step 4 In the Query Link Timeslot Segmentation window, click Query. The information about
Protection, Switching Status, Total Timeslots, Timeslots Available for ASON, and Idle
Timeslots is displayed.
----End
7.2.5 Setting Resource Reservation

You can configure the board ports and timeslots that are reserved for the permanent connections
on an ASON NE. Both ASON trails and permanent connections can be created in an ASON
network. Link resource reservation means that some timeslots of a link are reserved for the

creation of permanent connections. The reserved timeslots cannot be used when ASON trails
are created and or rerouted.
Prerequisite
Service Requirement
There are services running on NE1, NE2, NE3 and NE4. According to the planning, two months
later, four unprotected traditional services will be created between NE5 and NE6. These services
are required to pass NE3 and NE4. In this case, you need to reserve for the planned services
some timeslots between NE3 and NE4 to prevent the timeslots from being occupied by rerouted
ASON services.
Figure 7-5 Reserved link resources

NE5
NE1 NE4
NE6
NE2 NE3
: ASON NE
: Traditional NE
Board Configuration
To meet the previously mentioned service requirements, you can configure the boards as shown
in Figure 7-6. The 11-N2SL64 of NE3 and 8-N2SL64 of NE4 are connected by fibers.

Figure 7-6 Board configurations on NE3 and NE4
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
H Q Q Q C C C I I I
4 6 6 6 C 2 1 U U U
1 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Procedure
Step 1 To reserve link resources at the network layer, perform the following operations:
1. Choose Configuration > SDH ASON > Component Link Management from the Main
Menu.
2. Click Synchronize. The list displays all component links on the U2000. You can view the
information of each component link.
3. Set the filter criteria as required. Click Filter.
4. Select a link in the list, right-click it and choose Set Resource Reservation from the
shortcut menu. The Set Resource Reservation dialog box is displayed.
For example, select a component link.
l Source NE: NE3
l Source Port: 22-N4SLQ64-1(SDH-1)
l Sink NE: NE4
l Sink Port: 22-N4SLQ64-1(SDH-1)
Right-click the component link and choose Set Resource Reservation from the shortcut
menu.
5. Set timeslots in Resource Reservation. Click Apply.
For example, click timeslots 33-36 to reserve the four timeslots.
NOTE
If you want to cancel the resource reservation settings, click the reserved timeslot(s) that are
configured.
6. Click Close in the Operation Result dialog box.

7. Click Cancel in the Set Resource Reservation dialog box . The link resources are reserved.
Step 2 Optional: To reserve link resources on a per-NE basis, perform the following operations:
1. In the NE Explorer, select a board of an ASON NE and choose ASON > Resource
Reservation Management from the Function Tree.
2. Click Query to query the resource reservation status of the board from the NE.
3. Select the VC4 channel to be reserved and set the reservation status to Yes.
For example, set the reservation status of the channels from NE3-11-N2SL64-1(SDH-1)-
VC4:33 to NE3-11-N2SL64-1(SDH-1)-VC4:36 to Yes.
4. Click Apply and a dialog box is displayed telling that the settings are applied.
5. In the opposite station, repeat step a to step d to reserve link resources.
----End
7.2.6 Creating a Virtual TE Link

Without a TE link, ASON services cannot be created between a traditional NE and an ASON
NE. A virtual TE link, however, uses traditional resources to implement the creation and
protection for ASON services between traditional NEs and ASON NEs. You can directly create
ASON services on TE links.
Prerequisite
Service Requirement
See Figure 7-7. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 is a traditional NE. In this
scenario, a TE link can be created between NE3 and NE4. With the TE link, an ASON service
can be rerouted to the NE3-NE5-NE4 route.
Figure 7-7 Virtual TE link

NE1 NE4
Virtual TE link
NE5
NE2 NE3
: ASON NE
: Traditional NE

Board Configuration
To meet the previously mentioned service requirements, you can configure the boards on NE3
and NE4 as shown in Figure 7-8, and configure the boards on NE5 as shown in Figure 7-9. The
22-N4SLO16 of NE3 and the 6-N1SL16 of NE5 are connected. The 22-N4SLO16 of NE4 and
the 13-N1SL16 of NE5 are connected.
FAN
A
EF U
I1
S S S S S
L L L L L S S S F F F
O O Q Q Q C C C I I I
1 1 6 6 6 C 2 1 U U U
6 6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Figure 7-9 Board configuration for NE5

NOTE
You need to create 16 VC4 cross-connections between 6-N1SL16 and 13-N1SL16 on NE5 in advance.
Currently, you can create a TE link by adding a component link. On some occasions, (for
example, when the J0 byte is down), the link management protocol cannot automatically discover
TE links. In this case, you can create a TE link by manually creating a component link.
Procedure
Step 1 To create a TE link by directly creating a virtual TE link, perform the following operations:
1. Choose Configuration > SDH ASON > TE Link Management from the Main Menu.
2. Click Synchronize.
3. Click Maintenance and choose Create Virtual TE Link. The Create Virtual TE Link
dialog box is displayed.
4. Enter the attributes of the TE link.
For example, set the source NE to NE3 and the source port to 22-N4SLO16-1(SDH-1) (The
optical interface must be the one connected to NE5). Set the sink NE to E4, and the sink
port to 22-N4SLO16-1(SDH-1) (The optical interface must be the one connected to NE5).
Set the extended type to ASON Trail Creation.
NOTE
l The extended type has two options: ASON Trail Creation or Fault Detection Only.
l When the TE link is used to create a service, select ASON Trail Creation.
l If an MSP spans an ASON network and an SDH network over the boundary between the two
networks, select Fault Detection Only. If for the second time, the fiber cut happens to a gold
service, the virtual TE link is broken and triggers the rerouting.
5. Click OK.
Step 2 To create a TE link by creating a component link, perform the following operations:
1. Choose Configuration > SDH ASON > Component Link Management from the Main
Menu.
2. All the component links are displayed in the list. You can view all the information about
the links.
3. Click Create. The Create Component Link dialog box is displayed.
4. Set or enter a value for each parameter of the link and click OK.
NOTE
After the component link is successfully created, a TE link that corresponds to the component link
is automatically displayed in the SDH TE Link Management window. If the component link is
deleted, the corresponding TE link automatically disappears.
----End
7.3 Creating ASON Services

The trail levels that an ASON trail supports are as follows: diamond, gold, silver, copper and
iron. The trail levels that an ASON server trail supports are as follows: diamond, gold, silver

and copper. A label switched path (LSP) is a trail passed through by an ASON service. It is also
called an ASON trail.
The U2000 provides the end-to-end ASON trail management feature and supports services at
five classes of service (CoS) as follows:
l Diamond service: provides 1+1 protection (for example, SNCP) and rerouting ability.
l Gold service: provides 1:1 protection (for example, MSP) and rerouting ability.
l Silver service: provides rerouting services and re-calculates a route in the real time.
l Copper service: does not provide protection in the case of a fault.
l Iron service: extra services which can be preempted and have no protection.
7.3.1 Creating a Diamond ASON Service

You can create an ASON trail with the diamond-class protection.
Prerequisite
resources.
When you create a diamond service, you need to properly configure the rerouting attributes as
required. The following descriptions are based on the permanent 1+1 diamond service.
Service Requirement
See Figure 7-10. A permanent 1+1 diamond service at the rate of 155 Mbit/s is required between
NE1 and NE3. The working LSP is required to pass NE2 and the protection LSP is required to
pass NE4.
Figure 7-10 Diamond service requirement
NE1
Working LSP
Protection LSP
NE2 NE4
NE3 : ASON NE
: LSP

Board Configuration
in Figure 7-11.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
H Q Q Q C C C I I I
4 6 6 6 C 2 1 U U U
1 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
To meet the previously mentioned service requirement, you can refer to Table 7-1 to plan the
diamond service.
Table 7-1 Diamond service planning
Attribute NE1<->NE3
Source NE NE1
Source board-port 22-SLH41-1
Source timeslot 1
Sink NE NE3
Sink board-port 22-SLH41-1
Sink timeslot 1
SNCP Access None

Attribute NE1<->NE3
Route constraint Working path: NE1-NE2-

NE3; protection path: NE1-
NE4-NE3
Rerouting attributes Revertive Mode Non-Revertive
Lockout Unlocked
Priority High
Trigger condition Reroute when one trail fails
CrankBack 1
Policy Use existing trails whenever

possible
Rerouting Triggered by B3 No
Bit Error
Procedure
Step 1 Choose Configuration > SDH ASON > ASON Trail Management from the Main Menu.
Step 2 Choose Create > ASON Trail, and the creation wizard is displayed.
Step 3 In Basic information, enter the basic information of the ASON trail.
For example, enter the trail information as follows:
l Name: NE1-NE3-ASON-Trail-0001
l Type: ASON Trail
l Class: Diamond
l Concatenation Type: Non-Concatenation
l OVPN Customer: Share Resource
Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.
For example, enter the attributes as follows:
l Revetrive Mode: Non-Revetrive
l Lockout: Unlocked
l Priority: High
l CrankBack: 1
l Policy: Use existing trail whenever possible
l Rerouting Triggered by B3 Bit Error: No
Step 5 Set the source NE. In the right-hand topology, double-click the sink NE and select a slot, port
and timeslot from the dialog box displayed. Click OK.

For example, select the SLH41 in slot 22, the port 1 and the timeslot 1.
Step 6 Set the sink NE. In the right-hand topology, double-click the sink NE and select a slot, port and
timeslot from the dialog box displayed. Click OK.
to view the related route information.
NOTE
If you check the Automatic Pre-Calculate check box, the U2000 issues a command for the NE to perform
the automatic pre-calculation. Every change of the route constraints, the source/sink, or the protection type
triggers an automatic pre-calculation.
Step 8 Optional: Set Explicit Node or Explicit Link. Right-click an NE in the right-hand topology
and select an option from the shortcut menu as needed.
NOTE
l If you want to specify the timeslot when setting the explicit link, choose Browse from the shortcut
menu.
l After you select the Set Explicit Link shortcut menu item, its submenu is displayed in a folded manner
if there are more than ten available explicit links.
l To cancel the Explicit Node or Explicit Link, right-click an NE and choose Cancel Explicit Node or
Cancel Explicit Link.
For example, you can do as follows:
l Select the Working option button. Right-click NE2 in the right-hand topology and choose
Set As Explicit Node from the shortcut menu.
l Select the Protection option button. Right-click NE4 in the right-hand topology and choose
Step 9 Optional: Set Excluded Node or Excluded Link. Right-click an NE in the right-hand topology
NOTE
If you need to cancel the Excluded Node or Excluded Link, right-click an NE and choose Cancel
Excluded Node or Cancel Excluded Link from the shortcut menu.
Step 10 Optional: Set the Activate or Duplicate after created check box.

NOTE
l If you check the Activate check box, a created trail is applied to the NE so that the trail is in the activated
state.
l If you check the Duplicate after created check box, after a trail is created, you can create multiple
trails that share the same source and sink by duplicating the created trail.
Step 11 Verify that the trail information and route restrictions are correctly entered. Click Apply. If the
creation is successful, the system prompts that the operation was successful.
NOTE
To change the route restriction, select one or multiple route restrictions from the Route Restriction pane,
right-click and choose Delete from the shortcut menu. The selected route constraint is deleted. Repeat Steps
8 through 10 to set new route constraints.
Step 12 Click Close. If the system prompts that the route calculation fails, check whether the route
constraints are proper and whether the link resources are sufficient. Then start the configuration
again from Step 1.
Step 13 Click Cancel to go back to the SDH ASON Trail Management window. You can see the
detailed descriptions of the service.
----End
7.3.2 Creating a Gold ASON service

You can create an ASON trail with the gold-class protection. When you create a gold service,
primarily use the working TE links. If the working TE links are insufficient, you can use the
unprotected TE link resources. It is recommended that you ensure that sufficient working
resources are available in the network before you create a gold service.
Prerequisite
l The U2000 must have synchronized the links of the entire network and have sufficient link
resources.
l All links that the ASON trail passes through are under MSP protection. Otherwise, you
need to create fibers and configure the MSP protection before creating 1:1, 1:N, or 1+1
protected ASON trails.
The U2000 supports displaying the valid route of a gold service after multiplex section (MS)
switching. The requirements of realizing the function are as follows:
l The license for end-to-end must be available.
l The gold service must be managed in the end-to-end mode.
l The MS protection (MSP) ring on which the gold service runs must be searched out.
l When you query the valid route on the U2000 after the MS switching of a gold service
occurs, if the network interface fails to return the route data, the returned data is null, or
the returned route segment does not contain the information of source and sink NEs of
ASON route segment, the query of valid route fails. In this case, the actual route of the
ASON module is displayed.
Service Requirement
See Figure 7-12. Four ASON NEs compose an MSP ring. A gold service at the rate of 155 Mbit/
s is required between NE1 and NE3.

Figure 7-12 Gold service requirement

NE 1
NE 2 MSP NE 4
Ring
NE 3 : ASON NE
Board Configuration
To meet the previously mentioned service requirement, you can configure the boards on the NEs
as shown in Figure 7-13.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
H Q Q Q C C C I I I
4 6 6 6 C 2 1 U U U
1 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
To meet the service requirement, you can refer to Table 7-2 to plan a gold service.

Table 7-2 Gold service planning
Attribute NE1<->NE3
Source NE NE1
Source timeslot 1
Sink NE NE3
Sink timeslot 1
Protection class gold
Route constraint The service route must pass

NE2.
SNCP Access None
Rerouting attribute Revertive Mode Non-revertive
Lockout Unlocked
Priority Low
CrankBack 1

possible
Bit Error
The procedure for creating a gold ASON trail is similar to that described in "Creating a Diamond
ASON Trail". The difference lies in that the protection type is Gold.
Procedure
l Type: ASON Trail
l Class: Gold


l Revetrive Mode: Non-Revetrive
l Lockout: Unlocked
l Priority: Low
l CrankBack: 1
NOTE
NOTE
menu.
For example, select Working. Right-click NE2 in the right-hand topology and choose Set As
Explicit Node from the shortcut menu.

NOTE
NOTE
state.
NOTE
again from Step 1.
----End
7.3.3 Creating a Silver ASON Service

You can create an ASON trail with the silver-class protection. If a silver ASON trail fails, the
rerouting is periodically initiated until the trail is successfully rerouted. If the network resource
is insufficient, the service may be interrupted. Since the system calculates the reverting trail for
a silver trail in real time, you do not need to reserve resources for it. In this sense, the silver
services have a high bandwidth utilization.
Prerequisite
resources.
Service Requirement
See Figure 7-14. The four NEs are all ASON NEs. A silver service at the rate of 155 Mbit/s is
required between NE1 and NE3.

Figure 7-14 Silver service requirement

NE1
NE2 NE4
: ASON NE
NE3 : ASON Trail
Board Configuration
To meet the previously mentioned service requirement, you can configure the boards on the NEs
as shown in Figure 7-15.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
H Q Q Q C C C I I I
4 6 6 6 C 2 1 U U U
1 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
To meet the service requirement, you can refer to Table 7-3 to plan a silver service.

Attribute NE1<->NE3
Source NE NE1
Source timeslot 1
Sink NE NE3
Sink timeslot 1
SNCP Access None

NE2.
Rerouting attribute Revertive Mode Automatically Revertive
Lockout Unlocked
Priority Low
CrankBack 1

possible
Bit Error
The procedure for creating a silver ASON trail is similar to that described in "Creating a Diamond
ASON Trail". The difference lies in that the protection type is Silver.
Procedure
l Type: ASON Trail
l Class: Silver


l Revetrive Mode: Automatically Revetrive
l WTR Time(s): 600
l Lockout: Unlocked
l Priority: Low
l CrankBack: 1
l Rerouting Triggered by B3 Bit Error
NOTE
NOTE
menu.
For example, select Working. Right-click NE2 in the right-hand topology and choose Set As
Explicit Node from the shortcut menu.

NOTE
NOTE
state.
NOTE
again from Step 1.
----End
7.3.4 Creating a Copper ASON Service

You can create an ASON trail with the copper-class protection. Copper services are not used
often. Usually they are used to configure temporary services.
Prerequisite
resources.
Service Requirement
See Figure 7-16. The four NEs are all ASON NEs. A copper service at the rate of 155 Mbit/s
is required between NE1 and NE3.

Figure 7-16 Copper service requirement

NE1
NE2 NE4
: ASON NE
NE3 : ASON Trail
Board Configuration
in Figure 7-17.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
H Q Q Q C C C I I I
4 6 6 6 C 2 1 U U U
1 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
To meet the service requirement, you can refer to Table 7-4 to plan a copper service.

Table 7-4 Copper service planning
Attribute NE1<->NE3
Source NE NE1
Source timeslot 1
Sink NE NE3
Sink timeslot 1

NE2.
The procedure for creating a copper ASON trail is similar to that described in "Creating a
Diamond ASON Trail". The difference lies in that the protection type is Copper.
Procedure
l Type: ASON Trail
l Class: Copper
For example, select the SLH41 in slot 22, the port 4, and the timeslot 1.
NOTE

NOTE
menu.
For example, select the Working option button. Right-click NE2 in the right-hand topology and
choose Set As Explicit Node from the shortcut menu.
NOTE
NOTE
state.
NOTE
again from Step 1.
----End

7.3.5 Creating an Iron ASON Service

You can create an ASON trail with the iron-class protection. When you create an iron service,
primarily use the protection resource of a TE link. If the protection resource is insufficient, you
can use the non-protection resource of the TE link. It is recommended that you ensure sufficient
protection resources in the network before creating an iron service.
Prerequisite
resources.
l All links that the ASON trail passes through are under MSP protection. Otherwise, you
need to create fibers and configure the MSP protection before creating 1:1, 1:N, or 1+1
protected ASON trails.
Service Requirement
See Figure 7-18. The four ASON NEs compose an MSP ring. An iron service at the rate of 155
Mbit/s is required between NE1 and NE3.
Figure 7-18 Iron service requirement

NE 1
NE 2 MSP NE 4
Ring
NE 3 : ASON NE
Board Configuration
in Figure 7-19.

FAN
A
EF U
I1
S S S S
L L L L S S S F F F
H Q Q Q C C C I I I
4 6 6 6 C 2 1 U U U
1 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
To meet the service requirement, you can refer to Table 7-5 to plan an iron service.
Table 7-5 Iron service planning

Attribute NE1<->NE3
Source NE NE1
Source timeslot 1
Sink NE NE3
Sink timeslot 1
Protection class Iron

NE2.
The procedure for creating an iron ASON trail is similar to that described in "Creating a Diamond
ASON Trail". The difference lies in that the protection type is Iron.

Procedure
l Type: ASON Trail
l Class: Iron
NOTE
NOTE
menu.

NOTE
NOTE
state.
NOTE
again from Step 1.
----End
7.3.6 Creating an ASON Server Trail

An ASON server trail is mainly used to carry lower order services (VC3 or VC12). An ASON
server trail is applicable to diamond, gold, silver, or copper services. At the NE side, an ASON
server trail is also called a tunnel service.
Prerequisite
resources.
Service Requirement
The following descriptions are based on a diamond ASON server trail. See Figure 7-20. Eight
VC12 services need to be transmitted between NE5 and NE6, and the diamond-class protection
is required for these trails. In this case, you need to configure ASON server trails.

Figure 7-20 Diamond ASON server trail requirement

NE5
VC12
NE1
Working Protection
NE2 NE4
Diamond tunnel Diamond tunnel

NE3
: ASON Backbone layer NE

VC12 : ASON Access layer NE
NE6
Board Configuration
in Figure 7-21.

Service Planning
To meet the service requirement, you can refer to Table 7-6 to plan a diamond ASON server
trail.
Table 7-6 Diamond ASON server trail planning

Attribute NE5<->NE6
Source NE NE5
Source board-port 2-PQ1
Source timeslot 1-8
Sink NE NE6
Sink board-port 2-PQ1
Sink timeslot 1-8
ASON server trail Diamond ASON server trail
SNCP Access None
Route constraint Working path: NE5-NE1-

NE2-NE3-NE6; protection
path: NE5-NE1-NE4-NE3-
NE6
Rerouting attributes Revertive Mode Non-revertive
Lockout Unlocked
Priority High
Rerouting trigger condition Reroute when one trail fails
CrankBack 1
Rerouting policy Use existing trails whenever

possible
Bit Error
Procedure

l Type: ASON Server Trail
l Class: Diamond
l Revertive: Non-Revertive. (For revertive ASON server trails, select Revertive, For
scheduled revertive ASON server trails, select Scheduled revertive.)
l Lockout: Unlocked
l Priority: High
l CrankBack: 1
Step 5 On the left-hand side of the window, click Browse beside Source. In the dialog box displayed,
select the desired NE, slot, port, or timeslot. Click OK.
Step 6 On the left-hand side of the window, click Browse beside Sink. In the dialog box displayed,
select the desired NE, slot, port, or timeslot. Click OK.
NOTE
Step 8 Set Explicit Node or Explicit Link. Right-click an NE in the right-hand topology and select an
option from the shortcut menu as needed.
NOTE
menu.
For example, you can do as follows:
l Select the Working option button. Right-click NE2 in the right-hand topology and choose

l Select the Protection option button. Right-click NE4 in the right-hand topology and choose
NOTE
NOTE
state.
NOTE
again from Step 1.
----End
7.3.7 Creating Two Associated ASON Trails

The ASON trail association function associates two services so that the two services are not
preempted by each other during the rerouting and optimization. Two services that are transmitted
from the same source node can be associated.
Prerequisite
Application Scenario
As shown in Figure 7-22, the 1+1 services need to be created between R1 and R2 and pass
through the ASON network. To ensure that the two trails do not pass through the same ASON
node, the two ASON trails must be associated. After the two ASON trails are associated, one
ASON trail will not be rerouted to the other ASON trail.

Figure 7-22 Two associated ASON trails
E I
R1
F
A
C
B
H R2
G
: ASON NE
: User Equipment
NOTE
Currently, association is supported between silver trails, between copper trails, between silver and copper
trails, between silver server trails, between copper server trails, and between silver and copper server trails.
Procedure
Step 2 In the SDH ASON Trail Management window, choose Create > Association Trail.
Step 3 In the SDH ASON Association Trail window, enter Basic Information and Route
Restriction of trail 1 and trail 2. The example is provided as follows:

NOTE
Trail 1 and trail 2 must have the same source.
Step 4 Set the common attributes, including the Revertive Mode, WTR Time, Lockout, Priority,
CrackBack, Policy, Rerouting Triggered by B3 Bit Error and Rerouting Hold-off time.
Step 5 Click Apply. After confirmation, apply the configuration.

Step 6 Click Cancel to go back to the SDH ASON Trail Management window. You can see the detailed
descriptions of the service.
----End
7.3.8 Setting ASON Trail Association

ASON trail association means two ASON trails are associated. The associated trails are separated
from each other during the service optimization and rerouting whenever possible. Service
association is applied to access services that have two access points. After two trails are
associated, if one of the trails (or server trails) is rerouted or optimized, the ASON NE adopts
the 1+1 routing policy to try to avoid the associated ASON trail (or server trail).
Prerequisite

l Currently, association is supported between silver trails, between copper trails, between
silver and copper trails, between silver server trails, between copper server trails, and
between silver and copper server trails.
l The system supports automatically setting association only for SNCP ASON-SDH trails
in a single domain. For SNCP ASON-SDH trails in multiple domains, you need to manually
set association.
l Associating the two trails may clear their preset restoration trails.
Procedure
Step 2 In the SDH ASON Trail Management list, select two ASON trails to be associated. Right-click
them and choose Set Association.
Step 3 In the confirm dialog box, click Yes. A dialog box appears telling you that the operation was
successful.
Step 4 Click Close.
Step 5 Optional: Select an ASON trail in the SDH ASON Trail Management list. Right-click and
choose Set Association Source from the shortcut menu. Select another ASON trail, right-click
and choose Set Association from the shortcut menu. In the confirm dialog box, click Yes. A
dialog box appears, telling that the trails are successfully associated. Click Close.
NOTE
To cancel the association relations, right-click and choose Remove Association. A dialog box is displayed
indicating that this operation may decrease the service protection ability.
Step 6 Select a trail in the SDH ASON Trail Management list. You can know whether the association
is successful by viewing the value of Associated or Not.
Step 7 Optional: In the lower left area of the SDH ASON Trail Management window, click the
Associated Route tab to view the information about the two associated trails.
----End
7.3.9 Creating ASON Services in Batches

The batch creation function is always used if a large number of ASON services need to be created.
Prerequisite
resources.
Service Requirement
See Figure 7-23. The four NEs are all ASON NEs. Three non-revertive silver services at the
rate of 155 Mbit/s are required to be configured between NE1 and NE3.

Figure 7-23 Batch silver service requirement

NE1
NE2 NE4
: ASON NE
NE3 : ASON Trail
Board Configuration
in Figure 7-24.
FAN
A
EF U
I1
S S S S S
1 1 6 6 6 C 2 1 U U U
6 6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
To meet the service requirement, you can refer to Table 7-7 to plan a silver service.

Attribute NE1<->NE3
Source NE NE1
Source board-port 22-N4SLO16-1 22-N4SLO16-1 22-N4SLO16-1
Source timeslot 6 7 8
Sink NE NE3
Sink board-port 22-N4SLO16-1 22-N4SLO16-1 22-N4SLO16-1
Sink timeslot 6 7 8
Rerouting Reversion mode Non-revertive

attribute
Lockout Unlocked
Priority Low
CrankBack 1
Policy Use the existing trail whenever possible
Rerouting No
Triggered by B3
Bit Error
Rerouting Hold- 0
off time
Procedure
l Type: ASON Server
l Class: Silver

l Revetrive Mode: Non-Revetrive (Select Automatically Revertive or Scheduled

Revertive if the silver service is revertive.)
l Lockout: Unlocked
l Priority: Low
l CrankBack: 1
For example, select port 1 and timeslot 6 of the N1SL16.
NOTE
Step 8 Set Explicit Node or Explicit Link. Right-click an NE in the right-hand topology and select an
option from the shortcut menu as needed.
NOTE
menu.

NOTE
Step 10 Set the Activate or Duplicate after created check box.

NOTE
state.
NOTE
Step 12 Click Close. In the Copy dialog box displayed, select the source and sink timeslots. Click
Add.
For example, select the timeslots 7-8 of the source NE (NE1-22-N4SLO16-1(SDH-1)-VC4-7-8)
and the timeslots 7-8 of the sink NE (NE1-22-N4SLO16-1(SDH-1)-VC4-7-8).
Step 13 Check the Activate after Duplicate and Duplicate Route Constraint check boxes.
Step 14 Confirm that the trail and route information is correctly entered. Click OK.
Step 15 After the creation is complete, a dialog box appears, telling that the operation was successful.
Click Close.
----End
7.3.10 Deactivating the ASON Trail

Deactivating an ASON trail can release the resources that the trail occupies.
Prerequisite
NOTE
You do not need to cancel the association configured before deactivating the associated ASON service,
because the system automatically cancels the association during the deactivation operation.
During the SDH ASON trail management, if an active client trail exists, the corresponding ASON server
trail cannot be deactivated.
Procedure

Step 2 In the list, select the ASON trail to be deactivated. Right-click and choose Deactivate.
NOTE
After you deactivate trails in batches, wait for several minutes (for example, five minutes) before you
perform other operations. It is recommended not to deactivate trails in batches.
Step 3 Click Yes in the confirmation dialog box displayed twice.

NOTE
If the selected trails contain the trails that are managed by SDH trails, the confirmation dialog box is
displayed for the third time. Click Yes. The Operation Result dialog box is displayed indicating that the
operation fails. You can click Detail to view failure causes.
Step 4 After the operation is complete, the system prompts that the operation was successful. Click
Close. The list shows that the ASON trail is in the Inactive state.
----End
7.3.11 Deleting an ASON Trail

The operation of deleting ASON trails removes the trail data from the U2000 and the NE.
Prerequisite
l The ASON trail must be inactive.
NOTE
l Deleting an ASON trail removes the trail data from the U2000 and the NE. Exercise caution when you
perform this operation.
l In the SDH ASON Trail Management, if an active client trail exists, the corresponding ASON server
trail cannot be deactivated.
l When deactivating associated ASON trails, do not delete the association first. The system automatically
deletes the association during deactivation.
Procedure
Step 2 Select a deactivated ASON trail from the list, right-click, and choose Delete from the shortcut
menu.
Step 4 After the deletion is complete, a dialog box is displayed indicating that the operation was
successful. Click Close.
----End


7.4.1 Viewing WDM ASON Trail Attributes

You can view the detailed information about an ASON trail, including the basic attributes,
constraint routes, shared MESH restoration trail status information, associated ASON trail
attributes, and SLA-compliance.
Prerequisite
l An ASON trail must be created.
Procedure
Step 2 In the trail list, right-click the ASON trail that you want to view and choose Details from the
shortcut menu.
Step 3 In the dialog box displayed, view the basic attributes of the ASON trail.
Step 4 Click the Restrictive Route tab. View the route constraint information of the ASON trail.
Step 5 Optional: If an associated trail is set for the ASON trail, click the Associated ASON Trail
Attribute tab to view the attributes of the associated trail.

Step 6 Click the SLA-Compliant Details tab to view the details of the SLA-compliance of the WDM
ASON trail.
Step 7 Optional: If a shared MESH restoration trail is set, click the Shared MESH Restoration Trail
Status Details tab to view the details of the shared MESH restoration trail status.
----End
7.4.2 Setting the Routing Attributes

You can set the routing attributes for an ASON service, including rerouting revertive mode,
WTR time, scheduled revertive time, rerouting lockout status, revertive lockout, rerouting
triggered by B3 bit error, rerouting priority, trigger condition, times of crankbacks and route
selection policy.
Prerequisite
Procedure
Step 2 In the list displayed, select one or more ASON trails, right-click and choose Set Routing
NOTE
When you create an ASON trail, you can set the rerouting attributes. Click Create > ASON Trail. In the
ASON Trail Management user interface, click Routing Attributes tab to set the rerouting attributes.
Step 3 In the Set Routing Attributes user interface, set attributes of routing and click OK.
NOTE
l Currently, you can set trigger conditions of routing for diamond services only.
l Revertive Mode includes Non-Revertive, Scheduled Revertive, and Scheduled Revertive. If the
Revertive Mode is set as Scheduled Revertive, you need to set Scheduled revertive time.
Step 4 In the confirmation dialog box displayed, click Yes. A prompt appears telling you that the
operation was successful. Click Close.
----End

7.4.3 Setting the Scheduled Reversion Time

If the ASON service is rerouted successfully, you can set the scheduled reversion time after the
original trail is restored. Before the scheduled reversion time expires, the service is automatically
returned to the original trail. If you set the scheduled reversion time when the fault in the original
path is not rectified, the service may be interrupted.
Prerequisite
l The ASON service must be rerouted successfully.
l Revertive Mode of the ASON service must be set to Scheduled revertive.
Procedure
NOTE
Step 3 In Set Routing Attributes, select the Scheduled revertive time check box and set the time
limit within which the service must be returned to the original trail after the original trail is
restored.
----End
7.4.4 Setting the B3 Alarm to Trigger Rerouting

After the diamond service, gold service, or silver service is created, you can set the B3 alarm as
a condition for triggering rerouting.

Prerequisite
l The data of the ASON NEs must be configured and uploaded.
Procedure
NOTE
Step 3 In Set Routing Attributes, set Rerouting Triggered by B3 Bit Error to Yes.
NOTE
The B3_EXC and B3_SD alarms can trigger the rerouting.
----End
7.4.5 Setting Preset Restoration Trail

You can set priorities for rerouting ASON trails. When an ASON service is being rerouted, the
service has the priority to be restored to the preset trail. If the preset restoration trail is occupied,
the system computes the route again.
Prerequisite
l The rerouting ASON trail must be created.
resources.

Currently, the diamond, gold, and silver ASON trails and the silver ASON server trails support
setting the restoration reverting trail.
Procedure
Step 2 Select an ASON service and click Maintenance. Choose Set Preset Restoration Trail from
the drop-down menu.
Step 3 Click Pre-Calculation Route to view the related information. Click Apply to complete the
settings of the preset reverting trail.
NOTE
If the Automatic Pre-Calculation check box is checked, the U2000 sends a command to ask the NE to
precalculation.
Step 4 Optional: On the topology, right-click an NE and set the route constraints. Click the Route
Restriction to view or set the information of Explicit Node, Excluded Node, Explicit Link
and Excluded Link. Click Apply to complete the settings of the preset restoration trail.
----End
7.4.6 Setting Shared MESH Restoration Trail

You can preset a shared MESH restoration trail for an ASON trail. When an ASON service is
rerouted, you can restore the service to the preset trail with priority. The control plane reserves
the timeslot used by the shared MESH restoration trail. That is, the timeslot cannot be used by
other services during the service creation or rerouting.
Prerequisite
l Currently, only the revertive silver ASON trails and the silver ASON server trails support
setting the shared MESH restoration trail.
l If a timeslot is configured with a multiplex section, the timeslot is grayed out and cannot
be selected.
l Multiple revertive silver services can share the same shared MESH restoration trail.
Procedure
Step 1 Choose Configuration > Service > SDH ASON > ASON Trail Management from the Main
Menu.
Step 2 Select one revertive silver ASON service and click Maintenance. Select Set Shared MESH
Restoration Trail from the drop-down list.
Step 3 Click Pre-Calculation Route to view the related information. Click Apply to complete the
settings of the shared MESH restoration trail.

NOTE
If the Automatic Pre-Calculation check box is checked, the U2000 sends a command to ask the NE to
precalculation.
Step 4 Optional: On the topology, right-click an NE and set the route constraints. Click the Route
Restriction to view the information of Explicit Node and Excluded Node. Click Apply to
complete the settings of the shared MESH restoration trail.
----End
7.4.7 Setting the Original Route

The route of an ASON service is usually the original route when the service is created. If the
route of an ASON service changes, you can also set the route after change to the original route.
Prerequisite
For a non-revertive trail, if the original route is normally restored after trail rerouting, the trail
cannot automatically revert to the original route. For a revertive ASON service, if the failure is
cleared after rerouting, the service automatically reverts.
Procedure
Step 2 Set a trail that you want to set and click Maintenance. Choose Save As Original Route from
the drop-down menu.
Step 4 A dialog box is displayed indicating that the operation was successful. Click Close to complete
the setting of the original route.
Step 5 Optional: Set a trail for which the original route is already set and click Maintenance. Choose
Refresh Original Route from the drop-down menu.
----End

7.5.1 Reverting ASON Trails

After rerouting, you can revert an ASON trail to the original route or the route before rerouting,
based on the reverting function supported by the ASON.

Prerequisite
l The ASON trail must be created.
l ASON trails are classified into non-revertive ASON trails, automatically revertive ASON
trails and scheduled revertive ASON trails.
l For non-revertive ASON trails, you can specify whether they are restored to timeslots or
ports.
l For automatically revertive ASON trails, you can manually revert them to the routes before
rerouting.
l For scheduled revertive ASON trails, a fault of the original route is cleared after the
rerouting of a service in the scheduled reversion mode, you can set scheduled revertive
time to enable the service to revert at a specified time.
Procedure
l For non-revertive ASON trails
1. Choose Configuration > SDH ASON > ASON Trail Management from the Main
Menu.
2. Optional: Click Filter to set the filter criteria and set Whether Original Route Is
Active to No. Click Filter All. A dialog box is displayed. Click Yes.
3. In the list displayed, select one or more ASON trails to be reverted. Click the Original
Route tab to view the original routes of the ASON trails.
4. Choose Configuration > SDH ASON > TE Link Management from the Main Menu.
Check whether idle resources exist on the TE link of the original route.
5. In the SDH ASON Trail Management window, click Maintenance and select
Revert To Original Route > Revert to Port or Revert To Original > Revert to
Timeslot. The ASON trails then revert to the routes before rerouting.
6. A dialog box is displayed. Click Yes. The Restore to Port or Restore to Timeslot
dialog box is displayed indicating the operation result.
7. Click Close.
NOTE
You can click Retry to perform the restoration again.

l For automatically revertive ASON trails and scheduled revertive ASON trail
1. Choose Configuration > SDH ASON > ASON Trail Management from the Main
Menu.
2. Optional: Click Filter to set the filter criteria and set Whether Original Route Is
Active to No. Click Filter All. A dialog box is displayed. Click Yes.
3. In the list displayed, select one or more ASON trails to be reverted. Click
Maintenance and select Manual Revert from the drop-down menu. The ASON trails
then revert to the routes before rerouting.

NOTE
If the revertive mode is automatically revertive, you can set WTR time. When the original trail is
restored, the service is automatically returned to the original trail after a period of time.
If the revertive mode is scheduled revertive, you can set the scheduled revertive time after the original
trail is restored. Before the scheduled reversion time expires, the service is automatically returned to
the original trail.
----End
7.5.2 Optimizing an ASON Service

To manually adjust one or more service trails, you can use the optimization function to transfer
the service trails to the expected trails.
Prerequisite
l An ASON trail must be created.
l For a revertive silver service, you cannot perform the optimization operation when the
service is being reverted upon rerouting.
l Diamond and non-diamond service cannot be optimized in batches at the same time.
l ASON service in different domains cannot be optimized in batches.
Procedure
Step 2 In the list displayed, select one or more ASON trails that you want to adjust. Click
Step 3 Specify the explicit nodes, explicit links, excluded nodes, or excluded links to set the trail after
optimization.

Step 4 Optional: To save the optimization settings, check the Save Optimization Settings check box.
Step 5 Check whether the route adjustment is correctly set and click Apply.
The Operation Result dialog box is displayed.
Step 6 Click Close. A dialog box is displayed indicating that the operation saves the current route as
the original route.
NOTE
If you do not check the Set As Original Route Concurrently check box before clicking Apply, this dialog box
is not displayed.
Step 7 Click Yes. The Operation Result dialog box is displayed. Click Close.
Step 8 In the trail list, select the trail after optimization. You can view the route information of the trail
after optimization in the Actual Route.
----End
7.6 Migrating ASON Services

An ASON network supports the migration between traditional Services and ASON services, and
supports the in-service migration between ASON services at different levels.

7.6.1 Converting an ASON Service to a Traditional Service

After an ASON service is converted to a traditional service, you can use the trail search function
to manage the service in the SDH trail management.
Prerequisite
To convert the ASON route segment of an end-to-end trail that passes through an ASON network,
perform the following operations:
l Navigate to the SDH Trail Management window. Delete the ASON trail segment of the
trail from the network layer.
l Navigate to the SDH ASON Trail Management window. Convert the ASON trail segment
of the trail to an SDH service.
l Use the SDH trail search function to search again and manage the trail.
Procedure
Step 2 In the list displayed, right-click the ASON trail that you want to convert and choose Downgrade
to Traditional Service from the shortcut menu. In the confirmation dialog box displayed, click
Yes. If an error message is displayed indicating that the ASON trail cannot be downgraded
because it is managed by an SDH trail, this ASON service exists in the SDH Trail
Management window. You need to right-click the service in the SDH Trail Management and
choose Delete from Network Layer from the shortcut menu to downgrade it. Then, repeat Step
2.
NOTE
In this step, you can navigate to the SDH Trail Management window and view the ASON-SDH Trail
field in the list to check if the trail passes an ASON domain. If the trail passes an ASON domain, delete
the service from the network layer and then downgrade it in the ASON Trail Management window.
Step 3 After the conversion, choose Service > SDH Circuit > SDH Trail Search from the Main Menu.
You can search the service that is just converted.
NOTE
If you cannot search out this trail, wait for several minutes and search again. You can also synchronize the
NE cross-connections on the SDH ASON topology.
----End
7.6.2 Converting a Traditional Service to an ASON Service

You can convert a traditional service to an ASON service. This section describes how to upgrade
a traditional service to a non-revertive silver service.
Prerequisite

l A traditional service must be configured on an ASON NE.
l By default, SNCP services are converted to diamond services, MSP services are converted
to gold services or downgraded gold services, non-protection services are converted to
silver services, and protection timeslot services are converted to iron services. Inadaptable
services such as broadcasting and unidirectional services cannot be upgraded to ASON
services.
l If the entire trail exists on the ASON NE, you can upgrade the trail to an ASON trail. If
only part of the trail exists on the ASON NE, you can upgrade only the trail segment that
passes the ASON NE to an ASON trail.
l Partial upgrade means to upgrade part of the trail to an ASON service. Some part of the
trail is not in the ASON domain, so you cannot upgrade the entire trail to an ASON service.
Full upgrade is available for a trail that is within an ASON domain. A trail that is not within
the ASON domain cannot be fully upgraded to an ASON service.
Procedure
Step 1 Choose Service > SDH Circuit > SDH Trail Management from the Main Menu.
Step 2 In the list displayed, select one or more SDH trails that you want to upgrade. Right-click and
choose Upgrade to ASON Trail from the shortcut menu.
Step 3 In the dialog box displayed, enter the parameters of the ASON service.
For example,
l Class: Sliver.
l Revertive Mode: Non-Revertive.
l Rerouting Lockout: Unlocked.
l Rerouting Priority: Low Priority.
l Rerouting Policy: Use existing trails whenever possible.
----End
7.6.3 Migration Between ASON Services

The diamond service, gold service, silver service, and copper service can be migrated to each
other.
Prerequisite
l Silver services configured with the shared MESH restoration trail cannot be migrated.
l Associated services cannot be migrated to diamond services.

l The diamond service and gold service cannot be migrated to each other.
l This topic describes how to migrate a diamond service to a silver service. The procedure
is similar to the migration between a diamond service and a gold, silver, copper service.
Before you migrate an ASON service to a gold service, you need to create the MSP.
Procedure
Step 2 In the list displayed, right-click the diamond service that you want to convert and choose In-
Service Migration > Silver from the shortcut menu.
Step 3 Click Yes in the Prompt dialog box.

Step 4 The Confirm the route that you want to reserve dialog box is displayed. Confirm whether to
reserve the working route or the protection route for the desired diamond ASON service, and
correspondingly select Working Route or Protection Route.
NOTE
The route that you want to reserve can be selected only when a diamond service is migrated to a silver or copper
service.
Step 5 Click Yes in the Prompt dialog box. Then, you can query the rerouting attributes of the ASON
service as indicated.
----End

7.6.4 Migrating an ASON Server Trail to a Traditional Server Trail

You can perform migration between an ASON server trail and a traditional server trail.
Prerequisite
l The ASON server trail must be created.
The two ways of migrating an ASON server trail are as follows:
l In the SDH Trail Management window, use the Downgrade to Traditional Service
method to downgrade an ASON server trail.
l In the SDH ASON Trail Management window, use the Downgrade to Traditional
Service method to downgrade an ASON server trail.
The following procedure describes how to migrate an ASON server trail to a traditional server
trail in the second way.
Procedure
Step 2 Right-click the ASON server trail that needs to be downgraded and choose Downgrade to
Traditional Service from the shortcut menu. Click Yes in the confirmation dialog box. If a
message is displayed indicating that The ASON trail that an SDH trail manages cannot be
downgraded, it indicates that the ASON service exists in the SDH Trail Management window.
You need to navigate to the SDH Trail Management window, right-click the ASON service
and choose Delete from Network Layer from the shortcut menu. Repeat Step 2 to perform the
downgrade operation again.
NOTE
In this step, you can view the value of ASON-SDH Trail in the SDH Trail Management window to
determine whether the trail contains an ASON domain. If the trail contains an ASON domain, delete the
service from the network layer and then downgrade the service in the ASON Trail Management window.
Step 3 A prompt appears telling you that the operation was successful. Click Close.
Step 4 Optional: Choose Configuration > SDH ASON > ASON Trail Management from the Main
Menu. You cannot query the trail.
Step 5 Optional: Choose Configuration > SDH ASON > ASON Topology Management from the
Main Menu. Select all ASON NEs and click Synchronize Cross-Connection. A prompt appears
telling you that the operation was successful. Click Close.
Step 6 Choose Service > SDH Circuit > SDH Trail Search from the Main Menu. Click Next until
the operation is complete.
Step 7 Optional: Choose Service > SDH Circuit > SDH Trail Management from the Main Menu.
View the traditional server trail that is successfully migrated.
----End

7.6.5 Migrating a Traditional Server Trail to an ASON Server Trail

You can migrate a traditional server trail to an ASON server trail.
Prerequisite
Procedure
Step 2 In the list, select the traditional server trail that you want to migrate, right-click and choose
Upgrade to ASON Trail from the shortcut menu. The Upgrade to ASON Trail dialog box is
displayed.
----End
7.6.6 Migration Between ASON Server Trails

The migration between the diamond tunnel, gold tunnel, silver tunnel, and copper tunnel is
supported.
Prerequisite
l The silver server trail that is configured with the shared mesh restoration trail cannot be
migrated.
l The server trail that is associated with another trail cannot be migrated to diamond server
trails.
l This topic considers the migration from the diamond server trail to the silver server trail as
an example. The operations for the migration between the diamond server trail, gold server
trail, silver server trail, and copper server trail are similar. Before you migrate a server trail
into a gold server trail, however, you need to create the multiplex section.
Procedure
Step 2 Select the diamond server trail to be migrated from the list. Right-click and choose In-Service
Migration > Silver from the shortcut menu.
Step 3 Click Yes in the Prompt dialog box.
Step 4 The Confirm the route that you want to reserve dialog box is displayed. Select Working
Route if you determine to reserve the working route of the diamond server trail that needs to be

migrated. Select Protection Route if you need to reserve the protection route of the diamond
server trail that needs to be migrated. Then, click OK.
NOTE
You need to select the route to be reserved only when you migrate the diamond server trail to the silver or copper
server trail.
Step 5 Click Yes in the Prompt dialog box. Then, you can check the rerouting attributes of the ASON
trails.
----End
7.7 Creating ASON Trail Groups

An ASON trail group is often used with LCAS.
Prerequisite
An ASON trail group associates the member trails that belong to the same LCAS service to an
LSP group, and add, delete and modify these member trails in the ASON network. To enable
virtual concatenation services to have an enhanced fault tolerance capability, separate the
member trails whenever possible.
Each ASON trail group has an ID, which is the unique ID assigned by an ASON NE. The member
trails in the ASON trail group have the same source and sink, but the trails are separated whenever
possible. You can create an ASON trail group at the initial node only.
Service Requirement
See Figure 7-25. Create a GE service between NE1 and NE3, bind four VC4s to the service.
Configure an EGSH board each slot 20 of NE1 and NE3.
Figure 7-25 ASON trail group service requirement
ASON trail group(4×LSP)

NE4
NE1 NE3
NE2 : ASON NE
: LSP

Board Configuration
For the board configuration of NE1 and NE3, refer to Figure 7-26.
FAN
A
EF U
I1
S S S
E
L L L S S S F F F
G
Q Q Q C C C I I I
S
6 6 6 C 2 1 U U U
H
4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
FAN
A
EF U
I1
S S S
L L L S S S F F F
Q Q Q C C C I I I
6 6 6 C 2 1 U U U
4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN

Service Planning
Refer to Table 7-8 for GE service planning.
Table 7-8 GE service planning
Attribute NE1<->NE3
Source NE NE1
Source board-port 20-EGSH-1
Source timeslot VC4-1 to VC4-4
Source VCTRUNK VCTRUNK1
Bound bandwidth 4 x VC4
LCAS Start
Sink NE NE3
Sink board-port 20-EGSH-1
Sink timeslot VC4-1 to VC4-4
Sink VCTRUNK VCTRUNK1
ASON trail group The group ID is 1
Member trail Four silver services from NE1-EGSH to NE3-EGSH
Procedure
Step 1 In the Main Topology, right-click NE1 and choose NE Explorer from the shortcut menu.
Step 2 Select 20-EGSH and set the interface parameters according to Table 7-8.
Step 3 In the Main Topology, right-click NE3 and choose NE Explorer from the shortcut menu.
Step 4 Select 20-EGSH and set the interface parameters according to Table 7-8.
Step 5 Select four silver services from NE1-20-EGSH to NE3-20-EGSH.
Step 6 In the NE Explorer, select NE1 and choose ASON > ASON Trail Group from the Function
Tree.
Step 7 Click Create, and enter the ID and name of the ASON trail group. Click Apply.
Step 8 Select the created ASON trail group and click Add.
Step 9 Select the four created silver services and click OK.
----End

7.8 Creating Services Between an ASON NE and a

Traditional NE
7.8.1 Creating a VC4 Service Between Two Traditional NEs with

ASON NEs in Between
You can create end-to-end VC4 services between two traditional NEs with ASON NEs in
between.
Prerequisite
Service Requirement
A VC4 service needs to be configured between NE5 and NE6. This service is required to be an
Figure 7-28 VC4 service requirement between traditional NEs

NE1 NE4
NE6 NE5
VC4 VC4
NE2 NE3
Board Configuration
Figure 7-29 shows how the boards are configured on NE1, NE2, NE3 and NE4.

Figure 7-29 Board configuration for NE1-NE4
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
O Q Q Q C C C I I I
1 6 6 6 C 2 1 U U U
6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Figure 7-30 shows how the boards are configured on NE5 and NE6.
FAN
A
EF U
I1
S S S
L L L S S S F F F
O O H C C C I I I
1 1 4 C 2 1 U U U
6 6 1
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning

Table 7-9 VC4 service planning between traditional NEs

Attribute NE6<->NE5
Source NE NE6
Source board-port 26-N3SLH41-1
Source VC4 1
Sink NE NE5
Sink board-port 26-N3SLH41-1
Sink VC4 1
You can use the following two ways to create a VC4 service between traditional NEs that cross
an ASON domain.
l Use the trail feature of the U2000 to directly create a VC4 service.
l Create a silver service within the ASON domain. Then create VC4 cross-connections on
NE5 and NE6.
The following illustrates how to create such a VC4 trail in the first way.
Procedure
Step 2 Choose Create/Modify > Create Trail.
l Level: VC4
l Source: NE6-26-N3SLH41-1(SDH-1)-VC4:1
l Sink: NE5-26-N3SLH41-1(SDH-1)-VC4:1

protection type.
Step 6 In the SDH Trail Management window, click Filter and select Filter All.
Step 7 Choose Service > SDH Circuit > SDH Trail Management from the Main Menu. View the
detailed route information of the VC4 trail that is created. You can also view the value of ASON-
SDH Trail to check whether the ASON section of the ASON-SDH trail is successfully created.
Step 8 Choose Configuration > SDH ASON > ASON Trail Management from the Main Menu. You
can view the ASON trail information.
----End
7.8.2 Creating a VC12 Service Between Two Traditional NEs within

ASON NEs in Between
You can create end-to-end VC12 services between two traditional NEs within ASON NEs in
between.
Prerequisite

Service Requirement
A VC12 service needs to be configured between NE5 and NE6. This service is required to be
an unprotected service in the traditional network, but a silver service in the ASON network.
Figure 7-31 VC12 service requirement between traditional NEs

NE1 NE4
NE6
NE5
VC12
VC12
NE2 NE3
ASON NE
Taditional NE
Board Configuration
Figure 7-32 shows how the boards are configured on NE1, NE2, NE3 and NE4.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
O Q Q Q C C C I I I
1 6 6 6 C 2 1 U U U
6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN

S S S S S S S S S S S S S S S S S S S
1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3
9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
D75S
D75S
AUX
PIU
PIU
FAN FAN FAN
S S S S S S S S S S S S S S S S S S
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8
EXCSA
EXCSA
GSCC
GSCC
SL16
SL16
PQ1
PQ1
SL1
Service Planning
Table 7-10 VC12 service planning between traditional NEs
Attribute NE6<->NE5 (VC12) NE6<->NE5 (VC4 server trail)
Source NE NE6 NE6
Source board-port 2-N1PQ1 6-N1SL16-1
Source VC4 - 1
Source VC12 1 -
Sink NE NE5 NE5
Sink board-port 2-N1PQ1 6-N1SL16-1
Source VC4 - 1
Sink VC12 1 -
ASON service Silver

type
Traditional service Unprotected

type

You can use the following three ways to create a VC12 service between traditional NEs that
cross an ASON domain.
l Use the trail feature of the U2000 to create a VC4 server trail first. Then create a VC12
trail.
l Create a silver trail within the ASON domain. Then create VC12 cross-connections on NE5
and NE6.
l Create a silver server trail within the ASON domain. Then create VC12 cross-connections
on NE5 and NE6, and create VC12 cross-connections for both ends of the ASON server
trail.
Procedure
Step 2 Choose Create/Modify > Create Trail to create a VC4 server trail.
Step 3 Enter the VC4 server trail information as follows:

l Level: VC4 Server Trail
l Source: NE6
l Sink: NE5
protection type.
Step 6 In the SDH Trail Creation view, enter the VC12 trail information as follows:
l Level: VC12
l Source: NE6-2-PQ1-1(SDH_TU-1)
l Sink: NE5-2-PQ1-1(SDH_TU-1)
details of the VC4 server trail and the VC12 trail that are created. You can also view the value
of ASON-SDH Trail to check whether the ASON section of the ASON-SDH trail is successfully
created.
----End

7.8.3 Creating a VC4 Service Between a Traditional NE and an

ASON NE
You can create end-to-end VC4 services between traditional NEs and ASON NEs.
Prerequisite
Service Requirement
A VC4 service needs to be configured between NE1 and NE5. This service is required to be an
Figure 7-34 VC4 service requirement between traditional and ASON NEs
NE1 NE4
VC4
NE6 NE5
VC4
NE2 NE3
Board Configuration
Figure 7-35 shows how the boards are configured on NE1,

Figure 7-35 Board configuration for NE1
FAN
A
EF U
I1
S S S SS
O Q Q QH C C C I I I
1 6 6 6 4 C 2 1 U U U
6 4 4 4 1
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Figure 7-36 shows how the boards are configured on NE2, NE3 and NE4.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
O Q Q Q C C C I I I
1 6 6 6 C 2 1 U U U
6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN

FAN
A
EF U
I1
S S S
L L L S S S F F F
O O H C C C I I I
1 1 4 C 2 1 U U U
6 6 1
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
Table 7-11 VC4 service planning between traditional NE and ASON NE
Attribute NE1<->NE5
Source NE NE1
Source board-port 26-N3SLH41-1
Source VC4 1
Sink NE NE5
Sink board-port 26-N3SLH41-1
Sink VC4 1
You can use the following two ways to create a VC4 service between a traditional NE and an
ASON NE.

l Use the trail feature of the U2000 to directly create a VC4 service.
l Create a silver service within the ASON domain. Then create VC4 cross-connections on
NE5.
Procedure
Step 2 Choose Create/Modify > Create Trail.

l Level: VC4
l Source: NE1-26-N3SLH41-1(SDH-1)-VC4:1
l Sink: NE5-26-N3SLH41-1(SDH-1)-VC4:1
protection type.

detailed route information of the VC4 trail that is created. You can also view the value of ASON-
----End
7.8.4 Creating the 1+1 VC4 Service Between a Traditional NE and

an ASON NE
The 1+1 VC4 service can be configured between a traditional NE and an ASON NE.
Prerequisite
l The ASON software of the ASON NE must be of version 5.99.7.1 or later.
As shown in Figure 7-38, NE1, NE2, NE3, and NE4 are ASON NEs whereas NE5 and NE6 are
traditional NEs. A 1+1 VC4 service needs to be configured between NE5 and NE1. To implement
the 1+1 protection, the service association is configured in the ASON domain and the SNCP is
configured on the traditional NEs.
Figure 7-38 1+1 VC4 service requirement between a traditional NE and an ASON NE
NE 1 NE 4
VC4
NE 6 NE 5
VC4
NE 2 NE 3
Board Configuration
Figure 7-39 shows the board configuration of NE1-NE4.

Figure 7-39 Board configuration of NE1-NE4
FAN
A
EF U
I1
S S S SS
O Q Q QH C C C I I I
1 6 6 6 4 C 2 1 U U U
6 4 4 4 1
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Figure 7-40 shows the board configuration of NE5 and NE6.
FAN
A
EF U
I1
S S S
L L L S S S F F F
O O H C C C I I I
1 1 4 C 2 1 U U U
6 6 1
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
Table 7-12, Table 7-13, Table 7-14, and Table 7-15 show the service planning for the NEs.

Table 7-12 Service planning for the two silver ASON trails
Source NE NE1 NE1
Sink NE NE4 NE3
Protection type Silver trail Silver trail
Table 7-13 SNCP service planning for NE5

Attribute Working Service Protection Service
Source board- 22-N4SLO16-1 22-N4SLO16-1

port
Source VC4 1
timeslot
Sink board-port 26-N3SH41-1
Sink VC4 1
timeslot
Service level VC4
Direction Bidirectional
NOTE
The boards and timeslots that the two ASON trails occupy can be queried in the SDH ASON Trail
Management window only after the trails are created. In this example, the two ASON trails of NE1 occupy
the 64th VC4 of the 23-N4SLQ64-1 and the first VC4 of the 24-N4SLQ64-1.
Table 7-14 SNCP service planning for NE1

Attribute Working Service Protection Service
Source board- 23-N4SLQ64-1 24-N4SLQ64-1

port
Source VC4 64 1
timeslot
Sink board- 26-N3SLH41-1

port
Sink VC4 1
timeslot
Service level VC4
Direction Bidirectional

NOTE
The boards and timeslots that the two ASON trails occupy can be queried in the SDH ASON Trail
Management window only after the trails are created. In this example, the ASON trail of NE3 occupies
the 64th VC4 of the 22-N4SLQ64-1 and the ASON trail of NE4 occupies the first VC4 of the 22-
N4SLQ64-1.
Table 7-15 Service planning for NE3 and NE4
Attribute NE3 NE4
Source board-port 22-N4SLQ64-1 22-N4SLQ64-1
Source VC4 timeslot 1 1
Sink board-port 23-N4SLQ64-1 25-N4SLQ64-1
Sink VC4 timeslot 64 1
Service level VC4 VC4
Direction Bidirectional Bidirectional
To create the 1+1 VC4 service between a traditional NE and an ASON NE, do as follows:
Create a silver ASON trail between NE1 and NE4 and create a silver ASON trail between NE1
and NE3. Then, associate the two ASON trails. After that, create the 1+1 VC4 cross-connection
between NE1 and NE5, and create the VC4 cross-connection between NE3 and NE4.
Procedure
For example, enter the following attributes:
l Type: ASON Trail
l Class: Silver
For example, enter the following attributes:
l Revetrive Mode: Revertive (Select Non-Revetrive if the silver service is a non-revetrive
service. Select Scheduled revertive if the silver service is a scheduled revertive service.)
l Priority: High
l Lockout: Unlocked

For example, select the N1SL16 in slot 6, port 1, and timeslot 1.
NOTE
Step 8 Ensure that the trail information and routing restrictions are correct. Click Apply. If the creation
is successful, a dialog box is displayed indicating that the operation is successful.
again from Step 1.
Step 10 According to the service planning, repeat Steps 3-9 to create the silver service between NE1 and
NE3.
Step 11 Click Cancel to return to the SDH ASON Trail Management window. Hold down the Ctrl
key and select the two silver trails to be associated. Right-click and choose Set Association from
the shortcut menu. Click Yes in the Prompt dialog box that is displayed. After the two ASON
trails are associated, a dialog box is displayed indicating that the operation is successful.
Step 12 Select the NE1 icon in the Main Topology. Right-click and choose NE Explorer from the
shortcut menu.
Step 13 Choose Configuration > SDH Service Configuration from the Function Tree.
Step 14 Click Create SNCP Service and enter the following SNCP service information about NE1:
l Service Type: SNCP
l Level: VC4
l Source Slot:
– Working Service: 23-N4SLQ64-1
– Protection Service: 24-N4SLQ64-1
l Source Timeslot Range:
– Working Service: 64
– Protection Service: 1
l Sink Slot: 26-N3SLH41-1
l Sink Timeslot Range: 1
Step 15 Click Apply. After the SNCP service is created, a dialog box is displayed indicating that the
operation is successful.
Step 16 According to the service planning, repeat Steps 12-15 to create the SNCP service of NE5.
Step 17 Enter the NE Explorer of NE3.
Step 18 Choose Configuration > SDH Service Configuration from the Function Tree.

Step 19 Click Create and enter the following SDH service information about NE3:
l Level: VC4
l Source Slot: 22-N4SLQ64-1
l Source Timeslot Range: 1
l Sink Slot: 23-N4SLQ64-1
l Sink Timeslot Range: 64
l Activate Immediately: Yes
Step 20 Click OK. After the SDH service is created, a dialog box is displayed indicating that the operation
is successful.
Step 21 According to the service planning, repeat Steps 17-20 to create the SDH service of NE4.
Step 22 Choose Service > SDH Circuit > SDH Trail Search from the Main Menu. Click Next one after
another until the search is complete. Check whether the trail is created successfully in the SDH
Trail Management window.
Step 23 Choose Service > SDH Circuit > SDH Trail Management from the Main Menu. Click
Filter and choose Filter All. Check the detailed information about the trail that is created.
Step 24 Choose Configuration > SDH ASON > ASON Trail Management from the Main Menu. Then,
you can view the ASON trail information.
----End
7.8.5 Creating 1+1 VC12 Services Between Two Traditional NEs

with ASON NEs in Between
You can create 1+1 VC12 services between two traditional NEs with ASON NEs in between.
Prerequisite
l The ASON NE must be configured.
Service Requirement
In Figure 7-41, NE1, NE2, NE3 and NE4 are ASON NEs, and NE5 and NE6 are traditional
NEs. Configure a VC12 service between NE5 and NE6. The service requires SNCP protection.
Figure 7-41 1+1 VC12 service requirement between traditional NEs

NE1 NE4
NE6 NE5
VC12 VC12
NE2 NE3
: ASON NE
: Traditional NE

Board Configuration
For the board configuration of NE1-NE4, refer to Figure 7-42.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
O Q Q Q C C C I I I
1 6 6 6 C 2 1 U U U
6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3
9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
PIU
AUX
D75S
D75S
PIU
FAN FAN FAN
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8
EXCSA
EXCSA
SL16
SL16
GSCC
GSCC
PQ1
PQ1
SL1

Service Planning
Table 7-16 Planning of two silver ASON trails
Source NE NE1 NE2
Source board-port 21-N4SLO16-1 21-N4SLO16-1
Source VC4 1 1
Sink NE NE4 NE3
Sink board-port 21-N4SLO16-1 21-N4SLO16-1
Sink VC4 1 1
Service type ASON trail ASON trail

Source board- 2-PQ1 6-N1SL16-1 13-N1SL16-1

port
Source VC4 - 1
timeslot
Source VC12 1 1
timeslot
Sink board-port 6-N1SL16-1 13-N1SL16-1 2-PQ1
Sink VC4 1 -
timeslot
Sink VC12 1 1
timeslot


Source board- 2-PQ1 6-N1SL16-1 13-N1SL16-1

port
Source VC4 - 1
timeslot
Source VC12 1 1
timeslot
Sink board-port 6-N1SL16-1 13-N1SL16-1 2-PQ1
Sink VC4 1 -
timeslot
Sink VC12 1 1
timeslot
The two ways of creating 1+1 VC12 services between traditional NEs that cross an ASON
domain are as follows:
l Use the trail function of the U2000 to create two VC4 server trails and then create a VC12
trail.
l Create a silver ASON trail between NE1 and NE4 and a silver ASON trail between NE2
and NE3. Associate these two silver ASON trails. Configure VC12 cross-connections for
NE5 and NE6.
The following procedure describes how to create 1+1 VC12 services between traditional NEs
that cross an ASON domain in the first way.
Procedure
Step 2 Select Create/Modify > Create Trail to create a VC4 server trail.
Step 3 Create a VC4 server trail from NE5, NE4, NE1 to NE6.
1. Enter the information of the VC4 server trail.
For example:
l Level: VC4 server trail
l Source: NE5
l Sink: NE6

2. Check the SPC First check box. Click ASON Attributes Settings. Select Silver as the
protection type and click OK.
3. Check the Activate the trail check box. Click Apply.
4. A prompt appears telling you that the operation was successful. Click Close.
Step 4 Create a VC4 server trail from NE5, NE3, NE1 to NE6.
1. Enter the information of the VC4 server trail.
For example:
l Level: VC4 server trail
l Source: NE5
l Sink: NE6
2. Select the fiber between NE3 and NE2, and adjust the route to pass NE3 and NE2 and reach
NE1.
3. Check the SPC First check box. Click ASON Attributes Settings tab and select Silver as
the protection type.
Step 5 Create a VC12 trail.
1. In the SDH Trail Creation View, enter the information of the VC12 trail.
For example:
l Level: VC12
l Source: NE5-2-PQ1-1(SDH_TU-1)
l Sink: NE6-2-PQ1-1(SDH_TU-1)
2. Click the SNCP setting tab. Right-click NE5 and choose Set Dual-Fed Point from the
shortcut menu.
3. Right-click NE6 and choose Set Selective-Receiving Point from the shortcut menu.
Filter and select Filter All.
details of the VC4 server trail and the VC12 trail that are created. View the value of ASON-
Step 8 Choose Configuration > SDH ASON > ASON Trail Management from the Main Menu. View
the information of the created ASON trail.
----End
7.8.6 Creating 1+1 VC4 Services Between Two Traditional NEs with
ASON NEs in Between
You can create 1+1 VC4 services between two traditional NEs with ASON NEs in between.

Prerequisite
Service Requirement
In Figure 7-44, NE1, NE2, NE3 and NE4 are ASON NEs, and NE5 and NE6 are traditional
NEs. Configure a VC4 service between NE5 and NE6. The service requires SNCP protection.
Figure 7-44 1+1 VC4 service requirement between traditional NEs

NE1 NE4
NE6 NE5
VC4 VC4
NE2 NE3
Board Configuration
For the board configuration of NE1-NE4, refer to Figure 7-45.
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
O Q Q Q C C C I I I
1 6 6 6 C 2 1 U U U
6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN

FAN
A
EF U
I1
S S S S
L L L L S S S F F F
O O O H C C C I I I
1 1 1 4 C 2 1 U U U
6 6 6 1
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
Service Planning
Table 7-19 Planning of Two Silver ASON Trails
Source NE NE1 NE2
Source board-port 22-N4SLO16-1 22-N4SLO16-1
Source VC4 1 1
Sink NE NE4 NE3
Sink board-port 22-N4SLO16-1 22-N4SLO16-1
Sink VC4 1 1
Service type ASON trail ASON trail


Source board- 22-N4SLO16-1 23- 24-N4SLO16-1

port N4SLO16-1
Source VC4 2 2
timeslot
Sink board-port 23- 24-N4SLO16-1 22-N4SLO16-1

N4SLO16-1
Sink VC4 2 2
timeslot

Source board- 22-N4SLO16-1 23- 24-N4SLO16-1

port N4SLO16-1
Source VC4 2 2
timeslot
Sink board-port 23- 24-N4SLO16-1 22-N4SLO16-1

N4SLO16-1
Sink VC4 2 2
timeslot
The two ways of creating 1+1 VC4 services between traditional NEs that cross an ASON domain
are as follows:
l Use the trail function of the U2000 to create a VC4 service.

l Create a silver ASON trail between NE1 and NE4 and a silver ASON trail between NE2
and NE3. Associate these two silver ASON trails. Configure VC4 cross-connections for
NE5 and NE6.

The following procedure describes how to 1+1 VC4 services between traditional NEs that cross
an ASON domain in the first way.
Procedure
Step 2 Select Create/Modify > Create Trail.
Step 3 Enter the information of the service.

For example:
l Level: VC4
l Source: NE5-26-N3SLH41(SDH-1)-VC4:1
l Sink: NE6-26-N3SLH41(SDH-1)-VC4:1
Step 4 Check the SPC First check box. Click ASON Attributes Settings tab and select Silver as the
protection type.
Step 5 Click the SNCP setting tab. Right-click NE5 and choose Set Dual-Fed Point from the shortcut
menu.
Step 6 Right-click NE6 and choose Set Selective-Receiving Point from the shortcut menu.
Step 7 Check the SPC First check box. Click ASON Attributes Settings tab and select Silver as the
protection type.
Step 8 Check the Activate the trail check box. Click Apply. A prompt appears telling you that the
Filter and select Filter All.
details of the created VC4 trail. View the value of ASON-SDH Trail to check whether the
ASON section of the ASON-SDH trail is successfully created.
----End
7.9 Accessing a Traditional Network to an ASON Through

Linear MSP
When accessing services from a traditional network, to ensure that reliability of the accessed
services, you can create a 1+1 or 1:1 linear MSP at the edge of the traditional network and an
ASON domain. You can configure services in an ASON domain to the diamond, gold, and silver
level.
Prerequisite

Service Requirement
See Figure 7-47. If services exist between NE5 and NE3, a 1+1 linear MSP between NE5 and
NE2 can ensure the reliability of services accessed from the source node NE5.
Figure 7-47 Accessing 1+1 linear MSP

NE1 NE4
NE5
1+1 Linear MS
NE2 NE3
: ASON NE
: Traditional NE
Board Configuration
FAN
A
EF U
I1
S S S S
L L L L S S S F F F
O Q Q Q C C C I I I
1 6 6 6 C 2 1 U U U
6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN

FAN
A
EF U
I1
S S S S S
1 1 6 6 6 C 2 1 U U U
6 6 4 4 4
X X
C C
H H
M T T N N S N
R O D S S C S
8 M X 2 2 C 2
V
FAN
For the board configuration of NE5, refer to Figure 7-50.
Figure 7-50 Board configuration of NE5
1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3
9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7
D75S
D75S
AUX
PIU
PIU
FAN FAN FAN
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7 8
EXCSA
EXCSA
SL16
SL16
SL16
SL16
GSCC
GSCC
PQ1
PQ1

Service Planning
Refer to Table 7-22 for service planning.
Table 7-22 Planning of Diamond Services Accessed Through 1+1 Linear MSP
Attribute NE5<->NE3
Source NE NE5
Source board-port 14-N1SL16-1
Source VC4 1
Sink NE NE3
Sink board-port 22-N4SLO16-1
Sink VC4 1
Service route The system automatically calculates the service route.
ASON service type Diamond
Traditional service type 1+1 linear MSP
NOTE
In this case, a 1+1 linear MSP is created between NE5 and NE2.
Procedure
Step 2 Select Create/Modify > Create Trail.
Step 3 Enter the information of the service.

l Level: VC4
l Source: NE5-14-N1SL16-1(SDH-1)-VC4:1
l Sink: NE3-22-N4SLO16-1(SDH-1)-VC4:1
Step 4 Check the SPC First check box. Click ASON Attributes Settings tab and select Diamond as
the protection type.
Step 5 Check the Activate the trail check box. Click Apply. A prompt appears telling you that the
Step 6 Choose Service > SDH Circuit > SDH Trail Search from the Main Menu. Click Next and
click Finish.
details of the created VC4 trail.

----End
7.10 Managing Control Plane Alarms and Performance

Events

Prerequisite
Maintenance Period
Daily

U2000
Procedure
NOTE
----End
7.10.2 Suppressing Control Plane Alarms

The control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control link
alarm, and control channel alarm. Users can suppress the specific control plane alarms as
required.

Prerequisite
Context
This section considers suppressing the NE alarms as an example to describe how to suppress
control plane alarms.
Procedure
Step 1 In the NE Explorer, click the NE and then choose ASON > Control Plane Alarm
Suppression > NE Alarm Suppression
Step 2 Event names and corresponding suppression status displays in the right windows.
Step 3 Double-click Suppression Status, and then choose Suppressed from the drop-down menu.
Step 4 Click Apply to submit the alarm suppression setting.
Step 5 Optional: After the operation is complete, click Query to view the suppression status of the
current alarms.
----End
7.10.3 Suppressing Control Plane Alarm Events

Users can suppress control plane alarms at the service layer if required.
Prerequisite
Procedure
Step 2 Choose an ASON trail from the list, click Alarm and then select Control Plane Alarm
Suppression.
Step 3 Double click Suppression Status in the ASON Trail Alarm Suppression interface, and then
choose Suppressed from the drop-down menu.
Step 4 Click Apply to activate the alarm suppression setting.
Step 5 Click Query to query the control plane alarm suppression status of the SDH ASON trail.
----End


of the ASON Trail.
Prerequisite
Maintenance Period
Daily

U2000
Procedure
data.
5. Click Query.
performance data.
4. Click Query.
----End
7.10.5 Monitoring the Control Plane Performance

The control plane performance monitoring involves SDH ASON NE performance monitoring,
SDH ASON trail performance monitoring, SDH ASON TE Link performance monitoring and
control channel performance monitoring. The control plane performance monitor status defaults
to be disabled. Users can enable the monitoring function if required so that they can discover
and handle problems at the earliest time.

Prerequisite
This section considers enabling the NE monitoring function as an example to describe how to
enable or disable monitoring of the control plane performance.
Procedure
l In the NE Explorer, click the NE and then choose ASON > Control Plane Performance
> Performance Monitor Status.
l Click the NE Performance Monitor Status tab. Double-click Monitor Status of the
required performance event, and then choose Enabled from the drop-down menu.
l Click Apply to submit the setting.
l Optional: Click Query to view the control plane monitoring status of ASON NE.
----End
7.10.6 Setting the Auto-Report Status of the Control Plane

Performance Data
The control plane performance is monitored on a 24-hour basis. The performance is not reported
automatically by default. Users can enable the auto-report function if required. The control plane
performance monitoring involves SDH ASON NE performance monitoring, SDH ASON trail
performance monitoring, SDH ASON TE Link performance monitoring, and control channel
performance monitoring.
Prerequisite
This section considers enabling the auto-report function as an example to describe how to enable
or disable auto report of the control plane performance data.
Procedure
> Performance Monitor Status.
l Click the NE Performance Monitor Status tab. Double-click 24-Hour Auto-Report of
the required performance event, and then choose Enabled from the drop-down menu.

l Optional: Click Query to view the auto-report status of the control plane of the ASON
NE.
----End

7.10.7 Setting the Control Plane Performance Threshold

When an NE detects that a certain performance value exceeds the specified threshold, the NE
reports a performance threshold crossing event. Set the performance threshold for every SDH
ASON trail properly based on the requirements. In this way, the performance of every SDH
ASON trail can be monitored.
Prerequisite
Procedure
> SDH Performance Threshold.
l In the SDH ASON Trail list on the interface, select the desired SDH ASON trail.
l In the list, double-click the Threshold Value field of the SDH ASON trail, and then enter
a new performance threshold value.
l Click Query to query the control plane performance threshold of the SDH ASON trail.
----End

ASON User Guide 8 Routine Maintenance for an ASON Network
8 Routine Maintenance for an ASON Network
About This Chapter
The routine maintenance for an ASON network involves service monitoring and resource
monitoring. Service monitoring enables maintenance personnel to determine the affected scope
at the earliest time when a fault occurs on the network. Then, the maintenance personnel can
determine the rectification measures based on the characteristics of the fault and the current
service status. In this manner, the maintenance personnel can determine the health status of the
services promptly and minimize the impact on the services. Resource monitoring enables
maintenance personnel eliminate potential faults on the network in real time and thus eliminate
the severe potential risks in routine maintenance. Rectifying the resource anomalies in real time
can help to improve the network resources utilization rate, promote the service survivability,
discover the bottleneck of the network resources in advance, take capacity expansion measures
promptly, and ensure healthy operation of the network all the time.
This chapter focuses on the routine maintenance of the ASON control plane. For the routine
maintenance of the transport plane, refer to the OptiX OSN 8800 Intelligent Optical Transport
Platform Routine Maintenance.
8.1 Precautions for Routine Maintenance
The precautions for routine maintenance of an ASON network are described.
8.2 Routine Maintenance List
This section provides a list of the routine maintenance items and periods of an ASON network.
8.3 Routine Maintenance Items
The normal running of an ASON network depends on effective routine maintenance. The
purpose of routine maintenance is to find and solve problems in time.

8.1 Precautions for Routine Maintenance

The precautions for routine maintenance of an ASON network are described.
Precautions for Hardware Operation

l Switching off Laser
If the laser of a certain optical interface needs to be shut down in the maintenance process,
you need to migrate the ASON services that travel through this optical interface to another
trail or to set the rerouting function to Locked when no ASON services are running at the
optical interface before shutting down the laser.
CAUTION
Do not frequently enable or disable a laser where a TE link exists.
During routine maintenance,

– Switching off the laser on the OSC board does not affect the ASON services at the
optical layer and does not trigger rerouting. This operation, however, causes
authentication failure of the control channel at related optical interface and channel
interruption.
– Switching off the laser on the OTU board does not affect the ASON services at the
optical layer and does not trigger rerouting.
l Looping Back Optical Interface
When fiber jumpers are used to loopback an optical interface that has ASON services, first
transfer the ASON services to other ASON trails. If the optical interface has no services,
lock out the ASON trails that pass the optical interface by setting the Rerouting
Lockout attribute of the trails to Locked. If the service cannot be transferred to another
trail, you can change the service to a static service. In this case, loopback at the optical
interface causes service interruption.
CAUTION
Optimization of ASON service at the optical layer on the WDM equipment causes service
interruption for a long time.
l Inserting or Removing Fibers

Before inserting or removing fibers at an optical interface with ASON services, transfer
the ASON services to other trails. If the optical interface has no actual services, lock the
ASON trails that pass the optical interface by setting the Rerouting Lockout attribute of
the trails to Locked.

CAUTION
l Do not frequently insert or remove a fiber to or from an optical interface where a TE
link exists.
l Do not remove or insert fibers on an optical interface with services running.
l Replacing and Resetting the SCC Board

The ASON software runs on the SCC board and saves network data in real time. Hence,
the NE cannot run normally if the SCC board is absent for a long time. Before replacing
an SCC board, make sure that there is no rerouting or any other manual operation on ASON
services. Do not reset the SCC board when ASON services are created, deleted, or rerouted.
CAUTION
Do not reset the SCC board when ASON services are created, deleted, or rerouted.
l Precautions for Replacing and Resetting (Cold) the FIU Board

Before replacing or resetting (cold) the FIU board through which ASON services travel,
you need to migrate all the services on the board to another trail. Make sure that the services
are not interrupted for a long time and that all services on the board are rerouted at the same
time. If the ASON services cannot be migrated to another trail, you need to lock the
rerouting function of the services that pass through the FIU board to prevent rerouting.
After replacing or resetting the FIU board, unlock the rerouting function.
Precautions for Configuring Software Functions

During the maintenance, there is no need in general to modify the functions that have already
been configured on the current running software. If there is really a need to test or modify a
certain function, ensure that the operation does not affect the current services. In addition,
consider all possible results of such an operation and take necessary preventive measures.
NOTE
The configuration of software functions involves all configuration commands except the query command.
The configuration commands include setting, modification, deletion, and test commands. The execution
of these commands may directly or indirectly affect the running functions of the software. Thus, exercise
caution before running these commands.
l Precautions for Configuring Node ID
Node ID is used to identify an ASON NE and is unique in a network. You must specify the
requirement for configuring the node ID during network planning. When there are services,
you cannot modify the node ID.
CAUTION
The format of the node ID must be the same as the format of the IP address. The node ID
cannot be 0.0.0.0, 1.2.3.4 or 255.255.255.255. The node ID cannot be in the same network
segment as the IP address of the NE.

l Precautions for Enabling or Disabling the ASON Feature

An NE with the ASON software requires enabling the ASON feature. After the ASON
feature is enabled, it cannot be disabled if an ASON service is running on the node. If there
are no ASON services, you can use the U2000 to disable the ASON feature.
CAUTION
The ASON feature of the NEs with ASON services must be enabled. Hence, downgrade
or delete the ASON services on the NE before disabling the ASON feature on an NE. Do
not disable the ASON feature when the ASON software is running.
l Precautions for Configuring the Interface

By default, the ASON software does not enable the OSPF protocol at the Ethernet network
interface of the SCC board. PPP interfaces are created at each optical interface on the line
board that is physically installed on the equipment. By default, the OSPF protocol is enabled
at each PPP interface. Do not enable the OSPF protocol at the Ethernet network interface
of the SCC board.
Precautions for Maintaining the U2000 System

Do not exit the U2000 when it is normally running, though this operation does not interrupt the
network services. When the U2000 is shut down, however, it cannot monitor the ASON software
and the continuity for monitoring the ASON software is affected.
You also need to make sure that the U2000 computer is secure and not damaged.
8.2 Routine Maintenance List

This section provides a list of the routine maintenance items and periods of an ASON network.
Table 8-1 lists the routine maintenance items and periods of an ASON network.
Table 8-1 Routine maintenance items and periods of an ASON network
Maintenance Item Maintenance Period
Backing up NE data Daily
Checking ASON services Weekly
Querying ASON trail alarms Weekly
Querying control plane alarms Weekly
Querying control link alarms Weekly
Querying TE link alarms Weekly
Querying the performance of the control Weekly

plane

8.3 Routine Maintenance Items

The normal running of an ASON network depends on effective routine maintenance. The
purpose of routine maintenance is to find and solve problems in time.
8.3.1 Backing Up Device Data to the NMS Server or the NMS Client
This section describes how to back up device data manually for multiple devices of the same
device type. You can back up device data to the NMS server or the NMS client.
Prerequisite
The FTP, TFTP, or SFTP server must be configured and the FTP, TFTP, or SFTP service must
be started.
Tools, Equipment, and Materials

U2000
l The backup operation can be performed only for multiple devices of the same device type.
l When you select the device type in the device tree, all the devices and the device type
versions related to the device type are displayed in the NE View table.
l The files backed up from the server can be viewed on the Backup Information tab.
Procedure
Step 1 In the Main Topology view, choose Administration > NE Software Management > NE Data
Backup/Restoration from the Main Menu.
Step 2 Right click the device(s) that you want to back up in the NE View table.
NOTE
The Backup Information tab is unavailable when multiple devices are selected.
Step 3 Select Backup... to open the Backup dialog.

Step 4 Select the option NMS Server or NMS Client to back up the selected device information.
NOTE
By default, NMS Server is selected and the NMS Server is selected, the selected device information is
saved on the NMS server.
Step 5 Optional: If NMS Client is selected, click to select the location where the device data
has to be backed up.
Step 6 Click Start to start the backup operation for the selected device(s). On the NE View tab, the
backup progress is displayed.
----End
8.3.2 Checking ASON Services

In routine maintenance, check the changes in attributes of ASON services. On the U2000, you
can view the detailed information about the existing ASON services.
Prerequisite
You must be a U2000 user with U2000 operator" authority or higher.
Maintenance Period
Daily

U2000

Procedure
Step 1 In the Main Menu, choose Configuration > WDM ASON > ASON Trail Management to
view the created ASON trails.
Step 2 Click Synchronize and then set the synchronization conditions in the displayed dialog box.
Step 3 When the synchronization is complete, the system prompts that the operation is successful.
Step 4 Check the number of ASON services and the running status of each ASON service. Table 8-2
lists the check items and criteria.
NOTE
Assume that services are rerouted because of a fiber cut or other factors. If the services fail to be switched
back to the original trail after the fiber is repaired, it is recommended that you manually restore the services
back to the original trail by restoring (optimizing) the original trail on the U2000. This is to release the
occupied resource on the restoration trail so that the resource can be used in the process of rerouting other
services. In the case of silver optical services, optimizing trails causes a transient interruption of services.
(The transient interruption is due to switching between devices and the interruption time is of seconds.)
Thus, it is recommended that you optimize the optical service trails only when there is a small amount of
network traffic.
----End
Criteria
Table 8-2 Criteria for checking the running status of ASON services
Item Precaution
Number of services The number of configured services must comply with the network
planning requirements.
Service trail Check whether the attributes of each service are changed and whether
the actual routes and original routes comply with the networking
planning requirements.
Service attributes Check whether service attributes, including service activation status,
protection level, used wavelengths, revertive locking status, and
rerouting locking status, comply with the networking planning
requirements.
Service status All services are in Normal/Up state. If a service is not in normal or up
state due to a factor other than a manual operation, you need to rectify
the fault.
8.3.3 Querying the Alarms of an ASON Trail

For maintenance purposes, you can query the current alarms or historical alarms of a specified
ASON trail to learn the failures of an ASON network.
Prerequisite

l An ASON trail must be created and the trail must be active.
Maintenance Period
Daily

U2000
Procedure
Step 1 Query the alarms of a WDM ASON trail.
Menu.
2. On the trail list, select an ASON trail and click Alarms. Select Current Alarms from the
drop-down list.
In the displayed window, the current alarms of the ASON trail are displayed.
3. Optional: On the trail list, select an ASON trail and click Alarms. Select History
Alarms from the drop-down list.
In the displayed window, the historical alarms of the ASON trail are displayed.
4. Optional: Right-click an ASON-related alarm and choose Browse Alarm-Affected
ASON Trail from the shortcut menu. In the WDM ASON Trail Management window
displayed, you can view the information of the affected ASON trail.
NOTE
When you right-click an alarm, the Browse Alarm-Affected ASON Trail shortcut menu item is
available only if the alarm affects a WDM ASON trail.
5. Optional: Right-click an alarm related to a TE link, and choose Browse Alarm-Affected
TE Link from the shortcut menu. In the WDM TE Link Management window displayed,
you can view the information of the affected TE link.
NOTE
When you right-click an alarm, the Browse Alarm-Affected TE Link shortcut menu item is available
only if the alarm affects a TE link.
Step 2 Query the alarms of an SDH ASON trail.

1. Choose Configuration > SDH ASON > ASON Trail Management from the Main Menu.
2. On the trail list, select an ASON trail and click Alarms. Select Current Alarms from the
drop-down list.
In the displayed window, the current alarms of the ASON trail are displayed.
3. Optional: On the trail list, select an ASON trail and click Alarms. Select History
Alarms from the drop-down list.
In the displayed window, the historical alarms of the ASON trail are displayed.
Original Route from the shortcut menu. In the SDH ASON Trail Management window
displayed, you can view the information of the affected original route.
ASON Trail from the shortcut menu. In the SDH ASON Trail Management window
displayed, you can view the information of the affected ASON trail.

NOTE
When you right-click an alarm, the Browse Alarm-Affected ASON Trail shortcut menu item is
available only if the alarm affects an SDH ASON trail.
6. Optional: Right-click an alarm related to a TE link, and choose Browse Alarm-Affected
TE Link from the shortcut menu. In the SDH TE Link Management window displayed,
you can view the information of the affected TE link.
NOTE
When you right-click an alarm, the Browse Alarm-Affected TE Link shortcut menu item is available
only if the alarm affects a TE link.
----End

Prerequisite
Maintenance Period
Daily

U2000
Procedure
NOTE
----End
8.3.5 Querying Control Link Alarms

For maintenance purposes, you can query the current alarms or historical alarms of a control
link, to learn whether the control link is faulty.

Prerequisite
Maintenance Period
Daily

U2000
Procedure
Step 1 Choose Configuration > WDM ASON > Control Link Management or Configuration >
SDH ASON > Control Link Management from the Main Menu.
Step 2 In the control link list, select a control link and click Alarms. Choose Current Alarms from
the drop-down menu.
The currents alarms of the control link are then displayed in a new window.
Step 3 Optional: In the control link list, select a control link and click Alarms. Choose History
Alarms from the drop-down menu.
The historical alarms of the control link are then displayed in a new window.
----End
8.3.6 Querying TE Link Alarms

For maintenance purposes, you can query the current alarms or historical alarms of a TE link to
learn the failures of an ASON network.
Prerequisite
l A TE link must be created.
Maintenance Period
Daily

U2000
Procedure
Step 1 Choose Configuration > WDM ASON > TE Link Management or Configuration > SDH
ASON > TE Link Management from the Main Menu.
Step 2 In the link list, select a TE link and click Alarms. Choose Current Alarms from the drop-down
menu.

Step 3 Optional: In the link list, select a TE link and click Alarms. Choose History Alarms from the
drop-down menu.
Step 4 The current alarms of the TE link are displayed in a new window.
If you choose History Alarms from the drop-down menu, the historical alarms of the TE link
are displayed.
----End

of the ASON Trail.
Prerequisite
Maintenance Period
Daily

U2000
Procedure
data.
5. Click Query.
performance data.

4. Click Query.
----End

ASON User Guide 9 Handling ASON Network Failures
9 Handling ASON Network Failures
About This Chapter
By using the U2000, you can handle the common faults of an ASON network, such as the link
fault, service creation failure and service interruption fault.
9.1 Handling Link Failures

Link failures are classified into control channel failure, component link failure, and TE link
failure.
9.2 Handling the Failure in Creating Trails
Causes for the trail creation failure are various. These causes mainly include routing calculation
failures, label allocation failures, and cross-connection configuration failures.
9.3 Handling Trail Interruption
Causes for the trail interruption are various. In general, you need to first locate the trail that is
interrupted, and then solve the problem by either creating an ASON service or optimizing the
existing ASON service.

9.1 Handling Link Failures

Link failures are classified into control channel failure, component link failure, and TE link
failure.
Context
On an ASON network, there are three types of links: control channel, control link, and TE link.
These three types of links are associated with each other to certain extent.
l Connectivity of a control link can be tested only when there are available control channels
at adjacent nodes.
l A control link is available only when the control link connectivity test is successful.
l The ASON software continues to test the TE link consistency. If the consistency test is
successful, the TE links become available. The available TE links are used to carry ASON
services.
Consequently, link failures are classified into three types: control channel failure, control link
failure, and TE link failure.
9.1.1 Handling Impassable Control Channels

Control channels are classified into control channels inside and outside fibers. By default, control
channels inside a fiber are used. Control channels outside fibers are seldom used.
Context
Optical ASON control channels transmit LMP messages through the D4-D12 bytes; electrical
ASON control channels transmit LMP messages through the TTI overheads in the SM and PM
sections. For details about control channels, see ASON Link.
Symptom
A control channel is not in up state.
CPC_CC_DOWN alarms are reported, indicating an interruption of the control channel.
Impact on System
The existing services of the system are not affected. If all control channels between two nodes
are interrupted, however, the TE link is degraded.
Common Causes of Impassable Control Channels at the Optical Layer for OTN
networking
Common causes of an impassable control channel at the optical layer are as follows:
l Cause 1: The fiber between the OSC and FIU boards is connected inappropriately.
l Cause 2: The fiber connection between the FIU and OSC boards is configured
inappropriately.

l Cause 3: SD or SF alarms are generated at the optical interface where the impassable control
channel exists on the OSC board.
l Cause 4: The opposite NE is a non-ASON NE or the ASON function of the opposite NE
is disabled.
l Cause 5: The DCC byte setting on the NE is incorrect.
l Cause 6: The LMP protocol status of the control channel is manually disabled.
Common Causes of Impassable Control Channels at the Electrical Layer for OTN
networking
Common causes of impassable control channels at the electrical layer are as follows:
l Cause 1: SD or SF alarms are generated at the optical interface where the control channel
is impassable at the electrical layer.
l Cause 2: The server layer corresponding to the impassable control channel is not created
or deleted.
l Cause 3: The opposite NE is a non-ASON NE or the ASON function of the opposite NE
is disabled.
l Cause 4: The DCC byte setting on the NE is incorrect.
l Cause 5: The LMP protocol status of the control channel is manually disabled.
Common Causes of Impassable Control Channels for OCS networking

Possible causes for impassable control channels are listed below.
l Cause 1: The opposite NE is a traditional NE.

l Cause 2: The LMP protocol of the optical interface is manually disabled.
l Cause 3: No DCC is allocated to the optical interface.
l Cause 4: The ECC is not passable because of bit errors.
l Cause 5: Alarms such as R_LOS or R_LOF are raised at the optical interface.
l Cause 6: The board is not in position.
Procedure
Step 1 The steps for handling an impassable control channel at the optical layer are as follows.
1. Cause 1: According to the network diagram, check whether the fibers in two directions
between the FIU and OSC boards are connected properly. If they are connected
inappropriately, rectify the connection.
2. Cause 2: According to the network diagram, check whether the fiber connections in two
directions between the FIU and OSC boards are created properly on the U2000. If not,
correct the fiber connection configuration.
3. Cause 3: Check whether alarms or bit error performance events that are intended for
traditional WDM equipment are generated at an optical interface on the OSC board. If yes,
remove the alarms by referring to the procedure for handling alarms intended for traditional
WDM equipment. For details about the procedure, see the Alarms and Performance Events
Reference.
4. Cause 4: Check the ASON function status of the opposite NE. If the ASON function is
disabled, enable it if required.

5. Cause 5: See Setting the DCC Bytes for information on how to check the DCC byte settings
on the ASON NEs at the two ends of a channel. Ensure that the DCC resource of a port to
be used is enabled. Note that the state of DCC bytes on an ASON NE cannot be set as pass-
through.
6. Cause 6: Check the LMP protocol status of the optical interface. If the LMP protocol status
is Disabled, enable the LMP protocol of this optical interface.
Step 2 The steps for handling an impassable control channel at the electrical layer are as follows.
1. Cause 1: Check whether alarms or bit error performance events that are intended for
traditional WDM equipment are generated at the electrical-layer optical interface where
the impassable control channel exists. If such alarms or performance events occur at the
electrical-layer optical interface, remove the alarms by referring to the procedure for
handling alarms intended for traditional WDM equipment. For details about the procedure,
see the Alarms and Performance Events Reference.
2. Cause 2: On the U2000, check whether the control channel at the electrical layer has a
complete server trail. If the server trail is not established, create it.
3. Cause 3: Check the ASON function status on the opposite NE. If the ASON function is
disabled, enable it if required.
4. Cause 4: See Setting the DCC Bytes for information on how to check the DCC byte settings
on the ASON NEs at the two ends of a channel. Ensure that the DCC resource of a port to
be used is enabled. Note that the state of DCC bytes on an ASON NE cannot be set as pass-
through.
5. Cause 5: Check the LMP protocol status of the optical interface. If the LMP protocol status
is Disabled, enable LMP the protocol of this optical interface.
NOTE
When enabling the ASON function, shut down the control channels of the channels that are not used
currently. For details, see Configuring the LMP Protocol.
Step 3 The steps for handling an impassable control channel for OCS networking are as follows.
1. Cause 1: Check the type of the opposite NE. If the opposite NE is a traditional NE, the
control channel of the local NE is not passable.
2. Cause 2: Check the state of the LMP protocol at the optical interface. If the state of the
protocol at the optical interface is Disabled, it indicates that the LMP protocol is manually
disabled. Enable the LMP protocol at the optical interface again.
3. Cause 3: Check DCC state of the optical interface. If no DCC is allocated to the optical
interface, shut down the DCC of the optical interface that does not require ECC
communication.
NOTE
Only the DCC of the optical interface that does not require ECC communication can be shut down.
Make sure that ECC communication is not necessary for the optical interface before shutting down
the DCC.
4. Cause 4: Check the bit errors of the optical interface. If there is any bit error, clear them.
5. Cause 5: Check the alarms at the optical interface. If there are alarms such as R_LOS and
R_LOF, clear the alarms.
6. Cause 6: Check the state of the physical board.
l If the physical board is not in position, remove it and then insert it again. Add the logical
board correctly.

l If the physical board is faulty, replace it.
----End
9.1.2 Handling Impassable Control Links

In the case of testing the control link connectivity, the ASON software sends Test packets to
each control link to check the physical connectivity of the control link. The ASON software
obtains the control link identification at the opposite end based on the connectivity test result.
Context
When certain control channels are available, you can test the connectivity of the control links.
For details about control channels, see ASON Link.
Symptom
CPC_OSPF_CL_DOWN alarms are reported, indicating an interruption of a control link.
Impact on System
The existing service signals are not affected, but the IP reachability of the signaling packets is
affected.
Common Causes of Impassable Control Links

The common causes of impassable control links are as follows:
l Cause 1: A fiber cut occurs.
l Cause 2: The line board where the optical interface is located is not in position or is faulty.
Procedure
Step 1 Cause 1: Check and repair the fiber.
Step 2 Cause 2: Check and rectify the line board where the optical interface resides.
----End
9.1.3 Handling Impassable TE Links

On an ASON network, a TE link test can be performed only when available control channels
exist at adjacent nodes.
Context
Consistency test of TE link attributes is performed when the connectivity test of all the control
links where TE links exist is successful. A consistency test is performed to check whether the
interface mapping relationships discovered dynamically or set manually are consistent at two
nodes. If yes, the TE links enter the up state and the ASON software informs the ASON route
selection module that the TE links are available for creating ASON services. For details about
TE links, see ASON Links.
The TE link test sequence is as follows: control channel test -> control link connectivity test ->
TE link consistency test. The fault locating sequence is the same as the TE link test sequence.

That is, fault locating is performed from control channels to TE links. You need to determine,
locate, and remove faults in the sequence from control channels, to control links, and then to TE
links. Figure 9-1 shows the fault locating process. After excluding the possibility that a fault
occurs on control channels and control links, you need to remove the fault of impassable TE
links according to the handling procedure in this section.
Figure 9-1 Process for locating faults of impassable links
Start
Is a control Ye
s Handle the impassable
channel control channel
impassable?
No
Ye
Is a control link s Handle the impassable
impassable? control link
No
Handle impassable TE
links
End
Symptom
A TE link is not in up state. TE link interruption alarms are reported on the TE links that carry
services.
Impact on System
The existing services of the system are affected. After such an alarm is generated on the TE link,
the services on this TE link are interrupted and the TE link is unavailable. In this case, rerouting
of the services may be performed.
Common Causes of Impassable TE Links

Common causes of impassable TE links at the optical layer are as follows:
l Cause 1: Alarms are generated at the optical interface where an impassable TE link exists
on the FIU board.
l Cause 2: The board software does not match the NE software.
l Cause 3: Physical fibers are connected inappropriately.
l Cause 4: The nodes that are configured as pass-through nodes are upgraded as ASON nodes.
Common causes of impassable TE links at the electrical layer are as follows:

l Cause 1: Alarms are generated on the impassable TE links on the OTN board.
l Cause 2: The board software does not match the NE software.
l Cause 3: Physical fibers are connected inappropriately.
Procedure
Step 1 TE links at the optical layer
1. Cause 1: Check whether alarms that are intended for traditional WDM equipment are
generated at the optical interface on the FIU board. If yes, handle these alarms by referring
to the procedure for handling the alarms intended for traditional WDM equipment. For
details about the procedure, see the Alarms and Performance Events Reference.
2. Cause 2: Check the NE software and the board software. Determine the board software that
matches the NE software according to the Version Mapping Table. If the NE software does
not match the board software, reload the board software.
3. Cause 3: Check whether certain physical fibers are connected inappropriately. If yes, rectify
the connections.
If the TE links at both ends are disabled but a query of alarms shows that no abnormal
alarms are generated, check whether fibers are connected inappropriately according to the
network diagram.
4. Cause 4: If a pass-through node is upgraded as an ASON node, migrate all the services that
pass through the node to another trail. After that, disable and then immediately enable the
LMP protocols at the source and sink nodes of the services.
Step 2 TE links at the electrical layer

1. Cause 1: Check whether alarms that are intended for traditional WDM equipment are
generated at the OTU board where the impassable TE link exists. If yes, handle these alarms
by referring to the procedure for handling the alarms intended for traditional WDM
equipment. For details about the procedure, see the Alarms and Performance Events
Reference.
2. Cause 2: Check the NE software and the board software. Determine the board software that
matches the NE software according to the Version Mapping Table. If the NE software does
not match the board software, reload the board software.
3. Cause 3: Check whether certain physical fibers are connected inappropriately. If yes, rectify
the connections.
If the TE links at both ends are disabled but a query of alarms shows that no abnormal
alarms are generated, check whether fibers are connected inappropriately according to the
network diagram.
----End
9.1.4 Handling Degraded TE Links

Degradation of a TE link indicates that the TE link was once in normal state.
Symptom
TE link degradation alarms are reported on the TE links that carry services. When a TE link is
degraded, creating or optimizing a service, or rerouting the existing service on the TE link will
fail if an ASON service exists on the TE link.

Impact on System
The existing services of the system are not affected; however, creating or optimizing a service,
or rerouting of the existing service on the TE link will fail.
Common Causes of Degraded TE Links

l Cause 1: No control channel is available between the two end nodes of the TE link.
l Cause 2: The software or hardware of the board, where the optical interface of the TE link
resides, is faulty.
Procedure
Step 1 Cause 1:
1. View the control channel at the two ends of the TE link. For details, see the procedure for
handling the CPC_CC_DOWN alarm.
2. Check whether the system fails to perform the LMP check because (1) the control channel
between NEs is shut down, (2) the management of the opposite link is disabled, or (3) the
check of the opposite link is disabled. If yes, rectify the fault properly according to the
specific cause.
Step 2 Cause 2:
1. Check the state of the relevant board. If any fault occurs on the board, rectify the fault.
----End
9.2 Handling the Failure in Creating Trails

Causes for the trail creation failure are various. These causes mainly include routing calculation
failures, label allocation failures, and cross-connection configuration failures.
9.2.1 Handling the Failure of Route Calculation

If the route calculation fails during the ASON service creation, an error message is displayed
on the U2000.
Symptom
In the process of creating or optimizing an ASON service on the U2000 or in the process of
rerouting an existing ASON service after a fault occurs, the system returns a message indicating
that route calculation fails.
Impact on System
The existing services of the system are affected. Creating or optimizing an ASON service fails.
Rerouting an existing ASON service due to a fault also fails.
Common Causes for Route Calculation

The common causes for the route calculation are as follows.

l Cause 1: The network resource is insufficient.

l Cause 2: Routing constraints are incorrect. The explicit links and nodes are not specified
sequentially.
l Cause 3: Too many routing constraints are set.
l Cause 4: In the case of OCS ASON networking, the explicit timeslot has been reserved.
Procedure
Step 1 Cause 1:
1. Check the status of TE links between NEs. If a TE link is in abnormal state, see Handling
Impassable TE Links.
2. Check the use status of network resources such as wavelength resources and cross-
connection resources. If the network resources are insufficient, ensure sufficient network
resources by increasing the network resources, canceling wavelength reservation, or
releasing the occupied resources.
3. Check whether all potential trails are set as excluded trails.
Step 2 Cause 2: If routing constraints must be specified, check whether multiple explicit nodes are
specified according to the required node sequence. If not, the system reports an error message
for indication. In this case, you need to specify the explicit nodes according to the required node
sequence.
Step 3 Cause 3: Check whether the number of ASON service nodes exceeds the maximum number of
nodes. In the process of creating an ASON service, the ASON software by default considers that
the maximum hops of the ASON service is 64. That is, the maximum number of nodes that an
ASON service travels through is 65.
Step 4 Optional: Cause 4: In the case of OCS ASON networking, check the reservation of explicit
timeslots. If an explicit timeslot is reserved, specify another explicit timeslot.
----End
9.2.2 Handling the Failure of Label Allocation

If the label allocation fails during the ASON service creation, an error message is displayed on
the U2000.
Symptom
In the process of creating or optimizing an ASON service on the U2000, or in the process of
rerouting the ASON service after a fault occurs, the system returns a message indicating that
allocating labels fails.
Impact on System
The existing services of the system are affected. Creating or optimizing an ASON service, or
rerouting the ASON service due to a fault will fail.
Common Causes of a Failure to Allocate Labels

Usually this situation is caused by the incorrect channel occupation status. In this case, you can
query the cross-connections of each NE, and check whether any residual cross-connections exist.
If the problem persists, specify another explicit node.

NOTE
For the residual cross-connection generated by rerouting or service downgrade of the ASON system, the
system automatically clears the cross-connection after a period of time. There is no need to manually clear
the cross-connection. For the redundant cross-connections, the ASON system cannot automatically clear
them. They must be manually cleared one NE by one NE.
The following describes how to synchronize the cross-connections of an individual NE.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Optical Cross-Connection
Management from the Function Tree.
Step 2 Click the Single-Station Optical Cross-Connection or Board Optical Cross-Connection tab.
Click Query to refresh the optical cross-connection information of the NE.
Step 3 Record the optical cross-connection information and compare it with the planned optical cross-
connections to check whether any residual cross-connection exists. If there is any residual cross-
connection, deactivate the cross-connection and then delete it.
Step 4 In the NE Explorer, select the NE, and then choose Configuration > WDM Service
Management from the Function Tree.
Step 5 On the WDM Cross-Connection Configuration tab page, click Query to refresh the electrical
cross-connection information about this NE.
Step 6 Record the electrical cross-connection information and compare it with the planned electrical
cross-connections to check whether any residual cross-connection exists. If there is any residual
cross-connection, deactivate the cross-connection and then delete it.
----End
9.2.3 Handling the Cross-Connection Control Failure

If the configuration for the cross-connections fails during creation of an ASON service, an error
message is displayed on the U2000.
Symptom
In the process of creating or optimizing an ASON service on the U2000, or in the process of
rerouting the ASON service after a fault occurs, the system returns a message indicating that
configuring a cross-connection fails.
Impact on System
The existing services of the system are affected. Creating or optimizing an ASON service, or
rerouting the ASON service due to a fault will fail.
Common Causes for the Failure in Cross-Connection Configuration

The common causes for the failure in the cross-connection configuration are as follows:
l Cause 1: The corresponding cross-connect board is abnormal or the cross-connect capacity

is insufficient.
l Cause 2: The corresponding line board or OTU board is abnormal.

l Cause 3: The corresponding resources are in use.
Procedure
Step 1 Cause 1: Ensure that the corresponding cross-connect board runs normally and this cross-connect
board has sufficient cross-connect capacity.
Step 2 Cause 2: Ensure that the corresponding line or OTU board runs normally and has no alarms.
Step 3 Cause 3: Check whether any residual board cross-connections exist on the node. If so, delete the
residual cross-connections before configuring ASON services.
NOTE
To determine whether a residual cross-connection exists, you need to check configurations according to
the following requirements. If the following requirements are not met, you can determine that a residual
cross-connection exists.
l The two ends of a link have the same settings of channel use status.
l Static cross-connections exist at the two ends of a link.
l The wavelength use status settings at the two ends of a link are the same.
NOTE
For how to handle the residual cross-connection of the board of the NE, refer to the handling procedure in
the 9.2.2 Handling the Failure of Label Allocation.
----End
9.2.4 Handling an LSP Creation Timeout Fault

During creation of an ASON service, the U2000 reports an error if the creation of an LSP times
out.
Fault Symptom
When a user creates or optimizes an ASON service on the NMS or when an ASON service is
rerouted in case of a fault, the NMS displays a failure prompt, indicating that the server is busy
or the equipment is performing other operations and cannot respond to the request.
Impact on the System

The existing services of the system are affected. In addition, creating or optimizing an ASON
service, or rerouting the ASON service due to a fault will fail.
Common Causes of LSP Creation Timeout

The common causes of LSP creation timeout are as follows:
l Cause 1: The adjacent nodes have different RSVP MD5 authentication policies.
l Cause 2: A node is reset in the process of creating an LSP.
l Cause 3: No route is available between the source and sink nodes during creation of the
LSP on the network.
l Cause 4: The ASON service to be created involves many nodes and thus the service creation
time exceeds the time limit permitted by the NMS.

Procedure
Step 1 Cause 1: Check whether the adjacent nodes have the same RSVP MD5 authentication policy. If
not, set the RSVP MD5 authentication policies of the adjacent nodes so that they are the same.
For details, see Encrypting RSVP Protocol.
Step 2 Cause 2: Check whether an NE becomes unreachable by the NMS due to a reset. If an NE is
reset, proceed with the operation after the NE starts up again.
Step 3 Cause 3: Check the network topology between nodes to see whether a route is available between
the source and sink nodes. If not, adjust the network.
Step 4 Cause 4: Ensure that network resources are utilized properly on an ASON network by means of
network planning, or adjust the service trail by specifying an explicit node when creating an
ASON service.
----End
9.2.5 Handling the Fault with Unavailable Wavelengths at the

Service Adding/Dropping Ports
During creation or optimization of an ASON service, the NMS may display a message indicating
that the wavelengths at the ports for adding/dropping services are unavailable.
Fault Symptom
The system returns a failure message in the process of creating or optimizing an ASON service
on the NMS, indicating that the wavelengths at the ports for adding or dropping services are
unavailable.

Common Causes of Unavailable Wavelengths at Service Adding/Dropping Ports

The common causes of unavailable wavelengths at service adding/dropping ports are as follows:
l Cause 1: The wavelength at the port on the corresponding board at the source or sink node
is reserved.
l Cause 2: The fiber connections at the source or sink node are created incorrectly.
Procedure
Step 1 Cause 1:
1. Regarding services at the optical layer, check resource reservation of the corresponding
FIU board. For the method of checking resource reservation, see Setting Resource
Reservation. If the required wavelength is reserved but this wavelength must be used for
an ASON service, release this wavelength on the corresponding FIU board at the source or
sink node.
2. Regarding services at the electrical layer, check resource reservation of the corresponding
OTU or line board. For the method of checking resource reservation, see Setting Resource

Reservation. If the required wavelength is reserved but this wavelength must be used for
an ASON service, release this wavelength on the corresponding OTU or line board at the
source or sink node.
Step 2 Cause 2: Check whether the fiber connections of the ASON service link are created correctly
on the U2000. If not, rectify the fiber connections.
----End
9.2.6 Handling an Optical Parameter Verification Failure

During creation or optimization of an ASON service, an optical parameter verification failure
may occur.
Fault Symptom
With the optical parameter features enabled, the system returns a failure message in the process
of creating or optimizing an ASON service on the NMS, indicating that verification of optical
parameters fails.

Common Causes of an Optical Parameter Verification Failure

The common causes of an optical parameter verification failure are as follows:
l Cause 1: The input or output optical power fails to conform to the standard optical power
value.
l Cause 2: The dispersion setting is inconsistent with the dispersion value as planned for the
network.
l Cause 3: The link distance setting is inconsistent with the actual link distance.
Procedure
Step 1 Cause 1: Check whether the input or output optical power as set for each optical amplifier (OA)
board along the service signal flow conforms to the standard optical power value. If not, adjust
the input or output optical power to the standard value. For the details, see the Commissioning
Guide.
Step 2 Cause 2: Check whether the dispersion value set for an FIU board is the same as the dispersion
value planned for the network. If not, change the dispersion to a proper value. For details on the
dispersion setting, see Setting Optical Parameters.
Step 3 Cause 3: Check whether the link distance set in the ASON TE link management window is
correct. If not, change the link distance to a proper value. For the details on the link distance
setting, see Setting Optical Parameters.
----End

9.3 Handling Trail Interruption

Causes for the trail interruption are various. In general, you need to first locate the trail that is
interrupted, and then solve the problem by either creating an ASON service or optimizing the
existing ASON service.
You must consider the following guidelines to troubleshoot trails interruption.

1. Query alarms and check which trails are interrupted. Then record the information about the
source and sink ports for the interrupted trails.
2. If the interrupted trails are still displayed in the ASON Trail Management interface,
optimize the service trails to avoid the fault trails and restore the services.
3. If the optimization fails or the interrupted trails are not displayed in the ASON Trail
Management interface, delete the service. You should re-create traditional WDM or
SDH trails to avoid faulty trails and restore the services.
4. After the service is recovered, collect relevant data to identify the causes of the fault and
thus to remove the fault.
5. When the trails are restored and the network becomes stable, upgrade the created traditional
trails to ASON trails. You should determine if it is necessary to revert the trails to the
original trails by performing an optimization.
9.3.1 Methods of Identifying a Service Interruption Fault

You need to identify which trails are interrupted before you restore them.
Procedure
Step 1 Choose Fault > Synchronize Networkwide Alarms from the Main Menu on the U2000 to
synchronize alarms networkwide.
Step 2 Choose Fault > Browse Current Alarms from the Main Menu on the U2000 to view the current
alarms networkwide.
Step 3 On U2000, choose Configuration > WDM ASON > WDM ASON Trail Management. In
WDM ASON Trail Management, find a service whose Alarm Status is Critical Alarm (in
red).
Step 4 In WDM ASON Trail Management, select the trail of the service. Click Alarms, and then
select Current Alarms from the drop-down menu. Then, query the alarm such as
CPW_OCH_SER_INT that causes service interruption.

Step 5 Find all the currently interrupted trails according to the previously performed operations. Record
the information on the trails and handle the alarms according to associated alarm handling
method.
----End
9.3.2 Handling the Fault of Trail Interruption

You can restore the trails by recreation or optimization after confirming the faulty services.
NOTE
If multiple ASON trails are interrupted, identify the interrupted trails first, and analyze what the interrupted
trails have in common. Then respectively clear the fault for each ASON trail according to the procedure
for handling faults of a single trail.
Procedure
Step 1 Check whether the wavelengths at the source port and sink port of the interrupted trail are
occupied. If the residual cross-connections are occupied, delete these cross-connections and
create a WDM trail again to restore the trail.
Step 2 Try to optimize the ASON trail and avoid the original route. To avoid the original route, you
can either cancel all the constrains for the U2000 to automatically compute a new route or
manually specify new constraints.
Step 3 Try to downgrade the original ASON trail to a traditional WDM trail.
l If the downgrade is successful, delete the cross-connections at the source and sink ports
and then create a traditional WDM trail between the two ports. After the creation is
successfully created, the trail is restored.
l If the downgrade fails, please contact the local office of Huawei.
----End
9.3.3 Handling the Failure to Reroute Services

On an ASON network, rerouting of an ASON service may fail.
Fault Symptom
When rerouting of an ASON service fails, a rerouting failure event is reported. In addition, after
the ASON service is interrupted, corresponding ASON service interruption alarms are reported.
NOTE
On the main user interface of the NMS, choose FaultBrowse Event from the Main Menu. Then, select the
filtering conditions of ASON trail rerouting event. After that, the NMS lists all the rerouting success or
failure events in connection with the control plane, which reports a corresponding event to the NMS every
time rerouting of an ASON service fails.


Common Causes of a Service Rerouting Failure

The common causes of a service rerouting failure are as follows:
l Cause 1: Rerouting calculation fails.
l Cause 2: Optical parameter verification fails.
l Cause 3: The processing of the cross-connection control module fails.
Procedure
Step 1 Cause 1:
1. Check the upstream and downstream nodes of the service to see whether they are isolated.
If they are isolated, check whether the source and sink NEs are reset or whether the cross-
connect boards or the SCC boards on the relevant NEs are faulty. If yes, rectify such faults
first.
2. If the source and sink NEs are not isolated, optimize the ASON service trail. The fault is
removed if the optimization is successful. For the methods of optimizing an ASON service
trail, see Modifying the Route of an ASON Service.
3. If the optimization fails, it indicates that the link resources are insufficient on this network.
In this case, rectify the fault according to Failure of Route Calculation.
Step 2 Cause 2: Rectify the fault according to Handling an Optical Parameter Verification
Failure.
Step 3 Cause 3: Rectify the fault according to Handling the Cross-Connection Control Failure.
----End

ASON User Guide 10 Alarm Reference
10 Alarm Reference
About This Chapter
This chapter describes the alarms reported by the control plane.
10.1 Alarm Suppression Relationships

To avoid the situation that a large number of control plane alarms and transport plane alarms
are reported at the same time, control plane alarms caused by transport plane alarms are
suppressed, improving alarm reporting effectiveness.
10.2 Control Plane Alarms(OTN)
This section lists the control plane alarms of the ASON, and describes the meaning and severity
of the alarms.
10.3 Control Plane Alarms(OCS)
of the alarms.
10.4 Alarm Handling(OTN)
When the control plane alarm is detected, the services are abnormal, which needs to be handled
in time. This section describes the handling procedure of common alarms.
10.5 Alarm Handling(OCS)

10.1 Alarm Suppression Relationships

To avoid the situation that a large number of control plane alarms and transport plane alarms
are reported at the same time, control plane alarms caused by transport plane alarms are
suppressed, improving alarm reporting effectiveness.
Table 10-1 lists the suppression relationships between transport plane alarms and control plane
alarms.
Table 10-1 Suppression relationships between transport plane alarms and control plane alarms
Transport Plane Control Plane Alarm to Be Suppressed at the
Alarm Corresponding Port
SF, SD, or board offline TE link broken alarms:

alarms CPW_OMS_TEL_DOWN
CPW_OTU5G_TEL_DOWN
CPW_OTU3_TEL_DOWN
CPW_OTU2_TEL_DOWN
CPW_OTU1_TEL_DOWN
CPW_ODU5G_TEL_DOWN
CPW_ODU3_TEL_DOWN
CPW_ODU2_TEL_DOWN
CPW_ODU1_TEL_DOWN
CP_TEL_DOWN
SF, SD, board offline, or TE link degrade alarms:

COMMUN_FAIL CPW_OMS_TEL_DEG
alarms CPW_OTU5G_TEL_DEG
CPW_OTU3_TEL_DEG
CPW_OTU2_TEL_DEG
CPW_OTU1_TEL_DEG
CPW_ODU5G_TEL_DEG
CPW_ODU3_TEL_DEG
CPW_ODU2_TEL_DEG
CPW_ODU1_TEL_DEG
CP_TEL_DEG

Transport Plane Control Plane Alarm to Be Suppressed at the

Alarm Corresponding Port
SF, SD, board offline, or Alarms indicating inconsistent channel status at two ends of a TE
COMMUN_FAIL link:
alarms CPW_OMS_TEL_PATHMIS
CPW_OTU5G_TEL_PATHMIS
CPW_OTU3_TEL_PATHMIS
CPW_ODU5G_TEL_PATHMIS
CPW_ODU3_TEL_PATHMIS
CP_TEL_PATH_MIS
SF, SD, board offline, or Alarms indicating inconsistent ODUk Spring configurations at
COMMUN_FAIL two ends of a TE link:
alarms CPW_OTU2_TEL_ODURMIS
CPW_OTU1_TEL_ODURMIS
CPW_ODU3_TEL_ODURMIS
CPW_ODU2_TEL_ODURMIS
Alarms indicating inconsistent MSP status at two ends of a TE
link:
CP_TEL_MSP_MIS
SF, SD, or board offline Alarms indicating control channel interruption:

alarms CPC_CC_DOWN
10.2 Control Plane Alarms(OTN)

of the alarms.
For the alarms that can be reported by the control plane of the ASON, refer to the Table 10-2.
Table 10-2 Control plane alarms
Name Meaning Severity
CPC_CC_DOWN Indicates that the control Major

channel is down.
CPC_NODE_ID_CON- Indicates node ID conflict. Critical

FLICT
CPC_NODE_ID_ERR Indicates a node ID error. Critical

CPC_OSPF_AUTH_ERR Indicates an OSPF neighbor Major

authentication error.
CPC_OSPF_CL_DOWN Indicates an interruption of Major

the OSPF control link.
CPC_OSPF_NB_DOWN Indicates an OSPF neighbor Major

interruption.
CPC_RSVP_AUTH_ERR Indicates an RSVP neighbor Major

authentication error.
CPC_RSVP_NB_DOWN Indicates an RSVP neighbor Major

interruption.
CPW_CLNT_LSPOVPN_ Indicates that not all Major

MM resources used by an OVPN
service of client level are
allocated to the OVPN
customer.
CPW_CLNT_SER_INT Indicates an interruption of Critical

the client service.
CPW_CLNT_SER_NOTOR Indicates that the client Warning

service is not on the original
trail.
CPW_CLNT_SER_RRTLO Indicates that rerouting of the Major

CK client service is locked.
CPW_CLNT_SER_SLA- Indicates SLA degrade of the Major

DEG client service.
CPW_CLNT_SER_SYN- Indicates that Minor

FAIL synchronization of
associated client services
fails.
CPW_OCH_LSPOVPN_M Indicates that not all Major

M resources used by an OVPN
service of OCh level are
customer.
CPW_OCH_SER_INT Indicates an interruption of Critical

the OCh service.
CPW_OCH_SER_NOTOR Indicates that the OCh Warning

service is not on the original
trail.
CPW_OCH_SER_RRTLOC Indicates that rerouting of the Major

K OCh service is locked.

CPW_OCH_SER_SLADEG Indicates SLA degrade of the Major

OCh service.
CPW_OCH_SER_SYN- Indicates that Minor

associated OCh services
fails.
CPW_ODUk_LSPOVPN_ Indicates that not all Major

MM resources used by an OVPN
service of ODUk level are
customer.
CPW_ODUk_SER_INT Indicates an interruption of Critical

the ODUk service.
CPW_ODUk_SER_NO- Indicates that the ODUk Warning

TOR service is not on the original
trail.
CPW_ODUk_SER_RRTLO Indicates that rerouting of the Major

CK ODUk service is locked.
CPW_ODUk_SER_SLA- Indicates SLA degrade of the Major

DEG ODUk service.
CPW_ODUk_SER_SYN- Indicates that Minor

associated ODUk services
fails.
CPW_ODUk_TEL_DEG Indicates degrade of ODUk Major

TE link.
CPW_ODUk_TEL_DOWN Indicates an interruption of Critical

the ODUk TE link.
CPW_ODUk_TEL_ODUR- Indicates configuration Major

MIS inconsistency of the ODUk
SPRing at the two ends of the
ODUk TE link.
CPW_ODUk_TEL_PATH- Indicates path status Major

MIS inconsistency at the two ends
of the ODUk TE link.
CPW_ODUk_TELOVPN_ Indicates that the channels at Major

MM the two ends of the ODUk
link belong to different
OVPN customers.

CPW_ODUR_EWUOVPN_ Indicates that the east and Minor

MM west working channels of
ODUk SPRing protection
group belong to different
OVPN customers.
CPW_ODUR_WPOVPN_ Indicates that the working Minor

MM and protection channels of
the ODUk SPRing protection
group belong to different
OVPN customers.
CPW_OMS_TEL_DEG Indicates degrade of OMS Major

TE link.
CPW_OMS_TEL_DOWN Indicates an interruption of Critical

the OMS TE link.
CPW_OMS_TEL_EX- Indicates that the resource Minor

HAUST utilization of the optical-
layer OMS TE link exceeds
the preset threshold.
CPW_OMS_TEL_OCHMIS The settings of the maximum Major

number of channels at the
two ends of the OMS TE link
are inconsistent
CPW_OMS_TEL_PATH- Indicates path status Major

of the OMS TE link.
CPW_OMS_TELOVPN_M Indicates that the channels at Major

M the two ends of the OMS link
belong to different OVPN
customers.
CPW_OTUk_TEL_DEG Indicates degrade of OTUk Major

TE link.
CPW_OTUk_TEL_DOWN Indicates an interruption of Critical

the OTUk TE link.
CPW_OTUk_TEL_ODUR- Indicates configuration Major

MIS inconsistency of the ODUk
SPRing at the two ends of the
OTUk TE link.
CPW_OTUk_TEL_PATH- Indicates path status Major

of the OTUk TE link.

CPW_OTUk_TELOVPN_ Indicates that the channels at Major

MM the two ends of the OTUk TE
link belong to different
OVPN customers.
CPW_SER_XC_EXCEPT Indicates an ASON service Major

cross-connection exception.
10.3 Control Plane Alarms(OCS)

of the alarms.
For the alarms that can be reported by the control plane of the ASON, refer to the Table 10-3.
Table 10-3 Control plane alarms

CP_ASER_SYNC_FAIL Associated Service Minor

Synchronization Failure
CP_FIBER_CONNECT_FA Improper fiber connection Major

ULT
CP_LSP_NO_PRERRT Indicates that a preset Major

restoration trail is
unavailable for rerouting a
service.
CP_LSP_OVPN_MM Color mismatch of the LSP Major

and used resources
CP_MSP_EWUOVPN_MM Color mismatch of the east Minor

working timeslot and west
working timeslot of the MSP
CP_MSP_WPOVPN_MM Color mismatch of the Minor

working timeslot and
protection timeslot of the
MSP
CP_REROUTE_LOCK Rerouting lockout attribute Minor

being set for service
CP_SRV_INT Service interruption Critical
CP_SER_NOT_OR Service not on original route Minor
CP_SER_SLA_DEG Service SLA Degraded Major

CP_TEL_OVPN_MM Timeslot are configured to Major

different colors at the two
ends of the link
CP_TEL_DEG TE Link Degraded Major
CP_TEL_DOWN TE Link Down Critical
CP_TEL_MSP_MIS TE Link MSP Config Major

Mismatch
CP_TEL_PATH_MIS TE Link Path State Mismatch Major
CP_TEL_EXHAUST Threshold-crossing of the TE Minor

link resource utilization
CPC_CC_DOWN Control Channel Down Major
CPC_NODE_ID_CON- Node ID Conflict Critical

FLICT
CPC_NODE_ID_ERR Node ID Error Critical
CPC_OSPF_AUTH_ERR OSPF Neighbor Major

Authentication Error
CPC_OSPF_CL_DOWN OSPF Control Link Down Major
CPC_OSPF_NB_DOWN OSPF Neighbor Down Major
CPC_RSVP_AUTH_ERR RSVP Neighbor Major

Authentication Error
CPC_RSVP_NB_DOWN RSVP Neighbor Down Major
10.4 Alarm Handling(OTN)

Context
Only the handling procedures of the control plane alarms are described in this section. For the
transport plane alarms, refer to the Alarms and Performance Events Reference.
10.4.1 CPC_CC_DOWN
Description
The CP_CC_DOWN alarm indicates that the control channel is interrupted.

Attribute
Alarm Severity Alarm Type
Major Communication alarm
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm
Details field display the related parameters of the alarm. The alarm parameters are in the
following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example,
Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following
table.
Name Meaning
router_id Indicates the node ID of the NE on the link. The value is in dotted decimal notation,
for example, 1.1.1.1.
ccid Indicates the control link index and the value is in hexadecimal notation.
Sub-shelf Indicates the subrack of the link and the value is in decimal notation.
board Indicates the board of the link and the value is in decimal notation.
Port Indicates the optical interface of the link and the value is in decimal notation.

The service is not affected. If all control channels between two nodes are interrupted, however,
the TE link is degraded.
Fault Symptom
NOTE
If the fault has no symptom, or if the fault symptom is different from the one described in this topic, handle
the fault according to Handling Procedure.
Table 10-4 lists the fault symptom for the CPC_CC_DOWN alarm.
Table 10-4 Fault symptom for the CPC_CC_DOWN alarm
Fault Symptom Cause
The opposite node reports the Cause 5: The ID of the opposite node conflicts
CPC_NODE_ID_CONFLICT alarm. with the ID of other nodes.
Possible Causes
The possible causes of the CPC_CC_DOWN alarm are as follows:
l Cause 1: The control link is interrupted.

l Cause 2: The opposite node is a traditional node.

l Cause 3: The ASON software of the opposite node is not running.
l Cause 4: The control channel of the opposite node is disabled.
l Cause 5: The ID of the opposite node conflicts with the ID of other nodes.
Procedure
1. For details, see the procedure for handling the CPC_OSPF_CL_DOWN alarm.
1. Determine whether the opposite node needs to be upgraded to an ASON node
according to the networking requirement. If the upgrade is required, upgrade the
traditional node to an ASON node.
2. If the opposite node does not need to be upgraded to an ASON node, the user can
disable the LMP control protocol of the optical path between the ASON NE and non-
ASON NE, or suppress the alarm. For the operation steps, see Configuring the LMP
Protocol and Management of the Suppression Status of Alarms on the Control
Plane
1. Check the running status of the ASON software on the opposite node. Check whether
the ASON feature is enabled or whether the node ID setting is correct. Fix the problem
so that the ASON software can run properly.
1. Enable the opposite control channel.
1. For details, see the procedure for handling the CPC_NODE_ID_CONFLICT alarm.
----End
Related Information
None.
10.4.2 CPC_NODE_ID_CONFLICT
Description
The CPC_NODE_ID_CONFLICT alarm indicates a node ID conflict.
Attribute
Critical QoS
Parameters


table.
Name Meaning
NA NA

The existing services may be affected, the label switched path (LSP) may be abnormal, and the
service restoration mechanism may be affected.
Fault Symptom
NOTE
Table 10-5 lists the fault symptom for the CPC_NODE_ID_CONFLICT alarm.
Table 10-5 Fault symptom for the CPC_NODE_ID_CONFLICT alarm

Fault Symptom Cause
The CPC_NODE_ID_CONFLICT alarm is Cause 1: Two or more nodes have the same
reported. node ID.
Possible Causes
The cause of the CPC_NODE_ID_CONFLICT alarm is as follows:
l Cause 1: Two or more nodes have the same node ID.
Procedure
1. Change the node ID of the NE that reports this alarm so that the node ID of this NE
is different from the node IDs of other NEs in the ASON domain.
2. On the U2000, check the entire network for the node ID conflict, and then a list of
nodes with repeated IDs are displayed.
3. Change the IDs of the nodes in the list according to the design document so that the
node IDs are unique.
NOTE
For how to set the node ID, see Setting the Node ID.
----End
Related Information
None.

10.4.3 CPC_NODE_ID_ERR
Description
The CPC_NODE_ID_ERR alarm indicates a node ID error.
When the NE is started, the ASON function cannot be enabled normally because the internal
processing of the node ID setting is abnormal. As a result, this alarm is generated. After the error
is corrected, the ASON function can be enabled if there is no other problems. The alarm is
cleared, and an event indicating the end of this alarm is reported.
Attribute
Critical Process alarm
Parameters
table.
Name Meaning
NA NA

The ASON function cannot be enabled.
Fault Symptom
NOTE
Table 10-6 lists the fault symptom for the CPC_NODE_ID_ERR alarm.
Table 10-6 Fault symptom for the CPC_NODE_ID_ERR alarm

Fault Symptom Cause
The ASON function cannot be enabled. Cause 1: The internal processing of the node
ID setting is abnormal.
Possible Causes
The cause of the CPC_NODE_ID_ERR alarm is as follows:

l Cause 1: The internal processing of the node ID setting is abnormal.
Procedure
1. Check whether the node ID is set.
2. Check whether the preset node ID is the same as the one specified in the design
document. Set the node ID again according to the design document.
NOTE
Refer to Setting the Node ID for the configuration process.
----End
Related Information
None.
10.4.4 CPC_OSPF_AUTH_ERR
Description
The CP_OSPF_AUTH_ERR alarm indicates an authentication error of the OSPF neighbor.
Attribute
Major QoS
Parameters
table.
Name Meaning
nodeid Indicates the node ID of the NE on the link. The value is in dotted decimal
notation, for example, 1.1.1.1.
nbr_addr Indicates the node ID of the neighboring NE. The value is in dotted decimal
notation, for example 1.1.1.2.
telink_index Indicates the TE link index and the value is in hexadecimal notation.
Sub-shelf Indicates the subrack at the local end on the link and the value is in decimal
notation.
board Indicates the board at the local end on the link and the value is in decimal
notation.

Name Meaning
Port Indicates the optical interface at the local end on the link and the value is in
decimal notation.

The service signals are not affected, but the IP reachability of the control packets is affected.
Fault Symptom
NOTE
Table 10-7 lists the fault symptom for the CPC_OSPF_AUTH_ERR alarm.
Table 10-7 Fault symptom for the CPC_OSPF_AUTH_ERR alarm
Fault Symptom Cause
The CPC_OSPF_AUTH_ERR alarm is Cause 1: The OSPF authentication modes or

reported. keys at two ends of the control link are
inconsistent.
Possible Causes
The cause of the CPC_OSPF_AUTH_ERR alarm is as follows:
l Cause 1: The OSPF authentication modes or keys at two ends of the control link are
inconsistent.
Procedure
inconsistent.
1. Make the authentication modes and keys at the two ends consistent. Refer to
Encrypting the OSPF Protocol.
----End
Related Information
None.
10.4.5 CPC_OSPF_CL_DOWN
Description
The CPC_OSPF_CL_DOWN alarm indicates that the OSPF control link is interrupted.

Attribute
Major QoS
Parameters
table.
Name Meaning
Nodeid Indicates the node ID of the NE on the link. The value is in dotted decimal
notation.
Board Indicates the slot at the local end on the link and the value is in decimal notation.
decimal notation.

The service signals are not affected, but the IP reachability of the signaling packets is affected.
Fault Symptom
NOTE
Table 10-8 lists the fault symptoms for the CPC_OSPF_CL_DOWN alarm.
Table 10-8 Fault symptom for the CPC_OSPF_CL_DOWN alarm
Fault Symptom Cause
The alarm indicating a fiber cut is reported. Cause 1: A fiber cut occurs.
Possible Causes
The possible causes of the CPC_OSPF_CL_DOWN alarm are as follows:

Procedure
1. Check and repair the fiber.
----End
Related Information
None.
10.4.6 CPC_OSPF_NB_DOWN
Description
The CPC_OSPF_NB_DOWN alarm indicates that the OSPF communication between
neighboring NEs is interrupted.
Attribute
Major QoS
Parameters
table.
Name Meaning
notation.
board Indicates the slot at the local end on the link and the value is in decimal notation.
decimal notation.


Fault Symptom
NOTE
Table 10-9 lists the fault symptom for the CPC_OSPF_NB_DOWN alarm.
Table 10-9 Fault symptom for the CPC_OSPF_NB_DOWN alarm

Fault Symptom Cause
The CPC_OSPF_NB_DOWN alarm is l Cause 1: The OSPF protocol is not

reported. enabled on the control link of the opposite
node.
l Cause 2: The ASON software of the
opposite node is not running.
l Cause 4: The OSPF authentication
configuration is incorrect.
Possible Causes
l Cause 1: The OSPF protocol is not enabled on the control link of the opposite node.
l Cause 4: The OSPF authentication configuration is incorrect.
Procedure
1. Enable the OSPF protocol on the opposite control link. see the procedure for handling
the Configuring the OSPF Protocol.
1. For details, see the procedure for handling the CPC_OSPF_CL_DOWM alarm.
1. For details, see the procedure for handling the CPC_OSPF_AUTH_ERR alarm.
----End
Related Information
None.

10.4.7 CPC_RSVP_AUTH_ERR
Description
The CPC_RSVP_AUTH_ERR alarm indicates an authentication error of the RSVP neighboring
nodes.
This alarm is generated when the adjacent NEs (also called neighboring NEs) that the LSP
traverses fails to pass the authentication.
The alarm is cleared when the neighboring NEs pass the authentication successfully. In this case,
an event indicating the end of this alarm is reported. In addition, the alarm is not reported when
the neighboring NE does not exist.
Attribute
Parameters
table.
Name Meaning
Node Indicates the node ID of the NE that on the link. The value is in dotted decimal
Remote Node Indicates the node ID of the neighboring NE. The value is in dotted decimal
notation, such as 1.1.1.2.

The service signals are not affected. The signaling between the two adjacent NEs, however, is
affected, and certain operations cannot be performed. For example, creating a service between
the two NEs will time out, and rerouting of the services that traverse the two NEs will also fail
due to timeout.
Fault Symptom
NOTE
Table 10-10 lists the fault symptom for the CPC_RSVP_AUTH_ERR alarm.

Table 10-10 Fault symptom for the CPC_RSVP_AUTH_ERR alarm
Fault Symptom Cause
Creating a service or rerouting times out. Cause 1: The authentication modes or codes
of the two RSVP neighboring nodes are
inconsistent.
Possible Causes
The possible cause of the CPC_RSVP_AUTH_ERR alarm is as follows:
l Cause 1: The authentication modes or codes of the two RSVP neighboring nodes are
inconsistent.
Procedure
inconsistent.
1. Check whether the RSVP neighboring nodes are configured to be in different
authentication modes according to the network isolation requirement. If so, there is
no need to handle the alarm. Instead, suppress the alarm directly. Refer
toManagement of the Suppression Status of Alarms on the Control Plane.
2. Make two neighboring nodes have the same RSVP authentication mode and code.
Refer to Encrypting RSVP.
----End
Related Information
None.
10.4.8 CPC_RSVP_NB_DOWN
Description
The CPC_RSVP_NB_DOWN alarm indicates that the communication between neighboring
NEs fails, and the RSVP message from the neighboring NE cannot be received.
The alarm is cleared when the RSVP communication between the neighboring NEs is restored,
and an event indicating the end of this alarm is reported. In addition, the alarm is not reported
when the neighboring NE does not exist.
Attribute

Parameters
table.
Name Meaning
Remote Node Indicates the node ID of the neighboring NE. The value is in decimal dotted

The service signals are not affected, but the normal signaling process of the service is affected.
In this case, certain operations cannot be performed. For example, service optimization or
rerouting on the two NEs fails.
Fault Symptom
NOTE
Table 10-11 lists the fault symptoms for the CPC_RSVP_NB_DOWN alarm.
Table 10-11 Fault symptom for the CPC_RSVP_NB_DOWN alarm
Fault Symptom Cause
The CPC_OSPF_CL_DOWN alarm is Cause 1: The control link is interrupted.

generated, indicating that control link is
interrupted.
The NEs are unreachable to the U2000. Cause 2: The node is reset.
The CPC_RSVP_AUTH_ERR alarm is Cause 3: The configuration of the RSVP

generated, indicating that the RSVP neighboring authentication is incorrect.
neighboring authentication fails.
Possible Causes
The possible causes of the CPC_RSVP_AUTH_ERR alarm are as follows:

l Cause 2: The node is reset.
l Cause 3: The configuration of the RSVP neighboring authentication is incorrect.

Procedure
1. In this case, it is unnecessary to handle the alarm, because the alarm is cleared after
the NE is started.
1. For details, see the procedure for handling the CPC_RSVP_AUTH_ERR alarm.
----End
Related Information
None.
10.4.9 CPW_OCH_LSPOVPN_MM
Description
The CPW_OCH_LSPOVPN_MM alarm indicates that not all resources used by an OVPN
service of OCh level are allocated to the OVPN customer.
Attribute
Major QoS
Parameters
table.
Name Meaning
Src Indicates the source node ID of the service. The value is in dotted decimal notation,
Dst Indicates the sink node ID of the service. The value is in dotted decimal notation,
Index Indicates the main index to the service. The value is in decimal notation.
Instance Indicates the number of the service instance. The value is in decimal notation.

Name Meaning
MisType Indicates an information mismatch. The value is in hexadecimal notation. Valid
values of the parameter are as follows:
l 0x1: An information mismatch alarm exists on the service trail.
l 0x2: An information mismatch alarm exists on the shared mesh restoration trail.
l 0x3: An information mismatch alarm exists on both the service trail and the
shared mesh restoration trail.

This alarm does not affect the service; however, the resources for the services of other OVPN
customers may be unavailable because they are occupied by this service.
Fault Symptom
NOTE
Table 10-12 lists the fault symptoms for the CPW_OCH_LSPOVPN_MM alarm.
Table 10-12 Fault symptoms for the CPW_OCH_LSPOVPN_MM alarm
Fault Symptom Cause
The value of the MisType parameter of the Cause 1: Not all resources used by the OVPN
alarm is 0x1. service are allocated to this OVPN customer.
The value of the MisType parameter of the Cause 2: Not all resources used by the shared
alarm is 0x2. mesh restoration trail of the OVPN service
are allocated to the OVPN customer.
The value of the MisType parameter of the Cause 3: Not all resources used by the OVPN
alarm is 0x3. service and not all resources used by the
shared mesh restoration trail are allocated to
the OVPN customer.
Possible Causes
The possible causes of the CPW_OCH_LSPOVPN_MM alarm are as follows:
l Cause 1: Not all resources used by the OVPN service are allocated to this OVPN customer.
l Cause 2: Not all resources used by the shared mesh restoration trail of the OVPN service
l Cause 3: Not all resources used by the OVPN service and not all resources used by the
shared mesh restoration trail are allocated to the OVPN customer.

Procedure
l Cause 1: Not all resources used by the OVPN service are allocated to this OVPN customer.
1. Check the resource allocation along the service trail, and re-allocate the timeslot
resource on the link to the appropriate OVPN customer according to the design
document.
2. Change the affiliated OVPN customers according to the design document.
3. Optimize the service so that the service automatically uses the resources allocated to
the OVPN customer.
CAUTION
If you revert an OCh service without 1+1 protection to the original route, the service
is transiently interrupted due to the cross-connection characteristic of the optical
component.
l Cause 2: Not all resources used by the shared mesh restoration trail of the OVPN service
1. Check the resource allocation along the shared mesh restoration trail of the service,
and re-allocate the timeslot resource on the link to the appropriate OVPN customer
according to the design document.
2. Re-set the shared mesh restoration trail based on the link resources for the service.
l Cause 3: Not all resources used by the OVPN service and not all resources used by the
shared mesh restoration trail are allocated to the OVPN customer.
1. See the steps for handling the alarm due to the first and second causes.
----End
Related Information
None.
10.4.10 CPW_OCH_SER_INT
Description
The CPW_OCH_SER_INT alarm indicates a optical-layer OCh service interruption.
If none of the LSPs of a service fails to transmit the service, this alarm is reported. If any of the
LSPs can transmit the service, this alarm is cleared and an event indicating the end of this alarm
is reported.
Attribute
Critical QoS

Parameters
table.
Name Meaning
Dst Indicates the sink node ID of the service. The value is in dotted decimal notation, for
example, 1.1.1.2.

When this alarm occurs, the related service is interrupted.
Fault Symptom
NOTE
Table 10-13 lists the fault symptoms for the CPW_OCH_SER_INT alarm.
Table 10-13 Fault symptom for the CPW_OCH_SER_INT alarm
Fault Symptom Cause
The service is interrupted, and the alarm Cause 1: The rerouting function is locked
indicating that the rerouting function is manually.
locked is reported, but no event indicating
that rerouting fails is reported.
The service is interrupted, but no event Cause 2: All LSPs of the service are
indicating that rerouting fails is reported. interrupted, and the rerouting also fails.
The service is interrupted, and the alarms Cause 3: The boards for adding or dropping
such as BD_NOT_INSTALLED, services are offline.
WRG_BD_TYPE, and BD_STATUS for
traditional WDM equipment are generated.
Possible Causes
l Cause 1: The rerouting function is locked manually.

l Cause 2: All LSPs of the service are interrupted, and the rerouting also fails.

l Cause 3: The boards for adding or dropping services are offline.

– Sub-cause 1: The physical board is offline, or the logical board is not configured or
deleted.
– Sub-cause 2: The type of the physical board is different from the type of the logical
board.
– Sub-cause 3: The physical board is offline but the logical board is online.
Procedure
1. Check whether the rerouting function of the service is locked. If yes, change the setting
so that the rerouting function is unlocked. Then, the service is automatically rerouted
and restored. Refer to Setting the Routing Attributes.
l Cause 2: All LSPs of the service are interrupted, and the rerouting also fails due to lack of
resources.
1. Check whether alarms for traditional WDM equipment are generated along the route
of each LSP for the service. If alarms for traditional WDM equipment are generated,
see the Alarms and Performance Events Reference to handle the alarms.
2. Check whether the network has sufficient TE link resources to support rerouting of
an interrupted service. If the TE link resources are insufficient, replan the network.
deleted.
1. The board reports the BD_NOT_INSTALLED alarm. See the handling procedure
for the alarm to clear it.
board.
1. The board reports the WRG_BD_TYPE alarm. In this case, add the logical board
to the corresponding slot on the U2000. See the handling procedure for the alarm
to clear it.
1. The board reports the BD_STATUS alarm. See the handling procedure for the
alarm to clear it.
----End
Related Information
None.
10.4.11 CPW_OCH_SER_NOTOR
Description
The CPW_OCH_SER_NOTOR alarm indicates that the optical-layer OCh service is not on the
original trail.

Attribute
Warning QoS
Parameters
table.
Name Meaning
example, 1.1.1.2.

The service is not affected.
Fault Symptom
NOTE
Table 10-14 lists the fault symptoms for the CPW_OCH_SER_NOTOR alarm.
Table 10-14 Fault symptom for the CPW_OCH_SER_NOTOR alarm
Fault Symptom Cause
The current trail and the original trail of the Cause 1: The service is rerouted, or the
service are inconsistent. service is optimized.
Possible Causes
The possible cause of the CPW_OCH_SER_NOTOR alarm is as follows:
l Cause 1: The service is rerouted, or the service is optimized.

Procedure
1. Check whether alarms for traditional WDM equipment are generated on the original
trail of the service. If yes, analyze the alarms to identify faults and then rectify the
faults on the transport plane.
2. For a non-revertive service, revert the service to the original channel or optical port
so that the service is reverted to the original trail.
3. For a revertive service, manually revert the service to the previous trail or wait for
automatic reverting. If the alarm persists after the service is reverted to the previous
trail, revert the service to the original trail.
4. If reverting to the original trail is unnecessary, you can set the current trail of the
service as the original trail.
----End
Related Information
If the service is rerouted and the fault on the original trail is rectified, the service is reverted to
the previous trail automatically or at a specified time. After the service is reverted, the rerouting
LSP is retained for six minutes in case of a fiber cut on the current working trail. The
CPW_OCH_SER_NOTOR alarm persists within the six minutes and is cleared after the period
elapses.
10.4.12 CPW_OCH_SER_RRTLOCK
Description
The CPW_OCH_SER_RRTLOCK alarm indicates that rerouting of the optical-layer OCh
service is locked.
Attribute
Minor QoS
Parameters
table.
Name Meaning

Name Meaning
example, 1.1.1.2.

This alarm does not affect the service; however, if the service is interrupted, the service cannot
be restored, because rerouting of the service is locked.
Fault Symptom
NOTE
Table 10-15 lists the fault symptom for the CPW_OCH_SER_RRTLOCK alarm.
Table 10-15 Fault symptom for the CPW_OCH_SER_RRTLOCK alarm
Fault Symptom Cause
The CPW_OCH_SER_RRTLOCK alarm is Cause 1: The rerouting of the service is

reported. locked.
Possible Causes
The possible cause of the CPW_OCH_SER_RRTLOCK alarm is as follows:
l Cause 1: The rerouting of the service is locked.
Procedure
1. Check whether rerouting lockout is required for the service.
2. If rerouting lockout is not required, change the rerouting of the service to unlocked.
3. If rerouting lockout is required for the service, you do not need to proceed with the
alarm handling but you can suppress the alarm for the service.
----End
Related Information
None.

10.4.13 CPW_OCH_SER_SLADEG
Description
The CPW_OCH_SER_SLADEG alarm indicates that the optical-layer OCh service SLA is
degraded.
Attribute
Major QoS
Parameters
table.
Name Meaning
example, 1.1.1.2.
Error Indicates the type of the error. The value is in hexadecimal notation. Valid values of
the parameter are as follows:
l 0x0101: Only one LSP of the diamond service is available.
l 0x0102: The working and protection LSPs of the diamond service traverse the
same intermediate node, the same link, or the same SRLG.
l 0x0401: The two LSPs of the associated services traverse the same intermediate
node, the same link, or the same SRLG.

The service is not interrupted, but the service class is degraded.
Fault Symptom
NOTE
Table 10-16 lists the fault symptoms for the CPW_OCH_SER_SLADEG alarm.

Table 10-16 Fault symptoms for the CPW_OCH_SER_SLADEG alarm
Fault Symptom Cause
The error type is 0x0101. Cause 1: One LSP of the diamond service is
interrupted.
The error type is 0x0102. Cause 2: The working and protection LSPs of
the diamond service traverse the same
intermediate node, the same link, or the same
SRLG.
The error type is 0x0401. Cause 3: The two LSPs of the associated
services traverse the same intermediate node,
the same link, or the same SRLG.
Possible Causes
The possible causes of the CPW_OCH_SER_SLADEG alarm are as follows:
l Cause 1: One LSP of the diamond service is interrupted.

l Cause 2: The working and protection LSPs of the diamond service traverse the same
intermediate node, the same link, or the same SRLG.
l Cause 3: The two LSPs of the associated services traverse the same intermediate node, the
same link, or the same SRLG.
Procedure
1. Check the interrupted LSP of the service. View the alarms for traditional WDM
equipment along the LSP, and then analyze and rectify the fault on the transport plane.
1. Manually optimize the working or standby LSP so that the two LSPs are not
intersected. For details, see the description of service optimization operation.
1. Manually optimize the route for either of the associated services so that the two routes
are not intersected. For details, see the description of service optimization operation.
NOTE
Refer to Modifying the Route of an ASON Service for service optimization operation.
----End
Related Information
None.

10.4.14 CPW_OCH_SER_SYNFAIL
Description
The CPW_OCH_SER_SYNFAIL alarm indicates that the synchronization of the association
between two associated optical-layer OCh services fails.
In the case of two associated services with different source nodes, if the actual route of either
service is changed, the association between the source node of this service and the source node
of the other service needs to be synchronized, so that the other service is informed of the new
route information. This alarm is reported when the synchronization of association fails.
After the synchronization fails, the synchronization continues repeatedly and periodically until
it is successful. When the synchronization is successful, the alarm is cleared.
Attribute
Minor QoS
Parameters
table.
Name Meaning
example, 1.1.1.2.
Index Indicates the main index to the service. It is in decimal notation.

The service is not affected. Due to the failure of synchronization, however, whether the routes
of the associated services intersect with each other is unknown.
Fault Symptom
NOTE
the fault according to Handling Procedure described in this topic.
Table 10-17 lists the fault symptoms for the CPW_OCH_SER_SYNFAIL alarm.

Table 10-17 Fault symptom for the CPW_OCH_SER_SYNFAIL alarm

Fault Symptom Cause
The CPC_OSPF_CL_DOWN alarm is Cause 1: The control plane between the two
generated, indicating that control link is sources nodes of the associated services is
interrupted. unreachable.
The NE is offline. Cause 2: The source node of one of the two

associated services is reset.
One of the associated services does not exist. Cause 3: The associated service no longer
exists.
Possible Causes
The possible causes of the CPW_OCH_SER_SYNFAIL alarm are as follows:
l Cause 1: The control plane between the two sources nodes of the associated services is
unreachable.
l Cause 2: The source node of one of the two associated services is reset.
l Cause 3: The associated service no longer exists.
Procedure
unreachable.
1. View the control link topology, and check whether the control link is reachable to the
source nodes of the associated services. If not, see the procedure for handling the
CPC_OSPF_CL_DOWN alarm.
1. Check whether the source node of the associated service is reset. If yes, wait until the
node is started again.
1. Check whether the service exists on the source node of the associated service. If the
associated service does not exist, cancel the association, and then re-create a service
and set the association again.
NOTE
Refer to Setting Association of WDM ASON Trails for the creation of associated service.
----End
Related Information
None.

10.4.15 CPW_ODUk_SER_INT
Description
The CPW_ODUk_SER_INT alarm indicates a service interruption. k is equal to 0, 1, 2 or 3.
If none of the LSPs of a service fails to transmit the service, this alarm is reported. If any of the
LSPs can transmit the service, this alarm is cleared and an event indicating the end of this alarm
is reported.
Attribute
Critical QoS
Parameters
table.
Name Meaning
example, 1.1.1.2.

When this alarm occurs, the related service is interrupted.
Fault Symptom
NOTE
Table 10-18 lists the fault symptoms for the CPW_ODUk_SER_INT alarm.

Table 10-18 Fault symptom for the CPW_ODUk_SER_INT alarm
Fault Symptom Cause
The service is interrupted, and the alarm Cause 1: The rerouting function is locked
indicating that the rerouting function is manually.
locked is reported, but no event indicating
that rerouting fails is reported.
The service is interrupted, but no event Cause 2: All LSPs of the service are
indicating that rerouting fails is reported. interrupted, and the rerouting also fails.
The service is interrupted, and the alarms Cause 3: The boards for adding or dropping
such as BD_NOT_INSTALLED, services are offline.
WRG_BD_TYPE, and BD_STATUS for
traditional WDM equipment are generated.
Possible Causes
The possible causes of the CPW_ODUk_SER_INT alarm are as follows:

l Cause 2: All LSPs of the service are interrupted, and the rerouting also fails.
deleted.
board.
Procedure
1. Check whether the rerouting function of the service is locked. If yes, change the setting
so that the rerouting function is unlocked. Then, the service is automatically rerouted
and restored. Refer to Setting the Routing Attributes.
l Cause 2: All LSPs of the service are interrupted, and the rerouting also fails due to lack of
resources.
1. Check whether alarms for traditional WDM equipment are generated along the route
of each LSP for the service. If alarms for traditional WDM equipment are generated,
see the Alarms and Performance Events Reference to handle the alarms.
2. Check whether the network has sufficient TE link resources to support rerouting of
an interrupted service. If the TE link resources are insufficient, replan the network.
deleted.
1. The board reports the BD_NOT_INSTALLED alarm. See the handling procedure
for the alarm to clear it.

board.
1. The board reports the WRG_BD_TYPE alarm. In this case, add the logical board
to the corresponding slot on the U2000. See the handling procedure for the alarm
to clear it.
1. The board reports the BD_STATUS alarm. See the handling procedure for the
alarm to clear it.
----End
Related Information
None.
10.4.16 CPW_ODUk_SER_NOTOR
Description
The CPW_ODUk_SER_NOTOR alarm indicates that the service is not on the original trail. k
is equal to 0, 1, 2 or 3.
Attribute
Warning QoS
Parameters
table.
Name Meaning
example, 1.1.1.2.

The service is not affected.

Fault Symptom
NOTE
Table 10-19 lists the fault symptoms for the CPW_ODUk_SER_NOTOR alarm.
Table 10-19 Fault symptom for the CPW_ODUk_SER_NOTOR alarm
Fault Symptom Cause
The current trail and the original trail of the Cause 1: The service is rerouted, or the
service are inconsistent. service is optimized.
Possible Causes
The possible cause of the CPW_ODUk_SER_NOTOR alarm is as follows:
Procedure
1. Check whether alarms for traditional WDM equipment are generated on the original
trail of the service. If yes, analyze the alarms to identify faults and then rectify the
faults on the transport plane.
2. In the case of a non-revertive service, revert the service to the original channel or
optical interface so as to revert it to the original trail.
NOTE
If you revert a non-diamond OCh service to the original trail, the service is transiently
interrupted due to the cross-connection characteristic of the optical component.
3. In the case of a revertive service, manually revert the service to the previous trail or
wait for automatic reverting. If the alarm persists after the service is reverted to the
previous trail, revert the service to the original trail.
4. If reverting to the original trail is unnecessary, you can set the current trail of the
service as the original trail.
NOTE
If the rerouted service is a revertive service, do not set the current trail which the service is not
reverted to as the original trail.
For the operation steps for reverting to the original route, see Reverting A WDM ASON Trail
to the Original Route.
----End
Related Information
None.

10.4.17 CPW_ODUk_SER_RRTLOCK
Description
The CPW_ODUk_SER_RRTLOCK alarm indicates that rerouting of the ODUk service is
locked. k is equal to 0, 1, 2 or 3.
Attribute
Minor QoS
Parameters
table.
Name Meaning
example, 1.1.1.2.

This alarm does not affect the service; however, if the service is interrupted, the service cannot
be restored, because rerouting of the service is locked.
Fault Symptom
NOTE
Table 10-20 lists the fault symptom for the CPW_ODUk_SER_RRTLOCK alarm.
Table 10-20 Fault symptom for the CPW_ODUk_SER_RRTLOCK alarm
Fault Symptom Cause
The CPW_ODUk_SER_RRTLOCK alarm is Cause 1: The rerouting of the service is

reported. locked.

Possible Causes
The possible cause of the CPW_ODUk_SER_RRTLOCK alarm is as follows:
Procedure
1. Check whether rerouting lockout is required for the service.
2. If rerouting lockout is not required, change the rerouting of the service to unlocked.
3. If rerouting lockout is required for the service, you do not need to proceed with the
alarm handling but you can suppress the alarm for the service.
----End
Related Information
None.
10.4.18 CPW_ODUk_SER_SLADEG
Description
The CPW_ODUk_SER_SLADEG alarm indicates that the service SLA is degraded. k is equal
to 0, 1, 2 or 3.
Attribute
Major QoS
Parameters
table.
Name Meaning
example, 1.1.1.2.

Name Meaning
Error Indicates the type of the error. The value is in hexadecimal notation. Valid values of
the parameter are as follows:
l 0x0101: Only one LSP of the diamond service is available.
l 0x0102: The working and protection LSPs of the diamond service traverse the
same intermediate node, the same link, or the same SRLG.
l 0x0401: The two LSPs of the associated services traverse the same intermediate
node, the same link, or the same SRLG.

The service is not interrupted, but the service class is degraded.
Fault Symptom
NOTE
Table 10-21 lists the fault symptoms for the CPW_ODUk_SER_SLADEG alarm.
Table 10-21 Fault symptoms for the CPW_ODUk_SER_SLADEG alarm
Fault Symptom Cause
The error type is 0x0101. Cause 1: One LSP of the diamond service is
interrupted.
The error type is 0x0102. Cause 2: The working and protection LSPs of
the diamond service traverse the same
intermediate node, the same link, or the same
SRLG.
The error type is 0x0401. Cause 3: The two LSPs of the associated
services traverse the same intermediate node,
the same link, or the same SRLG.
Possible Causes
The possible causes of the CPW_ODUk_SER_SLADEG alarm are as follows:


Procedure
1. Check the interrupted LSP of the service. View the alarms for traditional WDM
equipment along the LSP, and then analyze and rectify the fault on the transport plane.
1. Manually optimize the working or standby LSP so that the two LSPs are not
intersected. For details, see the description of service optimization operation.
1. Manually optimize the route for either of the associated services so that the two routes
are not intersected. For details, see the description of service optimization operation.
NOTE
Refer to Modifying the Route of an ASON Service for service optimization operation.
----End
Related Information
None.
10.4.19 CPW_ODUk_SER_SYNFAIL
Description
The CPW_ODUk_SER_SYNFAIL alarm indicates that the synchronization of the association
between two associated services fails. k is equal to 0, 1, 2 or 3.
In the case of two associated services with different source nodes, if the actual route of either
service is changed, the association between the source node of this service and the source node
of the other service needs to be synchronized, so that the other service is informed of the new
route information. This alarm is reported when the synchronization of association fails.
After the synchronization fails, the synchronization continues repeatedly and periodically until
it is successful. When the synchronization is successful, the alarm is cleared.
Attribute
Minor QoS
Parameters
table.

Name Meaning
example, 1.1.1.2.
Index Indicates the main index to the service. It is in decimal notation.

The service is not affected. Due to the failure of synchronization, however, whether the routes
of the associated services intersect with each other is unknown.
Fault Symptom
NOTE
the fault according to Handling Procedure described in this topic.
Table 10-22 lists the fault symptoms for the CPW_ODUk_SER_SYNFAIL alarm.
Table 10-22 Fault symptom for the CPW_ODUk_SER_SYNFAIL alarm
Fault Symptom Cause
The CPC_OSPF_CL_DOWN alarm is Cause 1: The control plane between the two
generated, indicating that control link is sources nodes of the associated services is
interrupted. unreachable.
The NE is offline. Cause 2: The source node of one of the two

associated services is reset.
One of the associated services does not exist. Cause 3: The associated service no longer
exists.
Possible Causes
The possible causes of the CPW_ODUk_SER_SYNFAIL alarm are as follows:
unreachable.
Procedure
unreachable.

1. View the control link topology, and check whether the control link is reachable to the
source nodes of the associated services. If not, see the procedure for handling the
CPC_OSPF_CL_DOWN alarm.
1. Check whether the source node of the associated service is reset. If yes, wait until the
node is started again.
1. Check whether the service exists on the source node of the associated service. If the
associated service does not exist, cancel the association, and then re-create a service
and set the association again.
NOTE
Refer to Setting Association of WDM ASON Trails for the creation of associated service.
----End
Related Information
None.
10.4.20 CPW_ODUk_TEL_DEG
Description
The CPW_ODUk_TEL_DEG alarm indicates that the ODUk TE link is degraded. k is equal to
1, 2, 3, or 5G.
Attribute
Critical Communication alarm
Parameters
table.
Name Meaning
node_id Indicates the node ID of the NE on the link. The value is in decimal dotted notation,
if_index Indicates the TE link index and the value is in hexadecimal notation.


The service is not affected; however, the creation of a service, optimize the existing service, or
rerouting of the existing service on the TE link fails.
Fault Symptom
NOTE
Table 10-23 lists the fault symptoms for the CPW_ODUk_TEL_DEG alarm.
Table 10-23 Fault symptom for the CPW_ODUk_TEL_DEG alarm
Fault Symptom Cause
The CPC_CC_DOWN alarm is reported, the Cause 1: No control channel is available

creation of a service, optimize the existing between the two end nodes of the TE link.
service, or rerouting of the existing service on
the TE link fails.
The relevant board reports alarms related to Cause 2: The software or hardware of the
the board hardware, and the creation of a board, where the optical interface of the TE
service, optimize the existing service, or link resides, is faulty.
rerouting of the existing service on the TE
link fails.
Possible Causes
resides, is faulty.
Procedure
1. View the control channel at the two ends of the TE link. For details, see the procedure
for handling the CPC_CC_DOWN alarm.
2. Check whether the system fails to perform the LMP check because (1) the control
channel between NEs is shut down, (2) the management of the opposite link is
disabled, or (3) the check of the opposite link is disabled. If yes, rectify the fault
properly according to the specific cause.
resides, is faulty.
----End

Related Information
None.
10.4.21 CPW_ODUk_TEL_DOWN
Description
The CPW_ODUk_TEL_DOWN alarm indicates that the ODUk TE link in the OTN domain is
interrupted. k is equal to 1, 2, 3, or 5G.
The alarm is reported when the ODUk TE link is interrupted, or when the ODUk TE link is
unreachable after being created. The alarm is cleared when the interrupted ODUk TE link is
restored and an event indicating the end of this alarm is reported.
Attribute
Parameters
table.
Name Meaning
node_id Indicates the node ID of the NE on the link. The value is in dotted decimal notation,
Error Indicates the error type and the value is in hexadecimal notation. The valid values
of the parameter are as follows:
l 0x3: indicates that the ODUk TE link check fails.

The service is affected. After the alarm is generated on the ODUk TE link, the service on the
link is interrupted and the link is no longer available. In this case, rerouting of the service may
be performed.

Fault Symptom
NOTE
Table 10-24 lists the fault symptoms for the CPW_ODUk_TEL_DOWN alarm.
Table 10-24 Fault symptom for the CPW_ODUk_TEL_DOWN alarm
Fault Symptom Cause
The ODUk TE link is down, and the ASON Cause 1: The ODUk TE link check fails.
service on the link may be rerouted or
interrupted. In addition, no alarm for
traditional WDM equipment is generated.
Possible Causes
When the link is physically or logically interrupted, it cannot bear the data of the control plane
and transmission plane. The following alarms may cause an interruption of the TE link:
l Cause 1: The ODUk TE link check fails. (0x3) This problem may be due to the following
causes:
– Sub-cause 1: The LMP protocol of the opposite TE link is disabled.
– Sub-cause 2: No control channel is available between the two end nodes of the ODUk
TE link.
– Sub-cause 3: The NE software versions do not match the software versions of the boards
on the ODUk TE link.
– Sub-cause 4: The TE link detects two different remote link identifiers because the fibers
are connected improperly.
– Sub-cause 5: The opposite node/optical interface of the TE link that has services is
inconsistent with the original node/optical interface, because the fibers are connected
improperly.
l
Procedure
l Cause 1: The ODUk TE link check fails.
If this alarm is caused by a check failure, the check may be in process. In this case, wait
for tens of seconds. If the link is still interrupted, proceed with the next step to rectify the
fault according to the specific causes.

1. Check and ensure that the LMP protocol at the opposite end of the ODUk TE link
is enabled.
– Sub-cause 2: No control channel is available between the two end nodes of the ODUk
TE link.

1. Check all the control channels of the NE that reports this alarm. Make sure that at
least one control channel is connected to the opposite NE, and the control channel
state is up. Then, view alarms on the link to make sure that this alarm is cleared.
on the TE link.
1. Check and ensure that the NE software versions match the board software versions.
1. Check the fiber connections to ensure that they are properly established.
improperly.
----End
Related Information
After the TE link is interrupted, if the cause of the interruption is changed, an event is reported,
indicating the interruption due to the original cause ends and the alarm is reported again
according to the new cause after the change.
If the link is interrupted because the link administration status is set to down, this alarm is not
reported on the link. If the link interruption alarm is generated previously, the alarm is cleared
after the link administration status is set to down, and then an event indicating the end of
interruption is reported.
Whether an LMP check failure can cause an interruption of the TE link is determined according
to the following condition. If the link cannot obtain the information about the remote end and
no board off-service and optical interface alarm is generated, it can be determined that the LMP
check fails and thus the link is interrupted.
When the TE link is normal and is able to obtain the information about the remote end, if the
system fails to check the LMP because the available control channels are disabled, the
administration status at the opposite end is disabled, or the link check at the opposite is disabled,
the link interruption alarm is not reported. Instead, the CPW_ODUk_TEL_DEG alarm is
reported, indicating that the link is degraded.
When a factor (for example, the optical interface alarm disappears, the board gets online, or the
administration status is up) that can cause a link interruption no longer exists, the link interruption
alarm is reported for a short time because of an LMP check failure. The link interruption alarm
caused by the LMP check failure is cleared after the LMP check is complete and the information
about the remote end is successfully obtained.
10.4.22 CPW_ODUk_TEL_ODURMIS
Description
The CPW_ODUk_TEL_ODURMIS alarm indicates that the ODUk SPRing configurations in
the OTN domain are inconsistent. k is equal to 2 or 3.

Attribute
Major QoS
Parameters
table.
Name Meaning
router_id Indicates the node ID of the NE on the link. The value is in dotted decimal

The service is affected. The creation of an ASON service fails or the protection for the existing
ASON service fails.
Fault Symptom
NOTE
Table 10-25 lists the fault symptom for the CPW_ODUk_TEL_ODURMIS alarm.
Table 10-25 Fault symptom for the CPW_ODUk_TEL_ODURMIS alarm
Fault Symptom Cause
The creation of an ASON service fails or the Cause 1: The ODUk SPRing configurations
protection for the existing ASON service at the two ends of the TE link are inconsistent.
fails.
Possible Causes
The possible cause of the CPW_ODUk_TEL_ODURMIS alarm is as follows:

l Cause 1: The ODUk SPRing configurations at the two ends of the TE link are inconsistent.
Procedure
1. Check whether the channel resource reservation at two ends of the link is consistent.
If not, reserve the resource at the end where the resource is idle, or cancel the
reservation at the end where the resource is reserved.
----End
Related Information
None.
10.4.23 CPW_ODUk_TEL_PATHMIS
Description
The CPW_ODUk_TEL_PATHMIS alarm indicates that the path status at the two ends of the
ODUk link in the OTN domain is inconsistent. k is equal to 1, 2, 3, or 5G.
Attribute
Major QoS
Parameters
table.
Name Meaning
channel_num Indicates the channels that are in different states at the two ends of the link
and the value is in hexadecimal notation.
Local path state Indicates the status of the optical interface at the local end on the link and
the value is in decimal notation.

Name Meaning
remote path state Indicates the status of the optical interface at the remote end on the link and

The channels whose statuses are inconsistent on the TE link become unavailable. As a result,
the success rate of rerouting may be affected.
Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the CPW_ODUk_TELOVPN_MM alarm are as follows:
l Cause 1: The resource reservation operation is not finished. That is, the resource is reserved
at one end but remains idle at the other end.
l Cause 2: Resource release operations are incomplete. At one end, the resource is released,
while at the other end, the resource is occupied.
l Cause 3: The service conversion is incomplete. At one end, the service is a static service,
while at the other end, the service is an ASON service.
Procedure
l Cause 1: The resource reservation operation is not finished. The resource is reserved at one
end but remains idle at the other end.
1. Check whether the channel states at the two ends of the TE link are consistent. If the
channel is idle at one end, but is busy at the other end, delete the cross-connection at
the busy end. Alternatively, create a cross-connection at the end where the channel is
idle or at the end where certain channel resources are reserved.
whereas at the other end, the service is an ASON service.
channel is occupied by a static service at one end but occupied by an ASON service
at the other end, downgrade the ASON service to a static service.

2. Check whether the egress channel is idle but the ingress channel is busy at the two
ends of the link. If yes, a residual unidirectional cross-connection exists. In this case,
delete the residual unidirectional cross-connection, or add a reverse cross-connection.
----End
Related Information
None.
10.4.24 CPW_OMS_TEL_DEG
Description
The CPW_OMS_TEL_DEG alarm indicates that the OMS TE link is degraded.
Attribute
Parameters
table.
Name Meaning

Fault Symptom
NOTE

Table 10-26 lists the fault symptoms for the CPW_OMS_TEL_DEG alarm.
Table 10-26 Fault symptom for the CPW_OMS_TEL_DEG alarm
Fault Symptom Cause

the TE link fails.
link fails.
Possible Causes
resides, is faulty.
Procedure
resides, is faulty.
----End
Related Information
None.
10.4.25 CPW_OMS_TEL_DOWN
Description
The CPW_OMS_TEL_DOWN alarm indicates that the OMS TE link is interrupted.

The alarm is reported when the OMS TE link is interrupted, or when the OMS TE link is
unreachable after being created. The alarm is cleared when the interrupted OMS TE link is
Attribute
Parameters
table.
Name Meaning
l 0x3: indicates that the OMS TE link check fails.

The service is affected. After the alarm is generated on the OMS TE link, the service on the link
is interrupted and the link is no longer available. In this case, rerouting of the service may be
performed.
Fault Symptom
NOTE
Table 10-27 lists the fault symptoms for the CPW_OMS_TEL_DOWN alarm.

Table 10-27 Fault symptom for the CPW_OMS_TEL_DOWN alarm
Fault Symptom Cause
The OMS TE link is down, and the ASON Cause 1: The OMS TE link check fails.
Possible Causes
l Cause 1: The OMS TE link check fails. (0x3) This problem may be due to the following
causes:
– Sub-cause 2: No control channel is available between the two end nodes of the OMS
TE link.
on the OMS TE link.
improperly.
Procedure
l Cause 1: The OMS TE link check fails.

1. Check and ensure that the LMP protocol at the opposite end of the OMS TE link
is enabled.
– Sub-cause 2: No control channel is available between the two end nodes of the OMS
TE link.
on the TE link.

improperly.
----End
Related Information
the link interruption alarm is not reported. Instead, the CPW_OMS_TEL_DEG alarm is reported,
indicating that the link is degraded.
10.4.26 CPW_OMS_TEL_EXHAUST
Description
The CPW_OMS_TEL_EXHAUST alarm indicates that the resource utilization of the optical-
layer OMS TE link exceeds the preset threshold.
Attribute
Minor Communication alarm
Parameters


table.
Name Meaning
sub-shelf Indicates the subrack of the link and the value is in decimal notation.
port Indicates the optical interface of the link and the value is in decimal notation.

The existing service is not affected, but the service survivability is affected.
Fault Symptom
NOTE
Table 10-28 lists the fault symptom for the CPW_OMS_TEL_EXHAUST alarm.
Table 10-28 Fault symptom for the CPW_OMS_TEL_EXHAUST alarm
Fault Symptom Cause
The CPW_OMS_TEL_EXHAUST alarm is Cause 1: The resource utilization of the TE

reported. link exceeds the preset threshold because the
resources are occupied by services or
manually reserved.
Possible Causes
The possible cause of the CPW_OMS_TEL_EXHAUST alarm is as follows:
l Cause 1: The resource utilization of the TE link exceeds the preset threshold because the
resources are occupied by services or manually reserved.
Procedure
l Cause 1: The resource utilization of the TE link exceeds the preset threshold because the
resources are occupied by services or manually reserved.
1. Assess the resource utilization. If increasing the threshold does not greatly decrease
the survivability of the services in the existing network, set the threshold to a greater
one.

2. If the resource threshold cannot be increased, replan the existing services or the
network resources so that the resource utilization is lower than the threshold.
----End
Related Information
None.
10.4.27 CPW_OMS_TELOVPN_MM
Description
The CPW_OMS_TELOVPN_MM alarm indicates that the channels at the two ends of the OMS
TE link belong to different OVPN customers.
Attribute
Major QoS
Parameters
table.
Name Meaning
channel_num Indicates the channels that are in different states at the two ends of the link and
the value is in hexadecimal notation.
notation.
decimal notation.
OVPN-ID Indicates the OVPN ID of the local end on the link and the value is in
hexadecimal notation.
Sub_shelf Indicates the subrack at the remote end on the link and the value is in decimal
notation.

Name Meaning
board Indicates the slot at the remote end on the link and the value is in decimal
notation.
port Indicates the optical interface at the remote end on the link and the value is in
decimal notation.
OVPN_ID Indicates the OVPN ID of the remote end on the link and the value is in
hexadecimal notation.

This alarm does not affect the existing service. The channel resources assigned to different
OVPN customers at the two ends of the link, however, become unavailable. As a result, the
success rate of rerouting may be affected.
Fault Symptom
NOTE
Table 10-29 lists the fault symptoms for the CPW_OMS_TELOVPN_MM alarm.
Table 10-29 Fault symptom for the CPW_OMS_TELOVPN_MM alarm
Fault Symptom Cause
The CPW_OMS_TELOVPN_MM alarm is Cause 1: The OVPN configurations at the two

reported. ends of the TE link are different.
Possible Causes
The possible cause of the CPW_OMS_TELOVPN_MM alarm is as follows:
l Cause 1: A channel on the TE link is assigned to different OVPN customers at the two ends
of the link. In addition, the channel at neither end is configured as a shared resource.
Procedure
l Cause 1: A channel on the TE link is assigned to different OVPN customers at the two ends
of the link. In addition, the channel at neither end is configured as a shared resource.
1. Usually, the control plane can be automatically reestablished to restore the LSP
without user intervention. Re-assign the resource that reports the alarm to an OVPN
customer according to the network design.
----End
Related Information
The NEs at the two ends of the TE link report the CPW_OMS_TELOVPN_MM alarm.

10.4.28 CPW_OMS_TEL_OCHMIS
Description
The CPW_OMS_TEL_OCHMIS alarm indicates that the settings of the maximum number of
channels at the two ends of the OMS TE link are inconsistent.
Attribute
Parameters
table.
Name Meaning
channel_num Indicates the channels that are in different states at the two ends of the link,
sub-shelf Indicates the subrack of the link, and the value is in decimal notation.
board Indicates the board of the link, and the value is in decimal notation.
port Indicates the optical interface of the link, and the value is in decimal
notation.
local path state Indicates the status of the optical interface at the local end on the link, and
remote path state Indicates the status of the optical interface at the remote end on the link, and

The service signals are not affected but the symmetry detection of the occupancy status of
channels is affected.
Fault Symptom
None.

NOTE
Possible Causes
The possible cause of the CPW_OMS_TEL_OCHMIS alarm is as follows:
l Cause 1: The settings of the maximum number of channels at the two ends of the OMS TE
link are inconsistent.
Procedure
l Cause 1: The settings of the maximum number of channels at the two ends of the OMS TE
link are inconsistent.
1. Check whether the settings of the maximum number of wavelengths for optical
interfaces at the two ends of the TE link are the same.
2. If not, change the setting of the maximum number of wavelengths at one end to ensure
consistency.
----End
Related Information
None.
10.4.29 CPW_OMS_TEL_PATHMIS
Description
The CPW_OMS_TEL_PATHMIS alarm indicates that the path status at the two ends of the
OMS TE link is inconsistent.
Attribute
Major QoS
Parameters
table.
Name Meaning

Name Meaning

Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the CPW_OMS_TELOVPN_MM alarm are as follows:
Procedure

----End
Related Information
None.
10.4.30 CPW_OTUk_TEL_DEG
Description
The CPW_OTUk_TEL_DEG alarm indicates that the OTUk TE link is degraded. k is equal to
1, 2, 3, or 5G.
Attribute
Parameters
table.
Name Meaning


Fault Symptom
NOTE
Table 10-30 lists the fault symptoms for the CPW_OTUk_TEL_DEG alarm.
Table 10-30 Fault symptom for the CPW_OTUk_TEL_DEG alarm
Fault Symptom Cause

the TE link fails.
link fails.
Possible Causes
resides, is faulty.
Procedure
resides, is faulty.
----End

Related Information
None.
10.4.31 CPW_OTUk_TEL_DOWN
Description
The CPW_OTUk_TEL_DOWN alarm indicates that the OTUk TE link in the OTN domain is
interrupted. k is equal to 1, 2, 3, or 5G.
The alarm is reported when the OTUk TE link is interrupted, or when the OTUk TE link is
unreachable after being created. The alarm is cleared when the interrupted OTUk TE link is
Attribute
Parameters
table.
Name Meaning
l 0x3: indicates that the OTUk TE link check fails.

The service is affected. After the alarm is generated on the OTUk TE link, the service on the
link is interrupted and the link is no longer available. In this case, rerouting of the service may
be performed.

Fault Symptom
NOTE
Table 10-31 lists the fault symptoms for the CPW_OTUk_TEL_DOWN alarm.
Table 10-31 Fault symptom for the CPW_OTUk_TEL_DOWN alarm
Fault Symptom Cause
The OTUk TE link is down, and the ASON Cause 1: The OTUk TE link check fails.
Possible Causes
l Cause 1: The OTUk TE link check fails. (0x3) This problem may be due to the following
causes:
– Sub-cause 2: No control channel is available between the two end nodes of the OTUk
TE link.
on the OTUk TE link.
improperly.
l
Procedure
l Cause 1: The OTUk TE link check fails.

1. Check and ensure that the LMP protocol at the opposite end of the OTUk TE link
is enabled.
– Sub-cause 2: No control channel is available between the two end nodes of the OTUk
TE link.

on the TE link.
improperly.
----End
Related Information
the link interruption alarm is not reported. Instead, the CPW_OTUk_TEL_DEG alarm is
reported, indicating that the link is degraded.
10.4.32 CPW_OTUk_TEL_ODURMIS
Description
The CPW_OTUk_TEL_ODURMIS alarm indicates that the ODUk SPRing configurations in
the OTN domain are inconsistent. k is equal to 1 or 2.

Attribute
Major QoS
Parameters
table.
Name Meaning

The service is affected. The creation of an ASON service fails or the protection for the existing
ASON service fails.
Fault Symptom
NOTE
Table 10-32 lists the fault symptom for the CPW_OTUk_TEL_ODURMIS alarm.
Table 10-32 Fault symptom for the CPW_OTUk_TEL_ODURMIS alarm
Fault Symptom Cause
The creation of an ASON service fails or the Cause 1: The ODUk SPRing configurations
protection for the existing ASON service at the two ends of the TE link are inconsistent.
fails.
Possible Causes
The possible cause of the CPW_OTUk_TEL_ODURMIS alarm is as follows:

Procedure
----End
Related Information
None.
10.4.33 CPW_OTUk_TEL_PATHMIS
Description
The CPW_OTUk_TEL_PATHMIS alarm indicates that the path status at the two ends of the
OTUk link in the OTN domain is inconsistent. k is equal to 1, 2, 3, or 5G.
Attribute
Major QoS
Parameters
table.
Name Meaning

Name Meaning

Fault Symptom
None.
NOTE
Possible Causes
The possible causes of the CPW_OTUk_TELOVPN_MM alarm are as follows:
Procedure

----End
Related Information
None.
10.4.34 CPW_SER_XC_EXCEPT
Description
The CPW_SER_XC_EXCEPT alarm indicates a cross-connection exception in an ASON
service. This alarm is reported when the cross-connection information about the ASON service
is lost. When the cross-connection information about all ASON services is normal, the alarm is
cleared and an event indicating the end of this alarm is reported.
Attribute
Major QoS
Parameters
table.
Name Meaning
DB Node ID Indicates the source node ID of the service. The value is in dotted decimal

When the CPW_SER_XC_EXCEPT alarm is generated, the related service is interrupted.
Fault Symptom
NOTE
Table 10-33 lists the fault symptom for the CPW_SER_XC_EXCEPT alarm.

Table 10-33 Fault symptom for the CPW_SER_XC_EXCEPT alarm
Fault Symptom Cause
The related service is interrupted. Cause 1: When the ASON software is

performing an operation related to cross-
connections (for example, the ASON
software is performing rerouting), the NE is
reset. Before the NE is reset, the cross-
connection information is not saved in the
database.
Possible Causes
The possible cause of the CPW_SER_XC_EXCEPT alarm is as follows:
l Cause 1: When the ASON software is performing an operation related to cross-connections

(for example, the ASON software is performing rerouting), the NE is reset. Before the NE
is reset, the cross-connection information is not saved in the database.
Procedure
l Cause 1: When the ASON software is performing an operation related to cross-connections
(for example, the ASON software is performing rerouting), the NE is reset. Before the NE
is reset, the cross-connection information is not saved in the database.
1. Check the cross-connections of the ASON services on the NE, and find out the ASON
services whose cross-connections are lost.
2. Delete the ASON services whose cross-connections are lost, and then re-create them.
----End
Related Information
None.
10.5 Alarm Handling(OCS)

Context
Only the handling procedures of the control plane alarms are described in this section. For the
transport plane alarms, refer to the following documents.
l OptiX OSN 8800 Intelligent Optical Transport Platform Alarms and Performance Events
Reference
10.5.1 CP_ASER_SYNC_FAIL

Description
The CP_ASER_SYNC_FAIL is an alarm indicating that the synchronization of associated
services fails.
l When either of the associated services that do not share one source node changes the actual
route, the source node of the service needs to be synchronized with the source node of the
other service and notify it of the new route. If the synchronization fails, the
CP_ASER_SYNC_FAIL alarm occurs.
l After the synchronization of associated services fails, the periodical attempts of
synchronization continue until the synchronization succeeds. Then, the
CP_ASER_SYNC_FAIL alarm is cleared.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Scr Indicates the source node ID of this service.
Dst Indicates the sink node ID of this service.
Index Indicates the ID of the services, which is the only identity of the services
created at one source node.
Associated Src Indicates the source node ID of the service that is associated to this service.
Dst Indicates the sink node ID of the service that is associated to this service.
Index Indicates the ID of the service that is associated to this service, which is the
only identity of the services created at one source node.

When the CP_ASER_SYNC_FAIL alarm occurs, the services are not affected, but the routes
of associated services may be intersected due to the synchronization failure.

Fault Symptom
NOTE
Table 10-34 lists the symptoms of the CP_ASER_SYNC_FAIL alarm.
Table 10-34 Symptoms of the CP_ASER_SYNC_FAIL alarm
Fault Symptom Cause
The synchronization of l Cause 1: The IP connection is unavailable.

associated services fails. l Cause 2: The ASON feature is disabled at the opposite node
of the associated service.
l Cause 3: The data of associated services stored in the
database is lost due to abnormal conditions.
Possible Causes
The possible causes of the CP_ASER_SYNC_FAIL alarm are as follows:
l Cause 1: The IP connection is unavailable.
l Cause 2: The ASON feature is disabled at the opposite node of the associated service.
l Cause 3: The data of associated services stored in the database is lost due to abnormal
conditions.
Procedure
l Cause 1: The IP connection is unavailable.
Check the control link topology and determine whether the remote node is reachable. For
details, see 5.1.11 Synchronizing Control Links Networkwide. If the remote node is
unreachable, ensure that there are direct or indirect control channels between two NEs. If
there are no control channels between two NEs, find out the reason why the control channels
are unavailable and rectify the faulty by referring to 10.5.17 CPC_CC_DOWN.
l Cause 2: The ASON feature is disabled at the opposite node of the associated service.
Check the ASON feature and node status of the opposite node. If the ASON feature is
disabled, enable it by referring to 5.1.6 Enabling the ASON Feature .
l Cause 3: The data of associated services stored in the database is lost due to abnormal
conditions.
Check whether the associated service exists at the opposite node. If not, create or restore
the associated service, or cancel the association as required. For details, see 7.3.7 Creating
Two Associated ASON Trails.
----End
Related Information
None.

10.5.2 CP_FIBER_CONNECT_FAULT
Description
The CP_FIBER_CONNECT_FAULT is an alarm indicating the fiber misconnection.
l This alarm occurs when the fibers at both ends of a link are misconnected.
l This alarm is cleared when the fibers at both ends of a link are connected properly.
Attribute
Parameters
table.
Name Meaning
Node Indicates the node ID of the NE that reports the alarm, for example, 1.1.1.1.
TE LinkID Indicates the ID of the TE link that reports the alarm. The TE link ID is represented
by hexadecimals, for example, 0x6c000001.
Board Indicates the slot ID of the board that reports the alarm. The slot ID is represented
by decimals.
Port Indicates the ID of the port that reports the alarm. The port ID is represented by
decimals.

When the CP_FIBER_CONNECT_FAULT alarm occurs, the TE link cannot pass the
verification.
Fault Symptom
NOTE
Table 10-35 lists the symptoms of the CP_FIBER_CONNECT_FAULT alarm.

Table 10-35 Symptoms of the CP_FIBER_CONNECT_FAULT alarm
Fault Symptom Cause
The alarm indicating the fiber Cause 1: The fibers are misconnected.
misconnection is reported.
Possible Causes
Cause 1: The fibers are misconnected.
Procedure
Step 1 Locate the related board and port according to the alarm parameters.
Step 2 Check the fiber connections and reconnect the misconnected fibers.
----End
Related Information
None.
10.5.3 CP_LSP_NO_PRERRT
Description
The system reports this alarm when no preset restoration trail is available in the process of
regularly refreshing the preset restoration trails. When a preset restoration trail is available, the
system reports that this alarm is cleared.
Attribute
Major QoS
Parameters
table.
Name Meaning
Src Indicates the source node ID of the service. The value is expressed in dotted decimal

Name Meaning
Dst Indicates the destination node ID of the service. The value is expressed in dotted
decimal notation, for example, 1.1.1.2.
Index Indicates the main index to the service. It is expressed in decimal notation.
Instance Indicates the number of the service instance. It is expressed in decimal notation.
IsFirst Indicates whether the LSP is the first LSP (1 for yes and 0 for no). It is expressed in
decimal notation.

When this alarm is generated, the existing service is not affected, but a preset restoration trail is
unavailable during rerouting of the service on this faulty LSP.
Fault Symptom
NOTE
Possible Causes
The possible cause of this alarm is as follows:
l Cause 1: No preset restoration trail is available in the process of regularly refreshing the
preset restoration trails.
Procedure
l Cause 1: No preset restoration trail is available in the process of regularly refreshing the
preset LSPs.
1. You do not need to handle this alarm. When a preset restoration trail is available, the
trail list is automatically updated.
----End
Related Information
None
10.5.4 CP_LSP_OVPN_MM
Description
The CP_LSP_OVPN_MM is an alarm indicating that the LSP color is different from the color
of the resources the LSP uses. This alarm is cleared when the LSP color is the same as the color
of the resources the LSP uses.

Attribute
Major Service alarm
Parameters
table.
Name Meaning
Src Indicates the source node ID of the service that reports the alarm, for example,
1.1.1.1.
Dst Indicates the sink node ID of the service that reports the alarm, for example, 1.1.1.2.
Index Indicates the index of the service that reports the alarm. The index is represented by
decimals.
Instance Indicates the LSP instance of the service that reports the alarm. The LSP instance
is represented by decimals.
MisType Indicates the reason why the service reports the alarm. The reason is represented by
hexadecimals.
l 0x1: Color difference on the service path.
l 0x2: Color difference on the resource reservation path.
l 0x3: Color differences on the service path and the resource reservation path.

When the CP_LSP_OVPN_MM alarm occurs, services are not affected, but the services in
another color may have no available resources because this LSP uses the resources allocated for
the services in that color.
Fault Symptom
NOTE
Table 10-36 lists the symptoms of the CP_LSP_OVPN_MM alarm.

Table 10-36 Symptoms of the CP_LSP_OVPN_MM alarm
Fault Symptom Cause
This alarm does not cause l Cause 1: The color of services is changed.
service interruptions. Resources l Cause 2: The color of the resources that the LSP uses
are allocated and colored based is changed.
on services. A service in a
certain color uses the resources l Cause 3: The service is rerouted and no resources in the
allocated for the services in corresponding color are available, so the service uses
another color, so the services in the shared color resources.
that color may have inadequate l Cause 4: Certain information about the service color or
resources. resource color is lost on the control plane.
Possible Causes
The possible causes of the CP_LSP_OVPN_MM alarm are as follows:
l Cause 1: The color of the service is changed.

l Cause 2: The color of the resources that the LSP uses is changed.
l Cause 3: The service is rerouted and no resources in the corresponding color are available,
so the service uses the shared color resources.
l Cause 4: Certain information about the service color or resource color is lost on the control
plane.
Procedure
l Cause 1: The color of the service is changed.
Configure or change the color of the service that is not at the UNI server layer to the same
as the color of the resources that the service uses. For details, see Querying the TE Link
Resources of the OVPN Customers.
l Cause 2: The color of the resources that the LSP uses is changed.
Check the colors of the SDH links and timeslots along the LSP. If the resources in a certain
color are not allocated according to the resource coloring scheme, do as follows:
– Change the color of the resources according to the resource coloring scheme.
– Revise the resource coloring scheme. Allocate resources based on services, and ensure
that the color of the resources is the same as the color of the service that uses the
resources.
For details, see Querying the TE Link Resources of the OVPN Customers.
l Cause 3: The service is rerouted and no resources in the corresponding color are available,
so the service uses the shared color resources.
Two solutions are available.
NOTE
Solution 2 requires revising the resource coloring scheme, so it is not recommended.

– Solution 1: Analyze the reason why the service is rerouted and uses the shared color
resources. After the original service path is restored, route the service to the original
path.

– Solution 2: Allocate the resources in a corresponding color to the service. For details,
see Querying the TE Link Resources of the OVPN Customers.
l Cause 4: Certain information about the service color or resource color is lost on the control
plane.
Use the resources of a corresponding color for the LSP. For details, see Querying the TE
Link Resources of the OVPN Customers.
----End
Related Information
None.
10.5.5 CP_MSP_EWUOVPN_MM
Description
The CP_MSP_EWUOVPN_MM is an alarm indicating that the color of the west working
timeslot is different from the color of the east working timeslot.
l This alarm occurs when the west working timeslot and the east working timeslot on the
MSP network have different colors.
l This alarm is cleared when the west working timeslot and the east working timeslot on the
MSP network have the same color.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
MSP ID Indicates the ID of the MSP group that reports the alarm, for example, 1.
MSP Type Indicates the protection type of the MSP network that reports the alarm. The value
is represented by hexadecimals. If the parameter takes 0x10, it indicates the ring
MSP.


When the CP_MSP_EWUOVPN_MM alarm occurs, the system only prompts you to check
whether the resource allocation is reasonable.
Fault Symptom
NOTE
Table 10-37 lists the fault symptoms of the CP_MSP_EWUOVPN alarm.
Table 10-37 Symptoms of the CP_MSP_EWUOVPN_MM alarm
Fault Symptom Cause
The alarm indicating Cause 1: The west working timeslot and the east working timeslot
the different colors of have different colors.
the west working
timeslot and east
working timeslot, is
reported.
Possible Causes
Cause 1: The west working timeslot and the east working timeslot have different colors.
Procedure
Step 1 According to the alarm parameter, locate the MS link related to the alarm.
Step 2 Check the colors of the working timeslots and ensure that the west working timeslot and the east
working timeslot have the same color. For details, see Querying the TE Link Resources of the
OVPN Customers.
----End
Related Information
None.
10.5.6 CP_MSP_WPOVPN_MM
Description
The CP_MSP_WPOVPN_MM is an alarm indicating that the color of the working timeslot is
different from the color of the protection timeslot on the MSP network.
l This alarm occurs when the working timeslot and the protection timeslot on the MSP
network have different colors.

l This alarm is cleared when the working timeslot and the protection timeslot on the MSP
network have the same color.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
MSP ID Indicates the ID of the MSP group that reports the alarm, for example, 1.
MSP Type Indicates the protection type of the MSP network that reports the alarm. The value
is represented by hexadecimals. The meanings of different values for this
parameter are as follows:
l 0x10: ring MSP
l 0x20: linear MSP

When the CP_MSP_WPOVPN_MM alarm occurs, the system only prompts you to check
whether the resource allocation is reasonable.
Fault Symptom
NOTE
Table 10-38 lists the fault symptoms of the CP_MSP_WPOVPN_MM alarm.

Table 10-38 Symptoms of the CP_MSP_WPOVPN_MM alarm

Fault Symptom Cause
The alarm is Cause 1: The working timeslot and the protection timeslot on the MSP
reported, indicating network have different colors.
that the color of the
working timeslot is
different from the
color of the
protection timeslot
on the MSP network.
Possible Causes
Cause 1: The working timeslot and the protection timeslot on the MSP network have different
colors.
Procedure
Step 1 According to the alarm parameter, locate the MS link related to the alarm.
Step 2 Check the colors of the working and protection timeslots and ensure that the working timeslot
and the protection timeslot have the same color. For details, see Querying the TE Link Resources
of the OVPN Customers.
----End
Related Information
None.
10.5.7 CP_REROUTE_LOCK
Description
The CP_REROUTE_LOCK is an alarm indicating that the rerouting attribute of the service is
set to lock. That is, the interrupted service cannot be restored through rerouting.
l This alarm occurs when the rerouting attribute of the ASON service is set to lock.
l This alarm clears when the rerouting attribute of the ASON service is not set to lock.
Attribute
Minor Service alarm
Parameters


table.
Name Meaning
Src Indicates the Node ID of the source node of the service that reports the alarm, such as
1.1.1.1.
Dst Indicates the Node ID of the sink node of the service that reports the alarm, such as
1.1.1.2.
Index Indicates the index value of the service that reports the alarm, which is represented by
decimals.

When the CP_REROUTE_LOCK occurs, the services are not affected, but this LSP is not
allowed for rerouting. As a result, the services cannot be restored through rerouting after being
interrupted.
Fault Symptom
NOTE
Table 10-39 lists the fault symptoms of the CP_REROUTE_LOCK alarm.
Table 10-39 Symptoms of the CP_REROUTE_LOCK alarm
Fault Symptom Cause
The services are Cause 1: The rerouting attribute of the service is set to lock after a
interrupted or the fiber cut occurs.
service class is
lowered.
Possible Causes
The rerouting attribute of the service is set to lock after a fiber cut occurs.
Procedure
----End
Related Information
None.

10.5.8 CP_SRV_INT
Description
The CP_SRV_INT is an alarm indicating that all the LSPs corresponding to the services are
interrupted, and thus all the services are interrupted.
Attribute
Critical Service quality
Parameters
Name Meaning
ErrorCode Indicates the error code indicating the cause of the alarm, in hex.
l Ox01: The services are interrupted because of non-rerouting preemption.
l Ox02: The services are interrupted because of rerouting preemption.

When this alarm is generated, the services are interrupted. If the services have the rerouting
function and the ports for adding and dropping services are not faulty, the system restores the
services. When idle resources are available in the network, the services are successfully restored.
When the services are abnormally deleted, the system reconstructs the services.
Possible Causes
l On the service trail, a fiber is cut or a service board is faulty.
l No idle restoration resources are available in the network.
l The boards for adding and dropping services are off-service or faulty.
l The services are abnormally deleted.
l The services are interrupted because of rerouting preemption.
Procedure
Step 1 Based on the route of the interrupted LSP, check the alarms in the SDH link and path along the
route. Perform the traditional fault analysis.
Step 2 Recover the fault on the transport plane.
Step 3 Check whether the boards for adding and dropping services are off-service. In the case of the
TPS, check whether the protection board is off-service.
Step 4 Insert the boards for adding and dropping services to the original slots.
Step 5 If the services are abnormally deleted, recreate the services.
----End

Related Information
In the case of the OptiX GCP V100R005, this alarm is available. In the case of the OptiX GCP
V100R007, new error codes indicating the alarm causes are added.
10.5.9 CP_SER_NOT_OR
Description
The CP_SER_NOT_OR is an alarm indicating that the service is not on the original trail.
Attribute
Minor Service alarm
Parameters
table.
Name Meaning
Src Indicates the source node ID of this service.
Index Indicates the ID of the services, which is the only identity of the services created at
the same source node. This value is represented by decimals.

When the CP_SER_NOT_OR alarm is generated, the services are not affected.
Fault Symptom
NOTE
Table 10-40 lists the fault symptoms of the CP_SER_NOT_OR alarm.

Table 10-40 Symptoms of the CP_SER_NOT_OR alarm
Fault Symptom Cause
The current trail and Cause 1: The service is rerouted, optimized, or recreated.
the original trail of
the service are not
consistent.
Possible Causes
The service is rerouted, optimized, or recreated.
Procedure
l In the case of the non-revertive service, revert the service to the original trail through manual
operations.
For how to manually revert the service to the original trail, see 7.5.1 Reverting ASON
Trails.
NOTE
If the original trail is faulty or is occupied by other services, the ASON service cannot revert to the
original trail through manual operations.
l In the case of the revertive service, revert the service to the original trail through manual
operations or wait for the automatic reverting.
For how to manually revert the service to the original trail, see 7.5.1 Reverting ASON
Trails.
NOTE
If the original trail is faulty or is occupied by other services, the ASON service cannot revert to the
original trail through manual operations.
l In the case of the optimized service, set the actual trail to the original trail. Then, the alarm
can be cleared.
----End
Related Information
None.
10.5.10 CP_SER_SLA_DEG
Description
The CP_SER_SLA_DEG is an alarm indicating that the service level agreement (SLA) is
downgraded.
l This alarm occurs when the ASON protection level is downgraded.

l This alarm clears when the ASON protection level is recovered.

Attribute
Major Service alarm
Parameters
table.
Name Meaning
Src Indicates the source node ID of this service.
Index Indicates the ID of the services, which is the only identity of the services created at
one source node. This value is represented by decimals.
Error Indicates the cause of the SLA downgrade. This value is represented by hexadecimals
and has the following meanings:
l 0x0101: Only one LSP is valid for the diamond service.
l 0x0102: The active and standby LSP routes of the diamond service intersect.
l 0x0201: The route of the revertive silver service and the route of the shared mesh
restoration trail intersect.
l 0x0202: The shared mesh restoration trail of the revertive silver service is faulty.
l 0x0301: The gold service uses the unprotected resources of the TE link.
l 0x0302: The timeslots of the gold service on the same ring are inconsistent.
l 0x0303: The protection capability of the MS through which the gold service travels
decreases.
l 0x0401: The routes of the two associated services intersect.

When the CP_SER_SLA_DEG alarm occurs, the services are not affected but the SLA is
downgraded.
Fault Symptom
NOTE
Table 10-41 lists the fault symptoms of the CP_SER_SLA_DEG alarm.

Table 10-41 Symptoms of the CP_SER_SLA_DEG alarm

Fault Symptom Cause
After a fiber cut occurs Cause 1: Only one LSP is valid for the diamond service (non-
to the diamond service, permanent 1+1).
the rerouting rather than
the switching of the
service is performed.
After a fiber cut occurs Cause 2: The active and standby LSP routes of the diamond service
to the diamond service, intersect.
the active and standby
trails are rerouted.
The revertive silver Cause 3: The route of the revertive silver service and the route of
service cannot revert to the shared mesh restoration trail intersect.
the mesh restoration
trail after the
intermediate node
becomes faulty.
The revertive silver Cause 4: The shared mesh restoration trail of the revertive silver
service cannot revert to service is faulty.
the mesh restoration
trail after a fiber cut
occurs to the revertive
silver service.
After a fiber cut occurs Cause 5: The gold service uses the unprotected resources of the TE
to the gold service, the link.
rerouting rather than the
switching of the service
is performed.
When the source and Cause 6: The timeslots of the gold service on the same ring are
sink nodes of the gold inconsistent.
service are not isolated,
the gold service cannot
be switched to the
protection channel but
is rerouted after two
fiber cuts occur on the
working channel.
The gold service is in Cause 7: The protection capability of the MS through which the
the switching state, and gold service travels decreases (the MS is switched).
is rerouted when a
second fiber cut occurs
to the service.

Fault Symptom Cause
The two services are Cause 8: The routes of the two associated services intersect.
rerouted after the node
where the routes of the
associated silver
services intersect.
Possible Causes
The possible causes of the CP_SER_SLA_DEG alarm are as follows:
l Cause 1: Only one LSP is valid for the diamond service (non-permanent 1+1).
l Cause 2: The active and standby LSP routes of the diamond service intersect.
l Cause 3: The route of the revertive silver service and the route of the shared mesh restoration
trail intersect.
l Cause 4: The shared mesh restoration trail of the revertive silver service is faulty.
l Cause 5: The gold service uses the unprotected resources of the TE link.
l Cause 6: The timeslots of the gold service on the same ring are inconsistent.
l Cause 7: The protection capability of the MS through which the gold service travels
decreases (the MSP is performed).
l Cause 8: The routes of the two associated services intersect.
Procedure
l Cause 1: Only one LSP is valid for the diamond service (non-permanent 1+1).
Check the failed LSP. Specifically, check whether any link is faulty on the trail where the
LSP travels. For details, see 9.1 Handling Link Failures.
l Cause 2: The active and standby LSP routes of the diamond service intersect.
Check the actual route of the diamond service on the NMS. Determine whether the nodes
or links of the active and standby trails are overlapped. If yes, manually optimize the active
or standby LSP of the service so that they are not intersect. For details, see 7.5.2 Optimizing
an ASON Service.
l Cause 3: The route of the revertive silver service and the route of the shared mesh restoration
trail intersect.
If the route of the revertive silver service and the route of the shared mesh restoration trail
intersect, modify the shared mesh restoration trail so that the two routes do not intersect.
For details, see 7.4.6 Setting Shared MESH Restoration Trail.
l Cause 4: The shared mesh restoration trail of the revertive silver service is faulty.
If the shared mesh restoration trail of the revertive silver service is faulty, refresh or
reconfigure the shared mesh restoration trail. For details, see 7.4.6 Setting Shared MESH
Restoration Trail.
l Cause 5: The gold service uses the unprotected resources of the TE link.
If the gold service uses the unprotected resources of the TE link, optimize the gold service
or configure the MS for the TE link where the gold service travels. For details, see 7.5.2
Optimizing an ASON Service.

l Cause 6: The timeslots of the gold service on the same ring are inconsistent.
If the timeslots of the gold service on the same ring are inconsistent, optimize the gold
service so that the timeslots of the gold service on the same ring are consistent. For details,
see 7.5.2 Optimizing an ASON Service.
l Cause 7: The protection capability of the MS through which the gold service travels
decreases (the MS is switched).
If the protection capability of the MS through which the gold service travels decreases (the
MS is switched), rectify the MS fault so that the MS enters the normal state.
l Cause 8: The routes of the two associated services intersect.
If the routes of the two associated services intersect, optimize one of the services so that
the routes of the two associated services do not intersect. For details, see 7.5.2 Optimizing
an ASON Service.
----End
Related Information
None.
10.5.11 CP_TEL_DEG
Description
The CP_TEL_DEG is an alarm indicating the degrade of a TE link.
This alarm occurs when an abnormal degrade or LMP degrade occurs on the TE link. This alarm
clears when the degraded TE link is recovered.
Attribute
Parameters
table.
Name Meaning
Node Indicates the Node ID of the NE that reports the alarm. The value is represented
by decimals, for example, 1.1.1.1.
TE LinkID Indicates the link index of the TE link that is degraded. The value is represented
by hexadecimals, for example, 0x6c000001.

Name Meaning
Board Indicates the ID of the slot where the degraded TE link resides. The value is
represented by decimals.
Port Indicates the ID of the port where the degraded TE link resides. The value is

When the CP_TEL_DEG alarm occurs, the impacts of the system is affected as follows:
l The services on the link are interrupted.

l No new services can be created on the TE link.
l Other services cannot be rerouted to this TE link.
Fault Symptom
NOTE
Table 10-42 lists the fault symptoms of the CP_TEL_DEG alarm.
Table 10-42 Symptoms of the CP_TEL_DEG alarm
Fault Symptom Cause
The corresponding control Cause 1: LMP degrade. No control channel is available for the
channel is not available, TE link to perform the LMP check.
and the CP_CC_DOWN
alarm is reported.
The TE link is in the Cause 2: abnormal degrade.

DEGRADE state. In this
case, the ASON services on
this link are not affected but
no more service can be
created on this link.
Possible Causes
l Cause 1: LMP degrade. No control channel is available for the TE link to perform the LMP
check.
l Cause 2: An abnormal degrade occurs.
– Sub-cause 1: The software version of the line board is incorrect.
– Sub-cause 2: The line board is physically faulty.
– Sub-cause 3: The line board is offline.

– Sub-cause 4: The system control board is physically faulty.

– Sub-cause 5: The system control board is offline.
– Sub-cause 6: The cross-connect board is physically faulty.
– Sub-cause 7: The cross-connect board is offline.
Procedure
l Cause 1: LMP degrade. No control channel is available for the TE link to perform the LMP
check.
The control channel between the NEs is abnormal. Clear this alarm by referring to the
handling procedure of the 10.5.17 CPC_CC_DOWN alarm.
l Cause 2: abnormal degrade.
– Sub-cause 1: The software version of the line board is incorrect.
Check whether the software version of the line board is correct.
– Sub-cause 2: The line board is physically faulty.
Check whether the line board is physically faulty and whether the system reports the
HARD_BAD alarm related to the corresponding slot. If yes, replace the line board.
– Sub-cause 3: The line board is offline.
Check whether the line board is offline. If yes, reset the line board.
– Sub-cause 4: The system control board is physically faulty.
Check whether the system control board is physically faulty and whether the system
reports the HARD-BAD alarm related to the corresponding slot. If yes, replace the
system control board.
– Sub-cause 5: The system control board is offline.
Check whether the system control board is offline. If yes, reseat the system control
board.
– Sub-cause 6: The cross-connect board is physically faulty.
Check whether the cross-connect board is physically faulty and whether the system
reports the HARD-BAD alarm related to the corresponding slot. If yes, replace the cross-
connect board.
– Sub-cause 7: The cross-connect board is offline.
Check whether the cross-connect board is offline. If yes, reseat the cross-connect board.
----End
Related Information
None.
10.5.12 CP_TEL_DOWN
Description
The CP_TEL_DOWN alarm indicates the interruption of a TE link.
l This alarm occurs when a TE link becomes unavailable, or when a TE link fails to be
available after it is set up.

l This alarm is cleared after the TE link becomes available.
Attribute
Parameters
table.
Name Meaning
Node Indicates the Node ID of the NE that reports this alarm.
TE LinkID Indicates the link index of the TE link that becomes unavailable. The value is
represented by hexadecimals, for example, 0x6c000001.
Board Indicates the ID of the slot where the unavailable link resides. The value is
Port Indicates the number of the optical interface where the unavailable link resides.
The value is represented by decimals.
Error Indicates the cause of a link interruption. The value is represented by

hexadecimals, for example, 0x1. The meanings of different values for this
parameter are as follows:
l 0x3: The verification fails.

When the CP_TEL_DOWN alarm occurs on a TE link, this link is no longer used by ASON
services. The impacts of the CP_TEL_DOWN alarm on services are as follows:
l If the TE link interruption is caused by an alarm at the port, the services on this TE link are
rerouted.
l If the TE link interruption is caused by a link downgrade when the LMP protocol fails in
communication, the existing services are not affected.
Fault Symptom
NOTE

Table 10-43 lists the fault symptoms of the CP_TEL_DOWN alarm.
Table 10-43 Symptoms of the CP_TEL_DOWN alarm
Fault Symptom Cause
The TE link is in the Cause 1: The TE link verification fails.

DOWN state, and the
ASON services on the
TE link are not
rerouted or not
interrupted.
Possible Causes
The link is interrupted physically or logically, and thus it is no longer capable of transmitting
the data on the control plane and transport plane. The possible causes of the link interruption are
as follows:
l Cause 1: The TE link verification fails. (0x3)

– Sub-cause 1: All the available control channels between the NEs where the faulty TE
link resides are disabled.
– Sub-cause 2: The link management is disabled at the opposite end.
– Sub-cause 3: The link verification is disabled at one or both ends of the faulty TE link.
Procedure
l Cause 1: The TE link verification fails. (0x3)
– Sub-cause 1: All the available control channels between the NEs where the faulty TE
link resides are disabled.
Check the control channels of the NE where the link interruption alarm is reported.
Ensure that at least one control channel is available between this NE and its opposite
NE and the control channel is in the up state. For details, see 5.1.11 Synchronizing
Control Links Networkwide.
– Sub-cause 2: The link management is disabled at the opposite end.
Check and ensure that the TE link management on the opposite NE is in the up state.
For details, see 5.1.11 Synchronizing Control Links Networkwide.
– Sub-cause 3: The link verification is disabled at one or both ends of the faulty TE link.
Check and ensure that the LMP protocol is enabled at both ends of the TE link. For
details, see 7.1.2 Disabling/Enabling the LMP Protocol.
----End
Related Information
If the CP_TEL_DOWN alarm occurs, pay attention to the following points:

l If the cause of the TE link interruption changes during the period of the link interruption,
a performance event indicating the end of the link interruption should be reported before
an alarm indicating the new cause is reported.
l If the TE link interruption occurs when the TE link management is manually set to Down,
an alarm indicating the link interruption is no longer reported. If an alarm indicating the
link interruption is already reported, this alarm is cleared after the link management is
manually set to Down. In addition, a performance event indicating the end of the link
l To check whether the LMP verification fails, you should first exclude the other causes.
When the TE link fails to obtain the remote information, the board where the faulty TE link
resides is not offline, or no port alarms occur, you can infer that the TE link interruption is
caused by the failed LMP verification.
l If the TE link becomes normal and can obtain the remote information normally, the LMP
verification fails when the available control channel between NEs is disabled, the logical
board at the opposite end is deleted, the link management is disabled at the opposite end,
or the link verification is disabled at the opposite end. In this case, the LMP downgrade
alarm, rather than the alarm indicating the link interruption, is reported.
l The link interruption alarm caused by the failed LMP verification is transiently reported
after the factors that trigger the link interruption are eliminated. (These factors include
alarms reported at the optical interface, offline of the board, and link management being in
the down state.) This alarm is cleared until the LMP verification is successful and the remote
information is successfully obtained.
10.5.13 CP_TEL_MSP_MIS
Description
The CSPF module checks the MSP configuration at both ends of a link every five minutes. The
check items are as follows:
l Whether the numbers of timeslot segments are consistent
l Whether the indexes of timeslot segments are consistent
l Whether the number of timeslots contained in each timeslot segment is consistent
l Whether the MSP link type and MSP protection type are consistent
If any inconsistency exists and persists for 15 minutes, the CP_TEL_MSP_MIS alarm is
reported. When the MSP configuration at both ends of a link becomes consistent, the
CP_TEL_MSP_MIS alarm is cleared.
Attribute
Parameters

table.
Name Meaning
TE LinkID Indicates the link index of the TE link that reports the CP_TEL_MSP_MIS alarm.
The value is represented by hexadecimals, for example, 0x6c000001.
Board Indicates the ID of the slot connected to the TE link that reports the
CP_TEL_MSP_MIS alarm. The value is represented by decimals.
Port Indicates the number of the optical interface connected to the TE link that reports
the CP_TEL_MSP_MIS alarm. The value is represented by decimals.

When the CP_TEL_MSP_MIS alarm occurs, the services are not affected. The MSP resources
with inconsistent configurations cannot be used, and thus the services on the section of the MSP
fail to be switched.
Fault Symptom
NOTE
The following table lists the fault symptoms of the CP_TEL_MSP_MIS alarm.
Fault Cause
Symptom
The alarm l Cause 1: The numbers of MSP groups at both ends of the link are
indicating different.
inconsistent l Cause 2: The MSP at both ends of the link uses different timeslots.
MSP
configurations l Cause 3: The MSP at both ends of the link uses different types.
at both ends of
the link is
reported.
Possible Causes
The possible causes of the CP_TEL_MSP_MIS alarm are as follows:
l Cause 1: The numbers of MSP groups at both ends of the link are different.
l Cause 2: The MSP at both ends of the link uses different timeslots.
l Cause 3: The MSP at both ends of the link uses different types.

Procedure
l Cause 1: The numbers of MSP groups at both ends of the link are different.
Check whether the number of MSP groups at the local end is the same as the number of
MSP groups at the remote end. If not, reconfigure the MSP groups so that the numbers of
MSP groups at the local and at the remote end can be the same.
l Cause 2: The MSP at both ends of the link uses different timeslots.
Check whether the MSP at the local end and the MSP groups at the remote end use the
same timeslots. If not, reconfigure the MSP so that the MSP at the local end and at the
remote end uses the same timeslots.
l Cause 3: The MSP at both ends of the link uses different types.
Check whether the MSP at the local end and the MSP at the remote end uses the same type.
If not, reconfigure the MSP so that the MSP at the local end and at the remote end use the
same type.
----End
Related Information
The CP_TEL_MSP_MIS alarm is reported on NEs at both ends of the TE link.
10.5.14 CP_TEL_OVPN_MM
Description
When the CP_TEL_OVPN_MM alarm occurs, a certain timeslot is set to different colors at both
ends of a TE link, and the timeslot at neither end of the TE link is set to colorless.
Every five minutes, the system checks whether the colors of all the timeslots of all the TE links
at the local end are the same as the colors of all the timeslots of all the TE links at the opposite
end.
l If color inconsistency is found in three consecutive checks, the CP_TEL_OVPN_MM is

reported.
l The CP_TEL_OVPN_MM alarm is cleared after the colors of the timeslots at both ends
become the same.
Attribute
Parameters
table.

Name Meaning
Node Indicates the node ID of NE that reports the alarm, for example, 1.1.1.1.
TE LinkID Indicates the link index of the TE link where color configuration is found
inconsistent. The value is represented by hexadecimals, for example, 0x6c000001.
Path Indicates the number of the timeslot on the TE link with inconsistent color
configurations. The value is represented by hexadecimals.
Board Indicates the ID of the slot where the TE link with inconsistent color
configurations resides.
Port Indicates the number of the optical interface where the TE link with inconsistent
color configurations resides.
Color Indicates the color of the timeslot at the local end of the TE link with inconsistent
color configurations. The value is represented by hexadecimals, for example,
0x123.
RmtBoard Indicates the ID of the slot at the remote end of the TE link with inconsistent color
configurations.
RmtPort Indicates the number of the optical interface at the remote end of the TE link with
inconsistent color configurations.
RmtColor Indicates the color of the timeslot at the remote end of the TE link with inconsistent
color configurations. The value is a hexadecimal number, for example, 0x123.

When the CP_TEL_OVPN_MM alarm occurs, the existing services are not affected. The
timeslots with different colors on the TE link become unavailable, and thus rerouting success
rate decreases.
Fault Symptom
NOTE
Table 10-44 lists the fault symptoms of the CP_TEL_OVPN_MM alarm.

Table 10-44 Symptoms of the CP_TEL_OVPN_MM alarm
Fault Symptom Cause
When a timeslot with Cause 1: The colors of timeslots at both ends of a TE link are different.
inconsistent color
configurations at
both ends of a TE link
is used to create
services, the NMS
returns an error
message indicating
that the specified
resource is
unavailable.
Possible Causes
At least one timeslot is set to different colors on the NEs at both ends of a TE link, and the
timeslot at neither end of the TE link is set to colorless.
Procedure
----End
Related Information
The alarm indicating that a certain timeslot has different colors at both ends is reported on NEs
at both ends of a TE link.
10.5.15 CP_TEL_PATH_MIS
Description
The CSPF module checks the timeslots of each link every five minutes. If the CSPF module
finds that a certain timeslot is in different states at both ends of a link and the inconsistency
persists for more than 15 minutes, it instructs the SC module to clear the inconsistency. If the
inconsistency fails to be cleared, the CP_TEL_PATH_MIS alarm is reported in the next
detection period (that is, 20 minutes after the CSPF module detects the inconsistency).
If the CSPF module finds that the timeslot inconsistency between both ends is cleared or another
timeslot inconsistency situation occurs, the alarm indicating the previous timeslot inconsistency
situation is cleared.
Attribute

Parameters
table.
Name Meaning
TE LinkID Indicates the link index of the TE link that reports the
CP_TEL_PATH_MIS alarm. The value is represented by hexadecimals,
for example, 0x6c000001.
Board Indicates the ID of the slot connected to the TE link that reports the
CP_TEL_PATH_MIS alarm. The value is represented by decimals.
Port Indicates the number of the optical interface connected to the TE link that
reports the CP_TEL_PATH_MIS alarm. The value is represented by
decimals.

Name Meaning
Local path state Indicates the usage of the inconsistent timeslots at the local end on the TE
link that reports the CP_TEL_PATH_MIS alarm. The value is represented
by decimals. The meanings of different values for this parameter are as
follows:
l 0: The timeslot is idle.
l 1: The timeslot is used by the ASON service.
l 2: The timeslot is reserved for the ASON service.
l 3: The remote end of the timeslot is unavailable.
l 4: The timeslot is used by the iron service.
l 5: The state is set when the iron service processes the RESERVE
message.
l 6: The resource of the iron service is preempted.
l 7: The timeslot is reserved for the ASON service.
l 8: The timeslot is used by the ASON service and the timeslot is used
by the traditional service.
l 9: The timeslot is used by the iron service and the timeslot is used by
the traditional service.
l 10: The timeslot is used by the traditional service.
l 11: The resource of the iron service is preempted and the timeslot is
used by the traditional service.
l 12: The timeslot is used by the ASON service and the timeslot is
reserved by the ASON service.
l 13: The timeslot is used by the ASON service, the timeslot is reserved
for the ASON service, and the timeslot is used by the traditional service.
l 14: The timeslot is reserved for the ASON service and the timeslot is
used by the traditional service.
l 15: The egress timeslot is idle but the ingress timeslot is not idle.
l 16: Indicates a temporary state.
l 17: The timeslot is used by the ASON service, the timeslot is used by
the traditional service, and the timeslot is inconsistent.
l 18: The resource of the iron service is preempted, the timeslot is used
by the traditional service, and the timeslot is inconsistent.
l 19: The timeslot is used by the lower-priority service.
l 20: The timeslot is reserved for the lower-priority service.
l 21: The timeslot is used by the lower-priority service (FA) and the
timeslot is used by the traditional service.
l 22: The timeslot is reserved for the lower-priority service (FA) and the
timeslot is used by the traditional service.
l 23: The timeslot is used by the lower-priority service and the timeslot
is reserved for the ASON service.
l 24: The timeslot is reserved for the lower-priority service and the
timeslot is reserved for the ASON service.

Name Meaning
l 25: The timeslot is used by the lower-priority service by preempting
the resource of the iron service.
l 26: The timeslot is reserved for the lower-priority service by preempting
the resource of the iron service.
l 27: The timeslot is used by the lower-priority service (FA) by
preempting the resource of the iron service and the timeslot is used by
l 28: The timeslot is reserved for the lower-priority service (FA) by
preempting the resource of the iron service and the timeslot is used by
l 29: The timeslot is used by the lower-priority service, the timeslot is
used by the preset restoration trail, and the timeslot is used by the NE
software.
l 30: The timeslot is reserved for the lower-priority service, the timeslot
is used by the preset restoration trail, and the timeslot is used by the NE
software.
l 31: The transoceanic MSP protection timeslot is preempted.
Remote path state Indicates the usage of the inconsistent timeslots at the remote end on the
TE link that reports the CP_TEL_PATH_MIS alarm. The value is
represented by decimals. The value is an enumerated one. For meanings
of different values for this parameter, see the description of the Local path
state parameter.

When the CP_TEL_PATH_MIS alarm occurs, services on the TE link are not affected. Timeslots
of inconsistent path status on the TE link are unavailable, and success rate of rerouting decreases.
Fault Symptom
NOTE
Table 10-45 lists the fault symptoms of the CP_TEL_PATH_MIS alarm.

Table 10-45 Symptoms of the CP_TEL_PATH_MIS alarm
Fault Symptom Cause
The alarm l Cause 1: The resource reservation is incomplete. That is, timeslots
indicating are reserved at one end but are idle at the other end.
inconsistent l Cause 2: The resource configuration or release is incomplete. That
timeslots at both is, timeslots are used at one end, but are reserved or idle at the other
ends of the link is end.
reported.
l Cause 3: The service migration is incomplete. That is, permanent
services are configured at one end, and ASON services are
configured at the other end.
Possible Causes
The possible causes of the CP_TEL_PATH_MIS alarm are as follows:
l Cause 1: The resource reservation is incomplete. That is, timeslots are reserved at one end
but are idle at the other end.
l Cause 2: The resource configuration or release is incomplete. That is , timeslots are used
at one end, but are reserved or idle at the other end.
l Cause 3: The service migration is incomplete. That is, permanent services are configured
at one end, and ASON services are configured at the other end.
Procedure
l Cause 1: The ASON resource reservation is incomplete. That is, timeslots are reserved at
one end but are idle (not reserved) at the other end.
Check whether the path resource reservation at both ends of the TE link is consistent. If
not, reserve the resources at the end where timeslots are idle, or cancel the reservation at
the end where timeslots are reserved. For details, see 7.2.5 Setting Resource
Reservation.
l Cause 2: Permanent cross-connections may be left when the resource configuration or
release is incomplete; that is, timeslots are used at one end, but are reserved or idle at the
other end.
Check whether the timeslot usage status of both ends of the TE link is consistent. If the
timeslots at one end are idle or reserved and the permanent cross-connections at the other
end are used, delete the permanent cross-connections at the end, or create cross-connections
at the end where timeslots are idle or reserved.
l Cause 3: Unidirectional cross-connections may be left when the service migration is
incomplete; that is, permanent services are configured at one end, and ASON services are
configured at the other end.
No manual operations are required. Approximate 15 minutes later, the ASON software
automatically migrates from ASON cross-connections to SDH cross-connections at the
local end. Then, the alarm is cleared.
----End

Related Information
In the case of inconsistent timeslots, if the timeslot at the local end is idle and the timeslot at the
remote end is not idle, the CP_TEL_PATH_MIS alarm is reported at the remote end. Otherwise,
this alarm is reported at the local and remote ends of the TE link.
10.5.16 CP_TEL_EXHAUST
Description
The CP_TEL_EXHAUST alarm indicates that the resource usage of the TE link exceeds the
specified threshold.
When the timeslot status of the TE link changes, the possible situations are as follows:
l If the resource usage rate of the TE link is equal to or greater than the specified threshold,
the CP_TEL_EXHAUST alarm is reported.
l If the resource usage rate is smaller than the specified threshold, the CP_TEL_EXHAUST
alarm is cleared.
Attribute
Minor Communication alarm
Parameters
table.
Name Meaning
Node Indicates the node ID of NE that reports the alarm, for example, 1.1.1.1.
TE LinkID Indicates the link index of the TE link on which the resource usage rate exceeds
the specified threshold. The value is represented by hexadecimals, for example,
0x6c000001.
Board Indicates the ID of the slot connected to the TE link on which the resource usage
rate exceeds the specified threshold resides. The value is represented by decimals.
Port Indicates the number of the optical interface connected to the TE link on which
the resource usage rate exceeds the specified threshold resides. The value is


When the CP_TEL_EXHAUST alarm occurs, the existing services are not affected. The
survivability of the services, however, are affected.
Fault Symptom
NOTE
Table 10-46 lists the fault symptoms of the CP_TEL_EXHAUST alarm.
Table 10-46 Symptoms of the CP_TEL_EXHAUST alarm
Fault Cause
Symptom
The alarm Cause 1: The resource usage rate of the TE link exceeds the specified
indicating threshold when services use a large number of resources or resources are
threshold- manually reserved.
crossing of the
resource usage
rate is
reported.
Possible Causes
The resource usage rate of the TE link exceeds the specified threshold when the services use a
large number of resources or resources are manually reserved.
Procedure
Step 1 Evaluate the resource usage rate. If an increased resource usage threshold does not lower the
survivability of the existing services on the network to a great extent, increase the resource usage
threshold.
Step 2 If the resource usage threshold cannot be increased, replan the existing services or network
resources. For details, see 2 Planning the OTN ASON.
----End
Related Information
None.
10.5.17 CPC_CC_DOWN
Description
The CP_CC_DOWN alarm indicates that the control channel is interrupted.

Attribute
Parameters
table.
Name Meaning
router_id Indicates the node ID of the NE on the link. The value is in dotted decimal notation,
ccid Indicates the control link index and the value is in hexadecimal notation.

The service is not affected. If all control channels between two nodes are interrupted, however,
the TE link is degraded.
Fault Symptom
NOTE
Table 10-47 lists the fault symptom for the CPC_CC_DOWN alarm.
Table 10-47 Fault symptom for the CPC_CC_DOWN alarm
Fault Symptom Cause
The opposite node reports the Cause 5: The ID of the opposite node conflicts
CPC_NODE_ID_CONFLICT alarm. with the ID of other nodes.
Possible Causes
The possible causes of the CPC_CC_DOWN alarm are as follows:


Procedure
1. Determine whether the opposite node needs to be upgraded to an ASON node
according to the networking requirement. If the upgrade is required, upgrade the
traditional node to an ASON node.
2. If the opposite node does not need to be upgraded to an ASON node, the user can
disable the LMP control protocol of the optical path between the ASON NE and non-
ASON NE, or suppress the alarm. For the operation steps, see Configuring the LMP
Protocol and Management of the Suppression Status of Alarms on the Control
Plane
1. Enable the opposite control channel.
1. For details, see the procedure for handling the CPC_NODE_ID_CONFLICT alarm.
----End
Related Information
None.
10.5.18 CPC_NODE_ID_CONFLICT
Description
The CPC_NODE_ID_CONFLICT alarm indicates a node ID conflict.
Attribute
Critical QoS
Parameters


table.
Name Meaning
NA NA

The existing services may be affected, the label switched path (LSP) may be abnormal, and the
service restoration mechanism may be affected.
Fault Symptom
NOTE
Table 10-48 lists the fault symptom for the CPC_NODE_ID_CONFLICT alarm.
Table 10-48 Fault symptom for the CPC_NODE_ID_CONFLICT alarm

Fault Symptom Cause
The CPC_NODE_ID_CONFLICT alarm is Cause 1: Two or more nodes have the same
reported. node ID.
Possible Causes
The cause of the CPC_NODE_ID_CONFLICT alarm is as follows:
Procedure
1. Change the node ID of the NE that reports this alarm so that the node ID of this NE
is different from the node IDs of other NEs in the ASON domain.
2. On the U2000, check the entire network for the node ID conflict, and then a list of
nodes with repeated IDs are displayed.
3. Change the IDs of the nodes in the list according to the design document so that the
node IDs are unique.
NOTE
For how to set the node ID, see Setting the Node ID.
----End
Related Information
None.

10.5.19 CPC_NODE_ID_ERR
Description
The CPC_NODE_ID_ERR alarm indicates a node ID error.
When the NE is started, the ASON function cannot be enabled normally because the internal
processing of the node ID setting is abnormal. As a result, this alarm is generated. After the error
is corrected, the ASON function can be enabled if there is no other problems. The alarm is
cleared, and an event indicating the end of this alarm is reported.
Attribute
Critical Process alarm
Parameters
table.
Name Meaning
NA NA

The ASON function cannot be enabled.
Fault Symptom
NOTE
Table 10-49 lists the fault symptom for the CPC_NODE_ID_ERR alarm.
Table 10-49 Fault symptom for the CPC_NODE_ID_ERR alarm

Fault Symptom Cause
The ASON function cannot be enabled. Cause 1: The internal processing of the node
ID setting is abnormal.
Possible Causes
The cause of the CPC_NODE_ID_ERR alarm is as follows:

Procedure
1. Check whether the node ID is set.
2. Check whether the preset node ID is the same as the one specified in the design
document. Set the node ID again according to the design document.
NOTE
Refer to Setting the Node ID for the configuration process.
----End
Related Information
None.
10.5.20 CPC_OSPF_AUTH_ERR
Description
The CP_OSPF_AUTH_ERR alarm indicates an authentication error of the OSPF neighbor.
Attribute
Major QoS
Parameters
table.
Name Meaning
notation, for example 1.1.1.2.
notation.
board Indicates the board at the local end on the link and the value is in decimal
notation.

Name Meaning
decimal notation.

Fault Symptom
NOTE
Table 10-50 lists the fault symptom for the CPC_OSPF_AUTH_ERR alarm.
Table 10-50 Fault symptom for the CPC_OSPF_AUTH_ERR alarm
Fault Symptom Cause
The CPC_OSPF_AUTH_ERR alarm is Cause 1: The OSPF authentication modes or

reported. keys at two ends of the control link are
inconsistent.
Possible Causes
The cause of the CPC_OSPF_AUTH_ERR alarm is as follows:
inconsistent.
Procedure
inconsistent.
1. Make the authentication modes and keys at the two ends consistent. Refer to
Encrypting the OSPF Protocol.
----End
Related Information
None.
10.5.21 CPC_OSPF_CL_DOWN
Description
The CPC_OSPF_CL_DOWN alarm indicates that the OSPF control link is interrupted.

Attribute
Major QoS
Parameters
table.
Name Meaning
Nodeid Indicates the node ID of the NE on the link. The value is in dotted decimal
notation.
decimal notation.

The service signals are not affected, but the IP reachability of the signaling packets is affected.
Fault Symptom
NOTE
Table 10-51 lists the fault symptoms for the CPC_OSPF_CL_DOWN alarm.
Table 10-51 Fault symptom for the CPC_OSPF_CL_DOWN alarm
Fault Symptom Cause
The alarm indicating a fiber cut is reported. Cause 1: A fiber cut occurs.
Possible Causes

Procedure
1. Check and repair the fiber.
----End
Related Information
None.
10.5.22 CPC_OSPF_NB_DOWN
Description
The CPC_OSPF_NB_DOWN alarm indicates that the OSPF communication between
neighboring NEs is interrupted.
Attribute
Major QoS
Parameters
table.
Name Meaning
notation.
board Indicates the slot at the local end on the link and the value is in decimal notation.
decimal notation.


Fault Symptom
NOTE
Table 10-52 lists the fault symptom for the CPC_OSPF_NB_DOWN alarm.
Table 10-52 Fault symptom for the CPC_OSPF_NB_DOWN alarm

Fault Symptom Cause
The CPC_OSPF_NB_DOWN alarm is l Cause 1: The OSPF protocol is not

reported. enabled on the control link of the opposite
node.
l Cause 2: The ASON software of the
opposite node is not running.
l Cause 4: The OSPF authentication
configuration is incorrect.
Possible Causes
Procedure
1. Enable the OSPF protocol on the opposite control link. see the procedure for handling
the Configuring the OSPF Protocol.
1. For details, see the procedure for handling the CPC_OSPF_CL_DOWM alarm.
1. For details, see the procedure for handling the CPC_OSPF_AUTH_ERR alarm.
----End
Related Information
None.

10.5.23 CPC_RSVP_AUTH_ERR
Description
The CPC_RSVP_AUTH_ERR alarm indicates an authentication error of the RSVP neighboring
nodes.
This alarm is generated when the adjacent NEs (also called neighboring NEs) that the LSP
traverses fails to pass the authentication.
The alarm is cleared when the neighboring NEs pass the authentication successfully. In this case,
an event indicating the end of this alarm is reported. In addition, the alarm is not reported when
the neighboring NE does not exist.
Attribute
Parameters
table.
Name Meaning
Remote Node Indicates the node ID of the neighboring NE. The value is in dotted decimal
notation, such as 1.1.1.2.

The service signals are not affected. The signaling between the two adjacent NEs, however, is
affected, and certain operations cannot be performed. For example, creating a service between
the two NEs will time out, and rerouting of the services that traverse the two NEs will also fail
due to timeout.
Fault Symptom
NOTE
Table 10-53 lists the fault symptom for the CPC_RSVP_AUTH_ERR alarm.

Table 10-53 Fault symptom for the CPC_RSVP_AUTH_ERR alarm
Fault Symptom Cause
Creating a service or rerouting times out. Cause 1: The authentication modes or codes
of the two RSVP neighboring nodes are
inconsistent.
Possible Causes
The possible cause of the CPC_RSVP_AUTH_ERR alarm is as follows:
inconsistent.
Procedure
inconsistent.
1. Check whether the RSVP neighboring nodes are configured to be in different
authentication modes according to the network isolation requirement. If so, there is
no need to handle the alarm. Instead, suppress the alarm directly. Refer
toManagement of the Suppression Status of Alarms on the Control Plane.
2. Make two neighboring nodes have the same RSVP authentication mode and code.
Refer to Encrypting RSVP.
----End
Related Information
None.
10.5.24 CPC_RSVP_NB_DOWN
Description
The CPC_RSVP_NB_DOWN alarm indicates that the communication between neighboring
NEs fails, and the RSVP message from the neighboring NE cannot be received.
The alarm is cleared when the RSVP communication between the neighboring NEs is restored,
and an event indicating the end of this alarm is reported. In addition, the alarm is not reported
when the neighboring NE does not exist.
Attribute

Parameters
table.
Name Meaning
Remote Node Indicates the node ID of the neighboring NE. The value is in decimal dotted

The service signals are not affected, but the normal signaling process of the service is affected.
In this case, certain operations cannot be performed. For example, service optimization or
rerouting on the two NEs fails.
Fault Symptom
NOTE
Table 10-54 lists the fault symptoms for the CPC_RSVP_NB_DOWN alarm.
Table 10-54 Fault symptom for the CPC_RSVP_NB_DOWN alarm
Fault Symptom Cause
The CPC_OSPF_CL_DOWN alarm is Cause 1: The control link is interrupted.

generated, indicating that control link is
interrupted.
The NEs are unreachable to the U2000. Cause 2: The node is reset.
The CPC_RSVP_AUTH_ERR alarm is Cause 3: The configuration of the RSVP

generated, indicating that the RSVP neighboring authentication is incorrect.
neighboring authentication fails.
Possible Causes


Procedure
1. In this case, it is unnecessary to handle the alarm, because the alarm is cleared after
the NE is started.
1. For details, see the procedure for handling the CPC_RSVP_AUTH_ERR alarm.
----End
Related Information
None.

ASON User Guide A Glossary
A Glossary
A
AC See alternating current
access control list A list of entities, together with their access rights, which are authorized to have access
to a resource.
ACK See acknowledgement
acknowledgement A response sent by a receiver to indicate successful reception of information.
Acknowledgements may be implemented at any level including the physical level (using
voltage on one or more wires to coordinate transfer), at the link level (to indicate
successful transmission across a single hardware link), or at higher levels.
ACL See access control list
add/drop multiplexer Network elements that provide access to all or some subset of the constituent signals
contained within an STM-N signal. The constituent signals are added to (inserted), and/
or dropped from (extracted) the STM-N signal as it passed through the ADM.
Add/drop wavelength Add/drop wavelength refers to the wavelength that carries the add/drop services in the
OADM equipment.
Address Resolution Address Resolution Protocol (ARP) is an Internet Protocol used to map IP addresses to
Protocol MAC addresses. It allows hosts and routers to determine the link layer addresses through
ARP requests and ARP responses. The address resolution is a process in which the host
converts the target IP address into a target MAC address before transmitting a frame.
The basic function of the ARP is to query the MAC address of the target equipment
through its IP address.
ADM See add/drop multiplexer
administrative unit The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and an AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
Administrator A user who has authority to access all the Management Domains of the EMLCore
product. He has access to the whole network and to all the management functionalities.
ADSL See asymmetric digital subscriber line
AGC See automatic gain control

AID access identifier

AIS See alarm indication signal
alarm A message reported when a fault is detected by a device or by the network management
system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
alarm cable The cable for generation of visual or audio alarms.
alarm cascading The shunt-wound output of the alarm signals of several subracks or cabinets.
alarm cause A single disturbance or fault may lead to the detection of multiple defects. A fault cause
is the result of a correlation process which is intended to identify the defect that is
representative of the disturbance or fault that is causing the problem.
alarm indication On the cabinet of an NE, there are four indicators in different colors indicating the current
status of the NE. When the green indicator is on, it indicates that the NE is powered on.
When the red indicator is on, it indicates that a critical alarm is generated. When the
orange indicator is on, it indicates that a major alarm is generated. When the yellow
indicator is on, it indicates that a minor alarm is generated. The ALM alarm indicator on
the front panel of a board indicates the current status of the board.
alarm indication signal A code sent downstream in a digital network as an indication that an upstream failure
has been detected and alarmed. It is associated with multiple transport layers.
alarm mask On the host, an alarm management method through which users can set conditions for
the system to discard (not to save, display, or query for) the alarm information meeting
the conditions.
alarm severity The significance of a change in system performance or events. According to ITU-T
recommendations, an alarm can have one of the following severities: Critical, Major,
Minor, Warning.
alarm suppression A function used not to monitor alarms for a specific object, which may be the
networkwide equipment, a specific NE, a specific board and even a specific function
module of a specific board.
alarm type Classification of alarms with different attributes. There are six alarm types as following:
Communication: alarm indication related with information transfer. Processing: alarm
indication related with software or information processing Equipment: alarm indication
related with equipment fault Service: alarm indication related with QoS of the equipment
Environment: alarm related with the environment where the equipment resides, usually
generated by a sensor Security: alarm indication related with security
ALC See automatic level control
ALC link A piece of end-to-end configuration information, which exists in the equipment (single
station) as an ALC link node. Through the ALC function of each node, it fulfils optical
power control on the line that contains the link.
ALC node The ALC functional unit. It corresponds to the NE in a network. The power detect unit,
variable optical attenuator unit, and supervisory channel unit at the ALC node work
together to achieve the ALC function.
ALS See automatic laser shutdown
alternating current Electric current that reverses its direction of flow (polarity) periodically according to a
frequency measured in hertz, or cycles per second.

American National An organization that defines U.S standards for the information processing industry.
Standard Institute American National Standard Institute (ANSI) participates in defining network protocol
standards.
American Standard American Standard Code for Information Interchange - the standard system for
Code for Information representing letters and symbols. Each letter or symbol is assigned a unique number
Interchange between 0 and 127.
ANSI See American National Standard Institute
antistatic floor A floor that can quickly release the static electricity of the object contacting it to prevent
accumulated static electricity
APD See avalanche photodiode
APE automatic power equilibrium
APID access point identifier
application-specific A special type of chip that starts out as a nonspecific collection of logic gates. Late in
integrated circuit the manufacturing process, a layer is added to connect the gates for a specific function.
By changing the pattern of connections, the manufacturer can make the chip suitable for
many needs.
APS See automatic protection switching
ARP See Address Resolution Protocol
arrayed waveguide A device, built with silicon planar lightwave circuits (PLC), that allows multiple
grating wavelengths to be combined and separated in a dense wavelength-division multiplexing
(DWDM) system.
ASCII See American Standard Code for Information Interchange
ASE amplified spontaneous emission
ASIC See application-specific integrated circuit
ASON See automatically switched optical network
asymmetric digital A technology for transmitting digital information at a high bandwidth on existing phone
subscriber line lines to homes and businesses. Unlike regular dialup phone service, ADSL provides
continuously-available, "always on" connection. ADSL is asymmetric in that it uses most
of the channel to transmit downstream to the user and only a small part to receive
information from the user. ADSL simultaneously accommodates analog (voice)
information on the same line. ADSL is generally offered at downstream data rates from
512 Kbps to about 6 Mbps.
Asynchronous A protocol for the transmission of a variety of digital signals using uniform 53 byte cells.
Transfer Mode A transfer mode in which the information is organized into cells; it is asynchronous in
the sense that the recurrence of cells depends on the required or instantaneous bit rate.
Statistical and deterministic values may also be used to qualify the transfer mode.
ATAG autonomously generated correlation tag
ATM See Asynchronous Transfer Mode
AU See administrative unit
auto-negotiation An optional function of the IEEE 802.3u Fast Ethernet standard that enables devices to
automatically exchange information over a link about speed and duplex abilities.

automatic gain control A process or means by which gain is automatically adjusted in a specified manner as a
function of a specified parameter, such as received signal level.
automatic laser A technique (procedure) to automatically shutdown the output power of laser transmitters
shutdown and optical amplifiers to avoid exposure to hazardous levels.
automatic level control A well-known application in communication systems with a given input signal
conditioned to produce an output signal as possible, while supporting a wide gain range
and controlled gain-reduction and gain recovery characteristics.
automatic protection Capability of a transmission system to detect a failure on a working facility and to switch
switching to a standby facility to recover the traffic.
automatically switched A network which is based on technology enabling the automatic delivery of transport
optical network services. Specifically, an ASON can deliver not only leased-line connections but also
other transport services such as soft-permanent and switched optical connections.
avalanche photodiode A semiconductor photodetector with integral detection and amplification stages.
Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher voltages
than other semiconductor electronics.
AWG See arrayed waveguide grating
B
background block The ratio of background block errors (BBE) to total blocks in available time during a
error ratio fixed measurement interval. The count of total blocks excludes all blocks during SESs.
backup A periodic operation performed on the data stored in the database for the purposes of
database recovery in case that the database is faulty. The backup also refers to data
synchronization between active and standby boards.
bandwidth A range of transmission frequencies that a transmission line or channel can carry in a
network. In fact, it is the difference between the highest and lowest frequencies the
transmission line or channel. The greater the bandwidth, the faster the data transfer rate.
BAS See broadband access server
basic input/output A firmware stored in the computer mainboard. It contains basic input/output control
system programs, power-on self test (POST) programs, bootstraps, and system setting
information. The BIOS provides hardware setting and control functions for the computer.
bayonet-neill- A connector used for connecting two coaxial cables.
concelman
BBE background block error
BBER See background block error ratio
BC See boundary clock
BDI Backward Defect Indication
BEI backward error indication
BER See bit error rate
BIAE backward incoming alignment error

bill of material Listing of all the subassemblies, parts and raw materials that go into the parent assembly.
It shows the quantity of each raw material required to make the assembly. There are a
variety of display formats for BOMS, including single level, indented, modular/
planning, transient, matrix and costed BOMs [APICs, CMSG].
BIOS See basic input/output system
BIP See bit-interleaved parity
BIP-8 See bit interleaved parity order 8
bit error An incompatibility between a bit in a transmitted digital signal and the corresponding
bit in the received digital signal.
bit error rate Ratio of received bits that contain errors. BER is an important index used to measure the
communications quality of a network.
bit interleaved parity A frame is divided into several blocks with 8 bits (one byte)in a parity unit. Then arrange
order 8 the blocks in matrix. Compute the number of "1" over each column. Then fill a 1 in the
corresponding bit for the result if the number is odd, otherwise fill a 0.
bit-interleaved parity A method of error monitoring. With even parity an X-bit code is generated by the
transmitting equipment over a specified portion of the signal in such a manner that the
first bit of the code provides even parity over the first bit of all X-bit sequences in the
covered portion of the signal, the second bit provides even parity over the second bit of
all X-bit sequences within the specified portion, etc. Even parity is generated by setting
the BIP-X bits so that there is an even number of 1s in each monitored partition of the
signal. A monitored partition comprises all bits which are in the same bit position within
the X-bit sequences in the covered portion of the signal. The covered portion includes
the BIP-X.
BITS See building integrated timing supply
BMC best master clock
BNC See bayonet-neill-concelman
BOM See bill of material
boundary clock A clock with a clock port for each of two or more distinct PTP communication paths.
BPDU See bridge protocol data unit
BPS board-level protection switching
bridge protocol data The data messages that are exchanged across the switches within an extended LAN that
unit uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
bridging The action of transmitting identical traffic on the working and protection channels
simultaneously.
broadband access A server providing features as user access, connection management, address allocation
server and authentication, authorization and accounting. It also works as a router featuring
effective route management, high forwarding performance and abundant services.
broadcast A means of delivering information to all members in a network. The broadcast range is
determined by the broadcast address.

broadcast service The unidirectional services from one service source to multiple service sinks.
building integrated In the situation of multiple synchronous nodes or communication devices, one can use
timing supply a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
BWS Backbone WDM System
cable tie The tape used to bind the cables.

capex See capital expenditure
capital expenditure Capital expenditures (CAPEX or capex) are expenditures creating future benefits. A
capital expenditure is incurred when a business spends money either to buy fixed assets
or to add to the value of an existing fixed asset with a useful life that extends beyond the
taxable year. Capex are used by a company to acquire or upgrade physical assets such
as equipment, property, or industrial buildings.
CAR See committed access rate
CBS See committed burst size
CC See connectivity check
CCI connection control interface
CCM See continuity check message
CD chromatic dispersion
CDMA See Code Division Multiple Access
CE See customer edge
CENELEC See European Committee for Electrotechnical Standardization
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
centralized alarm The system that gathers all the information about alarms into a certain terminal console.
system
CF See compact flash
CGMP Cisco Group Management Protocol
channel A telecommunication path of a specific capacity and/or at a specific speed between two
or more locations in a network. The channel can be established through wire, radio
(microwave), fiber or a combination of the three. The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s),
and Tb/s (1012 bit/s).
channel spacing The center-to-center difference in frequency or wavelength between adjacent channels
in a WDM device.
CIR See committed information rate

CIST Common and Internal Spanning Tree

CLEI common language equipment identification
CLNP connectionless network protocol
CLNS connectionless network service
clock synchronization Also called frequency synchronization, clock synchronization means that the signal
frequency traces the reference frequency, but the start point need not be consistent.
clock synchronization A type of high-decision clock defined by the IEEE 1588 V2 standard. The IEEE 1588
compliant with V2 standard specifies the precision time protocol (PTP) in a measurement and control
precision time protocol system. The PTP protocol ensures clock synchronization precise to sub-microseconds.
clock tracing The method to keep the time on each node being synchronized with a clock source in a
network.
CM See configuration management
CMEP connection monitoring end point
CMI coded mark inversion
coarse wavelength A signal transmission technology that multiplexes widely-spaced optical channels into
division multiplexing the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM
does not support optical amplifiers and is applied in short-distance chain networking.
Code Division Multiple A communication scheme that forms different code sequences by using the frequency
Access expansion technology. In this case, subscribers of different addresses can use different
code sequences for multi-address connection.
committed access rate A traffic control method that uses a set of rate limits to be applied to a router interface.
CAR is a configurable method by which incoming and outgoing packets can be classified
into QoS (Quality of Service) groups, and by which the input or output transmission rate
can be defined.
committed burst size committed burst size. A parameter used to define the capacity of token bucket C, that is,
the maximum burst IP packet size when the information is transferred at the committed
information rate. This parameter must be larger than 0. It is recommended that this
parameter should be not less than the maximum length of the IP packet that might be
forwarded.
committed information The rate at which a frame relay network agrees to transfer information in normal
rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to
the leaky bucket.
Common Object A specification developed by the Object Management Group in 1992 in which pieces of
Request Broker programs (objects) communicate with other objects in other programs, even if the two
Architecture programs are written in different programming languages and are running on different
platforms. A program makes its request for objects through an object request broker, or
ORB, and thus does not need to know the structure of the program from which the object
comes. CORBA is designed to work in object-oriented environments. See also IIOP,
object (definition 2), Object Management Group, object-oriented.
compact flash Compact flash (CF) was originally developed as a type of data storage device used in
portable electronic devices. For storage, CompactFlash typically uses flash memory in
a standardized enclosure.
concatenation A process that combines multiple virtual containers. The combined capacities can be
used a single capacity. The concatenation also keeps the integrity of bit sequence.

Configuration Data A command file defining hardware configurations of an NE. With this file, an NE can
collaborate with other Nes in an entire network. Thus, configuration data is the key factor
for normal running of an entire network.
configuration 1. A network management function defined by the International Standards Organization
management (ISO). It involves installing, reinitializing & modifying hardware & software.
2. Configuration Management (CM) is a system for collecting the configuration
information of all nodes in the network.
configure To set the basic parameters of an operation object.

congestion An extra intra-network or inter-network traffic resulting in decreasing network service
efficiency.
connecting plate A metallic plate which is used to combine two cabinets.
connection point A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
connectivity check Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by
each MEP transmitting a Continuity Check Message (CCM) periodically.
continuity check CCM is used to detect the link status.
message
convergence 1. A process in which multiple channels of low-rate signals are multiplexed into one or
several channels of required signals.
2. It refers to the speed and capability for a group of networking devices to run a specific
routing protocol. It functions to keep the network topology consistent.
convergence service A service that provides enhancements to an underlying service in order to provide for
the specific requirements of the convergence service user.
CORBA See Common Object Request Broker Architecture
corrugated pipe Used to protect optical fibers.
CPLD Complex Programmable Logical Device
CPU See central processing unit
CRC See cyclic redundancy check
CSA Canadian Standards Association
CSES consecutive severely errored second
CSMA carrier sense multiple access
CST Common Spanning Tree
current alarm An alarm not handled or not acknowledged after being handled.
current performance Performance data stored currently in a register. An NE provides two types of registers,
data namely, 15-minute register and 24-hour register, to store performance parameters of a
performance monitoring entity. The two types of registers stores performance data only
in the specified monitoring period.

customer edge A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the
Service Provider (SP) network. A CE can be a router, switch, or host.
CWDM See coarse wavelength division multiplexing
cyclic redundancy A procedure used in checking for errors in data transmission. CRC error checking uses
check a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
D
DAPI destination access point identifiers
Data backup A method that is used to copy key data to the standby storage area, to prevent data loss
in the case of the damage or failure in the original storage area.
data communication A communication network used in a TMN or between TMNs to support the Data
network Communication Function (DCF).
data communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to
channel transmit information on operation, management, maintenance and provision (OAM&P)
between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the
192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12
is referred to as the 576 kbit/s DCC-M channel.
DBPS distribute board protect system
DCC See data communications channel
DCF See dispersion compensation fiber
DCM See dispersion compensation module
DCM frame A frame which is used to hold the DCM (Dispersion Compensation Module).
DCN See data communication network
DDF See digital distribution frame
DDN See digital data network
demultiplexer A device that separates signals that have been combined by a multiplexer for transmission
over a communications channel as a single signal.
dense wavelength Technology that utilizes the characteristics of broad bandwidth and low attenuation of
division multiplexing single mode optical fiber, employs multiple wavelengths with specific frequency spacing
as carriers, and allows multiple channels to transmit simultaneously in the same fiber.
device set A collection of multiple managed devices. By dividing managed devices into different
device sets, users can manage the devices by using the U2000 in an easier way. If an
operation authority over one device set is assigned to a user (user group), the authority
over all the devices in the device set is assigned to the user (user group), thus making it
unnecessary to set the operation authority over all the devices in a device set separately.
It is recommended to configure device set by geographical region, network level, device
type, or another criterion.
DHCP See Dynamic Host Configuration Protocol

diamond-shaped nut A type of nut that is used to fasten the wiring frame to the cabinet.
digital data network A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
digital distribution A type of equipment used between the transmission equipment and the exchange with
frame transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection,
cable patching, and test of loops that transmitting digital signals.
digital subscriber line A network device, usually situated in the main office of a telephone company that
access multiplexer receives signals from multiple customer Digital Subscriber Line (DSL) connections and
puts the signals on a high-speed backbone line using multiplexing techniques.
dispersion A kind of fiber which uses negative dispersion to compensate for the positive dispersion
compensation fiber of transmitting fiber to maintain the original shape of the signal pulse.
dispersion A module, which contains dispersion compensation fibers to compensate for the
compensation module dispersion of transmitting fiber.
Distance Vector An Internet gateway protocol mainly based on the RIP. The protocol implements a typical
Multicast Routing dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing
Protocol datagrams with its neighbors.
distributed link The distributed link aggregation group (DLAG) is a board-level port protection
aggregation group technology used to detect unidirectional fiber cuts and to negotiate with the opposite end.
In the case of a link down failure on a port or a hardware failure on a board, the services
can automatically be switched to the slave board, thus realizing 1+1 protection for the
inter-board ports.
DLAG See distributed link aggregation group
DMUX; DEMUX See demultiplexer
DNI Dual Node Interconnection
domain A logical subscriber group based on which the subscriber rights are controlled.
DQPSK differential quadrature phase shift keying
DRDB dynamic random database
DRZ differential phase return to zero
DSCP Differentiated Services Code Point
DSCR dispersion slope compensation rate
DSLAM See digital subscriber line access multiplexer
DSP Digital Signal Processing
DTE Data Terminal Equipment
DTMF See dual tone multiple frequency
DTR data terminal ready
dual tone multiple In telephone systems, multifrequency signaling in which standard set combinations of
frequency two specific voice band frequencies, one from a group of four low frequencies and the
other from a group of four higher frequencies, are used.
dual-ended switching A protection operation method which takes switching action at both ends of the protected
entity (e.g. "connection", "path"), even in the case of a unidirectional failure.

DVB Digital Video Broadcasting

DVMRP See Distance Vector Multicast Routing Protocol
DWDM See dense wavelength division multiplexing
Dynamic Host Dynamic Host Configuration Protocol (DHCP) is a client-server networking protocol.
Configuration Protocol A DHCP server provides configuration parameters specific to the DHCP client host
requesting, generally, information required by the host to participate on the Internet
network. DHCP also provides a mechanism for allocation of IP addresses to hosts.
E
E2E End to End
EAPE enhanced automatic power pre-equilibrium
EBS See excess burst size
ECC See embedded control channel
EDFA See erbium doped fiber amplifier
eDQPSK enhanced differential quadrature phase shift keying
EFM See Ethernet in the first mile
ejector lever A lever for removing circuit boards from an electronic chassis.
electric supervisory A technology realizes the communication among all the nodes and transmits the
channel monitoring data in the optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
electromagnetic Electromagnetic compatibility is the condition which prevails when telecommunications
compatibility equipment is performing its individually designed function in a common electromagnetic
environment without causing or suffering unacceptable degradation due to unintentional
electromagnetic interference to or from other equipment in the same environment.
electromagnetic Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or
interference limits the effective performance of electronics/electrical equipment.
electrostatic discharge The sudden and momentary electric current that flows between two objects at different
electrical potentials caused by direct contact or induced by an electrostatic field.
element management An element management system (EMS) manages one or more of a specific type of
system network elements (NEs). An EMS allows the user to manage all the features of each NE
individually, but not the communication between NEs - this is done by the network
management system (NMS).
embedded control A logical channel that uses a data communications channel (DCC) as its physical layer,
channel to enable transmission of operation, administration, and maintenance (OAM)
information between NEs.
EMC See electromagnetic compatibility
EMI See electromagnetic interference
EMS See element management system
enterprise system A path protocol which connects the host with various control units in a storage system.
connection It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
EPL See Ethernet private line

EPLAN See Ethernet private LAN service

erbium doped fiber An optical device that amplifies the optical signals. The device uses a short length of
amplifier optical fiber doped with the rare-earth element Erbium and the energy level jump of
Erbium ions activated by pump sources. When the amplifier passes the external light
source pump, it amplifies the optical signals in a specific wavelength range.
ESC See electric supervisory channel
ESCON See enterprise system connection
ESD See electrostatic discharge
ESD jack Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or
cabinet to the insertion of ESD wrist strap.
eSFP enhanced small form-factor pluggable
Ethernet A technology complemented in LAN. It adopts Carrier Sense Multiple Access/Collision
Detection. The speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/
s or 10000 Mbit/s. The Ethernet network features high reliability and easy maintaining..
Ethernet in the first Last mile access from the broadband device to the user community. The EFM takes the
mile advantages of the SHDSL.b is technology and the Ethernet technology. The EFM
provides both the traditional voice service and internet access service of high speed. In
addition, it meets the users' requirements on high definition television system (HDTV)
and Video On Demand (VOD).
Ethernet private LAN An Ethernet service type, which carries Ethernet characteristic information over a
service dedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or
MPLS server layer networks.
Ethernet private line A type of Ethernet service that is provided with dedicated bandwidth and point-to-point
connections on an SDH, PDH, ATM, or MPLS server layer network.
Ethernet virtual An Ethernet service type, which carries Ethernet characteristic information over a shared
private LAN service bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
Ethernet virtual An Ethernet service type, which carries Ethernet characteristic information over shared
private line bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server
layer networks.
ETS European Telecommunication Standards
ETSI European Telecommunications Standards Institute
ETSI 300mm cabinet A cabinet which is 600mm in width and 300mm in depth, compliant with the standards
of the ETSI.
European Committee The European Committee for Electrotechnical Standardization was established in 1976
for Electrotechnical in Brussels. It is the result of the incorporation of two former organizations. It aims to
Standardization reduce internal frontiers and trade barriers for electrotechnical products, systems and
services.
EVOA electrical variable optical attenuator
EVPL See Ethernet virtual private line
EVPLAN See Ethernet virtual private LAN service

excess burst size A parameter related to traffic. In the single rate three color marker (srTCM) mode, the
traffic control is achieved by the token buckets C and E. Excess burst size is a parameter
used to define the capacity of token bucket E, that is, the maximum burst IP packet size
when the information is transferred at the committed information rate. This parameter
must be larger than 0. It is recommended that this parameter should be not less than the
maximum length of the IP packet that might be forwarded.
Extended ID The number of the subnet that an NE belongs to, for identifying different network
segments in a WAN. The extended ID and ID form the physical ID of the NE.
External cable The cables and optical fibers which are used for connecting electrical interfaces and
optical interfaces of one cabinet to interfaces of other cabinets or peripherals.
eye pattern An oscilloscope display of synchronized pseudo-random digital data (signal amplitude
versus time), showing the superposition of accumulated output waveforms.
F
F1 byte The user path byte, which is reserved for the user, but is typically 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.
fast Ethernet Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 times
faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so
on. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the following
three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables),
100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical
fibers).
fault A failure to implement the function while the specified operations are performed. A fault
does not involve the failure caused by preventive maintenance, insufficiency of external
resources and intentional settings.
FBG fiber Bragg grating
FC See fiber channel
FDB flash database
FDDI See fiber distributed data interface
FE See fast Ethernet
FEC See forward error correction
fiber channel A high-speed transport technology used to build storage area networks (SANs). Fiber
channel can be on the networks carrying ATM and IP traffic. It is primarily used for
transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode
and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair
copper wires and coaxial cables. Fiber channel provides both connection-oriented and
connectionless services.
fiber distributed data A standard developed by the American National Standards Institute (ANSI) for high-
interface speed fiber-optic local area networks (LANs). FDDI provides specifications for
transmission rates of 100 megabits (100 million bits) per second on networks based on
the token ring network.
fiber management tray A device used to coil up extra optical fibers.

fiber patch cord A kind of fiber used for connections between the subrack and the ODF, and for
connections between subracks or inside a subrack.
fiber spool A device used in coiling up an extra length of optical fibers.
Fiber trough The trough that is used for routing fibers.
fiber/cable Fiber & Cable is the general name of optical fiber and cable. It refers to the physical
entities that connect the transmission equipment, carry transmission objects (user
information and network management information) and perform transmission function
in the transmission network. The optical fiber transmits optical signal, while the cable
transmits electrical signal. The fiber/cable between NEs represents the optical fiber
connection or cable connection between NEs. The fiber/cable between SDH NEs
represents the connection relation between NEs. At this time, the fiber/cable is of optical
fiber type.
field programmable A type of semi-customized circuit used in the Application Specific Integrated Circuit
gate array (ASIC) field. It is developed on the basis of the programmable components, such as the
PAL, GAL, and EPLD. It not only remedies the defects of customized circuits, but also
overcomes the disadvantage of the original programmable components in terms of the
limited number of gate arrays.
FIFO See First in First out
File Transfer Protocol A member of the TCP/IP suite of protocols, used to copy files between two computers
on the Internet. Both computers must support their respective FTP roles: one must be an
FTP client and the other an FTP server.
First in First out A stack management mechanism. The first saved data is first read and invoked.
Flow An aggregation of packets that have the same characteristics. On the network
management system or NE software, flow is a group of classification rules. On boards,
it is a group of packets that have the same quality of service (QoS) operation. At present,
two flows are supported: port flow and port+VLAN flow. Port flow is based on port ID
and port+VLAN flow is based on port ID and VLAN ID. The two flows cannot coexist
in the same port.
FMT See fiber management tray
FOADM fixed optical add/drop multiplexer
FOAs fixed optical attenuator
Forced switch For normal traffic signals, switches normal traffic signal to the protection section, unless
an equal or higher priority switch command is in effect or SF condition exists on the
protection section, by issuing a forced switch request for that traffic signal.
forward error A bit error correction technology that adds the correction information to the payload at
correction the transmit end. Based on the correction information, the bit errors generated during
transmission are corrected at the receive end.
four-wave mixing Four-Wave Mixing (FWM), also called four-photon mixing, occurs when the interaction
of two or three optical waves at different wavelengths generates new optical waves,
called mixing products or sidebands, at other wavelengths.
FPGA See field programmable gate array

frame A frame, starting with a header, is a string of bytes with a specified length. Frame length
is represented by the sampling circle or the total number of bytes sampled during a circle.
A header comprises one or a number of bytes with pre-specified values. In other words,
a header is a code segment that reflects the distribution (diagram) of the elements pre-
specified by the sending and receiving parties.
frame alignment signal A distinctive signal inserted in every frame or once in every n frames, always occupying
the same relative position within the frame, and used to establish and maintain frame
alignment.
FTP See File Transfer Protocol
full-duplex A full-duplex, or sometimes double-duplex system, allows communication in both
directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line
telephone networks are full-duplex, since they allow both callers to speak and be heard
at the same time. A good analogy for a full-duplex system would be a two-lane road with
one lane for each direction.
gain The ratio between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
gain flattening filter Gain Flattening Filter (GFFs), also known as gain equalizing filters, are used to flatten
or smooth out unequal signal intensities over a specified wavelength range. This unequal
signal intensity usually occurs after an amplification stage (for example, EDFA and/or
Raman). Typically, GFFs are used in conjunction with gain amplifiers to ensure that the
amplified channels all have the same gain. A static spectral device that flattens the output
spectrum of an erbium-doped fiber amplifier.
Gateway IP When an NE accesses a remote network management system or NE, a router can be used
to enable the TCP/IP communication. In this case, the IP address of the router is the
gateway IP. Only the gateway NE requires the IP address. The IP address itself cannot
identify the uniqueness of an NE. The same IP addresses may exist in different TCP/IP
networks. An NE may have multiple IP addresses, for example, one IP address of the
network and one IP address of the Ethernet port.
gateway network A network element that is used for communication between the NE application layer and
element the NM application layer
Gb See gigabit
GCC general communication channel
GCP See GMPLS control plan
GE See gigabit Ethernet
GE ADM The technology can optimize GE service transport over WDM for Metro network. It
owns the capability of GE service convergence and grooming and benefits to use the
network resource more effectively.
generic framing A framing and encapsulated method which can be applied to any data type. It has been
procedure standardized by ITU-T SG15.
GFF See gain flattening filter
GFP See generic framing procedure

gigabit In data communications, a gigabit is one billion bits, or 1,000,000,000 (that is, 10^9)
bits. It's commonly used for measuring the amount of data that is transferred in a second
between two telecommunication points.
gigabit Ethernet GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.
It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and it does not support
coaxial cables or other cables. It also supports the channels in the bandwidth mode. If
Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge
(switch) or a router as the center, it gives full play to the performance and the bandwidth.
In the network structure, Gigabit Ethernet uses full duplex links that are private, causing
the length of the links to be sufficient for backbone applications in a building and campus.
Global Positioning A global navigation satellite system. It provides reliable positioning, navigation, and
System timing services to worldwide users.
GMPLS generalized multiprotocol label switching
GMPLS control plan The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei.
The OptiX GCP applies to the OptiX OSN product series. By using this software, the
traditional network can evolve into the ASON network. The OptiX OSN product series
support the ASON features.
GNE See gateway network element
GPS See Global Positioning System
graphical user interface A visual computer environment that represents programs, files, and options with
graphical images, such as icons, menus, and dialog boxes, on the screen.
grounding The connection of sections of an electrical circuit to a common conductor, called the
ground, which serves as the reference for the other voltages in the circuit.
GSSP General Snooping and Selection Protocol
GUI See graphical user interface
H
Hardware loopback A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
HCS See hierarchical cell structure
HDB high density bipolar code
HDLC See high level data link control
hierarchical cell This is a term typically used to describe the priority of cells within a mixed environment.
structure That is when Macro, Micro, and Pico cells may be viewed as candidates for cell
reselection the priority described by the HCS will be used in the associated calculations.
high level data link The HDLC protocol is a general purpose protocol which operates at the data link layer
control of the OSI reference model. Each piece of data is encapsulated in an HDLC frame by
adding a trailer and a header.
History alarm The confirmed alarms that have been saved in the memory and other external memories.
History Performance The performance data that is stored in the history register or that is automatically reported
Data and stored in the NMS.

I
IAE incoming alignment error
IC See integrated circuit
ICC ITU carrier code
ICMP See Internet Control Message Protocol
ID See identity
identity The collective aspect of the set of characteristics by which a thing is definitively
recognizable or known.
Idle resource optical When the U2000 is started successfully, an NE icon called "Idle ONE" will be displayed
NE on the topological view. In this NE, the subracks and boards that are not divided to other
optical NEs (such as OTM, OADM and other NEs) are retained. In this NE, idle DWDM
subracks and boards are reserved, which can be distributed to other ONEs. Double-click
the NE icon to view all the currently idle DWDM subracks or boards in the network.
IE See Internet Explorer
IEC See International Electrotechnical Commission
IEEE See Institute of Electrical and Electronics Engineers
IETF See Internet Engineering Task Force
IGMP See Internet Group Management Protocol
Input jitter tolerance The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when
modulating the signal at an equipment input port, results in no more than two errored
seconds cumulative, where these errored seconds are integrated over successive 30
second measurement intervals.
Institute of Electrical A society of engineering and electronics professionals based in the United States but
and Electronics boasting membership from numerous other countries. The IEEE focuses on electrical,
Engineers electronics, computer engineering, and science-related matters.
integrated circuit A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
integrated services A network defined in CCITT, providing comprehensive transmission service for the
digital network voice, video, and data. The ISDN enables the voice, video, and data transmission on a
small number of data channels simultaneously, thus implementing a comprehensive
transmission service.
intelligent power A technology that the system reduces the optical power of all the amplifiers in an adjacent
adjustment regeneration section in the upstream to a safety level if the system detects the loss of
optical signals on the link. The loss of optical signals may due to the fiber is broken, the
performance of equipments trend to be inferior or the connector is not plugged well.
Thus, the maintenance engineers are not hurt by the laser being sent out from the slice
of broken fiber.
Internal cable The cables and optical fibers which are used for interconnecting electrical interfaces and
optical interfaces within the cabinet.
internal spanning tree A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0.

International The International Electrotechnical Commission (IEC) is an international and non-

Electrotechnical governmental standards organization dealing with electrical and electronical standards.
Commission
International An international association that works to establish global standards for communications
Organization for and information exchange. Primary among its accomplishments is the widely accepted
Standardization ISO/OSI reference model, which defines standards for the interaction of computers
connected by communications networks.
International A United Nations agency, one of the most important and influential recommendation
Telecommunication bodies, responsible for recommending standards for telecommunication (ITU-T) and
Union radio networks (ITU-R).
International An international body that develops worldwide standards for telecommunications
Telecommunication technologies. These standards are grouped together in series which are prefixed with a
Union- letter indicating the general subject and a number specifying the particular standard. For
Telecommunication example, X.25 comes from the "X" series which deals with data networks and open
Standardization Sector system communications and number "25" deals with packet switched networks.
Internet Control A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and
Message Protocol other information relevant to IP packet processing. For example, it can let the IP software
on one machine inform another machine about an unreachable destination. See also
communications protocol, IP, ISO/OSI reference model, packet (definition 1).
Internet Engineering A worldwide organization of individuals interested in networking and the Internet.
Task Force Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with
studying technical problems facing the Internet and proposing solutions to the Internet
Architecture Board (IAB). The work of the IETF is carried out by various working groups
that concentrate on specific topics, such as routing and security. The IETF is the publisher
of the specifications that led to the TCP/IP protocol standard.
Internet Explorer Microsoft's Web browsing software. Introduced in October 1995, the latest versions of
Internet Explorer include many features that allow you to customize your experience on
the Web. Internet Explorer is also available for the Macintosh and UNIX platforms.
Internet Group The protocol for managing the membership of Internet Protocol multicast groups among
Management Protocol the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish
and maintain multicast group memberships.
Internet Protocol The TCP/IP standard protocol that defines the IP packet as the unit of information sent
across an internet and provides the basis for connectionless, best-effort packet delivery
service. IP includes the ICMP control and error message protocol as an integral part. The
entire protocol suite is often referred to as TCP/IP because TCP and IP are the two
fundamental protocols. IP is standardized in RFC 791.
IP See Internet Protocol
IP address A 32-bit (4-byte) binary number that uniquely identifies a host (computer) connected to
the Internet for communication with other hosts in the Internet by transferring packets.
An IP address is expressed in dotted decimal notation, consisting of the decimal values
of its 4 bytes, separated with periods; for example, 127.0.0.1. The first three bytes of the
IP address identify the network to which the host is connected, and the last byte identify
the host itself.
IP over DCC The IP Over DCC follows TCP/IP telecommunications standards and controls the remote
NEs through the Internet. The IP Over DCC means that the IP over DCC uses overhead
DCC byte (the default is D1-D3) for communication.
IPA See intelligent power adjustment

IPG inter-packet gap

ISDN See integrated services digital network
ISO See International Organization for Standardization
IST See internal spanning tree
ITU See International Telecommunication Union
ITU-T See International Telecommunication Union-Telecommunication Standardization
Sector
J
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
Jitter transfer The physical relationship between jitter applied at the input port and the jitter appearing
at the output port.
L
label switched path A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label
switching mechanisms. A label-switched path can be chosen dynamically, based on
normal routing mechanisms, or through configuration.
LACP See Link Aggregation Control Protocol
LAG See link aggregation group
LAN See local area network
LAPD link access procedure on the D channel
LAPS link access protocol-SDH
Laser A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
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.
LB See loopback
LCAS See link capacity adjustment scheme
LCD See liquid crystal display
LCN local communication network
LCT local craft terminal
LED See light emitting diode
LHP long hop

light emitting diode A display and lighting technology used in almost every electrical and electronic product
on the market, to from a tiny on/off light to digital readouts, flashlights, traffic lights and
perimeter lighting. LEDs are also used as the light source in multimode fibers, optical
mice and laser-class printers.
Link Aggregation A method of bundling a group of physical interfaces together as a logical interface to
Control Protocol increase bandwidth and reliability. For related protocols and standards, refer to IEEE
802.3ad.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link
aggregation group so that a MAC client can treat the link aggregation group as if it were
a single link.
link capacity LCAS in the virtual concatenation source and sink adaptation functions provides a
adjustment scheme control mechanism to hitlessly increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the Network and Element Management Systems.
Link Control Protocol In the Point-to-Point Protocol (PPP), the Link Control Protocol (LCP) establishes,
configures, and tests data-link Internet connections.
link state The link in LSA is any type of connection between OSPF routers, while the state is the
advertisement condition of the link.
linktrace message The message sent by the initiator MEP of 802.1ag MAC Trace to the destination MEP
is called Linktrace Message(LTM). LTM includes the Time to Live (TTL) and the MAC
address of the destination MEP2.
linktrace reply For 802.1ag MAC Trace, the destination MEP replies with a response message to the
source MEP after the destination MEP receives the LTM, and the response message is
called Linktrace Reply (LTR). LTR also includes the TTL that equals the result of the
TTL of LTM minus 1.
liquid crystal display A type of display that uses a liquid compound having a polar molecular structure,
sandwiched between two transparent electrodes.
LLC See logical link control
LMP link management protocol
LOC loss of clock
local area network A network formed by the computers and workstations within the coverage of a few square
kilometers or within a single building. It features high speed and low error rate. Ethernet,
FDDI, and Token Ring are three technologies used to implement a LAN. Current LANs
are generally based on switched Ethernet or Wi-Fi technology and running at 1,000 Mbit/
s (that is, 1 Gbit/s).
Locked switching When the switching condition is satisfied, this function disables the service from being
switched from the working channel to the protection channel. When the service has been
switched, the function enables the service to be restored from the protection channel to
the working channel.
logical link control According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper
sublayer of the OSI data link layer. The LLC is the same for the various physical media
(such as Ethernet, token ring, WLAN).
logical port A logical port is a logical number assigned to every application.

loopback A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors.
LOP See loss of pointer
LOS See Loss Of Signal
loss of pointer Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the
PHY overhead indicating that the receiving equipment has lost the pointer to the start of
cell in the payload. This is used to monitor the performance of the PHY layer.
Loss Of Signal Loss of signal (LOS) indicates that there are no transitions occurring in the received
signal.
Lower subrack The subrack close to the bottom of the cabinet when a cabinet contains several subracks.
LP See logical port
LPT link-state pass through
LSA See link state advertisement
LSP See label switched path
LT linktrace
LTM See linktrace message
LTR See linktrace reply
M
MA Maintenance Associations
MAC See media access control
MADM multiple add/drop multiplexer
main distribution A device at a central office, on which all local loops are terminated.
frame
main path interface at A reference point on the optical fiber just after the OM/OA output optical connector.
the transmitter
main topology A interface that displays the connection relation of NEs on the NMS (screen display).
The default client interface of the NMS, a basic component of the human-machine
interactive interface. The topology clearly shows the structure of the network, the alarms
of different NEs, subnets in the network, the communication status as well as the basic
network operation status. All topology management functions are accessed here.
maintenance domain The network or the part of the network for which connectivity is managed by CFM. The
devices in an MD are managed by a single ISP.
maintenance point Maintenance Point (MP) is one of either a MEP or a MIP.
MAN See metropolitan area network
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.

Management The information that is used for network management in a transport network.
information
management A type of database used for managing the devices in a communications network. It
information base comprises a collection of objects in a (virtual) database used to manage entities (such as
routers and switches) in a network.
manual switch Switches normal traffic signal to the protection section, unless a failure condition exists
on other sections (including the protection section) or an equal or higher priority switch
command is in effect, by issuing a manual switch request for that normal traffic signal.
Mapping A procedure by which tributaries are adapted into virtual containers at the boundary of
an SDH network.
marking-off template A quadrate cardboard with four holes. It is used to mark the positions of the installation
holes for the cabinet.
MD See maintenance domain
MDB Memory Database
MDF See main distribution frame
MDP message dispatch process
MDS message distribution service software
ME maintenance entities
mean launched power The average power of a pseudo-random data sequence coupled into the fiber by the
transmitter.
Mean Time Between The average time between consecutive failures of a piece of equipment. It is a measure
Failures of the reliability of the system.
media access control A protocol at the media access control sublayer. The protocol is at the lower part of the
data link layer in the OSI model and is mainly responsible for controlling and connecting
the physical media at the physical layer. When transmitting data, the MAC protocol
checks whether to be able to transmit data. If the data can be transmitted, certain control
information is added to the data, and then the data and the control information are
transmitted in a specified format to the physical layer. When receiving data, the MAC
protocol checks whether the information is correct and whether the data is transmitted
correctly. If the information is correct and the data is transmitted correctly, the control
information is removed from the data and then the data is transmitted to the LLC layer.
MEP maintenance end point
metropolitan area A metropolitan area network (MAN) is a network that interconnects users with computer
network resources in a geographic area or region larger than that covered by even a large local
area network (LAN) but smaller than the area covered by a wide area network (WAN).
The term is applied to the interconnection of networks in a city into a single larger
network (which may then also offer efficient connection to a wide area network). It is
also used to mean the interconnection of several local area networks by bridging them
with backbone lines. The latter usage is also sometimes referred to as a campus network.
MFAS See multiframe alignment signal
MIB See management information base
MIP maintenance intermediate point
MLD See multicast listener discovery

MLM laser See multi-longitudinal mode laser

MO See managed object
mother board A printed board assembly that is used for interconnecting arrays of plug-in electronic
modules.
mounting ear A piece of angle plate with holes in it on a rack. It is used to fix network elements or
components.
MP See maintenance point
MPI main path interface
MPI-R main path interface at the receiver
MPI-S See main path interface at the transmitter
MPLS See Multiprotocol Label Switching
MS Multiplex Section
MSA Multiplex Section Adaptation
MSI multi-frame structure identifier
MSOH See multiplex section overhead
MSP See multiplex section protection
MSPP multi-service provisioning platform
MST See multiplex section termination
MSTI See multiple spanning tree instance
MSTP See Multiple Spanning Tree Protocol
MTA Mail Transfer Agent
MTBF See Mean Time Between Failures
MTU Maximum Transmission Unit
multi-longitudinal An injection laser diode which has a number of longitudinal modes.
mode laser
multicast listener The MLD is used by the IPv6 router to discover the multicast listeners on their directly
discovery connected network segments, and set up and maintain member relationships. On IPv6
networks, after MLD is configured on the receiver hosts and the multicast router to which
the hosts are directly connected, the hosts can dynamically join related groups and the
multicast router can manage members on the local network.
multiframe alignment A distinctive signal inserted in every multiframe or once in every n multiframes, always
signal occupying the same relative position within the multiframe, and used to establish and
maintain multiframe alignment.
multiple spanning tree Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTP
instance within an MST Region, to provide a simply and fully connected active topology for
frames classified as belonging to a VLAN that is mapped to the MSTI by the MST
Configuration. A VLAN cannot be assigned to multiple MSTIs.

Multiple Spanning Multiple spanning tree protocol. The MSTP can be used in a loop network. Using an
Tree Protocol algorithm, the MSTP blocks redundant paths so that the loop network can be trimmed
as a tree network. In this case, the proliferation and endless cycling of packets is avoided
in the loop network. The protocol that introduces the mapping between VLANs and
multiple spanning trees. This solves the problem that data cannot be normally forwarded
in a VLAN because in STP/RSTP, only one spanning tree corresponds to all the VLANs.
multiplex section The overhead that comprises rows 5 to 9 of the SOH of the STM-N signal. See SOH
overhead definition.
multiplex section A function, which is performed to provide capability for switching a signal between and
protection including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiplex section The function performed to generate the MSOH in the process of forming an SDH frame
termination signal and terminates the MSOH in the reverse direction.
multiplexer Equipment which combines a number of tributary channels onto a fewer number of
aggregate bearer channels, the relationship between the tributary and aggregate channels
being fixed.
Multiplexing A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
Multiprotocol Label A technology that uses short tags of fixed length to encapsulate packets in different link
Switching layers, and provides connection-oriented switching for the network layer on the basis of
IP routing and control protocols. It improves the cost performance and expandability of
networks, and is beneficial to routing.
MUX See multiplexer
MVOA mechanical variable optical attenuator
N
NA No Acknowledgment
NCP See Network Control Protocol
NE See network element
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 efficient operation, the NE configuration data is saved in DRDB and SDB at the same
time. Backing up an NE database means backing up the NE configuration data from SDB
to FDB0 and FDB1. When an NE is restarted after power-down, the NE database is
restored in the following procedures: As the SDB data is lost due to power-down, the
main control restores the data first from DRDB. If the data in DRDB is also lost due to
the exhaustion of the battery, the data is restored from FDB0 or FDB1.

NE Explorer The main operation interface, of the NMS, which is used to manage the
telecommunication equipment. In the NE Explorer, the user can query, manage and
maintain the NE, boards, and ports on a per-NE basis.
NE ID An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NE Panel A graphical user interface, of the network management system, which displays subracks,
boards, and ports on an NE. In the NE Panel, the user can complete most of the
configuration, management and maintenance functions for an NE.
NE-side data The NE configuration data that is stored on the SCC board of the equipment. The NE-
side data can be uploaded to the network management system(NMS) and thus is stored
on the NMS side.
NEBS Network Equipment Building System
NEF See network element function
Network Control This is the program that switches the virtual circuit connections into place, implements
Protocol path control, and operates the Synchronous Data Link Control (SDLC) link.
network element A network element (NE) contains both the hardware and the software running on it. One
NE is at least equipped with one system control and communication(SCC) board which
manages and monitors the entire network element. The NE software runs on the SCC
board.
network element A function block which represents the telecommunication functions and communicates
function with the TMN OSF function block for the purpose of being monitored and/or controlled.
network management The process of controlling a network so as to maximize its efficiency and productivity.
ISO's model divides network management into five categories: fault management,
accounting management, configuration management, security management and
performance management.
Network Management A system in charge of the operation, administration, and maintenance of a network.
System
network node interface The interface at a network node which is used to interconnect with another network node.
network segment A part of an Ethernet or other network, on which all message traffic is common to all
nodes, that is, it is broadcast from one node on the segment and received by all others.
network service access A network address defined by ISO, through which entities on the network layer can
point access OSI network services.
Network Time Protocol The Network Time Protocol (NTP) defines the time synchronization mechanism. It
synchronizes the time between the distributed time server and the client.
NM See network management
NMS See Network Management System
NNI See network node interface
NOC network operation center
Noise figure An index that represents the degrade extent of optical signals after the signals passing a
system.
NSAP See network service access point
NTP See Network Time Protocol

O
OA See optical amplifier
OADM See optical add/drop multiplexer
OADM frame A frame which is used to hold the OADM boards.
OAM See operation, administration and maintenance
OC See optical coupler
OCI open connection indication
OCP See optical channel protection
OD optical demultiplexing
ODB optical duobinary
ODF See optical distribution frame
ODUk optical channel data unit-k
OEQ optical equalizer
OFC open fiber control
OLA See optical line amplifier
OLP See optical line protection
OM optical multiplexing
OMS optical multiplexing section
ONE See optical network element
Online Help The capability of many programs and operating systems to display advice or instructions
for using their features when so requested by the user.
OOF See out of frame
OPA optical power adjust
open shortest path first A link-state, hierarchical interior gateway protocol (IGP) for network routing. Dijkstra's
algorithm is used to calculate the shortest path tree. It uses cost as its routing metric. A
link state database is constructed of the network topology which is identical on all routers
in the area.
Open Systems A framework of ISO standards for communication between different systems made by
Interconnection different vendors, in which the communications process is organized into seven different
categories that are placed in a layered sequence based on their relationship to the user.
Each layer uses the layer immediately below it and provides a service to the layer above.
Layers 7 through 4 deal with end-to-end communication between the message source
and destination, and layers 3 through 1 deal with network functions.
operation, A group of network support functions that monitor and sustain segment operation,
administration and activities that are concerned with, but not limited to, failure detection, notification,
maintenance location, and repairs that are intended to eliminate faults and keep a segment in an
operational state and support activities required to provide the services of a subscriber
access network to users/subscribers.
OpEx; OPEX operation expenditure
OPS optical physical section

optic fiber connector A device installed at the end of a fiber, optical source or receive unit. It is used to couple
the optical wave to the fiber when connected to another device of the same type. A
connector can either connect two fiber ends or connect a fiber end and a optical source
(or a detector).+
optical add/drop A device that can be used to add the optical signals of various wavelengths to one channel
multiplexer and drop the optical signals of various wavelengths from one channel.
optical amplifier Devices or subsystems in which optical signals can be amplified by means of the
stimulated emission taking place in a suitable active medium.
optical attenuator A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
optical channel A signal transmitted at one wavelength in a fiber-optic system.
optical channel In an optical transmission link that contains multiple wavelengths, when a certain
protection wavelength goes faulty, the services at the wavelength can be protected if the optical
channel protection is configured.
optical coupler A coupler for coupling light in an optical system. Multiple discrete layers of alternating
optical materials have respective first and second indexes of refraction. The thickness of
each layer is a fraction of the light wavelength.
optical distribution A frame which is used to transfer and spool fibers.
frame
optical line amplifier A piece of equipment that functions as an OLA to directly amplify the input optical
signals and to compensate for the line loss. Currently, the key component of the OLA is
the EDFA amplifier.
optical line protection A protection mechanism that adopts dual fed and selective receiving principle and single-
ended switching mode. In this protection, two pairs of fibers are used. One pair of fibers
forms the working route. The working route transmits line signals when the line is
normal. The other pair of fibers forms the protection route. The protection route carries
line signals when the line is broken or the signal attenuation is extremely large.
optical network A transport entity that implements the NE functions (terminal multiplexing, add/drop
element multiplexing, cross-connection and regeneration) in a DWDM layer network. The types
of ONEs include OTM, OADM, OLA, REG and OXC. The locating of an ONE is
equivalent to that of a common NE. In a view, an ONE is displayed with an icon, like a
common NE and its alarm status can be displayed with colors. Logically, an ONE consists
of different subracks. Like a common NE, an ONE cannot be expanded or entered like
a sub-network. Similar to a common NE, an ONE provides a list of the subracks that
form the NE to display the board layout.
optical signal-to-noise The most important index of measuring the performance of a DWDM system. The ratio
ratio of signal power and noise power in a transmission link. That is, OSNR = signal power/
noise power.
optical spectrum A device that allows the details of a region of an optical spectrum to be resolved.
analyzer Commonly used to diagnose DWDM systems.
optical supervisory A technology that realizes communication among nodes in optical transmission network
channel and transmits the monitoring data in a certain channel (the wavelength of the working
channel for it is 1510 nm and that of the corresponding protection one is 1625 nm).
Optical switch A passive component possessing two or more ports which selectively transmits, redirects,
or blocks optical power in an optical fiber transmission line.

optical time domain A device that sends a very short pulse of light down a fiber optic communication system
reflectometer and measures the time history of the pulse reflection to measure the fiber length, the light
loss and locate the fiber fault.
optical transmission Optical transmission section allows the network operator to perform monitoring and
section maintenance tasks between NEs.
optical transponder A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2-
unit compliant WDM wavelength.
optical transport A network that uses the optical signal to transmit data
network
optical wavelength In the optical wavelength shared protection (OWSP), the service protection between
shared protection different stations can be achieved by using the same wavelength, realizing wavelength
sharing. This saves the wavelength resources and lowers the cost. The optical wavelength
shared protection is mainly applied to the ring network which is configured with
distributed services. It is achieved by using the OWSP board. In a ring network where
services are distributed at adjacent stations, each station requires one OWSP board. Then,
two wavelengths are enough for configuring the shared protection to protect one service
among stations.
OPU optical channel payload unit
OPUk optical channel payload unit-k
orderwire A channel that provides voice communication between operation engineers or
maintenance engineers of different stations.
original equipment An original equipment manufacturer, or OEM is typically a company that uses a
manufacturer component made by a second company in its own product, or sells the product of the
second company under its own brand.
OSA See optical spectrum analyzer
OSC See optical supervisory channel
OSI See Open Systems Interconnection
OSN optical switch node
OSNR See optical signal-to-noise ratio
OSPF See open shortest path first
OTDR See optical time domain reflectometer
OTM optical terminal multiplexer
OTN See optical transport network
OTS See optical transmission section
OTU See optical transponder unit
OTUk optical channel transport unit-k
out of frame An NE transmits an OOF downstream when it receives framing errors in a specified
number of consecutive frame bit positions.
Output optical power The ranger of optical energy level of output signals.
overhead cabling Cables or fibers connect the cabinet with other equipment from the top of the cabinet.
OWSP See optical wavelength shared protection

P
PA pre-amplifier
packet over SDH/ A MAN and WAN technology that provides point-to-point data connections. The POS
SONET interface uses SDH/SONET as the physical layer protocol, and supports the transport of
packet data (such as IP packets) in MAN and WAN.
packet switched A telecommunication network which works in packet switching mode.
network
Packing case A case which is used for packing the board or subrack.
Paired slots Two slots of which the overheads can be passed through by using the bus on the
backplane.
pass-through The action of transmitting the same information that is being received for any given
direction of transmission.
PBS See peak burst size
PCB See printed circuit board
PCC protection communication channel
PCC See policy and charging control
PCS See physical coding sublayer
PDH See plesiochronous digital hierarchy
PDL See polarization dependent loss
PDU Protocol Data Unit
PE Provider Edge
peak burst size A parameter used to define the capacity of token bucket P, that is, the maximum burst
IP packet size when the information is transferred at the peak information rate. This
parameter must be larger than 0. It is recommended that this parameter should be not
less than the maximum length of the IP packet that might be forwarded.
peak information rate Peak Information Rate. A traffic parameter, expressed in bit/s, whose value should be
not less than the committed information rate.
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. The object of performance event monitoring is the board functional module, so
every board functional module has a performance register. A performance register is
used to count the performance events taking place within a period of operation time, so
as to evaluate the quality of operation from the angle of statistics.
PGND protection ground
phase-locked loop A circuit that consists essentially of a phase detector which compares the frequency of
a voltage-controlled oscillator with that of an incoming carrier signal or reference-
frequency generator; the output of the phase detector, after passing through a loop filter,
is fed back to the voltage-controlled oscillator to keep it exactly in phase with the
incoming or reference frequency.
PHY See physical sublayer & physical layer

physical coding The PCS further helps to define physical layer specifications for 10 gigabit Ethernet after
sublayer having been broken down into their Physical Media Dependent Sublayer or PMD. Each
sublayer places the 10GBASE standards into either LAN or WAN specifications.
physical sublayer & 1. physical sublayer: One of two sublayers of the FDDI physical layer. 2. physical layer:
physical layer In ATM, the physical layer provides the transmission of cells over a physical medium
that connects two ATM devices. The PHY is comprised of two sublayers: PMD and TC
PID photonics integrated device
PIM-DM protocol independent multicast-dense mode
PIM-SM See protocol independent multicast sparse mode
PIN See Positive Intrinsic Negative
PIR See peak information rate
plesiochronous digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
hierarchy rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
PLL See phase-locked loop
PMD polarization mode dispersion
PMI payload missing indication
POH path overhead
point to multipoint A communications network that provides a path from one location to multiple locations
(from one to many).
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates
data packets on the network layer. It is located in layer 2 of the IP protocol stack.
Point-to-Point Protocol PPPoE, point-to-point protocol over Ethernet, is a network protocol for encapsulating
over Ethernet PPP frames in Ethernet frames. It is used mainly with DSL services. It offers standard
PPP features such as authentication, encryption, and compression.
Pointer An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which it is supported.
polarization dependent The maximum, peak-to-peak insertion loss (or gain) variation caused by a component
loss when stimulated by all possible polarization states. It is specified in dB units.
policy and charging Short for Policy and Charging Control, the PCC is defined in 3GPP R7. The PCC
control provides the QoS control and service-based charging functions in the wireless bearer
network.
POS See packet over SDH/SONET
Positive Intrinsic Photodiode. A semiconductor detector with an intrinsic (i) region separating the p- and
Negative n-doped regions. It has fast linear response and is used in fiber-optic receivers.
Power box A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
power distribution box A power box through which the power enters the cabinet and is re-distributed to various
components, at the mean time, the Power Distribution Box protects the electric devices
from current overload.
PPP See Point-to-Point Protocol
PPPoE See Point-to-Point Protocol over Ethernet

PRBS See pseudo random binary sequence

PRC primary reference clock
PRI See primary rate interface
primary rate interface An interface consisting of 23 channel Bs and a 64 kbit/s channel D that uses the T1 line,
or consisting of 30 channel Bs and a channel D that uses the E1 line.
printed circuit board A board used to mechanically support and electrically connect electronic components
using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
protection ground A cable which connects the equipment and the protection grounding bar. Usually, one
cable half of the cable is yellow; while the other half is green.
Protection path A specific path that is part of a protection group and is labeled protection.
Protection policy In case the service route provides multiple service protections, different protection
policies can be selected as required. Protection policy refers to the protection mode given
the priority in use for the trail: protection, no protection, and extra traffic. Of the above,
the protection preference is divided into trail protection and subnet connection
protection.
Protection service A specific service that is part of a protection group and is labeled protection.
protocol independent It is applicable to large-scale multicast networks with scattered members.
multicast sparse mode
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the
sequence values of any of the other elements, similar to real random sequences.
PSI payload structure identifier
PSN See packet switched network
PSTN See public switched telephone network
PT payload type
PTMP See point to multipoint
PTN packet transport network
PTP Point-To-Point
public switched A telecommunications network established to perform telephone services for the public
telephone network subscribers. Sometimes called POTS.
Q
QA Q adaptation
QoS See quality of service
quality of service A commonly-used performance indicator of a telecommunication system or channel.
Depending on the specific system and service, it may relate to jitter, delay, packet loss
ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the
transmission system and the effectiveness of the services, as well as the capability of a
service provider to meet the demands of users.

R
radio network An equipment in the RNS which is in charge of controlling the use and the integrity of
controller the radio resources.
RAI remote alarm indication
RAM See random access memory
random access memory Semiconductor-based memory that can be read and written by the central processing unit
(CPU) or other hardware devices. The storage locations can be accessed in any order.
Note that the various types of ROM memory are capable of random access but cannot
be written to. The term RAM, however, is generally understood to refer to volatile
memory that can be written to as well as read.
Rapid Spanning Tree An evolution of the Spanning Tree Protocol, providing for faster spanning tree
Protocol convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Receiver Sensitivity Receiver sensitivity is defined as the minimum acceptable value of average received
power at point R to achieve a 10-12 (The FEC is open).
reconfiguration optical The WDM equipment supports the ROADM. It flexibly and dynamically adjusts add/
add/drop multiplexer drop wavelengths of sites on the network by adjusting the pass-through or block status
of any wavelength without affecting the service transmission in the main optical channel.
This implements wavelength allocation among sites on the network. After the ROADM
is used, the existing services are not affected during upgrade. The wavelength can be
modified quickly and efficiently during network maintenance, which reduces
maintenance cost. In addition, the ROADM supports the equalization for optical power,
which equalizes the optical power at the channel level.
Reed Solomon Code A type of forward error correcting codes invented in 1960 by Irving Reed and Gustave
Solomon, which has become commonplace in modern digital communications.
reference clock A kind of stable and high-precision autonous clock providing frequencies for other clocks
for reference.
Reflectance The ratio of the reflected optical power to the incident optical power.
REG A piece of equipment or device that regenerates electrical signals.
Regeneration The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
REI Remote Error Indication
Resource Reservation The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is
Protocol used to reserve resources on every node along a path. RSVP operates on the transport
layer; however, RSVP does not transport application data. RSVP is a network control
protocol like Internet Control Message Protocol (ICMP).
RF Radio Frequency
RFC Requirement for Comments
RFI remote failure indication
ring network A type of network topology in which each node connects to exactly two other nodes,
forming a circular pathway for signals.
RIP See Routing Information Protocol

RMON remote network monitoring

RNC See radio network controller
ROADM See reconfiguration optical add/drop multiplexer
route A route is the path that network traffic takes from its source to its destination. In a TCP/
IP network, each IP packet is routed independently. Routes can change dynamically.
Routing Information A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route
Protocol based on the smallest hop count between source and destination. RIP is a distance vector
protocol that routinely broadcasts routing information to its neighboring routers and is
known to waste bandwidth.
RS Code See Reed Solomon Code
RS232 In the asynchronous transfer mode and there is no hand-shaking signal. It can
communicate with RS232 and RS422 of other stations in point-to-point mode and the
transmission is transparent. Its highest speed is 19.2kbit/s.
RSTP See Rapid Spanning Tree Protocol
RSVP See Resource Reservation Protocol
RZ return to zero code
S1 byte In an SDH network, each network element traces step by step to the same clock reference
source through a specific clock synchronization path, thus realizing the synchronization
of the whole network. If a clock reference source traced by the NE is missing, this NE
will trace another clock reference source of a lower level. To implement protection
switching of clocks in the whole network, the NE must learn about clock quality
information of the clock reference source it traces. Therefore, ITU-T defines S1 byte to
transmit network synchronization status information. It uses the lower four bits of the
multiplex section overhead S1 byte to indicate 16 types of synchronization quality
grades. Auto protection switching of clocks in a synchronous network can be
implemented using S1 byte and a proper switching protocol.
Safe control switch The IPA safe switch is set in consideration of the long-span networking requirement,
which cannot allow too low output optical power. If the safe control switch is turned off,
IPA restarting optical power is the specified output power of the OAU. Otherwise, the
IPA restarting optical power is restricted to less than 10 dBm.
SAN See storage area network
SAP service access point
SAPI source access point identifiers
SBS stimulated Brillouin scattering
SC See square connector
SD See signal degrade
SD trigger flag SD stands for signal degrade. The SD trigger flag determines whether to perform a
switching when SD occurs. The SD trigger flag can be set by using the network
management system.
SDH See synchronous digital hierarchy

SDI See Serial Digital Interface

SDP serious disturbance period
Search domain Search field refers to the range of IP addresses being searched. In the TCP/IP, the IP
addresses include: Category A address (1.0.0.0---126.255.255.255). For example,
10.*.*.*, whose search field is 10.255.255.255, all 10.*.*.* to be searched. Category B
address (128.0.0.0---191. 255. 255. 255). For example, 129.9.*.*, whose search field is
129.9.255.255, all 129.9.*.* to be searched. Category C address (192.0.0.0---223. 255.
255. 255). For example, 192.224.9.*, whose search field is 192.224.9.255, all
192.224.9.* to be searched. Category D address (224.0.0.0---230.255.255.255), which
is reserved. Category E address (240.0.0.0---247.255.255.255), which is reserved. Net-
id 127.*.*.*, in which .*.*.* can be any number. This net-ID is a local address.
Secure File Transfer A network protocol designed to provide secure file transfer over SSH.
Protocol
Self-healing Self-healing is the establishment of a replacement connection by network without the
NMC function. When a connection failure occurs, the replacement connection is found
by the network elements and rerouted depending on network resources available at that
time.
Serial Digital Interface An interface for transmitting digital signals.
Serial Line Interface Serial Line Interface Protocol, defines the framing mode over the serial line to implement
Protocol transmission of messages over the serial line and provide the remote host interconnection
function with a known IP address.
service level agreement A service contract between a customer and a service provider that specifies the
forwarding service a customer should receive. A customer may be a user organization
(source domain) or another differentiated services domain (upstream domain). A SLA
may include traffic conditioning rules which constitute a traffic conditioning agreement
as a whole or partially.
Service protection A measure that ensures that the services can be received at the receive end.
SES See severely errored second
SETS See synchronous equipment timing source
settings Parameters of a system or operation that can be selected by the user.
severely errored second A one-second period which has a bit error ratio >= 10-3 or at least one defect. Time
interval of one second during which a given digital signal is received with an error ratio
greater than 10-3 (Rec. ITU R F. 592 needs correction) .
SF See signal fail
SFP See small form-factor pluggable
SFTP See Secure File Transfer Protocol
shock-proof reinforce A process by which the cabinet is fastened to the wiring frame or the top of the equipment
room so that the cabinet stands stably.
shortcut menu A menu that is displayed when right-clicking an object's name or icon. This is also
referred to a context menu.
side door The side door of a cabinet is used to protect the equipment inside the cabinet against
unexpected touch and environment impact.

side mode suppression The Side Mode Suppression Ratio (SMSR) is the ratio of the largest peak of the total
ratio source spectrum to the second largest peak.
side trough The trough on the side of the cable rack, which is used to place nuts so as to fix the
cabinet.
signal cable Common signal cables cover the E1 cable, network cable, and other non-subscriber
signal cable.
signal degrade A signal indicating the associated data has degraded in the sense that a degraded defect
(e.g., dDEG) condition is active.
signal fail A signal that indicates the associated data has failed in the sense that a near-end defect
condition (non-degrade defect) is active.
signal to noise ratio The ratio of the amplitude of the desired signal to the amplitude of noise signals at a
given point in time. SNR is expressed as 10 times the logarithm of the power ratio and
is usually expressed in dB (Decibel).
Simple Network A network management protocol of TCP/IP. It enables remote users to view and modify
Management Protocol the management information of a network element. This protocol ensures the
transmission of management information between any two points. The polling
mechanism is adopted to provide basic function sets. According to SNMP, agents, which
can be hardware as well as software, can monitor the activities of various devices on the
network and report these activities to the network console workstation. Control
information about each device is maintained by a management information block.
single-ended switching A protection operation method which takes switching action only at the affected end of
the protected entity (e.g. "trail", "subnetwork connection"), in the case of a unidirectional
failure.
single-mode fiber A type of fiber optic cable through which only one type of light signal with a fixed wave
length can travel at a time. The inner diameter of the single-mode fiber is less than 10
microns. This type of fiber is used to transmit data in long distance.
SLA See service level agreement
SLIP See Serial Line Interface Protocol
SLM single longitudinal mode
SM section monitoring
small form-factor A specification for a new generation of optical modular transceivers.
pluggable
SMF See single-mode fiber
SMSR See side mode suppression ratio
SNCP See subnetwork connection protection
SNCTP See subnetwork connection tunnel protection
SNMP See Simple Network Management Protocol
SNR See signal to noise ratio
soft permanent An ASON connection which features flexible and dynamic adjustment of routes. SPC
connections includes different classes of services (CoS).
SONET See synchronous optical network

span The physical reach between two pieces of WDM equipment. The number of spans
determines the signal transmission distance supported by a piece of equipment and varies
according to transmission system type.
Spanning Tree Protocol STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant
network to block some undesirable redundant paths through certain algorithms and prune
a loop network into a loop-free tree network.
SPC See soft permanent connections
SPM self phase modulation
SQL See structured query language
square connector Cables may use two styles of connectors: "square" and "D-style".
SRLG Shared Risk Link Group
SRS stimulated Raman scattering
SSM See Synchronization Status Message
SSMB synchronization status message byte
SSU synchronization supply unit
STM Synchronous Transfer Mode
STM-1 See synchronous transport mode 1
STM-4 Synchronous Transport Module of order 4
storage area network An architecture to attach remote computer storage devices such as disk array controllers,
tape libraries and CD arrays to servers in such a way that to the operating system the
devices appear as locally attached devices.
STP See Spanning Tree Protocol
structured query A database query and programming language widely used for accessing, querying,
language updating, and managing data in relational database systems.
sub-network Sub-network is the logical entity in the transmission network and comprises a group of
network management objects. The network that consists of a group of interconnected or
correlated NEs, according to different functions. For example, protection subnet, clock
subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a
sub-network is used to contain the equipments which are located in adjacent regions and
closely related with one another, and it is indicated with a sub-network icon on a
topological view. The U2000 supports multilevels of sub-networks. A sub-network
planning can better the organization of a network view. On the one hand, the view space
can be saved, on the other hand, it helps the network management personnel focus on
the equipments under their management.
sub-network number A number used to differentiate network sections in a sub-network conference. A sub-
network ID consists of the first several digits (one or two) of a user phone number. An
oderwire phone number consists of the sub-network ID and the user number.
subnet mask The technique used by the IP protocol to determine which network segment packets are
destined for. The subnet mask is a binary pattern that is stored in the client machine,
server or router and is matched with the IP address.
subnetwork connection A function, which allows a working subnetwork connection to be replaced by a protection
protection subnetwork connection if the working subnetwork connection fails, or if its performance
falls below a required level.

subnetwork connection SNCTP provides a VC-4 level channel protection. When the working channel is faulty,
tunnel protection the services of the entire VC-4 path can be switched over to the protection channel.
support A part used to support and fix a cabinet on the antistatic floor, it is made of welded steel
plates and is used to block the cabinets up, thus facilitating floor paving and cabling.
Before the whole set of equipment is grounded, insulation plates must be installed under
the supports, and insulating coverings must be added to the expansion bolts to satisfy
the insulation requirements.
Suppression state An attribute set to determine whether an NE monitors the alarm. Under suppression
status, NE will not monitor the corresponding alarm conditions and the alarm will not
occur even when the alarm conditions are met.
Switching priority There may be the case that several protected boards need to be switched; thus the tributary
board switching priority should be set. If the switching priority of each board is set the
same, the tributary board that fails later cannot be switched. The board with higher
priority can preempt the switching of that with lower priority.
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link.
Message Nodes on an SDH network and a synchronization network acquire upstream clock
information through this message. Then the nodes can perform proper operations on their
clocks, such as tracing, switching, or converting to holdoff, and forward the
synchronization information to downstream nodes.
synchronize NE time To send the system time of the server of the network management system to NEs so as
to synchronize all NEs with the server.
synchronous digital A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the
hierarchy transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and B-
ISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is only used only for signals. SDH is
suitable for the fiber communication system with high speed and a large capacity since
it uses synchronous multiplexing and flexible mapping structure.
synchronous The SETS function provides timing reference to the relevant component parts of
equipment timing multiplexing equipment and represents the SDH network clement clock.
source
synchronous optical A high-speed network that provides a standard interface for communications carriers to
network connect networks based on fiberoptic cable. SONET is designed to handle multiple data
types (voice, video, and so on). It transmits at a base rate of 51.84 Mbps, but multiples
of this base rate go as high as 2.488 Gbps (gigabits per second).
synchronous transport Synchronous Transfer Mode at 155 Mbit/s.
mode 1
T
TCM Tandem Connection Monitoring
TCP See Transmission Control Protocol
TDM See time division multiplexing
TE See traffic engineering

Telecommunication A protocol model defined by ITU-T for managing open systems in a communications
Management Network network. An architecture for management, including planning, provisioning, installation,
maintenance, operation and administration of telecommunications equipment, networks
and services.
terminal multiplexer A device used at a network terminal to multiplex multiple channels of low rate signals
into one channel of high rate signals, or to demultiplex one channel of high rate signals
into multiple channels of low rate signals.
TFTP See Trivial File Transfer Protocol
TIM trace identifier mismatch
time division A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
multiplexing (TSn, n=0, 1, 2, 3 and so on), and the sampling value codes of multiple signals engross
time slots in a certain order, forming multiple multiplexing digital signals to be
transmitted over one channel.
Time Slot Continuously repeating interval of time or a time period in which two devices are able
to interconnect.
Time Synchronization Also called the moment synchronization, time synchronization means that the
synchronization of the absolute time, which requires that the starting time of the signals
keeps consistent with the UTC time.
time to live A technique used in best-effort delivery systems to prevent packets that loop endlessly.
The TTL is set by the sender to the maximum time the packet is allowed to be in the
network. Each router in the network decrements the TTL field when the packet arrives,
and discards any packet if the TTL counter reaches zero.
TL1 See Transaction Language 1
TLV Type/Length/Value
TM See terminal multiplexer
TMN See Telecommunication Management Network
TP traffic Policing
traffic engineering A technology that is used to dynamically monitor the traffic of the network and the load
of the network elements, to adjust in real time the parameters such as traffic management
parameters, route parameters and resource restriction parameters, and to optimize the
utilization of network resources. The purpose is to prevent the congestion caused by
unbalanced loads.
Transaction Language Transaction Language One is a widely used telecommunications management protocol.
1 TL1 is a vendor-independent and technology-independent man-machine language. TL1
facilities can be provided as part of an OSS for interacting with either underlying
management systems or NEs. One popular application is for a management system (or
NE) to package its trap/notification data in TL1 format and forward it to an OSS
component. ...(from authors.phptr.com/morris/glossary.html) Transaction Language 1
(TL1) is a widely used, "legacy", management protocol in telecommunications. It is a
cross-vendor, cross-technology man-machine language, and is widely used to manage
optical (SONET) and broadband access infrastructure in North America. It is defined in
GR-831 by Bellcore (now Telcordia). (from en.wikipedia.org/wiki/TL1)

Transmission Control The protocol within TCP/IP that governs the breakup of data messages into packets to
Protocol be sent via IP (Internet Protocol), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
tray A component that can be installed in the cabinet for holding chassis or other devices.
tributary unit group One or more Tributary Units, occupying fixed, defined positions in a higher order VC-
n payload is termed a Tributary Unit Group (TUG). TUGs are defined in such a way that
mixed capacity payloads made up of different size Tributary Units can be constructed
to increase flexibility of the transport network
Trivial File Transfer A small and simple alternative to FTP for transferring files. TFTP is intended for
Protocol applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication. TFTP is
small enough to be contained in ROM to be used for bootstrapping diskless machines.
trTCM Two Rate Three Color Marker
TTI trail trace identifier
TTL See time to live
TU tributary unit
TUG See tributary unit group
U
UAS unavailable second
UAT See unavailable time event
UDP See User Datagram Protocol
unavailable time event 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 within 10 consecutive
seconds.
UNI See user network interface
universal time The world-wide scientific standard of timekeeping. It is based upon carefully maintained
coordinated atomic clocks and is kept accurate to within microseconds worldwide.
Unprotected Pertaining to the transmission of the services that are not protected, the services cannot
be switched to the protection channel if the working channel is faulty or the service is
interrupted, because protection mechanism is not configured.
upload An operation to report some or all configuration data of an NE to the NMS(Network
Management system). The configuration data then covers the configuration data stored
at the NMS side.
Upper subrack The subrack close to the top of the cabinet when a cabinet contains several subracks.
User A client user of the NMS. The user name and password uniquely identifies the operation
rights of a user in the NMS.

User Datagram A TCP/IP standard protocol that allows an application program on one device to send a
Protocol datagram to an application program on another. User Datagram Protocol (UDP) uses IP
to deliver datagrams. UDP provides application programs with the unreliable
connectionless packet delivery service. Thus, UDP messages can be lost, duplicated,
delayed, or delivered out of order. UDP is used to try to transmit the data packet, that is,
the destination device does not actively confirm whether the correct data packet is
received.
user network interface The interface between user equipment and private or public network equipment (for
example, ATM switches).
UTC See universal time coordinated
V
VB virtual bridge
VC See virtual container
VCG See virtual concatenation group
VCI See virtual channel identifier
virtual channel A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to
identifier identify the next destination of a cell as it passes through a series of ATM switches on
its way to its destination.
virtual concatenation A group of co-located member trail termination functions that are connected to the same
group virtual concatenation link
virtual container The information structure used to support path layer connections in the SDH. It consists
of information payload and path Overhead (POH) information fields organized in a block
frame structure which repeats every 125 μs or 500 μs.
virtual local area A logical grouping of two or more nodes which are not necessarily on the same physical
network network segment but which share the same IP network number. This is often associated
with switched Ethernet.
virtual path identifier The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which
VP (Virtual Path) the cell belongs.
virtual private network A system configuration, where the subscriber is able to build a private network via
connections to different network switches that may include private network capabilities.
VLAN See virtual local area network
VOA Variable Optical Attenuator
voice over IP An IP telephony term for a set of facilities used to manage the delivery of voice
information over the Internet. VoIP involves sending voice information in a digital form
in discrete packets rather than by using the traditional circuit-committed protocols of the
public switched telephone network (PSTN).
VoIP See voice over IP
VPI See virtual path identifier
VPN See virtual private network
VRRP Virtual Router Redundancy Protocol

W
WAN See wide area network
wavelength division A technology that utilizes the characteristics of broad bandwidth and low attenuation of
multiplexing single mode optical fiber, uses multiple wavelengths as carriers, and allows multiple
channels to transmit simultaneously in a single fiber.
Wavelength protection The wavelength protection group is important to describe the wavelength protection
group structure. Its function is similar to that of the protection subnet in the SDH NE. The
wavelength path protection can only work with the correct configuration of the
wavelength protection group.
WDM See wavelength division multiplexing
WEEE waste electrical and electronic equipment
wide area network A network composed of computers which are far away from each other which are
physically connected through specific protocols. WAN covers a broad area, such as a
province, a state or even a country.
Working path The channels allocated to transport the normal traffic.
Working service A specific service that is part of a protection group and is labeled working.
WRR weighted round Robin
WSS wavelength selective switching
WTR Wait To Restore
WXCP wavelength cross-connection protection
WXCP service The WXCP service is also called the GE ADM protection service. The WXCP is a type
of channel protection based on ring network. It adopts the dual fed and selective receiving
principle and uses the cross-connection function to achieve service switching between
working and protection channels.
X
XFP 10Gbit/s Small Form-Factor Pluggable
XPM cross-phase modulation


Ason User Guide (v100r006c00 - 03)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ason User Guide (v100r006c00 - 03)

Încărcat de

Drepturi de autor:

Formate disponibile

OptiX OSN 8800 Intelligent Optical Transport

ASON User Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 03 (2011-09-15) Huawei Proprietary and Confidential i

About This Document

Product Name Version

OptiX OSN 8800 V100R006C00

OptiX GSP V100R006C00

iManager U2000 V100R003C00

Issue 03 (2011-09-15) Huawei Proprietary and Confidential ii

Indicates a hazard with a high level of risk which, if not

Indicates a hazard with a medium or low level of risk which,

Indicates a potentially hazardous situation that, if not

NOTE Provides additional information to emphasize or

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

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

Updates in Issue 03 (2011-09-15) Based on Product Version

Issue 03 (2011-09-15) Huawei Proprietary and Confidential iii

Commissioning The updates in this chapter are as follows:

Updates in Issue 02 (2011-04-15) Based on Product Version

About the ASON The updates in this chapter are as follows:

Commissioning The updates in this chapter are as follows:

Configuring The updates in this chapter are as follows:

Issue 03 (2011-09-15) Huawei Proprietary and Confidential iv

Updates in Issue 01 (2010-12-31) Based on Product Version

Updates in Issue 03 (2011-08-30) Based on Product Version

Updates in Issue 02 (2011-05-25) Based on Product Version

About the ASON The updates in this chapter are as follows:

Issue 03 (2011-09-15) Huawei Proprietary and Confidential v

Commissioning The updates in this chapter are as follows:

Configuring The updates in this chapter are as follows:

Updates in Issue 01 (2010-07-30) Based on Product Version

Issue 03 (2011-09-15) Huawei Proprietary and Confidential vi

Configuring This chapter has the following updates:

Alarm This chapter has the following updates:

Issue 03 (2011-09-15) Huawei Proprietary and Confidential vii

About This Document.....................................................................................................................ii

Issue 03 (2011-09-15) Huawei Proprietary and Confidential viii

1.5.3 SLA Classification of Services................................................................................................................39

2 Planning the OTN ASON........................................................................................................100

Issue 03 (2011-09-15) Huawei Proprietary and Confidential ix

2.1 Requisite Knowledge on ASON Planning......................................................................................................101

3 Planning the OCS ASON.........................................................................................................111

4 Commissioning the OTN ASON............................................................................................136

Issue 03 (2011-09-15) Huawei Proprietary and Confidential x

4.2.5 Uploading NE Configuration Data........................................................................................................149

Issue 03 (2011-09-15) Huawei Proprietary and Confidential xi

5 Commissioning the OCS ASON............................................................................................ 195

6 Configuring OTN ASON Networks......................................................................................219

Issue 03 (2011-09-15) Huawei Proprietary and Confidential xii

6.1.12 Configuring the Explicit Link..............................................................................................................266

Issue 03 (2011-09-15) Huawei Proprietary and Confidential xiii

7 Configuring OCS ASON Networks.......................................................................................315

Issue 03 (2011-09-15) Huawei Proprietary and Confidential xiv

7.6.2 Converting a Traditional Service to an ASON Service.........................................................................374

8 Routine Maintenance for an ASON Network.....................................................................415

9 Handling ASON Network Failures.......................................................................................427

Issue 03 (2011-09-15) Huawei Proprietary and Confidential xv

9.2.3 Handling the Cross-Connection Control Failure...................................................................................436

Issue 03 (2011-09-15) Huawei Proprietary and Confidential xvi

Issue 03 (2011-09-15) Huawei Proprietary and Confidential xvii