OG For WDM ASON Network Management - (V100R002C01 - 02)

iManager U2000 Unified Network Management
System
V100R002C01
Operation Guide for WDM ASON
Network Management
Issue 02
Date 2010-09-24
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2010-09-24) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Related Version
The following table lists the product version related to this document.
Product Name Version
iManager U2000 V100R002C01

Intended Audience
This document describes the procedures and operations, such as how to configure and maintain
the WDM ASON network. This document also provide the glossary, the acronyms and
abbreviations.
This document is intended for:
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.
Symbol Description
DANGER
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
WARNING
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
iManager U2000 Unified Network Management System
Operation Guide for WDM ASON Network Management About This Document
iii
Symbol Description
CAUTION
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save
time.
NOTE
Provides additional information to emphasize or supplement
important points of the main text.

Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }
*
Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]
*
Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.

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.

About This Document
Operation Guide for WDM ASON Network Management
iv Huawei Proprietary and Confidential
Issue 02 (2010-09-24)
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Updates in Issue 02 (2010-09-24) Based on Product Version V100R002C01
The second release of the iManager U2000 V100R002C01.
Some bugs in the manual of the previous version are fixed.
Updates in Issue 01 (2010-08-16) Based on Product Version V100R002C01
The first release of the iManager U2000 V100R002C01.
Operation Guide for WDM ASON Network Management About This Document
v
Contents
About This Document...................................................................................................................iii
1 Configuring WDM ASON Networks.....................................................................................1-1
1.1 WDM ASON Network Configuration............................................................................................................1-3
1.2 ASON..............................................................................................................................................................1-4
1.2.1 Basic Concepts of ASON.......................................................................................................................1-5
1.2.2 Function Structure of the ASON............................................................................................................1-7
1.2.3 ASON Protocol......................................................................................................................................1-9
1.2.4 ASON Links.........................................................................................................................................1-12
1.2.5 SLA......................................................................................................................................................1-16
1.2.6 Diamond WDM ASON Trail...............................................................................................................1-17
1.2.7 Gold WDM ASON Trail......................................................................................................................1-22
1.2.8 Silver WDM ASON Trail....................................................................................................................1-23
1.2.9 Copper WDM ASON Trail..................................................................................................................1-26
1.2.10 OVPN.................................................................................................................................................1-26
1.3 Creating an ASON Topology........................................................................................................................1-29
1.3.1 Creating NEs in Batches......................................................................................................................1-30
1.3.2 Creating a Single NE............................................................................................................................1-33
1.3.3 Creating Optical NEs...........................................................................................................................1-34
1.3.4 Setting the Node ID..............................................................................................................................1-35
1.3.5 Enabling the ASON Feature ................................................................................................................1-36
1.3.6 Uploading NE Configuration Data.......................................................................................................1-37
1.3.7 Creating Domains for an ASON Network...........................................................................................1-37
1.3.8 Synchronizing ASON NEs...................................................................................................................1-38
1.3.9 Automatically Creating Fibers According to TE Link.........................................................................1-39
1.3.10 Setting the Primary NE or Secondary NE..........................................................................................1-39
1.3.11 Setting Control Plane Parameters.......................................................................................................1-40
1.3.12 Viewing ASON NE Software Version...............................................................................................1-41
1.3.13 Disabling the Electrical-Layer ASON Feature...................................................................................1-41
1.4 Managing the ASON Protocol......................................................................................................................1-42
1.4.1 Querying the LMP Discovery Type.....................................................................................................1-43
1.4.2 Disabling the LMP Protocol.................................................................................................................1-44
1.4.3 Disabling the OSPF Protocol...............................................................................................................1-44
1.4.4 Encrypting the OSPF Protocol.............................................................................................................1-45
Operation Guide for WDM ASON Network Management Contents
vii
1.4.5 Encrypting RSVP.................................................................................................................................1-46
1.4.6 Creating Out-Fiber Control Channels..................................................................................................1-47
1.5 Managing Link Resources.............................................................................................................................1-49
1.5.1 Synchronizing Control Links Networkwide........................................................................................1-50
1.5.2 Synchronizing TE Links.......................................................................................................................1-51
1.5.3 Viewing TE Links................................................................................................................................1-52
1.5.4 Configuring the Link Distance.............................................................................................................1-53
1.5.5 Setting the Usage Threshold of WDM Fiber Resources......................................................................1-54
1.5.6 Creating an SRLG................................................................................................................................1-54
1.5.7 Setting the Custom Cost of the TE Link .............................................................................................1-55
1.5.8 Querying Resource Occupation Status.................................................................................................1-56
1.5.9 Setting Resource Reservation...............................................................................................................1-56
1.5.10 Creating a Virtual TE Link.................................................................................................................1-57
1.5.11 Deleting an Interrupted TE Link Manually........................................................................................1-60
1.6 Managing SRGs............................................................................................................................................1-60
1.6.1 Creating an SRG...................................................................................................................................1-61
1.6.2 Querying the SRG Related to a TE Link..............................................................................................1-63
1.6.3 Querying the SRG Related to an ASON NE........................................................................................1-64
1.7 Creating WDM ASON Trails........................................................................................................................1-64
1.7.1 Synchronizing WDM ASON Trails.....................................................................................................1-67
1.7.2 Creating an Optical-Layer Diamond WDM ASON OCh Trail............................................................1-68
1.7.3 Creating an Optical-Layer Silver WDM ASON OCh Trail.................................................................1-72
1.7.4 Creating an Optical-Layer Copper WDM ASON OCh Trail...............................................................1-76
1.7.5 Creating an Electrical-Layer Diamond WDM ASON ODU0 Trail.....................................................1-79
1.7.9 Creating an Electrical-Layer Diamond WDM ASON Client Trail......................................................1-98
1.7.10 Creating an Electrical-Layer Gold WDM ASON ODU1 Trail........................................................1-102
1.7.11 Creating an Electrical-Layer Gold WDM ASON ODU2 Trail........................................................1-107
1.7.12 Creating an Electrical-Layer Silver WDM ASON ODU0 Trail......................................................1-110
1.7.16 Creating an Electrical-Layer Silver WDM ASON Client Trail.......................................................1-127
1.7.17 Creating an Electrical-Layer Copper WDM ASON ODU0 Trail....................................................1-131
1.7.21 Creating an Electrical-Layer Copper WDM ASON Client Trail.....................................................1-146
1.7.22 Creating a WDM ASON OCh Trail at the Optical Layer for an Explicit Optical Regenerator.......1-149
1.7.23 Creating WDM ASON Inverse Multiplexing Trail..........................................................................1-155
Contents
viii Huawei Proprietary and Confidential
Issue 02 (2010-09-24)
1.7.24 Creating Two Associated WDM ASON Trails................................................................................1-157
1.7.25 Setting Association of WDM ASON Trails.....................................................................................1-160
1.7.26 Creating WDM ASON Trails in Batches.........................................................................................1-161
1.7.27 Deactivating the WDM ASON Trail................................................................................................1-164
1.7.28 Deleting an ASON Trail...................................................................................................................1-165
1.8 Modifying the Attributes of ASON WDM Trails.......................................................................................1-165
1.8.1 Viewing WDM ASON Trail Attributes.............................................................................................1-166
1.8.2 Viewing the Optical Power of a WDM ASON Trail.........................................................................1-167
1.8.3 Setting the Routing Attributes............................................................................................................1-168
1.8.4 Setting the Scheduled Reversion Time..............................................................................................1-169
1.8.5 Setting the SD Alarm to Trigger Rerouting.......................................................................................1-170
1.8.6 Setting Preset Restoration Trail..........................................................................................................1-171
1.8.7 Setting the Original Route..................................................................................................................1-172
1.9 Modifying the Route of an ASON Service.................................................................................................1-172
1.9.1 Reverting the WDM ASON OCh Trail Manually.............................................................................1-173
1.9.2 Reverting A WDM ASON Trail to the Original Route.....................................................................1-173
1.9.3 Optimizing a WDM ASON OCh Trail..............................................................................................1-174
1.9.4 Optimizing WDM ASON ODUk Trail..............................................................................................1-175
1.9.5 Optimizing WDM ASON Client Trail...............................................................................................1-176
1.10 Migrating WDM ASON Trails.................................................................................................................1-177
1.10.1 Downgrading a WDM ASON Trail to a Traditional WDM Trail....................................................1-178
1.10.2 Upgrading a Traditional WDM Trail to an WDM ASON Trail.......................................................1-179
1.10.3 Migration Between the Diamond and Silver or Copper WDM ASON Trails.................................1-181
1.10.4 Migration Between the Gold and Silver or Copper WDM ASON Trails........................................1-182
1.10.5 Migration Between the Silver and Copper WDM ASON Trails.....................................................1-183
1.11 Creating Services Between an ASON NE and a Traditional NE..............................................................1-183
1.11.1 Creating a OCh Trail Between Traditional NEs that Cross an ASON Domain...............................1-185
1.11.2 Creating a ODU0 Trail Between Traditional NEs that Cross an ASON Domain............................1-190
1.11.5 Creating a Client Trail Between Traditional NEs that Cross an ASON Domain.............................1-203
1.11.6 Creating a OCh Trail Between a Traditional NE and an ASON NE...............................................1-207
1.11.7 Creating a ODU0 Trail Between a Traditional NE and an ASON NE............................................1-212
1.11.10 Creating a Client Trail Between a Traditional NE and an ASON NE...........................................1-224
1.11.11 Creating 1+1 OCh Trails Between Traditional NEs That Cross an ASON Domain.....................1-228
1.11.12 Creating 1+1 ODU0 Trails Between Traditional NEs That Cross an ASON Domain..................1-234
1.11.15 Creating 1+1 Client Trails Between Traditional NEs That Cross an ASON Domain...................1-251
1.11.16 Creating the 1+1 OCh Trails Between a Traditional NE and an ASON NE.................................1-257
ix
1.11.17 Creating the 1+1 ODU0 Trails Between a Traditional NE and an ASON NE..............................1-262
1.11.20 Creating the 1+1 Client Trails Between a Traditional NE and an ASON NE...............................1-283
1.11.21 Creating Client Trail between ASON NE and Traditional NE......................................................1-290
1.12 Managing Services Between an WDM ASON NE and a Conventional WDM NE.................................1-295
1.12.1 Searching for WDM Trails Crossing the ASON Domain................................................................1-295
1.12.2 Querying the ASON Trails Related to the Traditional WDM Trail.................................................1-296
1.12.3 Setting the Span ID of the ASON-WDM Trail................................................................................1-296
1.13 Importing and Exporting Data...................................................................................................................1-297
1.13.1 Exporting Data from U2000 to MDS...............................................................................................1-297
1.13.2 Importing Data from MDS to U2000...............................................................................................1-298
1.14 Managing the OVPN Customers and OVPN Services..............................................................................1-299
1.14.1 Enabling OVPN Function of ASON NE..........................................................................................1-300
1.14.2 Creating NM User for OVPN Customer..........................................................................................1-301
1.14.3 Creating an OVPN Customer...........................................................................................................1-303
1.14.4 Allocating Optical-Layer TE Links to an OVPN Customer............................................................1-304
1.14.5 Creating OVPN Services in ASON Domain....................................................................................1-306
1.14.6 Creating an OVPN OCh trail between ASON NE and Traditional NE...........................................1-310
1.14.7 Setting the OVPN Customer for an ASON Trail.............................................................................1-314
1.14.8 Querying TE Link Resources of an OVPN Customer.....................................................................1-315
1.14.9 Querying the WDM ASON Trails of the OVPN Customers...........................................................1-316
1.15 Managing Control Plane Alarms and Performance Events.......................................................................1-317
1.15.1 Querying Control Plane Alarms.......................................................................................................1-318
1.15.2 Setting the Severity of Control Plane Alarm....................................................................................1-319
1.15.3 Setting the Auto-Report Status of the Control Plane Alarm............................................................1-319
1.15.4 Suppressing Control Plane Alarms..................................................................................................1-320
1.15.5 Suppressing Control Plane Alarm Events........................................................................................1-321
1.15.6 Querying the Performance of the Control Plane..............................................................................1-321
1.15.7 Monitoring the Control Plane Performance.....................................................................................1-322
1.15.8 Setting the Auto-Report Status of the Control Plane Performance Data.........................................1-323
1.15.9 Setting the Control Plane Performance Threshold ..........................................................................1-323
2 Routine Maintenance for an ASON Network......................................................................2-1
2.1 Precautions for Routine Maintenance.............................................................................................................2-2
2.2 Routine Maintenance Items.............................................................................................................................2-4
2.2.1 Periodically Refreshing the ASON information....................................................................................2-5
2.2.2 Querying Network-Wide Alarms...........................................................................................................2-6
2.2.3 Querying ASON Trail Alarms...............................................................................................................2-7
2.2.4 Querying Control Plane Alarms.............................................................................................................2-7
2.2.5 Querying Control Link Alarms..............................................................................................................2-8
2.2.6 Querying TE Link Alarms......................................................................................................................2-8
2.2.7 Query the Interrupted TE Link...............................................................................................................2-9
Contents
x Huawei Proprietary and Confidential
Issue 02 (2010-09-24)
2.2.8 Creating a Performance Filtering Template.........................................................................................2-10
2.2.9 Querying the Performance of the Control Plane..................................................................................2-10
2.2.10 Querying Abnormal ASON Events....................................................................................................2-11
2.2.11 Checking the Running Status of ASON Trails...................................................................................2-12
2.2.12 Checking TE Links.............................................................................................................................2-13
2.2.13 Checking Control Links.....................................................................................................................2-14
3 Handling ASON Network Failures........................................................................................3-1
3.1 Handling Link Failures....................................................................................................................................3-2
3.1.1 Handling Impassable Control Channels.................................................................................................3-2
3.1.2 Handling Impassable TE Links..............................................................................................................3-3
3.1.3 Handling Downgraded TE Links........................................................................................................... 3-4
3.2 Handling the Failure in Creating Trails...........................................................................................................3-5
3.2.1 Handling the Failure of Route Computation..........................................................................................3-5
3.2.2 Handling the Failure of Label Allocation.............................................................................................. 3-6
3.2.3 Handling the Cross-Connection Configuration Failure......................................................................... 3-6
3.3 Handling Trail Interruption.............................................................................................................................3-7
3.3.1 Identifying the Interrupted trails............................................................................................................ 3-7
3.3.2 Handling the Fault of Trail Interruption.................................................................................................3-8
xi
Figures
Figure 1-1 Three planes of the ASON..................................................................................................................1-5
Figure 1-2 WDM ASON Trail.............................................................................................................................1-6
Figure 1-3 Function structure of the ASON.........................................................................................................1-8
Figure 1-4 ASON NE...........................................................................................................................................1-8
Figure 1-5 Creating control channels.................................................................................................................1-10
Figure 1-6 Verifying component links and TE links..........................................................................................1-10
Figure 1-7 OTU3 TE link and ODU3 TE link...................................................................................................1-13
Figure 1-10 ODU1 TE link................................................................................................................................1-15
Figure 1-11 OTU5 TE link and ODU5 TE link.................................................................................................1-15
Figure 1-12 Diamond Services...........................................................................................................................1-17
Figure 1-13 Gold WDM ASON trail..................................................................................................................1-22
Figure 1-14 A silver service...............................................................................................................................1-24
Figure 1-15 Networking diagram of an OVPN..................................................................................................1-27
Figure 1-16 Partitioning the TE link resources..................................................................................................1-28
Figure 1-17 Creating out-fiber control channels................................................................................................1-48
Figure 1-18 SRLG schematic diagram...............................................................................................................1-55
Figure 1-19 Virtual TE link................................................................................................................................1-57
Figure 1-20 Board configuration for NE3 and NE4...........................................................................................1-58
Figure 1-21 Board configuration for NE5..........................................................................................................1-59
Figure 1-22 Schematic diagram of the physical topology of an SRG................................................................1-62
Figure 1-23 Schematic diagram of the topology of the TE links in an SRG......................................................1-62
Figure 1-24 Diamond WDM ASON OCh Trail requirement.............................................................................1-69
Figure 1-26 Silver WDM ASON OCh Trail requirement..................................................................................1-73
Figure 1-28 Copper WDM ASON OCh Trail requirement................................................................................1-77
Figure 1-30 Service Requirements.....................................................................................................................1-80
Figure 1-32 Service Requirements.....................................................................................................................1-85
Figure 1-33 Diamond WDM ASON ODU1 trail...............................................................................................1-85
Operation Guide for WDM ASON Network Management Figures
xiii
Figure 1-35 Service requirements...................................................................................................................... 1-89
Figure 1-42 Diamond WDM ASON Client trail................................................................................................1-99
Figure 1-44 Gold WDM ASON ODU1 trail requirement................................................................................1-103
Figure 1-45 Gold WDM ASON ODU1 trail....................................................................................................1-103
Figure 1-46 Board configuration for NE1 and NE3.........................................................................................1-104
Figure 1-47 Gold WDM ASON ODU2 trail requirement................................................................................1-107
Figure 1-49 Silver WDM ASON ODU0 Trail requirement.............................................................................1-111
Figure 1-51 Silver WDM ASON ODU1 Trail requirement.............................................................................1-115
Figure 1-52 Silver WDM ASON ODU1 trail..................................................................................................1-116
Figure 1-54 Silver WDM ASON ODU2 trail requirements.............................................................................1-120
Figure 1-57 Silver WDM ASON ODU3 trail requirements.............................................................................1-124
Figure 1-59 Silver WDM ASON Client trail requirements.............................................................................1-128
Figure 1-60 Silver WDM ASON Client trail...................................................................................................1-128
Figure 1-62 Copper service requirements........................................................................................................1-132
Figure 1-64 Copper service requirements........................................................................................................1-136
Figure 1-65 Copper WDM ASON ODU1 trail................................................................................................1-136
Figure 1-67 Service requirements....................................................................................................................1-139
Figure 1-74 Copper WDM ASON Client trail.................................................................................................1-147
Figures
xiv Huawei Proprietary and Confidential
Issue 02 (2010-09-24)
Figure 1-76 Requirements of a WDM ASON OCh trail Traversing an Optical Regenerator.........................1-150
Figure 1-77 Board configuration for NE1, NE2 and NE3................................................................................1-151
Figure 1-78 Copper service requirement..........................................................................................................1-155
Figure 1-79 Inverse multiplexing trail..............................................................................................................1-155
Figure 1-81 Two Associated ASON Trails .....................................................................................................1-158
Figure 1-82 Batch silver service requirement..................................................................................................1-162
Figure 1-84 OCh trail requirement between traditional NEs...........................................................................1-185
Figure 1-85 Board configuration for NE1-NE4...............................................................................................1-186
Figure 1-87 ODU0 trail requirement between traditional NEs........................................................................1-190
Figure 1-96 Client trail requirement between traditional NEs.........................................................................1-203
Figure 1-99 OCh trail requirement between traditional and ASON NEs.........................................................1-207
Figure 1-100 Board configuration for NE1-NE4.............................................................................................1-208
Figure 1-101 Board configuration for NE5 and NE6.......................................................................................1-209
Figure 1-102 ODU0 trail requirement between traditional and ASON NEs....................................................1-212
Figure 1-111 Client trail requirement between traditional and ASON NEs....................................................1-224
Figure 1-114 1+1 OCh trail requirement between traditional NEs..................................................................1-228
Figure 1-117 1+1 ODU0 trail requirement between traditional NEs...............................................................1-234
Operation Guide for WDM ASON Network Management Figures
xv
Figure 1-126 1+1 Client trail requirement between traditional NEs................................................................1-252
Figure 1-129 1+1 OCh Trails requirement between a traditional NE and an ASON NE................................1-257
Figure 1-132 1+1 ODU0 Trail requirement between a traditional NE and an ASON NE...............................1-263
Figure 1-141 1+1 Client Trail requirement between a traditional NE and an ASON NE...............................1-284
Figure 1-144 Client trail requirement between traditional NE and ASON NE................................................1-291
Figure 1-147 OVPN service requirements.......................................................................................................1-307
Figure 1-148 Board configuration of NE1 and NE3........................................................................................1-307
Figure 1-149 OVPN ASON-WDM OCh trail requirements............................................................................1-311
Figures
xvi Huawei Proprietary and Confidential
Issue 02 (2010-09-24)
Tables
Table 1-1 Service level.......................................................................................................................................1-16
Table 1-2 TE links used by WDM ASON trails.................................................................................................1-16
Table 1-3 Attributes of the permanent 1+1 diamond services............................................................................1-18
Table 1-4 Attributes of the rerouting 1+1 diamond service...............................................................................1-19
Table 1-5 Attributes of the non-rerouting 1+1 diamond service........................................................................1-21
Table 1-6 Attributes of gold WDM ASON trail.................................................................................................1-22
Table 1-7 Attributes of silver services................................................................................................................1-24
Table 1-8 Attributes of copper services..............................................................................................................1-26
Table 1-9 OVPN service attributes.....................................................................................................................1-28
Table 1-10 Risk cause analysis...........................................................................................................................1-63
Table 1-11 SRGs for pipes.................................................................................................................................1-63
Table 1-12 Diamond WDM ASON OCh Trail planning...................................................................................1-70
Table 1-13 Silver WDM ASON OCh Trail planning.........................................................................................1-74
Table 1-14 Copper WDM ASON OCh trail planning........................................................................................1-77
Table 1-15 Diamond WDM ASON ODU0 trail planning..................................................................................1-81
Table 1-19 Diamond WDM ASON client trail planning.................................................................................1-100
Table 1-20 Gold WDM ASON ODU1 trail planning.......................................................................................1-104
Table 1-21 Gold WDM ASON ODU2 trail planning.......................................................................................1-108
Table 1-22 Silver WDM ASON ODU0 Trail planning....................................................................................1-112
Table 1-23 Silver WDM ASON ODU1 Trail planning....................................................................................1-117
Table 1-24 Silver WDM ASON ODU2 trail planning.....................................................................................1-121
Table 1-25 Silver WDM ASON ODU3 trail planning.....................................................................................1-125
Table 1-26 Silver WDM ASON Client trail planning......................................................................................1-129
Table 1-27 Copper WDM ASON ODU0 trail planning...................................................................................1-133
Table 1-31 Copper WDM ASON Client trail planning....................................................................................1-148
Table 1-32 Plan of a WDM ASON OCh trail traversing an optical regenerator..............................................1-151
Table 1-33 Inverse multiplexing trail planning................................................................................................1-156
Operation Guide for WDM ASON Network Management Tables
xvii
Table 1-34 Silver service planning...................................................................................................................1-162
Table 1-35 OCh trail planning between NE1 and NE4....................................................................................1-187
Table 1-36 Optical Cross-Connection planning for NE5 and NE6..................................................................1-188
Table 1-37 ODU0 trail planning between traditional NEs...............................................................................1-193
Table 1-40 Client trail planning between traditional NEs................................................................................1-205
Table 1-41 Silver ASON Trail planning between NE1 and NE4.....................................................................1-209
Table 1-42 Optical Cross-Connection planning of NE5..................................................................................1-210
Table 1-43 ODU0 trail planning between traditional NE and ASON NE........................................................1-215
Table 1-46 Client trail planning between traditional NE and ASON NE.........................................................1-226
Table 1-47 Planning of Two Silver ASON Trails............................................................................................1-230
Table 1-48 Intra-Board 1+1 Protection planning of NE5.................................................................................1-231
Table 1-49 Intra-Board 1+1 Protection planning of NE6.................................................................................1-231
Table 1-51 SNCP service planning of NE5......................................................................................................1-237
Table 1-62 Service planning for the two silver ASON trails...........................................................................1-259
Table 1-63 1+1 Protection Planning of NE5....................................................................................................1-260
Table 1-65 SNCP service planning for NE5....................................................................................................1-266
Table 1-67 Service planning for NE3 and NE4................................................................................................1-267
Tables
xviii Huawei Proprietary and Confidential
Issue 02 (2010-09-24)
Table 1-80 Client trail planning between traditional NE and ASON NE.........................................................1-293
Table 1-81 Silver WDM ASON OCh Trail planning.......................................................................................1-308
Table 1-82 Silver OVPN ASON-WDM OCh Trail planning...........................................................................1-312
Operation Guide for WDM ASON Network Management Tables
xix
1 Configuring WDM ASON Networks
About This Chapter
You can configure an ASON network using the U2000.
1.1 WDM ASON Network Configuration
This section describes how to configure an ASON network on the U2000.
1.2 ASON
The automatically switched optical network (ASON) is a new generation optical transmission
network. An ASON NE refers to the equipment that has ASON features. An ASON NE also has
the features of traditional WDM NEs besides the ASON features. The U2000 manages the ASON
network by integrating the ASON features with the WDM features.
1.3 Creating an ASON Topology
The ASON network uses the route protocol to create the topology information of the nodes in
the network so that each node can obtain a networkwide topology.The U2000 can discover other
ASON NEs in the network from any ASON NE.
1.4 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.
1.5 Managing Link Resources
As the network is growing larger, a reasonable way of resource management is required to make
the most of the network resources and to improve the network efficiency. ASON links are
composed of control channels, control links and TE links.
1.6 Managing SRGs
The TE links in the same optical cable, NE, site, and pipe have the same risk. You can find a
balance point between management costs and risk control, determine the risks to be managed,
and manage the risks by means of SRGs.
1.7 Creating WDM ASON Trails
The trail levels that an WDM ASON 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.
1.8 Modifying the Attributes of ASON WDM Trails
Operation Guide for WDM ASON Network Management 1 Configuring WDM ASON Networks
1-1
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.
1.9 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.
1.10 Migrating WDM ASON Trails
An ASON network supports the migration between traditional trails and ASON trails, and
supports the in-line migration between ASON trails at different levels.
1.11 Creating Services Between an ASON NE and a Traditional NE
A network can consist of ASON NEs and traditional NEs. This realizes end-to-end service
configuration and management.
1.12 Managing Services Between an WDM ASON NE and a Conventional WDM NE
A network can consist of WDM ASON NEs and conventional WDM NEs. This realizes end-
to-end service configuration and management.
1.13 Importing and Exporting Data
The existing ASON network may not be optimum, so we can use the OptiX Modeling and Design
System (MDS) to optimize the network. You can import the ASON data on the U2000 to the
MDS, and use the MDS to plan the imported ASON data and work out the optimum solution.
You can import a better planning scheme to the U2000. Then, use the U2000 to apply the settings
to NEs to optimize the existing ASON network.
1.14 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.
1.15 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.
1-2 Huawei Proprietary and Confidential
Issue 02 (2010-09-24)
1.1 WDM ASON Network Configuration
This section describes how to configure an ASON network on the U2000.
To configure an ASON network, the traditional network must run normally, and the ASON
software must be enabled and runs normally after commissioning. For details about the
commissioning and planning of an ASON network, refer to the ASON User Guide.
To configure an ASON network by using the U2000, do as follows:
Step Description Remarks
1 Create a GNE Create the ASON NE
connected with the U2000 as
a GNE.
2 Uploading NE
Configuration Data
Upload data to the U2000 to
ensure that the data on the
U2000 is consistent with that
on the NE.
3 Creating Domains for an
ASON Network
Create an ASON domain and
assign the ASON NEs that
belong to the same ASON
network to the ASON
domain.
4 Setting the Primary NE or
Secondary NE
To improve the reliability,
another NE can be set as the
standby of the primary NE.
5 Synchronize data
networkwide. The U2000
searches for ASON NEs and
displays them in the topology
view.
6 Create Fibers Inside an
Optical NE and Between
Optical NEs
Fibers inside an optical NE
can be created manually or
synchronized in batches for
creation.
Fibers between optical NEs
can be created manually or by
TE link.
7 Managing Link Resources A more reasonable way of
resource management is
required to make the most of
the network resources and to
improve the network
efficiency.
1-3
Step Description Remarks
8 Creating WDM ASON
Trails
The U2000 provides the end-
to-end WDM ASON trail
management feature.
9 Routine Maintenance
Items
View alarms and abnormal
events.

1.2 ASON
The automatically switched optical network (ASON) is a new generation optical transmission
network. An ASON NE refers to the equipment that has ASON features. An ASON NE also has
the features of traditional WDM NEs besides the ASON features. The U2000 manages the ASON
network by integrating the ASON features with the WDM features.
1.2.1 Basic Concepts of ASON
The basic concepts related to the ASON are the three planes, label switched path (LSP) and
rerouting.
1.2.2 Function Structure of the ASON
An ASON network consists of ASON NEs, TE links, domains and SPC (soft permanent
connections).
1.2.3 ASON Protocol
Huawei OptiX GCP applies the link management protocol (LMP) as the link management
protocol, OSPF-TE as the routing protocol, and RSVP-TE as the signaling protocol.
1.2.4 ASON Links
ASON Links include control channels, control links, and TE links.
1.2.5 SLA
The ASON network can provide services of different QoS to different clients.
1.2.6 Diamond WDM ASON Trail
Diamond WDM ASON trails have the best protection ability. When there are enough resources
in the network, diamond WDM ASON trails provide a permanent 1+1 protection. Diamond
services are applicable to voice and data services, VIP private line, such as banking, security
and aviation.
1.2.7 Gold WDM ASON Trail
Gold WDM ASON trails are applicable to voice and significant data services. The gold WDM
ASON trails are classified into ODU1 trail and ODU2 trail. Compared with diamond services,
gold services have greater bandwidth utilization.
1.2.8 Silver WDM ASON Trail
Silver WDM ASON services, including WDM ASON OCh trails, ODU0, ODU1 trails, ODU2
trails and Client 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.
1.2.9 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, ODU0 trail, ODU1 trail, ODU2 trail, and Client trail.
Issue 02 (2010-09-24)
1.2.10 OVPN
The optical virtual private network (OVPN) divides the TE link resources in an ASON network
to different customers. Sharing the fiber resources, the customers, however, can use and manage
only their own TE links and ASON services.
1.2.1 Basic Concepts of ASON
The basic concepts related to the ASON are the three planes, label switched path (LSP) and
rerouting.
As shown in Figure 1-1, the ASON has three planes: the control plane, the transport plane, and
the management plane.
Figure 1-1 Three planes of the ASON
Control plane
Transmission plane
Management
plane

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.
Control Plane
The control plane consists of a group of communication entities. It is responsible for the calling
control and connection control, including automatic setting up, releasing, monitoring, and
maintaining connections. The control plane automatically restores the failed connections through
signaling exchange.
1-5
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.
Management Plane
The management plane is a complement to the control plane. It maintains the transport plane,
the control plane and the whole system. It can configures end to end service. Its functions include
performance management, fault management, configuration management and security
management.
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, WDM ASON ODU2 Trail, WDM
ASON ODU1 Trail, , WDM ASON ODU0 Trail, WDM ASON Client Trail. See Figure 1-2.
NOTE
l OptiX OSN 3800 and OptiX OSN 6800 support WDM ASON Client Trail.
l OptiX OSN 8800 series support WDM ASON ODU0 Trail.
l The WDM ASON OCh trail can be created when there are sufficient OCh TE link resources.
l The WDM ASON ODU0 trail can be created when there are sufficient TE link resources
where the payload type is ODU0.
l The WDM ASON Client trail can be created when there are sufficient TE link resources
where the payload type is GE or Any.
Figure 1-2 WDM ASON Trail
Client trail
OCh trail
ODU0/ODU1/ODU2 trail
OTU OM OA OA OD OTU
Issue 02 (2010-09-24)

