OG for SDH ASON Network Management-(V100R002C01 02)[1]

iManager U2000 Unified Network ManagementSystemV100R002C01

Operation Guide for SDH ASONNetwork 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 writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2010-09-24) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

Related VersionThe following table lists the product version related to this document.

Product Name Version

iManager U2000 V100R002C01

Intended AudienceThis document describes the procedures and operations, such as how to configure and maintainthe SDH ASON network. This document also provide the timeslot numbering policy, theglossary, 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 ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

DANGERIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management About This Document


iii

Symbol Description

CAUTIONIndicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or savetime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

Command ConventionsThe 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 byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare 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 DocumentiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24)

Update HistoryUpdates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Updates in Issue 02 (2010-09-24) Based on Product Version V100R002C01The 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 V100R002C01The first release of the iManager U2000 V100R002C01.

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management About This Document


v

Contents

About This Document...................................................................................................................iii

1 Configuring SDH ASON Networks.......................................................................................1-11.1 SDH ASON Network Configuration...............................................................................................................1-41.2 ASON..............................................................................................................................................................1-5

1.2.1 Basic Concepts of ASON.......................................................................................................................1-61.2.2 Function Structure of the ASON............................................................................................................1-81.2.3 ASON Protocol....................................................................................................................................1-111.2.4 ASON Links.........................................................................................................................................1-131.2.5 SLA......................................................................................................................................................1-141.2.6 Diamond Services................................................................................................................................1-161.2.7 Gold Services.......................................................................................................................................1-211.2.8 Silver Services......................................................................................................................................1-231.2.9 Copper Services....................................................................................................................................1-251.2.10 Iron Services.......................................................................................................................................1-261.2.11 OVPN.................................................................................................................................................1-271.2.12 UNI Services......................................................................................................................................1-29

1.3 Creating an ASON Topology........................................................................................................................1-311.3.1 Creating NEs in Batches......................................................................................................................1-331.3.2 Creating a Single NE............................................................................................................................1-351.3.3 Setting the Node ID..............................................................................................................................1-361.3.4 Enabling the ASON Feature ................................................................................................................1-371.3.5 Uploading NE Configuration Data.......................................................................................................1-381.3.6 Enable the ASON Feature of a Board..................................................................................................1-391.3.7 Creating Domains for an ASON Network...........................................................................................1-391.3.8 Synchronizing ASON NEs...................................................................................................................1-401.3.9 Automatically Creating Fibers According to TE Link.........................................................................1-411.3.10 Setting the Primary NE or Secondary NE..........................................................................................1-421.3.11 Setting Control Plane Parameters.......................................................................................................1-421.3.12 Viewing ASON NE Software Version...............................................................................................1-44

1.4 Managing the ASON Protocol......................................................................................................................1-441.4.1 Modifying the LMP Discovery Type...................................................................................................1-461.4.2 Querying the LMP Discovery Type.....................................................................................................1-471.4.3 Disabling the LMP Protocol.................................................................................................................1-48

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management Contents


vii

1.4.4 Disabling the OSPF Protocol...............................................................................................................1-491.4.5 Encrypting the OSPF Protocol.............................................................................................................1-501.4.6 Setting the OSPF TE Link Flood Threshold........................................................................................1-501.4.7 Encrypting RSVP.................................................................................................................................1-511.4.8 Creating Out-Fiber Control Channels..................................................................................................1-52

1.5 Managing ASON Clock Subnet....................................................................................................................1-541.5.1 Creating an ASON Clock Subnet.........................................................................................................1-541.5.2 Converting a Preconfigured ASON Clock Subnet into an ASON Clock Subnet................................1-571.5.3 Converting a Traditional Clock Subnet into an ASON Clock Subnet.................................................1-611.5.4 Managing a Hybrid Network Composed of an ASON Clock Subnet and a Traditional Clock Subnet.......................................................................................................................................................................1-641.5.5 Setting the Clock Fault Recover Time.................................................................................................1-67

1.6 Managing Link Resources.............................................................................................................................1-671.6.1 Synchronizing Control Links Networkwide........................................................................................1-691.6.2 Synchronizing TE Links.......................................................................................................................1-691.6.3 Viewing TE Links................................................................................................................................1-701.6.4 Configuring the Link Distance.............................................................................................................1-711.6.5 Setting the Custom Cost of the TE Link .............................................................................................1-711.6.6 Setting the Usage Threshold of Fiber Resources.................................................................................1-721.6.7 Creating an SRLG................................................................................................................................1-721.6.8 Querying VC4 Timeslot Occupation Status.........................................................................................1-731.6.9 Querying the Information About the Timeslots on the Link Sections.................................................1-741.6.10 Setting Resource Reservation.............................................................................................................1-751.6.11 Creating a Virtual Interfaces..............................................................................................................1-771.6.12 Creating a Virtual TE Link.................................................................................................................1-781.6.13 Creating a TE Link Based on Virtual Interfaces................................................................................1-801.6.14 Deleting an Interrupted TE Link Manually........................................................................................1-84

1.7 Managing SRGs............................................................................................................................................1-851.7.1 Creating an SRG...................................................................................................................................1-851.7.2 Querying the SRG Related to a TE Link..............................................................................................1-891.7.3 Querying the SRG Related to an ASON NE........................................................................................1-89

1.8 Creating ASON Services...............................................................................................................................1-901.8.1 Synchronizing ASON Trails................................................................................................................1-911.8.2 Creating a Diamond ASON Service.....................................................................................................1-921.8.3 Creating a Gold ASON service............................................................................................................1-961.8.4 Creating a Silver ASON Service........................................................................................................1-1001.8.5 Creating a Copper ASON Service......................................................................................................1-1041.8.6 Creating an Iron ASON Service.........................................................................................................1-1071.8.7 Creating an ASON Server Trail.........................................................................................................1-1111.8.8 Creating a Segmented ASON Server Trail........................................................................................1-1151.8.9 Creating Two Associated SDH ASON Trails....................................................................................1-1181.8.10 Setting ASON Trail Association......................................................................................................1-1201.8.11 Creating ASON Services in Batches................................................................................................1-121

ContentsiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management

viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24)

1.8.12 Deactivating the SDH ASON Trail..................................................................................................1-1251.8.13 Deleting an ASON Trail...................................................................................................................1-126

1.9 Modifying the Attributes of ASON Services..............................................................................................1-1271.9.1 Viewing ASON Service Attributes....................................................................................................1-1271.9.2 Setting the Routing Attributes............................................................................................................1-1291.9.3 Setting the Scheduled Reversion Time..............................................................................................1-1291.9.4 Setting the B3 Alarm to Trigger Rerouting........................................................................................1-1301.9.5 Setting Preset Restoration Trail..........................................................................................................1-1311.9.6 Setting Shared MESH Restoration Trail............................................................................................1-1321.9.7 Setting the Original Route..................................................................................................................1-133

1.10 Modifying the Route of an ASON Service...............................................................................................1-1331.10.1 Reverting ASON Trails....................................................................................................................1-1341.10.2 Optimizing an ASON Service..........................................................................................................1-135

1.11 Migrating ASON Services........................................................................................................................1-1361.11.1 Downgrading an ASON Service to a Traditional Service................................................................1-1361.11.2 Upgrading a Traditional Service to an ASON Service.....................................................................1-1371.11.3 Migration Between ASON Services................................................................................................1-1381.11.4 Downgrading an ASON Server Trail to a Traditional Server Trail.................................................1-1391.11.5 Upgrading a Traditional Server Trail to an ASON Server Trail......................................................1-1401.11.6 Migration Between ASON Server Trails.........................................................................................1-141

1.12 Creating ASON Trail Groups....................................................................................................................1-1421.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-1451.13.2 Creating a VC12 Service Between Traditional NEs that Cross an ASON Domain.........................1-1491.13.3 Creating a VC4 Service Between a Traditional NE and an ASON NE...........................................1-1521.13.4 Creating a VC12 Service Between a Traditional NE and an ASON NE.........................................1-1561.13.5 Creating a 1+1 VC12 Service Between a Traditional NE and an ASON NE..................................1-1591.13.6 Creating a 1+1 VC4 Service Between a Traditional NE and an ASON NE....................................1-1641.13.7 Creating a 1+1 VC12 Service Between Traditional NEs That Cross an ASON Domain................1-1701.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-1781.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-1821.15.2 Creating SNCP Services Between Traditional NEs That Cross an ASON Domain........................1-1871.15.3 Querying the Information About the SNCP Accessed Service........................................................1-1931.15.4 Performing Switching at the SNCP Access End..............................................................................1-193

1.16 Managing UNI Services............................................................................................................................1-1941.16.1 Flow of Configuring UNI Services..................................................................................................1-1951.16.2 Enabling the UNI Feature of an ASON NE.....................................................................................1-1961.16.3 Setting the Information About the GMPLS UNI ............................................................................1-1971.16.4 Setting the Information About the OIF UNI ...................................................................................1-2001.16.5 Setting the UNI Access Policy.........................................................................................................1-202



ix

1.16.6 Setting the Information About the GMPLS UNI Link.....................................................................1-2031.16.7 Setting the Information About the OIF UNI Link............................................................................1-2041.16.8 Querying UNI Services....................................................................................................................1-2051.16.9 Deleting UNI Services.....................................................................................................................1-206

1.17 Managing the OVPN Customers and OVPN Services..............................................................................1-2071.17.1 Enabling OVPN Function of ASON NE..........................................................................................1-2081.17.2 Creating NM User for OVPN Customer..........................................................................................1-2081.17.3 Creating an OVPN Customer...........................................................................................................1-2101.17.4 Allocating TE Links for OVPN Customers.....................................................................................1-2121.17.5 Creating OVPN Services..................................................................................................................1-2131.17.6 Querying the TE Link Resources of the OVPN Customers.............................................................1-2161.17.7 Querying the Services of the OVPN Customers..............................................................................1-217

1.18 Importing and Exporting Data...................................................................................................................1-2181.18.1 Exporting Data from U2000 to MDS...............................................................................................1-2181.18.2 Importing Data from MDS to U2000...............................................................................................1-219

1.19 Managing Control Plane Alarms and Performance Events.......................................................................1-2201.19.1 Querying Control Plane Alarms.......................................................................................................1-2211.19.2 Setting the Severity of Control Plane Alarm....................................................................................1-2211.19.3 Setting the Auto-Report Status of the Control Plane Alarm............................................................1-2221.19.4 Suppressing Control Plane Alarms..................................................................................................1-2221.19.5 Suppressing Control Plane Alarm Events........................................................................................1-2231.19.6 Querying the Performance of the Control Plane..............................................................................1-2231.19.7 Monitoring the Control Plane Performance.....................................................................................1-2241.19.8 Setting the Auto-Report Status of the Control Plane Performance Data.........................................1-2251.19.9 Setting the Control Plane Performance Threshold ..........................................................................1-226

2 Routine Maintenance for an ASON Network......................................................................2-12.1 Precautions for Routine Maintenance.............................................................................................................2-22.2 Routine Maintenance Items.............................................................................................................................2-3

2.2.1 Periodically Refreshing the ASON information....................................................................................2-42.2.2 Querying Network-Wide Alarms...........................................................................................................2-42.2.3 Querying ASON Trail Alarms...............................................................................................................2-52.2.4 Querying Control Plane Alarms.............................................................................................................2-62.2.5 Querying Control Link Alarms..............................................................................................................2-72.2.6 Querying TE Link Alarms......................................................................................................................2-72.2.7 Creating a Performance Filtering Template...........................................................................................2-82.2.8 Querying the Performance of the Control Plane....................................................................................2-82.2.9 Querying Abnormal ASON Events........................................................................................................2-92.2.10 Checking the Running Status of ASON Trails...................................................................................2-102.2.11 Checking TE Links.............................................................................................................................2-122.2.12 Checking Control Links.....................................................................................................................2-132.2.13 Checking the Activation Status of ASON Services...........................................................................2-13

3 Handling ASON Network Failures........................................................................................3-1

ContentsiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management

x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24)

3.1 Handling Link Failures....................................................................................................................................3-23.1.1 Handling Impassable Control Channels.................................................................................................3-23.1.2 Handling Impassable Component Links................................................................................................3-33.1.3 Handling Impassable TE Links..............................................................................................................3-33.1.4 Handling Downgraded TE Links........................................................................................................... 3-4

3.2 Handling the Failure in Creating Trails...........................................................................................................3-43.2.1 Handling the Failure of Route Computation..........................................................................................3-53.2.2 Handling the Failure to Allocate Labels................................................................................................ 3-63.2.3 Handling the Failure in Creating Services in Batches............................................................................3-6

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

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management Figures


xiii

Figure 1-34 Schematic diagram of the topology of the TE links in an SRG......................................................1-86Figure 1-35 Diamond service requirement.........................................................................................................1-92Figure 1-36 Board configuration for NE1 and NE3...........................................................................................1-93Figure 1-37 Gold service requirement................................................................................................................1-97Figure 1-38 Board configuration for NE1 and NE3...........................................................................................1-97Figure 1-39 Silver service requirement............................................................................................................1-101Figure 1-40 Board configuration for NE1 and NE3.........................................................................................1-101Figure 1-41 Copper service requirement..........................................................................................................1-104Figure 1-42 Board configuration for NE1 and NE3.........................................................................................1-105Figure 1-43 Iron service requirement...............................................................................................................1-108Figure 1-44 Board configuration for NE1 and NE3.........................................................................................1-108Figure 1-45 Diamond ASON server trail requirement.....................................................................................1-111Figure 1-46 Board configuration for NE1 and NE3.........................................................................................1-112Figure 1-47 Segmented ASON server trail requirement..................................................................................1-115Figure 1-48 Board configuration for NE1-NE3...............................................................................................1-116Figure 1-49 Two associated ASON trails ........................................................................................................1-118Figure 1-50 Batch silver service requirement..................................................................................................1-122Figure 1-51 Board configuration for NE1 and NE3.........................................................................................1-122Figure 1-52 ASON trail group service requirement.........................................................................................1-142Figure 1-53 Board configuration of NE1 and NE3..........................................................................................1-143Figure 1-54 Board configuration of NE2 and NE4..........................................................................................1-143Figure 1-55 VC4 service requirement between traditional NEs......................................................................1-146Figure 1-56 Board configuration for NE1-NE4...............................................................................................1-146Figure 1-57 Board configuration for NE5 and NE6.........................................................................................1-147Figure 1-58 VC12 service requirement between traditional NEs....................................................................1-149Figure 1-59 Board configuration for NE1-NE4...............................................................................................1-150Figure 1-60 Board configuration for NE5 and NE6.........................................................................................1-150Figure 1-61 VC4 service requirement between traditional and ASON NEs....................................................1-152Figure 1-62 Board configuration for NE1........................................................................................................1-153Figure 1-63 Board configuration for NE2-NE4...............................................................................................1-153Figure 1-64 Board configuration for NE5 and NE6.........................................................................................1-154Figure 1-65 VC12 service requirement between traditional and ASON NEs..................................................1-156Figure 1-66 Board configuration for NE1-NE4...............................................................................................1-157Figure 1-67 Board configuration for NE5 and NE6.........................................................................................1-157Figure 1-68 1+1 VC12 service requirement between traditional and ASON NEs..........................................1-160Figure 1-69 Board configuration for NE1-NE4...............................................................................................1-160Figure 1-70 Board configuration for NE5 and NE6.........................................................................................1-161Figure 1-71 1+1 VC4 service requirement between a traditional NE and an ASON NE................................1-165Figure 1-72 Board configuration of NE1-NE4.................................................................................................1-165Figure 1-73 Board configuration of NE5 and NE6..........................................................................................1-166Figure 1-74 1+1 VC12 service requirement between traditional NEs.............................................................1-170Figure 1-75 Board configuration of NE1-NE4.................................................................................................1-171

FiguresiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management

xiv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24)

Figure 1-76 Board configuration of NE5 and NE6..........................................................................................1-171Figure 1-77 1+1 VC4 service requirement between traditional NEs...............................................................1-175Figure 1-78 Board configuration of NE1-NE4.................................................................................................1-175Figure 1-79 Board configuration of NE5 and NE6..........................................................................................1-176Figure 1-80 Accessing 1+1 linear MSP...........................................................................................................1-179Figure 1-81 Board configuration of NE1 and NE4..........................................................................................1-179Figure 1-82 Board configuration of NE2 and NE3..........................................................................................1-180Figure 1-83 Board configuration of NE5.........................................................................................................1-180Figure 1-84 SNCP service between a traditional NE and an ASON NE.........................................................1-183Figure 1-85 Board configuration of NE1-NE4.................................................................................................1-183Figure 1-86 Board configuration of NE5-NE7.................................................................................................1-184Figure 1-87 SNCP services between traditional NEs that cross the ASON domain........................................1-188Figure 1-88 Board configuration of NE1-NE4.................................................................................................1-188Figure 1-89 Board configuration of NE5-NE10...............................................................................................1-189Figure 1-90 Flow of configuring UNI services................................................................................................1-196Figure 1-91 Setting the information about the GMPLS UNI ..........................................................................1-198Figure 1-92 Board configuration of NE1.........................................................................................................1-198Figure 1-93 Board configuration of NE3.........................................................................................................1-199Figure 1-94 Setting the information about the OIF UNI .................................................................................1-200Figure 1-95 Board configuration of NE1.........................................................................................................1-201Figure 1-96 Board configuration of NE3.........................................................................................................1-201Figure 1-97 OVPN service requirements.........................................................................................................1-214Figure 1-98 Board configuration of NE1 and NE3..........................................................................................1-214

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management Figures


xv

Tables

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

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management Tables


xvii

Table 1-34 VC4 service planning between traditional NE and ASON NE......................................................1-154Table 1-35 Silver ASON server trail planning.................................................................................................1-158Table 1-36 VC12 service planning for NE1, NE4 and NE5............................................................................1-158Table 1-37 Service planning for double silver ASON server trails..................................................................1-161Table 1-38 SNCP service planning for NE5....................................................................................................1-161Table 1-39 SNCP service planning for NE1....................................................................................................1-162Table 1-40 Service planning for NE3 and NE4................................................................................................1-163Table 1-41 Service planning for the two silver ASON trails...........................................................................1-166Table 1-42 SNCP service planning for NE5....................................................................................................1-166Table 1-43 SNCP service planning for NE1....................................................................................................1-167Table 1-44 Service planning for NE3 and NE4................................................................................................1-167Table 1-45 Planning of two silver ASON trails...............................................................................................1-172Table 1-46 SNCP service planning of NE5......................................................................................................1-172Table 1-47 SNCP service planning of NE6......................................................................................................1-173Table 1-48 Planning of Two Silver ASON Trails............................................................................................1-176Table 1-49 SNCP service planning of NE5......................................................................................................1-177Table 1-50 SNCP service planning of NE6......................................................................................................1-177Table 1-51 Planning of Diamond Services Accessed Through 1+1 Linear MSP............................................1-181Table 1-52 Planning of the diamond service between NE1 and NE3..............................................................1-184Table 1-53 SNCP service planning for NE1 and NE5.....................................................................................1-185Table 1-54 Service planning for NE6 and NE7................................................................................................1-185Table 1-55 Planning of the diamond service between NE1 and NE3..............................................................1-189Table 1-56 SNCP service planning for NE1, NE3, NE5, and NE9..................................................................1-190Table 1-57 Service planning for NE6, NE7, NE8, and NE10..........................................................................1-190Table 1-58 OVPN service planning..................................................................................................................1-215Table 2-1 Abnormal Events List........................................................................................................................2-10

TablesiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management

xviii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24)

1 Configuring SDH ASON Networks

About This Chapter

You can configure an ASON network using the U2000.

1.1 SDH ASON Network ConfigurationThis section describes how to configure an ASON network on the U2000.

1.2 ASONThe automatically switched optical network (ASON) is a new generation optical transmissionnetwork. An ASON NE refers to the equipment that has ASON features. An ASON NE also hasthe features of traditional SDH NEs besides the ASON features. The U2000 manages the ASONnetwork by integrating the ASON features with the SDH features.

1.3 Creating an ASON TopologyThe ASON network uses the route protocol to create the topology information of the nodes inthe network so that each node can obtain a networkwide topology. The U2000 can discover otherASON NEs in the network from any ASON NE.

1.4 Managing the ASON ProtocolAfter 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 facilitatethe management of ASON link resources and ASON services.

1.5 Managing ASON Clock SubnetClock subnet is classified into ASON clock subnet and traditional clock subnet. Beforeconfiguring ASON services, you need to create a clock subnet to ensure that a consistent clocktracing relation is created for all NEs in the ASON network.

1.6 Managing Link ResourcesASON is capable of automatically switching optical network connections under the control ofthe signaling network. It dynamically allocates network resources as required. As the networkis growing larger, a more reasonable way of resource management is required to make the mostof the network resources and to improve the network efficiency. Link resource management isone aspect of resource management. In an actual network, thousands of connections may existbetween 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 areregarded as a whole, which is known as the traffic engineer link (TE link), serving as theprocessing object of the route information.

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management 1 Configuring SDH ASON Networks


1-1

1.7 Managing SRGsThe TE links in the same optical cable, NE, site, and pipe have the same risk. You can find abalance 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 ServicesThe trail levels that an ASON trail supports are as follows: diamond, gold, silver, copper andiron. 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 anASON trail.

1.9 Modifying the Attributes of ASON ServicesAs an ASON network is changing, you need to modify the attributes of ASON services in thenetwork according to different ASON features. This facilitates the configuration, managementand maintenance of the ASON network.

1.10 Modifying the Route of an ASON ServiceAs an ASON network is changing, you need to modify the route of an ASON service in thenetwork according to different situations. This facilitates the configuration, management andmaintenance of the ASON network.

1.11 Migrating ASON ServicesAn ASON network supports the migration between traditional services and ASON services, andsupports the in-service migration between ASON services at different levels.

1.12 Creating ASON Trail GroupsAn ASON trail group is often used with LCAS.

1.13 Creating Services Between an ASON NE and a Traditional NEA network can consist of ASON NEs and traditional NEs. This realizes end-to-end serviceconfiguration and management.

1.14 Accessing a Traditional Network to an ASON Through Linear MSPWhen accessing services from a traditional network, to ensure that reliability of the accessedservices, you can create a 1+1 or 1:1 linear MSP at the edge of the traditional network and anASON domain. You can configure services in an ASON domain to the diamond , gold, and silverlevel.

1.15 Accessing a Traditional Network to an ASON Network by Using the SNCP AccessedServiceWhen a traditional network is accessed to an ASON network by using the SNCP accessedservice, the end-to-end SNCP is implemented for the service.

1.16 Managing UNI ServicesThe UNI is the standard interface that is used to connect the client equipment to the transportnetwork. When the UNI is used, the client equipment can dynamically request transportresources 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 thanconfiguring traditional services. UNI services improve the reliability and real-time performanceof the transport network so that burst data service requirements can be met and end-to-end UNIservices can be realized.

1.17 Managing the OVPN Customers and OVPN ServicesIn the case of the OVPN, an ASON network is shared by multiple operators. When multipleoperators need to share an ASON network, you can allocate different TE link resources for eachoperator. Each operator can use and manage its own TE link resources and ASON services.

1.18 Importing and Exporting Data

1 Configuring SDH ASON NetworksiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management

1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 02 (2010-09-24)

The existing ASON network may not be optimum, so we can use the OptiX Modeling and DesignSystem (MDS) to optimize the network. You can import the ASON data on the U2000 to theMDS, 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 settingsto NEs to optimize the existing ASON network.

1.19 Managing Control Plane Alarms and Performance EventsUsers 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 thresholdbased on actual requirements.



1-3

1.1 SDH ASON Network ConfigurationThis section describes how to configure an ASON network on the U2000.

To configure an ASON network, the traditional network must run normally, and the ASONsoftware must be enabled and runs normally after commissioning. For details about thecommissioning 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 NEconnected with the U2000 asa GNE.

2 Uploading NEConfiguration Data

Upload data to the U2000 toensure that the data on theU2000 is consistent with thaton the NE.

3 Creating Domains for anASON Network

Create an ASON domain andassign the ASON NEs thatbelong to the same ASONnetwork to the ASONdomain.

4 Setting the Primary NE orSecondary NE

To improve the reliability,another NE can be set as thestandby of the primary NE.

5 Synchronizing ASON NEs Synchronize datanetworkwide. The U2000searches for ASON NEs anddisplays them in the topologyview.

6 Automatically CreatingFibers According to TELink

The U2000 can create fibersbetween NEs according tothe TE links.

7 Managing Link Resources A more reasonable way ofresource management isrequired to make the most ofthe network resources and toimprove the networkefficiency.

8 Creating ASON Services The U2000 provides the end-to-end ASON trailmanagement feature.

9 Routine MaintenanceItems

View alarms and abnormalevents.



Issue 02 (2010-09-24)

1.2 ASONThe automatically switched optical network (ASON) is a new generation optical transmissionnetwork. An ASON NE refers to the equipment that has ASON features. An ASON NE also hasthe features of traditional SDH NEs besides the ASON features. The U2000 manages the ASONnetwork by integrating the ASON features with the SDH features.

1.2.1 Basic Concepts of ASONThe basic concepts related to the ASON are the three planes, label switched path (LSP) andrerouting.

1.2.2 Function Structure of the ASONAn ASON network consists of ASON NEs, TE links, domains and SPC (soft permanentconnections).

1.2.3 ASON ProtocolHuawei OptiX GCP applies the link management protocol (LMP) as the link managementprotocol, OSPF-TE as the routing protocol, and RSVP-TE as the signaling protocol.

1.2.4 ASON LinksASON Links include control channels, control links, component links and TE links.

1.2.5 SLAThe ASON network can provide services of different QoS to different clients.

1.2.6 Diamond ServicesDiamond services have the best protection ability. When there are enough resources in thenetwork, diamond services provide a permanent 1+1 protection. Diamond services are applicableto voice and data services, VIP private line, such as banking, security and aviation.

1.2.7 Gold ServicesGold services are applicable to voice and significant data services. Compared with diamondservices, gold services have greater bandwidth utilization.

1.2.8 Silver ServicesSilver services, the revertive time is hundreds of milliseconds to several seconds. The silver levelservice is suitable for those data or internet services that have low real-time requirement.

1.2.9 Copper ServicesThe copper services are seldom used. Generally, temporary services, such as the abrupt servicesin holidays, are configured as copper services.

1.2.10 Iron ServicesThe iron services are also seldom used. Generally, temporary services are configured as ironservices. For example, when service volume soars, during holidays, the services can beconfigured as iron services to fully use the bandwidth resources.

1.2.11 OVPNThe optical virtual private network (OVPN) divides the TE links in an ASON network todifferent customers. Sharing the fiber resources, the customers, however, can use and manageonly 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 equipmentinitiates a request to the ASON equipment and the signaling is received. UNI services can beclassified into Ethernet UNI services and SDH UNI services.

1.2.1 Basic Concepts of ASONThe basic concepts related to the ASON are the three planes, label switched path (LSP) andrerouting.

As shown in Figure 1-1, the ASON has three planes: the control plane, the transport plane, andthe management plane.

Figure 1-1 Three planes of the ASON

Control plane

Transmission plane

Managementplane

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 callingcontrol and connection control, including automatic setting up, releasing, monitoring, andmaintaining connections. The control plane automatically restores the failed connections throughsignaling exchange.



Issue 02 (2010-09-24)

Transport PlaneThe traditional SDH network is the transport plane. It transmits and multiplexes optical signals,configures cross-connection and protection switching for optical signals, and guarantees thereliability of all optical signals.

Management PlaneThe 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 includeperformance management, fault management, configuration management and securitymanagement.

LSPLabel switched path (LSP) is the path ASON services pass through. In an ASON, to create ASONservices is to create LSPs. On U2000, LSP is also called ASON Trail.

ReroutingRerouting is a means of resuming services. When an LSP is disconnected, the source node queriesand finds the best route to resume services. Then, the initial node creates a new LSP to transmitthe service. After creating a new LSP, the source node deletes the original LSP.

CAUTIONAfter a revertive service reroutes, the original LSP is not deleted.

Rerouting LockoutIn some cases, rerouting is not required after failure of LSP. Then you need to set reroutinglockout.

Rerouting PriorityThere are 8 levels of rerouting priority. Level 1 is the highest, and its resource can not be occupiedby other levels whenever. The working path of level 2 can not be occupied, but the temp resourceused by rerouting can be occupied by level 1 service. Level 3 to level 8 services resources canbe 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 reroutedare restored in the sequence based on the priority levels. That is, the high-priority LSPs arerestored first. When the backup network resources are insufficient, the high-priority LSPs canempty 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 followingtable.



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 prioritylevels, the relationship between old version and new version ASON NE is list in the followingtable.

Priority of ASON NE with GCPV100R007C03 or prior version

Priority of ASON NE with GCPV100R007C03 or later version

High 1

Low 2

Low and Delay 3

Rerouting PolicyDiamond, 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 theservice, the service can first be switched to one of the other available TE links between thetwo nodes.

1.2.2 Function Structure of the ASONAn ASON network consists of ASON NEs, TE links, domains and SPC (soft permanentconnections).

See Figure 1-2.



Issue 02 (2010-09-24)

Figure 1-2 Function structure of the ASON

R1

R2

R3

R4

TE LinkASON NE

SPC

:ASON NE

:User equipment

ASON domain

UNI interface

UNI interface

ASON NEAn ASON NE is one of the topology components in the ASON. An ASON NE has the followingfunctions 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 thenode ID is the same as that of the IP address. But the node ID and the IP address of the NE mustbe at different network sections.

As a unique identification for NEs on the transport plane, the node ID has the same meaningregarding 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 LinkTE link is a traffic engineering link. The ASON NE sends its bandwidth information to otherASON NEs through the TE link to provide data for route computation. One inter-station fibercan be configured with one TE link.

The resources of a TE link can be classified into three types: non-protection resources, workingresources, and protection resources.

If the MSP is configured on some channels of a fiber, there are three types of resources. Forexample, if a 10 Gbit/s (64 VC4s) optical interface is configured with a 2.5 Gbit/s MSP, the TElinks 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 resourcesin this fiber.

If the MSP is not configured in a fiber, there are only non-protection resources in this fiber.

Component LinkComponent link is a bandwidth unit smaller than a TE link. One TE link consists of only onecomponent 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 thenetwork-wide TE links. ASON NEs do not flood their own component links to the whole network. Theyonly manage and store their own component links.

ASON DomainAn ASON domain is a subset of a network, which is classified by function for the purpose ofroute selection and management. An ASON domain consists of several ASON NEs and TE links.One ASON NE belongs to one ASON domain.

SPCIn the case of soft permanent connection (SPC), the connection between the user and thetransmission network is configured directly by the NM. The connection within the transmissionnetwork, however, is requested by the NM and then created by the NE's control plane throughsignaling. When ASON service is mentioned, it usually refers to SPC.

Permanent connection (PC) is a service connection calculated beforehand and then createdthrough 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, arouter) and is then created in the ASON control plane through signaling.

UNIThe user network interface (UNI) is the standard interface for connecting the transmissionnetwork and the client equipment. The client equipment can dynamically request or release thetransmission 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 UNIrealizes flexible and real-time service transmission in the transmission network, and thus realizesend-to-end configuration of the data service.

NOTE

The UNI service connection is performed in the SC mode.

1.2.3 ASON ProtocolHuawei OptiX GCP applies the link management protocol (LMP) as the link managementprotocol, 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.

LMPThe 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 2returns a message to Node 1, indicating that the messages fail to pass the check. In thisway, Node 2 waits for another check. Hence, a control channel between the two adjacentnodes is created.

– After the control channel is created, the two nodes store the information about the controlchannel 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 areconfigured according to the attributes of the optical interface. The attributes include slotnumber, 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 toNode 2, which checks if it has the same information and returns the check result to Node1. If the verification shows consistency, the OSPF-TE can then flood the informationabout 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-TEThe control plane of Huawei OptiX GCP applies the OSPF-TE, which is an extended protocolfor 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 arerequired for forwarding messages on the control plane.

l Floods and collects the information about the TE links on the transport plane. The protocolthen generates the information about the network service topologies for service trailcomputation.

RSVP-TEThe RSVP-TE is a protocol for resource reservation. It is a type of signaling. In terms of trafficengineering, the RSVP is extended to RSVP-TE. The RSVP-TE mainly supports the followingfunctions:l LSP creationl LSP deletionl LSP attribute modificationl LSP reroutingl LSP trail optimization

Protocol EncryptionAn external entity may modify the OSPF-TE protocol packets of the network, counterfeit a nodeof this network and transmit packets, or receive the packets transmitted by nodes in the networkand 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 forauthentication.

The RSVP authentication is configured for nodes and the OSPF-TE authentication forinterconnected 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 arethe same.

UNI ProtocolThe UNI is the standard interface for connecting the transmission network and the clientequipment. Currently, there are two schemes, namely, OIF and GMPLS. The equipment supportsthe 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 LinksASON Links include control channels, control links, component links and TE links.

Control ChannelsThe LMP creates and maintains the control channel between NEs. The control channel thenprovides 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 usethe D4-D12 bytes of DCC. The out-fiber control channel uses the Ethernet links, which shouldbe manually configured.

The verification of component links and TE links can be performed if the control channels areavailable between two adjacent nodes.

At least one control channel should be present between two adjacent nodes. If several fibersexist between adjacent nodes, several control channels can be created. The LMP selects onlyone control channel to transmit protocol packets at a time.

Control LinksControl links are the communication links created for the communication between the protocolentities 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 ofeach NE computes the shortest control routes to each NE according to the control topology. Theroutes are then recorded in the forward table. The signaling RSVP then uses the routes to transmitmessage packets.

By default, control links are created in fibers. Control links can also be created outside fibers onthe 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 interms of functions and are independent of each other. The OSPF-TE protocol floods the information aboutthe control links to the entire network. Each ASON NE stores the information about the network-widecontrol 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 LinksTE link is a traffic engineering link. The ASON NE sends its bandwidth information to otherASON 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 maycorrespond 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, workingresources, 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 protectionresources in this fiber.

l If the MSP is not configured in a fiber, there are only non-protection resources in this fiber.

Component LinksComponent link is a bandwidth unit smaller than a TE link. One TE link consists of only onecomponent 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 thenetwork-wide TE links. ASON NEs do not flood their own component links to the whole network. Theyonly manage and store their own component links.

UNI LinksThe UNI link is the TE link between the client equipment and a network node. The clientequipment can establish the UNI service through the UNI link.

1.2.5 SLAThe 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 andRestorationScheme

ImplementationMeans

Switching andRerouting Time

Diamond service Protection andrestoration

SNCP and rerouting Switching time <50msRerouting time < 2 s

Gold service Protection andrestoration

MSP and rerouting Switching time <50msRerouting time < 2 s

Silver service Restoration Rerouting Rerouting time < 2 s

Copper service No protectionNo 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 WorkingResource ofTE Link

ProtectionResource ofTE Link

Non-ProtectionResource ofTE Link

rowsep="1"Diamondservice

Service creation Not used Not used Used

Servicererouting

Not used Used when theresource is notenough

Used with thepriority

Serviceoptimization

Not used Not used Used

rowsep="1"Gold service

Service creation Used with thepriority


Servicererouting


Used when theresource is notenough




1-15

Service Level WorkingResource ofTE Link

ProtectionResource ofTE Link

Non-ProtectionResource ofTE Link

Serviceoptimization



Silver service Service creation Not used Not used Used

Servicererouting



Serviceoptimization


Copper service Service creation Not used Not used Used

Serviceoptimization


Iron service Service creation Not used Used with thepriority


