iManager U2000 Operation Guide for SDH ASON Network Management

iManager U2000 Unified Network Management
System
V100R002C01
Operation Guide for SDH 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 SDH ASON network. This document also provide the timeslot numbering policy, the
glossary, and 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 SDH 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 SDH 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 SDH ASON Network Management About This Document
v

Contents
About This Document...................................................................................................................iii
1 Configuring SDH ASON Networks.......................................................................................1-1
1.1 SDH ASON Network Configuration...............................................................................................................1-4
1.2 ASON..............................................................................................................................................................1-5
1.2.1 Basic Concepts of ASON.......................................................................................................................1-6
1.2.2 Function Structure of the ASON............................................................................................................1-8
1.2.3 ASON Protocol....................................................................................................................................1-11
1.2.4 ASON Links.........................................................................................................................................1-13
1.2.5 SLA......................................................................................................................................................1-14
1.2.6 Diamond Services................................................................................................................................1-16
1.2.7 Gold Services.......................................................................................................................................1-21
1.2.8 Silver Services......................................................................................................................................1-23
1.2.9 Copper Services....................................................................................................................................1-25
1.2.10 Iron Services.......................................................................................................................................1-26
1.2.11 OVPN.................................................................................................................................................1-27
1.2.12 UNI Services......................................................................................................................................1-29
1.3 Creating an ASON Topology........................................................................................................................1-31
1.3.1 Creating NEs in Batches......................................................................................................................1-33
1.3.2 Creating a Single NE............................................................................................................................1-35
1.3.3 Setting the Node ID..............................................................................................................................1-36
1.3.4 Enabling the ASON Feature ................................................................................................................1-37
1.3.5 Uploading NE Configuration Data.......................................................................................................1-38
1.3.6 Enable the ASON Feature of a Board..................................................................................................1-39
1.3.7 Creating Domains for an ASON Network...........................................................................................1-39
1.3.8 Synchronizing ASON NEs...................................................................................................................1-40
1.3.9 Automatically Creating Fibers According to TE Link.........................................................................1-41
1.3.10 Setting the Primary NE or Secondary NE..........................................................................................1-42
1.3.11 Setting Control Plane Parameters.......................................................................................................1-42
1.3.12 Viewing ASON NE Software Version...............................................................................................1-44
1.4 Managing the ASON Protocol......................................................................................................................1-44
1.4.1 Modifying the LMP Discovery Type...................................................................................................1-46
1.4.2 Querying the LMP Discovery Type.....................................................................................................1-47
1.4.3 Disabling the LMP Protocol.................................................................................................................1-48
Operation Guide for SDH ASON Network Management Contents
vii

1.4.4 Disabling the OSPF Protocol...............................................................................................................1-49
1.4.5 Encrypting the OSPF Protocol.............................................................................................................1-50
1.4.6 Setting the OSPF TE Link Flood Threshold........................................................................................1-50
1.4.7 Encrypting RSVP.................................................................................................................................1-51
1.4.8 Creating Out-Fiber Control Channels..................................................................................................1-52
1.5 Managing ASON Clock Subnet....................................................................................................................1-54
1.5.1 Creating an ASON Clock Subnet.........................................................................................................1-54
1.5.2 Converting a Preconfigured ASON Clock Subnet into an ASON Clock Subnet................................1-57
1.5.3 Converting a Traditional Clock Subnet into an ASON Clock Subnet.................................................1-61
1.5.4 Managing a Hybrid Network Composed of an ASON Clock Subnet and a Traditional Clock Subnet
.......................................................................................................................................................................1-64
1.5.5 Setting the Clock Fault Recover Time.................................................................................................1-67
1.6 Managing Link Resources.............................................................................................................................1-67
1.6.1 Synchronizing Control Links Networkwide........................................................................................1-69
1.6.2 Synchronizing TE Links.......................................................................................................................1-69
1.6.3 Viewing TE Links................................................................................................................................1-70
1.6.4 Configuring the Link Distance.............................................................................................................1-71
1.6.5 Setting the Custom Cost of the TE Link .............................................................................................1-71
1.6.6 Setting the Usage Threshold of Fiber Resources.................................................................................1-72
1.6.7 Creating an SRLG................................................................................................................................1-72
1.6.8 Querying VC4 Timeslot Occupation Status.........................................................................................1-73
1.6.9 Querying the Information About the Timeslots on the Link Sections.................................................1-74
1.6.10 Setting Resource Reservation.............................................................................................................1-75
1.6.11 Creating a Virtual Interfaces..............................................................................................................1-77
1.6.12 Creating a Virtual TE Link.................................................................................................................1-78
1.6.13 Creating a TE Link Based on Virtual Interfaces................................................................................1-80
1.6.14 Deleting an Interrupted TE Link Manually........................................................................................1-84
1.7 Managing SRGs............................................................................................................................................1-85
1.7.1 Creating an SRG...................................................................................................................................1-85
1.7.2 Querying the SRG Related to a TE Link..............................................................................................1-89
1.7.3 Querying the SRG Related to an ASON NE........................................................................................1-89
1.8 Creating ASON Services...............................................................................................................................1-90
1.8.1 Synchronizing ASON Trails................................................................................................................1-91
1.8.2 Creating a Diamond ASON Service.....................................................................................................1-92
1.8.3 Creating a Gold ASON service............................................................................................................1-96
1.8.4 Creating a Silver ASON Service........................................................................................................1-100
1.8.5 Creating a Copper ASON Service......................................................................................................1-104
1.8.6 Creating an Iron ASON Service.........................................................................................................1-107
1.8.7 Creating an ASON Server Trail.........................................................................................................1-111
1.8.8 Creating a Segmented ASON Server Trail........................................................................................1-115
1.8.9 Creating Two Associated SDH ASON Trails....................................................................................1-118
1.8.10 Setting ASON Trail Association......................................................................................................1-120
1.8.11 Creating ASON Services in Batches................................................................................................1-121
Contents
viii Huawei Proprietary and Confidential
Issue 02 (2010-09-24)