Rerouting
Rerouting is a means of resuming services. 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.
CAUTION
After a revertive service reroutes, the original LSP is not deleted.
Rerouting Lockout
In some cases, rerouting is not required after failure of LSP. Then you need to set rerouting
lockout.
Rerouting Policy
Diamond, gold and silver services all support the four rerouting polices.
l Use existing trails whenever possible: During rerouting, the route of the new LSP overlaps
the original route whenever possible.
l Do not use existing trails whenever possible: During rerouting, the route of the new LSP
is separated from the original route whenever possible.
l No Rerouting constraint: During rerouting, the best route is computed for the new LSP.
l Use simulated section restoration: There are several TE links between two nodes, but the
service only passes one of the links. When a fiber cut occurs in the link that carries the
service, the service can first be switched to one of the other available TE links between the
two nodes.
1.2.2 Function Structure of the ASON
An ASON network consists of ASON NEs, TE links, domains and SPC (soft permanent
connections).
See Figure 1-3.
1-7
Figure 1-3 Function structure of the ASON
R1
R2
R3
R4
ASON NE
SPC
ASON domain
TE link
: 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-4.
Figure 1-4 ASON NE
Link management protocol ( LMP )
WDM-side/Client-
side interface
WDM-side/Client-
side interface
Communication and control
Traditional NE
ASON NE
Wavelength
grooming
Signaling
( RSVP-TE )
Routing
( OSPF-TE )

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.
Issue 02 (2010-09-24)
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 be divided into working resource and protection resources, while those 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.
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
audience="nmason"
iManager U2000 only supports SPC and PC. SC is not supported at present.
1.2.3 ASON Protocol
Huawei OptiX GCP 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-5. When two adjacent ASON NEs start up, the LMP uses the Ethernet or
the D4-D12 bytes of DCC 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
1-9
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-5 Creating control channels
Node 1 Node 2
Message
Message
LMP LMP

l Verifying component links and TE links.
The following is the procedure of verifying component links and TE Links.
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.
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-6, 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-6 Verifying component links and TE links
Node 1
Node 2
Message
Message
LMP LMP

Issue 02 (2010-09-24)
OSPF-TE
The control plane of Huawei OptiX GCP applies the OSPF-TE, which is an extended protocol
for OSPF, and performs the following functions.
l Creates neighbor relations.
l Creates and maintains control links.
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 Encryption
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
encrypt protocols. In an ASON domain, the RSVP and OSPF-TE protocols are encrypted for
authentication.
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.
The check succeeds only when the authentication modes and passwords of adjacent nodes are
the same.
UNI Protocol
The UNI is the standard interface for connecting the transmission network and the client
equipment. Currently, there are two schemes, namely, OIF and GMPLS. The equipment supports
the following UNI interface functions:
1-11
l Establishes the SDH UNI service.
l Establish the Ethernet UNI service.
l Deletes the SDH UNI service.
l Deletes the Ethernet UNI service.
l UNI Access Policy and Security Policy Management
1.2.4 ASON Links
ASON Links include control channels, 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.
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 are 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.
TE Links
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. The TE link is a concept
of resources. Different boards generate different TE links. By link signal type, TE links can be
classified into the following types:
l OMS/OTS TE link
l OTU3 TE link and ODU3 TE link
Issue 02 (2010-09-24)
l OTU5G TE link and ODU5G TE link
See Figure 1-7. After the wavelength trail is created between the FIU boards at two ASON NEs,
the OMS/OTS TE link is generated automatically.
See Figure 1-7. 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 signal type of the OTU3
TE link is OTU3 and the payload type is ODU3. The signal type of the ODU3 TE link is ODU3
and the payload type is ODU2.
Figure 1-7 OTU3 TE link and ODU3 TE link
O
D
U
3
O
T
U
3
OCh TE link
OTU3 TE link
NS3
NE1
F
I
U
O
S
C
O
D
U
3
O
T
U
3
NE2
F
I
U
O
S
C
ODU3 TE link
ODU2
NS3
ODU2
ODU2
ODU2
ODU2
ODU2
ODU2
ODU2

See Figure 1-8. 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 signal type of the OTU2
TE link is OTU2 and the payload type is ODU2. The signal type of the ODU2 TE link is ODU2
and the payload type is ODU1. See Figure 1-8.
1-13
O
D
U
2
O
T
U
2
OCh TE link
OTU2 TE link
NS2
NE1
F
I
U
O
S
C
O
D
U
2
O
T
U
2
NS2
NE2
F
I
U
O
S
C
ODU2 TE link
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1

See Figure 1-9. After the wavelength trail is created between the LQMS boards at two ASON
NEs, the OTU1 TE link and ODU1 TE link are generated automatically. The signal type of the
OTU1 TE link is OTU1 and the payload type is ODU1. The signal type of the ODU1 TE link
is ODU1 and the payload type is GE/Any.
O
D
U
1
O
T
U
1
OCh TE link
OTU1 TE link
LQMS
NE1
F
I
U
O
S
C
O
D
U
1
O
T
U
1
NE2
F
I
U
O
S
C
ODU1 TE link
Any
Any
Any
Any
Any
Any
Any
Any
LQMS

Issue 02 (2010-09-24)
See Figure 1-10, The ODU1 TE link will be automatically created only after the ODU2 TE link
generates, and the cross-connection between the TQSTOM and NS2 boards is created. When
the accessed signal is STM-16/OC-48, the ODU1 TE link will be automatically created, the
signal type of which is ODU1 and the payload type is Any.
Figure 1-10 ODU1 TE link
LP1 ODU1 LP1 ODU1
O
D
U
1
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
O
D
U
1
ODU2 TE link
ODU1 TE link
NS2 TQS TQS
NS2
NE1 NE3
ODU1
XCS
XCS
ODU1

See Figure 1-11. After the wavelength trail is created between the L4G boards at two ASON
NEs, the OTU5G TE link and ODU5G TE link are generated automatically. The signal type of
the OTU5G TE link is OTU5G and the payload type is ODU5G. The signal type of the ODU5G
TE link is ODU5G and the payload type is GE.
OCh TE link
OTU5G TE link
L4G
NE1
F
I
U
O
S
C
NE2
F
I
U
O
S
C
ODU5G TE link
GE
GE
GE
GE
GE
GE
GE
GE
L4G
O
D
U
5
G
O
T
U
5
G
O
D
U
5
G
O
T
U
5
G

1-15
1.2.5 SLA
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-1. The rerouting time is related to the device type, interrupted service,
network resource and setting. The data are listed as follows only for reference.
Table 1-1 Service level
Service Protection
and
Restoration
Scheme
Implementati
on Means
Switching
Time
Rerouting
Time
Diamond
service
Protection and
restoration
intra-board 1+1
protection,
ODUk SNCP,
SW SNCP and
rerouting
Less than 50ms The rerouting
time varies with
the network
size, capacity
and service
types. For the
typical scenario
of a four-NE
mesh network
transmitting no
more than 40
wavelengths,
the rerouting
time is counted
in seconds.
Gold service Protection and
restoration
ODUk SPRing
protection and
rerouting
Less than 50ms
Silver service Restoration Rerouting -
Copper service No protection
No restoration
- - -

Table 1-2 lists details of the TE links used by ASON services.
Table 1-2 TE links used by WDM ASON trails
Service Level Working Resource
of TE Link
Protection
Resource of TE
Link
Non-Protection
Resource of TE
Link
Diamond service Not used Not used Used
Gold service Used with the
priority
Not used Used when the
resource is not
enough
Silver service Not used Not used Used
Copper service Not used Not used Used

Issue 02 (2010-09-24)
1.2.6 Diamond WDM ASON Trail
Diamond WDM ASON trails have the best protection ability. When there are enough resources
in the network, diamond WDM ASON trails 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-12 shows a diamond service.
Figure 1-12 Diamond Services
R1
R2
R3
R4
A
B
C
D
E
F
G
H
I
: ASON NE
: User equipment
Working LSP
Protection LSP

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-3 lists the attributes of the permanent 1+1 diamond service.
Table 1-4 lists the attributes of the rerouting 1+1 diamond service.
Table 1-5 lists the attributes of the non-rerouting 1+1 diamond service.
1-17
Table 1-3 Attributes of the permanent 1+1 diamond services
Attribute Permanent 1+1 Diamond Service
Requirements for creation Sufficient non-protection resources are available between the
source node and the sink node.
Protection type For WDM ASON OCh trail: supports intra-board 1+1 protection.
(The protection schemes are OTU intra-board dual-feed and
OTU+OLP/DCP dual-feed.)
For WDM ASON ODUk trail: supports ODUk SNCP
For WDM ASON Client trail: supports SW SNCP
Protection and restoration l If the resources are sufficient, two LSPs are always available
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 LSP can still be
reserved for a permanent 1+1 diamond service to ensure the
service survivability.
Rerouting l Supports setting the revertive mode.
l Supports setting the WTR time.
l Supports setting revertive lockout.
l Supports rerouting lockout.
l Supports setting the rerouting priority.
l Supports setting the crankback times.
l Supports rerouting triggered by SD.
l Supports setting the trigger condition.
l Supports setting the rerouting hold-off time.
l Supports three rerouting policies:
Use existing trails whenever possible
Do not use existing trails whenever possible
No rerouting constraint
Use simulated section restoration
Issue 02 (2010-09-24)
Attribute Permanent 1+1 Diamond Service
Revertive The WDM ASON ODUk or Client trail supports Automatically
Revertive, Non-Revertive, and Scheduled revertive.
The WDM ASON OCh trail supports Non-Revertive, and
Scheduled revertive, not supports Automatically 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.
Preset restoring trail Supports setting the preset restoring trail.
Service migration l Supports migration between diamond WDM ASON trails and
traditional 1+1 WDM trails.
l Migration between optical-layer WDM ASON OCh trails is
not supported.
l Supports migration between electrical-layer diamond WDM
ASON trails and silver WDM ASON trails.
ASON trails and copper WDM ASON trails.
Service switching Supports manual switching.
Service optimization Supports manual service optimization.

Table 1-4 Attributes of the rerouting 1+1 diamond service
Attribute Rerouting 1+1 Diamond Service
1-19
Protection and restoration l When the standby LSP fails, services are not switched.
Rerouting is 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.
l Supports setting the trigger condition.
rectified.
Issue 02 (2010-09-24)
not supported.

Table 1-5 Attributes of the non-rerouting 1+1 diamond service
Attribute Non-rerouting 1+1 diamond service
Protection and restoration l When the active LSP fails, services are switched to the
standby LSP 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.
not supported.

1-21
1.2.7 Gold WDM ASON Trail
Gold WDM ASON trails are applicable to voice and significant data services. The gold WDM
ASON trails are classified into ODU1 trail and ODU2 trail. Compared with diamond services,
gold services have greater bandwidth utilization.
A gold WDM ASON trail needs only one LSP. This LSP must use working resource of TE links
or non-protection resource of TE links. When the ODUk SPRing endures a fiber cut at the first
time, the ODUk SPRing protection switching is triggered to protect the gold services. Rerouting
is performed to restore the services if the ODUk SPRing protection switching fails.
As shown in Figure 1-13, a gold service can be configured from A to I.
Figure 1-13 Gold WDM ASON trail
ODUk
SPRing
R1
R2
R3
R4
:ASON NE
:User equipment
A
B
C
D
E
F
G
H
I
ODUk
SPRing
ODUk
SPRing

Table 1-6 lists the attributes of gold services.
Table 1-6 Attributes of gold WDM ASON trail
Attribute Gold WDM ASON trail
Requirements for creation Sufficient working resources or non-protection resources are
available between the source node and the sink node.
ODUk SPRing Supports using the working resources of the ODUk SPRing to
create gold services.
Protection and restoration When a fiber is cut for the first time, ODUk SPRing switching
is performed to protect services. When ODUk SPRing switching
fails, rerouting is then triggered to restore services.
Issue 02 (2010-09-24)
Attribute Gold WDM ASON trail
Revertive Supports Automatically Revertive, Non-Revertive, and
Scheduled revertive.
rectified.
Service migration l Supports migration between gold WDM ASON trails and
traditional WDM trails.
not supported.
l Supports migration between electrical-layer gold WDM
l Supports migration between electrical-layer gold WDM
Service switching Do not supports manual switching.

1.2.8 Silver WDM ASON Trail
Silver WDM ASON services, including WDM ASON OCh trails, ODU0, ODU1 trails, ODU2
trails and Client 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.
1-23
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-14, 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-14 A silver service
R1
R2
R3
R4
A
B
C
D
E
F
G
H
I
LSP after rerouting
Original LSP
: ASON NE
: User equipment

Table 1-7 lists the attributes of silver services.
Table 1-7 Attributes of silver services
Attribute Silver Services
Service restoration When the original LSP fails, rerouting is triggered to create a new
LSP to restore services.
Issue 02 (2010-09-24)
Attribute Silver Services
l Supports four rerouting policies:
rectified.
Service migration l Supports migration between silver WDM ASON trails and
traditional unprotected WDM trails without affecting them.
not supported.
l Supports migration between electrical-layer silver WDM
ASON trails and diamond WDM ASON trails.
l Supports migration between electrical-layer silver WDM
ASON trails and gold WDM ASON trails.
Service association Supports service association.

1-25
1.2.9 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, ODU0 trail, ODU1 trail, ODU2 trail, and Client trail.
Copper services are also called non-protection services. If an LSP fails, services do not reroute
and are interrupted. Table 1-8 lists the attributes of copper services.
Table 1-8 Attributes of copper services
Attribute Silver Service
Service restoration Does not support rerouting.
Service migration l Supports migration between copper WDM ASON trails and
traditional WDM trails.
not supported.
l Supports migration between electrical-layer copper WDM
ASON trails and diamond WDM ASON trails.
ASON trails and gold WDM ASON trails.
Service association Supports service association.

1.2.10 OVPN
The optical virtual private network (OVPN) divides the TE link resources in an ASON network
to different customers. Sharing the fiber resources, the customers, however, can use and manage
only their own TE links and ASON services.
As shown in Figure 1-15, certain wavelengths 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 wavelengths resources and ASON services.
Multiple NM users can be created for one OVPN customer. One NM user can manage multiple
OVPN customers.
Issue 02 (2010-09-24)
Figure 1-15 Networking diagram of an OVPN
T2000 Server
T2000 Client
OVPN Customer 1
T2000 Client
OVPN Customer 2
: Resource of OVPN customer 1
: Resource of OVPN customer 1
T2000 Client
NM User Admin
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.
NOTE
Only admin user of the U2000 can enable or disable the OVPN of an NE.
OVPN Customer
After you can create an OVPN customer, in the subsequent resource partitioning, you can
allocate the wavelengths of links to the OVPN customer, binding the resources with the
customer. The link resources that are allocated to the OVPN customer is considered as constraints
when you create a service. In this way, the service passes only the links that are allocated to the
OVPN customer. Currently, a maximum of 60,000 OVPN customers can be created on the
U2000.
1-27
Partitioning the OVPN
The partitioning of OVPN resources refers to allocating the TE link resources to different OVPN
customers. After partitioning, the TE links are classified as the follows: shared resources and
OVPN customer resources. See Figure 1-16.
Figure 1-16 Partitioning the TE link resources
.
.
.
.
.
.
.
Shared
Resource
TE Link
Wavelength 1
Resource of
OVPN
Customer1
Resource of
OVPN
Customer2
Wavelength n
NOTE
The resource which not support OVPN belongs to share resources, but you can not allocate it to customer.
The optical-layer support OVPN function, and electrical-layer resources is share resource, not support
OVPN.
OVPN NM User
On an OVPN network, an OVPN user manages OVPN customer resources and services. After
allocating links to OVPN customers, the pipe provider needs to create NM users the OVPN
customers and allocate the corresponding rights to the NM users. Each NM user represents the
corresponding OVPN customer. An OVPN customer logs into the NM and manages its own
OVPN network by using the corresponding NM user name and password.
Considering the security of an OVPN network, you need to allocate appropriate rights to OVPN
NM users as required.
OVPN Services
Table 1-9 lists the OVPN service attributes.
Table 1-9 OVPN service attributes
Attribute OVPN Service
Creating a service l When creating a service, the NM user Administrator can use the
shared resources and OVPN user resources. Each OVPN service can
use only the wavelength resources of the same color.
l An OVPN customer can create a service on the resources only
allocated to the OVPN customer.
Issue 02 (2010-09-24)
Attribute OVPN Service
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
restoration trail
A restoration trail can be preset. An OVPN customer can use the allocated
resources only.
Shared Mesh
restoration trail
A shared Mesh restoration trail can be preset. An OVPN customer can
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
optimization
An ASON service of an OVPN user can be optimized on the resources
only allocated to the OVPN customer.

1.3 Creating an ASON Topology
The ASON network uses the route protocol to create the topology information of the nodes in
the network so that each node can obtain a networkwide topology.The U2000 can discover other
ASON NEs in the network from any ASON NE.
Context
NOTE
l An ASON NE can only belong to one ASON domain.
l The configuration data of each newly created ASON NE must be uploaded from the NE side.
l Because of some DCN communication problems, the topology and TE link information on the
U2000 may be inconsistent with the data on the NE. In this case, perform NE data synchronization to
maintain data consistency.
1.3.1 Creating NEs in Batches
When the U2000 communicates properly with a GNE, you can search for all NEs that
communicate with the GNE by using the IP address of the GNE or the network segment to which
the IP address is associated. Then, you can create NEs in batches. This method is quicker and
more accurate than manual creation.
1.3.2 Creating a Single NE
After the NE is created, you can use the U2000 to manage the NE. Although creating a single
NE is not as fast and exact as creating NEs in batches, you can use this method regardless of
whether the data is configured on the NE or not.
1.3.3 Creating Optical NEs
The U2000 allocates the WDM equipment into different optical NEs for management. There
are four types of optical NEs. They are WDM_OADM, WDM_OEQ, WDM_OLA and
WDM_OTM.
1-29
1.3.4 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.
1.3.5 Enabling the ASON Feature
The NE obtains the ASON feature after this feature is enabled. The ASON feature is disabled
by default during delivery.
1.3.6 Uploading NE Configuration Data
After the ASON software of an NE is enabled, the ASON NE automatically generates data on
the NE. Considering that the data dynamically changes as the system runs, you can upload data
to the U2000 to ensure that the data on the U2000 is consistent with that on the NE. Do not use
the U2000 to initialize the ASON NE or download data to the ASON NE.
1.3.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.
1.3.8 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.
1.3.9 Automatically Creating Fibers According to TE Link
An ASON network can automatically discover TE links. The U2000 can create fibers between
NEs according to the TE links.
1.3.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.
1.3.11 Setting Control Plane Parameters
You can set the control plane parameters of an ASON NE. The parameters contain the custom
cost weight, the bandwidth load, bandwidth weight, distance weight, and hop weight.
1.3.12 Viewing ASON NE Software Version
Different ASON software versions provide different functions. By viewing the version of the
ASON software running on an NE, you can know the ASON feature of the NE. This help you
to configure, manage, maintain and troubleshoot the ASON NE.
1.3.13 Disabling the Electrical-Layer ASON Feature
WDM ASON features are implemented at both the electrical and optical layers. When you use
only the optical-layer ASON feature on an ASON NE, you can disable the electrical-layer ASON
feature on the ASON NE to release resources.
1.3.1 Creating NEs in Batches
When the U2000 communicates properly with a GNE, you can search for all NEs that
communicate with the GNE by using the IP address of the GNE or the network segment to which
Issue 02 (2010-09-24)
the IP address is associated. Then, you can create NEs in batches. This method is quicker and
more accurate than manual creation.
Prerequisite
You must be an NM user with "NE administrator" authority or higher.
The U2000 must communicate properly with the GNE.
The NE Explorer instance of the NEs must be created.
Procedure
Step 1 Choose File > Discovery > NE from the main menu.
Step 2 Click the Transport NE Search tab.
Step 3 Optional: Enter the network segment or IP addresses NEs to search for the NEs.
1. Click Add and the Input Search Domain dialog box is displayed.
2. Set Address type to IP Address Range of GNE, IP Address of GNE, or NSAP
Address, and enter Search Address, User Name, and Password. Then, click OK.
NOTE
You can repeat Steps a through b to add more search domains. You can delete the system default
search domain.
l If you use IP address to search for NEs:
l Usually, the broadcast function is disabled on the routers on a network, to avoid network
broadcast storm. Therefore, by using the IP Address Range of GNE method, only the NEs
in the same network segment can be searched out.
l To search the network segments across routers, the IP Address of GNE method is
recommended. Through a gateway NE, you can search out the NEs in the network segment
of the gateway NE.
Step 4 Optional: If you fail to enter a network segment correctly, enable IP auto discovery and enter
the User Name and Password of the NEs.
NOTE
After enabling IP auto discovery, you can obtain the IP address of the GNE and search out all the NEs
related to the GNE.
If the U2000 and an gateway NE are connected through a router, you need to create an NE by using the IP
address of the gateway NE.
Step 5 In the Search for NE area, perform the following operations:
l Select Create device after search, enter the NE User and Password.
1-31
NOTE
l The default NE user is root.
l The default password is password.
l Select Upload after create. The data related to the NEs are uploaded to the U2000 after
the NEs are created.
NOTE
You can select all options in the Search for NE area to search for NEs, create NEs, and upload the NE
data at a time.
Step 6 Click Next and the Result area is displayed.
Step 7 Optional: If you select Search for NE only, you can select the NEs, which are not yet created,
in the Result list after the search for NEs is complete. Click Create and then the Create dialog
box is displayed. Enter User Name and Password in the Create dialog box, and then click
OK.
Step 8 Optional: Click Change NE ID. Then, the Change NE ID dialog box is displayed. Users can
check against the Bar Code List by the value of Bar Code, and then modify the NE Name,
Extend NE ID, Base NE ID, and IP Address fields accordingly.
Issue 02 (2010-09-24)
NOTE
The Bar Code List is provided by the hardware installation personnel to the software commissioning personnel.
The list contains the bar codes of stations.
----End
Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
1.3.2 Creating a Single NE
After the NE is created, you can use the U2000 to manage the NE. Although creating a single
NE is not as fast and exact as creating NEs in batches, you can use this method regardless of
whether the data is configured on the NE or not.
Prerequisite
l You must be an NM user with "NM operator" authority or higher.
l The NE Explorer instance of the NEs must be created.
Context
First create a GNE, and then create a non-gateway NE.
If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray color.
Procedure
Step 1 Right-click in the blank space of the Main Topology and choose New > NE from the shortcut
menu. The Create NE dialog box is displayed.
Step 2 Select the NE type from the Object Type tree.
Step 3 Complete the following information: ID, Extended ID, Name and Remarks.
Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.
1-33
Step 5 Select Gateway from the Gateway Type drop-down list and set the IP address.
Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NE
is associated to from the Affiliated Gateway drop-down list.
Step 7 Select the optical NE to which the WDM NE is associated.
Step 8 Enter the NE User and Password.
NOTE
The default NE user is root, and the default password is password.
Step 9 Click OK. and click Open in the dialog box displayed.
----End
Result
After an NE is successfully created, the system automatically saves the information, such as the
IP address, subnet mask, and NE ID to the U2000 database.
Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as the IP address of the NE and NE ID.
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
1.3.3 Creating Optical NEs
The U2000 allocates the WDM equipment into different optical NEs for management. There
are four types of optical NEs. They are WDM_OADM, WDM_OEQ, WDM_OLA and
WDM_OTM.
Prerequisite
l You must be an NM user with "NM operator" authority or higher.
Procedure
Step 1 Choose File > Create > NE from the main menu.
Step 2 Select the optical NE type for the optical NE in the Create NE dialog box.
Step 3 In the General Attributes tab, set the attributes of the optical NE.
Step 4 Click the Resource Division tab. Select NEs or boards from the Select Boards and click
.
Step 5 Click OK.
Issue 02 (2010-09-24)
Step 6 Click in the blank space of the Main Topology and the NE icon appears in the position where
you clicked.The cursor is displayed as "+". Click on the Main Topology, and the NE will be
displayed on the topology.
----End
1.3.4 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 maintainer" 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 be duplicate in the same ASON domain.
l Node IDs of NG WDM NEs cannot be duplicate in the same NMS.
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.
l Node IDs must be set before the ASON feature is enabled. After the node ID is set, a warm
reset is performed on the NE.
CAUTION
When a delivered network is running, do not change the node ID. To change the node ID, contact
Huawei Technologies Co., Ltd.
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 is displayed indicating that the
operation was successful.
1-35
NOTE
You can also set the NE node ID in ASON Topology Management.
----End
1.3.5 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 You must be an NM user with "NE administrator" authority or higher.
l The NE software must contain the ASON feature and must be successfully enabled.
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 Check the Enable TIM Response status of the neighboring NEs before enabling the ASON
feature. If the Enable TIM Response status is Enabled, modify it into Disabled.
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, upload the NE data to keep the consistency of data
between the U2000 and the NE. For relevant operations, refer to 1.3.6 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.
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.
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > ASON Feature Management from the
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.
Step 4 Click Apply. After you confirm the operation twice, a prompt is displayed indicating that the
operation was successful.
After you disable the ASON feature, synchronize the NE data to keep the consistency of data
between the U2000 and the NE. For relevant operations, refer to 1.3.6 Uploading NE
Configuration Data.
----End
1.3.6 Uploading NE Configuration Data
After the ASON software of an NE is enabled, the ASON NE automatically generates data on
the NE. Considering that the data dynamically changes as the system runs, you can upload data
to the U2000 to ensure that the data on the U2000 is consistent with that on the NE. Do not use
the U2000 to initialize the ASON NE or download data to the ASON NE.
Prerequisite
l You must be an NM user with "NE operator" authority or higher.
l The NE must be created successfully.
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
1.3.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
1-37
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.
----End
1.3.8 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.
Issue 02 (2010-09-24)
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
and 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 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
1.3.9 Automatically Creating Fibers According to TE Link
An ASON network can automatically discover TE links. The U2000 can create fibers between
NEs according to the TE links.
Prerequisite
l The ASON network is running normally.
Procedure
Step 1 Choose Configuration > WDM ASON > TE Link Management from the main menu.
Step 2 The list shows all links on the U2000. View TE information of each link.
Step 3 Select a TE link for the fiber you want to create. Click Maintenance and choose Create
Fiber. Click Close in the Operation Result dialog box.
NOTE
The fibers created according to TE links are the fibers between NEs. After the fiber(s) is/are created
successfully, view them on the Main Topology.
----End
1.3.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
1-39
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 from the main
menu. . 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
1.3.11 Setting Control Plane Parameters
You can set the control plane parameters of an ASON NE. The parameters contain the custom
cost weight, the bandwidth load, bandwidth weight, distance weight, and hop weight.
Prerequisite
l The ASON NE must be created and configured.
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select an NE and choose ASON > Control Plane Parameters from the
Function Tree.
Step 2 Click Query to query the route computation policy from the NE.
Step 3 Set the Route Computation Policy field and complete the rest information.
NOTE
Only an ASON NE whose ASON version is GSP V100R004 or later support custom cost weight.
l The route computation policy has the following parameters: Custom Cost Weight (0 to 500), Bandwidth
Load (0 to 100), Bandwidth Weight (0 to 500), Distance Weight (0 to 500), Hop Weight (0 to 500).
l It is recommended to keep the default settings. The default settings are as follows: custom cost weight:
50. bandwidth load: 0. Bandwidth weight: 50. Distance weight: 50. Hop weight: 0.
Step 4 Click Apply.
----End
1.3.12 Viewing ASON NE Software Version
Different ASON software versions provide different functions. By viewing the version of the
ASON software running on an NE, you can know the ASON feature of the NE. This help you
to configure, manage, maintain and troubleshoot the ASON NE.
Prerequisite
l You must be an NM user with "NE monitor" authority or higher.
l This function applies to ASON NEs.
Procedure
Click the Configured NE tab.
Step 2 Select the desired domain in the Object Tree and click . All ASON NEs in the domain
are displayed in the list.
Step 3 View the ASON NE software version in the Version. for example,
5.99.21.10.
----End
1.3.13 Disabling the Electrical-Layer ASON Feature
WDM ASON features are implemented at both the electrical and optical layers. When you use
only the optical-layer ASON feature on an ASON NE, you can disable the electrical-layer ASON
feature on the ASON NE to release resources.
1-41
Prerequisite
l The electrical-layer ASON trail cannot exist on ASON NEs.
l It is applicable to the WDM ASON NEs of GSP V100R004 or later versions.
Procedure
Step 2 In the WDM ASON Topology Management window, select an ASON domain.
Step 3 Click the Enable Electrical-Layer ASON Feature tab. Select ASON NE, double-click the
corresponding Enable Electrical-Layer ASON Feature field, and select No from the drop-
down list.
TIP
Press Ctrl+A to select all NEs. In the Enable Electrical-Layer ASON Feature area, right-click and choose
No 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: Click Refresh to view the status of the electrical-layer ASON feature of the ASON
NE.
----End
1.4 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.
Issue 02 (2010-09-24)
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.
1.4.1 Querying the LMP Discovery Type
You can query the overhead bytes that are used by the LMP for the system to automatically
discover TE links. Currently only the D4-D12 bytes are used. They are used for the
communication between NEs.
1.4.2 Disabling 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.
1.4.3 Disabling 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.
1.4.4 Encrypting the OSPF Protocol
You can query and set the OSPF protocol authentication and encrypt the OSPF protocol to ensure
the security of the ASON network.
1.4.5 Encrypting RSVP
You can query and set the resource reservation protocol (RSVP) authentication and encrypt
RSVP to ensure the security of the ASON network.
1.4.6 Creating Out-Fiber Control Channels
The out-fiber control channel realizes 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.
1.4.1 Querying the LMP Discovery Type
You can query the overhead bytes that are used by the LMP for the system to automatically
discover TE links. Currently only the D4-D12 bytes are used. They are used for the
communication between NEs.
Prerequisite
l The ASON feature of the NEs is enabled.
l Applies to OptiX OSN 3800, OptiX OSN 6800, OptiX OSN 8800 series.
1-43
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.
----End
1.4.2 Disabling 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
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, complete the operation.
Step 6 Optional: Click Query. Queries LMP protocol status from the NE.
----End
1.4.3 Disabling 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
Issue 02 (2010-09-24)
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
Step 1 In the NE Explorer, select an NE and choose ASON > Advanced Maintenance from the
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 5 Click Yes.
Step 6 Click Query. Queries OSPF protocol status from the NE.
----End
1.4.4 Encrypting the OSPF Protocol
You can query and set the OSPF protocol authentication and encrypt the OSPF protocol to ensure
the security of the ASON network.
Prerequisite
1-45
CAUTION
The encryption 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 > 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
1.4.5 Encrypting RSVP
You can query and set the resource reservation protocol (RSVP) authentication and encrypt
RSVP to ensure the security of the ASON network.
Prerequisite
l The encryption 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.
Issue 02 (2010-09-24)
NOTE
l The following three options are available for Authentication Mode: 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 5 Click OK.
NOTE
To create multiple entries of RSVP authentication, click Apply.
----End
1.4.6 Creating Out-Fiber Control Channels
The out-fiber control channel realizes 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
Service Requirements
You can create an out-fiber control channel as shown in Figure 1-17. 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.
1-47
Figure 1-17 Creating out-fiber control channels
: ASON NE
: Fiber
: Ethernet link
NE1
NE2 NE3
NE4
NE5
NE6 NE7
NE8
ASON001 ASON002
NE9
: Traditional NE