Serviceoptimization

Not used Used with thepriority


1.2.6 Diamond ServicesDiamond services have the best protection ability. When there are enough resources in thenetwork, diamond services provide a permanent 1+1 protection. Diamond services are applicableto 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 isalso called a 1+1 service. For a diamond service, there are two different LSPs available betweenthe source node and the sink node. The two LSPs should be as separate as possible. One is theworking LSP and the other is the protection LSP. The same service is transmitted to the workingLSP and the protection LSP at the same time. If the working LSP is normal, the sink node receivesthe 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

AB

C

D

E

F

GH

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 thesource node and the sink node.

Protection and restoration l If the resources are sufficient, two LSPs are always availablefor a permanent 1+1 diamond service. One is the active LSPand the other is the standby LSP.

l If the resources are not sufficient, one LSP can still bereserved for a permanent 1+1 diamond service to ensure theservice 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, andScheduled revertive.l After the automatically revertive diamond service is rerouted,

the service is automatically reverted to the original path if thefault in the original path is rectified.

l After the scheduled revertive diamond service is rerouted, theuser can set the service to be reverted to the original path ata 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, theservice is not reverted to the original route after the fault isrectified.

Preset restoring trail Supports setting the preset restoring trail.

Service migration l Supports migration between diamond services and permanentSNCP connections.

l Supports migration between diamond services and goldservices.

l Supports migration between diamond services and silverservices.

l Supports migration between diamond services and copperservices.

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 triggerrerouting

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

Requirements for creation Sufficient non-protection resources are available between thesource 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 thestandby LSP for transmission. Rerouting is not triggered.

l When both the active and the standby LSPs fail, rerouting istriggered to create a new LSP to restore services.



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, andScheduled revertive.l After the automatically revertive diamond service is rerouted,


l After the scheduled revertive diamond service is rerouted, theuser can set the service to be reverted to the original path ata 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, theservice is not reverted to the original route after the fault isrectified.



1-19

Attribute Rerouting 1+1 Diamond Service












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

Attribute Non-rerouting 1+1 diamond service

Requirements for creation Sufficient non-protection resources are available between thesource node and the sink node

Protection and restoration l When the active LSP fails, services are switched to thestandby 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 isnot triggered.










Issue 02 (2010-09-24)

Attribute Non-rerouting 1+1 diamond service


1.2.7 Gold ServicesGold services are applicable to voice and significant data services. Compared with diamondservices, 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 ASONtriggers 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

AB

C

D

E

F

GH

MSP

MSP

MSPI

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 areavailable between the source node and the sink node.



1-21


Multiplex sectionprotection

l Supports using the working resources of a 1:1 linear multiplexsection protection chain to create gold services.

l Supports using the working resources of a 1+1 linearmultiplex section protection chain to create gold services.

l Supports using the working resources of a 1:N linearmultiplex section protection chain to create gold services.

l Supports using the working resources of a two-fiberbidirectional multiplex section protection ring to create goldservices.

l Supports using the working resources of a four-fiberbidirectional multiplex section protection ring to create goldservices.

Protection and restoration When a fiber is cut for the first time, MS switching is performedto protect services. When MS switching fails, rerouting is thentriggered to restore services.



l Supports setting the revertive mode.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, andScheduled revertive.l After the automatically revertive gold service is rerouted, the

service is automatically reverted to the original path if thefault in the original path is rectified.

l After the scheduled revertive gold service is rerouted, the usercan set the service to be reverted to the original path at aspecific future time (ranging from 10 minutes to 30 days) onthe NMS if the fault in the original path is rectified.

l After the non-revertive gold service is rerouted, the serviceis not reverted to the original route after the fault is rectified.




Issue 02 (2010-09-24)


Service migration l Supports migration between permanent connections and goldservices.

l Supports migration between gold services and diamondservices.

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

services.



ASON server trail Supports gold ASON server trails.



1.2.8 Silver ServicesSilver services, the revertive time is hundreds of milliseconds to several seconds. The silver levelservice is suitable for those data or internet services that have low real-time requirement.

Silver services are also called rerouting services. When an LSP failure, the ASON triggersrerouting to restore the service. If there are not enough resources, service may be interrupted.

As shown in Figure 1-8, 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-8 A silver service

: ASON NE

: User equipment

R1

R2

R3

R4

A

BC

D

E

F

GH

IELSP after rerouting

Original LSP



1-23

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 newLSP to restore services.



l Supports setting the revertive mode.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 status.

Revertive Supports Automatically Revertive, Non-Revertive, andScheduled revertive.l After the automatically revertive silver service is rerouted,


l After the scheduled revertive silver service is rerouted, theuser can set the service to be reverted to the original path ata specific future time (ranging from 10 minutes to 30 days)on the NMS if the fault in the original path is rectified.

l After the non-revertive silver service is rerouted, the serviceis not reverted to the original route after the fault is rectified.


Shared mesh restorationtrail

Supports setting the shared mesh restoration trial for revertivesilver trials.



Issue 02 (2010-09-24)

Attribute Silver Services

Service migration l Supports migration between permanent connections andsilver services.


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

services.

Service optimization l Supports service optimization.l If a revertive silver service reroutes, it cannot be optimized

before reverting to its original route.

Service association Supports service association.

ASON server trail Supports silver ASON server trails.



1.2.9 Copper ServicesThe copper services are seldom used. Generally, temporary services, such as the abrupt servicesin holidays, are configured as copper services.

Copper services are also called non-protection services. If an LSP fails, services do not rerouteand 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 services and traditionalservices.

l Supports migration between copper services and diamondservices.

l Supports migration between copper services and goldservices.

l Supports migration between copper services and silverservices.


Service association Supports service association.



1-25

Attribute Silver Service

ASON server trail Supports ASON server trails.

1.2.10 Iron ServicesThe iron services are also seldom used. Generally, temporary services are configured as ironservices. For example, when service volume soars, during holidays, the services can beconfigured as iron services to fully use the bandwidth resources.

An iron service is also called a preemptable service. Iron services apply non-protection resourcesor protection resources of the TE link to create LSPs. When an LSP fails, services are interruptedand rerouting is not triggered.l When the iron service uses the protection resources of the TE link, if the MS switching

occurs, the iron service is preempted and the service is interrupted. After the MS isrecovered, the iron service is restored. The interruption, preemption and restoration of theiron service are all reported to the U2000.

l When the iron service uses the non-protection resources, if the network resources areinsufficient, the iron service may be preempted by the rerouted silver service or diamondservice. Thus, the service is interrupted.

Table 1-9 lists the attributes of iron service.

Table 1-9 Attributes of iron services

Attribute Iron Service

Requirementsfor creation

Sufficient protection resources or non-protection resources are availablebetween the source node and the sink node.

Multiplexsectionprotection

To create iron services, the following resources can be used:l Protection resources of 1:1 linear MSPl Protection resources of 1:N linear MSPl Protection resources of two-fiber bidirectional MSPl Protection resources of four-fiber bidirectional MSP

Servicerestoration

Does not support rerouting.

Servicemigration

Supports migration between iron services and extra permanentconnections.

Serviceoptimization

Supports service optimization.



Issue 02 (2010-09-24)

1.2.11 OVPNThe optical virtual private network (OVPN) divides the TE links in an ASON network todifferent customers. Sharing the fiber resources, the customers, however, can use and manageonly their own TE links and ASON services.

As shown in Figure 1-9, certain timeslot resources are separately allocated to OVPN customers1 and 2. The network management (NM) users of OVPN customers 1 and 2 are separately createdon the U2000. Then, OVPN customers 1 and 2 can log in to the U2000 through their respectiveclients and NM users. OVPN customers 1 and 2 can separately manage and maintain theirtimeslot resources and ASON services.

Multiple NM users can be created for one OVPN customer. One NM user can manage multipleOVPN customers.

Figure 1-9 Networking diagram of an OVPN

Server

Client

OVPNCustomer 1

Client

OVPNCustomer 2

：Timeslot resouce of OVPN customer 1

：Timeslot resouce of OVPN customer 2

Client

NM User Admin

Enabling the OVPN FunctionTo perform the OVPN function, you must ensure that all the ASON NEs in the ASON domainenable the OVPN function. In addition, the OVPN License can be started on the NMS side.



1-27

NOTE

Only administrator user of the U2000 can enable or disable the OVPN of an NE.

OVPN Customer

After you can create a customer with an OVPN ID, in the subsequent resource allocation, youcan allocate the timeslots of links to the customer, binding the resources with the customer. Thiscustomer is also named OVPN customer. The links that are allocated to the OVPN customer isconsidered as constraints when you create a service. In this way, the service passes only the linksthat are allocated to the OVPN customer. Currently, a maximum of 60,000 OVPN customerscan be created on the U2000.

Allocating the OVPN

The allocation of OVPN resources refers to allocating the TE links to different OVPN customers.After being allocated, the TE links are classified as the follows: shared resources and OVPNcustomer resources. See Figure 1-10.

Figure 1-10 Allocating TE links

VC4timeslot.

.

.

.

.

.

.

.

.

.

SharedResource

OVPNCustomerResource

TE链路

VC4timeslot

NOTE

To allocate the TE links on the MSP ring for OVPN customers, ensure that the timeslots are consistentwith each other in each segment.

OVPN NM User

On an OVPN network, an OVPN user manages OVPN customer resources and services. Afterallocating links to OVPN customers, the pipe provider needs to create NM users the OVPNcustomers and allocate the corresponding rights to the NM users. Each NM user represents thecorresponding OVPN customer. An OVPN customer logs into the NM and manages its ownOVPN network by using the corresponding NM user name and password.

Considering the security of an OVPN network, you need to allocate appropriate rights to OVPNNM users as required.



Issue 02 (2010-09-24)

OVPN ServicesTable 1-10 lists the OVPN service attributes.

Table 1-10 OVPN service attributes

Attribute OVPN Service

Creating a service l When creating a service, the NM user admin can use the sharedresources and OVPN user resources. Each OVPN service can use onlythe timeslot resources of the same color.

l An OVPN customer can create a service on the resources onlyallocated to the OVPN customer.

Rerouting When the OVPN service is rerouted, it can use the resources allocated tothe OVPN customer first. If the OVPN customer resources are notavailable, the OVPN service can use the shared resources.

Presetting therestoration trail

A restoration trail can be preset. An OVPN customer can use the allocatedresources only.

Shared Meshrestoration trail

A shared Mesh restoration trail can be preset. An OVPN customer canuse the allocated resources only.

Service switching OVPN services and traditional services can be mutually switched fromeach 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.

Serviceoptimization

An ASON service of an OVPN user can be optimized on the resourcesonly allocated to the OVPN customer.

1.2.12 UNI ServicesA UNI service is an ASON service that is created automatically after the customer equipmentinitiates a request to the ASON equipment and the signaling is received. UNI services can beclassified into Ethernet UNI services and SDH UNI services.

Ethernet UNI ServicesEthernet UNI services are created in the ASON network after the customer equipment initiatesa service request to the ASON network by transmitting GMPLS signalling. Ethernet UNIservices are used to transmit GE signals, as shown in Figure 1-11. The service requests areclassified into OIF UNI service requests and GMPLS UNI service requests.

In the case of OIF UNI service requests, the message contains the information such as sourceTNA address, sink TNA address, logical port number, service rate, and service level. In theASON network, a node first translates the source and sink TNA addresses into the source andsink node IDs. Then, the node computes multiple service paths according to the service rate.Finally, the node creates the relevant server-layer path according to the service level.



1-29

In the case of GMPLS UNI service requests, the message contains the information such as sourceIP address, sink IP address, service rate, service priority, and access policy. In the ASONnetwork, a node first translates the source and sink IP addresses into the node IDs of the twoaccess nodes in the transport network. Then, the node computes multiple server-layer pathsaccording to the service rate. Finally, the node creates the relevant server-layer path accordingto the service level.

Ethernet UNI services are available at four types: diamond, gold, silver, and copper.

Figure 1-11 Ethernet UNI services

R1 R2

: ASON NE

: Customer equipment

ASON

Ethernet UNIservice

GE Interface

Ethernetboard

GE

GE Interface

SDH UNI Services

SDH UNI services are created in the ASON network after the customer equipment initiates aservice request to the ASON network by transmitting GMPLS signalling. SDH UNI servicesare used to transmit POS signals (including SDH concatenation signals), as shown in Figure1-12. The service requests are classified into OIF UNI service requests and GMPLS UNI servicerequests.

In the case of OIF UNI service requests, the message contains the information such as sourceTNA address, sink TNA address, logical port number, service rate, and service level. In theASON network, a node first translates the source and sink TNA addresses into the source andsink node IDs. Then, the node computes multiple server-layer (concatenation) service pathsaccording to the service rate. Finally, the node creates the relevant server-layer service accordingto the service level.

In the case of GMPLS UNI service requests, the message contains the information such as sourceIP address, sink IP address, service rate, service priority, and access policy. In the ASONnetwork, a node first translates the source and sink IP addresses into the node IDs of the twoaccess nodes in the transport network. Then, the node computes multiple server-layer



Issue 02 (2010-09-24)

(concatenation) service paths according to the service rate. Finally, the node creates the relevantserver-layer service according to the service level.

SDH UNI services are available at four types: diamond, gold, silver, and copper.

Figure 1-12 SDH UNI services

R1 R2

: ASON NE

: Customer equipment

ASON

SDH UNIService

SDH Interface

Opticalinterfaceboard

SDH Interface

1.3 Creating an ASON TopologyThe ASON network uses the route protocol to create the topology information of the nodes inthe network so that each node can obtain a networkwide topology. The U2000 can discover otherASON NEs in the network from any ASON NE.

ContextNOTE

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 theU2000 may be inconsistent with the data on the NE. In this case, perform NE data synchronization tomaintain data consistency.

1.3.1 Creating NEs in BatchesWhen the U2000 communicates properly with a GNE, you can search for all NEs thatcommunicate with the GNE by using the IP address of the GNE or the network segment to whichthe IP address is associated, or by using the NSAP address of the NE. Then, you can create NEsin batches. This method is quicker and more accurate than manual creation.

1.3.2 Creating a Single NE



1-31

The U2000 to manage the NE. Although creating a single NE is not as fast and exact as creatingNEs in batches, you can use this method regardless of whether the data is configured on the NEor not.

1.3.3 Setting the Node IDThe node ID, NE ID and IP address of the NE are independent from each other. In an ASONnetwork, each ASON NE is assigned with a unique node ID within a network. The node ID mustbe specified during the network planning.

1.3.4 Enabling the ASON FeatureThe NE obtains the ASON feature after this feature is enabled. The ASON feature is disabledby default during delivery.

1.3.5 Uploading NE Configuration DataAfter the ASON software of an NE is enabled, the ASON NE automatically generates data onthe NE. Considering that the data dynamically changes as the system runs, you can upload datato the U2000 to ensure that the data on the U2000 is consistent with that on the NE. Do not usethe U2000 to initialize the ASON NE or download data to the ASON NE.

1.3.6 Enable the ASON Feature of a BoardIn the case of an ASON NE, the ASON feature of the optical interface board of the STM-1 orSTM-4 level is disabled by default. The boards of the two levels cannot be used to create anASON service. To create an ASON service by using the boards of the two levels, you need toenable the ASON features of the boards. The ASON feature of the optical interface board of theSTM-16 or STM-64 level, however, is enabled by default. You can also disable the ASONfeatures of the boards of the two levels as required.

1.3.7 Creating Domains for an ASON NetworkThe U2000 manages an ASON network based on ASON domains. Usually, ASON domains areautomatically created. If for some reason, there are NEs that fail to be synchronized to the ASONdomain during the NE upload, you can create an ASON domain and assign the ASON NEs thatbelong to the same ASON network to the ASON domain.

1.3.8 Synchronizing ASON NEsBy communicating with the primary NE, the U2000 is kept synchronous with an ASON networkand automatically discovers other ASON NEs in the network.

1.3.9 Automatically Creating Fibers According to TE LinkAn ASON network can automatically discover TE links. The U2000 can create fibers betweenNEs according to the TE links.

1.3.10 Setting the Primary NE or Secondary NEIn an ASON network, each ASON NE is capable of obtaining the networkwide topologyinformation. The primary NE is the ASON NE that represents the ASON to communicate withthe U2000. It obtains the information of the ASON control plane and reports ASON events tothe 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 ECCbandwidth.

1.3.11 Setting Control Plane ParametersYou can set the control plane parameters of an ASON NE. The parameters contain the bandwidthload, bandwidth weight, distance weight, and hop weight.

1.3.12 Viewing ASON NE Software Version



Issue 02 (2010-09-24)

Different ASON software versions provide different functions. By viewing the version of theASON software running on an NE, you can know the ASON feature of the NE. This help youto configure, manage, maintain and troubleshoot the ASON NE.

1.3.1 Creating NEs in BatchesWhen the U2000 communicates properly with a GNE, you can search for all NEs thatcommunicate with the GNE by using the IP address of the GNE or the network segment to whichthe IP address is associated, or by using the NSAP address of the NE. Then, you can create NEsin batches. This method is quicker and more accurate than manual creation.

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

NOTEYou can repeat Steps a through b to add more search domains. You can delete the system defaultsearch 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 networkbroadcast storm. Therefore, by using the IP Address Range of GNE method, only the NEsin the same network segment can be searched out.

l To search the network segments across routers, the IP Address of GNE method isrecommended. Through a gateway NE, you can search out the NEs in the network segmentof the gateway NE.

Step 4 Optional: If you fail to enter a network segment correctly, enable IP auto discovery and enterthe User Name and Password of the NEs.



1-33

NOTE

After enabling IP auto discovery, you can obtain the IP address of the GNE and search out all the NEsrelated to the GNE.

If the U2000 and an gateway NE are connected through a router, you need to create an NE by using the IPaddress 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.

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 afterthe NEs are created.

NOTE

You can select all options in the Search for NE area to search for NEs, create NEs, and upload the NEdata 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 dialogbox is displayed. Enter User Name and Password in the Create dialog box, and then clickOK.

Step 8 Optional: Click Change NE ID. Then, the Change NE ID dialog box is displayed. Users cancheck against the Bar Code List by the value of Bar Code, and then modify the NE Name,Extend NE ID, Base NE ID, and IP Address fields accordingly.

NOTE

The Bar Code List is provided by the hardware installation personnel to the software commissioning personnel.The list contains the bar codes of stations.

----End



Issue 02 (2010-09-24)

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 NEThe U2000 to manage the NE. Although creating a single NE is not as fast and exact as creatingNEs in batches, you can use this method regardless of whether the data is configured on the NEor not.

Prerequisite

You must be an NM user with "NE operator" authority or higher.

The license must be installed and the license must support creating the NE of the type.

The NE Explorer instance of the NEs must be created.

Background Information

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 isabnormal, the NE is displayed in gray color.

Procedure

Step 1 Choose File > Create > NE from the main 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.

Step 5 Choose Gateway Type, Protocol and set the IP address and NSAP address.

1. Select Gateway from the Gateway Type drop-down list.

2. Select the Protocol type.

If the U2000communicates withNEs through

Do...

IP protocol Select IP from the Protocol drop-down list. Enter the IPAddress and use the default value for the Port number ofthe GNE.

OSI protocol Select OSI from the Protocol drop-down list. Enter theNSAP Address of the GNE.



1-35

NOTE

The NSAP address is a hexadecimal number that contains a maximum of 20 bytes. Its format is:domain address+08003e+NE ID+NSEL.

The domain address that contains a maximum of 13 bytes is entered by the user. NSEL is the portnumber of the network-level protocol, with a fixed value of 1d (one byte).

Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NEis associated to from the Affiliated Gateway drop-down list.

Step 7 Enter the NE User and Password.

NOTEThe default NE user is root, and the default password is password.

Step 8 Optional: If you do not want to apply the NE configuration data in the U2000 to the NE, checkthe NE Preconfiguration check box, and set NE Software Version.

NOTEIf you apply the configuration data of the preconfigured NE to the actual NE when the configuration dataon the preconfigured NE is inconsistent with that on the actual NE, the actual services will be affected.

Step 9 Click OK. Then, click in the blank space of the Main Topology and the NE icon appears in theposition where you clicked.

----End

ResultAfter an NE is successfully created, the system automatically saves the information, such as theIP address, NSAP address, subnet mask, and NE ID to the U2000 database.

PostrequisiteAfter 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 ofcommunication 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 Setting the Node IDThe node ID, NE ID and IP address of the NE are independent from each other. In an ASONnetwork, each ASON NE is assigned with a unique node ID within a network. The node ID mustbe specified during the network planning.

Prerequisitel You must be an NM user with "NE maintainer" authority or higher.l No ASON services exist on the NE.

Background InformationThe node ID must meet the following requirements:l Node IDs cannot be duplicate in the same ASON domain.



Issue 02 (2010-09-24)

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.

CAUTIONWhen a delivered network is running, do not change the node ID. To change the node ID, contactHuawei Technologies Co., Ltd.

Procedure

Step 1 In the NE Explorer, select an NE and choose ASON > ASON Feature Management from theFunction 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 theoperation was successful.

NOTE

You can also set the NE node ID in ASON Topology Management.

----End

1.3.4 Enabling the ASON FeatureThe NE obtains the ASON feature after this feature is enabled. The ASON feature is disabledby default during delivery.

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

Background Informationl 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 segmentas the IP address of the corresponding NE. The format of a node ID is the same as that ofan IP address. The node ID cannot be 0.0.0.0, 1.2.3.4 or 255.255.255.255. Properly set theNE node ID before you enable the ASON feature of the NE.



1-37

l The ASON feature can be enabled after the equipment commissioning is complete.l Add the correct logical boards on the NE before enabling the ASON features.l Set the correct DCC working mode for the NE before enabling the ASON features.l After you enable the ASON feature, upload the NE data to keep the consistency of data

between the U2000 and the NE. For relevant operations, refer to 1.3.5 Uploading NEConfiguration 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 ASONservice residual

l The fiber between the local NE and the adjacent node must not carry ASON services.

l The ASON Clock is disabled for the NE.

Procedure

Step 1 In the NE Explorer, select an NE and choose ASON > ASON Feature Management from theFunction 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 theoperation was successful.

After you disable the ASON feature, upload the NE data to keep the consistency of data betweenthe U2000 and the NE. For relevant operations, refer to 1.3.5 Uploading NE ConfigurationData.

----End

1.3.5 Uploading NE Configuration DataAfter the ASON software of an NE is enabled, the ASON NE automatically generates data onthe NE. Considering that the data dynamically changes as the system runs, you can upload datato the U2000 to ensure that the data on the U2000 is consistent with that on the NE. Do not usethe U2000 to initialize the ASON NE or download data to the ASON NE.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The NE must be created successfully.



Issue 02 (2010-09-24)

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.6 Enable the ASON Feature of a BoardIn the case of an ASON NE, the ASON feature of the optical interface board of the STM-1 orSTM-4 level is disabled by default. The boards of the two levels cannot be used to create anASON service. To create an ASON service by using the boards of the two levels, you need toenable the ASON features of the boards. The ASON feature of the optical interface board of theSTM-16 or STM-64 level, however, is enabled by default. You can also disable the ASONfeatures of the boards of the two levels as required.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON feature of the NEs is enabled.

Procedure

Step 1 In the NE Explorer, select an NE and choose ASON > ASON Feature Management from theFunction Tree. Click the Board ASON Feature Management tab.

Step 2 Click Query to view the current ASON Feature status of the board.

Step 3 Select the port at which the ASON feature is to be disabled. Double-click the Status columnand choose Disabled from the drop-down list.

NOTE

If you need to disable the ASON feature of a board, choose Disable.

Step 4 Click Apply. The Operation Result dialog box is displayed indicating the operation result.

Step 5 Click Close.

NOTE

If the Operation Result dialog box is displayed indicating that the operation fails. You can click Detail toview failure causes.

----End

1.3.7 Creating Domains for an ASON NetworkThe U2000 manages an ASON network based on ASON domains. Usually, ASON domains areautomatically created. If for some reason, there are NEs that fail to be synchronized to the ASONdomain during the NE upload, you can create an ASON domain and assign the ASON NEs thatbelong to the same ASON network to the ASON domain.



1-39

Prerequisitel You must be an NM user with "NE maintainer" authority or higher.

l The ASON NE must be configured and does not belong to any domain.

Background Informationl 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 > SDH ASON > ASON Topology Management from the main menu.

Step 2 ASON NEs that do not belong to any domain are displayed under root of the Object Tree. Right-click an NE and choose Create Domain.

Step 3 In the Domain Attributes dialog box, enter the Current Name and select the Primary NE.

Step 4 Click OK. The domain is successfully created.

----End

1.3.8 Synchronizing ASON NEsBy communicating with the primary NE, the U2000 is kept synchronous with an ASON networkand automatically discovers other ASON NEs in the network.

Prerequisitel You must be an NM user with "NE operator" authority or higher.

l The primary NE must exist.

Background Informationl 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.



Issue 02 (2010-09-24)

l If the node ID of an NE is modified manually, you need to re-synchronize the ASONnetwork topology on the U2000.

Procedure

Step 1 Choose Configuration > SDH ASON > ASON Topology Management from the main menu.Click the ASON NE tab.

Step 2 Select a domain in the Object Tree and all ASON NEs in the domain are shown in the list.

Step 3 Click Synchronize NE. The U2000 searches for the NEs in the ASON domain.If an ASON NE that is not created on U2000 is detected, add it to the NE to Be Created tab.

Step 4 If you want to create a detected NE on the U2000, click in the Creation Flag field. Enter theuser name and password.

NOTE

l If the U2000 uses the same user name and password to log in to all ASON NEs in the domain, checkthe Use the same password networkwide check box, and enter the user name and password.

l If you want to upload the NE data after creating the NE, check the Upload after created check box.

Step 5 Click Apply. The Operation Result dialog box is displayed. Click Close. The Confirm dialogbox is displayed.

Step 6 Click OK. A progress bar is displayed, showing the uploading progress.

----End

1.3.9 Automatically Creating Fibers According to TE LinkAn ASON network can automatically discover TE links. The U2000 can create fibers betweenNEs according to the TE links.

Prerequisitel You must be an NM user with "NE maintainer" authority or higher.l The ASON network is running normally.

Procedure

Step 1 Choose Configuration > SDH ASON > TE Link Management from the main menu.

Step 2 The list shows all links on the U2000. View Component information of each link.

Step 3 Select a TE link for the fiber you want to create. Click Maintenance and choose CreateFiber. Click Close in the Operation Result dialog box.



1-41

NOTE

The fibers created according to TE links are the fibers between NEs. After the fiber(s) is/are createdsuccessfully, view them on the Main Topology.

----End

1.3.10 Setting the Primary NE or Secondary NEIn an ASON network, each ASON NE is capable of obtaining the networkwide topologyinformation. The primary NE is the ASON NE that represents the ASON to communicate withthe U2000. It obtains the information of the ASON control plane and reports ASON events tothe 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 ECCbandwidth.

Prerequisitel You must be an NM user with "NE maintainer" authority or higher.

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 calledthe communication NE. It is the NE that represents the ASON network to communicate withthe U2000. Usually, the communication NE is the primary NE. When the primary NE fails, thesecondary NE becomes the communication NE. If both the primary and secondary NEs fail, thesystem automatically selects an ASON NE as the communication NE. You can set only oneprimary NE and one secondary NE in an ASON domain.

Procedure


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 Click Apply to apply the settings.

----End

1.3.11 Setting Control Plane ParametersYou can set the control plane parameters of an ASON NE. The parameters contain the bandwidthload, bandwidth weight, distance weight, and hop weight.



Issue 02 (2010-09-24)

Prerequisitel You must be an NM user with "NE maintainer" authority or higher.l The ASON NE must be created and configured.

Procedurel For an ASON NE whose ASON version is 5.51.05.10 or 5.99.2.10:

1. In the NE Explorer, select an NE and choose ASON > Control Plane Parametersfrom the Function Tree.

2. Click Query to query the route computation policy from the NE.3. Set the Route Computation Policy field and complete the rest information.

NOTE

l The route computation policy has the following parameters: Bandwidth Load, BandwidthWeight, Distance Weight, Hop Weight.

l It is recommended to keep the default settings. The default settings are as follows:bandwidth load: 0. Bandwidth weight: 50. Distance weight: 50. Hop weight: 0.

4. Click Apply to completed the setting.l For an ASON NE whose ASON version is earlier than 5.99.2.10:

1. In the NE Explorer, select an NE and choose ASON > Control Plane Parametersfrom the Function Tree. Click the Protocol Parameters tab.

2. Click Query to query the protocol parameters from the NE.3. Double-click Revertive Rerouting Reversion Time(s) and enter the time as required.

Default value: 600. Value range: 600 to 65535.4. Click Apply.5. Click the Route Calculate Strategy tab.6. Click Query to query the route calculation strategy from the NE.7. Set a value in the Route Calculate Strategy field. Complete the other information.

NOTE

l The route computation policy has the following parameters: Bandwidth Load, BandwidthWeight, Distance Weight, Hop Weight.

l It is recommended to keep the default settings. The default settings are as follows:bandwidth load: 0. Bandwidth weight: 50. Distance weight: 50. Hop weight: 0.

8. Click Apply to completed the setting..l For an ASON NE whose ASON version is later than 5.99.2.10:

1. In the NE Explorer, select an NE and choose ASON > Control Plane Parametersfrom the Function Tree.

2. Click Query to query the parameters from the NE.3. Double-click Rerouting Delay(ms) and enter the time as required.

Value range: 50 to 600000.4. Click Apply.5. Click the Route Calculate Strategy tab.6. Click Query to query the route calculation strategy from the NE.



1-43

7. Click Route Strategy and choose a mode from the drop-down list.

NOTE

The route computation policy has the following parameters: Bandwidth Load, BandwidthWeight, Distance Weight, Hop Weight.

The five modes of route strategy are as follows:

l Load Balancing Mode: Bandwidth Load: 0. Bandwidth Weight: 50. Distance Weight: 0.Hop Weight: 0.

l Shortest Distance Mode: Bandwidth Load: 0. Bandwidth Weight: 0. Distance Weight: 50.Hop Weight: 0.

l Minimum Hop Count Mode: Bandwidth Load: 0. Bandwidth Weight: 0. Distance Weight:0. Hop Weight: 50.

l Integrated Constraint Mode: Bandwidth Load: 0. Bandwidth Weight: 50. Distance Weight:50. Hop Weight: 0.

l Custom Mode: you set the parameter of route strategy as you need.

It is recommended that you keep the default settings. The default settings are as follows:bandwidth load: 0. Bandwidth weight: 50. Distance weight: 50. Hop weight: 0.

8. Click Apply to completed the setting..

----End

1.3.12 Viewing ASON NE Software VersionDifferent ASON software versions provide different functions. By viewing the version of theASON software running on an NE, you can know the ASON feature of the NE. This help youto configure, manage, maintain and troubleshoot the ASON NE.

Prerequisitel You must be an NM user with "NE monitor" authority or higher.

l This function applies to ASON NEs.

Procedure


Step 2 Select the desired domain in the Object Tree and click . All ASON NEs in the domainare displayed in the list.

Step 3 View the ASON NE software version in the Version.For example, 5.99.7.1.

----End

1.4 Managing the ASON ProtocolAfter 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 facilitatethe management of ASON link resources and ASON services.



Issue 02 (2010-09-24)

Precautions

CAUTIONl 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, orwhen a higher security is required.

1.4.1 Modifying the LMP Discovery TypeThere are two types of LMP discovery. One is by using the J0 byte (default). The other one isby using the D4-D12 bytes. When a REG NE is between two ASON NEs, you need to modifythe LMP discovery type for the corresponding boards of the two ASON NEs. That is, use D4-D12 bytes.

1.4.2 Querying the LMP Discovery TypeYou can query the overhead bytes that are used by the LMP for the system to automaticallydiscover TE links. Currently only the D4-D12 bytes are used. They are used for thecommunication between NEs.

1.4.3 Disabling the LMP ProtocolUsually it is not allowed to disable the LMP except in the following two cases. One is when anASON NE is connected with a traditional NE that is incapable of transparent transmission. Theother one is when an ASON NE has an optical interface that does not connect any fiber. In thesetwo cases, you can disable the LMP to release idle resources for a better resource allocation.

1.4.4 Disabling the OSPF ProtocolUsually it is not allowed to disable the OSPF protocol except in the following two cases. Oneis when an ASON NE is connected with a traditional NE that is incapable of transparenttransmission. The other one is when an ASON NE has an optical interface that does not connectany fiber. In the two cases, you can disable OSPF to release idle resources for a better resourceallocation.

1.4.5 Encrypting the OSPF ProtocolYou can query and set the OSPF protocol authentication and encrypt the OSPF protocol to ensurethe security of the ASON network.

1.4.6 Setting the OSPF TE Link Flood ThresholdThe TE link flood threshold defines the frequency of the flood on the TE link. After the networkfault is cleared, the TE link data changes for times as the NE data upload or synchronization isperformed. When the change times reaches the threshold, the flood takes place on the TE link.

1.4.7 Encrypting RSVPTo ensure the security of the ASON network, you can encrypt the Resource Reservation Protocol(RSVP). The encryption operation needs to be performed for two neighboring NEs. Twoneighboring NEs can implement protocol interworking only if the two NEs have the sameauthentication type and authentication key.

1.4.8 Creating Out-Fiber Control ChannelsThe out-fiber control channel realizes the interconnection between two ASON domains. Youcan use an Ethernet cable to connect two edge NEs of two ASON domains, and then manuallycreate an out-fiber control channel on the U2000. In this way, the communication between thetwo ASON domains is realized at the control plane.



1-45

1.4.1 Modifying the LMP Discovery TypeThere are two types of LMP discovery. One is by using the J0 byte (default). The other one isby using the D4-D12 bytes. When a REG NE is between two ASON NEs, you need to modifythe LMP discovery type for the corresponding boards of the two ASON NEs. That is, use D4-D12 bytes.


Service RequirementsIf the service requirement is shown in Figure 1-13, where NE1-NE4 are ASON NEs and NE5is a REG NE, you need to modify the LMP discovery type for the boards of NE3 and NE4.

Figure 1-13 LMP discovery mode

: ASON NE

:REGl NE

NE1

NE2 NE3

NE4

NE5

Board ConfigurationFigure 1-14 shows how the boards are configured for the case of the previously illustrated servicerequirements.



Issue 02 (2010-09-24)

Figure 1-14 Board configuration of NE3 and NE4

Procedure

Step 1 In the NE Explorer, click the NE and choose ASON > Link Management Protocol from theFunction Tree. Click LMP Auto Discovery Type tab.

Step 2 Click Query to query the LMP automatic discovery type.

Step 3 Double-click Configuration Mode to set the LMP automatic discovery type.For example, set the discovery type of 11-N2SL64 on both NE3 and NE4 to DCC.

Step 4 Click Apply. Click Close in the Operation Result dialog box.

Step 5 Choose Configuration > SDH ASON > Control Link Management from the main menu.

Step 6 Click Synchronize. Check whether the control links between NEs are normal.


Step 8 Click Synchronize. Check whether the TE links between NEs are normal.

----End

1.4.2 Querying the LMP Discovery TypeYou can query the overhead bytes that are used by the LMP for the system to automaticallydiscover TE links. Currently only the D4-D12 bytes are used. They are used for thecommunication between NEs.




1-47

ProcedureStep 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.3 Disabling the LMP ProtocolUsually it is not allowed to disable the LMP except in the following two cases. One is when anASON NE is connected with a traditional NE that is incapable of transparent transmission. Theother one is when an ASON NE has an optical interface that does not connect any fiber. In thesetwo cases, you can disable the LMP to release idle resources for a better resource allocation.