1.8.12 Deactivating the SDH ASON Trail..................................................................................................1-125
1.8.13 Deleting an ASON Trail...................................................................................................................1-126
1.9 Modifying the Attributes of ASON Services..............................................................................................1-127
1.9.1 Viewing ASON Service Attributes....................................................................................................1-127
1.9.2 Setting the Routing Attributes............................................................................................................1-129
1.9.3 Setting the Scheduled Reversion Time..............................................................................................1-129
1.9.4 Setting the B3 Alarm to Trigger Rerouting........................................................................................1-130
1.9.5 Setting Preset Restoration Trail..........................................................................................................1-131
1.9.6 Setting Shared MESH Restoration Trail............................................................................................1-132
1.9.7 Setting the Original Route..................................................................................................................1-133
1.10 Modifying the Route of an ASON Service...............................................................................................1-133
1.10.1 Reverting ASON Trails....................................................................................................................1-134
1.10.2 Optimizing an ASON Service..........................................................................................................1-135
1.11 Migrating ASON Services........................................................................................................................1-136
1.11.1 Downgrading an ASON Service to a Traditional Service................................................................1-136
1.11.2 Upgrading a Traditional Service to an ASON Service.....................................................................1-137
1.11.3 Migration Between ASON Services................................................................................................1-138
1.11.4 Downgrading an ASON Server Trail to a Traditional Server Trail.................................................1-139
1.11.5 Upgrading a Traditional Server Trail to an ASON Server Trail......................................................1-140
1.11.6 Migration Between ASON Server Trails.........................................................................................1-141
1.12 Creating ASON Trail Groups....................................................................................................................1-142
1.13 Creating Services Between an ASON NE and a Traditional NE..............................................................1-145
1.13.1 Creating a VC4 Service Between Traditional NEs that Cross an ASON Domain...........................1-145
1.13.2 Creating a VC12 Service Between Traditional NEs that Cross an ASON Domain.........................1-149
1.13.3 Creating a VC4 Service Between a Traditional NE and an ASON NE...........................................1-152
1.13.4 Creating a VC12 Service Between a Traditional NE and an ASON NE.........................................1-156
1.13.5 Creating a 1+1 VC12 Service Between a Traditional NE and an ASON NE..................................1-159
1.13.6 Creating a 1+1 VC4 Service Between a Traditional NE and an ASON NE....................................1-164
1.13.7 Creating a 1+1 VC12 Service Between Traditional NEs That Cross an ASON Domain................1-170
1.13.8 Creating a 1+1 VC4 Service Between Traditional NEs That Cross an ASON Domain..................1-174
1.14 Accessing a Traditional Network to an ASON Through Linear MSP......................................................1-178
1.15 Accessing a Traditional Network to an ASON Network by Using the SNCP Accessed Service.............1-182
1.15.1 Creating the SNCP Service Between a Traditional NE and an ASON NE......................................1-182
1.15.2 Creating SNCP Services Between Traditional NEs That Cross an ASON Domain........................1-187
1.15.3 Querying the Information About the SNCP Accessed Service........................................................1-193
1.15.4 Performing Switching at the SNCP Access End..............................................................................1-193
1.16 Managing UNI Services............................................................................................................................1-194
1.16.1 Flow of Configuring UNI Services..................................................................................................1-195
1.16.2 Enabling the UNI Feature of an ASON NE.....................................................................................1-196
1.16.3 Setting the Information About the GMPLS UNI ............................................................................1-197
1.16.4 Setting the Information About the OIF UNI ...................................................................................1-200
1.16.5 Setting the UNI Access Policy.........................................................................................................1-202
ix