NOTE
You need to create an out-fiber control channel 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 field respectively.
Issue 02 (2010-09-24)
NOTE
The remote address and the next hop address are the node ID of the remote NE.
l As shown in Figure 1-17, 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.
Step 4 Click Apply for the settings to take effect.
Step 5 Creating a Virtual TE Link.
If NE3 is the source, you need to create the virtual TE link between NE3 and NE6.
----End
1.5 Managing Link Resources
As the network is growing larger, a reasonable way of resource management is required to make
the most of the network resources and to improve the network efficiency. ASON links are
composed of control channels, control links and TE links.
1.5.1 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.
1.5.2 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.
1.5.3 Viewing TE Links
You can view the ASON TE link information on the U2000. This helps you to configure or
maintain TE links.
1.5.4 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.
1.5.5 Setting the Usage Threshold of WDM 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
alarm.
1.5.6 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.
1-49
1.5.7 Setting the Custom Cost of the TE Link
You can set the custom cost of the TE link on the U2000 for route calculation. You must set the
custom cost and custom cost weight at the same time to enable the parameters.
1.5.8 Querying Resource Occupation Status
You can query the resource occupation and reservation status of an optical port of a board. The
status includes the following: wavelength ingress occupation status, wavelength ingress
reservation status, wavelength egress occupation status, and wavelength egress reservation
status.
1.5.9 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.
1.5.10 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 realize the creation and protection
for ASON services between traditional NEs and ASON NEs. You can directly create ASON
services on TE links.
1.5.11 Deleting an Interrupted TE Link Manually
When a TE link is interrupted, the TE link is saved on the U2000 and the link status is
Interrupted. This facilitates fault locating. You can also manually delete the interrupted link.
1.5.1 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.
Issue 02 (2010-09-24)
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 are displayed in the list.
----End
1.5.2 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
Procedure
Step 2 In the Filter dialog box displayed, choose Name, Domain, Link Signal Type, Payload
Type, and Source/Sink NE of the TE links that need to be synchronized, and then click
Filter.
1-51
Step 3 Click Synchronize. In the Synchronize dialog box displayed, choose Domain, Payload
Type and Extended Attributes.
NOTE
After the synchronization is complete, all the information about the TE links is displayed in the list.
----End
1.5.3 Viewing TE Links
You can view the ASON TE link information on the U2000. This helps you to configure or
maintain TE links.
Prerequisite
Procedure
Step 2 In the Filter dialog box displayed, choose Domain, Link Signal Type, Payload Type, and
Source/Sink NE of the TE links that need to be synchronized, and then click Filter.
Issue 02 (2010-09-24)
NOTE
For hybrid link, when you select the payload type the TE link included, the TE link will be filtered.
Step 3 The list shows all links that fit the filtering restriction on the U2000. View the information of
each link.
NOTE
A TE link is unidirectional. So a two-fiber bidirectional fiber is displayed as two TE links.
Step 4 Optional: Click Filter, reset the filter restriction in the dialog box displayed according to
requirements.
Step 5 Optional: Click Print, in the Range dialog box displayed, enter the Start row and End row to
print the desired TE link information records.
Step 6 Optional: Click Save As, in the Saving Options dialog box displayed, enter the Start Row,
End Row and File Name. Click OK to save the desired TE link information records.
NOTE
Click the behind the File Name text box to set the path, file name and file type that you want to save.
----End
1.5.4 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.
1-53
NOTE
Step 4 Select a link, double-click the Distance(km) field, and enter a value.
----End
1.5.5 Setting the Usage Threshold of WDM 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
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 > WDM 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
1.5.6 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 must be configured on the U2000.
Service Requirement
See Figure 1-18. 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.
Issue 02 (2010-09-24)
Figure 1-18 SRLG schematic diagram
Two fibers in one cable
NE1
NE2 NE3
NE4
NE5

Procedure
Step 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 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
1.5.7 Setting the Custom Cost of the TE Link
You can set the custom cost of the TE link on the U2000 for route calculation. You must set the
custom cost and custom cost weight at the same time to enable the parameters.
Prerequisite
l TE link management is based on correct link information.
l The ASON NE of the GSP V100R004 version or a later version.
Procedure
Step 2 Click Synchronize. In the Synchronize dialog box displayed, choose Domain and Payload
Type.
1-55
NOTE
Step 4 Select a link, double-click the Custom Cost field, and enter a value. Or right-click the column,
enter the value in the dialog box.
NOTE
l The value of custom cost is 0 to 100.
l If the source NE of the TE link not support the custom cost, the value is 0 and you can not set it. Namely,
the route calculation not affected by this parameters.
----End
1.5.8 Querying Resource Occupation Status
You can query the resource occupation and reservation status of an optical port of a board. The
status includes the following: wavelength ingress occupation status, wavelength ingress
reservation status, wavelength egress occupation status, and wavelength egress reservation
status.
Prerequisite
l This function applies to the following boards: LWXS, LDGS, LSX, LQMS, L4G, LWX2,
LWXD, LDGD, LSXR, LQMD, FIU, and NS2.
Procedure
Step 1 In the NE Explorer, select a board and choose ASON > Resource Occupation Status from the
Function Tree.
Step 2 Click Query to view the Wavelength Ingress Occupation Status, Wavelength Ingress
Reservation Status, Wavelength Egress Occupation Status and Wavelength Egress
Reservation Status of the port.
----End
1.5.9 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
Issue 02 (2010-09-24)
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
1.5.10 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 realize the creation and protection
for ASON services between traditional NEs and ASON NEs. You can directly create ASON
services on TE links.
Prerequisite
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.
Service Requirement
See Figure 1-19. 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 1-19 Virtual TE link
NE1
NE2
NE3
NE4
NE5
Virtual TE link
: ASON NE
: Traditional NE
1-57
Board Configuration
To meet the previously mentioned service requirements, you can configure the boards on NE3
and NE4 as shown in Figure 1-20, and configure the boards on NE5 as shown in Figure 1-21.
The 8-FIU of NE3 and the 5-FIU of NE5 are connected. The 5-FIU of NE4 and the 8-FIU of
NE5 are connected.
Figure 1-20 Board configuration for NE3 and NE4
Slave Subrack2
S
C
C
F
I
U
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
F
I
U
F
I
U
X
C
S
T
D
G
S
C
2
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
W
S
M
D
4
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
W
S
M
D
4
S
C
C
N
D
2
N
D
2
N
D
2
N
D
2
P
I
U
P
I
U
A
U
X
N
D
2
X
C
S
1
2
N
S
2
N
D
2
L
Q
M
D
X
C
S
N
D
2
T
D
X
T
Q
X
Issue 02 (2010-09-24)
Figure 1-21 Board configuration for NE5
S
C
C
F
I
U
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
1
2
N
D
2
F
I
U
F
I
U
X
C
S
O
L
P
S
C
2
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
W
S
M
D
4
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
W
S
M
D
4
S
C
C
N
D
2
N
D
2
N
D
2
N
D
2
P
I
U
P
I
U
A
U
X
N
D
2
X
C
S
1
2
N
S
2
L
D
M
D
L
D
G
D
N
D
2
L
Q
M
D
X
C
S
N
D
2
T
D
X
T
Q
X
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.
For example
l Extended Type: ASON Trail Creation
l Signal Type: OCH
l Source NE: NE3; Source Port: 301-ND2-1(IN1/OUT1) (The optical interface must be the
one connected to NE5).
l Source NE: NE4; Source Port: 302-ND2-1(IN1/OUT1) (The optical interface must be the
one connected to NE5).
1-59
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 ODUk SPRing spans an ASON network and an WDM 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.
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
1.5.11 Deleting an Interrupted TE Link Manually
Interrupted. This facilitates fault locating. You can also manually delete the interrupted link.
Prerequisite
l The status of a TE link must be Interrupted.
Context
Interrupted. You can perform a network-wide synchronization to delete all interrupted TE links,
or manually delete a specific interrupted TE link.
In the window for viewing alarms, you can query the interrupted TE link by viewing the TE
links relevant to the alarm. Meanwhile, the interrupted TE link is displayed in the TE link
management list.
Procedure
Step 2 In the TE link list, select one or more links whose statuses are Interrupted, right-click, and
choose Delete from the shortcut menu.
Step 3 In the confirmation dialog box, click OK.
Step 4 A dialog box is displayed indicating that the operation is successful. Click Close.
----End
1.6 Managing SRGs
The TE links in the same optical cable, NE, site, and pipe have the same risk. You can find a
balance point between management costs and risk control, determine the risks to be managed,
and manage the risks by means of SRGs.
1.6.1 Creating an SRG
Issue 02 (2010-09-24)
The TE links in the same optical cable, NE, site, and pipe have the same risk. You can create an
SRG that associates the physical topology of an ASON network to TE links. In this manner, you
can easily manage risks.
1.6.2 Querying the SRG Related to a TE Link
The TE links in the same optical cable, NE, site, and pipe have the same risk. SRGs and TE links
are of the many-to-many relationship. That is, an SRG may contain multiple TE links and a TE
link may belong to multiple SRGs.
1.6.3 Querying the SRG Related to an ASON NE
You can query an SRG by means of an ASON NE.
1.6.1 Creating an SRG
The TE links in the same optical cable, NE, site, and pipe have the same risk. You can create an
SRG that associates the physical topology of an ASON network to TE links. In this manner, you
can easily manage risks.
Prerequisite
l You must have the U2000 license that supports the SRG function.
l The TE link data exists on the U2000.
Basic Concepts
The physical topology of an ASON network in a project usually differs from the TE links in the
control plane due to the differences in the planning and construction of sites, optical cables, and
pipes. The two links that seem to be irrelevant on the topology may be placed in the same optical
cable or pipe.
Hence, the TE links in the same optical cable, pipe, and NE have the same risk. The risk refers
to the probability of a link cut.
NOTE
The current version only support the SRGs with the type of pipe or customize, and you can only add the
fiber to the SRGs.
Physical Topology
Figure 1-22 shows the physical topology. NE 1 through NE 3 are ASON NEs. NE 2 and NE 3
are located on site B. Fiber 1 and fiber 3 are located in optical cable 1; fiber 2 and fiber 4 are
located in optical cable 2; fiber 2 and fiber 3 are located in optical cable 3; fiber 3 and fiber 4
are located in optical cable 4; optical cable 1 and fiber 2 are located in pipe 1.
1-61
Figure 1-22 Schematic diagram of the physical topology of an SRG
Node B
NE2 NE3
: ASON NE
NE1
Node A
: Fiber
: Cable
: Pipe
Fiber 1
Fiber2
Fiber 3
Fiber 4
Pipe 1
Cable 1
Cable 2
Cable 3
Calbe 4
Topology of TE Links
Figure 1-23 shows the topology of TE links. Link 1 and link 3 are located between NE 1 and
NE 2; link 4 is located between NE 1 and NE 3; link 2 is located between NE 2 and NE 3. All
NEs are located in ASON domains.
Figure 1-23 Schematic diagram of the topology of the TE links in an SRG
NE1 NE2
Link 4 Link 2
Link 1
Link 3
NE3
Risk Analysis
The TE links in the same pipe have the same risk. Table 1-10 lists the risk analysis result
according to the mapping relationship between the physical topology and the TE links.
Issue 02 (2010-09-24)
Table 1-10 Risk cause analysis
Risk Cause Member
Pipe 1 is cut. Link 1, link 2, link 3

SRG Planning
A TE link can belong to multiple SRGs (you can set multiple SRG IDs) and an SRG can contain
multiple TE links. Table 1-11 lists the division of SRGs according to the risk analysis result.
Table 1-11 SRGs for pipes
SRG Name ID Member
SRG_pipe_001 1 fiber 1, fiber 2, fiber 3

Procedure
Step 1 Choose Service > WDM ASON > SRG Management from the Main Menu.
Step 2 Click Create and the Create SRLG dialog box is displayed.
Step 3 Enter the basic information about the SRG.
Basic information
l Name: SRG_pipe_001
l ID: 1
l ASON Domain: ASON
l Type: pipe
l Remarks: pipe
Step 4 Add fiber 1, fiber 2, fiber 3 to the SRG.
1. In the Name text box, enter fiber and click . The object whose name begins with
Fiber is filtered out and displayed in the dialog box.
2. Select fiber 1, fiber 2, fiber 3 and click > to add it to the Selected Object pane.
NOTE
If the queried information is null, there is no information in the Unselected Object field.
Step 5 Click OK.
----End
1.6.2 Querying the SRG Related to a TE Link
The TE links in the same optical cable, NE, site, and pipe have the same risk. SRGs and TE links
are of the many-to-many relationship. That is, an SRG may contain multiple TE links and a TE
link may belong to multiple SRGs.
1-63
Prerequisite
l The TE link data exists on the U2000.
Procedure
Step 2 Select one or more TE links, right-click, and then choose Query Relevant SRGs from the
shortcut menu.
Step 3 The SRG Management window is displayed showing the SRG related to the selected TE link.
NOTE
No SRG is displayed if there is no SRG related to the TE link.
----End
1.6.3 Querying the SRG Related to an ASON NE
You can query an SRG by means of an ASON NE.
Prerequisite
l An SRG must be created on the U2000.
Procedure
Step 2 In the Object Tree, select the ASON domain where the NE to be queried resides and click the
ASON NE tab.
Step 3 Select one or more NEs, right-click, and then choose Query Relevant SRGs from the shortcut
menu.
Step 4 The SRG Management window is displayed showing the SRG related to the selected NE.
----End
1.7 Creating WDM ASON Trails
The trail levels that an WDM ASON 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 WDM ASON trail management feature and supports
services at four classes of service (CoS) as follows:
Issue 02 (2010-09-24)
l Diamond WDM ASON trail: provides 1+1 protection and rerouting ability.
l Gold WDM ASON trail: supports services of ODU1 and ODU2 level, provides ODUk
SPRing 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.
1.7.1 Synchronizing WDM ASON Trails
By synchronizing the ASON WDM trails, the ASON WDM trail data on the U2000 is kept
consistent with that in the ASON network.
1.7.2 Creating an Optical-Layer Diamond WDM ASON OCh Trail
You can create a WDM ASON OCh 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 OCh Trail, rerouting 1+1 diamond WDM ASON OCh
Trail, non-rerouting diamond WDM ASON OCh Trail. The following descriptions are based on
the permanent 1+1 diamond WDM ASON OCh Trail.
1.7.3 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 a high bandwidth utilization.
1.7.4 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.
1.7.5 Creating an Electrical-Layer Diamond WDM ASON ODU0 Trail
You can create a WDM ASON ODU0 trail with the diamond-class protection. According to
permanent 1+1 diamond WDM ASON ODU0 trail, rerouting 1+1 diamond WDM ASON ODU0
trail, non-rerouting diamond WDM ASON ODU0 trail. The following descriptions are based
on the permanent 1+1 diamond WDM ASON ODU0 trail.
1-65
1.7.9 Creating an Electrical-Layer Diamond WDM ASON Client Trail
You can create a WDM ASON Client trail with the diamond-class protection. According to
permanent 1+1 diamond WDM ASON Client trail, rerouting 1+1 diamond WDM ASON Client
trail, non-rerouting diamond WDM ASON Client trail. The following descriptions are based on
the permanent 1+1 diamond WDM ASON Client trail.
1.7.10 Creating an Electrical-Layer Gold WDM ASON ODU1 Trail
Create a WDM ASON ODU1 trail with gold-class protection. During the creation of a gold
WDM ASON ODU1 trail, the working channel of the ODU1 SPRing is preferred.
1.7.12 Creating an Electrical-Layer Silver WDM ASON ODU0 Trail
You can create a WDM ASON ODU1 trail with the silver-class protection. If a silver WDM
ASON ODU1 trail fails, the rerouting is periodically initiated until the ODU1 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 ODU1 trail in real time, you do not need
to reserve resources for it. In this sense, the silver services have a high bandwidth utilization.
1.7.16 Creating an Electrical-Layer Silver WDM ASON Client Trail
You can create a WDM ASON Client trail with the silver-class protection. If a silver WDM
ASON Client trail fails, the rerouting is periodically initiated until the Client trail is successfully
calculates the reverting trail for a silver WDM ASON Client trail in real time, you do not need
1.7.17 Creating an Electrical-Layer Copper WDM ASON ODU0 Trail
You can create a WDM ASON ODU0 trail with the copper-class protection. A copper WDM
ASON ODU0 trail is an unprotected trail. If it fails, no rerouting is initiated and the service is
interrupted.
interrupted.
Issue 02 (2010-09-24)
interrupted.
interrupted.
1.7.21 Creating an Electrical-Layer Copper WDM ASON Client Trail
You can create a WDM ASON Client trail with copper-class protection. A copper WDM ASON
Client trail is an unprotected trail. If it fails, no rerouting is initiated and the service is interrupted.
1.7.22 Creating a WDM ASON OCh Trail at the Optical Layer for an Explicit Optical
Regenerator
Normally, a regenerator is used on an intermediate node of a WDM ASON OCh trail at the
optical layer to improve the signal quality. In the electrical regenerator mode, the ASON module
considers this trail as two trails if an electrical regenerator is used or more than two trails if two
or more electrical regenerators are used. In the optical regenerator mode, the ASON module
considers this trail as an OCh trail.
1.7.23 Creating WDM ASON Inverse Multiplexing Trail
When the TDX board is used for accessing client services, you can create an inverse multiplexing
trail.
1.7.24 Creating Two Associated WDM ASON Trails
You can use this function to create two WDM ASON associated 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.
1.7.25 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 an 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.
1.7.26 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.
1.7.27 Deactivating the WDM ASON Trail
Deactivating an ASON trail can release the resources that the trail occupies.
1.7.28 Deleting an ASON Trail
The operation of deleting ASON trails removes the trail data from the U2000 and the NE.
1.7.1 Synchronizing WDM ASON Trails
By synchronizing the ASON WDM trails, the ASON WDM trail data on the U2000 is kept
consistent with that in the ASON network.
1-67
Prerequisite
l An WDM ASON trail must be created on the U2000.
Procedure
Step 1 Choose Configuration > WDM ASON > ASON Trail Management from the main menu.
Step 2 Optional: Set the filter criteria in the Filter dialog box, and select methods as needed. In the
Prompt dialog box displayed, click Yes.
l If you need to filter all the 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 Click Synchronize, in the Synchronize dialog box displayed, set the Domain, Level and
Attributes.
NOTE
l Attributes: basic information, SLA-compliant, rerouting attributes and associated services.
l Level: Client, ODU, ODU1, ODU2, ODU3 and OCh. Select All to synchronize ASON trails of all levels.
l You can also select one or more ASON trails, right-click and choose Synchronize from the shortcut menu
to synchronize the selected ASON trails. At this time, the synchronized attributes for the ASON trails are
consistent with the synchronization attributes that you set in the Synchronize window.
----End
1.7.2 Creating an Optical-Layer Diamond WDM ASON OCh Trail
You can create a WDM ASON OCh trail with the diamond-class protection. According to
permanent 1+1 diamond WDM ASON OCh Trail, rerouting 1+1 diamond WDM ASON OCh
Trail, non-rerouting diamond WDM ASON OCh Trail. The following descriptions are based on
the permanent 1+1 diamond WDM ASON OCh Trail.
Prerequisite
l The U2000 must have synchronized network-wide TE links and have sufficient TE link
resources.
l The following illustrates how to create such a WDM-ASON trail with OptiX OSN 6800.
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, WDM
ASON Client Trail.
l Diamond services are classified into Permanent 1+1 diamond service, Rerouting 1+1
diamond service and Non-rerouting diamond service.
Issue 02 (2010-09-24)
Precautions
If TOM unit is applied to create the diamond WDM ASON OCh trail, the working port and
protection port of the TOM unit should be specified prior to the creation of the ASON trail. Thus,
the intra-board 1+1 protection can be automatically created during the creation process of the
ASON trail.
Service Requirement
As shown in Figure 1-24, a permanent 1+1 diamond WDM ASON OCh 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 1-24 Diamond WDM ASON OCh Trail requirement
NE1
NE2
NE3
NE4
: ASON NE
Working LSP Protection LSP
: LSP

Board Configuration
In the case of the OptiX OSN 6800, Figure 1-25 shows the board configuration of NE1 and
NE3.
W
S
D
9
S
C
C
L
D
G
D
O
B
U
1
F
I
U
S
C
1
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
Slave Subrack1
W
S
D
9
R
M
U
9
W
S
D
9
R
M
U
9
W
S
D
9
S
C
C
F
I
U
O
B
U
1
W
S
D
9
O
A
U
1
O
B
U
1
F
I
U
S
C
C
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
R
M
U
9
S
C
2
Master Subrack

1-69
Service Planning
To meet the previously mentioned service requirement, you can refer to Table 1-12 to plan the
diamond WDM ASON OCh Trail.
Table 1-12 Diamond WDM ASON OCh Trail planning
Attribute NE1<->NE3
Source NE NE1
Source board Shelf1(Slave Shelf1)-1-LDGD
Source port 1(IN1/OUT1)
Source wavelength 2
Sink NE NE3
Sink board Shelf1(Slave Shelf1)-1-LDGD
Sink port 1(IN1/OUT1)
Sink wavelength 2
Protection class Diamond
Route constraint Working path: NE1-NE2-NE3
Protection path: NE1-NE4-NE3
Routing Attributes Revertive Mode Non-Revertive
Lockout Unlocked
Priority 1
CrankBack 1
Trigger Condition Reroute when one trail fails
Policy Use existing trails whenever possible
Rerouting Hold-off time 0

Procedure
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 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.
For example, set the parameters as follows:
l Name: NE9-1-NE9-3-ASON-WDM-Trail-001
Issue 02 (2010-09-24)
l Level: OCh
l Rate: -
l Class: Diamond
l Direction: Bidirectional
l OVPN Customer: Shared Resource
l Source: NE1-NE9-1-Shelf1(Slave Shelf1)-1-LDGD-1(IN1/OUT1)-2/1529.16/196.050
l Sink: NE3-NE9-3-Shelf1(Slave Shelf1)-1-LDGD-1(IN1/OUT1)-2/1529.16/196.050
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.
For example, set the attributes as follows:
l Revertive Mode: Non-Revertive
l Lockout: Unlocked
l Priority: 1
l CrankBack: 1
l Trigger Condition: Reroute when one trail fails
l Policy: Use existing trails whenever possible
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.
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 Click the Route Restriction tab. Select the Working option button. Right-click NE2 on the
right interface. Select Set As Explicit Node from the shortcut menu.
1-71
Step 7 Click the Route Restriction tab. Select the Protection. Right-click NE4 on the right interface.
Select Set As Explicit Node from the shortcut menu.
NOTE
l Right-click the NE and Set As Explicit Node, Set As Explicit Optical Regenerator, Set As Excluded
Node, Set Explicit Link and Set Excluded Link. To cancel the settings, right-click the NE in the
topology and choose the menu items as needed.
l To change the route constraint, select one or multiple route constraints from the Route Restriction
pane, right-click and choose Delete from the shortcut menu. The selected route constraint is deleted.
Repeat the Steps above to set new route constraints.
l Only optical-layer WDM ASON OCh trail can Set As Explicit Optical Regenerator.
Step 8 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 9 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 10 Select the Enable Optical Parameter Constraints check box.
NOTE
The Optical Parameter Constraints parameter involves OSNR, PMD, and dispersion.
Step 11 Verify that the trail information and route constraints are correctly entered. Click Apply.
Step 12 The system prompts that the operation was successful. Click Close in the Operation Result
dialog box.
Step 13 Optional: Choose Configuration > WDM ASON > ASON Trail Management from the main
menu. View the created ASON trail.
----End
1.7.3 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 a high bandwidth utilization.
Prerequisite
resources.
Issue 02 (2010-09-24)
ASON Client Trail
l Silver services are also called rerouting services. When an LSP failure, the ASON triggers
rerouting to restore the service.
Service Requirement
As shown in Figure 1-26, a silver service need be configured between NE1 and NE3, and the
service must goes through NE2.
Figure 1-26 Silver WDM ASON OCh Trail requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP
LSP

Board Configuration
In the case of the OptiX OSN 6800, you can configure the boards on the NEs as shown in Figure
1-27.
W
S
D
9
S
C
C
L
D
G
D
O
B
U
1
F
I
U
S
C
1
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
Slave Subrack1
W
S
D
9
R
M
U
9
W
S
D
9
R
M
U
9
W
S
D
9
S
C
C
F
I
U
O
B
U
1
W
S
D
9
O
A
U
1
O
B
U
1
F
I
U
S
C
C
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
R
M
U
9
S
C
2
Master Subrack
1-73

Service Planning
To meet the service requirement, you can refer to Table 1-13 to plan a silver WDM ASON OCh
Trail.
Table 1-13 Silver WDM ASON OCh Trail planning
Attribute NE1<->NE3
Source NE NE1
Source wavelength 2
Sink NE NE3
Sink wavelength 2
Protection class Silver
Route constraint The service route must pass NE2.
Routing attribute Revertive Mode Non-Revertive
Lockout Unlocked
Priority 2
CrankBack 1

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.
Issue 02 (2010-09-24)
l Level: OCh
l Rate: -
l Class: Silver
NOTE
Step 4 In the Routing Attributes field, enter the rerouting attributes for the OCh trail.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
Step 6 Optional: Click the Route Restriction tab. Select the Working option button. Right-click NE2
on the right interface. Select Set As Explicit Node from the shortcut menu.
1-75
NOTE
NOTE
dialog box.
----End
1.7.4 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
resources.
WDM ASON ODU2 Trail, WDM ASON ODU1 Trail, WDM ASON Client Trail
l Copper services are also called non-protection services. If an LSP fails, services do not
reroute and are interrupted.
Service Requirement
As shown in Figure 1-28, a copper WDM ASON OCh Trail need be configured between NE1
and NE3, and the service must goes through NE2.
Issue 02 (2010-09-24)
Figure 1-28 Copper WDM ASON OCh Trail requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP
LSP

Board Configuration
In the case of the OptiX OSN 6800, you can configure the boards as shown in Figure 1-29.
W
S
D
9
S
C
C
L
D
G
D
O
B
U
1
F
I
U
S
C
1
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
Slave Subrack1
W
S
D
9
R
M
U
9
W
S
D
9
R
M
U
9
W
S
D
9
S
C
C
F
I
U
O
B
U
1
W
S
D
9
O
A
U
1
O
B
U
1
F
I
U
S
C
C
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
R
M
U
9
S
C
2
Master Subrack

Service Planning
To meet the service requirement, you can refer to Table 1-14 to plan a copper WDM ASON
OCh trail.
Table 1-14 Copper WDM ASON OCh trail planning
Attribute NE1<->NE3
Source NE NE1
1-77
Attribute NE1<->NE3
Source wavelength 2
Sink NE NE3
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 Rate: -
l Class: Copper
l Source: NE1-NE9-Shelf1(Slave Shelf1)-1-1-LDGD-1(IN1/OUT1)-2/1529.16/196.050
l Sink:NE3-NE9-3-Shelf1(Slave Shelf1)-1-LDGD-1(IN1/OUT1)-2/1529.16/196.050
NOTE
NOTE
Step 5 Optional: Click the Route Restriction tab. Select the Working option button. Right-click NE2
on the right interface. Select Set As Explicit Node from the shortcut menu.
Issue 02 (2010-09-24)
NOTE
NOTE
dialog box.
----End
1.7.5 Creating an Electrical-Layer Diamond WDM ASON ODU0
Trail
Prerequisite
resources with ODU0 payload.
l The following illustrates how to create such a WDM-ASON trail use with OptiX OSN 8800
T32.
1-79
ASON Client Trail.
Service Requirement
As shown in Figure 1-30, a permanent 1+1 diamond WDM ASON ODU0 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 1-30 Service Requirements
NE1
NE2
NE3
NE4
Working LSP
: ASON NE
: LSP
Protection LSP

Board Configuration
In the case of the OptiX OSN 8800 T32, Figure 1-31 shows the board configuration of NE1 and
NE3.
Issue 02 (2010-09-24)
FAN
FAN
Slave Subrack1
PIU EFI2
EF
I1
ATE PIU PIU PIU
1
2
W
S
D
9
5
2
X
C
M
1
2
W
S
D
9
1
2
W
S
D
9
F
I
U
FAN
FAN
Mater Subrack
PIU EFI2
EF
I1
ATE PIU PIU PIU
1
2
W
S
D
9
5
2
X
C
M
5
2
X
C
M
1
2
W
S
D
9
N
1
S
L
O
1
6
A
O
A
U
1
N
1
S
L
O
1
6
A
5
2
N
Q
2
R
M
U
5
1
S
C
C
5
1
S
C
C
O
B
U
1
R
M
U
F
I
U
O
A
U
1
O
B
U
1
F
I
U
1
2
S
C
2
F
I
U
L
D
M
D
1
2
S
C
2
R
M
U
R
M
U
5
2
N
Q
2
5
2
N
Q
2
R
M
U
O
B
U
1
5
1
S
C
C
O
A
U
1
5
2
X
C
M
F
I
U