PrerequisiteYou must be an NM user with "NE operator" authority or higher.


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

Procedurel For NG SDH and OCS series equipments.

1. In the NE Explorer, select an NE and choose ASON > Advanced Maintenance fromthe Function Tree.

2. Click the ASON Protocol Management tab. Click Query to query the ASONprotocol information from the NE.

3. Select the port at which the LMP is to be disabled. Double-click the LMP ProtocolStatus column and choose Disabled from the drop-down list.

NOTE

If you need to enable the LMP, choose Enabled.

4. Click Apply. A confirm dialog box is displayed.5. Click Yes. The operation result dialog box is displayed, click Close.6. Click Query. Query LMP protocol status from the NE.

l For OptiX OSN 9560.1. In the NE Explorer, select an NE and choose ASON > Advanced Maintenance from

the Function Tree.2. Click the LMP Protocol Status tab. Click Query to query the ASON protocol

information from the NE3. 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.



Issue 02 (2010-09-24)

NOTE

If you need to enable the LMP, choose Enabled.

4. Click Apply. A confirm dialog box is displayed.

5. Click Yes. The operation result dialog box is displayed, click Close.

6. Click Query. Query LMP protocol status from the NE.

----End

1.4.4 Disabling the OSPF ProtocolUsually it is not allowed to disable the OSPF protocol except in the following two cases. Oneis when an ASON NE is connected with a traditional NE that is incapable of transparenttransmission. The other one is when an ASON NE has an optical interface that does not connectany fiber. In the two cases, you can disable OSPF to release idle resources for a better resourceallocation.



WARNINGIf the OSPF protocol is disabled, the ASON feature of the corresponding optical interface isdisabled, which severely affects ASON services. Hence, do not disable the OSPF protocol if notnecessary.

Procedure

Step 1 In the NE Explorer, select an NE and choose ASON > Advanced Maintenance from theFunction Tree.

Step 2 Click the ASON Protocol Management tab. Click Query to query the ASON protocolinformation from the NE.

Step 3 Select the port at which the OSPF protocol is to be disabled. Double-click the OSPF ProtocolStatus column. Choose Disabled from the drop-down list.

NOTE

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

Step 4 Click Apply. A confirm dialog box is displayed.

Step 5 Click Yes. The operation result dialog box is displayed, click Close.

Step 6 Click Query. Queries OSPF protocol status from the NE.

----End



1-49

1.4.5 Encrypting the OSPF ProtocolYou can query and set the OSPF protocol authentication and encrypt the OSPF protocol to ensurethe security of the ASON network.


Background InformationThe 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 theFunction 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 TextPassword Authentication and MD5 Encryption Authentication.

l When the value is Plain Text Password Authentication, the authentication is performed based on thespecified password. In this case, the Authentication Key must be a string of a maximum of eightcharacters.

l When the value is MD5 Encryption Authentication, the authentication is performed based on thepassword obtained by using the MD5 encryption algorithm. In this case, the Authentication Key mustbe a non-empty string of a maximum of 64 characters.

Step 5 Click Apply. A confirm dialog box is displayed.

Step 6 Click OK.

----End

1.4.6 Setting the OSPF TE Link Flood ThresholdThe TE link flood threshold defines the frequency of the flood on the TE link. After the networkfault is cleared, the TE link data changes for times as the NE data upload or synchronization isperformed. When the change times reaches the threshold, the flood takes place on the TE link.


Background Informationl You need to set a proper flood threshold. If the value is too low, network congestions may

happen. If the value is too high, the network data may not be synchronous.l It is recommended that you use the default value of the U2000. By default, the threshold

value is 100, and the hold-off time is 3s.



Issue 02 (2010-09-24)

Procedure


Step 2 Click the OSPF TE Link Flood Threshold tab to set the parameters.

Step 3 Click Query.

Step 4 For a TE link, double-click Trigger Condition, Threshold and Delay Time(s) to set theirrespective values. Click Apply.

----End

1.4.7 Encrypting RSVPTo ensure the security of the ASON network, you can encrypt the Resource Reservation Protocol(RSVP). The encryption operation needs to be performed for two neighboring NEs. Twoneighboring NEs can implement protocol interworking only if the two NEs have the sameauthentication type and authentication key.


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



1-51

NOTE

l The following three options are available for Authentication Mode: Plain Text PasswordAuthentication and MD5 Encryption Authentication.

l When the value is Plain Text Password Authentication, the authentication is performed based on thespecified password. In this case, the Authentication Key must be a string of a maximum of eightcharacters.

l When the value is MD5 Encryption Authentication, the authentication is performed based on thepassword obtained by using the MD5 encryption algorithm. In this case, the Authentication Key mustbe a non-empty string of a maximum of 64 characters.

Step 5 Click Apply.NOTE

After the RSVP authentication is successfully created. You can double-click the Authentication Mode columnand change the authentication type. Click Apply. The dialog box displayed, prompt the service survivabilitymay be affected, click Yes to apply the change.

----End

1.4.8 Creating Out-Fiber Control ChannelsThe out-fiber control channel realizes the interconnection between two ASON domains. Youcan use an Ethernet cable to connect two edge NEs of two ASON domains, and then manuallycreate an out-fiber control channel on the U2000. In this way, the communication between thetwo ASON domains is realized at the control plane.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON network is running normally.

Service RequirementsYou can create an out-fiber control channel as shown in Figure 1-15. In this example, NE3 inthe ASON001 domain and NE6 in the ASON002 domain are connected by an Ethernet line.NE3 and NE6 are connected to NE9 through fibers.

Figure 1-15 Creating out-fiber control channels

: ASON NE

: Fiber: Ethernet link

NE1

NE2 NE3

NE4 NE5

NE6 NE7

NE8

ASON001 ASON002NE9

: Traditional NE



Issue 02 (2010-09-24)

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 theFunction Tree.

Step 2 Click the LMP Control Channel tab. Click Query to query control channels of the linkmanagement protocol from the NE.

Step 3 Click New and the Create Control Channel dialog box is displayed. Enter a value in the RemoteAddress and Next Hop Address fields respectively.

NOTEThe remote address and the next hop address are the node ID of the remote NE.

l As shown in Figure 1-15, if only one Ethernet link exists between the source and the sink, the twoaddresses 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 nodeID 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 nodeID 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 remoteaddress is the node ID of the sink NE and the next hop address is the IP address of the LAN that connectsto the source NE.

For example, if NE3 is the source, the remote address and the next hop address are the node IDof NE6.

Step 4 Click Apply for the settings to take effect.


Step 6 Click the OSPF IP Address Management tab.

Step 7 Click Query.

Step 8 Find the source or sink NE of the newly created out-fiber control channel. Double-click IP orMask to set the parameters.



1-53

Step 9 Click Apply. Click Close in the Operation Result dialog box.

Step 10 Creating a Virtual TE Link.If NE3 is the source, you need to create the virtual TE link between NE3 and NE6.

----End

1.5 Managing ASON Clock SubnetClock subnet is classified into ASON clock subnet and traditional clock subnet. Beforeconfiguring ASON services, you need to create a clock subnet to ensure that a consistent clocktracing relation is created for all NEs in the ASON network.

Background InformationASON NEs support the traditional clock trace mode and the ASON clock trace mode. In anASON domain, you can set some or all of the ASON NEs to the ASON clock trace mode, toform an ASON clock subnet.

In the ASON clock subnet, each ASON NE automatically traces the best clock source. The clockis then automatically traced and switched, thus avoiding the clock interlocking. This simplifiesthe clock configuration. In an ASON domain with many ASON NEs, several ASON clocksubnets should be created if more than 20 ASON NEs are on the clock tracing link in a clocksubnet. Each ASON clock subnet generates its own clock tracing relation to trace the PRCsinside the subnet. In each ASON clock subnet, change of the PRCs and links does not affect theclock tracing relation in other ASON clock subnets.

Generally, you need to create only one ASON clock subnet in one ASON domain.

1.5.1 Creating an ASON Clock SubnetIn an ASON clock subnet, the clock tracing relation is formed based on the automatic tracingof clocks and thus need not be configured on a per-NE basis.

1.5.2 Converting a Preconfigured ASON Clock Subnet into an ASON Clock SubnetIf the preconfiguration mode is selected during creation of a clock subnet, the clock tracing modein this subnet is traditional and thus requires a manual configuration. You can convert apreconfigured ASON clock subnet into an ASON clock subnet.

1.5.3 Converting a Traditional Clock Subnet into an ASON Clock SubnetIf the clock trace mode of a clock subnet is traditional, you need to manually convert thetraditional clock subnet into an ASON clock subnet.

1.5.4 Managing a Hybrid Network Composed of an ASON Clock Subnet and a Traditional ClockSubnetIn the case of a hybrid network composed of an ASON clock subnet and a traditional clocksubnet, if the SSM mode of the traditional clock subnet changes, you need to adjust the ASONPRC of the ASON clock subnet accordingly.

1.5.5 Setting the Clock Fault Recover TimeWhen a fault occurs, the ASON clock is switched. When the original link is restored, the ASONclock can be used only after the WTR time for a clock upon a fault elapses.

1.5.1 Creating an ASON Clock SubnetIn an ASON clock subnet, the clock tracing relation is formed based on the automatic tracingof clocks and thus need not be configured on a per-NE basis.



Issue 02 (2010-09-24)


RequirementsAs shown in Figure 1-16, NE1 to NE4 are ASON NEs while NE5 and NE6 are traditional NEs.It is required that NE1 to NE4 form an ASON clock subnet. The ASON clock tracing modeneeds to be enabled. NE5 and NE6 provide primary reference clock sources, which contain theclock quality information. Compared with NE5, NE6 is of a higher priority.

In this way, the ASON clock subnet first traces the primary reference clock source of a higherquality. If the primary reference clock source of NE5 and NE6 are of the same quality, the ASONclock subnet traces NE6 as per the priority.

In addition, some changes are made to the fiber between NE2 and NE4. Therefore, services andclocks should not travel through this link.

Figure 1-16 ASON clock subnet

: ASON NE

: Traditional NE

NE1

NE2 NE3

NE4

NE6 NE5

Board ConfigurationFigure 1-17 shows the board configuration of NE1 to NE4. The 12-N1SL16 of NE2 is connectedto NE6 and the 12-N1SL16 of NE3 is connected to NE5.



1-55

Figure 1-17 Board configuration of NE1 to NE4

FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

Planning for the Clock SubnetTable 1-11 provides the clock subnet planning information.

Table 1-11 Board configuration of NE1 to NE4

Attributes Clock Subnet

Clock Subnet ID 1

ASON NE NE1, NE2, NE3 and NE4

SSM mode Standard Clock Mode

Primary reference clocksource

NE2-12-N1SL16-1 (SDH-1) NE3-12-N1SL16-1 (SDH-1)

Priority 1 (high) 2 (low)

Relay No relay

Interface mode NE4 cannot directly trace NE2

NOTEThe clock quality outputted by NE5 and NE6 is G.811.

Procedure

Step 1 Choose Configuration > SDH ASON > ASON Clock Subnet Management from the mainmenu.

Step 2 Click New.



Issue 02 (2010-09-24)

Step 3 Enter the following information in the dialog box:

l Subnet ID: 1

l NE: NE1, NE2, NE3 and NE4

l SSM Mode: Standard Clock Mode

l PRC ID: NE2-12-N1SL16-1 (SDH-1) and NE3-12-N1SL6-1 (SDH-1)

Step 4 Click OK.

Step 5 Click Query in the ASON Clock Subnet Management window.

Step 6 Select PRC Management to query the state of the primary reference clock source.

Step 7 Select Interface Mode Management. Set the interface mode of the NE4-7-N2SL64-1 toDetection of the Clock Quantity Disabled.

Step 8 Open the main topology, click the Current View drop-list, select Clock View.

Step 9 In the Clock View, right-click Search Clock Link to view the clock tracing relation within thesubnet.

----End

1.5.2 Converting a Preconfigured ASON Clock Subnet into anASON Clock Subnet

If the preconfiguration mode is selected during creation of a clock subnet, the clock tracing modein this subnet is traditional and thus requires a manual configuration. You can convert apreconfigured ASON clock subnet into an ASON clock subnet.



1-57


RequirementsAs shown in Figure 1-18, NE1 to NE4 are ASON NEs. These ASON NEs work in the traditionalclock mode. NE1 traces the external 2 Mbit/s clock source. NE2, NE3, and NE4 trace NE1. The2 Mbit/s external clock source of NE1 contains clock quality information. The clock quality isG.811 clock.

The clock mode of NE1 to NE4 need be modified to ASON clock mode. An ASON clock subnetthen need be created and the standard SSM protocol need be enabled. The 2 Mbit/s clock sourceof NE1 is taken as the primary reference clock source for the ASON clock subnet.

Figure 1-18 Traditional Clock Subnet

NE1

NE2

NE3

NE4

2Mbit/s externalclock source

Board ConfigurationFigure 1-19 shows the board configuration of NE1 to NE4.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64



Issue 02 (2010-09-24)

Planning for the Clock SubnetTable 1-12 provides the new clock subnet planning information.

Table 1-12 Planning for the new clock subnet

Attributes Clock Subnet

Clock Subnet ID 2


SSM mode Standard Clock Mode

Primary reference clock source NE1-External Clock1

Priority 1

Relay No relay

Interface mode None

PrecautionsNOTE

The operation of converting a preconfigured ASON clock subnet into an ASON clock subnet is similar tothat of creating an ASON clock subnet. In the former case, however, you need to select a preconfiguredsubnet.

Follow the steps below to modify a traditional clock subnet into an ASON clock subnet.

Procedure

Step 1 Choose Configuration > SDH ASON > ASON Clock Subnet Management from the mainmenu.

Step 2 Click New.

Step 3 Enter the following information in the dialog box:l Subnet ID: 2l NE: NE1, NE2, NE3 and NE4l SSM Mode: Standard Clock Model PRC ID: NE1-External Clock1



1-59

Step 4 Select Preconfigured Subnet and click OK.

Step 5 Click Query.

Step 6 Select PRC Management to query the state of the primary reference clock source.

Step 7 Right-click Clock Subnet1 from the Subnet Management Tree. Select Migrate to ASON ClockSubnet.

Step 8 A dialog box is displayed. Click Yes.

Step 9 A prompt is displayed indicating that the operation is successful. Click Close.

Step 10 Open the main topology, click the Current View drop-list, select Clock View.

Step 11 In the Clock View, right-click Search Clock Link to view the clock tracing relation within thesubnet.

----End



Issue 02 (2010-09-24)

1.5.3 Converting a Traditional Clock Subnet into an ASON ClockSubnet

If the clock trace mode of a clock subnet is traditional, you need to manually convert thetraditional clock subnet into an ASON clock subnet.


RequirementsAs shown in Figure 1-20, NE1, NE2, NE3, and NE4 are ASON NEs that work in the traditionalclock trace mode, and NE5 and NE6 are traditional NEs. It is required that NE1 to NE4 form anASON clock subnet. The ASON clock tracing mode needs to be enabled. NE5 and NE6 provideprimary reference clock sources, which contain the clock quality information. Compared withNE5, NE6 is of a higher priority.

In this way, the ASON clock subnet first traces the primary reference clock source of a higherquality. If the primary reference clock source of NE5 and NE6 are of the same quality, the ASONclock subnet traces NE6 as per the priority.

Figure 1-20 ASON clock subnet

: ASON NE

: Traditional NE

NE1

NE2 NE3

NE4

NE6 NE5

Board ConfigurationFigure 1-21 shows the board configuration of NE1 to NE4. The 12-N1SL16 of NE2 is connectedto NE6 and the 12-N1SL16 of NE3 is connected to NE5.



1-61


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

Clock Subnet Planning

Table 1-13 shows the planning of a new clock subnet.

Table 1-13 Board configuration of NE1 to NE4

Attribute Clock Subnet

Clock Subnet ID 1


SSM Mode Standard clock mode

PRC NE2-12-N1SL16-1 (SDH-1) NE3-12-N1SL16-1 (SDH-1)

PRC Priority 1 (high) 2 (low)

Relay No relay

Interface Mode Automatic detection of the clock quantity

NOTEThe clock quality outputted by NE5 and NE6 is G.811.

Follow a different procedure according to the scenario.

Procedurel Scenario 1: The ASON NEs work in the traditional clock trace mode and Stop SSM

Mode is enabled.



Issue 02 (2010-09-24)

1. Choose Configuration > SDH ASON > ASON Clock Subnet Management fromthe main menu.

2. Click New.3. Enter the following information in the dialog box:

– Subnet ID: 1– NE: NE1, NE2, NE3 and NE4– SSM Mode: Standard Clock Mode– PRC ID: NE2-12-N1SL16-1 (SDH-1) and NE3-12-N1SL6-1 (SDH-1)

4. Click OK.5. Click Query in the ASON Clock Subnet Management window.6. Click the PRC Management tab and query the PRC status.7. Click New. In the Add PRC window, select the desired Output PRC or Input

PRC according to the priority.8. Click OK and navigate to the PRC Management window. Click Apply.9. Select a PRC and right-click PRC Level to set the PRC quality.

For example, select NE2 as the PRC and set the quality to G.811 Clock Signal.10. Click OK in the prompt.11. Click Close in the operation result dialog box.12. Click Apply.

13. Select a PRC and click or to set the priority.For example, set the priority of NE2-12-N1SL16-1(SDH-1) to 1 and the priority ofNE3-12-N1SL6-1(SDH-1) to 2.

14. Click Apply.15. Select Interface Mode Management and click Query. Then, set all the interface

modes to Automatic Detection of the Clock Quantity.



1-63

16. Open the main topology, click the Current View drop-list, select Clock View.17. In the Clock View, right-click Search Clock Link to view the clock tracing relation

within the subnet.l Scenario 2: The ASON NEs work in the traditional clock trace mode and Standard SSM

Mode is enabled.1. Create an ASON clock subnet. For details, refer to Steps 1 through 5 in scenario 1.2. Configure the PRC priority. For details, refer to Steps 6, 13, and 14 in scenario 1.3. Query the networkwide clock synchronization status. For details, refer to Steps 16

through 17 in scenario 1.l Scenario 3: The ASON NEs work in the traditional clock trace mode and Extended SSM

Mode is enabled.1. Open the main topology, click the Current View drop-list, select Clock View.2. In the Clock View, right-click an NE and choose Configure Clock from the shortcut

menu.For example, select NE2 and NE3 to set the clock quality.

3. Choose Configuration > Clock > Clock Subnet Configuration in the NE explorer.4. Click Start Standard SSM Protocol.5. Click Apply.

The standard SSM protocol must be started for all ASON NEs in the clock subnet.6. Create an ASON clock subnet. For details, refer to Steps 1 through 5 in scenario 1.7. Configure the PRC priority. For details, refer to Steps 6, 13, and 14 in scenario 1.8. Query the networkwide clock synchronization status. For details, refer to Steps 16

through 17 in scenario 1.

----End

1.5.4 Managing a Hybrid Network Composed of an ASON ClockSubnet and a Traditional Clock Subnet

In the case of a hybrid network composed of an ASON clock subnet and a traditional clocksubnet, if the SSM mode of the traditional clock subnet changes, you need to adjust the ASONPRC of the ASON clock subnet accordingly.

Configuration RequirementsAs shown in Figure 1-22, NE1, NE2, NE3, and NE4 are ASON NEs that work in the ASONclock trace mode, and NE5 and NE6 are traditional NEs that work in the traditional clock tracemode. The clock subnet of the ASON NEs is an ASON clock subnet. NE2 and NE3 providePRCs but NE2 has a higher priority. The clock subnet of the traditional NEs is a traditional clocksubnet. NE5 and NE6 provide PRCs but NE6 has a higher priority. In addition, the line clocksources provided by NE5 and NE6 contain the clock quality information.



Issue 02 (2010-09-24)

Figure 1-22 Hybrid network composed of an ASON clock subnet and a traditional clock subnet

: ASON NE

: Traditional NE

NE1

NE2 NE3

NE4

NE6 NE5

Board ConfigurationFigure 1-23 shows the board configuration of NE1, NE2, NE3 and NE4. 12-N1SL16 of NE2connects to NE6, and 12-N1SL16 of NE3 connects to NE5.

Figure 1-23 Board configuration of NE1, NE2, NE3 and NE4

FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

Clock Subnet PlanningTable 1-14 shows the planning of a new clock subnet.



1-65

Table 1-14 Clock subnet planning

Attribute Clock Subnet

Clock Subnet ID 1


SSM Mode Standard clock mode

PRC NE2-12-N1SL16-1(SDH-1) NE3-12-N1SL16-1(SDH-1)

PRC Priority 1 (high) 2 (low)

Relay No relay

Interface Mode Automatic detection of the clock quality

Follow a different procedure according to the scenario.

Procedurel Scenario 1: The Stop SSM Mode is enabled in the traditional clock subnet.

1. Choose Configuration > SDH ASON > ASON Clock Subnet Management fromthe main menu.

2. In the Object Tree, select ASON Clock Subnet > Clock Subnet1.3. Click the PRC Management tab and query the PRC status.4. Click New. In the Add PRC window, select the desired Output PRC or Input

PRC according to the priority.For example, select NE2 and NE3 as PRCs, and set the priority of NE2 to 1 and thepriority of NE3 to 2.

5. Click OK and navigate to the PRC Management window. Click Apply.6. Select a PRC and right-click PRC Level to set the PRC quality.

For example, select NE2 as the PRC and set the quality to G.811 Clock Signal.7. Click OK in the prompt.8. Click Close in the operation result dialog box.9. Click Apply.

10. Select a PRC and click or to set the priority.For example, set the priority of NE2-12-N1SL16-1(SDH-1) to 1 and the priority ofNE3-12-N1SL6-1(SDH-1) to 2.

11. Click Apply.12. Open the main topology, click the Current View drop-list, select Clock View.13. In the Clock View, right-click Search Clock Link to view the clock tracing relation

within the subnet.l Scenario 2: The Standard SSM Mode is enabled in the traditional clock subnet.

1. Set the PRC. For details, refer to Steps 1 through 5 in scenario 1.2. Configure the PRC priority. For details, refer to Steps 10 through 11 in scenario 1.



Issue 02 (2010-09-24)

3. Query the networkwide clock synchronization status. For details, refer to Steps 12through 13 in scenario 1.

l Scenario 3: The Extended SSM Mode is enabled in the traditional clock subnet.1. Open the main topology, click the Current View drop-list, select Clock View.2. In the Clock View, right-click an NE and choose Configure Clock from the shortcut

menu.For example, select NE5 and NE6 to set the clock quality.

3. Choose Configuration > Clock > Clock Subnet Configuration in the NE explorer.4. Click Start Standard SSM Protocol.5. Click Apply.6. Set the PRC. For details, refer to Steps 1 through 5 in scenario 1.7. Configure the PRC priority. For details, refer to Steps 10 through 11 in scenario 1.8. Query the networkwide clock synchronization status. For details, refer to Steps 12

through 13 in scenario 1.

----End

1.5.5 Setting the Clock Fault Recover TimeWhen a fault occurs, the ASON clock is switched. When the original link is restored, the ASONclock can be used only after the WTR time for a clock upon a fault elapses.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON clock subnet must be created.

ProcedureStep 1 Choose Configuration > SDH ASON > ASON Clock Subnet Management from the main

menu.

Step 2 In Subnet Management Tree, select the required ASON clock subnet.

Step 3 Click the Subnet Attribute tab and click Query.

Step 4 Select the required NE, double-click the Clock Fault Recover Time field, and enter a value forthe WTR time.

NOTE

The WTR time for a clock upon a fault can be set to 60 to 900 seconds. The default value is 60 seconds.

Step 5 Click Apply.

----End

1.6 Managing Link ResourcesASON is capable of automatically switching optical network connections under the control ofthe signaling network. It dynamically allocates network resources as required. As the networkis growing larger, a more reasonable way of resource management is required to make the mostof the network resources and to improve the network efficiency. Link resource management is



1-67

one aspect of resource management. In an actual network, thousands of connections may existbetween 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 areregarded as a whole, which is known as the traffic engineer link (TE link), serving as theprocessing object of the route information.

1.6.1 Synchronizing Control Links NetworkwideBy synchronizing the control links, the control link data on the U2000 is kept consistent withthat on the NEs of the ASON network.

1.6.2 Synchronizing TE LinksYou can synchronize the TE links. The U2000 queries link resources in the network by theprimary NE to keep the TE link data on the U2000 consistent with the ASON data.

1.6.3 Viewing TE LinksYou can view the ASON TE link information on the U2000. This helps you to configure ormaintain TE links.

1.6.4 Configuring the Link DistanceYou can set the link distance on the U2000 for route calculation. If you want to use the physicaldistance between NEs as one element for the route calculation, you need to set the TE linkdistance according to the actual physical distance.

1.6.5 Setting the Custom Cost of the TE LinkYou can set the custom cost of the TE link on the U2000 for route calculation. You must set thecustom cost and custom cost weight at the same time to enable the parameters.

1.6.6 Setting the Usage Threshold of Fiber ResourcesThe usage threshold of the fiber resources can be set according to the requirements of thecustomer. When the fiber resource occupancy exceeds the usage threshold, the system reportsthe CP_TELINK_EXHAUST alarm.

1.6.7 Creating an SRLGFibers 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 sameshared risk link group (SRLG). Therefore, you need to set the same SRLG value for TE linksthat share the same risks in the network.

1.6.8 Querying VC4 Timeslot Occupation StatusWhen you query the VC4 timeslot occupation status, you can query the following status of theVC4 slot: timeslot occupation status, reservation status, and MSP switching status. Based on thespecific VC4 timeslot status, you can set reserved timeslots for an NE.

1.6.9 Querying the Information About the Timeslots on the Link SectionsThe TE link that is configured with MSP is divided into several sections. The sections of the TElink can be of the working, protection, non-protection attribute, or virtual link. You can queryProtection, Switching Status, Total Timeslots, Timeslots Available for ASON, and IdleTimeslots for each link section.

1.6.10 Setting Resource ReservationYou can configure the board ports and timeslots that are reserved for the permanent connectionson an ASON NE. Both ASON trails and permanent connections can be created in an ASONnetwork. Link resource reservation means that some timeslots of a link are reserved for thecreation of permanent connections. The reserved timeslots cannot be used when ASON trailsare created and or rerouted.

1.6.11 Creating a Virtual Interfaces



Issue 02 (2010-09-24)

You can partition a interface into several virtual interface with different rate by U2000, then youcan create TE link on the virtual interface.

1.6.12 Creating a Virtual TE LinkWithout a TE link, ASON services cannot be created between a traditional NE and an ASONNE. A virtual TE link, however, uses traditional resources to realize the creation and protectionfor ASON services between traditional NEs and ASON NEs. You can directly create ASONservices on TE links.

1.6.13 Creating a TE Link Based on Virtual InterfacesThis topic describes how to create a traffic engineering (TE) link based on virtual interfaces.When the port rates on the source and the sink are different, you can create a TE link based onvirtual interfaces. Such TE links are available for creating services.

1.6.14 Deleting an Interrupted TE Link ManuallyWhen a TE link is interrupted, the TE link is saved on the U2000 and the link status isInterrupted. This facilitates fault locating. You can also manually delete the interrupted link.

1.6.1 Synchronizing Control Links NetworkwideBy synchronizing the control links, the control link data on the U2000 is kept consistent withthat on the NEs of the ASON network.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON network must be running properly.

Procedure


Step 2 Click Synchronize. In the Synchronize dialog box displayed, choose Domain.

Step 3 Click Synchronize.

NOTE

After the synchronization is complete, all the information about the control links are displayed in the list.

----End

1.6.2 Synchronizing TE LinksYou can synchronize the TE links. The U2000 queries link resources in the network by theprimary NE to keep the TE link data on the U2000 consistent with the ASON data.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON network is running normally.

Background InformationIn current ASON software versions, one TE link contains only one component link. In this sense,to synchronize a TE link is the same as to synchronize a component link.



1-69

Procedure




NOTE

After the synchronization is complete, all the information about the TE links is displayed in the list.

----End

1.6.3 Viewing TE LinksYou can view the ASON TE link information on the U2000. This helps you to configure ormaintain TE links.


l The ASON network is running normally.

Procedure


Step 2 The list shows all links 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 3 Select a TE link. The component links of the TE link are displayed in the following table.

Step 4 Select one or more TE links. The total bandwidth utilization is displayed in the left side of thebutton bar in the middle of the window.

Step 5 Optional: Select the desired bandwidth unit from the Bandwidth Units drop-down list, forexample, VC4. The list is automatically refreshed and displays the link information accordingto the selected bandwidth unit.

NOTE

According to some standards, the bandwidth unit of TE links is kbit/s. On the U2000 you can choose adifferent bandwidth unit to cater for the requirements for the SDH transmission.

Step 6 Optional: Click Filter, in the Filter dialog box displayed, select the Domain, Source NE, SinkNE and OVPN Customer, and click Filter. The qualified links are shown in the list.

Step 7 Optional: Click Print to export the list to Internet Explorer for printing.

Step 8 Optional: Click Save As. Enter the start line number, end line number and the file name. ClickOK to save the list to a file.

----End



Issue 02 (2010-09-24)

1.6.4 Configuring the Link DistanceYou can set the link distance on the U2000 for route calculation. If you want to use the physicaldistance between NEs as one element for the route calculation, you need to set the TE linkdistance according to the actual physical distance.


l TE link management is based on correct link information.

Procedure




NOTE


Step 4 Select a link, double-click the Distance(km) field, and enter a value.


----End

1.6.5 Setting the Custom Cost of the TE LinkYou can set the custom cost of the TE link on the U2000 for route calculation. You must set thecustom cost and custom cost weight at the same time to enable the parameters.


l TE link management is based on correct link information.

l The ASON NE of the GCP V100R007C02 version or a later version.

Procedure

Step 1 Click Synchronize. In the Synchronize dialog box displayed, choose Domain and PayloadType.


NOTE


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



1-71

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.6.6 Setting the Usage Threshold of Fiber ResourcesThe usage threshold of the fiber resources can be set according to the requirements of thecustomer. When the fiber resource occupancy exceeds the usage threshold, the system reportsthe CP_TELINK_EXHAUST alarm.

Prerequisitel You must be an NM user with "NE operator" authority or higher.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 shortcutmenu.

Step 2 Choose ASON > Optical Fiber Resource Threshold Management from the Function Tree.

Step 3 Select the fiber. Click the Resource Threshold column and enter the planned resource usagethreshold.

NOTE

The default value of Resource Threshold is 75.

Step 4 Click Apply to validate the settings.

----End

1.6.7 Creating an SRLGFibers 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 sameshared risk link group (SRLG). Therefore, you need to set the same SRLG value for TE linksthat share the same risks in the network.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The TE link data must be configured on the U2000.

Service RequirementSee Figure 1-24. All NEs are ASON NEs. NE4 and NE5 are in the same equipment room. Thefiber between NE1 and NE4, and the fiber between NE1 and NE5 are within the same cable. Inthis situation, the TE links of the two fibers share the same risk.



Issue 02 (2010-09-24)

Figure 1-24 SRLG schematic diagram

NE1

NE2 NE3

NE4

NE5

Two fibers in one cable

Procedure


Step 2 Select the TE links. Double-click the SRLG field and enter a value. In this example, the samefield value should be applied to the SRLG of the TE link between NE1 and NE4 and the one ofthe 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 SRLGvalue.

----End

1.6.8 Querying VC4 Timeslot Occupation StatusWhen you query the VC4 timeslot occupation status, you can query the following status of theVC4 slot: timeslot occupation status, reservation status, and MSP switching status. Based on thespecific VC4 timeslot status, you can set reserved timeslots for an NE.


Procedure

Step 1 To query the VC4 timeslot occupation status at the network layer, perform the followingoperations:1. Choose Configuration > SDH ASON > Component Link Management from the main

menu.2. Click Synchronize. In the list displayed, you can view the information of all component

links of the U2000.3. Select a link from the list, right-click and choose Query VC4 Timeslot Occupation

Status. The VC4 Timeslot Occupation Status dialog box is displayed.



1-73

4. Click Source Timeslot Status or Sink Timeslot Status. Click Query.5. Click Cancel.

Step 2 Optional: To query the VC4 timeslot occupation status on a per-NE basis, perform the followingoperations:1. In the NE Explorer, select a board that belongs to an ASON NE and choose ASON > VC4

Timeslot Occupation Status from the Function Tree.2. Click Query.

----End

1.6.9 Querying the Information About the Timeslots on the LinkSections

The TE link that is configured with MSP is divided into several sections. The sections of the TElink can be of the working, protection, non-protection attribute, or virtual link. You can queryProtection, Switching Status, Total Timeslots, Timeslots Available for ASON, and IdleTimeslots for each link section.

Prerequisitel You must be an NM user with "NE monitor" authority or higher..l The ASON feature must be enabled.

Procedure

Step 1 Choose Configuration > SDH ASON > Component Link Management from the main menu.

Step 2 In the SDH Component Link Management window, click Synchronize.

Step 3 Select the member link to be queried. Right-click and choose Query Link TimeslotSegmentation from the shortcut menu.

Step 4 In the Query Link Timeslot Segmentation window, click Query. The information aboutProtection, Switching Status, Total Timeslots, Timeslots Available for ASON, and IdleTimeslots is displayed.

----End



Issue 02 (2010-09-24)

1.6.10 Setting Resource ReservationYou can configure the board ports and timeslots that are reserved for the permanent connectionson an ASON NE. Both ASON trails and permanent connections can be created in an ASONnetwork. Link resource reservation means that some timeslots of a link are reserved for thecreation of permanent connections. The reserved timeslots cannot be used when ASON trailsare created and or rerouted.


Service RequirementSee Figure 1-25. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.There are services running on NE1, NE2, NE3 and NE4. According to the planning, two monthslater, four unprotected traditional services will be created between NE5 and NE6. These servicesare required to pass NE3 and NE4. In this case, you need to reserve for the planned servicessome timeslots between NE3 and NE4 to prevent the timeslots from being occupied by reroutedASON services.

Figure 1-25 Reserved link resources

: ASON NE

: Traditional NE

NE1

NE2 NE3

NE4

NE5

NE6

Board ConfigurationTo meet the previously mentioned service requirements, you can configure the boards as shownin Figure 1-26. The 11-N2SL64 of NE3 and 8-N2SL64 of NE4 are connected by fibers.



1-75

Figure 1-26 Board configurations on NE3 and NE4

Procedure

Step 1 To reserve link resources at the network layer, perform the following operations:1. Choose Configuration > SDH ASON > Component Link Management from the main

menu.2. Click Synchronize. The list displays all component links on the U2000. You can view the

information of each component link.3. Set the filter criteria as required. Click Filter.4. Select a link in the list, right-click it and choose Set Resource Reservation from the

shortcut menu. The Set Resource Reservation dialog box is displayed.For example, select a component link.l Source NE: NE3l Source Port: 11-N2SL64-1(SDH-1)l Sink NE: NE4l Sink Port: 8-N2SL64-1(SDH-1)Right-click the component link and choose Set Resource Reservation from the shortcutmenu.

5. Set timeslots in Resource Reservation. Click Apply.For example, click timeslots 33-36 to reserve the four timeslots.

NOTE

If you want to cancel the resource reservation settings, click the reserved timeslot(s) that areconfigured.

6. Click Close in the Operation Result dialog box.7. Click Cancel in the Set Resource Reservation dialog box . The link resources are reserved.



Issue 02 (2010-09-24)