1.16.6 Setting the Information About the GMPLS UNI Link.....................................................................1-203
1.16.7 Setting the Information About the OIF UNI Link............................................................................1-204
1.16.8 Querying UNI Services....................................................................................................................1-205
1.16.9 Deleting UNI Services.....................................................................................................................1-206
1.17 Managing the OVPN Customers and OVPN Services..............................................................................1-207
1.17.1 Enabling OVPN Function of ASON NE..........................................................................................1-208
1.17.2 Creating NM User for OVPN Customer..........................................................................................1-208
1.17.3 Creating an OVPN Customer...........................................................................................................1-210
1.17.4 Allocating TE Links for OVPN Customers.....................................................................................1-212
1.17.5 Creating OVPN Services..................................................................................................................1-213
1.17.6 Querying the TE Link Resources of the OVPN Customers.............................................................1-216
1.17.7 Querying the Services of the OVPN Customers..............................................................................1-217
1.18 Importing and Exporting Data...................................................................................................................1-218
1.18.1 Exporting Data from U2000 to MDS...............................................................................................1-218
1.18.2 Importing Data from MDS to U2000...............................................................................................1-219
1.19 Managing Control Plane Alarms and Performance Events.......................................................................1-220
1.19.1 Querying Control Plane Alarms.......................................................................................................1-221
1.19.2 Setting the Severity of Control Plane Alarm....................................................................................1-221
1.19.3 Setting the Auto-Report Status of the Control Plane Alarm............................................................1-222
1.19.4 Suppressing Control Plane Alarms..................................................................................................1-222
1.19.5 Suppressing Control Plane Alarm Events........................................................................................1-223
1.19.6 Querying the Performance of the Control Plane..............................................................................1-223
1.19.7 Monitoring the Control Plane Performance.....................................................................................1-224
1.19.8 Setting the Auto-Report Status of the Control Plane Performance Data.........................................1-225
1.19.9 Setting the Control Plane Performance Threshold ..........................................................................1-226
2 Routine Maintenance for an ASON Network......................................................................2-1
2.1 Precautions for Routine Maintenance.............................................................................................................2-2
2.2 Routine Maintenance Items.............................................................................................................................2-3
2.2.1 Periodically Refreshing the ASON information....................................................................................2-4
2.2.2 Querying Network-Wide Alarms...........................................................................................................2-4
2.2.3 Querying ASON Trail Alarms...............................................................................................................2-5
2.2.4 Querying Control Plane Alarms.............................................................................................................2-6
2.2.5 Querying Control Link Alarms..............................................................................................................2-7
2.2.6 Querying TE Link Alarms......................................................................................................................2-7
2.2.7 Creating a Performance Filtering Template...........................................................................................2-8
2.2.8 Querying the Performance of the Control Plane....................................................................................2-8
2.2.9 Querying Abnormal ASON Events........................................................................................................2-9
2.2.10 Checking the Running Status of ASON Trails...................................................................................2-10
2.2.11 Checking TE Links.............................................................................................................................2-12
2.2.12 Checking Control Links.....................................................................................................................2-13
2.2.13 Checking the Activation Status of ASON Services...........................................................................2-13
3 Handling ASON Network Failures........................................................................................3-1
Contents
x Huawei Proprietary and Confidential
Issue 02 (2010-09-24)

3.1 Handling Link Failures....................................................................................................................................3-2
3.1.1 Handling Impassable Control Channels.................................................................................................3-2
3.1.2 Handling Impassable Component Links................................................................................................3-3
3.1.3 Handling Impassable TE Links..............................................................................................................3-3
3.1.4 Handling Downgraded TE Links........................................................................................................... 3-4
3.2 Handling the Failure in Creating Trails...........................................................................................................3-4
3.2.1 Handling the Failure of Route Computation..........................................................................................3-5
3.2.2 Handling the Failure to Allocate Labels................................................................................................ 3-6
3.2.3 Handling the Failure in Creating Services in Batches............................................................................3-6
3.3 Handling Trail Interruption.............................................................................................................................3-7
3.3.1 Determining Interrupted Services.......................................................................................................... 3-7
3.3.2 Troubleshooting Interruption of Services.............................................................................................. 3-8
3.4 Disaster Recovery........................................................................................................................................... 3-8
xi

Figures
Figure 1-1 Three planes of the ASON..................................................................................................................1-6
Figure 1-2 Function structure of the ASON.........................................................................................................1-9
Figure 1-3 ASON NE...........................................................................................................................................1-9
Figure 1-4 Creating control channels.................................................................................................................1-11
Figure 1-5 Verifying component links and TE links..........................................................................................1-12
Figure 1-6 Diamond Services.............................................................................................................................1-17
Figure 1-7 Gold services....................................................................................................................................1-21
Figure 1-8 A silver service.................................................................................................................................1-23
Figure 1-9 Networking diagram of an OVPN....................................................................................................1-27
Figure 1-10 Allocating TE links.........................................................................................................................1-28
Figure 1-11 Ethernet UNI services.....................................................................................................................1-30
Figure 1-12 SDH UNI services..........................................................................................................................1-31
Figure 1-13 LMP discovery mode......................................................................................................................1-46
Figure 1-14 Board configuration of NE3 and NE4............................................................................................1-47
Figure 1-15 Creating out-fiber control channels................................................................................................1-52
Figure 1-16 ASON clock subnet........................................................................................................................1-55
Figure 1-17 Board configuration of NE1 to NE4...............................................................................................1-56
Figure 1-18 Traditional Clock Subnet................................................................................................................1-58
Figure 1-20 ASON clock subnet........................................................................................................................1-61
Figure 1-22 Hybrid network composed of an ASON clock subnet and a traditional clock subnet...................1-65
Figure 1-23 Board configuration of NE1, NE2, NE3 and NE4..........................................................................1-65
Figure 1-24 SRLG schematic diagram...............................................................................................................1-73
Figure 1-25 Reserved link resources..................................................................................................................1-75
Figure 1-26 Board configurations on NE3 and NE4..........................................................................................1-76
Figure 1-27 Virtual TE link................................................................................................................................1-78
Figure 1-28 Board configuration for NE3 and NE4...........................................................................................1-79
Figure 1-29 Board configuration for NE5..........................................................................................................1-79
Figure 1-30 TE link based on virtual interfaces.................................................................................................1-81
Figure 1-32 Board configuration for virtual NEs...............................................................................................1-82
Figure 1-33 Schematic diagram of the physical topology of an SRG................................................................1-86
Operation Guide for SDH ASON Network Management Figures
xiii