NOTE
These boards must be installed on the same shelf.
Service Planning
To meet the previously mentioned service requirement, you can refer to Table 1-15 plan the
diamond WDM ASON ODU0 trail.
Table 1-15 Diamond WDM ASON ODU0 trail planning
Attribute NE1<->NE3
Source NE NE1
1-81
Attribute NE1<->NE3
Source board Shelf1(Slave Shelf1)-21-52NQ2
Source port 162(ODU0LP2/ODU0LP2)
Sink NE NE3
Sink board Shelf1(Slave Shelf1)-21-52NQ2
Sink port 162(ODU0LP2/ODU0LP2)
Lockout Unlocked
Priority 1
CrankBack 1
Rerouting Triggered
by SD
No
Rerouting Hold-off
time
0

Procedure
dialog box displayed, select the slot, port and channel for the source and the sink.
l Name: NE1-NE3-ASON-WDM-ODU0-Trail-0001
l Level: ODU0
l Rate: ODU0
l Class: Diamond
l SNCP Type: SNC/N
l OTN Level: PM
l Source: NE1-Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/ODU0LP2)
Issue 02 (2010-09-24)
l Sink: NE3-Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/ODU0LP2)
NOTE
The protection type must be set after the Level and Rate parameters.
l Lockout: Unlocked
l Priority: 1
l CrankBack: 1
l Rerouting Triggered by SD: No
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
1-83
NOTE
dialog box.
----End
Trail
Prerequisite
ASON Client Trail.
Service Requirement
As shown in Figure 1-32 and Figure 1-33, 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.
Issue 02 (2010-09-24)
Figure 1-32 Service Requirements
NE1
NE2
NE3
NE4
Working LSP
: ASON NE
: LSP
Protection LSP

Figure 1-33 Diamond WDM ASON ODU1 trail
LP1
ODU1
LP1
ODU1
O
D
U
1
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
O
D
U
1
ODU1 TE link
ODU1 Trail
NS2
TQS
TQS
NS2
NE1 NE3
ODU1 ODU1
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
NS2 NS2
XCS
XCS

Board Configuration
NE3.
1-85
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

NOTE
Service Planning
To meet the previously mentioned service requirement, you can refer to Table 1-16 plan the
Attribute NE1<->NE3
Source NE NE1
Source board Shelf0(Master Shelf)-4-TQS
Source port-channel 201(LP1/LP1)-1
Sink NE NE3
Sink board Shelf0(Master Shelf)-4-TQS
Sink port-channel 201(LP1/LP1)-1
Lockout Unlocked
Priority 1
CrankBack 1
Rerouting Triggered
by SD
No
Issue 02 (2010-09-24)
Attribute NE1<->NE3
Rerouting Hold-off
time
0

Procedure
l Name: NE9-1-NE9-3-ASON-WDM-ODU1-Trail-0001
l Level: ODU1
l Rate: ODU1
l Class: Diamond
l SNCP Type: SNC/N
l OTN Level: PM
l Source: NE1-NE9-1-Shelf0(Master Shelf)-4-TQS-201(LP1/LP1)-1
l Sink: NE3-NE9-3-Shelf0(Master Shelf)-4-TQS-201(LP1/LP1)-1
NOTE
l Lockout: Unlocked
l Priority: 1
l CrankBack: 1
1-87
NOTE
NOTE
NOTE
dialog box.
----End
Trail
Issue 02 (2010-09-24)
Prerequisite
ASON Client Trail.
Service Requirement
Figure 1-35 Service requirements
NE1
NE2
NE3
NE4
Working LSP
: ASON NE
: LSP
Protection LSP

1-89
LP1
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
ODU2 TE link
ODU2 Trail
12NS2
12TDX 12TDX
12NS2
NE1 NE3
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
12NS2 12NS2
XCS XCS
O
D
U
2
O
D
U
2
LP1
O
D
U
2
O
D
U
2

Board Configuration
NE3.
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
1
2
N
S
2
1
2
N
S
2
1
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
1
2
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

NOTE
Service Planning
To meet the previously mentioned service requirements, you can refer to Table 1-17 plan the
Issue 02 (2010-09-24)
Attribute NE1<->NE3
Source NE NE1
Source board Shelf0(Master Shelf)-5-12TDX
Source port-channel 201(ClientLP1/ClientLP1)-1
Sink NE NE3
Sink board Shelf0(Master Shelf)-5-12TDX
Sink port-channel 201(ClientLP1/ClientLP1)-1
Lockout Unlocked
Priority 1
CrankBack 1
Rerouting Triggered by
SD
No
Rerouting Hold-off
time
0

Procedure
l Level: ODU2
l Rate: 11.1G or 10.7G
l Class: Diamond
1-91
l SNCP Type: SNC/N
l OTN Level: PM
l Source: NE1-NE9-1-Shelf0(Master Shelf)-5-12TDX-201(ClientLP1/ClientLP1)-1
l Sink: NE3-NE9-3-Shelf0(Master Shelf)-5-12TDX-201(ClientLP1/ClientLP1)-1
NOTE
l Lockout: Unlocked
l Priority: 1
l CrankBack: 1
NOTE
NOTE
Issue 02 (2010-09-24)
NOTE
dialog box.
----End
Trail
Prerequisite
T32.
ASON Client Trail.
1-93
Service Requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP

LP1
O
D
U
3
O
T
U
3
O
T
U
3
O
D
U
3
ODU3 TE link
ODU3 ASON Trail
54NS3
53TSXL
53TSXL
54NS3
NE1 NE3
O
D
U
3
O
T
U
3
O
T
U
3
O
D
U
3
54NS3 54NS3
52XCH 52XCH
LP1
O
D
U
3
O
D
U
3
Board Configuration
NE3.
Issue 02 (2010-09-24)
FAN
S
C
C
ATE
FAN
A
U
X
PIU PIU PIU PIU EFI2
EF
I1
S
C
C
T
O
M
5
3
T
S
X
L
5
2
X
C
H
5
2
X
C
H
5
4
N
S
3
F
I
U
F
I
U
F
I
U
S
C
1
S
C
2
5
4
N
S
3
M
R
8
V
5
4
N
S
3
NOTE
Service Planning
Attribute NE1<->NE3
Source NE NE1
Source board Shelf0(Master Shelf)-5-53TSXL
Sink NE NE3
Sink board Shelf0(Master Shelf)-5-53TSXL
Lockout Unlocked
1-95
Attribute NE1<->NE3
Priority 1
CrankBack 1
Rerouting Triggered by
SD
No
Rerouting Hold-off
time
0

Procedure
l Level: ODU3
l Rate: 43.0184 or 44.5694G
l Class: Diamond
l SNCP Type: SNC/N
l OTN Level: PM
l Source: NE1-NE9-1-Shelf0(Master Shelf)-5-53TSXL-201(ClientLP1/ClientLP1)-1
l Sink: NE3-NE9-3-Shelf0(Master Shelf)-5-53TSXL-201(ClientLP1/ClientLP1)-1
NOTE
l Lockout: Unlocked
l Priority: 1
l CrankBack: 1
Issue 02 (2010-09-24)
NOTE
NOTE
NOTE
1-97
dialog box.
----End
1.7.9 Creating an Electrical-Layer Diamond WDM ASON Client
Trail
You can create a WDM ASON Client trail with the diamond-class protection. According to
permanent 1+1 diamond WDM ASON Client trail, rerouting 1+1 diamond WDM ASON Client
trail, non-rerouting diamond WDM ASON Client trail. The following descriptions are based on
the permanent 1+1 diamond WDM ASON Client trail.
Prerequisite
resources with GE/ANY payload.
l You cannot use OptiX OSN 8800 series to create Client trails.
l Applies to OptiX OSN 3800, OptiX OSN 6800.
ASON Client Trail.
Service Requirement
As shown in Figure 1-41 and Figure 1-42, a permanent 1+1 diamond WDM ASON Client Trail
NE1
NE2
NE3
NE4
Working LSP
: ASON NE
: LSP
Protection LSP
Issue 02 (2010-09-24)

Figure 1-42 Diamond WDM ASON Client trail
Client Trail
LDGS
NE1 NE3
XCS
LP1
O
D
U
1
O
T
U
1
LDGS
LP1
O
D
U
1
O
T
U
1
LDGS
XCS
LP1
O
D
U
1
O
T
U
1
LDGS
LP1
O
D
U
1
O
T
U
1
GE
GE/Any TE link
GE

Board Configuration
Figure 1-43 shows the board configuration of NE1 and NE3.
PI
U
PI
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
FI
U
FI
U
FI
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
L
D
G
S
L
D
G
S
L
D
G
S

1-99
NOTE
The ANY service boards without cross-connection function (such as LOM, LWX2, LWXS, LWXD, LDM,
LDMD, LDMS, LSX, and LSXL) do not support the diamond WDM ASON service at the rate of ANY.
The ANY service boards with cross-connection function support the creation of the diamond WDM ASON
service at the rate of ANY. In this case, the board to which the ANY service is rerouted must be installed
in the paired slot.
When the XCS is configured, make sure that the GE service board is installed in the paired slot. Then, the
diamond WDM ASON service at the rate of GE is supported.
Service Planning
diamond service.
Table 1-19 Diamond WDM ASON client trail planning
Attribute NE1<->NE3
Source NE NE1
Source board Shelf0(Master Shelf)-6-LDGS
Source port 4(RX2/TX2)
Sink NE NE3
Sink board Shelf0(Master Shelf)-6-LDGS
Sink port 4(RX2/TX2)
Lockout Unlocked
Priority 1
CrankBack 1
Rerouting Triggered
by SD
No
Rerouting Hold-off
time
0

Issue 02 (2010-09-24)
Procedure
l Name: NE9-1-NE9-3-ASON-WDM-Client-Trail-0001
l Level: Client
l Rate: GE-T
l Class: Diamond
l Source: NE1-NE9-1-Shelf0(Master Shelf)-6-LDGS-4(RX2/TX2)
l Sink: NE3-NE9-3-Shelf0(Master Shelf)-6-LDGS-4(RX2/TX2)
NOTE
l Lockout: Unlocked
l Priority: 1
l CrankBack: 1
NOTE
1-101
NOTE
NOTE
dialog box.
----End
Prerequisite
l The U2000 must have synchronized the TE linksof the entire network and have sufficient
link resources with ODU1 payload.
Issue 02 (2010-09-24)
l Idle ODU1 SPRing must be available.
WDM ASON ODU1 Trail, WDM ASON Client Trail
l A gold WDM ASON trail needs only one LSP. This LSP must use working resource of
TE links or non-protection resource of TE links.
Service Requirement
As shown in Figure 1-44 and Figure 1-45, four ASON NEs compose an ODUk SPRing. A gold
WDM ASON ODU1 trail is required between NE1 and NE3.
Figure 1-44 Gold WDM ASON ODU1 trail requirement
NE1
NE2
NE3
NE4 ODU1 SPRing

Figure 1-45 Gold WDM ASON ODU1 trail
TQS
XCS
NE1 (Management node)
1
NS2
NS2
2
3
4
1
2
3
4
1
NS2
2
3
4
1
NS2
2
3
4
XCS
1
NS2
2
3
4
1
NS2
2
3
4
XCS
NE4
NE2
ODU1-1
ODU1-2
ODU1-2
Working path
Protection path
TQS
XCS
NE3
1
NS2
NS2
2
3
4
1
2
3
4
ODU1-1
ODU1-2
ODU1-2
1-103

Board Configuration
1-46.
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

NOTE
Service Planning
To meet the service requirements, you can refer to Table 1-20 to plan a gold WDM ASON
ODU1 Trail.
Table 1-20 Gold WDM ASON ODU1 trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3
Protection class Gold
Lockout Unlocked
Priority 2
Issue 02 (2010-09-24)
Attribute NE1<->NE3
CrankBack 1
Rerouting Triggered
by SD
No
Rerouting Hold-off
time
0

Procedure
l Level: ODU1
l Rate: ODU1
l Class: Gold
NOTE
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
1-105
NOTE
NOTE
dialog box.
----End
Issue 02 (2010-09-24)
Prerequisite
l The U2000 must have synchronized the TE links of the entire network and have sufficient
l Idle ODU2 SPRing must be available.
WDM ASON ODU1 Trail, WDM ASON Client Trail
l A gold WDM ASON trail needs only one LSP. This LSP must use working resource of
TE links or non-protection resource of TE links.
Service Requirement
As shown in Figure 1-47, four ASON NEs compose an ODUk SPRing. A gold WDM ASON
ODU2 trail is required between NE1 and NE3.
Figure 1-47 Gold WDM ASON ODU2 trail requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Board Configuration
1-48.
1-107
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
2
F
I
U
F
I
U
1
2
N
S
2
1
2
N
S
2
1
2
N
S
2
M
R
8
M
R
8
T
Q
S
1
2
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
1
2
N
S
2

NOTE
Service Planning
o meet the service requirement, you can refer to Table 1-21to plan a gold WDM ASON ODU2
Trail.
Table 1-21 Gold WDM ASON ODU2 trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3
Protection class Gold
Routing
attribute
Revertive Mode Non-Revertive
Lockout Unlocked
Priority 2
CrankBack 1
Rerouting Triggered
by SD
No
Issue 02 (2010-09-24)
Attribute NE1<->NE3
Rerouting Hold-off
time
0

Procedure
l Level: ODU2
l Class: Gold
NOTE
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
1-109
NOTE
NOTE
dialog box.
----End
Prerequisite
Issue 02 (2010-09-24)
T32.
ASON Client Trail
Service Requirement
As shown in Figure 1-49, a silver WDM ASON ODU0 trail need be configured between NE1
and NE3, and the service must pass through NE2.
Figure 1-49 Silver WDM ASON ODU0 Trail requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Board Configuration
NE3.
1-111
FAN
FAN
Slave Subrack1
PIU EFI2
EF
I1
ATE PIU PIU PIU
1
2
W
S
D
9
5
2
X
C
M
1
2
W
S
D
9
1
2
W
S
D
9
F
I
U
FAN
FAN
Mater Subrack
PIU EFI2
EF
I1
ATE PIU PIU PIU
1
2
W
S
D
9
5
2
X
C
M
5
2
X
C
M
1
2
W
S
D
9
N
1
S
L
O
1
6
A
O
A
U
1
N
1
S
L
O
1
6
A
5
2
N
Q
2
R
M
U
5
1
S
C
C
5
1
S
C
C
O
B
U
1
R
M
U
F
I
U
O
A
U
1
O
B
U
1
F
I
U
1
2
S
C
2
F
I
U
L
D
M
D
1
2
S
C
2
R
M
U
R
M
U
5
2
N
Q
2
5
2
N
Q
2
R
M
U
O
B
U
1
5
1
S
C
C
O
A
U
1
5
2
X
C
M
F
I
U

NOTE
Service Planning
To meet the service requirement, you can refer to Table 1-22 to plan a silver WDM ASON
ODU0 Trail.
Table 1-22 Silver WDM ASON ODU0 Trail planning
Attribute NE1<->NE3
Source NE NE1
Issue 02 (2010-09-24)
Attribute NE1<->NE3
Sink NE NE3
Lockout Unlocked
Priority 2
CrankBack 1
Rerouting
Triggered by SD
No
Rerouting Hold-off
time
0

Procedure
Step 3 Enter the basic information of the ODU0 trail in the Basic Information tab. Click Browse. In
the dialog box displayed, select the slot, port and channel of the source and sink.
l Level: ODU0
l Rate: ODU0
l Class: Silver
NOTE
1-113
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
NOTE
Issue 02 (2010-09-24)
dialog box.
----End
Prerequisite
ASON Client Trail
Service Requirement
As shown in Figure 1-51 and Figure 1-52, a silver WDM ASON ODU1 trail need be configured
between NE1 and NE3, and the service must pass through NE2.
Figure 1-51 Silver WDM ASON ODU1 Trail requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP
1-115

Figure 1-52 Silver WDM ASON ODU1 trail
LP1 ODU1 LP1 ODU1
O
D
U
1
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
O
D
U
1
ODU1 TE link
ODU1 Trail
NS2 TQS TQS
NS2
NE1 NE3
ODU1
XCS
XCS
ODU1

Board Configuration
1-53.
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

NOTE
Service Planning
To meet the service requirement, you can refer to Table 1-23 to plan a silver WDM ASON
ODU1 Trail.
Issue 02 (2010-09-24)
Table 1-23 Silver WDM ASON ODU1 Trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3
Lockout Unlocked
Priority 2
CrankBack 1
Rerouting
Triggered by SD
No
Rerouting Hold-off
time
0

Procedure
l Level: ODU1
l Rate: ODU1
l Class: Silver
1-117
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
NOTE
Issue 02 (2010-09-24)
dialog box.
----End
Prerequisite
ASON Client Trail
Service Requirement
1-119
Figure 1-54 Silver WDM ASON ODU2 trail requirements
NE1
NE2
NE3
NE4
: ASON NE
: LSP

LP1
ODU2 TE link
ODU2 Trail
12TDX
12TDX
NE1 NE3
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
12NS2 12NS2
XCS
XCS
O
D
U
2
O
D
U
2
LP1
O
D
U
2
O
D
U
2

Board Configuration
1-56.
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
1
2
N
S
2
1
2
N
S
2
1
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
1
2
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Issue 02 (2010-09-24)

NOTE
Service Planning
To meet the service requirements, you can refer to Table 1-24 to plan a silver WDM ASON
ODU2 Trail.
Table 1-24 Silver WDM ASON ODU2 trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3
Lockout Unlocked
Priority 2
CrankBack 1
Rerouting Triggered
by SD
No
Rerouting Hold-off
time
0

Procedure
1-121
l Level: ODU2
l Class: Silver
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
Issue 02 (2010-09-24)
NOTE
dialog box.
----End
Prerequisite
T32.
ASON Client Trail
Service Requirement
1-123
Figure 1-57 Silver WDM ASON ODU3 trail requirements
NE1
NE2
NE3
NE4
: ASON NE
: LSP

LP1
ODU3 TE link
ODU3 Trail
53TSXL
53TSXL
NE1 NE3
O
D
U
3
O
T
U
3
O
T
U
3
O
D
U
3
54NS3 54NS3
52XCH
52XCH
O
D
U
3
LP1
O
D
U
3

Board Configuration
NOTE
Service Planning
ODU3 Trail.
Issue 02 (2010-09-24)
Table 1-25 Silver WDM ASON ODU3 trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3
Lockout Unlocked
Priority 2
CrankBack 1
Rerouting Triggered
by SD
No
Rerouting Hold-off
time
0

Procedure
l Level: ODU3
l Rate: 43.0184 or 44.5694G
l Class: Silver
1-125
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
NOTE
Issue 02 (2010-09-24)
dialog box.
----End
1.7.16 Creating an Electrical-Layer Silver WDM ASON Client Trail
You can create a WDM ASON Client trail with the silver-class protection. If a silver WDM
ASON Client trail fails, the rerouting is periodically initiated until the Client trail is successfully
calculates the reverting trail for a silver WDM ASON Client trail in real time, you do not need
Prerequisite
link resources with GE/ANY payload.
ASON Client Trail
Service Requirement
As shown in Figure 1-59 and Figure 1-60, a silver WDM ASON Client trail need be configured
1-127
Figure 1-59 Silver WDM ASON Client trail requirements
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Figure 1-60 Silver WDM ASON Client trail
GE/Any TE link
Client Trail
NE1 NE3
LDGS
LP1
O
D
U
1
O
T
U
1
LDGS
LP1
O
D
U
1
O
T
U
1
GE GE

Board Configuration
To meet the previously mentioned service requirements, you can configure the boards on the
NEs as shown in Figure 1-61.
PI
U
PI
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
FI
U
FI
U
FI
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
L
D
G
S
L
D
G
S
L
D
G
S
Issue 02 (2010-09-24)

NOTE
The boards must be installed in the same shelf.
The ANY service boards with cross-connection function support the creation of the silver WDM ASON
in the paired slot.
silver WDM ASON service at the rate of GE is supported.
Service Planning
Client Trail.
Table 1-26 Silver WDM ASON Client trail planning
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3
Lockout Unlocked
Priority 2
CrankBack 1
Rerouting Triggered
by SD
No
Rerouting Hold-off
time
0

1-129
Procedure
Step 3 Enter the basic information of the Client trail in the Basic Information tab. Click Browse. In
l Level: Client
l Rate: GE-T
l Class: Silver
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
Issue 02 (2010-09-24)
NOTE
dialog box.
----End
1.7.17 Creating an Electrical-Layer Copper WDM ASON ODU0
Trail
interrupted.
Prerequisite
T32.
1-131
Service Requirement
As shown in Figure 1-62, a copper WDM ASON ODU0 trail need be configured between NE1
and NE3, and the service must pass through NE2.
Figure 1-62 Copper service requirements
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Board Configuration
NE3.
Issue 02 (2010-09-24)
FAN
FAN
Slave Subrack1
PIU EFI2
EF
I1
ATE PIU PIU PIU
1
2
W
S
D
9
5
2
X
C
M
1
2
W
S
D
9
1
2
W
S
D
9
F
I
U
FAN
FAN
Mater Subrack
PIU EFI2
EF
I1
ATE PIU PIU PIU
1
2
W
S
D
9
5
2
X
C
M
5
2
X
C
M
1
2
W
S
D
9
N
1
S
L
O
1
6
A
O
A
U
1
N
1
S
L
O
1
6
A
5
2
N
Q
2
R
M
U
5
1
S
C
C
5
1
S
C
C
O
B
U
1
R
M
U
F
I
U
O
A
U
1
O
B
U
1
F
I
U
1
2
S
C
2
F
I
U
L
D
M
D
1
2
S
C
2
R
M
U
R
M
U
5
2
N
Q
2
5
2
N
Q
2
R
M
U
O
B
U
1
5
1
S
C
C
O
A
U
1
5
2
X
C
M
F
I
U

NOTE
Service Planning
To meet the service requirement, you can refer toTable 1-27 to plan a copper service.
Table 1-27 Copper WDM ASON ODU0 trail planning
Attribute NE1<->NE3
Source NE NE1
1-133
Attribute NE1<->NE3
Sink NE NE3

Procedure
Step 3 In the Basic Information field, enter the basic information of the ODU0 trail. Click Browse.
In the dialog box displayed, select the slot, port, and channel of the source and the sink.
l Level: ODU0
l Rate: ODU0
l Class: Copper
NOTE
Issue 02 (2010-09-24)
NOTE
dialog box.
----End
Trail
interrupted.
Prerequisite
Service Requirement
As shown in Figure 1-64 and Figure 1-65, a copper WDM ASON ODU1 trail need be
configured between NE1 and NE3, and the service must pass through NE2.
1-135
Figure 1-64 Copper service requirements
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Figure 1-65 Copper WDM ASON ODU1 trail
LP1 ODU1 LP1 ODU1
O
D
U
1
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
O
D
U
1
ODU1 TE link
ODU1 Trail
NS2 TQS TQS
NS2
NE1 NE3
ODU1
XCS
XCS
ODU1

Board Configuration
Issue 02 (2010-09-24)
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

NOTE
Service Planning
To meet the service requirement, you can refer toTable 1-28 to plan a copper service.
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3

Procedure
1-137
l Level: ODU1
l Rate: ODU1
l Class: Copper
NOTE
NOTE
dialog box.
----End
Issue 02 (2010-09-24)
Trail
interrupted.
Prerequisite
Service Requirement
As shown in Figure 1-67 and Figure 1-68 , a copper WDM ASON ODU2 trail need be
configured between NE1 and NE3, and the WDM ASON ODU2 Trail must goes through NE2.
NE1
NE2
NE3
NE4
: ASON NE
: LSP

1-139
LP1
ODU2 TE link
ODU2 Trail
12TDX
12TDX
NE1 NE3
O
D
U
2
O
T
U
2
O
T
U
2
O
D
U
2
12NS2 12NS2
XCS
XCS
O
D
U
2
O
D
U
2
LP1
O
D
U
2
O
D
U
2

Board Configuration
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
1
2
N
S
2
1
2
N
S
2
1
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
1
2
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

NOTE
Service Planning
To meet the service requirements, you can refer toTable 1-29 to plan a copper service.
Attribute NE1<->NE3
Source NE NE1
Issue 02 (2010-09-24)
Attribute NE1<->NE3
Sink NE NE3

Procedure
l Level: ODU2
l Class: Copper
NOTE
1-141
NOTE
dialog box.
----End
Trail
interrupted.
Prerequisite
Service Requirement
As shown in Figure 1-70 and Figure 1-71 , a copper WDM ASON ODU3 trail need be
configured between NE1 and NE3, and the WDM ASON ODU3 Trail must goes through NE2.
Issue 02 (2010-09-24)
NE1
NE2
NE3
NE4
: ASON NE
: LSP

LP1
ODU3 TE link
ODU3 Trail
53TSXL
53TSXL
NE1 NE3
O
D
U
3
O
T
U
3
O
T
U
3
O
D
U
3
54NS3 54NS3
52XCH
52XCH
O
D
U
3
LP1
O
D
U
3

Board Configuration
In the case of the OptiX OSN 8800 T32, you can configure the boards as shown in Figure
1-72.
1-143
FAN
S
C
C
ATE
FAN
A
U
X
PIU PIU PIU PIU EFI2
EF
I1
S
C
C
T
O
M
5
3
T
S
X
L
5
2
X
C
H
5
2
X
C
H
5
4
N
S
3
F
I
U
F
I
U
F
I
U
S
C
1
S
C
2
5
4
N
S
3
M
R
8
V
5
4
N
S
3
NOTE
Service Planning
To meet the service requirements, you can refer toTable 1-30 to plan a copper service.
Attribute NE1<->NE3
Source NE NE1
Sink NE NE3

Issue 02 (2010-09-24)
Procedure
l Level: ODU3
l Rate: 43.0184G or 44.5694G
l Class: Copper
NOTE
NOTE
1-145
dialog box.
----End
1.7.21 Creating an Electrical-Layer Copper WDM ASON Client
Trail
You can create a WDM ASON Client trail with copper-class protection. A copper WDM ASON
Client trail is an unprotected trail. If it fails, no rerouting is initiated and the service is interrupted.
Prerequisite
link resources with Client payload.
Service Requirement
As shown in Figure 1-73 and Figure 1-74, a copper WDM ASON Client Trail need be
configured between NE1 and NE3, and the service must pass through NE2.
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Issue 02 (2010-09-24)
Figure 1-74 Copper WDM ASON Client trail
GE/Any TE link
Client Trail
NE1 NE3
LDGS
LP1
O
D
U
1
O
T
U
1
LDGS
LP1
O
D
U
1
O
T
U
1
GE GE

Board Configuration
To meet the previously mentioned service requirements, you can configure the boards as shown
in Figure 1-75.
PI
U
PI
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
FI
U
FI
U
FI
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
L
D
G
S
L
D
G
S
L
D
G
S

NOTE
The ANY service boards with cross-connection function support the creation of the copper WDM ASON
in the paired slot.
copper WDM ASON service at the rate of GE is supported.
Service Planning
To meet the service requirement, you can refer to Table 1-31 to plan a copper service.
1-147
Table 1-31 Copper WDM ASON Client 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 Client trail. Click Browse. In
the dialog box displayed, select the slot, port, and channel of the source and the sink.
l Level: Client
l Rate: GE-T
l Class: Copper
NOTE
Issue 02 (2010-09-24)
NOTE
dialog box.
----End
1.7.22 Creating a WDM ASON OCh Trail at the Optical Layer for
an Explicit Optical Regenerator
Normally, a regenerator is used on an intermediate node of a WDM ASON OCh trail at the
optical layer to improve the signal quality. In the electrical regenerator mode, the ASON module
considers this trail as two trails if an electrical regenerator is used or more than two trails if two
or more electrical regenerators are used. In the optical regenerator mode, the ASON module
considers this trail as an OCh trail.
Prerequisite
resources.
l Only optical-layer WDM ASON OCh trail support setting explicit optical regenerator.
1-149
Service Requirement
As shown in Figure 1-76, you need to configure a WDM ASON OCh trail between NE1 and
NE3. The trail needs to traverses the regenerator NE2.
Figure 1-76 Requirements of a WDM ASON OCh trail Traversing an Optical Regenerator
: ASON NE
: LSP
: Relay NE
NE1
NE2
NE3
NE4
LSP

Board Configuration
1-77.
Issue 02 (2010-09-24)
Figure 1-77 Board configuration for NE1, NE2 and NE3
S
C
C
5
2
N
D
2
F
I
U
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Shelf
Slave Shelf 1
F
I
U
F
I
U
X
C
S
T
D
G
S
C
2
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
W
S
M
D
4
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
W
S
M
D
4
S
C
C
5
2
N
D
2
5
2
N
D
2
5
2
N
D
2
N
D
2
P
I
U
P
I
U
A
U
X
N
D
2
X
C
S
1
2
N
S
2
5
2
N
D
2
L
Q
M
D
X
C
S
N
D
2
T
D
X
T
Q
X
Slave Shelf 2
Slave Shelf 3

Service Planning
Table 1-32 lists the plan of a WDM ASON OCh trail that traverses an optical regenerator.
Table 1-32 Plan of a WDM ASON OCh trail traversing an optical regenerator
Attribute NE1<->NE3
Source NE NE1
Source board-port 301-52ND2-1(IN1/OUT1)
Source Wavelength 74
Sink NE NE3
Sink board-port 301-52ND2-1(IN1/OUT1)
1-151
Attribute NE1<->NE3
Sink Wavelength 74
Route constraint Explicit optical regenerator NE2
Lockout Unlocked
Priority 2
CrankBack 1