Step 2 Optional: To reserve link resources on a per-NE basis, perform the following operations:1. In the NE Explorer, select a board of an ASON NE and choose ASON > Resource

Reservation Management from the Function Tree.2. Click Query to query the resource reservation status of the board from the NE.3. Select the VC4 channel to be reserved and set the reservation status to Yes.

For example, set the reservation status of the channels from NE3-11-N2SL64-1(SDH-1)-VC4:33 to NE3-11-N2SL64-1(SDH-1)-VC4:36 to Yes.

4. Click Apply and a dialog box is displayed telling that the settings are applied.5. In the opposite station, repeat step a to step d to reserve link resources.

----End

1.6.11 Creating a Virtual InterfacesYou can partition a interface into several virtual interface with different rate by U2000, then youcan create TE link on the virtual interface.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l There is no TE link in the port.l The LMP protocol on the port is disabled.

Procedure

Step 1 Disable the LMP protocol.1. In the NE Explorer of NE1, select an NE and choose ASON > Advanced Maintenance

from the Function Tree.2. Click the ASON Protocol Management tab. Click Query to query the ASON protocol

information from the NE.3. Select the port at which the LMP is to be disabled, e.g. 5-N1SL4-1(SDH-1). Double-click

the LMP Protocol Status column and choose Disabled from the drop-down list.

NOTE

If you need to enable the LMP protocol, choose Enabled.

4. Click Apply. A confirmation dialog box is displayed.5. Click Yes. The operation result dialog box is displayed. Click Close.6. Click Query to query the LMP protocol status from the NE.7. Follow the preceding steps to disable the LMP protocol on the port 12-N2SL16-1(SDH-1)

of NE4.

Step 2 Create the virtual interface.1. In the NE Explorer of NE1, select a board of an ASON NE and choose ASON > ASON

Link Virtual Interface Management from the Function Tree.2. Select the TE link whose source is NE1-5-N1SL4-1(SDH-1) and click Create Virtual

Interface. The Create Virtual Interface dialog box is displayed.

3. Select timeslot 1-4, click , and then click OK.



1-77

CAUTIONThe timeslot sequence in the Selected Timeslots must map with the timeslot sequence ofthe remote virtual interface.

4. In the operation result dialog box, click Close.5. Click Query, view the information of the virtual interface.

----End

1.6.12 Creating a Virtual TE LinkWithout a TE link, ASON services cannot be created between a traditional NE and an ASONNE. A virtual TE link, however, uses traditional resources to realize the creation and protectionfor ASON services between traditional NEs and ASON NEs. You can directly create ASONservices on TE links.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l There must be at least two configured ASON NEs.

Service RequirementSee Figure 1-27. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 is a traditional NE. In thisscenario, a TE link can be created between NE3 and NE4. With the TE link, an ASON servicecan be rerouted to the NE3-NE5-NE4 route.

Figure 1-27 Virtual TE link

: ASON NE

: Traditional NE

Virtual TE link

NE1

NE2 NE3

NE4

NE5

Board ConfigurationTo meet the previously mentioned service requirements, you can configure the boards on NE3and NE4 as shown in Figure 1-28, and configure the boards on NE5 as shown in Figure 1-29.



Issue 02 (2010-09-24)

The 12-N1SL16 of NE3 and the 6-N1SL16 of NE5 are connected. The 12-N1SL16 of NE4 andthe 13-N1SL16 of NE5 are connected.

Figure 1-28 Board configuration for NE3 and NE4

Figure 1-29 Board configuration for NE5

NOTEYou need to create 16 VC4 cross-connections between 6-N1SL16 and 13-N1SL16 on NE5 in advance.



1-79


Currently, you can create a TE link by adding a component link. On some occasions, (forexample, when the J0 byte is down), the link management protocol cannot automatically discoverTE links. In this case, you can create a TE link by manually creating a component link.

Procedurel To create a TE link by directly creating a virtual TE link, perform the following operations:

1. Choose Configuration > SDH ASON > TE Link Management from the main menu.

2. Click Synchronize.

3. Click Maintenance and choose Create Virtual TE Link. The Create Virtual TELink dialog box is displayed.

4. Enter the attributes of the TE link.For example, set the source NE to NE3 and the source port to 12-N1SL16-1(SDH-1)(The optical interface must be the one connected to NE5). Set the sink NE to E4, andthe sink port to 12-N1SL16-1(SDH-1) (The optical interface must be the oneconnected to NE5). Set the extended type to ASON Trail Creation.

NOTE

l The extended type has two options: ASON Trail Creation, Fault Detection Only orVirtual Interface.

l When the TE link is used to create a service, select ASON Trail Creation.

l If an MSP spans an ASON network and an SDH network over the boundary between thetwo networks, select Fault Detection Only. If for the second time, the fiber cut happensto a gold service, the virtual TE link is broken and triggers the rerouting.

l When the rate source and sink port is different, select Virtual Interface. The TE link canbe used to create a service.

5. Click OK.

l To create a TE link by creating a component link, perform the following operations:

1. Choose Configuration > SDH ASON > Component Link Management from themain menu.

2. All the component links are displayed in the list. You can view all the informationabout the links.

3. Click Create. The Create Component Link dialog box is displayed.

4. Set or enter a value for each parameter of the link and click OK.

NOTE

After the component link is successfully created, a TE link that corresponds to the componentlink is automatically displayed in the SDH TE Link Management window. If the componentlink is deleted, the corresponding TE link automatically disappears.

----End

1.6.13 Creating a TE Link Based on Virtual InterfacesThis topic describes how to create a traffic engineering (TE) link based on virtual interfaces.When the port rates on the source and the sink are different, you can create a TE link based onvirtual interfaces. Such TE links are available for creating services.



Issue 02 (2010-09-24)


l At least two ASON NEs must be configured.

Service Requirement

As shown in Figure 1-30, NE1 and NE4 are ASON NEs residing in ASON domain A and ASONdomain B respectively. NE2 and NE3 are traditional NEs residing in a traditional synchronousdigital hierarchy (SDH) network or a non-Huawei network. NE2 and NE3 are connected througha subnet, NE1 and NE2 are connected by an STM-4 fiber, and NE3 and NE4 are connected byan STM-16 fiber. It is required that ASON domain A and B be combined and managed as oneASON domain. A virtual TE link between domain A and domain B, however, cannot be directlycreated by using the ports of NE1 and NE4, because the link rates are different. You need tocreate a virtual interface of 4 Mbit/s bandwidth on NE1 and NE4. Based on the virtual interfaces,the TE link can be created successfully. Thus, the ASON domain A and B are combined as aunified ASON domain A. You can manage equipment and services within a unified ASONdomain.

NOTE

If NE2 and NE3 cannot be managed by the U2000, you need to set them as virtual NEs.

Figure 1-30 TE link based on virtual interfaces

STM-4

STM-16: ASON NE

: Traditional NE

NE1

NE3

NE2

: Fiber

: Trail

Virtual TE Link

NE4

Domain A

Domain B

A B A



1-81

Board ConfigurationNE1 and NE4 are OptiX OSN 7500. Figure 1-31 shows the configuration of boards on NE1 andNE4.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S2

9

S30

S31

S32

S34

S36

S35

S2

8

PIU

EOW

S33

PIU

S38

S9

S10

S11

AUX

GS

CC

GSC

C

N2S

L16

T11X

CSA

T11X

CSA

N1S

L4

NE2 and NE3 are abstracted as virtual NEs. Figure 1-32 shows the configuration of boards onNE2 and NE3.

Figure 1-32 Board configuration for virtual NEs

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S19

S20

N1S

L4N

2SL1

6

Service PlanningTable 1-15 shows the planning of the virtual interfaces on NE1 and NE4.

Table 1-15 Virtual interface planning

Attribute NE1 NE4

Board 5-N1SL4 12-N2SL16

Port 1 1

Timeslot 1-4 1-4



Issue 02 (2010-09-24)

Table 1-16 shows the planning of the virtual TE link between NE1 and NE4.

Table 1-16 Virtual TE link planning

Attribute NE1<->NE4

Source NE NE1

Source Port 5-N1SL4-1(SDH-1)

Source Virtual Interface 1-4

Sink NE NE4

Sink Port 12-N2SL16-1(SDH-1)

Sink Virtual Interface 1-4

Extend Type Virtual Interface

Procedure

Step 1 Disable the LMP protocol.1. In the NE Explorer of NE1, select an NE and choose ASON > Advanced Maintenance

from the Function Tree.2. Click the ASON Protocol Management tab. Click Query to query the ASON protocol

information from the NE.3. Select the port at which the LMP is to be disabled, e.g. 5-N1SL4-1(SDH-1). Double-click

the LMP Protocol Status column and choose Disabled from the drop-down list.

NOTE

If you need to enable the LMP protocol, choose Enabled.

4. Click Apply. A confirmation dialog box is displayed.5. Click Yes. The operation result dialog box is displayed. Click Close.6. Click Query to query the LMP protocol status from the NE.7. Follow the preceding steps to disable the LMP protocol on the port 12-N2SL16-1(SDH-1)

of NE4.

Step 2 Create the virtual interface.1. In the NE Explorer of NE1, select a board of an ASON NE and choose ASON > ASON

Link Virtual Interface Management from the Function Tree.2. Select the TE link whose source is NE1-5-N1SL4-1(SDH-1) and click Create Virtual

Interface. The Create Virtual Interface dialog box is displayed.

3. Select timeslot 1-4, click , and then click OK.



1-83

CAUTIONThe timeslot sequence in the Selected Timeslots must map with the timeslot sequence ofthe remote virtual interface.

4. In the operation result dialog box, click Close.

Step 3 Create the virtual TE link.1. Choose Configuration > SDH ASON > TE Link Management from the main menu.2. Click Synchronize.3. Click Maintenance and choose Create Virtual TE Link. The Create Virtual TE Link

dialog box is displayed.4. Enter the attributes of the TE link.

For example, set the source NE to NE1, the source port to 5-N1SL4-1(SDH-1), and thesource virtual interface to 1-4. (The optical interface must be the one connected to NE2).Set the sink NE to E4, the sink port to 12-N1SL16-1(SDH-1), and the source virtualinterface to 1-4. (The optical interface must be the one connected to NE3). Set the extendedtype to Virtual Interface.

5. In the operation result dialog box, click Close.6. Click Synchronize. The virtual TE link is displayed in the link list.

Step 4 Synchronize NEs of an ASON domain from the NMS.1. Choose Configuration > SDH ASON > ASON Topology Management from the main

menu.2. Right-click the ASON domain B on the object tree and choose Delete from the shortcut

menu.3. Select the ASON domain A from the object tree and click Synchronize NE. The NEs that

reside in the ASON domain B are synchronized into the ASON domain A.

----End

1.6.14 Deleting an Interrupted TE Link ManuallyWhen a TE link is interrupted, the TE link is saved on the U2000 and the link status isInterrupted. This facilitates fault locating. You can also manually delete the interrupted link.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The status of a TE link must be Interrupted.

ContextWhen a TE link is interrupted, the TE link is saved on the U2000 and the link status isInterrupted. 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 TElinks relevant to the alarm. Meanwhile, the interrupted TE link is displayed in the TE linkmanagement list.



Issue 02 (2010-09-24)

Procedure


Step 2 In the TE link list, select one or more links whose statuses are Interrupted, right-click, andchoose 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.7 Managing SRGsThe TE links in the same optical cable, NE, site, and pipe have the same risk. You can find abalance point between management costs and risk control, determine the risks to be managed,and manage the risks by means of SRGs.

1.7.1 Creating an SRGThe TE links in the same optical cable, NE, site, and pipe have the same risk. You can create anSRG that associates the physical topology of an ASON network to TE links. In this manner, youcan easily manage risks.

1.7.2 Querying the SRG Related to a TE LinkThe TE links in the same optical cable, NE, site, and pipe have the same risk. SRGs and TE linksare of the many-to-many relationship. That is, an SRG may contain multiple TE links and a TElink may belong to multiple SRGs.

1.7.3 Querying the SRG Related to an ASON NEYou can query an SRG by means of an ASON NE.

1.7.1 Creating an SRGThe TE links in the same optical cable, NE, site, and pipe have the same risk. You can create anSRG that associates the physical topology of an ASON network to TE links. In this manner, youcan easily manage risks.

Prerequisitel You must be an NM user with "NE operator" authority or higher.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 thecontrol plane due to the differences in the planning and construction of sites, optical cables, andpipes. The two links that seem to be irrelevant on the topology may be placed in the same opticalcable or pipe.

Hence, the TE links in the same optical cable, pipe, and NE have the same risk. The risk refersto the probability of a link cut.



1-85

Physical TopologyFigure 1-33 shows the physical topology. NE 1 through NE 3 are ASON NEs. NE 2 and NE 3are located on site B. Fiber 1 and fiber 3 are located in optical cable 1; fiber 2 and fiber 4 arelocated in optical cable 2; fiber 2 and fiber 3 are located in optical cable 3; fiber 3 and fiber 4are located in optical cable 4; optical cable 1 and fiber 2 are located in pipe 1.

Figure 1-33 Schematic diagram of the physical topology of an SRG

Node B

NE2 NE3

: ASON NENE1

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 LinksFigure 1-34 shows the topology of TE links. Link 1 and link 3 are located between NE 1 andNE 2; link 4 is located between NE 1 and NE 3; link 2 is located between NE 2 and NE 3. AllNEs are located in ASON domains.

Figure 1-34 Schematic diagram of the topology of the TE links in an SRG

NE1 NE2

Link 4 Link 2

Link 1

Link 3

NE3



Issue 02 (2010-09-24)

Risk Analysis

The TE links in the same optical cable, NE, site, and pipe have the same risk. Table 1-17 liststhe risk analysis result according to the mapping relationship between the physical topology andthe TE links.

Table 1-17 Risk cause analysis

Risk Cause Member

Pipe 1 is cut. Link 1, link 2, link 3

Optical cable 1 is cut. Link 1, link 3




A power failure occurs in NE 1. Link 1, link 3, link 4

A power failure occurs in NE 2. Link 1, link 2, link 3

A power failure occurs in NE 3. Link 3, link 4

A power failure occurs in site B. Link 1, link 2, link 3, link 4

SRG Planning

A TE link can belong to multiple SRGs (you can set multiple SRG IDs) and an SRG can containmultiple TE links. Table 1-18, Table 1-19, Table 1-20, and Table 1-21 lists the division ofSRGs according to the risk analysis result.

Table 1-18 SRGs for pipes

SRG Name ID Member

SRG_pipe_001 1 Optical cable 1, fiber 2

Table 1-19 SRGs for optical cables

SRG Name ID Member

SRG_cable_001 2 Optical cable 1






1-87

Table 1-20 SRGs for NEs

SRG Name ID Member

SRG_NE_001 6 NE 1

SRG_NE_002 7 NE 2

SRG_NE_003 8 NE 3

Table 1-21 SRGs for sites

SRG Name ID Member

SRG_Station_001 9 NE 2, NE 3

Procedure

Step 1 Choose Configuration > SDH ASON > SRG Management from the main menu.

Step 2 Create an SRG for optical cables.

Step 3 Click Create and the Create SRLG dialog box is displayed.

Step 4 Enter the basic information about the SRG.

Basic information

l Name: SRG_pipe_001l ID: 1l ASON Domain: ASONl Type: pipel Remarks: pipe

Step 5 Add optical cable 1 to the SRG.

1. In the Name text box, enter Optical cable and click . The object whose namebegins with Optical cable is filtered out and displayed in the dialog box.

2. Select Optical Cable 1 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 6 Add fiber 1 to the SRG.

1. In the Name text box, enter Fiber and click . The object whose name beginswith Fiber is filtered out and displayed in the dialog box.

2. Select Fiber 1 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.



Issue 02 (2010-09-24)

Step 7 Click OK.

Step 8 Repeat Steps 1 through 7 to create other SRGs according to the SRG planning.

----End

1.7.2 Querying the SRG Related to a TE LinkThe TE links in the same optical cable, NE, site, and pipe have the same risk. SRGs and TE linksare of the many-to-many relationship. That is, an SRG may contain multiple TE links and a TElink may belong to multiple SRGs.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l You must have the U2000 license that supports the SRG function.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 theshortcut 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.7.3 Querying the SRG Related to an ASON NEYou can query an SRG by means of an ASON NE.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l You must have the U2000 license that supports the SRG function.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 theASON NE tab.

Step 3 Select one or more NEs, right-click, and then choose Query Relevant SRGs from the shortcutmenu.

Step 4 The SRG Management window is displayed showing the SRG related to the selected NE.

----End



1-89

1.8 Creating ASON ServicesThe trail levels that an ASON trail supports are as follows: diamond, gold, silver, copper andiron. 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 anASON trail.


The U2000 provides the end-to-end ASON trail management feature and supports services atfive classes of service (CoS) as follows:

l Diamond service: provides 1+1 protection (for example, SNCP) and rerouting ability.

l Gold service: provides 1:1 protection (for example, MSP) and rerouting ability.

l Silver service: provides rerouting services and re-calculates a route in the real time.

l Copper service: does not provide protection in the case of a fault.

l Iron service: extra services which can be preempted and have no protection.

NOTE

OptiX OSN 3800 and OptiX OSN 6800 support the WDM ASON client trail.

1.8.1 Synchronizing ASON TrailsBy synchronizing the ASON trails, the ASON trail data on the U2000 is kept consistent withthat in the ASON network.

1.8.2 Creating a Diamond ASON ServiceYou can create an ASON trail with the diamond-class protection.

1.8.3 Creating a Gold ASON serviceYou can create an ASON trail with the gold-class protection. When you create a gold service,primarily use the working TE links. If the working TE links are insufficient, you can use theunprotected TE link resources. It is recommended that you ensure that sufficient workingresources are available in the network before you create a gold service.

1.8.4 Creating a Silver ASON ServiceYou can create an ASON trail with the silver-class protection. If a silver ASON trail fails, thererouting is periodically initiated until the trail is successfully rerouted. If the network resourceis insufficient, the service may be interrupted. Since the system calculates the reverting trail fora silver trail in real time, you do not need to reserve resources for it. In this sense, the silverservices have a high bandwidth utilization.

1.8.5 Creating a Copper ASON ServiceYou can create an ASON trail with the copper-class protection. Copper services are not usedoften. Usually they are used to configure temporary services.

1.8.6 Creating an Iron ASON ServiceYou can create an ASON trail with the iron-class protection. When you create an iron service,primarily use the protection resource of a TE link. If the protection resource is insufficient, youcan use the non-protection resource of the TE link. It is recommended that you ensure sufficientprotection resources in the network before creating an iron service.

1.8.7 Creating an ASON Server Trail



Issue 02 (2010-09-24)

An ASON server trail is mainly used to carry lower order services (VC3 or VC12). An ASONserver trail is applicable to diamond, gold, silver, or copper services. At the NE side, an ASONserver trail is also called a tunnel service.

1.8.8 Creating a Segmented ASON Server TrailIn the case of a end-to-end tunnel that traverses multiple nodes, the intermediate nodes cannotadd or drop lower order services through this UNI link. In this case, you can use the sectionedtunnel to ensure that multiple nodes share the tunnel bandwidth.

1.8.9 Creating Two Associated SDH ASON TrailsThe ASON trail association function associates two services so that the two services are notpreempted by each other during the rerouting and optimization.

1.8.10 Setting ASON Trail AssociationASON trail association means two ASON trails are associated. The associated trails are separatedfrom each other during the service optimization and rerouting whenever possible. Serviceassociation is applied to access services that have two access points. After two trails areassociated, if one of the trails (or server trails) is rerouted or optimized, the ASON NE adoptsthe 1+1 routing policy to try to avoid the associated ASON trail (or server trail).

1.8.11 Creating ASON Services in BatchesThe batch creation function is always used if a large number of ASON services need to be created.

1.8.12 Deactivating the SDH ASON TrailDeactivating an SDH ASON trail can release the resources that the trail occupies.

1.8.13 Deleting an ASON TrailThe operation of deleting ASON trails removes the trail data from the U2000 and the NE.

1.8.1 Synchronizing ASON TrailsBy synchronizing the ASON trails, the ASON trail data on the U2000 is kept consistent withthat in the ASON network.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l An ASON trail must be created on the U2000.

Procedure

Step 1 Choose Configuration > SDH 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 thePrompt 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 and Attributes.



1-91

NOTE

l Attributes: basic information, working state, SLA-compliant, rerouting attributes and associated services.

l You can also select one or more ASON trails, right-click and choose Synchronize from the shortcut menuto synchronize the selected ASON trails. At this time, the synchronized attributes for the ASON trails areconsistent with the synchronization attributes that you set in the Synchronize window.


Step 5 In the Browse New/Lost Service on NE dialog box, view the new services and lost services ofthe NE.

Step 6 Click Close.

----End

1.8.2 Creating a Diamond ASON ServiceYou can create an ASON trail with the diamond-class protection.


l The U2000 must have synchronized networkwide TE links and have sufficient TE linkresources.


When you create a diamond service, you need to properly configure the rerouting attributes asrequired. The following descriptions are based on the permanent 1+1 diamond service.

Service Requirement

See Figure 1-35. A permanent 1+1 diamond service at the rate of 155 Mbit/s is required betweenNE1 and NE3. The working LSP is required to pass NE2 and the protection LSP is required topass NE4.

Figure 1-35 Diamond service requirement

Working LSP Protection LSP

NE1

NE2

NE3

NE4

: ASON NE: LSP



Issue 02 (2010-09-24)

Board ConfigurationTo meet the previously mentioned service requirement, you can configure the boards as shownin Figure 1-36.


Service PlanningTo meet the previously mentioned service requirement, you can refer to Table 1-22 to plan thediamond service.

Table 1-22 Diamond service planning

Attribute NE1<->NE3

Source NE NE1

Source board-port 13-SLQ1-1

Source timeslot 1

Sink NE NE3

Sink board-port 13-SLQ1-1

Sink timeslot 1

Protection class Diamond

SNCP Access None



1-93

Attribute NE1<->NE3

Route constraint Working path: NE1-NE2-NE3; protection path: NE1-NE4-NE3

Rerouting attributes Revertive Mode Non-Revertive

Lockout Unlocked

Priority 1

Trigger condition Reroute when one trail fails

CrankBack 1

Policy Use existing trails wheneverpossible

Rerouting Triggered by B3Bit Error

No

Rerouting Hold-off time 0

ProcedureStep 1 Choose Configuration > SDH ASON > ASON Trail Management from the main menu.

Step 2 Choose Create > ASON Trail, and the creation wizard is displayed.

Step 3 In Basic information, enter the basic information of the ASON trail.For example, enter the trail information as follows:l Name: NE1-NE3-ASON-Trail-0001l Type: ASON Traill Class: Diamondl Concatenation Type: Non-Concatenationl OVPN Customer: Share Resource

Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.For example, enter the attributes as follows:l Revetrive Mode: Non-Revetrivel Lockout: Unlockedl Priority: 1l Trigger Condition: Reroute when one trail failsl CrankBack: 1l Policy: Use existing trail whenever possiblel Rerouting Triggered by B3 Bit Error: Nol Rerouting Hold-off time: 0

Step 5 Set the source NE. In the right-hand topology, double-click the sink NE and select a slot, portand timeslot from the dialog box displayed. Click OK.



Issue 02 (2010-09-24)

For example, select the SLQ1 in slot 13, the port 1 and the timeslot 1.

Step 6 Set the sink NE. In the right-hand topology, double-click the sink NE and select a slot, port andtimeslot from the dialog box displayed. Click OK.

Step 7 Optional: Click Pre-Calculate to pre-calculate the route. Click the Pre-Calculate Route tabto view the related route information.

NOTE

If you check the Automatic Pre-Calculate check box, the U2000 issues a command for the NE to performthe automatic pre-calculation. Every change of the route constraints, the source/sink, or the protection typetriggers an automatic pre-calculation.

Step 8 Optional: Set Explicit Node or Explicit Link. Right-click an NE in the right-hand topologyand select an option from the shortcut menu as needed.

NOTE

l If you want to specify the timeslot when setting the explicit link, choose Browse from the shortcutmenu.

l After you select the Set Explicit Link shortcut menu item, its submenu is displayed in a folded mannerif there are more than ten available explicit links.

l To cancel the Explicit Node or Explicit Link, right-click an NE and choose Cancel Explicit Node orCancel Explicit Link.

For example, you can do as follows:l Select the Working option button. Right-click NE2 in the right-hand topology and choose

Set As Explicit Node from the shortcut menu.l Select the Protection option button. Right-click NE4 in the right-hand topology and choose

Set As Explicit Node from the shortcut menu.

Step 9 Optional: Set Excluded Node or Excluded Link. Right-click an NE in the right-hand topologyand select an option from the shortcut menu as needed.

NOTE

If you need to cancel the Excluded Node or Excluded Link, right-click an NE and choose CancelExcluded Node or Cancel Excluded Link from the shortcut menu.

Step 10 Optional: Set the Activate or Duplicate after created check box.



1-95

NOTE

l If you check the Activate check box, a created trail is applied to the NE so that the trail is in the activatedstate.

l If you check the Duplicate after created check box, after a trail is created, you can create multipletrails that share the same source and sink by duplicating the created trail.

Step 11 Verify that the trail information and route restrictions are correctly entered. Click Apply. If thecreation is successful, the system prompts that the operation was successful.

NOTETo change the route restriction, select one or multiple route restrictions from the Route Restriction pane,right-click and choose Delete from the shortcut menu. The selected route constraint is deleted. Repeat Steps8 through 10 to set new route constraints.

Step 12 Click Close. If the system prompts that the route calculation fails, check whether the routeconstraints are proper and whether the link resources are sufficient. Then start the configurationagain from Step 1.

Step 13 Click Cancel to go back to the SDH ASON Trail Management window. You can see thedetailed descriptions of the service.

----End

1.8.3 Creating a Gold ASON serviceYou can create an ASON trail with the gold-class protection. When you create a gold service,primarily use the working TE links. If the working TE links are insufficient, you can use theunprotected TE link resources. It is recommended that you ensure that sufficient workingresources are available in the network before you create a gold service.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The U2000 must have synchronized the links of the entire network and have sufficient link

resources.l All links that the ASON trail passes through are under MSP protection. Otherwise, you

need to create fibers and configure the MSP protection before creating 1:1, 1:N, or 1+1protected ASON trails.

The U2000 supports displaying the valid route of a gold service after multiplex section (MS)switching. The requirements of realizing the function are as follows:l The license for end-to-end must be available.l The gold service must be managed in the end-to-end mode.l The MS protection (MSP) ring on which the gold service runs must be searched out.l When you query the valid route on the U2000 after the MS switching of a gold service

occurs, if the network interface fails to return the route data, the returned data is null, orthe returned route segment does not contain the information of source and sink NEs ofASON route segment, the query of valid route fails. In this case, the actual route of theASON module is displayed.

Service RequirementSee Figure 1-37. Four ASON NEs compose an MSP ring. A gold service at the rate of 155 Mbit/s is required between NE1 and NE3.



Issue 02 (2010-09-24)

Figure 1-37 Gold service requirement

NE1

NE2

NE3

NE4MSP Ring

: ASON NE

Board Configuration

To meet the previously mentioned service requirement, you can configure the boards on the NEsas shown in Figure 1-38.


Service Planning

To meet the service requirement, you can refer to Table 1-23 to plan a gold service.

Table 1-23 Gold service planning

Attribute NE1<->NE3

Source NE NE1



1-97

Attribute NE1<->NE3


Source timeslot 1

Sink NE NE3


Sink timeslot 1

Protection class gold

Route constraint The service route must passNE2.

SNCP Access None

Rerouting attribute Revertive Mode Non-revertive

Lockout Unlocked

Priority 2

CrankBack 1



No



The procedure for creating a gold ASON trail is similar to that described in "Creating a DiamondASON Trail". The difference lies in that the protection type is Gold.

Procedure



Step 3 In Basic information, enter the basic information of the ASON trail.For example, set the attributes as follows:

l Name: NE1-NE3-ASON-Trail-0002

l Type: ASON Trail

l Class: Gold

l Concatenation Type: Non-Concatenation

l OVPN Customer: Share Resource



Issue 02 (2010-09-24)

Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.For example, set the attributes as follows:l Revetrive Mode: Non-Revetrivel Lockout: Unlockedl Priority: 2l CrankBack: 1l Policy: Use existing trail whenever possiblel Rerouting Triggered by B3 Bit Error: Nol Rerouting Hold-off time: 0

Step 5 Set the source NE. In the right-hand topology, double-click the sink NE and select a slot, portand timeslot from the dialog box displayed. Click OK.For example, select the SLQ1 in slot 13, the port 2 and the timeslot 1.



NOTE



NOTE




For example, select Working. Right-click NE2 in the right-hand topology and choose Set AsExplicit Node from the shortcut menu.




1-99

NOTE



NOTE







----End

1.8.4 Creating a Silver ASON ServiceYou can create an ASON trail with the silver-class protection. If a silver ASON trail fails, thererouting is periodically initiated until the trail is successfully rerouted. If the network resourceis insufficient, the service may be interrupted. Since the system calculates the reverting trail fora silver trail in real time, you do not need to reserve resources for it. In this sense, the silverservices have a high bandwidth utilization.


resources.

Service RequirementSee Figure 1-39. The four NEs are all ASON NEs. A silver service at the rate of 155 Mbit/s isrequired between NE1 and NE3.



Issue 02 (2010-09-24)

Figure 1-39 Silver service requirementNE1

NE2

NE3

NE4

：ASON NE： LSP

Board ConfigurationTo meet the previously mentioned service requirement, you can configure the boards on the NEsas shown in Figure 1-40.


Service PlanningTo meet the service requirement, you can refer to Table 1-24 to plan a silver service.

Table 1-24 Silver service planning

Attribute NE1<->NE3

Source NE NE1



1-101

Attribute NE1<->NE3


Source timeslot 1

Sink NE NE3


Sink timeslot 1

Protection class Silver

SNCP Access None


Rerouting attribute Revertive Mode Automatically Revertive

Lockout Unlocked

Priority 2

CrankBack 1



No



The procedure for creating a silver ASON trail is similar to that described in "Creating a DiamondASON Trail". The difference lies in that the protection type is Silver.

Procedure





l Type: ASON Trail

l Class: Silver





Issue 02 (2010-09-24)

Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.For example, set the attributes as follows:l Revetrive Mode: Automatically Revetrivel WTR Time(s): 600l Lockout: Unlockedl Priority: 2l CrankBack: 1l Policy: Use existing trail whenever possiblel Rerouting Triggered by B3 Bit Errorl Rerouting Hold-off time: 0




NOTE



NOTE




For example, select Working. Right-click NE2 in the right-hand topology and choose Set AsExplicit Node from the shortcut menu.




1-103

NOTE


Step 10 Optional: Set the Activate or Duplicate after created check box.NOTE







----End

1.8.5 Creating a Copper ASON ServiceYou can create an ASON trail with the copper-class protection. Copper services are not usedoften. Usually they are used to configure temporary services.


resources.

Service RequirementSee Figure 1-41. The four NEs are all ASON NEs. A copper service at the rate of 155 Mbit/sis required between NE1 and NE3.

Figure 1-41 Copper service requirementNE1

NE2

NE3

NE4

：ASON NE： LSP



Issue 02 (2010-09-24)



Service PlanningTo meet the service requirement, you can refer to Table 1-25 to plan a copper service.

Table 1-25 Copper service planning

Attribute NE1<->NE3

Source NE NE1


Source timeslot 1

Sink NE NE3


Sink timeslot 1

Protection class Copper




1-105

Background InformationThe procedure for creating a copper ASON trail is similar to that described in "Creating aDiamond ASON Trail". The difference lies in that the protection type is Copper.

Procedure



Step 3 In Basic information, enter the basic information of the ASON trail.For example, set the attributes as follows:l Name: NE1-NE3-ASON-Trail-0004l Type: ASON Traill Class: Copperl Concatenation Type: Non-Concatenation

Step 4 Set the source NE. In the right-hand topology, double-click the sink NE and select a slot, portand timeslot from the dialog box displayed. Click OK.For example, select the SLQ1 in slot 13, the port 4, and the timeslot 1.



NOTE



NOTE




For example, select the Working option button. Right-click NE2 in the right-hand topology andchoose Set As Explicit Node from the shortcut menu.




Issue 02 (2010-09-24)

NOTE


Step 9 Optional: Set the Activate or Duplicate after created check box.NOTE







----End

1.8.6 Creating an Iron ASON ServiceYou can create an ASON trail with the iron-class protection. When you create an iron service,primarily use the protection resource of a TE link. If the protection resource is insufficient, youcan use the non-protection resource of the TE link. It is recommended that you ensure sufficientprotection resources in the network before creating an iron service.


resources.l All links that the ASON trail passes through are under MSP protection. Otherwise, you

need to create fibers and configure the MSP protection before creating 1:1, 1:N, or 1+1protected ASON trails.

Service RequirementSee Figure 1-43. The four ASON NEs compose an MSP ring. An iron service at the rate of 155Mbit/s is required between NE1 and NE3.



1-107

Figure 1-43 Iron service requirement

NE1

NE2

NE3

NE4MSP Ring

: ASON NE

Board Configuration

To meet the previously mentioned service requirement, you can configure the boards as shownin Figure 1-44.


Service Planning

To meet the service requirement, you can refer to Table 1-26 to plan an iron service.

Table 1-26 Iron service planning

Attribute NE1<->NE3

Source NE NE1



Issue 02 (2010-09-24)

Attribute NE1<->NE3


Source timeslot 1

Sink NE NE3


Sink timeslot 1

Protection class Iron



The procedure for creating an iron ASON trail is similar to that described in "Creating a DiamondASON Trail". The difference lies in that the protection type is Iron.

Procedure





l Type: ASON Trail

l Class: Iron





NOTE





1-109

NOTE






NOTE



NOTE







----End



Issue 02 (2010-09-24)

1.8.7 Creating an ASON Server TrailAn ASON server trail is mainly used to carry lower order services (VC3 or VC12). An ASONserver trail is applicable to diamond, gold, silver, or copper services. At the NE side, an ASONserver trail is also called a tunnel service.


resources.

Service RequirementThe following descriptions are based on a diamond ASON server trail. See Figure 1-45. EightVC12 services need to be transmitted between NE1 and NE3, and the diamond-class protectionis required for these trails. In this case, you need to configure ASON server trails.

Figure 1-45 Diamond ASON server trail requirement

NE1

NE2

NE3

NE4

: ASON NE

VC12

VC12

Working Protection

Diamond tunnel Diamond tunnel




1-111


Service Planning

To meet the service requirement, you can refer to Table 1-27 to plan a diamond ASON servertrail.

Table 1-27 Diamond ASON server trail planning

Attribute NE1<->NE3

Source NE NE1

Source board-port 2-PQ1

Source timeslot 1-8

Sink NE NE3

Sink board-port 2-PQ1

Sink timeslot 1-8


ASON server trail Diamond ASON server trail

SNCP Access None


Rerouting attributes Revertive Mode Non-revertive



Issue 02 (2010-09-24)

Attribute NE1<->NE3

Lockout Unlocked

Priority 1

Rerouting trigger condition Reroute when one trail fails

CrankBack 1

Rerouting policy Use existing trails wheneverpossible


No


Procedure



Step 3 In Basic information, enter the basic information of the ASON trail.For example, set the attributes as follows:l Name: NE1-NE3-ASON-Trail-0009l Type: ASON Server Traill Class: Diamondl Concatenation Type: Non-Concatenation

Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.For example, set the attributes as follows:l Revertive: Non-Revertive. (For revertive ASON server trails, select Revertive, For

scheduled revertive ASON server trails, select Scheduled revertive.)l Lockout: Unlockedl Priority: 1l Trigger Condition: Reroute when one trail failsl CrankBack: 1l Policy: Use existing trail whenever possiblel Rerouting Triggered by B3 Bit Error: Nol Rerouting Hold-off time: 0