Figure 1-34 Schematic diagram of the topology of the TE links in an SRG......................................................1-86
Figure 1-35 Diamond service requirement.........................................................................................................1-92
Figure 1-37 Gold service requirement................................................................................................................1-97
Figure 1-39 Silver service requirement............................................................................................................1-101
Figure 1-40 Board configuration for NE1 and NE3.........................................................................................1-101
Figure 1-41 Copper service requirement..........................................................................................................1-104
Figure 1-43 Iron service requirement...............................................................................................................1-108
Figure 1-45 Diamond ASON server trail requirement.....................................................................................1-111
Figure 1-47 Segmented ASON server trail requirement..................................................................................1-115
Figure 1-48 Board configuration for NE1-NE3...............................................................................................1-116
Figure 1-49 Two associated ASON trails ........................................................................................................1-118
Figure 1-50 Batch silver service requirement..................................................................................................1-122
Figure 1-52 ASON trail group service requirement.........................................................................................1-142
Figure 1-53 Board configuration of NE1 and NE3..........................................................................................1-143
Figure 1-55 VC4 service requirement between traditional NEs......................................................................1-146
Figure 1-58 VC12 service requirement between traditional NEs....................................................................1-149
Figure 1-61 VC4 service requirement between traditional and ASON NEs....................................................1-152
Figure 1-62 Board configuration for NE1........................................................................................................1-153
Figure 1-65 VC12 service requirement between traditional and ASON NEs..................................................1-156
Figure 1-68 1+1 VC12 service requirement between traditional and ASON NEs..........................................1-160
Figure 1-71 1+1 VC4 service requirement between a traditional NE and an ASON NE................................1-165
Figure 1-72 Board configuration of NE1-NE4.................................................................................................1-165
Figure 1-74 1+1 VC12 service requirement between traditional NEs.............................................................1-170
Figures
xiv Huawei Proprietary and Confidential
Issue 02 (2010-09-24)

Figure 1-77 1+1 VC4 service requirement between traditional NEs...............................................................1-175
Figure 1-80 Accessing 1+1 linear MSP...........................................................................................................1-179
Figure 1-83 Board configuration of NE5.........................................................................................................1-180
Figure 1-84 SNCP service between a traditional NE and an ASON NE.........................................................1-183
Figure 1-87 SNCP services between traditional NEs that cross the ASON domain........................................1-188
Figure 1-89 Board configuration of NE5-NE10...............................................................................................1-189
Figure 1-90 Flow of configuring UNI services................................................................................................1-196
Figure 1-91 Setting the information about the GMPLS UNI ..........................................................................1-198
Figure 1-94 Setting the information about the OIF UNI .................................................................................1-200
Figure 1-97 OVPN service requirements.........................................................................................................1-214
Operation Guide for SDH ASON Network Management Figures
xv

Tables
Table 1-1 Service level.......................................................................................................................................1-15
Table 1-2 TE links used by ASON services.......................................................................................................1-15
Table 1-3 Attributes of the permanent 1+1 diamond services............................................................................1-17
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-20
Table 1-6 Attributes of gold services.................................................................................................................1-21
Table 1-7 Attributes of silver services................................................................................................................1-24
Table 1-8 Attributes of copper services..............................................................................................................1-25
Table 1-9 Attributes of iron services..................................................................................................................1-26
Table 1-10 OVPN service attributes...................................................................................................................1-29
Table 1-11 Board configuration of NE1 to NE4................................................................................................1-56
Table 1-12 Planning for the new clock subnet...................................................................................................1-59
Table 1-13 Board configuration of NE1 to NE4................................................................................................1-62
Table 1-14 Clock subnet planning......................................................................................................................1-66
Table 1-15 Virtual interface planning................................................................................................................1-82
Table 1-16 Virtual TE link planning..................................................................................................................1-83
Table 1-17 Risk cause analysis...........................................................................................................................1-87
Table 1-18 SRGs for pipes.................................................................................................................................1-87
Table 1-19 SRGs for optical cables....................................................................................................................1-87
Table 1-20 SRGs for NEs...................................................................................................................................1-88
Table 1-21 SRGs for sites...................................................................................................................................1-88
Table 1-22 Diamond service planning................................................................................................................1-93
Table 1-23 Gold service planning......................................................................................................................1-97
Table 1-24 Silver service planning...................................................................................................................1-101
Table 1-25 Copper service planning.................................................................................................................1-105
Table 1-26 Iron service planning......................................................................................................................1-108
Table 1-27 Diamond ASON server trail planning............................................................................................1-112
Table 1-28 Silver ASON server trail planning.................................................................................................1-116
Table 1-29 VC12 service planning on NE1, NE2 and NE...............................................................................1-117
Table 1-30 Silver service planning...................................................................................................................1-123
Table 1-31 GE service planning.......................................................................................................................1-144
Table 1-32 VC4 service planning between traditional NEs.............................................................................1-147
Table 1-33 VC12 service planning between traditional NEs...........................................................................1-151
Operation Guide for SDH ASON Network Management Tables
xvii