Procedure
Step 3 Select the NE2 in the topology view. Right-click and choose NE Explorer from the shortcut
menu.
Step 4 select the board of an ASON NE, such as 301-52ND2, choose Configuration > WDM
Interface from the Function Tree.
Step 5 In the right windows, choose the By Function option button. Select Board from the drop-list.
Step 6 Double-click the Board Mode, choose Optical Relay Mode, click Apply.
Step 7 In the WDM ASON Trail Creation windows, 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-ASON-WDM-Trail-001
l Level: OCh
l Rate: -
l Class: Silver
l Source: NE1-301-52ND2-1(IN1/OUT1)-74/1558.17/192.400
l Sink: NE3-301-52ND2-1(IN1/OUT1)-74/1558.17/192.400
Issue 02 (2010-09-24)
NOTE
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
1-153
NOTE
right interface. Select Set As Explicit Optical Regenerator from the shortcut menu.
NOTE
NOTE
dialog box.
Issue 02 (2010-09-24)
----End
1.7.23 Creating WDM ASON Inverse Multiplexing Trail
When the TDX board is used for accessing client services, you can create an inverse multiplexing
trail.
Prerequisite
l In the case of creation of 10 Gbit/s inverse multiplexing trail, the TDX board must be used.
Service Requirement
As shown in Figure 1-78 and Figure 1-79, a 10 Gbit/s inverse multiplexing trail must be created
between NE1 and NE3 and the service on the trail must pass through NE2.
Figure 1-78 Copper service requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Figure 1-79 Inverse multiplexing trail
LP1
ODU1 TE link
Inverse Multiplexing Trail
TDX
NE1
XCS
ODU1
O
D
U
1
-
V
O
D
U
1
-
V
ODU1
O
D
U
2
O
T
U
2
NS2
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
GE
LP1
TDX XCS
ODU1
O
D
U
1
-
V
O
D
U
1
-
V
ODU1
O
D
U
2
O
T
U
2
NS2
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
ODU1
GE
NE3
1-155

Board Configuration
To meet the previously mentioned service requirement, you can configure the boards as shown
in Figure 1-80.
P
I
U
P
I
U
A
U
X
S
C
C
S
C
C
S
C
1
S
C
2
F
I
U
F
I
U
F
I
U
N
S
2
N
S
2
N
S
2
M
R
2
M
R
2
M
R
2
T
Q
S
T
D
X
1
X
C
S
X
C
S
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

NOTE
Service Requirement
The service requirement is shown in Table 1-33
Table 1-33 Inverse multiplexing trail planning
Attribute NE1<->NE3
Source NE NE1
Source board Shelf0(Master Shelf)--5-TDX
Source port-channel 151(imp1/imp1)-1
Sink NE NE3
Sink board-port Shelf0(Master Shelf)--5-TDX
Sink port-channel 151(imp1/imp1)-1
Protection class Diamond, Gold, Silver or Copper
Route constraint None

Issue 02 (2010-09-24)
Procedure
Step 1 Choose Configuration > WDM ASON > ASON Trail Management from the main menu. In
the dialog box followed, set the filter conditions and then click the ok button to activate the
settings.
Step 2 Click Create > Inverse Multiplexing Trail, the WDM ASON Inverse Multiplexing Trail
Creation is displayed.
Step 3 To set the basic information of the WDM ASON inverse multiplexing trail, click Browse and
then in the dialog box displayed select the source and sink board IDs, ports, and channels.
l Source: NE1-NE9-1-Shelf0(Master Shelf)--5-TDX-151(imp1/imp1)-1
l Sink: NE3-NE9-3-Shelf0(Master Shelf)--5-TDX-151(imp1/imp1)-1
l Level: ODU1
l Capacity: 10G
Step 4 Optional: On the Trail1, Trail2, Trail3, or Trail4 tabs, click Route Restriction and then select
Working. On the right interface, right-click the NE that needs to be set, and then choose the
required working trail from the shortcut menu to set the restriction conditions.
NOTE
Right-click the NE and set the Set As Explicit Node, Set As Excluded Node, Set Explicit Link and Set
Excluded Link of the relevant trails. To cancel the settings, right-click the NE in the topology and choose
the menu items as required.
Step 5 On the Trail1, Trail2, Trail3 or Trail4 tabs, click Routing Attributes and then set route
attributes, including Revertive Mode, WTR Time, Priority, Lockout, CrankBack, Rerouting
Triggered by SD, Policy and Rerouting Hold-off time.
dialog box.
----End
1.7.24 Creating Two Associated WDM ASON Trails
You can use this function to create two WDM ASON associated trails. Two associated WDM
ASON trails should be separated whenever possible during optimization and rerouting. When a
1-157
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
l A minimum of two ASON NEs must be configured.
Application Scenario
As shown in Figure 1-81, 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 1-81 Two Associated ASON Trails
: ASON NE
: User Equipment
R1
R2
A
B
C
E
F
G
H
I

Context
NOTE
Currently, association is supported between silver trails, between copper trails, and between silver and
copper trails.
Procedure
Perform filter and confirmation.
Step 2 Click Create > Association Trail. The Create Associated WDM ASON Trail user interface
is displayed.
Step 3 Set the basic information and route restriction of trail 1.
Issue 02 (2010-09-24)
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.
Step 4 Repeat Step 3 to set the information of trail 2.
NOTE
l In the case of the ASON NE of the GSP V100R004 version or a later version, you can create the
associated ASON trails that share the same source or that have different sources.
l In the case of the ASON NE of the GCP V200R001 version or a later version, you can create the
associated ASON trails that share the same source.
Step 5 Set the common attributes, including the Lockout, Priority, CrankBack, Trigger Condition
for Rerouting Associated Route, Shared Policy of Associated Service, Rerouting Triggered
by SD, Policy and Rerouting Hold-off time.
1-159
NOTE
The WDM ASON OCh associated trail with the same resource support Shared Policy of Associated
Service.
Step 6 Select Automatic Pre-Calculation or click Pre-Calculate. After the operation is successful,
close the operation result dialog box.
NOTE
l In the case of the ASON NE of the GSP V100R004 version or a later version, you can pre-calculate
the associated ASON trails that share the same source or that have different sources.
l In the case of the ASON NE of the GCP V200R001 version or a later version, you can pre-calculate
the associated ASON trails that share the same source.
l Only after you pre-calculated successfully the associated ASON trails that have different sources , you
could create them.
Step 7 Click Apply. After confirmation, apply the configuration.
Step 8 Click Cancel to go back to the WDM ASON Trail Management window. You can see the
detailed descriptions of the ASON trails.
----End
1.7.25 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 an 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
l A minimum of two ASON NEs must be configured.
Context
NOTE
Currently, association is supported between silver trails, between copper trails, and between silver and
copper trails.
Issue 02 (2010-09-24)
Procedure
Perform filter and confirmation.
Step 2 In the WDM ASON trails 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 is displayed indicating that the operation was
successful.
Step 4 Click Close.
Step 5 Optional: Select an ASON trail in the WDM ASON trails 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 of WDM ASON trails, right-click an 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.
Step 6 The dialog box is displayed, set the associated route attributes, including trigger condition for
rerouting associated route, click OK.
Step 7 A dialog box appears, telling that the operation succeeded. Click Close.
Step 8 Select a trail in the WDM ASON trails list. You can know whether the association is successful
by viewing the value of Associated or Not.
Step 9 Optional: In the lower left area of the WDM ASON Trail Management window, click the
Associated Route tab to view the information about the two associated trails.
----End
1.7.26 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 1-82. 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.
1-161
Figure 1-82 Batch silver service requirement
NE1
NE2
NE3
NE4
: ASON NE
: LSP

Board Configuration
To meet the previously mentioned service requirement, you can configure the boards as shown
in Figure 1-83.
W
S
D
9
S
C
C
F
I
U
O
B
U
1
W
S
D
9
L
D
G
D
O
A
U
1
O
B
U
1
F
I
U
S
C
C
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
R
M
U
9
S
C
C
L
O
G
L
D
G
D
O
B
U
1
F
I
U
S
C
1
O
A
U
1
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
W
S
D
9
R
M
U
9

Service Planning
To meet the service requirement, you can refer to Table 1-34 to plan a silver service.
Table 1-34 Silver service planning
Attribute NE1<->NE3
Source NE NE1
Issue 02 (2010-09-24)
Attribute NE1<->NE3
Source board-port Shelf0(Master
Shelf)-2-LDGD-1
(IN/OUT)
Shelf1(Slave
Shelf1)-1-LOG-1
(IN/OUT)
Shelf1(Slave
Shelf1)-2-
LDGD-1(IN/
OUT)
Source Wavelength 2 42 68
Sink NE NE3
Sink board-port Shelf0(Master
Shelf)-2-LDGD-1
(IN/OUT)
Shelf1(Slave
Shelf1)-1-LOG-1
(IN/OUT)
Shelf1(Slave
Shelf1)-2-
LDGD-1(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 an WDM ASON trail is created, do as follows:
1. Choose Configuration > WDM ASON > ASON Trail Management from the main
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 an 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: NE1-NE9-1-Shelf1(Slave Shelf1)-2-LDGD-1(IN1/
OUT1)-68/1555.75/192.700
Sink: NE3-NE9-3-Shelf1(Slave Shelf1)-2-LDGD-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:
1-163
menu. Perform filter and confirmation.
2. Select an 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
1.7.27 Deactivating the WDM ASON Trail
Deactivating an ASON trail can release the resources that the trail occupies.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
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.
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 (not less than 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.
If the trails to be deactivated contain associated trails, the NMS cancels the trail association before
deactivating them. Detailed situations are as follows:
l If the trail association fails to be canceled, the NMS stops the deactivation and reports the failure of
canceling the association.
l If the trail association is canceled successfully but the deactivation fails, the NMS reports the
deactivation failure and the successful association cancelation.
l If the trail association is canceled and the trails are deactivated successfully, the NMS reports that the
deactivation is successful.
l If a trail is deactivated successfully but the associated trail fails to be deactivated, the NMS reports that
the operation is partially successful and the association is canceled for the trail failing to be deactivated.
Issue 02 (2010-09-24)
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
1.7.28 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 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 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
1.8 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.
1.8.1 Viewing WDM ASON Trail Attributes
You can view the detailed information of an WDM ASON trail, including the basic attributes,
constraint routes and SLA-compliant.
1.8.2 Viewing the Optical Power of a WDM ASON Trail
You can query the optical power for WDM ASON trails. The U2000 provides a way to manage
the optical power that is related to the NE layout, topology structure, and routing.
1.8.3 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.
1-165
1.8.4 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.
1.8.5 Setting the SD Alarm to Trigger Rerouting
The WDM ASON ODU2 trail, WDM ASON ODU1 trail, and WDM ASON client trail support
the rerouting upon the SD alarm.
1.8.6 Setting Preset Restoration Trail
You can specify restoration trails for an ASON service in advance and specify the priorities of
the two restoration trails. When a WDM ASON service is rerouted, the service is restored
preferentially to the preset restoration trail with priority 1. If the preset restoration trail with
priority 1 is occupied, the service is restored to the preset restoration trail with priority 2. If the
two preset restoration trails are occupied, the U2000 calculates a new route.
1.8.7 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.
1.8.1 Viewing WDM ASON Trail Attributes
You can view the detailed information of an WDM ASON trail, including the basic attributes,
constraint routes and SLA-compliant.
Prerequisite
l A WDM ASON trail must be created.
Procedure
Step 2 In the trail list, right-click the WDM 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 WDM ASON trail.
Issue 02 (2010-09-24)
Step 4 Click the Restrictive Route tab. View the route constraint information of the WDM ASON
trail.
Step 5 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 6 Click the SLA-Compliant Details tab to view the details of the SLA-compliant of the WDM
ASON trail.
Step 7 Optional: If the trail is a gold WDM ASON trail, click Section ID tab to view the detailed ID
information of the WDM ASON trail section.
----End
1.8.2 Viewing the Optical Power of a WDM ASON Trail
You can query the optical power for WDM ASON trails. The U2000 provides a way to manage
the optical power that is related to the NE layout, topology structure, and routing.
Prerequisite
l You must be an NM user with "network monitor" authority or higher.
l The WDM ASON trails must be correctly created.
1-167
Procedure
Step 2 In the Filter dialog box, click Filter All.
Step 3 Select the WDM ASON trail to query, click Maintenance and select Refresh Signal Flow from
the drop-down list.
Step 4 The Operation Result dialog box is displayed, indicating that the operation is successful. Click
Close.
Step 5 Select the preceding ASON trail, right-click, and choose Query Relevant Optical Power from
the shortcut menu.
Step 6 In the Optical Power Management dialog box, click the Port Optical Power tab and click
Query. In the Operation Result dialog box, click Close.
Step 7 Optional: Click Legend. In the Legend dialog box, view the mapping relationships between
Alert and Color to determine whether the optical power is proper.
Step 8 Click the Graphic tab to query the graphic interface of the port optical power.
NOTE
l Green indicates that the current optical power is in the normal range.
l Orange indicates that the current power exceeds the reference deviation and there is an exception.
l Black "E" shape in the histogram indicates the allowable deviation range of the optical power.
----End
1.8.3 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.
Issue 02 (2010-09-24)
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.
l Revertive Mode includes Non-Revertive, Automatically Revertive and Scheduled Revertive.
Step 4 Click Close in the Operation Result dialog box.
----End
1.8.4 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
1-169
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
You can set Scheduled revertive time only when the revertive mode is set to 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
1.8.5 Setting the SD Alarm to Trigger Rerouting
The WDM ASON ODU2 trail, WDM ASON ODU1 trail, and WDM ASON client trail support
the rerouting upon the SD alarm.
Prerequisite
l An ASON NE must be configured and the NE data must be uploaded.
l It is applicable for the WDM ASON ODU2 trail, WDM ASON ODU1 trail, and WDM
ASON client trail.
Procedure
Step 3 In Set Routing Attributes, set ROUTE BY SD ALARM to Yes.
Step 4 Set the other items according to the actual planning information. Then, 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.
Step 5 Then, another dialog box is displayed indicating that the operation is successful. Click Close.
----End
Issue 02 (2010-09-24)
1.8.6 Setting Preset Restoration Trail
You can specify restoration trails for an ASON service in advance and specify the priorities of
the two restoration trails. When a WDM ASON service is rerouted, the service is restored
preferentially to the preset restoration trail with priority 1. If the preset restoration trail with
priority 1 is occupied, the service is restored to the preset restoration trail with priority 2. If the
two preset restoration trails are occupied, the U2000 calculates a new route.
Prerequisite
l The rerouting ASON trail must be created.
l The U2000 must have synchronized TE links on the entire network and have sufficient TE
link resources.
CAUTION
Currently, the diamond, gold, and silver WDM ASON trails support the function of setting the
restoration reverting trail.
If you want to modify the preset restoration trail, first, you must delete the trail to be modified ,
then set the preset restoration trail again. In the delete preset restoration trail dialog box, you can
delete the trail 1, trail 2 or all of the trails.
Procedure
Step 2 Select an ASON WDM trail, click Maintenance, and select Set Preset Restoration Trail from
the drop-down list.
Step 3 Set the preset restoration trail 1 as follows:
1. Click Preset Restoration Trail and select Preset Restoration Trail 1 from the drop-down
list.
NOTE
For the ASON NE version with GSP V100R002 or a prior version. you can set only one preset restoration
trail and the trail is Preset Restoration Trail 1 by default. You can not set the priority.
2. Click Priority and select 1 from the drop-down list.
3. Click Pre-Calculation Route to view relevant information. Click Apply.
NOTE
If the Automatic Pre-Calculation check box is selected, the U2000 issues a command to NEs for
automatically precalculating a route. Any change to route constraints triggers automatic
precalculation.
The priority must set to 1 or 2. The priority of the preset restoration trail 1 and 2 can be the same. If
the ASON trail interrupted, the preset restoration trail which priority is 1 would restore first.
Step 4 Optional: Set the preset restoration trail 2 as the Step 3.
1-171
NOTE
For the ASON NE version with GSP V100R004 or a later version, you can set two preset restoration trails.
Step 5 Optional: On the topology, right-click an NE and set the route constraints, including Explicit
Node, Excluded Node, Explicit Link, and Excluded Link
Step 6 Optional: Click the Route Restriction tab to view or set the information about Explicit
Node and Excluded Node.
Step 7 Click Apply.
----End
1.8.7 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
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 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
1.9 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.
1.9.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. The automatic reverting, however, is not supported.
1.9.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.
Issue 02 (2010-09-24)
1.9.3 Optimizing a WDM ASON OCh Trail
To manually adjust one or more WDM ASON OCh trails, you can use the optimization function
to transfer the WDM ASON OCh trails to the expected trails.
1.9.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.
1.9.5 Optimizing WDM ASON Client Trail
To manually adjust one or more WDM ASON Client trails, you can use the optimization function
to transfer the WDM ASON Client trails to the expected trails.
1.9.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. The automatic reverting, however, is not supported.
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
1.9.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.
1-173
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, you can only click Revert To
Wavelength to perform the restoration.
----End
1.9.3 Optimizing a WDM ASON OCh Trail
To manually adjust one or more WDM ASON OCh trails, you can use the optimization function
to transfer the WDM ASON OCh trails to the expected trails.
Prerequisite
l A WDM ASON OCh trail must be created.
l For a revertive silver WDM OCh trail, you cannot perform the optimization operation when
the service is being reverted upon rerouting.
l Diamond and non-diamond WDM OCh trail cannot be optimized in batches at the same
time.
l ASON WDM OCh trail in different domains do not support optimization 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 Specify the explicit nodes, explicit links, excluded nodes, or excluded links to set the trail after
optimization.
Issue 02 (2010-09-24)
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
1.9.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.
1-175
l Diamond and non-diamond WDM ODUk trail cannot be optimized in batches at the same
time.
l WDM ASON ODUk trail in different domains do not support optimization in batches.
l ODU0, ODU1,ODU2 and ODU3 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
optimization.
Step 4 Check whether the route adjustment is correctly set and then click Apply.
information of the WDM ASON ODUk trail after optimization in the Actual Route.
----End
1.9.5 Optimizing WDM ASON Client Trail
To manually adjust one or more WDM ASON Client trails, you can use the optimization function
to transfer the WDM ASON Client trails to the expected trails.
Prerequisite
l A WDM ASON client trail must be created.
Context
l For a revertive silver WDM client trail, you cannot perform the optimization operation
when the service is being reverted upon rerouting.
l Diamond and non-diamond WDM Client trail cannot be optimized in batches at the same
time.
l WDM ASON Client trail in different domains do not support optimization in batches.
l Client 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 Client trails that you want to adjust. Click
Issue 02 (2010-09-24)
optimization.
Step 4 Check whether the route adjustment is correctly set and click Apply.
information of the WDM ASON Client trail after optimization in the Actual Route.
----End
1.10 Migrating WDM ASON Trails
An ASON network supports the migration between traditional trails and ASON trails, and
supports the in-line migration between ASON trails at different levels.
1-177
Context
NOTE
l The optical-layer WDM ASON OCh trail does not support in-line migration.
l The migration between electrical-layer gold WDM ASON trails and diamond WDM ASON trails is
not supported.
1.10.1 Downgrading a WDM ASON Trail to a Traditional WDM Trail
You can downgrade a WDM ASON trail at diamond, gold, silver or copper level to a traditional
WDM trail. This is applicable to network reconstruction, expansion and upgrade.
1.10.2 Upgrading a Traditional WDM Trail to an WDM ASON Trail
During network upgrade, expansion, and reconstruction, you can upgrade a traditional WDM
trail to an WDM ASON trail. The WDM ASON trail is classified into OCh, ODUk, and Client
trails.
1.10.3 Migration Between the Diamond and Silver or Copper WDM ASON Trails
The migration between the diamond WDM ASON trail and silver or copper WDM ASON trail
can be performed.
1.10.4 Migration Between the Gold and Silver or Copper WDM ASON Trails
The migration between the gold WDM ASON trail and silver or copper WDM ASON trail can
be performed.
1.10.5 Migration Between the Silver and Copper WDM ASON Trails
The migration between the silver WDM ASON trail and copper electrical-layer WDM ASON
trail can be performed.
1.10.1 Downgrading a WDM ASON Trail to a Traditional WDM
Trail
You can downgrade a WDM ASON trail at diamond, gold, 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 Migration 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.
Issue 02 (2010-09-24)
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 > Search for WDM Trail from the main menu. In the WDM
Trail Management window, manage the WDM ASON trails that are successfully
downgraded.
l Migration at the Traditional Network Layer
1. Choose Service > WDM Trail > Manage WDM Trail 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
1.10.2 Upgrading a Traditional WDM Trail to an WDM ASON Trail
During network upgrade, expansion, and reconstruction, you can upgrade a traditional WDM
trail to an WDM ASON trail. The WDM ASON trail is classified into OCh, ODUk, and Client
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.
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.
l Only the OCh trail in the intra-board 1+1 protection group can be upgraded to a diamond WDM ASON OCh
trail.
1-179
Procedure
Step 1 Choose Service > WDM Trail > Manage WDM Trail from the main menu.
Step 2 In the Set Trail Browse Filter Criteria 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 an WDM trail to be upgraded, right-click and choose Upgrade 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.
Issue 02 (2010-09-24)
Step 6 Select the trail that you want to upgrade and click OK.
Step 7 Click OK in the confirmation dialog box.
Step 8 A prompt is displayed indicating that the operation is successful. ClickOK.
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
1.10.3 Migration Between the Diamond and Silver or Copper WDM
ASON Trails
The migration between the 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 In the case of the optical-layer WDM ASON OCh trails, the conversion is not supported.
l In the case of the electrical-layer WDM ASON trails, conversion between the gold and
diamond levels are not supported.
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.
1-181
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
1.10.4 Migration Between the Gold and Silver or Copper WDM
ASON Trails
The migration between the gold WDM ASON trail and silver or copper WDM ASON trail can
be performed.
Prerequisite
l Associated WDM ASON trails cannot be converted into gold WDM ASON trails.
l In the case of the electrical-layer WDM ASON trails, conversion between the gold and
diamond levels are not supported.
l This section describes how to convert the gold WDM ASON trail into silver WDM ASON
trail. The conversion between the gold and copper WDM ASON trails and the conversion
between the copper and silver WDM ASON trails are similar.
Procedure
Issue 02 (2010-09-24)
Step 2 In the list displayed, right-click the desired gold service and choose In-Service Migration >
Silver from the shortcut menu.
Step 4 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
1.10.5 Migration Between the Silver and Copper WDM ASON
Trails
The migration between the silver WDM ASON trail and copper electrical-layer 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
1.11 Creating Services Between an ASON NE and a
Traditional NE
A network can consist of ASON NEs and traditional NEs. This realizes end-to-end service
configuration and management.
1.11.1 Creating a OCh Trail Between Traditional NEs that Cross an ASON Domain
You can create end-to-end OCh trails between traditional NEs that cross an ASON domain.
1.11.2 Creating a ODU0 Trail Between Traditional NEs that Cross an ASON Domain
1-183
You can create end-to-end ODU0 trail between traditional NEs that cross an ASON domain.
1.11.5 Creating a Client Trail Between Traditional NEs that Cross an ASON Domain
You can create end-to-end Client trail between traditional NEs that cross an ASON domain.
1.11.6 Creating a OCh Trail Between a Traditional NE and an ASON NE
You can create end-to-end OCh Trail between traditional NEs and ASON NEs.
1.11.7 Creating a ODU0 Trail Between a Traditional NE and an ASON NE
You can create end-to-end ODU0 Trail between traditional NEs and ASON NEs.
1.11.10 Creating a Client Trail Between a Traditional NE and an ASON NE
You can create end-to-end Client Trail between traditional NEs and ASON NEs.
1.11.11 Creating 1+1 OCh Trails Between Traditional NEs That Cross an ASON Domain
You can create 1+1 OCh trails between traditional NEs that cross an ASON domain.
1.11.12 Creating 1+1 ODU0 Trails Between Traditional NEs That Cross an ASON Domain
You can create 1+1 ODU0 trails between traditional NEs that cross an ASON domain.
1.11.15 Creating 1+1 Client Trails Between Traditional NEs That Cross an ASON Domain
1.11.16 Creating the 1+1 OCh Trails Between a Traditional NE and an ASON NE
The 1+1 OCh Trails can be configured between a traditional NE and an ASON NE.
1.11.17 Creating the 1+1 ODU0 Trails Between a Traditional NE and an ASON NE
The 1+1 ODU0 Trails can be configured between a traditional NE and an ASON NE.
1.11.20 Creating the 1+1 Client Trails Between a Traditional NE and an ASON NE
The 1+1 Client Trails can be configured between a traditional NE and an ASON NE.
1.11.21 Creating Client Trail between ASON NE and Traditional NE
If there are OCh trail but not server trail of client between traditional NE and ASON NE, you
also can create client trail . The U2000 will create the server tail automatically. Then the server
trail of client trail is ASON-WDM trail.
Issue 02 (2010-09-24)
1.11.1 Creating a OCh Trail Between Traditional NEs that Cross an
ASON Domain
You can create end-to-end OCh trails between traditional NEs that cross an ASON domain.
Prerequisite
l ASON NEs must be configured.
l There must be server trail of OCh trail, such as fiber, OTS or OMS.
Service Requirement
See Figure 1-84. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.
A OCh 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 1-84 OCh trail requirement between traditional NEs
NE1
NE2 NE3
NE4
: ASON NE
: Traditional NE
NE6
NE5
OCh
OCh

Board Configuration
Figure 1-85 shows how the boards are configured on NE1, NE2, NE3 and NE4.
1-185
Figure 1-85 Board configuration for NE1-NE4
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Figure 1-86 shows how the boards are configured on NE5 and NE6.
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
You can refer to Table 1-35 and Table 1-36 to plan a service.
Table 1-35 OCh trail planning between NE1 and NE4
Attribute NE1<->NE4
Source NE NE1
Source board-port Shelf0(Master Shelf)-8-FIU
Source Wavelength 2
Sink NE NE4
Sink board-port Shelf0(Master Shelf)-5-FIU
1-187
Attribute NE1<->NE4
Sink Wavelength 2
Service route Automatically calculated by the system
ASON service type Silver
Traditional service type Unprotected

Table 1-36 Optical Cross-Connection planning for NE5 and NE6
Attribute NE5 NE6
Source board-Port Shelf0(Master Shelf)-12-NS3-1
(IN/OUT)
Shelf0(Master Shelf)-12-NS3-1
(IN/OUT)
Source Wavelength 2 2
Sink Board-Port 8-FIU-1(IN/OUT) 5-FIU-1(IN/OUT)
Sink Wavelength 2 2

You can use the following way to create a OCh trail between traditional NEs that cross an ASON
domain.
Create a silver service within the ASON domain. Then create OCh cross-connections on NE5
and NE6.
Procedure
l Name: NE1-NE4-ASON-Trail-0001
l Level OCh
l Rate: -
l Class: Silver
l Source: NE1-Shelf0(Master Shelf)-8-FIU-1(IN/OUT)-2/1529.55/196.000
l Sink: NE4-Shelf0(Master Shelf)-5-FIU-1(IN/OUT)-2/1529.55/196.000
Issue 02 (2010-09-24)
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
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.
Step 6 Set the sink NE. In the right-hand topology, double-click the sink NE and select a slot, port and
channel 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 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.
Step 9 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 10 Select the NE5 icon in the Main Topology. Right-click and choose NE Explorer from the
shortcut menu.
Step 11 Choose Configuration > Optical Cross-Connection Management from the Function Tree,
click Single-Station Optical Cross-Connection tab.
Step 12 Click New and enter the following optical cross-connection information about NE1:
l Source Slot: Shelf0(Master Shelf)-12-NS3
l Source Port: 1(IN/OUT)
l Source Band: C
l Source Wavelength No.: 2
l Sink Slot: Shelf0(Master Shelf)-8-FIU
l Sink Port: 1(IN/OUT)
l Sink Band: C
l Sink Wavelength No.: 2
Step 13 Click Apply. After the optical cross-connection is created, a dialog box is displayed indicating
that the operation is successful.
Step 14 According to the service planning, repeat Steps 10-13 to create another optical cross-connection
service of NE5.
1-189
Step 15 Choose Service > WDM Trail > Search for WDM Trail from the main menu. Click Next one
after another until the search is complete. Check whether the trail is created successfully in the
WDM Trail Management window.
Step 16 Choose Service > WDM Trail > Manage WDM Trail from the main menu. Click Filter and
choose Filter All. Check the detailed information about the trail that is created.
Then, you can view the ASON trail information.
----End
1.11.2 Creating a ODU0 Trail Between Traditional NEs that Cross
an ASON Domain
Prerequisite
l There must be server trail of ODU0 trail, such as ODU3, ODU2 or ODU1.
T32.
Service Requirement
A ODU0 trail needs to be configured between NE5 and NE6. This service is required to be an
Figure 1-87 ODU0 trail requirement between traditional NEs
NE1
NE2 NE3
NE4
NE6
NE5
ODU0
ODU0
: ASON NE
: Traditional NE

Board Configuration
Issue 02 (2010-09-24)
FAN
FAN
Slave Subrack1
E F I 2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
FAN
FAN
Master Subrack
EFI2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
N
1
S
L
O
1
6
A
N
1
S
L
O
1
6
A
F
I
U
O
B
U
1
O
A
U
1
R
M
U
1
2
W
S
D
9
5
1
S
C
C
1
2
W
S
D
9
R
M
U
5
1
S
C
C
1
2
S
C
2
O
A
U
1
O
B
U
1
F
I
U
1
2
W
S
D
9
O
A
U
1
O
B
U
1
1
2
W
S
D
9
R
M
U
1
2
S
C
1
L
D
M
D
F
I
U
R
M
U
1
2
W
S
D
9
R
M
U
5
1
S
C
C
5
2
N
Q
2
F
I
U
5
2
N
Q
2

1-191
FAN
FAN
Slave Subrack1
E F I 2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
FAN
FAN
Master Subrack
EFI2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
N
1
S
L
O
1
6
A
N
1
S
L
O
1
6
A
F
I
U
O
B
U
1
O
A
U
1
R
M
U
1
2
W
S
D
9
5
1
S
C
C
1
2
W
S
D
9
R
M
U
5
1
S
C
C
1
2
S
C
2
O
A
U
1
O
B
U
1
F
I
U
1
2
W
S
D
9
O
A
U
1
O
B
U
1
1
2
W
S
D
9
R
M
U
1
2
S
C
1
L
D
M
D
F
I
U
R
M
U
1
2
W
S
D
9
R
M
U
5
1
S
C
C
5
2
N
Q
2
F
I
U
5
2
N
Q
2

Issue 02 (2010-09-24)
Service Planning
You can refer to Table 1-37 to plan a service.
Table 1-37 ODU0 trail planning between traditional NEs
Attribute NE6<->NE5
Source NE NE6
Source board-port Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/
ODU0LP2)
Source Channel 1
Sink NE NE5
Sink board-port Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/
ODU0LP2)
Source Channel 1