Step 5 On the left-hand side of the window, click Browse beside Source. In the dialog box displayed,select the desired NE, slot, port, or timeslot. Click OK.

Step 6 On the left-hand side of the window, click Browse beside Sink. In the dialog box displayed,select the desired NE, slot, port, or timeslot. Click OK.




1-113

NOTE


Step 8 Set Explicit Node or Explicit Link. Right-click an NE in the right-hand topology and select anoption from the shortcut menu as needed.

NOTE




For example, you can do as follows:

l Select the Working option button. Right-click NE2 in the right-hand topology and chooseSet As Explicit Node from the shortcut menu.

l Select the Protection option button. Right-click NE4 in the right-hand topology and chooseSet As Explicit Node from the shortcut menu.


NOTE



NOTE






Issue 02 (2010-09-24)




----End

1.8.8 Creating a Segmented ASON Server TrailIn the case of a end-to-end tunnel that traverses multiple nodes, the intermediate nodes cannotadd or drop lower order services through this UNI link. In this case, you can use the sectionedtunnel to ensure that multiple nodes share the tunnel bandwidth.


resources.

Service RequirementSee Figure 1-47. There are ASON server trails available between NE1 and NE2, and betweenNE2 and NE3. To improve the resource utilization, you do not need to create an additional servertrail between NE1 and NE3 to create a lower order services between NE1 and NE3, but directlycreate the service based on the two segments of existing server trails. This server trail betweenNE1 and NE3, which consists of two segments in this case, is called a segmented server trail.

Figure 1-47 Segmented ASON server trail requirement

NE4

NE1

NE2

NE3

Silver tunnel Silver tunnel

lower order servicefrom NE1 to NE3

lower order servicefrom NE1 to NE2




1-115

Figure 1-48 Board configuration for NE1-NE3

Service PlanningTo meet the service requirement, you can refer to Table 1-28 to plan a segmented ASON servertrail between NE1 and NE3.

Table 1-28 Silver ASON server trail planning

Attribute NE1<->NE2 NE2<->NE3

Source NE NE1 NE2

Sink NE NE2 NE3

Protection class Silver ASON server trail

Route constraint Routes are automatically calculated.

NOTE

The boards and timeslots occupied by an ASON server trail can be queried in the ASON TrailManagement window after the server trail is created. The following description is based on the assumptionthat on NE1, the first VC4 of 11-N2SL64-1 is occupied; on NE2, the first VC4 of 11-N2SL64-1 and thefirst VC4 of 8-N2SL64-1 are occupied; on NE3, the first VC4 of 8-N2SL64-1 is occupied.

Table 1-29 shows the VC12 service planning on NE1, NE2 and NE3.



Issue 02 (2010-09-24)

Table 1-29 VC12 service planning on NE1, NE2 and NE

Attribute Cross-Connectionon NE1

Cross-Connectionon NE2

Cross-Connectionon NE3

Source board-port 2- PQ1 8-N2SL64-1 8-N2SL64-1

Source VC4 timeslot - 1 1

Source VC12timeslot

1 1 1

Sink board-port 11-N2SL64-1 11-N2SL64-1 2- PQ1

Sink VC4 timeslot 1 1 1


Service level VC12 VC12 VC12

Direction Bidirectional Bidirectional Bidirectional

Procedure

Step 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.

Step 2 Choose Create/Modify > Create Trail to create a VC4 server trail.

Step 3 Enter the information about the VC4 server trail.For example, set the server trail as follows:l Direction: Bidirectionall Level: VC4 Server Traill Source: NE1l Sink: NE2

Step 4 Check the SPC First check box. Click ASON Attributes Settings tab.

Step 5 Set the protection type to Silver.

Step 6 Check the Activate the Trail check box. Click Apply. The system prompts that the operationwas successful. Click Close.

NOTE

If you check the Activate the Trail check box, the created trail is applied to the so that the trail is in theactivated state.

Step 7 Repeat Steps 1 through 6 to create a VC4 server trail between NE2 and NE3.

Step 8 In the Create Trail window, enter the information about the VC12 trail.For example, set the VC12 trail as follows:l Direction: Bidirectionall Level: VC12l Source: NE1-2-PQ1-1(SDH_TU-1)



1-117

l Sink: NE3-2-PQ1-1(SDH_TU-1)

Step 9 Check the Activate the Trail check box. Click Apply. The system prompts that the operationwas successful. Click Close.

Step 10 Choose Service > SDH Trail > Search for SDH Trail from the main menu. Click Nextrepeatedly until the Finish button is displayed. Click Finish.

Step 11 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the detailsabout the VC4 server trail and the VC12 trail that you create.

Step 12 Choose Configuration > SDH ASON > ASON Trail Management from the main menu. Viewthe information about the created ASON trail.

----End

1.8.9 Creating Two Associated SDH ASON TrailsThe ASON trail association function associates two services so that the two services are notpreempted by each other during the rerouting and optimization.


Application Scenario

As shown in Figure 1-49, the 1+1 services need to be created between R1 and R2 and passthrough the ASON network. To ensure that the two trails do not pass through the same ASONnode, the two ASON trails must be associated. After the two ASON trails are associated, oneASON trail will not be rerouted to the other ASON trail.

Figure 1-49 Two associated ASON trails

: ASON NE

: User Equipment

R1

R2

A

B

C

E

F

GH

I



Issue 02 (2010-09-24)

Background InformationNOTE

Currently, association is supported between silver trails, between copper trails, between silver and coppertrails, between silver server trails, between copper server trails, and between silver and copper server trails.

Procedure


Step 2 In the SDH ASON Trail Management window, choose Create > Association Trail.

Step 3 In the SDH ASON Association Trail Creation window, enter Basic Information and RouteRestriction of trail 1 and trail 2. The example is provided as follows:



1-119

NOTE

l Only the association between routes in silver or copper protection is supported. Hence, set the protectiontype 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.

l In the case of the SDH ASON NE of the GCP V100R007C02 version or a later version, and the OptiX OSN9560 NE of the GSP V100R004 version or later version, you can create the associated ASON trails thatshare the same source or that have different sources.

l In the case of the SDH ASON NE of the GCP V100R007C01 version or a later version, and the OptiX OSN9560 NE of the GSP V100R002 version or later version, you can create the associated ASON trails thatshare the same source.

Step 4 Set the common attributes, including the Revertive Mode, WTR Time, Lockout, Priority,CrackBack, Trigger Condition for Rerouting Associated Route, Policy, ReroutingTriggered by B3 Bit Error and Rerouting Hold-off time.

Step 5 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 SDH ASON NE of the GCP V100R007C02 version or a later version, and the OptiX OSN9560 NE of the GSP V100R004 version or later version, you can pre-calculate the associated ASON trailsthat share the same source or that have different sources.

l Only after you pre-calculated successfully the associated ASON trails that have different sources, you couldcreate them.

Step 6 Click Apply. After confirmation, apply the configuration.


----End

1.8.10 Setting ASON Trail AssociationASON trail association means two ASON trails are associated. The associated trails are separatedfrom each other during the service optimization and rerouting whenever possible. Serviceassociation is applied to access services that have two access points. After two trails areassociated, if one of the trails (or server trails) is rerouted or optimized, the ASON NE adoptsthe 1+1 routing policy to try to avoid the associated ASON trail (or server trail).




Issue 02 (2010-09-24)

Background Informationl Currently, association is supported between silver trails, between copper trails, between

silver and copper trails, between silver server trails, between copper server trails, andbetween silver and copper server trails.

l The system supports automatically setting association only for SNCP ASON-SDH trailsin a single domain. For SNCP ASON-SDH trails in multiple domains, you need to manuallyset association.

l Associating the two trails may clear their preset restoration trails.

Procedure


Step 2 In the SDH ASON Trail Management list, select two ASON trails to be associated. Right-clickthem and choose Set Association.

Step 3 In the confirm dialog box, click Yes. A dialog box is displayed indicating that the operation wassuccessful.

Step 4 Click Close.

Step 5 Optional: Select an ASON trail in the SDH ASON Trail Management list. Right-click andchoose Set Association Source from the shortcut menu. Select another ASON trail, right-clickand choose Set Association from the shortcut menu. In the confirm dialog box, click Yes. Adialog box appears, telling that the trails are successfully associated. Click Close.

NOTE

To cancel the association relations, right-click and choose Remove Association. A dialog box is displayedindicating that this operation may decrease the service protection ability.

Step 6 The dialog box is displayed, set the associated route attributes, including trigger condition forrerouting associated route, click OK.

Step 7 A dialog box appears, telling that the operation succeeded. Click Close.

Step 8 Select a trail in the SDH ASON Trail Management list. You can know whether the associationis successful by viewing the value of Associated or Not.

Step 9 Optional: In the lower left area of the SDH ASON Trail Management window, click theAssociated Route tab to view the information about the two associated trails.

----End

1.8.11 Creating ASON Services in BatchesThe batch creation function is always used if a large number of ASON services need to be created.


l The U2000 must have synchronized networkwide TE links and have sufficient TE linkresources.



1-121

Service Requirement

See Figure 1-50. The four NEs are all ASON NEs. Three non-revertive silver services at therate of 155 Mbit/s are required to be configured between NE1 and NE3.

Figure 1-50 Batch silver service requirementNE1

NE2

NE3

NE4

：ASON NE： LSP

Board Configuration

To meet the previously mentioned service requirement, you can configure the boards as shownin Figure 1-51.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

N1S

L16

Service Planning

To meet the service requirement, you can refer to Table 1-30 to plan a silver service.



Issue 02 (2010-09-24)

Table 1-30 Silver service planning

Attribute NE1<->NE3

Source NE NE1

Source board-port 6-N1SL16-1 6-N1SL16-1 6-N1SL16-1

Source timeslot 6 7 8

Sink NE NE3

Sink board-port 13-N1SL16-1 13-N1SL16-1 13-N1SL16-1

Sink timeslot 6 7 8


Route constraint The service route must pass NE2.

Reroutingattribute

Reversion mode Non-revertive

Lockout Unlocked

Priority 2

CrankBack 1

Policy Use the existing trail whenever possible

ReroutingTriggered by B3Bit Error

No

Rerouting Hold-off time

0

Procedure





l Type: ASON Server

l Class: Silver



Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.For example, set the attributes as follows:



1-123

l Revetrive Mode: Non-Revetrive (Select Automatically Revertive or ScheduledRevertive if the silver service is revertive.)

l Lockout: Unlockedl Priority: 2l CrankBack: 1l Policy: Use existing trail whenever possiblel Rerouting Triggered by B3 Bit Error: Nol Rerouting Hold-off time: 0

Step 5 Set the source NE. In the right-hand topology, double-click the sink NE and select a slot, portand timeslot from the dialog box displayed. Click OK.For example, select port 1 and timeslot 6 of the N1SL16.



NOTE


Step 8 Set Explicit Node or Explicit Link. Right-click an NE in the right-hand topology and select anoption from the shortcut menu as needed.

NOTE








Issue 02 (2010-09-24)

NOTE


Step 10 Set the Activate or Duplicate after created check box.

NOTE





Step 12 Click Close. In the Copy dialog box displayed, select the source and sink timeslots. ClickAdd.For example, select the timeslots 7-8 of the source NE (NE1-6-N1SL16-1(SDH-1)-VC4-7-8)and the timeslots 7-8 of the sink NE (NE3-13-N1SL16-1(SDH-1)-VC4-7-8).

Step 13 Check the Activate after Duplicate and Duplicate Route Constraint check boxes.

Step 14 Confirm that the trail and route information is correctly entered. Click OK.

Step 15 After the creation is complete, a dialog box appears, telling that the operation was successful.Click Close.


----End

1.8.12 Deactivating the SDH ASON TrailDeactivating an SDH ASON trail can release the resources that the trail occupies.



You do not need to cancel the association configured before deactivating the associated ASON trail, becausethe system automatically cancels the association during the deactivation operation.

During the SDH ASON trail management, if an active client trail exists, the corresponding ASON servertrail cannot be deactivated.

Procedure




1-125

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 youperform other operations. It is recommended not to deactivate trails in batches.

Step 3 Click Yes in the confirmation dialog box displayed twice.

NOTE

If the selected trails contain the trails that are managed by SDH trails, the confirmation dialog box isdisplayed for the third time. Click Yes. The Operation Result dialog box is displayed indicating that theoperation fails. You can click Detail to view failure causes.

If the trails to be deactivated contain associated trails, the NMS cancels the trail association beforedeactivating them. Detailed situations are as follows:

l If the trail association fails to be canceled, the NMS stops the deactivation and reports the failure ofcanceling the association.

l If the trail association is canceled successfully but the deactivation fails, the NMS reports thedeactivation failure and the successful association cancelation.

l If the trail association is canceled and the trails are deactivated successfully, the NMS reports that thedeactivation is successful.

l If a trail is deactivated successfully but the associated trail fails to be deactivated, the NMS reports thatthe operation is partially successful and the association is canceled for the trail failing to be deactivated.

Step 4 After the operation is complete, the system prompts that the operation was successful. ClickClose. The list shows that the ASON trail is in the Inactive state.

----End

1.8.13 Deleting an ASON TrailThe operation of deleting ASON trails removes the trail data from the U2000 and the NE.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON service must be inactive.


l Deleting an ASON trail removes the trail data from the U2000 and the NE. Exercise caution when youperform this operation.

l In the SDH ASON Trail Management, if an active client trail exists, the corresponding ASON servertrail cannot be deactivated.

l When deactivating associated ASON services, do not delete the association first. The systemautomatically deletes the association during deactivation.

Procedure


Step 2 Select a deactivated ASON trail from the list, right-click, and choose Delete from the shortcutmenu.

Step 3 Click OK in the confirmation dialog box.



Issue 02 (2010-09-24)

Step 4 After the deletion is complete, a dialog box is displayed indicating that the operation wassuccessful. Click Close.

----End

1.9 Modifying the Attributes of ASON ServicesAs an ASON network is changing, you need to modify the attributes of ASON services in thenetwork according to different ASON features. This facilitates the configuration, managementand maintenance of the ASON network.

1.9.1 Viewing ASON Service AttributesYou can view the detailed information of an ASON trail, including the basic attributes, constraintroutes, shared MESH restoration trail status information, associated ASON trail attributes, andSLA-compliant.

1.9.2 Setting the Routing AttributesYou can set the routing attributes for an ASON service, including rerouting revertive mode,WTR time, scheduled revertive time, rerouting lockout status, revertive lockout, reroutingtriggered by B3 bit error, rerouting priority, trigger condition, times of crankbacks and routeselection policy.

1.9.3 Setting the Scheduled Reversion TimeIf the ASON service is rerouted successfully, you can set the scheduled reversion time after theoriginal trail is restored. Before the scheduled reversion time expires, the service is automaticallyreturned to the original trail. If you set the scheduled reversion time when the fault in the originalpath is not rectified, the service may be interrupted.

1.9.4 Setting the B3 Alarm to Trigger ReroutingAfter the diamond service, gold service, or silver service is created, you can set the B3 alarm asa condition for triggering rerouting.

1.9.5 Setting Preset Restoration TrailYou can set priorities for rerouting ASON trails. When an ASON service is being rerouted, theservice has the priority to be restored to the preset trail. If the preset restoration trail is occupied,the system computes the route again.

1.9.6 Setting Shared MESH Restoration TrailYou can preset a shared MESH restoration trail for an ASON trail. When an ASON service isrerouted, you can restore the service to the preset trail with priority. The control plane reservesthe timeslot used by the shared MESH restoration trail. That is, the timeslot cannot be used byother services during the service creation or rerouting.

1.9.7 Setting the Original RouteThe route of an ASON service is usually the original route when the service is created. If theroute of an ASON service changes, you can also set the route after change to the original route.

1.9.1 Viewing ASON Service AttributesYou can view the detailed information of an ASON trail, including the basic attributes, constraintroutes, shared MESH restoration trail status information, associated ASON trail attributes, andSLA-compliant.



1-127

Prerequisitel You must be an NM user with "NE monitor" authority or higher.

l An ASON trail must be created.

Procedure


Step 2 In the trail list, right-click the ASON trail that you want to view and choose Details from theshortcut menu.

Step 3 In the dialog box displayed, view the basic attributes of the ASON trail.

Step 4 Click the Restrictive Route tab. View the route constraint information of the ASON trail.

Step 5 Optional: If an associated trail is set for the ASON trail, click the Associated ASON TrailAttribute tab to view the attributes of the associated trail.

Step 6 Click the SLA-Compliant Details tab to view the details of the SLA-compliant of the ASONtrail.

Step 7 Optional: If a shared MESH restoration trail is set, click the Shared MESH Restoration TrailStatus Details tab to view the details of the shared MESH restoration trail status.

----End



Issue 02 (2010-09-24)

1.9.2 Setting the Routing AttributesYou can set the routing attributes for an ASON service, including rerouting revertive mode,WTR time, scheduled revertive time, rerouting lockout status, revertive lockout, reroutingtriggered by B3 bit error, rerouting priority, trigger condition, times of crankbacks and routeselection policy.

Prerequisitel You must be an NM user with "NE operator" authority or higher.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 ASON trails, right-click and choose Set RoutingAttributes from the shortcut menu. The Set Routing Attributes dialog box is displayed.

NOTE

When you create an ASON trail, you can set the rerouting attributes. Click Create > ASON Trail. In theASON Trail Management user interface, click Routing Attributes tab to set the rerouting attributes.

Step 3 In the Set Routing Attributes user interface, set attributes of routing and click OK.

NOTE

l Currently, you can set trigger conditions of routing for diamond services only.

l Revertive Mode includes Non-Revertive, Scheduled Revertive, and Scheduled Revertive. If theRevertive Mode is set as Scheduled Revertive, you need to set Scheduled revertive time.

Step 4 In the confirmation dialog box displayed, click Yes. A prompt is displayed indicating that theoperation was successful. Click Close.

----End

1.9.3 Setting the Scheduled Reversion TimeIf the ASON service is rerouted successfully, you can set the scheduled reversion time after theoriginal trail is restored. Before the scheduled reversion time expires, the service is automaticallyreturned to the original trail. If you set the scheduled reversion time when the fault in the originalpath is not rectified, the service may be interrupted.



1-129

Prerequisitel You must be an NM user with "NE operator" authority or higher.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



NOTE


Step 3 Click Revertive Mode and choose Scheduled Revertive from the drop-down list.

Step 4 In Set Routing Attributes, select the Scheduled revertive time check box and set the timelimit within which the service must be returned to the original trail after the original trail isrestored.

Step 5 Set the other items according to the actual planning information. Then, click OK.

Step 6 Then, another dialog box is displayed indicating that the operation is successful. Click Close.

----End

1.9.4 Setting the B3 Alarm to Trigger ReroutingAfter the diamond service, gold service, or silver service is created, you can set the B3 alarm asa condition for triggering rerouting.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The data of the ASON NEs must be configured and uploaded.



Issue 02 (2010-09-24)

l The NE time must be synchronous with the NM time.

Procedure



NOTE


Step 3 In Set Routing Attributes, set Rerouting Triggered by B3 Bit Error to Yes.

NOTE

The B3_EXC and B3_SD alarms can trigger the rerouting.

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.9.5 Setting Preset Restoration TrailYou can set priorities for rerouting ASON trails. When an ASON service is being rerouted, theservice has the priority to be restored to the preset trail. If the preset restoration trail is occupied,the system computes the route again.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The rerouting ASON trail must be created.l The U2000 must have synchronized networkwide TE links and have sufficient TE link

resources.

Background InformationCurrently, the diamond, gold, and silver ASON trails and the silver ASON server trails supportsetting the restoration reverting trail.



1-131

In the case of the ASON NEs of the GCP V100R007C02 version or a later version, a presetrestoration trail is rerouted when if a link of the preset restoration trail is interrupted.

Procedure


Step 2 Select an ASON service and click Maintenance. Choose Set Preset Restoration Trail fromthe drop-down menu.

Step 3 Click Pre-Calculation Route to view the related information. Click Apply to complete thesettings of the preset reverting trail.

NOTE

If the Automatic Pre-Calculation check box is checked, the U2000 sends a command to ask the NE toautomatically precalculate the route. Any change to the route constraints triggers the automaticprecalculation.

Step 4 Optional: On the topology, right-click an NE and set the route constraints. Click the RouteRestriction to view or set the information of Explicit Node, Excluded Node, Explicit Linkand Excluded Link. Click Apply to complete the settings of the preset restoration trail.

----End

1.9.6 Setting Shared MESH Restoration TrailYou can preset a shared MESH restoration trail for an ASON trail. When an ASON service isrerouted, you can restore the service to the preset trail with priority. The control plane reservesthe timeslot used by the shared MESH restoration trail. That is, the timeslot cannot be used byother services during the service creation or rerouting.


l There must be at least two configured ASON NEs.

Background Informationl Currently, only the revertive silver ASON trails and the silver ASON server trails support

setting the shared MESH restoration trail.

l If a timeslot is configured with a multiplex section, the timeslot is grayed out and cannotbe selected.

l Multiple revertive silver services can share the same shared MESH restoration trail.

Procedure


Step 2 Select one revertive silver ASON service and click Maintenance. Select Set Shared MESHRestoration Trail from the drop-down list.

Step 3 Click Pre-Calculation Route to view the related information. Click Apply to complete thesettings of the shared MESH restoration trail.



Issue 02 (2010-09-24)

NOTE

If the Automatic Pre-Calculation check box is checked, the U2000 sends a command to ask the NE toautomatically precalculate the route. Any change to the route constraints triggers the automaticprecalculation.

Step 4 Optional: On the topology, right-click an NE and set the route constraints. Click the RouteRestriction to view the information of Explicit Node and Excluded Node. Click Apply tocomplete the settings of the shared MESH restoration trail.

----End

1.9.7 Setting the Original RouteThe route of an ASON service is usually the original route when the service is created. If theroute of an ASON service changes, you can also set the route after change to the original route.


Background InformationFor a non-revertive trail, if the original route is normally restored after trail rerouting, the trailcannot automatically revert to the original route. For a revertive ASON service, if the failure iscleared after rerouting, the service automatically reverts.

Procedure


Step 2 Set a trail that you want to set and click Maintenance. Choose Save As Original Route fromthe 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 completethe setting of the original route.

Step 5 Optional: Set a trail for which the original route is already set and click Maintenance. ChooseRefresh Original Route from the drop-down menu.

----End

1.10 Modifying the Route of an ASON ServiceAs an ASON network is changing, you need to modify the route of an ASON service in thenetwork according to different situations. This facilitates the configuration, management andmaintenance of the ASON network.

1.10.1 Reverting ASON TrailsAfter rerouting, you can revert an ASON trail to the original route or the route before rerouting,based on the reverting function supported by the ASON.

1.10.2 Optimizing an ASON Service



1-133

To manually adjust one or more service trails, you can use the optimization function to transferthe ASON service to the expected trails.

1.10.1 Reverting ASON TrailsAfter rerouting, you can revert an ASON trail to the original route or the route before rerouting,based on the reverting function supported by the ASON.


l The ASON trail must be created.

Background Informationl ASON trails are classified into non-revertive ASON trails, automatically revertive ASON

trails and scheduled revertive ASON trails.

l For non-revertive ASON trails, you can specify whether they are restored to timeslots orports.

l For automatically revertive ASON trails, you can manually revert them to the routes beforererouting.

l For scheduled revertive ASON trails, a fault of the original route is cleared after thererouting of a service in the scheduled reversion mode, you can set scheduled revertivetime to enable the service to revert at a specified time.

Procedurel For non-revertive ASON trails

1. Choose Configuration > SDH ASON > ASON Trail Management from the mainmenu.

2. Optional: Click Filter to set the filter criteria and set Whether Original Route IsActive to No. Click Filter All. A dialog box is displayed. Click Yes.

3. In the list displayed, select one or more ASON trails to be reverted. Click the OriginalRoute tab to view the original routes of the ASON trails.

4. Choose Configuration > SDH ASON > TE Link Management from the main menu.Check whether idle resources exist on the TE link of the original route.

5. In the SDH ASON Trail Management window, click Maintenance and selectRevert To Original Route > Revert to Port or Revert To Original > Revert toTimeslot. The ASON trails then revert to the routes before rerouting.

6. A dialog box is displayed. Click Yes. The Restore to Port or Restore to Timeslotdialog box is displayed indicating the operation result.

7. Click Close.

NOTE

You can click Retry to perform the restoration again.

l For automatically revertive ASON trails and scheduled revertive ASON trail




Issue 02 (2010-09-24)

2. Optional: Click Filter to set the filter criteria and set Whether Original Route IsActive to No. Click Filter All. A dialog box is displayed. Click Yes.

3. In the list displayed, select one or more ASON trails to be reverted. ClickMaintenance and select Manual Revert from the drop-down menu. The ASON trailsthen revert to the routes before rerouting.

NOTE

If the revertive mode is automatically revertive, you can set WTR time. When the original trail isrestored, the service is automatically returned to the original trail after a period of time.

If the revertive mode is scheduled revertive, you can set the scheduled revertive time after the originaltrail is restored. Before the scheduled reversion time expires, the service is automatically returned tothe original trail.

----End

1.10.2 Optimizing an ASON ServiceTo manually adjust one or more service trails, you can use the optimization function to transferthe ASON service to the expected trails.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l An ASON trail must be created.

Background Informationl For a revertive silver service, you cannot perform the optimization operation when the

service is being reverted upon rerouting.l Diamond and non-diamond service cannot be optimized in batches at the same time.l ASON service in different domains do not support optimization in batches.

Procedure


Step 2 In the list displayed, select one or more ASON trails that you want to adjust. ClickMaintenance 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 afteroptimization.

Step 4 Optional: To save the optimization settings, check the Save Optimization Settings check box.

Step 5 Check whether the route adjustment is correctly set and click Apply.The Operation Result dialog box is displayed.

Step 6 Click Close. A dialog box is displayed indicating that the operation saves the current route asthe original route.

NOTEIf you do not check the Set As Original Route Concurrently check box before clicking Apply, this dialog boxis not displayed.

Step 7 Click Yes. The Operation Result dialog box is displayed. Click Close.



1-135

Step 8 In the trail list, select the trail after optimization. You can view the route information of thetrail after optimization in the Actual Route.

----End

1.11 Migrating ASON ServicesAn ASON network supports the migration between traditional services and ASON services, andsupports the in-service migration between ASON services at different levels.

1.11.1 Downgrading an ASON Service to a Traditional ServiceAfter an ASON service is converted to a traditional service, you can use the trail search functionto manage the service in the SDH trail management.

1.11.2 Upgrading a Traditional Service to an ASON ServiceYou can convert a traditional service to an ASON service. This section describes how to upgradea traditional service to a non-revertive silver service.

1.11.3 Migration Between ASON ServicesThe diamond service, gold service, silver service, and copper service can be migrated to eachother.

1.11.4 Downgrading an ASON Server Trail to a Traditional Server TrailYou can perform migration between an ASON server trail and a traditional server trail.

1.11.5 Upgrading a Traditional Server Trail to an ASON Server TrailYou can upgrade a traditional server trail to an ASON server trail.

1.11.6 Migration Between ASON Server TrailsThe migration between the diamond tunnel, gold tunnel, silver tunnel, and copper tunnel issupported.

1.11.1 Downgrading an ASON Service to a Traditional ServiceAfter an ASON service is converted to a traditional service, you can use the trail search functionto manage the service in the SDH trail management.


l The ASON trail must be created.


To convert the ASON route segment of an end-to-end trail that passes through an ASON network,perform the following operations:

l Navigate to the SDH Trail Management window. Delete the ASON trail segment of thetrail from the network layer.

l Navigate to the SDH ASON Trail Management window. Convert the ASON trail segmentof the trail to an SDH service.

l Use the SDH trail search function to search again and manage the trail.



Issue 02 (2010-09-24)

Procedure


Step 2 In the list displayed, right-click the ASON trail that you want to convert and choose Downgradeto Traditional Service from the shortcut menu. In the confirmation dialog box displayed, clickYes. If an error message is displayed indicating that the ASON trail cannot be downgradedbecause it is managed by an SDH trail, this ASON service exists in the SDH TrailManagement window. You need to right-click the service in the SDH Trail Management andchoose Delete from Network Layer from the shortcut menu to downgrade it. Then, repeat Step2.

NOTEIn this step, you can navigate to the SDH Trail Management window and view the ASON-SDH Trailfield in the list to check if the trail passes an ASON domain. If the trail passes an AOSN domain, deletethe service from the network layer and then downgrade it in the ASON Trail Management window.

Step 3 After the conversion, Choose Service > SDH Trail > Search for SDH Trail from the mainmenu. You can search the service that is just converted.

NOTE

If you cannot search out this trail, wait for several minutes and search again. You can also synchronize theNE cross-connections on the SDH ASON topology.

----End

1.11.2 Upgrading a Traditional Service to an ASON ServiceYou can convert a traditional service to an ASON service. This section describes how to upgradea traditional service to a non-revertive silver service.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l A traditional service must be configured on an ASON NE.

Background Informationl By default, SNCP services are converted to diamond services, MSP services are converted

to gold services or downgraded gold services, non-protection services are converted tosilver services, and protection timeslot services are converted to iron services. Inadaptableservices such as broadcasting and unidirectional services cannot be upgraded to ASONservices.

l If the entire trail exists on the ASON NE, you can upgrade the trail to an ASON trail. Ifonly part of the trail exists on the ASON NE, you can upgrade only the trail segment thatpasses the ASON NE to an ASON trail.

l Partial upgrade means to upgrade part of the trail to an ASON service. Some part of thetrail is not in the ASON domain, so you cannot upgrade the entire trail to an ASON service.Full upgrade is available for a trail that is within an ASON domain. A trail that is not withinthe ASON domain cannot be fully upgraded to an ASON service.

Procedure




1-137

Step 2 In the list displayed, select one or more SDH trails that you want to upgrade. Right-click andchoose Upgrade to ASON Trail from the shortcut menu.

Step 3 In the dialog box displayed, enter the parameters of the ASON service.For example,l Class: Sliver.l Revertive Mode: Non-Revertive.l Rerouting Lockout: Unlocked.l Rerouting Priority: 2.l Rerouting Policy: Use existing trails whenever possible.

Step 4 Select the trail that you want to upgrade and click OK.


Step 6 A prompt is displayed indicating that the operation is successful. Click OK.

----End

1.11.3 Migration Between ASON ServicesThe diamond service, gold service, silver service, and copper service can be migrated to eachother.


Background Informationl Silver services configured with the shared MESH restoration trail cannot be migrated.l Associated services cannot be migrated to diamond services.l The diamond service and gold service cannot be migrated to each other.l This topic describes how to migrate a diamond service to a silver service. The procedure

is similar to the migration between a diamond service and a gold, silver, copper service.Before you migrate an ASON service to a gold service, you need to create the MSP.

Procedure


Step 2 In the list displayed, right-click the diamond service that you want to convert and choose In-Service Migration > Silver from the shortcut menu.



Issue 02 (2010-09-24)

Step 3 Click Yes in the Prompt dialog box.

Step 4 The Confirm the route that you want to reserve dialog box is displayed. Confirm whether toreserve the working route or the protection route for the desired diamond ASON service, andcorrespondingly select Working Route or Protection Route.

NOTE

The route that you want to reserve can be selected only when a diamond service is migrated to a silver or copperservice.

Step 5 Click Yes in the Prompt dialog box. Then, you can query the rerouting attributes of the ASONservice as indicated.

----End

1.11.4 Downgrading an ASON Server Trail to a Traditional ServerTrail

You can perform migration between an ASON server trail and a traditional server trail.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON server trail must be created.



1-139


The two ways of migrating an ASON server trail are as follows:

l In the SDH Trail Management window, use the Downgrade to Traditional Servicemethod to downgrade an ASON server trail.

l In the SDH ASON Trail Management window, use the Downgrade to TraditionalService method to downgrade an ASON server trail.

The following procedure describes how to migrate an ASON server trail to a traditional servertrail in the second way.

Procedure


Step 2 Right-click the ASON server trail that needs to be downgraded and choose Downgrade toTraditional Service from the shortcut menu. Click Yes in the confirmation dialog box. If amessage is displayed indicating that The ASON trail that an SDH trail manages cannot bedowngraded, it indicates that the ASON service exists in the SDH Trail Management window.You need to navigate to the SDH Trail Management window, right-click the ASON serviceand choose Delete from Network Layer from the shortcut menu. Repeat Step 2 to perform thedowngrade operation again.

NOTEIn this step, you can view the value of ASON-SDH Trail in the SDH Trail Management window todetermine whether the trail contains an ASON domain. If the trail contains an ASON domain, delete theservice from the network layer and then downgrade the service in the ASON Trail Management window.

Step 3 A prompt is displayed indicating that the operation is successful. Click Close.

Step 4 Optional: Choose Configuration > SDH ASON > ASON Trail Management from the mainmenu. You cannot query the trail.

Step 5 Optional: Choose Configuration > SDH ASON > ASON Topology Management from themain menu. Select all ASON NEs and click Synchronize Cross-Connection. A prompt isdisplayed indicating that the operation is successful. Click Close.

Step 6 Choose Service > SDH Trail > Search for SDH Trail from the main menu. Click Next untilthe operation is complete.

Step 7 Optional: Choose Service > SDH Trail > Manage SDH Trail from the main menu. View thetraditional server trail that is successfully migrated.

----End

1.11.5 Upgrading a Traditional Server Trail to an ASON Server TrailYou can upgrade a traditional server trail to an ASON server trail.


l There must be at least two configured ASON NEs.



Issue 02 (2010-09-24)

ProcedureStep 1 Choose Service > SDH Trail > Manage SDH Trail from the main menu.

Step 2 In the list, select the traditional server trail that you want to migrate, right-click and chooseUpgrade to ASON Trail from the shortcut menu. The Upgrade to ASON Trail dialog box isdisplayed.

Step 3 Select the trail that you want to upgrade and click OK.


Step 5 A prompt is displayed indicating that the operation is successful. Click OK.

----End

1.11.6 Migration Between ASON Server TrailsThe migration between the diamond tunnel, gold tunnel, silver tunnel, and copper tunnel issupported.


Background Informationl The silver server trail that is configured with the shared mesh restoration trail cannot be

migrated.l The server trail that is associated with another trail cannot be migrated to diamond server

trails.l This topic considers the migration from the diamond server trail to the silver server trail as

an example. The operations for the migration between the diamond server trail, gold servertrail, silver server trail, and copper server trail are similar. Before you migrate a server trailinto a gold server trail, however, you need to create the multiplex section.


Step 2 Select the diamond server trail to be migrated from the list. Right-click and choose In-ServiceMigration > Silver from the shortcut menu.

Step 3 Click Yes in the Prompt dialog box.

Step 4 The Confirm the route that you want to reserve dialog box is displayed. Select WorkingRoute if you determine to reserve the working route of the diamond server trail that needs to bemigrated. Select Protection Route if you need to reserve the protection route of the diamondserver trail that needs to be migrated. Then, click OK.

NOTE

You need to select the route to be reserved only when you migrate the diamond server trail to the silver or copperserver trail.

Step 5 Click Yes in the Prompt dialog box. Then, you can check the rerouting attributes of the ASONtrails.

----End



1-141

1.12 Creating ASON Trail GroupsAn ASON trail group is often used with LCAS.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON trail must be created.