Table 1-34 VC4 service planning between traditional NE and ASON NE......................................................1-154
Table 1-35 Silver ASON server trail planning.................................................................................................1-158
Table 1-36 VC12 service planning for NE1, NE4 and NE5............................................................................1-158
Table 1-37 Service planning for double silver ASON server trails..................................................................1-161
Table 1-38 SNCP service planning for NE5....................................................................................................1-161
Table 1-40 Service planning for NE3 and NE4................................................................................................1-163
Table 1-41 Service planning for the two silver ASON trails...........................................................................1-166
Table 1-45 Planning of two silver ASON trails...............................................................................................1-172
Table 1-46 SNCP service planning of NE5......................................................................................................1-172
Table 1-48 Planning of Two Silver ASON Trails............................................................................................1-176
Table 1-51 Planning of Diamond Services Accessed Through 1+1 Linear MSP............................................1-181
Table 1-52 Planning of the diamond service between NE1 and NE3..............................................................1-184
Table 1-53 SNCP service planning for NE1 and NE5.....................................................................................1-185
Table 1-55 Planning of the diamond service between NE1 and NE3..............................................................1-189
Table 1-56 SNCP service planning for NE1, NE3, NE5, and NE9..................................................................1-190
Table 1-57 Service planning for NE6, NE7, NE8, and NE10..........................................................................1-190
Table 1-58 OVPN service planning..................................................................................................................1-215
Table 2-1 Abnormal Events List........................................................................................................................2-10
Tables
xviii Huawei Proprietary and Confidential
Issue 02 (2010-09-24)

1Configuring SDH ASON Networks
About This Chapter
You can configure an ASON network using the U2000.
1.1 SDH 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 SDH NEs besides the ASON features. The U2000 manages the ASON
network by integrating the ASON features with the SDH 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 ASON Clock Subnet
Clock subnet is classified into ASON clock subnet and traditional clock subnet. Before
configuring ASON services, you need to create a clock subnet to ensure that a consistent clock
tracing relation is created for all NEs in the ASON network.
1.6 Managing Link Resources
ASON is capable of automatically switching optical network connections under the control of
the signaling network. It dynamically allocates network resources as required. As the network
is growing larger, a more reasonable way of resource management is required to make the most
of the network resources and to improve the network efficiency. Link resource management is
one aspect of resource management. In an actual network, thousands of connections may exist
between two nodes, while each connection may be composed of multiple data links. Usually,
there are links that have the same attributes according to a route protocol. These links are
regarded as a whole, which is known as the traffic engineer link (TE link), serving as the
processing object of the route information.
Operation Guide for SDH ASON Network Management 1 Configuring SDH ASON Networks
1-1

1.7 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.8 Creating ASON Services
The trail levels that an ASON trail supports are as follows: diamond, gold, silver, copper and
iron. The trail levels that an ASON server trail supports are as follows: 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.9 Modifying the Attributes of ASON Services
As an ASON network is changing, you need to modify the attributes of ASON services in the
network according to different ASON features. This facilitates the configuration, management
and maintenance of the ASON network.
1.10 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.11 Migrating ASON Services
An ASON network supports the migration between traditional services and ASON services, and
supports the in-service migration between ASON services at different levels.
1.12 Creating ASON Trail Groups
An ASON trail group is often used with LCAS.
1.13 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.14 Accessing a Traditional Network to an ASON Through Linear MSP
When accessing services from a traditional network, to ensure that reliability of the accessed
services, you can create a 1+1 or 1:1 linear MSP at the edge of the traditional network and an
ASON domain. You can configure services in an ASON domain to the diamond , gold, and silver
level.
1.15 Accessing a Traditional Network to an ASON Network by Using the SNCP Accessed
Service
When a traditional network is accessed to an ASON network by using the SNCP accessed
service, the end-to-end SNCP is implemented for the service.
1.16 Managing UNI Services
The UNI is the standard interface that is used to connect the client equipment to the transport
network. When the UNI is used, the client equipment can dynamically request transport
resources from the transport network and release transport resources to the transport network,
by using the control signalling. Configuring UNI services is simpler and takes less time than
configuring traditional services. UNI services improve the reliability and real-time performance
of the transport network so that burst data service requirements can be met and end-to-end UNI
services can be realized.
1.17 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.18 Importing and Exporting Data
1 Configuring SDH ASON Networks
1-2 Huawei Proprietary and Confidential
Issue 02 (2010-09-24)

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.19 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-3