You can use the following two ways to create a ODU0 trail between traditional NEs that cross
an ASON domain.
l Use the trail feature of the U2000 to directly create a ODU0 trail.
l Create a silver service within the ASON domain. Then create ODU0 cross-connections on
NE5 and NE6.
The following illustrates how to create such a ODU0 trail in the first way.
Procedure
Step 2 Choose Create/Modify > Create Trail.
Step 3 Enter the service information as follows:
l Level: ODU0
l Rate: ODU0
l Source: NE6-Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/ODU0LP2)-1
l Sink: NE5-Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/ODU0LP2)-1
Step 4 Check the SPC First check box. Click ASON Attributes Settings tab and choose the Silver
protection type.
1-193
l Lockout: Unlocked
l Priority: 2
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 selectFilter All.
Step 7 Choose Service > WDM Trail > Manage WDM Trail from the main menu. View the detailed
route information of the WDM 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
an ASON Domain
Prerequisite
l There must be server trail of ODU1 trail, such as ODU2 or OTU1.
Service Requirement
Issue 02 (2010-09-24)
NE1
NE2 NE3
NE4
NE6
NE5
ODU1
ODU1
: ASON NE
: Traditional NE

Board Configuration
1-195
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Attribute NE6<->NE5
Source NE NE6
Source board-port Shelf0(Master Shelf)-13-TDG-201(LP/LP)-1
Sink NE NE5
Sink board-port Shelf0(Master Shelf)-13-TDG-201(LP/LP)-1
1-197
Attribute NE6<->NE5

an ASON domain.
NE5 and NE6.
Procedure
l Level: ODU1
l Rate: ODU1
l Source: NE6-Shelf0(Master Shelf)-13-TDG-201(LP/LP)-1
l Sink: NE5-Shelf0(Master Shelf)-13-TDG-201(LP/LP)-1
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
Issue 02 (2010-09-24)
----End
an ASON Domain
Prerequisite
l There must be server trail of ODU2 trail, such as ODU3 and OTU2.
Service Requirement
NE1
NE2 NE3
NE4
NE6
NE5
ODU2
ODU2
: ASON NE
: Traditional NE

Board Configuration
1-199
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Attribute NE6<->NE5
Source NE NE6
Source board-port Shelf0(Master Shelf)-1-12NS2-71(ODU2LP/
ODU2LP)-1
Sink NE NE5
Sink board-port Shelf0(Master Shelf)-1-12NS2-71(ODU2LP/
ODU2LP)-1
1-201
Attribute NE6<->NE5

an ASON domain.
NE5 and NE6.
Procedure
l Level: ODU2
l Rate: Standard Mode
l Source: NE6-Shelf0(Master Shelf)-1-12NS2-71(ODU2LP/ODU2LP)-1
l Sink: NE6-Shelf0(Master Shelf)-1-12NS2-71(ODU2LP/ODU2LP)-1
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
Issue 02 (2010-09-24)
----End
1.11.5 Creating a Client Trail Between Traditional NEs that Cross
an ASON Domain
You can create end-to-end Client trail between traditional NEs that cross an ASON domain.
Prerequisite
l There must be server trail of Client trail, such as OCh, ODU2, ODU5G, ODU1 and ODU0.
Service Requirement
A Client trail needs to be configured between NE5 and NE6. This service is required to be an
Figure 1-96 Client trail requirement between traditional NEs
NE1
NE2 NE3
NE4
NE6
NE5
Client
Client
: ASON NE
: Traditional NE

Board Configuration
1-203
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Table 1-40 Client trail planning between traditional NEs
Attribute NE6<->NE5
Source NE NE6
Source board-port Shelf0(Master Shelf)-3-L4G-101(AP1/AP1)
Sink NE NE5
Sink board-port Shelf0(Master Shelf)-3-L4G-101(AP1/AP1)
1-205
Attribute NE6<->NE5

You can use the following two ways to create a Client trail between traditional NEs that cross
an ASON domain.
l Use the trail feature of the U2000 to directly create a Client trail.
l Create a silver service within the ASON domain. Then create Client cross-connections on
NE5 and NE6.
The following illustrates how to create such a Client trail in the first way.
Procedure
l Level: Client
l Rate: GE
l Source: NE6-Shelf0(Master Shelf)-3-L4G-101(AP1/AP1)
l Sink: NE6-Shelf0(Master Shelf)-3-L4G-101(AP1/AP1)
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
Issue 02 (2010-09-24)
----End
1.11.6 Creating a OCh Trail Between a Traditional NE and an ASON
NE
You can create end-to-end OCh Trail between traditional NEs and ASON NEs.
Prerequisite
Service Requirement
A OCh trail needs to be configured between NE1 and NE5. This service is required to be an
Figure 1-99 OCh trail requirement between traditional and ASON NEs
NE1
NE2 NE3
NE4
NE6
NE5
OCh
OCh
: ASON NE
: Traditional NE
Board Configuration
1-207
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Table 1-41 Silver ASON Trail planning between NE1 and NE4
Attribute NE1<->NE4
Source NE NE1
Source Board-Port Shelf0(Master Shelf)-12-NS3-1(IN/OUT)
Source Wavelength 2
Sink NE NE4
Sink Board-Port Shelf0(Master Shelf)-5-FIU
1-209
Attribute NE1<->NE4
Sink Wavelength 2

Table 1-42 Optical Cross-Connection planning of NE5
Attribute NE5
Source Board-Port Shelf0(Master Shelf)-12-NS3-1(IN/OUT)
Source Wavelength 2
Sink Board-Port Shelf0(Master Shelf)-8-FIU-1(IN/OUT)
Sink Wavelength 2

You can use the following way to create a OCh trail between a traditional NE and an ASON
NE.
Create a silver service within the ASON domain. Then create OCh cross-connections on NE5.
Procedure
l Level OCh
l Rate: -
l Class: Silver
l Source: NE1-Shelf0(Master Shelf)-12-NS3-1(IN/OUT)-2/1529.55/196.000
l Lockout: Unlocked
Issue 02 (2010-09-24)
l Priority: 2
l CrankBack: 1
NOTE
shortcut menu.
again from Step 1.
l Source Band: C
l Sink Band: C
l Sink Wavelength No.: 2
1-211
----End
1.11.7 Creating a ODU0 Trail Between a Traditional NE and an
ASON NE
Prerequisite
T32.
Service Requirement
Figure 1-102 ODU0 trail requirement between traditional and ASON NEs
NE1
NE2 NE3
NE4
NE6
NE5
ODU0
ODU0
: ASON NE
: Traditional NE
Board Configuration
Issue 02 (2010-09-24)
FAN
FAN
Slave Subrack1
E F I 2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
FAN
FAN
Master Subrack
EFI2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
N
1
S
L
O
1
6
A
N
1
S
L
O
1
6
A
F
I
U
O
B
U
1
O
A
U
1
R
M
U
1
2
W
S
D
9
5
1
S
C
C
1
2
W
S
D
9
R
M
U
5
1
S
C
C
1
2
S
C
2
O
A
U
1
O
B
U
1
F
I
U
1
2
W
S
D
9
O
A
U
1
O
B
U
1
1
2
W
S
D
9
R
M
U
1
2
S
C
1
L
D
M
D
F
I
U
R
M
U
1
2
W
S
D
9
R
M
U
5
1
S
C
C
5
2
N
Q
2
F
I
U
5
2
N
Q
2

1-213
FAN
FAN
Slave Subrack1
E F I 2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
FAN
FAN
Master Subrack
EFI2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
N
1
S
L
O
1
6
A
N
1
S
L
O
1
6
A
F
I
U
O
B
U
1
O
A
U
1
R
M
U
1
2
W
S
D
9
5
1
S
C
C
1
2
W
S
D
9
R
M
U
5
1
S
C
C
1
2
S
C
2
O
A
U
1
O
B
U
1
F
I
U
1
2
W
S
D
9
O
A
U
1
O
B
U
1
1
2
W
S
D
9
R
M
U
1
2
S
C
1
L
D
M
D
F
I
U
R
M
U
1
2
W
S
D
9
R
M
U
5
1
S
C
C
5
2
N
Q
2
F
I
U
5
2
N
Q
2

Issue 02 (2010-09-24)
Service Planning
Table 1-43 ODU0 trail planning between traditional NE and ASON NE
Attribute NE1<->NE5
Source NE NE1
Source board-port Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/
ODU0LP2)
Source Channel 1
Sink NE NE5
Sink board-port Shelf1(Slave Shelf1)-21-52NQ2-162(ODU0LP2/
ODU0LP2)
Sink Channel 1
Level ODU0

You can use the following two ways to create a ODU0 trail between a traditional NE and an
ASON NE.
NE5.
Procedure
l Level: ODU0
l Rate: ODU0
protection type.
1-215
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
----End
ASON NE
Prerequisite
Service Requirement
Issue 02 (2010-09-24)
NE1
NE2 NE3
NE4
NE6
NE5
ODU1
ODU1
: ASON NE
: Traditional NE
Board Configuration
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D
1-217

S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Attribute NE1<->NE5
Source NE NE1
Source board-port Shelf0(Master Shelf)-13-TDG-201(LP/LP)-1
Sink NE NE5
Issue 02 (2010-09-24)
Attribute NE1<->NE5
Sink board-port Shelf0(Master Shelf)-13-TDG-201(LP/LP)-1

ASON NE.
NE5.
Procedure
l Level: ODU1
l Rate: ODU1
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
1-219
----End
ASON NE
Prerequisite
Service Requirement
NE1
NE2 NE3
NE4
NE6
NE5
ODU2
ODU2
: ASON NE
: Traditional NE
Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-221
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Attribute NE1<->NE5
Source NE NE1
Source board-port-channel Shelf0(Master Shelf)-1-12NS2-71(ODU2LP/
ODU2LP1)-1
Sink NE NE5
Sink board-port-channel Shelf0(Master Shelf)-1-12NS2-71(ODU2LP/
ODU2LP1)-1
Issue 02 (2010-09-24)
Attribute NE1<->NE5

ASON NE.
NE5.
Procedure
l Level: ODU2
l Rate: Standard Mode
l Source: NE1-Shelf0(Master Shelf)-1-12NS2-71(ODU21LP/ODU2LP1)-1
l Sink: NE5-Shelf0(Master Shelf)-1-12NS2-71(ODU2LP/ODU2LP1)-1
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
1-223
----End
1.11.10 Creating a Client Trail Between a Traditional NE and an
ASON NE
You can create end-to-end Client Trail between traditional NEs and ASON NEs.
Prerequisite
Service Requirement
A Client trail needs to be configured between NE1 and NE5. This service is required to be an
Figure 1-111 Client trail requirement between traditional and ASON NEs
NE1
NE2 NE3
NE4
NE6
NE5
Client
Client
: ASON NE
: Traditional NE
Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-225
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Table 1-46 Client trail planning between traditional NE and ASON NE
Attribute NE1<->NE5
Source NE NE1
Sink NE NE5
Issue 02 (2010-09-24)
Attribute NE1<->NE5

You can use the following two ways to create a Client trail between a traditional NE and an
ASON NE.
l Use the trail feature of the U2000 to directly create a Client trail.
l Create a silver service within the ASON domain. Then create Client cross-connections on
NE5.
The following illustrates how to create such a Client trail in the first way.
Procedure
l Level: Client
l Rate: GE
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
1-227
----End
1.11.11 Creating 1+1 OCh Trails Between Traditional NEs That
Cross an ASON Domain
You can create 1+1 OCh trails between traditional NEs that cross an ASON domain.
Prerequisite
Service Requirement
As shown in Figure 1-114, NE1, NE2, NE3, and NE4 are ASON NEs whereas NE5 and NE6
are traditional NEs. A 1+1 OCh trail 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 1-114 1+1 OCh trail requirement between traditional NEs
NE1
NE2 NE3
NE4
NE6
NE5
OCh
OCh
: ASON NE
: Traditional NE
: Working Trail
: Protection trail

Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-229
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Refer to Table 1-47, Table 1-48 and Table 1-49 for service planning.
Table 1-47 Planning of Two Silver ASON Trails
Attribute NE1<->NE4 NE2<->NE3
Source NE NE1 NE2
Source Board-Port Shelf0(Master Shelf)-8-
FIU-1(IN1/OUT1)
Shelf0(Master Shelf)-5-
FIU-1(IN1/OUT1)
Sink NE NE4 NE3
Issue 02 (2010-09-24)
Sink Board-Port Shelf0(Master Shelf)-5-
FIU-1(IN1/OUT1)
FIU-1(IN1/OUT1)
Sink Wavelength 2 2
Protection type Silver Silver
Service type ASON trail ASON trail
Trail type Working trail Protection trail

Table 1-48 Intra-Board 1+1 Protection planning of NE5
Attribute Working Protection
Source Board Shelf3(Slave Shelf3)-1-
LDGD
Shelf3(Slave Shelf3)-1-
LDGD
Source Port 1(IN1/OUT1) 2(IN2/OUT2)
Sink Board Shelf0(Master Shelf)-8-FIU Shelf0(Master Shelf)-5-FIU
Sink Port 1(IN1/OUT1) 1(IN1/OUT1)
Sink Wavelength 2 2

Table 1-49 Intra-Board 1+1 Protection planning of NE6
Attribute Working Protection
Source Board Shelf3(Slave Shelf3)-1-
LDGD
Shelf3(Slave Shelf3)-1-
LDGD
Sink Wavelength 2 2

The two ways of creating 1+1 VC4 services between traditional NEs that cross an ASON domain
are as follows:
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 optical cross-connections for NE5.
1-231
Procedure
l Level OCh
l Rate: -
l Class: Silver
l Source: NE1-Shelf0(Master Shelf)-8-FIU-1(IN/OUT)-2/1529.55/196.000
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
again from Step 1.
Step 10 According to the service planning, repeat Steps 3-9 to create the silver service between NE2 and
NE3.
Issue 02 (2010-09-24)
Step 11 Click Cancel to return to the WDM 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.
shortcut menu.
Step 13 Choose Configuration > Port Protection from the Function Tree. Click New.
Step 14 Click OK, and enter the following port protection information about NE5:
l Protection Type: Intra-Board 1+1 Protection
l Board with Working Channel: Shelf3(Slave Shelf3)-1-LDGD
l Working Channel: 1(IN1/OUT1)
l Board with Protection Channel: Shelf3(Slave Shelf3)-1-LDGD
l Protection Channel: 2(IN1/OUT1)
Step 15 Click OK. If the creation is successful, a dialog box is displayed indicating that the operation is
Step 16 According to the service planning, repeat Steps 12-15 to create the port protection of NE6.
l Source Slot: Shelf3(Slave Shelf3)-1-LDGD
l Source Band: C
l Sink Band: C
l Sink Wavelength: 2
Step 20 According to the service planning, repeat Steps 17-19 to create optical cross-connection of NE5
and NE6.
----End
1-233
1.11.12 Creating 1+1 ODU0 Trails Between Traditional NEs That
Prerequisite
T32.
Service Requirement
are traditional NEs. A 1+1 ODU0 trail needs to be configured between NE5 and NE1. To
Figure 1-117 1+1 ODU0 trail requirement between traditional NEs
NE1
NE2 NE3
NE4
NE6
NE5
ODU0
ODU0
: ASON NE
: Traditional NE
: Working Trail
: Protection trail
Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-235
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Source NE NE1 NE1
Source Slot Shelf1(Slave Shelf1)-22-52NQ2 Shelf1(Slave Shelf1)-122-52NQ2
Source Optical
Port-Optical
Channel
161(ODU0LP1/ODU0LP1)-1 161(ODU0LP1/ODU0LP1)-1
Sink NE NE4 NE3
Issue 02 (2010-09-24)
Sink Slot Shelf1(Slave Shelf1)-22-52NQ2 Shelf1(Slave Shelf1)-22-52NQ2
Source Optical
Port-Optical
Channel
Level ODU0 ODU0

Table 1-51 SNCP service planning of NE5
Attribute Transmit direction Receive direction
Working
service
Protection
service
Working
service
Protection
service
Source Slot Shelf1(Slave Shelf1)-20-52NQ2 Shelf1(Slave
Shelf1)-
21-52NQ2
Shelf1(Slave
Shelf1)-
22-52NQ2
Source Optical
Port-Optical
Channel
161(ODU0LP1/ODU0LP1)-1 161
(ODU0LP1/
ODU0LP1)-1
161(ODU0LP1/
ODU0LP1)-1
Sink Slot Shelf1(Slave
Shelf1)-
21-52NQ2
Shelf1(Slave
Shelf1)-
22-52NQ2
Shelf1(Slave Shelf1)-20-52NQ2
Sink Optical
Port-Optical
Channel
161
(ODU0LP1/
ODU0LP1)-1
161(ODU0LP1/
ODU0LP1)-1
161(ODU0LP1/ODU0LP1)-1
Level ODU0 ODU0
Direction Unidirectional Unidirectional

Working
service
Protection
service
Working
service
Protection
service
Source Slot Shelf1(Slave Shelf1)-20-52NQ2 Shelf1(Slave
Shelf1)-
21-52NQ2
Shelf1(Slave
Shelf1)-
22-52NQ2
1-237
Working
service
Protection
service
Working
service
Protection
service
Source Optical
Port-Optical
Channel
161(ODU0LP1/ODU0LP1)-1 161
(ODU0LP1/
ODU0LP1)-1
161(ODU0LP1/
ODU0LP1)-1
Shelf1)-
21-52NQ2
Shelf1(Slave
Shelf1)-
22-52NQ2
Shelf1(Slave Shelf1)-20-52NQ2
Sink Optical
Port-Optical
Channel
161
(ODU0LP1/
ODU0LP1)-1
161(ODU0LP1/
ODU0LP1)-1
Level ODU0 ODU0

Context
The two ways of creating 1+1 ODU0 trails between traditional NEs that cross an ASON domain
are as follows:
l Use the trail function of the U2000 to create a ODU0 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 ODU0 cross-connections for
NE5 and NE6.
The following procedure describes how to 1+1 ODU0 trails between traditional NEs that cross
an ASON domain in the first way.
Procedure
l Level: ODU0
l Rate: ODU0
protection type.
Issue 02 (2010-09-24)
l Lockout: Unlocked
l Priority: 2
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.
----End
Prerequisite
Service Requirement
1-239
NE1
NE2 NE3
NE4
NE6
NE5
ODU1
ODU1
: ASON NE
: Traditional NE
: Working Trail
: Protection trail
Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-241
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Source NE NE1 NE1
Source Slot Shelf0(Master Shelf)-2-12NS2 Shelf0(Master Shelf)-2-12NS2
Source Optical
Port-Optical
Channel
1(IN/OUT)-1 1(IN/OUT)-1
Sink NE NE4 NE3
Issue 02 (2010-09-24)
Sink Slot Shelf0(Master Shelf)-2-12NS2 Shelf0(Master Shelf)-2-12NS2
Sink Optical
Port-Optical
Channel
1(IN/OUT)-1 1(IN/OUT)-1
Level ODU1 ODU1

Working
service
Protection
service
Working
service
Protection
service
Source Slot Shelf0(Master Shelf)-13-TDG Shelf0(Master
Shelf)-
1-12NS2
Shelf0(Master
Shelf)-2-12NS2
Source Optical
Port-Optical
Channel
201(LP/LP) 51(ODU1LP/
ODU1LP)-1
51(ODU1LP/
ODU1LP)-1
Sink Slot Shelf0(Master
Shelf)-
1-12NS2
Shelf0(Master
Shelf)-2-12NS2
Shelf0(Master Shelf)-13-TDG
Sink Optical
Port-Optical
Channel
51(ODU1LP/
ODU1LP)-1
51(ODU1LP/
ODU1LP)-1
201(LP/LP)
Level ODU1 ODU1

Working
service
Protection
service
Working
service
Protection
service
Source Slot Shelf0(Master Shelf)-1-12NS2 Shelf0(Master
Shelf)-
1-12NS2
Shelf0(Master
Shelf)-2-12NS2
1-243
Working
service
Protection
service
Working
service
Protection
service
Source Optical
Port-Optical
Channel
201(LP/LP) 51(ODU1LP/
ODU1LP)-1
51(ODU1LP/
ODU1LP)-1
Shelf)-
1-12NS2
Shelf0(Master
Shelf)-2-12NS2
Shelf0(Master Shelf)-13-TDG
Sink Optical
Port-Optical
Channel
51(ODU1LP/
ODU1LP)-1
51(ODU1LP/
ODU1LP)-1
201(LP/LP)
Level ODU1 ODU1

Context
are as follows:
NE5 and NE6.
Procedure
l Level: ODU1
l Rate: ODU1
protection type.
Issue 02 (2010-09-24)
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
shortcut menu.
----End
Prerequisite
Service Requirement
1-245
NE1
NE2 NE3
NE4
NE6
NE5
ODU2
ODU2
: ASON NE
: Traditional NE
: Working Trail
: Protection trail

Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-247
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Source NE NE1 NE1
Source Slot Shelf0(Master Shelf)-15-NS3 Shelf0(Master Shelf)-15-NS3
Source Optical
Port-Optical
Channel
71(ODU2LP/ODU2LP)-1 71(ODU2LP/ODU2LP)-1
Sink NE NE4 NE3
Issue 02 (2010-09-24)
Sink Slot Shelf0(Master Shelf)-15-NS3 Shelf0(Master Shelf)-15-NS3
Sink Optical
Port-Optical
Channel
Level ODU2 ODU2

Working
service
Protection
service
Working
service
Protection
service
Shelf)-12-NS3
Shelf0(Master
Shelf)-15NS3
Source Optical
Port-Optical
Channel
71(ODU2LP/ODU2LP)-1 71(ODU2LP/
ODU2LP)-1
71(ODU2LP/
ODU2LP)-1
Sink Board Shelf0(Master
Shelf)-12-NS3
Shelf0(Master
Shelf)-15NS3
Shelf0(Master Shelf)-1-12NS2
Sink Optical
Port-Optical
Channel
71(ODU2LP/
ODU2LP)-1
71(ODU2LP/
ODU2LP)-1
71(ODU2LP/ODU2LP)-1
Level ODU2 ODU2

Working
service
Protection
service
Working
service
Protection
service
Shelf)-12-NS3
Shelf0(Master
Shelf)-15NS3
Source Optical
Port-Optical
Channel
71(ODU2LP/ODU2LP)-1 71(ODU2LP/
ODU2LP)-1
71(ODU2LP/
ODU2LP)-1
1-249
Working
service
Protection
service
Working
service
Protection
service
Sink Board Shelf0(Master
Shelf)-12-NS3
Shelf0(Master
Shelf)-15NS3
Shelf0(Master Shelf)-1-12NS2
Sink Optical
Port-Optical
Channel
71(ODU2LP/
ODU2LP)-1
71(ODU2LP/
ODU2LP)-1
71(ODU2LP/ODU2LP)-1
Level ODU2 ODU2

Context
are as follows:
NE5 and NE6.
Procedure
l Level: ODU2
l Direction: Bidirectional(Mandatory)
l Rate: ODU2
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
Issue 02 (2010-09-24)
shortcut menu.
----End
1.11.15 Creating 1+1 Client Trails Between Traditional NEs That
Prerequisite
Service Requirement
are traditional NEs. A 1+1 Client trail needs to be configured between NE5 and NE1. To
1-251
Figure 1-126 1+1 Client trail requirement between traditional NEs
NE1
NE2 NE3
NE4
NE6
NE5
Client
Client
: ASON NE
: Traditional NE
: Working Trail
: Protection trail

Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-253
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Source NE NE1 NE1
Source Slot Shelf0(Master Shelf)-13-TDG Shelf0(Master Shelf)-13-TDG
Source Optical
Port-Optical
Channel
201(LP/LP)-1 201(LP/LP)-1
Sink NE NE4 NE3
Issue 02 (2010-09-24)
Sink Slot Shelf0(Master Shelf)-13-TDG Shelf0(Master Shelf)-13-TDG
Sink Optical
Port-Optical
Channel
201(LP/LP)-1 201(LP/LP)-1
Level Client Client

Working
service
Protection
service
Working
service
Protection
service
Source Slot Shelf0(Master Shelf)-3-L4G Shelf0(Master Shelf)-13-TDG
Source Optical
Port-Optical
Channel
101(AP1/AP1) 201(LP/LP)-1 201(LP/LP)-1
Sink Board Shelf0(Master Shelf)-13-TDG Shelf0(Master Shelf)-3-L4G
Sink Optical
Port-Optical
Channel
201(LP/LP)-1 201(LP/LP)-1 101(AP1/AP1)
Level Client Client

Working
service
Protection
service
Working
service
Protection
service
Source Slot Shelf0(Master Shelf)-3-L4G Shelf0(Master Shelf)-13-TDG
Source Optical
Port-Optical
Channel
101(AP1/AP1) 201(LP/LP)-1 201(LP/LP)-1
Sink Slot Shelf0(Master Shelf)-13-TDG Shelf0(Master Shelf)-3-L4G
1-255
Working
service
Protection
service
Working
service
Protection
service
Sink Optical
Port-Optical
Channel
201(LP/LP)-1 201(LP/LP)-1 101(AP1/AP1)
Level Client Client

Context
The two ways of creating 1+1 Client trail between traditional NEs that cross an ASON domain
are as follows:
l Use the trail function of the U2000 to create a Client trail.
NE5 and NE6.
The following procedure describes how to 1+1 Client trails between traditional NEs that cross
Procedure
l Level: Client
l Direction: Bidirectional(Mandatory)
l Rate: GE
l Source: NE5-Shelf0(Master Shelf)-3-L4G(AP1/AP1)
l Sink: NE6-Shelf0(Master Shelf)-3-L4G(AP1/AP1)
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
Issue 02 (2010-09-24)
shortcut menu.
----End
1.11.16 Creating the 1+1 OCh Trails Between a Traditional NE and
an ASON NE
Prerequisite
are traditional NEs. A 1+1 OCh trail needs to be configured between NE5 and NE1. To
implement the 1+1 protection, the trail association is configured in the ASON domain and the
SNCP is configured on the traditional NEs.
Figure 1-129 1+1 OCh Trails requirement between a traditional NE and an ASON NE
NE1
NE2 NE3
NE4
NE6
NE5
OCh
OCh
: ASON NE
: Traditional NE
: Working Trail
: Protection trail
1-257

Board Configuration
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Table 1-62 Service planning for the two silver ASON trails
Source NE NE1 NE1
Source Board Shelf3(Slave Shelf3)-1-LDGD Shelf3(Slave Shelf3)-1-LDGD
Source
Wavelength
2 2
1-259
Sink NE NE4 NE3
Sink Wavelength 2 2
Protection type Silver trail Silver trail
Level ODU1 ODU1
Service Type ASON Trail ASON Trail
Trail Type Working Trail Protection Trail

Table 1-63 1+1 Protection Planning of NE5
Attribute Working Service Protection Service
Source Board Shelf3(Slave Shelf3)-1-LDGD Shelf3(Slave Shelf3)-1-LDGD
Source
Wavelength
2 2
Sink Wavelength 2 2
Protection Type Intra-Board 1+1 Protection

You can use the following way to create a 1+1 OCh trail between a traditional NE and an ASON
NE.
Create a silver ASON trail between NE1 and NE4, and another silver ASON trail between NE1
and NE3. Associate the two silver ASON trails. Then create intra-board 1+1 protection and
optical cross-connection on NE5.
Procedure
Issue 02 (2010-09-24)
l Level OCh
l Rate: -
l Class: Silver
l Source: NE1-Shelf3(Slave Shelf3)-1-LDGD-1(IN/OUT)-2/1529.55/196.000
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
NE3.
shortcut menu.
Step 12 Choose Configuration > Port Protection from the Function Tree. Click New.
Step 13 Click OK, and enter the following port protection information about NE5:
l Protection Type: Intra-Board 1+1 Protection
l Board with Working Channel: Shelf3(Slave Shelf3)-1-LDGD
l Working Channel: 1(IN1/OUT1)
1-261
l Board with Protection Channel: Shelf3(Slave Shelf3)-1-LDGD
l Protection Channel: 2(IN1/OUT1)
Step 14 Click OK. If the creation is successful, a dialog box is displayed indicating that the operation is
l Source Slot: Shelf3(Slave Shelf3)-1-LDGD
l Source Band: C
l Sink Band: C
l Sink Wavelength: 2
Step 18 According to the service planning, repeat Steps 15-17 to create optical cross-connection of NE5.
----End
1.11.17 Creating the 1+1 ODU0 Trails Between a Traditional NE and
an ASON NE
Prerequisite
T32.
Issue 02 (2010-09-24)
Figure 1-132 1+1 ODU0 Trail requirement between a traditional NE and an ASON NE
NE1
NE2 NE3
NE4
NE6
NE5
ODU0
ODU0
: ASON NE
: Traditional NE
: Working Trail
: Protection trail

Board Configuration
1-263
FAN
FAN
Slave Subrack1
E F I 2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
FAN
FAN
Master Subrack
EFI2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
N
1
S
L
O
1
6
A
N
1
S
L
O
1
6
A
F
I
U
O
B
U
1
O
A
U
1
R
M
U
1
2
W
S
D
9
5
1
S
C
C
1
2
W
S
D
9
R
M
U
5
1
S
C
C
1
2
S
C
2
O
A
U
1
O
B
U
1
F
I
U
1
2
W
S
D
9
O
A
U
1
O
B
U
1
1
2
W
S
D
9
R
M
U
1
2
S
C
1
L
D
M
D
F
I
U
R
M
U
1
2
W
S
D
9
R
M
U
5
1
S
C
C
5
2
N
Q
2
F
I
U
5
2
N
Q
2

Issue 02 (2010-09-24)
FAN
FAN
Slave Subrack1
E F I 2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
FAN
FAN
Master Subrack
EFI2 PIU PIU
EF
I1
PIU PIU ATE
5
2
N
Q
2
5
2
X
C
M
5
2
X
C
M
N
1
S
L
O
1
6
A
N
1
S
L
O
1
6
A
F
I
U
O
B
U
1
O
A
U
1
R
M
U
1
2
W
S
D
9
5
1
S
C
C
1
2
W
S
D
9
R
M
U
5
1
S
C
C
1
2
S
C
2
O
A
U
1
O
B
U
1
F
I
U
1
2
W
S
D
9
O
A
U
1
O
B
U
1
1
2
W
S
D
9
R
M
U
1
2
S
C
1
L
D
M
D
F
I
U
R
M
U
1
2
W
S
D
9
R
M
U
5
1
S
C
C
5
2
N
Q
2
F
I
U
5
2
N
Q
2