Background InformationAn ASON trail group associates the member trails that belong to the same LCAS service to anLSP group, and add, delete and modify these member trails in the ASON network. To enablevirtual concatenation services to have an enhanced fault tolerance capability, separate themember trails whenever possible.

Each ASON trail group has an ID, which is the unique ID assigned by an ASON NE. The membertrails in the ASON trail group have the same source and sink, but the trails are separated wheneverpossible. You can create an ASON trail group at the initial node only.

Service RequirementSee Figure 1-52. Create a GE service between NE1 and NE3, bind four VC4s to the service.Configure an EGT2 board each slot 4 of NE1 and NE3.

Figure 1-52 ASON trail group service requirement

NE4

NE1

NE2

NE3

: ASON NE: LSP

ASON trail group(4×LSP)

Board ConfigurationFor the board configuration of NE1 and NE3, refer to Figure 1-53.



Issue 02 (2010-09-24)


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

EG

T2

For the board configuration of NE2 and NE4, refer to Figure 1-54.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

Service Planning

Refer to Table 1-31 for GE service planning.



1-143

Table 1-31 GE service planning

Attribute NE1<->NE3

Source NE NE1

Source board-port 4-EGT2-1

Source timeslot VC4-1 to VC4-4

Source VCTRUNK VCTRUNK1

Bound bandwidth 4 x VC4

LCAS Start

Sink NE NE3

Sink board-port 4-EGT2-1

Sink timeslot VC4-1 to VC4-4

Sink VCTRUNK VCTRUNK1

ASON trail group The group ID is 1

Member trail Four silver services from NE1-EGT2 to NE3-EGT2

Procedure

Step 1 In the Main Topology, right-click NE1 and choose NE Explorer from the shortcut menu.

Step 2 Select 4-EGT2 and set the interface parameters according to Table 1-31.

Step 3 In the Main Topology, right-click NE3 and choose NE Explorer from the shortcut menu.

Step 4 Select 4-EGT2 and set the interface parameters according to Table 1-31.

Step 5 Select four silver services from NE1-4-EGT2 to NE3-4-EGT2.

Step 6 In the NE Explorer, select NE1 and choose ASON > ASON Trail Group from the FunctionTree.

Step 7 Click Create, and enter the ID, name and distance difference of the ASON trail group. ClickApply.

Step 8 Select the created ASON trail group and click Add.

Step 9 Select the four created silver services and click OK.

----End



Issue 02 (2010-09-24)

1.13 Creating Services Between an ASON NE and aTraditional NE

A network can consist of ASON NEs and traditional NEs. This realizes end-to-end serviceconfiguration and management.

1.13.1 Creating a VC4 Service Between Traditional NEs that Cross an ASON DomainYou can create end-to-end VC4 services between traditional NEs that cross an ASON domain.

1.13.2 Creating a VC12 Service Between Traditional NEs that Cross an ASON DomainYou can create end-to-end VC12 services between traditional NEs that cross an ASON domain.

1.13.3 Creating a VC4 Service Between a Traditional NE and an ASON NEYou can create end-to-end VC4 services between traditional NEs and ASON NEs.

1.13.4 Creating a VC12 Service Between a Traditional NE and an ASON NEYou can create end-to-end VC12 services between traditional NEs and ASON NEs.

1.13.5 Creating a 1+1 VC12 Service Between a Traditional NE and an ASON NEYou can create end-to-end 1+1 VC12 services between traditional NEs and ASON NEs.

1.13.6 Creating a 1+1 VC4 Service Between a Traditional NE and an ASON NEThe 1+1 VC4 service can be configured between a traditional NE and an ASON NE.

1.13.7 Creating a 1+1 VC12 Service Between Traditional NEs That Cross an ASON DomainYou can create 1+1 VC12 services between traditional NEs that cross an ASON domain.

1.13.8 Creating a 1+1 VC4 Service Between Traditional NEs That Cross an ASON DomainYou can create 1+1 VC4 services between traditional NEs that cross an ASON domain.

1.13.1 Creating a VC4 Service Between Traditional NEs that Crossan ASON Domain

You can create end-to-end VC4 services between traditional NEs that cross an ASON domain.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l ASON NEs must be configured.

Service RequirementSee Figure 1-55. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.A VC4 service needs to be configured between NE5 and NE6. This service is required to be anunprotected service in the traditional network, but a silver service in the ASON network.



1-145

Figure 1-55 VC4 service requirement between traditional NEs

: ASON NE

: Traditional NE

NE1

NE2 NE3

NE4

NE6 NE5

VC4 VC4

Board ConfigurationFigure 1-56 shows how the boards are configured on NE1, NE2, NE3 and NE4.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

Figure 1-57 shows how the boards are configured on NE5 and NE6.



Issue 02 (2010-09-24)


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning

You can refer to Table 1-32 to plan a service.

Table 1-32 VC4 service planning between traditional NEs

Attribute NE6<->NE5

Source NE NE6

Source board-port 4-N1SL1-1

Source VC4 1

Sink NE NE5

Sink board-port 4-N1SL1-1

Sink VC4 1

Service route Automatically calculated by the system

ASON service type Silver

Traditional service type Unprotected

You can use the following two ways to create a VC4 service between traditional NEs that crossan ASON domain.

l Use the trail feature of the U2000 to directly create a VC4 service.



1-147

l Create a silver service within the ASON domain. Then create VC4 cross-connections onNE5 and NE6.

The following illustrates how to create such a VC4 trail in the first way.

Procedure


Step 2 Choose Create/Modify > Create Trail.

Step 3 Enter the service information as follows:

l Direction: Bidirectional

l Level: VC4

l Source: NE6-4-N1SL1-1(SDH-1)-VC4:1

l Sink: NE5-4-N1SL1-1(SDH-1)-VC4:1

Step 4 Check the SPC First check box. Click ASON Attributes Settings tab and choose the Silverprotection type.



Issue 02 (2010-09-24)

Step 5 Check the Activate the trail check box and click Apply. The system prompts that the operationwas successful. Click Close.

Step 6 In the SDH Trail Management window, click Filter and selectFilter All.

Step 7 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the detailedroute information of the VC4 trail that is created. You can also view the value of ASON-SDHTrail to check whether the ASON section of the ASON-SDH trail is successfully created.

Step 8 Choose Configuration > SDH ASON > ASON Trail Management from the main menu. Youcan view the ASON trail information.

----End

1.13.2 Creating a VC12 Service Between Traditional NEs that Crossan ASON Domain

You can create end-to-end VC12 services between traditional NEs that cross an ASON domain.


l ASON NEs must be configured.

Service Requirement

See Figure 1-58. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.A VC12 service needs to be configured between NE5 and NE6. This service is required to bean unprotected service in the traditional network, but a silver service in the ASON network.

Figure 1-58 VC12 service requirement between traditional NEs

: ASON NE

: Traditional NE

VC12 VC12

NE1

NE2 NE3

NE4

NE6 NE5

Board Configuration

Figure 1-59 shows how the boards are configured on NE1, NE2, NE3 and NE4.



1-149


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning




Issue 02 (2010-09-24)

Table 1-33 VC12 service planning between traditional NEs

Attribute NE6<->NE5 (VC12) NE6<->NE5 (VC4 server trail)

Source NE NE6 NE6

Source board-port 2-N1PQ1 6-N1SL16-1

Source VC4 - 1

Source VC12 1 -

Sink NE NE5 NE5

Sink board-port 2-N1PQ1 6-N1SL16-1

Source VC4 - 1

Sink VC12 1 -


ASON servicetype

Silver

Traditional servicetype

Unprotected

You can use the following three ways to create a VC12 service between traditional NEs thatcross an ASON domain.

l Use the trail feature of the U2000 to create a VC4 server trail first. Then create a VC12trail.

l Create a silver trail within the ASON domain. Then create VC12 cross-connections on NE5and NE6.

l Create a silver server trail within the ASON domain. Then create VC12 cross-connectionson NE5 and NE6, and create VC12 cross-connections for both ends of the ASON servertrail.


Procedure



Step 3 Enter the VC4 server trail information as follows:


l Level: VC4 Server Trail

l Source: NE6

l Sink: NE5



1-151



Step 6 In the SDH Trail Creation view, enter the VC12 trail information as follows:l Direction: Bidirectionall Level: VC12l Source: NE6-2-PQ1-1(SDH_TU-1)l Sink: NE5-2-PQ1-1(SDH_TU-1)


Step 8 In the SDH Trail Management window, click Filter and select Filter All.

Step 9 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the details ofthe VC4 server trail and the VC12 trail that are created. You can also view the value of ASON-SDH Trail to check whether the ASON section of the ASON-SDH trail is successfully created.


----End

1.13.3 Creating a VC4 Service Between a Traditional NE and anASON NE

You can create end-to-end VC4 services between traditional NEs and ASON NEs.


Service RequirementSee Figure 1-61. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.A VC4 service needs to be configured between NE1 and NE5. This service is required to be anunprotected service in the traditional network, but a silver service in the ASON network.

Figure 1-61 VC4 service requirement between traditional and ASON NEs

: ASON NE

: Traditional NE

VC4

VC4

NE1

NE2 NE3

NE4

NE6 NE5



Issue 02 (2010-09-24)

Board ConfigurationFigure 1-62 shows how the boards are configured on NE1,

Figure 1-62 Board configuration for NE1

FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

N1S

L1

Figure 1-63 shows how the boards are configured on NE2, NE3 and NE4.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16



1-153



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning


Table 1-34 VC4 service planning between traditional NE and ASON NE

Attribute NE1<->NE5

Source NE NE1


Source VC4 1

Sink NE NE5


Sink VC4 1


ASON service type Silver

Traditional service type Unprotected

You can use the following two ways to create a VC4 service between a traditional NE and anASON NE.



Issue 02 (2010-09-24)

l Use the trail feature of the U2000 to directly create a VC4 service.

l Create a silver service within the ASON domain. Then create VC4 cross-connections onNE5.


Procedure


Step 2 Choose Create/Modify > Create Trail.

Step 3 Enter the service information as follows:


l Level: VC4






1-155


Step 6 In the SDH Trail Management window, click Filter and selectFilter All.

Step 7 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the detailedroute information of the VC4 trail that is created. You can also view the value of ASON-SDHTrail to check whether the ASON section of the ASON-SDH trail is successfully created.


----End

1.13.4 Creating a VC12 Service Between a Traditional NE and anASON NE

You can create end-to-end VC12 services between traditional NEs and ASON NEs.


l ASON NEs must be configured.

Service Requirement

See Figure 1-65. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.A VC12 service needs to be configured between NE1 and NE5. This service is required to bean unprotected service in the traditional network, but a silver service in the ASON network.

Figure 1-65 VC12 service requirement between traditional and ASON NEs

: ASON NE

: Traditional NE

VC12

VC12

NE1

NE2 NE3

NE4

NE6 NE5

Board Configuration




Issue 02 (2010-09-24)


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

Figure 1-67 shows how the boards are configured on NE5 and NE6,


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning

You can refer to Table 1-35 and Table 1-36 to plan a service.



1-157

Table 1-35 Silver ASON server trail planning

Attribute NE1<->NE4

Source NE NE1

Sink NE NE4

Protection type Silver ASON server trail

Service Route Automatically calculated by the system

NOTE

You can query the board and timeslots occupied by the ASON server trail in the SDH ASON TrailManagement window after the server trail is created. The example illustrated in this section is based onthe assumption that NE1 occupies the first VC4 of 8-N2SL64-1, and NE4 occupies the first VC4 of 11-N2SL64-1.

Table 1-36 VC12 service planning for NE1, NE4 and NE5

Attribute NE5 Cross-Connection

NE1 Cross-Connection

NE4 Cross-Connection

Source board-port 2-PQ1 2-PQ1 12-N1SL16-1

Source VC4timeslot

- - 1

Source VC12timeslot

1 1 1

Sink board-port 6-N1SL16-1 8-N2SL64-1 11-N2SL64-1


Sink VC12timeslot

1 1 1

Service level VC12 VC12 VC12

Direction Bidirectional Bidirectional Bidirectional

Context

You can use the following two ways to create a VC12 service between a traditional NE and anASON NE.

l Use the trail feature of the U2000 to create a VC4 server trail first. Then create a VC12trail.

l Create a silver server trail between NE1 and NE4. Then create VC12 cross-connections onNE1, NE4 and NE5.




Issue 02 (2010-09-24)

Procedure



Step 3 Enter the VC4 server trail information as follows:l Direction: Bidirectionall Level: VC4 Server Traill Source: NE5l Sink: E1



Step 6 In the SDH Trail Creation view, enter the VC12 trail information as follows:l Direction: Bidirectionall Level: VC12l Source: NE5-2-PQ1-1(SDH_TU-1)l Sink: E1-2-PQ1-1(SDH_TU-1)



Step 9 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the detailedinformation of the VC4 server trail and the VC12 trail that are created. You can also view thevalue of ASON-SDH Trail to check whether the ASON section of the ASON-SDH trail issuccessfully created.


----End

1.13.5 Creating a 1+1 VC12 Service Between a Traditional NE andan ASON NE

You can create end-to-end 1+1 VC12 services between traditional NEs and ASON NEs.


Service RequirementSee Figure 1-68. NE1, NE2, NE3 and NE4 are ASON NEs. NE5 and NE6 are traditional NEs.A VC12 service needs to be configured between NE1 and NE5. The service is required to be anSNCP service.



1-159

The direction of the working service and protection service of the SNCP service between NE1and NE5 must be the same.

Figure 1-68 1+1 VC12 service requirement between traditional and ASON NEs

: ASON NE

: Traditional NE

VC12

VC12

NE1

NE2 NE3

NE4

NE6 NE5

: Working Trail: Protection trail

Board Configuration



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

Figure 1-70 shows how the boards are configured on NE5 and NE6,



Issue 02 (2010-09-24)


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning

You can refer to Table 1-37, Table 1-38, Table 1-39 and Table 1-40 to plan a service.

Table 1-37 Service planning for double silver ASON server trails


Source NE NE1 NE1

Sink NE NE4 NE3

Protection type Silver ASON server trail Silver ASON server trail

Table 1-38 SNCP service planning for NE5

Attribute Transmit Direction Receive Direction

Workingservice

Protectionservice

Workingservice

Protectionservice

Source board-port

2-PQ1 6-N1SL16-1 13-N1SL16-1

Source VC4timeslot

- 1

Source VC12timeslot

1 1



1-161


Workingservice

Protectionservice

Workingservice

Protectionservice

Sink board-port 6-N1SL16-1 13-N1SL16-1 2-PQ1

Sink VC4timeslot

1 -

Sink VC12timeslot

1 1

Service level VC12 VC12

Direction Unidirectional Unidirectional

NOTE

You can query the boards and timeslots occupied by the two ASON server trails in the SDH ASON TrailManagement window after the server trails are created. The example illustrated in this section is based onthe assumption that NE1 occupies the 64 VC4 of 7-N2SL64-1 and the first VC4 of 8-N2SL64-1.



Workingservice

Protectionservice

Workingservice

Protectionservice

Source board-port 2-PQ1 7-N2SL64-1 8-N2SL64-1

Source VC4timeslot

- 64 1

Source VC12timeslot

1 1


Sink VC4 timeslot 64 1 -

Sink VC12timeslot

1 1



NOTE

You can query the boards and timeslots occupied by the two ASON server trails in the SDH ASON TrailManagement window after the server trails are created. The example illustrated in this section is based onthe assumption that NE3 occupies the 64 VC4 of 7-N2SL64-1, and NE4 occupies the first VC4 of 11-N2SL64-1.



Issue 02 (2010-09-24)

Table 1-40 Service planning for NE3 and NE4

Attribute NE3 NE4

Source board-port 12-N1SL16-1 12-N1SL16-1

Source VC4 timeslot 1 1


Sink board-port 7-N2SL64-1 11-N2SL64-1

Sink VC4 timeslot 64 1



Direction Bidirectional Bidirectional

You can use the following two ways to create a 1+1 VC12 service between a traditional NE andan ASON NE.

l Use the trail feature of the U2000 to create two VC4 server trails first. Then create VC12trails.

l Create a silver ASON server trail between NE1 and NE4, and another silver ASON servertrail between NE1 and NE3. Associate the two silver ASON server trails. Then create 1+1VC12 cross-connections on NE1 and NE5, and create VC12 cross-connections on NE3 andNE4.

The following illustrates how to create such a 1+1 VC12 trail in the first way.

Procedure



Step 3 Create a VC4 server trail that passing NE5, NE4, and NE1 in sequence.1. Enter the VC4 server trail information as follows:


l Level: VC4 Server Trail

l Source: NE5

l Sink: NE12. Check the SPC First check box. Click ASON Attributes Settings tab and select the

Silver protection type.3. Check the Activate the trail check box and click Apply.4. The system prompts that the operation was successful. Click Close.

Step 4 Create a VC4 server trail that passing NE5, NE3, and NE1 in sequence.1. Enter the VC4 server trail information as follows:



1-163

l Direction: Bidirectionall Level: VC4 Server Traill Source: NE5l Sink: NE1

2. Select the fiber between NE5 and NE3, and route the service from NE5 to NE3, and thento NE1.

3. Check the SPC First check box. Click ASON Attributes Settings and select the Silverprotection type. Click OK.

4. Check the Activate the trail check box and click Apply.5. The system prompts that the operation was successful. Click Close.

Step 5 Create a VC12 trail.1. In the SDH Trail Creation view, enter the VC12 trail information as follows:

l Direction: Bidirectionall Level: VC12l Source: NE5-2-PQ1-1(SDH_TU-1)l Sink: NE1-2-PQ1-1(SDH_TU-1)

2. Click the SNCP setting tab. Right-click NE5 and choose Set Dual-Fed Point from theshortcut menu.

3. Right-click NE1 and choose Set Selective-Receiving Point from the shortcut menu.4. Check the Activate the trail check box and click Apply.5. The system prompts that the operation was successful. Click Close.


Step 7 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the detailsabout the VC4 server trail and the VC12 trail that are created. You can also view the value ofASON-SDH Trail to check whether the ASON section of the ASON-SDH trail is successfullycreated.


----End

1.13.6 Creating a 1+1 VC4 Service Between a Traditional NE and anASON NE

The 1+1 VC4 service can be configured between a traditional NE and an ASON NE.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON software of the ASON NE must be of version 5.99.7.1 or later.

Service RequirementsAs shown in Figure 1-71, NE1, NE2, NE3, and NE4 are ASON NEs whereas NE5 and NE6 aretraditional NEs. A 1+1 VC4 service needs to be configured between NE5 and NE1. To implement



Issue 02 (2010-09-24)

the 1+1 protection, the service association is configured in the ASON domain and the SNCP isconfigured on the traditional NEs.

Figure 1-71 1+1 VC4 service requirement between a traditional NE and an ASON NE

VC4

VC4

NE1

NE2 NE3

NE4

: ASON NE

: Traditional NE

NE6 NE5

Board Configuration

Figure 1-72 shows the board configuration of NE1-NE4.

Figure 1-72 Board configuration of NE1-NE4

FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

N1S

L1



1-165

Figure 1-73 shows the board configuration of NE5 and NE6.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning

Table 1-41, Table 1-42, Table 1-43, and Table 1-44 show the service planning for the NEs.

Table 1-41 Service planning for the two silver ASON trails


Source NE NE1 NE1

Sink NE NE4 NE3

Protection type Silver trail Silver trail


Attribute Working Service Protection Service

Source board-port

6-N1SL16-1 13-N1SL16-1

Source VC4timeslot

1




Issue 02 (2010-09-24)


Sink VC4timeslot

1

Service level VC4

Direction Bidirectional

NOTE

The boards and timeslots that the two ASON trails occupy can be queried in the SDH ASON TrailManagement window only after the trails are created. In this example, the two ASON trails of NE1 occupythe 64th VC4 of the 7-N2SL64-1 and the first VC4 of the 8-N2SL64-1.



Source board-port

7-N2SL64-1 8-N2SL64-1

Source VC4timeslot

64 1

Sink board-port

4-N1SL1-1

Sink VC4timeslot

1

Service level VC4


NOTE

The boards and timeslots that the two ASON trails occupy can be queried in the SDH ASON TrailManagement window only after the trails are created. In this example, the ASON trail of NE3 occupiesthe 64th VC4 of the 7-N2SL64-1 and the ASON trail of NE4 occupies the first VC4 of the 11-N2SL64-1.


Attribute NE3 NE4








1-167

Attribute NE3 NE4


To create the 1+1 VC4 service between a traditional NE and an ASON NE, do as follows:

Create a silver ASON trail between NE1 and NE4 and create a silver ASON trail between NE1and NE3. Then, associate the two ASON trails. After that, create the 1+1 VC4 cross-connectionbetween NE1 and NE5, and create the VC4 cross-connection between NE3 and NE4.

Procedure



Step 3 In Basic information, enter the basic information of the ASON trail.For example, enter the following attributes:


l Type: ASON Trail

l Class: Silver


Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.For example, enter the following attributes:

l Revetrive Mode: Revertive (Select Non-Revetrive if the silver service is a non-revetriveservice. Select Scheduled revertive if the silver service is a scheduled revertive service.)

l Priority: 1

l Lockout: Unlocked

l Policy: Use existing trail whenever possible

Step 5 Set the source NE. In the right-hand topology, double-click the sink NE and select a slot, portand timeslot from the dialog box displayed. Click OK.For example, select the N1SL16 in slot 6, port 1, and timeslot 1.



NOTE


Step 8 Ensure that the trail information and routing restrictions are correct. Click Apply. If the creationis successful, a dialog box is displayed indicating that the operation is successful.



Issue 02 (2010-09-24)


Step 10 According to the service planning, repeat Steps 3-9 to create the silver service between NE1 andNE3.

Step 11 Click Cancel to return to the SDH ASON Trail Management window. Hold down the Ctrlkey and select the two silver trails to be associated. Right-click and choose Set Association fromthe shortcut menu. Click Yes in the Prompt dialog box that is displayed. After the two ASONtrails are associated, a dialog box is displayed indicating that the operation is successful.

Step 12 Select the NE1 icon in the Main Topology. Right-click and choose NE Explorer from theshortcut menu.

Step 13 Choose Configuration > SDH Service Configuration from the Function Tree.

Step 14 Click Create SNCP Service and enter the following SNCP service information about NE1:l Service Type: SNCPl Direction: Bidirectionall Level: VC4l Source Slot:

– Working Service: 7-N2SL64-1

– Protection Service: 8-N2SL64-1l Source Timeslot Range:

– Working Service: 64

– Protection Service: 1l Sink Slot: 4-N1SL1-1l Sink Timeslot Range: 1

Step 15 Click Apply. After the SNCP service is created, a dialog box is displayed indicating that theoperation is successful.

Step 16 According to the service planning, repeat Steps 12-15 to create the SNCP service of NE5. ?

Step 17 Enter the NE Explorer of NE3.

Step 18 Choose Configuration > SDH Service Configuration from the Function Tree.

Step 19 Click Create and enter the following SDH service information about NE3:l Direction: Bidirectionall Level: VC4l Source Slot: 12-N1SL16-1l Source Timeslot Range: 1l Sink Slot: 7-N2SL64-1l Sink Timeslot Range: 64l Activate Immediately: Yes

Step 20 Click OK. After the SDH service is created, a dialog box is displayed indicating that the operationis successful.



1-169

Step 21 According to the service planning, repeat Steps 17-20 to create the SDH service of NE4.

Step 22 Choose Service > SDH Trail > Search for SDH Trail from the main menu. Click Next oneafter another until the search is complete. Check whether the trail is created successfully in theSDH Trail Management window.

Step 23 Choose Service > SDH Trail > Manage SDH Trail from the main menu. Click Filter andchoose Filter All. Check the detailed information about the trail that is created.

Step 24 Choose Configuration > SDH ASON > ASON Trail Management from the main menu. Then,you can view the ASON trail information.

----End

1.13.7 Creating a 1+1 VC12 Service Between Traditional NEs ThatCross an ASON Domain

You can create 1+1 VC12 services between traditional NEs that cross an ASON domain.


l The ASON NE must be configured.

Service Requirement

In Figure 1-74, NE1, NE2, NE3 and NE4 are ASON NEs, and NE5 and NE6 are traditionalNEs. Configure a VC12 service between NE5 and NE6. The service requires SNCP protection.

Figure 1-74 1+1 VC12 service requirement between traditional NEs

VC12 VC12

NE1

NE2 NE3

NE4

NE6 NE5

: ASON NE

: Traditional NE

: Working Trail: Protection trail

Board Configuration

For the board configuration of NE1-NE4, refer to Figure 1-75.



Issue 02 (2010-09-24)


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning

Refer to Table 1-45, Table 1-46 and Table 1-47 for service planning.



1-171

Table 1-45 Planning of two silver ASON trails


Source NE NE1 NE2


Source VC4 1 1

Sink NE NE4 NE3


Sink VC4 1 1

Protection type Silver Silver

Service type ASON trail ASON trail

Trail type Working trail Protection trail

Table 1-46 SNCP service planning of NE5

Attribute Transmit direction Receive direction

Workingservice

Protectionservice

Workingservice

Protectionservice

Source board-port

2-PQ1 6-N1SL16-1 13-N1SL16-1

Source VC4timeslot

- 1

Source VC12timeslot

1 1


Sink VC4timeslot

1 -

Sink VC12timeslot

1 1





Issue 02 (2010-09-24)



Workingservice

Protectionservice

Workingservice

Protectionservice

Source board-port

2-PQ1 6-N1SL16-1 13-N1SL16-1

Source VC4timeslot

- 1

Source VC12timeslot

1 1


Sink VC4timeslot

1 -

Sink VC12timeslot

1 1



The two ways of creating 1+1 VC12 services between traditional NEs that cross an ASONdomain are as follows:

l Use the trail function of the U2000 to create two VC4 server trails and then create a VC12trail.

l Create a silver ASON trail between NE1 and NE4 and a silver ASON trail between NE2and NE3. Associate these two silver ASON trails. Configure VC12 cross-connections forNE5 and NE6.

The following procedure describes how to create 1+1 VC12 services between traditional NEsthat cross an ASON domain in the first way.

Procedure


Step 2 Select Create/Modify > Create Trail to create a VC4 server trail.

Step 3 Create a VC4 server trail from NE5, NE4, NE1 to NE6.1. Enter the information of the VC4 server trail.

For example:l Direction: Bidirectionall Level: VC4 server traill Source: NE5l Sink: NE6



1-173

2. Check the SPC First check box. Click ASON Attributes Settings. Select Silver as theprotection type and click OK.

3. Check the Activate the trail check box. Click Apply.4. A prompt is displayed indicating that the operation is successful. Click Close.

Step 4 Create a VC4 server trail from NE5, NE3, NE1 to NE6.1. Enter the information of the VC4 server trail.

For example:l Direction: Bidirectionall Level: VC4 server traill Source: NE5l Sink: NE6

2. Select the fiber between NE3 and NE2, and adjust the route to pass NE3 and NE2 and reachNE1.

3. Check the SPC First check box. Click ASON Attributes Settings tab and select Silver asthe protection type.

4. Check the Activate the trail check box. Click Apply.5. A prompt is displayed indicating that the operation is successful. Click Close.

Step 5 Create a VC12 trail.1. In the SDH Trail Creation View, enter the information of the VC12 trail.

For example:l Direction: Bidirectionall Level: VC12l Source: NE5-2-PQ1-1(SDH_TU-1)l Sink: NE6-2-PQ1-1(SDH_TU-1)

2. Click the SNCP setting tab. Right-click NE5 and choose Set Dual-Fed Point from theshortcut menu.

3. Right-click NE6 and choose Set Selective-Receiving Point from the shortcut menu.4. Check the Activate the trail check box. Click Apply.5. A prompt is displayed indicating that the operation is successful. Click Close.

Step 6 Choose Service > SDH Trail > Manage SDH Trail from the main menu. Click Filter andselect Filter All.

Step 7 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the details ofthe VC4 server trail and the VC12 trail that are created. View the value of ASON-SDH Trailto check whether the ASON section of the ASON-SDH trail is successfully created.

Step 8 Choose Configuration > SDH ASON > ASON Trail Management from the main menu. Viewthe information of the created ASON trail.

----End

1.13.8 Creating a 1+1 VC4 Service Between Traditional NEs ThatCross an ASON Domain

You can create 1+1 VC4 services between traditional NEs that cross an ASON domain.



Issue 02 (2010-09-24)

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON NE must be configured.

Service RequirementIn Figure 1-77, NE1, NE2, NE3 and NE4 are ASON NEs, and NE5 and NE6 are traditionalNEs. Configure a VC4 service between NE5 and NE6. The service requires SNCP protection.

Figure 1-77 1+1 VC4 service requirement between traditional NEs

VC4 VC4

NE1

NE2 NE3

NE4

NE6 NE5

: ASON NE

: Traditional NE

: Working Trail

: Protection trail

Board ConfigurationFor the board configuration of NE1-NE4, refer to Figure 1-78.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16



1-175



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L1

N1S

L16

Service Planning

Refer to Table 1-48, Table 1-49 and Table 1-50 for service planning.

Table 1-48 Planning of Two Silver ASON Trails


Source NE NE1 NE2


Source VC4 1 1

Sink NE NE4 NE3


Sink VC4 1 1

Protection type Silver Silver

Service type ASON trail ASON trail

Trail type Working trail Protection trail



Issue 02 (2010-09-24)



Workingservice

Protectionservice

Workingservice

Protectionservice

Source board-port

5-N1SL16-1 6-N1SL16-1 13-N1SL16-1

Source VC4timeslot

2 2

Sink board-port 6-N1SL16-1 13-N1SL16-1 5- N1SL16-1

Sink VC4timeslot

2 2





Workingservice

Protectionservice

Workingservice

Protectionservice

Source board-port

5- N1SL16-1 6-N1SL16-1 13-N1SL16-1

Source VC4timeslot

2 2

Sink board-port 6-N1SL16-1 13-N1SL16-1 5- N1SL16-1

Sink VC4timeslot

2 2



The two ways of creating 1+1 VC4 services between traditional NEs that cross an ASON domainare as follows:

l Use the trail function of the U2000 to create a VC4 service.l Create a silver ASON trail between NE1 and NE4 and a silver ASON trail between NE2

and NE3. Associate these two silver ASON trails. Configure VC4 cross-connections forNE5 and NE6.

The following procedure describes how to 1+1 VC4 services between traditional NEs that crossan ASON domain in the first way.



1-177

Procedure


Step 2 Select Create/Modify > Create Trail.

Step 3 Enter the information of the service.For example:


l Level: VC4



Step 4 Check the SPC First check box. Click ASON Attributes Settings tab and select Silver as theprotection type.

Step 5 Click the SNCP setting tab. Right-click NE5 and choose Set Dual-Fed Point from the shortcutmenu.

Step 6 Right-click NE6 and choose Set Selective-Receiving Point from the shortcut menu.

Step 7 Check the SPC First check box. Click ASON Attributes Settings tab and select Silver as theprotection type.

Step 8 Check the Activate the trail check box. Click Apply. A prompt is displayed indicating that theoperation is successful. Click Close.

Step 9 Choose Service > SDH Trail > Manage SDH Trail from the main menu. Click Filter andselect Filter All.

Step 10 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the details ofthe created VC4 trail. View the value of ASON-SDH Trail to check whether the ASON sectionof the ASON-SDH trail is successfully created.


----End

1.14 Accessing a Traditional Network to an ASON ThroughLinear MSP

When accessing services from a traditional network, to ensure that reliability of the accessedservices, you can create a 1+1 or 1:1 linear MSP at the edge of the traditional network and anASON domain. You can configure services in an ASON domain to the diamond , gold, and silverlevel.


l The ASON NE must be configured.



Issue 02 (2010-09-24)

Service Requirement

See Figure 1-80. If services exist between NE5 and NE3, a 1+1 linear MSP between NE5 andNE2 can ensure the reliability of services accessed from the source node NE5.

Figure 1-80 Accessing 1+1 linear MSP

1+1 Linear MS

: ASON NE

: Traditional NE

NE1

NE2 NE3

NE4

NE5

Board Configuration



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16




1-179


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

N1S

L16

For the board configuration of NE5, refer to Figure 1-83.

Figure 1-83 Board configuration of NE5

FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

L16

N1S

L16

N1S

L16

Service PlanningRefer to Table 1-51 for service planning.



Issue 02 (2010-09-24)

Table 1-51 Planning of Diamond Services Accessed Through 1+1 Linear MSP

Attribute NE5<->NE3

Source NE NE5


Source VC4 1

Sink NE NE3


Sink VC4 1

Service route The system automatically calculates the service route.

ASON service type Diamond

Traditional service type 1+1 linear MSP

NOTE

In this case, a 1+1 linear MSP is created between NE5 and NE2.

Procedure


Step 2 Select Create/Modify > Create Trail.

Step 3 Enter the information of the service.


l Level: VC4



Step 4 Check the SPC First check box. Click ASON Attributes Settings tab and select Diamond asthe protection type.

Step 5 Check the Activate the trail check box. Click Apply. A prompt is displayed indicating that theoperation is successful. Click Close.

Step 6 Choose Service > SDH Trail > Search for SDH Trail from the main menu. Click Next andclick Finish.

Step 7 Choose Service > SDH Trail > Manage SDH Trail from the main menu. View the details ofthe created VC4 trail.


----End



1-181

1.15 Accessing a Traditional Network to an ASON Networkby Using the SNCP Accessed Service

When a traditional network is accessed to an ASON network by using the SNCP accessedservice, the end-to-end SNCP is implemented for the service.

1.15.1 Creating the SNCP Service Between a Traditional NE and an ASON NETo configure the SNCP service between a traditional NE and an ASON NE, you need toconfigure the SNCP in the traditional network and configure the diamond service, gold service,silver service, copper service, or iron service in the ASON network.

1.15.2 Creating SNCP Services Between Traditional NEs That Cross an ASON DomainTo configure the SNCP services between traditional NEs that cross the ASON domain, you needto configure the SNCP in the traditional network and configure the diamond service, gold service,or silver service in the ASON network.

1.15.3 Querying the Information About the SNCP Accessed ServiceAfter the SNCP accessed service is created, you can query the relevant information, such as theaccess point and switching status.

1.15.4 Performing Switching at the SNCP Access EndAfter the SNCP accessed service is created, you can perform switching at the SNCP access end.

1.15.1 Creating the SNCP Service Between a Traditional NE and anASON NE

To configure the SNCP service between a traditional NE and an ASON NE, you need toconfigure the SNCP in the traditional network and configure the diamond service, gold service,silver service, copper service, or iron service in the ASON network.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON software of the ASON NE must be of version 5.99.7.1 or later.

Service RequirementsAs shown in Figure 1-84, a VC4 service is configured between NE5 and NE3. This VC4 serviceis configured with SNCP in the traditional network between NE5 and NE1 and is configured asa diamond service in the ASON network between NE1 and NE3.



Issue 02 (2010-09-24)

Figure 1-84 SNCP service between a traditional NE and an ASON NE

NE1

NE2

NE3

NE4

NE5ASONSDH

SNCP access

: ASON NE

: Traditional NE

NE6

NE7

Board ConfigurationFigure 1-85 shows the board configuration of NE1-NE4.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

N1S

LD4

N1S

L16



1-183



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

LD4

N1S

L16

Service Planning

Table 1-52, Table 1-53, and Table 1-54 show the service planning for the NEs.

Table 1-52 Planning of the diamond service between NE1 and NE3

Attribute NE1<->NE3

Source NE NE1

Source board-port 4-N1SLD4-1