1.1 SDH 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 Synchronizing ASON NEs Synchronize data
networkwide. The U2000
searches for ASON NEs and
displays them in the topology
view.
6 Automatically Creating
Fibers According to TE
Link
The U2000 can create fibers
between NEs according to
the TE links.
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.
8 Creating ASON Services The U2000 provides the end-
to-end ASON trail
management feature.
9 Routine Maintenance
Items
View alarms and abnormal
events.
Issue 02 (2010-09-24)

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 SDH NEs besides the ASON features. The U2000 manages the ASON
network by integrating the ASON features with the SDH 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, component links and TE links.
1.2.5 SLA
The ASON network can provide services of different QoS to different clients.
1.2.6 Diamond Services
Diamond services have the best protection ability. When there are enough resources in the
network, diamond services provide a permanent 1+1 protection. Diamond services are applicable
to voice and data services, VIP private line, such as banking, security and aviation.
1.2.7 Gold Services
Gold services are applicable to voice and significant data services. Compared with diamond
services, gold services have greater bandwidth utilization.
1.2.8 Silver Services
Silver services, the revertive time is hundreds of milliseconds to several seconds. The silver level
service is suitable for those data or internet services that have low real-time requirement.
1.2.9 Copper Services
The copper services are seldom used. Generally, temporary services, such as the abrupt services
in holidays, are configured as copper services.
1.2.10 Iron Services
The iron services are also seldom used. Generally, temporary services are configured as iron
services. For example, when service volume soars, during holidays, the services can be
configured as iron services to fully use the bandwidth resources.
1.2.11 OVPN
The optical virtual private network (OVPN) divides the TE links 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.12 UNI Services
1-5

A UNI service is an ASON service that is created automatically after the customer equipment
initiates a request to the ASON equipment and the signaling is received. UNI services can be
classified into Ethernet UNI services and SDH UNI 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.
Issue 02 (2010-09-24)

Transport Plane
The traditional SDH network is the transport plane. It transmits and multiplexes 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.
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 Priority
There are 8 levels of rerouting priority. Level 1 is the highest, and its resource can not be occupied
by other levels whenever. The working path of level 2 can not be occupied, but the temp resource
used by rerouting can be occupied by level 1 service. Level 3 to level 8 services resources can
be occupied by the higher level.
When a node or link fails, all the LSPs that are affected by the one-time fault and can be rerouted
are restored in the sequence based on the priority levels. That is, the high-priority LSPs are
restored first. When the backup network resources are insufficient, the high-priority LSPs can
empty the restoring resources of the rerouted low-priority and low-and-delayed-priority LSPs.
NOTE
One-time fault: indicates the collection of faults that occur within the time period (shorter than period T)
after a fault occurs. Period T is the "one-time fault delay time".
For the SDH ASON trail, the relationships between priorities and SLA is list in the following
table.
1-7

SLA Supported Priority
Diamond 1,2
Gold 1,2
Silver 1,2,3,4,5,6,7,8
Copper 1,2,3,4,5,6,7,8
Iron Not Supported
The ASON NE with the version prior than GCP V100R007C03 can not supported eight priority
levels, the relationship between old version and new version ASON NE is list in the following
table.
Priority of ASON NE with GCP
V100R007C03 or prior version
Priority of ASON NE with GCP
V100R007C03 or later version
High 1
Low 2
Low and Delay 3
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-2.
Issue 02 (2010-09-24)

Figure 1-2 Function structure of the ASON
R1
R2
R3
R4
TE Link
ASON NE
SPC
:ASON NE
:User equipment
ASON domain
UNI interface
UNI interface
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-3.
Figure 1-3 ASON NE
Line unit
Cross-
connection
Line unit
Communication and control
Link management protocol（LMP）
Signaling
（RSVP-TE）
Routing
（OSPF-TE）
Traditional NE
ASON NE
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.
1-9

TE Link
TE link is a traffic engineering link. The ASON NE sends its bandwidth information to other
ASON NEs through the TE link to provide data for route computation. One inter-station fiber
can be configured with one TE link.
The resources of a TE link can be classified into three types: non-protection resources, working
resources, and protection resources.
If the MSP is configured on some channels of a fiber, there are three types of resources. For
example, if a 10 Gbit/s (64 VC4s) optical interface is configured with a 2.5 Gbit/s MSP, the TE
links are allocated as follows.
l 1-8 VC4s are the working resources of the TE link.
l 33-40 VC4s are the protection resources of the TE link.
l The rest VC4s are non-protection resources of the TE link.
If the MSP is configured completely in a fiber, there are only working and protection resources
in this fiber.
If the MSP is not configured in a fiber, there are only non-protection resources in this fiber.
Component Link
Component link is a bandwidth unit smaller than a TE link. One TE link consists of only one
component link in the actual ASON software.
NOTE
Each ASON NE floods its own TE links to the whole network through OSPF-TE. Each NE obtains the
network-wide TE links. ASON NEs do not flood their own component links to the whole network. They
only manage and store their own component links.
ASON Domain
An ASON domain is a subset of a network, which is classified by function for the purpose of
route selection and management. An ASON domain consists of several ASON NEs and TE links.
One ASON NE belongs to one ASON domain.
SPC
In the case of soft permanent connection (SPC), the connection between the user and the
transmission network is configured directly by the NM. The connection within the transmission
network, however, is requested by the NM and then created by the NE's control plane through
signaling. When ASON service is mentioned, it usually refers to SPC.
Permanent connection (PC) is a service connection calculated beforehand and then created
through the NM by issuing a command to NE. A traditional SDH service is a PC.
Switched connection (SC) is a service connection requested by a terminal user (for example, a
router) and is then created in the ASON control plane through signaling.
UNI
The user network interface (UNI) is the standard interface for connecting the transmission
network and the client equipment. The client equipment can dynamically request or release the
transmission resources by means of control signaling.
Issue 02 (2010-09-24)