1-265
Service Planning
Table 1-64, Table 1-65, Table 1-66, and Table 1-67 show the service planning for the NEs.
Source NE NE1 NE1
Sink NE NE4 NE3
Level ODU0 ODU0

Table 1-65 SNCP service planning for NE5
Attribute Working Service Working Service
Source Optical
Port-Optical
Channel
Sink Slot Shelf1(Slave Shelf1)-20-52NQ2
Sink Optical Port-
Optical Channel
Protection Type ODUK SNCP
Service Type ODU0

Source Optical
Port-Optical
Channel
Sink Slot Shelf1(Slave Shelf1)-20-52NQ2
Sink Optical Port-
Optical Channel
Service Type ODU0

Issue 02 (2010-09-24)
Table 1-67 Service planning for NE3 and NE4
Attribute NE3 NE4
Source Slot Shelf1(Slave
Shelf1)-21-52NQ2
Shelf1(Slave
Shelf1)-22-52NQ2
Source Optical Port-Optical
Channel
161(ODU0LP1/
ODU0LP1)-1
161(ODU0LP1/
ODU0LP1)-1
Shelf1)-22-52NQ2
Shelf1(Slave
Shelf1)-21-52NQ2
Sink Optical Port-Optical
Channel
161(ODU0LP1/
ODU0LP1)-1
161(ODU0LP1/
ODU0LP1)-1
Level ODU0 ODU0
Direction Bidirectional Bidirectional

To create the 1+1 ODU0 trails 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 ODU0 cross-connection
between NE1 and NE5, and create the ODU0 cross-connection between NE3 and NE4.
Procedure
l Level: ODU0
l Rate: ODU0
l Class: Silver
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
1-267
For example, select the 52NQ2 in slot 122, the port 161(ODU0LP1/ODU0LP1) and the channel
1.
NOTE
again from Step 1.
NE3.
shortcut menu.
Step 13 Choose Configuration > WDM Service Configuration from the Function Tree.
Step 14 Click Create SNCP Service and enter the following SNCP service information about NE1:
l Protection Type: SW SNCP
l Service Type: ODU0
l Source Slot:
Working Service: Shelf1(Slave Shelf1)-21-52NQ2
Protection Service: Shelf1(Slave Shelf1)-22-52NQ2
l Source Optical Port
Working Service: 161(ODU0LP1/ODU0LP1)
Protection Service: 161(ODU0LP1/ODU0LP1)
l Source Optical Channel
Working Service: 1
Protection Service: 1
Issue 02 (2010-09-24)
l Sink Slot: Shelf1(Slave Shelf1)-20-52NQ2
l Sink Optical Port: 161(ODU0LP1/ODU0LP1)
l Sink Optical Channel: 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 19 Click Create and enter the following WDM service information about NE3:
l Level: ODU0
l Source Slot: Shelf1(Slave Shelf1)-21-52NQ2
l Source Optical Port: 161(ODU0LP1/ODU0LP1)
l Source Optical Channel: 1
l Source Slot: Shelf1(Slave Shelf1)-22-52NQ2
l Source Optical Port: 161(ODU0LP1/ODU0LP1)
l Activate Immediately: Active
Step 20 Click OK. After the WDM service is created, a dialog box is displayed indicating that the
Step 21 According to the service planning, repeat Steps 17-20 to create the WDM service of NE4.
----End
an ASON NE
Prerequisite
1-269
NE1
NE2 NE3
NE4
NE6
NE5
ODU1
ODU1
: ASON NE
: Traditional NE
: Working Trail
: Protection trail

Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-271
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Source NE NE1 NE1
Sink NE NE4 NE3
Level ODU1 ODU1

Issue 02 (2010-09-24)
Source Optical
Port-Optical
Channel
Sink Slot Shelf0(Master Shelf)-13-TDG
Sink Optical Port-
Optical Channel
201(LP/LP)-1
Service Type ODU1

Source Optical
Port-Optical
Channel
Sink Slot Shelf0(Master Shelf)-13-TDG
Sink Optical Port-
Optical Channel
201(LP/LP)-1
Service Type ODU1

Attribute NE3 NE4
Source Slot Shelf0(Master
Shelf)-1-12NS2
Shelf0(Master
Shelf)-2-12NS2
Channel
Shelf)-1-12NS2-
Shelf0(Master
Shelf)-1-12NS2
Channel
1-273
Attribute NE3 NE4
Level ODU1 ODU1

Procedure
l Level ODU1
l Rate: ODU1
l Class: Silver
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
For example, select the 12NS2 in slot 2, the port 51(ODU1LP/ODU1LP) and the channel 1.
Issue 02 (2010-09-24)
NOTE
again from Step 1.
NE3.
shortcut menu.
l Protection Type: ODUK SNCP
l Source Slot:
Working Service: Shelf0(Master Shelf)-1-12NS2
Protection Service: Shelf0(Master Shelf)-2-12NS2
Working Service: 51(ODU1LP/ODU1LP)
Protection Service: 51(ODU1LP/ODU1LP)
Working Service: 1
l Sink Slot: Shelf0(Master Shelf)-13-TDG
l Sink Optical Port: 201(LP/LP)
l Level: ODU1
1-275
l Source Slot: Shelf0(Master Shelf)-1-12NS2
l Source Optical Port: 51(ODU1LP/ODU1LP)
l Source Optical Channle1: 1
l Source Slot: Shelf0(Master Shelf)-2-12NS2
----End
an ASON NE
Prerequisite
Issue 02 (2010-09-24)
NE1
NE2 NE3
NE4
NE6
NE5
ODU2
ODU2
: ASON NE
: Traditional NE
: Working Trail
: Protection trail

Board Configuration
1-277
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Source NE NE1 NE1
Sink NE NE4 NE3
Level ODU2 ODU2

1-279
Source Optical
Port-Optical
Channel
Sink Slot Shelf0(Master Shelf)-1-12NS2
Sink Optical Port-
Optical Channel
71(ODU2LP/ODU2LP)-1
Service Type ODU2

Source Optical
Port-Optical
Channel
Sink Slot Shelf0(Master Shelf)-1-12NS2
Sink Optical Port-
Optical Channel
71(ODU2LP/ODU2LP)-1
Service Type ODU2

Attribute NE3 NE4
Source Slot Shelf0(Master Shelf)-12-
NS3
NS3
Channel
Sink Slot Shelf0(Master Shelf)-15-
NS3
NS3
Channel
Issue 02 (2010-09-24)
Attribute NE3 NE4
Level ODU2 ODU2

Procedure
l Level: ODU2
l Rate: ODU2
l Class: Silver
l Source: NE1-Shelf0(Master Shelf)-12-NS3-71(ODU2LP/ODU2LP)-1
l Sink: NE4-Shelf0(Master Shelf)-15-NS3-71(ODU2LP/ODU2LP)-1
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
For example, select the NS3 in slot 12, the port 71(ODU2LP/ODU2LP) and the channel 1.
1-281
NOTE
again from Step 1.
NE3.
shortcut menu.
l Protection Type: ODUK SNCP
l Source Slot:
Working Service: Shelf0(Master Shelf)-12-NS3
Protection Service: Shelf0(Master Shelf)-15-NS3
Working Service: 71(ODU2LP/ODU2LP)
Protection Service: 71(ODU2LP/ODU2LP)
Working Service: 1
l Sink Slot: Shelf0(Master Shelf)-1-12NS2
l Sink Optical Port: 71(ODU2LP/ODU2LP)
l Level: ODU2
Issue 02 (2010-09-24)
----End
1.11.20 Creating the 1+1 Client Trails Between a Traditional NE and
an ASON NE
The 1+1 Client Trails can be configured between a traditional NE and an ASON NE.
Prerequisite
are traditional NEs. A 1+1 Client trail needs to be configured between NE5 and NE1. To
1-283
Figure 1-141 1+1 Client Trail requirement between a traditional NE and an ASON NE
NE1
NE2 NE3
NE4
NE6
NE5
Client
Client
: ASON NE
: Traditional NE
: Working Trail
: Protection trail

Board Configuration
Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

1-285
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
Source NE NE1 NE1
Sink NE NE4 NE3
Level Client Client

Issue 02 (2010-09-24)
Source Optical
Port-Optical
Channel
201(LP/LP)-1 201(LP/LP)-1
Sink Slot Shelf0(Master Shelf)-3-L4G
Sink Optical Port-
Optical Channel
101(AP1/AP1)
Protection Type SW SNCP
Service Type Client

Source Optical
Port-Optical
Channel
201(LP/LP)-1 201(LP/LP)-1
Sink Slot Shelf0(Master Shelf)-3-L4G
Sink Optical Port-
Optical Channel
101(AP1/AP1)
Protection Type SW SNCP
Service Type Client

Attribute NE3 NE4
Source Slot Shelf0(Master Shelf)-4-
TDG
TDG
Channel
201(LP/LP)-1 201(LP/LP)-1
Sink Slot Shelf0(Master Shelf)-13-
TDG
TDG
Channel
201(LP/LP)-1 201(LP/LP)-1
1-287
Attribute NE3 NE4
Level Client Client

To create the 1+1 Client trails between a traditional NE and an ASON NE, do as follows:
and NE3. Then, associate the two ASON trails. After that, create the 1+1 Client cross-connection
between NE1 and NE5, and create the Client cross-connection between NE3 and NE4.
Procedure
l Level Client
l Rate: GE
l Class: Silver
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
For example, select the TDG in slot 13, the port 201(LP/LP) and the channel 1.
Issue 02 (2010-09-24)
NOTE
again from Step 1.
NE3.
shortcut menu.
l Protection Type: SW SNCP
l Service Type: Client
l Source Slot:
Working Service: Shelf0(Master Shelf)-4-TDG
Protection Service: Shelf0(Master Shelf)-13-TDG
Working Service: 201(LP/LP)
Protection Service: 201(LP/LP)
Working Service: 1
l Sink Slot: Shelf0(Master Shelf)-3-L4G
l Sink Optical Port: 101(AP1/AP1)
l Level: Client
1-289
l Source Slot: Shelf0(Master Shelf)-4-TDG
l Source Optical Port: 201(LP/LP)
l Source Slot: Shelf0(Master Shelf)-13-TDG
l Source Optical Port: 201(LP/LP)
----End
1.11.21 Creating Client Trail between ASON NE and Traditional
NE
If there are OCh trail but not server trail of client between traditional NE and ASON NE, you
also can create client trail . The U2000 will create the server tail automatically. Then the server
trail of client trail is ASON-WDM trail.
Prerequisite
l There must be OCh trail, but there are not server trail of ODU1, ODU2 orODU3.
Service Requirement
are traditional NEs. The OCh trail have be created between NE1 and NE5, but there are not
server trail of client. A Client trail needs to be configured between NE1 and NE5. This service
is required to be an unprotected service in the traditional network, but a silver service in the
ASON network.
Issue 02 (2010-09-24)
Figure 1-144 Client trail requirement between traditional NE and ASON NE
NE1
NE2 NE3
NE4
NE6
NE5
Client
Client
: ASON NE
: Traditional NE

Board Configuration
1-291
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Issue 02 (2010-09-24)
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
You can refer Table 1-80 to plan a service.
Table 1-80 Client trail planning between traditional NE and ASON NE
Attribute NE1<->NE5
Source NE NE1
Sink NE NE5
1-293
Attribute NE1<->NE5

Procedure
l Level: Client
l Rate: GE
protection type.
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
Step 8 Select the WDM trail, right-click, choose Browse Relevant Server Trails from the shortcut
menu. 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 created automatically by the U2000.
----End
Issue 02 (2010-09-24)
1.12 Managing Services Between an WDM ASON NE and a
Conventional WDM NE
A network can consist of WDM ASON NEs and conventional WDM NEs. This realizes end-
to-end service configuration and management.
1.12.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.
1.12.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.
1.12.3 Setting the Span ID of the ASON-WDM Trail
The ASON 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 GCP software on the U2000.
1.12.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.
1-295
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
1.12.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
1.12.3 Setting the Span ID of the ASON-WDM Trail
The ASON 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 GCP software on the U2000.
Issue 02 (2010-09-24)
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 > Search for 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 > Search for 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
1.13 Importing and Exporting Data
The existing ASON network may not be optimum, so we can use the OptiX Modeling and Design
System (MDS) to optimize the network. You can import the ASON data on the U2000 to the
MDS, and use the MDS to plan the imported ASON data and work out the optimum solution.
You can import a better planning scheme to the U2000. Then, use the U2000 to apply the settings
to NEs to optimize the existing ASON network.
1.13.1 Exporting Data from U2000 to MDS
You can export ASON data from the U2000 to the MDS, and use the MDS to plan the existing
ASON network according to the imported data.
1.13.2 Importing Data from MDS to U2000
You can use the MDS to plan ASON data, import the data from the MDS to the U2000, and then
use the U2000 to optimize the existing ASON network.
1.13.1 Exporting Data from U2000 to MDS
You can export ASON data from the U2000 to the MDS, and use the MDS to plan the existing
ASON network according to the imported data.
1-297
Prerequisite
l An ASON NE must be created and the NE data must be uploaded to the U2000.
l The license of the U2000 supports exporting data to the MDS.
Procedure
Step 1 Choose Administration > Back Up/Restore NMS Data > Import/Export Script File from
the main menu. The Import/Export Script File window is displayed.
Step 2 Select TXT as the script format and select Network Modeling and Design Information File
from the Script File Type drop-down list.
NOTE
The interaction files with the MDS is the txt script file.
Step 3 Select Export.
Step 4 Click Create File Directory and the Input window is displayed. Enter the directory name.
Step 5 Click OK and the new directory name appears in the Default File Directory in the Operation
Directory List.
Step 6 Click Apply and click OK in the Confirm dialog box.
Step 7 A progress bar is displayed and a prompt is displayed indicating that the operation is successful.
The directory where the script files reside is displayed.
Step 8 Click Close.
----End
1.13.2 Importing Data from MDS to U2000
You can use the MDS to plan ASON data, import the data from the MDS to the U2000, and then
use the U2000 to optimize the existing ASON network.
Prerequisite
l ASON NEs must be created and the NEs data must be uploaded to the U2000.
l The license of the U2000 supports importing data from the MDS.
l Before the import, the U2000 database must not be initialized.
l The ASON information about the basic attributes and links of the U2000 before the data
import to the U2000 must be the same as those before the data export to the MDS.
Procedure
Step 1 Choose Administration > Back Up/Restore NMS Data > Import/Export Script File from
the main menu. The Import/Export Script File window is displayed.
Step 2 Select TXT as the script format and select Network Modeling and Design Information File
from the Script File Type drop-down list.
Issue 02 (2010-09-24)
NOTE
The interaction files with the MDS is the txt script file.
Step 3 Select Import.
Step 4 Click Refresh File Directory to keep the script file directory in the U2000 synchronized with
the directory in the MDS.
Step 5 Select the directory in the Default File Directory in the Operation Directory List.
Step 6 In the Import File List, select the desired file.
Step 7 Click Apply and the Confirm dialog boxes are displayed. Follow the instructions as prompted
and then click OK.
Step 9 Click Close and the Select an Option dialog box is displayed.
Step 10 Select ASON Trail Information in WDM DOMAIN and click OK.
Click Close.
----End
1.14 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.
1.14.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.
1.14.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.
1.14.3 Creating an OVPN Customer
Before the resources are allocated for different OVPN customers, the corresponding OVPN
customers need to be created on the NMS.
1.14.4 Allocating Optical-Layer TE Links to an OVPN Customer
Each OVPN customer can use only the allocated TE links to create services. The timeslots in
the TE links allocated to each OVPN customer should be planned properly according to the
actual situations before the services are configured. Currently, only the TE links whose payload
type is OCh can be allocated.
1.14.5 Creating OVPN Services in ASON Domain
The OVPN services may be diamond, silver, copper WDM ASON OCh trails.
1.14.6 Creating an OVPN OCh trail between ASON NE and Traditional NE
You can create end-to-end OVPN OCh Trail between traditional NEs and ASON NEs. In the
ASON domain, the trail belongs to the OVPN customer resources.
1-299
1.14.7 Setting the OVPN Customer for an ASON Trail
You can change the OVPN customer for an ASON trail. A CPW_OCH_LSPOVPN_MM alarm
is reported when the ASON trail of an OVPN customer uses the resources that do not belong to
the customer. An ASON trail can belong to one OVPN customer only.
1.14.8 Querying TE Link Resources of an OVPN Customer
After the TE link resources are allocated to OVPN customers, you can query the TE link
resources of each OVPN customer.
1.14.9 Querying the WDM ASON Trails of the OVPN Customers
After the WDM ASON trails are created for the OVPN customers, you can query the WDM
ASON trails of each OVPN customer.
1.14.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.
Step 3 Click OVPN Enable Status tab, select the NE to be set, click OVPN Status field, choose
Enable.
TIP
You can quickly set OVPN status of all the NEs in this domain. Press Ctrl+A, select all of the NEs, right-
click, choose Enable.
Issue 02 (2010-09-24)
Step 4 Click Apply. A dialog box is displayed indicating that the operation is successful.
----End
1.14.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 super user admin.
l The license of the NMS must support the OVPN function.
l The operation set and the object set must be created.
NOTE
To facilitate management, it is recommend that only one NM user is created for each OVPN client.
For the OVPN working principles and authorities of the NM user, see 1.2.10 OVPN.
Procedure
Step 1 Choose Administration > NMS Security > NMS User Management from the main menu.
Step 2 Create the NM user OVPN_NM_User1.
1. Choose User in the Security Management object tree.
2. In the right pane, click New User.
3. In the Details tab, enter the information of the new user.
For example:
l Name: OVPN_NM_User1
l Password: osninfo123
l Confirm password: osninfo123
l For the other parameters, adopt the default values.
1-301
4. Click OK.
Step 3 Add the NM user OVPN_NM_User1 into Operator Group.
1. In the Security Management object tree, select the NM user OVPN_NM_User1.
2. In the right pane, click the User Group tab.
3. Click Add. Then, the Add User Group dialog box is displayed.
4. Select Operator Group and click OK.
The user group that is added is displayed in the User Groups list.
Step 4 Set the domain of the NM user.
1. In the right pane, click the Domain tab.
2. Click Select. Then, the Select Domain dialog box is displayed.
3. In the dialog box, select the object set managed by the NM user.
For example, OVPN_NE_user1
4. Click OK.
The object set that is added is displayed in the Domain list.
Step 5 Adjust the authority of the NM user OVPN_NM_User1.
1. In the right pane, click the Operation Rights tab.
2. Click Select. Then, the Select Rights dialog box is displayed.
Issue 02 (2010-09-24)
3. In the dialog box, select the operation set.
For example, ASON E2E Operator Operation set.
4. Click OK.
The authorities that are added are displayed in the authority list.
Step 6 Set the access control list of the NM user OVPN_NM_User1.
1. In the right pane, click the ACL tab.
2. Select the Use the current user ACL option box.
3. Click Set ACL. Then, the ACL dialog box is displayed.
4. Click Add. Then, the New System Access Control Item dialog box is displayed.
5. Select the Start IP address - end IP address option box and set the following parameters.
An example is provided as follows:
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
1.14.3 Creating an OVPN Customer
Before the resources are allocated for different OVPN customers, the corresponding OVPN
customers need to be created on the NMS.
Prerequisite
l You must be an NM user with "NE administrator" authority or higher.
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 Optional: Create an OVPN customer group for conveniently managing OVPN customers.
1. Right-click the root object tree and choose Create Group from the shortcut menu.
2. In the dialog box that is displayed, enter a name in the Group Name field.
For example, OVPN Group.
1-303
3. Click OK.
Step 3 Create OVPN customer that belongs to the OVPN customer group.
1. In the Object Tree, select OVPN Group and click Create in the lower right portion of the
window.
2. In the dialog box that is displayed, enter the customer name, OVPN ID, and other
information.
For example, OVPNuser1 and 1100.
NOTE
l The OVPN ID ranges from 1 to 60000.
l When you select Automatch OVPN ID, the system automatically allocates an OVPN ID to the
customer.
3. Click OK, create the OVPN customer successfully.
Step 4 Set the authority of the NM user to the OVPN customers.
NOTE
An NM user can manage multiple OVPN customers resources and services.
An OVPN customer can be managed by multiple NM users.
1. Select OVPN Group in the object tree in the left of the windows, choose OVPNuser1 in
the right list, right-click, select Authorize to User.
2. In the Customer Authorize Management windows, choose the Available Users. For
example, OVPN_NM_User1.
3. Click OK to complete the setting.
----End
1.14.4 Allocating Optical-Layer TE Links to an OVPN Customer
Each OVPN customer can use only the allocated TE links to create services. The timeslots in
the TE links allocated to each OVPN customer should be planned properly according to the
Issue 02 (2010-09-24)
actual situations before the services are configured. Currently, only the TE links whose payload
type is OCh can be allocated.
Prerequisite
l You must log in to the U2000 as user 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.
Procedure
Step 2 In the dialog box that is displayed, set Payload Type to Optical Layer and click Filter.
Step 3 In the TE Link list, select the desired TE link for resource allocation. Click Partition
Resource.
Step 4 Optional: Click Maximum Bandwidth and select the required wavelength quantity from the
drop-down list. You can filter TE links according to the maximum wavelength quantity.
Step 5 Optional: Click OVPN Customer and select an OVPN customer from the drop-down list. You
can filter the corresponding wavelength resources of the OVPN customer.
TIP
To select multiple TE links to be allocated, you can hold down the Ctrl key and click the target TE links.
To select multiple consecutive TE links, you can hold down the Shift key and click the first of the desired
TE links and the last of the desired TE links.
Step 6 In the dialog box that is displayed, select the desired TE link for resource allocation, click the
corresponding OVPN Customer field of a wavelength, and specify the OVPN customer.
1-305
Step 7 Click Apply. A dialog box is displayed indicating that the operation is successful, click Close.
Step 8 Optional: After you allocating a TE link to a customer, you can duplicate the allocation
information of this TE link to other TE links with the same bandwidth.
1. Select the TE link to be copied, right-click, and choose Copy from the shortcut menu.
2. Select another TE link to copy the previously selected TE link to, right-click, and choose
Paste from the shortcut menu.
3. Click Apply. A dialog box is displayed indicating that the operation is successful. Close
the window.
Step 9 Optional: Click Synchronize and select a TE link. Then, you can check the TE link allocation
in the lower left portion of the window.
----End
1.14.5 Creating OVPN Services in ASON Domain
The OVPN services may be diamond, silver, copper WDM ASON OCh trails.
Issue 02 (2010-09-24)
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 1-147, the four NEs are ASON NEs. An OVPN silver WDM ASON OCh
trail needs to be configured for the OVPN1 customer between NE1 and NE3.
Figure 1-147 OVPN service requirements
NE1
NE2
NE3
NE4
: ASON NE
: LSP
Board Configuration
According to the service requirements, the NEs can be configured with the boards as shown in
Figure 1-148.
Figure 1-148 Board configuration of NE1 and NE3
W
S
D
9
S
C
C
L
D
G
D
O
B
U
1
F
I
U
S
C
1
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
Slave Subrack1
W
S
D
9
R
M
U
9
W
S
D
9
R
M
U
9
W
S
D
9
S
C
C
F
I
U
O
B
U
1
W
S
D
9
O
A
U
1
O
B
U
1
F
I
U
S
C
C
O
A
U
1
P
I
U
P
I
U
A
U
X
R
M
U
9
R
M
U
9
S
C
2
Master Subrack

1-307
Service Planning
The OVPN silver WDM ASON trail is planned according to the service requirements. Table
1-81 provides the service planning information.
Table 1-81 Silver WDM ASON OCh Trail planning
Attribute NE1<->NE3
Source NE NE1
Source wavelength 2
Sink NE NE3
Sink wavelength 2
OVPN Customer OVPN1
Route constraint The trail route must pass NE2.
Lockout Unlocked
Priority 2
CrankBack 1

NOTE
Before you create the OVPN services, ensure that the TE link resources are already allocated for the OVPN
customers.
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.
Issue 02 (2010-09-24)
l Level: OCh
l Rate: -
l Class: Silver
l OVPN Customer: OVPN1
NOTE
l Lockout: Unlocked
l Priority: 2
l CrankBack: 1
NOTE
1-309
NOTE
l Right-click the NE and set Set As Explicit Node, Set As Excluded Node, Set Explicit Link and Set
Excluded Link. To cancel the settings, right-click the NE in the topology and choose the menu items
as needed.
CAUTION
The user must ensure the explicit link is the resource of the selected OVPN customer.
NOTE
dialog box.
----End
1.14.6 Creating an OVPN OCh trail between ASON NE and
Traditional NE
You can create end-to-end OVPN OCh Trail between traditional NEs and ASON NEs. In the
ASON domain, the trail belongs to the OVPN customer resources.
Prerequisite
l There must be NM users who use the OVPN resources.
As shown in Figure 1-149, the four NEs are ASON NEs. An OVPN silver ASON-WDM OCh
trail needs to be configured for the OVPN1 customer between NE1 and NE5.
Issue 02 (2010-09-24)
Figure 1-149 OVPN ASON-WDM OCh trail requirements
NE1
NE2 NE3
NE4
NE6
NE5
OCh
OCh
OVPN1
: ASON NE
: Traditional NE
Board Configuration
S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D
1-311

S
C
C
1
2
N
S
2
F
I
U
1
2
N
S
2
S
C
C
P
I
U
P
I
U
A
U
X
F
I
U
X
C
S
S
C
C
O
L
P
M
40
P
I
U
P
I
U
A
U
X
S
C
2
Master Subrack
Slave Subrack1
L
4
G
T
D
G
F
I
U
F
I
U
X
C
S
N
S
3
T
D
G
N
S
3
Slave Subrack3
W
S
D
9
M
40
W
S
D
9
W
S
D
9
W
S
D
9
S
C
C
O
L
P
D
4
0
P
I
U
P
I
U
A
U
X
Slave Subrack2
W
S
M
9
D
4
0
W
S
M
9
W
S
M
9
W
S
M
9
S
C
C
L
D
G
D
L
D
G
D
L
Q
M
D
L
Q
M
D
P
I
U
P
I
U
A
U
X
X
C
S
L
Q
M
D
X
C
S
L
D
G
D

Service Planning
The OVPN silver ASON-WDM trail is planned according to the service requirements. Table
1-82 provides the service planning information.
Table 1-82 Silver OVPN ASON-WDM OCh Trail planning
Attribute NE1<->NE5
Source NE NE1
Issue 02 (2010-09-24)
Attribute NE1<->NE5
Source wavelength 2
Sink NE NE3
Sink wavelength 2
OVPN Customer OVPN1
Lockout Unlocked
Priority 2
CrankBack 1