Source timeslot 1

Sink NE NE3

Sink board-port 4-N1SLD4-1

Sink timeslot 1


SNCP Access Source: NE1-12-N1SL16-1-VC4:1


Rerouting attributes Revertive attribute Non-revertive



Issue 02 (2010-09-24)

Attribute NE1<->NE3

Rerouting trigger condition Initiates rerouting if any oneof the LSPs is interrupted.



Table 1-53 SNCP service planning for NE1 and NE5


Source board-port

6-N1SL16-1 12-N1SL16-1

Source VC4timeslot

1 1

Sink board-port

4-N1SLD4-1

Sink VC4timeslot

1

Service level VC4



Attribute NE6 NE7







To configure the SNCP service between a traditional NE and an ASON NE, do as follows:

Create a diamond ASON trail between NE1 and NE3 (NE1 and NE3 need to be configured withthe SNCP accessed service). Create the SNCP services on NE1 and NE5. Then, configure theSDH services on NE6 and NE7. Search the trail by using the trail search function.



1-185

Procedure

Step 1 To create the diamond service between NE1 and NE3, do as follows:1. Choose Configuration > SDH ASON > ASON Trail Management from the main menu.

2. Click Create to enter the creation wizard window.3. Enter the following basic information aboutthe trail in the Basic Information column:

l Name: NE1-NE3-ASON-Trail-0001l Type: ASON Traill Class: Diamondl Concatenation Type: Non-Concatenation

4. In the Routing Attributes field, set the rerouting attributes of the trail.l Revetrive Mode: Non-Revetrive (Select Revertive if the diamond service is a revertive

service. Select Scheduled revertive if the diamond service is a scheduled revertiveservice.)

l Priority: 1l Lockout: Unlockedl Trigger Condition: Reroute when one trail failsl Policy: Use existing trail whenever possiblel Rerouting Hold-off time: 0

5. Set the source NE. In the topology view on the right, double-click the sink NE and selectthe slot, port, and timeslot in the dialog box that is displayed. Click OK.

6. Set the sink NE. In the topology view on the right, double-click the sink NE and select theslot, port, and timeslot in the dialog box that is displayed. Click OK.

7. In the Basic Information column, set the working/protection route of the diamond service.l Select the Working option button. Right-click NE4 in the topology view on the right

and choose Set As Explicit Node from the shortcut menu.l Select the Protection option button. Right-click NE2 in the topology view on the right

and choose Set As Explicit Node from the shortcut menu.8. Add the source access point NE1-12-N1SL16-1-VC4:1 in the SNCP Access column.9. Ensure that the trail information and route restrictions are correct. Click Apply. After the

creation is complete, a dialog box is displayed indicating that the operation is successful.

Step 2 To configure the SNCP services of NE1 and NE5, do as follows:1. Select the NE1 icon in the Main Topology. Right-click and choose NE Explorer from the

shortcut menu.2. Choose Configuration > SDH Service Configuration from the Function Tree.3. Click Create SNCP Service and enter the following SNCP service information aboutNE1:

l Service Type: SNCPl Direction: Bidirectionall Level: VC4l Source Slot:

– Working Service: 6-N1SL16-1– Protection Service: 12-N1SL16-1



Issue 02 (2010-09-24)

l Source Timeslot Range:


– Protection Service: 1

l Sink Slot: 4-N1SLD4-1

l Sink Timeslot Range: 14. Click Apply. After the SNCP service is created, a dialog box is displayed indicating that

the operation is successful.5. According to the service planning, repeat Steps 1-4 to create the SNCP service of NE5.

Step 3 To configure the SDH services of NE6 and NE7, do as follows:1. Enter the NE Explorer of NE6.2. Choose Configuration > SDH Service Configuration from the Function Tree.3. Click Create and enter the following SDH service information aboutNE6:


l Level: VC4

l Source Slot: 12-N1SL16-1

l Source Timeslot Range: 1

l Sink Slot: 6-N1SL16-1

l Sink Timeslot Range: 1

l Activate Immediately: Yes4. Click OK. After the SDH service is created, a dialog box is displayed indicating that the

operation is successful.5. According to the service planning, repeat Steps 1-4 to create the SDH service of NE7.


Step 5 Choose Service > SDH Trail > Manage SDH Trail from the main menu. Click Filter andchoose Filter All. Then, you can view the detailed information aboutthe trail that is created.


----End

1.15.2 Creating SNCP Services Between Traditional NEs That Crossan ASON Domain

To configure the SNCP services between traditional NEs that cross the ASON domain, you needto configure the SNCP in the traditional network and configure the diamond service, gold service,or silver service in the ASON network.


l The ASON software of the ASON NE must be of version 5.99.7.1 or later.



1-187

Service RequirementsAs shown in Figure 1-87, a VC4 service is configured between NE5 and NE9. This VC4 serviceis configured with the SNCP in the traditional network between NE5 and NE1 and in thetraditional network between NE3 and NE9, and is configured as a diamond service in the ASONnetwork between NE1 and NE3.

Figure 1-87 SNCP services between traditional NEs that cross the ASON domain

NE1

NE2

NE3

NE4

NE5 NE9ASONSDH SDH

NE6

NE7

NE8

NE10

SNCP access

: ASON NE

: Traditional NE

SNCP access

Board ConfigurationFigure 1-88 shows the board configuration of NE1-NE4.


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

N2S

L64

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N2S

L64

N2S

L64

N1S

L16

N1S

LD4

N1S

L16



Issue 02 (2010-09-24)



FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

PIU

PIU

AU

X

D75

SD

75S

PQ

1P

Q1

GS

CC

GS

CC

EX

CS

A

EX

CS

A

N1S

L16

N1S

LD4

N1S

L16

Service Planning

Table 1-55, Table 1-56, and Table 1-57 show the service planning for the NEs.

Table 1-55 Planning of the diamond service between NE1 and NE3

Attribute NE1<->NE3

Source NE NE1

Source board-port 4-N1SLD4-1

Source timeslot 1

Sink NE NE3

Sink board-port 4-N1SLD4-1

Sink timeslot 1


SNCP access Source: NE1-12-N1SL16-1-VC4:1Sink: NE3-12-N1SL16-1-VC4:1



1-189

Attribute NE1<->NE3


Rerouting attributes Revertive attribute Non-revertive

Rerouting trigger condition Initiates rerouting if any oneof the LSPs is interrupted.



Table 1-56 SNCP service planning for NE1, NE3, NE5, and NE9


Source board-port

6-N1SL16-1 12-N1SL16-1

Source VC4timeslot

1 1

Sink board-port

4-N1SLD4-1

Sink VC4timeslot

1

Service level VC4


Table 1-57 Service planning for NE6, NE7, NE8, and NE10

Attribute NE


Source VC4 timeslot 1


Sink VC4 timeslot 1

Service level VC4




Issue 02 (2010-09-24)

To configure the SNCP services between traditional NEs that cross the ASON domain, do asfollows:

Create a diamond ASON trail between NE1 and NE3 (NE1 and NE3 need to be configured withthe SNCP accessed service). Create the SNCP services of NE1, NE3, NE5, and NE9. Then,configure the SDH services of NE6, NE7, NE8, and NE10. Search the trail by using the trailsearch function.

Procedure

Step 1 To create the diamond service between NE1 and NE3, do as follows:1. Choose Configuration > SDH ASON > ASON Trail Management from the main menu.2. Click Create to enter the creation wizard window.3. Enter the following basic information aboutthe trail in the Basic Information column:

l Name: NE1-NE3-ASON-Trail-0001l Type: ASON Traill Class: Diamondl Concatenation Type: Non-Concatenation

4. In the Routing Attributes field, set the rerouting attributes of the trail.l Revetrive Mode: Non-Revetrive (Select Revertive if the diamond service is a revertive

service. Select Scheduled revertive if the diamond service is a scheduled revertiveservice.)

l Priority: 1l Lockout: Unlockedl Trigger Condition: Reroute when one trail failsl Policy: Use existing trail whenever possiblel Rerouting Hold-off time: 0

5. Set the source NE. In the topology view on the right, double-click the sink NE and selectthe slot, port, and timeslot in the dialog box that is displayed. Click OK.

6. Set the sink NE. In the topology view on the right, double-click the sink NE and select theslot, port, and timeslot in the dialog box that is displayed. Click OK.

7. Set the working/protection route for the diamond service in the Basic Information column.l Select the Working option button. Right-click NE4 in the topology view on the right

and choose Set As Explicit Node from the shortcut menu.l Select the Protection option button. Right-click NE2 in the topology view on the right

and choose Set As Explicit Node from the shortcut menu.8. Enter the following SNCP access information in the SNCP Access column:

l Source: NE1-12-N1SL16-1-VC4:1l Sink: NE3-12-N1SL16-1-VC4:1

9. Ensure that the trail information and route restrictions are correct. Click Apply. After thecreation is complete, a dialog box is displayed indicating that the operation is successful.

Step 2 To configure the SNCP services of NE1, NE3, NE5, and NE9, do as follows:1. Select the NE1 icon in the Main Topology. Right-click and choose NE Explorer from the

shortcut menu.



1-191

2. Choose Configuration > SDH Service Configuration from the Function Tree.3. Click Create SNCP Service and enter the following SNCP service information aboutNE1:

l Service Type: SNCP


l Level: VC4

l Source Slot:

– Working Service: 6-N1SL16-1

– Protection Service: 12-N1SL16-1

l Source Timeslot Range:


– Protection Service: 1

l Sink Slot: 4-N1SLD4-1

l Sink Timeslot Range: 14. Click Apply. After the SNCP service is created, a dialog box is displayed indicating that

the operation is successful.5. According to the service planning, repeat Steps 1-4 to create the SNCP services of NE3,

NE5, and NE9.

Step 3 To configure the SNCP services of NE6, NE7, NE8, and NE10, do as follows:1. Enter the NE Explorer of NE6.2. Choose Configuration > SDH Service Configuration from the Function Tree.3. Click Create and enter the following SDH service information aboutNE6:


l Level: VC4

l Source Slot: 12-N1SL16-1

l Source Timeslot Range: 1

l Sink Slot: 6-N1SL16-1

l Sink Timeslot Range: 1

l Activate Immediately: Yes4. Click OK. After the SDH service is created, a dialog box is displayed indicating that the

operation is successful.5. According to the service planning, repeat Steps 1-4 to create the SDH services of NE7,

NE8, and NE10.


Step 5 Choose Service > SDH Trail > Manage SDH Trail from the main menu. Click Filter andchoose Filter All. Check the detailed information aboutthe trail that is created.


----End



Issue 02 (2010-09-24)

1.15.3 Querying the Information About the SNCP Accessed ServiceAfter the SNCP accessed service is created, you can query the relevant information, such as theaccess point and switching status.


l The unidirectional SNCP accessed service or bidirectional SNCP accessed service must becreated.

Procedure


Step 2 Select the SNCP accessed ASON service to be queried. Choose Maintenance > SNCP AccessedService.

Step 3 In SNCP Accessed Service, click Query Switching Status.

Step 4 After the query is performed successfully, a dialog box is displayed indicating that the operationis successful. Click to close the window.

----End

1.15.4 Performing Switching at the SNCP Access EndAfter the SNCP accessed service is created, you can perform switching at the SNCP access end.


l The unidirectional SNCP accessed service or bidirectional SNCP accessed service must becreated.



1-193

Procedure


Step 2 Select the ASON service for which switching needs to be performed at the SNCP access end.Choose Maintenance > SNCP Accessed Service.

Step 3 Select the access point where switching needs to be performed. Click Access PointSwitching.

Step 4 After switching is performed successfully, a dialog box is displayed indicating that the operationis successful. Click to close the window. Then, you can check that switching is alreadyperformed at the access point of Selective Receiving End.

----End

1.16 Managing UNI ServicesThe UNI is the standard interface that is used to connect the client equipment to the transportnetwork. When the UNI is used, the client equipment can dynamically request transportresources 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 thanconfiguring traditional services. UNI services improve the reliability and real-time performanceof the transport network so that burst data service requirements can be met and end-to-end UNIservices can be realized.

ContextThe ASON NE of the USP V100R005 version not support the UNI function.

1.16.1 Flow of Configuring UNI ServicesThe UNI (logical user-network interface) services are available in two types, namely, generalizedmulti-protocol label switching (GMPLS) UNI services and Optical Internetworking Forum(OIF) UNI services. The flow of configuring GMPLS UNI services is different from the flowof configuring OIF UNI services.

1.16.2 Enabling the UNI Feature of an ASON NEAfter an ASON NE is activated, the UNI services can be created only after the UNI feature isenabled.

1.16.3 Setting the Information About the GMPLS UNIThe GMPLS UNI is a standard UNI specified by the Internet Engineering Task Force (IETF).The GMPLS UNI inherits the normal LSP features, including the creating, deleting, protecting,and restoring the LSP.

1.16.4 Setting the Information About the OIF UNIThe OIF UNI is the standard UNI specified by the OIF. The OIF UNI has similar functions tothe GMPLS UNI.

1.16.5 Setting the UNI Access PolicyIn the case of an ASON network, the management strategy can be customized according therequirements of the UNI users. In addition, the user name and password, and the restrictions onthe service creation can be set according to the requirements of the UNI users.

1.16.6 Setting the Information About the GMPLS UNI LinkIn the case of the GMPLS UNI, you need to set the information such as the IP address.



Issue 02 (2010-09-24)

1.16.7 Setting the Information About the OIF UNI LinkIn the case of the OIF UNI, you need to set the information such as the transport network address(TNA).

1.16.8 Querying UNI ServicesYou can query the detailed information about the services that UNI users create, by using theU2000.

1.16.9 Deleting UNI ServicesYou can manually delete the services that the UNI users create, by using the U2000.

1.16.1 Flow of Configuring UNI ServicesThe UNI (logical user-network interface) services are available in two types, namely, generalizedmulti-protocol label switching (GMPLS) UNI services and Optical Internetworking Forum(OIF) UNI services. The flow of configuring GMPLS UNI services is different from the flowof configuring OIF UNI services.

In the case of UNI services, the ASON NE is generally considered as the UNI-N side. In thiscase, the flow of configuring the UNI services is shown in Figure 1-90.



1-195

Figure 1-90 Flow of configuring UNI services

Start

Create the OIF UNI link

Enable the UNI feature

The UNI-N automaticallycreates the UNI service

Create the GMPLS UNI linkDetermine the

signaling protocoltype

GMPLS

End

OIF

Configure the UNI

Configure the UNI accesspolicy

The UNI-C initiates theservice creation

Query the UNI services onthe T2000

1.16.2 Enabling the UNI Feature of an ASON NEAfter an ASON NE is activated, the UNI services can be created only after the UNI feature isenabled.

Prerequisitel The ASON feature must be enabled for the ASON NE.l You must be an NM user with "NE operator" authority or higher.



Issue 02 (2010-09-24)

Procedure

Step 1 Select NE1 in the Main Topology. Right-click and choose NE Explorer from the short-cutmenu.

Step 2 In the NE Explorer, select NE1 and then choose ASON > UNI Management from the FunctionTree. Click UNI Feature Management.

Step 3 Click Query to query the current status of the ASON feature.

Step 4 Set UNI Feature to Enabled.

NOTETo disable the ASON feature of NE1, set UNI Feature to Disabled.

Step 5 Click Apply.

Step 6 Repeat Steps 1-4 to enable the UNI feature of NE3.

----End

1.16.3 Setting the Information About the GMPLS UNIThe GMPLS UNI is a standard UNI specified by the Internet Engineering Task Force (IETF).The GMPLS UNI inherits the normal LSP features, including the creating, deleting, protecting,and restoring the LSP.


Service RequirementsAs shown in Figure 1-91, NE1 and NE3 are connected to two routers through the GMPLS UNIs.The information about the GMPLS UNI must be set for NE1 and NE3 so that the routers can becreated dynamically and the LSP link between the routers can be managed.



1-197

Figure 1-91 Setting the information about the GMPLS UNI

NE1

NE2

NE3

NE4

ASON NE

Router

GMPLS UNI GMPLS UNI

Board Configuration

Figure 1-92 shows the board configuration of NE1. Figure 1-93 shows the board configurationof NE3. The JL64 board in slot 1 of NE1 is connected to the T2SL64 board in slot 11 of NE3.The JL64 board in slot 6 of NE1 is connected to one router and the N1SL16 board in slot 13 ofNE3 is connected to the other router.


S1

JL64

S2

JL64

S5

JL64

S6

S4

S7

S8

S9

S3

S10

S11

S12

S13

S14

S15

S16

S17

S18

S19

S20

S21

S22

S23

S24

S25

S26

S27

S28

S29

S30

S31

S32

S55

JEO

W

S51

S33

S34

JSC

C

S48

S41

GXC

H

S42

S35

S47

S36

S58

S52

S56

S53

S49

S50

S54

S37

S38

S43

S44

S39

S40

S45

S46

S57

JPIU

EMPU

JSTG

JSC

C

Front Rear

GXC

HG

XCH

GXC

H

JPIU

JL64



Issue 02 (2010-09-24)


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

AU

X

T1E

XC

SA

T2S

L64

EO

WG

SC

CG

SC

C

PIU

PIU

S38

T1E

XC

SA

N1S

L16

N1S

L16

Service Planning

Procedure


Step 2 Click NE1 in the NE Explorer. Choose ASON > UNI Management > UNI interfaceManagement from the Function Tree.

Step 3 Select the board and port whose attributes need to be set. Set Interface Attributes to GMPLSUNI-N Attributes.



1-199

Step 4 Click Apply.

Step 5 Repeat Steps 1-4 to set attributes of the GMPLS UNI of NE3.

----End

1.16.4 Setting the Information About the OIF UNIThe OIF UNI is the standard UNI specified by the OIF. The OIF UNI has similar functions tothe GMPLS UNI.

Prerequisitel The ASON feature of the NEs is enabled.

l You must be an NM user with "NE operator" authority or higher.

Service Requirements

As shown in Figure 1-94, NE1 and NE3 are connected to two routers through the OIF UNIs.The information about the OIF UNI must be set for NE1 and NE3 so that the routers can becreated dynamically and the LSP link between the routers can be managed.

Figure 1-94 Setting the information about the OIF UNI

NE1

NE2

NE3

NE4

ASONNE

Router

OIF UNI OIF UNI



Issue 02 (2010-09-24)

Board ConfigurationFigure 1-95 shows the board configuration of NE1. Figure 1-96 shows the board configurationof NE3. The JL64 board in slot 1 of NE1 is connected to the T2SL64 board in slot 11 of NE3.The JL64 board in slot 5 of NE1 is connected to one router and the N1SL16 board in slot 12 ofNE3 is connected to the other router.


S1

JL64

S2

JL64

S5

JL64

S6

S4

S7

S8

S9

S3

S10

S11

S12

S13

S14

S15

S16

S17

S18

S19

S20

S21

S22

S23

S24

S25

S26

S27

S28

S29

S30

S31

S32

S55

JEO

W

S51

S33

S34

JSC

C

S48

S41

GXC

H

S42

S35

S47

S36

S58

S52

S56

S53

S49

S50

S54

S37

S38

S43

S44

S39

S40

S45

S46

S57

JPIU

EMPU

JSTG

JSC

C

Front Rear

GXC

HG

XCH

GXC

H

JPIU

JL64


FAN FANFAN

S1

S2

S3

S4

S5

S6

S7

S8

S9

S10

S11

S12

S13

S14

S15

S16

S17

S18

S27

S19

S20

S21

S22

S23

S24

S25

S26

S37

S29

S30

S31

S32

S33

S34

S36

S35

S28

AU

X

T1E

XC

SA

T2S

L64

EO

WG

SC

CG

SC

C

PIU

PIU

S38

T1E

XC

SA

N1S

L16

N1S

L16



1-201

Service Planning

Procedure


Step 2 Click NE1 in the NE Explorer. Choose ASON > UNI Management > UNI interfaceManagement from the Function Tree.

Step 3 Select the board and port whose attributes need to be set. Set Interface Attributes to OIF UNI-N Attributes.

Step 4 Click Apply.

Step 5 Repeat Steps 1-4 to set attributes of the OIF UNI of NE3.

----End

1.16.5 Setting the UNI Access PolicyIn the case of an ASON network, the management strategy can be customized according therequirements of the UNI users. In addition, the user name and password, and the restrictions onthe service creation can be set according to the requirements of the UNI users.


otherprops="u2klct;lct"The ASON feature of the NEs is enabled.

Procedure


Step 2 Click NE1 in the NE Explorer. Choose ASON > UNI Management > UNI Access PolicyManagement from the Function Tree.

Step 3 Click the UNI Access Policy Management tab. Click Create. Enter the information about theUNI access policy in the Create UNI Access Policy Management dialog box that is displayed.Set the following information:



Issue 02 (2010-09-24)

l User: szhwl password: nwsoftl Color: 0l Maximum Bandwidth(M): 10000l Minimum Service Creation Interval: 30

Step 4 Click Apply.

Step 5 Repeat Steps 1-4 to set the UNI access policy of NE3.

----End

1.16.6 Setting the Information About the GMPLS UNI LinkIn the case of the GMPLS UNI, you need to set the information such as the IP address.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON feature of the NEs is enabled.l The GMPLS UNI must be configured.

Procedure


Step 2 Click NE1 in the NE Explorer. Choose ASON > UNI Management > IP AddressManagement of GMPLS UNI Link from the Function Tree.

Step 3 Click Create. Set the link information for the GMPLS UNI in the Create GMPLS UNI Linkwindow.Set the following information:



1-203

l Board: 6-JL64l Port: 1(SDH-1)l Local IP Address: 129.0.0.13l Subnet Mask: 255.255.255.0l Remote Router ID: 1.1.1.16l Remote IP Address: 129.0.0.16

Step 4 Click Apply.

Step 5 Repeat Steps 1-4 to set the information about the GMPLS UNI link of NE3.

----End

1.16.7 Setting the Information About the OIF UNI LinkIn the case of the OIF UNI, you need to set the information such as the transport network address(TNA).

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The OIF UNI must be configured.l The ASON feature of the NEs is enabled.

Procedure


Step 2 Click NE1 in the NE Explorer. Choose ASON > UNI Management > TNA AddressManagement from the Function Tree.



Issue 02 (2010-09-24)

Step 3 Click Create. Set the link information for the OIF UNI in the Create OIF UNI LinkAddress window.Set the following information:l Board: 5-JL64l Port: 1(SDH-1)l TNA Address: 129.1.1.13

Step 4 Click Apply.

Step 5 Repeat Steps 1-4 to set the information about the OIF UNI link of NE3.

----End

1.16.8 Querying UNI ServicesYou can query the detailed information about the services that UNI users create, by using theU2000.


Procedure

Step 1 Choose Configuration > SDH ASON > UNI Trail Management from the main menu.

Step 2 In the Filter window, select the domain, source NE, and sink NE according to the requirements.Click Filter.



1-205

----End

1.16.9 Deleting UNI ServicesYou can manually delete the services that the UNI users create, by using the U2000.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The UNI services must be configured.

Procedure

Step 1 Choose Configuration > SDH ASON > UNI Trail Management from the main menu.

Step 2 In the Filter window, select the domain, source NE, and sink NE according to the requirements.Click Filter.

Step 3 Select the service that needs to be deleted. Right-click and choose Deactivate from the short-cut menu.

Step 4 After the service is deactivated, a dialog box is displayed, indicating that the operation issuccessful. Click Close.

Step 5 Select the service that is deactivated in Step 3. Right-click and choose Delete from the short-cutmenu.



Issue 02 (2010-09-24)

Step 6 After the service is deleted, a dialog box is displayed, indicating that the operation is successful.Click Close.

----End

1.17 Managing the OVPN Customers and OVPN ServicesIn the case of the OVPN, an ASON network is shared by multiple operators. When multipleoperators need to share an ASON network, you can allocate different TE link resources for eachoperator. Each operator can use and manage its own TE link resources and ASON services.

1.17.1 Enabling OVPN Function of ASON NEThe optical virtual private network (OVPN) function can be used only when the OVPN functionis enabled for all the NEs in the ASON domain. The OVPN function of the ASON NEs iscontrolled through the license of the NMS. The OVPN function of the ASON NEs can be enabledonly if the license of the NMS supports the OVPN function.

1.17.2 Creating NM User for OVPN CustomerTo ensure that each OVPN customer can manage its own resources and services, an independentNM user needs to be created for each OVPN customer.

1.17.3 Creating an OVPN CustomerBefore the resources are allocated for different OVPN customers, the corresponding OVPNcustomers need to be created on the NMS.

1.17.4 Allocating TE Links for OVPN CustomersEach OVPN customer can use only the allocated TE links to create services. The timeslots inthe TE links allocated for each OVPN customer should be planned properly according to theactual situations before the services are configured.

1.17.5 Creating OVPN ServicesThe OVPN services may be diamond services, gold services, silver services, copper services,or iron services.

1.17.6 Querying the TE Link Resources of the OVPN CustomersAfter the TE link resources are allocated for the OVPN customers, you can query the TE linkresources of each OVPN customer.



1-207

1.17.7 Querying the Services of the OVPN CustomersAfter the ASON services are created for the OVPN customers, you can query the ASON servicesof each OVPN customer.

1.17.1 Enabling OVPN Function of ASON NEThe optical virtual private network (OVPN) function can be used only when the OVPN functionis enabled for all the NEs in the ASON domain. The OVPN function of the ASON NEs iscontrolled through the license of the NMS. The OVPN function of the ASON NEs can be enabledonly if the license of the NMS supports the OVPN function.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The license of the NMS must support the OVPN function.

CAUTIONThe 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 SDH ASON Topology Management window, select the domain for which the OVPNfunction needs to be enabled. Set OVPN Enable Status of all the NEs in this domain toEnabled.

Step 3 Click Apply. A dialog box is displayed indicating that the operation is successful.

----End

1.17.2 Creating NM User for OVPN CustomerTo ensure that each OVPN customer can manage its own resources and services, an independentNM user needs to be created for each OVPN customer.

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



Issue 02 (2010-09-24)

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.11 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_User1l Password: osninfo123l Confirm password: osninfo123l For the other parameters, adopt the default values.

4. Click OK.

Step 3 Add the NM user OVPN_NM_User1 into Operator Group.



1-209

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_user14. 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.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.1l 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.17.3 Creating an OVPN CustomerBefore the resources are allocated for different OVPN customers, the corresponding OVPNcustomers need to be created on the NMS.

Prerequisitel You must be an NM user with "NE administrator" authority or higher.



Issue 02 (2010-09-24)

l The OVPN function must be enabled for the ASON NEs.l The NM users of the OVPN customers must be created.

CAUTIONTo facilitate management, it is recommended that each NM user should correspond to an OVPNcustomer.

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



1-211

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 inthe right list, right-click, select Authorize to User.

2. In the Customer Authorize Management windows, choose the Available Users. Forexample, OVPN_NM_User1.

3. Click OK to complete the setting.

----End

1.17.4 Allocating TE Links for OVPN CustomersEach OVPN customer can use only the allocated TE links to create services. The timeslots inthe TE links allocated for each OVPN customer should be planned properly according to theactual situations before the services are configured.

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

NOTE

When you partition the TE links on the MSP ring for OVPN customers, ensure that the timeslots of eachsection are consistent.

Procedure


Step 2 In the TE Link window, select the TE link that needs to be partitioned. Click PartitionResource.

TIP

You can select multiple TE links to be partitioned, by holding down the Ctrl key and clicking the targetTE links.

Step 3 In the Partition Resource window, select the TE link that needs to be partitioned. Double-clickOVPN Customer that corresponds to the specific timeslot and set the OVPN customer.



Issue 02 (2010-09-24)

Step 4 Click Apply. A dialog box is displayed indicating that the operation is successful.

Step 5 Optional: After the TE link resources are allocated, select a TE link and right-click Copy.

Step 6 Optional: Select another TE link to copy the previously selected TE link to. Right-click andchoose Paste from the shortcut menu.

Step 7 Then, a dialog box is displayed indicating that the operation is successful. Close the window.

Step 8 Optional: Click Synchronize and select a TE link. Then, you can check the TE link allocationin the OVPN Customer Information window on the lower left.

----End

1.17.5 Creating OVPN ServicesThe OVPN services may be diamond services, gold services, silver services, copper services,or iron services.


l The TE link resources must be allocated for the OVPN customers.

l There must be NM users who use the OVPN resources.

Service Requirements

As shown in Figure 1-97, the four NEs are ASON NEs. A 155 Mbit/s OVPN silver serviceneeds to be configured for the OVPN1 customer between NE1 and NE3.



1-213

Figure 1-97 OVPN service requirementsNE1

NE2

NE3

NE4

：ASON NE： LSP

Board ConfigurationAccording to the service requirements, the NEs can be configured with the boards as shown inFigure 1-98.


Service PlanningThe OVPN services are planned according to the service requirements. Table 1-58 provides theservice planning information.



Issue 02 (2010-09-24)

Table 1-58 OVPN service planning

Attribute NE1<->NE3

Source NE NE1


Source timeslot 1

Sink NE NE3


Sink timeslot 1


OVPN customer OVPN1

SNCP access None


Rerouting attribute Revertive Mode Automatically Revertive


NOTE

Before you create the OVPN services, ensure that the TE link resources are already allocated for the OVPNcustomers.

Procedure



Step 3 In Basic information, enter the basic information of the ASON trail.For example, enter the following attributes:l Name: NE1-NE3-ASON-Trail-0003l Type: ASON Traill Class: Silverl Concatenation Type: Non-Concatenationl OVPN Customer: OVPN1

Step 4 In the Routing Attributes field, enter the rerouting attributes of the trail.For example, enter the following attributes:l Revetrive Mode: Revertive (Select Non-Revetrive if the silver service is a non-revertive

service. Select Scheduled revertive if the silver service is a scheduled revertive service.)l Priority: 2



1-215

l Lockout: Unlockedl WTR Time(s): 600l Policy: Use existing trail whenever possible

Step 5 Set the source NE. In the right-hand topology, double-click the sink NE and select a slot, portand timeslot from the dialog box displayed. Click OK.For example, select the 7-N2SL64-1.



NOTE


Step 8 Select the Activate check box to deliver the created trails to the NE side, thus ensuring that thetrails are in the Activate state.





----End

1.17.6 Querying the TE Link Resources of the OVPN CustomersAfter the TE link resources are allocated for the OVPN customers, you can query the TE linkresources of each OVPN customer.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The TE link resources must be allocated for the OVPN customers.

Procedure


Step 2 Click Filter. Enter the filtering information in the Filter dialog box.An example is provided as follows:l Domain: ASON



Issue 02 (2010-09-24)

l Source NE: Alll Sink NE: Alll OVPN Customer: OVPN1

Step 3 Click Filter. Then, the NMS returns the information about the queried TE link resources of theOVPN customer.

----End

1.17.7 Querying the Services of the OVPN CustomersAfter the ASON services are created for the OVPN customers, you can query the ASON servicesof each OVPN customer.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l The ASON services must be created for the OVPN customers.

Procedure


Step 2 Click Filter. In the Filter dialog box, select Select OVPN Customer.

Step 3 Select the OVPN customer whose ASON services need to be queried. Click OK.



1-217

Step 4 In the Filter dialog box, click Filter All. Click Yes in the dialog box that is displayed.

Step 5 The NMS returns the query result.

----End

1.18 Importing and Exporting DataThe existing ASON network may not be optimum, so we can use the OptiX Modeling and DesignSystem (MDS) to optimize the network. You can import the ASON data on the U2000 to theMDS, 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 settingsto NEs to optimize the existing ASON network.

1.18.1 Exporting Data from U2000 to MDSYou can export ASON data from the U2000 to the MDS, and use the MDS to plan the existingASON network according to the imported data.

1.18.2 Importing Data from MDS to U2000You can use the MDS to plan ASON data, import the data from the MDS to the U2000, and thenuse the U2000 to optimize the existing ASON network.

1.18.1 Exporting Data from U2000 to MDSYou can export ASON data from the U2000 to the MDS, and use the MDS to plan the existingASON network according to the imported data.

Prerequisitel You must be an NM user with "NE operator" authority or higher.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.



Issue 02 (2010-09-24)

Procedure

Step 1 Choose Administration > Back Up/Restore NMS Data > Import/Export Script File fromthe 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 Filefrom 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 OperationDirectory 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.18.2 Importing Data from MDS to U2000You can use the MDS to plan ASON data, import the data from the MDS to the U2000, and thenuse the U2000 to optimize the existing ASON network.

Prerequisitel You must be an NM user with "NE operator" authority or higher.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 fromthe 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 Filefrom the Script File Type drop-down list.

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 withthe directory in the MDS.



1-219

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 promptedand then click OK.

Step 8 A progress bar is displayed and a prompt is displayed indicating that the operation is successful.

Step 9 Click Close and the Select an Option dialog box is displayed.

Step 10 Select ASON Trail Information in SDH DOMAIN and click OK.

Step 11 A progress bar is displayed and a prompt is displayed indicating that the operation is successful.Click Close.

----End

1.19 Managing Control Plane Alarms and PerformanceEvents

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 thresholdbased on actual requirements.

1.19.1 Querying Control Plane AlarmsFor maintenance purposes, you can query the current alarms or history alarms that specifiedtrails generate on the control plane, to learn whether there are any faults on the control plane.

1.19.2 Setting the Severity of Control Plane AlarmThe control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control linkalarm, and control channel alarm. Users can set the severity of the control plane alarms asrequired.

1.19.3 Setting the Auto-Report Status of the Control Plane AlarmThe control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control linkalarm, and control channel alarm. Users can set the auto report status of the control plane alarmsas required.

1.19.4 Suppressing Control Plane AlarmsThe control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control linkalarm, and control channel alarm. Users can suppress the specific control plane alarms asrequired.

1.19.5 Suppressing Control Plane Alarm EventsUsers can suppress control plane alarms at the service layer if required.

1.19.6 Querying the Performance of the Control PlaneUsers can view the current and history performance data of the control plane. In this manner,users can monitor the performance of the ASON Trail.

1.19.7 Monitoring the Control Plane PerformanceThe control plane performance monitoring involves SDH ASON NE performance monitoring,SDH ASON trail performance monitoring, SDH ASON TE Link performance monitoring andcontrol channel performance monitoring. The control plane performance monitor status defaultsto be disabled. Users can enable the monitoring function if required so that they can discoverand handle problems at the earliest time.



Issue 02 (2010-09-24)

1.19.8 Setting the Auto-Report Status of the Control Plane Performance DataThe control plane performance is monitored on a 24-hour basis. The performance is not reportedautomatically by default. Users can enable the auto-report function if required. The control planeperformance monitoring involves SDH ASON NE performance monitoring, SDH ASON trailperformance monitoring, SDH ASON TE Link performance monitoring, and control channelperformance monitoring.

1.19.9 Setting the Control Plane Performance ThresholdWhen an NE detects that a certain performance value exceeds the specified threshold, the NEreports a performance threshold crossing event. Set the performance threshold for every SDHASON trail properly based on the requirements. In this way, the performance of every SDHASON trail trail can be monitored.


PrerequisiteYou must be an NM user with "NE monitor" authority or higher.

Procedure

Step 1 To query networkwide alarms, see 2.2.2 Querying Network-Wide Alarms. In the window forviewing the current alarms, click Filter.

NOTE

You can choose other navigation path.

Choose Fault > Browse Current Alarm from the main menu.

Step 2 In the Filter dialog box displayed, select Alarm Name check box. Click , the SelectAlarm dialog box displayed.

Step 3 In the option alarm tree, select Control Plane Alarms, click , select all of the controlplane alarms, click OK.