The traditional transmission service configuration is complex and lasts for a long time. The UNI
realizes flexible and real-time service transmission in the transmission network, and thus realizes
end-to-end configuration of the data service.
NOTE
The UNI service connection is performed in the SC mode.
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-4. 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
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-4 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
1-11

performs the verification to verify the consistency of information at both ends of a link.
As shown in Figure 1-5, 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-5 Verifying component links and TE links
Node 1 Node 2
Message
Message
LMP LMP
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
Issue 02 (2010-09-24)

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:
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, component links and TE links.
Control Channels
The LMP creates and maintains the control channel between NEs. The control channel then
provides a physical channel for the LMP packets. The control channels are classified into in-
fiber and out-fiber control channels. The in-fiber control channels automatically find and use
the D4-D12 bytes of DCC. The out-fiber control channel uses the Ethernet links, which should
be manually configured.
The verification of component links and TE links can be performed if the control channels are
available between two adjacent nodes.
At least one control channel should be present between two adjacent nodes. If several fibers
exist between adjacent nodes, several control channels can be created. The LMP selects only
one control channel to transmit protocol packets at a time.
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
1-13

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 DCC channels (D4-D12), they differ in
terms of functions and are independent of each other. The OSPF-TE 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 only manages and stores the information 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. As a kind of resources,
TE links can be regarded as fibers that have bandwidth information and protection attributes.
However, the TE link does not correspond to a fiber respectively, because each fiber may
correspond to many TE links. Currently, a fiber can be configured with one TE link.
The resources of a TE link can be classified into three types: non-protection resources, working
resources, and protection resources.
l If the MSP is configured on some channels of a fiber, there are three types of resources.
For example, if a 10 Gbit/s (64 VC4s) optical interface is configured with a 2.5 Gbit/s MSP,
the TE links are allocated as follows.
– 1-8 VC4s are the working resources of the TE link.
– 33-40 VC4s are the protection resources of the TE link.
– The rest VC4s are non-protection resources of the TE link.
l If the MSP is configured completely in a fiber, there are only working and protection
resources in this fiber.
l If the MSP is not configured in a fiber, there are only non-protection resources in this fiber.
Component Links
Component link is a bandwidth unit smaller than a TE link. One TE link consists of only one
component link in the actual ASON software.
NOTE
Each ASON NE floods its own TE links to the whole network through OSPF-TE. Each NE obtains the
network-wide TE links. ASON NEs do not flood their own component links to the whole network. They
only manage and store their own component links.
UNI Links
The UNI link is the TE link between the client equipment and a network node. The client
equipment can establish the UNI service through the UNI link.
1.2.5 SLA
The ASON network can provide services of different QoS to different clients.
Issue 02 (2010-09-24)

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
Implementation
Means
Switching and
Rerouting Time
Diamond service Protection and
restoration
SNCP and rerouting Switching time <
50ms
Rerouting time < 2 s
Gold service Protection and
restoration
MSP and rerouting Switching time <
50ms
Rerouting time < 2 s
Silver service Restoration Rerouting Rerouting time < 2 s
Copper service No protection
No restoration
- -
Iron service Preemptable MSP -
Table 1-2 lists details of the TE links used by ASON services.
Table 1-2 TE links used by ASON services
Service Level Working
Resource of
TE Link
Protection
Resource of
TE Link
Non-
Protection
Resource of
TE Link
rowsep="1"
Diamond
service
Service creation Not used Not used Used
Service
rerouting
Not used Used when the
resource is not
enough
Used with the
priority
Service
optimization
Not used Not used Used
rowsep="1"
Gold service
Service creation Used with the
priority
resource is not
enough
Service
rerouting
Used with the
priority
Used when the
resource is not
enough
Used when the
resource is not
enough
1-15

Service Level Working
Resource of
TE Link
Protection
Resource of
TE Link
Non-
Protection
Resource of
TE Link
Service
optimization
Used with the
priority
resource is not
enough
Silver service Service creation Not used Not used Used
Service
rerouting
resource is not
enough
Used with the
priority
Service
optimization
Copper service Service creation Not used Not used Used
Service
optimization
Iron service Service creation Not used Used with the
priority
Used when the
resource is not
enough
Service
optimization
Not used Used with the
priority
Used when the
resource is not
enough
1.2.6 Diamond Services
Diamond services have the best protection ability. When there are enough resources in the
network, diamond services provide a permanent 1+1 protection. Diamond services are applicable
to voice and data services, VIP private line, such as banking, security and aviation.
A diamond service is a service with 1+1 protection from the source node to the sink node. It is
also called a 1+1 service. For a diamond service, there are two different LSPs available between
the source node and the sink node. The two LSPs should be as separate as possible. One is the
working LSP and the other is the protection LSP. The same service is transmitted to the working
LSP and the protection LSP at the same time. If the working LSP is normal, the sink node receives
the service from the working LSP; otherwise, from the protection LSP.
Figure 1-6 shows a diamond service.
Issue 02 (2010-09-24)