NOTE
Before you create the OVPN services, ensure that the TE link resources are already allocated for the OVPN
customers.
Procedure
Step 1 Open the main topology. Choose Service > WDM Trail > Create WDM Trail from the main
menu.
Step 2 Set the level and direction of the services.
The level is OCh, direction is bidirectional.
Step 3 Select SPC Firts, choose the OVPN1 in OVPN customer drop-list.
Step 4 Click Browse. In the dialog box displayed, select the slot, port and wavelength of the source
and sink.
Step 5 In the ASON Trail Parameters Setting tab, enter the route attributes of the ASON trail.
l Lockout: Unlocked
1-313
l Priority: 2
l CrankBack: 1
Step 6 Optional: Set the route constraint in the Route Constraint field.
1. Select Explicit Link tab. Right-click and choose Add in the Explicit Link list, set the
explicit link.
2. Select Explicit Node tab. Right-click and choose Add in the Explicit Node list, set the
explicit node.
3. Select Excluded Nodek tab. Right-click and choose Add in the Excluded Node list, set
the excluded node.
dialog box.
Step 11 Choose Service > WDM Trail > Manage WDM Trail from the main menu. View the OVPN
ASON-WDM trail.
----End
1.14.7 Setting the OVPN Customer for an ASON Trail
You can change the OVPN customer for an ASON trail. A CPW_OCH_LSPOVPN_MM alarm
is reported when the ASON trail of an OVPN customer uses the resources that do not belong to
the customer. An ASON trail can belong to one OVPN customer only.
Prerequisite
l An ASON trail must be created for the OVPN customer.
Procedure
Step 2 In the ASON trail list, select an ASON trail, right-click, and choose Set OVPN Customer from
the shortcut menu.
Step 3 In the dialog box that is displayed, select the desired OVPN customer, double-click the
corresponding Selected Status field, and select Selected from the drop-down list.
Issue 02 (2010-09-24)
TIP
You can select only one OVPN customer.
In the OVPN Customer field, enter the name of the OVPN customer or the keyword, click Filter to display
the qualified OVPN customer.
Step 4 Click OK.
CAUTION
A CPW_OCH_LSPOVPN_MM alarm is reported when the ASON trail of an OVPN customer
uses the resources that do not belong to the customer.
----End
1.14.8 Querying TE Link Resources of an OVPN Customer
After the TE link resources are allocated to OVPN customers, you can query the TE link
resources of each OVPN customer.
Prerequisite
Procedure
Step 2 Click Filter. Enter the filtering information in the Filter dialog box.
For example:
l Domain: ASON
l Link Signal Type: All
l Payload Type: All
1-315
l Source NE: All
l Sink NE: All
l OVPN Customer: OVPN1
Step 3 Click Filter. In the TE link list, the TE links of the selected OVPN customer are displayed.
Step 4 Select a TE link. In the lower right portion of the window, you can view the mapping relationships
between the wavelength and OVPN customer.
----End
1.14.9 Querying the WDM ASON Trails of the OVPN Customers
After the WDM ASON trails are created for the OVPN customers, you can query the WDM
ASON trails of each OVPN customer.
Prerequisite
l The WDM ASON trails must be created for the OVPN customers.
Procedure
Step 2 Click Filter. In the Filter dialog box, select Customize OVPN Customer.
Step 3 Select the OVPN customer whose WDM ASON trails need to be queried. Click OK.
Issue 02 (2010-09-24)
NOTE
To select multiple OVPN customers, you can hold down the Ctrl key and click the target OVPN customers.
Step 4 In the OVPN Customer field of the filter windows, choose the OVPN customer to be filtered.
Step 5 In the Filter dialog box, click Filter All. Click Yes in the dialog box that is displayed.
The WDM ASON trails displayed in the list.
----End
1.15 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.
Postrequisite
Applies to OptiX OSN 3800, OptiX OSN 6800, OptiX OSN 8800 series.
1.15.1 Querying Control Plane Alarms
For maintenance purposes, you can query the current alarms or history alarms that specified
trails generate on the control plane, to learn whether there are any faults on the control plane.
1.15.2 Setting the Severity of Control Plane Alarm
The control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control link
alarm, and control channel alarm. Users can set the severity of the control plane alarms as
required.
1.15.3 Setting the Auto-Report Status of the Control Plane Alarm
1-317
alarm, and control channel alarm. Users can set the auto report status of the control plane alarms
as required.
1.15.4 Suppressing Control Plane Alarms
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.
1.15.5 Suppressing Control Plane Alarm Events
Users can suppress control plane alarms at the service layer if required.
1.15.6 Querying the Performance of the Control Plane
Users can view the current and history 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.
1.15.7 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.
1.15.8 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.
1.15.9 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 trail can be monitored.
Prerequisite
Procedure
Step 1 To query networkwide alarms, see 2.2.2 Querying Network-Wide Alarms. In the window for
viewing the current alarms, click Filter.
NOTE
You can choose other navigation path.
Choose Fault > Browse Current Alarm from the main menu.
Issue 02 (2010-09-24)
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
1.15.2 Setting the Severity of Control Plane Alarm
alarm, and control channel alarm. Users can set the severity of the control plane alarms as
required.
Prerequisite
Context
This section considers suppressing the NE alarms as an example to describe how to set the
severity of control plane alarms.
Procedure
Step 1 In the NE Explorer, click the NE and then choose ASON > Control Plane Alarm > Alarm
Suppression and Severity.
Step 2 Click NE Alarm Suppression and Severity tab.
Step 3 Event names, suppress status and severity displays in the right windows.
Step 4 Select the required event, double-click Severity, and then choose Critical from the drop-down
menu.
Step 5 Click Default, set the severity of alarm to the default value.
Step 6 Optional: After the operation is complete, click Query to view the severity of the current alarms.
----End
1.15.3 Setting the Auto-Report Status of the Control Plane Alarm
alarm, and control channel alarm. Users can set the auto report status of the control plane alarms
as required.
Prerequisite
1-319
Procedure
Step 1 In the NE Explorer, click the NE and then choose ASON > Control Plane Alarm > Alarm
Auto Reporting.
Step 2 Event names and corresponding auto reporting status displays in the right windows.
Step 3 Select the required event, double-click Auto Reporting Status, and then choose Reported from
the drop-down menu.
Step 4 Click Apply to submit the alarm suppression setting.
Step 5 Optional: Click Default, set the auto report status of alarm to the default value.
Step 6 Optional: After the operation is complete, click Query to view the suppression status of the
current alarms.
----End
1.15.4 Suppressing Control Plane Alarms
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
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 from the drop-down menu.
Step 4 Click Apply to submit the alarm suppression setting.
Issue 02 (2010-09-24)
Step 5 Optional: After the operation is complete, click Query to view the suppression status of the
current alarms.
----End
1.15.5 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 Control Plane Alarm Suppression interface, and then
choose Suppressed from the drop-down menu.
Step 4 Click Apply to activate the alarm suppression setting.
----End
ASON Trail.
Prerequisite
l The NE Performance Monitoring Time is enabled.
l Applies to OptiX OSN 3800, OptiX OSN 6800 and OptiX OSN 8800 series.
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 history performance data.
4. Optional: Click Performance Threshold-Crossing Record tab to view the data of
the performance threshold crossing events.
5. Optional: Click Filter by Template and select Open from the drop-down list. In the
Open dialog box, select a template for filtering performance data and click Open.
Certain performance events are filtered and you can view the performance.
1-321
NOTE
The performance filtering template is already saved.
6. 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 history 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.
NOTE
5. Click Query.
----End
1.15.7 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.
Issue 02 (2010-09-24)
Step 3 Click Apply to submit the setting.
Step 4 Optional: Click Query to view the control plane monitoring status of ASON NE.
----End
1.15.8 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
1.15.9 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 trail can be monitored.
Prerequisite
1-323
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
Issue 02 (2010-09-24)
2 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 following documents.
l OptiX OSN 8800 T32 Intelligent Optical Transport Platform Routine Maintenance
l OptiX OSN 6800 Intelligent Optical Transport Platform Routine Maintenance
l OptiX OSN 3800 Compact Intelligent Optical Transport Platform Routine Maintenance
2.1 Precautions for Routine Maintenance
The precautions for routine maintenance of an ASON network are described.
2.2 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.
Operation Guide for WDM ASON Network Management 2 Routine Maintenance for an ASON Network
2-1
2.1 Precautions for Routine Maintenance
The precautions for routine maintenance of an ASON network are described.
Switching off Laser
During routine maintenance,
l 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 port and channel interruption.
l Switching off the laser on the OTU board does not affect the ASON services at the optical
layer and does not trigger rerouting.
Looping Back Optical Port
When fiber jumpers are used to loopback an optical port that has ASON services, first transfer
the ASON services to other ASON trails. If the optical port has no services, lock out the ASON
trails that pass the optical port 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 port causes service interruption.
CAUTION
Optimization of ASON service at the optical layer on the WDM equipment causes service
interruption for a long time.
Inserting or Removing Fibers
Before inserting or removing fibers at an optical port with ASON services, transfer the ASON
services to other trails. If the optical port has no actual services, lock the ASON trails that pass
the optical port by setting the Rerouting Lockout attribute of the trails to Locked.
CAUTION
l Do not frequently insert or remove fibers at an optical port that has TE links.
l Do not remove or insert fibers on an optical port with services running.
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 you replace 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 there are ASON services being created, deleted, or rerouted.
Issue 02 (2010-09-24)
CAUTION
Do not reset the SCC board when there are ASON services being created, deleted, or rerouted.
Precautions for Replacing the FIU Board
Before replacing the FIU board through which ASON services pass, you need to transfer all the
services on the board to other trails. 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.
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.
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. The disabling operation, however,
causes automatic soft reset of the SCC board of the current node.
CAUTION
Disabling the ASON feature on an NE with ASON services interrupt the ASON services. 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.
Precautions for Configuring the Interface
By default, the ASON software does not enable the OSPF protocol at the Ethernet network port
of the SCC board. A PPP interface is created at each optical port 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 port of the SCC board.
2-3
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.
2.2 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.
2.2.1 Periodically Refreshing the ASON information
Every time an ASON NE is rerouted, the service route and link information change. You need
to periodically refresh the ASON information to keep consistency between the data on the
U2000 and the data on the NE.
2.2.2 Querying Network-Wide Alarms
You can query the NE alarms in the entire network to find abnormal alarms timely.
2.2.3 Querying ASON Trail Alarms
For maintenance purposes, you can query the current alarms or history alarms of a specified
ASON trail to learn the failures of an ASON network.
2.2.5 Querying Control Link Alarms
For maintenance purposes, you can query the current alarms or history alarms of a control link,
to learn whether the control link is faulty.
2.2.6 Querying TE Link Alarms
For maintenance purposes, you can query the current alarms or history alarms of a TE link to
learn the failures of an ASON network.
2.2.7 Query the Interrupted TE Link
The U2000 will delete the interrupted TE link after synchronization. Then you can query the TE
link from the NEs to U2000 by query the TE link interrupt alarm. You can do troubleshooting
by this operation.
2.2.8 Creating a Performance Filtering Template
By creating and modifying performance filtering template, a network maintainer can quickly
view the specific performance events of specific NEs when the maintainer enables the
performance monitoring next time.
ASON Trail.
2.2.10 Querying Abnormal ASON Events
During routine maintenance, you need to query abnormal events to check the running status of
the network.
2.2.11 Checking the Running Status of ASON Trails
Issue 02 (2010-09-24)
During routine maintenance, you must periodically check the running status of ASON trails to
check whether the trail attributes are changed and to ensure the normal running of the trails.
2.2.12 Checking TE Links
During routine maintenance, you need to know the resource utilizations of TE links. First, check
the number of TE links in the entire network. Then, check the remaining resources of each TE
link. The number of TE links should be consistent with the number of TE links that are actually
used. The remaining resources of the TE links on two adjacent nodes on one fiber should be the
same.
2.2.13 Checking Control Links
During routine maintenance, you need to check the number and status of control links.
2.2.1 Periodically Refreshing the ASON information
Every time an ASON NE is rerouted, the service route and link information change. You need
to periodically refresh the ASON information to keep consistency between the data on the
U2000 and the data on the NE.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
You can choose the information that you want to refresh periodically, which includes TE link
information, ASON trail status, and ASON trail route information. The ASON trail status
includes ASON trail channel status, SLA compliant, rerouting attributes, information of
associated services, and information of preset restoration trail.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management from the main menu.
Step 2 Create a task to periodically refresh the ASON information.
1. In the Schedule Task Management window, click New.
2. Set the task type to Refresh ASON Information and enter the task name. Click Next.
3. Select the information that you want to refresh periodically and click Next.
4. Specify the period for executing the task.
NOTE
The time period can be Every Fixed Minutes, Daily, Weekly, Monthly or Running Once.
5. Enter the start date and time of the task.
NOTE
The setting of the task running time depends on the execution period. For example, if the execution
period is Daily, you need to set the time for running the task every day.
6. Click Finish and the related information is displayed in the list in the Schedule Task
Management window.
Step 3 In the Schedule Task Management window, select the task whose Task Type is Refresh
ASON Information.
Step 4 Click Run and you can view the parameters in the list to know the running status.
2-5
Step 5 Optional: Click Modify and you can modify the task information.
----End
2.2.2 Querying Network-Wide Alarms
You can query the NE alarms in the entire network to find abnormal alarms timely.
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
l The numeral on the right of the indicator indicates the number of current critical alarms in
the entire network.
l If there is a block outside the circle that indicates the alarm indicator, the alarm is not
acknowledged.
Procedure
Step 1 Click (red) at the upper right of the U2000 user interface to view the network-wide
critical alarms. The Networkwide Critical Alarm window is displayed. The critical alarms that
require high attention include the following:
l R_LOS
l R_LOF
l EXT_SYNC_LOS
l HARD_BAD
l SUBCARD_ABN
l NESTATE_INSTALL
NOTE
It is recommended to keep this window open during alarm monitoring.
Step 2 Click (orange) at the upper right of the U2000 user interface to view the networkwide
major alarms. The major alarms that require high attention include the following:
l MS_AIS, TU_AIS
l B2_EXC, B3_EXC
l POWER_ABNORMAL
l APS_INDI
l TEMP_OVER
l TPS_ALM
Step 3 Click (yellow) at the upper right of the U2000 user interface to view the networkwide
minor alarms. The minor alarms that require high attention include the following:
l B1_EXC, B1_SD, B2_SD, B3_SD
l MS_RDI, HP_RDI
Issue 02 (2010-09-24)
l J0_MM
Step 4 Optional: Right-click an ASON-related alarm and choose Alarm-Affected Original Route
from the shortcut menu. In the SDH ASON Trail Management window displayed, you can
view the detailed information of the affected original route.
----End
2.2.3 Querying ASON Trail Alarms
For maintenance purposes, you can query the current alarms or history 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.
Procedure
Step 2 In the trail list, select an ASON trail and click Alarms. Choose Current Alarms from the drop-
down menu.
The current alarms of the ASON trial are displayed in a new window.
Step 3 Optional: In the trail list, select an ASON trail and click Alarms. Choose History Alarms from
the drop-down menu.
The history alarms of the ASON trail are displayed in a new window.
Step 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.
Step 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.
----End
2-7
Prerequisite
Procedure
Step 1 To query networkwide alarms, see 2.2.2 Querying Network-Wide Alarms. In the window for
viewing the current alarms, click Filter.
NOTE
You can choose other navigation path.
Choose Fault > Browse Current Alarm from the main menu.
----End
2.2.5 Querying Control Link Alarms
For maintenance purposes, you can query the current alarms or history alarms of a control link,
to learn whether the control link is faulty.
Prerequisite
Procedure
Step 1 Choose Configuration > WDM 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 history alarms of the control link are then displayed in a new window.
----End
2.2.6 Querying TE Link Alarms
For maintenance purposes, you can query the current alarms or history alarms of a TE link to
learn the failures of an ASON network.
Issue 02 (2010-09-24)
Prerequisite
l A TE link must be created.
Procedure
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 history alarms of the TE link are
displayed.
----End
2.2.7 Query the Interrupted TE Link
The U2000 will delete the interrupted TE link after synchronization. Then you can query the TE
link from the NEs to U2000 by query the TE link interrupt alarm. You can do troubleshooting
by this operation.
Prerequisite
l The ASON NE of the USP V100R005 version or a later version.
Procedure
Step 4 Select the control plane alarm of the interrupted TE link, for example,
CPW_OTU1_TEL_DOWN. Right-click, choose Query Relevant TE Link from the shortcut
menu.
Step 5 The interrupted TE link displayed in the WDM TE Link Management interface.
NOTE
If the TE link is recovered and the alarm terminated, the status of TE link is Normal.
----End
2-9
2.2.8 Creating a Performance Filtering Template
By creating and modifying performance filtering template, a network maintainer can quickly
view the specific performance events of specific NEs when the maintainer enables the
performance monitoring next time.
Prerequisite
Context
The Filter by Template function involves the following windows: viewing the SDH
performance, viewing the WDM performance, and viewing the control panel performance.
Procedure
Step 1 In the Object Tree on the left of the window for viewing performance, select one or more NEs
or boards on NEs. In filter criteria area of the table on the right of the window, set parameters
for filtering performance events.
Step 2 On the lower portion of the window for viewing performance, click Filter by Template and
select Save. from the drop-down list.
Step 3 In the Enter the Name dialog box, enter the template name and click OK.
NOTE
l After the template is saved, the name of the current template is displayed next to the window title.
l When you save the template, the filtering parameters in only the current window are saved.
l When you modify the original template, select Save from the drop-down list. The template needs not
to be renamed.
----End
ASON Trail.
Prerequisite
l The NE Performance Monitoring Time is enabled.
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.
Issue 02 (2010-09-24)
3. Optional: Click History Performance Data tab to view the history performance data.
4. Optional: Click Performance Threshold-Crossing Record tab to view the data of
the performance threshold crossing events.
NOTE
6. 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 history 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.
NOTE
5. Click Query.
----End
2.2.10 Querying Abnormal ASON Events
During routine maintenance, you need to query abnormal events to check the running status of
the network.
Prerequisite
CAUTION
Viewing abnormal events is important for maintaining an ASON network. Hence, view abnormal
events periodically.
2-11
Procedure
Step 1 Click Fault > Browse Event in the main manual, the Filter dialog box is displayed.
Step 2 Select Basic Settings tab in the Filter dialog box, set the Event name, Severity, Type and
Generated Time of the desired events, you can also enter the remarks contained by the events
if necessary.
NOTE
Check the Event name check box, click the behind the Event name textbox, in the displayed
Select Event dialog box, select the events desired.
Step 3 Click the Event Source tab, you can filter the events by object or by type.
Step 4 Click OK, all of the records that fit the filter restriction is displayed.
Step 5 Click Save as to save the records to the specified path.
----End
2.2.11 Checking the Running Status of ASON Trails
During routine maintenance, you must periodically check the running status of ASON trails to
check whether the trail attributes are changed and to ensure the normal running of the trails.
Prerequisite
Procedure
l Perform the following steps to check the running status of all ASON trails on the topology:
menu.
2. In the trail list, right-click the ASON trails that you want to view and choose
Details from the shortcut menu.
3. In the dialog box displayed, check the status of the selected ASON trails.
Activation Status: Active is the normal status.
Control Plane Alarm Status: If there is any alarm, handle it immediately.
Issue 02 (2010-09-24)
4. Click OK.
l Perform the following steps to check the running status of all ASON trails in the NE
Explorer:
1. In the NE Explorer, select an NE and choose ASON > WDM ASON Trail from the
Function Tree.
2. Select a query mode in Query ASON Trail.
NOTE
There are four query modes, which are With this node as source, With this node as the
intermediate node, With this node as sink, and Passing through this node.
3. Click Query.
----End
2.2.12 Checking TE Links
During routine maintenance, you need to know the resource utilizations of TE links. First, check
the number of TE links in the entire network. Then, check the remaining resources of each TE
link. The number of TE links should be consistent with the number of TE links that are actually
used. The remaining resources of the TE links on two adjacent nodes on one fiber should be the
same.
Prerequisite
2-13
Procedure
l Perform the following steps to check all the TE links on the topology:
1. Choose Configuration > WDM ASON > TE Link Management from the main
menu. The WDM TE Link Management window is displayed.
2. Click Synchronize. In the Synchronize dialog box displayed, choose Domain and
Payload Type.
3. Click Synchronize, the information in the list is refreshed.
4. Refer to the Total at the bottom of the TE Link group box to learn the number of TE
links. View the Alarm Status, Resource Usage(%), , and Downgrade Type of each
TE link.
Control Plane Alarm Status: If there is any alarm, handle it immediately.
Resource Usage(%): Displays the utilization of the wavelength resources. The
information is displayed in different colors according to the value of the
Threshold field.
Downgrade Type: Normal indicates that the TE link is not downgraded.
5. Optional: You can view the Total Resource Usage(%) of multiple links at the bottom
of the TE Link group box.
l Perform the following steps to view the LMP protocol status of TE links in the NE Explorer:
1. In the NE Explorer, select an NE and choose ASON > Link Management
Protocol from the Function Tree.
2. Click the LMP TE Link tab.
3. Click Query.
l Perform the following steps to view the OSPF protocol status of TE links in the NE
Explorer:
1. In the NE Explorer, select an NE and choose ASON > OSPF Protocol
Management from the Function Tree.
2. Click the OSPF TE Link tab.
3. Click Query.
----End
2.2.13 Checking Control Links
During routine maintenance, you need to check the number and status of control links.
Prerequisite
Procedure
l Perform the following steps to query the status and number of control links in the entire
network:
1. Choose Configuration > WDM ASON > Control Link Management from the main
menu.
2. Click Synchronize. The information in the list is refreshed.
Issue 02 (2010-09-24)
3. View the status of control links in the list. You can also view the number of control
links in the entire network.
l Perform the following steps to query the status of control links on a single NE:
1. In the NE Explorer, select an NE and choose ASON > OSPF Protocol
2. Click the OSPF Control Link tab.
3. To query the status and number of control links on the NE, click Query.
----End
2-15
3 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, service interruption and NE database fault.
3.1 Handling Link Failures
Link failure contains control channel failure, and TE link failure.
3.2 Handling the Failure in Creating Trails
Causes for the trail creation failure are various.
3.3 Handling Trail Interruption
Causes for the trail interruption are various.
Operation Guide for WDM ASON Network Management 3 Handling ASON Network Failures
3-1
3.1 Handling Link Failures
Link failure contains control channel failure, and TE link failure.
3.1.1 Handling Impassable Control Channels
Control channels are classified into control channels inside and outside fibers. The control
channels inside fibers use D4-D12 bytes to transmit the check information. The control channels
outside fibers are seldom used.
3.1.2 Handling Impassable TE Links
Only when control channels between adjacent nodes are available in an ASON network can TE
links be checked.
3.1.3 Handling Downgraded TE Links
If a TE link is downgraded, it indicates that the status of the TE link is normal before.
3.1.1 Handling Impassable Control Channels
Control channels are classified into control channels inside and outside fibers. The control
channels inside fibers use D4-D12 bytes to transmit the check information. The control channels
outside fibers are seldom used.
Common Causes for Impassable Control Channels
Common causes for impassable optical-layer control channels are listed as follows:
l The physical fiber between the OSC and FIU is improperly connected.
l The fiber connection between the FIU and OSC is wrongly configured on the U2000.
l The SD/SF alarm exists at the OSC port.
l The number of the OSC ports exceeds the limit. (An OSC port should be uniquely mapped
with a control channel. A maximum of 40 control channels are allowed to fail in the
verification.)
l The opposite NE is not an ASON NE or the ASON feature is not successfully enabled.
l The LMP Protocol Status is manually set to Disabled.
l The point-to-point protocol (PPP) fails because of the bit errors in the CPU channel.
Common causes for impassable electrical-layer control channels are listed as follows:
l The SD/SF alarm exists at the corresponding port of the TTI.
l The corresponding server trail for the TTI is not created or is already deleted.
l The number of the OSC and TTI ports exceeds 40. (An OSC port should be uniquely
mapped with a control channel.)
l The opposite NE is not an ASON NE or the ASON feature of the opposite NE is not
successfully enabled.
l The LMP Protocol Status is manually set to Disabled.
l The point-to-point protocol (PPP) fails because of the bit errors in the CPU channel.
Procedure
l Optical-layer control channel
Issue 02 (2010-09-24)
1. Check the fiber connection according to the networking.
2. Check whether the bidirectional fiber connection between an FIU and the
corresponding OSC is correctly configured.
3. Check whether alarms exist at the OSC port. If alarms exist, clear the alarms.
4. If control channels are excessive, disable certain control channels.
5. Check the running status of the ASON feature of the opposite NE. If the running is
abnormal, confirm whether the ASON feature needs to be run. If yes, enable the ASON
feature.
6. Check whether the status of the LMP protocol at the FIU port is set to Disabled. If
yes, modify the status to Enabled.
7. Check the error bit performance events on the fibers and optical interface for the OSC.
Check whether a large number of error bits exist and cause the impassability of the
control channel.
l Electrical-layer control channel
1. Check whether alarms exist at the corresponding port of the TTI. If alarms exist, clear
the alarms.
2. Create a corresponding server trail fro the TTI.
3. If control channels are excessive, disable certain control channels.
4. Check the running status of the ASON feature of the opposite NE. If the running is
abnormal, confirm whether the ASON feature needs to be run. If yes, enable the ASON
feature.
5. Check whether the status of the LMP protocol at the FIU port or at the corresponding
port of the OTN board is set to Disabled. If yes, modify the status to Enabled.
6. Check the error bit performance events on the fibers and optical interface for the OSC.
Check whether a large number of error bits exist and cause the impassability of the
control channel.
----End
3.1.2 Handling Impassable TE Links
Only when control channels between adjacent nodes are available in an ASON network can TE
links be checked.
Common Causes for Impassable TE Links
Common causes for impassable optical layer TE links are listed as follows:
l Control channels are impassable.
l Alarms exist at the FIU port.
l The board software does not match with the NE software.
l Physical fibers are improperly connected.
l The pass-through node is upgraded to an ASON node.
Common causes for impassable electrical layer TE links are listed as follows:
l Control channels are impassable.
l Alarms exist on the corresponding link of the OTN board.
l The board software does not match with the NE software.
3-3
l Physical fibers are improperly connected.
Procedure
Step 1 Optical-layer TE links.
1. Check the status of the control channel between the remote and the local nodes. If the control
channel is not passable, see 3.1.1 Handling Impassable Control Channels to rectify the
fault on the control channel.
2. Check whether alarms exist at the FIU port. If alarms exist, clear the alarms.
3. Check the NE software and the board software. According to the mapping table, find the
board software that is mapped with the NE software. If the NE software does not match
with the board software, load the board software again.
4. Check whether physical fibers are improperly connected. If the physical fibers are
improperly connected, connect the fibers again.
5. When you upgrade a pass-through node to an ASON node, change all services that pass
through the node to other trails and, on the sources and sinks of the services and on this
node, disable and enable the LMP protocol.
Step 2 Electrical-layer TE links.
1. Check the status of the control channel between the remote and the local nodes. If the control
channel is not passable, see 3.1.1 Handling Impassable Control Channels to rectify the
fault on the control channel.
2. Check whether alarms exist on the OTN board. If alarms exist, clear the alarms.
3. Check the NE software and the board software. According to the mapping table, find the
board software that is mapped with the NE software. If the NE software does not match
with the board software, load the board software again.
4. Check whether physical fibers are improperly connected. If the physical fibers are
improperly connected, connect the fibers again.
If the TE links on the two ends are in the Disabled status, but the result of the alarm query
is normal, you can view the networking in details to check whether fibers are improperly
connected.
----End
3.1.3 Handling Downgraded TE Links
If a TE link is downgraded, it indicates that the status of the TE link is normal before.
Common Causes for Downgraded TE Links
Common causes for downgraded TE links are listed as follows.
l The control channel is down.
l The communication between the NE software and the board software is abnormal.
Procedure
Step 1 Remove the fault of the control channel.
Step 2 If you encounter the following problems, perform a soft reset on the SCC to remove the fault.
Issue 02 (2010-09-24)
l If you query from the WDM TE Link Management interface, the query result shows that
the TE link is downgraded.
l If you query from the NE Explorer interface, the query result shows that the TE link is not
downgraded.
----End
3.2 Handling the Failure in Creating Trails
Causes for the trail creation failure are various.
3.2.1 Handling the Failure of Route Computation
If the route computation fails during the ASON service creation, an error message is displayed
on the U2000.
3.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.
3.2.3 Handling the Cross-Connection Configuration Failure
If the configuration for the cross-connections fails during the ASON service creation, an error
message is displayed on the U2000.
3.2.1 Handling the Failure of Route Computation
If the route computation fails during the ASON service creation, an error message is displayed
on the U2000.
Common Causes for Route Computation
Common causes for the route computation are listed as follows.
l The network resource is insufficient.
l The explicit link is not correct. The egress FIU of the passed NE must be specified.
l All possible routes are excluded during exclusive route setting.
Procedure
Step 1 Check the CrankBack attempts. If the value of CrankBack is not 0, the system still returns a
failure message after a rerouting is performed. It is recommended that you set the Crankback to
0.
Step 2 Check the utilization of the network resource. If the network resource is not sufficient, add some
resource and then create the ASON service.
Step 3 Check the explicit link to ensure that the egress FIU of the passed NE is specified.
Step 4 Check the reservation state of the designated link. If the designated link does not have available
resources, release the designated link.
Step 5 Check the links in both directions. If the links are not through, check whether the fiber
connections between the boards of the NEs are correctly configured.
Step 6 Check whether all possible routes are set to be exclusive.
3-5
Step 7 Check whether the explicit nodes are arranged in the expected sequence. If not, an error is
reported. In this case, specify multiple explicit nodes in the sequence you want.
Step 8 If the designated node does not have resources, release the designated node.
Step 9 Check whether the number of nodes passed by an ASON trail exceeds the maximum. When you
create an ASON trail, note that by default, the maximum hops of an ASON trail supported by
the OptiX GCP is 64. In other words, an ASON trail can pass through a maximum of 65 nodes.
----End
3.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.
Common Causes and Troubleshooting Suggestions
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 single station optical cross-connections or board optical 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
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.
----End
3.2.3 Handling the Cross-Connection Configuration Failure
If the configuration for the cross-connections fails during the ASON service creation, an error
message is displayed on the U2000.
Common Causes for the Failure in Cross-Connection Configuration
The common causes for the failure in the cross-connection configuration are listed as follows:
l The cross-connection information on the U2000 is inconsistent with the channel status on
the control plane.
Issue 02 (2010-09-24)
l The 1+1 port protection group exists at the service board, but the service created is not a 1
+1 service.
l Residual cross-connections exist on the node.
Procedure
Step 1 Check the resource information. If the cross-connection already exists, and it is not consistent
with the channel status of the ASON control plane, the system prompts a failure message during
the creation of the cross-connection when you create an ASON service. In this case, you can
synchronize the NE cross-connections before you configure ASON services.
NOTE
For details about synchronizing NE cross-connections, refer to 3.2.2 Handling the Failure of Label
Allocation.
Step 2 If an error message is displayed on the U2000 when you configure 1+1 services on a board that
is capable of dually feeding services, check whether the port protection group exists. 1+1 services
are not allowed if the port protection group exists. In this case, delete the port protection group
before you configure ASON services.
Step 3 Check whether any residual board cross-connections exist on the node. If so, clear the residual
cross-connections before you configure ASON services.
NOTE
For how to handle the residual cross-connection of the board of the NE, refer to the handling procedure in
the 3.2.2 Handling the Failure of Label Allocation.
----End
3.3 Handling Trail Interruption
Causes for the trail interruption are various.
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 trails to
avoid faulty trails and restore the trails.
4. 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.
3.3.1 Identifying the Interrupted trails
You need to identify which trails are interrupted before you restore them.
3.3.2 Handling the Fault of Trail Interruption
You can restore the trails by recreation or optimization after confirming the faulty services.
3.3.1 Identifying the Interrupted trails
You need to identify which trails are interrupted before you restore them.
3-7
Prerequisite
The system prompts that the trail interruption occurs.
Procedure
Step 1 Choose Fault > Synchronize Networkwide Alarms from the main menu. Synchronize alarms
networkwide.
Step 2 Choose Fault > Browse Current Alarm from the main menu. View the current alarms
networkwide.
Step 3 Find the service-affecting alarms reported from the control plane.
Step 4 Select an alarm from the ones you find in the previous step and right-click. Choose Alarm
Affected Trails from the shortcut menu.
l If the system prompts that This alarm does not affect any trails, the
selected alarm is not the one that affects the trail. Select another alarm and repeat this step.
l If the This alarm does not affect any trails is displayed for all the alarms
but the trail is interrupted, it is an indication that the trail is exceptionally deleted. In this
case, skip to Step 6.
l If the WDM ASON Trail Management is displayed, continue with the next step.
Step 5 In the WDM ASON Trail Management, identify the interrupted trail. Record the information
of the trails and take corresponding measures to clear the alarm.
Step 6 In the abnormal event browsing window, find the ASON trails that fail to be rerouted or rebuilt.
Step 7 Find all the currently interrupted trails according to the previously performed operations.
Step 8 Access the NE Explorer of the NE on which the trails are interrupted.
Step 9 In the NE Explorer, click the NE and choose ASON > WDM ASON Trail from the Function
Tree. Specify the Query ASON Trail as Passing through this node and click Query. Click
Print to save the current ASON trails on the U2000 in case any trail check is required in future.
----End
3.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.
Issue 02 (2010-09-24)
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
3-9

OG For WDM ASON Network Management - (V100R002C01 - 02)

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

OG For WDM ASON Network Management - (V100R002C01 - 02)

Transféré par

Droits d'auteur :

Formats disponibles

iManager U2000 Unified Network Management

Vous aimerez peut-être aussi