OG for RTN End-To-End Management-(V100R002C01 02)[1]

iManager U2000 Unified Network ManagementSystemV100R002C01

Operation Guide for RTN End-to-EndManagement

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 how to configure an RTN network by using the end-to-end function.

This document guides you to manage an RTN network by using the trail management function.

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 RTN End-to-End 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 System

Operation Guide for RTN End-to-End 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 RTN End-to-End Management About This Document


v

Contents

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

1 Managing RTN Protection Subnets........................................................................................1-11.1 Basic Concepts................................................................................................................................................1-3

1.1.1 Protection Subnet...................................................................................................................................1-31.1.2 Isolated Node..........................................................................................................................................1-3

1.2 Searching for Protection Subnets....................................................................................................................1-41.3 Configuring an MSP Ring...............................................................................................................................1-4

1.3.1 Creating an MS Ring Protection Subnet................................................................................................1-51.3.2 Checking Networkwide Multiplex Section Parameters.........................................................................1-71.3.3 Verifying MSP Protection Switching.....................................................................................................1-7

1.4 Configuring Linear MSP.................................................................................................................................1-91.4.1 Creating a Linear MS Protection Subnet................................................................................................1-91.4.2 Checking Networkwide Multiplex Section Parameters.......................................................................1-111.4.3 Verifying MSP Protection Switching...................................................................................................1-12

1.5 Creating an Path Protection Ring..................................................................................................................1-131.6 Configuring a Non-Protection Ring..............................................................................................................1-141.7 Configuring a Non-Protection Chain............................................................................................................1-151.8 Configuring DNI Protection..........................................................................................................................1-161.9 Configuring IF 1+1 Protection......................................................................................................................1-171.10 Configuring IF N+1 Protection...................................................................................................................1-181.11 Maintaining Protection Subnets..................................................................................................................1-19

1.11.1 Finding Protection Subnets................................................................................................................1-201.11.2 Querying Protection Subnet Resources..............................................................................................1-211.11.3 Collecting Statistics on the SDH Protection Subnet Resources.........................................................1-211.11.4 Checking MS Protection Switching Status........................................................................................1-221.11.5 Setting Protection Subnet Parameters................................................................................................1-221.11.6 Checking TPS Switching status.........................................................................................................1-231.11.7 Performing MSP Switching...............................................................................................................1-231.11.8 Performing SNCP Service Switching................................................................................................1-241.11.9 Adjusting the Capacity of an MSP Ring............................................................................................1-251.11.10 Adjusting the Capacity of a Linear MSP.........................................................................................1-261.11.11 Changing an NP Chain to a 1+1 Linear MSP..................................................................................1-261.11.12 Checking IF 1+1 Protection Switching Status.................................................................................1-29

iManager U2000 Unified Network Management SystemOperation Guide for RTN End-to-End Management Contents


vii

1.11.13 Checking IF N+1 Protection Switching Status................................................................................1-291.12 Deleting Protection Subnets........................................................................................................................1-291.13 Deleting Isolated Nodes..............................................................................................................................1-30

2 End-to-End RTN Management................................................................................................2-12.1 Managing SDH Trails.....................................................................................................................................2-2

2.1.1 Configuration Task Flow.......................................................................................................................2-32.1.2 Basic Concepts.......................................................................................................................................2-42.1.2.1 SDH Trail............................................................................................................................................2-52.1.2.2 Radio Trails.........................................................................................................................................2-72.1.2.3 Conflict Trail.......................................................................................................................................2-92.1.2.4 Trail Creation Method.......................................................................................................................2-102.1.2.5 Process for Creating a Trail...............................................................................................................2-122.1.2.6 Trail Protection Strategy...................................................................................................................2-152.1.2.7 Trail Resource Use Strategy..............................................................................................................2-172.1.2.8 Principles for Selecting Timeslots During the Trail Creation...........................................................2-172.1.2.9 Platinum Service Group....................................................................................................................2-192.1.3 Disabling a Fiber..................................................................................................................................2-202.1.4 Creating SDH Trails by Trail Search...................................................................................................2-212.1.4.1 Searching for SDH Trails..................................................................................................................2-212.1.4.2 Viewing Discrete Services................................................................................................................2-222.1.4.3 Discrete Service Causes and Handling Measures.............................................................................2-232.1.4.4 Setting the Remarks of a Discrete Service........................................................................................2-242.1.4.5 Activating and Deactivating Discrete Services.................................................................................2-262.1.4.6 Acknowledging or Unacknowledging Discrete Services..................................................................2-262.1.4.7 Deleting Discrete Services................................................................................................................2-272.1.5 Automatically Creating VC4 Trails.....................................................................................................2-282.1.5.1 Creating a Non-SNCP VC4 Trail......................................................................................................2-282.1.5.2 Creating an SNCP VC4 Trail............................................................................................................2-302.1.5.3 Verifying the SNCP Trail Protection Switching...............................................................................2-332.1.6 Automatically Creating VC12 and VC3 Trails....................................................................................2-332.1.6.1 Creating a VC4 Server Trail..............................................................................................................2-342.1.6.2 Creating a Non-SNCP VC12 or VC3 Trail.......................................................................................2-362.1.6.3 Creating an SNCP VC12 or VC3 Trail.............................................................................................2-382.1.6.4 Verifying the SNCP Trail Protection Switching...............................................................................2-412.1.7 Creating a Platinum Service Group......................................................................................................2-422.1.8 Bound Platinum Service Group............................................................................................................2-432.1.9 Creating an SDH Trail Manually.........................................................................................................2-442.1.10 Creating PDH Radio Trails................................................................................................................2-452.1.10.1 Creating a Link Server Trail............................................................................................................2-452.1.10.2 Creating a PDH Radio Trail............................................................................................................2-472.1.11 Creating SDH Radio Trails................................................................................................................2-492.1.11.1 Creating a VC4 Server Trail............................................................................................................2-49

ContentsiManager U2000 Unified Network Management System


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

Issue 02 (2010-09-24)

2.1.11.2 Creating an SDH Radio Trail..........................................................................................................2-512.1.12 Copying SDH Trails...........................................................................................................................2-522.1.13 Modifying an SDH Trail....................................................................................................................2-542.1.13.1 Modifying the Port/Timeslot/Route of an SDH Trail.....................................................................2-542.1.13.2 Modifying the SNC Service Control of SDH Trails.......................................................................2-552.1.13.3 Modifying Trail Names in Batches.................................................................................................2-562.1.13.4 Modifying the Trails in a Platinum Service Group.........................................................................2-572.1.14 Removing a Trail from a Platinum Service Group............................................................................2-572.1.15 Configuring Overhead Bytes of an SDH Trail...................................................................................2-582.1.15.1 Setting the Trace Byte.....................................................................................................................2-582.1.15.2 Setting the C2 Byte.........................................................................................................................2-602.1.15.3 Setting the V5 Byte.........................................................................................................................2-612.1.15.4 Setting the Overhead Termination..................................................................................................2-622.1.15.5 Setting Service Load Signals...........................................................................................................2-632.1.16 Changing Between SNCP and Non-SNCP Trails..............................................................................2-642.1.16.1 Changing a Non-SNCP Trail to an SNCP Trail..............................................................................2-642.1.16.2 Changing an SNCP Trail to a Non-SNCP Trail..............................................................................2-662.1.17 Enabling or Disabling VC4 Server Trails..........................................................................................2-662.1.17.1 Disabling VC4 Server Trails...........................................................................................................2-672.1.17.2 Enabling VC4 Server Trails............................................................................................................2-672.1.18 Joining and Splitting VC4 Server Trails............................................................................................2-682.1.18.1 Joining VC4 Server Trails...............................................................................................................2-692.1.18.2 Splitting a VC4 Server Trail............................................................................................................2-702.1.19 Service Authorization Management...................................................................................................2-712.1.19.1 Specifying a Customer for a Service...............................................................................................2-722.1.19.2 Authorizing a Customer to a U2000 User.......................................................................................2-732.1.19.3 Authorizing a Trail to a U2000 User...............................................................................................2-742.1.19.4 Modifying Trail Authorization Information....................................................................................2-742.1.20 Viewing SDH Trails...........................................................................................................................2-752.1.20.1 Viewing SDH Trail Details.............................................................................................................2-752.1.20.2 Viewing the Use Information of a VC4 Server Trail......................................................................2-762.1.20.3 Viewing Relevant Client Trails.......................................................................................................2-772.1.20.4 Viewing the Optical Power for the Trails.......................................................................................2-772.1.20.5 Viewing the Status of the Fiber Break on an SDH Trail.................................................................2-782.1.20.6 Viewing Fiber Information of a Trail..............................................................................................2-792.1.21 Maintaining SDH Trails.....................................................................................................................2-792.1.21.1 Locking or Unlocking an SDH Trail...............................................................................................2-802.1.21.2 Activating or Deactivating an SDH Trail........................................................................................2-812.1.21.3 Setting a Loopback for a Trail.........................................................................................................2-822.1.21.4 Performing the Protection Switching for a Single SNCP Trail.......................................................2-842.1.21.5 Performing the SNCP Trail Switching in Batches..........................................................................2-852.1.21.6 Verifying Platinum Service Groups in Batches..............................................................................2-87



ix

2.1.21.7 Converting SDH Discrete Services to Mono Nodal Trails.............................................................2-872.1.22 Deleting SDH Trails...........................................................................................................................2-88

2.2 Managing Ethernet Trails..............................................................................................................................2-902.2.1 Basic Concepts.....................................................................................................................................2-912.2.1.1 Ethernet End-to-End Management....................................................................................................2-912.2.1.2 Ethernet Services...............................................................................................................................2-932.2.1.3 Relation Between SDH/Radio Trails and Ethernet Trails.................................................................2-942.2.1.4 Tag Attributes....................................................................................................................................2-952.2.2 Creating Ethernet Trails by Trail Search..............................................................................................2-962.2.2.1 Searching for Ethernet Trails............................................................................................................2-962.2.2.2 Viewing Ethernet Discrete Services..................................................................................................2-982.2.3 Configuring EPL Service.....................................................................................................................2-982.2.3.1 Creating a VC4 Server Trail..............................................................................................................2-992.2.3.2 Creating a Trunk Link.....................................................................................................................2-1012.2.3.3 Creating an EPL Trail.....................................................................................................................2-1032.2.3.4 Verifying Ethernet Services............................................................................................................2-1042.2.3.5 Sample Application: Configuring EPL Services.............................................................................2-1052.2.4 Configuring an Unterminated EPL Service.......................................................................................2-1112.2.4.1 Creating a VC4 Server Trail............................................................................................................2-1122.2.4.2 Creating an Unterminated Trunk Link............................................................................................2-1142.2.4.3 Creating a Trunk Link.....................................................................................................................2-1152.2.4.4 Creating an Unterminated EPL Trail..............................................................................................2-1162.2.4.5 Verifying Ethernet Services............................................................................................................2-1172.2.5 Configuring EVPL Services...............................................................................................................2-1182.2.5.1 Creating a VC4 Server Trail............................................................................................................2-1182.2.5.2 Creating a Trunk Link.....................................................................................................................2-1202.2.5.3 Creating an EVPL Trail...................................................................................................................2-1222.2.5.4 Verifying Ethernet Services............................................................................................................2-1232.2.6 Configuring EPLAN Service.............................................................................................................2-1242.2.6.1 Creating a VC4 Server Trail............................................................................................................2-1242.2.6.2 Creating a Trunk Link.....................................................................................................................2-1272.2.6.3 Creating an EPLAN Trail................................................................................................................2-1282.2.6.4 Adjusting VB Mount Ports in an EPLAN.......................................................................................2-1312.2.6.5 Verifying Ethernet Services............................................................................................................2-1322.2.7 Configuring EVPL (QinQ) Service ...................................................................................................2-1332.2.7.1 Creating a VC4 Server Trail............................................................................................................2-1332.2.7.2 Creating a Trunk Link.....................................................................................................................2-1352.2.7.3 Creating an EVPL (QinQ) Trail......................................................................................................2-1372.2.7.4 Verifying Ethernet Services............................................................................................................2-1382.2.8 Specifying a Customer for a Created Trail.........................................................................................2-1392.2.9 Checking the Connectivity of Ethernet Link......................................................................................2-1402.2.9.1 Ethernet OAM.................................................................................................................................2-140



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

Issue 02 (2010-09-24)

2.2.9.2 Creating MPs...................................................................................................................................2-1412.2.9.3 Performing a CC Check..................................................................................................................2-1422.2.9.4 Performing an LB Check.................................................................................................................2-1422.2.9.5 Performing an LT Check.................................................................................................................2-1432.2.9.6 Performing a Ping Test....................................................................................................................2-1442.2.9.7 Performing Performance Detection.................................................................................................2-1452.2.10 Viewing Ethernet Services...............................................................................................................2-1452.2.10.1 Viewing Trunk Links....................................................................................................................2-1462.2.10.2 Analyzing the Trunk Link Fault....................................................................................................2-1462.2.10.3 Viewing Relevant Trails of a Trunk Link.....................................................................................2-1472.2.10.4 Viewing Ethernet Trails................................................................................................................2-1482.2.10.5 Viewing the Server Trail of an Ethernet Trail...............................................................................2-1482.2.10.6 Analyzing the Ethernet Trail Fault................................................................................................2-1492.2.10.7 Viewing the Connectivity of Ethernet Services Networkwide.....................................................2-1502.2.11 Maintaining Ethernet Trails.............................................................................................................2-1502.2.11.1 Adjusting the Ethernet Trail Bandwidth.......................................................................................2-1502.2.11.2 Activating or Deactivating Ethernet Services...............................................................................2-1512.2.12 Deleting Ethernet Services...............................................................................................................2-1522.2.12.1 Deleting Ethernet Trails................................................................................................................2-1522.2.12.2 Deleting Trunk Links....................................................................................................................2-153

2.3 Managing Alarms of an SDH Trail.............................................................................................................2-1542.3.1 Viewing Current Alarms of an SDH Trail.........................................................................................2-1552.3.2 Viewing History Alarms of an SDH Trail.........................................................................................2-1562.3.3 Setting Alarm Reversion for an SDH Trail........................................................................................2-1562.3.4 Inserting an Alarm on an SDH Trail..................................................................................................2-1572.3.5 Managing Networkwide SDH Alarm Trails in Real Time.................................................................2-1582.3.6 Analyzing SDH alarm correlation......................................................................................................2-1582.3.7 Browsing Relevant WDM Trails........................................................................................................2-159

2.4 Managing the Performance of SDH Trails..................................................................................................2-1602.4.1 Viewing Current Performance Data of an SDH Trail........................................................................2-1602.4.2 Viewing History Performance Data of an SDH Trail........................................................................2-1612.4.3 Viewing UAT of SDH Trails.............................................................................................................2-1622.4.4 Viewing Performance Threshold-Crossing Records of SDH Trails..................................................2-1622.4.5 Setting Performance Monitoring Parameters of an SDH Trail..........................................................2-1632.4.6 Setting SDH Trail Performance Threshold........................................................................................2-164

2.5 Managing Ethernet Trail Alarms.................................................................................................................2-1642.5.1 Viewing Current Alarms of a Trunk Link..........................................................................................2-1652.5.2 Viewing History Alarms of a Trunk Link..........................................................................................2-1662.5.3 Viewing Current Alarms of an Ethernet Trail....................................................................................2-1662.5.4 Viewing History Alarms of an Ethernet Trail....................................................................................2-1672.5.5 Managing Networkwide ETH Alarm Trails in Real Time.................................................................2-168

2.6 Browsing the Performance of an Ethernet Trail..........................................................................................2-168



xi

3 End-to-End RTN IP Management...........................................................................................3-13.1 Process of Configuring RTN IP Services........................................................................................................3-23.2 Automatically Searching RTN IP Services.....................................................................................................3-33.3 Managing Tunnel............................................................................................................................................3-4

3.3.1 Introduction to the Tunnel......................................................................................................................3-53.3.1.1 Introduction to the Tunnel...................................................................................................................3-53.3.1.2 Standards and Protocols Compliance of the Tunnel...........................................................................3-73.3.1.3 Basic Concepts of the Tunnel..............................................................................................................3-93.3.1.4 Working Principles............................................................................................................................3-103.3.1.5 Tunnel Protection Group...................................................................................................................3-113.3.1.6 Application of the Tunnel.................................................................................................................3-133.3.2 Tunnel Configuration Flow..................................................................................................................3-143.3.3 Configuring a Tunnel...........................................................................................................................3-163.3.3.1 Creating a Tunnel..............................................................................................................................3-173.3.3.2 Creating Tunnels in Batches.............................................................................................................3-203.3.3.3 Creating a Protection Group..............................................................................................................3-213.3.3.4 Configuring OAM for a Tunnel........................................................................................................3-233.3.3.5 Automatic Search for Protection Groups..........................................................................................3-243.3.3.6 Deploying a Tunnel...........................................................................................................................3-253.3.3.7 Viewing a Discrete Tunnel................................................................................................................3-263.3.3.8 Deleting a Tunnel..............................................................................................................................3-263.3.4 Monitoring a Tunnel.............................................................................................................................3-273.3.4.1 Viewing the VPN Service Carried on a Tunnel................................................................................3-273.3.4.2 Viewing the Topology of a Tunnel...................................................................................................3-283.3.4.3 Viewing the Performance of a Tunnel..............................................................................................3-293.3.4.4 Viewing the Alarms of a Tunnel.......................................................................................................3-293.3.4.5 Monitoring the Running Status of a Tunnel......................................................................................3-303.3.4.6 Viewing the LSP Topology of a Tunnel...........................................................................................3-303.3.4.7 Diagnosing a Tunnel.........................................................................................................................3-313.3.5 Configuration Example (Static CR Tunnel).........................................................................................3-323.3.5.1 Networking Diagram.........................................................................................................................3-323.3.5.2 Service Planning................................................................................................................................3-333.3.5.3 Configuration Process (Creating a Static CR Tunnel)......................................................................3-353.3.6 Configuration Example (RSVP TE Tunnel)........................................................................................3-443.3.6.1 Networking Diagram.........................................................................................................................3-443.3.6.2 Service Planning................................................................................................................................3-453.3.6.3 Configuration Process (Creating a RSVP TE Tunnel)......................................................................3-47

3.4 Configuring a Service Template...................................................................................................................3-593.4.1 Creating a Service Template................................................................................................................3-603.4.2 Creating a Service by Using a Template..............................................................................................3-60

3.5 Viewing a Service Resource.........................................................................................................................3-613.5.1 Querying Public Resources..................................................................................................................3-61



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

Issue 02 (2010-09-24)

3.5.2 Querying CTP Resources.....................................................................................................................3-623.6 Managing PWE3 Services.............................................................................................................................3-62

3.6.1 Overview of PWE3..............................................................................................................................3-633.6.1.1 Introduction.......................................................................................................................................3-643.6.1.2 Reference Standards and Protocols...................................................................................................3-643.6.1.3 PWE3 Basic Principle.......................................................................................................................3-653.6.1.4 PW Template.....................................................................................................................................3-693.6.1.5 VCCV................................................................................................................................................3-703.6.1.6 Static and Dynamic Hybrid Multi-Hop PW......................................................................................3-703.6.1.7 PW Protection...................................................................................................................................3-713.6.1.8 ATM Cell Transparent Transmission................................................................................................3-743.6.1.9 The Application of PWE3 Service....................................................................................................3-773.6.2 PWE3 Configuration Process...............................................................................................................3-783.6.3 PWE3 Operation Tasks........................................................................................................................3-833.6.3.1 Creating a CES Service.....................................................................................................................3-833.6.3.2 Creating an ETH Service...................................................................................................................3-863.6.3.3 Creating an ATM Service.................................................................................................................3-883.6.3.4 Creating a PWE3 Service Through Duplication...............................................................................3-923.6.3.5 Deploying a PWE3 Service...............................................................................................................3-943.6.3.6 Adjusting a Discrete PWE3 Service..................................................................................................3-943.6.4 PWE3 Service Monitoring...................................................................................................................3-953.6.4.1 Viewing the PWE3 Service Topology..............................................................................................3-963.6.4.2 Monitoring Performance of a PWE3 Service....................................................................................3-963.6.4.3 Monitoring Alarms of a PWE3 Service............................................................................................3-973.6.5 Locating a PWE3 Service Fault...........................................................................................................3-983.6.5.1 CES Service Troubleshooting...........................................................................................................3-983.6.5.2 ATM Service Troubleshooting........................................................................................................3-1013.6.5.3 Ethernet Service Troubleshooting...................................................................................................3-1043.6.6 Example for Configuring a CES Emulation Service..........................................................................3-1073.6.6.1 Networking Diagram.......................................................................................................................3-1073.6.6.2 Service Planning..............................................................................................................................3-1083.6.6.3 Configuration Process.....................................................................................................................3-1113.6.7 Example for Configuring an ATM Emulation Service......................................................................3-1273.6.7.1 Networking Diagram.......................................................................................................................3-1283.6.7.2 Service Planning..............................................................................................................................3-1283.6.7.3 Configuration Process.....................................................................................................................3-1323.6.8 Example for Configuring an Ethernet Private Line Emulation Service.............................................3-1473.6.8.1 Networking Diagram.......................................................................................................................3-1473.6.8.2 Service Planning..............................................................................................................................3-1473.6.8.3 Configuration Process.....................................................................................................................3-149

3.7 Modifying Configurations...........................................................................................................................3-1583.7.1 Modifying Tunnel Attributes.............................................................................................................3-159



xiii

3.7.1.1 Modifying a Tunnel.........................................................................................................................3-1593.7.1.2 Deleting a Tunnel............................................................................................................................3-1593.7.2 Modifying PWE3 Attributes..............................................................................................................3-1603.7.2.1 Modifying a PWE3 Service.............................................................................................................3-1603.7.2.2 Deleting a PWE3 Service................................................................................................................3-1603.7.2.3 Deleting a PWE3 Service on the Network Side..............................................................................3-1613.7.2.4 Undeploying a PWE3 Service.........................................................................................................3-161



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

Issue 02 (2010-09-24)

Figures

Figure 1-1 DNI protection example...................................................................................................................1-16Figure 2-1 End-to-end RTN network management flow.....................................................................................2-4Figure 2-2 A conflict trail generated because a fiber is added.............................................................................2-9Figure 2-3 A conflict trail generated because a single station cross-connection is lost.......................................2-9Figure 2-4 A conflict trail generated because a protection service is deleted on a per-NE basis......................2-10Figure 2-5 Creating trails by trail search............................................................................................................2-13Figure 2-6 Creating trails in the automatic mode...............................................................................................2-14Figure 2-7 Creating trails in the manual mode...................................................................................................2-15Figure 2-8 Platinum service group.....................................................................................................................2-19Figure 2-9 Downgraded platinum service group................................................................................................2-20Figure 2-10 Joining and splitting VC4 server trails...........................................................................................2-68Figure 2-11 Restrictions on VC4 server trail joining.........................................................................................2-69Figure 2-12 Restrictions on VC4 server trail joining.........................................................................................2-70Figure 2-13 Service authorization management.................................................................................................2-72Figure 2-14 Loopback to Source........................................................................................................................2-82Figure 2-15 Loopback to Sink............................................................................................................................2-83Figure 2-16 Basic hierarchy of the Ethernet feature..........................................................................................2-93Figure 2-17 EPL services of the Port type.........................................................................................................2-93Figure 2-18 EPL services sharing a PORT port.................................................................................................2-94Figure 2-19 EPL services sharing a VCTRUNK port........................................................................................2-94Figure 2-20 Relation Between SDH Trails and Ethernet Trails.........................................................................2-95Figure 2-21 Networking diagram.....................................................................................................................2-106Figure 2-22 IDU board configuration .............................................................................................................2-106Figure 2-23 Configuring Ethernet services......................................................................................................2-106Figure 2-24 Timeslot allocation of Ethernet services.......................................................................................2-107Figure 2-25 Server trail for an unterminated EPL service...............................................................................2-111Figure 2-26 EPLAN between different boards on an NE.................................................................................2-129Figure 3-1 Process of configuring RTN IP services.............................................................................................3-2Figure 3-2 MPLS tunnel on the MPLS network..................................................................................................3-6Figure 3-3 ATM PWE3 over IP tunnel................................................................................................................3-7Figure 3-4 Process of creating a tunnel..............................................................................................................3-10Figure 3-5 Working process of a tunnel.............................................................................................................3-11Figure 3-6 Principles of the tunnel protection....................................................................................................3-13

iManager U2000 Unified Network Management SystemOperation Guide for RTN End-to-End Management Figures


xv

Figure 3-7 Transparent transmission of point-to-point data packets..................................................................3-14Figure 3-8 Tunnel configuration flow................................................................................................................3-15Figure 3-9 The figure of tunnel protection group...............................................................................................3-22Figure 3-10 Networking diagram of the MPLS tunnel...................................................................................... 3-32Figure 3-11 Networking diagram of the MPLS tunnel...................................................................................... 3-44Figure 3-12 Basic transmission components of the PWE3................................................................................3-66Figure 3-13 PWE3 single-hop topology.............................................................................................................3-67Figure 3-14 PWE3 multi-hop topology..............................................................................................................3-68Figure 3-15 Network of the static and dynamic hybrid multi-hop PW..............................................................3-71Figure 3-16 PW redundancy protection............................................................................................................. 3-72Figure 3-17 CE symmetrical access dual-homing protection.............................................................................3-72Figure 3-18 Backup protection...........................................................................................................................3-73Figure 3-19 PW APS protection.........................................................................................................................3-73Figure 3-20 Application of the PWE3................................................................................................................3-77Figure 3-21 CES service configuration process.................................................................................................3-78Figure 3-22 ATM service configuration process................................................................................................3-80Figure 3-23 Flow of configuring an IP line service........................................................................................... 3-82Figure 3-24 Flowchart for troubleshooting CES service faults........................................................................3-100Figure 3-25 Flowchart for troubleshooting ATM service faults......................................................................3-103Figure 3-26 Flowchart for troubleshooting Ethernet service faults..................................................................3-106Figure 3-27 Networking diagram of the CES service......................................................................................3-107Figure 3-28 Networking diagram of the IMA service......................................................................................3-128Figure 3-29 Networking diagram of the Ethernet service................................................................................3-147

FiguresiManager U2000 Unified Network Management System


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

Issue 02 (2010-09-24)

Tables

Table 2-1 SDH trail level......................................................................................................................................2-7Table 2-2 Comparison of methods for creating trails.........................................................................................2-11Table 2-3 Priority relations of protection strategies...........................................................................................2-16Table 2-4 Scheme for managing timeslot resources...........................................................................................2-18Table 2-5 Processing policy at ingress...............................................................................................................2-95Table 2-6 Processing policy at egress.................................................................................................................2-96Table 3-1 Tunnel configuration tasks.................................................................................................................3-15Table 3-2 Microwave port planning...................................................................................................................3-33Table 3-3 NE parameter planning......................................................................................................................3-33Table 3-4 Tunnel planning.................................................................................................................................3-34Table 3-5 Planning of protection group parameters...........................................................................................3-35Table 3-6 Microwave port planning...................................................................................................................3-45Table 3-7 NE parameter planning......................................................................................................................3-45Table 3-8 Control plane planning.......................................................................................................................3-46Table 3-9 Tunnel planning.................................................................................................................................3-46Table 3-10 Features of the ATM cell transparent transmission services............................................................3-76Table 3-11 Applicable scenarios of various connection types...........................................................................3-76Table 3-12 Comparison between 1-to-1 and N-to-1 modes...............................................................................3-77Table 3-13 Tasks for configuring a CES service................................................................................................3-79Table 3-14 Tasks for configuring an ATM service............................................................................................3-80Table 3-15 Operation tasks for configuring an IP line service...........................................................................3-82Table 3-16 List of common symptoms of CES service faults............................................................................3-99Table 3-17 List of common symptoms of ATM service faults........................................................................3-102Table 3-18 List of common symptoms of Ethernet service faults....................................................................3-104Table 3-19 Service port planning.....................................................................................................................3-108Table 3-20 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots are partially occupied.)...........................................................................................................................................................................3-108Table 3-21 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots are fully occupied.)...........................................................................................................................................................................3-109Table 3-22 Parameters for configuring the CES service: NE1-NE3 (The E1 timeslots are fully occupied.)...........................................................................................................................................................................3-110Table 3-23 Parameters of general attributes.....................................................................................................3-114Table 3-24 Parameters of the source node........................................................................................................3-115Table 3-25 Parameters of the sink node...........................................................................................................3-116

iManager U2000 Unified Network Management SystemOperation Guide for RTN End-to-End Management Tables


xvii

Table 3-26 PW parameters...............................................................................................................................3-118Table 3-27 Parameters of advanced attributes..................................................................................................3-120Table 3-28 Parameters of general attributes.....................................................................................................3-121Table 3-29 Parameters of the source node........................................................................................................3-121Table 3-30 Parameters of the sink node...........................................................................................................3-121Table 3-31 PW parameters...............................................................................................................................3-122Table 3-32 Parameters of advanced attributes..................................................................................................3-123Table 3-33 Parameters of general attributes.....................................................................................................3-124Table 3-34 Parameters of the source node........................................................................................................3-124Table 3-35 Parameters of the sink node...........................................................................................................3-125Table 3-36 PW parameters...............................................................................................................................3-125Table 3-37 Parameters of advanced attributes..................................................................................................3-127Table 3-38 Service port planning.....................................................................................................................3-129Table 3-39 IMA planning.................................................................................................................................3-129Table 3-40 ATM QoS policy planning.............................................................................................................3-130Table 3-41 ATM service planning....................................................................................................................3-130Table 3-42 Parameters of general attributes.....................................................................................................3-136Table 3-43 Parameters of the source node........................................................................................................3-137Table 3-44 Parameters of the sink node...........................................................................................................3-138Table 3-45 PW parameters...............................................................................................................................3-138Table 3-46 Parameter for configuring a ATM connection...............................................................................3-140Table 3-47 Parameters of advanced attributes..................................................................................................3-141Table 3-48 Parameters of general attributes.....................................................................................................3-142Table 3-49 Parameters of the source node........................................................................................................3-142Table 3-50 Parameters of the sink node...........................................................................................................3-143Table 3-51 PW parameters...............................................................................................................................3-143Table 3-52 Parameter for configuring a ATM connection...............................................................................3-145Table 3-53 Parameters of advanced attributes..................................................................................................3-146Table 3-54 Service port planning.....................................................................................................................3-148Table 3-55 Ethernet service planning...............................................................................................................3-148Table 3-56 Parameters of general attributes.....................................................................................................3-151Table 3-57 Parameters of the source node........................................................................................................3-151Table 3-58 Parameters of the sink node...........................................................................................................3-151Table 3-59 PW parameters...............................................................................................................................3-152Table 3-60 Service parameters.........................................................................................................................3-154Table 3-61 PW QoS parameters.......................................................................................................................3-154Table 3-62 Parameters of advanced attributes..................................................................................................3-154Table 3-63 Parameters of general attributes.....................................................................................................3-155Table 3-64 Parameters of the source node........................................................................................................3-155Table 3-65 Parameters of the sink node...........................................................................................................3-156Table 3-66 PW parameters...............................................................................................................................3-156Table 3-67 Service parameters.........................................................................................................................3-157

TablesiManager U2000 Unified Network Management System


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

Issue 02 (2010-09-24)

Table 3-68 PW QoS parameters.......................................................................................................................3-158Table 3-69 Parameters of advanced attributes..................................................................................................3-158

iManager U2000 Unified Network Management SystemOperation Guide for RTN End-to-End Management Tables


xix

1 Managing RTN Protection Subnets

About This Chapter

A protection subnet has a structure of providing complete self-protection functions. The purposeof managing RTN protection subnets is to configure and display network protection, for example,viewing, creating, deleting, modifying and searching for protection subnets, managing NNIs,and managing isolated nodes.

1.1 Basic ConceptsAccording to the layered structure of transport network, protection subnet, belonging to thenetwork layer, refers to a network structure that has a comprehensive self-protection function.The protection subnet is a network unit of composing the optical transport network. To have agood understanding of the protection subnet, you need to learn some basic concepts of thenetwork layer.

1.2 Searching for Protection SubnetsBy searching for a protection subnet, the configured protection attributes at the NE layer on theU2000 are synchronized to the network layer on the U2000 to create protection subnetsautomatically.

1.3 Configuring an MSP RingIn a ring network topology or when a service exists between rings or between a ring and a chain,you can configure an MSP ring to protect the service if a fault occurs.

1.4 Configuring Linear MSPIn the linear network topology, you can configure the linear MSP to protect the network sectionby section.

1.5 Creating an Path Protection RingA path protection ring is used to protect a private ring network. Normally, the protection pathalso transmits the primary service. STM-N signals can be quickly protected at a VC level withoutrunnig a switching protocol.

1.6 Configuring a Non-Protection RingWhen services on a ring do not need protection, you can configure a non-protection (NP) ring.All timeslots on the ring can be used to transmit services.

1.7 Configuring a Non-Protection ChainIf a service in the chain does not need to be protected, you can configure a non-protection chain.In this case, all the timeslots in the chain can be used to transmit the service.

iManager U2000 Unified Network Management SystemOperation Guide for RTN End-to-End Management 1 Managing RTN Protection Subnets


1-1

1.8 Configuring DNI ProtectionYou can create DNI protection for the interworking nodes of two rings, and for the protectionof the interworking services between two ring networks. The network can be a combination ofequipment from different vendors or different protection modes. Moreover, DNI is also availableto fiber and node failures.

1.9 Configuring IF 1+1 ProtectionIF 1+1 protection uses a standby path to protect an active service.

1.10 Configuring IF N+1 ProtectionIF N+1 protection uses a standby path to protect N active services.

1.11 Maintaining Protection SubnetsWhen the protection status of a network is abnormal or when adjusting a network, you need tomaintain the protection subnet.

1.12 Deleting Protection SubnetsWhen an existing protection subnet is not suitable, you can delete the protection subnet.

1.13 Deleting Isolated NodesTo release protection resources that are used by isolated nodes, you need to delete isolated nodes.

1 Managing RTN Protection SubnetsiManager U2000 Unified Network Management System


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

Issue 02 (2010-09-24)

1.1 Basic ConceptsAccording to the layered structure of transport network, protection subnet, belonging to thenetwork layer, refers to a network structure that has a comprehensive self-protection function.The protection subnet is a network unit of composing the optical transport network. To have agood understanding of the protection subnet, you need to learn some basic concepts of thenetwork layer.

1.1.1 Protection SubnetA protection subnet refers to a network architecture that has a comprehensive self-protectionfunction. It is a network that composes the optical transmission network. In the U2000, theprotection subnet is a generalized concept that includes not only the network architecture withthe comprehensive self-protection function, such as the MSP ring and PP ring, but also thenetwork architecture without the self-protection function, such as the non-protection ring andnon-protection chain.

1.1.2 Isolated NodeAn isolated node is not equal to an isolated NE. An isolated node refers to a special logicalsystem that is independent from any protection subnet. It is independent from any protectionsubnet.

1.1.1 Protection SubnetA protection subnet refers to a network architecture that has a comprehensive self-protectionfunction. It is a network that composes the optical transmission network. In the U2000, theprotection subnet is a generalized concept that includes not only the network architecture withthe comprehensive self-protection function, such as the MSP ring and PP ring, but also thenetwork architecture without the self-protection function, such as the non-protection ring andnon-protection chain.

In the U2000, a protection subnet is a network level concept rather than merely an MSP ring ora PP ring. NEs and fiber connections are the basic elements required to construct a protectionsubnet. You should create NEs, perform basic configurations for them, and then properly createfiber connections between the NEs. You should have access to sufficient resources to create aprotection subnet.

1.1.2 Isolated NodeAn isolated node is not equal to an isolated NE. An isolated node refers to a special logicalsystem that is independent from any protection subnet. It is independent from any protectionsubnet.

An isolated node is a node that is configured at NEs but cannot or does not compose a protectionsubnet with other nodes.

An isolated node should not exist in a transmission network that runs normally. The reason forthe existence of any isolated nodes can be as follows:l The fiber that should be connected to the node is not created on the U2000.



1-3

1.2 Searching for Protection SubnetsBy searching for a protection subnet, the configured protection attributes at the NE layer on theU2000 are synchronized to the network layer on the U2000 to create protection subnetsautomatically.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l The NE data must be configured, and fibers must be properly created.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Search for SDH Protection Subnet from theMain Menu.

Step 2 In the Consistency Verification of Existing Subnet screen, select the protection subnet andclick Next.

NOTE

If the verification is unsuccessful and the subnet becomes abnormal, the search menu is unavailable. Inthis case, you need to delete the abnormal subnet from the network layer and then re-search for the subnet.

Step 3 Click Search to start the search. The Subnet Name, Consistent Status and Subnet Typeparameters of the searched protection subnet are automatically displayed.

Step 4 Click Next. The isolated nodes are displayed in the upper left pane of the window.

Step 5 Optional: Select the nodes that do not form any protection subnet, and click Delete. ClickYes in the Operation Prompt dialog box.

Step 6 Click Finish. The searched protection subnet is displayed in the Main Topology.

----End

1.3 Configuring an MSP RingIn a ring network topology or when a service exists between rings or between a ring and a chain,you can configure an MSP ring to protect the service if a fault occurs.

1.3.1 Creating an MS Ring Protection SubnetThe MS ring protection scheme is adopted in a common ring network. Normally, it is adoptedto protect a channel to transmit additional services. By running the APS protocol, it achieves theMS level protection.

1.3.2 Checking Networkwide Multiplex Section ParametersIn the same MSP subnet, each NE should have the same multiplex section parameter settings.After configuring or adjusting an MSP subnet, you need to check the parameters for thenetworkwide multiplex section.

1.3.3 Verifying MSP Protection SwitchingAfter creating a protection scheme and setting the related parameters, you can check whetherthe protection scheme functions normally by performing a switching operation and query theswitching status.




Issue 02 (2010-09-24)

1.3.1 Creating an MS Ring Protection SubnetThe MS ring protection scheme is adopted in a common ring network. Normally, it is adoptedto protect a channel to transmit additional services. By running the APS protocol, it achieves theMS level protection.


Contextl The number of nodes in an MSP ring cannot exceed 16.l When creating a protection subnet, select SDH NEs only. It is not required to select REG

or WDM equipment.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Create 2f_MS SPRing from the Main Menu. ThePrompt dialog box is displayed. Click OK.

NOTE

l To create a four-fiber bidirectional MS shared protection ring, choose Service > SDH Protection Subnet> Create 4f_MS SPRing from the Main Menu to display the related dialog box.

l To create a two-fiber unidirectional MS shared protection ring, choose Service > SDH ProtectionSubnet > Create 2f_MS DPRing from the Main Menu to display the related dialog box.

Step 2 Enter the name of the protection subnet. The default name is usually used, for example, 2f_MSSPRing_1.

Step 3 Select the rate of the protection subnet, for example, STM-4.



1-5

Step 4 Select Resource Sharing and Assigned by VC4 as needed.

NOTE

l Resource Sharing indicates that a port is mapped into multiple protection subnets. If multipleprotection subnets uses one port of a board, you need to check the Resource Sharing check box. Ifdifferent protection subnets use different ports of a board, do not check this check box. If MSP Sharingis enabled, you can check the Resource Sharing check box to map a port of the board to multipleMSPs.

l Select the Assigned by VC4 option when there are different VC4s belonging to different protectionsubnets to achieve virtual optical path protection. For example, for an STM-16 fiber, the VC4 1-4belong to an STM-4 MSP, and VC4 5-8 belong to a non-protection ring.

Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the Main Topologyto add it to the node list in the left-hand pane. Meanwhile, is displayed on the NE icon. If youwant to cancel the selection, double-click the NE again.

NOTE

For easy maintenance, the nodes should be added anticlockwise to the protection subnet.

Step 6 Set the attribute of the nodes. Select MSP Node in this example.




Issue 02 (2010-09-24)

Step 7 Click Next to proceed to the Select Link screen of the wizard. Set parameters, such as PhysicalLink Information.

NOTE

l If there are multiple fibers between two NEs, select them from the Physical Link Information drop-down list.

l If Assigned by VC4 is selected, you can select the working and protection VC4 timeslots as needed.

Step 8 Click Finish to deliver the configuration data. Then the Operation Result prompt box isdisplayed. Click Close.

Step 9 Right-click the protection subnet and choose Protection Subnet Attributes from the shortcutmenu.

Step 10 Click the Protection Subnet Maintenance tab to check whether the protocol controller starts.If not, select all the NEs of the protection subnet. Right-click and choose Start/Stop Protocol> Start from the shortcut menu. Click Yes in the dialog box that is displayed twice. Ensure thatthe status of all the values in the Protocol Controller column is Protocol Started.

Step 11 Click the Protection Subnet Parameters tab and set the WTR time and SD Condition asneeded. Click Apply to deliver the configuration.

NOTE

The WTR time of all NEs in the same protection subnet should be the same.

----End


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

l The MSP protection subnet must be created.

l You need to select the Protection Type in the filter from the Main Topology.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Verify Networkwide MS Parameters from theMain Menu. A progress bar is displayed.

Step 2 A prompt appears telling you that the operation was successful. Click Close.

----End




1-7

Prerequisitel You must be an NM user with "network operator" authority or higher.l The MSP protection subnet must be created.

ContextNOTE

The external switching for MSP protection includes: lockout, forced switching, manual switching andexercise switching.

l In the event of lockout of switching, the switching request for the port is denied, but the reversion ofswitching is allowed. Regardless of the status of the working and protection channels, the services arelocked in the working channel.

l Forced switching has a higher priority than signal failure and signal degrade, on the protection section.This switching is performed regardless of the protection channel state, unless the protection channelis satisfying a higher priority bridging request.

l Manual switching has a lower priority than signal failure and signal degrade, on the protection section.The manual switching request is valid only when there is no signal failure or signal degrade on theprotection section.

l The exercise switching is used to test the APS protocol. In fact services are not switched to the protectionsection, and only the calculation result of the protocol is displayed.

CAUTIONSwitching other than the exercise switching may interrupt services.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the MainMenu.

Step 2 Select an MSP protection subnet from the subnet list. The attribute information of the protectionsubnet is displayed in the right pane.

Step 3 Click the Protection Subnet Maintenance tab.

Step 4 Right-click the desired NE and choose an office direction to switch, lock out or clear switching.The prompt dialog box is displayed.

NOTE

l The office direction can be switched only when it is not locked out.

l For two-fiber and four-fiber rings, only two office directions can be switched.

Step 5 Click Yes. A prompt appears telling you that the operation was successful. Click OK.

Step 6 Click Query and check whether the service of the node is already switched to the protectionpath.

Step 7 Select the node to be verified, right-click it and choose East > Clear All or West > Clear Allto clear the switching.

----End




Issue 02 (2010-09-24)

1.4 Configuring Linear MSPIn the linear network topology, you can configure the linear MSP to protect the network sectionby section.

1.4.1 Creating a Linear MS Protection SubnetIn a chain network, an NE can protect a service in different sections of the fiber after a linearMS protection subnet is created.



1.4.1 Creating a Linear MS Protection SubnetIn a chain network, an NE can protect a service in different sections of the fiber after a linearMS protection subnet is created.


ContextFibers that are related to an linear MSP cannot be used by other protection subnets. That is, anlinear MSP and other subnets cannot create virtual fibers together.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Create 1+1 Linear MSP from the Main Menu.

NOTE

To create a M:N linear MS protection scheme, choose Service > SDH Protection Subnet > Create M:NLinear MSP from the Main Menu to display the related dialog box.

Step 2 Enter the name of the protection subnet. The default name is usually used, for example, 1+1_MSP_1.




1-9

Step 4 Set Revertive Mode and Switching Mode based on the protection type and requirements.

NOTE

l For M:N linear MS protection scheme, set the number of working links to N. M indicates the number ofprotection links and cannot be set. Currently, the value is 1 only.

l Revertive Mode refers to the handling strategy adopted after the faulty line recovers to normal.

l Non-Revertive: The service does not automatically revert to the working channel after the faulty linerecovers to normal.

l Revertive: The service automatically reverts to the working channel after the faulty line recovers tonormal.

l Switching Mode refers to the switching strategy adopted after a fault occurs to the line.

l Single-ended switching: To protect services, switching occurs at the receive end when the receive endis faulty and at the transmit end when the transmit end is faulty.

l Dual-ended switching: To protect services, the switching occurs at the receive and transmit ends wheneither end is faulty.

l Resource Sharing indicates that a port is mapped into multiple protection subnets. If multiple protectionsubnets uses one port of a board, you need to check the Resource Sharing check box. If different protectionsubnets use different ports of a board, do not check this check box.

l Select the Assigned by VC4 option when there are different VC4s belonging to different protection subnetsto achieve virtual optical path protection. For example, for an STM-16 fiber, the VC4 1-4 belong to anSTM-4 MSP, and VC4 5-8 belong to a non-protection ring.

Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the Main Topologyto add it to the node list in the left-hand pane. Meanwhile, is displayed on the NE icon. If youwant to cancel the selection, double-click the NE again.




Issue 02 (2010-09-24)

Step 6 Click Next to proceed to the Select Link of the wizard. Set the Physical Link Information ofWorking Link and Protection Link.

Step 7 Click Finish to deliver the configuration data. The Operation Result prompt box is displayed.ClickClose.

Step 8 Right-click the protection subnet and choose Protection Subnet Attributes from the shortcutmenu.

Step 9 Click the Protection Subnet Maintenance tab to check whether the protocol controller isstarted.

NOTE

If the protocol controller is not started, select all the NEs of the protection subnet. Right-click them andchoose Start/Stop Protocol > Start from the shortcut menu. Click Yes in the dialog box that is displayedtwice. Ensure that the status of all the values in the Protocol Controller column is Protocol Started.

Start/Stop Protocol > Start means to enables the APS protocol of the selected station.

Start/Stop Protocol > Start the Protocol Networkwide means to enables the APS protocol of all nodeson the ring.

Step 10 Click the Protection Subnet Parameters tab and set the WTR time and SD condition asneeded. Click Apply to deliver the configuration.

NOTE

The WTR time of all NEs in the same protection subnet should be the same.

You can set the WTR Time only after you set the Revertive Mode to Revertive.

----End




l You need to select the Protection Type in the filter from the Main Topology.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Verify Networkwide MS Parameters from theMain Menu. A progress bar is displayed.

Step 2 A prompt appears telling you that the operation was successful. Click Close.

----End



1-11


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


ContextNOTE







Procedure





NOTE







Issue 02 (2010-09-24)

Step 6 Click Query and check whether the service of the node is already switched to the protectionpath.

Step 7 Select the node to be verified, right-click it and choose East > Clear All or West > Clear Allto clear the switching.

----End

1.5 Creating an Path Protection RingA path protection ring is used to protect a private ring network. Normally, the protection pathalso transmits the primary service. STM-N signals can be quickly protected at a VC level withoutrunnig a switching protocol.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l On the U2000, the data of each NE must be configured, and fibers must be created correctly.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Create PP(Diverse Route) from the Main Menu.

NOTE

To create a two-fiber bidirectional path protection ring, choose Service > SDH Protection Subnet >Create PP(Uniform Route) from the Main Menu to display the related dialog box.

Step 2 Enter the name of the protection subnet. Generally, enter the default name, for example, two-fiber unidirectional path protection ring_1.

Step 3 Select the capacity level of the protection subnet, for example, STM-4.

Step 4 Select Resource Sharing or Assigned by VC4 as required.

NOTE

l Resource Sharing indicates that a port is mapped into multiple protection subnets. If multipleprotection subnets uses one port of a board, you need to check the Resource Sharing check box. IfMSP Sharing is enabled, you can check the Resource Sharing check box to map a port of the boardto multiple MSPs. If different protection subnets use different ports of a board, do not check this checkbox.

l Select the Assigned by VC4 option when there are different VC4s belonging to different protectionsubnets to achieve virtual optical path protection.

Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the to add it to thenode list in the left-hand pane. Meanwhile, is displayed on the NE icon. If you want to cancelthe selection, double-click the NE again.



1-13

NOTE

For easy maintenance, the nodes should be added anticlockwise to the protection subnet.

Step 6 Set the attribute of each node to PP Node.



----End

1.6 Configuring a Non-Protection RingWhen services on a ring do not need protection, you can configure a non-protection (NP) ring.All timeslots on the ring can be used to transmit services.

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

l The NE data must be configured, and fibers must be properly created.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Create Unprotected Ring from the Main Menu.

Step 2 Enter the name of the protection subnet. The default name is usually used, for example,NP_Ring_1.






Issue 02 (2010-09-24)

NOTE

l Resource Sharing indicates that a port is mapped into multiple protection subnets. When multipleprotection subnets occupy a port of a board, Resource Sharing must be selected. When differentprotection subnets occupy different ports of a board, Resource Sharing is not required.

l Assigned by VC4 indicates that different VC4s belong to different protection subnets to achieve virtualoptical path protection. For example, in the case of an STM-16 fiber, the first through fourth VC4sbelong to an STM-4 MS shared protection, while the fifth through eighth VC4s belong to a non-protection ring. If you enable multiple MSPs for a single optical port, you can configure multiple MSPrings by VC4 for the optical port.

Step 5 Add nodes to the protection subnet to be created. Double-click the NE on the Main Topologyand add it to the node list in the left-hand pane. Meanwhile, is displayed on the NE icon. Ifyou want to cancel the selection, double-click the NE again.



----End

1.7 Configuring a Non-Protection ChainIf a service in the chain does not need to be protected, you can configure a non-protection chain.In this case, all the timeslots in the chain can be used to transmit the service.


l On the U2000, the data of each NE must be configured, and fibers must be created correctly.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Create Unprotected Chain from the Main Menu.

Step 2 Enter the name of the protection subnet. Generally, enter the default name, for example, non-protection chain_1.

Step 3 Select the capacity level of the protection subnet, for example, STM-4.




1-15

NOTE

l Resource Sharing indicates that a port is mapped into multiple protection subnets. When multipleprotection subnets occupy a port of a board, Resource Sharing must be selected. When differentprotection subnets occupy different ports of a board, Resource Sharing is not required.

l Assigned by VC4 indicates that different VC4s belong to different protection subnets to achieve virtualoptical path protection. For example, in the case of an STM-16 fiber, the first through fourth VC4sbelong to an STM-4 MS shared protection, while the fifth through eighth VC4s belong to a non-protection ring. If you enable multiple MSPs for a single optical port, you can configure multiple MSPrings by VC4 for the optical port.

Step 5 Select a node to create a non-protection chain. Double-click an NE in the Main Topology andadd it to the left node list. At the same time, is displayed on the NE icon. Double-click theNE icon again to cancel the selection.

Step 6 Click Next to display the Select Link dialog box. Set parameters, such as Physical LinkInformation.


----End

1.8 Configuring DNI ProtectionYou can create DNI protection for the interworking nodes of two rings, and for the protectionof the interworking services between two ring networks. The network can be a combination ofequipment from different vendors or different protection modes. Moreover, DNI is also availableto fiber and node failures.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l NE data must be configured, and fibers must be properly created.l Protection subnets must be created for the two rings for which you want to create DNI

protection.l The DNI protection cannot be created on four-fiber rings.

ContextFigure 1-1 shows a sample networking of DNI protection.

Figure 1-1 DNI protection exampleNE3 or NE5 is the master node while the NE4 or NE6 is the slave node.




Issue 02 (2010-09-24)

Two-fiber MSSPRING_1

Two-fiber PPRING_1

NP CHAIN_2

NE1

NE2 NE3

NE4

NE5

NE6 NE7

NE8

NP CHAIN_1

Procedure

Step 1 Choose Service > SDH Protection Subnet > Create DNI from the Main Menu.

Step 2 Enter the name of the protection subnet, for example, DNI_1.

Step 3 Double-click the icons of NE3 and NE4 on the view, and select them as the master and slavenodes respectively for the DNI protection.

NOTE

When you select DNI nodes on a protection ring, the west node is the master node and the east node is theslave node.

Step 4 Click Next to select the protection subnet to which the nodes are associated. Select the associatedprotection subnet from the protection subnet list: 2f-MS-SPRING_1.

Step 5 Click Finish to deliver the configuration data.

Step 6 Repeat Steps 2 through 6 to create the master node and the slave node, which are NE5 and NE6.

----End

1.9 Configuring IF 1+1 ProtectionIF 1+1 protection uses a standby path to protect an active service.


l The corresponding IF board and the ODU that connects to the IF board must be added.



1-17

Procedure

Step 1 Choose Service > RTN Protection Subnet > Create IF_1+1 Protection Subnet from the MainMenu.

Step 2 Enter the name of the protection subnet. The default name is usually used. For example, IF_1+1_1.

Step 3 Select the capacity level of the protection subnet. For example, STM-1.

Step 4 Select the working mode of the protection subnet. For example, SD.

Step 5 Select the revertive mode of the protection subnet. For example, non-revertive.

l Revertive: The service is switched back to the working channel after the waiting timespecified in WTR Time when the working channel recovers.

l Non-Revertive: The service keeps working in the protection channel after the workingchannel recovers.

Step 6 Choose whether to enable reverse switching of a protection subnet. For example, Enable.

NOTE

l Enable: When the active or standby IF board has a service alarm at the source, switching takes placeat the source.

l Disable: When the preceding situation occurs, switching does not take place at the source.

Step 7 Select the nodes that the protection subnet contains. Double-click the selected NE on the MainTopology and add it to the left-hand node list. Meanwhile, is displayed on the NE icon. Double-click the NE again to cancel it.

Step 8 Click Next. Set parameters such as Working Link and Protection Link.

Step 9 Click Finish to impose the settings. The Operation Result dialog box is displayed. ClickClose.

----End

1.10 Configuring IF N+1 ProtectionIF N+1 protection uses a standby path to protect N active services.


l The IF boards and ODUs connected to the IF boards must be created.

l The STM-1 optical/electrical interface boards (only for the primary NE in the case of 3+1protection) must be created.

l In the case of 3+1 protection, configure REG on the secondary NEs.

Procedure

Step 1 Choose Service > RTN Protection Subnet > Create IF_N+1 Protection Subnet from the Mainmenu.




Issue 02 (2010-09-24)

Step 2 Enter the name of the protection subnet. The default name is usually used, for example, IF_N+1_1.

Step 3 Choose the capacity level for the protection subnet, for example, STM-1.

Step 4 Set N, which indicates the number of working channels in the protection subnet.

NOTE

"M" indicates the number of protection links. By default, it is 1. "N" indicates the number of working links.

Step 5 Select included NEs for the protection subnet to be created. In Main Topology, double-click theselected NEs to add them to the node list on the left. Then, the NE icons are displayed as . Tocancel the setting, double-click the selected NEs again.

Step 6 Click Next. Set the parameters about the physical link information in Working Link andProtection Link.

Step 7 Click Finish to deliver the configuration data. The Operation Result dialog box is displayed.Click Close.

----End

1.11 Maintaining Protection SubnetsWhen the protection status of a network is abnormal or when adjusting a network, you need tomaintain the protection subnet.

1.11.1 Finding Protection SubnetsWhen there are a number of protection subnets in a network, you use the search function toquickly find the desired protection subnet.

1.11.2 Querying Protection Subnet ResourcesYou can query the resources of the protection subnets to know the resource distribution in theexisting network. Then, you can rationally plan the services.

1.11.3 Collecting Statistics on the SDH Protection Subnet ResourcesThe statistics on the information about protection subnet resources include the basic informationabout protection subnets and detailed parameters of each node.

1.11.4 Checking MS Protection Switching StatusBy checking MS protection switching status, in addition to learning about the faults of the NEsor fibers in the MS protection subnet, the network maintenance personnel can locate the faultsaccording to the switching status of each NE in the MS protection subnet.

1.11.5 Setting Protection Subnet ParametersFor the SDH and RTN equipment, youYou can set parameters for protection subnet by usingthe protection subnet maintenance function.

1.11.6 Checking TPS Switching statusIf tributary protection switching (TPS) takes place, it indicates that the protected tributary boardhas failed. You can check the TPS switching status to detect faults that caused the failure.

1.11.7 Performing MSP SwitchingDuring deployment and commissioning, you can perform switching to test whether MSPswitching works properly. In fault maintenance, you can perform this operation to locate faults.

1.11.8 Performing SNCP Service Switching



1-19

During deployment and commissioning, you can perform switching to test whether SNCPswitching works properly. In fault maintenance, you can perform this operation to locate faults.

1.11.9 Adjusting the Capacity of an MSP RingTo increase bandwidth utilization without interrupting services, you can adjust the VC4 channelsthat the configured MSP ring occupies.

1.11.10 Adjusting the Capacity of a Linear MSPYou can adjust the number of VC4 channels that the configured linear MSP occupies, withoutinterrupting the service.

1.11.11 Changing an NP Chain to a 1+1 Linear MSPThe U2000 allows you to change some protection types without interrupting services, deletingexisting services from the protection subnet, and changing the trail name and other attributes.To facilitate network management and maintenance, you can change a non-protection (NP) chainto a 1+1 linear MSP.

1.11.12 Checking IF 1+1 Protection Switching StatusIf IF 1+1 protection switching occurs, it means that the protected IF board is faulty. By checkingthe IF 1+1 protection switching status, the network maintenance personnel can detect a fault ina timely manner and prevent the fault from affecting services.

1.11.13 Checking IF N+1 Protection Switching StatusChecking protection switching status helps the network maintenance personnel to detect faultsin NEs or radio links in the IF N+1 protection subnet and to locate faults to the specific NE.

1.11.1 Finding Protection SubnetsWhen there are a number of protection subnets in a network, you use the search function toquickly find the desired protection subnet.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The protection subnet must be created.

ProcedureStep 1 Right-click in the Main Topology and choose Search SDH Protection Subnet. The Search

Protection Subnet dialog box is displayed.




Issue 02 (2010-09-24)

NOTEYou need to select the Protection check box on the upper right corner of the Main Topology in advance.

Step 2 Set the search condition and enter the keyword.

Step 3 Click Search and the protection subnet that is searched out is highlighted in the Network View.

----End

1.11.2 Querying Protection Subnet ResourcesYou can query the resources of the protection subnets to know the resource distribution in theexisting network. Then, you can rationally plan the services.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l The data of each NE must have be configured on the U2000 and the fibers must have been

properly created.l The protection subnet must have been configured.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the MainMenu to display the Protection Subnet Attributes dialog box.

Step 2 Select the protection subnet to be viewed from the protection subnet list. The attributeinformation of the protection subnet is displayed in the right pane.

Step 3 Click the Resource Description tab, view related resources.

----End

1.11.3 Collecting Statistics on the SDH Protection Subnet ResourcesThe statistics on the information about protection subnet resources include the basic informationabout protection subnets and detailed parameters of each node.

PrerequisiteYou must be an NM user with "network monitor" authority or higher.

Procedure

Step 1 Choose Inventory > SDH Report > Statistics Report of SDH Protection SubnetResources from the main menu.

Step 2 In the Filter window, select the protection subnet type and click Filter.

Step 3 In the Statistics Report of SDH Protection Subnet Resource window, view the resources ofthe qualified protection subnets.

Step 4 Optional: Click Print or Save As to output the report.

----End



1-21

1.11.4 Checking MS Protection Switching StatusBy checking MS protection switching status, in addition to learning about the faults of the NEsor fibers in the MS protection subnet, the network maintenance personnel can locate the faultsaccording to the switching status of each NE in the MS protection subnet.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The MSP protection subnet must be created.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the MainMenu to display the Protection Subnet Attributes dialog box.

Step 2 Select an MSP protection subnet from the left pane. The attribute information of the protectionsubnet is displayed in the right pane.


Step 4 Click Query to query the switching status of each node.

----End

1.11.5 Setting Protection Subnet ParametersFor the SDH and RTN equipment, youYou can set parameters for protection subnet by usingthe protection subnet maintenance function.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l On the U2000, the data of each NE must be configured, and fibers are created correctly.l The protection subnet must be configured.

Procedure


Step 2 In the left-hand pane, select a protection subnet and the attributes of the protection subnet aredisplayed in the right-hand pane.

Step 3 Click the Protection Subnet Parameters tab.

Step 4 Click Query to query the parameters of the protection subnet

Step 5 Click the WTR Time(s) text box and enter a new value.

NOTE

In the case of the RTN equipment, after you create a protection subnet, you cannot modify the workingmode.

Step 6 Optional: To set the SD as the trigger condition of the switching, check the SD Condition checkbox.




Issue 02 (2010-09-24)

Step 7 Click Apply. Click Close in the Operation Result dialog box displayed.

----End

1.11.6 Checking TPS Switching statusIf tributary protection switching (TPS) takes place, it indicates that the protected tributary boardhas failed. You can check the TPS switching status to detect faults that caused the failure.

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

l TPS protection must be configured.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > TPS Protection from the FunctionTree.

Step 2 Click Query to query the protection switching status.

Step 3 Click Close.

----End

1.11.7 Performing MSP SwitchingDuring deployment and commissioning, you can perform switching to test whether MSPswitching works properly. In fault maintenance, you can perform this operation to locate faults.


l The MSP must be created.

ContextNOTE








1-23


Procedure





NOTE




----End

1.11.8 Performing SNCP Service SwitchingDuring deployment and commissioning, you can perform switching to test whether SNCPswitching works properly. In fault maintenance, you can perform this operation to locate faults.


l The SNCP services must be configured.

ContextThe external switching for SNCP protection includes: lockout, forced switching and manualswitching.

l In the event of lockout of switching, the switching request for the port is denied, but thereversion of switching is allowed. Regardless of the status of the working and protectionchannels, the services are locked in the working channel.

l Forced switching has a higher priority than signal failure and signal degrade, on theprotection section. This switching is performed regardless of the protection channel state,unless the protection channel is satisfying a higher priority bridging request.

l Manual switching has a lower priority than signal failure and signal degrade, on theprotection section. The manual switching request is valid only when there is no signalfailure or signal degrade on the protection section.




Issue 02 (2010-09-24)

CAUTIONAll switching may interrupt services.

Procedure

Step 1 In the NE Explorer, select an NE and choose Configuration > SNCP Service Control from theFunction Tree.

Step 2 Select the service in Working Service and right-click on the Current Status. Select theswitching or lock operation.

NOTE

A service can be switched only when it is not locked.

Step 3 Click OK. A prompt appears telling you that the operation was successful. Click Close.

Step 4 Click Query to query the switching status.

----End

1.11.9 Adjusting the Capacity of an MSP RingTo increase bandwidth utilization without interrupting services, you can adjust the VC4 channelsthat the configured MSP ring occupies.


l The MSP ring must be created.

Contextl The capacity adjustment for a protection subnet results in the loss of service protection.

l Capacity adjustment cannot be performed when the protection subnet is in the switchingstate.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnetfrom the MainMenu.

Step 2 Select the desired MSP subnet for which you wish to adjust capacity from the protection subnetlist, right-click and choose Capacity adjustment from the shortcut menu, the dialogue box isdisplayed, click Yes.

Step 3 Select the capacity level in the Modify Information field, and check the Resource Sharingcheck box.

Step 4 Click VC4 in Modify Information. Select the desired VC4 channel from the drop-down list,

and click to set it as the selected channel.



1-25

Step 5 Click Apply. In the Operation Result dialog box displayed, click Close.

----End

1.11.10 Adjusting the Capacity of a Linear MSPYou can adjust the number of VC4 channels that the configured linear MSP occupies, withoutinterrupting the service.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l The linear MSP must be created.

Contextl This function applies to 1+1 linear MSP and 1:N linear MSP.l If the timeslots of a protection subnet is occupied, you cannot change the capacity of the

protection subnet to a smaller value.l Capacity adjustment cannot be performed when the protection subnet is in the switching

state.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnetfrom the MainMenu.

Step 2 Select the desired MSP subnet from the protection subnet list, right-click and choose Capacityadjustment, the dialogue box is displayed, click Yes.

Step 3 Select the capacity level in the Modify Information field, and check the Resource Sharingcheck box.

Step 4 Click VC4 in Modify Information. Select the desired VC4 channel from the drop-down list,

and click to set it as the selected channel.

Step 5 Click Apply.

Step 6 Click Yes in the dialog box. A prompt is displayed telling you that the operation was successful.Click Close.

----End

1.11.11 Changing an NP Chain to a 1+1 Linear MSPThe U2000 allows you to change some protection types without interrupting services, deletingexisting services from the protection subnet, and changing the trail name and other attributes.To facilitate network management and maintenance, you can change a non-protection (NP) chainto a 1+1 linear MSP.





Issue 02 (2010-09-24)

l The protection type should be changed for both the release 5.0 NEs. They should beconfigured on the U2000 and must run normally.

l A minimum of two fibers of the same level should lie between the two NEs and should notbe occupied by other protection subnets, such as PP, MSP, NP ring, or NP chain with morethan two NEs.

l The protection chain contains no service before you perform this operation.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Change SDH Protection Type from the MainMenu. The protection type change wizard is displayed.

Step 2 Select the switching type and the capacity level. Under the Protection switching type area,select a Capacity level. Click Next.

NOTE

As the U2000 allows only the change from an NP chain to a 1+1 linear MSP, you should use the defaultvalue for the change type.

Step 3 Select an NE. Select an NE in the List of available NEs pane or click to select an

NE on the Main Topology. Click the to transfer it to the List of selected NEs pane.Click Next.



1-27

NOTE

You can choose only two NEs.

Step 4 Select the working link and the protection link. Select appropriate links as the Working Linkand the Protection Link in the Available links pane. Click Next.

Step 5 Set the attributes of the protection subnet. Select values for Protection Subnet Name, Switchingmode, and Revertive Mode, and set WTR time and Enabling SD.




Issue 02 (2010-09-24)

Step 6 Click Finish.

----End

1.11.12 Checking IF 1+1 Protection Switching StatusIf IF 1+1 protection switching occurs, it means that the protected IF board is faulty. By checkingthe IF 1+1 protection switching status, the network maintenance personnel can detect a fault ina timely manner and prevent the fault from affecting services.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The IF 1+1 protection group must be created.

ProcedureStep 1 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the Main

Menu.

Step 2 In the left-hand pane, select an IF 1+1 protection subnet. The attributes of the protection subnetare displayed in the right-hand pane.



----End

1.11.13 Checking IF N+1 Protection Switching StatusChecking protection switching status helps the network maintenance personnel to detect faultsin NEs or radio links in the IF N+1 protection subnet and to locate faults to the specific NE.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l An IF N+1 protection subnet must be created.

ProcedureStep 1 Choose Service > SDH Protection Subnet > Maintain SDH Protection Subnet from the Main

menu.

Step 2 In the left-hand pane, select an N+1 protection subnet, right-click. The attributes of the protectionsubnet are displayed in the right-hand pane.



----End

1.12 Deleting Protection SubnetsWhen an existing protection subnet is not suitable, you can delete the protection subnet.



1-29

PrerequisiteYou must be an NM user with "network maintainer" authority or higher.

ContextNOTE

The deletion of a protection subnet will leave the equipment or services unprotected. Hence, exercisecaution before this operation.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Manage SDH Protection Subnet from the MainMenu.

Step 2 Right-click the protection subnet to be deleted and choose Delete from the NM or Delete fromthe NE or Delete All from the NM from the shortcut menu.

NOTEThe methods to delete a protection subnet are as follows:

l Delete from the NM: Deletes the relation between the protection subnet and logical systems at the NEside, to allow deleting of fibers, re-uploading, and so on. This command is not delivered to the NE anddoes not affect the services. The deleted protection subnet can be located by using the search feature.The U2000 locates it according to the NE layer protection information.

l Delete from the NE: Deletes the protection subnet, logical systems at the NE side, and all traffic inthe protection subnet. The deleted protection subnet cannot be restored without being created again.

l Delete All from the NM: Deletes data other than fibers in the network layer. After the deletion, youcan search out trails and protection subnets again by using the search feature. It is recommended thatyou do not select this option, because a large amount of data will be deleted.

Step 3 In the Operation Prompt dialog box, click Yes.

NOTE

If Delete from the NE is selected, you need to confirm the operation once more.

Step 4 Optional: If there are trails or services on the protection subnet, a confirmation dialog box isdisplayed. In the confirmation dialog box, specify whether to delete the trails that pass theprotection subnet from the network layer of the U2000, and then click Continue.

Step 5 After completion, click Close in the dialog box displayed to complete the operation.

----End

1.13 Deleting Isolated NodesTo release protection resources that are used by isolated nodes, you need to delete isolated nodes.


l One or more isolated nodes must exist.




Issue 02 (2010-09-24)

Context

CAUTIONDeleting isolated nodes may interrupt services. Exercise caution when you perform thisoperation.

Procedure

Step 1 Choose Service > SDH Protection Subnet > Manage SDH Isolated Node from the MainMenu.

Step 2 Select the isolated node you want to delete, right-click and choose Delete.

Step 3 Click Yes in the confirmation dialog box.

----End



1-31

2 End-to-End RTN Management

About This Chapter

In the end-to-end configuration mode, you can quickly configure radio services and SDHservices of the VC12, VC3, VC4 levels. During the end-to-end configuration, you only need tospecify the source and sink for the service, and the U2000 automatically calculates the route andcreates the service for each NE on the route. The end-to-end configuration mode is also calledthe trail management function.

PrerequisiteThe trail management license must be provided for the U2000.

2.1 Managing SDH TrailsThis section describes how to use the trail function of U2000 to configure an end-to-end SDHservice.

2.2 Managing Ethernet TrailsIn the end-to-end configuration mode, you can quickly create Ethernet services, such as EPL,EVPL or EPLAN. During the end-to-end configuration, you only need to specify the source andsink for the service, and the U2000 automatically calculates the route and creates the service foreach NE on the route. The end-to-end configuration mode is also called the trail managementfunction.

2.3 Managing Alarms of an SDH TrailBy using the end-to-end trail management function of the U2000, you can manage alarmsgenerated on SDH trails at the network layer.

2.4 Managing the Performance of SDH TrailsYou can use the network layer function of the U2000 to perform end-to-end performancemanagement on SDH trails.

2.5 Managing Ethernet Trail AlarmsYou can use the U2000 function of the end-to-end trail management to manage the alarmsgenerated on Ethernet trails at the network layer.

2.6 Browsing the Performance of an Ethernet TrailBy browsing the performance of the Ethernet trail, you can learn about the running status of theservices in the existing trail.

iManager U2000 Unified Network Management SystemOperation Guide for RTN End-to-End Management 2 End-to-End RTN Management


2-1

2.1 Managing SDH TrailsThis section describes how to use the trail function of U2000 to configure an end-to-end SDHservice.

PrerequisiteA U2000 user can manage all the trails that the user creates. To manage a trail that is created byanother U2000 user, a U2000 user must meet any of the following conditions:l The U2000 user belongs to the Administrators user group.l The right to manage the required trail is allocated to the U2000 user.

2.1.1 Configuration Task FlowA configuration task flow describes the operation tasks that manage an RTN network by usingthe end-to-end function of the U2000. In addition, the relationships between the operation tasksare described.

2.1.2 Basic ConceptsThis section describes the basic concepts of the end-to-end management.

2.1.3 Disabling a FiberCertain fibers may be deleted during O&M. Those fiber resources are not used when you createa trail. Therefore, you can disable those fibers.

2.1.4 Creating SDH Trails by Trail SearchFor the SDH trails created by trail search, the configured services on each NE are displayed onthe U2000 in an end-to-end form. In this way, you can view and manage the routes and resourcesoccupied of each service in an intuitive manner.

2.1.5 Automatically Creating VC4 TrailsIf you want to create SDH services of the E4, STM-1 levels, you can complete the serviceconfiguration quickly by creating end-to-end VC4 trails.

2.1.6 Automatically Creating VC12 and VC3 TrailsIf you want to create SDH services of the VC12 and VC3 levels, you can complete the serviceconfiguration quickly by creating end-to-end VC12 and VC3 trails.

2.1.7 Creating a Platinum Service GroupIn a platinum service group, the SDH trails do not pass through the same NE, fiber, or fiber/cable pipe, so that the risk that multiple trails are interrupted is lowered.

2.1.8 Bound Platinum Service GroupYou can bind a trail or trails when you need to add an existing trail to a platinum service groupor bind existing trails as a platinum service group.

2.1.9 Creating an SDH Trail ManuallyThe U2000 has restrictions on trail route computation and does not support complicated networkvery well. If you fail to create trails using the route computation function, you can use the functionof manually creating trails to create them.

2.1.10 Creating PDH Radio TrailsWhen you create a PDH radio trail in the end-to-end mode, services configured on each NE aredisplayed in the U2000 in the end-to-end mode. This provides a visual display of the route ofeach service, so that you can view and manage routes and used resources in an easy way.

2.1.11 Creating SDH Radio Trails

2 End-to-End RTN ManagementiManager U2000 Unified Network Management System



Issue 02 (2010-09-24)

When you create an SDH radio trail in the end-to-end mode, services configured on each NEare displayed in the U2000 in the end-to-end mode. Such display facilitates the check andmanagement over the routes of each service and resources used for each service.

2.1.12 Copying SDH TrailsTo expand a network, you can quickly create SDH trails by duplicating a created SDH trail.

2.1.13 Modifying an SDH TrailYou can use the U2000 to modify a created SDH trail.

2.1.14 Removing a Trail from a Platinum Service GroupWhen the platinum service protection is no longer required but the trail of the platinum serviceprotection needs to be retained, you can remove the trail from the platinum service group.

2.1.15 Configuring Overhead Bytes of an SDH TrailIf you want to maintain or monitor the SDH trails, you can set the trail overhead bytes.

2.1.16 Changing Between SNCP and Non-SNCP TrailsIn the case of a protection subnet change, you can change non-SNCP trails to SNCP trails andvice versa by following this process. This change may interrupt the service.

2.1.17 Enabling or Disabling VC4 Server TrailsA VC4 server trail is used to carry lower order client trails between NEs. When the timeslotusage of a VC4 server trail reaches the limit, or you want to transfer a service to another servertrail, you can disable or enable the VC4 server trail to set whether it continues to carry lowerorder trails. This function helps telecom operators to maintain network resources.

2.1.18 Joining and Splitting VC4 Server TrailsA VC4 server trail is used only to carry the services between the source and sink NEs, and cannotbe used by any intermediate NEs between the source and sink NEs. If you want to change thesource and sink NEs of a configured VC4 server trail, you can use the joining and splittingfunctions.

2.1.19 Service Authorization ManagementIf there are multiple service trails maintained by different operators, they may care about onlythe trails in their own responsibility but ignore the other services. Service authorization can filterthe information not in concern of an operator, who then views and manages only the trails in theresponsibility. In this manner, the management and maintenance efficiency is improved.

2.1.20 Viewing SDH TrailsBy viewing SDH trails, you can learn about the distribution and usage of the SDH trails in thenetwork.

2.1.21 Maintaining SDH TrailsYou can check and maintain SDH trails to find potential faults in the earliest time.

2.1.22 Deleting SDH TrailsThe deletion of needless SDH trails releases relevant network resources.

2.1.1 Configuration Task FlowA configuration task flow describes the operation tasks that manage an RTN network by usingthe end-to-end function of the U2000. In addition, the relationships between the operation tasksare described.

Referring to the Figure 2-1, configure and manage an RTN network.



2-3

Figure 2-1 End-to-end RTN network management flow

Configure atrail

Maintain atrail

Create anSDH trail View trails

Switch trails

Configureoverheads

Modify a trail

Disable aserver trail

Merge servertrails

Delete a trail

Managealarms

Manageperformance

Configure aprotection subnet

Create aradio trail

Create aplatinumservice

Optional

Mandatory

NOTE

l When you create a Client or an ODUk trail whose source or sink is an NG WDM NE, you need to setthe working mode of the card, and service mode and service type of the port. For details, see ConfiguringBoard Parameters.

l When you create a Client or an ODUk trail in a network that consists of NG WDM NEs, you can createthe trail on an OCh server trail directly. Specifically, cross-layer creation is supported and the U2000can create mid-layer server trails automatically.

In the landscape orientation of the configuration flow diagram, the main phases of managing anRTN network by using the end-to-end function of the U2000 are shown, that is, configuring andmaintaining a trail. All these functions require the corresponding license that provides the end-to-end management function.

The portrait orientation of the flow chart shows the relations between operation tasks in eachphase.

2.1.2 Basic ConceptsThis section describes the basic concepts of the end-to-end management.




Issue 02 (2010-09-24)

2.1.2.1 SDH TrailThis section describes the definition, level and related knowledge of the SDH trail.

2.1.2.2 Radio TrailsDescribes the definition of the radio trail and related information about the radio trail.

2.1.2.3 Conflict TrailIf a trail exists on the U2000, but the cross-connection that forms the trail does not exist at theNE layer, this trail is a conflict trail.

2.1.2.4 Trail Creation MethodThe U2000 provides multiple methods for creating trails to meet different operation habits ofusers and requirements of different service scenarios.

2.1.2.5 Process for Creating a TrailThe trail creation process describes a series of procedures before a trail is generated on theU2000. The detailed process varies with the creation method.

2.1.2.6 Trail Protection StrategyDuring trail creation, if multiple routes exist between the source and sink of the trail and theroutes belong to different protection subnets, you can use a protection priority strategy toautomatically select a route. In the case of sharing of protection subnet resources on the sameroute, you can also select a different protection priority strategy to determine a protection subnetthat the trail uses on this route.

2.1.2.7 Trail Resource Use StrategyResource use strategies specify the protection subnet resources or timeslots that can be usedwhen the U2000 automatically computes a route during trail creation.

2.1.2.8 Principles for Selecting Timeslots During the Trail CreationAfter the working and protection routes are defined through the route computation, the U2000defines the detailed timeslots that each segment of the working or protection route of the trailpasses through, according to the networking, the requirement that whether the same timeslotsare used, and different schemes for managing timeslot resources.

2.1.2.9 Platinum Service GroupThe platinum service group is the combination of multiple trails. Any two trails in the group donot pass through the same NE, fiber, or fiber/cable pipe. In this way, services are not hardlyinterrupted.

2.1.2.1 SDH Trail

This section describes the definition, level and related knowledge of the SDH trail.

Definition

The U2000 network-layer management functions enable the U2000 to implement the SDHservice end-to-end management. By using the SDH end-to-end management function, anauthorized U2000 user can perform the following operations:

l Configure end-to-end services.

l View the routes of a trail through the GUI.

l View details of a trail.

l Quickly filter, search for and locate trails.



2-5

l Manage and maintain trails in a centralized manner.l Manage alarms and performances based on trails.l Print trail reports.

Purpose and Gain

The U2000 provides graphic wizards to display information and guide you to perform SDH end-to-end management operations. In this way the operations on the U2000 are performed in anintuitive manner. An SDH trail can be created in the following three modes: automatic, semi-automatic and manual.

l Using the automatic mode, you only need to specify the source node, sink node and portsfor a trail.

l Using the semi-automatic mode, you can specify the routes and timeslots that a trail passes.l Using the manual mode, you need to manually specify the routes and timeslots for a trail.

The end-to-end management is the core of the U2000 network-layer functions. The trail-basedway of management greatly simplifies the operation of service configuration and thus reducesthe chances of misoperation.

l Without the end-to-end management function, configuring a trail requires completelymanual operations. For example, to configure a 2M trail that is added from an NE anddropped to the number n NE after passing n NEs, you need to configure cross-connectionson each of the n+1 NEs.

l With the help of the end-to-end management function, configuring such a trail is muchsimplified. You can ignore the intermediate n-1 nodes. The U2000 automatically generatesa trail after you specify the source port and sink port of the trail.

Availabilityl Involved NE: The U2000 SDH end-to-end management function is applicable to all SDH

and RTN NEs.l license support: SDH end-to-end management is an optional feature of the U2000. It is

controlled by license. Hence, the SDH end-to-end management function is available onlyafter a license that supports this feature is obtained.

l Supporting version: The U2000 V100R001 and later versions support the SDH end-to-endmanagement feature.

Impactl Impact on system performance: If the requirements for the U2000 system are met and if

the U2000 runs normally, SDH end-to-end management does not impose severe impactson the system. However, the system performance is likely to be affected if the U2000 runsin heavy load.

l Impact on other features: The SDH end-to-end management is based on the fiberconfiguration and the protection subnet configuration. The data end-to-end management,if any, is based on the SDH end-to-end management.

SDH Trail Level

Table 2-1 lists the SDH trail levels.




Issue 02 (2010-09-24)

Table 2-1 SDH trail level

Trail Level Rate (Mbit/s)

VC12 2

VC3 34

VC4 155

NOTE

For a trail of the VC12 or VC3 level, you need to create a VC4 server trail first.

PrincipleThe following describes the principles for the automatic creation of end-to-end SDH trails.

l A user selects the source, sink and the level of the trail to be created on the U2000 GUI.l The U2000 automatically calculates the routes for the trail and displays the routes on the

GUI.l The user confirms the trail routes and delivers the command of trail creation.l The U2000 creates the trail according to the source, sink and routes of the trail, calculates

corresponding cross-connections and gives them down to NEs.

In this way, an end-to-end SDH trail is created on the U2000 and at the same time, the serviceis automatically delivered to related NEs.

ImplementationSDH end-to-end management is an optional function, available only after a license that supportsthis function is provided.

2.1.2.2 Radio TrailsDescribes the definition of the radio trail and related information about the radio trail.

DefinitionRadio trails are classified into PDH radio trails and SDH radio trails.

Radio end-to-end management refers to the end-to-end management of radio services by usingthe network-level management function of the U2000. With the radio end-to-end managementfunction, the user can perform the following operations:

l Configures end-to-end services.l View the routes of a trail through the GUI.l Queries details on trails.l Quickly filters, searches for, and locates trails.l Manages and maintains trails in a centralized manner.l Manages alarms and performance events by trail.



2-7

l Prints trail reports.

Objective and Benefit

In the case of radio end-to-end management, the operations are performed and displayed in agraphic wizard, which makes the operations vivid. A radio trail can be created in the semi-automatic mode, automatic mode, or manual mode.

l Automatic mode: Specify only the source node and sink node, and the port on each node.l Semi-automatic mode: Optionally specify the routes that the trail traverses along and

involved timeslots.l Manual mode: Manually specify each route that the trail traverses and each involved

timeslot.

End-to-end management is the key network-level function of the U2000. Configuring servicesby means of trail management simplifies the operations and reduces the error likeliness to a greatextent.

l If the end-to-end management function is unavailable, configuration of a trail is totallybased on manual operations. For example, a required 2 Mbit/s trail starts from an NE,traverses N-1 NEs, and finally ends at the Nth NE. To configure such a 2 Mbit/s trail, youneed to configure timeslot cross-connections on each of the N NEs.

l The end-to-end function makes configuration of such a trail as simple as to specify onlythe source port and sink port. Then, the U2000 generates the required trail.

Availabilityl Involved NEs: The radio end-to-end management function of the U2000 is intended to

manage all RTN NEs.l License support: The radio end-to-end management feature is optional for the U2000 and

is controlled by a license file. The radio end-to-end management function is available onlywhen the required license file is provided.

l Version support: The radio end-to-end management function is supported by the U2000 ofV100R001 or any later version.

Impactl Impact on System Performance

On the required conditions for the management capability of U2000, the radio end-to-endmanagement does not cause great impact on system performance. If the U2000 works withoverload, the system performance, however, is definitely affected.

l Impact on Other FeaturesThe end-to-end radio trail management is based on configuration of fibers and protectionsubnets. The data end-to-end function, if made available, depends on the radio end-to-endfunction.

Principles

The principle for automatic creation of a radio end-to-end trial is as follows:

l The user selects the level, source, and sink for the trail to be created on the U2000.




Issue 02 (2010-09-24)

l The U2000 automatically computes the routes for the trail and displays the routes in theuser interface.

l The user checks the routes for the trail and confirms creation of the trail.l The U2000 creates the trail according to the source, sink, and routes, computes the cross-

connections, and delivers the configuration to NEs.

In this way, one end-to-end radio trail is created on the U2000. Also, the trail configuration isdelivered to NEs for trail setup.

ImplementationThe radio end-to-end function is optional and is available only when the required license file isprovided.

2.1.2.3 Conflict TrailIf a trail exists on the U2000, but the cross-connection that forms the trail does not exist at theNE layer, this trail is a conflict trail.

CauseA trail consists of a single station cross-connection at the NE layer. If the configuration data atthe NE layer changes and a complete trail cannot be formed at the network layer, the trail thatexists on the U2000 is a conflict trail, and the corresponding cross-connection at the NE layerbecomes a discrete service.l Adding a fiber leads to trail extension.

Assume that a trail is NE A-> NE B. Create a fiber from NE B to NE C, and create a serviceon NE C. As a result, the trail is extended as NE A->NE C. The trail NE A-> NE B thatexists on the U2000 becomes a conflict trail. See Figure 2-2.

Figure 2-2 A conflict trail generated because a fiber is added

NE A NE B NE C

l The single station cross-connection is lost.

The original trail is NE A-> NE C. The cross-connection of the trail on NE B is deleted.On the U2000, the original trail of NE A-> NE C becomes a conflict trail and services onNE A and NE C become discrete services. See Figure 2-3.

Figure 2-3 A conflict trail generated because a single station cross-connection is lost

NE A NE B NE C



2-9

l Delete a protection service on a per-NE basis.

NE 1 and NE 2 comprises a 1+1 linear protection and the original trail is NE 1-> NE 2. Ifcross-connection D of NE 2 is deleted, the original trail of NE 1-> NE 2 becomes a conflicttrail. See Figure 2-4.

Figure 2-4 A conflict trail generated because a protection service is deleted on a per-NEbasis

Working Trail

Protection Trail

NE1 NE2

Cross-ConnectionA

Cross-ConnectionB

Cross-ConnectionC

Cross-ConnectionD

Handling Method

During trail search, if the U2000 searches out a conflict trail, the U2000 stops the searching andasks you to confirm the conflict trail. There are the following two handling methods:

l Stop searching.

If you fail to verify that the conflict trail is correct, you can choose to stop searching. Theconflict trail remains, but the U2000 does not generate a new trail.

l Continue to search.

The system deletes the conflict trail from the network layer. This operation does not deletethe cross-connection on a per-NE basis, and does not affect services on the NE.

NOTE

After the conflict trail is deleted, its customized information, including the trail name, remarks, ispermanently lost and cannot be restored.

2.1.2.4 Trail Creation Method

The U2000 provides multiple methods for creating trails to meet different operation habits ofusers and requirements of different service scenarios.

To successfully create a trail on the U2000, the following prerequisites must be met:

l All the NEs that the trail passes through must have enough idle resources.

l The data on the U2000 must be consistent with the data on the NE.

l The fibers on the U2000 are correctly connected.

Table 2-2 shows the methods, features, and application scenarios of the trail creation.




Issue 02 (2010-09-24)

Table 2-2 Comparison of methods for creating trails

Trail Creation Method Feature Application Scenario

Creating trails by trail search On a per-NE basis, configureall nodes that a service passesthrough. Then, by using thenetwork-layer trail searchfunction, combine cross-connections of each node toform end-to-end trails.

This method is applicable tothe scenario that the service isalready configured on a per-NE basis.This method requires bettertechnical knowledge ofusers. During the search,users may need to handleconflict trails and discreteservices.

Creating trails in theautomatic mode

l The service is configureddirectly at the networklayer. After the activationof the trail, the U2000deliver the cross-connections related to thetrail to all NEs involved.

l The route can becomputed automatically.

l If multiple routes existbetween the selectedsource and sink, you canset to select a route.

This method is applicable tothe creation of a majority ofnormal trails.

Creating trails in the manualmode


l The method does notsupport the automaticroute computation, andthus you need to manuallyadd all segments of theroutes.

This method is applicable tocertain special trails, such asthe mono nodal trail whosesource and sink are the sameNE, the trail that passesthrough a DNI protectionsubnet, the trail with multiplesources and sinks, and thebroadcast trail. This methodis usually used to createbroadcast services.Operations of this functionare complicated. Thus, thisfunction is not recommendedfor the creation of normaltrails.



2-11

Trail Creation Method Feature Application Scenario

Creating trails by trailreplication


l The route can becomputed automatically.

l You can only use theexsiting trail on theU2000 as a template andcreate the trails with thesame route in batches.

This method is applicable tothe batch creation of trailswith the same route, that is,the trails share the samesource, sink, and server trailwith the original trail.

2.1.2.5 Process for Creating a TrailThe trail creation process describes a series of procedures before a trail is generated on theU2000. The detailed process varies with the creation method.

Figure 2-5 shows the process for creating trails by trail search. Figure 2-6 shows the processfor creating trails in the automatic mode. Figure 2-7 shows the process for creating trails in themanual mode.

Creating trails by trail replication depends on the existing trail on the U2000. The process issimilar to the process of creating trails in the automatic mode.




Issue 02 (2010-09-24)

Figure 2-5 Creating trails by trail search

End

Y

N

Obtain all cross-connectionsof NEs networkwide

Y

Stop the trail search

N

Check whetherdiscrete services that do

not form trails exist

Y

N

Start

Sort cross-connections by level

Search out trails at the serverlayer and then the client layer

Check whethernew trails conflict with

original trails

The network managementsystem starts to manage

new trails

The information about discreteservices is displayed

The searched is paused andconflicting trails are displayed

Whether to resumethe searchDelete conflicting trails



2-13

Figure 2-6 Creating trails in the automatic mode

End

Y

N

Check whether theserver trail for the trail to

be created exists

N

Y

Set trail attributes, such as thedirection, level, and rate

Set the resource use strategyand protection priority strategy

(optional)

Set the source and sink NEsfor the trail

Set route restriction conditionsrelated to the node, link, and

timeslot (optional)

Whether to set thetrail as an SNCP trail

Set basic attributes for the trail

Activate the trail

Start

Set the SNCP protection route

Create or search out theserver trail




Issue 02 (2010-09-24)

Figure 2-7 Creating trails in the manual mode

End

Check whether theserver trail for the trail to

be created exists

N

Y

Start

Set trail attributes, such as thedirection, level, and rate

Set the source and sink NEsfor the trail

Specify the routes that the trailpasses through section by

section

Set basic attributes for the trail

Activate the trail

Create or search out theserver trail

2.1.2.6 Trail Protection StrategyDuring trail creation, if multiple routes exist between the source and sink of the trail and theroutes belong to different protection subnets, you can use a protection priority strategy toautomatically select a route. In the case of sharing of protection subnet resources on the sameroute, you can also select a different protection priority strategy to determine a protection subnetthat the trail uses on this route.

The U2000 provides three protection priority strategies, that is, Trail Protection First, SNCPFirst, and NP First, as shown in Table 2-3. Based on different protection priority strategies,the protection subnets have different priorities.



2-15

Table 2-3 Priority relations of protection strategies

Priority Trail ProtectionFirst

SNCP First NP First

1 Two-fiberbidirectional MSshared protectionring

DNI Non-protection

2 Four-fiberbidirectional MSshared protectionring

SNCP protection SNCP protection

3 Two-fiberunidirectional MSdedicated protectionring

Two-fiberunidirectional PPring

Two-fiberbidirectional PP ring

4 MS linear protection1:N

Two-fiberbidirectional PP ring

Two-fiberunidirectional PPring

5 MS linear protection1+1

MS linear protection1+1

MS linear protection1+1

6 Non-protection MS linear protection1:N

MS linear protection1:N

7 SNCP protection Two-fiberunidirectional MSdedicated protectionring

Two-fiberbidirectional MSshared protectionring

8 Two-fiberbidirectional PP ring

Four-fiberbidirectional MSshared protectionring

Four-fiberbidirectional MSshared protectionring

9 Two-fiberunidirectional PPring

Two-fiberbidirectional MSshared protectionring

Two-fiberunidirectional MSdedicated protectionring

10 DNI Non-protection DNI

Application Example of Trail Protection StrategiesAccording to priority relations of protection strategies, when you select SNCP First, the pathprotection is prior to the non-protection.

When the path protection and non-protection share resources on a route, if you want to configurethe service to a path ring to obtain the ring protection by using the trail management function,you must set Protection Priority Strategy to SNCP First.




Issue 02 (2010-09-24)

2.1.2.7 Trail Resource Use StrategyResource use strategies specify the protection subnet resources or timeslots that can be usedwhen the U2000 automatically computes a route during trail creation.

U2000 defines three resource use strategies. That is, Protected Resource, Extra Resource, andAll Resource. The principles for selecting the resource use strategies are as follows:l Protected Resource: During trail creation, the following resources are available: PP,

SNCP, non-protection, 1+1 protection, protection timeslots of an MSP ring, and protectiontimeslots of 1:1 protection. Select this strategy to create trails in general situations.

l Extra Resource: During trail creation, the following resources are available: non-protection, extra timeslots of an MSP ring, and extra timeslots of 1:1 protection. Select thisstrategy to create extra trails.

l All Resource: During trail creation, the following resources are available: PP, SNCP, non-protection, 1+1 protection, protection timeslots of an MSP ring, extra timeslots of an MSPring, protection timeslots of 1:1 protection, and extra timeslots of 1:1 protection. Thisstrategy means that all resources can be used.

Application Example for Resource Use Strategiesl If you want to create a trail that uses the extra timeslots of the PP ring and MSP ring, you

should select the All Resource strategy. If you select the other two options, a trail of thistype cannot be created.

l If the non-protection subnet and the protection subnet without extra resources exist, duringthe trail creation, the Extra Resource strategy cannot be used to create trails on the non-protection subnet.

2.1.2.8 Principles for Selecting Timeslots During the Trail CreationAfter the working and protection routes are defined through the route computation, the U2000defines the detailed timeslots that each segment of the working or protection route of the trailpasses through, according to the networking, the requirement that whether the same timeslotsare used, and different schemes for managing timeslot resources.

The process for selecting timeslots during the trail creation is a process that consists of the checkof available timeslot resources and the computation of detailed timeslots.

Management of Timeslot ResourcesThe U2000 provides two schemes for managing timeslot resources, as shown in Table 2-4. Theydiffer from each other in the methods of saving idle resources. The two schemes complementeach other and can define timeslots for a majority of networking. The U2000 often combine theworking and protection routes and then define timeslots. If the U2000 fails to define timeslots,the U2000 defines timeslots for the working and protection routes respectively, combine theworking and protection routes, and verify whether the timeslots conflict with each other.



2-17

Table 2-4 Scheme for managing timeslot resources

Scheme for ManagingTimeslot Resources

Advantage Disadvantage

All idle resources of routesare managed in a uniformmanner.

It is easy to handle a normalsituation.

l The situation that theprotection subnet is ofresource sharing or theprotection subnet isdivided according to VC4cannot be handled.

l The situation that theforward and inverseresources are notsymmetrical cannot behandled.

Each segment of working orprotection route manages theavailable resources on itsown route respectively.

l The situation that theprotection subnet is ofresource sharing or theprotection subnet isdivided according to VC4can be handled.

l The situation that theforward and inverseresources are notsymmetrical can behandled.

l The resources for eachsegment of the route aresaved respectively. Thus,the handling of timeslotscan be flexible.

When you calculate detailedtimeslots, you shouldconsider saving forward andinverse resourcesrespectively and the forwardand inverse resource shouldbe symmetrical wheneverpossible.

Principles for Calculating Timeslots

The timeslot calculation must follow certain rules. For example, the timeslot that is occupied byeach segment of the route on the MSP ring must be consistent and, on the release 4.0 NEs, thetimeslots that are used by a dual fed and selective receiving service must be the same. Theselimitations or optimization schemes form the principles for calculating timeslots. The details areas follows:

l Principle for binding timeslots: Certain segments of the route are bound. When the timeslotfor a certain segment of the route is updated, the timeslots for other segments of the routeare updated. For example, in the case of the unidirectional MSP on the trail, you shouldbind the forward and inverse timeslots, that is, the forward and inverse timeslots should besymmetrical whenever possible.

l Principle for reducing timeslots: With consideration of all situations, reduce idle timeslotsgradually and select available timeslots from the remaining idle timeslots. For example, tomake inverse and forward routes to use the same timeslots, you should reduce the inverseresources according to the existing forward resources.




Issue 02 (2010-09-24)

Situation That Timeslots Cannot Be Defined AutomaticallyIn the case of a minority of networking, if you create a cross-ring E4 service on intersecting pathprotection shared rings, the U2000 cannot select timeslots automatically. Thus, you need tospecify the explicit timeslots for all segments of the route manually. If the timeslots failed to bedefined, check whether there are enough idle timeslots in the forward and inverse directions ofthe server trail and check whether the selected explicit timeslots are correct.

2.1.2.9 Platinum Service GroupThe platinum service group is the combination of multiple trails. Any two trails in the group donot pass through the same NE, fiber, or fiber/cable pipe. In this way, services are not hardlyinterrupted.

As shown in Figure 2-8, a bidirectional service exists between Router1 and Router2 and thisservice is displayed as trail A between NE1 and NE2 in the management scope of the U2000.To protect the service, another bidirectional trail needs to be added between the two routers andthis trail is displayed as trail B between NE3 and NE4 in the management scope of the U2000.When you create trail B, trail A is considered as a reference trail so that the two trails do notpass through the same NE, fiber, or fiber/cable pipe. In this way, the risk that the two trails areinterrupted at the same time is lowered. Therefore, trail A and trail B form a platinum servicegroup.

Figure 2-8 Platinum service group

The platinum service group must meet the requirements as follows:l A platinum service group contains a minimum of two trails.l The trails cannot pass through the same NEs.l The trails cannot pass through the same fiber.l The trails cannot pass through the same fiber/cable pipes.

When a third trail needs to be added into the platinum service group, you only need to specifythe existing trail A or trail B as the reference trail and then the U2000 automatically searchesout the two existing trails and groups the three trails.

NOTE

You can also bind the existing trails to generate a platinum service group.



2-19

As shown in Figure 2-8, when the platinum service group is no longer required, you can removetrail B from the platinum service group instead of deleting trail B. In this way, trail A and trailB are independent of each other and their routes are not mutually constrained. If rerouting occursor the route is modified, the two trails may pass through the same NE, fiber, and fiber/cable pipe.

When you create trails, different trails cannot fully comply with the requirements of the platinumservices due to insufficient resources and then you can create downgraded platinum services.As shown in Figure 2-9, trail A and trail B pass through NE5 and thus you can create only adowngraded platinum service group. A downgraded platinum service group cannot provide theexpected protection of a platinum service group. For example, when NE5 is faulty, theconnection between Router1 and Router2 is interrupted. To make the service group fully complywith the requirements of the platinum service, you can change the route of trail B to the routeof trail C between NE3 and NE4, when resources are sufficient.

Figure 2-9 Downgraded platinum service group

A platinum service group contains multiple trails. Therefore, the service is not interrupted unlessall trails are interrupted. After detecting the interruption of a certain trail, the U2000 checkswhether other trails in the platinum service group are interrupted. If a complete trail exists, theseverity of the service interruption alarm is reduced to a lower level.

When the platinum service group does not meet the requirements due to a certain cause, theplatinum service group is in the downgraded state and the U2000 reports an alarm about thedowngrade of the platinum service.

2.1.3 Disabling a FiberCertain fibers may be deleted during O&M. Those fiber resources are not used when you createa trail. Therefore, you can disable those fibers.

Prerequisitel You must be an NM user with "network administrator" authority or higher.

l When both ends of a fiber are connected to the SDH equipment, the fiber can be disabled.When both ends of a fiber are connected to the WDM equipment or Ethernet cards, thefiber cannot be disabled. When one end of a fiber is connected to the SDH equipment andthe other end is connected to the WDM equipment, the fiber cannot be disabled.

Procedure

Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the Main Menu.

Step 2 Select the fiber/cable to be disabled and click Modify Fiber/Cable.

Step 3 In the dialog box that is displayed, double-click Disabled Status and select from Disable thedrop-down list.

Step 4 Click OK.

Step 5 In the Operation Result dialog box, click Close.

----End




Issue 02 (2010-09-24)

2.1.4 Creating SDH Trails by Trail SearchFor the SDH trails created by trail search, the configured services on each NE are displayed onthe U2000 in an end-to-end form. In this way, you can view and manage the routes and resourcesoccupied of each service in an intuitive manner.

2.1.4.1 Searching for SDH TrailsAfter a new network is set up or services are configured on a per-NE basis, you need to performan SDH trail search so that you can manage configured services by using the trail managementfunction.

2.1.4.2 Viewing Discrete ServicesIf some cross-connections on an NE cannot form trails of the network layer and can only beisolated on the NE, these cross-connections are called discrete services.

2.1.4.3 Discrete Service Causes and Handling MeasuresAfter trail search, discrete services are usually caused by the following factors, which areunsatisfied trail search conditions, U2000 trail search restrictions, incomplete or wrongconfiguration of cross-connections.

2.1.4.4 Setting the Remarks of a Discrete ServiceWhen managing discrete services, you can set the remarks of a discrete service.

2.1.4.5 Activating and Deactivating Discrete ServicesIf certain cross-connections on NEs cannot form network-layer trails but exist on NEs separately,these cross-connections are called discrete services. Deactivating discrete services deletes theNE cross-connections from NEs and saves the relevant data on the U2000 only. This operationhelps to release the occupied channels. On the contrary, activating discrete services deployscross-connections to NEs according to the data saved on the U2000.

2.1.4.6 Acknowledging or Unacknowledging Discrete ServicesIn this user interface, you can acknowledge discrete services and filter discrete services basedon their acknowledgment status.

2.1.4.7 Deleting Discrete ServicesDiscrete services occupy the cross-connections required by normal services. As a result, normalservices cannot be created. Therefore, you need to delete the discrete services that are not in use.

2.1.4.1 Searching for SDH Trails

After a new network is set up or services are configured on a per-NE basis, you need to performan SDH trail search so that you can manage configured services by using the trail managementfunction.


l The license for the trail management function must be provided.

l NE data must be uploaded to the U2000.

l Fiber connections between the NEs must be created correctly.

l All the desired services that are configured on a per-NE basis must be active when trailsare created through trail search.



2-21

Context

The search only updates the trail information at the network layer on the U2000. The serviceoperation or the configuration data of the NE is not affected by the search.

In the searching progress, the U2000 does not permit another SDH trail search, a search for SDHprotection subnets, or creation of SDH trails.

Procedure

Step 1 Choose Service > SDH Trail > Search for SDH Trail from the Main Menu.

Step 2 Optional: Select a proper Search Strategy if necessary.

NOTE

l Search Discrete Cross-Connections Only: searches for all discrete cross-connections that do not formtrails in the entire network.

l Search By Subnet: searches for trails only in the specific subnet.

Step 3 In the Search for SDH Trail wizard displayed, click Next to start the trail search.

NOTE

If an end-to-end trail cannot be formed due to the conflict of cross-connections, the information about thecross-connections in conflict is displayed. The search can only be continued after deleting the conflictingtrails. Deleting conflicting trails does not affect services.

Step 4 The search process lasts for some time, with the specific duration depending on the number ofservices. Wait until the search is complete as indicated by the progress bar, and then clickNext to view the trail information.

Step 5 Optional: Select a trail and right-click to set the management flag.

NOTE

The management flag indicates whether the trail is included in the network trail management. By default,the trail is under management. If you exclude the trail from the network trail management, you can alsomanage cross-connections of single NEs during station-by-station service configuration.

Step 6 Click Next and the trails that are searched out without the management flags are deleted fromthe network layer by the U2000. This operation does not affect the NE services or the NM dataof single NEs. You can then view all discrete services (that is, the cross-connections that cannotform trails) in the network.


----End

2.1.4.2 Viewing Discrete Services

If some cross-connections on an NE cannot form trails of the network layer and can only beisolated on the NE, these cross-connections are called discrete services.





Issue 02 (2010-09-24)

Procedure

Step 1 Choose Service > SDH Trail > Manage SDH Discrete Service from the Main Menu.

Step 2 In the Prompt dialog box displayed, click OK.

Step 3 In the Set Discrete Service Browse Filter Criteria dialog box displayed, select the filter criteriaand click Filter. In the Manage SDH Discrete Service window, you can view details of thediscrete services and causes of forming these services.

----End

2.1.4.3 Discrete Service Causes and Handling MeasuresAfter trail search, discrete services are usually caused by the following factors, which areunsatisfied trail search conditions, U2000 trail search restrictions, incomplete or wrongconfiguration of cross-connections.

Causes of Discrete Services1. Unsatisfied trail search conditions

l The data on the U2000 is inconsistent with those on NEs.l The fibers created on the U2000 do not match actual fiber connections.l Protection subnets are not created or cannot be searched.l The NE data configuration is incorrect. For example, a non-protection chain service is

created on the protection ring, the NE logic system of the service does not belong toany protection subnet, or the protection subnet configuration is wrong.



2-23

2. U2000 trail search restrictionsl If the VC4 server trail is created between two NEs but the lower order (VC12 and VC3)

trails are not created, the services are not sent to NEs. In this case, when anotherU2000 performs the trail search on these two NEs, the VC4 server trail cannot besearched out.

l In a VC4 server trail with multiple sources and multiple sinks, if some sources or sinksare on SDH NNIs and others are on common optical and electrical interfaces, the trailcannot be searched.

3. Incomplete or wrong configuration of cross-connectionsl The timeslot for the protection route is not configured. This often happens in a PP or

SNCP protection subnet.l The timeslot configured for the protection route is wrong.l The SNCP service configuration is wrong, which results in an incomplete protection

route.l The service configuration is incomplete. Check whether incomplete services are

configured in the station-by-station mode, for example, pass-through services may notbe configured on pass-through NEs. You should complete this service configurationand search for the trails again.

Handling Discrete Services1. Method I:

(1) Perform a consistency check to check whether the data on the U2000 and the data onthe NEs are consistent or not. If not, upload the configuration data to the U2000.

(2) Verify that the fiber connections created on the U2000 are consistent with the actualfiber connections, and that there are no errors like wrong fiber connection on theU2000.

(3) Search for protection subnets. Verify that all the protection subnets are searched.Check whether the parameters for protection subnets and the logical system of eachnode are set correctly, and whether SDH NNIs are created for SDH NNI services.

(4) Perform a trail search on the U2000.(5) If discrete services are found, analyze and handle them according to the causes

displayed on the U2000 and the handling measures that are given above. It isrecommended that you handle the discrete services at add/drop tributaries first, thenhandle the those SDH NNI discrete services, and finally the pass-through discreteservices.

2. Method II: Convert discrete services to mono nodal trails. For detailed operations, see2.1.21.7 Converting SDH Discrete Services to Mono Nodal Trails.

How to Avoid Discrete Services

Use the trail management function to configure services whenever possible. This is becauseservices configured in this way do not form discrete services. When a discrete service is found,handle it as soon as possible so that it does not affect subsequent service configuration.

2.1.4.4 Setting the Remarks of a Discrete Service

When managing discrete services, you can set the remarks of a discrete service.




Issue 02 (2010-09-24)

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

ContextWhen the NMS receives notifications like deleting cross-connections or fibers, trails may bedeleted. As a result, discrete services exist. The remarks of these discrete services automaticallyrecord the original path.

Procedure



Step 3 In the Set Discrete Service Browse Filter Conditions dialog box displayed, select the filtercriteria and click Filter. In the Manage SDH Discrete Service window, you can view detailsof the discrete services and causes of forming these services.

NOTEIn the remarks of the Set Discrete Service Browse Filter Conditions dialog box, enter the keyword. Then, youcan perform a fuzzy query for discrete services by remarks.

Step 4 Select a discrete service, right-click, and then choose Remarks from the shortcut menu.

Step 5 In the dialog box that is displayed, set the remarks of the discrete service, and click OK.

----End



2-25

PostrequisiteYou can click the table header to sort discrete services by remarks.

2.1.4.5 Activating and Deactivating Discrete ServicesIf certain cross-connections on NEs cannot form network-layer trails but exist on NEs separately,these cross-connections are called discrete services. Deactivating discrete services deletes theNE cross-connections from NEs and saves the relevant data on the U2000 only. This operationhelps to release the occupied channels. On the contrary, activating discrete services deployscross-connections to NEs according to the data saved on the U2000.


Procedure


Step 2 In the prompt dialog box, click OK.

Step 3 In the Set Discrete Service Browse Filter Criteria dialog box, set the filter criteria, and clickFilter.

Step 4 Optional: Select one or more inactive discrete services, right-click, and then choose Activefrom the shortcut menu.

Step 5 Optional: Select one or more active discrete services, right-click, and then choose Deactivatefrom the shortcut menu.

NOTE

When activating or deactivating discrete services in batches each time, you can select a maximum numberof 1,000 records. Otherwise, the Active or Deactivate menu grays out.



----End

2.1.4.6 Acknowledging or Unacknowledging Discrete ServicesIn this user interface, you can acknowledge discrete services and filter discrete services basedon their acknowledgment status.


ContextDiscrete services occupy network resources and this may affect the successful creation of trails.Therefore, you can acknowledge unnecessary cross-connections. In this way, another networkmaintainer can determine whether a discrete service is an unnecessary cross-connection basedon the acknowledgment status. If unnecessary, the maintainer deletes the service.




Issue 02 (2010-09-24)

Procedure


Step 2 In the dialog box displayed, click OK.

Step 3 In the Set Discrete Service Browse Filter Criteria dialog box, set filter criteria and clickFilter.

Step 4 Optional: In the list, select one or more discrete services that are not acknowledged, right-click,and choose Acknowledge from the shortcut menu.

Step 5 Optional: In the list, select one or more discrete services that are acknowledged, right-click,and choose Cancel Acknowledgement from the shortcut menu.


NOTE

Right-click one or more discrete services and choose Remarks from the shortcut menu. In the Remarksdialog box, enter detailed descriptions of the discrete services.

----End

Resultl If a discrete service is acknowledged, Acknowledge Status of the service is Yes.l If a discrete service is not acknowledged yet, Acknowledge Status of the service is No.

Postrequisitel When viewing discrete services, you can filter the services based on their acknowledgment

status.l To release resources, you can delete the discrete services that are acknowledged. For

detailed operations, see 2.1.4.7 Deleting Discrete Services.

2.1.4.7 Deleting Discrete ServicesDiscrete services occupy the cross-connections required by normal services. As a result, normalservices cannot be created. Therefore, you need to delete the discrete services that are not in use.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The discrete services to be deleted must be in the inactive state.

Procedure



Step 3 In the Set Discrete Service Browse Filter Criteria dialog box, set the filter criteria, and clickFilter.

Step 4 Select one or more discrete services to be deleted, right-click, and then choose Delete from theshortcut menu.



2-27

NOTE

When deleting discrete services in batches each time, you cannot select inactive and active discrete servicesand can select a maximum number of 1,000 records. Otherwise, the Delete menu grays out.



----End

2.1.5 Automatically Creating VC4 TrailsIf you want to create SDH services of the E4, STM-1 levels, you can complete the serviceconfiguration quickly by creating end-to-end VC4 trails.

2.1.5.1 Creating a Non-SNCP VC4 TrailBy creating an end-to-end VC4 trail, you can quickly create an E4, STM-1 SDH service withoutSNCP. In different protection subnets, the methods for creating a non-SNCP VC4 trail are thesame.

2.1.5.2 Creating an SNCP VC4 TrailBy creating an end-to-end VC4 trail, you can quickly create an E4, STM-1 SDH service withSNCP. The methods for creating an SNCP VC4 trail are the same in different protection subnets.

2.1.5.3 Verifying the SNCP Trail Protection SwitchingTo detect faults on NEs or on fibers through which an SNCP trail passes, the maintenanceengineers can check the switching status of the trail. The engineers can then locate the pointwhere the fault is generated according to the switching status of each NE in the protection subnet.

2.1.5.1 Creating a Non-SNCP VC4 Trail

By creating an end-to-end VC4 trail, you can quickly create an E4, STM-1 SDH service withoutSNCP. In different protection subnets, the methods for creating a non-SNCP VC4 trail are thesame.


l The license for the trail management function must be provided.

Context

When creating the VC4 trail, you do not need to create a server trail.

Procedure

Step 1 Choose Service > SDH Trail > Create SDH Trail from the Main Menu.

Step 2 Set the service direction according to the protection subnet type. Set the service level to VC4 orVC4-Xc.

Step 3 Set the Service Domain, Resource Usage Strategy and Protection Priority Strategy.




Issue 02 (2010-09-24)

NOTE

l Resource Usage Strategy defines the protection subnet resources or timeslots available during trailcreation. The values are Protected Resource, Extra Resource and All Resource.

l Protection Priority Strategy defines the protection subnet resources that must be selected first duringtrail creation. The values are Trail Protection First, SNCP First and NP First.

Step 4 Optional: On the main topology in the right pane of the trail creation window, right-click therequired NE, and then choose Browse Alarms List from the shortcut menu. Then, you can viewthe alarms of the NE. This operation helps to plan and configure services in a better way.

Step 5 Double-click the source NE and the sink NE in turn. Select the board and port in the SelectBoard Port dialog box and click OK. The trail is automatically selected, and is displayedbetween the source and sink NEs.

Step 6 Optional: Specify the explicit link of the service.

l Click a server trail between the NEs to specify the included route. Click the trail again orclick Cancel Route Restriction to cancel the selection.

l Click the Explicit Link tab. Right-click the blank area in the tab and choose Add from theshortcut menu. In the Add Explicit Link window displayed, you can search for the existingserver trails and set them as the explicit links of the trails to be created.

Step 7 Optional: Specify the explicit node.

l Click the Explicit Node tab. Double-click an NE of the subnet to specify the explicit NEof the route. This NE is shown as the icon. Double-click the NE again to cancel theselection.

l Click the Explicit Node tab. Right-click the blank area in the tab and choose Add from theshortcut menu. In the Add Explicit Node window displayed, you can search for the nodesand set them as the explicit nodes of the trails to be created.

Step 8 Optional: Specify the excluded node.

l Click the Excluded Node tab. You can specify the NE that the route of the trail to be createdis not allowed to pass through by double-clicking the NE. The selected NE is marked witha sign. (Double-click the NE again to cancel the selection.)

l Click the Excluded Node tab. Right-click the blank area and choose Add from the shortcutmenu. In the Add Excluded Node window displayed, you can search for the nodes and setthem as the explicit nodes of the trails to be created.

Step 9 Optional: Click Set Route Timeslot. The Set Route Timeslot dialog box is displayed. Selectthe timeslot and click OK.



2-29

NOTE

l If you do not assign the timeslot, the first available timeslot is selected automatically.

l If multiple trails are selected, right-click them and choose Uniform Timeslot. U2000 consider thetimeslot value of the trail in the first row as the datum value and modify the timeslot values of othertrails to be consistent with the datum value. In this way, all trails use the same timeslot.

Step 10 Optional: If the trail passes through an ASON domain, you can check the SPC First check boxand click ASON Attributes Settings to set the parameters.

Step 11 Optional: Click the General Attributes tab and set the general attributes of the trail, such asthe Name and Order No..

Step 12 Optional: If you do not want to activate the created trail when the configuration is issued toNEs, you can uncheck the Activate the trail check box.

NOTE

l If you activate a trail, the service configuration data of the trail is sent to the NE.

l If you do not activate a trail, the service configuration data of the trail is stored at the NE layer on theU2000.

Step 13 Optional: Check the Alarm Reversion check box to set the alarm reversion on the trail to becreated.

Step 14 Optional: If you want to create multiple trails with the same route, check the Copy afterCreation check box. After the creation of the trail, a dialog box is displayed and you can copythe trail.

Step 15 Click Apply.

Step 16 Optional: If the creation is successful, click Browse Trail in the displayed dialog box. Then,you can view the trail on the interface.

----End

2.1.5.2 Creating an SNCP VC4 Trail

By creating an end-to-end VC4 trail, you can quickly create an E4, STM-1 SDH service withSNCP. The methods for creating an SNCP VC4 trail are the same in different protection subnets.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The license for the trail management function must be provided.

Context

When creating the VC4 trail, you do not need to create a server trail.

Procedure


Step 2 Set the service direction and the level to VC4 or VC4-Xc.

Step 3 Set the Service Domain.




Issue 02 (2010-09-24)

Step 4 Set the resource usage strategy to Protected Resource and the protection priority strategy toSNCP First.

NOTE




Step 6 Double-click the source NE and the sink NE in turn. Select the board and port in the SelectBoard Port dialog box and click OK. The trail is automatically selected, and is displayedbetween the source and sink NEs.












2-31


NOTE



Step 11 Click the SNCP setting tab.

l Right-click the dual-fed point and choose Set Dual-Fed Point, and the node is marked witha sign. Right-click the selective-receiving point and choose Set Selective-ReceivingPoint, and the node is marked with a sign.

l Right-click in the dual-fed and selective-receiving list and choose Add from the shortcutmenu. In the Add the dual-fed and selective-receiving node displayed, select Dual-FedPoint and Selective-Receiving Point. Click OK.

Step 12 Click the SNCP Attribute tab and set SNCP attribute.

Step 13 Optional: If the trail passes through an ASON domain, you can check the SPC First check boxand click ASON Attributes Settings to set the parameters.



NOTE









Issue 02 (2010-09-24)


----End


Prerequisitel You must be an NM user with "network operator" authority or higher.l The SNCP trail must be created.

Context

CAUTIONPerforming the SNCP switching may cause short interruption of the services.

Procedure

Step 1 Select Service > SDH Trail > Manage SDH Trail from the Main Menu.

Step 2 In the Set Trail Browse Filter Criteria dialog box, set the filter conditions, and then click FilterAll. The trails are displayed in the list.

NOTE

l Click Filter All to refresh and display all the qualified trails.

l Click Secondary Filter to filter the trails that are already displayed.

l Click Incremental Filter to add the newly qualified trails to the list without refreshing the trails thatare already displayed.

Step 3 Select an SNCP trail from the list. Click the Maintenance > SNC Service Control.

Step 4 In the SNC Service Controldialog box, select the source or sink of the SNC. Click Function.Then select a proper switching mode to switch the SNC service.

Step 5 Click Query. Check whether Active Channel shows that the SNC service is switched to theexpected trail. If not, the explicit NE or fiber of the trail is faulty.

Step 6 If you want to clear the switching, select the NE verified in Step 4. Click Function, and thenselect Clear.

----End

2.1.6 Automatically Creating VC12 and VC3 TrailsIf you want to create SDH services of the VC12 and VC3 levels, you can complete the serviceconfiguration quickly by creating end-to-end VC12 and VC3 trails.



2-33

2.1.6.1 Creating a VC4 Server TrailA VC4 server trail is used to carry the VC12 and VC3 trails between the NEs. Before creatinga VC12 or VC3 trail, you need to create a VC4 server trail between the NEs.

2.1.6.2 Creating a Non-SNCP VC12 or VC3 TrailBy creating an end-to-end VC12 or VC3 trail, you can quickly create an E1 or T1 or E3 or T3SDH service without SNCP. In different protection subnets, the methods for creating a non-SNCP VC12 or VC3 trail are the same.

2.1.6.3 Creating an SNCP VC12 or VC3 TrailBy creating an end-to-end VC12 or VC3 trail, you can quickly create an E1 or T1 or E3 or T3SDH service with SNCP. The methods for creating an SNCP VC12 or VC3 trail in differentprotection subnets are the same.



Prerequisitel You must be an NM user with "network operator" authority or higher.l A protection subnet must be created for release 4.0 NEs, including the OptiX 155/622H

(Metro 1000), the OptiX 155/622, the OptiX 2500+ (Metro 3000), and the OptiX Metro3100 and so on.

l The license for the trail management function must be provided.l The OptiX 10G (Metro 5000) NE must have the AMXS, EMXS or ETXC board where the

low order cross-connection protection pairs are created in U2000.l The OptiX OSN 9500 NE must have the GXCL or EXCL board where the lower order

cross-connection protection pairs are created in U2000.l The available resources must be sufficient.

Contextl A VC4 server trail is used only to carry services between the source and sink NEs, and

cannot be used by any intermediate NEs. Hence, for the convenience of bandwidth use,VC4 server trails are usually created between two adjacent NEs, instead of between twoNEs that have intermediate NEs. Before deleting a VC4 server trail, you need to delete itslower order trail.

l A VC4 server trail is used to carry the VC12 and VC3 trails between the NEs. Hence, whenyou create higher order services such as VC4 or VC4-Xc services, you need not create theVC4 server trail.

Procedure


Step 2 Set the service direction to Bidirectional and level to VC4 Server Trail.




Issue 02 (2010-09-24)

Step 3 Set the Service Domain, Resource Usage Strategy and Protection Priority Strategyparameters.

NOTE

Pay attention to the following points when setting the parameters:


l Protection Priority Strategy defines the protection subnet resources to be selected first during trailcreation. The values are Trail Protection First, SNCP First and NP First.

Step 4 Double-click the source NE and the sink NE in turn. The automatically selected route is displayedbetween the NEs.



l Click the Explicit Link tab. Right-click the blank area and choose Add from the shortcutmenu. In the Add Explicit Link window displayed, you can search for the existing servertrails and set them as the explicit links of the trails to be created.





l Double-click another NE in this subnet to specify the excluded nodes for the trail. Theselected NE is marked with a sign. (Double-click the NE again to cancel the selection.)





2-35

NOTE





NOTE






----End

2.1.6.2 Creating a Non-SNCP VC12 or VC3 TrailBy creating an end-to-end VC12 or VC3 trail, you can quickly create an E1 or T1 or E3 or T3SDH service without SNCP. In different protection subnets, the methods for creating a non-SNCP VC12 or VC3 trail are the same.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The VC4 server trail is created between the source and sink NEs, and free timeslots are

available on the VC4 server trail.

Contextl When the VC12/VC3 trail transits multiple VC4 server trails, the consistency of VC4

timeslot used by each server trail is not required, but the U2000 automatically uses theserver trails that use the same VC4 timeslot if possible.

l To create a VC12/VC3 trail in a unidirectional or bidirectional PP ring, you need to createa VC4 server trail that forms a closed loop, and the VC4 timeslot used by each server trailmust be consistent.

Procedure


Step 2 Select the service direction according to the protection subnet type. Set the service level toVC12 or VC3.




Issue 02 (2010-09-24)

Step 3 Configure the Service Domain, Resource Usage Strategy and Protection Priority Strategy.NOTE




Step 5 Double-click the source NE and the sink NE in turn. Select the board and port in the SelectBoard Port dialog box and click OK. The trail is automatically selected, and is displayedbetween the NEs.

Step 6 Optional: Specify the explicit link of the service.l Click a server trail between the NEs to specify the included route. Click the trail again or

click Cancel Route Restriction to cancel the selection.l Click the Explicit Link tab. Right-click the blank area in the tab and choose Add from the

shortcut menu. In the Add Explicit Link window displayed, you can search for the existingserver trails and set them as the explicit links of the trails to be created.

Step 7 Optional: Specify the explicit node.l Click the Explicit Node tab. Double-click an NE of the subnet to specify the explicit NE

of the route. This NE is shown as the icon. Double-click the NE again to cancel theselection.


Step 8 Optional: Specify the excluded node.l Click the Excluded Node tab. You can specify the NE that the route of the trail to be created

is not allowed to pass through by double-clicking the NE. The selected NE is marked witha sign. (Double-click the NE again to cancel the selection.)





2-37

NOTE



Step 10 Optional: If the trail passes through the ASON domain, you can check the Select ASON ServerTrail First check box. Click the ASON Attributes Settings tab and set the correspondingprotection attributes.



NOTE







----End

2.1.6.3 Creating an SNCP VC12 or VC3 TrailBy creating an end-to-end VC12 or VC3 trail, you can quickly create an E1 or T1 or E3 or T3SDH service with SNCP. The methods for creating an SNCP VC12 or VC3 trail in differentprotection subnets are the same.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The VC4 server trail is created between the source and sink NEs, and free timeslots are

available on the VC4 server trail.

ContextWhen the VC12/VC3 trail transits multiple VC4 server trails, the consistency of VC4 timeslotused by each server trail is not required, but the U2000 automatically uses the server trails thatuse the same VC4 timeslot if possible.

Procedure





Issue 02 (2010-09-24)

Step 2 Set the service direction and the level to VC12 or VC3.


Step 4 Set the resource usage strategy to Protected Resource and the protection priority strategy toSNCP First.

NOTE




Step 6 Double-click the source NE and the sink NE in turn. Select the board and port in the SelectBoard Port dialog box and click OK. The trail is automatically selected, and is displayedbetween the NEs.











2-39



NOTE



Step 11 Click the SNCP Setting tab.

l Right-click the dual-fed point and choose Set Dual-Fed Point, and the node is displayedas . Right-click the selective-receiving point and choose Set Selective-ReceivingPoint, and the node is displayed as .

l Right-click the area in the tab and choose Add from the shortcut menu. In the Add thedual-fed and selective-receiving node displayed, select Dual-Fed Point and Selective-Receiving Point. Click OK.


Step 13 Optional: If the trail passes through the ASON, you can check the Select ASON Server TrailFirst check box. Click the ASON Attributes Settings tab and set the corresponding protectionattributes.



NOTE







Issue 02 (2010-09-24)




----End



Context

CAUTIONPerforming the SNCP switching may cause short interruption of the services.

Procedure

Step 1 Select Service > SDH Trail > Manage SDH Trail from the Main Menu.

Step 2 In the Set Trail Browse Filter Criteria dialog box, set the filter conditions, and then click FilterAll. The trails are displayed in the list.

NOTE




Step 3 Select an SNCP trail from the list. Click the Maintenance > SNC Service Control.

Step 4 In the SNC Service Controldialog box, select the source or sink of the SNC. Click Function.Then select a proper switching mode to switch the SNC service.

Step 5 Click Query. Check whether Active Channel shows that the SNC service is switched to theexpected trail. If not, the explicit NE or fiber of the trail is faulty.

Step 6 If you want to clear the switching, select the NE verified in Step 4. Click Function, and thenselect Clear.

----End



2-41

2.1.7 Creating a Platinum Service GroupIn a platinum service group, the SDH trails do not pass through the same NE, fiber, or fiber/cable pipe, so that the risk that multiple trails are interrupted is lowered.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The U2000 license that is used must support platinum services.l The platinum service supports the SDH trail only, instead of the WDM trail, Ethernet trail,

and radio trail.l For the prerequisites of creating a lower order SDH trail, see 2.1.6.2 Creating a Non-SNCP

VC12 or VC3 Trail. For the prerequisites of creating a higher order SDH trail, see 2.1.5.1Creating a Non-SNCP VC4 Trail.

l The levels of the trails in a platinum service group must be consistent.l The preconfigured trail cannot be added into a platinum service group.l The platinum service cannot be manually created.

ContextThe procedures of creating a platinum trail are almost the same as the procedures of creating anon-platinum service, that is, normal service. The only difference is that you need to select areference trail for a platinum service. If a reference trail is selected, a platinum service group iscreated at the same time. Otherwise, a non-platinum service (normal service) is created.

During the creation of a platinum service, if a reference trail is selected, the U2000 automaticallyfilters out the NE, fiber, and fiber/cable pipe that the reference trail passes through to calculatea new route. If this reference trail already belongs to a certain platinum service group, theU2000 also considers other trails in the platinum service group as reference trails to calculate anew route.

If the U2000 cannot calculate a route after filtering out the NE, fiber, and fiber/cable pipe thatthe reference trail passes through, the U2000 reduces the restrictions. Then, the U2000 calculatesa relatively appropriate route that passes through the preceding NE, fiber, or fiber/cable pipe tocontinue the creation. Therefore, a downgraded platinum service group is created.

Procedure

Step 1 Create the trail in the platinum service group according to the procedures of creating a non-platinum service.

To Create See

Higher order trail 2.1.5.1 Creating a Non-SNCP VC4 Trail

Lower order trail 2.1.6.2 Creating a Non-SNCP VC12 or VC3 Trail

Step 2 In the Router Constraint area, click the Platinum Service Group tab.

Step 3 Click Add. In the Set Trail Browse Filter Criteria dialog box displayed, set the filter criteriaand then click Filter. The trails that meet the criteria are displayed in the list.

Step 4 Select a trail as the reference trail and then click OK.




Issue 02 (2010-09-24)

NOTE

If the new trail and the reference trail cannot fully comply with the requirements of the platinum service,in the Operation Result dialog box, click Close. Then, in the Calculate Platinum Service Trail dialogbox displayed, determine whether to create the downgraded platinum service group. To create thedowngraded platinum service group, click Yes. Otherwise, click No.

Step 5 Finish other settings and then click Apply. In the Operation Result dialog box displayed, clickClose.

----End

2.1.8 Bound Platinum Service GroupYou can bind a trail or trails when you need to add an existing trail to a platinum service groupor bind existing trails as a platinum service group.


l The U2000 license that is used must support platinum services.

l The levels of the trails to be bound must be the same.

Context

The platinum service group can be bound in the following two scenarios:

l Add a trail or more to an existing platinum service group.

l Bind a trail or more as a new platinum service group.

In the preceding two scenarios, the levels of the trails must be the same. That is, in the firstscenario, the level of the trail to be added must be the same as the platinum service group. In thesecond scenario, the levels of all trails must be the same.

After the binding, the U2000 automatically checks whether the trails in the platinum servicegroup meet the requirements.

Procedure

Step 1 Choose Service > SDH Trail > Manage SDH Trail from the Main Menu.

Step 2 In the Set Trail Browse Filter Criteria dialog box displayed, set the filter criteria and clickFilter All. The trails are displayed in the list.

NOTE




Step 3 Select all the trails that you want to bind, right-click, and then choose Bind Platinum ServiceGroup from the shortcut menu.




2-43

Step 5 Optional: In Platinum Service Group Status, you can check whether the status of the platinumservice group is normal.

----End

2.1.9 Creating an SDH Trail ManuallyThe U2000 has restrictions on trail route computation and does not support complicated networkvery well. If you fail to create trails using the route computation function, you can use the functionof manually creating trails to create them.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The license for the trail management function must be provided.l The optical fiber at the server layer must be created.l The VC4 server trail must be created before creating a VC12 or VC3 trail.

ContextYou can use the function of manually creating an SDH trail to create the following trails:l A multi-source multi-home traill A trail that passes a DNI protection subnetl A mono nodal trail whose source and sink terminate on the same NE

During manual creation of a bidirectional SDH trail, if you do not specify the reverse route, theU2000 automatically generates a reverse route. The generated reverse route and the positiveroute use a consistent route even if the protection subnet passed through is unidirectional.Therefore, make sure you specify the reverse route when manually creating a bidirectional trailthat passes through a unidirectional PP ring.

Procedure

Step 1 Choose Service > SDH Trail > Create SDH Trail Manually from the Main Menu.

Step 2 Select the Direction, Level and Service Domain for the service.

NOTE

If you want to create a broadcast trail, set the value of Direction to Unidirectional.

Step 3 Select the source and sink NEs for the trail that you want to create.

NOTE

In the Trail View, right-click an NE and choose Select Source or Select Sink from the shortcut menu tospecify this NE as the source or sink NE. Alternatively, click Browse to designate the source and sink NEsfor the trail.

Step 4 Optional: Select route computation policy.




Issue 02 (2010-09-24)

NOTE

l In the Calculate Route pane, select Normal reverse route or Reverse route between cross-ringnodes. The U2000 automatically creates the negative route according to the positive route manuallycreated by the user.

l In the Calculate Route pane, click Calculate Route. The U2000 automatically computes the routebetween the source and sink nodes.

Step 5 Specify the route.NOTE

l When you create bidirectional trails, you need to specify the negative route. When you create a protectedtrail, you need to specify the protection route.

l Click a route in the Trail View. The available trails on this route are displayed in the lower-right SetRoute Timeslot pane. Set the Direction, Timeslot and Route Type parameters for the trail. ClickAdd and the trail is displayed in Route Information. If you need to delete trails from RouteInformation, click Delete.

Step 6 Repeat preceding step to specify the route segment by segment.

Step 7 Click the General Attributes tab and set the general attributes of the trail, such as theCustomer, Remarks, Name and Order No..

Step 8 Optional: If you do not want to activate the created trail when the configuration is issued toNEs, you can uncheck the Activated check box.

NOTE

l If you activate a trail, the service configuration data of the trail is sent to the NE.l If you do not activate a trail, the service configuration data of the trail is stored at the NE layer on the

U2000.


NOTE

You cannot set this parameter when creating a VC4 server trail or link server trail.


----End

2.1.10 Creating PDH Radio TrailsWhen you create a PDH radio trail in the end-to-end mode, services configured on each NE aredisplayed in the U2000 in the end-to-end mode. This provides a visual display of the route ofeach service, so that you can view and manage routes and used resources in an easy way.

2.1.10.1 Creating a Link Server TrailA link server trail is used to carry the PDH radio trails between NEs. You need to create a linkserver trail between NEs before you configure the PDH radio trails between the NEs.

2.1.10.2 Creating a PDH Radio TrailWhen you want to create a PDH radio service, you can quickly configure the service by creatingan end-to-end PDH radio trail.

2.1.10.1 Creating a Link Server TrailA link server trail is used to carry the PDH radio trails between NEs. You need to create a linkserver trail between NEs before you configure the PDH radio trails between the NEs.



2-45


l You must have a license that supports radio end-to-end management to create a link servertrail.

l Make sure that there are sufficient available resources.

Contextl A link server trail is used to carry only the services between the source and sink NEs, and

cannot be used by any intermediate NEs between the source and sink NEs. Hence, in actualapplications, for easier bandwidth utilization, you can create a link server trail betweenevery two adjacent NEs in the network, instead of a link server trail that crosses multipleNEs. Currently, a link server trail between every two adjacent NEs is supported, and a linkserver trail that crosses multiple NEs is not supported.

l Before you delete a link server trail, you need to delete the lower level trails over the trail.

l A link server trail is used to carry the PDH radio trails between NEs. Hence, you need tocreate a link server trail before you create a higher order service.

Procedure


Step 2 Set the service direction to Bidirectional and set the service level to Link Server Trail.

Step 3 Set Resource Usage Strategy and Protection Priority Strategy.

NOTE

When setting parameters, note the following points:

l The resource usage strategy means which protection subnet resources or timeslots that you can useduring the process for creating a trail. The values are Protected Resource, Extra Resource, and AllResource.

l The protection priority strategy means which types of protection subnets to which you give priorityduring the process for creating a trail. The values are Trail Protection First, SNCP First, and NPFirst.

Step 4 Double-click the source NE and then the sink NE. The system automatically selects a trail anddisplays it between the source NE and the sink NE.


l Click a server trail between NEs to specify the explicit link for the service. To cancel yourselection, click the route again or click Cancel Route Restriction.

l Click the Explicit Link tab. Right-click in the blank area and choose Add from the shortcutmenu. In the Add Explicit Link window, you can search for the existing server trail andset it as the explicit link for the trail to be created.


l Click the Explicit Node tab. Double-click the NE in the subnet to specify the explicit NEthat the route passes through. The NE is displayed as (double-click it again to cancel theselection).




Issue 02 (2010-09-24)

l Click the Explicit Node tab. Right-click in the blank area and choose Add from the shortcutmenu. In the Add Explicit Node window, you can search for the node and set it as theexplicit node of the trail to be created.

Step 7 Optional: Specify the excluded node.l Click the Excluded Node tab. Double-click the other NE in the subnet to specify the

excluded NE that the route should not pass through. The NE is displayed as (double-click it again to cancel the selection).

l Click the Excluded Node tab. Right-click the blank area and choose Add from the shortcutmenu. In the Adding Excluded Node window, you can search for the node and set it asthe excluded node of the trail to be created.

Step 8 Optional: Click the General Attributes tab and set the general attributes of the trail, such asName and Order No.

Step 9 Optional: If you do not want to apply the settings of the created trail to NEs, clear the Activatethe trail check box.

NOTE

l In the case of an active trail, the service configuration data is applied to NEs.

l In the case of an inactive trail, the service configuration data is saved in the U2000.

Step 10 Optional: If you want to create multiple trails that have the same route, select the Copy afterCreation check box. After you create the trail, a dialog box is displayed and you can duplicatethe trail.


----End

2.1.10.2 Creating a PDH Radio TrailWhen you want to create a PDH radio service, you can quickly configure the service by creatingan end-to-end PDH radio trail.

Prerequisitel You must be an NM user with "network operator" authority or higher.l A link server trail must be created between the source and sink NEs of the service, and the

link server trail has idle timeslots.

Procedure


Step 2 Set the Direction and Level of the service.

Step 3 Set Resource Usage Strategy to Protected Resource, and set Protection Priority Strategy toSNCP First.



2-47

NOTEWhen setting parameters, note the following points:

l The resource usage strategy means which protection subnet resources or timeslots that you can useduring the process for creating a trail. The values are Protected Resource, Extra Resource, and AllResource.

l The protection priority strategy means which types of protection subnets to which you give priorityduring the process for creating a trail. The values are Trail Protection First, SNCP First, and NPFirst.

Step 4 Double-click the source NE and the sink NE in sequence. In the Select Board Port dialog box,select a port and then click OK. The system automatically selects a trail and displays it betweenthe source NE and the sink NE.


l Click a server trail between NEs to specify the explicit link for the service. To cancel yourselection, click the route again or click Cancel Route Restriction.

l Click the Explicit Link tab. Right-click in the blank area and choose Add from the shortcutmenu. In the Adding Explicit Link window, you can search for the existing server trailand set it as the explicit link of the trail to be created.


l Click the Explicit Node tab. Double-click the NE in the subnet to specify the explicit NEthat the route passes through. The NE is displayed as (double-click it again to cancel theselection).

l Click the Explicit Node tab. Right-click in the blank area and choose Add from the shortcutmenu. In the Adding Explicit Node window, you can search for a node and set it as theexplicit node of the trail to be created.


l Click the Excluded Node tab. Double-click an NE in the subnet to specify the excludedNE that the route should not pass through. The NE is displayed as (double-click it againto cancel the selection).

l Click the Excluded Node tab. Right-click in the blank area and choose Add from theshortcut menu. In the Adding Excluded Node window, you can search for a node and setit as the explicit node of the trail to be created.

Step 8 Click the SNCP Setting tab.

l Right-click the NE that dual-feeds services and choose Set Dual-Fed Point from theshortcut menu. A flag of the NE is displayed. Right-click the NE that selects a serviceand choose Set Selective-Receiving Point from the shortcut menu. A flag of the NE isdisplayed.

l Right-click the blank area in the tab and choose Add from the shortcut menu. In the Addthe dual-fed and selective-receiving node window, select Dual-Fed Point and Selective-Receiving Point. Click OK.

Step 9 Click the General Attributes tab. Set the general attributes of the trail, such as Name and OrderNo..

Step 10 Optional: If you do not want to activate the created trail when you apply the configuration toNEs, clear the Activate the trail check box.




Issue 02 (2010-09-24)

NOTE

l In the case of an active trail, the service configuration data is applied to NEs.

l In the case of an inactive trail, the service configuration data is saved in the U2000.


Step 12 Optional: If you want to create multiple trails that have the same route, select the Copy afterCreation check box. After you create the trail, a dialog box is displayed and you can duplicatethe trail.


----End

2.1.11 Creating SDH Radio TrailsWhen you create an SDH radio trail in the end-to-end mode, services configured on each NEare displayed in the U2000 in the end-to-end mode. Such display facilitates the check andmanagement over the routes of each service and resources used for each service.

2.1.11.1 Creating a VC4 Server TrailA VC4 server trail is intended to bear inter-NE SDH radio trails. Create a VC4 server trail beforeyou creating lower order SDH radio trails between NEs.

2.1.11.2 Creating an SDH Radio TrailThe end-to-end creation of an SDH radio link helps to quickly provide an SDH radio service.

2.1.11.1 Creating a VC4 Server Trail

A VC4 server trail is intended to bear inter-NE SDH radio trails. Create a VC4 server trail beforeyou creating lower order SDH radio trails between NEs.

Prerequisitel You must be an NM user with "network operator" authority or higher.l A license enabling the trail function must be available for creating a VC4 server trail.l Sufficient resources must be available.

Contextl A VC4 server trail is intended to bear only the services on the source NE and sink NE,

instead of the services on any intermediate NE. Practically, for convenience in usingbandwidth, a VC4 server trail is always created between two adjacent NEs instead ofmultiple NEs. Delete the lower level service trails before you delete the underlying VC4server trail.

l A VC4 server trial is intended to bear lower order SDH radio trails between NEs. Hence,no VC4 server trail is necessary in the course of creating higher order services.

Procedure




2-49

Step 2 Set the service direction to Bidirectional and set the service level to VC4 Server Trail.

Step 3 Set Service Domain, Resource Usage Strategy and Protection Priority Strategy.

NOTE

Note the following when setting these parameters:

l The resource usage policy defines the resources or timeslots of which protection subnets are availablefor creating the trail. This parameter can be set to Protected Resource, Extra Resource, or AllResource.

l The protection priority policy defines which types of protection subnets are selected with priority duringthe course of trail creating. This parameter can be set to Trail Protection First, SNCP First, or NPFirst.

Step 4 Double-click the source NE and sink NE in sequence. Then, the system automatically selects atrail and displays it between the source NE and sink NE.

Step 5 Optional: Specify explicit links for the service.l To specify an explicit link for the service, you need to click a server trail between NEs. To

cancel the setting, you need to re-click the server trail or click Cancel RouteRestriction.

l Click the Explicit Link tab, right-click the blank, and choose Add from the shortcut menu.In the Add Explicit Link window displayed, you can search for the existing server trailsand set them as explicit links for the trail to be created.

Step 6 Optional: Specify explicit nodes.l Click the Explicit Node tab. Double-click an NE in the subnet to specify it as an explicit

node that the route traverses. Then, the NE is displayed as . To cancel the setting, double-click the NE.

l Click the Explicit Node tab, right-click the blank, and choose Add from the shortcut menu.In the Add Explicit Node window displayed, you can search for the nodes and set them asexplicit nodes for the trail to be created.

Step 7 Optional: Specify excluded nodes.l Double-click another NE in the protection subnet to specify it as an excluded NE. Then,

the NE is displayed as . To cancel the setting, double-click the NE.l Click the Excluded Node tab, right-click the blank, and choose Add from the shortcut

menu. In the Add Excluded Node window displayed, you can search for the nodes and setthem as excluded nodes for the trail to be created.

Step 8 Optional: Click the General Attributes tab and set the general attributes of the trail, such asName and Order No..

Step 9 Optional: If it is unnecessary to activate the created trail, deselect the Activate the trail checkbox.

NOTE

l If you activate the trail, the service configuration data is delivered to NEs.

l If you leave the trail unactivated, the service configuration data is stored only on the U2000.

Step 10 Optional: To create multiple route-shared trails, select the Copy after Creation check box.When creation of the trail is complete, a dialog box is displayed indicating trail copying.


----End




Issue 02 (2010-09-24)

2.1.11.2 Creating an SDH Radio Trail

The end-to-end creation of an SDH radio link helps to quickly provide an SDH radio service.


l In the case of a lower order SDH microwave trail, a VC4 server trail must be createdbetween the source and sink NEs of the service. In addition, idle timeslots must be availableon the VC4 server trail.

Procedure


Step 2 Specify the direction and level of the service.


Step 4 Set the resource usage policy to Protected Resource and protection priority policy to SNCPFirst.

NOTENote the following when setting these parameters:

l The resource usage policy defines the resources or timeslots of which protection subnets are availablefor creating the trail. This parameter can be set to Protected Resource, Extra Resource, or AllResource.

l The protection priority policy defines which types of protection subnets are selected with priority duringthe course of trail creating. This parameter can be set to Trail Protection First, SNCP First, or NPFirst.

Step 5 Double-click the source NE and sink NE in sequence. In the Select Board Port dialog box,select a port and click OK. Then, the system automatically selects a trail and displays it betweenthe source NE and the sink NE.

Step 6 Optional: Specify explicit links for the service.

l To specify an explicit link for the service, you need to click a server trail between NEs. Tocancel the setting, you need to re-click the server trail or click Cancel RouteRestriction.

l Click the Explicit Link tab, right-click the blank, and choose Add from the shortcut menu.In the Add Explicit Link window displayed, you can search for the existing server trailsand set them as explicit links for the trail to be created.

Step 7 Optional: Specify explicit nodes.

l Click the Explicit Node tab. Double-click an NE in the subnet to specify it as an explicitnode that the route traverses. Then, the NE is displayed as . To cancel the setting, double-click the NE.

l Click the Explicit Node tab, right-click the blank, and choose Add from the shortcut menu.In the Add Explicit Node window displayed, you can search for the nodes and set them asexplicit nodes for the trail to be created.

Step 8 Optional: Specify excluded nodes.



2-51

l Click the Excluded Node tab. Double-click an NE in the subnet to specify it as an excludednode from all routes. Then, the NE is displayed as . To cancel the setting, double-clickthe NE.

l Click the Excluded Node tab, right-click the blank, and choose Add from the shortcutmenu. In the Add Excluded Node window displayed, you can search for the nodes and setthem as excluded nodes for the trail to be created.

Step 9 Then, click the SNCP setting tab.l Right-click the NE where the service is dually fed, choose Set Dual-Fed Point from the

shortcut menu. The NE is displayed as . Right-click the NE where the service isselectively received, choose Set Selective-Receiving Point from the shortcut menu. TheNE is displayed as .

l Right-click the blank in the tab and choose Add from the shortcut menu. In the Add thedual-fed and selective-receiving node dialog box displayed, specify Dual-Fed Point andSelective-Receiving Point. Click OK.

Step 10 Click the General Attributes tab and set the general attributes of the trail, such as Name andOrder No..

Step 11 Optional: If it is unnecessary to activate the created trail, deselect the Activate the trail checkbox.

NOTE

l If you activate the trail, the service configuration data is delivered to NEs.l If you leave the trail unactivated, the service configuration data is stored only on the U2000.

Step 12 Optional: Select the Alarm Reversion check box to set the alarm reversion on the created trail.

Step 13 Optional: To create multiple route-shared trails, select the Copy after Creation check box.When creation of the trail is complete, a dialog box is displayed indicating trail copying.


----End

2.1.12 Copying SDH TrailsTo expand a network, you can quickly create SDH trails by duplicating a created SDH trail.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The SDH trail must be created.

ContextIn tangent ring and dual node interconnection (DNI) scenarios, SDH trails across the DNIprotection can be copied.

Procedure


Step 2 In the Set Trail Browse Filter Criteria dialog box, set the filter criteria and click Filter All.The trails are displayed in the list.




Issue 02 (2010-09-24)

NOTE



l Click Incremental Filter to add newly qualified trails to the list without refreshing the trails that arealready displayed.

Step 3 Right-click a trail and choose Copy.

Step 4 In the Copy dialog box displayed, select the source and sink boards for the duplicate trail.

Step 5 In the Available Timeslots/Port area, select the source and sink timeslots for the duplicate trail.Click Add. In the Selected Timeslots/Port area, the selected timeslots and ports are displayed.

Step 6 Optional: If you need to set the start timeslot of the trail, in the Copy setting pane, check Specifythe start timeslot check box and select the corresponding start timeslot.

Step 7 Optional: Select the start value of the trail name suffix.

Step 8 Click OK. In the Operation Result dialog box displayed, click Close.

----End



2-53

2.1.13 Modifying an SDH TrailYou can use the U2000 to modify a created SDH trail.

2.1.13.1 Modifying the Port/Timeslot/Route of an SDH TrailBy using the U2000, you can modify the source or sink port, used timeslot, and route that aspecified SDH trail passes through. When settings are applied to the NE, the systemautomatically deletes the original trail.

2.1.13.2 Modifying the SNC Service Control of SDH TrailsYou can modify the control attributes that were previously set when you create an SNCP service.

2.1.13.3 Modifying Trail Names in BatchesThe network administrator can set the trail naming rules and modify trail names in batchesaccording to these rules.

2.1.13.4 Modifying the Trails in a Platinum Service GroupYou can modify the trails that do not fully comply with the requirements of the platinum servicein the downgraded platinum service group. Therefore, the fully-compliant platinum servicegroup is created.

2.1.13.1 Modifying the Port/Timeslot/Route of an SDH Trail

By using the U2000, you can modify the source or sink port, used timeslot, and route that aspecified SDH trail passes through. When settings are applied to the NE, the systemautomatically deletes the original trail.


l The trail cannot be locked.

l The source and sink of the VC4 server trail and the information of the route that is near thesource and sink cannot be modified.

Contextl Change the route: Change the route of the trail based on unchanged source and sink NEs.

For example, the NE that the trail passes through.

l Change the port or timeslot of a board on the source or sink NE: Change the port or timeslotof a board on the source or sink NE, based on unchanged route. For example, the linetimeslot or tributary port that is used by the trail.

l The U2000 supports modifying the board, port and timeslot on the source and the sink NEs,and the route that the trail passes through at the same time.

CAUTIONThis operation may interrupt services. Exercise caution when you perform this operation.




Issue 02 (2010-09-24)

Procedure



NOTE




Step 3 Select a trail. Click Create/Modify and choose Modify Trail.

Step 4 To modify the boards, ports or timeslots on the source and sink NEs, click Browse. In the windowdisplayed, select new boards, ports or timeslots.

Step 5 To modify the route that a trail passes through, in the Route constraint area, delete the originalexplicit links, explicit nodes and excluded nodes, and specify new explicit links, explicit nodesand excluded nodes.

Step 6 To modify the timeslot on the route that a trail passes through, click Set Route Timeslot. In theSet Route Timeslot window displayed, select new Server Layer Trail Name, Server LayerTrail and Timeslot as required.

NOTE

If multiple trails are selected, right-click them and choose Uniform Timeslot. U2000 consider the timeslotvalue of the trail in the first row as the datum value and modify the timeslot values of other trails to beconsistent with the datum value. In this way, all trails use the same timeslot.

Step 7 Click OK. In the Confirm dialog box, click Yes. A prompt is displayed, indicating that theoperation is successful. Click Close.

----End

2.1.13.2 Modifying the SNC Service Control of SDH Trails

You can modify the control attributes that were previously set when you create an SNCP service.


l The trail cannot be locked.

l The SNCP service must be existed.

Context

CAUTIONThis operation may interrupt services. Exercise caution when you perform this operation.



2-55

Procedure



NOTE




Step 3 Select an SNCP trail from the list, click Maintenance and choose SNC Service Control.

Step 4 In the SNC Service Control dialog box, double-click and modify Revertive Mode, WTRTime and Hold-Off Time of the service.

NOTE

When Revertive Mode of the service is set to Revertive, you can modify WTR Time.


----End

2.1.13.3 Modifying Trail Names in Batches

The network administrator can set the trail naming rules and modify trail names in batchesaccording to these rules.


l The trail naming rules must be set on the U2000.

Procedure



NOTE




Step 3 Right-click one or more trails from the list, and choose Name from the shortcut menu. For thenaming rules, refer to Customizing Naming Rule.

Step 4 In the Confirm dialog box displayed, click OK.

----End




Issue 02 (2010-09-24)

2.1.13.4 Modifying the Trails in a Platinum Service Group

You can modify the trails that do not fully comply with the requirements of the platinum servicein the downgraded platinum service group. Therefore, the fully-compliant platinum servicegroup is created.

PrerequisiteFor details, see 2.1.13.1 Modifying the Port/Timeslot/Route of an SDH Trail.

Context

The procedures of modifying a trail in a platinum service group are almost the same as theprocedures of modifying a non-platinum service, that is normal service. The differences aredescribed as follows:l When a trail in the platinum service group is modified, the U2000 automatically considers

other trails in the platinum service group as reference trails. Therefore, when calculatingthe route, the U2000 automatically filters out the available resources of the fibers in thefiber/cable pipe that the reference trails pass through.

l When the trail in the platinum service group is modified, the U2000 checks whether thetrails in the platinum service group meet the requirements of the platinum service.

Procedure

Step 1 Modify the trail in the platinum service group according to the procedures of modifying the non-platinum service. For details, see 2.1.13.1 Modifying the Port/Timeslot/Route of an SDHTrail.

----End

2.1.14 Removing a Trail from a Platinum Service GroupWhen the platinum service protection is no longer required but the trail of the platinum serviceprotection needs to be retained, you can remove the trail from the platinum service group.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The U2000 license that is used must support platinum services.l The platinum service group must be created.

ContextIf a trail is deleted or removed from the platinum service group, the U2000 automatically checkswhether the trails in the platinum service group meet the requirements of the platinum service.

Procedure





2-57

NOTE




Step 3 Right-click the trail that you want to remove from the platinum service group and then chooseMove Out of Platinum Service Group from the shortcut menu.


----End

2.1.15 Configuring Overhead Bytes of an SDH TrailIf you want to maintain or monitor the SDH trails, you can set the trail overhead bytes.

2.1.15.1 Setting the Trace ByteThe trace byte is used by the receive end to confirm the continuous connection status with thetransmit end. The trace byte of the equipment that belongs to the same vendor can be set to anysame characters. Between equipment of different vendors, the trace byte must be set to the samecharacters that are previously agreed, so that the interconnection can be successful.

2.1.15.2 Setting the C2 ByteThe C2 byte indicates the multiframe structure of VC frames and the type of bearer services (forexample, PDH services or ATM services).

2.1.15.3 Setting the V5 ByteThe V5 byte is an overhead byte at the lower order channel. During the interaction of VC12services or interaction with a non-SDH service, you can set the V5 byte on a trail according tothe interacted service.

2.1.15.4 Setting the Overhead TerminationOverhead termination means that the SDH equipment processes and terminates the receivedoverhead signals, and sends the recreated (or default) overhead signals to another optical boardat the opposite end.

2.1.15.5 Setting Service Load SignalsIf a VC12 or VC3 trail is not loaded with services, you can set the loading status of the trail tounloaded. U2000 does not monitor the alarms that are generated on the trail whose loading statusis set to unloaded.

2.1.15.1 Setting the Trace Byte

The trace byte is used by the receive end to confirm the continuous connection status with thetransmit end. The trace byte of the equipment that belongs to the same vendor can be set to anysame characters. Between equipment of different vendors, the trace byte must be set to the samecharacters that are previously agreed, so that the interconnection can be successful.


l Trails must be created and activated.




Issue 02 (2010-09-24)

Context

There are two modes for handling overhead bytes, which are the standard mode and the extendedmode. In the extended mode, you can set bytes to be transmitted for pass-through services. Inthe standard mode, bytes to be transmitted cannot be set for pass-through services.

CAUTIONCorrectly configure the trace byte. This operation may affect services.

Procedure



NOTE




Step 3 Select a trail, click Maintenance and select Trace Byte.

Step 4 In the Set Overhead dialog box, double-click Byte to be sent or Byte to be received.

Step 5 In the Please input the overhead byte dialog box displayed, enter the contents of the overheadbytes and click OK.

Step 6 In the Prompt dialog box displayed, click Yes.

Step 7 In Set Overhead dialog box, click Apply.



2-59

NOTE

You can click Switch Mode to select an overhead processing mode.

Step 8 Click Yes to confirm the operation. In the Operation Result dialog box displayed, clickClose.

----End

2.1.15.2 Setting the C2 Byte

The C2 byte indicates the multiframe structure of VC frames and the type of bearer services (forexample, PDH services or ATM services).


l Trails must be created and activated.

Context

There are two modes for handling overhead bytes, which are the standard mode and the extendedmode. In the extended mode, you can set bytes to be transmitted for pass-through services. Inthe standard mode, bytes to be transmitted cannot be set for pass-through services.

CAUTIONCorrectly configure the C2 byte. This operation may affect services.

Procedure



NOTE




Step 3 Select the trail that you want to set the C2 byte, click Maintenance and select C2 Byte from thedrop-down list.

Step 4 In the Set Overhead dialog box, double-click and set Byte to be Sent or Byte to beReceived. Click Apply.




Issue 02 (2010-09-24)

NOTE



----End

2.1.15.3 Setting the V5 ByteThe V5 byte is an overhead byte at the lower order channel. During the interaction of VC12services or interaction with a non-SDH service, you can set the V5 byte on a trail according tothe interacted service.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l Applies for VC12 trails only.

ContextThere are two modes for handling overhead bytes, which are the standard mode and the extendedmode. In the extended mode, you can set bytes to be transmitted for pass-through services. Inthe standard mode, bytes to be transmitted cannot be set for pass-through services.

CAUTIONCorrectly configure the V5 byte. This operation may affect services.

ProcedureStep 1 Choose Service > SDH Trail > Manage SDH Trail from the Main Menu.




2-61

NOTE




Step 3 Select a VC12 trail that you want to set the V5 byte, click Maintenance and select V5 Bytefrom the drop-down list.

Step 4 In the Set Overhead dialog box, double-click and set Byte to be Sent or Byte to beReceived. Click Apply.

NOTE



----End

2.1.15.4 Setting the Overhead TerminationOverhead termination means that the SDH equipment processes and terminates the receivedoverhead signals, and sends the recreated (or default) overhead signals to another optical boardat the opposite end.

Prerequisitel You must be an NM user with "network operator" authority or higher.l Trails must be created and activated.

Context

CAUTIONCorrectly set overhead termination. This operation may affect services.




Issue 02 (2010-09-24)

Procedure



NOTE




Step 3 Select a trail and click Maintenance and select Overhead Termination.

Step 4 In the Set Overhead dialog box displayed, double-click and set Overhead Status. ClickApply.

NOTE



----End

2.1.15.5 Setting Service Load Signals

If a VC12 or VC3 trail is not loaded with services, you can set the loading status of the trail tounloaded. U2000 does not monitor the alarms that are generated on the trail whose loading statusis set to unloaded.


l In the case of a unidirectional trail, the source must be the tributary board. In the case of abidirectional trail, one end should be the tributary board at least. The trail whose sourceand sink are line boards does not support setting the service load.



2-63

Context

CAUTIONDo not set the loading status of an SDH trail that already has services to unloaded. Otherwise,services are interrupted.

Procedure



NOTE




Step 3 Select a VC12/VC3 trail. Click Maintenance and choose Service Load Signal from the drop-down menu.

Step 4 In the Service Load Signal dialog box displayed, double-click and set Loading Status.


----End

2.1.16 Changing Between SNCP and Non-SNCP TrailsIn the case of a protection subnet change, you can change non-SNCP trails to SNCP trails andvice versa by following this process. This change may interrupt the service.

2.1.16.1 Changing a Non-SNCP Trail to an SNCP TrailIn the case of a protection subnet change, you can change the non-SNCP trail to the SNCP trail.

2.1.16.2 Changing an SNCP Trail to a Non-SNCP TrailIn the case of a protection subnet change, you can change an SNCP trail to a non-SNCP trail.

2.1.16.1 Changing a Non-SNCP Trail to an SNCP Trail

In the case of a protection subnet change, you can change the non-SNCP trail to the SNCP trail.


l The normal trail must be created and the two ends of the trail cannot terminate at Ethernetboards.




Issue 02 (2010-09-24)

Context

CAUTIONThis operation may cause short interruption of the services.



NOTE

l Click Filter All to refresh and display all the qualified trails.l Click Secondary Filter to filter the trails that are already displayed.l Click Incremental Filter to add the newly qualified trails to the list without refreshing the trails that

are already displayed.

Step 3 Select a trail and click Create/Modify and choose Modify Trail.

Step 4 Click the SNCP Setting tab.l Right-click the dual-fed point and choose Set Dual-Fed Point from the shortcut menu, and

the node is displayed as . Right-click the selective-receiving point and choose SetSelective-Receiving Point from the shortcut menu, and the node is displayed as .

l Right-click the blank area in the tab and choose Add from the shortcut menu. The Add thedual-fed and selective-receiving node is displayed, select Dual-Fed Point and Selective-Receiving Point. Click OK.


Step 6 Click OK. In the Confirm dialog box, click Yes. In the Operation Result dialog box, clickClose.

----End



2-65

2.1.16.2 Changing an SNCP Trail to a Non-SNCP TrailIn the case of a protection subnet change, you can change an SNCP trail to a non-SNCP trail.

Prerequisitel You must be an NM user with "network maintainer" authority or higher.l The SNCP trail must be created.

Context

CAUTIONThis operation may cause short interruption of the services.

Procedure


Step 2 In the Set Trail Browse Filter Conditions dialog box displayed, set the filter criteria and clickFilter All. The trails are displayed in the list.

NOTE




Step 3 Select an SNCP trail and click Create/Modify and select Modify Trail from the drop-downlist.

Step 4 Click the SNCP Setting tab. Right-click a record of dual-fed and selective-receiving points, andchoose Delete from the shortcut menu.

Step 5 Click OK. In the Confirm dialog box, click Yes. In the Operation Result dialog box, clickClose.

----End

2.1.17 Enabling or Disabling VC4 Server TrailsA VC4 server trail is used to carry lower order client trails between NEs. When the timeslotusage of a VC4 server trail reaches the limit, or you want to transfer a service to another servertrail, you can disable or enable the VC4 server trail to set whether it continues to carry lowerorder trails. This function helps telecom operators to maintain network resources.




Issue 02 (2010-09-24)

2.1.17.1 Disabling VC4 Server TrailsYou can disable a VC4 server trail, so that the trail no longer carries new lower order clientservices. When the timeslot usage of a VC4 server trail reaches the limit, or you want to transfera service to another server trail, you can disable the VC4 server trail. In this way, when youcreate a new client service, the service automatically avoids the disabled VC4 server trail.

2.1.17.2 Enabling VC4 Server TrailsA VC4 server trail is used to carry lower order client trails between NEs. When you need adisabled VC4 server trail to serve as a server trail for client trails, you can enable the VC4 servertrail.

2.1.17.1 Disabling VC4 Server TrailsYou can disable a VC4 server trail, so that the trail no longer carries new lower order clientservices. When the timeslot usage of a VC4 server trail reaches the limit, or you want to transfera service to another server trail, you can disable the VC4 server trail. In this way, when youcreate a new client service, the service automatically avoids the disabled VC4 server trail.

Prerequisitel You must be an NM user with "network operator" authority or higher.l Applies to VC4 server trails only.l The VC4 server trail must not be disabled.

ContextYou can disable an ASON VC4 server trail, but when an ASON trail reroutes, it can be reroutedto a VC4 server trail that is enabled or disabled.

Procedure



NOTE




Step 3 Right-click one or more VC4 server trails that you want to disable, and choose Disable from theshortcut menu.

Step 4 In the Operation Result dialog box displayed, click Close.

----End

2.1.17.2 Enabling VC4 Server TrailsA VC4 server trail is used to carry lower order client trails between NEs. When you need adisabled VC4 server trail to serve as a server trail for client trails, you can enable the VC4 servertrail.



2-67

Prerequisitel You must be an NM user with "network operator" authority or higher.l Applies to VC4 server trails only.l The VC4 server trail must be disabled.



NOTE

l Click Filter All to refresh and display all the qualified trails.l Click Secondary Filter to filter the trails that are already displayed.l Click Incremental Filter to add the newly qualified trails to the list without refreshing the trails that

are already displayed.

Step 3 Right-click one or more VC4 server trails that you want to enable, and choose Enable from theshortcut menu.


----End

2.1.18 Joining and Splitting VC4 Server TrailsA VC4 server trail is used only to carry the services between the source and sink NEs, and cannotbe used by any intermediate NEs between the source and sink NEs. If you want to change thesource and sink NEs of a configured VC4 server trail, you can use the joining and splittingfunctions.

ContextFigure 2-10 shows the joining and splitting of VC4 server trails.

Figure 2-10 Joining and splitting VC4 server trails

NE1 NE3

NE1 NE2 NE3

NE2

Trail 3

Join Split

Trail 2

Trail 1

There is only one VC4 server trail between NE1 and NE3. If you want to configure a VC12 orVC3 trail between NE1 and NE2 or between NE2 and NE3, you can split Trail 1 into two VC4server trails, that is, Trail 2 and Trail 3. On the contrary, you can join Trail 2 and Trail 3 as Trail1.




Issue 02 (2010-09-24)

2.1.18.1 Joining VC4 Server TrailsAn NE has two VC4 server trails for which the NE functions as the source for one trail and thesink for the other trail. The two trails carry lower order services that pass through the NE. Youcan combine the two trails into a VC4 server trail. The joining process deletes the lower orderVC4 services that pass through the NE and creates higher order pass-through services at thesame time. After the two VC4 server trails are joined, the VC4 server trail that passes throughthe NE does not use lower order cross-connections. Hence, the lower order cross-connectresources on the NE that the trail passes through are saved.

2.1.18.2 Splitting a VC4 Server TrailSplitting is the inverse process of joining. During the process of splitting, the VC4 server trailthat passes through an NE is split in to two VC4 server trails. The NE functions as the sourcefor one VC4 server trail and functions as the sink for the other VC4 server trail. The splittingprocess deletes the higher order VC4 services that pass through the NE and creates a lower orderpass-through service at the same time. The two trails that are split carry lower order servicesthat add or drop from the NE.

2.1.18.1 Joining VC4 Server TrailsAn NE has two VC4 server trails for which the NE functions as the source for one trail and thesink for the other trail. The two trails carry lower order services that pass through the NE. Youcan combine the two trails into a VC4 server trail. The joining process deletes the lower orderVC4 services that pass through the NE and creates higher order pass-through services at thesame time. After the two VC4 server trails are joined, the VC4 server trail that passes throughthe NE does not use lower order cross-connections. Hence, the lower order cross-connectresources on the NE that the trail passes through are saved.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The trails to be joined must not carry lower order services that are added/dropped at the

joining NE.l All lower order services carried by one trail must be able to pass through to the other trail.

Context

CAUTIONDuring the joining, services are interrupted.

The lower order services carried by the trails to be joined cannot be added/dropped at the joiningNE. Otherwise, the trails cannot be joined. See Figure 2-11. VC4 server trails 1 and 2 cannotbe joined due to the existence of VC12 trail 1.

Figure 2-11 Restrictions on VC4 server trail joining

NE1 NE2 NE3

VC4 ServerTrail 1

VC12 Trail 1

VC4 ServerTrail 2



2-69

The two trails can be joined only when all the lower order services carried by one trail are ableto pass through to the other trail. The timeslots for the two trails can be different. See Figure2-12. If any of VC12 trails 1 and 2 exists, VC4 server trails 1 and 2 cannot be joined.

Figure 2-12 Restrictions on VC4 server trail joining

NE3NE1 NE2 NE4

NE5 NE6

VC4 ServerTrail 1

VC4 ServerTrail 5

VC4 ServerTrail 2

VC4 ServerTrail 3

VC4 ServerTrail 4

VC12Trail 1

VC12Trail 2

Procedure

Step 1 In the Physical Map, right-click an NE and choose Trails > Join VC4 Server Layer Trailsfrom the shortcut menu.

NOTE

You need to select the Trail check box on the upper right corner of the Main Topology in advance.

Step 2 In the Join VC4 Server Trails dialog box displayed, select the trail numbers and click Join. Ifmultiple trails are available, multiple combinations are displayed. You can select thecombination as required.

Step 3 Enter the name of the joined trail and click OK.

Step 4 In the two Confirm dialog boxes displayed, click OK. In the Operation Result dialog boxdisplayed, click Close.

----End

2.1.18.2 Splitting a VC4 Server Trail

Splitting is the inverse process of joining. During the process of splitting, the VC4 server trailthat passes through an NE is split in to two VC4 server trails. The NE functions as the sourcefor one VC4 server trail and functions as the sink for the other VC4 server trail. The splittingprocess deletes the higher order VC4 services that pass through the NE and creates a lower orderpass-through service at the same time. The two trails that are split carry lower order servicesthat add or drop from the NE.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The NE that has been split must have sufficient lower order cross-connect resources.




Issue 02 (2010-09-24)

Context

CAUTIONDuring the splitting, services are interrupted.

Procedure

Step 1 In the Physical Map, right-click an NE and choose Trails > Split a VC4 Server Layer Trailfrom the shortcut menu.

NOTE

You need to select the Trail check box on the upper right corner of the Main Topology in advance.

Step 2 In the Split a VC4 Server Trail dialog box displayed, select the trail to be split and clickSplit.

Step 3 In the Split a VC4 Server Trail dialog box displayed, enter the names of the split trails andclick OK.

Step 4 In the two Confirm dialog boxes displayed, click OK. In the Operation Result dialog boxdisplayed, click Close.

----End

2.1.19 Service Authorization ManagementIf there are multiple service trails maintained by different operators, they may care about onlythe trails in their own responsibility but ignore the other services. Service authorization can filterthe information not in concern of an operator, who then views and manages only the trails in theresponsibility. In this manner, the management and maintenance efficiency is improved.

Figure 2-13 shows four service trails. Trails 1-2 are maintained by operator A and trails 3-4 aremaintained by operator B. By means of service authorization, operator A can maintain only trails1-2 and cannot maintain trails 3-4 on the U2000. Similarly, operator B cannot maintain trails1-2.



2-71

Figure 2-13 Service authorization management

Trail 1NE1

NE3

NE4NE2

Trail 4Trail 3

Trail 2

You can authorize a service to an U2000 user in two modes:

l Directly authorize the service to an U2000 user.

l Specify a customer for the service and authorize the customer to an U2000 user.

Service authorization management must meet the following conditions:

l A license for service authorization management must be available.

l The U2000 user has the operation rights related to service authorization.

2.1.19.1 Specifying a Customer for a ServiceYou can logically group services for management by specifying customers for them.

2.1.19.2 Authorizing a Customer to a U2000 UserWhen you authorizing a customer to a U2000 user, you also authorize all the services specifiedfor the customer to the U2000 user.

2.1.19.3 Authorizing a Trail to a U2000 UserBy authorizing a trail to a U2000 user, the U2000 user manages only the trail but ignores othertrails.

2.1.19.4 Modifying Trail Authorization InformationYou can view, modify, and delete trail authorization information, if necessary.

2.1.19.1 Specifying a Customer for a Service

You can logically group services for management by specifying customers for them.


l The U2000 user that performs such an operation must have the Right- and domain-basedauthorization (transport domain) right.




Issue 02 (2010-09-24)

l The service and the customer to be specified for the service must exist.

Contextl You can not specify customers for VC4 server trails.l You can also specify a customer for a trail when creating the trail.

Procedure



NOTE




Step 3 Right-click the trail and choose Details from the shortcut menu.

Step 4 In the displayed dialog box, click Customer and select a customer for the service from the drop-down list.

NOTE

The U2000 provides a fuzzy query function, with which you can quickly search for a specific customerout of many customers.

Step 5 Click OK.

----End

2.1.19.2 Authorizing a Customer to a U2000 User

When you authorizing a customer to a U2000 user, you also authorize all the services specifiedfor the customer to the U2000 user.

Prerequisitel You must be an NM user with "network administrator" authority or higher.l The U2000 user that performs such an operation must have the Right- and domain-based

authorization (transport domain) right.l The U2000 user and the customer to be authorized to the U2000 user must exist.

Procedure

Step 1 Choose Service > Customer Management from the Main Menu.

Step 2 Right-click the customer and choose Authorize to User from the shortcut menu.

Step 3 In the displayed dialog box, select the U2000 user from Available Users in the pane on the left,

and then click .



2-73

Step 4 Click OK.

----End

2.1.19.3 Authorizing a Trail to a U2000 User

By authorizing a trail to a U2000 user, the U2000 user manages only the trail but ignores othertrails.



l The U2000 user to which the trail is to be authorized must exist and must have the rightsof network maintainer, network operator, or network monitor.

l The trail to be authorized must exist.

Procedure



NOTE




Step 3 Right-click the trail and choose Confer Rights to User from the shortcut menu.

Step 4 In the displayed dialog box, select the U2000 user from Available Users in the pane on the left,

and then click .

Step 5 Click OK.

----End

2.1.19.4 Modifying Trail Authorization Information

You can view, modify, and delete trail authorization information, if necessary.



l A trail or customer must be authorized to a U2000 user.




Issue 02 (2010-09-24)

Procedure

Step 1 Choose Service > SDH Trail > Manage SDH Service Authority from the Main Menu.

Step 2 Select the user from the User List pane in the displayed window.

Step 3 In the pane on the right, view, modify, or delete the trails authorized to the user.

Step 4 Click OK.

----End

2.1.20 Viewing SDH TrailsBy viewing SDH trails, you can learn about the distribution and usage of the SDH trails in thenetwork.

2.1.20.1 Viewing SDH Trail DetailsBy viewing SDH trails, the network administrator is able to know the trail details, such as theworking status, and source and sink ports.

2.1.20.2 Viewing the Use Information of a VC4 Server TrailBy viewing the use information of VC4 server trails, you can learn the trail resources occupiedby lower order services in the network.

2.1.20.3 Viewing Relevant Client TrailsAt a level higher than sever trails, client trails are used to carry services. By using the U2000,you can view the client trail information of a specified trail.

2.1.20.4 Viewing the Optical Power for the TrailsYou can query the optical power for trails. The U2000 provides a way to manage the opticalpower that is related to the NE layout, topology structure and routing.

2.1.20.5 Viewing the Status of the Fiber Break on an SDH TrailWhen an alarm is generated on an SDH trail due to the fiber break, the color of the fiber in theview is changed, for convenience of the primary fault location.

2.1.20.6 Viewing Fiber Information of a TrailDuring service planning or fault locating, you need to query or collect statistics on theinformation about fibers where a certain trail passes. The U2000 supports the ability to querythe information about the fibers occupied by a trail.

2.1.20.1 Viewing SDH Trail Details

By viewing SDH trails, the network administrator is able to know the trail details, such as theworking status, and source and sink ports.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The SDH or PDH trail must be created.

Procedure




2-75


NOTE




Step 3 Optional: If you need to view the alarm or performance information of a trail, click Alarm orPerformance to view the alarm or performance information of the trail.

Step 4 Optional: If you need to view the client trail information of a trail, choose Browse RelevantClient Trails from the shortcut menu.

Step 5 Optional: To view the details of the route of a certain trail, select the trail and then chooseReport > Single Specifics.

----End

2.1.20.2 Viewing the Use Information of a VC4 Server TrailBy viewing the use information of VC4 server trails, you can learn the trail resources occupiedby lower order services in the network.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The VC4 server trail must be created.

Procedure

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


NOTE




Step 3 Optional: Select one or more VC4 server trails, right-click, and then choose Browse RelevantClient Trails from the shortcut menu. Then, you can view the client trails that the VC4 servertrails carry.

Step 4 Select one or more VC4 server trails, click Report and choose Server Layer Trail UseInformation.

Step 5 In the Server Layer Trail Use Information window, query the resource use information of thetrails.

Step 6 In the Server Layer Trail Use Information window, select a VC4 server trail. In the timeslotdiagram that is displayed in the lower portion of the window, view the timeslots that are occupiedby lower order services.




Issue 02 (2010-09-24)

NOTEA timeslot diagram can be displayed in the sequential mode or the interleaved mode. The display mode isconsistent with the timeslot mode used when the trail is created.

----End

2.1.20.3 Viewing Relevant Client TrailsAt a level higher than sever trails, client trails are used to carry services. By using the U2000,you can view the client trail information of a specified trail.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The SDH trail must be created or searched out.

ContextIn the network model specified in the ITU-T G.805, the transport network is classified into thecircuit layer, path layer, and transmission media layer.That is, each layer manages its ownoverheads and each layer can be classified into sub-layers and the relationship between theadjacent layers is client and server.

A connection of the client layer is carried by an adjacent server trail for transmission. Forexample, the link connection in a circuit layer network is provided by the path of a path layernetwork, while the link connection in a path layer network is provided by the section of thetransmission media layer. The path layer is the server layer of the circuit layer, and the sectionlayer is the server layer of the path layer.

VC12/VC3 services are fixedly carried at the VC4 server layer. Therefore, VC12/VC3 trails areclient trails of the VC4 server trails.

Procedure



NOTE




Step 3 Right-click a trail and choose Browse Relevant Client Trails from the shortcut menu. Thecorresponding client trails are displayed in the trail list.

----End

2.1.20.4 Viewing the Optical Power for the TrailsYou can query the optical power for trails. The U2000 provides a way to manage the opticalpower that is related to the NE layout, topology structure and routing.



2-77


l The SDH trails must be correctly created.

Procedure



NOTE




Step 3 Right-click a trail and choose Query Relevant Optical Power from the shortcut menu.

Step 4 In the Optical Power Management window displayed, click the Table tab. Click Query toquery the optical power information of ports from the NE. In the Operation Result dialog boxdisplayed, click Close.

NOTE

In the View tab, move the cursor on a link. The U2000 shows the optical power information of all fibersin the link.

Step 5 Click the Graphic tab to query the graphic interface of the port optical power.

NOTE

l Green indicates that the current optical power is in the normal range.

l Orange indicates that the current power exceeds the reference deviation and there is an exception.

l Black "E" shape in the histogram indicates the allowable deviation range of the optical power.

----End

2.1.20.5 Viewing the Status of the Fiber Break on an SDH Trail

When an alarm is generated on an SDH trail due to the fiber break, the color of the fiber in theview is changed, for convenience of the primary fault location.


Procedure






Issue 02 (2010-09-24)

NOTE




Step 3 In the trail list, select a trail. In the Transmission Media Layer Route view, the route wherethe fiber break occurs of the trail is displayed.

Step 4 Optional: To refresh the view, right-click the blank area of the Transmission Media LayerRoute view and choose Refresh Route from the shortcut menu. When the fiber break status ischanged, the view is changed after the manual refresh.

----End

2.1.20.6 Viewing Fiber Information of a TrailDuring service planning or fault locating, you need to query or collect statistics on theinformation about fibers where a certain trail passes. The U2000 supports the ability to querythe information about the fibers occupied by a trail.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The trail must be created.

Procedure



NOTE




Step 3 Select a trail, right-click, and then choose Browse Relevant Fibers from the shortcut menu.

Step 4 In the Fiber/Cable Management window, view the information about the fibers where the trailpasses.

----End

2.1.21 Maintaining SDH TrailsYou can check and maintain SDH trails to find potential faults in the earliest time.

2.1.21.1 Locking or Unlocking an SDH TrailThe U2000 can lock out some important trails. After lockout, you cannot delete, activate, orrename the locked SDH trails. Locking or unlocking an SDH trail does not affect services thatare running.



2-79

2.1.21.2 Activating or Deactivating an SDH TrailActivation is to deliver the data that is saved on the U2000 to NEs and the execution is performed.Deactivation is to delete the data from NEs, while the data on the U2000 remains. To change anSDH trail from the active to the inactive state, you need to deactivate the trail. Oppositely, tochange an SDH trail from the inactive state to the active state, you need to activate the trail.

2.1.21.3 Setting a Loopback for a TrailUse this procedure to set a loopback for an SDH trail. The SDH trail loopback is a common faultlocation method used to test and maintain the SDH equipment. The SDH trail loopback is usedto test whether the nodes between the source and loopback nodes (including the source andloopback nodes themselves) work properly, and is also used to test whether the nodes betweenthe sink and loopback nodes (including the sink and loopback nodes themselves) work properly.

2.1.21.4 Performing the Protection Switching for a Single SNCP TrailOn the U2000, you can perform or release the external switching operation for an SNCP trail.During the deployment commissioning, the external switching operation can be performed totest whether the SNCP switching is normal or whether the protection switching is equipped.During the fault maintenance, this operation can be performed to locate faults.

2.1.21.5 Performing the SNCP Trail Switching in BatchesOn the U2000, you can perform or release the external switching operation for SNCP trails inbatches. During the deployment commissioning, the external switching operation can beperformed to test whether the SNCP switching is normal or whether the protection switching isequipped. During the fault maintenance, this operation can be performed to locate faults.

2.1.21.6 Verifying Platinum Service Groups in BatchesWhen the NE or fiber/cable pipe that a service passes through is changed, the service may failto meet the requirements of the platinum service group. Therefore, you can manually verify theservices in the group to learn about the status of the platinum group.

2.1.21.7 Converting SDH Discrete Services to Mono Nodal TrailsSDH discrete cross-connections can be converted to mono nodal trails.

2.1.21.1 Locking or Unlocking an SDH TrailThe U2000 can lock out some important trails. After lockout, you cannot delete, activate, orrename the locked SDH trails. Locking or unlocking an SDH trail does not affect services thatare running.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The SDH trail must be created.

ContextNOTE

l After you lock out a trail, when you configure the trail on a per-NE basis, you cannot activate, deactivate,delete, or modify the cross-connection used by the trail. In the Trail Management window, right-clicka trail but some commands are grayed out in the shortcut menu. The commands are Delete, Delete fromNetwork Layer, Activate, Deactivate, and Name.

l After you lock out a VC4 server trail, you can still create a client trail on the server trail.




Issue 02 (2010-09-24)

Procedure



NOTE




Step 3 Right-click a trail and choose Lock or Unlock from the shortcut menu.


----End

2.1.21.2 Activating or Deactivating an SDH Trail

Activation is to deliver the data that is saved on the U2000 to NEs and the execution is performed.Deactivation is to delete the data from NEs, while the data on the U2000 remains. To change anSDH trail from the active to the inactive state, you need to deactivate the trail. Oppositely, tochange an SDH trail from the inactive state to the active state, you need to activate the trail.


Contextl If an inactive SDH trail is activated again, the attributes of services that the trail carries are

consistent with the attributes of services that the trail carried before activation.

l If the lower order service that the VC4 server trail carries is active, you need deactivate thelower order service before you deactivate the VC4 server trail.

CAUTIONDeactivating an SDH trail interrupts services.

Procedure





2-81

NOTE




Step 3 Right-click an SDH trail that you want to activate or deactivate and choose Activate orDeactivate from the shortcut menu. In the Confirm and Reconfirm dialog boxes, click OK.


----End

2.1.21.3 Setting a Loopback for a Trail

Use this procedure to set a loopback for an SDH trail. The SDH trail loopback is a common faultlocation method used to test and maintain the SDH equipment. The SDH trail loopback is usedto test whether the nodes between the source and loopback nodes (including the source andloopback nodes themselves) work properly, and is also used to test whether the nodes betweenthe sink and loopback nodes (including the sink and loopback nodes themselves) work properly.


l Trails must be created.

ContextThe SDH trail loopback includes "Loopback to Source" and "Loopback to Sink".

l When "Loopback to Source" is used, the signal coming from the trail source is returned tothe source over the trail. See Figure 2-14. "Loopback to Source" is used to test whetherthe nodes between the source and loopback nodes (including the source and loopback nodesthemselves) work properly.

Figure 2-14 Loopback to Source

l When "Loopback to Sink" is used, the signal coming from the trail sink is returned to thesink over the trail. See Figure 2-15. "Loopback to Sink" is used to test whether the nodesbetween the sink node and the loopback node (including the sink node and the loopbacknode themselves) work properly.




Issue 02 (2010-09-24)

Figure 2-15 Loopback to Sink

CAUTIONAs a loopback interrupts services, it is only used for fault location and must be released after thefault is removed.

Procedure



NOTE




Step 3 Select a trail and click Maintenance and select Loopback.

Step 4 In the Loopback dialog box displayed, click the tab according to the loopback location.

NOTE

You can choose to set the loopback status at the tributary board, VC4 path and optical or electrical port.

Step 5 Select a PDH interface, an SDH interface or a VC path. Double-click the Loopback Status toselect the loopback mode.



2-83

Step 6 Optional: Double-click LoopRelease Time, and enter or select the releasing time of theloopback.

NOTE

When the time is up, the loopback is released automatically. This can prevent that you forget to release theloopback and the communication is affected for a long time.

Step 7 Click Apply. In the Confirm dialog box displayed, click Yes. In the Operation Result dialogbox displayed, click Close.

----End

2.1.21.4 Performing the Protection Switching for a Single SNCP TrailOn the U2000, you can perform or release the external switching operation for an SNCP trail.During the deployment commissioning, the external switching operation can be performed totest whether the SNCP switching is normal or whether the protection switching is equipped.During the fault maintenance, this operation can be performed to locate faults.


ContextThe external switching for SNCP trail includes: lockout, forced switching and manual switching.




Issue 02 (2010-09-24)

l In the event of lockout of switching, the switching request for the port is denied, but thereversion of switching is allowed.

l The forced switching has a higher priority than signal failure and signal degrade on theprotection section. This switching is performed regardless of the protection channel state,unless the protection channel is satisfying a higher priority bridging request.

l The manual switching has a lower priority than signal failure and signal degrade on theprotection section. The manual switching request is valid only when there are no signalfailure or signal degrade on the protection section.


Procedure



NOTE




Step 3 Select a trail and click Maintenance and choose SNC Service Control.

Step 4 In the SNC Service Control dialog box displayed, select a trail, click Function and choose anoption from the drop-down list.


----End

2.1.21.5 Performing the SNCP Trail Switching in Batches

On the U2000, you can perform or release the external switching operation for SNCP trails inbatches. During the deployment commissioning, the external switching operation can beperformed to test whether the SNCP switching is normal or whether the protection switching isequipped. During the fault maintenance, this operation can be performed to locate faults.


ContextThe external switching for SNCP trail includes: lockout, forced switching and manual switching.



2-85

l In the event of lockout of switching, the switching request for the port is denied, but thereversion of switching is allowed.

l Forced switching has a higher priority than signal failure and signal degrade, on theprotection section. This switching is performed regardless of the protection channel state,unless the protection channel is satisfying a higher priority bridging request.

l Manual switching has a lower priority than signal failure and signal degrade, on theprotection section. The manual switching request is valid only when there are no signalfailure or signal degrade on the protection section.


Procedure



NOTE




Step 3 Select a VC4 server trail that carries an SNCP service. Click Maintenance and choose SNCService Batch Control.

Step 4 In the SNC Trails dialog box displayed, select the trails to be switched. Click Function andchoose an option from the drop-down list. The Confirm dialog box is displayed.

Step 5 In the Confirm dialog box, click OK. In the Operation Result dialog box displayed, clickClose.

----End




Issue 02 (2010-09-24)

2.1.21.6 Verifying Platinum Service Groups in Batches

When the NE or fiber/cable pipe that a service passes through is changed, the service may failto meet the requirements of the platinum service group. Therefore, you can manually verify theservices in the group to learn about the status of the platinum group.


l The U2000 license that is used must support platinum services.

l The platinum service group must be created.

ContextFor the requirements that the trails in a platinum service group must meet, see 2.1.2.9 PlatinumService Group.

Procedure



NOTE




Step 3 Right-click the trail to be verified and then choose Check Platinum Service Group from theshortcut menu.

Step 4 In the Operation Result dialog box that is displayed, click Close.

NOTE

If the verification result shows that the platinum service group is downgraded, you can view the causes inthe Operation Result dialog box that is displayed again.

----End

2.1.21.7 Converting SDH Discrete Services to Mono Nodal Trails

SDH discrete cross-connections can be converted to mono nodal trails.


l A cross-connection with a fiber or radio connection at the source or sink cannot be convertedto a mono nodal trail.



2-87

Contextl If you select only the positive cross-connection for conversion, the U2000 automatically

searches for the reverse cross-connection and converts the cross-connection to abidirectional mono nodal trail.

l If you select only the working cross-connection for conversion, the U2000 automaticallysearches for the protection cross-connection and then verifies and converts it.

Procedure



Step 3 In the Set Discrete Service Browse Filter Criteria dialog box displayed, set the filter criteriaand then click Filter.

Step 4 Right-click one or more discrete service and choose Convert to Mono Nodal Trail.

Step 5 Optional: If the conversion is successful, you can click Browse Trail in the displayed dialogbox to view the trail on the interface.

----End

2.1.22 Deleting SDH TrailsThe deletion of needless SDH trails releases relevant network resources.




Issue 02 (2010-09-24)

Prerequisitel You must be an NM user with "network operator" authority or higher.l Make sure that the SDH trail to be deleted is inactive.l Make sure that the SDH trail to be deleted does not carry any other SDH trailor trunk

link.

ContextNOTE

The procedure for deleting server trails and client trails are similar. The difference is that before deletinga server trail, its client trails must be deleted first. If the SDH trail to be deleted is already used by a trunklink trail, you need to delete the trunk link first.

Procedure



NOTE




Step 3 Right-click one or more SDH trails you want to delete and choose Delete from the shortcutmenu.



2-89

NOTE

The two schemes for trail deletion are as follows:

l Delete: This scheme deletes trail from the U2000 and relevant services from the NE. Be careful whenusing this scheme because it may affect the services.

l Delete from Network Layer: This scheme deletes trails from the U2000 only. This command is notissued to the NE and thus does not affect services. After the deletion, you can perform a trail search tofind the trails again according to the service information in the NE.

If the trail you want to delete is activated, deactivate it before you delete it. If you attempt to delete the trailfrom the network layer, you need not to deactivate the trail in advance.

Step 4 In the Confirm and Reconfirm dialog boxes, click OK.


----End

2.2 Managing Ethernet TrailsIn the end-to-end configuration mode, you can quickly create Ethernet services, such as EPL,EVPL or EPLAN. During the end-to-end configuration, you only need to specify the source andsink for the service, and the U2000 automatically calculates the route and creates the service foreach NE on the route. The end-to-end configuration mode is also called the trail managementfunction.

PrerequisiteThe trail management license must be provided for the U2000.

2.2.1 Basic ConceptsYou can learn certain basic concepts that can help you to use the end-to-end Ethernetmanagement function.

2.2.2 Creating Ethernet Trails by Trail SearchAfter a new network is set up or services are configured on a per-NE basis, you need to performan Ethernet trail search so that you can manage configured services with the trail managementfunction.

2.2.3 Configuring EPL ServiceYou can use the trail function to configure EPL services.

2.2.4 Configuring an Unterminated EPL ServiceThis section describes how to configure the unterminated EPL service by using the trailmanagement function.

2.2.5 Configuring EVPL ServicesYou can use the trail function to configure EVPL services.

2.2.6 Configuring EPLAN ServiceYou can use the trail function to configure EPLAN services.

2.2.7 Configuring EVPL (QinQ) ServiceYou can use the trail function to configure EVPL (QinQ) services.

2.2.8 Specifying a Customer for a Created TrailYou can specify a customer for a created trail according to actual demands for the purpose ofnetwork maintenance.




Issue 02 (2010-09-24)

2.2.9 Checking the Connectivity of Ethernet LinkYou can perform Ethernet operation, administration and maintenance (OAM).

2.2.10 Viewing Ethernet ServicesThe network maintainer or administrator must know about the occupied resources and servicestatuses in time.

2.2.11 Maintaining Ethernet TrailsThis section describes how to maintain Ethernet trails.

2.2.12 Deleting Ethernet ServicesYou can delete the services that you do not need.

2.2.1 Basic ConceptsYou can learn certain basic concepts that can help you to use the end-to-end Ethernetmanagement function.

2.2.1.1 Ethernet End-to-End ManagementYou can use a U2000 function at the network level to fast create and manage Ethernet trails andservices in the end-to-end mode. Compared with configuration on a per-NE basis, the end-to-end mode ensures faster and more convenient operation.

2.2.1.2 Ethernet ServicesThe U2000 supports the following types of Ethernet services:

2.2.1.3 Relation Between SDH/Radio Trails and Ethernet TrailsYou must create trunk links before creating Ethernet trails. In addition, you must create SDHtrails before creating trunk links.

2.2.1.4 Tag AttributesThe tag attribute of an Ethernet port indicates how the port processes Ethernet packets.

2.2.1.1 Ethernet End-to-End Management

You can use a U2000 function at the network level to fast create and manage Ethernet trails andservices in the end-to-end mode. Compared with configuration on a per-NE basis, the end-to-end mode ensures faster and more convenient operation.

Definition

The U2000 network-layer management functions enable the U2000 to implement the Ethernetservice end-to-end management. By using the Ethernet end-to-end management function, anauthorized U2000 user can perform the following operations:

l Configure Ethernet end-to-end services.

l View details of an Ethernet trail.

l Quickly filter, search for and locate Ethernet trails.

l Manage and maintain Ethernet trails in a centralized manner.

l Manage alarms and performances based on Ethernet trails.

l Print Ethernet trail reports.



2-91

Purpose and Gain

In the Ethernet end-to-end management, a graphic wizard is provided for the operations anddisplays. This makes the operation much more direct. You can create the Ethernet trail in themanual, semi-automatic, or automatic mode.

l Using the manual mode, a user needs to manually create a server trail, and then create anEthernet trail on it.

l Using the semi-automatic mode, a user can specify an existing server trail to create anEthernet trail.

l Using the automatic mode, a user only needs to specify the source node, sink node andports for a trail. The U2000 automatically calculates and creates the trail and its server trail.

The Ethernet end-to-end management is one of the U2000 network-layer features. Consideringthe status of the difficulty in turning up Ethernet services, the way of end-to-end configurationgreatly simplifies the process of configuring Ethernet services, and reduces the chances ofmisoperations that are likely to take place during the per-NE based configuration.

l Without the end-to-end management function, configuring an Ethernet trail requirescompletely manual operations. You need to configure cross-connections and bindings oneach NE, set attributes of many Ethernet ports and configure the cross-connections fortransport paths.

l With the help of the Ethernet end-to-end management, to configure an Ethernet trail, youonly need to specify the source and sink nodes. The system automatically creates the servertrail and the trail you want, and at the same time, correctly sets the port attributes. In thisway, the efficiency of turning up an Ethernet service is greatly improved.

Availabilityl Involved NE: The U2000 Ethernet end-to-end management function is applicable to all

SDH and RTN NEs that support Ethernet services.

l License support: Ethernet end-to-end management is an optional feature of the U2000. Itis controlled by license. Hence, the Ethernet end-to-end management function is availableonly after a license that supports this feature is obtained.

l Supporting version: The U2000 V100R001 and later versions support the Ethernet end-to-end management feature.

Impactl Impact on system performance: If the requirements for the U2000 system are met and if

the U2000 runs normally, adding the Ethernet end-to-end management does not imposeimpacts on the system.

l Impact on other features: The Ethernet end-to-end feature depends on the single-NEEthernet feature. The Ethernet end-to-end function can be normally used only when theU2000 single-NE Ethernet feature is normal.

Principle1. The following describes the basic hierarchy of the Ethernet feature.

Current Ethernet end-to-end is based on the Ethernet Over SDH (EOS) technology, that is,the Ethernet service is carried on SDH paths. As shown in Figure 2-16, the Ethernet end-to-end, which is above the SDH end-to-end, is the at the client layer.




Issue 02 (2010-09-24)

Figure 2-16 Basic hierarchy of the Ethernet feature

2. The following describes how an Ethernet service is configured.

According to the source and sink of the Ethernet trail, the U2000 calculates the cross-connections to be delivered to each NE. When the U2000 creates an Ethernet trail on theU2000, it delivers the service to each NEs that the service passes. In this way, the Ethernetservice is turned up.

ImplementationEthernet end-to-end management is an optional function, available only after a license thatsupports this function is provided.

2.2.1.2 Ethernet ServicesThe U2000 supports the following types of Ethernet services:

EPL ServicesThe Ethernet private line (EPL) is of two types, which are as follows:l Portl Port + VLAN

EPL services of Port type can be transparently transmitted. See Figure 2-17.

Figure 2-17 EPL services of the Port type

PORT2

PORT1

B

A

PORT2

PORT1

A'TrunkLink2

NE2NE1

VCTRUNK1

B'

TrunkLink1VCTRUNK1

VCTRUNK2 VCTRUNK2



2-93

EPL services of Port + VLAN type can be converged to save port resources through severalservices that share a PORT port, or save VCTRUNK resources by sharing a VCTRUNK port.See Figure 2-18 and Figure 2-19.

l Share a PORT port

Figure 2-18 EPL services sharing a PORT port

PORT1

PORT2

PORT1

VLAN22

VLAN11A'

TrunkLink2

NE2NE1

VCTRUNK1

A"

A

TrunkLink1VCTRUNK1

VCTRUNK2 VCTRUNK2VLAN22

VLAN11

l Share a VCTRUNK port

Figure 2-19 EPL services sharing a VCTRUNK port

VLAN22

VLAN11

PORT2

PORT1

PORT2

PORT1

VLAN22

VLAN11

B

A A'TrunkLink1

NE2NE1

VCTRUNK1 VCTRUNK1

B'

For the RTN equipment, only the EPL services of the Port type are supported at present.

2.2.1.3 Relation Between SDH/Radio Trails and Ethernet TrailsYou must create trunk links before creating Ethernet trails. In addition, you must create SDHtrails before creating trunk links.

The Figure 2-20 shows the relation between SDH trails, trunk link trails and Ethernet trails.




Issue 02 (2010-09-24)

Figure 2-20 Relation Between SDH Trails and Ethernet Trails

The lower level bearer trail is called the server trail, and the upper level trail is called the clienttrail. A trunk link is the server trail of an Ethernet trail, and the Ethernet trail is the client trailof the trunk link. An SDH trail is the server trail of a trunk link, and oppositely the trunk link isthe client trail of the SDH trail.

You can query associated trails using the U2000. For example, when you are viewing a trunklink, you can view its associated server trail or client trail.

2.2.1.4 Tag AttributesThe tag attribute of an Ethernet port indicates how the port processes Ethernet packets.

Ethernet packets are classified into tagged and untagged packets in 802.1q. A four-byte field isadded to the Ethernet frame header of a tagged packet. The 802.1q-compliant field is used toidentify the VLAN ID. An untagged packet does not have such field.

An Ethernet port has the following three types, which are Tag aware, Access and Hybrid.

See Table 2-5 for details on how an Ethernet board processes tagged and untagged packets atthe ingress.

Table 2-5 Processing policy at ingress

Port Type Tagged Packet Untagged Packet

Tag aware Transparently transmitted Discarded

Access Discarded Added with the defaultVLAN tag

Hybrid Transparently transmitted Added with the defaultVLAN tag

See Table 2-6 for details on how an Ethernet board processes tagged and untagged packets atthe egress.



2-95

Table 2-6 Processing policy at egress

Port Type Tagged Packet Untagged Packet

Tag aware Transparently transmitted -

Access The VLAN tag is removed -

Hybrid The VLAN tag is removed ifit is the same as the defaulttag for the portTransparently transmitted ifthe VLAN tag is differentfrom the default tag for theport

-

As shown in Table 2-5 and Table 2-6, in an actual network, you need to set the port type forthe Ethernet board of an NE according to the Tag attribute of the messages sent from the user-side equipment. If the user-side equipment sends the Untag message, set the external port toAccess and set the internal port to Tag aware. If the user-side equipment sends the Tag message,set the external port to Tag aware and set the internal port to Tag aware.

For example, if the source equipment of a service does not support Tag messages but the sinkequipment supports Tag messages, you need to set the external port of the Ethernet board thatresides on the NE connected to the source to Access, and set the external port of the Ethernetboard that resides on the NE connected to the sink to Tag aware. Set the internal ports of theEthernet boards that resides on the NEs connected to the source and the sink to Tag aware.

2.2.2 Creating Ethernet Trails by Trail SearchAfter a new network is set up or services are configured on a per-NE basis, you need to performan Ethernet trail search so that you can manage configured services with the trail managementfunction.

2.2.2.1 Searching for Ethernet TrailsAfter a new network is set up or services are configured station by station, you need to performan Ethernet trail search so that you can manage configured services with the trail managementfunction.

2.2.2.2 Viewing Ethernet Discrete ServicesIf some cross-connections on an NE cannot form trails at the network layer and are isolated onthe NE, these cross-connections are called discrete services.

2.2.2.1 Searching for Ethernet Trails

After a new network is set up or services are configured station by station, you need to performan Ethernet trail search so that you can manage configured services with the trail managementfunction.





Issue 02 (2010-09-24)

l The license for the Ethernet trail management function must be provided.l The NE data must be uploaded to the U2000.l Fiber connections between the NEs must be created correctly.

Contextl The search only updates the trail information at the network layer on the U2000. The service

operation or the configuration data of the NE is not affected by the search.l By using this function, you can search out the unterminated Ethernet trails. The

unterminated Ethernet trail refer to the Ethernet trail whose source or sink is in the currentU2000 management domain, while the sink or source is in the management domain ofanother NMS.

l By using this function, you can search out one-source and one-sink trunk links and one-source and two-sink trunk links. The one-source and two-sink trunk links carryunterminated EPL trails that are configured with the SDH SNCP protection. If the servertrail of an unterminated EPL trail is a trunk link with a single source and double sinks, atrunk link can be searched out.

Procedure

Step 1 Choose Service > MSTP Trail > Search for Ethernet Trail from the Main Menu.

Step 2 Select the Ethernet trail search mode.l Delete the existing trails before searching: Select this to delete the current Ethernet trails

without deleting virtual paths and static routes. You can then search for Ethernet trails again.l Search for RPR: Select this to search the RPR based on the existing ones. The searched

RPR may conflict with the existing ones.l Search for Trunk Link: Select this to search the trunk link based on the existing ones.

The searched trunk link may conflict with the existing ones.l Search for Ethernet Trail: Select this to search the Ethernet Trail based on the existing

ones. The searched Ethernet Trail may conflict with the existing ones.l Search for unterminated trails: Select this to perform a search based on the existing

Ethernet trails again. The unterminated Ethernet trails and unterminated trunk links maybe searched out.

l Search By Subnet: Searches for trails that are formed by cross-connections of the selectedsubnets.

Step 3 Click Next to start the trail search. The time taken to return the search result depends on thenumber of services. You may have to wait for some time before the search is complete.

Step 4 Click Next to view the search result.l If there are new trails, the Confirm window will displayed. Click OK to synchronize the

trail information, or click Cancel and the trail information is not synchronized.

NOTE

If you click OK, trails are synchronized and, after synchronization, the trail management window isdisplayed. If you click Cancel, the trail management window is displayed directly.

l If any conflicting trunk link , RPR or Ethernet trail is found when the search is complete,click Next. These conflicting trails are displayed. By default, the conflicting trunk links,RPR or Ethernet trails are set to be deleted. You can set whether to delete the conflictingtrunk links according to actual situation. Click Next. The U2000 deletes the trails that are



2-97

set to be deleted at the network layer, and displays the trunk links, RPR and Ethernet trailsthat are searched out. By default, the management flag of all trunk links, RPR and Ethernettrails that the U2000 searches out are configured, which indicates that they are subject tothe management of the network layer. You can delete the trunk link, RPR or Ethernet trailwhose management flag is not configured according to actual requirements.

l If conflicting trunk link, RPR or Ethernet trail is not found, when you click Next, theU2000 displays the trunk links, RPR and Ethernet trails that the U2000 searches out. Bydefault, the management flag of all trunk links, RPR and Ethernet trails that the U2000searches out are configured, which indicates that they are subject to the management of thenetwork layer. You can delete the trunk link, RPR or Ethernet trail whose management flagis not configured according to actual requirements.

NOTE

The management flag indicates that the trail is included in the network trail management. By default, thetrail is under management. If you exclude the trail from the network trail management, you can also managecross-connections of single NEs during the service configuration on a per-NE basis.

Step 5 Click Next and the trails searched out without management flags are deleted from the networklayer by the U2000. This operation does not affect the NE services or the NM data of singleNEs. You can then view all discrete services in the network, including private line service, LANservice, binding relation and discrete RPR.


----End

2.2.2.2 Viewing Ethernet Discrete ServicesIf some cross-connections on an NE cannot form trails at the network layer and are isolated onthe NE, these cross-connections are called discrete services.


Procedure

Step 1 Choose Service > MSTP Trail > Manage Ethernet Discrete Service from the Main Menu.

Step 2 In the Set Discrete Service Browse Filter Criteria dialog box, set the filtering criteria.

NOTE

l In the Filter area, click Add, NE and Board will display All, then double-click NE and Board to selectthe specific NEs and boards.

l In the Service Status area, check Activate or Inactive check box.

Step 3 Click Filter to view the details of the discrete services.

----End

2.2.3 Configuring EPL ServiceYou can use the trail function to configure EPL services.





Issue 02 (2010-09-24)

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

2.2.3.2 Creating a Trunk LinkBefore creating EPL, Unterminated EPL, EVPL and EPLAN trails, create a trunk link as thebearer trail.

2.2.3.3 Creating an EPL TrailIn this user interface, you can create an EPL trail.

2.2.3.4 Verifying Ethernet ServicesAfter you configure Ethernet services, you need to verify whether service channels are available.

2.2.3.5 Sample Application: Configuring EPL ServicesThis topic uses an example to describe how to plan the service parameters and complete theentire process of configuring the point-to-point EPL service by trail method.










Procedure






2-99

NOTE






click Cancel Route Restriction to cancel the selection.l Click the Explicit Link tab. Right-click the blank area and choose Add from the shortcut

menu. In the Add Explicit Link window displayed, you can search for the existing servertrails and set them as the explicit links of the trails to be created.




Step 7 Optional: Specify the excluded node.l Double-click another NE in this subnet to specify the excluded nodes for the trail. The

selected NE is marked with a sign. (Double-click the NE again to cancel the selection.)l Click the Excluded Node tab. Right-click the blank area and choose Add from the shortcut

menu. In the Add Excluded Node window displayed, you can search for the nodes and setthem as the explicit nodes of the trails to be created.





Issue 02 (2010-09-24)

NOTE





NOTE






----End


Prerequisitel You must be an NM user with "network operator" authority or higher.l The Ethernet processing board and the corresponding interface board must be installed.

Procedure

Step 1 Choose Service > MSTP Trail > Create Trunk Link from the Main Menu.

Step 2 Set the Bandwidth parameter.

Step 3 Optional: Check the Auto Create Server Trail check box.



2-101

NOTE

l If you do not create an SDH trail, check the Auto Create Server Trail check box so that U2000 cancreate an SDH trail when creating the trunk link. If an SDH trail is already created, you can uncheckthe Auto Create Server Trail check box.

l To create a one-source and two-sink trunk link, you must create an SDH trail manually instead ofselecting the Auto Create Server Trail check box. For details of the operations, see 2.1.9 Creatingan SDH Trail Manually.

l If the trunk link to be created is a server trail of an unterminated EPL trail, the following requirementsmust be met.

l The sink of the trunk link must be terminated on the EOD board.

l The sink of the server trail of this trunk link must be terminated on the same EOD board.

l If the trunk link has a single source and double sinks, the source and sink boards of the SDH trailthat is created manually must be the same as those of the trunk link. Additionally, the sink boardsmust be same EOD board.

Step 4 Set the Source and Sink. Click Browse to select the appropriate VCTRUNK ports.

NOTE


l To create a one-source and two-sink trunk link, you need to set two VCTRUNK ports for Sink. Thetwo VCTRUNK ports that are displayed in the user interface are separated by .

l If the Auto Create Server Trail check box is checked in Step 3, select Bound Timeslot in additionto the VCTRUNK port. Otherwise you need to select the VCTRUNK port only.

l You need to keep the bandwidth of the source or sink VCTRUNK consistent with the bandwidth settingin Step 2.

l You can set the port attributes as need. Click Port Attribute. In the Port Attributes dialog boxdisplayed, you can view the port information. You can edit TAG, Port Type, Mapping Protocol,Enabling LCAS, Port Enabled and Entry Detection. Click Apply to complete the settings of theport attributes.

Step 5 Optional: In Available Trail of the Server Layer Trail tab, select an appropriate lower orderpath trail as the server trail of the trunk link tail.

NOTE

If Step 3 is executed, skip this step.

Step 6 Optional: Complete the information for this trunk link in the General Attributes tab, such asName, Order NO..

NOTE

If you want to use the default values, skip this step.


NOTE

l If you activate the trail, service configuration data is sent to the NE.

l If you do not activate the trail, the service configuration data is saved only in the U2000.

Step 8 Click Apply. A prompt is displayed, indicating that the operation is successful.

Step 9 Click Close.

----End




Issue 02 (2010-09-24)

2.2.3.3 Creating an EPL TrailIn this user interface, you can create an EPL trail.

Prerequisitel You must be an NM user with "network operator" authority or higher.l A trunk link must be created.l The Ethernet processing card and the corresponding interface card must be installed.

Procedure

Step 1 Choose Service > MSTP Trail > Create EPL from the main menu.

Step 2 Set the source and sink for EPL trail. Select Port Usage Strategy for the source and sink.

NOTE

The Port Usage Strategy parameter has the following values:

l PORT: Use this strategy to configure transparent transmission of the EPL service. This strategy usuallyapplies to point-to-point communication. The VLAN ID cannot be edited.

l PORT+VLAN: Use this strategy to configure convergence of the EPL service. This strategy appliesto point-to-point, point-to-multipoint communication, and communication among multiple points.

Step 3 Click Browse to select the appropriate PORT port. If the value of Port Usage Strategy is PORT+VLAN, the VLAN ID must be set.

NOTEWhen you set Port Usage Strategy to PORT+VLAN, you can create multiple VLANs at a time. When settingVLAN IDs, note that the sign - indicates several consecutive VLAN IDs and the sign , separates two VLANIDs. For example, 1-3,6,8-10 indicates the following VLAN IDs: 1,2,3,6,8,9,10.

Step 4 Set the trunk link. Select the route strategy for the trunk link, and perform the next operationaccordingly.l Strategy 1: Create a trunk link automatically. Set the bandwidth of the trunk link and click

Next.l Strategy 2: Create a trunk link manually. Click Next to create the trunk link. The default

value of the trunk link route strategy is Using Existing Trunk Link. Select the createdtrunk link and click Next.

l Strategy 3: Use the existing trunk link.– Specify the explicit node.

Right-click the NE that you want to set as an explicit node and choose Set AsCompulsory Node from the shortcut menu. In the Set As Compulsory Node window,specify the NE and cards.

CAUTIONWhen you specify multiple explicit nodes, you need to specify them in an order fromthe source to sink.

In the left-hand Explicit Node pane, select a node, right-click, and add a new explicitnode or delete the explicit node by using the shortcut menu.



2-103

After explicit nodes are specified, click Next.– Do not specify the explicit node.

Select a proper trunk link route and click Next.NOTE


l The route strategy for the trunk link depends on the application in practice. Usually it is recommendedthat you create a trunk link first, and then create an Ethernet trail. Hence, Use Existing Trunk Linkis the default value.

l Create Trunk Link Manually and Create Trunk Link Automatically are often used for serviceexpansion. In the former one, the source and sink of the trunk link need to be specified manually, butthe timeslot allocation can be controlled manually. In the latter one, the source and sink of the trunklink can be specified automatically, but the timeslot allocation cannot be controlled manually.

Step 5 Set the port attributes. Set the TAG, Enabling LCAS, Mapping Protocol, Port Enabled andEntry Detection parameters in Port Attribute Setting.

NOTE

Enabling LCAS needs the support of cards.

Step 6 Optional: Complete the information for the EPL trail, such as Name and Order No..NOTE


Step 7 Optional: If you do not want to activate the created trail when the configuration is issued toNEs, you can clear the selection of the Activate the trail check box.

NOTE



Step 8 Click Finish. A prompt is displayed, indicating that the operation is successful.

Step 9 Click Close.

----End


PrerequisiteThe Ethernet service must be created and activated.

Procedurel For the boards (such as N1EMS4) that support Ethernet OAM, use the Ethernet OAM

function to verify the Ethernet services.For details, refer to:– 2.2.9.1 Ethernet OAM– 2.2.9.2 Creating MPs– 2.2.9.3 Performing a CC Check




Issue 02 (2010-09-24)

– 2.2.9.4 Performing an LB Check– 2.2.9.5 Performing an LT Check– 2.2.9.6 Performing a Ping Test– 2.2.9.7 Performing Performance Detection

l For the boards (such as N1EFS0) that do not support Ethernet OAM, use the ping commandto verify the Ethernet services.1. At the source end and then the sink end of the service, use a crossover cable to connect

the port on the Ethernet board and a computer.2. Set the IP addresses of the two computers and ensure they are in the same network

segment.

NOTE

l Do not set the IP address to the 127.0.0.0 loopback address.

l Before you verify the Port+VLAN services, set the port type of the external port of theEthernet board that is connected to the computer to Access.

3. Use the ping command on one computer to ping the other computer. Run the commandping x.x.x.x -n 60. If no packet is lost, it indicates that the channel is available.

----End

2.2.3.5 Sample Application: Configuring EPL ServicesThis topic uses an example to describe how to plan the service parameters and complete theentire process of configuring the point-to-point EPL service by trail method.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The license for SDH and Ethernet trail management must be provided.

ContextProject Network Design

As shown in Figure 2-21, NE1 and NE2 adopt the OptiX RTN 600 NEs configured with theIDU 620. The new service requirements are as follows:

l The two branches of User A that are located at NE1 and NE2 need communicate with eachother over Ethernet. A 10 Mbit/s bandwidth is required.

l The two branches of User B that are located at NE1 and NE2 need communicate with eachother over Ethernet. A 20 Mbit/s bandwidth is required.

l The service of User A need be isolated from the service of User B.l The Ethernet equipment of User A and User B provide 100 Mbit/s Ethernet electrical ports

of which the working mode is auto-negotiation, and does not support VLAN.



2-105

Figure 2-21 Networking diagram

NE 1 NE2

User A1 User A2

User B1 User B2

NE Panel

In the following example, NE1 and NE2 can use Ethernet transparent transmission boards tocreate point-to-point EPL services. Slot 8 on NE1/NE2 houses the EFT4 board.

Figure 2-22 IDU board configuration

FAN

Slot 20

EXT Slot7

EXT Slot5

PXC Slot3

PXC Slot1

EXT Slot8

EXT Slot6

EXT Slot4

SCC Slot2

IF1A

IF1A

PH1PXC

PXC SCC

FAN

EMS

Service Configuration Diagram

Figure 2-23 Configuring Ethernet services

Timeslot Allocation Information

l The EPL service of User A is as follows:– Occupies VC-12 timeslots 17-21 of the first VC-4 on the radio link between NE1 and

NE2.– Uses VC-12 timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE1 and

VC-12 timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/dropservices.




Issue 02 (2010-09-24)

l The EPL service of User B is as follows:– Occupies VC-12 timeslots 22-31 of the first VC-4 on the radio link between NE1 and

NE2.– Uses VC-12 timeslots 6-15 in the second VC-4 of the EFT4 board in slot 8 of NE1 and

VC-12 timeslots 6-15 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/drop services.

Figure 2-24 Timeslot allocation of Ethernet services

Process

1. Creating a Link Server Trail2. Creating a Trunk Link3. Creating an EPL Trail4. Verifying Ethernet Services

The following procedure describes how to configure EPL services based on the network that ispreviously configured.

Procedure

Step 1 Creating a Link Server Trail1. Choose Service > SDH Trail > Create SDH Trail from the Main Menu.2. Set the service direction to Bidirectional and set the service level to Link Server Trail.3. Set Resource Usage Strategy and Protection Priority Strategy.

Set the parameters as follows:

l Resource Usage Strategy: Protected Resourcel Protection Priority Strategy: Trail Protection First

4. Double-click the source NE and the sink NE in turn. The automatically selected route isdisplayed between the NEs.


In the right-hand pane, double-click to select the source NE NE1 and the sink NE NE5.Double-click again can cancel the selection. Alternatively, click Browse to select an NE.The sign appears on the source NE and the sign appears on the sink NE.



2-107

5. Click Set Route Timeslot. The Set Route Timeslot dialog box is displayed. Select thetimeslot and click OK.

Parameter settings:

Timeslot: 16. Click the General Attributes tab and set the general attributes of the trail, such as the

Name and Order No..


Name: NE1-NE2-Link Server Trail-0001

The Trail View where you create a link server trail is as follows:

7. Click Apply. In the Operation Result dialog box displayed, click Close.

Step 2 Creating a Trunk Link

NOTE

You must create one trunk link from A1 (NE1) to A2 (NE2) and one trunk link from B1 (NE1) to B2 (NE2).

1. Choose Service > MSTP Trail > Create Trunk Link from the Main Menu.2. Set the Bandwidth parameter.


Bandwidth: 5 X VC12.3. Check the Auto Create Server Trail check box.4. Set the Source and Sink. Click Browse to select the appropriate VCTRUNK ports.

l Set parameters for a trunk link from A1 (NE1) to A2 (NE2) as follows:– The source of the trunk link:

– Source: NE1-8-EMS-VCTRUNK1– Bound Timeslot: NE1-8-EMS-1(SDH-1)-VC4-1-VC12(6-10)

– The sink of the trunk link:– Sink: NE2-8-EMS-VCTRUNK1




Issue 02 (2010-09-24)

– Bound Timeslot: NE2-8-EMS-1(SDH-1)-VC4-1-VC12(6-10)l Set parameters for a trunk link from B1 (NE1) to B2 (NE2) as follows:

– The source of the trunk link:– Source: NE1-8-EMS-VCTRUNK2– Bound Timeslot: NE1-8-EMS-1(SDH-1)-VC4-1-VC12(11-20)

– The sink of the trunk link:– Sink: NE2-8-EMS-VCTRUNK2– Bound Timeslot: NE2-8-EMS-1(SDH-1)-VC4-1-VC12(11-20)

5. Complete the information for this trunk link in the General Attributes tab, such asName, Order NO..


l The trail name of the trunk link from A1 (NE1) to A2 (NE2): Trunk_Link-0001.l The trail name of the trunk link from B1 (NE1) to B2 (NE2): Trunk_Link-0002.

6. If you do not want to activate the created trail when the configuration is issued to NEs, youcan uncheck the Activate the trail check box.The Trail View where you create a trunk link is as follows:

7. Click Apply.

Step 3 Creating an EPL TrailNOTE

You must create one EPL trail from A1 (NE1) to A2 (NE2) and one EPL trail from B1 (NE1) to B2 (NE2).

1. Choose Service > MSTP Trail > Create EPL from the main menu.2. Set the source and sink for EPL trail. Select Port Usage Strategy for the source and sink.


Port Usage Strategy: Port+VLAN3. Click Browse to select the appropriate PORT port. If the value of Port Usage Strategy is

PORT+VLAN, the VLAN ID must be set.



2-109

l Set parameters for an EPL trail from A1(NE1) to A2 (NE2) as follows:

– Source Port: NE1-8-EMS-PORT3.

– Source VLAN ID: 3.

– Sink Port: NE2-8-EMS-PORT3.

– Sink VLAN ID: 3.

l Set parameters for an EPL trail from B1 (NE1) to B2 (NE2) as follows:

– Source Port: NE1-8-EMS-PORT4.

– Source VLAN ID: 4.

– Sink Port: NE2-8-EMS-PORT4.

– Sink VLAN ID: 4.

4. Set the trunk link. Select the route strategy for the trunk link, and perform the next operationaccordingly.

l Set parameters for an EPL trail from A1 (NE1) to A2 (NE2) as follows:

– Trunk Link Route Strategy: Use Existing Trunk Link

– Trunk link: Trunk_Link-0001

l Set parameters for an EPL trail from B1 (NE1) to B2 (NE2) as follows:

– Trunk Link Route Strategy: Use Existing Trunk Link

– Trunk link: Trunk_Link-0002

5. Set the port attributes. Set the TAG, Enabling LCAS, Mapping Protocol, PortEnabled and Entry Detection parameters in Port Attribute Setting.

Parameter settings:

l Set port attributes for NE1.

– TAG: Tag Aware

– Port Enabled: Enabled

l Set port attributes for NE5.

– TAG: Access

– Port Enabled: Enabled6. Complete the information for the EPL trail, such as Name and Order No..7. If you do not want to activate the created trail when the configuration is issued to NEs, you

can clear the selection of the Activate the trail check box.

8. Click Finish. A prompt is displayed, indicating that the operation is successful.

Step 4 Verifying Ethernet Services

1. At the source end and then the sink end of the service, use a crossover cable to connect theport on the Ethernet board and a computer.

2. Set the IP addresses of the two computers and ensure they are in the same network segment.

NOTE


l Before you verify the Port+VLAN services, set the port type of the external port of the Ethernetboard that is connected to the computer to Access.




Issue 02 (2010-09-24)


----End

2.2.4 Configuring an Unterminated EPL ServiceThis section describes how to configure the unterminated EPL service by using the trailmanagement function.

ContextAs shown in Figure 2-25, the server trail for an unterminated EPL service can be a terminatedtrunk link or an unterminated trunk link. The sink of the terminated trunk link must be locatedon an EOD card.

Figure 2-25 Server trail for an unterminated EPL service

Unterminatedtrunk link

One-sourceand one-sink

trunk link

One-sourceand multi-sink

trunk link

UnterminatedEPL trail

SDH trail from anEthernet card to

multiple SDH line cards

SDH trail from anEthernet card to an

SDH line card

SDH trail from anEthernet card to

one EOD line card

SDH trail from anEthernet card tomultiple

EOD line cards

A->B: A is the server trail of B. That is, B is the client trail of A.

NOTE

Currently, the NMS supports the functions of searching, creating, and managing one-source and multi-sinktrunk links.


2.2.4.2 Creating an Unterminated Trunk LinkBefore creating an unterminated EPL service, you need to create a server trail for theunterminated EPL service. An unterminated trunk link is the server trail of the unterminatedEPL service. There are four types of paths for the unterminated trunk link: VC12 virtualconcatenation, VC3 virtual concatenation, VC4 virtual concatenation, and VC4 adjacentconcatenation.




2-111

2.2.4.4 Creating an Unterminated EPL TrailWhen the planned sink of an EPL service is not located on a Huawei network, you need to createan unterminated EPL trail.











ProcedureStep 1 Choose Service > SDH Trail > Create SDH Trail from the Main Menu.



NOTE

Pay attention to the following points when setting the parameters:l Resource Usage Strategy defines the protection subnet resources or timeslots available during trail

creation. The values are Protected Resource, Extra Resource and All Resource.l Protection Priority Strategy defines the protection subnet resources to be selected first during trail

creation. The values are Trail Protection First, SNCP First and NP First.





Issue 02 (2010-09-24)











NOTE







2-113

NOTE






----End

2.2.4.2 Creating an Unterminated Trunk Link

Before creating an unterminated EPL service, you need to create a server trail for theunterminated EPL service. An unterminated trunk link is the server trail of the unterminatedEPL service. There are four types of paths for the unterminated trunk link: VC12 virtualconcatenation, VC3 virtual concatenation, VC4 virtual concatenation, and VC4 adjacentconcatenation.


l The SDH trail at the corresponding level must be created. The source is the port of a datacard and the sinks are the ports of N SDH line cards. N can be 1 or 2.

Procedure

Step 1 Choose Service > MSTP Trail > Create Unterminated Trunk Link from the Main Menu.

Step 2 In the Bandwidth area, select the number and the types of the paths.

Step 3 In the topology, double-click the terminated NE, or click Browse. The Select Board Port-Source dialog box is displayed. Select boards and ports.

Step 4 Click OK. The source information is displayed in the Source group box.

Step 5 In the Existing Server Trail area, select a server trail.

Step 6 Optional: Click Port Attribute. In the Port Attributes dialog box displayed, double-click thecells of each attribute to set the attributes. Use the default values unless otherwise requested.

Step 7 Enter the information related to the Ethernet trails, such as Name, Order No..

NOTE

If the default values are used, you can skip this step.





Issue 02 (2010-09-24)

NOTE

l In the case of the active trail, the service configuration data is issued to the NE side.

l In the case of the inactive trail, the service configuration data is saved at the U2000 side.

Step 9 Click Apply. The Operation Result dialog box is displayed. Click Close.

----End



Procedure




NOTE










2-115

NOTE







NOTE



NOTE



NOTE




Step 9 Click Close.

----End

2.2.4.4 Creating an Unterminated EPL TrailWhen the planned sink of an EPL service is not located on a Huawei network, you need to createan unterminated EPL trail.

Prerequisitel You must be an NM user with "network operator" authority or higher.l There must be the unterminated trunk links to carry the unterminated EPL service to be

created. If the unterminated trunk link does not exist, see 2.2.4.2 Creating anUnterminated Trunk Link.

ContextNOTE

The server trail of an unterminated EPL service can be a terminated trunk link whose sink must be locatedon an EOD card.




Issue 02 (2010-09-24)

Procedure

Step 1 Choose Service > MSTP Trail > Create Unterminated EPL from the Main Menu.

Step 2 Select Port Usage Strategy for the source.

NOTEPort Usage Strategy includes the following two types:

l Port: configure an EPL service that is transmitted transparently. This strategy is applicable to the point-to-point communication usually. You cannot edit VLAN ID.

l Port+VLAN: configure the Ethernet services that are converged. This strategy is applicable to thepoint-to-point, point-to-multipoint and inter-multipoint communication.

Step 3 Select the source of the unterminated service. In the topology, double-click the source NE, orclick Browse. The Select Board Port-Source dialog box is displayed. Select boards and ports.

Step 4 Click OK. In the Existing Server Trail area, select the server trail available.

Step 5 Click Next to set other attributes.

Step 6 Optional: In the Port Attribute Setting group box, double-click the cells to set the portattributes as required.

Step 7 Enter the information related to the Ethernet trails, such as Name, Order No..NOTE



NOTE

l In the case of the active trail, the service configuration data is issued to the NE side.

l In the case of the inactive trail, the service configuration data is saved at the U2000 side.

Step 9 Click Finish and the Operation Result dialog box is displayed. Click Close.

----End




function to verify the Ethernet services.For details, refer to:– 2.2.9.1 Ethernet OAM– 2.2.9.2 Creating MPs– 2.2.9.3 Performing a CC Check– 2.2.9.4 Performing an LB Check



2-117

– 2.2.9.5 Performing an LT Check– 2.2.9.6 Performing a Ping Test– 2.2.9.7 Performing Performance Detection



segment.

NOTE




----End

2.2.5 Configuring EVPL ServicesYou can use the trail function to configure EVPL services.



2.2.5.3 Creating an EVPL TrailYou can create an EVPL trail.







low order cross-connection protection pairs are created in U2000.




Issue 02 (2010-09-24)

l The OptiX OSN 9500 NE must have the GXCL or EXCL board where the lower ordercross-connection protection pairs are created in U2000.

l The available resources must be sufficient.




Procedure




NOTE










2-119








NOTE





NOTE






----End






Issue 02 (2010-09-24)

Procedure




NOTE








NOTE







NOTE



NOTE





2-121

NOTE




Step 9 Click Close.

----End

2.2.5.3 Creating an EVPL Trail

You can create an EVPL trail.

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

l A trunk link must be created.

l The Ethernet processing board and the corresponding interface board must be installed.

Procedure

Step 1 Choose Service > MSTP Trail > Create EVPL from the Main Menu.

Step 2 Set the EVPL source and sink. Select Port Usage Strategy for the source and sink.

NOTE

The Port Usage Strategy parameter has the following three values:

l PORT: Use this strategy to configure transparent transmission of the EVPL service. This strategyusually applies to point-to-point communication. The VLAN ID cannot be edited.

l PORT+VLAN: Use this strategy to configure convergence of the EVPL service. This strategy appliesto point-to-point, point-to-multipoint communication, and communication among multiple points.

l PORT+MPLS: Configure port-shared EPL services that are distinguished by MPLS labels.

Step 3 Click Browse to select the appropriate PORT port. If the value of Port Usage Strategy is PORT+VLAN, the VLAN ID must be set. If the value of Port Usage Strategy is PORT+MPLS, thetunnel flag must be set.

NOTEWhen you set Port Usage Strategy to PORT+VLAN, you can create multiple VLANs at a time. When settingVLAN IDs, note that the sign - indicates several consecutive VLAN IDs and the sign , separates two VLANIDs. For example, 1-3,6,8-10 indicates the following VLAN IDs: 1,2,3,6,8,9,10.

Step 4 Set the trunk link. Select the route strategy for the trunk link, and perform the next operation.

l Strategy 1: Create the trunk link automatically. Set the bandwidth of the trunk link andclick Next.

l Strategy 2: Create a trunk link manually. Click Next to create the trunk link. The defaultvalue of the trunk link route strategy is Using Existing Trunk Link. Select the createdtrunk link and click Next.

l Strategy 3: Use the existing trunk link. Select an existing trunk link trail and click Next.




Issue 02 (2010-09-24)

NOTE




Step 5 Set the port attributes. Set the TAG, Port Type, Encapsulation Format, Enabling LCAS,Mapping Protocol, Port Enabled and Entry Detection parameters in Port AttributeSetting.

Step 6 Optional: Complete the information for this EVPL trail, such as Name and Order No..

NOTE



NOTE



Step 8 Click Finish. A prompt is displayed, indicating that the operation is successful.

----End

2.2.5.4 Verifying Ethernet Services

After you configure Ethernet services, you need to verify whether service channels are available.






2-123

– 2.2.9.4 Performing an LB Check

– 2.2.9.5 Performing an LT Check

– 2.2.9.6 Performing a Ping Test

– 2.2.9.7 Performing Performance Detection

l For the boards (such as N1EFS0) that do not support Ethernet OAM, use the ping commandto verify the Ethernet services.

1. At the source end and then the sink end of the service, use a crossover cable to connectthe port on the Ethernet board and a computer.

2. Set the IP addresses of the two computers and ensure they are in the same networksegment.

NOTE




----End

2.2.6 Configuring EPLAN ServiceYou can use the trail function to configure EPLAN services.



2.2.6.3 Creating an EPLAN TrailYou can create an EPLAN trail.

2.2.6.4 Adjusting VB Mount Ports in an EPLANBy adjusting the VB mount ports for each EPLAN node, you can reallocate Ethernet serviceports, so that the accessed Ethernet services can be changed without changing the structure ofthe whole EPLAN.








Issue 02 (2010-09-24)

l A protection subnet must be created for release 4.0 NEs, including the OptiX 155/622H(Metro 1000), the OptiX 155/622, the OptiX 2500+ (Metro 3000), and the OptiX Metro3100 and so on.







Procedure




NOTE







2-125











NOTE





NOTE






----End




Issue 02 (2010-09-24)

2.2.6.2 Creating a Trunk Link

Before creating EPL, Unterminated EPL, EVPL and EPLAN trails, create a trunk link as thebearer trail.


Procedure




NOTE








NOTE









2-127

NOTE



NOTE



NOTE




Step 9 Click Close.

----End

2.2.6.3 Creating an EPLAN TrailYou can create an EPLAN trail.

Prerequisitel You must be an NM user with "network operator" authority or higher..l A trunk link must be created.l Before adding a VB node to an EPLAN trail, you must create a trunk link between a port

of the new node and a port of the EPLAN trail.l The Ethernet processing board and the corresponding interface board must be installed.

ContextThe U2000 does not use an existing VB even if this VB is not used by another trail and is thesame as the VB to be created, that is, the mounted ports are the same.

Besides the EPLAN service described 2.2.1.2 Ethernet Services, you can also create the EPLANservice as shown in Figure 2-26. The VB1 and VB2 that are located on the two Ethernet boardson NE3 are added to the trail at a time. The two VBs are connected by using the mono nodaltrunk link, which is not provided in the figure.




Issue 02 (2010-09-24)

Figure 2-26 EPLAN between different boards on an NE

VCTRUNK1

VCTRUNK2

VCTRUNK1 VCTRUNK1

PORT1

PORT1 PORT1

A1 A2NE1 NE2

NE3

VB1 VB1

VB1 VB2

A3 A4

PORT2

Procedure

Step 1 Choose Service > MSTP Trail > Create EPLAN from the Main Menu.

Step 2 Double-click an NE in the topology. The Select Board Port dialog box is displayed.

Step 3 Select a board in Slot Layout. Select appropriate ports in Available Timeslots/Port and clickthe double-right-arrow button. Click OK.



2-129

NOTE

To create the service as shown in Figure 2-26, you need to select the board and port where the VB1 islocated on NE3, right-click, and then choose Select Board Port from the shortcut menu. In the dialog boxdisplayed, select the board and port where the VB2 is located on NE3.

Step 4 Repeat Steps 2 and 3 to select ports on other NEs.

Step 5 Set the trunk link. Select the route strategy for the trunk link, and perform the next operation.l Strategy 1: Create a trunk link manually. Click Next to create the trunk link. After it is

created, click Next. The default value of the trunk link route strategy is Using ExistingTrunk Link. Select the created trunk link and click Next.

l Strategy 2: Use the existing trunk link. Select an existing trunk link and click Next.NOTE


l The route strategy for the trunk link depends on the application in practice. It is recommended that youcreate the trunk link trail first, and then create the Ethernet trail. Hence, Use Existing Trunk Link isthe default value.

l Create Trunk Link Manually is often used for service expansion.

l To create the service as shown in Figure 2-26, you need to create a trunk link whose source and sinkare the ports of VB1 and VB2 on NE3.

Step 6 Set port attributes for all ports on the Ethernet trail, such as TAG, Mapping Protocol, PortEnabled, Enabling LCAS and Entry Detection.

Step 7 Create VLAN. Click Add in VLAN Configuration. The VLAN Configuration for EthernetTrail dialog box is displayed.

NOTE

The VLAN can only be created on the port where the Bridge Switch Mode is set to IVL/Ingress FilterEnable(VB).

Step 8 Enter VLAN ID. Select appropriate mounted ports in the Available Mounted Ports pane, and

click .

Step 9 Click OK or Apply. Repeat Steps 7 through 9 to create more VLANs.

Step 10 Click Next. Enter the information related to the EPLAN trail, such as Name and Order No..NOTE



NOTE






Issue 02 (2010-09-24)

Step 12 Click Finish. A prompt appears is displayed, indicating that the operation is successful.

----End

2.2.6.4 Adjusting VB Mount Ports in an EPLANBy adjusting the VB mount ports for each EPLAN node, you can reallocate Ethernet serviceports, so that the accessed Ethernet services can be changed without changing the structure ofthe whole EPLAN.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The EPLAN trail must be created.

Context

CAUTIONTo delete a port mounted to the VB, make sure that it does not belong to any VLAN filteringtable. Otherwise, the deletion fails.

Procedurel Adding a VB Mount Port

1. Choose Service > MSTP Trail > Manage Ethernet Trail from the Main Menu.2. Select filter criteria. After the filtering is complete, select a trail in the Ethernet trail

list and click the Node tab.3. Right-click an appropriate node in the node list and choose Configure VB attached

port from the shortcut menu. The VB Configuration for Ethernet Trail dialog boxis displayed.

4. Select an appropriate port from the Available Mounted Ports pane and click .Click OK.



2-131

5. Repeat Steps 1 to step 4 to add VB mount ports for other nodes as required.l Deleting a VB Mount Port

NOTE

To delete a mounted port, make sure that it is not a forwarding port of any VLAN filtering table.

1. In the NE Explorer, select the Ethernet board used for the EPLAN, and chooseConfiguration > Ethernet Service > Ethernet LAN Service from the Function Tree.Click the VLAN Filtering tab.

2. Check whether the port is included in any VLAN filtering table. If the port is included,select the VLAN and click Modify to delete the port from the VLAN filtering table.

3. Choose Trail > Ethernet Trail Management. Select the EPLAN trail from theEthernet trail list and then click the Node tab.

4. Right-click an appropriate node in the node list and choose Configure VB attachedport from the shortcut menu. The VB Configuration for Ethernet Trail dialog boxis displayed.

5. Select an appropriate port from the Selected Mounted Ports pane and click .Click OK.

6. Repeat Steps 1 through 6 to delete the mounted ports for other nodes.

----End





function to verify the Ethernet services.For details, refer to:– 2.2.9.1 Ethernet OAM




Issue 02 (2010-09-24)

– 2.2.9.2 Creating MPs– 2.2.9.3 Performing a CC Check– 2.2.9.4 Performing an LB Check– 2.2.9.5 Performing an LT Check– 2.2.9.6 Performing a Ping Test– 2.2.9.7 Performing Performance Detection



segment.

NOTE




----End

2.2.7 Configuring EVPL (QinQ) ServiceYou can use the trail function to configure EVPL (QinQ) services.



2.2.7.3 Creating an EVPL (QinQ) TrailYou can create an EVPL (QinQ) trail.







2-133







Procedure




NOTE






click Cancel Route Restriction to cancel the selection.




Issue 02 (2010-09-24)









NOTE





NOTE






----End

2.2.7.2 Creating a Trunk Link

Before creating EPL, Unterminated EPL, EVPL and EPLAN trails, create a trunk link as thebearer trail.



2-135


Procedure




NOTE








NOTE







NOTE






Issue 02 (2010-09-24)

NOTE



NOTE




Step 9 Click Close.

----End

2.2.7.3 Creating an EVPL (QinQ) TrailYou can create an EVPL (QinQ) trail.

Prerequisitel You must be an NM user with "network operator" authority or higher.l A trunk link must be created.l The Ethernet processing board and the corresponding interface board must be installed.

Procedure

Step 1 Choose Service > MSTP Trail > Create EVPL(QinQ) from the Main Menu.

Step 2 Set the direction of the trail.

Step 3 Select Port Usage Strategy for the source and sink.

NOTE

The Port Usage Strategy parameter has the following two values:

l PORT: Use this strategy to configure transparent transmission of the EVPL service. This strategyusually applies to point-to-point communication.

l PORT+VLAN: Use this strategy to configure convergence of the EVPL service. This strategy appliesto point-to-point, point-to-multipoint communication, and communication among multiple points.

Step 4 Select the Operation Type for the source and sink.

Step 5 Click Browse to select the appropriate port.

Step 6 Set S-VLAN and C-VLAN tag depending on the selected operation type.

Step 7 Set the trunk link. Select the route strategy for the trunk link, and then perform the next operation.l Strategy 1: Create the trunk link automatically. Set the bandwidth of the trunk link and

click Next.l Strategy 2: Create a trunk link manually. Click Next to create the trunk link. The default

value of the trunk link route strategy is Using Existing Trunk Link. Select the createdtrunk link and click Next.

l Strategy 3: Use the existing trunk link. Select an existing trunk link trail and click Next.



2-137

NOTE




Step 8 Set the port attributes. Set the TAG, Port Type, Mapping Protocol, Port Enable, EnablingLCAS and Entry Detection parameters in Port Attribute Setting.

Step 9 Optional: Complete the information for this EVPL(QinQ) trail, such as Name and OrderNo..

NOTE



NOTE



Step 11 Click Finish. A prompt appears telling you that the operation was successful.

----End









Issue 02 (2010-09-24)

– 2.2.9.4 Performing an LB Check

– 2.2.9.5 Performing an LT Check

– 2.2.9.6 Performing a Ping Test

– 2.2.9.7 Performing Performance Detection

l For the boards (such as N1EFS0) that do not support Ethernet OAM, use the ping commandto verify the Ethernet services.

1. At the source end and then the sink end of the service, use a crossover cable to connectthe port on the Ethernet board and a computer.

2. Set the IP addresses of the two computers and ensure they are in the same networksegment.

NOTE




----End

2.2.8 Specifying a Customer for a Created TrailYou can specify a customer for a created trail according to actual demands for the purpose ofnetwork maintenance.


l The trail must be created.

l The customer must be created.

Procedure

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


NOTE




Step 3 In the trail list, right-click a trail and choose Details.

Step 4 In the Details dialog box, select a proper customer from the Customer drop-down list. ClickOK.

----End



2-139

2.2.9 Checking the Connectivity of Ethernet LinkYou can perform Ethernet operation, administration and maintenance (OAM).

2.2.9.1 Ethernet OAMYou can maintain Ethernet Layer 2 by using the Ethernet OAM feature.

2.2.9.2 Creating MPsYou must create maintenance points (MPs) before executing the Ethernet OAM operations.

2.2.9.3 Performing a CC CheckYou can perform a consecutive check (CC) on Ethernet services to check the connectivity ofservices for locating and handling faults.

2.2.9.4 Performing an LB CheckYou can perform a loopback (LB) check on Ethernet services without interrupting services tocheck the connectivity of the services for locating and handling faults.

2.2.9.5 Performing an LT CheckYou can perform a link trace (LT) check on Ethernet services to check the MIP information inthe link for locating and handling faults.

2.2.9.6 Performing a Ping TestYou can perform a ping test to check if the opposite end is reachable.

2.2.9.7 Performing Performance DetectionYou can perform performance detection, to check if a link between two nodes is normal.

2.2.9.1 Ethernet OAM

You can maintain Ethernet Layer 2 by using the Ethernet OAM feature.

With the growth of Ethernet services, more Ethernet services are applied in MAN and WANnetworks. Thus, there is an increased focus on the maintainability of Ethernet services. Currently,the ways to maintain Ethernet Layer-2 are limited. Thus, the ways of operating, managing andmaintaining the Ethernet services through a transport network are limited.

The Ethernet OAM contains IEEE 802.1ag ETHOAM and IEEE 802.3ah ETHOAM. The IEEE802.1ag ETHOAM is used to realize networkwide end-to-end Ethernet OAM function and IEEE802.3ah ETHOAM is used to realize the OAM function in the last one kilometer at the accessside of a transmission network.

IEEE 802.1ag ETHOAM

Ethernet OAM implements the automatic fault detection, fault location and fault isolationthrough continuity check (CC), in-service loopback (LB), link trace (LT), Ping Test andPerformance Detection operations. In this way, OAM capability of Ethernet services isimproved.

The operation objects of Ethernet OAM are the maintenance points, which include maintenanceend points (MEPs) and maintenance intermediate points (MIPs).

The Ethernet OAM is implemented when an MEP initiates fault detection. When the MP detectsa fault, it reports alarms. These alarms are correctly synchronized to the Ethernet trails, whichare related to the MPs.




Issue 02 (2010-09-24)

IEEE 802.3ah ETHOAM

Ethernet OAM function uses discovery to check whether the opposite equipment supports the802.3ah OAM function.

Ethernet OAM function uses error frame monitor to check link performance condition.

Ethernet OAM function uses remote alarm support for link event to check remote failures.

2.2.9.2 Creating MPs

You must create maintenance points (MPs) before executing the Ethernet OAM operations.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The Ethernet trail must be created and activated.

Context

The MPs include maintenance end points (MEPs) and maintenance intermediate points (MIPs).All the OAM functions must be initiated by the MEPs. The MIP does not send any OAM frames,but responds to:l LT framesl LB frames where the destination node is the MIP itself

An MP cannot be created automatically in the following situations:l An unidirectional Ethernet trail is selected.l The PORT port at the source or sink of the selected bidirectional Ethernet trail does not

support the creation of OAM nodes.l The bidirectional Ethernet trail that is selected is the Layer 2 switching service based on

PORT+C-VLAN+S-VLAN.

The following Ethernet services supports the automatic creation of MPs.l EPLl EVPLl EVPL(QinQ)

The following Ethernet services does not support the automatic creation of MPs. But you canperform the manual configuration.l EPLANl RPR EVPLl RPR EVPLAN

Procedure

Step 1 Choose Service > MSTP Trail > Manage Ethernet Trail from the Main Menu. Select abidirectional Ethernet trail and click Ethernet Service OAM.

Step 2 Click New and the Create MP dialog box is displayed. Complete the information.



2-141

NOTE

l VLAN ID: Leave this field blank for PORT services. For PORT+VLAN services, set the VLAN IDof the services to be monitored.

l Direction: This indicates the direction of transmitting and receiving the OAM data from the MP to themaintenance area. If the data is from the board, the MP direction is SDH. If the data is from the outsideof the board, the MP direction is IP. The MIPs can be only bidirectional.

Step 3 Optional: Click Advanced. In the dialog box displayed, set the corresponding parameters andclick OK.

Step 4 Click OK. A prompt appears telling you that the operation was successful. Click Close to finishthe operation.

----End

2.2.9.3 Performing a CC CheckYou can perform a consecutive check (CC) on Ethernet services to check the connectivity ofservices for locating and handling faults.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The MEP maintenance point must be created.

ContextDuring the CC check, the source MEP constructs and transmits CC frames periodically. Thedestination MEP receives the CC frames and starts the CC check. If the destination MEP doesnot receive the CC frames from the source within a specified period of time (for example, 3.5times the transmit period), the MEP automatically reports the CCLOS alarm.

ProcedureStep 1 Choose Service > MSTP Trail > Manage Ethernet Trail from the Main Menu. Select a

bidirectional Ethernet trail and click Ethernet Service OAM.

Step 2 Select the node that you want to monitor, click OAM Operation and select Activate CC. Aprompt appears telling you that the operation was successful. Click Close.

NOTE

Before you perform the check, set an appropriate CCM Sending Period as required.

----End

2.2.9.4 Performing an LB CheckYou can perform a loopback (LB) check on Ethernet services without interrupting services tocheck the connectivity of the services for locating and handling faults.




Issue 02 (2010-09-24)


l The MEP maintenance point must be created.

ContextDuring the LB check, the source MEP constructs and transmits the LBM frames and starts thetimer. If the destination MP receives the LBM frames, it sends the LBR frames back to the sourceMEP. This indicates that the loopback is successful. If the source MEP timer times out, itindicates that the loopback fails.

Procedure


Step 2 Select the node that you want to monitor, click OAM Operation and select Start LB. The LBTest dialog box is displayed.

Step 3 Enter the LB test source maintenance point ID and sink maintenance point ID.

Step 4 Click Start LB and the check result is displayed.

NOTE

Before you perform the check, set an appropriate LB Timeout as required.

----End

2.2.9.5 Performing an LT Check

You can perform a link trace (LT) check on Ethernet services to check the MIP information inthe link for locating and handling faults.


l The MEP maintenance point must be created.

ContextDuring the LT check, the source MEP constructs and transmits LTM frames and starts the timer.All the MPs that receive the LTM frames send the LTR frame response. According to the LTRframe response, you can verify all the MIPs that pass from the source MEP to the destinationMEP.



2-143

Procedure


Step 2 Select the node that you want to monitor, click OAM Operation and select Start LT. The LTTest dialog box is displayed.

Step 3 Enter the LT test source maintenance point ID and sink maintenance point ID.

Step 4 Click Start LT and the check result is displayed.

NOTE

Before you perform the check, set an appropriate LT Timeout as required.

----End

2.2.9.6 Performing a Ping TestYou can perform a ping test to check if the opposite end is reachable.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The OAM maintenance node of a service must be created for an Ethernet board. The type

of the maintenance node is MEP.

ContextPerforming a ping test does not affect the service.

Procedure


Step 2 Optional: Click Query to query OAM information from the NE.

Step 3 Select a node, click OAM Operation and select Start Ping. The Ping Test window is displayed.

Step 4 Set Send Mode.l If you select Burst Mode, you need to set Packet Length, Timeout, and Ping Attempts.l If you select Continue Mode, you need to set Packet Length, and Timeout.

Step 5 In the IP Address Configuration area, set Destination IP Address and Local IP Address.

Step 6 Click Start Ping and view the returned result in the Detail pane.

----End




Issue 02 (2010-09-24)

2.2.9.7 Performing Performance DetectionYou can perform performance detection, to check if a link between two nodes is normal.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The OAM maintenance node of a service must be created for an Ethernet board. The type

of the maintenance node is MEP.

ContextPerforming performance detection does not affect the service.

Procedure


Step 2 Optional: Click Query to query OAM information from the NE.

Step 3 Select a node, click OAM Operation and select Performance Detect. The PerformanceDetect window is displayed.

Step 4 Set Send Mode.l If you select Burst Mode, you need to set Packet Length, Timeout, and Detect

Attempts.l If you select Continue Mode, you need to set Packet Length, and Timeout.

Step 5 In the Maintenance Point area, set Source MP ID and Destination MP ID.

Step 6 Click Start Detect and view the returned result in the Detail pane.

----End

2.2.10 Viewing Ethernet ServicesThe network maintainer or administrator must know about the occupied resources and servicestatuses in time.

ContextThe bearer trails for Ethernet trails are trunk links, and the bearer trails for trunk links are SDHtrails. To view the information of Ethernet trails, you can use the following methods:

2.2.10.1 Viewing Trunk LinksYou can view the trunk link information.

2.2.10.2 Analyzing the Trunk Link FaultThis section describes how to query relevant information about the trunk link status.

2.2.10.3 Viewing Relevant Trails of a Trunk LinkThe trunk link trail is located between its client layer Ethernet trail and server layer SDH trail.When you view the trunk link, you can also view its relevant server and client trails. Thisfacilitates management and maintenance.

2.2.10.4 Viewing Ethernet Trails



2-145

By viewing Ethernet trails, you can know the trail details such as the route and occupiedresources.

2.2.10.5 Viewing the Server Trail of an Ethernet TrailThe server trail of an Ethernet trail is the trunk link. When you view the Ethernet trail, you canalso view its trunk link.

2.2.10.6 Analyzing the Ethernet Trail FaultYou can query the status of an Ethernet trail.

2.2.10.7 Viewing the Connectivity of Ethernet Services NetworkwideThe U2000 periodically checks the connectivity of the trails that receive alarm notifications anddisplays the result. You can learn about the connectivity of services networkwide by viewingthe check result and thus adopt different handling policies. For example, the alarm that causesservice interruption is handled with priority.

2.2.10.1 Viewing Trunk Links

You can view the trunk link information.


l The trunk link is created.

Procedure

Step 1 Choose Service > MSTP Trail > Manage Trunk Link from the Main Menu.

Step 2 In the Filter dialog box displayed, select the filter criteria. The desired trails are displayed inthe trail list.

NOTE

l If you need to filter all trails on the U2000, click Filter All.

l Based on the existing trails, to add trails that meet the new criteria, click Incremental Filter.

l Based on the existing trails, to filter the trails again according to the new criteria, click SecondaryFilter.

Step 3 Click a link and view the trail attributes in the trunk link list.

l If you want to view the details of a trail, right-click the trail in the list and choose Detailsfrom the shortcut menu. The Details window is displayed. View the information and thenclick OK.

l If you want to view the SDH trail used by the trunk link, click the trunk link in the list andclick the Channel Member tab.

l If you want to view the source or sink port attributes of a trail, click the trail in the list andclick the Port Attributes tab.

----End

2.2.10.2 Analyzing the Trunk Link Fault

This section describes how to query relevant information about the trunk link status.




Issue 02 (2010-09-24)


l Trunk links must be created and in the active state.

l Trunk links must be already terminated.

Procedure


Step 2 In the Filter dialog box displayed, select the filter criteria. Then, the desired trails are displayedin the trail list.

NOTE

l To filter all the trails on the U2000, click Filter All.

l To add trails that meet the new criteria based on the existing trails, click Incremental Filter.

l To filter the trails again according to the new criteria based on the existing trails, click SecondaryFilter.

Step 3 Select a trunk link in the trail list, right-click, and then choose Analyse Trail Status.

Step 4 In the displayed window, view Trail Status.

----End

2.2.10.3 Viewing Relevant Trails of a Trunk Link

The trunk link trail is located between its client layer Ethernet trail and server layer SDH trail.When you view the trunk link, you can also view its relevant server and client trails. Thisfacilitates management and maintenance.


l The trunk link must be created.

Procedure



NOTE




Step 3 If you want to view server layer trail, right-click a trunk link in the list and choose BrowseRelevant Server Trails from the shortcut menu. The SDH Trail Management interface isdisplayed, showing the server trail of the trunk link trail.



2-147

NOTE

To go back from the server trail to the trunk link, right-click the server trail, and choose Browse RelevantClient Trails.

----End

2.2.10.4 Viewing Ethernet TrailsBy viewing Ethernet trails, you can know the trail details such as the route and occupiedresources.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The Ethernet trail must be created.

ProcedureStep 1 Choose Service > MSTP Trail > Manage Ethernet Trail from the Main Menu.


NOTE

l If you need to filter all trails on the U2000, click Filter All.l Based on the existing trails, to add trails that meet the new criteria, click Incremental Filter.l Based on the existing trails, to filter the trails again according to the new criteria, click Secondary

Filter.

Step 3 View the basic attributes of the Ethernet trail in the Ethernet trail list.

Step 4 If you want to view the route information of each NE on an EPL or EVPL trail, right-click a trailin the trail list and choose Details from the shortcut menu. The Details dialog box is displayed.Click the Route Information or Attributes tab. View the information and then click OK.

NOTE

The route information is automatically generated by the system. When configuring the Ethernet trail, theU2000 sets up the corresponding route on each NE according to the sink and source ports of the Ethernettrail and those of the trunk link trail.

Step 5 If you want to view the node and port information on an Ethernet trail, click a trail in the traillist and click the Node tab. In the node list, you can view the PORT and VCTRUNK ports usedby each NE. Click Port Attributes and the Ethernet Trail Port Attribute window is displayed.You can view the attributes of all ports used by the trail.

Step 6 If you want to view the trunk link trail used by an Ethernet trail, click the trail in the trail listand click the Trunk Link tab.

Step 7 If you want to view the VLAN filtering table of an EPLAN, click the trail in the trail list andclick the VLAN tab.

----End

2.2.10.5 Viewing the Server Trail of an Ethernet TrailThe server trail of an Ethernet trail is the trunk link. When you view the Ethernet trail, you canalso view its trunk link.




Issue 02 (2010-09-24)

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The Ethernet trail must be created.

Procedure

Step 1 Choose Service > MSTP Trail > Manage Ethernet Trail from the Main Menu.


NOTE




Step 3 Right-click a trail in the Ethernet trail list and choose Browse Relevant Server Trails from theshortcut menu. The Trunk Link Management interface is displayed, and shows the trunk linkthat the Ethernet trail uses.

NOTE

To go back from the trunk link to the Ethernet trail, right-click the trunk link and choose Browse clienttrail from the shortcut menu.

----End

2.2.10.6 Analyzing the Ethernet Trail Fault

You can query the status of an Ethernet trail.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The Ethernet trail must be created and activated.l Unterminated EPL trails are not supported.

Procedure


Step 2 In the filter dialog box, specify the filter criteria. The desired trails are displayed in the trail list.

NOTE

l To filter all trails on the U2000, click Filter All.



Step 3 In the list, select an Ethernet trail, right-click, and choose Analyse Trail Status from the shortcutmenu.



2-149

Step 4 In the displayed window, view Trail Status.

----End

2.2.10.7 Viewing the Connectivity of Ethernet Services NetworkwideThe U2000 periodically checks the connectivity of the trails that receive alarm notifications anddisplays the result. You can learn about the connectivity of services networkwide by viewingthe check result and thus adopt different handling policies. For example, the alarm that causesservice interruption is handled with priority.


ContextIn the case of the trails that reports the alarms, certain services of the trails are interrupted whileother services of the trails are not interrupted. The services that are interrupted cannot beidentified when you view alarms. You can only handle those alarms one by one. The alarm thatcauses service interruption, however, is not handled in time.

After the service interruption is detected, the U2000 automatically generates a service-levelalarm that is displayed in the Browse Current Alarm window.

Procedure

Step 1 Choose Fault > Service Monitoring > Real-Time Faulty MSTP Ethernet TrailManagement from the Main Menu.


Step 3 View Connection Status. The connectivity of the service is refreshed in real time.

----End

2.2.11 Maintaining Ethernet TrailsThis section describes how to maintain Ethernet trails.

2.2.11.1 Adjusting the Ethernet Trail BandwidthBy adjusting the bandwidth of a trunk link, you can adjust the bandwidth of the Ethernet trailthat the trunk link carries.

2.2.11.2 Activating or Deactivating Ethernet ServicesTo change the state of an Ethernet service from active to inactive state, you need to deactivatethe Ethernet service. Oppositely, to change an Ethernet service from the inactive to the activestate, you need to activate the trail.

2.2.11.1 Adjusting the Ethernet Trail BandwidthBy adjusting the bandwidth of a trunk link, you can adjust the bandwidth of the Ethernet trailthat the trunk link carries.




Issue 02 (2010-09-24)


l The trunk link must be created.

l The LCAS function of the trunk link must be enabled.

ContextAfter Ethernet services run for a period, a larger transmission bandwidth is required because ofan increase of traffics. A simple and reliable way for the expansion is to add path members tothe trunk link that carries the Ethernet trail. This operation does not interrupt existing servicesor does not require any changes to the source and sink ports of the Ethernet trail. On the otherhand, if the traffic load is overestimated when Ethernet services are initially provided, you candelete extra path members to avoid wasting bandwidth and save costs.

Procedure


Step 2 In the Set Trunk Link Browse Filter Criteria dialog box displayed, select the filter criteria.The desired trails are displayed in the trail list.

NOTE




Step 3 Select the trunk link from the list.

Step 4 To increase the bandwidth of the trunk link, click the Channel Member tab. Click Add and theAdd Channel Member dialog box is displayed. Select an appropriate channel member and clickOK.

NOTE

l There must be server trails available when you need to increase the trunk link bandwidth.

l The channel member to be added must have the same rate as the original ones.

Step 5 To reduce the bandwidth of the trunk link, click the Channel Member tab. Select an appropriatechannel member and click Delete.

----End

2.2.11.2 Activating or Deactivating Ethernet Services

To change the state of an Ethernet service from active to inactive state, you need to deactivatethe Ethernet service. Oppositely, to change an Ethernet service from the inactive to the activestate, you need to activate the trail.




2-151

ContextIf you activate the inactive Ethernet service again, the attributes of the service over the trail areconsistent with those before the activation.

CAUTIONDeactivating Ethernet services may interrupt services. Exercise caution when you perform thisoperation.

Procedure



NOTE

l Filter All refreshes and displays all trails that meet the filter criteria.

l Secondary Filter performs filtering on the trails that are already displayed according to the filtercriteria.

l Incremental Filter does not refresh the trail information that is already displayed. This functiondisplays the updated filter result below the existing trail information.

Step 3 Right-click the Ethernet service that you want to activate or deactivate and choose Activate orDeactivate from the shortcut menu. In the Confirm dialog boxes, click OK.

NOTE

During the deactivation, the Reconfirm dialog box is displayed. Click OK.


----End

2.2.12 Deleting Ethernet ServicesYou can delete the services that you do not need.

ContextEthernet services must be deleted in the following order:

2.2.12.1 Deleting Ethernet TrailsOnly when the Ethernet trail is deleted, the trunk link or SDH trail that carries the Ethernet trailcan be deleted.

2.2.12.2 Deleting Trunk LinksYou can delete trunk links.

2.2.12.1 Deleting Ethernet TrailsOnly when the Ethernet trail is deleted, the trunk link or SDH trail that carries the Ethernet trailcan be deleted.




Issue 02 (2010-09-24)


l The Ethernet trail to be deleted must be in the inactive state.

Procedure


Step 2 In the Set Trail Browse Filter Criteria dialog box displayed, select the filter criteria. Thedesired trails are displayed in the trail list.

NOTE




Step 3 Right-click the Ethernet trail that you want to delete and select Delete from the shortcut menu.The Confirm dialog box is displayed.

Step 4 Click OK and the Reconfirm dialog box is displayed.

Step 5 Click OK and the Operation Result dialog box is displayed.

Step 6 Click Close.

----End

2.2.12.2 Deleting Trunk Links

You can delete trunk links.


l The trunk link to be deleted must not carry any Ethernet trail.

l The trunk link to be deleted must be in the inactive state.

Context

If the trunk link you want to delete is already used for an Ethernet trail, you need to delete theEthernet trail first. For details, refer to Deleting Ethernet Trails.

Procedure


Step 2 In the Set Trail Browse Filter Criteria dialog box displayed, select the filter criteria. Thedesired trails are displayed in the trail list.



2-153

NOTE

l If you need to filter all trails on the U2000, click Filter All.l Based on the existing trails, to add trails that meet the new criteria, click Incremental Filter.l Based on the existing trails, to filter the trails again according to the new criteria, click Secondary

Filter.

Step 3 Select one or more trunk link trails that you want to delete, right-click and choose Delete fromthe shortcut menu. The Delete Trunk Link dialog box is displayed.

NOTE

l The server trail refers to an SDH trail used by the trunk link.l To delete the server trail of a trunk link, ensure that the server trail is in the inactive state.

Step 4 Click Yes, and the Confirm dialog box is displayed.

Step 5 Click OK, and the Operation Result dialog box is displayed.

Step 6 Click Close.

----End

2.3 Managing Alarms of an SDH TrailBy using the end-to-end trail management function of the U2000, you can manage alarmsgenerated on SDH trails at the network layer.

2.3.1 Viewing Current Alarms of an SDH TrailBy viewing the current alarms of an SDH trail, you can know the running status of the servicescarried on this trail. This helps during the network maintenance when you need to update thealarm information and take proper measures on time. When you view the current alarms of anSDH trail, you can perform other operations for these alarms at the same time. For example,synchronize, refresh, check, acknowledge and filter alarms.

2.3.2 Viewing History Alarms of an SDH TrailBy viewing history alarms of an SDH trail, you can learn history faults of the trail for referenceof operation and maintenance.

2.3.3 Setting Alarm Reversion for an SDH TrailDuring a new deployment, certain alarms that are reasonable but meaningless occur. Forexample, when you configure an SDH trail but not connect cables, the corresponding LOS alarmis generated. After the alarm reversion is set, the alarm is not displayed. This does not affect thenetwork monitoring that is performed by maintainers.

2.3.4 Inserting an Alarm on an SDH TrailIn the case of an SDH trail of VC4 level, during maintenance, you can manually insert an MS-AIS or MS-RDI alarm at the source end of the trail. If the sink end of the trail can correctlyreceive the alarm, it indicates that the trail works normally.

2.3.5 Managing Networkwide SDH Alarm Trails in Real TimeThe U2000 can manage the networkwide SDH alarm trails in real time. It manages all the SDHtrails that have current alarms. If an alarm ends, the related trail is automatically removed fromthe user interface.

2.3.6 Analyzing SDH alarm correlationAfter a fault occurs, the NE may report a lot of alarms. By analyzing the alarm correlation, youcan quickly locate the fault to the root alarm.




Issue 02 (2010-09-24)

2.3.7 Browsing Relevant WDM TrailsOn an SDH-WDM hybrid network, an SDH trail may be associated with other WDM trails. Bybrowsing relevant WDM trails, you can quickly query the associated WDM trails.

2.3.1 Viewing Current Alarms of an SDH TrailBy viewing the current alarms of an SDH trail, you can know the running status of the servicescarried on this trail. This helps during the network maintenance when you need to update thealarm information and take proper measures on time. When you view the current alarms of anSDH trail, you can perform other operations for these alarms at the same time. For example,synchronize, refresh, check, acknowledge and filter alarms.

Prerequisitel To view the alarms, You must be an NM user with "network monitor" authority or

higher. To acknowledge, check, synchronize and delete alarms, You must be an NM userwith "network operator" authority or higher.

l The SDH trail must be created.

Procedure

Step 1 Choose Service > SDH Trail > Manage SDH Trail from the Main Menu.TIP

Right-click the trail on the Main Topology and choose Browse Current Alarm.

Step 2 In the Set Trail Browse Filter Criteria dialog box displayed, select or enter parameters and setfilter criteria. Click Filter All.

NOTE




Step 3 Optional: Select a trail on which there are alarms. Then, right-click in the Transmission MediaLayer Route window and then choose Display Alarm. If the NEs have alarms, each of the NEicons is indicated with a specific alarm color. When you hold the cursor on any one of the NEicons, alarm information of the NE is displayed.

Step 4 Select one or more trails. Click the Alarm and select Current Alarm.

NOTE

Click an alarm. The details of the alarm and the recommended handling are displayed in the pane below.

Step 5 Optional: To display the latest alarms, check the Display latest alarms check box.

Step 6 Optional: To check the alarms, select one or more alarms. Right-click alarms and choose CheckAlarms.

NOTE

When you check the alarm, you are comparing one or more uncleared alarms on the U2000 with those onthe NE. If the alarm exists as a current alarm in the NE, it means that the alarm information remainsunchanged on the U2000. If the alarm does not exist in the NE, the alarm is cleared on the U2000.

Step 7 Optional: To acknowledge the alarms, select one or more alarms and click Acknowledge. Inthe Confirm dialog box displayed, click Yes.



2-155

NOTE

Acknowledged and cleared alarms automatically change to history alarms.

Step 8 Optional: To clear the alarms, select one or more alarms and click Clear. In the Confirm dialogbox displayed, click Yes.

NOTE

l If you select the alarm that is in the Unacknowledged & Uncleared state, click the button to changethe status to Unacknowledged & Cleared.

l you select the alarm that is in the Acknowledged & Uncleared state, click the button to move thealarm to the alarm log database.

Step 9 Optional: To view the trails, customers, and protection subnets that are affected by an alarm,you can select one alarm, right-click, and choose the required menu item, for example,Protection Subnet.

----End

2.3.2 Viewing History Alarms of an SDH TrailBy viewing history alarms of an SDH trail, you can learn history faults of the trail for referenceof operation and maintenance.



Procedure



NOTE




Step 3 Select a trail. Click Alarm and choose History Alarm.

Step 4 In the History Alarms-[Custom] window, view history alarms of the specified SDH trail.

----End

2.3.3 Setting Alarm Reversion for an SDH TrailDuring a new deployment, certain alarms that are reasonable but meaningless occur. Forexample, when you configure an SDH trail but not connect cables, the corresponding LOS alarmis generated. After the alarm reversion is set, the alarm is not displayed. This does not affect thenetwork monitoring that is performed by maintainers.




Issue 02 (2010-09-24)

Prerequisitel You must be an NM user with "network operator" authority or higher.l The trail must be activated.l Reversion Mode of the NE where the alarm is generated must be set to Automatic

Reversion or Manual Reversion.

Context

If you set alarm reversion for a trail, all alarms of this trail which support the function are reverted.You cannot set alarm reversion for a single alarm of the trail. Currently, you can set the alarmreversion for the following alarms: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, andDDN_ALOS.

Procedure



NOTE




Step 3 Select one or more trails, click Alarm and select Alarm Reversion from the drop-down list.

NOTE

Alarm reversion is not applicable to the VC4 server trail.

Step 4 In the Alarm Reversion dialog box displayed, set Reversion Status of the trail to Enabled.


----End

2.3.4 Inserting an Alarm on an SDH TrailIn the case of an SDH trail of VC4 level, during maintenance, you can manually insert an MS-AIS or MS-RDI alarm at the source end of the trail. If the sink end of the trail can correctlyreceive the alarm, it indicates that the trail works normally.


Procedure





2-157

NOTE




Step 3 Select a VC4 trail or VC4 server trail. Click Maintenance and choose Alarm Insertion fromthe drop-down menu.

Step 4 In the Alarm Insertion dialog box displayed, set the value of AIS Alarm Insertion or RDIAlarm Insertion to Insert.


----End

2.3.5 Managing Networkwide SDH Alarm Trails in Real TimeThe U2000 can manage the networkwide SDH alarm trails in real time. It manages all the SDHtrails that have current alarms. If an alarm ends, the related trail is automatically removed fromthe user interface.


Procedure

Step 1 Choose Fault > Service Monitoring > Real-Time Faulty SDH Trail Management from theMain Menu.


Step 3 Optional: To manage the trail alarms, select a trail, click Alarm, select Current Alarm orHistory Alarm from the drop-down list, and manage the alarms in the corresponding window.

Step 4 Optional: To manage the trail performance, select a trail, click Performance, select QueryPerformance or Performance Parameter from the drop-down list, and manage theperformance in the corresponding window.

----End

2.3.6 Analyzing SDH alarm correlationAfter a fault occurs, the NE may report a lot of alarms. By analyzing the alarm correlation, youcan quickly locate the fault to the root alarm.


Procedure

Step 1 Choose Fault > Correlation Analysis > Trail Alarm Correlation Rules from the Main Menu.




Issue 02 (2010-09-24)

Step 2 Click Create in the Alarm Correlation Rules dialog box, a rule of alarm correlation is created.

NOTE

You can also modify the existed alarm correlation rules.

Step 3 Set the Alarm1, Alarm2, Conditions and Action of the new rule.

NOTE

When you select Enable Automatic Correlation Analysis, dynamic analysis of the root alarm is adopted.

When you deselect Enable Automatic Correlation Analysis, static analysis of the root alarm is adopted.

Step 4 Click Apply.


Step 6 Click Close in the Alarm Correlation Rules dialog box.

Step 7 Choose Fault > Browse Alarm List from the Main Menu.

Step 8 In the Filter dialog box that is displayed, set the filtering criteria, and click OK.

Step 9 Optional: If use the dynamically analyzing trail root alarms, right-click a root alarm and choosecorrelative alarms from the shortcut menu to display the correlative alarms suppressed by thisroot alarm.

Step 10 Optional: If use the static analyzing trail root alarms, choose Fault > Correlation Analysis >Analyze Trail Alarm Correlation from the Main Menu.

1. Click OK in the Correlation Analysis for Current Alarm dialog box.

2. Click OK in the Confirm dialog box, the root alarm informations are displays in the BrowseRoot Alarm.

----End

2.3.7 Browsing Relevant WDM TrailsOn an SDH-WDM hybrid network, an SDH trail may be associated with other WDM trails. Bybrowsing relevant WDM trails, you can quickly query the associated WDM trails.


Procedure



NOTE






2-159

Step 3 Right-click the trail and choose Browse Relevant WDM Trail from the shortcut menu to viewthe WDM trails relevant to the trail.

----End

2.4 Managing the Performance of SDH TrailsYou can use the network layer function of the U2000 to perform end-to-end performancemanagement on SDH trails.

2.4.1 Viewing Current Performance Data of an SDH TrailTo know whether services in an SDH trail are normal, view the current performance data.

2.4.2 Viewing History Performance Data of an SDH TrailTo know whether services in an SDH trail are normal, view the history performance data.

2.4.3 Viewing UAT of SDH TrailsYou can view performance UAT of SDH trails to know the UAT events of the SDH trails.

2.4.4 Viewing Performance Threshold-Crossing Records of SDH TrailsYou can view performance threshold-crossing record of SDH trails to know the performancethreshold-crossing events of the SDH trails.

2.4.5 Setting Performance Monitoring Parameters of an SDH TrailPerformance monitoring keeps a detailed record of the performance of services over a trail,helping the maintenance engineer to monitor and analyze the states of services.

2.4.6 Setting SDH Trail Performance ThresholdIn this user interface, you can set performance thresholds based on a trail. Specifically, you canset the corresponding performance thresholds for the performance events and performance typeson the source and sink of a trail.

2.4.1 Viewing Current Performance Data of an SDH TrailTo know whether services in an SDH trail are normal, view the current performance data.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The SDH trail must be created.

Procedure


Step 2 In the Set Trail Browse Filter Criteria dialog box, set the filter criteria and click Filter All.

NOTE




Step 3 Select one or more trails. Click the Performance and select Query Performance.




Issue 02 (2010-09-24)

Step 4 Click the 15-Minute Current Performance or 24-Hour Current Performance tab and viewthe current performance of the trail.

Step 5 Optional: To browse the performance events on the NEs that the trail traverses, select theDisplay all monitored objects check box.

NOTE

If this check box is selected, the performance events of the source, sink, and intermediate nodes that a trailtraverse are displayed. If this check box is cleared, the performance events of only the source and sinknodes of a trail are displayed.

Step 6 Optional: Click Filter. In the Filter dialog box, set the filter criteria and click OK. The qualifiedperformance events are displayed.

----End

2.4.2 Viewing History Performance Data of an SDH TrailTo know whether services in an SDH trail are normal, view the history performance data.



Procedure



NOTE




Step 3 Select one or more trails. Click the Performance button and select Query Performance.

Step 4 Click the 15-Minute History Performance or 24-Hour History Performance tab and viewthe history performance of the trail.


NOTE



Step 7 Optional: Click Graph. In the displayed window, select Performance Event and Monitor

Object. Click and then click Show to view the graphic display.



2-161

NOTE

l By displaying data in a graph, you can clearly learn the performance change trend in a certain period.

l Applies to the performance events related to the optical power only.

----End

2.4.3 Viewing UAT of SDH TrailsYou can view performance UAT of SDH trails to know the UAT events of the SDH trails.


Procedure


Step 2 The Set Trail Browse Filter Criteria dialog box is displayed. Set the filter criteria and viewthe desired trails in the trail list.l If you need to filter all the trails, click Filter All.l If you need to add to the list more trails that match the requirement, click Incremental

Filter.l If you need to filter the trails in the list, click Secondary Filter.

Step 3 Select one or several trails, click Performance, choose Browse Performance.

Step 4 click UAT tab to view the UAT events of the SDH trails.


NOTE



----End

2.4.4 Viewing Performance Threshold-Crossing Records of SDHTrails

You can view performance threshold-crossing record of SDH trails to know the performancethreshold-crossing events of the SDH trails.





Issue 02 (2010-09-24)

Procedure


Step 2 The Set Trail Browse Filter Criteria dialog box is displayed. Set the filter criteria and viewthe desired trails in the trail list.l If you need to filter all the trails, click Filter All.l If you need to add to the list more trails that match the requirement, click Incremental

Filter.l If you need to filter the trails in the list, click Secondary Filter.

Step 3 Select one or several trails, click Performance, choose Browse Performance.

Step 4 Click performance threshold-crossing record tab to view the performance threshold-crossingevents of the SDH trails.


NOTE



----End

2.4.5 Setting Performance Monitoring Parameters of an SDH TrailPerformance monitoring keeps a detailed record of the performance of services over a trail,helping the maintenance engineer to monitor and analyze the states of services.


Procedure



NOTE




Step 3 Select a trail. Click Performance and choose Performance Parameter from the drop-downmenu.

Step 4 In the Performance Parameter dialog box displayed, select an object, and set the monitoringstatus and auto reporting status.



2-163


----End

2.4.6 Setting SDH Trail Performance ThresholdIn this user interface, you can set performance thresholds based on a trail. Specifically, you canset the corresponding performance thresholds for the performance events and performance typeson the source and sink of a trail.

Prerequisitel You must be an NM user with "network monitor" authority or higher.l The trail must be created.

Procedure


Step 2 In the Set Trail Browse Filter Criteria dialog box, set the filter criteria and click Filter All.NOTE




Step 3 Select one or more trails. Click Performance and choose Performance Threshold from thedrop-down menu.

Step 4 In the Performance Threshold window, double-click Threshold Value to change theperformance threshold value.

Step 5 Click Apply, in the Operation Result window, click Close.

Step 6 Click Cancel to exit the Performance Threshold window.

----End

2.5 Managing Ethernet Trail AlarmsYou can use the U2000 function of the end-to-end trail management to manage the alarmsgenerated on Ethernet trails at the network layer.

2.5.1 Viewing Current Alarms of a Trunk LinkBy viewing current alarms of a trunk link, you can query the running status of services that thecurrent trail carries. During the network maintenance, you need to update alarm information andproperly handle the alarms in time. When viewing the current alarms of the trunk link, you canalso synchronize, refresh, check, acknowledge and filter the alarms.

2.5.2 Viewing History Alarms of a Trunk LinkBy viewing history alarms of a specified trunk link, you can learn history faults of the trail forreference of operation and maintenance.

2.5.3 Viewing Current Alarms of an Ethernet Trail




Issue 02 (2010-09-24)

By viewing current alarms of an Ethernet trail, you can query the running status of services thatthe current trail carries. During the network maintenance, you need to update alarm informationand properly handle the alarms in time. When viewing the current alarms of the Ethernet trail,you can also synchronize, refresh, check, acknowledge and filter the alarms.

2.5.4 Viewing History Alarms of an Ethernet TrailBy viewing history alarms of an Ethernet trail, you can learn history faults of the trail forreference of the operation and maintenance.

2.5.5 Managing Networkwide ETH Alarm Trails in Real TimeThe U2000 can manage the networkwide ETH alarm trails in real time. It manages all the ETHtrails that have current alarms. If an alarm ends, the related trail is automatically removed fromthe user interface.

2.5.1 Viewing Current Alarms of a Trunk LinkBy viewing current alarms of a trunk link, you can query the running status of services that thecurrent trail carries. During the network maintenance, you need to update alarm information andproperly handle the alarms in time. When viewing the current alarms of the trunk link, you canalso synchronize, refresh, check, acknowledge and filter the alarms.

Prerequisitel The trunk link must be created.l To view alarms, You must be an NM user with "network monitor" authority or higher. To

acknowledge, check, synchronize and delete alarms, You must be an NM user with"network operator" authority or higher.

Procedure


Step 2 In the Set Trunk Link Browse Filter Criteria window, select or enter parameters and set filtercriteria. Click Filter All.

NOTE




Step 3 Select one or more trails. Click Alarm and select Current Alarm from the drop-down list. Thewindow that is displayed shows the current alarms of all severity levels.

Step 4 Optional: Select one or more alarms and choose Check from the shortcut menu to check theselected alarms.

NOTE

Checking alarms is to compare one or more uncleared alarms on the U2000 with those on the NE. If analarm exists as a current alarm on the NE, the alarm information remains unchanged on the U2000. If thealarm does not exist on the NE, the alarm is cleared on the U2000.

Step 5 Optional: Select an alarm. The detailed information and handling suggestions of the alarm aredisplayed in the panes below.



2-165

Step 6 Optional: Select one or more alarms and click Acknowledge. The Acknowledge Alarms dialogbox is displayed. Click Yes. The Ack User, Ack Time and Ack Status fields display thecorresponding values of the selected alarms.

NOTE

Acknowledged and cleared alarms change to history alarms automatically.

----End

2.5.2 Viewing History Alarms of a Trunk LinkBy viewing history alarms of a specified trunk link, you can learn history faults of the trail forreference of operation and maintenance.

Prerequisitel The trunk link must be created.

l You must be an NM user with "network monitor" authority or higher.

Procedure


Step 2 In the Set Trunk Link Browse Filter Criteria window, select or enter parameters and set filtercriteria. Click Filter All.

NOTE




Step 3 Select one or more trails. Click Alarm and select History Alarm from the drop-down list. Inthe window displayed, view the details of the history alarms of the specified trail.

----End

2.5.3 Viewing Current Alarms of an Ethernet TrailBy viewing current alarms of an Ethernet trail, you can query the running status of services thatthe current trail carries. During the network maintenance, you need to update alarm informationand properly handle the alarms in time. When viewing the current alarms of the Ethernet trail,you can also synchronize, refresh, check, acknowledge and filter the alarms.

Prerequisitel The Ethernet trail must be created.

l To view alarms, You must be an NM user with "network monitor" authority or higher. Toacknowledge, check, synchronize and delete alarms, You must be an NM user with"network operator" authority or higher.




Issue 02 (2010-09-24)

Procedure


Step 2 In the Set Trail Browse Filter Criteria window, select or enter parameters and set filter criteria.Click Filter All.

NOTE




Step 3 Select one or more trails. Click Alarm and select Current Alarm from the drop-down list. Thewindow that is displayed shows the current alarms of all severity levels.

Step 4 Optional: Select one or more alarms and choose Check from the shortcut menu to check theselected alarms.

NOTE

Checking alarms is to compare one or more uncleared alarms on the U2000 with those on the NE. If analarm exists as a current alarm on the NE, the alarm information remains unchanged on the U2000. If thealarm does not exist on the NE, the alarm is cleared on the U2000.

Step 5 Optional: Select an alarm. The detailed information and handling suggestions of the alarm aredisplayed in the panes below.

Step 6 Optional: Select one or more alarms and click Acknowledge. The Acknowledge Alarms dialogbox is displayed. Click Yes. The Ack User, Ack Time and Ack Status fields display thecorresponding values of the selected alarms.

NOTE

Acknowledged and cleared alarms change to history alarms automatically.

----End

2.5.4 Viewing History Alarms of an Ethernet TrailBy viewing history alarms of an Ethernet trail, you can learn history faults of the trail forreference of the operation and maintenance.

Prerequisitel The Ethernet trail must be created.

l You must be an NM user with "network monitor" authority or higher.

Procedure


Step 2 In the Set Trail Browse Filter Criteria window, select or enter parameters and set filter criteria.Click Filter All.



2-167

NOTE




Step 3 Select one or more trails. Click Alarm and select History Alarm from the drop-down list. Inthe window displayed, view the details of the history alarms of the specified trail.

----End

2.5.5 Managing Networkwide ETH Alarm Trails in Real TimeThe U2000 can manage the networkwide ETH alarm trails in real time. It manages all the ETHtrails that have current alarms. If an alarm ends, the related trail is automatically removed fromthe user interface.


Procedure

Step 1 Choose Fault > Service Monitoring > Real-Time Faulty MSTP Ethernet TrailManagement from the Main Menu.


Step 3 Optional: To manage the trail alarms, select a trail, click Alarm, select Current Alarm orHistory Alarm from the drop-down list, and manage the alarms in the corresponding window.

Step 4 Optional: To manage the trail performance, select a trail, click Performance, manage theperformance in the corresponding window.

----End

2.6 Browsing the Performance of an Ethernet TrailBy browsing the performance of the Ethernet trail, you can learn about the running status of theservices in the existing trail.


Procedure

Step 1 On the Main Menu, choose Service > MSTP Trail > Manage Ethernet Trail to display theSet Trail Browse Filter Criteria dialog box.

Step 2 Select the filter conditions in the dialog box, and then click Filter All.




Issue 02 (2010-09-24)

NOTE

l Click Filter All to refresh all the trails that meet the specified conditions.

l Click Secondary Filter to filter the displayed trails based on the filter conditions.

l Click Incremental Filter not to refresh the displayed trails. Instead, the new result is added to the end ofthe displayed trails.

Step 3 Select one or more trails. Click Performance, select Current Performance or HistoryPerformance from the drop-down list. For detailed operations, see chapter "PerformanceManagement".

----End



2-169

3 End-to-End RTN IP Management

About This Chapter

In the end-to-end configuration mode, you can quickly configure RTN IP services. The end-to-end configuration mode is also called the trail management function.

PrerequisiteThe trail management license must be provided.

3.1 Process of Configuring RTN IP ServicesThis topic describes the process of configuring RTN IP services in terms of network deployment,service discovery, service deployment, and service assurance.

3.2 Automatically Searching RTN IP ServicesThis topic describes how to automatically search IP services. With this function, you can recoverthe services existing on the current network to the end to end management module of the NMSfor monitoring. In this manner, you can ensure the normal running of these services.

3.3 Managing TunnelBy using the tunnel technology, you can create private data transmission channels on a PSNnetwork to transparently transmit packets.

3.4 Configuring a Service TemplateBy using a service template, you can create services more quickly and easily. You can customizea service template according to actual O&M requirements.

3.5 Viewing a Service ResourceThis topic describes how to view the usage of a service resource.

3.6 Managing PWE3 ServicesThis section describes how to configure PWE3 services.

3.7 Modifying ConfigurationsThis topic describes how to modify service configurations, which includes modifying anddeleting service configurations.

iManager U2000 Unified Network Management SystemOperation Guide for RTN End-to-End Management 3 End-to-End RTN IP Management


3-1

3.1 Process of Configuring RTN IP ServicesThis topic describes the process of configuring RTN IP services in terms of network deployment,service discovery, service deployment, and service assurance.

Figure 3-1 shows the process of configuring RTN IP services.

Figure 3-1 Process of configuring RTN IP services

Network deployment Service deployment

Add equipment to the NMS

Configure basic routes

Configure control plane

Configure tunnels

Service assurance

Discover single services

Create a service through a template

Create a service with defined parameters

Monitor alarms in centralized mode

Service discovery

Discover composite services

Discover tunnels

Monitor performance services

Service m

onitoring

View service resources

Predeploym

ent

Deploy the service Monitor service alarms

Locate faults with the test and check

Fault location

View the service topology

Optional

Mandatory

Upload/Synchronize data

Configure interface

l Network deployment: is the prerequisite for the service deployment and includes addingequipment to the NMS, upload/synchronize data, and configuring basic routes, configuringcontrol plane, and tunnels.

l Service discovery: discovers the existing services on the NMS for unified management andincludes the discovery of tunnels, single services, and composite services.

l Service deployment

– Viewing service resources: Before deployment services, you can view the serviceresources to check the available service resources.

– Predeploying services: Predeploying services refers to creating services on the NMS.After services are predeployed, the configuration data of the services are not deployedto equipment. To create services, you can either manually enter the parameters of theservices or use a template to create the services in batches.

– Service deployment: deploys the configuration data of services to equipment.

l Service assurance: includes service monitoring and fault location. Service monitoringincludes service alarm monitoring and service performance monitoring. By monitoringservice alarms, you can view affected services, and then locate the failure point throughthe test diagnosis tool.

3 End-to-End RTN IP ManagementiManager U2000 Unified Network Management System



Issue 02 (2010-09-24)

– Service monitoring: monitors the alarms and performance of services and views theservice topology. The service topology provides rich service operation accesses.According to the topology color, you can discover alarms according to the topologycolor and view the related alarms in the topology view.

– Fault location: By monitoring service alarms, you can view affected services, and thenlocate the failure point through the test and check.

3.2 Automatically Searching RTN IP ServicesThis topic describes how to automatically search IP services. With this function, you can recoverthe services existing on the current network to the end to end management module of the NMSfor monitoring. In this manner, you can ensure the normal running of these services.

PrerequisiteData synchronization must be complete on the related equipment.

Procedure

Step 1 Choose Service > Search for IP Service from the main menu.

Step 2 On the Discovery Policy tab page, set the discovery policy.1. Specify the equipment range for automatically searching IP services.

l Click the All option button to discover all the NEs on the entire network.l Click the Select NE option button, and then click Add. In the dialog box that is

displayed, select one or more NEs, and then click OK to discover the specified NEs.2. In the Discover Service navigation tree, select the check box to the left of the related service

to specify the type of the services to be searched.3. On the lower-right part, click each service tab to configure the customer policy and

discovery policy.Customer association policies are classified into the following types:l Set Customer: The searched services are automatically associated with the specified

customer.l Do Not Set Customer: The automatically searched services are not associated with any

customer.4. After the configuration, click Start.

Step 3 Click the Discovery Result tab. A progress bar is displayed indicating the progress ofautomatically discovering services.You can view the automatically searched services on the Add Service, Modify Service, andDiscrete Service tab pages, as shown in the following figure. After selecting a record andclicking Jump Service, you can access the service management user interface for this service.



3-3

----End

3.3 Managing TunnelBy using the tunnel technology, you can create private data transmission channels on a PSNnetwork to transparently transmit packets.

3.3.1 Introduction to the TunnelDifferent tunnel technologies are used in different scenarios and use different protocols totransparently transmit data packets.

3.3.2 Tunnel Configuration FlowThis section describes the operation tasks for configuring the Tunnel, and relations among thesetasks. When configuring and managing the Tunnel, follow the configuration flow.

3.3.3 Configuring a TunnelThis topic describes how to configure a tunnel, such as creating a tunnel, deploying a tunnel,viewing discrete tunnels, and deleting a tunnel.

3.3.4 Monitoring a TunnelThis topic describes how to monitor a tunnel to facilitate tunnel services management.

3.3.5 Configuration Example (Static CR Tunnel)This topic describes a networking diagram and the corresponding example of configuring a staticCR tunnel on the network.

3.3.6 Configuration Example (RSVP TE Tunnel)This topic describes a networking diagram and the corresponding example of configuring a staticRSVP TE tunnel on the network.




Issue 02 (2010-09-24)

3.3.1 Introduction to the TunnelDifferent tunnel technologies are used in different scenarios and use different protocols totransparently transmit data packets.

3.3.1.1 Introduction to the TunnelOptiX equipment supports the MPLS tunnel, which is a tunneling technology using the MPLS-protocol-based encapsulation, and the IP tunnel, which is a tunneling technology using the IP-protocol-based encapsulation.

3.3.1.2 Standards and Protocols Compliance of the TunnelThis topic describes the standards Compliance and the two protocols that the tunnelingtechnology uses. They are the MPLS-LDP protocol and the MPLS-RSVP protocol.

3.3.1.3 Basic Concepts of the TunnelMulti-protocol label switching (MPLS) is a tunnel technology and enables a routing andswitching platform that integrates the switching and forwarding technologies of labels andnetwork-layer routing technologies. In the MPLS architecture, the control plane isconnectionless and uses the powerful and flexible routing function of the IP network to meet thenetwork requirements of new application; the data plane is connection-oriented and uses shortand fixed-length labels to encapsulate packets for implementation of fast forwarding. This topicdescribes basic concepts of the tunnel.

3.3.1.4 Working PrinciplesThis topic describes how to create a tunnel and the working principles of a tunnel.

3.3.1.5 Tunnel Protection GroupAutomatic protection switching (APS) of the MPLS tunnel is a network protection mechanism.The protection MPLS tunnel protects the services transmitted in the working MPLS tunnel.When the working MPLS tunnel is faulty, the services are switched to the protection MPLStunnel. In this way, the services transmitted in the working tunnel are protected. OptiX RTNequipment supports the 1+1 and 1:1 APS protection of the MPLS tunnel.

3.3.1.6 Application of the TunnelAs the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmitservice packets. The MPLS Tunnel can carry various services, such as CES services, ATM/IMAservices, Ethernet service and protocol packets. The MPLS Tunnel is mainly used for transparenttransmission of point-to-point data service packets.

3.3.1.1 Introduction to the TunnelOptiX equipment supports the MPLS tunnel, which is a tunneling technology using the MPLS-protocol-based encapsulation, and the IP tunnel, which is a tunneling technology using the IP-protocol-based encapsulation.

MPLS TunnelAs a transmission technology, the multi-protocol label switching (MPLS) can realize transparenttransmission of data packets among users. The MPLS tunnel is the tunnel defined in the MPLSprotocol. Independent from the service, the MPLS tunnel realizes the end-to-end transmissionand carries the PWs related to the service.

Figure 3-2 shows how the MPLS tunnel is used as the service transmission channel.



3-5

Figure 3-2 MPLS tunnel on the MPLS network

IMA E1

FE

ATM STM-1MPLS tunnel

Ingress node Transit node Egress node IMA E1

FE

ATM STM-1

PW

The MPLS tunnel only provides an end-to-end channel, and does not care which service isencapsulated in the PW it carries. Data packets are first encapsulated in the PW, which is stuckwith an MPLS label and sent to the MPLS tunnel for transmission. At the sink end, data packetsare recovered and retain the original service features. In the tunnel, the intermediate nodes arecalled Transit nodes. Hence, a tunnel contains the Ingress node, Egress node and Transit nodes.

Based on signaling types, MPLS tunnels can be classified into three types, that is, the static CRtunnel, RSVP TE tunnel, and LDP tunnel. These three types of tunnels are different and thedetails are as follows:l Static CR tunnel: You need to specify the nodes that a static CR tunnel traverses. In addition,

you can also specify the bandwidth and QoS of the tunnel.l RSVP TE tunnel: You need to specify only the ingress and egress nodes for an RSVP TE

tunnel. The MPLS protocol automatically calculates a route for the tunnel. In addition, youcan specify constraint nodes to plan a specific route for the tunnel. You can configure FRRprotection and the QoS function for an RSVP TE tunnel. Therefore, an RSVP tunnel ismore flexible and safer than a static CR tunnel.

l LDP: You only need to specify the ingress and egress nodes for an LDP tunnel. Then, theLDP protocol sets up a route for the tunnel. An LDP tunnel functions on the network thatsupports the MPLS domain and thus is more flexible.

IP TunnelIf ATM or CES emulation service that travels through an IP network is required, the RTNequipment can use the IP tunnel to carry the service. Figure 3-3 shows the protocol stack modelof the ATM service. In the case of the IP tunnel, the situation is similar to that where "IP header"replaces the MPLS external label (MPLS tunnel label) to establish a tunnel in the IP network.An ATM emulation service can be provided between NE A and NE B, even though the IPnetwork between NE A and NE B does not support the MPLS.




Issue 02 (2010-09-24)

Figure 3-3 ATM PWE3 over IP tunnel

3.3.1.2 Standards and Protocols Compliance of the TunnelThis topic describes the standards Compliance and the two protocols that the tunnelingtechnology uses. They are the MPLS-LDP protocol and the MPLS-RSVP protocol.

MPLS-RSVP ProtocolMulti-protocol label switch resource reservation protocol (MPLS-RSVP) supports thedistribution of MPLS labels. In addition, when transmitting the label binding message, it carriesthe resource reservation information, used as a signaling protocol to create, delete or modify thetunnel in the MPLS network.

Basic Concepts of the MPLS-RSVP

The MPLS-RSVP is a notification mechanism of the resource reservation in the network, whichrealizes the bandwidth reservation on the control plane. As a label distribution protocol, it isused to set up the LSP in the MPLS network.

For details of the MPLS-RSVP extension, refer to RFC3209.

Resource Reservation Style

The LSP set up by using the MPLS-RSVP is of a certain reservation style. When the RSVPsession is set up, the receive end determines which reservation style to be used, and thusdetermines which LSP to be used.l Fixed-filter (FF) style: When this style is used, resources are reserved for each transmit end

individually. Thus, transmit ends in the same session cannot share the resources with eachother.

l Shared-explicit (SE) style: When this style is used, resources are reserved for all transmitends in the same session. Thus, transmit ends can share the resources.

NOTE

Currently, OptiX equipment supports only the SE resource reservation style.

MPLS-RSVP Message Type

The MPLS-RSVP uses the following message types:l Path message: The transmit end sends this type of message in the transmission direction of

data packets. In addition, the path state is saved on all the nodes along the trail.



3-7

l Resv message: The receive end sends this type of message in the reverse transmissiondirection of data packets. In addition, the resource reservation is requested, and thereservation state is created and maintained on all the nodes along the trail.

Parameters of the MPLS-RSVP State Timer

The parameters of the MPLS-RSVP state timer include the refreshing period of the Path or Resvmessage, multiple of the path state block (PSB) timeout and reservation state block (RSB)timeout.

In the case of the creation of the LSP, the transmit end adds the LABEL_REQUEST object tothe Path message. When the receive end receives the Path message with the LABEL_REQUESTobject, it distributes one label and adds the label to the LABEL object of the Resv message.

The LABEL_REQUEST object is saved in the PSB of the upstream node, and the LABEL objectis saved in the RSB of the downstream node. When the message indicating that the number ofmessage refreshing times exceeds the multiple of the PSB or RSB timeout is not continuouslyreceived, the corresponding state in the PSB or RSB is deleted.

Assume that there is a resource reservation request, which does not pass the access control onsome nodes. In some cases, this request is not supposed to be immediately deleted, but it cannotstop other requests from using its reserved resources. In this case, the node enters the blockadestate, and the blockade state block (BSB) is generated on the node of the downstream. When themessage indicating that the number of the message refreshing times exceeds the multiple of thePSB or RSB timeout is continuously received, the corresponding state in the BSB is deleted.

MPLS-LDP ProtocolThe multi-protocol label switch label distribution protocol (MPLS-LDP) is used for the labelswitched routers (LSR) to distribute labels in the network.

MPLS-LDP Peer Entities

The MPLS-LDP peer entities refer to two NEs, where LDP session exists, use the MPLS-LDPto exchange labels mapping relation.

MPLS-LDP Session

The MPLS-LDP session is used to exchange label mapping and releasing messages betweendifferent equipment. The MPLS-LDP session consists the following two types:l Local MPLS-LDP session, in which the two NEs used to set up the session is directly

connected.l Remote MPLS-LDP session, in which the two NEs used to set up the session is not directly

connected.

MPLS-LDP Message Types

The MPLS-LDP protocol mainly uses the following four types of messages:l Discovery message, which is used to notify and maintain the existence of the equipment

in the network.l Session message, which is used to set up, maintain and end the session between MPLS-

LDP peer entities.l Advertisement message, which is used to create, change and delete the label mapping.l Notification message, which is used to provide the constructive message and error

notification.




Issue 02 (2010-09-24)

Standards and Protocols ComplianceThe tunneling technology is mainly compliant with the following:l ITU-T G.8110 MPLS layer network architecturel ITU-T G.8110.1 Application of MPLS in the transport networkl ITU-T G.8121 Characteristics of transport MPLS equipment functional blocksl RFC 3031 MPLS architecturel RFC 3032 MPLS label stack encoding

3.3.1.3 Basic Concepts of the TunnelMulti-protocol label switching (MPLS) is a tunnel technology and enables a routing andswitching platform that integrates the switching and forwarding technologies of labels andnetwork-layer routing technologies. In the MPLS architecture, the control plane isconnectionless and uses the powerful and flexible routing function of the IP network to meet thenetwork requirements of new application; the data plane is connection-oriented and uses shortand fixed-length labels to encapsulate packets for implementation of fast forwarding. This topicdescribes basic concepts of the tunnel.

FEC

Forwarding equivalence class (FEC) is a class of packets that are forwarded in the same way onan MPLS network.

Label

Label is a short and length-fixed identifier. The label identifies the FEC that a packet belongsto and functions only in the MPLS domain. One FEC may involve multiple labels but one labelcan only indicate one FEC.

LDP

Label distribution protocol (LDP) is the control protocol for MPLS. Similar to the signalingprotocol of a traditional network, the LDP protocol is responsible for creation and maintenanceof LSPs and PWs, FEC classification, and label distribution. MPLS can use the following labeldistribution protocols:l Protocols exclusive for label distribution, such as LDP.l Existing protocols extended to support label distribution, such as RSVP-TE.

LSP

On an MPLS network, the trail that an FEC traverses is a label switched path (LSP), that is, aunidirectional trail from the ingress to egress. LSPs are classified into static LSPs and dynamicLSPs. Static LSPs should be manually configured and dynamic LSPs are dynamically generatedby the LDP protocol.

LSR

Label switching router (LSR) is the basic element in an MPLS domain. All LSRs support theMPLS protocol. Each node on an LSP is an LSR. An edge LSR (LER) is at the edge of an MPLSdomain and connects to other user networks. The core LSR is in the center of an MPLS domain.Packets travel along an LSP and enter an MPLS domain. The incoming LER is the ingress, theoutgoing LER is the egress, and the intermediate nodes are the transit nodes.

An LSR consists of the control unit and forward unit.



3-9

l The control unit is responsible for label distribution, route selection, setup of label forwardtables, and setup and removal of LSPs.

l The forward unit forwards received packets according to the label forward tables.

NHLFE

Next hop label forwarding entry (NHLFE) describes the operations that an LSR performs onlabels, including push, swap, and pop.

3.3.1.4 Working PrinciplesThis topic describes how to create a tunnel and the working principles of a tunnel.

Process of Creating a TunnelFigure 3-4 shows the process of creating a tunnel. Meanwhile, the working principles of a tunnelare described.

Figure 3-4 Process of creating a tunnel

Ingress node

Label request packet

Label mapping packet

Transit node Egress node

Set up the forward entry

Allocate the ingress label and set up the forward entry

Allocate the ingress label and set up the forward entry

Label request packet

Label mapping packet

A tunnel is created as follows:

1. The ingress node uses the encapsulation protocol to calculates a path to the egress nodeand transmits a label request packet to the egress node in the direction of the path.

2. After receiving the label request packets, the transit node forwards them to the egress node.3. After receiving the label request packet, the egress node allocates an ingress label for the

tunnel, sets up a forward entry, and transmits a label mapping packet to the ingress node.4. After receiving the label mapping packet, the transit node allocates an ingress label for the

tunnel, sets up a forward entry, and forwards the label mapping packet to the ingress node.5. After receiving the label mapping packet, the ingress node sets up a forward entry. The

tunnel is created successfully between the ingress node and egress node.

Working Process of a TunnelFigure 3-5 shows the working process of a tunnel.




Issue 02 (2010-09-24)

Figure 3-5 Working process of a tunnel

IMA E1

FE

ATM STM-1MPLS Tunnel

Ingress node Transit node Egress

nodeIMA E1

FE

ATM STM-1

PW

Packet FEC

Push Swap Pop

Tunnel

At each LSR, the LDP protocol and traditional routing protocol work together to set up the routetable and label mapping table for the FEC as required. Each LSR node receives packets andperforms the NHLFE operations for the packets:l Push: The ingress node receives packets and checks for the FEC that the packets belong

to. Then, the ingress node adds labels on the packets and transmits the encapsulated MPLSpackets to the next hop through the egress interface.

l Swap: A transit node uses the forward unit to forward the packets only according to packetlabels and the label forward table. A transit node does not perform any Layer 3 operationfor the packets.

l Pop: The egress node stripes the labels from the packets and forwards the packets.

3.3.1.5 Tunnel Protection GroupAutomatic protection switching (APS) of the MPLS tunnel is a network protection mechanism.The protection MPLS tunnel protects the services transmitted in the working MPLS tunnel.When the working MPLS tunnel is faulty, the services are switched to the protection MPLStunnel. In this way, the services transmitted in the working tunnel are protected. OptiX RTNequipment supports the 1+1 and 1:1 APS protection of the MPLS tunnel.

Basic InformationAPS (Automatic Protection Switching)

The automatic protection switching (APS) protocol is used to coordinate actions of the sourceand the sink in the case of bidirectional protection switching. By the APS protocol, the sourceand the sink cooperate with each other to perform functions such as protection switching,switching delay, and WTR function.

According to ITU-T Y.1720, the source and the sink both need to select channels in the APS.In this case, the APS protocol is required for coordination. In the case of bidirectional protectionswitching, the APS protocol needs to be used regardless of the revertive mode.

The APS protocol is always transmitted through the protection tunnel. Then, the equipment ateither end knows that the tunnel from which the APS protocol is received is the protection tunnelof the opposite end and thus to determine whether the configuration about the working tunneland the protection tunnel is consistent at the two ends.

Switching Mode



3-11

MPLS APS provides two switching modes, that is, single-ended switching and dual-endedswitching.

In the case of single-ended switching, when one end detects a fault, it only performs switchingon the local end and does not instruct the opposite end to perform any switching.

In the case of dual-ended switching, when one end detects a fault, it performs switching on thelocal end and also instructs the opposite end to perform switching.

Single-ended switching does not require the APS protocol for negotiation and it features rapidand stable switching.

Dual-ended switching ensures that the services are transmitted in a consistent channel, whichfacilitates service management.

Revertive Mode

The MPLS APS function supports two revertive modes, that is, revertive mode and non-revertivemode.

In the non-revertive mode, services are not switched from the protection tunnel to the workingtunnel even the working tunnel is restored to the normal state.

In the revertive mode, services are switched from the protection tunnel to the original workingtunnel if the working tunnel is restored to the normal state within the WTR time.

WTR Time

The WTR time refers to the period from the time when the original working tunnel is restoredto the time when the services are switched from the protection tunnel to the original workingtunnel.

In certain scenarios, the state of the working tunnel is unstable. In this case, setting the WTRtime can prevent frequent switching of services between the working tunnel and the protectiontunnel.

By default, the WTR time of the equipment is 5 minutes.

Hold-off Time

The hold-off time refers to the period from the time when the equipment detects a fault to thetime when the switching operation is performed.

When the equipment is configured with the MPLS APS protection and other protection, settingthe hold-off time can ensure that other protection switching operations are performed first.

By default, the hold-off time of the equipment is 0s.

Application of the Tunnel Protection

The MPLS tunnels of the same type are created in one tunnel protection group. In this way, 1:1protection is provided to these MPLS tunnels. If the working MPLS tunnel fails, the Tunnelprotection group ensures that services can still normally run.

By using the U2000, the user can configure 1:1 protection for MPLS tunnels that carry importantservices.

Figure 3-6 shows the protection principle for unicast tunnels.




Issue 02 (2010-09-24)

Figure 3-6 Principles of the tunnel protection

CE

CE

Ingress node

Egress node

Working tunnel

Protection tunnel

Configuration of source protection group

Configuration of sink protection group

3.3.1.6 Application of the TunnelAs the carrier of PWs in the network, the MPLS Tunnel provides the service tunnel to transmitservice packets. The MPLS Tunnel can carry various services, such as CES services, ATM/IMAservices, Ethernet service and protocol packets. The MPLS Tunnel is mainly used for transparenttransmission of point-to-point data service packets.

Transparent Transmission of Point-to-Point Data PacketsCommonly, the tunnel is used to provide a point-to-point channel for services such as EPLservice. In this way, PEs on a RTN network can transparently transmit services. Figure 3-7shows how point-to-multipoint data packets are transparently transmitted on a network.



3-13

Figure 3-7 Transparent transmission of point-to-point data packets

Third-party IP network

Node BRNCPE

PE

Static CR tunnelRSVP TE tunnelLDP tunnel

IP tunnel

MPLS network

RSVP TEnetwork

An edge node on one network receives services from Node B, and transmits the services to theRNC connected to another PE. In this case, a point-to-point MPLS tunnel can be used. Theapplication scenarios of different tunnels are as follows:

l When an IP tunnel transmits services, the service can be transparently transmitted on athird-party IP network. Therefore, IP tunnels are used mainly when the services that theRTN equipment transmits need to be transparently transmitted on a third-party IP network.

l When a static CR tunnel transmits services, the service can be transparently transmitted onan entire MPLS network. Therefore, static CR tunnels are used mainly when high QoS isnot required and the routes are specified.

l When an RSVP TE tunnel transmits services, the service can be transparently transmittedon an entire RSVP TE network. RSVP TE tunnels are used when high QoS and resourceusage are required on a network.

l When an LDP tunnel transmits services, the service can be transparently transmitted on anentire MPLS network. LDP tunnels are widely used on MPLS VPNs. To prevent trafficcongestion on a certain node of a VPN, you can configure the LDP over RSVP feature.That is, the LSP of an LDP tunnel traverses the RSVP TE domain and thus the LDP tunnelcan transmit VPN services.

When all the preceding tunnels traverse the third-party equipment, you can set the third-partyequipment as a virtual node to ensure that the tunnels are created properly.

3.3.2 Tunnel Configuration FlowThis section describes the operation tasks for configuring the Tunnel, and relations among thesetasks. When configuring and managing the Tunnel, follow the configuration flow.

Configure and manage Tunnels by following the configuration flow shown in Figure 3-8.




Issue 02 (2010-09-24)

Figure 3-8 Tunnel configuration flow

Creating Network

StartRequired

End

Create the Tunnel

Optional

Configure the network-side interface

Configure the LSR ID

Configure the control plane

For the detailed configuration tasks shown in Figure 3-8, see Table 3-1.

Table 3-1 Tunnel configuration tasks

Task Remarks

1. Create Network To create a network, you need to create NEs, configureNE data, create fibers and crate level 2 link.

2. Configure the network-sideinterface

Set the general attributes and Layer 3 attributes (tunnelenable status and IP address) for interfaces to carry thetunnel carrying.

3. Configure the LSR ID Specifies the LSR ID for each NE that a servicetraverses and the start value of the global label space.Each LSR ID is unique on a network.



3-15

Task Remarks

4. Configure the control plane Set the protocol parameters related to the control planeto create the tunnel.l When you create a static CR tunnel to carry services,

you do not need to set the parameters relevant to thecontrol plane but you need to manually add labels.

l When you create an RSVP TE tunnel to carryservices, the LDP automatically distributes labels.In this case, you need to set the parameters relevantto the control plane.1. Set the IGP-ISIS protocol parameters.2. Set the MPLS-RSVP protocol parameters.

l When you create an LDP Tunnel to carry services,the LDP automatically distributes labels. In thiscase, you need to set the parameters relevant to thecontrol plane.1. Set the IGP-ISIS protocol parameters.2. Create the MPLS-LDP.

l When you create an IP tunnel to carry services, thelabel distribution protocol automatically allocatesthe forwarding label value. In addition, you need toconfigure parameters relevant to the control plane.Create a static route table.

NOTETo configure parameters relevant to the control plane, refer tothe descriptions of configuring the control plane in theOperation Guide for RTN NE Management.

5. Create the Tunnel Configure the basic information, equipment list,advanced attributes of the tunnel.

3.3.3 Configuring a TunnelThis topic describes how to configure a tunnel, such as creating a tunnel, deploying a tunnel,viewing discrete tunnels, and deleting a tunnel.

3.3.3.1 Creating a TunnelThis topic describes how to create a tunnel in the end-to-end mode. You can create a tunneleasily and efficiently.

3.3.3.2 Creating Tunnels in BatchesIn certain commonly used networks, the U2000 provides the function of creating tunnels inbatches. Currently, you can create only RSVP-TE tunnels in batches.

3.3.3.3 Creating a Protection GroupThis topic describes how to create a tunnel protection group. If a tunnel protection group iscreated, the services carried over the active tunnel is switched over to the protection tunnel whenthe working tunnel is faulty.




Issue 02 (2010-09-24)

3.3.3.4 Configuring OAM for a TunnelThis topic describes how to configure OAM for a tunnel.

3.3.3.5 Automatic Search for Protection GroupsThis topic describes automatic search for protection groups. With this function, you can recoverthe protection group existing on the current network to the end to end management module ofthe NMS for monitoring. In this manner, you can ensure the normal running of these protectiongroup.

3.3.3.6 Deploying a TunnelThis topic describes how to apply the settings of a tunnel to NEs.

3.3.3.7 Viewing a Discrete TunnelTo view a discrete tunnel facilitates the management of discrete tunnels.

3.3.3.8 Deleting a TunnelThis topic describes how to delete a tunnel on the U2000.

3.3.3.1 Creating a TunnelThis topic describes how to create a tunnel in the end-to-end mode. You can create a tunneleasily and efficiently.


You must complete the correct configuration of the port attributes.

You must complete the correct setting of the LSR ID for each NE.

The control plane must be configured for the RSVP-TE, and IP tunnels.

Procedure

Step 1 Choose Service > Tunnel > Create Tunnel from the main menu.



3-17

Step 2 Configure basic information.

NOTE

l When you create a reverse tunnel, the U2000 automatically allocates different Tunnel Name to theforward and reverse tunnels. If you manually set Tunnel Name for the forward tunnel, the U2000automatically set Tunnel Name to Forward Tunnel Name+_Reverse for the reverse tunnel.

l When "Signaling Type" is set to be Static CR. In this case, if you select Create Reverse Tunnel, theU2000 creates two unidirectional tunnels in two opposite directions. If you select Create BidirectionalTunnel, the U2000 creates a bidirectional tunnel, which has two opposite directions.

l When "Signaling Type" is set to be Static CR, You can select the "Create Protection Group", the tunneland the protection group of tunnel are created at the same time.

l The "Template" parameter is available only when the "Signaling Type" parameter is set to RSVPTE. You can configure the detailed information of a tunnel by using a template.

l When you create a RSVP-TE tunnel, you can select the "Configure As Bypass Tunnel" check boxto create a bypass protection tunnel.

l A static CR tunnel is created on the basis of certain constraints. The mechanism for creating andmanaging those constraints are constraint-based routing (CR). Different from a static tunnel, theestablishment of a CR tunnel depends on the routing information and other conditions, for example,the specified bandwidth, the fixed route, and QoS parameters. The PTN supports only the static CRtunnel.

Step 3 Configure the NE list.1. Select the source and sink NEs or the transit NE and configure the NE location in a tunnel

in the NE Role column.

You can select an NE in the following methods:l Manner 1: In the physical topology in the upper right pane, select the required NE, right-

click and choose Add from the shortcut menu.l Manner 2: In the physical topology in the upper right pane, double-click the required

NE.l Manner 3:

a. Click Add and select NE from the drop-down list.




Issue 02 (2010-09-24)

b. In the dialog box that is displayed, select the required NE and click OK.

NOTE

In the case of an RSVP-TE, LDP, or IP tunnel, you need to specify only the source and sink nodesof the tunnel. In the case of a static CR tunnel, you need to specify the source node, sink node, andtransit nodes of the tunnel.

You can choose Add and select Virtual Node from the drop-down list to specify virtual nodesthrough which a tunnel travels. A virtual node simulates an NE beyond the management range of theU2000. The virtual node is used for creating a tunnel whose source NE is on the U2000 but the sinkNE is not on the U2000.

2. Optional: In the case of a static CR tunnel.

Set the route calculation for the U2000 as follows:

a. Select Auto-Calculate route. Then, the U2000 automatically calculates the routes fora tunnel after you finish steps 2 and 3.

b. Set Restriction Bandwidth(Kbit/s) and specify the source and sink nodes.c. Specify route constraint. Specifically, you can click Route Restriction and specify

route constraint in the dialog box that is displayed. Alternatively, you can specify theexplicit and excluded restriction through shortcut menu items in the physical topology.

NOTE

You can set NEs or ports as route constraints as required.

d. If you do not select Auto-Calculate route, you can click Calculate Route to calculatethe routes for a tunnel in the U2000.

NOTE

A layer 2 link must be configured before route calculation, refer the chapter of topology managementto configure the layer 2 link.

By default, the shortest route is selected from the routes that are calculated according to RestrictionBandwidth(Kbit/s) and route constraints.

You select Create Protection Group and click Configure Protection Group to configureparameters relevant to the protection group.

Step 4 Click Details to configure details of the tunnel.

NOTE

l It is recommended that you configure details of an RSVP-TE tunnel by using a template.

l In the case of a static CR tunnel, Next Hop is the IP address of the ingress port of the next node in thedirection of the tunnel.

l In the case of a static CR tunnel, double-click Out Interface or In Interface. In the dialog box that isdisplayed, select an interface and click Configure to configure the attributes of the interface or clickAdd Virtual Interface to create Ethernet virtual interface.

Step 5 Optional: In the case of static CR tunnel, if you select Create Protection Group, you can clickConfigure Protection Group to configure parameters relevant to the protection group and clickConfigure OAM to configure OAM parameters relevant to the protection group.

Step 6 Select the Deploy check box and click OK.



3-19

NOTE

l If you clear the Deploy check box, the configuration data information is stored only on the U2000. Ifyou select the Deploy check box, the configuration data information is stored on the U2000 and appliedto NEs. By default, the Deploy check box is selected.

l When you select the Deploy and Enable check box, A tunnel is available on NEs only when it isenabled.

----End

3.3.3.2 Creating Tunnels in Batches

In certain commonly used networks, the U2000 provides the function of creating tunnels inbatches. Currently, you can create only RSVP-TE tunnels in batches.

Prerequisite

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

Configuration of the port attributes must be correct.

Settings of the LSR ID for each NE must be correct.

Configuration of the control plan for each NE must be correct.

Procedure

Step 1 Choose Service > Tunnel > Batch Create Tunnel from the main menu.

Step 2 Configure basic information. In the Basic Information field, set the Network Type, ProtocolType and Signaling Type parameters.




Issue 02 (2010-09-24)

NOTE

Currently, the U2000 supports the following networking modes:l 1. Full-Mesh: The equipment is bidirectionally and fully connected.l 2. Hub-Spoke: All spoke nodes and hub nodes are directionally connected. In addition, the hub nodes

are bidirectionally and fully connected.l 3. Ring: Bidirectional connections are generated based on rings.You can set the Template parameter when the Signaling Type parameter is set to RSVP TE.

Step 3 Configure the NE list.1. Select the source and sink NEs or the transit NE and configure the NE location in a tunnel

in the NE Role column.

You can select an NE in the following manners:l Manner 1: In the physical topology in the upper right pane, select the required NE, right-

click and choose Add from the shortcut menu.l Manner 2: In the physical topology in the upper right pane, double-click the required

NE.l Manner 3:

a. Click Add and select NE from the drop-down list.b. In the dialog box that is displayed, select the required NE and click OK.

2. Optional: You can set the NE Role parameter when the Network Type parameter is setto Hub-Spoke.

Step 4 Click Auto-Assign. Then, the U2000 automatically assigns IDs to the tunnels created in batches.NOTE

You can also enter tunnel IDs.

Step 5 Configure details of tunnels.l In the case of RSVP-TE tunnels, set the General, TE Information, Trail Information,

Protection Attribute, QoS Information, and Advance Information parameters.l In the case of LDP tunnels, set the EXP parameter.

Step 6 Select the Deploy check box and click OK.NOTE

If you select the Deploy check box, the tunnel information is stored on the U2000 and applied to NEs. Bydefault, the Deploy check box is selected.When you select the Deploy and Enable check box, A tunnel is available on NEs only when it is enabled.

----End

3.3.3.3 Creating a Protection GroupThis topic describes how to create a tunnel protection group. If a tunnel protection group iscreated, the services carried over the active tunnel is switched over to the protection tunnel whenthe working tunnel is faulty.


The working and protection tunnels of an MPLS tunnel must be created.



3-21

Context

Figure 3-9 shows the window for creating a tunnel protection group.

Figure 3-9 The figure of tunnel protection group

Precautions:l The MPLS APS protection must not be coupled with the FRR, LMSP, LAG, and microwave

1+1 protection.

l The protection tunnel should not carry any extra service.

Procedure

Step 1 Choose Service > Tunnel > Create Protection Group from the main menu.

Step 2 Configure basic information of a tunnel protection group.

NOTE

If a tunnel protection group is of the 1+1 protection type, services are dually fed on the source and selectivelyreceived on the sink. If a tunnel protection is of the 1:1 protection type, services are processed in the singlefed single receiving mode.

Single-ended switching refers to the scenario wherein only the local end is switched but the peer end is notnotified to switch when a fault occurs at one end. Single-ended switching does not negotiate by usingnegotiation packets. Therefore, it is fast and reliable.

Dual-ended switching refers to the scenario wherein the local end is switched and the peer end is notifiedto switch when a fault occurs at one end. In the case of dual-ended switching, the come-and-go path of aservice is the same. This facilitates service management.

Step 3 Click Add. In the dialog box that is displayed, select the working tunnel and the protection tunneland click OK.

Step 4 Optional: Select a required tunnel, click Configure OAM, and then configure the OAMinformation of the tunnel. An OAM packet is used to detect the connectivity of a link. When afault occurs on the working tunnel, services are switched to the protection tunnel.




Issue 02 (2010-09-24)

NOTE

By default, the OAM status is enabled for the protection tunnel, to ensure that the duration of switching tothe protection tunnel is less than 50 ms, set the detect type to FFD and the frequency to 3.3.

It is optional to configure OAM. If you do not configure it, the U2000, by default, enables the OAM of thetunnel protection group when you configure the tunnel protection group.

You can set other OAM parameters only when you set OAM Status to Enabled. You can set DetectionPacket Type and Detection Packet Period(ms) only when you set Detection Mode of the sink toManual. The value of SF Threshold must be equal to or greater than the value of SD Threshold.

Step 5 Configure attributes of the tunnel protection group.

Step 6 Choose Deploy. Click OK.

----End

3.3.3.4 Configuring OAM for a Tunnel

This topic describes how to configure OAM for a tunnel.




3-23

l The running status of RSVP TE tunnel is UP.l OAM cannot be configured for an IP tunnel.

ProcedureStep 1 Choose Service > Tunnel > Manage Tunnel from the main menu.

Step 2 In the Set Filter Criteria dialog box set the filter criteria. Then, click Filter. The servicesmeeting the filter criteria are displayed in the query result area.

Step 3 Right-click a required tunnel and choose OAM > Configure OAM from the shortcut menu.

Step 4 In the dialog box that is displayed, set OAM parameters of the tunnel.

Step 5 Click OK.

Step 6 Select one or more tunnel, right click and choose OAM > Enable OAM to enable the OAM oftunnel.

----End

3.3.3.5 Automatic Search for Protection GroupsThis topic describes automatic search for protection groups. With this function, you can recoverthe protection group existing on the current network to the end to end management module of




Issue 02 (2010-09-24)

the NMS for monitoring. In this manner, you can ensure the normal running of these protectiongroup.


Procedure

Step 1 Choose Service > Tunnel > Search for Protection Group from the main menu.

Step 2 In the dialog box that is displayed, click Add, select required equipment, and then click OK.

Step 3 Click OK. A dialog box is displayed indicating the number of protection groups.

Step 4 Click OK in the Prompt dialog box.

----End

3.3.3.6 Deploying a TunnelThis topic describes how to apply the settings of a tunnel to NEs.


Procedure

Step 1 Choose Service > Tunnel > Manage Tunnel from the main menu.


Step 3 Right-click a tunnel whose settings are not applied to NEs and choose Deploy from the shortcutmenu.



3-25

Step 4 Click Close in the dialog box displayed.

----End

3.3.3.7 Viewing a Discrete TunnelTo view a discrete tunnel facilitates the management of discrete tunnels.


A discrete tunnel must exist on the U2000.

ProcedureStep 1 Choose Service > Tunnel > Manage Discrete Tunnel from the main menu.

Step 2 Click Filter Criteria. In the dialog box that is displayed, set filtering criteria and click Filter.

Step 3 On the discrete tunnel management window, select a discrete tunnel, click the correspondingtab to view details.

Step 4 Optional: Select a discrete tunnel, click Delete button and click Yes in the dialog box displayed.

----End

3.3.3.8 Deleting a TunnelThis topic describes how to delete a tunnel on the U2000.





Issue 02 (2010-09-24)

A tunnel must exist on the U2000.

Procedure


Step 2 Click Filter to set the filter criteria. Then, click OK. The services meeting the filter criteria aredisplayed in the query result area..

Step 3 Right-click a required tunnel and choose Delete from the shortcut menu.

NOTE

Deleting a tunnel is to delete a tunnel on a per-NE basis and an end-to-end tunnel. When you choose Deletefrom Network Side, only the data about end-to-end tunnels is deleted.

A discrete tunnel cannot be deleted from the network side.

Step 4 In the dialog box that is displayed, click Yes.

----End

3.3.4 Monitoring a TunnelThis topic describes how to monitor a tunnel to facilitate tunnel services management.

3.3.4.1 Viewing the VPN Service Carried on a TunnelTAfter viewing VPN services that are transmitted in a tunnel, you can conveniently manage thetunnel and the VPN services.

3.3.4.2 Viewing the Topology of a TunnelThis topic describes how to view the tunnel topology. By viewing the topology of a tunnel, youcan learn the topology structure and running status of the tunnel in real time

3.3.4.3 Viewing the Performance of a TunnelThis topic describes how to view the performance of a tunnel.

3.3.4.4 Viewing the Alarms of a TunnelThis topic describes how to view the alarms of a tunnel.

3.3.4.5 Monitoring the Running Status of a TunnelBy using this function, you can view the running status of a tunnel in real time.

3.3.4.6 Viewing the LSP Topology of a TunnelThis topic describes how to view the LSP topology of a tunnel. To view the actual routinginformation of a tunnel, you can perform this operation.

3.3.4.7 Diagnosing a TunnelThis topic describes how to diagnose a tunnel by performing the LSP ping and LSP tracert tests.

3.3.4.1 Viewing the VPN Service Carried on a TunnelTAfter viewing VPN services that are transmitted in a tunnel, you can conveniently manage thetunnel and the VPN services.

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



3-27

Procedure



Step 3 Right-click a required tunnel and choose View VPN from the shortcut menu.

NOTE

You can view the VPN service of only one tunnel at a time.

You can view the end-to-end services that are transmitted in a tunnel, but not the discrete services that aretransmitted in the tunnel.

Step 4 View information of the VPN service carried on the tunnel in View VPN window.

Step 5 Optional: Select a required VPN service, click View Details. In the relevant servicemanagement window, you can view or modify parameters of the VPN service.

----End

3.3.4.2 Viewing the Topology of a TunnelThis topic describes how to view the tunnel topology. By viewing the topology of a tunnel, youcan learn the topology structure and running status of the tunnel in real time


Procedure



Step 3 Select a required tunnel and view the topology of the tunnel.Perform the following operations as required.l On the Topology tab page, right-click an NE and choose View Real-Time Performance or

NE Explorer from the shortcut menu.l On the Topology tab page, right-click a link and choose Fast Diagnose, View VPN, View

LSP Topology, or Alarm from the shortcut menu.

NOTE

You can view the real-time performance of only the tunnels that are in the deployed states. You can viewthe LSP topology of the RSVP TE tunnel that is in the UP running state.




Issue 02 (2010-09-24)

Step 4 Optional: On the window for creating a tunnel, click the Service Topology tab to view topologyinformation of the new tunnel.

Step 5 Optional: In the Main Topology, click Current View, select Tunnel View from the drop-downlist, and then view the topology of the tunnel in the network-side tunnel topology view.

----End

3.3.4.3 Viewing the Performance of a TunnelThis topic describes how to view the performance of a tunnel.


Procedure



Step 3 View the runtime performance of a tunnel. Right-click the NE and choose View Real-TimePerformance from the shortcut menu in the topology view.

Step 4 Create a monitoring instance for a tunnel. For details, refer to the chapter of monitoring instancemanagement in Performance Management System (PMS).

Step 5 View the history performance of a tunnel. Right-click a required tunnel and choosePerformance > View History Data from the shortcut menu.

----End

3.3.4.4 Viewing the Alarms of a TunnelThis topic describes how to view the alarms of a tunnel.



3-29

Prerequisite

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

Procedure



Step 3 View the Alarm Status parameter of a tunnel.

Step 4 Right-click a required tunnel and choose Alarm > View Current Alarm from the shortcut menuto view current alarms of the tunnel.

Step 5 Right-click a required tunnel and choose Alarm > View History Alarm from the shortcut menuto view history alarms of the tunnel.

----End

3.3.4.5 Monitoring the Running Status of a Tunnel

By using this function, you can view the running status of a tunnel in real time.

Prerequisite

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

Procedure



Step 3 Right-click the tunnel and select Update Running Status, view the Running Status parameterof a tunnel.

----End

3.3.4.6 Viewing the LSP Topology of a Tunnel

This topic describes how to view the LSP topology of a tunnel. To view the actual routinginformation of a tunnel, you can perform this operation.

Prerequisite

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

The RSVP-TE tunnel must support this operation and the running status of tunnel is UP.

The function of viewing a tunnel must be supported.




Issue 02 (2010-09-24)

Procedure



Step 3 Right-click a required tunnel and choose View LSP Topology from the shortcut menu. Clickthe link in the dialog box that is displayed, view the actual routing information of the tunnel.

----End

3.3.4.7 Diagnosing a TunnelThis topic describes how to diagnose a tunnel by performing the LSP ping and LSP tracert tests.


In the case of a static CR tunnel, the IS-IS protocol must be enabled on the source and sink portsof an MPLS tunnel. Alternatively, a diagnose test must be initiated at the local NE and a staticroute in control plane must be configured on the opposite NE.

Procedure



Step 3 Configure a scheduled test.1. Right-click a required tunnel and choose Diagnose > Create Test Suite from the shortcut

menu.2. Select the Select check box and click Next.3. Select the LSP Ping check box and click Details. In the dialog box that is displayed, set

advance test parameters and click OK.4. Set parameters in the Test Time field, click Add, and then click Finish.

Step 4 View the test strategy.1. Right-click a required tunnel and choose Diagnose > View Test Strategy from the shortcut

menu.2. Click Condition. In the dialog box that is displayed, set relevant criteria and click OK.

Click Query.3. Select a record and click Task Information and Associated Test Suite to view relevant

information.

Step 5 View the result of a scheduled test.1. Right-click a required tunnel and choose Diagnose > View Test Result from the shortcut

menu.2. Click Query to view the result of a scheduled test.3. Optional: Click Export Result to export the result of the scheduled test to local computer.



3-31

NOTEThe result of a scheduled test can be exported in a .cvs, .html, .xls, .pdf or .txt file.

Step 6 Configure a manual test.1. Right-click a required tunnel and choose Test and Check from the shortcut menu.

2. Optional: Select the LSP Ping or ICMP Ping check box and click . In the dialogbox that is displayed, set parameters of the ping test and click OK.

3. Optional: Select the LSP Tracert or ICMP Tracert check box and click . In thedialog box that is displayed, set parameters of the LSP tracert test and click OK.

4. Click Run and view the test result on the right pane.

----End

3.3.5 Configuration Example (Static CR Tunnel)This topic describes a networking diagram and the corresponding example of configuring a staticCR tunnel on the network.

3.3.5.1 Networking DiagramThis topic describes the networking topology of the NEs.3.3.5.2 Service PlanningThis topic describes parameters that are required for the data configuration.3.3.5.3 Configuration Process (Creating a Static CR Tunnel)This topic describes how to create a static CR tunnel by using the trail function.

3.3.5.1 Networking DiagramThis topic describes the networking topology of the NEs.

Between BTS and BSC, the voice service is transported through the RTN equipment and thestatic MPLS tunnel service needs to be created, as shown in Figure 3-10.

Figure 3-10 Networking diagram of the MPLS tunnel

Packet Swtiching NetworkNE1

NE2

BTSBSCNE3

NE4

Working tunnel

Bypass tunnel




Issue 02 (2010-09-24)

The voice service requires high network security. The service tunnel between NE1 and NE3 isconfigured with 1:1 protection. In the case of a service that requires high network security, MPLSAPS protection can be configured to protect the service.

l The NE1-to-NE3 working tunnel is along the NE1-NE2-NE3 trail. NE2 is the transit node.l The NE1-to-NE3 protection tunnel is along the NE1-NE4-NE3 trail. When the NE1-NE2

link fails or NE2 fails, the protection tunnel protects the working tunnel.

3.3.5.2 Service Planning

This topic describes parameters that are required for the data configuration.

Microwave Port Planning

Table 3-2 Microwave port planning

NE Microwave Port Peer NE Peer MicrowavePort

NE13-IFE2-1 NE2 4-IFE2-1

4-IFE2-1 NE4 3-IFE2-1


4-IFE2-1 NE1 3-IFE2-1


4-IFE2-1 NE2 3-IFE2-1


4-IFE2-1 NE3 3-IFE2-1

NE Parameter Planning

Table 3-3 NE parameter planning

NE LSR ID Port Port IP Mask

NE1 1.0.0.13-IFE2-1 10.1.1.1 255.255.255.252

4-IFE2-1 10.1.4.2 255.255.255.252

NE2 1.0.0.23-IFE2-1 10.1.2.1 255.255.255.252

4-IFE2-1 10.1.1.2 255.255.255.252

NE3 1.0.0.33-IFE2-1 10.1.3.1 255.255.255.252

4-IFE2-1 10.1.2.2 255.255.255.252



3-33


NE4 1.0.0.43-IFE2-1 10.1.4.1 255.255.255.252

4-IFE2-1 10.1.3.2 255.255.255.252

Tunnel Planning

Table 3-4 Tunnel planning

Parameter Working Tunnel Protection Tunnel

Tunnel ID 100 101 120 121

Tunnel Name WorkingTunnel

WorkingTunnel_Reverse

ProtectionTunnel

ProtectionTunnel_Reverse

Signaling Type Static CR Static CR Static CR Static CR

Protocol Type MPLS MPLS MPLS MPLS

LSP Type E-LSP E-LSP E-LSP E-LSP

EXP None None None None

CIR(Kbit/s) No Limit No Limit No Limit No Limit

Ingress Node NE1 NE3 NE1 NE3

Transit Node NE2 NE2 NE4 NE4

Egress Node NE3 NE1 NE3 NE1

Ingress NodeRouteInformation

NE1l Out

Interface: 3-IFE2-1(Port-1)

l Out Label:20

NE3l Out Interface:

4-IFE2-1(Port-1)

l Out Label: 21

NE1l Out


l Out Label:22

NE3l Out


l Out Label:23

Transit NodeRouteInformation

NE2l In Interface:

4-IFE2-1(Port-1)

l In Label: 20l Out


l Out Label:30

NE2l In Interface:

3-IFE2-1(Port-1)

l In Label: 21l Out Interface:

4-IFE2-1(Port-1)

l Out Label: 31

NE4l In Interface:

3-IFE2-1(Port-1)

l In Label: 22l Out


l Out Label:32

NE4l In Interface:

4-IFE2-1(Port-1)

l In Label: 23l Out


l Out Label:33




Issue 02 (2010-09-24)

Parameter Working Tunnel Protection Tunnel

Egress NodeRouteInformation

NE3l In Interface:

4-IFE2-1(Port-1)

l In Label: 30

NE1l In Interface:

3-IFE2-1(Port-1)

l In Label: 31

NE3l In Interface:

3-IFE2-1(Port-1)

l In Label: 32

NE1l In Interface:

4-IFE2-1(Port-1)

l In Label: 33

Protection Group Planning

Table 3-5 Planning of protection group parameters

Parameter Vlaue

Group Name Protection Group

Protection Type 1:1

Switch Mode Double Ended

Protocol Status Enable

Revertive Mode Revertive

Hold-off Time(100ms) 0

WTR Time(min) 5

Tunnel Type Working Tunnel: Forward WorkingProtection Tunnel:Forward ProtectingProtection Tunnel_Reverse: BackwardWorkingWorking Tunnel_Reverse: BackwardProtecting

3.3.5.3 Configuration Process (Creating a Static CR Tunnel)

This topic describes how to create a static CR tunnel by using the trail function.

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

l You must understand the networking, requirements and service planning of the example.

l A network must be created.

Procedure

Step 1 Configure the microwave port that carries the MPLS tunnel.



3-35

1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > InterfaceManagement > Microwave Interface from the Function Tree to configure the network-side interface.

2. In the General Attributes tab, select the 3-IFE2-1(Port-1)and 4-IFE2-1(Port-1). Right-click the Port Mode filed and select Layer 3. Set the parameters as required, and clickApply.

NOTE

l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ.l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the

interface can be used by tunnel.

3. Select 3-IFE2-1(Port-1) and 4-IFE2-1(Port-1) on the Layer 3 Attributes tab page. Right-click the Enable Tunnel field and choose Enabled from the shortcut menu. Right-clickthe Specify IP Address field and choose Manually from the shortcut menu. Then, set theparameters, such as IP Address and IP Mask, and click Apply.

Parameter Example Value Principle for ValueSelection

Enable Tunnel Enabled Set this parameteraccording to the serviceplanning.

Max Reserved Bandwidth(Kbit/s)

1000000 The maximum reservedbandwidth should notexceed the physicalbandwidth of the bearerport.

Admin Group 0 It is configured only for adynamic tunnel.

Specify IP Address Manually You can set the port IPaddress when Manually isselected.

IP Address 3-IFE2-1(Port-1): 10.1.1.14-IFE2-1(Port-1): 10.1.4.2

Set this parameteraccording to the serviceplanning.

IP Mask 255.255.255.252 Set this parameteraccording to the serviceplanning.

4. Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 1.1 through

Step 1.3 to set parameters of relevant interfaces.

Set the relevant parameters as follows:




Issue 02 (2010-09-24)

The general attributes and Layer 3 attributes of each interface are consistent with those ofNE1-4-IFE2-1(Port-1), except that the IP addresses are different.

The Layer 3 attributes for each interface are set as follows:


IP Address The layer 3 attributes ofeach port are as follows:l NE2-3-IFE2-1(Port-1)

IP Address: 10.1.2.1l NE2-4-IFE2-1(Port-1)





IP Address: 10.1.3.2


Step 2 Set LSR IDs.1. In the NE Explorer, select NE1 and choose Configuration > MPLS Management > Basic

Configuration from the Function Tree.2. Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.


LSR ID NE1: 1.0.0.1 Set this parameteraccording to the networkplanning. In addition, thisvalue is unique on the entirenetwork.

Start of Global Label Space 0 Set this parameteraccording to the networkplanning.

3. Display the NE Explorer of NE2, NE3, and NE4 separately and perform the preceding two

steps to set the parameters, such as LSR ID.



3-37


LSR ID NE2: 1.0.0.2NE3: 1.0.0.3NE4: 1.0.0.4

Set this parameteraccording to the networkplanning. In addition, thisvalue is unique on the entirenetwork.


Step 3 Create the working tunnel.1. Choose Service > Tunnel > Create Tunnel from the main menu.2. Set the basic information about the working tunnel.


Tunnel Name Working Tunnel Set this parameteraccording to the serviceplanning.

Protocol Type MPLS Set this parameteraccording to the serviceplanning.

Signaling Type Static CR Set this parameteraccording to the serviceplanning.

Create Reverse Tunnel Selected This parameter is selectedwhen a reverse tunnel needsto be created.

3. Configure the NE list. On the physical topology, double-click NE1, NE2, and NE3 to add

them to the NE list and set the corresponding NE roles.




Issue 02 (2010-09-24)


NE Role NE1: IngressNE2: TransitNE3: Egress

An ingress is the incomingnode of a network. In thisexample, NE1 is an ingressnode.A transit is a pass-throughnode. In this example, NE2is a transit node.An egress is the outgoingnode of a network. In thisexample, NE3 is an egressnode.

Deploy Selected When this parameter isselected, a tunnel is savedon the U2000 and appliedto the corresponding NEs

4. Click Details to set the details of the reverse tunnel. Click OK.


Tunnel ID l Forward Tunnel: 100l Reverse Tunnel: 101


CIR(Kbit/s) Forward and ReverseTunnels: 10000




3-39


LSP Type Forward and ReverseTunnels: E-LSP

Currently, this parametercan be set to E-LSP only.E-LSP indicates that thetunnel determines thescheduling priority anddiscarding priority ofpackets according to theEXP information. On oneMPLS tunnel of the E-LSPtype, there can be amaximum of eight types ofPWs.

EXP Forward and ReverseTunnels: None

Set this parameteraccording to the networkplanning.

Out Interface Forward Tunnel:l NE1: 3-IFE2-1l NE2: 3-IFE2-1Reverse Tunnel:l NE3: 4-IFE2-1l NE2: 4-IFE2-1

Set this parameteraccording to the serviceplanning. Only thisparameter needs to be setfor only the ingress nodeand transit node.

Out Label Forward Tunnel:l NE1: 20l NE2: 30Reverse Tunnel:l NE3: 21l NE2: 31


In Interface Forward Tunnel:l NE2: 4-IFE2-1l NE3: 4-IFE2-1Reverse Tunnel:l NE2: 3-IFE2-1l NE1: 3-IFE2-1

Set this parameteraccording to the serviceplanning. Only thisparameter needs to be setfor only the egress node andtransit node.

In Label Forward Tunnel:l NE2: 20l NE3: 30Reverse Tunnel:l NE2: 21l NE1: 31





Issue 02 (2010-09-24)


Next Hop Forward Tunnel:l NE1: 10.1.1.2l NE2: 10.1.2.2Reverse Tunnel:l NE3: 10.1.2.1l NE2: 10.1.1.1

Set this parameteraccording to the serviceplanning. Only thisparameter needs to be setfor only the ingress nodeand transit node.

Step 4 Create the protection tunnel.1. Create the protection tunnel by referring to Step 3.1 through Step 3.4.

Set the basic Information as follows:


Tunnel Name Working Tunnel Set this parameteraccording to the serviceplanning.


Signaling Type Static CR Set this parameteraccording to the serviceplanning.


Set the node information as follows:



3-41


NE Role NE1: IngressNE4: TransitNE3: Egress

An ingress is the incomingnode of a network. In thisexample, NE1 is an ingressnode.A transit is a pass-throughnode. In this example, NE4is transit node.An egress is the outgoingnode of a network. In thisexample, NE3 is an egressnode.

Deploy Selected When this parameter isselected, a tunnel is savedon the U2000 and deliveredto the corresponding NEs

For route details, see the descriptions of route settings in Table 3-4.

Step 5 Creating the protection group.

1. Choose Service > Tunnel > Create Protection Group from the main menu.2. Configure basic information of a tunnel protection group.


Group Name Protection Group Set this parameteraccording to the serviceplanning.




Issue 02 (2010-09-24)


Protection Type 1:1 Set this parameteraccording to the serviceplanning.

Switch Mode Double Ended This parameter is selectedwhen a reverse tunnel needsto be created.

3. Click Add. In the dialog box that is displayed, select the working tunnel and the protection

tunnel and click OK.4. Configure the type of tunnel.


Working Tunnel Forward Working Set this parameteraccording to the serviceplanning.

Protection Tunnel Forward Protecting Set this parameteraccording to the serviceplanning.

Protection Tunnel_Reverse Backward Working Set this parameteraccording to the serviceplanning.

Working Tunnel_Reverse Backward Protecting This parameter is selectedwhen a reverse tunnel needsto be created.

5. Configure attributes of the tunnel protection group, choose Deploy, click OK.


Protocol Status Enable Set this parameteraccording to the serviceplanning.

Revertive Mode Revertive Set this parameteraccording to the serviceplanning.

Hold-off Time(100ms) 0 Set this parameteraccording to the serviceplanning.

WTR Time(min) 5 This parameter is selectedwhen a reverse tunnel needsto be created.



3-43

----End

3.3.6 Configuration Example (RSVP TE Tunnel)This topic describes a networking diagram and the corresponding example of configuring a staticRSVP TE tunnel on the network.


3.3.6.2 Service PlanningThis topic describes parameters that are required for the data configuration.

3.3.6.3 Configuration Process (Creating a RSVP TE Tunnel)This topic describes how to create a RSVP TE tunnel by using the trail function.

3.3.6.1 Networking Diagram

This topic describes the networking topology of the NEs.

Between BTS and BSC, the voice service is transported through the RTN equipment, as shownin Figure 3-11.

Figure 3-11 Networking diagram of the MPLS tunnel


NE2

BTSBSCNE3

NE4

Working tunnel

Bypass tunnel

The voice service requires high network security. The service tunnel between NE1 and NE3 isconfigured with FRR protection.

l The primary tunnel between NE1 and NE3 is along the NE1-NE2-NE3 trail. NE2 is thetransit node.




Issue 02 (2010-09-24)

l The bypass tunnel between NE1 and NE3 is along the NE1-NE4-NE3 trail. When the NE1-NE2 link fails or NE2 fails, the bypass tunnel protects the primary tunnel.



Microwave Port Planning

Table 3-6 Microwave port planning

NE Microwave Port Peer NE Peer MicrowavePort


4-IFE2-1 NE4 3-IFE2-1


4-IFE2-1 NE1 3-IFE2-1


4-IFE2-1 NE2 3-IFE2-1


4-IFE2-1 NE3 3-IFE2-1

NE Parameter Planning

Table 3-7 NE parameter planning


NE1 1.0.0.13-IFE2-1 10.1.1.1 255.255.255.252

4-IFE2-1 10.1.4.2 255.255.255.252

NE2 1.0.0.23-IFE2-1 10.1.2.1 255.255.255.252

4-IFE2-1 10.1.1.2 255.255.255.252

NE3 1.0.0.33-IFE2-1 10.1.3.1 255.255.255.252

4-IFE2-1 10.1.2.2 255.255.255.252

NE4 1.0.0.43-IFE2-1 10.1.4.1 255.255.255.252

4-IFE2-1 10.1.3.2 255.255.255.252



3-45

Control Plane Planning

Table 3-8 Control plane planning

Parameter NE1 NE2 NE3 NE4

IGP-ISIS

Node Level level-1-2 level-1-2 level-1-2 level-1-2

Area ID 490001 490001 490001 490001

Port 3-IFE2-1(level-1-2)4-IFE2-1(level-1-2)

3-IFE2-1(level-1-2)4-IFE2-1(level-1-2)



MPLS-LDPPeerEntity

Opposite LSRID

1.0.0.3 - 1.0.0.1 -

Tunnel Planning

Table 3-9 Tunnel planning

Parameter Primary Tunnel Bypass Tunnel

Tunnel ID Forward: 1Reverse: 2

Forward: 3Reverse: 4

Name Forward: Tunnel-0001Reverse: Tunnel-0002

Forward: Tunnel-0003Reverse: Tunnel-0004

Signal Type Dynamic Dynamic

Scheduling Type E-LSP E-LSP

Bandwidth (kbit/s) 10240 10240

Tunnel Source Node NE1 NE1

Tunnel Sink Node NE3 NE3

Forward Route ConstraintPort IP Address

IP addresses of ingress port ofNE2:4-IFE2-1: 10.1.1.2IP addresses of ingress port ofNE3:4-IFE2-1: 10.1.2.2





Issue 02 (2010-09-24)

Parameter Primary Tunnel Bypass Tunnel

Reverse Route ConstraintPort IP Address



Rerouting Mode Include Strict Include Strict

3.3.6.3 Configuration Process (Creating a RSVP TE Tunnel)This topic describes how to create a RSVP TE tunnel by using the trail function.

Prerequisitel You must be an NM user with "NE operator" authority or higher.l You must understand the networking, requirements and service planning of the example.l A network must be created.

Procedure

Step 1 Configure the microwave port that carries the MPLS tunnel.1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface

Management > Microwave Interface from the Function Tree to configure the network-side interface.

2. In the General Attributes tab, select the 3-IFE2-1(Port-1)and 4-IFE2-1(Port-1). Right-click the Port Mode filed and select Layer 3. Set the parameters as required, and clickApply.

NOTE

l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ.

l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then theinterface can be used by tunnel.

3. Select 3-IFE2-1(Port-1) and 4-IFE2-1(Port-1) on the Layer 3 Attributes tab page. Right-click the Enable Tunnel field and choose Enabled from the shortcut menu. Right-clickthe Specify IP Address field and choose Manually from the shortcut menu. Then, set theparameters, such as IP Address and IP Mask, and click Apply.



3-47


Enable Tunnel Enabled Set this parameteraccording to the serviceplanning.

Max Reserved Bandwidth(Kbit/s)

1000000 The maximum reservedbandwidth should notexceed the physicalbandwidth of the bearerport.

Admin Group 0 It is configured only for adynamic tunnel.

Specify IP Address Manually You can set the port IPaddress when Manually isselected.

IP Address 3-IFE2-1(Port-1): 10.1.1.14-IFE2-1(Port-1): 10.1.4.2


IP Mask 255.255.255.252 Set this parameteraccording to the serviceplanning.

4. Display the NE Explorer for NE2, NE3, and NE4 separately. Perform Step 1.1 through

Step 1.3 to set parameters of relevant interfaces.

Set the relevant parameters as follows:

The general attributes and Layer 3 attributes of each interface are consistent with those ofNE1-4-IFE2-1(Port-1), except that the IP addresses are different.

The Layer 3 attributes for each interface are set as follows:




Issue 02 (2010-09-24)


IP Address The layer 3 attributes ofeach port are as follows:l NE2-3-IFE2-1(Port-1)






IP Address: 10.1.3.2







3. Display the NE Explorer of NE2, NE3, and NE4 separately and perform the preceding two

steps to set the parameters, such as LSR ID.


LSR ID NE2: 1.0.0.2NE3: 1.0.0.3NE4: 1.0.0.4




3-49



Step 3 Configure the control plane.1. In the NE Explorer, select NE1 and choose Configuration > Control Plane

Configuration > IGP-ISIS Configuration from the Function Tree.2. Click the Port Configuration tab page. Click New. In the dialog box displayed, click

Add. Select 3-IFE2-1(Port-1) and 4-IFE2-1(Port-1), and click OK.Set parameters as follows:


Link Level level-1-2 Currently, only level-1-2 issupported by the U2000.

LSP RetransmissionInterval(s)

5 In the case of a point-to-point link, if the localequipment fails to receiveany response in a periodafter transmitting an LSP,the local equipmentconsiders that the LSP islost or discarded. To ensurethe transmission reliability,the local equipmenttransmits the LSP again.

Minimum LSPTransmission Interval (ms)

100 Sets the minimum delaybetween two consecutiveLSPs.

3. Display the NE Explorers of NE2, NE3, and NE4 separately and refer to Step 3.1 through

Step 3.2 to set control plane parameters for NE2, NE3, and NE4.The parameters of NE2, NE3, and NE4 are the same as those of NE1, except that the portsspecified for NE2, NE3, and NE4 are different as follows:




Issue 02 (2010-09-24)


Port NE2:l 3-IFE2-1(Port-1)l 4-IFE2-1(Port-1)NE3:l 3-IFE2-1(Port-1)l 4-IFE2-1(Port-1)NE4:l 3-IFE2-1(Port-1)l 4-IFE2-1(Port-1)


Step 4 Create an active tunnel.1. Choose Service > Tunnel > Create Tunnel from the main menu.2. Set the basic information about a tunnel.


Tunnel Name Tunnel-0001 Set this parameteraccording to the serviceplanning.


Signaling Type RSVP TE Set this parameteraccording to the serviceplanning.



3-51



3. Configure the NE list. On the physical topology, double-click NEs to add them to the NE

list. Then, specify the ingress and egress NEs.


NE Role NE1: IngressNE3: Egress

An ingress is the incomingnode of a network. In thisexample, NE1 is an ingressnode.An egress is the outgoingnode of a network. In thisexample, NE3 is an egressnode.


4. Click Details to configure details of the tunnel management.

The general information is as follows:


Tunnel ID Forward Tunnel: 1Reverse Tunnel: 2


The parameters of the affinity object are as follows:




Issue 02 (2010-09-24)


Enable Affinity Forward and ReverseTunnels: Selected

After you select EnableAffinity, when the activetunnel is faulty, the linkswith the same route colorare preferred during arerouting.

Color(0x) Forward and ReverseTunnels: 0

The forward and reversetunnels are set to the samevalue.Set the affinity attribute ofa link. When the primarytunnel is faulty, the link ofthe same color is preferredduring rerouting. When theaffinity attribute of links isnot required, adopt thedefault value.

Mask(0x) Forward and ReverseTunnels: 0

The forward and reversetunnels are set to the samevalue.Set the number of bits of themask. Match the link coloraccording to the number ofbits of the mask. Select theroute of a matching linkcolor.

The parameters of a hop-by-hop object are as follows:


IP Address Forward Tunnel: 10.1.1.2,10.1.2.2Reverse Tunnel: 10.1.2.1,10.1.1.1

Set the IP address that atunnel traverses. For theforward tunnel, use the IPaddress of the NE2-4-IFE2-1(Port-1) and NE3-4-IFE2-1(Port-1) ports. Forthe reverse tunnel, use theIP addresses of the NE3-3-IFE2-1(Port-1) and NE1-3-IFE2-1(Port-1) ports.



3-53


Hop Type Forward and ReverseTunnels: Strictly include

When this parameter is setto Strictly include, thetunnel is created strictly inthe sequence of the set IPaddresses.

Fast reroute attributes are as follows:


Enable FRR Forward and ReverseTunnels: Selected

Select this parameter toenable the FRR function.

FRR BW Type Forward and ReverseTunnels: facility

Currently, only facility issupported. In this mode, aprotection tunnel canprotect multiple LSPs.

FRR Protect Type Forward and ReverseTunnels: Node Protection

The bypass tunnel that aPLR selects is required toprotect the adjacentdownstream node of thePLR and the link betweenthe adjacent downstreamnode and the PLR.

FRR Bandwidth(Kbit/s) Forward and ReverseTunnels: 10000


The QoS configuration is as follows:




Issue 02 (2010-09-24)




EXP Forward and ReverseTunnels: 4


Step 5 Create bypass tunnel.1. Refer to Step 4.1 through Step 4.2 to configure the basic attributes of bypass tunnel.


Tunnel Name Tunnel-0002 Set this parameteraccording to the serviceplanning.


Signaling Type RSVP TE Set this parameteraccording to the serviceplanning.


Configure As BypassTunnel

Selected This parameter needs to beselected because the tunnelis a bypass tunnel.

2. Configure the NE list. On the physical topology, double-click NEs to add them to the NE

list. Then, specify the ingress and egress NEs.



3-55


NE Role NE1: IngressNE3: Egress

An ingress is the incomingnode of a network. In thisexample, NE1 is an ingressnode.An egress is the outgoingnode of a network. In thisexample, NE3 is an egressnode.


3. Click Details to configure details of the tunnel management.

The basic Information is as follows:


Tunnel ID Forward Tunnel: 3Reverse Tunnel: 4


The parameters of the affinity object are as follows:




Issue 02 (2010-09-24)


Enable Affinity Forward and ReverseTunnels: Selected

After you select EnableAffinity, when the activetunnel is faulty, the linkswith the same route colorare preferred during arerouting.

Color(0x) Forward and ReverseTunnels: 0

The forward and reversetunnels are set to the samevalue.Set the affinity attribute ofa link. When the primarytunnel is faulty, the link ofthe same color is preferredduring rerouting. When theaffinity attribute of links isnot required, adopt thedefault value.

Mask(0x) Forward and ReverseTunnels: 0

The forward and reversetunnels are set to the samevalue.Set the number of bits of themask. Match the link coloraccording to the number ofbits of the mask. Select theroute of a matching linkcolor.

The parameters of a hop-by-hop object are as follows:


IP Address Forward Tunnel: 10.1.4.1,10.1.3.1Reverse Tunnel: 10.1.3.2,10.1.4.2

Set the IP address that atunnel traverses. For theforward tunnel, use the IPaddresses of the NE4-3-IFE2-1(Port-1) and NE3-3-IFE2-1(Port-1) ports. Forthe reverse tunnel, use theIP addresses of the NE4-4-IFE2-1(Port-1) and NE1-4-IFE2-1(Port-1) ports.



3-57


Hop Type Forward and ReverseTunnels: Strictly include

When this parameter is setto Strictly include, thetunnel is created strictly inthe sequence of the set IPaddresses.

Fast reroute attributes are as follows:


Enable FRR Forward and ReverseTunnels: Selected

Select this parameter toenable the FRR function.

FRR BW Type Forward and ReverseTunnels: facility

Currently, only facility issupported. In this mode, aprotection tunnel canprotect multiple LSPs.

FRR Protect Type Forward and ReverseTunnels: Node Protection

The bypass tunnel that aPLR selects is required toprotect the adjacentdownstream node of thePLR and the link betweenthe adjacent downstreamnode and the PLR.

FRR Bandwidth(Kbit/s) Forward and ReverseTunnels: 10000


The QoS configuration is as follows:




Issue 02 (2010-09-24)




EXP Forward and ReverseTunnels: 4


The Bypass attribute is as follows:


Protected BW Unlimit Yes Set this parameteraccording to the serviceplanning.

Protected Out Interface Port 4/2 Set this parameteraccording to the serviceplanning.

----End

3.4 Configuring a Service TemplateBy using a service template, you can create services more quickly and easily. You can customizea service template according to actual O&M requirements.

3.4.1 Creating a Service TemplateThis topic describes how to create a service template. There are service templates as follows:VPLS service template, L3VPN service template, PWE3 service template, and RSVP-TE servicetemplate.

3.4.2 Creating a Service by Using a TemplateThis topic describes how to create a service by using a template.



3-59

3.4.1 Creating a Service TemplateThis topic describes how to create a service template. There are service templates as follows:VPLS service template, L3VPN service template, PWE3 service template, and RSVP-TE servicetemplate.

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

Procedure

Step 1 Choose Service > Service Template from the main menu.

Step 2 Click Create and select the required type of the service template from the drop-down list.

Step 3 Set the parameters relevant to the service template.

NOTE

To set the new service template as the default template, select Set as Default Template.

Step 4 Click OK. The service template is created successfully.

Step 5 Optional: In the service template management window, select the new service template, andclick the Configure Template tab to view the details of the template.

Step 6 Optional: In the service template management window, select the new service template, clickConfigure to modify the details of the template.

----End

3.4.2 Creating a Service by Using a TemplateThis topic describes how to create a service by using a template.

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

ContextThe following example describes how to create a tunnel service by using an RSVP TE ServiceTemplate.

Procedure

Step 1 Choose Service > Tunnel > Create Tunnel from the main menu.

Step 2 Configure the general information about a tunnel.1. Set Protocol Type to MPLS and set Signaling Type to RSVP TE.

2. Click . In the dialog box displayed, select the service template to be used.3. Click OK. A dialog box is displayed, indicating that data loss may occur.4. Click Confirm.




Issue 02 (2010-09-24)

5. Select Create Reverse Tunnel or Configure As Bypass Tunnel as required.

Step 3 Configure the NE list. Select source and sink NEs. In NE Role, set the location of an NE in atunnel as follows:

You can select an NE by using any of the following three methods:l Method 1: On the physical topology in the upper right portion, select an NE, right-click, and

choose Add from the shortcut menu.l Method 2: On the physical topology in the upper right portion, double-click an NE.l Method 3:

1. Click Add and select NE from the drop-down list.2. In the dialog box displayed, select an NE and click OK.

Step 4 Select Deploy and click OK. In the dialog box displayed, click Close.

NOTE

If Deploy is not selected, the tunnel is saved only on the U2000. If Deploy is selected, the tunnel is saveon the U2000 and delivered to corresponding NEs. By default, Deploy is selected.

When Deploy is selected, Enable is selected accordingly. A tunnel on the NE side can be used only whenthe tunnel is enabled.

----End

3.5 Viewing a Service ResourceThis topic describes how to view the usage of a service resource.

3.5.1 Querying Public ResourcesThis topic describes how to view the details about a service resource. Service resources includePW IDs, VSI IDs, RDs, RTs, and IP addresses.

3.5.2 Querying CTP ResourcesThis topic describes how to view the interface resources bound to a service.

3.5.1 Querying Public ResourcesThis topic describes how to view the details about a service resource. Service resources includePW IDs, VSI IDs, RDs, RTs, and IP addresses.

Procedure

Step 1 Choose Service > Service Resource > Common Resource Management from the main menu.


NOTE

You can set the filter criteria, such as Resource Type and NE Name. In this manner, only the informationmeeting the filter criteria is displayed in the query result area.

Step 3 In the query result area, you can view the Resource Type, Resource Value, and ServiceSum information about a resource.



3-61

Step 4 After selecting a resource that is already added to a service, you can click the Details tab to viewthe details about the resource, such as Resource Value, NE Name, Service Name, ServiceType, Customer, and Service Deployment Status.

Step 5 On the Details tab page, right-click a resource and choose View Service from the shortcut menu.The service management user interface for the service corresponding to the selected resource isdisplayed.

Step 6 Optional: Click Print to set the print parameters and prints the related data on the current userinterface.

Step 7 Optional: Click Save to export all the service resources in the query result area to a file of thespecified format.

NOTE

The file can be saved in .xls, .txt, .html, .csv.

----End

3.5.2 Querying CTP ResourcesThis topic describes how to view the interface resources bound to a service.

Procedure

Step 1 Choose Service > Service Resource > SAI from the main menu.


NOTE

You can set the filter criteria, such as Service Type and NE name. In this manner, only the informationmeeting the filter criteria is displayed in the query result area.

Step 3 In the query result area, you can view the details about the interface.

Step 4 Right-click an interface that is already bound to a service and choose View Service from theshortcut menu. The service management user interface for the service corresponding to theselected interface is displayed.

Step 5 Optional: Click Print to set the print parameters and prints the related data on the current userinterface.

Step 6 Optional: Click Save to export all the interface resources in the query result area to a file of thespecified format.

NOTE

The file can be saved in .xls, .txt, .html, .csv.

----End

3.6 Managing PWE3 ServicesThis section describes how to configure PWE3 services.

3.6.1 Overview of PWE3This topic describes basic concepts of the PWE3.




Issue 02 (2010-09-24)

3.6.2 PWE3 Configuration ProcessThe configuration process of the PWE3 consists of configure the CES services, ATM services,IP line service and Ethernet services. This section describes the operation tasks for configuringthe services, and relations between the tasks. When configure and managing the PWE3 service,follow the configuration process.

3.6.3 PWE3 Operation TasksThis topic describes all operation tasks relevant to a PWE3 service.

3.6.4 PWE3 Service MonitoringThe PWE3 service monitoring enables you to view the service topology, monitor serviceperformance, and monitor service alarms.

3.6.5 Locating a PWE3 Service FaultThis topic describes how to locate a PWE3 service fault.

3.6.6 Example for Configuring a CES Emulation ServiceThis topic describes the example of configuring a CES emulation service. Specifically, theexample description, service planning, and configuration process are provided.

3.6.7 Example for Configuring an ATM Emulation ServiceThis topic describes the example of configuring an ATM emulation service. Specifically, theexample description, service planning, and configuration process are provided.

3.6.8 Example for Configuring an Ethernet Private Line Emulation ServiceThis topic describes the example of configuring an Ethernet private line emulation service.Specifically, the example description, service planning, and configuration process are provided.

3.6.1 Overview of PWE3This topic describes basic concepts of the PWE3.

3.6.1.1 IntroductionIn a packet switched network (PSN), PWE3 is a Layer 2 service bearing technology that emulatesas faithfully as possible the basic behaviors and characteristics of ATM services, Ethernetservices, low-rate time division multiplexing (TDM) circuit services, and other services. Sucha technology can interconnect the traditional network with PSN network to share resources andexpand the network.

3.6.1.2 Reference Standards and ProtocolsThis topic describes the compliant standards and protocols for various technologies used in thePWE3.

3.6.1.3 PWE3 Basic PrincipleThis topic describes the implementation principle for the PWE3 to carry various Layer 2 serviceson the customer edge (CE) side.

3.6.1.4 PW TemplateA PW template abstracts common attributes of PWs. Hence, you can use the PW templateconveniently for different PWs. Specifically, by using a PW template, you can configure PWswith similar attributes easily.

3.6.1.5 VCCVVirtual circuit connectivity verification (VCCV) is a technology that is used to verify anddiagnose the connectivity of a PW forwarding trail.

3.6.1.6 Static and Dynamic Hybrid Multi-Hop PWThis topic describes the static and dynamic hybrid multi-hop PW.



3-63

3.6.1.7 PW ProtectionTo implement quick data switching, the PW protection mechanism ensures that services can bequickly switched to another PW when one PW fails.

3.6.1.8 ATM Cell Transparent TransmissionThis topic describes the ATM cell transparent transmission technology.

3.6.1.9 The Application of PWE3 ServiceThis topic describes a typical application of the PWE3.

3.6.1.1 IntroductionIn a packet switched network (PSN), PWE3 is a Layer 2 service bearing technology that emulatesas faithfully as possible the basic behaviors and characteristics of ATM services, Ethernetservices, low-rate time division multiplexing (TDM) circuit services, and other services. Sucha technology can interconnect the traditional network with PSN network to share resources andexpand the network.

DefinitionPWE3 is a Layer 2 service bearing technology, mainly used to emulate essential behaviors andcharacteristics of services such as ATM, frame relay, Ethernet, low-rate TDM circuit, andsynchronous optical network (SONET)/synchronous digital hierarchy (SDH) as faithfully aspossible in a PSN.

PWE3 is a point-to-point L2 VPN(Virtual Private Network) technology. PWE3 has the followingfeatures: Adding new signaling; reducing cost of signaling; regulating the auto-negotiation modeof multiple hops; achieving flexible networking diagrams. The PWE3 protocol can reduce packetexchange, avoid repeated PW creations and deletions caused by network unstabilities.

ObjectivesWith development of the IP network, the IP network has great compatibility and great capabilitiesfor expansion, upgrade, and interoperation. The traditional communication network, which haspoor capabilities for expansion, upgrade, and interoperation, is restricted by the transmissionmode and service type. In addition, newly built networks support few services and are unsuitablefor interoperation management. Hence, during the upgrade and expansion of traditionalcommunication networks, you should consider whether to build duplicated networks or useexisting or common network resources. PWE3 is a solution that combines traditionalcommunication networks with the existing packet networks.

PWE3 has certain advantages of MPLS L2VPN. In addition, PWE3 can be used to interconnecttraditional networks with PSNs. Hence, resources can be shared and networks can be expanded.

3.6.1.2 Reference Standards and ProtocolsThis topic describes the compliant standards and protocols for various technologies used in thePWE3.

The reference documents of this feature are as follows:




Issue 02 (2010-09-24)

Document Description Remarks

RFC3916 Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)

RFC3985 Pseudo Wire Emulation Edge-to-Edge (PWE3)Architecture

RFC4446 IANA Allocations for Pseudowire Edge to EdgeEmulation (PWE3)

draft-ietf-pwe3-control-protocol-17

Pseudo wire Setup and Maintenance using the LabelDistribution Protocol

draft-martini-pwe3-pw-switching-03

Pseudo Wire Switching

draft-ietf-pwe3-cw-00 PWE3 Control Word for use over an MPLS PSN

draft-ietf-pwe3-vccv-03

Pseudo Wire Virtual Circuit Connectivity Verification(VCCV)

draft-ietf-pwe3-ethernet-encap-10

Encapsulation Methods for Transport of Ethernet OverMPLS Networks

draft-ietf-pwe3-atm-encap-11

Encapsulation Methods for Transport of ATM OverMPLS Networks

draft-ietf-pwe3-cell-transport-05

PWE3 ATM Transparent Cell Transport Service

RFC 5085 Pseudowire Virtual Circuit Connectivity Verification(VCCV) A Control Channel for Pseudowires

VCCV ofPWs inL2TP V3mode isnotsupported.

3.6.1.3 PWE3 Basic Principle

This topic describes the implementation principle for the PWE3 to carry various Layer 2 serviceson the customer edge (CE) side.

Basic Transmission Components of the PWE3

As shown in Figure 3-12, the basic transmission components of the PWE3 network are asfollows:

l Virtual link pseudo wire (PW)

l Forwarder

l Tunnels



3-65

l PW signaling protocol

Figure 3-12 Basic transmission components of the PWE3

PE1 PE2

CE1

CE2

CE3

CE4

P

VPN1Site1

VPN2Site1

VPN1Site2

VPN2Site2

MPLS Network

ACPWPW Signal

Tunnel

Forwarder Forwarder

The VPN1 packet flow from CE1 to CE3 is taken as an example. The basic data flow is asfollows:

l Layer 2 packets are sent to CE1 first, and the packets gain access to PE1 through the link.

l After PE1 receives the packets, the forwarder selects the PWs for forwarding packets.

l PE1 generates two MPLS labels (a private network label and a public network label)according to the PW forwarding table entries. The private network label is used to identifythe PW, and the public network label is used for a service to traverse over the tunnel toPE2.

l The Layer 2 packets reach PE2 through the public network. Then, the system promptsprivate network labels (on the P equipment, public network labels are prompted in the lasthop but one).

l The forwarder of PE2 selects the link for forwarding packets, and then forwards the Layer2 packets to CE3.

PWE3 Network Mode

The PWE3 network can be in single-hop mode or multi-hop mode.

l Single-hop PWE3 network

Single-hop PW indicates that only one PW is available between U-PEs, and the labelswitching of the internal label is not required.

Figure 3-13 shows the typical network topology of the single-hop PW.




Issue 02 (2010-09-24)

Figure 3-13 PWE3 single-hop topology

MPLS Network

PE1 PE2P

PW

CE1 CE2

l Multi-hop PWE3 network in LDP mode

In most cases, the single-hop PW can meet the actual requirement. In the following threecases, however, the single-hop PW cannot meet the requirement and the multi-hop PWneeds to be used:– Two PEs are not in the same AS domain. In addition, the signaling connection or tunnel

between the two PEs cannot be constructed.– The signaling types on the two PEs are different. For example, one end runs the LDP,

and the other end runs the RSVP.– The access equipment can run the MPLS, but it cannot construct a large number of LDP

sessions. In this case, the user facing provider equipment (UFPE) is used as the U-PE,and the high-performance S-PE is used as the switching node (similar to the signalingreflector) of the LDP sessions.

– The multi-hop PW indicates that multiple PWs are available between U-PEs. Theforwarding mechanisms of the U-PE in the case of multi-hop forwarding and the U-PEin the case of single-hop forwarding are the same. In the case of multi-hop forwarding,the label switching of the PW label should be performed on the S-PE.

Figure 3-14 shows the typical network topology of the multi-hop PW using the LDP asthe signaling.



3-67

Figure 3-14 PWE3 multi-hop topology

MPLS Network

U-PE1 U-PE2S-PE1

PW1

CE1 CE2

S-PE2

PW2 PW3

Static PWThe static PW does not use the signaling protocol for parameter negotiation. The informationrequired by the static PW is manually specified through commands, and the data is transmittedbetween PEs through the tunnel.

Dynamic PWThe dynamic PW is a PW constructed through signaling protocol. The U-PE switches the PWlabel through the LDP, and bundles the corresponding CE through PW ID. After the tunnel thatconnects two PEs is successfully constructed and the label switching and bundling are complete,if the link of the two PEs is up, a PW is constructed.

The message packets of the dynamic PW consist of:

l Request: Requests for label allocation from the opposite end.l Mapping: Notifies the opposite end of the label at the local end and determines whether to

contain the status message according to the default signaling action. (The default Martinimode does not support the status message.)

l Notification: Notifies status to negotiate the PW status, and thus reducing the count ofpackets for interaction.

l Withdraw: Contains the relevant label and status to inform the opposite end to cancel thelabel.

l Release: As a response to the Withdraw packet, informs the opposite end that sends theWithdraw packet to cancel the label.

Extension at the PWE3 Control Planel Signaling extension

The Notification mode is added to the LDP signaling. In this manner, only status is notifiedand the signaling is not cleared unless the configuration is deleted or the signaling protocolis interrupted. This mode reduces packet interaction and signaling overheads, and iscompatible with the original LDP and Martini modes.




Issue 02 (2010-09-24)

l Multi-hop extensionThe multi-hop PW function is added, which extends the network mode.– The multi-hop PW lowers the requirement on the count of LDP connections of the access

equipment, that is, lowers the overheads of the LDP session of the access nodes.– Multi-hop access nodes meet the PW convergence requirement, which facilitates the

network flexibility and is applicable to different levels (access, convergence, and core).l TDM interface extension

Supports more telecommunication low-speed TDM interfaces. The functions of TDMpacket sequencing, and clock extraction and synchronization are added through the controlword (CW) and the forwarding plane Real-time Transport Protocol (RTP).The advantages of the low-speed TDM interfaces are as follows:– The encapsulation type is added to support the encapsulation of low-speed TDMs.– Supports integration of the PSTN, TV, and data networks.– It is a mode to substitute the traditional DDN service.

l Other extensionsOther extensions at the control plane are as follows:– The negotiation mechanism of the fragmentation capability is added to the control plane.– The PW connectivity check, such as the virtual circuit connectivity verification (VCCV)

and PW operation administration and maintenance (OAM), is added, which improvesthe quick convergence capability and reliability of the network.

Extension at the PWE3 Data Planel Real-time information extension.l Clock extraction and time synchronization through the Real-time Transport Protocol

(RTP).l Assurance of the bandwidth, jitter, and delay of telecommunication signals.l Re-transmission of out-of-order packets.

3.6.1.4 PW TemplateA PW template abstracts common attributes of PWs. Hence, you can use the PW templateconveniently for different PWs. Specifically, by using a PW template, you can configure PWswith similar attributes easily.

In order that common attributes extracted from various PWs can be shared by the PWs, the PWtemplate is defined to contain the common attributes of the PWs for convenient extension. Thetemplate can be used for creating a PW in interface mode.

PWs can be bound with the PW template and they can be reset.

The PW template simplifies the configuration of PWs with similar attributes.

Attributes of the PW TemplateThe PW template can be created and specified with certain attributes on the PEs of a PW.Specifying attributes include specifying the address of the remote PW peer, enabling the controlword (CW), enabling the VC connectivity verification (VCCV), specifying the PW tunnelpolicy, and specifying the maximum count of transmission cells. The attributes are optional and



3-69

the operation sequence is not specified. Select the required attributes in actual configuration. Tocheck the connectivity by using the CW mode, you need to enable the CW function first.

To check the PW connectivity, it is recommended to use the PW template to create the PWs forthe equipment along the trail and enable the VCCV (Virtual Circuit Connectivity Verification).

l In CW mode, in the case of pure dynamic PW, enable the VCCV on both U-PEs; in thecase of pure static PW or hybrid PW, enable the VCCV also on the hybrid switching node.

l In MPLS Router Alert mode, enable the VCCV for the PE equipment along the trail.

3.6.1.5 VCCVVirtual circuit connectivity verification (VCCV) is a technology that is used to verify anddiagnose the connectivity of a PW forwarding trail.

VCCV is an end-to-end PW fault detection and diagnosis mechanism. That is, the VCCV is thecontrol channel on which connectivity verification messages are sent between the PW ingressand egress nodes.

The objective of the VCCV is to verify and further diagnose the connectivity of the PWforwarding trail.

The VCCV PING is a tool that help you to manually check the connection status of the virtualcircuit. The VCCV PING is achieved through the extended LSP-PING. The VCCV defines aserial of messages exchanged between PEs to verify the connectivity of the PW. To ensure thatthe packets of the VCCV and data packets in the PW pass through the same trail, the VCCVpackets and the PW packets must have the same encapsulation mode and pass through the sametunnel.

3.6.1.6 Static and Dynamic Hybrid Multi-Hop PWThis topic describes the static and dynamic hybrid multi-hop PW.

Hybrid multi-hop PW refers to a PW with one end being the static PW and the other end beingthe dynamic PW (LDP). Either the static PW or the dynamic PW can have multiple hops. Thestatic and dynamic PWs, however, cannot have multiple hops in interleaved mode.

As shown in Figure 3-15, the PW between U-PE1 and S-PE is a dynamic PW and that betweenU-PE2 and S-PE is a static PW.




Issue 02 (2010-09-24)

Figure 3-15 Network of the static and dynamic hybrid multi-hop PW

CE-A CE-B

U-PE1 U-PE2

S-PEP1 P2

DynamicPW Static PW

3.6.1.7 PW ProtectionTo implement quick data switching, the PW protection mechanism ensures that services can bequickly switched to another PW when one PW fails.

PW RedundancyAs shown in Figure 3-16, CE1 is connected to PE1 through a single link. CE2 is connected toPE2 and PE3 in dual-homing mode.

NOTEPWs between PE equipment must be created by using the LDP signaling.

l Create a PW between PE1 and PE3. This PW is the working PW.l Create a PW between PE1 and PE2. This PW is the protection PW.l Detect faults between CE and PE.l When the active trail CE2- PE3- PE1- CE1 is faulty, the service traffic can be quickly

switched to the standby trail CE2- PE2- PE1- CE1.l After the fault on the active trail CE2- PE3- PE1- CE1 is rectified, the service traffic is

switched to the original trail.



3-71

Figure 3-16 PW redundancy protection

W

P

Working PW

PE1 PE2

PE3

CE1 CE2

CE Symmetrical Access Dual-Homing Protection

As shown in Figure 3-17, CE1 is connected to PE1 and PE2 through the dual-homing mode,and CE1 is connected to PE2 and PE4 through the dual-homing mode.

l Connect CE1 and CE2 to PE.

l Between PE1 and PE3 and between PE2 and PE4, create PWs.

l Trail CE2- PE3- PE1- CE1 and trail CE2- PE4- PE2- CE1 serve as mutual backups for eachother. When a tail is faulty, the service traffic can be quickly switched to the other trail. Bydefault, use trail CE2- PE3- PE1- CE1 as the working trail.

Figure 3-17 CE symmetrical access dual-homing protection

P

W

P

Working PW

Protection PW

CE1 CE2

PE1

PE2

PE3

PE4

Backup Protection

As shown in Figure 3-18, CE1 is connected to PE1 and CE2 is connected to PE2.




Issue 02 (2010-09-24)

l Between PE1 and PE3, create two dynamic PWs.

l The two PWs on trail PE1- PE2 serve as mutual backups. When a trail is faulty, the servicetraffic can be quickly switched to the other trail.

Figure 3-18 Backup protection

Protection PW

Working PW

CE1 CE2

PE1 PE2

PW APS Protection

As shown in Figure 3-19, CE1 is connected to PE1 and CE2 is connected to PE2 and PE3.

l Between PE1 and PE2, create a PW.

l Between PE1 and PE3 and between PE2 and PE3, create PWs.

l When trail CE1- PE1- PE2- CE2 is faulty, the service traffic can be quickly switched tothe protection trail CE1- PE1- PE3- PE2- CE2.

Figure 3-19 PW APS protection

W

P

P

Working PW

Protection PW

CE1 CE2

PE1

PE2

PE3



3-73

3.6.1.8 ATM Cell Transparent TransmissionThis topic describes the ATM cell transparent transmission technology.

DefinitionATM cell transparent transmission is a technology that is used to bear ATM cells on the PWE3virtual circuit.

ObjectiveThe ATM cell transparent transmission uses the PSN network to connect traditional ATMnetwork resources and emulates traditional ATM services on the PSN network. In this case,traditional ATM network services are emulated to the maximum when traversing the PSNnetwork. Therefore, end users can rarely sense any difference and the existing investment ofcustomers and operators are fully utilized in the network integration and construction.

Implementation of the ATM Cell Transparent TransmissionThe objective of the PWE3 is to use the PSN network to connect traditional network resources(ATM/FR/LAN) and provide the emulation of the traditional services on the PSN network. Inthis case, traditional network services are emulated to the maximum when traversing the PSNnetwork. Therefore, end users can rarely sense any difference and the existing investment ofcustomers and operators are fully utilized in the network integration and construction.

By creating P2P tunnels, bearing data packets, cells, and bit streams, Layer 2 emulation serviceon the PSN traverses the public or private PSN. The original services are emulated to themaximum between two PEs that a PW connects.

l Port-based ATM cell transparent transmissionIn this mode, the connection between two remote ATM ports is emulated.The port-based ATM cell transparent transmission can be classified into port-based remoteATM cell transparent transmission and port-based local ATM cell transparent transmission.

l ATM cell transparent transmission in 1-to-1 virtual circuit connection (VCC) modeIn this mode, a PW bears an ATM VCC cell. This mode supports all ATM adaptation layer(AAL) types. Because a PW bears only one ATM VCC cell, the tunnel packet does notcontain the values of virtual path identifier (VPI) or virtual channel identifier (VCI).In addition, the permanent virtual circuits (PVCs) for the PEs are mapped through the PW,that is, the MPLS PW functions as the ATM switch to support the VPI/VCI switchingwithout configuring the switching relation on the PE. The ATM cell transparenttransmission in 1-to-1 VCC mode can be classified into remote ATM cell transparenttransmission in 1-to-1 VCC mode and local ATM cell transparent transmission in 1-to-1VCC mode.

l ATM cell transparent transmission in N-to-1 VCC modeIn this mode, a PW bears multiple ATM VCC cells. This mode supports all AAL types.Because a PW bears multiple ATM VCC cells, the tunnel packet contains the values ofVPI and VCI.This encapsulation mode supports the function of mapping multiple VCs in the same ATMsub-interface to a PW, and does not support the function of mapping multiple VCs indifferent ATM interfaces to a PW or the function of mapping multiple inter-board VCs toa PW.




Issue 02 (2010-09-24)

The ATM cell transparent transmission in N-to-1 VCC mode can be classified into remoteATM cell transparent transmission in N-to-1 VCC mode and local ATM cell transparenttransmission in N-to-1 VCC mode.

l ATM cell transparent transmission in 1-to-1 virtual path connection (VPC) modeIn this mode, a PW bears an ATM VPC cell. This mode supports all AAL types. Comparedwith the ATM cell transparent transmission in 1-to-1 VCC mode, the tunnel packet of thismode contains only the value of VCI. The output equipment then determines the destinationCE based on the value of VCI.Because a PW bears only one ATM VPC cell, the PVCs for the PEs are mapped throughthe PW, that is, the MPLS PW functions as the ATM switch to support the VPI switchingwithout configuring the switching relation on the PE.The ATM cell transparent transmission in 1-to-1 VPC mode can be classified into remoteATM cell transparent transmission in 1-to-1 VPC mode and local ATM cell transparenttransmission in 1-to-1 VPC mode.

l ATM cell transparent transmission in N-to-1 VPC modeIn this mode, a PW bears multiple ATM VPC cells. This mode supports all AAL types.Because a PW bears multiple ATM VPC cells, the tunnel packet contains the value of VPIand VCI. The encapsulation modes of the ATM cell transparent transmission in N-to-1VPC and N-to-1 VCC modes are the same.The ATM cell transparent transmission in N-to-1 VPC mode can be classified into remoteATM cell transparent transmission in N-to-1 VPC mode and local ATM cell transparenttransmission in N-to-1 VPC mode.

Encapsulation Modes of the ATM Cell Transparent TransmissionThe ATM cell transparent transmission covers the following transparent transmission services:

l PVC-based transparent transmission servicel Permanent virtual path (PVP)-based transparent transmission servicel Interface-based transparent transmission service

The encapsulation modes of the ATM cell transparent transmission are as follows:

l 1-to-1l N-to-1

The ATM cell transparent transmission has the following transparent transmission modes:

l Celll Frame

Table 3-10 describes the features of the ATM cell transparent transmission services of differentlevels.



3-75

Table 3-10 Features of the ATM cell transparent transmission services

Encapsulation Mode

TransparentTransmissionMode

AAL Type SupportedConnectionType

Encapsulation Method

N-to-1 VCC Cell All AALs VC Contains the VPI and VCI.The control word (CW) isoptional. Supports the VPI/VCI switching.

1-to-1 VCC Cell All AALs VC Not contain the VPI or VCI.The CW is mandatory.Supports the VPI/VCIswitching.

N-to-1 VPC Cell All AALs VP Contains the VPI and VCI.The CW is optional.

1-to-1 VPC Cell All AALs VP Contains the VPI and notcontain the VCI. The CW ismandatory.

Interfacetransparenttransmission

Cell All AALs Interface Contains the VPI and VCI.The CW is optional.

Table 3-11 describes the applicable scenarios of various connection types.

Table 3-11 Applicable scenarios of various connection types

Connection Type Applicable Scenario

VCC cell transparenttransmission

Virtual channel connection, which is a basic unit on the ATMnetwork.Applicable to transmission of various ATM network services.

VPC cell transparenttransmission

Virtual path connection, a group of VCCs with the same destination.Applicable to transmission of various ATM network services,especially when multiple services with the same destination exist inthe transmission direction. The VPC cell transparent transmission isquicker and easier for management and configuration than VCC celltransparent transmission.

Whole porttransparenttransmission

Applicable to the scenario that the VP and VC do not need to beprocessed and the equipment functions an ATM transmission privateline.

Table 3-12 describes the comparison between 1-to-1 and N-to-1 modes.




Issue 02 (2010-09-24)

Table 3-12 Comparison between 1-to-1 and N-to-1 modes

Mode Description Applicable Scope Difference

1-to-1 A VCC or VPC maps one PW. All AAL types The VPI and VCI are notcontained.

N-to-1 Multiple VCCs or VPCs mapone PW. (N >= 1)

All AAL types The VPI and VCI mustbe contained in theencapsulation regardlesswhether N = 1 or N > 1.

3.6.1.9 The Application of PWE3 ServiceThis topic describes a typical application of the PWE3.

As an end-to-end Layer 2 service transmission technology, the PWE3 provides end-to-endvirtual emulation links on edges of packet switched networks (PSNs) for transmitting variousservices (ATM, Ethernet, and CES) on PSN networks. Such a technology can interconnect thetraditional network and PSN to share resources and expand the network.

Figure 3-20 Application of the PWE3

BTS

RNC

PEPE

PE

Node B

CE

CE

AC

AC

PW1

PW2 PW3

CE

CE

CE

BSCBITS

E1 interface

IMA E1interface

FE interface

NMS

CE



3-77

Figure 3-20 shows a PWE3 single-hop mobile carrier network. On this network, the followingtypes of services are transmitted:

l BTS is connected to the PSN network through the E1 interface and TDM signals aretransmitted to the BSC by using CES services.

l Node B is connected to the PSN network through the IMA E1 interface and ATM cells aretransmitted to the RNC by using ATM services.

l Node B is connected to the PSN network through the FE interface and Ethernet packets aretransmitted to the NMS by using Ethernet services.

All the preceding services are emulated by using the PWE3 technology and transmitted on PSNnetworks. By using the PWE3 technology, carriers can smoothly migrate original access schemesto PSN networks. This helps to reduce repeated network constructions and lower OPEX.

3.6.2 PWE3 Configuration ProcessThe configuration process of the PWE3 consists of configure the CES services, ATM services,IP line service and Ethernet services. This section describes the operation tasks for configuringthe services, and relations between the tasks. When configure and managing the PWE3 service,follow the configuration process.

CES Service Configuration Process

Figure 3-21 shows the recommended configuration process for configuring and managing aCES service.

Figure 3-21 CES service configuration process


StartRequired

Optional

End

Set the NE LSR ID

Configure Control Plane

Configure Tunnel

Configure CES Service

Create a Network




Issue 02 (2010-09-24)

Table 3-13 Tasks for configuring a CES service

Operation Description

1. Create a network Complete creating the NE, configure the NE data, and creating fibers.

2. Set the NE LSRID

Specifies the LSR ID for each NE that a service traverses and the startvalue of the global label space. Each LSR ID is unique on a network.

3. Configure thenetwork-sideinterface

Set the basic attributes and Layer 3 attributes (such as tunnel enablingstatus and IP address) for the interface to bear tunnels.

4. ConfigureControl Plane

Set the associated protocol parameters of the control plane for creatingtunnels.l To create the static MPLS tunnel to bear the CES service, you do

not need to set the associated parameters of the control plane.l To create the dynamic MPLS tunnel to bear the CES service, you

need to set the following parameters:1. IGP-ISIS protocol parameters2. MPLS-RSVP protocol parametersTo create the dynamic PW to bear services, you need to set the IGP-ISIS and MPLS-LDP protocol parameters.

l To create the IP tunnel or GRE tunnel to bear the CES service, youneed to add a static route.

5. Configure Tunnel The tunnel is used to bear services.l In the case of the static MPLS tunnel, you can create the tunnel in

either NE or trail mode. Select the signaling type as static and setthe relevant information about the tunnel, including the tunnel ID,service name, ingress node, egress node, and transit node.

l In the case of the dynamic MPLS tunnel, you need to select thesignaling type as dynamic and set the relevant information aboutthe tunnel, including service name, and sink and source nodes ofthe tunnel.

l In the case of the IP tunnel or GRE tunnel, set the source board,source port, and IP address of the sink port.

6. Configure theservice interface

Use the CD1 board or tributary card to access the base station services.

7. Configure CESService

1. Create the CES service, including setting the service ID and servicename.

2. Set the source and sink information, including setting the board andchannel.

3. Configure the PW, including setting the PW type, label, and tunneltype.

4. Configure the advanced attributes, including setting the jitter buffertime, packet loading time, and clock mode.



3-79

ATM Service Configuration ProcessFigure 3-22 shows the flowchart for configuring an ATM service. For details of each step, seethe relevant section.

Figure 3-22 ATM service configuration process

Create Network

Configure the ATM Interface

Configure the control plane

Configure the UNIs-NNI ATM service

StartRequired

End

Configure the ATM Policy

Configure Tunnel

Optional


Configure the LSR ID

Table 3-14 Tasks for configuring an ATM service


1. Create Network Complete creating the NE, configure the NE data, and creating fibers.

2. Configure theLSR ID

Specifies the LSR ID for each NE that a service traverses and the startvalue of the global label space. Each LSR ID is unique on a network.




Issue 02 (2010-09-24)


3. Configure thenetwork-sideinterface

Set the basic attributes and Layer 3 attributes (such as tunnel enablingstatus and IP address) for the interface to bear tunnels.

4. Configure thecontrol plane

Set the associated protocol parameters of the control plane for creatingtunnels.l To create the static MPLS tunnel to bear the ATM service, you do

not need to set the associated parameters of the control plane.l To create the dynamic MPLS tunnel to bear the ATM service, you

need to set the following parameters:1. IGP-ISIS protocol parameters2. MPLS-RSVP protocol parametersTo create the dynamic PW to bear the service, you need to set theIGP-ISIS and MPLS-LDP protocol parameters.

l To create the IP tunnel or GRE tunnel to bear the ATM service, youneed to add a static route.

5. ConfigureTunnel

The tunnel is used to bear services.l In the case of the static MPLS tunnel, you can create the tunnel in

either NE or trail mode. Select the signaling type as static and set therelevant information about the tunnel, including the tunnel ID,service name, ingress node, egress node, and transit node.

l In the case of the dynamic MPLS tunnel, you need to select thesignaling type as dynamic and set the relevant information about thetunnel, including service name, and sink and source nodes of thetunnel.

l In the case of the IP tunnel or GRE tunnel, set the source board, sourceport, and IP address of the sink port.

6. Configure theATM Policy

The ATM policy is used to perform the traffic management on the ATMservice.

7. Configure theATM interface

The ATM interface is used to access the base station services.

8. Configure theUNIs-NNI ATMservice

1. Create the ATM service, including setting the service ID and servicename, and selecting the service type and connection type.

2. Configure the connection, including setting the source information,PW ID, sink information, and policy.

3. Configure the PW, including setting the PW type, label, and tunneltype.

4. Configure the CoS mapping and CoS policy of the PW.

IP Line Service Configuration FlowFigure 3-23 shows the recommended flow for configuring an IP line service.



3-81

Figure 3-23 Flow of configuring an IP line service

Create a network

Configure interfaces

Configure an IP line service

Configure a QoS policy

StartMandatory

Optional

End

Configure a Layer 3 virtual interface

Create a static MPLS tunnel

Table 3-15 Operation tasks for configuring an IP line service

Task Remarks

1. Create a network. Create NEs and fibers, and configure NE data.

2. Configureinterface.

l Configure a UNI port, which is used from service access from abase station.

l Configure an NNI port. That is, set the general attributes and Layer3 attributes (such as Enable Tunnel and IP Address) for the portso that the port can carry tunnels.

3. Configure a Layer3 virtual interface.

Configure a Layer 3 virtual interface as the sink port for the IP lineservice.

4. Configure a staticMPLS tunnel.

An IP line service can be carried only by a static MPLS tunnel.l You can create a static MPLS tunnel site by site or end to end. When

creating a static MPLS tunnel, you need to set the signaling type tostatic and specify the service name, ingress node, egress node, andtransit node.




Issue 02 (2010-09-24)

Task Remarks

5. Configure an IPline service.

1. Create an IP line service. That is, set the service ID and specify theservice name.

2. Set the source and sink. That is, choose boards and a tunnel.3. Configure a PW. That is, set the PW type, PW label, and tunnel

type.4. Set advanced attributes. That is, set parameters such as QoS for the

UNI port.

3.6.3 PWE3 Operation TasksThis topic describes all operation tasks relevant to a PWE3 service.

3.6.3.1 Creating a CES ServiceThis topic describes how to create a CES service. You can create a CES PWE3 service tunnelfor transmitting TDM signals in trail configuration mode. By using the trail configuration mode,you can directly configure the source and sink nodes of a CES service and the PW attributes onthe GUI of the U2000. In this manner, the CES service can be created quickly.

3.6.3.2 Creating an ETH ServiceThis topic describes how to create an ETH service. The service is connected to the user side,and transmitted to one PW at the network side. In this manner, user data can be transparentlytransmitted in a point-to-point manner. By using the trail configuration mode, you can directlyconfigure the source and sink nodes of an ETH service and the PW attributes on the GUI of theU2000. In this manner, the ETH service can be created quickly.

3.6.3.3 Creating an ATM ServiceThis topic describes how to create an ATM service. You can create an ATM PWE3 servicetunnel for transmitting ATM signals in trail configuration mode. By using the trail configurationmode, you can directly configure the source and sink nodes of an ATM service and the PWattributes on the GUI of the U2000. In this manner, the ATM service can be created quickly.

3.6.3.4 Creating a PWE3 Service Through DuplicationThis topic describes how to create a PWE3 service through duplication. You can duplicate aPWE3 service and change certain parameters to create another PWE3 service.

3.6.3.5 Deploying a PWE3 ServiceThis topic describes how to deploy a PWE3 service. When you deploy a PWE3 service, theservice is applied from the U2000 to NEs.

3.6.3.6 Adjusting a Discrete PWE3 ServiceThis topic describes how to adjust a discrete PWE3 service. The U2000 searches out all discreteservices on the network automatically. Then, the U2000 converts these services to unterminatedservices or delete these services.

3.6.3.1 Creating a CES ServiceThis topic describes how to create a CES service. You can create a CES PWE3 service tunnelfor transmitting TDM signals in trail configuration mode. By using the trail configuration mode,you can directly configure the source and sink nodes of a CES service and the PW attributes onthe GUI of the U2000. In this manner, the CES service can be created quickly.



3-83


l The DCN function must be disabled for the port that carries the CES service.

l The CES service interface must be configured. Specifically, the interface mode must beconfigured to Layer 1 and the frame format and frame mode of the interface must beconfigured.

l If the service need be carried by an MPLS Tunnel, you must configure a tunnel first..

l To create the dynamic PW to bear the service, you need to set the IGP-ISIS and MPLS-LDP protocol parameters.

Context

When the interface is used to carry the CES service, you need to set the frame format, to ensurethat the frame format is the same as the service encapsulation format. When the emulation modeof a CES service is CESoPSN, it is recommended that you set the frame format at the interfaceto CRC-4 multiframe. When the emulation mode of a CES service is SATop, the frame formatat the interface should be set to non-framing.

When the UNI interface is used to carry the CES service, you need to set the frame mode.

Procedure

Step 1 Choose Service > PWE3 Service > Create PWE3 Service from the main menu.

Step 2 Set the parameters on the General Attributes tab page.

NOTE

l You can use a template to configure a service. Specifically, you can select a template in the Servicetemplate field. Alternatively, you can create another template.

l Set Service Type to CES.

Step 3 Selects the source and sink NEs for a service.

1. Click Configure Source And Sink. A dialog box is displayed.

2. Select a source NE from Physical Topology on the left. Then, the selected NE is displayedin the upper-right pane.

3. In the right portion of NE Panel, all slots and available cards of the NE are displayed.According to the service type to be created, select the appropriate card.

4. Select an interface.




Issue 02 (2010-09-24)

5. Set the SAI attribute of the CES service in the SAI configuration. After you complete thesetting, click Add Node, In the lower portion of the window, the new source and sink NEsare displayed,click OK.

NOTE

The configuration method is the same for the sink NE and source NE. Hence, only the example forconfiguring a source NE is provided as follows.

In the dialog box for configuring the source and sink, you can select multiple lower order timeslots andcreate CES services in batches.

Step 4 Optional: Click Configure Source And Sink,select the Unterminated on the left,specify theLSR ID of unterminated node and click Add Node,In the lower portion of the window, theunterminated source and sink NEs are displayed, click OK.

NOTE

On a network, if the equipment at one end of a service can be managed by the U2000, and the equipmentat the other end of the service is from another vendor and cannot be managed by the U2000, selectUnterminated to set the LSR ID of the opposite end of the service.

Currently, the RTN equipment in the same management domain can be used to configure unterminatedtrails.

If Protection Type is PW backup protection or PW APS protection, the unterminated node cannot beset.

Step 5 Set parameters for the source and sink NEs that are displayed in Node List. To view the topologyof a configured service, click the Service Topology tab in the upper-right area.

Step 6 In the PW pane in lower left portion of the window, configure parameters. Configure generalattributes of the PW.

NOTE

l The PW ID can be automatically allocated.

l You can set Signaling Type to Dynamic or Static. If you set Signaling Type to Dynamic, the ForwardLabel and Reverse Label are assigned automatically. If you set Signaling Type to Static, the ForwardLabel and Reverse Label can be assigned automatically or manually.

l You can set Forward Type and Reverse Type to Static Binding or Select policy. If you set ForwardType to Static Binding, you need to manually specify a tunnel in the Forward Tunnel field. If youset Forward Type to Select Policy, you need to set the tunnel priority in the Forward Type field sothat the system selects a tunnel according to the priority.

l You may also set the forward tunnel and reverse tunnel by clicking the Service Topology tab in theupper-right area. Select a tunnel between the source NE and sink NE, right-click, and then chooseSelect Forward Tunnel or Select Reverse Tunnel. In the dialog box that is displayed, select the tunnelfor static binding.

Step 7 Optional: Click Detail. A pane is displayed in the lower-right area.

Step 8 Optional: Click the Advanced PW Attribute tab to set parameters for a PW and set the clockmode of the source and sink NEs.



3-85

NOTE

Generally, Packet Loading Time (us) for packets that carry the CES service is 1 ms.

The value of Jitter Compensation Buffering Time(us) must be greater than the value of Packet LoadingTime (us) at the peer end.


NOTE


l When you select the Deploy and Enable check box, A service is available on NEs only when it isenabled.

----End

3.6.3.2 Creating an ETH Service

This topic describes how to create an ETH service. The service is connected to the user side,and transmitted to one PW at the network side. In this manner, user data can be transparentlytransmitted in a point-to-point manner. By using the trail configuration mode, you can directlyconfigure the source and sink nodes of an ETH service and the PW attributes on the GUI of theU2000. In this manner, the ETH service can be created quickly.

Prerequisitel You must be an NM user with "network operator" authority or higher.l If you need to use the port exclusively, disable the DCN function of the UNI port.l The MPLS tunnel for carrying services must be created if it is used.l To create the dynamic PW to bear the service, you need to set the IGP-ISIS and MPLS-

LDP protocol parameters.

Procedure



NOTE

l You can use a template to configure a service. Specifically, you can select a template in the Servicetemplate field. Alternatively, you can create another template.

l Set Service Type to ETH.




Issue 02 (2010-09-24)

Step 3 Selects the source and sink NEs for a service.

1. Click Configure Source And Sink. A dialog box is displayed.



4. Select an interface.

5. Set the SAI attribute of the Ethernet service in the SAI configuration. After you completethe setting, click Add Node, In the lower portion of the window, the new source and sinkNEs are displayed. Click OK.

NOTE


Step 4 Optional: Click Configure Source And Sink, select the Unterminated on the left, specify theLSR ID of unterminated node, and click Add Node, In the lower portion of the window, theunterminated source and sink NEs are displayed, click OK.

NOTE

On a network, if the equipment at one end of a service can be managed by the U2000, and the equipmentat the other end of the service is from another vendor and cannot be managed by the U2000, selectUnterminated to set the LSR ID of the opposite end of the service.

Currently, the RTN equipment in the same management domain can be used to configure unterminatedtrails.

If Protection Type is PW backup protection or PW APS protection, the unterminated node cannot beset.





3-87

NOTE






Step 8 Optional: Click the SAI QoS tab to view the Local QoS Policy or configure the global templateof SAI. Alternatively, you can select one of the policies that are configured in the Global QoSPolicy Template field.

Step 9 Optional: Click Service Parameter tab to configure the service parameter. If you set BPDUto Transparent Transmission, the MTU(byte) cannot be set.

Step 10 Optional: Click the PW QoS tab to configure the global template of a PW. Alternatively, youcan click Global QoS Policy Template and select the global template of QoS from the drop-down list. Then, set parameters.

Step 11 Optional: Click the Advanced PW Attribute tab to set parameters for a PW. When the PWType is set to Ethernet Tagged Mode, the TPID and Request VLAN is available.


NOTE



----End

3.6.3.3 Creating an ATM ServiceThis topic describes how to create an ATM service. You can create an ATM PWE3 servicetunnel for transmitting ATM signals in trail configuration mode. By using the trail configuration




Issue 02 (2010-09-24)

mode, you can directly configure the source and sink nodes of an ATM service and the PWattributes on the GUI of the U2000. In this manner, the ATM service can be created quickly.

Prerequisitel You must be an NM user with "network operator" authority or higher.l The control plane must be configured.l The interface must be configured. If IMA services are connected, the IMA group must be

configured.l The ATM policy must be configured.l The MPLS tunnel for carrying services must be created if it is used.l To create the dynamic PW to bear the service, you need to set the IGP-ISIS and MPLS-

LDP protocol parameters.

Procedure



NOTE

l You can use a template to configure a service. Specifically, you can select a template in the ServiceTemplate field. Alternatively, you can create another template.

l Set Service Type to ATM.

Step 3 Selects the source and sink NEs for a service.1. Click Configure Source And Sink. A dialog box is displayed.



3-89



4. Select an interface.5. Set the SAI attribute of the ETH service in the SAI configuration. After you complete the

setting, click Add Node, In the lower portion of the window, the new source and sink NEsare displayed,click OK.

6. Configure the sink NE, protection NE and transit NE with the same method and based ondifferent protection types.

7. To configure multiple ATM connections for an ATM service at the same time, selectmultiple ports for an NE by using the same method.

NOTE


Step 4 Optional: Click Configure Source And Sink,select the Unterminated on the left,specify theLSR ID of unterminated node and click Add Node,In the lower portion of the window, theunterminated source and sink NEs are displayed, click OK.

NOTE

On a network, if the equipment at one end of a service can be managed by the U2000, and the equipmentat the other end of the service is from another vendor and cannot be managed by the U2000, selectUnterminated to set the LSR ID of the opposite end of the service.Currently, the RTN equipment in the same management domain can be used to configure unterminatedtrails.If Protection Type is PW backup protection or PW APS protection, the unterminated node cannot beset.






Issue 02 (2010-09-24)

NOTE





Step 7 Click ATM Link. In the dialog box that is displayed, add the ATM connection, and set relevantparameters of the ATM connection.

NOTEAfter you finishing configuring VPI/VCI of the source and sink, the U2000 assigns the transit VPI/VCIautomatically. In the case of a network consisting of RTN equipment, the transit VPI/VCI can be set.Moreover, the transit VPI/VCI can be set be different from the VPI/VCI of the source and sink.


Step 9 Optional: Click the PW QoS tab to configure the global template of a PW. Alternatively, youcan select one of the templates that are configured in the Global QoS Policy Template field,and set parameters.

Step 10 Optional: Click the Advanced PW Attribute tab to set parameters for a PW.


NOTE



----End



3-91

PostrequisiteAfter the service is created successful, the service is displayed in the PWE3 service managementwindow.

3.6.3.4 Creating a PWE3 Service Through Duplication

This topic describes how to create a PWE3 service through duplication. You can duplicate aPWE3 service and change certain parameters to create another PWE3 service.


l PWE3 services that are created successfully must exist.

Context

To create a PWE3 services through duplication, you can specify the source, sink, and transitnodes again, or change certain parameters only.

Procedure

Step 1 Choose Service > PWE3 Service > Manage PWE3 Service from the main menu.

Step 2 Set the query criteria and click Filter.

Step 3 Create a PWE3 service by duplicating either a protected PWE3 service or an unprotected PWE3service.

l Methods of duplicating different protected PWE3 services and the corresponding windowsare similar. The following example describes how to duplicate a PWE3 service with the PWbackup protection.

1. Select a PWE3 service with PW backup protection, right-click, and choose Copy fromthe shortcut menu.

2. In the Copy PWE3 Service window, modify the attributes relevant to the new servicebased on service planning, and click OK.




Issue 02 (2010-09-24)

NOTE

In the Copy PWE3 Service window, all parameters of the original PWE3 service are retained,including parameters of the access ports. You must change an original access port to another idleaccess port before a duplicate service can be created successfully.

l If you want to change the access port to another port of the same NE, change the port directlyin the node list on the left.

l If you want to change the access port to a port of another NE, change the port by any of thetwo methods. Method 1: In the topology view, right-click the NE where the required portresides and choose the corresponding shortcut menu (change source, sink or transit node). Inthe dialog box that is displayed, change the service access port. Method 2: In the node liston the left, delete the corresponding NE. Then configure another NE for the access port.

l Methods of duplicating unprotected Ethernet services, IP E-line services and CES servicesand the corresponding windows are similar. The following example describes how toduplicate a CES service.

1. Select one CES service to be duplicated, right-click, and choose Copy from the shortcutmenu.

2. In the Copy PWE3 Service dialog box, click Add.3. In the Add Service dialog box, set the source and sink nodes, and then click OK.

NOTE

On a network, if the equipment at one end of a service can be managed by the U2000, and theequipment at the other end of the service is from another vendor and cannot be managed by theU2000, select Unterminated to set the LSR ID of the opposite end of the service.

Currently, the RTN equipment in the same management domain can be used to configureunterminated trails.

NOTE

In the Add Service dialog box, you can set multiple source and sink nodes to create thecorresponding services through duplication. Those services can share intermediate NEs. Thefollowing describes the details.

l The mapping between the source and sink NEs is 1:N or N:1. In this case, only one sourcenode exists, and a service is created between the source node and a sink node. In this way,N services are created.

l The mapping between the source and sink NEs is N:N. In this case, a service is createdbetween a source node and the sink node with the same number. For example, a service iscreated between source node 1 and sink node 1 and a service is created between source node2 and sink node 2. In this way, N services are created.

l The mapping between the source and sink NEs is N:M and M is greater than N. In this case,a service is created between the source node whose number is smaller than or equal to N andthe sink node with the same number. For the remaining sink nodes, a service is createdbetween source node N and each remaining sink node. In this way, M services are created.

Select an NE of the same type as the original NE when you select the source, sink, or transit nodefor the duplication.

4. Click Advanced and Modify SAI tabs respectively to modify relevant parameters ofthe service.

5. Click OK.

l The following describes how to duplicate an unprotected ATM service.

1. Configure the general attributes of the service created through duplication. For details,see 3.1 through 3.4.

2. In the Service Parameter area, modify the attributes relevant to the ATM connectionof the new service.



3-93

3. Click Add Link to add an ATM connection to the new service.4. Click OK.

----End

3.6.3.5 Deploying a PWE3 Service

This topic describes how to deploy a PWE3 service. When you deploy a PWE3 service, theservice is applied from the U2000 to NEs.

Prerequisitel You must be an NM user with "network operator" authority or higher.l A PWE3 service must be created.

Procedure


Step 2 In the Set Filter Criteria dialog box that is displayed, set the filter criteria, and click Filter.The NMS displays the PWE3 services that meet the filter criteria.

Step 3 Select one PWE3 service that is configured, right-click, and then choose Deploy from theshortcut menu.

NOTE

l If you deploy a service, the service configuration data is applied to NEs.

l If you do not deploy a service, the service configuration data is saved in the U2000.

l After the service is created successful, in the PWE3 service management window, DeploymentStatus of the service is displayed as Deployed.

----End

Postrequisite

When you need to delete the service, select the service and click Delete, click Yes in the dialogbox displayed.

NOTE

Deleting a service is to delete a service on a per-NE basis and an end-to-end tunnel. When you chooseDelete from Network Side, only the data about end-to-end services is deleted.

3.6.3.6 Adjusting a Discrete PWE3 Service

This topic describes how to adjust a discrete PWE3 service. The U2000 searches out all discreteservices on the network automatically. Then, the U2000 converts these services to unterminatedservices or delete these services.

Prerequisitel You must be an NM user with "network operator" authority or higher.l Discrete services must exist on the network.




Issue 02 (2010-09-24)

ContextNOTE

You cannot convert a discrete service that has no LSR IDs for both the source and sink ends to anunterminated service.

Procedure

Step 1 Choose Service > PWE3 Service > Manage PWE3 Discrete Service from the main menu.

Step 2 Set the query criteria and click Filter.

NOTE

Currently, only the router supports the function of filtering services by port name.

Step 3 Select one or more discrete services, click Convert to Unterminated. Alternatively, right-clickand choose Convert to Unterminated from the shortcut menu.

Step 4 Set the parameters in the dialog box, click OK.

Step 5 In the Confirm dialog box, click OK.

The adjusted discrete PWE3 service is displayed in the service list in the PWE3 ServiceManagement window.

Step 6 Optional: Delete a discrete PWE3 service.

1. Select one or more discrete services, click Delete Discrete. Alternatively, right-click andchoose Delete Discrete rom the shortcut menu.

2. In the Confirm dialog box, click OK.

----End

3.6.4 PWE3 Service MonitoringThe PWE3 service monitoring enables you to view the service topology, monitor serviceperformance, and monitor service alarms.

3.6.4.1 Viewing the PWE3 Service TopologyThis topic describes how to view the PWE3 service topology. By viewing the service topologyof a PWE3 service, you can learn the topology structure and running status of the service in realtime.

3.6.4.2 Monitoring Performance of a PWE3 ServiceThis topic describes how to monitor performance of a PWE3 service. While a PWE3 service isrunning, abnormal status may occur. By viewing the performance data of a PWE3 service, youmay learn the abnormal status in time. In this manner, the maintenance personnel can take timelymeasures to avoid faults.

3.6.4.3 Monitoring Alarms of a PWE3 ServiceThis topic describes how to monitor alarms of a PWE3 service. By creating a service monitoringtemplate, the maintenance personnel can monitor alarms of services that important to customers,and learn the running status of services in real time, thus ensuring the normal running of services.



3-95

3.6.4.1 Viewing the PWE3 Service Topology

This topic describes how to view the PWE3 service topology. By viewing the service topologyof a PWE3 service, you can learn the topology structure and running status of the service in realtime.


l PWE3 services that are created must exist.

Procedure



Step 3 In the service list, select a service to be viewed.

Step 4 View the topology structure of a service.

In the service topology, you can learn PE information of the source and sink ends, and interfaceinformation for connecting to CE.

Step 5 Check alarm information of a service.If a fault occurs, the corresponding interface and PW of the PE in the service topology isdisplayed with fault identifier.

Step 6 You can perform the following operations in the service topology.

l In the service topology, select a PE, right-click, and then choose the following menu itemsfrom the shortcut menu respectively.

– Choose NE Explorer to view the NE Explorer of the equipment.

– Choose View Real-Time Performance to view the real-time performance of the PW.

l In the service topology, select one interface, right-click, and then choose View Real-TimePerformance to view the real-time performance of the interface.

l In the topology view, select a PW between PEs, right-click, and then choose the followingmenu items from the shortcut menu respectively.

– Choose View Real-Time Performance to view the real-time performance of the PW.

– Choose View Tunnel. In the Tunnel Management dialog box that is displayed, viewthe Tunnel information.

----End

3.6.4.2 Monitoring Performance of a PWE3 Service

This topic describes how to monitor performance of a PWE3 service. While a PWE3 service isrunning, abnormal status may occur. By viewing the performance data of a PWE3 service, youmay learn the abnormal status in time. In this manner, the maintenance personnel can take timelymeasures to avoid faults.




Issue 02 (2010-09-24)

Procedure



Step 3 View the runtime performance of a service. Right-click the NE and choose View Real-TimePerformance from the shortcut menu in the topology view.

Step 4 Create a monitoring instance for a service. For details, refer to the chapter of monitoring instancemanagement in Performance Management System (PMS).

Step 5 View the history performance of a service. Right-click a required service and choosePerformance > View History Data from the shortcut menu.

----End

3.6.4.3 Monitoring Alarms of a PWE3 ServiceThis topic describes how to monitor alarms of a PWE3 service. By creating a service monitoringtemplate, the maintenance personnel can monitor alarms of services that important to customers,and learn the running status of services in real time, thus ensuring the normal running of services.

Procedure

Step 1 Choose Fault > Service Monitoring > Service Monitoring Template from the main menu.

Step 2 In the Centralized Monitoring dialog box, expand the All Service branch to view alarminformation of all services.

Step 3 Click Select Monitoring Group.

Step 4 In the Select Monitoring Group dialog box, click Add from the shortcut menu.

Step 5 In the Add Monitoring Group dialog box, enter the name of the monitoring group and clickOK.

The newly-added monitoring group is displayed in the monitoring group list.



3-97

Step 6 Select the monitoring group that is added, right-click, and then choose Add MonitoringService from the shortcut menu.

Step 7 In the Add Monitoring Service dialog box, select the corresponding service tab and select theservice to be added. Then, click Add.

Step 8 Click Close.

----End

3.6.5 Locating a PWE3 Service FaultThis topic describes how to locate a PWE3 service fault.

3.6.5.1 CES Service TroubleshootingThis section describes how to troubleshoot interruption or bit errors of the CES service in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.

3.6.5.2 ATM Service TroubleshootingThis section describes how to troubleshoot interruption or bit errors of the ATM or IMA servicein terms of the symptoms, impact on the system, possible causes, tools required fortroubleshooting, troubleshooting procedure, and precautions that should be taken during thetroubleshooting.

3.6.5.3 Ethernet Service TroubleshootingThis section describes how to troubleshoot Ethernet service interruption or packet loss in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.

3.6.5.1 CES Service Troubleshooting

This section describes how to troubleshoot interruption or bit errors of the CES service in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.




Issue 02 (2010-09-24)

SymptomsThe symptoms of a CES service fault may be as follows. See Table 3-16. Clear up all the reportedalarms and the fault is rectified.

Table 3-16 List of common symptoms of CES service faults

Symptom Alarm Reported Board

The CES service isinterrupted.

HARD_BAD,TEMP_OVER,COMMUN_FAIL, orBUS_ERR

SCA, XCS, or MP1

T_ALOS, UP_E1_AIS, orDOWN_E1_AIS

D75 or D12

R_LOS,LASER_MOD_ERR,LSR_WILL_DIE,IN_PWR_ABN, TEM_HA,or LSR_BCM_ALM

CD1

MPLS_TUNNEL_LOCV EG16 or EX2

PW_DOWM EG16, EX2, or PM1

The CES service has biterrors and thecommunication is degraded.

HARD_BAD,TEMP_OVER, orBUS_ERR

SCA, XCS, or MP1

SYNC_C_LOS or LTI XCS

LASER_MOD_ERR,LSR_WILL_DIE,IN_PWR_ABN, TEM_HA,or LSR_BCM_ALM

CD1

CES_LOSPKT_EXC,CES_MISORDERPKT_EXC, CES_STRAYPKT_EXC,CES_JTRUDR_EXC, orCES_JTROVR_EXC

MD1, MQ1, or CD1

Troubleshooting FlowchartFigure 3-24 shows the flowchart for troubleshooting CES service faults.



3-99

Figure 3-24 Flowchart for troubleshooting CES service faults

Start

Whether HARD_BAD, TEMP_OVER,

BUS_ERR, or COMMUN_FAIL alarm exists?

Whether T_ALOS, R_LOS, orLASER_MOD_ERR

alarm exists?

Whether MPLS_TUNNEL_LOCV

or PW_DOWN alarm exists?

Rectify fault of physical link

Whether SYNC_C_LOS or LTI

alarm exists?Rectify clock fault

WhetherCES_LOSPKT_EXC, CES_JTRUDR_EXC

alarm exists?

Check fiber, opticalmodule, and connections,

and handle problems

Whether faultis rectified?

EndContact Huawei technical support engineers

Reset/re-insert/replace board

Check fiber, optical module, and network

cable, and handle problems

Yes

Rectify fault of opposite equipment

Reset/re-insert/replace cross-connect board

Modify network configuration

Yes

Yes

Yes

Yes

No

No

No

No

No

No

No

No

Yes

Board is faulty or inter-board communication

fails

Signals are lost or degradeed

Tunnel or PW which carries service is faulty

Synchronous clock is lost

Lost packets, errored packets, or jitter

crosses threshold


No

Impact on the System

The CES service in the network has bit errors or is interrupted. As a result, the communicationis degraded or interrupted. If the CES service fault is caused by the SCA or XCS board, otherservices accessed by the equipment may also be affected.

Possible Causes

As shown in the troubleshooting flowchart, a CES service fault may be due to the followingcauses:

l Cause 1: The board has a hardware fault or excessively high temperature, or the inter-boardcommunication fails. As a result, the board does not work normally.

l Cause 2: The signals accessed by the processing board or interface board are lost ordegraded.

l Cause 3: The tunnel or PW that carries the CES service is interrupted.

l Cause 4: The priority of the synchronous clock source or the synchronous clock sourceitself is lost.




Issue 02 (2010-09-24)

l Cause 5: The number of lost packets or erorred packets, or the jitter buffer of the CESservice over the PW crosses the threshold.

Procedurel Cause 1: The board has a hardware fault or excessively high temperature, or the inter-board

communication fails. As a result, the board does not work normally.

1. Query the current alarms of the system to check for the HARD_BAD, TEMP_OVER,COMMUN_FAIL, or BUS_ERR alarm and determine which board reports the alarm.

2. Handle theHARD_BAD, TEMP_OVER, COMMUN_FAIL, or BUS_ERR alarm.

l Cause 2: The signals accessed by the processing board or interface board are lost ordegraded.

1. Check for the T_ALOS, UP_E1_AIS, or DOWN_E1_AIS alarm of the system andhandle the T_ALOS, UP_E1_AIS, or DOWN_E1_AIS alarm.

2. Check for the R_LOS alarm of the system and handle the R_LOS alarm.

3. Check for the LASER_MOD_ERR, LSR_WILL_DIE, IN_PWR_ABN, TEM_HA,or LSR_BCM_ALM alarm of the system and handle the LASER_MOD_ERR,LSR_WILL_DIE, IN_PWR_ABN, TEM_HA, or LSR_BCM_ALM alarm.

l Cause 3: The tunnel or PW that carries the CES service is interrupted.

1. Check for the MPLS_TUNNEL_LOCV alarm of the system and handle theMPLS_TUNNEL_LOCV alarm.

2. Check for the PW_DOWN alarm of the system and handle the PW_DOWN alarm.

l Cause 4: The priority of the synchronous clock source or the synchronous clock sourceitself is lost.

1. Check for the SYNC_C_LOS or LTI alarm of the system and handle theSYNC_C_LOS or LTI alarm.

l Cause 5: The number of lost packets or erorred packets, or the jitter buffer of the CESservice over the PW crosses the threshold.

1. Check for the CES_LOSPKT_EXC, CES_MISORDERPKT_EXC, orCES_STRAYPKT_EXC alarm of the system and handle the CES_LOSPKT_EXC,CES_MISORDERPKT_EXC, or CES_STRAYPKT_EXC alarm.

2. Check for the CES_JTRUDR_EXC, or CES_JTROVR_EXC alarm of the system andhandle the CES_JTRUDR_EXC, or CES_JTROVR_EXC alarm.

----End

3.6.5.2 ATM Service Troubleshooting

This section describes how to troubleshoot interruption or bit errors of the ATM or IMA servicein terms of the symptoms, impact on the system, possible causes, tools required fortroubleshooting, troubleshooting procedure, and precautions that should be taken during thetroubleshooting.

Symptoms

The symptoms of ATM or IMA service faults may be as follows:

See Table 3-17. Clear up all the reported alarms and the fault is rectified.



3-101

Table 3-17 List of common symptoms of ATM service faults


The ATM or IMA service isinterrupted.


SCA, XCS, or MP1

R_LOS or ALM_ALS AD1, AFO1, or CD1

VC_AIS or VP_AIS AD1 or AFO1

IMA_GROUP_LE_DOWNorIMA_GROUP_RE_DOWN

MQ1, CD1, or MD1

The IMA service has biterrors or loses packets.


SCA, XCS, or MP1

ALM_IMA_RFI,ALM_IMA_LIF,ALM_IMA_RE_RX_UN-USABLE, orALM_IMA_RE_TX_UN-USABLE

D12, D75, or CD1

Troubleshooting FlowchartFigure 3-25 shows the flowchart for troubleshooting ATM service faults.




Issue 02 (2010-09-24)

Figure 3-25 Flowchart for troubleshooting ATM service faults

Start



Whether R_LOS alarm

exists?

Whether ALM_ALS alarm

exists?Re-set laser

Whether VC_AIS or VP_AIS

alarm exists?

Rectify fault of upstream NE

WhetherIMA_GROUP_LE_DOWN

or IMA_GROUP_RE_DOWNalarm exists?

Enable the IMA protocol

Whether fault is rectified?



Check fiber, optical module, and network cable,

and handle problems

Yes


Modify the IMAlink configuration

Yes

Yes

Yes

Yes

No

No

No

No

No

No

No

Yes

Board is faulty or inter-board communication fails

Received signals are lost

Laser shutdown is set

Upstream service is interrupted

IMA protocol is not enabled


No

Impact on the SystemThe ATM service in the network is interrupted, has bit errors, or loses packets. If the fault iscaused by the SCA, XCS board, other services accessed by the equipment may also be affected.

Possible CausesAs shown in the troubleshooting flowchart, an ATM service fault may be due to the followingcauses:

l Cause 1: The board has a hardware fault or excessively high temperature, or the inter-boardcommunication fails. As a result, the board does not work normally.

l Cause 2: The signals on the receive side of the interface board are lost.l Cause 3: The laser is automatically shut down.l Cause 4: The VC and VP connections are abnormal and the upstream ATM service is

interrupted.l Cause 5: The IMA group attributes are incorrect on the two ends of the link. As a result,

the local and remote ends mis-step in receiving IMA frames, and the remote IMA linkabnormally transmits and receives signals.



3-103


communication fails. As a result, the board does not work normally.1. Query the current alarms of the system to check for the HARD_BAD, TEMP_OVER,

COMMUN_FAIL, or BUS_ERR alarm and the board that reports the alarm.2. Handle the HARD_BAD, TEMP_OVER, COMMUN_FAIL, or BUS_ERR alarm.

l Cause 2: The signals on the receive side of the interface board are lost.1. Check for the R_LOS alarm of the system and handle the R_LOS alarm.

l Cause 3: The laser is automatically shut down.1. Check for the ALM_ALS alarm of the system and handle the ALM_ALS alarm.

l Cause 4: The VC or VP connections are abnormal, or the upstream ATM service isinterrupted.1. Check for the VC_AIS or VP_AIS alarm of the system and handle the VC_AIS or

VP_AIS alarm.l Cause 5: The IMA group attributes are incorrect on the two ends of the link. As a result,

the local and remote ends mis-step in receiving IMA frames, and the remote IMA linkabnormally transmits and receives signals.1. Check for the ALM_IMA_RFI or ALM_IMA_LIF alarm of the system and handle

the ALM_IMA_RFI or ALM_IMA_LIF alarm.2. Check for the ALM_IMA_RE_RX_UNUSABLE or

ALM_IMA_RE_TX_UNUSABLE alarm of the system and handle theALM_IMA_RE_RX_UNUSABLE or ALM_IMA_RE_TX_UNUSABLE alarm.

----End

3.6.5.3 Ethernet Service TroubleshootingThis section describes how to troubleshoot Ethernet service interruption or packet loss in termsof the symptoms, impact on the system, possible causes, tools required for troubleshooting,troubleshooting procedure, and precautions that should be taken during the troubleshooting.

SymptomsThe symptoms of Ethernet service faults may be as follows. See Table 3-18. Clear up all thereported alarms and the fault is rectified.

Table 3-18 List of common symptoms of Ethernet service faults


The Ethernet service isinterrupted.


SCA, XCS, EG16, or EX2

ETH_LOS,ETH_AUTO_LINK_DOWN, or MAC_FCS_EXC

EG16, EX2, ETFC, EFG2, orEFF8

R_LOS POD41




Issue 02 (2010-09-24)


ETH_LINK_DOWN EG16, EX2, EFG2, or EFF8

LOOP_ALM EG16, EX2, ETFC, EFG2,EFF8, or POD41

ETH_EFM_LOOPBACK EG16, EX2, ETFC, EFG2, orEFF8

LASER_SHUT orLSR_WILL_DIE

EG16, EX2, EFG2, EFF8, orPOD41

The Ethernet service losespackets or has erorredpackets.


SCA, XCS, EG16, or EX2

LSR_WILL_DIE EG16, EX2, EFG2, EFF8, orPOD41

MAC_FCS_EXC orFLOW_OVER

EG16, EX2, ETFC, EFF8, orEFG2

ETH_CFM_UNEXPERI EG16 or EX2

Troubleshooting FlowchartFigure 3-26 shows the flowchart for troubleshooting Ethernet service faults.



3-105

Figure 3-26 Flowchart for troubleshooting Ethernet service faults

Start



Whether ETH_LOS, R_LOS, or MAC_FCS_EXC alarm

exists?

Whether ETH_LINK_DOWN alarm

exists?

Modify port configuration, including port attributes

and working mode

Whether LOOP_ALM or

ETH_EFM_LOOPBACKalarm exists?

Modify port loopback configuration

WhetherFLOW_OVER or

ETH_CFM_UNEXPERIalarm exists?

Modify service configuration

Whether fault is rectified?



Check fiber, optical module, and network cable,

and handle problems

Yes


Yes

Yes

Yes

Yes

No

No

No

No

No

No

Yes

Board is faulty or inter-board communication fails

Signals are lost or degraded

Port negotiation fails

Port loopback is set

Service configuration is incorrect


communication fails. As a result, the board does not work normally.

1. Query the current alarms of the system to check for the HARD_BAD, TEMP_OVER,COMMUN_FAIL, or BUS_ERR alarm and the board that reports the alarm.

2. Handle the HARD_BAD, TEMP_OVER, COMMUN_FAIL, or BUS_ERR alarm.

l Cause 2: The signals on the receive side are lost.

1. Check for the ETH_LOS or ETH_AUTO_LINK_DOWN alarm of the system andhandle the ETH_LOS or ETH_AUTO_LINK_DOWN alarm.

2. Check for the R_LOS alarm of the system and handle the R_LOS alarm.

3. Check for the LASER_SHUT or LSR_WILL_DIE alarm of the system and handlethe LASER_SHUT or LSR_WILL_DIE alarm.

4. Check for the MAC_FCS_EXC alarm of the system and handle the MAC_FCS_EXCalarm.

l Cause 3: The Ethernet port is misconnected and the port negotiation fails.




Issue 02 (2010-09-24)

1. Check for the ETH_LINK_DOWN alarm of the system and handle theETH_LINK_DOWN alarm.

l Cause 4: Loopback is configured for the port.1. Check for the LOOP_ALM alarm of the system and handle the LOOP_ALM alarm.2. Check for the ETH_EFM_LOOPBACK alarm of the system and handle the

ETH_EFM_LOOPBACK alarm.l Cause 5: The configured traffic limit is excessively low at the port and configurations of

the source and sink ports are inconsistent.1. Check for the FLOW_OVER alarm of the system and handle the FLOW_OVER

alarm.2. Check for the ETH_CFM_UNEXPERI alarm of the system and handle the

ETH_CFM_UNEXPERI alarm.

----End

3.6.6 Example for Configuring a CES Emulation ServiceThis topic describes the example of configuring a CES emulation service. Specifically, theexample description, service planning, and configuration process are provided.



3.6.6.3 Configuration ProcessThis topic describes how to configure a CES emulation service.


Between BTS and BSC, the CES service is transported through the RTN equipment, as shownin Figure 3-27.

Figure 3-27 Networking diagram of the CES service


NE2

BTS

BTS

BSCNE3



3-107

Between BTS and NE2, two CES services are configured. All the timeslots of one E1 areoccupied, and timeslots 1-14 and 20 of another E1 are occupied. Between BTS and NE1, theservice is configured through one E1 interface. All the timeslots of the E1 are occupied.



Service Port Planning

Table 3-19 Service port planning

Service Source NE Sink NE

E1 Port Microwave Port Microwave Port E1 Port

NE2-NE3 (TheE1 timeslots arefully occupied.)

3-ML1-1 4-IFE2-1 4-IFE2-1 3-ML1-1

NE2-NE3 (TheE1 timeslots arepartiallyoccupied.)

3-ML1-2 4-IFE2-1 4-IFE2-1 3-ML1-2

NE1-NE3 (TheE1 timeslots arefully occupied.)

3-ML1-1 4-IFE2-1 2-IFE2-1 3-ML1-3

Service Planning

Table 3-20 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots arepartially occupied.)

Attribute Value Value

Station NE2 NE3

Level E1 E1

Service ID 4 4

Service Name CES Remote Service 1 CES Remote Service 1

Mode UNI-NNI UNI-NNI

Protection Type No Protection No Protection

Source Board 3-ML1 -

Source Port 3-ML1-2(Port-2) -




Issue 02 (2010-09-24)


Source 64k timeslot 1-14,20 1-14,20

Source High-order timeslot - -

Source Low-order timeslot - -

PW ID 8 8

Forward Tunnel Working Tunnel-Forward(Tunnel-0100)

Working Tunnel-Forward(Tunnel-0100)

Reverse Tunnel Working Tunnel-Reverse(Tunnel-0101)

Working Tunnel-Reverse(Tunnel-0101)

Sink Board - 3-ML1

Sink Port - 3-ML1-2(Port-2)

Sink 64k timeslot 1-14,20 1-14,20

Sink High-order timeslot - -

Sink Low-order timeslot - -

Signaling Type Static Static

PW Type CESoPSN CESoPSN

Forward Label 36 36

Reverse Label 36 36

Peer IP 10.10.10.3 10.10.10.2

RTP Header Disabled Disabled

Jitter CompensationBuffering Time(us)

5000 5000

Packet Loading Time (us) 1000 1000

Clock Mode Null Null

EXP 4 4

Table 3-21 Parameters for configuring the CES service: NE2-NE3 (The E1 timeslots are fullyoccupied.)


Station NE2 NE3

Level E1 E1

Service ID 5 5



3-109







PW ID 9 9





Sink Board - 3-ML1



PW Type SAToP SAToP

Forward Label 37 37

Reverse Label 37 37

Peer IP 10.10.10.3 10.10.10.2



5000 5000



EXP 4 4

Table 3-22 Parameters for configuring the CES service: NE1-NE3 (The E1 timeslots are fullyoccupied.)


Station NE1 NE3

Level E1 E1

Service ID 6 6





Issue 02 (2010-09-24)






PW ID 9 9





Sink Board - 3-ML1



PW Type SAToP SAToP

Forward Label 35 35

Reverse Label 35 35

Peer IP 10.10.10.3 10.10.10.1



5000 5000



EXP 4 4

3.6.6.3 Configuration Process

This topic describes how to configure a CES emulation service.

Prerequisite

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

You must learn about the networking requirements and service planning described in theexample.

The network must be created.

Tunnel 2 exists between NE1 and NE3. And Tunnel 1 exists between NE2 and NE3.



3-111

Context

When the interface is used to carry the CES service, you need to set the frame format, to ensurethat the frame format is the same as the service encapsulation format. When the emulation modeof a CES service is CESoPSN, it is recommended that you set the frame format at the interfaceto CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame formatat the interface should be set to non-framing.

When the UNI interface is used to carry the CES service, you need to set the frame mode. TheFrame Mode of the PDH port packets of theRTN support 30 and 31 timeslots. In a mixednetworking, ensure that the frame mode of the local port is the same as that of the peer port.l 30 timeslots: The 1-15 and 17-31 timeslots in the E1 frame format are used to transmit

service data.l 31 timeslots: The 31 timeslots in the E1 frame format are used to transmit service data.

Procedure






3. Display the NE Explorer of NE2, and NE3 separately and perform the preceding two steps

to set the parameters, such as LSR ID.


LSR ID NE2: 1.0.0.2NE3: 1.0.0.3






Issue 02 (2010-09-24)

Step 2 Configure the tunnel that carries the CES service. For details of the configuration, see 3.3.5.3Configuration Process (Creating a Static CR Tunnel) or 3.3.6.3 Configuration Process(Creating a RSVP TE Tunnel).

Step 3 Configure the E1 interface at the BTS side.1. In the NE Explorer, select NE2 and choose Configuration > Interface Management >

PDH Interface from the Function Tree.2. Click the General Attributes tab. Select 3-ML1-1(Port-1) and 3-ML1-2(Port-2) and set

Port Mode to Layer 1.

NOTE

Before setting the port mode, ensure that the DCN of the port is disabled.

3. Click Apply. The Operation Result dialog box is displayed, indicating that the operationis successful. Click Close.

4. Click the Advanced Attributes tab. Select 3-ML1-2(Port-2) and set Frame Format toCRC-4 Multiframe. Select 3-ML1-1(Port-1) and set Frame Format to Unframe.


6. Display the NE Explorer for NE1. Perform Step 3.1 through Step 3.5 to set parameters ofrelevant E1 interfaces.

The general attributes and advanced attributes of each interface are consistent with thoseof NE2-3-ML1-1(Port-1).



3-113

Step 4 Configure the E1 interface on the BSC side. Display the NE Explorer for NE3. Perform Step3.1 through Step 3.5 to set parameters of relevant E1 interfaces.l The general attributes and advanced attributes of NE3-3-ML1-1(Port-1) are consistent with

those of NE2-3-ML1-1(Port-1).l The general attributes and advanced attributes of NE3-3-ML1-2(Port-2) are consistent with

those of NE2-3-ML1-2(Port-2).l The general attributes and advanced attributes of NE3-3-ML1-3(Port-3) are consistent with

those of NE1-3-ML1-1(Port-1).

Step 5 Create remote CES service 1.1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu.2. Set the parameters of the CES service.

Table 3-23 Parameters of general attributes


Service Type CES Set this parameteraccording to the networkplanning.

Service ID 4 A service ID uniquelyidentifies a service on theentire network.

Service Name CES Remote Service 1 Set this parameteraccording to the networkplanning.

Protection Type Protection-free Set this parameteraccording to the networkplanning.

3. Click Configure Source And Sink. A dialog box is displayed. On the Physical

Topology in the upper left portion of the window, set NE2 as the source NE. Set relevantparameters, click Add Node and click OK.




Issue 02 (2010-09-24)

Table 3-24 Parameters of the source node


Name 3-ML1-2 Set this parameteraccording to the networkplanning.

SAI Type CES Set this parameteraccording to the networkplanning.

ID Auto-Assign Indicates the SAI ID of aport. Set this parameteraccording to the networkplanning.

Channelized Checked l When working inchannelized mode, theCE1 port is divided into32 timeslots physically.You can bind any of thetimeslots excepttimeslot 0. The boundtimeslots work as asingle port whoselogical features are thesame as those of asynchronous serial port.

l When working in clearchannel mode, the CE1port does not supporttimeslotting.



3-115


64k timeslot 1-14,20 This parameter indicatesthe timeslot compressionlist for structured CESemulation services.Services are loaded in thetimeslots that are includedin the timeslot compressionlist, encapsulated into PWpackets, and thentransmitted to the peer endon an Ethernet. Servicesloaded in the timeslots thatare not included in thetimeslot compression listare not encapsulated intoPW packets and thus thenetwork bandwidth issaved. After receiving thePW packets, the peer endrestores the services to thecorresponding timeslotbased on its own timeslotcompression list. Thetimeslot lists at the two endscan be different, but thenumber of timeslots mustbe the same. Otherwise,services are unavailable.


Topology in the upper left portion of the window, set NE3 as the sink NE. Set relevantparameters, click Add Node and click OK.

Table 3-25 Parameters of the sink node


Name 3-ML1-2 Set this parameteraccording to the networkplanning.

SAI Type CES Set this parameteraccording to the networkplanning.




Issue 02 (2010-09-24)



Channelized Checked l When working inchannelized mode, theCE1 port is divided into32 timeslots physically.You can bind any of thetimeslots excepttimeslot 0. The boundtimeslots work as asingle port whoselogical features are thesame as those of asynchronous serial port.

l When working in clearchannel mode, the CE1port does not supporttimeslotting.

64k timeslot 1-14,20 This parameter indicatesthe timeslot compressionlist for structured CESemulation services.Services are loaded in thetimeslots that are includedin the timeslot compressionlist, encapsulated into PWpackets, and thentransmitted to the peer endon an Ethernet. Servicesloaded in the timeslots thatare not included in thetimeslot compression listare not encapsulated intoPW packets and thus thenetwork bandwidth issaved. After receiving thePW packets, the peer endrestores the services to thecorresponding timeslotbased on its own timeslotcompression list. Thetimeslot lists at the two endscan be different, but thenumber of timeslots mustbe the same. Otherwise,services are unavailable.



3-117

5. In PW in the lower left portion of the window, set relevant parameters.

Table 3-26 PW parameters


PW ID 8 A PW ID uniquelyidentifies a PW on theentire network.

Signaling Type Static This parameter specifieswhether a PW is dynamic orstatic. In the case of adynamic PW, services areavailable after a signalingnegotiation is successful. Inthe case of a static PW, asignaling negotiation is notrequired. In addition, youneed to configure UplinkLabel and DownlinkLabel for a static PW.

Forward Label 36 An uplink label is attachedto the packet header when aCES frame is encapsulatedinto a PW. An uplink labelis used for label switching.

Reverse Label 36 A downlink label isattached to the packetheader when a CES frame isencapsulated into a PW. Adownlink label is used forlabel switching.




Issue 02 (2010-09-24)


Forward Type Static Binding l If you set Uplink Typeto Static Binding, youneed to manuallyspecify a tunnel in theUplink Name area.

l If you set Uplink Typeto Select Policy, youneed to set the tunnelpriority in the UplinkName area so that thesystem selects a tunnelaccording to thepriority.



Reverse Type Static Binding l If you set DownlinkType to StaticBinding, you need tomanually specify atunnel in the DownlinkName area.

l If you set DownlinkType to Select Policy,you need to set thetunnel priority in theDownlink Name areaso that the systemselects a tunnelaccording to thepriority.



Encapsulation Type MPLS Set this parameteraccording to the networkplanning.

6. Click Advanced and configure Advanced PW Attribute.



3-119

Table 3-27 Parameters of advanced attributes


PW Type CESoPSN CESoPSN is the structuredemulation, for which thetimeslot compression canbe set. SAToP is the non-structured emulation, forwhich the timeslotcompression cannot be set.

Control Word Must Use On an MPLS PSN network,a control word carries thepacket information. Acontrol word is theencapsulation packetheader that consists of fourbytes. A control word canbe used to identify thepacket sequence or used forbit stuffing.

Control Channel Type CW Set this parameteraccording to the networkplanning.

VCCV Verification Mode Ping The VCCV verificationmode is used to detect theconnectivity of a PW.

RTP Header Disabled Set this parameteraccording to the networkplanning.

Emulation Level E1 Set this parameteraccording to the networkplanning.

Source Ingress Clock Mode Null Set this parameteraccording to the networkplanning.

Source Egress Clock Mode Null Set this parameteraccording to the networkplanning.

Sink Ingress Clock Mode Null Set this parameteraccording to the networkplanning.

Sink Egress Clock Mode Null Set this parameteraccording to the networkplanning.




Issue 02 (2010-09-24)

7. Click OK and the Operation Result dialog box is displayed indicating that the operationis successful. Click Close.

Step 6 Create remote CES service 2. For details, refer to Step 5.1 through Step 5.7.



Service Type CES Set this parameter accordingto the network planning.


Service Name CES Remote Service 2 Set this parameter accordingto the network planning.

Protection Type Protection-free Set this parameter accordingto the network planning.



Name 3-ML1-1 Set this parameter accordingto the network planning.

SAI Type CES Set this parameter accordingto the network planning.

ID Auto-Assign Indicates the SAI ID of a port.Set this parameter accordingto the network planning.








3-121



PW ID 9 A PW ID uniquely identifiesa PW on the entire network.

Signaling Type Static This parameter specifieswhether a PW is dynamic orstatic. In the case of adynamic PW, services areavailable after a signalingnegotiation is successful. Inthe case of a static PW, asignaling negotiation is notrequired. In addition, youneed to configure UplinkLabel and Downlink Labelfor a static PW.

Forward Label 37 An uplink label is attached tothe packet header when aCES frame is encapsulatedinto a PW. An uplink label isused for label switching.

Reverse Label 37 A downlink label is attachedto the packet header when aCES frame is encapsulatedinto a PW. A downlink labelis used for label switching.

Forward Type Static Binding l If you set Uplink Type toStatic Binding, you needto manually specify atunnel in the UplinkName area.

l If you set Uplink Type toSelect Policy, you need toset the tunnel priority inthe Uplink Name area sothat the system selects atunnel according to thepriority.


Set this parameter accordingto the network planning.




Issue 02 (2010-09-24)


Reverse Type Static Binding l If you set DownlinkType to Static Binding,you need to manuallyspecify a tunnel in theDownlink Name area.

l If you set DownlinkType to Select Policy,you need to set the tunnelpriority in the DownlinkName area so that thesystem selects a tunnelaccording to the priority.

Reverse Tunnel Working Tunnel-reverse(Tunnel-0101)


Encapsulation Type MPLS Set this parameter accordingto the network planning.



PW Type SAToP CESoPSN is the structuredemulation, for which thetimeslot compression can beset. SAToP is the non-structured emulation, forwhich the timeslotcompression cannot be set.

Control Word Must Use On an MPLS PSN network, acontrol word carries thepacket information. Acontrol word is theencapsulation packet headerthat consists of four bytes. Acontrol word can be used toidentify the packet sequenceor used for bit stuffing.

Control Channel Type CW Set this parameter accordingto the network planning.




3-123


RTP Header Disabled Set this parameter accordingto the network planning.

Emulation Level E1 Set this parameter accordingto the network planning.

Source Ingress Clock Mode Null Set this parameter accordingto the network planning.

Source Egress Clock Mode Null Set this parameter accordingto the network planning.

Sink Ingress Clock Mode Null Set this parameter accordingto the network planning.

Sink Egress Clock Mode Null Set this parameter accordingto the network planning.

Step 7 Create remote CES service 3. For details, refer to Step 5.1 through Step 5.7.



Service Type CES Set this parameter accordingto the network planning.


Service Name CES Remote Service 3 Set this parameter accordingto the network planning.









Issue 02 (2010-09-24)












Forward Label 35 An uplink label is attached tothe packet header when aCES frame is encapsulatedinto a PW. An uplink label isused for label switching.



3-125


Reverse Label 35 A downlink label is attachedto the packet header when aCES frame is encapsulatedinto a PW. A downlink labelis used for label switching.







Reverse Tunnel Working Tunnel-reverse(Tunnel-0121)






Issue 02 (2010-09-24)



PW Type SAToP CESoPSN is the structuredemulation, for which thetimeslot compression can beset. SAToP is the non-structured emulation, forwhich the timeslotcompression cannot be set.


Control Channel Type CW Set this parameter accordingto the network planning.


RTP Header Disabled Set this parameter accordingto the network planning.

Emulation Level E1 Set this parameter accordingto the network planning.

Source Ingress Clock Mode Null Set this parameter accordingto the network planning.

Source Egress Clock Mode Null Set this parameter accordingto the network planning.

Sink Ingress Clock Mode Null Set this parameter accordingto the network planning.

Sink Egress Clock Mode Null Set this parameter accordingto the network planning.

----End

3.6.7 Example for Configuring an ATM Emulation ServiceThis topic describes the example of configuring an ATM emulation service. Specifically, theexample description, service planning, and configuration process are provided.

3.6.7.1 Networking Diagram



3-127

This topic describes the networking topology of the NEs.


3.6.7.3 Configuration ProcessThis topic describes how to configure an ATM emulation service.


Between NodeB1 and RNC, NodeB2 and RNC, the IMA service is transported through theRTN equipment. Figure 3-28 shows the service networking requirements. The R99 service andHSDPA service each need to be transmitted over one PW. The committed bandwidth of eachPW is 4 Mbit/s, and the peak bandwidth of each PW is 10 Mbit/s.

Figure 3-28 Networking diagram of the IMA service

Packet Swtiching Network

RNC

Node B 2

IMA 1

NE1

UNI NNI NNI UNI

NE2

IMA 2

VPI1

VCI100

1 101R99

HSDPA

VPI60

VCI32

61 32

VPI1

VCI100

1 101R99

HSDPA

VPI50

VCI32

51 32

VPI50

VCI32

51 32

VPI50

VCI32

51 32

VPI60

VCI32

61 32

VPI60

VCI32

61 32

Node B 1

Service

Service





Issue 02 (2010-09-24)



Service Source NE (NE1) Sink NE (NE2)

MicrowavePort

Trunk Port MicrowavePort

Trunk Port

R99 service 4-IFE2-1 3-ML1-1(Trunk1)3-ML1-2(Trunk2)

4-IFE2-1 3-ML1-1(Trunk1)

HSDPA service 4-IFE2-1 3-ML1-1(Trunk1)3-ML1-2(Trunk2)

4-IFE2-1 3-ML1-1(Trunk1)

IMA Planning

Table 3-39 IMA planning

Parameter NE1 NE2

3-ML1-1(Trunk1) 3-ML1-2(Trunk2) 3-ML1-1(Trunk1)

IMA Protocol EnableStatus

Enabled Enabled Enabled

Binding Channel 3-ML1-(9-10) 3-ML1-(11-12) 3-ML1-(9-12)

Port Type UNI UNI UNI

ATM Cell PayloadScrambling

Enabled Enabled Enabled

Max. VPI 255 255 255

Max. VCI 127 127 127

VCC-Supported VPICount

32 32 32



3-129

ATM QoS Policy Planning

Table 3-40 ATM QoS policy planning

Parameter R99 Service HSDPA Service

Policy Name RT-VBR UBR (policy)

Service Type RT-VBR UBR

Traffic Type ClpTransparentNoScr NoTrafficDescriptor

Clp01Pcr(cell/s) 1000 -

Clp01Scr(cell/s) - -

Clp0Scr(cell/s) - -

MBS(cell) - -

CDVT(us) 100000 -

Enable Traffic FrameDiscarding

No No

UPC/NPC Enabled Enabled

ATM Service Planning

Table 3-41 ATM service planning


Service Name ATMService-R99 ATMService-HSDPA

Connect Type PVC PVC

Source NE NE1 NE1

Source Port 3-ML1-1(Trunk1)3-ML1-2(Trunk2)

3-ML1-1(Trunk1)3-ML1-2(Trunk2)

Sink NE NE2 NE2

Sink Port 3-ML1-1(Trunk1) 3-ML1-1(Trunk1)

ATM Connection 1 (the R99 service of NodeB1 and the HSDPA service of NodeB1)

Source Port 3-ML1-1(Trunk1) 3-ML1-1(Trunk1)

Source VPI 1 1

Source VCI 100 101





Issue 02 (2010-09-24)


Sink VPI 50 51

Sink VCI 32 32

Uplink ATM Policy RT-VBR UBR (policy)

Downlink ATM Policy RT-VBR UBR (policy)

Transit VPI 50 51

Transit VCI 32 32

ATM Connection 2 (the R99 service of NodeB2 and the HSDPA service of NodeB2)

Source Port 3-ML1-2(Trunk2) 3-ML1-2(Trunk2)

Source VPI 1 1

Source VCI 100 101


Sink VPI 60 61

Sink VCI 32 32

Uplink ATM Policy RT-VBR UBR (policy)

Downlink ATM Policy RT-VBR UBR (policy)

Transit VPI 60 61

Transit VCI 32 32

PW

PW ID 35 36

Signaling Type Dynamic Dynamic

PW Ingress Label 35 36

PW Egress Label 35 36

Link Type ATM N-to-1 VCC CellTransport

ATM N-to-1 VCC CellTransport

Direction Bidirectional Bidirectional

Uplink Tunnel 1(Tunnel-0001) 1(Tunnel-0001)

Downlink Tunnel 2(Tunnel-0002) 2(Tunnel-0002)

Control Word Must use Must use

Control Channel Type CW CW

VCCV Verification Mode Ping Ping



3-131


Max. Concatenated CellsCount

10 20


Mapping Between ATM CoSand CoS Priority

Default mapping Default mapping


This topic describes how to configure an ATM emulation service.

Prerequisite




A tunnel exists between NE1 and NE2.

Procedure

Step 1 Set LSR IDs.

1. In the NE Explorer, select NE1 and choose Configuration > MPLS Management > BasicConfiguration from the Function Tree.

2. Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.




3. In the NE Explorer of NE2, perform the preceding two steps to set the parameters, such asLSR ID.




Issue 02 (2010-09-24)




Step 2 Configure the tunnel that carries the ATM service. For details of the configuration, see 3.3.5.3Configuration Process (Creating a Static CR Tunnel) or 3.3.6.3 Configuration Process(Creating a RSVP TE Tunnel).

Step 3 Configure ATM ports on Node B.1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >

PDH Interface from the Function Tree to configure ports on Node B.2. Select the ports from 3-ML1-1(Port-1) to 3-ML1-8(Port-8). In the Port Mode field, right-

click, and choose Layer 2 from the shortcut menu. Click Apply.

NOTE

Before setting the frame format, ensure that the DCN of the port is disabled.

Set relevant parameters as follows:

l Port: ports from 3-ML1-1(Port-1) to 3-ML1-8(Port-8)l Name: NodeB ATM (You can set port names to distinguish different service ports for

easy location and query.)l Port Mode: Layer 2 (IMA signals are carried.)l Encapsulation Type: ATM

3. Click the Advanced Attributes tab. Select the ports from 3-ML1-1(Port-1) to 3-ML1-8(Port-8) and set Frame Format to CRC-4 Multiframe.



3-133

NOTE

Before setting the frame format, ensure that the DCN of the port is disabled.


l Port: ports from 3-ML1-1(Port-1) to 3-ML1-8(Port-8)l Frame Format: CRC-4 multiframe (The frame format must be same as the cell format

on Node B.)l Frame Mode: 31


5. Choose Configuration > Interface Management > ATM IMA Management from theFunction Tree. Click the Binding tab.

6. On the Binding tab page, click Configuration. Then, set the bound ports for 3-ML1-1(Trunk1) and 3-ML1-2(Trunk2). Click OK.




Issue 02 (2010-09-24)

Set the parameters relevant to 3-ML1-1(Trunk1) as follows:l Available Boards: 3-ML1l Configurable Ports: 3-ML1-1(Trunk1)l Level: E1

– E1: For the E1 card, when the E1 level is selected, the entire E1 channel is used totransmit ATM IMA signals.

– Fractional E1: For the E1 card, when the fractional E1 level is selected, certain 64kbit/s timeslots of an E1 channel are used to transmit ATM IMA signals. For theATM STM-1 card, when the fractional E1 level is selected, certain 64 kbit/s timeslotsof a VC12 lower order path are used to transmit ATM IMA signals. Before selectingthe fractional E1 level, ensure that the serial port for the 64 kbit/s timeslot is created.

l Direction: Bidirectional (default)l Optical Interface: -l Available Resources: ports from 3-ML1-9(Port-9) to 3-ML1-1(Port-10)l Available Timeslots: -

Set the parameters relevant to 3-ML1-2(Trunk2) as follows:l Available Boards: 3-ML1l Configurable Ports: 3-ML1-2(Trunk2)l Level: E1l Direction: Bidirectional (default)l Optical Interface: -l Available Resources: ports from 3-ML1-11(Port-11) to 3-ML1-12(Port-12)l Available Timeslots: -

7. On the IMA Group Management tab page, double-click the IMA Protocol EnableStatus field to enable the IMA protocol. Set other relevant parameters as required. ClickApply.



3-135

NOTEThe settings of IMA Protocol Version , IMA Transmit Frame Length , IMA Group ConfigurationMode , Maximum Delay Between Links (ms) , Minimum Number of Active Transmitting Links andMinimum Number of Active Receiving Links need to be the same as those on Node B.

8. On the ATM Interface Management tab page, set the parameters, such as Max VPI andMax VCI. Click Apply.


l Port Type: UNI (A UNI port is used to connect to the client-side equipment, and an NNIport is used to connect the ATM equipment on a core network.)

l ATM Cell Payload Scrambling: Enabled

l Max. VPI: 255 (Set this parameter according to the networking planning. You candetermine the value range of VPIs by setting Max VPI.)

l Max. VPI: 127(Set this parameter according to the networking planning. You candetermine the value range of VPIs by setting Max VPI.)

l VCC-Supported VPI Count: 32 (Set this parameter according to the networkingplanning.)

l Loopback: No Loopback

Step 4 Configure ATM ports on RNC. Display the NE Explorer for NE2. Perform Step 3.1 to Step3.8 to set parameters of relevant RNC-side interfaces.

Step 5 Create two UNI-NNI ATM services.

1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu. Createthe R99 service from NE1 to NE2.



Service Type ATM Set this parameteraccording to the networkplanning.




Issue 02 (2010-09-24)



Service Name ATMService-R99 Set this parameteraccording to the networkplanning.





Topology in the upper left portion of the window, set NE1 as the source NE. Set relevantparameters, click Add Node and click OK.



Name NE1-3-ML1-1(Trunk1)and NE1-3-ML1-2(Trunk2)

Set this parameteraccording to the networkplanning. There are twoUNI ports in this example.

Description P2MP P2P: point to pointP2MP: point to multi-point

SAI Type ATM Set this parameteraccording to the networkplanning.



Topology in the upper left portion of the window, set NE3 as the sink NE. Set relevantparameters, click Add Node and click OK.



3-137



Name NE2-3-ML1-1(Trunk1) Set this parameteraccording to the networkplanning.








Signaling Type Dynamic This parameter specifieswhether a PW is dynamic orstatic. In the case of adynamic PW, services areavailable after a signalingnegotiation is successful. Inthe case of a static PW, asignaling negotiation is notrequired. In addition, youneed to configure UplinkLabel and DownlinkLabel for a static PW.




Issue 02 (2010-09-24)




Forward Tunnel Tunnel-0001 Set this parameteraccording to the networkplanning.



Reverse Tunnel Tunnel-0002 Set this parameteraccording to the networkplanning.


5. Click ATM Link. In the dialog box that is displayed, set the parameters relevant to the

connection.



3-139

Table 3-46 Parameter for configuring a ATM connection


Connection Name Connection1 andConnection2


Source SAI Connection1: NE1-3-ML1-1(Trunk1)Connection2: NE1-3-ML1-2(Trunk2)


Source VPI Connection1: 1Connection2: 1

VPI information carried bythe service from a basestation.

Source VCI Connection1: 100Connection2: 100

VCI information carried bythe service from a basestation.

Source ATM Policy Connection1: RT-VBRConnection2: RT-VBR

Connection1 is an R99service and you need toselect the RT-VBR policyfor it.Connection2 is an R99service and you need toselect the RT-VBR policyfor it.

Sink SAI Connection1: NE2-3-ML1-1(Trunk1)Connection2: NE2-3-ML1-1(Trunk1)


Sink VPI Connection1: 50Connection2: 60

VPI information carried bythe service after a VPIswitching. Max VPI of anATM port is 255 accordingto the planning and thus thevalue of the VPI on the sinkranges between 0 and 255.

Sink VCI Connection1: 32Connection2: 32

VCI information carried bythe service after a VCIswitching. Max VCI of anATM port is 127 accordingto the planning and thus thevalue of the VPI on the sinkranges between 32 and 127.




Issue 02 (2010-09-24)


Sink ATM Policy Connection1: RT-VBRConnection2: RT-VBR

Connection1 is an R99service and you need toselect the RT-VBR policyfor it.Connection2 is an R99service and you need toselect the RT-VBR policyfor it.

6. Click Advanced and configure PW QoS, Advanced PW Attribute, and CE.



EXP 1 Set this parameteraccording to the networkplanning.

Control Word Must use On an MPLS PSN network,a control word carries thepacket information. Acontrol word is theencapsulation packetheader that consists of fourbytes. A control word canbe used to identify thepacket sequence or used forbit stuffing.

Control Channel Type CW A CW control word is usedto detect the connectivity ofa PW.


Source ATM CoS Map 1(mapping1) Set this parameteraccording to the networkplanning.

Sink ATM CoS Map 1(mapping1) Set this parameteraccording to the networkplanning.


10 Maximum number of ATMcells that can beencapsulated into a packet.



3-141


Packet Loading Time (us) 1000 Set this parameteraccording to the networkplanning.

7. Click OK. The ATMService-R99 service is created successfully.

8. Create the ATMService-HSDPA service. For details, refer to the preceding steps.



Service Type ATM Set this parameteraccording to the networkplanning.


Service Name ATMService-HSDPA Set this parameteraccording to the networkplanning.






Name NE1-3-ML1-1(Trunk1)and NE1-3-ML1-2(Trunk2)

Set this parameteraccording to the networkplanning. There are twoUNI ports in this example.






Issue 02 (2010-09-24)





Name NE2-3-ML1-1(Trunk1) Set this parameteraccording to the networkplanning.







Signaling Type Dynamic This parameter specifieswhether a PW is dynamic orstatic. In the case of adynamic PW, services areavailable after a signalingnegotiation is successful. Inthe case of a static PW, asignaling negotiation is notrequired. In addition, youneed to configure UplinkLabel and DownlinkLabel for a static PW.



3-143




Forward Tunnel Tunnel-0001 Set this parameteraccording to the networkplanning.



Reverse Tunnel Tunnel-0002 Set this parameteraccording to the networkplanning.





Issue 02 (2010-09-24)

Table 3-52 Parameter for configuring a ATM connection


Connection Name Connection1 andConnection2


Source SAI Connection1: NE1-3-ML1-1(Trunk1)Connection2: NE1-3-ML1-2(Trunk2)


Source VPI Connection1: 1Connection2: 1

VPI information carried bythe service from a basestation.

Source VCI Connection1: 101Connection2: 101

VCI information carried bythe service from a basestation.

Source ATM Policy Connection1: UBR(policy)Connection2: UBR(policy)

Connection1 is an HSDPAservice and you need toselect the UBR policy for it.Connection2 is an HSDPAservice and you need toselect the UBR policy for it.

Sink SAI Connection1: NE2-3-ML1-1(Trunk1)Connection2: NE2-3-ML1-1(Trunk1)


Sink VPI Connection1: 51Connection2: 61

VPI information carried bythe service after a VPIswitching. Max VPI of anATM port is 255 accordingto the planning and thus thevalue of the VPI on the sinkranges between 0 and 255.

Sink VCI Connection1: 32Connection2: 32

VCI information carried bythe service after a VCIswitching. Max VCI of anATM port is 127 accordingto the planning and thus thevalue of the VPI on the sinkranges between 32 and 127.



3-145


Sink ATM Policy Connection1: UBR(policy)Connection2: UBR(policy)

Connection1 is an HSDPAservice and you need toselect the UBR policy for it.Connection2 is an HSDPAservice and you need toselect the UBR policy for it.




Control Word Must use On an MPLS PSN network,a control word carries thepacket information. Acontrol word is theencapsulation packetheader that consists of fourbytes. A control word canbe used to identify thepacket sequence or used forbit stuffing.



Source ATM CoS Map 1(mapping1) Set this parameteraccording to the networkplanning.

Sink ATM CoS Map 1(mapping1) Set this parameteraccording to the networkplanning.


20 Maximum number of ATMcells that can beencapsulated into a packet.

Packet Loading Time (us) 1000 Set this parameteraccording to the networkplanning.




Issue 02 (2010-09-24)

----End

3.6.8 Example for Configuring an Ethernet Private Line EmulationService

This topic describes the example of configuring an Ethernet private line emulation service.Specifically, the example description, service planning, and configuration process are provided.



3.6.8.3 Configuration ProcessThis topic describes how to configure an Ethernet private line emulation service.


Between NodeB and RNC, BTS and BSC, the Ethernet service is transported through theRTN equipment, as shown in Figure 3-29.

Figure 3-29 Networking diagram of the Ethernet service

NE1

NodeB

RNC

NE2

FEFE

BTS

FE

FE

Packet Swtiching Network

BSC




3-147



Service Source NE Sink NE

FE Port MicrowavePort

MicrowavePort

FE Port

NodeB-sideservice

2-EF8T-1 3-IFE2-1 3-IFE2-1 2-EF8T-1

BTS-sideservice

2-EF8T-2 3-IFE2-1 3-IFE2-1 2-EF8T-2

Ethernet Service Planning

Table 3-55 Ethernet service planning

Parameter NodeB-SideService

BTS-SideService

RNC-SideService

BSC-SideService

NE1 NE2

Service ID 1 2 1 2

Service Name E-Line-1 E-Line-2 E-Line-1 E-Line-2

ServiceDirection

UNI-NNI UNI-NNI UNI-NNI UNI-NNI

UNI 2-EF8T-1(Port-1)

2-EF8T-2(Port-2)

2-EF8T-1(Port-1)

2-EF8T-2(Port-)

VLANs 100 200 100 200

BPDUBPDU

Non-transparenttransmission




Bearer Type PW PW PW PW

PW ID 35 45 35 45

PWSignalingType

Static Static Static Static

PW Type Ethernet tagmode

Ethernet tagmode

Ethernet tagmode

Ethernet tagmode

Direction Bidirectional Bidirectional Bidirectional Bidirectional

Forward Label 20 30 20 30

Reverse Label 20 30 20 30




Issue 02 (2010-09-24)

Parameter NodeB-SideService

BTS-SideService

RNC-SideService

BSC-SideService

NE1 NE2

Peer IP 10.10.10.2 10.10.10.2 10.10.10.1 10.10.10.1

Tunnel 1(Tunnel-0001) 1(Tunnel-0001) 2(Tunnel-00012)

2(Tunnel-0002)


This topic describes how to configure an Ethernet private line emulation service.

Prerequisite




A tunnel exists between NE1 and NE2.

Procedure

Step 1 Set LSR IDs.

1. In the NE Explorer, select NE1 and choose Configuration > MPLS Management > BasicConfiguration from the Function Tree.

2. Set LSR ID, Start of Global Label Space, and other parameters. Click Apply.




3. In the NE Explorer of NE2, perform the preceding two steps to set the parameters, such asLSR ID.



3-149




Step 2 Configure the tunnel that carries the E-Line service. For details of the configuration, see 3.3.5.3Configuration Process (Creating a Static CR Tunnel) or 3.3.6.3 Configuration Process(Creating a RSVP TE Tunnel).

Step 3 Configure ports.1. In the NE Explorer, select NE1 and choose Configuration > Interface Management >

Ethernet Interface from the Function Tree to configure ports.2. On the General Attributes tab page, select 2-EF8T-1(Port-1) and 2-EF8T-2(Port-2) and

set the parameters, such as Port Mode and Working Mode, for those ports. ClickApply.


Port: 2-EF8T-1(Port-1) and 2-EF8T-2(Port-2)l Enable Port: Enabledl Port Mode: Layer 2 (UNI port for accessing services of NodeB-side and BTS-side.)l Encapsulation Type: 802.1Ql Working Mode: Auto-Negotiationl Max Frame Length: 1620

3. Display the NE Explorers of NE2 and set the parameters relevant. For details, refer to Step3.1 through Step 3.2.

Step 4 Configure an Ethernet private line (EPL) service.1. Choose Service > PWE3 Service > Create PWE3 Service from the main menu.2. Set the parameters of the E-Line-1 Ethernet service.




Issue 02 (2010-09-24)



Service Type ETH Set this parameteraccording to the networkplanning.


Service Name E-Line-1 Set this parameteraccording to the networkplanning.


3. Click Configure Source And Sink. A dialog box is displayed. On the PhysicalTopology in the upper left portion of the window, set NE1 as the source NE. Set relevantparameters, click Add Node and click OK.



Name 2-EF8T-1(Port-1) NodeB-side is connected to2-EF8T-1(Port-1).

SAI Type ETH Set this parameteraccording to the networkplanning.

Connect Type VLAN Subinterface Set this parameteraccording to the networkplanning.

4. Click Configure Source And Sink. A dialog box is displayed. On the PhysicalTopology in the upper left portion of the window, set NE3 as the sink NE. Set relevantparameters, click Add Node and click OK.



Name 2-EF8T-1(Port-1) RNC-side is connected to2-EF8T-1(Port-1).



3-151


SAI Type ETH Set this parameteraccording to the networkplanning.

Connect Type VLAN Subinterface Set this parameteraccording to the networkplanning.





Signaling Type Static This parameter specifieswhether a PW is dynamic orstatic. In the case of adynamic PW, services areavailable after a signalingnegotiation is successful. Inthe case of a static PW, asignaling negotiation is notrequired. In addition, youneed to configure UplinkLabel and DownlinkLabel for a static PW.

Forward Label 20 An uplink label is attachedto the packet header whenan Ethernet frame isencapsulated into a PW. Anuplink label is used for labelswitching.

Reverse Label 20 A downlink label isattached to the packetheader when an Ethernetframe is encapsulated into aPW. A downlink label isused for label switching.




Issue 02 (2010-09-24)




Forward Tunnel Tunnel-0001(Forward) Set this parameteraccording to the networkplanning.



Reverse Tunnel Tunnel-0002(Reverse) Set this parameteraccording to the networkplanning.


6. Click Advanced and configure SAI QoS, PW QoS, Advanced PW Attributes, Service

Parameter and CE. Use the default value for SAI QoS.



3-153

Table 3-60 Service parameters


MTU(byte) 1526 Set this parameteraccording to the networkplanning.

BPDU Not TransparentlyTransmitted


Service Tag User Set this parameteraccording to the networkplanning.

Table 3-61 PW QoS parameters



LSP Mode Uniform The CoS of user packetsneeds to be restored whenthe tunnel labels arestripped.



PW Type Ethernet tag mode Set this parameteraccording to the networkplanning.

Control Word Must Use On an MPLS PSN network,a control word carries thepacket information. Acontrol word is theencapsulation packetheader that consists of fourbytes. A control word canbe used to identify thepacket sequence or used forbit stuffing.




Issue 02 (2010-09-24)




7. Click OK. The E-Line-1 Ethernet service is created.

Step 5 Create the E-Line-2 Ethernet service. For details, refer to Step 4.1 through Step 4.7.



Service Type ETH Set this parameter accordingto the network planning.


Service Name E-Line-2 Set this parameter accordingto the network planning.




Name 2-EF8T-2(Port-2) BTS-side is connected to 2-EF8T-2(Port-2).

SAI Type ETH Set this parameter accordingto the network planning.

Connect Type VLAN Subinterface Set this parameter accordingto the network planning.



3-155



Name 2-EF8T-2(Port-2) BSC-side is connected to 2-EF8T-2(Port-2).

SAI Type ETH Set this parameter accordingto the network planning.

Connect Type VLAN Subinterface Set this parameter accordingto the network planning.





Forward Label 30 An uplink label is attached tothe packet header when anEthernet frame isencapsulated into a PW. Anuplink label is used for labelswitching.

Reverse Label 30 A downlink label is attachedto the packet header when anEthernet frame isencapsulated into a PW. Adownlink label is used forlabel switching.




Issue 02 (2010-09-24)




Forward Tunnel Tunnel-0001(Forward) Set this parameter accordingto the network planning.



Reverse Tunnel Tunnel-0002(Reverse) Set this parameter accordingto the network planning.


Table 3-67 Service parameters


MTU(byte) 1526 Set this parameter accordingto the network planning.

BPDU Not TransparentlyTransmitted


Service Tag User Set this parameter accordingto the network planning.



3-157

Table 3-68 PW QoS parameters


EXP 4 Set this parameter accordingto the network planning.

LSP Mode Uniform The CoS of user packetsneeds to be restored when thetunnel labels are stripped.



PW Type Ethernet tag mode Set this parameter accordingto the network planning.


Control Channel Type CW A CW control word is used todetect the connectivity of aPW.


----End

3.7 Modifying ConfigurationsThis topic describes how to modify service configurations, which includes modifying anddeleting service configurations.

3.7.1 Modifying Tunnel AttributesThis topic describes how to modify tunnel attributes, which includes modifying and deletingtunnels.

3.7.2 Modifying PWE3 AttributesThis topic describes how to modify PWE3 attributes. When certain existing PWE3 services needto be adjusted, you need to modify the related attributes.




Issue 02 (2010-09-24)

3.7.1 Modifying Tunnel AttributesThis topic describes how to modify tunnel attributes, which includes modifying and deletingtunnels.

3.7.1.1 Modifying a TunnelThis topic describes how to modify a tunnel.

3.7.1.2 Deleting a TunnelThis topic describes how to delete a tunnel.

3.7.1.1 Modifying a TunnelThis topic describes how to modify a tunnel.


Procedure



Step 3 Select a tunnel, and then click the related tabs to modify the related parameters.

NOTE

If you need to modify only the basic information about a tunnel, right-click the tunnel and chooseDetails from the shortcut menu.

----End

3.7.1.2 Deleting a TunnelThis topic describes how to delete a tunnel.


ContextDeleting a tunnel is to delete a configured tunnel from the NMS and equipment at the same time.

Procedure



Step 3 Right-click one or more services and choose Delete from the shortcut menu.



3-159

Step 4 In the Confirm dialog box, click Yes.

----End

3.7.2 Modifying PWE3 AttributesThis topic describes how to modify PWE3 attributes. When certain existing PWE3 services needto be adjusted, you need to modify the related attributes.

3.7.2.1 Modifying a PWE3 ServiceThis topic describes how to modify a PWE3 service. When certain existing PWE3 services needto be adjusted, you need to modify the related attributes.

3.7.2.2 Deleting a PWE3 ServiceThis topic describes how to delete a PWE3 service. You can delete a PWE3 service if it isinapplicable, for example, when the network is adjusted.

3.7.2.3 Deleting a PWE3 Service on the Network SideThis topic describes how to delete a PWE3 service from the network side. After a PWE3 serviceis deleted from the network side, the information about the PWE3 service is deleted from theNMS, the VSI in the PWE3 service changes to a discrete service, but the configurations on theNE side are not affected.

3.7.2.4 Undeploying a PWE3 ServiceThis topic describes how to undeploy a PWE3 service. Undeploying a PWE3 service is deletingthe PWE3 service from the NE side only. The service data still exists on the NMS side, and theservice status changes from Deployed to Undeployed.

3.7.2.1 Modifying a PWE3 Service

This topic describes how to modify a PWE3 service. When certain existing PWE3 services needto be adjusted, you need to modify the related attributes.

Procedure



Step 3 Right-click a service and choose Details from the shortcut menu.

Step 4 In the details, Set the related parameters as required..

Step 5 Click OK to return to the main user interface.

----End

3.7.2.2 Deleting a PWE3 Service

This topic describes how to delete a PWE3 service. You can delete a PWE3 service if it isinapplicable, for example, when the network is adjusted.




Issue 02 (2010-09-24)

Procedure



Step 3 Right-click one or more services and choose Delete from the shortcut menu.


----End

3.7.2.3 Deleting a PWE3 Service on the Network SideThis topic describes how to delete a PWE3 service from the network side. After a PWE3 serviceis deleted from the network side, the information about the PWE3 service is deleted from theNMS, the VSI in the PWE3 service changes to a discrete service, but the configurations on theNE side are not affected.

Procedure



Step 3 Right-click one or more services and choose Delete from Network Side from the shortcut menu.


----End

PostrequisiteAfter a PWE3 service is deleted from the network side, the information about the PWE3 serviceis deleted from the NMS and cannot be viewed in PWE3 service management. The PWinformation related to the PWE3 service, however, can be viewed in discrete servicemanagement.

3.7.2.4 Undeploying a PWE3 ServiceThis topic describes how to undeploy a PWE3 service. Undeploying a PWE3 service is deletingthe PWE3 service from the NE side only. The service data still exists on the NMS side, and theservice status changes from Deployed to Undeployed.

Procedure



Step 3 Right-click a service with Deployment Status being Deployed and choose Undeploy from theshortcut menu.




3-161

After the service is undeployed, the value of Deployment Status changes from Deployed toUndeployed.

----End

PostrequisiteAfter the service is undeployed, you can redeploy the service. If the service fails to beundeployed, you can modify the service according to the error message, and then undeploy theservice again.




Issue 02 (2010-09-24)

Documents

OG for RTN End-To-End Management-(V100R002C01 02)[1]