Step 4 Click OK. The alarms generated on the control plane are then displayed in the alarm list.

----End

1.19.2 Setting the Severity of Control Plane AlarmThe control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control linkalarm, and control channel alarm. Users can set the severity of the control plane alarms asrequired.


l An ASON NE must be created and the NE data must be uploaded.



1-221

ContextThis section considers suppressing the NE alarms as an example to describe how to set theseverity of control plane alarms.

ProcedureStep 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-downmenu.

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.19.3 Setting the Auto-Report Status of the Control Plane AlarmThe control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control linkalarm, and control channel alarm. Users can set the auto report status of the control plane alarmsas required.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l An ASON NE must be created and the NE data must be uploaded.

ProcedureStep 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 fromthe 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 thecurrent alarms.

----End

1.19.4 Suppressing Control Plane AlarmsThe control plane alarms consist of NE alarm, ASON trail alarm, TE link alarm, control linkalarm, and control channel alarm. Users can suppress the specific control plane alarms asrequired.



Issue 02 (2010-09-24)


ContextThis section considers suppressing the NE alarms as an example to describe how to suppresscontrol plane alarms.

ProcedureStep 1 In the NE Explorer, click the NE and then choose ASON > Control Plane Alarm

Suppression > NE Alarm Suppression

Step 2 Event names and corresponding suppression status displays in the right windows.

Step 3 Double-click Suppression Status, and then choose Suppressed from the drop-down menu.NOTE

In the case of OptiX OSN 9560, choose Status.

Step 4 Click Apply to submit the alarm suppression setting.

Step 5 Optional: After the operation is complete, click Query to view the suppression status of thecurrent alarms.

----End

1.19.5 Suppressing Control Plane Alarm EventsUsers can suppress control plane alarms at the service layer if required.



Step 2 Choose an ASON trail from the list, click Alarm and then select Control Plane AlarmSuppression.

Step 3 Double click Suppression Status in the ASON Trail Alarm Suppression interface, and thenchoose Suppressed from the drop-down menu.

Step 4 Click Apply to activate the alarm suppression setting.

Step 5 Click Query to query the control plane alarm suppression status of the SDH ASON trail.

----End




1-223

Prerequisitel You must be an NM user with "NE monitor" authority or higher.l An ASON NE must be created and the NE data must be uploaded.l The NE Performance Monitoring Time is enabled.

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

NOTEThe 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 PlanePerformance > Current Performance from the Function Tree to view the currentperformance data.

2. Optional: Choose ASON > Control Plane Performance > History Performancefrom the Function Tree to view the history performance data.

3. Optional: Click Filter by Template and select Open from the drop-down list. In theOpen dialog box, select a template for filtering performance data and click Open.Certain performance events are filtered and you can view the performance.


4. Click Query.

----End

1.19.7 Monitoring the Control Plane PerformanceThe control plane performance monitoring involves SDH ASON NE performance monitoring,SDH ASON trail performance monitoring, SDH ASON TE Link performance monitoring andcontrol channel performance monitoring. The control plane performance monitor status defaultsto be disabled. Users can enable the monitoring function if required so that they can discoverand handle problems at the earliest time.


This section considers enabling the NE monitoring function as an example to describe how toenable or disable monitoring of the control plane performance.



Issue 02 (2010-09-24)

Procedurel In the case of NG SDH and OCS series equipment.

1. In the NE Explorer, click the NE and then choose ASON > Control PlanePerformance > Monitor Status.

2. Click the SDH ASON NE tab. Double-click Monitoring Status of the requiredperformance event, and then choose Enabled from the drop-down menu.

3. Click Apply to submit the setting.4. Optional: Click Query to view the control plane monitoring status of ASON NE.

l In the case of OptiX OSN 9560.1. In the NE Explorer, click the NE and then choose ASON > Control Plane

Performance > Performance Monitor Status.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.3. Click Apply to submit the setting.4. Optional: Click Query to view the control plane monitoring status of ASON NE.

----End

1.19.8 Setting the Auto-Report Status of the Control PlanePerformance Data

The control plane performance is monitored on a 24-hour basis. The performance is not reportedautomatically by default. Users can enable the auto-report function if required. The control planeperformance monitoring involves SDH ASON NE performance monitoring, SDH ASON trailperformance monitoring, SDH ASON TE Link performance monitoring, and control channelperformance monitoring.


This section considers enabling the auto-report function as an example to describe how to enableor disable auto report of the control plane performance data.


1. In the NE Explorer, click the NE and then choose ASON > Control PlanePerformance > Auto-Reporting Status. options.

2. Click the SDH ASON NE tab. Double-click Auto-Reporting Status of the requiredperformance event, and then choose Enabled from the drop-down menu.

3. Click Apply to submit the setting.



1-225

4. Optional: Click Query to view the auto-report status of the control plane of the ASONNE.

l In the case of OptiX OSN 9560.1. In the NE Explorer, click the NE and then choose ASON > Control Plane

Performance > Performance Monitor Status.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.

3. Click Apply to submit the setting.4. Optional: Click Query to view the auto-report status of the control plane of the ASON

NE.

----End

1.19.9 Setting the Control Plane Performance ThresholdWhen an NE detects that a certain performance value exceeds the specified threshold, the NEreports a performance threshold crossing event. Set the performance threshold for every SDHASON trail properly based on the requirements. In this way, the performance of every SDHASON trail trail can be monitored.



1. In the NE Explorer, click the NE and then choose ASON > Control PlanePerformance > Performance Threshold.

2. In the SDH ASON Trail list on the interface, select the desired SDH ASON trail.3. In the list, double-click the Threshold Value field of the SDH ASON trail, and then

enter a new performance threshold value.4. Click Apply to submit the setting.5. Optional: Click Query to query the control plane performance threshold of the SDH

ASON trail.l In the case of OptiX OSN 9560.

1. In the NE Explorer, click the NE and then choose ASON > Control PlanePerformance > SDH Performance Threshold.

2. In the SDH ASON Trail list on the interface, select the desired SDH ASON trail.



Issue 02 (2010-09-24)

3. In the list, double-click the Threshold Value field of the SDH ASON trail, and thenenter a new performance threshold value.

4. Click Apply to submit the setting.5. Optional: Click Query to query the control plane performance threshold of the SDH

ASON trail.

----End



1-227

2 Routine Maintenance for an ASON Network

About This Chapter

The routine maintenance for an ASON network involves service monitoring and resourcemonitoring. Service monitoring enables maintenance personnel to determine the affected scopeat the earliest time when a fault occurs on the network. Then, the maintenance personnel candetermine the rectification measures based on the characteristics of the fault and the currentservice status. In this manner, the maintenance personnel can determine the health status of theservices promptly and minimize the impact on the services. Resource monitoring enablesmaintenance personnel eliminate potential faults on the network in real time and thus eliminatethe severe potential risks in routine maintenance. Rectifying the resource anomalies in real timecan help to improve the network resources utilization rate, promote the service survivability,discover the bottleneck of the network resources in advance, take capacity expansion measurespromptly, and ensure healthy operation of the network all the time.

This chapter focuses on the routine maintenance of the ASON control plane. For the routinemaintenance of the transport plane, refer to the following documents.l OptiX OSN 9500 Intelligent Optical Switching System Routine Maintenancel OptiX OSN 7500 Intelligent Optical Switching System Routine Maintenancel OptiX OSN 3500 Intelligent Optical Transmission System Routine Maintenancel OptiX OSN 3500 II Intelligent Optical Transmission System Routine Maintenancel OptiX OSN 2500 Intelligent Optical Transmission System Routine Maintenancel OptiX OSN 1500 Intelligent Optical Transmission System Routine Maintenance

2.1 Precautions for Routine MaintenanceThe precautions for routine maintenance of an ASON network are described.

2.2 Routine Maintenance ItemsThe normal running of an ASON network depends on effective routine maintenance. Thepurpose of routine maintenance is to find and solve problems in time.

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management 2 Routine Maintenance for an ASON Network


2-1

2.1 Precautions for Routine MaintenanceThe precautions for routine maintenance of an ASON network are described.

Switching off LaserBefore switching off the laser at an optical port with an ASON service, transfer the ASON serviceto another trail. If the optical port has no service, lock the ASON trail that pass the optical portby setting the Rerouting Lockout attribute of the trail to Locked.

CAUTIONDo not frequently switch on or switch off the laser at an optical port that has a TE link.

Looping Back Optical PortWhen fiber jumpers are used to loopback an optical port that has ASON services, first transferthe ASON services to other ASON trails. If the optical port has no services, lock out the ASONtrails that pass the optical port by setting the Rerouting Lockout attribute of the trails toLocked.

Inserting or Removing FibersBefore inserting or removing fibers at an optical port with ASON services, transfer the ASONservices to other trails. If the optical port has no actual services, lock the ASON trails that passthe optical port by setting the Rerouting Lockout attribute of the trails to Locked.

CAUTIONl 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 BoardThe ASON software runs on the SCC board and saves network data in real time. Hence, the NEcannot run normally if the SCC board is absent for a long time. Before you replace an SCCboard, 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.

CAUTIONDo not reset the SCC board when there are ASON services being created, deleted, or rerouted.

2 Routine Maintenance for an ASON NetworkiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management


Issue 02 (2010-09-24)

Precautions for Maintaining the U2000 SystemDo not exit the U2000 when it is normally running, though this operation does not interrupt thenetwork services. When the U2000 is shut down, however, it cannot monitor the ASON softwareand 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 ItemsThe normal running of an ASON network depends on effective routine maintenance. Thepurpose of routine maintenance is to find and solve problems in time.

2.2.1 Periodically Refreshing the ASON informationEvery time an ASON NE is rerouted, the service route and link information change. You needto periodically refresh the ASON information to keep consistency between the data on theU2000 and the data on the NE.

2.2.2 Querying Network-Wide AlarmsYou can query the NE alarms in the entire network to find abnormal alarms timely.

2.2.3 Querying ASON Trail AlarmsFor maintenance purposes, you can query the current alarms or history alarms of a specifiedASON trail to learn the failures of an ASON network.


2.2.5 Querying Control Link AlarmsFor 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 AlarmsFor maintenance purposes, you can query the current alarms or history alarms of a TE link tolearn the failures of an ASON network.

2.2.7 Creating a Performance Filtering TemplateBy creating and modifying performance filtering template, a network maintainer can quicklyview the specific performance events of specific NEs when the maintainer enables theperformance monitoring next time.


2.2.9 Querying Abnormal ASON EventsDuring routine maintenance, you need to query abnormal events to check the running status ofthe network.

2.2.10 Checking the Running Status of ASON TrailsDuring routine maintenance, you must periodically check the running status of ASON trails tocheck whether the trail attributes are changed and to ensure the normal running of the trails.

2.2.11 Checking TE LinksDuring routine maintenance, you need to know the resource utilizations of TE links. First, checkthe number of TE links in the entire network. Then, check the remaining resources of each TE



2-3

link. The number of TE links should be consistent with the number of TE links that are actuallyused. The remaining resources of the TE links on two adjacent nodes on one fiber should be thesame.

2.2.12 Checking Control LinksDuring routine maintenance, you need to check the number and status of control links.

2.2.13 Checking the Activation Status of ASON ServicesThe activation status of ASON services should be periodically checked to ensure the normalrunning of ASON services.

2.2.1 Periodically Refreshing the ASON informationEvery time an ASON NE is rerouted, the service route and link information change. You needto periodically refresh the ASON information to keep consistency between the data on theU2000 and the data on the NE.

PrerequisiteYou must be an NM user with "NE maintainer" authority or higher.

Background InformationYou can choose the information that you want to refresh periodically, which includes TE linkinformation, ASON trail status, and ASON trail route information. The ASON trail statusincludes ASON trail channel status, SLA compliant, rerouting attributes, information ofassociated services, and information of preset restoration trail.

ProcedureStep 1 Choose Administration > Task Schedule > Task Management from the main menu.

Step 2 Create a task to periodically refresh the ASON information.1. Click New and the New Task is displayed.2. Set the task type to Refresh ASON Information, select the Run Type and enter the task

name. Click Next.3. Set the Time Setting or the Period Setting. Click Next.4. Select the information that you want to refresh periodically and click Finish. A scheduled

task is successfully created.

Step 3 Select the task whose Task Type is Refresh ASON Information.

Step 4 Select the Run At Once in the shortcut menu. And you can view the parameters in the list toknow the running status.

Step 5 Optional: Double-click the scheduled task to modify the parameters of the task.

----End

2.2.2 Querying Network-Wide AlarmsYou can query the NE alarms in the entire network to find abnormal alarms timely.




Issue 02 (2010-09-24)

Background Informationl 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-widecritical alarms. The Networkwide Critical Alarm window is displayed. The critical alarms thatrequire high attention include the following:l R_LOSl R_LOFl EXT_SYNC_LOSl HARD_BADl SUBCARD_ABNl 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 networkwidemajor alarms. The major alarms that require high attention include the following:l MS_AIS, TU_AISl B2_EXC, B3_EXCl POWER_ABNORMALl APS_INDIl TEMP_OVERl TPS_ALM

Step 3 Click (yellow) at the upper right of the U2000 user interface to view the networkwideminor alarms. The minor alarms that require high attention include the following:l B1_EXC, B1_SD, B2_SD, B3_SDl MS_RDI, HP_RDIl J0_MM

Step 4 Optional: Right-click an ASON-related alarm and choose Alarm-Affected Original Routefrom the shortcut menu. In the SDH ASON Trail Management window displayed, you canview the detailed information of the affected original route.

----End

2.2.3 Querying ASON Trail AlarmsFor maintenance purposes, you can query the current alarms or history alarms of a specifiedASON trail to learn the failures of an ASON network.



2-5

Prerequisitel You must be an NM user with "NE monitor" authority or higher.l An ASON trail must be created.

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 fromthe 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 OriginalRoute from the shortcut menu. In the SDH ASON Trail Management window displayed, youcan view the information of the affected original route.

Step 5 Optional: Right-click an alarm related to an ASON trail, and choose Browse Alarm-AffectedASON Trail from the shortcut menu. In the SDH ASON Trail Management window displayed,you can view the information of the affected ASON trail.

NOTE

When you right-click an alarm, the Browse Alarm-Affected ASON Trail shortcut menu item is availableonly if the alarm affects an SDH ASON trail.

Step 6 Optional: Right-click an alarm related to a TE link, and choose Browse Alarm-Affected TELink from the shortcut menu. In the SDH TE Link Management window displayed, you canview the information of the affected TE link.

NOTE

When you right-click an alarm, the Browse Alarm-Affected TE Link shortcut menu item is availableonly if the alarm affects a TE link.

----End



Procedure

Step 1 To query networkwide alarms, see 2.2.2 Querying Network-Wide Alarms. In the window forviewing 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 SelectAlarm dialog box displayed.

Step 3 In the option alarm tree, select Control Plane Alarms, click , select all of the controlplane alarms, click OK.

Step 4 Click OK. The alarms generated on the control plane are then displayed in the alarm list.

----End

2.2.5 Querying Control Link AlarmsFor maintenance purposes, you can query the current alarms or history alarms of a control link,to learn whether the control link is faulty.


Procedure


Step 2 In the control link list, select a control link and click Alarms. Choose Current Alarms fromthe 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 HistoryAlarms 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 AlarmsFor maintenance purposes, you can query the current alarms or history alarms of a TE link tolearn the failures of an ASON network.

Prerequisitel You must be an NM user with "NE monitor" authority or higher.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-downmenu.

Step 3 Optional: In the link list, select a TE link and click Alarms. Choose History Alarms from thedrop-down menu.

Step 4 The current alarms of the TE link are displayed in a new window.



2-7

If you choose History Alarms from the drop-down menu, the history alarms of the TE link aredisplayed.

----End

2.2.7 Creating a Performance Filtering TemplateBy creating and modifying performance filtering template, a network maintainer can quicklyview the specific performance events of specific NEs when the maintainer enables theperformance monitoring next time.


ContextThe Filter by Template function involves the following windows: viewing the SDHperformance, 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 NEsor boards on NEs. In filter criteria area of the table on the right of the window, set parametersfor filtering performance events.

Step 2 On the lower portion of the window for viewing performance, click Filter by Template andselect 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 notto be renamed.

----End


Prerequisitel You must be an NM user with "NE monitor" authority or higher.l An ASON NE must be created and the NE data must be uploaded.l The NE Performance Monitoring Time is enabled.

Procedurel Query the data on a network basis.

1. Choose Performance > Browse Control Plane Performance from the main menu.



Issue 02 (2010-09-24)

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.


6. Click Query.l Query the data on a station basis.

1. In the NE Explorer, click the NE and then choose ASON > Control PlanePerformance > Current Performance from the Function Tree to view the currentperformance data.

2. Optional: Choose ASON > Control Plane Performance > History Performancefrom the Function Tree to view the history performance data.

3. Optional: Click Filter by Template and select Open from the drop-down list. In theOpen dialog box, select a template for filtering performance data and click Open.Certain performance events are filtered and you can view the performance.


4. Click Query.

----End

2.2.9 Querying Abnormal ASON EventsDuring routine maintenance, you need to query abnormal events to check the running status ofthe network.


Background InformationThe following events require high attention:l Failed iron trial restoration eventl ASON trail deletion event on failed restoration.l Failed ASON trial restoration eventl ASON trail rerouting eventl ASON trial downgrade eventl Control channel down event



2-9

CAUTIONViewing abnormal events is important for maintaining an ASON network. Hence, view abnormalevents periodically.

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 andGenerated Time of the desired events, you can also enter the remarks contained by the eventsif necessary.

NOTE

Check the Event name check box, click the behind the Event name textbox, in the displayedSelect 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

ResultThe list displays the detailed information of some abnormal events.

Table 2-1 Abnormal Events List

Item Description

Failed ASON Trail Restoration Event The revertive ASON trail fails to revert.

ASON Trail Deletion Event upon FailedRestoration

After the revertive ASON trail fails to revert,it is deleted.

Failed Iron Service Restoration Event After MS switching, the iron service fails tobe restored.

ASON Trail Rerouting Event The ASON trail reroutes.

Failed ASON Trail Rerouting Event The ASON trail fails to reroute.

2.2.10 Checking the Running Status of ASON TrailsDuring routine maintenance, you must periodically check the running status of ASON trails tocheck whether the trail attributes are changed and to ensure the normal running of the trails.




Issue 02 (2010-09-24)

Procedurel Perform the following steps to check the running status of all ASON trails on the topology:


2. In the trail list, right-click the ASON trails that you want to view and chooseDetails 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.

4. Click OK.

l Perform the following steps to check the running status of all ASON trails in the NEExplorer:

1. In the NE Explorer, select an NE and choose ASON > ASON Trail from the FunctionTree.

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 theintermediate node, With this node as sink, and Passing through this node.

3. Click Query.

----End



2-11

2.2.11 Checking TE LinksDuring routine maintenance, you need to know the resource utilizations of TE links. First, checkthe number of TE links in the entire network. Then, check the remaining resources of each TElink. The number of TE links should be consistent with the number of TE links that are actuallyused. The remaining resources of the TE links on two adjacent nodes on one fiber should be thesame.


Procedurel Perform the following steps to check all the TE links on the topology:

1. Choose Configuration > SDH ASON > TE Link Management from the main menu.

2. Click Synchronize. In the Synchronize dialog box displayed, choose Domain.

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 TElinks. View the , Bandwidth Usage, and Downgrade Type of each TE link.

– Control Plane Alarm Status: If there is any alarm, handle it immediately.

– Bandwidth Usage: Displays the utilization of the bandwidth resources. Theinformation is displayed in different colors according to the value of theThreshold 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 bottomof 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 ManagementProtocol from the Function Tree.

2. Click the LMP TE Link or LMP Component Link tab.

3. Click Query.

l Perform the following steps to view the OSPF protocol status of TE links in the NEExplorer:

1. In the NE Explorer, select an NE and choose ASON > OSPF ProtocolManagement from the Function Tree.

2. Click the OSPF TE Link or OSPF Component Link tab.

NOTEFor OptiX OSN 9560, the tabs is OSPF SDH TE link or OSPF Component Link.

3. Optional: Select a desired unit in Bandwidth Units.

NOTEThere are four bandwidth units, which are VC4, VC3, VC12, and kbit/s.

4. Click Query.

----End



Issue 02 (2010-09-24)

2.2.12 Checking Control LinksDuring routine maintenance, you need to check the number and status of control links.


Procedurel Perform the following steps to query the status and number of control links in the entire

network:1. Choose Configuration > SDH ASON > Control Link Management from the main

menu.2. Click Synchronize. The information in the list is refreshed.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

Management from the Function Tree.2. Click the OSPF Control Link tab.3. To query the status and number of control links on the NE, click Query.

----End

2.2.13 Checking the Activation Status of ASON ServicesThe activation status of ASON services should be periodically checked to ensure the normalrunning of ASON services.



2-13


Procedure

Step 1 Choose Configuration > SDH ASON > ASON Trail Management from the main menu. ClickFilter in SDH ASON Trail Management.

Step 2 Select Inactive from Filter to filter all the inactive ASON services.

Step 3 If an inactive ASON service exists, perform the following steps.1. In SDH ASON Trail Management, view the sink node of the service, and then delete the

service. If the service exists in SDH Trail Management, delete the service.2. Open the NE Explorer of the sink node. Choose ASON > Advanced Maintenance from

the Function Tree.3. Select the Query ASON Trail dropdown list in the ASON Signaling Maintenance tab.

Select With this node as sink in the dropdown list, and then click Query to check viewthe inactive ASON service.

4. Right-click the service to choose Downgrade ASON Signaling. Then, downgrade theservice from the sink node, and thus the service is converted to a traditional service.

5. Choose Service > SDH Trail > Search for SDH Trail from the main menu. Search thetrail.

6. The trail search is complete. Choose Service > SDH Trail > Manage SDH Trail from themain menu. View the searched traditional service. Right-click the service to chooseUpgrade to ASON. Select the proper service attribute in the displayed Upgrade toASON window, and then click OK. Thus, the upgrade is complete.

----End



Issue 02 (2010-09-24)

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 linkfault, service creation failure, service interruption and NE database fault.

3.1 Handling Link FailuresLink failure contains control channel failure, component link failure, and TE link failure.

3.2 Handling the Failure in Creating TrailsCauses for the trail creation failure are various.

3.3 Handling Trail InterruptionCauses for the trail interruption are various.

3.4 Disaster RecoveryIf the dual SCC boards of an NE becomes faulty, or the NE is in the installation status, or thedatabase of the NE is lost, you can restore the data on the NE in the ASON NE recovery wizard.

iManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management 3 Handling ASON Network Failures


3-1

3.1 Handling Link FailuresLink failure contains control channel failure, component link failure, and TE link failure.

3.1.1 Handling Impassable Control ChannelsControl channels are classified into control channels inside and outside fibers. The controlchannels inside fibers use D4-D12 bytes to transmit the check information. The control channelsoutside fibers are seldom used.

3.1.2 Handling Impassable Component LinksOnly when control channels between adjacent nodes are available in an ASON network, cancomponent links be verified.

3.1.3 Handling Impassable TE LinksOnly when control channels between adjacent nodes are available in an ASON network can TElinks be checked.

3.1.4 Handling Downgraded TE LinksIf a TE link is downgraded, it indicates that the status of the TE link is normal before.

3.1.1 Handling Impassable Control ChannelsControl channels are classified into control channels inside and outside fibers. The controlchannels inside fibers use D4-D12 bytes to transmit the check information. The control channelsoutside fibers are seldom used.

Common Causes for Impassable Control ChannelsPossible causes for impassable control channels are listed below.l The opposite NE is a traditional NE.l The LMP protocol of the optical interface is manually disabled.l No DCC is allocated to the optical interface.l The ECC is not passable because of bit errors.l Alarms such as R_LOS or R_LOF are raised at the optical interface.l The board is not in position.

Procedure

Step 1 Check the type of the opposite NE. If the opposite NE is a traditional NE, the control channelof the local NE is not passable.

Step 2 Check the state of the LMP protocol at the optical interface. If the state of the protocol at theoptical interface is Disabled, it indicates that the LMP protocol is manually disabled. Enablethe LMP protocol at the optical interface again.

Step 3 Check DCC state of the optical interface. If no DCC is allocated to the optical interface, shutdown the DCC of the optical interface that does not require ECC communication.

NOTE

Only the DCC of the optical interface that does not require ECC communication can be shut down. Makesure that ECC communication is not necessary for the optical interface before shutting down the DCC.

3 Handling ASON Network FailuresiManager U2000 Unified Network Management SystemOperation Guide for SDH ASON Network Management


Issue 02 (2010-09-24)

Step 4 Check the bit errors of the optical interface. If there is any bit error, clear them.

Step 5 Check the alarms at the optical interface. If there are alarms such as R_LOS and R_LOF, clearthe alarms.

Step 6 Check the state of the physical board.

l If the physical board is not in position, remove it and then insert it again. Add the logicalboard correctly.

l If the physical board is faulty, replace it.

Step 7 Disable LMP of the optical interfaces at the two ends of the control channel. Then enable LMPof the optical interfaces at the two ends of the control channel.

----End

3.1.2 Handling Impassable Component LinksOnly when control channels between adjacent nodes are available in an ASON network, cancomponent links be verified.

Common Causes for Impassable Component Links

Common causes for impassable component links are listed below.

l Control channels are not passable.

l Logical boards are not added.

l Logical boards do not match physical boards.

Procedure

Step 1 Check the status of the control channel between the remote and local ends. If the control channelis not passable, troubleshoot the fault.

Step 2 Check whether the logical boards and physical boards at the remote and local ends are consistent.If logical boards do not match physical boards, add new logical boards or replace the physicalboards.

----End

3.1.3 Handling Impassable TE LinksOnly when control channels between adjacent nodes are available in an ASON network can TElinks be checked.

Common Causes for Impassable TE Links

Common causes for impassable TE links are listed as follows:

l Control channels are impassable.

l The board software does not match with the NE software.

l Physical fibers are improperly connected.



3-3

ProcedureStep 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 faulton the control channel.

Step 2 Check the NE software and the board software. According to the mapping table, find the boardsoftware that is mapped with the NE software. If the NE software does not match with the boardsoftware, load the board software again.

Step 3 Check whether physical fibers are improperly connected. If the physical fibers are improperlyconnected, connect the fibers again.

Step 4 When you upgrade a pass-through node to an ASON node, change all services that pass throughthe node to other trails and, on the sources and sinks of the services and on this node, disableand enable the LMP protocol.

----End

3.1.4 Handling Downgraded TE LinksIf a TE link is downgraded, it indicates that the status of the TE link is normal before.

Common Causes for Downgraded TE LinksCommon 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.

ProcedureStep 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.l If you query from the SDH 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 TrailsCauses for the trail creation failure are various.

3.2.1 Handling the Failure of Route ComputationIf the route computation fails during the ASON service creation, an error message is displayedon the U2000.

3.2.2 Handling the Failure to Allocate LabelsIf label allocation fails during ASON service creation, an error message is displayed on theU2000.

3.2.3 Handling the Failure in Creating Services in Batches



Issue 02 (2010-09-24)

You can create ASON services in batches.

3.2.1 Handling the Failure of Route ComputationIf the route computation fails during the ASON service creation, an error message is displayedon the U2000.

Common Causes for Route ComputationCommon causes for the route computation are listed as follows.l The network resource is insufficient.

– When you create a diamond service, the non-protection resource of the TE link is notsufficient.

– When you create a gold service, the working and non-protection resources of the TElink are not sufficient.

– When you create a silver service, the non-protection resource of the TE link is notsufficient.

– When you create a copper service, the non-protection resource of the TE link is notsufficient.

– When you create an iron service, the protection and non-protection resources of the TElink are not sufficient.

l The explicit links are not specified in a correct manner.– When you create a diamond service, the explicit link has no non-protection resources.– When you create a gold service, the explicit link only has protection resources.– When you create a silver service, the explicit link has no non-protection resources.– When you create a copper service, the explicit link has no non-protection resources.– When you create an iron service, the explicit link only has working resources.

l The explicit timeslot has been reserved.l The explicit nodes are not specified in a correct manner.

Procedure

Step 1 Check the CrankBack attempts. If the value of CrankBack is not 0, the system still returns afailure message after a rerouting is performed. It is recommended that you set the Crankback to0.

Step 2 Check the utilization of the network resource. If the network resource is not sufficient, add someresource and then create the ASON service.

Step 3 Check the reservation state of the designated link. If the designated link does not have availableresources, release the designated link.

Step 4 Check the reservation of explicit timeslots. If an explicit timeslot is reserved, specify anotherexplicit timeslot.

Step 5 Check whether the explicit nodes are arranged in the expected sequence. If not, an error isreported. In this case, specify multiple explicit nodes in the sequence you want.

Step 6 If the designated node does not have resources, release the designated node.

----End



3-5

3.2.2 Handling the Failure to Allocate LabelsIf label allocation fails during ASON service creation, an error message is displayed on theU2000.

Common Causes for the Failure to Allocate LabelsCommon causes for the failure to allocate labels are listed below.l The timeslot states are not consistent.l The timeslot is reserved at a single end.

Procedure

Step 1 Synchronize the cross-connection of the NE.1. Choose Configuration > SDH ASON > ASON Trail Management from the main menu.2. The Filter dialog box is displayed. Click Filter All, Incremental Filter or Secondary

Filter.NOTE

l If you need to filter all the ASON trails, click Filter All.l If you need to add to the list more ASON trails that match the requirement, click Incremental

Filter.l If you need to filter the ASON trails in the list, click Secondary Filter.

3. Click Synchronize, in the Synchronize dialog box displayed, set the Domain andAttributes.

NOTE

l Attributes: basic information, working state, SLA-compliant, rerouting attributes and associatedservices.

l You can also select one or more ASON trails, right-click and choose Synchronize from the shortcutmenu to synchronize the selected ASON trails. At this time, the synchronized attributes for the ASONtrails are consistent with the synchronization attributes that you set in the Synchronize window.

4. Choose Configuration > SDH ASON > ASON Topology Management from the mainmenu. Select the ASON domain that requires synchronization of cross-connection of NEs.Right-click all these NEs and choose Synchronize NE Cross-Connection.

Step 2 Check the reservation of explicit timeslots. If an explicit timeslot is reserved, specify anotherexplicit timeslot.

----End

3.2.3 Handling the Failure in Creating Services in BatchesYou can create ASON services in batches.



Issue 02 (2010-09-24)

Common causes for the failure to create services in batchThe batch creation of services fail due to the following causes.l Sufficient resources are not available.l The batch creation involves too many services.l The previous batch creation or optimization of services is still in progress.

Procedure

Step 1 Check the network resources.l If the network resources are not sufficient, create less number of services in a batch.l If the network resources are sufficient, check if the previous batch creation of services is

complete.

Step 2 After the previous batch service creation or the service optimization is complete, make anotherattempt to create the services in a batch.

----End

3.3 Handling Trail InterruptionCauses 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 thesource and sink ports for the interrupted trails.

2. Optimize the service trails to avoid the fault trails and restore the services.3. If the optimization fails , delete the service. You should re-create traditional SDH trails to

avoid faulty trails and restore the trails.4. After services are restored, collect the related data to find out the cause and handle the fault.

3.3.1 Determining Interrupted ServicesYou need to determine the interrupted services before restoring the services.

3.3.2 Troubleshooting Interruption of ServicesAfter determining the interrupted services, you can restore them.

3.3.1 Determining Interrupted ServicesYou need to determine the interrupted services before restoring the services.

PrerequisiteOne or more services are interrupted.

Procedure

Step 1 Choose Fault > Synchronize Networkwide Alarms from the main menu. Synchronize thenetwork-wide alarms.

Step 2 Choose Fault > Browse Current Alarm from the main menu.



3-7

Step 3 The dialog box is displayed, click OK, browse all of the alarms.

Step 4 Search the CP_SER_IN alarm in these alarms.

Step 5 Right-click the CP_SER_IN to choose Alarm-Affected ASON Trail. The SDH ASON TrailManagement is displayed. Thus, check the interrupted ASON trails.

----End

3.3.2 Troubleshooting Interruption of ServicesAfter determining the interrupted services, you can restore them.

PrerequisiteServices are interrupted.

Procedure

Step 1 In SDH ASON Trail Management, check Activation Status of the interrupted services. If theactivation state is Inactive, do as follows:1. Right-click the interrupted service to choose Deactivate. If the deactivation fails, proceed

to the next step. Right-click the interrupted service to choose Force to Deactivate.2. Right-click the interrupted service to choose Activate. If the activation succeeds, the fault

is rectified. If the activation fails, proceed to the next step.3. Select the interrupted service, and then click Maintenance to choose Optimize Route.

Optimize this service to other trails. If the optimization succeeds, the fault is rectified. Ifthe optimization fails, proceed to the next step.

4. According to the recorded information on the faulty services, create the traditional SDHservice for service restoration.

Step 2 If the activation state of the interrupted service is Active, check whether the TE link isinterrupted. If the TE link is interrupted, refer to 3.1.3 Handling Impassable TE Links formanagement. Otherwise, proceed to the next step.

Step 3 Check whether the boards that used for adding and dropping this service are in position. If not,insert the boards well.

----End

3.4 Disaster RecoveryIf the dual SCC boards of an NE becomes faulty, or the NE is in the installation status, or thedatabase of the NE is lost, you can restore the data on the NE in the ASON NE recovery wizard.

Prerequisitel You must be an NM user with "NM maintainer" authority or higher.l Log in to the U2000 in single user mode.l The hardware of the NE to be recovered is in the normal state, including dual control boards,

faulty boards, and optical fiber connections. The settings such as NE ID, IP address, andASON node ID must be the same as those before the fault occurs.



Issue 02 (2010-09-24)

l The communication between the U2000 and the NE to be recovered, and thecommunication between the U2000 and the other ASON NEs in the ASON domain are inthe normal state.

l The ASON feature at the NE side of the NE to be recovered is disabled.l OptiX OSN 9560 cannot support disaster recovery.

PrecautionsWhen recovering the ASON trail, this wizard also recovers the traditional data, such as staticservice and the multiplex section. In this case, you do not need to download the NE dataseparately.

l This function is applicable only to the fault recovery when a single SDH ASON NE databasefails or the dual control boards fail, and the NE cannot start.

l The data that is not synchronized to the U2000 before the fault occurs cannot be recovered.l Do not use this function on a normal NE. Otherwise, the NE or the service may become

abnormal.l All of the ASON NEs in the ASON domain to which the faulty NE belongs must support

the function.l Do not restart the U2000 after the NE failed, otherwise some data would not recover.

Procedure

Step 1 Choose Configuration > SDH ASON > Recover ASON NE from the main menu. Then, theASON NE Recovery Wizard-Step dialog box is displayed.

Step 2 Read the Function Description of the wizard carefully. Click Next.

Step 3 Please select the NE to be recovered from the NE list, and then click Next.

Step 4 Check whether the information of the NE to be restored is correct. If not, click back to modifythe information. After you confirm that the information is correct, click Next.

Step 5 After the NE data restoration is complete, the Prompt dialog box is displayed indicating thatthe data restoration is successful. Click OK.

Step 6 Check for the restoration result. Certain services may fail to be restored. Restore these servicesmanually. Click Close.

Step 7 In the displayed Prompt dialog box, click OK.

NOTE

It is recommended that you synchronize the data of the entire network after the NE data is restoredsuccessfully.

----End



3-9

OG for SDH ASON Network Management-(V100R002C01 02)[1]

Documents

Transcript of OG for SDH ASON Network Management-(V100R002C01 02)[1]