Figure 1-6 Diamond Services
:ASON NE
:User equipment
R1
R2
R3
R4
A
B
C
D
E
F
G
H
I
Protection LSP
Working 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.
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 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.
1-17

Rerouting l Supports rerouting lockout.
l Supports rerouting priority.
l Supports four rerouting policies:
– Use existing trails whenever possible
– Do not use existing trails whenever possible
– No rerouting constraint
– Use simulated section restoration
l Supports setting the revertive mode.
l Supports setting the trigger condition.
l Supports setting the WTR time.
l Supports setting the crankback times.
l Supports rerouting triggered by B3 bit error.
l Supports setting the rerouting hold-off time.
l Supports setting the revertive lockout.
Revertive Supports Automatically Revertive, Non-Revertive, and
Scheduled revertive.
l After the automatically revertive diamond service is rerouted,
the service is automatically reverted to the original path if the
fault in the original path is rectified.
l After the scheduled revertive diamond service is rerouted, the
user can set the service to be reverted to the original path at
a specific future time (ranging from 10 minutes to 30 days)
on the NMS if the fault in the original path is rectified.
l After the non-revertive diamond service is rerouted, the
service is not reverted to the original route after the fault is
rectified.
Preset restoring trail Supports setting the preset restoring trail.
Service migration l Supports migration between diamond services and permanent
SNCP connections.
l Supports migration between diamond services and gold
services.
l Supports migration between diamond services and silver
services.
l Supports migration between diamond services and copper
services.
Service switching Supports manual switching.
Service optimization Supports service optimization.
Service association Does not support service association.
ASON server trail Support diamond ASON server trails.
Issue 02 (2010-09-24)

Alarms to trigger
rerouting
R_LOS, R_LOF, B2_EXC, B2_SD, MS_AIS, MS_RDI,
AU_AIS, B3_EXC (can be set), B3_SD (can be set)
Table 1-4 Attributes of the rerouting 1+1 diamond service
Attribute Rerouting 1+1 Diamond Service
source node and the sink node
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.
l After the automatically revertive diamond service is rerouted,
the service is automatically reverted to the original path if the
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.
1-19

Attribute Rerouting 1+1 Diamond Service
SNCP connections.
services.
services.
services.
Alarms to trigger
rerouting
R_LOS, R_LOF, B2_EXC, B2_SD, MS_AIS, MS_RDI,
AU_AIS, B3_EXC (can be set), B3_SD (can be set)
Table 1-5 Attributes of the non-rerouting 1+1 diamond service
Attribute Non-rerouting 1+1 diamond service
source node and the sink node
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.
SNCP connections.
services.
services.
services.
Issue 02 (2010-09-24)

Attribute Non-rerouting 1+1 diamond service
1.2.7 Gold Services
Gold services are applicable to voice and significant data services. Compared with diamond
services, gold services have greater bandwidth utilization.
A gold service needs only one LSP. This LSP must use working resource of TE links or non-
protection resource of TE links. When a fiber on the path of a gold service is cut, the ASON
triggers MSP switching to protect the service at first. If the multiplex section protection fails,
the ASON triggers rerouting to restore the service.
As shown in Figure 1-7, a gold service can be configured from A to I.
Figure 1-7 Gold services
R1
R2
R3
R4
:ASON NE
:User equipment
A
B
C
D
E
F
G
H
MSP
MSP
MSP
I
Table 1-6 lists the attributes of gold services.
Table 1-6 Attributes of gold services
Attribute Gold Service
Requirements for creation Sufficient working resources or non-protection resources are
available between the source node and the sink node.
1-21

Attribute Gold Service
Multiplex section
protection
l Supports using the working resources of a 1:1 linear multiplex
section protection chain to create gold services.
l Supports using the working resources of a 1+1 linear
multiplex section protection chain to create gold services.
l Supports using the working resources of a 1:N linear
multiplex section protection chain to create gold services.
l Supports using the working resources of a two-fiber
bidirectional multiplex section protection ring to create gold
services.
l Supports using the working resources of a four-fiber
bidirectional multiplex section protection ring to create gold
services.
Protection and restoration When a fiber is cut for the first time, MS switching is performed
to protect services. When MS switching fails, rerouting is then
triggered to restore services.
l After the automatically revertive gold service is rerouted, the
service is automatically reverted to the original path if the
l After the scheduled revertive gold service is rerouted, the user
can set the service to be reverted to the original path at a
specific future time (ranging from 10 minutes to 30 days) on
the NMS if the fault in the original path is rectified.
l After the non-revertive gold service is rerouted, the service
is not reverted to the original route after the fault is rectified.
Issue 02 (2010-09-24)

iManager U2000 Operation Guide for SDH ASON Network Management

iManager U2000 Operation Guide for SDH ASON Network Management

Recommended

Recommended

More Related Content

What's hot

What's hot (10)

Viewers also liked

Viewers also liked (20)

Similar to iManager U2000 Operation Guide for SDH ASON Network Management

Similar to iManager U2000 Operation Guide for SDH ASON Network Management (20)

Recently uploaded

Recently uploaded (20)

iManager U2000 Operation Guide for SDH ASON Network Management